Clustered 2 filings across 1 jurisdiction · filing window Feb 28, 2025 → Mar 28, 2025. View entity profile → Other incidents for this victim →
incident inc_538e5e5eef054ca3 · merge_method human · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
PHI · Health (basic)
CA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 28, 2024 → Nov 11, 2024
When the intrusion reportedly occurred, per the linked filings
Nov 8, 2024
Reported by CALIFORNIA AG filing
Blue Shield of California reported to HHS on 2025-02-28 an Unauthorized Access/Disclosure affecting 624 individuals. Due to a configuration error, PHI including medications and other treatment information was viewable by others via the Internet through an Electronic Medical Record system. The CE notified HHS, affected individuals, and the media, and provided free credit monitoring.
Affected (this filing): 624
Blue Shield of California notified members that a data mismatch error in a health information exchange feed allowed family members on the same plan to potentially view each other's health records (visit types, dates, providers, medications) via the Member Portal between Oct 28 and Nov 11, 2024. The issue was identified on Nov 8, 2024, and the data feed was terminated on Nov 11, 2024. No demographic identifiers, SSNs, or financial data were exposed.
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.