Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-28856

Remove sentence

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci HRex (FHIR)
    • current
    • Clinical Interoperability Council
    • Approaches to Exchanging FHIR Data
    • 3.0 Approaches
    • Hide

      Will reword "Following the guidance here is not required to claim FHIR conformance but diverging from these recommendations may result in higher long-term implementation costs, fewer interoperability partners, or both." to

      "Following the guidance here is not required to claim FHIR conformance but adhering to these recommendations is likely to result in lower long-term implementation costs, more interoperability partners, etc."

      Show
      Will reword "Following the guidance here is not required to claim FHIR conformance but diverging from these recommendations may result in higher long-term implementation costs, fewer interoperability partners, or both." to "Following the guidance here is not required to claim FHIR conformance but adhering to these recommendations is likely to result in lower long-term implementation costs, more interoperability partners, etc."
    • Marti Velezis / Jimmy Tcheng : 6-0-1
    • Clarification
    • Non-substantive

    Description

      I think that in particular we’d want this sentence removed, as it is going to discourage people from using the “less preferable” options – perhaps prematurely.

      Existing Wording:

      Following the guidance here is not required to claim FHIR conformance but diverging from these recommendations may result in higher long-term implementation costs, fewer interoperability partners, or both.

      Attachments

        Activity

          People

            Unassigned Unassigned
            celine_lefebvre Celine Lefebvre
            Celine Lefebvre
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: