CDex Task Data Request Profile

This Task profile is used to solicit information from a system. The Data Consumer uses it when direct query transactions are not an option, and the transaction may require human intervention. It represents both the data request and the returned "data request". Data requests are supplied as codes, free-text, or FHIR Restful queries. It can also support requests for more detailed missing data using Questionnaire, CQL, and QuestionnaireResponse as supported by Da Vinci DTR.

It constrains the following elements to be *mandatory* (min=1):

• A `Task.status` with a required binding to HRex Task Status ValueSet (this element is a mandatory Task element). For guidance when the provider is not able to complete the Task, refer to the When The Task Cannot Be Completed section.
• A `Task.intent` fixed to "order" (this element is a mandatory Task element)
• A `Task.code` of "data-request-query", "data-request-code", or "data-request-questionnaire" communicating that the Data Consumer is requesting data using a FHIR RESTful query, a code (or free text), or a data request questionnaire.

- If the code is "data-request-query", the provider system returns data(s) identified by the FHIR RESTful query in the "query" input parameter. - If the code is "data-request-code", the provider system returns data(s) identified by the LOINC code in the "code" input parameter. - If the code is "data-request-questionnaire", the provider system uses Documentation Templates and Rules (DTR) to complete the Questionnaire referenced in the "questionnaire" input parameter.

• A `Task.for` element representing the member (i.e.,patient) for whom the data is being requested
• A `Task.authoredOn` to communicate the date and time this task was created
• A `Task.requester` element communicating who is requesting the data
• A `Task.owner` element representing the Provider who is being asked to provide the data

It constrains following elements to be *must support* (min=0):

• A `Task.identifier` element representing the unique data request identifier
• A `Task.basedOn` element to communicate the order (ServiceRequest, CommunicationRequest, etc.) that authorizes the data request
• A `Task.statusReason.text` to communicate the reason for the status (for example, if the Task is rejected or failed)
• A `Task.businessStatus.text` element representing the progress in retrieving the data (for example, "waiting on internal review").
• A `Task.for.reference.identifier` element representing a patient business identifier like a Member ID
• A `Task.requester.reference.identifier` element representing the Data Consumer business identifier
• A `Task.owner.reference.identifier` element representing the Provider business identifier
• A `Task.reasonCode.text` to communicate why the data is being requested
• A `Task.reasonReference.reference.identifier` for the claim, pre-auth or coverage business identifier*
• A "query" `Task.input` element to communicate to the provider what information is needed using a FHIR RESTful query.*
• A "code" `Task.input` element to communicate to the provider what information is needed using a LOINC code.*

- For the "code" `Task.input` element, an extensible LOINC® Document types value set to communicate the specific information being requested

• A `Task.input` element representing a flag to indicate whether the requested data requires a signature
• A "data" `Task.output` element referring to FHIR resource(s) representing the result(s) of the data request.

It defines the following elements to be *optional*:

• A `meta.tag` element representing work-queue hints. Refer to the Work Queues section For more information about work-queue hint codes.
• A "questionnaire" `Task.input` element to communicate to the provider a URL of a data request FHIR Questionnaire that conforms to the DTR Standard Questionnaire Profile or the DTR Questionnaire for Adaptive Form Profile.*

- A questionnaireDisplay extension to communicate the display name of the Questionnaire

• A `Task.input` element representing the purpose of use for the requested data using an extensible CDex Purpose of Use Value Set
• A "response" `Task.output` element which is a local reference to the FHIR QuestionnaireResponse resulting from the data request Questionnaire. The QuestionnaireResponse conforms to the CDex SDC QuestionnaireResponse Profile or the SDC Adaptive Questionnaire Response Profile.

It prohibits the following elements (max=0):

• `Task.focus`

\* Either a "query", "code", or "questionnaire" `Task.input` element is required