Family Medical Center of Michigan reported a data breach to the Montana Attorney General. The breach was reported on 2021-08-26. The breach occurred on 7/23/2020. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Aug 26, 2021. View entity profile → Other incidents for this victim →
incident inc_ab482252d96d4624 · 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.
Identity (basic) · Government ID · Health (basic)
FEDERAL MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 23, 2020
When the intrusion reportedly occurred, per the linked filings
Family Medical Center of Michigan reported a data breach to the Montana Attorney General. The breach was reported on 2021-08-26. The breach occurred on 7/23/2020. 1 Montana residents were affected.
Affected (this filing): 1
Family Medical Center of Michigan reported a hacking attack to HHS on August 26, 2021, which compromised the protected health information of 21,988 individuals. The breach involved data such as names, addresses, Social Security numbers, and medical treatment information, which was located on a network server. In response, the center implemented additional technical safeguards and notified the affected individuals and the media. OCR provided technical assistance.
Affected (this filing): 21,988
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.