Clustered 4 filings across 2 jurisdictions · filing window Sep 19, 2023 → Oct 22, 2024. View entity profile → Other incidents for this victim →
incident inc_8c22adb3a90542c5 · merge_method deterministic · confidence 100%
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
ME
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 19, 2023
When the intrusion reportedly occurred, per the linked filings
Our mission is to improve the lives of children and adults in our communities by providing needed, accessible, comprehensive, quality oral health care.We have personal data of clients, accounting information, medical data of clients, their medica...
Community Dental reported to HHS on 2023-11-17 a Hacking/IT Incident affecting 1523 individuals. Breached information located on Network Server.
Our mission is to improve the lives of children and adults in our communities by providing needed, accessible, comprehensive, quality oral health care.We have personal data of clients, accounting information, medical data of clients, their medica...
Sep 10, 2024
Reported by MAINE AG filing
Community Dental, a healthcare organization, reported an external system breach (hacking) that occurred on September 19, 2023. The breach was discovered on September 10, 2024 and affected 270 Maine residents. In response, the company offered Experian credit monitoring and identity restoration services to those affected.
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.
Affected (this filing): 1,523
Affected (this filing): 270