RESOURCE AND PATIENT MANAGEMENT SYSTEM
Laboratory
(LR)
TCP/IP Lab Interface Setup Manual
Version 1.2 January 2010
Reformatted April 2015
Office of Information Technology Division of Information Technology Laboratory (LR) Version 1.2
Document Changes
Page Change Made Justification Date 3 Changed the Caché $I value from The listed $I value was for 4/17/03 56 to //./nul
TCP/IP Lab Interface Setup Manual Document Changes January 2010 ii Laboratory (LR) Version 1.2
Table of Contents
1.0 Package Requirements ...... 1 2.0 Caché Setup ...... 2 2.1 Initial installation of the Lab Interface...... 2 2.1.1 RPMS Setup ...... 2 2.1.2 Instrument Manager Setup ...... 6 2.2 Switching from Serial to TCP Connection ...... 10 2.2.1 RPMS Setup ...... 10 2.2.2 Instrument Manager Setup ...... 13 3.0 Troubleshooting ...... 17 3.1 TCP/IP Differences ...... 17 3.2 Troubleshooting Matrix ...... 19 3.3 Troubleshooting Notes ...... 20 3.3.1 IMDEVIO errors ...... 20 3.3.2 HL TASK Errors (Caché) ...... 21 Acronym List ...... 23 Contact Information ...... 24
TCP/IP Lab Interface Setup Manual Table of Contents January 2010 iii Laboratory (LR) Version 1.2
Preface
This manual provides site managers and Area ISCs the necessary information to convert existing Lab interface connections (LAT and serial) to TCP/IP (Transmission Control Protocol/Internet Protocol). This manual also covers how to establish a TCP/IP connection to a new laboratory interface.
This manual is only pertinent to sites that have installed the Consolidated Fileman22/Kernel Distribution including Kernel Toolkit and Health Level 7 (HL7).
TCP/IP Lab Interface Setup Manual Preface January 2010 iv Laboratory (LR) Version 1.2
1.0 Package Requirements • HL*1.6*1004, which is contained in the Consolidated Fileman22/Kernel Distribution including Kernel Toolkit and HL7. • Instrument Manager running on NT or DOS with a Network Card installed.
TCP/IP Lab Interface Setup Manual Package Requirements January 2010 1 Laboratory (LR) Version 1.2
2.0 Caché Setup
2.1 Initial installation of the Lab Interface For the initial installation of the Instrument Manager, the user can complete the RPMS setup any time before the interface is installed.
Note: Before setting up the TCP/IP connection, the user’s IT department must assign a static IP (Internet Protocol) address for the Instrument Manager.
2.1.1 RPMS Setup 1. Open the Caché Configuration Manager from the Caché Cube and click the Advanced tab. Expand the Device option and double-click the Devices folder (see Figure 2-1).
Figure 2-1: RPMS setup (Caché) Step 1
2. Expand the |TRM| device option. Make sure that Type is set to TRM and the Sub-Type is set to C-Cache Terminal. If the user does not have a |TRM| connection, create one (see Figure 2-2).
TCP/IP Lab Interface Setup Manual Caché Setup January 2010 2 Laboratory (LR) Version 1.2
Figure 2-2: RPMS setup (Caché) Step 2
3. To set up a NULL DEVICE in the DEVICE file (3.5):
a. Set Name to NULL DEVICE. b. Set $I to //./nul
a. Set Name to LABDATA-IM-TCP. b. Set $I to |TCP|
TCP/IP Lab Interface Setup Manual Caché Setup January 2010 3 Laboratory (LR) Version 1.2
c. Set Ask Device to NO. d. Set Ask Parameters to NO. e. Set Volume Set (CPU) to DHC
o. Set Subtype to P-OTHER. p. Set Open Timeout to 10. q. Set Type to NETWORK CHANNEL. Note: The OPEN Parameters value contains the static IP and port of the DI box, assigned by the network. It must not conflict with another port being used (e.g., the port used by the BGU listener for Patient Chart).
5. To set up File #770:
a. Set Name to Lab Interface. Note: Name must be unique
b. Set DHCP Station Number to 202811 i. Set Lower Level Protocol Timeout to 3. j. Set Related File 771 Entry to LAB INTERFACE. k. Set HL7 Processing ID to PRODUCTION. l. Set Start/Stop Transmission Log to STOP LOG. Note: The HL7 DEVICE must match the LABDATA-IM-TCP device name and the DHCP STATION NUMBER must match the Institution file Station Number field. The recommended Lower Level Protocol Timeout value is 3. 6. To set up File #771 for LAB INTERFACE (this file is populated in Version 5.2 of the Laboratory package): a. Set Name to Lab Interface. b. Set Active/Inactive to ACTIVE. c. Set Facility Name to Instrument Manager. d. Set Country Code to USA. e. Set HL7 Field Separator: to |. 7. To set up File #771 for LA AUTO INST: a. Set Name to LA AUTO INST. b. Set Active/Inactive to ACTIVE. c. Set FACILITY NAME to TCP/IP Lab Interface Setup Manual Caché Setup January 2010 5 Laboratory (LR) Version 1.2 q. Set HL7 Segment to PID. r. Set FIELDS Used In This Segment to 3,5,7,8,19. s. Set HL7 Segment to ORC. t. Set FIELDS Used In This Segment to 1,2,3. u. Set HL7 Segment to NTE. v. Set FIELDS Used In This Segment to 3. Note: There is a mistake in the released version of the LA AUTO INST file. In the HL7 Segment OBR there is a period (.) between 14 and 22. This must be changed to a comma (,). 8. To set up File #62.48: a. Set Configuration to UNIVERSAL INTERFACE. b. Set Protocol to HEALTH LEVEL SEVEN. c. Set Status to ACTIVE. d. Set Log Errors to ON. e. Set HL7 non-DHCP application to Lab Interface. f. Set Process In to D QUE^LA7UIIN. g. Set Process Download to D EN^LA7UID1. h. Set Remote System ID to Lab InterfaceInstrument Manager LA AUTO INST202810. Set in this file, the HL7 non-DHCP application name is the name given to file 770. This name must be unique. In this file, the REMOTE SYSTEM ID consists of four parts: the first part is the 770 file name, the second is the Facility name found in the 771 file LAB INTERFACE, the third part is one of the 771 file names, and the fourth part is the facility number found in file #4. The Load/Worklist file #68.2 and the Autoinstrument file #62.4 must be set up prior to turning on the interface. The procedure on setting up these files can be found on pages 106-114 and pages 247-261 of the DHCP Planning and Implementation Guide http://www.ihs.gov/lab/files/lr__52o1.pdf. 2.1.2 Instrument Manager Setup In this section, the user will create a connection and configure it for the Caché TCP (Transmission Control Protocol) connection in the Instrument Manager. TCP/IP Lab Interface Setup Manual Caché Setup January 2010 6 Laboratory (LR) Version 1.2 1. To create a new configuration, click the Configuration option on the menu bar and select the Configuration Editor option. Note: These setup instructions apply to the NT version of the Instrument Manager only. If the user is running the DOS version of the Instrument Manager, open the Configuration manager in whatever way is appropriate for his/her IM version. 2. On the Configuration Editor page, click Add (see Figure 2-3). Figure 2-3: Creating the CACHE configuration (Steps 2 through 9) 3. Type CACHE in the Configuration Name and Configuration Description fields. 4. Select the VA Hybrid HL7 LIS option from the Driver Type field and click Driver Properties. The VA Hybrid HL7 LIS Configuration dialog displays. 5. Type Lab Interface in the 770 Name field. TCP/IP Lab Interface Setup Manual Caché Setup January 2010 7 Laboratory (LR) Version 1.2 Note: If the user’s settings in File #770 are different than the values established here in steps 5-8, use the values from his/her #770 file. 6. Type Instrument Manager in the 770 Non-DHCP Facility Name field. 7. Type LA AUTO INST in the 770 DHCP Application field. 8. Type the station number from File #770 in the 770 DHCP Station Number field. 9. Click Close on the VA Hybrid HL7 LIS Configuration dialog and Close on the Configuration Properties dialog. If prompted to save changes, do so. 10. To create a connection to the new configuration, click the Configuration option on the menu bar and then click the Connection Assignment option. Click Add and a blank Connection Properties dialog will display (see Figure 2-4). Figure 2-4: Creating the CACHETCP connection (Steps 10 through 14) 11. Type CACHE in the Connection Name and Configuration Name fields. 12. Select the appropriate TCP/IP port number in the Device field and click Device Parameters. 13. In the TCP/IP Port Configuration dialog, type the appropriate port number in the TCP/IP Port Number field and click Close. The TCP/IP Port Number value should match that used in the Device File Open Parameter field. Leave the TCP/IP Address field blank. 14. When finished, click Close. TCP/IP Lab Interface Setup Manual Caché Setup January 2010 8 Laboratory (LR) Version 1.2 15. Open each lab instrument’s connection properties. In the Destination Line(s) field, select the new connection (CACHE). 16. Click the Management menu option and select the Manage Debug Connection option. The Manage Debugging for a Connection dialog will display (see Figure 2-5). Figure 2-5: Setting up connection debugging for Cache (Steps 16 through 19) 17. In the Connection field, select cache from the drop down menu. 18. Click Start. 19. Click Watch. 20. Reopen the Status Display window and turn on all connections, excluding any old connections (e.g., RPMS). Note: Only the Purge, Qmgr, Cache, and instrument connections should be activated at this point. All old connections should be turned off. 21. Start the background job (HLZTCP) through the Reinitiate Background Job option (HL7 V 1.5). TCP/IP Lab Interface Setup Manual Caché Setup January 2010 9 Laboratory (LR) Version 1.2 22. Test the connection with all of the instruments, watching the debugger screens. Make sure to test sending orders AND entering results for tests. If there is a problem with any of the connections, see Section 3.0 for troubleshooting information. 23. Once all lab instruments have been successfully tested, stop all debug connections and close any debug dialogs still open. 2.2 Switching from Serial to TCP Connection For sites already using the Instrument Manager, the user will need to complete the RPMS and Instrument Manager setup all at one time. Completing just the RPMS portion of the setup will prevent the current interface from working. Do not begin the RPMS setup until the user has all of the hardware/software required to complete the DI setup as well. Note: Before the user can set up the TCP/IP connection, the user’s IT department must assign a static IP address for the Instrument Manager. 2.2.1 RPMS Setup 1. Have the user’s site manager kill the HLLP job. 2. Open the Caché Configuration Manager from the Caché Cube and click the Advanced tab. Expand the Device option and double-click the Devices folder (see Figure 2-6). TCP/IP Lab Interface Setup Manual Caché Setup January 2010 10 Laboratory (LR) Version 1.2 Figure 2-6: RPMS setup (Caché) Step 2 3. Expand the |TRM| device option. Make sure that the Type is set to TRM and the Sub-Type is set to C-Cache Terminal. If the user does not have a |TRM| connection, one must be created (see Figure 2-7). Figure 2-7: RPMS setup (Caché) Step 3 TCP/IP Lab Interface Setup Manual Caché Setup January 2010 11 Laboratory (LR) Version 1.2 4. Verify that a NULL DEVICE exists in the DEVICE file. 5. To set up a new LABDATA-IM-TCP device in the DEVICE file: a. Set Name to LABDATA-IM-TCP. b. Set $I to |TCP| 6. To set up File #770: a. Set Name to Lab interface. b. Set DHCP Station Number to 202811 TCP/IP Lab Interface Setup Manual Caché Setup January 2010 12 Laboratory (LR) Version 1.2 h. Set DHCP Application to LA AUTO INST. i. Set Lower Level Protocol Timeout to 3. j. Set Related File 771 Entry to LAB INTERFACE. k. Set HL7 Processing ID to PRODUCTION. l. Set Start/Stop Transmission Log to STOP LOG. Note that the HL7 DEVICE must match the LABDATA-IM-TCP device name and the DHCP STATION NUMBER must match the DI interface setting. The recommended Lower Level Protocol Timeout value is 3. 2.2.2 Instrument Manager Setup In this section, the user will create a connection and configure it for the Caché TCP connection in the Instrument Manager. 1. Make sure that all connections are turned off. To do this, open the Instrument Manager Status Display, select the checkbox to the left of any connections with an ON status, and click Stop Selected Connections. 2. To create a new configuration, click the Configuration option on the menu bar and select the Configuration Editor option. Note: These setup instructions apply to the NT version of the Instrument Manager only. If the user is running the DOS version of the Instrument Manager, open the Configuration manager in whatever way is appropriate for his/her IM version. 3. On the Configuration Editor page, click Add (see Figure 2-8). TCP/IP Lab Interface Setup Manual Caché Setup January 2010 13 Laboratory (LR) Version 1.2 Figure 2-8: Creating the CACHE configuration (Steps 3 through 10) 4. Type CACHE in the Configuration Name and Configuration Description fields. 5. Select the VA Hybrid HL7 LIS option in the Driver Type field and click Driver Properties. The VA Hybrid HL7 LIS Configuration dialog will display. 6. Type Lab Interface in the 770 Name field. Note: If the user’s settings in File #770 are different than the values established here in steps 6-9, use the values from his/her #770 file. 7. Type Instrument Manager in the 770 Non-DHCP Facility Name field. 8. Type LA AUTO INST in the 770 DHCP Application field. 9. Type the station number in File #770 in the 770 DHCP Station Number field. 10. Click Close on the VA Hybrid HL7 LIS Configuration dialog and click Close on the Configuration Properties dialog. If prompted to save changes, do so. TCP/IP Lab Interface Setup Manual Caché Setup January 2010 14 Laboratory (LR) Version 1.2 11. To create a connection to the new configuration, click the Configuration option on the menu bar and then click the Connection Assignment option. Click Add and a blank Connection Properties dialog will display (see Figure 2-9). Figure 2-9: Creating the CACHE connection (Steps 11 through 15) 12. Type CACHE in the Connection Name and Configuration Name fields. 13. Select the appropriate TCP/IP port number in the Device field and click Device Parameters. 14. In the TCP/IP Port Configuration dialog, type the appropriate port number in the TCP/IP Port Number field and click Close. The TCP/IP Port Number value should match that used in the Device File $I field. Leave the TCP/IP Address field blank. 15. When finished, click Close. 16. Open each lab instrument’s connection properties. In the Destination Line(s) field, select the new connection (CACHE) and click to uncheck the old connection (e.g., RPMS). 17. Click the Management menu option and select the Manage Debug Connection option. The Manage Debugging for a Connection dialog will display (see Figure 2-10). TCP/IP Lab Interface Setup Manual Caché Setup January 2010 15 Laboratory (LR) Version 1.2 Figure 2-10: Setting up connection debugging for CACHE (Steps 17 through 20) 18. In the Connection field, select cache. 19. Click Start. 20. Click Watch. 21. Reopen the Status Display window and turn on all connections, excluding any old connections (e.g., RPMS). Only the Purge, Qmgr, Cache, and instrument connections should be activated at this point. All old connections should be turned off. 22. Start the background job (HLZTCP) through the Reinitiate Background Job option (HL7 V 1.5). 23. Test the connection with all of the instruments, watching the debugger screen. Make sure to test sending orders and entering tests results. If there is a problem with any connections, see Section 3.0 for troubleshooting information. Once the lab instruments have been successfully tested, stop all debug connections and close any open debug dialogs. TCP/IP Lab Interface Setup Manual Caché Setup January 2010 16 Laboratory (LR) Version 1.2 3.0 Troubleshooting 3.1 TCP/IP Differences To verify that a connection has been opened by the Instrument Manager, go to the DOS prompt and type the following command: C:\> netstat –a Active Connections Proto Local Address Foreign Address State TCP labdi:telnet 0.0.0.0:0 LISTENING TCP labdi:69 0.0.0.0:0 LISTENING TCP labdi:135 0.0.0.0:0 LISTENING TCP labdi:135 0.0.0.0:0 LISTENING TCP labdi:1028 0.0.0.0:0 LISTENING TCP labdi:1030 0.0.0.0:0 LISTENING TCP labdi:1489 0.0.0.0:0 LISTENING TCP labdi:2701 0.0.0.0:0 LISTENING TCP labdi:2702 0.0.0.0:0 LISTENING TCP labdi:4001 0.0.0.0:0 LISTENING TCP labdi:5700 0.0.0.0:0 LISTENING TCP labdi:6001 0.0.0.0:0 LISTENING TCP labdi:6006 0.0.0.0:0 LISTENING TCP labdi:38037 0.0.0.0:0 LISTENING TCP labdi:1027 0.0.0.0:0 LISTENING TCP labdi:1027 localhost:1028 ESTABLISHED TCP labdi:1028 localhost:1027 ESTABLISHED Figure 3-1: Example of listing for computer and ports upon which the IM resides In the second column, the name of the computer that the Instrument Manager resides on is followed by a colon. The number after the colon indicates the open port. The last column has the state (or status) of that port. The port number that the user chose in the “connection assignment” on the Instrument Manager should be listed in the second column. If it is not listed, the IM is NOT listening and there is a problem. One problem may be that the TCP Port that the user chose is malfunctioning or is in use by some other setting. Another way to check to see if the DI server is available on the network at all is to ping it. At the DOS/Unix prompt type: C:\>ping ip_address where ip_address is the DI address If the result is something like: Reply from 161.223.90.221: bytes=32 time<10ms TTL=128 Then the DI machine is on the network, however this does NOT mean that the DI port selected is available. TCP/IP Lab Interface Setup Manual Troubleshooting January 2010 17 Laboratory (LR) Version 1.2 If the result is something like the following: Timeout Then the port is not on the network or the port is blocked. Another way to determine whether the DI is available on the network is to use the telnet command: • At the “DOS/Unix prompt” type C:\>telnet ip_address port#. If the following displays, the connection to the port is blocked. C:\>telnet 161.223.90.221 5700 Connecting To 161.223.90.221...Could not open a connection to host on port 5700 : Connect failed If the connection is not blocked the screen will clear and the cursor will jump to the top of the screen. All DI machines have Caché running and the user should be able connect via telnet to cache as follows: telnet ip_address Cache for Windows NT (Intel) 2.1.9-F.14 (Build 040+CFL157+CFL182+RJW191) Tue Dec 28 1999 11:06:13 EST Node LABDI Port: NPA03TFRAZIERW2/1833 Username: • If the prompt in the example does not display, then port 23 for Caché is blocked. • If the user cannot connect using any of the commands, the network has been improperly configured or configured in such a way that the port is blocked. The network settings will have to be reconfigured. • If for any reason the connection used for RPMS on the Instrument Manager is turned off (e.g., the PC is shut down), communication between the Instrument Manager and the RPMS server will be lost, and there is no automatic re- connection. • To find out if the connection has been lost, open a Manage a Debugging Connection on the Instrument Manager and watch the connection for the RPMS. If ^imdevio displays in any of the messages then there is a problem with the connection. The problem may be that the connection on the Instrument Manager was stopped, or the IP address for the Instrument Manager is not correct. TCP/IP Lab Interface Setup Manual Troubleshooting January 2010 18 Laboratory (LR) Version 1.2 • If the connection on the Instrument Manager was stopped or the PC was shut down, kill the HLZTCP background job on the RPMS system and then re-start using the HL7 v 1.5 option re-initiate background job. The RPMS connection on the Instrument Manager must be ON. • If the IP address assigned to the Instrument Manager is not a static address, the connection will be lost if the Instrument Manager PC is shut off and restarted, since the IP address may be assigned on start up. 3.2 Troubleshooting Matrix Figure 3-2: Troubleshooting matrix TCP/IP Lab Interface Setup Manual Troubleshooting January 2010 19 Laboratory (LR) Version 1.2 3.3 Troubleshooting Notes 3.3.1 IMDEVIO errors Any errors similar to WRITE> +171^imdevio indicate an error in the device setup, the port settings, the IM connection, or the Caché configuration for the TCP device. The IMDEVIO error can also indicate that the Caché (RPMS) system is down. For MSM systems, check the system status and see if the HLZTCP routine is running. MSM - System Job Status 02-OCT-02 12:09 PM Max Partitions: 49 Current in Use: 7 JOB UCI/VOL ROUTINE P-SIZE STATUS #-COMMANDS DEVICES NUM NAME NAME CURR/MAX TOTAL/INCR OWNED ------1 * * * M S M * * * 2 PRD,DHC %SS 3.7/100 Running 34865/513 65pc(tfrazierw2k~12 4 MGR,DHC %ZTM 6.8/100 Hang 7967998/7967998 5 PRD,DHC %GSEL 3.2/100 TermI-64 124913/34 64pc(tfrazierw2k~11 9 PRD,DHC BGUTCPL 0.2/100 TCP_IO 306/306 56c 13 PRD,DHC HLZTCP 10.0/100 TCP_IO 355100/355100 56c 17 PRD,DHC MSMSHELL 2.7/100 TermI-1 17921/260 1pc Figure 3-3: Sample IMDEVIO error If the user runs a system status and sees a WaitQ3a status for the HLZTCP routine, the Instrument Manager PC might be turned off, the IP address for the Instrument Manager might be incorrect, or the RPMS connection might be turned off in the Instrument Manager. MSM - System Job Status 02-OCT-02 12:18 PM Max Partitions: 49 Current in Use: 8 JOB UCI/VOL ROUTINE P-SIZE STATUS #-COMMANDS DEVICES NUM NAME NAME CURR/MAX TOTAL/INCR OWNED ------1 * * * M S M * * * 2 PRD,DHC %SS 3.8/100 Running 39789/2500 65pc(tfrazierw2k~12 4 MGR,DHC %ZTM 6.8/100 Hang 8022768/8022768 5 PRD,DHC %GSEL 3.2/100 TermI-64 124913/34 64pc(tfrazierw2k~11 9 PRD,DHC BGUTCPL 0.2/100 TCP_IO 306/306 56c 13 PRD,DHC HLZTCP 10.1/100 WaitQ3a 393440839/393440839 56c 17 PRD,DHC MSMSHELL 2.7/100 TermI-1 17921/260 1pc 18 PRD,DHC %ZTMS1 4.3/100 Hang 16138/16138 p - Principal Device c - Current Device Total Figure 3-4: Sample WaitQ3a error TCP/IP Lab Interface Setup Manual Troubleshooting January 2010 20 Laboratory (LR) Version 1.2 3.3.2 HL TASK Errors (Caché) When the IM connection is turned off and the HL TASK is started via the HL MAIN MENU (i.e. option 2, Initiate Background Task [HL TASK]), the task will continue to be rescheduled in TaskMan until the IM connection is turned back on. If using the List task option in TaskMan, the user will see that the Scheduled for Today time will keep changing. If the user looks at the node ^%ZTSK(task number,.1) “rescheduled for busy device” displays. List Tasks Option All of one user's tasks. One user's future tasks. Every task. List of tasks. Unsuccessful tasks. Select Type Of Listing: l List of tasks. Enter list to display: 421455 All tasks within the list 421455... 421455: ^HLLP, HL7 Message Processor for Lab Interface. Device LABDATA-IM-TCP. LABPRD,LAB. From Today at 9:46, By you. Scheduled for Today at 10:06 There is 1 task in that list. D ^%G Global ^%ZTSK(421455,.1 ^%ZTSK(421455,.1)=1^59087,36113^rescheduled for busy device^0^^^^^^ Figure 3-5: Sample HL Task Errors in Caché Either one of these indicators will tell the user the Caché TCP connection on the Instrument Manager is not available. As soon as the Caché TCP connection is available, the task list will appear as it does in Figure 3-6. All tasks within the list 421455... 421455: ^HLLP, HL7 Message Processor for Lab Interface. Device LABDATA-IM-TCP. LABPRD,LAB. From Today at 9:46, By you. Started running Today at 10:16. Job #: 1868 Figure 3-6: Sample HL Task Errors in Caché, screen 2 The user will also see the HLZTCP routine running when he/she views the system status. LABPRD>D ^%SS Cache System Status: 10:17 am 10 Oct 2002 Process Devices KB Namespace Routine CPU,Glob Pri UIC Location 524 %SYS 0,0 0 0,0 CONTROL TCP/IP Lab Interface Setup Manual Troubleshooting January 2010 21 Laboratory (LR) Version 1.2 552 %SYS 27063,36038 0 0,0 WRTDMN 564 %SYS 0,0 0 0,0 GARCOL 572 %SYS 7,6 0 0,0 JRNDMN 580 %SYS 0,0 0 0,0 EXPDMN 1476* |TRM|:|1476 122 LABPRD %GPARSE 427813,62943 0 0,0 924 |TCP|4001 60 %SYS LMFSERV 470922,999 1 0,0 1936 |TCP|1972 57 %SYS %cmtP0 3538,32 0 0,0 1380 //./nul 70 LABPRD %ZTMS1 62590,15652 0 0,0 1868 |TCP|5700 73 LABPRD HLZTCP 18665,4574 -1 0,0 1792* |TRM|:|1792 123 LABPRD %SS 100014612,5026588 0 0,0 1224 //./nul 51 LABPRD %ZTMS1 4874,1189 0 0,0 1732 //./nul 59 LABPRD %ZTMS1 43952,10711 0 0,0 Figure 3-7: Screenshot of HLZTCP routine running Keep in mind there may be, at most, a five-minute delay between the time the Caché TCP connection on the Instrument Manager (DI) becomes available and the time HLZTCP begins running. If the HLZTCP is running and the Caché TCP connection on the Instrument Manager (IM) is stopped, the task will reschedule itself until the Caché connection is available again. TCP/IP Lab Interface Setup Manual Troubleshooting January 2010 22 Laboratory (LR) Version 1.2 Acronym List Acronym Meaning HL7 Health Level 7 IHS Indian Health Service IP Internet Protocol RPMS Resource and Patient Management System TCP Transmission Control Protocol TCP/IP Transmission Control Protocol/Internet Protocol TCP/IP Lab Interface Setup Manual Acronym List January 2010 23 Laboratory (LR) Version 1.2 Contact Information If you have any questions or comments regarding this distribution, please contact the OIT Help Desk (IHS). Phone: (888) 830-7280 (toll free) Web: http://www.ihs.gov/helpdesk/ Email: [email protected] TCP/IP Lab Interface Setup Manual Contact Information January 2010 24