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

The Physical Medicine Rehabilitation Center

Clustered 4 filings across 3 jurisdictions · filing window Jul 8, 2024 → Nov 1, 2024. View entity profile → Other incidents for this victim →

✓ affected count agreeMerge100%

Determination

Confirmed

Members

4 filings

States

2

Affected · reported

4,083

First → last filing

Jul 8, 2024 → Nov 1, 2024

Merge confidence

100%

incident inc_6f9f948ee25c4dd6 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings and 2 unverified claims. The filing describes unauthorized access. Discovered Jul 8, 2024 — the first regulatory filing landed 112 days later. 4,083 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
112days

Discovered → first regulatory filing

Leak precedence
112days 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
116days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.

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

Sensitive data

identity_government

Incident timeline

? — ?breach window unknown
Jul 8, 2024discovered
notification delay · 112 days
Oct 28, 2024first filing
Nov 1, 2024most 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 8Leak sitekairos postfirst filing · attacker claim · unverifiedday 0
  2. JUL 26Leak sitemeow postattacker claim · unverified+18d
  3. OCT 28HHS OCRHHS OCR noticestates nationwide total 4,083+112d
  4. NOV 1IL AGIL AG noticemost recent · no count stated+116d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
Jul 8, 2024
IL AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR
Attack vector
Unauthorized Access
HHS OCR

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

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

116 days

Cadence

~1 / 38.7d

vs. multi-state median

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