| name | abridge-install-auth |
| description | Set up Abridge clinical AI platform authentication and EHR integration credentials.
Use when onboarding a healthcare org to Abridge, configuring Epic/Athena integration,
or setting up developer sandbox access for ambient AI documentation.
Trigger: "install abridge", "setup abridge", "abridge auth", "configure abridge credentials".
|
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(pip:*), Grep |
| version | 1.4.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","healthcare","ai","abridge","clinical-documentation"] |
| compatibility | Designed for Claude Code |
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
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)
interface AbridgeEpicConfig {
epicClientId: string;
epicFhirBaseUrl: string;
abridgeOrgId: string;
abridgeApiBaseUrl: string;
: ;
}
: = {
: process..!,
: process..!,
: process..!,
: process..!,
: ,
};
config;