University of Florida Health — February 2020 breach
Clustered 3 filings across 3 jurisdictions · filing window Aug 12, 2020 → Aug 14, 2020. View entity profile → Other incidents for this victim →
incident inc_868f312ddbc640aa · merged by deterministic · confidence 100%
Litigation Timing
Discovered → first regulatory filing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- AUG 12MT AGMT AG noticefirst filing · 11 MT residentsauto-linkedday 0
- AUG 13NH AGNH AG notice34 NH residentsauto-linked+1d
- AUG 14HHS OCRHHS OCR noticemost recent · states nationwide total 135,959auto-linked+2d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Feb 1, 2020 MT AG
- Discovered
- Jul 16, 2020· 166d undetected MT AG + NH AG
- Data types
- Identity (basic) · Health (basic) MT AG + NH AG + HHS OCR
- Attack vector
- Ransomware MT AG
- Response
- Began an investigation to understand whether any data was compromised and assess the impact · Hired ID Experts to provide MyIDCare identity theft protection services · Established required and necessary communications to customers and regulatory officials MT AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Count reconciliation
per-state reported counts
Nationwide (stated in a filing)
135,959
Sum of filed state slices
45· 0.0% of stated
100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
2 days
Cadence
~1 / 1d
vs. multi-state median
2.5× faster
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.