Clustered 2 filings across 1 jurisdiction · filing window Mar 30, 2018 → Apr 2, 2018. View entity profile → Other incidents for this victim →
incident inc_6534114c463d448c · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
Identity (basic) · Health (basic)
CA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 8, 2018
When the intrusion reportedly occurred, per the linked filings
Mar 8, 2018
Reported by HHS OCR filing
Mar 16, 2018
Reported by CALIFORNIA AG filing
Sonoma County Indian Health Project, Inc reported to HHS on 2018-03-30 a Unauthorized Access/Disclosure affecting 662 individuals. Breached information located on Desktop Computer, Email. A former employee sent ePHI (demographic and clinical) to personal email.
Affected (this filing): 662
Sonoma County Indian Health Project, Inc. disclosed that a former employee sent an unencrypted email containing patient names, dates of birth, appointment dates, and some health information to their personal email address. The incident was discovered on March 16, 2018, with the breach occurring on March 8, 2018. The organization deleted the email and offered one year of credit monitoring to affected 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.