Clustered 3 filings across 3 jurisdictions · filing window Sep 24, 2021 → Sep 28, 2021. View entity profile → Other incidents for this victim →
incident inc_a7c3326f50e0481d · 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.
ME MT TX
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 30, 2021
When the intrusion reportedly occurred, per the linked filings
Jul 26, 2021
Reported by MAINE AG filing
The Menninger Clinic reported to HHS on 2021-09-24 a Hacking/IT Incident affecting 1365 individuals. Breached information located on Email. Employees were victims of an email phishing scheme exposing PHI including names, DOB, addresses, SSNs, and medical/financial data. Response included credit monitoring, security safeguards, and staff retraining.
Affected (this filing): 1,365
The Menninger Clinic reported a data breach to the Montana Attorney General. The breach was reported on 2021-09-24. The breach occurred on 3/30/2021. 4 Montana residents were affected.
Affected (this filing): 4
The Menninger Clinic, a healthcare organization, reported an external system breach that occurred on March 18, 2021, and was discovered on July 26, 2021. The incident affected 2,076 individuals, compromising names and financial account numbers with associated access credentials. The clinic notified affected individuals on September 24, 2021, and offered 12 months of credit and identity monitoring services through IDX.
Affected (this filing): 2,076
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.