Clustered 3 filings across 2 jurisdictions · filed Nov 6, 2018. View entity profile → Other incidents for this victim →
incident inc_d9675e4af03043be · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
OR WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 27, 2018
When the intrusion reportedly occurred, per the linked filings
Sep 25, 2018
Reported by OREGON AG, WASHINGTON AG filings
Southwest Washington Regional Surgery Center, LLC reported to HHS on 2018-11-06 a Hacking/IT Incident affecting 2,393 individuals. Breached information located on Email. The breach involved a malware/phishing attack exposing names, driver's license info, SSNs, claims, credit card info, and clinical data. The entity implemented multi-factor authentication for email.
Southwest Washington Regional Surgery Center, LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2018-11-06. The breach occurred during 5/27/2018 - 5/27/2018. The breach was discovered on 9/25/2018. 2,393 individuals were affected. Notice was sent on 11/6/2018.
Affected (this filing): 2,393
Southwest Washington Regional Surgery Center, LLC, a health sector entity reported a phishing incident to the Washington Attorney General. The organization became aware of the incident on 2018-09-25 and filed notice on 2018-11-06. 1,690 Washington residents were affected. 42 days elapsed between awareness and notification. 121 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 1,690
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.
Affected (this filing): 2,393