What problem does it solve? Building Electronic Medical Record systems requires strict patient-safety rules, clinical workflow knowledge, and accessibility standards that typical web development guidance does not cover. This Skill provides concrete patterns for encounter workflows, medication safety, and clinical UI design so developers avoid dangerous mistakes like silent drug-interaction failures or editable signed records. ## Core Features & Use Cases - Single-Page Encounter Workflow: Structures the full clinical encounter (complaint, exam, vitals, diagnosis, medications, sign-off) as a vertical flow with a sticky patient header and smart templates with red-flag alerts. - Medication Safety & CDSS Integration: Defines interaction checking against current medications and allergies, dose validation, blocking of critical interactions, and documented clinician overrides stored in an audit trail. - Locked Encounter & Audit Patterns: Enforces addendum-only edits after signing, with full audit trails for clinical data access and modification. - Use Case: A developer building a hospital outpatient module uses these patterns to implement a chest-pain encounter template that auto-calculates NEWS2 scores from vitals, blocks a Warfarin-Aspirin critical interaction until an override reason is documented, and locks the record after signing. ## Quick Start Use the healthcare-emr-patterns skill to design a patient encounter workflow with drug interaction checking and locked signed records.
