The pathDocumentation Index
Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
Use this file to discover all available pages before exploring further.
/cl/virtual-groups/:sessionId (without a sub-path) is not a registered route in the Clinical core. Virtual group session participation is split into two distinct sub-routes: a join flow for attendees and a host flow for facilitators.
Overview
/cl/virtual-groups/:sessionId is not a registered route. Navigating to it without /join or /host renders NotFound.
The two active sub-routes are:
| Route | Component | Permission |
|---|---|---|
/cl/virtual-groups/:sessionId/join | VirtualGroupJoinPage | cl.group.virtual.attend |
/cl/virtual-groups/:sessionId/host | VirtualGroupHostPage | cl.group.virtual.host |
VirtualGroupJoinPage is a patient-facing pre-session preparation screen. It requires two steps before enabling the telehealth room join button:
- Technology Check — opens
TechnologyCheckSheetto verify camera, microphone, and connection. Completion is recorded intechnology_check_completed_aton the attendance record. - Recording Consent — shown only if
recording_enabledis true on the session. OpensRecordingConsentDialog. Consent is locked once captured (recording_consent_captured_at).
scheduled or in_progress. The join URL (vendor_session_ref) is sourced from useTelehealthMetadata; if absent, the button shows “Awaiting host to start.”
Who it’s for
/joinroute:cl.group.virtual.attendpermission/hostroute:cl.group.virtual.hostpermission
Before you start
- For the join flow: you need
cl.group.virtual.attendpermission and an attendance record for the session. TheattendanceIdcan be passed as a query parameter (?attendanceId=<uuid>). - For the host flow: you need
cl.group.virtual.hostpermission. - The session must be in
scheduledorin_progressstatus to join.
Steps
Navigate to the join page
Open
/cl/virtual-groups/:sessionId/join (optionally appending ?attendanceId=<uuid>). The page loads session details and your attendance record.Complete the technology check
Click “Start” next to “Technology Check”. The
TechnologyCheckSheet guides you through verifying camera, microphone, and network. On completion, the step shows a green checkmark.Capture recording consent (if required)
If the session has recording enabled, click “Capture” next to “Recording Consent”. The
RecordingConsentDialog opens. Once consent is captured, it is locked and cannot be changed for this session.Key concepts
| Term | Meaning |
|---|---|
vendor_session_ref | Telehealth vendor URL for the virtual room, sourced from useTelehealthMetadata; owned by PM-13 integration |
technology_check_completed_at | Timestamp on the attendance record indicating the tech check was completed |
recording_consent_captured_at | Timestamp on the attendance record when recording consent was given; locks the consent for the session |
recording_consent_modality | How consent was captured (RecordingConsentModality type) |
TechnologyCheckSheet | Slide-over component guiding users through camera/mic/network verification |
RecordingConsentDialog | Dialog for capturing and locking recording consent for a specific attendance record |
Related
Clinical
Clinical core overview.
Governance & parity
This page documents shipped product behavior. It is not medical, legal, or
billing advice. Verify against your organization’s policies and applicable
regulations before using it for clinical, compliance, or billing decisions.
Protected health information (PHI) shown in the product is governed by your
tenant’s access controls and is never exposed in this documentation.
Documentation sources
Documentation sources
- src/routes/cl.tsx
- src/cores/cl/pages/VirtualGroupJoinPage.tsx
- src/cores/cl/hooks/useGroupSessions.ts
- src/cores/cl/hooks/useGroupAttendance.ts
- src/cores/cl/hooks/useVirtualGroupSessions.ts
- src/cores/cl/components/virtual-group/TechnologyCheckSheet.tsx
- src/cores/cl/components/virtual-group/RecordingConsentDialog.tsx
- src/cores/cl/types/virtual-group.ts