Baptist Health reported a data breach to the Indiana Attorney General. The breach occurred on 2024-04-22 and was reported on 2024-09-30. 1 Indiana residents were affected. 1,823 individuals affected in total.
Affected (this filing): 1,823
Clustered 2 filings across 2 jurisdictions · filing window Sep 30, 2024 → Oct 2, 2024. View entity profile → Other incidents for this victim →
incident inc_02a1e2dbdff44557 · 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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 22, 2024
When the intrusion reportedly occurred, per the linked filings
Jul 8, 2024
Reported by NEW HAMPSHIRE AG filing
Baptist Health reported a data breach to the Indiana Attorney General. The breach occurred on 2024-04-22 and was reported on 2024-09-30. 1 Indiana residents were affected. 1,823 individuals affected in total.
Affected (this filing): 1,823
Baptist Health notified the NH Attorney General of a security incident at Baptist Health Medical Center-Drew County. Unauthorized access occurred between April 22 and July 8, 2024, affecting employee and dependent PII. Baptist Health became aware on July 8, 2024, engaged forensic investigators, notified law enforcement, and mailed notifications to 1 NH resident on Sept 30, 2024, offering Experian IdentityWorks.
Affected (this filing): 1
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.