Task (49)

#NameSourceVerDescription
1Anliegen erfassenfhir.qpath4ms#currentR4Profil einer Aufgabe zur Erfassung von Anliegen eines Patienten zur Diskussion beim nächsten Arztbesuch
2BePerformerTaskhl7.fhir.be.referral#currentR4Subtask performed by one performer
3BeReferralTaskhl7.fhir.be.referral#currentR4The task that is referred to in the referral prescription (this is the common task for the execution of the prescription). The subtasks per performer can be found in BePerformerTask
4BSeR Referral Taskhl7.fhir.us.bser#currentR4This Task profile represents state of a task containing a BSeR referral service request.
5CDex Task Attachment Request Profilehl7.fhir.us.davinci-cdex#currentR4Payers use the [Task](http://hl7.org/StructureDefinition/Task) based profile to request additional documentation ("attachments") for claims or prior authorizations. It constrains the Task resource to minimal necessary data elements needed to request attachments and respond in a way that is compatible with existing X12 277 RFAI and 278 response transactions to allow for association and requests for (typically PDF and CCDA) documents using LOINC as the standard. It also supports 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 [contained](http://hl7.org/fhir/R4/references.html) Patient Resource defined by the [CDex Patient Demographics Profile](http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-patient-demographics) and communicating additional patient demographic data elements. - A [contained](http://hl7.org/fhir/R4/references.html) PractitionerRole Resource defined by the [CDex PractitionerRole Profile](http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-practitionerrole) to communicate the provider ID as either a unique organization/location identifier (e.g., Type 2 NPI) or unique provider identifier (e.g., Type 1 NPI) or both. - A Task.identifier element representing the payers tracking identifier (referred to as the “re-association tracking control numbers”) - A Task.status with a required binding to HRex [Task Status ValueSet](http://hl7.org/fhir/us/davinci-hrex/STU1/ValueSet-hrex-task-status.html) (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](http://hl7.org/fhir/us/davinci-cdex/STU2/task-based-approach.html#when-the-task-cannot-be-completed). - A Task.intent fixed to "order" (this element is a mandatory Task element) - A Task.code of either "attachment-request-code" or "attachment-request-questionnaire" communicating that the Payer is requesting attachments for a claim or prior authorization using a code or data request questionnaire. - If the code is "attachment-request-code", the provider system returns attachment(s) identified by the LOINC attachment code(s) in the "code" input parameter. - If the code is "attachment-request-questionnaire", the provider system uses [Documentation Templates and Rules (DTR)](http://hl7.org/fhir/us/davinci-dtr/2022May/) to complete the Questionnaire referenced in the "questionnaire" input parameter. - When either code is present, the provider system uses the $submit-attachment operation to return the information to the endpoint provided in "payer-url" input parameter. - A Task.requester.identifier element representing the Payer ID - A Task.owner.reference element fixed to "\#practionerrole" - a reference the contained PractitionerRole Resource that represents the Provider ID. - A Task.for.reference element fixed to "\#patient" - a reference the contained Patient Resource that represents basic Patient demographic data. - A Task.reasonCode to communicate whether the attachments are for a Claim or Prior Authorization - A Task.reasonReference.reference referencing the Claim or Prior Authorization ID (business Identifier) - A "payer-url" Task.input element representing the Payer endpoint URL to communicate to the provider to submit the attachments using the `$submit-attachment` operation It constrains following elements to be [*must support*](attachments-conformance.html#cdex-must-support-definition) (min=0): - A Task.Restriction.period element representing the due date for submitting the attachments - A Task.statusReason.text to communicate the reason for the status (for example, if the Task is rejected or failed) - A "code" Task.input element to communicate to the provider what attachments are needed using LOINC attachment codes.* - A "code" or "questionnaire" Task.input element extension representing a claim or prior authorization line item numbers associated with the attachment or questionnaire. - A "signature" Task.input element representing a flag to indicate whether the requested data requires a signature. For more information about requiring and requesting signatures, refer to the [Signatures section](http://hl7.org/fhir/us/davinci-cdex/STU2/sending-attachments.html#signatures). - A "service-date" Task.input element representing the date of service or starting date of the service for the claim or prior authorization. It SHALL be present if the attachment is for a claim. It defines the following elements to be *optional*: - A "questionnaire" Task.input element to communicate to the provider a URL of a data request [FHIR Questionnaire](http://hl7.org/fhir/questionnaire.html) that conforms to the [DTR SDC Questionnaire Profile](http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-sdc-questionnaire) or the [DTR SDC Questionnaire for Adaptive Form Profile](http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-sdc-questionnaire-adapt).* - A questionnaireDisplay extension to communicate the display name of the Questionnaire - A "POU" Task.input element representing the purpose of use (POU) for the requested data using an extensible [CDex Purpose of Use Value Set](http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-POU). For more information about sending purpose POU codes, refer to the [Purpose of Use section](http://hl7.org/fhir/us/davinci-cdex/STU2/sending-attachments.html#signatures). - A "multiple-submits" Task.input element representing a flag to indicate whether the requested data can be sent in multiple submissions - A "data-value" Task.output element referring to FHIR resource(s) representing the result(s) of the data request code. - A "response" Task.output element which is a local reference to the [FHIR QuestionnaireResponse](http://hl7.org/fhir/questionnaireresponse.html) resulting from the data request Questionnaire. The QuestionnaireResponse conforms to the [SDC Questionnaire Response Profile](http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse) or the [SDC Adaptive Questionnaire Response Profile](http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse-adapt). \* Either a "code" or a "questionnaire" Task.input element is required
6CDex Task Data Request Profilehl7.fhir.us.davinci-cdex#currentR4This 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](http://hl7.org/fhir/us/davinci-hrex/STU1/ValueSet-hrex-task-status.html) (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](http://hl7.org/fhir/us/davinci-cdex/STU2/task-based-approach.html#when-the-task-cannot-be-completed). - A Task.intent fixed to "order" (this element is a mandatory Task element) - A Task.code of either "data-request-code", "data-request-code", or "data-request-questionnaire" communicating that the Data Consumer is requesting data using a code(or free text), a FHIR RESTful query, 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)](http://hl7.org/fhir/us/davinci-dtr/2022May/) 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.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*](task-based-conformance.html#cdex-must-support-definition) (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 code. It defines the following elements to be *optional*: - A meta.tag element representing work-queue hints. - A "questionnaire" Task.input element to communicate to the provider a URL of a data request [FHIR Questionnaire](http://hl7.org/fhir/questionnaire.html) that conforms to the [DTR SDC Questionnaire Profile](http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-sdc-questionnaire) or the [DTR SDC Questionnaire for Adaptive Form Profile](http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-sdc-questionnaire-adapt).* - 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](http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-POU) - A "response" Task.output element which is a local reference to the [FHIR QuestionnaireResponse](http://hl7.org/fhir/questionnaireresponse.html) resulting from the data request Questionnaire. The QuestionnaireResponse conforms to the [SDC Questionnaire Response Profile](http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse) or the [SDC Adaptive Questionnaire Response Profile](http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse-adapt). It prohibits the following elements (max=0): - Task.focus \* Either a "query", "code", or "questionnaire" Task.input element is required
7Check-In eines Patientenfhir.qpath4ms#currentR4Profil zum Check-In eines Patienten zum nächsten Arztbesuch
8CPG Administer Medication Taskhl7.fhir.uv.cpg#currentR4Recommendation to administer a specific medication as part of the delivery of a computable clinical practice guideline
9CPG Dispense Medication Taskhl7.fhir.uv.cpg#currentR4Recommendation to dispense a specific medication as part of the delivery of a computable clinical practice guideline
10CPG Document Medication Taskhl7.fhir.uv.cpg#currentR4Recommendation to document the use of a specific medication as part of the delivery of a computable clinical practice guideline
11CPG Enrollment Taskhl7.fhir.uv.cpg#currentR4Proposal to enroll the patient in a strategy or pathway as part of a computable clinical practice guideline
12CPG Generate Report Taskhl7.fhir.uv.cpg#currentR4Proposal to generate a metric, measure, or case report as part of a computable clinical practice guideline
13CPG Propose Diagnosis Taskhl7.fhir.uv.cpg#currentR4Recommendation to propose a specific diagnosis as part of the delivery of a computable clinical practice guideline
14CPG Questionnaire Taskhl7.fhir.uv.cpg#currentR4Recommendation to collect specific information using a particular questionnaire as part of the delivery of a computable clinical practice guideline
15CPG Record Detected Issue Taskhl7.fhir.uv.cpg#currentR4Recommendation to record a specific detected issue as part of the delivery of a computable clinical practice guideline
16CPG Record Inference Taskhl7.fhir.uv.cpg#currentR4Recommendation to record a particular inference as part of the delivery of a computable clinical practice guideline
17CPG Report Flag Taskhl7.fhir.uv.cpg#currentR4Recommendation to report a flag as part of the delivery of a computable clinical practice guideline
18CPG Taskhl7.fhir.uv.cpg#currentR4Defines the expectations common to tasks that represent activities used in computable guidelines
19CRD Questionnaire Taskhl7.fhir.us.davinci-crd#currentR4This profile specifies constraints on the Task resource to support requests for form (Questionnaire) completion.
20Diagnostic Task Basehl7.fhir.au.draft.diagnostic-orders#currentR4Diagnostic Task Base
21Diagnostic Task Grouphl7.fhir.au.draft.diagnostic-orders#currentR4Diagnositic Task Group
22Diagnostic Task Requesthl7.fhir.au.draft.diagnostic-orders#currentR4Diagnostic Task Request
23Dokumente bereitstellenfhir.qpath4ms#currentR4Profil einer Aufgabe zur Bereitstellung von Dokumenten zum nächsten Arztbesuch eines Patienten
24Followup Recommendationhl7.fhir.uv.genomics-reporting#currentR4Task describing the follow-up that is recommended
25Fragebögen ausfüllenfhir.qpath4ms#currentR4Profil einer Aufgabe zum Ausfüllen von Fragebögen zum nächsten Arztbesuch eines Patienten
26HRex Task Data Request Profilehl7.fhir.us.davinci-hrex#currentR4This Task profile is used to solicit information from a system when direct query is not possible and human intervention might be required
27Medication Recommendationhl7.fhir.uv.genomics-reporting#currentR4Task proposing medication recommendations based on genetic results.
28Medikation aktualisierenfhir.qpath4ms#currentR4Profil einer Aufgabe zur Aktualisierung der aktuellen Medikation eines Patienten zum nächsten Arztbesuch
29OpenMRS Taskopenmrs.fhir.core#currentR4A Task resource represent an activity that is to be performed,and track the completion of said activity between an OpenMRS and a FHIR2
30PA Task for Referral Managementhl7.fhir.us.physical-activity#currentR4Represents a request for fulfillment of a physical activity-related referral or order and supports management of the same.
31PAO Taskhl7.fhir.us.dme-orders#currentR4PAO Task Resource Profile
32Patient Correction Taskhl7.fhir.uv.patient-corrections#currentR4Represents the process of reviewing the patient’s request for correction or the patient’s request to log a disagreement to a prior request for correction decision. This Task is spawned by the Fulfiller as a result of a post of a Communication resource that indicates a new request for correction or a new logging of a disagreement.
33PCDE Coverage Transition Task - Request Profilehl7.fhir.us.davinci-pcde#currentR4Constraints on Task when requesting a Coverage Transition Document
34PCDE Coverage Transition Task - Search Profilehl7.fhir.us.davinci-pcde#currentR4Constraints on Task when polling / searching for completed Coverage Transition Documentation
35QICore Taskhl7.fhir.us.qicore#currentR4Profile of Task for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.
36QICore Task Rejectedhl7.fhir.us.qicore#currentR4Profile of TaskRejected for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.
37Referral Taskhl7.fhir.us.bser#currentR4This Task profile represents the state of a task containing a referral service request.
38Risk Adjustment Clinical Evaluation Evidence Taskhl7.fhir.us.davinci-ra#currentR4This Task profile is used to support the risk adjustment coding gap remediation process.
39RORTaskans.fhir.fr.ror#0.1.1R4Anomalie concerant une donnée dans une ressource du ROR
40SDOHCC Task For Patienthl7.fhir.us.sdoh-clinicalcare#currentR4Profile for SDOH-related tasks to be carried out by the patient or someone acting on their behalf.
41SDOHCC Task For Referral Managementhl7.fhir.us.sdoh-clinicalcare#currentR4Profile for tasks requesting fulfillment of an SDOHCC ServiceRequest (i.e. referral for service) and subsequently tracking and managing the fulfillment of that referral.
42Specialty Rx Task - Consent Requesthl7.fhir.us.specialty-rx#currentR4This profile defines use of the Task resource to request that consent or authorization associated with prescribed product be obtained and made available to the requesting system.
43Specialty Rx Task - SMART Launchhl7.fhir.us.specialty-rx#currentR4This profile defines Task content enabling a pharmacy or other external party to prompt clinic staff to launch a SMART app and answer prescription-related questions.
44Taskndhm.in#currentR4This profile describes an activity that can be performed and tracks the state of completion of that activity. It is a representation that an activity should be or has been initiated, and eventually, represents the successful or unsuccessful completion of that activity.
45Task - Milton Keynes (Gatekeeper)hl7.eu.fhir.gk#currentR4This profile defines how to represent a task in FHIR for supporting the Milton Keynes pilot in the scope of the Gatekeeper project
46Task Questionnairehl7.fhir.uv.sdc.r4#3.0.0R4Defines how Task is used to ask for a Questionnaire to be completed
47TaskEhrLaunchhl7.fhir.uv.smart-app-launch#currentR4Defines a Task that indicates the user should launch an application using the SMART on FHIR EHR launch.
48TaskStandaloneLaunchhl7.fhir.uv.smart-app-launch#currentR4Defines a Task that indicates the user should launch an application as a standalone application.
49U.S. Data Access Framework (DAF) Task Profilehl7.fhir.us.daf#2.0.0R3
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
Task I D I D I D I D D D I I D I S
Task.definition[x] C
Task.id C C C
Task.reasonReference C D D I I D I D
Task.reasonReference.display D D
Task.reasonReference.reference C D C D
Task.reasonReference.identifier C D D C F D C F D
Task.reasonReference.identifier.value C C
Task.reasonCode C D B M D C B M C B M
Task.reasonCode.text B M C C C
Task.reasonCode.coding S C B M (2)
Task.reasonCode.coding.code C
Task.reasonCode.coding.system
Task.meta
Task.meta.tag S D B M (2) S C B M (2) S F S F
Task.meta.tag.code C
Task.meta.tag.system
Task.implicitRules C
Task.language
Task.text
Task.contained S C D (3)
Task.extension S C (3)
Task.modifierExtension S C S C (2) C
Task.identifier S C F D (2) C C S C (3) C S C F D (2) C
Task.identifier.assigner C (2)
Task.identifier.type C F (2) C D
Task.identifier.value C C (2) C
Task.identifier.system C
Task.instantiatesCanonical F D
Task.instantiatesUri
Task.basedOn C C C
Task.groupIdentifier C C
Task.partOf C C C C S C (2) S C (2) S C (2) C
Task.status B M B M F B M F B M F B M C B M F C B M C F C B M D B M D B M C C
Task.statusReason B M B M C C B M D D
Task.statusReason.text C C C C C C C
Task.businessStatus D D D B M C B M C
Task.businessStatus.text C C C
Task.intent B M F F F F F F F F C F F C F F F D F D C F C F
Task.priority B M C C D B M D C
Task.doNotPerform
Task.code C D B M C D B M F F F F F F F F F F B M C B M B M C F B M F B M C B M C B M C B M C F C B M C B M C F C F D B M C F D B M C B M C F B M C F B M C
Task.code.text
Task.code.extension S C
Task.code.coding C C
Task.code.coding.code C C
Task.code.coding.system F F
Task.description C D C D C
Task.focus C C C C C C C C C C
Task.for C C D C D C C C C C C D C C C C C C C C D C D C
Task.for.identifier D
Task.for.reference C F
Task.encounter D C
Task.requestedPeriod
Task.executionPeriod C C
Task.executionPeriod.end
Task.executionPeriod.start
Task.authoredOn C C C C C C C C C C C C C C C
Task.lastModified C C C
Task.requester C C C C C C C C C C I D C I D C C
Task.requester.reference C C
Task.requester.identifier C D D S C F D (3) S C F D (3)
Task.requester.identifier.value C (2) C (2)
Task.requestedPerformer
Task.owner C C D C D C C C C C C I D C I D C C
Task.owner.identifier D C F D C F D
Task.owner.identifier.value C C
Task.owner.reference C F C C
Task.performer
Task.performer.extension
Task.performer.modifierExtension
Task.performer.function
Task.performer.actor
Task.location
Task.reason C
Task.insurance
Task.note C
Task.note.text
Task.note.time C
Task.note.author[x] C
Task.relevantHistory
Task.restriction C C C
Task.restriction.extension
Task.restriction.modifierExtension
Task.restriction.repetitions C
Task.restriction.period C C D C C C C
Task.restriction.recipient C
Task.input S C D B M (8) S C D (6) C S C D (3) S C D (2) S C D (2) S C D (2) S C D (2) S C D (2) S C D (2) S C D (2) S C D (2) S C D (2) S C D (2) C S C D (3) I S C (2) S C D (3) S C (7) S C D (6) S C D (2) S C D (3) S C D (3) S C (3) S C (3) C
Task.input.valueUrl C
Task.input.valueIdentifier C
Task.input.valueReference C
Task.input.id C
Task.input.extension C (2) C
Task.input.extension.value[x] C (2)
Task.input.extension.url F (2)
Task.input.modifierExtension C
Task.input.type C F (7) C F (5) F (2) F F F F F F F F F F B M F (2) B M F (2) F (6) F D B M (5) C F B M C F B M (2) C F (2) F (2) F (2) C
Task.input.type.coding F
Task.input.type.text F
Task.input.value[x] C I B M (7) C B M (5) (2) D S C B M (2) (2) F (2) (6) D B M (5) C (2) (2) (2) C
Task.input.value[x].extension S C D S C D
Task.output C S C D (3) S C D (3) S C D (2) S C D (2) S C D (2) S C D (2) S C D (2) S C D (2) S C D (2) C S C (3) I C S C (3) S C D (5) S C (3) S C D (2) S C D (2) C
Task.output.id C
Task.output.extension C
Task.output.modifierExtension C C
Task.output.type F (2) F (2) F F F F F F F B M F F (2) B M F (2) F (4) F (2) C F B M C F C
Task.output.type.text F F
Task.output.value[x] C (2) C D (2) D D (2) (2) (4) S C B M (4) C C
Task.output.value[x].text C
S: There is slicing defined in the element(s)
C: There is cardinality erstrictions defined in the element(s)
I: There is invariants defined in the element(s)
F: There is a fixed or pattern value defined in the element(s)
D: There is document provided in the element(s)
B: There is terminology bindings defined in the element(s)
M: At least one of the element(s) has must-support = true
(N): The number of elements if > 1

Produced 08 Sep 2023