Healthcare EMR Patterns
Build EMR/EHR with Muse the safe way: patient-safety-first encounter flows, medication safety with interaction blocking, locked encounters, and clinical UI accessibility.
- What
- Build EMR/EHR with Muse the safe way: patient-safety-first encounter flows, medication safety with interaction blocking, locked encounters, and clinical UI accessibility.
- Cost
- Free
- Needs
- none to install. Pure guidance; a healthcare app project helps.
- Level
- Beginner
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: development patterns for electronic medical records that put patient safety ahead of everything, contributed by Dr. Keyur Patel (Health1 Super Speciality Hospitals). Every design decision is evaluated against one question: could this harm a patient. The encounter flow runs vertically on a single page with a sticky patient header showing allergies and active medications, from chief complaint through history, examination, vitals with auto-calculated clinical scores, diagnosis with ICD-10 and SNOMED search, medications with drug interaction checking, investigations, and plan to sign and lock. The medication safety pattern blocks prescribing on critical interactions by default, requiring a documented override reason stored in the audit trail, while major interactions need active acknowledgment. Red flags trigger non-dismissable alerts, never toasts. Once signed, an encounter locks completely and only an addendum, a separate linked record, can add information. Clinical UI patterns cover vitals display with range highlighting and trend arrows, lab results with critical value alerts, one-click prescription PDFs, and stricter accessibility than typical web apps: 4.5:1 contrast, large touch targets for gloved hands, no color-only indicators, no auto-dismissing toasts for clinical alerts. By @affaan-m, listed here with credit to its creator and contributor. From the affaan-m/ECC repository (MIT). Honest caveats: patterns do not make an app compliant or clinically safe by themselves, a real clinical review is required; never put real patient data in a chat while using it; this is development guidance, not medical advice. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Healthcare EMR Patterns is a free Muse skill with development patterns for electronic medical records that put patient safety ahead of everything, contributed by Dr. Keyur Patel. Every design decision is evaluated against one question: could this harm a patient. The encounter flow runs vertically on a single page, with medication safety, interaction blocking, locked encounters, and clinical accessibility.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "Healthcare EMR Patterns" with your Muse. Prerequisites: none to install. Pure guidance; a healthcare app project helps. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/healthcare-emr-patterns/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Review this encounter workflow against the patient-safety patterns: [paste code or mockup]." 3. Ask follow-ups like "where could a critical drug interaction pass silently here?" or "design the locked-encounter addendum flow for this module." Tip: never use real patient data in the chat; use synthetic fixtures. Safety: a skill is plain-text instructions; it runs nothing by itself. This is development guidance, not medical advice. A real clinical review is required before any deployment.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.