¶ 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.dllSolution
- 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)
¶ 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 printing an ECG from Office Medic
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:
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
On some systems running Windows 10 version 21H2 (and above) with newer USB 3.2 chipsets (such as the latest HP mini desktop PCs) your QRS Diagnostic Universal ECG device may not work. Upon looking further into the issue, you may see an exclamation mark next to the Universal ECG Bus Controller device in Device Manager. This article can help with this specific issue.
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.
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
{Bad Image}%hs is either not designed to run on Windows or it contains an error. Try reinstalling the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0x
This error is caused by an incompatibility between the older QRS Diagnostic / Vectracor USB drivers and some newer systems. As the QRS Universal ECG device uses an FTDI USB to Serial chipset, we can use another driver to work around the problem. Please follow these steps.
1. In device manager, Right click on the Universal ECG Bus Controller device and click on Uninstall device
2. Tick the Delete the driver software for this device box and click Uninstall
3. Download and extract the latest FTDI VCP drivers for Windows (Desktop) - be sure to pick the correct download based on your system architecture (32-bit or 64-bit, most systems these day are 64-bit)
Link: https://ftdichip.com/drivers/vcp-drivers/
4. Now click on the Scan for hardware changes button in Device Manager - An item named TTL232R will appear under Other devices in the list after a moment
5. Right click on TTL232R then click on Update driver
6. Click on Browse my computer for drivers
7. Click on Let me pick from a list of available drivers on my computer
8. Click on Show All Devices at the top of the list then click on Next
9. Click on Have Disk… then browse to the path where the driver files were extracted in step 3
10. Then choose USB Serial Converter from the Model list then click on Next - then click Yes on the Update Driver Warning window
11. Click on Close - the USB Serial Converter driver will now be installed and the ECG should work as expected
Need Help?
LEMR customers can get help by contacting LEMR Support.