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

MedicationRequest.medication[x]

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Applied (View Workflow)
    • Priority: Highest
    • Resolution: Not Persuasive with Modification
    • Specification:
      US Core (FHIR)
    • Raised in Version:
      3.1.1
    • Work Group:
      Cross-Group Projects
    • Related Artifact(s):
      USCoreMedicationRequestProfile
    • Resolution Description:
      Hide

      As part of a general clarification of Must Support - add implementation guidance that systems Must Support either a code, or a reference to Medication resource, or Both. Systems are not required to support both.

       

      (reviewed with commenter on 10/29/2020 - ok to vote on CGP) 

       

      Show
      As part of a general clarification of Must Support - add implementation guidance that systems Must Support either a code, or a reference to  Medication  resource, or Both. Systems are not required to support both.   (reviewed with commenter on 10/29/2020 - ok to vote on CGP)   
    • Resolution Vote:
      Brett Marquard/Gay Dolin:11-0-0
    • Change Category:
      Clarification
    • Change Impact:
      Non-substantive

      Description

      In context of https://jira.hl7.org/browse/FHIR-28375 we propose that MedicationRequest.medication[x] does not require both the .medicationCodeableConcept and .medicationReference.

      We note that the current construct where within .medicationReference only the .code is required thus effectively being the same as medicationCodeableConcept, while also systems only need to convey the code without the other details. A system that only maintains the medication code (RxNorm) would be required, under current requirements, to “support” both options for sending the exact same information. Therefore, .medication as a reference should be optional and available for use in systems that store and need to convey the additional, optional information (as per US Core) that comes into play with compounded medications.

      As the FHIR US Core profile is used for accessing and exchanging data based on what the source system has, this should not require the data source system to add functionality to capture a patient as part of the provenance.

      Links to pages:

      http://hl7.org/fhir/us/core/StructureDefinition-us-core-medicationrequest.html

      https://build.fhir.org/ig/HL7/US-Core-R4/StructureDefinition-us-core-medicationrequest.html

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              hbuitendijk Hans Buitendijk
              Request in-person:
              Drew Torres, Hans Buitendijk
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: