2. Dynamic OL Monitor Program streamlines information. Developed by a Medical Technologist working in the lab at HMSW hospital (Site THR). Based on the SmarTerm terminal emulation software already in use in the laboratory. Implemented for a nominal fee, and is easy to maintain.

4. Why an OL Monitor? Problem: Solution: Tests frequently left pending. Pressure to improve turn-around- times. Tedious and redundant method of monitoring pending and overdue tests and collections. Interruption of workflow. Unhappy physicians. Cumbersome method of monitoring stat collections and orders. Delay from order to label print times. Impossible to determine where heaviest workload was in a lab where everyone is a generalist. No way to prioritize tasks. Visual display of all pending tests. Built-in TAT criteria with audible alerts. Requires no paper and no staff intervention to run, interpret, and reconcile manual reports. Allows tech to remain at bench. Monitor in ER for physician use. Immediate visual and audible alerts for new stat orders. Can see order before label prints, allowing quicker response. Visual display allows techs to concentrate work in areas where workload is the greatest. Built in timers.

6. It automatically pulls up the OL Log, analyzes, sorts, and presents the information in a graphical format. Since the data is up to the minute, test age can be calculated in real time. New orders appear dynamically and audibly alerts all staff within seconds. Is used as a supervisory tool to enhance staffing. Calculations are performed referencing standard TATs and audible and visual alerts notify staff when exceeded. Dual-purpose options allow TAT standards to be set up for phlebotomy as well as technical staff, all condensed and organized in one place. Allows staff in remote locations to monitor outstanding collections and orders in real time. TAT standards, audible alerts, refresh times, and other options can be customized without changing the hard coding. What does the OL Monitor do?

7. How does it work? Through the of Visual Basic MACROS !

8. Heres how... Smarterm uses a proprietary version of Visual Basic for macros. This allows the macros to call upon functions that normally are not available in competing emulation software. Upon activation, the macro carries out the following steps: 1. Searches for.ini file and loads options, or uses defaults if not found. 2. Script calls up a group worksheet consisting of single worksheets containing the tests you wish to monitor for a specific HID (for MULHOS sites). 3. As the report prints back to terminal screen, it is captured to a file. The file is then scanned line by line. The current time and date are read in first, and then each field on each line of the OL report is read in. Duplicates are eliminated automatically. 4. TAT standards are checked as the time in process is calculated, outliers if found, are indexed for audible and visual cues. 5. The list is then sorted by patient, priority, and finally status. The result is a more organized, understandable, and prioritized workload. 6. Finally the information is displayed, and any audible cues played if necessary. 7. The process repeats itself at a user-defined interval.

9. Whats needed? Minimum P-75 PC with sound card, speakers, SmarTerm v8.0a or higher, and access to SunQuest. Video splitter, VGA cables, and enough monitors to place where needed. Generic SunQuest login access code and tech code with OL (^LUCP0) and CPW (^O2^Q03A) security. Group Worksheet. Copy of the macro on hard-drive or network.

11. Ultimately, everybody strives to be...