Best Practice Orchid edition - BP to Office Medic Proxy compatibilty issue

If you are running BP Orchid edition and get the following error when trying to launch an ECG or Spirometry test in Office Medic via Best Practice, it means that the old BP to Office Medic Proxy application is no longer able to communicate with the new BPDevice components released in the new BP Orchid. The great news is our LEMR solution is fully compatible with BP Orchid edition and Office Medic! To get your Office Medic ECG and Spirometer integration up and running again with ongoing support, contact us! QRS Universal ECG devices (USB and Serial), QRS Orbit Spirometer (USB) and Vectracor Universal SmartECG (USB) devices are fully supported in LEMR.

Need Help?
LEMR customers can get help by contacting LEMR Support.

Error details:



************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'BPDevice, Version=1.0.5.0, Culture=neutral, PublicKeyToken=093d1fdeef495a0c' or one of its dependencies. The system cannot find the file specified.
File name: 'BPDevice, Version=1.0.5.0, Culture=neutral, PublicKeyToken=093d1fdeef495a0c'
  at OfficeMedicTest.MainWindow.Init()
  at OfficeMedicTest.MainWindow.MainWindow_Load(Object sender, EventArgs e)
  at System.Windows.Forms.Form.OnLoad(EventArgs e)
  at System.Windows.Forms.Form.OnCreateControl()
  at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
  at System.Windows.Forms.Control.CreateControl()
  at System.Windows.Forms.Control.WmShowWindow(Message& m)
  at System.Windows.Forms.Control.WndProc(Message& m)
  at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
  at System.Windows.Forms.Form.WmShowWindow(Message& m)
  at System.Windows.Forms.Form.WndProc(Message& m)
  at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
  at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
  at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

************** Loaded Assemblies **************
mscorlib
   Assembly Version: 4.0.0.0
   Win32 Version: 4.8.4515.0 built by: NET48REL1LAST_C
   CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
BPtoOMproxy
   Assembly Version: 1.0.2.26
   Win32 Version: 1.0.2.26
   CodeBase: file:///C:/Program%20Files%20(x86)/QRS%20Diagnostic/Best%20Practice%20Proxy/BPtoOMproxy.exe
----------------------------------------

splwow64.exe ColorAdapterClientUpdateDisplayGamma error when printing a PDF (save to file) in Office Medic version 5.8.1 upwards

Symptom

Error appears when producing a PDF that stated the following:

<Title>splwow64.exe - Entry Point Not Found</Title>
The procedure entry point
ColorAdapterClientUpdateDisplayGamma could not be
located in the dynamic link library
C:\WINDOWS\system32\spool\DRIVERS\x64\3\mscms.dll

Solution

Open the folder
C:\WINDOWS\system32\spool\DRIVERS\x64\3
Rename mscms.dll to mscms_orig.dll

PDF printing will now work in Office Medic. Note that there may be other printers installed on the system that rely on this file; please test other printers to ensure printing works as expected.

Increase size of buttons in Office Medic application on small screens with high resolution

By default, the size of the buttons in Office Medic do not change when DPI settings are adjusted in Windows. To force these DPI changes, we must use the Application Compatibility options available in Windows.

To do this:

Find the Office Medic icon on the desktop
Right-click on the icon and choose Properties
Click on the Compatibility tab
If you need to adjust the setting for all users on this computer, click on the Change settings for all users button; if you don't have permission to do this or you only need this setting for the current Windows user, proceed to the next step
Click on the Change high DPI settings button
Tick both boxes on the form, change the first dropdown to I open this program and the second dropdown to System (Enhanced)
Click OK button for the two open property pages (three if the settings were changed or all users)

Compatibility tab

DPI settings property page

Office Medic ECG capture performance issue on slower CPUs

On Intel Atom CPUs and systems with slower processors, if an ECG test is run with the Leads view set to 3x4 View, the timer may appear to lag at times and Office Medic may crash after a minute or two. If you see the timer misbehaving, it could be this issue or it could be an issue with the latency setting for the FTDI adaptor used with the ECG.

To work around this specific performance issue:

Open Office Medic from the icon on the desktop
Go to the Options menu, then to ECG…
Click on the Acquisition Settings tab, then change the Leads dropdown to 12 Leads - this will adjust the default view when capturing an ECG
Click OK and close Office Medic

Error when producing a PDF from Office Medic - Error 1012: You have an old version of Ghostscript installed

When producing a PDF in newer versions of Office Medic, an error may appear as follows:

Window title: PDF Writer - bioPDF

An error occurred.
Error 1012: You have an old version of Ghostscript installed. Ghostscript version 8.50 or newer is required. Please install a newer version.
Source: GUI
Internal hint: Run converter to create PDF file
Developers: You can hide this message with the "suppreserrors" setting.

This means that some old GhostScript files are hanging around in the Office Medic directory. To fix this:

1. Download the latest GhostScript version install files for both Windows x86 and Windows x64 from https://www.ghostscript.com/releases/gsdnld.html

2. Install both packages on the computer, installing to the default directory; keep note of the install directory for each package

3. Go to the installation directory for the x64 package then open the folder named bin
e.g. C:\Program Files\gs\gs10.06.0\bin

4. Copy the files from the bin folder directly into the bioPDF installation directory
e.g. Copy from C:\Program Files\gs\gs10.06.0\bin
To: C:\Program Files\bioPDF\PDF Writer\gs\

5. Repeat process for the files in the profiles directory, copying all from the folder to the bioPDF folder.
e.g. Copy from C:\Program Files\gs\gs10.06.0\profiles
To: C:\Program Files\bioPDF\PDF Writer\gs\

6. Go to the installation directory for the x86 package then open the folder named bin
e.g. C:\Program Files (x86)\gs\gs10.06.0\bin

7. Copy the files from the x86 bin folder directly into the bioPDF installation directory
e.g. Copy from C:\Program Files (x86)\gs\gs10.06.0\bin
To: C:\Program Files\bioPDF\PDF Writer\gs\

This issue should now be resolved! Try producing another PDF.

Error when printing an ECG from Office Medic - Path cannot be the empty string or all whitespace

When choosing Save and print or when clicking on the Print icon on the toolbar in Office Medic on Windows 10 and 11 systems, an error may appear as follows:

Error -2147024809: Path cannot be the empty string or all whitespace, Source: mscorlib, Internal hint: Copy output to destination

Office Medic expects a default printer to be set, which doesn't occur when Windows is managing the default printer automatically.

To fix the issue in Windows 10:

1. Open the Printers & Scanners app

2. Scroll down and untick Let Windows manage my default printer

3. Find your preferred printer in the list above, click on it then click Manage

4. Click Set as default then close the window - you should be able to print in Office Medic now

Universal ECG Bus Controller driver incompatibilty

Please see this article for more information on driver issues: https://wiki.lemr.com/en/support/technical-support/qrs-universal-ecg-bus-controller-driver-incompatibility

Note: this article only applies to the QRS Diagnostic ECG devices with original manufacturers' USB trunk leads and does not apply to ECG devices originally using a serial port-based trunk lead (with or without a seperate connected USB to Serial adaptor cable), or any ECG devices converted to USB by any non-original USB trunk lead.

How to turn Muscle and Power filters on in Office Medic

To turn the Muscle and Power filters on in Office Medic to improve readability of captured ECGs for every new test performed, please follow the steps below:

Open Office Medic (from the icon on the desktop).
Click on the Options menu, then click ECG.
Click on the Acquisition Settings tab.
Then tick the boxes next to the Muscle and Power filters (50Hz) and click ok.

For any ECG tests where the ECG was captured without the Muscle and Power filters set to on by default:

Open the ECG through Office Medic (from the icon on the desktop).
When the ECG Review window appears, press the Muscle Filter On/Off and/or the 50Hz Power Filter On/Off buttons as indicated below.

Note: When the setting is activated, the buttons should look pressed down like this:

How to use Average Complexes feature in Office Medic

The Average Complexes feature affects the view of each ECG tracing dramatically, though it does allow for users to view automatic measurement data.

To make the ECG trace for each lead look “normal” when reviewing an ECG in the default 12 Lead mode, click the button on the toolbar as indicated in the screenshot below:

Your ECG tracings will then look something like this instead:

However, if you leave the Average Complexes setting on, then click the Measurements button and click the Zoom button, you get some automatic measurements. You can then select which lead you would like it to show the readings for (as per the screenshot below):

Error during an Office Medic Test: Could not find file Diagnostic Test Data\Spiro\Session.txt

The following error may appear when you have completed a Spirometry test in Office Medic when integrated with an EMR or LEMR:

Error: Error during an Office Medic Test: Could not find file Diagnostic Test Data\Spiro\Session.txt

Firstly, please check if the correct path is set for the File Directory path setting; more information about this here: https://wiki.lemr.com/en/support/technical-support/om-cannot-open-command-file

The next step is to check the values for the following Registry keys:

HKEY_CURRENT_USER\Software\Vectracor\Office_Medic

and

HKEY_CURRENT_USER\Software\Vectracor_OEM\Office_Medic

In both registry paths above, ensure the DWORD values are set as follows:

ExportOptions is set to 1
FlowVolumeExport is set to 1
Metric is set to 1

Then try the testing again; this should resolve the issue.

Installation of bioPDF Printer Fails with error 0x00000002

Printers
Operation could not be completed (error 0x00000002). The system cannot find the file specified.

If this error comes up during the setup of the bioPDF PDF printer, either during Office Medic installation or when running the BioPDF setup manually, try these steps below.

Using the Print Management MMC tool in Windows, delete both of the BioPDF drivers from the list in the Drivers node:

If you aren't allowed to remove these bioPDF drivers as a printer is using them, be sure to remove the printer named PDF Writer - bioPDF from the Printers node in the same tool.

Then you will need to add a printer as follows:

Remove the Microsoft PS Class Driver item from the Drivers node (check if warning about printer using the driver; if so, remove related printer from printers node then try again - the printer you remove may need to be reinstalled; always be careful when deleting anything; backups are your friend). Keep in mind that it is ok if the package cannot be removed in the process; the driver is the main thing.

An example of the note that will appear on removal is as follows:
Driver Microsoft PS Class Driver was removed.
Driver Microsoft XPS Class Driver was removed.
Failed to remove package prnms005.inf.
Add a local printer
Use existing port: FILE:
Install a new driver: Microsoft PS Class Driver (Windows 10/11)
Finish.

Then try reinstalling the bioPDF printer using the setup provided with Office Medic on the ISO or in the Office Medic install folder. This should work now without error.

Print Management (printmanagement.msc) is not on Windows Home editions. It is a Pro / Enterprise / Education / Pro for Workstations feature. If you are running a Home edition, you will need to remove the driver using Print Server properties instead.

To install the Print Management console if it is missing on a Windows 10/11 Pro operating system, the process is as follows:

Settings

Settings → Apps → Optional features
(Windows 11: System → Optional features)

Add a feature / View features

Search Print Management

Install Print Management (sometimes listed as Print Management Console)

ECG not detected warning

If your QRS/Vectracor ECG device is not being detected properly on your computer, you may see one or more of the following warning messages:

ECG not found message from Office Medic v5.x - Cannot find ECG cable. Ensure the cable is securely connected to the computer and try again. [Retry] [Cancel]

ECG not found message from Office Medic v6.x - Cannot find ECG cable. Ensure the cable is securely connected to the computer and try again. [OK]

ECG not found message when using latest LEMR release - ECG Not Detected - Office Medic ECG device was not detected.

The first thing to check is if the device is properly plugged in to your computer. This is such a common cause, so it is worth having a quick look to confirm!

If it looks like the device is correctly plugged in, the next thing is to check if the drivers for the ECG device are appearing correctly in the Windows Device Manager. If the drivers have loaded correctly, it should look like this:

How the device drivers should look for the QRS/Vectracor Universal ECG if loaded properly

If your device is not appearing in the device manager like the screenshot above, please double-check if the ECG is connected properly to the USB port and check if the USB port is damaged. If there are any USB extension leads, please remove it and connect the ECG directly to your computer's USB port. You can also try it in a different USB port on your computer (perhaps connect to to an available USB port on the back of your computer if you are using a desktop PC to rule out possible issues with front USB ports).

If there is an obvious issue with the driver in the device manager, the following article may help too: https://wiki.lemr.com/en/support/technical-support/qrs-universal-ecg-bus-controller-driver-incompatibility

If the drivers are loaded correctly in the device manager, and Office Medic is still not detecting the ECG, it is possible that the USB trunk cable of the ECG may have a partially broken wire inside it. An illustration of this can be found below and is relatively common with old or heavily used devices.

Illustration of the ECG's USB plug and part of the USB trunk cable that leads back to the ECG device - one of the internal wires may have a partial breakage from years of use (and the cable bending one way then the other) - these breaks won't be visible from the outside of the cable, though can result in intermittent connection issues at first, over time getting worse.

Note: The reason the device drivers will still show as loaded in the case of a partial wire breakage in the ECG's USB trunk lead is that the ECG's USB plug (the part that plugs into the USB port) is the part that contains the USB to serial converter components that the driver loads for. The drivers will still load if this end part is connected, even if the ECG's USB trunk lead is completely severed.

If any of the wires in the ECG's USB trunk cable are broken, the device is typically repairable; the Australian repairer for QRS/Vectracor devices here (contact for a repair quote):
https://u-techmedical.com.au/contact-us/

For LEMR customers, if you would like assistance in troubleshooting the issue (or if the above information doesn't help), please contact LEMR Support. There are ways to confirm if there is a broken wire that can be covered in a support session.

Need Help?
LEMR customers can get help by contacting LEMR Support.