Medication Prescription and Dispense (MPD)
0.1.0 - ci-build
Medication Prescription and Dispense (MPD), published by Integrating the Healthcare Enterprise (IHE). This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/pharm-mpd/tree/jct-wip and changes regularly. See the Directory of published versions
For managing the lifecycle of orders (from proposal to draft or plan, to active prescription and fulfilled prescription), and considering the variety of use cases and architectures that this profile is intended to support (Push, Pull, central repositories, etc.), IHE presents the following actors for managing orders - submission and retrieval:
For Dispense, a similar approach is taken:
Table XX.1-1: IHE MPD - Actors and Transactions
| Actors | Transactions | Initiator or Responder | Optionality | Reference |
| Medication Order Placer | PHARM-5 | Initiator | O | PHARM MPD TF-2: 3.Y1 |
| Medication Order Receiver | PHARM-5 | Responder | O | PHARM MPD TF-2: 3.Y1 |
| Medication Order Consumer | PHARM-7 | Initiator | R | PHARM MPD TF-2: 3.Y1 |
| Medication Order Responder | PHARM-7 | Responder | R | PHARM MPD TF-2: 3.Y1 |
| Medication Dispense Reporter | PHARM-8 | Initiator | R | PHARM MPD TF-2: 3.Y1 |
| Medication Dispense Receiver | PHARM-8 | Responder | R | PHARM MPD TF-2: 3.Y1 |
| Medication Dispense Consumer | PHARM-9 | Initiator | R | PHARM MPD TF-2: 3.Y1 |
| Medication Dispense Responder | PHARM-9 | Responder | R | PHARM MPD TF-2: 3.Y1 |
Note 1: The transaction PHARM-5 for submitting an order uses the MedicationRequest. IHE REcognizes that in common cases, the request also includes other resources, so in future editions we expect to prepare a new transaction for submitting medication orders. This current specification only provides the transaction using MedicationRequest.
The actors in this profile are described in more detail in the sections below.
This is used in a Pull scenario, where an Order Consumer (or other actors) can query the existing orders from the Order Responder.
No options are defined at the moment.
No actor groupings are defined at the moment.