Documentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
Feature ID: CL-55
Status: Planned
Spec Reference: CL-55 virtual telehealth group therapy
Last Updated: 2026-05-09
Overview
CL-55 extends CL-14 group therapy documentation and CL-24 telehealth documentation patterns for virtual and hybrid group sessions, plus non-group multi-party clinical encounters. It integrates with PM-13 for telehealth session lifecycle and PM-07 through CL-39 for charge suggestions. CL-55 does not own telehealth vendor configuration, durable join URLs, or final charge creation.
Ownership Boundaries
| Concern | Owner | Contract |
|---|
| Group clinical documentation and attendance | CL-14 / CL-55 | cl_group_sessions, cl_group_attendance, CL-55 metadata extensions |
| Telehealth vendor configuration, durable join URLs, session lifecycle | PM-13 | pm_telehealth_sessions; see CL-PM-TELEHEALTH.md and PM-13-telehealth-integration-INTEGRATION.md |
| Telehealth clinical documentation patterns | CL-24 | Consent/session documentation patterns consumed by CL-55 |
| Billing and final modifiers/charges | PM-07 | PM owns charges; CL-55 publishes suggestions only |
| Modifier and code validation | PF-70 / PF-96 | Code library and jurisdiction profiles |
| Multi-party clinical encounter record | CL-55 | cl_multi_party_encounters, cl_multi_party_participants |
Data Contracts
CL-55 stores
cl_group_sessions.pm_telehealth_session_id: UUID-only reference to PM-13 pm_telehealth_sessions.id; no direct FK.
cl_group_session_telehealth_metadata: clinical telehealth metadata, contingency plan support, recording consent state, technology failures, PM-13 session reference, and non-PHI vendor session reference.
cl_multi_party_encounters and cl_multi_party_participants: CL-owned N-party encounter records for crisis/family/interpreter/care-team sessions.
CL-55 does not store
- Durable patient/provider join URLs.
- Telehealth vendor credentials or account configuration.
- Final charge, claim, payment, or ledger fields.
- PHI in event payloads or application logs.
Event Contracts
Events use cl_pm_events unless the platform event registry assigns a different channel during implementation. Payloads are UUID-only and PHI-free.
cl_virtual_group_started
Publisher: CL-55
Consumers: PM-07, PF-10/FW-16 if configured
Trigger: Facilitator starts a virtual or hybrid group.
| Field | Type | Required | Notes |
|---|
event_type | string | Yes | cl_virtual_group_started |
organization_id | uuid | Yes | Tenant isolation |
timestamp | string | Yes | ISO 8601 event time |
session_id | uuid | Yes | cl_group_sessions.id |
schedule_id | uuid | No | PM-04 schedule reference if present |
pm_telehealth_session_id | uuid | No | PM-13 session reference |
modality | string | Yes | virtual or hybrid |
started_at | string | Yes | ISO 8601 session start |
facilitator_id | uuid | Yes | Staff profile id |
attendee_count | number | Yes | Count only; no attendee identities |
correlation_id | uuid | No | Idempotency/audit chain |
cl_virtual_group_concluded
Publisher: CL-55
Consumers: PM-07
Trigger: Facilitator completes a virtual or hybrid group.
| Field | Type | Required | Notes |
|---|
event_type | string | Yes | cl_virtual_group_concluded |
organization_id | uuid | Yes | Tenant isolation |
timestamp | string | Yes | ISO 8601 event time |
session_id | uuid | Yes | cl_group_sessions.id |
schedule_id | uuid | No | PM-04 schedule reference if present |
pm_telehealth_session_id | uuid | No | PM-13 session reference |
modality | string | Yes | virtual or hybrid |
concluded_at | string | Yes | ISO 8601 session end |
duration_minutes | number | Yes | Actual documented service duration |
participant_count | number | Yes | Present attendee count |
modifier_suggestions | string[] | Yes | Jurisdiction-resolved suggestions, e.g. Arizona default ["95", "HQ"] |
jurisdiction_profile_id | uuid | No | PF-96 profile used for suggestion |
correlation_id | uuid | No | Idempotency/audit chain |
PHI logging guidelines
- Allowed: UUIDs, modality, counts, durations, modifier codes, jurisdiction profile id, timestamps.
- Prohibited: Patient/member names, DOB, addresses, phone/email, clinical content, session URLs, recording URLs, raw patient location, recording transcripts.
- Retention: Event audit may be logged to
pf_audit_logs; application logs must avoid PHI.
@/platform/scheduling: PM-04 schedule context and PM-13 telehealth session lookup.
@/platform/clinical: CL-39 billing adapter and jurisdiction-aware billing suggestion composition.
@/platform/permissions: PF-30 permission gates for cl.group.virtual.* and cl.multi_party.*.
@/platform/notifications: Optional PF-10 reminders and technology-failure notifications.
Security and Compliance
- RLS uses CL SECURITY DEFINER helpers with UPDATE
WITH CHECK.
- SUD/Part 2 group content remains gated through CL-11 before display, save, export, or AI use.
- Recording consent evidence is auditable and append-only for non-admin users.
- PM-13 vendor sessions must meet HIPAA/BAA requirements before use with PHI-bearing clinical workflows.