Clustered 2 filings across 2 jurisdictions · filed Mar 28, 2024. View entity profile → Other incidents for this victim →
incident inc_46327294cd9d403c · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Government ID · Health (basic)
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
NH VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 3, 2023 → Oct 6, 2023
When the intrusion reportedly occurred, per the linked filings
Oct 5, 2023
Reported by VERMONT AG, NEW HAMPSHIRE AG filings
Northern Virginia Oral, Maxillofacial & Implant Surgery notified consumers of a data breach occurring Oct 3-6, 2023, discovered Oct 5, 2023. Unauthorized access likely involved stolen credentials. Impacted data included names, driver's license numbers, medical/health insurance info. The company engaged forensic experts, notified law enforcement, and offered 12-24 months of Experian credit monitoring.
Northern Virginia Oral, Maxillofacial & Implant Surgery (NOVA OMS) notified the New Hampshire Attorney General on March 28, 2024, of a data security incident. An unknown criminal actor gained unauthorized access to NOVA OMS's network between October 3 and 6, 2023. The breach potentially exposed personal information (names, driver's license numbers) and protected health information for 2 New Hampshire residents. NOVA OMS engaged a cybersecurity firm, notified the FBI, and offered credit monitoring services.
Affected (this filing): 2
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.