Feature ID: CL-24Documentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
Status: 📝 Planned
Spec Reference: CL-24-telehealth-documentation-compliance.md
Last Updated: 2026-02-24
Overview
CL-24 provides telehealth consent tracking, session-level technology and location metadata, GT/95 modifier logic for billing, and telehealth-specific safety and group documentation. It integrates with CL-04 (progress notes), CL-07 (safety planning), CL-11 (consent), CL-14 (group therapy), and PM-07 (charge capture / fee schedules) for modality and modifier logic.Integration Points (from Spec)
| Dependency | Pattern | Purpose |
|---|---|---|
| PF-01, PF-02 | Direct | Encounter and RBAC context for consent check at encounter (US-2) |
| CL-04 | Data | Progress notes — cl_telehealth_sessions.progress_note_id; service_modality remains on note |
| CL-07 | Data / API | Remote safety planning protocols |
| CL-11 | Data / Boundary | Telehealth consent separate from TPO/SUD consent |
| CL-14 | Data | Group telehealth attendance and consent |
| PM-07 | Data | GT/95 modifier logic reads session modality from CL-24 session data |
API / Data Contracts
Data Provided by CL-24
- Consent:
cl_telehealth_consents— per-patient telehealth consent with expiration (status derived fromexpires_at,revoked_at). - Sessions:
cl_telehealth_sessions— session-level modality, patient location, state jurisdiction, technology verified, connectivity issues; linked tocl_progress_notesviaprogress_note_id.
Consumed by PM-07
- Modifier logic: PM-07 (charge capture / fee schedules) reads session modality (e.g. synchronous_video, synchronous_audio_only) from
cl_telehealth_sessionsto apply GT/95 or payer-specific modifiers. Contract: modality + org/payer rules → modifier selection; feed into charge/claim workflow.
Consent Check at Encounter (PF-01 / PF-02)
- Contract: At encounter start, registration/workflow checks valid telehealth consent for chart (e.g.
deriveTelehealthConsentStatus(planned — not yet implemented): active whenrevoked_at IS NULL AND expires_at > now()). Block or warn if expired/missing; renewal workflow available.
Event Contracts (Planned)
No events currently specified. Modality data is read synchronously by PM-07 fromcl_telehealth_sessions when building charges. If event-based flow is adopted later, document here.
Security and RLS
- All CL-24 tables: RLS enabled; policies use SECURITY DEFINER helpers (e.g.
cl_has_org_access); UPDATE policies include WITH CHECK (§5.2.4). - Consent and session data are PHI; permission-gated UI; no RLS policies query RLS-protected tables directly (§5.7).
Related Docs
- CL-04 Progress Notes & Session Documentation
- CL-PM Encounter-to-Billing — PM-07 charge capture consumes note/session data
- CL-PM Telehealth
- CROSS_CORE_INTEGRATIONS.md