FHIR R4 ExplanationOfBenefit API

Overview

This asset is a component of MuleSoft Accelerator for Healthcare.

MuleSoft Accelerator for Healthcare enables healthcare providers to unlock critical patient data to build a patient 360 within Salesforce Health Cloud, faster and easier than ever before. The solution includes pre-built APIs, connectors, integration templates, and prescriptive end-to-end reference architecture to bring patient demographics information and COVID-19 test results from any EHR into Health Cloud using HL7 V2 or FHIR standards.

The solution also provides a library of United States Core Data for Interoperability (USCDI) and FHIR R4 resources to help healthcare developers adhere to interoperability needs and jumpstart the development of healthcare digital transformation initiatives.

Use case covered

The ExplanationOfBenefit (EOB) resource combines key information from a Claim, a ClaimResponse and optional Account information to inform a patient of the goods and services rendered by a provider and the settlement made under the patient's coverage in respect of that Claim. The ExplanationOfBenefit resource may also be used as a resource for data exchange for bulk data analysis, as the resource encompasses Claim, ClaimResponse and Coverage/Eligibility information.

This is the logical combination of the Claim, ClaimResponse and some Coverage accounting information in respect of a single payor prepared for consumption by the subscriber and/or patient. It is not simply a series of pointers to referred-to content models, is a physical subset scoped to the adjudication by a single payor which details the services rendered, the amounts to be settled and to whom, and optionally the coverage allowed under the policy and the amounts used to date.

Typically the EOB is only used to convey Claim (use=claim) and the associated ClaimResponse information to patients or subscribers. It may also be used to convey consolidated predetermination and preauthorization request and response information to patients or subscribers. An EOB will never be created for patient or subscriber information exchange if an error was detected in the Claim.

It is also recognized that "EOB" is a term that carries additional meaning in certain areas of the industry. When the resource was originally being developed there was substantial discussion about the adoption of an alternative name for the resource but after much discussion it was resolved that the ExplanationOfBenefit name has the advantage of familiarity that has been proven through the early adoption of the resource for multiple purposes.

Note: when creating profiles for EOB as a patient focused information exchange the payment details, other than date, should be excluded if the payee is the provider as that would leak business confidential information.

Note: the EOB SHALL NOT be used as a replacement for a ClaimResponse when responding to Claims. Only the ClaimResponse contains the appropriate adjudication information for a payor response to a Claim.

The ExplanationOfBenefit resource is an "event" resource from a FHIR workflow perspective - see Workflow Event.

This API uses FHIR R4 ExplanationOfBenefit Library.

More information about FHIR R4 ExplanationOfBenefit specification can be found here.