Breach filing
ArchivedCentral Utah Clinic: 31,677 individuals, Aug 2014.
Central Utah Clinic reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 7 August 2014. The filing records the organisation as a healthcare provider in Utah and lists 31,677 individuals affected, which makes it the 13th largest of the 68 Utah filings on the register and the 39th largest of the 314 filings submitted nationally in 2014. Among the 5 Utah filings made in 2014 it ranks 1st.
Individuals affected
31,677
As reported to HHS
Modelled cost (IBM 2025)
$5.07M
Method shown, not disclosed
Rank in UT
13th
of 68 Utah filings
Rank in 2014
39th
of 314 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
- 31,677
- Breach submission date
- 7 August 2014
- Submission year
- 2014
- 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
- 13th of 68
- Rank in 2014 nationally
- 39th of 314
- Utah median filing
- 5,381 individuals
- Register id (derived)
- UT-20140807-central-utah-clinic
Section F.2 / In context
Where this filing sits in Utah and in 2014
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 12% of all filings submitted in 2014. 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 31,677 individuals the breach is 5.9 times the Utah median filing of 5,381 and 7.9 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 31,677 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 $5.07M; the 2026 edition's $192 gives $6.08M. Both are modelled estimates with the method shown, not costs disclosed by Central Utah Clinic. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 0.9 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 June 9, 2014, Revere Health, the covered entity (CE), discovered that cybercriminals had compromised one of its Internet-facing servers containing electronic protected health information (ePHI), affecting 31,677 patients. The compromised ePHI which included images, written imaging notes, and radiology reports dating 2010 and earlier, which contained identifying patient information - names, and/or dates of birth, and/or social security numbers, and/or addresses, and/or telephone numbers. The CE provided breach notification to the affected individuals, the media, and HHS. Following the breach, the CE took several corrective actions, including but not limited to: updating its inventory of ePHI, servers, databases, users, and applications; reducing vulnerabilities and blocking the affected server from the Internet; conducting penetration tests; drafting new security policies; implementing new response procedures; updating patch management procedures; upgrading the functionality in its firewalls, antivirus, and antimalware software; expanding its security team; and providing security and awareness training to its workforce. In the course of its review, OCR provided the CE with technical assistance regarding necessary changes to its policies and procedures, and its security management process.
Section F.5 / Modelled cost
31,677 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
ModelledIBM 2025 customer PII, $160 per record
$5.07M
31,677 x $160
IBM 2026 customer PII, $192 per record
$6.08M
31,677 x $192
Method: individuals affected, as reported by Central Utah Clinic 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 2014, topped up from other years where 2014 has too few. Filings of 10,000 or more link to their own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| Alliance Health Networks, LLC | Healthcare Provider | 42,372 | 15 Feb 2016 | |||
| MedQuest Pharmacy, Inc. | Healthcare Provider | 39,447 | 23 Dec 2021 | |||
| Intermountain Healthcare | Healthcare Provider | 28,628 | 16 Jul 2021 | |||
| Sorenson Communications/CaptionCall Group Health Plan | Health Plan | 9,800 | 24 Apr 2014 | |||
| Myriad Genetic Laboratories, Inc. | Healthcare Provider | 643 | 29 Mar 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 6068.
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.