healthcare-emr-patterns

Provide EMR/EHR development patterns for safe clinical encounter workflows.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/riftzen-bit/gemini-setup --skill healthcare-emr-patterns-riftzen-bit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: healthcare-emr-patterns
Source: https://github.com/riftzen-bit/gemini-setup/tree/main/skills/healthcare-emr-patterns
Command: npx skills add https://github.com/riftzen-bit/gemini-setup --skill healthcare-emr-patterns-riftzen-bit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides practical design patterns and guardrails to build EMR/EHR systems that prioritize patient safety, clinical accuracy, and efficient clinician workflows, reducing harmful errors and fragmented encounters.

Core Features & Use Cases

  • Patient Safety Enforcement: Non-dismissable red-flag alerts, medication interaction blocking with documented overrides, and critical-value escalation flows.
  • Single-Page Encounter UX: Vertical encounter flow with sticky patient header, structured templates, vitals with automated scoring, and locked-signed encounter addendum patterns.
  • Clinical Integration & Accessibility: CDSS integration points, lab result highlighting, audit trails for all changes, and WCAG-compliant UI requirements for clinical settings.
  • Use Case: Implement a chest pain encounter that auto-calculates NEWS2, blocks critical drug interactions, suggests ICD-10 codes, and locks the encounter after signing while allowing addenda.

Quick Start

Ask the skill to generate a single-page adult emergency chest pain encounter template including vitals, red-flag alerts, ICD-10 suggestions, medication interaction checks, and audit-trail requirements.

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 single-page EMR encounter workflow that prioritizes clinical safety?

Implement medication safety in EHR systems by enforcing medication interaction blocking with mandatory documented overrides. This pattern prevents critical drug errors by requiring clinicians to provide explicit justification before proceeding, while maintaining a complete audit trail of the override decision.

How does CDSS integration work within clinical encounter workflows?

EMR systems require comprehensive audit trails for all changes, locked-signed encounter addendum patterns, and critical-value escalation flows. Encounters are locked after signing while allowing formal addenda, and critical lab values trigger automated escalation flows to ensure responsible clinicians are notified immediately.

Can I build WCAG-compliant clinical UIs with strict input validation for healthcare applications?

Build WCAG-compliant clinical UIs with strict input validation requirements specifically designed for healthcare applications. The patterns enforce accessibility-first UI requirements for clinical settings, ensuring medical applications are usable by all clinicians while maintaining data integrity through validated inputs.

What is the best way to handle locked encounter signing and addenda in an EHR system?

Handle locked encounter signing and addenda in an EHR system by locking the encounter immediately after the clinician signs it. This prevents alteration of the legal medical record while permitting formal, audit-trailed addenda to be appended later if additional clinical information needs to be documented.