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.

This screen lists all multi-party encounters for the organization and is accessible at /cl/multi-party-encounters.

​
Overview

The Multi-Party Encounters page displays a filterable table of encounters that involve more than one participant, including family therapy, mobile crisis, interpreter-assisted, and care team encounters. The list is fetched via useMultiPartyEncountersList and supports filtering by status using a dropdown. Columns show the encounter start datetime, type (resolved to a human-readable label via MULTI_PARTY_ENCOUNTER_TYPE_OPTIONS), modality (outline badge), and status (color-coded badge). Each row is keyboard-accessible and navigates to the encounter detail at /cl/multi-party-encounters/:encounterId. Users with cl.multi_party.host permission see a “New Encounter” button.

​
Who it’s for

Requires the cl.multi_party.view permission. Creating encounters additionally requires cl.multi_party.host.

​
Before you start

  • You must hold cl.multi_party.view to access this page.
  • To schedule a new encounter you must hold cl.multi_party.host.

​
Steps

1

Navigate to Multi-Party Encounters

Open the Clinical core and go to /cl/multi-party-encounters. The page loads all encounters for your organization, sorted by start time (most recent first).
2

Filter by status (optional)

Use the Status dropdown to filter encounters to a specific status. Select “All Statuses” to clear the filter.
3

Open an encounter

Click any row (or press Enter/Space) to navigate to the encounter detail page at /cl/multi-party-encounters/:encounterId.
4

Create a new encounter (if authorized)

If you hold cl.multi_party.host, click “New Encounter” to open the encounter form dialog. After submission, you are automatically navigated to the new encounter’s detail page.

​
Key concepts

The status column uses badge variants: completed (default), in_progress (secondary), cancelled (destructive), all other values (outline). Clinical meaning of transitions between statuses is not determinable from code — SME confirmation required.
When no encounters match (or exist), an empty state with a users icon and “No Multi-Party Encounters” message is shown, describing the supported encounter types. If the data fetch fails, a card with “Unable to load multi-party encounters. Please try again.” is displayed.

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/MultiPartyEncounterListPage.tsx
  • src/cores/cl/hooks/useMultiPartyEncounters.ts