Extensions for Using Data Elements from FHIR STU3 in FHIR R4B - Downloaded Version null See the Directory of published versions
The FHIR STU3 resource is represented in FHIR R4B via the Basic resource.
Note that there is a profile defined to simplify use of this cross-version resource representation:Profile: DeviceComponent
A computable version of the following element information is available in: R3DeviceComponentElementMapToR4B
| Source Element (FHIR STU3) | Target(s) | Comments |
|---|---|---|
DeviceComponent |
||
DeviceComponent.meta |
Basic.meta | Element matches Basic element path Basic.meta (Resource.meta), use that element instead.Element DeviceComponent.meta is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.meta has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.implicitRules |
Basic.implicitRules | Element matches Basic element path Basic.implicitRules (Resource.implicitRules), use that element instead.Element DeviceComponent.implicitRules is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.implicitRules has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.language |
Basic.language | Element matches Basic element path Basic.language (Resource.language), use that element instead.Element DeviceComponent.language is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.language has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.text |
Basic.text | Element matches Basic element path Basic.text (DomainResource.text), use that element instead.Element DeviceComponent.text is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.text has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.contained |
Basic.contained | Element matches Basic element path Basic.contained (DomainResource.contained), use that element instead.Element DeviceComponent.contained is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.contained has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.identifier |
Basic.identifier | Element matches Basic element path Basic.identifier (Basic.identifier), use that element instead.Element DeviceComponent.identifier is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.identifier has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.type |
Extension: ExtensionDeviceComponent_Type | Element DeviceComponent.type is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.type has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.lastSystemChange |
Extension: ExtensionDeviceComponent_LastSystemChange | Element DeviceComponent.lastSystemChange is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.lastSystemChange has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.source |
Extension: ExtensionDeviceComponent_Source | Element DeviceComponent.source is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.source has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.parent |
Extension: ExtensionDeviceComponent_Parent | Element DeviceComponent.parent is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.parent has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.operationalStatus |
Extension: ExtensionDeviceComponent_OperationalStatus | Element DeviceComponent.operationalStatus is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.operationalStatus has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.parameterGroup |
Extension: ExtensionDeviceComponent_ParameterGroup | Element DeviceComponent.parameterGroup is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.parameterGroup has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.measurementPrinciple |
Extension: ExtensionDeviceComponent_MeasurementPrinciple | Element DeviceComponent.measurementPrinciple is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.measurementPrinciple has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.productionSpecification |
Extension: ExtensionDeviceComponent_ProductionSpecification | Element DeviceComponent.productionSpecification is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.productionSpecification has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.productionSpecification.specType |
Extension: ExtensionDeviceComponent_ProductionSpecification Slice:specType | Element DeviceComponent.productionSpecification.specType is part of an existing definition because parent element DeviceComponent.productionSpecification requires a cross-version extension.Element DeviceComponent.productionSpecification.specType is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.productionSpecification.specType has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.productionSpecification.componentId |
Extension: ExtensionDeviceComponent_ProductionSpecification Slice:componentId | Element DeviceComponent.productionSpecification.componentId is part of an existing definition because parent element DeviceComponent.productionSpecification requires a cross-version extension.Element DeviceComponent.productionSpecification.componentId is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.productionSpecification.componentId has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.productionSpecification.productionSpec |
Extension: ExtensionDeviceComponent_ProductionSpecification Slice:productionSpec | Element DeviceComponent.productionSpecification.productionSpec is part of an existing definition because parent element DeviceComponent.productionSpecification requires a cross-version extension.Element DeviceComponent.productionSpecification.productionSpec is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.productionSpecification.productionSpec has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |
DeviceComponent.languageCode |
Extension: ExtensionDeviceComponent_LanguageCode | Element DeviceComponent.languageCode is not mapped to FHIR R4B, since FHIR STU3 DeviceComponent is not mapped.Element DeviceComponent.languageCode has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element). |