Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR STU3 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R5-DeviceAssociation-element-map-to-R3 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R5DeviceAssociationElementMapToR3 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR R5 DeviceAssociation 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/DeviceAssociation|5.0.0 to http://hl7.org/fhir/StructureDefinition/Device|3.0.2
| Source Code | Relationship | Target Code | Comment |
| DeviceAssociation.meta (meta) | is equivalent to | Device.meta | Element `DeviceAssociation.meta` is mapped to FHIR STU3 element `Device.meta` as `Equivalent`. |
| DeviceAssociation.implicitRules (implicitRules) | is equivalent to | Device.implicitRules | Element `DeviceAssociation.implicitRules` is mapped to FHIR STU3 element `Device.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. |
| DeviceAssociation.language (language) | is equivalent to | Device.language | Element `DeviceAssociation.language` is mapped to FHIR STU3 element `Device.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). |
| DeviceAssociation.text (text) | is equivalent to | Device.text | Element `DeviceAssociation.text` is mapped to FHIR STU3 element `Device.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. |
| DeviceAssociation.contained (contained) | is equivalent to | Device.contained | Element `DeviceAssociation.contained` is mapped to FHIR STU3 element `Device.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. |
| DeviceAssociation.identifier (identifier) | is equivalent to | Device.identifier | Element `DeviceAssociation.identifier` is mapped to FHIR STU3 element `Device.identifier` as `Equivalent`. |
| DeviceAssociation.subject (subject) | maps to wider concept | Device.patient | Element `DeviceAssociation.subject` is mapped to FHIR STU3 element `Device.patient` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DeviceAssociation.subject` with unmapped reference targets: Device, Group, Patient, Practitioner, RelatedPerson. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceAssociation|5.0.0 to R5: Reference to the devices associated with the patient or group (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceAssociation.device (device) | maps to wider concept | Extension (R5: Reference to the devices associated with the patient or group (new)) | Element `DeviceAssociation.device` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `DeviceAssociation.device` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceAssociation|5.0.0 to R5: Describes the relationship between the device and subject (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceAssociation.category (category) | maps to wider concept | Extension (R5: Describes the relationship between the device and subject (new)) | Element `DeviceAssociation.category` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `DeviceAssociation.category` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceAssociation|5.0.0 to R5: implanted | explanted | attached | entered-in-error | unknown (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceAssociation.status (status) | is equivalent to | Extension (R5: implanted | explanted | attached | entered-in-error | unknown (new)) | Element `DeviceAssociation.status` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `DeviceAssociation.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceAssociation|5.0.0 to R5: The reasons given for the current association status (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceAssociation.statusReason (statusReason) | is equivalent to | Extension (R5: The reasons given for the current association status (new)) | Element `DeviceAssociation.statusReason` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `DeviceAssociation.statusReason` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceAssociation|5.0.0 to R5: Current anatomical location of the device in/on subject (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceAssociation.bodyStructure (bodyStructure) | maps to wider concept | Extension (R5: Current anatomical location of the device in/on subject (new)) | Element `DeviceAssociation.bodyStructure` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `DeviceAssociation.bodyStructure` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceAssociation|5.0.0 to R5: Begin and end dates and times for the device association (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceAssociation.period (period) | maps to wider concept | Extension (R5: Begin and end dates and times for the device association (new)) | Element `DeviceAssociation.period` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `DeviceAssociation.period` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceAssociation|5.0.0 to R5: The details about the device when it is in use to describe its operation (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DeviceAssociation.operation (operation) | maps to wider concept | Extension (R5: The details about the device when it is in use to describe its operation (new)) | Element `DeviceAssociation.operation` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `DeviceAssociation.operation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
| DeviceAssociation.operation.status (status) | maps to wider concept | Extension.extension:status (R5: Device operational condition (new)) | Element `DeviceAssociation.operation.status` is part of an existing definition because parent element `DeviceAssociation.operation` requires a cross-version extension. Element `DeviceAssociation.operation.status` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `DeviceAssociation.operation.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
| DeviceAssociation.operation.operator (operator) | maps to wider concept | Extension.extension:operator (R5: The individual performing the action enabled by the device (new)) | Element `DeviceAssociation.operation.operator` is part of an existing definition because parent element `DeviceAssociation.operation` requires a cross-version extension. Element `DeviceAssociation.operation.operator` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `DeviceAssociation.operation.operator` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
| DeviceAssociation.operation.period (period) | maps to wider concept | Extension.extension:period (R5: Begin and end dates and times for the device's operation (new)) | Element `DeviceAssociation.operation.period` is part of an existing definition because parent element `DeviceAssociation.operation` requires a cross-version extension. Element `DeviceAssociation.operation.period` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `DeviceAssociation.operation.period` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r5.r3#0.1.0 based on FHIR 3.0.2. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change