Extensions for Using Data Elements from FHIR STU3 in FHIR R5
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR STU3 in FHIR R5 - Downloaded Version null See the Directory of published versions

ConceptMap: R3DeviceMetricElementMapToR5

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R3-DeviceMetric-element-map-to-R5 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R3DeviceMetricElementMapToR5

This ConceptMap represents cross-version mappings for elements from a FHIR STU3 DeviceMetric to FHIR R5.

Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/5.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceMetric|3.0.2 to DeviceMetricversion: 5.0.0)

Source CodeRelationshipTarget CodeComment
DeviceMetric.meta (meta)is broader thanDeviceMetric.metaElement `DeviceMetric.meta` is mapped to FHIR R5 element `DeviceMetric.meta` as `SourceIsBroaderThanTarget`. The mappings for `DeviceMetric.meta` do not cover the following types: Meta. The mappings for `DeviceMetric.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
DeviceMetric.implicitRules (implicitRules)is equivalent toDeviceMetric.implicitRulesElement `DeviceMetric.implicitRules` is mapped to FHIR R5 element `DeviceMetric.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. 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.
DeviceMetric.language (language)is equivalent toDeviceMetric.languageElement `DeviceMetric.language` is mapped to FHIR R5 element `DeviceMetric.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).
DeviceMetric.text (text)is broader thanDeviceMetric.textElement `DeviceMetric.text` is mapped to FHIR R5 element `DeviceMetric.text` as `SourceIsBroaderThanTarget`. The mappings for `DeviceMetric.text` do not cover the following types: Narrative. The mappings for `DeviceMetric.text` do not cover the following types based on type expansion: div, status. 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.
DeviceMetric.contained (contained)is equivalent toDeviceMetric.containedElement `DeviceMetric.contained` is mapped to FHIR R5 element `DeviceMetric.contained` as `SourceIsBroaderThanTarget`. 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.
DeviceMetric.identifier (identifier)is broader thanDeviceMetric.identifierElement `DeviceMetric.identifier` is mapped to FHIR R5 element `DeviceMetric.identifier` as `RelatedTo`. The mappings for `DeviceMetric.identifier` do not cover the following types: Identifier. The mappings for `DeviceMetric.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
DeviceMetric.type (type)is equivalent toDeviceMetric.typeElement `DeviceMetric.type` is mapped to FHIR R5 element `DeviceMetric.type` as `Equivalent`. DeviceMetric.type can be referred to either IEEE 11073-10101 or LOINC.
DeviceMetric.unit (unit)is equivalent toDeviceMetric.unitElement `DeviceMetric.unit` is mapped to FHIR R5 element `DeviceMetric.unit` as `Equivalent`. DeviceMetric.unit can refer to either UCUM or preferable a RTMMS coding system.
DeviceMetric.parent (parent)is broader thanDeviceMetric.deviceElement `DeviceMetric.parent` is mapped to FHIR R5 element `DeviceMetric.device` as `SourceIsBroaderThanTarget`. The mappings for `DeviceMetric.parent` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `DeviceMetric.parent` with unmapped reference targets: DeviceComponent.
DeviceMetric.operationalStatus (operationalStatus)is equivalent toDeviceMetric.operationalStatusElement `DeviceMetric.operationalStatus` is mapped to FHIR R5 element `DeviceMetric.operationalStatus` as `Equivalent`.
DeviceMetric.color (color)is equivalent toDeviceMetric.colorElement `DeviceMetric.color` is mapped to FHIR R5 element `DeviceMetric.color` as `Equivalent`.
DeviceMetric.category (category)is equivalent toDeviceMetric.categoryElement `DeviceMetric.category` is mapped to FHIR R5 element `DeviceMetric.category` as `Equivalent`.
DeviceMetric.calibration (calibration)is broader thanDeviceMetric.calibrationElement `DeviceMetric.calibration` is mapped to FHIR R5 element `DeviceMetric.calibration` as `Equivalent`.
DeviceMetric.calibration.type (type)is equivalent toDeviceMetric.calibration.typeElement `DeviceMetric.calibration.type` is mapped to FHIR R5 element `DeviceMetric.calibration.type` as `Equivalent`.
DeviceMetric.calibration.state (state)is equivalent toDeviceMetric.calibration.stateElement `DeviceMetric.calibration.state` is mapped to FHIR R5 element `DeviceMetric.calibration.state` as `Equivalent`.
DeviceMetric.calibration.time (time)is equivalent toDeviceMetric.calibration.timeElement `DeviceMetric.calibration.time` is mapped to FHIR R5 element `DeviceMetric.calibration.time` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceMetric|3.0.2 to STU3: meta additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceMetric.meta (meta)is equivalent toExtension (STU3: meta additional types)Element `DeviceMetric.meta` is mapped to FHIR R5 element `DeviceMetric.meta` as `SourceIsBroaderThanTarget`. The mappings for `DeviceMetric.meta` do not cover the following types: Meta. The mappings for `DeviceMetric.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceMetric|3.0.2 to STU3: text additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceMetric.text (text)is equivalent toExtension (STU3: text additional types)Element `DeviceMetric.text` is mapped to FHIR R5 element `DeviceMetric.text` as `SourceIsBroaderThanTarget`. The mappings for `DeviceMetric.text` do not cover the following types: Narrative. The mappings for `DeviceMetric.text` do not cover the following types based on type expansion: div, status. 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.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceMetric|3.0.2 to STU3: Unique identifier of this DeviceMetric additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceMetric.identifier (identifier)is equivalent toExtension (STU3: Unique identifier of this DeviceMetric additional types)Element `DeviceMetric.identifier` is mapped to FHIR R5 element `DeviceMetric.identifier` as `RelatedTo`. The mappings for `DeviceMetric.identifier` do not cover the following types: Identifier. The mappings for `DeviceMetric.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceMetric|3.0.2 to STU3: Describes the link to the source Device (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceMetric.source (source)is equivalent toExtension (STU3: Describes the link to the source Device (new))Element `DeviceMetric.source` has a context of DeviceMetric based on following the parent source element upwards and mapping to `DeviceMetric`. Element `DeviceMetric.source` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceMetric|3.0.2 to STU3: Describes the measurement repetition time (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceMetric.measurementPeriod (measurementPeriod)is equivalent toExtension (STU3: Describes the measurement repetition time (new))Element `DeviceMetric.measurementPeriod` has a context of DeviceMetric based on following the parent source element upwards and mapping to `DeviceMetric`. Element `DeviceMetric.measurementPeriod` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).