Computer Virus Forces Hospital To Divert Ambulances

McGruber writes "The Atlanta Journal Constitution newspaper is reporting that a hospital with campuses in Lawrenceville and Duluth, Georgia turned ambulances away after the discovery of 'a system-wide computer virus that slowed patient registration and other operations.' They're only currently accepting patients with 'dire emergencies.' A spokeswoman for the hospital said the diversion happened because 'it's a trauma center and needs to be able to respond rapidly.' The situation began on Thursday afternoon and is expected to last through the weekend."

Comments

Nuisance, Not Crisis

[stevedog]

I work at a trauma center, and we go to diversion all the time. It happens whenever the ER gets backed up to the point that the patients would be better served by going to a less-full ER than by coming to ours, even if that ER is a little further away. This happens at least twice weekly, although perhaps not as often as other, less busy ERs. Yes, the virus undoubtedly brought them to this clogged state much faster, but this isn't nearly the crisis the summary (or the article it is summarizing) makes it out to be.

Re:We're in a sad state when...

[Datamonstar]

I'm currently inside a hospital data center and I can tell you that windows is behind the scenes of a lot of the systems we use. Everyone in "the know" thinks it sucks that the majority of the problems we encounter is because of borked hardware configurations in appliance machines or Windows servers. We are on mainframe (as of today, it's still the only way to get everyone's critical data to almost a dozen moajor sites at once with 99.9 uptime and I don't see us abandoning it anytime soon) and there is a god-damned Windows server that is only used to encode EDI transactions to the JES2 spooler that always crashes, causing the spool to fill up, endangering the entire system. It's a very serious problem as the only solution to it once JES is full is to IPL the system.

The server in question doesn't even show an error message. Well, sometimes it does, sometimes it doesn't. you can stop and start the services all you like, but you're just wasting time as the JES2 spool gets bigger. The only solution is to reboot the Windows Server. It is redundantly mirrored, but we any of you with any sense will know that this does not make the situation any less frightening. The mirror is bound to be subject to the exact same problem, since it's software-related, which would put you back at square 1 in the event of a fail-over.

Don't even get me started about malware. Of course, all the workstations throughout the system are Windows systems. Those should not matter in case of a power outage or system-wide failure because we have downtime procedures in place, but let's face it, we'd be majorly crippled if we were to ever loose our entire network and it would likely impair our ability to serve customers. Although it shouldn't. So far we've been lucky.