Remove dangerous constraints from medication list guidance

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Highest
    • US Core (FHIR)
    • 3.1.1
    • Cross-Group Projects
    • Medication List Guidance [deprecated]
    • Hide

      The commenter is correct to point out the dangerous fragmentation of FHIR Medication resources which requires a client application to merge data with many disparate resources to provide a single 'Active Medication List'.

      To mitigate that risk, the designers of US Core worked closely with many vendors to achieve consensus on a single resource to serve all Active Medication of content. Please see:
      https://build.fhir.org/ig/HL7/US-Core/medication-list-guidance.html

      Show
      The commenter is correct to point out the dangerous fragmentation of FHIR Medication resources which requires a client application to merge data with many disparate resources to provide a single 'Active Medication List'. To mitigate that risk, the designers of US Core worked closely with many vendors to achieve consensus on a single resource to serve all Active Medication of content. Please see: https://build.fhir.org/ig/HL7/US-Core/medication-list-guidance.html
    • Brett Marquard/Gay Dolin: 9-0-3

      The changes do not address the problematic guidance that not only may implementers support medication lists with a single resource but that they must do so, seemingly causing US implementers to need to design extensions to support information that already exists in the core spec\.

      Existing Wording:

      A MedicationRequest resource query:

      SHALL be all that is required.

      (Comment 72 - imported by: Jean Duteau)

            Assignee:
            Unassigned
            Reporter:
            klsalzman
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: