Clustered 4 filings across 1 jurisdiction · filed Jan 27, 2026. View entity profile → Other incidents for this victim →
incident inc_afc4f0c9fafb4b3a · 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.
Health (basic)
IN
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 22, 2025
When the intrusion reportedly occurred, per the linked filings
WindRose Health Network reported a data breach to the Indiana Attorney General. The breach occurred on 2025-08-22 and was reported on 2026-01-27. 681 Indiana residents were affected. 691 individuals affected in total.
Affected (this filing): 691
WindRose Health Network reported a data breach to the Indiana Attorney General. The breach occurred on 2025-08-22 and was reported on 2026-01-27. 681 Indiana residents were affected. 691 individuals affected in total.
Affected (this filing): 691
WindRose Health Network reported to HHS on 2026-01-27 a Hacking/IT Incident affecting 9087 individuals. Breached information located on Network Server.
Affected (this filing): 9,087
WindRose Health Network (Indiana) reported to HHS OCR on 2026-01-27 a Hacking/IT Incident affecting 691 individuals. Breached information was located on a Network Server. No business associate was identified as involved. No further detail is available from the HHS portal web description.
Affected (this filing): 691
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.