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

Remove dangerous constraints from medication list guidance

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Resolved - No Change (View Workflow)
    • Highest
    • Resolution: Not Persuasive
    • US Core (FHIR)
    • 3.1.1
    • Cross-Group Projects
    • Medication List Guidance
    • 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

    Description

      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)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              klsalzman Keith Salzman
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: