Midwest Geriatric Management, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-14. The breach occurred from 10/13/2020 to 10/14/2020. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Dec 14, 2020. View entity profile → Other incidents for this victim →
incident inc_12af8b2d42034a91 · merge_method deterministic · confidence 100%
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.
PII · PHI · Financial
MO MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 13, 2020
When the intrusion reportedly occurred, per the linked filings
Midwest Geriatric Management, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-14. The breach occurred from 10/13/2020 to 10/14/2020. 1 Montana residents were affected.
Affected (this filing): 1
Midwest Geriatric Management, LLC (Missouri healthcare provider) reported to HHS OCR on 2020-12-14 that an employee fell victim to an email phishing scheme, exposing PHI of 4,814 individuals. Compromised data included names, Social Security numbers, and financial and treatment information. The entity notified HHS, affected individuals, and the media; provided substitute notice; offered complimentary credit monitoring; implemented additional administrative, technical, and security safeguards; and retrained staff on email security.
Affected (this filing): 4,814
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.