DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed3 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 3 filings

One Medical — June 2026 breach

Clustered 3 filings across 3 jurisdictions · filing window Jul 3, 2026 → Jul 17, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

153,174

First → last filing

Jul 3, 2026 → Jul 17, 2026

Merge confidence

100%

incident inc_b46ee886ac594200 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe hacking. Intrusion Jun 8, 2026–Jun 11, 2026, discovered Jun 13, 2026 — the first regulatory filing landed 20 days later. 153,174 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 14-day schedule across 3 filings beginning Jul 3, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
20days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
14days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksWashington✓ WA AG ≤30dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 8, 2026breach begins
Jun 13, 2026discovered
notification delay · 20 days
Jul 3, 2026first filing
Jul 17, 2026most 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. JUL 3WA AGWA AG noticefirst filing · 16,884 WA residentsday 0
  2. JUL 6NH AGNH AG notice125 NH residents+3d
  3. JUL 17HHS OCRHHS OCR noticemost recent · states nationwide total 153,174+14d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 8, 2026 – Jun 11, 2026
WA AG
Discovered
Jun 13, 2026· 5d undetected
WA AG + NH AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
WA AG + NH AG + HHS OCR
Attack vector
Third-Party / Supply Chain
WA AG

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

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

153,174

Sum of filed state slices

17,009· 11.1% of stated

89% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

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 filing3 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

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

Filing velocity

Spread

14 days

Cadence

~1 / 7d

vs. multi-state median

1.8× 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.