US health plans that signed FHIR vendor contracts under CMS-9115-F in 2021 are arriving at renewal in 2026. The question that triggers each renewal review used to be simple: did the vendor deliver Patient Access on time, and is the SLA still being met. The question in 2026 is different. CMS-0057-F changed what compliance means, and the contract that satisfied CMS-9115-F in 2021 does not, by default, satisfy CMS-0057-F in 2027. This guide lays out the renewal-decision framework most mid-size payers are using, including the eight-question RFP framework that has emerged as the practical test. For broader context, the Prior Auth FHIR reference covers the deeper material on this site.
What Renewal Actually Tests in 2026
A CMS-9115-F vendor contract from 2021 typically covered Patient Access and Provider Directory. CMS-0057-F adds three new APIs (Provider Access, Payer-to-Payer, Prior Authorization), tightens existing requirements (PA data must reach Patient Access within one business day), adds reporting obligations (annual API usage metrics, public PA reporting metrics), and pulls in new IGs (PDex Plan Net v1.1.0, CARIN BB v2.0.0 with Vision and Dental EOB).
A renewal in 2026 is the natural moment to test whether the incumbent vendor can deliver all of this by January 1, 2027. The honest framing is that few of the 2021 vendors clear the full CMS-0057-F bar without significant extension work.
The WEDI Data That Shapes the Renewal Conversation
The WEDI February 2026 survey found that only 16 percent of payers expect to be 75 to 100 percent ready by Jan 2027, while 35 percent are at 25 percent or less complete on Patient Access alone. The implementation cost estimate is also instructive: 28 percent of payers expect compliance to cost $1 to $5 million, and 25 percent expect more than $5 million.
These are large numbers for a compliance program that was supposed to be an extension of CMS-9115-F. The reality is that CMS-0057-F is closer to a fresh implementation than an extension.
The Eight-Question RFP Framework
The cmspriorauth.com RFP framework lists eight capability categories that have emerged as the practical test for CMS-0057-F vendor capability. Each category maps to a renewal-decision question the payer puts to the incumbent.
The eight: API development and FHIR implementation across all four endpoints, data integration and USCDI conformance, security and authentication (SMART App Launch, OAuth, OIDC), PA workflow automation with SLA tracking, metrics collection and public reporting, provider attribution and patient consent, testing and documentation with IG conformance maintenance, and timeline plus phased implementation feasibility.
The honest assessment after running the framework against an incumbent is usually that two or three of the eight are strong, two or three are weak, and the rest are in between. The decision is whether the strong-and-weak split is closeable in twelve months or wider than that.
What "Strong" and "Weak" Actually Mean in Each Category
Strong API development means all four CMS-0057-F APIs in production, not just Patient Access. Weak means one API done and the other three on a 2026 roadmap.
Strong reporting means automated metrics ready to ship to CMS each March 31 and public PA reporting metrics on a dashboard. Weak means raw data captured and the customer engineering team builds the report.
Strong IG maintenance means the vendor handles US Core, Da Vinci, X12 ↔ FHIR conformance over time. Weak means each IG release is a separate project the customer pays for.
The Renewal Outcomes That Actually Happen
In practice, 2026 renewals tend to land in one of three buckets. The incumbent passes the eight-question framework cleanly and the renewal is straightforward. The gap is wider than twelve months can close, and the payer issues a fresh RFP. The gap is closeable, but only with a significant scope expansion that effectively becomes a new contract.
The third bucket is the most common and the most poorly handled. Payers who treat scope expansion as a minor amendment often discover during implementation that the gap was wider than the amendment covered.
What Comes Next
For the detailed eight-question framework, the Top 8 RFP questions to ask your FHIR vendor before renewing in 2026 covers each category in depth. For health plans that have already concluded the gap is too wide to close with the incumbent, the Best FHIR platforms for health plans behind schedule on CMS-0057-F covers the alternatives.