Summit Eye Associates reported a data breach to the Montana Attorney General. The breach was reported on 2022-04-27. The breach occurred on 12/4/2021. 5 Montana residents were affected.
Affected (this filing): 5
Clustered 2 filings across 2 jurisdictions · filed Apr 27, 2022. View entity profile → Other incidents for this victim →
incident inc_88fd44338c1841a0 · 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.
Government ID · Identity (basic)
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 4, 2021
When the intrusion reportedly occurred, per the linked filings
Mar 1, 2022
Reported by MAINE AG filing
Summit Eye Associates reported a data breach to the Montana Attorney General. The breach was reported on 2022-04-27. The breach occurred on 12/4/2021. 5 Montana residents were affected.
Affected (this filing): 5
Summit Eye Associates, P.C., a healthcare provider based in Hermitage, TN, reported an external system breach (hacking) occurring on December 4, 2021, discovered on March 1, 2022. The incident affected 53,818 individuals, including 3 Maine residents. Acquired data included names and Social Security Numbers. The entity provided written notification and offered one year of credit monitoring and identity theft protection services through IDX.
Affected (this filing): 53,818
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.