Enforced2 filings · 2 statesUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 2 filings

ST. JOSEPH HEALTH SYSTEM — February 2011 breach

Clustered 2 filings across 2 jurisdictions · filing window Feb 15, 2012 → Oct 17, 2016. View entity profile → Other incidents for this victim →

✓ affected count agreeMerge100%

Determination

Enforced

Members

2 filings

States

Affected · reported

12,234

First → last filing

Feb 15, 2012 → Oct 17, 2016

Merge confidence

100%

incident inc_05849d71d2ef4ef4 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes unauthorized access. Intrusion Feb 1, 2011–Feb 13, 2012, discovered Feb 14, 2012 — the first regulatory filing landed 1 days later. 12,234 individuals reported across the linked filings. Data reported: Health (basic) and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

1days

Discovered → first regulatory filing

Filing span

1706days

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 report on time · 1dFull clock table in Litigation Timeline

Incident timeline

Feb 1, 2011breach begins

Feb 14, 2012discovered

notification delay · 1 days

Feb 15, 2012first filing

Oct 17, 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

FEB 15HHS OCRHHS OCR noticefirst filing · states nationwide total 12,234day 0
OCT 17HHS OCR enforcementHHS OCR enforcement noticemost recent · no count statedoperator-confirmed+1706d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Feb 1, 2011 – Feb 13, 2012
Discovered: Feb 14, 2012· 378d undetected
Data types: Health (basic) · Identity (basic)
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 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
Reviewed: operator-reviewed Sep 7, 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

1706 days

vs. multi-state median

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