Generated Narrative: ConceptMap R3-MedicationRequest-element-map-to-R4B Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.3 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|3.0.2 to MedicationRequestversion: 4.3.0) Source Code Relationship Target Code Comment MedicationRequest.meta (meta) maps to wider concept MedicationRequest.meta Element `MedicationRequest.meta` is mapped to FHIR R4B element `MedicationRequest.meta` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.meta` do not cover the following types: Meta. The mappings for `MedicationRequest.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. MedicationRequest.implicitRules (implicitRules) is equivalent to MedicationRequest.implicitRules Element `MedicationRequest.implicitRules` is mapped to FHIR R4B 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. MedicationRequest.language (language) is equivalent to MedicationRequest.language Element `MedicationRequest.language` is mapped to FHIR R4B 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) maps to wider concept MedicationRequest.text Element `MedicationRequest.text` is mapped to FHIR R4B element `MedicationRequest.text` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.text` do not cover the following types: Narrative. The mappings for `MedicationRequest.text` do not cover the following types based on type expansion: div, status. Contained resources do not have 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 in formation is added later. MedicationRequest.contained (contained) is equivalent to MedicationRequest.contained Element `MedicationRequest.contained` is mapped to FHIR R4B 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. MedicationRequest.identifier (identifier) maps to wider concept MedicationRequest.identifier Element `MedicationRequest.identifier` is mapped to FHIR R4B element `MedicationRequest.identifier` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.identifier` do not cover the following types: Identifier. The mappings for `MedicationRequest.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. MedicationRequest.basedOn (basedOn) maps to wider concept MedicationRequest.basedOn Element `MedicationRequest.basedOn` is mapped to FHIR R4B element `MedicationRequest.basedOn` as `RelatedTo`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.basedOn` with unmapped reference targets: CarePlan, MedicationRequest, ProcedureRequest, ReferralRequest. MedicationRequest.groupIdentifier (groupIdentifier) maps to wider concept MedicationRequest.groupIdentifier Element `MedicationRequest.groupIdentifier` is mapped to FHIR R4B element `MedicationRequest.groupIdentifier` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.groupIdentifier` do not cover the following types: Identifier. The mappings for `MedicationRequest.groupIdentifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. MedicationRequest.status (status) is equivalent to MedicationRequest.status Element `MedicationRequest.status` is mapped to FHIR R4B element `MedicationRequest.status` as `Equivalent`. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. MedicationRequest.intent (intent) is equivalent to MedicationRequest.intent Element `MedicationRequest.intent` is mapped to FHIR R4B element `MedicationRequest.intent` as `SourceIsNarrowerThanTarget`. The mappings for `MedicationRequest.intent` do not allow expression of the necessary codes, per the bindings on the source and target. 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. 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 Element `MedicationRequest.category` is mapped to FHIR R4B element `MedicationRequest.category` as `SourceIsNarrowerThanTarget`. MedicationRequest.priority (priority) is equivalent to MedicationRequest.priority Element `MedicationRequest.priority` is mapped to FHIR R4B element `MedicationRequest.priority` as `Equivalent`. MedicationRequest.medication[x] (medication[x]) maps to wider concept MedicationRequest.medication[x] Element `MedicationRequest.medication[x]` is mapped to FHIR R4B element `MedicationRequest.medication[x]` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.medication[x]` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.medication[x]` with unmapped reference targets: Medication. Source element `MedicationRequest.medication[x]` has unmapped reference types. While the target element `MedicationRequest.medication[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it. 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 Element `MedicationRequest.subject` is mapped to FHIR R4B element `MedicationRequest.subject` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.subject` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 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.context (context) maps to wider concept MedicationRequest.encounter Element `MedicationRequest.context` is mapped to FHIR R4B element `MedicationRequest.encounter` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.context` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.context` with unmapped reference targets: Encounter, EpisodeOfCare. SubstanceAdministration->component->EncounterEvent. MedicationRequest.supportingInformation (supportingInformation) maps to wider concept MedicationRequest.supportingInformation Element `MedicationRequest.supportingInformation` is mapped to FHIR R4B element `MedicationRequest.supportingInformation` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.supportingInformation` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.supportingInformation` with unmapped reference targets: Resource. MedicationRequest.authoredOn (authoredOn) is equivalent to MedicationRequest.authoredOn Element `MedicationRequest.authoredOn` is mapped to FHIR R4B element `MedicationRequest.authoredOn` as `Equivalent`. MedicationRequest.requester (requester) maps to wider concept MedicationRequest.requester Element `MedicationRequest.requester` is mapped to FHIR R4B element `MedicationRequest.requester` as `Equivalent`. MedicationRequest.requester.agent (agent) maps to wider concept MedicationRequest.requester Element `MedicationRequest.requester.agent` is mapped to FHIR R4B element `MedicationRequest.requester` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.requester.agent` with unmapped reference targets: Device, Organization, Patient, Practitioner, RelatedPerson. 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. MedicationRequest.recorder (recorder) maps to wider concept MedicationRequest.recorder Element `MedicationRequest.recorder` is mapped to FHIR R4B element `MedicationRequest.recorder` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.recorder` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.recorder` with unmapped reference targets: Practitioner. MedicationRequest.reasonCode (reasonCode) is equivalent to MedicationRequest.reasonCode Element `MedicationRequest.reasonCode` is mapped to FHIR R4B element `MedicationRequest.reasonCode` as `Equivalent`. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference. MedicationRequest.reasonReference (reasonReference) maps to wider concept MedicationRequest.reasonReference Element `MedicationRequest.reasonReference` is mapped to FHIR R4B element `MedicationRequest.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.reasonReference` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.reasonReference` with unmapped reference targets: Condition, Observation. This is a reference to a condition or observation that is the reason for the medication order. If only a code exists, use reasonCode. MedicationRequest.note (note) maps to wider concept MedicationRequest.note Element `MedicationRequest.note` is mapped to FHIR R4B element `MedicationRequest.note` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.note` do not cover the following types: Annotation. The mappings for `MedicationRequest.note` do not cover the following types based on type expansion: author[x], text, time. MedicationRequest.dosageInstruction (dosageInstruction) maps to wider concept MedicationRequest.dosageInstruction Element `MedicationRequest.dosageInstruction` is mapped to FHIR R4B element `MedicationRequest.dosageInstruction` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.dosageInstruction` do not cover the following types: Dosage. The mappings for `MedicationRequest.dosageInstruction` do not cover the following types based on type expansion: additionalInstruction, asNeeded[x], dose[x], maxDosePerAdministration, maxDosePerLifetime, maxDosePerPeriod, method, patientInstruction, rate[x], route, sequence, site, text, timing. 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. MedicationRequest.dispenseRequest (dispenseRequest) maps to wider concept MedicationRequest.dispenseRequest Element `MedicationRequest.dispenseRequest` is mapped to FHIR R4B element `MedicationRequest.dispenseRequest` as `Equivalent`. MedicationRequest.dispenseRequest.validityPeriod (validityPeriod) maps to wider concept MedicationRequest.dispenseRequest.validityPeriod Element `MedicationRequest.dispenseRequest.validityPeriod` is mapped to FHIR R4B element `MedicationRequest.dispenseRequest.validityPeriod` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.dispenseRequest.validityPeriod` do not cover the following types: Period. The mappings for `MedicationRequest.dispenseRequest.validityPeriod` do not cover the following types based on type expansion: end, start. 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 Element `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` is mapped to FHIR R4B element `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` as `SourceIsNarrowerThanTarget`. If displaying "number of authorized fills", add 1 to this number. MedicationRequest.dispenseRequest.quantity (quantity) is equivalent to MedicationRequest.dispenseRequest.quantity Element `MedicationRequest.dispenseRequest.quantity` is mapped to FHIR R4B element `MedicationRequest.dispenseRequest.quantity` as `Equivalent`. MedicationRequest.dispenseRequest.expectedSupplyDuration (expectedSupplyDuration) is equivalent to MedicationRequest.dispenseRequest.expectedSupplyDuration Element `MedicationRequest.dispenseRequest.expectedSupplyDuration` is mapped to FHIR R4B 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.performer (performer) maps to wider concept MedicationRequest.dispenseRequest.performer Element `MedicationRequest.dispenseRequest.performer` is mapped to FHIR R4B element `MedicationRequest.dispenseRequest.performer` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.dispenseRequest.performer` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.dispenseRequest.performer` with unmapped reference targets: Organization. MedicationRequest.substitution (substitution) maps to wider concept MedicationRequest.substitution Element `MedicationRequest.substitution` is mapped to FHIR R4B element `MedicationRequest.substitution` as `Equivalent`. MedicationRequest.substitution.allowed (allowed) is equivalent to MedicationRequest.substitution.allowed[x] Element `MedicationRequest.substitution.allowed` is mapped to FHIR R4B 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 modifer because whether substitution is allow or not cannot be ignored. MedicationRequest.substitution.reason (reason) is equivalent to MedicationRequest.substitution.reason Element `MedicationRequest.substitution.reason` is mapped to FHIR R4B element `MedicationRequest.substitution.reason` as `Equivalent`. MedicationRequest.priorPrescription (priorPrescription) maps to wider concept MedicationRequest.priorPrescription Element `MedicationRequest.priorPrescription` is mapped to FHIR R4B element `MedicationRequest.priorPrescription` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.priorPrescription` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.priorPrescription` with unmapped reference targets: MedicationRequest. MedicationRequest.detectedIssue (detectedIssue) maps to wider concept MedicationRequest.detectedIssue Element `MedicationRequest.detectedIssue` is mapped to FHIR R4B element `MedicationRequest.detectedIssue` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.detectedIssue` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.detectedIssue` with unmapped reference targets: DetectedIssue. MedicationRequest.eventHistory (eventHistory) maps to wider concept MedicationRequest.eventHistory Element `MedicationRequest.eventHistory` is mapped to FHIR R4B element `MedicationRequest.eventHistory` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.eventHistory` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.eventHistory` with unmapped reference targets: Provenance. This may 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|3.0.2 to STU3: meta additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.meta (meta) is equivalent to Extension (STU3: meta additional types) Element `MedicationRequest.meta` is mapped to FHIR R4B element `MedicationRequest.meta` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.meta` do not cover the following types: Meta. The mappings for `MedicationRequest.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|3.0.2 to STU3: text additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.text (text) is equivalent to Extension (STU3: text additional types) Element `MedicationRequest.text` is mapped to FHIR R4B element `MedicationRequest.text` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.text` do not cover the following types: Narrative. The mappings for `MedicationRequest.text` do not cover the following types based on type expansion: div, status. Contained resources do not have 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 in formation is added later. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|3.0.2 to STU3: identifier additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.identifier (identifier) is equivalent to Extension (STU3: identifier additional types) Element `MedicationRequest.identifier` is mapped to FHIR R4B element `MedicationRequest.identifier` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.identifier` do not cover the following types: Identifier. The mappings for `MedicationRequest.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|3.0.2 to STU3: Protocol or definition (new)version: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.definition (definition) is equivalent to Extension (STU3: Protocol or definition (new)) Element `MedicationRequest.definition` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.definition` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|3.0.2 to STU3: groupIdentifier additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.groupIdentifier (groupIdentifier) is equivalent to Extension (STU3: groupIdentifier additional types) Element `MedicationRequest.groupIdentifier` is mapped to FHIR R4B element `MedicationRequest.groupIdentifier` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.groupIdentifier` do not cover the following types: Identifier. The mappings for `MedicationRequest.groupIdentifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|3.0.2 to STU3: Organization agent is acting for (new)version: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.requester.onBehalfOf (onBehalfOf) is equivalent to Extension (STU3: Organization agent is acting for (new)) Element `MedicationRequest.requester.onBehalfOf` has a context of MedicationRequest.requester based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.requester.onBehalfOf` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|3.0.2 to STU3: note additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.note (note) is equivalent to Extension (STU3: note additional types) Element `MedicationRequest.note` is mapped to FHIR R4B element `MedicationRequest.note` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.note` do not cover the following types: Annotation. The mappings for `MedicationRequest.note` do not cover the following types based on type expansion: author[x], text, time. Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|3.0.2 to STU3: dosageInstruction additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.dosageInstruction (dosageInstruction) is equivalent to Extension (STU3: dosageInstruction additional types) Element `MedicationRequest.dosageInstruction` is mapped to FHIR R4B element `MedicationRequest.dosageInstruction` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.dosageInstruction` do not cover the following types: Dosage. The mappings for `MedicationRequest.dosageInstruction` do not cover the following types based on type expansion: additionalInstruction, asNeeded[x], dose[x], maxDosePerAdministration, maxDosePerLifetime, maxDosePerPeriod, method, patientInstruction, rate[x], route, sequence, site, text, timing. 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. Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/MedicationRequest|3.0.2 to STU3: validityPeriod additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MedicationRequest.dispenseRequest.validityPeriod (validityPeriod) is equivalent to Extension (STU3: validityPeriod additional types) Element `MedicationRequest.dispenseRequest.validityPeriod` is mapped to FHIR R4B element `MedicationRequest.dispenseRequest.validityPeriod` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.dispenseRequest.validityPeriod` do not cover the following types: Period. The mappings for `MedicationRequest.dispenseRequest.validityPeriod` do not cover the following types based on type expansion: end, start. 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.
Cross-version mapping for FHIR STU3 MedicationRequest to FHIR R4B MedicationRequest
This ConceptMap represents cross-version mappings for elements from a FHIR STU3 MedicationRequest to FHIR R4B.
Element `MedicationRequest.meta` is mapped to FHIR R4B element `MedicationRequest.meta` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.meta` do not cover the following types: Meta. The mappings for `MedicationRequest.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Element `MedicationRequest.implicitRules` is mapped to FHIR R4B 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
Element `MedicationRequest.language` is mapped to FHIR R4B 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 R4B element `MedicationRequest.text` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.text` do not cover the following types: Narrative. The mappings for `MedicationRequest.text` do not cover the following types based on type expansion: div, status. Contained resources do not have 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 in formation is added later.
Element `MedicationRequest.contained` is mapped to FHIR R4B 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.
Element `MedicationRequest.identifier` is mapped to FHIR R4B element `MedicationRequest.identifier` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.identifier` do not cover the following types: Identifier. The mappings for `MedicationRequest.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Element `MedicationRequest.basedOn` is mapped to FHIR R4B element `MedicationRequest.basedOn` as `RelatedTo`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.basedOn` with unmapped reference targets: CarePlan, MedicationRequest, ProcedureRequest, ReferralRequest.
Element `MedicationRequest.groupIdentifier` is mapped to FHIR R4B element `MedicationRequest.groupIdentifier` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.groupIdentifier` do not cover the following types: Identifier. The mappings for `MedicationRequest.groupIdentifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Element `MedicationRequest.status` is mapped to FHIR R4B element `MedicationRequest.status` as `Equivalent`. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
Element `MedicationRequest.intent` is mapped to FHIR R4B element `MedicationRequest.intent` as `SourceIsNarrowerThanTarget`. The mappings for `MedicationRequest.intent` do not allow expression of the necessary codes, per the bindings on the source and target. 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 R4B element `MedicationRequest.category` as `SourceIsNarrowerThanTarget`.
Element `MedicationRequest.priority` is mapped to FHIR R4B element `MedicationRequest.priority` as `Equivalent`.
Element `MedicationRequest.medication[x]` is mapped to FHIR R4B element `MedicationRequest.medication[x]` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.medication[x]` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.medication[x]` with unmapped reference targets: Medication. Source element `MedicationRequest.medication[x]` has unmapped reference types. While the target element `MedicationRequest.medication[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it. 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 R4B element `MedicationRequest.subject` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.subject` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 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.
Element `MedicationRequest.context` is mapped to FHIR R4B element `MedicationRequest.encounter` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.context` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.context` with unmapped reference targets: Encounter, EpisodeOfCare. SubstanceAdministration->component->EncounterEvent.
Element `MedicationRequest.supportingInformation` is mapped to FHIR R4B element `MedicationRequest.supportingInformation` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.supportingInformation` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.supportingInformation` with unmapped reference targets: Resource.
Element `MedicationRequest.authoredOn` is mapped to FHIR R4B element `MedicationRequest.authoredOn` as `Equivalent`.
Element `MedicationRequest.requester` is mapped to FHIR R4B element `MedicationRequest.requester` as `Equivalent`.
Element `MedicationRequest.requester.agent` is mapped to FHIR R4B element `MedicationRequest.requester` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.requester.agent` with unmapped reference targets: Device, Organization, Patient, Practitioner, RelatedPerson. 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.
Element `MedicationRequest.recorder` is mapped to FHIR R4B element `MedicationRequest.recorder` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.recorder` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.recorder` with unmapped reference targets: Practitioner.
Element `MedicationRequest.reasonCode` is mapped to FHIR R4B element `MedicationRequest.reasonCode` as `Equivalent`. This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonReference.
Element `MedicationRequest.reasonReference` is mapped to FHIR R4B element `MedicationRequest.reasonReference` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.reasonReference` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.reasonReference` with unmapped reference targets: Condition, Observation. This is a reference to a condition or observation that is the reason for the medication order. If only a code exists, use reasonCode.
Element `MedicationRequest.note` is mapped to FHIR R4B element `MedicationRequest.note` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.note` do not cover the following types: Annotation. The mappings for `MedicationRequest.note` do not cover the following types based on type expansion: author[x], text, time.
Element `MedicationRequest.dosageInstruction` is mapped to FHIR R4B element `MedicationRequest.dosageInstruction` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.dosageInstruction` do not cover the following types: Dosage. The mappings for `MedicationRequest.dosageInstruction` do not cover the following types based on type expansion: additionalInstruction, asNeeded[x], dose[x], maxDosePerAdministration, maxDosePerLifetime, maxDosePerPeriod, method, patientInstruction, rate[x], route, sequence, site, text, timing. 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.
Element `MedicationRequest.dispenseRequest` is mapped to FHIR R4B element `MedicationRequest.dispenseRequest` as `Equivalent`.
Element `MedicationRequest.dispenseRequest.validityPeriod` is mapped to FHIR R4B element `MedicationRequest.dispenseRequest.validityPeriod` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.dispenseRequest.validityPeriod` do not cover the following types: Period. The mappings for `MedicationRequest.dispenseRequest.validityPeriod` do not cover the following types based on type expansion: end, start. 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 R4B element `MedicationRequest.dispenseRequest.numberOfRepeatsAllowed` as `SourceIsNarrowerThanTarget`. If displaying "number of authorized fills", add 1 to this number.
Element `MedicationRequest.dispenseRequest.quantity` is mapped to FHIR R4B element `MedicationRequest.dispenseRequest.quantity` as `Equivalent`.
Element `MedicationRequest.dispenseRequest.expectedSupplyDuration` is mapped to FHIR R4B 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.performer` is mapped to FHIR R4B element `MedicationRequest.dispenseRequest.performer` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.dispenseRequest.performer` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.dispenseRequest.performer` with unmapped reference targets: Organization.
Element `MedicationRequest.substitution` is mapped to FHIR R4B element `MedicationRequest.substitution` as `Equivalent`.
Element `MedicationRequest.substitution.allowed` is mapped to FHIR R4B 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 modifer because whether substitution is allow or not cannot be ignored.
Element `MedicationRequest.substitution.reason` is mapped to FHIR R4B element `MedicationRequest.substitution.reason` as `Equivalent`.
Element `MedicationRequest.priorPrescription` is mapped to FHIR R4B element `MedicationRequest.priorPrescription` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.priorPrescription` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.priorPrescription` with unmapped reference targets: MedicationRequest.
Element `MedicationRequest.detectedIssue` is mapped to FHIR R4B element `MedicationRequest.detectedIssue` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.detectedIssue` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.detectedIssue` with unmapped reference targets: DetectedIssue.
Element `MedicationRequest.eventHistory` is mapped to FHIR R4B element `MedicationRequest.eventHistory` as `SourceIsBroaderThanTarget`. The mappings for `MedicationRequest.eventHistory` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `MedicationRequest.eventHistory` with unmapped reference targets: Provenance. This may 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.definition` has a context of MedicationRequest based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.definition` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Element `MedicationRequest.requester.onBehalfOf` has a context of MedicationRequest.requester based on following the parent source element upwards and mapping to `MedicationRequest`. Element `MedicationRequest.requester.onBehalfOf` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).