For more than a decade, CMS has steadily pushed the industry toward interoperability — from the meaningful use era of electronic health records (EHRs) to today’s payer-to-payer and patient-access API mandates. CMS-0057-F is the latest, and in many ways most ambitious, chapter in that story: it takes direct aim at electronic prior authorization, requiring payers to build FHIR-based infrastructure that provides a shared, well-defined language for exchanging prior authorization data with providers and patients alike.

That infrastructure is a genuine achievement. But standing up the pipes is not the same as fixing what flows through them — and that distinction is where health plan executives need to focus their attention now.

The Problem the Rule Doesn’t Solve

Prior authorization today is riddled with administrative friction — from manual submissions and fragmented utilization management portals to repeated requests for information. These inefficiencies delay approvals, push back care, and place the greatest burden on the patients and providers the system is supposed to serve. CMS-0057-F addresses part of the problem by setting timeliness requirements for decisions and notifications and giving plans and providers a standardized electronic channel to reduce reliance on fax and portal-based requests.

What it doesn’t do is touch the underlying workflow. Providers still don’t want to initiate prior authorization requests in the first place, and nothing in the rule changes the policies, criteria, or layered clinical logic that require generation of those requests. Early data bears this out: end-to-end electronic prior authorization has not meaningfully improved turnaround times, and it hasn’t moved approval or denial rates — the metrics that drive member and provider abrasion.

In practice, the rule has added a channel rather than replaced one. Clinical review teams are still fielding faxes from non-participating providers, still relying on delegated utilization management vendors, and still running onsite concurrent reviews. CMS-0057-F’s addition of an Electronic Prior Authorization measure to MIPS provides some incentive for eligible clinicians to adopt FHIR-based electronic prior authorization, but it may not be enough to drive broad or rapid upgrades to EHR connectivity. As a result, health plans now have to manage more inbound pathways, not fewer.

Why Workflow Is the Real Lever

The FHIR mandate solves a data-exchange problem: it standardizes how a request moves from provider to payer and back. It does not solve a decision problem, the ambiguity that sits underneath almost every prior authorization request. Providers frequently submit requests without a clear picture of what the payer actually needs to approve them, and payers, in turn, have to interpret incomplete submissions against policies, criteria, and layered clinical logic that can vary by service line, product, and even individual reviewer. An API doesn’t resolve that ambiguity; it just delivers it faster.

That’s why the volume of inbound channels matters as much as the speed of any single channel. Electronic prior authorization doesn’t retire a fax, portal, or delegated vendor relationship — it adds itself on top of them. Utilization management teams are left triaging requests that arrive through more pathways than before, each with its own format, completeness, and level of clinical detail. Without a workflow layer designed to normalize and route that variability, the operational burden on clinical reviewers goes up even as the technology improves.

This is also where rigid, one-size-fits-all platforms become a liability rather than a solution. A system that can’t be reconfigured as policies change forces health plans to either live with a workflow that no longer fits their business, or pay for a costly custom rebuild every time it doesn’t. The plans that will meaningfully reduce friction are the ones that treat workflow as a living, configurable layer — one that can absorb new inbound channels, adjust to new criteria, and evolve with the business, rather than one that has to be re-implemented every time the environment shifts.

What Health Plans Should Do Now

Meeting the interoperability requirement is necessary but not sufficient. Reducing friction in prior authorization — the outcome that members, providers, and health plans all care about — depends on the workflow layer, not the API layer. The real opportunity lies in using the CMS-0057-F mandate as a catalyst to repair those workflows. That means:

• Evaluating current state with the business and clinicians at the table, not just IT — so workflows reflect how utilization management actually operates, not just how data moves.
• Reviewing not just what requires prior authorization, but the criteria and layered logic behind each policy, since that complexity is what’s driving reviewer burden, independent of any API.
• Designing intuitive, configurable workflows that can flex as policies and business needs change, rather than hard-wiring a static process to meet the mandate.
• Keeping AI-forward tools human-led, so automation reduces redundant work without removing clinical judgment from decisions that need it.
• Tracking the metrics that matter — turnaround times and denial rates — to measure whether the investment is actually reducing friction rather than merely satisfying technical requirements.

The Bottom Line

CMS-0057-F gives the industry a common set of pipes. What flows through them — the policies, criteria, and reviewer experience, as well as the patient’s wait for an answer — is still up to each health plan to fix. Organizations that treat this as a workflow transformation, not a compliance project, will be the ones that reduce administrative burden and improve care delivery. Those that don’t should plan now for the rework that’s coming.