Skip to main content

​
Overview

This guide covers administrative configuration for the Telehealth module. Only users with pm.telehealth_configuration.admin permission can access these settings.

​
Platform Configuration

Navigate to Practice Management → Scheduling → Telehealth → Configuration tab.

​
Adding a Platform

  1. Click “Add Configuration”.
  2. Fill in:
    • Platform Name — e.g., “Zoom Healthcare”, “Doxy.me”, “Microsoft Teams”
    • API Key — Stored securely in Supabase Vault (never displayed after entry)
    • API Endpoint — The platform’s API base URL
    • Settings — Platform-specific JSON configuration
  3. Toggle “Active” to enable.
Security: API keys are stored as Supabase secrets and accessed only by the edge function. They are never exposed to the browser.

​
Default Platform

Set the default platform in PM Settings → Telehealth:
  • telehealth_default_platform — The platform used when creating new sessions without specifying one.

​
Module Settings

Navigate to Practice Management → Settings (requires pm.admin permission).

​
Telehealth-Specific Settings

​
Permissions

Three permission keys control Telehealth access:

​
Role Assignments

  • org_admin — Automatically receives all three permissions.
  • Front Desk / Scheduler — Grant view and create.
  • Billing Staff — Grant view only (to verify modifiers).
  • IT/Admin — Grant admin for platform configuration.
Permissions are managed in Settings → Roles & Permissions.

​
HIPAA Compliance

​
Business Associate Agreements (BAA)

Before using any video platform in production, ensure:
  1. A signed BAA is on file with the video platform vendor.
  2. The platform meets HIPAA technical safeguards (encryption in transit and at rest).
  3. Recording retention policies align with state and federal requirements.

​
Audit Trail

All telehealth sessions are logged with:
  • Creation timestamp and creator
  • Status transitions (scheduled → active → completed)
  • Patient/provider join timestamps
  • Duration
  • Consent confirmation

​
PHI in Session URLs

Session URLs may contain identifiers. The system:
  • Generates unique, non-guessable session URLs
  • Does not include patient names or MRNs in URLs
  • Expires session URLs after completion

​
Troubleshooting

​
References