Salina Family Healthcare Center reported a data breach to the Montana Attorney General. The breach was reported on 2017-08-16. The breach occurred on 6/18/2017. 15 Montana residents were affected.
Affected (this filing): 15
Clustered 2 filings across 2 jurisdictions · filed Aug 16, 2017. View entity profile → Other incidents for this victim →
incident inc_df695153f3cb4ae5 · 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.
Health (basic) · Identity (basic) · Financial account
FEDERAL MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 18, 2017
When the intrusion reportedly occurred, per the linked filings
Salina Family Healthcare Center reported a data breach to the Montana Attorney General. The breach was reported on 2017-08-16. The breach occurred on 6/18/2017. 15 Montana residents were affected.
Affected (this filing): 15
On June 18, 2017, Salina Family Healthcare Center suffered a ransomware attack that encrypted some of its computer workstations and network servers, affecting approximately 77,337 individuals. The protected health information (PHI) involved included demographic, clinical, and health insurance information. The center restored its computers and servers from a recent backup, provided breach notifications, and engaged a computer forensics expert. Safeguards were improved by scanning the network for viruses, upgrading servers, limiting internet access, and providing additional security training to staff.
Affected (this filing): 77,337
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.