Centers for Medicare & Medicaid Services: 107,154 individuals, Jun 2025.

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 81% of all filings submitted in 2025. Network Server appears on 45% of Maryland filings.

No business associate is recorded on the filing; 38% of Maryland filings do involve one. At 107,154 individuals the breach is 22 times the Maryland median filing of 4,792 and 27 times the national median of 4,000 across all 7,884 filings. It is one of 801 filings of 100,000 or more individuals.

As of 28 August 2026 the case is listed by HHS OCR under Cases Currently Under Investigation. OCR has not published a closing summary, so this page is limited to the fields on the filing itself; the archive entry that follows a closed investigation usually adds a short account of what was exposed and what the entity did afterwards.

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 107,154 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 $17.1M; the 2026 edition's $192 gives $20.6M. Both are modelled estimates with the method shown, not costs disclosed by Centers for Medicare & Medicaid Services. 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.