DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed13 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedsnatchcritical sensitivity
Merged incident · 13 filings

Atlantic Dialysis Management Services

Clustered 13 filings across 3 jurisdictions · filing window Jun 30, 2022 → Mar 23, 2023. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

13 filings

States

2

Affected · reported

3,851

First → last filing

Jun 30, 2022 → Mar 23, 2023

Merge confidence

100%

incident inc_ca0fbce01fc64e23 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. The filings describe unauthorized access. 3,851 individuals reported across the linked filings. Data reported: Government ID, Minor, PHI, and 3 more. Notifications rolled out on a 265-day schedule across 12 filings beginning Jun 30, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Leak precedence
263days 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
265days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

? — ?breach window unknown
Mar 21, 2023first filing
Mar 23, 2023most 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. JUN 30Leak sitesnatch postfirst filing · attacker claim · unverifiedday 0
  2. MAR 21HHS OCRHHS OCR noticestates nationwide total 3,851+263d
  3. MAR 21HHS OCRHHS OCR noticestates nationwide total 776+263d
  4. MAR 22HHS OCRHHS OCR noticestates nationwide total 1,126+264d
  5. MAR 22HHS OCRHHS OCR noticestates nationwide total 563+264d
  6. MAR 22HHS OCRHHS OCR noticestates nationwide total 922+264d
  7. MAR 22HHS OCRHHS OCR noticestates nationwide total 2,204+264d
  8. MAR 22HHS OCRHHS OCR noticestates nationwide total 970+264d
  9. MAR 22HHS OCRHHS OCR noticestates nationwide total 3,851+264d
  10. MAR 22HHS OCRHHS OCR noticestates nationwide total 745+264d
  11. MAR 22HHS OCRHHS OCR noticestates nationwide total 653+264d
  12. MAR 22HHS OCRHHS OCR noticestates nationwide total 1,345+264d
  13. MAR 23MA AGMA AG noticemost recent · 9 MA residents+265d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
—
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PHI
HHS OCR + MA 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)

3,851

Sum of filed state slices

9· 0.2% 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 claim1 member

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

Press / market report

No press coverage linked yet.

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

265 days

Cadence

~1 / 22.1d

vs. multi-state median

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