Confirmed breach. Intrusion Jan 26, 2024–Jan 31, 2024, discovered Jun 17, 2024 — the first regulatory filing landed 10 days later. 775,860 individuals reported across the linked filings.
Ann & Robert H. Lurie Children's Hospital of Chicago Ann & Robert H. Lurie Children's Hospital of Chicago provides superior pediatric care in a setting that offers the latest benefits and innovations in medical technology, research and family-friendly design.
🌐GLOBALClaimed by Rhysidalinked via cross-source match · 100%
Ann & Robert H. Lurie Children's Hospital of Chicago Ann & Robert H. Lurie Children's Hospital of Chicago provides superior pediatric care in a setting that offers the latest benefits and innovations in medical technology, research and family-friendly design.
111 days
Breach discovered
Jun 17, 2024
Reported by MAINE AG filing
🦞Maine State AGLeaked → filing gap · 5 molinked via cross-source match · 100%
Ann & Robert H. Lurie Children's Hospital of Chicago suffered an external cybersecurity attack in which cybercriminals accessed hospital systems between January 26–31, 2024. The hospital took systems offline on January 31 including Epic EHR and MyChart. The breach was discovered on June 17, 2024. PII and PHI of patients and minors were impacted. 791,784 individuals were affected nationally; 8 Maine residents were affected. Experian IdentityWorks (24-month) was offered as remediation.
🇺🇸ILHHS OCRMost recentLeaked → filing gap · 5 molinked via same-victim cross-source · 100%
Ann & Robert H. Lurie Children's Hospital of Chicago reported to HHS on 2024-06-27 a Hacking/IT Incident affecting 775,860 individuals. Breached information located on Network Server. The cyberattack exposed PHI including names, addresses, DOB, SSN, driver's license, claims, financial info, diagnoses, lab results, and medications. The CE notified HHS, individuals, and media, and implemented additional technical safeguards.
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.