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

Confirmed2 filings · 1 stateUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 2 filings

Advanced Care Hospital of Montana — January 2024 breach

Clustered 2 filings across 1 jurisdiction · filing window Mar 29, 2024 → Apr 2, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

2,331

First → last filing

Mar 29, 2024 → Apr 2, 2024

Merge confidence

100%

incident inc_ebd051b608b04697 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filings describe unauthorized access. Intrusion Jan 16, 2024–Feb 4, 2024, discovered Feb 1, 2024 — the first regulatory filing landed 57 days later. 2,331 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

57days

Discovered → first regulatory filing

Filing span

4days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 16, 2024breach begins

Feb 1, 2024discovered

notification delay · 57 days

Mar 29, 2024first filing

Apr 2, 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

MAR 29MT AGMT AG noticefirst filing · 2,190 MT residentsauto-linkedday 0
APR 2HHS OCRHHS OCR noticemost recent · states nationwide total 2,331auto-linked+4d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jan 16, 2024 – Feb 4, 2024
Discovered: Feb 1, 2024· 16d undetected
Data types: 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)

2,331

Sum of filed state slices

2,190· 94.0% of stated

6% 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 filing2 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

4 days

vs. multi-state median

2.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.