resourceType: ImplementationGuide
id: hl7.fhir.us.davinci-cdex
extension:
- url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
  valueCode: trial-use
- url: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
  valueInteger: 2
- url: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
  valueCode: claims
url: http://hl7.org/fhir/us/davinci-cdex/ImplementationGuide/hl7.fhir.us.davinci-cdex
version: 2.1.0
name: DaVinciCDex
title: Da Vinci Clinical Data Exchange (CDex)
status: active
date: '2024-11-01'
publisher: HL7 International / Payer/Provider Information Exchange Work Group
contact:
- name: HL7 International / Payer/Provider Information Exchange Work Group
  telecom:
  - system: url
    value: http://www.hl7.org/Special/committees/claims
  - system: email
    value: pie@lists.hl7.org
description: This IG provides detailed guidance that helps implementers use FHIR-based
  interactions to support specific exchanges of clinical data between providers and
  payers (or other providers).
jurisdiction:
- coding:
  - code: US
    system: urn:iso:std:iso:3166
copyright: Used by permission of HL7 International all rights reserved Creative Commons
  License
packageId: hl7.fhir.us.davinci-cdex
license: CC0-1.0
fhirVersion:
- 4.0.1
dependsOn:
- id: uscore7
  packageId: hl7.fhir.us.core
  uri: http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core
  version: 7.0.0
  extension:
  - url: http://hl7.org/fhir/5.0/StructureDefinition/extension-ImplementationGuide.dependsOn.reason
    valueMarkdown: 'Needed for systems supporting USCDI v4

      '
- id: uscore6
  packageId: hl7.fhir.us.core.v610
  uri: http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core
  version: 6.1.0
  extension:
  - url: http://hl7.org/fhir/5.0/StructureDefinition/extension-ImplementationGuide.dependsOn.reason
    valueMarkdown: 'Needed for systems supporting USCDI v3

      '
- id: uscore3
  packageId: hl7.fhir.us.core.v311
  uri: http://hl7.org/fhir/us/core/ImplementationGuide/hl7.fhir.us.core
  version: 3.1.1
  extension:
  - url: http://hl7.org/fhir/5.0/StructureDefinition/extension-ImplementationGuide.dependsOn.reason
    valueMarkdown: 'Needed for systems supporting USCDI v1

      '
- id: hrex
  packageId: hl7.fhir.us.davinci-hrex
  uri: http://hl7.org/fhir/us/davinci-hrex/ImplementationGuide/hl7.fhir.us.davinci-hrex
  version: 1.1.0
- id: pas
  packageId: hl7.fhir.us.davinci-pas
  uri: http://hl7.org/fhir/us/davinci-pas/ImplementationGuide/hl7.fhir.us.davinci-pas
  version: 2.1.0
- id: c4bb
  packageId: hl7.fhir.us.carin-bb
  uri: http://hl7.org/fhir/us/carin-bb/ImplementationGuide/hl7.fhir.us.carin-bb
  version: 2.0.0
- id: dtr
  packageId: hl7.fhir.us.davinci-dtr
  uri: http://hl7.org/fhir/us/davinci-dtr/ImplementationGuide/hl7.fhir.us.davinci-dtr
  version: 2.1.0
- id: sdc
  packageId: hl7.fhir.uv.sdc
  uri: http://hl7.org/fhir/uv/sdc/ImplementationGuide/hl7.fhir.uv.sdc
  version: 3.0.0
- id: backport
  packageId: hl7.fhir.uv.subscriptions-backport.r4
  uri: http://hl7.org/fhir/uv/subscriptions-backport/ImplementationGuide/hl7.fhir.uv.subscriptions-backport
  version: 1.1.0
definition:
  extension:
  - url: http://hl7.org/fhir/tools/StructureDefinition/ig-link-dependency
    valueCode: hl7.fhir.us.davinci-cdex#2.0.0
  - url: http://hl7.org/fhir/tools/StructureDefinition/ig-link-dependency
    valueCode: hl7.fhir.us.davinci-cdex#2.0.0-ballot
  - url: http://hl7.org/fhir/tools/StructureDefinition/ig-link-dependency
    valueCode: hl7.fhir.us.davinci-cdex#1.1.0
  - url: http://hl7.org/fhir/tools/StructureDefinition/ig-link-dependency
    valueCode: hl7.fhir.us.davinci-cdex#1.0.0
  - url: http://hl7.org/fhir/tools/StructureDefinition/ig-link-dependency
    valueCode: hl7.fhir.us.davinci-cdex#0.2.0
  - url: http://hl7.org/fhir/tools/StructureDefinition/ig-link-dependency
    valueCode: hl7.fhir.us.davinci-cdex#0.1.0
  grouping:
  - id: CapabilityStatements
    name: CDex Capability Statements
    description: The following artifacts define the specific capabilities that different
      types of systems are expected to have in order to comply with this implementation
      guide. Systems conforming to this implementation guide are expected to declare
      conformance to one or more of the following capability statements.
  - id: AttachmentsProfiles
    name: Attachments Profiles
    description: Profiles Associated with CDex Attachments Transactions
  - id: AttachmentsOperations
    name: Attachments Operations
    description: Operations Associated with CDex Attachments Transactions
  - id: AttachmentsTerminology
    name: Attachments Terminology
    description: ValueSets Associated with CDex Attachments Transactions
  - id: AttachmentsExamples
    name: Attachments Examples
    description: Examples Associated with CDex Attachments Transactions (see also
      "Signature Examples" below)
  - id: TaskBasedProfiles
    name: Task Based Approach Profiles
    description: Profiles Associated with CDex Task Based Approach Transactions
  - id: TaskBasedTerminology
    name: Task Based Approach Terminology
    description: ValueSets Associated with CDex Task Based Approach Transactions
  - id: TaskBasedExamples
    name: Task Based Approach Examples
    description: Examples Associated with CDex Task Based Approach Transactions
  - id: DirectQueryExamples
    name: Direct Query Examples
    description: Examples Associated with CDex Direct Query (FHIR RESTful search)
      Approach Transactions
  - id: QuestionnaireExamples
    name: Questionnaire Examples
    description: Questionnaire examples used in both CDex Attachments and Task Based
      Approach Transaction (see also "Signature Examples" below)
  - id: SignatureProfiles
    name: Signature Profiles
    description: Profiles Associated with CDex Signatures
  - id: SignatureTerminology
    name: Signature Terminology
    description: ValueSets Associated with CDex Signatures
  - id: SignatureExamples
    name: Signature Examples
    description: Examples Associated with CDex Signatures
  - id: CommonTerminology
    name: Common Terminology
    description: ValueSets and CodeSystems used in both CDex Attachments and Task
      Based Approach Transactions
  - id: InlineExamples
    name: Inline Examples
    description: These examples are used in the inline example scenarios throughout
      the guide. They are listed here so the implementation guide's publication tooling
      can validate them against the CDex profile definitions.  Since they are used
      to illustrate "over-the-wire" transactions, the rendered narrative and id elements
      are often absent.
  resource:
  - reference:
      reference: CapabilityStatement/data-consumer-client
    description: "This CapabilityStatement describes the expected capabilities of\
      \ a Da Vinci CDex Data Consumer  in *Client* mode when requesting clinical data\
      \ from the Data Source  during clinical data exchange. The capabilities include\
      \ one or more of the following interactions:\n\n1. Requesting and Fetching Clinical\
      \ Data using a FHIR RESTful query\n2. Requesting and Fetching Clinical Data\
      \ using a Task-based query including:\n   -  Polling or Subscribing for Task\
      \ update notifications\n3. Requesting Attachments\n   - Requesting Attachments\
      \ Using Attachments Codes\n   - Requesting Attachments Using Questionnaires"
    exampleBoolean: false
    name: Data Consumer Client CapabilityStatement
    groupingId: CapabilityStatements
  - reference:
      reference: CapabilityStatement/data-consumer-server
    description: 'This CapabilityStatement describes the expected capabilities of
      a Da Vinci CDex Data Consumer  in *Server* mode when responding to a  Data Source   or
      one of its proxies during clinical data exchange.   The capabilities include
      one or more of the following interactions:


      1. Responding to a query for authorization information represented by a CommunicationRequest
      or ServiceRequest

      1. Responding to  the `$submit-attachment` operation.'
    exampleBoolean: false
    name: Data Consumer Server CapabilityStatement
    groupingId: CapabilityStatements
  - reference:
      reference: CapabilityStatement/data-source-client
    description: 'This CapabilityStatement describes the expected capabilities of
      a Da Vinci CDex Data Source  in *Client* mode during clinical data exchange
      with a Data Consumer. The capabilities include one or more of the following
      interactions:

      1. Post the `$submit-attachment` operation to a Data Consumer endpoint.

      2. Launch Da Vinci DTR.

      3. Query for Authorization information represented by a CommunicationRequest
      or ServiceRequest.

      4. Post a subscription notification to a Data Consumer endpoint updating the
      status of a task.'
    exampleBoolean: false
    name: Data Source Client CapabilityStatement
    groupingId: CapabilityStatements
  - reference:
      reference: CapabilityStatement/data-source-server
    description: "This CapabilityStatement describes the expected capabilities of\
      \ a Da Vinci CDex Data Source in *Server* mode when responding to a Data Consumer\
      \ during clinical data exchange. The capabilities include one or more of the\
      \ following interactions:\n\n1. Responding to a FHIR RestFul Query for Clinical\
      \ Data \n2. Responding to a Task-based query request for clinical data\nincluding:\n\
      \   -  Polling or Subscription requests for Task update notifications\n1. Responding\
      \ to\n   - Requesting Attachments Using Attachments Codes\n   - Requesting Attachments\
      \ Using Questionnaires"
    exampleBoolean: false
    name: Data Source Server CapabilityStatement
    groupingId: CapabilityStatements
  - reference:
      reference: StructureDefinition/cdex-task-attachment-request
    description: 'Payers use this [Task](http://hl7.org/StructureDefinition/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 and X12 standard
      codes. It also supports requests for more detailed missing data using Questionnaire,
      CQL, and QuestionnaireResponse, as supported by [Da Vinci Documentation Templates
      and Rules (DTR)](http://hl7.org/fhir/us/davinci-dtr/index.html).

      '
    exampleBoolean: false
    name: CDex Task Attachment Request Profile
    groupingId: AttachmentsProfiles
  - reference:
      reference: StructureDefinition/cdex-practitionerrole
    description: 'This Profile is defined as a [contained](http://hl7.org/fhir/R4/references.html)
      resource within the CDex Task Attachment Request Profile.  It is referenced
      by `Task.owner` to communicate the provider ID as a unique organization/location
      identifier (e.g., Type 2 NPI), or unique provider identifier (e.g., Type 1 NPI),
      or both. It constrains the following elements to be [*must support*](attachments-conformance.html#cdex-must-support-definition)
      (min=0).:


      - A default resource ID of "practitionerrole"

      - A `practitioner.identifier`

      - An `organization.identifier`


      At least a practitioner identifier or organization identifier **SHALL** be present.'
    exampleBoolean: false
    name: CDex PractitionerRole Profile
    groupingId: AttachmentsProfiles
  - reference:
      reference: StructureDefinition/cdex-patient-demographics
    description: "This Profile is defined as a [contained](http://hl7.org/fhir/R4/references.html)\
      \ resource within the CDex Task Attachment Request Profile or CDex Task Data\
      \ Request Profile.  It is referenced when additional patient demographic data\
      \ is communicated for a clinical data request (such as verifying patient identity\
      \ for HIPAA compliance regulations).  It constrains the following elements to\
      \ be *mandatory* (min=1):\n\n- A default resource ID of \"patient\"\n- A member\
      \ ID identifier [slice](https://hl7.org/fhir/R4/profiling.html#slicing)\n- A\
      \ patient's name\n\nand the following element to be [*must support*](attachments-conformance.html#cdex-must-support-definition)\
      \ (min=0):\n\n- A patient account number identifier slice  \n- A date of birth"
    exampleBoolean: false
    name: CDex Patient Demographics Profile
    groupingId: AttachmentsProfiles
  - reference:
      reference: StructureDefinition/cdex-parameters-submit-attachment
    description: The Parameters profile for Da Vinci [Submit Attachment Operation](OperationDefinition-submit-attachment.html)
    exampleBoolean: false
    name: CDex Parameters Submit Attachment Profile
    groupingId: AttachmentsProfiles
  - reference:
      reference: OperationDefinition/submit-attachment
    description: Providers use this [operation](http://hl7.org/fhir/operations.html)
      to submit *solicited* and *unsolicited* attachments or additional information
      for claims or prior authorization. The $submit-attachment operation accepts
      the clinical/administrative attachments and the information required to associate
      them with the claim or prior authorization and returns an HTTP response. For
      *unsolicited* attachments, the Provider invokes this operation *before, concurrently,
      or after*  the claim or pre-authorization transaction. For *solicited* attachments,
      the Provider invokes it when responding to a Payer request for attachments or
      additional information. Any HTTP endpoint can use $submit-attachment, not just
      FHIR RESTful server endpoints. Implementers of CDex's *Unsolicited* Attachments
      **SHOULD** support the [Endpoint Discovery Strategy](https://hl7.org/fhir/us/davinci-hrex/STU1.1/endpoint-discovery.html)
      defined in the Da Vinci HRex specification to allow discovery of the endpoint
      for this operation. For *Solicited Attachments*, the $submit-attachment endpoint
      is supplied in the [CDex Task Attachment Request Profile](http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request)
    exampleBoolean: false
    name: Submit Attachment Operation
    groupingId: AttachmentsOperations
  - reference:
      reference: ValueSet/cdex-claim-use
    description: The purpose of a Claim resource and the reason for attachments. It
      includes the codes "preauthorization" and "claim".
    exampleBoolean: false
    name: CDex Claim Use Value Set
    groupingId: AttachmentsTerminology
  - reference:
      reference: ValueSet/cdex-loinc-attachment-codes
    description: This value set includes LOINC terms that can be sent by a payer as
      part of an HL7 attachment request for additional information. It has been curated
      by the HL7 Payer/Provider Information Exchange (PIE) Work Group.  More information
      about using LOINC in HIPAA attachments and the source of this value set can
      be found at [LOINC Attachments](https://loinc.org/attachments/).
    exampleBoolean: false
    name: CDex LOINC Attachment Codes Value Set
    groupingId: AttachmentsTerminology
  - reference:
      reference: ValueSet/cdex-pwk01-attachment-report-type-code
    description: 'In addition to using LOINC attachment codes, a payer may request
      for additional information from the provider to support a prior authorization
      request using X12''s PWK01 Attachment Report Type Code.


      Note that the PWK01 codes will not be published in due to X12 IP restrictions.

      '
    exampleBoolean: false
    name: CDex PWK01 Attachment Report Type Code Value Set
    groupingId: AttachmentsTerminology
  - reference:
      reference: Task/cdex-task-example19
    description: '**Claim Attachment Request Example:**   Claim Attachment Request
      sent by payer to a provider requesting a signed Progress note (H&P) note'
    name: CDex Task Example 19
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request
    groupingId: AttachmentsExamples
  - reference:
      reference: Task/cdex-task-example20
    description: '**Prior-Auth Attachment Request Example:**   Prior Authorization
      Attachment Request with a POU of "coverage authorization" sent by payer to a
      provider requesting a signed History and physical (H&P) note.'
    name: CDex Task Example 20
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request
    groupingId: AttachmentsExamples
  - reference:
      reference: Task/cdex-task-example22
    description: '**Request Additional Data using a Questionnaire:**   Prior Authorization
      Attachment Request with a POU of "coverage authorization" sent by payer to a
      provider requesting a data request questionnaire be completed.'
    name: CDex Task Example 22
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request
    groupingId: AttachmentsExamples
  - reference:
      reference: Task/cdex-task-example23
    description: '**Request Additional Data using an Adaptive Questionnaire:**  Prior
      Authorization Attachment Request with a POU of "coverage authorization" sent
      by payer to a provider requesting an adaptive questionnaire be completed.'
    name: CDex Task Example 23
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request
    groupingId: AttachmentsExamples
  - reference:
      reference: Task/cdex-task-example24
    description: '**Completed Request for Additional Data using a Questionnaire:**   Completed
      Task for CDex Task Example 22. This example has a status of "completed" and
      a "lastModified" date of 6/17/2022. The "reasonCode" is "request additional
      data" and the "output" is a QuestionnaireResponse.'
    name: CDex Task Example 24
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request
    groupingId: AttachmentsExamples
  - reference:
      reference: Task/cdex-task-example25
    description: '**Completed Request for Additional Data Using an Adaptive Questionnaire:**  Completed
      Task for CDex Task Example 23. This example has a status of "completed" and
      a "lastModified" date of 6/17/2022. The "reasonCode" is "request additional
      data" and the "output" is a QuestionnaireResponse.'
    name: CDex Task Example 25
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request
    groupingId: AttachmentsExamples
  - reference:
      reference: Task/cdex-task-example28
    description: '**Request Additional Data Requiring a Verification Signature Using
      a Questionnaire:** Prior Authorization Attachment Request with a POU of "coverage
      authorization" and Signature required sent by payer to a provider requesting
      a data request questionnaire be completed and signed.'
    name: CDex Task Example 28
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request
    groupingId: AttachmentsExamples
  - reference:
      reference: Task/cdex-task-example29
    description: '**Completed Request for Additional Data Requiring a Verification
      Signature Using a Questionnaire:**  Completed Prior Authorization Attachment
      Request (CDex Task Example 28) with a status of "completed" and output referencing
      the digitally signed QuestionnaireResponse.'
    name: CDex Task Example 29
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request
    groupingId: AttachmentsExamples
  - reference:
      reference: Parameters/cdex-parameters-example1
    description: '**CCDA Attachment Example:** Parameters Resource example showing
      how it is used to submit attachments using the `$submit-attachment` operation.
      It contains a CCDA attachment and the necessary information needed to associate
      them to the claim.'
    name: CDex Parameters Example 1
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-parameters-submit-attachment
    groupingId: AttachmentsExamples
  - reference:
      reference: Parameters/cdex-parameters-example3
    description: '**PDF Attachment Example:** Parameters Resource example showing
      how it is used to submit attachments using the `$submit-attachment` operation.
      It contains a PDF attachment and the necessary information needed to associate
      them to the claim.'
    name: CDex Parameters Example 3
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-parameters-submit-attachment
    groupingId: AttachmentsExamples
  - reference:
      reference: Parameters/cdex-parameters-example4
    description: '**Laboratory Results Attachment Example:** Parameters Resource example
      showing how it is used to submit multiple attachments using the `$submit-attachment`
      operation. It contains 3 Hemoglobin A1c results as attachments and the necessary
      information needed to associate them to the claim.'
    name: CDex Parameters Example 4
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-parameters-submit-attachment
    groupingId: AttachmentsExamples
  - reference:
      reference: Parameters/cdex-parameters-example5
    description: '**Completed QuestionnaireResponse Attachment Example:** Parameters
      Resource example showing how it is used to submit a solicited attachment using
      the `$submit-attachment` operation for a prior authorization. The attachment
      parameter payload is a QuestionnaireResponse completed using DTR in response
      to a Questionnaire sent in the Attachments request.'
    name: CDex Parameters Example 5
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-parameters-submit-attachment
    groupingId: AttachmentsExamples
  - reference:
      reference: StructureDefinition/cdex-task-data-request
    description: 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.
    exampleBoolean: false
    name: CDex Task Data Request Profile
    groupingId: TaskBasedProfiles
  - reference:
      reference: ValueSet/cdex-work-queue
    description: The set work queue tags that the provider may use in their workflow
      to process requests. This code set is composed of codes defined by this Guide.
    exampleBoolean: false
    name: CDex Work Queue Value Set
    groupingId: TaskBasedTerminology
  - reference:
      reference: ValueSet/cdex-data-request-task-code
    description: "Codes used to identify the type of data request. It includes the\
      \ codes \u201Cdata-request-query\u201D, \u201Cdata-request-code\u201D, and \u201C\
      data-request-questionnaire\u201D."
    exampleBoolean: false
    name: CDex Data Request Task Code Value Set
    groupingId: TaskBasedTerminology
  - reference:
      reference: Task/cdex-task-example1
    description: '**Query String Request for Condition:** Task to seek a patient''s
      active conditions using the CDex Profile query input. This example illustrates
      the use of business identifiers (instead of pointing to a FHIR resource) to
      references the various actors.'
    name: CDex Task Example 1
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example2
    description: '**Completed Query String Request for Condition:**   Completed Task
      to seek a patient active conditions using the CDex Profile query input. This
      example illustrates the use of business identifiers (instead of pointing to
      a FHIR resource) to references the various actors.'
    name: CDex Task Example 2
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example3
    description: '**Completed Query String Request for Condition with Contained Output:**   Completed
      Task to seek a patient active conditions using the CDex Profile query input
      and using a contained resource for the output data. This example illustrates
      the use of business identifiers (instead of pointing to a FHIR resource) to
      references the various actors.'
    name: CDex Task Example 3
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example4
    description: '**Free Text Request for Condition:**   Task to seek a patient active
      conditions using free text in the CDex Profile code input. This example illustrates
      the use of business identifiers (instead of pointing to a FHIR resource) to
      references the various actors.'
    name: CDex Task Example 4
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example5
    description: '**Completed Free Text Request for Condition:**   Completed Task
      to seek a patient active conditions using free text for the input in the CDex
      Profile code input. This example illustrates the use of business identifiers
      (instead of pointing to a FHIR resource) to references the various actors.'
    name: CDex Task Example 5
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example6
    description: '**Coded Request for Progress note:**   Task to seek a patient''s
      latest Progress notes using the CDex Profile code input. This example illustrates
      the use of FHIR resource references to the various actors.'
    name: CDex Task Example 6
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example7
    description: '**Completed Coded Request for Progress note - PDF:**   Completed
      Task to seek a patient''''''''s latest Progress notes using the CDex Profile
      code input. This example illustrates the use of FHIR resource references to
      the various actors. The output data is a contained DocumentReference with an
      inline base64 encoded PDF document.'
    name: CDex Task Example 7
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example8
    description: '**Completed Coded RequestOperative note -CCDA:**   Completed Task
      to seek a patient''s Operative notes using the CDex Profile code input. This
      example illustrates the use of FHIR resource references to the various actors.
      The output data is a contained DocumentReference with an inline base64 encoded
      CCDA document.'
    name: CDex Task Example 8
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example9
    description: '**Failed Coded Request for A1C Results:**  Task to seek a patient''s
      HbA1c test results using the CDex Profile query input with a failed status.
      This example illustrates the use of FHIR resource references to the various
      actors.'
    name: CDex Task Example 9
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example10
    description: '**Coded Request for A1C Results:**   Task to seek a patient''s HbA1c
      test results using the CDex Profile query input. This example illustrates the
      use of FHIR resource references to the various actors.'
    name: CDex Task Example 10
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example11
    description: '**Query String Request for Condition with Authorization:**  In this
      provider to provider request, a Task is used to request a patient active conditions
      using the CDex Profile query input.  A reference to a formal authorization is
      provided.  This example illustrates the use of business identifiers (instead
      of pointing to a FHIR resource) to references the various actors.'
    name: CDex Task Example 11
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example12
    description: '**Completed Query String Request for Condition with Authorization:**
      In this completed provider to provider request, a Task is used to request a
      patient active conditions using the CDex Profile query input.  A reference to
      a formal authorization is provided.  This example illustrates the use of business
      identifiers (instead of pointing to a FHIR resource) to references the various
      actors.'
    name: CDex Task Example 12
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example13
    description: '**Free Text Request for Condition with Provenance:**   Task to seek
      a patient active conditions and its provenance using free text in the CDex Profile
      code input. This example illustrates the use of  business identifiers (instead
      of pointing to a FHIR resource) to references the various actors.'
    name: CDex Task Example 13
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example14
    description: '**Completed Free Text Request for Condition with Provenance:**   Completed
      Task to seek a patient active conditions and its provenance using free text
      in the CDex Profile code input. This example illustrates the use of business
      identifiers (instead of pointing to a FHIR resource) to references the various
      actors.'
    name: CDex Task Example 14
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example15
    description: '**Query String Request for Condition with Provenance:**  Task to
      seek a patient active conditions and its provenance using query string in the
      CDex Profile query input. This example illustrates the use of  business identifiers
      (instead of pointing to a FHIR resource) to references the various actors.'
    name: CDex Task Example 15
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example16
    description: '**Completed Query String Request for Condition with Provenance:**   Completed
      Task to seek a patient active conditions their provenance using the CDex Profile
      query input. This example illustrates the use of business identifiers (instead
      of pointing to a FHIR resource) to references the various actors.'
    name: CDex Task Example 16
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example17
    description: '**Query String Request for Signed Condition Data:**   Task to seek
      a patient active conditions using the CDex Profile query input and using the
      signature input to indicate a signature is required. This example illustrates
      the use of business identifiers (instead of pointing to a FHIR resource) to
      references the various actors.'
    name: CDex Task Example 17
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example18
    description: '**Completed Query String Request for Signed Condition Data:**   Completed
      Task to seek a *signed* patient active conditions. This example illustrates
      the use of business identifiers (instead of pointing to a FHIR resource) to
      references the various actors.'
    name: CDex Task Example 18
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example21
    description: '**Coded Request for Surgical Operation Note:**   Task to seek a
      patient''s latest operative notes using the CDex Profile code input. This example
      illustrates the use of FHIR resource references to the various actors.'
    name: CDex Task Example 21
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example26
    description: '**Data Request Using a Questionnaire:** Task to seek reason for
      home oxygen therapy using the CDex Profile questionnaire input. This example
      illustrates the use of Questionnaire to request data from a data source'
    name: CDex Task Example 26
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example27
    description: '**Completed Data Request Using a Questionnaire:** Completed Task
      for CDex Task Example 26. This example has a status of "completed" and a "lastModified"
      date of 6/19/2022. The "output" is a QuestionnaireResponse.Task to seek reason
      for home oxygen therapy.'
    name: CDex Task Example 27
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example30
    description: '**Data Request Requiring a Verification Signature Using Questionnaire:**
      Task to seek reason for home oxygen therapy using the CDex Profile questionnaire
      input. This example illustrates the use of Questionnaire to request data from
      a data source and requires a digitally signed QuestionnaireResponse.'
    name: CDex Task Example 30
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Task/cdex-task-example31
    description: '**Completed Data Request Requiring a Verification Signature Using
      Questionnaire:** Completed Task (CDex Task Example 30) with a status of "completed"
      and output referencing the digitally signed QuestionnaireResponse.'
    name: CDex Task Example 31
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: TaskBasedExamples
  - reference:
      reference: Bundle/cdex-searchbundle-scenario1-example
    description: Bundle example used in direct query transactions [scenario 1](direct-query.html#scenario-1)
      and in task based transactions - for example, [scenario 1a](task-based-approach.html#scenario-1).
    name: Direct Query for Patient's Active Conditions
    exampleBoolean: true
    groupingId: DirectQueryExamples
  - reference:
      reference: Bundle/cdex-searchbundle-provenance-example
    description: Bundle example used in the [direct query scenario](direct-query.html#provenance)
      that includes the corresponding Provenance records. Payer Seeks Insured Person/Patient
      Active Conditions from Provider to support a claims audit.
    name: Direct Query Response Including Provenance
    exampleBoolean: true
    groupingId: DirectQueryExamples
  - reference:
      reference: Bundle/cdex-searchbundle-scenario3-example
    description: Bundle example used in direct query [scenario 3](direct-query.html#scenario-3).
      Payer Seeks Insured Person/Patient Progress Notes from Provider to support a
      claim submission.
    name: Direct Query for Patient's Progress Notes
    exampleBoolean: true
    groupingId: DirectQueryExamples
  - reference:
      reference: Bundle/cdex-searchbundle-scenario2-example
    description: Bundle example used in direct query [scenario 2](direct-query.html#scenario-2).
      Payer Seeks Insured Person/Patient HbA1c Test Results from Provider
    name: Direct Query for Patient's HbA1c Test Results
    exampleBoolean: true
    groupingId: DirectQueryExamples
  - reference:
      reference: Questionnaire/cdex-questionnaire-example1
    description: This example is a simple data request Questionnaire used in the Task
      Based and Attachments transactions. It is adapted from the Da Vinci DTR IG.
    name: CDex Questionnaire Example1
    exampleCanonical: http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-std-questionnaire
    groupingId: QuestionnaireExamples
  - reference:
      reference: QuestionnaireResponse/cdex-questionnaireresponse-example1
    description: This Questionnaire Response example demonstrates the response to
      a CDEX Data Query or Attachments that uses a Questionnaire to request the data.  It
      is adapted from the Da Vinci DTR IG.
    name: CDex QuestionnaireResponse Example1
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-sdc-questionnaireresponse
    groupingId: QuestionnaireExamples
  - reference:
      reference: QuestionnaireResponse/cdex-questionnaireresponse-example2
    description: This Questionnaire Response example demonstrates the response to
      a CDEX Data Query or Attachments that uses a Questionnaire to request the data.
      The Questionnaire is an adaptive questionnaire and the resulting QuestionnaireResponse
      contains the generated Questionnaire instance.  This example is adapted from
      the Da Vinci DTR IG. For more information about adaptive questionnaires in FHIR
      see the [SDC Implementation Guide](http://hl7.org/fhir/uv/sdc/).
    name: CDex QuestionnaireResponse Example2
    exampleCanonical: http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse-adapt
    groupingId: QuestionnaireExamples
  - reference:
      reference: StructureDefinition/cdex-digital-signature
    description: This Signature DataType profile enforces the various elements of
      digital signatures documented in [Digital Signature Rules and Guidance For CDEX
      Bundle and QuestionnaireResponse](https://hl7.org/fhir/us/davinci-cdex/signatures.html#digital-signature-rules-and-guidance-for-cdex-bundle-and-questionnaireresponse).
    exampleBoolean: false
    name: CDex Digital Signature Profile
    groupingId: SignatureProfiles
  - reference:
      reference: StructureDefinition/cdex-signature-bundle
    description: "This Bundle profile supports the signatures as documented in the\
      \ CDex guide. It adds the following *mandatory* (min=1) constraint:\n\n- A `Bundle.signature`\
      \ element using:\n  1. The [CDex Digital Signature Profile](https://hl7.org/fhir/us/davinci-cdex/StructureDefinition-cdex-digital-signature.html)\
      \ for digital signatures\n  1. The base Signature datatype for other electronic\
      \ signatures (picture, etc)"
    exampleBoolean: false
    name: CDex Signature Bundle Profile
    groupingId: SignatureProfiles
  - reference:
      reference: StructureDefinition/cdex-sdc-questionnaireresponse
    description: "This profile is derived from the [US Core QuestionnaireResponse\
      \ Profile](https://hl7.org/fhir/us/core/STU6.1/StructureDefinition-us-core-questionnaireresponse.html)\
      \ profile and enforces the various elements of [signature](https://hl7.org/fhir/us/davinci-cdex/signatures.html)\
      \ documented in the CDex guide. It adds the following constraints:\n- The signature\
      \ extensions use using:\n  1. The [CDex Digital Signature Profile](https://hl7.org/fhir/us/davinci-cdex/StructureDefinition-cdex-digital-signature.html)\
      \ for digital signatures\n  1. The base Signature datatype for other electronic\
      \ signatures (picture, etc)"
    exampleBoolean: false
    name: CDex SDC QuestionnaireResponse Profile
    groupingId: SignatureProfiles
  - reference:
      reference: ValueSet/cdex-identifier-types
    description: "Identifier types for providers and organizations. It includes the\
      \ codes \u201CTAX\u201D and \u201CNPI\u201D."
    exampleBoolean: false
    name: CDex Identifier Types Value Set
    groupingId: SignatureTerminology
  - reference:
      reference: Bundle/cdex-searchbundle-digital-sig-example
    description: Digital signature example showing how it is used to sign a [search
      set Bundle ](direct-query.html#signatures).  The CDEX use case would be a response
      to a Direct Query where a digital signature was required.
    name: CDEX SearchSet Bundle with Digital Signature Example
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-signature-bundle
    groupingId: SignatureExamples
  - reference:
      reference: Bundle/cdex-document-digital-sig-example
    description: Digital signature example showing how it is used to sign a FHIR Document.  The
      CDEX use case would be the target resource in response to a Task-based request
      where a digital signature was required.  If no signature was required, the response
      would typically be in the form of an individual resource.
    name: CDEX Document with Digital Signature Example
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-signature-bundle
    groupingId: SignatureExamples
  - reference:
      reference: Bundle/cdex-electronic-sig-example
    description: Electronic signature example showing how an image file can be used
      to sign a document Bundle.  The CDEX use case would be the target resource in
      response to a Task-based request where an electronic signature was required.  If
      no signature was required, the response would typically be in the form of an
      individual resource.
    name: CDEX Document with Electronic Signature Example
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-signature-bundle
    groupingId: SignatureExamples
  - reference:
      reference: Parameters/cdex-parameters-example2
    description: '**Signed FHIR Document Attachment Example:** Parameters Resource
      example showing how it is used to submit attachments using the `$submit-attachment`
      operation. It contains a Signed FHIR Document attachment and the necessary information
      needed to associate it to a claim.'
    name: CDex Parameters Example 2
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-parameters-submit-attachment
    groupingId: SignatureExamples
  - reference:
      reference: Questionnaire/cdex-questionnaire-example2
    description: This example is a simple data request Questionnaire used in the Task
      Based and Attachments transactions. It indicates that a verification signature
      is needed when completing the QuestionnaireResponse.  It is adapted from the
      Da Vinci DTR IG.
    name: CDex Questionnaire Example2
    exampleCanonical: http://hl7.org/fhir/us/davinci-dtr/StructureDefinition/dtr-std-questionnaire
    groupingId: SignatureExamples
  - reference:
      reference: QuestionnaireResponse/cdex-questionnaireresponse-example3
    description: This Questionnaire Response example demonstrates the response to
      a CDEX Data Query or Attachments that uses a Questionnaire to request the data
      when an electronic verification signature is required. It is adapted from the
      Da Vinci DTR IG.  The electronic signature is an image file in the QuestionnaireResponse
      signature extension. This example is adapted from the Da Vinci DTR IG.
    name: CDex QuestionnaireResponse Example3
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-sdc-questionnaireresponse
    groupingId: SignatureExamples
  - reference:
      reference: QuestionnaireResponse/cdex-questionnaireresponse-example4
    description: This Questionnaire Response example demonstrates the response to
      a CDEX Data Query or Attachments that uses a Questionnaire to request the data
      and an electronic *digital* Verification signature is required. It is adapted
      from the Da Vinci DTR IG. The digital signature is a JSON [FHIR Signature](http://hl7.org/fhir/R4/signatures.html)
      in the QuestionnaireResponse signature extension. This example is adapted from
      the Da Vinci DTR IG.
    name: CDex QuestionnaireResponse Example4
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-sdc-questionnaireresponse
    groupingId: SignatureExamples
  - reference:
      reference: ValueSet/cdex-POU
    description: The set of purpose of use (POU) codes for requesting data. This code
      set is composed of [FHIR core Purpose of Use security labels](http://hl7.org/fhir/security-labels.html#core)
      and additional codes defined by this Guide.
    exampleBoolean: false
    name: CDex Purpose of Use Value Set
    groupingId: CommonTerminology
  - reference:
      reference: CodeSystem/cdex-temp
    description: Codes temporarily defined as part of the CDex implementation guide.  These
      will eventually migrate into an officially maintained terminology (likely HL7's
      [UTG](https://terminology.hl7.org/codesystems.html) code systems).
    exampleBoolean: false
    name: CDex Temporary Code System
    groupingId: CommonTerminology
  - reference:
      reference: Task/cdex-task-inline-example1
    description: Task example used to create inline scenarios for example tasked-based
      transactions based in scenarios [1a](task-based-approach.html#fhir-restful-query-syntax),
      [1c](task-based-approach.html#contained-task-outputs) and [4](task-based-approach.html#example-task-based-transaction-using-subscription).
    name: CDex Inline Task Example 1
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: InlineExamples
  - reference:
      reference: Task/cdex-task-inline-example4
    description: Task example used to create [example task based transactions using
      free text inputs](task-based-approach.html#free-text)
    name: CDex Inline Task Example 4
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: InlineExamples
  - reference:
      reference: Task/cdex-task-inline-example6
    description: Task example used to create inline task based scenario for [progress
      note exam notes as PDF](task-based-approach.html#progress-note-exam-notes-as-pdf)
    name: CDex Task Inline Example 6
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: InlineExamples
  - reference:
      reference: Task/cdex-task-inline-example21
    description: Task example used to create inline task based scenarios for [surgical
      notes as ccda documents](task-based-approach.html#surgical-notes-as-ccda-documents)
    name: CDex Inline Task Example 21
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: InlineExamples
  - reference:
      reference: Task/cdex-task-inline-example10
    description: Task example used to create inline task based scenarios for and [example
      unsuccessful task based transaction](task-based-approach.html#example-unsuccessful-task-based-transaction)
    name: CDex Inline Task Example 10
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: InlineExamples
  - reference:
      reference: Task/cdex-task-inline-example11
    description: Task example used to create inline scenarios for [task based transaction
      with a formal authorization](task-based-approach.html#formal-authorization).
    name: CDex Inline Task Example 11
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: InlineExamples
  - reference:
      reference: Task/cdex-task-inline-example13
    description: Task example used to create inline [requests for provenance using
      task based transaction](task-based-approach.html#example-requests-for-provenance-using-task-based-transaction)
    name: CDex Inline Task Example 13
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: InlineExamples
  - reference:
      reference: Task/cdex-task-inline-example15
    description: Task example used to create inline [requests for provenance using
      task based transaction](task-based-approach.html#example-requests-for-provenance-using-task-based-transaction)
    name: CDex Inline Task Example 15
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: InlineExamples
  - reference:
      reference: Task/cdex-task-inline-example17
    description: Task example used to create inline scenarios for a [signed task based
      transaction](task-based-approach.html#example-of-a-signed-task-based-transaction)
    name: CDex Inline Task Example 17
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: InlineExamples
  - reference:
      reference: Task/cdex-task-inline-example19
    description: Task example used to create inline scenarios for the [requesting
      attachments using codes transaction](requesting-attachments-code.html#complete-solicited-attachment-transaction)
    name: CDex Inline Task Example 19
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request
    groupingId: InlineExamples
  - reference:
      reference: Task/cdex-task-inline-example22
    description: Task example used to create inline [requesting attachments using
      questionnaire transaction](requesting-attachments-questionnaire.html#complete-solicited-attachment-transaction)
    name: CDex Inline Task Example 22
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-attachment-request
    groupingId: InlineExamples
  - reference:
      reference: Task/cdex-task-inline-example26
    description: Task example used to create inline task based scenarios [using questionnaire
      as task input](task-based-approach.html#using-questionnaire-as-task-input)
    name: CDex Inline Task Example 26
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-task-data-request
    groupingId: InlineExamples
  - reference:
      reference: Subscription/cdex-task-inline-scenario1-subscription-requested
    description: Subscription example used to create inline scenarios for the [example
      task based transaction using subscription](task-based-approach.html#example-task-based-transaction-using-subscription)
    name: Inline Subscription Task Scenario1 Subscription Requested
    exampleCanonical: http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription
    groupingId: InlineExamples
  - reference:
      reference: Subscription/cdex-task-inline-scenario1-subscription-active
    description: Subscription example used to create inline scenarios for the [example
      task based transaction using subscription](task-based-approach.html#example-task-based-transaction-using-subscription)
    name: Inline Subscription Task Scenario1 Subscription Active
    exampleCanonical: http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription
    groupingId: InlineExamples
  - reference:
      reference: Bundle/cdex-task-inline-scenario1-subscription-notification
    description: Notification Bundle example used to create inline scenarios for the
      [example task based transaction using subscription](task-based-approach.html#example-task-based-transaction-using-subscription)
    name: Inline Subscription Task Scenario1 Subscription Notification
    exampleCanonical: http://hl7.org/fhir/uv/subscriptions-backport/StructureDefinition/backport-subscription-notification-r4
    groupingId: InlineExamples
  - reference:
      reference: Bundle/cdex-bundle-inline-example-858p
    description: Bundle example used to create inline [requests for provenance using
      task based transaction](task-based-approach.html#example-requests-for-provenance-using-task-based-transaction)
    name: CDex Bundle Inline Example 858p
    exampleBoolean: true
    groupingId: InlineExamples
  - reference:
      reference: Condition/cdex-condition-inline-example-858
    description: Condition example used to create inline scenarios for this guide
    name: CDex Condition Inline Example 858
    exampleCanonical: http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-problems-health-concerns
    groupingId: InlineExamples
  - reference:
      reference: Provenance/cdex-provenance-inline-example-858
    description: Provenance example used to create inline scenarios for this guide
    name: CDex Provenance Inline Example 858
    exampleCanonical: http://hl7.org/fhir/us/core/StructureDefinition/us-core-provenance
    groupingId: InlineExamples
  - reference:
      reference: CommunicationRequest/cdex-task-inline-communicationrequest-example1
    description: CommunicationRequest example used to create inline scenarios for
      this guide.
    name: Inline CDex Task Inline Communicationrequest Example 1
    exampleBoolean: true
    groupingId: InlineExamples
  - reference:
      reference: QuestionnaireResponse/cdex-questionnaireresponse-inline-example1
    description: QuestionnaireResponse example example used to create inline task
      based scenarios [using questionnaire as task input](task-based-approach.html#using-questionnaire-as-task-input)
    name: CDex Questionnaireresponse Inline Example 1
    exampleCanonical: http://hl7.org/fhir/us/davinci-cdex/StructureDefinition/cdex-sdc-questionnaireresponse
    groupingId: InlineExamples
  - reference:
      reference: OperationOutcome/cdex-operationoutcome-inline-example1
    description: OperationOutcome example used to create inline scenarios for this
      guide
    name: CDex Inline OperationOutcome Example 1
    exampleBoolean: true
    groupingId: InlineExamples
  - reference:
      reference: CapabilityStatement/cdex-capabilitystatement-inline-example
    description: R4 example of a CapabilityStatement advertising support for CDex
      Task Update topic-based subscription
    name: cdex-capabilitystatement-inline-example
    exampleBoolean: true
    groupingId: InlineExamples
  page:
    nameUrl: toc.html
    title: Table of Contents
    generation: html
    page:
    - nameUrl: index.html
      title: IG Home
      generation: markdown
    - nameUrl: background.html
      title: Background
      generation: markdown
      extension:
      - url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
        valueCode: trial-use
    - nameUrl: direct-query.html
      title: Direct Query
      generation: markdown
      extension:
      - url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
        valueCode: trial-use
    - nameUrl: task-based-approach.html
      title: Task Based Approach
      generation: markdown
      extension:
      - url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
        valueCode: trial-use
      page:
      - nameUrl: task-based-conformance.html
        title: Conforming to CDex Task Based Approach
        generation: markdown
        extension:
        - url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
          valueCode: trial-use
    - nameUrl: attachments.html
      title: Attachments
      generation: markdown
      page:
      - nameUrl: solicited-unsolicited-attachments.html
        title: Solicited and Unsolicited Attachments
        generation: markdown
      - nameUrl: sending-attachments.html
        title: Sending Attachments
        generation: markdown
        extension:
        - url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
          valueCode: trial-use
      - nameUrl: requesting-attachments-code.html
        title: Requesting Attachments Using Attachments Codes
        generation: markdown
        extension:
        - url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
          valueCode: trial-use
      - nameUrl: requesting-attachments-questionnaire.html
        title: Requesting Attachments Using Questionnaires
        generation: markdown
        extension:
        - url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
          valueCode: trial-use
      - nameUrl: burden-reduction.html
        title: Using CDex Attachments with DaVinci PAS
        generation: markdown
      - nameUrl: attachments-conformance.html
        title: Conforming to CDex Attachments
        generation: markdown
        extension:
        - url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
          valueCode: trial-use
    - nameUrl: signatures.html
      title: Signatures
      generation: markdown
      extension:
      - url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
        valueCode: trial-use
      page:
      - nameUrl: signed-searchset-bundle-example.html
        title: 'Worked Example: Signed Searchset Bundle'
        generation: markdown
        extension:
        - url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
          valueCode: informative
      - nameUrl: signed-document-bundle-example.html
        title: 'Worked Example: Signed Document Bundle'
        generation: markdown
        extension:
        - url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
          valueCode: informative
    - nameUrl: security.html
      title: Security and Privacy
      generation: markdown
      extension:
      - url: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
        valueCode: trial-use
    - nameUrl: downloads.html
      title: Downloads
      generation: markdown
    - nameUrl: ImplementationGuide-hl7.fhir.us.davinci-cdex.html
      title: CDex ImplementationGuide Resource
      generation: markdown
    - nameUrl: changes.html
      title: Change Log
      generation: markdown
  parameter:
  - code: copyrightyear
    value: 2024+
  - code: releaselabel
    value: STU 2.1
  - code: path-resource
    value: input/resources
  - code: path-resource
    value: fsh-generated/resources
  - code: path-resource
    value: input/examples
  - code: path-pages
    value: input/pagecontent
  - code: path-pages
    value: input/intro-notes
  - code: path-pages
    value: fsh-generated/includes
  - code: path-expansion-params
    value: ../../input/_resources/exp-params.json
  - code: active-tables
    value: 'false'
  - code: apply-contact
    value: 'true'
  - code: apply-jurisdiction
    value: 'true'
  - code: apply-publisher
    value: 'true'
  - code: apply-version
    value: 'true'
  - code: show-inherited-invariants
    value: 'false'
  - code: usage-stats-opt-out
    value: 'true'
  - code: excludettl
    value: 'true'
  - code: generate
    value: xml
  - code: generate
    value: json
  - code: version-comparison
    value: 1.0.0
  - code: version-comparison
    value: 1.1.0
  - code: version-comparison
    value: 2.0.0
  - code: bundle-references-resolve
    value: 'false'
  - code: no-narrative
    value: Parameters/cdex-parameters-example4
  - code: no-narrative
    value: Parameters/cdex-parameters-example5
  - code: no-narrative
    value: Parameters/cdex-parameters-example1
  - code: no-narrative
    value: Parameters/cdex-parameters-example2
  - code: no-narrative
    value: Parameters/cdex-parameters-example3
  - code: no-narrative
    value: Task/cdex-task-inline-example1
  - code: no-narrative
    value: Task/cdex-task-inline-example4
  - code: no-narrative
    value: Task/cdex-task-inline-example6
  - code: no-narrative
    value: Task/cdex-task-inline-example21
  - code: no-narrative
    value: Task/cdex-task-inline-example22
  - code: no-narrative
    value: Task/cdex-task-inline-example26
  - code: no-narrative
    value: Task/cdex-task-inline-example10
  - code: no-narrative
    value: Task/cdex-task-inline-example11
  - code: no-narrative
    value: Task/cdex-task-inline-example13
  - code: no-narrative
    value: Task/cdex-task-inline-example15
  - code: no-narrative
    value: Task/cdex-task-inline-example17
  - code: no-narrative
    value: Task/cdex-task-inline-example19
  - code: no-narrative
    value: Subscription/cdex-task-inline-scenario1-subscription-requested
  - code: no-narrative
    value: Subscription/cdex-task-inline-scenario1-subscription-active
  - code: no-narrative
    value: QuestionnaireResponse/cdex-questionnaireresponse-inline-example1
  - code: no-narrative
    value: Bundle/cdex-task-inline-scenario1-subscription-notification
  - code: no-narrative
    value: Bundle/cdex-bundle-inline-example-858p
  - code: suppressed-ids
    value: Parameters/cdex-parameters-example1,Parameters/cdex-parameters-example2,Parameters/cdex-parameters-example3,Parameters/cdex-parameters-example4,Parameters/cdex-parameters-example5,Task/cdex-task-inline-example1,Subscription/cdex-task-inline-scenario1-subscription-requested,Task/cdex-task-inline-example4,Task/cdex-task-inline-example6,Task/cdex-task-inline-example21,Task/cdex-task-inline-example10,Task/cdex-task-inline-example11,Task/cdex-task-inline-example13,Task/cdex-task-inline-example15,Task/cdex-task-inline-example17,Task/cdex-task-inline-example26,QuestionnaireResponse/cdex-questionnaireresponse-inline-example1,Task/cdex-task-inline-example19,Task/cdex-task-inline-example22,OperationOutcome/cdex-operationoutcome-inline-example1
  - code: tabbed-snapshots
    value: 'true'
  - code: auto-oid-root
    value: 2.16.840.1.113883.4.642.40.21
  - code: path-history
    value: http://hl7.org/fhir/us/davinci-cdex/history.html