Confirmed breach. Intrusion Oct 12, 2016–Oct 13, 2016, discovered Oct 13, 2016 — the first regulatory filing landed 22 days later. 544 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)
544
Data types
—
Jurisdictions
1
OR
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 12, 2016 → Oct 13, 2016
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Oct 13, 2016
Reported by OREGON AG filing
🦫Oregon State AGFirst filinglinked via same-victim cross-source · 100%
Kaiser Foundation Health Plan of the Northwest reported a data breach to the Oregon Attorney General. The breach was reported on 2016-11-04. The breach occurred during 10/12/2016 - 10/13/2016. The breach was discovered on 10/13/2016. 544 individuals were affected. Notice was sent on 11/4/2016.
Affected (this filing): 544
OR AG ≤45d
🦫OREGONHHS OCRMost recentlinked via same-victim cross-source · 100%
Kaiser Foundation Health Plan of the Northwest reported to HHS on 2016-11-06 a Unauthorized Access/Disclosure affecting 544 individuals. Breached information located on Network Server. A website upgrade resulted in an incorrect caching configuration, saving PHI into browser cache accessible to other visitors. The CE provided notifications and implemented a corrective action plan including staff education and process improvements.
Affected (this filing): 544
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.