Clustered 2 filings across 2 jurisdictions · filed Dec 18, 2020. View entity profile → Other incidents for this victim →
incident inc_7c54d761e58c4182 · merge_method deterministic · 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.
Identity (basic) · Government ID
ME TN
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 24, 2020 → Jul 1, 2020
When the intrusion reportedly occurred, per the linked filings
Nov 9, 2020
Reported by MAINE AG filing
BlueCross BlueShield of Tennessee, Inc. reported to HHS on 2020-12-18 a Hacking/IT Incident affecting 1340 individuals. Breached information located on Email. A business associate employee was victim of an email phishing scheme exposing ePHI including names, addresses, SSNs, and treatment info.
Affected (this filing): 1,340
BlueCross BlueShield of Tennessee, Inc. reported a data breach affecting 3 Maine residents. The breach was discovered on November 9, 2020, and occurred between June 24, 2020, and July 1, 2020. The breach was due to unauthorized access at their vendor, EyeMed. The information acquired includes names and Social Security Numbers. Identity theft protection services are being offered for 2 years through Experian.
Affected (this filing): 3
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.