abridge-core-workflow-a
Implement Abridge ambient clinical documentation capture-to-note pipeline. Use when building the primary encounter workflow: audio capture, real-time transcription, AI note generation, and EHR note insertion. Trigger: "abridge clinical workflow", "abridge encounter pipeline", "ambient documentation workflow", "abridge note generation".
Best use case
abridge-core-workflow-a is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement Abridge ambient clinical documentation capture-to-note pipeline. Use when building the primary encounter workflow: audio capture, real-time transcription, AI note generation, and EHR note insertion. Trigger: "abridge clinical workflow", "abridge encounter pipeline", "ambient documentation workflow", "abridge note generation".
Teams using abridge-core-workflow-a 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-core-workflow-a/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How abridge-core-workflow-a Compares
| Feature / Agent | abridge-core-workflow-a | 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?
Implement Abridge ambient clinical documentation capture-to-note pipeline. Use when building the primary encounter workflow: audio capture, real-time transcription, AI note generation, and EHR note insertion. Trigger: "abridge clinical workflow", "abridge encounter pipeline", "ambient documentation workflow", "abridge note generation".
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
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.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Abridge Core Workflow A — Encounter-to-Note Pipeline
## Overview
Primary money-path workflow for Abridge: capturing a clinical encounter via ambient listening, processing it through Abridge's generative AI, producing a structured clinical note, and pushing it into the EHR. This is the workflow that runs millions of times daily across health systems using Abridge.
## Prerequisites
- Completed `abridge-install-auth` setup
- EHR integration configured (Epic preferred)
- Audio capture infrastructure (microphone array or mobile device)
- HIPAA-compliant transport layer (TLS 1.3+)
## Instructions
### Step 1: Initialize Encounter Session
```typescript
// src/workflows/encounter-pipeline.ts
import axios, { AxiosInstance } from 'axios';
interface EncounterContext {
patient_id: string; // FHIR Patient resource ID
encounter_id: string; // FHIR Encounter resource ID
provider_id: string; // NPI or FHIR Practitioner ID
specialty: string; // e.g., 'internal_medicine', 'cardiology'
encounter_type: 'outpatient' | 'inpatient' | 'emergency';
department_id?: string;
language: string; // ISO 639-1 (Abridge supports 28+ languages)
}
interface SessionResponse {
session_id: string;
websocket_url: string; // For real-time audio streaming
status: 'initialized' | 'recording' | 'processing' | 'completed';
created_at: string;
}
async function initializeEncounter(
api: AxiosInstance,
context: EncounterContext
): Promise<SessionResponse> {
const { data } = await api.post('/encounters/sessions', {
...context,
capture_mode: 'ambient', // Background listening, no wake word
note_template: 'soap', // SOAP, H&P, progress note, etc.
real_time_preview: true, // Enable live note preview during encounter
smart_phrases_enabled: true, // Support Epic SmartPhrases in output
});
console.log(`Encounter session initialized: ${data.session_id}`);
console.log(`WebSocket URL: ${data.websocket_url}`);
return data;
}
```
### Step 2: Stream Audio via WebSocket
```typescript
// src/workflows/audio-stream.ts
import WebSocket from 'ws';
interface AudioStreamConfig {
sampleRate: 16000; // 16kHz required
channels: 1; // Mono
encoding: 'pcm_s16le'; // 16-bit PCM little-endian
chunkDurationMs: 100; // Send 100ms chunks
}
interface TranscriptFragment {
type: 'transcript_fragment';
speaker: 'provider' | 'patient' | 'unknown';
text: string;
confidence: number;
timestamp_ms: number;
is_final: boolean;
}
interface NotePreview {
type: 'note_preview';
sections: Record<string, string>;
last_updated: string;
}
function streamEncounterAudio(
wsUrl: string,
audioSource: NodeJS.ReadableStream
): Promise<void> {
return new Promise((resolve, reject) => {
const ws = new WebSocket(wsUrl, {
headers: {
'Authorization': `Bearer ${process.env.ABRIDGE_CLIENT_SECRET}`,
'X-Org-Id': process.env.ABRIDGE_ORG_ID!,
},
});
ws.on('open', () => {
console.log('Audio stream connected');
// Stream audio chunks
audioSource.on('data', (chunk: Buffer) => {
if (ws.readyState === WebSocket.OPEN) {
ws.send(chunk);
}
});
audioSource.on('end', () => {
ws.send(JSON.stringify({ type: 'end_of_stream' }));
});
});
ws.on('message', (data: Buffer) => {
const msg = JSON.parse(data.toString());
if (msg.type === 'transcript_fragment') {
const frag = msg as TranscriptFragment;
if (frag.is_final) {
console.log(`[${frag.speaker}]: ${frag.text}`);
}
}
if (msg.type === 'note_preview') {
const preview = msg as NotePreview;
console.log('Live note preview updated:', Object.keys(preview.sections).join(', '));
}
});
ws.on('close', () => resolve());
ws.on('error', reject);
});
}
export { streamEncounterAudio, AudioStreamConfig };
```
### Step 3: Generate and Retrieve Clinical Note
```typescript
// src/workflows/note-generation.ts
interface ClinicalNote {
note_id: string;
session_id: string;
template: 'soap' | 'hp' | 'progress' | 'procedure';
sections: {
chief_complaint: string;
history_present_illness: string;
review_of_systems: string;
physical_exam: string;
assessment: string;
plan: string;
medications?: string;
allergies?: string;
};
coding: {
icd10: Array<{ code: string; description: string; confidence: number }>;
cpt: Array<{ code: string; description: string; confidence: number }>;
hcc: Array<{ code: string; raf_score: number }>; // Risk adjustment
};
source_map: Array<{
section: string;
note_text: string;
source_transcript: string;
audio_start_ms: number;
audio_end_ms: number;
}>;
quality_metrics: {
confidence_score: number;
completeness_score: number;
coding_accuracy: number;
};
}
async function generateAndRetrieveNote(
api: AxiosInstance,
sessionId: string
): Promise<ClinicalNote> {
// Finalize session and trigger note generation
await api.post(`/encounters/sessions/${sessionId}/finalize`);
// Poll for completed note (typically 10-30 seconds)
for (let i = 0; i < 60; i++) {
const { data } = await api.get(`/encounters/sessions/${sessionId}/note`);
if (data.status === 'completed') {
return data.note;
}
await new Promise(r => setTimeout(r, 1000));
}
throw new Error(`Note generation timed out for session ${sessionId}`);
}
```
### Step 4: Push Note to EHR via FHIR
```typescript
// src/workflows/ehr-push.ts
import axios from 'axios';
interface FhirDocumentReference {
resourceType: 'DocumentReference';
status: 'current';
type: { coding: Array<{ system: string; code: string; display: string }> };
subject: { reference: string };
context: { encounter: Array<{ reference: string }> };
content: Array<{ attachment: { contentType: string; data: string } }>;
}
async function pushNoteToEpic(
fhirBaseUrl: string,
accessToken: string,
note: { patient_id: string; encounter_id: string; content: string }
): Promise<string> {
const docRef: FhirDocumentReference = {
resourceType: 'DocumentReference',
status: 'current',
type: {
coding: [{
system: 'http://loinc.org',
code: '11506-3',
display: 'Progress note',
}],
},
subject: { reference: `Patient/${note.patient_id}` },
context: { encounter: [{ reference: `Encounter/${note.encounter_id}` }] },
content: [{
attachment: {
contentType: 'text/plain',
data: Buffer.from(note.content).toString('base64'),
},
}],
};
const response = await axios.post(
`${fhirBaseUrl}/DocumentReference`,
docRef,
{ headers: { Authorization: `Bearer ${accessToken}`, 'Content-Type': 'application/fhir+json' } }
);
console.log(`Note pushed to Epic: DocumentReference/${response.data.id}`);
return response.data.id;
}
```
## Output
- Ambient encounter session with real-time transcription
- Structured SOAP note with ICD-10, CPT, and HCC codes
- Source-mapped citations linking AI output to conversation audio
- FHIR DocumentReference created in Epic EHR
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| WebSocket disconnect | Network instability | Implement reconnection with buffered audio |
| Empty transcript | Microphone not capturing | Verify audio input device and sample rate |
| Low confidence score | Background noise | Use directional mic or noise cancellation |
| FHIR push `422` | Invalid resource format | Validate FHIR R4 schema before POST |
| Note generation timeout | Complex multi-specialty encounter | Increase timeout; split into segments |
## Resources
- [Abridge Clinician Platform](https://www.abridge.com/platform/clinicians)
- [FHIR R4 DocumentReference](https://hl7.org/fhir/R4/documentreference.html)
- [Epic FHIR API](https://fhir.epic.com/)
## Next Steps
For patient-facing summaries and portal integration, see `abridge-core-workflow-b`.Related Skills
calendar-to-workflow
Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes. Use when the user mentions calendar events, meeting prep, standup generation, or scheduling workflows. Trigger with phrases like "prep for my meetings", "generate standup notes", "create workflow from calendar", or "summarize today's schedule".
workhuman-core-workflow-b
Workhuman core workflow b for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow b".
workhuman-core-workflow-a
Workhuman core workflow a for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman core workflow a".
wispr-core-workflow-b
Wispr Flow core workflow b for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow b".
wispr-core-workflow-a
Wispr Flow core workflow a for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr core workflow a".
windsurf-core-workflow-b
Execute Windsurf's secondary workflow: Workflows, Memories, and reusable automation. Use when creating reusable Cascade workflows, managing persistent memories, or automating repetitive development tasks. Trigger with phrases like "windsurf workflow", "windsurf automation", "windsurf memories", "cascade workflow", "windsurf slash command".
windsurf-core-workflow-a
Execute Windsurf's primary workflow: Cascade Write mode for multi-file agentic coding. Use when building features, refactoring across files, or performing complex code tasks. Trigger with phrases like "windsurf cascade write", "windsurf agentic coding", "windsurf multi-file edit", "cascade write mode", "windsurf build feature".
webflow-core-workflow-b
Execute Webflow secondary workflows — Sites management, Pages API, Forms submissions, Ecommerce (products/orders/inventory), and Custom Code via the Data API v2. Use when managing sites, reading pages, handling form data, or working with Webflow Ecommerce products and orders. Trigger with phrases like "webflow sites", "webflow pages", "webflow forms", "webflow ecommerce", "webflow products", "webflow orders".
webflow-core-workflow-a
Execute the primary Webflow workflow — CMS content management: list collections, CRUD items, publish items, and manage content lifecycle via the Data API v2. Use when working with Webflow CMS collections and items, managing blog posts, team members, or any dynamic content. Trigger with phrases like "webflow CMS", "webflow collections", "webflow items", "create webflow content", "manage webflow CMS", "webflow content management".
veeva-core-workflow-b
Veeva Vault core workflow b for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow b".
veeva-core-workflow-a
Veeva Vault core workflow a for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva core workflow a".
vastai-core-workflow-b
Execute Vast.ai secondary workflow: multi-instance orchestration, spot recovery, and cost optimization. Use when running distributed training, handling spot preemption, or optimizing GPU spend across multiple instances. Trigger with phrases like "vastai distributed training", "vastai spot recovery", "vastai multi-gpu", "vastai cost optimization".