Choice Cancer Care reported a data breach to the Montana Attorney General. The breach was reported on 2019-11-15. The breach occurred from 5/1/2019 to 5/21/2019. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Nov 15, 2019. View entity profile → Other incidents for this victim →
incident inc_f048fc55bb5446d4 · merge_method deterministic · confidence 100%
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.
Identity (basic) · Government ID · Health (basic)
MT TX
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 1, 2019
When the intrusion reportedly occurred, per the linked filings
Choice Cancer Care reported a data breach to the Montana Attorney General. The breach was reported on 2019-11-15. The breach occurred from 5/1/2019 to 5/21/2019. 1 Montana residents were affected.
Affected (this filing): 1
Choice Cancer Care (TX) reported to HHS OCR on 2019-11-15 a Hacking/IT Incident — email phishing scheme — affecting 14,673 individuals. An employee was the victim of a phishing attack, exposing ePHI via Email, including names, dates of birth, driver's license numbers, Social Security numbers, claims information, diagnoses/conditions, and treatment information. The CE notified HHS, affected individuals, and the media, and subsequently improved technical/administrative safeguards, retrained staff, and updated email security. OCR obtained assurances of corrective action.
Affected (this filing): 14,673
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.