Skip to main content
skill CX Codex

hipaa-compliance · affaan-m — Claude Code skill: HIPAA checks for PHI handling

The skill runs in Claude Code and other platforms, handling HIPAA compliance tasks and PHI security workflows in software.

MIT 6,200 installs ★ 308,413 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add affaan-m/ECC --skill hipaa-compliance -a claude-code
Open on GitHub

What hipaa-compliance does

The skill activates when tasks involve US healthcare compliance, PHI storage, or BAA covered entities. It sets up decision gates for handling protected health information and connects with healthcare-phi-compliance and healthcare-reviewer for deeper checks.

The workflow enforces minimum necessary access, strict audit logging, and payload isolation. Third-party SaaS and LLM endpoints remain blocked by default until BAA status and encryption boundaries are confirmed.

Identifiers such as MRNs and names are replaced with opaque internal IDs across prompts and error strings. Make sure the target platform CLI is available before adding the package to the project.

What it helps with

  • check clinic dashboard architecture for HIPAA exposure
  • audit logging and export paths for protected health information
  • validate vendor BAA status before sending text transcripts
  • enforce minimum necessary access controls for patient data

Example prompts for the agent

  • Review our clinician dashboard for HIPAA compliance and PHI leaks
  • Check if our external analytics stack is approved for PHI workloads
  • Audit prompt boundaries and logging for the new patient summary feature

How to install hipaa-compliance

1Skills CLI (Vercel)

npx skills add affaan-m/ECC --skill hipaa-compliance -a claude-code

2Manually: put the files in place

~/.claude/skills/hipaa-compliance/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/hipaa-compliance/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about hipaa-compliance

How to install hipaa-compliance in Claude Code?

Run npx skills add affaan-m/ECC --skill hipaa-compliance -a claude-code in your terminal and verify ~/.claude/skills/hipaa-compliance/SKILL.md.

What does hipaa-compliance do?

It acts as a compliance entrypoint for healthcare projects, guiding AI agents through PHI protection rules and BAA requirements.

Which related skills work with hipaa-compliance?

It delegates implementation details to healthcare-phi-compliance and architecture reviews to healthcare-reviewer.

Source text

SKILL.md · MIT
---
name: hipaa-compliance
description: HIPAA-specific entrypoint for healthcare privacy and security work. Use when a task is explicitly framed around HIPAA, PHI handling, covered entities, BAAs, breach posture, or US healthcare compliance requirements.
metadata:
  version: "1.0.0"
  origin: ECC direct-port adaptation
---

# HIPAA Compliance

Use this as the HIPAA-specific entrypoint when a task is clearly about US healthcare compliance. This skill intentionally stays thin and canonical:

- `healthcare-phi-compliance` remains the primary implementation skill for PHI/PII handling, data classification, audit logging, encryption, and leak prevention.
- `healthcare-reviewer` remains the specialized reviewer when code, architecture, or product behavior needs a healthcare-aware second pass.
- `security-review` still applies for general auth, input-handling, secrets, API, and deployment hardening.

## When to Use

- The request explicitly mentions HIPAA, PHI, covered entities, business associates, or BAAs
- Building or reviewing US healthcare software that stores, processes, exports, or transmits PHI
- Assessing whether logging, analytics, LLM prompts, storage, or support workflows create HIPAA exposure
- Designing patient-facing or clinician-facing systems where minimum necessary access and auditability matter

## How It Works

Treat HIPAA as an overlay on top of the broader healthcare privacy skill:

1. Start with `healthcare-phi-compliance` for the concrete implementation rules.
2. Apply HIPAA-specific decision gates:
   - Is this data PHI?
   - Is this actor a covered entity or business associate?
   - Does a vendor or model provider require a BAA before touching the data?
   - Is access limited to the minimum necessary scope?
   - Are read/write/export events auditable?
3. Escalate to `healthcare-reviewer` if the task affects patient safety, clinical workflows, or regulated production architecture.

## HIPAA-Specific Guardrails

- Never place PHI in logs, analytics events, crash reports, prompts, or client-visible error strings.
- Never expose PHI in URLs, browser storage, screenshots, or copied example payloads.
- Require authenticated access, scoped authorization, and audit trails for PHI reads and writes.
- Treat third-party SaaS, observability, support tooling, and LLM providers as blocked-by-default until BAA status and data boundaries are clear.
- Follow minimum necessary access: the right user should only see the smallest PHI slice needed for the task.
- Prefer opaque internal IDs over names, MRNs, phone numbers, addresses, or other identifiers.

## Examples

### Example 1: Product request framed as HIPAA

User request:

> Add AI-generated visit summaries to our clinician dashboard. We serve US clinics and need to stay HIPAA compliant.

Response pattern:

- Activate `hipaa-compliance`
- Use `healthcare-phi-compliance` to review PHI movement, logging, storage, and prompt boundaries
- Verify whether the summarization provider is covered by a BAA before any PHI is sent
- Escalate to `healthcare-reviewer` if the summaries influence clinical decisions

### Example 2: Vendor/tooling decision

User request:

> Can we send support transcripts and patient messages into our analytics stack?

Response pattern:

- Assume those messages may contain PHI
- Block the design unless the analytics vendor is approved for HIPAA-bound workloads and the data path is minimized
- Require redaction or a non-PHI event model when possible

## Related Skills

- `healthcare-phi-compliance`
- `healthcare-reviewer`
- `healthcare-emr-patterns`
- `healthcare-eval-harness`
- `security-review`

© affaan-m · MIT · affaan-m/ECC

Similar skills

All skills for Security →

hipaa-compliance by other authors comes first.

hipaa-compliance devops-skills The hipaa-compliance skill maps HIPAA requirements to safeguards for systems handling ePHI. Use it when reviewing healthcare data protections or planning cloud infrastructure. CX Codex +1 357installs hipaa-compliance curiositech The hipaa-compliance skill guides PHI handling with audit logging, log sanitization, and session checks. Use it when coding features that touch health data. CX Codex +1 215installs hipaa-audit briiirussell hipaa-audit audits applications and infrastructure that handle PHI against HIPAA and HITECH. Use it when an engineering review involves ePHI, BAAs, or breach duties. CX Codex +1 401installs VLayer abasensei VLayer audits healthcare software against HIPAA rules. Flags PHI exposure, missing encryption, and suggests code patches directly inside the AI agent. CX Codex +1 1,871installs run-compliance-review gtmagents run-compliance-review — a Claude Code command that runs a regulatory compliance review for healthcare marketing campaigns against HIPAA, FDA, and FTC rules. Covers email, landing, paid, webinar, field, and events channels. CX Codex +1 ★ 450repo stars data-privacy-compliance davila7 data-privacy-compliance provides implementation blueprints for GDPR, CCPA, and HIPAA compliance directly in your codebase. CX Codex +1 259installs compliance-tracking official anthropics compliance-tracking tracks compliance requirements and audit readiness across SOC 2, ISO 27001, GDPR, HIPAA and PCI DSS, helping structure control data for upcoming audits. CX Codex +1 3,100installs legal-compliance travisjneuman legal-compliance is a Claude Code skill for contract analysis, compliance questions, and legal risk reviews. It covers corporate governance, intellectual property, and litigation management. CX Codex +1 389installs

From the same set150

The whole set →
dotnet-patterns dotnet-patterns is a Claude Code skill that sets C# and ASP.NET Core conventions for AI coding agents generating or refactoring code, covering dependency injection, async/await, and error handling. CX Codex +1 6,300installs autonomous-loops The autonomous-loops skill covers autonomous development loops, from sequential claude -p pipelines to multi-agent DAG orchestration. Use it for CI/CD workflows and long-running tasks. CX Codex +1 6,300installs data-scraper-agent The data-scraper-agent skill walks you through building an agent that scrapes public sources on a schedule, enriches results with Gemini Flash, and stores them in Notion, Sheets or Supabase. CX Codex +1 6,300installs compose-multiplatform-patterns compose-multiplatform-patterns is a skill that guides shared UI design for Compose Multiplatform and Jetpack Compose in KMP projects, covering state, navigation, theming, and platform-specific UI. CX Codex +1 6,300installs regex-vs-llm-structured-text The regex-vs-llm-structured-text Claude Code skill helps choose an extraction method for structured text. It starts with regex for repeated patterns and sends uncertain results to an LLM for review. CX Codex +1 6,200installs click-path-audit click-path-audit — a skill for Claude Code and Codex that audits user-facing touchpoints. Traces sequential state mutations to uncover silent side effects and conflicting resets across UI handlers. CX Codex +1 6,200installs homelab-wireguard-vpn The homelab-wireguard-vpn Claude Code skill guides WireGuard setup for remote access to a home network. It covers server and client configuration, key generation, and the choice between split and full tunnel routing. CX Codex +1 6,200installs healthcare-emr-patterns healthcare-emr-patterns is a Claude Code skill that defines EMR and EHR development patterns focused on patient safety, encounter workflows, and medication checks. CX Codex +1 6,200installs

Project sponsors

Companies that keep this analytics open