Confirmed breach. Intrusion Oct 3, 2015, discovered Oct 3, 2015 — the first regulatory filing landed 153 days later (flagged late). 2,213,597 individuals reported across the linked filings.
21st Century Oncology, a health sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2015-11-13 and filed notice on 2016-03-04. 2,802 Washington residents were affected. 112 days elapsed between awareness and notification. 41 days to identify the breach.
Affected (this filing): 2,802
🐻California State AGlinked via multistate filing link · 100%
21st Century Oncology notified California AG in 2016 regarding a 2015 breach. An unauthorized third party accessed a database containing patient names, SSNs, diagnoses, and insurance info starting Oct 3, 2015. FBI advised on Nov 13, 2015. Notification was delayed per FBI request. Affected individuals received one year of Experian ProtectMyID.
CA 60-day late · 237d
🇺🇸FLHHS OCRlinked via same-victim cross-source · 100%
21st Century Oncology, Inc. reported to HHS on 2016-03-04 a Hacking/IT Incident affecting 2,213,597 individuals. Breached information located on Network Server. The attacker accessed the SQL database via remote desktop protocol starting October 3, 2015. Patient names, SSNs, diagnoses, and insurance info were exposed. 21CO settled for $2.3 million and implemented a corrective action plan.
Affected (this filing): 2,213,597
🦬Montana State AGMost recentlinked via operator-confirmed · 100%
21st Century Oncology reported a data breach to the Montana Attorney General. The breach was reported on 2016-03-14. The breach occurred on 10/3/2015. 264 Montana residents were affected.
Affected (this filing): 264
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.