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

Tri-City Healthcare District — November 2023 breach

Clustered 4 filings across 4 jurisdictions · filing window Oct 11, 2024 → Oct 14, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

108,149

First → last filing

Oct 11, 2024 → Oct 14, 2024

Merge confidence

100%

incident inc_1383ec4acbd847ee · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe unauthorized access. Intrusion Nov 8, 2023, discovered Nov 9, 2023 — the first regulatory filing landed 337 days later (flagged late). 108,149 individuals reported across the linked filings. Data reported: Identity (basic), PII, PHI, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
337days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
3days

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 bdayMaine✗ ME AG >90d · 338dCalifornia✗ CA 60-day late · 337dFull clock table in Litigation Timeline

Incident timeline

Nov 8, 2023breach begins
Nov 9, 2023discovered
notification delay · 337 days
Oct 11, 2024first filing
Oct 14, 2024most 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. OCT 11VT AGVT AG noticefirst filing · no count statedday 0
  2. OCT 12ME AGME AG noticestates nationwide total 108,149+1d
  3. OCT 12CA AGCA AG noticeno count stated+1d
  4. OCT 14NH AGNH AG noticemost recent · 17 NH residents+3d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 8, 2023
VT AG
Discovered
Nov 9, 2023· 1d undetected
VT AG + ME AG + CA AG +1
Data types
Health (basic) · Identity (basic) · PHI · PII
VT AG + ME AG + CA AG +1
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)

108,149

Sum of filed state slices

31· 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

3 days

Cadence

~1 / 1d

vs. multi-state median

2.7× faster

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.