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 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). DeviceComponent.text (text) is equivalent to Basic.text 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. DeviceComponent.contained (contained) is equivalent to Basic.contained 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. DeviceComponent.identifier (identifier) is equivalent to Basic.identifier 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 2 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceComponent|3.0.2 to STU3: What kind of component it is (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceComponent.type (type) maps to wider concept Extension (STU3: What kind of component it is (new)) 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. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceComponent|3.0.2 to STU3: Recent system change timestamp (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceComponent.lastSystemChange (lastSystemChange) maps to wider concept Extension (STU3: Recent system change timestamp (new)) 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). Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceComponent|3.0.2 to STU3: Top-level device resource link (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceComponent.source (source) maps to wider concept Extension (STU3: Top-level device resource link (new)) 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). Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceComponent|3.0.2 to STU3: Parent resource link (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceComponent.parent (parent) maps to wider concept Extension (STU3: Parent resource link (new)) 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). Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceComponent|3.0.2 to STU3: Current operational status of the component, for example On, Off or Standby (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceComponent.operationalStatus (operationalStatus) maps to wider concept Extension (STU3: Current operational status of the component, for example On, Off or Standby (new)) 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. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceComponent|3.0.2 to STU3: Current supported parameter group (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceComponent.parameterGroup (parameterGroup) maps to wider concept Extension (STU3: Current supported parameter group (new)) 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). Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceComponent|3.0.2 to STU3: other | chemical | electrical | impedance | nuclear | optical | thermal | biological | mechanical | acoustical | manual+ (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceComponent.measurementPrinciple (measurementPrinciple) maps to wider concept Extension (STU3: other | chemical | electrical | impedance | nuclear | optical | thermal | biological | mechanical | acoustical | manual+ (new)) 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). Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceComponent|3.0.2 to STU3: Specification details such as Component Revisions, or Serial Numbers (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceComponent.productionSpecification (productionSpecification) maps to wider concept Extension (STU3: Specification details such as Component Revisions, or Serial Numbers (new)) 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). DeviceComponent.productionSpecification.specType (specType) maps to wider concept Extension.extension:specType (STU3: Type or kind of production specification, for example serial number or software revision (new)) 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). DeviceComponent.productionSpecification.componentId (componentId) maps to wider concept Extension.extension:componentId (STU3: Internal component unique identification (new)) 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). DeviceComponent.productionSpecification.productionSpec (productionSpec) maps to wider concept Extension.extension:productionSpec (STU3: A printable string defining the component (new)) 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). Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceComponent|3.0.2 to STU3: Language code for the human-readable text strings produced by the device (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceComponent.languageCode (languageCode) maps to wider concept Extension (STU3: Language code for the human-readable text strings produced by the device (new)) 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).
Cross-version mapping for FHIR STU3 DeviceComponent to FHIR R4B Basic
This ConceptMap represents cross-version mappings for elements from a FHIR STU3 DeviceComponent to FHIR R4B.
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 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 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 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 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 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).
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.
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).
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).
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).
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.
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).
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).
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 `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 `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 `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).
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).