DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed6 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 6 filings

Carle Health

Clustered 6 filings across 1 jurisdiction · filing window Jun 19, 2026 → Jul 1, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

1

Affected · reported

1,444

First → last filing

Jun 19, 2026 → Jul 1, 2026

Merge confidence

100%

incident inc_a5db2685cfac497c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filing describes unauthorized access. Discovered Jan 13, 2026 — the first regulatory filing landed 157 days later. 1,444 individuals reported across the linked filings. Data reported: PHI, Health (basic), and Identity (basic). Notifications rolled out on a 12-day schedule across 6 filings beginning Jun 19, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
157days

Discovered → first regulatory filing

Discovery variance
143days

Range of discovered_at dates across filings

Filing span
12days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Incident timeline

? — ?breach window unknown
Jan 13, 2026discovered · members disagree
notification delay · 157 days
Jun 19, 2026first filing
Jul 1, 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. JUN 19HHS OCRHHS OCR noticefirst filing · states nationwide total 1,444day 0
  2. JUL 1IL AGIL AG noticeno count stated+12d
  3. JUL 1IL AGIL AG noticeno count stated+12d
  4. JUL 1IL AGIL AG noticeno count stated+12d
  5. JUL 1IL AGIL AG noticeno count stated+12d
  6. JUL 1IL AGIL AG noticemost recent · no count stated+12d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
Jan 13, 2026IL AGApr 15, 2026IL AGMay 4, 2026IL AGMay 13, 2026IL AGJun 5, 2026IL AGfilings disagree on discovery
Data types
PHI · Health (basic) · Identity (basic)
HHS OCR + IL 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.

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 filing6 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
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

12 days

Cadence

~1 / 2.4d

vs. multi-state median

1.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.