Migrating to New Code Levels
By Kris Galezewski

While planning a migration to new code levels, it is important to follow processes similar to a new implementation. In order to have a successful upgrade, it is imperative to plan and test appropriately. Below are some high level topics that deserve focus during a migration.

Create a Test plan:

1. Multiple testing cycles; i.e. 2- two week testing cycles with issue resolution between cycles
2. Review issues daily during testing cycles
3. Track issue resolution progress daily
4. Create a testing strategy for installation of new service package. Decide who will execute testing and how the service package affect multiple solutions
5. Determine go/no go decision deadline
6. Identify and define issue priorities: Go Live (cannot go Live without priorities because it has a major impact on process or patient care), High (issue requires resolution soon after conversion), Medium (requires some attention but can wait on the resolution), Low (issue does not affect patient safety)
7. Identify impact to end user if issues with High, Medium, or Low priority are not corrected at the time of an upgrade. Determine if there is a satisfactory workaround to the issue

Domain strategy

1. Necessary for tracking and installing new service packages
2. Determine if new development will parallel integration testing. If so, include new project build in the testing timeline
3. Copy of domains and or domain upgrade
4. Change control to track system changes so they are used as a checklist for any build changes in the PRODUCTION domain
5. Update new code into the Train domain
6. Decide when to install new service package for corrections
7. Identify domain to install service packages for testing
8. Develop a time frame for updating the non prod domains: Train, Cert, Build

Develop testing scenarios

1. Integrate all solutions: PowerChart^®, PCO, Scheduling, lab system, rad system, transcription, billing
2. Use real life scenarios
3. Track new development to determine if new projects should be introduced into the testing cycle

Core Build

1. Create generic user positions for testing
2. Build appropriate security for generic users: organization security
3. If using Cerner scheduling, consider scheduling security build, resource build. Lock & key functionality
4. Interfaces: identify build for new locations if necessary
5. Verify downstream systems have built generic providers to be used in testing. If not, designate an active provider for example for testing in the non-prod domain

Training materials

1. Determine how new functionality will be communicated to the customer
2. Develop training materials
3. Inform staff of new features

As with any install/upgrade, planning and testing are the keys to success. It is important to focus on the areas above with as much detail as would be done for a new application installation. For each application area being upgraded, similar care needs to be taken.

For further information call us at (610) 444-1233 or visit our website at www.getvitalized.com.