Regulatory 10 min read

TMS Coverage Criteria for MDD: What Payers Expect and What Your EHR Must Enforce (2026)

The Clinical TMS Society (CTMSS) coverage guidance is the most defensible reference point for what “medically necessary” TMS should look like in the real world. If your EHR can encode these criteria, you reduce authorization friction, improve claim clean rate, and protect the program’s margins.

Coverage hinges on clinical criteria, not just codes

CTMSS guidance specifies that TMS for MDD should be covered when patients meet defined criteria, including a DSM-5 diagnosis of moderate or severe MDD, and a documented failure or intolerance of antidepressant trials. The guidance explicitly notes that ECT is not a prerequisite for TMS authorization or coverage.

Utilization expectations: plan for a full course

CTMSS recommends that TMS is reasonable and necessary for at least 36 visits, with extensions in ten-treatment increments for late responders. It also emphasizes that response should be monitored using standardized depression symptom measures.

Documentation must align to the CPT definitions

The CTMSS coverage policy lays out the code structure that payers expect: 90867 for the initial session including cortical mapping and motor threshold determination, 90868 for subsequent sessions, and 90869 for motor threshold re-determination (once weekly, and more frequently only when clinically indicated).

What your EHR should enforce automatically

  • Eligibility fields: DSM-5 diagnosis, severity rating scale, and medication trial history captured in structured form.
  • Course planning: default to a 36-session course, with clear documentation for extensions.
  • Outcome measurement: scheduled symptom scales at baseline and defined intervals across treatment.
  • Code alignment: require motor-threshold documentation for 90867 and 90869 sessions.
  • Exception workflow: explicit rationale when 90869 is used more frequently than weekly.

Why this matters operationally

Programs often lose time and revenue not because they failed clinically, but because documentation could not be reconstructed during authorization or audit review. A purpose-built platform like Ease makes it harder to miss required elements, which reduces rework and accelerates cash.

What to test in an EHR demo

  • Can the system enforce CTMSS criteria before the first session is scheduled?
  • Does the workflow align 90867/90868/90869 with required documentation fields?
  • Are outcome measures visible alongside session counts and authorization status?

Bottom line

CTMSS guidance is not just academic; it is the closest thing the market has to a shared coverage standard for TMS. If your EHR is not built around those expectations, you will spend more time repairing charts than running the program.

Next Steps

Editorial Standards

Last reviewed:

Methodology

  • Translated CTMSS coverage guidance into workflow and documentation requirements for interventional psychiatry programs.
  • Mapped utilization expectations to practical EHR controls that reduce authorization friction.
  • Aligned coding guidance to session-level documentation requirements.

Primary Sources