Skip to main content
The state of ai impact assessment
Penalty Freeze or Not, OCR Is Still Asking for Your Risk AnalysisOCR Enforcement & Penalties
5 min readFor Compliance Officers

Penalty Freeze or Not, OCR Is Still Asking for Your Risk Analysis

The questions below arise from compliance team discussions following OCR's $800,000 settlement with Lehigh Valley Health Network (LVHN) on October 29. This settlement came just eight days after HHS confirmed in an October 21 Federal Register notice that HIPAA penalty amounts would remain at their 2025 levels. Some teams see the freeze as a reprieve, but the LVHN case suggests otherwise. Here's what people are asking, and what we'd advise.

Q1: Penalties are frozen at 2025 levels. Can we ease off a little this year?

No. The freeze affects per-violation dollar caps, not OCR's enforcement intensity. The LVHN settlement is OCR's 22nd ransomware enforcement action, with three years of OCR monitoring, longer than the two years in prior settlements. Monitoring can be costly, tying up your team, documentation, and budget long after the settlement check clears.

There's also a catch-up risk. HIPAA Journal expects the inflation adjustment to cover two years at once in 2027. Delaying compliance efforts now won't save money later.

Q2: What did OCR actually find at LVHN?

OCR identified five potential violations across the HIPAA Security, Privacy, and Breach Notification Rules:

  • Failure to conduct an accurate and thorough risk analysis of risks and vulnerabilities to all Electronic Protected Health Information (ePHI)
  • Failure to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports
  • Impermissible disclosure of the Protected Health Information (PHI) of 248,359 individuals
  • Failure to notify affected individuals in time
  • Failure to notify the HHS Secretary in time

The settlement isn't an admission of liability by LVHN, but the pattern is significant. The first two findings are Security Rule basics, and OCR Director Paula M. Stannard linked them directly to attack exposure.

Q3: The ransomware came in through an acquired physician group. Does an acquisition change our risk analysis obligations?

Yes, it expands your scope. The attackers used ransomware in the IT system of a physician group LVHN acquired. Your risk analysis must cover all ePHI your organization creates, receives, maintains, or transmits, including acquired systems from the day they hold your data.

In practice, integrate an M&A step into your process. Before connecting an acquired entity's network to yours, inventory where its ePHI resides and flows, and conduct a risk analysis that includes it. Then incorporate it into your enterprise analysis and risk management plan. Don't wait for the next annual cycle. For example, if a Covered Entity acquires a small practice in March and plans to integrate IT by year-end, that practice's systems hold your patients' data for nine months without analysis. That's the gap OCR targets.

Q4: What does an "accurate and thorough" risk analysis look like in practice?

OCR's guidance suggests several concrete steps:

  1. Map your ePHI. Identify where it resides and how it enters, moves through, and exits your systems. Email is one exit path, so include it in your scope.
  2. Identify threats and vulnerabilities for each system and data flow, not just critical systems.
  3. Document the analysis and keep dated versions. An investigator will request it.
  4. Incorporate it into a risk management plan. An analysis that doesn't inform remediation decisions is incomplete. LVHN's corrective action plan requires both.
  5. Update it periodically and when your environment changes, such as an acquisition, a new EHR module, or a new Business Associate handling ePHI.

NIST SP 800-66 is a practical reference for aligning your approach to the HIPAA Security Rule. If your team treats risk analysis as an annual checkbox, this is where to tighten first. The same failure appeared in every settlement covered in earlier penalty-freeze coverage, from the four ransomware cases OCR closed in April to the Ambry Genetics phishing case in September.

Q5: Nobody's reviewing our audit logs on a schedule. How big a deal is that?

It's significant enough to be a standalone finding. OCR cited LVHN for failing to regularly review records of information system activity. Under the Security Rule's information system activity review requirement, logs that aren't reviewed don't protect anyone.

Set a schedule and assign an owner. Decide which sources get reviewed (audit logs, access reports, security incident tracking reports), how often, and what triggers escalation. Keep a record that reviews occurred, even when they find nothing. "We review logs" is an assertion. A dated review record is evidence.

Q6: What are the breach notification deadlines, and why do teams keep missing them?

Two of OCR's five LVHN findings involve late notice, so precision is essential. Under the Breach Notification Rule:

  • Affected individuals must be notified without unreasonable delay and no later than 60 days after the breach is discovered.
  • The HHS Secretary must be notified on the same timeline when a breach affects 500 or more people, as LVHN's did.
  • Smaller breaches can be reported to the Secretary once a year, within 60 days after the end of the calendar year.

Remember, 60 days is an outer limit, not a target. HIPAA Journal notes breach notification failures in five of the 12 HIPAA settlements announced this year, so this isn't an LVHN-specific issue.

Teams miss deadlines because the clock is nobody's responsibility. Include it in your incident response plan: assign an owner for the notification timeline, define who determines the discovery date, and set internal checkpoints well before day 60. Pre-draft your notification templates and HHS submission steps so you're not creating them mid-crisis.

Where to go for more

Start with OCR's resolution agreement and press materials for the LVHN matter, as the corrective action plan serves as a free audit checklist. Pair it with NIST SP 800-66 for Security Rule implementation guidance and HHS's Breach Notification Rule page for deadline mechanics. If you're building out your audit log program or reviewing how ePHI leaves your organization by email, these are the starting points. Regardless of the penalty tables, an investigator will ask for two things: a current risk analysis and proof of system activity review.

Application Security Isn’t Optional Anymore.

You Might Also Like