DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed7 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedpysahigh sensitivity
Merged incident · 7 filings

One Community Health — April 2021 breach

Clustered 7 filings across 6 jurisdictions · filing window Sep 13, 2021 → Nov 22, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

39,865

First → last filing

Sep 13, 2021 → Nov 22, 2021

Merge confidence

100%

incident inc_fa585cafed044b2f · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. Intrusion Apr 19, 2021–Apr 20, 2021, discovered Apr 20, 2021 — the first regulatory filing landed 216 days later (flagged late). 39,865 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 1 more. Notifications rolled out on a 70-day schedule across 6 filings beginning Sep 13, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
216days

Discovered → first regulatory filing

Discovery variance
169days

Range of discovered_at dates across filings

Leak precedence
70days 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
70days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksWashington✗ WA AG >90dOregon✗ OR AG >45dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 19, 2021breach begins
Apr 20, 2021discovered · members disagree
notification delay · 216 days
Nov 22, 2021first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. SEP 13Leak sitepysa postfirst filing · attacker claim · unverifiedday 0
  2. NOV 22MA AGMA AG notice12 MA residents+70d
  3. NOV 22WA AGWA AG notice7,945 WA residents+70d
  4. NOV 22CA AGCA AG noticeno count stated+70d
  5. NOV 22HHS OCRHHS OCR noticestates nationwide total 39,865+70d
  6. NOV 22MT AGMT AG notice19 MT residents+70d
  7. NOV 22OR AGOR AG noticemost recent · states nationwide total 39,865+70d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 19, 2021 – Apr 20, 2021
WA AG
Discovered
Apr 20, 2021WA AG + CA AG + MT AGOct 6, 2021OR AGfilings disagree on discovery
Data types
Government ID · Identity (basic) · PHI · Health (basic)
MA AG + WA AG + CA AG +2
Attack vector
Ransomware
WA AG

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)

39,865

Sum of filed state slices

7,976· 20.0% of stated

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

US39,865
WA7,945
MT19
MA12

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 claim1 member

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

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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 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

70 days

Cadence

~1 / 11.7d

vs. multi-state median

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