Although the CDex Task Data Request Profile is based upon the Da Vinci HRex Task Data Request, this profile is technically non-conformant with it because of the questionnaire input parameter. The CDex editors made a change request FHIR-39686 to update the HRex Profile. If the change request is approved and applied, a future version of CDex will be derived from HRex.

The Task.reasonReference DocumentReference.author is a *Must Support element with four target profile and three Coverage profiles. Servers SHALL support at least one of them, and when supporting a Coverage profile, SHALL support the Coverage Profile based on the US Core version as follows:

Clients SHALL support all four profiles.

[Da Vinci Prior Authorization Support (PAS)]: [CDex Work Queue Value Set]: ValueSet-cdex-work-queue.html [What is Signed]: signatures.html#what-is-signed [Signatures for Task Based Requests]: task-based-approach.html#signatures [X12]: https://x12.org/ [X12 transactions]: https://x12.org/ [X12 Transaction Sets]: https://x12.org/products/transaction-sets [HEDIS]: https://en.wikipedia.org/wiki/Healthcare_Effectiveness_Data_and_Information_Set [Specification]: specification.html [$match]: http://hl7.org/fhir/R4/patient-operation-match.html [Coverage]: http://hl7.org/fhir/R4/coverage.html [FHIR RESTful Search syntax]: http://hl7.org/fhir/R4/search.html#Introduction [DocumentReference]: http://hl7.org/fhir/R4/documentreference.html [FHIR Signature]: http://hl7.org/fhir/R4/datatypes.html#signature [Bundle.signature]: http://hl7.org/fhir/R4/bundle-definitions.html#Bundle.signature [enveloped signature]: http://www.w3.org/TR/xmldsig-core/#def-SignatureEnveloped [(Verification Signature)]: http://hl7.org/fhir/R4/valueset-signature-type.html [FHIR Document]: http://hl7.org/fhir/R4/documents.html [RFC 7515]: https://tools.ietf.org/html/rfc7515 [JSON Signature rules]: http://hl7.org/fhir/R4/datatypes.html#JSON [RFC 7515: JSON Web Signature (JWS)]: https://tools.ietf.org/html/rfc7515 [Detached]: https://tools.ietf.org/html/rfc7515#appendix-F [Canonical JSON]: http://hl7.org/fhir/R4/json.html#canonical [JWS JSON Serialization]: https://datatracker.ietf.org/doc/html/rfc7515#section-3.2 [X.509 certificates]: https://www.itu.int/rec/T-REC-X.509 [RFC 7518]: https://tools.ietf.org/html/rfc7518 [RFC 7517]: https://tools.ietf.org/html/rfc7517 [RFC 8785]: https://datatracker.ietf.org/doc/rfc8785 [self-signed certificates]: https://en.wikipedia.org/wiki/Self-signed_certificate [Signed SearchSet Bundle Example]: signed-searchset-bundle-example.html [Signed Document Bundle Example]: signed-document-bundle-example.html [FHIR-36158]: https://jira.hl7.org/browse/FHIR-36158 [Solicited and Unsolicited Attachments]: solicited-unsolicited-attachments.html [Sending Attachments]: sending-attachments.html [Requesting Attachments Using Attachment Codes]: requesting-attachments-code.html [Requesting Attachments Using Questionnaires]: requesting-attachments-questionnaire.html [Using Questionnaire as Task Input]: task-based-approach.html#using-questionnaire-as-task-input [Using CDex Attachments with DaVinci PAS]: burden-reduction.html [CDex Task Attachment Request Profile]: StructureDefinition-cdex-task-attachment-request.html [LOINC attachment codes]: https://loinc.org/attachments/ [Parameters]: http://hl7.org/fhir/R4/parameters.html [CDex Patient Demographics Profile]: StructureDefinition-cdex-patient-demographics.html [CDex Claim Use Value Set]: ValueSet-cdex-claim-use.html [Prior-Auth AttachmentRequest Example]: Task-cdex-task-example20.html [Claim AttachmentRequest Example]: Task-cdex-task-example19.html [CDex Temporary Code System]: CodeSystem-cdex-temp.html [NHIN Purpose Of Use Code System]: http://hl7.org/fhir/R4/codesystem-nhin-purposeofuse.html [LOINC Document Ontology]: https://loinc.org/document-ontology/ [CDex Signature Bundle Profile]: StructureDefinition-cdex-signature-bundle.html [FHIR RESTful search]: http://hl7.org/fhir/R4/http.html#search [FHIR RESTful read]: http://hl7.org/fhir/R4/http.html#read [Change Log]: changes.html [CDex Parameters Example1]: Parameters-cdex-parameters-example1.html [CDex Parameters Example2]: Parameters-cdex-parameters-example2.html [CDex Parameters Example3]: Parameters-cdex-parameters-example3.html [CDex Parameters Example4]: Parameters-cdex-parameters-example4.html [validating profiles and resources]: http://hl7.org/fhir/R4/validation.html [ImplementationGuide]: http://hl7.org/fhir/R4/implementationguide.html [CDex ImplementationGuide Resource]: ImplementationGuide-hl7.fhir.us.davinci-cdex.html [Da Vinci DTR]: http://hl7.org/fhir/us/davinci-dtr/STU2.1 [Questionnaire]: http://hl7.org/fhir/R4/questionnaire.html [Smart Version 2.0.0 EHR launch flow]: https://hl7.org/fhir/smart-app-launch/app-launch.html#launch-app-ehr-launch [Using Da Vinci DTR to Complete the Questionnaire]: requesting-attachments-questionnaire.html#using-da-vinci-dtr-to-complete-the-questionnaire [Conforming to CDex Attachments]: attachments-conformance.html [Request for Additional Information]: /additionalinfo.html [SDC Questionnaire Response Profile]:http://hl7.org/fhir/uv/sdc/STU3StructureDefinition-sdc-questionnaireresponse.html [SDC Adaptive Questionnaire Response Profile]:http://hl7.org/fhir/uv/sdc/STU3StructureDefinition-sdc-questionnaireresponse-adapt.html [45 CFR 164.506 Treatment, Payment, and Health Care Operations (TPO)]: https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E/section-164.506 [must support]: http://hl7.org/fhir/us/davinci-hrex/STU1.1/conformance.html [DTR SMART App Launch]: requesting-attachments-questionnaire.html#dtr-smart-app-launch [Conforming to CDex Task Based Approach]: task-based-conformance.html [Signature Extension]: http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature [DTR Standard Questionnaire]: http://hl7.org/fhir/us/davinci-dtr/STU2.1StructureDefinition-dtr-std-questionnaire.html [signatureRequired]: http://hl7.org/fhir/StructureDefinition/questionnaire-signatureRequired [CDex Signature Profile]: StructureDefinition-cdex-signature.html [CDex SDC QuestionnaireResponse Profile]: StructureDefinition-cdex-sdc-questionnaireresponse.html [QuestionnaireResponse]: http://hl7.org/fhir/R4/questionnaireresponse.html [Topic-Based Subscriptions Framework]: http://hl7.org/fhir/2022Sep/subscriptions.html [C-CDA on FHIR Documents]: http://www.hl7.org/fhir/us/ccda/index.html [FHIR Conformance]: http://hl7.org/fhir/R4/conformance-rules.html#conflang [Must Support]: http://hl7.org/fhir/R4/profiling.html#mustsupport [modifier elements]: http://hl7.org/fhir/R4/conformance-rules.html#isModifier [CDex PractitionerRole Profile]: StructureDefinition-cdex-practitionerrole.html [CDex Task Update]: SubscriptionTopic-cdex-task-update.html [Subscription R5 Backport Implementation Guide]: http://hl7.org/fhir/uv/subscriptions-backport/STU1.1 [SubscriptionTopic]: https://hl7.org/fhir/R4B/subscriptiontopic.html [CapabilityStatement SubscriptionTopic Canonical]: http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-capabilitystatement-subscriptiontopic-canonical.html [Conformance in FHIR R4]: http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/conformance.html#conformance-in-fhir-r4 [R4/B Topic-Based Subscription Profile]: http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription.html [R4 Topic-Based Subscription Notification Bundle]: http://hl7.org/fhir/uv/subscriptions-backport/STU1.1/StructureDefinition-backport-subscription-notification-r4.html [HRex Task Status ValueSet]: http://hl7.org/fhir/us/davinci-hrex/STU1.1/ValueSet-hrex-task-status.html [Task.businessStatus]: http://hl7.org/fhir/R4/task-definitions.html#Task.businessStatus [Benefits]: task-based-approach.html#benefits [Task Inputs and Outputs]: task-based-approach.html#task-inputs-and-outputs [Purpose of Use]: task-based-approach.html#purpose-of-use [Task Reason]: task-based-approach.html#task-reason [Discovery of Identifiers]: task-based-approach.html#discovery-of-identifiers [Task State Machine]: task-based-approach.html#task-state-machine [Approaches to Exchanging FHIR Data]: https://hl7.org/fhir/R5/exchanging.html [PAS Claim Response Bundle]: /StructureDefinition-profile-pas-response-bundle.html [PAS Task]: /StructureDefinition-profile-task.html [Patient Matching]: https://hl7.org/fhir/us/identity-matching/patient-matching.html [Guidance on Identity Assurance]: https://hl7.org/fhir/us/identity-matching/guidance-on-identity-assurance.html [Interoperable Digital Identity and Patient Matching]: https://hl7.org/fhir/us/identity-matching/index.html [CQL]: https://cql.hl7.org/ [Da Vinci Use Cases]: https://confluence.hl7.org/display/DVP/Da+Vinci+Use+Cases [FHIR R4 core]: http://hl7.org/fhir/R4/fhir-spec.zip [FHIR core downloads]: http://hl7.org/fhir/R4/downloads.html [validator]: https://fhir.github.io/latest-ig-validator/org.hl7.fhir.validator.jar [instructions on how to use it]: https://confluence.hl7.org/display/FHIR/Using+the+FHIR+Validator

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

Name	Flags	Card.	Type	Description & Constraints
Task	C	0..*	Task	A task to be performed dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated dom-5: If a resource is contained in another resource, it SHALL NOT have a security label dom-6: A resource should have narrative for robust management inv-1: Last modified date must be greater than or equal to authored-on date. cdex-7: If code = "data-request-code", must have one "code" input. cdex-12: If code = "data-request-query", must have one "query" input. cdex-8: If code = "data-request-questionnaire", must have one "questionnaire" input. cdex-9: Must have exactly one input that is data-query or data-code or questionnaire tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed' tdr-3: Task output SHALL be populated if status is 'completed' cdex-11: If code = "data-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse.
meta	Σ	0..1	Meta	Metadata about the resource ele-1: All FHIR elements must have a @value or children
Slices for tag	Σ	0..*	Coding	Tags applied to this resource Slice: Unordered, Open by value:$this Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones". ele-1: All FHIR elements must have a @value or children
tag:All Slices				Content/Rules for all slices
system	Σ	1..1	uri	Identity of the terminology system ele-1: All FHIR elements must have a @value or children
code	Σ	1..1	code	Symbol in syntax defined by the system ele-1: All FHIR elements must have a @value or children
tag:work-queue	Σ	0..*	Coding	Work Queue Tag Binding: CDex Work Queue Value Set (required) ele-1: All FHIR elements must have a @value or children
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created ele-1: All FHIR elements must have a @value or children
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both
identifier	S	0..*	Identifier	Task Instance Identifier ele-1: All FHIR elements must have a @value or children
basedOn	SΣ	0..*	Reference(Resource)	Authorization for data request ele-1: All FHIR elements must have a @value or children
status	?!SΣC	1..1	code	draft | requested | received | accepted | + Binding: HRex Task Status ValueSet (required) ele-1: All FHIR elements must have a @value or children
statusReason	SΣC	0..1	CodeableConcept	Reason for current status Binding Description (No ValueSet): (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow. ele-1: All FHIR elements must have a @value or children
text	SΣ	1..1	string	Plain text representation of the concept ele-1: All FHIR elements must have a @value or children
businessStatus	SΣ	0..1	CodeableConcept	For example, 'waiting on internal review' Binding Description (No ValueSet): (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc. ele-1: All FHIR elements must have a @value or children
text	SΣ	1..1	string	Plain text representation of the concept ele-1: All FHIR elements must have a @value or children
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. ele-1: All FHIR elements must have a @value or children Fixed Value: order
code	SΣC	1..1	CodeableConcept	data-request-query | data-request-code | data-request-questionnaire Binding: CDex Data Request Task Code Value Set (required) ele-1: All FHIR elements must have a @value or children
coding	SΣ	1..*	Coding	Code defined by a terminology system ele-1: All FHIR elements must have a @value or children
system	SΣ	0..1	uri	Identity of the terminology system ele-1: All FHIR elements must have a @value or children Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
code	SΣ	1..1	code	Symbol in syntax defined by the system ele-1: All FHIR elements must have a @value or children
for	SΣ	1..1	Reference(US Core Patient Profile(3.1.1) | US Core Patient Profile(6.1.0) | US Core Patient Profile(7.0.0))	Member (i.e., patient) being queried ele-1: All FHIR elements must have a @value or children
identifier	SΣ	0..1	Identifier	Patient Member ID ele-1: All FHIR elements must have a @value or children
authoredOn	SC	1..1	dateTime	Task Creation Date ele-1: All FHIR elements must have a @value or children
requester	SΣ	1..1	Reference(US Core Practitioner Profile(3.1.1) | US Core Practitioner Profile(6.1.0) | US Core Practitioner Profile(7.0.0) | HRex Organization Profile(1.1.0))	Who is asking for data ele-1: All FHIR elements must have a @value or children
identifier	SΣ	0..1	Identifier	Data Consumer ID ele-1: All FHIR elements must have a @value or children
owner	SΣ	1..1	Reference(US Core Practitioner Profile(3.1.1) | US Core Practitioner Profile(6.1.0) | US Core Practitioner Profile(7.0.0) | HRex Organization Profile(1.1.0))	Who is being asked for data ele-1: All FHIR elements must have a @value or children
identifier	SΣ	0..1	Identifier	Provider ID ele-1: All FHIR elements must have a @value or children
reasonCode	S	0..1	CodeableConcept	Why task is needed Binding Description (No ValueSet): (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital. ele-1: All FHIR elements must have a @value or children
text	SΣ	1..1	string	Plain text representation of the concept ele-1: All FHIR elements must have a @value or children
reasonReference	S	0..1	Reference(Claim | Coverage | US Core Coverage Profile(6.1.0) | US Core Coverage Profile(7.0.0))	Why task is needed ele-1: All FHIR elements must have a @value or children
identifier	SΣ	0..1	Identifier	Coverage or Claim ID ele-1: All FHIR elements must have a @value or children
Slices for input	S	1..*	BackboneElement	Information used to perform task Slice: Unordered, Open by value:type ele-1: All FHIR elements must have a @value or children
input:All Slices				Content/Rules for all slices
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both
type		1..1	CodeableConcept	Label for the input Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc. ele-1: All FHIR elements must have a @value or children
value[x]		1..1		Content to use in performing the task ele-1: All FHIR elements must have a @value or children
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
input:query	SC	0..1	BackboneElement	Requested query ele-1: All FHIR elements must have a @value or children
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both
type	S	1..1	CodeableConcept	Label for the input Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc. ele-1: All FHIR elements must have a @value or children Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-query
value[x]	S	1..1	string	query value ele-1: All FHIR elements must have a @value or children
input:code	SC	0..1	BackboneElement	Requested data code ele-1: All FHIR elements must have a @value or children
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both
type	S	1..1	CodeableConcept	Label for the input Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc. ele-1: All FHIR elements must have a @value or children Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-code
value[x]	S	1..1	CodeableConcept	query value Binding: US Core DocumentReference Type (extensible) ele-1: All FHIR elements must have a @value or children
input:questionnaire	C	0..1	BackboneElement	Data Request questionnaire ele-1: All FHIR elements must have a @value or children
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both
type		1..1	CodeableConcept	Label for the input Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc. ele-1: All FHIR elements must have a @value or children 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 Standard Questionnaire | DTR Questionnaire for adaptive form)	URL ele-1: All FHIR elements must have a @value or children
Slices for extension				Content/Rules for all slices
questionnaireDisplay		0..1	string	Display name for canonical reference URL: http://hl7.org/fhir/StructureDefinition/display ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both
input:signature	S	0..1	BackboneElement	Signature flag ele-1: All FHIR elements must have a @value or children
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both
type	S	1..1	CodeableConcept	Label for the input Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc. ele-1: All FHIR elements must have a @value or children 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 ele-1: All FHIR elements must have a @value or children
input:POU		0..1	BackboneElement	Purpose of use code ele-1: All FHIR elements must have a @value or children
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both
type		1..1	CodeableConcept	Label for the input Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc. ele-1: All FHIR elements must have a @value or children 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) ele-1: All FHIR elements must have a @value or children
Slices for output	SC	0..*	BackboneElement	Information produced as part of task Slice: Unordered, Open by value:type ele-1: All FHIR elements must have a @value or children
output:All Slices				Content/Rules for all slices
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both
type		1..1	CodeableConcept	Label for output Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc. ele-1: All FHIR elements must have a @value or children
value[x]		1..1		Result of output ele-1: All FHIR elements must have a @value or children
valueBase64Binary			base64Binary
valueBoolean			boolean
valueCanonical			canonical(Any)
valueCode			code
valueDate			date
valueDateTime			dateTime
valueDecimal			decimal
valueId			id
valueInstant			instant
valueInteger			integer
valueMarkdown			markdown
valueOid			oid
valuePositiveInt			positiveInt
valueString			string
valueTime			time
valueUnsignedInt			unsignedInt
valueUri			uri
valueUrl			url
valueUuid			uuid
valueAddress			Address
valueAge			Age
valueAnnotation			Annotation
valueAttachment			Attachment
valueCodeableConcept			CodeableConcept
valueCoding			Coding
valueContactPoint			ContactPoint
valueCount			Count
valueDistance			Distance
valueDuration			Duration
valueHumanName			HumanName
valueIdentifier			Identifier
valueMoney			Money
valuePeriod			Period
valueQuantity			Quantity
valueRange			Range
valueRatio			Ratio
valueReference			Reference(Any)
valueSampledData			SampledData
valueSignature			Signature
valueTiming			Timing
valueContactDetail			ContactDetail
valueContributor			Contributor
valueDataRequirement			DataRequirement
valueExpression			Expression
valueParameterDefinition			ParameterDefinition
valueRelatedArtifact			RelatedArtifact
valueTriggerDefinition			TriggerDefinition
valueUsageContext			UsageContext
valueDosage			Dosage
valueMeta			Meta
output:data	S	0..*	BackboneElement	Requested data ele-1: All FHIR elements must have a @value or children
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both
type	S	1..1	CodeableConcept	Label for output Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc. ele-1: All FHIR elements must have a @value or children Required Pattern: At least the following
coding		1..*	Coding	Code defined by a terminology system Fixed Value: (complex)
system		1..1	uri	Identity of the terminology system Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
code		1..1	code	Symbol in syntax defined by the system Fixed Value: data-value
value[x]	S	1..1	Reference()	data reference ele-1: All FHIR elements must have a @value or children
output:response	C	0..1	BackboneElement	Information produced as part of task ele-1: All FHIR elements must have a @value or children
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both
type		1..1	CodeableConcept	Label for output Binding Description (No ValueSet): (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc. ele-1: All FHIR elements must have a @value or children 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(CDex SDC QuestionnaireResponse Profile | Adaptive Questionnaire Response)	Reference to the QuestionnaireResponse ele-1: All FHIR elements must have a @value or children
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
Task.meta.tag	example	CommonTags http://hl7.org/fhir/ValueSet/common-tags from the FHIR Standard
Task.meta.tag:work-queue	required	CDexWorkQueueCodes http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-work-queue from this IG
Task.status	required	HRexTaskStatus http://hl7.org/fhir/us/davinci-hrex/ValueSet/hrex-task-status
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	Fixed Value: order http://hl7.org/fhir/ValueSet/task-intent|4.0.1 from the FHIR Standard
Task.code	required	CDexDataRequestTaskCode http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-data-request-task-code from this IG
Task.reasonCode	example
Task.input.type	example
Task.input:query.type	example	Pattern: data-query
Task.input:code.type	example	Pattern: data-code
Task.input:code.value[x]	extensible	USCoreDocumentReferenceType http://hl7.org/fhir/us/core/ValueSet/us-core-documentreference-type
Task.input:questionnaire.type	example	Pattern: questionnaire
Task.input:signature.type	example	Pattern: signature-flag
Task.input:POU.type	example	Pattern: purpose-of-use
Task.input:POU.value[x]	extensible	CDexPOUCodes http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-POU from this IG
Task.output.type	example
Task.output:data.type	example	Pattern: data-value
Task.output:response.type	example	Pattern: questionnaire-response

Constraints

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

This structure is derived from Task

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

Terminology Bindings (Differential)

Path	Conformance	ValueSet	URI
Task.meta.tag:work-queue	required	CDexWorkQueueCodes http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-work-queue from this IG
Task.status	required	HRexTaskStatus http://hl7.org/fhir/us/davinci-hrex/ValueSet/hrex-task-status
Task.code	required	CDexDataRequestTaskCode http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-data-request-task-code from this IG
Task.input:code.value[x]	extensible	USCoreDocumentReferenceType http://hl7.org/fhir/us/core/ValueSet/us-core-documentreference-type
Task.input:POU.value[x]	extensible	CDexPOUCodes http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-POU from this IG

Constraints

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

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

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
Task.meta.security	extensible	All Security Labels http://hl7.org/fhir/ValueSet/security-labels from the FHIR Standard
Task.meta.tag	example	CommonTags http://hl7.org/fhir/ValueSet/common-tags from the FHIR Standard
Task.meta.tag:work-queue	required	CDexWorkQueueCodes http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-work-queue from this IG
Task.language	preferred	CommonLanguages http://hl7.org/fhir/ValueSet/languages from the FHIR Standard Additional Bindings Purpose AllLanguages Max Binding
Task.status	required	HRexTaskStatus http://hl7.org/fhir/us/davinci-hrex/ValueSet/hrex-task-status
Task.statusReason	example
Task.businessStatus	example
Task.intent	required	Fixed Value: order http://hl7.org/fhir/ValueSet/task-intent|4.0.1 from the FHIR Standard
Task.priority	required	RequestPriority http://hl7.org/fhir/ValueSet/request-priority|4.0.1 from the FHIR Standard
Task.code	required	CDexDataRequestTaskCode http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-data-request-task-code from this IG
Task.for.type	extensible	ResourceType http://hl7.org/fhir/ValueSet/resource-types from the FHIR Standard
Task.requester.type	extensible	ResourceType http://hl7.org/fhir/ValueSet/resource-types from the FHIR Standard
Task.performerType	preferred	ProcedurePerformerRoleCodes http://hl7.org/fhir/ValueSet/performer-role from the FHIR Standard
Task.owner.type	extensible	ResourceType http://hl7.org/fhir/ValueSet/resource-types from the FHIR Standard
Task.reasonCode	example
Task.reasonReference.type	extensible	ResourceType http://hl7.org/fhir/ValueSet/resource-types from the FHIR Standard
Task.input.type	example
Task.input:query.type	example	Pattern: data-query
Task.input:code.type	example	Pattern: data-code
Task.input:code.value[x]	extensible	USCoreDocumentReferenceType http://hl7.org/fhir/us/core/ValueSet/us-core-documentreference-type
Task.input:questionnaire.type	example	Pattern: questionnaire
Task.input:signature.type	example	Pattern: signature-flag
Task.input:POU.type	example	Pattern: purpose-of-use
Task.input:POU.value[x]	extensible	CDexPOUCodes http://hl7.org/fhir/us/davinci-cdex/ValueSet/cdex-POU from this IG
Task.output.type	example
Task.output:data.type	example	Pattern: data-value
Task.output:response.type	example	Pattern: questionnaire-response

Constraints

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