Extensions for Using Data Elements from FHIR R4B in FHIR R4
0.1.0 - STU International flag

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

ConceptMap: R4BDeviceMetricElementMapToR4

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

This ConceptMap represents cross-version mappings for elements from a FHIR R4B DeviceMetric to FHIR R4.

Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/4.0


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

Source CodeRelationshipTarget CodeComment
DeviceMetric.meta (meta)is equivalent toDeviceMetric.metaElement `DeviceMetric.meta` is mapped to FHIR R4 element `DeviceMetric.meta` as `Equivalent`.
DeviceMetric.implicitRules (implicitRules)is equivalent toDeviceMetric.implicitRulesElement `DeviceMetric.implicitRules` is mapped to FHIR R4 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 it's narrative along with other profiles, value sets, etc.
DeviceMetric.language (language)is equivalent toDeviceMetric.languageElement `DeviceMetric.language` is mapped to FHIR R4 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 equivalent toDeviceMetric.textElement `DeviceMetric.text` is mapped to FHIR R4 element `DeviceMetric.text` as `Equivalent`. 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 information is added later.
DeviceMetric.contained (contained)is equivalent toDeviceMetric.containedElement `DeviceMetric.contained` is mapped to FHIR R4 element `DeviceMetric.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.
DeviceMetric.identifier (identifier)is equivalent toDeviceMetric.identifierElement `DeviceMetric.identifier` is mapped to FHIR R4 element `DeviceMetric.identifier` as `Equivalent`. For identifiers assigned to a device by the device or gateway software, the `system` element of the identifier should be set to the unique identifier of the device.
DeviceMetric.type (type)is equivalent toDeviceMetric.typeElement `DeviceMetric.type` is mapped to FHIR R4 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 R4 element `DeviceMetric.unit` as `Equivalent`. DeviceMetric.unit can refer to either UCUM or preferable a RTMMS coding system.
DeviceMetric.source (source)is equivalent toDeviceMetric.sourceElement `DeviceMetric.source` is mapped to FHIR R4 element `DeviceMetric.source` as `Equivalent`.
DeviceMetric.parent (parent)is equivalent toDeviceMetric.parentElement `DeviceMetric.parent` is mapped to FHIR R4 element `DeviceMetric.parent` as `Equivalent`.
DeviceMetric.operationalStatus (operationalStatus)is equivalent toDeviceMetric.operationalStatusElement `DeviceMetric.operationalStatus` is mapped to FHIR R4 element `DeviceMetric.operationalStatus` as `Equivalent`.
DeviceMetric.color (color)is equivalent toDeviceMetric.colorElement `DeviceMetric.color` is mapped to FHIR R4 element `DeviceMetric.color` as `Equivalent`.
DeviceMetric.category (category)is equivalent toDeviceMetric.categoryElement `DeviceMetric.category` is mapped to FHIR R4 element `DeviceMetric.category` as `Equivalent`.
DeviceMetric.measurementPeriod (measurementPeriod)is equivalent toDeviceMetric.measurementPeriodElement `DeviceMetric.measurementPeriod` is mapped to FHIR R4 element `DeviceMetric.measurementPeriod` as `Equivalent`.
DeviceMetric.calibration (calibration)maps to wider conceptDeviceMetric.calibrationElement `DeviceMetric.calibration` is mapped to FHIR R4 element `DeviceMetric.calibration` as `Equivalent`.
DeviceMetric.calibration.type (type)is equivalent toDeviceMetric.calibration.typeElement `DeviceMetric.calibration.type` is mapped to FHIR R4 element `DeviceMetric.calibration.type` as `Equivalent`.
DeviceMetric.calibration.state (state)is equivalent toDeviceMetric.calibration.stateElement `DeviceMetric.calibration.state` is mapped to FHIR R4 element `DeviceMetric.calibration.state` as `Equivalent`.
DeviceMetric.calibration.time (time)is equivalent toDeviceMetric.calibration.timeElement `DeviceMetric.calibration.time` is mapped to FHIR R4 element `DeviceMetric.calibration.time` as `Equivalent`.