TMS Prior Authorization Checklist
Use a TMS prior authorization checklist for current payer criteria, member and provider data, treatment-history evidence, device and protocol context, submission, extensions, and appeals.
On this page: Direct answer
Direct answer
TMS prior authorization checklist: what operators need to know
Use a TMS prior authorization checklist for current payer criteria, member and provider data, treatment-history evidence, device and protocol context, submission, extensions, and appeals. Retrieve the current policy for the exact payer, product, jurisdiction, service, and effective date. Convert every criterion into an evidence field without copying unsupported conclusions forward.
TMS prior authorization should begin with the exact payer, plan, member, diagnosis context documented by qualified clinicians, requested device and protocol, provider and setting, anticipated dates, and current coverage policy. Requirements can vary by payer and Medicare jurisdiction, and linked billing or documentation articles may carry operational details not visible in a policy summary.
This checklist supports administrative completeness and traceability; it does not determine diagnosis, treatment resistance, contraindications, medical necessity, device use, protocol, or treatment plan. Qualified clinicians make those decisions, and coding, coverage, contract, and legal questions need the appropriate responsible owners.
Key takeaways
The short version
- Retrieve the current policy for the exact payer, product, jurisdiction, service, and effective date.
- Convert every criterion into an evidence field without copying unsupported conclusions forward.
- Keep clinical authorship and approval explicit for treatment-history, severity, safety, and protocol content.
- Reconcile authorized sessions, dates, conditions, extensions, and retreatment rules field by field.
- Use the exact adverse-decision notice to build peer-review or appeal work and deadlines.
Take the template with you
Free to copy · no email required
Adapt this administrative structure to the current payer policy and qualified clinical workflow.
1. TMS prior authorization checklist
| Requirement area | Administrative check | Evidence owner |
|---|---|---|
| Coverage context | Payer, plan, product, member, benefit, network, authorization entity, jurisdiction, policy ID, version, and effective date | Benefits, contracting, and authorization operations |
| Request | Initial, extension, continuation, retreatment, or appeal; service, device or protocol context, provider, setting, dates, sessions or units | Authorization owner with qualified clinical confirmation |
| Diagnosis and episode | Payer-required diagnosis, severity, episode, scale, functional, and other clinical fields | Treating qualified clinician |
| Treatment history | Required medication, dose, duration, response, adherence, intolerance, psychotherapy, prior TMS, ECT, or other policy fields | Qualified clinician and source-record owners |
| Safety and exclusions | Payer-requested contraindication, device, implant, neurological, medication, or other screening documentation | Qualified clinician under approved clinical process |
| Provider and equipment | Ordering and supervising professional, qualifications, site, device status, and policy-specific requirements | Clinical, credentialing, compliance, and operations owners |
| Submission and decision | Form, packet, signatures, channel, receipt, reference, decision clock, approval scope, denial reason, and appeal rights | Authorization operations |
2. Build a current policy-to-evidence matrix
- 01
Select the right policy
Confirm commercial or public program, plan product, jurisdiction, network, service, indication, request type, policy identifier, effective version, and linked forms or articles.
- 02
Extract exactly
Record each coverage, provider, device, documentation, safety, course, continuation, retreatment, and submission requirement in the payer's own operational terms.
- 03
Assign authority
Map administrative fields to operations and clinical questions to appropriately qualified professionals; never ask staff or AI to infer missing clinical conclusions.
- 04
Link evidence
Identify the current source record, author, date, required time window, accepted format, and validation for every criterion.
- 05
Recheck changes
Trigger policy review when payer, plan, jurisdiction, diagnosis request, device, protocol, provider, site, date, request type, or policy version changes.
3. Assemble and reconcile the TMS packet
- Member, payer, product, benefit, network, authorization entity, provider, facility, location, service, diagnosis context, dates, sessions or units, and request type agree across forms and records
- Current policy and effective version are attached to a requirement-to-evidence matrix
- Medication and other treatment history preserves name, class when required, dose, dates, duration, response, intolerance, adherence context, source, and qualified author as applicable
- Psychotherapy, prior procedures, standardized scales, functional information, safety screening, prior response, and requested protocol fields match the payer's stated criteria and clinical record
- Ordering, supervision, qualifications, setting, device, and facility fields are validated against current policy and organizational evidence
- Missing, conflicting, stale, not applicable, and pending qualified-review items remain visible until resolved
- Final human-approved packet, minimum-necessary review, submission channel, receipt, reference, clock, and follow-up are preserved
4. Reconcile approval, extension, or retreatment
| Decision field | Compare | Next work |
|---|---|---|
| Scope | Requested and approved service, indication, provider, site, device or protocol conditions | Clarify discrepancy before scheduling or delivery |
| Course | Start, end, sessions or units, frequency, taper, conditions, and expiration | Build schedule and remaining-authorization tracking from the decision |
| Continuation | Required response measure, time point, documentation, submission, and reviewer | Work backward with qualified clinician and operations |
| Retreatment | Prior response, elapsed time, recurrence, new policy evidence, and request pathway | Treat as a current payer-specific request, not an automatic repeat |
| Partial or adverse | Denied fields, exact reason, policy citation, notice, rights, and deadlines | Route clinical discussion, correction, peer review, or appeal appropriately |
5. Prepare peer review or appeal from the exact decision
- Separate an administrative missing item, benefit or network issue, noncoverage position, medical-necessity rationale, provider requirement, timing issue, and coding or claim issue
- Retrieve the policy version applied, decision notice, case record, submission, communications, reference numbers, and applicable appeal instructions
- Have qualified clinicians address clinical criteria, evidence, patient-specific context, alternatives, and requested action in their own approved judgment
- Use operations to build a traceable index, reconcile dates and facts, manage deadlines, verify recipients and channels, and preserve delivery proof
- Document urgent or expedited analysis under the actual rule and route immediately to qualified owners; do not infer eligibility from urgency alone
- Track outcome, reason change, additional evidence, authorized scope, access effect, and repeat root cause for quality improvement
Common questions
Answers before you build.
Does TMS require prior authorization?+
Many plans may require it, but the answer depends on the payer, plan, product, jurisdiction, benefit, diagnosis and requested service context, provider, facility, network, and date. Verify the current source.
What documentation is needed for TMS authorization?+
Use the current payer policy. Requirements may address diagnosis and episode, severity or scales, treatment history and response, psychotherapy, safety screening, provider qualifications, device or setting, requested course, and signatures.
Are Medicare TMS criteria the same nationwide?+
Do not assume so. Medicare Administrative Contractors publish local coverage determinations and linked billing articles. Search the Medicare Coverage Database for the current jurisdiction and effective version.
How should a TMS clinic track authorized sessions?+
Reconcile the written decision into approved service, provider, site, dates, sessions or units, conditions, expiration, continuation requirements, and remaining amount; compare scheduled and completed services against that record.
Practical closeout
Use this operator checklist.
- Retrieve the current policy for the exact payer, product, jurisdiction, service, and effective date.
- Convert every criterion into an evidence field without copying unsupported conclusions forward.
- Keep clinical authorship and approval explicit for treatment-history, severity, safety, and protocol content.
- Reconcile authorized sessions, dates, conditions, extensions, and retreatment rules field by field.
- Use the exact adverse-decision notice to build peer-review or appeal work and deadlines.
Continue through the cluster
Verified customer case studies are added only with customer permission and supporting evidence; none is implied by these operational examples.
Sources & methodology
Trace the operational claims.
Marsa Health Editorial reviewed the primary and research sources below on July 22, 2026. We translate them into workflow controls, distinguish proposals from final rules, and flag where plan, program, state, contract, or clinical requirements vary.
- 01Medicare Local Coverage Determination: Transcranial Magnetic Stimulation (L34641) Centers for Medicare & Medicaid ServicesOne current Medicare Administrative Contractor LCD illustrating TMS coverage indications, limitations, supervision, and linked documentation requirements; it is not a universal rule for every Medicare jurisdiction or payer.Accessed or rechecked July 22, 2026
- 02Medicare Coverage Database Centers for Medicare & Medicaid ServicesOfficial search for current national and local Medicare coverage documents. Users must select the relevant jurisdiction, effective version, service, and linked billing article.Accessed or rechecked July 22, 2026
- 03CMS Interoperability and Prior Authorization Final Rule CMS-0057-F Centers for Medicare & Medicaid ServicesCurrent implementation dates, decision timeframes, denial-reason requirements, metrics, and API provisions for impacted payers.Accessed or rechecked July 22, 2026
- 04Electronic Prior Authorization Centers for Medicare & Medicaid ServicesCurrent CMS provider-readiness guidance for 2027 electronic prior authorization, EHR questions, FHIR testing, and workflow preparation.Accessed or rechecked July 22, 2026
- 05How to appeal an insurance company decision Centers for Medicare & Medicaid ServicesFederal overview of internal appeals, external review, notices, and general appeal timing. Plan and state rules can differ.Accessed or rechecked July 22, 2026
- 06Minimum Necessary Requirement U.S. Department of Health and Human ServicesHIPAA guidance on limiting uses, disclosures, and requests for protected health information when the standard applies.Accessed or rechecked July 22, 2026
- 07AI Risk Management Framework Core National Institute of Standards and TechnologyVoluntary framework for governing, mapping, measuring, and managing AI risks, including defined roles for human-AI oversight.Accessed or rechecked July 22, 2026
- 08Autism services Medicaid.govFederal Medicaid overview and guidance collection on autism services; state coverage and operational requirements vary.Accessed or rechecked July 22, 2026
Organizational author. Editorial review covers source accuracy, search intent, workflow boundaries, and human-oversight requirements. This material is educational and does not provide clinical, legal, coding, or coverage advice.
No named clinical or legal expert reviewer is attributed to this version. Marsa Health does not invent reviewer credentials.
Read our editorial methodRevision history
What changed and when
July 22, 2026
Initial publication, source review, and operational editing.