Hot Fixes - and making the decision to install them or not

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Revision as of 18:32, 18 March 2009 by Paula.Peter (talk | contribs) (New page: == Hot Fixes - and making the decision to install them or not == A Hot Fix is an adjustment to the code of the Enterprise EHR to resolve specific issues. '''The process''' The Hot Fix...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Hot Fixes - and making the decision to install them or not

A Hot Fix is an adjustment to the code of the Enterprise EHR to resolve specific issues.

The process

The Hot Fix is Announced

The Hot Fix is announced and a Release Document is provided by Allscripts

The Hot Fix Release Document may be found on the KB

The Technical Team reviews the Hot Fix and determines if the client would benefit from it or not

The client reviews the Hot Fix to determine if they would benefit from it or not


Pre-Requisites for installing in Live Production Environment

Before any Hot Fix can be applied to a clients Live production environment it must be thoroughly and completely tested in their V11 Test Environment.

Is it worth it?

Although all hot fixes should be considered, some are definitely more necessary than others.

If the Hot Fix will fix a clients Critical Issue – It’s worth it

If the Hot Fix is necessary to fix a “Patient Safety” issue – It’s a must

If the client is upgrading and has not yet started testing their v11 Test System – It’s worth it

If the Hot Fix does not offer specific resolution to a client’s critical issue – It may not be worth it

If the client has just finished testing their new v11 test System – It may not be worth it

If the client does not have the resources to thoroughly test the test system after the Hot Fix has been applied – It may not be worth it

If it’s not broken don’t fix it

This often applies to hot fixes, but not always. Although Hot Fixes are designed to resolve/fix specific issues, it is never a guarantee that the fix will not affect a module or feature not listed on the Hot5 Fix Release Document. This is why it is critical that after a Hot Fix regardless of size, it is tested intensely before installing it on the clients Live Production System.

New Active X and Web Controls

Please be aware that most often there are new web/active x controls that will need to be installed

Moving Forward with the Hot Fix

Once the decision is made to move forward with a Hot Fix…

The Upgrade Technician and Client PM will schedule the installation

The client will backup their v11 Test Server and notify the Upgrade Technician

The Upgrade Technician will install the Hot Fix on the clients V11 Test System

The client must perform complete and thorough testing of their new v11 environment

Upgrading?

If you are in the process of an upgrade the Hot Fix will be installed on the Live system during Go-Live weekend so that the v11 Test and v11 Live Systems match.

If you are not in the process of an upgrade…The client will work with Support to complete the Hot Fix process.