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

Medical Healthcare Solutions, Inc. — October 2021 breach

Clustered 6 filings across 5 jurisdictions · filing window Oct 26, 2021 → Jan 25, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

4

Affected · reported

133,997

First → last filing

Oct 26, 2021 → Jan 25, 2022

Merge confidence

100%

incident inc_72ece9805ab1414e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe malware. Intrusion Oct 1, 2021–Oct 4, 2021, discovered Nov 19, 2021 — the first regulatory filing landed 43 days later. 133,997 individuals reported across the linked filings. Data reported: Government ID, Minor, PHI, and 6 more. Notifications rolled out on a 91-day schedule across 5 filings beginning Oct 26, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
43days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
67days 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
91days

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

financial_credentialsidentity_governmentminor

Incident timeline

Oct 1, 2021breach begins
Nov 19, 2021discovered
notification delay · 43 days
Jan 1, 2022first filing
Jan 25, 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. OCT 26Leak siteconti postfirst filing · attacker claim · unverifiedday 0
  2. JAN 1IL AGIL AG noticeno count stated+67d
  3. JAN 21MT AGMT AG noticestates nationwide total 133,997+87d
  4. JAN 22HHS OCRHHS OCR noticestates nationwide total 133,997+88d
  5. JAN 24MA AGMA AG notice118,417 MA residents+90d
  6. JAN 25NH AGNH AG noticemost recent · 2,929 NH residents+91d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 1, 2021 – Oct 4, 2021
MT AG
Discovered
Nov 19, 2021· 49d undetected
IL AG + MT AG + NH AG
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · Minor · PCI · PHI · PII
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)

133,997

Sum of filed state slices

121,359· 90.6% of stated

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

US133,997
MA118,417
NH2,929
MT13

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

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

Press / market report

No press coverage linked yet.

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

91 days

Cadence

~1 / 18.2d

vs. multi-state median

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