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

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

Lookup for Profile_R5_DeviceRequest_R4B

Lookup for FHIR R5 DeviceRequest for use in FHIR R4B

The FHIR R5 resource is represented in FHIR R4B via the DeviceRequest resource.

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

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

Source Element (FHIR R5) Target(s) Comments
DeviceRequest    
DeviceRequest.meta DeviceRequest.meta Element DeviceRequest.meta is mapped to FHIR R4B element DeviceRequest.meta as Equivalent.
DeviceRequest.implicitRules DeviceRequest.implicitRules Element DeviceRequest.implicitRules is mapped to FHIR R4B element DeviceRequest.implicitRules as Equivalent.
DeviceRequest.language DeviceRequest.language Element DeviceRequest.language is mapped to FHIR R4B element DeviceRequest.language as Equivalent.
DeviceRequest.text DeviceRequest.text Element DeviceRequest.text is mapped to FHIR R4B element DeviceRequest.text as Equivalent.
DeviceRequest.contained DeviceRequest.contained Element DeviceRequest.contained is mapped to FHIR R4B element DeviceRequest.contained as Equivalent.
DeviceRequest.identifier DeviceRequest.identifier Element DeviceRequest.identifier is mapped to FHIR R4B element DeviceRequest.identifier as Equivalent.
DeviceRequest.instantiatesCanonical DeviceRequest.instantiatesCanonical Element DeviceRequest.instantiatesCanonical is mapped to FHIR R4B element DeviceRequest.instantiatesCanonical as Equivalent.
DeviceRequest.instantiatesUri DeviceRequest.instantiatesUri Element DeviceRequest.instantiatesUri is mapped to FHIR R4B element DeviceRequest.instantiatesUri as Equivalent.
DeviceRequest.basedOn DeviceRequest.basedOn Element DeviceRequest.basedOn is mapped to FHIR R4B element DeviceRequest.basedOn as Equivalent.
DeviceRequest.replaces DeviceRequest.priorRequest
Standard Extension: alternate-reference
Element DeviceRequest.replaces is mapped to FHIR R4B element DeviceRequest.priorRequest as SourceIsBroaderThanTarget.
The mappings for DeviceRequest.replaces do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension alternate-reference has been mapped as the representation of FHIR R5 element DeviceRequest.replaces with unmapped reference targets: DeviceRequest.
DeviceRequest.groupIdentifier DeviceRequest.groupIdentifier Element DeviceRequest.groupIdentifier is mapped to FHIR R4B element DeviceRequest.groupIdentifier as Equivalent.
DeviceRequest.status DeviceRequest.status Element DeviceRequest.status is mapped to FHIR R4B element DeviceRequest.status as Equivalent.
DeviceRequest.intent DeviceRequest.intent Element DeviceRequest.intent is mapped to FHIR R4B element DeviceRequest.intent as Equivalent.
DeviceRequest.priority DeviceRequest.priority Element DeviceRequest.priority is mapped to FHIR R4B element DeviceRequest.priority as Equivalent.
DeviceRequest.doNotPerform Modifier Extension: ExtensionDeviceRequest_DoNotPerform Element DeviceRequest.doNotPerform has a context of DeviceRequest based on following the parent source element upwards and mapping to DeviceRequest.
Element DeviceRequest.doNotPerform has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
DeviceRequest.code DeviceRequest.code[x] Element DeviceRequest.code is mapped to FHIR R4B element DeviceRequest.code[x] as SourceIsBroaderThanTarget.
The target context DeviceRequest.code[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element DeviceRequest.
DeviceRequest.quantity Extension: ExtensionDeviceRequest_Quantity Element DeviceRequest.quantity has a context of DeviceRequest based on following the parent source element upwards and mapping to DeviceRequest.
Element DeviceRequest.quantity has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
DeviceRequest.parameter DeviceRequest.parameter Element DeviceRequest.parameter is mapped to FHIR R4B element DeviceRequest.parameter as Equivalent.
DeviceRequest.parameter.code DeviceRequest.parameter.code Element DeviceRequest.parameter.code is mapped to FHIR R4B element DeviceRequest.parameter.code as Equivalent.
DeviceRequest.parameter.value[x] DeviceRequest.parameter.value[x] Element DeviceRequest.parameter.value[x] is mapped to FHIR R4B element DeviceRequest.parameter.value[x] as Equivalent.
The target context DeviceRequest.parameter.value[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element DeviceRequest.parameter.
DeviceRequest.subject DeviceRequest.subject Element DeviceRequest.subject is mapped to FHIR R4B element DeviceRequest.subject as Equivalent.
DeviceRequest.encounter DeviceRequest.encounter Element DeviceRequest.encounter is mapped to FHIR R4B element DeviceRequest.encounter as Equivalent.
DeviceRequest.occurrence[x] DeviceRequest.occurrence[x] Element DeviceRequest.occurrence[x] is mapped to FHIR R4B element DeviceRequest.occurrence[x] as Equivalent.
The target context DeviceRequest.occurrence[x] is a choice-type element and cannot directly hold extensions. The context is moved up to parent element DeviceRequest.
DeviceRequest.authoredOn DeviceRequest.authoredOn Element DeviceRequest.authoredOn is mapped to FHIR R4B element DeviceRequest.authoredOn as Equivalent.
DeviceRequest.requester DeviceRequest.requester Element DeviceRequest.requester is mapped to FHIR R4B element DeviceRequest.requester as Equivalent.
DeviceRequest.performer DeviceRequest.performer
DeviceRequest.performerType
Extension: ExtensionDeviceRequest_Performer
Element DeviceRequest.performer is mapped to FHIR R4B element DeviceRequest.performerType as SourceIsBroaderThanTarget.
Element DeviceRequest.performer is mapped to FHIR R4B element DeviceRequest.performer as SourceIsBroaderThanTarget.
The mappings for DeviceRequest.performer do not cover the following types: CodeableReference.
DeviceRequest.reason DeviceRequest.reasonCode
DeviceRequest.reasonReference
Extension: ExtensionDeviceRequest_Reason
Element DeviceRequest.reason is mapped to FHIR R4B element DeviceRequest.reasonCode as SourceIsBroaderThanTarget.
Element DeviceRequest.reason is mapped to FHIR R4B element DeviceRequest.reasonReference as SourceIsBroaderThanTarget.
The mappings for DeviceRequest.reason do not cover the following types: CodeableReference.
DeviceRequest.asNeeded Extension: ExtensionDeviceRequest_AsNeeded Element DeviceRequest.asNeeded has a context of DeviceRequest based on following the parent source element upwards and mapping to DeviceRequest.
Element DeviceRequest.asNeeded has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
DeviceRequest.asNeededFor Extension: ExtensionDeviceRequest_AsNeededFor Element DeviceRequest.asNeededFor has a context of DeviceRequest based on following the parent source element upwards and mapping to DeviceRequest.
Element DeviceRequest.asNeededFor has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
DeviceRequest.insurance DeviceRequest.insurance Element DeviceRequest.insurance is mapped to FHIR R4B element DeviceRequest.insurance as Equivalent.
DeviceRequest.supportingInfo DeviceRequest.supportingInfo Element DeviceRequest.supportingInfo is mapped to FHIR R4B element DeviceRequest.supportingInfo as Equivalent.
DeviceRequest.note DeviceRequest.note Element DeviceRequest.note is mapped to FHIR R4B element DeviceRequest.note as Equivalent.
DeviceRequest.relevantHistory DeviceRequest.relevantHistory Element DeviceRequest.relevantHistory is mapped to FHIR R4B element DeviceRequest.relevantHistory as Equivalent.