Supporting Downtime in a Clinical Setting

For the average application, IT professionals strive to minimize downtime. But when it happens – as it inevitably will – the users are simply forced to wait until the system is once again available.

In a clinical setting, this strategy is not acceptable. Regardless of whether the system unavailability is caused by an outage in your server or the hospital’s connectivity to it, the hospital must address the question: How will we continue to care for patients until the system comes back up?

A typical fallback strategy is paper. Today’s hospitals are being pushed to cut costs and go paperless, though, and having everything printed from the system, just in case there’s an outage, does not sit well with those working toward these goals.

One recent application built by NVISIA solved this problem in a very straightforward way. Each hospital department using the application configured a daily report, including an FTP location on their own LAN where the report should be sent. Each night in batch, the application generates and sends the downtime reports to their respective locations. Each morning, the department managers review their downtime report and copy it to their local machine.    In the event of a system downtime, the local daily downtime report is available to continue department operations.

This strategy allows the hospitals to remain paperless, while adequately accounting for downtime.Unless the system, the FTP server and the department manager’s computer are simultaneously unavailable, patient care is uninterrupted.