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

Affordacare Urgent Care Clinics — February 2020 breach

Clustered 8 filings across 6 jurisdictions · filing window Feb 1, 2020 → Apr 16, 2020. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

5

Affected · reported

57,411

First → last filing

Feb 1, 2020 → Apr 16, 2020

Merge confidence

100%

incident inc_47f45dcd61a24d79 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 2 unverified claims. The filings describe a ransomware attack. Intrusion Feb 1, 2020, discovered Feb 1, 2020 — the first regulatory filing landed 55 days later. 57,411 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 1 more. Notifications rolled out on a 75-day schedule across 6 filings beginning Feb 1, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
55days

Discovered → first regulatory filing

Discovery variance
2days

Range of discovered_at dates across filings

Leak precedence
55days 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
75days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 1, 2020breach begins
Feb 1, 2020discovered · members disagree
notification delay · 55 days
Mar 27, 2020first filing
Apr 16, 2020most 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. FEB 1Leak sitemaze postfirst filing · attacker claim · unverifiedday 0
  2. FEB 1Leak sitemaze postattacker claim · unverifiedday 0
  3. MAR 27IN AGIN AG noticestates nationwide total 55,338+55d
  4. MAR 30MT AGMT AG notice15 MT residents+58d
  5. MAR 31HHS OCRHHS OCR noticestates nationwide total 57,411+59d
  6. APR 6NH AGNH AG notice1 NH residents+65d
  7. APR 14MA AGMA AG notice3 MA residents+73d
  8. APR 16NH AGNH AG noticemost recent · 1 NH residents+75d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 1, 2020
IN AG
Discovered
Feb 1, 2020MT AGFeb 3, 2020NH AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI
MT AG + HHS OCR + NH AG +1
Attack vector
Ransomware
MT 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)

57,411

Sum of filed state slices

42· 0.1% of stated

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

US57,411
IN23
MT15
MA3
NH1

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 claim2 members

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

75 days

Cadence

~1 / 10.7d

vs. multi-state median

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