Confirmed breach. Intrusion Feb 1, 2018–May 31, 2018, discovered May 31, 2018 — the first regulatory filing landed 127 days later. 42,000 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
42,000
Data types
4
PHI · Health (basic) · Identity (basic)
Jurisdictions
1
FL
Linked filings
1
all HHS OCR
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 1, 2018 → May 31, 2018
When the intrusion reportedly occurred, per the linked filings
Health First, Inc reported to HHS on 2018-10-05 a Hacking/IT Incident affecting 42000 individuals. Breached information located on Email. A phishing attack compromised 38 email accounts beginning in February 2018, affecting the PHI of 41,810 individuals.
Affected (this filing): 42,000
HHS notified
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.