Clustered 3 filings across 3 jurisdictions · filed Nov 14, 2023. View entity profile → Other incidents for this victim →
incident inc_b47a7b2d4434416b · 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.
PHI · Identity (basic) · Government ID
MT VT WI
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 27, 2023
When the intrusion reportedly occurred, per the linked filings
Sep 21, 2023
Reported by VERMONT AG filing
Medical College of Wisconsin reported a data breach to the Montana Attorney General. The breach was reported on 2023-11-14. The breach occurred on 5/27/2023. 27 Montana residents were affected.
Affected (this filing): 27
Medical College of Wisconsin reported to HHS on 2023-11-14 a Hacking/IT Incident affecting 240,667 individuals. A third-party vendor experienced a cybersecurity incident allowing unauthorized access to its network server, compromising PHI including names, addresses, SSNs, dates of birth, claims information, diagnoses, lab results, and medications. The CE notified HHS, affected individuals, and the media, and terminated its relationship with the vendor.
Affected (this filing): 240,667
Medical College of Wisconsin notified consumers of a data breach involving its MOVEit Transfer vendor. Unauthorized actors accessed files containing personal information (names, addresses, SSNs, health data) on May 27, 2023. MCW discovered the incident on September 21, 2023, engaged forensic investigators, and is offering credit monitoring services.
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.