Confirmed breach. discovered Oct 8, 2025 — the first regulatory filing landed 61 days later (flagged late). 69,740 individuals reported across the linked filings.
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.
Regulatory clocksTexas✗ TX AG >30dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
69,740
Data types
1
PHI
Jurisdictions
1
TX
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
HHS OCR breach portal entry: Vida Y Salud-Health Systems, Inc. (TX, Healthcare Provider) reported a Hacking/IT Incident affecting 35,236 individuals; breached information located on a Network Server. Submitted 2025-12-08. No business associate involved. No further narrative provided in the listing row.
Vida Y Salud-Health Systems, Inc., based in Crystal City, Texas, a healthcare – medical provider entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-10-08 and reported on 2026-01-05. 34,504 Texas residents were affected. 34,661 individuals affected in total. Types of information involved: Social Security Number Information;Driver’s License number;Financial Information (e.g. account number, credit or debit card number);Health Insurance Information;Date of Birth. Consumers were notified via Posted at company website or special website;U.S. Mail.
Affected (this filing): 34,504
TX AG >30d
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.