Confirmed breach. Intrusion Jun 1, 2019–Nov 8, 2019, discovered Jun 1, 2019 — the first regulatory filing landed 321 days later (flagged late). 233,835 individuals reported across the linked filings.
Good Samaritan Hospital, Inc. reported to HHS on 2020-04-17 a Hacking/IT Incident affecting 233,835 individuals. Breached information located on Email. A phishing attack compromised employee email accounts, exposing PHI including names, SSNs, and medical data. The entity settled with OCR for $600,000 and implemented a corrective action plan.
Affected (this filing): 233,835
42 days
🐻California State AGlinked via multistate filing link · 95%
Good Samaritan Hospital, Inc. reported a phishing incident in California on October 22, 2019. Between October 28 and November 8, 2019, employee email accounts were compromised via a targeted phishing campaign. The breach potentially exposed patient personal information (names, DOB, SSN, driver's license), protected health information, and financial account numbers. Good Sam engaged forensic investigators, reset credentials, and offered one year of credit monitoring.
Good Samaritan Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2020-07-01. The breach occurred from 10/28/2019 to 11/8/2019. 29 Montana residents were affected.
Affected (this filing): 29
🐻California State AGMost recentlinked via multistate filing link · 95%
Good Samaritan Hospital, Inc. disclosed a phishing incident affecting approximately 142,800 individuals, including 6 California residents. Unauthorized access to employee email accounts occurred between October 28 and November 8, 2019, potentially exposing PHI, SSNs, and financial data. The hospital engaged forensic investigators, reset credentials, and offered credit monitoring.
Affected (this filing): 142,800
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.