This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Check the current Medtech32 installed version [HelpAbout Medtech32] before attempting this upgrade. The practice must be on one of the following Medtech32 versions:
Version 22.4 Build 5146,5159,5166 Version 22.6 Build 5195,5220,5221
2. Ensure all customised Monitoring, Third party softwares integrating with our database and automated backup softwares (e.g. Shadow protect) if there are any, are turned off during this process.
3.
This release requires a mandatory InterBase database backup and restore. Please note that backup and restore is also applicable to Briefcasing databases. Click here for the Database Backup and Restore Guide. The Installer will validate the backup and restore prerequisite before upgrade. NOTE: Backup and restore must be performed on all databases configured in the MT32.ini file. If you do not want to perform backup and restore on a particular database, then remove the configuration section related to that database from the MT32.ini file or comment “i.e. //” the related database section.
4.
Before attempting to run the Version 22.6 Build 5223 upgrade, 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.
5.
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 databases.
6.
Check that the following utilities/services have been shut down or stopped: Medtech32 Scheduler Windows Scheduler NIR Directory Monitoring Utility Medtech Generic Directory Monitor Utility Medtech Services GP2GP Services
6.
The Medtech and GP2GP Services are being upgraded during this installation and will be stopped and restarted automatically. However, as a precaution, please ensure that the Medtech & GP2GP Services have been stopped prior to running this update.
7. Ensure that the Medtech Clinical Audit Tool [CAT] is not currently running on any machine.
6. Ensure that all the points mentioned in the Pre Installation Check are performed. Then tick the checkbox and click the ‘Next’ button.
7. The Installation progress is shown.
8. If the database backup has not been restored prior to the upgrade, the following error message will be displayed and the Installation will terminate. If the database backup is completed correctly, then the installation will continue to the next step
10. If there are any Upgrade issues, the following error message will be displayed and the Installation will terminate. In this scenario, go back to the previous file level backup. If there are no upgrade issues, the installation will continue to the next step.
11. The Medtech Services will now be started. Once the installation is complete, the following message will be displayed:
12. Click ‘OK’ to close the installation.
13. 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 Post Installation Checklist (Pages 10-11)
have been reviewed and completed prior to the practice using the Medtech32
If any errors are encountered while installing Version 22.6 Build 5223, a rollback to the previous version is required using the complete file level backup of the MT32 directory (see Prerequisites point 4). Please contact Medtech Support for assistance and include screenshots.
2.
If the installation complete message is not displayed (as shown in point 13 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 4). 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 4). Please contact Medtech Support for assistance with the following details:
4. Please reboot the server after installation if prompted.
5. Check that the update has been run on all laptops that are used for Briefcasing and has completed without errors.
6.
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 [22.6.0.5223]
7.
If any of the following utilities/services were shut down or stopped prior to the Version 22.6 Build 5223 upgrade, please ensure that they are restarted: Medtech32 Scheduler Windows Scheduler NIR Directory Monitoring Utility Medtech Generic Directory Monitor Utility GP2GP Services Medtech Services
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 upgrade was successful. If the upgrade 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 upgrade has not been succesfully performed.
Please follow the steps below to correct the issue: - If you have not already rebooted the server (Step 4), then please
reboot and try logging into Medtech32 again - If you still get the warning message, re-run the upgrade - Post re-running the upgrade, if you still get the warning message,
roll back (Step 3) and contact Medtech Support for assistance
10. Check the current Medtech32 installed version [HelpAbout Medtech32]. After the upgrade has been run, this should read Version 22.6 Build 5223.
11. Ensure that all staff can successfully log into Medtech32 without error.
12.
Ensure that any errors encountered during the post-installation process have been captured and have been provided to Medtech Support for assistance.
13. Remove the complete file level backup of the MT32 directory once the practice is satisfied there are no issues post-upgrade.
To confirm MedtechPrinter has registered successfully on the workstation:
Select a patient who is an account holder and has a valid email Select Module ► Accounts ► New Invoice or press F9 to open the New Invoice screen Generate an invoice and click the ‘Send Invoice’ button
Positive outcome
The email will open in the default email client on the workstation. The invoice in PDF format will
be attached in the draft email.
Negative outcome
If MedtechPrinter is not registered on the workstation, then the following error message will be
displayed, highlighting the requirement to login to Medtech32 as Run as Administrator.
For email integration, an email client must be associated with MAPI on the workstation.
The most common email client is Microsoft Outlook.
NOTE: 1. According to current software requirements specifications (SRS), Office 2003, 2007,
2010, 2013 and 2016* are supported.
[*Office 2016 is supported from Medtech32 Version 22.4 and above]
2. According to current SRS, the 32-bit edition of Office has to be installed on 64-bit Operating System.
The following error message will be displayed when Medtech32 is not able to communicate with the default email client installed on the machine.
Potential reasons for email integration failure on workstation Operating System may not be supported by Medtech32 (please refer to the SRS) Windows security upgrades block MAPI integration Default email client may have more than one profile.
Potential workaround Close the email client and try sending email from an Out Box document in Medtech32.
Please note that the email will be queued and only sent once the email client is opened.
For further information or any other queries, please contact Medtech Support via: