What the Rule Actually Requires of State FFS Programs
CMS-0057-F applies to a specific set of payers: Medicare Advantage organizations, Medicaid FFS programs, CHIP FFS programs, Medicaid managed care plans, CHIP managed care entities, and QHP issuers on the federally facilitated marketplace. The January 1, 2027 date applies to state Medicaid and CHIP FFS programs and Medicare Advantage organizations; Medicaid managed care plans and CHIP managed care entities comply by the rating period beginning on or after January 1, 2027. The rule builds directly on the 2020 Patient Access final rule by adding three new APIs and significantly expanding the data the existing Patient Access endpoint must carry.
Patient Access API — Prior Authorization Data Added
State Medicaid FFS programs have operated a Patient Access API since the 2020 interoperability rule, with a compliance date of January 1, 2021. CMS-0057-F expands that existing HL7 FHIR R4 endpoint to include prior authorization data starting January 1, 2027: specifically, the item or service being authorized, the status of each PA decision, and the specific denial reason where applicable. For programs already running a Patient Access API, this is a data layer extension rather than a new system build — but it requires the prior authorization workflow and the claims system to be integrated with the existing FHIR server.
Provider Access API — New
The Provider Access API allows treating providers to query a state Medicaid program on behalf of their patients to retrieve claims, encounter, and clinical information needed for care coordination. A physician seeing a Medicaid patient for the first time can retrieve that patient's prior claims history from the state without calling a hotline or requesting a manual records transfer.
The implementation constraint is provider identity and attribution. The API can only respond to providers who actually have an active care relationship with the beneficiary — a constraint that requires the state to operate a queryable, current provider directory and attribution logic connecting provider NPI to enrolled patients. Without those prerequisites, the FHIR server can be running and still unable to respond to valid queries.
Payer-to-Payer API — New
The Payer-to-Payer API allows a receiving payer to request a beneficiary's data when that beneficiary transitions between coverage — from Medicaid FFS to a managed care plan, from Medicaid to commercial coverage, or the reverse. The technical exchange uses HL7 FHIR R4 with standard patient-matching criteria.
For state programs, there is an additional coordination obligation: when a Medicaid FFS beneficiary opts in to Payer-to-Payer data exchange, the state must pass that opt-in to the beneficiary's managed care plans as well. This requires state FFS and MCO systems to handle opt-in routing consistently, which is a workflow integration requirement beyond the FHIR API itself.
Prior Authorization API — New
The Prior Authorization API converts prior authorization from a predominantly fax-and-phone workflow to a structured FHIR-based exchange. CMS finalized a framework based on the Da Vinci Coverage Requirements Discovery (CRD), Documentation Templates and Rules (DTR), and Prior Authorization Support (PAS) implementation guides. States may satisfy the requirement using a FHIR-only approach or a FHIR plus X12 combination, but the clinical workflow must accept structured PA requests and return decisions with standard status codes and specific denial reasons.
This is the most technically demanding of the four APIs for most state programs. The Da Vinci guides require specific FHIR profiling that most existing PA systems weren't originally built to support. Implementing CRD, DTR, and PAS in production requires FHIR profiling expertise and testing against real provider EHR systems — which many state IT teams do not have in-house.
What Was Already Required in 2026
The operational PA requirements in CMS-0057-F — specific decision timelines, real-time denial notifications, specific denial reasons — took effect January 1, 2026. Beginning in 2026 and annually thereafter, impacted payers must also report PA metrics at the state level. These two requirements are separate from the API technical mandates, but they are connected to the same systems. A state that struggled with the operational requirements is likely to face the same capacity and infrastructure constraints building the API layer.
The 2026 metrics reporting requirement is worth checking explicitly: states that have not filed their first annual PA metrics report may have PA workflow infrastructure gaps that will affect the Prior Authorization API build.
The One-Year Extension for State FFS Programs
Under 42 CFR § 431.61(c), a state Medicaid FFS program may apply for a one-time, one-year extension of the Provider Access and Payer-to-Payer API requirements. The rule provides a parallel extension mechanism for the Prior Authorization API requirement under 42 CFR § 431.80. The extension does not apply to the Patient Access API expansion. The request must include three components:
- A narrative justification specific to the state agency's FFS program — not a general statement about industry readiness challenges, but a documented explanation of the specific circumstances preventing compliance by January 1.
- A report on completed and ongoing state activities demonstrating a good-faith compliance effort to date.
- A comprehensive plan to achieve full compliance no later than January 1, 2028.
The request goes in the state's annual Advance Planning Document for MMIS operations and must be approved before the compliance date. A state that determines in late December that it cannot comply and hasn't filed the APD request by then has fewer viable options.
What the extension does not cover. This flexibility is specific to Medicaid FFS programs. Medicaid managed care organizations face the same January 1, 2027 date through a different regulatory pathway, and there is no equivalent extension option for them — they comply by the rating period beginning on or after January 1, 2027. In states where managed care accounts for most Medicaid enrollment, state compliance and MCO compliance are independent obligations that must be tracked separately. A state FFS extension does not reduce the exposure from non-compliant MCOs.
Common Implementation Barriers for State Medicaid Programs
Legacy MMIS infrastructure. Many Medicaid Management Information Systems were built to process transactions, not to serve FHIR APIs. The integration typically requires a middleware or integration layer connecting a FHIR server to the core transaction processing system. That layer must be designed, built, configured for state-specific data structures, security-tested, and load-tested before it can go to production. For states that haven't started, twelve to eighteen months is a common planning estimate for this kind of work — which is why January 2027 was always a tight timeline for programs that received little dedicated funding.
Provider directory currency and attribution. The Provider Access API requires confirming that a querying provider has an active care relationship with the patient. Many state Medicaid systems don't maintain a queryable provider-patient attribution that can be called in real time. Building that capability is a separate project from building the FHIR server.
Member matching across payers. The Payer-to-Payer API requires reliable beneficiary identity matching across different payer systems. FHIR R4 includes standard patient-matching criteria, but state Medicaid systems commonly use state-specific beneficiary identifiers that don't translate cleanly to multi-payer matching without an identity resolution layer.
Da Vinci implementation guide expertise. The Prior Authorization API depends on the Da Vinci CRD, DTR, and PAS guides — a specific set of FHIR profiling constraints that most state IT organizations, and many MMIS vendors, have limited production experience with. Building and testing a compliant PA API requires FHIR profiling skills and an EHR integration partner willing to test.
Network testing. FHIR API compliance involves live testing with real provider systems. State Medicaid programs cover networks of thousands of providers with varying EHR platforms. Coordinating provider participation in pre-launch testing is a significant operational undertaking.
Five Decisions for the Next 40 Days
1. Get a clear status on each API separately Confirm from your MMIS vendor or state health IT team where each of the four APIs stands: in production, in testing, in development, or not started. These are independent systems with independent readiness conditions. An aggregate status ("we're working on it") is insufficient for assessing whether an extension request is needed.
2. Assess the extension path now if any API is behind If any of the three new APIs cannot reach production by January 1, the APD-based extension request must be initiated immediately. The documentation required — narrative justification, good-faith activity report, and a full compliance plan — takes time to develop. The APD process itself takes time. A state that waits until December to assess readiness may not be able to file a compliant extension request before the deadline.
3. Confirm managed care coordination Review what your MCO contracts specify about CMS-0057-F API compliance. Each MCO is independently responsible for its own January 1, 2027 compliance. If an MCO is behind, the state's contract oversight mechanisms are the lever — a state FFS extension does not cover MCO non-compliance. Confirm MCO readiness now, while there is time to escalate if needed.
4. Verify prior authorization metrics reporting The 2026 annual PA metrics reporting requirement was due for state FFS programs this year. Confirm that your program filed its first report and that the data infrastructure behind it is functioning. The Prior Authorization API builds on some of the same data the reporting requirement uses; gaps in reporting infrastructure are likely gaps in API readiness.
5. Plan provider communication for the post-launch period A live Prior Authorization API without providers knowing how to query it doesn't deliver the operational intent of the rule. Prepare a provider communication strategy now — documentation, help desk support, and outreach through provider associations — so that when January 1 arrives, there's a path for providers to adopt the new workflow rather than continue calling.
Sources and further reading
- CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) Fact Sheet, CMS, January 17, 2024
- CMS-0057-F Final Rule, 89 FR 8758, Federal Register, February 8, 2024
- 42 CFR § 431.61, Provider Access and Payer-to-Payer API requirements and extension provisions, eCFR
- 42 CFR § 431.80, Prior Authorization API requirements, eCFR
- Gainwell Technologies: Interoperability in 2026 — A Roadmap for State Agencies
- Leavitt Partners: Survey Highlights Delays in Readiness for the CMS Interoperability and Prior Authorization Final Rule
- Prior Authorization API — CMS overview and Da Vinci implementation guides
Spartan X's work in state health and human services has consistently surfaced the same gap: the technical requirement is clear, but the system architecture needed to meet it was never on the roadmap of programs built for transaction throughput rather than data exchange. For state programs assessing readiness today, that architectural gap — between MMIS transaction systems and the FHIR API layer they now need — is usually where the honest conversation about timeline and flexibility has to start.



