Difference between revisions of "Go-live Checklist"

From TMS Support Wiki
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...")
 
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
Here is a simple suggested go-live checklist for a PTS 5 installation or upgrade.
While we recognise that PTS is highly configurable, and installation and configuration is a fluid process, we offer this document as a reference for your own go-live plan.
=Pre-Go-Live Preparation=
=Pre-Go-Live Preparation=
<ol>
<ol>
Line 13: Line 16:
Ensure that appropriate data backup and recovery mechanisms are in place.<br/>
Ensure that appropriate data backup and recovery mechanisms are in place.<br/>
Test data restoration procedures.</li>
Test data restoration procedures.</li>
<li><strong>Wipe Test Data</strong><br/>
This T_SQL script will remove all prescription data from the database, whilst preserving system configuration (setup pages, application settings etc.)<br/>
Never run this on a live system!<br/>
<blockquote><nowiki>TRUNCATE TABLE [PatientDrugs]
TRUNCATE TABLE [Patients]
TRUNCATE TABLE [PrescriptionNotes]
TRUNCATE TABLE [Events]
TRUNCATE TABLE [PrescriptionChangeAudits]
DELETE FROM [Prescriptions]</nowiki></blockquote></li>
</ol>
</ol>
==System Configuration==
 
=System Configuration=
<ol>
<ol>
<li><strong>Config Verification</strong><br/>
<li><strong>Config Verification</strong><br/>
Line 23: Line 36:
(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==
=User Access and Support=
<ol>
<ol>
<li><strong>User Account Setup</strong><br/>
<li><strong>User Account Setup</strong><br/>
Line 33: Line 46:
</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>
Address and resolve issues promptly.
<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/>
Address any performance issues in real-time.
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 and stakeholders.
<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 promptly.
Celebration and Recognition:
 
Acknowledge the successful go-live with the project team and stakeholders.

Latest revision as of 16:10, 24 January 2024

Here is a simple suggested go-live checklist for a PTS 5 installation or upgrade.

While we recognise that PTS is highly configurable, and installation and configuration is a fluid process, we offer this document as a reference for your own go-live plan.

Pre-Go-Live Preparation

  1. User Training
    Confirm that all users have completed the relevant training on PTS 5.
    Provide access to training materials and documentation.
  2. Data Migration
    Verify that all necessary data (users, wards) has been successfully imported to PTS 5.
    Perform data validation to ensure accuracy.
  3. 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.
  4. Backup and Recovery
    Ensure that appropriate data backup and recovery mechanisms are in place.
    Test data restoration procedures.
  5. Wipe Test Data
    This T_SQL script will remove all prescription data from the database, whilst preserving system configuration (setup pages, application settings etc.)
    Never run this on a live system!

    TRUNCATE TABLE [PatientDrugs] TRUNCATE TABLE [Patients] TRUNCATE TABLE [PrescriptionNotes] TRUNCATE TABLE [Events] TRUNCATE TABLE [PrescriptionChangeAudits] DELETE FROM [Prescriptions]

System Configuration

  1. 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.
  2. 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

  1. User Account Setup
    Confirm that PTS user accounts are created for all necessary personnel.
    Verify that login credentials are distributed securely.
  2. Support
    Create an account/s on tmsinsight.com.
    Verify that relevant users can access the wiki.

Go-Live Day

  1. 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.
  2. User Acceptance Testing (UAT)
    Conduct final user acceptance testing to identify any last-minute issues.
    Work with TMSi to address and resolve issues promptly.
  3. Monitoring and Performance
    Monitor system performance closely during the go-live period.
    Report any performance issues to IT and to TMSi.
  4. Contingency Planning
    Have a contingency plan in place for critical issues.
    Ensure that key personnel are aware of escalation procedures.

Post-Go-Live

  1. Post-Implementation Review
    Conduct a post-implementation review to gather feedback from users.
    Identify areas for improvement and implement necessary changes.
  2. Documentation Update
    Update system documentation based on any changes made during or after the go-live.
  3. Training Reinforcement
    Provide additional training or support sessions if needed.
    Address any recurring issues or user concerns.
  4. Performance Monitoring
    Continue monitoring system performance post-go-live.
    Address any lingering issues.
  5. Celebration and Recognition
    Acknowledge the successful go-live with the team!
    Doughnuts suggested.