All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed6 filings · 5 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 6 filings

Saint Anthony Hospital — February 2025 breach

Clustered 6 filings across 5 jurisdictions · filing window Mar 1, 2026 → Mar 10, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

Affected · reported

146,108

First → last filing

Mar 1, 2026 → Mar 10, 2026

Merge confidence

100%

incident inc_a1c2d835223e4011 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. Intrusion Feb 18, 2025–Mar 10, 2025, discovered Feb 27, 2025 — the first regulatory filing landed 367 days later (flagged late). 146,108 individuals reported across the linked filings. Data reported: Government ID, Financial account, PII, and 3 more. Notifications rolled out on a 9-day schedule across 6 filings beginning Mar 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

367days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

9days

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 clocksLeak gap✗ Leak >180dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 18, 2025breach begins

Feb 27, 2025discovered

notification delay · 367 days

Mar 1, 2026first filing

Mar 10, 2026most recent filing

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

Member cascade — every filing about this breach

MAR 1IL AGIL AG noticefirst filing · no count statedday 0
MAR 6NE AGNE AG noticeno count statedauto-linked+5d
MAR 6VT AGVT AG noticeno count statedauto-linked+5d
MAR 6HHS OCRHHS OCR noticestates nationwide total 146,108auto-linked+5d
MAR 7MA AGMA AG noticeno count statedauto-linked+6d
MAR 10NH AGNH AG noticemost recent · 1 NH residentsauto-linked+9d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Feb 18, 2025 – Mar 10, 2025
Discovered: Feb 27, 2025· 9d undetected
Data types: Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
Attack vector: Unauthorized Access

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)

146,108

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

9 days

Cadence

~1 / 1.8d

vs. multi-state median

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