The Opala Solution
The Opala Patient Access API Resources and Interactions

SMART App Launch Framework Authorization Flows Access Tokens Scopes Endpoints Working with the FHIR Server

CARIN for Blue Button®
Da Vinci Payer Data Exchange (PDex)
Mapping Adjudicated Claims and Encounter Information

The Patient Access API

© 2021-2023 Opala. All Rights Reserved.

Version 1.0.2.0


Contact Opala's
Documentation Team

Da Vinci Payer Data Exchange (PDex)

The DaVinci Payer Data Exchange IG (PDex) and the US Core IG (USCDI) define how Clinical Data is provided. The Da Vinci PDex solution started with the goal of providing payer sourced information to providers in the form of FHIR resources consistent with US Core profiles for FHIR Release 4. Da Vinci expanded the scope of PDex to include not only payer-to-provider exchange at the request of the provider, but also payer-to-third-party-application exchange at the request of the member.

Provisioning Clinical Data is defined by the Da Vinci Payer Data Exchange (PDex) and US Core Implementation Guides , while provisioning Plan Coverage and Formularies is defined by the Da Vinci Payer Data Exchange US Drug Formulary Implementation Guide .

The Da Vinci PDex IG covers the exchange of:

This information is exchanged using US Core and Da Vinci Health Record Exchange (HRex) Profiles. This superset of clinical profiles forms the Health Plan Member’s Health History.

The Da Vinci PDex IG covers the exchange of a member’s Health History in the following scenarios:

Note: The latter two scenarios are provided to meet the requirements identified in the CMS Interoperability Notice for Proposed Rule Making issued on February 11, 2019.

PDex vs. US Core

Unlike the US Core 3.1.0 Implementation Guide, PDex provides guidance for payers about making the following information available via a Patient Access API:

Claims

Information coming from claims is represented as USCDI v1.1 information. This includes, at a minimum, encounters, providers, organizations, locations, dates of service, diagnoses (conditions), procedures, and observations. This would also include clinical information from sources other than claims that are maintained by the payer, such as:

The following table describes the search parameters that are required by this Implementation Guide.

Resource Parameter Type Example
ExplanationOfBenefit _id token
GET [baseurl]/ExplanationOfBenefit?_id=[id]
ExplanationOfBenefit _lastUpdated date
GET [baseurl]/ExplanationOfBenefit?_lastUpdated=[_lastUpdated]
ExplanationOfBenefit identifier token
GET [baseurl]/ExplanationOfBenefit?identifier=[system]|[code]
ExplanationOfBenefit patient reference
GET [baseurl]/ExplanationOfBenefit?patient=[patient]
ExplanationOfBenefit type token
GET [baseurl]/ExplanationOfBenefit?type=[system]|[code]
ExplanationOfBenefit service-date date
GET [baseurl]/ExplanationOfBenefit?service-date=[service-date]

Mapping Claims and Encounters

Tables providing mapping from the Consumer-Directed Payer Data Exchange IG (CARIN for Blue Button®) to fields in the respective clinical (US Core and PDex) profiles are provided on the Mapping Adjudicated Claims and Encounter Information to Clinical Resources (1.2) page.

Additional Resources

Top