DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed11 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedthreeamhigh sensitivity
Merged incident · 11 filings

Kootenai Health — February 2024 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

464,088

First → last filing

Mar 25, 2024 → Aug 14, 2024

Merge confidence

100%

incident inc_7d4379aa29ae49a6 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. Intrusion Feb 22, 2024–Mar 2, 2024, discovered Feb 22, 2024 — the first regulatory filing landed 62 days later (flagged late). 464,088 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 141-day schedule across 10 filings beginning Mar 25, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
62days

Discovered → first regulatory filing

Discovery variance
161days

Range of discovered_at dates across filings

Leak precedence
29days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
141days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksCalifornia✗ CA 60-day late · 163dMaine✗ ME AG >90d · 163dWashington✗ WA AG >90dLeak gap⏱ Leak >90dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 22, 2024breach begins
Feb 22, 2024discovered · members disagree
notification delay · 62 days
Apr 24, 2024first filing
Aug 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. MAR 25Leak sitethreeam postfirst filing · attacker claim · unverifiedday 0
  2. APR 24HHS OCRHHS OCR noticestates nationwide total 464,088+30d
  3. AUG 1IL AGIL AG noticeno count stated+129d
  4. AUG 12MT AGMT AG notice6,684 MT residents+140d
  5. AUG 12CA AGCA AG noticeno count stated+140d
  6. AUG 12NH AGNH AG notice80 NH residents+140d
  7. AUG 12ME AGME AG noticestates nationwide total 464,088+140d
  8. AUG 12IN AGIN AG noticestates nationwide total 464,088+140d
  9. AUG 13OR AGOR AG noticestates nationwide total 464,088+141d
  10. AUG 13WA AGWA AG notice94,530 WA residents+141d
  11. AUG 14MA AGMA AG noticemost recent · 168 MA residents+142d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 22, 2024
MT AG
Discovered
Feb 22, 2024IL AGMar 2, 2024MT AG + CA AG + NH AG +2Aug 1, 2024OR AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MT AG + CA AG +4
Attack vector
Unauthorized Access
HHS OCR

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)

464,088

Sum of filed state slices

101,848· 21.9% of stated

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

US464,088
WA94,530
MT6,684
IN303
MA168
ME83
NH80

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 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 Aug 25, 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

141 days

Cadence

~1 / 14.1d

vs. multi-state median

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