Clustered 2 filings across 1 jurisdiction · filed Feb 22, 2013. View entity profile → Other incidents for this victim →
incident inc_0e77cdaa9edb4491 · merge_method deterministic · confidence 100%
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.
Health (basic) · Identity (basic)
CA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 28, 2012
When the intrusion reportedly occurred, per the linked filings
Crescent Health Inc. (a Walgreens Company), a healthcare provider in California, reported to HHS OCR on 2013-02-22 a theft incident affecting 109,000 individuals. The breached information was located on a Desktop Computer. No business associate was identified as present. The entity operates as a Walgreens subsidiary, suggesting a retail pharmacy context.
Affected (this filing): 109,000
Crescent Health Inc. (a Walgreen Company) reported a data breach to the California Attorney General. The incident occurred on December 28, 2012. The filing includes sample patient and employee notification letters, indicating that both customer and employee data were potentially affected. Specific details regarding the nature of the breach, number of individuals affected, and data types are not present in the provided HTML summary or attachment text.
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.