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 Telehealth Configuration page at /pm/telehealth/configuration lets authorized administrators view and manage the organization’s telehealth platform integration records, including platform name, default modality, active status, and vault-stored API key references.

​
Overview

The Telehealth Configuration page queries pm_telehealth_configuration for the current organization and renders one card per record. Each card displays the platform name, default modality (defaulting to audio_video when not set), active/inactive status, and a masked indicator when an API key vault reference is configured. The page is intentionally read-only in the current UI; creation and editing of configurations are performed outside this interface.

​
Who it’s for

Requires permission pm.telehealth_configuration.admin (PM_PERMISSIONS.TELEHEALTH_CONFIGURATION_ADMIN). This is an administrative permission and is not expected to be held by standard clinical or scheduling staff.

​
Before you start

  • You must hold the pm.telehealth_configuration.admin permission.
  • A telehealth platform integration must be provisioned by an administrator before any configuration records appear.

​
Steps

1

Navigate to Telehealth Configuration

Go to /pm/telehealth/configuration. The page loads and shows all telehealth platform configurations for your organization, ordered by creation date descending.
2

Review platform records

Each card shows: platform name, default modality, active/inactive status. If an API key vault reference is stored, the page shows “API Key: ••••••• (vault ref configured)” — the actual key is never displayed.

​
Key concepts

Each configuration record can specify a default modality. The UI falls back to displaying audio_video when no modality is set. Observable modality enum values from the hook type: audio_video, audio_only, store_forward, remote_monitoring.
The api_key_vault_ref field stores a reference string pointing to a secrets vault, not the raw API key. The UI only confirms whether a reference is configured; it never renders the key value.
When no configuration records exist, a card with the message “No telehealth platform configured. Contact your administrator to set up a video provider integration.” is displayed.

Practice Management

Overview of the Practice Management 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/pm.tsx
  • src/cores/pm/pages/TelehealthConfigurationPage.tsx
  • src/cores/pm/hooks/useTelehealthConfiguration.ts
  • src/platform/permissions/constants.ts