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

Confirmed2 filings · 1 stateUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 2 filings

Gardner Family Health Network — February 2019 breach

Clustered 2 filings across 1 jurisdiction · filing window Apr 16, 2019 → Jun 6, 2019. View entity profile → Other incidents for this victim →

✓ affected count, data types agreeMerge99%

Determination

Confirmed

Members

2 filings

States

Affected · reported

5,064

First → last filing

Apr 16, 2019 → Jun 6, 2019

Merge confidence

99%

incident inc_c37183b5c0b74d5f · merged by deterministic · confidence 99%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes unauthorized access. Intrusion Feb 19, 2019, discovered Feb 19, 2019 — the first regulatory filing landed 56 days later. 5,064 individuals reported across the linked filings. Data reported: PHI, Health (basic), and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

56days

Discovered → first regulatory filing

Filing span

51days

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 clocksHIPAA✓ HHS notifiedCalifornia✓ CA 60-day OK · 37dFull clock table in Litigation Timeline

Incident timeline

Feb 19, 2019breach begins

Feb 19, 2019discovered

notification delay · 56 days

Apr 16, 2019first filing

Jun 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

APR 16HHS OCRHHS OCR noticefirst filing · states nationwide total 5,064day 0
JUN 6CA AGCA AG noticemost recent · 5,064 CA residents+51d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Feb 19, 2019
Discovered: Feb 19, 2019
Data types: Health (basic) · Identity (basic) · PHI
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)

5,064

Sum of filed state slices

5,064· 100.0% of stated

0% 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 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: 0.99 · above the 0.85 auto-merge floor
Audit: Every link edge records its method, confidence and model + prompt versions (99% is the strongest edge).

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

Filing velocity

Spread

51 days

vs. multi-state median

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