Skip to main content
v2026.11,986 entries · CC-BY 4.0

HL7 FHIR Coverage Resource: Eligibility, X12 270/271, and CARIN

How the HL7 FHIR R4 Coverage resource models subscriber, beneficiary, and plan classes, maps to X12 270/271 eligibility, and powers CARIN Blue Button APIs.

Written and maintained by CASRAI Editorial Board

Published

On this page

The HL7 FHIR R4 Coverage resource is the foundational financial and administrative data structure used to represent a patient’s health insurance policy, government healthcare benefit (such as Medicare or Medicaid), or self-pay financial arrangement. Within the broader FHIR Claim and financial workflow architecture, Coverage bridges clinical identity (`Patient`) and payer adjudication (`ExplanationOfBenefit` and `ClaimResponse`), supplying the policy identifiers, subscriber relationships, and pharmacy routing numbers required for prior authorization, real-time benefit checks, and health economics research.

Under federal interoperability rules—including the CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) and the CMS Patient Access API (CMS-9115-F)—health plans and electronic health record (EHR) systems exchange Coverage profiles standardized by both US Core and the HL7 Da Vinci FHIR Project.

How Does the HL7 FHIR R4 Coverage Resource Represent Subscriber, Beneficiary, and Plan Hierarchy?

In healthcare administration and claims databases, the person who holds the insurance policy is not always the person receiving clinical care, and a single insurance card often carries multiple hierarchical routing identifiers (group, plan, pharmacy BIN, and processor control numbers). The FHIR R4 Coverage resource models these distinctions through explicit elements:

  • status (1..1): Indicates whether the coverage record is active, cancelled, draft, or entered-in-error. Note that an active status combined with a historical period.end date represents a policy that has expired.
  • type (0..1): Classifies the coverage program using the X12 Source of Payment Typology or HL7 v3 CoverageType code system (for example, commercial PPO, Medicare Part A/B/D, Medicaid, TRICARE, or workers’ compensation).
  • subscriber, subscriberId, and beneficiary (1..1): The subscriber is the policy holder (referenced as a Patient or RelatedPerson) whose member ID string is stored in subscriberId. The beneficiary is the Patient for whom clinical services are covered, linked to the subscriber via relationship (such as self, spouse, or child).
  • payor (1..*): References the insuring Organization (or a Patient / RelatedPerson when `type` indicates self-pay).
  • class (0..* BackboneElement): Encodes the multi-tier plan and pharmacy benefit hierarchy using typed key-value pairs where class.type binds to codes such as group, subgroup, plan, subplan, class, rxbin (Pharmacy Benefit Manager BIN), rxpcn (Processor Control Number), and rxgroupid.

How Do CoverageEligibilityRequest and CoverageEligibilityResponse Map to ASC X12N 270/271?

During patient registration and pre-visit financial clearance, provider systems verify whether a patient’s policy is active and inspect copay, coinsurance, and deductible balances. Historically, this exchange has relied on the HIPAA-mandated ASC X12N 270 (Eligibility, Coverage or Benefit Inquiry) and 271 (Eligibility, Coverage or Benefit Information) EDI transactions. In HL7 FHIR R4, these transactions are represented by CoverageEligibilityRequest and CoverageEligibilityResponse:

ASC X12N 270/271 Loop / Segment FHIR R4 Resource & Element Path Operational Role in Financial Clearance
270 Header (`BHT`) & Inquiry Purpose CoverageEligibilityRequest.purpose (auth-requirements, benefits, discovery, validation) Specifies whether the provider is checking active status, benefit balances, or prior-auth rules.
270 Loop `2100A` (Information Source) & `2100B` (Receiver) CoverageEligibilityRequest.insurer & provider Identifies the target payer (`Organization`) and requesting clinician or facility.
270 Loop `2100C`/`2100D` (Subscriber / Dependent) & `EQ` (Service Type) CoverageEligibilityRequest.patient, insurance.coverage, and item.category Links the patient and target Coverage resource and queries specific X12 Service Type Codes (e.g., `30` Health Benefit Plan Coverage).
271 Loop `2110C`/`2110D` `EB01` (Eligibility/Benefit Info) CoverageEligibilityResponse.insurance.inforce (boolean) Confirms whether the policy is currently in force (`EB01 = ‘1’` Active Coverage vs. `’6’` Inactive).
271 `EB` Segments (Deductible, Out-of-Pocket, Copay) CoverageEligibilityResponse.insurance.item.benefit (type, allowedMoney, usedMoney) Returns network tier (`network`), individual/family unit (`unit`), total annual deductible, and amount already met (`usedMoney`).

How Does the CMS Patient Access API Use CARIN Blue Button Coverage and ExplanationOfBenefit?

Under the CMS Interoperability and Patient Access Final Rule (CMS-9115-F, 42 CFR § 422.119 and § 431.60) and CMS-0057-F, regulated health plans must expose member claims, encounter history, and clinical data via FHIR R4 APIs conforming to two flagship Implementation Guides:

  • CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button): Standardizes how payers present adjudicated financial and clinical claims to members and authorized third-party applications. The CARIN Blue Button C4BB-Coverage profile constrains Coverage to require status, subscriberId, beneficiary, relationship, and payor. Every adjudicated claim is exposed as a profiled ExplanationOfBenefit (EOB) resource—split into five profiles (Inpatient Institutional, Outpatient Institutional, Professional/Non-Clinician, Pharmacy, and Oral)—which references the active C4BB-Coverage instance via ExplanationOfBenefit.insurance.coverage.
  • HL7 Da Vinci Payer Data Exchange (PDex): Governs payer-to-payer and payer-to-provider exchange of longitudinal clinical and coverage history. Da Vinci PDex links clinical US Core resources derived from prior claims and C-CDA documents with the member’s historical and active Coverage resources so receiving care teams and health services researchers can reconstruct continuous enrollment windows.

Frequently Asked Questions

How do researchers determine continuous enrollment periods from FHIR Coverage resources?

In observational claims and EHR-linked studies, establishing a baseline washout or follow-up window requires verifying that a patient had uninterrupted medical and pharmacy coverage. Researchers query GET [base]/Coverage?beneficiary=Patient/[id], filter for medical (`type`) vs. pharmacy (`rxbin` class) policies, and evaluate contiguous `Coverage.period.start` and `Coverage.period.end` intervals (accounting for administrative grace periods).

What is the difference between subscriberId and Identifier on a FHIR Coverage resource?

Coverage.subscriberId holds the identifier assigned by the payer to the primary policy holder (the subscriber), which may be shared across multiple family members on the same policy. By contrast, Coverage.identifier (and specifically the `memberid` slice in US Core and CARIN Blue Button) holds the unique member identifier assigned to the specific beneficiary covered by that Coverage instance.

How does Coverage.order work when a patient has dual coverage (such as Medicare and Medicaid)?

When a patient is covered by multiple active policies simultaneously, Coverage.order is a positive integer (`1` for primary payer, `2` for secondary payer, `3` for tertiary payer) that specifies the Coordination of Benefits (COB) adjudication sequence used when submitting claims.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · full access

Ask about HL7 FHIR Coverage Resource: Eligibility, X12 270/271, and CARIN

Full access: large monthly usage, up to 10 source passages behind each answer, and MCP and API access for Claude Code, Codex and other CLIs. Cancel any time.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →