Jefferson Dental Center Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-11-14 and was reported on 2024-11-18. 74 Indiana residents were affected. 75 individuals affected in total.
Affected (this filing): 75
Clustered 2 filings across 1 jurisdiction · filing window Nov 18, 2024 → Nov 27, 2024. View entity profile → Other incidents for this victim →
incident inc_f3eb163d0fea4da2 · merge_method deterministic · confidence 100%
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)
IN
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 14, 2024
When the intrusion reportedly occurred, per the linked filings
Jefferson Dental Center Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-11-14 and was reported on 2024-11-18. 74 Indiana residents were affected. 75 individuals affected in total.
Affected (this filing): 75
Jefferson Dental Center, Inc. (Indiana) reported to HHS on 2024-11-27 a ransomware incident affecting 12,340 individuals. Breached information was located on a Network Server and included treatment information (PHI). The CE notified HHS and affected individuals, provided substitute notice, and implemented additional administrative, technical, and security safeguards, and retrained workforce members.
Affected (this filing): 12,340
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.