Clustered 3 filings across 2 jurisdictions · filed Mar 29, 2024. View entity profile → Other incidents for this victim →
incident inc_daa52d9891394bc1 · 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
Jan 16, 2024
When the intrusion reportedly occurred, per the linked filings
Feb 1, 2024
Reported by CALIFORNIA AG filing
Rehabilitation Hospital of Southern California, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-29. The breach occurred from 1/16/2024 to 2/4/2024. 1 Montana residents were affected.
Affected (this filing): 1
Rehabilitation Hospital of Southern California reported that an unauthorized party gained access to its IT network between January 16 and February 4, 2024. The incident was discovered on February 1, 2024. The breach affected current and former employees as well as patients, potentially exposing names and other personal/health information. The hospital secured systems, engaged a third-party forensic firm, and notified law enforcement. Affected individuals are offered one year of identity theft protection.
Rehabilitation Hospital of Southern California reported to HHS on 2024-03-29 a Hacking/IT Incident affecting 925 individuals. Breached information located on Network Server. The incident involved ransomware encrypting PHI including names, DOB, SSN, driver's license, and treatment data. The entity offered credit monitoring and enhanced safeguards.
Affected (this filing): 925
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.