R4-NutritionOrder-element-map-to-R5
type: ConceptMap
node role: treeRoot
id:
  v: R4-NutritionOrder-element-map-to-R5
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R4-NutritionOrder-element-map-to-R5 Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/5.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/NutritionOrder|4.0.1 to NutritionOrderversion: 5.0.0) Source Code Relationship Target Code Comment NutritionOrder.meta (meta) is equivalent to NutritionOrder.meta Element `NutritionOrder.meta` is mapped to FHIR R5 element `NutritionOrder.meta` as `Equivalent`. NutritionOrder.implicitRules (implicitRules) is equivalent to NutritionOrder.implicitRules Element `NutritionOrder.implicitRules` is mapped to FHIR R5 element `NutritionOrder.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 it's narrative along with other profiles, value sets, etc. NutritionOrder.language (language) is equivalent to NutritionOrder.language Element `NutritionOrder.language` is mapped to FHIR R5 element `NutritionOrder.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 HTM…
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-r4.r5
        l: hl7.fhir.uv.xver-r4.r5
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-r4.r5
        l: hl7.fhir.uv.xver-r4.r5
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R4-NutritionOrder-element-map-to-R5
  l: R4-NutritionOrder-element-map-to-R5
version:
  v: 0.1.0
name:
  v: R4NutritionOrderElementMapToR5
title:
  v: Cross-version mapping for FHIR R4 NutritionOrder to FHIR R5 NutritionOrder
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:37.211383-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 R4 NutritionOrder to FHIR R5.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source scope: Canonical
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
target scope: Uri
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/NutritionOrder|4.0.1
    l: http://hl7.org/fhir/StructureDefinition/NutritionOrder
  target:
    v: http://hl7.org/fhir/StructureDefinition/NutritionOrder|5.0.0
    l: http://hl7.org/fhir/StructureDefinition/NutritionOrder
  element:
    code:
      v: NutritionOrder.meta
    display:
      v: meta
    target:
      code:
        v: NutritionOrder.meta
      display:
        v: NutritionOrder.meta
      relationship:
        v: equivalent
      comment:
        v: Element `NutritionOrder.meta` is mapped to FHIR R5 element `NutritionOrder.meta` as `Equivalent`.
  element:
    code:
      v: NutritionOrder.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: NutritionOrder.implicitRules
      display:
        v: NutritionOrder.implicitRules
      relationship:
        v: equivalent
      comment:
        v: Element `NutritionOrder.implicitRules` is mapped to FHIR R5 element `NutritionOrder.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 it's narrative along with other profiles, value sets, etc.
  element:
    code:
      v: NutritionOrder.language
    display:
      v: language
    target:
      code:
        v: NutritionOrder.language
      display:
        v: NutritionOrder.language
      relationship:
        v: equivalent
      comment:
        v: Element `NutritionOrder.language` is mapped to FHIR R5 element `NutritionOrder.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: NutritionOrder.text
    display:
      v: text
    target:
      code:
        v: NutritionOrder.text
      display:
        v: NutritionOrder.text
      relationship:
        v: equivalent
      comment:
        v: Element `NutritionOrder.text` is mapped to FHIR R5 element `NutritionOrder.text` as `Equivalent`. 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 information is added later.
  element:
    code:
      v: NutritionOrder.contained
    display:
      v: contained
    target:
      code:
        v: NutritionOrder.contained
      display:
        v: NutritionOrder.contained
      relationship:
        v: equivalent
      comment:
        v: Element `NutritionOrder.contained` is mapped to FHIR R5 element `NutritionOrder.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: NutritionOrder.identifier
    display:
      v: identifier
    target:
      code:
        v: NutritionOrder.identifier
      display:
        v: NutritionOrder.identifier
      relationship:
        v: equivalent
      comment:
        v: Element `NutritionOrder.identifier` is mapped to FHIR R5 element `NutritionOrder.identifier` as `Equivalent`. The Identifier.type element can be to indicate filler vs. placer if needed. This is explained in further detail [here](https://hl7.org/fhir/servic.html#notes).
  element:
    code:
      v: NutritionOrder.instantiatesCanonical
    display:
      v: instantiatesCanonical
    target:
      code:
        v: NutritionOrder.instantiatesCanonical
      display:
        v: NutritionOrder.instantiatesCanonical
      relationship:
        v: equivalent
      comment:
        v: Element `NutritionOrder.instantiatesCanonical` is mapped to FHIR R5 element `NutritionOrder.instantiatesCanonical` as `Equivalent`. Note: This is a business identifier, not a resource identifier (see [discussion](https://hl7.org/fhir/resource.htm#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.
  element:
    code:
      v: NutritionOrder.instantiatesUri
    display:
      v: instantiatesUri
    target:
      code:
        v: NutritionOrder.instantiatesUri
      display:
        v: NutritionOrder.instantiatesUri
      relationship:
        v: equivalent
      comment:
        v: Element `NutritionOrder.instantiatesUri` is mapped to FHIR R5 element `NutritionOrder.instantiatesUri` as `Equivalent`. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
  element:
    code:
      v: NutritionOrder.instantiates

v: instantiates

code:
  v: NutritionOrder.instantiates
display:
  v: NutritionOrder.instantiates
relationship:
  v: equivalent
comment:
  v: Element `NutritionOrder.instantiates` is mapped to FHIR R5 element `NutritionOrder.instantiates` as `Equivalent`.

code:
  v: NutritionOrder.status
display:
  v: status
target:
  code:
    v: NutritionOrder.status
  display:
    v: NutritionOrder.status
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.status` is mapped to FHIR R5 element `NutritionOrder.status` as `Equivalent`. Typically the system placing the order sets the status to "requested". Thereafter, the order is maintained by the receiver that updates the status as the request is handled. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

code:
  v: NutritionOrder.intent
display:
  v: intent
target:
  code:
    v: NutritionOrder.intent
  display:
    v: NutritionOrder.intent
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.intent` is mapped to FHIR R5 element `NutritionOrder.intent` as `Equivalent`. When resources map to this element, they are free to define as many codes as necessary to cover their space and will map to "proposal, plan or order". Can have multiple codes that map to one of these. E.g. "original order", "encoded order", "reflex order" would all map to "order". Expectation is that the set of codes is mutually exclusive or a strict all-encompassing hierarchy.

code:
  v: NutritionOrder.patient
display:
  v: patient
target:
  code:
    v: NutritionOrder.subject
  display:
    v: NutritionOrder.subject
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.patient` is mapped to FHIR R5 element `NutritionOrder.subject` as `Equivalent`.

code:
  v: NutritionOrder.encounter
display:
  v: encounter
target:
  code:
    v: NutritionOrder.encounter
  display:
    v: NutritionOrder.encounter
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.encounter` is mapped to FHIR R5 element `NutritionOrder.encounter` as `Equivalent`.

code:
  v: NutritionOrder.dateTime
display:
  v: dateTime
target:
  code:
    v: NutritionOrder.dateTime
  display:
    v: NutritionOrder.dateTime
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.dateTime` is mapped to FHIR R5 element `NutritionOrder.dateTime` as `Equivalent`.

code:
  v: NutritionOrder.orderer
display:
  v: orderer
target:
  code:
    v: NutritionOrder.orderer
  display:
    v: NutritionOrder.orderer
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.orderer` is mapped to FHIR R5 element `NutritionOrder.orderer` as `Equivalent`.

code:
  v: NutritionOrder.allergyIntolerance
display:
  v: allergyIntolerance
target:
  code:
    v: NutritionOrder.allergyIntolerance
  display:
    v: NutritionOrder.allergyIntolerance
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.allergyIntolerance` is mapped to FHIR R5 element `NutritionOrder.allergyIntolerance` as `Equivalent`. Information on a patient's food allergies and intolerances to inform healthcare personnel about the type of foods that the patient shouldn't receive or consume.

code:
  v: NutritionOrder.foodPreferenceModifier
display:
  v: foodPreferenceModifier
target:
  code:
    v: NutritionOrder.foodPreferenceModifier
  display:
    v: NutritionOrder.foodPreferenceModifier
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.foodPreferenceModifier` is mapped to FHIR R5 element `NutritionOrder.foodPreferenceModifier` as `Equivalent`. Information on a patient's food preferences that inform healthcare personnel about the food that the patient should receive or consume.

code:
  v: NutritionOrder.excludeFoodModifier
display:
  v: excludeFoodModifier
target:
  code:
    v: NutritionOrder.excludeFoodModifier
  display:
    v: NutritionOrder.excludeFoodModifier
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.excludeFoodModifier` is mapped to FHIR R5 element `NutritionOrder.excludeFoodModifier` as `Equivalent`. Information on a patient's food allergies, intolerances and preferences to inform healthcare personnel about the type of foods that the patient shouldn't receive or consume.

code:
  v: NutritionOrder.oralDiet
display:
  v: oralDiet
target:
  code:
    v: NutritionOrder.oralDiet
  display:
    v: NutritionOrder.oralDiet
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `NutritionOrder.oralDiet` is mapped to FHIR R5 element `NutritionOrder.oralDiet` as `Equivalent`.

code:
  v: NutritionOrder.oralDiet.type
display:
  v: type
target:
  code:
    v: NutritionOrder.oralDiet.type
  display:
    v: NutritionOrder.oralDiet.type
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.oralDiet.type` is mapped to FHIR R5 element `NutritionOrder.oralDiet.type` as `Equivalent`.

code:
  v: NutritionOrder.oralDiet.schedule
display:
  v: schedule
target:
  code:
    v: NutritionOrder.oralDiet.schedule
  display:
    v: NutritionOrder.oralDiet.schedule
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `NutritionOrder.oralDiet.schedule` is mapped to FHIR R5 element `NutritionOrder.oralDiet.schedule` as `SourceIsBroaderThanTarget`. The mappings for `NutritionOrder.oralDiet.schedule` do not cover the following types: Timing. The mappings for `NutritionOrder.oralDiet.schedule` do not cover the following types based on type expansion: bounds[x], code, count, countMax, dayOfWeek, duration, durationMax, durationUnit, event, frequency, frequencyMax, offset, period, periodMax, periodUnit, repeat, timeOfDay, when.

code:
  v: NutritionOrder.oralDiet.nutrient
display:
  v: nutrient
target:
  code:
    v: NutritionOrder.oralDiet.nutrient
  display:
    v: NutritionOrder.oralDiet.nutrient
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `NutritionOrder.oralDiet.nutrient` is mapped to FHIR R5 element `NutritionOrder.oralDiet.nutrient` as `Equivalent`.

code:
  v: NutritionOrder.oralDiet.nutrient.modifier
display:
  v: modifier
target:
  code:
    v: NutritionOrder.oralDiet.nutrient.modifier
  display:
    v: NutritionOrder.oralDiet.nutrient.modifier
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.oralDiet.nutrient.modifier` is mapped to FHIR R5 element `NutritionOrder.oralDiet.nutrient.modifier` as `Equivalent`.

code:
  v: NutritionOrder.oralDiet.nutrient.amount
display:
  v: amount
target:
  code:
    v: NutritionOrder.oralDiet.nutrient.amount
  display:
    v: NutritionOrder.oralDiet.nutrient.amount
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.oralDiet.nutrient.amount` is mapped to FHIR R5 element `NutritionOrder.oralDiet.nutrient.amount` as `Equivalent`.

code:
  v: NutritionOrder.oralDiet.texture
display:
  v: texture
target:
  code:
    v: NutritionOrder.oralDiet.texture
  display:
    v: NutritionOrder.oralDiet.texture
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `NutritionOrder.oralDiet.texture` is mapped to FHIR R5 element `NutritionOrder.oralDiet.texture` as `Equivalent`.

code:
  v: NutritionOrder.oralDiet.texture.modifier
display:
  v: modifier
target:
  code:
    v: NutritionOrder.oralDiet.texture.modifier
  display:
    v: NutritionOrder.oralDiet.texture.modifier
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.oralDiet.texture.modifier` is mapped to FHIR R5 element `NutritionOrder.oralDiet.texture.modifier` as `Equivalent`. Coupled with the foodType (Meat).

code:
  v: NutritionOrder.oralDiet.texture.foodType
display:
  v: foodType
target:
  code:
    v: NutritionOrder.oralDiet.texture.foodType
  display:
    v: NutritionOrder.oralDiet.texture.foodType
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.oralDiet.texture.foodType` is mapped to FHIR R5 element `NutritionOrder.oralDiet.texture.foodType` as `Equivalent`. Coupled with the `texture.modifier`; could be (All Foods).

code:
  v: NutritionOrder.oralDiet.fluidConsistencyType
display:
  v: fluidConsistencyType
target:
  code:
    v: NutritionOrder.oralDiet.fluidConsistencyType
  display:
    v: NutritionOrder.oralDiet.fluidConsistencyType
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.oralDiet.fluidConsistencyType` is mapped to FHIR R5 element `NutritionOrder.oralDiet.fluidConsistencyType` as `Equivalent`.

code:
  v: NutritionOrder.oralDiet.instruction
display:
  v: instruction
target:
  code:
    v: NutritionOrder.oralDiet.instruction
  display:
    v: NutritionOrder.oralDiet.instruction
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.oralDiet.instruction` is mapped to FHIR R5 element `NutritionOrder.oralDiet.instruction` as `Equivalent`. Free text dosage instructions can be used for cases where the instructions are too complex to code.

code:
  v: NutritionOrder.supplement
display:
  v: supplement
target:
  code:
    v: NutritionOrder.supplement
  display:
    v: NutritionOrder.supplement
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `NutritionOrder.supplement` is mapped to FHIR R5 element `NutritionOrder.supplement` as `Equivalent`.

code:
  v: NutritionOrder.supplement.type
display:
  v: type
target:
  code:
    v: NutritionOrder.supplement.type
  display:
    v: NutritionOrder.supplement.type
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.supplement.type` is mapped to FHIR R5 element `NutritionOrder.supplement.type` as `SourceIsNarrowerThanTarget`.

code:
  v: NutritionOrder.supplement.productName
display:
  v: productName
target:
  code:
    v: NutritionOrder.supplement.productName
  display:
    v: NutritionOrder.supplement.productName
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.supplement.productName` is mapped to FHIR R5 element `NutritionOrder.supplement.productName` as `Equivalent`.

code:
  v: NutritionOrder.supplement.schedule
display:
  v: schedule
target:
  code:
    v: NutritionOrder.supplement.schedule
  display:
    v: NutritionOrder.supplement.schedule
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `NutritionOrder.supplement.schedule` is mapped to FHIR R5 element `NutritionOrder.supplement.schedule` as `SourceIsBroaderThanTarget`. The mappings for `NutritionOrder.supplement.schedule` do not cover the following types: Timing. The mappings for `NutritionOrder.supplement.schedule` do not cover the following types based on type expansion: bounds[x], code, count, countMax, dayOfWeek, duration, durationMax, durationUnit, event, frequency, frequencyMax, offset, period, periodMax, periodUnit, repeat, timeOfDay, when.

code:
  v: NutritionOrder.supplement.quantity
display:
  v: quantity
target:
  code:
    v: NutritionOrder.supplement.quantity
  display:
    v: NutritionOrder.supplement.quantity
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.supplement.quantity` is mapped to FHIR R5 element `NutritionOrder.supplement.quantity` as `Equivalent`.

code:
  v: NutritionOrder.supplement.instruction
display:
  v: instruction
target:
  code:
    v: NutritionOrder.supplement.instruction
  display:
    v: NutritionOrder.supplement.instruction
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.supplement.instruction` is mapped to FHIR R5 element `NutritionOrder.supplement.instruction` as `Equivalent`. Free text dosage instructions can be used for cases where the instructions are too complex to code.

code:
  v: NutritionOrder.enteralFormula
display:
  v: enteralFormula
target:
  code:
    v: NutritionOrder.enteralFormula
  display:
    v: NutritionOrder.enteralFormula
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `NutritionOrder.enteralFormula` is mapped to FHIR R5 element `NutritionOrder.enteralFormula` as `Equivalent`.

code:
  v: NutritionOrder.enteralFormula.baseFormulaType
display:
  v: baseFormulaType
target:
  code:
    v: NutritionOrder.enteralFormula.baseFormulaType
  display:
    v: NutritionOrder.enteralFormula.baseFormulaType
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.enteralFormula.baseFormulaType` is mapped to FHIR R5 element `NutritionOrder.enteralFormula.baseFormulaType` as `SourceIsNarrowerThanTarget`.

code:
  v: NutritionOrder.enteralFormula.baseFormulaProductName
display:
  v: baseFormulaProductName
target:
  code:
    v: NutritionOrder.enteralFormula.baseFormulaProductName
  display:
    v: NutritionOrder.enteralFormula.baseFormulaProductName
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.enteralFormula.baseFormulaProductName` is mapped to FHIR R5 element `NutritionOrder.enteralFormula.baseFormulaProductName` as `Equivalent`.

code:
  v: NutritionOrder.enteralFormula.additiveProductName
display:
  v: additiveProductName
target:
  code:
    v: NutritionOrder.enteralFormula.additive.productName
  display:
    v: NutritionOrder.enteralFormula.additive.productName
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.enteralFormula.additiveProductName` is mapped to FHIR R5 element `NutritionOrder.enteralFormula.additive.productName` as `Equivalent`.

code:
  v: NutritionOrder.enteralFormula.caloricDensity
display:
  v: caloricDensity
target:
  code:
    v: NutritionOrder.enteralFormula.caloricDensity
  display:
    v: NutritionOrder.enteralFormula.caloricDensity
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.enteralFormula.caloricDensity` is mapped to FHIR R5 element `NutritionOrder.enteralFormula.caloricDensity` as `Equivalent`.

code:
  v: NutritionOrder.enteralFormula.routeofAdministration
display:
  v: routeofAdministration
target:
  code:
    v: NutritionOrder.enteralFormula.routeOfAdministration
  display:
    v: NutritionOrder.enteralFormula.routeOfAdministration
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.enteralFormula.routeofAdministration` is mapped to FHIR R5 element `NutritionOrder.enteralFormula.routeOfAdministration` as `Equivalent`.

code:
  v: NutritionOrder.enteralFormula.administration
display:
  v: administration
target:
  code:
    v: NutritionOrder.enteralFormula.administration
  display:
    v: NutritionOrder.enteralFormula.administration
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `NutritionOrder.enteralFormula.administration` is mapped to FHIR R5 element `NutritionOrder.enteralFormula.administration` as `Equivalent`. See implementation notes below for further discussion on how to order continuous vs bolus enteral feeding using this resource.

code:
  v: NutritionOrder.enteralFormula.administration.schedule
display:
  v: schedule
target:
  code:
    v: NutritionOrder.enteralFormula.administration.schedule
  display:
    v: NutritionOrder.enteralFormula.administration.schedule
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.enteralFormula.administration.schedule` is mapped to FHIR R5 element `NutritionOrder.enteralFormula.administration.schedule` as `Equivalent`.

code:
  v: NutritionOrder.enteralFormula.administration.quantity
display:
  v: quantity
target:
  code:
    v: NutritionOrder.enteralFormula.administration.quantity
  display:
    v: NutritionOrder.enteralFormula.administration.quantity
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.enteralFormula.administration.quantity` is mapped to FHIR R5 element `NutritionOrder.enteralFormula.administration.quantity` as `Equivalent`.

code:
  v: NutritionOrder.enteralFormula.administration.rate[x]
display:
  v: rate[x]
target:
  code:
    v: NutritionOrder.enteralFormula.administration.rate[x]
  display:
    v: NutritionOrder.enteralFormula.administration.rate[x]
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.enteralFormula.administration.rate[x]` is mapped to FHIR R5 element `NutritionOrder.enteralFormula.administration.rate[x]` as `Equivalent`. The target context `NutritionOrder.enteralFormula.administration.rate[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `NutritionOrder.enteralFormula.administration`. Ratio is used when the quantity value in the denominator is not "1", otherwise use Quantity. For example, the Ratio datatype is used for "200 mL/4 hrs" versus the Quantity datatype for "50 mL/hr".

code:
  v: NutritionOrder.enteralFormula.maxVolumeToDeliver
display:
  v: maxVolumeToDeliver
target:
  code:
    v: NutritionOrder.enteralFormula.maxVolumeToDeliver
  display:
    v: NutritionOrder.enteralFormula.maxVolumeToDeliver
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.enteralFormula.maxVolumeToDeliver` is mapped to FHIR R5 element `NutritionOrder.enteralFormula.maxVolumeToDeliver` as `Equivalent`.

code:
  v: NutritionOrder.enteralFormula.administrationInstruction
display:
  v: administrationInstruction
target:
  code:
    v: NutritionOrder.enteralFormula.administrationInstruction
  display:
    v: NutritionOrder.enteralFormula.administrationInstruction
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.enteralFormula.administrationInstruction` is mapped to FHIR R5 element `NutritionOrder.enteralFormula.administrationInstruction` as `Equivalent`. Free text dosage instructions can be used for cases where the instructions are too complex to code.

code:
  v: NutritionOrder.note
display:
  v: note
target:
  code:
    v: NutritionOrder.note
  display:
    v: NutritionOrder.note
  relationship:
    v: equivalent
  comment:
    v: Element `NutritionOrder.note` is mapped to FHIR R5 element `NutritionOrder.note` as `Equivalent`. This element SHALL NOT be used to supply free text instructions for the diet which are represented in the `.oralDiet.instruction`, `supplement.instruction`, or `enteralFormula.administrationInstruction` elements.

source:
  v: http://hl7.org/fhir/StructureDefinition/NutritionOrder|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/NutritionOrder
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-NutritionOrder.oralDiet.schedule|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-NutritionOrder.oralDiet.schedule
element:
  code:
    v: NutritionOrder.oralDiet.schedule
  display:
    v: schedule
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `NutritionOrder.oralDiet.schedule` is mapped to FHIR R5 element `NutritionOrder.oralDiet.schedule` as `SourceIsBroaderThanTarget`. The mappings for `NutritionOrder.oralDiet.schedule` do not cover the following types: Timing. The mappings for `NutritionOrder.oralDiet.schedule` do not cover the following types based on type expansion: bounds[x], code, count, countMax, dayOfWeek, duration, durationMax, durationUnit, event, frequency, frequencyMax, offset, period, periodMax, periodUnit, repeat, timeOfDay, when.

source:
  v: http://hl7.org/fhir/StructureDefinition/NutritionOrder|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/NutritionOrder
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-NutritionOrder.supplement.schedule|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-NutritionOrder.supplement.schedule
element:
  code:
    v: NutritionOrder.supplement.schedule
  display:
    v: schedule
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `NutritionOrder.supplement.schedule` is mapped to FHIR R5 element `NutritionOrder.supplement.schedule` as `SourceIsBroaderThanTarget`. The mappings for `NutritionOrder.supplement.schedule` do not cover the following types: Timing. The mappings for `NutritionOrder.supplement.schedule` do not cover the following types based on type expansion: bounds[x], code, count, countMax, dayOfWeek, duration, durationMax, durationUnit, event, frequency, frequencyMax, offset, period, periodMax, periodUnit, repeat, timeOfDay, when.

source:
  v: http://hl7.org/fhir/StructureDefinition/NutritionOrder|4.0.1
  l: http://hl7.org/fhir/StructureDefinition/NutritionOrder
target:
  v: http://hl7.org/fhir/4.0/StructureDefinition/extension-NutritionOrder.enteralFormula.additiveType|0.1.0
  l: http://hl7.org/fhir/4.0/StructureDefinition/extension-NutritionOrder.enteralFormula.additiveType
element:
  code:
    v: NutritionOrder.enteralFormula.additiveType
  display:
    v: additiveType
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `NutritionOrder.enteralFormula.additiveType` has a context of NutritionOrder.enteralFormula based on following the parent source element upwards and mapping to `NutritionOrder`. Element `NutritionOrder.enteralFormula.additiveType` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).