ΒΆ 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
----------------------------------------