THE BASICS OF L.I.S.

COMMUNICATIONS

For the Advia 120

Written by: Jim Maccalous

Presented by: Ray Gagne and Jim Maccalous

L.I.S (Laboratory Information System)

Most Common: Mysis (Sunquest) Meditech Cerner Soft Lab Soft Home grown (Built by the Lab)

About the 120 Interface:

Two types of communication protocol:
Host Spec 79: Is the Advias bi-directional communication protocol used to communicate with a host computer. 99% of Advias that are interfaced use this type of protocol. Information is both sent to and received from the host computer. (Note: There is both a serial and a network version of host spec 79) H*Emulation: Mimics the unidirectional interface used in the Technicon H systems. Information/results are only sent to the host. No communication from the host is received by the Advia. (This will not be discussed in this presentation.)

About the 120 Interface:

Can be run in 3 modes: Download: Workorders are received into the data managers pending file when the host computer has control of the communication line. It does not require prompting from the 120. When a SID # is entered, either by manual entry or from reading the barcode label, the Advia searches the data managers pending file for a matching workorder. Query: After a SID # is entered, either by manual entry or from reading the barcode label, the 120 searches the pending file within the data manager. If it can not find a workorder, it will ask (Query) the host computer for a workorder. Full Query: The Advia does not search within its own database and will always query the host directly for the workorder.

Customer Parameters

Customize System Setup Tools Modify Customer Parameters Option 32 (Allows you to choose mode of operation)

MESSAGE TYPE Initialization Token Transfer

CODE I

ORIGIN Host Host or Advia

PURPOSE Starts Communication by informing Advia that the host is ready to receive information. Allows the receiving device (either host or Advia) to take control and transmit data. If the receiving device does not have anything to send, it sends back a Token transfer ("S" message) to give the other device control. This continues until either the Host or Advia has something to send. When they have something to send, they will keep control until they are finished, and then send a "S" message to relinquish control to the other device.

Workorder

Host

This is sent by host and contains information such as patient demographics and tests to be run on a particular sample ID number (SID #). Informs the host that the workorder is either valid or contained an error. Contains the results for a sample identified by the SID#. Informs the Advia if result message sent was accepted. Requests a workorder from the Host based on the SID#. (Used in query mode only.) Informs the Advia that there is no workorder for the SID# that was Queried. (Used in query mode only.)

Workorder Validation Result Result Validation Query No Order

Advia

R Z Q N

Advia Host Advia Host

Where do you start?

Check the Data Managers sample control panel to see if the LIS light is red or green. A green light will tell you that the host has established a connection with the Advia.

What if the LIS light is red?

The LIS must start communication with the
Advia by sending an initialization message (I). Double click on the letters LIS to open the window which will allow you to see if messages are being sent or received

What if the LIS light is red?

Once the LIS sends an initialization message,
the LIS light and box should turn green. You should see the received characters and messages increase, indicating that information is being exchanged.

What if the LIS light is red?

A red LIS light may also indicate that there is a problem with the physical connection between the Host and the Advia.
Check that Host connection on Com port 1 is connected properly. Check that the Port Configuration is set up properly Check that cabling is set up properly.

What if the LIS light is green?

Sometimes the LIS light is green and the customer states that the Advia still will not transmit the results.
Check Tools View, Routine Parameters. Check Data manager, Control Panel Capture Spy File and analyze

What if the LIS light is green?

Sometimes the LIS light is green and the customer states that the Advia still will not transmit the results. Switch to the Data Manager, Sample Control Panel. Scan and Run a specimen in a manual mode. Where do the results go? (incomplete, unmatched, c complete, or complete)

What if the LIS light is green?

If the customer is running in Query mode, the pending file should increase by one after the SID # is scanned or entered. You should then be able to find the workorder in the pending file. If the customer is running in Download mode, they should be able to find the workorder in the Pending file.

What if the LIS light is green?

What if the LIS light is green?

If after specimen is run, Incomplete increases by one.

Check Data Manager, Review and Edit, Parameters

What if the LIS light is green?

Data Manager, Review Edit, Parameter

What if the LIS light is green?

If after specimen is run, Incomplete and Unmatched increase by one.

Workorder is not being received by the Data Manager.

What if the LIS light is green?

If after specimen is run, Complete increases by one.

Check Tools View, Routine Parameters

What if the LIS light is green?

Under Host Transmission, check which results they want sent to the host.

What if the LIS light is green?

If after specimen is run, C. Complete increases by one.

Successful transfer has not occurred. Turn on spy file and analyze for problems.

What if the LIS light is green?

Turning on the Spy File (Delete old file first if not needed)

Customize Tools View Spy View File, Delete Choose file you want to delete and click OK

What if the LIS light is green?

Turning on the Spy File

Customize Tools Modify Customer Parameters Option 36 (Trace spy Activation on LIS communication) Remember to turn back off after you have captured data.

What if the LIS light is green?

Viewing the Spy File

Customize Tools view or modify Spy view Open, Host.spy, O.K

The Spy File

B04SHOSX Communication HOST: (08/19/04 06:29:00)(COM1 9600 N 8 1) Indicated date and time spy file was turned on. Indicates that message is coming in to Advia and Date and Time IN (08/19/04 06:30:58) -> 0I ^ <OUT (08/19/04 06:30:58) ->0<Indicates that the message is going out of the Advia and Date and Time sent This is the Message Toggle (MT) It should be the same as the MT in the last received message. Initialization Message. Note that MT is always 0 for initialization message. The I is the code for the initialization message.

IN (08/19/04 06:31:01) -> 1S e <-

Indicates that the message is coming in to Advia and Date and Time received MT/Token Transfer Message. The MT has increased by one character from the last out MT. The S is the code for a token transfer. The host is now giving control of the line to the Advia. If the Advia has any result messages, it can now send them. If it does not, It will MT the host and then send a MT and S message.

The Spy File

IN (08/19/04 06:31:01) -> 1S e <OUT (08/19/04 06:31:02) ->1<OUT (08/19/04 -> 2S f <IN (08/19/04 06:31:08) ->2<Indicates that message is coming in to Advia and Date and Time MT. Note it is the same MT as the last MT from the S message coming from the Advia. /Token Transfer Message. Indicates that the message going out of the Advia and Date and Time MT. Note it is the same as the last MT from the S message coming in from the host Indicates that message going out of the Advia and Date and Time 06:31:07) MT/Token Transfer. Note the MT increase one character

IN (08/19/04 06:31:11) -> 3S g <OUT (08/19/04 06:31:12) ->3<OUT (08/19/04 06:31:17) -> 4S ` <This exchange continues until either the Host or the Advia has something to send When either device has something to send to the other, it must have received a S message, before it can send the message.

The Spy File

IN (08/09/04 16:11:30) -> ES
MT/Token Transfer. Gives control To the Advia

<OUT (08/09/04 16:11:30) ->E<MT. Note it is the same as the last MT from the S message coming in from the host The Advia still has control, No S message sent back yet. has a query message to send to the host. Note the MT has incremented one character since the last MT It

OUT (08/09/04 16:11:30) -> FQ 00000000042488 2 <IN (08/09/04 16:11:31) ->F<The Q is the code for the query message. The following 14 numbers is the ID number read from the barcode. Note: the Advia always queries 14 digits.

The host responds with the same MT as in the previous Q message.

The Spy File

IN (08/09/04 16:11:31) ->F<-

MT. Response from Host to last OUT message.

IN (08/09/04 16:11:32) -> GY 00000000042488 GV104490685 TESTA TESTABCDE 10/06/1963 F 08/09/04 1510 ER

001002003004005006007008010011015016014017018022020023021024 F <-

Workorder Message, Y. Note: the MT has incremented one character since the last MT ID number Patient number Patient Name Birth Date Sex Collection Date Collection Time Location Ordered Tests

WORKORDER CAN HAVE MORE OR LESS INFORMATION DEPENDING ON WHAT INFORMATION IS SENT TO THE ADVIA BY THE HOST
OUT (08/09/04 16:11:32) ->G<-

MT. Response to Host from last IN message.

The Spy File

OUT (08/09/04 16:11:32) ->G<MT. Response to Host from last IN message.

OUT (08/09/04 16:11:33) -> HE <IN (08/09/04 16:11:34) ->H<OUT (08/09/04 16:11:34) -> IS <10
Workorder Validation Message. E is the message code Error code/flag (Does not necessarily indicate error) 10(Query Mode) or 0 (downloading mode) indicates that workorder message content was valid. 14(Query Mode) or 4 (downloading mode) indicates invalid test number received in workorder. MT. Response from host to last OUT message MT/ Token Transfer.

The Spy File

IN (08/09/04 16:12:48) -> 3S g <OUT (08/09/04 16:12:48) ->3<OUT (08/09/04 16:12:48) -> 4R 00000000042488 22 08/09/04 16:11:45 10 318 11 8.5 20 62.6 21 25.8

MT/ token transfer. Advia now has control of the line

MT from Advia in response to token transfer

111.25 2 4.94 3 15.0 4 42.7 5 86.5 6 30.4 7 35.1 8 12.7 5.1 23 4.6 24 0.7 14 7.04 15 2.91 16 0.57 17 0.52 18 0.08

T <-

MT/ Result Message. R is the id code for the result message. SID#. Default is 14 characters Aspiration Date and time Host number followed by the result for the test associated with that host number.

IN (08/09/04 16:12:49) ->4<-

MT from Host in response to Advias result message

The Spy File

IN (08/09/04 16:12:49) ->4<MT. Response from host to result messages sent by Advia..

IN (08/09/04 16:12:50) -> 5Z X <OUT (08/09/04 16:12:50) ->5<OUT (08/09/04 16:12:50) -> 6S b <MT. Response from Advia to the result validation sent by the host MT/ Token Transfer.

Error code/flag (Does not necessarily indicate error) 0 = Result message content is valid, send next result 1 = Result can not be accepted 2 = Result message accepted, but host takes control of line MT/ Result Validation message. Z is the ID code for this message.

Other LIS Problems

After The LIS is connected and working properly there are still a few common situations that can occur:
When specimen is rerun, the results will not transmit to the LIS. Results will go over to LIS but flags will not. All results except one or two go to the LIS.

Other LIS Problems

When a specimen is rerun, The results will not go to the LIS The first time an SID# is run the results transmit just fine, but upon rerun they will not. They get a run screen, but results do not appear in the data manager.

Other LIS Problems

Check the UIW_Mode Setting (Should be OVR or HIS)

1. 2. 3. 4.

Tools modify FSE Parameters Password B00MFSEA File, Load, wst.ini, click ok

Other LIS Problems

Check the UIW_Mode Setting

5. Scroll down until you reach the first blank line, UIW_Mode is the line right above it 6. Change parameter to either OVR or HIS 7. Click on File, Save. Then File, Exit.

Other LIS Problems

Check the UIW_Mode setting in WST.ini file. There are 3 options. (Should be either OVR or HIS)
REJ (Reject) Rejects any subsequent runs of the same SID# from the data manager. Subsequent runs not transmitted to the LIS. OVR (Overwrite) Overwrites previous SID# in data manger with most current run. All runs are transmitted to LIS. HIS (Historical) Keeps record of all runs in the data manager. All runs are transmitted to the LIS

Other LIS Problems

What if the UIW setting is correct and a rerun still will not transmit to the LIS?
Check Customer Parameter # 1 List of sample status allowed to receive results / query answers should be set to P/H/I/CC/C. The default is P/H/I . During first run, the SID# is in the pending file, thus it can receive results from the Advia. Upon receiving results, in most cases the SID# with results moves to the complete file. Changing the parameter to P/H/I/CC/C, will allow that SID# in the complete file to receive additional results.

Other LIS Problems

Customer Parameter #1

1. 2. 3. 4.

Tools Modify Customer Parameters Parameter One Change both list of samples allowed to receive results and query answers to P/H/I/CC/C

Other LIS Problems

Results transmit over to the LIS just fine, but flags will not. This is optional on the Advia 120 and must be set up properly in the LIS.ini file, Customer parameters, and Possibly the WDR.par file.

Other LIS Problems

LIS.ini

1. 2. 3.

Tools Modify FSE PARAMETERS File, Load, lis.ini

Other LIS Problems

Lis.ini Host_Flag

4. Find the Host_Flag Parameter 6. Change parameter to F, if they want asterisk to transmit with flagged results results 7. Click on File, Save. Then File, Exit.

Other LIS Problems

If the customer wants the asterisk for flagged results to be sent to the host the Host_Flag option in LIS.ini must be set to F or DF. There are 3 options.
D (Disposition) The Advia sends the disposition code over to the host. If there is none, it will send a space. F (Flag) The system will transmit an * if there is a flag associated with a result. If there is none, it will send a space. DF (Disposition & Flag) The system will send both the disposition and Flag to the Host. IMPORTANT: This will change the size of the field from one to two bytes. The LIS must be then set up two receive two bytes for this field.

Other LIS Problems

If the customer wants to also send sample system flags to the LIS, Customer parameter 35 must be set to Yes. This will Allow a flag specific, two character code to be sent to the host computer whenever there is a sample system flag generated. If the lis.ini Host_Flag is set to F or DF, an asterisk will also be sent for all results affected by the sample system flag. A customer can either send asterisk, sample system flags or both, depending on their preferences.

Other LIS Problems

1. 2. 3. 4.

Tools Modify Customer Parameters Change Option 35 to Y File, Save. File Exit.

Other LIS Problems

If the customer states that the severity level for morphology flags are not transmitting over to the LIS, their system may not be able to accept the default severity levels (+++) that are being sent over. If this is the case, the pluses can be translated to numerical values, i.e. + = 1, ++ = 2, +++ = 3. This is done by modifying the WDR.par file and making a change to customer parameter number nine.

Other LIS Problems

1. 2. 3. 4.

Tools Modify Customer Parameters Change Option 9 to Y File, Save. File Exit.

Changing Option 9 to Y tells the Advia to use the WDR.par to translate the severity level pluses to the user defined characters in the wdr.par.

Other LIS Problems

1. 2. 3. 4. 5. 6. Tools Modify Customer Parameters Format File, Load, wdr.par, Click O.K. Change default to customer defined File, Save, File, Exit

DEFAULT

CUSTOMIZED

Other LIS Problems

The WDR.PAR file is used to associate a morphology flag transmitted by the analyzer to corresponding text defined in the Comment Dictionary of the Text Dictionaries, or to range checked values defined in the Test Dictionary. This comment can be displayed in the Review / Edit tab or transmitted to a Host computer. File Description Each line is composed of two parameters separated by a space: the first parameter is the morphology flag transmitted by the analyzer, and the second one is the corresponding text defined the Text Dictionary.

???? +@@@ ++@@ +++@

@ SLIGH MOD MARK

???? Indicates that the analyzer has transmitted a comment which is not described in the WDR.PAR file. @ = a space. The received comment can be translated into a numeric result that will be compared to the validation range. Example: The ++ comment result can be translated into 2, a + into 1, and a +++ into 3. These numeric values can be compared to applicable validation ranges. In order to send the comment to the Host, create a WDR.PAR file that correspond to the Text Dictionary.

Other LIS Problems

Most results transmit over to the LIS fine, but some do not. The customer states that they can see all the results on the run screen, but not on the LIS.

Other LIS Problems

The Advia will only transmit the tests that are contained in the workorder, but the Advia will run all tests that are associated with the selectivity that is run.
For instance: A HCT & HGB is ordered. The Advia will run a CBC and all tests can be seen on the Run Screen. Only the HCT and HGB will be accepted into the Data Manager as that is all that was ordered. Since the results do not enter the Data Manager, they will not be transmitted to the LIS. This can be changed by altering the Keep_Requested_Tests_Only parameter in the wst.ini file to N. Once this is done, both the ordered tests, and all tests run for the selectivity will be sent to the LIS. Sometimes LIS companies will cheat by only ordering one test in the profile such as RBC for CBC, %NEUT for the DIFF, %RETIC for RETIC. This will work if the Keep_Requested_Tests_Only is set to N. It is best if they order all tests. If all results are sent to the LIS, the LIS must be able to ignore the ones it does not need.

Other LIS Problems

This should bring up the workorder and show all the ordered tests.

To Check what tests are ordered on a SID#.

If LIS is on Query mode, scan or enter ID number. This should bring the workorder into the Data Manager pending file. If LIS is set to download mode, the workorder should already be in the pending file Double click on the number, next to pending and this will bring you to the file management screen.

Other LIS Problems

To Check what tests are ordered on a SID#.
Find the SID # that you are going to run and double click on it.

Other LIS Problems

To Check what tests are ordered on a SID#.
This should bring up the workorder and show all the ordered tests.

Other LIS Problems

Check the UIW_Keep_RequestedTestOnly

1. 2. 3. 4.

Tools modify FSE Parameters Password B00MFSEA File, Load, wst.ini, click ok

Other LIS Problems

Check the UIW_Keep_RequestedTestOnly

5. Scroll down until you reach UIW_Keep_RequestedTestOnly 6. Change parameter to N 7. Click on File, Save. Then File, Exit.

Back of Advia 120 Dell 1.8 Ghz computer.

Com 1 (LIS connection)

Com 2

BACK

Port Configuration

Port Configuration (Device Details)

Click on LIS Click on settings Click on Device Details

BACK

Cabling

BACK