Half your support tickets are billing questions in disguise
Authorization units, unit conversion, who renders 97155, whether concurrent supervision is billable in that state. Your team answers them because there is nobody else to ask — and none of them are software problems.
- check_circleWe build no software
- check_circleABA and behavioral specialists
- check_circleWorks inside your platform
- check_circleFree cheat sheet, no agreement
What a behavioral health platform or specialty consultant gets from this partnership
MedPrecision handles outsourced billing for ABA, mental health and behavioral health practices — the AMA 97151–97158 adaptive behavior series, unit conversion, technician versus QHP rendering identity, supervision billing, and state autism mandate variation. We build no software, so nothing in the relationship competes with your platform or moves a customer off it. Partners get an ABA and behavioral-health billing guide written for their specific platform workflow, a guest session for their customer community, and an already-published mental health denial cheat sheet they can link from their help centre today with no agreement of any kind.
- No competing EHR, PM, scheduling or data-collection product
- We work inside CentralReach, TheraNest, SimplePractice and others
- Denial cheat sheet is live, free and ungated — link it today
- Introductions come from you, to customers you choose
Five tickets your team should not have to answer
Every one of these arrives looking like a product defect and resolves as a billing rule. They are expensive precisely because they route to engineering-adjacent support rather than to somebody who bills these codes daily.
- support_agent “Why did this session deny when the authorization is still open?”
- Authorized units are tracked per code, not per case. A case with remaining 97153 units and exhausted 97155 units denies every protocol-modification session while the dashboard still shows authorization remaining.
- support_agent “The units in the note do not match the units on the claim.”
- Time-based adaptive behavior codes convert session minutes to billable units under rounding rules the scheduling module does not apply. A note and a claim can both be correct and still disagree.
- support_agent “Which rendering provider goes on the claim — the RBT or the BCBA?”
- Technician-delivered and QHP-delivered services take different rendering identities, and payer requirements differ on whose NPI appears. Getting it wrong denies the whole date of service, not the line.
- support_agent “Concurrent supervision keeps getting denied as a duplicate.”
- A BCBA supervising while a technician delivers treatment produces two overlapping services on one date, and payer policies on billing them concurrently vary by plan and by state.
- support_agent “The state Medicaid plan wants something the commercial plan does not.”
- State autism mandates layer requirements on top of commercial policy — diagnosis documentation, supervision ratios, reassessment intervals — and they change without touching the software.
The adaptive behavior series, and why rendering identity decides the claim
The AMA adaptive behavior codes split by who delivers the service. That split is the single most common source of denied ABA dates of service, because a scheduling system records who was in the room while a claim records who is permitted to bill it.
| CPT | Delivered by | Service |
|---|---|---|
| 97151 | Physician or QHP | Behavior identification assessment |
| 97152 | Technician | Behavior identification supporting assessment |
| 97153 | Technician | Adaptive behavior treatment by protocol |
| 97154 | Technician | Group adaptive behavior treatment by protocol |
| 97155 | Physician or QHP | Adaptive behavior treatment with protocol modification |
| 97156 | Physician or QHP | Family adaptive behavior treatment guidance |
| 97157 | Physician or QHP | Multiple-family group adaptive behavior treatment guidance |
| 97158 | Physician or QHP | Group adaptive behavior treatment with protocol modification |
QHP denotes a qualified healthcare professional. Full detail, including documentation requirements and the payer variation behind each code, sits on our ABA therapy billing services page and the 97153 and 97155 code reference.
Take the cheat sheet, skip the meeting
The mental health denial cheat sheet is already published, free, and carries no email capture or gate. Link it from your help centre or send it to a customer who is fighting denials, today, with no agreement and no conversation with us. If it turns out to be useful, that is a better basis for a partnership than a call would have been.
What behavioral health platforms ask us first
Name your platform
We will write the ABA and behavioral-health billing guide around your product’s actual workflow — yours to brand and publish.
Start a partner conversation arrow_forwardDo you compete with our platform?
No. MedPrecision builds no software of any kind — no EHR, no practice-management system, no scheduling or data-collection product. We are a billing service that works inside whatever platform your customers already run. For behavioral health that includes CentralReach, TheraNest and SimplePractice; the site publishes the full supported platform list rather than describing it vaguely. Nothing in the relationship pulls a customer off your product, because we have nothing to move them to.
What do your customers actually gain from this?
A billing team that already knows the 97151–97158 adaptive behavior series, unit conversion, supervision billing and state autism mandate variation — rather than a general medical biller learning it on your customers’ claims. In practice the difference shows up in your support queue: authorization and unit questions that are really billing questions stop arriving as software bugs.
What can you give us that we can use immediately?
A mental health denial cheat sheet that is already published, free and ungated — link it from your help centre today with no agreement of any kind. Beyond that: an ABA and behavioral-health billing guide written specifically for your platform’s workflow, a guest session for your customer community on authorization and unit management, and a joint webinar. The first costs you nothing and requires nothing.
How does billing work for a customer who has never outsourced?
Pricing is a percentage of collections — 7.0% solo, 6.0% group — with no setup fees on standard platforms and no per-claim charges. We work inside the customer’s existing system rather than migrating them, so the platform relationship is untouched. Standard API integrations complete in 5 to 7 business days; a custom HL7 or sFTP build for a non-standard system takes 2 to 3 weeks at separately quoted scope.
Are you going to spam our customer base?
No, and we would put that in the agreement. Introductions come from you, to customers you choose, at a moment you choose. We do not want a customer list and would not know what to do with one that arrived without context — a referral that lands cold reflects on you before it reflects on us, which is exactly why the program starts with a single introduction rather than a campaign.
Behavioral specialties
What we handle
Send us the ticket you cannot answer
The next authorization-unit question your support team escalates — forward it. We will answer it properly and in writing, for free, whether or not this ever becomes a partnership. That answer is a more honest sample of the work than anything on this page.
- check_circleNo contract
- check_circleNo setup fees
- check_circleReply within 1 business day