DentaQuest reported to HHS on 2026-05-22 a Unauthorized Access/Disclosure affecting 3086 individuals. Breached information located on Network Server. Business Associate present: Yes.
Affected (this filing): 3,086
Clustered 2 filings across 2 jurisdictions · filed May 22, 2026. View entity profile → Other incidents for this victim →
incident inc_825f80b336d24d81 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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)
MA NH
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 27, 2026
When the intrusion reportedly occurred, per the linked filings
Mar 30, 2026
Reported by NEW HAMPSHIRE AG filing
DentaQuest reported to HHS on 2026-05-22 a Unauthorized Access/Disclosure affecting 3086 individuals. Breached information located on Network Server. Business Associate present: Yes.
Affected (this filing): 3,086
DentaQuest, a dental benefits provider, notified the New Hampshire Attorney General of a data security incident involving 3,086 NH residents. On March 27, 2026, a CMS Prior Authorization Interoperability Report was posted to DentaQuest.com containing a second tab with member-level PII, including names and Medicaid/Medicare ID numbers. DentaQuest discovered the error on March 30, 2026, removed the report, and notified HHS. Notices were mailed to affected individuals on May 22, 2026. No evidence of misuse was found.
Affected (this filing): 3,086
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.