DisclosureLens
NEW YORKHackingHealthcareHealthcareHealth (basic)Identity (basic)MediumContained

Clinical Registry Solutions

bd_fe5df6567cc5082d · schema v1 · pii pii-v1

Severity

Medium

Discovered

Filed

Jun 12, 2026

To disclose

Affected

8,545

Linked

10 filings

Confidence

69%
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.

Leak gap clock Leak >30d
no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.
⚠ No discovery dateThe OCR public portal omits the discovery date, so the 60-day notification clock cannot be evaluated from this source — only that the filing was submitted.

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.

This filing is one of 10 about the same incident.View merged incident
A leak claim by akira about this victim predates this filing by 64 days.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (2)

Regulatory filings (7) · sorted by filing gap

Show 3 more filingsup to 47d gap

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

Leak-site claim

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

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.