Skip to main content

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.

The Group Session detail screen shows session metadata, attendance roster, and per-participant documentation for a single group session at /cl/group-sessions/:sessionId.

Overview

The page loads session metadata from cl_group_sessions via useGroupSessionDetail and the attendance list via useGroupAttendanceBySession. The header shows the session topic, date, and current status badge (scheduled, in_progress, completed, cancelled). A Session Details card displays start and end times, location, group type, and attendee count. An Attendance card lists every enrolled participant with their chart ID, attendance status, sign-in/sign-out times, participation level, and a per-row documentation action. Users with cl.group_sessions.edit and status not completed can edit session metadata via a dialog; users with cl.group_sessions.edit and status in_progress can mark the session complete, which transitions status to completed and publishes a domain event with the present-participant count.

Who it’s for

Requires permission cl.group_sessions.view. Additional actions require:
  • cl.group_sessions.edit — edit session metadata, mark complete
  • cl.group_sessions.delete — delete session (soft delete)
  • cl.group_attendance.edit — add attendees
  • cl.group_attendance.document — write per-participant documentation

Before you start

  • You must have cl.group_sessions.view.
  • The session must exist and not be soft-deleted.
  • To complete a session, it must be in in_progress status.

Steps

1

Open the session

Navigate to /cl/group-sessions, then click a session row. The detail page loads session metadata and the attendance roster.
2

Review session details

The Session Details card shows scheduled time window (actual_start_timeactual_end_time), location, group type, and attendance count relative to max_capacity (if set).
3

Add attendees (optional)

If the session is not completed, click Add Attendee (requires cl.group_attendance.edit) to open the RecordAttendanceDialog and enroll a participant.
4

Document per participant

In the Attendance table, click Document (or Edit) in the Documentation column for a participant row (requires cl.group_attendance.document). This opens IndividualDocumentationDialog scoped to that attendance record.
5

Complete the session

When the session is in_progress and documentation is sufficient, click Complete Session (requires cl.group_sessions.edit). The mutation counts present and late attendees and transitions status to completed.
6

Edit session metadata (optional)

Click Edit (requires cl.group_sessions.edit, session not completed) to open CreateEditGroupSessionDialog.
7

Delete the session (optional)

Click Delete (requires cl.group_sessions.delete, session not completed) and confirm the destructive action. The session is soft-deleted and the user is redirected to /cl/group-sessions.

Key concepts

scheduledin_progresscompleted. A session can also be cancelled. Only in_progress sessions display the Complete Session button. Edit and delete are blocked once a session is completed.
Each row in cl_group_attendance carries an attendance_status of present, absent, excused, late, or early_departure. Only present and late records count toward the participant count passed to completeSession.
  • No attendees: “No attendees recorded yet.” with an Add Attendee button for permitted users.
  • Session not found: “Session not found.” with a back link to /cl/group-sessions.
  • Loading: skeleton placeholders for both the header and attendance table.

Clinical

Overview of the Clinical core.

Governance & parity

Documentation coverage and governance.
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.
  • src/routes/cl.tsx
  • src/cores/cl/pages/GroupSessionDetailPage.tsx
  • src/cores/cl/hooks/useGroupSessions.ts
  • src/cores/cl/hooks/useGroupAttendance.ts
  • src/cores/cl/types/group-therapy.ts