Form: Cost-of-Breach DisclosureSource: IBM Cost of a Data BreachFiled: 28 Apr 2026
DataBreachCost.comOpen calc
Independent breach-cost research, read by security and risk leaders.Sponsor this site →
Filing CO-20140422-centura-healthHHS OCR Breach Register, Colorado

Breach filing

Archived

Centura Health: 12,286 individuals, Apr 2014.

Centura Health reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 22 April 2014. The filing records the organisation as a healthcare provider in Colorado and lists 12,286 individuals affected, which makes it the 46th largest of the 139 Colorado filings on the register and the 64th largest of the 314 filings submitted nationally in 2014. Among the 8 Colorado filings made in 2014 it ranks 2nd.

Individuals affected

12,286

As reported to HHS

Modelled cost (IBM 2025)

$1.97M

Method shown, not disclosed

Rank in CO

46th

of 139 Colorado filings

Rank in 2014

64th

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
12,286
Breach submission date
22 April 2014
Submission year
2014
Type of breach
Hacking/IT Incident
Location of breached information
Email
Business associate present
No
Portal status
listed in the HHS OCR breach portal archive
Rank in Colorado by size
46th of 139
Rank in 2014 nationally
64th of 314
Colorado median filing
3,845 individuals
Register id (derived)
CO-20140422-centura-health

Section F.2 / In context

Where this filing sits in Colorado and in 2014

OCR classifies the incident as a hacking or IT incident, with the breached information held in email. Hacking/IT Incident is the type recorded on 83 of the 139 Colorado filings (60%) and on 12% of all filings submitted in 2014. Email appears on 24% of Colorado filings.

No business associate is recorded on the filing; 24% of Colorado filings do involve one. At 12,286 individuals the breach is 3.2 times the Colorado median filing of 3,845 and 3.1 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.

Colorado's breach notification statute (C.R.S. 6-1-716) requires notice to affected residents within 30 days of determining a breach occurred. Its attorney general threshold: 500 or more Colorado residents. 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 12,286 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 $1.97M; the 2026 edition's $192 gives $2.36M. Both are modelled estimates with the method shown, not costs disclosed by Centura Health. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 0.4 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.

OCR initiated an investigation after the covered entity (CE), Centura Health, reported that it experienced a phishing attack. Because a few of its employees inadvertently responded to the fraudulent email by clicking on a link and providing their usernames and passwords, these employees' email accounts may have been accessible to the attacker(s). The CE detected and contained the incident because less than 5% of its employees received the phishing email. The compromised email accounts resulted in a breach of 12,286 individuals' electronic protected health information (ePHI) in the form of demographic (names, addresses, dates of birth, telephone numbers, social security numbers, other identifiers), clinical (diagnoses, lab results, medications, other treatment) and/or financial (claims) information. The CE provided breach notification to HHS, affected individuals, and the media. The CE also notified the Federal Bureau of Investigation and offered free credit monitoring services to the individuals who had their social security number or financial information potentially compromised. Following the breach, the CE updated its risk management plan which included escalating in priority its implementation of certain previously identified security measures; retrained all its employees, and enhanced its annual compliance education training to provide additional content regarding phishing scams. OCR obtained assurance that the CE implemented the corrective actions noted above.

Section F.5 / Modelled cost

12,286 individuals through IBM's per-record figures

Modelled cost / method shown, not a disclosed cost

Modelled

IBM 2025 customer PII, $160 per record

$1.97M

12,286 x $160

IBM 2026 customer PII, $192 per record

$2.36M

12,286 x $192

Method: individuals affected, as reported by Centura Health 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

Colorado statute and the HIPAA rule

State notification statute

Colorado: C.R.S. 6-1-716

Notice to individuals
Within 30 days of determining a breach occurred
Attorney general threshold
500 or more Colorado residents (Within the same 30-day window)
Private right of action
No: Only the Colorado Attorney General may enforce
Penalty
Treated as a deceptive trade practice; up to $20,000 per violation with no aggregate cap

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

Colorado filings closest in size

Neighbours by size rank among Colorado 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 entityTypeIndividualsSubmitted
Colorado Department of Health Care Policy & FinancingHealth Plan15,38010 Oct 2014
Kaiser Foundation Health Plan of ColoradoHealth Plan11,55112 Aug 2014
Valley View Hospital AssociationHealthcare Provider5,41514 Mar 2014

Index / Companion schedules

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 6149.

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.