
Healthcare Emr Patterns
Built by Dr. Keyur Patel at Health1 Super Speciality Hospitals, this gives you proven patterns for EMR/EHR systems where patient safety isn't negotiable. It covers single-page encounter flows, medication safety with blocking critical interactions (not just warnings), locked encounter patterns with addendum-only editing, and accessibility requirements specific to clinical environments. The core insight is treating every design decision through a "could this harm a patient" lens, which means non-dismissable alerts for red flags, mandatory audit trails, and visual flagging of abnormal values. If you're building clinical software and need to understand why healthcare UIs behave differently than typical web apps, this explains the reasoning behind those constraints.
- skills.sh installs
- 5.5K
- GitHub stars
- 300.3K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add affaan-m/ecc --skill healthcare-emr-patterns --agent claude-codeInstalls into .claude/skills of the current project.
Files
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:
Sponsors
Details
- Repository
- github.com/affaan-m/ecc
- Categories
- Productivity & Planning, Design & UI/UX
- First seen
- Jul 14, 2026
More from affaan-m/ecc
All 263- Homelab Network Setup5.5K
- Ios Icon Gen5.5K
- Kotlin Ktor Patterns5.5K
- Api Connector Builder5.5K
- Safety Guard5.5K
- Csharp Testing5.5K
- Skill Scout5.5K
- Customs Trade Compliance5.5K
- Research Ops5.5K
- Crosspost5.5K
- Videodb5.5K
- Click Path Audit5.5K
- Skill Comply5.5K
- Hipaa Compliance5.5K
- Angular Developer5.5K
- Regex Vs Llm Structured Text5.5K
- Investor Outreach5.5K
- Homelab Wireguard Vpn5.5K
- Repo Scan5.5K
- Agent Payment X4025.5K
- Ck5.5K
- Clickhouse Io5.5K
- Terminal Ops5.4K
- Knowledge Ops5.4K