abridge-webhooks-events
Implement Abridge webhook handling for clinical documentation events. Use when receiving note completion notifications, encounter status changes, provider enrollment events, or quality alert callbacks from Abridge. Trigger: "abridge webhook", "abridge events", "abridge notifications", "abridge note completed event", "abridge encounter event".
Best use case
abridge-webhooks-events is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement Abridge webhook handling for clinical documentation events. Use when receiving note completion notifications, encounter status changes, provider enrollment events, or quality alert callbacks from Abridge. Trigger: "abridge webhook", "abridge events", "abridge notifications", "abridge note completed event", "abridge encounter event".
Teams using abridge-webhooks-events 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-webhooks-events/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How abridge-webhooks-events Compares
| Feature / Agent | abridge-webhooks-events | 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 webhook handling for clinical documentation events. Use when receiving note completion notifications, encounter status changes, provider enrollment events, or quality alert callbacks from Abridge. Trigger: "abridge webhook", "abridge events", "abridge notifications", "abridge note completed event", "abridge encounter event".
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.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
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 Webhooks & Events
## Overview
Handle Abridge webhook events for clinical documentation lifecycle: note completion, encounter status changes, quality alerts, and provider enrollment notifications. All webhook payloads are HIPAA-scoped (contain session IDs but no PHI).
## Abridge Event Types
| Event | Trigger | Use Case |
|-------|---------|----------|
| `encounter.session.completed` | Note generation finished | Push note to EHR |
| `encounter.session.failed` | Note generation failed | Alert clinical team |
| `encounter.note.reviewed` | Clinician reviewed/edited note | Update EHR with final version |
| `encounter.note.signed` | Clinician signed the note | Lock note in EHR |
| `patient.summary.ready` | Patient summary generated | Push to patient portal |
| `provider.enrolled` | Provider onboarded | Update provider roster |
| `quality.alert` | Low confidence or missing content | Flag for clinical review |
## Instructions
### Step 1: Webhook Endpoint with Signature Verification
```typescript
// src/webhooks/abridge-webhook-handler.ts
import express from 'express';
import crypto from 'crypto';
const router = express.Router();
// CRITICAL: Use raw body for signature verification
router.post('/webhooks/abridge',
express.raw({ type: 'application/json' }),
async (req, res) => {
const signature = req.headers['x-abridge-signature'] as string;
const timestamp = req.headers['x-abridge-timestamp'] as string;
if (!verifySignature(req.body, signature, timestamp)) {
return res.status(401).json({ error: 'Invalid signature' });
}
const event = JSON.parse(req.body.toString());
// Idempotency check
if (await isProcessed(event.event_id)) {
return res.status(200).json({ status: 'already_processed' });
}
// Process asynchronously — respond immediately
processEvent(event).catch(err =>
console.error(`Event processing failed: ${event.event_id}`, err)
);
res.status(200).json({ received: true });
}
);
function verifySignature(payload: Buffer, signature: string, timestamp: string): boolean {
const secret = process.env.ABRIDGE_WEBHOOK_SECRET!;
const maxAge = 300000; // 5 minutes
if (Date.now() - parseInt(timestamp) * 1000 > maxAge) {
console.error('Webhook timestamp expired');
return false;
}
const expected = crypto
.createHmac('sha256', secret)
.update(`${timestamp}.${payload.toString()}`)
.digest('hex');
return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
}
```
### Step 2: Event Router
```typescript
// src/webhooks/event-router.ts
interface AbridgeEvent {
event_id: string;
type: string;
timestamp: string;
data: {
session_id?: string;
note_id?: string;
provider_id?: string;
status?: string;
quality_score?: number;
};
}
type EventHandler = (data: AbridgeEvent['data']) => Promise<void>;
const handlers: Record<string, EventHandler> = {
'encounter.session.completed': async (data) => {
console.log(`Note ready for session ${data.session_id}`);
// Fetch note and push to EHR
await fetchAndPushNote(data.session_id!);
},
'encounter.session.failed': async (data) => {
console.error(`Note generation failed: ${data.session_id} — ${data.status}`);
// Alert clinical operations team
await sendClinicalAlert(data.session_id!, 'Note generation failed');
},
'encounter.note.signed': async (data) => {
console.log(`Note signed: ${data.note_id}`);
// Lock note in EHR — no further edits
await lockNoteInEhr(data.note_id!);
},
'patient.summary.ready': async (data) => {
console.log(`Patient summary ready: ${data.session_id}`);
// Push to patient portal
await pushSummaryToPortal(data.session_id!);
},
'quality.alert': async (data) => {
console.warn(`Quality alert: session ${data.session_id}, score ${data.quality_score}`);
// Flag for clinical review if score < 0.7
if ((data.quality_score || 0) < 0.7) {
await flagForReview(data.session_id!);
}
},
};
async function processEvent(event: AbridgeEvent): Promise<void> {
const handler = handlers[event.type];
if (!handler) {
console.log(`Unhandled event: ${event.type}`);
return;
}
await handler(event.data);
await markProcessed(event.event_id);
}
```
### Step 3: Idempotency Store
```typescript
// src/webhooks/idempotency.ts
// Use Redis or database for production — in-memory for dev
const processedEvents = new Map<string, number>();
async function isProcessed(eventId: string): Promise<boolean> {
return processedEvents.has(eventId);
}
async function markProcessed(eventId: string): Promise<void> {
processedEvents.set(eventId, Date.now());
// Clean up events older than 7 days
const cutoff = Date.now() - 7 * 24 * 60 * 60 * 1000;
for (const [id, ts] of processedEvents) {
if (ts < cutoff) processedEvents.delete(id);
}
}
```
### Step 4: Webhook Registration
```bash
# Register webhook endpoint with Abridge
curl -X POST "${ABRIDGE_BASE_URL}/webhooks" \
-H "Authorization: Bearer ${ABRIDGE_CLIENT_SECRET}" \
-H "X-Org-Id: ${ABRIDGE_ORG_ID}" \
-H "Content-Type: application/json" \
-d '{
"url": "https://your-service.run.app/webhooks/abridge",
"events": [
"encounter.session.completed",
"encounter.session.failed",
"encounter.note.signed",
"patient.summary.ready",
"quality.alert"
],
"secret": "your-webhook-secret"
}'
```
## Output
- Secure webhook endpoint with HMAC signature verification
- Event router with handlers for all clinical documentation events
- Idempotency store preventing duplicate processing
- Webhook registration via Abridge API
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Invalid signature | Wrong webhook secret | Verify secret matches Abridge config |
| Timestamp expired | Clock drift > 5 min | Sync server clock via NTP |
| Duplicate processing | Missing idempotency | Implement event ID tracking |
| Handler timeout | Slow EHR push | Process async; respond 200 immediately |
## Resources
- [Abridge Platform](https://www.abridge.com/product)
- [HMAC Signature Verification](https://nodejs.org/api/crypto.html#cryptocreatehmacsignedalgorithm-key-options)
## Next Steps
For performance optimization, see `abridge-performance-tuning`.Related Skills
workhuman-webhooks-events
Workhuman webhooks events for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman webhooks events".
wispr-webhooks-events
Wispr Flow webhooks events for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr webhooks events".
windsurf-webhooks-events
Build Windsurf extensions and integrate with VS Code extension API events. Use when building custom Windsurf extensions, tracking editor events, or integrating Windsurf with external tools via extension development. Trigger with phrases like "windsurf extension", "windsurf events", "windsurf plugin", "build windsurf extension", "windsurf API".
webflow-webhooks-events
Implement Webflow webhook registration, signature verification, and event handling for form_submission, site_publish, ecomm_new_order, page_created, and more. Use when setting up webhook endpoints, implementing event-driven workflows, or handling Webflow notifications. Trigger with phrases like "webflow webhook", "webflow events", "webflow webhook signature", "handle webflow events", "webflow notifications".
vercel-webhooks-events
Implement Vercel webhook handling with signature verification and event processing. Use when setting up webhook endpoints, processing deployment events, or building integrations that react to Vercel deployment lifecycle. Trigger with phrases like "vercel webhook", "vercel events", "vercel deployment.ready", "handle vercel events", "vercel webhook signature".
veeva-webhooks-events
Veeva Vault webhooks events for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva webhooks events".
vastai-webhooks-events
Build event-driven workflows around Vast.ai instance lifecycle events. Use when monitoring instance status changes, implementing auto-recovery, or building event-driven GPU orchestration. Trigger with phrases like "vastai events", "vastai instance monitoring", "vastai status changes", "vastai lifecycle events".
twinmind-webhooks-events
Handle TwinMind meeting events including transcription completion, action item extraction, and calendar sync notifications. Use when implementing webhooks events, or managing TwinMind meeting AI operations. Trigger with phrases like "twinmind webhooks events", "twinmind webhooks events".
together-webhooks-events
Together AI webhooks events for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together webhooks events".
techsmith-webhooks-events
TechSmith webhooks events for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith webhooks events".
supabase-webhooks-events
Implement Supabase database webhooks, pg_net async HTTP, LISTEN/NOTIFY, and Edge Function event handlers with signature verification. Use when setting up database webhooks for INSERT/UPDATE/DELETE events, sending HTTP requests from PostgreSQL triggers, handling Realtime postgres_changes as an event source, or building event-driven architectures. Trigger with phrases like "supabase webhook", "database events", "pg_net trigger", "supabase LISTEN NOTIFY", "webhook signature verify", "supabase event-driven", "supabase_functions.http_request".
stackblitz-webhooks-events
WebContainer lifecycle events: server-ready, port changes, error handling. Use when working with WebContainers or StackBlitz SDK. Trigger: "webcontainer events".