Medtech32 Australia. Version Build Release Notes

Transcription

1 Medtech32 Australia Version Build 4071 Release Notes This Release Notes document contains important information for all Medtech32 users. Please ensure that they are circulated amongst all your staff. We suggest these should be filed safely for future reference. Level 2, 180 Albert Road, South Melbourne, Victoria T F E supportau@medtechglobal.com W

2 Table of Contents Version Build 4071 Release Notes Introduction... 3 Medtech32 Pre-requisites... 4 Medtech32 Server Installation... 7 Resolved Items in this Release...12 MediSecure Script Transmission errors for User Defined Drugs...12 Batching window Inactive and Resubmit Rules...14 Unmatched Provider Results Improved Visibility...17 Scanning Load from File...19 SMS Account Credentials for Multiple Locations...20 SMS Merge Fields for Providers and Location...21 erx Multi-Location Support...22 Norav ECG File Name Format and Import Location Change...23 Error Message while Opening Clinical Ease window...24 Access Violation Error in Patient Verification window...24 Access Violation/Dataset Error in Patient Inbox...25 Prescription Unit Error Message...26 Consultation Screen - Radiology Outbox...27 Enhancements...28 Staff Address field length increased...28 Column Sorting in Patient / Provider Inbox...28 Short Date Format...29 Send Patient Claim (SPC)...30 Activate Send Patient Claims...30 Lodge Patient Claim...30 Cancel Patient Claim...31 Log File for Invoice...32 ManageMyHealth Issue Fixes...34 Login to ManageMyHealth...34 ManageMyHealth Patient Registration...35 Technical Fixes...36 Access Violation Errors...36 Focus issue in New Invoice and Patient Medication...36 Out of Memory Errors...36 Incorrect Field Length for Location...36 EIB Client Error during Auto Logoff...36 Copyright Medtech Healthcare Pty Ltd Page 2

3 INTRODUCTION Medtech32 Version Build 4071 is a Patch Release of Medtech32. This document provides an overview on resolved issues, enhancements and changes to the Medtech32 application to accommodate the Nehta and PCEHR utilities. Please refer to the separate CDA Bridge Release Notes - MT32 V9.1.4 document for further updates and changes to the Healthcare Identifiers (HI) Service and the Personally Controlled Electronic Health Records (PCEHR). IMPORTANT NOTE RE: NEHTA epip PCEHR Requirements In order to be eligible for the NEHTA epip (Practice Incentives Program ehealth Incentive), practices should install Medtech32 Version Build 4071 as soon as possible in order to meet the PCEHR (Personally Controlled Electronic Health Records) requirements. NOTE: Please ONLY run the Upgrade at a time when your site is not required to be up and running in a short amount of time. It is recommended that you run the Upgrade afterhours or on the weekend when you would have adequate time to complete the Upgrade. NOTE: The amount of time required to run the Upgrade is dependent on the specification of your server and the size of ALL databases. IMPORTANT NOTE WARNING: It is HIGHLY recommended to employ ONLY qualified system engineers when performing ANY installation and upgrade. The consequences of ruining a database during upgrade could possibly lead to data corruptions, and as a result data loss and systems downtime. If in doubt, please consult with your qualified IT technician/service provider, or contact one of the Medtech Channel Partners listed on our web site: For further information on this release, or any other queries regarding Medtech32 Version Build 4071, please contact the Medtech Helpdesk on , or supportau@medtechglobal.com. Copyright Medtech Healthcare Pty Ltd Page 3

4 MEDTECH32 PRE-REQUISITES Please review the following pre-requisites and ensure they are met prior to running the Medtech32 Version Build 4071 Update: 1. Ensure the minimum version and build requirements are met. IMPORTANT NOTE Your practice MUST be on Medtech32 VERSION BUILD 3992 to install this Update. If you ARE NOT currently on this exact version and build, please DO NOT continue and contact the Medtech Helpdesk for assistance. Your current Medtech32 version can be checked by logging into Medtech32 and going to Main Menu Help About Medtech32. The following table will assist you in determining your upgrade path requirements if you are not running on the required Medtech32 Version Build Current MT32 Version Upgrade Path to Version Build 4071 Version Build 3794 Step 1: Download and Install Version Build 3835 Step 2: Download and Install Version Build 3893 Step 3: Download and Install Version Build 3915 Step 4: Download and Install Version Build 3992 Step 5: Download and Install Version Build 4071 Version Build 3835 Step 1: Download and Install Version Build 3893 Step 2: Download and Install Version Build 3915 Step 3: Download and Install Version Build 3992 Step 4: Download and Install Version Build 4071 Version Build 3893 Step 1: Download and Install Version Build 3915 Step 2: Download and Install Version Build 3992 Step 3: Download and Install Version Build 4071 Version Build 3915 Step 1: Download and Install Version Build 3992 Step 2: Download and Install Version Build 4071 Version Build 3992 Step 2: Download and Install Version Build Ensure the person(s) who will be performing the upgrade has READ THROUGH this release documentation provided on the Medtech32 website, including the Release Notes and Technical Instructions. 3. Ensure you are always logged onto Windows with ADMINISTRATIVE RIGHTS when performing ANY installation, update or maintenance tasks. Copyright Medtech Healthcare Pty Ltd Page 4

5 4. "User Account Control" (UAC) MUST be DISABLED as a policy across ALL Server and Client computers that are running on Windows Vista or Windows 7 or Windows 2008 or Windows 2008 R2. 5. To avoid unnecessary problems during installation, upgrade, or maintenance, preferably you should ALWAYS log onto Windows in "Console Mode" i.e. not through Remote Desktop Connection, Terminal Services, or Citrix. 6. Ensure ALL Briefcasing Laptops with OUTSTANDING Briefcased data are CHECKED-IN prior to running the update. 7. A SUCCESSFUL Database Maintenance must have been performed on ALL databases. 8. Ensure you have a COMPLETE backup of the MT32 directory and ALL databases located in the MT32\Data directory. 9. The amount of free hard disk space required to perform database backup and maintenance on the Interbase Server should be at least THREE times the size of ALL databases you will be working with. 10. Ensure ALL activities that require access to the databases have been STOPPED: ALL Users have LOGGED OUT of Medtech32 including remote users and idle users in Terminal/Citrix sessions ALL Services have been STOPPED e.g. Medtech Services (for ManageMyHealth SMS and Portal), Medtech Data Transfer Service (for RxSQL Clinical Link), IIS Server (for Medtech Clinical Audit Tool), erx Services, MediSecure Services, etc. ALL Applications have been STOPPED e.g. Medtech CDA Bridge (for NEHTA HI Service, SMD, PCEHR), eclinic SMSC Desktop, Pen Clinical Audit Tool, other Custom/Third-party Applications and Reporting Utilities not supplied by Medtech, etc. ALL Scheduled Tasks have been STOPPED e.g. Message Transfer Utility, Auto Scan from Folder, NPS RADAR Update/Submit, etc. ALL Backup/Maintenance Tasks have been STOPPED e.g. Database File Backup, Interbase Backup/Restore, Interbase Database Sweep, etc. Copyright Medtech Healthcare Pty Ltd Page 5

6 IMPORTANT NOTE FOR BRIEFCASING ALL Briefcasing laptops MUST ALWAYS be on the SAME MEDTECH32 VERSION AND BUILD as the "Main" Medtech32 Server. Otherwise data corruptions, and thus data loss, might occur during check-ins and check-outs. You MUST install this Update separately on EACH Briefcasing laptop by following the same instructions in the "Medtech32 Server Installation" section below. IMPORTANT: Once you have SUCCESSFULLY updated the Briefcasing laptops to the SAME version and build as the Main Medtech32 Server, you MUST then perform a COMPLETE CHECK-OUT on EACH Briefcasing laptop. IMPORTANT NOTE BATCH PROCESSING It is IMPORTANT to ensure that all your Medicare and DVA claims that are to be trasmitted electronically have been completed, closed, and transmitted before you upgrade to this latest Release Version. Failure to do so may result in existing claims having to be reversed, and re-invoiced in the new Medtech32 Version and this may impact on the financial workflow or your Practice. Copyright Medtech Healthcare Pty Ltd Page 6

7 MEDTECH32 SERVER INSTALLATION The Medtech32 Version Build 4071 Update must be run on the Medtech32 Server machine. The following procedures only need to be run ONCE for EACH practice (or once per server if your practice has multiple servers). NOTE: If you are uncertain which computer is the Medtech32 Server, please contact your IT technician or the service provider who has performed the Medtech32 installation and/or upgrade. 1. Please visit our website at 2. Select Region: Australia from the Region dropdown list on the top right corner of the screen. The Australia Home Page will be displayed. 3. Select from the top menu, Medtech Online medtech32 Downloads. The Australia Medtech32 Downloads page will be displayed. Copyright Medtech Healthcare Pty Ltd Page 7

8 4. Here you will find the Version Build 4071 Update. 5. Click on the Link Version Build 4071 Update. 6. If the File Download Security Warning dialogue box appears, select the Run option. 7. If the Open File Security Warning dialogue box appears, select the Run option. 8. The Update will then begin to run. 9. The Welcome screen will be displayed.. Please READ THROUGH the onscreen instructions CAREFULLY and then click on the Next button to continue. Copyright Medtech Healthcare Pty Ltd Page 8

9 10. The Select Installationn Folder screen will be displayed. The path of the current MT32 directory on the Medtech32 Server should be displayed under the Installation Folder section. If Medtech32 is installed on a different path, then click on the Browse button to manually select the correct Installation Folder where Medtech32 is installed. NOTE: If you are uncertain where Medtech32 is installed, please contact your IT technician or service provider who has performed the Medtech32 installation and/or upgrade. Click on the Next button to begin the installation. 11. The installation progress screen will be displayed. Copyright Medtech Healthcare Pty Ltd Page 9

10 12. During the upgrade process, the Database Structure Check utility will appear a few times to upgrade the databases: WARNING: DO NOTclose the Database Structure Checkutility when it is half-way upgrading the databases doing so could damage your databases. WARNING: If you encounter ANY errors during Database Structure Check, DO NOT CONTINUE with the Upgrade. Please LOG the exact errors you have encountered, and contact Medtech Helpdesk for assistance. 13. The erx Entity ID update screen will be displayed to notify that the erx Entity ID is applied for all Locations. Click on the OK button to continue the installation process Note: For further information on this new update screen, please refer to Page 22 of this document - erx Multi-Location Support. Copyright Medtech Healthcare Pty Ltd Page 10

11 14. Once the Medtech32 V9.1.4 upgrade has successfully completed, the following screen will be displayed. 15. Click on the Finish button to exit the Update. IMPORTANT NOTE FOR BRIEFCASING If your Practice is using the Briefcasing option then you MUST Repeat Steps 1-15 above on EACH Briefcasing Laptop to successfully upgrade them to the same Medtech32 Version and Build and the same Interbase Version as the Main Medtech32 Server. IMPORTANT: Once the Medtech32 Versions are identical on the Main Medtech32 Server, and the Briefcasing Laptop, you MUST then perform a COMPLETE CHECK-OUT on EACH one of your Briefcasing Laptops. Copyright Medtech Healthcare Pty Ltd Page 11

12 RESOLVED ITEMS IN THIS RELEASE MediSecure Script Transmission errors for User Defined Drugs In Medtech32 Version 9.1.3, the error message Error with XML request data would occasionally be displayed when transmitting scripts to MediSecure. This issue had been identified as only happening for those prescribed medications that were in the User Defined Drugs list. 1. Find and display an appropriate patient on the palette 2. Go to Module Clinical New Prescription or press hotkey F10 to bring up the New Medication window. 3. Select an appropriate the Ellipsis button. User Defined drugs from the Find Drug window by clicking 4. Enter the respective mandatory fields in the New Medication window and then click on the OK button. Copyright Medtech Healthcare Pty Ltd Page 12

13 5. The Consultation screen will open and display the selected Medication. 6. Click the Print the Selected Prescribed Medications icon to print and transmit the Medication details through to MediSecure. In Medtech32 Version 9.1.3, it would be during this process of sending the Scripts to MediSecure that the error message below would be displayed. This issue has now been resolved in Medtech32 Version and this error will no longer appear when sending Script information through to MediSecure. Copyright Medtech Healthcare Pty Ltd Page 13

14 Batching window Inactive and Resubmit Rules In the earlier versions of Medtech32, it was possible to inactivate any partially/fully paid Batch from within the Batching window (other than write-offs batches). It was also possible for users to resubmit the partially/fully paid (or those with exception services and vouchers) from within the Batching window. The use of the Inactive and Resubmit options when processing partially paid Batches had occasionally resulted in users having to resubmit or delete Batches unnecessarily in order to try to assign payments to the correct vouchers. This resulted in some confusion on which voucher payment belonged to which Batch. In Medtech32 Version 9.1.4, restrictions have been implemented in the Batching screen to ensure that the following Inactive/Resubmit rules are followed, to support the electronic Batch Payments process. For partially or fully paid batches, the Inactive button will be greyed-out/disabled. The Inactive button will be enabled only for unpaid batches Copyright Medtech Healthcare Pty Ltd Page 14

15 The Resubmit button will be enabledonly for those invoices that have an Exception Service Report associated with them. The Resubmit button will not be enabled for a Non-ExceptionService Copyright Medtech Healthcare Pty Ltd Page 15

16 Version Build 4071 Release Notes The Resubmit button will be enabled only when all the line Services in the Voucher have exceptions. The Resubmit button will not be enabled if any of the line Services in a Voucher do exceptions on them (have been paid by Medicare/DVA). not have any exceptions Copyright Medtech Healthcare Pty Pt Ltd Page 16

17 Unmatched Providerr Results Improved Visibility In the earlier versions of Medtech32, when a document/test result from an external provider was transmitted to the Medtech32 application via the Message Transfer utility, matching of the Provider details was done using the following criteria: 1. Provider ID Number 2. Provider Name 3. Patients Default Provider 4. Login Provider If any of the above criteria matched, the document/test result was stored in to the respective Provider s Inbox window; otherwise it was assigned to the Default Provider as specified in the Location Settings (Setup Location Location Settings Codes & Defaults tab). In Medtech32 Version 9.1.4, there is a change to this functionality. This change has been implemented to ensure that all documents/test results are visible to all Providers and not just the Default Provider that has been specified in the Location Settings. Whenever an external document/test result reaches Medtech32 and it is not able to be matched using the above criteria, the Provider Inbox icon will be highlighted in red and the icon will blink as well -. Click on the blinking Provider Inbox icon to view the unmatched external provider documents in the Provider Inbox window. Copyright Medtech Healthcare Pty Ltd Page 17

18 Double-click the document/test result and select the respective provider from the Attention dropdown list. The document/test result will be placed in to the respective Provider s Inbox window. Note: It is also possible to assign the record to the correct Patients file via the Find button. Or From the Filter icon, select the new checkbox option Unmatched Provider Inbox to view the unmatched external provider documents/test results. Copyright Medtech Healthcare Pty Ltd Page 18

19 IMPORTANT NOTE The provider inbox icon will return to its original display (not Red, or Blinking) when all the unmatched documents have been either matched with the respective patient and Provider, or they have been made inactive. Note: A change has also been made in the label/name of the checkbox option - Unmatched records only has now been renamed as Unmatched patient records only. Version Version Scanning Load from File In the previous version of Medtech32 Version 9.1.3, the ability to select multiple image files when using the Load from File option in the Scanning (Module Inbox Scanning) had been restricted to loading a single file only. The multiple file selections functionality had been redirected to the Load from Folder option only. However due to overwhelming requests to reinstate this feature, the Load from File option has reverted to its previous functionality, and users can now select multiple files using the Load from File option from within the Scanning menu. Copyright Medtech Healthcare Pty Ltd Page 19

20 SMS Account Credentials for Multiple Locations In the earlier versions of Medtech32, the SMS Account credentials for each Location had been unique in its Set up for the Practice s Main Location only (Setup Location Location Settings SMS tab). This unique set up also caused a restriction in that the SMSReminders was not able to be used across multiple locations, as an error message would be displayed if another Location SMS Setup had been detected. This restriction has since been removed in this Release Version of Medtech32. Practices can now use the same SMSS Account Credentials across all their different Locations by entering the SMS Setup in to each of the Locations setup. Copyright Medtech Healthcare Pty Ltd Page 20

21 SMS Merge Fields for Providers and Location In the earlier versions of Medtech32 there had been an issue with the Provider and Location Merge fields. These merge fields were displaying the logged in Provider and Location details in the SMS text rather than the selected/specified Provider and Location details from the Appointments/Queue/Recalls window. This issue has now been resolved in Medtech32 Version 9.1.4; the following two new Merge fields have been included in the Merge Symbol window under the filter SMS Keywords (SMS). These new merge fields will display the selected/specified Provider and Location details from within the Appointments/Queue/Recalls windows: Appointment Location (SMS_APP_LOCNAME) to display the selected / specified Location details Appointment Provider (SMS_APP_PROVNAME) to display the selected / specified Provider details (Provider s External Name) Copyright Medtech Healthcare Pty Ltd Page 21

22 erx Multi-Location Support In the earlier versions of Medtech32, there was no option to provide unique erx Entity ID s for staff members for multiple locations. This meant that all Providers sending Prescriptions to the erx Server were using their single erx Entity for multiple locations. Setup Staff Members Provider tab This issue has now been resolved in Medtech32 Version 9.1.4; the erx Entity ID in the Codes and References section has been moved to the Provider Location Details section in the Staff Settings window (Setup Staff Members Provider tab). The list of the Practice s locations are already displayed in the Provider Location Details section, and the new erx EntityID field allows for the entry of the unique erx Entity IDs per location. Copyright Medtech Healthcare Pty Ltd Page 22

23 Norav ECG File Name Format and Import Location Change The Norav ECG device reads and output the patient s results to a PDF and a Native file format. These files are then retrieved from the output folder (path \Program Files\PCECG\Data) by Medtech32. All Medtech32 users are able to access the Native file format results from within Medtech32. However, the more desirable PDF file view was only visible from the workstation that the Norav ECG device is connected to. Recently, in the process of investigating how to make both File Formats available to all users on the network, an issue had been identified in the naming convention of the file names. This issue has now been resolved in Medtech32 Version The Norav ECG output files will now be stored under a new path \Program Files\PCECG\Data\MTRepository and the file name ID will be more detailed. The naming convention of the files will follow the format below to ensure accurate patient record association: <Patient Surname><Patient Internal ID>_<Date>_<Time>.<File Format> Note: To ensure that all users on the network are able to access the Norav ECG files from different workstations, you will need to have upgraded to this Release Build as well as: a. Set up a Shared Drive to save the Norav ECG Output Files to. b. Set the Norav ECG Configuration Output folder to use that shared folder. c. Map the Shared Drive on all workstations that wish to view the Norav ECG files d. Ensure all workstations have the PDF Adobe application installed. Copyright Medtech Healthcare Pty Ltd Page 23

24 Error Message while Opening Clinical Ease window There was an issue in Medtech32 Version 9.1.3, where an error message HASANNOTATION would display when opening the Clinical Ease window. Module Clinical Clinical Ease or press Shift + F3 This issue has now been resolved in this Release and the Clinical Ease window will open without the error above occurring. Access Violation Error in Patient Verification window In Medtech32 Version 9.1.3, an Access Violation error message came up when the Process button in Patient Eligibility window was clicked for a second time during the Patient Eligibility Verification process. This issue has now been resolved in Medtech32 Version The error message will not display as once the Process button has been clicked, the Process button itself will become disabled/greyed out. Copyright Medtech Healthcare Pty Ltd Page 24

25 Access Violation/Dataset Error in Patient Inbox In Medtech32 Version 9.1.3, an Access Violation or Dataset Not in Edit Mode error would display when the Previous or the Next button was clicked from within the View Patient Inbox window. These errors only occurred if the Patient Inbox window was closed at the time. Module Inbox View Patient Inbox This issue has now been resolved in Medtech32 Version It will not be possible to close the Patient Inbox window if the View Patient Inbox screen is open. If an attempt is made to do so, a warning message You cannot close the Patient Inbox while a record is being viewed will be displayed as shown below: Copyright Medtech Healthcare Pty Ltd Page 25

26 Prescription Unit Error Message There was an issue in Medtech32 Version 9.1.3, where an error message would display when the Units field in the New Patient Medication window exceeded 64 characters, as shown below: This issue has now been resolved in Medtech32 Version The Units field in the New Patient Medication window has now been restricted to accept only 64 characters. Copyright Medtech Healthcare Pty Ltd Page 26

27 Consultation Screen - Radiology Outbox Version Build 4071 Release Notes In Medtech32 Version , an error message would display when accessing the Radiology option through the Consultation window, as shown below: This issue has now been resolved in Medtech32 Version The Radiology option will be accessible via the Consultation window, without the error message above being displayed. Copyright Medtech Healthcare Pty Ltd Page 27

28 ENHANCEMENTS Staff Address field length increased Version Build 4071 Release Notes The length of the Address field in the Staff Settings window (Setup Staff Members Staff Details tab) has now been increased from 32 to 64 to accommodate longer address details. Column Sorting in Patient / Provider Inbox The Column Sorting option has been introduced in both the Patient Inbox and Provider Inbox screens (Module Inbox Patient Inbox / Provider Inbox) to help improve the view by allowing the columns to be highlighted and clicked on to any preferred order. Note: The Sort Order shown in the screenshot above is from the Folder column. Copyright Medtech Healthcare Pty Ltd Page 28

29 Short Date Format In the earlier versions of Medtech32, the Date collected and Date requested columns in the Provider Inbox and Patient Inbox appeared cluttered as shown below. In Medtech32 Version 9.1.4, a new checkbox option Short Date Format in Inbox has been introduced in the Location Settings window (Setup Location Location Settings Codes & Defaults tab), to offer users the option to view/hide the time stamp as required. Select this option to hide the time stamp in the Provider and Patient Inbox window. The new view is shown in the screenshot sample below. Copyright Medtech Healthcare Pty Ltd Page 29

30 Send Patient Claim (SPC) In the earlier versions of MT32, the Medicare JAVA component used for the Private claim windows (Lodge Patient Claim and Cancel Patient Claim) was not releasing the RAM memory consumed, which lead to Out of Memory issues. In order to overcome this issue a new functionality Send Patient Claim (SPC) has been introduced in Medtech32 Version This functionality will allow the Lodge Patient Claim and Cancel Patient Claim process to be run via a separate tool from the main Medtech application. This ensures that the process will not impact on the main Medtech32 application with regards to any memory issues. Activate Send Patient Claims Once the MT32 Version installation has been successfully completed, the new SPC tool will be placed in the \MT32\Bin\Tools\ path. A new parameter HASSPC has also been included in the MT32.ini file. By default this parameter will be disabled (i.e. the flag set to N ). The SPC tool will be activated only when this parameter is enabled (i.e. the flag set to Y). Follow the steps below to enable the parameter HASSPC in the MT32.ini file: 1. Go to MT32.ini file path (under the directory \MT32\Bin ) 2. Open the MT32.ini file and enable the parameter HASSPC by setting the value to Y as shown below: [HICONLINE] HASSPC=Y 3. Save and close the MT32.ini file. Lodge Patient Claim When processing an interactive Patient Claim (PCI) i.e. bring up the Lodge Patient Claim window to send the claim, immediately after the patient has been invoiced - the SPC tool will act as the Lodge Patient Claim window to minimize the amount of memory used. Transmit the claim as per the usual process. Follow the below steps to perform Patient Claim Interactive: 1. Find and display an appropriate patient on the palette. 2. Go to Module menu Accounts New Invoice or press F9 to bring up the Invoice window Copyright Medtech Healthcare Pty Ltd Page 30

31 3. Generate an Invoice in a usual way and ensure that the Payment Level is selected as Private and the checkbox option Send Patient Claim is selected. 4. Click on the OK button to save the invoice. The Lodge Patient Claim window will be displayed as a separate window; external to the main application (previously, the Lodge Patient Claim would open within the Medtech32 application). 5. Select the option Send Claim Now to send the claim immediately to Medicare or click Store and Send Later option to store and send the claim later, as per your normal processes. Cancel Patient Claim When cancelling any Patient Claims stored in the Medicare Australia Online Patient Claims window, the SPC tool will also manage the Cancel Patient Claim window to reduce the amount of memory required. The SPC tool will cancel the claim as required. Follow the below steps to Cancel Patient Claim: 1. Find and display an appropriate patient on the palette. 2. Go to Module menu Accounts Patient Claims to bring up the Medicare Australia Online Patient Claims window. Copyright Medtech Healthcare Pty Ltd Page 31

32 3. Select an appropriate claim to cancel and click Patient Claims menu Cancel the Claim to bring up the Cancel Patient Claim window. This window will be displayed as a separate window to further assist in reducing the amount of memory required (previously, the Cancel Patient Claim would open within the Medtech32 application) 4. Select an appropriate reason from Reason for cancelling claim dropdown list and continue the cancellation process as normal. Log File for Invoice A new log file Invoice-<Machine Number>.log has been introduced in Medtech32 Version This log file will be created under the directory \MT32\Bin automatically, when the parameter INVOICEDEBUGLOG has been manually included and enabled in MT32.ini file. Follow the steps below to include and enable the INVOICEDEBUGLOG in the MT32.ini file: 1. Go to MT32.ini file path (under the directory \MT32\Bin ) 2. Open the MT32.ini file and add the following parameter manually under the [LOGGING] section. Enable the parameter INVOICEDEBUGLOG by setting the value to Y as shown below: [LOGGING] INVOICEDEBUGLOG=Y 3. Save and close the MT32.ini file. Copyright Medtech Healthcare Pty Ltd Page 32

33 Version Build 4071 Release Notes 4. The Log file Invoice--<Machine Number>.log will be created under the directory \MT32\Bin. The log file will record all actions in the Invoice window, with the date and time stamp, which will assist in trouble shooting issues in this window. Note: This log file utility can be turned on/off as per the parameter described in Step 2 above. Copyright Medtech Healthcare Pty Pt Ltd Page 33

34 MANAGEMYHEALTH ISSUE FIXES Login to ManageMyHealth There was an issue in Medtech32 Version 9.1.3, where an incorrect webpage Activate Account screenshot sample below - was being displayed when accessing the login process - ManageMyHealth Login to ManageMyHealth. This issue has now been resolved in Medtech32 Version The correct ManageMyHealth Login page as shown in the screenshot below - will be displayed when logging in to the ManageMyHealth Login to ManageMyHealth screen. Copyright Medtech Healthcare Pty Ltd Page 34

35 ManageMyHealth Patient Registration Within Medtech32, a patient s MMH status could be viewed easily from the Patient Palette screen. If the patient had not been Registered in MMH, the MMH icon on the toolbar would be displayed in ORANGE - as shown below: In the earlier version of Medtech32 Version 9.1.3, the incorrect webpage Activate Account (refer to previous Login to MMH section) would display when clicking on the MMH icon (on the toolbar) for unregistered MMH Patients. This issue has now been resolved in Medtech32 Version The correct ManageMyHealth Patient Registration page will display when clicking on the MMH icon on the toolbar, for unregistered MMH Patients. Copyright Medtech Healthcare Pty Ltd Page 35

36 Access Violation Errors TECHNICAL FIXES There was an issue in Medtech32 Version 9.1.3, where the Access Violation error message would display in the following screens: Patient Outbox Staff Task Patient Register Patient Claims This issue has now been resolved in Medtech32 Version 9.1.4; the Access Violation error message will not be displayed in any of the screens specified above. Focus issue in New Invoice and Patient Medication In Medtech32 Version 9.1.3, there had been a Focus issue in both the New Invoice and the Patient Medication screens. This issue has now been resolved in this Release Version. Out of Memory Errors In Medtech32 Version 9.1.3, the Out of Memory error message was displayed in the following screens: Status Screen Find Drug This issue has now been resolved in Medtech32 Version The Out of Memory error message will not be displayed in any of the two screens specified above. Incorrect Field Length for Location In earlier versions of Medtech32, an incorrect field length had been assigned for the Location field. This issue has now been resolved and the Location field length has been corrected. EIB Client Error during Auto Logoff In Medtech32 Version 9.1.3, an EIB Client Error message came up during Auto Logoff. This issue has now been resolved in Medtech32 Version The Auto Logoff will complete without any error messages. For further information on this release, or any other queries regarding Medtech32 Version Build 4071, please contact the Medtech Helpdesk on , or supportau@medtechglobal.com. Copyright Medtech Healthcare Pty Ltd Page 36