Breach filing
ArchivedManaged Health Services: 31,300 individuals, Jan 2019.
Managed Health Services reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 3 January 2019. The filing records the organisation as a health plan in Indiana and lists 31,300 individuals affected, which makes it the 38th largest of the 200 Indiana filings on the register and the 81st largest of the 511 filings submitted nationally in 2019. Among the 13 Indiana filings made in 2019 it ranks 5th. Managed Health Services submitted 1 further report on the same day (576 individuals); this page covers the largest and lists the others below.
Individuals affected
31,300
As reported to HHS
Modelled cost (IBM 2025)
$5.01M
Method shown, not disclosed
Rank in IN
38th
of 200 Indiana filings
Rank in 2019
81st
of 511 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
- Health Plan
- Individuals affected
- 31,300
- Breach submission date
- 3 January 2019
- Submission year
- 2019
- Type of breach
- Hacking/IT Incident
- Location of breached information
- Business associate present
- Yes
- State
- Indiana (IN)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in Indiana by size
- 38th of 200
- Rank in 2019 nationally
- 81st of 511
- Indiana median filing
- 3,600 individuals
- Register id (derived)
- IN-20190103-managed-health-services
Section F.2 / In context
Where this filing sits in Indiana and in 2019
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 119 of the 200 Indiana filings (60%) and on 61% of all filings submitted in 2019. Email appears on 25% of Indiana filings.
A business associate is recorded as present on the filing, as it is on 31% of Indiana filings. At 31,300 individuals the breach is 8.7 times the Indiana median filing of 3,600 and 7.8 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.
Indiana's breach notification statute (Ind. Code 24-4.9) requires notice to affected residents without unreasonable delay, no more than 45 days after discovery. Its attorney general threshold: all qualifying breaches. 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,300 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.01M; the 2026 edition's $192 gives $6.01M. Both are modelled estimates with the method shown, not costs disclosed by Managed Health Services. 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.
The covered entity (CE), Managed Health Services, reported that employees of its business associate (BA) were the victims of an email phishing attack affecting the protected health information (PHI) of 31,300 individuals. The PHI involved included names, dates of birth, addresses, diagnoses, and other identifiers. The CE notified HHS, affected individuals, the media, and provided substitute notice. In response to the breach, the CE provided complimentary credit monitoring services and the BA implemented additional administrative, technical, and security safeguards.
Section F.4 / Same-day filings
1 further report by Managed Health Services on 3 January 2019
Separate rows on the HHS portal with their own counts; this page covers the largest and lists the rest here rather than giving each its own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| Managed Health Services | Health Plan | 576 | 3 Jan 2019 |
Section F.5 / Modelled cost
31,300 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
ModelledIBM 2025 customer PII, $160 per record
$5.01M
31,300 x $160
IBM 2026 customer PII, $192 per record
$6.01M
31,300 x $192
Method: individuals affected, as reported by Managed Health Services 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
Indiana statute and the HIPAA rule
State notification statute
Indiana: Ind. Code 24-4.9
- Notice to individuals
- Without unreasonable delay, no more than 45 days after discovery
- Attorney general threshold
- All qualifying breaches (Within the 45-day consumer notification window)
- Private right of action
- No: Enforced exclusively by the Indiana Attorney General
- Penalty
- Up to $150,000 per deceptive act, plus investigation costs
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
Indiana filings closest in size
Neighbours by size rank among Indiana filings in 2019, topped up from other years where 2019 has too few. Filings of 10,000 or more link to their own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| Select Health Network | Business Associate | 56,790 | 13 Nov 2019 | |||
| LCP Transportation, Inc | Business Associate | 54,528 | 15 Mar 2019 | |||
| Valley Professionals Community Health Center | Healthcare Provider | 12,029 | 25 Jan 2019 | |||
| Goshen Health | Healthcare Provider | 9,160 | 30 Sep 2019 |
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 4624.
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.