DisclosureLens
State AGConfirmed2 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 2 filings

ZOLL Medical — November 2018 breach

Clustered 2 filings across 2 jurisdictions · filing window Jun 10, 2019 Jul 16, 2019. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

2 filings

States

2

Affected · reported

4

First → last filing

Jun 10, 2019 Jul 16, 2019

Merge confidence

100%

incident inc_db1dc0360a0144bb · merged by deterministic · confidence 100%

Confirmed breach. One breach, 2 legal records. Intrusion Nov 8, 2018–Dec 28, 2018, discovered Jan 24, 2019 — the first regulatory filing landed 137 days later. 4 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
137days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
36days

Time between earliest and latest filing

Not recorded for this incident

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

Sensitive data

identity_government

Incident timeline

Nov 8, 2018breach begins
Jan 24, 2019discovered
notification delay · 137 days
Jun 10, 2019first filing
Jul 16, 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

  1. JUN 10NH AGNH AG noticefirst filing · 4 NH residentsday 0
  2. JUL 16DE AGDE AG noticemost recent · no count stated+36d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 8, 2018Dec 28, 2018
NH AG
Discovered
Jan 24, 2019· 77d undetected
NH AG + DE AG
Data types
Identity (basic) · Government ID · Health (basic) · PHI
NH AG + DE AG
Attack vector
Third-Party / Supply Chain
NH AG
Response
Initiated an internal review · Retained a leading independent forensics firm to help conduct a thorough investigation · Notified law enforcement and federal and state agencies
NH AG

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

36 days

vs. multi-state median

7.2× 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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.