DisclosureLens
ARIZONAHackingHealthcareHealthcareHealth (basic)Identity (basic)High

SimonMed Imaging

bd_654acdd2bf01fd0c · schema v1 · pii pii-v1

Severity

High

Discovered

—

Filed

Mar 27, 2025

To disclose

—

Affected

1,275,669

Linked

11 records

Confidence

70%
Full breach record for SimonMed Imaging →

SimonMed Imaging reported to HHS on 2025-03-27 a Hacking/IT Incident affecting 1275669 individuals. Breached information located on Network Server.

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

Mar 27, 2025

Filed

No interval is drawn: no breach start or discovery date is on record for this filing.

This filing is one of 11 records about the same incident.View merged incident
A leak claim by medusa about this victim was first seen 45 days before this filing.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (9) · sorted by filing gap

Show 5 more filings ↓up to 201d gap

Filing propagation · 10 filings · 10 states

View merged incident ↗

Pattern: first filing Mar 27 (AZ), last Oct 14 (NH) — a 201-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.