abridge-install-auth

# Abridge Install & Auth ## Overview Configure Abridge ambient AI platform credentials and EHR integration tokens. Abridge is an enterprise clinical documentation platform — it does not have a public npm/pip SDK. Integration happens through EHR-embedded workflows (Epic Pal, Athena, eClinicalWorks) and partner API access. ## Prerequisites - Healthcare organization with Abridge contract - EHR system access (Epic, Athena, eClinicalWorks, Cerner, or AllScripts) - Abridge Partner Portal credentials from your sales engineer - HIPAA-compliant infrastructure (required for PHI handling) ## Instructions ### Step 1: Obtain Abridge Partner Credentials ```bash # Abridge uses partner-issued credentials, not self-service API keys # Contact your Abridge sales engineer for: # 1. Partner API client_id and client_secret # 2. Organization ID (org_id) # 3. Sandbox environment URL # Store credentials securely (never in source control) cat > .env.local << 'EOF' ABRIDGE_CLIENT_ID=partner_xxxxxxxxxxxx ABRIDGE_CLIENT_SECRET=secret_xxxxxxxxxxxx ABRIDGE_ORG_ID=org_xxxxxxxxxxxx ABRIDGE_BASE_URL=https://api.abridge.com/v1 ABRIDGE_SANDBOX_URL=https://sandbox.api.abridge.com/v1 EOF chmod 600 .env.local echo ".env.local" >> .gitignore ``` ### Step 2: Configure Epic EHR Integration (Most Common Path) ```typescript // src/config/abridge-ehr.ts // Abridge is Epic's first "Pal" — integration uses Epic's FHIR R4 APIs interface AbridgeEpicConfig { epicClientId: string; // From Epic App Orch...