Eye Institute of Corpus Christi reported a data breach to the Montana Attorney General. The breach was reported on 2016-02-26. The breach occurred on 1/6/2016. 3 Montana residents were affected.
Affected (this filing): 3
Clustered 3 filings across 3 jurisdictions · filing window Feb 26, 2016 → Mar 1, 2016. View entity profile → Other incidents for this victim →
incident inc_7cc0740a314b4172 · 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 SC TX
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 6, 2016
When the intrusion reportedly occurred, per the linked filings
Eye Institute of Corpus Christi reported a data breach to the Montana Attorney General. The breach was reported on 2016-02-26. The breach occurred on 1/6/2016. 3 Montana residents were affected.
Affected (this filing): 3
Eye Institute of Corpus Christi reported to HHS on 2016-02-26 a Theft affecting 43961 individuals. Breached information located on Electronic Medical Record. OCR review determined that a breach of protected health information did not occur.
Affected (this filing): 43,961
State of South Carolina Attorney General's office received a breach notification from The Eye Institute of Corpus Christi, Inc. regarding an incident in 2016. The provided PDF extraction contains no narrative text, preventing extraction of incident details, affected counts, or data types.
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.