FHIR Claim, Coverage, ClaimResponse, and ExplanationOfBenefit (EOB) Resources Explained

In the HL7 FHIR (Fast Healthcare Interoperability Resources) standard, administrative, eligibility, prior authorization, and billing workflows are governed by the Financial Module. At the core of this module are four tightly coupled resources—Coverage, Claim, ClaimResponse, and ExplanationOfBenefit (EOB)—which standardize how healthcare providers, health plans (payers), clearinghouses, and clinical research data networks represent health insurance policies, service submissions, real-time adjudication responses, and longitudinal paid-claim histories.

How Are Insurance Coverage and Claims Modeled in HL7 FHIR?

Unlike clinical resources covered in US Core (such as Condition, Procedure, or MedicationRequest) that document patient care from a clinical perspective, the FHIR Financial Module models the contractual and reimbursement lifecycle across four distinct stages:

1. Coverage (Insurance Policy & Eligibility): Represents a patient’s active or historical health insurance plan, Medicaid/Medicare enrollment, or workers’ compensation policy. Key elements in FHIR R4 include status (active | cancelled | draft | entered-in-error), type (plan category such as medical, dental, or prescription drug), subscriber and subscriberId, beneficiary (a reference to the Patient), relationship (self, spouse, child), period (effective dates), payor (reference to the insurer Organization), and class[] (repeating slices for group, subgroup, plan, and rxbin / rxpcn pharmacy routing identifiers).
2. Claim (Provider Submission / Request): Issued by a healthcare provider or facility to a payer requesting reimbursement or approval for healthcare products and services. Critically, a single FHIR Claim resource structure serves three distinct operational workflows controlled by the required Claim.use code:
   • claim: A formal bill requesting financial adjudication and payment for completed healthcare services.
   • preauthorization: A prospective request for prior authorization before delivering a scheduled procedure, diagnostic study, or specialty medication.
   • predetermination: An exploratory simulation asking the payer to estimate coverage and patient cost-sharing without creating a binding authorization or bill.
3. ClaimResponse (Payer Adjudication or Authorization Result): The direct reply from the insurer to a submitted Claim, indicating processing outcome (queued | complete | error | partial), line-item approval or denial codes, approved units, and prior authorization tracking numbers.
4. ExplanationOfBenefit (EOB — Consolidated Longitudinal Record): Combines the original request details from Claim with the final financial adjudication details from ClaimResponse into a single immutable patient- and provider-facing record of billed charges, allowed amounts, deductibles, coinsurance, copayments, and payer net payment.

Core Structure of the FHIR Claim Resource (R4)

In HL7 FHIR Release 4 (R4), the Claim resource maps traditional X12 837 (Institutional, Professional, and Dental) and NCPDP Telecommunication claim structures into a hierarchical JSON or XML document:

• type and subType: Classifies the claim under the standard extensible value set (institutional [UB-04 / 837I], oral [837D], pharmacy [NCPDP], professional [CMS-1500 / 837P], or vision).
• patient, provider, and insurer: References to the beneficiary (Patient), billing practitioner or organization (Practitioner / PractitionerRole / Organization), and target health plan (Organization).
• insurance[] (1..*): Links the claim to one or more Coverage resources via insurance.coverage, specifying coordination-of-benefits order via sequence (1 = primary payer, 2 = secondary payer) and focal (boolean indicating which coverage is being billed in the current transaction).
• diagnosis[] and procedure[]: Ordered arrays of ICD-10-CM diagnosis codes (including Present on Admission [POA] indicators and Diagnosis Related Group [DRG] pointers) and ICD-10-PCS / CPT procedure codes.
• supportingInfo[]: Attaches clinical justification, admission/discharge dates, type of bill, patient status, or references to clinical FHIR resources (such as DocumentReference or Observation) required for medical necessity review.
• item[] (Line Items): Each service line specifies a sequence number, productOrService (CPT, HCPCS, NDC, or revenue code), servicedDate or servicedPeriod, locationCodeableConcept (Place of Service), quantity, unitPrice, net charge, and diagnosisSequence[] pointers linking the line item to specific diagnoses.

What Data Elements Are in the FHIR ExplanationOfBenefit (EOB) Resource?

While Claim represents what the provider submitted, the ExplanationOfBenefit (EOB) resource represents the complete post-adjudication financial and clinical history. Under the HL7 CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button®) implementation guide, the EOB resource is profiled into five specialized structures (Inpatient Institutional, Outpatient Institutional, Professional/NonClinician, Pharmacy, and Oral) and contains the following core data elements:

EOB Element Path	Cardinality (R4 / CARIN BB)	Clinical & Financial Data Captured
identifier & status	1..* / 1..1	Unique Payer Claim Control Number (ICN/DCN) and lifecycle state (active | cancelled | draft | entered-in-error).
type & use	1..1 / 1..1	Claim category (institutional | professional | pharmacy | oral | vision) and workflow type (claim).
patient, insurer, provider	1..1 each	References to the member (Patient), adjudicating health plan (Organization), and rendering/billing provider.
outcome	1..1	Adjudication status (queued | complete | error | partial).
careTeam[]	0..*	Attending, operating, rendering, referring, and prescribing clinicians with NPI identifiers and taxonomy roles.
diagnosis[] & procedure[]	0..*	Principal, admitting, and secondary ICD-10-CM diagnoses (with POA flags) and inpatient ICD-10-PCS procedures.
item[].adjudication[]	0..*	Line-level financial breakdown: submitted amount, allowed/eligible amount, deductible, coinsurance, copay, non-covered amount, and benefit payment amount, plus CARC/RARC denial reason codes.
total[] & payment	0..* / 0..1	Header-level aggregated financial totals across all lines and actual check/EFT disbursement date and amount.

How Do CMS Interoperability Rules Require Payers to Expose FHIR Claim and Coverage Resources?

Two landmark federal regulations issued by the Centers for Medicare & Medicaid Services—the CMS Interoperability and Patient Access Final Rule (CMS-9115-F) and the CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F)—mandate that Medicare Advantage organizations, state Medicaid and CHIP agencies, Medicaid managed care plans, and Qualified Health Plan (QHP) issuers on the Federally Facilitated Exchanges expose these FHIR resources through production FHIR server APIs:

• Patient Access API & Provider Access API (CARIN Blue Button + US Core): Impacted payers must expose adjudicated claims and encounter data (specifically ExplanationOfBenefit and Coverage resources profiled to the CARIN IG for Blue Button®, alongside clinical USCDI data and prior authorization decisions) to patients via SMART on FHIR apps and to in-network providers via the Provider Access API (with Bulk FHIR $export support).
• Payer-to-Payer API: When a member switches health plans, payers must exchange five years of adjudicated ExplanationOfBenefit, Coverage, clinical USCDI, and active prior authorization records to preserve care continuity.
• Prior Authorization API (HL7 Da Vinci PAS — Prior Authorization Support): To automate prior authorization software workflows, the Da Vinci PAS implementation guide uses the FHIR Claim resource (with Claim.use = "preauthorization") submitted to the custom operation Claim/$submit (and queried via Claim/$inquire). The payer’s FHIR server translates or orchestrates the payload with mandated HIPAA X12 278 transactions and returns a real-time ClaimResponse containing the authorization status (approved, denied with specific clinical reason codes, or pended) within statutory turnaround windows (72 hours for expedited requests and 7 calendar days for standard requests under CMS-0057-F).

Frequently Asked Questions

How are insurance coverage and claims modeled in HL7 FHIR?

HL7 FHIR models insurance policies in the Coverage resource (storing subscriber IDs, group/plan classes, and payer references), service bills and prior authorization requests in the Claim resource (distinguished by Claim.use values of claim, preauthorization, or predetermination), immediate adjudication replies in ClaimResponse, and finalized longitudinal claim histories in ExplanationOfBenefit.

What data elements are in the FHIR ExplanationOfBenefit (EOB) resource?

The FHIR ExplanationOfBenefit resource combines submitted claim data with payer adjudication outcomes, including the claim identifier, claim type (institutional, professional, pharmacy, oral, or vision), patient and provider references, care team NPIs, ICD-10 diagnoses and DRGs, CPT/HCPCS/NDC line items (item[]), line-level and header-level financial adjudication slices (submitted, allowed, deductible, copay, coinsurance, and net paid amounts), and CARC/RARC adjustment codes.

How do CMS Interoperability Rules require payers to expose FHIR Claim and Coverage resources?

Under CMS-9115-F and CMS-0057-F, regulated payers must expose adjudicated claims as FHIR ExplanationOfBenefit and policy data as Coverage resources (using the CARIN Blue Button IG) across Patient Access, Provider Access, and Payer-to-Payer APIs, and support prior authorization submissions using FHIR Claim and ClaimResponse profiles under the HL7 Da Vinci Prior Authorization Support (PAS) implementation guide.