Breach filing
ArchivedNorth Broward Hospital District d/b/a Broward Health: 1,351,431 individuals, Jan 2022.
North Broward Hospital District d/b/a Broward Health reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 2 January 2022. The filing records the organisation as a healthcare provider in Florida and lists 1,351,431 individuals affected, which makes it the 13th largest of the 463 Florida filings on the register and the 11th largest of the 718 filings submitted nationally in 2022. Among the 40 Florida filings made in 2022 it ranks 2nd.
Individuals affected
1,351,431
As reported to HHS
Modelled cost (IBM 2025)
$216M
Upper bound, method shown
Rank in FL
13th
of 463 Florida filings
Rank in 2022
11th
of 718 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
- 1,351,431
- Breach submission date
- 2 January 2022
- Submission year
- 2022
- Type of breach
- Hacking/IT Incident
- Location of breached information
- Network Server
- Business associate present
- No
- State
- Florida (FL)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in Florida by size
- 13th of 463
- Rank in 2022 nationally
- 11th of 718
- Florida median filing
- 4,912 individuals
- Register id (derived)
- FL-20220102-north-broward-hospital-district-d-b-a-br
Section F.2 / In context
Where this filing sits in Florida and in 2022
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 256 of the 463 Florida filings (55%) and on 79% of all filings submitted in 2022. Network Server appears on 45% of Florida filings.
No business associate is recorded on the filing; 25% of Florida filings do involve one. At 1,351,431 individuals the breach is 275 times the Florida median filing of 4,912 and 338 times the national median of 4,000 across all 7,884 filings. It is one of 149 filings on the register of one million or more individuals.
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.
Florida's breach notification statute (Fla. Stat. 501.171) requires notice to affected residents within 30 days of determining a breach occurred (up to 15-day extension for good cause). Its attorney general threshold: 500 or more Florida 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 1,351,431 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 $216M; the 2026 edition's $192 gives $259M. Both are modelled estimates with the method shown, not costs disclosed by North Broward Hospital District d/b/a Broward Health. Because the filing is above the roughly 100,000-record range in which the per-record figure is reliable, the result is an upper bound, not an estimate: fixed costs are spread across far more records at this scale.
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), North Broward Hospital District dba Broward Health, reported that it experienced a cyber-attack that compromised the protected health information (PHI) of 1,351,432 individuals. The PHI involved included names, addresses, telephone numbers, financial information, Social Security and drivers' license numbers, health insurance information, diagnoses, medical record numbers, and email addresses. The CE notified HHS, affected individuals, the media, and posted substitute notice on its website. In response to the breach, the CE reset all passwords, implemented additional technical safeguards, and offered complimentary credit monitoring services to affected individuals.
Section F.5 / Modelled cost
1,351,431 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
Upper boundIBM 2025 customer PII, $160 per record
$216M
1,351,431 x $160
IBM 2026 customer PII, $192 per record
$259M
1,351,431 x $192
Method: individuals affected, as reported by North Broward Hospital District d/b/a Broward 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
Florida statute and the HIPAA rule
State notification statute
Florida: Fla. Stat. 501.171
Florida Information Protection Act (FIPA)
- Notice to individuals
- Within 30 days of determining a breach occurred (up to 15-day extension for good cause)
- Attorney general threshold
- 500 or more Florida residents (Within 30 days of the breach determination)
- Private right of action
- No: FIPA does not permit direct individual lawsuits; AG enforcement only
- Penalty
- Escalating civil penalties up to $500,000 per breach; also an unfair or deceptive trade practice
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
Florida filings closest in size
Neighbours by size rank among Florida filings in 2022, topped up from other years where 2022 has too few. Filings of 10,000 or more link to their own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| Independent Living Systems, LLC | Business Associate | 4,226,508 | 2 Sep 2022 | |||
| Synergic Healthcare Solutions, LLC d/b/a Fast Track Urgent Care Center | Healthcare Provider | 258,411 | 12 Jul 2022 | |||
| Comprehensive Health Services | Healthcare Provider | 106,752 | 15 Feb 2022 |
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 2737.
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.