University of Chicago Medical Center reported a data breach to the Montana Attorney General. The breach was reported on 2022-05-27. The breach occurred from 3/24/2022 to 3/31/2022. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed May 27, 2022. View entity profile → Other incidents for this victim →
incident inc_bd8b66be2e1e4385 · 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
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 24, 2022
When the intrusion reportedly occurred, per the linked filings
Mar 24, 2022
Reported by MAINE AG filing
University of Chicago Medical Center reported a data breach to the Montana Attorney General. The breach was reported on 2022-05-27. The breach occurred from 3/24/2022 to 3/31/2022. 1 Montana residents were affected.
Affected (this filing): 1
The University of Chicago Medical Center reported a data breach to the Maine Attorney General, indicating that an external system breach (hacking) occurred on March 24, 2022. The breach was also discovered on the same day. The incident affected 2 Maine residents, exposing their names and Social Security Numbers. The medical center provided written notification to the affected individuals on May 27, 2022, and offered two years of complimentary credit monitoring and identity protection services through Kroll.
Affected (this filing): 2
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.