Elk Ridge Dentistry reported a data breach to the Montana Attorney General. The breach was reported on 2020-03-02. The breach occurred on 1/31/2020. 3 Montana residents were affected.
Affected (this filing): 3
Clustered 2 filings across 2 jurisdictions · filed Mar 2, 2020. View entity profile → Other incidents for this victim →
incident inc_45c7f95f03244314 · 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)
CO MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 31, 2020
When the intrusion reportedly occurred, per the linked filings
Elk Ridge Dentistry reported a data breach to the Montana Attorney General. The breach was reported on 2020-03-02. The breach occurred on 1/31/2020. 3 Montana residents were affected.
Affected (this filing): 3
Elk Ridge Dentistry (Angus Dental Solutions, Inc. dba Elk Ridge Dentistry), a healthcare provider in Colorado, reported to HHS on 2020-03-02 a Theft affecting 2,793 individuals. An unencrypted portable hard drive was stolen from a workforce member's car. The ePHI involved included names, addresses, Social Security numbers, dates of birth, diagnoses, lab results, and other treatment information. The CE notified HHS, affected individuals, and media, and implemented additional technical/security safeguards and staff retraining. OCR provided technical assistance.
Affected (this filing): 2,793
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.