Peak Vista Community Health Centers reported a data breach to the Montana Attorney General. The breach was reported on 2021-04-23. The breach occurred on 3/7/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Apr 23, 2021 → Apr 26, 2021. View entity profile → Other incidents for this victim →
incident inc_a06bad0c05234240 · 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.
Health (basic) · Identity (basic)
CO MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 7, 2021
When the intrusion reportedly occurred, per the linked filings
Peak Vista Community Health Centers reported a data breach to the Montana Attorney General. The breach was reported on 2021-04-23. The breach occurred on 3/7/2021. 1 Montana residents were affected.
Affected (this filing): 1
Peak Vista Community Health Centers (Colorado) reported to HHS on 2021-04-26 that two desktop computers containing ePHI of 3,118 individuals were stolen from its facility. Exposed ePHI included names, dates of birth, diagnoses/conditions, and medications prescribed. The CE notified HHS, affected individuals, and the media, and provided complimentary credit monitoring. Additional technical, administrative, and physical safeguards were implemented. OCR provided HIPAA Security Rule technical assistance.
Affected (this filing): 3,118
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.