Clustered 4 filings across 3 jurisdictions · filing window Nov 24, 2024 → Mar 25, 2025. View entity profile → Other incidents for this victim →
incident inc_2785d22e128e44da · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IN NH
Leak Site · HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 21, 2024
When the intrusion reportedly occurred, per the linked filings
Nov 21, 2024
Reported by NEW HAMPSHIRE AG filing
Medical records and personal data of all patients from 2018 More than 30,000 identity documents https://www.concordortho.com/ Company representative should follow the instructions to contact us before time runs out
Concord Orthopaedics reported to HHS on 2025-03-25 a Hacking/IT Incident affecting 72815 individuals. Breached information located on Network Server.
Concord Orthopaedics reported a data breach to the Indiana Attorney General. The breach occurred on 2024-11-21 and was reported on 2025-03-25. 12 Indiana residents were affected. 73 individuals affected in total.
Affected (this filing): 73
Concord Orthopaedics notified patients that an unauthorized actor accessed a third-party patient registration software on November 21, 2024. Potentially impacted data includes names, DOBs, SSNs, appointment info, health insurance details, and driver's license images. Concord engaged forensic specialists, reset passwords, notified law enforcement, and offered 12 months of credit monitoring.
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.
Affected (this filing): 72,815