Da Vinci - Payer Coverage Decision Exchange (PCDE)
1.0.0 - STU 1

Da Vinci - Payer Coverage Decision Exchange (PCDE), published by HL7 International - Financial Management Work Group. This is not an authorized publication; it is the continuous build for version 1.0.0). This version is based on the current content of https://github.com/HL7/davinci-pcde/ and changes regularly. See the Directory of published versions

Technical Background

Da Vinci

Da Vinci is an industry sponsored project that brings together the U.S. provider, HIT vendor and payer communities to help payers and providers to positively impact clinical, quality, cost, and care management outcomes using FHIR-related technologies. The project organizes meetings (face-to-face and conference calls) as well as connectathons to find ways to leverage FHIR technologies to support and integrate value-based care (VBC) data exchange across communities. Da Vinci identifies value-based care use cases of interest to its members and the community as a whole.

The process that Da Vinci has adopted includes:

  1. identify business, clinical, technical and testing requirements,
  2. develop and ballot a FHIR based implementation guide (IG),
  3. develop a reference implementation (RI) that is used to demonstrate that the concepts in the IG are possible to implement,
  4. pilot the standard
  5. support the production use of the IG to enable exchange of data to support interoperability for value-based care.

Additional information about Da Vinci, its members, the use cases and the implementation guides being developed can all be found on the HL7 website. Meeting minutes and other materials can be found on the Da Vinci Confluence page.


The PCDE implementation guide defines the responsibilities of the two types of systems involved in a PCDE solution:

Original payer systems Systems that manage data on behalf of a payer who is a source for data to be transferred

New payer systems Systems that manage data on behalf of a payer who is an intended recipient of transferred data.

Underlying technologies

This guide is based on the HL7 FHIR standard. Implementers of this specification therefore need to understand some basic information about these specifications.


This implementation guide uses terminology, notations and design principles that are specific to FHIR. Before reading this implementation guide, it’s important to be familiar with some of the basic principles of FHIR as well as general guidance on how to read FHIR specifications. Readers who are unfamiliar with FHIR are encouraged to read (or at least skim) the following prior to reading the rest of this implementation guide.

This implementation guide supports the R4 version of the FHIR standard. R4 is just recently published and the goal is to ensure the implementation guide is aligned with the current direction of the FHIR standard.

Because of this IG’s focus on document creation, implementers should also familiarize themselves with the FHIR Composition and the guidelines around the creation and processing of FHIR documents.

This implementation guide builds on the following IGs:

Implementers should familiarize themselves with the Task-based communication mechanism and the member match operation defined within HRex and the profiles defined in that IG as well as all of the others.