Agent skill · software engineering · jeremylongshore
abridge-webhooks-events
Implement Abridge webhook handling for clinical documentation events.
Why this skill is useful
Provides specific implementation details for handling Abridge webhook events, which are crucial for clinical documentation workflows.
What it needs
Requires abridge account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 Prerequisites A publicly reachable, TLS-protected sandbox callback endpoint and a webhook secret stored in the platform’s secret manager. Persistent idempotency storage and a redacted operational log; in-memory storage is suitable only for local development. A documented clinical and EHR fallback when a completed-note event cannot be verified or delivered. Instructions Step 1: Webhook Endpoint with Signature Verification Step 2: Event Router Step 3: Idempotency Store Step 4: Webhook Registration 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 Examples Register a sandbox callback, then send a signed synthetic encounter.session.completed event twice with the same event ID. The first request should verify its timestamp and signature, enqueue the safe note-push work, and create an idempotency record; the second should return the duplicate response without a second push. Capture only the event ID, status, and timing in test output. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/abridge-webhooks-events