Providence WA Anesthesia Services PC reported a data breach to the Montana Attorney General. The breach was reported on 2022-10-24. The breach occurred on 7/11/2022. 72 Montana residents were affected.
Affected (this filing): 72
Clustered 2 filings across 2 jurisdictions · filing window Oct 24, 2022 → Oct 25, 2022. View entity profile → Other incidents for this victim →
incident inc_4601b6835a194466 · 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
Jul 11, 2022
When the intrusion reportedly occurred, per the linked filings
Jul 11, 2022
Reported by WASHINGTON AG filing
Providence WA Anesthesia Services PC reported a data breach to the Montana Attorney General. The breach was reported on 2022-10-24. The breach occurred on 7/11/2022. 72 Montana residents were affected.
Affected (this filing): 72
Providence WA Anesthesia Services PC, a health sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2022-07-11 and filed notice on 2022-10-25. 56,578 Washington residents were affected. 106 days elapsed between awareness and notification. 2 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 56,578
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.