Clustered 3 filings across 3 jurisdictions · filing window Oct 7, 2023 → Dec 11, 2023. View entity profile → Other incidents for this victim →
incident inc_929ea11717b14f33 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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.
Identity (basic) · Government ID · Financial account
TX VT
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 8, 2023 → Sep 12, 2023
When the intrusion reportedly occurred, per the linked filings
Sep 12, 2023
Reported by VERMONT AG filing
Healix provides physician office-based infusion services. We obtained 642Gb of this company data and there is a probability that the files will be available here for downloading next week. Complete personal information set with medical records of thousands patients could be found in the data. Medical staff personal info is presented as well, Wait for the update.
Healix Infusion Therapy, LLC (TX) reported to HHS OCR on 2023-12-11 a Hacking/IT Incident affecting 10,277 individuals. Breached information was located on a Network Server. A business associate was present. No further detail is available from the HHS portal web description.
Healix Infusion Therapy, LLC notified consumers of a data breach occurring between Sept 8-12, 2023. Unauthorized access compromised PHI, SSNs, financial data, and government IDs. The company engaged forensic specialists, notified law enforcement, and offered credit monitoring. Investigation is ongoing; exact count of affected individuals is not yet determined.
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): 10,277