Cove Family & Sports Medicine reported a data breach to the Montana Attorney General. The breach was reported on 2017-06-12. The breach occurred on 4/14/2017. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Jun 12, 2017. View entity profile → Other incidents for this victim →
incident inc_06c33f21236a4e82 · 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.
AL MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 14, 2017
When the intrusion reportedly occurred, per the linked filings
Apr 14, 2017
Reported by HHS OCR filing
Cove Family & Sports Medicine reported a data breach to the Montana Attorney General. The breach was reported on 2017-06-12. The breach occurred on 4/14/2017. 1 Montana residents were affected.
Affected (this filing): 1
Cove Family and Sports Medicine, LLC (AL) reported to HHS OCR on 2017-06-12 a Hacking/IT Incident (ransomware) affecting 4,300 individuals. On April 14, 2017, the CE discovered ransomware had attacked its network server, potentially compromising its entire electronic medical records system — including names, SSNs, addresses, patient IDs, prescriptions, diagnoses, procedures, and treatment dates for 4,299 individuals. The CE responded by reinstalling its OS, restoring from off-site backup, resetting passwords, and hardening security controls. OCR obtained assurances of corrective actions.
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.
Affected (this filing): 4,300