Eye Institute of Marin reported a data breach to the Montana Attorney General. The breach was reported on 2016-11-16. The breach occurred from 7/26/2016 to 7/27/2016. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Nov 16, 2016 → Nov 18, 2016. View entity profile → Other incidents for this victim →
incident inc_3746bc65aeff4183 · 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.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 26, 2016
When the intrusion reportedly occurred, per the linked filings
Jul 27, 2016
Reported by CALIFORNIA AG filing
Eye Institute of Marin reported a data breach to the Montana Attorney General. The breach was reported on 2016-11-16. The breach occurred from 7/26/2016 to 7/27/2016. 1 Montana residents were affected.
Affected (this filing): 1
Eye Institute of Marin, a California healthcare provider, disclosed a ransomware incident affecting its electronic medical record provider, Marin Medical Practice Concepts, Inc. (MMPC). The attack occurred July 26-27, 2016. While no patient data was accessed, consultation notes from July 11-26 were lost due to backup failure. Patient PII (names, SSNs, DOB) and PHI were at risk. The provider secured its network and notified law enforcement.
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.