You are on page 1of 58

KONELAB LIMS AND LAS INTERFACES

Code:

895304-4301

Manual version:

H

Date:

1.10.2003

KONELAB LIMS AND LAS INTERFACES Code: 895304-4301 Manual version: H Date: 1.10.2003 The CE mark attached

The CE mark attached on Konelab indicates the conformity with the EMC (electromagnetic compatibility) directive 89/336/EC.

Thermo Electron Oy, Clinical Diagnostics Clinical Chemistry & Automation Systems Ratastie 2, P.O. Box 100 FIN-01621 VANTAA, Finland Tel.: +358 9 329 100 Fax: +358 9 3291 0300

Information in this manual is subject to change without prior notice.

www.thermo.com/konelab

KONELAB LIMS AND LAS INTERFACES Code: 895304-4301 Manual version: H Date: 1.10.2003 The CE mark attached
I LIMS INTERFACE 1. HARDWARE INTERFACE 1 1.1 HOW TO INSTALL AND CONFIGURE THE ASTM SOFTWARE

I LIMS INTERFACE

  • 1. HARDWARE INTERFACE

1

  • 1.1 HOW TO INSTALL AND CONFIGURE THE ASTM SOFTWARE

2

INSTALLATION

  • 1.1.1 ..........................................................................................................................

2

CONFIGURATION

  • 1.1.2 .....................................................................................................................

3

  • 2. Konelab ONLINE (=KONE ONLINE) PROTOCOL

...................................................................

4

  • 2.1 BI-DIRECTIONAL MODE

4

  • 2.1.1 COMMUNICATION RECORDS

5

  • 2.1.1.1 INITIALISATION RECORDS

..............................................................................................................

5

  • 2.1.1.2 PATIENT INFORMATION RECORD

6

  • 2.1.1.3 SAMPLE INFORMATION RECORD

7

  • 2.1.1.4 TEST ANALYSIS RECORD

7

  • 2.1.1.5 RESULT RECORD

8

  • 2.1.1.6 FINISHING RECORD

8

  • 2.1.2 BI-DIRECTIONAL PROTOCOLS

9

  • 2.1.3 DATA VALIDITY CHECK

14

  • 2.1.3.1 CHECK SUM

14

  • 2.1.4 TIMING REQUIREMENTS

14

  • 2.2 EXAMPLES OF COMMUNICATION

15

  • 2.2.1 SAMPLE AND TEST DATA ENTRY

.........................................................................................

15

  • 2.2.2 RECEIVING NEW READY RESULTS

......................................................................................

16

  • 2.2.3 RECEIVING ALL READY RESULTS

17

  • 2.2.4 RECEIVING RESULTS FOR A SPECIFIC SAMPLE

17

  • 2.2.5 SENDING TEST DATA FOR OLD SAMPLES

18

  • 2.2.6 ENQUIRING TESTS IN USE IN THE ANALYSER

19

  • 2.3 ERROR HANDLING

..............................................................................................................

.........

20

  • 2.3.1 ERROR RECORD

20

  • 2.3.2 RESULT ERROR CODES

21

  • 2.3.3 COMMUNICATION ERROR CODES

......................................................................................

21

  • 2.3.4 ON LINE ERROR CODES

22

  • 2.3.5 EXAMPLES OF ERROR HANDLING

......................................................................................

24

  • 2.4 REQUESTING A CALCULATED TEST

25

  • 3. ASTM PROTOCOL

27

  • 3.1 FEATURES

27

  • 3.2 ASTM IN KONELAB

28

  • 3.2.1 ASTM 1394 – 91 STRUCTURE OF MESSAGES

28

  • 3.2.1.1 Header record (level 0)

.........................................................................................................................

28

  • 3.2.1.2 Message terminator record (level 0)

29

  • 3.2.1.3 Patient information record (level 1)

29

  • 3.2.1.4 Test order record (level 2)

31

  • 3.2.1.5 Result record (level 3)

..........................................................................................................................

33

  • 3.2.1.6 Comment record (level 4) used with the Result Record

.......................................................................

35

  • 3.2.1.7 Comment record (level 3) used with transmission related error conditions

36

  • 3.2.1.8 Request information record (level 1)

37

  • 3.2.2 FIELD LENGTHS USED BY Konelab

38

  • 3.2.3 EXAMPLES OF COMMUNICATION BETWEEN Konelab AND THE HOST

COMPUTER

39

II LAS INTERFACE

  • 4. KONELAB / LAS INTERFACE

..................................................................................................

44

  • 4.1 HARDWARE INTERFACE

 

44

  • 4.2 GENERAL DESCRIPTION

44

  • 4.2.1 MESSAGE RECORD FORMAT

44

  • 4.2.2 CALCULATION OF CHECKSUM

...........................................................................................

45

  • 4.2.3 SEQUENCE FOR INITIALISING THE COMMUNICATION INTERFACE

............................

46

  • 4.2.4 ANALYSER BOOT SEQUENCE

...............................................................................................

46

  • 4.2.5 KUSTI STATES AND ERROR RECOVERY

 

47

4.3.

COMMUNICATION RECORDS

49

  • 4.3.1 INITIALISATION RECORD

 

49

  • 4.3.2 ILLEGAL COMMAND RECORD

.............................................................................................

49

  • 4.3.3 ANALYSER STATUS QUERY RECORD

 

49

  • 4.3.4 ANALYSER STATUS RECORD

50 ................................................................................................

  • 4.3.5 ASPIRATE SAMPLE RECORD

50 ................................................................................................

  • 4.3.6 SAMPLE DISPENSING COMPLETE RECORD

......................................................................

51

  • 4.3.7 REINITIALISE COMMUNICATION RECORD

51

4.4

COMMUNICATION EXAMPLES

52

  • 4.4.1 INITIALISATION SEQUENCE

.................................................................................................

52

  • 4.4.2 SAMPLE ASPIRATION SEQUENCE FOR TWO SAMPLES

52

  • 4.4.3 SAMPLE ASPIRATION FAILS, RECOVERY SUCCESSFUL 1

53 ...............................................

  • 4.4.4 SAMPLE ASPIRATION FAILS, RECOVERY SUCCESSFUL 2

54 ...............................................

  • 4.4.5 SAMPLE ASPIRATION FAILS, RECOVERY UNSUCCESSFUL

............................................

55

1. HARDWARE INTERFACE The Konelab LIMS hardware interface works through serial communication channel. Figure 1: The
  • 1. HARDWARE INTERFACE

The Konelab LIMS hardware interface works through serial communication channel.

1. HARDWARE INTERFACE The Konelab LIMS hardware interface works through serial communication channel. Figure 1: The
1. HARDWARE INTERFACE The Konelab LIMS hardware interface works through serial communication channel. Figure 1: The

Figure 1: The connectors for serial communication channels are at the back of the

Konelab workstation. The connectors are 9-pin male D-connectors.

The channel (COM1,COM2) as well as the LIMS protocol (Konelab Online or

ASTM) and communication parameters (baud rate, number of bits in character,

number of start and stop bits and the use of parity) to be used can be configured in

the Konelab LIMS Configuration window.

Main window F8/F1 Configuration Configuration F7 LIMS Configuration LIMS Configuration
Main window
F8/F1
Configuration
Configuration
F7
LIMS
Configuration
LIMS Configuration
1. HARDWARE INTERFACE The Konelab LIMS hardware interface works through serial communication channel. Figure 1: The

Konelab LIMS and LAS Interfaces

29.09.03

895304-4301

1

LIMS AND LAS INTERFACES

The cable should be

made according to the

documentation of LIMS

system in use.

The signals needed at the Konelab end of cable

Pin 2

Receive Data

Pin 3

Transmit Data

Pin 5

Ground

This example describes

the minimum cable

connections needed.

Some computer systems

may require some

additional signals

connected locally within

connector. Please refer

to your LIMS

documentation for

further information.

An example of the cabling between Konelab and LIMS

Konelab and a PC (RS-232)

Konelab

PC

Pin 2 RxD---------------------------

TxD

Pin 3 TxD-----------------------------

RxD

Pin 5 Gnd ----------------------------- Gnd

  • 1.1 HOW TO INSTALL AND

CONFIGURE THE ASTM SOFTWARE

1.1.1

INSTALLATION

The ASTM software can be taken into use after the Konelab V3.0 software is

installed. If Konelab application is running, close the application by selecting

Management and Exit. Select Start->Programs->Konelab Lims Selection and select

ASTM from there. Now the LIMS interface will use ASTM software instead of

Konelab Online software. The ASTM configurations should be checked after

starting the Konelab application again, because the configuration file is updated in

start of the application.

LIMS AND LAS INTERFACES

1.1.2

CONFIGURATION

ASTM software has additional configurations as compared to Konelab Online

software. The configuration file is Konelab.ini and it is in folder C:\Konelab\Config.

The ASTM software

supports sending results

on ready sample or on

ready request basis. The

sending of results on

ready request basis will

load the interface heavily

and it is recommended

that sending results by

ready sample should be

used. This selection can

be done through the

Konelab Configuration

function.

The changes to the configuration are:

LimsProtocol = ASTM

  • - This is a new choice for protocol.

LimsAutomaticResultSending = YES

  • - When YES the new results are automatically send to Laboratory computer.

LimsThreadPriority = LOW

  • - This enables the Lims thread to use lower priority and give other software

processes more time.

LimsInterruptible = NO

  • - When YES the ASTM protocol allows the receiver to ask for interruption of

sending information.

LimsHostQuery =YES

  • - When YES the Konelab software will automatically send a query for sample

information and requests when new sample is introduced into Konelab.

SentryWaitsLimsRequests = YES

  • - When YES the sample entry function waits for the response to a query when new

sample is introduced.

ASTMControlResultSending = NO

  • - When YES the new control sample analysis results are automatically send to

Laboratory computer.

ASTMStandardResultSending = NO

  • - When YES the new calibrator sample analysis results are automatically send to

Laboratory computer.

SampleIdSendingDelay = 0

  • - If value is not 0, Konelab will use this delay between successive sending of new

sample Id's. This can be used to ease the burden on Laboratory computer when

e.g. a full segment with 14 samples is introduced. The value is expressed in

milliseconds.

ResultSendingDelay = 0

  • - If value is not 0, Konelab will use this delay between successive sending of new

sample results. This can be used to ease the burden on Laboratory computer. The

value is expressed in milliseconds.

In order to take ASTM protocol in use the configuration file should be edited

manually. Close the Konelab application by selecting MANAGEMENT and EXIT

from there. Wait for the Konelab application to shut down. Start Windows NT

Explorer by selecting Start-> Programs->Windows NT Explorer. Select the folder

C:\Konelab\Config and on the right side of Explorer display should be seen files

Konelab and UserText. Double click with mouse on Konelab file. Now the Notepad

program should open with the Konelab.ini file. Change the configuration manually

and after that save the modified file selecting File->Save. Now the Konelab software

can be started again with ASTM configurations.

LIMS AND LAS INTERFACES

LIMS AND LAS INTERFACES 2. Konelab ONLINE (=KONE ONLINE) PROTOCOL 2.1 BI-DIRECTIONAL MODE The analyser is
  • 2. Konelab ONLINE (=KONE

ONLINE) PROTOCOL

  • 2.1 BI-DIRECTIONAL MODE

The analyser is always

acting as co-operator

and the computer is the

host.

Konelab uses bi-directional data communication between the analyser and the

external computer i.e. both an external computer and the analyser can communicate

with each other. For example, the external computer can send test requests to

Konelab and the analyser can send completed results to the computer.

Bi-directional mode consists of seven different functions:

Function 1 is used when Patient data, Sample data and Test data is sent to

the analyser.

Function 2 is used to send Sample and Test data only to the analyser.

Control and Calibrator sample data can also be sent to the analyser using this

function.

Function 3 is used when a laboratory computer wishes to receive all newly

completed results which have not already been sent.

Function 4 is used when a laboratory computer wishes to receive all

results completed that day.

Function 5 is used when a laboratory computer wishes to receive all

results for a particular sample. Complete and incomplete tests are sent by the

analyser.

Function 6 is used for request inquiry i.e. a laboratory computer wishes to

know which patient samples exist in the database of the analyser. The laboratory

computer can then send new requests.

Function 7 is used when a laboratory computer wishes to know which tests

exist in the database of the analyser.

These functions are activated using the initialisation records. Refer to section 2.1.1.1.

LIMS AND LAS INTERFACES

  • 2.1.1 COMMUNICATION RECORDS

The following records are used when the analyser and the host computer

communicates with each other.

  • 2.1.1.1 INITIALISATION RECORDS

Initialisation records are activating commands which the host computer sends to the

analyser when the communication begins.

INITIALISATION RECORD 1

This record is used when Patient data, Sample data and Test data is sent to the

analyser.

:I:PR1/C/

C = check sum, refer to section 2.1.3.1.

INITIALISATION RECORD 2

This record is used to send Sample and Test data only to the analyser. Control and

Calibrator sample data can also be sent to the analyser using this initialisation record.

:I:PR2/C/

INITIALISATION RECORD 3

This record is used when a laboratory computer wishes to receive all newly

completed results which have not already been sent.

:I:PR3/C/

INITIALISATION RECORD 4

This record is used when a laboratory computer wishes to receive all results

completed that day.

:I:PR4/C/

INITIALISATION RECORD 5

This record is used when a laboratory computer wishes to receive all results for a

particular sample. Complete and incomplete tests are sent by the analyser.

:I:PR5/C/

INITIALISATION RECORD 6

This record is used when a laboratory computer wishes to know which patient

samples exist on the database of the analyser. The laboratory computer can then send

new requests.

:I:PR6/C/

INITIALISATION RECORD 7

LIMS AND LAS INTERFACES

This record is used when a laboratory computer wishes to know which tests exist on

the database of the analyser.

New or Old: If the

switch is N or n - the

analyser expects the

patient to be new. If

already present, an error

message is sent to the

computer. If the switch is

O or o and the patient

does not exist in the

analyser, again an error

message is sent. If the

switch is omitted the

patient is accepted in

ith

r

a

 

:I:PR7/C/

 

2.1.1.2

 

PATIENT INFORMATION RECORD

 

:P:nn

..

n/ii

..

i/M

or F/A or C/b

..

b/ss

..

s/n

or o/C/

P

- identifies the record to be a

 

Patient Information Record

nn

n

- Patient Name

 

(up to 24 characters)

ii

i

- Patient Identification

 

(up to 16 characters)

M

- Male (M) or Female (F)

 

Konelab ignores this; reference

 

class is always 0

A

- Adult (A) or Child (C)

 

Konelab ignores this; reference

 

class is always 0

bb

b

- Age or Date of Birth

 

(up to 8 characters)

ss

s

- Sender name

 

(up to 24 characters)

n or o

 

- New (n) or Old (o)

 

(1 character)

C

- check sum, refer to section

2.1.3.1.

The slash (/) must be entered into the string, since it is the field delimiter. This

means that the number of slashes in a record is always constant. Note that the slash is

a forbidden character inside a field.

For example, if no sender information and no age information is sent, the Data String

looks like:

 

:P:nn

..

n/ii

i/M/A///n

or o/C/

LIMS AND LAS INTERFACES

2.1.1.3 SAMPLE INFORMATION RECORD :S:ii .. i/pn/pp/st/nn/dd .. d/tt t/rrr/n or o/C/ Sample Type: S -
2.1.1.3
SAMPLE INFORMATION RECORD
:S:ii
..
i/pn/pp/st/nn/dd
..
d/tt
t/rrr/n
or o/C/
Sample Type:
S
- identifies the record to be a sample
If the type is @S, a
information record
calibrator name (i.e.
S0
S19)
is expected as the
ii
i
-
sample identification
(up to 16 characters)
id. If the identification is not
a calibrator name, an error
pn
- sample segment number
(up to 2 characters)
message will be sent.
If the type is @C, a control
pp
- sample segment position
(up to 3 characters)
name (i.e. C1
C19)
is
expected as the id. If the
st
- sample type
(up to 2 characters)
identification is not a
control name, an error
nn
- sample note data e.g. icteric (ic),
(up to 2 characters)
message will be sent.
haemolysed (HE), a user defined character
code, handled only as an information string
New or Old:
dd
d
- collection date, a user defined character
(up to 8 characters)
If the switch is N or n - the
code, handled only as an information string
analyser expects the sample
to be new. If already
tt
t
- collection time, a user defined character
(up to 5 characters)
present, an error message is
code, handled only as an information string
sent to the computer.
If the switch is O or o and
rrr
- dilution ratio (format is 1 + rrr)
(up to 3 characters)
the sample does not exist in
the analyser, again an error
n or o
- new/old
(1 character)
message is sent. If the switch
is omitted, the sample is
C
-
check sum, refer to section 2.1.3.1.
accepted in either case.
2.1.1.4
TEST ANALYSIS RECORD
:A:xx x/!/yy y/
..
..
....
/C/
A
- identifies the record to be the test analysis
record
!
- STAT identifier for following request
(1 character)
xx
..
x
-
test identification
(up to 8 characters)
Use the same test
yy y,etc ..
identification as in test's
parameters.
C
-
Check sum, refer to section 2.1.3.1.

The STAT identifier indicates that the following request must be performed urgently.

This is valid only for one request following the STAT identifier. If there is a STAT

profile to be sent, each test identification must have its separate STAT identifier. If

the '!' is omitted then the request is performed routinely,

i.e. :A:xx x/yy y/ /C/

..

... ..

LIMS AND LAS INTERFACES

SPECIAL NOTE:

The most significant

digit is lost if the

result includes more

than 6 characters.

2.1.1.5

 

RESULT RECORD

 
 

:R:ii

..

i/aa

..

a/rr r/ddd/ee e/aa a/rr r///

..

..

..

..

...

/C/

R

- identifies the record to be a result type record

 

ii

i

- sample identification, a shorter identification is

(16 characters)

 

filled with blanks by the analyser

 

aa

a

- analysis identification, a shorter identification

(8 characters)

 

is filled with blanks by the analyser

rr

r

- result, right justified, field is filled with blanks

(6 characters)

 

by the analyser. A possible minus sign is leading

the most significant character. The 6 characters

might include a decimal point which position is

defined by the parameter 'Number of decimals'

in the TEST DEFINITION window.

ddd

 

- dilution ratio (format is 1+ddd), total dilution

(up to 3

 

including both manual and automatic dilution

characters)

ee

e

- result error codes, refer to section 2.3.2.

(up to 10

 

characters)

If the result was obtained without a dilution, the dilution field is skipped (/ remains).

If the result has no error, the error field is skipped, (/ remains).

 

2.1.1.6

FINISHING RECORD

 

Finishing record is used in data sending as the last record to indicate to receiver that

communication is over. The receiver must always acknowledge finishing record by

<ACK>.

Finishing record has always the same format:

:F:PR/C/
:F:PR/C/

where C is the check sum. Refer to section 2.1.3.1 for the calculation of the check

sum.

LIMS AND LAS INTERFACES

  • 2.1.2 BI-DIRECTIONAL PROTOCOLS

PROTOCOL FOR SENDING PATIENT, SAMPLE AND TEST DATA TO THE ANALYSER

LABORATORY COMPUTER

ANALYSER

(Initialization record 1)(CR)(LF)

(Initialization record 1)(CR)(LF)
(ACK)

(ACK)

(Patient info record)(CR)(LF)

(Patient info record)(CR)(LF)
(ACK)

(ACK)

(Sample info record)(CR)(LF)

(Sample info record)(CR)(LF)
(ACK)

(ACK)

(Test analysis record)*(CR)(LF)

(Test analysis record)*(CR)(LF)
(ACK)

(ACK)

(Sample info record)(CR)(LF)

(Sample info record)(CR)(LF)
(ACK)

(ACK)

(Test analysis record)*(CR)(LF)

(Test analysis record)*(CR)(LF)
(ACK)

(ACK)

(Patient info record)(CR)(LF)

(Patient info record)(CR)(LF)
(ACK)

(ACK)

(Sample info record)(CR)(LF)

(Sample info record)(CR)(LF)
(ACK)

(ACK)

(Test analysis record)*(CR)(LF)

(Test analysis record)*(CR)(LF)
(ACK)

(ACK)

(Finishing record)(CR)(LF)

(Finishing record)(CR)(LF)
(ACK)

(ACK)

*A number of Test Analysis records may follow, which must be acknowledged by

(ACK)

LIMS AND LAS INTERFACES

PROTOCOL FOR SENDING SAMPLE AND TEST DATA TO THE ANALYSER

LABORATORY COMPUTER

ANALYSER

(Initialization record 2)(CR)(LF)

(Initialization record 2)(CR)(LF)
(ACK)

(ACK)

(Sample info record)(CR)(LF)

(Sample info record)(CR)(LF)
(ACK)

(ACK)

(Test analysis record)*(CR)(LF)

(Test analysis record)*(CR)(LF)
(ACK)

(ACK)

(Sample info record)(CR)(LF)

(Sample info record)(CR)(LF)
(ACK)

(ACK)

(Test analysis record)*(CR)(LF)

(Test analysis record)*(CR)(LF)
(ACK)

(ACK)

(Finishing record)(CR)(LF)

(Finishing record)(CR)(LF)
(ACK)

(ACK)

* A number of Test Analysis records may follow, which must be acknowledged by

(ACK).

PROTOCOL FOR RECEIVING NEWLY COMPLETED RESULTS FROM THE ANALYSER

LABORATORY COMPUTER

ANALYSER

(Initialization record 3)(CR)(LF)

(Initialization record 3)(CR)(LF)
(ACK)

(ACK)

(Result record)*(CR)(LF)

(Result record)*(CR)(LF)

(ACK)

(ACK)
(Finishing record)(CR)(LF)

(Finishing record)(CR)(LF)

(ACK)

(ACK)

*

A number of Result Records may follow, which must be acknowledged by

(ACK).

LIMS AND LAS INTERFACES

PROTOCOL FOR RECEIVING ALL COMPLETED RESULTS FROM THE ANALYSER, I.E. RECOVERY WHEN THE ANALYSER OR COMPUTER GOES DOWN

LABORATORY COMPUTER

ANALYSER

(Initialization record 4)(CR)(LF)

(Initialization record 4)(CR)(LF)
(ACK)

(ACK)

(Result record)*(CR)(LF)

(Result record)*(CR)(LF)

(ACK)

(ACK)
(Finishing record)(CR)(LF)

(Finishing record)(CR)(LF)

(ACK)

(ACK)

* A number of Result Records may follow, which must be acknowledged by (ACK).

LIMS AND LAS INTERFACES

PROTOCOL FOR RECEIVING RESULTS ON A SPECIFIC SAMPLE, I.E. STAT SAMPLE

 

LABORATORY COMPUTER

ANALYSER

 

(Initialization record 5)(CR)(LF)

(Initialization record 5)(CR)(LF)
 
(ACK)

(ACK)

 

(Sample info record)(CR)(LF)

(Sample info record)(CR)(LF)
 
(ACK)

(ACK)

(Result record)*(CR)(LF)

(Result record)*(CR)(LF)

 

(ACK)

(ACK)
 
(Finishing record)(CR)(LF)

(Finishing record)(CR)(LF)

 

(ACK)

(ACK)

***

(Sample info record)(CR)(LF)

(Sample info record)(CR)(LF)
 
(ACK)

(ACK)

(Result record)*(CR)(LF)

(Result record)*(CR)(LF)

 

(ACK)

(ACK)
 
(Finishing record)(CR)(LF)

(Finishing record)(CR)(LF)

 

(ACK)

(ACK)

***

(Finishing record)(CR)(LF)

(Finishing record)(CR)(LF)
 
(ACK)

(ACK)

*

A number of Result Records may follow, which must be acknowledged by

(ACK).

** A short delay (10 ms) must exist in these phases.

LIMS AND LAS INTERFACES

PROTOCOL FOR SENDING REQUESTS FOR OLD SAMPLES

Sample info record is

identical to the record

used by the laboratory

computer to send sample

info.

The part between '== 1

==' and '== 2 ==' is

repeated until all the

samples in the analyser's

database have been

processed, excluding

calibrators and controls.

LABORATORY COMPUTER

ANALYSER

(Initialization record 6)(CR)(LF)
(Initialization record 6)(CR)(LF)
  • (ACK)

= = 1 = =

  • (Sample info record)*(CR)(LF)

(ACK)

LABORATORY COMPUTER ANALYSER (Initialization record 6)(CR)(LF) (ACK) = = 1 = = (Sample info record)*(CR)(LF) (ACK)

**

(Test analysis record)(CR)(LF)

LABORATORY COMPUTER ANALYSER (Initialization record 6)(CR)(LF) (ACK) = = 1 = = (Sample info record)*(CR)(LF) (ACK)

(Finishing record)(CR)(LF)

(ACK) (ACK)
(ACK)
(ACK)

= = 2 = =

  • (Finishing record)(CR)(LF)

(ACK)

LABORATORY COMPUTER ANALYSER (Initialization record 6)(CR)(LF) (ACK) = = 1 = = (Sample info record)*(CR)(LF) (ACK)

*

A number of Test Analysis Records may follow, which must be acknowledged by

(ACK).

** A short delay must exist in these phases.

PROTOCOL FOR ENQUIRING TESTS IN USE IN THE ANALYSER

Test analysis record is

identical to the record

used by the host to send

requests, except it never

contains the STAT

identifier ('!').

LABORATORY COMPUTER

ANALYSER

(Initialization record 7)(CR)(LF)

(Initialization record 7)(CR)(LF)
(ACK)

(ACK)

(Test analysis record)*(CR)(LF)

(Test analysis record)*(CR)(LF)

(ACK)

(ACK)
(Finishing record)(CR)(LF)

(Finishing record)(CR)(LF)

(ACK)

(ACK)

*

A number of Test Analysis Records may follow, which must be acknowledged by

(ACK).

LIMS AND LAS INTERFACES

2.1.3 DATA VALIDITY CHECK The communication is full duplex and ASCII characters are used, but the
2.1.3
DATA VALIDITY CHECK
The communication is full duplex and ASCII characters are used, but the user can
select the number of data bits, stop bits, parity and speed in the Configuration
window.
Each record begins with a colon ':' and ends with a check character 'C' followed by a
slash '/', carriage return and line feed.
Maximum record length is 132, including check sum.
2.1.3.1
CHECK SUM
The check sum is calculated from the colon to the last slash before the check sum
character.
The check sum is defined by the following formula (decimal system):
C = Σ i (C i - 32) mod 64 + 32
where C i = each character
EXAMPLE OF CALCULATING A CHECK SUM
String without check sum
:
I:
P
R2
/
The string begins with
the : character and
ASCII VALUE
58
73
58
80
82
50
47
includes all characters
up to, and including,
SUBTRACT 32
26
41
26
48
50
18
15
the / character before
TOTAL
26
67
93
141
191
209
224
the check sum
character.
MODULUS 64
26
3
29
13
63
17
32
ADD 32
64
CHARACTER
@
String with check sum and delimiter
:I
:
P
R
2
/
@
/
2.1.4
TIMING REQUIREMENTS

The host computer has max. 60 seconds time for answering by (ACK) or (NAK).

Otherwise the protocol has to be restarted.

The time the analyser needs for validation of a record depends on the situation and in

the worst case it may take few minutes. Recommended time out value is at least 3

minutes when waiting the response from the analyser.

When the host computer asks results from the analyser with certain intervals, the

recommended minimum time between consecutive asking is at least 5 minutes.

LIMS AND LAS INTERFACES

  • 2.2 EXAMPLES OF COMMUNICATION

This section gives brief examples of the protocol as it would be used in practice.

The examples are only intended to give an indication of the stages involved in each

operation, the data transmitted is arbitrary.

The direction in which the message is going.

LIMS AND LAS INTERFACES 2.2 EXAMPLES OF COMMUNICATION This section gives brief examples of the protocol
LIMS AND LAS INTERFACES 2.2 EXAMPLES OF COMMUNICATION This section gives brief examples of the protocol

means from the computer to the analyser

means from the analyser to the computer

  • 2.2.1 SAMPLE AND TEST DATA ENTRY

WITH PATIENT DATA

LABORATORY COMPUTER

ANALYSER

:I:PR1/?/

:I:PR1/?/
ACK

ACK

:P:SMITH JOHN/4///30/2/N/8/

:P:SMITH JOHN/4///30/2/N/8/
ACK

ACK

:S:6///PL/HA/97-12-18/12:13/0/N/7/

:S:6///PL/HA/97-12-18/12:13/0/N/7/
ACK

ACK

:A:ISE/ALB/ALK.PH/ALT/DBIL/GGT/PROT/T/

:A:ISE/ALB/ALK.PH/ALT/DBIL/GGT/PROT/T/
ACK

ACK

:P:JONES SUSAN/23423///97-12-08/3/O/_/

:P:JONES SUSAN/23423///97-12-08/3/O/_/
ACK

ACK

:S:12/2/1/SE//97-12-07/09:45/0/O/)/

:S:12/2/1/SE//97-12-07/09:45/0/O/)/
ACK

ACK

:A:!/ALB/!/ALK.PH/!/ALT/!/DBIL/!/GGT/@/

:A:!/ALB/!/ALK.PH/!/ALT/!/DBIL/!/GGT/@/
ACK

ACK

:F:PR/+/

:F:PR/+/
ACK

ACK

LIMS AND LAS INTERFACES

WITHOUT PATIENT DATA

Sample number 12 has

been allocated to position

1 on segment 2, but sample

number 6 will be allocated

to a position when the

sample is entered to the

analyser. Also, the tests for

sample number 12 are to

be performed as STAT

tests.

LABORATORY COMPUTER

ANALYSER

:I:PR2/@/

:I:PR2/@/
ACK

ACK

:S:6///PL/HA/97-12-18/12:13/0/N/7/

:S:6///PL/HA/97-12-18/12:13/0/N/7/
ACK

ACK

:A:ISE/ALB/ALK.PH/ALT/DBIL/GGT/PROT/T/

:A:ISE/ALB/ALK.PH/ALT/DBIL/GGT/PROT/T/
ACK

ACK

:S:12/2/1/SE//97-12-07/09:45/0/O/)/

:S:12/2/1/SE//97-12-07/09:45/0/O/)/
ACK

ACK

:A:!/ALB/!/ALK.PH/!/ALT/!/DBIL/!/GGT/@/

:A:!/ALB/!/ALK.PH/!/ALT/!/DBIL/!/GGT/@/
ACK

ACK

:F:PR/+/

:F:PR/+/
ACK

ACK

  • 2.2.2 RECEIVING NEW READY RESULTS

Results which had been transmitted previously will not be sent again.
Results which had
been transmitted
previously will not be
sent again.

LABORATORY COMPUTER

ANALYSER

:I:PR3/A/

:I:PR3/A/
ACK

ACK

:R:2/ K / 4.7///NA /136//102; 137/CL///002;/-/

:R:2/ K / 4.7///NA /136//102; 137/CL///002;/-/

ACK

ACK
:R:2 /ALB / 43.3///PROT / 48.4//102; 60/^/

:R:2 /ALB / 43.3///PROT / 48.4//102; 60/^/

ACK

ACK
:F:PR/+/

:F:PR/+/

ACK

ACK

LIMS AND LAS INTERFACES

  • 2.2.3 RECEIVING ALL READY RESULTS

 

The results for

 

sample 1 had been

transmitted

previously but were

sent again along

with new results for

samples 2 and 3.

 
 

The error message

against the ALB

test indicates that

the result is not

ready.

LABORATORY COMPUTER ANALYSER :I:PR4/B/
LABORATORY COMPUTER
ANALYSER
:I:PR4/B/
  • ACK

  • :R:1/ LDH / 600/5.0//CREA /67///G/

ACK

LABORATORY COMPUTER ANALYSER :I:PR4/B/ ACK :R:1/ LDH / 600/5.0//CREA /67///G/ ACK :R:2 /K / 4.7///NA /
  • :R:2 /K / 4.7///NA / 136//102; 137/CL ///002;/-/

ACK

LABORATORY COMPUTER ANALYSER :I:PR4/B/ ACK :R:1/ LDH / 600/5.0//CREA /67///G/ ACK :R:2 /K / 4.7///NA /
  • :R3 /ALB / 43.3///PROT / 48.4//102; 60/^/

ACK

ACK

LABORATORY COMPUTER ANALYSER :I:PR4/B/ ACK :R:1/ LDH / 600/5.0//CREA /67///G/ ACK :R:2 /K / 4.7///NA /
  • :F:PR/+/

LABORATORY COMPUTER ANALYSER :I:PR4/B/ ACK :R:1/ LDH / 600/5.0//CREA /67///G/ ACK :R:2 /K / 4.7///NA /
  • 2.2.4 RECEIVING RESULTS FOR A SPECIFIC

SAMPLE

LABORATORY COMPUTER

ANALYSER

:I:PR5/C/

:I:PR5/C/
ACK

ACK

:S:6/// PL/HA/97-12-18/12:13/0/N/7/

:S:6/// PL/HA/97-12-18/12:13/0/N/7/
ACK

ACK

:R:6 /ALB ///001;/PROT / 4

:R:6 /ALB ///001;/PROT / 4

 

8.4//102; 60.0/C/

ACK

ACK
:F:PR/+/

:F:PR/+/

ACK

ACK

:F:PR/+/

:F:PR/+/
ACK

ACK

LIMS AND LAS INTERFACES

  • 2.2.5 SENDING TEST DATA FOR OLD

SAMPLES

LABORATORY COMPUTER

ANALYSER

:I:PR6/D/

:I:PR6/D/
ACK

ACK

:S:6 / 1/ 19/PL/HA/97-12-19/14:55/ 0//D/

:S:6 / 1/ 19/PL/HA/97-12-19/14:55/ 0//D/

ACK

ACK

:A:GLUC/CREA/CA/ALB/CHOL/_/

:A:GLUC/CREA/CA/ALB/CHOL/_/
ACK

ACK

:F:PR/+/

:F:PR/+/
ACK

ACK

ACK

ACK :S:12 / 1/20/SE/CO/97-12-13/11:35/ 0//N/

:S:12 / 1/20/SE/CO/97-12-13/11:35/ 0//N/

:A:CA/ALB/CHOL/;/

:A:CA/ALB/CHOL/;/
ACK

ACK

:F:PR/+/

:F:PR/+/
ACK

ACK

:F:PR/+/

:F:PR/+/

ACK

ACK

LIMS AND LAS INTERFACES

  • 2.2.6 ENQUIRING TESTS IN USE IN THE

ANALYSER

LABORATORY COMPUTER

ANALYSER

:I:PR7/E/

:I:PR7/E/
ACK

ACK

 

:A:ALT /ALB / ALP /AMYL / AST

 
/CA /CHOL /CL /CPK /CREA

/CA /CHOL /CL /CPK /CREA

 

/CRP / FE / GGT /F/

ACK

ACK
 

:A:GLUC /K /LDH /LI / MG /NA /P

 
/PH / TBIL/ TPROT / TRIGLY /UR

/PH / TBIL/ TPROT / TRIGLY /UR

 

AC /J/

ACK

ACK
:F:PR/+/

:F:PR/+/

ACK

ACK

LIMS AND LAS INTERFACES

  • 2.3 ERROR HANDLING

In the event of an error in the data transmission, the analyser returns an error record

instead of ACK. This situation could arise for instance when the laboratory

computer sends a test analysis record for a test which does not exist in the analyser.

For example:

LABORATORY COMPUTER

ANALYSER

(Initialization record 1)(CR)(LF)

(Initialization record 1)(CR)(LF)
(ACK)

(ACK)

(Patient info record)(CR)(LF)

(Patient info record)(CR)(LF)
(ACK)

(ACK)

(Sample info record)(CR)(LF)

(Sample info record)(CR)(LF)
(ACK)

(ACK)

(Test analysis record)(CR)(LF)

(Test analysis record)(CR)(LF)

- error in this record

 
(Error record)(CR)(LF)

(Error record)(CR)(LF)

(ACK)

(ACK)

(Finishing record)(CR)(LF)

(Finishing record)(CR)(LF)
(ACK)

(ACK)

When the laboratory computer receives an error record, the analyser expects a

finishing record to be sent back to acknowledge the error situation. The analyser

acknowledges this by sending back an ACK. After this, the protocol begins again

with the laboratory computer starting the bidding with the initialisation record. All

data up to the ACK sent by the analyser prior to the error is saved in the analyser,

including also the requests at the beginning of an analysis record up to the wrong test

identification.

  • 2.3.1 ERROR RECORD

:E:xx x/C/ ..
:E:xx x/C/ ..

E

xx

..

x

- identifies the record to be an error record

- communication error code, refer to section 2.3.3

(up to 30 characters)

LIMS AND LAS INTERFACES

2.3.2

RESULT ERROR CODES

 

ERROR CODE

EXPLANATION

001;

result not ready, in this case result is skipped in result record

002;

result rejected, result will never come, e.g. one ISE electrode

was disabled

003;

screening test not measurable, condition due to screening test

rejection

101;xx x ..

result over reference, xx

x

is the limit

102;xx x ..

result under reference, xx

x

is the limit

2.3.3

COMMUNICATION ERROR CODES

ERROR CODES

EXPLANATION

001;

format error, this error occurs when the laboratory computer

has three times sent a record which either has wrong check

sum or is too long (> 132 characters)

 

003;

invalid initialisation record

 

004;

invalid record identification

 

005;

protocol error

101;x xx ..

invalid sender identification, x

xx

means the invalid sender id

103;x xx ..

invalid sample identification, x

xx

means the invalid sample

id

104;x xx ..

invalid sample plate position, x

xx

means the invalid position

105;x xx ..

invalid analysis identification, x

xx

means the invalid id

106;x xx ..

calibrator or control name does not exist, x

xx

is the name

107;x xx ..

invalid sample type, x

xx

is the type

- this error occurs when @C or @S is the sample type when

initialisation record 1 is used

 

108;

number of samples / patient exceeded, max nbr is 10

201;x xx ..

sample segment position is reserved, x

xx

is the sample

segment position

210;x xx ..

patient already exists, x

xx

is the patient name

 

211;x xx ..

patient does not exist, x

xx

is the patient name

 

220;x xx ..

sample already exists, x

xx

is the sample id

 

221;x xx ..

sample does not exist, x

xx

is the sample id

 

LIMS AND LAS INTERFACES

  • 2.3.4 ON LINE ERROR CODES

The message 'Online' is given on the Main window during data transmission. If there

are errors on the transmission, error messages are given via the analyser.

  • 32 WRONG DATA FROM AN OTHER PROCESS (LIMS)

Internal software problem in the database. Restart the workstation.

  • 401 SERIAL LINE PARAMETER ERROR (LIMS)

Check the serial interface parameters in the Configuration window.

  • 402 WRONG SERIAL PORT (LIMS)

Check the serial interface parameters in the Configuration window.

  • 403 WRITE ERROR (LIMS)

  • 407 TRANSMISSION ERROR (LIMS)

  • 409 MESSAGE BUFFER ERROR (LIMS)

External computer has received the data but transmission has been detected to be

incorrect.

Possible causes

E.g. electronic malfunction, software error,

initialisation error or power failure.

Check the cable and cable connection. If the problem

persists, print the reports and call service.

  • 404 READ ERROR (LIMS)

The analyser has received the data but transmission has been recognised to be

incorrect.

Possible causes

E.g. electronic malfunction, software error,

initialisation error or power failure.

Check the cable and cable connection. If the problem

persists, print the reports and call service.

LIMS AND LAS INTERFACES

  • 405 SYNCRONIZATION ERROR (LIMS)

The analyser received a data record 1 while it was expecting an ACK character or it

received ACK/NAK while expecting a data record.

Possible causes

E.g. faulty cable, electronic malfunction, software

error.

Check the cable and cable connection. If the problem

persists, print the reports and call service.

1 ) A data record is a string of any characters beginning with ':' and ending with

(0D hex) or a string of any characters whose length exceeds the size of input buffer

(currently 132).

  • 406 COMMUNICATION TIMEOUT (LIMS)

External computer did not answer in the allowed time.

Possible causes

E.g. faulty cable, electronic malfunction or wrong

initialisation data.

Check the cable and cable connection. If the problem

persists, print the reports and call service.

  • 408 ERROR WHEN DOING DATABASE OPERATION

(LIMS)

Warning about internal software problem in the database. Analysis

continues. If the problem persists restart the workstation.

  • 410 LIMS TYPE MISMATCH BETWEEN LIMS PROCESS

AND KONELAB.INI

To continue using the Konelab program, first exit from it by selecting

F8/F3 in the Management window. Then select the correct LIMS process from

Start: Programs: lims selection. Finally, start the Konelab program again by

clicking the konelab –icon.

  • 999 LIMS ERROR MESSAGE (%u)

- %u MEANS THE ERROR NUMBER

- Software problem. Analysis continues.

LIMS AND LAS INTERFACES

  • 2.3.5 EXAMPLES OF ERROR HANDLING

INVALID CHECK SUM

 

The check sum in the

 

LABORATORY COMPUTER

ANALYSER

first message was

 
 

incorrect, so the

analyser requested the

:I:PR2/?/

analyser requested the :I:PR2/?/

message to be sent

 

again.

 
again. NAK

NAK

 

:I:PR2/@/

:I:PR2/@/
ACK

ACK

ERROR IN DATA TRANSMITTED

 

The analyser does not

recognise XXX as a valid

 

LABORATORY COMPUTER

ANALYSER

 
 

test id and so it sends

error message 105 which

:I:PR2/@/

error message 105 which :I:PR2/@/

the computer

 

acknowledges. The

 
acknowledges. The ACK

ACK

computer would

 

probably now try to send

:S:126///SE//97-12-18/12:13/0/N/O/

probably now try to send :S:126///SE//97-12-18/12:13/0/N/O/

the other tests for

 

samples and inform the

 
samples and inform the ACK

ACK

user of the problem.

:A:XXX/PROT/@/

user of the problem. :A:XXX/PROT/@/
 
:E:105;XXX /A/

:E:105;XXX /A/

ACK

ACK

:F:PR/+/

:F:PR/+/
ACK

ACK

LIMS AND LAS INTERFACES

  • 2.4 REQUESTING A CALCULATED

TEST

Calculated tests can be requested online. All needed test requests belonging to the

calculated test are generated automatically. The analyser is trying to use the latest

introduced samples. If it doesn't success in that it uses the older ones.

The following requirements for requesting calculated tests online must be fulfilled:

If requirements are

not fulfilled the error

message '105:

Analysing error' is

appearing.

1) Tests

  • All tests including into the calculated test and the calculated test itself must be defined in use.

  • All tests including into the calculated test and the calculated test itself must have the online name.

This concerns also external tests belonging to the calculated test.

A B
A
B

To define a calculated test refer to Konelab Reference manual, chapter 4.1.4.

2) Samples

First introduce samples with the right sample types, after that give the test request for

the calculated test.

The right sample type here means the sample type belonging to the calculated test

request.

LIMS AND LAS INTERFACES

When a calculated

(patient) test has been

requested there must

be a PR1-record or the

patient must have been

introduced in the

Patient entry window

in the user interface.

An example of requesting a calculated (patient) test (=CC) and a calculated (sample) test (=LDL) via LIMS:

:I:PR1/?/

:P:Patient1///////3/

:S:Sample1///S//////4/

:S:Sample2///U//////7/

:A:CC/J/

:F:PR/+/

:I:PR2/@/

:S:Sample3///S//////6/

:A:LDL/@/

:F:PR/+/

Reporting

Reporting gives result of calculated (patient) test according to a patient. In addition

the external test is reported according to a patient. Results of tests including into the

calculated test are reported separately according to samples.

LIMS AND LAS INTERFACES

LIMS AND LAS INTERFACES 3. ASTM PROTOCOL The ASTM Laboratory Information Management System interface is based
  • 3. ASTM PROTOCOL

The ASTM Laboratory Information Management System interface is based on the

following ASTM standards: ASTM 1394-91 "Standard Specification for

Transferring Information Between Clinical Instruments and Computer Systems" and

ASTM 1381-95 "Standard Specification for Low-Level Protocol to Transfer

Messages Between Clinical Laboratory Instruments and Computer Systems.

3.1

FEATURES

The physical transmission layer is implemented according to ASTM 1381. The cable

connector is a 9-pin male connector instead of the standard 25-pin male connector.

The logical layer contains selected portions of ASTM 1394. The detailed record

structure is described in section 3.2.1 ASTM in Konelab: ASTM 1394-91 Structure

of messages.

The main features are:

  • - automatic request for sample information when new sample is introduced to the

instrument (configurable ON/OFF)

  • - automatic sending of results either on ready sample or ready request basis

(configurable reporting basis and ON/OFF)

  • - automatic sending of control sample results (configurable ON/OFF)

  • - automatic sending of calibrator sample results (configurable ON/OFF)

  • - response to sample information requests from Laboratory computer

  • - response to control sample information requests from Laboratory computer

  • - response to sample information received from Laboratory computer

  • - cancelling of requests through ASTM by Laboratory computer

  • - error situation management

LIMS AND LAS INTERFACES

  • 3.2 ASTM in Konelab

    • 3.2.1 ASTM 1394 – 91 STRUCTURE OF

MESSAGES

Following sections show the ASTM records used by Konelab. The tables in sections

include field name and number, next two fields has the information about the fields

usage by the host or the instrument, and a comment on use of the field. If the field is

optional the mark at usage information is between brackets. Host can send all fields,

but only the ones with mark are processed.

  • 3.2.1.1 Header record (level 0)

Field Name

No

Host

Instr.

Comment

Record type

1

  • X X

 

Always H. Starts every message. Note: no

ID

delimiter between the first and the second

field

Delimiter

2

  • X X

 

Field, repeat, component and escape

definition

delimiters

Message

3-

 

-

 

control ID

Access

4-

 

-

 

password

Sender name

5

 

X

  • - Instrument type

60/30/20

or ID

X

  • - ^instrument ID

InstrumentData.iId

X

  • - ^software version

Get_version ?

Sender street

6-

 

-

 

address

Reserved

7-

 

-

 

field

Sender

8-

 

-

 

telephone

number

Characteristic

9-

 

-

 

s of sender

Receiver ID

  • 10 -

 

-

 

Comment or

  • 11 -

 

-

 

special

instructions

Processing

  • 12 X

   
  • X P –production

ID

X

  • X T –training

X

  • X D –debugging

X

  • X Q –QC

Version No.

  • 13 -

 

-

 

Date and time

  • 14 -

 

(X)

Form YYYYMMDDHHMMSS. Only in

of message

debug mode

LIMS AND LAS INTERFACES

3.2.1.2

Message terminator record (level 0)

Field Name

No

Host

Instr.

Comment

Record type ID

1

  • X X

 

Always L. Ends every message.

Sequence

2

  • X X

 

Always 1. One terminator per message.

number

Termination

3

(X)

(X)

N or missing –normal termination

code

X

X

T –sender aborted

X

X

R –receiver requested abort

X

X

E –unknown error

-

X

Q –error in last request for information

-

X

I –no information available from last

query

-

X

F –last request for information processed

3.2.1.3

Patient information record (level 1)

Field Name

No

Host

Instr.

Comment

Record type ID

1

X

X

Always P.

Sequence

2

X

X

Running number within Message. Starts

number

with 1.

Practice

3

(X)

(X)

If no code is given, this gets the value of

assigned patient

Patient name.

ID

PatientData.sCode

Laboratory

4-

 

-

 

assigned patient

ID

Patient ID No.

5-

 

-

 

3

Patient name

6

(X)

(X)

Last name

-

-

^First name

-

-

^middle name or initial

-

-

^suffix

-

-

^title

Only one text field. The whole name

should be given there. Optional if no

patient relates to sample.

PatientData.sName

Mothers

7-

 

-

 

maiden name

Date of birth

8

(X)

(X)

Form YYYYMMDD.

PatientData.acBirthDate

Patient sex

9

(X)

-

RefClassData.sName

Patient race-

  • 10 -

 

-

 

ethnic origin

Patient address

  • 11 -

 

-

 

Reserved field

  • 12 -

 

-

 

Patient

  • 13 -

 

-

 

telephone

number

Attending

  • 14 -

 

-

 

physician ID

Special field 1

  • 15 -

 

-

 

Special field 2

  • 16 -

 

-

 

LIMS AND LAS INTERFACES

Patient height

17

-

-

 

Patient weight

18

-

-

 

Patient’s known

19

-

-

 

or suspected

diagnosis

Patient active

20

-

-

 

medications

Patient’s diet

21

-

-

 

Practice field 1

22

-

-

 

Practice field 2

23

-

-

 

Admission or

24

-

-

 

discharge dates

Admission

25

-

-

 

status

Location

26

(X)

(X)

SenderData.sID

Native of

27

-

-

 

alternative

diagnostic code

and classifiers

Alternative

28

-

-

 

diagnostic code

and

classification

Patient religion

29

-

-

 

Marital status

30

-

-

 

Isolation status

31

-

-

 

Language

32

-

-

 

Hospital

33

-

-

 

service

Hospital

34

-

-

 

institution

Dosage

35

-

-

 

category

LIMS AND LAS INTERFACES

If even one test is

requested as stat the

priority of test order

record is set to stat (S)

when results are

reported by samples.

When results are

reported by requests

the right test priority is

always seen.

  • 3.2.1.4 Test order record (level 2)

Field Name

No

Host

Instr.

Comment

Record type ID

 
  • 1 X

X

 

Always O.

Sequence

 
  • 2 X

X

 

Running number within Patient

number

information. Starts with 1.

Specimen ID

3

(X)

(X)

SpecimenID^ManualDilution^Segment^P

osition

Optional if no sample in order.

Mapping to Konelab internal presentation:

SpecimenID

PatientSampleData.sID

ManualDilution

PatientSampleData.fManualDilRatio

Segment

StorageCollectionData.iId

Position

StorageItemData.ucPosition

If ManualDilution, Segment and Position

information is omitted, the value of 0 will

be used for each. Segment value 0 with

position value 0 refer to a virtual

collection and can be used safely, when no

actual position is known.

Instrument

4-

 

-

 

specimen ID

Universal test

5

-

-

Universal test ID

ID

-

-

^universal test name

-

-

^universal test ID type

X

X

^manufacturer defined test code

TestData.sOnlineName

-

X

^auto-dilution factor

Multiple tests can be ordered separated by

repeat delimiter.

Priority

6

(X)

 
  • (X) S –stat

REQ_PRIOR_STAT

(X)

  • (X) A –asap

REQ_PRIOR_ASAP

(X)

  • (X) R –routine

REQ_PRIOR_NORMAL

-

-

C –callback

-

-

P –preoperative

*.ucPriority

Optional if no sample or sample is

calibrator or control.

Requested/orde

7-

 

-

 

red date and

time

Specimen

8

(X)

(X)

Form YYYYMMDDHHMMSS

collection date

PatientSampleData.sCollectionInfo

and time

Collection end

9-

 

-

 

time

Collection

  • 10 -

 

-

 

volume

Collector ID

  • 11 -

 

-

 

LIMS AND LAS INTERFACES

Action code

12

X

X

C

–cancel

X

-

A –add test requests to existing specimen

X

-

N –new test requests + new specimen

-

X

P –pending specimen

-

-

L

–reserved

-

X

X

–specimen or test in process

X

X

Q –QC specimen

Multiple action codes can be given

separated by repeat delimiter. For example

 

X\Q.

Danger code

13

-

-

 

Relevant

14

(X)

(X)

PatientSampleData.osComment

clinical

information

Date/time

15

-

-

 

specimen

received