Breach Update

Health Network Pays $800K HIPAA Penalty After Ransomware

A Pennsylvania health network paid OCR $800,000 after a BlackCat ransomware breach exposed 248,359 patients. Here's what went wrong and what to fix.

Article Image

Key takeaways

  • A Pennsylvania health network paid $800,000 to settle a HIPAA penalty tied to a 2023 BlackCat ransomware attack that exposed the PHI of 248,359 people.
  • OCR pointed to two Security Rule failures: no accurate, thorough risk analysis, and no regular review of system activity records such as audit logs.
  • The network was also cited for late breach notices to patients and to the HHS Secretary.
  • The network agreed to a corrective action plan, and OCR will monitor it for three years. It did not admit liability.
  • This is OCR's 22nd ransomware enforcement action, and breach notification failures keep showing up in recent settlements.

A Pennsylvania health network has agreed to pay an $800,000 HIPAA penalty to the HHS Office for Civil Rights (OCR). The settlement resolves alleged violations of the HIPAA Privacy, Security, and Breach Notification Rules found during OCR's investigation of a 2023 ransomware attack. Besides the payment, the network agreed to a corrective action plan to fix the compliance gaps OCR identified. OCR announced the settlement on October 29, and it is the agency's 22nd enforcement action against a HIPAA-regulated organization after a ransomware attack.

How the ransomware attack unfolded

The network found suspicious activity on its systems in early February 2023. OCR places detection on February 4, and the network later confirmed ransomware was involved. The ALPHV/BlackCat ransomware group had broken into the IT systems supporting a physician group the network acquired in 2021.

The attackers stole data before deploying the ransomware and demanded a ransom to keep it private. The network refused to pay. BlackCat then published stolen data on the dark web, including clinical photographs of cancer patients taken during radiation oncology treatment. Other exposed information included names, addresses, Social Security numbers, financial information, diagnoses, medications, and treatment records.

The network sent OCR a breach report in May 2023 covering 248,359 people, and OCR opened its investigation after receiving it.

Separate from the OCR penalty The breach also led to a class action lawsuit, which the network settled for $65 million. A Pennsylvania judge approved that settlement in November 2024. The litigation followed the release of patient photographs after the ransom demand was refused.

The HIPAA violations OCR identified

OCR found several potential violations across all three HIPAA rules. Two of them came under the Security Rule, and they are the kind of gaps that let an intrusion grow into a large breach.

Security Rule failures

  • No accurate and thorough risk analysis. The network had not properly assessed the risks and vulnerabilities to the confidentiality, integrity, and availability of all of its electronic PHI.
  • No regular review of information system activity. The network had no procedures for regularly reviewing records like audit logs, access reports, and security incident tracking reports.

OCR said these failures led to the impermissible disclosure of ePHI belonging to 248,359 people, which it treated as a Privacy Rule violation.

Breach Notification Rule failures

OCR also found that the network was late notifying affected patients that their personal and health information had been stolen, and late notifying the HHS Secretary. When a breach of unsecured PHI affects 500 or more people, the Secretary must be told within 60 days of discovery. OCR's timeline runs from detection on February 4, 2023, to a breach report on May 15, 2023, which is longer than that window.

"The best defense against cyberattacks is full implementation of the HIPAA Security Rule."

Paula M. Stannard, Director, HHS Office for Civil Rights

Stannard also said that skipping an accurate risk analysis and regular reviews of system activity makes regulated entities attractive targets for cyberattackers.

What the corrective action plan requires

Under the resolution agreement, the network will work through a corrective action plan that OCR will monitor for three years. The plan requires the network to:

  1. Conduct a comprehensive, accurate risk analysis of risks and vulnerabilities to its ePHI.
  2. Develop and implement a risk management plan to address the risks the analysis finds.
  3. Put audit controls in place that record and examine information system activity, and review that activity regularly.
  4. Review and revise its HIPAA policies and procedures so they comply with the HIPAA Rules.
  5. Develop training materials and train its workforce on the HIPAA Rules as they apply to each person's job duties.

The network did not admit liability as part of the agreement.

When did you last complete a real risk analysis?It's the first thing OCR asks for after a breach. We'll handle it for you.

Contact us

Breach notification penalties keep coming

OCR hasn't announced a formal enforcement initiative on the Breach Notification Rule. Even so, late notification keeps appearing in its settlements. Five of the 12 HIPAA settlements announced so far this year included penalties for breach notification failures, and five settlements last year did too.

A lot of organizations treat notification as paperwork for later, after containment and forensics. OCR doesn't see it that way. The 60-day limit starts when the breach is discovered, not when the investigation ends. If a full count of affected people isn't ready yet, that doesn't stop the clock.

Deadline reminder Affected people must be notified without unreasonable delay, and no later than 60 days after a breach is discovered. Breaches affecting 500 or more people must also be reported to the HHS Secretary within that same 60-day window.

Lessons for healthcare organizations from this HIPAA penalty

This case follows a familiar pattern. Ransomware gets in, data leaves, and OCR's investigation finds that basic Security Rule requirements had not been met before the attack. Several points apply to practices and health systems of any size:

  • Acquisitions bring in their own risk. The attackers here got in through IT systems belonging to a physician group acquired two years earlier. Your risk analysis has to cover acquired practices, their networks, and any legacy systems that come with them.
  • Logs only help if someone reads them. Audit controls are required, but OCR also expects regular, documented reviews of audit logs and access reports. Those reviews are often how an intrusion gets caught early.
  • Build a notification plan ahead of time. Decide who drafts notices, who contacts HHS, and how you'll meet the 60-day deadline while forensics is still going.
  • Update the risk analysis when things change. Mergers, new systems, and new vendors all change your risk picture.

Many smaller practices don't have staff who can scan their own networks and document risks well enough to hold up in an OCR investigation. PolySec does on-site HIPAA security risk assessments that include vulnerability and network scanning, policy and BAA review, and an audit-ready findings report with a remediation roadmap. Those are the same areas this corrective action plan now requires the network to fix.

Frequently asked questions

How much was the HIPAA penalty in this case?

The health network paid $800,000 to OCR and agreed to a corrective action plan with three years of OCR monitoring.

How many people were affected by the breach?

The breach report covered 248,359 people. Exposed data included Social Security numbers, financial information, diagnoses, treatment records, and photographs of radiation oncology patients.

Which HIPAA rules did OCR say were violated?

OCR cited potential violations of the Security Rule (risk analysis and review of system activity), the Privacy Rule (impermissible disclosure of ePHI), and the Breach Notification Rule (late notices to patients and to HHS).

How many ransomware cases has OCR settled?

This settlement is OCR's 22nd enforcement action against a HIPAA-regulated organization following a ransomware attack.

Next steps for your practice

The most expensive parts of this case were the $65 million class action and the patients whose photos were published, not the $800,000 OCR payment. A current, thorough risk analysis and routine log reviews won't stop every attack, but they are what OCR checks for first. They also give you the best chance of catching an intruder before data is taken. If your last risk analysis is more than a year old or skipped part of your network, start there.


This article is for general information and isn't legal advice. Talk to a qualified professional about your practice's specific situation.

Written by the PolySec Team

PolySec performs HIPAA Security Risk Assessments for healthcare practices and business associates nationwide.

Get your required HIPAA risk assessment done.

Tell us about your practice and we'll scope the assessment for you.

Contact us