Medical Center Barbour reported a data breach to the Indiana Attorney General. The breach occurred on 2023-10-24 and was reported on 2024-08-22. 53 Indiana residents were affected. 61,014 individuals affected in total.
Affected (this filing): 61,014
Clustered 2 filings across 2 jurisdictions · filed Aug 22, 2024. View entity profile → Other incidents for this victim →
incident inc_2e421cea5bcd46ab · 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.
IN ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 24, 2023
When the intrusion reportedly occurred, per the linked filings
Medical Center Barbour reported a data breach to the Indiana Attorney General. The breach occurred on 2023-10-24 and was reported on 2024-08-22. 53 Indiana residents were affected. 61,014 individuals affected in total.
Affected (this filing): 61,014
Medical Center Barbour, a healthcare organization, reported a data breach to the Maine Attorney General, affecting 3 state residents. The incident, identified as an external system breach or hacking, occurred between October 24, 2023, and October 29, 2023. The breach was discovered on January 12, 2030. Affected individuals were notified in writing on August 22, 2024, and offered 12 months of complimentary credit monitoring and identity protection services.
Affected (this filing): 3
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.