Confirmed breach. Intrusion Jan 18, 2016, discovered Jan 18, 2016 — the first regulatory filing landed 46 days later. 1,024 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1,024
Data types
5
PHI · Health (basic) · Identity (basic)
Jurisdictions
1
CA
Linked filings
1
all HHS OCR
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 18, 2016
When the intrusion reportedly occurred, per the linked filings
City of Hope reported to HHS on 2016-03-04 a Hacking/IT Incident affecting 1024 individuals. Breached information located on Email. The breach involved a phishing email containing an embedded link that granted unauthorized access to employee email accounts, exposing patient PHI including names, MRNs, DOBs, addresses, clinical data, and one SSN.
Affected (this filing): 1,024
HHS notified
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.