DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed10 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

Illinois Bone & Joint Institute, LLC — May 2024 breach

Clustered 10 filings across 6 jurisdictions · filing window Aug 30, 2024 → Dec 20, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

6

Affected · reported

665,321

First → last dated filing

Aug 30, 2024 → Dec 20, 2024

Merge confidence

100%

incident inc_d90414da5c3e47e0 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion May 30, 2024–Jul 4, 2024, discovered May 30, 2024. 665,321 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 3 more. Notifications rolled out on a 112-day schedule across 9 dated filings beginning Aug 30, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
35days

Range of discovered_at dates across filings

Filing span
112days

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 clocksVermont✗ VT AG >45 bdayMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 30, 2024breach begins
May 30, 2024discovered · members disagree
Aug 30, 2024first dated filing
Dec 20, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. AUG 1IL AGIL AG noticefiling day not on record · no count stated—
  2. AUG 30VT AGVT AG noticefirst filing · no count statedday 0
  3. AUG 30MA AGMA AG notice213 MA residentsday 0
  4. AUG 30MT AGMT AG notice17 MT residentsday 0
  5. AUG 30HHS OCRHHS OCR noticestates nationwide total 665,321day 0
  6. SEP 3NH AGNH AG notice6 NH residents+4d
  7. DEC 19MT AGMT AG notice60 MT residents+111d
  8. DEC 19CA AGCA AG noticeno count stated+111d
  9. DEC 19VT AGVT AG noticeno count stated+111d
  10. DEC 20NH AGNH AG noticemost recent · 36 NH residents+112d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2024 – Jul 4, 2024
VT AG
Discovered
May 30, 2024IL AGJul 4, 2024VT AG + MT AG + NH AG +1filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + MT AG + HHS OCR +3
Attack vector
Unauthorized Access
VT 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)

665,321

Sum of filed state slices

309· 0.0% of stated

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

US665,321
MA213
MT60
NH36

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 filing10 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 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

112 days

Cadence

~1 / 14d

vs. multi-state median

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