An order for both supply of the medication and the instructions for administration of the medication to a patient. The resource is called "MedicationRequest" rather than "MedicationPrescription" or "MedicationOrder" to generalize the use across inpatient and outpatient settings as well as for care plans, etc and to harmonize with workflow patterns.

External identifier - one that would be used by another non-FHIR system - for example a re-imbursement system might issue its own id for each prescription that is created. This is particularly important where FHIR only provides part of an entire workflow process where records have to be tracked through an entire system.

Protocol or definition followed by this request.

Plan/proposal/order fulfilled by this request.

Composite request this is part of.

A code specifying the state of the order. Generally this will be active or completed state.

Whether the request is a proposal, plan, or an original order.

It is expected that the type of requester will be restricted for different stages of a MedicationRequest. For example, Proposals can be created by a patient, relatedPerson, Practitioner or Device. Plans can be created by Practitioners, Patients, RelatedPersons and Devices. Original orders can be created by a Practitioner only.

Identifies the medication being administered. This is a link to a resource that represents the medication which may be the details of the medication or simply an 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. Note: do not use Medication.name to describe the prescribed medication. When the only available information is a text description of the medication, Medication.code.text should be used.

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

The patient on a medicationRequest is mandatory. For the secondary use case where the actual patient is not provided, there still must be an anonymyzed patient specified.

A link to a resource that identifies the particular occurrence or set oc occurences of contact between patient and health care provider.

SubstanceAdministration->component->EncounterEvent.

Include additional information (for example, patient height and weight) that supports the ordering of the medication.

The date (and perhaps time) when the prescription was initially written.

The healthcare professional responsible for authorizing the initial prescription.

It is expected that the type of requester will be restricted for different stages of a MedicationRequest. For example, Proposals can be created by a patient, relatedPerson, Practitioner or Device. Plans can be created by Practitioners, Patients, RelatedPersons and Devices. Original orders can be created by a Practitioner only.

Can be the reason or the indication for writing the prescription.

This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference.

Condition or observation that supports why the prescription is being written.

This is a reference to a condition that is the reason for the medication order. If only a code exists, use reasonCode.

Extra information about the prescription that could not be conveyed by the other attributes.

Indicates where type of medication order and where the medication is expected to be consumed or administered.

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

Indicates the specific details for the dispense or medication supply part of a medication order (also known as a Medication Prescription). Note that this information is NOT always sent with the order. There may be in some settings (e.g. hospitals) institutional or system support for completing the dispense details in the pharmacy department.

This indicates the validity period of a prescription (stale dating the Prescription).

Indicates when the Prescription becomes valid, and when it ceases to be a dispensable Prescription.

It reflects the prescriber perspective for the validity of the prescription. Dispenses must not be made against the prescription outside of this period. The lower-bound of the Dispensing Window signifies the earliest date that the prescription can be filled for the first time. If an upper-bound is not specified then the Prescription is open-ended or will default to a stale-date based on regulations.

An integer indicating the number of times, in addition to the original dispense, (aka refills or repeats) that the patient can receive the prescribed medication. Usage Notes: This integer does NOT include the original order dispense. This means that if an order indicates dispense 30 tablets plus "3 repeats", then the order can be dispensed a total of 4 times and the patient can receive a total of 120 tablets.

If displaying "number of authorized fills", add 1 to this number.

The amount that is to be dispensed for one fill.

Identifies the period time over which the supplied product is expected to be used, or the length of time the dispense is expected to last.

In some situations, this attribute may be used instead of quantity to identify the amount supplied by how long it is expected to last, rather than the physical quantity issued, e.g. 90 days supply of medication (based on an ordered dosage) When possible, it is always better to specify quantity, as this tends to be more precise. expectedSupplyDuration will always be an estimate that can be influenced by external factors.

Indicates the intended dispensing Organization specified by the prescriber.

Indicates whether or not substitution can or should be part of the dispense. In some cases substitution must happen, in other cases substitution must not happen, and in others it does not matter. This block explains the prescriber's intent. If nothing is specified substitution may be done.

True if the prescriber allows a different drug to be dispensed from what was prescribed.

Indicates the reason for the substitution, or why substitution must or must not be performed.

A link to a resource representing an earlier order related order or prescription.

A summary of the events of interest that have occurred as the request is processed; e.g. when the order was verified or when it was completed.

See usage notes in Request pattern in request history.