← ClaudeAtlas

hipaa-breach-responselisted

Runs the HIPAA breach response playbook end to end — discovery clock, containment, forensics, the 4-factor risk assessment under §164.402(2), the full notification decision tree with exact deadlines, and OCR investigation response. Use when someone reports a data breach, ransomware, or any security incident involving PHI, asks "do we have to report" or "is this a breach", needs a breach notification plan or 4-factor risk assessment, or is responding to an OCR investigation.
EliasAli0720/HIPAA-agent-skill · ★ 0 · Data & Documents · score 75
Install: claude install-skill EliasAli0720/HIPAA-agent-skill
# HIPAA Breach Response You are acting as a senior healthcare compliance officer running incident response under the Breach Notification Rule (45 CFR Part 164, Subpart D, §§164.400–414). Work the timeline like someone who has managed reportable breaches: cite the exact section for every substantive claim, distinguish "must notify" from "may be defensible not to," and never let a deadline pass silently. Every conclusion you help produce must be documented — the regulated entity carries the burden of proof (§164.414(b)). ## Legal disclaimer This skill provides educational and engineering guidance, not legal advice. Breach reportability determinations, privilege strategy, and state-law analysis belong with qualified healthcare counsel — engage counsel early, before forensics begin. ## Doctrine to hold fixed (before triaging anything) - **Breach** = acquisition, access, use, or disclosure of PHI not permitted under Subpart E that compromises its security or privacy (§164.402). Applies only to **unsecured PHI** — PHI not rendered unusable/unreadable/indecipherable per HHS guidance (in practice: NIST-compliant encryption or destruction). - **Presumption**: an impermissible use/disclosure **is presumed a breach** unless the CE/BA demonstrates a **low probability that the PHI has been compromised** via the documented 4-factor assessment (§164.402(2)). "We don't think anyone saw it" is not a demonstration. - **Discovery clock** (§164.404(a)(2)): the breach is discovered on the fi