Agent skill · software engineering · jeremylongshore
abridge-reference-architecture
Define an Abridge reference architecture that separates vendor, EHR, identity, device, customer, and clinical authority boundaries. Use when reviewing an enterprise Abridge design. Trigger with \"design the Abridge architecture\".
Why this skill is useful
Adds detailed implementation patterns and executable scripts for Abridge clinical AI integration that are not commonly found in public documentation.
What it needs
Requires node installed locally. Requires abridge account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Abridge Health-System Integration Architecture Overview Produce a tenant-grounded component and trust-boundary model for clinician capture, Abridge processing, review, Linked Evidence, EHR handoff, identity, support, telemetry, and downtime. Show unknown private interfaces explicitly instead of filling them with generic REST or FHIR assumptions. Prerequisites The authorized Abridge environment, clinical owner, and health-system policy set Current tenant-specific implementation evidence for every private interface in scope Synthetic data or the organization's formally approved test-record procedure Tool Discipline Use Read, Glob, and Grep to inspect repository configuration, adapters, tests, policies, and existing evidence. Use WebFetch only for current official Abridge, HHS, or named EHR documentation. Use Write or Edit only after confirming scope, environment, owners, patient-data boundary, and approval state. These tools do not confer access to Abridge, an EHR, or a clinical record; return exact operator steps or an approval-gated handoff for live actions. Current Contract Abridge publicly documents application and Epic-integrated user workflows across multiple care settings. Linked Evidence supports review by relating generated text to source material. Exact data flows, retention, interfaces, identity protocols, and EHR mappings require tenant and vendor evidence. Authentication Use only the health system's provisioned Abridge application access, SSO, administrative role, or tenant-specific partner authentication documented for the approved environment. Do not infer public API credentials, reuse production secrets in tests, or expose tokens and session material. Verify identity owner, least privilege, environment binding, storage, rotation, and revocation before any authenticated action. Instructions 1. Inventory actors, care settings, devices, Abridge tenant capabilities, EHR modules, identity systems, networks, support channels, and owners. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/abridge-reference-architecture--a5a71e