Da Vinci Clinical Data Exchange (CDex)
2.1.0-preview - CI Build United States of America flag

Da Vinci Clinical Data Exchange (CDex), published by HL7 International - Patient Care Work Group. This is not an authorized publication; it is the continuous build for version 2.1.0-preview). This version is based on the current content of https://github.com/HL7/davinci-ecdx/ and changes regularly. See the Directory of published versions

Resource Profile: CDex Task Data Request Profile

Official URL: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request Version: 2.1.0-preview
Standards status: Trial-use Maturity Level: 2 Computable Name: CDexTaskDataRequest

Copyright/Legal: Used by permission of HL7 International all rights reserved Creative Commons License

This Task profile is used to solicit information from a system. The Data Consumer uses it when direct query transactions are not an option, and the transaction may require human intervention. It represents both the data request and the returned “data request”. Data requests are supplied as codes, free-text, or FHIR Restful queries. It can also support requests for more detailed missing data using Questionnaire, CQL, and QuestionnaireResponse as supported by Da Vinci DTR.

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

  • A Task.status with a required binding to HRex Task Status ValueSet (this element is a mandatory Task element). For guidance when the provider is not able to complete the Task, refer to the When The Task Cannot Be Completed section.
  • A Task.intent fixed to “order” (this element is a mandatory Task element)
  • A Task.code of either “data-request-code”, “data-request-code”, or “data-request-questionnaire” communicating that the Data Consumer is requesting data using a code(or free text), a FHIR RESTful query, or a data request questionnaire.
    • If the code is “data-request-query”, the provider system returns data(s) identified by the FHIR RESTful query in the “query” input parameter.
    • If the code is “data-request-code”, the provider system returns data(s) identified by the LOINC code in the “code” input parameter.
    • If the code is “data-request-questionnaire”, the provider system uses Documentation Templates and Rules (DTR) to complete the Questionnaire referenced in the “questionnaire” input parameter.
  • A Task.for element representing the member (i.e.,patient) for whom the data is being requested
  • A Task.requester element communicating who is requesting the data
  • A Task.owner element representing the Provider who is being asked to provide the data

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

  • A Task.identifier element representing the unique data request identifier
  • A Task.basedOn element to communicate the order (ServiceRequest, CommunicationRequest, etc.) that authorizes the data request
  • A Task.statusReason.text to communicate the reason for the status (for example, if the Task is rejected or failed)
  • A Task.businessStatus.text element representing the progress in retrieving the data (for example, “waiting on internal review”).
  • A Task.for.reference.identifier element representing a patient business identifier like a Member ID
  • A Task.requester.reference.identifier element representing the Data Consumer business identifier
  • A Task.owner.reference.identifier element representing the Provider business identifier
  • A Task.reasonCode.text to communicate why the data is being requested
  • A Task.reasonReference.reference.identifier for the claim, pre-auth or coverage business identifier
  • A “query” Task.input element to communicate to the provider what information is needed using a FHIR RESTful query.*
  • A “code” Task.input element to communicate to the provider what information is needed using a LOINC code.*
    • For the “code” Task.input element, an extensible LOINC® Document types value set to communicate the specific information being requested
  • A Task.input element representing a flag to indicate whether the requested data requires a signature
    • A “data” Task.output element referring to FHIR resource(s) representing the result(s) of the data request code.

It defines the following elements to be optional:

It prohibits the following elements (max=0):

  • Task.focus

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

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. Therefore, the CDex made a change request FHIR-39686 to update the HRex Profile, and after published updates to the HRex profile, future versions of this profile will derive from it.

Usage:

Formal Views of Profile Content

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

This structure is derived from Task

NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA 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..1MetaMetadata about the resource
.... Slices for tag 0..*CodingTags applied to this resource
Slice: Unordered, Open by pattern:$this
..... tag:All Slices Content/Rules for all slices
...... system 0..1uriIdentity of the terminology system
...... code 1..1codeSymbol in syntax defined by the system
..... tag:work-queue 0..*CodingWork Queue Tag
Binding: CDex Work Queue Value Set (required)
... identifier S0..*IdentifierTask Instance Identifier
... basedOn S0..*Reference(Resource)Authorization for data request
... status SC1..1codedraft | requested | received | accepted | +
Binding: HRex Task Status ValueSet (required)
... statusReason SC0..1CodeableConceptReason for current status
.... text S1..1stringPlain text representation of the concept
... businessStatus S0..1CodeableConceptFor example, 'waiting on internal review'
.... text S1..1stringPlain text representation of the concept
... intent S1..1codeunknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Fixed Value: order
... code SC1..1CodeableConceptdata-request-code | data-request-query | data-request-questionnaire
Binding: CDex Data Request Task Code Value Set (required)
.... coding S1..*CodingCode defined by a terminology system
..... system S0..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
..... code S1..1codeSymbol in syntax defined by the system
... focus 0..0
... for S1..1Reference(US Core Patient Profile)Member (i.e., patient) being queried
.... identifier S0..1IdentifierPatient Member ID
... authoredOn S1..1dateTimeTask Creation Date
... requester S1..1Reference(US Core Organization Profile | US Core Practitioner Profile)Who is asking for data
.... identifier S0..1IdentifierData Consumer ID
... owner S1..1Reference(US Core Organization Profile | US Core Practitioner Profile)Who is being asked for data
.... identifier S0..1IdentifierProvider ID
... reasonCode S0..1CodeableConceptWhy task is needed
.... text S1..1stringPlain text representation of the concept
... reasonReference S0..1Reference(Claim | HRex Coverage Profile)Why task is needed
.... identifier S0..1IdentifierCoverage or Claim ID
... Slices for input S1..*BackboneElementInformation used to perform task
Slice: Unordered, Open by pattern:type
.... input:query SC0..1BackboneElementRequested query
..... type S1..1CodeableConceptLabel for the input
Required Pattern: At least the following
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: data-query
..... value[x] S1..1stringquery value
.... input:code SC0..1BackboneElementRequested data code
..... type S1..1CodeableConceptLabel for the input
Required Pattern: At least the following
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: data-code
..... value[x] S1..1CodeableConceptquery value
Binding: US Core DocumentReference Type (extensible)
.... input:questionnaire CD0..1BackboneElementData Request questionnaire
..... type 1..1CodeableConceptLabel for the input
Required Pattern: At least the following
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: questionnaire
..... value[x] 1..1canonical(DTR SDC Questionnaire | DTR SDC Questionnaire for adaptive form)URL
...... questionnaireDisplay 0..1stringDisplay name for canonical reference
URL: http://hl7.org/fhir/StructureDefinition/display
.... input:signature S0..1BackboneElementSignature flag
..... type S1..1CodeableConceptLabel for the input
Required Pattern: At least the following
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: signature-flag
..... value[x] S1..1booleanSignature flag value
.... input:POU 0..1BackboneElementPurpose of use code
..... type 1..1CodeableConceptLabel for the input
Required Pattern: At least the following
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: purpose-of-use
..... value[x] 1..1CodeableConceptPurpose of use value
Binding: CDex Purpose of Use Value Set (extensible)
... Slices for output SC0..*BackboneElementInformation produced as part of task
Slice: Unordered, Open by pattern:type
.... output:data S0..*BackboneElementRequested data
..... type S1..1CodeableConceptLabel for output
Required Pattern: At least the following
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: data-value
..... value[x] S1..1Reference()data reference
.... output:response CD0..1BackboneElementInformation produced as part of task
..... type 1..1CodeableConceptLabel for output
Required Pattern: At least the following
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: questionnaire-response
..... value[x] 1..1Reference(SDC Questionnaire Response | Adaptive Questionnaire Response)Reference to the QuestionnaireResponse

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
Task.meta.tag:work-queuerequiredCDexWorkQueueCodes
Task.statusrequiredHRexTaskStatus
Task.coderequiredCDexDataRequestTaskCode
Task.input:code.value[x]extensibleUSCoreDocumentReferenceType
Task.input:POU.value[x]extensibleCDexPOUCodes

Constraints

IdGradePath(s)DetailsRequirements
cdex-7errorTaskIf 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-8errorTaskIf 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-9errorTaskMust 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-11warningTaskIf 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-12errorTaskIf 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-2errorTaskTask statusReason SHALL be populated if status is 'rejected' or 'failed'
: (status = 'rejected' or status = 'failed') implies statusReason.exists()
tdr-3errorTaskTask output SHALL be populated if status is 'completed'
: (status = 'completed') implies output.exists()
NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA 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..1MetaMetadata about the resource
.... Slices for tag Σ0..*CodingTags applied to this resource
Slice: Unordered, Open by pattern:$this
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".


..... tag:All Slices Content/Rules for all slices
...... system Σ0..1uriIdentity of the terminology system
...... code Σ1..1codeSymbol in syntax defined by the system
..... tag:work-queue Σ0..*CodingWork Queue Tag
Binding: CDex Work Queue Value Set (required)
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S0..*IdentifierTask Instance Identifier
... basedOn SΣ0..*Reference(Resource)Authorization for data request
... status ?!SΣC1..1codedraft | requested | received | accepted | +
Binding: HRex Task Status ValueSet (required)
... statusReason SΣC0..1CodeableConceptReason 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..1stringPlain text representation of the concept
... businessStatus SΣ0..1CodeableConceptFor example, 'waiting on internal review'
Binding: (unbound) (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.

.... text SΣ1..1stringPlain text representation of the concept
... intent SΣ1..1codeunknown | 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ΣC1..1CodeableConceptdata-request-code | data-request-query | data-request-questionnaire
Binding: CDex Data Request Task Code Value Set (required)
.... coding SΣ1..*CodingCode defined by a terminology system
..... system SΣ0..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
..... code SΣ1..1codeSymbol in syntax defined by the system
... for SΣ1..1Reference(US Core Patient Profile)Member (i.e., patient) being queried
.... identifier SΣ0..1IdentifierPatient Member ID
... authoredOn SC1..1dateTimeTask Creation Date
... requester SΣ1..1Reference(US Core Organization Profile | US Core Practitioner Profile)Who is asking for data
.... identifier SΣ0..1IdentifierData Consumer ID
... owner SΣ1..1Reference(US Core Organization Profile | US Core Practitioner Profile)Who is being asked for data
.... identifier SΣ0..1IdentifierProvider ID
... reasonCode S0..1CodeableConceptWhy task is needed
Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.

.... text SΣ1..1stringPlain text representation of the concept
... reasonReference S0..1Reference(Claim | HRex Coverage Profile)Why task is needed
.... identifier SΣ0..1IdentifierCoverage or Claim ID
... Slices for input S1..*BackboneElementInformation used to perform task
Slice: Unordered, Open by pattern:type
.... input:All Slices Content/Rules for all slices
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type 1..1CodeableConceptLabel 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..1Content to use in performing the task
...... valueBase64Binarybase64Binary
...... valueBooleanboolean
...... valueCanonicalcanonical(Any)
...... valueCodecode
...... valueDatedate
...... valueDateTimedateTime
...... valueDecimaldecimal
...... valueIdid
...... valueInstantinstant
...... valueIntegerinteger
...... valueMarkdownmarkdown
...... valueOidoid
...... valuePositiveIntpositiveInt
...... valueStringstring
...... valueTimetime
...... valueUnsignedIntunsignedInt
...... valueUriuri
...... valueUrlurl
...... valueUuiduuid
...... valueAddressAddress
...... valueAgeAge
...... valueAnnotationAnnotation
...... valueAttachmentAttachment
...... valueCodeableConceptCodeableConcept
...... valueCodingCoding
...... valueContactPointContactPoint
...... valueCountCount
...... valueDistanceDistance
...... valueDurationDuration
...... valueHumanNameHumanName
...... valueIdentifierIdentifier
...... valueMoneyMoney
...... valuePeriodPeriod
...... valueQuantityQuantity
...... valueRangeRange
...... valueRatioRatio
...... valueReferenceReference(Any)
...... valueSampledDataSampledData
...... valueSignatureSignature
...... valueTimingTiming
...... valueContactDetailContactDetail
...... valueContributorContributor
...... valueDataRequirementDataRequirement
...... valueExpressionExpression
...... valueParameterDefinitionParameterDefinition
...... valueRelatedArtifactRelatedArtifact
...... valueTriggerDefinitionTriggerDefinition
...... valueUsageContextUsageContext
...... valueDosageDosage
...... valueMetaMeta
.... input:query SC0..1BackboneElementRequested query
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type S1..1CodeableConceptLabel 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
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: data-query
..... value[x] S1..1stringquery value
.... input:code SC0..1BackboneElementRequested data code
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type S1..1CodeableConceptLabel 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
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: data-code
..... value[x] S1..1CodeableConceptquery value
Binding: US Core DocumentReference Type (extensible)
.... input:questionnaire C0..1BackboneElementData Request questionnaire
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type 1..1CodeableConceptLabel 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
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: questionnaire
..... value[x] 1..1canonical(DTR SDC Questionnaire | DTR SDC Questionnaire for adaptive form)URL
...... questionnaireDisplay 0..1stringDisplay name for canonical reference
URL: http://hl7.org/fhir/StructureDefinition/display
.... input:signature S0..1BackboneElementSignature flag
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type S1..1CodeableConceptLabel 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
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: signature-flag
..... value[x] S1..1booleanSignature flag value
.... input:POU 0..1BackboneElementPurpose of use code
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type 1..1CodeableConceptLabel 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
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: purpose-of-use
..... value[x] 1..1CodeableConceptPurpose of use value
Binding: CDex Purpose of Use Value Set (extensible)
... Slices for output SC0..*BackboneElementInformation produced as part of task
Slice: Unordered, Open by pattern:type
.... output:All Slices Content/Rules for all slices
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type 1..1CodeableConceptLabel 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..1Result of output
...... valueBase64Binarybase64Binary
...... valueBooleanboolean
...... valueCanonicalcanonical(Any)
...... valueCodecode
...... valueDatedate
...... valueDateTimedateTime
...... valueDecimaldecimal
...... valueIdid
...... valueInstantinstant
...... valueIntegerinteger
...... valueMarkdownmarkdown
...... valueOidoid
...... valuePositiveIntpositiveInt
...... valueStringstring
...... valueTimetime
...... valueUnsignedIntunsignedInt
...... valueUriuri
...... valueUrlurl
...... valueUuiduuid
...... valueAddressAddress
...... valueAgeAge
...... valueAnnotationAnnotation
...... valueAttachmentAttachment
...... valueCodeableConceptCodeableConcept
...... valueCodingCoding
...... valueContactPointContactPoint
...... valueCountCount
...... valueDistanceDistance
...... valueDurationDuration
...... valueHumanNameHumanName
...... valueIdentifierIdentifier
...... valueMoneyMoney
...... valuePeriodPeriod
...... valueQuantityQuantity
...... valueRangeRange
...... valueRatioRatio
...... valueReferenceReference(Any)
...... valueSampledDataSampledData
...... valueSignatureSignature
...... valueTimingTiming
...... valueContactDetailContactDetail
...... valueContributorContributor
...... valueDataRequirementDataRequirement
...... valueExpressionExpression
...... valueParameterDefinitionParameterDefinition
...... valueRelatedArtifactRelatedArtifact
...... valueTriggerDefinitionTriggerDefinition
...... valueUsageContextUsageContext
...... valueDosageDosage
...... valueMetaMeta
.... output:data S0..*BackboneElementRequested data
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type S1..1CodeableConceptLabel 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
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: data-value
..... value[x] S1..1Reference()data reference
.... output:response C0..1BackboneElementInformation produced as part of task
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type 1..1CodeableConceptLabel 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
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: questionnaire-response
..... value[x] 1..1Reference(SDC Questionnaire Response | Adaptive Questionnaire Response)Reference to the QuestionnaireResponse

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
Task.meta.tagexampleCommonTags
Task.meta.tag:work-queuerequiredCDexWorkQueueCodes
Task.statusrequiredHRexTaskStatus
Task.statusReasonexample
Task.businessStatusexample
Task.intentrequiredFixed Value: order
Task.coderequiredCDexDataRequestTaskCode
Task.reasonCodeexample
Task.input.typeexample
Task.input:query.typeexamplePattern: data-query
Task.input:code.typeexamplePattern: data-code
Task.input:code.value[x]extensibleUSCoreDocumentReferenceType
Task.input:questionnaire.typeexamplePattern: questionnaire
Task.input:signature.typeexamplePattern: signature-flag
Task.input:POU.typeexamplePattern: purpose-of-use
Task.input:POU.value[x]extensibleCDexPOUCodes
Task.output.typeexample
Task.output:data.typeexamplePattern: data-value
Task.output:response.typeexamplePattern: questionnaire-response

Constraints

IdGradePath(s)DetailsRequirements
cdex-7errorTaskIf 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-8errorTaskIf 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-9errorTaskMust 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-11warningTaskIf 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-12errorTaskIf 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-2errorTaskTask statusReason SHALL be populated if status is 'rejected' or 'failed'
: (status = 'rejected' or status = 'failed') implies statusReason.exists()
tdr-3errorTaskTask output SHALL be populated if status is 'completed'
: (status = 'completed') implies output.exists()
NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA task to be performed
cdex-7: If code = "data-request-code", must have one "code" input.
cdex-12: If code = "data-request-query", must have one "query" input.
cdex-8: If code = "data-request-questionnaire", must have one "questionnaire" input.
cdex-9: Must have exactly one input that is data-query or data-code or questionnaire
tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed'
tdr-3: Task output SHALL be populated if status is 'completed'
cdex-11: If code = "data-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse.
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... versionId Σ0..1idVersion specific identifier
.... lastUpdated Σ0..1instantWhen the resource version last changed
.... source Σ0..1uriIdentifies where the resource comes from
.... profile Σ0..*canonical(StructureDefinition)Profiles this resource claims to conform to
.... security Σ0..*CodingSecurity Labels applied to this resource
Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.


.... Slices for tag Σ0..*CodingTags applied to this resource
Slice: Unordered, Open by pattern:$this
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".


..... tag:All Slices Content/Rules for all slices
...... id 0..1stringUnique id for inter-element referencing
...... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
...... system Σ0..1uriIdentity of the terminology system
...... version Σ0..1stringVersion of the system - if relevant
...... code Σ1..1codeSymbol in syntax defined by the system
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... tag:work-queue Σ0..*CodingWork Queue Tag
Binding: CDex Work Queue Value Set (required)
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S0..*IdentifierTask Instance Identifier
... instantiatesCanonical Σ0..1canonical(ActivityDefinition)Formal definition of task
... instantiatesUri Σ0..1uriFormal definition of task
... basedOn SΣ0..*Reference(Resource)Authorization for data request
... groupIdentifier Σ0..1IdentifierRequisition or grouper id
... partOf Σ0..*Reference(Task)Composite task
... status ?!SΣC1..1codedraft | requested | received | accepted | +
Binding: HRex Task Status ValueSet (required)
... statusReason SΣC0..1CodeableConceptReason 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..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... coding Σ0..*CodingCode defined by a terminology system
.... text SΣ1..1stringPlain text representation of the concept
... businessStatus SΣ0..1CodeableConceptFor example, 'waiting on internal review'
Binding: (unbound) (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.

.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... coding Σ0..*CodingCode defined by a terminology system
.... text SΣ1..1stringPlain text representation of the concept
... intent SΣ1..1codeunknown | 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..1coderoutine | urgent | asap | stat
Binding: RequestPriority (required): The task's priority.

... code SΣC1..1CodeableConceptdata-request-code | data-request-query | data-request-questionnaire
Binding: CDex Data Request Task Code Value Set (required)
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... coding SΣ1..*CodingCode defined by a terminology system
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... system SΣ0..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
..... version Σ0..1stringVersion of the system - if relevant
..... code SΣ1..1codeSymbol in syntax defined by the system
..... display Σ0..1stringRepresentation defined by the system
..... userSelected Σ0..1booleanIf this coding was chosen directly by the user
.... text Σ0..1stringPlain text representation of the concept
... description Σ0..1stringHuman-readable explanation of task
... for SΣ1..1Reference(US Core Patient Profile)Member (i.e., patient) being queried
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... reference ΣC0..1stringLiteral reference, Relative, internal or absolute URL
.... type Σ0..1uriType 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..1IdentifierPatient Member ID
.... display Σ0..1stringText alternative for the resource
... encounter Σ0..1Reference(Encounter)Healthcare event during which this task originated
... executionPeriod Σ0..1PeriodStart and end time of execution
... authoredOn SC1..1dateTimeTask Creation Date
... lastModified ΣC0..1dateTimeTask Last Modified Date
... requester SΣ1..1Reference(US Core Organization Profile | US Core Practitioner Profile)Who is asking for data
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... reference ΣC0..1stringLiteral reference, Relative, internal or absolute URL
.... type Σ0..1uriType 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..1IdentifierData Consumer ID
.... display Σ0..1stringText alternative for the resource
... performerType 0..*CodeableConceptRequested performer
Binding: ProcedurePerformerRoleCodes (preferred): The type(s) of task performers allowed.


... owner SΣ1..1Reference(US Core Organization Profile | US Core Practitioner Profile)Who is being asked for data
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... reference ΣC0..1stringLiteral reference, Relative, internal or absolute URL
.... type Σ0..1uriType 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..1IdentifierProvider ID
.... display Σ0..1stringText alternative for the resource
... location Σ0..1Reference(Location)Where task occurs
... reasonCode S0..1CodeableConceptWhy task is needed
Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.

.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... coding Σ0..*CodingCode defined by a terminology system
.... text SΣ1..1stringPlain text representation of the concept
... reasonReference S0..1Reference(Claim | HRex Coverage Profile)Why task is needed
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... reference ΣC0..1stringLiteral reference, Relative, internal or absolute URL
.... type Σ0..1uriType 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..1IdentifierCoverage or Claim ID
.... display Σ0..1stringText alternative for the resource
... insurance 0..*Reference(Coverage | ClaimResponse)Associated insurance coverage
... note 0..*AnnotationComments made about the task
... relevantHistory 0..*Reference(Provenance)Key events in history of the Task
... restriction 0..1BackboneElementConstraints on fulfillment tasks
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... repetitions 0..1positiveIntHow many times to repeat
.... period 0..1PeriodWhen fulfillment sought
.... recipient 0..*Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization)For whom is fulfillment sought?
... Slices for input S1..*BackboneElementInformation used to perform task
Slice: Unordered, Open by pattern:type
.... input:All Slices Content/Rules for all slices
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type 1..1CodeableConceptLabel 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..1Content to use in performing the task
...... valueBase64Binarybase64Binary
...... valueBooleanboolean
...... valueCanonicalcanonical(Any)
...... valueCodecode
...... valueDatedate
...... valueDateTimedateTime
...... valueDecimaldecimal
...... valueIdid
...... valueInstantinstant
...... valueIntegerinteger
...... valueMarkdownmarkdown
...... valueOidoid
...... valuePositiveIntpositiveInt
...... valueStringstring
...... valueTimetime
...... valueUnsignedIntunsignedInt
...... valueUriuri
...... valueUrlurl
...... valueUuiduuid
...... valueAddressAddress
...... valueAgeAge
...... valueAnnotationAnnotation
...... valueAttachmentAttachment
...... valueCodeableConceptCodeableConcept
...... valueCodingCoding
...... valueContactPointContactPoint
...... valueCountCount
...... valueDistanceDistance
...... valueDurationDuration
...... valueHumanNameHumanName
...... valueIdentifierIdentifier
...... valueMoneyMoney
...... valuePeriodPeriod
...... valueQuantityQuantity
...... valueRangeRange
...... valueRatioRatio
...... valueReferenceReference(Any)
...... valueSampledDataSampledData
...... valueSignatureSignature
...... valueTimingTiming
...... valueContactDetailContactDetail
...... valueContributorContributor
...... valueDataRequirementDataRequirement
...... valueExpressionExpression
...... valueParameterDefinitionParameterDefinition
...... valueRelatedArtifactRelatedArtifact
...... valueTriggerDefinitionTriggerDefinition
...... valueUsageContextUsageContext
...... valueDosageDosage
...... valueMetaMeta
.... input:query SC0..1BackboneElementRequested query
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type S1..1CodeableConceptLabel 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
...... id0..1stringUnique id for inter-element referencing
...... extension0..*ExtensionAdditional content defined by implementations
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... id0..1stringUnique id for inter-element referencing
....... extension0..*ExtensionAdditional content defined by implementations
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
....... version0..1stringVersion of the system - if relevant
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: data-query
....... display0..1stringRepresentation defined by the system
....... userSelected0..1booleanIf this coding was chosen directly by the user
...... text0..1stringPlain text representation of the concept
..... value[x] S1..1stringquery value
.... input:code SC0..1BackboneElementRequested data code
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type S1..1CodeableConceptLabel 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
...... id0..1stringUnique id for inter-element referencing
...... extension0..*ExtensionAdditional content defined by implementations
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... id0..1stringUnique id for inter-element referencing
....... extension0..*ExtensionAdditional content defined by implementations
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-hrex/CodeSystem/hrex-temp
....... version0..1stringVersion of the system - if relevant
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: data-code
....... display0..1stringRepresentation defined by the system
....... userSelected0..1booleanIf this coding was chosen directly by the user
...... text0..1stringPlain text representation of the concept
..... value[x] S1..1CodeableConceptquery value
Binding: US Core DocumentReference Type (extensible)
.... input:questionnaire C0..1BackboneElementData Request questionnaire
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type 1..1CodeableConceptLabel 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
...... id0..1stringUnique id for inter-element referencing
...... extension0..*ExtensionAdditional content defined by implementations
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... id0..1stringUnique id for inter-element referencing
....... extension0..*ExtensionAdditional content defined by implementations
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/uv/sdc/CodeSystem/temp
....... version0..1stringVersion of the system - if relevant
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: questionnaire
....... display0..1stringRepresentation defined by the system
....... userSelected0..1booleanIf this coding was chosen directly by the user
...... text0..1stringPlain text representation of the concept
..... value[x] 1..1canonical(DTR SDC Questionnaire | DTR SDC Questionnaire for adaptive form)URL
...... id 0..1stringxml:id (or equivalent in JSON)
...... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
...... questionnaireDisplay 0..1stringDisplay name for canonical reference
URL: http://hl7.org/fhir/StructureDefinition/display
...... value 0..1stringPrimitive value for canonical
.... input:signature S0..1BackboneElementSignature flag
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type S1..1CodeableConceptLabel 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
...... id0..1stringUnique id for inter-element referencing
...... extension0..*ExtensionAdditional content defined by implementations
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... id0..1stringUnique id for inter-element referencing
....... extension0..*ExtensionAdditional content defined by implementations
....... system1..1uriIdentity of the terminology system
Fixed Value: http://hl7.org/fhir/us/davinci-cdex/CodeSystem/cdex-temp
....... version0..1stringVersion of the system - if relevant
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: signature-flag
....... display0..1stringRepresentation defined by the system
....... userSelected0..1booleanIf this coding was chosen directly by the user
...... text0..1stringPlain text representation of the concept
..... value[x] S1..1booleanSignature flag value
.... input:POU 0..1BackboneElementPurpose of use code
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
..... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
..... type 1..1CodeableConceptLabel 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
...... id0..1stringUnique id for inter-element referencing
...... extension0..*ExtensionAdditional content defined by implementations
...... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
....... id0..1stringUnique id for inter-element referencing