Boulder Neurosurgical and Spine Associates reported a data breach to the Montana Attorney General. The breach was reported on 2021-11-24. The breach occurred on 9/21/2021. 21 Montana residents were affected.
Affected (this filing): 21
Clustered 2 filings across 2 jurisdictions · filing window Nov 24, 2021 → Nov 29, 2021. View entity profile → Other incidents for this victim →
incident inc_084bc05b888a4b6c · 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.
CO MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 21, 2021
When the intrusion reportedly occurred, per the linked filings
Boulder Neurosurgical and Spine Associates reported a data breach to the Montana Attorney General. The breach was reported on 2021-11-24. The breach occurred on 9/21/2021. 21 Montana residents were affected.
Affected (this filing): 21
Boulder Neurosurgical and Spine Associates reported to HHS on 2021-11-29 a Hacking/IT Incident affecting 21,450 individuals. Breached information located on Email. An employee was the victim of an email phishing attack which affected the protected health information (PHI) of 21,450 individuals. The PHI involved included names, dates of birth, diagnoses, lab results, medications prescribed, and other treatment information. The CE closed its business; the investigation was subsequently closed.
Affected (this filing): 21,450
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.