healthcare-emr-patterns

Define EMR/EHR development patterns for clinical workflows with safety alerts and audit logging.

Updated Sep 13, 2025
One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill healthcare-emr-patterns-llmh333
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: healthcare-emr-patterns
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/healthcare-emr-patterns
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill healthcare-emr-patterns-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Healthcare teams need consistent, safety-first design patterns for EMR/EHR workflows so clinical data entry, prescribing, and auditing don’t become error-prone or unsafe at scale.

Core Features & Use Cases

  • Single-page encounter flow that guides clinicians through a structured vertical progression from chief complaint to sign/lock/print.
  • Medication safety pattern with interaction checks, severity-based blocking/warnings, and documented overrides recorded to an audit trail.
  • Locked encounter + addendum model that prevents post-sign edits while still allowing clinically relevant updates via linked addenda.
  • Accessibility-first UI guidance including contrast targets, large touch targets, keyboard navigation, screen-reader labels, and non-dismissable alerts for critical safety events.

Quick Start

Ask the AI to produce an EMR encounter UI and backend workflow spec that applies the locked encounter, medication safety blocking/override, and non-dismissable clinical alert patterns for a single-page clinician experience.

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 EMR workflows that prevent clinical documentation errors?▼

EMR workflows prevent clinical documentation errors by enforcing a single-page vertical encounter flow from chief complaint to sign, locking encounters post-signature, and restricting updates to linked addenda only.

What's the best way to implement medication safety checks in an EHR system?▼

Medication safety checks in an EHR system require severity-based interaction blocking with non-dismissable critical alerts, plus documented override audit logging to ensure all clinical decisions are tracked.

How does a locked encounter model handle clinical corrections in healthcare software?▼

A locked encounter model handles clinical corrections by preventing all post-sign edits to the original record, instead requiring clinicians to append linked addenda for any necessary updates.

What accessibility standards should EMR user interfaces follow for clinical safety?▼

EMR user interfaces should follow accessibility standards including high contrast targets, large touch targets, full keyboard navigation, screen-reader labels, and non-dismissable alerts for critical safety events.

Can I use single-page workflow patterns for complex EHR encounter creation?▼

Single-page workflow patterns support complex EHR encounter creation by guiding clinicians through a structured vertical progression, ensuring structured data entry from chief complaint through final sign and lock.

Why do clinical safety alerts need to be non-dismissable in EMR systems?▼

Clinical safety alerts must be non-dismissable in EMR systems to prevent clinicians from bypassing critical medication interaction warnings, ensuring patient safety events are always addressed and override actions are audited.