CMS-0057-F Fundamentals

Start here if you are new to the rule. These pages summarize the regulation, its deadlines, and what is already in force.

Fact Sheet

CMS-0057-F Fact Sheet

Requirements, the four APIs, FHIR standards, and implementation deadlines at a glance — the primary reference hub.

Status

What's in Effect in 2026

Which prior authorization process requirements are already live versus the January 2027 API deadlines.

Timeline

Compliance Timeline

Phased deadlines, extension pathways, and enforcement across payer types.

Required APIs

Detailed references for each of the four FHIR APIs mandated by the rule.

API

Patient Access API

Consumer-facing FHIR access to claims, clinical data, and prior authorization information.

API

Provider Access API

Attributed-patient data access for in-network providers, including architecture and a payer checklist.

API

Payer-to-Payer API

Automated data exchange when members change plans — consent, provenance, reconciliation, and build-vs-buy.

API

Prior Authorization API

Electronic PA discovery, documentation, and submission via the Da Vinci CRD/DTR/PAS workflow.

FHIR and Da Vinci

Deeper technical guides for the standards and Da Vinci implementation guides that underpin the rule's APIs.

Guide

FHIR for CMS-0057-F

A practical FHIR guide for health plans: where FHIR fits across all four APIs, US Core, Da Vinci, SMART on FHIR, terminology, and mapping FHIR to existing payer data models.

Guide

CRD, DTR & PAS Explained

How the three Da Vinci prior authorization implementation guides fit together, where the payer API boundary sits, and where X12 still appears.

Payer Architecture & Core Administration

How the CMS-0057-F interoperability layer fits with established core administration platforms.

Guide

CMS-0057-F with QNXT

A reference architecture for implementing the interoperability layer in front of a QNXT core administration platform using adapters.

Independent educational resource. These guides describe the regulation and common implementation patterns. They are not official CMS guidance, and they do not assert capabilities of any specific commercial product beyond what that product's own documentation supports. Always validate architectural decisions against the official CMS materials and the relevant HL7 / Da Vinci implementation guides.