DisclosureLens
HHS OCRState AGConfirmed7 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 7 filings

TRINITY HEALTH CORPORATION — April 2020 breach

Clustered 7 filings across 7 jurisdictions · filing window Sep 14, 2020 → Nov 2, 2020. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

7

Affected · reported

3,320,726

First → last filing

Sep 14, 2020 → Nov 2, 2020

Merge confidence

100%

incident inc_71ef25a7650b482f · merged by human · confidence 100%

Part of the BLACKBAUD, INC. supply-chain incident (2020) — at least 168 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 7 regulatory filings. Intrusion Apr 18, 2020–May 16, 2020, discovered Jul 16, 2020 — the first regulatory filing landed 60 days later. 3,320,726 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 49-day schedule across 7 filings beginning Sep 14, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
60days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
49days

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 clocksMaine⏱ ME AG >30d · 99dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Apr 18, 2020breach begins
Jul 16, 2020discovered
notification delay · 60 days
Sep 14, 2020first filing
Nov 2, 2020most 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. SEP 14IN AGIN AG noticefirst filing · states nationwide total 6,288day 0
  2. SEP 14HHS OCRHHS OCR noticestates nationwide total 3,320,726day 0
  3. OCT 23ME AGME AG noticestates nationwide total 6,288+39d
  4. OCT 23CA AGCA AG noticeno count stated+39d
  5. OCT 23MT AGMT AG notice4 MT residents+39d
  6. OCT 26MA AGMA AG notice293 MA residents+42d
  7. NOV 2NH AGNH AG noticemost recent · 9 NH residents+49d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 18, 2020
IN AG
Discovered
Jul 16, 2020· 89d undetected
ME AG + CA AG + MT AG +1
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + ME AG + CA AG +3
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)

3,320,726

Sum of filed state slices

379· 0.0% of stated

100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US3,320,726
MA293
IN67
NH9
ME6
MT4

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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 filing7 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 Oct 22, 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

49 days

Cadence

~1 / 8.2d

vs. multi-state median

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