Breach filing
ArchivedLifeBridge Community Gastroenterology, LLC dba Woodholme Gastroenterology: 66,342 individuals, Apr 2021.
LifeBridge Community Gastroenterology, LLC dba Woodholme Gastroenterology reported a breach of unsecured protected health information to the HHS Office for Civil Rights on 30 April 2021. The filing records the organisation as a healthcare provider in Maryland and lists 66,342 individuals affected, which makes it the 26th largest of the 170 Maryland filings on the register and the 109th largest of the 715 filings submitted nationally in 2021. Among the 15 Maryland filings made in 2021 it ranks 3rd.
Individuals affected
66,342
As reported to HHS
Modelled cost (IBM 2025)
$10.6M
Method shown, not disclosed
Rank in MD
26th
of 170 Maryland filings
Rank in 2021
109th
of 715 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
- 66,342
- Breach submission date
- 30 April 2021
- Submission year
- 2021
- Type of breach
- Hacking/IT Incident
- Location of breached information
- Network Server
- Business associate present
- No
- State
- Maryland (MD)
- Portal status
- listed in the HHS OCR breach portal archive
- Rank in Maryland by size
- 26th of 170
- Rank in 2021 nationally
- 109th of 715
- Maryland median filing
- 4,792 individuals
- Register id (derived)
- MD-20210430-lifebridge-community-gastroenterology-db
Section F.2 / In context
Where this filing sits in Maryland and in 2021
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 117 of the 170 Maryland filings (69%) and on 76% of all filings submitted in 2021. Network Server appears on 45% of Maryland filings.
No business associate is recorded on the filing; 38% of Maryland filings do involve one. At 66,342 individuals the breach is 14 times the Maryland median filing of 4,792 and 17 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.
Maryland's breach notification statute (Md. Code, Com. Law 14-3504) requires notice to affected residents within 45 days after discovery or notification of the breach. Its attorney general threshold: all breaches (AG notified before individual notices are sent). 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 66,342 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 $10.6M; the 2026 edition's $192 gives $12.7M. Both are modelled estimates with the method shown, not costs disclosed by LifeBridge Community Gastroenterology, LLC dba Woodholme Gastroenterology. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 1.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), LifeBridge Community Gastroenterology dba Woodholme Gastroenterology, reported that it experienced a cyber-attack that compromised the protected health information (PHI) of approximately 66,342 individuals. The PHI involved included names, mailing addresses, email addresses, dates of birth, patient identification numbers, diagnoses, Social Security numbers, drivers' license numbers, and health insurance and other treatment information. The CE notified HHS, affected individuals, the media, and provided substitute notice. In its mitigation efforts, the CE implemented additional administrative, technical, and security safeguards to better protect its PHI.
Section F.5 / Modelled cost
66,342 individuals through IBM's per-record figures
Modelled cost / method shown, not a disclosed cost
ModelledIBM 2025 customer PII, $160 per record
$10.6M
66,342 x $160
IBM 2026 customer PII, $192 per record
$12.7M
66,342 x $192
Method: individuals affected, as reported by LifeBridge Community Gastroenterology, LLC dba Woodholme Gastroenterology 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
Maryland statute and the HIPAA rule
State notification statute
Maryland: Md. Code, Com. Law 14-3504
- Notice to individuals
- Within 45 days after discovery or notification of the breach
- Attorney general threshold
- All breaches (AG notified before individual notices are sent) (Before individual notifications are sent)
- Private right of action
- No: No PROA under the breach statute; AG enforcement only
- Penalty
- Unfair or deceptive trade practice; up to $10,000 per violation, $25,000 per repeat violation
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
Maryland filings closest in size
Neighbours by size rank among Maryland filings in 2021, topped up from other years where 2021 has too few. Filings of 10,000 or more link to their own page.
| Covered entity | Type | Individuals | Submitted | Breach type | Location | BA |
|---|---|---|---|---|---|---|
| Luminis Health Anne Arundel Medical Center | Healthcare Provider | 824,450 | 2 Nov 2021 | |||
| The Centers for Advanced Orthopaedics | Healthcare Provider | 125,291 | 25 Mar 2021 | |||
| Maxim Healthcare Group | Healthcare Provider | 65,267 | 4 Nov 2021 | |||
| University of Maryland, Baltimore | Business Associate | 37,263 | 2 Jul 2021 |
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 3225.
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.