Clustered 3 filings across 2 jurisdictions · filed Jul 25, 2025. View entity profile → Other incidents for this victim →
incident inc_a14a3841aa634fc4 · 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.
PHI · Health (basic)
IN WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 27, 2025
When the intrusion reportedly occurred, per the linked filings
May 28, 2025
Reported by WASHINGTON AG filing
Northwest Denture Center, Inc., a health sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2025-05-28 and filed notice on 2025-07-25. 12,209 Washington residents were affected. 58 days elapsed between awareness and notification. 1 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 12,209
Northwest Denture Center, Inc. reported to HHS OCR on 2025-07-25 a Hacking/IT Incident affecting 19,419 individuals. Breached information was located on a Network Server. No business associate was present. The covered entity is a Healthcare Provider located in Washington state.
Affected (this filing): 19,419
Northwest Denture Center Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-05-27 and was reported on 2025-07-25. 1 Indiana residents were affected.
Affected (this filing): 1
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.