Health Fitness Corporation, a Business Associate in Illinois, reported the theft of a laptop containing the personal information of 4,837 individuals. The breach was submitted to HHS on November 14, 2013.
Affected (this filing): 4,837
Clustered 2 filings across 1 jurisdiction · filed Nov 14, 2013. View entity profile → Other incidents for this victim →
incident inc_4ead4e109b3a400e · merge_method llm · confidence 60%
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.
Health (basic) · Identity (basic) · Government ID
IL
all HHS OCR
Earliest sighting first · deep chronology in Litigation Timeline
Health Fitness Corporation, a Business Associate in Illinois, reported the theft of a laptop containing the personal information of 4,837 individuals. The breach was submitted to HHS on November 14, 2013.
Affected (this filing): 4,837
Health Fitness Corporation (a Business Associate, IL) reported to HHS on 2013-11-14 a Theft affecting 3,804 individuals. An unencrypted company laptop was stolen from a BA employee's car. The laptop contained PHI including employee and/or spouse names, birthdates, health plan elections, and Social Security numbers. The CE notified HHS; the BA notified affected individuals and media. Corrective actions included mandatory laptop encryption policies, employee training, and a BA certification process for encrypted mobile devices. OCR obtained assurances that all corrective actions were taken. Breached information located on Laptop.
Affected (this filing): 3,804
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.