Confirmed breach. Intrusion Jan 4, 2014–Apr 11, 2014, discovered Jun 10, 2014 — the first regulatory filing landed 66 days later. 60,582 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
60,582
Data types
2
Identity (basic) · PHI
Jurisdictions
1
TN
Linked filings
1
all HHS OCR
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 4, 2014 → Apr 11, 2014
When the intrusion reportedly occurred, per the linked filings
State of Tennessee State Insurance Plan reported to HHS on 2014-08-15 a Hacking/IT Incident affecting 60582 individuals. Breached information located on Network Server. The incident involved unauthorized access to a subcontractor's online scheduler, exposing names, dates of birth, addresses, emails, phone numbers, and genders.
Affected (this filing): 60,582
HHS notified
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.