Greetings! Today we are posting here the new company, "College Hospital Costa Mesa". Company Description: College Hospital Costa Mesa is a facility specializing in psychiatric and medical/surgical services as well as outpatient telehealth, and...
Clustered 2 filings across 2 jurisdictions · filing window Sep 26, 2024 → Mar 10, 2025. View entity profile → Other incidents for this victim →
incident inc_057719782ea44978 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
CA
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 14, 2024 → Sep 17, 2024
When the intrusion reportedly occurred, per the linked filings
Sep 17, 2024
Reported by CALIFORNIA AG filing
Greetings! Today we are posting here the new company, "College Hospital Costa Mesa". Company Description: College Hospital Costa Mesa is a facility specializing in psychiatric and medical/surgical services as well as outpatient telehealth, and...
College Hospital Costa Mesa notified former employees and patients of a data breach. Unauthorized access occurred between August 14, 2024, and September 17, 2024. The organization discovered the incident on September 17, 2024. Affected data included names, Social Security numbers, driver's license numbers, dates of birth, and health information such as diagnoses and dates of service. The organization engaged forensic experts, notified law enforcement, and offered 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.