Confirmed breach. Intrusion Mar 16, 2021, discovered Mar 16, 2021 — the first regulatory filing landed 80 days later (flagged late). 5,509 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)
5,509
Data types
—
Jurisdictions
1
OR
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Mar 16, 2021
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Mar 16, 2021
Reported by OREGON AG filing
80 days
🦫Oregon State AGFirst filinglinked via same-victim cross-source · 100%
Providence Health Plan reported a data breach to the Oregon Attorney General. The breach was reported on 2021-06-04. The breach occurred during 3/16/2021 - 3/18/2021, 3/22/2021 - 3/23/2021. The breach was discovered on 3/16/2021. 5,509 individuals were affected.
Affected (this filing): 5,509
OR AG >45d
🦫OREGONHHS OCRMost recentlinked via same-victim cross-source · 100%
Providence Health Plan reported to HHS on 2021-06-07 a Unauthorized Access/Disclosure affecting 5509 individuals. Breached information located on Email. A temporary contract worker sent emails containing ePHI (names, SSNs, DOB, treatment info) to a personal email address. The CE notified HHS, affected individuals, and the media, and implemented additional technical safeguards.
Affected (this filing): 5,509
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.