Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR STU3 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R5-MedicationRequest-element-map-to-R3 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R5MedicationRequestElementMapToR3 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR R5 MedicationRequest to FHIR STU3.
Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/3.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to http://hl7.org/fhir/StructureDefinition/MedicationRequest|3.0.2
| Source Concept Details | Relationship | Target Concept Details | Comment | ||
| Codes from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 | Codes from http://hl7.org/fhir/StructureDefinition/MedicationRequest|3.0.2 | ||||
| MedicationRequest.meta | meta | is equivalent to | MedicationRequest.meta | MedicationRequest.meta | Element `MedicationRequest.meta` is mapped to FHIR STU3 element `MedicationRequest.meta` as `Equivalent`. |
| MedicationRequest.implicitRules | implicitRules | is equivalent to | MedicationRequest.implicitRules | MedicationRequest.implicitRules | Element `MedicationRequest.implicitRules` is mapped to FHIR STU3 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 STU3 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 STU3 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 STU3 element `MedicationRequest.contained` as `SourceIsBroaderThanTarget`. 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 STU3 element `MedicationRequest.identifier` as `Equivalent`. This is a business identifier, not a resource identifier. |
| MedicationRequest.basedOn | basedOn | maps to wider concept | MedicationRequest.basedOn | MedicationRequest.basedOn | Element `MedicationRequest.basedOn` is mapped to FHIR STU3 element `MedicationRequest.basedOn` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `MedicationRequest.basedOn` with unmapped reference targets: CarePlan, ImmunizationRecommendation, MedicationRequest, ServiceRequest. |
| MedicationRequest.priorPrescription | priorPrescription | maps to wider concept | MedicationRequest.priorPrescription | MedicationRequest.priorPrescription | Element `MedicationRequest.priorPrescription` is mapped to FHIR STU3 element `MedicationRequest.priorPrescription` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.priorPrescription` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `MedicationRequest.priorPrescription` with unmapped reference targets: MedicationRequest. |
| MedicationRequest.groupIdentifier | groupIdentifier | is equivalent to | MedicationRequest.groupIdentifier | MedicationRequest.groupIdentifier | Element `MedicationRequest.groupIdentifier` is mapped to FHIR STU3 element `MedicationRequest.groupIdentifier` as `Equivalent`. |
| MedicationRequest.status | status | maps to wider concept | MedicationRequest.status | MedicationRequest.status | Element `MedicationRequest.status` is mapped to FHIR STU3 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.intent | intent | maps to wider concept | MedicationRequest.intent | MedicationRequest.intent | Element `MedicationRequest.intent` is mapped to FHIR STU3 element `MedicationRequest.intent` as `SourceIsBroaderThanTarget`. The target context `MedicationRequest.intent` is a modifier element, so this extension does not need to be defined as a modifier. It is expected that the type of requester will be restricted for different stages of a MedicationRequest. For example, Proposals can be created by a patient, relatedPerson, Practitioner or Device. Plans can be created by Practitioners, Patients, RelatedPersons and Devices. Original orders can be created by a Practitioner only. An instance-order is an instantiation of a request or order and may be used to populate Medication Administration Record. This element is labeled as a modifier because the intent alters when and how the resource is actually applicable. |
| MedicationRequest.category | category | is equivalent to | MedicationRequest.category | MedicationRequest.category | Element `MedicationRequest.category` is mapped to FHIR STU3 element `MedicationRequest.category` as `SourceIsBroaderThanTarget`. 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 STU3 element `MedicationRequest.priority` as `Equivalent`. |
| MedicationRequest.medication | medication | is equivalent to | MedicationRequest.medication[x] | MedicationRequest.medication[x] | Element `MedicationRequest.medication` is mapped to FHIR STU3 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 | maps to wider concept | MedicationRequest.subject | MedicationRequest.subject | Element `MedicationRequest.subject` is mapped to FHIR STU3 element `MedicationRequest.subject` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.subject` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `MedicationRequest.subject` with unmapped reference targets: Group, Patient. 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 | maps to wider concept | MedicationRequest.context | MedicationRequest.context | Element `MedicationRequest.encounter` is mapped to FHIR STU3 element `MedicationRequest.context` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.encounter` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `MedicationRequest.encounter` with unmapped reference targets: Encounter. 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 | maps to wider concept | MedicationRequest.supportingInformation | MedicationRequest.supportingInformation | Element `MedicationRequest.supportingInformation` is mapped to FHIR STU3 element `MedicationRequest.supportingInformation` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.supportingInformation` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `MedicationRequest.supportingInformation` with unmapped reference targets: Resource. 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 STU3 element `MedicationRequest.authoredOn` as `Equivalent`. |
| MedicationRequest.requester | requester | maps to wider concept | MedicationRequest.requester.agent | MedicationRequest.requester.agent | Element `MedicationRequest.requester` is mapped to FHIR STU3 element `MedicationRequest.requester.agent` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `MedicationRequest.requester` with unmapped reference targets: Device, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson. |
| MedicationRequest.recorder | recorder | maps to wider concept | MedicationRequest.recorder | MedicationRequest.recorder | Element `MedicationRequest.recorder` is mapped to FHIR STU3 element `MedicationRequest.recorder` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.recorder` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `MedicationRequest.recorder` with unmapped reference targets: Practitioner, PractitionerRole. |
| MedicationRequest.reason | reason | is related to | MedicationRequest.reasonCode | MedicationRequest.reasonCode | Element `MedicationRequest.reason` is mapped to FHIR STU3 element `MedicationRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `MedicationRequest.reason` is mapped to FHIR STU3 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 STU3 element `MedicationRequest.reasonCode` as `SourceIsBroaderThanTarget`. Element `MedicationRequest.reason` is mapped to FHIR STU3 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.note | note | is equivalent to | MedicationRequest.note | MedicationRequest.note | Element `MedicationRequest.note` is mapped to FHIR STU3 element `MedicationRequest.note` as `Equivalent`. |
| MedicationRequest.dosageInstruction | dosageInstruction | is equivalent to | MedicationRequest.dosageInstruction | MedicationRequest.dosageInstruction | Element `MedicationRequest.dosageInstruction` is mapped to FHIR STU3 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 STU3 element `MedicationRequest.dispenseRequest` as `Equivalent`. |
| MedicationRequest.dispenseRequest.validityPeriod | validityPeriod | is equivalent to | MedicationRequest.dispenseRequest.validityPeriod | MedicationRequest.dispenseRequest.validityPeriod | Element `MedicationRequest.dispenseRequest.validityPeriod` is mapped to FHIR STU3 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 | maps to wider concept | MedicationRequest.dispenseRequest.numberOfRepeatsAllowed | MedicationRequest.dispenseRequest.numberOfRepeatsAllowed | Element `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` is mapped to FHIR STU3 element `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` do not cover the following types: unsignedInt. The mappings for `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` do not cover the following types based on type expansion: value. 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 STU3 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 STU3 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 | maps to wider concept | MedicationRequest.dispenseRequest.performer | MedicationRequest.dispenseRequest.performer | Element `MedicationRequest.dispenseRequest.dispenser` is mapped to FHIR STU3 element `MedicationRequest.dispenseRequest.performer` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.dispenseRequest.dispenser` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `MedicationRequest.dispenseRequest.dispenser` with unmapped reference targets: Organization. |
| MedicationRequest.substitution | substitution | maps to wider concept | MedicationRequest.substitution | MedicationRequest.substitution | Element `MedicationRequest.substitution` is mapped to FHIR STU3 element `MedicationRequest.substitution` as `Equivalent`. |
| MedicationRequest.substitution.allowed[x] | allowed[x] | maps to wider concept | MedicationRequest.substitution.allowed | MedicationRequest.substitution.allowed | Element `MedicationRequest.substitution.allowed[x]` is mapped to FHIR STU3 element `MedicationRequest.substitution.allowed` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.substitution.allowed[x]` do not cover the following types: CodeableConcept. The mappings for `MedicationRequest.substitution.allowed[x]` do not cover the following types based on type expansion: coding, text. 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 STU3 element `MedicationRequest.substitution.reason` as `Equivalent`. |
| MedicationRequest.eventHistory | eventHistory | maps to wider concept | MedicationRequest.eventHistory | MedicationRequest.eventHistory | Element `MedicationRequest.eventHistory` is mapped to FHIR STU3 element `MedicationRequest.eventHistory` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.eventHistory` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `MedicationRequest.eventHistory` with unmapped reference targets: Provenance. 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 STU3 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: Reason for current status (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| MedicationRequest.statusReason (statusReason) | is equivalent to | Extension (R5: Reason for current status (new)) | Element `MedicationRequest.statusReason` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.statusReason` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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. |
Group 4 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 STU3. 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: proposal | plan | order | original-order | reflex-order | filler-order | instance-order | optionversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| MedicationRequest.intent (intent) | is equivalent to | Extension (R5: proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option) | Element `MedicationRequest.intent` is mapped to FHIR STU3 element `MedicationRequest.intent` as `SourceIsBroaderThanTarget`. The target context `MedicationRequest.intent` is a modifier element, so this extension does not need to be defined as a modifier. 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. |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: True if patient is to stop taking or not to start taking the medication (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| MedicationRequest.doNotPerform (doNotPerform) | is equivalent to | Extension (R5: True if patient is to stop taking or not to start taking the medication (new)) | Element `MedicationRequest.doNotPerform` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.doNotPerform` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If do not perform is not specified, the request is a positive request e.g. "do perform". |
Group 7 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 STU3. 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: Reported rather than primary record (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| MedicationRequest.reported (reported) | is equivalent to | Extension (R5: Reported rather than primary record (new)) | Element `MedicationRequest.reported` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.reported` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If not populated, then assume that this is the original record and not reported |
Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: Desired kind of performer of the medication administration (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| MedicationRequest.performerType (performerType) | is equivalent to | Extension (R5: Desired kind of performer of the medication administration (new)) | Element `MedicationRequest.performerType` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.performerType` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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. |
Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: Intended performer of administration (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| MedicationRequest.performer (performer) | maps to wider concept | Extension (R5: Intended performer of administration (new)) | Element `MedicationRequest.performer` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.performer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 11 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 STU3. Typically, this is because the element has been added (is a new element). |
Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: Overall pattern of medication administration (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| MedicationRequest.courseOfTherapyType (courseOfTherapyType) | is equivalent to | Extension (R5: Overall pattern of medication administration (new)) | Element `MedicationRequest.courseOfTherapyType` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.courseOfTherapyType` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This attribute should not be confused with the protocol of the medication. |
Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: Associated insurance coverage (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| MedicationRequest.insurance (insurance) | is equivalent to | Extension (R5: Associated insurance coverage (new)) | Element `MedicationRequest.insurance` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.insurance` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 14 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 STU3. Typically, this is because the element has been added (is a new element). |
Group 15 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 STU3. Typically, this is because the element has been added (is a new element). |
Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: First fill details (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| MedicationRequest.dispenseRequest.initialFill (initialFill) | is equivalent to | Extension (R5: First fill details (new)) | Element `MedicationRequest.dispenseRequest.initialFill` has a context of MedicationRequest.dispenseRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.dispenseRequest.initialFill` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If populating this element, either the quantity or the duration must be included. |
| MedicationRequest.dispenseRequest.initialFill.quantity (quantity) | is equivalent to | Extension.extension:quantity (R5: First fill quantity (new)) | Element `MedicationRequest.dispenseRequest.initialFill.quantity` is part of an existing definition because parent element `MedicationRequest.dispenseRequest.initialFill` requires a cross-version extension. Element `MedicationRequest.dispenseRequest.initialFill.quantity` has a context of MedicationRequest.dispenseRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.dispenseRequest.initialFill.quantity` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
| MedicationRequest.dispenseRequest.initialFill.duration (duration) | is equivalent to | Extension.extension:duration (R5: First fill duration (new)) | Element `MedicationRequest.dispenseRequest.initialFill.duration` is part of an existing definition because parent element `MedicationRequest.dispenseRequest.initialFill` requires a cross-version extension. Element `MedicationRequest.dispenseRequest.initialFill.duration` has a context of MedicationRequest.dispenseRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.dispenseRequest.initialFill.duration` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: Minimum period of time between dispenses (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| MedicationRequest.dispenseRequest.dispenseInterval (dispenseInterval) | is equivalent to | Extension (R5: Minimum period of time between dispenses (new)) | Element `MedicationRequest.dispenseRequest.dispenseInterval` has a context of MedicationRequest.dispenseRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.dispenseRequest.dispenseInterval` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: numberOfRepeatsAllowed additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| MedicationRequest.dispenseRequest.numberOfRepeatsAllowed (numberOfRepeatsAllowed) | is equivalent to | Extension (R5: numberOfRepeatsAllowed additional types) | Element `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` is mapped to FHIR STU3 element `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` do not cover the following types: unsignedInt. The mappings for `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` do not cover the following types based on type expansion: value. If displaying "number of authorized fills", add 1 to this number. |
Group 19 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 STU3. Typically, this is because the element has been added (is a new element). |
Group 20 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 STU3. Typically, this is because the element has been added (is a new element). |
Group 21 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|5.0.0 to R5: Whether substitution is allowed or not additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| MedicationRequest.substitution.allowed[x] (allowed[x]) | maps to wider concept | Extension (R5: Whether substitution is allowed or not additional types) | Element `MedicationRequest.substitution.allowed[x]` is mapped to FHIR STU3 element `MedicationRequest.substitution.allowed` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.substitution.allowed[x]` do not cover the following types: CodeableConcept. The mappings for `MedicationRequest.substitution.allowed[x]` do not cover the following types based on type expansion: coding, text. This element is labeled as a modifier because whether substitution is allow or not, it cannot be ignored. |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r5.r3#0.1.0 based on FHIR 3.0.2. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change