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. For a full list of available versions, see the Directory of published versions

• Content
• Detailed Descriptions
• Examples
• XML
• JSON

Resource Profile: CDex Task Attachment Request Profile

Payers use the Task based profile to request additional documentation (“attachments”) for claims or prior authorizations. It constrains the Task resource to minimal necessary data elements needed to request attachments and respond in a way that is compatible with existing X12 277 RFAI and 278 response transactions to allow for association and requests for (typically PDF and CCDA) documents using LOINC as the standard. It also supports requests for more detailed missing data using Questionnaire, CQL, and QuestionnaireResponse, as supported by Da Vinci DTR.

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

• A contained Patient Resource defined by the CDex Patient Demographics Profile and communicating additional patient demographic data elements.
• A contained PractitionerRole Resource defined by the CDex PractitionerRole Profile to communicate the provider ID as either a unique organization/location identifier (e.g., Type 2 NPI) or unique provider identifier (e.g., Type 1 NPI) or both.
• A Task.identifier element representing the payers tracking identifier (referred to as the “re-association tracking control numbers”)
• A Task.status with a required binding to HRex Task Status ValueSet (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 “attachment-request-code” or “attachment-request-questionnaire” communicating that the Payer is requesting attachments for a claim or prior authorization using a code or data request questionnaire.
  • If the code is “attachment-request-code”, the provider system returns attachment(s) identified by the LOINC attachment code(s) in the “code” input parameter.
  • If the code is “attachment-request-questionnaire”, the provider system uses Documentation Templates and Rules (DTR) to complete the Questionnaire referenced in the “questionnaire” input parameter.
  • When either code is present, the provider system uses the $submit-attachment operation to return the information to the endpoint provided in “payer-url” input parameter.
• A Task.requester.identifier element representing the Payer ID
• A Task.owner.reference element fixed to “#practionerrole” - a reference the contained PractitionerRole Resource that represents the Provider ID.
• A Task.for.reference element fixed to “#patient” - a reference the contained Patient Resource that represents basic Patient demographic data.
• A Task.reasonCode to communicate whether the attachments are for a Claim or Prior Authorization
• A Task.reasonReference.reference referencing the Claim or Prior Authorization ID (business Identifier)
• A “payer-url” Task.input element representing the Payer endpoint URL to communicate to the provider to submit the attachments using the $submit-attachment operation

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

• A Task.Restriction.period element representing the due date for submitting the attachments
• A Task.statusReason.text to communicate the reason for the status (for example, if the Task is rejected or failed)
• A “code” Task.input element to communicate to the provider what attachments are needed using LOINC attachment codes.*
• A “code” or “questionnaire” Task.input element extension representing a claim or prior authorization line item numbers associated with the attachment or questionnaire.
• A “signature” Task.input element representing a flag to indicate whether the requested data requires a signature. For more information about requiring and requesting signatures, refer to the Signatures section.
• A “service-date” Task.input element representing the date of service or starting date of the service for the claim or prior authorization. It SHALL be present if the attachment is for a claim.

It defines the following elements to be optional:

• A “questionnaire” Task.input element to communicate to the provider a URL of a data request FHIR Questionnaire 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 “POU” Task.input element representing the purpose of use (POU) for the requested data using an extensible CDex Purpose of Use Value Set. For more information about sending purpose POU codes, refer to the Purpose of Use section.
• A “multiple-submits” Task.input element representing a flag to indicate whether the requested data can be sent in multiple submissions
• A “data-value” Task.output element referring to FHIR resource(s) representing the result(s) of the data request code.
• A “response” Task.output element which is a local reference to the FHIR QuestionnaireResponse resulting from the data request Questionnaire. The QuestionnaireResponse conforms to the SDC Questionnaire Response Profile or the SDC Adaptive Questionnaire Response Profile.

* Either a “code” or a “questionnaire” Task.input element is required

Usage:

• Examples for this Resource Profile: Task/cdex-task-example19, Task/cdex-task-example20, Task/cdex-task-example22, Task/cdex-task-example23... Show 4 more, Task/cdex-task-example24, Task/cdex-task-example25, Task/cdex-task-example28 and Task/cdex-task-example29

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-1: The "service-date" input SHALL be present if the attachment is for a claim. cdex-4: If code = "attachment-request-code", must have one or more "code" inputs. cdex-5: If code = "attachment-request-questionnaire", must have one "questionnaire" input. cdex-6: Must only have "code" inputs or one "questionnaire" input not both. cdex-10: If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed'
Slices for contained	S	1..*	Resource	Contained, inline Resources Slice: Unordered, Open by type:$this
contained:practitionerrole	S	1..1	CDexPractitionerRole	Contained PractitionerRole resource
contained:patient	S	1..1	CDexPatientDemographics	Contained Patient resource
Slices for identifier	S	1..*	Identifier	Task Instance Identifier Slice: Unordered, Open by pattern:$this
identifier:tracking-id	S	1..1	Identifier	Re-association tracking control number Required Pattern: At least the following
type		1..1	CodeableConcept	Description of identifier Fixed Value: (complex)
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: tracking-id
system	S	0..1	uri	The namespace for the identifier value
value	S	1..1	string	The value that is unique
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
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	attachment-request-code | attachment-request-questionnaire Binding: CDex Attachment 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(CDex Patient Demographics Profile) {c}	Contained Patient.
reference	S	1..1	string	Contained resource reference Fixed Value: #patient
requester	S	1..1	Reference(US Core Organization Profile)	Payer asking for attachments
identifier	S	1..1	Identifier	Payer ID
owner	S	1..1	Reference(CDex PractitionerRole Profile) {c}	Provider who submitted claim or preauthorization
reference	S	1..1	string	Contained resource reference Fixed Value: #practitionerrole
reasonCode	S	1..1	CodeableConcept	Why task is needed
Slices for coding	SC	1..*	Coding	Code defined by a terminology system Slice: Unordered, Open by value:$this
coding:use	S	1..*	Coding	Code defined by a terminology system Binding: CDex Claim Use Value Set (required)
system	S	0..1	uri	Identity of the terminology system
code	S	1..1	code	claim | preauthorization
text	S	0..1	string	claim | preauthorization Binding: CDex Claim Use Value Set (required)
reasonReference	S	1..1	Reference(Resource)	Why task is needed
identifier	S	1..1	Identifier	Claim or Prior Authorization ID
restriction	S	0..1	BackboneElement	Constraints on fulfillment tasks
period	S	0..1	Period	Attachments due date
Slices for input	S	2..*	BackboneElement	Information used to perform task Slice: Unordered, Open by pattern:type
input:code	SC	0..*	BackboneElement	Attachment Codes Binding: LOINC valid-hl7-attachment-requests (extensible)
extension	S	0..*	Extension	Extension
url	S	1..1	uri	"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
value[x]	S	1..1	positiveInt	Value of extension
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	LOINC attachment code value
input:questionnaire	CD	0..1	BackboneElement	Data Request questionnaire
extension	S	0..*	Extension	Extension
url	S	1..1	uri	"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
value[x]	S	1..1	positiveInt	Value of extension
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:payer-url	S	1..1	BackboneElement	Payer Url
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: payer-url
value[x]	S	1..1	url	Payer url value
input:service-date	SC	0..1	BackboneElement	Service Date
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: service-date
value[x]	SC	1..1	date	Service Date value cdex-2: Date must be to day.
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)
input:multiple-submits		0..1	BackboneElement	Multiple submits flag
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: multiple-submits-flag
value[x]		1..1	boolean	Multiple submits flag value
Slices for output		0..*	BackboneElement	Information produced as part of task Slice: Unordered, Open by pattern:type
output:data		0..*	BackboneElement	Requested data
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/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-value
value[x]		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.status	required	HRexTaskStatus
Task.code	required	CDexAttachmentTaskCode
Task.reasonCode.coding:use	required	CDexClaimUseCodes
Task.reasonCode.text	required	CDexClaimUseCodes
Task.input:code	extensible	LOINC valid-hl7-attachment-requests
Task.input:POU.value[x]	extensible	CDexPOUCodes

Constraints

Id	Grade	Path(s)	Details	Requirements
cdex-1	error	Task	The "service-date" input SHALL be present if the attachment is for a claim. : Task.reasonCode.coding.code.where($this='claim').exists() implies Task.input.type.coding.code.where($this='service-date').exists()
cdex-2	error	Task.input:service-date.value[x]	Date must be to day. : $this.toString().length() = 10
cdex-4	error	Task	If code = "attachment-request-code", must have one or more "code" inputs. : Task.code.coding.code.where($this='attachment-request-code').exists() implies Task.input.type.coding.code.where($this='data-code').exists()
cdex-5	error	Task	If code = "attachment-request-questionnaire", must have one "questionnaire" input. : Task.code.coding.code.where($this='attachment-request-questionnaire').exists() implies Task.input.type.coding.code.where($this='questionnaire').exists()
cdex-6	error	Task	Must only have "code" inputs or one "questionnaire" input not both. : Task.input.type.coding.code.where($this='data-code').exists() implies Task.input.type.coding.code.where($this='questionnaire').empty()
cdex-10	warning	Task	If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. : (Task.code.coding.code.where($this='attachment-request-questionnaire').exists() and Task.status.where($this='completed').exists()) implies Task.output.type.coding.code.where($this='questionnaire-response').exists()
tdr-2	error	Task	Task statusReason SHALL be populated if status is 'rejected' or 'failed' : (status = 'rejected' or status = 'failed') implies statusReason.exists()

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed cdex-1: The "service-date" input SHALL be present if the attachment is for a claim. cdex-4: If code = "attachment-request-code", must have one or more "code" inputs. cdex-5: If code = "attachment-request-questionnaire", must have one "questionnaire" input. cdex-6: Must only have "code" inputs or one "questionnaire" input not both. cdex-10: If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed'
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
Slices for contained	S	1..*	Resource	Contained, inline Resources Slice: Unordered, Open by type:$this
contained:practitionerrole	SC	1..1	CDexPractitionerRole	Contained PractitionerRole resource
contained:patient	S	1..1	CDexPatientDemographics	Contained Patient resource
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
Slices for identifier	S	1..*	Identifier	Task Instance Identifier Slice: Unordered, Open by pattern:$this
identifier:tracking-id	S	1..1	Identifier	Re-association tracking control number Required Pattern: At least the following
type		1..1	CodeableConcept	Description of identifier Fixed Value: (complex)
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: tracking-id
use	?!Σ	0..1	code	usual | official | temp | secondary | old (If known) Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
system	SΣ	0..1	uri	The namespace for the identifier value Example General: http://www.acme.com/identifiers/patient
value	SΣ	1..1	string	The value that is unique Example General: 123456
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
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	attachment-request-code | attachment-request-questionnaire Binding: CDex Attachment 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(CDex Patient Demographics Profile) {c}	Contained Patient.
reference	SΣC	1..1	string	Contained resource reference Fixed Value: #patient
requester	SΣ	1..1	Reference(US Core Organization Profile)	Payer asking for attachments
identifier	SΣ	1..1	Identifier	Payer ID
owner	SΣ	1..1	Reference(CDex PractitionerRole Profile) {c}	Provider who submitted claim or preauthorization
reference	SΣC	1..1	string	Contained resource reference Fixed Value: #practitionerrole
reasonCode	S	1..1	CodeableConcept	Why task is needed Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.
Slices for coding	SΣC	1..*	Coding	Code defined by a terminology system Slice: Unordered, Open by value:$this
coding:use	SΣ	1..*	Coding	Code defined by a terminology system Binding: CDex Claim Use Value Set (required)
system	SΣ	0..1	uri	Identity of the terminology system
code	SΣ	1..1	code	claim | preauthorization
text	SΣ	0..1	string	claim | preauthorization Binding: CDex Claim Use Value Set (required)
reasonReference	S	1..1	Reference(Resource)	Why task is needed
identifier	SΣ	1..1	Identifier	Claim or Prior Authorization ID
restriction	S	0..1	BackboneElement	Constraints on fulfillment tasks
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
period	S	0..1	Period	Attachments due date
Slices for input	S	2..*	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:code	SC	0..*	BackboneElement	Attachment Codes
extension	S	0..*	Extension	Extension
url	S	1..1	uri	"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
value[x]	S	1..1	positiveInt	Value of extension
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	LOINC attachment code value
input:questionnaire	C	0..1	BackboneElement	Data Request questionnaire
extension	S	0..*	Extension	Extension
url	S	1..1	uri	"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
value[x]	S	1..1	positiveInt	Value of extension
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:payer-url	S	1..1	BackboneElement	Payer Url
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: payer-url
value[x]	S	1..1	url	Payer url value
input:service-date	SC	0..1	BackboneElement	Service Date
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: service-date
value[x]	SC	1..1	date	Service Date value cdex-2: Date must be to day.
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)
input:multiple-submits		0..1	BackboneElement	Multiple submits flag
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: multiple-submits-flag
value[x]		1..1	boolean	Multiple submits flag value
Slices for output		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		0..*	BackboneElement	Requested data
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/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-value
value[x]		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.identifier:tracking-id.use	required	IdentifierUse
Task.status	required	HRexTaskStatus
Task.statusReason	example
Task.intent	required	Fixed Value: order
Task.code	required	CDexAttachmentTaskCode
Task.reasonCode	example
Task.reasonCode.coding:use	required	CDexClaimUseCodes
Task.reasonCode.text	required	CDexClaimUseCodes
Task.input.type	example
Task.input:code.type	example	Pattern: data-code
Task.input:questionnaire.type	example	Pattern: questionnaire
Task.input:payer-url.type	example	Pattern: payer-url
Task.input:service-date.type	example	Pattern: service-date
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.input:multiple-submits.type	example	Pattern: multiple-submits-flag
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-1	error	Task	The "service-date" input SHALL be present if the attachment is for a claim. : Task.reasonCode.coding.code.where($this='claim').exists() implies Task.input.type.coding.code.where($this='service-date').exists()
cdex-2	error	Task.input:service-date.value[x]	Date must be to day. : $this.toString().length() = 10
cdex-4	error	Task	If code = "attachment-request-code", must have one or more "code" inputs. : Task.code.coding.code.where($this='attachment-request-code').exists() implies Task.input.type.coding.code.where($this='data-code').exists()
cdex-5	error	Task	If code = "attachment-request-questionnaire", must have one "questionnaire" input. : Task.code.coding.code.where($this='attachment-request-questionnaire').exists() implies Task.input.type.coding.code.where($this='questionnaire').exists()
cdex-6	error	Task	Must only have "code" inputs or one "questionnaire" input not both. : Task.input.type.coding.code.where($this='data-code').exists() implies Task.input.type.coding.code.where($this='questionnaire').empty()
cdex-10	warning	Task	If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. : (Task.code.coding.code.where($this='attachment-request-questionnaire').exists() and Task.status.where($this='completed').exists()) implies Task.output.type.coding.code.where($this='questionnaire-response').exists()
tdr-2	error	Task	Task statusReason SHALL be populated if status is 'rejected' or 'failed' : (status = 'rejected' or status = 'failed') implies statusReason.exists()

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed cdex-1: The "service-date" input SHALL be present if the attachment is for a claim. cdex-4: If code = "attachment-request-code", must have one or more "code" inputs. cdex-5: If code = "attachment-request-questionnaire", must have one "questionnaire" input. cdex-6: Must only have "code" inputs or one "questionnaire" input not both. cdex-10: If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed'
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
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
Slices for contained	S	1..*	Resource	Contained, inline Resources Slice: Unordered, Open by type:$this
contained:practitionerrole	SC	1..1	CDexPractitionerRole	Contained PractitionerRole resource
contained:patient	S	1..1	CDexPatientDemographics	Contained Patient resource
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
Slices for identifier	S	1..*	Identifier	Task Instance Identifier Slice: Unordered, Open by pattern:$this
identifier:tracking-id	S	1..1	Identifier	Re-association tracking control number Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
use		0..1	code	usual | official | temp | secondary | old (If known)
type		1..1	CodeableConcept	Description of identifier Fixed Value: (complex)
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: tracking-id
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
system		0..1	uri	The namespace for the identifier value
value		0..1	string	The value that is unique
period		0..1	Period	Time period when id is/was valid for use
assigner		0..1	Reference(Organization)	Organization that issued id (may be just text)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
use	?!Σ	0..1	code	usual | official | temp | secondary | old (If known) Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
type	Σ	0..1	CodeableConcept	Description of identifier Binding: Identifier Type Codes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
system	SΣ	0..1	uri	The namespace for the identifier value Example General: http://www.acme.com/identifiers/patient
value	SΣ	1..1	string	The value that is unique Example General: 123456
period	Σ	0..1	Period	Time period when id is/was valid for use
assigner	Σ	0..1	Reference(Organization)	Organization that issued id (may be just text)
instantiatesCanonical	Σ	0..1	canonical(ActivityDefinition)	Formal definition of task
instantiatesUri	Σ	0..1	uri	Formal definition of task
basedOn	Σ	0..*	Reference(Resource)	Request fulfilled by this task
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	Σ	0..1	CodeableConcept	E.g. "Specimen collected", "IV prepped" Binding: (unbound) (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.
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	attachment-request-code | attachment-request-questionnaire Binding: CDex Attachment 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
focus	Σ	0..1	Reference(Resource)	What task is acting on
for	SΣ	1..1	Reference(CDex Patient Demographics Profile) {c}	Contained Patient.
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	SΣC	1..1	string	Contained resource reference Fixed Value: #patient
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	Σ	0..1	Identifier	Logical reference, when literal reference is not known
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	C	0..1	dateTime	Task Creation Date
lastModified	ΣC	0..1	dateTime	Task Last Modified Date
requester	SΣ	1..1	Reference(US Core Organization Profile)	Payer asking for attachments
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Σ	1..1	Identifier	Payer 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(CDex PractitionerRole Profile) {c}	Provider who submitted claim or preauthorization
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	SΣC	1..1	string	Contained resource reference Fixed Value: #practitionerrole
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	Σ	0..1	Identifier	Logical reference, when literal reference is not known
display	Σ	0..1	string	Text alternative for the resource
location	Σ	0..1	Reference(Location)	Where task occurs
reasonCode	S	1..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
Slices for coding	SΣC	1..*	Coding	Code defined by a terminology system Slice: Unordered, Open by value:$this
coding:use	SΣ	1..*	Coding	Code defined by a terminology system Binding: CDex Claim Use 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
system	SΣ	0..1	uri	Identity of the terminology system
version	Σ	0..1	string	Version of the system - if relevant
code	SΣ	1..1	code	claim | preauthorization
display	Σ	0..1	string	Representation defined by the system
userSelected	Σ	0..1	boolean	If this coding was chosen directly by the user
text	SΣ	0..1	string	claim | preauthorization Binding: CDex Claim Use Value Set (required)
reasonReference	S	1..1	Reference(Resource)	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Σ	1..1	Identifier	Claim or Prior Authorization 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	S	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	S	0..1	Period	Attachments due date
recipient		0..*	Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization)	For whom is fulfillment sought?
Slices for input	S	2..*	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:code	SC	0..*	BackboneElement	Attachment Codes
id		0..1	string	Unique id for inter-element referencing
extension	S	0..*	Extension	Extension
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
url	S	1..1	uri	"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
value[x]	S	1..1	positiveInt	Value of extension
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	LOINC attachment code value
input:questionnaire	C	0..1	BackboneElement	Data Request questionnaire
id		0..1	string	Unique id for inter-element referencing
extension	S	0..*	Extension	Extension
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
url	S	1..1	uri	"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
value[x]	S	1..1	positiveInt	Value of extension
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:payer-url	S	1..1	BackboneElement	Payer Url
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: payer-url
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	url	Payer url value
input:service-date	SC	0..1	BackboneElement	Service Date
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: service-date
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]	SC	1..1	date	Service Date value cdex-2: Date must be to day.
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)
input:multiple-submits		0..1	BackboneElement	Multiple submits 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		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: multiple-submits-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]		1..1	boolean	Multiple submits flag value
Slices for output		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		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		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]		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.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding
Task.identifier:tracking-id.use	required	IdentifierUse
Task.identifier:tracking-id.type	extensible	Identifier Type Codes
Task.status	required	HRexTaskStatus
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	Fixed Value: order
Task.priority	required	RequestPriority
Task.code	required	CDexAttachmentTaskCode
Task.for.type	extensible	ResourceType
Task.requester.type	extensible	ResourceType
Task.performerType	preferred	ProcedurePerformerRoleCodes
Task.owner.type	extensible	ResourceType
Task.reasonCode	example
Task.reasonCode.coding:use	required	CDexClaimUseCodes
Task.reasonCode.text	required	CDexClaimUseCodes
Task.reasonReference.type	extensible	ResourceType
Task.input.type	example
Task.input:code.type	example	Pattern: data-code
Task.input:questionnaire.type	example	Pattern: questionnaire
Task.input:payer-url.type	example	Pattern: payer-url
Task.input:service-date.type	example	Pattern: service-date
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.input:multiple-submits.type	example	Pattern: multiple-submits-flag
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-2	error	Task.input:service-date.value[x]	Date must be to day. : $this.toString().length() = 10

This structure is derived from Task

Summary

Mandatory: 22 elements (6 nested mandatory elements)
Must-Support: 50 elements
Fixed Value: 6 elements

Structures

This structure refers to these other structures:

• CDex PractitionerRole Profile (http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-practitionerrole)
• CDex Patient Demographics Profile (http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-patient-demographics)
• US Core Organization Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization)
• 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.contained is sliced based on the value of type:$this
• The element Task.identifier is sliced based on the value of pattern:$this
• The element Task.reasonCode.coding is sliced based on the value of value:$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-1: The "service-date" input SHALL be present if the attachment is for a claim. cdex-4: If code = "attachment-request-code", must have one or more "code" inputs. cdex-5: If code = "attachment-request-questionnaire", must have one "questionnaire" input. cdex-6: Must only have "code" inputs or one "questionnaire" input not both. cdex-10: If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed'
Slices for contained	S	1..*	Resource	Contained, inline Resources Slice: Unordered, Open by type:$this
contained:practitionerrole	S	1..1	CDexPractitionerRole	Contained PractitionerRole resource
contained:patient	S	1..1	CDexPatientDemographics	Contained Patient resource
Slices for identifier	S	1..*	Identifier	Task Instance Identifier Slice: Unordered, Open by pattern:$this
identifier:tracking-id	S	1..1	Identifier	Re-association tracking control number Required Pattern: At least the following
type		1..1	CodeableConcept	Description of identifier Fixed Value: (complex)
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: tracking-id
system	S	0..1	uri	The namespace for the identifier value
value	S	1..1	string	The value that is unique
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
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	attachment-request-code | attachment-request-questionnaire Binding: CDex Attachment 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(CDex Patient Demographics Profile) {c}	Contained Patient.
reference	S	1..1	string	Contained resource reference Fixed Value: #patient
requester	S	1..1	Reference(US Core Organization Profile)	Payer asking for attachments
identifier	S	1..1	Identifier	Payer ID
owner	S	1..1	Reference(CDex PractitionerRole Profile) {c}	Provider who submitted claim or preauthorization
reference	S	1..1	string	Contained resource reference Fixed Value: #practitionerrole
reasonCode	S	1..1	CodeableConcept	Why task is needed
Slices for coding	SC	1..*	Coding	Code defined by a terminology system Slice: Unordered, Open by value:$this
coding:use	S	1..*	Coding	Code defined by a terminology system Binding: CDex Claim Use Value Set (required)
system	S	0..1	uri	Identity of the terminology system
code	S	1..1	code	claim | preauthorization
text	S	0..1	string	claim | preauthorization Binding: CDex Claim Use Value Set (required)
reasonReference	S	1..1	Reference(Resource)	Why task is needed
identifier	S	1..1	Identifier	Claim or Prior Authorization ID
restriction	S	0..1	BackboneElement	Constraints on fulfillment tasks
period	S	0..1	Period	Attachments due date
Slices for input	S	2..*	BackboneElement	Information used to perform task Slice: Unordered, Open by pattern:type
input:code	SC	0..*	BackboneElement	Attachment Codes Binding: LOINC valid-hl7-attachment-requests (extensible)
extension	S	0..*	Extension	Extension
url	S	1..1	uri	"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
value[x]	S	1..1	positiveInt	Value of extension
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	LOINC attachment code value
input:questionnaire	CD	0..1	BackboneElement	Data Request questionnaire
extension	S	0..*	Extension	Extension
url	S	1..1	uri	"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
value[x]	S	1..1	positiveInt	Value of extension
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:payer-url	S	1..1	BackboneElement	Payer Url
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: payer-url
value[x]	S	1..1	url	Payer url value
input:service-date	SC	0..1	BackboneElement	Service Date
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: service-date
value[x]	SC	1..1	date	Service Date value cdex-2: Date must be to day.
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)
input:multiple-submits		0..1	BackboneElement	Multiple submits flag
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: multiple-submits-flag
value[x]		1..1	boolean	Multiple submits flag value
Slices for output		0..*	BackboneElement	Information produced as part of task Slice: Unordered, Open by pattern:type
output:data		0..*	BackboneElement	Requested data
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/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-value
value[x]		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.status	required	HRexTaskStatus
Task.code	required	CDexAttachmentTaskCode
Task.reasonCode.coding:use	required	CDexClaimUseCodes
Task.reasonCode.text	required	CDexClaimUseCodes
Task.input:code	extensible	LOINC valid-hl7-attachment-requests
Task.input:POU.value[x]	extensible	CDexPOUCodes

Constraints

Id	Grade	Path(s)	Details	Requirements
cdex-1	error	Task	The "service-date" input SHALL be present if the attachment is for a claim. : Task.reasonCode.coding.code.where($this='claim').exists() implies Task.input.type.coding.code.where($this='service-date').exists()
cdex-2	error	Task.input:service-date.value[x]	Date must be to day. : $this.toString().length() = 10
cdex-4	error	Task	If code = "attachment-request-code", must have one or more "code" inputs. : Task.code.coding.code.where($this='attachment-request-code').exists() implies Task.input.type.coding.code.where($this='data-code').exists()
cdex-5	error	Task	If code = "attachment-request-questionnaire", must have one "questionnaire" input. : Task.code.coding.code.where($this='attachment-request-questionnaire').exists() implies Task.input.type.coding.code.where($this='questionnaire').exists()
cdex-6	error	Task	Must only have "code" inputs or one "questionnaire" input not both. : Task.input.type.coding.code.where($this='data-code').exists() implies Task.input.type.coding.code.where($this='questionnaire').empty()
cdex-10	warning	Task	If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. : (Task.code.coding.code.where($this='attachment-request-questionnaire').exists() and Task.status.where($this='completed').exists()) implies Task.output.type.coding.code.where($this='questionnaire-response').exists()
tdr-2	error	Task	Task statusReason SHALL be populated if status is 'rejected' or 'failed' : (status = 'rejected' or status = 'failed') implies statusReason.exists()

Key Elements View

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed cdex-1: The "service-date" input SHALL be present if the attachment is for a claim. cdex-4: If code = "attachment-request-code", must have one or more "code" inputs. cdex-5: If code = "attachment-request-questionnaire", must have one "questionnaire" input. cdex-6: Must only have "code" inputs or one "questionnaire" input not both. cdex-10: If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed'
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
Slices for contained	S	1..*	Resource	Contained, inline Resources Slice: Unordered, Open by type:$this
contained:practitionerrole	SC	1..1	CDexPractitionerRole	Contained PractitionerRole resource
contained:patient	S	1..1	CDexPatientDemographics	Contained Patient resource
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
Slices for identifier	S	1..*	Identifier	Task Instance Identifier Slice: Unordered, Open by pattern:$this
identifier:tracking-id	S	1..1	Identifier	Re-association tracking control number Required Pattern: At least the following
type		1..1	CodeableConcept	Description of identifier Fixed Value: (complex)
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: tracking-id
use	?!Σ	0..1	code	usual | official | temp | secondary | old (If known) Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
system	SΣ	0..1	uri	The namespace for the identifier value Example General: http://www.acme.com/identifiers/patient
value	SΣ	1..1	string	The value that is unique Example General: 123456
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
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	attachment-request-code | attachment-request-questionnaire Binding: CDex Attachment 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(CDex Patient Demographics Profile) {c}	Contained Patient.
reference	SΣC	1..1	string	Contained resource reference Fixed Value: #patient
requester	SΣ	1..1	Reference(US Core Organization Profile)	Payer asking for attachments
identifier	SΣ	1..1	Identifier	Payer ID
owner	SΣ	1..1	Reference(CDex PractitionerRole Profile) {c}	Provider who submitted claim or preauthorization
reference	SΣC	1..1	string	Contained resource reference Fixed Value: #practitionerrole
reasonCode	S	1..1	CodeableConcept	Why task is needed Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.
Slices for coding	SΣC	1..*	Coding	Code defined by a terminology system Slice: Unordered, Open by value:$this
coding:use	SΣ	1..*	Coding	Code defined by a terminology system Binding: CDex Claim Use Value Set (required)
system	SΣ	0..1	uri	Identity of the terminology system
code	SΣ	1..1	code	claim | preauthorization
text	SΣ	0..1	string	claim | preauthorization Binding: CDex Claim Use Value Set (required)
reasonReference	S	1..1	Reference(Resource)	Why task is needed
identifier	SΣ	1..1	Identifier	Claim or Prior Authorization ID
restriction	S	0..1	BackboneElement	Constraints on fulfillment tasks
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
period	S	0..1	Period	Attachments due date
Slices for input	S	2..*	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:code	SC	0..*	BackboneElement	Attachment Codes
extension	S	0..*	Extension	Extension
url	S	1..1	uri	"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
value[x]	S	1..1	positiveInt	Value of extension
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	LOINC attachment code value
input:questionnaire	C	0..1	BackboneElement	Data Request questionnaire
extension	S	0..*	Extension	Extension
url	S	1..1	uri	"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
value[x]	S	1..1	positiveInt	Value of extension
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:payer-url	S	1..1	BackboneElement	Payer Url
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: payer-url
value[x]	S	1..1	url	Payer url value
input:service-date	SC	0..1	BackboneElement	Service Date
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: service-date
value[x]	SC	1..1	date	Service Date value cdex-2: Date must be to day.
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)
input:multiple-submits		0..1	BackboneElement	Multiple submits flag
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: multiple-submits-flag
value[x]		1..1	boolean	Multiple submits flag value
Slices for output		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		0..*	BackboneElement	Requested data
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/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-value
value[x]		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.identifier:tracking-id.use	required	IdentifierUse
Task.status	required	HRexTaskStatus
Task.statusReason	example
Task.intent	required	Fixed Value: order
Task.code	required	CDexAttachmentTaskCode
Task.reasonCode	example
Task.reasonCode.coding:use	required	CDexClaimUseCodes
Task.reasonCode.text	required	CDexClaimUseCodes
Task.input.type	example
Task.input:code.type	example	Pattern: data-code
Task.input:questionnaire.type	example	Pattern: questionnaire
Task.input:payer-url.type	example	Pattern: payer-url
Task.input:service-date.type	example	Pattern: service-date
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.input:multiple-submits.type	example	Pattern: multiple-submits-flag
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-1	error	Task	The "service-date" input SHALL be present if the attachment is for a claim. : Task.reasonCode.coding.code.where($this='claim').exists() implies Task.input.type.coding.code.where($this='service-date').exists()
cdex-2	error	Task.input:service-date.value[x]	Date must be to day. : $this.toString().length() = 10
cdex-4	error	Task	If code = "attachment-request-code", must have one or more "code" inputs. : Task.code.coding.code.where($this='attachment-request-code').exists() implies Task.input.type.coding.code.where($this='data-code').exists()
cdex-5	error	Task	If code = "attachment-request-questionnaire", must have one "questionnaire" input. : Task.code.coding.code.where($this='attachment-request-questionnaire').exists() implies Task.input.type.coding.code.where($this='questionnaire').exists()
cdex-6	error	Task	Must only have "code" inputs or one "questionnaire" input not both. : Task.input.type.coding.code.where($this='data-code').exists() implies Task.input.type.coding.code.where($this='questionnaire').empty()
cdex-10	warning	Task	If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. : (Task.code.coding.code.where($this='attachment-request-questionnaire').exists() and Task.status.where($this='completed').exists()) implies Task.output.type.coding.code.where($this='questionnaire-response').exists()
tdr-2	error	Task	Task statusReason SHALL be populated if status is 'rejected' or 'failed' : (status = 'rejected' or status = 'failed') implies statusReason.exists()

Snapshot View

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed cdex-1: The "service-date" input SHALL be present if the attachment is for a claim. cdex-4: If code = "attachment-request-code", must have one or more "code" inputs. cdex-5: If code = "attachment-request-questionnaire", must have one "questionnaire" input. cdex-6: Must only have "code" inputs or one "questionnaire" input not both. cdex-10: If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse. tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed'
id	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
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
Slices for contained	S	1..*	Resource	Contained, inline Resources Slice: Unordered, Open by type:$this
contained:practitionerrole	SC	1..1	CDexPractitionerRole	Contained PractitionerRole resource
contained:patient	S	1..1	CDexPatientDemographics	Contained Patient resource
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
Slices for identifier	S	1..*	Identifier	Task Instance Identifier Slice: Unordered, Open by pattern:$this
identifier:tracking-id	S	1..1	Identifier	Re-association tracking control number Required Pattern: At least the following
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
use		0..1	code	usual | official | temp | secondary | old (If known)
type		1..1	CodeableConcept	Description of identifier Fixed Value: (complex)
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: tracking-id
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
system		0..1	uri	The namespace for the identifier value
value		0..1	string	The value that is unique
period		0..1	Period	Time period when id is/was valid for use
assigner		0..1	Reference(Organization)	Organization that issued id (may be just text)
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
use	?!Σ	0..1	code	usual | official | temp | secondary | old (If known) Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .
type	Σ	0..1	CodeableConcept	Description of identifier Binding: Identifier Type Codes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
system	SΣ	0..1	uri	The namespace for the identifier value Example General: http://www.acme.com/identifiers/patient
value	SΣ	1..1	string	The value that is unique Example General: 123456
period	Σ	0..1	Period	Time period when id is/was valid for use
assigner	Σ	0..1	Reference(Organization)	Organization that issued id (may be just text)
instantiatesCanonical	Σ	0..1	canonical(ActivityDefinition)	Formal definition of task
instantiatesUri	Σ	0..1	uri	Formal definition of task
basedOn	Σ	0..*	Reference(Resource)	Request fulfilled by this task
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	Σ	0..1	CodeableConcept	E.g. "Specimen collected", "IV prepped" Binding: (unbound) (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.
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	attachment-request-code | attachment-request-questionnaire Binding: CDex Attachment 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
focus	Σ	0..1	Reference(Resource)	What task is acting on
for	SΣ	1..1	Reference(CDex Patient Demographics Profile) {c}	Contained Patient.
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	SΣC	1..1	string	Contained resource reference Fixed Value: #patient
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	Σ	0..1	Identifier	Logical reference, when literal reference is not known
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	C	0..1	dateTime	Task Creation Date
lastModified	ΣC	0..1	dateTime	Task Last Modified Date
requester	SΣ	1..1	Reference(US Core Organization Profile)	Payer asking for attachments
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Σ	1..1	Identifier	Payer 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(CDex PractitionerRole Profile) {c}	Provider who submitted claim or preauthorization
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	SΣC	1..1	string	Contained resource reference Fixed Value: #practitionerrole
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	Σ	0..1	Identifier	Logical reference, when literal reference is not known
display	Σ	0..1	string	Text alternative for the resource
location	Σ	0..1	Reference(Location)	Where task occurs
reasonCode	S	1..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
Slices for coding	SΣC	1..*	Coding	Code defined by a terminology system Slice: Unordered, Open by value:$this
coding:use	SΣ	1..*	Coding	Code defined by a terminology system Binding: CDex Claim Use 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
system	SΣ	0..1	uri	Identity of the terminology system
version	Σ	0..1	string	Version of the system - if relevant
code	SΣ	1..1	code	claim | preauthorization
display	Σ	0..1	string	Representation defined by the system
userSelected	Σ	0..1	boolean	If this coding was chosen directly by the user
text	SΣ	0..1	string	claim | preauthorization Binding: CDex Claim Use Value Set (required)
reasonReference	S	1..1	Reference(Resource)	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Σ	1..1	Identifier	Claim or Prior Authorization 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	S	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	S	0..1	Period	Attachments due date
recipient		0..*	Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization)	For whom is fulfillment sought?
Slices for input	S	2..*	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:code	SC	0..*	BackboneElement	Attachment Codes
id		0..1	string	Unique id for inter-element referencing
extension	S	0..*	Extension	Extension
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
url	S	1..1	uri	"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
value[x]	S	1..1	positiveInt	Value of extension
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	LOINC attachment code value
input:questionnaire	C	0..1	BackboneElement	Data Request questionnaire
id		0..1	string	Unique id for inter-element referencing
extension	S	0..*	Extension	Extension
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
url	S	1..1	uri	"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
value[x]	S	1..1	positiveInt	Value of extension
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:payer-url	S	1..1	BackboneElement	Payer Url
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: payer-url
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	url	Payer url value
input:service-date	SC	0..1	BackboneElement	Service Date
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: service-date
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]	SC	1..1	date	Service Date value cdex-2: Date must be to day.
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)
input:multiple-submits		0..1	BackboneElement	Multiple submits 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		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: multiple-submits-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]		1..1	boolean	Multiple submits flag value
Slices for output		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		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		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]		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.language	preferred	CommonLanguages Additional Bindings Purpose AllLanguages Max Binding
Task.identifier:tracking-id.use	required	IdentifierUse
Task.identifier:tracking-id.type	extensible	Identifier Type Codes
Task.status	required	HRexTaskStatus
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	Fixed Value: order
Task.priority	required	RequestPriority
Task.code	required	CDexAttachmentTaskCode
Task.for.type	extensible	ResourceType
Task.requester.type	extensible	ResourceType
Task.performerType	preferred	ProcedurePerformerRoleCodes
Task.owner.type	extensible	ResourceType
Task.reasonCode	example
Task.reasonCode.coding:use	required	CDexClaimUseCodes
Task.reasonCode.text	required	CDexClaimUseCodes
Task.reasonReference.type	extensible	ResourceType
Task.input.type	example
Task.input:code.type	example	Pattern: data-code
Task.input:questionnaire.type	example	Pattern: questionnaire
Task.input:payer-url.type	example	Pattern: payer-url
Task.input:service-date.type	example	Pattern: service-date
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.input:multiple-submits.type	example	Pattern: multiple-submits-flag
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-2	error	Task.input:service-date.value[x]	Date must be to day. : $this.toString().length() = 10

This structure is derived from Task

Summary

Mandatory: 22 elements (6 nested mandatory elements)
Must-Support: 50 elements
Fixed Value: 6 elements

Structures

This structure refers to these other structures:

• CDex PractitionerRole Profile (http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-practitionerrole)
• CDex Patient Demographics Profile (http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-patient-demographics)
• US Core Organization Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization)
• 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.contained is sliced based on the value of type:$this
• The element Task.identifier is sliced based on the value of pattern:$this
• The element Task.reasonCode.coding is sliced based on the value of value:$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