# Healthcare Interoperability FAQ for Health Plans: CMS Rules, HL7 FHIR APIs, and Key Deadlines ## Key Facts - **May 1, 2020:** The **CMS Interoperability and Patient Access Final Rule (CMS-9115-F)** required impacted plans to implement a **Patient Access API** so enrollees can access **claims, encounter, and clinical data** via third-party apps. (Section: “What Regulatory Requirements Are Driving Interoperability?”) - **January 17, 2024:** The **CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F)** mandates **HL7 FHIR-based APIs** for real-time data exchange and streamlined prior authorization workflows. (Section: “What Regulatory Requirements Are Driving Interoperability?”) - **January 1, 2026:** **Operational and process-related prior authorization requirements** under **CMS-0057-F** took effect, including **new transparency standards** and **timeframe requirements**. (Section: “What Are the Key Compliance Deadlines Health Plans Need to Know?”) - **January 1, 2027:** Plans must have **full HL7 FHIR-based API compliance** in place, including **CRD, DTR, and PAS** and the **Patient Access API prior authorization enhancement, Provider Directory API, Provider Access API, and Payer-to-Payer API**; CMS has indicated this is an **active enforcement date**. (Section: “What Are the Key Compliance Deadlines Health Plans Need to Know?”) - **May 26, 2028:** **CMS-0053-F** sets federal standards for electronic claims attachments using **X12 and HL7 Clinical Document Architecture (HL7 CDA)—Consolidated CDA (C-CDA) Implementation Guides**, with a compliance deadline of **May 26, 2028**. (Section: “What Regulatory Requirements Are Driving Interoperability?” and “What Are the Key Compliance Deadlines Health Plans Need to Know?”) - **Prior authorization decision timeframes (CMS-0057-F):** Health plans must send decisions within **72 hours (urgent)** and **seven calendar days (standard)**, and provide a **specific reason for any denial**. (Section: “What Does the New Prior Authorization Drug Proposed Rule Mean for Health Plans?”) ## Summary ### What interoperability means for health plans—and why it’s now strategic Interoperability is described as the ability of different healthcare systems, applications, and stakeholders to **securely exchange, interpret, and act on data in real time**. The article positions this as more than a technical project for health plans, linking efficient data exchange to operational improvements such as **faster prior authorization decisions**, reduced administrative burden, stronger provider collaboration, and improved member satisfaction. It also frames interoperability as foundational for value-based care models, AI-powered analytics, and predictive population health management. (Section: “What Is Interoperability and Why Should Health Plans Care?”) ### Which CMS rules are driving requirements—and what they mandate The content traces regulatory momentum from **CMS-9115-F (published May 1, 2020)**—which established Patient Access API requirements—through **CMS-0057-F (published January 17, 2024)**, which expands and adds **HL7 FHIR (Fast Healthcare Interoperability Resources)–based APIs** to support real-time exchange and prior authorization workflow modernization. A related rule, **CMS-0053-F**, establishes electronic claims attachment standards with a compliance deadline of **May 26, 2028**. (Section: “What Regulatory Requirements Are Driving Interoperability?”) ### What APIs are required under CMS-0057-F and when they go live CMS-0057-F requires health plans to implement or expand several **HL7 FHIR-based APIs by January 1, 2027**. These include a **Prior Authorization API** (often implemented using HL7 Da Vinci Project implementation guides **CRD v2.2.1**, **DTR v2.2.0**, and **PAS v2.2.1**, which CMS “currently recommends but does not yet mandate”), plus a **Provider Access API**, **Payer-to-Payer API**, **Patient Access API** enhancement that adds prior authorization details (including denial reasons), and a **Provider Directory API** (extended to Medicaid and CHIP fee-for-service programs). The article also notes three key compliance dates to track: **January 1, 2026** (operational/process prior authorization requirements), **January 1, 2027** (API compliance), and **May 26, 2028** (electronic claims attachments). (Sections: “What Specific API Requirements Apply to Health Plans Under CMS-0057-F?” and “What Are the Key Compliance Deadlines Health Plans Need to Know?”)

About this content