Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/abridge-core-workflow-a

@820dfc8
Run it yourself

Design and verify the clinician workflow from consent through recording, draft review, Linked Evidence, and final note disposition. Use when implementing or auditing an Abridge clinical documentation pathway. Trigger with "map the Abridge note workflow".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/abridge-core-workflow-a

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈70 tokens for metadata: the name and description. ≈1k when used: this file. ≈437 more on demand in 1 file.

Description uses 3.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈280 characters, or 3.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Abridge Encounter-to-Reviewed-Note Workflow

Overview

Define a clinician-in-the-loop path that keeps consent, patient selection, capture quality, draft verification, edits, and finalization explicit. Treat generated content as a draft until the authorized clinician completes the health system's review process.

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's recording guidance tells clinicians to follow organizational consent policy before recording.
  • The Web Editor supports reviewing and editing generated notes, and Linked Evidence supports source verification.
  • A generated note remains subject to clinician review and the health system's documentation policy.

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. Identify care setting, authorized user, patient-selection source, consent rule, note type, and final record destination.
  2. Map the happy path and failure exits from patient selection through recording, note creation, review, editing, and submission.
  3. Use Read, Glob, and Grep to inspect local policies, templates, training, and integration configuration without reading patient data.
  4. Add checks for wrong-patient risk, interrupted capture, missing source support, unsupported statements, and unsigned drafts.
  5. Use WebFetch only for current official Abridge workflow documentation and label tenant-specific behavior separately.
  6. Use Write or Edit to update the workflow artifact, acceptance script, and rollback handoff after owner confirmation.

Approval Boundaries

Do not automate consent, clinical verification, note signing, or chart submission beyond the explicitly approved tenant workflow. A clinician must retain final review authority.

Output

Return actors, states, handoffs, evidence checks, failure exits, clinical owner, and the boundary between generated draft and finalized record. Separate verified facts, tenant-specific evidence, assumptions, and actions still awaiting approval.

Error Handling

Condition Response
Patient identity is ambiguous Stop before recording or opening the draft.
Evidence does not support a statement Correct or remove it before finalization.
Destination workflow differs from the map Hold submission and reconcile the tenant configuration.

Example

The example is a redacted operational receipt, not patient data or proof of vendor certification.

setting=outpatient; consent=confirmed; draft=reviewed; linked-evidence=sampled; clinician-signoff=required; ehr-handoff=approved

Resources

Read the source map before changing a workflow. Recheck tenant-specific implementation evidence for every interface or capability that public documentation does not define.

Next Steps

Revalidate the evidence date and tenant-specific authority before repeating this workflow in another environment, cohort, care setting, or integration mode.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a secure framework for designing Abridge clinical workflows. It includes strict prohibitions against accessing patient data (PHI) and hardcoding credentials, while limiting network activity to official documentation sources.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[care-setting] [note-type]
version
1.5.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "abridge",
  "clinical-workflow",
  "note-review",
  "consent"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live work requires an authorized Abridge tenant, approved test data, and health-system change authority

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/abridge-core-workflow-a