DisclosureLens
All incidentsView linkage analytics →
HHS OCRHHS OCR enforcementState AGEnforced8 records · 7 statesLifecycle stage 3 of 3: EnforcedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 records

21st Century Oncology — October 2015 breach

Clustered 8 records across 8 jurisdictions: 7 filings and 1 enforcement record · filing window Mar 4, 2016 → Apr 28, 2016. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Enforced

Members

8 records

States

7

Affected · reported

2,213,597

First → last filing

Mar 4, 2016 → Apr 28, 2016

Merge confidence

100%

incident inc_ab6003507d754bd0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 enforcement record. The filings describe unauthorized access. 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. Data reported: Government ID, Financial account, Health (basic), and 3 more. Notifications rolled out on a 55-day schedule across 7 filings beginning Mar 4, 2016. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
153days

Discovered → first regulatory filing

Discovery variance
41days

Range of discovered_at dates across filings

Filing span
55days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksHIPAA✗ HHS report late · 153dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 3, 2015breach begins
Oct 3, 2015discovered · members disagree
notification delay · 153 days
Mar 4, 2016first filing
Apr 28, 2016most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing and enforcement record in this incident

  1. MAR 4WA AGWA AG noticefirst filing · 2,802 WA residentsday 0
  2. MAR 4CA AGCA AG noticeno count statedday 0
  3. MAR 4NH AGNH AG notice1,202 NH residentsday 0
  4. MAR 4HHS OCRHHS OCR noticestates nationwide total 2,213,597day 0
  5. MAR 14MT AGMT AG notice264 MT residents+10d
  6. APR 27MA AGMA AG notice2 MA residents+54d
  7. APR 28SC AGSC AG notice97,842 SC residents+55d
  8. DEC 28HHS OCR enforcementHHS OCR enforcement noticemost recent · no count stated+664d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 3, 2015
WA AG
Discovered
Oct 3, 2015HHS OCRNov 13, 2015WA AG + CA AG + NH AG +2filings disagree on discovery
Data types
Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI
WA AG + MT AG + SC AG +4
Attack vector
Unauthorized Access
WA AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

2,213,597

Sum of filed state slices

102,112· 4.6% of stated

95% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US2,213,597
SC97,842
WA2,802
NH1,202
MT264
MA2

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing8 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Sep 7, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

55 days

Cadence

~1 / 9.2d

vs. multi-state median

9.2× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.