Approve
Response
- With the date or circumstance under which the authorization ends [1]
Impacted payers are a defined list [1]; a commercial API is a business decision, not a January 1 obligation.
| Payer type | In scope | What it means for ABA authorizations |
|---|---|---|
| Medicaid managed care plan (MCO) | Yes | Decision clocks, denial reasons and the API all apply |
| State Medicaid fee-for-service | Yes | Same obligations, via the state or its vendor |
| CHIP FFS and CHIP managed care | Yes | Same obligations |
| Medicare Advantage | Yes | Rarely authorizes ABA, but in scope where it does |
| QHP issuer on a federal exchange | APIs yes; clocks no | API and denial-reason rules apply; the clocks do not |
| Employer and self-funded commercial plans, TRICARE | No | Contract and plan policy govern; ask, do not assume |
Nearly every ABA authorization from a Medicaid MCO is covered; nearly none from a self-funded employer plan is.
Response
Response
Response
Before you submit
| Question | Why it matters | Evidence 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 |
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.
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.
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.
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.
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.
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.
Checked October 27, 2026. Confirm against the source; proposed rules are marked proposed.
We send the six questions, log the answers, and rebuild your authorization ledger for API responses.