Clustered 2 filings across 2 jurisdictions · filing window Jul 2, 2026 → Jul 7, 2026. View entity profile → Other incidents for this victim →
incident inc_22e1a1caa5874781 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PHI · PII
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
CA TX
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 16, 2026
Reported by CALIFORNIA AG filing
Apr 17, 2026
When the intrusion reportedly occurred, per the linked filings
Apr 17, 2026
Reported by TEXAS AG filing
TriWest Healthcare Alliance discovered unauthorized activity on its network on April 16, 2026. An unauthorized person accessed and downloaded information including names, DoD benefits numbers, ZIP codes, and authorization request types. The company contained the incident, engaged experts, and reported to authorities. Affected individuals are offered 24 months of identity monitoring.
TriWest Healthcare Alliance based in Tampa, Florida, a other entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-04-17 and reported on 2026-07-07. 2,408 Texas residents were affected. 11,844 individuals affected in total. Types of information involved: Name of individual;Health Insurance Information;Other. Consumers were notified via Notice by publication in print media;U.S. Mail.
Affected (this filing): 2,408
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.