This website uses cookies

Read our Privacy policy and Terms of use for more information.

S

Hey friends, A federal rule went live on January 1 that cut prior authorization wait times almost in half for tens of millions of Americans. Most patients have no idea it exists. Most doctors found out from a memo. Today Biscuit the corgi walks us through what changed, whether your insurance is actually on the hook (it probably isn't the way you'd guess), and the one move worth making this week - Shivang

TL;DR

CMS-0057-F is a federal rule that forces certain insurance plans to decide prior auth requests faster, explain their denials in plain detail, and by 2027 plug into a standard digital pipe so your doctor can submit requests straight from their software. The first clocks started January 1, 2026. The deeper plumbing arrives January 1, 2027. The single biggest category of insurance in the country, the plan you get through your job, isn't covered at all.

If "prior authorization" already sounds like a foreign language, start with our medical billing 101 and insurance 101 issues, then come back. We'll wait.

The cast (one of them wears a blazer):

Quick cast, in case you're new.

Biscuit is a corgi who sprained his right ankle chasing a squirrel a few issues back (code S93.401A, if you were taking notes).

Dr. Singh is his doctor.

Sage is the border collie who runs Dr. Singh's front office and fights with insurers for a living.

Otis is a French bulldog who reviews prior auth requests at Biscuit's insurance plan, a fictional Medicaid managed care plan we call Pawferred Health.

Story time

It’s Wednesday morning. Dr. Singh presses on Biscuit's ankle. Biscuit winces. Dr. Singh frowns and says the four words that start the whole story.

"We need an MRI."

Biscuit knows the drill. Before the MRI can happen, his insurance has to agree in advance that it's medically necessary and worth paying for. That agreement is the prior authorization. He knows it takes a while. What he doesn't know is that the rules changed in January, and for the first time, the insurance company is the one watching the clock.

Before we go back to the story, let’s dive a little bit deeper into what this CMS ruling is, who it covers and how it affects you.

So what is CMS-0057-F?

On January 17, 2024, CMS, the federal agency that runs Medicare and Medicaid, finalized a rule named CMS-0057-F. It does two things. The first lands in 2026: covered insurers have to decide prior auth faster, explain their denials in detail, and post their prior auth metrics publicly every year (the first reports were due March 31, 2026). The second lands January 1, 2027: they have to build standardized digital connections (called APIs) between their systems and your doctor's software. If you read our [payer policy] issue, this is the rule that finally puts a deadline on the part of the system that used to run on "we'll get back to you."

Does this rule cover you?

Before we follow Biscuit's MRI, answer the only question that matters first: does this reach your insurance? Find your plan.

  1. Medicare Advantage: Medicare is federal coverage for people 65 and up (and some younger people with disabilities). Medicare Advantage is the private version you buy from an insurer instead of getting it straight from the government. Covered. The clocks apply.

  2. Medicaid. Medicaid is joint federal and state coverage for low-income people. It comes two ways. Fee-for-service, where the state pays your doctor one bill at a time. And managed care, where the state hands a private insurer a flat amount per person to run the whole thing. Managed care is where most enrollees land, about 78% of them (KFF), Biscuit included. Both are covered. The clocks apply.

  3. CHIP: The Children's Health Insurance Program covers kids whose families earn a little too much for Medicaid. Same two flavors as Medicaid, same answer. Covered. The clocks apply.

  4. Qualified Health Plans on HealthCare.gov: These are private plans you buy yourself on the federal marketplace. This is the only commercial plan the rule touches at all. Here's the catch most write-ups get wrong: these plans owe you the public reporting and the detailed denials, but they're specifically exempt from the faster decision clocks. Transparency yes, speed no.

  5. Your job's plan: Not covered. Whether your employer buys coverage or pays the claims itself (self-funded), the federal rule doesn't reach it. CMS said so directly. And it's the biggest bucket of all: employer plans cover about 154 million people, more than Medicare, Medicaid, or any other single source in the country (KFF).

tldr: government plans get the clocks. HealthCare.gov plans get the transparency but not the speed. Job plans get neither. Find your row before you start counting days, or you'll be calling Pawferred next Tuesday to demand a deadline they don't owe you.

The whole rule, explained

The rule changes two sets of things. Some are happening now, in 2026. The rest is new technology that has to be ready by 2027. The rest of this issue is just these changes happening to Biscuit the corgi.

Happening now (2026): Three changes to how your plan has to handle a request:

  • Faster answers. Your plan has to decide a normal request in 7 days. An urgent one in 3 days (72 hours). It used to take about twice as long.

  • A real reason for a "no." If your plan says no, it has to tell you the exact thing that was missing. Not just "we don't think you need it."

  • A public scoreboard. Once a year, every plan has to post its own numbers: how often it says yes, how often it says no, how fast it answers. Now anyone can look.

Coming in 2027 four new APIs: First, what's an API? It's a way for two computer programs to talk to each other. Instead of a person logging into a website to check something, one program just asks another and gets a reply, with no person in the middle. The rule makes insurers build four of these. Each one connects two different people.

  • Prior Authorization API (your doctor's computer and your plan). This is the big one, and it does two jobs.

    • First, before anyone submits a thing, the plan's software can tell the doctor's software whether a service even needs prior auth and exactly which documents to send. Today that answer is buried in PDFs, portals, and phone calls, so offices often learn what was required only after a denial.

    • Second, the office submits the request from its own software and gets the plan's answer back the same way. The decision can still take the normal few days, because a person may still have to look at it. What changes is that you know the rules going in, with fewer logins and faxes

  • Provider Access API (your doctor and what your plan already knows). Your plan already has a lot of your history: old visits, lab results, things it already said yes to. Your doctor often can't see any of it without calling. This lets the doctor pull it straight from the plan, instead of asking you to remember. (You can tell the plan to keep it private if you'd rather.)

  • Patient Access API (you and your plan). Your plan's app already shows your claims. This adds your prior approvals too. So you can open the app and see "MRI approved" or "denied, we need more paperwork," instead of waiting on hold.

  • Payer-to-Payer API (your old plan and your new one). When you switch plans, your history usually gets left behind, so the new plan starts from nothing. This lets your new plan grab the last five years from your old one, if you say yes. Then you don't have to prove everything all over again.

One thing the headlines skip: none of this is about prescription drugs. Those are left out. The faster answers, the clear reasons, the new apps, all of it is for medical care like Biscuit's MRI. Not the medicine your pharmacy is waiting on.

Sage submits the request

Dr. Singh writes the MRI order and hands it to Sage. Old way, Sage logs into Pawferred's portal, hunts for Biscuit's history, and rekeys it. New way, one of the 2027 APIs (the Provider Access API) lets her pull Biscuit's payer-held records straight into her own system. The labs Pawferred already has. The prior auth from his ER visit. Less re-faxing the same chart the insurer already owns.

Otis opens the file

Sage submits. A clock starts at Pawferred. Under the old Medicaid managed care standard, a decision could take up to 14 days. Now Otis has 7 calendar days for a standard request and 72 hours for an urgent one (source: CMS). Not business days. Calendar days. The clock doesn't care whether the request came by fax, portal, or Sage reading the form out loud over the phone.

The request itself rides another 2027 piece, the Prior Authorization API. Before Sage submitted anything, it could tell her two things she used to dig for: whether the MRI needed prior auth at all, and the exact documents to attach. Then it carried the request and Otis's answer back through the same pipe, instead of the old mess of portals and PDFs.

Here's what changes Otis's job. If he denies, he now has to name the specific clinical reason. Not "lacks medical necessity" with nothing attached (source: CMS). The actual criterion Biscuit's chart didn't meet. A vague denial used to be almost impossible to appeal. A specific one hands Sage and Dr. Singh something to push on.

And there's a scoreboard now. Pawferred has to publicly report its prior auth stats every year: approval rates, denial rates, decision times. The first reports were due March 31, 2026 (source: CMS).

The 2027 piece

Zoom out from the ankle.

The 2027 half is what insiders are losing sleep over. In 2024, only 35% of medical prior auths were fully electronic, and the average portal request ate 16 minutes (source: 2024 CAQH Index).

After January 2027, covered insurers have to expose all of this through standardized FHIR connections, the same plumbing across every payer, so the whole back-and-forth runs software to software instead of a human logging into ten different portals. CMS is also nudging adoption with a new measure that asks clinicians and hospitals to attest they sent at least one prior auth through the API. Sounds minor. It's the lever that gives a health system a reason to lean on Epic, Athena, and its RCM vendors to actually build this, instead of leaving it on a roadmap forever. And the Patient Access API means Biscuit himself will eventually open his plan's app and see "MRI auth: approved, valid until June 30" instead of calling to ask.

Wait, what's FHIR?

Fair question, because it's the load-bearing piece and nobody explains it. FHIR (pronounced "fire," which is the most exciting thing about it) is an agreed-on format for health data. Think of it as a standard plug. Right now, every connection between a doctor's software and a payer's system is a custom one-off, a different adapter for every payer. FHIR is the plug they all agree to use, so any doctor's system can talk to any payer's without building a new adapter each time. The clinical data moving through it follows a shared list too, called USCDI, so "your records" means the same set of fields at every plan instead of a different shape from each one.

On top of FHIR sit three pre-built recipes for prior auth, the Da Vinci guides. One checks whether a service needs auth (CRD). One collects the exact documents required (DTR). One submits the request and carries the answer back (PAS). That's the "does this need auth, what docs, here's the request" chain from Otis's desk, with its real names.

How it lands for Biscuit

Friday afternoon, three days after Sage hit send, Pawferred approves the MRI. Biscuit's booked for Tuesday. Under the old timeline he'd likely still be waiting.

One more piece, and it's why Medicaid is the right example. Medicaid coverage changes a lot. People lose one plan and land on another. When Biscuit switches to a new plan, the Payer-to-Payer API (starts 2027, and he has to opt in) lets that new plan pull his last five years of claims and prior auth history. So he doesn't start from zero and re-prove the ankle all over again.

Where I plant my flag

This rule speeds the decision up and drags it into the open. The insurer still decides what's covered, off the same medical policy it used in December, and CMS didn't touch that. What CMS touched is everything around the decision. Right now, the call comes faster, in writing, with a real reason for a no, and the plan's whole track record gets posted in public once a year. By 2027 it goes further. The plan has to publish, up front, which services even need prior auth and what documents they take, instead of leaving the office to find out by getting denied. And the stuff that used to be scattered across portals, faxes, and PDFs lands in one place a provider can reach.

That's the real shift, and it's bigger than it sounds. A denial you can see and pull the paper on is one you can fight. Otis can still say no. He just has to say it faster, in writing, and in public, where anyone can count how often he does.

If your work touches payer policy or market access

This is the part to read twice. Three moves, each with a reason.

  1. Pull the public reports and benchmark your book: As of March 31, 2026, every covered plan's prior auth stats are published, by plan, by category, refreshed yearly. You always knew which plans dragged their feet on imaging. Now it's a number instead of a hunch. Pull the first round and rank every plan you sell into, so your value story runs on the payer's actual behavior instead of a rep's memory.

  2. Audit the endpoints, not the PDFs: Today Pawferred's MRI policy sits in a PDF four clicks deep. After 2027, the operational version, which services need auth and what documents they require, lives in an endpoint Sage's software queries in real time. When the PDF and the endpoint disagree, the endpoint wins, because that's what the provider sees at the point of order.

  3. Plan for two worlds: A product that sails through on Biscuit's Medicaid plan can still hit a wall on the employer plan covering most of working America, because that plan isn't covered. You're running two access strategies for the next few years whether you budgeted for it or not.

Here's the catch the standardization talk hides: The APIs make the pipe the same. They don't make the requirements the same. Each payer can still ask for different documentation and apply different criteria, and your team still has to turn all of it into rules your own system can actually run. That translation is the real work, and it's what Converus.ai does. It takes each payer's requirements, normalizes them into one consistent format, and applies them across your whole org, so a forty-person team runs the same rules instead of forty people reading forty different PDFs. When a payer changes something, you catch it the afternoon it happens, not three weeks later in a denial.

What to do this week

If you're a patient: pull your insurance card and match it to the list above. If you're covered and waiting on an auth, count the days. Seven calendar, or 72 hours urgent. Past that with no answer is a rule violation worth a phone call.

If you run a clinic or billing desk: build the deadline into your work queue so the system flags a late payer instead of your staff guessing when to follow up. And start routing the new specific denials by reason: resubmit with the missing document, appeal, or fix the code, instead of calling to ask what "not medically necessary" meant this time. (Past a couple of staff, the hard part is keeping everyone on the same current rules for each payer, which is the specific job Converus does in one place.) Doctors still average 39 prior auths a week and 13 hours on them (source: AMA 2024). The clock helps. The volume is still brutal.

Before and after, on one page

That's CMS-0057-F. The countdown is already running on Otis's desk.

That's issue one. Hit reply — I read everything, and the best questions become the next lesson.

— Shivang

Names note: All insurance companies and clinics in pre·imbursed are fictional. We use made-up names so we can teach honestly without dragging any real company.

Sources cited in this issue (full reference list)

For readers who want to dig deeper, here's every source linked in the body of this issue:

  1. CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) Fact Sheet. The primary official document for the rule. Covers who's affected, the 72-hour and 7-calendar-day timeframes, the denial transparency requirement, and the API implementation deadlines. https://www.cms.gov/newsroom/fact-sheets/cms-interoperability-prior-authorization-final-rule-cms-0057-f

  2. CMS Prior Authorization API FAQ. The official Q&A on the API requirements and the March 31, 2026 public reporting deadline. https://www.cms.gov/priorities/burden-reduction/overview/interoperability/frequently-asked-questions/prior-authorization-api

  3. CMS Interoperability General FAQ. The official source confirming that employer-based group health plans are not covered by the rule. https://www.cms.gov/priorities/burden-reduction/overview/interoperability/frequently-asked-questions/general

  4. CMS State-Based Exchanges Directory. The official list of the 21 states (plus DC) running their own marketplace for plan year 2026. https://www.cms.gov/cciio/resources/fact-sheets-and-faqs/state-marketplaces

  5. KFF, Medicare Advantage in 2026: Enrollment Update and Key Trends. Source for the 55% MA enrollment statistic. https://www.kff.org/medicare/medicare-advantage-in-2026-enrollment-update-and-key-trends/

  6. Virginia Department of Medical Assistance Services (DMAS) Implementation Bulletin. State-level implementation document confirming the 14-day-to-7-day shift in standard prior auth timeframes.https://vamedicaid.dmas.virginia.gov/bulletin/interoperability-and-prior-authorization-final-rule-implementation-update

  7. 2024 CAQH Index Report. Source for the 35% electronic prior auth adoption rate and the 16-minute average portal transaction time.https://www.caqh.org/hubfs/Index/2024%20Index%20Report/CAQH_IndexReport_2024_FINAL.pdf

  8. AMA 2024 Prior Authorization Physician Survey. Source for the 40 prior auths per week and 13 hours of staff time statistics. https://www.ama-assn.org/practice-management/prior-authorization/fixing-prior-auth-nearly-40-prior-authorizations-week-way