Route 1: API
Impacted payers, Jan 1, 2027
Guide · Prior authorization
Automated prior authorization in 2027: API, voice or portal, and the order to run them
Short answer: the payer decides the first route. Impacted payers owe an API from January 1, 2027 under CMS-0057-F; commercial employer plans owe a portal and a phone number; drugs sit on a separate proposed track to October 1, 2027. Run API, then voice, then portal, and log every route.
CMS-0057-F · API Jan 1, 202772 h expedited · 7 days standardHL7 Da Vinci CRD · DTR · PASCMS-0062-P · drugs, proposed
Focus
Prior auth
Audience
Auth desk
Framework
CMS-0057-F
Effective date
Jan 1, 2027
Payers
MA · Medicaid · QHP
Length
7 min
Jan 1, 2027
Prior Authorization API required of impacted payers under CMS-0057-F [1]
72h / 7 days
Expedited and standard decision clocks already in force for impacted payers other than QHP issuers [1]
Oct 1, 2027
Proposed compliance date for electronic prior authorization of drugs, CMS-0062-P, proposed not final [2]
24of 35
Patients whose authorization question the precedence resolver answered at high or medium confidence on a therapy file; the 271 alone answered 6
Three routes to a prior authorization answer
None covers every payer. The order is set by what the payer is obliged to offer.
Route 2: Voice
Where no transaction carries it
- CPT-level rules at a commercial plan, peer-to-peer scheduling, a request stuck past the clock
- Every quote reconciled to the structured record
- Every call leaves a reference number and timestamp
Route 3: Portal
Last and logged
- Submission and attachments where no API exists
- Never for status when a 276/277, an API or a logged call can answer
- Most fragile to automate: the page changes without notice
Status first
Cheapest automation
- Most daily minutes go to asking where a request sits
- Automate status before submission
What the API gives an authorization team, function by function [1]
| API function | Replaces | What to store |
|---|---|---|
| Covered items and services list | The call to ask whether this code needs an authorization | Required or not, per payer and code, with the date checked |
| Documentation requirements | The denial for missing records | The payer's list mapped to your template fields |
| Request and response | Portal entry or fax | Request ID and time sent |
| Approval with end date or circumstance | The letter that arrived after units were used | End date or trigger on the authorization record |
| Denial with a specific reason | The generic code | Reason text, so the appeal starts from it |
Limits: payers outside the rule, the drug exclusion, your own connection. CMS says to confirm readiness with the EHR vendor, including integration capability and any upgrade or module costs [3].
What runs first, payer by payer
The table we build for a multi-site group before January: one row per payer, the answer to each question in order [1].
Payer typeRequired? and submitStatus and denial reason
Medicaid MCO, Medicaid and CHIP FFSImpacted
Required and submitAPI covered-services list; API submission, portal for attachments until the API carries them
StatusAPI with 72-hour and 7-day clocks logged; denial reason from the API
Medicare AdvantageImpacted
Required and submitAPI covered-services list; API or delegated vendor channel
StatusAPI, then portal; denial reason from the API
Exchange QHP issuerImpacted, no clocks
Required and submitAPI covered-services list; API submission
StatusAPI; the decision clocks do not apply; denial reason from the API
Commercial employer and self-fundedOutside the rule
Required and submitPayer rule table with a source date, then a call; portal or fax to submit
Status276/277 where claim-linked; voice; portal. Denial reason by call, documented in writing
Any payer, drugsSeparate track
Required and submitPharmacy channels today
StatusPharmacy channels; a specific denial reason proposed from October 1, 2027 under CMS-0062-P [2]
Authorization question on a 35-patient therapy file, our own desk, August 2026
Our eligibility verification workbench answers coverage with a 270/271; a precedence resolver layers payer rules on top for the authorization question. From January the API is one more input to that resolver.
Patients with the authorization question answered, by method
Internal measurement on one physical therapy file, not a client outcome. The 271 is the input; payer rules layered on top are the resolver.
271 aloneeligibility response only
6 of 3517%
271 + precedence resolverhigh or medium confidence
24 of 3569%, 4x the 271 alone
Routed to the payer portalquestion already written
11 of 3531%, named portal per patient
010203035 patients
271 aloneResolver answerPortal hand-off
Four rules for voice and portal
Our prior authorization automation treats the portal as one channel beside fax and EDI: packet from the record, receipt logged, status polled, reauthorization triggered when units run down.
Transaction first
- Send the 270/271, 276/277 or API call first; call when the response is thin
- Same rule as our voice versus 270 guide and 276/277 note
Reconcile every quote
- A representative's answer never overrides a 271 or API response without a person seeing both
- We publish routing rules, not voice outcome numbers; we do not have them yet
Receipt on the record
- Portal reference and receipt captured at submission
- Reference number, representative name and timestamp on every call; a call with no record did not happen
Received is not decided
- Received past the clock is an escalation in writing, citing the 72-hour or 7-day rule
- Review portal automation after every payer site change; a silent failure looks like a payer delay
Takeaway
The API shrinks the phone queue payer by payer, not all at once. Build the sequence per payer, log every route, and let each API go-live retire a column of calls.
Five steps, in order
Same pattern as our ABA MCO readiness map and the behavioral health API explainer.
- 1Tag every payerImpacted or not under CMS-0057-F
- 2Ask for go-live and test accessPayer API date and test access; will the EHR consume it, at what cost
- 3Open the ledgerRequest-to-decision: plan, code, standard or expedited, date sent, date decided, denial reason text
- 4Write the sequence tableTop fifteen payers, one row each, where the coordinators work
- 5Keep drugs separatePharmacy channels today; watch CMS-0062-P, proposed not final [2]
Checklist for the authorization desk
List the authorization payersTop fifteen by volume, tagged impacted or not.
Send three vendor questionsAPI go-live date, test access, and the cost of consuming the response in your system.
Start the request-to-decision ledgerOne row per request from today; the January baseline comes from it.
Pull last month of received-no-decision requestsAny past 72 hours or 7 days at an impacted payer is an escalation in writing.
Audit call notes for reference numbersCalls without a reference, name and timestamp are retrained this week.
Read the buyer-side viewOur 2027 eligibility system buyer's guide has the scorecard; the AI suite handles the claim once the authorization is on file.
Frequently asked questions
What is the best way to automate prior authorization in 2027?
Sequence the routes by payer. For Medicare Advantage, Medicaid, CHIP and exchange QHP payers, the CMS-0057-F Prior Authorization API is the first route from January 1, 2027. For commercial employer plans outside the rule, a payer rule table, the portal and a logged call remain the routes. Drugs stay on pharmacy channels under a separate proposed rule.
Does CMS-0057-F require my practice to use the API?
No. The obligation is on the payer to offer it. CMS encourages providers to request prior authorizations electronically beginning January 1, 2027 and to confirm readiness with their EHR vendor, including integration capabilities and any upgrade or module costs.
When should a voice agent be used for prior authorization?
After the transaction or API has been tried: for CPT-level rules at commercial plans, for payers with no electronic route, and for requests that sit past the decision clock. Every quoted value should be reconciled to the structured record and every call should leave a reference number and timestamp.
Are drug prior authorizations covered by the 2027 API?
No. Drugs are excluded from CMS-0057-F. CMS-0062-P, published April 14, 2026, proposes electronic prior authorization for drugs through the API and NCPDP standards beginning October 1, 2027. It is a proposed rule.
- CMS fact sheet, CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F), January 17, 2024
- Federal Register public inspection, CMS-0062-P, Interoperability Standards and Prior Authorization for Drugs proposed rule (published April 14, 2026)
- CMS, Electronic Prior Authorization overview (page updated October 21, 2026)
Checked October 25, 2026. Rules change; confirm against the source before relying on them. The 35-patient figures are an internal measurement from our own desk in August 2026, not a client outcome. We do not publish production outcome numbers for voice automation.
Want the per-payer sequence built for your authorization list?
We tag your payers under CMS-0057-F, write the API, voice and portal sequence for each, and open the request-to-decision ledger before January.