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

Adaptive Health — October 2021 breach

Clustered 3 filings across 3 jurisdictions · filing window Apr 11, 2022 → Apr 19, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

510,574

First → last filing

Apr 11, 2022 → Apr 19, 2022

Merge confidence

100%

incident inc_c378902f627c4220 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe unauthorized access. Intrusion Oct 17, 2021, discovered Oct 17, 2021 — the first regulatory filing landed 176 days later. 510,574 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 8-day schedule across 3 filings beginning Apr 11, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
176days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
8days

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 notifiedSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 17, 2021breach begins
Oct 17, 2021discovered
notification delay · 176 days
Apr 11, 2022first filing
Apr 19, 2022most 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. APR 11HHS OCRHHS OCR noticefirst filing · states nationwide total 510,574day 0
  2. APR 13MT AGMT AG notice813 MT residents+2d
  3. APR 19SC AGSC AG noticemost recent · 1,404 SC residents+8d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 17, 2021
MT AG
Discovered
Oct 17, 2021
MT AG + SC AG
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MT AG + SC 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.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

510,574

Sum of filed state slices

2,217· 0.4% 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

8 days

Cadence

~1 / 4d

vs. multi-state median

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