Medication Prescription and Dispense (MPD)
1.0.0-comment-3 - ballot

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 1.0.0-comment-3 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/115/merge and changes regularly. See the Directory of published versions

## Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

### Requirements: Actor Definitions

The following artifacts define the types of individuals and/or systems that will interact as part of the use cases covered by this implementation guide.

IHE MPD Dispense Consumer | The Dispense Consumer retrieves dispense records from the Dispense Responder.
IHE MPD Dispense Receiver | The Dispense Receiver accepts and stores dispense reports from the Dispense Reporter.
IHE MPD Dispense Reporter | The Dispense Reporter submits dispense reports to the Dispense Receiver.
IHE MPD Dispense Responder | The Dispense Responder provides access to dispense records to the Dispense Consumer.
IHE MPD Order Consumer | The Order Consumer retrieves medication orders for dispensing or review.
IHE MPD Order Placer | The Order Placer is responsible for submitting a medication order to an Order Receiver.
IHE MPD Order Receiver | The Order Receiver processes received medication orders and may store or forward them for further processing.
IHE MPD Order Responder | The Order Responder provides access to medication orders stored in the system.

### Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

IHE MPD Dispense Consumer Actor | The CapabilityStatement for the Dispense Consumer Actor describes the requirements for systems that retrieve dispense data.
IHE MPD Dispense Receiver Actor (server) | The CapabililtyStatement for the Dispense Receiver Actor expresses the compliance requirements for systems implementing the actor.
IHE MPD Dispense Reporter Actor (server) | The CapabililtyStatement for the Dispense Reporter Actor expresses the compliance requirements for systems implementing the actor.
IHE MPD Dispense Responder Actor (server) | The CapabililtyStatement for the Dispense Responder Actor expresses the compliance requirements for systems implementing the actor.
IHE MPD Order Consumer Actor | The CapabililtyStatement for the Order Consumer Actor expresses the compliance requirements for systems implementing the actor.
IHE MPD Order Placer Actor | The CapabililtyStatement for the Order Placer Actor expresses the compliance requirements for systems implementing the actor.
IHE MPD Order Receiver Actor (server) | The CapabililtyStatement for the Order Receiver Actor expresses the compliance requirements for systems implementing the actor.
IHE MPD Order Responder Actor (server) | The CapabililtyStatement for the Order Responder Actor expresses the compliance requirements for systems implementing the actor.

### Behavior: Search Parameters

These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.

activity-resource | Search on the resources that are linked to a RequestOrchestration - important to allow for example _revInclude
group-or-identifier | Single search on both request.identifier or groupIdentifier

### Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

Device (model) | Logical model for a device (basic data relevant for the IHE MPD use cases)
Dosaging (model) | Logical model for usage instructions for administring the requested product. Based on FHIR Dosage complex data type.
Medication dispense (model) | Logical model for medication dispense report (based on request or independently)
Medication order (model) | Logical model for medication prescription or other types of medication orders
Medication order - multiline (model) | Logical model for multiline medication prescription
Medicinal product (model) | Logical model for prescribed/dispensed medication. The model is shared by statements, requests, dispensations, and treatment lines. Each of those may have different restrictions in FHIR profile.
Organization (model) | Logical model for an organization (basic data relevant for IHE MPD use cases)
Patient (model) | Logical model for patient (basic data relevant for this use case)
Practitioner (model) | Logical model for practitioner (basic data relevant for this use case)
Practitioner role (model) | Logical model for a practitioner role within an organization (basic data relevant for this use case)
Related person (model) | Logical model for a related person with basic data relevant to the IHE MPD use cases.

### Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

IHE Medication | Medication for clinical use cases. This could be a branded product or a generic concept, also allowing describing pack size and components of complex products.
IHE Medication Dispense | MedicationDispense profile for capturing dispensation information based on a medication prescription.
IHE Medication Order | IHE Medication Order profile

### Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

Medication - Characteristic | Any characteristic of the medicinal product prescribed or dispensed (for example, price, textual package description, special program information, etc)
Medication - Classification | Medication classification/category. Allows the product to be classified by various systems, e.g ATC, narcotic class, legal status of supply, etc..
Medication - Device | Device, typically an administration device, included in the medicinal product.
Medication - Ingreditne role | Medication ingredient role - whether it is an active ingredient, excipient, adjuvant, solvent, flavouring, etc.
Medication - Product Name | Name of the medicinal product. This is typically the name of a real product as registered. This element should not contain display names of virtual product concepts.
Medication - Size of Item | Size of a manufactured item or unit of presentation. For example, size of one vial in a package that may contain several vials.
Medication - Strength substance | Substance for marking the basis of strength. When the precise active ingredient is a salt, the strength is often provided for the active moiety (basis of strength).
Medication - Strength type | Strength type (e.g. concentration strength, presentation strength)
Medication - Unit of presentation | Unit of presentation, typically describing the smallest countable package item (e.g tablet, vial, ampoule, etc). Unit of presentation is also often used in describing pack size and the denominator of strength. If the size of presentation unit is relevant, it should be described in sizeOfItem extension.
MedicationRequest - Prescribed Quantity | Total amount of product being requested. This may refer to number of packages when package size is indicated in Medication resource.
Off-label use | Indicates that the prescriber has intentionally prescribed the medication in a manner not covered by the product authorization — such as for a different indication, age group, dosage, or route of administration.

### Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

01A-Cefuroxime1500GenericExplicit | 1A. Cefuroxime 1500mg (1.5g) powder for solution in a vial. Generic product, defined by attributes.
01B-Cefuroxime1500GenericConcept | 1B. Cefuroxime 1500mg (1.5g) powder for solution in a vial. Generic product, defined by a code system (receiving system is expected to have access to the code system for additional attributes or display names).
01C-Cefuroxime1500Branded | 1C. Cefuroxime 1500mg (1.5g) powder for solution in a vial. Branded packaged product, defined by attributes.
01D-Cefuroxime750Branded | 1D. Cefuroxime 750mg powder for solution in a vial (5 vials per package). Branded packaged product, defined by attributes.
02A-ClotrimazoleCanifugCremolum | 2A. Clotrimazole cream 10mg/g and 6 pessaries 100g. Branded packaged product, consisting of different medication items. Defined by attributes.
02A1-CanifugCremolumCreamItem | 2A2. Clotrimazole cream (10mg/g, 1 tube of 20g) as part of Canifug Cremolum product (ISO IDMP manufactured item)
02A2-CanifugCremolumPessaryItem | 2A1. Clotrimazole pessary (6 pessaries of 100mg) as part of Canifug Cremolum product (ISO IDMP manufactured item)
03B-VitaminBComplexBranded | 3B. Milgamma N, B-vitamin complex. Branded packaged product, defined by attributes.
04-FirmagonBranded | 4A. Firmagon. Branded packaged product, defined by attributes, includes administration devices.
05A-Tilidin-Branded | 05A. Tilidin (50mg), Naloxon (4mg) oral drops. Branded packaged product, defined by attributes. Unusual strength.
10-dispense-1 | Medication dispense fulfilling the first part of the order: 1 package containing 10 vials
10-dispense-2 | Medication dispense fulfilling the second part of the order: 3 packages containing 5 vials each
10-prescription-cefuroxime-singleline | A prescription/request with one medication and changing dosaging. Uses 'actionable' tag. Cefuroxime sodium.
100-3-medication-prescription-request1 | A prescription item (MedicationRequest) that is a part of a three-item-prescription (42-day treatment cycle). Generic. Thalidomide 50mgx4 once a day before bed for 42 days.
100-3-medication-prescription-request2 | A prescription item (MedicationRequest) that is a part of a three-item-prescription (42-day treatment cycle). Generic. Melphalan 2mgx4 once a day for 4 days in the beginning of cycle.
100-3-medication-prescription-request3 | A prescription item (MedicationRequest) that is a part of a three-item-prescription (42-day treatment cycle). Generic. Prednisone 50mgx3 once a day for 4 days in the beginning of cycle.
200-multiitem-prescription-without-orchestration | Multiitem prescription where items on the same prescription are not interdependent. Kept together by the same groupIdentifier.
300-dispense-for-2-requests | Medication dispense dispensing one combination product for two prescribed products (multiitem prescription)
PrescriptionLine1 | Prescription Line 1
PrescriptionLine2 | Prescription Line 2
PrescriptionLine3 | Prescription Line 3
PrescriptionLine4 | Prescription Line 4
PrescriptionLine5 | Prescription Line 5
PrescriptionLine6 | Prescription Line 6
PrescriptionLine7 | Prescription Line 7
PrescriptionLine8 | Prescription Line 8
PrescriptionLine9 | Prescription Line 9
doctor1 | Dr Meryl Ärztin - clinical oncologist
organization1 | An organization: clinic
organization2 | An organization: pharmacy
patient1 | A patient: Thomas, born 1950
patient2 | A patient: Emily, born 1990
pharmacist1 | Mr Moon Farmatseut - pharmacist
practitioner1 | Dr Meryl Ärztin
practitioner2 | Mr Moon Farmatseut