Breach filing
ArchivedAssured Imaging: 244,813 individuals, Aug 2020.
Assured Imaging reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 27 August 2020. The filing records the organisation as a healthcare provider in Arizona and lists 244,813 individuals affected, which makes it the 13th largest of the 164 Arizona filings on the register and the 31st largest of the 663 filings submitted nationally in 2020. Among the 12 Arizona filings made in 2020 it ranks 3rd.
Individuals affected
244,813
As reported to HHS
Modelled cost (IBM 2025)
$39.2M
Upper bound, method shown
Rank in AZ
13th
of 164 Arizona filings
Rank in 2020
31st
of 663 filings nationally
Section F.1 / The filing
As posted by HHS OCR
Every value below is the portal's own field for this filing, plus its rank within the register.
- Covered entity type
- Healthcare Provider
- Individuals affected
- 244,813
- Breach submission date
- 27 August 2020
- Submission year
- 2020
- Type of breach
- Hacking/IT Incident
- Location of breached information
- Network Server
- Business associate present
- No
- State
- Arizona (AZ)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in Arizona by size
- 13th of 164
- Rank in 2020 nationally
- 31st of 663
- Arizona median filing
- 3,146 individuals
- Register id (derived)
- AZ-20200827-assured-imaging
Section F.2 / In context
Where this filing sits in Arizona and in 2020
OCR classifies the incident as a hacking or IT incident, with the breached information held in a network server. Hacking/IT Incident is the type recorded on 94 of the 164 Arizona filings (57%) and on 69% of all filings submitted in 2020. Network Server appears on 43% of Arizona filings.
No business associate is recorded on the filing; 21% of Arizona filings do involve one. At 244,813 individuals the breach is 78 times the Arizona median filing of 3,146 and 61 times the national median of 4,000 across all 7,884 filings. It is one of 801 filings of 100,000 or more individuals.
As of 28 August 2026 the case is listed in the HHS OCR breach portal archive. OCR's closing summary of the case is reproduced in full below.
Arizona's breach notification statute (A.R.S. 18-551, 18-552) requires notice to affected residents within 45 days after determining a breach occurred. Its attorney general threshold: more than 1,000 Arizona residents (AG and Dept. of Homeland Security). The HIPAA Breach Notification Rule ran alongside it: notice to affected individuals and to HHS without unreasonable delay and no later than 60 days after discovery, which is the clock that put this filing on the portal.
Multiplying 244,813 individuals by IBM's $160 customer-PII cost per record (Cost of a Data Breach 2025, the figure the site's calculator uses) gives a modelled $39.2M; the 2026 edition's $192 gives $47.0M. Both are modelled estimates with the method shown, not costs disclosed by Assured Imaging. Because the filing is above the roughly 100,000-record range in which the per-record figure is reliable, the result is an upper bound, not an estimate: fixed costs are spread across far more records at this scale.
Section F.3 / OCR closing summary
The portal's archived description, in full
Written by the Office for Civil Rights when the case was closed and reproduced verbatim from the HHS export.
Today, the U.S. Department of Health and Human Services (HHS), Office for Civil Rights (OCR) announced a settlement with Assured Imaging ("Assured") on behalf of Assured Imaging Affiliated Covered Entities, a medical imaging and screening service provider, concerning a potential violation of the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Security Rule. Assured is a covered entity that provides services in Arizona, California, Georgia, , New Mexico, Nevada, New York, New Jersey, Pennsylvania, Texas, Oregon, and Washington .
The settlement resolves an investigation that OCR initiated after receiving a breach report that Assured filed on August 27, 2020. Assured reported that on May 19, 2020, Assured discovered that a server on its network was infected with ransomware, impacting the PHI of over 244,000 patients. Affected PHI included patient names, addresses, dates of birth, diagnosis and conditions, lab results, medications, and treatment information. OCR's investigation determined that Assured had impermissibly disclosed PHI, failed to conduct an accurate and thorough risk analysis to determine the potential risks and vulnerabilities to the confidentiality, integrity, and availability of its ePHI, and failed to timely notify affected individuals of the breach.
Under the terms of the resolution agreement, Assured agreed to implement a corrective action plan that will be monitored by OCR for two years and paid $375,000 to OCR. Under the corrective action plan, Assured has committed to take steps to ensure compliance with the HIPAA Security Rule and protect the security of ePHI, including:
• Conduct an accurate and thorough risk analysis to determine the potential risks and vulnerabilities to the confidentiality, integrity, and availability of its ePHI;
• Develop and implement a risk management plan to address and mitigate security risks and vulnerabilities identified in its risk analysis to a reasonable and appropriate level;
• Develop, maintain, and revise, as necessary, written policies and procedures to comply with the HIPAA Privacy, Security and Breach Notification Rules; and
• Provide annual training for all workforce members with access to ePHI.
OCR recommends that health care providers, health plans, health care clearinghouses, and business associates that are covered by HIPAA take the following steps to mitigate or prevent cyber-threats:
• Identify where ePHI is located in the organization, including how ePHI enters, flows through, and leaves the organization's information systems.
• Periodically conduct, and update as needed, a risk analysis and develop and implement a risk management plan to address identified risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI.
• Ensure audit controls are in place to record and examine information system activity.
• Implement regular review of information system activity.
• Utilize mechanisms to authenticate information to ensure only authorized users are accessing ePHI.
• Encrypt ePHI in transit and at rest to guard against unauthorized access to ePHI when appropriate.
• Incorporate lessons learned from incidents into the organization's overall security management process.
• Provide workforce members with regular HIPAA training that is specific to the organization and to the workforce members' respective job duties.
Section F.5 / Modelled cost
244,813 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
Upper boundIBM 2025 customer PII, $160 per record
$39.2M
244,813 x $160
IBM 2026 customer PII, $192 per record
$47.0M
244,813 x $192
Method: individuals affected, as reported by Assured Imaging to HHS, multiplied by IBM's customer-PII cost per record (Cost of a Data Breach 2025 Figure 6 and the 2026 edition). No cost has been disclosed by the entity for this filing; the figure is a planning estimate, not a fact about the breach. IBM's per-record figures come from mid-volume breaches and IBM cautions against applying them to breaches involving millions of records; the site's per-record page explains where the multiplication holds and where it breaks down.
Context: IBM's average cost of a healthcare breach is $6.64M in the 2026 report ($7.42M in 2025); the global average across all sectors was $4.44M in 2025.
Cost per record: method and limits / Healthcare breach cost, IBM 2026
Section F.6 / Notification clock
Arizona statute and the HIPAA rule
State notification statute
Arizona: A.R.S. 18-551, 18-552
- Notice to individuals
- Within 45 days after determining a breach occurred
- Attorney general threshold
- More than 1,000 Arizona residents (AG and Dept. of Homeland Security) (Within the same 45-day window)
- Private right of action
- No: Only the Arizona Attorney General may enforce
- Penalty
- Up to $10,000 per affected individual, capped at $500,000 per breach, under the Consumer Fraud Act
The HIPAA Breach Notification Rule runs alongside the state statute: notice to affected individuals and to HHS without unreasonable delay and no later than 60 days after discovery.
Section F.7 / Peer filings
Arizona filings closest in size
Neighbours by size rank among Arizona filings in 2020, topped up from other years where 2020 has too few. Filings of 10,000 or more link to their own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| Magellan Health Inc. | Health Plan | 1,013,956 | 12 Jun 2020 | |||
| Magellan Rx Management | Business Associate | 314,704 | 12 Jun 2020 | |||
| GenRx Pharmacy | Healthcare Provider | 137,110 | 18 Dec 2020 | |||
| Arizona Endocrinology Center | Healthcare Provider | 74,122 | 10 Apr 2020 |
Index / Companion schedules
13 HHS breach register
→Hub: every filing, by state, year and entity.
04 Biggest breaches
→Mega-breaches with primary-source cost figures.
Industry / Healthcare
→IBM 2026: $6.64M average, 13 years at #1.
Regulation / HIPAA penalties
→OCR enforcement tiers and the 60-day rule.
11 50-state laws
→Deadline, AG threshold and penalties per state.
Cost / Per record
→Where the per-record model is reliable.
Provenance
Source: U.S. Department of Health and Human Services, Office for Civil Rights, Breach Portal (breaches affecting 500 or more individuals), retrieved 2026-08-28. Public domain. Individuals affected and dates as reported by the covered entity.
Portal: ocrportal.hhs.gov breach report. Statutory basis: HITECH Act section 13402(e)(4): the Secretary must post a list of breaches of unsecured protected health information affecting 500 or more individuals. Breaches affecting fewer than 500 individuals are reported to OCR annually and are not posted, so they are not on this register. Status wording follows the portal's two tabs ("Cases Currently Under Investigation" and "Archive") as of 28 August 2026; a filing moves to the archive when OCR closes the case. Modelled costs on this site are a method applied to the reported count, using IBM Cost of a Data Breach per-record figures, and are never a cost disclosed by the entity. This row: hhs-breach-archive__2026-08-28.csv, export row 3769.
Corrections: if you represent a listed entity and the portal row has been amended, email [email protected] with the portal entry and we will re-pull the export.