abridge-reference-architecture
Implement Abridge reference architecture for clinical AI integration. Use when designing a new Abridge deployment, reviewing project structure, or planning multi-site health system rollouts with EHR integration. Trigger: "abridge architecture", "abridge project structure", "abridge system design", "abridge multi-site".
Best use case
abridge-reference-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement Abridge reference architecture for clinical AI integration. Use when designing a new Abridge deployment, reviewing project structure, or planning multi-site health system rollouts with EHR integration. Trigger: "abridge architecture", "abridge project structure", "abridge system design", "abridge multi-site".
Teams using abridge-reference-architecture should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/abridge-reference-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How abridge-reference-architecture Compares
| Feature / Agent | abridge-reference-architecture | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Implement Abridge reference architecture for clinical AI integration. Use when designing a new Abridge deployment, reviewing project structure, or planning multi-site health system rollouts with EHR integration. Trigger: "abridge architecture", "abridge project structure", "abridge system design", "abridge multi-site".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Abridge Reference Architecture
## Overview
Reference architecture for Abridge clinical AI integration in a multi-site health system. Covers data flow, component design, EHR integration patterns, and HIPAA-compliant infrastructure.
## System Architecture
```
Health System Network
┌──────────────────────────────────────────────────────┐
│ │
│ ┌─────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Provider │───▶│ Abridge App │───▶│ Integration │ │
│ │ Device │ │ (Ambient AI) │ │ Service │ │
│ │ (mobile/ │ │ │ │ (your code) │ │
│ │ desktop) │ └──────┬───────┘ └──────┬───────┘ │
│ └─────────┘ │ │ │
│ │ │ │
│ ┌─────────▼─────────┐ │ │
│ │ Abridge Cloud API │ │ │
│ │ (Partner API) │ │ │
│ │ - Session mgmt │ │ │
│ │ - Note generation │ │ │
│ │ - Patient summary │ │ │
│ └─────────┬─────────┘ │ │
│ │ │ │
│ ┌─────────▼─────────┐ ┌──────▼───────┐ │
│ │ Webhook Events │ │ EHR System │ │
│ │ - Note completed │──│ (Epic/Athena)│ │
│ │ - Quality alerts │ │ FHIR R4 API │ │
│ └───────────────────┘ └──────────────┘ │
│ │
└──────────────────────────────────────────────────────┘
```
## Project Structure
```
abridge-integration/
├── src/
│ ├── config/
│ │ ├── abridge.ts # Abridge API configuration
│ │ ├── ehr.ts # EHR/FHIR endpoint config
│ │ └── index.ts # Environment-based config loader
│ ├── abridge/
│ │ ├── client.ts # API client singleton
│ │ ├── errors.ts # HIPAA-safe error handling
│ │ ├── retry.ts # Retry with backoff
│ │ └── session-manager.ts # Encounter session lifecycle
│ ├── ehr/
│ │ ├── fhir-client.ts # FHIR R4 API wrapper
│ │ ├── epic-adapter.ts # Epic-specific mappings
│ │ ├── athena-adapter.ts # Athena-specific mappings
│ │ └── note-pusher.ts # DocumentReference creation
│ ├── webhooks/
│ │ ├── handler.ts # Express webhook endpoint
│ │ ├── signature.ts # HMAC signature verification
│ │ ├── event-router.ts # Event type → handler mapping
│ │ └── idempotency.ts # Duplicate event prevention
│ ├── security/
│ │ ├── audit-logger.ts # HIPAA audit trail
│ │ ├── phi-redactor.ts # PHI detection and redaction
│ │ ├── rbac.ts # Role-based access control
│ │ └── tls-config.ts # TLS 1.3 enforcement
│ ├── monitoring/
│ │ ├── health.ts # Health check endpoint
│ │ ├── metrics.ts # Performance metrics collector
│ │ └── alerts.ts # Quality and latency alerts
│ └── server.ts # Express server entry point
├── tests/
│ ├── unit/ # Unit tests (no API calls)
│ ├── integration/ # Sandbox API tests
│ └── fhir-validation/ # FHIR resource schema tests
├── fixtures/
│ └── transcripts/ # Synthetic encounter transcripts
├── scripts/
│ ├── deploy-cloud-run.sh # GCP Cloud Run deployment
│ ├── readiness-check.ts # Production readiness validation
│ └── diagnostic.sh # Debug data collection
├── Dockerfile # HIPAA-compliant container
├── .env.example # Environment template (no secrets)
└── package.json
```
## Key Design Decisions
| Decision | Choice | Rationale |
|----------|--------|-----------|
| Language | TypeScript | Type safety for healthcare data |
| EHR adapter | Strategy pattern | Swap EHR backends without changing core |
| Error handling | Custom error class | HIPAA-safe: never log PHI |
| Authentication | SMART on FHIR | Standard for healthcare OAuth |
| Deployment | Cloud Run | HIPAA BAA, auto-scaling, managed |
| Secrets | GCP Secret Manager | HIPAA-compliant, audited access |
| Monitoring | Custom health endpoint | Abridge + FHIR connectivity checks |
## Data Flow
```
1. Provider opens encounter on device
2. Abridge app captures ambient audio
3. Audio streams to Abridge Cloud via WebSocket
4. Real-time transcript fragments returned
5. Provider closes encounter
6. Abridge generates structured clinical note (10-30s)
7. Webhook fires: encounter.session.completed
8. Integration service fetches note via API
9. Note pushed to EHR via FHIR DocumentReference
10. Patient summary generated and pushed to portal
11. Provider reviews, edits, and signs note in EHR
12. Webhook fires: encounter.note.signed
```
## Multi-Site Deployment
```typescript
// src/config/multi-site.ts
interface SiteConfig {
siteId: string;
siteName: string;
ehrType: 'epic' | 'athena' | 'cerner';
fhirBaseUrl: string;
abridgeOrgId: string;
specialties: string[];
providerCount: number;
goLiveDate: Date;
}
const sites: SiteConfig[] = [
{
siteId: 'main-campus',
siteName: 'Main Hospital',
ehrType: 'epic',
fhirBaseUrl: 'https://fhir.main-hospital.epic.com/interconnect-fhir-oauth',
abridgeOrgId: 'org_main_campus',
specialties: ['internal_medicine', 'cardiology', 'pulmonology'],
providerCount: 200,
goLiveDate: new Date('2026-06-01'),
},
{
siteId: 'community-clinic',
siteName: 'Community Clinic Network',
ehrType: 'athena',
fhirBaseUrl: 'https://api.athenahealth.com/fhir/r4',
abridgeOrgId: 'org_community',
specialties: ['family_medicine', 'pediatrics'],
providerCount: 50,
goLiveDate: new Date('2026-09-01'),
},
];
```
## Output
- Complete project structure for Abridge integration
- EHR adapter pattern supporting Epic, Athena, and Cerner
- Multi-site deployment configuration
- End-to-end data flow documentation
## Resources
- [Abridge Platform](https://www.abridge.com/product)
- [Abridge Clinician App](https://www.abridge.com/platform/clinicians)
- [FHIR R4 Specification](https://hl7.org/fhir/R4/)
- [Epic FHIR APIs](https://fhir.epic.com/)
- [GCP Healthcare API](https://cloud.google.com/healthcare-api)
## Next Steps
Start implementation with `abridge-install-auth`, then follow the skill sequence through production deployment.Related Skills
exa-reference-architecture
Implement Exa reference architecture for search pipelines, RAG, and content discovery. Use when designing new Exa integrations, reviewing project structure, or establishing architecture standards for neural search applications. Trigger with phrases like "exa architecture", "exa project structure", "exa RAG pipeline", "exa reference design", "exa search pipeline".
exa-architecture-variants
Choose and implement Exa architecture patterns at different scales: direct search, cached search, and RAG pipeline. Use when designing Exa integrations, choosing between simple search and full RAG, or planning architecture for different traffic volumes. Trigger with phrases like "exa architecture", "exa blueprint", "how to structure exa", "exa RAG design", "exa at scale".
evernote-reference-architecture
Reference architecture for Evernote integrations. Use when designing system architecture, planning integrations, or building scalable Evernote applications. Trigger with phrases like "evernote architecture", "design evernote system", "evernote integration pattern", "evernote scale".
elevenlabs-reference-architecture
Implement ElevenLabs reference architecture for production TTS/voice applications. Use when designing new ElevenLabs integrations, reviewing project structure, or building a scalable audio generation service. Trigger: "elevenlabs architecture", "elevenlabs project structure", "how to organize elevenlabs", "TTS service architecture", "elevenlabs design patterns", "voice API architecture".
documenso-reference-architecture
Implement Documenso reference architecture with best-practice project layout. Use when designing new Documenso integrations, reviewing project structure, or establishing architecture standards for document signing applications. Trigger with phrases like "documenso architecture", "documenso best practices", "documenso project structure", "how to organize documenso".
deepgram-reference-architecture
Implement Deepgram reference architecture for scalable transcription systems. Use when designing transcription pipelines, building production architectures, or planning Deepgram integration at scale. Trigger: "deepgram architecture", "transcription pipeline", "deepgram system design", "deepgram at scale", "enterprise deepgram", "deepgram queue".
databricks-reference-architecture
Implement Databricks reference architecture with best-practice project layout. Use when designing new Databricks projects, reviewing architecture, or establishing standards for Databricks applications. Trigger with phrases like "databricks architecture", "databricks best practices", "databricks project structure", "how to organize databricks", "databricks layout".
customerio-reference-architecture
Implement Customer.io enterprise reference architecture. Use when designing integration layers, event-driven architectures, or enterprise-grade Customer.io setups. Trigger: "customer.io architecture", "customer.io design", "customer.io enterprise", "customer.io integration pattern".
cursor-reference-architecture
Reference architecture for Cursor IDE projects: directory structure, rules organization, indexing strategy, and team configuration patterns. Triggers on "cursor architecture", "cursor project structure", "cursor best practices", "cursor file structure".
coreweave-reference-architecture
Reference architecture for CoreWeave GPU cloud deployments. Use when designing ML infrastructure, planning multi-model serving, or establishing CoreWeave deployment standards. Trigger with phrases like "coreweave architecture", "coreweave design", "coreweave infrastructure", "coreweave best practices".
configuration-reference-generator
Configuration Reference Generator - Auto-activating skill for Technical Documentation. Triggers on: configuration reference generator, configuration reference generator Part of the Technical Documentation skill category.
cohere-reference-architecture
Implement Cohere reference architecture with layered project layout for RAG and agents. Use when designing new Cohere integrations, reviewing project structure, or establishing architecture standards for Cohere API v2 applications. Trigger with phrases like "cohere architecture", "cohere project structure", "cohere layout", "organize cohere app", "cohere design pattern".