LHC Group reported to HHS on 2026-03-26 a Hacking/IT Incident affecting 8644 individuals. Breached information located on Network Server.
Affected (this filing): 8,644
Clustered 2 filings across 2 jurisdictions · filing window Mar 26, 2026 → Apr 2, 2026. View entity profile → Other incidents for this victim →
incident inc_aa66a46774194b0f · 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.
PHI · PII
LA TX
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 23, 2026
Reported by TEXAS AG filing
LHC Group reported to HHS on 2026-03-26 a Hacking/IT Incident affecting 8644 individuals. Breached information located on Network Server.
Affected (this filing): 8,644
LHC Group based in Lafayette, Louisiana, a healthcare – medical provider entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-02-23 and reported on 2026-04-02. 522 Texas residents were affected. 8,644 individuals affected in total. Types of information involved: Name of individual;Address;Medical Information;Health Insurance Information;Other;Date of Birth. Consumers were notified via Posted at company website or special website;U.S. Mail.
Affected (this filing): 522
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.