# A Health Plan’s Guide to CMS-0057-F API Requirements (CMS Interoperability & Prior Authorization Final Rule) ## Key Facts - **January 1, 2027:** CMS Interoperability and Prior Authorization Final Rule **CMS-0057-F** requires health plans to implement **three new HL7 FHIR® APIs**—**Provider Access**, **Payer-to-Payer**, and **Prior Authorization**—by this date. (Section: “Key Takeaways,” bullet 1; Section: “January 1, 2027, is closer than it seems…,” para 1) - **January 2026 (already active):** Prior authorization decision timelines include **72-hour expedited** and **seven-day standard** turnaround requirements. (Section: “Key Takeaways,” bullet 2) - **Five total API obligations:** In addition to the **three new** APIs, plans must **expand the existing Patient Access API** to include **prior authorization data** and **update the Provider Directory API** to meet **new implementation guide standards**. (Section: “January 1, 2027…,” para 1; Section: “The Five APIs and What They Entail”) - **Estimated savings:** CMS estimates the rule will save the healthcare system **approximately $15 billion over 10 years** by reducing prior authorization burdens. (Section: “January 1, 2027…,” para 3) - **Prior Authorization API is a coordinated 3-guide workflow:** It uses three HL7® Da Vinci implementation guides—**CRD v2.2.1**, **DTR v2.2.0**, and **PAS v2.2.1**—to support coverage checks, documentation requirements, and electronic prior authorization submission/decisioning. (Section: “The Prior Authorization API,” bullets) - **Payer-to-Payer data scope:** When requested by a new payer, plans must share **up to five years** of **claims** and **prior authorization data**; the FAQ specifies inclusion of claims/encounter data (with stated exclusions), **USCDI clinical data classes**, and prior authorization records (with stated exclusions). (Section: “Payer-to-Payer API,” para 1; Section: “Frequently Asked Questions,” Q5) ## Summary ### What CMS-0057-F requires (deadlines, APIs, and what changes) CMS-0057-F (the CMS Interoperability and Prior Authorization Final Rule) sets a major interoperability deadline of **January 1, 2027** for health plans to implement **three new HL7 FHIR® APIs**: **Provider Access**, **Payer-to-Payer**, and **Prior Authorization**. At the same time, it expands the **Patient Access API** to include **prior authorization data** and requires updates to the **Provider Directory API** to align with new implementation guide standards. Separately, the article notes that **January 2026 provisions**—including **72-hour expedited** and **seven-day standard** prior authorization decision timelines—are already active. CMS estimates the rule will generate **approximately $15 billion in savings over 10 years** by reducing prior authorization burdens. ### How each API works (and why the Prior Authorization API is the most complex) The guide breaks down what each of the five APIs entails. The **Provider Access API** enables in-network providers to request bulk data for attributed members, which hinges on **attribution accuracy** and **opt-out management**. The **Payer-to-Payer API** supports member transitions by sharing **up to five years** of data when requested by a new payer, with key compliance challenges including member matching, provider attribution, and consent management. The **Prior Authorization API** is described as the most complex because it is designed as an end-to-end workflow built on three Da Vinci implementation guides—**Coverage Requirements Discovery (CRD) v2.2.1**, **Documentation Templates and Rules (DTR) v2.2.0**, and **Prior Authorization Support (PAS) v2.2.1**—where CRD determines whether prior authorization is required, DTR communicates documentation requirements in a computable format, and PAS enables structured submission and response (including status, denial reasons, and approval data). ### What “API readiness” looks like and how the guide recommends sequencing the work Beyond building endpoints, the guide frames readiness as three layers: **data quality**, **attribution and consent logic**, and **integration architecture** (connecting APIs into core administrative, care management, and provider data systems rather than treating them as stand-alone). For implementation, it recommends a phased approach: 1) Start with **Prior Authorization** (due to complexity across CRD/DTR/PAS and real-time workflow needs) alongside the **Provider Directory API**; 2) then implement **Patient Access** and **Provider Access** while addressing surfaced data quality issues and building attribution/opt-out tracking; 3) finish with **Payer-to-Payer** after establishing robust consent frameworks. The guide emphasizes testing throughout, including conformance testing against Da Vinci implementation guides and stress testing under realistic query volumes. ### What the guide flags as “next” (CMS-0062-P) The article also points to **CMS-0062-P** (a proposed **2026** rule) as a signal that interoperability expectations are increasing, including proposals such as mandated Da Vinci conformance (CRD/DTR/PAS), extending HL7 FHIR-based prior authorization to drug workflows, and the possibility of elevating Da Vinci implementation guides into HIPAA requirements—while noting CMS-0062-P is still proposed.

About this content