HRP module now supports ADT Error Report log

Data from the ADT Error Log Report can be added alongside Ol Log and/or PL log data in any existing OL Monitor installation.  Or ADT error log data only can be displayed.  The error log contains a lot of duplicate messages, these are eliminated.  You can apply filters, sorts, and coloring to the ADT error log data to make seeing significant errors easy. Like the OL and PL log, the data is updated continuously so you will see errors as soon as they happen.
Somebody’s job is about to get a whole lot easier!

Getting started with the HRP ADT log:

First you need to enable the HRP option under the HRP tab, then setup your options.
It is not possible at this time to pull both the ‘Orders not Processed’ and ‘ADT Error Report log’ reports at the same time.

Next you need to make sure the ADT Error log fields are selected on the misc tab.

<– Available fields as they appear in options.

*IF THIS is the first time you have enabled HRP, you may need to click OK then go back into the options so that the HRP fields will be enabled.

These are the available fields for ADT you can display:
Priority
Coll Date (For this I use Admit or Discharge date if it is present.  Otherwise it defaults to the current day, 00:00)
Coll Time (same as Coll Date but it will always be 00:00)
Rec Date – From Date column on report
Rec Time – From Time column on report
Dept – On the one sample ADT log this was either ‘LAB’ or CHNG
Location – from the LOC column
HID  – this will be the Patient Number from report.
Episode type
Episode ID
Test – This is the MSG #- ‘1002’ (just the number portion)
Order Phys: 1st phy
Cpy Phys: 2nd phy
Comments: The entire message line

Field map:

 

Duplicate messages on the ADT log are automatically filtered out.

You may want to turn OFF your filters to see all the data from the ADT log.

After that cross fingers and give it a spin!

Email archive

If you are new to this list, you may not have gotten these previous emails:
1. Website announcement
2. Jokes 2
3. You know your instrument is a piece of junk when…
4. Macro tutorial online, minor OL Monitor updates
5. Ol Monitor/DragInfo program updates & new feature poll
6. On OL Monitor ‘not working’ with 6.4.
7. OL Monitor Budget n Bugfixes
8. Testers needed for pending log module
9. Pending log module ready
10. Windows 7, HRP, and new field.
11. 2 new Ol Monitor-related programs available, more Windows 7 info, and HRP beta.
12. Ol Monitor HRP ready, CPL labs added, and some new features.

Installing OL Monitor on Windows 7

The installation process should be virtually the same as with Windows XP.  But here is some extended info about Windows 7 installing and help for any potential issues:

1. Download OL Monitor or run install from cd*(Only use CD if it is a recent version, 1.78 or higher).  (Registered users email me for link to download if you need it)
-You should be logged on as an admin user of the pc to install programs.  (Windows 7 will prompt you for admin credentials if you are not)
-You should not need to run the installer in compatibility mode for it to work. (In fact, if you run the installer in compatibility mode it may try to use the wrong folder locations.)
-Make sure Smarterm is installed first.
-When you install Smarterm you should select to use a common location for all users:

2. Run Ol Monitor.  Remember you DO NOT need to set OL Monitor to run in ‘compatibility mode’, just run it:

3. After a few seconds you will be prompted to setup a login password:

4. Click Yes and it will bring up the options.  The login, password, ip address, and other options are the same as with XP and covered in other install instructions on the Download page.  The first video on that page goes through installing.

5. With regards to Windows 7 there are 2 areas of note under the Advanced tab, you shouldn’t have to change anything here:

-The ‘Logfiles path’ has changed from what it was in XP.  It used to be the Smarterm Sessions folder but in Windows 7 all folder locations have been centralized to C:\users\Public\Documents\OlMonitor
Using the Public folder ensures all users and the Smarterm program will be able to access the settings and files in the folder.
-Operating System: You should not have to mess with this setting.  Normally OL Monitor should automatically detect Windows 7 and you will see that button selected.  If you override and set it to Windows XP it will attempt to use the XP folder locations, which are largely inaccessible in Windows 7.

6. If you have your login, password, ip address, device loc, and access code set then you can go ahead and click OK in the options and allow Smarterm to start and attempt to pull a log from Sunquest.
-One site reported that OL Monitor had a problem launching Smarterm.  I have not experienced this myself and don’t have much info.  If OL Monitor seems to freeze after attempting Smarterm launch get in touch with me.
-IT folks:
If you are installing this for a lab and you do not have the login and access code etc, if you can at least set the IP address for the Sunquest server you can go ahead and verify that Ol Monitor can launch Smarterm and let the lab worry about setting the password and stuff.
Alternatively, if you want to keep OL Monitor from trying to launch Smarterm you can enable ‘test mode’ under the Misc tab of options.  Careful!  If you leave test mode on it can be very confusing for the next person trying to figure out why Smarterm won’t start!
-You may have to click Action-Start to get Smarterm to launch the first time (it will eventually launch on it’s own but the wait can be tedious)

-You may see a messagebar message about Smarterm sessions folder not matching up, just ignore it:

7. If Smarterm launches ok and pulls a log then you are all set!  Take a break.
-If you need to restore your old settings from XP see this post.
-95{fd72016040d8cd0556234298fa216115d17f974a3f3ed976037886290d762d66} of the time if there are problems pulling the log, messages about the Smarterm server, and getting old or no patient/log data, it is due to having the wrong password, login, or ip address setting.
-If you have any problems or need help feel free to contact me.

Migrating Ol Monitor from XP to Windows 7

This post is more for people who already have OL Monitor running on Windows XP and want to move it over to Windows 7.  If you are installing Ol Monitor to Windows 7 from scratch nothing here applies.

This post explains all things in detail and assumes you have forgotten everything so it’s pretty long, you may want to print it out first.

So you have been running OL Monitor on XP for years and years, and have invested a fair amount of time getting colors, filters, sorting, and various other tweaks set just right.  But now IT insists that you need to switch to Windows 7.  This tutorial will walk you through the process of backing up your settings, restoring them to Windows 7, and then dealing with any compatibility issues that may arise.

1. Your settings, where are they?

First thing to check is where your settings are stored right now, there are 3 possible locations.  To find out which one from Ol Monitor click options and take note of where the checkmark is:
  <— Here we see that the settings are stored in the INI file.

IF your settings are stored in Local pc , this location is NOT available under Windows 7.
IF your settings are stored in one of the other locations you can skip to the next step but make a note of which location is currently selected.

2. Saving your settings to a different location because you had them saved in ‘Local pc’/’This pc only’:

Settings location topic in help manual: http://www.olmonitor.com/ManualM/window_3_6.htm
The ‘Local pc’ location is not available under Windows 7. So you can save yourself some trouble later by changing the location now to either USER or INI file.  You cannot change the location by simply clicking one of the locations from this menu, you need to go into the Options window.  Click Options-Options and it will bring you to the Misc tab:
 * ‘This pc only’ means ‘Local pc’
So you can see the ‘This pc only’ button is selected.  To write your settings to another location you need only to select one of the other locations.  When you select the other location you will see this warning:

This is ok, we want to write our settings to the new location.  There is one possible exception:
A few labs have 2 groups of settings saved to 2 of the locations, say one for night shift and one for days, night shift in INI file and day shift in USER.  If you have this setup you will need to go in and export your settings for each location separately.
But most likely you do not have alternate settings setup in one of the other locations.
Click OK and you will see the selected button has changed to the other location.  But your settings have not been saved there just yet!  You have to click OK or Apply, when you do, your settings will be saved to the new location.
IF you see any error messages after clicking OK or Apply there may have been some problem writing the settings to the new location.  Try selecting another location and see if you get any errors.
Now make a note of which location you saved your settings to.



3. Backing up your current settings:

There are 2 ways of backing up setting available to you, I suggest you use both to be safe.

Backup method 1: Go into options to the Misc tab:

Just click the ‘Export options’ button.  A browse window will come up so you can choose where to store the backup file.

Note:  You need to type in the appropriate file extension for the backup type.  If exporting from USER use the .reg extension. So your filename will be something like:  OlMonitor_Backup.reg
If exporting from INI file put ‘.ini’ as the file extension.
Store the file on a USB drive or a network drive since IT will be re-imaging the pc or giving you a brand new one.  It just needs to be somewhere that you will be able to access from the new pc later.

Backup method 2a: Quick backup
Go into options and under the Misc tab, click the blue “Quick Backup” link:
<– All settings will be saved in a dated folder on the pc desktop.

Backup method 2b: Using Ol Monitor Settings Manager
If you have Ol Monitor version 1.80 or above:  Simply click the blue link that says ‘Settings Manager’:

If you do not have OL Monitor version 1.80 or higher you will need to install the Settings Manager.  Do this now and when done run the Settings Manager program and return to this tutorial.  How to install Settings Manager.

Having Settings Manager loaded:

1. Click the cube-magnifying-glass icon.  All your current settings will be loaded up, each location in a different tab:

2. Click the Green-arrow-folder icon.  A new tab named ‘Backup to folder’ appears.  Select this tab:

To the left is the list of drives on the system, you can browse to your USB drive or network folder.

Here you can see I previously made a folder on the USB drive named OL Monitor.  You can also just select the root of the drive.
You will see that the date (1_17_2013) is used as a folder name, you can choose your own folder name but the name cannot be blank.

3. Click the ‘Backup’ button and all settings locations will be saved to separate backup files:
Unlike what happens when you click the ‘Export options’ button in OL Monitor, all locations get backed up not just the current one.

So now you have your precious settings backed up and after the upgrade to Windows 7 you can move on to:

Part II: Restoring your backed up settings to your new Windows 7 installation:

1. If you have not already, install OL Monitor on Windows 7.

2. After you install OL Monitor you will have the default settings.  As you can see the ‘Logfiles path’ is in the public users’ folder:

3. Ol Monitor will tell you that you need to input the login and password etc, but we don’t need to worry about that we saved them in our backup!

4. Restoring from your backup:

1. Close OL Monitor for now.
2. Locate your backup(s) you made on the USB key or network location using Windows Explorer.

3. This is why it was important to take a note of which settings location was selected back when you were backing up.

4. 2 ways to restore settings:  You can double-click on .reg files, for .ini files you cannot.

Restoring from a .reg file in Windows 7

As of this writing (Ol Monitor version 1.81), the Import function does not work for .reg files in Windows 7 (likely due to some security feature).
If you try to import a .reg file from within Ol Monitor you will get this error:

 “Error in: ExportImportReg #:75 Path/File access error OlMonitor 750/750”

The workaround is to simply double-click the backup file in Windows Explorer.

Restoring from an .ini file in Windows 7

Before you start it up here’s a quick tip:
Hold down the shift key as you Right-click on the file, in the drop down you will see ‘copy as path’:

Ok now start OL Monitor and go to the Options window.  Make sure that you have selected ‘Ini File’ first.  Click on ‘Import Options’:

In the dialog that pops up either browse for the file or paste its path into the File Name field:

*If you are only seeing .reg files and not .ini files in this dialog, close it out, make sure Ini file is selected as the backup location, click OK and close and restart Ol Monitor.

Getting the settings imported was the hard part, but there are still some things to check.
In our backup file, the file locations were set like this:

Here’s where we can get into trouble, we imported the settings and they wrote over the default file paths.  Let’s pull up the advanced tab and see if OL Monitor was smart enough to figure this out:

Well it got the logfiles path right, but macro folder and Smarterm exe are wrong.
The exe on my machine should be: C:\Program Files\Esker\SmarTerm\stoffice.exe
The macro folder should have been: C:\Users\Eric\Documents\SmarTerm\Macros

Don’t worry about the stoffice.exe location: OL Monitor will automatically search and locate the exe file on the first run.  You will see this:

Ol Monitor quickly locates the exe file and fixes the path.

What about the Macro Folder path? Actually, OL Monitor doesn’t really need to know this, it’s to avoid a rare error that comes up when someone has deleted their default macro file. Ol Monitor already has an alternate method of clearing this error, so it’s really, really not important.
If you want to correct it you can paste in the path for the Smarterm\Macros folder.  At this writing (ol monitor v1.81), the find button finds the wrong folder, and the browse option is a little confusing.

That’s it! You’re done.  If you run into any issues be sure and contact me so I can update this post for others.

Windows 7 Compatibility

With version 1.77 Ol Monitor is now Windows 7 compatible. To be compatible with Windows 7, the locations of various files (ini file, captured logfiles, error log, and session file) had to be changed. Since changing these locations on existing XP installations might cause problems, Ol Monitor detects the OS and works the same as always if it’s on XP. So you can continue to update your current XP installations without worry. Regarding running OL Monitor in Windows 7: *(In Windows 7 you can enable ‘compatibility mode’ option that tricks a program into thinking it is running in XP. So in Ol Monitor there is an option to override the OS detection in advanced settings. It only seemed fair to give the program an option to know the truth. Actually this was left in for troubleshooting purposes only, I do not recommend overriding OS detection otherwise.)

Running Ol Monitor in Windows 7:

 

This is redundant, but here is the link to email about Win 7 compatibility: http://us1.campaign-archive1.com/?u=2b1b01defc2a1b7e3212a7744&id=1d0b83e2a2

Ol Monitor Settings Manager

Managing your settings can get a little confusing.  Also, it’s very rare, but sometimes if your settings get corrupted Ol Monitor will not even load. To make things easier I have created a program specifically to manage Ol Monitor settings.
OL Monitor Settings Manager is designed to accomplish the following:

  • Easily locate and load all existing settings
  • Easy 2-click backup of all settings.
  • Load and examine any backed-up settings
  • Transfer settings from one location to the other, or restore settings from a backup

Installing the program is also easier, utilizing ClickOnce deployment.

Install OL Monitor Settings Manager
.

Also, now in OL Monitor versions 1.80 and above, there are 2 new links under the Misc settings tab:

Click on ‘Settings Manager’ to launch OL Monitor Settings Manager.
Clicking on ‘Quick Backup’ will launch OL Monitor Settings Manager with the command line argument ‘backall’.  This instantly backs up all current settings to a folder on the desktop or in my documents with the current date as the folder name.

Finding lost settings / copy settings to new pc:

There are 3 locations where settings can be stored.
-If you are missing settings, you can cycle through these 3 locations looking for your settings.
-If you just need to copy your current settings over to the new pc, you can do that also

First you need to try and locate the settings.
Run OL Monitor and click Options-Options from the drop-down menu.
NO settings found: The settings appear blank like this, with a couple of asterisks in the login fields:

Settings FOUND:  Access code and login are not asterisks (password will always be asterisks):

If you found your settings you can skip the next step:

Cycling through the other locations:
Start Ol Monitor.
Click on options, and look at the ‘Reload with…’ options:
<— The checkmark indicates which location it was using.
Wherever the checkmark is, select one of the other locations.  Ol Monitor will close and you have to restart it.
Look again for your options, if not found, try the last location.

If you found your settings:
You can export them to a file and restore them to the new pc.
Here are instructions on exporting the settings to a reg / ini file:
http://www.olmonitor.com/ManualM/window_3_6.htm

You can then import the reg file to the new pc.

There are extended instuctions on working with the registry manually here:
http://www.olmonitor.com/settings.html
Recommended if you have worked with the registry editor before.

I am working on another program whose purpose is to make managing Ol Monitor settings easier.  It is almost done, if you would like to try it I can provide you with a link to download it, but at this point it is a little rough around the edges.

Is there a way to filter out a package of tests versus individual tests.

Patrick M recently asked me this question and it’s a good one.  The short answer is no, but here are several ways to make filtering easier:

Hi Patrick,

Believe me I wish there was.  The only way to quickly ‘filter’ out a broad group of tests is to use a worksheet.  You can put up to 2 worksheets, separated by a comma, in the Worksheet field:


You can now (as of version 1.78) use the lab department in filters.  So you could include only one or two departments or exclude some:

If there is any consistency in the naming of a group of tests, you can get a little creative and filter them by name.

Say you have a group of tests: GLU1, GLU2, GLU3, BGLUC…

Since they all contain ‘GLU’, you could make a single filter using the ‘CONTAINS’ operator to get rid of them all:

If you don’t want to waste a lot of time typing in filters, you can quickly add a filter by right-clicking on the test on the main display:

It’s easy to create a bunch of filters this way, you end up with a ton of filters in your filter config, but there is no limit so it’s fine.

Finally the alternative is to go into the filter options and manually create one or a few huge filters with all the tests listed.


These all-in-one filters can create a problem later on if you want to remove or change a test that is listed in the middle!  But an easy way around that is to nix the test by typing in something else in the field.  So say later on you don’t want to filter out DAT’s:

 Where ‘DAT’ was, I replaced with ‘NONSENSE’.  Hopefully you don’t have any tests named nonsense so this will have no ill effect, and your DAT’s will start to show up.

Hope that helps.  The manual covers filters in more detail: http://www.olmonitor.com/ManualM/module_5.htm

Sluggish OL Monitor/Optimizing OL Monitor

After helping a site troubleshoot a problem that came up on one of their pc’s, I have a few tips for anyone who might be having similar problems or just wants to optimize their current installation.
Symptoms:
– Ol Monitor refreshes once and then becomes extremely sluggish, freezes, and has to be terminated with Task Manager.
– Multiple Smarterm sessions with “KillMe” in the title bar.
– Clicking on Ol Monitor application and getting “This program is not responding..” message.

Solutions:
-Turn off Error Logging: This option is in the Misc tab under ‘Error Controls’.  On the pc in question, this turned out to be consuming way too much time and causing timeouts and freezing.  If you are having no issues with Ol Monitor you can safely turn off this option anyway.
-Un-Check ‘Test Mode’: This option is also under ‘Error Controls’ and is only used when testing out Ol Monitor.  If you have it enabled during normal use the Smarterm macro will prompt you at every refresh.  If the Smarterm window is hidden or in the background this prompt will hang up the macro.
-Check Smarterm’s shutdown options: Newer versions of Smarterm have various shutdown options:

Note which option you have selected and then try selecting ‘Close the session’ and ‘Exit Smarterm if last session closed’.  Although your server may have a timeout and disconnects Ol Monitor, Smarterm will still not close when a macro is running.  The macro will try to reconnect if the session disconnects.  The other options, ‘Show disconnect options’ in particular, may cause Smarterm to pop up a question box that prevents Ol Monitor from shutting it down.

Finally, note that with version 1.54 of Ol Monitor 2 additional connection checks have been added to sections of the macro.

SSH upgrade effect on OLM monitor, or: The somewhat convoluted process of getting the SSH password to save.

*Note:  The SSH process has changed in newer versions of Smarterm and this post is very outdated.  Please see this post.

Please help.None of our OL_monitors are connecting to Smarterm after a server upgrade.We are no longer using a telnet session in smarterm.We ware using SSH.

Remember you should always backup your settings before installing or updating!
See the “Export options” topic here:

http://www.olmonitor.com/ManualM/window_3_6.htm#id_4
IN ADDITION, I suggest you also save your session file. The file should be located in:

C:\Program Files\OlMonitor VIM\OlMonitor.stw

After backing up your settings be sure to uninstall the previous version. (the installer will ask you if you want to uninstall the earlier version)

The SSH issue:  Basically what the issue is that Smarterm encrypts the SSH password.  Since there is no way for me to reverse-engineer their encryption, we cannot put the password into OL Monitor options.  So you have to do the password saving via Smarterm.  It’s a little tricky because you have to stop the macro before saving the session file within Smarterm.  After you get the SSH password saved into the Smarterm Session file you won’t be prompted for it anymore and Ol Monitor will function normally.

Workaround:
When you start Ol Monitor immediately go to the options screen and change the comm. Method to SSH:

 

Set the Misys server to the SSH server address:

When you press OK the settings will get saved to the session file.

When OlMonitor starts Smarterm, I expect you may first get a message saying ‘Password encryption failed’. This is because I left the password blank.

Since I don’t have an SSH server to test with I’m not sure what other prompts/messages you will get.

If you would make a note of the extra steps you have to do on the first connection, and if on repeat connections of any other prompts that continue to popup.

Also, of course, let me know if the macro fails, gets hung, or for whatever reason doesn’t work.

Smarterm starts, after you have gotten the password setup and checked the box to save it you will need to save the session.

Smarterm will not let you save while a macro is running.

Press the green triangle button to get to the macro control:

or press tools macros:

Click stop macro and then save the session.

Here you can also set the SSH login string.