MedWatch, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2018-04-13. The breach occurred from 10/20/2017 to 12/15/2017. 285 Montana residents were affected.
Affected (this filing): 285
Clustered 2 filings across 2 jurisdictions · filing window Apr 13, 2018 → Apr 27, 2018. View entity profile → Other incidents for this victim →
incident inc_6c246d8c3757400f · 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.
FL MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 20, 2017
When the intrusion reportedly occurred, per the linked filings
Dec 15, 2017
Reported by HHS OCR filing
MedWatch, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2018-04-13. The breach occurred from 10/20/2017 to 12/15/2017. 285 Montana residents were affected.
Affected (this filing): 285
MedWatch LLC reported to HHS on 2018-04-27 a Unauthorized Access/Disclosure affecting 40621 individuals. Breached information located on Network Server. An IT subcontractor applied a misconfigured security patch to an online portal, exposing PHI including demographic and health insurance data.
Affected (this filing): 40,621
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.