Why is VisionPrescription a request - 2016-09 core #575

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Duplicate
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • FHIR Infrastructure
    • Workflow
    • 12.1.1
    • Hide

      A VisionPrescription is an authorization for a dispense to occur - in the same manner as a MedicationPrescription is an authorization for a dispense to occur, a ReferralRequest is an authorization for an encounter to occur, etc. The actual "fulfillment request" is handled by Task. But from a workflow perspective, this is definitely a Request (i.e. INT mood), not an Event (i.e. EVN mood)

      Show
      A VisionPrescription is an authorization for a dispense to occur - in the same manner as a MedicationPrescription is an authorization for a dispense to occur, a ReferralRequest is an authorization for an encounter to occur, etc. The actual "fulfillment request" is handled by Task. But from a workflow perspective, this is definitely a Request (i.e. INT mood), not an Event (i.e. EVN mood)
    • Correction

      Existing Wording: "Not all resources in FHIR are related to workflow - many are used to describe entities and roles (patients, medications, etc.) or infrastructure (structure definitions, value sets, etc.)."

      Comment:

      12.1.1.1 lists a VisionPrescription as a request. VisionPrescription is not a request, it is an authorization from a licensed provider authorizing the provision of controlled products/services which conform to the prescription to the specified individuals(s). VisionPrescriptions may be referred to by multiple requests but cannot be 'actioned on their own'.

      Prescriptions in general would more closely match the 'Event' resources - statements of fact.

      Summary:

      Why is VisionPrescription a request

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

              Created:
              Updated:
              Resolved: