healthcare-phi-compliance

Implement row-level security and audit logging to protect PHI in healthcare systems.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides actionable patterns and guardrails to prevent unauthorized exposure of Protected Health Information (PHI) and Personally Identifiable Information (PII) in healthcare applications, reducing legal risk and data breaches while enabling safe access for authorized clinicians.

Core Features & Use Cases

  • PHI/PII Classification & Schema Tagging: Guidance for marking sensitive columns and treating identifiers as PHI versus PII for operational handling and compliance.
  • Access Control & Row-Level Security: Patterns to implement RLS policies and multi-facility isolation so staff only see permitted patient records.
  • Audit Trails, Secure Logging & Deployment Checklist: Definitions for tamper-resistant audit entries, safe logging practices, and a pre-deployment checklist to remove PHI from errors, URLs, and client code.
  • Real-world Example: Use RLS to ensure a doctor at Facility A cannot query Facility B patients and log every read with an opaque internal record ID.

Quick Start

Use the healthcare-phi-compliance guidance to create an RLS policy, an insert-only audit schema, and a pre-deployment checklist that prevents PHI leaks.

Frequently Asked Questions about healthcare-phi-compliance

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

FAQPage Schema
Does this PHI compliance guidance work for securing healthcare APIs and multi-facility deployments?

Yes, this PHI compliance guidance applies to securing healthcare APIs and multi-facility deployments. It provides patterns for RLS enforcement, audit logging, and secure error handling across EHRs and distributed systems.

How do I create a tamper-proof audit trail for PHI access in an EHR system?

A tamper-proof audit trail for PHI access uses an insert-only audit schema to log every read operation with an opaque internal record ID. This ensures historical access entries cannot be modified or deleted.

What is the difference between PHI and PII classification for healthcare data schema tagging?

PHI and PII classification distinguishes health-related identifiers from general personally identifiable information for operational handling. Schema tagging marks sensitive columns to apply appropriate regulatory compliance controls.

How do I prevent PHI leaks in application logs and error messages before deployment?

Preventing PHI leaks in logs and error messages requires a pre-deployment checklist that removes sensitive patient data from errors, URLs, and client code. This ensures secure logging practices aligned with HIPAA and GDPR.

Does this PHI compliance guidance work for securing healthcare APIs and multi-facility deployments?

Yes, this PHI compliance guidance applies to securing healthcare APIs and multi-facility deployments. It provides patterns for RLS enforcement, audit logging, and secure error handling across EHRs and distributed systems.