Clustered 3 filings across 3 jurisdictions · filed Apr 2, 2019. View entity profile → Other incidents for this victim →
incident inc_a28f828eb98f4e6a · 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.
Identity (basic) · Health (basic) · Government ID
FEDERAL MT OR
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 9, 2018 → Nov 26, 2018
When the intrusion reportedly occurred, per the linked filings
Feb 11, 2019
Reported by OREGON AG filing
Oregon Endodontic Group reported a data breach to the Oregon Attorney General. The breach was reported on 2019-04-02. The breach occurred during 11/9/2018 - 11/26/2018. The breach was discovered on 2/11/2019. 2,952 individuals were affected. Notice was sent on 4/2/2019.
Affected (this filing): 2,952
Oregon Endodontic Group reported to HHS on April 2, 2019, that an email phishing scheme affected 2,952 individuals. The exposed information included names, birthdates, diagnoses, health insurance details, driver's license numbers, financial information, and Social Security numbers. The breach was located within the email system. In response, the entity enhanced its security safeguards, retrained staff on identifying fraudulent emails, and received technical assistance from the Office for Civil Rights (OCR).
Affected (this filing): 2,952
Oregon Endodontic Group reported a data breach to the Montana Attorney General. The breach was reported on 2019-04-02. The breach occurred from 11/9/2018 to 11/13/2018. 1 Montana 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.