Clustered 2 filings across 1 jurisdiction · filing window Sep 30, 2019 → Oct 4, 2019. View entity profile → Other incidents for this victim →
incident inc_2c2cc8699d1b4d32 · 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
Jul 25, 2019
When the intrusion reportedly occurred, per the linked filings
Aug 1, 2019
Reported by CALIFORNIA AG filing
Sep 30, 2019
Reported by HHS OCR filing
Telecare Corporation reported to HHS on 2019-09-30 a Hacking/IT Incident affecting 823 individuals. Breached information located on Email. An employee was the victim of an email phishing scheme that affected electronic protected health information (ePHI) including names, birthdates, financial information, and clinical/treatment data.
Affected (this filing): 823
Telecare Corporation experienced a business email compromise (BEC) attempt in August 2019. Imposters sent fraudulent emails to vendors and business contacts, attempting to redirect payments. An unauthorized party accessed one Telecare email account, potentially exposing limited personal information including names, medical information, and health insurance information for some individuals. The motive was financial. Telecare alerted authorities, vendors, and customers, and is implementing additional safeguards.
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.