Skip to main content
Agent skill

Healthcare Emr Patterns

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.

Get started

Get the complete skill folder, including its scripts and reference files.

·

When to use this skill

Use Healthcare Emr Patterns when an AI agent needs a reusable SKILL.md workflow for this job: 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.

When not to use it

Skip Healthcare Emr Patterns when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/healthcare-emr-patterns
# Save SKILL.md to ~/.claude/skills/healthcare-emr-patterns/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/healthcare-emr-patterns/SKILL.md. For a shared project, commit the folder at .claude/skills/healthcare-emr-patterns/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Healthcare Emr Patterns skill for this task: Building patient encounter workflows (complaint, exam, diagnosis, prescription). Confirm any required inputs or files before making changes.

What supports this recommendation?

83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
92/100
Practical detail
92/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# 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 ```

Intended uses

  • 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

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.