EVOLIS

EVOLIS
Connectivity Manual
Version 1.1
Date of issue February 2003
We reserve the right to make changes in the course of technical development
without previous notice.
EVOLIS, BIO-RAD. All rights reserved.

BIO-RAD
3, boulevard Raymond Poincar B.P. 3
92430 Marnes-la-Coquette, France
Neither this manual nor any parts of it may be duplicated or transmitted in any way without the
written approval of BIO-RAD.
Edition
Date: February 2003

Item No: 6300000052
Version: 1.1
EVOLIS System
Softwarecopyrights
Manufacturer:
STRATEC Biomedical Systems AG
Distributor:
BIO-RAD
The software for the EVOLIS has been licensed to BIO-RAD for worldwide
distribution. The EVOLIS software is the intellectual property of STRATEC
Biomedical Systems AG. Intellectual property rights shall remain with
STRATEC Biomedical Systems AG
You are entitled to use the EVOLIS software and the printed accompanying
material at your place of work only.
Any violations of property rights or copyright or trademark may be subject to
legal action.
Trademarks
MS-DOS and Windows 95/2000 are registered trademarks of Microsoft

Corporation.
BIO-RAD
3, boulevard Raymond Poincar B.P. 3
92430 Marnes-la-Coquette, France
tel: +33 (0)1 47 95 60 00
fax: +33 (0)1 47 41 91 33
Contents
Contents
1
Introduction ........................................................... 5
1.1
Purpose .................................................................................5
1.2
Scope ....................................................................................5
1.3
Connectivity...........................................................................5
1.4
ASTM Link Overview .............................................................5
1.5
Procedure..............................................................................6
ASTM Interface...................................................... 7
2.1
Setup .....................................................................................7
2.2
Low-Level Protocol................................................................8
2.2.1
Physical Layer................................................................................ 8
2.2.2
Data Link Layer.............................................................................. 8
2.3
Logical Structure of the Message Level Protocol ..................9
2.4
Incoming and Outgoing Transmission Examples ................10
2.4.1
Host to EVOLIS............................................................................ 10
2.4.2
Test Results ................................................................................. 11
2.4.3
EVOLIS to Host............................................................................ 11
2.5
Data Record Usage .............................................................13
2.5.1
Message Header Record ............................................................. 13
2.5.2
Patient Information Record .......................................................... 14
2.5.3
Test Order Record ....................................................................... 15
2.5.4
Result Record .............................................................................. 17
2.5.5
Comment Record......................................................................... 18
2.5.6
Request Information Record ........................................................ 18
2.5.7
Message Terminator Record ....................................................... 18
2.5.8
Scientific Record .......................................................................... 18
2.5.9
Manufacturer Information Record ................................................ 18
ASCII File Transfer .............................................. 20
3.1
Introduction..........................................................................20
3.2
Hardware Configurations.....................................................20
3.3
Manual Import of a Worklist.................................................20
EVOLIS - Connectivity Manual
Page 3
Contents
Page 4
3.3.1
Import a Worklist File ................................................................... 20
3.3.2
Examples of Import files............................................................... 23
3.4
Automatic Import of a Worklist File......................................24
3.4.1
File Polling ................................................................................... 24
3.4.2
Setup Polling................................................................................ 25
Export of files ...................................................... 26
4.1
Directory for Export Files .....................................................26
4.2
Assay Definition for Export ..................................................27
4.2.1
Available Header and Data Fields ............................................... 29
4.3
Examples of Export Files.....................................................30
1 Introduction
1.1 Purpose
Introduction
1.1
Purpose
To describe the various methods of importing and exporting information or

data for the EVOLIS software.
1.2
Scope
Document includes description for the ASTM link, and ASCII file exchanges.
1.3
Connectivity
The EVOLIS has been designed to easily integrate into a laboratory

environment. It provides a variety of connection methods for importing and
exporting data. Imported data is for ASCII patient information that allows the
system to create worklists and download of worklists. It is not possible to
import absorbance data, pipette data or other file types from other systems or
readers. Export data is for the patient results in a variety of formats; the
software supports a flexible format report structure, that can create ASCII files
as well as utilizing the ASTM link to up load patient results.
1.4
ASTM Link Overview
This section is intended to document the interface for exchanging information

between the EVOLIS instrument and a host computer.
Communication between the EVOLIS and an external host computer
consists of receiving test requests from the host and reporting results back to
the host. This is accomplished via an RS232 connection and follows the
ASTM 1394 (high level) and 1381 (low level) standards for communication.
The EVOLIS host interface consists of:
o
ASTM 1381 low-level transfer protocol used to transmit or receive

messages
Interpretation of received data from the intermediate files and entering

it into the EVOLIS database
The general procedure at the EVOLIS related to communication with an

external host, as well as the specific implementation of the ASTM standards
are described here.
The ASTM 1394 defines how the data to be transmitted is represented as a
structured message consisting of several records. These messages are then
translated into one or more frames that will actually be transmitted.
Page 5
1 Introduction
1.5 Procedure
1.5
Procedure
EVOLIS communication sessions with a host computer can be initiated on

request of the EVOLIS operator. An operator can upload test results on
request through a EVOLIS menu selection. The host may also send test
orders spontaneously.
When a sample is placed on the instrument, all tests previously ordered for the
sample at the host and downloaded to the EVOLIS will appear on the
EVOLIS 'Sample Loading Screen'. After a test is performed, the results
become available for transferring to the host computer. An operator can
upload results to the host.
Page 6
2 ASTM Interface
2.1 Setup
ASTM Interface
2.1
Setup
By means of the following Dialog the LIS interface can be customized:

1. ComPORT
This field specifies the serial port used for host

transmissions. This must be different to the system COM
Port.
2. BaudRate
Specifies the Baudrate used for transmissions between the

EVOLIS and the host any values from 110 to 56,000 can
be chosen. Default is 9600.
3. DataBits
7 or 8, default is 7.
4. StopBits
1, 1.5 or 2, default is 1.
5. Parity
None, odd, even, mark, space, default is None.
6. DateTemplate Must not be changed, in all cases, dates shall be recorded

in the YYYYMMDD format as required in the ASTM1394
standard.
7. TimeTemplate Must not be changed, in all cases, dates shall be recorded
in the HHMMSS format as required in the ASTM1394
standard.
8. Delimiters
These fields specify the set of delimiters used for

transmissions.
Table 2-1: Customizing

1. The ASTM setup screen can be accessed from Utilities | Options
menu.
2. Select the ASTM tab.
3. Check the entry 'Enable ASTM E 1381/1394 link to enable. The ASTM
E 1394 delimiters could be configured as well as the ASTM E 1381
communication ports.
4. Select the correct com ports.
PLEASE MAKE SURE, THAT YOU MUST NOT SELECT THE PORT USED TO CONNECT
THE PC TO THE ANALYZER.
Page 7
2 ASTM Interface
2.2 Low-Level Protocol
Figure 2-1: ASTM configuration
2.2
Low-Level Protocol
2.2.1
Physical Layer
Figure 2-2: RS232 Connection to Host
2.2.2
Data Link Layer
Establishment
Phase
Refer to ASTM 1381, Section 6.2 (see 2.6 Referenced Documents).
Transfer Phase

The checksum is encoded as two characters sent after the <ETB> or <ETX>
character. The checksum includes the first character after <STX> (the frame
number) up to and including <ETB> or <ETX>. It is computed by adding the
binary values of the characters, keeping the least significant eight bits of the
result.
Page 8
2 ASTM Interface
2.3 Logical Structure of the Message Level Protocol
During the transfer phase, if the LIS responds to a frame with an <EOT> the
EVOLIS does not stop transmitting and chooses to ignore the interrupt
request.
Termination
Phase
Error Recovery

After the EVOLIS transmits or receives the <EOT>, indicating that all
messages have been sent, the line is considered to be in the neutral state.
The EVOLIS checks every frame it receives to guarantee its validity and
sends an <ACK> for a valid frame, or a <NAK> for an invalid frame. Frames
are invalidated when:
o
Any character errors are detected (ie. parity error, framing error)
The frame checksum does not match the checksum computed on the
received frame.
The frame number is not the same as the last accepted frame or one
number higher.
When the EVOLIS receives a <NAK> for a frame rejected by a host it

resends the frame. If a single frame is sent and rejected six times, the
EVOLIS proceeds to the termination phase.
During the establishment phase, the EVOLIS expects to receive a reply
within 15 seconds after sending <ENQ>. During the transfer phase, the
EVOLIS expects to receive a reply within 15 seconds after transmitting the
last character of a frame. If a timeout occurs, the EVOLIS proceeds to the
termination phase.
During the transfer phase, the EVOLIS expects to receive a frame or <EOT>
within 30 seconds after first entering the transfer phase or replying to a frame.
After a timeout, the last incomplete message is discarded and the line is
considered to be in the neutral state. The EVOLIS will also timeout if a reply
to a frame is not received within 15 seconds.
2.3
Logical Structure of the Message Level

Protocol
The blocked stream of data sent between a host computer and the analyzer at
a given time is called a message.
Messages consist of a hierarchy of records of various types:
Level:
Segment Name:
Identifier (Record
TypeID):
Message Header Record
Message Terminator Record
Patient Information Record
Request Information Segment
Comments:
Page 9
2 ASTM Interface
2.4 Incoming and Outgoing Transmission Examples
Level:
Segment Name:
Identifier (Record
TypeID):
Comments:
Scientific Record
not allowed
for EVOLIS
Test Order Record
Result Record
Common Comment Record
Manufacturer Information
Record
not allowed
for EVOLIS
Table 2-2: Logical Structure of the Message Level Protocol

A record is identified by the first field of a record, the RecordTypeID. Most of
the various record types are related to each other in a definite hierarchy. A
lower level record may never appear without the preceding higher level record.
(Order records must be preceded by a patient record, result records must be
preceded by an order record... ) A sequence of records at one level is
terminated by the appearance of a record of the same or higher level. (In
some other descriptions a record might also be called segment.)
2.4
Incoming and Outgoing Transmission

Examples
2.4.1
Host to EVOLIS
Response from host includes patient demographics, patient ID, sample ID,
and test orders according to the following record hierarchy.
The response to requests for test orders is expected to be received within 10
seconds after the request has been sent.
Structure defined by ASTM 1394
(multiple records comprise a

single message)
(each record is sent as one or

more frames)

Patient Information Record 1
Test Order Record 1
:
Test Order Record n
:
Patient Information Record n
Test Order Record 1
:
Test Order Record n
Frame 1
:
Frame n

Table 2-3: Structure of ASTM 1394 and ASTM 1381
Page 10
2 ASTM Interface
In case there are no test orders available the LIS should respond with an
empty message containing header and terminator records only. The
terminator record should contain an I (no information available) flag in the
Termination Code Field.
S:<ENQ>
R:<ACK>
S:<STX>1H|\^&|||LaborEDV||||||||1|19941115202738<CR><ETX><CR>
<LF>
R:<ACK>
S:<STX>2P|1|PatID01|42670070||Meier^Anna||19741001|F|||||
MARTINEZ<CR><ETX><CR><LF>
R:<ACK>
S:<STX>3O|1|||^^^HBsAg||20011115|||||||||S||||||||||X<CR><ETX>
<CR><LF>
R:<ACK>
S:<STX>4P|1|PatID02|43681136||Mueller^Fritz||19941001|M|||||
R:<ACK>
<CR><LF>
R:<ACK>
S:<STX>6P|1|PatID03|43691135||Otto^Hans||19941001|M|||||
R:<ACK>
<CR><LF>
R:<ACK>
S:<STX>0P|1|PatID04|00102105||Mayer^John||19941001|M|||||
R:<ACK>
<CR><LF>
R:<ACK>
S:<STX>4L|1|N<CR><ETX><CR><LF>
R:<ACK>
S:<EOT>
Table 2-4: Example

After the EVOLIS receives all test orders from the host, the records are
interpreted. Valid test orders are entered into the load list database, while
invalid test orders are not.
2.4.2
Test Results
Only the final calculated result (Abs, concentration or interpretation) is

transferred per test. For multiple replicate results the mean is transmitted only.
2.4.3
EVOLIS to Host
Transmit sample information with corresponding tests and results.
Page 11
2 ASTM Interface
(multiple records comprise a

single message)
(each record is sent as one or

more frames)

Patient Information Record 1
Test Order Record 1
Result Record 1
Comment 1
:
Result Record n
Comment 1
:
Test Order Record n
Result Record 1
Comment 1
:
Result Record n
Comment 1
:
Patient Information Record n
Test Order Record 1
Result Record 1
Comment 1
:
Result Record n
Comment 1
:
Test Order Record n
Result Record 1
Comment 1
:
Result Record n
Comment 1
Frame 1
:
Frame n

Table 2-5: Structure of ASTM 1394 and ASTM 1381
R:<ENQ>
S:<ACK>
R:<STX>1H|\^&|||LaborEDV||||||||1|19941115202738
<CR>P|1|PatID01|42670070||Meir^Anna||19741001|F|||||MARTINEZ
<CR>O|1|||^^^HBsAg||20011115|||||||||S||||||||||X<CR>R|1||13.1|
IU/ml<CR>P|2|PatID02|43681136||Mueller^Fritz||19941001|M|||||
MARTINEZ<CR>O|1|||^^^HBsAg||20011115|||||||||S||||||||||X
<CR>R|1||132.1|IU/ml<CR>.
S:<ACK>
R:<STX>4L|1|N<CR><ETX><CR><LF>
S:<ACK>
R:<EOT>
Table 2-6: Example
Page 12
2 ASTM Interface
2.5 Data Record Usage
2.5
Data Record Usage
Refer to ASTM 1394, particularly Section 6 through 13 (see 2.6 Referenced

Documents).
Each record sent by the EVOLIS will contain up to the last field used by the
EVOLIS, which may or may not be all fields possible for the record. An O in
Required or Sent field indicates optional. The first <MaxLength> characters
are significant only. Any more characters transmitted for a specific field are
ignored.
2.5.1
Field ASTM Field

No.
Description
Valid
Max
Required
Contents Length
Record Type ID
Character
identifying the
record as a
message header
Delimiter Definition
Any received
delimiter set is
accepted.
The delimiters
defined in
ASTMSetupDialog
are sent.
Message Control
ID
Access Password
Sender Name / ID
Sender Street
Address
Reserved Field
Sender Telephone
No.
Characteristics of
Sender
10
Receiver ID
11
Comment
12
Processing ID
13
Version No.
14
Date and Time of

Message
20
1
Format is
YYYYMMDD
HHMMSS
14
Table 2-7: Message Header Record
Page 13
2 ASTM Interface
2.5.2
Page 14
Patient Information Record
Field ASTM Field

No.
Description
Valid
Max
Required
Contents Length
Record Type ID
Character
P
identifying the
record as a patient
information record
Sequence Number
Practice Assigned
Patient ID
Laboratory
Assigned Patient
ID
Patient ID No. 3
6^1
Patient Name
6^2
Patient First Name
Mother's Maiden
Name
Birthdate
Patient Sex
10
Patient Race Ethnic Origin
11
Patient Address
12
Reserved Field
13
Patient Telephone
Number
14
Attending
Physician ID
15
Special Field 1
16
Special Field 2
17
Patient Height
18
Patient Weight
19
Diagnosis
20
Active Medications
21
Diet
22
Practice Field No.

1
23
Practice Field No.

2
Becomes our
PatientID
Becomes our
SenderID
2 ASTM Interface
Field ASTM Field

No.
Description
Valid
Max
Required
Contents Length
24
Admission and
Discharge Dates
25
Admission Status
26
Location
27
Nature of
Alternative
Diagnostic Code
and Classifiers
28
Alternative
Diagnostic Code
and Classification
29
Religion
30
Marital Status
31
Isolation Status
32
Language
33
Hospital Service
34
Hospital Institution
35
Dosage Category
Table 2-8: Patient Information Record
2.5.3
Test Order Record
Field ASTM Field

No.
Description
Valid
Max
Required
Contents Length
Record Type ID
Character
identifying the
record as a test
order record
Sequence Number
Specimen ID
Instrument
Specimen ID
5^4
Universal Test ID
5^5
Dilution
Priority
Requested /
Ordered Date and
Time
Test Abbreviation
Page 15
2 ASTM Interface
Page 16
Field ASTM Field

No.
Description
Valid
Max
Required
Contents Length
Specimen
Collection Date
and Time
YYYYMMDDHHM
MSS
Collection End
Time
10
Collection Volume
11
Collector ID
12
Action Code
13
Danger Code
14
Relevant Clinical
Information
15
Date/Time
Specimen
Received
16
Specimen
Descriptor (Type)
17
Ordering Physician
18
Physicians
Telephone
Number
19
User Field No. 1
20
User Field No. 2
21
Laboratory Field
No. 1
22
Laboratory Field
No. 2
23
Date/Time Results
Reported or Last
Modified
24
Instrument Charge
to Computer
System
25
Instrument Section
ID
26
Report Types
27
Reserved Field
28
Location of Ward
of Specimen
Collection
14
2 ASTM Interface
Field ASTM Field

No.
Description
Valid
Max
Required
Contents Length
29
Nosocomial
Infection Flag
30
Specimen Service
31
Specimen
Institution
Table 2-9: Test Order Record
2.5.4
Result Record
PLEASE NOTE, THAT THE RESULT RECORD CAN JUST BE SEND ONCE TO THE HOST
COMPUTER.
PLEASE NOTE, THAT THE DATA VALUE IN FIELD NO. 4 INCLUDES ONLY THE FINAL
CALCULATED RESULT, DEPENDING ON THE ASSAY PROGRAMMATION .
Field ASTM Field
No.
Description
Record Type ID
Character
R
identifying the
record as a
result record
Sequence Number
Test ID
Data or
Measurement
Value
Units
Reference Ranges
Result Abnormal
Flags
Nature of
Abnormality
Testing
Result Status
10
Date of Change in
Instrument
Normative Values
or Units
Valid
Contents
Max
Length
Required
Final
calculated
result,
depends
on value
Page 17
2 ASTM Interface
Field ASTM Field

No.
Description
Valid
Contents
Max
Length
Required
11
Operator
Identification
12
Date/Time Test
Started
13
Date/Time Test
Completed
14
Instrument ID
Table 2-10: Result Record
2.5.5
Comment Record
Comment Records are used either to describe reasons for rejected test orders
or to supply additional result information, e.g. result relevant flags.
2.5.6
Request Information Record
Not applicable.
2.5.7
Field ASTM Field

No.
Description
Valid
Required Sent
Contents
Record Type ID
Character
identifying the
record as the last
record in the
message
2
3
Sequence Number
Termination Code
Table 2-11: Message Terminator Record
2.5.8
Scientific Record
A Scientific Record must not be sent
2.5.9
Manufacturer Information Record
A Manufacturer Information Record must not be sent
Page 18
2 ASTM Interface
2.6 Referenced Documents
2.6
ASTM
Standards
Referenced Documents
E 1381 Standard Specification for Low-Level Protocol to Transfer

Messages Between Clinical Laboratory Instruments and Computer
Systems (Annual Book of ASTM Standards, Vol 14.01.)
E 1394 Standard Specification for Transferring Information Between

Clinical Instruments and Computer Systems (Annual Book of ASTM
Standards, Vol 14.01.)
Page 19
3 ASCII File Transfer

3.1 Introduction
ASCII File Transfer

3.1
Introduction
The EVOLIS has the possibility to receive worklist files and transmit result
files from and to a network server. Both file formats (Import and Export) can be
defined within the EVOLIS software.
The import of worklist files can be performed manually by the user or
automatically with a polling sequence.
3.2
Hardware Configurations
The communication between the EVOLIS and the host system is established
using an Ethernet card.
In case that the EVOLIS computer should be connected to an other host
system, please install the necessary protocol or client and configure it
according to the specifications for this host.
FOR ALL TYPE OF SERVERS TAKE CARE OF FOLLOWING RESTRICTIONS:
THE FILE NAMES SHOULD NO BE LONGER THAN 20 CHARACTERS
DO NOT USE SPECIAL CHARACTERS IN THE FILE NAMES EXCEPT - AND _
CHARACTERS FOR FILE NAMES ALLOWED: NUMBERS FROM 0 TO 9 AND LETTERS
FROM A TO Z (SMALL AND BIG CAPITALS)
3.3
Manual Import of a Worklist
3.3.1
Import a Worklist File
1. Choose File | Open at the main menu of the EVOLIS software and the
file open dialog will be shown.
Page 20

3.3 Manual Import of a Worklist
Figure 3-1: Open import file

2. As file type "ASCII Patient Information (*.txt) must be selected.
3. The directory should be \\network_drive\EVOLIS\Import.
4. Select the worklist file (e.g. Import.txt) from the folder on the host.
5. Click on the Open button.
THE FILE FORMAT OF IMPORT.TXT IS DESCRIBED IN CHAPTER 3.3.2 EXAMPLES
OF IMPORT FILES.
The following window will be displayed:
Figure 3-2: ASCII Patient Information Import

This setup menu allows you to define the format of the files that you want to
import.
6. Select the entry 'Has Header Row' if the file has, as its first record the
heading labels.
Page 21

PLEASE NOTE, THAT THE HEADER LABELS MUST CONSISTS OF THE SAME
RECORDS AS SHOWN IN THE 'AVAILABLE FIELDS' LIST!
7. Select the entry 'Use Header Row to determine Mappings' or create
the 'Select Fields' box, if the header from the file should not be used to
determine mappings. The 'Selected fields' must be created in the
order they appear in the file.
8. Select the separator character. As default comma is defined.
9. Click on the OK button.
ONCE A PATIENT IMPORT SETTING HAS BEEN CREATED, IT CAN BE SAVED (SAVE
SETTINGS) FOR RE-USE (OPEN SETTINGS) LATER.
Patient ID
Alphanumeric strings accepted.
Patient Name
No limits on patient name
Birthdate
YYYYMMDD
Sex
ASTM states M, F, or U but no actual restrictions
Test name
Test name must correspond exactly to the assay protocol

stored in the Assay Protocol Files sub-directory default
C:\BioRad\Resources\Apf. E.g. CMV-IgG (no extension or
directory)
Collection
Date
YYYYMMDDHHMMSS
Table 3-1: Available fields to import.

If all settings have been done the file import is confirmed with a message.
Figure 3-3: Import message

THIS MESSAGE JUST CONFIRMS THAT THE FILE HAS BEEN IMPORTED THIS
MESSAGE DOES NOT CONFIRM THE CORRECT IMPORT OF ALL THE DATE FIELDS.
The imported information's are transferred into the EVOLIS Patient
management.
11. Chose Utilities | Patient Details' at the main menu of the EVOLIS
software.
Page 22

Figure 3-4: Patient editor with the imported worklist

IF YOU IMPORT AN OTHER WORKLIST THE EXISTING INFORMATION'S WILL NOT BE
OVERWRITTEN. NEW INFORMATION'S WILL BE ADDED TO THE EXISTING ONE.
3.3.2
Example 1
Examples of Import files
File:
Patient ID,Test name,Test name,Test name
AD001,CMV-IgG,HSV-IgG,RUB-IgG
AD002,CMV-IgG,HSV-IgG,RUB-IgG
BF056,CMV-IgG,HSV-IgG,RUB-IgG
RR008,CMV-IgG,HSV-IgG,RUB-IgG
RR015,CMV-IgG,HSV-IgG,RUB-IgG
Meaning:
First Line: Header Row (Separator ,)
Second Line: Data fields (Separator ,)
Table 3-2: File includes Patient ID and Test names
Page 23

3.4 Automatic Import of a Worklist File
Example 2
File:
Patient ID,Patient name,Test name,Test name,Test name,Test
name,Birthdate,Sex
AD001,Williams Mandy,CMV-IgG,HSV-IgG,RUB-IgG,,19710520,F
AD002,Graham Michael,CMV-IgG,HSV-IgG,RUB-IgG,TOX-IgG,19520815,M
BF056,Mulder Ken,CMV-IgG,HSV-IgG,RUB-IgG,TOX-IgG,19801208,M
RR008,Fox Judy,CMV-IgG,HSV-IgG,,,19750416,F
RR015,Black Bill,CMV-IgG,HSV-IgG,RUB-IgG,,19860904,M
Meaning:
First Line: Header Row (Separator ,)
Second Line: Data fields (Separator ,)
Table 3-3: File includes Patient ID, Test names and Details
IF A PATIENT DOES NOT HAVE ALL FIELDS WHICH ARE DEFINED IN THE HEADER
(E.G. PATIENT RR008 HAS JUST TWO TEST NAME), THE DATA FIELD MUST BE
EMPTY BUT SEPARATED VIA ,.
THIS MEANS:
NUMBER SEPARATORS HEADER FIELD = NUMBER SEPARATORS DATA FIELD
The Patient Editor (see Figure 3-4: Patient editor with the imported worklist)
represents the example file 2.
1. To show patient details select a Patient ID.
2. Click on the Edit button.
Figure 3-5: Patient Details
3.4
Automatic Import of a Worklist File
3.4.1
File Polling
The EVOLIS software allows the User to configure specific locations that the
software will poll looking for ASCII patient information files. When a valid file is
found, it is imported into the software, interpreted and the patient database
updated with the new patient details. The User determines the frequency the
software polls the specified directory.
Page 24

3.4 Automatic Import of a Worklist File
3.4.2
Setup Polling
1. Choose Utilities | Options at the main menu of the EVOLIS software.

2. Select the File Polling tab.
Figure 3-6: File polling configuration

3. To specify the ASCII file format click on the File Options button and
select the appropriate labels.
FILE OPTIONS IS THE SAME DIALOG WHEN USED MANUALLY FROM THE FILE | OPEN
MENU ITEM (SEE 3.3.1 IMPORT A WORKLIST FILE).
THE SYSTEM TIME OF THE SERVER AND THE SYSTEM TIME OF THE EVOLIS
COMPUTER MUST BE SYNCHRONIZED!
IF THE SYSTEM TIME OF THE SERVER IS BEHIND THE SYSTEM TIME OF THE
EVOLIS COMPUTER AND THEY DEVIATE MORE THAN THE DEFINED POLLING TIME
THE WORKLIST FILES WILL NEVER BE IMPORTED !
Page 25
4 Export of files
4.1 Directory for Export Files
Export of files
4.1
Directory for Export Files
The EVOLIS software allows the ASCII export of data.

The destination where the Export Files shall be transferred can be defined in
the options.
1. Choose Utilities | Options at the main menu of the EVOLIS software.
2. Select the Directories tab.
Figure 4-1: Present the directories

3. Select the file-type Export Files.
4. Click on the Browse button.
5. Select the target folder (default setting is C:\BioRad\Export).
7. Select a file or write a name (e.g. xxx) in the File name field.
DO NOT CHANGE THE TARGET FOLDER FOR THE RESULT FILES.
As soon as a result is available the software generates an ASCII file (*.txt)

which is than automatically transferred to the defined target folder.
Page 26
4 Export of files
4.2 Assay Definition for Export
If a file should be exported and the target file is not available, the following
message appears:
Figure 4-2: Error message

As soon as the communication is build up again, open the Result File in
EVOLIS (Subdirectory Result Files) once again and the Export File will be
generated and transferred automatically.
4.2
Assay Definition for Export
Within every assay definition you will find in the sub-category Read a report
section, which can be customized to the customer needs.
1. To set up or open the settings, click on the Read Step.
2. Double click on Report Settings.
Figure 4-3: Report Settings
Page 27
4 Export of files
PLEASE NOTE, THAT THE DEFAULT SETTING ONLY INCLUDES THE ASSAY HEADER
AND READER RESULTS. THE EXPORT FILE FORMAT CAN BE INDIVIDUALLY
CUSTOMIZED FOR EACH TEST ACCORDING TO THE CUSTOMER NEEDS.
3. Select the Export tab.
Figure 4-4: Export settings

4. Click on Settings... button.
Figure 4-5: Text file settings

The format can be table or matrix, normally a table format is used for ASCII
export.
Page 28
4 Export of files
Define the settings according to the customer needs from the available header
and data fields windows.
4.2.1
Available Header and Data Fields
Fields:
Meaning:
Assay Header
Date and time, OVER limit, operator and wavelengths
Kinetic readings
Raw data from each read
Validation criteria
QC evaluation
Qualitative
Qualitative QC, qualitative equations and notes
Quantitative
Quantitative notes
Patient ID
Patient ID
Assay
Assay name
Well Location
e.g. A1
Layout Label
e.g. T1
Flag
Clot detection, No liquid detected , etc.
Reader value
Reader value for that replicate
Reader mean
Averaged reader value across replicates
Reader SD
Standard Deviation of replicates
Reader CV
%co-efficient of variation of replicates
Reader SE
Standard Error of replicates
Reader units
Reader units
Qual. Value
As above, but for qualitative results
Qual. Mean
As above, but for qualitative results
Quant. 1 value
As above, but for 1st curve fit (quantitative)
Quant. 1 mean
Quant. 1 SD
Quant. 1 CV
Quant. 1 SE
Quant. 1 units
Spread. Value
As above, but for spreadsheet results
Spread. Mean
Spread. SD
Spread. CV
Spread. SE
Spred. Units
Page 29
4 Export of files
4.3 Examples of Export Files
Fields:
Meaning:
Quant. 2 value
As above, but for 2nd curve fit (quantitative)
Quant. 2 mean
Quant. 2 SD
Quant. 2 CV
Quant. 2 SE
Quant. 2 units
Table 4-1: Meaning of header and data fields
4.3
Example 1
Examples of Export Files
File:
Meaning:
[HSV-IgG]
No header information
[Results]
Patient ID,Assay,Reader value,Qual. value
"","HSV-IgG","0.009","NC1"
"","HSV-IgG","0.011","NC2"
"","HSV-IgG","0.093","NC3"
"","HSV-IgG","1.455","PC1"
"","HSV-IgG","1.465","PC2
"AD001","HSV-IgG","0.004","neg"
"AD002","HSV-IgG","0.075","equ"
"BF056","HSV-IgG","0.011","neg"
"RR008","HSV-IgG","0.002","neg"
"RR015","HSV-IgG","0.987","pos"
Data field header

separated via ,
Table 4-2: Export Files without Header Fields defined
Page 30
4 Export of files
4.3 Examples of Export Files
Example 2
File:
Meaning:
[HSV-IgG]
Time:;11:15:00
Date:;27/09/00
OVER limit:;3.000
Operator:;User
Wavelengths:;450nm/620nm
Assay Header Field
-0.01<=NCi<=0.50;-0.01<=0.010<=0.50
;-0.01<=0.009<=0.50
;-0.01<=0.011<=0.50
;-0.01<=0.093<=0.50;Removed
Valid(NC)>=2;2>=2
PCi>=0.550;1.460>=0.55
;1.455>=0.55
;1.465>=0.55
valid(PC)=2;2=2
Validation Criteria
Header Field
If 'Sample<(NC+0.05)*0.9' Then Result:='neg' Qualitative Header

Field
If 'Sample>=(NC+0.05)*1.1' Then
Result:='pos'
Default result := equ
cut off;(NC + 0.055);0.060
[Results]
Patient ID,Assay,Reader value,Qual. value
"","HSV-IgG","0.009","NC1"
"","HSV-IgG","0.011","NC2"
"","HSV-IgG","0.093","NC3"
"","HSV-IgG","1.455","PC1"
"","HSV-IgG","1.465","PC2
"AD001","HSV-IgG","0.004","neg"
"AD002","HSV-IgG","0.075","equ"
"BF056","HSV-IgG","0.011","neg"
"RR008","HSV-IgG","0.002","neg"
"RR015","HSV-IgG","0.987","pos"
Data field header

separated via ,
Table 4-3: Export Files with Header Fields defined
Page 31

EVOLIS - Connectivity Manual 1 1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EVOLIS - Connectivity Manual 1 1

Uploaded by

Copyright:

Available Formats

EVOLIS, BIO-RAD. All rights reserved.

Date: February 2003

STRATEC Biomedical Systems AG

MS-DOS and Windows 95/2000 are registered trademarks of Microsoft

ASTM Link Overview .............................................................5

Data Link Layer.............................................................................. 8

Logical Structure of the Message Level Protocol ..................9

Incoming and Outgoing Transmission Examples ................10

Test Results ................................................................................. 11

Data Record Usage .............................................................13

Message Header Record ............................................................. 13

Patient Information Record .......................................................... 14

Test Order Record ....................................................................... 15

Result Record .............................................................................. 17

Request Information Record ........................................................ 18

Message Terminator Record ....................................................... 18

Scientific Record .......................................................................... 18

Manufacturer Information Record ................................................ 18

ASCII File Transfer .............................................. 20

Manual Import of a Worklist.................................................20

EVOLIS - Connectivity Manual

Import a Worklist File ................................................................... 20

Examples of Import files............................................................... 23

Automatic Import of a Worklist File......................................24

File Polling ................................................................................... 24

Export of files ...................................................... 26

Directory for Export Files .....................................................26

Assay Definition for Export ..................................................27

Available Header and Data Fields ............................................... 29

Examples of Export Files.....................................................30

EVOLIS - Connectivity Manual

To describe the various methods of importing and exporting information or

The EVOLIS has been designed to easily integrate into a laboratory

ASTM Link Overview

This section is intended to document the interface for exchanging information

ASTM 1381 low-level transfer protocol used to transmit or receive

Interpretation of received data from the intermediate files and entering

The general procedure at the EVOLIS related to communication with an

EVOLIS - Connectivity Manual

EVOLIS communication sessions with a host computer can be initiated on

EVOLIS - Connectivity Manual

By means of the following Dialog the LIS interface can be customized:

This field specifies the serial port used for host

Specifies the Baudrate used for transmissions between the

None, odd, even, mark, space, default is None.

6. DateTemplate Must not be changed, in all cases, dates shall be recorded

These fields specify the set of delimiters used for

Table 2-1: Customizing

EVOLIS - Connectivity Manual

Figure 2-1: ASTM configuration

Figure 2-2: RS232 Connection to Host

Data Link Layer

Refer to ASTM 1381, Section 6.2 (see 2.6 Referenced Documents).

Refer to ASTM 1381, Section 6.3 (see 2.6 Referenced Documents).

EVOLIS - Connectivity Manual

Refer to ASTM 1381, Section 6.4 (see 2.6 Referenced Documents).

When the EVOLIS receives a <NAK> for a frame rejected by a host it

Logical Structure of the Message Level

Message Header Record

Message Terminator Record

Patient Information Record

Request Information Segment

EVOLIS - Connectivity Manual