Regulatory 15 min read

ECT Patient Selection and Treatment Setting: A Documentation Blueprint (2026)

ECT programs need clear documentation around who is an appropriate candidate and where treatment should take place. APNA’s ECT considerations outline the clinical decision points. This blueprint turns them into structured, auditable fields.

1) Document the clinical rationale for ECT candidacy

APNA notes that ECT candidates often include patients with treatment-resistant mental illness or those at risk for severe harm. Your documentation should explicitly capture the indication and the clinical rationale for choosing ECT.

2) Record medical considerations and risk factors

APNA lists medical considerations such as cardiovascular risk, implanted devices, and other comorbidities that may require further evaluation. These should be recorded as structured fields so the review is auditable and consistent.

3) Decide and document the treatment setting

APNA states there are no absolute contraindications for ECT, but some patients with complicated medical or neurologic conditions may require a medical hospital setting. The decision of treatment location is made by the clinical team based on risk/benefit analysis. This decision should be captured clearly in the chart.

4) Use role-based permissions for orders and sign-off

The APNA checklist emphasizes that ECT recommendations and follow-up should be performed by appropriately credentialed psychiatric providers. Your EHR should enforce this via role-based permissions and required sign-off.

ECT selection checklist

  • Indication: structured field for treatment-resistant illness or acute risk profile.
  • Medical review: capture cardiovascular risk, implanted devices, and anesthesia considerations.
  • Setting decision: document outpatient vs. hospital setting rationale.
  • Credentialing: ECT orders and procedure notes signed by credentialed providers.

Patient Selection Decision Matrix

Decision Area What to Document Why It Matters
Clinical indication Diagnosis, severity, treatment resistance, acute suicidality, catatonia, mania, psychosis, or severe functional decline where applicable. Establishes why ECT is clinically reasonable compared with medication-only or lower-intensity options.
Treatment history Medication trials, therapy, hospitalization, TMS/ketamine history, response, adverse effects, and urgency. Supports medical necessity and avoids vague “failed treatment” statements.
Medical risk Cardiovascular, neurologic, anesthesia, pregnancy, implanted device, and frailty considerations. Drives setting, anesthesia planning, consultation needs, and monitoring intensity.
Capacity and consent Capacity assessment, informed consent, guardian/surrogate process, revocation rights, and re-consent triggers. Protects patient rights and creates a defensible consent record.
Treatment setting Outpatient vs. hospital setting rationale, required monitoring, transfer plan, and emergency pathway. Shows that the program matched treatment location to patient acuity and medical complexity.

Setting Decision: Outpatient, Hospital-Based, or Higher-Acuity Pathway

Setting selection should not be a default. Programs should document why the chosen site can safely manage the patient’s psychiatric acuity, medical risk, anesthesia needs, recovery monitoring, and emergency escalation. The EHR should force the team to name the setting rationale before scheduling the first session.

  • Outpatient ECT: appropriate only when medical risk, transportation, post-treatment supervision, and follow-up plan are manageable.
  • Hospital-based ECT: often better for medically complex patients, unstable psychiatric risk, inpatient treatment courses, or higher monitoring needs.
  • Deferred or escalated evaluation: needed when medical clearance, consent, anesthesia review, or emergency stabilization is incomplete.

What to Test in the EHR Demo

  1. Create a candidate with treatment-resistant depression and acute safety concerns, then document indication and urgency.
  2. Add cardiovascular risk, implanted-device history, and anesthesia review needs; show how the system routes tasks.
  3. Document informed consent and setting rationale, then schedule a course with session-level tracking.
  4. Change the patient’s medical status mid-course and show how the system prompts re-review or setting escalation.
  5. Export a patient-selection packet for peer review, payer review, or compliance audit.

Why Ease supports this workflow well

Ease’s program-level workflows and role-based permissions make it easier to standardize ECT candidate documentation and enforce sign-off rules without manual workarounds.

Bottom line

ECT patient selection is a high-stakes decision. The best programs document the clinical rationale, treatment history, medical review, consent, and setting choice in a way that is easy to audit and reproduce. Your EHR should make that the default before the first treatment is ever scheduled.

Next Steps

Editorial Standards

Last reviewed:

Methodology

  • Used APNA’s ECT treatment considerations to define candidate eligibility and setting selection criteria.
  • Translated medical considerations into structured documentation fields.
  • Emphasized role-based permissions for ECT orders and sign-off.

Primary Sources