Agent skill · writing content · jeremylongshore
abridge-core-workflow-b
Verify the approved handoff of clinician-reviewed Abridge note sections into Epic templates and downstream workflows. Use when configuring or auditing Abridge-to-Epic documentation flow. Trigger with \"verify the Abridge Epic handoff\".
Why this skill is useful
Provides specific integration patterns and API commands for generating patient summaries and pushing them to patient portals, which the AI wouldn't reliably generate on its own.
What it needs
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 Epic Note Handoff Assurance Overview Prove that reviewed content reaches the intended Epic note sections through the tenant's supported workflow, with clear handling for manual patients, template differences, and patient-facing content. Do not substitute a generic FHIR push for the documented integration. 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 documents a Send Now workflow and Epic SmartLinks for several note sections. Its support guidance states that manually added patients may require copy and paste, and Patient Visit Summaries are not sent directly into Epic in that documented flow. Epic-integrated product behavior varies by licensed deployment, care setting, and implementation phase. 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. Freeze the Epic environment, department, note type, template owner, SmartLink mapping, and approved test-patient procedure. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/abridge-core-workflow-b