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 Admin Docs (Transcription Vendor Admin) screen manages transcription vendor configuration at the route /transcription/admin/vendors.

​
Overview

The screen presents three tabs — Vendor BAAs, Jurisdiction Routing, and Org Defaults — for administering ambient clinical transcription vendor settings. The “Vendor BAAs” tab (VendorBaaTable) manages signed Business Associate Agreements with transcription vendors. “Jurisdiction Routing” (JurisdictionRoutingTable) configures which vendor is selected based on jurisdiction. “Org Defaults” (OrgVendorDefaultsCard) sets the fallback vendor configuration for the organization.

​
Who it’s for

Required permission: pf.transcription.vendors.manage

​
Before you start

  • You must hold the pf.transcription.vendors.manage permission.
  • Transcription must be enabled for the organization.

​
Steps

1

Open Transcription Vendor Admin

Navigate to /transcription/admin/vendors.
2

Review Vendor BAAs

On the BAAs tab, view and manage signed Business Associate Agreements with transcription vendors.
3

Configure Jurisdiction Routing

Switch to the Routing tab to set jurisdiction-aware vendor selection rules.
4

Set Org Defaults

On the Defaults tab, configure the organization-wide fallback transcription vendor.

​
Key concepts

  • BAA (Business Associate Agreement) — contractual requirement for vendors handling PHI
  • Jurisdiction Routing — rules for selecting a transcription vendor based on jurisdiction
  • Org Defaults — fallback vendor settings applied when no jurisdiction rule matches

Platform Foundation

Platform Foundation overview.

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/platform.tsx
  • src/platform/transcription/admin/pages/TranscriptionVendorAdminPage.tsx
  • src/platform/transcription/admin/components/VendorBaaTable.tsx
  • src/platform/transcription/admin/components/JurisdictionRoutingTable.tsx
  • src/platform/transcription/admin/components/OrgVendorDefaultsCard.tsx