DisclosureLens
All incidentsView linkage analytics →
HHS OCRHHS OCR enforcementState AGEnforced5 filings · 5 statesLifecycle stage 3 of 3: EnforcedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

Advocate Health Care Network — July 2013 breach

Clustered 5 filings across 5 jurisdictions · filing window Aug 23, 2013 → Aug 4, 2016. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Enforced

Members

5 filings

States

5

Affected · reported

4,029,530

First → last filing

Aug 23, 2013 → Aug 4, 2016

Merge confidence

100%

incident inc_1f47f25f283f4008 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Jul 14, 2013–Jul 15, 2013, discovered Jul 15, 2013 — the first regulatory filing landed 39 days later. 4,029,530 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 3 more. Notifications rolled out on a 1077-day schedule across 5 filings beginning Aug 23, 2013. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
39days

Discovered → first regulatory filing

Filing span
1077days

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

Sensitive data

identity_government

Incident timeline

Jul 14, 2013breach begins
Jul 15, 2013discovered
notification delay · 39 days
Aug 23, 2013first filing
Aug 4, 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

  1. AUG 23NH AGNH AG noticefirst filing · 271 NH residentsday 0
  2. AUG 23CA AGCA AG noticeno count statedday 0
  3. AUG 23HHS OCRHHS OCR noticestates nationwide total 4,029,530day 0
  4. AUG 26MA AGMA AG notice1,437 MA residents+3d
  5. AUG 4HHS OCR enforcementHHS OCR enforcement noticemost recent · no count stated+1077d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 14, 2013 – Jul 15, 2013
NH AG
Discovered
Jul 15, 2013· 1d undetected
NH AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NH AG + CA AG + HHS OCR +1
Attack vector
Unauthorized Access
NH AG

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)

4,029,530

Sum of filed state slices

1,708· 0.0% 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 filing5 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

1077 days

Cadence

~1 / 269.3d

vs. multi-state median

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