TMS Prior Authorization Checklist: What Intake Teams Must Capture Before Session 1 (2026)
TMS denials often start before treatment starts. If intake teams fail to capture the right clinical facts, the program loses days to callbacks, addenda, and resubmissions. This checklist turns CTMSS coverage guidance into a front-end workflow your EHR should enforce before the first session.
Start with the minimum clinical story a payer needs
The Clinical TMS Society says coverage for MDD should be considered medically necessary when an adult patient has a documented diagnosis of moderate or severe major depressive disorder and meets at least one qualifying treatment-history pathway. That means intake cannot stop at "TRD referral received." The chart needs diagnosis severity, the current episode context, and clear treatment history before authorization review begins.
Checklist item 1: Confirm diagnosis and severity in structured form
Capture the DSM-5 diagnosis, whether the episode is single or recurrent, and a standardized symptom measure showing moderate or severe severity. If this lives only inside scanned notes, prior auth work slows down immediately.
Checklist item 2: Document the qualifying treatment-history pathway
CTMSS allows several routes to medical necessity, including failure of one adequate medication trial in the current episode, inability to tolerate medication trials with documented side effects, prior meaningful response to TMS, or a medical reason additional antidepressants are contraindicated. Intake staff should know exactly which pathway the prescriber is using and collect supporting evidence for that pathway.
Checklist item 3: Do not build the packet around an ECT prerequisite
The guidance is explicit that electroconvulsive therapy is not a prerequisite for TMS authorization or coverage. If your intake packet implies the patient must fail ECT first, you are adding friction the policy does not require.
Checklist item 4: Establish the planned course up front
CTMSS says TMS is reasonable and necessary for at least 36 visits, with extensions in ten-treatment increments for late responders. The authorization request should reflect the intended course design, not a vague request for "TMS treatment as indicated."
Checklist item 5: Make coding and session planning visible early
Intake teams should know the core code structure because authorizations and scheduling depend on it: 90867 for the initial mapping session, 90868 for subsequent sessions, and 90869 for motor-threshold re-determination. When that structure is visible before approval, operations can reserve the right visit types and avoid rework after the auth arrives.
What your EHR should hard-stop before auth submission
- Missing severity evidence: no rating scale or no documentation of moderate or severe MDD.
- Unclear treatment pathway: medication failure, intolerance, prior TMS response, or contraindication not specified.
- Unsupported course request: planned visit count does not match the proposed treatment design.
- Scattered records: supporting clinical notes live in uploads but are not indexed to the authorization packet.
What to test in your EHR demo
- Show an intake workflow that collects the CTMSS-required facts before staff can mark a referral auth-ready.
- Demonstrate how supporting medication history and symptom scores appear in one prior auth work view.
- Confirm the planned 36-session course and visit types can flow directly from intake into scheduling.
Bottom line
TMS prior auth is an intake discipline problem before it becomes a clinical one. When your EHR makes the eligibility story complete before submission, authorizations move faster and the treatment schedule starts with fewer surprises.
Next Steps
Editorial Standards
Last reviewed:
Methodology
- Used CTMSS coverage guidance to define the minimum facts a payer-facing TMS prior authorization packet should contain.
- Translated coverage and utilization rules into intake-stage workflow requirements and hard stops.
- Focused on the front-end documentation failures that cause avoidable authorization delays.