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

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

Lookup for Profile_R3_ProcessResponse_R4B_Task

Lookup for FHIR STU3 ProcessResponse for use in FHIR R4B

The FHIR STU3 resource is represented in FHIR R4B via the Task resource.

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

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

Source Element (FHIR STU3) Target(s) Comments
ProcessResponse    
ProcessResponse.meta Task.meta
Extension: ExtensionProcessResponse_Meta		 Element ProcessResponse.meta is mapped to FHIR R4B element Task.meta as SourceIsBroaderThanTarget.
The mappings for ProcessResponse.meta do not cover the following types: Meta.
The mappings for ProcessResponse.meta do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
ProcessResponse.implicitRules Task.implicitRules Element ProcessResponse.implicitRules is mapped to FHIR R4B element Task.implicitRules as Equivalent.
ProcessResponse.language Task.language Element ProcessResponse.language is mapped to FHIR R4B element Task.language as Equivalent.
ProcessResponse.text Task.text
Extension: ExtensionProcessResponse_Text		 Element ProcessResponse.text is mapped to FHIR R4B element Task.text as SourceIsBroaderThanTarget.
The mappings for ProcessResponse.text do not cover the following types: Narrative.
The mappings for ProcessResponse.text do not cover the following types based on type expansion: div, status.
ProcessResponse.contained Task.contained Element ProcessResponse.contained is mapped to FHIR R4B element Task.contained as SourceIsBroaderThanTarget.
ProcessResponse.identifier Task.identifier
Extension: ExtensionProcessResponse_Identifier		 Element ProcessResponse.identifier is mapped to FHIR R4B element Task.identifier as SourceIsBroaderThanTarget.
The mappings for ProcessResponse.identifier do not cover the following types: Identifier.
The mappings for ProcessResponse.identifier do not cover the following types based on type expansion: assigner, period, system, type, use, value.
ProcessResponse.status Task.status
Extension: ExtensionProcessResponse_Status		 Element ProcessResponse.status is mapped to FHIR R4B element Task.status as RelatedTo.
The mappings for ProcessResponse.status do not allow expression of the necessary codes, per the bindings on the source and target.
The target context Task.status is a modifier element, so this extension does not need to be defined as a modifier.
ProcessResponse.created Extension: ExtensionProcessResponse_Created Element ProcessResponse.created has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.created has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ProcessResponse.organization Extension: ExtensionProcessResponse_Organization Element ProcessResponse.organization has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.organization has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ProcessResponse.request Extension: ExtensionProcessResponse_Request Element ProcessResponse.request has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.request has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ProcessResponse.outcome Extension: ExtensionProcessResponse_Outcome Element ProcessResponse.outcome has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.outcome has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ProcessResponse.disposition Extension: ExtensionProcessResponse_Disposition Element ProcessResponse.disposition has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.disposition has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ProcessResponse.requestProvider Extension: ExtensionProcessResponse_RequestProvider Element ProcessResponse.requestProvider has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.requestProvider has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ProcessResponse.requestOrganization Extension: ExtensionProcessResponse_RequestOrganization Element ProcessResponse.requestOrganization has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.requestOrganization has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ProcessResponse.form Extension: ExtensionProcessResponse_Form Element ProcessResponse.form has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.form has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ProcessResponse.processNote Extension: ExtensionProcessResponse_ProcessNote Element ProcessResponse.processNote has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.processNote has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ProcessResponse.processNote.type Extension: ExtensionProcessResponse_ProcessNote Slice:type Element ProcessResponse.processNote.type is part of an existing definition because parent element ProcessResponse.processNote requires a cross-version extension.
Element ProcessResponse.processNote.type has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.processNote.type has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ProcessResponse.processNote.text Extension: ExtensionProcessResponse_ProcessNote Slice:text Element ProcessResponse.processNote.text is part of an existing definition because parent element ProcessResponse.processNote requires a cross-version extension.
Element ProcessResponse.processNote.text has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.processNote.text has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ProcessResponse.error Extension: ExtensionProcessResponse_Error Element ProcessResponse.error has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.error has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ProcessResponse.communicationRequest Extension: ExtensionProcessResponse_CommunicationRequest Element ProcessResponse.communicationRequest has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessResponse.communicationRequest has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).