healthcare-eval-harness

Execute five-category patient safety tests and block deployments on CRITICAL failures.

86|21|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill healthcare-eval-harness-jamkris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: healthcare-eval-harness
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/healthcare-eval-harness
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill healthcare-eval-harness-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates patient safety evaluation for healthcare deployments by enforcing deployment gates and blocking releases on any CRITICAL failure.

Core Features & Use Cases

  • Five-category evaluation covering CDSS accuracy, PHI exposure, data integrity, clinical workflow, and integration, with CRITICAL gates requiring 100% pass and HIGH gates requiring 95%+.
  • Framework-agnostic guidance with Jest as the reference runner, including result aggregation and gate enforcement across CI/CD pipelines.
  • Use Case: Before EMR/EHR rollouts or after changes to CDSS logic to prevent unsafe deployments.

Quick Start

Run the evaluation harness in your CI/CD workflow to validate safety gates prior to deployment.

Frequently Asked Questions about healthcare-eval-harness

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

FAQPage Schema
How do I block unsafe CDSS logic changes from deploying in CI/CD?▼

Block unsafe CDSS deployments by integrating a patient safety evaluation harness into CI/CD pipelines that enforces 100% pass on CRITICAL gates and halts releases on any failure. It applies deterministic gating with bail-on-first-failure semantics.

What categories should patient safety testing cover for EMR and EHR rollouts?▼

Patient safety testing for EMR and EHR rollouts should cover five categories: CDSS accuracy, PHI exposure, data integrity, clinical workflow, and integration. CRITICAL gates require 100% pass while HIGH gates require 95% or higher.

Can I run healthcare deployment gates with test runners other than Jest?▼

Healthcare deployment gates are framework-agnostic and use Jest as the reference runner. You need a test runner and scripting for result aggregation to enforce threshold rules and gate semantics across your CI/CD pipeline.

What's the best way to automate compliance testing for clinical authentication controls?▼

Automate compliance testing for clinical authentication controls by running a five-category evaluation harness in CI/CD that applies deterministic gating and threshold enforcement. This blocks deployments on any CRITICAL failure across clinical workflow and integration gates.

When do I need to enforce critical deployment gates versus high-severity gates?▼

Enforce CRITICAL deployment gates with 100% pass requirements for any changes impacting CDSS accuracy, PHI exposure, or data integrity. HIGH gates require 95% or higher pass rates and apply to clinical workflow and integration evaluations.

Why does my healthcare deployment pipeline fail on the first critical test error?▼

Healthcare deployment pipelines fail on the first critical test error due to bail-on-first-failure semantics. This deterministic gating strategy enforces patient safety by immediately blocking releases when any CRITICAL gate fails, preventing unsafe deployments.