Enforced2 filings · 2 statesUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 2 filings

St. Elizabeth's Medical Center

Clustered 2 filings across 2 jurisdictions · filing window Aug 26, 2014 → Jun 10, 2015. View entity profile → Other incidents for this victim →

✓ affected count agreeMerge100%

Determination

Enforced

Members

2 filings

States

Affected · reported

595

First → last filing

Aug 26, 2014 → Jun 10, 2015

Merge confidence

100%

incident inc_a5bc389e241740c6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes unauthorized access. 595 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

Filing span

288days

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

Incident timeline

? — ?breach window unknown

Aug 26, 2014first filing

Jun 10, 2015most recent filing

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing about this breach

AUG 26HHS OCRHHS OCR noticefirst filing · states nationwide total 595day 0
JUN 10HHS OCR enforcementHHS OCR enforcement noticemost recent · no count statedoperator-confirmed+288d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: —
Discovered: —
Data types: PHI · 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 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

288 days

vs. multi-state median

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