Summit Surgical LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-03-28. The breach occurred on 10/8/2021. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Mar 28, 2022 → Mar 30, 2022. View entity profile → Other incidents for this victim →
incident inc_27484803039c41e9 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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 NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 8, 2021
When the intrusion reportedly occurred, per the linked filings
Oct 8, 2021
Reported by NEW HAMPSHIRE AG filing
Summit Surgical LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-03-28. The breach occurred on 10/8/2021. 1 Montana residents were affected.
Affected (this filing): 1
Summit Surgical, LLC, a Kansas-based physician-owned specialty hospital, notified the New Hampshire Attorney General of a cybersecurity attack detected on October 8, 2021. The incident involved a ransomware attempt by an unauthorized third party. One New Hampshire resident was potentially affected, with exposure of names, addresses, SSNs, and protected health information. Summit Surgical engaged forensic investigators, worked with law enforcement, and offered 12 months of credit monitoring and identity theft protection.
Affected (this filing): 1
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.