DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed4 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 4 filings

Roper St. Francis Healthcare — June 2020 breach

Clustered 4 filings across 3 jurisdictions · filing window Jan 1, 2020 → Sep 8, 2020. View entity profile → Other incidents for this victim →

✓ affected count, data types, discovery date agreeMerge100%

Determination

Confirmed

Members

4 filings

States

3

Affected · reported

92,964

First → last filing

Jan 1, 2020 → Sep 8, 2020

Merge confidence

100%

incident inc_9ee6ac1e640841b7 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. Intrusion Jun 13, 2020–Jun 17, 2020, discovered Jul 8, 2020. 92,964 individuals reported across the linked filings. Data reported: PHI, Health (basic), and Identity (basic). Notifications rolled out on a 251-day schedule across 4 filings beginning Jan 1, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
251days

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 notifiedFull clock table in Litigation Timeline

Incident timeline

Jun 13, 2020breach begins
Jul 8, 2020discovered
Jan 1, 2020first filing
Sep 8, 2020most recent filing

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

Member cascade — every filing about this breach

  1. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. SEP 3HHS OCRHHS OCR noticestates nationwide total 6,000+246d
  3. SEP 4MT AGMT AG notice1 MT residents+247d
  4. SEP 8HHS OCRHHS OCR noticemost recent · 92,963 affected+251d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 13, 2020 – Jun 17, 2020
MT AG
Discovered
Jul 8, 2020· 25d undetected
IL AG + MT AG
Data types
Health (basic) · Identity (basic) · PHI
HHS OCR + MT AG
Attack vector
Unauthorized Access
HHS OCR

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)

6,000

Sum of filed state slices

1· 0.0% of stated

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

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 filing4 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
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

251 days

Cadence

~1 / 83.7d

vs. multi-state median

31.4× 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.