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

MedicationRequest can not be used for conveying "Patient-Reported medications"

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Core (FHIR)
    • Structured Documents
    • (many)
    • Hide

      Do everything in the previous resolution except for point #3.3 where the SHALL is replaced with SHOULD:

      1. When recording “self-prescribed” medications-orders-, *SHALL*SHOULD use the requester to indicate the Patient or RelatedPerson as the prescriber.
      Show
      Do everything in the previous resolution except for point #3.3 where the SHALL is replaced with SHOULD: When recording “self-prescribed” medications-orders-, * SHALL * SHOULD use the requester to indicate the Patient or RelatedPerson as the prescriber.
    • Eric Haas / Floyd Eisenberg: 9-0-0
    • Correction
    • Non-substantive

    Description

      In the recent US-Core ballot, there was an issue raised about the use of the MedicationRequest and MedicationStatement. The resolution to that issue effectively changed the scope of the MedicationRequest resource.

      The MedicationRequest resource is an Order resource and represents an actual order for a medication for a patient. It can be "patient-reported" but that is just the patient reporting that they received an order for a medication that might not have been formally ordered in a clinician's system.

      It definitely can not be used to represent what is more commonly understood as a "Patient-reported medication" which is when a patient wants to communicate "I am taking/plan to take/did take this medication". That is the scope of the MedicationStatement resource which is an Event resource.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jduteau Jean Duteau
            Jean Duteau
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: