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

/abridge-reference-architecture

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/abridge-reference-architecture

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

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

Description uses 3.3% 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 ≈261 characters, or 3.3%.

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 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. Use Read, Glob, and Grep to locate interface control documents, data-flow diagrams, retention decisions, and threat models.
  3. Draw data and control flows with classification, system of record, trust boundary, authorization, retention, and failure owner on each edge.
  4. Model consent, wrong-patient prevention, clinician review, downtime, rollback, and protected support evidence as first-class paths.
  5. Use WebFetch only for current official Abridge product context and label all tenant-specific facts by source revision.
  6. Use Write or Edit to update the architecture record and unresolved evidence register.

Approval Boundaries

Do not label an inferred interface, FHIR resource, webhook, hosting model, or retention period as implemented without authoritative evidence.

Output

Return component map, flows, trust boundaries, data classes, systems of record, owners, failure paths, evidence revisions, and open assumptions. Separate verified facts, tenant-specific evidence, assumptions, and actions still awaiting approval.

Error Handling

Condition Response
Edge lacks an owner Keep the design unapproved.
PHI crosses an undocumented boundary Stop and escalate to privacy and security review.
Diagram conflicts with tenant evidence Update the diagram and record the superseded assumption.

Example

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

settings=outpatient+ed; ehr=epic; boundaries=7; undocumented-edges=2; phi-flows=owner-reviewed; status=design-review

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

    The skill provides a comprehensive reference architecture for clinical AI integration within healthcare environments. It includes design patterns for HIPAA-compliant data flow, EHR integration, and security controls. A low-risk finding was identified regarding indirect prompt injection due to the skill's primary function of processing external clinical transcripts.

  • 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-settings] [ehr-landscape]
version
1.5.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "abridge",
  "architecture",
  "ehr",
  "governance"
]
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-reference-architecture