The scariest words in a hospital shouldn’t be “systems are down,” but that’s exactly what John hears while he’s lying in a bed with crushing pain, fever, and doctors worried an infection could be moving toward sepsis. He came in expecting fast answers and coordinated care. Instead, he watches a modern emergency workflow buckle under a ransomware incident, and he feels the emotional whiplash that comes when patient safety suddenly depends on clipboards, phone calls, and memory.

We talk through what a healthcare cyberattack looks like from the patient’s side: staff scrambling to find orders they can’t see, “shortly” turning into long delays for antibiotics, lab results arriving slowly or needing retesting, and the constant uncertainty of not knowing what comes next. John describes how electronic health record downtime changes the tone of care, not because clinicians stop caring, but because systems that normally keep treatment organized and safe are no longer available. The result is a roller coaster of fear, especially when every minute feels like it matters.

Then we follow the story past the hospital stay. John ends up admitted longer than expected, leaves with shaken confidence in the health system, and receives no post-discharge outreach or apology. That silence becomes part of the lasting impact, raising a hard question for healthcare cybersecurity leaders, IT teams, and administrators: how do we rebuild trust after ransomware, and how do we communicate in a way that supports patients without creating more confusion?

If you care about ransomware defense, incident response, patient safety, and cyber resilience in healthcare, listen now, then subscribe, share the episode with someone in healthcare, and leave a review so more people hear what downtime really costs.