FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.xver-r5.r3
Resource TypeConceptMap
IdConceptMap-R5-Device-element-map-to-R3.json
FHIR VersionR3
Sourcehttp://hl7.org/fhir/uv/xver-r5.r3/0.1.0/ConceptMap-R5-Device-element-map-to-R3.html
URLhttp://hl7.org/fhir/uv/xver/ConceptMap/R5-Device-element-map-to-R3
Version0.1.0
Statusactive
Date2026-03-17T16:05:15.2242115-05:00
NameR5DeviceElementMapToR3
TitleCross-version mapping for FHIR R5 Device to FHIR STU3 Device
Realmuv
Authorityhl7
DescriptionThis ConceptMap represents cross-version mappings for elements from a FHIR R5 Device to FHIR STU3.

Resources that use this resource

No resources found


Resources that this resource uses

StructureDefinition
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.availabilityStatusCross-version Extension for R5.Device.availabilityStatus for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.biologicalSourceEventCross-version Extension for R5.Device.biologicalSourceEvent for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.categoryCross-version Extension for R5.Device.category for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.cycleCross-version Extension for R5.Device.cycle for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.definitionCross-version Extension for R5.Device.definition for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.displayNameCross-version Extension for R5.Device.displayName for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.durationCross-version Extension for R5.Device.duration for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.endpointCross-version Extension for R5.Device.endpoint for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.gatewayCross-version Extension for R5.Device.gateway for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.modeCross-version Extension for R5.Device.mode for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.name.displayCross-version Extension for R5.Device.name.display for use in FHIR R4
hl7.fhir.uv.xver-r5.r3#0.1.0extension-Device.name.typeR5: registered-name | user-friendly-name | patient-reported-name (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-Device.name.valueR5: The term that names the device additional types
hl7.fhir.uv.xver-r5.r3#0.1.0extension-Device.parentR5: The higher level or encompassing device that this device is a logical part of (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-Device.partNumberR5: The part number or catalog number of the device (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-Device.propertyR5: Inherent, essentially fixed, characteristics of the device. e.g., time properties, size, material, etc. (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-Device.serialNumberR5: Serial number assigned by the manufacturer (new)
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.udiCarrier.entryTypeCross-version Extension for R5.Device.udiCarrier.entryType for use in FHIR R4
hl7.fhir.uv.xver-r5.r3#0.1.0extension-Device.version.componentR5: The hardware or software module of the device to which the version applies (new)
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-Device.version.installDateCross-version Extension for R5.Device.version.installDate for use in FHIR R4
hl7.fhir.uv.xver-r5.r3#0.1.0extension-Device.version.typeR5: The type of the device version, e.g. manufacturer, approved, internal (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-Device.version.valueR5: The version text (new)

Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ConceptMap R5-Device-element-map-to-R3

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


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

Source CodeRelationshipTarget CodeComment
Device.meta (meta)is equivalent toDevice.metaElement `Device.meta` is mapped to FHIR STU3 element `Device.meta` as `Equivalent`.
Device.implicitRules (implicitRules)is equivalent toDevice.implicitRulesElement `Device.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.
Device.language (language)is equivalent toDevice.languageElement `Device.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).
Device.text (text)is equivalent toDevice.textElement `Device.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.
Device.contained (contained)is equivalent toDevice.containedElement `Device.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.
Device.identifier (identifier)is equivalent toDevice.identifierElement `Device.identifier` is mapped to FHIR STU3 element `Device.identifier` as `Equivalent`. Certain attributes, like serial number and UDI Carrier (the HRF or AIDC barcode string) are not device instance identifiers as they are not consistently able to uniquely identify the instance of a device, thus are not appropriate to be used to value Device.identifier. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used. The identifier is typically valued if the serialNumber or lotNumber is not valued and represents a different type of identifier. However, it is permissible to still include those identifiers in DeviceDefinition.identifier with the appropriate identifier.type.
Device.displayName (displayName)is related toDevice.udiElement `Device.displayName` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`. The mappings for `Device.displayName` do not cover the following types: string. The mappings for `Device.displayName` do not cover the following types based on type expansion: value.
Device.udiCarrier (udiCarrier)maps to wider conceptDevice.udiElement `Device.udiCarrier` is mapped to FHIR STU3 element `Device.udi` as `SourceIsBroaderThanTarget`. UDI may identify an unique instance of a device, or it may only identify the type of the device. See [UDI mappings](https://hl7.org/fhir/devi.html#udi) for a complete mapping of UDI parts to Device.
Device.udiCarrier.deviceIdentifier (deviceIdentifier)is equivalent toDevice.udi.deviceIdentifierElement `Device.udiCarrier.deviceIdentifier` is mapped to FHIR STU3 element `Device.udi.deviceIdentifier` as `Equivalent`.
Device.udiCarrier.issuer (issuer)is equivalent toDevice.udi.issuerElement `Device.udiCarrier.issuer` is mapped to FHIR STU3 element `Device.udi.issuer` as `Equivalent`.
Device.udiCarrier.jurisdiction (jurisdiction)is equivalent toDevice.udi.jurisdictionElement `Device.udiCarrier.jurisdiction` is mapped to FHIR STU3 element `Device.udi.jurisdiction` as `Equivalent`.
Device.udiCarrier.carrierAIDC (carrierAIDC)is equivalent toDevice.udi.carrierAIDCElement `Device.udiCarrier.carrierAIDC` is mapped to FHIR STU3 element `Device.udi.carrierAIDC` as `Equivalent`. The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.
Device.udiCarrier.carrierHRF (carrierHRF)is equivalent toDevice.udi.carrierHRFElement `Device.udiCarrier.carrierHRF` is mapped to FHIR STU3 element `Device.udi.carrierHRF` as `Equivalent`. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.
Device.udiCarrier.entryType (entryType)is related toDevice.udi.entryTypeElement `Device.udiCarrier.entryType` is mapped to FHIR STU3 element `Device.udi.entryType` as `RelatedTo`. The mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target.
Device.status (status)is equivalent toDevice.statusElement `Device.status` is mapped to FHIR STU3 element `Device.status` as `SourceIsNarrowerThanTarget`. The mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target.
Device.manufacturer (manufacturer)is equivalent toDevice.manufacturerElement `Device.manufacturer` is mapped to FHIR STU3 element `Device.manufacturer` as `Equivalent`.
Device.manufactureDate (manufactureDate)is equivalent toDevice.manufactureDateElement `Device.manufactureDate` is mapped to FHIR STU3 element `Device.manufactureDate` as `Equivalent`.
Device.expirationDate (expirationDate)is equivalent toDevice.expirationDateElement `Device.expirationDate` is mapped to FHIR STU3 element `Device.expirationDate` as `Equivalent`.
Device.lotNumber (lotNumber)is equivalent toDevice.lotNumberElement `Device.lotNumber` is mapped to FHIR STU3 element `Device.lotNumber` as `Equivalent`.
Device.name (name)maps to wider conceptDevice.udiElement `Device.name` is mapped to FHIR STU3 element `Device.udi` as `SourceIsBroaderThanTarget`.
Device.name.value (value)is related toDevice.udiElement `Device.name.value` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`. The mappings for `Device.name.value` do not cover the following types: string. The mappings for `Device.name.value` do not cover the following types based on type expansion: value.
Device.name.display (display)is related toDevice.udiElement `Device.name.display` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`. The mappings for `Device.name.display` do not cover the following types: boolean. The mappings for `Device.name.display` do not cover the following types based on type expansion: value.
Device.modelNumber (modelNumber)is equivalent toDevice.modelElement `Device.modelNumber` is mapped to FHIR STU3 element `Device.model` as `Equivalent`.
Device.type (type)is equivalent toDevice.typeElement `Device.type` is mapped to FHIR STU3 element `Device.type` as `SourceIsBroaderThanTarget`. Multiple device types are use when a device is categorized in more than one context – for example, hybrid devices in which the device is both of type gateway and sensor.
Device.version (version)maps to wider conceptDevice.versionElement `Device.version` is mapped to FHIR STU3 element `Device.version` as `SourceIsBroaderThanTarget`.
Device.owner (owner)maps to wider conceptDevice.ownerElement `Device.owner` is mapped to FHIR STU3 element `Device.owner` as `SourceIsBroaderThanTarget`. The mappings for `Device.owner` 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 `Device.owner` with unmapped reference targets: Organization.
Device.contact (contact)is equivalent toDevice.contactElement `Device.contact` is mapped to FHIR STU3 element `Device.contact` as `Equivalent`. used for troubleshooting etc.
Device.location (location)maps to wider conceptDevice.locationElement `Device.location` is mapped to FHIR STU3 element `Device.location` as `SourceIsBroaderThanTarget`. The mappings for `Device.location` 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 `Device.location` with unmapped reference targets: Location.
Device.url (url)is equivalent toDevice.urlElement `Device.url` is mapped to FHIR STU3 element `Device.url` as `Equivalent`. If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.
Device.note (note)is equivalent toDevice.noteElement `Device.note` is mapped to FHIR STU3 element `Device.note` as `Equivalent`.
Device.safety (safety)is equivalent toDevice.safetyElement `Device.safety` is mapped to FHIR STU3 element `Device.safety` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The name used to display by default when the device is referenced additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.displayName (displayName)maps to wider conceptExtension (R5: The name used to display by default when the device is referenced additional types)Element `Device.displayName` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`. The mappings for `Device.displayName` do not cover the following types: string. The mappings for `Device.displayName` do not cover the following types based on type expansion: value.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The reference to the definition for the device (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.definition (definition)maps to wider conceptExtension (R5: The reference to the definition for the device (new))Element `Device.definition` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.definition` 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/Device|5.0.0 to R5: barcode | rfid | manual | card | self-reported | electronic-transmission | unknown additional codesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.udiCarrier.entryType (entryType)maps to wider conceptExtension (R5: barcode | rfid | manual | card | self-reported | electronic-transmission | unknown additional codes)Element `Device.udiCarrier.entryType` is mapped to FHIR STU3 element `Device.udi.entryType` as `RelatedTo`. The mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: lost | damaged | destroyed | available (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.availabilityStatus (availabilityStatus)maps to wider conceptExtension (R5: lost | damaged | destroyed | available (new))Element `Device.availabilityStatus` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.availabilityStatus` 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/Device|5.0.0 to R5: An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.biologicalSourceEvent (biologicalSourceEvent)maps to wider conceptExtension (R5: An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled (new))Element `Device.biologicalSourceEvent` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.biologicalSourceEvent` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Necessary to support mandatory requirements for traceability from donor/source to recipient and vice versa, while also satisfying donor anonymity requirements. The element is defined consistently across BiologicallyDerivedProduct, NutritionProduct, and Device. The identifier references an event that links to a single biological entity such as a blood donor, or to multiple biological entities (e.g. when the product is an embryo or a pooled platelet product). A single biologicalSourceEvent identifier may appear on multiple products of many types derived from a single donation event or source extraction. As an example, a single donation event may provide 2 kidneys and a liver for organ transplantation, 2 corneas for eye surgery, heart valves and arterial tissue for cardiovascular surgery, multiple skin grafts, tendons, multiple shaped bone grafts and a large number of bone putty/paste products; and each of them may be assigned to the same biological source event identifier.

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: Serial number assigned by the manufacturer (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.serialNumber (serialNumber)is equivalent toExtension (R5: Serial number assigned by the manufacturer (new))Element `Device.serialNumber` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.serialNumber` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Alphanumeric Maximum 20. While a serial number is a type of identifier, in the context of devices for which a UDI is required, thus a serial number may be part of the production identifier, it is more informative to have the serial number as a dedicated attribute together with the other UDI production identifier. When the device is not subject to including the UDI (e.g., its presence and exchange is not mandated by local regulatory requirements or specific use case at hand), thus the concept of production identifiers is not relevant as a set, it remains helpful for consistency to still use Device.serialNumber rather than using Device.identifier with an appropriate type. Systems that do not realize an identifier is a serial number may place it in Device.identifier or if the identifier.system is known for the serial number, it may also be populated in the Device.identifier as a globally unique id_.

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The term that names the device additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.name.value (value)maps to wider conceptExtension (R5: The term that names the device additional types)Element `Device.name.value` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`. The mappings for `Device.name.value` do not cover the following types: string. The mappings for `Device.name.value` do not cover the following types based on type expansion: value.

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: registered-name | user-friendly-name | patient-reported-name (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.name.type (type)maps to wider conceptExtension (R5: registered-name | user-friendly-name | patient-reported-name (new))Element `Device.name.type` has a context of Device.udi based on following the parent source element upwards and mapping to `Device`. Element `Device.name.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The preferred device name additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.name.display (display)maps to wider conceptExtension (R5: The preferred device name additional types)Element `Device.name.display` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`. The mappings for `Device.name.display` do not cover the following types: boolean. The mappings for `Device.name.display` do not cover the following types based on type expansion: value.

Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The part number or catalog number of the device (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.partNumber (partNumber)is equivalent toExtension (R5: The part number or catalog number of the device (new))Element `Device.partNumber` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.partNumber` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Alphanumeric Maximum 20.

Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: Indicates a high-level grouping of the device (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.category (category)maps to wider conceptExtension (R5: Indicates a high-level grouping of the device (new))Element `Device.category` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.category` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The type of the device version, e.g. manufacturer, approved, internal (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.version.type (type)is equivalent toExtension (R5: The type of the device version, e.g. manufacturer, approved, internal (new))Element `Device.version.type` has a context of Device.version based on following the parent source element upwards and mapping to `Device`. Element `Device.version.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The hardware or software module of the device to which the version applies (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.version.component (component)is equivalent toExtension (R5: The hardware or software module of the device to which the version applies (new))Element `Device.version.component` has a context of Device.version based on following the parent source element upwards and mapping to `Device`. Element `Device.version.component` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Note that the module of the device would not need to be tracked as a separate device, e.g., using different UDI, thus would typically involve one or more software modules. For example, a device may involve two software modules each on a different version.

Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The date the version was installed on the device (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.version.installDate (installDate)maps to wider conceptExtension (R5: The date the version was installed on the device (new))Element `Device.version.installDate` has a context of Device.version based on following the parent source element upwards and mapping to `Device`. Element `Device.version.installDate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The version text (new)version: 0.1.0)

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

Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: Inherent, essentially fixed, characteristics of the device. e.g., time properties, size, material, etc. (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.property (property)is equivalent toExtension (R5: Inherent, essentially fixed, characteristics of the device. e.g., time properties, size, material, etc. (new))Element `Device.property` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.property` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Dynamic or current properties, such as settings, of an individual device are described using a Device instance-specific [DeviceMetric] and recorded using [Observation]. Static characteristics of a device could also be documented in an associated [DeviceDefinition] instance. The Device instance's properties, and their values, could be, but need not be, the same as those described in an associated DeviceDefinition.
Device.property.type (type)is equivalent toExtension.extension:type (R5: Code that specifies the property being represented (new))Element `Device.property.type` is part of an existing definition because parent element `Device.property` requires a cross-version extension. Element `Device.property.type` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.property.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Device.property.value[x] (value[x])maps to wider conceptExtension.extension:value (R5: Value of the property (new))Element `Device.property.value[x]` is part of an existing definition because parent element `Device.property` requires a cross-version extension. Element `Device.property.value[x]` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.property.value[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The text element in CodeableConcept.text is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g. a custom implant size, or a security classification which depends on configuration). Otherwise the string choice type is used for descriptive properties, or instructions.

Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The designated condition for performing a task (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.mode (mode)maps to wider conceptExtension (R5: The designated condition for performing a task (new))Element `Device.mode` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.mode` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 19 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The series of occurrences that repeats during the operation of the device (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.cycle (cycle)maps to wider conceptExtension (R5: The series of occurrences that repeats during the operation of the device (new))Element `Device.cycle` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.cycle` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 20 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: A measurement of time during the device's operation (e.g., days, hours, mins, etc.) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.duration (duration)maps to wider conceptExtension (R5: A measurement of time during the device's operation (e.g., days, hours, mins, etc.) (new))Element `Device.duration` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.duration` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 21 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: Technical endpoints providing access to electronic services provided by the device (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.endpoint (endpoint)maps to wider conceptExtension (R5: Technical endpoints providing access to electronic services provided by the device (new))Element `Device.endpoint` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.endpoint` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 22 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: Linked device acting as a communication/data collector, translator or controller (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.gateway (gateway)maps to wider conceptExtension (R5: Linked device acting as a communication/data collector, translator or controller (new))Element `Device.gateway` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.gateway` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The Device.gateway may be used when the Device being referenced has a gateway and/or to capture one or more gateways associated with the device. If the Gateway is included in the Observation resource, the Observation.gatewayDevice should be used instead.

Group 23 Mapping from http://hl7.org/fhir/StructureDefinition/Device|5.0.0 to R5: The higher level or encompassing device that this device is a logical part of (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Device.parent (parent)is equivalent toExtension (R5: The higher level or encompassing device that this device is a logical part of (new))Element `Device.parent` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.parent` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). For example a vital signs monitor (parent) where three separate modules can be plugged into such as interchangeable blood pressure, oximeter, temperature modules. These modules are represented as devices with the .parent valued to the vital signs monitor when plugged in.

Source1

{
  "resourceType": "ConceptMap",
  "id": "R5-Device-element-map-to-R3",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-Device-element-map-to-R3",
  "version": "0.1.0",
  "name": "R5DeviceElementMapToR3",
  "title": "Cross-version mapping for FHIR R5 Device to FHIR STU3 Device",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:05:15.2242115-05:00",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This ConceptMap represents cross-version mappings for elements from a FHIR R5 Device to FHIR STU3.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceUri": "http://hl7.org/fhir/5.0",
  "targetUri": "http://hl7.org/fhir/3.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/StructureDefinition/Device",
      "targetVersion": "3.0.2",
      "element": [
        {
          "code": "Device.meta",
          "display": "meta",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.meta",
              "display": "Device.meta",
              "equivalence": "equivalent",
              "comment": "Element `Device.meta` is mapped to FHIR STU3 element `Device.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.implicitRules",
              "display": "Device.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element `Device.implicitRules` is mapped to FHIR STU3 element `Device.implicitRules` as `Equivalent`.\nAsserting 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."
            }
          ]
        },
        {
          "code": "Device.language",
          "display": "language",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.language",
              "display": "Device.language",
              "equivalence": "equivalent",
              "comment": "Element `Device.language` is mapped to FHIR STU3 element `Device.language` as `Equivalent`.\nLanguage 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)."
            }
          ]
        },
        {
          "code": "Device.text",
          "display": "text",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.text",
              "display": "Device.text",
              "equivalence": "equivalent",
              "comment": "Element `Device.text` is mapped to FHIR STU3 element `Device.text` as `Equivalent`.\nContained 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."
            }
          ]
        },
        {
          "code": "Device.contained",
          "display": "contained",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.contained",
              "display": "Device.contained",
              "equivalence": "equivalent",
              "comment": "Element `Device.contained` is mapped to FHIR STU3 element `Device.contained` as `SourceIsBroaderThanTarget`.\nThis 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."
            }
          ]
        },
        {
          "code": "Device.identifier",
          "display": "identifier",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.identifier",
              "display": "Device.identifier",
              "equivalence": "equivalent",
              "comment": "Element `Device.identifier` is mapped to FHIR STU3 element `Device.identifier` as `Equivalent`.\nCertain attributes, like serial number and UDI Carrier (the HRF or AIDC barcode string) are not device instance identifiers as they are not consistently able to uniquely identify the instance of a device, thus are not appropriate to be used to value Device.identifier. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used. The identifier is typically valued if the serialNumber or lotNumber is not valued and represents a different type of identifier.  However, it is permissible to still include those identifiers in DeviceDefinition.identifier with the appropriate identifier.type."
            }
          ]
        },
        {
          "code": "Device.displayName",
          "display": "displayName",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "relatedto"
                }
              ],
              "code": "Device.udi",
              "display": "Device.udi",
              "equivalence": "relatedto",
              "comment": "Element `Device.displayName` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`.\nThe mappings for `Device.displayName` do not cover the following types: string.\nThe mappings for `Device.displayName` do not cover the following types based on type expansion: value."
            }
          ]
        },
        {
          "code": "Device.udiCarrier",
          "display": "udiCarrier",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Device.udi",
              "display": "Device.udi",
              "equivalence": "wider",
              "comment": "Element `Device.udiCarrier` is mapped to FHIR STU3 element `Device.udi` as `SourceIsBroaderThanTarget`.\nUDI may identify an unique instance of a device, or it may only identify the type of the device.  See [UDI mappings](https://hl7.org/fhir/devi.html#udi) for a complete mapping of UDI parts to Device."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.deviceIdentifier",
          "display": "deviceIdentifier",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.udi.deviceIdentifier",
              "display": "Device.udi.deviceIdentifier",
              "equivalence": "equivalent",
              "comment": "Element `Device.udiCarrier.deviceIdentifier` is mapped to FHIR STU3 element `Device.udi.deviceIdentifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.issuer",
          "display": "issuer",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.udi.issuer",
              "display": "Device.udi.issuer",
              "equivalence": "equivalent",
              "comment": "Element `Device.udiCarrier.issuer` is mapped to FHIR STU3 element `Device.udi.issuer` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.jurisdiction",
          "display": "jurisdiction",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.udi.jurisdiction",
              "display": "Device.udi.jurisdiction",
              "equivalence": "equivalent",
              "comment": "Element `Device.udiCarrier.jurisdiction` is mapped to FHIR STU3 element `Device.udi.jurisdiction` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.carrierAIDC",
          "display": "carrierAIDC",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.udi.carrierAIDC",
              "display": "Device.udi.carrierAIDC",
              "equivalence": "equivalent",
              "comment": "Element `Device.udiCarrier.carrierAIDC` is mapped to FHIR STU3 element `Device.udi.carrierAIDC` as `Equivalent`.\nThe AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.carrierHRF",
          "display": "carrierHRF",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.udi.carrierHRF",
              "display": "Device.udi.carrierHRF",
              "equivalence": "equivalent",
              "comment": "Element `Device.udiCarrier.carrierHRF` is mapped to FHIR STU3 element `Device.udi.carrierHRF` as `Equivalent`.\nIf separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label."
            }
          ]
        },
        {
          "code": "Device.udiCarrier.entryType",
          "display": "entryType",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "relatedto"
                }
              ],
              "code": "Device.udi.entryType",
              "display": "Device.udi.entryType",
              "equivalence": "relatedto",
              "comment": "Element `Device.udiCarrier.entryType` is mapped to FHIR STU3 element `Device.udi.entryType` as `RelatedTo`.\nThe mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        },
        {
          "code": "Device.status",
          "display": "status",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.status",
              "display": "Device.status",
              "equivalence": "equivalent",
              "comment": "Element `Device.status` is mapped to FHIR STU3 element `Device.status` as `SourceIsNarrowerThanTarget`.\nThe mappings for `Device.status` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        },
        {
          "code": "Device.manufacturer",
          "display": "manufacturer",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.manufacturer",
              "display": "Device.manufacturer",
              "equivalence": "equivalent",
              "comment": "Element `Device.manufacturer` is mapped to FHIR STU3 element `Device.manufacturer` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.manufactureDate",
          "display": "manufactureDate",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.manufactureDate",
              "display": "Device.manufactureDate",
              "equivalence": "equivalent",
              "comment": "Element `Device.manufactureDate` is mapped to FHIR STU3 element `Device.manufactureDate` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.expirationDate",
          "display": "expirationDate",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.expirationDate",
              "display": "Device.expirationDate",
              "equivalence": "equivalent",
              "comment": "Element `Device.expirationDate` is mapped to FHIR STU3 element `Device.expirationDate` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.lotNumber",
          "display": "lotNumber",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.lotNumber",
              "display": "Device.lotNumber",
              "equivalence": "equivalent",
              "comment": "Element `Device.lotNumber` is mapped to FHIR STU3 element `Device.lotNumber` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.name",
          "display": "name",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Device.udi",
              "display": "Device.udi",
              "equivalence": "wider",
              "comment": "Element `Device.name` is mapped to FHIR STU3 element `Device.udi` as `SourceIsBroaderThanTarget`."
            }
          ]
        },
        {
          "code": "Device.name.value",
          "display": "value",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "relatedto"
                }
              ],
              "code": "Device.udi",
              "display": "Device.udi",
              "equivalence": "relatedto",
              "comment": "Element `Device.name.value` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`.\nThe mappings for `Device.name.value` do not cover the following types: string.\nThe mappings for `Device.name.value` do not cover the following types based on type expansion: value."
            }
          ]
        },
        {
          "code": "Device.name.display",
          "display": "display",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "relatedto"
                }
              ],
              "code": "Device.udi",
              "display": "Device.udi",
              "equivalence": "relatedto",
              "comment": "Element `Device.name.display` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`.\nThe mappings for `Device.name.display` do not cover the following types: boolean.\nThe mappings for `Device.name.display` do not cover the following types based on type expansion: value."
            }
          ]
        },
        {
          "code": "Device.modelNumber",
          "display": "modelNumber",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.model",
              "display": "Device.model",
              "equivalence": "equivalent",
              "comment": "Element `Device.modelNumber` is mapped to FHIR STU3 element `Device.model` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.type",
          "display": "type",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.type",
              "display": "Device.type",
              "equivalence": "equivalent",
              "comment": "Element `Device.type` is mapped to FHIR STU3 element `Device.type` as `SourceIsBroaderThanTarget`.\nMultiple device types are use when a device is categorized in more than one context – for example, hybrid devices in which the device is both of type gateway and sensor."
            }
          ]
        },
        {
          "code": "Device.version",
          "display": "version",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Device.version",
              "display": "Device.version",
              "equivalence": "wider",
              "comment": "Element `Device.version` is mapped to FHIR STU3 element `Device.version` as `SourceIsBroaderThanTarget`."
            }
          ]
        },
        {
          "code": "Device.owner",
          "display": "owner",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Device.owner",
              "display": "Device.owner",
              "equivalence": "wider",
              "comment": "Element `Device.owner` is mapped to FHIR STU3 element `Device.owner` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.owner` do not cover the following types based on type expansion: display, identifier, reference, type.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Device.owner` with unmapped reference targets: Organization."
            }
          ]
        },
        {
          "code": "Device.contact",
          "display": "contact",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.contact",
              "display": "Device.contact",
              "equivalence": "equivalent",
              "comment": "Element `Device.contact` is mapped to FHIR STU3 element `Device.contact` as `Equivalent`.\nused for troubleshooting etc."
            }
          ]
        },
        {
          "code": "Device.location",
          "display": "location",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Device.location",
              "display": "Device.location",
              "equivalence": "wider",
              "comment": "Element `Device.location` is mapped to FHIR STU3 element `Device.location` as `SourceIsBroaderThanTarget`.\nThe mappings for `Device.location` do not cover the following types based on type expansion: display, identifier, reference, type.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Device.location` with unmapped reference targets: Location."
            }
          ]
        },
        {
          "code": "Device.url",
          "display": "url",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.url",
              "display": "Device.url",
              "equivalence": "equivalent",
              "comment": "Element `Device.url` is mapped to FHIR STU3 element `Device.url` as `Equivalent`.\nIf the device is running a FHIR server, the network address should  be the Base URL from which a conformance statement may be retrieved."
            }
          ]
        },
        {
          "code": "Device.note",
          "display": "note",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.note",
              "display": "Device.note",
              "equivalence": "equivalent",
              "comment": "Element `Device.note` is mapped to FHIR STU3 element `Device.note` as `Equivalent`."
            }
          ]
        },
        {
          "code": "Device.safety",
          "display": "safety",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Device.safety",
              "display": "Device.safety",
              "equivalence": "equivalent",
              "comment": "Element `Device.safety` is mapped to FHIR STU3 element `Device.safety` as `Equivalent`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.displayName",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.displayName",
          "display": "displayName",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.displayName` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`.\nThe mappings for `Device.displayName` do not cover the following types: string.\nThe mappings for `Device.displayName` do not cover the following types based on type expansion: value."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.definition",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.definition",
          "display": "definition",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.definition` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.definition` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.udiCarrier.entryType",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.udiCarrier.entryType",
          "display": "entryType",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.udiCarrier.entryType` is mapped to FHIR STU3 element `Device.udi.entryType` as `RelatedTo`.\nThe mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.availabilityStatus",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.availabilityStatus",
          "display": "availabilityStatus",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.availabilityStatus` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.availabilityStatus` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.biologicalSourceEvent",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.biologicalSourceEvent",
          "display": "biologicalSourceEvent",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.biologicalSourceEvent` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.biologicalSourceEvent` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nNecessary to support mandatory requirements for traceability from donor/source to recipient and vice versa, while also satisfying donor anonymity requirements. The element is defined consistently across BiologicallyDerivedProduct, NutritionProduct, and Device.  The identifier references an event that links to a single biological entity such as a blood donor, or to multiple biological entities (e.g. when the product is an embryo or a pooled platelet product).  A single biologicalSourceEvent identifier may appear on multiple products of many types derived from a single donation event or source extraction.  As an example, a single donation event may provide 2 kidneys and a liver for organ transplantation, 2 corneas for eye surgery, heart valves and arterial tissue for cardiovascular surgery, multiple skin grafts, tendons, multiple shaped bone grafts and a large number of bone putty/paste products; and each of them may be assigned to the same biological source event identifier."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.serialNumber",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.serialNumber",
          "display": "serialNumber",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `Device.serialNumber` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.serialNumber` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nAlphanumeric Maximum 20. While a serial number is a type of identifier, in the context of devices for which a UDI is required, thus a serial number may be part of the production identifier, it is more informative to have the serial number as a dedicated attribute together with the other UDI production identifier.  When the device is not subject to including the UDI (e.g., its presence and exchange is not mandated by local regulatory requirements or specific use case at hand), thus the concept of production identifiers is not relevant as a set, it remains helpful for consistency to still use Device.serialNumber rather than using Device.identifier with an appropriate type.  Systems that do not realize an identifier is a serial number may place it in Device.identifier or if the identifier.system is known for the serial number, it may also be populated in the Device.identifier as a globally unique id_."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.name.value",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.name.value",
          "display": "value",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.name.value` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`.\nThe mappings for `Device.name.value` do not cover the following types: string.\nThe mappings for `Device.name.value` do not cover the following types based on type expansion: value."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.name.type",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.name.type",
          "display": "type",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.name.type` has a context of Device.udi based on following the parent source element upwards and mapping to `Device`.\nElement `Device.name.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.name.display",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.name.display",
          "display": "display",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.name.display` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`.\nThe mappings for `Device.name.display` do not cover the following types: boolean.\nThe mappings for `Device.name.display` do not cover the following types based on type expansion: value."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.partNumber",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.partNumber",
          "display": "partNumber",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `Device.partNumber` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.partNumber` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nAlphanumeric Maximum 20."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.category",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.category",
          "display": "category",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.category` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.category` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.version.type",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.version.type",
          "display": "type",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `Device.version.type` has a context of Device.version based on following the parent source element upwards and mapping to `Device`.\nElement `Device.version.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.version.component",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.version.component",
          "display": "component",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `Device.version.component` has a context of Device.version based on following the parent source element upwards and mapping to `Device`.\nElement `Device.version.component` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nNote that the module of the device would not need to be tracked as a separate device, e.g., using different UDI, thus would typically involve one or more software modules. For example, a device may involve two software modules each on a different version."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.version.installDate",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.version.installDate",
          "display": "installDate",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.version.installDate` has a context of Device.version based on following the parent source element upwards and mapping to `Device`.\nElement `Device.version.installDate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.version.value",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.version.value",
          "display": "value",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `Device.version.value` has a context of Device.version based on following the parent source element upwards and mapping to `Device`.\nElement `Device.version.value` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.property",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.property",
          "display": "property",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `Device.property` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.property` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nDynamic or current properties, such as settings, of an individual device are described using a Device instance-specific [DeviceMetric] and recorded using [Observation].  Static characteristics of a device could also be documented in an associated [DeviceDefinition] instance. The Device instance's properties, and their values, could be, but need not be, the same as those described in an associated DeviceDefinition."
            }
          ]
        },
        {
          "code": "Device.property.type",
          "display": "type",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Extension.extension:type",
              "equivalence": "equivalent",
              "comment": "Element `Device.property.type` is part of an existing definition because parent element `Device.property` requires a cross-version extension.\nElement `Device.property.type` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.property.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "Device.property.value[x]",
          "display": "value[x]",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:value",
              "equivalence": "wider",
              "comment": "Element `Device.property.value[x]` is part of an existing definition because parent element `Device.property` requires a cross-version extension.\nElement `Device.property.value[x]` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.property.value[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe text element in CodeableConcept.text is used for properties which would usually be coded (such as the size of an implant, or a security classification) but for which there is not currently an appropriate concept in the vocabulary (e.g. a custom implant size, or a security classification which depends on configuration). Otherwise the string choice type is used for descriptive properties, or instructions."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.mode",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.mode",
          "display": "mode",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.mode` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.mode` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.cycle",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.cycle",
          "display": "cycle",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.cycle` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.cycle` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.duration",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.duration",
          "display": "duration",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.duration` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.duration` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.endpoint",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.endpoint",
          "display": "endpoint",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.endpoint` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.endpoint` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.gateway",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.gateway",
          "display": "gateway",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `Device.gateway` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.gateway` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe Device.gateway may be used when the Device being referenced has a gateway and/or to capture one or more gateways associated with the device. If the Gateway is included in the Observation resource, the Observation.gatewayDevice should be used instead."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/Device",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.parent",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "Device.parent",
          "display": "parent",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `Device.parent` has a context of Device based on following the parent source element upwards and mapping to `Device`.\nElement `Device.parent` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nFor example a vital signs monitor (parent) where three separate modules can be plugged into such as interchangeable blood pressure, oximeter, temperature modules.  These modules are represented as devices with the .parent valued to the vital signs monitor when plugged in."
            }
          ]
        }
      ]
    }
  ]
}