Generated Narrative: ConceptMap R5-MedicationRequest-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to MedicationRequestversion: 4.0.1) Source Concept Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 Codes from MedicationRequest MedicationRequest.meta meta is equivalent to MedicationRequest.meta MedicationRequest.meta Element `MedicationRequest.meta` is mapped to FHIR R4 element `MedicationRequest.meta` as `Equivalent`. MedicationRequest.implicitRules implicitRules is equivalent to MedicationRequest.implicitRules MedicationRequest.implicitRules Element `MedicationRequest.implicitRules` is mapped to FHIR R4 element `MedicationRequest.implicitRules` as `Equivalent`. 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. MedicationRequest.language language is equivalent to MedicationRequest.language MedicationRequest.language Element `MedicationRequest.language` is mapped to FHIR R4 element `MedicationRequest.language` as `Equivalent`. 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). MedicationRequest.text text is equivalent to MedicationRequest.text MedicationRequest.text Element `MedicationRequest.text` is mapped to FHIR R4 element `MedicationRequest.text` as `Equivalent`. 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. MedicationRequest.contained contained is equivalent to MedicationRequest.contained MedicationRequest.contained Element `MedicationRequest.contained` is mapped to FHIR R4 element `MedicationRequest.contained` as `Equivalent`. 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. MedicationRequest.identifier identifier is equivalent to MedicationRequest.identifier MedicationRequest.identifier Element `MedicationRequest.identifier` is mapped to FHIR R4 element `MedicationRequest.identifier` as `Equivalent`. This is a business identifier, not a resource identifier. MedicationRequest.basedOn basedOn is equivalent to MedicationRequest.basedOn MedicationRequest.basedOn Element `MedicationRequest.basedOn` is mapped to FHIR R4 element `MedicationRequest.basedOn` as `Equivalent`. MedicationRequest.priorPrescription priorPrescription is equivalent to MedicationRequest.priorPrescription MedicationRequest.priorPrescription Element `MedicationRequest.priorPrescription` is mapped to FHIR R4 element `MedicationRequest.priorPrescription` as `Equivalent`. MedicationRequest.groupIdentifier groupIdentifier is equivalent to MedicationRequest.groupIdentifier MedicationRequest.groupIdentifier Element `MedicationRequest.groupIdentifier` is mapped to FHIR R4 element `MedicationRequest.groupIdentifier` as `Equivalent`. MedicationRequest.status status maps to wider concept MedicationRequest.status MedicationRequest.status Element `MedicationRequest.status` is mapped to FHIR R4 element `MedicationRequest.status` as `RelatedTo`. The mappings for `MedicationRequest.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `MedicationRequest.status` is a modifier element, so this extension does not need to be defined as a modifier. 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 statusReason is equivalent to MedicationRequest.statusReason MedicationRequest.statusReason Element `MedicationRequest.statusReason` is mapped to FHIR R4 element `MedicationRequest.statusReason` as `Equivalent`. 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.intent intent is equivalent to MedicationRequest.intent MedicationRequest.intent Element `MedicationRequest.intent` is mapped to FHIR R4 element `MedicationRequest.intent` as `Equivalent`. 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.#xD;#xD;An instance-order is an instantiation of a request or order and may be used to populate Medication Administration Record.#xD;#xD;This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. MedicationRequest.category category is equivalent to MedicationRequest.category MedicationRequest.category Element `MedicationRequest.category` is mapped to FHIR R4 element `MedicationRequest.category` as `Equivalent`. 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 priority is equivalent to MedicationRequest.priority MedicationRequest.priority Element `MedicationRequest.priority` is mapped to FHIR R4 element `MedicationRequest.priority` as `Equivalent`. MedicationRequest.doNotPerform doNotPerform is equivalent to MedicationRequest.doNotPerform MedicationRequest.doNotPerform Element `MedicationRequest.doNotPerform` is mapped to FHIR R4 element `MedicationRequest.doNotPerform` as `Equivalent`. If do not perform is not specified, the request is a positive request e.g. "do perform". MedicationRequest.medication medication is equivalent to MedicationRequest.medication[x] MedicationRequest.medication[x] Element `MedicationRequest.medication` is mapped to FHIR R4 element `MedicationRequest.medication[x]` as `SourceIsBroaderThanTarget`. The target context `MedicationRequest.medication[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `MedicationRequest`. 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 subject is equivalent to MedicationRequest.subject MedicationRequest.subject Element `MedicationRequest.subject` is mapped to FHIR R4 element `MedicationRequest.subject` as `Equivalent`. 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.encounter encounter is equivalent to MedicationRequest.encounter MedicationRequest.encounter Element `MedicationRequest.encounter` is mapped to FHIR R4 element `MedicationRequest.encounter` as `Equivalent`. 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 supportingInformation is equivalent to MedicationRequest.supportingInformation MedicationRequest.supportingInformation Element `MedicationRequest.supportingInformation` is mapped to FHIR R4 element `MedicationRequest.supportingInformation` as `Equivalent`. This attribute can be used to reference a MedicationStatement about the patients' medication use. MedicationRequest.authoredOn authoredOn is equivalent to MedicationRequest.authoredOn MedicationRequest.authoredOn Element `MedicationRequest.authoredOn` is mapped to FHIR R4 element `MedicationRequest.authoredOn` as `Equivalent`. MedicationRequest.requester requester is equivalent to MedicationRequest.requester MedicationRequest.requester Element `MedicationRequest.requester` is mapped to FHIR R4 element `MedicationRequest.requester` as `Equivalent`. MedicationRequest.reported reported is equivalent to MedicationRequest.reported[x] MedicationRequest.reported[x] Element `MedicationRequest.reported` is mapped to FHIR R4 element `MedicationRequest.reported[x]` as `Equivalent`. The target context `MedicationRequest.reported[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `MedicationRequest`. If not populated, then assume that this is the original record and not reported MedicationRequest.performerType performerType is equivalent to MedicationRequest.performerType MedicationRequest.performerType Element `MedicationRequest.performerType` is mapped to FHIR R4 element `MedicationRequest.performerType` as `Equivalent`. 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 performer maps to wider concept MedicationRequest.performer MedicationRequest.performer Element `MedicationRequest.performer` is mapped to FHIR R4 element `MedicationRequest.performer` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `MedicationRequest.performer` with unmapped reference targets: DeviceDefinition, HealthcareService. MedicationRequest.recorder recorder is equivalent to MedicationRequest.recorder MedicationRequest.recorder Element `MedicationRequest.recorder` is mapped to FHIR R4 element `MedicationRequest.recorder` as `Equivalent`. MedicationRequest.reason reason is related to MedicationRequest.reasonCode MedicationRequest.reasonCode Element `MedicationRequest.reason` is mapped to FHIR R4 element `MedicationRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `MedicationRequest.reason` is mapped to FHIR R4 element `MedicationRequest.reasonReference` as `SourceIsBroaderThanTarget`. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference. is related to MedicationRequest.reasonReference MedicationRequest.reasonReference Element `MedicationRequest.reason` is mapped to FHIR R4 element `MedicationRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `MedicationRequest.reason` is mapped to FHIR R4 element `MedicationRequest.reasonReference` as `SourceIsBroaderThanTarget`. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference. MedicationRequest.courseOfTherapyType courseOfTherapyType is equivalent to MedicationRequest.courseOfTherapyType MedicationRequest.courseOfTherapyType Element `MedicationRequest.courseOfTherapyType` is mapped to FHIR R4 element `MedicationRequest.courseOfTherapyType` as `Equivalent`. This attribute should not be confused with the protocol of the medication. MedicationRequest.insurance insurance is equivalent to MedicationRequest.insurance MedicationRequest.insurance Element `MedicationRequest.insurance` is mapped to FHIR R4 element `MedicationRequest.insurance` as `Equivalent`. MedicationRequest.note note is equivalent to MedicationRequest.note MedicationRequest.note Element `MedicationRequest.note` is mapped to FHIR R4 element `MedicationRequest.note` as `Equivalent`. MedicationRequest.dosageInstruction dosageInstruction is equivalent to MedicationRequest.dosageInstruction MedicationRequest.dosageInstruction Element `MedicationRequest.dosageInstruction` is mapped to FHIR R4 element `MedicationRequest.dosageInstruction` as `Equivalent`. 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 dispenseRequest maps to wider concept MedicationRequest.dispenseRequest MedicationRequest.dispenseRequest Element `MedicationRequest.dispenseRequest` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest` as `Equivalent`. MedicationRequest.dispenseRequest.initialFill initialFill maps to wider concept MedicationRequest.dispenseRequest.initialFill MedicationRequest.dispenseRequest.initialFill Element `MedicationRequest.dispenseRequest.initialFill` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.initialFill` as `Equivalent`. If populating this element, either the quantity or the duration must be included. MedicationRequest.dispenseRequest.initialFill.quantity quantity is equivalent to MedicationRequest.dispenseRequest.initialFill.quantity MedicationRequest.dispenseRequest.initialFill.quantity Element `MedicationRequest.dispenseRequest.initialFill.quantity` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.initialFill.quantity` as `Equivalent`. MedicationRequest.dispenseRequest.initialFill.duration duration is equivalent to MedicationRequest.dispenseRequest.initialFill.duration MedicationRequest.dispenseRequest.initialFill.duration Element `MedicationRequest.dispenseRequest.initialFill.duration` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.initialFill.duration` as `Equivalent`. MedicationRequest.dispenseRequest.dispenseInterval dispenseInterval is equivalent to MedicationRequest.dispenseRequest.dispenseInterval MedicationRequest.dispenseRequest.dispenseInterval Element `MedicationRequest.dispenseRequest.dispenseInterval` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.dispenseInterval` as `Equivalent`. MedicationRequest.dispenseRequest.validityPeriod validityPeriod is equivalent to MedicationRequest.dispenseRequest.validityPeriod MedicationRequest.dispenseRequest.validityPeriod Element `MedicationRequest.dispenseRequest.validityPeriod` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.validityPeriod` as `Equivalent`. 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 numberOfRepeatsAllowed is equivalent to MedicationRequest.dispenseRequest.numberOfRepeatsAllowed MedicationRequest.dispenseRequest.numberOfRepeatsAllowed Element `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` as `Equivalent`. If displaying "number of authorized fills", add 1 to this number. MedicationRequest.dispenseRequest.quantity quantity is equivalent to MedicationRequest.dispenseRequest.quantity MedicationRequest.dispenseRequest.quantity Element `MedicationRequest.dispenseRequest.quantity` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.quantity` as `Equivalent`. MedicationRequest.dispenseRequest.expectedSupplyDuration expectedSupplyDuration is equivalent to MedicationRequest.dispenseRequest.expectedSupplyDuration MedicationRequest.dispenseRequest.expectedSupplyDuration Element `MedicationRequest.dispenseRequest.expectedSupplyDuration` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.expectedSupplyDuration` as `Equivalent`. 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 dispenser is equivalent to MedicationRequest.dispenseRequest.performer MedicationRequest.dispenseRequest.performer Element `MedicationRequest.dispenseRequest.dispenser` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.performer` as `Equivalent`. MedicationRequest.substitution substitution maps to wider concept MedicationRequest.substitution MedicationRequest.substitution Element `MedicationRequest.substitution` is mapped to FHIR R4 element `MedicationRequest.substitution` as `Equivalent`. MedicationRequest.substitution.allowed[x] allowed[x] is equivalent to MedicationRequest.substitution.allowed[x] MedicationRequest.substitution.allowed[x] Element `MedicationRequest.substitution.allowed[x]` is mapped to FHIR R4 element `MedicationRequest.substitution.allowed[x]` as `Equivalent`. The target context `MedicationRequest.substitution.allowed[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `MedicationRequest.substitution`. This element is labeled as a modifier because whether substitution is allow or not, it cannot be ignored. MedicationRequest.substitution.reason reason is equivalent to MedicationRequest.substitution.reason MedicationRequest.substitution.reason Element `MedicationRequest.substitution.reason` is mapped to FHIR R4 element `MedicationRequest.substitution.reason` as `Equivalent`. MedicationRequest.eventHistory eventHistory is equivalent to MedicationRequest.eventHistory MedicationRequest.eventHistory Element `MedicationRequest.eventHistory` is mapped to FHIR R4 element `MedicationRequest.eventHistory` as `Equivalent`. 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.). Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: active | on-hold | ended | stopped | completed | cancelled | entered-in-error | draft | unknown additional codesversion: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.status (status) is equivalent to Extension (R5: active | on-hold | ended | stopped | completed | cancelled | entered-in-error | draft | unknown additional codes) Element `MedicationRequest.status` is mapped to FHIR R4 element `MedicationRequest.status` as `RelatedTo`. The mappings for `MedicationRequest.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `MedicationRequest.status` is a modifier element, so this extension does not need to be defined as a modifier. 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. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: When the status was changed (new)version: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.statusChanged (statusChanged) maps to wider concept Extension (R5: When the status was changed (new)) Element `MedicationRequest.statusChanged` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.statusChanged` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: The person or organization who provided the information about this request, if the source is someone other than the requestor (new)version: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.informationSource (informationSource) maps to wider concept Extension (R5: The person or organization who provided the information about this request, if the source is someone other than the requestor (new)) Element `MedicationRequest.informationSource` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.informationSource` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: Intended type of device for the administration (new)version: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.device (device) maps to wider concept Extension (R5: Intended type of device for the administration (new)) Element `MedicationRequest.device` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.device` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: Full representation of the dosage instructions (new)version: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.renderedDosageInstruction (renderedDosageInstruction) maps to wider concept Extension (R5: Full representation of the dosage instructions (new)) Element `MedicationRequest.renderedDosageInstruction` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.renderedDosageInstruction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: Period over which the medication is to be taken (new)version: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.effectiveDosePeriod (effectiveDosePeriod) maps to wider concept Extension (R5: Period over which the medication is to be taken (new)) Element `MedicationRequest.effectiveDosePeriod` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.effectiveDosePeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: Additional information for the dispenser (new)version: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.dispenseRequest.dispenserInstruction (dispenserInstruction) maps to wider concept Extension (R5: Additional information for the dispenser (new)) Element `MedicationRequest.dispenseRequest.dispenserInstruction` has a context of MedicationRequest.dispenseRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.dispenseRequest.dispenserInstruction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: Type of adherence packaging to use for the dispense (new)version: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.dispenseRequest.doseAdministrationAid (doseAdministrationAid) maps to wider concept Extension (R5: Type of adherence packaging to use for the dispense (new)) Element `MedicationRequest.dispenseRequest.doseAdministrationAid` has a context of MedicationRequest.dispenseRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.dispenseRequest.doseAdministrationAid` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Cross-version mapping for FHIR R5 MedicationRequest to FHIR R4 MedicationRequest
This ConceptMap represents cross-version mappings for elements from a FHIR R5 MedicationRequest to FHIR R4.
Element `MedicationRequest.meta` is mapped to FHIR R4 element `MedicationRequest.meta` as `Equivalent`.
Element `MedicationRequest.implicitRules` is mapped to FHIR R4 element `MedicationRequest.implicitRules` as `Equivalent`. 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.
Element `MedicationRequest.language` is mapped to FHIR R4 element `MedicationRequest.language` as `Equivalent`. 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).
Element `MedicationRequest.text` is mapped to FHIR R4 element `MedicationRequest.text` as `Equivalent`. 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.
Element `MedicationRequest.contained` is mapped to FHIR R4 element `MedicationRequest.contained` as `Equivalent`. 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.
Element `MedicationRequest.identifier` is mapped to FHIR R4 element `MedicationRequest.identifier` as `Equivalent`. This is a business identifier, not a resource identifier.
Element `MedicationRequest.basedOn` is mapped to FHIR R4 element `MedicationRequest.basedOn` as `Equivalent`.
Element `MedicationRequest.priorPrescription` is mapped to FHIR R4 element `MedicationRequest.priorPrescription` as `Equivalent`.
Element `MedicationRequest.groupIdentifier` is mapped to FHIR R4 element `MedicationRequest.groupIdentifier` as `Equivalent`.
Element `MedicationRequest.status` is mapped to FHIR R4 element `MedicationRequest.status` as `RelatedTo`. The mappings for `MedicationRequest.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `MedicationRequest.status` is a modifier element, so this extension does not need to be defined as a modifier. 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.
Element `MedicationRequest.statusReason` is mapped to FHIR R4 element `MedicationRequest.statusReason` as `Equivalent`. 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.
Element `MedicationRequest.intent` is mapped to FHIR R4 element `MedicationRequest.intent` as `Equivalent`. 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.
Element `MedicationRequest.category` is mapped to FHIR R4 element `MedicationRequest.category` as `Equivalent`. 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.
Element `MedicationRequest.priority` is mapped to FHIR R4 element `MedicationRequest.priority` as `Equivalent`.
Element `MedicationRequest.doNotPerform` is mapped to FHIR R4 element `MedicationRequest.doNotPerform` as `Equivalent`. If do not perform is not specified, the request is a positive request e.g. "do perform".
Element `MedicationRequest.medication` is mapped to FHIR R4 element `MedicationRequest.medication[x]` as `SourceIsBroaderThanTarget`. The target context `MedicationRequest.medication[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `MedicationRequest`. 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.
Element `MedicationRequest.subject` is mapped to FHIR R4 element `MedicationRequest.subject` as `Equivalent`. 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.
Element `MedicationRequest.encounter` is mapped to FHIR R4 element `MedicationRequest.encounter` as `Equivalent`. 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.
Element `MedicationRequest.supportingInformation` is mapped to FHIR R4 element `MedicationRequest.supportingInformation` as `Equivalent`. This attribute can be used to reference a MedicationStatement about the patients' medication use.
Element `MedicationRequest.authoredOn` is mapped to FHIR R4 element `MedicationRequest.authoredOn` as `Equivalent`.
Element `MedicationRequest.requester` is mapped to FHIR R4 element `MedicationRequest.requester` as `Equivalent`.
Element `MedicationRequest.reported` is mapped to FHIR R4 element `MedicationRequest.reported[x]` as `Equivalent`. The target context `MedicationRequest.reported[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `MedicationRequest`. If not populated, then assume that this is the original record and not reported
Element `MedicationRequest.performerType` is mapped to FHIR R4 element `MedicationRequest.performerType` as `Equivalent`. 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.
Element `MedicationRequest.performer` is mapped to FHIR R4 element `MedicationRequest.performer` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `MedicationRequest.performer` with unmapped reference targets: DeviceDefinition, HealthcareService.
Element `MedicationRequest.recorder` is mapped to FHIR R4 element `MedicationRequest.recorder` as `Equivalent`.
Element `MedicationRequest.reason` is mapped to FHIR R4 element `MedicationRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `MedicationRequest.reason` is mapped to FHIR R4 element `MedicationRequest.reasonReference` as `SourceIsBroaderThanTarget`. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference.
Element `MedicationRequest.courseOfTherapyType` is mapped to FHIR R4 element `MedicationRequest.courseOfTherapyType` as `Equivalent`. This attribute should not be confused with the protocol of the medication.
Element `MedicationRequest.insurance` is mapped to FHIR R4 element `MedicationRequest.insurance` as `Equivalent`.
Element `MedicationRequest.note` is mapped to FHIR R4 element `MedicationRequest.note` as `Equivalent`.
Element `MedicationRequest.dosageInstruction` is mapped to FHIR R4 element `MedicationRequest.dosageInstruction` as `Equivalent`. 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.
Element `MedicationRequest.dispenseRequest` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest` as `Equivalent`.
Element `MedicationRequest.dispenseRequest.initialFill` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.initialFill` as `Equivalent`. If populating this element, either the quantity or the duration must be included.
Element `MedicationRequest.dispenseRequest.initialFill.quantity` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.initialFill.quantity` as `Equivalent`.
Element `MedicationRequest.dispenseRequest.initialFill.duration` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.initialFill.duration` as `Equivalent`.
Element `MedicationRequest.dispenseRequest.dispenseInterval` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.dispenseInterval` as `Equivalent`.
Element `MedicationRequest.dispenseRequest.validityPeriod` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.validityPeriod` as `Equivalent`. 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.
Element `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` as `Equivalent`. If displaying "number of authorized fills", add 1 to this number.
Element `MedicationRequest.dispenseRequest.quantity` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.quantity` as `Equivalent`.
Element `MedicationRequest.dispenseRequest.expectedSupplyDuration` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.expectedSupplyDuration` as `Equivalent`. 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.
Element `MedicationRequest.dispenseRequest.dispenser` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.performer` as `Equivalent`.
Element `MedicationRequest.substitution` is mapped to FHIR R4 element `MedicationRequest.substitution` as `Equivalent`.
Element `MedicationRequest.substitution.allowed[x]` is mapped to FHIR R4 element `MedicationRequest.substitution.allowed[x]` as `Equivalent`. The target context `MedicationRequest.substitution.allowed[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `MedicationRequest.substitution`. This element is labeled as a modifier because whether substitution is allow or not, it cannot be ignored.
Element `MedicationRequest.substitution.reason` is mapped to FHIR R4 element `MedicationRequest.substitution.reason` as `Equivalent`.
Element `MedicationRequest.eventHistory` is mapped to FHIR R4 element `MedicationRequest.eventHistory` as `Equivalent`. 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.).
Element `MedicationRequest.statusChanged` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.statusChanged` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `MedicationRequest.informationSource` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.informationSource` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `MedicationRequest.device` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.device` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `MedicationRequest.renderedDosageInstruction` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.renderedDosageInstruction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `MedicationRequest.effectiveDosePeriod` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.effectiveDosePeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `MedicationRequest.dispenseRequest.dispenserInstruction` has a context of MedicationRequest.dispenseRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.dispenseRequest.dispenserInstruction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `MedicationRequest.dispenseRequest.doseAdministrationAid` has a context of MedicationRequest.dispenseRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.dispenseRequest.doseAdministrationAid` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).