FierceHealthcare FierceHealthIT FierceMobileHealthcare FierceHealthPayer
FierceHealthFinance FierceEMR FiercePracticeManagemtn Hospital Impact

Be sure to checkout FierceEMR for Meaningful Use updates!

Network reliability becomes ever more critical as systems proliferate

It's a simple truth about information technology: The more you have, the more you have to lose. Any CIO who's ever had to deal with network downtime can tell you that.

An escalating series of events, starting with the random act of a tree hitting a power line on an otherwise sunny morning, knocked the EMR offline at Fletcher Allen Health Care in Burlington, Vt., for more than four hours in August, just two months after the health system had turned on the EMR. Two sets of battery back-ups failed, sending an electrical spike through the lines that disabled storage hardware. Then the "failover" software that switches functions to one server when another goes down also malfunctioned.

"If you audited this and looked at what we did with failover and mirroring, you'd say, 'Wow, this thing is never going to go down.' And that's what we thought. When you line up the scenario that happened to us, you realize that you can't replicate this in a million years," CIO Chuck Podesta tells Healthcare Informatics. But it happened. And has happened to others. And will likely happen to more healthcare organizations as they bring up more IT applications.

While it's impossible to assure 100 percent reliability, many health systems are looking at multiple backups, dual data and power feeds and increasingly popular virtualization technologies. And they constantly test their capabilities. Thibodaux Regional Medical Center in Louisiana takes its servers down every 90 days for maintenance. Carilion Clinic in Roanoke, Va., has local backups and read-only mode so clinicians can continue working even during scheduled downtime.

To learn more about these strategies for network reliability:
- read this Healthcare Informatics story

Related Articles:
San Francisco nursing home turns to SaaS for network monitoring
EMR fails following power outage at VT hospital

SHARE WITH:
Email Twitter Facebook LinkedIn StumbleUpon
Get Your FREE FierceHealthIT Email Newsletter:
Comments (1) | Post a comment

Comments

One of the problem with clusters can easily be seen in this example. They are meant for recovery from failure, not failure prevention and do nothing to track and save data in-flight.

If they had fault tolerant servers (or even HA software), the system still would have failed (no power), but their recovery would have not taken the extra 5 hours to sort out the status of the information.

Post new comment

The content of this field is kept private and will not be shown publicly.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.