Clustered 3 filings across 2 jurisdictions · filing window Jun 8, 2024 → Jul 19, 2024. View entity profile → Other incidents for this victim →
incident inc_6830973521584750 · merge_method human · confidence 100%
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IN
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 2, 2024
When the intrusion reportedly occurred, per the linked filings
At Barrett Eye Care we pride ourselves on being a full service, comprehensive, ophthalmology clinic. We are equipped to handle the full spectrum ofeye problems ranging from complex medical eye diseases to routine eye exams. We provide multiple services and procedures which can help our patients to see better and enjoy a higher quality of life.
Barrett Eye Care (Indiana) reported to HHS OCR on 2024-07-19 a ransomware incident affecting the PHI of 4,648 individuals. Breached information was located on a Network Server. PHI involved demographic and financial information. The CE notified HHS, affected individuals, the media, and posted substitute notice in a major print publication. In response, the CE implemented additional administrative, technical, and security safeguards.
Barrett Eye Care reported a data breach to the Indiana Attorney General. The breach occurred on 2024-06-02 and was reported on 2024-07-19. 1,685 Indiana residents were affected. 1,694 individuals affected in total.
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.
Affected (this filing): 4,648