This page is part of the Da Vinci Clinical Documentation Exchange (v2.0.0: STU2) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

• Content
• Detailed Descriptions
• Examples
• XML
• JSON

Resource Profile: 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 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) 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 (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 that conforms to the DTR SDC Questionnaire Profile or the DTR SDC 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 SDC Questionnaire Response 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

Usage:

• Examples for this Resource Profile: Task/cdex-task-example1, Task/cdex-task-example10, Task/cdex-task-example11, Task/cdex-task-example12... Show 19 more, Task/cdex-task-example13, Task/cdex-task-example14, Task/cdex-task-example15, Task/cdex-task-example16, Task/cdex-task-example17, Task/cdex-task-example18, Task/cdex-task-example2, Task/cdex-task-example21, Task/cdex-task-example26, Task/cdex-task-example27, Task/cdex-task-example3, Task/cdex-task-example30, Task/cdex-task-example31, Task/cdex-task-example4, Task/cdex-task-example5, Task/cdex-task-example6, Task/cdex-task-example7, Task/cdex-task-example8 and Task/cdex-task-example9

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

• Differential Table
• Key Elements Table
• Snapshot Table
• Statistics/References
• All

This structure is derived from Task

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed 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.
meta		0..1	Meta	Metadata about the resource
Slices for tag		0..*	Coding	Tags applied to this resource Slice: Unordered, Open by pattern:$this
tag:All Slices				Content/Rules for all slices
system		0..1	uri	Identity of the terminology system
code		1..1	code	Symbol in syntax defined by the system
tag:work-queue		0..*	Coding	Work Queue Tag Binding: CDex Work Queue Value Set (required)
identifier	S	0..*	Identifier	Task Instance Identifier
basedOn	S	0..*	Reference(Resource)	Authorization for data request
status	SC	1..1	code	draft | requested | received | accepted | + Binding: HRex Task Status ValueSet (required)
statusReason	SC	0..1	CodeableConcept	Reason for current status
text	S	1..1	string	Plain text representation of the concept
businessStatus	S	0..1	CodeableConcept	For example, 'waiting on internal review'
text	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 Fixed Value: order
code	SC	1..1	CodeableConcept	data-request-code | data-request-query | data-request-questionnaire Binding: CDex Data Request Task Code Value Set (required)
coding	S	1..*	Coding	Code defined by a terminology system
system	S	0..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code	S	1..1	code	Symbol in syntax defined by the system
focus		0..0
for	S	1..1	Reference(US Core Patient Profile)	Member (i.e., patient) being queried
identifier	S	0..1	Identifier	Patient Member ID
authoredOn	S	1..1	dateTime	Task Creation Date
requester	S	1..1	Reference(US Core Organization Profile | US Core Practitioner Profile)	Who is asking for data
identifier	S	0..1	Identifier	Data Consumer ID
owner	S	1..1	Reference(US Core Organization Profile | US Core Practitioner Profile)	Who is being asked for data
identifier	S	0..1	Identifier	Provider ID
reasonCode	S	0..1	CodeableConcept	Why task is needed
text	S	1..1	string	Plain text representation of the concept
reasonReference	S	0..1	Reference(Claim | HRex Coverage Profile)	Why task is needed
identifier	S	0..1	Identifier	Coverage or Claim ID
Slices for input	S	1..*	BackboneElement	Information used to perform task Slice: Unordered, Open by pattern:type
input:query	SC	0..1	BackboneElement	Requested query
type	S	1..1	CodeableConcept	Label for the input Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-query
value[x]	S	1..1	string	query value
input:code	SC	0..1	BackboneElement	Requested data code
type	S	1..1	CodeableConcept	Label for the input Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-code
value[x]	S	1..1	CodeableConcept	query value Binding: US Core DocumentReference Type (extensible)
input:questionnaire	CD	0..1	BackboneElement	Data Request questionnaire
type		1..1	CodeableConcept	Label for the input Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: questionnaire
value[x]		1..1	canonical(DTR SDC Questionnaire | DTR SDC Questionnaire for adaptive form)	URL
questionnaireDisplay		0..1	string	Display name for canonical reference URL: http://hl7.org/fhir/StructureDefinition/display
input:signature	S	0..1	BackboneElement	Signature flag
type	S	1..1	CodeableConcept	Label for the input Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: signature-flag
value[x]	S	1..1	boolean	Signature flag value
input:POU		0..1	BackboneElement	Purpose of use code
type		1..1	CodeableConcept	Label for the input Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: purpose-of-use
value[x]		1..1	CodeableConcept	Purpose of use value Binding: CDex Purpose of Use Value Set (extensible)
Slices for output	SC	0..*	BackboneElement	Information produced as part of task Slice: Unordered, Open by pattern:type
output:data	S	0..*	BackboneElement	Requested data
type	S	1..1	CodeableConcept	Label for output Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-value
value[x]	S	1..1	Reference()	data reference
output:response	CD	0..1	BackboneElement	Information produced as part of task
type		1..1	CodeableConcept	Label for output Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: questionnaire-response
value[x]		1..1	Reference(SDC Questionnaire Response | Adaptive Questionnaire Response)	Reference to the QuestionnaireResponse
Documentation for this format

Terminology Bindings (Differential)

Path	Conformance	ValueSet
Task.meta.tag:work-queue	required	CDexWorkQueueCodes
Task.status	required	HRexTaskStatus
Task.code	required	CDexDataRequestTaskCode
Task.input:code.value[x]	extensible	USCoreDocumentReferenceType
Task.input:POU.value[x]	extensible	CDexPOUCodes

Constraints

Id	Grade	Path(s)	Details	Requirements
cdex-7	error	Task	If code = "data-request-code", must have one "code" input. : Task.code.coding.code.where($this='data-request-code').exists() implies Task.input.type.coding.code.where($this='data-code').exists()
cdex-8	error	Task	If code = "data-request-questionnaire", must have one "questionnaire" input. : Task.code.coding.code.where($this='data-request-questionnaire').exists() implies Task.input.type.coding.code.where($this='questionnaire').exists()
cdex-9	error	Task	Must have exactly one input that is data-query or data-code or questionnaire : Task.input.type.coding.code.where($this='data-query' or $this='data-code' or $this='questionnaire').count()=1
cdex-11	warning	Task	If code = "data-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. : (Task.code.coding.code.where($this='data-request-questionnaire').exists() and Task.status.where($this='completed').exists()) implies Task.output.type.coding.code.where($this='questionnaire-response').exists()
cdex-12	error	Task	If code = "data-request-query", must have one "query" input. : Task.code.coding.code.where($this='data-request-query').exists() implies Task.input.type.coding.code.where($this='data-query').exists()
tdr-2	error	Task	Task statusReason SHALL be populated if status is 'rejected' or 'failed' : (status = 'rejected' or status = 'failed') implies statusReason.exists()
tdr-3	error	Task	Task output SHALL be populated if status is 'completed' : (status = 'completed') implies output.exists()

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed 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.
meta	Σ	0..1	Meta	Metadata about the resource
Slices for tag	Σ	0..*	Coding	Tags applied to this resource Slice: Unordered, Open by pattern:$this Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
tag:All Slices				Content/Rules for all slices
system	Σ	0..1	uri	Identity of the terminology system
code	Σ	1..1	code	Symbol in syntax defined by the system
tag:work-queue	Σ	0..*	Coding	Work Queue Tag Binding: CDex Work Queue Value Set (required)
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	S	0..*	Identifier	Task Instance Identifier
basedOn	SΣ	0..*	Reference(Resource)	Authorization for data request
status	?!SΣC	1..1	code	draft | requested | received | accepted | + Binding: HRex Task Status ValueSet (required)
statusReason	SΣC	0..1	CodeableConcept	Reason for current status Binding: (unbound) (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow.
text	SΣ	1..1	string	Plain text representation of the concept
businessStatus	SΣ	0..1	CodeableConcept	For example, 'waiting on internal review' Binding: (unbound) (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.
text	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: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: order
code	SΣC	1..1	CodeableConcept	data-request-code | data-request-query | data-request-questionnaire Binding: CDex Data Request Task Code Value Set (required)
coding	SΣ	1..*	Coding	Code defined by a terminology system
system	SΣ	0..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code	SΣ	1..1	code	Symbol in syntax defined by the system
for	SΣ	1..1	Reference(US Core Patient Profile)	Member (i.e., patient) being queried
identifier	SΣ	0..1	Identifier	Patient Member ID
authoredOn	SC	1..1	dateTime	Task Creation Date
requester	SΣ	1..1	Reference(US Core Organization Profile | US Core Practitioner Profile)	Who is asking for data
identifier	SΣ	0..1	Identifier	Data Consumer ID
owner	SΣ	1..1	Reference(US Core Organization Profile | US Core Practitioner Profile)	Who is being asked for data
identifier	SΣ	0..1	Identifier	Provider ID
reasonCode	S	0..1	CodeableConcept	Why task is needed Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.
text	SΣ	1..1	string	Plain text representation of the concept
reasonReference	S	0..1	Reference(Claim | HRex Coverage Profile)	Why task is needed
identifier	SΣ	0..1	Identifier	Coverage or Claim ID
Slices for input	S	1..*	BackboneElement	Information used to perform task Slice: Unordered, Open by pattern:type
input:All Slices				Content/Rules for all slices
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding: (unbound) (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		Content to use in performing the task
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
input:query	SC	0..1	BackboneElement	Requested query
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-query
value[x]	S	1..1	string	query value
input:code	SC	0..1	BackboneElement	Requested data code
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-code
value[x]	S	1..1	CodeableConcept	query value Binding: US Core DocumentReference Type (extensible)
input:questionnaire	C	0..1	BackboneElement	Data Request questionnaire
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: questionnaire
value[x]		1..1	canonical(DTR SDC Questionnaire | DTR SDC Questionnaire for adaptive form)	URL
questionnaireDisplay		0..1	string	Display name for canonical reference URL: http://hl7.org/fhir/StructureDefinition/display
input:signature	S	0..1	BackboneElement	Signature flag
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: signature-flag
value[x]	S	1..1	boolean	Signature flag value
input:POU		0..1	BackboneElement	Purpose of use code
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: purpose-of-use
value[x]		1..1	CodeableConcept	Purpose of use value Binding: CDex Purpose of Use Value Set (extensible)
Slices for output	SC	0..*	BackboneElement	Information produced as part of task Slice: Unordered, Open by pattern:type
output:All Slices				Content/Rules for all slices
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for output Binding: (unbound) (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		Result of output
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
output:data	S	0..*	BackboneElement	Requested data
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for output Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-value
value[x]	S	1..1	Reference()	data reference
output:response	C	0..1	BackboneElement	Information produced as part of task
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for output Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: questionnaire-response
value[x]		1..1	Reference(SDC Questionnaire Response | Adaptive Questionnaire Response)	Reference to the QuestionnaireResponse
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code
Task.meta.tag	example	CommonTags
Task.meta.tag:work-queue	required	CDexWorkQueueCodes
Task.status	required	HRexTaskStatus
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	Fixed Value: order
Task.code	required	CDexDataRequestTaskCode
Task.reasonCode	example
Task.input.type	example
Task.input:query.type	example	Pattern: data-query
Task.input:code.type	example	Pattern: data-code
Task.input:code.value[x]	extensible	USCoreDocumentReferenceType
Task.input:questionnaire.type	example	Pattern: questionnaire
Task.input:signature.type	example	Pattern: signature-flag
Task.input:POU.type	example	Pattern: purpose-of-use
Task.input:POU.value[x]	extensible	CDexPOUCodes
Task.output.type	example
Task.output:data.type	example	Pattern: data-value
Task.output:response.type	example	Pattern: questionnaire-response

Constraints

Id	Grade	Path(s)	Details	Requirements
cdex-7	error	Task	If code = "data-request-code", must have one "code" input. : Task.code.coding.code.where($this='data-request-code').exists() implies Task.input.type.coding.code.where($this='data-code').exists()
cdex-8	error	Task	If code = "data-request-questionnaire", must have one "questionnaire" input. : Task.code.coding.code.where($this='data-request-questionnaire').exists() implies Task.input.type.coding.code.where($this='questionnaire').exists()
cdex-9	error	Task	Must have exactly one input that is data-query or data-code or questionnaire : Task.input.type.coding.code.where($this='data-query' or $this='data-code' or $this='questionnaire').count()=1
cdex-11	warning	Task	If code = "data-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. : (Task.code.coding.code.where($this='data-request-questionnaire').exists() and Task.status.where($this='completed').exists()) implies Task.output.type.coding.code.where($this='questionnaire-response').exists()
cdex-12	error	Task	If code = "data-request-query", must have one "query" input. : Task.code.coding.code.where($this='data-request-query').exists() implies Task.input.type.coding.code.where($this='data-query').exists()
tdr-2	error	Task	Task statusReason SHALL be populated if status is 'rejected' or 'failed' : (status = 'rejected' or status = 'failed') implies statusReason.exists()
tdr-3	error	Task	Task output SHALL be populated if status is 'completed' : (status = 'completed') implies output.exists()

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed 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
meta	Σ	0..1	Meta	Metadata about the resource
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
versionId	Σ	0..1	id	Version specific identifier
lastUpdated	Σ	0..1	instant	When the resource version last changed
source	Σ	0..1	uri	Identifies where the resource comes from
profile	Σ	0..*	canonical(StructureDefinition)	Profiles this resource claims to conform to
security	Σ	0..*	Coding	Security Labels applied to this resource Binding: All Security Labels (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: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
tag:All Slices				Content/Rules for all slices
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
system	Σ	0..1	uri	Identity of the terminology system
version	Σ	0..1	string	Version of the system - if relevant
code	Σ	1..1	code	Symbol in syntax defined by the system
display	Σ	0..1	string	Representation defined by the system
userSelected	Σ	0..1	boolean	If this coding was chosen directly by the user
tag:work-queue	Σ	0..*	Coding	Work Queue Tag Binding: CDex Work Queue Value Set (required)
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	S	0..*	Identifier	Task Instance Identifier
instantiatesCanonical	Σ	0..1	canonical(ActivityDefinition)	Formal definition of task
instantiatesUri	Σ	0..1	uri	Formal definition of task
basedOn	SΣ	0..*	Reference(Resource)	Authorization for data request
groupIdentifier	Σ	0..1	Identifier	Requisition or grouper id
partOf	Σ	0..*	Reference(Task)	Composite task
status	?!SΣC	1..1	code	draft | requested | received | accepted | + Binding: HRex Task Status ValueSet (required)
statusReason	SΣC	0..1	CodeableConcept	Reason for current status Binding: (unbound) (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
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system
text	SΣ	1..1	string	Plain text representation of the concept
businessStatus	SΣ	0..1	CodeableConcept	For example, 'waiting on internal review' Binding: (unbound) (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
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system
text	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: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: order
priority		0..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority.
code	SΣC	1..1	CodeableConcept	data-request-code | data-request-query | data-request-questionnaire Binding: CDex Data Request Task Code Value Set (required)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	SΣ	1..*	Coding	Code defined by a terminology system
id		0..1	string	Unique id for inter-element referencing
extension		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
version	Σ	0..1	string	Version of the system - if relevant
code	SΣ	1..1	code	Symbol in syntax defined by the system
display	Σ	0..1	string	Representation defined by the system
userSelected	Σ	0..1	boolean	If this coding was chosen directly by the user
text	Σ	0..1	string	Plain text representation of the concept
description	Σ	0..1	string	Human-readable explanation of task
for	SΣ	1..1	Reference(US Core Patient Profile)	Member (i.e., patient) being queried
id		0..1	string	Unique id for inter-element referencing
extension		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
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ResourceType (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	SΣ	0..1	Identifier	Patient Member ID
display	Σ	0..1	string	Text alternative for the resource
encounter	Σ	0..1	Reference(Encounter)	Healthcare event during which this task originated
executionPeriod	Σ	0..1	Period	Start and end time of execution
authoredOn	SC	1..1	dateTime	Task Creation Date
lastModified	Σ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
id		0..1	string	Unique id for inter-element referencing
extension		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
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ResourceType (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	SΣ	0..1	Identifier	Data Consumer ID
display	Σ	0..1	string	Text alternative for the resource
performerType		0..*	CodeableConcept	Requested performer Binding: ProcedurePerformerRoleCodes (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
id		0..1	string	Unique id for inter-element referencing
extension		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
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ResourceType (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	SΣ	0..1	Identifier	Provider ID
display	Σ	0..1	string	Text alternative for the resource
location	Σ	0..1	Reference(Location)	Where task occurs
reasonCode	S	0..1	CodeableConcept	Why task is needed Binding: (unbound) (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
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system
text	SΣ	1..1	string	Plain text representation of the concept
reasonReference	S	0..1	Reference(Claim | HRex Coverage Profile)	Why task is needed
id		0..1	string	Unique id for inter-element referencing
extension		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
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ResourceType (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	SΣ	0..1	Identifier	Coverage or Claim ID
display	Σ	0..1	string	Text alternative for the resource
insurance		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage
note		0..*	Annotation	Comments made about the task
relevantHistory		0..*	Reference(Provenance)	Key events in history of the Task
restriction		0..1	BackboneElement	Constraints on fulfillment tasks
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
repetitions		0..1	positiveInt	How many times to repeat
period		0..1	Period	When fulfillment sought
recipient		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
input:All Slices				Content/Rules for all slices
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding: (unbound) (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		Content to use in performing the task
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
input:query	SC	0..1	BackboneElement	Requested query
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-query
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]	S	1..1	string	query value
input:code	SC	0..1	BackboneElement	Requested data code
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-code
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]	S	1..1	CodeableConcept	query value Binding: US Core DocumentReference Type (extensible)
input:questionnaire	C	0..1	BackboneElement	Data Request questionnaire
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: questionnaire
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]		1..1	canonical(DTR SDC Questionnaire | DTR SDC Questionnaire for adaptive form)	URL
id		0..1	string	xml:id (or equivalent in JSON)
Slices for extension		0..*	Extension	Extension Slice: Unordered, Open by value:url
questionnaireDisplay		0..1	string	Display name for canonical reference URL: http://hl7.org/fhir/StructureDefinition/display
value		0..1	string	Primitive value for canonical
input:signature	S	0..1	BackboneElement	Signature flag
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..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
code		1..1	code	Symbol in syntax defined by the system Fixed Value: signature-flag
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]	S	1..1	boolean	Signature flag value
input:POU		0..1	BackboneElement	Purpose of use code
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..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
code		1..1	code	Symbol in syntax defined by the system Fixed Value: purpose-of-use
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]		1..1	CodeableConcept	Purpose of use value Binding: CDex Purpose of Use Value Set (extensible)
Slices for output	SC	0..*	BackboneElement	Information produced as part of task Slice: Unordered, Open by pattern:type
output:All Slices				Content/Rules for all slices
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for output Binding: (unbound) (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		Result of output
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
output:data	S	0..*	BackboneElement	Requested data
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for output Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-value
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]	S	1..1	Reference()	data reference
output:response	C	0..1	BackboneElement	Information produced as part of task
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for output Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: questionnaire-response
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]		1..1	Reference(SDC Questionnaire Response | Adaptive Questionnaire Response)	Reference to the QuestionnaireResponse
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code
Task.meta.security	extensible	All Security Labels
Task.meta.tag	example	CommonTags
Task.meta.tag:work-queue	required	CDexWorkQueueCodes
Task.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding
Task.status	required	HRexTaskStatus
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	Fixed Value: order
Task.priority	required	RequestPriority
Task.code	required	CDexDataRequestTaskCode
Task.for.type	extensible	ResourceType
Task.requester.type	extensible	ResourceType
Task.performerType	preferred	ProcedurePerformerRoleCodes
Task.owner.type	extensible	ResourceType
Task.reasonCode	example
Task.reasonReference.type	extensible	ResourceType
Task.input.type	example
Task.input:query.type	example	Pattern: data-query
Task.input:code.type	example	Pattern: data-code
Task.input:code.value[x]	extensible	USCoreDocumentReferenceType
Task.input:questionnaire.type	example	Pattern: questionnaire
Task.input:signature.type	example	Pattern: signature-flag
Task.input:POU.type	example	Pattern: purpose-of-use
Task.input:POU.value[x]	extensible	CDexPOUCodes
Task.output.type	example
Task.output:data.type	example	Pattern: data-value
Task.output:response.type	example	Pattern: questionnaire-response

This structure is derived from Task

Summary

Mandatory: 8 elements (8 nested mandatory elements)
Must-Support: 37 elements
Fixed Value: 2 elements
Prohibited: 1 element

Structures

This structure refers to these other structures:

• US Core Patient Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient)
• US Core Organization Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization)
• US Core Practitioner Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner)
• HRex Coverage Profile (http://hl7.org/fhir/us/davinci-hrex/StructureDefinition/hrex-coverage)
• DTR SDC Questionnaire (http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-sdc-questionnaire)
• DTR SDC Questionnaire for adaptive form (http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-sdc-questionnaire-adapt)
• SDC Questionnaire Response (http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse)
• Adaptive Questionnaire Response (http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse-adapt)

Extensions

This structure refers to these extensions:

• http://hl7.org/fhir/StructureDefinition/display

Slices

This structure defines the following Slices:

• The element Task.meta.tag is sliced based on the value of pattern:$this
• The element Task.input is sliced based on the value of pattern:type
• The element Task.output is sliced based on the value of pattern:type

Maturity: 2

Differential View

This structure is derived from Task

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed 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.
meta		0..1	Meta	Metadata about the resource
Slices for tag		0..*	Coding	Tags applied to this resource Slice: Unordered, Open by pattern:$this
tag:All Slices				Content/Rules for all slices
system		0..1	uri	Identity of the terminology system
code		1..1	code	Symbol in syntax defined by the system
tag:work-queue		0..*	Coding	Work Queue Tag Binding: CDex Work Queue Value Set (required)
identifier	S	0..*	Identifier	Task Instance Identifier
basedOn	S	0..*	Reference(Resource)	Authorization for data request
status	SC	1..1	code	draft | requested | received | accepted | + Binding: HRex Task Status ValueSet (required)
statusReason	SC	0..1	CodeableConcept	Reason for current status
text	S	1..1	string	Plain text representation of the concept
businessStatus	S	0..1	CodeableConcept	For example, 'waiting on internal review'
text	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 Fixed Value: order
code	SC	1..1	CodeableConcept	data-request-code | data-request-query | data-request-questionnaire Binding: CDex Data Request Task Code Value Set (required)
coding	S	1..*	Coding	Code defined by a terminology system
system	S	0..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code	S	1..1	code	Symbol in syntax defined by the system
focus		0..0
for	S	1..1	Reference(US Core Patient Profile)	Member (i.e., patient) being queried
identifier	S	0..1	Identifier	Patient Member ID
authoredOn	S	1..1	dateTime	Task Creation Date
requester	S	1..1	Reference(US Core Organization Profile | US Core Practitioner Profile)	Who is asking for data
identifier	S	0..1	Identifier	Data Consumer ID
owner	S	1..1	Reference(US Core Organization Profile | US Core Practitioner Profile)	Who is being asked for data
identifier	S	0..1	Identifier	Provider ID
reasonCode	S	0..1	CodeableConcept	Why task is needed
text	S	1..1	string	Plain text representation of the concept
reasonReference	S	0..1	Reference(Claim | HRex Coverage Profile)	Why task is needed
identifier	S	0..1	Identifier	Coverage or Claim ID
Slices for input	S	1..*	BackboneElement	Information used to perform task Slice: Unordered, Open by pattern:type
input:query	SC	0..1	BackboneElement	Requested query
type	S	1..1	CodeableConcept	Label for the input Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-query
value[x]	S	1..1	string	query value
input:code	SC	0..1	BackboneElement	Requested data code
type	S	1..1	CodeableConcept	Label for the input Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-code
value[x]	S	1..1	CodeableConcept	query value Binding: US Core DocumentReference Type (extensible)
input:questionnaire	CD	0..1	BackboneElement	Data Request questionnaire
type		1..1	CodeableConcept	Label for the input Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: questionnaire
value[x]		1..1	canonical(DTR SDC Questionnaire | DTR SDC Questionnaire for adaptive form)	URL
questionnaireDisplay		0..1	string	Display name for canonical reference URL: http://hl7.org/fhir/StructureDefinition/display
input:signature	S	0..1	BackboneElement	Signature flag
type	S	1..1	CodeableConcept	Label for the input Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: signature-flag
value[x]	S	1..1	boolean	Signature flag value
input:POU		0..1	BackboneElement	Purpose of use code
type		1..1	CodeableConcept	Label for the input Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: purpose-of-use
value[x]		1..1	CodeableConcept	Purpose of use value Binding: CDex Purpose of Use Value Set (extensible)
Slices for output	SC	0..*	BackboneElement	Information produced as part of task Slice: Unordered, Open by pattern:type
output:data	S	0..*	BackboneElement	Requested data
type	S	1..1	CodeableConcept	Label for output Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-value
value[x]	S	1..1	Reference()	data reference
output:response	CD	0..1	BackboneElement	Information produced as part of task
type		1..1	CodeableConcept	Label for output Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: questionnaire-response
value[x]		1..1	Reference(SDC Questionnaire Response | Adaptive Questionnaire Response)	Reference to the QuestionnaireResponse
Documentation for this format

Terminology Bindings (Differential)

Path	Conformance	ValueSet
Task.meta.tag:work-queue	required	CDexWorkQueueCodes
Task.status	required	HRexTaskStatus
Task.code	required	CDexDataRequestTaskCode
Task.input:code.value[x]	extensible	USCoreDocumentReferenceType
Task.input:POU.value[x]	extensible	CDexPOUCodes

Constraints

Id	Grade	Path(s)	Details	Requirements
cdex-7	error	Task	If code = "data-request-code", must have one "code" input. : Task.code.coding.code.where($this='data-request-code').exists() implies Task.input.type.coding.code.where($this='data-code').exists()
cdex-8	error	Task	If code = "data-request-questionnaire", must have one "questionnaire" input. : Task.code.coding.code.where($this='data-request-questionnaire').exists() implies Task.input.type.coding.code.where($this='questionnaire').exists()
cdex-9	error	Task	Must have exactly one input that is data-query or data-code or questionnaire : Task.input.type.coding.code.where($this='data-query' or $this='data-code' or $this='questionnaire').count()=1
cdex-11	warning	Task	If code = "data-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. : (Task.code.coding.code.where($this='data-request-questionnaire').exists() and Task.status.where($this='completed').exists()) implies Task.output.type.coding.code.where($this='questionnaire-response').exists()
cdex-12	error	Task	If code = "data-request-query", must have one "query" input. : Task.code.coding.code.where($this='data-request-query').exists() implies Task.input.type.coding.code.where($this='data-query').exists()
tdr-2	error	Task	Task statusReason SHALL be populated if status is 'rejected' or 'failed' : (status = 'rejected' or status = 'failed') implies statusReason.exists()
tdr-3	error	Task	Task output SHALL be populated if status is 'completed' : (status = 'completed') implies output.exists()

Key Elements View

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed 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.
meta	Σ	0..1	Meta	Metadata about the resource
Slices for tag	Σ	0..*	Coding	Tags applied to this resource Slice: Unordered, Open by pattern:$this Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
tag:All Slices				Content/Rules for all slices
system	Σ	0..1	uri	Identity of the terminology system
code	Σ	1..1	code	Symbol in syntax defined by the system
tag:work-queue	Σ	0..*	Coding	Work Queue Tag Binding: CDex Work Queue Value Set (required)
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	S	0..*	Identifier	Task Instance Identifier
basedOn	SΣ	0..*	Reference(Resource)	Authorization for data request
status	?!SΣC	1..1	code	draft | requested | received | accepted | + Binding: HRex Task Status ValueSet (required)
statusReason	SΣC	0..1	CodeableConcept	Reason for current status Binding: (unbound) (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow.
text	SΣ	1..1	string	Plain text representation of the concept
businessStatus	SΣ	0..1	CodeableConcept	For example, 'waiting on internal review' Binding: (unbound) (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.
text	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: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: order
code	SΣC	1..1	CodeableConcept	data-request-code | data-request-query | data-request-questionnaire Binding: CDex Data Request Task Code Value Set (required)
coding	SΣ	1..*	Coding	Code defined by a terminology system
system	SΣ	0..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code	SΣ	1..1	code	Symbol in syntax defined by the system
for	SΣ	1..1	Reference(US Core Patient Profile)	Member (i.e., patient) being queried
identifier	SΣ	0..1	Identifier	Patient Member ID
authoredOn	SC	1..1	dateTime	Task Creation Date
requester	SΣ	1..1	Reference(US Core Organization Profile | US Core Practitioner Profile)	Who is asking for data
identifier	SΣ	0..1	Identifier	Data Consumer ID
owner	SΣ	1..1	Reference(US Core Organization Profile | US Core Practitioner Profile)	Who is being asked for data
identifier	SΣ	0..1	Identifier	Provider ID
reasonCode	S	0..1	CodeableConcept	Why task is needed Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.
text	SΣ	1..1	string	Plain text representation of the concept
reasonReference	S	0..1	Reference(Claim | HRex Coverage Profile)	Why task is needed
identifier	SΣ	0..1	Identifier	Coverage or Claim ID
Slices for input	S	1..*	BackboneElement	Information used to perform task Slice: Unordered, Open by pattern:type
input:All Slices				Content/Rules for all slices
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding: (unbound) (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		Content to use in performing the task
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
input:query	SC	0..1	BackboneElement	Requested query
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-query
value[x]	S	1..1	string	query value
input:code	SC	0..1	BackboneElement	Requested data code
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-code
value[x]	S	1..1	CodeableConcept	query value Binding: US Core DocumentReference Type (extensible)
input:questionnaire	C	0..1	BackboneElement	Data Request questionnaire
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: questionnaire
value[x]		1..1	canonical(DTR SDC Questionnaire | DTR SDC Questionnaire for adaptive form)	URL
questionnaireDisplay		0..1	string	Display name for canonical reference URL: http://hl7.org/fhir/StructureDefinition/display
input:signature	S	0..1	BackboneElement	Signature flag
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: signature-flag
value[x]	S	1..1	boolean	Signature flag value
input:POU		0..1	BackboneElement	Purpose of use code
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: purpose-of-use
value[x]		1..1	CodeableConcept	Purpose of use value Binding: CDex Purpose of Use Value Set (extensible)
Slices for output	SC	0..*	BackboneElement	Information produced as part of task Slice: Unordered, Open by pattern:type
output:All Slices				Content/Rules for all slices
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for output Binding: (unbound) (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		Result of output
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
output:data	S	0..*	BackboneElement	Requested data
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for output Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-value
value[x]	S	1..1	Reference()	data reference
output:response	C	0..1	BackboneElement	Information produced as part of task
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for output Binding: (unbound) (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. Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: questionnaire-response
value[x]		1..1	Reference(SDC Questionnaire Response | Adaptive Questionnaire Response)	Reference to the QuestionnaireResponse
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code
Task.meta.tag	example	CommonTags
Task.meta.tag:work-queue	required	CDexWorkQueueCodes
Task.status	required	HRexTaskStatus
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	Fixed Value: order
Task.code	required	CDexDataRequestTaskCode
Task.reasonCode	example
Task.input.type	example
Task.input:query.type	example	Pattern: data-query
Task.input:code.type	example	Pattern: data-code
Task.input:code.value[x]	extensible	USCoreDocumentReferenceType
Task.input:questionnaire.type	example	Pattern: questionnaire
Task.input:signature.type	example	Pattern: signature-flag
Task.input:POU.type	example	Pattern: purpose-of-use
Task.input:POU.value[x]	extensible	CDexPOUCodes
Task.output.type	example
Task.output:data.type	example	Pattern: data-value
Task.output:response.type	example	Pattern: questionnaire-response

Constraints

Id	Grade	Path(s)	Details	Requirements
cdex-7	error	Task	If code = "data-request-code", must have one "code" input. : Task.code.coding.code.where($this='data-request-code').exists() implies Task.input.type.coding.code.where($this='data-code').exists()
cdex-8	error	Task	If code = "data-request-questionnaire", must have one "questionnaire" input. : Task.code.coding.code.where($this='data-request-questionnaire').exists() implies Task.input.type.coding.code.where($this='questionnaire').exists()
cdex-9	error	Task	Must have exactly one input that is data-query or data-code or questionnaire : Task.input.type.coding.code.where($this='data-query' or $this='data-code' or $this='questionnaire').count()=1
cdex-11	warning	Task	If code = "data-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. : (Task.code.coding.code.where($this='data-request-questionnaire').exists() and Task.status.where($this='completed').exists()) implies Task.output.type.coding.code.where($this='questionnaire-response').exists()
cdex-12	error	Task	If code = "data-request-query", must have one "query" input. : Task.code.coding.code.where($this='data-request-query').exists() implies Task.input.type.coding.code.where($this='data-query').exists()
tdr-2	error	Task	Task statusReason SHALL be populated if status is 'rejected' or 'failed' : (status = 'rejected' or status = 'failed') implies statusReason.exists()
tdr-3	error	Task	Task output SHALL be populated if status is 'completed' : (status = 'completed') implies output.exists()

Snapshot View

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed 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
meta	Σ	0..1	Meta	Metadata about the resource
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
versionId	Σ	0..1	id	Version specific identifier
lastUpdated	Σ	0..1	instant	When the resource version last changed
source	Σ	0..1	uri	Identifies where the resource comes from
profile	Σ	0..*	canonical(StructureDefinition)	Profiles this resource claims to conform to
security	Σ	0..*	Coding	Security Labels applied to this resource Binding: All Security Labels (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: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
tag:All Slices				Content/Rules for all slices
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
system	Σ	0..1	uri	Identity of the terminology system
version	Σ	0..1	string	Version of the system - if relevant
code	Σ	1..1	code	Symbol in syntax defined by the system
display	Σ	0..1	string	Representation defined by the system
userSelected	Σ	0..1	boolean	If this coding was chosen directly by the user
tag:work-queue	Σ	0..*	Coding	Work Queue Tag Binding: CDex Work Queue Value Set (required)
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	S	0..*	Identifier	Task Instance Identifier
instantiatesCanonical	Σ	0..1	canonical(ActivityDefinition)	Formal definition of task
instantiatesUri	Σ	0..1	uri	Formal definition of task
basedOn	SΣ	0..*	Reference(Resource)	Authorization for data request
groupIdentifier	Σ	0..1	Identifier	Requisition or grouper id
partOf	Σ	0..*	Reference(Task)	Composite task
status	?!SΣC	1..1	code	draft | requested | received | accepted | + Binding: HRex Task Status ValueSet (required)
statusReason	SΣC	0..1	CodeableConcept	Reason for current status Binding: (unbound) (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
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system
text	SΣ	1..1	string	Plain text representation of the concept
businessStatus	SΣ	0..1	CodeableConcept	For example, 'waiting on internal review' Binding: (unbound) (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
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system
text	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: TaskIntent (required): Distinguishes whether the task is a proposal, plan or full order. Fixed Value: order
priority		0..1	code	routine | urgent | asap | stat Binding: RequestPriority (required): The task's priority.
code	SΣC	1..1	CodeableConcept	data-request-code | data-request-query | data-request-questionnaire Binding: CDex Data Request Task Code Value Set (required)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	SΣ	1..*	Coding	Code defined by a terminology system
id		0..1	string	Unique id for inter-element referencing
extension		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
version	Σ	0..1	string	Version of the system - if relevant
code	SΣ	1..1	code	Symbol in syntax defined by the system
display	Σ	0..1	string	Representation defined by the system
userSelected	Σ	0..1	boolean	If this coding was chosen directly by the user
text	Σ	0..1	string	Plain text representation of the concept
description	Σ	0..1	string	Human-readable explanation of task
for	SΣ	1..1	Reference(US Core Patient Profile)	Member (i.e., patient) being queried
id		0..1	string	Unique id for inter-element referencing
extension		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
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ResourceType (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	SΣ	0..1	Identifier	Patient Member ID
display	Σ	0..1	string	Text alternative for the resource
encounter	Σ	0..1	Reference(Encounter)	Healthcare event during which this task originated
executionPeriod	Σ	0..1	Period	Start and end time of execution
authoredOn	SC	1..1	dateTime	Task Creation Date
lastModified	Σ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
id		0..1	string	Unique id for inter-element referencing
extension		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
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ResourceType (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	SΣ	0..1	Identifier	Data Consumer ID
display	Σ	0..1	string	Text alternative for the resource
performerType		0..*	CodeableConcept	Requested performer Binding: ProcedurePerformerRoleCodes (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
id		0..1	string	Unique id for inter-element referencing
extension		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
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ResourceType (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	SΣ	0..1	Identifier	Provider ID
display	Σ	0..1	string	Text alternative for the resource
location	Σ	0..1	Reference(Location)	Where task occurs
reasonCode	S	0..1	CodeableConcept	Why task is needed Binding: (unbound) (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
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system
text	SΣ	1..1	string	Plain text representation of the concept
reasonReference	S	0..1	Reference(Claim | HRex Coverage Profile)	Why task is needed
id		0..1	string	Unique id for inter-element referencing
extension		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
type	Σ	0..1	uri	Type the reference refers to (e.g. "Patient") Binding: ResourceType (extensible): Aa resource (or, for logical models, the URI of the logical model).
identifier	SΣ	0..1	Identifier	Coverage or Claim ID
display	Σ	0..1	string	Text alternative for the resource
insurance		0..*	Reference(Coverage | ClaimResponse)	Associated insurance coverage
note		0..*	Annotation	Comments made about the task
relevantHistory		0..*	Reference(Provenance)	Key events in history of the Task
restriction		0..1	BackboneElement	Constraints on fulfillment tasks
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
repetitions		0..1	positiveInt	How many times to repeat
period		0..1	Period	When fulfillment sought
recipient		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
input:All Slices				Content/Rules for all slices
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding: (unbound) (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		Content to use in performing the task
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
input:query	SC	0..1	BackboneElement	Requested query
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-query
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]	S	1..1	string	query value
input:code	SC	0..1	BackboneElement	Requested data code
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-code
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]	S	1..1	CodeableConcept	query value Binding: US Core DocumentReference Type (extensible)
input:questionnaire	C	0..1	BackboneElement	Data Request questionnaire
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: questionnaire
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]		1..1	canonical(DTR SDC Questionnaire | DTR SDC Questionnaire for adaptive form)	URL
id		0..1	string	xml:id (or equivalent in JSON)
Slices for extension		0..*	Extension	Extension Slice: Unordered, Open by value:url
questionnaireDisplay		0..1	string	Display name for canonical reference URL: http://hl7.org/fhir/StructureDefinition/display
value		0..1	string	Primitive value for canonical
input:signature	S	0..1	BackboneElement	Signature flag
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..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
code		1..1	code	Symbol in syntax defined by the system Fixed Value: signature-flag
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]	S	1..1	boolean	Signature flag value
input:POU		0..1	BackboneElement	Purpose of use code
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for the input Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..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
code		1..1	code	Symbol in syntax defined by the system Fixed Value: purpose-of-use
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]		1..1	CodeableConcept	Purpose of use value Binding: CDex Purpose of Use Value Set (extensible)
Slices for output	SC	0..*	BackboneElement	Information produced as part of task Slice: Unordered, Open by pattern:type
output:All Slices				Content/Rules for all slices
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for output Binding: (unbound) (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		Result of output
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
output:data	S	0..*	BackboneElement	Requested data
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type	S	1..1	CodeableConcept	Label for output Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-value
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]	S	1..1	Reference()	data reference
output:response	C	0..1	BackboneElement	Information produced as part of task
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
type		1..1	CodeableConcept	Label for output Binding: (unbound) (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. Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
version		0..1	string	Version of the system - if relevant
code		1..1	code	Symbol in syntax defined by the system Fixed Value: questionnaire-response
display		0..1	string	Representation defined by the system
userSelected		0..1	boolean	If this coding was chosen directly by the user
text		0..1	string	Plain text representation of the concept
value[x]		1..1	Reference(SDC Questionnaire Response | Adaptive Questionnaire Response)	Reference to the QuestionnaireResponse
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code
Task.meta.security	extensible	All Security Labels
Task.meta.tag	example	CommonTags
Task.meta.tag:work-queue	required	CDexWorkQueueCodes
Task.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding
Task.status	required	HRexTaskStatus
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	Fixed Value: order
Task.priority	required	RequestPriority
Task.code	required	CDexDataRequestTaskCode
Task.for.type	extensible	ResourceType
Task.requester.type	extensible	ResourceType
Task.performerType	preferred	ProcedurePerformerRoleCodes
Task.owner.type	extensible	ResourceType
Task.reasonCode	example
Task.reasonReference.type	extensible	ResourceType
Task.input.type	example
Task.input:query.type	example	Pattern: data-query
Task.input:code.type	example	Pattern: data-code
Task.input:code.value[x]	extensible	USCoreDocumentReferenceType
Task.input:questionnaire.type	example	Pattern: questionnaire
Task.input:signature.type	example	Pattern: signature-flag
Task.input:POU.type	example	Pattern: purpose-of-use
Task.input:POU.value[x]	extensible	CDexPOUCodes
Task.output.type	example
Task.output:data.type	example	Pattern: data-value
Task.output:response.type	example	Pattern: questionnaire-response

This structure is derived from Task

Summary

Mandatory: 8 elements (8 nested mandatory elements)
Must-Support: 37 elements
Fixed Value: 2 elements
Prohibited: 1 element

Structures

This structure refers to these other structures:

• US Core Patient Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient)
• US Core Organization Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization)
• US Core Practitioner Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner)
• HRex Coverage Profile (http://hl7.org/fhir/us/davinci-hrex/StructureDefinition/hrex-coverage)
• DTR SDC Questionnaire (http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-sdc-questionnaire)
• DTR SDC Questionnaire for adaptive form (http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-sdc-questionnaire-adapt)
• SDC Questionnaire Response (http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse)
• Adaptive Questionnaire Response (http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse-adapt)

Extensions

This structure refers to these extensions:

• http://hl7.org/fhir/StructureDefinition/display

Slices

This structure defines the following Slices:

• The element Task.meta.tag is sliced based on the value of pattern:$this
• The element Task.input is sliced based on the value of pattern:type
• The element Task.output is sliced based on the value of pattern:type

Maturity: 2