Review the CMS Interoperability and Patient Access Final Rule (CMS-9115-F) published on cms.gov to identify the four mandatory FHIR API types: Patient Access API, Provider Access API, Payer-to-Payer Data Exchange API, and the Prior Authorization API (added by CMS-0057-F).
Understand the Patient Access API requirements: payers must expose a FHIR R4 endpoint providing claims, clinical (US Core profiles), formulary (PDex Formulary IG), and provider directory (Plan-Net IG) data to members via SMART on FHIR.
Review the compliance date timeline: the Patient Access API was required by July 1, 2021 for most impacted payers; the Provider Access API and Payer-to-Payer API have later effective dates tied to subsequent rulemaking.
Identify the impacted payer types: Medicare Advantage organizations, Medicaid FFS programs, CHIP FFS programs, Medicaid managed care plans, CHIP managed care entities, and QHP issuers on the federally facilitated exchanges.
Review documentation and attribution requirements: payers must document their FHIR API endpoints in a machine-readable format and provide member-facing documentation on how to access the API.
Review the penalties and enforcement framework: CMS enforces compliance through the annual plan performance review and can impose compliance actions on non-conformant plans.
Known gotchas
CMS-9115-F and its companion rules (CMS-0057-F for prior auth) have different effective dates and impacted payer populations — a Medicaid managed care plan may have different compliance timelines than a Medicare Advantage plan.
The rule requires the Patient Access API to be available to 'third-party applications' authenticated via SMART on FHIR — payers that require manual app registration approval processes risk non-compliance if approval is not timely or transparent.
The rule mandates specific FHIR IG versions (e.g., specific versions of CARIN BB, PDex, US Core) which may lag behind the latest published IG versions — always verify the CMS-mandated IG version against the current published version before implementing.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp