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 Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|5.0.0 Codes from DeviceDefinition DeviceDefinition.meta meta is equivalent to DeviceDefinition.meta DeviceDefinition.meta Element `DeviceDefinition.meta` is mapped to FHIR R4 element `DeviceDefinition.meta` as `Equivalent`. DeviceDefinition.implicitRules implicitRules is equivalent to DeviceDefinition.implicitRules DeviceDefinition.implicitRules Element `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.language language is equivalent to DeviceDefinition.language DeviceDefinition.language Element `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.text text is equivalent to DeviceDefinition.text DeviceDefinition.text Element `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.contained contained is equivalent to DeviceDefinition.contained DeviceDefinition.contained Element `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.identifier identifier is equivalent to DeviceDefinition.identifier DeviceDefinition.identifier Element `DeviceDefinition.identifier` is mapped to FHIR R4 element `DeviceDefinition.identifier` as `Equivalent`. DeviceDefinition.udiDeviceIdentifier udiDeviceIdentifier maps to wider concept DeviceDefinition.udiDeviceIdentifier DeviceDefinition.udiDeviceIdentifier Element `DeviceDefinition.udiDeviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier` as `Equivalent`. DeviceDefinition.udiDeviceIdentifier.deviceIdentifier deviceIdentifier is equivalent to DeviceDefinition.udiDeviceIdentifier.deviceIdentifier DeviceDefinition.udiDeviceIdentifier.deviceIdentifier Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` as `Equivalent`. DeviceDefinition.udiDeviceIdentifier.issuer issuer is equivalent to DeviceDefinition.udiDeviceIdentifier.issuer DeviceDefinition.udiDeviceIdentifier.issuer Element `DeviceDefinition.udiDeviceIdentifier.issuer` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.issuer` as `Equivalent`. DeviceDefinition.udiDeviceIdentifier.jurisdiction jurisdiction is equivalent to DeviceDefinition.udiDeviceIdentifier.jurisdiction DeviceDefinition.udiDeviceIdentifier.jurisdiction Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` as `Equivalent`. DeviceDefinition.manufacturer manufacturer is equivalent to DeviceDefinition.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.deviceName deviceName maps to wider concept DeviceDefinition.deviceName DeviceDefinition.deviceName Element `DeviceDefinition.deviceName` is mapped to FHIR R4 element `DeviceDefinition.deviceName` as `Equivalent`. DeviceDefinition.deviceName.name name is equivalent to DeviceDefinition.deviceName.name DeviceDefinition.deviceName.name Element `DeviceDefinition.deviceName.name` is mapped to FHIR R4 element `DeviceDefinition.deviceName.name` as `Equivalent`. DeviceDefinition.deviceName.type type is equivalent to DeviceDefinition.deviceName.type DeviceDefinition.deviceName.type Element `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.modelNumber modelNumber is equivalent to DeviceDefinition.modelNumber DeviceDefinition.modelNumber Element `DeviceDefinition.modelNumber` is mapped to FHIR R4 element `DeviceDefinition.modelNumber` as `Equivalent`. DeviceDefinition.conformsTo conformsTo maps to wider concept DeviceDefinition.specialization DeviceDefinition.specialization Element `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.category category narrower DeviceDefinition.specialization DeviceDefinition.specialization Element `DeviceDefinition.conformsTo.category` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `SourceIsNarrowerThanTarget`. DeviceDefinition.conformsTo.specification specification narrower DeviceDefinition.specialization DeviceDefinition.specialization Element `DeviceDefinition.conformsTo.specification` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `SourceIsNarrowerThanTarget`. DeviceDefinition.conformsTo.version version is equivalent to DeviceDefinition.specialization.version DeviceDefinition.specialization.version Element `DeviceDefinition.conformsTo.version` is mapped to FHIR R4 element `DeviceDefinition.specialization.version` as `SourceIsBroaderThanTarget`. DeviceDefinition.conformsTo.source source is equivalent to DeviceDefinition.specialization DeviceDefinition.specialization Element `DeviceDefinition.conformsTo.source` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `Equivalent`. DeviceDefinition.version version maps to wider concept DeviceDefinition.version DeviceDefinition.version Element `DeviceDefinition.version` is mapped to FHIR R4 element `DeviceDefinition.version` as `Equivalent`. DeviceDefinition.safety safety is equivalent to DeviceDefinition.safety DeviceDefinition.safety Element `DeviceDefinition.safety` is mapped to FHIR R4 element `DeviceDefinition.safety` as `Equivalent`. DeviceDefinition.shelfLifeStorage shelfLifeStorage is equivalent to DeviceDefinition.shelfLifeStorage DeviceDefinition.shelfLifeStorage Element `DeviceDefinition.shelfLifeStorage` is mapped to FHIR R4 element `DeviceDefinition.shelfLifeStorage` as `Equivalent`. DeviceDefinition.languageCode languageCode is equivalent to DeviceDefinition.languageCode DeviceDefinition.languageCode Element `DeviceDefinition.languageCode` is mapped to FHIR R4 element `DeviceDefinition.languageCode` as `Equivalent`. DeviceDefinition.property property maps to wider concept DeviceDefinition.property DeviceDefinition.property Element `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.type type is equivalent to DeviceDefinition.property.type DeviceDefinition.property.type Element `DeviceDefinition.property.type` is mapped to FHIR R4 element `DeviceDefinition.property.type` as `Equivalent`. DeviceDefinition.property.value[x] value[x] is related to DeviceDefinition.property.valueCode DeviceDefinition.property.valueCode 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. is related to DeviceDefinition.property.valueQuantity DeviceDefinition.property.valueQuantity 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. DeviceDefinition.owner owner is equivalent to DeviceDefinition.owner DeviceDefinition.owner Element `DeviceDefinition.owner` is mapped to FHIR R4 element `DeviceDefinition.owner` as `Equivalent`. DeviceDefinition.contact contact is equivalent to DeviceDefinition.contact DeviceDefinition.contact Element `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.note note is equivalent to DeviceDefinition.note DeviceDefinition.note Element `DeviceDefinition.note` is mapped to FHIR R4 element `DeviceDefinition.note` as `Equivalent`. DeviceDefinition.material material maps to wider concept DeviceDefinition.material DeviceDefinition.material Element `DeviceDefinition.material` is mapped to FHIR R4 element `DeviceDefinition.material` as `Equivalent`. DeviceDefinition.material.substance substance is equivalent to DeviceDefinition.material.substance DeviceDefinition.material.substance Element `DeviceDefinition.material.substance` is mapped to FHIR R4 element `DeviceDefinition.material.substance` as `Equivalent`. DeviceDefinition.material.alternate alternate is equivalent to DeviceDefinition.material.alternate DeviceDefinition.material.alternate Element `DeviceDefinition.material.alternate` is mapped to FHIR R4 element `DeviceDefinition.material.alternate` as `Equivalent`. DeviceDefinition.material.allergenicIndicator allergenicIndicator is equivalent to DeviceDefinition.material.allergenicIndicator DeviceDefinition.material.allergenicIndicator Element `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 Code Relationship Target Code Comment DeviceDefinition.udiDeviceIdentifier (udiDeviceIdentifier) is equivalent to Extension (R5: udiDeviceIdentifier) Element `DeviceDefinition.udiDeviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier` as `Equivalent`. DeviceDefinition.udiDeviceIdentifier.deviceIdentifier (deviceIdentifier) is equivalent to Extension.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 to Extension.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 to Extension.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 concept Extension.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 concept Extension.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 concept Extension.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 concept Extension.extension:udiDeviceIdentifier 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). 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 Code Relationship Target Code Comment DeviceDefinition.udiDeviceIdentifier.marketDistribution (marketDistribution) maps to wider concept Extension (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 concept Extension.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 concept Extension.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 Code Relationship Target Code Comment DeviceDefinition.regulatoryIdentifier (regulatoryIdentifier) maps to wider concept Extension (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 concept Extension.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 concept Extension.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 concept Extension.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 concept Extension.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 Code Relationship Target Code Comment DeviceDefinition.partNumber (partNumber) maps to wider concept Extension (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 Code Relationship Target Code Comment DeviceDefinition.classification (classification) maps to wider concept Extension (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 concept Extension.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 concept Extension.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 Code Relationship Target Code Comment DeviceDefinition.hasPart (hasPart) maps to wider concept Extension (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 concept Extension.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 concept Extension.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 Code Relationship Target Code Comment DeviceDefinition.packaging (packaging) maps to wider concept Extension (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 concept Extension.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 concept Extension.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 concept Extension.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 concept Extension.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 concept Extension.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 concept Extension.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 concept Extension.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 concept Extension.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 Code Relationship Target Code Comment DeviceDefinition.version.type (type) maps to wider concept Extension (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 Code Relationship Target Code Comment DeviceDefinition.version.component (component) maps to wider concept Extension (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 Code Relationship Target Code Comment DeviceDefinition.version.value (value) maps to wider concept Extension (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 Code Relationship Target Code Comment DeviceDefinition.property.value[x] (value[x]) maps to wider concept Extension (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 Code Relationship Target Code Comment DeviceDefinition.link (link) maps to wider concept Extension (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 concept Extension.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 concept Extension.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 Code Relationship Target Code Comment DeviceDefinition.productionIdentifierInUDI (productionIdentifierInUDI) maps to wider concept Extension (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 Code Relationship Target Code Comment DeviceDefinition.guideline (guideline) maps to wider concept Extension (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 concept Extension.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 concept Extension.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 to Extension.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 concept Extension.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 concept Extension.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 concept Extension.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 concept Extension.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 Code Relationship Target Code Comment DeviceDefinition.correctiveAction (correctiveAction) maps to wider concept Extension (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 concept Extension.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 concept Extension.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 concept Extension.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 Code Relationship Target Code Comment DeviceDefinition.chargeItem (chargeItem) maps to wider concept Extension (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 concept Extension.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 concept Extension.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 concept Extension.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 concept Extension.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).
Cross-version mapping for FHIR R5 DeviceDefinition to FHIR R4 DeviceDefinition
This ConceptMap represents cross-version mappings for elements from a FHIR R5 DeviceDefinition to FHIR R4.
Element `DeviceDefinition.meta` is mapped to FHIR R4 element `DeviceDefinition.meta` as `Equivalent`.
Element `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.
Element `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).
Element `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.
Element `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.
Element `DeviceDefinition.identifier` is mapped to FHIR R4 element `DeviceDefinition.identifier` as `Equivalent`.
Element `DeviceDefinition.udiDeviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier` as `Equivalent`.
Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` as `Equivalent`.
Element `DeviceDefinition.udiDeviceIdentifier.issuer` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.issuer` as `Equivalent`.
Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` is mapped to FHIR R4 element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` as `Equivalent`.
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`.
Element `DeviceDefinition.deviceName` is mapped to FHIR R4 element `DeviceDefinition.deviceName` as `Equivalent`.
Element `DeviceDefinition.deviceName.name` is mapped to FHIR R4 element `DeviceDefinition.deviceName.name` as `Equivalent`.
Element `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.
Element `DeviceDefinition.modelNumber` is mapped to FHIR R4 element `DeviceDefinition.modelNumber` as `Equivalent`.
Element `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`.
Element `DeviceDefinition.conformsTo.category` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `SourceIsNarrowerThanTarget`.
Element `DeviceDefinition.conformsTo.specification` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `SourceIsNarrowerThanTarget`.
Element `DeviceDefinition.conformsTo.version` is mapped to FHIR R4 element `DeviceDefinition.specialization.version` as `SourceIsBroaderThanTarget`.
Element `DeviceDefinition.conformsTo.source` is mapped to FHIR R4 element `DeviceDefinition.specialization` as `Equivalent`.
Element `DeviceDefinition.version` is mapped to FHIR R4 element `DeviceDefinition.version` as `Equivalent`.
Element `DeviceDefinition.safety` is mapped to FHIR R4 element `DeviceDefinition.safety` as `Equivalent`.
Element `DeviceDefinition.shelfLifeStorage` is mapped to FHIR R4 element `DeviceDefinition.shelfLifeStorage` as `Equivalent`.
Element `DeviceDefinition.languageCode` is mapped to FHIR R4 element `DeviceDefinition.languageCode` as `Equivalent`.
Element `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.
Element `DeviceDefinition.property.type` is mapped to FHIR R4 element `DeviceDefinition.property.type` as `Equivalent`.
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.
Element `DeviceDefinition.owner` is mapped to FHIR R4 element `DeviceDefinition.owner` as `Equivalent`.
Element `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.
Element `DeviceDefinition.note` is mapped to FHIR R4 element `DeviceDefinition.note` as `Equivalent`.
Element `DeviceDefinition.material` is mapped to FHIR R4 element `DeviceDefinition.material` as `Equivalent`.
Element `DeviceDefinition.material.substance` is mapped to FHIR R4 element `DeviceDefinition.material.substance` as `Equivalent`.
Element `DeviceDefinition.material.alternate` is mapped to FHIR R4 element `DeviceDefinition.material.alternate` as `Equivalent`.
Element `DeviceDefinition.material.allergenicIndicator` is mapped to FHIR R4 element `DeviceDefinition.material.allergenicIndicator` as `Equivalent`.
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).
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).
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).
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).
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.
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).
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).
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).
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).
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.
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.
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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
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).
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.
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).
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).
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).
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).
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).
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.
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).
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).
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).
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.
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.
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.
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).
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).
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'.
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).
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).
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).
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).
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).
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).
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).