hipaa-compliance

Enforce HIPAA-specific decision gates for PHI handling in healthcare workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HIPAA-compliance provides a HIPAA-aware overlay to enforce PHI handling, auditing, and minimum-necessary access in healthcare software, enabling regulatory alignment while simplifying integration with broader privacy controls.

Core Features & Use Cases

  • Serves as the canonical entrypoint for HIPAA-focused tasks, coordinating with concrete implementations like healthcare-phi-compliance, healthcare-reviewer, and security-review.
  • Enforces robust guardrails around PHI movement, logging, data storage, and prompt boundaries, with escalation for regulated workflows.
  • Use case: when building patient-facing or clinician-facing systems where PHI handling and auditability matter.

Quick Start

Activate hipaa-compliance to apply HIPAA-specific checks and route PHI review to the healthcare-phi-compliance path.

Frequently Asked Questions about hipaa-compliance

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

FAQPage Schema
How do I enforce HIPAA compliance for PHI handling in healthcare software workflows?

HIPAA compliance for PHI handling is enforced by applying decision gates that constrain data movement, logging, and storage. This overlay ensures authenticated access, minimum necessary data usage, and auditable events across regulated healthcare software workflows.

What guardrails are needed for minimum necessary data access in healthcare applications?

Guardrails for minimum necessary data access require authenticated entry points, auditable event logging, and secure data handling boundaries. These constraints prevent unauthorized PHI exposure and escalate regulated data flows to specialized reviewers when patient safety is affected.

How do I start adding auditable events and PHI review to patient-facing systems?

Start adding auditable events by activating the HIPAA compliance overlay to apply specific checks. This routes PHI review tasks to the healthcare-phi-compliance path, applying guardrails for secure data handling and authenticated access across patient-facing systems.

Can I use this HIPAA guardrails overlay for clinician-facing systems where patient safety is affected?

Yes, this HIPAA guardrails overlay is designed for clinician-facing systems where patient safety is affected. It applies regulated data flow constraints and escalates sensitive PHI handling tasks to a healthcare-reviewer to maintain compliance.

When should I escalate a regulated data flow to a healthcare reviewer during PHI auditing?

Escalate a regulated data flow to a healthcare reviewer when patient safety or regulated data boundaries are impacted. This escalation is triggered automatically by HIPAA-specific decision gates evaluating auditable events and minimum necessary access constraints.