Indicates that a medication product is to be or has been dispensed for a named person/patient. This includes a description of the medication product (supply) provided and the instructions for administering the medication. The medication dispense is the result of a pharmacy system responding to a medication order.

Identifier assigned Identifiers associated with this Medication Dispense that are defined by business processes and/or used to refer to it when a direct URL reference to the dispensing facility - this resource itself is an identifier not appropriate. They are business identifiers assigned outside FHIR. to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server.

This is a business identifier, not a resource identifier.

A plan that is fulfilled in whole or in part by this MedicationDispense.

The procedure or medication administration that triggered the dispense.

While both a procedure and a medication administration may have triggered the dispense, but it is not expected that multiple procedures and/or multiple medication administrations would be triggers.

A code specifying the state of the set of dispense events.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

Indicates the reason why a dispense was not performed.

The date (and maybe time) when the status of the dispense record changed.

Indicates the type of medication dispense and (for example, drug classification like ATC, where the medication is expected to meds would be consumed or administered. administered, legal category of the medication.).

The category can be used to include where the medication is expected to be consumed or other types of dispenses. Invariants can be used to bind to different value sets when profiling to bind.

The committee will revisit these codes, expecting to use a codesystem from terminology.hl7.org .

Identifies the medication being administered. supplied (or intended to be supplied). This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications.

If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the medication resource is recommended.  recommended. For example if you require form or lot example, if you require form or lot number, then you must reference must reference the Medication resource. . resource.

A link to a resource representing the person or the group to whom the medication will be given.

SubstanceAdministration->subject->Patient.

The encounter or episode of care that establishes the context for this event.

Additional information that supports the medication being dispensed. For example, there may be requirements that a specific lab test has been completed prior to dispensing or the patient's weight at the time of dispensing is documented.

Indicates who or what performed the event. It should be assumed that the performer is

Distinguishes the dispenser type of performer in the medication. dispense. For example, date enterer, packager, final checker.

The performer will be reviewed as part Allows disambiguation of STU4. the types of involvement of different performers.

The device, practitioner, etc. who performed the action. It should be assumed that the actor is the dispenser of the medication.

The different performer functions within a dispense process can vary - and some of these functions may be restricted to clinical professionals - such distinction is usually specific to a jurisdiction and context. While performer.function and performer.actor don't add restrictions on which resources can be referenced, this element is expected to be used according to the local restrictions, for example not allowing Group (e.g., household) or RelatedPerson to be the dispenser.

The organization principal physical location where the device or practitioner dispense was acting on behalf of. performed.

Indicates the medication order that is being dispensed against.

Maps to basedOn in Event logical model.

Indicates the type of dispensing event that is performed. For example, Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc.

The amount of medication that has been (or was intended to be) dispensed. Includes unit of measure.

The amount of medication expressed as a timing amount.

Represents the known number of the fill over the entire lifetime of the prescription, i.e. if this is the first dispense by this pharmacy but the third fill overall, then the fillNumber will be 3. Each fill number represents one dispensation, even if that dispensation is not for the full quantity. Partial fills are not represented by decimal quantities, i.e., a partial fill of 40 tablets (full quantity is 100 tablets) adds 1 to the prior fill number, not 0.4. This means that the 'fillNumber' may sometimes be higher than the MedicationRequest.numberOfRepeatsAllowed, as the latter assumes full fills, while fillNumber does not.

This element may be inaccurate as it relies on the dispensing pharmacy to be aware of all fills that have occurred for the request.

The date the occurrence of the MedicationDispense was first captured in the system.

The time when the dispensed product was packaged and reviewed.

The time the dispensed product was provided to the patient or their representative.

Identification of the facility/location where the medication was was/will be shipped to, as part of the dispense event.

Identifies the person who picked up the medication. medication or the location or organization where the medication was delivered. This will usually be a patient or their caregiver, but some cases exist where it can be a healthcare professional. professional or a location, or organization.

Extra information about the dispense that could not be conveyed in the other attributes.

The full representation of the dose of the medication included in all dosage instructions. To be used when multiple dosage instructions are included to represent complex dosing such as increasing or tapering doses.

The content of the renderedDosageInstructions must not be different than the dose represented in the dosageInstruction content.

Indicates how the medication is to be used by the patient.

When the dose or rate is intended to change over the entire administration period (e.g. Tapering dose prescriptions), multiple instances of dosage instructions will need to be supplied to convey the different doses/rates. The pharmacist reviews the medication order prior to dispense and updates the dosageInstruction based on the actual product being dispensed.

Provides information about the type of adherence packaging supplied for the medication dispense.

When the dose or rate is intended to change over the entire administration period (e.g. Tapering dose prescriptions), multiple instances of dosage instructions will need to be supplied to convey the different doses/rates. The pharmacist reviews the medication order prior to dispense and updates the dosageInstruction based on the actual product being dispensed.

Indicates whether or not substitution was made as part of the dispense. In some cases cases, substitution will be expected but does not happen, in other cases substitution is not expected but does happen. This block explains what substitution did or did not happen and why. If nothing is specified, substitution was not done.

True if the dispenser dispensed a different drug or product from what was prescribed.

A code signifying whether a different drug was dispensed from what was prescribed.

Indicates the reason for the substitution of (or lack of substitution) from what was prescribed.

The person or organization that has primary responsibility for the substitution.

A summary of the events of interest that have occurred, such as when the dispense was verified.

This may might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.).