Da Vinci - Payer Coverage Decision Exchange
0.4.1 - CI Build

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

PCDE IG Home Page

This specification is currently undergoing ballot and connectathon testing. It is expected to evolve, possibly significantly, as part of that process.

Feedback is welcome and may be submitted through the FHIR change tracker indicating "US Da Vinci PCDE" as the specification.

This implementation guide is dependent on other specifications. Please submit any comments you have on these base specifications as follows:

  • Feedback on the FHIR core specification should be submitted to the FHIR change tracker with "FHIR Core" as the specification.
  • Feedback on the US core profiles should be submitted to the FHIR change tracker with "US Core" as the specification.
  • Feedback on profiles from one of the other Da Vinci implementation guides should also be submitted to the FHIR change tracker with the specification set to the appropriate IG.

Individuals interested in participating in the Prior Authorization Support or other HL7 Da Vinci projects can find information about Da Vinci [here](http://www.hl7.org/about/davinci).

Overview

The United States has one of the world’s most complex healthcare systems, with different organizations providing different types of care across geographic and clinical lines as well as with separate organizations often providing different services and equipment independently. Transitions of care are therefore complex and provide frequent opportunities for medical errors, redundant care, and care gaps. Despite federal regulatory policy mandating data exchange between care providers, there remain serious problems with timely and comprehensive data exchange. Beyond issues with disconnected data transmission across care providers, patients generally have multiple payers including their role as a self-payer. As with care provider coordination, payer coordination is also essential to care continuity. For example, a patient who relies on home oxygen should not be at risk of hospitalization because a new payer is not aware of the requirement until after the oxygen runs out.

This need for continuity across payers has been recognized also by the United States’ largest payer, the Centers for Medicare and Medicaid Services (CMS), who has proposed in 2019 (ref) to require the exchange of data about ongoing and planned treatments covered by a previous payer and send it to a current payer along with the metadata around the conditions they are treating and how the determination was made. This requirement, while still proposed, would apply to plans funded by CMS include Medicare Advantage plans, qualified health plans, and Medicaid plans among others. Optimally, the routine and electronic exchange of this information would minimize the need for additional information to be obtained from patients and other providers and ensure that critical services and therapies are continued without interruption. While for large scale payer transitions, such as employer plan transitions, there have been some efforts to provide coordination of care and information exchange, there are no known formal efforts to support information and care exchange in a systematic way at the payer level.

The DaVinci Project is already supporting the exchange of payer information for prior authorization, formulary information sharing, provider and patient directory information, and other coverage information. Furthermore, there are aspects of the need to exchange active treatment plans and decisions which should align to use cases beyond the payer exchange use case. Optimally, the coverage decision exchange should allow relevant clinical information about decisions, treatments, and their context to align with the approach that clinicians and clinical systems take to describe this same content. This should and does include consideration of the Patient Care approach to longitudinal care planning and exchange and the regulatory framework of data exchange at transitions of care mandated by the Office of the National Coordinator for Health IT (ONC) and CMS.

For this use case, we address the need for continuity of treatment when patients move from one payer’s health insurance plan to another. In the current situation, the patient and new payers often don’t have the information needed to continue treatment in progress or to determine that the therapies are necessary or medically appropriate. As a result, patients can face a break in continuity of care, challenges to share additional information, and increased costs as tests are re-run or prior therapies need to be re-tested in order to comply with the rules of the new payer. By enabling an authorized transfer of information from the original payer to the new payer, the new payer can have access to information about what therapies are currently in place and the rationale for them, as well as what precursor steps have been taken to demonstrate the medical necessity and appropriateness of the current therapy. By automating this exchange and maximizing the computability of the information shared, a process that frequently takes weeks or months can be reduced to a few days or even minutes - reducing costs and improving patient safety, quality and experience.

This implementation guide defines standardized mechanisms for a patient or payer to enable a transfer of “current active treatments” with other relevant metadata and coverage-related information from a prior payer to a new payer. It also defines a standardized structure for organizing and encoding that information to ease it’s consumption by the new payer organization.

Content and organization

The implementation guide is organized into the following sections:

  • Use Cases and Overview describes the intent of the implementation guide, gives examples of its use and provides a high-level overview of expected process flow
  • Technical Background describes the different specifications this implementation guide relies on and indicates what developers should read and understand prior to implementing this specification
  • Formal Specification covers the detailed implementation requirements and conformance expectations
  • Artifacts introduces and provides links to the FHIR R4 profiles, operations and other FHIR artifacts used in this implementation guide
  • Downloads allows download of this and other specifications as well as other useful files
  • Credits identifies the individuals and organizations involved in developing this implementation guide

Dependencies

This implementation guide relies on the following other specifications:

  • FHIR R4 - The ‘current’ official version of FHIR as of the time this implementation guide was published. See the background page for key pieces of this specification implementers should be familiar with.
  • US Core STU3.1 - The most recent official release of US Core (based on FHIR R4).
  • Da Vinci PDex July 2019 ballot - The balloted version of Da Vinci Payer Data Exchange IG. This implementation guide will be updated to be based on the official published version of this IG once the ballot process is complete.
  • Da Vinci CDex July 2019 ballot - The balloted version of Da Vinci Clinical Data Exchange IG. This implementation guide will be updated to be based on the official published version of this IG once the ballot process is complete.
  • Da Vinci HRex July 2019 ballot - The balloted version of Da Vinci Health Record Exchange IG. This implementation guide will be updated to be based on the official published version of this IG once the ballot process is complete.
  • Da Vinci PAS Sept 2019 ballot - The balloted version of Da Vinci Prior Authorization Support IG. This implementation guide will be updated to be based on the official published version of this IG once the ballot process is complete.

This implementation guide defines additional constraints and usage expectations above and beyond the information found in these base specifications.