R3-DeviceComponent-element-map-to-R4B
type: ConceptMap
node role: treeRoot
id:
  v: R3-DeviceComponent-element-map-to-R4B
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R3-DeviceComponent-element-map-to-R4B Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.3 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceComponent|3.0.2 to Basicversion: 4.3.0) Source Code Relationship Target Code Comment DeviceComponent.meta (meta) is equivalent to Basic.meta Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `DeviceComponent.meta` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.meta` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). DeviceComponent.implicitRules (implicitRules) is equivalent to Basic.implicitRules Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `DeviceComponent.implicitRules` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.implicitRules` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. DeviceComponent.language (language) is equivalent to Basic.language Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `DeviceComponent.language` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not map…
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-r3.r4b
        l: hl7.fhir.uv.xver-r3.r4b
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-r3.r4b
        l: hl7.fhir.uv.xver-r3.r4b
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R3-DeviceComponent-element-map-to-R4B
  l: R3-DeviceComponent-element-map-to-R4B
version:
  v: 0.1.0
name:
  v: R3DeviceComponentElementMapToR4B
title:
  v: Cross-version mapping for FHIR STU3 DeviceComponent to FHIR R4B Basic
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:10.5506655-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 STU3 DeviceComponent to FHIR R4B.
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/3.0
  l: http://hl7.org/fhir/3.0
target: Uri
  v: http://hl7.org/fhir/4.3
  l: http://hl7.org/fhir/4.3
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/DeviceComponent
    l: DeviceComponent
  source version:
    v: 3.0.2
  target:
    v: http://hl7.org/fhir/StructureDefinition/Basic
    l: Basic
  target version:
    v: 4.3.0
  element:
    code:
      v: DeviceComponent.meta
    display:
      v: meta
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.meta
      display:
        v: Basic.meta
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `DeviceComponent.meta` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.meta` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
  element:
    code:
      v: DeviceComponent.implicitRules
    display:
      v: implicitRules
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.implicitRules
      display:
        v: Basic.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `DeviceComponent.implicitRules` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.implicitRules` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
  element:
    code:
      v: DeviceComponent.language
    display:
      v: language
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.language
      display:
        v: Basic.language
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `DeviceComponent.language` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.language` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). 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: DeviceComponent.text
    display:
      v: text
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.text
      display:
        v: Basic.text
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `DeviceComponent.text` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.text` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
  element:
    code:
      v: DeviceComponent.contained
    display:
      v: contained
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.contained
      display:
        v: Basic.contained
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `DeviceComponent.contained` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.contained` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
  element:
    code:
      v: DeviceComponent.identifier
    display:
      v: identifier
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.identifier
      display:
        v: Basic.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `DeviceComponent.identifier` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.identifier` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/DeviceComponent
    l: DeviceComponent
  source version:
    v: 3.0.2
  target:
    v: http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceComponent.type
    l: extension-DeviceComponent.type
  target version:
    v: 0.1.0
  element:
    code:
      v: DeviceComponent.type

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

v: type

modifier extension:
  url:
    v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
    l: extension-ConceptMap.element.target.equivalence
  value: Code
    v: wider
code:
  v: Extension
equivalence:
  v: wider
comment:
  v: Element `DeviceComponent.type` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.type` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). DeviceComponent.type can be referred to either GDMN (nomenclature system supported by FDA Global UDI Database) or preferable RTMMS coding system.

source:
  v: http://hl7.org/fhir/StructureDefinition/DeviceComponent
  l: DeviceComponent
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceComponent.lastSystemChange
  l: extension-DeviceComponent.lastSystemChange
target version:
  v: 0.1.0
element:
  code:
    v: DeviceComponent.lastSystemChange
  display:
    v: lastSystemChange
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceComponent.lastSystemChange` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.lastSystemChange` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/DeviceComponent
  l: DeviceComponent
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceComponent.source
  l: extension-DeviceComponent.source
target version:
  v: 0.1.0
element:
  code:
    v: DeviceComponent.source
  display:
    v: source
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceComponent.source` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.source` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/DeviceComponent
  l: DeviceComponent
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceComponent.parent
  l: extension-DeviceComponent.parent
target version:
  v: 0.1.0
element:
  code:
    v: DeviceComponent.parent
  display:
    v: parent
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceComponent.parent` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.parent` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/DeviceComponent
  l: DeviceComponent
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceComponent.operationalStatus
  l: extension-DeviceComponent.operationalStatus
target version:
  v: 0.1.0
element:
  code:
    v: DeviceComponent.operationalStatus
  display:
    v: operationalStatus
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceComponent.operationalStatus` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.operationalStatus` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). OperationalStatus for the MDS, VMD, or Channel will be bound to a specific ValueSet that is defined in its profile.

source:
  v: http://hl7.org/fhir/StructureDefinition/DeviceComponent
  l: DeviceComponent
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceComponent.parameterGroup
  l: extension-DeviceComponent.parameterGroup
target version:
  v: 0.1.0
element:
  code:
    v: DeviceComponent.parameterGroup
  display:
    v: parameterGroup
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceComponent.parameterGroup` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.parameterGroup` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/DeviceComponent
  l: DeviceComponent
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceComponent.measurementPrinciple
  l: extension-DeviceComponent.measurementPrinciple
target version:
  v: 0.1.0
element:
  code:
    v: DeviceComponent.measurementPrinciple
  display:
    v: measurementPrinciple
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceComponent.measurementPrinciple` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.measurementPrinciple` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/DeviceComponent
  l: DeviceComponent
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceComponent.productionSpecification
  l: extension-DeviceComponent.productionSpecification
target version:
  v: 0.1.0
element:
  code:
    v: DeviceComponent.productionSpecification
  display:
    v: productionSpecification
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceComponent.productionSpecification` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.productionSpecification` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceComponent.productionSpecification.specType
  display:
    v: specType
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:specType
    equivalence:
      v: wider
    comment:
      v: Element `DeviceComponent.productionSpecification.specType` is part of an existing definition because parent element `DeviceComponent.productionSpecification` requires a cross-version extension. Element `DeviceComponent.productionSpecification.specType` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.productionSpecification.specType` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceComponent.productionSpecification.componentId
  display:
    v: componentId
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:componentId
    equivalence:
      v: wider
    comment:
      v: Element `DeviceComponent.productionSpecification.componentId` is part of an existing definition because parent element `DeviceComponent.productionSpecification` requires a cross-version extension. Element `DeviceComponent.productionSpecification.componentId` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.productionSpecification.componentId` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: DeviceComponent.productionSpecification.productionSpec
  display:
    v: productionSpec
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:productionSpec
    equivalence:
      v: wider
    comment:
      v: Element `DeviceComponent.productionSpecification.productionSpec` is part of an existing definition because parent element `DeviceComponent.productionSpecification` requires a cross-version extension. Element `DeviceComponent.productionSpecification.productionSpec` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.productionSpecification.productionSpec` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/DeviceComponent
  l: DeviceComponent
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-DeviceComponent.languageCode
  l: extension-DeviceComponent.languageCode
target version:
  v: 0.1.0
element:
  code:
    v: DeviceComponent.languageCode
  display:
    v: languageCode
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `DeviceComponent.languageCode` is not mapped to FHIR R4B, since FHIR STU3 `DeviceComponent` is not mapped. Element `DeviceComponent.languageCode` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).