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

INDIANA UNIVERSITY HEALTH, INC. — August 2024 breach

Clustered 4 filings across 1 jurisdiction · filing window Jan 2, 2025 → Jan 27, 2025. View entity profile → Other incidents for this victim →

✓ affected count agreeMerge100%

Determination

Confirmed

Members

4 filings

States

1

Affected · reported

1,446

First → last filing

Jan 2, 2025 → Jan 27, 2025

Merge confidence

100%

incident inc_6406135132474915 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filing describes a phishing attack. Intrusion Aug 27, 2024. 1,446 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 1 more. Notifications rolled out on a 25-day schedule across 4 filings beginning Jan 2, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span
25days

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

Aug 27, 2024breach begins
Jan 2, 2025first filing
Jan 27, 2025most 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

  1. JAN 2IN AGIN AG noticefirst filing · states nationwide total 214day 0
  2. JAN 7HHS OCRHHS OCR noticestates nationwide total 1,446+5d
  3. JAN 17IN AGIN AG notice1 IN residents+15d
  4. JAN 27IN AGIN AG noticemost recent · 1 IN residents+25d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 27, 2024
IN AG
Discovered
—
Data types
Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR
Attack vector
Phishing
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)

1,446

Sum of filed state slices

209· 14.5% of stated

86% 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 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 9, 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

25 days

Cadence

~1 / 8.3d

vs. multi-state median

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