Difference between revisions of "Go-live Checklist"
Jump to navigation
Jump to search
(Created page with "=Pre-Go-Live Preparation= <ol> <li><strong>User Training</strong><br/> Confirm that all users have completed the relevant training on PTS 5.<br/> Provide access to training materials and documentation.</li> <li><strong>Data Migration</strong><br/> Verify that all necessary data (users, wards) has been successfully imported to PTS 5.<br/> Perform data validation to ensure accuracy.</li> <li><strong>Infrastructure Readiness</strong><br/> Confirm that the required hardware...") |
|||
| Line 14: | Line 14: | ||
Test data restoration procedures.</li> | Test data restoration procedures.</li> | ||
</ol> | </ol> | ||
=System Configuration= | |||
<ol> | <ol> | ||
<li><strong>Config Verification</strong><br/> | <li><strong>Config Verification</strong><br/> | ||
| Line 23: | Line 23: | ||
(EPMA) Ensure seamless data flow between the dispensing software and PTS.</li> | (EPMA) Ensure seamless data flow between the dispensing software and PTS.</li> | ||
</ol> | </ol> | ||
=User Access and Support= | |||
<ol> | <ol> | ||
<li><strong>User Account Setup</strong><br/> | <li><strong>User Account Setup</strong><br/> | ||
| Line 33: | Line 33: | ||
</ol> | </ol> | ||
=Go-Live Day= | =Go-Live Day= | ||
Communication Plan | <ol> | ||
<li><strong>Communication Plan</strong><br/> | |||
Execute a communication plan to inform all users about the go-live date and process. | Execute a communication plan to inform all users about the go-live date and process.<br/> | ||
Provide contact information for support during the transition. | Provide contact information for support during the transition.</li> | ||
User Acceptance Testing (UAT) | <li><strong>User Acceptance Testing (UAT)</strong><br/> | ||
Conduct final user acceptance testing to identify any last-minute issues.<br/> | |||
Conduct final user acceptance testing to identify any last-minute issues. | Work with TMSi to address and resolve issues promptly.</li> | ||
<li><strong>Monitoring and Performance</strong><br/> | |||
Monitoring and Performance | Monitor system performance closely during the go-live period.<br/> | ||
Report any performance issues to IT and to TMSi.</li> | |||
Monitor system performance closely during the go-live period. | <li><strong>Contingency Planning</strong><br/> | ||
Have a contingency plan in place for critical issues.<br/> | |||
Contingency Planning | Ensure that key personnel are aware of escalation procedures.</li> | ||
</ol> | |||
Have a contingency plan in place for critical issues. | =Post-Go-Live= | ||
Ensure that key personnel are aware of escalation procedures. | <ol> | ||
Post-Go-Live | <li><strong>Post-Implementation Review</strong><br/> | ||
Post-Implementation Review | Conduct a post-implementation review to gather feedback from users.<br/> | ||
Identify areas for improvement and implement necessary changes.</li> | |||
Conduct a post-implementation review to gather feedback from users | <li><strong>Documentation Update</strong><br/> | ||
Identify areas for improvement and implement necessary changes. | Update system documentation based on any changes made during or after the go-live.</li> | ||
Documentation Update | <li><strong>Training Reinforcement</strong><br/> | ||
Provide additional training or support sessions if needed.<br/> | |||
Update system documentation based on any changes made during or after the go-live. | Address any recurring issues or user concerns.</li> | ||
Training Reinforcement | <li><strong>Performance Monitoring</strong><br/> | ||
Continue monitoring system performance post-go-live.<br/> | |||
Provide additional training or support sessions if needed. | Address any lingering issues.</li> | ||
Address any recurring issues or user concerns. | <li><strong>Celebration and Recognition</strong><br/> | ||
Performance Monitoring | Acknowledge the successful go-live with the team!<br/> | ||
Doughnuts suggested.</li> | |||
Continue monitoring system performance post-go-live. | </ol> | ||
Address any lingering issues | |||
Celebration and Recognition | |||
Acknowledge the successful go-live with the | |||
Revision as of 11:45, 19 January 2024
Pre-Go-Live Preparation
- User Training
Confirm that all users have completed the relevant training on PTS 5.
Provide access to training materials and documentation. - Data Migration
Verify that all necessary data (users, wards) has been successfully imported to PTS 5.
Perform data validation to ensure accuracy. - Infrastructure Readiness
Confirm that the required hardware (e.g. barcode scanners, label printers) and software (e.g. PTS Comms Client) is in place.
Verify server capacity and performance. - Backup and Recovery
Ensure that appropriate data backup and recovery mechanisms are in place.
Test data restoration procedures.
System Configuration
- Config Verification
Double-check that the system configuration (e.g. user views, prescription types) to ensure they align with your requirements.
Verify that user roles and permissions are correctly set up. - Integration Testing
Test integrations with other systems (e.g. patient lookup link on booking in screen).
(EPMA) Ensure seamless data flow between the dispensing software and PTS.
User Access and Support
- User Account Setup
Confirm that PTS user accounts are created for all necessary personnel.
Verify that login credentials are distributed securely. - Support
Create an account/s on tmsinsight.com.
Verify that relevant users can access the wiki.
Go-Live Day
- Communication Plan
Execute a communication plan to inform all users about the go-live date and process.
Provide contact information for support during the transition. - User Acceptance Testing (UAT)
Conduct final user acceptance testing to identify any last-minute issues.
Work with TMSi to address and resolve issues promptly. - Monitoring and Performance
Monitor system performance closely during the go-live period.
Report any performance issues to IT and to TMSi. - Contingency Planning
Have a contingency plan in place for critical issues.
Ensure that key personnel are aware of escalation procedures.
Post-Go-Live
- Post-Implementation Review
Conduct a post-implementation review to gather feedback from users.
Identify areas for improvement and implement necessary changes. - Documentation Update
Update system documentation based on any changes made during or after the go-live. - Training Reinforcement
Provide additional training or support sessions if needed.
Address any recurring issues or user concerns. - Performance Monitoring
Continue monitoring system performance post-go-live.
Address any lingering issues. - Celebration and Recognition
Acknowledge the successful go-live with the team!
Doughnuts suggested.