Community Connections: 18,949 individuals, Dec 2024.

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 12 of the 33 District of Columbia filings (36%) and on 83% of all filings submitted in 2024. Network Server appears on 36% of District of Columbia filings.

No business associate is recorded on the filing; 27% of District of Columbia filings do involve one. At 18,949 individuals the breach is 7.8 times the District of Columbia median filing of 2,416 and 4.7 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 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.

District of Columbia's breach notification statute (D.C. Code 28-3851 et seq.) requires notice to affected residents in the most expedient time possible and without unreasonable delay. Its attorney general threshold: 50 or more District 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 18,949 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 $3.03M; the 2026 edition's $192 gives $3.64M. Both are modelled estimates with the method shown, not costs disclosed by Community Connections. For scale, IBM's 2026 average cost of a healthcare breach is $6.64M, so this filing models at 0.5 times the sector average.