Profile Comparison between http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request vs http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Task
copyright	Used by permission of HL7 International all rights reserved Creative Commons License
date	2023-03-22T00:14:31+11:00	2024-09-28T07:22:25-04:00	Values Differ
description	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](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	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](http://hl7.org/fhir/us/davinci-hrex/2024Sep/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](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 "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)](https://hl7.org/fhir/us/davinci-dtr/STU2index.html) 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*](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. It defines the following elements to be *optional*: - A `meta.tag` element representing work-queue hints. Refer to the [Work Queues](task-based-approach.html#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](http://hl7.org/fhir/questionnaire.html) that conforms to the [DTR Standard Questionnaire Profile](http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-std-questionnaire) or the [DTR Questionnaire for Adaptive Form Profile](http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-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](ValueSet-cdex-POU.html) - 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 [CDex SDC QuestionnaireResponse Profile](StructureDefinition-cdex-sdc-questionnaireresponse.html) 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	Values Differ
experimental
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	CDexTaskDataRequest
publisher	HL7 International - Patient Care Work Group	HL7 International / Payer/Provider Information Exchange Work Group	Values Differ
purpose
status	active
title	CDex Task Data Request Profile
type	Task
url	http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
version	2.0.0	2.1.0-snapshot	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	R Type	R Description & Constraints	Comments
Task	C	0..*	Task	A task to be performed inv-1: Last modified date must be greater than or equal to authored-on date. cdex-7: If code = "data-request-code", must have one "code" input. cdex-12: If code = "data-request-query", must have one "query" input. cdex-8: If code = "data-request-questionnaire", must have one "questionnaire" input. cdex-9: Must have exactly one input that is data-query or data-code or questionnaire tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed' tdr-3: Task output SHALL be populated if status is 'completed' cdex-11: If code = "data-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse.	C	0..*	Task	A task to be performed inv-1: Last modified date must be greater than or equal to authored-on date. cdex-7: If code = "data-request-code", must have one "code" input. cdex-12: If code = "data-request-query", must have one "query" input. cdex-8: If code = "data-request-questionnaire", must have one "questionnaire" input. cdex-9: Must have exactly one input that is data-query or data-code or questionnaire tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed' tdr-3: Task output SHALL be populated if status is 'completed' cdex-11: If code = "data-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse.
id	Σ	0..1	id	Logical id of this artifact	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource	Σ	0..1	Meta	Metadata about the resource
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
versionId	Σ	0..1	id	Version specific identifier	Σ	0..1	id	Version specific identifier
lastUpdated	Σ	0..1	instant	When the resource version last changed	Σ	0..1	instant	When the resource version last changed
source	Σ	0..1	uri	Identifies where the resource comes from	Σ	0..1	uri	Identifies where the resource comes from
profile	Σ	0..*	canonical(StructureDefinition)	Profiles this resource claims to conform to	Σ	0..*	canonical(StructureDefinition)	Profiles this resource claims to conform to
security	Σ	0..*	Coding	Security Labels applied to this resource Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System.	Σ	0..*	Coding	Security Labels applied to this resource Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
Slices for tag	Σ	0..*	Coding	Tags applied to this resource Slice: Unordered, Open by pattern:$this Binding: ?? (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".	Σ	0..*	Coding	Tags applied to this resource Slice: Unordered, Open by pattern:$this Binding: ?? (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
system	Σ	0..1	uri	Identity of the terminology system	Σ	1..1	uri	Identity of the terminology system	Element minimum cardinalities differ: '0' vs '1'
version	Σ	0..1	string	Version of the system - if relevant	Σ	0..1	string	Version of the system - if relevant
code	Σ	1..1	code	Symbol in syntax defined by the system	Σ	1..1	code	Symbol in syntax defined by the system
display	Σ	0..1	string	Representation defined by the system	Σ	0..1	string	Representation defined by the system
userSelected	Σ	0..1	boolean	If this coding was chosen directly by the user	Σ	0..1	boolean	If this coding was chosen directly by the user
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored	?!	0..*	Extension	Extensions that cannot be ignored
identifier	S	0..*	Identifier	Task Instance Identifier	S	0..*	Identifier	Task Instance Identifier
instantiatesCanonical	Σ	0..1	canonical(ActivityDefinition)	Formal definition of task	Σ	0..1	canonical(ActivityDefinition)	Formal definition of task
instantiatesUri	Σ	0..1	uri	Formal definition of task	Σ	0..1	uri	Formal definition of task
basedOn	SΣ	0..*	Reference(Resource)	Authorization for data request	SΣ	0..*	Reference(Resource)	Authorization for data request
groupIdentifier	Σ	0..1	Identifier	Requisition or grouper id	Σ	0..1	Identifier	Requisition or grouper id
partOf	Σ	0..*	Reference(Task)	Composite task	Σ	0..*	Reference(Task)	Composite task
status	?!SΣC	1..1	code	draft | requested | received | accepted | + Binding: ?? (required)	?!SΣC	1..1	code	draft | requested | received | accepted | + Binding: ?? (required)
statusReason	SΣC	0..1	CodeableConcept	Reason for current status Binding Description (No ValueSet): (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow.	SΣC	0..1	CodeableConcept	Reason for current status Binding Description (No ValueSet): (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow.
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system	Σ	0..*	Coding	Code defined by a terminology system
text	SΣ	1..1	string	Plain text representation of the concept	SΣ	1..1	string	Plain text representation of the concept
businessStatus	SΣ	0..1	CodeableConcept	For example, 'waiting on internal review' Binding Description (No ValueSet): (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.	SΣ	0..1	CodeableConcept	For example, 'waiting on internal review' Binding Description (No ValueSet): (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system	Σ	0..*	Coding	Code defined by a terminology system
text	SΣ	1..1	string	Plain text representation of the concept	SΣ	1..1	string	Plain text representation of the concept
intent	SΣ	1..1	code	unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option Binding: ?? (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: order	SΣ	1..1	code	unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option Binding: ?? (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: order
priority		0..1	code	routine | urgent | asap | stat Binding: ?? (required): The task's priority.		0..1	code	routine | urgent | asap | stat Binding: ?? (required): The task's priority.
code	SΣC	1..1	CodeableConcept	data-request-code | data-request-query | data-request-questionnaire Binding: ?? (required)	SΣC	1..1	CodeableConcept	data-request-query | data-request-code | data-request-questionnaire Binding: ?? (required)
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	SΣ	1..*	Coding	Code defined by a terminology system	SΣ	1..*	Coding	Code defined by a terminology system
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
system	SΣ	0..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp	SΣ	0..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
version	Σ	0..1	string	Version of the system - if relevant	Σ	0..1	string	Version of the system - if relevant
code	SΣ	1..1	code	Symbol in syntax defined by the system	SΣ	1..1	code	Symbol in syntax defined by the system
display	Σ	0..1	string	Representation defined by the system	Σ	0..1	string	Representation defined by the system
userSelected	Σ	0..1	boolean	If this coding was chosen directly by the user	Σ	0..1	boolean	If this coding was chosen directly by the user
text	Σ	0..1	string	Plain text representation of the concept	Σ	0..1	string	Plain text representation of the concept
description	Σ	0..1	string	Human-readable explanation of task	Σ	0..1	string	Human-readable explanation of task
focus	Σ	0..0			Σ	0..0
for	SΣ	1..1	Reference(US Core Patient Profile)	Member (i.e., patient) being queried	SΣ	1..1	Reference(US Core Patient Profile(3.1.1) | US Core Patient Profile(6.1.0) | US Core Patient Profile(7.0.0))	Member (i.e., patient) being queried
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
reference	ΣC	0..1	string	Literal reference, Relative, internal or absolute URL	ΣC	0..1	string	Literal reference, Relative, internal or absolute URL
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	SΣ	0..1	Identifier	Patient Member ID	SΣ	0..1	Identifier	Patient Member ID
display	Σ	0..1	string	Text alternative for the resource	Σ	0..1	string	Text alternative for the resource
encounter	Σ	0..1	Reference(Encounter)	Healthcare event during which this task originated	Σ	0..1	Reference(Encounter)	Healthcare event during which this task originated
executionPeriod	Σ	0..1	Period	Start and end time of execution	Σ	0..1	Period	Start and end time of execution
authoredOn	SC	1..1	dateTime	Task Creation Date	SC	1..1	dateTime	Task Creation Date
lastModified	ΣC	0..1	dateTime	Task Last Modified Date	ΣC	0..1	dateTime	Task Last Modified Date
requester	SΣ	1..1	Reference(US Core Organization Profile | US Core Practitioner Profile)	Who is asking for data	SΣ	1..1	Reference(HRex Organization Profile(1.1.0-ballot) | HRex Practitioner Profile(1.1.0-ballot))	Who is asking for data
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
reference	ΣC	0..1	string	Literal reference, Relative, internal or absolute URL	ΣC	0..1	string	Literal reference, Relative, internal or absolute URL
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	SΣ	0..1	Identifier	Data Consumer ID	SΣ	0..1	Identifier	Data Consumer ID
display	Σ	0..1	string	Text alternative for the resource	Σ	0..1	string	Text alternative for the resource
performerType		0..*	CodeableConcept	Requested performer Binding: ?? (preferred): The type(s) of task performers allowed.		0..*	CodeableConcept	Requested performer Binding: ?? (preferred): The type(s) of task performers allowed.
owner	SΣ	1..1	Reference(US Core Organization Profile | US Core Practitioner Profile)	Who is being asked for data	SΣ	1..1	Reference(HRex Organization Profile(1.1.0-ballot) | HRex Practitioner Profile(1.1.0-ballot))	Who is being asked for data
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
reference	ΣC	0..1	string	Literal reference, Relative, internal or absolute URL	ΣC	0..1	string	Literal reference, Relative, internal or absolute URL
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	SΣ	0..1	Identifier	Provider ID	SΣ	0..1	Identifier	Provider ID
display	Σ	0..1	string	Text alternative for the resource	Σ	0..1	string	Text alternative for the resource
location	Σ	0..1	Reference(Location)	Where task occurs	Σ	0..1	Reference(Location)	Where task occurs
reasonCode	S	0..1	CodeableConcept	Why task is needed Binding Description (No ValueSet): (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.	S	0..1	CodeableConcept	Why task is needed Binding Description (No ValueSet): (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system	Σ	0..*	Coding	Code defined by a terminology system
text	SΣ	1..1	string	Plain text representation of the concept	SΣ	1..1	string	Plain text representation of the concept
reasonReference	S	0..1	Reference(Claim | HRex Coverage Profile)	Why task is needed	S	0..1	Reference(Claim | HRex Coverage Profile(1.1.0-ballot))	Why task is needed
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
reference	ΣC	0..1	string	Literal reference, Relative, internal or absolute URL	ΣC	0..1	string	Literal reference, Relative, internal or absolute URL
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ?? (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	SΣ	0..1	Identifier	Coverage or Claim ID	SΣ	0..1	Identifier	Coverage or Claim ID
display	Σ	0..1	string	Text alternative for the resource	Σ	0..1	string	Text alternative for the resource
insurance		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage
note		0..*	Annotation	Comments made about the task		0..*	Annotation	Comments made about the task
relevantHistory		0..*	Reference(Provenance)	Key events in history of the Task		0..*	Reference(Provenance)	Key events in history of the Task
restriction		0..1	BackboneElement	Constraints on fulfillment tasks		0..1	BackboneElement	Constraints on fulfillment tasks
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
repetitions		0..1	positiveInt	How many times to repeat		0..1	positiveInt	How many times to repeat
period		0..1	Period	When fulfillment sought		0..1	Period	When fulfillment sought
recipient		0..*	Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization)	For whom is fulfillment sought?		0..*	Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization)	For whom is fulfillment sought?
Slices for input	S	1..*	BackboneElement	Information used to perform task Slice: Unordered, Open by pattern:type	S	1..*	BackboneElement	Information used to perform task Slice: Unordered, Open by pattern:type
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc.		1..1	CodeableConcept	Label for the input Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc.
value[x]		1..1	base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference(), SampledData, Signature, Timing, ContactDetail, Contributor, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Dosage, Meta	Content to use in performing the task		1..1	base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference(), SampledData, Signature, Timing, ContactDetail, Contributor, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Dosage, Meta	Content to use in performing the task
Slices for output	SC	0..*	BackboneElement	Information produced as part of task Slice: Unordered, Open by pattern:type	SC	0..*	BackboneElement	Information produced as part of task Slice: Unordered, Open by pattern:type
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for output Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc.		1..1	CodeableConcept	Label for output Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc.
value[x]		1..1	base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference(), SampledData, Signature, Timing, ContactDetail, Contributor, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Dosage, Meta	Result of output		1..1	base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference(), SampledData, Signature, Timing, ContactDetail, Contributor, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Dosage, Meta	Result of output
Documentation for this format