Clustered 3 filings across 3 jurisdictions · filed Aug 25, 2022. View entity profile → Other incidents for this victim →
incident inc_bb94b3cd131245aa · 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.
ME MT NC
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 18, 2022
When the intrusion reportedly occurred, per the linked filings
Aug 19, 2022
Reported by MAINE AG filing
EmergeOrtho reported a data breach to the Montana Attorney General. The breach was reported on 2022-08-25. The breach occurred on 5/18/2022. 7 Montana residents were affected.
Affected (this filing): 7
EmergeOrtho, a healthcare provider, reported a data breach affecting 75,200 individuals. The breach, which occurred on May 18, 2022, and was discovered on August 19, 2022, was described as an external system breach or hacking incident. The compromised information included names combined with financial account or credit/debit card numbers along with their security codes, access codes, passwords, or PINs. EmergeOrtho began notifying affected individuals in writing on August 25, 2022, and offered 12 months of credit monitoring and identity theft protection services through Sontiq/Cyberscout.
Affected (this filing): 75,200
EmergeOrtho reported to HHS on 2022-08-25 a Hacking/IT Incident affecting 68,661 individuals. Breached information located on Network Server. The incident involved a ransomware attack encrypting PHI including names, addresses, DOB, driver's license numbers, SSNs, and diagnoses. The entity notified HHS, individuals, and media, and provided credit monitoring.
Affected (this filing): 68,661
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.