Clustered 2 filings across 2 jurisdictions · filing window Sep 17, 2019 → Sep 18, 2019. View entity profile → Other incidents for this victim →
incident inc_da0fd2a9ff7642c8 · merge_method deterministic · confidence 100%
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 OR
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 31, 2019
When the intrusion reportedly occurred, per the linked filings
Salem Health reported a data breach to the Montana Attorney General. The breach was reported on 2019-09-17. The breach occurred on 7/31/2019. 1 Montana residents were affected.
Affected (this filing): 1
Salem Health reported a data breach to the Oregon Attorney General. The breach was reported on 2019-09-18. The breach occurred during 1/1/0001. The breach was discovered on 1/1/0001. 749 individuals were affected. Notice was sent on 1/1/0001.
Affected (this filing): 749
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.