The fix was not a modifier. It was two rendering providers and a note that proved it.
A 40-BCBA autism group kept losing 97155 whenever it landed in the same clock window as 97153. The payer's overlapping-service edit read one supervising human doing two timed things at once and denied the supervision line. Nothing was wrong with the care. The claim just never showed the payer that a technician and a BCBA were two different people doing two different jobs at the same time, which is exactly what AMA CPT says 97155 is for.
Start with what the code actually says
CPT already blesses the overlap. The claim just has to prove it.
Read that twice. The higher-level supervision code is written to expect that a technician is delivering 97153 in the same room, at the same time, while the BCBA modifies the plan. Concurrent is not a loophole here. It is the intended shape of the service.
So the denials were never a coding-legitimacy problem. They were a claims-evidence problem. The payer's automated edit had no way to see that the 97155 unit and the 97153 unit were performed by two separate people, so it treated them as one provider double-billing the same minutes.
The two paths a concurrent session can take
Same session, same codes. One claim clears, one gets denied.
The three things that changed
No appeal template fixed this. The claim structure did.
97153 renders under the technician who delivered it. 97155 renders under the BCBA who modified the plan. Two distinct rendering NPIs on the claim is the single change that turns an "overlap" into two legitimate simultaneous services.
// distinct NPI per lineThe session note carries a technician-delivery entry and a separate BCBA entry describing the specific protocol change made and the direction given. When a reviewer opens the record, the concurrency explains itself instead of looking like a duplicate.
// who did what, whenSome plans and state Medicaid ABA manuals permit 97153 and 97155 concurrently with distinct providers. Others cap or prohibit it. The group built a payer grid so the front end knows, per plan, whether concurrent is billable before the session is ever scheduled.
// check before you billLine level, side by side
The denied claim and the clean claim, in the fields the edit reads.
| Claim field | Denied version | Clean version |
|---|---|---|
| 97153 rendering provider | Supervising BCBA | Technician (RBT) who delivered |
| 97155 rendering provider | Supervising BCBA | Same BCBA who modified protocol |
| Distinct providers on claim | No, one NPI on both | Yes, two NPIs |
| Note structure | Single blended narrative | Separate delivery and modification entries |
| Units for the same minutes | Read as duplicated | Read as two roles, not double-counted |
| Payer overlap edit result | 97155 denied | Both lines adjudicated |
Note the columns describe claim structure, not dollar figures. Every plan prices these codes differently and several state Medicaid programs set their own concurrency rules, so the win here is a claim the edit can read correctly, not a promised recovery number.
What the BCBA note has to carry
The documentation that lets concurrency survive a reviewer.
- Separate technician-delivery entry for the 97153 units, naming the RBT.
- Distinct BCBA entry describing the specific protocol modification made during the session.
- Evidence of live direction of the technician, tied to the 97155 minutes.
- Start and stop or unit-level time for each service so the minutes reconcile.
- Two rendering identities that match the two claim lines exactly.
- Medical-necessity link to the authorized treatment plan and goals.
What this is grounded in
The 2026 guidance behind the approach.
The Category I adaptive behavior services set. The 97155 descriptor is delivered by a physician or other QHP and may include simultaneous direction of the technician, which is what makes concurrent delivery with 97153 codeable in the first place.
State ABA manuals define who may render each code and whether concurrent supervision is permitted, capped, or prohibited. These vary by state, so the governing manual for each plan has to be confirmed before billing concurrently.
Commercial payer reimbursement policies define how overlapping timed services are adjudicated, including when distinct rendering providers are required for two services in the same interval. Reading the specific policy is what tells you the claim structure the edit expects.
If 97155 keeps getting written off, the problem is usually the claim, not the care.
ASP-RCM builds ABA billing the way this group ended up running it: rendering-provider separation on every concurrent session, a documentation standard your BCBAs can actually keep, and a payer-by-payer concurrency grid so your team knows what is billable before the schedule is set. We work the appeals too, but the goal is claims that never trip the edit.
Talk through your 97155 denials →This case study describes an archetypal 40-BCBA autism group and does not name a specific client. It is educational and does not constitute coding, billing, or legal advice. Code definitions, concurrency rules, and reimbursement policies change and differ by payer and by state, so confirm current AMA CPT language, the applicable state Medicaid ABA provider manual, and each payer's overlapping-service policy before billing 97153 and 97155 concurrently.
Related reading
What actually happened, and when
EOHHS proposes re-adopting 101 CMR 358.00 with zero rate change, holding MassHealth ABA reimbursement rates at
Read →InsightThe 97153 Unit Cap Map: why ABA reimbursement changes at the state line
How 2026 state Medicaid unit caps and concurrent 97155/97153 rules for ABA code 97153 diverge, the EPSDT floor
Read →Case studyTwo disciplines, one roof, five rulebooks that never overlap
How an employee-owned, multi-state pediatric therapy and special-education group bills ABA and physical therap
Read →