Confirmed breach. Intrusion Oct 17, 2019, discovered Oct 17, 2019 — the first regulatory filing landed 323 days later (flagged late). 471,591 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 >45dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
471,591
Data types
—
Jurisdictions
2
CA OR
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Oct 17, 2019
When the intrusion reportedly occurred, per the linked filings
INTEGRIS Baptist Medical Center, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2020-09-04. The breach occurred during 10/17/2019 - 10/17/2019. The breach was discovered on 5/27/20208/29/2020. 471,591 individuals were affected. Notice was sent on 5/29/20209/4/2020.
Affected (this filing): 471,591
OR AG >45d
🐻California State AGMost recentlinked via multistate filing link · 100%
INTEGRIS Baptist Medical Center, Inc. reported the loss of a portable hard drive containing patient information during an on-campus office move. The incident was discovered on October 17, 2019. The missing drive contained names, Social Security numbers, and limited clinical information. A backup was analyzed to confirm the data contents. The organization offered one year of identity protection services and implemented staff education and secure disposal of similar drives.
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.