Confirmed breach. Intrusion Dec 17, 2019–Jan 14, 2020, discovered Jan 14, 2020 — the first regulatory filing landed 59 days later. 2,999 individuals reported across the linked filings.
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.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
2,999
Data types
3
PHI · Health (basic) · Identity (basic)
Jurisdictions
2
CA MA
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Dec 17, 2019 → Jan 14, 2020
When the intrusion reportedly occurred, per the linked filings
Breach discoveredletter-grounded
Jan 14, 2020
Reported by CALIFORNIA AG filing
59 days
🏛️MASSACHUSETTSHHS OCRFirst filinglinked via same-victim cross-source · 100%
Foundation Medicine, Inc. reported to HHS on 2020-03-13 a Hacking/IT Incident affecting 2999 individuals. Breached information located on Email. An employee was victim of an email phishing scheme affecting ePHI including names, SSNs, DOB, and clinical/treatment info. The CE implemented safeguards and retrained workforce.
Affected (this filing): 2,999
🐻California State AGMost recentlinked via same-victim cross-source · 100%
Foundation Medicine, Inc. notified the California AG of an email account compromise. An employee fell victim to phishing, resulting in unauthorized access to their email account on December 17, 2019 and January 14, 2020. The affected mailbox contained patient PHI including full name, date of birth, age, test name, ordering physician, and an FMI-assigned ID number. Financial data and SSNs were not involved.
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.