Clustered 2 filings across 1 jurisdiction · filing window Feb 18, 2022 → Mar 14, 2022. View entity profile → Other incidents for this victim →
incident inc_e91c8ec171fd4976 · merge_method llm · confidence 72%
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.
WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 18, 2022
Reported by WASHINGTON AG filing
Virginia Mason Medical Center, a health sector entity reported a phishing incident to the Washington Attorney General. The organization became aware of the incident on 2022-01-18 and filed notice on 2022-02-18. 3,000 Washington residents were affected. 31 days elapsed between awareness and notification. 28 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 3,000
Virginia Mason Medical Center reported to HHS on 2022-03-14 a Hacking/IT Incident affecting 2733 individuals. Breached information located on Email. Employees were victims of an email phishing attack exposing PHI including names, SSNs, addresses, driver's license numbers, DOB, lab results, medications, and financial information. The entity notified HHS, individuals, and media, strengthened safeguards, and retrained staff.
Affected (this filing): 2,733
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.