Medtech32 NES Reactivation for Customers on Medtech32 Version Release Notes & Installation Instructions. Version 22.

Transcription

1 Medtech32 NES Reactivation for Customers on Medtech32 Version 22.7 Release Notes & Installation Instructions Version 22.7 Build 5383 (May 2017) Please ensure that these Release Notes and Installation Instructions have been reviewed and are understood. This document contains important information for Medtech32 users. Please ensure that it is circulated among all relevant staff. We suggest that this document is filed safely for future reference. Copyright Medtech Limited Page 1 of 10

2 Introduction We recently advised of a potential security vulnerability due to the failing of encryption of the communication between the Medtech32 NES module and the Medtech NES Web Application. This release addresses the above issue and provides instructions on how to apply this patch and reactivate NES in your practice. IMPORTANT NOTE: REACTIVATING NES MODULE Follow the steps outlined in the Reactivating the NES Module in Medtech32 document to reactivate the NES Service within your practice once you have installed this patch. Ensure you have your new password available from your PHO before attempting to complete the reactivation process. NES Resolved Issues As part of this patch we have also included resolutions to two issues that had been highlighted by practices in relation to NES features: Description Category Impact When activating NES in the Medtech32 PMS by entering the NES Username the system was allowing spaces before or after the Username and there were no error messages to indicate that the credentials were invalid When editing non-core fields in the Patient Register (F3) screen (e.g. Mobile Ph, Notes, Marital status, etc.) for a validated patient, the Medtech32 PMS was, in some situations, incorrectly showing the patient was not synchronised, leading to the NHI number displaying in an orange colour. General Resolved Issues Other significant resolved issues in this release include the following: Admin Admin Minor Minor Description Category Impact Auto Recalls were not applying to new patients when added to the Patient Register without an Ethnicity selected Clinical Minor IMPORTANT NOTE There is no requirement to perform a standard Medtech32 Interbase Backup and Restore prior to applying this patch. However, you may wish to perform an Interbase Backup and Restore as part of your scheduled maintenance plan. Copyright Medtech Limited Page 2 of 10

3 Installation Prerequisites Checklist Check the current Medtech32 installed version [HelpAbout Medtech32] before installing this patch. The practice must be on one of the following Medtech32 versions: Version 22.7 Build 5242 Version 22.7 Build 5243 Version 22.7 Build 5345 Ensure all monitoring, third party software integrating with our database and automated backup software (e.g. Shadow protect) are turned off prior to installing the patch. 3. Before attempting to install the Version 22.7 Build 5383 patch, please ensure that a complete file level backup of the MT32 directory (including all databases located in the MT32\Data folder) has been completed successfully. 4. Ensure all users (including remote users) have logged out of Medtech32 and all scheduled utilities, backup or maintenance tasks, and third party interfaces and services that require access to the databases have been stopped. Please stop and start Interbase guardian services to reset all connections to the database(s). Please check that the following utilities/services have been stopped: Medtech Services Medtech32 Scheduler Windows Scheduler 5. NIR Directory Monitoring Utility Medtech Generic Directory Monitor Utility GP2GP Services Clinical Audit Tool (CAT) (if using) 6. Login to the Medtech32 Server with Administrative Rights. 7. If you are using Briefcasing, please ensure all Briefcasing laptops with outstanding briefcased data have been checked-in. Please also check that all Briefcasing laptops have been disconnected from the network before installing the patch. Copyright Medtech Limited Page 3 of 10

4 Installation Instructions 1. Visit our website at 2. Select New Zealand in the region drop down menu (top right-hand side of the screen). 3. Select the menu Support Medtech32 Downloads. The New Zealand Medtech32 Downloads page will be displayed. 4. Locate the release called Medtech32 Version 22.7 Build 5383 (May 2017) in the list. 5. Download the installer Medtech32 Version 22.7 Build 5383 May 2017 (EXE). Copyright Medtech Limited Page 4 of 10

5 Medtech32 Version 22.7 Build 5383 Server Installation 1. Ensure that you have completed and checked all the items in the Installation Prerequisites Checklist above. 2. Download the Version 22.7 Build 5383 Installer as described above. 3. Double-click on the Upgrade EXE to start the installation process. 4. Click I Accept button to continue. Copyright Medtech Limited Page 5 of 10

6 5. Select the Medtech32 Server Installation on this computer radio button and then click the Next button. 6. Ensure that all the points mentioned in the Installation Prerequisites Checklist are performed. Then tick the checkbox and click the Next button. 7. The Installation progress is shown. Copyright Medtech Limited Page 6 of 10

7 8. If there are any upgrade issues the below error message will be displayed and the installation will terminate. In this case, you need to go back to the previous file level back up. If no issues with the patch are encountered, it will continue with next step. 9. The Medtech Services will now be started. Once the installation is complete, the following message will be displayed: 10. Click OK to close the installation. 11. A prompt to reboot the server is displayed on completion of the installation. Please do so when required. MANDATORY POST-INSTALLATION STEPS Please ensure that ALL steps within the following Post-Installation Checklist have been reviewed and completed prior to the practice using the Medtech32 application after installing to Version 22.7 Build 5383 patch. Copyright Medtech Limited Page 7 of 10

8 Post-Installation Checklist 1. If any errors are encountered while installing Version 22.7 Build 5383, a rollback to the previous version is required using the complete file level backup of the MT32 directory (see Prerequisites point 3). Please contact Medtech Support for assistance and include screenshots. 2. If the installation complete message is not displayed (as shown in point 9 of the Server Installation section in this document), a rollback to the previous version is required using the complete file level backup of the MT32 directory (see Prerequisites point 3). Please contact Medtech Support for assistance and include screenshots. 3. Search for Error in MTStruct.Log (MT32\Bin folder) and in MTSQL32.log (MT32\Bin\Tools Folder) for the installation date. If there are any errors, a rollback to the previous version is required using the complete file level backup of the MT32 directory (see Prerequisites point 3). Please contact Medtech Support for assistance with the following details: MTStruct.log (MT32\Bin folder) MTSQL32.LOG (MT32\Bin\Tools folder) 4. Please reboot the server after installation if prompted Check that the patch has been run on all laptops that are used for Briefcasing and has completed without errors. Check the Version and Build of the replaced application EXEs: Right-click on the relevant EXE, select Properties from the menu, click on the Details tab and check the File Version. The required file version of each EXE is shown in brackets below: Medtech32 Main Application: Bin\MT32.exe [ ] Please ensure the following utilities/services that were stopped prior to installing this patch are restarted: Medtech Services Medtech32 Scheduler Windows Scheduler NIR Directory Monitoring Utility Medtech Generic Directory Monitor Utility GP2GP Services Clinical Audit Tool (CAT) (if using) Copyright Medtech Limited Page 8 of 10

9 8. Login to Medtech32 and ensure database connection is successful. Check that the database connection is successful for all registered databases. Please note: an additional integrity check has been introduced to ensure the installation was successful. If the installation was unsuccessful then an EXE will automatically run during the logon process. Should this occur please wait for this to complete. Other users will not be able to login while the EXE is running. The following warning message is displayed while logging into Medtech32 if the patch has not been succesfully installed Please follow the steps below to correct the issue: o If you have not already rebooted the server (point 4), then please reboot and try logging into Medtech32 again o If you still get the warning message, re-run the patch After re-running the patch, if you still get the warning message, roll back (Prerequisites Checklist point 3) and contact Medtech Support for assistance Check the current Medtech32 installed version [HelpAbout Medtech32]. After the patch has been run, this should read Version 22.7 Build Ensure that all staff can successfully log into Medtech32 without error Ensure that any errors encountered during the post-installation process have been captured and have been provided to Medtech Support for assistance. Remove the complete file level backup of the MT32 directory once the practice is satisfied there are no issues post-installation. Copyright Medtech Limited Page 9 of 10

10 Reactivation of the NES Module 1. Follow the steps outlined in the Reactivating the NES Module for Medtech32 document to reactivate NES Service within your practice. NOTE: ensure you have your new password available from your PHO before attempting to complete the reactivation process. After reactivating the NES module, you will need to run the NES Gap Catch-Up Utility. This will ensure that patients enrolled during the period the NES service was deactivated have their information sent to the NES. To run the NES Gap Catch-up Utility, go to Setup Connected Health Information Services NES Gap Catch-Up Utility. 2. We recommend you run the Gap Catch-Up Utility when the practice is not busy or after hours to avoid adversely impacting the performance of Medtech32 during busy times. 3. Follow the steps outlined in the Reactivating the NES Module for Medtech32 document to test that the NES Services have been reactivated successfully. For further information or any other queries, please contact Medtech Support via: Medtech32 application [Help Contact Support] Online chat: Phone: MEDTECH ( ) Copyright Medtech Limited Page 10 of 10