Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions
The FHIR R5 resource is represented in FHIR R4 via the DeviceDefinition 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: R5DeviceDefinitionElementMapToR4
| Source Element (FHIR R5) | Target(s) | Comments |
|---|---|---|
DeviceDefinition |
||
DeviceDefinition.meta |
DeviceDefinition.meta | Element DeviceDefinition.meta is mapped to FHIR R4 element DeviceDefinition.meta as Equivalent. |
DeviceDefinition.implicitRules |
DeviceDefinition.implicitRules | Element DeviceDefinition.implicitRules is mapped to FHIR R4 element DeviceDefinition.implicitRules as Equivalent. |
DeviceDefinition.language |
DeviceDefinition.language | Element DeviceDefinition.language is mapped to FHIR R4 element DeviceDefinition.language as Equivalent. |
DeviceDefinition.text |
DeviceDefinition.text | Element DeviceDefinition.text is mapped to FHIR R4 element DeviceDefinition.text as Equivalent. |
DeviceDefinition.contained |
DeviceDefinition.contained | Element DeviceDefinition.contained is mapped to FHIR R4 element DeviceDefinition.contained as Equivalent. |
DeviceDefinition.description |
Standard Extension: artifact-description | Element DeviceDefinition.description has a context of DeviceDefinition based on following the parent source element upwards and mapping to DeviceDefinition.Element DeviceDefinition.description has no mapping targets in FHIR R4. 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 |
DeviceDefinition.identifier | Element DeviceDefinition.identifier is mapped to FHIR R4 element DeviceDefinition.identifier as Equivalent. |
DeviceDefinition.udiDeviceIdentifier |
DeviceDefinition.udiDeviceIdentifier Extension: ExtensionDeviceDefinition_UdiDeviceIdentifier |
Element DeviceDefinition.udiDeviceIdentifier is mapped to FHIR R4 element DeviceDefinition.udiDeviceIdentifier as Equivalent.Creating extension because element DeviceDefinition.udiDeviceIdentifier is a content reference and requires an extesion definition. |
DeviceDefinition.udiDeviceIdentifier.deviceIdentifier |
DeviceDefinition.udiDeviceIdentifier.deviceIdentifier | Element DeviceDefinition.udiDeviceIdentifier.deviceIdentifier is mapped to FHIR R4 element DeviceDefinition.udiDeviceIdentifier.deviceIdentifier as Equivalent. |
DeviceDefinition.udiDeviceIdentifier.issuer |
DeviceDefinition.udiDeviceIdentifier.issuer | Element DeviceDefinition.udiDeviceIdentifier.issuer is mapped to FHIR R4 element DeviceDefinition.udiDeviceIdentifier.issuer as Equivalent. |
DeviceDefinition.udiDeviceIdentifier.jurisdiction |
DeviceDefinition.udiDeviceIdentifier.jurisdiction | Element DeviceDefinition.udiDeviceIdentifier.jurisdiction is mapped to FHIR R4 element DeviceDefinition.udiDeviceIdentifier.jurisdiction as Equivalent. |
DeviceDefinition.udiDeviceIdentifier.marketDistribution |
Extension: ExtensionDeviceDefinition_UdiDeviceIdentifier_MarketDistribution | 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 |
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 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 |
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 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.regulatoryIdentifier |
Extension: ExtensionDeviceDefinition_RegulatoryIdentifier | 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). |
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 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 |
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 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 |
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 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 |
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 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). |
DeviceDefinition.partNumber |
Extension: ExtensionDeviceDefinition_PartNumber | 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). |
DeviceDefinition.manufacturer |
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 |
DeviceDefinition.deviceName | Element DeviceDefinition.deviceName is mapped to FHIR R4 element DeviceDefinition.deviceName as Equivalent. |
DeviceDefinition.deviceName.name |
DeviceDefinition.deviceName.name | Element DeviceDefinition.deviceName.name is mapped to FHIR R4 element DeviceDefinition.deviceName.name as Equivalent. |
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 |
DeviceDefinition.modelNumber | Element DeviceDefinition.modelNumber is mapped to FHIR R4 element DeviceDefinition.modelNumber as Equivalent. |
DeviceDefinition.classification |
Extension: ExtensionDeviceDefinition_Classification | 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). |
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 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 |
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 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). |
DeviceDefinition.conformsTo |
DeviceDefinition.specialization Standard Extension: device-conformsTo |
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 |
DeviceDefinition.specialization | Element DeviceDefinition.conformsTo.category is mapped to FHIR R4 element DeviceDefinition.specialization as SourceIsNarrowerThanTarget. |
DeviceDefinition.conformsTo.specification |
DeviceDefinition.specialization | Element DeviceDefinition.conformsTo.specification is mapped to FHIR R4 element DeviceDefinition.specialization as SourceIsNarrowerThanTarget. |
DeviceDefinition.conformsTo.version |
DeviceDefinition.specialization.version | Element DeviceDefinition.conformsTo.version is mapped to FHIR R4 element DeviceDefinition.specialization.version as SourceIsBroaderThanTarget. |
DeviceDefinition.conformsTo.source |
DeviceDefinition.specialization | Element DeviceDefinition.conformsTo.source is mapped to FHIR R4 element DeviceDefinition.specialization as Equivalent. |
DeviceDefinition.hasPart |
Extension: ExtensionDeviceDefinition_HasPart | 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 |
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 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 |
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 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). |
DeviceDefinition.packaging |
Extension: ExtensionDeviceDefinition_Packaging | 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 |
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 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 |
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 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 |
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 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 |
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 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 |
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 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 |
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 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 |
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 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 |
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 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). |
DeviceDefinition.version |
DeviceDefinition.version | Element DeviceDefinition.version is mapped to FHIR R4 element DeviceDefinition.version as Equivalent. |
DeviceDefinition.version.type |
Extension: ExtensionDeviceDefinition_Version_Type | 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). |
DeviceDefinition.version.component |
Extension: ExtensionDeviceDefinition_Version_Component | 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). |
DeviceDefinition.version.value |
Extension: ExtensionDeviceDefinition_Version_Value | 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). |
DeviceDefinition.safety |
DeviceDefinition.safety | Element DeviceDefinition.safety is mapped to FHIR R4 element DeviceDefinition.safety as Equivalent. |
DeviceDefinition.shelfLifeStorage |
DeviceDefinition.shelfLifeStorage | Element DeviceDefinition.shelfLifeStorage is mapped to FHIR R4 element DeviceDefinition.shelfLifeStorage as Equivalent. |
DeviceDefinition.languageCode |
DeviceDefinition.languageCode | Element DeviceDefinition.languageCode is mapped to FHIR R4 element DeviceDefinition.languageCode as Equivalent. |
DeviceDefinition.property |
DeviceDefinition.property | Element DeviceDefinition.property is mapped to FHIR R4 element DeviceDefinition.property as Equivalent. |
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] |
DeviceDefinition.property.valueCode DeviceDefinition.property.valueQuantity Extension: ExtensionDeviceDefinition_Property_Value |
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. |
DeviceDefinition.owner |
DeviceDefinition.owner | Element DeviceDefinition.owner is mapped to FHIR R4 element DeviceDefinition.owner as Equivalent. |
DeviceDefinition.contact |
DeviceDefinition.contact Standard Extension: artifact-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. |
DeviceDefinition.link |
Extension: ExtensionDeviceDefinition_Link | 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 |
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 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 |
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 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). |
DeviceDefinition.note |
DeviceDefinition.note | Element DeviceDefinition.note is mapped to FHIR R4 element DeviceDefinition.note as Equivalent. |
DeviceDefinition.material |
DeviceDefinition.material | Element DeviceDefinition.material is mapped to FHIR R4 element DeviceDefinition.material as Equivalent. |
DeviceDefinition.material.substance |
DeviceDefinition.material.substance | Element DeviceDefinition.material.substance is mapped to FHIR R4 element DeviceDefinition.material.substance as Equivalent. |
DeviceDefinition.material.alternate |
DeviceDefinition.material.alternate | Element DeviceDefinition.material.alternate is mapped to FHIR R4 element DeviceDefinition.material.alternate as Equivalent. |
DeviceDefinition.material.allergenicIndicator |
DeviceDefinition.material.allergenicIndicator | Element DeviceDefinition.material.allergenicIndicator is mapped to FHIR R4 element DeviceDefinition.material.allergenicIndicator as Equivalent. |
DeviceDefinition.productionIdentifierInUDI |
Extension: ExtensionDeviceDefinition_ProductionIdentifierInUDI | 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). |
DeviceDefinition.guideline |
Extension: ExtensionDeviceDefinition_Guideline | 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). |
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 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 |
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 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 |
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 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 |
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 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). |
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 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). |
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 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). |
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 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). |
DeviceDefinition.correctiveAction |
Extension: ExtensionDeviceDefinition_CorrectiveAction | 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 |
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 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). |
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 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 |
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 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). |
DeviceDefinition.chargeItem |
Extension: ExtensionDeviceDefinition_ChargeItem | 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 |
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 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 |
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 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 |
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 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 |
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 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). |