Dental Center of Northwest Ohio reported a data breach to the Montana Attorney General. The breach was reported on 2018-12-28. The breach occurred from 8/16/2018 to 9/18/2018. 3 Montana residents were affected.
Affected (this filing): 3
Clustered 2 filings across 2 jurisdictions · filed Dec 28, 2018. View entity profile → Other incidents for this victim →
incident inc_06a0abc907d34d50 · 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)
MT OH
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 16, 2018
When the intrusion reportedly occurred, per the linked filings
Dental Center of Northwest Ohio reported a data breach to the Montana Attorney General. The breach was reported on 2018-12-28. The breach occurred from 8/16/2018 to 9/18/2018. 3 Montana residents were affected.
Affected (this filing): 3
Dental Center of Northwest Ohio reported to HHS on 2018-12-28 a Hacking/IT Incident (ransomware) affecting 85,874 individuals. The covered entity's business associate was the subject of a ransomware attack. PHI involved included names, addresses, dates of birth, drivers' license and Social Security numbers, claims information, diagnoses, lab results, medications, and other treatment information. Breached information located on Network Server. The CE ceased operations during OCR's investigation.
Affected (this filing): 85,874
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.