DisclosureLens
HHS OCRState AGConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 2 filings

Canby Clinic — April 2025 breach

Clustered 2 filings across 1 jurisdiction · filing window Apr 30, 2025 May 17, 2025. View entity profile → Other incidents for this victim →

affected count agreeMerge77%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

549

First → last filing

Apr 30, 2025 May 17, 2025

Merge confidence

77%

incident inc_4ef9852426e845ad · merged by llm · confidence 77%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes unauthorized access. Intrusion Apr 22, 2025–May 7, 2025, discovered Apr 25, 2025 — the first regulatory filing landed 5 days later. 549 individuals reported across the linked filings. Data reported: PHI, Health (basic), and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
5days

Discovered → first regulatory filing

Filing span
17days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delayno 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

Incident timeline

Apr 22, 2025breach begins
Apr 25, 2025discovered
notification delay · 5 days
Apr 30, 2025first filing
May 17, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. APR 30HHS OCRHHS OCR noticefirst filing · states nationwide total 549day 0
  2. MAY 17OR AGOR AG noticemost recent · states nationwide total 549+17d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 22, 2025May 7, 2025
OR AG
Discovered
Apr 25, 2025· 3d undetected
OR AG
Data types
PHI · Health (basic) · Identity (basic)
HHS OCR
Attack vector
Unauthorized Access
HHS OCR

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing2 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
llm
Confidence
0.77 · below the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (77% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

17 days

vs. multi-state median

1.9× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.