Buy CMS-0057-F APIs First, Then Add AI Prior Auth Review

CMS-0057-F requires prior authorization APIs by January 1, 2027 and does not require AI review. Payers should build the APIs first and add Cohere-style review only once clinicians sign every denial. Epic health systems should start with Epic's CRD checks.

By Rajesh Beri·November 20, 2026·15 min read
Share:
A hospital utilization review office at dusk: a nurse reviewer's desk with two monitors showing a patient chart and a request queue, a stack of faxed authorization forms beside an unused fax machine, a stethoscope restin

Illustration generated using AI

Federal rules require health plans to have prior authorization APIs running by January 1, 2027. They do not require AI review. Buy the API layer first, add AI review afterwards, and only once a licensed clinician signs every denial and you can prove it. For payers that means the FHIR plumbing from your clearinghouse or core platform now, and Cohere Health as the review layer when you are ready to govern it. For a health system on Epic, it means switching on Epic's own Coverage Requirements Discovery with your payers before you sign with anyone. Rhyme covers the payers Epic cannot reach yet. Waystar Auth Accelerate is the weakest buy here for an Epic shop, for reasons covered below.

Prices were checked on November 20, 2026. None of these vendors publishes a list price for its AI prior authorization product; every one runs through a sales conversation.

Product Side What you are actually buying Outcome the vendor publishes Price (Nov 20, 2026) Pick it if Skip it if
Cohere Health Payer Clinical review and auto-approval, delegated UM or in-house software 85% approved in real time; 90% auto-approval (vendor claims) Contact sales You run UM yourself and want approvals automated with clinicians owning denials Your FHIR APIs are not live, or you have no audit process for AI-assisted decisions
Availity (AuthAI + FHIR APIs) Payer and provider network CMS-0057-F APIs, a multi-payer FHIR network, AI recommendations that never deny AuthAI "does not auto-deny" (vendor policy) Payer side: contact sales. Provider portal: free for providers through payer sponsorship You need the compliance APIs and broad provider reach fast You want a standalone clinical review engine
Epic (Payer Platform + CRD) Both, inside the EHR Real-time "is auth required" checks and payer-provider exchange in Epic Ochsner and Humana completed 53% of prior authorizations instantly on Payer Platform (Epic) Not published Your health system or plan already runs Epic Your payers are not connected to Payer Platform yet
Rhyme Provider EHR-integrated submission, status tracking, gold-card logic Not independently published Contact sales You are not on Epic, or many of your payers still run portals Every payer you bill is live on FHIR APIs through your EHR
Waystar Auth Accelerate Provider Submission automation inside Waystar's revenue cycle platform 70% less submission time and 85% auto-approval at launch; later "over 90%" auto-approval Contact sales You already run Waystar for claims and are not on Epic You are an Epic shop facing payers' 2027 APIs
Humata Health Both Payer review contractor (WISeR Oklahoma) plus a provider portal Not independently published Contact sales You are a smaller practice that needs a portal without EHR work You need a long public track record

The workload behind every judgment on this page: a regional health plan with Medicare Advantage and Medicaid managed care lines, so CMS-0057-F applies in full, and a multi-hospital Epic health system that submits to that plan and a dozen others.


What CMS-0057-F Actually Requires by January 1, 2027

CMS-0057-F is a federal rule that requires specific payers to run FHIR APIs for prior authorization and to answer requests on fixed deadlines. It does not mention AI review at all, and most of the confusion in this market starts there.

The CMS fact sheet names the 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 federal exchanges. By January 1, 2027 they must run a Prior Authorization API that lists which items and services need approval, tells the provider what documentation is required, and returns a decision with a denial reason. Three more APIs come with it: Patient Access, Provider Access and Payer-to-Payer.

The decision-time limits arrived a year earlier. Starting January 1, 2026, impacted payers other than exchange QHP issuers must decide expedited requests within 72 hours and standard requests within seven calendar days. They also have to post prior authorization metrics publicly, per the same fact sheet. The rule leaves out drugs, so a pharmacy benefit prior authorization tool is a separate purchase.

CMS points to the HL7 Da Vinci implementation guides for the build, on its APIs and implementation guides page. There are three of them:

  1. Coverage Requirements Discovery (CRD) answers "does this order need prior auth?" inside the EHR while the clinician is ordering.
  2. Documentation Templates and Rules (DTR) sends the payer's documentation questionnaire to the EHR and fills it in from the chart.
  3. Prior Authorization Support (PAS) submits the request and returns the decision.

HIPAA still names the X12 278 transaction as the standard for prior authorization. CMS has said HHS will use enforcement discretion for covered entities that run an all-FHIR Prior Authorization API without the 278. Take that seriously during scoping, because some vendor proposals still quote a 278 translation layer as mandatory.

None of this calls for a model. A payer can meet every 2027 obligation with a rules engine that publishes its coverage list and a clinical team that answers within the time limits. The AI products sit on top.


Payer-Side Review: Why Cohere Health Leads and What It Will Not Tell You

For a health plan that wants automated clinical review, Cohere Health has the clearest design: AI approves, clinicians deny. Cohere's provider page says only human clinical experts make denial decisions. Its decision product page claims 85% of prior authorizations approved in real time, and its in-house UM page claims an auto-approval rate of 90%. Cohere can also be bought as delegated utilization management, where its own clinicians do the review, or as software your UM team runs.

Its distribution is the other reason it leads. Epic Payer Platform added Cohere's AI-driven prior authorization in 2024, per Becker's, which puts it inside the EHR most large health systems run. CMS also chose Cohere as one of the six WISeR vendors for traditional Medicare prior authorization, assigned to Texas.

Raise two problems with Cohere's published numbers in diligence. First, both approval rates are vendor claims with an undefined denominator. Is 85% measured on the requests Cohere receives after your plan's own exemptions, or on every request? If your plan already gold-cards high-approval providers, the requests left over approve at a lower rate, and Cohere's figure will not carry over to you.

Second, "AI never denies" is a policy, and you cannot audit a policy. Cigna and Aetna have made the same statement, as TechTarget's reporting notes. The policy holds only if the clinician who signs a denial saw the chart, spent real time on it, and was not handed a ranking that marked the case as a likely denial before they opened it.

Who should not buy Cohere now: a plan whose Prior Authorization API is not live yet. Cohere will not shorten your 2027 build, and running the API build alongside an AI review rollout doubles your change management in the year CMS starts reading your public metrics.


Availity and Epic: The Compliance Layer Most Buyers Should Start With

Most payers should buy the CMS-0057-F API layer from their existing network or platform vendor first, and Availity is the default choice because providers already use it. Availity's AuthAI page describes its prior authorization APIs for the rule (CRD, DTR and PAS), with AuthAI recommendations returned to the EHR or the Availity portal. It also says AuthAI does not auto-deny. In September 2026 Availity announced progress on a multi-payer FHIR network intended to cut point-to-point onboarding, authentication and testing.

Availity's reach also gets AI into the exam room. In January 2026 Abridge announced a collaboration with Availity with the goal of enabling payer determination during the visit. If you already run Abridge, ask where that integration stands.

On the provider side, the Availity Essentials portal is free to providers because payers sponsor it, per Premera's provider FAQ. Coverage varies by plan; Premera, for example, excludes some lines from prior authorization on Availity.

Epic is the other compliance path, and for a health system on Epic it should come first. In August 2026 Epic went live with real-time CRD checks at Ochsner Health, Froedtert ThedaCare, Denver Health and Summit Health, built with UnitedHealthcare, Aetna and Network Health. Clinicians see in the order whether approval is needed. Epic handles the "is auth required" question today, and the DTR and PAS steps depend on each payer.

Who should not lead with Availity: a plan that wants one vendor for both the APIs and a full clinical review engine. AuthAI produces recommendations, and you still need a UM product or your own clinicians behind it. Who should not lead with Epic: a health system whose largest payers are not on Payer Platform. Check with each of your top ten payers before assuming Epic covers them.


Provider-Side Submission Tools: Rhyme Wins, Waystar Loses for Epic Shops

Provider-side tools automate the request your staff would otherwise key into a payer portal, and their value shrinks as each payer turns on its 2027 APIs. Buy them on short terms.

Rhyme is the pick for a health system that is not on Epic, or one with many payers outside the CMS rule (self-funded employer plans and smaller commercial carriers). Its pitch is touchless submission plus a gold-carding approach that exempts providers with consistently high approval rates. It publishes no independently audited outcome figures, so ask for your peers' payer-by-payer touchless rates before you sign.

Waystar Auth Accelerate is the loser in this comparison for an Epic health system. Waystar's launch release claimed a 70% reduction in submission time and 85% auto-approval, and later award materials said "over 90%". That is three different headline figures from one vendor in one year. More importantly, an Epic shop gets the CRD check from Epic and, through 2027, the PAS submission from each payer's own API, so Waystar ends up buying you a second path to the same payers. The case for Waystar is narrower: a non-Epic provider that already runs Waystar for claims and eligibility gets authorization automation without adding another vendor. Waystar publishes no prices and routes buyers to a demo request.

Humata Health is the newcomer on both sides. CMS chose it as the WISeR contractor for Oklahoma, and in June 2026 it opened early access to a web portal for independent practices and specialty clinics. R1 has since acquired Humata. A small practice with no EHR integration budget can start there. A large system should wait for a longer public record.

Who should not buy any standalone provider tool on a three-year contract in 2026: anyone whose top payers are among the early adopters CMS named in May 2026, which also include Epic, Oracle, athenahealth and Meditech. Those connections are being built for you.


The Rules on AI and Denials You Must Design For

Every serious jurisdiction now says the same thing: an algorithm can help, but a qualified human makes the adverse decision, based on the individual patient. Build that into your contract and your audit trail, because a vendor's policy statement is not evidence.

For Medicare Advantage, CMS's February 2024 FAQ allowed plans to use algorithms and AI to assist coverage decisions, but held them to the individual patient's circumstances and barred tools from changing publicly posted coverage criteria. An algorithm that predicts outcomes from a broad population dataset does not meet that standard on its own.

States have gone further. California's SB 1120, in force since January 2025, requires a licensed physician or qualified provider to make any denial, delay or modification based on medical necessity. KFF's survey of federal and state protections tracks similar rules elsewhere, and Becker's counted seven state AI health insurance laws passed in 2026 alone. ERISA self-funded plans sit outside most of these, so a national plan ends up running several rule sets.

The enforcement risk shows up in court. In February 2025 a federal judge in Minnesota let breach of contract claims proceed against UnitedHealth over its alleged use of the nH Predict algorithm in Medicare Advantage post-acute denials. UnitedHealth's naviHealth unit has said the case has no merit. The Senate Permanent Subcommittee on Investigations' October 2024 majority staff report found that UnitedHealthcare's post-acute denial rate rose from 10.9% in 2020 to 22.7% in 2022, a rise the report ties to the company's automation initiatives. UnitedHealthcare said the report mischaracterized its clinical practices. Physicians have noticed: 61% told the AMA in February 2025 they fear payer AI is raising denials.

In practice, a defensible deployment logs four things for every adverse decision: the reviewer's licence and specialty, the time they had the chart open, whether the AI's output was visible to them, and the criteria they cited. If your vendor cannot export those fields, it fails the requirement regardless of how good its approval rate is.


How to Verify the Auto-Approval Numbers

An auto-approval rate means nothing until you know its denominator, its exclusions and the appeal overturn rate behind it. Ask every vendor for three figures computed on your own data in a pilot:

  1. Touchless rate on all requests, measured before your existing exemptions remove the easy ones.
  2. Median and 90th percentile decision time against the 72-hour and seven-day limits.
  3. Overturn rate on appeal for cases the AI routed toward denial review. A high overturn rate means clinicians are signing whatever the model hands them.

You can now compare against public baselines. Impacted payers had to post their first metrics by March 31, 2026, and KFF's analysis found the data aggregated across all services, with no breakdown by service type. Read it as a floor, and treat a vendor's service-level claim as unproven until your pilot reproduces it.

The industry has also made public promises that you can hold your vendor to. The AHIP pledge of June 2025 committed plans covering 257 million people to answer at least 80% of electronic prior authorization approvals in real time by 2027, counting only requests submitted with complete clinical documentation. AHIP and the Blue Cross Blue Shield Association later reported an 11% cut in services requiring prior authorization. If your plan signed the pledge, the 80% figure becomes your contract target.


Who Should Buy Only the Compliance APIs and Skip AI Review for Now

A plan that has not shipped its Prior Authorization API, cannot yet export reviewer audit fields, or does business in California should buy the API layer only and revisit AI review in late 2027. That is the right call for most Medicaid managed care plans and smaller MA plans this year.

The reasoning is sequencing. The API is mandatory and dated. AI review is optional and carries legal exposure that grows with every state law. A plan that adds an AI review vendor before its FHIR endpoints are stable ends up debugging two systems at once while its first decision-time metrics are public. Wait a year and you buy AI review against twelve months of your own baseline data, which is the only honest way to judge a vendor's approval rate.

The exception is a plan with a staffing crisis in utilization review. Delegated UM from Cohere, where the vendor's own clinicians make the decisions, can make sense now because it buys capacity, and the model comes along with it.


The Decision: Criteria That Predict Regret

The buyers who regret these purchases usually made one of four mistakes:

  1. They bought AI review to meet the CMS rule. It meets nothing. Check that your proposal separates API deliverables from review features line by line.
  2. They signed a provider-side tool for three years just as their payers' FHIR APIs were going live. Keep terms to 12 to 18 months with a price step-down as payers connect.
  3. They accepted "AI never denies" without the audit export. Write the four audit fields into the contract.
  4. They compared approval rates without a shared denominator. Run a pilot on your own request mix.

What changes the answer: if CMS moves the January 1, 2027 date (watch the CMS-0062-P proposed rule, which proposes revisions to metrics reporting), or if your EHR is not Epic, in which case Rhyme moves up and Epic drops out.

This Week: List your top ten payers by volume and ask each one which Da Vinci APIs it will have live on January 1, 2027 and through which network.

This Month: For a payer, separate your CMS-0057-F scope from any AI review RFP and fund the API build first. For a provider on Epic, ask your Epic team which of your payers are on Payer Platform CRD today.

Before Contract Signature: Require a pilot on your own data reporting touchless rate, decision time and appeal overturn rate, plus a reviewer audit export for every adverse decision.

The Bottom Line

Electronic claims went the same way in the 2000s: the standard transaction became mandatory first, and the software that made it smarter was worth buying only once it ran on top of that standard. Prior authorization is following the same order. Get the Da Vinci APIs working with your largest payers, measure your own baseline, and buy AI review against numbers you collected yourself.

Continue Reading

Share:

Frequently Asked Questions

Does CMS-0057-F require health plans to use AI for prior authorization?

No. CMS-0057-F requires impacted payers to run FHIR-based Prior Authorization, Provider Access, Patient Access and Payer-to-Payer APIs by January 1, 2027, and to meet 72-hour expedited and seven-day standard decision limits from January 1, 2026. AI review is optional and sits on top of those APIs.

Which payers are covered by the CMS prior authorization rule?

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 federal exchanges. Prescription drugs are excluded, and self-funded employer plans are not impacted payers.

Can AI deny a prior authorization request?

In practice, no. CMS guidance requires Medicare Advantage decisions to rest on the individual patient's circumstances, and California's SB 1120 requires a licensed physician or qualified provider to make any medical necessity denial. Vendors such as Cohere Health and Availity say their AI approves or recommends but never denies.

What are the Da Vinci implementation guides for prior authorization?

Three HL7 FHIR guides: Coverage Requirements Discovery (CRD) tells the clinician in the EHR whether prior auth is needed, Documentation Templates and Rules (DTR) collects the required documentation from the chart, and Prior Authorization Support (PAS) submits the request and returns the decision.

Should a health system on Epic buy a separate prior authorization tool?

Usually not first. Epic's real-time Coverage Requirements Discovery checks went live in 2026 at health systems including Ochsner and Denver Health. Confirm which of your top payers connect through Epic Payer Platform, and use a tool like Rhyme only for the payers that do not.

Newsletter

More on Automation & Workflows, every Sunday

The week's enterprise AI news, Automation & Workflows included, in one Sunday email.

Weekly, free. Unsubscribe any time. Privacy