Enforced3 filings · 3 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 3 filings

Touchstone Medical Imaging, LLC — May 2014 breach

Clustered 3 filings across 3 jurisdictions · filing window Oct 3, 2014 → May 6, 2019. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Enforced

Members

3 filings

States

Affected · reported

307,528

First → last filing

Oct 3, 2014 → May 6, 2019

Merge confidence

100%

incident inc_9412d5b439964ba7 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. Intrusion May 9, 2014, discovered May 9, 2014 — the first regulatory filing landed 147 days later (flagged late). 307,528 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 1 more. Notifications rolled out on a 1676-day schedule across 3 filings beginning Oct 3, 2014. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

147days

Discovered → first regulatory filing

Filing span

1676days

Time between earliest and latest filing

Not recorded for this incident

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 clocksCalifornia✗ CA 60-day late · 144dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 9, 2014breach begins

May 9, 2014discovered

notification delay · 147 days

Oct 3, 2014first filing

May 6, 2019most recent filing

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

Member cascade — every filing about this breach

OCT 3HHS OCRHHS OCR noticefirst filing · states nationwide total 307,528auto-linkedday 0
OCT 3CA AGCA AG noticeno count statedauto-linkedday 0
MAY 6HHS OCR enforcementHHS OCR enforcement noticemost recent · no count statedoperator-confirmed+1676d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: May 9, 2014
Discovered: May 9, 2014
Data types: Health (basic) · Identity (basic) · Government ID · PHI
Attack vector: Unauthorized Access

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 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
Reviewed: operator-reviewed Aug 21, 2026 · at least one link edge was human-adjudicated
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

1676 days

Cadence

~1 / 838d

vs. multi-state median

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