Clustered 2 filings across 1 jurisdiction · filed Jan 11, 2021. View entity profile → Other incidents for this victim →
incident inc_98234186c8e245db · 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.
Identity (basic) · Government ID · Financial account
WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 12, 2020
Reported by WASHINGTON AG filing
Jefferson Healthcare, a health sector entity reported a phishing incident to the Washington Attorney General. The organization became aware of the incident on 2020-11-12 and filed notice on 2021-01-11. 2,496 Washington residents were affected. 60 days elapsed between awareness and notification. 3 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 2,496
Jefferson Healthcare (WA) reported to HHS on 2021-01-11 a Hacking/IT Incident affecting 2,543 individuals. An employee was the victim of an email phishing attack that compromised ePHI including names, addresses, dates of birth, driver's license numbers, Social Security numbers, financial information, claims information, diagnoses, lab results, and medications. Breached information was located in Email. The CE notified HHS, affected individuals, the media, and provided substitute notice on its website, and implemented additional technical safeguards and staff retraining.
Affected (this filing): 2,543
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.