Confirmed breach. Intrusion Jan 14, 2022, discovered Oct 21, 2022 — the first regulatory filing landed 39 days later. 547 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 notifiedOregon✓ OR AG ≤45dFull clock table in Litigation Timeline
HHS OCRState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
547
Data types
—
Jurisdictions
1
OR
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 14, 2022
When the intrusion reportedly occurred, per the linked filings
280 days
Breach discoveredAG web form
Oct 21, 2022
Reported by OREGON AG filing
39 days
🦫OREGONHHS OCRFirst filinglinked via same-victim cross-source · 100%
Klamath County reported to HHS on 2022-11-29 a Unauthorized Access/Disclosure affecting 547 individuals. Breached information located on Email. A workforce member impermissibly emailed PHI (names, addresses, DOB, health insurance) to a personal account. The entity sanctioned the employee, retrained staff, and notified HHS/individuals.
Affected (this filing):
🦫Oregon State AGMost recentlinked via same-victim cross-source · 100%
Klamath County reported a data breach to the Oregon Attorney General. The breach was reported on 2022-11-29. The breach occurred during 1/14/2022 - 1/14/2022, 3/29/2022 - 3/29/2022, 5/1/2022 - 5/1/2022, 7/29/2022 - 7/29/2022, 10/10/2022 - 10/10/2022. The breach was discovered on 10/21/2022. 547 individuals were affected. Notice was sent on 11/28/2022.
Affected (this filing): 547
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.