Agent skill · product strategy · affaan-m
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.
Why this skill is useful
Provides domain-specific patterns for EMR/EHR development that enhance clinical safety and efficiency, which the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
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: Smart Template System Red flags in any template must trigger a visible, non-dismissable alert — NOT a toast notification. Medication Safety Pattern 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/healthcare-emr-patterns--c40fdb