Breach filing
ArchivedMidwest Orthopedic Pain and Spine: 29,153 individuals, Jul 2016.
Midwest Orthopedic Pain and Spine reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 26 July 2016. The filing records the organisation as a healthcare provider in Missouri and lists 29,153 individuals affected, which makes it the 35th largest of the 164 Missouri filings on the register and the 36th largest of the 328 filings submitted nationally in 2016. Among the 7 Missouri filings made in 2016 it ranks 2nd.
Individuals affected
29,153
As reported to HHS
Modelled cost (IBM 2025)
$4.66M
Method shown, not disclosed
Rank in MO
35th
of 164 Missouri filings
Rank in 2016
36th
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
- 29,153
- Breach submission date
- 26 July 2016
- Submission year
- 2016
- Type of breach
- Hacking/IT Incident
- Location of breached information
- Network Server
- Business associate present
- No
- State
- Missouri (MO)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in Missouri by size
- 35th of 164
- Rank in 2016 nationally
- 36th of 328
- Missouri median filing
- 4,800 individuals
- Register id (derived)
- MO-20160726-midwest-orthopedic-pain-and-spine
Section F.2 / In context
Where this filing sits in Missouri 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 100 of the 164 Missouri filings (61%) and on 35% of all filings submitted in 2016. Network Server appears on 38% of Missouri filings.
No business associate is recorded on the filing; 23% of Missouri filings do involve one. At 29,153 individuals the breach is 6.1 times the Missouri median filing of 4,800 and 7.3 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.
Missouri's breach notification statute (Mo. Rev. Stat. 407.1500) requires notice to affected residents without unreasonable delay. Its attorney general threshold: more than 1,000 Missouri consumers. 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 29,153 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 $4.66M; the 2026 edition's $192 gives $5.60M. Both are modelled estimates with the method shown, not costs disclosed by Midwest Orthopedic Pain and Spine. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 0.8 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), Midwest Orthopedic, reported that it learned of a breach when notified by the Federal Bureau of Investigation (FBI) on May 27, 2016. Based on the information provided by the FBI the CE believes that the weakness or vulnerability that lead to the breach may have been a third party company that had access to the database for patient record transferring purposes. This breach affected the protected health information (PHI) of 29,153 individuals and included names, addresses, dates of birth, social security numbers, driver's license numbers and clinical information. The CE provided breach notification to HHS, affected individuals, and the media.
To resolve the issues raised in this matter, the CE changed the companies it uses for information technology, billing and electronic medical records. The new information technology company implemented new internet firewalls and began continuous monitoring of the CE's computer server for unauthorized access to electronic PHI and malware. The CE also retrained staff on HIPAA. OCR obtained documented assurances that the CE implemented the corrective action steps listed above..
Section F.5 / Modelled cost
29,153 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
ModelledIBM 2025 customer PII, $160 per record
$4.66M
29,153 x $160
IBM 2026 customer PII, $192 per record
$5.60M
29,153 x $192
Method: individuals affected, as reported by Midwest Orthopedic Pain and Spine 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
Missouri statute and the HIPAA rule
State notification statute
Missouri: Mo. Rev. Stat. 407.1500
- Notice to individuals
- Without unreasonable delay
- Attorney general threshold
- More than 1,000 Missouri consumers (Without unreasonable delay)
- Private right of action
- No: AG has exclusive enforcement authority
- Penalty
- Up to $150,000 per breach (or series) for willful and knowing 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
Missouri filings closest in size
Neighbours by size rank among Missouri 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 |
|---|---|---|---|---|---|---|
| Laser & Dermatologic Surgery Center | Healthcare Provider | 31,000 | 14 Jun 2016 | |||
| Prosthetic & Orthotic Care, Inc. | Healthcare Provider | 23,015 | 7 Aug 2016 | |||
| Burrell Behavioral Health | Healthcare Provider | 7,748 | 2 Sep 2016 |
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 5511.
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.