DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed6 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedworldleakshigh sensitivity
Merged incident · 6 filings

Deaconess Health System — December 2025 breach

Clustered 6 filings across 4 jurisdictions · filing window Jan 7, 2026 → Aug 7, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

3

Affected · reported

203,874

First → last filing

Jan 7, 2026 → Aug 7, 2026

Merge confidence

100%

incident inc_6455cd18f5bf455a · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 2 unverified claims. The filing describes unauthorized access. Intrusion Dec 2, 2025–Dec 18, 2025, discovered Feb 2, 2026 — the first regulatory filing landed 27 days later (flagged late). 203,874 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Financial account, and 2 more. Notifications rolled out on a 212-day schedule across 4 filings beginning Jan 7, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
27days

Discovered → first regulatory filing

Discovery variance
144days

Range of discovered_at dates across filings

Leak precedence
53days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
212days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 2, 2025breach begins
Feb 2, 2026discovered · members disagree
notification delay · 27 days
Mar 1, 2026first filing
Aug 7, 2026most 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. JAN 7Leak siteworldleaks postfirst filing · attacker claim · unverifiedday 0
  2. MAR 1IL AGIL AG noticeno count stated+53d
  3. MAR 20HHS OCRHHS OCR noticestates nationwide total 8,941+72d
  4. APR 8Leak siteworldleaks postattacker claim · unverified+91d
  5. AUG 1IL AGIL AG noticeno count stated+206d
  6. AUG 7TX AGTX AG noticemost recent · states nationwide total 203,874+212d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 2, 2025 – Dec 18, 2025
TX AG
Discovered
Feb 2, 2026IL AGJun 26, 2026IL AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
IL AG + HHS OCR + TX AG
Attack vector
Unauthorized Access
HHS OCR

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)

203,874

Sum of filed state slices

374· 0.2% 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 claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing4 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 25, 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

212 days

Cadence

~1 / 42.4d

vs. multi-state median

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