Clustered 2 filings across 1 jurisdiction · filing window Oct 15, 2021 → Oct 19, 2021. View entity profile → Other incidents for this victim →
incident inc_26a91be9423a456a · merge_method deterministic · confidence 85%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · PHI
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
CA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 17, 2021 → May 5, 2021
When the intrusion reportedly occurred, per the linked filings
May 1, 2021
Reported by CALIFORNIA AG filings
Anthem, Inc. reported a ransomware attack on its vendor, PracticeMax, affecting the VillageHealth program for End Stage Kidney Disease members. The breach occurred between April 17 and May 5, 2021, exposing PHI and basic PII (names, DOB, addresses, clinical data). PracticeMax engaged forensic investigators, notified law enforcement, and provided 24 months of credit monitoring.
PracticeMax Inc. reported a ransomware attack on its network occurring between April 17, 2021, and May 5, 2021. The incident involved unauthorized access to a server containing Protected Health Information (PHI) and personally identifiable information (PII), including names, dates of birth, addresses, phone numbers, and Social Security Numbers for some individuals. PracticeMax engaged legal counsel and a forensic firm, restored system access, and notified law enforcement. Affected individuals were offered 24 months of credit monitoring via Equifax. The breach impacted patients of DaVita's VillageHealth program.
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.