Breach filing
ArchivedAlliance Health Networks, LLC: 42,372 individuals, Feb 2016.
Alliance Health Networks, LLC reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 15 February 2016. The filing records the organisation as a healthcare provider in Utah and lists 42,372 individuals affected, which makes it the 11th largest of the 68 Utah filings on the register and the 27th largest of the 328 filings submitted nationally in 2016. It was the only Utah filing in 2016.
Individuals affected
42,372
As reported to HHS
Modelled cost (IBM 2025)
$6.78M
Method shown, not disclosed
Rank in UT
11th
of 68 Utah filings
Rank in 2016
27th
of 328 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
- 42,372
- Breach submission date
- 15 February 2016
- Submission year
- 2016
- Type of breach
- Hacking/IT Incident
- Location of breached information
- Network Server
- Business associate present
- No
- State
- Utah (UT)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in Utah by size
- 11th of 68
- Rank in 2016 nationally
- 27th of 328
- Utah median filing
- 5,381 individuals
- Register id (derived)
- UT-20160215-alliance-health-networks
Section F.2 / In context
Where this filing sits in Utah and in 2016
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 51 of the 68 Utah filings (75%) and on 35% of all filings submitted in 2016. Network Server is the most common location in the state, appearing on 57% of Utah filings.
No business associate is recorded on the filing; 34% of Utah filings do involve one. At 42,372 individuals the breach is 7.9 times the Utah median filing of 5,381 and 11 times the national median of 4,000 across all 7,884 filings. It sits in the 10,000 to 99,999 band, which holds 1,938 filings.
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.
Utah's breach notification statute (Utah Code 13-44-202) requires notice to affected residents in the most expedient time possible, without unreasonable delay. Its attorney general threshold: 500 or more Utah residents (AG and Utah Cyber Center). 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 42,372 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 $6.78M; the 2026 edition's $192 gives $8.14M. Both are modelled estimates with the method shown, not costs disclosed by Alliance Health Networks, LLC. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 1.2 times the sector average.
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.
On December 17, 2015, the covered entity (CE), Alliance Health Networks, LLC., discovered that a test database containing protected health information (PHI) was accessible to the public via the Internet. The breach affected approximately 42,372 individuals, and their unsecured PHI included names, addresses, telephone numbers, email addresses, medications, and some clinical information. The CE provided breach notification to affected individuals, the media, and HHS. The CE also mitigated the effects of the breach by immediately securing the database, implementing monitoring of its test databases, performing weekly vulnerability scans of its systems, and updating its policies to ensure that production data is not used in test databases. In resolving the breach, OCR provided the CE with technical assistance regarding necessary changes to its policies and procedures, as well its risk management process.
Section F.5 / Modelled cost
42,372 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
ModelledIBM 2025 customer PII, $160 per record
$6.78M
42,372 x $160
IBM 2026 customer PII, $192 per record
$8.14M
42,372 x $192
Method: individuals affected, as reported by Alliance Health Networks, LLC 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
Utah statute and the HIPAA rule
State notification statute
Utah: Utah Code 13-44-202
Protection of Personal Information Act
- Notice to individuals
- In the most expedient time possible, without unreasonable delay
- Attorney general threshold
- 500 or more Utah residents (AG and Utah Cyber Center) (Without unreasonable delay)
- Private right of action
- No: No PROA; only the Attorney General can enforce
- Penalty
- Up to $2,500 per consumer, capped at $100,000 aggregate for related violations
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
Utah filings closest in size
Neighbours by size rank among Utah filings in 2016, topped up from other years where 2016 has too few. Filings of 10,000 or more link to their own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| Uintah Basin Healthcare | Healthcare Provider | 103,974 | 10 May 2023 | |||
| Valley Obstetrics & Gynecology PC | Healthcare Provider | 61,327 | 9 Jun 2023 | |||
| Rocky Mountain Associated Physicians, P.C.Open | Healthcare Provider | 50,640 | 3 Apr 2026 | |||
| MedQuest Pharmacy, Inc. | Healthcare Provider | 39,447 | 23 Dec 2021 | |||
| Central Utah Clinic | Healthcare Provider | 31,677 | 7 Aug 2014 |
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 5659.
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.