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.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
38,628
Data types
2
Health (basic) · Identity (basic)
Jurisdictions
2
CA FEDERAL
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 25, 2019
When the intrusion reportedly occurred, per the linked filings
Golden Valley Health Centers reported unauthorized access to an email account containing patient billing, insurance, referral, and appointment records. The breach date is listed as October 25, 2019. The organization engaged forensic experts and implemented additional security training and policy reviews.
Golden Valley Health Centers reported that an employee was the victim of an email phishing scheme that affected the electronic protected health information (ePHI) of 38,268 individuals. The ePHI involved included names, claims information, health insurance information, and other treatment information. The CE notified HHS, affected individuals, and the media. In its mitigation efforts, the CE implemented additional administrative and technical safeguards and retrained its staff on recognizing and responding to fraudulent email communications. During the investigation, OCR provided the CE with technical assistance.
Affected (this filing): 38,628
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.