All incidents View linkage analytics →Get the evidence package — $79

Confirmed3 filings · 3 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 3 filings

Yale New Haven Health Services Corporation — April 2021 breach

Clustered 3 filings across 3 jurisdictions · filed Jul 23, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

14,603

First → last filing

Jul 23, 2021

Merge confidence

100%

incident inc_b3b402711ba6447d · merged by deterministic · confidence 100%

Part of the Elekta supply-chain incident (2021) — at least 3 organizations filed notifications naming this third party.

Confirmed breach. One breach, 3 legal records. Intrusion Apr 2, 2021–Apr 20, 2021, discovered May 26, 2021 — the first regulatory filing landed 58 days later. 14,603 individuals reported across the linked filings. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

58days

Discovered → first regulatory filing

Filing span

0days

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

Apr 2, 2021breach begins

May 26, 2021discovered

notification delay · 58 days

Jul 23, 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

JUL 23MA AGMA AG noticefirst filing · 7 MA residentsauto-linkedday 0
JUL 23HHS OCRHHS OCR noticestates nationwide total 14,603auto-linkedday 0
JUL 23NH AGNH AG noticemost recent · 2 NH residentsauto-linkedday 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Apr 2, 2021 – Apr 20, 2021
Discovered: May 26, 2021· 54d undetected
Data types: Identity (basic) · Government ID · Health (basic)
Attack vector: Unauthorized Access
Response: Notified HHS · Notified affected individuals · Notified the media

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)

14,603

Sum of filed state slices

9· 0.1% 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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing3 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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.