R5-DeviceDefinition-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-DeviceDefinition-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R5-DeviceDefinition-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/DeviceDefinition|5.0.0 to DeviceDefinitionversion: 4.0.1) Source Concept Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 Codes from DeviceDefinition DeviceDefinition.meta meta is equivalent to DeviceDefinition.meta DeviceDefinition.meta Element `DeviceDefinition.meta` is mapped to FHIR R4 element `DeviceDefinition.meta` as `Equivalent`. DeviceDefinition.implicitRules implicitRules is equivalent to DeviceDefinition.implicitRules DeviceDefinition.implicitRules Element `DeviceDefinition.implicitRules` is mapped to FHIR R4 element `DeviceDefinition.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. DeviceDefinition.language language is equivalent to DeviceDefinition.language DeviceDefinition.language Element `DeviceDefinition.language` is mapped to FHIR R4 element `DeviceDefinition.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 conten…
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-DeviceDefinition-element-map-to-R4
  l: R5-DeviceDefinition-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5DeviceDefinitionElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 DeviceDefinition to FHIR R4 DeviceDefinition
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:44.9668049-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 DeviceDefinition 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/DeviceDefinition
    l: DeviceDefinition
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/DeviceDefinition
    l: DeviceDefinition
  target version:
    v: 4.0.1
  element:
    code:
      v: DeviceDefinition.meta
    display:
      v: meta
    target:
      code:
        v: DeviceDefinition.meta
      display:
        v: DeviceDefinition.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `DeviceDefinition.meta` is mapped to FHIR R4 element `DeviceDefinition.meta` as `Equivalent`.
  element:
    code:
      v: DeviceDefinition.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: DeviceDefinition.implicitRules
      display:
        v: DeviceDefinition.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element `DeviceDefinition.implicitRules` is mapped to FHIR R4 element `DeviceDefinition.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: DeviceDefinition.language
    display:
      v: language
    target:
      code:
        v: DeviceDefinition.language
      display:
        v: DeviceDefinition.language
      equivalence:
        v: equivalent
      comment:
        v: Element `DeviceDefinition.language` is mapped to FHIR R4 element `DeviceDefinition.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: DeviceDefinition.text
    display:
      v: text
    target:
      code:
        v: DeviceDefinition.text
      display:
        v: DeviceDefinition.text
      equivalence:
        v: equivalent
      comment:
        v: Element `DeviceDefinition.text` is mapped to FHIR R4 element `DeviceDefinition.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: DeviceDefinition.contained
    display:
      v: contained
    target:
      code:
        v: DeviceDefinition.contained
      display:
        v: DeviceDefinition.contained
      equivalence:
        v: equivalent
      comment:
        v: Element `DeviceDefinition.contained` is mapped to FHIR R4 element `DeviceDefinition.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: DeviceDefinition.identifier
    display:
      v: identifier
    target:
      code:
        v: DeviceDefinition.identifier
      display:
        v: DeviceDefinition.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element `DeviceDefinition.identifier` is mapped to FHIR R4 element `DeviceDefinition.identifier` as `Equivalent`.
  element:
    code:
      v: DeviceDefinition.udiDeviceIdentifier
    display:
      v: udiDeviceIdentifier
    target:
      code:
        v: DeviceDefinition.udiDeviceIdentifier
      display:
        v: DeviceDefinition.udiDeviceIdentifier
      equivalence:
        v: wider
      comment:
        v: Element `DeviceDefinition.udiDeviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier` as `Equivalent`.
  element:
    code:
      v: DeviceDefinition.udiDeviceIdentifier.deviceIdentifier
    display:
      v: deviceIdentifier
    target:
      code:
        v: DeviceDefinition.udiDeviceIdentifier.deviceIdentifier
      display:
        v: DeviceDefinition.udiDeviceIdentifier.deviceIdentifier
      equivalence:
        v: equivalent
      comment:
        v: Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` as `Equivalent`.

code:
  v: DeviceDefinition.udiDeviceIdentifier.issuer
display:
  v: issuer
target:
  code:
    v: DeviceDefinition.udiDeviceIdentifier.issuer
  display:
    v: DeviceDefinition.udiDeviceIdentifier.issuer
  equivalence:
    v: equivalent
  comment:
    v: Element `DeviceDefinition.udiDeviceIdentifier.issuer` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.issuer` as `Equivalent`.

code:
  v: DeviceDefinition.udiDeviceIdentifier.jurisdiction
display:
  v: jurisdiction
target:
  code:
    v: DeviceDefinition.udiDeviceIdentifier.jurisdiction
  display:
    v: DeviceDefinition.udiDeviceIdentifier.jurisdiction
  equivalence:
    v: equivalent
  comment:
    v: Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` as `Equivalent`.

code:
  v: DeviceDefinition.manufacturer
display:
  v: manufacturer
target:
  code:
    v: DeviceDefinition.manufacturer[x]
  display:
    v: DeviceDefinition.manufacturer[x]
  equivalence:
    v: equivalent
  comment:
    v: Element `DeviceDefinition.manufacturer` is mapped to FHIR R4 element `DeviceDefinition.manufacturer[x]` as `Equivalent`. The target context `DeviceDefinition.manufacturer[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceDefinition`.

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

code:
  v: DeviceDefinition.deviceName.name
display:
  v: name
target:
  code:
    v: DeviceDefinition.deviceName.name
  display:
    v: DeviceDefinition.deviceName.name
  equivalence:
    v: equivalent
  comment:
    v: Element `DeviceDefinition.deviceName.name` is mapped to FHIR R4 element `DeviceDefinition.deviceName.name` as `Equivalent`.

code:
  v: DeviceDefinition.deviceName.type
display:
  v: type
target:
  code:
    v: DeviceDefinition.deviceName.type
  display:
    v: DeviceDefinition.deviceName.type
  equivalence:
    v: equivalent
  comment:
    v: Element `DeviceDefinition.deviceName.type` is mapped to FHIR R4 element `DeviceDefinition.deviceName.type` as `SourceIsNarrowerThanTarget`. The mappings for `DeviceDefinition.deviceName.type` do not allow expression of the necessary codes, per the bindings on the source and target.

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

code:
  v: DeviceDefinition.conformsTo
display:
  v: conformsTo
target:
  code:
    v: DeviceDefinition.specialization
  display:
    v: DeviceDefinition.specialization
  equivalence:
    v: wider
  comment:
    v: Element `DeviceDefinition.conformsTo` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `Equivalent`. An externally-defined extension that has been mapped as the representation of FHIR R5 element `DeviceDefinition.conformsTo`: `http://hl7.org/fhir/StructureDefinition/device-conformsTo`.

code:
  v: DeviceDefinition.conformsTo.category
display:
  v: category
target:
  code:
    v: DeviceDefinition.specialization
  display:
    v: DeviceDefinition.specialization
  equivalence:
    v: narrower
  comment:
    v: Element `DeviceDefinition.conformsTo.category` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `SourceIsNarrowerThanTarget`.

code:
  v: DeviceDefinition.conformsTo.specification
display:
  v: specification
target:
  code:
    v: DeviceDefinition.specialization
  display:
    v: DeviceDefinition.specialization
  equivalence:
    v: narrower
  comment:
    v: Element `DeviceDefinition.conformsTo.specification` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `SourceIsNarrowerThanTarget`.

code:
  v: DeviceDefinition.conformsTo.version
display:
  v: version
target:
  code:
    v: DeviceDefinition.specialization.version
  display:
    v: DeviceDefinition.specialization.version
  equivalence:
    v: equivalent
  comment:
    v: Element `DeviceDefinition.conformsTo.version` is mapped to FHIR R4 element `DeviceDefinition.specialization.version` as `SourceIsBroaderThanTarget`.

code:
  v: DeviceDefinition.conformsTo.source
display:
  v: source
target:
  code:
    v: DeviceDefinition.specialization
  display:
    v: DeviceDefinition.specialization
  equivalence:
    v: equivalent
  comment:
    v: Element `DeviceDefinition.conformsTo.source` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `Equivalent`.

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

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

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

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

code:
  v: DeviceDefinition.property
display:
  v: property
target:
  code:
    v: DeviceDefinition.property
  display:
    v: DeviceDefinition.property
  equivalence:
    v: wider
  comment:
    v: Element `DeviceDefinition.property` is mapped to FHIR R4 element `DeviceDefinition.property` as `Equivalent`. Dynamic or current properties, such as settings, of an individual device are described using a Device instance-specific DeviceMetric and recorded using Observation. Static characteristics of an individual device could also be documented in a [Device] instance. The Device instance's properties, and their values, could be, but need not be, the same as in the associated DeviceDefinition.

code:
  v: DeviceDefinition.property.type
display:
  v: type
target:
  code:
    v: DeviceDefinition.property.type
  display:
    v: DeviceDefinition.property.type
  equivalence:
    v: equivalent
  comment:
    v: Element `DeviceDefinition.property.type` is mapped to FHIR R4 element `DeviceDefinition.property.type` as `Equivalent`.

code:
  v: DeviceDefinition.property.value[x]
display:
  v: value[x]
target:
  code:
    v: DeviceDefinition.property.valueCode
  display:
    v: DeviceDefinition.property.valueCode
  equivalence:
    v: relatedto
  comment:
    v: Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueQuantity` as `RelatedTo`. Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueCode` as `RelatedTo`. The mappings for `DeviceDefinition.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string. This use of string or CodeableConcept is supported to address different purposes The text element of the valueCodeableConcept choice type is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g., a custom implant size, or a security classification which depends on configuration. Otherwise the valueString choice type is used for textual descriptive device properties that cannot be expressed in other elements.
target:
  code:
    v: DeviceDefinition.property.valueQuantity
  display:
    v: DeviceDefinition.property.valueQuantity
  equivalence:
    v: relatedto
  comment:
    v: Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueQuantity` as `RelatedTo`. Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueCode` as `RelatedTo`. The mappings for `DeviceDefinition.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string. This use of string or CodeableConcept is supported to address different purposes The text element of the valueCodeableConcept choice type is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g., a custom implant size, or a security classification which depends on configuration. Otherwise the valueString choice type is used for textual descriptive device properties that cannot be expressed in other elements.

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

code:
  v: DeviceDefinition.contact
display:
  v: contact
target:
  code:
    v: DeviceDefinition.contact
  display:
    v: DeviceDefinition.contact
  equivalence:
    v: equivalent
  comment:
    v: Element `DeviceDefinition.contact` is mapped to FHIR R4 element `DeviceDefinition.contact` as `Equivalent`. An externally-defined extension that has been mapped as the representation of FHIR R5 element `DeviceDefinition.contact`: `http://hl7.org/fhir/StructureDefinition/artifact-contact`. used for troubleshooting etc.

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

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

code:
  v: DeviceDefinition.material.substance
display:
  v: substance
target:
  code:
    v: DeviceDefinition.material.substance
  display:
    v: DeviceDefinition.material.substance
  equivalence:
    v: equivalent
  comment:
    v: Element `DeviceDefinition.material.substance` is mapped to FHIR R4 element `DeviceDefinition.material.substance` as `Equivalent`.

code:
  v: DeviceDefinition.material.alternate
display:
  v: alternate
target:
  code:
    v: DeviceDefinition.material.alternate
  display:
    v: DeviceDefinition.material.alternate
  equivalence:
    v: equivalent
  comment:
    v: Element `DeviceDefinition.material.alternate` is mapped to FHIR R4 element `DeviceDefinition.material.alternate` as `Equivalent`.

code:
  v: DeviceDefinition.material.allergenicIndicator
display:
  v: allergenicIndicator
target:
  code:
    v: DeviceDefinition.material.allergenicIndicator
  display:
    v: DeviceDefinition.material.allergenicIndicator
  equivalence:
    v: equivalent
  comment:
    v: Element `DeviceDefinition.material.allergenicIndicator` is mapped to FHIR R4 element `DeviceDefinition.material.allergenicIndicator` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.udiDeviceIdentifier
  l: extension-DeviceDefinition.udiDeviceIdentifier
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.udiDeviceIdentifier
  display:
    v: udiDeviceIdentifier
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `DeviceDefinition.udiDeviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier` as `Equivalent`.
element:
  code:
    v: DeviceDefinition.udiDeviceIdentifier.deviceIdentifier
  display:
    v: deviceIdentifier
  target:
    code:
      v: Extension.extension:deviceIdentifier
    equivalence:
      v: equivalent
    comment:
      v: Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` as `Equivalent`.
element:
  code:
    v: DeviceDefinition.udiDeviceIdentifier.issuer
  display:
    v: issuer
  target:
    code:
      v: Extension.extension:issuer
    equivalence:
      v: equivalent
    comment:
      v: Element `DeviceDefinition.udiDeviceIdentifier.issuer` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.issuer` as `Equivalent`.
element:
  code:
    v: DeviceDefinition.udiDeviceIdentifier.jurisdiction
  display:
    v: jurisdiction
  target:
    code:
      v: Extension.extension:jurisdiction
    equivalence:
      v: equivalent
    comment:
      v: Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` as `Equivalent`.
element:
  code:
    v: DeviceDefinition.udiDeviceIdentifier.marketDistribution
  display:
    v: marketDistribution
  target:
    code:
      v: Extension.extension:marketDistribution
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod
  display:
    v: marketPeriod
  target:
    code:
      v: Extension.extension:marketDistribution.extension:marketPeriod
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction
  display:
    v: subJurisdiction
  target:
    code:
      v: Extension.extension:marketDistribution.extension:subJurisdiction
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.packaging.udiDeviceIdentifier
  display:
    v: udiDeviceIdentifier
  target:
    code:
      v: Extension.extension:udiDeviceIdentifier
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.packaging.udiDeviceIdentifier` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.udiDeviceIdentifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.udiDeviceIdentifier` 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/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.udiDeviceIdentifier.marketDistribution
  l: extension-DeviceDefinition.udiDeviceIdentifier.marketDistribution
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.udiDeviceIdentifier.marketDistribution
  display:
    v: marketDistribution
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod
  display:
    v: marketPeriod
  target:
    code:
      v: Extension.extension:marketPeriod
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction
  display:
    v: subJurisdiction
  target:
    code:
      v: Extension.extension:subJurisdiction
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` 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/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.regulatoryIdentifier
  l: extension-DeviceDefinition.regulatoryIdentifier
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.regulatoryIdentifier
  display:
    v: regulatoryIdentifier
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.regulatoryIdentifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.regulatoryIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This should not be used for regulatory authorization numbers which are to be captured elsewhere.
element:
  code:
    v: DeviceDefinition.regulatoryIdentifier.type
  display:
    v: type
  target:
    code:
      v: Extension.extension:type
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.regulatoryIdentifier.type` is part of an existing definition because parent element `DeviceDefinition.regulatoryIdentifier` requires a cross-version extension. Element `DeviceDefinition.regulatoryIdentifier.type` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.regulatoryIdentifier.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.regulatoryIdentifier.deviceIdentifier
  display:
    v: deviceIdentifier
  target:
    code:
      v: Extension.extension:deviceIdentifier
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.regulatoryIdentifier.deviceIdentifier` is part of an existing definition because parent element `DeviceDefinition.regulatoryIdentifier` requires a cross-version extension. Element `DeviceDefinition.regulatoryIdentifier.deviceIdentifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.regulatoryIdentifier.deviceIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.regulatoryIdentifier.issuer
  display:
    v: issuer
  target:
    code:
      v: Extension.extension:issuer
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.regulatoryIdentifier.issuer` is part of an existing definition because parent element `DeviceDefinition.regulatoryIdentifier` requires a cross-version extension. Element `DeviceDefinition.regulatoryIdentifier.issuer` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.regulatoryIdentifier.issuer` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.regulatoryIdentifier.jurisdiction
  display:
    v: jurisdiction
  target:
    code:
      v: Extension.extension:jurisdiction
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.regulatoryIdentifier.jurisdiction` is part of an existing definition because parent element `DeviceDefinition.regulatoryIdentifier` requires a cross-version extension. Element `DeviceDefinition.regulatoryIdentifier.jurisdiction` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.regulatoryIdentifier.jurisdiction` 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/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.partNumber
  l: extension-DeviceDefinition.partNumber
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.partNumber
  display:
    v: partNumber
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.partNumber` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.partNumber` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Alphanumeric Maximum 20.

source:
  v: http://hl7.org/fhir/StructureDefinition/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.classification
  l: extension-DeviceDefinition.classification
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.classification
  display:
    v: classification
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.classification` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.classification` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). In this element various classifications can be used, such as GMDN, EMDN, SNOMED CT, risk classes, national product codes.
element:
  code:
    v: DeviceDefinition.classification.type
  display:
    v: type
  target:
    code:
      v: Extension.extension:type
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.classification.type` is part of an existing definition because parent element `DeviceDefinition.classification` requires a cross-version extension. Element `DeviceDefinition.classification.type` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.classification.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.classification.justification
  display:
    v: justification
  target:
    code:
      v: Extension.extension:justification
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.classification.justification` is part of an existing definition because parent element `DeviceDefinition.classification` requires a cross-version extension. Element `DeviceDefinition.classification.justification` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.classification.justification` 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/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.hasPart
  l: extension-DeviceDefinition.hasPart
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.hasPart
  display:
    v: hasPart
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.hasPart` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.hasPart` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.hasPart.reference
  display:
    v: reference
  target:
    code:
      v: Extension.extension:reference
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.hasPart.reference` is part of an existing definition because parent element `DeviceDefinition.hasPart` requires a cross-version extension. Element `DeviceDefinition.hasPart.reference` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.hasPart.reference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.hasPart.count
  display:
    v: count
  target:
    code:
      v: Extension.extension:count
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.hasPart.count` is part of an existing definition because parent element `DeviceDefinition.hasPart` requires a cross-version extension. Element `DeviceDefinition.hasPart.count` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.hasPart.count` 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/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.packaging
  l: extension-DeviceDefinition.packaging
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.packaging
  display:
    v: packaging
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.packaging` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.packaging.identifier
  display:
    v: identifier
  target:
    code:
      v: Extension.extension:identifier
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.packaging.identifier` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.identifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.packaging.type
  display:
    v: type
  target:
    code:
      v: Extension.extension:type
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.packaging.type` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.type` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.packaging.count
  display:
    v: count
  target:
    code:
      v: Extension.extension:count
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.packaging.count` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.count` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.count` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.packaging.distributor
  display:
    v: distributor
  target:
    code:
      v: Extension.extension:distributor
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.packaging.distributor` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.distributor` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.distributor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.packaging.distributor.name
  display:
    v: name
  target:
    code:
      v: Extension.extension:distributor.extension:name
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.packaging.distributor.name` is part of an existing definition because parent element `DeviceDefinition.packaging.distributor` requires a cross-version extension. Element `DeviceDefinition.packaging.distributor.name` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.distributor.name` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.packaging.distributor.organizationReference
  display:
    v: organizationReference
  target:
    code:
      v: Extension.extension:distributor.extension:organizationReference
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.packaging.distributor.organizationReference` is part of an existing definition because parent element `DeviceDefinition.packaging.distributor` requires a cross-version extension. Element `DeviceDefinition.packaging.distributor.organizationReference` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.distributor.organizationReference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.packaging.udiDeviceIdentifier
  display:
    v: udiDeviceIdentifier
  target:
    code:
      v: Extension.extension:udiDeviceIdentifier
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.packaging.udiDeviceIdentifier` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.udiDeviceIdentifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.udiDeviceIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.packaging.packaging
  display:
    v: packaging
  target:
    code:
      v: Extension.extension:packaging
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.packaging.packaging` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.packaging` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.packaging` 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/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.version.type
  l: extension-DeviceDefinition.version.type
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.version.type
  display:
    v: type
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.version.type` has a context of DeviceDefinition.version based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.version.type` 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/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.version.component
  l: extension-DeviceDefinition.version.component
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.version.component
  display:
    v: component
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.version.component` has a context of DeviceDefinition.version based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.version.component` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Note that the module of the device would not need to be tracked as a separate device, e.g., using different UDI, thus would typically involve one or more software modules. For example, a device may involve two software modules each on a different version.

source:
  v: http://hl7.org/fhir/StructureDefinition/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.version.value
  l: extension-DeviceDefinition.version.value
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.version.value
  display:
    v: value
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.version.value` has a context of DeviceDefinition.version based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.version.value` 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/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.property.value
  l: extension-DeviceDefinition.property.value
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.property.value[x]
  display:
    v: value[x]
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueQuantity` as `RelatedTo`. Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueCode` as `RelatedTo`. The mappings for `DeviceDefinition.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string. This use of string or CodeableConcept is supported to address different purposes The text element of the valueCodeableConcept choice type is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g., a custom implant size, or a security classification which depends on configuration. Otherwise the valueString choice type is used for textual descriptive device properties that cannot be expressed in other elements.

source:
  v: http://hl7.org/fhir/StructureDefinition/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.link
  l: extension-DeviceDefinition.link
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.link
  display:
    v: link
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.link` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.link` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.link.relation
  display:
    v: relation
  target:
    code:
      v: Extension.extension:relation
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.link.relation` is part of an existing definition because parent element `DeviceDefinition.link` requires a cross-version extension. Element `DeviceDefinition.link.relation` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.link.relation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.link.relatedDevice
  display:
    v: relatedDevice
  target:
    code:
      v: Extension.extension:relatedDevice
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.link.relatedDevice` is part of an existing definition because parent element `DeviceDefinition.link` requires a cross-version extension. Element `DeviceDefinition.link.relatedDevice` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.link.relatedDevice` 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/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.productionIdentifierInUDI
  l: extension-DeviceDefinition.productionIdentifierInUDI
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.productionIdentifierInUDI
  display:
    v: productionIdentifierInUDI
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.productionIdentifierInUDI` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.productionIdentifierInUDI` 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/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.guideline
  l: extension-DeviceDefinition.guideline
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.guideline
  display:
    v: guideline
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.guideline` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). For more structured data, a ClinicalUseDefinition that points to the DeviceDefinition can be used.
element:
  code:
    v: DeviceDefinition.guideline.useContext
  display:
    v: useContext
  target:
    code:
      v: Extension.extension:useContext
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.guideline.useContext` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.useContext` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.useContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.guideline.usageInstruction
  display:
    v: usageInstruction
  target:
    code:
      v: Extension.extension:usageInstruction
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.guideline.usageInstruction` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.usageInstruction` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.usageInstruction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.guideline.relatedArtifact
  display:
    v: relatedArtifact
  target:
    code:
      v: Extension.extension:relatedArtifact
    equivalence:
      v: equivalent
    comment:
      v: Element `DeviceDefinition.guideline.relatedArtifact` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.relatedArtifact` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.relatedArtifact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.guideline.indication
  display:
    v: indication
  target:
    code:
      v: Extension.extension:indication
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.guideline.indication` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.indication` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.indication` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). A ClinicalUseDefinition that points to the DeviceDefinition can be used if more structured data is needed.
element:
  code:
    v: DeviceDefinition.guideline.contraindication
  display:
    v: contraindication
  target:
    code:
      v: Extension.extension:contraindication
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.guideline.contraindication` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.contraindication` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.contraindication` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). A ClinicalUseDefinition that points to the DeviceDefinition can be used if more structured data is needed.
element:
  code:
    v: DeviceDefinition.guideline.warning
  display:
    v: warning
  target:
    code:
      v: Extension.extension:warning
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.guideline.warning` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.warning` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.warning` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). A ClinicalUseDefinition that points to the DeviceDefinition can be used if more structured data is needed.
element:
  code:
    v: DeviceDefinition.guideline.intendedUse
  display:
    v: intendedUse
  target:
    code:
      v: Extension.extension:intendedUse
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.guideline.intendedUse` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.intendedUse` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.intendedUse` 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/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.correctiveAction
  l: extension-DeviceDefinition.correctiveAction
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.correctiveAction
  display:
    v: correctiveAction
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.correctiveAction` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.correctiveAction.recall
  display:
    v: recall
  target:
    code:
      v: Extension.extension:recall
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.correctiveAction.recall` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension. Element `DeviceDefinition.correctiveAction.recall` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction.recall` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When a field safety action has been initiated but not yet resulted in a recall, this element will be set to 'false'.
element:
  code:
    v: DeviceDefinition.correctiveAction.scope
  display:
    v: scope
  target:
    code:
      v: Extension.extension:scope
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.correctiveAction.scope` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension. Element `DeviceDefinition.correctiveAction.scope` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction.scope` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.correctiveAction.period
  display:
    v: period
  target:
    code:
      v: Extension.extension:period
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.correctiveAction.period` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension. Element `DeviceDefinition.correctiveAction.period` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction.period` 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/DeviceDefinition
  l: DeviceDefinition
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.chargeItem
  l: extension-DeviceDefinition.chargeItem
target version:
  v: 0.1.0
element:
  code:
    v: DeviceDefinition.chargeItem
  display:
    v: chargeItem
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.chargeItem` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.chargeItem` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.chargeItem.chargeItemCode
  display:
    v: chargeItemCode
  target:
    code:
      v: Extension.extension:chargeItemCode
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.chargeItem.chargeItemCode` is part of an existing definition because parent element `DeviceDefinition.chargeItem` requires a cross-version extension. Element `DeviceDefinition.chargeItem.chargeItemCode` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.chargeItem.chargeItemCode` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.chargeItem.count
  display:
    v: count
  target:
    code:
      v: Extension.extension:count
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.chargeItem.count` is part of an existing definition because parent element `DeviceDefinition.chargeItem` requires a cross-version extension. Element `DeviceDefinition.chargeItem.count` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.chargeItem.count` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.chargeItem.effectivePeriod
  display:
    v: effectivePeriod
  target:
    code:
      v: Extension.extension:effectivePeriod
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.chargeItem.effectivePeriod` is part of an existing definition because parent element `DeviceDefinition.chargeItem` requires a cross-version extension. Element `DeviceDefinition.chargeItem.effectivePeriod` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.chargeItem.effectivePeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceDefinition.chargeItem.useContext
  display:
    v: useContext
  target:
    code:
      v: Extension.extension:useContext
    equivalence:
      v: wider
    comment:
      v: Element `DeviceDefinition.chargeItem.useContext` is part of an existing definition because parent element `DeviceDefinition.chargeItem` requires a cross-version extension. Element `DeviceDefinition.chargeItem.useContext` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.chargeItem.useContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).