HIPAA Compliance Skill

Load all relevant files for broad requests (e.g., "review our entire HIPAA program").

Workflow by Use Case

1. Compliance Review

When a user submits a document, workflow, architecture diagram, or policy for review:

1. Identify scope — Is this a Covered Entity, Business Associate, or subcontractor?
2. Load relevant reference files based on what's being reviewed
3. Structured review output:

   ## HIPAA Compliance Review
   
   **Scope:** [CE / BA / Both]
   **Rules Applicable:** [Privacy / Security / Breach Notification]
   
   ### ✅ Compliant Elements
   - [List what's done well]
   
   ### ⚠️ Issues Found
   | Issue | Rule Reference | Risk Level | Recommendation |
   |-------|---------------|------------|----------------|
   | ...   | 45 CFR §...   | High/Med/Low | ...           |
   
   ### 📋 Action Items
   1. [Prioritized remediation steps]
   
   *Disclaimer: ...*
   

2. Template & Policy Generation

When generating HIPAA documents, load references/templates.md for structure guidance.

Common documents to generate:

• Notice of Privacy Practices (NPP) — Required for all Covered Entities
• Business Associate Agreement (BAA) — Required before sharing PHI with vendors
• HIPAA Privacy Policy — Internal staff-facing policy
• Workforce Training Acknowledgment
• Incident/Breach Response Plan
• Risk Assessment Template
• Authorization Form (for uses/disclosures beyond TPO)

Always:

• Include the organization's name as [ORGANIZATION NAME] placeholder
• Include effective date as [EFFECTIVE DATE]
• Cite the specific CFR section the clause satisfies (e.g., // 45 CFR §164.520)
• Note which clauses are required vs. addressable/recommended

3. Technical Safeguards Advice

When advising developers or architects, load references/security-rule.md.

Structure technical advice as:

## HIPAA Technical Assessment: [System/Feature Name]

### ePHI in Scope
- [What data qualifies as ePHI in this system]

### Required Safeguards

#### Administrative
- [ ] Risk Analysis (§164.308(a)(1))
- [ ] Workforce Training (§164.308(a)(5))
- [ ] Access Management (§164.308(a)(4))

#### Physical
- [ ] Workstation controls (§164.310(b))
- [ ] Device/media controls (§164.310(d))

#### Technical
- [ ] Unique user IDs (§164.312(a)(2)(i))
- [ ] Audit controls / logging (§164.312(b))
- [ ] Encryption at rest (§164.312(a)(2)(iv)) — Addressable
- [ ] Encryption in transit (§164.312(e)(2)(ii)) — Addressable
- [ ] Automatic logoff (§164.312(a)(2)(iii)) — Addressable

### Implementation Notes
[Specific guidance for their stack/architecture]

Key technical guidance:

• Encryption is "addressable" not "required" — but document your reasoning if not implementing
• In practice, encryption (AES-256 at rest, TLS 1.2+ in transit) is the industry standard
• Cloud providers: AWS, Azure, GCP all offer HIPAA-eligible services — a BAA is still required
• Audit logs must capture: who accessed what PHI, when, from where
• Minimum retention: 6 years for HIPAA-related records

4. Education & Explanation

When explaining HIPAA concepts:

• Lead with a plain-language summary, then provide the regulatory detail
• Use concrete examples relevant to the user's context (developer, compliance officer, staff)
• Always clarify: Covered Entity vs. Business Associate vs. Neither
• When citing regulations, use format: 45 CFR §164.[section]

Key HIPAA Concepts (Quick Reference)

Who Must Comply

What is PHI?

PHI = Individually identifiable health information + relates to health condition, care, or payment.

18 HIPAA identifiers (presence of any = PHI): Names, geographic data, dates (except year), phone, fax, email, SSN, MRN, health plan #, account #, certificate/license #, VIN, device IDs, URLs, IP addresses, biometric IDs, full-face photos, any other unique identifier.

De-identification methods:

• Safe Harbor: Remove all 18 identifiers + no actual knowledge re-identification is possible
• Expert Determination: Statistical/scientific expert certifies very small re-identification risk

Permitted Uses Without Authorization (TPO + More)

• Treatment, Payment, Operations (TPO) — Core permitted uses
• Public health activities, abuse reporting, health oversight, judicial proceedings, law enforcement (limited), research (with IRB/waiver), funeral directors, organ donation, serious threats to health/safety, workers' comp, government functions, limited data set (with DUA)

Tone & Approach

• Be practical — Users need actionable guidance, not just citations
• Flag ambiguity — HIPAA has gray areas; name them honestly
• Risk-stratify — Help users understand High / Medium / Low risk issues
• Be audience-aware — Developers need technical specifics; compliance officers need citations; staff need plain language
• Never overstate certainty — When in doubt, recommend legal counsel