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 Vendor Settings page is the administrative hub for configuring transcription vendors: their signed Business Associate Agreements, routing rules by jurisdiction, and organization-wide defaults. Primary route: /transcription/admin/vendors. Alternate route /transcription/vendor-settings was listed as an alternate but was not found in the route files; the primary route should be used.

​
Overview

The page is gated by pf.transcription.vendors.manage. It renders three tabs (active tab synced to ?tab= query parameter via useTabUrlState):
  • Vendor BAAs — VendorBaaTable: list and manage signed Business Associate Agreements with transcription vendors.
  • Jurisdiction Routing — JurisdictionRoutingTable: configure which vendor handles transcription for each jurisdiction.
  • Org Defaults — OrgVendorDefaultsCard: set the organization-wide fallback transcription vendor.

​
Who it’s for

Requires pf.transcription.vendors.manage (route guard).

​
Before you start

  • Transcription vendors must be known before configuring BAAs or routing rules.
  • Your account must have pf.transcription.vendors.manage.

​
Steps

  1. Navigate to /transcription/admin/vendors.
  2. On the Vendor BAAs tab, review or add BAA records for each vendor.
  3. Switch to Jurisdiction Routing to configure vendor assignment by jurisdiction.
  4. Use Org Defaults to set a fallback vendor for the organization.

​
Key concepts

BAA (Business Associate Agreement) — a HIPAA-required agreement between the organization and a vendor handling PHI. Jurisdiction routing — rules that direct transcription requests to the appropriate vendor based on the encounter’s jurisdiction code.

Platform Foundation

Platform Foundation overview.

Governance & parity

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