MedicationRequest
Overview
Profile (MedicationRequest) An order or request for both supply of the medication and the instructions for administration of the medication to a patient.
Canonical url - http://roche.com/fhir/iop/StructureDefinition/MedicationRequest
The below overview shows the elements of the resource, data type and the cardinality of each. Further details like "Binding"/"Fixed values"/"contraints" etc can be found on clicking on each element.
Structure definition :
MedicationRequest | I | MedicationRequest | There are no (further) constraints on this element Element idMedicationRequest Ordering of medication for patient or group Alternate namesPrescription, Order DefinitionAn 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.
| |
id | Σ | 0..1 | id | There are no (further) constraints on this element Element idMedicationRequest.id Logical id of this artifact DefinitionThe 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 | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idMedicationRequest.meta Metadata about the resource DefinitionThe 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.
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idMedicationRequest.implicitRules A set of rules under which this content was created DefinitionA 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 | 0..1 | codeBinding | There are no (further) constraints on this element Element idMedicationRequest.language Language of the resource content DefinitionThe 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). IETF language tag for a human language
| |
text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idMedicationRequest.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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 | I | 0..* | Resource | There are no (further) constraints on this element Element idMedicationRequest.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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 | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationRequest.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationRequest.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
identifier | I | 0..0 | Identifier | There are no (further) constraints on this element Element idMedicationRequest.identifier External ids for this request DefinitionIdentifiers 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.
|
basedOn | Σ I | 0..0 | Reference(CarePlan | MedicationRequest | ServiceRequest | ImmunizationRecommendation) | There are no (further) constraints on this element Element idMedicationRequest.basedOn A plan or request that is fulfilled in whole or in part by this medication request DefinitionA plan or request that is fulfilled in whole or in part by this medication request. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(CarePlan | MedicationRequest | ServiceRequest | ImmunizationRecommendation) Constraints
|
priorPrescription | I | 0..0 | Reference(MedicationRequest) | There are no (further) constraints on this element Element idMedicationRequest.priorPrescription Reference to an order/prescription that is being replaced by this MedicationRequest DefinitionReference to an order/prescription that is being replaced by this MedicationRequest. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
groupIdentifier | Σ I | 0..0 | Identifier | There are no (further) constraints on this element Element idMedicationRequest.groupIdentifier Composite request this is part of DefinitionA 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. 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. The rules of the identifier.type determine if a check digit is part of the ID value or sent separately, such as through the checkDigit extension.
|
status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idMedicationRequest.status active | on-hold | ended | stopped | completed | cancelled | entered-in-error | draft | unknown DefinitionA 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. A coded concept specifying the state of the prescribing event. Describes the lifecycle of the prescription.
|
statusReason | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idMedicationRequest.statusReason Reason for current status DefinitionCaptures 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. Identifies the reasons for a given status.
| |
statusChanged | 0..0 | dateTime | There are no (further) constraints on this element Element idMedicationRequest.statusChanged When the status was changed DefinitionThe date (and perhaps time) when the status was changed. UTC offset is allowed for dates and partial dates
| |
intent | Σ ?! | 1..1 | codeBinding | Element idMedicationRequest.intent proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option DefinitionWhether 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. The kind of medication order.
|
category | 0..0 | CodeableConcept | There are no (further) constraints on this element Element idMedicationRequest.category Grouping or category of medication request DefinitionAn 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. A coded concept identifying where the medication is to be consumed or administered.
| |
priority | Σ | 0..0 | codeBinding | There are no (further) constraints on this element Element idMedicationRequest.priority routine | urgent | asap | stat DefinitionIndicates how quickly the Medication Request should be addressed with respect to other requests. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size Identifies the level of importance to be assigned to actioning the request.
|
doNotPerform | Σ ?! | 0..0 | boolean | There are no (further) constraints on this element Element idMedicationRequest.doNotPerform True if patient is to stop taking or not to start taking the medication DefinitionIf 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".
|
medication | Σ | 1..1 | CodeableReference(Medication) | There are no (further) constraints on this element Element idMedicationRequest.medication Medication to be taken DefinitionIdentifies 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. A coded concept identifying substance or product that can be ordered.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationRequest.medication.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationRequest.medication.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
concept | Σ | 0..1 | CodeableConceptBinding | Element idMedicationRequest.medication.concept Reference to a concept (by class) DefinitionA reference to a concept - e.g. the information is identified by its general class to the degree of precision found in the terminology. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
|
reference | Σ I | 0..1 | Reference() | There are no (further) constraints on this element Element idMedicationRequest.medication.reference Reference to a resource (by instance) DefinitionA reference to a resource the provides exact details about the information being referenced. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
subject | Σ I | 1..1 | Reference(Patient | Group) | There are no (further) constraints on this element Element idMedicationRequest.subject Individual or group for whom the medication has been requested DefinitionThe 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.
|
informationSource | I | 0..0 | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) | There are no (further) constraints on this element Element idMedicationRequest.informationSource The person or organization who provided the information about this request, if the source is someone other than the requestor DefinitionThe 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Organization) Constraints
|
encounter | I | 0..0 | Reference(Encounter) | There are no (further) constraints on this element Element idMedicationRequest.encounter Encounter created as part of encounter/admission/stay DefinitionThe 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.
|
supportingInformation | I | 0..0 | Reference(Resource) | There are no (further) constraints on this element Element idMedicationRequest.supportingInformation Information to support fulfilling of the medication DefinitionInformation 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.
|
authoredOn | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idMedicationRequest.authoredOn When request was initially authored DefinitionThe date (and perhaps time) when the prescription was initially written or authored on. UTC offset is allowed for dates and partial dates
|
requester | Σ I | 0..0 | Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device) | There are no (further) constraints on this element Element idMedicationRequest.requester Who/What requested the Request DefinitionThe individual, organization, or device that initiated the request and has responsibility for its activation. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device) Constraints
|
reported | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idMedicationRequest.reported Reported rather than primary record DefinitionIndicates 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
|
performerType | Σ | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idMedicationRequest.performerType Desired kind of performer of the medication administration DefinitionIndicates 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. Identifies the type of individual that is desired to administer the medication.
|
performer | I | 0..* | Reference(Practitioner | PractitionerRole | Organization | Patient | DeviceDefinition | RelatedPerson | CareTeam | HealthcareService | Device) | Element idMedicationRequest.performer Intended performer of administration DefinitionThe 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. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole | Organization | Patient | DeviceDefinition | RelatedPerson | CareTeam | HealthcareService | Device) Constraints
|
device | 0..0 | CodeableReference(DeviceDefinition) | There are no (further) constraints on this element Element idMedicationRequest.device Intended type of device for the administration DefinitionThe intended type of device that is to be used for the administration of the medication (for example, PCA Pump). CodeableReference(DeviceDefinition) Constraints
| |
recorder | I | 0..0 | Reference(Practitioner | PractitionerRole) | There are no (further) constraints on this element Element idMedicationRequest.recorder Person who entered the request DefinitionThe person who entered the order on behalf of another individual for example in the case of a verbal or a telephone order. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Practitioner | PractitionerRole) Constraints
|
reason | 0..0 | CodeableReference(Condition | Observation) | There are no (further) constraints on this element Element idMedicationRequest.reason Reason or indication for ordering or not ordering the medication DefinitionThe 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. CodeableReference(Condition | Observation) BindingA coded concept indicating why the medication was ordered.
| |
courseOfTherapyType | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idMedicationRequest.courseOfTherapyType Overall pattern of medication administration DefinitionThe 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. Identifies the overall pattern of medication administratio.
| |
insurance | I | 0..0 | Reference(Coverage | ClaimResponse) | There are no (further) constraints on this element Element idMedicationRequest.insurance Associated insurance coverage DefinitionInsurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be required for delivering the requested service. References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Coverage | ClaimResponse) Constraints
|
note | 0..0 | Annotation | There are no (further) constraints on this element Element idMedicationRequest.note Information about the prescription DefinitionExtra information about the prescription that could not be conveyed by the other attributes. For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
renderedDosageInstruction | 0..0 | markdown | There are no (further) constraints on this element Element idMedicationRequest.renderedDosageInstruction Full representation of the dosage instructions DefinitionThe 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. Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/
| |
effectiveDosePeriod | I | 0..0 | Period | There are no (further) constraints on this element Element idMedicationRequest.effectiveDosePeriod Period over which the medication is to be taken DefinitionThe 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. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
dosageInstruction | I | 0..* | Dosage | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction Specific instructions for how the medication should be taken DefinitionSpecific 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.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
sequence | Σ | 0..1 | integer | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.sequence The order of the dosage instructions DefinitionIndicates the order in which the dosage instructions should be applied or interpreted. If the sequence number of multiple Dosages is the same, then it is implied that the instructions are to be treated as concurrent. If the sequence number is different, then the Dosages are intended to be sequential. 32 bit number; for values larger than this, use decimal
|
text | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.text Free text dosage instructions e.g. SIG DefinitionFree text dosage instructions e.g. SIG. Free text dosage instructions can be used for cases where the instructions are too complex to code. The content of this attribute does not include the name or description of the medication. When coded instructions are present, the free text instructions may still be present for display to humans taking or administering the medication. It is expected that the text instructions will always be populated. If the dosage.timing attribute is also populated, then the dosage.text should reflect the same information as the timing. Additional information about administration or preparation of the medication should be included as text. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size
|
additionalInstruction | Σ | 0..* | CodeableConceptBinding | Element idMedicationRequest.dosageInstruction.additionalInstruction Supplemental instruction or warnings to the patient - e.g. "with meals", "may cause drowsiness" DefinitionSupplemental instructions to the patient on how to take the medication (e.g. "with meals" or"take half to one hour before food") or warnings for the patient about the medication (e.g. "may cause drowsiness" or "avoid exposure of skin to direct sunlight or sunlamps"). Additional instruction is intended to be coded, but where no code exists, the element could include text. For example, "Swallow with plenty of water" which might or might not be coded. Information about administration or preparation of the medication (e.g. "infuse as rapidly as possibly via intraperitoneal port" or take "immediately following drug x") should be populated in dosage.text. A coded concept identifying additional instructions such as "take with water" or "avoid operating heavy machinery".
|
patientInstruction | Σ | 0..1 | string | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.patientInstruction Patient or consumer oriented instructions DefinitionInstructions in terms that are understood by the patient or consumer. Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size
|
timing | Σ | 0..1 | Timing | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.timing When medication should be administered DefinitionWhen medication should be administered. The timing schedule for giving the medication to the patient. This data type allows many different expressions. For example: "Every 8 hours"; "Three times a day"; "1/2 an hour before breakfast for 10 days from 23-Dec 2011:"; "15 Oct 2013, 17 Oct 2013 and 1 Nov 2013". Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period. This attribute might not always be populated while the Dosage.text is expected to be populated. If both are populated, then the Dosage.text should reflect the content of the Dosage.timing.
|
asNeeded | Σ I | 0..1 | boolean | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.asNeeded Take "as needed" DefinitionIndicates whether the Medication is only taken when needed within a specific dosing schedule (Boolean option). Can express "as needed" without a reason by setting the Boolean = True. In this case the CodeableConcept is not populated.
|
asNeededFor | Σ I | 0..* | CodeableConcept | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.asNeededFor Take "as needed" (for x) DefinitionIndicates whether the Medication is only taken based on a precondition for taking the Medication (CodeableConcept). Can express "as needed" with a reason by including the CodeableConcept. In this case the Boolean is assumed to be False, then the dose is given according to the schedule and is not "prn" or "as needed". A coded concept identifying the precondition that should be met or evaluated prior to consuming or administering a medication dose. For example "pain", "30 minutes prior to sexual intercourse", "on flare-up" etc.
|
site | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.site Body site to administer to DefinitionBody site to administer to. A coded specification of the anatomic site where the medication first enters the body. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension http://hl7.org/fhir/StructureDefinition/bodySite. May be a summary code, or a reference to a very precise definition of the location, or both. A coded concept describing the site location the medicine enters into or onto the body.
|
route | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.route How drug should enter body DefinitionHow drug should enter body. A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. A coded concept describing the route or physiological path of administration of a therapeutic agent into or onto the body of a subject.
|
method | Σ | 0..1 | CodeableConceptBinding | Element idMedicationRequest.dosageInstruction.method Technique for administering medication DefinitionTechnique for administering medication. A coded value indicating the method by which the medication is introduced into or onto the body. Most commonly used for injections. For examples, Slow Push; Deep IV. Terminologies used often pre-coordinate this term with the route and or form of administration. A coded concept describing the technique by which the medicine is administered.
|
doseAndRate | Σ | 0..* | Element | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.doseAndRate Amount of medication administered, to be administered or typical amount to be administered DefinitionDepending on the resource,this is the amount of medication administered, to be administered or typical amount to be administered.
|
id | 0..1 | string | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.doseAndRate.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.doseAndRate.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
type | Σ | 0..1 | CodeableConceptBinding | Element idMedicationRequest.dosageInstruction.doseAndRate.type The kind of dose or rate specified DefinitionThe kind of dose or rate specified, for example, ordered or calculated. If the type is not populated, assume to be "ordered". Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The kind of dose or rate specified.
|
dose[x] | Σ | 0..1 | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.doseAndRate.dose[x] Amount of medication per dose DefinitionAmount of medication per dose. The amount of therapeutic or other substance given at one administration event. Note that this specifies the quantity of the specified medication, not the quantity for each active ingredient(s). Each ingredient amount can be communicated in the Medication resource. For example, if one wants to communicate that a tablet was 375 mg, where the dose was one tablet, you can use the Medication resource to document that the tablet was comprised of 375 mg of drug XYZ. Alternatively if the dose was 375 mg, then you may only need to use the Medication resource to indicate this was a tablet. If the example were an IV such as dopamine and you wanted to communicate that 400mg of dopamine was mixed in 500 ml of some IV solution, then this would all be communicated in the Medication resource. If the administration is not intended to be instantaneous (rate is present or timing has a duration), this can be specified to convey the total amount to be administered over the period of time as indicated by the schedule e.g. 500 ml in dose, with timing used to convey that this should be done over 4 hours.
| |
doseRange | Range | There are no (further) constraints on this element Data type | ||
doseQuantity | SimpleQuantity | There are no (further) constraints on this element Data type | ||
rate[x] | Σ | 0..1 | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.doseAndRate.rate[x] Amount of medication per unit of time DefinitionAmount of medication per unit of time. Identifies the speed with which the medication was or will be introduced into the patient. Typically the rate for an infusion e.g. 100 ml per 1 hour or 100 ml/hr. May also be expressed as a rate per unit of time e.g. 500 ml per 2 hours. Other examples: 200 mcg/min or 200 mcg/1 minute; 1 liter/8 hours. Sometimes, a rate can imply duration when expressed as total volume / duration (e.g. 500mL/2 hours implies a duration of 2 hours). However, when rate doesn't imply duration (e.g. 250mL/hour), then the timing.repeat.duration is needed to convey the infuse over time period. It is possible to supply both a rate and a doseQuantity to provide full details about how the medication is to be administered and supplied. If the rate is intended to change over time, depending on local rules/regulations, each change should be captured as a new version of the MedicationRequest with an updated rate, or captured with a new MedicationRequest with the new rate. It is possible to specify a rate over time (for example, 100 ml/hour) using either the rateRatio and rateQuantity. The rateQuantity approach requires systems to have the capability to parse UCUM grammar where ml/hour is included rather than a specific ratio where the time is specified as the denominator. Where a rate such as 500ml over 2 hours is specified, the use of rateRatio may be more semantically correct than specifying using a rateQuantity of 250 mg/hour.
| |
rateRatio | Ratio | There are no (further) constraints on this element Data type | ||
rateRange | Range | There are no (further) constraints on this element Data type | ||
rateQuantity | SimpleQuantity | There are no (further) constraints on this element Data type | ||
maxDosePerPeriod | Σ I | 0..* | Ratio | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.maxDosePerPeriod Upper limit on medication per unit of time DefinitionUpper limit on medication per unit of time. The maximum total quantity of a therapeutic substance that may be administered to a subject over the period of time. For example, 1000mg in 24 hours. This is intended for use as an adjunct to the dosage when there is an upper cap. For example "2 tablets every 4 hours to a maximum of 8/day".
|
maxDosePerAdministration | Σ I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.maxDosePerAdministration Upper limit on medication per administration DefinitionUpper limit on medication per administration. The maximum total quantity of a therapeutic substance that may be administered to a subject per administration. This is intended for use as an adjunct to the dosage when there is an upper cap. For example, a body surface area related dose with a maximum amount, such as 1.5 mg/m2 (maximum 2 mg) IV over 5 – 10 minutes would have doseQuantity of 1.5 mg/m2 and maxDosePerAdministration of 2 mg.
|
maxDosePerLifetime | Σ I | 0..1 | SimpleQuantity | There are no (further) constraints on this element Element idMedicationRequest.dosageInstruction.maxDosePerLifetime Upper limit on medication per lifetime of the patient DefinitionUpper limit on medication per lifetime of the patient. The maximum total quantity of a therapeutic substance that may be administered per lifetime of the subject. The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
|
dispenseRequest | 0..0 | BackboneElement | There are no (further) constraints on this element Element idMedicationRequest.dispenseRequest Medication supply authorization DefinitionIndicates 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.
| |
substitution | 0..0 | BackboneElement | There are no (further) constraints on this element Element idMedicationRequest.substitution Any restrictions on medication substitution DefinitionIndicates 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.
| |
eventHistory | I | 0..0 | Reference(Provenance) | There are no (further) constraints on this element Element idMedicationRequest.eventHistory A list of events of interest in the lifecycle DefinitionLinks 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.).
|
Attribute description :
Attribute | Description | Terminology reference |
---|---|---|
status | status of MedicationRequest resource | status |
Intent | code from Terminology for Bolus activation type | insulin-codes |
medication.concept | Informs the type of administration conducted (ex. Basal or Bolus).. | insulin-codes |
medication.reference | Reference to specific medication administered.(Future implementation) | |
Subject | Patient for whom the request is generated. | |
Authored on | Date or period of time when the request is produced. | |
Performer | Who (HcP) or what (device) produced the request. | |
dosageInstruction.Method | Bolus delivery type | insulin-codes |
dosageInstruction.doseAndRate | Amount of bolus in the MedicationRequest | insulin-codes |