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

Da Vinci Clinical Data Exchange (CDex), published by HL7 International / Payer/Provider Information Exchange Work Group. This guide is not an authorized publication; it is the continuous build for version 2.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-ecdx/ and changes regularly. See the Directory of published versions

## CapabilityStatement: cdex-capabilitystatement-inline-example

Official URL: http://hl7.org/fhir/us/davinci-cdex/CapabilityStatement/cdex-capabilitystatement-inline-example | Version: 2.1.0
Standards status: Informative | Computable Name:
Other Identifiers: OID:2.16.840.1.113883.4.642.40.21.13.1
Copyright/Legal: Used by permission of HL7 International all rights reserved Creative Commons License

R4 example of a CapabilityStatement advertising support for CDex Task Update topic-based subscription

Raw OpenAPI-Swagger Definition file | Download

##

- Implementation Guide Version: 2.1.0
- FHIR Version: 4.0.1
- Supported Formats: `json`
- Supported Patch Formats:
- Published on: 2024-05-16
- Published by: HL7 International / Payer/Provider Information Exchange Work Group

> Note to Implementers: FHIR Capabilities

> Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

This CapabilityStatement instantiates the CapabilityStatement BackportSubscriptionCapabilityStatementR4version: null1.1.0)

## FHIR RESTful Capabilities

### Mode: `server`

Summary of System-wide Interactions

### Capabilities by Resource/Profile

#### Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

- The relevant profiles (if any)
- The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
- The required, recommended, and some optional search parameters (if any).
- The linked resources enabled for `_include`
- The other resources enabled for `_revinclude`
- The operations on the resource (if any)

Resource Type | Profile | R | S | U | C | D | Searches | `_include` | `_revinclude` | Operations
--- | --- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Subscription | Supported Profiles R4/B Topic-Based Subscriptionversion: null1.1.0) | y |  | y | y |  |  |  |  | `$status`
Patient |  | y |  | y | y | y |  |  |  |
Encounter |  | y |  | y | y | y |  |  |  |
Observation |  | y |  | y | y | y |  |  |  |

#### Resource Conformance: supported Subscription

Core FHIR Resource
Subscription
Reference Policy
Interaction summary

- Supports `read`, `create`, `update`.

Supported Profiles

R4/B Topic-Based Subscriptionversion: null1.1.0)

Extended Operations

Conformance | Operation | Documentation
--- | --- | ---
SHALL | $status |

#### Resource Conformance: supported Patient

Core FHIR Resource
Patient
Reference Policy
Interaction summary

- Supports `read`, `create`, `update`, `delete`.

#### Resource Conformance: supported Encounter

Core FHIR Resource
Encounter
Reference Policy
Interaction summary

- Supports `read`, `create`, `update`, `delete`.

#### Resource Conformance: supported Observation

Core FHIR Resource
Observation
Reference Policy
Interaction summary

- Supports `read`, `create`, `update`, `delete`.