DisclosureLens
State AGConfirmed6 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 6 filings

Radiology Associates of Albuquerque and Advanced Imaging, LL — December 2020 breach

Clustered 6 filings across 4 jurisdictions · filing window Jul 28, 2022 Oct 11, 2022. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

not comparable

First → last filing

Jul 28, 2022 Oct 11, 2022

Merge confidence

100%

incident inc_94f0e45383f4488f · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. Intrusion Dec 22, 2020–Aug 3, 2021, discovered Aug 1, 2021 — the first regulatory filing landed 361 days later (flagged late). Data reported: Government ID, Biometric, Identity (basic), and 6 more. Notifications rolled out on a 75-day schedule across 6 filings beginning Jul 28, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
361days

Discovered → first regulatory filing

Discovery variance
3days

Range of discovered_at dates across filings

Filing span
75days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksWashington WA AG >90dCalifornia CA 60-day late · 396dFull clock table in Litigation Timeline

Sensitive data

authenticationbiometricidentity_government

Incident timeline

Dec 22, 2020breach begins
Aug 1, 2021discovered · members disagree
notification delay · 361 days
Jul 28, 2022first filing
Oct 11, 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. JUL 28MT AGMT AG noticefirst filing · 113 MT residentsday 0
  2. AUG 1NH AGNH AG notice14 NH residents+4d
  3. SEP 9WA AGWA AG notice882 WA residents+43d
  4. SEP 9CA AGCA AG noticeno count stated+43d
  5. SEP 13NH AGNH AG notice65 NH residents+47d
  6. OCT 11CA AGCA AG noticemost recent · no count stated+75d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 22, 2020Aug 3, 2021
MT AG
Discovered
Aug 1, 2021MT AG + NH AG + CA AGAug 4, 2021WA AGfilings disagree on discovery
Data types
Authentication · Biometric · Credentials · Financial · Financial account · Health (basic) · Identity (basic) · Government ID · PHI
MT AG + NH AG + WA AG +1
Attack vector
Unauthorized Access
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

WA882
MT113
NH65

State AGs report only their own residents; teal bars show each state's reported slice.

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 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 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 / 15d

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.