Healthcare Emr Patterns

1---2name: healthcare-emr-patterns3description: 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.4origin: Health1 Super Speciality Hospitals — contributed by Dr. Keyur Patel5version: "1.0.0"6---7 8# Healthcare EMR Development Patterns9 10Patterns for building Electronic Medical Record (EMR) and Electronic Health Record (EHR) systems. Prioritizes patient safety, clinical accuracy, and practitioner efficiency.11 12## When to Use13 14- Building patient encounter workflows (complaint, exam, diagnosis, prescription)15- Implementing clinical note-taking (structured + free text + voice-to-text)16- Designing prescription/medication modules with drug interaction checking17- Integrating Clinical Decision Support Systems (CDSS)18- Building lab result displays with reference range highlighting19- Implementing audit trails for clinical data20- Designing healthcare-accessible UIs for clinical data entry21 22## How It Works23 24### Patient Safety First25 26Every design decision must be evaluated against: "Could this harm a patient?"27 28- Drug interactions MUST alert, not silently pass29- Abnormal lab values MUST be visually flagged30- Critical vitals MUST trigger escalation workflows31- No clinical data modification without audit trail32 33### Single-Page Encounter Flow34 35Clinical encounters should flow vertically on a single page — no tab switching:36 37```38Patient Header (sticky — always visible)39├── Demographics, allergies, active medications40│41Encounter Flow (vertical scroll)42├── 1. Chief Complaint (structured templates + free text)43├── 2. History of Present Illness44├── 3. Physical Examination (system-wise)45├── 4. Vitals (auto-trigger clinical scoring)46├── 5. Diagnosis (ICD-10/SNOMED search)47├── 6. Medications (drug DB + interaction check)48├── 7. Investigations (lab/radiology orders)49├── 8. Plan & Follow-up50└── 9. Sign / Lock / Print51```52 53### Smart Template System54 55```typescript56interface ClinicalTemplate {57  id: string;58  name: string;             // e.g., "Chest Pain"59  chips: string[];          // clickable symptom chips60  requiredFields: string[]; // mandatory data points61  redFlags: string[];       // triggers non-dismissable alert62  icdSuggestions: string[]; // pre-mapped diagnosis codes63}64```65 66Red flags in any template must trigger a visible, non-dismissable alert — NOT a toast notification.67 68### Medication Safety Pattern69 70```71User selects drug72  → Check current medications for interactions73  → Check encounter medications for interactions74  → Check patient allergies75  → Validate dose against weight/age/renal function76  → If CRITICAL interaction: BLOCK prescribing entirely77  → Clinician must document override reason to proceed past a block78  → If MAJOR interaction: display warning, require acknowledgment79  → Log all alerts and override reasons in audit trail80```81 82Critical 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.83 84### Locked Encounter Pattern85 86Once a clinical encounter is signed:87- No edits allowed — only an addendum (a separate linked record)88- Both original and addendum appear in the patient timeline89- Audit trail captures who signed, when, and any addendum records90 91### UI Patterns for Clinical Data92 93**Vitals Display:** Current values with normal range highlighting (green/yellow/red), trend arrows vs previous, clinical scoring auto-calculated (NEWS2, qSOFA), escalation guidance inline.94 95**Lab Results Display:** Normal range highlighting, previous value comparison, critical values with non-dismissable alert, collection/analysis timestamps, pending orders with expected turnaround.96 97**Prescription PDF:** One-click generation with patient demographics, allergies, diagnosis, drug details (generic + brand, dose, route, frequency, duration), clinician signature block.98 99### Accessibility for Healthcare100 101Healthcare UIs have stricter requirements than typical web apps:102- 4.5:1 minimum contrast (WCAG AA) — clinicians work in varied lighting103- Large touch targets (44x44px minimum) — for gloved/rushed interaction104- Keyboard navigation — for power users entering data rapidly105- No color-only indicators — always pair color with text/icon (colorblind clinicians)106- Screen reader labels on all form fields107- No auto-dismissing toasts for clinical alerts — clinician must actively acknowledge108 109### Anti-Patterns110 111- Storing clinical data in browser localStorage112- Silent failures in drug interaction checking113- Dismissable toasts for critical clinical alerts114- Tab-based encounter UIs that fragment the clinical workflow115- Allowing edits to signed/locked encounters116- Displaying clinical data without audit trail117- Using `any` type for clinical data structures118 119## Examples120 121### Example 1: Patient Encounter Flow122 123```124Doctor opens encounter for Patient #4521125  → Sticky header shows: "Rajesh M, 58M, Allergies: Penicillin, Active Meds: Metformin 500mg"126  → Chief Complaint: selects "Chest Pain" template127    → Clicks chips: "substernal", "radiating to left arm", "crushing"128    → Red flag "crushing substernal chest pain" triggers non-dismissable alert129  → Examination: CVS system — "S1 S2 normal, no murmur"130  → Vitals: HR 110, BP 90/60, SpO2 94%131    → NEWS2 auto-calculates: score 8, risk HIGH, escalation alert shown132  → Diagnosis: searches "ACS" → selects ICD-10 I21.9133  → Medications: selects Aspirin 300mg134    → CDSS checks against Metformin: no interaction135  → Signs encounter → locked, addendum-only from this point136```137 138### Example 2: Medication Safety Workflow139 140```141Doctor prescribes Warfarin for Patient #4521142  → CDSS detects: Warfarin + Aspirin = CRITICAL interaction143  → UI: red non-dismissable modal blocks prescribing144  → Doctor clicks "Override with reason"145  → Types: "Benefits outweigh risks — monitored INR protocol"146  → Override reason + alert stored in audit trail147  → Prescription proceeds with documented override148```149 150### Example 3: Locked Encounter + Addendum151 152```153Encounter #E-2024-0891 signed by Dr. Shah at 14:30154  → All fields locked — no edit buttons visible155  → "Add Addendum" button available156  → Dr. Shah clicks addendum, adds: "Lab results received — Troponin elevated"157  → New record E-2024-0891-A1 linked to original158  → Timeline shows both: original encounter + addendum with timestamps159```