Clustered 3 filings across 3 jurisdictions · filed Nov 15, 2024. View entity profile → Other incidents for this victim →
incident inc_724fd34975a747ab · 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 IL MT
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 31, 2024
When the intrusion reportedly occurred, per the linked filings
Aug 1, 2024
Reported by CALIFORNIA AG filing
Option Care Health reported to HHS on 2024-11-15 a Hacking/IT Incident affecting 2897 individuals. Breached information located on Email. An employee was the subject of an email phishing scheme that compromised PHI including SSNs, birthdates, addresses, and diagnoses.
Affected (this filing): 2,897
Option Care Health reported a data breach to the Montana Attorney General. The breach was reported on 2024-11-15. The breach occurred from 07/31/2024 to 08/01/2024. 17 Montana residents were affected.
Affected (this filing): 17
Option Care Health notified patients that an unknown party briefly accessed an employee's email inbox on July 31, 2024. The company became aware of the issue on August 1, 2024, and terminated access. Forensic analysis determined that Protected Health Information (PHI) and basic identity information may have been impacted. The company reset passwords, restricted access, and engaged Kroll for identity monitoring services.
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.