November 9, 2015 – It’s Monday and the day starts like any other at your hospital. Patients are arriving for their appointments, doctors are rotating shifts, and IT operations are running smoothly. Then, you hear a knock at your door. It’s one of your top IT staff members and he has some bad news — he received an offer from a competing facility and he’s resigning, effective immediately.

What does this mean for your organization?

If you’re not prepared for that departure, it could be disastrous. Here’s why: At many healthcare facilities, data centers are managed on-premise and the organization is dependent on hundreds of legacy applications. In that scenario, IT staff often hold the keys to the kingdom because they possess the knowledge (and credentials) to keep that infrastructure operational. If you haven’t created a plan to limit your dependence on their expertise before they walk out the door, it can expose your facility to significant technological and operational risk.

So, how can you protect against this? In short: Move to the cloud.

While it’s impossible to completely remove your dependence on IT staff and some technology will need to stay on-premise, what you can (and should) do is create redundancies that take certain day-to-day processes and responsibilities out of human hands. The virtual cloud empowers this shift by:

  • Relocating infrastructure (servers, VM’s, the network, etc.) externally. This protects your facility from the loss of a key individual who’s responsible for keeping it all going. When IT staff no longer hold the keys to the kingdom, you no longer need to worry about how or when important updates and maintenance will be completed.
  • Virtualizing applications to create greater control over how you deliver them (physical or virtual desktop). This can create greater flexibility and control for your facility, while also removing the overhead of maintaining how those applications are delivered to the end user. As a result, this critical aspect of IT is less reliant on specific IT staff, which protects your organization and frees up employees to focus on more important tasks.

It’s important to keep in mind that there may not be any warning signs before an IT employee leaves. Their departure might be money related, or it might be prompted by a spouse’s relocation. Regardless of the reason, the last thing you want is to find yourself in a position where losing someone negatively impacts day-to-day operations, team efficiency, or patient care.

Transitioning to the cloud before this becomes a problem is a simple way to mitigate this risk.

This not only lessens your reliance on key IT people to keep the proverbial lights on, it also creates an environment for IT staff to thrive, learn and grow. Instead of focusing on mundane, day-to-day maintenance, they’ll be able to focus on strategic builds and key business challenges. It’s a win-win for everyone, and you can rest assured that your facility is vaccinated against the loss of any one person.

2017-07-27T00:00:59+00:00 November 9th, 2015|News|

About the Author:

Fatal error: Uncaught exception 'GuzzleHttp\Exception\ClientException' with message 'Client error: `POST` resulted in a `400 Invalid instrumentation key` response: {"itemsReceived":1,"itemsAccepted":0,"errors":[{"index":0,"statusCode":400,"message":"Invalid instrumentation key"}]} ' in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 Stack trace: #0 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Middleware.php(66): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response)) #1 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response)) #2 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(156): GuzzleHttp\Promi in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113