Sanger Skilled Care, LLC dba Cornerstone Care Center reported to HHS on 2026-05-07 a Hacking/IT Incident affecting 1510 individuals. Breached information located on Electronic Medical Record, Network Server.
Affected (this filing): 1,510
Clustered 2 filings across 1 jurisdiction · filed May 7, 2026. View entity profile → Other incidents for this victim →
incident inc_4180d3f0ab6b4fba · 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.
PHI · Health (basic) · Identity (basic)
CA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 7, 2026
When the intrusion reportedly occurred, per the linked filings
Apr 7, 2026
Reported by CALIFORNIA AG filing
Sanger Skilled Care, LLC dba Cornerstone Care Center reported to HHS on 2026-05-07 a Hacking/IT Incident affecting 1510 individuals. Breached information located on Electronic Medical Record, Network Server.
Affected (this filing): 1,510
Sanger Skilled Care, LLC dba Cornerstone Care Center notified the California Attorney General of an incident where unauthorized activity involving one user account was detected on April 7, 2026. The organization contained the incident and engaged a forensic firm. Investigation determined that Protected Health Information (PHI) may have been accessed by an unauthorized third party. No evidence of misuse was found. Affected individuals were offered 12 months of complimentary credit monitoring.
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.