BlueCross BlueShield of Tennessee, Inc. reported to HHS on 2025-12-26 a Unauthorized Access/Disclosure affecting 780 individuals. Breached information located on Email.
Affected (this filing): 780
Clustered 2 filings across 2 jurisdictions · filing window Dec 26, 2025 → Feb 11, 2026. View entity profile → Other incidents for this victim →
incident inc_5030a0d017dc41c2 · merge_method llm · confidence 62%
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.
PHI · Identity (basic)
FEDERAL TN
all HHS OCR
Earliest sighting first · deep chronology in Litigation Timeline
BlueCross BlueShield of Tennessee, Inc. reported to HHS on 2025-12-26 a Unauthorized Access/Disclosure affecting 780 individuals. Breached information located on Email.
Affected (this filing): 780
BlueCross BlueShield of Tennessee, Inc., acting as a business associate, reported a Hacking/IT Incident affecting a network server. A subcontractor of its covered entity experienced the breach, which the BA reported affected approximately 37,402 individuals overall (HHS portal row attributes 1,670 to this filing). PHI involved names and other identifiers. BCBSTN notified HHS, affected individuals, and the media, and offered free credit monitoring. OCR provided technical assistance regarding the HIPAA Rules.
Affected (this filing): 1,670
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.