The ransomware attack on Frederick Health on 27 January 2025 forced critical systems offline, led to ambulances being diverted to other emergency departments, delayed patient care, cancelled appointments and disrupted operations across multiple facilities. The exposure affected more than 934,000 patients, recorded at 25-0127.
Two Files, Two Different Harms
The record count is the notifiable event. It produces a filing, an affected number, a credit monitoring offer and, in due course, litigation of the kind at 25-1228.
The diversion produces none of those. No register records that an ambulance travelled further on a particular night. It is the availability gap at 26-0209, in the sector where it is least abstract.
Diversion Is Measurable And Nobody Aggregates It
This is what makes the omission avoidable rather than inherent. Emergency medical services already record diversion status, receiving facility and transport time as routine operational data. The measurement exists.
What does not exist is any mechanism connecting it to a cyber incident. The corpus filed at 25-0715 that one hospital in three reports care impact, and that the figure measures *disruption* rather than *harm* — self-reported, spanning a rescheduled appointment to a delayed intervention.
Diversion minutes would be a harder number. It is collected already, and connecting it to an incident date would require somebody to decide the question is worth answering — the same conclusion this desk reached about breach-to-fraud causation at 25-1219.
And The Corpus Should Not Overstate It Either
Diversion is a routine emergency-medicine practice used for capacity, staffing and specialty availability. Hospitals divert without any cyber incident, regularly.
That an attack caused diversion is established. That any specific patient was harmed by it is not, and this desk does not assert it — the same discipline applied at 25-0715.
Compiled from public reporting, listed below. Diversion and care delay are as reported. No patient harm is established and none is asserted. Corrections: corrections@forensicpost.com.