Behavioral health treatment plan workflows in EHRs are governed by a small number of structural decisions: how the plan is organized, who must sign or attest, when it is reviewed, and how problems, goals, objectives, and interventions relate to later encounter notes. Public documentation for athenahealth, Alabama WITS, Salt Lake County UWITS, eClinicalWorks, and CCBHC toolkits shows that these workflows converge around problem-goal-objective-intervention hierarchies but diverge on completion requirements, review defaults, and patient endorsement [1][2][4][6]. The named systems differ in whether the workflow is a vendor product feature, a state-module configuration, or a compliance standard. This guide maps those documented decision points and supplies a concrete evaluation example, without assuming that one system matches every organization or that vendor claims represent verified outcomes.
What the Core Workflow Actually Contains
athenahealth describes a behavioral health treatment plan as a set of written instructions relating to a mental health concern, in which the user defines the patient's concerns, assesses characteristics, and enters goals to measure outcomes as treatment progresses [1]. The workflow then adds objectives and interventions, with interventions representing strategies, resources, or services that the patient's behavioral health provider should act upon to support the patient's goals [1]. The vendor's example pairs an objective to set a bedtime reminder with an intervention that provides a healthy sleep habits video link [1]. This ordering matters because interventions are attached to objectives rather than floating independently in the plan.
Salt Lake County's UWITS guide makes the same hierarchy explicit through its Outline section, instructing users to add problems, then goals, then objectives [4]. The documented workflow states that interventions should be added first and then associated with an existing objective, and that multiple problems can support multiple goals and objectives [4]. At least one problem must be added to the plan, and each problem must contain specified elements [4]. WITS similarly organizes the plan into workspace sections with completion requirements displayed on the right as the provider works through the plan [2]. These sources agree on content structure, but the ordering rules differ slightly: UWITS documents a deliberate intervention-first association workflow, while athenahealth shows objectives and interventions being added within the Goals card [1][4].
Attestation, Signatures, and Patient Endorsement
Documentation often requires a formal sign-off step. In athenahealth, the Attestation workflow allows a provider to attest that the treatment plan accurately reflects what was discussed during a therapeutic session [1]. The workflow can also request attestation from the patient, a person authorized to sign on behalf of the patient, and supervising providers [1]. After provider attestation, the patient receives an SMS text or email with a link to the finalized plan and can select Agree or Deny [1]. This represents a patient-facing endorsement mechanism built into the vendor workflow, not a universal clinical requirement, although organizations may direct its use [1].
UWITS takes a different approach to completion. In the Salt Lake County guide, all listed completion requirements must be finished before any Treatment Team member signature, and the plan status moves from Pending to Active only after a signed version is created [4]. A Pending plan can be deleted; an Active plan is the current signed version, and a Retired plan is superseded by a newer signed version, with history available for review [4]. The treatment team structure itself is a prerequisite: at least one Treatment Team member must exist before a treatment plan can be completed [4]. These rules mean the signature gate is tied to team composition and plan version state, which differs from athenahealth's focus on patient and supervising provider attestation [1][4].
A Concrete Evaluation Exercise for One Organization
Consider a CCBHC that runs outpatient mental health and SUD services and must meet the six-month treatment plan review criterion while also serving residential clients. The evaluation team would start by asking how the EHR maps the problem-goal-objective-intervention hierarchy and whether it exposes the treatment team as a completion prerequisite [4][6]. Next, it would test whether review dates auto-calculate and what default appears when staff leave the field blank; the UWITS 30-day fallback is one documented example, but the organization should confirm its own system's behavior because athenahealth's guide only states a common 90-day practice, not a system-enforced default [1][4].
The team would then examine attestation. For outpatient clients, it would verify that the system can capture patient, supervising provider, and staff endorsements in the manner required by its program. For residential clients, it would confirm whether a standalone treatment plan workflow or a care-plan progress note can meet the 10-calendar-day admission requirement documented for ASAM 3.1, 3.3, and 3.5 [5]. This approach evaluates decision points against the organization's own payer and certification obligations rather than selecting a system based on product-page language. The evaluation remains incomplete without live configuration testing, because the source documents describe capabilities and requirements but do not establish performance, client satisfaction, or clinical outcomes.
Review Timing and Plan Lifecycle Decisions
The systems also document different defaults for when a plan must be revisited. athenahealth lets users enter a date of next review and notes that most therapists enter the patient's next appointment or set the date for 90 days from the start of a plan, because many organizations require staff to renew or update plans at that interval [1]. This is a stated norm within the vendor's user guide, not a regulatory mandate. The system also supports changing an intervention's state to Active, Inactive, Completed, or Canceled at any time, with filters available to access historical states [1].
UWITS documents an automated calculation path. If a user enters a review period in days, the next review date is calculated automatically; if the next review date is entered first, the review period is calculated [4]. If neither field is populated, the guide states that a default of 30 days is automatically calculated from the Active Date for the Next Review Date [4]. This means the Salt Lake County configuration applies a 30-day fallback when users leave the fields blank, a concrete technical decision point that an implementing organization should verify against its own treatment planning policy. The CCBHC standard adds another layer: SAMHSA criteria referenced by the National Council require treatment plan review and update no less frequently than every six months unless a more stringent standard applies [6].
Regulatory Variations by Setting and Payer
Treatment plan requirements are not uniform across behavioral health settings. The San Francisco Department of Public Health guidelines state that under CalAIM, a comprehensive treatment plan of care is no longer needed for most outpatient specialty mental health services, although a BH Care Plan is still required for certain services and must be reviewed annually [5]. The guidelines identify specific settings where formal care plans remain necessary, including providers using the BHS EHR where an integrated problem list is not yet available, all ASAM 3.1, 3.3, and 3.5 residential programs, Targeted Case Management, and Peer Supportive Services [5]. Substance use providers in those settings may use either a standalone treatment plan uploaded or entered into the EHR, or a care plan progress note outlining treatment goals, measurable objectives, and planned interventions [5].
The same guidelines impose timing differentiations by level of care. Residential providers for ASAM 3.1, 3.3, and 3.5 must complete a Care Plan within 10 calendar days of admission, while ASAM 3.2 withdrawal management programs do not need a Care Plan because they focus on stabilization and transition planning [5]. These are payer-and-program-specific requirements, not general EHR capabilities. An evaluation of treatment plan workflow must therefore distinguish between what the software can do and what a particular state, payer, or certification standard requires the organization to document within that software. A system can support attestation or review-date automation while remaining noncompliant with a program-specific timeline unless the organization configures those controls correctly.
Vendor Claims Versus Documented Workflow Capabilities
eClinicalWorks markets a Behavioral Health EHR that connects assessment, treatment planning, documentation, reporting, and Revenue Cycle Management [8]. The vendor's product page lists enhanced treatment plans with measurable goals and Wiley content, Golden Thread Documentation connecting assessment, diagnosis, treatment goals, services, progress, and discharge, and behavioral-health-tuned templates for DAP, SOAP, BIRP, individual, and group documentation [8]. It also says the platform supports person-centered treatment planning with recovery-oriented goals and family or caregiver involvement [8]. These are vendor claims drawn from promotional source text, not independently verified workflow outcomes, and MedtechLedger analysis did not locate a published eClinicalWorks user guide in this public documentation that would confirm the exact step sequence or completion gating.
The National Council's CCBHC-focused guidance offers a requirements-driven alternative to vendor marketing. It tells organizations to look for EHR features that draw from previous visits to build a person-directed treatment plan including needs, strengths, abilities, preferences, and goals, and that allow all care team members to view and update treatment plans [6]. The toolkit also specifies alerts and reminders for regular review, electronic signature functionality so people receiving services can endorse the plan, and standardized templates that lead the documentation process [6]. Part 1 of the same toolkit frames treatment plans as one data element among many that should be implementable, shareable, and revisable across providers, with updates on referrals and individual progress supporting care coordination [7]. This guidance is a planning checklist, not evidence that any listed EHR meets every criterion.
Sources & references
- User Guide — Behavioral Health Treatment Plans · help.athenahealth.com
- WITS Treatment User Guide · mh.alabama.gov
- BHI Workflow Guide for Adult Patient Care | AMA · www.ama-assn.org
- UWITS Treatment plan guide · prod.saltlakecounty.gov
- Clinical Practice Guidelines on Evidence-Based and Best Practices for San Francisco Department of Public Health Behavioral Health Services System of · media.api.sf.gov
- Health Information Technology for CCBHCs Toolkit Part 3: CCBHC Requirements and Needed HIT Capacity · www.thenationalcouncil.org
- Health Information Technology for CCBHCs Toolkit Part 1: Important Considerations for Establishing HIT to Fulfill the CCBHC Model · www.thenationalcouncil.org
- Behavioral Health EHR & Practice Management Solutions From eClinicalWorks - eClinicalWorks · www.eclinicalworks.com