Prescriptions and Orders should remain distinct - 2016-09 core #592

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • FHIR Infrastructure
    • Workflow
    • 12.1.3
    • Hide

      Will add a usage note to Request indicating the following:

      The amount of information needed for a Request to be actionable can vary by circumstance. Some request instances may not be "fully specified" - additional information from protocol, patient preference and/or professional decision-making may be necessary before the authorized action can occur. For example, a MedicationOrder might be specified without indicating a strength or route in situations where the pharmacy (or even nursing information) has the authority to determine those parameters. A VisionPrescription might not be actionable until frames have been chosen and the necessary measurements of the patient's face have been taken to allow the lenses to be positioned appropriately within the frames.

      All requests with an intent of "order" authorize something. Whether what is authorized is sufficient to be immediately actionable depends on who is fulfilling the order and the context in which the fulfillment request is made. The determination of whether a given "request" is actionable may be made by the systems involved or the humans being asked to act.

      As well, the existence of a "Request" instance doesn't necessarily imply that fufillment will be requested immediately - or even ever. The decision to request fulfillment may be delegated to the patient or to down-stream practitioners. Such fufilling practitioners may need to capture additional information prior to executing the fufillment.

      Show
      Will add a usage note to Request indicating the following: The amount of information needed for a Request to be actionable can vary by circumstance. Some request instances may not be "fully specified" - additional information from protocol, patient preference and/or professional decision-making may be necessary before the authorized action can occur. For example, a MedicationOrder might be specified without indicating a strength or route in situations where the pharmacy (or even nursing information) has the authority to determine those parameters. A VisionPrescription might not be actionable until frames have been chosen and the necessary measurements of the patient's face have been taken to allow the lenses to be positioned appropriately within the frames. All requests with an intent of "order" authorize something. Whether what is authorized is sufficient to be immediately actionable depends on who is fulfilling the order and the context in which the fulfillment request is made. The determination of whether a given "request" is actionable may be made by the systems involved or the humans being asked to act. As well, the existence of a "Request" instance doesn't necessarily imply that fufillment will be requested immediately - or even ever. The decision to request fulfillment may be delegated to the patient or to down-stream practitioners. Such fufilling practitioners may need to capture additional information prior to executing the fufillment.
    • Jose Costa Teixeira/Hans Buitendijk: 7-0-0
    • Correction
    • Non-substantive
    • DSTU2

      Existing Wording: The SupplyRequest, DeviceUseRequest and VisionPrescription resources have a significant degree of overlap. Should they remain distinct resources?

      Comment:

      The Prescription is an authorization to dispense controlled goods or services which conform to the Prescribed specification by a party licensed to give that authorization. Prescriptions may be referred to by multiple orders. The Request resources are orders for goods or services by whomever. The intents and content model are different, therefore the Prescription should remain distinct from the Orders (Requests).

      Summary:

      Prescriptions and Orders should remain distinct

            Assignee:
            Unassigned
            Reporter:
            Paul Knapp
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: