Atrium Health reported a data breach to the Montana Attorney General. The breach was reported on 2020-09-01. The breach occurred from 2/7/2020 to 5/20/2020. 9 Montana residents were affected.
Affected (this filing): 9
Clustered 2 filings across 2 jurisdictions · filed Sep 1, 2020. View entity profile → Other incidents for this victim →
incident inc_8a8335b1f0cf4852 · 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.
MT NC
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 7, 2020
When the intrusion reportedly occurred, per the linked filings
Atrium Health reported a data breach to the Montana Attorney General. The breach was reported on 2020-09-01. The breach occurred from 2/7/2020 to 5/20/2020. 9 Montana residents were affected.
Affected (this filing): 9
Atrium Health (NC) reported to HHS on 2020-09-01 a Hacking/IT Incident (ransomware) affecting 165,000 individuals. The breach occurred at a business associate and involved ePHI stored on a network server. Exposed data included names, addresses, dates of birth, and treatment information. The CE notified HHS, affected individuals, the media, and posted substitute notice on its website.
Affected (this filing): 165,000
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.