pub struct MedicationRequestInner {Show 74 fields
pub id: Option<String>,
pub meta: Option<Meta>,
pub implicit_rules: Option<String>,
pub language: Option<String>,
pub text: Option<Narrative>,
pub contained: Vec<Resource>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub identifier: Vec<Option<Identifier>>,
pub identifier_ext: Vec<Option<FieldExtension>>,
pub based_on: Vec<Option<Reference>>,
pub based_on_ext: Vec<Option<FieldExtension>>,
pub prior_prescription: Option<Reference>,
pub prior_prescription_ext: Option<FieldExtension>,
pub group_identifier: Option<Identifier>,
pub group_identifier_ext: Option<FieldExtension>,
pub status: MedicationRequestStatusCodes,
pub status_ext: Option<FieldExtension>,
pub status_reason: Option<CodeableConcept>,
pub status_reason_ext: Option<FieldExtension>,
pub status_changed: Option<DateTime>,
pub status_changed_ext: Option<FieldExtension>,
pub intent: MedicationRequestIntentCodes,
pub intent_ext: Option<FieldExtension>,
pub category: Vec<Option<CodeableConcept>>,
pub category_ext: Vec<Option<FieldExtension>>,
pub priority: Option<RequestPriority>,
pub priority_ext: Option<FieldExtension>,
pub do_not_perform: Option<bool>,
pub do_not_perform_ext: Option<FieldExtension>,
pub medication: CodeableReference,
pub medication_ext: Option<FieldExtension>,
pub subject: Reference,
pub subject_ext: Option<FieldExtension>,
pub information_source: Vec<Option<Reference>>,
pub information_source_ext: Vec<Option<FieldExtension>>,
pub encounter: Option<Reference>,
pub encounter_ext: Option<FieldExtension>,
pub supporting_information: Vec<Option<Reference>>,
pub supporting_information_ext: Vec<Option<FieldExtension>>,
pub authored_on: Option<DateTime>,
pub authored_on_ext: Option<FieldExtension>,
pub requester: Option<Reference>,
pub requester_ext: Option<FieldExtension>,
pub reported: Option<bool>,
pub reported_ext: Option<FieldExtension>,
pub performer_type: Option<CodeableConcept>,
pub performer_type_ext: Option<FieldExtension>,
pub performer: Vec<Option<Reference>>,
pub performer_ext: Vec<Option<FieldExtension>>,
pub device: Vec<Option<CodeableReference>>,
pub device_ext: Vec<Option<FieldExtension>>,
pub recorder: Option<Reference>,
pub recorder_ext: Option<FieldExtension>,
pub reason: Vec<Option<CodeableReference>>,
pub reason_ext: Vec<Option<FieldExtension>>,
pub course_of_therapy_type: Option<CodeableConcept>,
pub course_of_therapy_type_ext: Option<FieldExtension>,
pub insurance: Vec<Option<Reference>>,
pub insurance_ext: Vec<Option<FieldExtension>>,
pub note: Vec<Option<Annotation>>,
pub note_ext: Vec<Option<FieldExtension>>,
pub rendered_dosage_instruction: Option<String>,
pub rendered_dosage_instruction_ext: Option<FieldExtension>,
pub effective_dose_period: Option<Period>,
pub effective_dose_period_ext: Option<FieldExtension>,
pub dosage_instruction: Vec<Option<Dosage>>,
pub dosage_instruction_ext: Vec<Option<FieldExtension>>,
pub dispense_request: Option<MedicationRequestDispenseRequest>,
pub dispense_request_ext: Option<FieldExtension>,
pub substitution: Option<MedicationRequestSubstitution>,
pub substitution_ext: Option<FieldExtension>,
pub event_history: Vec<Option<Reference>>,
pub event_history_ext: Vec<Option<FieldExtension>>,
/* private fields */
}
Expand description
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.
MedicationRequest v5.0.0
Ordering of medication for patient or group
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.
Fields§
§id: Option<String>
Logical id of this artifact
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
meta: Option<Meta>
Metadata about the resource
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
implicit_rules: Option<String>
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
language: Option<String>
Language; Language of the resource content
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
text: Option<Narrative>
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it “clinically safe” for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a “text blob” or where text is additionally entered raw or narrated and encoded information is added later.
contained: Vec<Resource>
Contained, inline Resources
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
extension: Vec<Extension>
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
modifier_extension: Vec<Extension>
Extensions that cannot be ignored
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element’s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
identifier: Vec<Option<Identifier>>
External ids for this request
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.
This is a business identifier, not a resource identifier.
identifier_ext: Vec<Option<FieldExtension>>
Extension field.
based_on: Vec<Option<Reference>>
A plan or request that is fulfilled in whole or in part by this medication request
A plan or request that is fulfilled in whole or in part by this medication request.
based_on_ext: Vec<Option<FieldExtension>>
Extension field.
prior_prescription: Option<Reference>
Reference to an order/prescription that is being replaced by this MedicationRequest
Reference to an order/prescription that is being replaced by this MedicationRequest.
prior_prescription_ext: Option<FieldExtension>
Extension field.
group_identifier: Option<Identifier>
Composite request this is part of
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.
group_identifier_ext: Option<FieldExtension>
Extension field.
status: MedicationRequestStatusCodes
MedicationRequestStatus; active | on-hold | ended | stopped | completed | cancelled | entered-in-error | draft | unknown
A code specifying the current state of the order. Generally, this will be active or completed state.
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.
status_ext: Option<FieldExtension>
Extension field.
status_reason: Option<CodeableConcept>
MedicationRequestStatusReason; Reason for current status
Captures the reason for the current state of the MedicationRequest.
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.
status_reason_ext: Option<FieldExtension>
Extension field.
status_changed: Option<DateTime>
When the status was changed
The date (and perhaps time) when the status was changed.
status_changed_ext: Option<FieldExtension>
Extension field.
intent: MedicationRequestIntentCodes
MedicationRequestIntent; proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
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.
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.
intent_ext: Option<FieldExtension>
Extension field.
category: Vec<Option<CodeableConcept>>
MedicationRequestAdministrationLocation; Grouping or category of medication request
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.
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.
category_ext: Vec<Option<FieldExtension>>
Extension field.
priority: Option<RequestPriority>
MedicationRequestPriority; routine | urgent | asap | stat
Indicates how quickly the Medication Request should be addressed with respect to other requests.
priority_ext: Option<FieldExtension>
Extension field.
do_not_perform: Option<bool>
True if patient is to stop taking or not to start taking the medication
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.
If do not perform is not specified, the request is a positive request e.g. “do perform”.
do_not_perform_ext: Option<FieldExtension>
Extension field.
medication: CodeableReference
MedicationCode; Medication to be taken
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.
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.
medication_ext: Option<FieldExtension>
Extension field.
subject: Reference
Individual or group for whom the medication has been requested
The individual or group for whom the medication has been requested.
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.
subject_ext: Option<FieldExtension>
Extension field.
information_source: Vec<Option<Reference>>
The person or organization who provided the information about this request, if the source is someone other than the requestor
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.
information_source_ext: Vec<Option<FieldExtension>>
Extension field.
encounter: Option<Reference>
Encounter created as part of encounter/admission/stay
The Encounter during which this [x] was created or to which the creation of this record is tightly associated.
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.
encounter_ext: Option<FieldExtension>
Extension field.
supporting_information: Vec<Option<Reference>>
Information to support fulfilling of the medication
Information to support fulfilling (i.e. dispensing or administering) of the medication, for example, patient height and weight, a MedicationStatement for the patient).
This attribute can be used to reference a MedicationStatement about the patients’ medication use.
supporting_information_ext: Vec<Option<FieldExtension>>
Extension field.
When request was initially authored
The date (and perhaps time) when the prescription was initially written or authored on.
Extension field.
requester: Option<Reference>
Who/What requested the Request
The individual, organization, or device that initiated the request and has responsibility for its activation.
requester_ext: Option<FieldExtension>
Extension field.
reported: Option<bool>
Reported rather than primary record
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.
If not populated, then assume that this is the original record and not reported
reported_ext: Option<FieldExtension>
Extension field.
performer_type: Option<CodeableConcept>
MedicationRequestPerformerType; Desired kind of performer of the medication administration
Indicates the type of performer of the administration of the medication.
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.
performer_type_ext: Option<FieldExtension>
Extension field.
performer: Vec<Option<Reference>>
Intended performer of administration
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.
performer_ext: Vec<Option<FieldExtension>>
Extension field.
device: Vec<Option<CodeableReference>>
Intended type of device for the administration
The intended type of device that is to be used for the administration of the medication (for example, PCA Pump).
device_ext: Vec<Option<FieldExtension>>
Extension field.
recorder: Option<Reference>
Person who entered the request
The person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order.
recorder_ext: Option<FieldExtension>
Extension field.
reason: Vec<Option<CodeableReference>>
MedicationRequestReason; Reason or indication for ordering or not ordering the medication
The reason or the indication for ordering or not ordering the medication.
This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference.
reason_ext: Vec<Option<FieldExtension>>
Extension field.
course_of_therapy_type: Option<CodeableConcept>
MedicationRequestCourseOfTherapy; Overall pattern of medication administration
The description of the overall pattern of the administration of the medication to the patient.
This attribute should not be confused with the protocol of the medication.
course_of_therapy_type_ext: Option<FieldExtension>
Extension field.
insurance: Vec<Option<Reference>>
Associated insurance coverage
Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service.
insurance_ext: Vec<Option<FieldExtension>>
Extension field.
note: Vec<Option<Annotation>>
Information about the prescription
Extra information about the prescription that could not be conveyed by the other attributes.
note_ext: Vec<Option<FieldExtension>>
Extension field.
rendered_dosage_instruction: Option<String>
Full representation of the dosage instructions
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.
rendered_dosage_instruction_ext: Option<FieldExtension>
Extension field.
effective_dose_period: Option<Period>
Period over which the medication is to be taken
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.
effective_dose_period_ext: Option<FieldExtension>
Extension field.
dosage_instruction: Vec<Option<Dosage>>
Specific instructions for how the medication should be taken
Specific instructions for how the medication is to be used by the patient.
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.
dosage_instruction_ext: Vec<Option<FieldExtension>>
Extension field.
dispense_request: Option<MedicationRequestDispenseRequest>
Medication supply authorization
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.
dispense_request_ext: Option<FieldExtension>
Extension field.
substitution: Option<MedicationRequestSubstitution>
Any restrictions on medication substitution
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.
substitution_ext: Option<FieldExtension>
Extension field.
event_history: Vec<Option<Reference>>
A list of events of interest in the lifecycle
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.
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.).
event_history_ext: Vec<Option<FieldExtension>>
Extension field.
Trait Implementations§
Source§impl Clone for MedicationRequestInner
impl Clone for MedicationRequestInner
Source§fn clone(&self) -> MedicationRequestInner
fn clone(&self) -> MedicationRequestInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read more