CARIN Blue Button IG STU 2.0.0 is the implementation guide that powers claims and EOB data exposure under the Patient Access API. The CARIN BB profiles cover ExplanationOfBenefit (medical, pharmacy, oral, vision), Coverage, Patient, and Organization, with specific value sets and constraints. The IG looks straightforward; the variations across vendor implementations are wider than the spec text suggests. Here are five implementations that handle CARIN BB cleanly for more on payer-side FHIR decision-making in 2026.
What CARIN BB Implementation Maturity Looks Like
A solid CARIN BB implementation does five things. It maps the payer's claims data model (typically a mix of medical, pharmacy, dental, vision claims) to the four EOB profile flavors. It handles the value-set bindings for service codes, adjustment reason codes, and place-of-service codes. It exposes Coverage resources with current and historical periods. It includes the recently expanded Vision and Dental EOB scope from STU 2.0.0. It supports the search parameters members actually use (date range, claim type, patient).
The implementations differ in how cleanly each piece is wired and how much custom mapping the payer has to author.
1. Smile Digital Health (CARIN BB Module)
Smile CDR ships a CARIN BB module with pre-configured profiles, value sets, and search parameters. The strength is the bundled value-set coverage; the payer does not author the typical CARIN BB code-system mappings from scratch. The platform also includes a claims-data ingestion path that turns common payer claims feeds into CARIN BB EOB resources reliably. The Vision and Dental EOB scope from STU 2.0.0 is supported.
2. 1upHealth Patient Access (CARIN BB Profile Set)
1upHealth's Patient Access module includes complete CARIN BB profile support and a developer-friendly authoring layer for mapping payer-specific code systems. The integration ergonomics are strong, which matters when payers have to handle vendor or self-insured plans with non-standard code mappings.
3. InterSystems IRIS for Health
InterSystems IRIS supports CARIN BB profiles and exposes them through the FHIR API layer. For payers with claims data already in IRIS for analytics or HIE work, the CARIN BB extension uses the same data tier rather than requiring a separate FHIR ingestion. The integration runway is longer than at the FHIR-native vendors for greenfield deployments.
4. Edifecs (CARIN BB on FHIR Layer)
Edifecs added CARIN BB IG support to its FHIR Patient Access layer. The X12-to-FHIR translation handles the claims data conversion cleanly, which is the strength of the Edifecs lineage. The value-set bindings and search parameter support are conformant; the developer documentation is less polished than at the FHIR-native vendors.
5. Microsoft Azure Health Data Services
Microsoft Cloud for Healthcare exposes CARIN BB profile support through the Azure FHIR service. For payers running on Azure with claims data in Azure data services, the integration is clean. The CARIN BB-specific tooling is thinner than at the dedicated payer-interoperability vendors, which means more authoring work for value sets and mappings.
The Value-Set Trap in CARIN BB Implementation
CARIN BB depends on specific terminology bindings (service codes, adjustment codes, place-of-service codes). Payers whose internal data uses proprietary or legacy code systems have to map to the CARIN BB-required value sets before EOB resources are conformant. Implementations that ship pre-built mappings for common payer code systems save weeks of authoring work. Implementations that leave value-set mapping entirely to the payer engineering team end up with longer rollouts and inconsistent code coverage.
How CARIN BB Connects to the Other Patient Access Profiles
CARIN BB covers claims and EOB. PDex covers clinical data and additional Patient Access scope. US Drug Formulary covers formulary data. A complete Patient Access implementation runs all three IGs side by side and exposes them through one Patient Access API surface.
For the Patient Access platform level, the Top 5 Patient Access API platforms for CMS-0057-F covers the leading vendors. For the IG-level question of CARIN BB versus PDex when scopes overlap, the PDex vs CARIN BB comparison breaks down where each profile fits.