affaan-m avatar

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-code

Installs 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
1affaan-m avatarhomelab-network-setupaffaan-m/eccPractical home and homelab network planning for gateways, switches, access points, IP ranges, DHCP reservations, DNS, cabling, and common beginner mistakes.5.5Kskills.sh installs
2affaan-m avatarclaude-devfleetaffaan-m/eccOrchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured 5.4Kskills.sh installs
3affaan-m avatarhealthcare-cdss-patternsaffaan-m/eccClinical Decision Support System (CDSS) development patterns. Drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), alert severity classi5.4Kskills.sh installs
4julianoczkowski avatardesign-briefjulianoczkowski/designer-skillsCreate a design brief through an interactive interview, codebase exploration, and experience design decisions. Saved as a markdown file in the project. Use when5.4Kskills.sh installs
5thedotmack avatarpathfinderthedotmack/claude-memMap a codebase into feature-grouped flowcharts, identify duplicated concerns across features, and propose a unified architecture. Use when asked to "find the id5.4Kskills.sh installs
6affaan-m avatarcustomer-billing-opsaffaan-m/eccOperate customer billing workflows such as subscriptions, refunds, churn triage, billing-portal recovery, and plan analysis using connected billing tools like S5.4Kskills.sh installs