Most payer respondents were still short of 100% in October 2026. In WEDI's September and October 2026 survey, 10% of payer respondents put their CMS-0057-F Prior Authorization API work at 100% approximate completion; 20% were at 0% or unsure. Impacted payers must generally offer the API beginning January 1, 2027.
| WEDI figure, fourth survey (fielded September and October 2026) | Number | What it means in practice |
|---|---|---|
| Payer respondents at 100% approximate completion on the Prior Authorization API | 10% | Up from 3% in February 2026. Most payer respondents were below 100% about three months before the compliance date |
| Payer respondents at 75%, 50%, and 25% on the same API | 25%, 37%, and 7% | Our reading: expect a mixed January across payers |
| Payer respondents at 0% or unsure on the same API | 20% | WEDI does not split "not started" from "unsure" |
| Payer respondents somewhat or very likely to offer the prior authorization APIs through an online portal | 52% | About half of payer respondents call a portal option somewhat or very likely. Our reading: plan for portal steps |
| Total responses, all stakeholder types | 174 | WEDI does not print how many of the 174 were payers |
What did WEDI's fourth survey find about payer Prior Authorization API work?
WEDI, the Workgroup for Electronic Data Interchange, posted its fourth Interoperability and Prior Authorization survey on November 16, 2026. WEDI describes itself in the deck as an HHS advisor tracking industry progress toward compliance with CMS-0057-F. The question asked each organization for its "current approximate completion" toward the January 1, 2027 compliance date.
On the Prior Authorization API , 10% of payer respondents put their work at 100% approximate completion in the October 2026 results. Another 25% put it at 75%, 37% at 50%, 7% at 25%, and 20% at 0% or unsure. In February 2026, the 100% share was 3% and the 0% or unsure share was 13%.
The other APIs vary. At 100% approximate completion in October 2026, WEDI shows 10% of payer respondents for the Provider Access API, 5% for the Payer-to-Payer API, and 22% for the incremental Patient Access API requirements.
Payer respondents named three top challenges in October 2026:
- Delegated third parties facing challenges connecting with different systems.
- Meeting compliance timelines.
- Coordination with trading partners.
WEDI also asked payers whether implementation costs were more, less, or as expected. The deck shows that question as a chart with no printed percentages, so this article reports no cost share.
Who did WEDI survey, and what do the percentages mean?
WEDI says it surveyed payers, providers, clearinghouses, and health IT vendors in four rounds: January and February 2025, October 2025, February 2026, and September and October 2026. The rounds drew 243, 173, 83, and 174 responses. The deck does not print how many of the 174 fourth-round responses came from payers.
That changes how to read the numbers. Every payer percentage is a share of an unstated count of self-reported answers. It is not a CMS audit, a finding of noncompliance, or a measure of all payers. "Approximate completion" is also the respondent's own estimate of build progress. A payer at 100% on the survey has not necessarily connected with your organization.
The ONC and CMS voluntary testing sprints are covered in our post on electronic prior authorization testing .
What does CMS-0057-F require in 2026 and 2027?
CMS split the Interoperability and Prior Authorization final rule into two phases. Process rules came first, with compliance dates starting January 1, 2026. The API requirements come next, with compliance dates generally beginning January 1, 2027. CMS says the exact compliance dates vary by the type of payer.
| Requirement | What CMS requires | Compliance date | Which payers |
|---|---|---|---|
| Specific denial reason | A specific reason for denied prior authorization decisions, whatever method sent the request | Starting January 1, 2026 | All impacted payers |
| Decision timeframes | 72 hours for expedited requests, seven calendar days for standard requests | Starting January 1, 2026 | Impacted payers except QHP issuers on the FFEs |
| Public prior authorization metrics | Certain metrics posted on the payer's website, annually | Initial set due March 31, 2026 | All impacted payers |
| Prior Authorization API | Covered items and services, documentation requirements, request and response | January 1, 2027 for MA organizations and state Medicaid and CHIP FFS programs | Medicaid and CHIP managed care: rating period beginning on or after January 1, 2027. FFE QHP issuers: plan years beginning on or after January 1, 2027 |
| Provider Access API and Payer-to-Payer API | Data sharing with in-network providers and between payers | Compliance dates in 2027, same payer-type split | All impacted payers, on the same payer-type dates as the Prior Authorization API |
| Patient Access API, prior authorization data | Prior authorization information added, excluding drugs | Compliance dates in 2027, same payer-type split | All impacted payers, on the same payer-type dates as the Prior Authorization API |
The 2026 denial-reason rule already applies on every channel. CMS says those decisions "may be communicated via portal, fax, email, mail, or phone." When the Prior Authorization API is live, CMS requires it to return an approval with the date or circumstance under which it ends, a denial with a specific reason, or a request for more information.
Which payers does CMS-0057-F cover?
CMS calls them impacted payers: Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities, and Qualified Health Plan issuers on the Federally Facilitated Exchanges. CMS states that the requirements do not directly pertain to Medicare fee-for-service. The rule's prior authorization policies do not apply to drugs.
Original Medicare runs its own prior authorization programs outside this rule. Examples include WISeR prior authorization for skin substitutes and Botox prior authorization in hospital outpatient departments . Payers also keep changing their own prior authorization lists alongside the rule, as in the UnitedHealthcare pediatric prior authorization changes .
Has CMS delayed the January 1, 2027 date?
As of November 19, 2026, no CMS source we checked shows a delay. CMS's CMS-0057-F rule page, last modified October 8, 2026, still says impacted payers "have until primarily January 1, 2027, to meet the application programming interface (API) requirements."
The enforcement discretion on that page is narrower. On February 28, 2024, CMS announced that it will not take HIPAA Administrative Simplification enforcement action against covered entities that use an all-FHIR Prior Authorization API without the X12 278 standard. CMS also states that an X12 278 transaction alone cannot meet the other requirements of the rule. The discretion does not move a compliance date.
Do providers have to use the Prior Authorization API in 2027?
No. The API requirement sits with impacted payers. Providers connect through their own health IT when a payer's API is live.
CMS's Electronic Prior Authorization measure is the provider-side lever. Under the FY 2027 inpatient final rule, the measure is an optional bonus measure for eligible hospitals and critical access hospitals in the CY 2027 EHR reporting period and becomes mandatory beginning with CY 2028. CMS's summary of electronic prior authorization rulemaking says the measure stays optional for MIPS eligible clinicians in CY 2027 and becomes required for the CY 2028 performance period.
What should revenue cycle and coding teams do if a payer is not on the API yet?
Plan for two channels in January. Our reading of the WEDI and CMS material, not a WEDI finding:
- List the payers in your book that are impacted payers, and note each one's compliance date. Managed care plans and Exchange plans may not start on January 1.
- Ask each major impacted payer, in writing, which Prior Authorization API capabilities will be live on its compliance date, for which plans, and whether requests will come through a direct connection or a portal.
- Keep portal, fax, and phone routes staffed for payers that are not live. January 1 does not retire them.
- Log the specific denial reason on every denied request, by payer and by channel. That reason is already required in 2026.
- Check the payer's posted prior authorization metrics, first due March 31, 2026, before contract or escalation talks.
- Match the codes. The CPT or HCPCS codes, units, modifiers, and ICD-10-CM diagnoses on the authorization request should match what the documentation supports and what the claim will bill.
- Review authorization-related denials by payer in the first months of 2027, with attention to mismatches between authorized and billed codes.
An electronic approval does not mean a claim will pay if the billed codes differ from what the payer authorized. Payer rules on codes and units also vary, as our guide to managing payer-specific coding requirements explains. This article is not legal advice. Confirm obligations with your compliance team and each payer contract.
Where does coding accuracy fit in prior authorization?
Our reading: an authorization request and the claim that follows both depend on documentation that supports the codes, and on those codes matching each other. That holds whether the request goes through an API, a portal, or a fax.
MediCodio AI works on the coding step behind the claim. Complete charts flow through AutoPilot for fully autonomous coding. Charts where the documentation is thin or contradictory stay in CoPilot, where certified coders review and finalize the output. Every code ships with its documentation passage and the compliance rule behind it, so your team can see why a code was assigned when a payer asks.
Frequently asked questions
How many payers have finished the CMS-0057-F Prior Authorization API?
WEDI's survey does not measure all payers. In its September and October 2026 round, 10% of payer respondents put their Prior Authorization API work at 100% approximate completion, 25% at 75%, 37% at 50%, 7% at 25%, and 20% at 0% or unsure. The round drew 174 responses across stakeholder types.
When is the CMS-0057-F Prior Authorization API due?
January 1, 2027, for Medicare Advantage organizations and state Medicaid and CHIP fee-for-service programs. Medicaid managed care plans and CHIP managed care entities use the rating period beginning on or after January 1, 2027. QHP issuers on the Federally Facilitated Exchanges use plan years beginning on or after that date.
Which payers does CMS-0057-F cover?
Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities, and QHP issuers on the Federally Facilitated Exchanges. CMS says the requirements do not directly pertain to Medicare fee-for-service, and the rule's prior authorization policies do not apply to drugs. Employer plans are not on the list.
What prior authorization rules already apply in 2026?
Starting January 1, 2026, impacted payers must give a specific reason for denied prior authorization requests, on any channel, and publicly report certain prior authorization metrics. Payers other than QHP issuers on the Federally Facilitated Exchanges must decide expedited requests within 72 hours and standard requests within seven calendar days.
Has CMS delayed the Prior Authorization API date?
As of November 19, 2026, no CMS source we checked shows a delay. CMS's rule page, last modified October 8, 2026, still says "primarily January 1, 2027" for the API requirements. Its listed enforcement discretion covers only the X12 278 standard in an all-FHIR Prior Authorization API and does not move a date.
See this on your own charts. Book a Demo to run a review on your own charts and see the documentation passage and rule behind every code before the claim goes out.
Sources
- WEDI. "WEDI Interoperability and Prior Authorization Survey Results (2025 & 2026)." November 16, 2026. https://www.wedi.org/2026/11/16/wedi-interoperability-and-prior-authorization-survey-results-2025-2026/
- WEDI. Interoperability and Prior Authorization Survey, 2025 & 2026 results deck (PDF). https://l.feathr.co/wedisurvey2026
- CMS. "CMS Interoperability and Prior Authorization Final Rule CMS-0057-F" (fact sheet). January 17, 2024. https://www.cms.gov/newsroom/fact-sheets/cms-interoperability-prior-authorization-final-rule-cms-0057-f
- CMS. "CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F)" rule page. https://www.cms.gov/initiatives/burden-reduction/overview/interoperability/policies-regulations/cms-interoperability-prior-authorization-final-rule-cms-0057-f
- Federal Register. 89 FR 8758, document 2024-00895. February 8, 2024. https://www.federalregister.gov/documents/2024/02/08/2024-00895/medicare-and-medicaid-programs-patient-protection-and-affordable-care-act-advancing-interoperability
- CMS. "HIPAA Transaction Enforcement Discretion" FAQs. https://www.cms.gov/initiatives/burden-reduction/overview/interoperability/frequently-asked-questions/hipaa-transaction-enforcement-discretion
- CMS. "FY 2027 Hospital Inpatient Prospective Payment System and Long-Term Care Hospital Prospective Payment System Final Rule" (fact sheet). https://www.cms.gov/newsroom/fact-sheets/fy-2027-hospital-inpatient-prospective-payment-system-long-term-care-hospital-prospective-payment
- CMS. "Electronic Prior Authorization: Industry Commitments & Finalized and Proposed Rulemaking." https://www.cms.gov/files/document/electronic-prior-authorization-industry-commitments-finalized-proposed-rulemaking.pdf
