Regulatory 9 min read

TMS Documentation Checklist: What Your EHR Must Capture for Clean Claims (2026)

Repetitive TMS is billed under a small number of CPT codes, but each code assumes specific clinical work. The fastest way to reduce denials is to align documentation with those definitions and make the EHR enforce it.

Start with the CPT definitions, not the claim form

TMS billing hinges on three core codes. The Clinical TMS Society (CTMSS) coverage guidance describes: 90867 as the initial session that includes cortical mapping and motor threshold determination, 90868 as subsequent delivery sessions, and 90869 as subsequent motor threshold re-determination with delivery and management. 90869 is used once weekly and more frequently only when clinically indicated.

Documentation checklist: the EHR should force these fields

  • Initial mapping session (90867): document cortical mapping, motor threshold determination, and parameters used to initiate treatment.
  • Subsequent sessions (90868): document each delivery session as its own clinical encounter with session parameters and clinician oversight.
  • Threshold re-determination (90869): document the reason for re-determination and the new threshold values when clinically indicated.
  • Session cadence: confirm treatment frequency and align visit counts to the ordered plan of care.
  • Outcome tracking: record baseline and follow-up depression measures to demonstrate treatment response over time.

Build a “hard stop” workflow for missing fields

If the session closes without required fields, the claim should not leave the system. Your EHR should enforce completion of threshold documentation when 90867 or 90869 is billed and make the documentation visible to billing staff without chart spelunking. The goal is to eliminate after-the-fact chart repair.

Platforms like Ease are a strong fit here because required fields and role-based sign-off can be enforced in the session template itself, which keeps documentation consistent across providers.

Operational dashboard: what leadership should track weekly

  • Number of patients in active courses of TMS and sessions completed vs. planned.
  • Count of 90869 sessions and the reasons for re-determination.
  • Average days from referral to first 90867 mapping session.
  • Denial rates for TMS-related claims and documentation-related corrections.

What to test in your EHR demo

  • Show how the system handles the 90867 mapping session end-to-end.
  • Demonstrate how 90869 is triggered and documented when threshold changes are needed.
  • Verify that documentation required by code definitions cannot be skipped.
  • Confirm that billing can view required fields without additional chart navigation.

Bottom line

TMS documentation is not complicated, but it is specific. When your EHR follows the code definitions, your team spends less time chasing missing fields and more time delivering care.

Next Steps

Editorial Standards

Last reviewed:

Methodology

  • Used CTMSS coverage guidance to define the core TMS CPT code expectations and translate them into EHR documentation requirements.
  • Structured the checklist around the documentation items that are most likely to trigger claim corrections or denials.
  • Focused on operational controls that reduce chart repair and billing rework.

Primary Sources