ECT Program Readiness Checklist: What Your EHR Must Support (2026)
ECT is one of the most tightly governed services in psychiatry. A successful program depends on clear clinical roles, consistent candidate evaluation, and documentation systems that prevent gaps. This checklist translates professional guidance into EHR requirements.
1) Credentialing and scope of practice must be explicit
The APNA ECT considerations checklist emphasizes that ECT recommendations and follow-up should be performed by an appropriately credentialed psychiatric provider, with credentialing aligned to state scope and facility rules. Your EHR should reflect this by assigning ECT orders and note sign-off to the appropriate role and tracking credential status.
2) Candidate eligibility should be standardized
The APNA checklist outlines candidate eligibility considerations and highlights that ECT candidates often include patients with treatment-resistant mental illness or those at risk for severe harm. The clinical team should record the rationale for ECT candidacy and make sure it is easy to review across the course of treatment.
3) Medical risk review must be documented
APNA’s checklist details medical considerations such as cardiovascular risks and implanted devices. These are precisely the kinds of pre-treatment checks that should appear as structured fields in the EHR rather than free-text comments that are hard to audit.
4) Build an ECT-specific workflow, not a generic visit type
CMS lists CPT 90870 for electroconvulsive therapy in its Medicare mental health coverage guidance. A program should track ECT sessions as a distinct workflow with per-session documentation, role-based sign-off, and easy retrieval of course-level records.
5) Operational controls to prevent documentation drift
- Structured candidate evaluation: eligibility and contraindication fields captured at baseline.
- Role-based signoff: ECT orders and procedure notes limited to credentialed providers.
- Course-level tracking: easy view of session count, schedule adherence, and note completion.
- Audit-ready data: clear retrieval of eligibility rationale, risk review, and session documentation.
What to test in your EHR demo
- Show how the system enforces role-based permissions for ECT orders and procedure notes.
- Demonstrate a structured ECT candidate evaluation workflow.
- Confirm that ECT sessions are grouped into a single course of treatment with session-level notes.
- Prove that a full ECT course can be reviewed without piecing together fragmented encounters.
Why Ease is often the best fit
ECT programs need strict role-based permissions, structured eligibility workflows, and course-level tracking. Ease’s program-based workflows make those controls easier to standardize across sites without adding extra administrative work.
Bottom line
ECT programs succeed when the EHR protects clinical integrity, not just billing. If your system treats ECT as a generic outpatient visit, you will rely on manual checklists to stay compliant. A purpose-built workflow is safer and faster.
Next Steps
Editorial Standards
Last reviewed:
Methodology
- Used professional guidance from APNA to define ECT candidate, scope, and medical review considerations.
- Mapped those considerations to EHR workflow requirements and audit-friendly documentation controls.
- Referenced Medicare mental health guidance for the ECT CPT code context.