Clustered 2 filings across 2 jurisdictions · filed Jun 19, 2017. View entity profile → Other incidents for this victim →
incident inc_02332746217b4d7f · merge_method deterministic · confidence 100%
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.
PHI · Identity (basic) · Government ID
CA MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 18, 2017
When the intrusion reportedly occurred, per the linked filings
Torrance Memorial Medical Center reported a data breach to the Montana Attorney General. The breach was reported on 2017-06-19. The breach occurred from 4/18/2017 to 4/19/2017. 5 Montana residents were affected.
Affected (this filing): 5
HHS OCR breach portal entry: Torrance Memorial Medical Center (CA) reported a Hacking/IT Incident involving Email on 2017-06-19, affecting 46,632 individuals per the portal count (the narrative text states 44,960 individuals plus 3,304 SSNs — discrepancy noted). Two workforce members responded to a phishing email, exposing PHI including names, addresses, DOBs, healthcare claims information, diagnoses, medications, other treatment information, and 3,304 SSNs. The CE notified HHS, affected individuals, and the media; remediation included expanded security training, enhanced authentication, and improved malicious-email controls. OCR's investigation closed with the CE improving PHI safeguards.
Affected (this filing): 46,632
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.