Clustered 3 filings across 2 jurisdictions · filing window Apr 8, 2021 → Apr 21, 2021. View entity profile → Other incidents for this victim →
incident inc_ea782ff41efd4963 · 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.
CA MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 30, 2020
Reported by CALIFORNIA AG filing
Oct 22, 2020
When the intrusion reportedly occurred, per the linked filings
Health Center Partners of Southern California reported a data breach to the Montana Attorney General. The breach was reported on 2021-04-08. The breach occurred from 10/22/2020 to 12/2/2020. 134 Montana residents were affected.
Affected (this filing): 134
Health Center Partners of Southern California reported to HHS on 2021-04-09 a Hacking/IT Incident affecting 337,245 individuals. Breached information located on Network Server. A vendor experienced a ransomware attack affecting ePHI including names, diagnoses, SSNs, medications, and financial/insurance data. The BA implemented additional administrative, technical, and security safeguards.
Affected (this filing): 337,245
Health Center Partners of Southern California (HCP) notified the California AG of a data breach involving its IT provider, Netgain Technology, LLC. An unauthorized third party accessed Netgain's systems between Oct 22 and Dec 3, 2020, obtaining files containing personal information of HCP's patients and staff. HCP engaged cybersecurity experts, reported the incident to the FBI, and offered credit monitoring. No misuse of data was identified.
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.