7/24/2019 Konelab 20i http://slidepdf.com/reader/full/konelab-20i 1/58 KONELAB LIMS AND LAS INTERFACES Code: 895304-4301 Manual version: G Date: 23.4.2003 The CE mark attached on Konelab indicates the conformity with the EMC (electromagnetic compatibility) directive 89/336/EC. Thermo Clinical Labsystems Ratastie 2, P.O. Box 100 FIN-01621 VANTAA, Finland Tel.: +358 9 802 766 Fax: +358 9 8027 6300 www.thermo.com/konelab Information in this manual is subject to change without prior notice.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 1/58
KONELAB
LIMS AND LASINTERFACES
Code: 895304-4301
Manual version: G
Date: 23.4.2003
The CE mark attached on Konelab indicates the conformity with
the EMC (electromagnetic compatibility) directive 89/336/EC.
Thermo Clinical LabsystemsRatastie 2, P.O. Box 100FIN-01621 VANTAA, Finland
Tel.: +358 9 802 766Fax: +358 9 8027 6300
www.thermo.com/konelab
Information in this manual is subject to change withoutprior notice.
2.1 BI-DIRECTIONAL MODE ...............................................................................................................42.1.1 COMMUNICATION RECORDS ................................................................................................5
2.1.1.1 INITIALISATION RECORDS..............................................................................................................52.1.1.2 PATIENT INFORMATION RECORD ...................... ....................... ...................... ....................... .......6
2.1.1.3 SAMPLE INFORMATION RECORD ..................................................................................................72.1.1.4 TEST ANALYSIS RECORD ................................................................................................................7
2.1.1.5 RESULT RECORD................................................................................................................................82.1.1.6 FINISHING RECORD...........................................................................................................................8
2.1.3 DATA VALIDITY CHECK........................................................................................................142.1.3.1 CHECK SUM ......................................................................................................................................14
2.1.4 TIMING REQUIREMENTS......................................................................................................142.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.........................................................................182.2.6 ENQUIRING TESTS IN USE IN THE ANALYSER ..................................................................19
2.3.2 RESULT ERROR CODES.........................................................................................................21
2.3.3 COMMUNICATION ERROR CODES......................................................................................21
2.3.4 ON LINE ERROR CODES........................................................................................................222.3.5 EXAMPLES OF ERROR HANDLING......................................................................................24
2.4 REQUESTING A CALCULATED TEST .......................................................................................25
3.2 ASTM IN K ONELAB ..........................................................................................................................28
3.2.1 ASTM 1394 – 91 STRUCTURE OF MESSAGES .....................................................................283.2.1.1 Header record (level 0).................. .................... ..................... .................... ....................... ................... 283.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) ....................................................................................................................313.2.1.5 Result record (level 3) ..........................................................................................................................333.2.1.6 Comment record (level 4) used with the Result Record.......... ..................... ..................... ................... 353.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
4.2 GENERAL DESCRIPTION.............................................................................................................44
4.2.1 MESSAGE RECORD FORMAT ...............................................................................................444.2.2 CALCULATION OF CHECKSUM...........................................................................................45
4.2.3 SEQUENCE FOR INITIALISING THE COMMUNICATION INTERFACE............................46
4.3.6 SAMPLE DISPENSING COMPLETE RECORD......................................................................514.3.7 REINITIALISE COMMUNICATION RECORD .......................................................................51
4.4 COMMUNICATION EXAMPLES .................................................................................................52
The Konelab LIMS hardware interface works through serial communication channel.
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.
LIMS Configuration
Main window
F8/F1
Configuration
Configuration
F7
LIMSConfiguration
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 5/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 2
The signals needed at the Konelab end of cable
Pin 2 Receive Data
Pin 3 Transmit Data
Pin 5 Ground
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 isinstalled. 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.
The cable should be
made according to the
documentation of LIMS
system in use.
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.
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 6/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 3
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 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 newsample 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.
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.
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 7/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 4
2. Konelab ONLINE (=KONE
ONLINE) PROTOCOL
2.1 BI-DIRECTIONAL MODE
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.
The analyser is always
acting as co-operator
and the computer is the
host.
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 8/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 5
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/
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 9/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 6
INITIALISATION RECORD 7
This record is used when a laboratory computer wishes to know which tests exist on
the database of the analyser.
: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 section2.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/
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 thepatient is accepted in
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 10/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 7
2.1.1.3 SAMPLE INFORMATION RECORD
:S:ii..i/pn/pp/st/nn/dd..d/tt..t/rrr/n or o/C/
S - identifies the record to be a sample
information record
ii..i - sample identification (up to 16 characters)
pn - sample segment number (up to 2 characters)
pp - sample segment position (up to 3 characters)
st - sample type (up to 2 characters)
nn - sample note data e.g. icteric (ic),
haemolysed (HE), a user defined character
code, handled only as an information string
(up to 2 characters)
dd..d - collection date, a user defined character
code, handled only as an information string
(up to 8 characters)
tt..t - collection time, a user defined character
code, handled only as an information string
(up to 5 characters)
rrr - dilution ratio (format is 1 + rrr) (up to 3 characters)
n or o - new/old (1 character)
C - check sum, refer to section 2.1.3.1.
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
yy..y,etc
- test identification (up to 8 characters)
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,
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:
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 - identifies the record to be an error record
xx..x - communication error code, refer to section 2.3.3 (up to 30 characters)
LABORATORY COMPUTER ANALYSER
(Initialization record 1)(CR)(LF)
(ACK)
(Patient info record)(CR)(LF)
(ACK)
(Sample info record)(CR)(LF)
(ACK)
(Test analysis record)(CR)(LF)- error in this record
(Error record)(CR)(LF)
(ACK)
(Finishing record)(CR)(LF)
(ACK)
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 24/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 21
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 electrodewas 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 CODESERROR 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
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 25/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 22
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 causesE.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.
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 26/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 23
405 SYNCRONIZATION ERROR (LIMS)
The analyser received a data record1 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.
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 27/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 24
2.3.5 EXAMPLES OF ERROR HANDLING
INVALID CHECK SUM
ERROR IN DATA TRANSMITTED
LABORATORY COMPUTER ANALYSER
:I:PR2/?/
NAK
:I:PR2/@/
ACK
The check sum in thefirst message was
incorrect, so the
analyser requested the
message to be sent
again.
LABORATORY COMPUTER ANALYSER
:I:PR2/@/
ACK
:S:126///SE//97-12-18/12:13/0/N/O/
ACK
:A:XXX/PROT/@/
:E:105;XXX /A/
ACK
:F:PR/+/
ACK
The analyser does not
recognise XXX as a valid
test id and so it sends
error message 105 which
the computer
acknowledges. The
computer would
probably now try to send
the other tests for
samples and inform theuser of the problem.
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 28/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 25
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 latestintroduced samples. If it doesn't success in that it uses the older ones.
The following requirements for requesting calculated tests
online must be fulfilled:
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.
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
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.
When a calculated
(patient) test has been
requested there must
be a PR1-record or thepatient must have been
introduced in the
Patient entry window
in the user interface.
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 30/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 27
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
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 31/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 28
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
ID
1 X X Always H. Starts every message. Note: no
delimiter between the first and the second
field
Delimiter
definition
2 X X Field, repeat, component and escape
delimiters
Message
control ID
3 - -
Access
password
4 - -
Sender name
or ID
5 -
-
-
X
X
X
Instrument type 60/30/20
^instrument ID InstrumentData.iId
^software version Get_version ?
Sender streetaddress
6 - -
Reserved
field
7 - -
Sender
telephone
number
8 - -
Characteristic
s of sender
9 - -
Receiver ID 10 - -
Comment or
special
instructions
11 - -
Processing
ID
12 X
X
X
X
X
X
X
X
P –production
T –training
D –debugging
Q –QC
Version No. 13 - -
Date and time
of message
14 - (X) Form YYYYMMDDHHMMSS. Only in
debug mode
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 32/58
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 33/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 30
Patient height 17 - -
Patient weight 18 - -
Patient’s known
or suspected
diagnosis
19 - -
Patient activemedications
20 - -
Patient’s diet 21 - -
Practice field 1 22 - -
Practice field 2 23 - -
Admission or
discharge dates
24 - -
Admission
status
25 - -
Location 26 (X) (X) SenderData.sID
Native of alternative
diagnostic code
and classifiers
27 - -
Alternative
diagnostic code
and
classification
28 - -
Patient religion 29 - -
Marital status 30 - -
Isolation status 31 - -
Language 32 - -
Hospital
service
33 - -
Hospital
institution
34 - -
Dosage
category
35 - -
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 34/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 31
3.2.1.4 Test order record (level 2)
Field Name No Host Instr. Comment
Record type ID 1 X X Always O.
Sequence
number
2 X X Running number within Patient
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.ucPositionIf 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
specimen ID
4 - -
Universal test
ID
5 -
-
-
X
-
-
-
-
X
X
Universal test ID
^universal test name
^universal test ID type
^manufacturer defined test code
TestData.sOnlineName^auto-dilution factor
Multiple tests can be ordered separated by
repeat delimiter.
Priority 6 (X)
(X)
(X)
-
-
(X)
(X)
(X)
-
-
S –stat REQ_PRIOR_STAT
A –asap REQ_PRIOR_ASAP
R –routine REQ_PRIOR_NORMAL
C –callback
P –preoperative
*.ucPriority
Optional if no sample or sample is
calibrator or control.
Requested/ordered date and
time
7 - -
Specimen
collection date
and time
8 (X) (X) Form YYYYMMDDHHMMSS
PatientSampleData.sCollectionInfo
Collection end
time
9 - -
Collection
volume
10 - -
Collector ID 11 - -
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 isalways seen.
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 35/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 32
Action code 12 X
X
X
-
-
-
X
X
-
-
X
-
X
X
C –cancel
A –add test requests to existing specimen
N –new test requests + new specimen
P –pending specimen
L –reserved
X –specimen or test in process
Q –QC specimenMultiple action codes can be given
separated by repeat delimiter. For example
X\Q.
Danger code 13 - -
Relevant
clinical
information
14 (X) (X) PatientSampleData.osComment
Date/time
specimen
received
15 - -
Specimen
descriptor (typeand source)
16 X
-
X
-
Type
^SourceType is coded as: 1 –Serum, 2 –Plasma, 3
–Urine, 4 –CSF, 5 –Other
PatientSampleData.ucSampleType
Ordering
physician
17 - -
Physicians
telephone
number
18 - -
User field No.1 19 - -
User field No.2 20 - -
Laboratory field No.1
21 - -
Laboratory field
No.2
22 - -
Date/time
results reported
or last modified
23 - -
Instrument
charge to
computer
system
24 - -
Instrument
section ID
25 (X) (X) Optional if no sample. InstrumentData.iId
Report types 26 X
-
-
X
X
-
-
-
X
-
-
X
X
X
X
X
X
X
O –order
C –correction to previously transmitted
results
P –preliminary results
F –final results
X –requests cancelled
I –in instrument pending
Y –no order for test (response to query)
Z –no record of this patient (response to
query)
Q –response to query (info)
Multiple report types can be given
separated by repeat delimiter. For exampleY\Z.
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 36/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 33
Reserved field 27 - -
Location or
ward of
specimen
collection
28 - -
Nosocomialinfection flag 29 - -
Specimen
service
30 - -
Specimen
institution
31 - -
3.2.1.5 Result record (level 3)
Field Name No Host Instr. Comment
Record type ID 1 X X Always R.
Sequencenumber 2 X X Running number within Test order.Starts with 1.
Universal test
ID
3 -
-
-
X
(X)
-
-
-
X
X
Universal test ID
^universal test name
^universal test ID type
^manufacturer defined test code
TestData.sOnlineName
^dilution factor used in calculation
Data or
measurement
value
4 X (X) If result status is X (cancelled) or result
is UNSTABLE, no result is given.
*.fResult
The range of result will be [99999.9 …
0.00000] and [-0.00000 … -99999.9]. If
actual result exceeds these values, thenearest value will be shown.
Units 5 X X TestData.sResultUnit
Reference
ranges
6
-
-
-
X
X
-
Components:
Low
TRCLimitsData.fLowerlimit
^High
TRCLimitsData.fUpperlimit
^Description
Result
abnormal flags
7 -
-
-
-
-
-
X
X
X
X/-
-
-
L/H –below/above normal
LL/HH –below/above panic normal
</> -below/above absolute low/high (off
the scale of instrument) N/A –normal/abnormal
U/D –significant change up/down (delta)
B/W –better/worse (used when direction
is not relevant)
*.ulErrorFlags
Nature of
abnormality
testing
8 - -
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 37/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 34
Result status 9 -
-
X
-
-
-
--
-
-
-
-
X
X
X
X
-
-X
-
X
-
C –correction
P –preliminary
F –final
X –cancelled,
I –pending
S –partial
M –MIC levelR –reported
N –contains necessary information to run a
new order
Q –response to query
V –verified
Multiple status flags can be given separated
by repeat delimiter. For example F\Q.
REQ_ASKED ~ I, REQ_FIXABLE ~ I
REQ_FIXED ~ I , REQ_CALCULATED
~ P, REQ_MEASURED ~ P,
REQ_XXX_ACC ~ F, REQ_XXX_REJ ~X
Date of change
in instrument
normative
values or units
10 - -
Operator
identification
11 - (X) User login name if User levels have been
set on
Date/time test
started
12 - -
Date/time test
completed
13 (X) (X) Form YYYYMMDDHHMMSS. No value
if test is not completed. *.iResultDateTime
Instrument
identification
14 - X InstrumentData.iId
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 38/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 35
3.2.1.6 Comment record (level 4) used with the Result Record
Field Name No Host Instr. Comment
Record type ID 1 - X Always C. Used to transfer instrument
flags after Result record.
Sequence Number
2 - X Always 1, because of the use.
Comment
source
3 -
-
-
-
-
X
P –practice
L –computer system
I –clinical instrument system
Comment text 4 - X Error condition identified with a number
and a text in English
1 Init abs.
2 Bichr. net abs.
3 Linearity
4 Unstable
5 Instr, error
6 Addl. meas. error
7 Sample blank error
8 Dil. limit low
9 Dil. limit high
10 Test limit low
11 Test limit high
12 Antigen limit high
13 Out of limit
14 QC
15 Calc. error
16 Outlier
17 Cut curve
18 Bias corr. limit
19 Antigen limit low20 AE meas error
21 Blank resp. low
22 Blank resp. high
23 Blank init abs. low
24 Blank init abs. High
25 Critical limit low
26 Critical limit high
27 Instrument abs. Limit
28 Not measurable
Multiple flags can be given separated
with repeat delimiter.
*.ulErrorFlags
Comment type 5 --
-
-
-
--
-
-
X
G –generic/free text documentT –test name comment
P –positive test comment
N –negative test comment
I –instrument flag(s) comment
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 39/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 36
3.2.1.7 Comment record (level 3) used with transmission
related error conditions
Field Name No Host Instr. Comment
Record type ID 1 - X Always C. Used to transfer instrument
flags after Result record.Sequence
Number
2 - X Always 1, because of the use.
Comment
source
3 -
-
-
-
-
X
P –practice
L –computer system
I –clinical instrument system
Comment text 4 - X Error condition identified by 'E' followed
by a number
E3 - wrong initialising character in
record
E4 - wrong termination code or
request code in record
E5 - records found in wrong order E104 - sample position already
reserved in analyzer by another
sample or calibrator or control.
The new sample was wrongly
positioned by LIS. Use position
0^0 for any sample when the
position is defined at a later
moment with sample insertion
into the Konelab.
E105 - problems with analysis request,
request could not be created
E108 - Maximum number of samples/
patient exceededE210 - problems with updating patient
information
E211 - patient information could not be
found
E220 - . Sample already exists
E221 - problems with sample
information
Comment type 5 -
-
-
-
-
X
-
-
-
-
G –generic/free text document
T –test name comment
P –positive test comment
N –negative test comment
I –instrument flag(s) comment
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 40/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 37
3.2.1.8 Request information record (level 1)
Field Name No Host Instr. Comment
Record type ID 1 X X Always Q. Used by Instrument to ask
external test results or orders to new
samples, and by host for requestingresults and orders that are in
instrument’s database.
Sequence
number
2 X X Always 1. Only one request may be
outstanding at a time.
Starting range
ID number
3 (X)
(X)
(X)
(X)
(X)
(X)
(X)
(X)
patient ID or ALL
^ sample ID or ALL
^segment
^position
Patient ID and sample ID are text fields,
so field is not used as range. Multiple
patients or samples can be requested
separated by repeat delimiter.
Ending range
ID number
4 - -
Universal test
ID
5 -
-
-
(X)
-
-
-
-
(X)
-
Universal test ID
^universal test name
^universal test ID type
^manufacturer defined test code
TestData.sOnlineName
^auto-dilution factor
Multiple tests can be requested separated
by repeat delimiter.
Nature of
request time
limits
6 -
(X)
-
(X)
S –specimen collect date
R result test date
According to standard R is taken asdefault, so it is optional.
Beginning
request results
date and time
7 (X) (X) Form YYYYMMDDHHMMSS
Ending request
results date and
time
8 (X) (X) Form YYYYMMDDHHMMSS
Requesting
physician name
9 - -
Requesting
physician
telephone
number
10 - -
User field No.1 11 - -
User field No.2 12 - -
Request
information
status codes
13 -
X
X
X
X
-
-
X
-
-
X
X
X
X
-
-
X
-
C –correction
P –preliminary
F –final
X –cancelled
I –pending
S –unfinalized results
M –MIC level,
R –previously transmitted
A –cancel last request criteria
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 41/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 38
X
X
-
X
X
-
N –requesting new or edited results only,
O –requesting test orders only (no
results)
D –requesting demographics only
Note: not repeated.
3.2.2 FIELD LENGTHS USED BY Konelab
Field Length in charactersInstrument type 3
instrument ID 2
software version 16
Date and time of message 14
Laboratory assigned patient ID 16
Patient name 24
Date of birth 8
Patient sex 10Hospital institution 24
Specimen ID 16
Instrument specimen ID Segment , Position integers max 6
characters
Universal test ID 30
Specimen collection date and time 14
Relevant clinical information 30
Instrument section ID 2
Data or measurement value 8
Units 10
Reference ranges Low 6, High 6
Date/time test completed 14Beginning request results date and
time
14
Ending request results date and time 14
7/24/2019 Konelab 20i
http://slidepdf.com/reader/full/konelab-20i 42/58
LIMS AND LAS INTERFACES
Konelab
23.04.03
895304-4301 39
3.2.3 EXAMPLES OF COMMUNICATION
BETWEEN Konelab AND THE HOST
COMPUTER
Examples of transmissions between Konelab and the host computer, when Konelab
is configured to use automatic sample ID sending and automatic result sending. Thecontrol characters are presented between '<>'. For example <enq> means an ASCII
character ENQ which hexadecimal value is 05. These examples give only an
overview, the actual communication may vary.
1) New sample is introduced to Konelab. Example of the