Difference between revisions of "Upgrade Timeline and Dependencies"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
Line 2: Line 2:
  
  
The upgrade is divided into Phases.  Phase 1 consists of all of the components of Touchworks V11/Allscripts EHR except for V11 note.  Your users will be able to go-live on V11 while still using their V10 note, and V11 note will be configured and rolled out in Phase 2.  Below is a rough timeline of what to expect with dependencies in bold italics.  When discussing the upgrade timeline with your account manager it is iporant to understand that the initial timeline is a tentative timeline based on everything running smoothly.  There are times when there is hardware issue or a critical upgrade issue that could affect your timeline and proposed go-live date.
+
The upgrade is divided into Phases.  Phase 1 consists of all of the components of Touchworks V11/Allscripts EHR except for V11 note.  Your users will be able to go-live on V11 while still using their V10 note, and V11 note will be configured and rolled out in Phase 2.  Below is a rough timeline of what to expect with dependencies in bold italics.  When discussing the upgrade timeline with your account manager it is important to understand that the initial timeline is a tentative timeline based on everything running smoothly.  There are times when there is hardware issue or a critical upgrade issue that could affect your timeline and proposed go-live date.
  
 
== '''Initial Engagement with you Account Manager''' ==
 
== '''Initial Engagement with you Account Manager''' ==
Line 21: Line 21:
 
**'''''Project Team Education''''' - Project team education is required prior to test upgrade.
 
**'''''Project Team Education''''' - Project team education is required prior to test upgrade.
 
**'''Tollgate 1 Call''' -  '''''The Tollgate call must occur prior to the Test Upgrade''''' A "tollgate" call is a go/no go call.  The tollgate one call is the go/no go call for the Test upgrade.  We will review any action items that are unresolved, any software/hardware changes that need to be in place for the test upgrade to occur, ensuring that a full system backup is taken prior to the test upgrade, confirm onsite timeline for configuration, sign off on the project plan,  review testing strategy & issue reporting.
 
**'''Tollgate 1 Call''' -  '''''The Tollgate call must occur prior to the Test Upgrade''''' A "tollgate" call is a go/no go call.  The tollgate one call is the go/no go call for the Test upgrade.  We will review any action items that are unresolved, any software/hardware changes that need to be in place for the test upgrade to occur, ensuring that a full system backup is taken prior to the test upgrade, confirm onsite timeline for configuration, sign off on the project plan,  review testing strategy & issue reporting.
**'''Test Upgrade''' - '''''Prior to the Test Upgrade, project team education must be complete, any show-stoppers identified in the tollgate call must be addressed and a complete system backup has been taken.''''' The Test upgrade and initial testing will take 2-4 days and must happen 1 week prior to the on-site configuration week.
+
**'''Test Upgrade''' - '''''Prior to the Test Upgrade, project team education must be complete, any show-stoppers identified in the tollgate call must be addressed and a complete system backup must been completed.''''' The Test upgrade and initial testing will take 2-4 days and must happen at least 1 week prior to the on-site configuration week.
**'''Configuration on-site visit''' - (1 Week) The Galen/Allscripts Upgrade Consultant will come to your Organization for one week and meet with the project team to review the [[Build Workbook (BW)]], review the configuration tasks build work necessary for the upgrade and determine a plan for configuration with your project team.  The Upgrade consultant will also review your current workflows and the certified V11 workflows in order to determine if there are any changes needed to your workflow or additional workflow testing needed.
+
**'''Configuration on-site visit''' - (1 Week) The Galen/Allscripts Upgrade Consultant will visit your organization for one week and meet with the project team to review the [[Build Workbook (BW)]], review the configuration tasks and build work necessary for the upgrade and to determine a plan for configuration.  The Upgrade consultant will also review your current workflows against the certified V11 workflows to determine if there are any major gaps to resolve, changes to be made or if additional workflow testing will be needed.
**'''Build/Configuration''' - (3 weeks) - The project team will spend two weeks configuring the V11 system to work best for your end-users.  
+
**'''Build/Configuration''' - (3 weeks) - The project team will spend at least 3 weeks configuring a V11 system that works best for your organization and end-users.  
**'''Testing''' (5-6 weeks) - The Project team will test the V11 system and configuration through using both a [[Smoke Test]] and working through the certified workflows to ensure everything is working properly.  Any issues uncovered during testing will be logged into webfirst and the Galen/Allscripts Upgrade Team will assist with resolving those issues.  Concurrent with testing, your education team will be developing a plan for end user training.
+
**'''Testing''' (5-6 weeks) - The Project team will test the V11 system and configuration using both a [[Smoke Test]] and your certified workflows to ensure everything is working properly.  Any issues uncovered during testing will be logged into webfirst and the Galen/Allscripts Upgrade Team will assist with resolving those issues.  Concurrent with testing, your education team will be developing a plan for end user training.
**'''Tollgate 2 meeting''' - '''''All testing is to be complete prior to the Tollgate 2 meeting.  The Tollgate 2 meeting should occur 2 weeks before end-user training is to begin.  The Project Manager needs to have education scedule and materials to review at least 3 weeks prior to the beginning of end user training.'''''
+
**'''Tollgate 2 meeting''' - '''''All testing is to be complete prior to the Tollgate 2 meeting.  The Tollgate 2 meeting should occur 2 weeks before end-user training is to begin.  The Project Manager needs to receive your training plan, schedule and material at least 3 weeks prior to the beginning of end user training.'''''
**'''Phase 1 End User Training''' (2-4 weeks depending on size of organization)  '''''Configuration must be complete prior to end-user training.  The Tollgate 2 call should occur two weeks prior to the beginning of end-user training'''''  We recommend planning end-user training to occur as close to go-live as possible in order to ensure that the information is fresh in the minds of the users.  This way also if anything should occur in the upgrade process that affects your go-live date you may be able to post-pone your end-user training to be in line with the revised go-live date.   
+
**'''Phase 1 End User Training''' (2-4 weeks depending on size of organization)  '''''Configuration must be complete prior to end-user training.  The Tollgate 2 call should occur two weeks prior to the beginning of end-user training'''''  We recommend planning end-user training to occur as close to go-live as possible in order to ensure that the information is fresh in the minds of the users.  This way if anything should occur in the upgrade process that affects your go-live date you may be able to post-pone your end-user training to be in line with the revised go-live date.   
**'''Phase 1 Go-Live Planning''' (Begin planning 4 weeks prior to Go-Live) - The two teams will work together to develop the go-live playbook including a detailed plan for the week prior to go-live and go-live weekend. 2 weeks prior to go-live the plan should be reviewed by both teams and finalized.
+
**'''Phase 1 Go-Live Planning''' (Begin planning 4 weeks prior to Go-Live) - The two teams will work together to develop the go-live playbook; including a detailed plan for the week prior to go-live and go-live weekend. 2 weeks prior to go-live the plan should be reviewed by both teams and finalized.
**'''Phase 1 Go-Live''' - The Galen/Allscripts Upgrade Consultant will travel to your site for the go-live weekend.  The Upgrade Tech will upgrade your live system and the Upgrade Consultant will work to move all of the configuration built in the test system over to the live system.  The Upgrade consultant will stay on site until Thursday of Go-live week to troubleshoot any issues that may arise post-go-live and to provide support to the project team.
+
**'''Phase 1 Go-Live''' - The Galen/Allscripts Upgrade Consultant will travel to your site for the go-live weekend.  The Upgrade Tech will upgrade your live system and the Upgrade Consultant will work to move all of the configuration built in the test system over to the live system.  The Upgrade consultant will stay on site Monday thruugh Wednesday of Go-live week to troubleshoot any issues that may arise post-go-live and to provide support to the project team.
 
**'''Phase 1 Transition to Support''' - After Go-Live, support for Touchworks V11/ Allscripts EHR will transfer from the Upgrade team to support.  The Upgrade team will continue to work with you on the implementation and roll-out strategy for note.
 
**'''Phase 1 Transition to Support''' - After Go-Live, support for Touchworks V11/ Allscripts EHR will transfer from the Upgrade team to support.  The Upgrade team will continue to work with you on the implementation and roll-out strategy for note.
 
*Phase 2
 
*Phase 2

Revision as of 23:13, 17 November 2008

Upgrade Timeline and Dependencies

The upgrade is divided into Phases. Phase 1 consists of all of the components of Touchworks V11/Allscripts EHR except for V11 note. Your users will be able to go-live on V11 while still using their V10 note, and V11 note will be configured and rolled out in Phase 2. Below is a rough timeline of what to expect with dependencies in bold italics. When discussing the upgrade timeline with your account manager it is important to understand that the initial timeline is a tentative timeline based on everything running smoothly. There are times when there is hardware issue or a critical upgrade issue that could affect your timeline and proposed go-live date.

Initial Engagement with you Account Manager

  • Establish Contract
  • Hardware to be used in both Test and Live for V11 is in place
  • Health Check - The health check is a process where Allscripts runs some performance tests on your system and reviews you current server environment to ensure that you have the system requirements needed to successfully run V11. The Allscripts resource completing the Health check will prepare a report that will outline any areas that need to be addressed (if any) before moving forward with the upgrade. If there are action items from the health check, these must be completed prior to the test upgrade
  • Customization Review - An Allscripts resource will review any customizations that have been built for your system to determine if they are still necessary in V11 and if so, how to carry them over to your new test system.
  • Creation of the SOW (Statement of Work) for the upgrade
  • Education Prerequisites - Your account manager will provide you with the Allscripts education calender and will encourage you to get scheduled for your prerequisite training. We recommend attending your in person education classes within at least a month of your on-site configuration week so that the information is fresh.Allscripts requires V11 Upgrade training prior to the beginning of the test upgrade

Work with your Upgrade Team

  • Phase 1
    • System Certification
    • Technical Call - This call is conducted in order to: Review Action Items from Health Check call, Review Upgrade Questionnaire, Review Environment Diagram (Current and Future), Review Results from System Certification, Review Interfaces, Final discussion to allow Account Manager to create SOW
    • Intro Call (2-3 Weeks Prior to test upgrade) - This call is conducted in order to introduce the members of the Galen/Allscripts Upgrade team, to establish a time for regular weekly meetings over the course of the project, review any action items from the technical call, ensure a plan is in place for the project team to attend required training, review the contract and statement of work, to conduct a technical review, and outline a tentative timeline for the project
    • Project Team Education - Project team education is required prior to test upgrade.
    • Tollgate 1 Call - The Tollgate call must occur prior to the Test Upgrade A "tollgate" call is a go/no go call. The tollgate one call is the go/no go call for the Test upgrade. We will review any action items that are unresolved, any software/hardware changes that need to be in place for the test upgrade to occur, ensuring that a full system backup is taken prior to the test upgrade, confirm onsite timeline for configuration, sign off on the project plan, review testing strategy & issue reporting.
    • Test Upgrade - Prior to the Test Upgrade, project team education must be complete, any show-stoppers identified in the tollgate call must be addressed and a complete system backup must been completed. The Test upgrade and initial testing will take 2-4 days and must happen at least 1 week prior to the on-site configuration week.
    • Configuration on-site visit - (1 Week) The Galen/Allscripts Upgrade Consultant will visit your organization for one week and meet with the project team to review the Build Workbook (BW), review the configuration tasks and build work necessary for the upgrade and to determine a plan for configuration. The Upgrade consultant will also review your current workflows against the certified V11 workflows to determine if there are any major gaps to resolve, changes to be made or if additional workflow testing will be needed.
    • Build/Configuration - (3 weeks) - The project team will spend at least 3 weeks configuring a V11 system that works best for your organization and end-users.
    • Testing (5-6 weeks) - The Project team will test the V11 system and configuration using both a Smoke Test and your certified workflows to ensure everything is working properly. Any issues uncovered during testing will be logged into webfirst and the Galen/Allscripts Upgrade Team will assist with resolving those issues. Concurrent with testing, your education team will be developing a plan for end user training.
    • Tollgate 2 meeting - All testing is to be complete prior to the Tollgate 2 meeting. The Tollgate 2 meeting should occur 2 weeks before end-user training is to begin. The Project Manager needs to receive your training plan, schedule and material at least 3 weeks prior to the beginning of end user training.
    • Phase 1 End User Training (2-4 weeks depending on size of organization) Configuration must be complete prior to end-user training. The Tollgate 2 call should occur two weeks prior to the beginning of end-user training We recommend planning end-user training to occur as close to go-live as possible in order to ensure that the information is fresh in the minds of the users. This way if anything should occur in the upgrade process that affects your go-live date you may be able to post-pone your end-user training to be in line with the revised go-live date.
    • Phase 1 Go-Live Planning (Begin planning 4 weeks prior to Go-Live) - The two teams will work together to develop the go-live playbook; including a detailed plan for the week prior to go-live and go-live weekend. 2 weeks prior to go-live the plan should be reviewed by both teams and finalized.
    • Phase 1 Go-Live - The Galen/Allscripts Upgrade Consultant will travel to your site for the go-live weekend. The Upgrade Tech will upgrade your live system and the Upgrade Consultant will work to move all of the configuration built in the test system over to the live system. The Upgrade consultant will stay on site Monday thruugh Wednesday of Go-live week to troubleshoot any issues that may arise post-go-live and to provide support to the project team.
    • Phase 1 Transition to Support - After Go-Live, support for Touchworks V11/ Allscripts EHR will transfer from the Upgrade team to support. The Upgrade team will continue to work with you on the implementation and roll-out strategy for note.
  • Phase 2
    • Note Configuration (Pilot group)
    • Note Testing (Pilot Group)
    • Note Final Issue Resolution (Pilot Group)
    • Note Go-Live Planning
    • Note Go-Live (Pilot Group)
    • Note Transition to Support
    • Note Roll out to other users.