Confirmed breach. Intrusion Nov 1, 2023–Nov 30, 2023, discovered Nov 27, 2023 — the first regulatory filing landed 114 days later. 13,519 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 claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
13,519
Data types
2
Health (basic) · Identity (basic)
Jurisdictions
3
CA FEDERAL MT
Linked filings
3
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Nov 1, 2023
When the intrusion reportedly occurred, per the linked filings
Pomona Valley Hospital Medical Center reported that its business associate experienced a cybersecurity incident affecting the protected health information (PHI) of 13,516 individuals. The PHI involved included names, dates of birth, diagnoses, medications, and other treatment information. The incident was reported to HHS on March 20, 2024.
Affected (this filing): 13,516
HHS notified
🦬Montana State AGlinked via same-victim cross-source · 100%
Pomona Valley Hospital Medical Center reported a data breach to the Montana Attorney General. The breach was reported on 2024-03-22. The breach occurred from 11/1/2023 to 12/31/2023. 3 Montana residents were affected.
Affected (this filing): 3
🐻California State AGMost recentlinked via same-victim cross-source · 100%
Pomona Valley Hospital Medical Center notified patients of a security incident at a vendor's subcontractor. In late November 2023, an unauthorized third party accessed a patient-management tool and encrypted files containing protected health information (PHI), including names, medical record numbers, dates of birth, and clinical details. The hospital confirmed the breach on February 1, 2024, after the vendor provided additional information. The hospital engaged third-party experts, stopped using the affected vendor, and is assisting impacted individuals.
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.