Preparing For Changing ABA CPT Codes In 2027
Juan Pablo Montoya is Founder and CEO of Solum Health, which automates insurance verification and prior authorization with AI.
gettyWhen a code set changes, the first thing practice owners ask me is which codes are new. I understand why, but it’s the wrong place to start. A new code can’t really hurt you because your billing system has never seen it and will say so. Deleted codes are also noisy since the claim usually bounces within days.
What hurts is a code that keeps its number and changes what it means. That claim goes out clean, and you find out weeks later from a denial or an auditor’s question nobody on the team can answer.
On January 1, 2027, applied behavior analysis gets that kind of change. Speech therapy gets a big dose of the other kind.
The ABA Coding Coalition’s crosswalk spells out the ABA CPT code changes: six new codes, revised descriptors for 97151 through 97158 and two Category III codes deleted. The change that matters is 97155. Under the 2019 descriptors, it covered protocol modification by the behavior analyst, with or without directing a technician, so it was where the analyst’s own hands-on treatment got billed. Beginning in January, it will mean the analyst directing a technician, and the analyst’s direct treatment will get its own code (97173).
In speech, 92507 is deleted on January 1. ASHA described 10 replacements across five clinical categories, each built as a base code for the first 30 minutes plus an add-on for every additional 15 minutes. The group code, 92508, is revised into a stand-alone code. Outside Medicare, each payer decides when to add the new codes to its fee schedule.
This is a data problem before it’s a billing problem. If your system treats a CPT code as a plain label, “97155” in July and “97155” in January are the same string, and nothing downstream knows they describe different work. A code is really a definition with a start date. An authorization approved under last year’s definition doesn’t carry over to this year’s on its own.
The timing makes it worse. Most ABA authorizations I see run six months, so almost anything approved since midsummer will still be open in January. Those approvals funded 97155 hours that belong to two different codes from January 1, and unless the payer says otherwise in writing, the authorization won’t tell you how to split them.
The claim to worry about is the one that pays. If an analyst keeps billing hands-on treatment as 97155 out of habit, it matches the old authorization and goes through, and it stays wrong until someone reads it against the 2027 definition. The speech authorizations I see are usually written as a number of 92507 visits, which in January becomes a count of visits for a code that no longer exists.
Don’t expect payer reporting to flag any of this for you. The largest Medicaid-managed care insurers denied 14% of standard prior authorization requests in 2025, and the published figures can’t show which services those were. If the cutover produces a run of mismatches, you’ll see it in your own data or not at all.
This should be a single query: every authorization ending after December 31 that references 97151 through 97158, 0362T, 0373T, 92507 or 92508. If it turns into a week of opening PDFs and reading notes fields, that’s your real finding.
Your code table needs start and end dates, so a December session is read against the 2026 definition and a January session against the 2027 one. Keep last year’s descriptors instead of overwriting them because sooner or later, someone will ask you to justify a 2026 claim. Load the crosswalk as reference data that your claim logic actually reads.
HIPAA-covered payers must accept code sets valid on the date of service, but each one decides when it will cover, price and authorize the new codes. For a stretch, one payer may have 97173 loaded and priced while another hasn’t, so your system needs to know which payers have moved. Ask each one, in writing, how it will treat authorizations that cross January 1.
Splitting an authorization between technician direction and the analyst’s own treatment is a clinical call. Your behavior analysts have to make it, and the payer has to amend the authorization to match, ideally before the first January session.
While you’re asking, consider whether you also need the new code for non-face-to-face analyst work, 97180, which no 2026 authorization could have listed. For speech teams, the equivalent job is turning approved visits into base and add-on units.
Set up a weekly view of rejections, denials and authorization mismatches on every new and revised code, and keep it running through February. Put paid 97155 claims in that view, too. Nobody reviews claims that paid, which is exactly where the habitual billing errors will sit.
Most of January’s coding problems will announce themselves with a rejection. The expensive one won’t; it’ll be a familiar number on an authorization you approved months ago now describing different work. I’d treat the cutover as a data migration rather than a coding update, and I’d start that inventory now while payers still have time to process amendments.
Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?

