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,834
Data types
—
Jurisdictions
1
OR
Linked filings
2
HHS OCR · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 12, 2014 → Jan 3, 2023
When the intrusion reportedly occurred, per the linked filings
3,179 days
🦫Oregon State AGFirst filinglinked via same-victim cross-source · 100%
Asante reported a data breach to the Oregon Attorney General. The breach was reported on 2023-02-24. The breach occurred during 6/12/2014 - 1/3/2023. The breach was discovered on 12/30/20222/14/2023. 8,834 individuals were affected. Notice was sent on 2/27/2023.
Affected (this filing): 8,834
OR AG >45d
🦫OREGONHHS OCRMost recentlinked via same-victim cross-source · 100%
Asante Ashland Community Hospital (OR) reported an insider breach affecting 8,834 individuals. An affiliate provider impermissibly accessed Electronic Medical Records containing PHI (names, DOB, diagnoses, lab results, medications). The entity notified HHS, individuals, and media, sanctioned the provider, and implemented administrative safeguards.
Affected (this filing): 8,834
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.