Your EHR Wasn’t Built for Group Therapy: What to Demand Instead
Run four groups a day with eight clients each, and by 5pm you owe 32 individualized notes, not 4. Most group therapy EHR setups treat that math like 32 separate problems, when it should be one workflow. The honest truth is that most behavioral health EHRs were built for one-on-one sessions and bolted groups on later, which is why the demo looked fine and the Wednesday after the IOP cohort starts feels like a fire.
This post is for clinical directors, program leads, and owner-operators actively comparing platforms. We’ll skip the 90853 explainer (you know it) and walk through the four operational axes that separate a real group therapy EHR from a sales-deck checkbox: individualized documentation, attendance-driven workflow, payer-aware billing, and co-facilitation.
Where group therapy notes break standard EHRs
Payers want individualization. Each participant’s note has to reflect that client’s goals, their participation in the group, and their response to the interventions you used. Identical notes across the group are one of the top denial triggers in group claims, and audits catch the pattern fast.1
The clone-and-edit trap is how most EHRs invite that mistake. You write one group narrative, duplicate it across eight participants, and try to swap in a sentence per client. Thirty minutes a group, every group, all week. The documentation is technically there, but the per-participant detail is thin, and the audit risk is real.
What good looks like: one group narrative for the session-level content, plus a per-client layer for goals, participation, and progress, all in one screen. PIMSY’s group notes module works that way, and PAISLY ai progress notes help fill in the individualized layer so the per-participant content is honest, not pasted. Shorter time per note, no identical-text shortcuts.
Attendance drives group therapy documentation and billing
Attendance is the spine of group billing. Who showed up, who was late, who left early, who was a no-show. Every one of those facts changes whether a claim goes out and at what rate. When attendance lives in one screen, scheduling in another, and billing in a third, things slip: no-shows get billed, present clients get missed, and the IOP attendance log stops matching the clinical record.
What good looks like is one group session record where attendance feeds documentation, claim generation, and (for higher levels of care) institutional billing without re-entry. Mark attendance once, and the note knows, the claim knows, the treatment plan compliance tracker knows.
This matters most for intensive outpatient and PHP. Per-week service-hour thresholds depend on documented attendance hours. Miss the documentation, lose the claim, and the program’s revenue model wobbles.2 Groups also change mid-cycle: late additions, early drops, waitlist moves. The enrollment logic in a group therapy EHR has to handle it without the front desk re-creating sessions by hand.
Group billing: 90853, modifiers, and the payer maze
CPT 90853 is the baseline code for group psychotherapy, but every payer treats it differently. Session-length caps, group-size limits, modifier requirements (GT for telehealth, 59 for distinct procedural service), same-day stacking rules with other services. A real group therapy EHR lets billing admins configure those rules per payer in advance, so claims go out clean instead of bouncing back two weeks later.3
For SUD and IOP programs, the claim format itself is different. Standard outpatient EHRs generate CMS-1500 professional claims. IOP and PHP often require UB-04 / 837i institutional claims with revenue codes pulled from documented attendance. If the EHR cannot produce a UB-04, the program either bills wrong or hand-keys claims into a payer portal, which is not a long-term plan.
PIMSY’s clearinghouse integrations cover the major rails (Claim MD, Office Ally, Trizetto, Waystar), with real time eligibility verification before a client joins a group. UB-04 support sits on the Platinum tier, so the same EHR handles professional and institutional billing when the program adds higher levels of care.
Co-facilitation and team-based group therapy software
Most groups in SUD, IOP, eating disorders, and clinical process work involve a lead and a co-facilitator. Sometimes a third clinician supervising a trainee. Many EHRs only let you assign one rendering provider per session, which breaks supervision documentation and, depending on payer rules, breaks the claim outright.
Real group therapy software supports multi-facilitator assignment, role-based access for the supervisor, and a clear record of who provided what. PIMSY’s Team Notes are designed for that: collaborative documentation across co-facilitators on the same session record, with role-based access so a supervisor can review and sign without becoming the rendering provider on the claim.
Why this matters for IOP and PHP specifically: didactic groups often run with a licensed clinician plus a peer support specialist or recovery coach. Both need to appear in the documentation, and the EHR has to model that without forcing a workaround.
What changes when groups move into IOP, PHP, or residential
Practices that start with weekly outpatient groups often add IOP, PHP, or residential within 18 to 24 months. That move is where most EHRs break. IOP and PHP need UB-04 institutional billing, per-week service-hour tracking, and (for residential) bed management, eMAR, and medication inventory. Standard outpatient platforms don’t have it, which means the program is either capped or the practice is shopping for a new EHR mid-growth.
42 CFR Part 2 is non-negotiable if you treat substance use disorder. The 2024 Final Rule aligned Part 2 more closely with HIPAA but raised the documentation and consent bar at the same time.4 Non-certified behavioral health ehr platforms are an increasingly risky bet for SUD groups in 2026, which is why Part 2 certification belongs on any short list of group therapy EHR requirements.
PIMSY is ONC-Certified, HIPAA and 42 CFR Part 2 compliant, and covers IOP, PHP, and residential natively on the higher tiers. The hidden cost of switching EHRs at year three (months of migration, dual-entry, clinical disruption, and at least one botched payroll run) is the reason we tell program leads to vet for institutional billing before they need it, not after.
What to demand from a group therapy EHR
Four things, in order: individualized documentation that doesn’t reward cloning, attendance that drives the rest of the workflow, billing rules that match each payer’s quirks, and co-facilitation that doesn’t require a workaround. “We support group notes” in a vendor demo is a feature checkbox. A real group therapy EHR is a workflow.
Here’s a stress test for the next demo you sit through. Ask the vendor to walk you through one group: eight clients, one no-show, two clients on different payers, with a co-facilitator on the session. Watch how many screens the rep has to open, and count how many times they say “and then you’d just.” That’s the answer.
Ready to see what the PIMSY group workflow actually looks like? Book a demo and we’ll run that exact eight-client scenario, end to end.
Sources
1 CPT Code 90853: Group Therapy Billing Guide
2 No-Show Proof Your IOP: Smarter Group Scheduling & Attendance Tracking
3 Sessions Health: CPT Code 90853, Everything You Need to Know About Group Therapy Billing
