Ambucor Health Solutions — March 2016 breach

One linked filing — more sources may join as they report · filed Jul 22, 2016. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

1 filing

States

Affected · reported

53,000

First → last filing

Jul 22, 2016

incident inc_d143ceaaa4604c85 · merged by deterministic

Confirmed breach. Intrusion Mar 17, 2016, discovered Mar 17, 2016 — the first regulatory filing landed 127 days later (flagged late). 53,000 individuals reported across the linked filings.

Litigation Timing

Notification delay

127days

Discovered → first regulatory filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✗ HHS report lateFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 17, 2016breach begins

Mar 17, 2016discovered

notification delay · 127 days

Jul 22, 2016first & only filing

—watching for filings

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

Member cascade — every filing about this breach

JUL 22HHS OCRHHS OCR noticeonly filing · states nationwide total 53,000day 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 17, 2016
Discovered: Mar 17, 2016
Data types: PHI · Health (basic) · Identity (basic) · Government ID
Attack vector: Unauthorized Access
Response: Shut off the employee's computer access · Conducted a thorough investigation · Provided breach notification to HHS and its 53 customers

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 filing1 member

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

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.