All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed3 filings · 2 statesUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 3 filings

OptumRx — March 2016 breach

Clustered 3 filings across 2 jurisdictions · filing window Apr 8, 2016 → Apr 12, 2016. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

7,261

First → last filing

Apr 8, 2016 → Apr 12, 2016

Merge confidence

100%

incident inc_c1022ec58a0b4c1d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe unauthorized access. Intrusion Mar 16, 2016, discovered Mar 22, 2016 — the first regulatory filing landed 17 days later. 7,261 individuals reported across the linked filings. Data reported: PHI, Health (basic), Identity (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

17days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

4days

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 clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Incident timeline

Mar 16, 2016breach begins

Mar 22, 2016discovered

notification delay · 17 days

Apr 8, 2016first filing

Apr 12, 2016most recent filing

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

Member cascade — every filing about this breach

APR 8CA AGCA AG noticefirst filing · no count statedauto-linkedday 0
APR 8MT AGMT AG notice5 MT residentsauto-linkedday 0
APR 12HHS OCRHHS OCR noticemost recent · states nationwide total 7,261auto-linked+4d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 16, 2016
Discovered: Mar 22, 2016· 6d undetected
Data types: Health (basic) · Identity (basic) · PHI · PII
Attack vector: Unauthorized Access

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)

7,261

Sum of filed state slices

5· 0.1% of stated

100% 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

4 days

Cadence

~1 / 2d

vs. multi-state median

2.0× faster

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.