Confirmed breach. Intrusion Aug 8, 2022, discovered Aug 9, 2022 — the first regulatory filing landed 57 days later (flagged late). 8,022 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)
8,022
Data types
—
Jurisdictions
1
OR
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 8, 2022
When the intrusion reportedly occurred, per the linked filings
CareOregon reported a data breach to the Oregon Attorney General. The breach was reported on 2022-10-05. The breach occurred during 8/8/2022 - 8/8/2022. The breach was discovered on 8/9/2022. 8,022 individuals were affected. Notice was sent on 9/26/2022.
Affected (this filing): 8,022
OR AG >45d
🦫OREGONHHS OCRMost recentlinked via same-victim cross-source · 100%
CareOregon (OR, Health Plan) reported to HHS on 2022-10-05 an Unauthorized Access/Disclosure affecting 8,022 individuals. Due to an error in its mail merging system, the CE mailed PHI — including names and health insurance information — to unintended recipients. Breached information was located on Paper/Films. The CE corrected the mail merging system and implemented additional administrative and technical safeguards, and notified HHS, affected individuals, and the media.
Affected (this filing): 8,022
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.