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

FHIR IG analytics

Packagehl7.fhir.uv.xver-r5.r4
Resource TypeConceptMap
IdConceptMap-R5-DeviceDefinition-element-map-to-R4.json
FHIR VersionR4
Sourcehttp://hl7.org/fhir/uv/xver-r5.r4/0.1.0/ConceptMap-R5-DeviceDefinition-element-map-to-R4.html
URLhttp://hl7.org/fhir/uv/xver/ConceptMap/R5-DeviceDefinition-element-map-to-R4
Version0.1.0
Statusactive
Date2026-03-17T16:04:44.9668049-05:00
NameR5DeviceDefinitionElementMapToR4
TitleCross-version mapping for FHIR R5 DeviceDefinition to FHIR R4 DeviceDefinition
Realmuv
Authorityhl7
DescriptionThis ConceptMap represents cross-version mappings for elements from a FHIR R5 DeviceDefinition to FHIR R4.

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-DeviceDefinition.chargeItemCross-version Extension for R5.DeviceDefinition.chargeItem for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-DeviceDefinition.classificationCross-version Extension for R5.DeviceDefinition.classification for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-DeviceDefinition.correctiveActionCross-version Extension for R5.DeviceDefinition.correctiveAction for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-DeviceDefinition.guidelineCross-version Extension for R5.DeviceDefinition.guideline for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-DeviceDefinition.hasPartCross-version Extension for R5.DeviceDefinition.hasPart for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-DeviceDefinition.linkCross-version Extension for R5.DeviceDefinition.link for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-DeviceDefinition.packagingCross-version Extension for R5.DeviceDefinition.packaging for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-DeviceDefinition.partNumberCross-version Extension for R5.DeviceDefinition.partNumber for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-DeviceDefinition.productionIdentifierInUDICross-version Extension for R5.DeviceDefinition.productionIdentifierInUDI for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-DeviceDefinition.property.valueCross-version Extension for R5.DeviceDefinition.property.value[x] for use in FHIR R4
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-DeviceDefinition.regulatoryIdentifierCross-version Extension for R5.DeviceDefinition.regulatoryIdentifier for use in FHIR R4
hl7.fhir.uv.xver-r5.r4#0.1.0extension-DeviceDefinition.udiDeviceIdentifierR5: udiDeviceIdentifier
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-DeviceDefinition.udiDeviceIdentifier.marketDistributionCross-version Extension for R5.DeviceDefinition.udiDeviceIdentifier.marketDistribution for use in FHIR R4
hl7.fhir.uv.xver-r5.r4#0.1.0extension-DeviceDefinition.version.componentR5: The hardware or software module of the device to which the version applies (new)
hl7.fhir.uv.xver-r5.r4#0.1.0extension-DeviceDefinition.version.typeR5: The type of the device version, e.g. manufacturer, approved, internal (new)
hl7.fhir.uv.xver-r5.r4#0.1.0extension-DeviceDefinition.version.valueR5: The version text (new)

Narrative

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

Generated Narrative: ConceptMap R5-DeviceDefinition-element-map-to-R4

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to DeviceDefinitionversion: 4.0.1)

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0Codes from DeviceDefinition
DeviceDefinition.metametais equivalent toDeviceDefinition.metaDeviceDefinition.metaElement `DeviceDefinition.meta` is mapped to FHIR R4 element `DeviceDefinition.meta` as `Equivalent`.
DeviceDefinition.implicitRulesimplicitRulesis equivalent toDeviceDefinition.implicitRulesDeviceDefinition.implicitRulesElement `DeviceDefinition.implicitRules` is mapped to FHIR R4 element `DeviceDefinition.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.
DeviceDefinition.languagelanguageis equivalent toDeviceDefinition.languageDeviceDefinition.languageElement `DeviceDefinition.language` is mapped to FHIR R4 element `DeviceDefinition.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).
DeviceDefinition.texttextis equivalent toDeviceDefinition.textDeviceDefinition.textElement `DeviceDefinition.text` is mapped to FHIR R4 element `DeviceDefinition.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.
DeviceDefinition.containedcontainedis equivalent toDeviceDefinition.containedDeviceDefinition.containedElement `DeviceDefinition.contained` is mapped to FHIR R4 element `DeviceDefinition.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
DeviceDefinition.identifieridentifieris equivalent toDeviceDefinition.identifierDeviceDefinition.identifierElement `DeviceDefinition.identifier` is mapped to FHIR R4 element `DeviceDefinition.identifier` as `Equivalent`.
DeviceDefinition.udiDeviceIdentifierudiDeviceIdentifiermaps to wider conceptDeviceDefinition.udiDeviceIdentifierDeviceDefinition.udiDeviceIdentifierElement `DeviceDefinition.udiDeviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier` as `Equivalent`.
DeviceDefinition.udiDeviceIdentifier.deviceIdentifierdeviceIdentifieris equivalent toDeviceDefinition.udiDeviceIdentifier.deviceIdentifierDeviceDefinition.udiDeviceIdentifier.deviceIdentifierElement `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` as `Equivalent`.
DeviceDefinition.udiDeviceIdentifier.issuerissueris equivalent toDeviceDefinition.udiDeviceIdentifier.issuerDeviceDefinition.udiDeviceIdentifier.issuerElement `DeviceDefinition.udiDeviceIdentifier.issuer` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.issuer` as `Equivalent`.
DeviceDefinition.udiDeviceIdentifier.jurisdictionjurisdictionis equivalent toDeviceDefinition.udiDeviceIdentifier.jurisdictionDeviceDefinition.udiDeviceIdentifier.jurisdictionElement `DeviceDefinition.udiDeviceIdentifier.jurisdiction` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` as `Equivalent`.
DeviceDefinition.manufacturermanufactureris equivalent toDeviceDefinition.manufacturer[x]DeviceDefinition.manufacturer[x]Element `DeviceDefinition.manufacturer` is mapped to FHIR R4 element `DeviceDefinition.manufacturer[x]` as `Equivalent`. The target context `DeviceDefinition.manufacturer[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceDefinition`.
DeviceDefinition.deviceNamedeviceNamemaps to wider conceptDeviceDefinition.deviceNameDeviceDefinition.deviceNameElement `DeviceDefinition.deviceName` is mapped to FHIR R4 element `DeviceDefinition.deviceName` as `Equivalent`.
DeviceDefinition.deviceName.namenameis equivalent toDeviceDefinition.deviceName.nameDeviceDefinition.deviceName.nameElement `DeviceDefinition.deviceName.name` is mapped to FHIR R4 element `DeviceDefinition.deviceName.name` as `Equivalent`.
DeviceDefinition.deviceName.typetypeis equivalent toDeviceDefinition.deviceName.typeDeviceDefinition.deviceName.typeElement `DeviceDefinition.deviceName.type` is mapped to FHIR R4 element `DeviceDefinition.deviceName.type` as `SourceIsNarrowerThanTarget`. The mappings for `DeviceDefinition.deviceName.type` do not allow expression of the necessary codes, per the bindings on the source and target.
DeviceDefinition.modelNumbermodelNumberis equivalent toDeviceDefinition.modelNumberDeviceDefinition.modelNumberElement `DeviceDefinition.modelNumber` is mapped to FHIR R4 element `DeviceDefinition.modelNumber` as `Equivalent`.
DeviceDefinition.conformsToconformsTomaps to wider conceptDeviceDefinition.specializationDeviceDefinition.specializationElement `DeviceDefinition.conformsTo` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `Equivalent`. An externally-defined extension that has been mapped as the representation of FHIR R5 element `DeviceDefinition.conformsTo`: `http://hl7.org/fhir/StructureDefinition/device-conformsTo`.
DeviceDefinition.conformsTo.categorycategorynarrowerDeviceDefinition.specializationDeviceDefinition.specializationElement `DeviceDefinition.conformsTo.category` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `SourceIsNarrowerThanTarget`.
DeviceDefinition.conformsTo.specificationspecificationnarrowerDeviceDefinition.specializationDeviceDefinition.specializationElement `DeviceDefinition.conformsTo.specification` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `SourceIsNarrowerThanTarget`.
DeviceDefinition.conformsTo.versionversionis equivalent toDeviceDefinition.specialization.versionDeviceDefinition.specialization.versionElement `DeviceDefinition.conformsTo.version` is mapped to FHIR R4 element `DeviceDefinition.specialization.version` as `SourceIsBroaderThanTarget`.
DeviceDefinition.conformsTo.sourcesourceis equivalent toDeviceDefinition.specializationDeviceDefinition.specializationElement `DeviceDefinition.conformsTo.source` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `Equivalent`.
DeviceDefinition.versionversionmaps to wider conceptDeviceDefinition.versionDeviceDefinition.versionElement `DeviceDefinition.version` is mapped to FHIR R4 element `DeviceDefinition.version` as `Equivalent`.
DeviceDefinition.safetysafetyis equivalent toDeviceDefinition.safetyDeviceDefinition.safetyElement `DeviceDefinition.safety` is mapped to FHIR R4 element `DeviceDefinition.safety` as `Equivalent`.
DeviceDefinition.shelfLifeStorageshelfLifeStorageis equivalent toDeviceDefinition.shelfLifeStorageDeviceDefinition.shelfLifeStorageElement `DeviceDefinition.shelfLifeStorage` is mapped to FHIR R4 element `DeviceDefinition.shelfLifeStorage` as `Equivalent`.
DeviceDefinition.languageCodelanguageCodeis equivalent toDeviceDefinition.languageCodeDeviceDefinition.languageCodeElement `DeviceDefinition.languageCode` is mapped to FHIR R4 element `DeviceDefinition.languageCode` as `Equivalent`.
DeviceDefinition.propertypropertymaps to wider conceptDeviceDefinition.propertyDeviceDefinition.propertyElement `DeviceDefinition.property` is mapped to FHIR R4 element `DeviceDefinition.property` as `Equivalent`. 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 an individual device could also be documented in a [Device] instance. The Device instance's properties, and their values, could be, but need not be, the same as in the associated DeviceDefinition.
DeviceDefinition.property.typetypeis equivalent toDeviceDefinition.property.typeDeviceDefinition.property.typeElement `DeviceDefinition.property.type` is mapped to FHIR R4 element `DeviceDefinition.property.type` as `Equivalent`.
DeviceDefinition.property.value[x]value[x]is related toDeviceDefinition.property.valueCodeDeviceDefinition.property.valueCodeElement `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueQuantity` as `RelatedTo`. Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueCode` as `RelatedTo`. The mappings for `DeviceDefinition.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string. This use of string or CodeableConcept is supported to address different purposes The text element of the valueCodeableConcept choice type 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 valueString choice type is used for textual descriptive device properties that cannot be expressed in other elements.
is related toDeviceDefinition.property.valueQuantityDeviceDefinition.property.valueQuantityElement `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueQuantity` as `RelatedTo`. Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueCode` as `RelatedTo`. The mappings for `DeviceDefinition.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string. This use of string or CodeableConcept is supported to address different purposes The text element of the valueCodeableConcept choice type 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 valueString choice type is used for textual descriptive device properties that cannot be expressed in other elements.
DeviceDefinition.ownerowneris equivalent toDeviceDefinition.ownerDeviceDefinition.ownerElement `DeviceDefinition.owner` is mapped to FHIR R4 element `DeviceDefinition.owner` as `Equivalent`.
DeviceDefinition.contactcontactis equivalent toDeviceDefinition.contactDeviceDefinition.contactElement `DeviceDefinition.contact` is mapped to FHIR R4 element `DeviceDefinition.contact` as `Equivalent`. An externally-defined extension that has been mapped as the representation of FHIR R5 element `DeviceDefinition.contact`: `http://hl7.org/fhir/StructureDefinition/artifact-contact`. used for troubleshooting etc.
DeviceDefinition.notenoteis equivalent toDeviceDefinition.noteDeviceDefinition.noteElement `DeviceDefinition.note` is mapped to FHIR R4 element `DeviceDefinition.note` as `Equivalent`.
DeviceDefinition.materialmaterialmaps to wider conceptDeviceDefinition.materialDeviceDefinition.materialElement `DeviceDefinition.material` is mapped to FHIR R4 element `DeviceDefinition.material` as `Equivalent`.
DeviceDefinition.material.substancesubstanceis equivalent toDeviceDefinition.material.substanceDeviceDefinition.material.substanceElement `DeviceDefinition.material.substance` is mapped to FHIR R4 element `DeviceDefinition.material.substance` as `Equivalent`.
DeviceDefinition.material.alternatealternateis equivalent toDeviceDefinition.material.alternateDeviceDefinition.material.alternateElement `DeviceDefinition.material.alternate` is mapped to FHIR R4 element `DeviceDefinition.material.alternate` as `Equivalent`.
DeviceDefinition.material.allergenicIndicatorallergenicIndicatoris equivalent toDeviceDefinition.material.allergenicIndicatorDeviceDefinition.material.allergenicIndicatorElement `DeviceDefinition.material.allergenicIndicator` is mapped to FHIR R4 element `DeviceDefinition.material.allergenicIndicator` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: udiDeviceIdentifierversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceDefinition.udiDeviceIdentifier (udiDeviceIdentifier)is equivalent toExtension (R5: udiDeviceIdentifier)Element `DeviceDefinition.udiDeviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier` as `Equivalent`.
DeviceDefinition.udiDeviceIdentifier.deviceIdentifier (deviceIdentifier)is equivalent toExtension.extension:deviceIdentifier (R5: The identifier that is to be associated with every Device that references this DeviceDefintiion for the issuer and jurisdiction provided in the DeviceDefinition.udiDeviceIdentifier)Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` as `Equivalent`.
DeviceDefinition.udiDeviceIdentifier.issuer (issuer)is equivalent toExtension.extension:issuer (R5: issuer)Element `DeviceDefinition.udiDeviceIdentifier.issuer` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.issuer` as `Equivalent`.
DeviceDefinition.udiDeviceIdentifier.jurisdiction (jurisdiction)is equivalent toExtension.extension:jurisdiction (R5: jurisdiction)Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` as `Equivalent`.
DeviceDefinition.udiDeviceIdentifier.marketDistribution (marketDistribution)maps to wider conceptExtension.extension:marketDistribution (R5: Indicates whether and when the device is available on the market (new))Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod (marketPeriod)maps to wider conceptExtension.extension:marketDistribution.extension:marketPeriod (R5: Begin and end dates for the commercial distribution of the device (new))Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction (subJurisdiction)maps to wider conceptExtension.extension:marketDistribution.extension:subJurisdiction (R5: National state or territory where the device is commercialized (new))Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.udiDeviceIdentifier (udiDeviceIdentifier)maps to wider conceptExtension.extension:udiDeviceIdentifierElement `DeviceDefinition.packaging.udiDeviceIdentifier` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.udiDeviceIdentifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.udiDeviceIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: Indicates whether and when the device is available on the market (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceDefinition.udiDeviceIdentifier.marketDistribution (marketDistribution)maps to wider conceptExtension (R5: Indicates whether and when the device is available on the market (new))Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod (marketPeriod)maps to wider conceptExtension.extension:marketPeriod (R5: Begin and end dates for the commercial distribution of the device (new))Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction (subJurisdiction)maps to wider conceptExtension.extension:subJurisdiction (R5: National state or territory where the device is commercialized (new))Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: Regulatory identifier(s) associated with this device (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceDefinition.regulatoryIdentifier (regulatoryIdentifier)maps to wider conceptExtension (R5: Regulatory identifier(s) associated with this device (new))Element `DeviceDefinition.regulatoryIdentifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.regulatoryIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This should not be used for regulatory authorization numbers which are to be captured elsewhere.
DeviceDefinition.regulatoryIdentifier.type (type)maps to wider conceptExtension.extension:type (R5: basic | master | license (new))Element `DeviceDefinition.regulatoryIdentifier.type` is part of an existing definition because parent element `DeviceDefinition.regulatoryIdentifier` requires a cross-version extension. Element `DeviceDefinition.regulatoryIdentifier.type` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.regulatoryIdentifier.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.regulatoryIdentifier.deviceIdentifier (deviceIdentifier)maps to wider conceptExtension.extension:deviceIdentifier (R5: The identifier itself (new))Element `DeviceDefinition.regulatoryIdentifier.deviceIdentifier` is part of an existing definition because parent element `DeviceDefinition.regulatoryIdentifier` requires a cross-version extension. Element `DeviceDefinition.regulatoryIdentifier.deviceIdentifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.regulatoryIdentifier.deviceIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.regulatoryIdentifier.issuer (issuer)maps to wider conceptExtension.extension:issuer (R5: The organization that issued this identifier (new))Element `DeviceDefinition.regulatoryIdentifier.issuer` is part of an existing definition because parent element `DeviceDefinition.regulatoryIdentifier` requires a cross-version extension. Element `DeviceDefinition.regulatoryIdentifier.issuer` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.regulatoryIdentifier.issuer` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.regulatoryIdentifier.jurisdiction (jurisdiction)maps to wider conceptExtension.extension:jurisdiction (R5: The jurisdiction to which the deviceIdentifier applies (new))Element `DeviceDefinition.regulatoryIdentifier.jurisdiction` is part of an existing definition because parent element `DeviceDefinition.regulatoryIdentifier` requires a cross-version extension. Element `DeviceDefinition.regulatoryIdentifier.jurisdiction` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.regulatoryIdentifier.jurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

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

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

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: What kind of device or device system this is (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceDefinition.classification (classification)maps to wider conceptExtension (R5: What kind of device or device system this is (new))Element `DeviceDefinition.classification` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.classification` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). In this element various classifications can be used, such as GMDN, EMDN, SNOMED CT, risk classes, national product codes.
DeviceDefinition.classification.type (type)maps to wider conceptExtension.extension:type (R5: A classification or risk class of the device model (new))Element `DeviceDefinition.classification.type` is part of an existing definition because parent element `DeviceDefinition.classification` requires a cross-version extension. Element `DeviceDefinition.classification.type` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.classification.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.classification.justification (justification)maps to wider conceptExtension.extension:justification (R5: Further information qualifying this classification of the device model (new))Element `DeviceDefinition.classification.justification` is part of an existing definition because parent element `DeviceDefinition.classification` requires a cross-version extension. Element `DeviceDefinition.classification.justification` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.classification.justification` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: A device, part of the current one (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceDefinition.hasPart (hasPart)maps to wider conceptExtension (R5: A device, part of the current one (new))Element `DeviceDefinition.hasPart` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.hasPart` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.hasPart.reference (reference)maps to wider conceptExtension.extension:reference (R5: Reference to the part (new))Element `DeviceDefinition.hasPart.reference` is part of an existing definition because parent element `DeviceDefinition.hasPart` requires a cross-version extension. Element `DeviceDefinition.hasPart.reference` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.hasPart.reference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.hasPart.count (count)maps to wider conceptExtension.extension:count (R5: Number of occurrences of the part (new))Element `DeviceDefinition.hasPart.count` is part of an existing definition because parent element `DeviceDefinition.hasPart` requires a cross-version extension. Element `DeviceDefinition.hasPart.count` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.hasPart.count` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: Information about the packaging of the device, i.e. how the device is packaged (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceDefinition.packaging (packaging)maps to wider conceptExtension (R5: Information about the packaging of the device, i.e. how the device is packaged (new))Element `DeviceDefinition.packaging` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.identifier (identifier)maps to wider conceptExtension.extension:identifier (R5: Business identifier of the packaged medication (new))Element `DeviceDefinition.packaging.identifier` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.identifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.type (type)maps to wider conceptExtension.extension:type (R5: A code that defines the specific type of packaging (new))Element `DeviceDefinition.packaging.type` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.type` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.count (count)maps to wider conceptExtension.extension:count (R5: The number of items contained in the package (devices or sub-packages) (new))Element `DeviceDefinition.packaging.count` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.count` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.count` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.distributor (distributor)maps to wider conceptExtension.extension:distributor (R5: An organization that distributes the packaged device (new))Element `DeviceDefinition.packaging.distributor` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.distributor` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.distributor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.distributor.name (name)maps to wider conceptExtension.extension:distributor.extension:name (R5: Distributor's human-readable name (new))Element `DeviceDefinition.packaging.distributor.name` is part of an existing definition because parent element `DeviceDefinition.packaging.distributor` requires a cross-version extension. Element `DeviceDefinition.packaging.distributor.name` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.distributor.name` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.distributor.organizationReference (organizationReference)maps to wider conceptExtension.extension:distributor.extension:organizationReference (R5: Distributor as an Organization resource (new))Element `DeviceDefinition.packaging.distributor.organizationReference` is part of an existing definition because parent element `DeviceDefinition.packaging.distributor` requires a cross-version extension. Element `DeviceDefinition.packaging.distributor.organizationReference` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.distributor.organizationReference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.udiDeviceIdentifier (udiDeviceIdentifier)maps to wider conceptExtension.extension:udiDeviceIdentifier (R5: Unique Device Identifier (UDI) Barcode string on the packaging (new))Element `DeviceDefinition.packaging.udiDeviceIdentifier` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.udiDeviceIdentifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.udiDeviceIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.packaging (packaging)maps to wider conceptExtension.extension:packaging (R5: Allows packages within packages (new))Element `DeviceDefinition.packaging.packaging` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension. Element `DeviceDefinition.packaging.packaging` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.packaging.packaging` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

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

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

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|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
DeviceDefinition.version.component (component)maps to wider conceptExtension (R5: The hardware or software module of the device to which the version applies (new))Element `DeviceDefinition.version.component` has a context of DeviceDefinition.version based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.version.component` has no mapping targets in FHIR R4. 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 11 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: The version text (new)version: 0.1.0)

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

Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: Value of the property additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceDefinition.property.value[x] (value[x])maps to wider conceptExtension (R5: Value of the property additional types)Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueQuantity` as `RelatedTo`. Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueCode` as `RelatedTo`. The mappings for `DeviceDefinition.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string. This use of string or CodeableConcept is supported to address different purposes The text element of the valueCodeableConcept choice type 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 valueString choice type is used for textual descriptive device properties that cannot be expressed in other elements.

Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: An associated device, attached to, used with, communicating with or linking a previous or new device model to the focal device (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceDefinition.link (link)maps to wider conceptExtension (R5: An associated device, attached to, used with, communicating with or linking a previous or new device model to the focal device (new))Element `DeviceDefinition.link` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.link` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.link.relation (relation)maps to wider conceptExtension.extension:relation (R5: The type indicates the relationship of the related device to the device instance (new))Element `DeviceDefinition.link.relation` is part of an existing definition because parent element `DeviceDefinition.link` requires a cross-version extension. Element `DeviceDefinition.link.relation` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.link.relation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.link.relatedDevice (relatedDevice)maps to wider conceptExtension.extension:relatedDevice (R5: A reference to the linked device (new))Element `DeviceDefinition.link.relatedDevice` is part of an existing definition because parent element `DeviceDefinition.link` requires a cross-version extension. Element `DeviceDefinition.link.relatedDevice` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.link.relatedDevice` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: lot-number | manufactured-date | serial-number | expiration-date | biological-source | software-version (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceDefinition.productionIdentifierInUDI (productionIdentifierInUDI)maps to wider conceptExtension (R5: lot-number | manufactured-date | serial-number | expiration-date | biological-source | software-version (new))Element `DeviceDefinition.productionIdentifierInUDI` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.productionIdentifierInUDI` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: Information aimed at providing directions for the usage of this model of device (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceDefinition.guideline (guideline)maps to wider conceptExtension (R5: Information aimed at providing directions for the usage of this model of device (new))Element `DeviceDefinition.guideline` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). For more structured data, a ClinicalUseDefinition that points to the DeviceDefinition can be used.
DeviceDefinition.guideline.useContext (useContext)maps to wider conceptExtension.extension:useContext (R5: The circumstances that form the setting for using the device (new))Element `DeviceDefinition.guideline.useContext` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.useContext` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.useContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.guideline.usageInstruction (usageInstruction)maps to wider conceptExtension.extension:usageInstruction (R5: Detailed written and visual directions for the user on how to use the device (new))Element `DeviceDefinition.guideline.usageInstruction` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.usageInstruction` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.usageInstruction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.guideline.relatedArtifact (relatedArtifact)is equivalent toExtension.extension:relatedArtifact (R5: A source of information or reference for this guideline (new))Element `DeviceDefinition.guideline.relatedArtifact` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.relatedArtifact` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.relatedArtifact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.guideline.indication (indication)maps to wider conceptExtension.extension:indication (R5: A clinical condition for which the device was designed to be used (new))Element `DeviceDefinition.guideline.indication` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.indication` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.indication` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). A ClinicalUseDefinition that points to the DeviceDefinition can be used if more structured data is needed.
DeviceDefinition.guideline.contraindication (contraindication)maps to wider conceptExtension.extension:contraindication (R5: A specific situation when a device should not be used because it may cause harm (new))Element `DeviceDefinition.guideline.contraindication` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.contraindication` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.contraindication` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). A ClinicalUseDefinition that points to the DeviceDefinition can be used if more structured data is needed.
DeviceDefinition.guideline.warning (warning)maps to wider conceptExtension.extension:warning (R5: Specific hazard alert information that a user needs to know before using the device (new))Element `DeviceDefinition.guideline.warning` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.warning` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.warning` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). A ClinicalUseDefinition that points to the DeviceDefinition can be used if more structured data is needed.
DeviceDefinition.guideline.intendedUse (intendedUse)maps to wider conceptExtension.extension:intendedUse (R5: A description of the general purpose or medical use of the device or its function (new))Element `DeviceDefinition.guideline.intendedUse` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension. Element `DeviceDefinition.guideline.intendedUse` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.guideline.intendedUse` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: Tracking of latest field safety corrective action (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceDefinition.correctiveAction (correctiveAction)maps to wider conceptExtension (R5: Tracking of latest field safety corrective action (new))Element `DeviceDefinition.correctiveAction` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.correctiveAction.recall (recall)maps to wider conceptExtension.extension:recall (R5: Whether the corrective action was a recall (new))Element `DeviceDefinition.correctiveAction.recall` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension. Element `DeviceDefinition.correctiveAction.recall` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction.recall` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When a field safety action has been initiated but not yet resulted in a recall, this element will be set to 'false'.
DeviceDefinition.correctiveAction.scope (scope)maps to wider conceptExtension.extension:scope (R5: model | lot-numbers | serial-numbers (new))Element `DeviceDefinition.correctiveAction.scope` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension. Element `DeviceDefinition.correctiveAction.scope` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction.scope` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.correctiveAction.period (period)maps to wider conceptExtension.extension:period (R5: Start and end dates of the corrective action (new))Element `DeviceDefinition.correctiveAction.period` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension. Element `DeviceDefinition.correctiveAction.period` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.correctiveAction.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 to R5: Billing code or reference associated with the device (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DeviceDefinition.chargeItem (chargeItem)maps to wider conceptExtension (R5: Billing code or reference associated with the device (new))Element `DeviceDefinition.chargeItem` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.chargeItem` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.chargeItem.chargeItemCode (chargeItemCode)maps to wider conceptExtension.extension:chargeItemCode (R5: The code or reference for the charge item (new))Element `DeviceDefinition.chargeItem.chargeItemCode` is part of an existing definition because parent element `DeviceDefinition.chargeItem` requires a cross-version extension. Element `DeviceDefinition.chargeItem.chargeItemCode` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.chargeItem.chargeItemCode` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.chargeItem.count (count)maps to wider conceptExtension.extension:count (R5: Coefficient applicable to the billing code (new))Element `DeviceDefinition.chargeItem.count` is part of an existing definition because parent element `DeviceDefinition.chargeItem` requires a cross-version extension. Element `DeviceDefinition.chargeItem.count` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.chargeItem.count` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.chargeItem.effectivePeriod (effectivePeriod)maps to wider conceptExtension.extension:effectivePeriod (R5: A specific time period in which this charge item applies (new))Element `DeviceDefinition.chargeItem.effectivePeriod` is part of an existing definition because parent element `DeviceDefinition.chargeItem` requires a cross-version extension. Element `DeviceDefinition.chargeItem.effectivePeriod` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.chargeItem.effectivePeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
DeviceDefinition.chargeItem.useContext (useContext)maps to wider conceptExtension.extension:useContext (R5: The context to which this charge item applies (new))Element `DeviceDefinition.chargeItem.useContext` is part of an existing definition because parent element `DeviceDefinition.chargeItem` requires a cross-version extension. Element `DeviceDefinition.chargeItem.useContext` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`. Element `DeviceDefinition.chargeItem.useContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Source1

{
  "resourceType": "ConceptMap",
  "id": "R5-DeviceDefinition-element-map-to-R4",
  "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",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-DeviceDefinition-element-map-to-R4",
  "version": "0.1.0",
  "name": "R5DeviceDefinitionElementMapToR4",
  "title": "Cross-version mapping for FHIR R5 DeviceDefinition to FHIR R4 DeviceDefinition",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:04:44.9668049-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 DeviceDefinition to FHIR R4.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceCanonical": "http://hl7.org/fhir/5.0",
  "targetUri": "http://hl7.org/fhir/4.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "targetVersion": "4.0.1",
      "element": [
        {
          "code": "DeviceDefinition.meta",
          "display": "meta",
          "target": [
            {
              "code": "DeviceDefinition.meta",
              "display": "DeviceDefinition.meta",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.meta` is mapped to FHIR R4 element `DeviceDefinition.meta` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "DeviceDefinition.implicitRules",
              "display": "DeviceDefinition.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.implicitRules` is mapped to FHIR R4 element `DeviceDefinition.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": "DeviceDefinition.language",
          "display": "language",
          "target": [
            {
              "code": "DeviceDefinition.language",
              "display": "DeviceDefinition.language",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.language` is mapped to FHIR R4 element `DeviceDefinition.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": "DeviceDefinition.text",
          "display": "text",
          "target": [
            {
              "code": "DeviceDefinition.text",
              "display": "DeviceDefinition.text",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.text` is mapped to FHIR R4 element `DeviceDefinition.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": "DeviceDefinition.contained",
          "display": "contained",
          "target": [
            {
              "code": "DeviceDefinition.contained",
              "display": "DeviceDefinition.contained",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.contained` is mapped to FHIR R4 element `DeviceDefinition.contained` as `Equivalent`.\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": "DeviceDefinition.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "DeviceDefinition.identifier",
              "display": "DeviceDefinition.identifier",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.identifier` is mapped to FHIR R4 element `DeviceDefinition.identifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.udiDeviceIdentifier",
          "display": "udiDeviceIdentifier",
          "target": [
            {
              "code": "DeviceDefinition.udiDeviceIdentifier",
              "display": "DeviceDefinition.udiDeviceIdentifier",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.udiDeviceIdentifier.deviceIdentifier",
          "display": "deviceIdentifier",
          "target": [
            {
              "code": "DeviceDefinition.udiDeviceIdentifier.deviceIdentifier",
              "display": "DeviceDefinition.udiDeviceIdentifier.deviceIdentifier",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.udiDeviceIdentifier.issuer",
          "display": "issuer",
          "target": [
            {
              "code": "DeviceDefinition.udiDeviceIdentifier.issuer",
              "display": "DeviceDefinition.udiDeviceIdentifier.issuer",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier.issuer` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.issuer` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.udiDeviceIdentifier.jurisdiction",
          "display": "jurisdiction",
          "target": [
            {
              "code": "DeviceDefinition.udiDeviceIdentifier.jurisdiction",
              "display": "DeviceDefinition.udiDeviceIdentifier.jurisdiction",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.manufacturer",
          "display": "manufacturer",
          "target": [
            {
              "code": "DeviceDefinition.manufacturer[x]",
              "display": "DeviceDefinition.manufacturer[x]",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.manufacturer` is mapped to FHIR R4 element `DeviceDefinition.manufacturer[x]` as `Equivalent`.\nThe target context `DeviceDefinition.manufacturer[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceDefinition`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.deviceName",
          "display": "deviceName",
          "target": [
            {
              "code": "DeviceDefinition.deviceName",
              "display": "DeviceDefinition.deviceName",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.deviceName` is mapped to FHIR R4 element `DeviceDefinition.deviceName` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.deviceName.name",
          "display": "name",
          "target": [
            {
              "code": "DeviceDefinition.deviceName.name",
              "display": "DeviceDefinition.deviceName.name",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.deviceName.name` is mapped to FHIR R4 element `DeviceDefinition.deviceName.name` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.deviceName.type",
          "display": "type",
          "target": [
            {
              "code": "DeviceDefinition.deviceName.type",
              "display": "DeviceDefinition.deviceName.type",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.deviceName.type` is mapped to FHIR R4 element `DeviceDefinition.deviceName.type` as `SourceIsNarrowerThanTarget`.\nThe mappings for `DeviceDefinition.deviceName.type` do not allow expression of the necessary codes, per the bindings on the source and target."
            }
          ]
        },
        {
          "code": "DeviceDefinition.modelNumber",
          "display": "modelNumber",
          "target": [
            {
              "code": "DeviceDefinition.modelNumber",
              "display": "DeviceDefinition.modelNumber",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.modelNumber` is mapped to FHIR R4 element `DeviceDefinition.modelNumber` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.conformsTo",
          "display": "conformsTo",
          "target": [
            {
              "code": "DeviceDefinition.specialization",
              "display": "DeviceDefinition.specialization",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.conformsTo` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `Equivalent`.\nAn externally-defined extension that has been mapped as the representation of FHIR R5 element `DeviceDefinition.conformsTo`: `http://hl7.org/fhir/StructureDefinition/device-conformsTo`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.conformsTo.category",
          "display": "category",
          "target": [
            {
              "code": "DeviceDefinition.specialization",
              "display": "DeviceDefinition.specialization",
              "equivalence": "narrower",
              "comment": "Element `DeviceDefinition.conformsTo.category` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.conformsTo.specification",
          "display": "specification",
          "target": [
            {
              "code": "DeviceDefinition.specialization",
              "display": "DeviceDefinition.specialization",
              "equivalence": "narrower",
              "comment": "Element `DeviceDefinition.conformsTo.specification` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `SourceIsNarrowerThanTarget`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.conformsTo.version",
          "display": "version",
          "target": [
            {
              "code": "DeviceDefinition.specialization.version",
              "display": "DeviceDefinition.specialization.version",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.conformsTo.version` is mapped to FHIR R4 element `DeviceDefinition.specialization.version` as `SourceIsBroaderThanTarget`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.conformsTo.source",
          "display": "source",
          "target": [
            {
              "code": "DeviceDefinition.specialization",
              "display": "DeviceDefinition.specialization",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.conformsTo.source` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.version",
          "display": "version",
          "target": [
            {
              "code": "DeviceDefinition.version",
              "display": "DeviceDefinition.version",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.version` is mapped to FHIR R4 element `DeviceDefinition.version` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.safety",
          "display": "safety",
          "target": [
            {
              "code": "DeviceDefinition.safety",
              "display": "DeviceDefinition.safety",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.safety` is mapped to FHIR R4 element `DeviceDefinition.safety` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.shelfLifeStorage",
          "display": "shelfLifeStorage",
          "target": [
            {
              "code": "DeviceDefinition.shelfLifeStorage",
              "display": "DeviceDefinition.shelfLifeStorage",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.shelfLifeStorage` is mapped to FHIR R4 element `DeviceDefinition.shelfLifeStorage` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.languageCode",
          "display": "languageCode",
          "target": [
            {
              "code": "DeviceDefinition.languageCode",
              "display": "DeviceDefinition.languageCode",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.languageCode` is mapped to FHIR R4 element `DeviceDefinition.languageCode` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.property",
          "display": "property",
          "target": [
            {
              "code": "DeviceDefinition.property",
              "display": "DeviceDefinition.property",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.property` is mapped to FHIR R4 element `DeviceDefinition.property` as `Equivalent`.\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 an individual device could also be documented in a [Device] instance. The Device instance's properties, and their values, could be, but need not be, the same as in the associated DeviceDefinition."
            }
          ]
        },
        {
          "code": "DeviceDefinition.property.type",
          "display": "type",
          "target": [
            {
              "code": "DeviceDefinition.property.type",
              "display": "DeviceDefinition.property.type",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.property.type` is mapped to FHIR R4 element `DeviceDefinition.property.type` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.property.value[x]",
          "display": "value[x]",
          "target": [
            {
              "code": "DeviceDefinition.property.valueCode",
              "display": "DeviceDefinition.property.valueCode",
              "equivalence": "relatedto",
              "comment": "Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueQuantity` as `RelatedTo`.\nElement `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueCode` as `RelatedTo`.\nThe mappings for `DeviceDefinition.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string.\nThis use of string or CodeableConcept is supported to address different purposes The text element of the valueCodeableConcept choice type 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 valueString choice type is used for textual descriptive device properties that cannot be expressed in other elements."
            },
            {
              "code": "DeviceDefinition.property.valueQuantity",
              "display": "DeviceDefinition.property.valueQuantity",
              "equivalence": "relatedto",
              "comment": "Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueQuantity` as `RelatedTo`.\nElement `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueCode` as `RelatedTo`.\nThe mappings for `DeviceDefinition.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string.\nThis use of string or CodeableConcept is supported to address different purposes The text element of the valueCodeableConcept choice type 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 valueString choice type is used for textual descriptive device properties that cannot be expressed in other elements."
            }
          ]
        },
        {
          "code": "DeviceDefinition.owner",
          "display": "owner",
          "target": [
            {
              "code": "DeviceDefinition.owner",
              "display": "DeviceDefinition.owner",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.owner` is mapped to FHIR R4 element `DeviceDefinition.owner` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.contact",
          "display": "contact",
          "target": [
            {
              "code": "DeviceDefinition.contact",
              "display": "DeviceDefinition.contact",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.contact` is mapped to FHIR R4 element `DeviceDefinition.contact` as `Equivalent`.\nAn externally-defined extension that has been mapped as the representation of FHIR R5 element `DeviceDefinition.contact`: `http://hl7.org/fhir/StructureDefinition/artifact-contact`.\nused for troubleshooting etc."
            }
          ]
        },
        {
          "code": "DeviceDefinition.note",
          "display": "note",
          "target": [
            {
              "code": "DeviceDefinition.note",
              "display": "DeviceDefinition.note",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.note` is mapped to FHIR R4 element `DeviceDefinition.note` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.material",
          "display": "material",
          "target": [
            {
              "code": "DeviceDefinition.material",
              "display": "DeviceDefinition.material",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.material` is mapped to FHIR R4 element `DeviceDefinition.material` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.material.substance",
          "display": "substance",
          "target": [
            {
              "code": "DeviceDefinition.material.substance",
              "display": "DeviceDefinition.material.substance",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.material.substance` is mapped to FHIR R4 element `DeviceDefinition.material.substance` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.material.alternate",
          "display": "alternate",
          "target": [
            {
              "code": "DeviceDefinition.material.alternate",
              "display": "DeviceDefinition.material.alternate",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.material.alternate` is mapped to FHIR R4 element `DeviceDefinition.material.alternate` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.material.allergenicIndicator",
          "display": "allergenicIndicator",
          "target": [
            {
              "code": "DeviceDefinition.material.allergenicIndicator",
              "display": "DeviceDefinition.material.allergenicIndicator",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.material.allergenicIndicator` is mapped to FHIR R4 element `DeviceDefinition.material.allergenicIndicator` as `Equivalent`."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.udiDeviceIdentifier",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.udiDeviceIdentifier",
          "display": "udiDeviceIdentifier",
          "target": [
            {
              "code": "Extension",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.udiDeviceIdentifier.deviceIdentifier",
          "display": "deviceIdentifier",
          "target": [
            {
              "code": "Extension.extension:deviceIdentifier",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.udiDeviceIdentifier.issuer",
          "display": "issuer",
          "target": [
            {
              "code": "Extension.extension:issuer",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier.issuer` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.issuer` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.udiDeviceIdentifier.jurisdiction",
          "display": "jurisdiction",
          "target": [
            {
              "code": "Extension.extension:jurisdiction",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` as `Equivalent`."
            }
          ]
        },
        {
          "code": "DeviceDefinition.udiDeviceIdentifier.marketDistribution",
          "display": "marketDistribution",
          "target": [
            {
              "code": "Extension.extension:marketDistribution",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.udiDeviceIdentifier.marketDistribution` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod",
          "display": "marketPeriod",
          "target": [
            {
              "code": "Extension.extension:marketDistribution.extension:marketPeriod",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` requires a cross-version extension.\nElement `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction",
          "display": "subJurisdiction",
          "target": [
            {
              "code": "Extension.extension:marketDistribution.extension:subJurisdiction",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` requires a cross-version extension.\nElement `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.packaging.udiDeviceIdentifier",
          "display": "udiDeviceIdentifier",
          "target": [
            {
              "code": "Extension.extension:udiDeviceIdentifier",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.packaging.udiDeviceIdentifier` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension.\nElement `DeviceDefinition.packaging.udiDeviceIdentifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.packaging.udiDeviceIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.udiDeviceIdentifier.marketDistribution",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.udiDeviceIdentifier.marketDistribution",
          "display": "marketDistribution",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.udiDeviceIdentifier.marketDistribution` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod",
          "display": "marketPeriod",
          "target": [
            {
              "code": "Extension.extension:marketPeriod",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` requires a cross-version extension.\nElement `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction",
          "display": "subJurisdiction",
          "target": [
            {
              "code": "Extension.extension:subJurisdiction",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier.marketDistribution` requires a cross-version extension.\nElement `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` has a context of DeviceDefinition.udiDeviceIdentifier based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.regulatoryIdentifier",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.regulatoryIdentifier",
          "display": "regulatoryIdentifier",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.regulatoryIdentifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.regulatoryIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThis should not be used for regulatory authorization numbers which are to be captured elsewhere."
            }
          ]
        },
        {
          "code": "DeviceDefinition.regulatoryIdentifier.type",
          "display": "type",
          "target": [
            {
              "code": "Extension.extension:type",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.regulatoryIdentifier.type` is part of an existing definition because parent element `DeviceDefinition.regulatoryIdentifier` requires a cross-version extension.\nElement `DeviceDefinition.regulatoryIdentifier.type` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.regulatoryIdentifier.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.regulatoryIdentifier.deviceIdentifier",
          "display": "deviceIdentifier",
          "target": [
            {
              "code": "Extension.extension:deviceIdentifier",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.regulatoryIdentifier.deviceIdentifier` is part of an existing definition because parent element `DeviceDefinition.regulatoryIdentifier` requires a cross-version extension.\nElement `DeviceDefinition.regulatoryIdentifier.deviceIdentifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.regulatoryIdentifier.deviceIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.regulatoryIdentifier.issuer",
          "display": "issuer",
          "target": [
            {
              "code": "Extension.extension:issuer",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.regulatoryIdentifier.issuer` is part of an existing definition because parent element `DeviceDefinition.regulatoryIdentifier` requires a cross-version extension.\nElement `DeviceDefinition.regulatoryIdentifier.issuer` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.regulatoryIdentifier.issuer` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.regulatoryIdentifier.jurisdiction",
          "display": "jurisdiction",
          "target": [
            {
              "code": "Extension.extension:jurisdiction",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.regulatoryIdentifier.jurisdiction` is part of an existing definition because parent element `DeviceDefinition.regulatoryIdentifier` requires a cross-version extension.\nElement `DeviceDefinition.regulatoryIdentifier.jurisdiction` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.regulatoryIdentifier.jurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.partNumber",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.partNumber",
          "display": "partNumber",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.partNumber` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.partNumber` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nAlphanumeric Maximum 20."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.classification",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.classification",
          "display": "classification",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.classification` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.classification` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nIn this element various classifications can be used, such as GMDN, EMDN, SNOMED CT, risk classes, national product codes."
            }
          ]
        },
        {
          "code": "DeviceDefinition.classification.type",
          "display": "type",
          "target": [
            {
              "code": "Extension.extension:type",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.classification.type` is part of an existing definition because parent element `DeviceDefinition.classification` requires a cross-version extension.\nElement `DeviceDefinition.classification.type` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.classification.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.classification.justification",
          "display": "justification",
          "target": [
            {
              "code": "Extension.extension:justification",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.classification.justification` is part of an existing definition because parent element `DeviceDefinition.classification` requires a cross-version extension.\nElement `DeviceDefinition.classification.justification` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.classification.justification` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.hasPart",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.hasPart",
          "display": "hasPart",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.hasPart` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.hasPart` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.hasPart.reference",
          "display": "reference",
          "target": [
            {
              "code": "Extension.extension:reference",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.hasPart.reference` is part of an existing definition because parent element `DeviceDefinition.hasPart` requires a cross-version extension.\nElement `DeviceDefinition.hasPart.reference` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.hasPart.reference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.hasPart.count",
          "display": "count",
          "target": [
            {
              "code": "Extension.extension:count",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.hasPart.count` is part of an existing definition because parent element `DeviceDefinition.hasPart` requires a cross-version extension.\nElement `DeviceDefinition.hasPart.count` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.hasPart.count` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.packaging",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.packaging",
          "display": "packaging",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.packaging` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.packaging` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.packaging.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Extension.extension:identifier",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.packaging.identifier` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension.\nElement `DeviceDefinition.packaging.identifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.packaging.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.packaging.type",
          "display": "type",
          "target": [
            {
              "code": "Extension.extension:type",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.packaging.type` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension.\nElement `DeviceDefinition.packaging.type` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.packaging.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.packaging.count",
          "display": "count",
          "target": [
            {
              "code": "Extension.extension:count",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.packaging.count` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension.\nElement `DeviceDefinition.packaging.count` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.packaging.count` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.packaging.distributor",
          "display": "distributor",
          "target": [
            {
              "code": "Extension.extension:distributor",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.packaging.distributor` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension.\nElement `DeviceDefinition.packaging.distributor` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.packaging.distributor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.packaging.distributor.name",
          "display": "name",
          "target": [
            {
              "code": "Extension.extension:distributor.extension:name",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.packaging.distributor.name` is part of an existing definition because parent element `DeviceDefinition.packaging.distributor` requires a cross-version extension.\nElement `DeviceDefinition.packaging.distributor.name` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.packaging.distributor.name` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.packaging.distributor.organizationReference",
          "display": "organizationReference",
          "target": [
            {
              "code": "Extension.extension:distributor.extension:organizationReference",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.packaging.distributor.organizationReference` is part of an existing definition because parent element `DeviceDefinition.packaging.distributor` requires a cross-version extension.\nElement `DeviceDefinition.packaging.distributor.organizationReference` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.packaging.distributor.organizationReference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.packaging.udiDeviceIdentifier",
          "display": "udiDeviceIdentifier",
          "target": [
            {
              "code": "Extension.extension:udiDeviceIdentifier",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.packaging.udiDeviceIdentifier` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension.\nElement `DeviceDefinition.packaging.udiDeviceIdentifier` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.packaging.udiDeviceIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.packaging.packaging",
          "display": "packaging",
          "target": [
            {
              "code": "Extension.extension:packaging",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.packaging.packaging` is part of an existing definition because parent element `DeviceDefinition.packaging` requires a cross-version extension.\nElement `DeviceDefinition.packaging.packaging` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.packaging.packaging` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.version.type",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.version.type",
          "display": "type",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.version.type` has a context of DeviceDefinition.version based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.version.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.version.component",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.version.component",
          "display": "component",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.version.component` has a context of DeviceDefinition.version based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.version.component` has no mapping targets in FHIR R4. 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/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.version.value",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.version.value",
          "display": "value",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.version.value` has a context of DeviceDefinition.version based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.version.value` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.property.value",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.property.value[x]",
          "display": "value[x]",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueQuantity` as `RelatedTo`.\nElement `DeviceDefinition.property.value[x]` is mapped to FHIR R4 element `DeviceDefinition.property.valueCode` as `RelatedTo`.\nThe mappings for `DeviceDefinition.property.value[x]` do not cover the following types: Attachment, boolean, integer, Range, string.\nThis use of string or CodeableConcept is supported to address different purposes The text element of the valueCodeableConcept choice type 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 valueString choice type is used for textual descriptive device properties that cannot be expressed in other elements."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.link",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.link",
          "display": "link",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.link` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.link` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.link.relation",
          "display": "relation",
          "target": [
            {
              "code": "Extension.extension:relation",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.link.relation` is part of an existing definition because parent element `DeviceDefinition.link` requires a cross-version extension.\nElement `DeviceDefinition.link.relation` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.link.relation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.link.relatedDevice",
          "display": "relatedDevice",
          "target": [
            {
              "code": "Extension.extension:relatedDevice",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.link.relatedDevice` is part of an existing definition because parent element `DeviceDefinition.link` requires a cross-version extension.\nElement `DeviceDefinition.link.relatedDevice` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.link.relatedDevice` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.productionIdentifierInUDI",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.productionIdentifierInUDI",
          "display": "productionIdentifierInUDI",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.productionIdentifierInUDI` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.productionIdentifierInUDI` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.guideline",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.guideline",
          "display": "guideline",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.guideline` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.guideline` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nFor more structured data, a ClinicalUseDefinition that points to the DeviceDefinition can be used."
            }
          ]
        },
        {
          "code": "DeviceDefinition.guideline.useContext",
          "display": "useContext",
          "target": [
            {
              "code": "Extension.extension:useContext",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.guideline.useContext` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension.\nElement `DeviceDefinition.guideline.useContext` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.guideline.useContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.guideline.usageInstruction",
          "display": "usageInstruction",
          "target": [
            {
              "code": "Extension.extension:usageInstruction",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.guideline.usageInstruction` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension.\nElement `DeviceDefinition.guideline.usageInstruction` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.guideline.usageInstruction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.guideline.relatedArtifact",
          "display": "relatedArtifact",
          "target": [
            {
              "code": "Extension.extension:relatedArtifact",
              "equivalence": "equivalent",
              "comment": "Element `DeviceDefinition.guideline.relatedArtifact` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension.\nElement `DeviceDefinition.guideline.relatedArtifact` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.guideline.relatedArtifact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.guideline.indication",
          "display": "indication",
          "target": [
            {
              "code": "Extension.extension:indication",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.guideline.indication` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension.\nElement `DeviceDefinition.guideline.indication` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.guideline.indication` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nA ClinicalUseDefinition that points to the DeviceDefinition can be used if more structured data is needed."
            }
          ]
        },
        {
          "code": "DeviceDefinition.guideline.contraindication",
          "display": "contraindication",
          "target": [
            {
              "code": "Extension.extension:contraindication",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.guideline.contraindication` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension.\nElement `DeviceDefinition.guideline.contraindication` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.guideline.contraindication` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nA ClinicalUseDefinition that points to the DeviceDefinition can be used if more structured data is needed."
            }
          ]
        },
        {
          "code": "DeviceDefinition.guideline.warning",
          "display": "warning",
          "target": [
            {
              "code": "Extension.extension:warning",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.guideline.warning` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension.\nElement `DeviceDefinition.guideline.warning` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.guideline.warning` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nA ClinicalUseDefinition that points to the DeviceDefinition can be used if more structured data is needed."
            }
          ]
        },
        {
          "code": "DeviceDefinition.guideline.intendedUse",
          "display": "intendedUse",
          "target": [
            {
              "code": "Extension.extension:intendedUse",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.guideline.intendedUse` is part of an existing definition because parent element `DeviceDefinition.guideline` requires a cross-version extension.\nElement `DeviceDefinition.guideline.intendedUse` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.guideline.intendedUse` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.correctiveAction",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.correctiveAction",
          "display": "correctiveAction",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.correctiveAction` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.correctiveAction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.correctiveAction.recall",
          "display": "recall",
          "target": [
            {
              "code": "Extension.extension:recall",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.correctiveAction.recall` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension.\nElement `DeviceDefinition.correctiveAction.recall` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.correctiveAction.recall` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nWhen a field safety action has been initiated but not yet resulted in a recall, this element will be set to 'false'."
            }
          ]
        },
        {
          "code": "DeviceDefinition.correctiveAction.scope",
          "display": "scope",
          "target": [
            {
              "code": "Extension.extension:scope",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.correctiveAction.scope` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension.\nElement `DeviceDefinition.correctiveAction.scope` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.correctiveAction.scope` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.correctiveAction.period",
          "display": "period",
          "target": [
            {
              "code": "Extension.extension:period",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.correctiveAction.period` is part of an existing definition because parent element `DeviceDefinition.correctiveAction` requires a cross-version extension.\nElement `DeviceDefinition.correctiveAction.period` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.correctiveAction.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/DeviceDefinition",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DeviceDefinition.chargeItem",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "DeviceDefinition.chargeItem",
          "display": "chargeItem",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.chargeItem` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.chargeItem` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.chargeItem.chargeItemCode",
          "display": "chargeItemCode",
          "target": [
            {
              "code": "Extension.extension:chargeItemCode",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.chargeItem.chargeItemCode` is part of an existing definition because parent element `DeviceDefinition.chargeItem` requires a cross-version extension.\nElement `DeviceDefinition.chargeItem.chargeItemCode` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.chargeItem.chargeItemCode` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.chargeItem.count",
          "display": "count",
          "target": [
            {
              "code": "Extension.extension:count",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.chargeItem.count` is part of an existing definition because parent element `DeviceDefinition.chargeItem` requires a cross-version extension.\nElement `DeviceDefinition.chargeItem.count` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.chargeItem.count` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.chargeItem.effectivePeriod",
          "display": "effectivePeriod",
          "target": [
            {
              "code": "Extension.extension:effectivePeriod",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.chargeItem.effectivePeriod` is part of an existing definition because parent element `DeviceDefinition.chargeItem` requires a cross-version extension.\nElement `DeviceDefinition.chargeItem.effectivePeriod` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.chargeItem.effectivePeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "DeviceDefinition.chargeItem.useContext",
          "display": "useContext",
          "target": [
            {
              "code": "Extension.extension:useContext",
              "equivalence": "wider",
              "comment": "Element `DeviceDefinition.chargeItem.useContext` is part of an existing definition because parent element `DeviceDefinition.chargeItem` requires a cross-version extension.\nElement `DeviceDefinition.chargeItem.useContext` has a context of DeviceDefinition based on following the parent source element upwards and mapping to `DeviceDefinition`.\nElement `DeviceDefinition.chargeItem.useContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    }
  ]
}