Confirmed breach. Intrusion Sep 7, 2024, discovered Sep 12, 2024 — the first regulatory filing landed 329 days later (flagged late). 13,318 individuals reported across the linked filings.
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 clocksWashington✗ WA AG >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
13,318
Data types
—
Jurisdictions
2
IN WA
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Sep 7, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Sep 12, 2024
Reported by WASHINGTON AG filing
329 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
East Adams Rural Healthcare reported a data breach to the Indiana Attorney General. The breach occurred on 2024-09-07 and was reported on 2025-08-07. 8 Indiana residents were affected. 13,318 individuals affected in total.
East Adams Rural Healthcare, a health sector entity reported a other incident to the Washington Attorney General. The organization became aware of the incident on 2024-09-12 and filed notice on 2025-08-11. 8,896 Washington residents were affected. 333 days elapsed between awareness and notification. 5 days to identify the breach. 1 days to contain the breach.
Affected (this filing): 8,896
WA AG >90d
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.