Northern Idaho Advanced Care Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-29. The breach occurred from 1/16/2024 to 2/4/2024. 184 Montana residents were affected.
Affected (this filing): 184
Clustered 2 filings across 2 jurisdictions · filing window Mar 29, 2024 → Apr 1, 2024. View entity profile → Other incidents for this victim →
incident inc_52eae5d429fe4b08 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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.
MT WA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 16, 2024
When the intrusion reportedly occurred, per the linked filings
Feb 1, 2024
Reported by WASHINGTON AG filing
Northern Idaho Advanced Care Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-29. The breach occurred from 1/16/2024 to 2/4/2024. 184 Montana residents were affected.
Affected (this filing): 184
Northern Idaho Advanced Care Hospital, a health sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2024-02-01 and filed notice on 2024-04-01. 2,728 Washington residents were affected. 60 days elapsed between awareness and notification. 16 days to identify the breach. 3 days to contain the breach.
Affected (this filing): 2,728
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.