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)
49,000
Data types
2
PII · PHI
Jurisdictions
1
CA
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Sep 25, 2013
When the intrusion reportedly occurred, per the linked filings
58 days
🐻CALIFORNIAHHS OCRFirst filinglinked via same-victim cross-source · 100%
Kaiser Foundation Hospital- Orange County reported to HHS on 2013-11-22 a Loss affecting 49000 individuals. Breached information located on Other Portable Electronic Device. The CE misplaced a portable computer drive containing PHI (names, DOB, medications) and subsequently phased out flash drives and moved PHI to secured servers.
Kaiser Foundation Hospital Orange County, Anaheim Medical Center reported a data breach to the California Attorney General on September 25, 2013. The incident date is listed as September 25, 2013. The filing includes a patient notification letter, indicating that protected health information (PHI) and personally identifiable information (PII) of patients were likely involved. Specific details regarding the cause, scope, and number of affected individuals are not available in the provided HTML summary; the attachment text was empty.
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.