Confirmed breach. Intrusion Feb 6, 2021, discovered Feb 19, 2021 — the first regulatory filing landed 123 days later. 2,042 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 clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
2,042
Data types
3
Identity (basic) · Government ID · Health (basic)
Jurisdictions
1
CA
Linked filings
2
HHS OCR · State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 6, 2021
When the intrusion reportedly occurred, per the linked filings
Breach discoveredletter-grounded
Feb 19, 2021
Reported by CALIFORNIA AG filing
123 days
🐻CALIFORNIAHHS OCRFirst filinglinked via same-victim cross-source · 100%
Tiburcio Vasquez Health Center Inc. reported to HHS on 2021-06-22 a Hacking/IT Incident affecting 2042 individuals. Breached information located on Network Server. A business associate suffered the breach, exposing ePHI including names, dates of birth, and medications. The CE notified HHS, affected individuals, and the media.
Affected (this filing): 2,042
🐻California State AGMost recentlinked via same-victim cross-source · 100%
Tiburcio Vasquez Health Center Inc. notified the California AG of a security incident involving its vendor, CaptureRx. Unauthorized access occurred on Feb 6, 2021, and was discovered on Feb 19, 2021. Affected data included names, dates of birth, and prescription information (PHI). CaptureRx investigated, secured systems, and is enhancing policies and training.
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.