Putnam County Memorial Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2021-10-27. The breach occurred from 7/16/2021 to 7/18/2021. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filing window Oct 27, 2021 → Nov 3, 2021. View entity profile → Other incidents for this victim →
incident inc_70e44c4a04574283 · 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)
MO MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 16, 2021
When the intrusion reportedly occurred, per the linked filings
Putnam County Memorial Hospital reported a data breach to the Montana Attorney General. The breach was reported on 2021-10-27. The breach occurred from 7/16/2021 to 7/18/2021. 2 Montana residents were affected.
Affected (this filing): 2
Putnam County Memorial Hospital (Putnam County, MO) reported to HHS OCR on 2021-11-03 a ransomware attack affecting the PHI of 6,916 individuals. Breached information was located on a Network Server. Exposed data included names, addresses, dates of birth, driver's license numbers, Social Security numbers, diagnoses, lab results, medications, and other treatment information. In response, the CE offered credit monitoring, notified affected individuals and media, and implemented additional administrative, technical, and security safeguards including staff retraining.
Affected (this filing): 6,916
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.