abridge-common-errors
Diagnose and fix common Abridge clinical AI integration errors. Use when encountering EHR connectivity failures, note generation errors, audio streaming issues, or FHIR validation problems with Abridge. Trigger: "abridge error", "abridge not working", "abridge debug", "fix abridge issue", "abridge troubleshoot".
Best use case
abridge-common-errors is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Diagnose and fix common Abridge clinical AI integration errors. Use when encountering EHR connectivity failures, note generation errors, audio streaming issues, or FHIR validation problems with Abridge. Trigger: "abridge error", "abridge not working", "abridge debug", "fix abridge issue", "abridge troubleshoot".
Teams using abridge-common-errors should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/abridge-common-errors/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How abridge-common-errors Compares
| Feature / Agent | abridge-common-errors | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Diagnose and fix common Abridge clinical AI integration errors. Use when encountering EHR connectivity failures, note generation errors, audio streaming issues, or FHIR validation problems with Abridge. Trigger: "abridge error", "abridge not working", "abridge debug", "fix abridge issue", "abridge troubleshoot".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Abridge Common Errors
## Overview
Comprehensive troubleshooting guide for Abridge clinical documentation integration. Covers authentication failures, EHR connectivity, audio streaming, note generation, and FHIR push errors.
## Error Reference
### Authentication & Authorization Errors
| Code | Error | Root Cause | Fix |
|------|-------|-----------|-----|
| `401` | `INVALID_CREDENTIALS` | Expired or wrong partner secret | Rotate credentials in Abridge Partner Portal |
| `401` | `TOKEN_EXPIRED` | SMART on FHIR token expired | Refresh token before 60-min expiry |
| `403` | `ORG_NOT_PROVISIONED` | org_id not activated | Contact Abridge sales engineer |
| `403` | `SPECIALTY_NOT_LICENSED` | Specialty not in contract | Check licensed specialties in Partner Portal |
| `403` | `PROVIDER_NOT_ENROLLED` | Provider not onboarded | Complete provider enrollment in Abridge admin |
### Session & Encounter Errors
| Code | Error | Root Cause | Fix |
|------|-------|-----------|-----|
| `409` | `SESSION_ALREADY_ACTIVE` | Duplicate session for same encounter | Reuse existing session_id |
| `422` | `INVALID_SPECIALTY` | Unsupported specialty code | Use codes from `/specialties` endpoint |
| `422` | `PATIENT_NOT_FOUND` | Patient ID not in EHR context | Verify FHIR Patient resource exists |
| `408` | `SESSION_TIMEOUT` | Session idle > 30 minutes | Create new session; old ones auto-expire |
| `500` | `SESSION_CORRUPTED` | Server-side state error | Create new session; report to Abridge support |
### Audio & Transcription Errors
```typescript
// Common audio streaming diagnostics
async function diagnoseAudioIssues(wsUrl: string): Promise<string[]> {
const issues: string[] = [];
// Check WebSocket connectivity
try {
const ws = new WebSocket(wsUrl);
await new Promise((resolve, reject) => {
ws.onopen = resolve;
ws.onerror = reject;
setTimeout(() => reject(new Error('Connection timeout')), 5000);
});
ws.close();
} catch {
issues.push('WebSocket connection failed — check firewall allows wss:// on port 443');
}
// Check audio format requirements
// Abridge requires: 16kHz, mono, 16-bit PCM little-endian
const requiredFormat = { sampleRate: 16000, channels: 1, encoding: 'pcm_s16le' };
issues.push(`Verify audio format: ${JSON.stringify(requiredFormat)}`);
return issues;
}
```
| Symptom | Root Cause | Fix |
|---------|-----------|-----|
| Empty transcript | Microphone not capturing | Check audio input device; verify 16kHz sample rate |
| Garbled transcript | Wrong encoding | Must be 16-bit PCM LE mono at 16kHz |
| Speaker mislabeled | Single-channel audio | Use stereo mic or speaker diarization hints |
| WebSocket drops | Network instability | Implement reconnect with buffered chunks |
| High latency | Large audio chunks | Send 100ms chunks, not full sentences |
### Note Generation Errors
```typescript
// Note generation failure handler
async function handleNoteFailure(sessionId: string, error: any): Promise<void> {
const status = error.response?.status;
const code = error.response?.data?.error_code;
switch (code) {
case 'INSUFFICIENT_CONTENT':
console.error('Transcript too short — need at least 30 seconds of clinical conversation');
break;
case 'UNSUPPORTED_LANGUAGE':
console.error('Language not in Abridge supported set (28+ languages)');
break;
case 'TEMPLATE_NOT_FOUND':
console.error('Note template not available — use: soap, hp, progress, procedure');
break;
case 'GENERATION_TIMEOUT':
console.error('Note generation exceeded 120s — complex encounter, retry once');
break;
default:
console.error(`Unknown note error: ${status} ${code}`);
}
}
```
### FHIR Integration Errors
| Error | Root Cause | Fix |
|-------|-----------|-----|
| FHIR `422 Unprocessable` | Invalid DocumentReference | Validate against FHIR R4 schema |
| FHIR `401 Unauthorized` | Epic token expired | Re-authenticate via SMART on FHIR |
| FHIR `404 Not Found` | Wrong FHIR base URL | Verify Epic FHIR endpoint in EHR config |
| FHIR `409 Conflict` | Duplicate document ID | Generate unique DocumentReference IDs |
| Epic SmartPhrase error | Template mismatch | Verify SmartPhrase names match Epic config |
### HIPAA Compliance Errors
```typescript
// PHI leak detection in error logs
function auditErrorLog(error: any): void {
const serialized = JSON.stringify(error);
// Check for accidental PHI in error output
const phiPatterns = [
/\b\d{3}-\d{2}-\d{4}\b/, // SSN
/\b\d{10}\b/, // MRN (10-digit)
/\b[A-Z][a-z]+\s[A-Z][a-z]+\b/, // Patient names (heuristic)
/\b\d{1,2}\/\d{1,2}\/\d{4}\b/, // DOB
];
for (const pattern of phiPatterns) {
if (pattern.test(serialized)) {
console.error('WARNING: Possible PHI detected in error log — redact before logging');
return;
}
}
}
```
## Diagnostic Script
```bash
#!/bin/bash
# abridge-diagnostic.sh — Run before opening a support ticket
echo "=== Abridge Integration Diagnostics ==="
# 1. Check credentials
echo "Checking credentials..."
curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $ABRIDGE_CLIENT_SECRET" \
-H "X-Org-Id: $ABRIDGE_ORG_ID" \
"${ABRIDGE_BASE_URL}/health"
# 2. Check FHIR server
echo "Checking FHIR connectivity..."
curl -s -o /dev/null -w "%{http_code}" \
"${EPIC_FHIR_BASE_URL}/metadata"
# 3. Check WebSocket
echo "Checking WebSocket..."
curl -s -o /dev/null -w "%{http_code}" \
--header "Upgrade: websocket" \
"${ABRIDGE_BASE_URL/http/ws}/ws/health"
echo "=== Diagnostics Complete ==="
```
## Output
- Identified root cause from error code lookup
- Applied targeted fix for the specific error
- HIPAA-safe error logging verified
## Resources
- [Abridge Platform](https://www.abridge.com/product)
- [FHIR R4 Operation Outcomes](https://hl7.org/fhir/R4/operationoutcome.html)
- [HIPAA Breach Notification Rule](https://www.hhs.gov/hipaa/for-professionals/breach-notification/)
## Next Steps
For collecting debug evidence for support tickets, see `abridge-debug-bundle`.Related Skills
workhuman-common-errors
Workhuman common errors for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman common errors".
wispr-common-errors
Wispr Flow common errors for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr common errors".
windsurf-common-errors
Diagnose and fix common Windsurf IDE and Cascade errors. Use when Cascade stops working, Supercomplete fails, indexing hangs, or encountering Windsurf-specific issues. Trigger with phrases like "windsurf error", "fix windsurf", "windsurf not working", "cascade broken", "windsurf slow".
webflow-common-errors
Diagnose and fix Webflow Data API v2 errors — 400, 401, 403, 404, 409, 429, 500. Use when encountering Webflow API errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "webflow error", "fix webflow", "webflow not working", "debug webflow", "webflow 429", "webflow 401".
vercel-common-errors
Diagnose and fix common Vercel deployment and function errors. Use when encountering Vercel errors, debugging failed deployments, or troubleshooting serverless function issues. Trigger with phrases like "vercel error", "fix vercel", "vercel not working", "debug vercel", "vercel 500", "vercel build failed".
veeva-common-errors
Veeva Vault common errors for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva common errors".
vastai-common-errors
Diagnose and fix Vast.ai common errors and exceptions. Use when encountering Vast.ai errors, debugging failed instances, or troubleshooting GPU rental issues. Trigger with phrases like "vastai error", "fix vastai", "vastai not working", "debug vastai", "vastai instance failed".
twinmind-common-errors
Diagnose and fix TwinMind common errors and exceptions. Use when encountering transcription errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "twinmind error", "fix twinmind", "twinmind not working", "debug twinmind", "transcription failed".
together-common-errors
Together AI common errors for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together common errors".
techsmith-common-errors
TechSmith common errors for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith common errors".
supabase-common-errors
Diagnose and fix Supabase errors across PostgREST, PostgreSQL, Auth, Storage, and Realtime. Use when encountering error codes like PGRST301, 42501, 23505, or auth failures. Use when debugging failed queries, RLS policy violations, or HTTP 4xx/5xx responses. Trigger with "supabase error", "fix supabase", "PGRST", "supabase 403", "RLS not working", "supabase auth error", "unique constraint", "foreign key violation".
stackblitz-common-errors
Fix WebContainer and StackBlitz errors: COOP/COEP, SharedArrayBuffer, boot failures. Use when WebContainers fail to boot, embeds don't load, or processes crash inside WebContainers. Trigger: "stackblitz error", "webcontainer error", "SharedArrayBuffer not defined".