Clustered 3 filings across 3 jurisdictions · filing window Jun 22, 2020 → Jul 1, 2020. View entity profile → Other incidents for this victim →
incident inc_1718a1d5a573424f · 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.
CA FL MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 9, 2020
When the intrusion reportedly occurred, per the linked filings
Apr 9, 2020
Reported by CALIFORNIA AG filing
Florida Orthopaedic Institute reported a data breach to the Montana Attorney General. The breach was reported on 2020-06-22. The breach occurred on 4/9/2020. 70 Montana residents were affected.
Affected (this filing): 70
Florida Orthopaedic Institute experienced a ransomware attack on or about April 6, 2020, which encrypted data on its servers. The breach impacted patient personal information, including names, dates of birth, Social Security numbers, and medical/financial data. The organization engaged forensic investigators and offered identity monitoring services through Kroll to affected individuals.
Florida Orthopaedic Institute reported to HHS on 2020-07-01 a Hacking/IT Incident affecting 651,527 individuals. Breached information located on Network Server. A ransomware attack affected protected health information (PHI) including names, addresses, dates of birth, drivers’ license numbers, claims information, diagnoses, medical conditions, laboratory results, and medications. The CE implemented additional technical safeguards and conducted employee training.
Affected (this filing): 651,527
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.