FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

Pharmacy icon Work GroupMaturity Level: 4 Trial UseSecurity Category: Patient Compartments: Encounter, Patient, Practitioner

Detailed Descriptions for the elements in the MedicationRequest resource.

MedicationRequest
Element Id MedicationRequest
Definition

An order or request 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, including care plans, etc., and to harmonize with workflow patterns.

Short Display Ordering of medication for patient or group
Cardinality 0..*
Type DomainResource
Alternate Names Prescription; Order
Summary false
MedicationRequest.identifier
Element Id MedicationRequest.identifier
Definition

Identifiers associated with this medication request that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server.

Short Display External ids for this request
Note This is a business identifier, not a resource identifier (see discussion)
Cardinality 0..*
Type Identifier
Summary false
Comments

This is a business identifier, not a resource identifier.

MedicationRequest.basedOn
Element Id MedicationRequest.basedOn
Definition

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

Short Display A plan or request that is fulfilled in whole or in part by this medication request
Cardinality 0..*
Type Reference(CarePlan | MedicationRequest | ServiceRequest | ImmunizationRecommendation | RequestOrchestration)
Summary true
MedicationRequest.priorPrescription
Element Id MedicationRequest.priorPrescription
Definition

Reference to an order/prescription that is being replaced by this MedicationRequest.

Short Display Reference to an order/prescription that is being replaced by this MedicationRequest
Cardinality 0..1
Type Reference(MedicationRequest)
Summary false
MedicationRequest.groupIdentifier
Element Id MedicationRequest.groupIdentifier
Definition

A shared identifier common to multiple independent Request instances that were activated/authorized more or less simultaneously by a single author. The presence of the same identifier on each request ties those requests together and may have business ramifications in terms of reporting of results, billing, etc. E.g. a requisition number shared by a set of lab tests ordered together, or a prescription number shared by all meds ordered at one time.

Short Display Composite request this is part of
Cardinality 0..1
Type Identifier
Requirements

Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.

Summary true
MedicationRequest.status
Element Id MedicationRequest.status
Definition

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

Short Display active | on-hold | ended | stopped | completed | cancelled | entered-in-error | draft | unknown
Cardinality 1..1
Terminology Binding medicationrequest Status (Required)
Type code
Is Modifier true (Reason: This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid)
Summary true
Comments

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

Clinical decision support systems should take the status into account when determining which medications to include in their algorithms.

MedicationRequest.statusReason
Element Id MedicationRequest.statusReason
Definition

Captures the reason for the current state of the MedicationRequest.

Short Display Reason for current status
Cardinality 0..1
Terminology Binding medicationRequest Status Reason Codes (Example)
Type CodeableConcept
Summary false
Comments

This is generally only used for "exception" statuses such as "suspended" or "cancelled". The reason why the MedicationRequest was created at all is captured in reasonCode, not here.

MedicationRequest.statusChanged
Element Id MedicationRequest.statusChanged
Definition

The date (and perhaps time) when the status was changed.

Short Display When the status was changed
Cardinality 0..1
Type dateTime
Summary false
MedicationRequest.intent
Element Id MedicationRequest.intent
Definition

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

Short Display proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Cardinality 1..1
Terminology Binding medicationRequest Intent (Required)
Type code
Is Modifier true (Reason: This element changes the interpretation of all descriptive attributes. For example "the time the request is recommended to occur" vs. "the time the request is authorized to occur" or "who is recommended to perform the request" vs. "who is authorized to perform the request)
Summary true
Comments

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.

An instance-order is an instantiation of a request or order and may be used to populate Medication Administration Record.

This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.

MedicationRequest.category
Element Id MedicationRequest.category
Definition

An arbitrary categorization or grouping of the medication request. It could be used for indicating where meds are intended to be administered, eg. in an inpatient setting or in a patient's home, or a legal category of the medication.

Short Display Grouping or category of medication request
Cardinality 0..*
Terminology Binding medicationRequest Administration Location Codes (Example)
Type CodeableConcept
Summary false
Comments

The category can be used to include where the medication is expected to be consumed or other types of requests. The examplar value set represents where the meds are intended to be administered and is just one example of request categorization.

MedicationRequest.priority
Element Id MedicationRequest.priority
Definition

Indicates how quickly the Medication Request should be addressed with respect to other requests.

Short Display routine | urgent | asap | stat
Cardinality 0..1
Terminology Binding RequestPriority (Required)
Type code
Summary true
MedicationRequest.doNotPerform
Element Id MedicationRequest.doNotPerform
Definition

If true, indicates that the provider is asking for the patient to either stop taking or to not start taking the specified medication. For example, the patient is taking an existing medication and the provider is changing their medication. They want to create two seperate requests: one to stop using the current medication and another to start the new medication.

Short Display True if patient is to stop taking or not to start taking the medication
Cardinality 0..1
Type boolean
Is Modifier true (Reason: This element is labeled as a modifier because this element negates the request to occur (ie, this is a request for the medication not to be ordered or prescribed, etc.))
Summary true
Comments

If do not perform is not specified, the request is a positive request e.g. "do perform".

MedicationRequest.medication
Element Id MedicationRequest.medication
Definition

Identifies the medication being requested. 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.

Short Display Medication to be taken
Cardinality 1..1
Terminology Binding SNOMED CT Medication Codes (Example)
Type CodeableReference(Medication)
Summary true
Comments

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. For example, if you require form or lot number or if the medication is compounded or extemporaneously prepared, then you must reference the Medication resource.

MedicationRequest.subject
Element Id MedicationRequest.subject
Definition

The individual or group for whom the medication has been requested.

Short Display Individual or group for whom the medication has been requested
Cardinality 1..1
Type Reference(Patient | Group)
Summary true
Comments

The subject on a medication request is mandatory. For the secondary use case where the actual subject is not provided, there still must be an anonymized subject specified.

MedicationRequest.informationSource
Element Id MedicationRequest.informationSource
Definition

The person or organization who provided the information about this request, if the source is someone other than the requestor. This is often used when the MedicationRequest is reported by another person.

Short Display The person or organization who provided the information about this request, if the source is someone other than the requestor
Cardinality 0..*
Type Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization)
Summary false
MedicationRequest.encounter
Element Id MedicationRequest.encounter
Definition

The Encounter during which this [x] was created or to which the creation of this record is tightly associated.

Short Display Encounter created as part of encounter/admission/stay
Cardinality 0..1
Type Reference(Encounter)
Summary false
Comments

This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter." If there is a need to link to episodes of care they will be handled with an extension.

MedicationRequest.supportingInformation
Element Id MedicationRequest.supportingInformation
Definition

Information to support fulfilling (i.e. dispensing or administering) of the medication, for example, patient height and weight, a MedicationStatement for the patient).

Short Display Information to support fulfilling of the medication
Cardinality 0..*
Type Reference(Any)
Summary false
Comments

This attribute can be used to reference a MedicationStatement about the patients' medication use.

MedicationRequest.authoredOn
Element Id MedicationRequest.authoredOn
Definition

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

Short Display When request was initially authored
Cardinality 0..1
Type dateTime
Summary true
MedicationRequest.requester
Element Id MedicationRequest.requester
Definition

The individual, organization, or device that initiated the request and has responsibility for its activation.

Short Display Who/What requested the Request
Cardinality 0..1
Type Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)
Summary true
MedicationRequest.reported
Element Id MedicationRequest.reported
Definition

Indicates if this record was captured as a secondary 'reported' record rather than as an original primary source-of-truth record. It may also indicate the source of the report.

Short Display Reported rather than primary record
Cardinality 0..1
Type boolean
Summary true
Comments

If not populated, then assume that this is the original record and not reported

MedicationRequest.performerType
Element Id MedicationRequest.performerType
Definition

Indicates the type of performer of the administration of the medication.

Short Display Desired kind of performer of the medication administration
Cardinality 0..1
Terminology Binding Medication Intended Performer Role (Extensible)
Type CodeableConcept
Summary true
Comments

If specified without indicating a performer, this indicates that the performer must be of the specified type. If specified with a performer then it indicates the requirements of the performer if the designated performer is not available.

MedicationRequest.performer
Element Id MedicationRequest.performer
Definition

The specified desired performer of the medication treatment (e.g. the performer of the medication administration). For devices, this is the device that is intended to perform the administration of the medication. An IV Pump would be an example of a device that is performing the administration. Both the IV Pump and the practitioner that set the rate or bolus on the pump can be listed as performers.

Short Display Intended performer of administration
Cardinality 0..*
Type Reference(Practitioner | PractitionerRole | Organization | Patient | DeviceDefinition | RelatedPerson | CareTeam | HealthcareService)
Summary false
MedicationRequest.device
Element Id MedicationRequest.device
Definition

The intended type of device that is to be used for the administration of the medication (for example, PCA Pump).

Short Display Intended type of device for the administration
Cardinality 0..*
Type CodeableReference(DeviceDefinition)
Summary false
MedicationRequest.recorder
Element Id MedicationRequest.recorder
Definition

The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.

Short Display Person who entered the request
Cardinality 0..1
Type Reference(Practitioner | PractitionerRole)
Summary false
MedicationRequest.reason
Element Id MedicationRequest.reason
Definition

The reason or the indication for ordering or not ordering the medication.

Short Display Reason or indication for ordering or not ordering the medication
Cardinality 0..*
Terminology Binding Condition/Problem/Diagnosis Codes (Example)
Type CodeableReference(Condition | Observation | DiagnosticReport | Procedure)
Summary false
Comments

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

MedicationRequest.courseOfTherapyType
Element Id MedicationRequest.courseOfTherapyType
Definition

The description of the overall pattern of the administration of the medication to the patient.

Short Display Overall pattern of medication administration
Cardinality 0..1
Terminology Binding medicationRequest Course of Therapy Codes (Extensible)
Type CodeableConcept
Summary false
Comments

This attribute should not be confused with the protocol of the medication.

MedicationRequest.insurance
Element Id MedicationRequest.insurance
Definition

Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service.

Short Display Associated insurance coverage
Cardinality 0..*
Type Reference(Coverage | ClaimResponse)
Summary false
MedicationRequest.note
Element Id MedicationRequest.note
Definition

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

Short Display Information about the prescription
Cardinality 0..*
Type Annotation
Summary false
MedicationRequest.renderedDosageInstruction
Element Id MedicationRequest.renderedDosageInstruction
Definition

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.

Short Display Full representation of the dosage instructions
Cardinality 0..1
Type markdown
Requirements

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

Summary false
MedicationRequest.effectiveDosePeriod
Element Id MedicationRequest.effectiveDosePeriod
Definition

The period over which the medication is to be taken. Where there are multiple dosageInstruction lines (for example, tapering doses), this is the earliest date and the latest end date of the dosageInstructions.

Short Display Period over which the medication is to be taken
Cardinality 0..1
Type Period
Summary false
MedicationRequest.dosageInstruction
Element Id MedicationRequest.dosageInstruction
Definition

Specific instructions for how the medication is to be used by the patient.

Short Display Specific instructions for how the medication should be taken
Cardinality 0..*
Type Dosage
Summary false
Comments

There are examples where a medication request may include the option of an oral dose or an Intravenous or Intramuscular dose. For example, "Ondansetron 8mg orally or IV twice a day as needed for nausea" or "Compazine® (prochlorperazine) 5-10mg PO or 25mg PR bid prn nausea or vomiting". In these cases, two medication requests would be created that could be grouped together. The decision on which dose and route of administration to use is based on the patient's condition at the time the dose is needed. In general, each prescribed drug will be a separate Medication Request.

When drug orders are grouped together at the time of order entry, but each of the drugs can be manipulated independently e.g. changing the status of one order to "completed" or "cancelled", changing another order status to "on-hold", the method to "group" all of the medication requests together is to use MedicationRequest.groupIdentifier element. All of the orders grouped together in this manner will have the same groupIdentifier, and separately, each order in the group may have a unique identifier.

There are cases that require grouping of Medication orders together when it is necessary to specify optionality e.g. order two drugs at one time, but stating either of these drugs may be used to treat the patient. The use of a RequestOrchestration should be used as a parent for the Medication orders that require this type of grouping. An example when it may be necessary to group medication orders together is when you specify timing relationships e.g. order drug "xyz" with dose 123, then taper the same drug to a different dose after some interval of time precedence: e.g. give drug "abc" followed by drug "def" e.g. give drug 30 minutes before some procedure was performed more generically this supports - hierarchical groups of actions, where each specific action references the action to be performed (in terms of a Request resource), and each group describes additional behavior, relationships, and applicable conditions between the actions in the overall group. Note that one should NOT use the List or Composition resource to accomplish the above requirements. You may use List or Composition for other business requirements, but not to address the specific requirements of grouping medication orders.

MedicationRequest.dispenseRequest
Element Id MedicationRequest.dispenseRequest
Definition

Indicates the specific details for the dispense or medication supply part of a medication request (also known as a Medication Prescription or Medication Order). 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.

Short Display Medication supply authorization
Cardinality 0..1
Summary false
MedicationRequest.dispenseRequest.initialFill
Element Id MedicationRequest.dispenseRequest.initialFill
Definition

Indicates the quantity or duration for the first dispense of the medication.

Short Display First fill details
Cardinality 0..1
Summary false
Comments

If populating this element, either the quantity or the duration must be included.

MedicationRequest.dispenseRequest.initialFill.quantity
Element Id MedicationRequest.dispenseRequest.initialFill.quantity
Definition

The amount or quantity to provide as part of the first dispense.

Short Display First fill quantity
Cardinality 0..1
Type SimpleQuantity
Summary false
MedicationRequest.dispenseRequest.initialFill.duration
Element Id MedicationRequest.dispenseRequest.initialFill.duration
Definition

The length of time that the first dispense is expected to last.

Short Display First fill duration
Cardinality 0..1
Type Duration
Summary false
MedicationRequest.dispenseRequest.dispenseInterval
Element Id MedicationRequest.dispenseRequest.dispenseInterval
Definition

The minimum period of time that must occur between dispenses of the medication.

Short Display Minimum period of time between dispenses
Cardinality 0..1
Type Duration
Summary false
MedicationRequest.dispenseRequest.validityPeriod
Element Id MedicationRequest.dispenseRequest.validityPeriod
Definition

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

Short Display Time period supply is authorized for
Cardinality 0..1
Type Period
Requirements

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

Summary false
Comments

It reflects the prescribers' 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.

MedicationRequest.dispenseRequest.numberOfRepeatsAllowed
Element Id MedicationRequest.dispenseRequest.numberOfRepeatsAllowed
Definition

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. A prescriber may explicitly say that zero refills are permitted after the initial dispense.

Short Display Number of refills authorized
Cardinality 0..1
Type unsignedInt
Summary false
Comments

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

MedicationRequest.dispenseRequest.quantity
Element Id MedicationRequest.dispenseRequest.quantity
Definition

The amount that is to be dispensed for one fill.

Short Display Amount of medication to supply per dispense
Cardinality 0..1
Type SimpleQuantity
Summary false
MedicationRequest.dispenseRequest.expectedSupplyDuration
Element Id MedicationRequest.dispenseRequest.expectedSupplyDuration
Definition

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.

Short Display Number of days supply per dispense
Cardinality 0..1
Type Duration
Summary false
Comments

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.

MedicationRequest.dispenseRequest.dispenser
Element Id MedicationRequest.dispenseRequest.dispenser
Definition

Indicates the intended performing Organization that will dispense the medication as specified by the prescriber.

Short Display Intended performer of dispense
Cardinality 0..1
Type Reference(Organization)
Summary false
MedicationRequest.dispenseRequest.dispenserInstruction
Element Id MedicationRequest.dispenseRequest.dispenserInstruction
Definition

Provides additional information to the dispenser, for example, counselling to be provided to the patient.

Short Display Additional information for the dispenser
Cardinality 0..*
Type Annotation
Summary false
MedicationRequest.dispenseRequest.doseAdministrationAid
Element Id MedicationRequest.dispenseRequest.doseAdministrationAid
Definition

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

Short Display Type of adherence packaging to use for the dispense
Cardinality 0..1
Terminology Binding Medication Dose Aids (Example)
Type CodeableConcept
Summary false
MedicationRequest.substitution
Element Id MedicationRequest.substitution
Definition

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. This block explains the prescriber's intent. If nothing is specified substitution may be done.

Short Display Any restrictions on medication substitution
Cardinality 0..1
Summary false
MedicationRequest.substitution.allowed[x]
Element Id MedicationRequest.substitution.allowed[x]
Definition

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

Short Display Whether substitution is allowed or not
Cardinality 1..1
Terminology Binding ActSubstanceAdminSubstitutionCode icon (Preferred)
Type boolean|CodeableConcept
[x] Note See Choice of Datatypes for further information about how to use [x]
Summary false
Comments

This element is labeled as a modifier because whether substitution is allow or not, it cannot be ignored.

MedicationRequest.substitution.reason
Element Id MedicationRequest.substitution.reason
Definition

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

Short Display Why should (not) substitution be made
Cardinality 0..1
Terminology Binding SubstanceAdminSubstitutionReason icon (Example)
Type CodeableConcept
Summary false
MedicationRequest.eventHistory
Element Id MedicationRequest.eventHistory
Definition

Links to Provenance records for past versions of this resource or fulfilling request or event resources that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the resource.

Short Display A list of events of interest in the lifecycle
Cardinality 0..*
Type Reference(Provenance)
Summary false
Comments

This 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.).