Nobody Read the Logs: What OCR’s Latest Ransomware Settlement Means for Your Practice

HIPAA Audit Log Review: Lessons From OCR's Latest Settlement (Dark Edge Consulting)

Written by

in

On October 29, 2026, the HHS Office for Civil Rights announced that Lehigh Valley Health Network agreed to a monetary settlement and a three-year corrective action plan monitored by OCR after a 2023 ransomware attack. HHS called it OCR’s 22nd ransomware enforcement action. The attack exposed information on 248,359 people, including sensitive photographs of cancer patients receiving radiation oncology treatment.

It is easy to read that and think, “That is a health system. I run a four-provider practice.” Read the findings instead of the headline. They are the same gaps we see in independent medical and dental offices, and none of them requires a big budget to close.

What OCR actually found

According to the HHS announcement, OCR found that the organization potentially:

  • Failed to conduct an accurate and thorough risk analysis covering all of its electronic protected health information (ePHI).
  • Failed to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports.
  • Impermissibly disclosed the PHI of 248,359 individuals.
  • Failed to notify affected individuals in time.
  • Failed to notify the HHS Secretary in time.

OCR Director Paula M. Stannard put the first two findings together on purpose: “Failure to conduct an accurate and thorough risk analysis and to undertake regular review of information system activity makes regulated entities attractive targets for cyberattacks.”

The risk analysis finding is familiar. OCR has been hammering it since it launched its Risk Analysis Initiative in October 2024. The finding that deserves more attention from small practices is the second one, because it is the one that quietly causes the last two.

Logs that nobody reads are not a control

The HIPAA Security Rule has two related requirements. Audit controls (45 CFR 164.312(b)) say your systems must record activity involving ePHI. Information system activity review (45 CFR 164.308(a)(1)(ii)(D)) says someone must actually look at those records on a regular schedule.

Most practices have the first and not the second. The EHR keeps an access log. The firewall keeps a log. Microsoft 365 or Google Workspace keeps sign-in records. Then nobody opens any of them until something is already on fire.

That gap matters because of how breach notification works. Under the HIPAA Breach Notification Rule, a breach is treated as discovered on the first day it is known, or by exercising reasonable diligence would have been known, to anyone in your workforce. Notice to patients is due without unreasonable delay and no later than 60 calendar days after discovery (45 CFR 164.404). If your logs showed the intruder weeks before anyone noticed, the clock may have started long before your “discovery” meeting.

In plain English: unread logs do not just let attackers stay longer. They can make your notice late on paper, which turns one problem into two findings.

The state clock is often shorter than the federal one

HIPAA’s 60 days is the ceiling, not the plan. Several states run their own clocks alongside it, and counsel should confirm how each applies to your situation.

  • Texas. Under Texas Business and Commerce Code 521.053, individuals must be notified no later than 60 days after you determine a breach occurred, and the Texas Attorney General must be notified no later than 30 days after that determination if 250 or more Texans are affected. The Attorney General posts those reports publicly. Texas practices also carry the separate privacy duties of HB 300 on top of HIPAA.
  • Florida. Florida Statutes 501.171 sets a 30-day deadline for notifying affected individuals and, for breaches affecting 500 or more Floridians, a 30-day deadline for notifying the Department of Legal Affairs, with a possible 15-day extension for good cause.

A 30-day state deadline leaves no room for a two-week scramble to figure out what happened. The only way to hit it is to already know what your logs say.

What a small practice should check this month

You do not need a security operations center to meet this standard. You need a short list of sources, a schedule, and evidence that the review happened.

  1. List every place ePHI lives. OCR’s first recommendation in the LVHN release is to identify where ePHI enters, flows through, and leaves your systems. That includes the EHR or practice management system, imaging and specialty systems, email, file shares, backups, and any cloud portals. The LVHN breach included clinical photographs, so do not forget image stores.
  2. Confirm each one is actually logging. Check that EHR audit logging is on, that cloud sign-in logs are retained long enough to be useful, and that the firewall and servers keep records somewhere an attacker cannot easily erase.
  3. Decide what “regular review” means for you and write it down. For most independent practices, that is a defined weekly review of a few high-value signals: failed and unusual sign-ins, new admin accounts, mass record access, after-hours access to charts, and changes to forwarding rules in email.
  4. Keep proof. A dated note, ticket, or report showing who reviewed what and what they did about it. OCR asks for evidence, not intentions.
  5. Tie it back to your risk analysis. Your risk analysis should name log review as a safeguard, and your risk management plan should show it is working.
  6. Rehearse the clock. Walk through a mock incident once a year: who decides a breach occurred, who calls counsel and your cyber insurer, and how you would meet a 30-day state deadline.

Where Dark Edge fits

Dark Edge Consulting runs managed security with compliance built in. That means continuous monitoring and alerting on the systems that hold ePHI, a defined log review cadence with records you can hand to an auditor, exploit-first patching driven by the CISA Known Exploited Vulnerabilities catalog, and a full help desk that resolves tickets instead of just logging them.

We are careful about one line. We never audit systems we manage. Our job is to make your independent auditor’s job easier by keeping clean, dated evidence of what was reviewed and when. If you are not a managed client, we can assess your environment independently, including whether your logging and review would hold up to an OCR data request.

Our team holds CISSP and CCSP credentials and brings more than 20 years of security work, and our client relationships have averaged over 15 years. No one can promise you will never have an incident. What you can control is whether you see it early and whether your paperwork shows you were doing the work.

Book a strategy call

If you are not sure who in your practice reads the logs, or whether anyone does, that is the conversation to have before a regulator asks. We will walk through where your ePHI lives, what is being recorded, and what a defensible review routine looks like for a practice your size.

This article is general information, not legal advice. Confirm breach notification obligations with your counsel.