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

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

ConceptMap: R5DeviceMetricElementMapToR3

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

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

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


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

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/DeviceMetric|5.0.0Codes from http://hl7.org/fhir/StructureDefinition/DeviceMetric|3.0.2
DeviceMetric.metameta​is equivalent toDeviceMetric.metaDeviceMetric.metaElement `DeviceMetric.meta` is mapped to FHIR STU3 element `DeviceMetric.meta` as `Equivalent`.
DeviceMetric.implicitRulesimplicitRules​is equivalent toDeviceMetric.implicitRulesDeviceMetric.implicitRulesElement `DeviceMetric.implicitRules` is mapped to FHIR STU3 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. 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.
DeviceMetric.languagelanguage​is equivalent toDeviceMetric.languageDeviceMetric.languageElement `DeviceMetric.language` is mapped to FHIR STU3 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.texttext​is equivalent toDeviceMetric.textDeviceMetric.textElement `DeviceMetric.text` is mapped to FHIR STU3 element `DeviceMetric.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.
DeviceMetric.containedcontained​is equivalent toDeviceMetric.containedDeviceMetric.containedElement `DeviceMetric.contained` is mapped to FHIR STU3 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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
DeviceMetric.identifieridentifier​is equivalent toDeviceMetric.identifierDeviceMetric.identifierElement `DeviceMetric.identifier` is mapped to FHIR STU3 element `DeviceMetric.identifier` as `SourceIsBroaderThanTarget`. For identifiers assigned to a device by the device or gateway software, the `system` element of the identifier should be set to any identifier of the device.
DeviceMetric.typetype​is equivalent toDeviceMetric.typeDeviceMetric.typeElement `DeviceMetric.type` is mapped to FHIR STU3 element `DeviceMetric.type` as `Equivalent`. DeviceMetric.type can be referred to either IEEE 11073-10101 or LOINC.
DeviceMetric.unitunit​is equivalent toDeviceMetric.unitDeviceMetric.unitElement `DeviceMetric.unit` is mapped to FHIR STU3 element `DeviceMetric.unit` as `Equivalent`. DeviceMetric.unit can refer to either UCUM or preferable a RTMMS coding system.
DeviceMetric.devicedevice​is related toDeviceMetric.parentDeviceMetric.parentElement `DeviceMetric.device` is mapped to FHIR STU3 element `DeviceMetric.source` as `SourceIsBroaderThanTarget`. Element `DeviceMetric.device` is mapped to FHIR STU3 element `DeviceMetric.parent` as `SourceIsBroaderThanTarget`. The mappings for `DeviceMetric.device` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DeviceMetric.device` with unmapped reference targets: Device. Note if this is not the top level device - also know as the source device, it may be referenced in the device.parent element.
​is related toDeviceMetric.sourceDeviceMetric.sourceElement `DeviceMetric.device` is mapped to FHIR STU3 element `DeviceMetric.source` as `SourceIsBroaderThanTarget`. Element `DeviceMetric.device` is mapped to FHIR STU3 element `DeviceMetric.parent` as `SourceIsBroaderThanTarget`. The mappings for `DeviceMetric.device` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DeviceMetric.device` with unmapped reference targets: Device. Note if this is not the top level device - also know as the source device, it may be referenced in the device.parent element.
DeviceMetric.operationalStatusoperationalStatus​is equivalent toDeviceMetric.operationalStatusDeviceMetric.operationalStatusElement `DeviceMetric.operationalStatus` is mapped to FHIR STU3 element `DeviceMetric.operationalStatus` as `Equivalent`.
DeviceMetric.colorcolor​is equivalent toDeviceMetric.colorDeviceMetric.colorElement `DeviceMetric.color` is mapped to FHIR STU3 element `DeviceMetric.color` as `Equivalent`.
DeviceMetric.categorycategory​is equivalent toDeviceMetric.categoryDeviceMetric.categoryElement `DeviceMetric.category` is mapped to FHIR STU3 element `DeviceMetric.category` as `Equivalent`.
DeviceMetric.calibrationcalibration​maps to wider conceptDeviceMetric.calibrationDeviceMetric.calibrationElement `DeviceMetric.calibration` is mapped to FHIR STU3 element `DeviceMetric.calibration` as `Equivalent`.
DeviceMetric.calibration.typetype​is equivalent toDeviceMetric.calibration.typeDeviceMetric.calibration.typeElement `DeviceMetric.calibration.type` is mapped to FHIR STU3 element `DeviceMetric.calibration.type` as `Equivalent`.
DeviceMetric.calibration.statestate​is equivalent toDeviceMetric.calibration.stateDeviceMetric.calibration.stateElement `DeviceMetric.calibration.state` is mapped to FHIR STU3 element `DeviceMetric.calibration.state` as `Equivalent`.
DeviceMetric.calibration.timetime​is equivalent toDeviceMetric.calibration.timeDeviceMetric.calibration.timeElement `DeviceMetric.calibration.time` is mapped to FHIR STU3 element `DeviceMetric.calibration.time` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceMetric|5.0.0 to R5: Indicates how often the metric is taken or recorded (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceMetric.measurementFrequency (measurementFrequency)​maps to wider conceptExtension (R5: Indicates how often the metric is taken or recorded (new))Element `DeviceMetric.measurementFrequency` has a context of DeviceMetric based on following the parent source element upwards and mapping to `DeviceMetric`. Element `DeviceMetric.measurementFrequency` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).