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

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

Lookup for Profile_R2_ProcessRequest_R5_Task

Lookup for FHIR DSTU2 ProcessRequest for use in FHIR R5

The FHIR DSTU2 resource is represented in FHIR R5 via the Task resource.

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

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

Source Element (FHIR DSTU2) Target(s) Comments
ProcessRequest    
ProcessRequest.meta Task.meta
Extension: ExtensionProcessRequest_Meta		 Element ProcessRequest.meta is mapped to FHIR R5 element Task.meta as SourceIsBroaderThanTarget.
The mappings for ProcessRequest.meta do not cover the following types: Meta.
The mappings for ProcessRequest.meta do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
ProcessRequest.implicitRules Task.implicitRules Element ProcessRequest.implicitRules is mapped to FHIR R5 element Task.implicitRules as Equivalent.
ProcessRequest.language Task.language Element ProcessRequest.language is mapped to FHIR R5 element Task.language as Equivalent.
ProcessRequest.text Task.text
Extension: ExtensionProcessRequest_Text		 Element ProcessRequest.text is mapped to FHIR R5 element Task.text as SourceIsBroaderThanTarget.
The mappings for ProcessRequest.text do not cover the following types: Narrative.
The mappings for ProcessRequest.text do not cover the following types based on type expansion: div, status.
ProcessRequest.contained Task.contained Element ProcessRequest.contained is mapped to FHIR R5 element Task.contained as SourceIsBroaderThanTarget.
ProcessRequest.action Extension: ExtensionProcessRequest_Action Element ProcessRequest.action has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.action has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.identifier Task.identifier
Extension: ExtensionProcessRequest_Identifier		 Element ProcessRequest.identifier is mapped to FHIR R5 element Task.identifier as SourceIsBroaderThanTarget.
The mappings for ProcessRequest.identifier do not cover the following types: Identifier.
The mappings for ProcessRequest.identifier do not cover the following types based on type expansion: assigner, period, system, type, use, value.
ProcessRequest.ruleset Extension: ExtensionProcessRequest_Ruleset Element ProcessRequest.ruleset has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.ruleset has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.originalRuleset Extension: ExtensionProcessRequest_OriginalRuleset Element ProcessRequest.originalRuleset has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.originalRuleset has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.created Extension: ExtensionProcessRequest_Created Element ProcessRequest.created has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.created has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.target Extension: ExtensionProcessRequest_Target Element ProcessRequest.target has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.target has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.provider Extension: ExtensionProcessRequest_Provider Element ProcessRequest.provider has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.provider has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.organization Extension: ExtensionProcessRequest_Organization Element ProcessRequest.organization has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.organization has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.request Extension: ExtensionProcessRequest_Request Element ProcessRequest.request has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.request has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.response Extension: ExtensionProcessRequest_Response Element ProcessRequest.response has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.response has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.nullify Extension: ExtensionProcessRequest_Nullify Element ProcessRequest.nullify has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.nullify has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.reference Extension: ExtensionProcessRequest_Reference Element ProcessRequest.reference has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.reference has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.item Extension: ExtensionProcessRequest_Item Element ProcessRequest.item has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.item has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.item.sequenceLinkId Extension: ExtensionProcessRequest_Item Slice:sequenceLinkId Element ProcessRequest.item.sequenceLinkId is part of an existing definition because parent element ProcessRequest.item requires a cross-version extension.
Element ProcessRequest.item.sequenceLinkId has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.item.sequenceLinkId has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.include Extension: ExtensionProcessRequest_Include Element ProcessRequest.include has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.include has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.exclude Extension: ExtensionProcessRequest_Exclude Element ProcessRequest.exclude has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.exclude has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
ProcessRequest.period Extension: ExtensionProcessRequest_Period Element ProcessRequest.period has a context of Task based on following the parent source element upwards and mapping to Task.
Element ProcessRequest.period has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).