Da Vinci Clinical Data Exchange (CDex)
2.0.0 - 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.0.0). 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 Attachment Request Profile

Official URL: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request Version: 2.0.0
Standards status: Trial-use Maturity Level: 2 Computable Name: CDexTaskAttachmentRequest

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

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

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

  • A contained Patient Resource defined by the CDex Patient Demographics Profile and communicating additional patient demographic data elements.
  • A contained PractitionerRole Resource defined by the CDex PractitionerRole Profile to communicate the provider ID as either a unique organization/location identifier (e.g., Type 2 NPI) or unique provider identifier (e.g., Type 1 NPI) or both.
  • A Task.identifier element representing the payers tracking identifier (referred to as the “re-association tracking control numbers”)
  • A Task.status with a required binding to HRex Task Status ValueSet (this element is a mandatory Task element). For guidance when the provider is not able to complete the Task, refer to the [When The Task Cannot Be Completed section(http://hl7.org/fhir/us/davinci-cdex/STU2/task-based-approach.html#when-the-task-cannot-be-completed).
  • A Task.intent fixed to “order” (this element is a mandatory Task element)
  • A Task.code of either “attachment-request-code” or “attachment-request-questionnaire” communicating that the Payer is requesting attachments for a claim or prior authorization using a code or data request questionnaire.
    • If the code is “attachment-request-code”, the provider system returns attachment(s) identified by the LOINC attachment code(s) in the “code” input parameter.
    • If the code is “attachment-request-questionnaire”, the provider system uses Documentation Templates and Rules (DTR) to complete the Questionnaire referenced in the “questionnaire” input parameter.
    • When either code is present, the provider system uses the $submit-attachment operation to return the information to the endpoint provided in “payer-url” input parameter.
  • A Task.requester.identifier element representing the Payer ID
  • A Task.owner.reference element fixed to “#practionerrole” - a reference the contained PractitionerRole Resource that represents the Provider ID.
  • A Task.for.reference element fixed to “#patient” - a reference the contained Patient Resource that represents basic Patient demographic data.
  • A Task.reasonCode to communicate whether the attachments are for a Claim or Prior Authorization
  • A Task.reasonReference.reference referencing the Claim or Prior Authorization ID (business Identifier)
  • A “payer-url” Task.input element representing the Payer endpoint URL to communicate to the provider to submit the attachments using the $submit-attachment operation

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

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

It defines the following elements to be optional:

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

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-1: The "service-date" input SHALL be present if the attachment is for a claim.
cdex-4: If code = "attachment-request-code", must have one or more "code" inputs.
cdex-5: If code = "attachment-request-questionnaire", must have one "questionnaire" input.
cdex-6: Must only have "code" inputs or one "questionnaire" input not both.
cdex-10: If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse.
tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed'
... Slices for contained S1..*ResourceContained, inline Resources
Slice: Unordered, Open by type:$this
.... contained:practitionerrole S1..1CDexPractitionerRoleContained PractitionerRole resource
.... contained:patient S1..1CDexPatientDemographicsContained Patient resource
... Slices for identifier S1..*IdentifierTask Instance Identifier
Slice: Unordered, Open by pattern:$this
.... identifier:tracking-id S1..1IdentifierRe-association tracking control number
Required Pattern: At least the following
..... type1..1CodeableConceptDescription of identifier
Fixed Value: (complex)
...... 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: tracking-id
..... system S0..1uriThe namespace for the identifier value
..... value S1..1stringThe value that is unique
... 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
... intent S1..1codeunknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
Fixed Value: order
... code SC1..1CodeableConceptattachment-request-code | attachment-request-questionnaire
Binding: CDex Attachment 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
... for S1..1Reference(CDex Patient Demographics Profile) {c}Contained Patient.
.... reference S1..1stringContained resource reference
Fixed Value: #patient
... requester S1..1Reference(US Core Organization Profile)Payer asking for attachments
.... identifier S1..1IdentifierPayer ID
... owner S1..1Reference(CDex PractitionerRole Profile) {c}Provider who submitted claim or preauthorization
.... reference S1..1stringContained resource reference
Fixed Value: #practitionerrole
... reasonCode S1..1CodeableConceptWhy task is needed
.... Slices for coding SC1..*CodingCode defined by a terminology system
Slice: Unordered, Open by value:$this
..... coding:use S1..*CodingCode defined by a terminology system
Binding: CDex Claim Use Value Set (required)
...... system S0..1uriIdentity of the terminology system
...... code S1..1codeclaim | preauthorization
.... text S0..1stringclaim | preauthorization
Binding: CDex Claim Use Value Set (required)
... reasonReference S1..1Reference(Resource)Why task is needed
.... identifier S1..1IdentifierClaim or Prior Authorization ID
... restriction S0..1BackboneElementConstraints on fulfillment tasks
.... period S0..1PeriodAttachments due date
... Slices for input S2..*BackboneElementInformation used to perform task
Slice: Unordered, Open by pattern:type
.... input:code SC0..*BackboneElementAttachment Codes
Binding: LOINC valid-hl7-attachment-requests (extensible)
..... extension S0..*ExtensionExtension
...... url S1..1uri"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
...... value[x] S1..1positiveIntValue of extension
..... 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..1CodeableConceptLOINC attachment code value
.... input:questionnaire CD0..1BackboneElementData Request questionnaire
..... extension S0..*ExtensionExtension
...... url S1..1uri"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
...... value[x] S1..1positiveIntValue of extension
..... 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:payer-url S1..1BackboneElementPayer Url
..... 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: payer-url
..... value[x] S1..1urlPayer url value
.... input:service-date SC0..1BackboneElementService Date
..... 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: service-date
..... value[x] SC1..1dateService Date value
cdex-2: Date must be to day.
.... 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)
.... input:multiple-submits 0..1BackboneElementMultiple submits flag
..... 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: multiple-submits-flag
..... value[x] 1..1booleanMultiple submits flag value
... Slices for output 0..*BackboneElementInformation produced as part of task
Slice: Unordered, Open by pattern:type
.... output:data 0..*BackboneElementRequested data
..... 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/us/davinci-hrex/CodeSystem/hrex-temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: data-value
..... value[x] 1..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.statusrequiredHRexTaskStatus
Task.coderequiredCDexAttachmentTaskCode
Task.reasonCode.coding:userequiredCDexClaimUseCodes
Task.reasonCode.textrequiredCDexClaimUseCodes
Task.input:codeextensibleLOINC valid-hl7-attachment-requests
Task.input:POU.value[x]extensibleCDexPOUCodes

Constraints

IdGradePath(s)DetailsRequirements
cdex-1errorTaskThe "service-date" input SHALL be present if the attachment is for a claim.
: Task.reasonCode.coding.code.where($this='claim').exists() implies Task.input.type.coding.code.where($this='service-date').exists()
cdex-2errorTask.input:service-date.value[x]Date must be to day.
: $this.toString().length() = 10
cdex-4errorTaskIf code = "attachment-request-code", must have one or more "code" inputs.
: Task.code.coding.code.where($this='attachment-request-code').exists() implies Task.input.type.coding.code.where($this='data-code').exists()
cdex-5errorTaskIf code = "attachment-request-questionnaire", must have one "questionnaire" input.
: Task.code.coding.code.where($this='attachment-request-questionnaire').exists() implies Task.input.type.coding.code.where($this='questionnaire').exists()
cdex-6errorTaskMust only have "code" inputs or one "questionnaire" input not both.
: Task.input.type.coding.code.where($this='data-code').exists() implies Task.input.type.coding.code.where($this='questionnaire').empty()
cdex-10warningTaskIf code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse.
: (Task.code.coding.code.where($this='attachment-request-questionnaire').exists() and Task.status.where($this='completed').exists()) implies Task.output.type.coding.code.where($this='questionnaire-response').exists()
tdr-2errorTaskTask statusReason SHALL be populated if status is 'rejected' or 'failed'
: (status = 'rejected' or status = 'failed') implies statusReason.exists()
NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA task to be performed
cdex-1: The "service-date" input SHALL be present if the attachment is for a claim.
cdex-4: If code = "attachment-request-code", must have one or more "code" inputs.
cdex-5: If code = "attachment-request-questionnaire", must have one "questionnaire" input.
cdex-6: Must only have "code" inputs or one "questionnaire" input not both.
cdex-10: If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse.
tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed'
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... Slices for contained S1..*ResourceContained, inline Resources
Slice: Unordered, Open by type:$this
.... contained:practitionerrole SC1..1CDexPractitionerRoleContained PractitionerRole resource
.... contained:patient S1..1CDexPatientDemographicsContained Patient resource
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... Slices for identifier S1..*IdentifierTask Instance Identifier
Slice: Unordered, Open by pattern:$this
.... identifier:tracking-id S1..1IdentifierRe-association tracking control number

Required Pattern: At least the following
..... type1..1CodeableConceptDescription of identifier
Fixed Value: (complex)
...... 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: tracking-id
..... use ?!Σ0..1codeusual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .

..... system SΣ0..1uriThe namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
..... value SΣ1..1stringThe value that is unique
Example General: 123456
... 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
... 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..1CodeableConceptattachment-request-code | attachment-request-questionnaire
Binding: CDex Attachment 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(CDex Patient Demographics Profile) {c}Contained Patient.
.... reference SΣC1..1stringContained resource reference
Fixed Value: #patient
... requester SΣ1..1Reference(US Core Organization Profile)Payer asking for attachments
.... identifier SΣ1..1IdentifierPayer ID
... owner SΣ1..1Reference(CDex PractitionerRole Profile) {c}Provider who submitted claim or preauthorization
.... reference SΣC1..1stringContained resource reference
Fixed Value: #practitionerrole
... reasonCode S1..1CodeableConceptWhy task is needed
Binding: (unbound) (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.

.... Slices for coding SΣC1..*CodingCode defined by a terminology system
Slice: Unordered, Open by value:$this
..... coding:use SΣ1..*CodingCode defined by a terminology system
Binding: CDex Claim Use Value Set (required)
...... system SΣ0..1uriIdentity of the terminology system
...... code SΣ1..1codeclaim | preauthorization
.... text SΣ0..1stringclaim | preauthorization
Binding: CDex Claim Use Value Set (required)
... reasonReference S1..1Reference(Resource)Why task is needed
.... identifier SΣ1..1IdentifierClaim or Prior Authorization ID
... restriction S0..1BackboneElementConstraints on fulfillment tasks
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... period S0..1PeriodAttachments due date
... Slices for input S2..*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:code SC0..*BackboneElementAttachment Codes
..... extension S0..*ExtensionExtension
...... url S1..1uri"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
...... value[x] S1..1positiveIntValue of extension
..... 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..1CodeableConceptLOINC attachment code value
.... input:questionnaire C0..1BackboneElementData Request questionnaire
..... extension S0..*ExtensionExtension
...... url S1..1uri"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
...... value[x] S1..1positiveIntValue of extension
..... 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:payer-url S1..1BackboneElementPayer Url
..... 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: payer-url
..... value[x] S1..1urlPayer url value
.... input:service-date SC0..1BackboneElementService Date
..... 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: service-date
..... value[x] SC1..1dateService Date value
cdex-2: Date must be to day.
.... 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)
.... input:multiple-submits 0..1BackboneElementMultiple submits flag
..... 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: multiple-submits-flag
..... value[x] 1..1booleanMultiple submits flag value
... Slices for output 0..*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 0..*BackboneElementRequested data
..... 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/us/davinci-hrex/CodeSystem/hrex-temp
....... code1..1codeSymbol in syntax defined by the system
Fixed Value: data-value
..... value[x] 1..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.identifier:tracking-id.userequiredIdentifierUse
Task.statusrequiredHRexTaskStatus
Task.statusReasonexample
Task.intentrequiredFixed Value: order
Task.coderequiredCDexAttachmentTaskCode
Task.reasonCodeexample
Task.reasonCode.coding:userequiredCDexClaimUseCodes
Task.reasonCode.textrequiredCDexClaimUseCodes
Task.input.typeexample
Task.input:code.typeexamplePattern: data-code
Task.input:questionnaire.typeexamplePattern: questionnaire
Task.input:payer-url.typeexamplePattern: payer-url
Task.input:service-date.typeexamplePattern: service-date
Task.input:signature.typeexamplePattern: signature-flag
Task.input:POU.typeexamplePattern: purpose-of-use
Task.input:POU.value[x]extensibleCDexPOUCodes
Task.input:multiple-submits.typeexamplePattern: multiple-submits-flag
Task.output.typeexample
Task.output:data.typeexamplePattern: data-value
Task.output:response.typeexamplePattern: questionnaire-response

Constraints

IdGradePath(s)DetailsRequirements
cdex-1errorTaskThe "service-date" input SHALL be present if the attachment is for a claim.
: Task.reasonCode.coding.code.where($this='claim').exists() implies Task.input.type.coding.code.where($this='service-date').exists()
cdex-2errorTask.input:service-date.value[x]Date must be to day.
: $this.toString().length() = 10
cdex-4errorTaskIf code = "attachment-request-code", must have one or more "code" inputs.
: Task.code.coding.code.where($this='attachment-request-code').exists() implies Task.input.type.coding.code.where($this='data-code').exists()
cdex-5errorTaskIf code = "attachment-request-questionnaire", must have one "questionnaire" input.
: Task.code.coding.code.where($this='attachment-request-questionnaire').exists() implies Task.input.type.coding.code.where($this='questionnaire').exists()
cdex-6errorTaskMust only have "code" inputs or one "questionnaire" input not both.
: Task.input.type.coding.code.where($this='data-code').exists() implies Task.input.type.coding.code.where($this='questionnaire').empty()
cdex-10warningTaskIf code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse.
: (Task.code.coding.code.where($this='attachment-request-questionnaire').exists() and Task.status.where($this='completed').exists()) implies Task.output.type.coding.code.where($this='questionnaire-response').exists()
tdr-2errorTaskTask statusReason SHALL be populated if status is 'rejected' or 'failed'
: (status = 'rejected' or status = 'failed') implies statusReason.exists()
NameFlagsCard.TypeDescription & Constraintsdoco
.. Task C0..*TaskA task to be performed
cdex-1: The "service-date" input SHALL be present if the attachment is for a claim.
cdex-4: If code = "attachment-request-code", must have one or more "code" inputs.
cdex-5: If code = "attachment-request-questionnaire", must have one "questionnaire" input.
cdex-6: Must only have "code" inputs or one "questionnaire" input not both.
cdex-10: If code = "attachment-request-questionnaire" and status = "completed", should have one "questionnaire-response" output referencing the QuestionnaireResponse.
tdr-2: Task statusReason SHALL be populated if status is 'rejected' or 'failed'
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... 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
... Slices for contained S1..*ResourceContained, inline Resources
Slice: Unordered, Open by type:$this
.... contained:practitionerrole SC1..1CDexPractitionerRoleContained PractitionerRole resource
.... contained:patient S1..1CDexPatientDemographicsContained Patient resource
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... Slices for identifier S1..*IdentifierTask Instance Identifier
Slice: Unordered, Open by pattern:$this
.... identifier:tracking-id S1..1IdentifierRe-association tracking control number

Required Pattern: At least the following
..... id0..1stringUnique id for inter-element referencing
..... extension0..*ExtensionAdditional content defined by implementations
..... use0..1codeusual | official | temp | secondary | old (If known)
..... type1..1CodeableConceptDescription of identifier
Fixed Value: (complex)
...... 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: tracking-id
....... display0..1stringRepresentation defined by the system
....... userSelected0..1booleanIf this coding was chosen directly by the user
...... text0..1stringPlain text representation of the concept
..... system0..1uriThe namespace for the identifier value
..... value0..1stringThe value that is unique
..... period0..1PeriodTime period when id is/was valid for use
..... assigner0..1Reference(Organization)Organization that issued id (may be just text)
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... use ?!Σ0..1codeusual | official | temp | secondary | old (If known)
Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .

..... type Σ0..1CodeableConceptDescription of identifier
Binding: Identifier Type Codes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

..... system SΣ0..1uriThe namespace for the identifier value
Example General: http://www.acme.com/identifiers/patient
..... value SΣ1..1stringThe value that is unique
Example General: 123456
..... period Σ0..1PeriodTime period when id is/was valid for use
..... assigner Σ0..1Reference(Organization)Organization that issued id (may be just text)
... instantiatesCanonical Σ0..1canonical(ActivityDefinition)Formal definition of task
... instantiatesUri Σ0..1uriFormal definition of task
... basedOn Σ0..*Reference(Resource)Request fulfilled by this task
... 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 Σ0..1CodeableConceptE.g. "Specimen collected", "IV prepped"
Binding: (unbound) (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc.

... intent SΣ1..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..1CodeableConceptattachment-request-code | attachment-request-questionnaire
Binding: CDex Attachment 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
... focus Σ0..1Reference(Resource)What task is acting on
... for SΣ1..1Reference(CDex Patient Demographics Profile) {c}Contained Patient.
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... reference SΣC1..1stringContained resource reference
Fixed Value: #patient
.... 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 Σ0..1IdentifierLogical reference, when literal reference is not known
.... 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 C0..1dateTimeTask Creation Date
... lastModified ΣC0..1dateTimeTask Last Modified Date
... requester SΣ1..1Reference(US Core Organization Profile)Payer asking for attachments
.... 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Σ1..1IdentifierPayer 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(CDex PractitionerRole Profile) {c}Provider who submitted claim or preauthorization
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... reference SΣC1..1stringContained resource reference
Fixed Value: #practitionerrole
.... 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 Σ0..1IdentifierLogical reference, when literal reference is not known
.... display Σ0..1stringText alternative for the resource
... location Σ0..1Reference(Location)Where task occurs
... reasonCode S1..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
.... Slices for coding SΣC1..*CodingCode defined by a terminology system
Slice: Unordered, Open by value:$this
..... coding:use SΣ1..*CodingCode defined by a terminology system
Binding: CDex Claim Use Value Set (required)
...... 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
...... version Σ0..1stringVersion of the system - if relevant
...... code SΣ1..1codeclaim | preauthorization
...... display Σ0..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
.... text SΣ0..1stringclaim | preauthorization
Binding: CDex Claim Use Value Set (required)
... reasonReference S1..1Reference(Resource)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Σ1..1IdentifierClaim or Prior Authorization 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 S0..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 S0..1PeriodAttachments due date
.... recipient 0..*Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization)For whom is fulfillment sought?
... Slices for input S2..*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:code SC0..*BackboneElementAttachment Codes
..... id 0..1stringUnique id for inter-element referencing
..... extension S0..*ExtensionExtension
...... id 0..1stringUnique id for inter-element referencing
...... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
...... url S1..1uri"http://hl7.org/fhir/us/davinci-pas/StructureDefinition/extension-serviceLineNumber"
...... value[x] S1..1positiveIntValue of extension
..... 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
..