Home / ASP Insights / ABA billing
Insight · CMS-0057-F and ABA authorizations

ABA prior authorization API: MCO readiness for January 1, 2027

Short answer: Medicaid MCOs, state FFS programs and Medicare Advantage plans must run a Prior Authorization API from January 1, 2027. Scope, what it returns, and six questions for every MCO.
CMS-0057-F · final Jan 17, 2024 72 h expedited · 7 days standard Drug PA excluded · CMS-0062-P proposed

October 27, 20267 min readASP-RCM Solutions

Rule
CMS-0057-F
Effective
Jan 1, 2027
Payers
MCO · FFS · MA
Clocks
72 h / 7 days
Codes
97151 to 97158
Questions
6 per MCO
Jan 12027
Prior Authorization API required under CMS-0057-F [1]
72h / 7 days
Expedited and standard clocks since January 1, 2026 [1]
Mar 312026
First prior authorization metrics due on payer websites [1]
6questions
In writing to every plan that authorizes ABA
Who must run the API

Scope first: your Medicaid MCOs are in, self-funded plans are out

Impacted payers are a defined list [1]; a commercial API is a business decision, not a January 1 obligation.

Payer typeIn scopeWhat it means for ABA authorizations
Medicaid managed care plan (MCO)YesDecision clocks, denial reasons and the API all apply
State Medicaid fee-for-serviceYesSame obligations, via the state or its vendor
CHIP FFS and CHIP managed careYesSame obligations
Medicare AdvantageYesRarely authorizes ABA, but in scope where it does
QHP issuer on a federal exchangeAPIs yes; clocks noAPI and denial-reason rules apply; the clocks do not
Employer and self-funded commercial plans, TRICARENoContract and plan policy govern; ask, do not assume
Takeaway

Nearly every ABA authorization from a Medicaid MCO is covered; nearly none from a self-funded employer plan is.

What the API must return

Covered services, documentation list, and a response that says one of three things [1]

Approve

Response

  • With the date or circumstance under which the authorization ends [1]

Deny

Response

  • With a specific reason for the denial [1]

More information

Response

  • A structured request for what is missing [1]

Documentation list

Before you submit

  • The API identifies documentation requirements for approval [1]
The calendar

CMS-0057-F on an ABA calendar

  1. 1
    Jan 1, 2026Decision clocks and specific denial reasons generally begin [1]
  2. 2
    Mar 31, 2026First annual PA metrics on payer websites
  3. 3
    Apr 14, 2026CMS-0062-P, drug PA, published (proposed) [4]
  4. 4
    Jan 1, 2027Prior Authorization, Patient Access, Provider Access, Payer-to-Payer APIs required
  5. 5
    CY 2027 to 2028Hospital electronic PA measure: optional CY 2027, mandatory CY 2028 (FY 2027 IPPS) [3]
The clocks

Hours, not business days: already enforceable

Decision and planning clocks in hours

Expedited decision72 hours
72 h43% of standard
Standard decision7 calendar days
168 h100%, baseline
Reauthorization leadfrom the API end date
30 days720 h, 4.3x standard
072 h168 h
ExpeditedStandardPractice lead time
The readiness map

Six questions for every MCO, before January

QuestionWhy it mattersEvidence to keep
Where are your published prior authorization metrics for 2025?Due on the payer website March 31, 2026 [1]URL and the ABA-relevant approval, denial and timeliness figures
What are your measured standard and expedited decision times for ABA codes 97151 to 97158?72 hours and 7 days since January 1, 2026 [1]Your own request-to-decision log by plan
Will your Prior Authorization API be live on January 1, 2027, and through which implementation guides (CRD, DTR, PAS)?The API obligation; the test kits CMS names [1] [3]Written answer, go-live date, sandbox access
Which documentation requirements for ABA will the API expose?The API must identify documentation requirements [1]The list, against your treatment plan template
How will the API communicate the end date of an approval and the specific reason for a denial?Required response content [1]Sample responses to map into your authorization ledger
Which clearinghouse, portal or vendor paths will you support alongside the API?Provider-side connection is not mandated [3]Your fallback workflow per plan
Takeaway

The API will not approve more hours. It will tell you faster, in a structured form, why a plan said no. Build the ledger to capture that reason and the clinical team to answer it.

What to do this week

Five steps before January

Send the six questions in writing in NovemberReply date before the holidays.
Start a request-to-decision log nowBy plan and by standard or expedited, so January has a baseline.
Rebuild the authorization ledger for API fieldsDecision, end date, denial reason text, documentation requested; see the multi-location operating model.
Align the treatment plan template to 2027 state rulesIndiana caregiver coaching hours and RBT supervision ratio; North Carolina three-month reauthorization above 16 hours a week [5] [6]; more in the ABA payer matrix.
Pick the connection path per planPM vendor, clearinghouse or portal; name the fallback.
FAQ

Frequently asked questions

Does CMS-0057-F require Medicaid MCOs to run a prior authorization API for ABA?

Yes. Medicaid MCOs are impacted payers; from January 1, 2027 they must run a Prior Authorization API that lists covered services, identifies documentation requirements, accepts requests and returns an approval with its end date, a denial with a specific reason, or a request for more information. Drug prior authorizations are excluded.

What are the prior authorization decision deadlines under CMS-0057-F?

72 hours expedited, seven calendar days standard, for impacted payers other than QHP issuers on the federal exchanges; generally since January 1, 2026, with a specific reason for each denial.

Do ABA providers have to connect to the payer API?

No. The obligation sits on the impacted payer. CMS encourages electronic requests, and an electronic PA measure applies to MIPS clinicians and hospitals, but an ABA practice can keep a portal or vendor path while it plans a connection.

Are commercial ABA authorizations covered by the rule?

Only if the plan is a QHP issuer on a federally facilitated exchange. Employer-sponsored and self-funded plans and TRICARE are outside CMS-0057-F; contract and plan policy govern.

Does the API change the clinical criteria for approving ABA hours?

No. It standardizes how requirements are published and decisions returned. Approved hours still follow the plan's medical necessity criteria and state rules such as Indiana's lifetime allocation or North Carolina's reauthorization cycle.

Sources
  1. CMS fact sheet, CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F), January 17, 2024
  2. CMS, Interoperability and Prior Authorization Final Rule (CMS-0057-F) overview page
  3. CMS, Electronic Prior Authorization overview (page updated October 21, 2026)
  4. Federal Register, CMS-0062-P, Interoperability Standards and Prior Authorization for Drugs proposed rule (published April 14, 2026)
  5. Indiana IHCP bulletin BT202627, IHCP announces changes to applied behavior analysis (ABA) therapy services (February 26, 2026)
  6. NC Medicaid bulletin, Updated reminder: requirements for Research-Based Behavioral Health Treatment service delivery (August 31, 2026)

Checked October 27, 2026. Confirm against the source; proposed rules are marked proposed.

Related

Want your MCO readiness questions sent and tracked for you?

We send the six questions, log the answers, and rebuild your authorization ledger for API responses.