This page is part of the Da Vinci Clinical Documentation Exchange (v1.0.0: STU1) 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
Official URL: http://hl7.org/fhir/us/davinci-cdex/ImplementationGuide/hl7.fhir.us.davinci-cdex | Version: 1.0.0 | |||
Active as of 2021-12-13 | Computable Name: DaVinciCDex | |||
Copyright/Legal: Used by permission of HL7 International all rights reserved Creative Commons License |
The attachment transaction and signature content is DRAFT. It has not yet undergone HL7 balloting. The appropriate pages and sections are preceded with a STU-Note indicating the draft content.
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). This guide documents the Direct Query, Task Based and Attachments transaction approaches for requesting and sending information. Key scenarios this IG can support include:
In the context of this guide, “clinical data” means any information a provider holds in a patient’s health record. The format of the data exchanged is not limited to FHIR resources, but includes C-CDA documents, pdfs, text files and other types of data. There may be requests for payloads of clinical records of care such as CCD Documents, clinical data sets that may be represented in a FHIR Bundle (or C-CDA on FHIR Documents), and clinical data such as a specific FHIR resource.
By using the FHIR standard and implementing this guide, payers can be explicit about the data they are requesting as opposed to general requests which often result in providers sending more information than is necessary. The anticipated benefit of using FHIR is more efficient and effective exchange of health record information in several areas such as claims management, care coordination, risk adjustment and quality reporting.
This IG provides several general examples to illustrate the different approaches for exchanging clinical data, but it does not to document specific use cases. We plan to create a set of Clinical Data Exchange- Supplemental Guides which will document and provide examples for specific use cases.
This Implementation Guide is supported by the Da Vinci initiative which is a private effort to accelerate the adoption of Health Level Seven International Fast Healthcare Interoperability Resources (HL7® FHIR®) as the standard to support and integrate value-based care (VBC) data exchange across communities. Like all Da Vinci Implementation Guides, it follows the HL7 Da Vinci Guiding Principles for exchange of patient health information. The guide is based upon the prior work from the US Core and Da Vinci Health Record Exchange (HRex) Implementation Guides. As illustrated in figure 1 below, this guide is built on top of FHIR and other implementation guides that provide more and more focused use cases by constraining profiles and extending functionality to cover gaps.
Changes to this specification are managed by the sponsoring HL7 Patient Care workgroup and are incorporated as part of the standard HL7 balloting process. You can suggest changes to this specification by creating a change request tracker by clicking on the Propose a Change link at the bottom of any page.
This Guide is divided into several pages which are listed at the top of each page in the menu bar.
This Implementation Guide was made possible by the contributions of the Da Vinci Project member organizations and project management staff, the Patient Care Work Group and the Payer/Provider Information Exchange Work Group.
Authors: