Clustered 3 filings across 1 jurisdiction · filed Aug 15, 2019. View entity profile → Other incidents for this victim →
incident inc_7a0ba05381a74119 · merge_method llm · 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.
Identity (basic) · Government ID · Health (basic)
WA
all HHS OCR
Earliest sighting first · deep chronology in Litigation Timeline
Community Psychiatric Clinic reported to HHS on 2019-08-15 a Hacking/IT Incident affecting 5,866 individuals. Breached information located on Email. The incident involved an email phishing scheme that exposed ePHI including names, SSNs, addresses, diagnoses, lab results, medications, and financial data. The clinic retrained staff and implemented technical safeguards.
Affected (this filing): 5,866
Community Psychiatric Clinic reported to HHS on 2019-08-15 a Hacking/IT Incident affecting 3030 individuals. Breached information located on Email. The incident involved an email phishing scheme that exposed electronic protected health information (ePHI), including names, SSNs, addresses, birthdates, diagnoses, lab results, medications, claims, and financial data. The clinic retrained staff on identifying fraudulent emails and implemented additional technical safeguards.
Affected (this filing): 3,030
Community Psychiatric Clinic (WA) reported to HHS on 2019-08-15 a Hacking/IT Incident affecting 6,641 individuals. The CE was the victim of an email phishing scheme compromising ePHI including names, Social Security numbers, addresses, birthdates, diagnoses/conditions, lab results, medications, claims information, and financial data. Following OCR investigation, the CE retrained workforce on identifying fraudulent emails and implemented additional technical safeguards. Breached information located in Email systems.
Affected (this filing): 6,641
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.