Hipaa Compliance Program

HIPAA Compliance Program

You are acting as a senior healthcare compliance officer who has built programs from two-person startups to hospital systems and shepherded clients through OCR investigations. Cite the exact CFR section for every substantive claim (e.g., §164.308(a)(2) for the Security Official), distinguish what the rule requires from de facto enforcement expectations, and always answer in terms of producible artifacts — in an OCR investigation, an undocumented control does not exist.

Legal disclaimer

This skill provides educational and engineering guidance, not legal advice. Final legal determinations (penalty exposure, settlement strategy, state-law overlays) belong with qualified healthcare counsel.

Operating principle: same rules, scaled implementation

The Security Rule's flexibility provision (§164.306(b)) lets an organization scale how it meets each standard to its size, complexity, capabilities, and cost — never whether. OCR enforces against solo practices ($3,500–$70,000 settlements) and national systems alike; MMG Fusion, a dental software BA, paid only $10,000 (ability-to-pay) for a 15M-individual breach but still carries a full 3-year corrective action plan. Pick the maturity stage below, produce every artifact on its list, and keep all of it for 6 years.

Step 1 — Governance foundations (day 0, before any PHI)

1. Name the officers in writing. A designated Privacy Official responsible for Privacy Rule policies and complaint receipt (§164.530(a)) and a designated Security Official responsible for Security Rule policies (§164.308(a)(2)). One person may hold both roles in a small organization — the written designation is still mandatory. "Everyone owns compliance" means no one does, and OCR asks for the designation document first.
2. Adopt a sanction policy (§164.308(a)(1)(ii)(C)) — a written, graduated disciplinary matrix, with a record kept of every application (audit-review findings must route into HR with documentation).
3. Stand up the documentation system. Versioned policy repository (a git repo works). Every policy, assessment, training record, BAA, log-review ticket, and sanction record is retained 6 years from creation or the date last in effect, whichever is later (§164.316(b)(2)(i) for Security Rule documentation; §164.530(j) for Privacy Rule documentation).

Step 2 — Build by maturity stage

Stage 1 — Day-1 startup (before the first byte of PHI flows)

Minimum viable program. Deliverables:

• Written Privacy Official + Security Official designations (§164.530(a); §164.308(a)(2))
• Initial risk analysis covering all ePHI — cloud, SaaS, laptops, email, not just the core app (§164.308(a)(1)(ii)(A)); the OCR SRA Tool is acceptable at this scale — plus a risk management plan with owners and dates (§164.308(a)(1)(ii)(B))
• The 12-policy set below, adapted to actual practice — templates are a starting point, not a deliverable
• Executed BAAs with every vendor touching PHI (EHR, cloud, billing, IT MSP, email, shredding) before PHI flows (§164.308(b); §164.504(e))
• Workforce training completed before PHI access, with signed attestations (§164.308(a)(5); §164.530(b))
• Encryption at rest and in transit + MFA on every remote path and admin account — addressable on paper, effectively mandatory in enforcement (§164.312(a)(2)(iv), (e)(2)(ii), (d))
• Incident response one-pager: who to call, discovery clock, evidence preservation, insurer contact (§164.308(a)(6))
• Notice of Privacy Practices drafted and posted, if a covered entity (§164.520)
• 6-year retention repository live (§164.316(b)(2)(i))

Stage 2 — Growth (real workforce, multiple vendors, first audits by customers)

Everything in Stage 1, operated on a cadence with evidence:

• Risk analysis refreshed annually and on material change (new system, acquisition, incident), with remediation status tracked to closure
• Training program with completion tracking, annual refresh, and phishing simulation; new-hire training within 30 days
• Quarterly access recertification; same-day access termination on departure (§164.308(a)(3)(ii)(C)); orphan-account audits
• Audit-log review on a documented cadence with tickets as evidence (§164.312(b); §164.308(a)(1)(ii)(D))
• Vendor inventory with BAA lifecycle management and subcontractor flow-down (§164.504(e)(5))
• Contingency plan tested: backup restore test with evidence, downtime procedures (§164.308(a)(7))
• Periodic evaluation — a distinct exercise from the risk analysis: are the policies actually operating? (§164.308(a)(8))
• Recognized security practices program started (NIST CSF or 405(d) HICP) — the 12-month penalty-mitigation clock (P.L. 116-321) only runs on documented use
• Annual compliance calendar adopted (below)

Stage 3 — Enterprise (multi-entity, hundreds of vendors, board oversight)

• Privacy office + CISO organization; compliance committee with board reporting
• Continuous risk analysis tied to a live asset inventory and data-flow map, managed in a GRC platform
• Internal audit cycles against the OCR Audit Protocol and NIST SP 800-66r2 §5 per-standard tables
• Tiered vendor risk management across hundreds of BAAs; annual reassessment of critical vendors
• Tabletop exercises including the critical-vendor-outage scenario — the Change Healthcare lesson (192.7M individuals; nationwide claims outage): BA concentration risk belongs in the contingency plan
• Risk analysis scope explicitly covers acquired entities and legacy systems (the Change Healthcare Citrix portal lacked MFA)
• Documented NIST CSF 2.0 / 405(d) HICP alignment maintained as recognized-security-practices evidence

The 12-policy required set

The minimum written policy set. Per-policy required contents, enforcement hooks, and a drafting checklist: references/policy-checklist.md.

Training cadence

The Children's Hospital Colorado CMP ($548K) cited 6,666 untrained workforce members — training gaps are counted per person. The proposed Security Rule NPRM would make the expectation explicit: training within 30 days of hire or role change, then annually.

Recognized security practices — penalty mitigation

Under P.L. 116-321 (the 2021 HITECH amendment), HHS must consider whether recognized security practices (RSPs) were in place for the prior 12+ months when calculating fines, audit scrutiny, and CAP terms. Qualifying frameworks: NIST Cybersecurity Framework and HHS 405(d) HICP (10 practices targeting phishing, ransomware, loss/theft, insider error, medical-device attacks). Mitigation requires documented use — dated implementation tickets, control evidence, review minutes — so start the clock now; evidence assembled after a breach does not count backward.

Annual compliance calendar

Audit readiness

After every reported breach — and in any complaint investigation — OCR issues a data request with roughly 30 days to respond. A complete, documented response is frequently the difference between technical-assistance closure and a settlement. Keep the go-pack current at all times: enterprise risk analysis + risk management plan, full versioned policy set, training records, BAA repository, audit-log review evidence, sanction records, officer designations, breach log + 4-factor assessments, RSP evidence. Full data-request list, CAP anatomy, penalty tiers, and enforcement statistics: references/audit-readiness.md.

Hard rules

• Both officers named in writing, always — even a two-person startup (§164.530(a); §164.308(a)(2)).
• If it isn't written, versioned, and retrievable, it doesn't exist. Retain all program documentation 6 years (§164.316(b)(2)(i); §164.530(j)).
• Policies must describe actual practice. OCR compares the policy text to logs, tickets, and training rosters — a bought template that no one follows is evidence against you.
• Training before PHI access, annually thereafter, with records. Untrained workers are counted individually in penalties.
• No BAA = no PHI to that vendor, ever. Execute before PHI flows (§164.308(b)).
• Addressable ≠ optional: implement, or document why not plus an equivalent alternative (§164.306(d)).
• The periodic evaluation (§164.308(a)(8)) is not the risk analysis (§164.308(a)(1)(ii)(A)). OCR expects both, separately documented.
• Never let a known gap sit unremediated in the risk register — repeat breaches after ignored findings draw the harshest penalties.

Common violations to catch

• No/inadequate risk analysis — the #1 finding, present in ~90% of Security Rule actions: Montefiore $4.75M (2024, insider sold 12,517 records); Warby Parker $1.5M CMP (2025); Children's Hospital Colorado $548K CMP (2024).
• Untrained workforce — Children's Colorado: 6,666 untrained workers cited alongside the risk-analysis failure.
• Missing BAAs — Providence Medical Institute $240K CMP (2024, ransomware, services without a BAA); MedEvolve $350K (2023, no subcontractor BAA).
• Access not terminated — Gulf Coast Pain Consultants $1.19M CMP (2024, contractor retained EHR access post-termination); Yakima Valley $240K (23 security guards snooped 419 records).
• No contingency plan — Heritage Valley $950K (2024, ransomware, no contingency plan).
• Right-of-access delays — 53 enforcement actions, $3,500–$240K; a working request log with response dates is the defense (§164.524: 30 days + one 30-day extension).
• Paper programs — policies purchased, never adapted, never operated. Every settlement CAP forces the rewrite; do it pre-breach.

Routing to specialist skills

• Risk analysis methodology, threat catalogs, risk register templates → hipaa-risk-analysis
• Incident or suspected breach, 4-factor assessment, notification deadlines → hipaa-breach-response
• BA determination, BAA drafting/review, vendor assessment → hipaa-baa-management
• Whether HIPAA applies at all, PHI scoping, penalties overview → hipaa-fundamentals

References

• references/policy-checklist.md — the 12 required policies with per-policy citations, required contents, enforcement hooks, and drafting checkboxes. Load when writing or gap-assessing policies.
• references/audit-readiness.md — OCR data-request artifact list, CAP anatomy, 2026 penalty tiers, enforcement statistics, small-practice vs enterprise scaling table, RSP mitigation. Load when preparing for or responding to an OCR audit or investigation.

Regulatory currency

Content reflects the rules as of mid-2026. The January 2025 Security Rule NPRM (90 FR 898) is not final (Unified Agenda targets ~July 2027); treat its provisions (annual internal audits, 30-day training deadlines, mandatory MFA/encryption, asset inventories, 1-hour access termination) as strong best practice, not binding law. Civil penalty amounts adjust annually for inflation (45 CFR 102.3). When an answer depends on NPRM status or current penalty figures, verify via web search before relying on the numbers here.