Generated Narrative: ConceptMap R4B-DeviceDefinition-element-map-to-R3 Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/3.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to http://hl7.org/fhir/StructureDefinition/Basic|3.0.2 Source Code Relationship Target Code Comment DeviceDefinition.meta (meta) is equivalent to Basic.meta Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `DeviceDefinition.meta` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.implicitRules (implicitRules) is equivalent to Basic.implicitRules Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `DeviceDefinition.implicitRules` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.implicitRules` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. DeviceDefinition.language (language) is equivalent to Basic.language Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `DeviceDefinition.language` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.language` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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 Basic.text Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `DeviceDefinition.text` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.text` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. DeviceDefinition.contained (contained) is equivalent to Basic.contained Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `DeviceDefinition.contained` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.contained` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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 Basic.identifier Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `DeviceDefinition.identifier` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.identifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: Unique Device Identifier (UDI) Barcode string (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.udiDeviceIdentifier (udiDeviceIdentifier) maps to wider concept Extension (R4B: Unique Device Identifier (UDI) Barcode string (new)) Element `DeviceDefinition.udiDeviceIdentifier` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.udiDeviceIdentifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.udiDeviceIdentifier.deviceIdentifier (deviceIdentifier) maps to wider concept Extension.extension:deviceIdentifier (R4B: The identifier that is to be associated with every Device that references this DeviceDefintiion for the issuer and jurisdication porvided in the DeviceDefinition.udiDeviceIdentifier (new)) Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.udiDeviceIdentifier.issuer (issuer) maps to wider concept Extension.extension:issuer (R4B: The organization that assigns the identifier algorithm (new)) Element `DeviceDefinition.udiDeviceIdentifier.issuer` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.issuer` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.udiDeviceIdentifier.issuer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.udiDeviceIdentifier.jurisdiction (jurisdiction) maps to wider concept Extension.extension:jurisdiction (R4B: The jurisdiction to which the deviceIdentifier applies (new)) Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: Name of device manufacturer (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.manufacturer[x] (manufacturer[x]) maps to wider concept Extension (R4B: Name of device manufacturer (new)) Element `DeviceDefinition.manufacturer[x]` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.manufacturer[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: A name given to the device to identify it (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.deviceName (deviceName) maps to wider concept Extension (R4B: A name given to the device to identify it (new)) Element `DeviceDefinition.deviceName` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.deviceName` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.deviceName.name (name) maps to wider concept Extension.extension:name (R4B: The name of the device (new)) Element `DeviceDefinition.deviceName.name` is part of an existing definition because parent element `DeviceDefinition.deviceName` requires a cross-version extension. Element `DeviceDefinition.deviceName.name` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.deviceName.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.deviceName.type (type) maps to wider concept Extension.extension:type (R4B: udi-label-name | user-friendly-name | patient-reported-name | manufacturer-name | model-name | other (new)) Element `DeviceDefinition.deviceName.type` is part of an existing definition because parent element `DeviceDefinition.deviceName` requires a cross-version extension. Element `DeviceDefinition.deviceName.type` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.deviceName.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: The model number for the device (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.modelNumber (modelNumber) maps to wider concept Extension (R4B: The model number for the device (new)) Element `DeviceDefinition.modelNumber` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.modelNumber` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: What kind of device or device system this is (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.type (type) maps to wider concept Extension (R4B: What kind of device or device system this is (new)) Element `DeviceDefinition.type` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: The capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.specialization (specialization) maps to wider concept Extension (R4B: The capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication (new)) Element `DeviceDefinition.specialization` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.specialization` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.specialization.systemType (systemType) maps to wider concept Extension.extension:systemType (R4B: The standard that is used to operate and communicate (new)) Element `DeviceDefinition.specialization.systemType` is part of an existing definition because parent element `DeviceDefinition.specialization` requires a cross-version extension. Element `DeviceDefinition.specialization.systemType` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.specialization.systemType` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.specialization.version (version) maps to wider concept Extension.extension:version (R4B: The version of the standard that is used to operate and communicate (new)) Element `DeviceDefinition.specialization.version` is part of an existing definition because parent element `DeviceDefinition.specialization` requires a cross-version extension. Element `DeviceDefinition.specialization.version` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.specialization.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: Available versions (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.version (version) maps to wider concept Extension (R4B: Available versions (new)) Element `DeviceDefinition.version` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: Safety characteristics of the device (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.safety (safety) maps to wider concept Extension (R4B: Safety characteristics of the device (new)) Element `DeviceDefinition.safety` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.safety` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: Shelf Life and storage information (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.shelfLifeStorage (shelfLifeStorage) maps to wider concept Extension (R4B: Shelf Life and storage information (new)) Element `DeviceDefinition.shelfLifeStorage` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.shelfLifeStorage` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: Dimensions, color etc. (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.physicalCharacteristics (physicalCharacteristics) maps to wider concept Extension (R4B: Dimensions, color etc. (new)) Element `DeviceDefinition.physicalCharacteristics` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.physicalCharacteristics` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: Language code for the human-readable text strings produced by the device (all supported) (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.languageCode (languageCode) maps to wider concept Extension (R4B: Language code for the human-readable text strings produced by the device (all supported) (new)) Element `DeviceDefinition.languageCode` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.languageCode` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: Device capabilities (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.capability (capability) maps to wider concept Extension (R4B: Device capabilities (new)) Element `DeviceDefinition.capability` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.capability` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.capability.type (type) maps to wider concept Extension.extension:type (R4B: Type of capability (new)) Element `DeviceDefinition.capability.type` is part of an existing definition because parent element `DeviceDefinition.capability` requires a cross-version extension. Element `DeviceDefinition.capability.type` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.capability.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.capability.description (description) maps to wider concept Extension.extension:description (R4B: Description of capability (new)) Element `DeviceDefinition.capability.description` is part of an existing definition because parent element `DeviceDefinition.capability` requires a cross-version extension. Element `DeviceDefinition.capability.description` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.capability.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.property (property) maps to wider concept Extension (R4B: The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties (new)) Element `DeviceDefinition.property` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.property` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.property.type (type) maps to wider concept Extension.extension:type (R4B: Code that specifies the property DeviceDefinitionPropetyCode (Extensible) (new)) Element `DeviceDefinition.property.type` is part of an existing definition because parent element `DeviceDefinition.property` requires a cross-version extension. Element `DeviceDefinition.property.type` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.property.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.property.valueQuantity (valueQuantity) maps to wider concept Extension.extension:valueQuantity (R4B: Property value as a quantity (new)) Element `DeviceDefinition.property.valueQuantity` is part of an existing definition because parent element `DeviceDefinition.property` requires a cross-version extension. Element `DeviceDefinition.property.valueQuantity` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.property.valueQuantity` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.property.valueCode (valueCode) maps to wider concept Extension.extension:valueCode (R4B: Property value as a code, e.g., NTP4 (synced to NTP) (new)) Element `DeviceDefinition.property.valueCode` is part of an existing definition because parent element `DeviceDefinition.property` requires a cross-version extension. Element `DeviceDefinition.property.valueCode` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.property.valueCode` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: Organization responsible for device (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.owner (owner) maps to wider concept Extension (R4B: Organization responsible for device (new)) Element `DeviceDefinition.owner` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.owner` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: Access to on-line information (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.onlineInformation (onlineInformation) maps to wider concept Extension (R4B: Access to on-line information (new)) Element `DeviceDefinition.onlineInformation` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.onlineInformation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: Device notes and comments (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.note (note) maps to wider concept Extension (R4B: Device notes and comments (new)) Element `DeviceDefinition.note` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.note` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: The quantity of the device present in the packaging (e.g. the number of devices present in a pack, or the number of devices in the same package of the medicinal product) (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.quantity (quantity) maps to wider concept Extension (R4B: The quantity of the device present in the packaging (e.g. the number of devices present in a pack, or the number of devices in the same package of the medicinal product) (new)) Element `DeviceDefinition.quantity` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.quantity` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 19 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: The parent device it can be part of (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.parentDevice (parentDevice) maps to wider concept Extension (R4B: The parent device it can be part of (new)) Element `DeviceDefinition.parentDevice` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.parentDevice` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Group 20 Mapping from http://hl7.org/fhir/StructureDefinition/DeviceDefinition|4.3.0 to R4B: A substance used to create the material(s) of which the device is made (new)version: 0.1.0) Source Code Relationship Target Code Comment DeviceDefinition.material (material) maps to wider concept Extension (R4B: A substance used to create the material(s) of which the device is made (new)) Element `DeviceDefinition.material` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.material` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.material.substance (substance) maps to wider concept Extension.extension:substance (R4B: The substance (new)) Element `DeviceDefinition.material.substance` is part of an existing definition because parent element `DeviceDefinition.material` requires a cross-version extension. Element `DeviceDefinition.material.substance` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.material.substance` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.material.alternate (alternate) maps to wider concept Extension.extension:alternate (R4B: Indicates an alternative material of the device (new)) Element `DeviceDefinition.material.alternate` is part of an existing definition because parent element `DeviceDefinition.material` requires a cross-version extension. Element `DeviceDefinition.material.alternate` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.material.alternate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). DeviceDefinition.material.allergenicIndicator (allergenicIndicator) maps to wider concept Extension.extension:allergenicIndicator (R4B: Whether the substance is a known or suspected allergen (new)) Element `DeviceDefinition.material.allergenicIndicator` is part of an existing definition because parent element `DeviceDefinition.material` requires a cross-version extension. Element `DeviceDefinition.material.allergenicIndicator` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.material.allergenicIndicator` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Cross-version mapping for FHIR R4B DeviceDefinition to FHIR STU3 Basic
This ConceptMap represents cross-version mappings for elements from a FHIR R4B DeviceDefinition to FHIR STU3.
Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `DeviceDefinition.meta` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `DeviceDefinition.implicitRules` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.implicitRules` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `DeviceDefinition.language` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.language` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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 matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `DeviceDefinition.text` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.text` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `DeviceDefinition.contained` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.contained` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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 matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `DeviceDefinition.identifier` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.identifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.udiDeviceIdentifier` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.udiDeviceIdentifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.udiDeviceIdentifier.deviceIdentifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.udiDeviceIdentifier.issuer` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.issuer` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.udiDeviceIdentifier.issuer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` is part of an existing definition because parent element `DeviceDefinition.udiDeviceIdentifier` requires a cross-version extension. Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.udiDeviceIdentifier.jurisdiction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.manufacturer[x]` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.manufacturer[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.deviceName` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.deviceName` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.deviceName.name` is part of an existing definition because parent element `DeviceDefinition.deviceName` requires a cross-version extension. Element `DeviceDefinition.deviceName.name` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.deviceName.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.deviceName.type` is part of an existing definition because parent element `DeviceDefinition.deviceName` requires a cross-version extension. Element `DeviceDefinition.deviceName.type` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.deviceName.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.modelNumber` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.modelNumber` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.type` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.specialization` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.specialization` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.specialization.systemType` is part of an existing definition because parent element `DeviceDefinition.specialization` requires a cross-version extension. Element `DeviceDefinition.specialization.systemType` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.specialization.systemType` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.specialization.version` is part of an existing definition because parent element `DeviceDefinition.specialization` requires a cross-version extension. Element `DeviceDefinition.specialization.version` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.specialization.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.version` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.safety` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.safety` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.shelfLifeStorage` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.shelfLifeStorage` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.physicalCharacteristics` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.physicalCharacteristics` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.languageCode` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.languageCode` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.capability` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.capability` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.capability.type` is part of an existing definition because parent element `DeviceDefinition.capability` requires a cross-version extension. Element `DeviceDefinition.capability.type` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.capability.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.capability.description` is part of an existing definition because parent element `DeviceDefinition.capability` requires a cross-version extension. Element `DeviceDefinition.capability.description` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.capability.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.property` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.property` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.property.type` is part of an existing definition because parent element `DeviceDefinition.property` requires a cross-version extension. Element `DeviceDefinition.property.type` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.property.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.property.valueQuantity` is part of an existing definition because parent element `DeviceDefinition.property` requires a cross-version extension. Element `DeviceDefinition.property.valueQuantity` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.property.valueQuantity` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.property.valueCode` is part of an existing definition because parent element `DeviceDefinition.property` requires a cross-version extension. Element `DeviceDefinition.property.valueCode` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.property.valueCode` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.owner` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.owner` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.onlineInformation` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.onlineInformation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.note` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.note` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.quantity` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.quantity` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.parentDevice` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.parentDevice` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.material` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.material` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.material.substance` is part of an existing definition because parent element `DeviceDefinition.material` requires a cross-version extension. Element `DeviceDefinition.material.substance` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.material.substance` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.material.alternate` is part of an existing definition because parent element `DeviceDefinition.material` requires a cross-version extension. Element `DeviceDefinition.material.alternate` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.material.alternate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `DeviceDefinition.material.allergenicIndicator` is part of an existing definition because parent element `DeviceDefinition.material` requires a cross-version extension. Element `DeviceDefinition.material.allergenicIndicator` is not mapped to FHIR STU3, since FHIR R4B `DeviceDefinition` is not mapped. Element `DeviceDefinition.material.allergenicIndicator` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).