News
Amplifon Discloses February 2026 Cyberattack Affecting Patients' Hearing and Medical Records, Including Social Security Numbers · Data BreachINC Ransom Claims Attack on Tanner Clinic, Utah Multispecialty Medical Group; Patient Data at Risk · Data BreachPremise Health Insider Breach Affects 417,000 Patients in Five States; Nationwide Toll May Reach Millions · Data BreachOCR Settles HIPAA Security Rule Investigation with Genetic Testing Firm for $700,000 Following 2020 Phishing Breach Affecting 225,370 Individuals · OCR EnforcementMultistate AG Coalition Reaches $10 Million Settlement with Perry Johnson & Associates Over 13.3 Million-Record Medical Transcription Breach · OCR EnforcementCognitive Health Technologies Discloses Network Intrusion Affecting 49,467 Patients; Added to HHS Breach Portal · Data BreachHCA Healthcare, Blossom Health, El Camino Health, and UMMC Disclose Patient Data Breaches; Medusa Ransomware Linked to UMMC Incident · Data BreachVida Y Salud-Health Systems and Hampton Regional Medical Center Reach Class-Action Data Breach Settlements · Data BreachMarathon Health Discloses August 2026 Social-Engineering Breach Affecting 5.7 Million Employer-Plan Members · Data BreachUniversity Hospitals (Cleveland) Still Offline Weeks After October 22 Cyberattack; EyeMed Vision Care and Facial Surgery Group Also Report Incidents · Data BreachFour Healthcare Entities Disclose New Breaches: Cognitive Health Technologies, City Ambulance Service, Baraga County Memorial Hospital, and Others · Data BreachOCR Settles HIPAA Ransomware Investigation with Lehigh Valley Health Network · OCR EnforcementHospital Ransomware Attacker Sentenced to 70 Months in Federal Prison for Extorting Healthcare Targets · OCR EnforcementConduent Agrees to $80 Million Class-Action Settlement Over 62.2 Million-Record Healthcare Data Breach · Data BreachDenver Health Medical Plan Notifies 238,000 Members After Vendor SquareML Access-Key Leak Exposes Personal and Health Data · Data BreachByod Ransomware Group Claims Attack on UNM Health Sciences Center, Disrupting Surgeries and Ambulance Diversions at New Mexico's Only Level I Trauma Center · Data BreachInsomnia Ransomware Group Claims Attack on NorthShore Health Centers; Indiana Nonprofit Warns Patients of PHI Exposure · Data BreachQuest Diagnostics Discloses Breach of Quanum Lab Services Manager; Unauthorized Party Accessed Patient Records · Data BreachManhattan Law Firm Tarter Krinsky & Drogin Reports PHI Breach Affecting 196,645 Patients; Park Dental and Heritage Pediatrics Also Disclose Incidents · Data BreachAmplifon Discloses February 2026 Cyberattack Affecting Patients' Hearing and Medical Records, Including Social Security Numbers · Data BreachINC Ransom Claims Attack on Tanner Clinic, Utah Multispecialty Medical Group; Patient Data at Risk · Data BreachPremise Health Insider Breach Affects 417,000 Patients in Five States; Nationwide Toll May Reach Millions · Data BreachOCR Settles HIPAA Security Rule Investigation with Genetic Testing Firm for $700,000 Following 2020 Phishing Breach Affecting 225,370 Individuals · OCR EnforcementMultistate AG Coalition Reaches $10 Million Settlement with Perry Johnson & Associates Over 13.3 Million-Record Medical Transcription Breach · OCR EnforcementCognitive Health Technologies Discloses Network Intrusion Affecting 49,467 Patients; Added to HHS Breach Portal · Data BreachHCA Healthcare, Blossom Health, El Camino Health, and UMMC Disclose Patient Data Breaches; Medusa Ransomware Linked to UMMC Incident · Data BreachVida Y Salud-Health Systems and Hampton Regional Medical Center Reach Class-Action Data Breach Settlements · Data BreachMarathon Health Discloses August 2026 Social-Engineering Breach Affecting 5.7 Million Employer-Plan Members · Data BreachUniversity Hospitals (Cleveland) Still Offline Weeks After October 22 Cyberattack; EyeMed Vision Care and Facial Surgery Group Also Report Incidents · Data BreachFour Healthcare Entities Disclose New Breaches: Cognitive Health Technologies, City Ambulance Service, Baraga County Memorial Hospital, and Others · Data BreachOCR Settles HIPAA Ransomware Investigation with Lehigh Valley Health Network · OCR EnforcementHospital Ransomware Attacker Sentenced to 70 Months in Federal Prison for Extorting Healthcare Targets · OCR EnforcementConduent Agrees to $80 Million Class-Action Settlement Over 62.2 Million-Record Healthcare Data Breach · Data BreachDenver Health Medical Plan Notifies 238,000 Members After Vendor SquareML Access-Key Leak Exposes Personal and Health Data · Data BreachByod Ransomware Group Claims Attack on UNM Health Sciences Center, Disrupting Surgeries and Ambulance Diversions at New Mexico's Only Level I Trauma Center · Data BreachInsomnia Ransomware Group Claims Attack on NorthShore Health Centers; Indiana Nonprofit Warns Patients of PHI Exposure · Data BreachQuest Diagnostics Discloses Breach of Quanum Lab Services Manager; Unauthorized Party Accessed Patient Records · Data BreachManhattan Law Firm Tarter Krinsky & Drogin Reports PHI Breach Affecting 196,645 Patients; Park Dental and Heritage Pediatrics Also Disclose Incidents · Data Breach

OCR Enforcement

Assured Imaging Fined for Never Conducting a Risk Analysis: 244,813 Patients Affected

TL;DR

Assured Imaging, a medical imaging provider operating across Arizona and California, was fined by OCR after a 2020 ransomware attack exposed the PHI of 244,813 individuals. OCR found the organization had never conducted a HIPAA Security Rule risk analysis and failed to notify affected individuals within the required 60-day window, two separate violations that compounded each other's penalty exposure.

Assured Imaging, a medical imaging provider operating across Arizona and California, was fined by OCR after a 2020 ransomware attack exposed the PHI of 244,813 individuals. OCR found the organization had never conducted a HIPAA Security Rule risk analysis and failed to notify affected individuals within the required 60-day window, two separate violations that compounded each other's penalty exposure.

OCR's settlement with Assured Imaging highlights two compounding violations: no risk analysis ever conducted and delayed breach notification. Here is what every covered entity must learn from this case.

medcomply.ai editorial teamPublished May 3, 2026Updated May 3, 20265 min read

Of the four ransomware settlements OCR announced on April 23, 2026, the Assured Imaging case is the most instructive. It is not just a story about a ransomware attack. It is a story about what happens when an organization operates as a HIPAA covered entity for years without ever fulfilling its most fundamental Security Rule obligation, and then compounds that failure with a delayed response when the inevitable breach occurs.

What happened

The largest financial penalty announced this month resolved potential HIPAA violations identified by OCR during an investigation of a ransomware-related data breach at Assured Imaging Affiliated Covered Entities, a medical imaging and screening service provider with corporate headquarters in Arizona and California. The ransomware attack was discovered on May 19, 2020, and involved the theft of ePHI such as names, contact information, dates of birth, diagnosis and conditions, lab results, medications, and treatment information of 244,813 individuals.

The nature of the exposed data matters here. Medical imaging records contain among the most sensitive PHI a healthcare organization can hold, diagnoses, lab results, and treatment information that patients share in contexts of significant vulnerability. A breach of this data carries real potential for harm through discrimination, stigma, and identity fraud.

The two violations: and why they compound

OCR identified two distinct violations at Assured Imaging. Understanding each is essential.

Violation 1. No risk analysis, ever.

Assured Imaging was unable to provide evidence that a risk analysis had ever been completed.

This is the most serious finding OCR makes in a breach investigation. It is not a finding that the risk analysis was outdated, or incomplete, or not updated after a system change. It is a finding that the organization, which had been handling the PHI of hundreds of thousands of patients, had never once conducted the foundational assessment required by the HIPAA Security Rule.

45 CFR §164.308(a)(1)(ii)(A)

Without a risk analysis, every other Security Rule safeguard becomes a guess. Access controls, encryption decisions, incident response planning, all of these depend on knowing what ePHI you hold, where it lives, and what threatens it. Assured Imaging did not know those things because it had never looked.

Violation 2. Late breach notification.

OCR determined that Assured Imaging failed to notify the affected individuals within 60 days, as required by the HIPAA Breach Notification Rule.

The breach was discovered May 19, 2020. The 60-day individual notification deadline was July 18, 2020. Missing that deadline is an independent HIPAA violation, separate from the breach itself and separate from the risk analysis failure.

45 CFR §164.404(b)

Warning

Breach notification timing is non-negotiable. The 60-day clock runs from the date of discovery, not the date your investigation concludes, not the date you confirm the scope of the breach, not the date your legal team finishes its review. Missing this deadline creates a second independent violation on top of whatever caused the breach.

The stackable violation problem

Breach notification timeliness remains a separate, stackable violation, as illustrated by OCR's settlement with Assured Imaging.

This is a critical concept for every covered entity to understand. HIPAA violations do not merge, they stack. An organization that experiences a ransomware attack and had no risk analysis faces one set of penalties. The same organization that also misses its 60-day notification deadline faces an additional set of penalties for the notification failure. Each violation category carries its own annual penalty cap.

For Assured Imaging, two violation categories, risk analysis failure and breach notification failure, meant two separate penalty tracks running simultaneously.

What the corrective action plan requires

As part of the settlement, Assured Imaging agreed to a corrective action plan that OCR will monitor. Based on OCR's standard CAP requirements for similar cases, this includes:

Conducting and documenting a comprehensive, enterprise-wide risk analysis covering all systems containing ePHI. Developing a risk management plan that addresses every identified vulnerability with assigned responsibility and timelines. Implementing written HIPAA policies and procedures. Providing workforce training. Establishing and testing breach detection and response procedures, including clear ownership of the 60-day notification deadline.

Three things every medical imaging organization must do now

The Assured Imaging case has specific implications for medical imaging providers, a category of covered entity that handles particularly sensitive PHI across multiple locations and systems.

Audit your ePHI inventory immediately. Medical imaging organizations typically operate across multiple facilities with complex technology infrastructure, PACS systems, diagnostic workstations, cloud archives, and referring physician portals all potentially containing ePHI. Your risk analysis must cover every one of these systems. An asset inventory is the foundation.

Establish a 60-day notification tracking system. From the moment any potential breach is discovered, a documented countdown must begin. Every person involved in breach response, IT, legal, compliance, leadership, must know the deadline and their role in meeting it. Missing the deadline because the investigation was still ongoing is not a defense OCR accepts.

Do not let investigation timelines override notification obligations. Organizations often delay notification while investigating the scope of a breach. This is understandable operationally but legally dangerous. HIPAA permits notification with incomplete information, supplemented later. It does not permit notification delays while you gather complete information.

Assured Imaging had never conducted a risk analysis. That single failure made every other compliance question moot, because without knowing what you have and what threatens it, every security decision your organization makes is uninformed. The risk analysis is not a compliance formality. It is the document that proves your organization knows what it is protecting.

Sources & citations

  • HHS OCR. April 23 2026 Ransomware Enforcement ActionsOpen
  • HIPAA Journal, OCR Fines Four Entities for Ransomware ViolationsOpen
  • 45 CFR §164.308(a)(1). Risk Analysis RequirementOpen
  • 45 CFR §164.404. Individual Breach NotificationOpen

All content verified against official HHS guidance and the Code of Federal Regulations.

Frequently asked questions

What was the Assured Imaging HIPAA violation?▾
Assured Imaging faced two violations: first, OCR determined the organization had never conducted a HIPAA Security Rule risk analysis at any point before the breach. Second, after the ransomware attack exposed the PHI of 244,813 individuals, Assured Imaging failed to notify affected individuals within the required 60-day window.
What data was exposed in the Assured Imaging breach?▾
The May 2020 ransomware attack exposed names, contact information, dates of birth, diagnoses and conditions, lab results, medications, and treatment information of 244,813 individuals, highly sensitive clinical data that significantly increases the harm potential to affected patients.
Why does failing to notify on time make a HIPAA situation worse?▾
Late breach notification is treated as a separate, independent HIPAA violation, what OCR calls a stackable violation. This means a covered entity already facing penalties for a breach can face additional penalties specifically for the notification delay, increasing total exposure significantly.
What does 'never conducted a risk analysis' mean in practice?▾
It means that at no point in the organization's operation as a covered entity had it performed the documented assessment of threats and vulnerabilities to ePHI required by 45 CFR §164.308(a)(1). This is the most serious finding OCR makes, it indicates systemic non-compliance rather than a gap in an otherwise functioning program.
Can a covered entity reduce its penalty by cooperating with OCR?▾
Yes. Informal resolution, where the entity agrees to settle rather than contest the findings, typically results in a reduced penalty. All four entities in the April 2026 ransomware settlements accepted reduced penalties in exchange for agreeing to corrective action plans.

Not legal advice. medcomply.ai provides compliance intelligence for educational and operational planning. Consult qualified counsel for legal interpretation.