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 Encounter Detail screen shows a single multi-party encounter record with its participant list at /cl/multi-party-encounters/:encounterId.

​
Overview

The page loads a single multi-party encounter via useMultiPartyEncounterDetail and its participants via useMultiPartyParticipants, both scoped to encounterId. The Encounter Details card shows encounter type (human-readable label from MULTI_PARTY_ENCOUNTER_TYPE_OPTIONS), modality (in_person, virtual, hybrid), status, and optional encounter notes. The Participants card shows each participant’s role (from PARTICIPANT_ROLE_OPTIONS), name (external_participant_name or a fallback of “Staff Member”/“Patient” based on staff_user_id), join time, and recording consent status. Users with cl.multi_party.host can add participants via AddParticipantDialog and remove participants whose consent has not yet been captured.

​
Who it’s for

Requires permission cl.multi_party.view. Users with cl.multi_party.host additionally see the Add participant button and per-row remove controls.

​
Before you start

  • You must have cl.multi_party.view.
  • The cl_multi_party_encounters database migration must be applied; until then, the page shows an error state.
  • The encounter must exist and not be soft-deleted.

​
Steps

1

Open the encounter

Navigate to /cl/multi-party-encounters, then click an encounter row. The detail page loads encounter metadata and the participant table.
2

Review encounter details

The Encounter Details card shows type, modality, status, and any freetext encounter_notes.
3

Add a participant (host only)

Click Add in the Participants card header (requires cl.multi_party.host) to open AddParticipantDialog. Assign a role from PARTICIPANT_ROLE_OPTIONS.
4

Review participant consent status

Each participant row shows a Captured or Pending badge for recording consent based on recording_consent_captured_at.
5

Remove a participant (host only)

For participants who have not yet had recording consent captured, a remove button is available for users with cl.multi_party.host. Clicking it calls removeParticipant scoped to the participant id and encounter_id.

​
Key concepts

Multi-party encounters are typed as family_therapy, mobile_crisis_virtual, interpreter_assisted, care_team_meeting, or other. The display label is resolved from MULTI_PARTY_ENCOUNTER_TYPE_OPTIONS.
Participants are assigned roles from PARTICIPANT_ROLE_OPTIONS: primary_clinician, co_facilitator, peer_specialist, interpreter, patient, family_member, guardian, or other.
  • Migration pending / load error: EmptyState with title “Error Loading Encounter” and message “The feature may not be available yet (migration pending).”
  • Participants error: separate EmptyState for participant load failure.
  • Encounter not found: EmptyState with title “Encounter Not Found”.
  • No participants: “No participants recorded.”
  • Loading: skeleton placeholders for both cards.

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/MultiPartyEncounterDetailPage.tsx
  • src/cores/cl/hooks/useMultiPartyEncounters.ts
  • src/cores/cl/types/multi-party-encounter.ts