|
Written by Dale Kern
|
|
Friday, 16 April 2010 23:27 |
 |
PrintPad
|
| Print to screen utility |
| Using too much paper? |
|
|
Many computer systems offer printed reports for the user's convenience. Many times these reports are looked at briefly, then thrown out. In the clinical laboratory, pending test reports might be an example of such a report. PrintPad is a utility that allows you to capture these printed reports to a computer screen. In addition to capturing the report, PrintPad can filter out unwanted reports alert your users that a new report is available.
In the clinical laboratory, such an application could be set up to capture reports to a high-profile PC located centrally in the laboratory. Overdue or pending tests would be visible to the laboratory staff.
Download PrintPad for Windows
|
|
| Printing to the PC |
|
| This utility accepts data using the TCP/IP protocol. To have a remote system print to your PC, the PC must have a known static IP address. Using the Port toolbar button, select the IP port that will be used for the data capture. One the IP address and port are known, set up a printer driver on the remote system to send to that particular address.
The following is an example of a printer using the sunquest LIS system, notice the indication of the IP address and port of the PC capturing the printed data:

|
|
| Using PrintPad with Sunquest overdue logs. |
|
| Sunquest offers methods for printing overdue logs through the use of the ^LODM and ^DRODZ program references. You are allowed to specify which tests to monitor and at what interval they become "overdue". This program prints a list of new overdue tests a 5 minute intervals. A summary is printed every 20 minutes. We found these program useful and informative, yet it wasted a lot of paper (A report prints even if there are no overdue tests). Printing to a high-visibility computer in this case would be more efficient and save paper.
The Sunquest program references
You will most likely want to display the 5 minutes reports (new overdue tests), or the 20 minute reports (all overdue tests), but not both. To receive only 20 minute reports, set up a report filter rejecting reports that do not contain "Results delayed at". To receive only 5 minutes reports, set up a report filter that will reject reports not containing "New Entries Printed at".
- Set the Alert trigger to only alarm when the report does not contain delays in processing. Reports with no overdue tests display "No delays in processing" or "No abnormal delays in processing".
- You will most likely want to display the 5 minutes reports (new overdue tests), or the 20 minute reports (all overdue tests), but not both. To recieve only 20 minute reports, set up a report filter rejecting reports that do not contain "Results delayed at". To recieve only 5 minutes reports, set up a report filter that will reject reports not containing "New Entries Printed at".
- Set the Alert trigger to only alarm when the report does not contain delays in processing. Reports with no overdue tests display "No delays in processing" or "No abnormal delays in processing".
^LODM contains the properties that define an "overdue" test

^DRODZ starts and stops the overdue log process

Using the alert and filter properties, an audio alert can play only when overdue tests are reported. Try the following:
- You will most likely want to display the 5 minutes reports (new overdue tests), or the 20 minute reports (all overdue tests), but not both. To recieve only 20 minute reports, set up a report filter rejecting reports that do not contain "Results delayed at". To recieve only 5 minutes reports, set up a report filter that will reject reports not containing "New Entries Printed at".
- Set the Alert trigger to only alarm when the report does not contain delays in processing. Reports with no overdue tests display "No delays in processing" or "No abnormal delays in processing".
|
|
| © 1998-2010 IronStone Technology |
|
|
Last Updated on Friday, 30 April 2010 20:26 |