healthcare-emr-patterns

Implements EMR/EHR development patterns for clinical workflows, medication safety, and healthcare UI design.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill healthcare-emr-patterns-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: healthcare-emr-patterns
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/healthcare-emr-patterns
Command: npx skills add https://github.com/ibytechaos/claude --skill healthcare-emr-patterns-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building Electronic Medical Record (EMR) and Electronic Health Record (EHR) systems requires strict patient-safety rules, clinical workflow knowledge, and accessibility standards that general-purpose development guidance does not cover. This Skill provides concrete patterns for encounter workflows, prescription safety, and clinical data display. ## Core Features & Use Cases - Single-Page Encounter Flow: Structures clinical encounters vertically from chief complaint through diagnosis, medications, and sign-off, with a sticky patient header showing allergies and active medications. - Medication Safety Pattern: Enforces drug interaction checking, allergy validation, and dose verification, blocking critical interactions unless the clinician documents an override reason in the audit trail. - Locked Encounter & Addendum Pattern: Prevents edits to signed encounters, allowing only linked addendum records with full audit trails. - Use Case: A developer building a hospital EMR module uses these patterns to implement a chest-pain encounter template where red-flag symptoms trigger non-dismissable alerts, NEWS2 scores auto-calculate from vitals, and a Warfarin-Aspirin critical interaction blocks prescribing until an override reason is recorded. ## Quick Start Use the healthcare-emr-patterns skill to design a patient encounter workflow with drug interaction checking and locked signed encounters.

Frequently Asked Questions about healthcare-emr-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a patient encounter workflow for an EMR system?

Structure the encounter as a single vertical page flowing from chief complaint through history, examination, vitals, diagnosis, medications, investigations, and sign-off. Keep a sticky patient header visible with demographics, allergies, and active medications, and avoid tab-based layouts that fragment the clinical workflow.

How should drug interaction checking work in e-prescribing software?

Check the selected drug against current medications, encounter medications, and patient allergies, then validate dose against weight, age, and renal function. Critical interactions must block prescribing entirely until the clinician documents an override reason, which is stored in the audit trail.

Can signed clinical encounters be edited in an EHR system?

No, signed encounters must be locked against edits. Corrections are made only through an addendum, a separate linked record, and both the original and addendum appear in the patient timeline with full audit trail capture of who signed and when.

What accessibility requirements apply to healthcare data entry UIs?

Healthcare UIs require 4.5:1 minimum contrast, 44x44px touch targets, full keyboard navigation, screen reader labels on all form fields, and no color-only indicators. Clinical alerts must never use auto-dismissing toasts and require active clinician acknowledgment.

What are common anti-patterns in EMR development?

Anti-patterns include storing clinical data in browser localStorage, silent failures in drug interaction checking, dismissable toasts for critical alerts, tab-based encounter UIs, allowing edits to signed encounters, and using untyped structures for clinical data.