Skip to main content
Kavera

Documenting Medical Necessity for Neuropsych Testing

Medical necessity for neuropsychological testing (CPT 96116–96146) is established when the chart shows a specific referral question, a documented cognitive or behavioral change, prior lower-intensity assessment that was insufficient, and a clear link between the testing ordered and a treatment or return-to-activity decision the results will inform.

This page provides general educational information about CPT and RTM billing codes. It is not coding advice, a guarantee of reimbursement, or a substitute for your own compliance review. Payer coverage and documentation requirements vary by plan and can change — verify current requirements with CMS, your Medicare Administrative Contractor, and each payer before billing.

Why Medical Necessity Denials Happen in Neuropsych Testing

Neuropsychological and psychological testing codes (96116/96121, 96132/96133, 96136/96137, 96138/96139, 96146) are hour- or time-based services with no diagnosis code that automatically qualifies a claim. Payers evaluate necessity case by case, which means the documentation has to do the work a simpler procedure code would not need. According to CMS's Psychological and Neuropsychological Testing FAQ, testing services are billed based on time spent on administration, interpretation, and integration of data — and that time, along with the clinical rationale for ordering it, is exactly what reviewers look for when a claim is audited or denied.

The most common necessity-related denial reasons are not about the test itself but about what surrounds it in the chart: no documented reason testing was ordered instead of, or in addition to, a standard clinical exam; no evidence that a less intensive option (a brief in-office cognitive screen, a symptom questionnaire) was tried or considered insufficient first; and no statement tying the results to a decision that will actually change management — return to work, return to play, medication changes, referral to another specialist, or a treatment plan revision.

What "Medical Necessity" Means for This Code Family

Medical necessity documentation for 96116–96146 generally needs to answer four questions in the chart, in the clinician's own language rather than a generic checkbox:

  1. What prompted testing? A specific clinical trigger — new-onset cognitive complaints after concussion, persistent symptoms beyond expected recovery windows, a mood or anxiety change interfering with function, or an unexplained cognitive decline — rather than a routine or protocol-driven order with no individualized rationale.
  2. What has already been tried or ruled out? Prior office-based screening (for example a MoCA or a validated symptom scale like the PCSS) that suggested testing was warranted, or documentation that the presentation was too complex for a brief screen alone.
  3. What specific domains or conditions is testing evaluating? Reference the relevant clinical domain — attention, memory, processing speed, executive function — rather than a blanket "cognitive testing" order.
  4. How will results change management? The plan should state, even briefly, what decision the testing will inform: clearance for return to play or return to work, a referral, a treatment adjustment, or ongoing monitoring frequency.

Documentation Checklist by Encounter Stage

At the ordering/referral stage:

  • Referral question stated in specific, answerable terms (not "cognitive eval" alone)
  • Relevant history: injury or onset date, prior level of function, comorbidities that could confound results (sleep disorder, depression, prior learning disability)
  • Any prior screening results that support proceeding to formal testing

At the administration stage (96136/96137, 96138/96139, or 96146):

  • Start and stop times or total minutes for QHP- or technician-administered codes (96146 is billed once per date regardless of time, per CMS guidance, so time documentation requirements differ for that code)
  • Tests administered, by name, with the rationale for that specific battery
  • For technician-administered codes, documentation that a physician or clinical psychologist provided the required general supervision — CMS's FAQ specifies this supervision role is limited to physicians and clinical psychologists, a carve-out from the broader diagnostic-testing supervision rule that otherwise permits NPs, PAs, and CNSs

At the evaluation stage (96132/96133 or 96116/96121):

  • Total time spent integrating data, interpreting results, and preparing the report, separate from administration time
  • Interpretation tied to the referral question — not just raw scores, but what they mean for this patient's function
  • A stated plan: diagnosis, treatment recommendation, referral, or monitoring plan
  • Testing ordered without a documented trigger. A blanket annual or protocol-based testing order, with no individualized clinical reasoning in that visit's note, is a frequent denial pattern across payers.
  • Missing or vague time documentation. Especially for the hour-based evaluation codes (96132/96133, 96116/96121), payers commonly deny claims where total time is not stated or cannot be reconstructed from the note.
  • No link between results and management change. A report that documents scores but never states what the clinician will do differently because of them reads as diagnostic curiosity rather than medically necessary care.
  • Redundant testing. Repeating a full battery shortly after a prior one without documenting why (new symptoms, treatment response check, legal/return-to-activity requirement) invites a frequency-based denial.
  • Frequency limits. Many payers cap how often testing codes can be billed for the same patient within a defined period; check payer-specific policy before scheduling repeat batteries.

Worked Example (Illustrative — No Dollar Amounts)

A sports-medicine physician sees a patient eight weeks after a concussion whose post-concussion recovery timeline is significantly delayed relative to the expected course. Office-based PCSS scores remain elevated, and the patient reports new difficulty concentrating at work. The physician documents this trajectory as the reason for referral to a neuropsychologist, specifying attention and processing-speed concerns as the referral question. The neuropsychologist's technician administers a battery under the psychologist's general supervision, logging total face-to-face time and the specific instruments given (Trail Making Test A and B, SDMT, Digit Span). The psychologist then documents evaluation time separately, interprets the results against the referral question, and states a specific recommendation: a graduated return-to-work plan with cognitive pacing strategies. Each stage of the chart ties back to the original clinical trigger and ends in a stated management decision — the pattern payers look for when assessing necessity.

How Kavera Handles This

Medical necessity is written by you, at the visit. Kavera gives you the scored baseline, the symptom trend and the referral triggers on one screen so the note has something to point at, and it stores the note with the record. Self-Serve practices run this with their own staff. On Managed, Juliet Mott's team runs it and bills it under your credentials. Educational, not coding advice. Verify requirements with CMS, your MAC and each payer.

FAQ

Common questions

Does a low score on a screening tool alone establish medical necessity for full neuropsych testing?
Not by itself in most protocols. Payers generally want to see the screening result connected to a specific clinical question that the screening tool cannot answer — for example, distinguishing between multiple possible causes of cognitive change — rather than the low score serving as the sole justification.
Can the same clinician who orders testing also perform it?
Yes, when they meet the applicable credential and supervision requirements for the code being billed. The documentation expectations are the same either way: a stated rationale for testing and a plan for how results will be used.
How much detail is enough for the "medical necessity" note?
Enough that another reviewer, reading only that note, could understand why testing (rather than a brief in-office screen) was needed and what decision it will inform. A one-line justification copied across visits is a common audit flag.
Does repeat testing need new medical-necessity documentation each time?
In most protocols, yes — each testing episode should have its own stated rationale, such as a treatment-response check, new symptoms, or a required return-to-activity determination, even if the patient was tested previously.
Where can I find the authoritative source for these documentation expectations?
Start with CMS's Psychological and Neuropsychological Testing FAQ and your specific payer's published testing policy, since documentation requirements can vary by plan.

See it on your patients

One field. 30 minutes. Live demo with a clinician.