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.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
2,155
Data types
2
Health (basic) · Identity (basic)
Jurisdictions
2
IL NH
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jul 20, 2024
When the intrusion reportedly occurred, per the linked filings
68 days
Breach discoveredletter-grounded
Sep 26, 2024
Reported by NEW HAMPSHIRE AG filing
60 days
🇺🇸ILHHS OCRFirst filinglinked via same-victim cross-source · 100%
Citadel of Northbrook (IL), a Healthcare Provider, reported to HHS OCR on 2024-11-25 a Hacking/IT Incident affecting 2,155 individuals. Breached information was located on Electronic Medical Record and Network Server systems. A business associate was present. No further details were provided in the public disclosure.
Affected (this filing):
⛰️New Hampshire State AGMost recentlinked via same-victim cross-source · 100%
Citadel of Northbrook notified the NH Attorney General of a data incident involving its EHR provider, PointClickCare. An unauthorized actor used compromised credentials to access limited patient information (names, health data) starting July 20, 2024. Citadel learned of the incident on Sept 26, 2024. One NH resident was affected. Notices offering credit monitoring were sent Nov 25, 2024.
Affected (this filing): 1
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.