Clinical Registry Solutions
bd_fe5df6567cc5082d · schema v1 · pii pii-v1
Full breach record for Clinical Registry Solutions →Clinical Registry Solutions reported to HHS on 2026-06-12 a Hacking/IT Incident affecting 8545 individuals. Breached information located on Network Server. Business associate involved.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jun 12, 2026
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Ransomware claims (2)
- Leak Siteakirabd_f828cc6ad7ec7ecc2026-05-06 · +37dVerified by operator
- Leak Siteakirabd_401d01df51fe3e5f2026-04-09 · +64dVerified by operator
Regulatory filings (7) · sorted by filing gap
- California State AGbd_cf661af5a4e58e572026-06-11 · +1dVerified
- New Hampshire State AGbd_f331216109245cf42026-06-11 · +1dVerified
- Nebraska State AGbd_3dde56a6b54fc5f22026-06-17 · +5dVerified by operator
- Indiana State AGbd_8e3980e02c3b30f22026-06-17 · +5dVerified
Show 3 more filings ↓Show fewer ↑up to 47d gap
- Massachusetts State AGbd_769d7856f7ce42202026-06-25 · +13dVerified by operator
- California State AGbd_84ea03610972f25d2026-07-29 · +47dVerified by operator
- California State AGbd_b568d923923502902026-07-29 · +47dVerified by operator
Filing propagation · 8 filings · 6 states
View merged incident ↗Pattern: first filing Jun 11 (CA), last Jul 29 (CA) — a 48-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.