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
npx skills add affaan-m/ECC --skill hipaa-compliance -a claude-codeWhat 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-code2Manually: put the files in place
~/.claude/skills/hipaa-compliance/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/hipaa-compliance/
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill hipaa-compliance -a codex2Manually: put the files in place
.agents/skills/hipaa-compliance/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill hipaa-compliance -a cursor2Manually: put the files in place
.cursor/skills/hipaa-compliance/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install affaan-m/ECC skills/hipaa-compliance2Manually: put the files in place
.github/skills/hipaa-compliance/SKILL.md1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill hipaa-compliance -a gemini-cli2Platform CLI
gemini skills install https://github.com/affaan-m/ECC --path skills/hipaa-complianceManually: put the files in place
.devin/skills/hipaa-compliance/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill hipaa-compliance -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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.