Extensions for Using Data Elements from FHIR R5 in FHIR STU3
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R5 in FHIR STU3 - Downloaded Version null See the Directory of published versions

Lookup for Profile_R5_DeviceDefinition_R3

Lookup for FHIR R5 DeviceDefinition for use in FHIR STU3

The FHIR R5 resource is represented in FHIR STU3 via the Basic resource.

Note that there is a profile defined to simplify use of this cross-version resource representation:Profile: DeviceDefinition

A computable version of the following element information is available in: R5DeviceDefinitionElementMapToR3

Source Element (FHIR R5) Target(s) Comments
DeviceDefinition    
DeviceDefinition.meta 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 R5 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 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 R5 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).
DeviceDefinition.language 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 R5 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).
DeviceDefinition.text 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 R5 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).
DeviceDefinition.contained 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 R5 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).
DeviceDefinition.description Standard Extension: artifact-description Element DeviceDefinition.description is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.description has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
An externally-defined extension that has been mapped as the representation of FHIR R5 element DeviceDefinition.description: http://hl7.org/fhir/StructureDefinition/artifact-description.
DeviceDefinition.identifier 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 R5 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).
DeviceDefinition.udiDeviceIdentifier Extension: ExtensionDeviceDefinition_UdiDeviceIdentifier Element DeviceDefinition.udiDeviceIdentifier is not mapped to FHIR STU3, since FHIR R5 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 Extension: ExtensionDeviceDefinition_UdiDeviceIdentifier Slice:deviceIdentifier 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 R5 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 Extension: ExtensionDeviceDefinition_UdiDeviceIdentifier Slice:issuer 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 R5 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 Extension: ExtensionDeviceDefinition_UdiDeviceIdentifier Slice:jurisdiction 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 R5 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).
DeviceDefinition.udiDeviceIdentifier.marketDistribution Extension: ExtensionDeviceDefinition_UdiDeviceIdentifier Slice:marketDistribution Element DeviceDefinition.udiDeviceIdentifier.marketDistribution is part of an existing definition because parent element DeviceDefinition.udiDeviceIdentifier requires a cross-version extension.
Element DeviceDefinition.udiDeviceIdentifier.marketDistribution is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.udiDeviceIdentifier.marketDistribution has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod Extension: ExtensionDeviceDefinition_UdiDeviceIdentifier_MarketDistribution Slice:marketPeriod 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 is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.udiDeviceIdentifier.marketDistribution.marketPeriod has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction Extension: ExtensionDeviceDefinition_UdiDeviceIdentifier_MarketDistribution Slice:subJurisdiction 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 is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.udiDeviceIdentifier.marketDistribution.subJurisdiction has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.regulatoryIdentifier Extension: ExtensionDeviceDefinition_RegulatoryIdentifier Element DeviceDefinition.regulatoryIdentifier is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.regulatoryIdentifier has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.regulatoryIdentifier.type Extension: ExtensionDeviceDefinition_RegulatoryIdentifier Slice:type Element DeviceDefinition.regulatoryIdentifier.type is part of an existing definition because parent element DeviceDefinition.regulatoryIdentifier requires a cross-version extension.
Element DeviceDefinition.regulatoryIdentifier.type is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.regulatoryIdentifier.type has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.regulatoryIdentifier.deviceIdentifier Extension: ExtensionDeviceDefinition_RegulatoryIdentifier Slice:deviceIdentifier Element DeviceDefinition.regulatoryIdentifier.deviceIdentifier is part of an existing definition because parent element DeviceDefinition.regulatoryIdentifier requires a cross-version extension.
Element DeviceDefinition.regulatoryIdentifier.deviceIdentifier is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.regulatoryIdentifier.deviceIdentifier has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.regulatoryIdentifier.issuer Extension: ExtensionDeviceDefinition_RegulatoryIdentifier Slice:issuer Element DeviceDefinition.regulatoryIdentifier.issuer is part of an existing definition because parent element DeviceDefinition.regulatoryIdentifier requires a cross-version extension.
Element DeviceDefinition.regulatoryIdentifier.issuer is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.regulatoryIdentifier.issuer has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.regulatoryIdentifier.jurisdiction Extension: ExtensionDeviceDefinition_RegulatoryIdentifier Slice:jurisdiction Element DeviceDefinition.regulatoryIdentifier.jurisdiction is part of an existing definition because parent element DeviceDefinition.regulatoryIdentifier requires a cross-version extension.
Element DeviceDefinition.regulatoryIdentifier.jurisdiction is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.regulatoryIdentifier.jurisdiction has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.partNumber Extension: ExtensionDeviceDefinition_PartNumber Element DeviceDefinition.partNumber is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.partNumber has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.manufacturer Extension: ExtensionDeviceDefinition_Manufacturer Element DeviceDefinition.manufacturer is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.manufacturer has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.deviceName Extension: ExtensionDeviceDefinition_DeviceName Element DeviceDefinition.deviceName is not mapped to FHIR STU3, since FHIR R5 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 Extension: ExtensionDeviceDefinition_DeviceName Slice:name 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 R5 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 Extension: ExtensionDeviceDefinition_DeviceName Slice:type 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 R5 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).
DeviceDefinition.modelNumber Extension: ExtensionDeviceDefinition_ModelNumber Element DeviceDefinition.modelNumber is not mapped to FHIR STU3, since FHIR R5 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).
DeviceDefinition.classification Extension: ExtensionDeviceDefinition_Classification Element DeviceDefinition.classification is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.classification has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.classification.type Extension: ExtensionDeviceDefinition_Classification Slice:type Element DeviceDefinition.classification.type is part of an existing definition because parent element DeviceDefinition.classification requires a cross-version extension.
Element DeviceDefinition.classification.type is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.classification.type has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.classification.justification Extension: ExtensionDeviceDefinition_Classification Slice:justification Element DeviceDefinition.classification.justification is part of an existing definition because parent element DeviceDefinition.classification requires a cross-version extension.
Element DeviceDefinition.classification.justification is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.classification.justification has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.conformsTo Standard Extension: device-conformsTo Element DeviceDefinition.conformsTo is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.conformsTo has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
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 Extension: ExtensionDeviceDefinition_ConformsTo Slice:category Element DeviceDefinition.conformsTo.category is part of an existing definition because parent element DeviceDefinition.conformsTo requires a cross-version extension.
Element DeviceDefinition.conformsTo.category is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.conformsTo.category has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.conformsTo.specification Extension: ExtensionDeviceDefinition_ConformsTo Slice:specification Element DeviceDefinition.conformsTo.specification is part of an existing definition because parent element DeviceDefinition.conformsTo requires a cross-version extension.
Element DeviceDefinition.conformsTo.specification is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.conformsTo.specification has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.conformsTo.version Extension: ExtensionDeviceDefinition_ConformsTo Slice:version Element DeviceDefinition.conformsTo.version is part of an existing definition because parent element DeviceDefinition.conformsTo requires a cross-version extension.
Element DeviceDefinition.conformsTo.version is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.conformsTo.version has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.conformsTo.source Extension: ExtensionDeviceDefinition_ConformsTo Slice:source Element DeviceDefinition.conformsTo.source is part of an existing definition because parent element DeviceDefinition.conformsTo requires a cross-version extension.
Element DeviceDefinition.conformsTo.source is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.conformsTo.source has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.hasPart Extension: ExtensionDeviceDefinition_HasPart Element DeviceDefinition.hasPart is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.hasPart has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.hasPart.reference Extension: ExtensionDeviceDefinition_HasPart Slice:reference Element DeviceDefinition.hasPart.reference is part of an existing definition because parent element DeviceDefinition.hasPart requires a cross-version extension.
Element DeviceDefinition.hasPart.reference is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.hasPart.reference has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.hasPart.count Extension: ExtensionDeviceDefinition_HasPart Slice:count Element DeviceDefinition.hasPart.count is part of an existing definition because parent element DeviceDefinition.hasPart requires a cross-version extension.
Element DeviceDefinition.hasPart.count is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.hasPart.count has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging Extension: ExtensionDeviceDefinition_Packaging Element DeviceDefinition.packaging is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.packaging has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.identifier Extension: ExtensionDeviceDefinition_Packaging Slice:identifier Element DeviceDefinition.packaging.identifier is part of an existing definition because parent element DeviceDefinition.packaging requires a cross-version extension.
Element DeviceDefinition.packaging.identifier is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.packaging.identifier has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.type Extension: ExtensionDeviceDefinition_Packaging Slice:type Element DeviceDefinition.packaging.type is part of an existing definition because parent element DeviceDefinition.packaging requires a cross-version extension.
Element DeviceDefinition.packaging.type is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.packaging.type has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.count Extension: ExtensionDeviceDefinition_Packaging Slice:count Element DeviceDefinition.packaging.count is part of an existing definition because parent element DeviceDefinition.packaging requires a cross-version extension.
Element DeviceDefinition.packaging.count is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.packaging.count has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.distributor Extension: ExtensionDeviceDefinition_Packaging Slice:distributor Element DeviceDefinition.packaging.distributor is part of an existing definition because parent element DeviceDefinition.packaging requires a cross-version extension.
Element DeviceDefinition.packaging.distributor is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.packaging.distributor has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.distributor.name Extension: ExtensionDeviceDefinition_Packaging_Distributor Slice:name 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 is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.packaging.distributor.name has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.distributor.organizationReference Extension: ExtensionDeviceDefinition_Packaging_Distributor Slice:organizationReference 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 is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.packaging.distributor.organizationReference has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.udiDeviceIdentifier Extension: ExtensionDeviceDefinition_Packaging Slice:udiDeviceIdentifier
Extension: ExtensionDeviceDefinition_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 is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.packaging.udiDeviceIdentifier has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.packaging.packaging Extension: ExtensionDeviceDefinition_Packaging Slice:packaging Element DeviceDefinition.packaging.packaging is part of an existing definition because parent element DeviceDefinition.packaging requires a cross-version extension.
Element DeviceDefinition.packaging.packaging is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.packaging.packaging has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.version Extension: ExtensionDeviceDefinition_Version Element DeviceDefinition.version is not mapped to FHIR STU3, since FHIR R5 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).
DeviceDefinition.version.type Extension: ExtensionDeviceDefinition_Version Slice:type Element DeviceDefinition.version.type is part of an existing definition because parent element DeviceDefinition.version requires a cross-version extension.
Element DeviceDefinition.version.type is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.version.type has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.version.component Extension: ExtensionDeviceDefinition_Version Slice:component Element DeviceDefinition.version.component is part of an existing definition because parent element DeviceDefinition.version requires a cross-version extension.
Element DeviceDefinition.version.component is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.version.component has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.version.value Extension: ExtensionDeviceDefinition_Version Slice:value Element DeviceDefinition.version.value is part of an existing definition because parent element DeviceDefinition.version requires a cross-version extension.
Element DeviceDefinition.version.value is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.version.value has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.safety Extension: ExtensionDeviceDefinition_Safety Element DeviceDefinition.safety is not mapped to FHIR STU3, since FHIR R5 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).
DeviceDefinition.shelfLifeStorage Extension: ExtensionDeviceDefinition_ShelfLifeStorage Element DeviceDefinition.shelfLifeStorage is not mapped to FHIR STU3, since FHIR R5 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).
DeviceDefinition.languageCode Extension: ExtensionDeviceDefinition_LanguageCode Element DeviceDefinition.languageCode is not mapped to FHIR STU3, since FHIR R5 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).
DeviceDefinition.property Extension: ExtensionDeviceDefinition_Property Element DeviceDefinition.property is not mapped to FHIR STU3, since FHIR R5 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 Extension: ExtensionDeviceDefinition_Property Slice:type 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 R5 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.value[x] Extension: ExtensionDeviceDefinition_Property Slice:value Element DeviceDefinition.property.value[x] is part of an existing definition because parent element DeviceDefinition.property requires a cross-version extension.
Element DeviceDefinition.property.value[x] is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.property.value[x] has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.owner Extension: ExtensionDeviceDefinition_Owner Element DeviceDefinition.owner is not mapped to FHIR STU3, since FHIR R5 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).
DeviceDefinition.contact Standard Extension: artifact-contact Element DeviceDefinition.contact is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.contact has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
An externally-defined extension that has been mapped as the representation of FHIR R5 element DeviceDefinition.contact: http://hl7.org/fhir/StructureDefinition/artifact-contact.
DeviceDefinition.link Extension: ExtensionDeviceDefinition_Link Element DeviceDefinition.link is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.link has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.link.relation Extension: ExtensionDeviceDefinition_Link Slice:relation Element DeviceDefinition.link.relation is part of an existing definition because parent element DeviceDefinition.link requires a cross-version extension.
Element DeviceDefinition.link.relation is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.link.relation has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.link.relatedDevice Extension: ExtensionDeviceDefinition_Link Slice:relatedDevice Element DeviceDefinition.link.relatedDevice is part of an existing definition because parent element DeviceDefinition.link requires a cross-version extension.
Element DeviceDefinition.link.relatedDevice is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.link.relatedDevice has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.note Extension: ExtensionDeviceDefinition_Note Element DeviceDefinition.note is not mapped to FHIR STU3, since FHIR R5 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).
DeviceDefinition.material Extension: ExtensionDeviceDefinition_Material Element DeviceDefinition.material is not mapped to FHIR STU3, since FHIR R5 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 Extension: ExtensionDeviceDefinition_Material Slice:substance 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 R5 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 Extension: ExtensionDeviceDefinition_Material Slice:alternate 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 R5 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 Extension: ExtensionDeviceDefinition_Material Slice:allergenicIndicator 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 R5 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).
DeviceDefinition.productionIdentifierInUDI Extension: ExtensionDeviceDefinition_ProductionIdentifierInUDI Element DeviceDefinition.productionIdentifierInUDI is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.productionIdentifierInUDI has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.guideline Extension: ExtensionDeviceDefinition_Guideline Element DeviceDefinition.guideline is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.guideline has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.guideline.useContext Extension: ExtensionDeviceDefinition_Guideline Slice:useContext Element DeviceDefinition.guideline.useContext is part of an existing definition because parent element DeviceDefinition.guideline requires a cross-version extension.
Element DeviceDefinition.guideline.useContext is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.guideline.useContext has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.guideline.usageInstruction Extension: ExtensionDeviceDefinition_Guideline Slice:usageInstruction Element DeviceDefinition.guideline.usageInstruction is part of an existing definition because parent element DeviceDefinition.guideline requires a cross-version extension.
Element DeviceDefinition.guideline.usageInstruction is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.guideline.usageInstruction has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.guideline.relatedArtifact Extension: ExtensionDeviceDefinition_Guideline Slice:relatedArtifact Element DeviceDefinition.guideline.relatedArtifact is part of an existing definition because parent element DeviceDefinition.guideline requires a cross-version extension.
Element DeviceDefinition.guideline.relatedArtifact is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.guideline.relatedArtifact has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.guideline.indication Extension: ExtensionDeviceDefinition_Guideline Slice:indication Element DeviceDefinition.guideline.indication is part of an existing definition because parent element DeviceDefinition.guideline requires a cross-version extension.
Element DeviceDefinition.guideline.indication is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.guideline.indication has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.guideline.contraindication Extension: ExtensionDeviceDefinition_Guideline Slice:contraindication Element DeviceDefinition.guideline.contraindication is part of an existing definition because parent element DeviceDefinition.guideline requires a cross-version extension.
Element DeviceDefinition.guideline.contraindication is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.guideline.contraindication has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.guideline.warning Extension: ExtensionDeviceDefinition_Guideline Slice:warning Element DeviceDefinition.guideline.warning is part of an existing definition because parent element DeviceDefinition.guideline requires a cross-version extension.
Element DeviceDefinition.guideline.warning is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.guideline.warning has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.guideline.intendedUse Extension: ExtensionDeviceDefinition_Guideline Slice:intendedUse Element DeviceDefinition.guideline.intendedUse is part of an existing definition because parent element DeviceDefinition.guideline requires a cross-version extension.
Element DeviceDefinition.guideline.intendedUse is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.guideline.intendedUse has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.correctiveAction Extension: ExtensionDeviceDefinition_CorrectiveAction Element DeviceDefinition.correctiveAction is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.correctiveAction has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.correctiveAction.recall Extension: ExtensionDeviceDefinition_CorrectiveAction Slice:recall Element DeviceDefinition.correctiveAction.recall is part of an existing definition because parent element DeviceDefinition.correctiveAction requires a cross-version extension.
Element DeviceDefinition.correctiveAction.recall is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.correctiveAction.recall has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.correctiveAction.scope Extension: ExtensionDeviceDefinition_CorrectiveAction Slice:scope Element DeviceDefinition.correctiveAction.scope is part of an existing definition because parent element DeviceDefinition.correctiveAction requires a cross-version extension.
Element DeviceDefinition.correctiveAction.scope is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.correctiveAction.scope has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.correctiveAction.period Extension: ExtensionDeviceDefinition_CorrectiveAction Slice:period Element DeviceDefinition.correctiveAction.period is part of an existing definition because parent element DeviceDefinition.correctiveAction requires a cross-version extension.
Element DeviceDefinition.correctiveAction.period is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.correctiveAction.period has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.chargeItem Extension: ExtensionDeviceDefinition_ChargeItem Element DeviceDefinition.chargeItem is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.chargeItem has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.chargeItem.chargeItemCode Extension: ExtensionDeviceDefinition_ChargeItem Slice:chargeItemCode Element DeviceDefinition.chargeItem.chargeItemCode is part of an existing definition because parent element DeviceDefinition.chargeItem requires a cross-version extension.
Element DeviceDefinition.chargeItem.chargeItemCode is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.chargeItem.chargeItemCode has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.chargeItem.count Extension: ExtensionDeviceDefinition_ChargeItem Slice:count Element DeviceDefinition.chargeItem.count is part of an existing definition because parent element DeviceDefinition.chargeItem requires a cross-version extension.
Element DeviceDefinition.chargeItem.count is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.chargeItem.count has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.chargeItem.effectivePeriod Extension: ExtensionDeviceDefinition_ChargeItem Slice:effectivePeriod Element DeviceDefinition.chargeItem.effectivePeriod is part of an existing definition because parent element DeviceDefinition.chargeItem requires a cross-version extension.
Element DeviceDefinition.chargeItem.effectivePeriod is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.chargeItem.effectivePeriod has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
DeviceDefinition.chargeItem.useContext Extension: ExtensionDeviceDefinition_ChargeItem Slice:useContext Element DeviceDefinition.chargeItem.useContext is part of an existing definition because parent element DeviceDefinition.chargeItem requires a cross-version extension.
Element DeviceDefinition.chargeItem.useContext is not mapped to FHIR STU3, since FHIR R5 DeviceDefinition is not mapped.
Element DeviceDefinition.chargeItem.useContext has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).