Require Individual Notes for Group Sessions
Providers are blocked from signing or locking a group charting note until every client marked as attended has an individual note. If documentation is missing, a clear error message flags exactly which clients still need one, so no group session closes with incomplete client-level records.
Built by Core Engineering
The problem it solves
Group charting lets providers document a session once and distribute notes across attended clients, but nothing previously stopped a group note from being signed or locked while individual clients were missing documentation. That gap created audit and payer risk, since a "complete" group note could still leave gaps in client-level records.
What's included
- Org-level setting that gates the group note sign/lock action
- Validation check for a non-empty individual note per attended client
- Blocking error message identifying which clients still need notes
- No change to the underlying group charting workflow
- Manual enablement by request through Healthie support
How it works
Enable require-individual-notes-group-charting setting at the org level. Once enabled, the trigger fires whenever a provider attempts to sign or lock a group charting note. The logic checks whether every client marked as Attended has a non-empty individual note. If any attended client is missing a note, the action blocks the sign/lock and displays an error identifying which clients still need documentation; if all attended clients have notes, the sign/lock proceeds as normal.
This organization-level setting blocks providers from signing or locking a group charting note until every client marked as attended has a non-empty individual note. It's built for organizations that need complete, client-level documentation before a group session can be closed. It requires the Charting module. When a provider attempts to sign or lock a note with missing documentation, a clear error message identifies exactly which attended clients still need an individual note. Enabling it currently requires emailing Healthie support to turn on the setting at the org level.
