Da Vinci Clinical Data Exchange (CDex) Implementation Guide
0.2.0 - ballot

This page is part of the Da Vinci Clinical Documentation Exchange (v0.2.0: STU1 Ballot 1) based on FHIR R4. The current version which supercedes this version is 1.1.0. For a full list of available versions, see the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

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.

Data Consumer Client CapabilityStatement

This CapabilityStatement describes the expected capabilities of a Da Vinci CDex Data Consumer (often a Payer) in Client mode when requesting clinical data from the Data Source (often an EHR) during a clinical data exchange. This includes the following interactions:

  1. Requesting Clinical Data using a FHIR RESTful query
  2. POSTing a Task resource representing a request for clinical data
  3. POSTing a Subscription resource
  4. Polling a Task resource
Data Consumer Server CapabilityStatement

This CapabilityStatement describes the expected capabilities of a Da Vinci CDex Data Consumer (often a Payer) in Server mode when responding to a Data Source (often an EHR) or one of its proxies during a clinical data exchange. This includes the following interactions:

  1. Responding to a query for Authorization information represented by a CommunicationRequest or ServiceRequest
  2. Responding to Subscription Notification posted to it endpoint updating the status of a Task
Data Source Client CapabilityStatement

This CapabilityStatement describes the expected capabilities of a Da Vinci CDex Data Source (often an EHR) in Client mode during a clinical data exchange with a Data Consumer. This includes the following interactions:

  1. Query for Authorization information represented by a CommunicationRequest or ServiceRequest
  2. Posting a subscription notification to a Data Consumer endpoint updating the status of a Task
Data Source Server CapabilityStatement

This CapabilityStatement describes the expected capabilities of a Da Vinci CDex Data Source (often an EHR) in Server mode when responding to a Data Consumer (often a Payer) during a clinical data exchange. This includes the following interactions:

  1. Responding to a FHIR RestFul Query for Clinical Data
  2. Responding to a POST of a Task resource representing a request for clinical data
  3. Responding to a POST of a Subscription resource
  4. Responding to polling of a Task resource

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide

CDex Task Data Request Profile

This Task profile is based upon the Da Vinci Hrex Task Data Request Profile. It extensibly binds Task.input.value codes to LOINC® Document types.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like

Scenario 1 Completed Authorization Example

Completed Task to seek a patient active conditions with a reference to a formal authorization.
Scenario 1 Authorization Example

Task to seek a patient active conditions with a reference to a formal authorization.
Scenario 1 Completed Free Text Example

Completed Task to seek a patient active conditions using free text for the input.
Scenario 1 Free Text Example

Task to seek a patient active conditions using free text for the input.
Scenario 1 Contained Example

Completed Task to seek a patient active conditions using a contained resource for output.
Scenario 1 Completed Example

Completed Task to seek a patient active conditions.
Scenario 1 Example

Task to seek a patient active conditions.
Scenario 2 Failed Task Example

Task to seek a patient’s HbA1c test results.
Scenario 2 Task Example

Task to seek a patient HbA1c test results.
Scenario 3 Completed Task Example

Completed Task to seek a patient’s latest history and physical exam notes.
Scenario 3 Task Example

Task to seek a patient’s latest history and physical exam notes.