Da Vinci Clinical Data Exchange (CDex)
2.1.0 - STU 2.1

Publication Build: This will be filled in by the publication tooling

## CDex ImplementationGuide Resource

Page standards status: Informative

Official URL: http://hl7.org/fhir/us/davinci-cdex/ImplementationGuide/hl7.fhir.us.davinci-cdex | Version: 2.1.0
NPM package name: hl7.fhir.us.davinci-cdex | ComputableName: DaVinciCDex
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License | Standards status: trial-use Maturity Level: 2

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).

- XML
- JSON

### Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (hl7.fhir.us.davinci-cdex.r4) and R4B (hl7.fhir.us.davinci-cdex.r4b) are available.

### IG Dependencies

This IG Contains the following dependencies on other IGs.

IG | Package | FHIR | Comment
--- | --- | --- | ---
Da Vinci Clinical Data Exchange (CDex) | hl7.fhir.us.davinci-cdex#2.1.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#6.2.0 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology
FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#5.1.0 | R4 | Automatically added as a dependency - all IGs depend on the HL7 Extension Pack
US Core Implementation Guide | hl7.fhir.us.core#7.0.0 | R4 | Needed for systems supporting USCDI v4
HL7 Terminology (THO) | hl7.terminology.r4#5.5.0 | R4 |
SMART App Launch | hl7.fhir.uv.smart-app-launch#2.0.0 | R4 |
VSAC | us.nlm.vsac#0.18.0 | R4 |
Structured Data Capture | hl7.fhir.uv.sdc#3.0.0 | R4 |
PHINVads | us.cdc.phinvads#0.12.0 | R4 |
US Core (Reuse Wrapper) | hl7.fhir.us.core.v610#6.1.0 | R4 | Needed for systems supporting USCDI v3
US Core Implementation Guide | hl7.fhir.us.core#6.1.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#5.0.0 | R4 |
FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#1.0.0 | R4 |
Bulk Data Access IG | hl7.fhir.uv.bulkdata#2.0.0 | R4 |
SMART App Launch | hl7.fhir.uv.smart-app-launch#2.1.0 | R4 |
VSAC | us.nlm.vsac#0.11.0 | R4 |
IHE FormatCode Vocabulary | ihe.formatcode.fhir#1.1.0 | R4 |
US Core (Reuse Wrapper) | hl7.fhir.us.core.v311#3.1.1 | R4 | Needed for systems supporting USCDI v1
US Core | hl7.fhir.us.core#3.1.1 | R4 |
Da Vinci Health Record Exchange (HRex) | hl7.fhir.us.davinci-hrex#1.1.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#6.1.0 | R4 |
VSAC | us.nlm.vsac#0.19.0 | R4 |
Da Vinci Prior Authorization Support (PAS) FHIR IG | hl7.fhir.us.davinci-pas#2.1.0 | R4 |
Da Vinci - Coverage Requirements Discovery | hl7.fhir.us.davinci-crd#2.0.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#5.3.0 | R4 |
Da Vinci Health Record Exchange (HRex) | hl7.fhir.us.davinci-hrex#1.0.0 | R4 |
Security for Scalable Registration, Authentication, and Authorization | hl7.fhir.us.udap-security#0.1.0 | R4 |
Subscriptions R5 Backport | hl7.fhir.uv.subscriptions-backport.r4#1.1.0 | R4 |
CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) | hl7.fhir.us.carin-bb#2.0.0 | R4 |
VSAC | us.nlm.vsac#0.7.0 | R4 |
Da Vinci - Documentation Templates and Rules | hl7.fhir.us.davinci-dtr#2.1.0 | R4 |
Da Vinci - Coverage Requirements Discovery | hl7.fhir.us.davinci-crd#2.1.0 | R4 |

Package hl7.fhir.uv.extensions.r4#5.1.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00)

Package hl7.fhir.uv.sdc#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. This includes two components: * Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains. *Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Tue, Mar 8, 2022 18:36+0000+00:00)

Package hl7.fhir.us.core#7.0.0 The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm. These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Wed, May 8, 2024 15:33+0000+00:00)

Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)

Package hl7.fhir.uv.bulkdata#2.0.0 FHIR based approach for exporting large data sets from a FHIR server to a client application (built Fri, Nov 26, 2021 05:56+1100+11:00)

Package ihe.formatcode.fhir#1.1.0 Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00)

Package hl7.fhir.us.core#6.1.0 The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm. These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Fri, Jun 30, 2023 14:02+0000+00:00)

Package hl7.fhir.us.davinci-hrex#1.1.0 The Da Vinci Payer Health Record exchange (HRex) Framework/library specifies the FHIR elements used in multiple Da Vinci implementation guides. This includes FHIR profiles, functions, operations, and constraints on other specifications such as CDS-Hooks and other aspects of Da Vinci Use Cases that are common across more than a single use case.\n\nDa Vinci HRex Implementation Guide (IG) will make use of US Core profiles that are based on the FHIR R4 specification wherever practical. The HRex IG will use the HL7 FHIR Release 4/US Core STU3 specification as its base but will provide additional guidance and documentation to support implementations that follow the HL7 FHIR STU3/US Core STU2 and HL7 FHIR DSTU2/Argonaut specifications.\n\nThe HRex profiles documented in this IG will be used to exchange data between providers systems (e.g. EHRs) and other providers, payers, and third-party applications where appropriate. In addition, exchanges from payer systems to providers, other payers, and third-party applications are supported by the HRex profiles and operations.\n\nHRex may define new extensions, profiles, value sets, constraints/extension to other specification (e.g. specific CDS-Hooks) that are specific Da Vinci requirements. Where appropriate these Da Vinci specific artifacts will be promoted for incorporation into the future versions of existing standards (e.g. R4 US Core profiles) and deprecated in this guide on publication in the updated standard. (built Tue, Dec 10, 2024 16:43+0000+00:00)

Package hl7.fhir.us.udap-security#0.1.0 This implementation guide describes how to extend OAuth 2.0 to support secure and scalable workflows for business-to-business (B2B) apps that implement the client credentials flow or authorization code flow. (built Fri, Aug 6, 2021 15:57+0000+00:00)

Package hl7.fhir.us.davinci-hrex#1.0.0 The Da Vinci Payer Health Record exchange (HRex) Framework/library specifies the FHIR elements used in multiple Da Vinci implementation guides. This includes FHIR profiles, functions, operations, and constraints on other specifications such as CDS-Hooks and other aspects of Da Vinci Use Cases that are common across more than a single use case. Da Vinci HRex Implementation Guide (IG) will make use of US Core profiles that are based on the FHIR R4 specification wherever practical. The HRex IG will use the HL7 FHIR Release 4/US Core STU3 specification as its base but will provide additional guidance and documentation to support implementations that follow the HL7 FHIR STU3/US Core STU2 and HL7 FHIR DSTU2/Argonaut specifications. The HRex profiles documented in this IG will be used to exchange data between providers systems (e.g. EHRs) and other providers, payers, and third-party applications where appropriate. In addition, exchanges from payer systems to providers, other payers, and third-party applications are supported by the HRex profiles and operations. HRex may define new extensions, profiles, value sets, constraints/extension to other specification (e.g. specific CDS-Hooks) that are specific Da Vinci requirements. Where appropriate these Da Vinci specific artifacts will be promoted for incorporation into the future versions of existing standards (e.g. R4 US Core profiles) and deprecated in this guide on publication in the updated standard. (built Wed, Mar 23, 2022 18:55+0000+00:00)

Package hl7.fhir.us.davinci-crd#2.0.0 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Fri, Oct 20, 2023 14:17+0000+00:00)

Package hl7.fhir.uv.subscriptions-backport.r4#1.1.0 The Subscription R5 Backport Implementation Guide enables servers running versions of FHIR earlier than R5 to implement a subset of R5 Subscriptions in a standardized way. (built Wed, Jan 11, 2023 15:34+1100+11:00)

Package hl7.fhir.us.carin-bb#2.0.0 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) (built Mon, Nov 28, 2022 15:15+0000+00:00)

Package hl7.fhir.us.davinci-pas#2.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment. (built Fri, Dec 20, 2024 21:03+0000+00:00)

Package hl7.fhir.us.davinci-crd#2.1.0 Guidelines for conveying coverage requirements to clinicians when planning treatment (built Wed, Dec 11, 2024 18:43+0000+00:00)

Package hl7.fhir.us.davinci-dtr#2.1.0 The Documentation Templates and Rules (DTR) Implementation Guide (IG) specifies how payer rules can be executed in a provider context to ensure that documentation requirements are met. The IG is a companion to the Coverage Requirements Discovery (CRD) IG, which uses CDS Hooks to query payers to determine if there are documentation requirements for a proposed medication, procedure or other service. (built Sat, Dec 21, 2024 15:48+0000+00:00)

### Global Profiles

There are no Global profiles defined

### Copyrights

This publication includes IP covered under the following statements.

- ISO Maintains the copyright on the country codes, and controls it's use carefully. For futher details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
  Show Usage
  - ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code: CDEXSDCQuestionnaireResponse, CDexClaimUseCodes... Show 22 more, CDexDataRequestTaskCode, CDexIdentifierTypes, CDexLOINCAttachmentCodesValueSet, CDexPOUCodes, CDexPWK01AttachmentReportTypeCodeValueSet, CDexParametersSubmitAttachment, CDexPatientDemographics, CDexPractitionerRole, CDexSignature, CDexSignatureBundle, CDexTaskAttachmentRequest, CDexTaskDataRequest, CDexTempCodes, CDexWorkQueueCodes, CapabilityStatement/cdex-capabilitystatement-inline-example, DaVinciCDex, DataConsumerClientCapabilityStatement, DataConsumerServerCapabilityStatement, DataSourceClientCapabilityStatement, DataSourceServerCapabilityStatement, HomeOxygenTherapyQuestionnaire and SubmitAttachment
- The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
  Show Usage
  - Unified Code for Units of Measure (UCUM): Bundle/cdex-searchbundle-scenario2-example and Parameters/cdex-parameters-example4
- These codes are excerpted from ASTM Standard, E1762-95(2013) - Standard Guide for Electronic Authentication of Health Care Information, Copyright by ASTM International, 100 Barr Harbor Drive, West Conshohocken, PA 19428. Copies of this standard are available through the ASTM Web Site at www.astm.org.
  Show Usage
  - Signature Type Codes: Bundle/cdex-document-digital-sig-example, Bundle/cdex-electronic-sig-example... Show 6 more, Bundle/cdex-searchbundle-digital-sig-example, CDexSignature, HomeOxygenTherapyQuestionnaire, Parameters/cdex-parameters-example2, QuestionnaireResponse/cdex-questionnaireresponse-example3 and QuestionnaireResponse/cdex-questionnaireresponse-example4
- This CodeSystem is not copyrighted.
  Show Usage
  - C4BB Identifier Type Code System: CDexPatientDemographics, Task/cdex-task-example20... Show 7 more, Task/cdex-task-example22, Task/cdex-task-example23, Task/cdex-task-example24, Task/cdex-task-example25, Task/cdex-task-example28, Task/cdex-task-example29 and Task/cdex-task-inline-example22
- This material contains content from LOINC. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.
  Show Usage
  - LOINC: Bundle/cdex-document-digital-sig-example, Bundle/cdex-electronic-sig-example... Show 19 more, Bundle/cdex-searchbundle-scenario2-example, Bundle/cdex-searchbundle-scenario3-example, CDexLOINCAttachmentCodesValueSet, CDexParametersSubmitAttachment, CDexTaskAttachmentRequest, CDexTaskDataRequest, Parameters/cdex-parameters-example1, Parameters/cdex-parameters-example2, Parameters/cdex-parameters-example3, Parameters/cdex-parameters-example4, Task/cdex-task-example19, Task/cdex-task-example20, Task/cdex-task-example21, Task/cdex-task-example6, Task/cdex-task-example7, Task/cdex-task-example8, Task/cdex-task-inline-example19, Task/cdex-task-inline-example21 and Task/cdex-task-inline-example6
- This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
  Show Usage
  - SNOMED Clinical Terms&reg; (SNOMED CT&reg;): Bundle/cdex-bundle-inline-example-858p, Bundle/cdex-document-digital-sig-example... Show 7 more, Bundle/cdex-electronic-sig-example, Bundle/cdex-searchbundle-digital-sig-example, Bundle/cdex-searchbundle-provenance-example, Bundle/cdex-searchbundle-scenario1-example, Condition/cdex-condition-inline-example-858, Parameters/cdex-parameters-example2 and Task/cdex-task-example3
- This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
  Show Usage
  - Condition Category Codes: Bundle/cdex-bundle-inline-example-858p, Bundle/cdex-document-digital-sig-example... Show 7 more, Bundle/cdex-electronic-sig-example, Bundle/cdex-searchbundle-digital-sig-example, Bundle/cdex-searchbundle-provenance-example, Bundle/cdex-searchbundle-scenario1-example, Condition/cdex-condition-inline-example-858, Parameters/cdex-parameters-example2 and Task/cdex-task-example3
  - Condition Clinical Status Codes: Bundle/cdex-bundle-inline-example-858p, Bundle/cdex-document-digital-sig-example... Show 7 more, Bundle/cdex-electronic-sig-example, Bundle/cdex-searchbundle-digital-sig-example, Bundle/cdex-searchbundle-provenance-example, Bundle/cdex-searchbundle-scenario1-example, Condition/cdex-condition-inline-example-858, Parameters/cdex-parameters-example2 and Task/cdex-task-example3
  - ConditionVerificationStatus: Bundle/cdex-bundle-inline-example-858p, Bundle/cdex-searchbundle-digital-sig-example, Bundle/cdex-searchbundle-provenance-example and Bundle/cdex-searchbundle-scenario1-example
  - Observation Category Codes: Bundle/cdex-searchbundle-scenario2-example and Parameters/cdex-parameters-example4
  - Provenance participant type: Bundle/cdex-bundle-inline-example-858p, Bundle/cdex-searchbundle-provenance-example and Provenance/cdex-provenance-inline-example-858
  - identifierType: Bundle/cdex-document-digital-sig-example, Bundle/cdex-electronic-sig-example... Show 44 more, CDexIdentifierTypes, CDexPatientDemographics, CDexSignature, Parameters/cdex-parameters-example2, Parameters/cdex-parameters-example5, QuestionnaireResponse/cdex-questionnaireresponse-example1, QuestionnaireResponse/cdex-questionnaireresponse-example2, QuestionnaireResponse/cdex-questionnaireresponse-example3, QuestionnaireResponse/cdex-questionnaireresponse-example4, QuestionnaireResponse/cdex-questionnaireresponse-inline-example1, Task/cdex-task-example1, Task/cdex-task-example11, Task/cdex-task-example12, Task/cdex-task-example13, Task/cdex-task-example14, Task/cdex-task-example15, Task/cdex-task-example16, Task/cdex-task-example17, Task/cdex-task-example18, Task/cdex-task-example19, Task/cdex-task-example2, Task/cdex-task-example20, Task/cdex-task-example22, Task/cdex-task-example23, Task/cdex-task-example24, Task/cdex-task-example25, Task/cdex-task-example26, Task/cdex-task-example27, Task/cdex-task-example28, Task/cdex-task-example29, Task/cdex-task-example3, Task/cdex-task-example30, Task/cdex-task-example31, Task/cdex-task-example4, Task/cdex-task-example5, Task/cdex-task-inline-example1, Task/cdex-task-inline-example11, Task/cdex-task-inline-example13, Task/cdex-task-inline-example15, Task/cdex-task-inline-example17, Task/cdex-task-inline-example19, Task/cdex-task-inline-example22, Task/cdex-task-inline-example26 and Task/cdex-task-inline-example4
  - ActCode: Bundle/cdex-document-digital-sig-example, Bundle/cdex-electronic-sig-example and Parameters/cdex-parameters-example2
  - ActReason: CDexPOUCodes, CDexTaskAttachmentRequest... Show 44 more, CDexTaskDataRequest, Task/cdex-task-example1, Task/cdex-task-example10, Task/cdex-task-example11, Task/cdex-task-example12, Task/cdex-task-example13, Task/cdex-task-example14, Task/cdex-task-example15, Task/cdex-task-example16, Task/cdex-task-example17, Task/cdex-task-example18, Task/cdex-task-example19, Task/cdex-task-example2, Task/cdex-task-example20, Task/cdex-task-example21, Task/cdex-task-example22, Task/cdex-task-example23, Task/cdex-task-example24, Task/cdex-task-example25, Task/cdex-task-example26, Task/cdex-task-example27, Task/cdex-task-example28, Task/cdex-task-example29, Task/cdex-task-example3, Task/cdex-task-example30, Task/cdex-task-example31, Task/cdex-task-example4, Task/cdex-task-example5, Task/cdex-task-example6, Task/cdex-task-example7, Task/cdex-task-example8, Task/cdex-task-example9, Task/cdex-task-inline-example1, 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-example19, Task/cdex-task-inline-example21, Task/cdex-task-inline-example22, Task/cdex-task-inline-example26, Task/cdex-task-inline-example4 and Task/cdex-task-inline-example6
  - HL7 Document Format Codes: Bundle/cdex-searchbundle-scenario3-example
  - NullFlavor: CDexTaskDataRequest
- Used by permission of HL7 International all rights reserved Creative Commons License
  Show Usage
  - CDex Temporary Code System: CDexDataRequestTaskCode, CDexPOUCodes... Show 46 more, CDexTaskAttachmentRequest, CDexTaskDataRequest, CDexWorkQueueCodes, Task/cdex-task-example1, Task/cdex-task-example10, Task/cdex-task-example11, Task/cdex-task-example12, Task/cdex-task-example13, Task/cdex-task-example14, Task/cdex-task-example15, Task/cdex-task-example16, Task/cdex-task-example17, Task/cdex-task-example18, Task/cdex-task-example19, Task/cdex-task-example2, Task/cdex-task-example20, Task/cdex-task-example21, Task/cdex-task-example22, Task/cdex-task-example23, Task/cdex-task-example24, Task/cdex-task-example25, Task/cdex-task-example26, Task/cdex-task-example27, Task/cdex-task-example28, Task/cdex-task-example29, Task/cdex-task-example3, Task/cdex-task-example30, Task/cdex-task-example31, Task/cdex-task-example4, Task/cdex-task-example5, Task/cdex-task-example6, Task/cdex-task-example7, Task/cdex-task-example8, Task/cdex-task-example9, Task/cdex-task-inline-example1, 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-example19, Task/cdex-task-inline-example21, Task/cdex-task-inline-example22, Task/cdex-task-inline-example26, Task/cdex-task-inline-example4 and Task/cdex-task-inline-example6
- Used by permission of HL7 International, all rights reserved Creative Commons License
  Show Usage
  - US Core DocumentReferences Category Codes: Bundle/cdex-searchbundle-scenario3-example, Parameters/cdex-parameters-example1, Parameters/cdex-parameters-example3, Task/cdex-task-example7 and Task/cdex-task-example8

### Parameter Settings

The following IG Parameters are set for this Implementation Guide:

- 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