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

Southwest Healthcare Services — October 2022 breach

Clustered 7 filings across 6 jurisdictions · filing window Oct 22, 2022 → Apr 1, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

15,996

First → last filing

Oct 22, 2022 → Apr 1, 2023

Merge confidence

100%

incident inc_ed5fd32d864141ed · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. Intrusion Oct 28, 2022–Oct 29, 2022, discovered Oct 28, 2022 — the first regulatory filing landed 65 days later. 15,996 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 2 more. Notifications rolled out on a 161-day schedule across 6 filings beginning Oct 22, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
65days

Discovered → first regulatory filing

Discovery variance
95days

Range of discovered_at dates across filings

Leak precedence
71days 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
161days

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

Oct 28, 2022breach begins
Oct 28, 2022discovered · members disagree
notification delay · 65 days
Jan 1, 2023first filing
Apr 1, 2023most 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. OCT 22Leak sitedonutleaks postfirst filing · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticeno count stated+71d
  3. MAR 31WA AGWA AG notice1,225 WA residents+160d
  4. MAR 31VT AGVT AG noticeno count stated+160d
  5. MAR 31VT AGVT AG noticeno count stated+160d
  6. MAR 31MT AGMT AG notice547 MT residents+160d
  7. APR 1HHS OCRHHS OCR noticemost recent · states nationwide total 15,996+161d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 28, 2022 – Oct 29, 2022
WA AG
Discovered
Oct 28, 2022IL AGJan 31, 2023WA AG + VT AG + MT AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
WA AG + VT AG + MT AG +1
Attack vector
Ransomware
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)

15,996

Sum of filed state slices

1,772· 11.1% of stated

89% 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 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 Aug 25, 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

161 days

Cadence

~1 / 26.8d

vs. multi-state median

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