R5-MedicationRequest-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-MedicationRequest-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: 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…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R5-MedicationRequest-element-map-to-R4
  l: R5-MedicationRequest-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5MedicationRequestElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 MedicationRequest to FHIR R4 MedicationRequest
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:46.8925501-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R5 MedicationRequest to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/MedicationRequest
    l: MedicationRequest
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/MedicationRequest
    l: MedicationRequest
  target version:
    v: 4.0.1
  element:
    code:
      v: MedicationRequest.meta
    display:
      v: meta
    target:
      code:
        v: MedicationRequest.meta
      display:
        v: MedicationRequest.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `MedicationRequest.meta` is mapped to FHIR R4 element `MedicationRequest.meta` as `Equivalent`.
  element:
    code:
      v: MedicationRequest.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: MedicationRequest.implicitRules
      display:
        v: MedicationRequest.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: 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:
    code:
      v: MedicationRequest.language
    display:
      v: language
    target:
      code:
        v: MedicationRequest.language
      display:
        v: MedicationRequest.language
      equivalence:
        v: equivalent
      comment:
        v: 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:
    code:
      v: MedicationRequest.text
    display:
      v: text
    target:
      code:
        v: MedicationRequest.text
      display:
        v: MedicationRequest.text
      equivalence:
        v: equivalent
      comment:
        v: 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:
    code:
      v: MedicationRequest.contained
    display:
      v: contained
    target:
      code:
        v: MedicationRequest.contained
      display:
        v: MedicationRequest.contained
      equivalence:
        v: equivalent
      comment:
        v: 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:
    code:
      v: MedicationRequest.identifier
    display:
      v: identifier
    target:
      code:
        v: MedicationRequest.identifier
      display:
        v: MedicationRequest.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element `MedicationRequest.identifier` is mapped to FHIR R4 element `MedicationRequest.identifier` as `Equivalent`. This is a business identifier, not a resource identifier.
  element:
    code:
      v: MedicationRequest.basedOn
    display:
      v: basedOn
    target:
      code:
        v: MedicationRequest.basedOn
      display:
        v: MedicationRequest.basedOn
      equivalence:
        v: equivalent
      comment:
        v: Element `MedicationRequest.basedOn` is mapped to FHIR R4 element `MedicationRequest.basedOn` as `Equivalent`.
  element:
    code:
      v: MedicationRequest.priorPrescription
    display:
      v: priorPrescription
    target:
      code:
        v: MedicationRequest.priorPrescription
      display:
        v: MedicationRequest.priorPrescription
      equivalence:
        v: equivalent
      comment:
        v: Element `MedicationRequest.priorPrescription` is mapped to FHIR R4 element `MedicationRequest.priorPrescription` as `Equivalent`.

code:
  v: MedicationRequest.groupIdentifier
display:
  v: groupIdentifier
target:
  code:
    v: MedicationRequest.groupIdentifier
  display:
    v: MedicationRequest.groupIdentifier
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.groupIdentifier` is mapped to FHIR R4 element `MedicationRequest.groupIdentifier` as `Equivalent`.

code:
  v: MedicationRequest.status
display:
  v: status
target:
  code:
    v: MedicationRequest.status
  display:
    v: MedicationRequest.status
  equivalence:
    v: wider
  comment:
    v: 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.

code:
  v: MedicationRequest.statusReason
display:
  v: statusReason
target:
  code:
    v: MedicationRequest.statusReason
  display:
    v: MedicationRequest.statusReason
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.intent
display:
  v: intent
target:
  code:
    v: MedicationRequest.intent
  display:
    v: MedicationRequest.intent
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.category
display:
  v: category
target:
  code:
    v: MedicationRequest.category
  display:
    v: MedicationRequest.category
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.priority
display:
  v: priority
target:
  code:
    v: MedicationRequest.priority
  display:
    v: MedicationRequest.priority
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.priority` is mapped to FHIR R4 element `MedicationRequest.priority` as `Equivalent`.

code:
  v: MedicationRequest.doNotPerform
display:
  v: doNotPerform
target:
  code:
    v: MedicationRequest.doNotPerform
  display:
    v: MedicationRequest.doNotPerform
  equivalence:
    v: equivalent
  comment:
    v: 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".

code:
  v: MedicationRequest.medication
display:
  v: medication
target:
  code:
    v: MedicationRequest.medication[x]
  display:
    v: MedicationRequest.medication[x]
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.subject
display:
  v: subject
target:
  code:
    v: MedicationRequest.subject
  display:
    v: MedicationRequest.subject
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.encounter
display:
  v: encounter
target:
  code:
    v: MedicationRequest.encounter
  display:
    v: MedicationRequest.encounter
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.supportingInformation
display:
  v: supportingInformation
target:
  code:
    v: MedicationRequest.supportingInformation
  display:
    v: MedicationRequest.supportingInformation
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.authoredOn
display:
  v: authoredOn
target:
  code:
    v: MedicationRequest.authoredOn
  display:
    v: MedicationRequest.authoredOn
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.authoredOn` is mapped to FHIR R4 element `MedicationRequest.authoredOn` as `Equivalent`.

code:
  v: MedicationRequest.requester
display:
  v: requester
target:
  code:
    v: MedicationRequest.requester
  display:
    v: MedicationRequest.requester
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.requester` is mapped to FHIR R4 element `MedicationRequest.requester` as `Equivalent`.

code:
  v: MedicationRequest.reported
display:
  v: reported
target:
  code:
    v: MedicationRequest.reported[x]
  display:
    v: MedicationRequest.reported[x]
  equivalence:
    v: equivalent
  comment:
    v: 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

code:
  v: MedicationRequest.performerType
display:
  v: performerType
target:
  code:
    v: MedicationRequest.performerType
  display:
    v: MedicationRequest.performerType
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.performer
display:
  v: performer
target:
  code:
    v: MedicationRequest.performer
  display:
    v: MedicationRequest.performer
  equivalence:
    v: wider
  comment:
    v: 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.

code:
  v: MedicationRequest.recorder
display:
  v: recorder
target:
  code:
    v: MedicationRequest.recorder
  display:
    v: MedicationRequest.recorder
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.recorder` is mapped to FHIR R4 element `MedicationRequest.recorder` as `Equivalent`.

code:
  v: MedicationRequest.reason
display:
  v: reason
target:
  code:
    v: MedicationRequest.reasonCode
  display:
    v: MedicationRequest.reasonCode
  equivalence:
    v: relatedto
  comment:
    v: 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.
target:
  code:
    v: MedicationRequest.reasonReference
  display:
    v: MedicationRequest.reasonReference
  equivalence:
    v: relatedto
  comment:
    v: 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.

code:
  v: MedicationRequest.courseOfTherapyType
display:
  v: courseOfTherapyType
target:
  code:
    v: MedicationRequest.courseOfTherapyType
  display:
    v: MedicationRequest.courseOfTherapyType
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.insurance
display:
  v: insurance
target:
  code:
    v: MedicationRequest.insurance
  display:
    v: MedicationRequest.insurance
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.insurance` is mapped to FHIR R4 element `MedicationRequest.insurance` as `Equivalent`.

code:
  v: MedicationRequest.note
display:
  v: note
target:
  code:
    v: MedicationRequest.note
  display:
    v: MedicationRequest.note
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.note` is mapped to FHIR R4 element `MedicationRequest.note` as `Equivalent`.

code:
  v: MedicationRequest.dosageInstruction
display:
  v: dosageInstruction
target:
  code:
    v: MedicationRequest.dosageInstruction
  display:
    v: MedicationRequest.dosageInstruction
  equivalence:
    v: equivalent
  comment:
    v: 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 ac…

code:
  v: MedicationRequest.dispenseRequest
display:
  v: dispenseRequest
target:
  code:
    v: MedicationRequest.dispenseRequest
  display:
    v: MedicationRequest.dispenseRequest
  equivalence:
    v: wider
  comment:
    v: Element `MedicationRequest.dispenseRequest` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest` as `Equivalent`.

code:
  v: MedicationRequest.dispenseRequest.initialFill
display:
  v: initialFill
target:
  code:
    v: MedicationRequest.dispenseRequest.initialFill
  display:
    v: MedicationRequest.dispenseRequest.initialFill
  equivalence:
    v: wider
  comment:
    v: 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.

code:
  v: MedicationRequest.dispenseRequest.initialFill.quantity
display:
  v: quantity
target:
  code:
    v: MedicationRequest.dispenseRequest.initialFill.quantity
  display:
    v: MedicationRequest.dispenseRequest.initialFill.quantity
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.dispenseRequest.initialFill.quantity` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.initialFill.quantity` as `Equivalent`.

code:
  v: MedicationRequest.dispenseRequest.initialFill.duration
display:
  v: duration
target:
  code:
    v: MedicationRequest.dispenseRequest.initialFill.duration
  display:
    v: MedicationRequest.dispenseRequest.initialFill.duration
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.dispenseRequest.initialFill.duration` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.initialFill.duration` as `Equivalent`.

code:
  v: MedicationRequest.dispenseRequest.dispenseInterval
display:
  v: dispenseInterval
target:
  code:
    v: MedicationRequest.dispenseRequest.dispenseInterval
  display:
    v: MedicationRequest.dispenseRequest.dispenseInterval
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.dispenseRequest.dispenseInterval` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.dispenseInterval` as `Equivalent`.

code:
  v: MedicationRequest.dispenseRequest.validityPeriod
display:
  v: validityPeriod
target:
  code:
    v: MedicationRequest.dispenseRequest.validityPeriod
  display:
    v: MedicationRequest.dispenseRequest.validityPeriod
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.dispenseRequest.numberOfRepeatsAllowed
display:
  v: numberOfRepeatsAllowed
target:
  code:
    v: MedicationRequest.dispenseRequest.numberOfRepeatsAllowed
  display:
    v: MedicationRequest.dispenseRequest.numberOfRepeatsAllowed
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.dispenseRequest.quantity
display:
  v: quantity
target:
  code:
    v: MedicationRequest.dispenseRequest.quantity
  display:
    v: MedicationRequest.dispenseRequest.quantity
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.dispenseRequest.quantity` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.quantity` as `Equivalent`.

code:
  v: MedicationRequest.dispenseRequest.expectedSupplyDuration
display:
  v: expectedSupplyDuration
target:
  code:
    v: MedicationRequest.dispenseRequest.expectedSupplyDuration
  display:
    v: MedicationRequest.dispenseRequest.expectedSupplyDuration
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.dispenseRequest.dispenser
display:
  v: dispenser
target:
  code:
    v: MedicationRequest.dispenseRequest.performer
  display:
    v: MedicationRequest.dispenseRequest.performer
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.dispenseRequest.dispenser` is mapped to FHIR R4 element `MedicationRequest.dispenseRequest.performer` as `Equivalent`.

code:
  v: MedicationRequest.substitution
display:
  v: substitution
target:
  code:
    v: MedicationRequest.substitution
  display:
    v: MedicationRequest.substitution
  equivalence:
    v: wider
  comment:
    v: Element `MedicationRequest.substitution` is mapped to FHIR R4 element `MedicationRequest.substitution` as `Equivalent`.

code:
  v: MedicationRequest.substitution.allowed[x]
display:
  v: allowed[x]
target:
  code:
    v: MedicationRequest.substitution.allowed[x]
  display:
    v: MedicationRequest.substitution.allowed[x]
  equivalence:
    v: equivalent
  comment:
    v: 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.

code:
  v: MedicationRequest.substitution.reason
display:
  v: reason
target:
  code:
    v: MedicationRequest.substitution.reason
  display:
    v: MedicationRequest.substitution.reason
  equivalence:
    v: equivalent
  comment:
    v: Element `MedicationRequest.substitution.reason` is mapped to FHIR R4 element `MedicationRequest.substitution.reason` as `Equivalent`.

code:
  v: MedicationRequest.eventHistory
display:
  v: eventHistory
target:
  code:
    v: MedicationRequest.eventHistory
  display:
    v: MedicationRequest.eventHistory
  equivalence:
    v: equivalent
  comment:
    v: 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.).

source:
  v: http://hl7.org/fhir/StructureDefinition/MedicationRequest
  l: MedicationRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-MedicationRequest.status
  l: extension-MedicationRequest.status
target version:
  v: 0.1.0
element:
  code:
    v: MedicationRequest.status
  display:
    v: status
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/MedicationRequest
  l: MedicationRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-MedicationRequest.statusChanged
  l: extension-MedicationRequest.statusChanged
target version:
  v: 0.1.0
element:
  code:
    v: MedicationRequest.statusChanged
  display:
    v: statusChanged
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/MedicationRequest
  l: MedicationRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-MedicationRequest.informationSource
  l: extension-MedicationRequest.informationSource
target version:
  v: 0.1.0
element:
  code:
    v: MedicationRequest.informationSource
  display:
    v: informationSource
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/MedicationRequest
  l: MedicationRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-MedicationRequest.device
  l: extension-MedicationRequest.device
target version:
  v: 0.1.0
element:
  code:
    v: MedicationRequest.device
  display:
    v: device
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/MedicationRequest
  l: MedicationRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-MedicationRequest.renderedDosageInstruction
  l: extension-MedicationRequest.renderedDosageInstruction
target version:
  v: 0.1.0
element:
  code:
    v: MedicationRequest.renderedDosageInstruction
  display:
    v: renderedDosageInstruction
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/MedicationRequest
  l: MedicationRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-MedicationRequest.effectiveDosePeriod
  l: extension-MedicationRequest.effectiveDosePeriod
target version:
  v: 0.1.0
element:
  code:
    v: MedicationRequest.effectiveDosePeriod
  display:
    v: effectiveDosePeriod
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/MedicationRequest
  l: MedicationRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-MedicationRequest.dispenseRequest.dispenserInstruction
  l: extension-MedicationRequest.dispenseRequest.dispenserInstruction
target version:
  v: 0.1.0
element:
  code:
    v: MedicationRequest.dispenseRequest.dispenserInstruction
  display:
    v: dispenserInstruction
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).

source:
  v: http://hl7.org/fhir/StructureDefinition/MedicationRequest
  l: MedicationRequest
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-MedicationRequest.dispenseRequest.doseAdministrationAid
  l: extension-MedicationRequest.dispenseRequest.doseAdministrationAid
target version:
  v: 0.1.0
element:
  code:
    v: MedicationRequest.dispenseRequest.doseAdministrationAid
  display:
    v: doseAdministrationAid
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: 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).