Testing Codes Deserve Their Own Review: CPT 96112 and Revenue Integrity
Testing services are where a behavioral health practice's coding discipline is tested most and watched least.
They are lower volume than therapy and psychiatry, so they rarely dominate a revenue report. But they are higher in complexity per claim — more documentation-sensitive, more dependent on correct code selection, and more exposed to payer-specific policy. That combination makes testing the place where small process gaps quietly become revenue and compliance problems.
Across this series we have looked at where reimbursement changes surface, how annual and quarterly postings differ, and why the allowed amount is the number to watch. This article narrows to a single high-stakes category: testing codes, and why they deserve a review of their own.
Why Testing Is Lower Volume but Higher Complexity
A busy clinician may bill the same handful of therapy codes hundreds of times a month. The pattern is familiar, the documentation is routine, and errors tend to surface quickly because volume makes them visible.
Testing is the opposite profile. A practice may bill a given assessment code a few dozen times a month, or fewer. Each instance can involve different instruments, different time, different components, and different payer rules about who may perform and bill the service. Low volume means a coding or documentation error can persist for months before anyone notices, because there is no high-frequency pattern to make it obvious.
Several factors drive the complexity:
Component structure. Testing services often involve distinct components — evaluation, administration, scoring, interpretation — that carry their own coding and documentation expectations.
Provider-type rules. Payers may have specific requirements about which credentials can perform and bill particular assessment services.
Documentation dependence. Testing claims are more likely to require supporting documentation that substantiates the instruments used, the time involved, and the clinical rationale.
Authorization and policy variation. Coverage, prior authorization, and medical-necessity rules for testing vary meaningfully across payers and plans.
None of this makes testing unmanageable. It makes testing a category that cannot be reviewed casually alongside high-volume therapy codes. It needs its own pass.
CPT 96112 as a Developmental Testing Example
Consider developmental testing as an illustration of how specific a testing category can be.
CPT 96112 describes developmental test administration using standardized developmental instruments, with interpretation and reporting. The important word is developmental. It denotes a particular kind of standardized assessment with its own instruments, its own documentation expectations, and its own place in a clinical workflow.
That specificity is the point. 96112 is not a general-purpose testing code, and it is not interchangeable with diagnostic interviewing, general psychological testing, or neuropsychological testing. Each of those is a distinct service with distinct coding. Using a developmental testing code as a stand-in for a different kind of assessment — or vice versa — is a coding accuracy problem regardless of intent.
The broader lesson generalizes to every testing category: the code must match the service actually performed, documented by the instruments used and the clinical work done. The service defines the code. The code does not define the service.
Never Substitute a Code Based on Reimbursement Alone
This is the single most important discipline in testing revenue integrity, and it deserves to be stated without hedging:
A code is selected because it describes the service performed — never because it reimburses better.
The temptation is understandable. When a practice notices that one testing code pays more than another, or that a reimbursement change has reduced what a familiar code returns, the path of least resistance is to reach for a different code. That is exactly the wrong response.
Code selection is a clinical and documentation question, not a revenue question. The service that was performed, and the documentation that substantiates it, determine the correct code. If a reimbursement change makes a legitimately-coded service less profitable, the answer is to understand the change — the kind of allowed-amount review covered earlier in this series — not to re-label the service.
Substituting codes to chase reimbursement creates exposure on multiple fronts: it misrepresents the service, it undermines documentation integrity, and it can trigger audit and recoupment risk that dwarfs any short-term gain. A reimbursement change should trigger a workflow and policy review. It should never trigger a code-chasing spree.
Testing Workflow Review Questions
Rather than a coding cheat-sheet — which would be inappropriate given how much varies by payer and plan — here is a set of questions a practice can use to review its testing workflow. These are the questions that surface problems before an audit does.
On code-to-service alignment:
Does the code billed match the service actually performed and the instruments actually used?
Has any testing code been selected, even informally, because of what it pays rather than what it describes?
When a reimbursement change occurred, did anyone respond by changing codes rather than investigating the change?
On documentation:
Does the documentation substantiate the instruments, the time, and the clinical rationale for each testing service?
Would the documentation stand on its own if a payer requested records?
On provider type and authorization:
Do the credentials of the person performing each testing service match payer requirements for that code?
Are prior authorization and medical-necessity requirements confirmed per payer before the service, not after?
On review cadence:
Are testing codes reviewed separately from therapy and psychiatry codes, on their own schedule?
When a fee schedule posting occurs, are testing codes checked as their own segment rather than folded into a general review?
A practice that can answer these confidently has a testing workflow that will hold up. A practice that cannot has found its next area to strengthen — before a payer finds it first.
Bottom Line
Testing services carry more coding, documentation, and policy complexity per claim than any other category behavioral health practices routinely bill, and their lower volume means errors hide longer.
The discipline is straightforward to state and requires ongoing attention to maintain: code the service that was actually performed, document it thoroughly, confirm payer policy and provider-type rules, and review testing codes on their own — never substitute a code to chase a rate.
When reimbursement changes, investigate the change. Do not re-label the work.
CBI Center for Education supports the long-term development of mental health professionals through education, consultation, and research. This series offers practical guidance on behavioral health reimbursement awareness, documentation, testing workflow review, and operational decision-making. Explore CBI Center for Education courses and resources designed to help clinicians and behavioral health organizations keep improving the care they provide.
Compliance Note
This series is for educational purposes only and is not legal, coding, billing, payer-contract, or compliance advice. CPT coding, coverage, authorization, documentation, provider eligibility, and reimbursement vary by payer, contract, region, plan, provider type, place of service, and date of service. Behavioral health organizations should confirm payer policy, contract terms, current CPT guidance, state scope-of-practice requirements, and internal compliance standards before selecting codes or changing any billing workflow. CPT codes referenced are for illustration only and do not constitute coding instructions.