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

MEDNAX Services, Inc. — June 2020 breach

Clustered 8 filings across 7 jurisdictions · filing window Dec 16, 2020 → Jan 12, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

1,442,997

First → last filing

Dec 16, 2020 → Jan 12, 2021

Merge confidence

100%

incident inc_6f5021478caa4829 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe a phishing attack. Intrusion Jun 17, 2020–Jul 3, 2020, discovered Jan 1, 2020 — the first regulatory filing landed 350 days later (flagged late). 1,442,997 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 5 more. Notifications rolled out on a 27-day schedule across 8 filings beginning Dec 16, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
350days

Discovered → first regulatory filing

Discovery variance
197days

Range of discovered_at dates across filings

Filing span
27days

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 clocksWashington✗ WA AG >90dOregon✗ OR AG >45dCalifornia✗ CA 60-day late · 180dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Jun 17, 2020breach begins
Jan 1, 2020discovered · members disagree
notification delay · 350 days
Dec 16, 2020first filing
Jan 12, 2021most 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. DEC 16WA AGWA AG noticefirst filing · 29,861 WA residentsday 0
  2. DEC 16HHS OCRHHS OCR noticestates nationwide total 1,442,997day 0
  3. DEC 16MT AGMT AG notice1,671 MT residentsday 0
  4. DEC 16OR AGOR AG noticestates nationwide total 2,411day 0
  5. DEC 16CA AGCA AG notice45 CA residentsday 0
  6. DEC 23CA AGCA AG noticeno count stated+7d
  7. DEC 23MA AGMA AG notice2 MA residents+7d
  8. JAN 12NH AGNH AG noticemost recent · 109 NH residents+27d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 17, 2020 – Jun 22, 2020
WA AG
Discovered
Jan 1, 2020MT AGJun 19, 2020WA AG + OR AG + CA AGJul 16, 2020NH AGfilings disagree on discovery
Data types
Financial · Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PHI · PII
WA AG + HHS OCR + MT AG +3
Attack vector
Phishing
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)

1,442,997

Sum of filed state slices

31,688· 2.2% of stated

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

US1,442,997
WA29,861
MT1,671
NH109
CA45
MA2

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 filing8 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

27 days

Cadence

~1 / 3.9d

vs. multi-state median

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