Confirmed breach. Intrusion Jul 22, 2019–Jul 30, 2019, discovered Jul 29, 2019 — the first regulatory filing landed 60 days later (flagged late). 3,290 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 clocksOregon✗ OR AG >45dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
3,290
Data types
—
Jurisdictions
2
GA OR
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jul 22, 2019 → Jul 30, 2019
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Jul 29, 2019
Reported by OREGON AG filing
60 days
🦫Oregon State AGFirst filinglinked via same-victim cross-source · 100%
Cancer Treatment Centers of America at Southeastern Regional Medical Center reported a data breach to the Oregon Attorney General. The breach was reported on 2019-09-27. The breach occurred during 7/22/2019 - 7/30/2019. The breach was discovered on 7/29/2019. 3,290 individuals were affected. Notice was sent on 9/27/2019.
Affected (this filing): 3,290
🇺🇸GAHHS OCRMost recentlinked via same-victim cross-source · 100%
Cancer Treatment Centers of America (CTCA) at Southeastern Regional Medical Center reported to HHS on 2019-09-27 a Hacking/IT Incident affecting 3290 individuals. Breached information located on Email. Employees were victims of an email phishing scheme exposing ePHI including names, SSNs, DOB, financial and clinical data. CE implemented safeguards and retrained staff.
Affected (this filing): 3,290
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.