Skip to main content
skill CX Codex

healthcare-emr-patterns — Claude Code skill: what it does

healthcare-emr-patterns is a Claude Code skill that defines EMR and EHR development patterns focused on patient safety, encounter workflows, and medication checks.

MIT 6,200 installs ★ 308,413 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add affaan-m/ECC --skill healthcare-emr-patterns -a claude-code
Open on GitHub

What healthcare-emr-patterns does

The skill sets structural patterns for electronic health record systems where drug interactions block prescribing until clinician override is documented. Vertical encounter layouts avoid tab switching and keep patient vitals, diagnosis, and prescriptions in a single scrollable view.

Signed encounters lock against edits and require linked addendums for subsequent data. User interfaces enforce strict contrast, large touch targets, and non-dismissable clinical alerts without toast notifications.

What it helps with

  • build single-page medical encounter workflows
  • implement medication safety checks with prescription blocking
  • create audit trails for clinical data modifications
  • design accessible medical data entry interfaces

Example prompts for the agent

  • Design an encounter workflow using healthcare-emr-patterns
  • Add medication interaction checking with blocking logic
  • Implement locked encounter addendums

How to install healthcare-emr-patterns

1Skills CLI (Vercel)

npx skills add affaan-m/ECC --skill healthcare-emr-patterns -a claude-code

2Manually: put the files in place

~/.claude/skills/healthcare-emr-patterns/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/healthcare-emr-patterns/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about healthcare-emr-patterns

How to install healthcare-emr-patterns in Claude Code?

Run npx skills add affaan-m/ECC --skill healthcare-emr-patterns -a claude-code and use ~/.claude/skills/healthcare-emr-patterns/SKILL.md.

What does healthcare-emr-patterns do?

It provides EMR and EHR architectural patterns covering clinical safety, medication checks, audit trails, and accessible UI design.

What UI requirements does the skill enforce for medical data?

It requires 4.5:1 contrast, 44x44px touch targets, keyboard navigation, and persistent alerts instead of auto-dismissing toasts.

Source text

SKILL.md · MIT
---
name: healthcare-emr-patterns
description: EMR/EHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry. Use when building EMR or EHR features such as encounter workflows, prescription generation, or clinical data entry UI.
metadata:
  version: "1.0.0"
  origin: Health1 Super Speciality Hospitals — contributed by Dr. Keyur Patel
---

# Healthcare EMR Development Patterns

Patterns for building Electronic Medical Record (EMR) and Electronic Health Record (EHR) systems. Prioritizes patient safety, clinical accuracy, and practitioner efficiency.

## When to Use

- Building patient encounter workflows (complaint, exam, diagnosis, prescription)
- Implementing clinical note-taking (structured + free text + voice-to-text)
- Designing prescription/medication modules with drug interaction checking
- Integrating Clinical Decision Support Systems (CDSS)
- Building lab result displays with reference range highlighting
- Implementing audit trails for clinical data
- Designing healthcare-accessible UIs for clinical data entry

## How It Works

### Patient Safety First

Every design decision must be evaluated against: "Could this harm a patient?"

- Drug interactions MUST alert, not silently pass
- Abnormal lab values MUST be visually flagged
- Critical vitals MUST trigger escalation workflows
- No clinical data modification without audit trail

### Single-Page Encounter Flow

Clinical encounters should flow vertically on a single page — no tab switching:

```
Patient Header (sticky — always visible)
├── Demographics, allergies, active medications
│
Encounter Flow (vertical scroll)
├── 1. Chief Complaint (structured templates + free text)
├── 2. History of Present Illness
├── 3. Physical Examination (system-wise)
├── 4. Vitals (auto-trigger clinical scoring)
├── 5. Diagnosis (ICD-10/SNOMED search)
├── 6. Medications (drug DB + interaction check)
├── 7. Investigations (lab/radiology orders)
├── 8. Plan & Follow-up
└── 9. Sign / Lock / Print
```

### Smart Template System

```typescript
interface ClinicalTemplate {
  id: string;
  name: string;             // e.g., "Chest Pain"
  chips: string[];          // clickable symptom chips
  requiredFields: string[]; // mandatory data points
  redFlags: string[];       // triggers non-dismissable alert
  icdSuggestions: string[]; // pre-mapped diagnosis codes
}
```

Red flags in any template must trigger a visible, non-dismissable alert — NOT a toast notification.

### Medication Safety Pattern

```
User selects drug
  → Check current medications for interactions
  → Check encounter medications for interactions
  → Check patient allergies
  → Validate dose against weight/age/renal function
  → If CRITICAL interaction: BLOCK prescribing entirely
  → Clinician must document override reason to proceed past a block
  → If MAJOR interaction: display warning, require acknowledgment
  → Log all alerts and override reasons in audit trail
```

Critical interactions **block prescribing by default**. The clinician must explicitly override with a documented reason stored in the audit trail. The system never silently allows a critical interaction.

### Locked Encounter Pattern

Once a clinical encounter is signed:
- No edits allowed — only an addendum (a separate linked record)
- Both original and addendum appear in the patient timeline
- Audit trail captures who signed, when, and any addendum records

### UI Patterns for Clinical Data

**Vitals Display:** Current values with normal range highlighting (green/yellow/red), trend arrows vs previous, clinical scoring auto-calculated (NEWS2, qSOFA), escalation guidance inline.

**Lab Results Display:** Normal range highlighting, previous value comparison, critical values with non-dismissable alert, collection/analysis timestamps, pending orders with expected turnaround.

**Prescription PDF:** One-click generation with patient demographics, allergies, diagnosis, drug details (generic + brand, dose, route, frequency, duration), clinician signature block.

### Accessibility for Healthcare

Healthcare UIs have stricter requirements than typical web apps:
- 4.5:1 minimum contrast (WCAG AA) — clinicians work in varied lighting
- Large touch targets (44x44px minimum) — for gloved/rushed interaction
- Keyboard navigation — for power users entering data rapidly
- No color-only indicators — always pair color with text/icon (colorblind clinicians)
- Screen reader labels on all form fields
- No auto-dismissing toasts for clinical alerts — clinician must actively acknowledge

### Anti-Patterns

- Storing clinical data in browser localStorage
- Silent failures in drug interaction checking
- Dismissable toasts for critical clinical alerts
- Tab-based encounter UIs that fragment the clinical workflow
- Allowing edits to signed/locked encounters
- Displaying clinical data without audit trail
- Using `any` type for clinical data structures

## Examples

### Example 1: Patient Encounter Flow

```
Doctor opens encounter for Patient #4521
  → Sticky header shows: "Rajesh M, 58M, Allergies: Penicillin, Active Meds: Metformin 500mg"
  → Chief Complaint: selects "Chest Pain" template
    → Clicks chips: "substernal", "radiating to left arm", "crushing"
    → Red flag "crushing substernal chest pain" triggers non-dismissable alert
  → Examination: CVS system — "S1 S2 normal, no murmur"
  → Vitals: HR 110, BP 90/60, SpO2 94%
    → NEWS2 auto-calculates: score 8, risk HIGH, escalation alert shown
  → Diagnosis: searches "ACS" → selects ICD-10 I21.9
  → Medications: selects Aspirin 300mg
    → CDSS checks against Metformin: no interaction
  → Signs encounter → locked, addendum-only from this point
```

### Example 2: Medication Safety Workflow

```
Doctor prescribes Warfarin for Patient #4521
  → CDSS detects: Warfarin + Aspirin = CRITICAL interaction
  → UI: red non-dismissable modal blocks prescribing
  → Doctor clicks "Override with reason"
  → Types: "Benefits outweigh risks — monitored INR protocol"
  → Override reason + alert stored in audit trail
  → Prescription proceeds with documented override
```

### Example 3: Locked Encounter + Addendum

```
Encounter #E-2024-0891 signed by Dr. Shah at 14:30
  → All fields locked — no edit buttons visible
  → "Add Addendum" button available
  → Dr. Shah clicks addendum, adds: "Lab results received — Troponin elevated"
  → New record E-2024-0891-A1 linked to original
  → Timeline shows both: original encounter + addendum with timestamps
```

© affaan-m · MIT · affaan-m/ECC

Similar skills

All skills for Security →

From the same set150

The whole set →
hipaa-compliance The skill runs in Claude Code and other platforms, handling HIPAA compliance tasks and PHI security workflows in software. CX Codex +1 6,200installs regex-vs-llm-structured-text The regex-vs-llm-structured-text Claude Code skill helps choose an extraction method for structured text. It starts with regex for repeated patterns and sends uncertain results to an LLM for review. CX Codex +1 6,200installs click-path-audit click-path-audit — a skill for Claude Code and Codex that audits user-facing touchpoints. Traces sequential state mutations to uncover silent side effects and conflicting resets across UI handlers. CX Codex +1 6,200installs homelab-wireguard-vpn The homelab-wireguard-vpn Claude Code skill guides WireGuard setup for remote access to a home network. It covers server and client configuration, key generation, and the choice between split and full tunnel routing. CX Codex +1 6,200installs skill-comply skill-comply is a Claude Code skill that tests whether agents follow skills, rules, and agent definitions. Run it after changing an instruction file or as part of recurring compliance checks. CX Codex +1 6,200installs terminal-ops terminal-ops — a repo execution skill: runs commands, reads git state, debugs CI failures and makes narrow fixes with proof of what was actually verified. CX Codex +1 6,200installs clickhouse-io clickhouse-io guides AI agents on ClickHouse table engines, query tuning, and batch ingestion patterns for analytical workloads. CX Codex +1 6,200installs nutrient-document-processing nutrient-document-processing is a Claude Code skill that processes files through the Nutrient DWS API. It handles conversions, OCR, data extraction, redaction, signatures, and PDF forms. CX Codex +1 6,200installs

Project sponsors

Companies that keep this analytics open