Clustered 3 filings across 3 jurisdictions · filing window Aug 1, 2022 → Aug 2, 2022. View entity profile → Other incidents for this victim →
incident inc_e42131784f4b4687 · 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.
PHI · Identity (basic) · Health (basic)
ID MT OR
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 15, 2022
When the intrusion reportedly occurred, per the linked filings
Jul 6, 2022
Reported by OREGON AG filing
St. Luke's Health System reported a data breach to the Montana Attorney General. The breach was reported on 2022-08-01. The breach occurred from 5/15/2022 to 5/31/2022. 25 Montana residents were affected.
Affected (this filing): 25
St. Luke’s Health System reported a data breach to the Oregon Attorney General. The breach was reported on 2022-08-02. The breach occurred during 5/18/2022 - 6/2/2022. The breach was discovered on 7/6/2022. 31,573 individuals were affected. Notice was sent on 8/1/2022.
Affected (this filing): 31,573
St. Luke's Health System, Ltd. (Idaho healthcare provider) reported to HHS OCR on 2022-08-02 that its business associate suffered a hacking/IT cybersecurity incident on a network server, affecting PHI of 31,573 individuals. PHI included names, dates of birth, addresses, and treatment and financial information. St. Luke's notified HHS, affected individuals, the media, provided substitute notice, terminated the BA relationship, and offered complimentary credit monitoring.
Affected (this filing): 31,573
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.