Mat-Su Surgical Associates, APC reported a data breach to the Montana Attorney General. The breach was reported on 2020-05-15. The breach occurred on 3/16/2020. 15 Montana residents were affected.
Affected (this filing): 15
Clustered 2 filings across 2 jurisdictions · filed May 15, 2020. View entity profile → Other incidents for this victim →
incident inc_d6556770d6ad40cb · 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.
AK MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 16, 2020
When the intrusion reportedly occurred, per the linked filings
Mat-Su Surgical Associates, APC reported a data breach to the Montana Attorney General. The breach was reported on 2020-05-15. The breach occurred on 3/16/2020. 15 Montana residents were affected.
Affected (this filing): 15
Mat-Su Surgical Associates, APC (AK) reported to HHS on 2020-05-15 a ransomware attack (Hacking/IT Incident) affecting the ePHI of 13,146 individuals on a Network Server. Exposed data included names, addresses, dates of birth, Social Security numbers, diagnoses, medications prescribed, and claims information. The CE notified HHS, affected individuals, and the media, and provided complimentary credit monitoring. Additional technical safeguards were implemented; OCR provided HIPAA Security Rule technical assistance.
Affected (this filing):
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.