DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SitePressHHS OCRState AGConfirmed9 records · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhousehigh sensitivity
Merged incident · 9 records

Dameron Hospital — November 2023 breach

Clustered 9 records across 6 jurisdictions: 7 filings, 1 press report and 1 leak-site claim · filed Apr 2, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 records

States

6

Affected · reported

210,706

First → last dated filing

Apr 2, 2025

Merge confidence

100%

incident inc_a4503fe7951d442e · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings, 1 press report and 1 unverified claim. The filings describe unauthorized access. Intrusion Nov 4, 2023–Nov 5, 2023, discovered Nov 5, 2023. 210,706 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
502days

Range of discovered_at dates across filings

Filing span
0days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 4, 2023breach begins
Nov 5, 2023discovered · members disagree
Apr 2, 2025first dated filing
—watching for filings

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 and leak-site claim in this incident

  1. DEC 13Leak siteransomhouse postfirst record · attacker claim · unverifiedday 0
  2. APR 1IL AGIL AG noticefiling day not on record · no count stated—
  3. APR 2IN AGIN AG noticestates nationwide total 210,706+476d
  4. APR 2VT AGVT AG noticeno count stated+476d
  5. APR 2HHS OCRHHS OCR noticestates nationwide total 210,706+476d
  6. APR 2MA AGMA AG notice27 MA residents+476d
  7. APR 2CA AGCA AG noticeno count stated+476d
  8. APR 2MT AGMT AG noticemost recent · 54 MT residents+476d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 4, 2023
IN AG
Discovered
Nov 5, 2023IL AGMar 21, 2025VT AG + MT AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + HHS OCR + MA AG +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)

210,706

Sum of filed state slices

145· 0.1% of stated

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

US210,706
IN64
MT54
MA27

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing7 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 23, 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

0 days

Cadence

~1 / 0d

vs. multi-state median

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