Clustered 4 filings across 4 jurisdictions · filing window Aug 14, 2024 → Jun 30, 2025. View entity profile → Other incidents for this victim →
incident inc_3e5213ec468040a0 · 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.
IN NH TX
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 13, 2024
When the intrusion reportedly occurred, per the linked filings
Jul 19, 2024
Reported by NEW HAMPSHIRE AG filing
TCIDA is a private infectious disease group serving the entire DFW metroplex - Dallas and Fort Worth - with brand new buildings in both cities, infusion centers in both cities, and its own pharmacy.
Texas Centers for Infectious Disease Associates reported a data breach to the Indiana Attorney General. The breach occurred on 2024-07-13 and was reported on 2025-06-26. 11 Indiana residents were affected. 19,776 individuals affected in total.
Texas Centers for Infectious Disease Associates (TCIDA) notified the New Hampshire Attorney General on June 26, 2025, of a data security incident affecting 1 NH resident. TCIDA detected unusual network activity on July 19, 2024, which was linked to a compromise of a former third-party billing vendor. The incident may have exposed names, SSNs, DOBs, driver's license numbers, and medical/insurance information. TCIDA engaged forensic experts, notified the FBI, and provided identity protection services to affected individuals.
Texas Center for Infectious Disease Associates (TX) reported to HHS OCR on 2025-06-30 a Hacking/IT Incident affecting 19,481 individuals. Breached information was located on a Network Server. No business associate was identified as involved. No further detail is available from the HHS web description.
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): 19,776
Affected (this filing): 1
Affected (this filing): 19,481