Healthcare Phi Compliance

Contributed by Dr. Keyur Patel from Health1 Super Speciality Hospitals, this covers the practical patterns you need when building healthcare apps that handle patient data. It walks through PHI/PII classification, row-level security policies for multi-facility isolation, audit trail schemas, and the common leak vectors that'll get you in trouble: error messages, console logs, URL parameters, browser storage. Includes deployment checklists and concrete examples of safe versus unsafe error handling. Built for HIPAA, DISHA, and GDPR contexts. The RLS examples are Postgres-flavored but the principles apply broadly. Most useful when you're implementing access control or reviewing code for data exposure issues in clinical systems.

skills.sh installs: 4K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --skill healthcare-phi-compliance --agent claude-code

Installs into .claude/skills of the current project.

Files

Healthcare PHI/PII Compliance Patterns

Patterns for protecting patient data, clinician data, and financial data in healthcare applications. Applicable to HIPAA (US), DISHA (India), GDPR (EU), and general healthcare data protection.

When to Use

Building any feature that touches patient records
Implementing access control or authentication for clinical systems
Designing database schemas for healthcare data
Building APIs that return patient or clinician data
Implementing audit trails or logging
Reviewing code for data exposure vulnerabilities
Setting up Row-Level Security (RLS) for multi-tenant healthcare systems

How It Works

Healthcare data protection operates on three layers: classification (what is sensitive), access control (who can see it), and audit (who did see it).