Addendum Eng

Addendum
EUROLineScan
EUROIMMUN Medizinische Labordiagnostika AG • 23560 Lübeck (Germany) • Seekamp 31 • Phone +49 451 2032 0
Copyright and Trademark
All contents of this document, particularly images, are protected by copyright.

The copyright owner is EUROIMMUN, unless otherwise specified.
This document may not be duplicated, printed, copied or reproduced in any
other way, and not given to a third party unless explicitly authorised in writing
by EUROIMMUN.
Trademarks or product names mentioned in this document refer to companies
that are laying claim to those trademarks and product names. The trademarks
or product names which do not belong to EUROIMMUN are exclusively used
in the context of the description of this product.
Revision
The descriptions and other information, the images and drawings are
constantly revised and adjusted. In some details, the images may differ
slightly from the product (e.g. from the actual design). However, these
deviations have no influence on the safe use of the product.
Product version
Software version ...................................................................................... 3.4
Document information
Document number ...................................................... YG_0006_A_UK_Z03

Last revised ................................................................................ 12/05/2021
Print format ........................................................................................ DIN A4
Translation of the original Addendum to the instructions for use
Publisher:
EUROIMMUN Medizinische Labordiagnostika AG
Seekamp 31
23560 Lübeck, Germany
Telephone: +49 451 2032 0
Fax: +49 451 2032 100
Internet: www.euroimmun.com
Addendum • EUROLineScan 3
4 Addendum • EUROLineScan
Table of contents
1 Introduction ............................................................................................................................ 7
Further documents ............................................................................................................ 7
Changes to this manual .................................................................................................... 7
Typographic conventions .................................................................................................. 7
Symbols ............................................................................................................................ 7
2 Dealing with software errors ................................................................................................. 8

Licence restriction ............................................................................................................. 8
Technical service .............................................................................................................. 8
3 Safety ...................................................................................................................................... 9
Intended use ..................................................................................................................... 9
EUROLineScan features................................................................................................... 9
System requirements ...................................................................................................... 10
General safety instructions.............................................................................................. 10
User qualification ............................................................................................................ 10
4 Connection ........................................................................................................................... 11
GDT format ..................................................................................................................... 11
4.1.1 Structure of the requirements file............................................................................................. 11
4.1.2 Importing the requirements ...................................................................................................... 13
4.1.3 Selective import ....................................................................................................................... 14
4.1.4 Structure of the result file ......................................................................................................... 15
4.1.5 Settings for the GDT format ..................................................................................................... 17
Text format ..................................................................................................................... 20
4.2.1 Structure of the requirements file............................................................................................. 20
4.2.2 Structure of the result file ......................................................................................................... 21
4.2.3 Text format settings ................................................................................................................. 21
ASTM format .................................................................................................................. 24
4.3.1 Structure of an ASTM transmission ......................................................................................... 24
4.3.2 Data set specifications ............................................................................................................. 27
4.3.3 Importing the requirements ...................................................................................................... 33
4.3.4 Export of the results ................................................................................................................. 34
4.3.5 Settings for the ASTM format .................................................................................................. 35
Replacement filter ........................................................................................................... 38
List of abbreviations ........................................................................................................ 40
5 Network installation ............................................................................................................. 42
6 Database management ........................................................................................................ 43

DataSourceManager ....................................................................................................... 43
6.1.1 Editing a database connection................................................................................................. 44
6.1.2 Creating a new database connection ...................................................................................... 47
6.1.3 Importing a Firebird database .................................................................................................. 47
6.1.4 Using Embedded Firebird ........................................................................................................ 47
7 Import and export of protocols ........................................................................................... 48
From EUROLineScan ..................................................................................................... 48
ImpEx ............................................................................................................................. 50
7.2.1 Export protocols ....................................................................................................................... 50
7.2.2 Import protocols ....................................................................................................................... 52
7.2.3 Export Lots ............................................................................................................................... 52
7.2.4 Import lots ................................................................................................................................ 53
File upload ...................................................................................................................... 54
8 Data backup ......................................................................................................................... 56

Manual backup ............................................................................................................... 56
ImpEx ............................................................................................................................. 56
9 Data migration...................................................................................................................... 57
Copying the data using ImpEx ........................................................................................ 57
Replacing the database file ............................................................................................. 57
Adding a new data source .............................................................................................. 57
10 List of figures ................................................................................................................... 58
11 List of tables ..................................................................................................................... 59
1 Introduction
This document is intended for the user and describes how to use
EUROLineScan safely and correctly.
Information on warranty and liability, as well as safety information and detailed
instructions for use of the EUROLineScan software can be found in the
instructions for use.
Read and familiarise yourself with this document and keep it for the entire
lifetime of the product.
Further documents
The following quick reference guides are available for this product:
 Instructions for use EUROLineScan (YG_0006_A_UK_CXX)
 EUROLineScan Quick guide database installation (YG_0006_A_UK_TXX)
 Network installation EUROLineScan (YG_0006_A_UK_UXX)
 Quick guide EUROLineScan calibration (YG_0006_A_UK_VXX)
 Quick guide ImpEx Software (YG_0006_A_UK_Xxx)
 EUROLineScan: Step-by-step application (YG_0006_A_UK_YXX)
Changes to this manual

The present version of the addendum to the EUROLineScan software is a
completely revised version. Therefore, changes to the previous version are
not indicated.
Typographic conventions
Some categories of terms in this manual are highlighted for clarity.
Operating elements ..................................................................... ON/OFF , File
Window, Register .......................................................................... “Protocol“
Symbols
You will find various symbols in the software and in this document.
Symbol Explanation
Manufacturer
Note
Observe instructions for use
Tab. 1 Other symbols
2 Dealing with software errors
Licence restriction
The licensee is not permitted to make changes to the software or have them
made by third parties, to perform reverse engineering, to decompile the
EUROIMMUN software or to attempt to determine the source code in any
other way. The source code remains property of EUROIMMUN at all times.
Technical service
In case of problems, please contact your local distributor.
3 Safety
Intended use
The EUROLineScan program is used for the digital evaluation of EUROLINE
and Westernblot test strips from EUROIMMUN for the detection of antibodies
in allergies, autoimmune diseases and infectious diseases. In addition to the
evaluation and the output of findings, the EUROLineScan program
automatically creates a patient archive.
Findings generated by the EUROLineScan program must always be checked
for accuracy. EUROIMMUN accepts liability for the findings produced by
means of the EUROLineScan software exclusively within the framework of the
Medical Devices Act. All clinical and serological data must be taken into
account when making a diagnosis.
We assume that the operating personnel compare the band patterns of each
blot strip with the reactions recorded by the program and displayed on the
results page and in this way ensure the correctness of the results.
EUROLineScan features
Automatic evaluation of membrane-based test:
For all EUROIMMUN blot systems: EUROLINE, EUROLINE-WB,
Westernblot,
Autoimmune , infection and allergy diagnostics (incl. Allergy EUROASSAY),
EUROBlotCamera: Digitisation of strips while still in the incubation channel,
EUROBlotScanner: Digitisation of the strips by flatbed scanner,
EUROBlotOne: Fully automated processing of immunoblot tests,
Fully automated identification, quantification and registration of bands,
Possibility of adding findings by the specialist staff (obligatory logging of
modifications),
Complete findings within a few minutes after the end of incubation,
Fully automated administration and documentation of the individual data,
Electronic archiving of all images and data (eliminates the need to store the
potentially infectious blot strips).
The EUROLineScan system was created by EUROIMMUN to evaluate
membrane-based test systems quantitatively and fully automatically, to
facilitate the administration of the individual data and to document the results
in detail, all of which previously took a lot of time. For this purpose, the
incubated membrane strips are optically recorded by means of a flatbed
scanner on a protocol sheet (EUROBlotScanner) or with a camera system
while still in the incubation channel (EUROBlotCamera or EUROBlotOne).
The EUROLineScan software independently detects the bands contained in
the protocol and automatically corrects minor errors caused by inaccurate
positioning of the bands. It then identifies the bands and measures their
intensity.
The automatic evaluation can be controlled and it is possible to add to the
data manually, with all changes automatically logged. Finally, the results are
stored together with the image data.
It is no longer necessary to archive potentially infectious incubated test strips.
A separate report sheet can be created for each patient. EUROIMMUN will be
happy to assist with the integration of the EUROLineScan program into an
already existing EDP environment.
System requirements
Computer: Pentium 350 MHz or higher or compatible with Windows XP,
Windows Vista, Windows 7, Windows 8 or Windows 10, 512 MB RAM, about 1
GB hard disk space (for installation only about 120 MB, the rest for graphics
and patient data), graphics resolution 1024 x 768 or better.
Flatbed scanner: CanoScan LiDE series, at least 300 dpi; recommended:
600 dpi
Camera system: For capturing the membrane strips directly in the incubation
tray; only available from EUROIMMUN
Printer: Commercially available simple printer (sufficient for printing of findings
and protocols)
Barcode scanner: Symbol DS6707, Zebra DS8108, Honeywell Xenon 1900
(only for allergy EUROASSAY).
General safety instructions

 The EUROLineScan software has been developed according to the
current state of the art in compliance with the requirements of EC
Directive 98/79/EC for in vitro diagnostic medical devices.
 The software may only be used in accordance with its intended purpose.
 Observe the instructions in the software and the safety instructions,
warnings and precautions listed in this manual.
 The software may only be used by trained and qualified personnel.
 Familiarise yourself with the software before using it.
 Keep these instructions for use near the software workstation so that they
are accessible at all times.
 If the software is not used as intended, the protective measures of the
software may be ineffective.
 Configurations may only be carried out by trained and authorised
EUROIMMUN technicians.
 If the PC on which the EUROLineScan software is installed has a network
connection, the use of regularly updated anti-virus software is
recommended.
 To secure the program database, it is strongly recommended to change
the default password for the Firebird database administrator “SYSDBA”.
Please ensure beforehand that none of the other programs installed on
the system is affected by this change.
User qualification
The software may only be used by instructed persons who have been trained
in its use and in the respective area of application.
4 Connection
The EUROLineScan program offers you the possibility to exchange
requirement and result data with a laboratory information or management
system. Various file-based exchange formats are available for this purpose.
The most common of these formats are described in the following chapters.
To establish such a connection, first select the file format to be used in the
settings menu of EUROLineScan (section “Connection”).
Figure 1 - Selection of the connection format
After you have decided on a format, you can now make further format-specific
settings. These are briefly explained in the course of the description of the
respective connection formats.
GDT format
EUROLineScan implements parts of the GDT format (Device Data Transfer),
a standardised interface for data exchange between laboratory EDP systems
and medical devices. An official interface description can be found at the
following address:
http://www.qms-standards.de/standards/gdt-schnittstelle
In the following sections, the basic structure of the import and export files as
well as the configuration options available for the GDT format are explained in
detail.
4.1.1 Structure of the requirements file
Note
A GDT file contains all information relevant to EUROLineScan for a patient

sample. If several requests are to be transferred at the same time, a
separate GDT file must be created for each sample.
Each line of a requirements file is structured according to the following

scheme:
LLLFFFF[D]
LLL: The total length of the line; this is a three-digit numerical value which
is padded with leading zeros if necessary. The length includes all characters
of the line including the length itself and two characters for CR/LF.
FFFF: A four-digit field identifier that indicates what type of value is
transmitted in this line. The meaning of each field identifier can be found in
the GDT specification, but the fields implemented by EUROLineScan are
explained in more detail at the end of this section.
[D]: A variable length string containing the actual user data.
This will be explained with a short example. Let the following line be given:
0193101Mustermann
The first three characters indicate that the entire line contains 19 characters
(17 + CF/LF). “3101” is the identifier of the field “patient’s surname” (see
below) and finally “Mustermann” is the name to be transmitted.
A header is to be inserted at the beginning of each GDT file, which contains
meta-information about the file:
01380006302
014810000255
014921802.10
These three mandatory lines are in detail:
1) Field 8000: The record type, i.e. the type of file present. EUROLineScan
uses record type 6302, “Request test”, when importing requests.
2) Field 8100: The record length. This denotes the total length of the file, i.e.
the sum of all line lengths. In this example, the record length is 255
characters and has been padded with leading zeros to 5 digits.
3) The GDT version. EUROLineScan implements version 02.10.
Furthermore, the GDT format offers the possibility to define free categories,
i.e. application-specific fields. These are stored in the field numbers 6300 ff.
and consist of two lines each, the first of which contains the identifier of the
free category and the second (with a field number higher by 1) the actual user
data, e.g.:
0206330 Laboratory number
0226331 Example laboratory
When importing request files, EUROLineScan implements the following fields
of the GDT specification:
Field Explanation
8000 Record type (6302)
8100 Set length
9218 GDT version
3000 Patient ID
3101 Last name of the patient
3102 First name of the patient
3103 Date of birth of the patient in the format “DDMMYYYY”
Field Explanation
8410 Test identification. This value contains the abbreviation of the

test to be performed with this strip (see chapter 7.1)
8402 Device-specific map (optional). Can be used in EUROLineScan

as an alternative to field 8410.
6330 Contains the character string “Labornummer”.
6331 Laboratory number; alphanumeric, maximum 32 characters.
6332 Contains the character string “Einsender”
6333 Name of the sender of the sample; alphanumeric, maximum 32

characters.
6334 Contains the string “Einsenderdatum”
6335 Date of sample receipt in the format “DDMMYYY”.
6336 Contains the character string “SID”
6337 Contains the designation of the test kit used; alphanumeric,

maximum 24 characters
Table 1 - GDT format, field identifiers (import)
Bold fields are mandatory and must be included in the request file. All other
entries are optional.
4.1.2 Importing the requirements

In the default setting, all .GDT files are read in from the import path (“read
directory”) in alphabetical order. Should you wish to deviate from this scheme,
you will find further information in Chapter 4.1.3, “Selective Import”.
Note
Before a request list can be imported, the desired connection format must
be selected (cf. section 1).
To perform an import, create a new protocol and then click the Import button.
Figure 2 - Import of a request list
All GDT files stored in the read directory are then imported (up to a maximum
of 48), whereby a new strip is created in the current protocol for each imported
file. All data contained in the request file are automatically transferred to the
protocol input form.
Figure 3 - Overview of imported requirements
If errors occur during the import, you will be shown a corresponding warning.
Nevertheless, the program will try to import all those parts of the requirement
that can be recognised as error-free and clearly assigned. Thus you have the
possibility to correct the imported values manually and continue with the
evaluation.
Figure 4 - Error when importing a request
After completing the import and making any corrections or additions, click on
the Save button to save the protocol in the database.
4.1.3 Selective import

Selective import is an alternative procedure for importing GDT request files, in
which the entire contents of the read directory are not imported, but you can
specifically select the required files.
To use the selective import, please activate the option of the same name in
the section “GDT” of the settings menu. If you now click on “Import” in the
protocol input window, the following dialogue opens:
Figure 5 - Selective import
All request files found in the read directory are listed here. For easier
assignment, EUROLineScan already reads out basic information such as the
patient ID and the examination to be performed and displays it in the overview
table.
By marking the Import option in the first column of the table, you can mark the
respective request file for import.
Files in which an error was already found when reading out the basic
information are highlighted in yellow. In this case, by clicking on the
respective entry, you will receive a list of all problems found in the “Warnings”
field.
Figure 6 - Information on faulty request file
After selecting all the request files to be imported, confirm with OK.
4.1.4 Structure of the result file

Analogous to the import of requirements, EUROLineScan offers you the
possibility to export the results of the evaluations carried out. The basic
structure of the results file is identical to the requirements files described in
chapter 4.1.1.
However, numerous new fields are added in which the actual evaluation
results are transferred. The structure of a results file is briefly explained
below:
At the beginning of the file there is again a header, as already described in
chapter 4.1.1. This is supplemented by the field 0103, the name of the
software with which the evaluation was carried out. The header of a result file
could therefore look like this:
01380006310
014810001849
014921802.10
0210103EUROLineScan
This header contains the following information:
 The record type used is 6310 (“Transmit data of an examination”).
 The result file is 1849 characters long.
 The GDT version is again 02.10
 The evaluation result was created with EUROLineScan.
Subsequently, the patient data and evaluation results are transmitted in the
following fields:
Field Explanation
3000 Patient ID
8402 Type of results transmitted. For EUROLineScan this is “ALLG00”.
6200 Date of protocol generation in the format “DDMMYYY”.
6201 Time of protocol generation in the format “HHMMSS”.
6330 Always contains the string “PRT/STR” for “protocol/strip”
6331 Protocol ID/strip number, e.g. 39/12 for protocol ID 39, strip 12.
The strip number starts at 0.
6332 Contains the string “Laboratory number”.
6333 Laboratory number; alphanumeric, maximum 32 characters.
6334 Contains the character string “sender”
6335 Name of the sender of the sample; alphanumeric, maximum 32
characters
6336 Contains the string “date of sender”
6337 Date of sample receipt in the format “DDMMYYY”.
6338 Contains the character string “strip number”
6339 The name of the strip optionally stored during protocol generation;
alphanumeric, maximum 24 characters
6340 Contains the character string “Test kit”
6341 Contains the designation of the test kit used; alphanumeric,
maximum 24 characters
8410 Abbreviation of the test performed (see chapter 7.1)
8411 Full name of the test performed (see chapter 7.1)
8432 Date of protocol incubation in the format “DDMMYYY”.
8439 Time of protocol incubation in the format “HHMMSS”
8480 Overall result of the strip in text form (e.g. “Positive”, “Negative”,
“Borderline”). If a strip has several overall results, these are
marked by name and output in several lines, e.g.:
0228480 HSV 1 positive
0228480 HSV 2 negative
This field is also used to transfer the results of the individual bands
(see following table).
Table 2 - GDT format, field identifiers (export)
The following structure is then used to transfer the band results (once for
each band):
Field Explanation
8410 Band abbreviation
8411 Full name of the band
8420 The determined intensity or concentration value
Field Explanation
8421 The type of result transmitted in field 8420; either “intensity” or
“kU/l” (for concentration).
8480 The actual band result, e.g. (“o”, “(+)”, “+” etc.)
8470 The ratio (= quantitative evaluation result) of the band in the
format “Ratio:XX,X” (“XX,X” = numerical value with one decimal
place). If the ratio for the respective band is not defined or could
not be determined, the string “Ratio:-“ is transmitted. is
transmitted.
This field is only included in the export file if the option “Export
quantitative result” has been activated in the section “GDT” of the
EUROLineScan settings menu.
Table 3 - GDT format, field identifiers (export of band results)
4.1.5 Settings for the GDT format

EUROLineScan offers you various settings to adjust the behaviour of the GDT
connection according to your wishes. These are explained below:
Figure 7 - Settings for GDT connection
Setting Explanation
“Read directory”: The directory from which
EUROLineScan reads in request files.
“Write directory”: The directory in which EUROLineScan
stores the result files.
“Band result test ident without Disables the output of the examination
examination”: abbreviation before each transmitted
antigen.
“Do not check record length” Prevents a warning from being issued if
the number of characters specified in
field 8100 does not match the actual
length of the file.
“Output concentrations instead If activated, the concentration value is
of intensities if possible”: output in field 8480 instead of the
intensity, if defined for the
corresponding examination.
“Delete file after import”: Specifies whether successfully imported
request files should be deleted after
saving the protocol.
“Apply replacement filter”: If this option is activated, the previously
defined replacement filters are applied
when importing and exporting GDT files
(cf. chapter 4.4)
“Export striped images”: If activated, the captured strip images
are also stored in the write directory
when exporting the results. The image
format selected in the "Program" section
is used here; the file name corresponds
to that of the results file, e.g.
"Sub001.gdt" <-> "Sub001.png".
“Selective import”: Specifies whether to use the selective
requirement import function described in
chapter 4.1.3
“Export corrected intensities”: If a band result was corrected manually
by the user, the originally measured
intensity that may no longer match the
new band result is exported by default.
This setting can be used to specify that
an intensity value in the middle of the
intensity range applicable to the new
result level is output instead.
“Export quantitative result”: If this setting is activated, the ratio
(quantitative band result) is exported to
field 8470 (see chapter 4.1.4).
Otherwise, this field is omitted without
replacement.
Setting Explanation
“Disable warning for long/non- The GDT format provides for patient IDs
numeric patient IDs”: that consist exclusively of digits and are
a maximum of 10 characters long. If one
of these conditions is violated,
EUROLineScan issues a corresponding
warning when exporting the results,
which can be deactivated with this
setting.
“Disable warning for long/non- The GDT format provides for patient IDs
numeric patient IDs”: that consist exclusively of digits and are
a maximum of 10 characters long. If one
of these conditions is violated,
EUROLineScan issues a corresponding
warning when exporting the results,
which can be deactivated with this
setting.
"Disable warning for unknown If the request file contains a field that is
field types": not known to EUROLineScan, the field
is ignored and a corresponding warning
is issued. With this setting the warning
can be deactivated.
"Export patient gender": If activated, the sex of the patient is
output in field 3110::
Value Meaning
0 Unknown
1 Male
2 Female
“Separate files for each strip If an examination has several overall
result”: results (e.g. HSV, EBV), you can use
this setting to specify that a separate
results file is output for each of the
results.
These files differ only in the overall
result field (8480) and are otherwise
identical.
“Round intensity values”: If activated, intensity values are written
to the export file rounded to whole
numbers, regardless of the number of
decimal places selected in
EUROLineScan.
“Use suffix for inhibited strips”: If activated, strips treated with anti-CCD
absorbent (ZD 3001) are identified by
appending the suffix "_#abs" to the
examination designation (field 8410).
“Use numeric file extensions”: If this option is activated, not only files
with the extension ".gdt" are taken into
account when searching for request
files, but also those files whose
extension consists exclusively of
numbers.
Setting Explanation
“Export file name”: Defines the scheme according to which
the exported result files are named.
Table 4 - Settings for the GDT format
Text format
The text format is a simple and flexible way to exchange data with other
programs. The content and structure of the import and export files can be
individually defined by the user.
4.2.1 Structure of the requirements file

In the default setting, only the abbreviation of the examination to be
performed and the ID of the patient are read from the request file. Therefore,
a minimal request file could, for example, only consist of the following line:
ELBG;Pat1
When importing this file, a single strip is created with the examination
“Borrelia EUROLINE IgG” (abbreviation “ELMG”, see chapter 4.5); the patient
ID is “Pat1”. These two pieces of information are already sufficient for the
evaluation of such a strip, but optionally further information can be transferred
in the request file.
For example, it is possible to also import the patient's name and date of birth:
ELBG;Pat1;Mustermann, Monica;03.07.1975
All other data fields behave in the same way.
Note
If changes are made to the structure of the request file, the EUROLineScan
configuration must always be adapted accordingly.
For the above example, the following configuration would be selected:
Figure 8 - Exemplary settings for the text format
Furthermore, it is possible to transfer several requests within one file. Each

request is in a new line and is interpreted by EUROLineScan as a new strip
within the imported protocol.
The above example could be extended as follows:
ELBG;Pat1;Mustermann, Monica;03.07.1975
ELBG;Pat2;Mustermann, Martin;27.01.1973
ELBG;Pat3;Mustermann, Max;12.12.1999
When importing this file, three strips would be created in the protocol, again
each with the examination “Borrelia EUROLINE IgG”.
4.2.2 Structure of the result file
The results file is identical in its basic structure to the request file, with the
addition of the actual evaluation results.
ELBG;Pat1;Mustermann, Monica;03.07.1975;positive;Et o[0];Ko +[136]; [usw.]
Here, the evaluation results were exported for one of the requests transferred
in the previous section.
After the examination and patient data, the overall result of the strip (in this
case “positive”) is output first. It should be noted, however, that a strip does
not necessarily have to have an overall result and this entry can therefore
also be omitted. Conversely, a strip can also have several such results; in this
case, these are marked by name (e.g. “HSV 1 positive ;HSV 2 positive;”).
The results of the individual strips are then transferred. In the above example,
only the first three bands of the strip are listed for the sake of clarity. A band
result always follows the same format:
Ko +[136]
Here “Ko” is the name of the band, “+” the band result determined by the
program and 136 the measured band intensity. Please note that the band
name and band result are separated by a space.
If a concentration value exists for the respective band and the option “Also
export concentrations” is in the settings menu, this value is output after the
band intensity, separated by a slash.
m6 1[4/0,47] Band m6, result level 1, intensity 4,
concentration 0.47
The export of the ratio behaves analogously if the option “Export quantitative
result” is selected.
M2 +++[153/13.9] Band M2, result level +++, intensity 153, ratio
13.9
If both options (export of concentration and ratio) are activated, both values
are written into the export file. The value that does not apply (ratio for allergy
profiles, concentration for infection and autoantibody examinations) is deleted
by a “-“. The first of the two values is the concentration, the second value is
the ratio.
M2 +++[153/-/13.9] Band M2, result level +++, intensity 153,
Concentration not applicable, ratio 13.9
resp.
m6 1[4/0.47/-] Band m6, result level 1, intensity 4,
Concentration 0.47, ratio not applicable
When exporting a protocol, a separate line is created in the result file for each
strip, so that the results of several strips are usually transferred in a single file:
ELBG;Pat1;Mustermann, Monica;03.07.1975;positive;Et o[0];Ko +[136]; [etc.]
ELBG;Pat2;Mustermann, Martin;27.01.1973;negative;Et o[0];Ko +[140]; [etc.]
4.2.3 Text format settings

Since the text format, unlike the GDT format, is not standardised, the desired
file structure must first be defined. The following settings are available for this
purpose:
Figure 9 - Text format settings
Setting Explanation
“Import file/ Specifies which data EUROLineScan reads from the
Export file”: import file or writes to the export file. By marking the
corresponding entry you can mark a value for import;
here the order of the data is important. Therefore,
you can use the “Arrow up” and “Arrow down”
buttons to move the selected entry up or down in the
list to determine the desired order.
“Date Format”: Specifies the format in which date values are
transmitted. The default setting “dd.mm.yyyy”
corresponds to the common German date format,
e.g. “11.12.2020”.
“Import Path”: The path from which the request files are loaded.
“Export path”: The path to which the result files are written.
Setting Explanation
“Export mode”: Manual
The export must be triggered manually by clicking
the Export button in the results overview. The target
file can be freely selected by the user. The initial
path of the file selection dialogue is the last path
opened in such a dialogue.
Use default path

As “Manual”, whereby the output path here is the
directory entered under “Export path”.
Automatic export – Run name as file name

When clicking the “Export” button, EUROLineScan
creates the result file without any further user action
being necessary. The export path set is used as the
target directory, the file name is the name of the
selected protocol. If a file with this name already
exists, it will be overwritten.
Automatic export – Consecutively numbered

Even with this setting, the result files are
automatically saved in the set export path. However,
the exported files are numbered consecutively,
starting with 0.
“File extension”: Specifies the file extension with which the export files
are provided.
“Text in quotation With this setting you can determine that the
marks”: individual data fields are not only separated from
each other by the selected separator (see below),
but also enclosed in inverted commas. This is
particularly advisable if each of the available
separators occurs frequently in your user data.
“Export striped If this option is activated, in addition to the actual
image as well”: result file, the captured strip images are also stored
in the export directory. The file name is identical to
that of the export file, but has the extension “.bmp”. If
a protocol includes several strips, the individual
strips are numbered consecutively, starting with 0.
“Also export If this setting is selected, not only the intensity value
concentration”: but also the concentration value of each band (if
available) is written to the export file.
“Export corrected If a band result was corrected manually by the user,
intensities”: the originally measured intensity that may no longer
match the new band result is exported by default.
This setting can be used to specify that an intensity
value in the middle of the intensity range applicable
to the new result level is output instead.
“Delete file after Specifies whether to delete successfully imported
import”: request files after saving the log.
Setting Explanation
“Investigation With this setting you can determine whether the
abbreviation before designation of the individual bands in the export file
band name”: should be preceded by the abbreviation of the
corresponding examination.
If this option is selected, the antigen “p21” from the
examination “EUROLine Borrelia IgG” (abbreviation
“ELBG”), for example, is transferred as “ELBGp21”.
Otherwise, only the band abbreviation (in this case
“p21”) is transmitted.
“Apply replacement If this option is activated, the previously defined
filter”: replacement filters are applied during import and
export (cf. chapter 4.4)
“Round intensity If activated, intensity values are written to the export
values”: file rounded to whole numbers, regardless of the
number of decimal places selected in
EUROLineScan.
“Use suffix for When activated, strips treated with anti-CCD
inhibited strips”: absorbent (ZD 3001) are identified by appending the
suffix “_#abs” to the examination designation.
“Separator”: Allows you to select which character should be used
to separate the individual data fields. It is
recommended to select a character that does not
occur in the data you enter (e.g. protocol and patient
data).
“Band results”: Determines which values are exported for each
band. The results are output in square brackets and
separated by slashes in the order “intensity /
concentration / ratio”:
m6 3[18/5.49/-]
If a value is not defined for the respective
examination, a “-“ is output instead.
Table 5 - Text format settings
ASTM format
ASTM International (American Society for Testing and Materials) has
established an extensive collection of standards for various applications.
EUROLineScan implements the ASTM E1394 standard for communication
between clinical instruments and computer systems.
In the standard setting, communication takes place via the TCP/IP interface.
Alternatively, file-based communication is possible (see below).
4.3.1 Structure of an ASTM transmission

Each requirement consists of several records, called “records” in ASTM. In
addition, various control characters are used to regulate the communication.
The individual elements of an ASTM transmission are explained below:
Records
ASTM E1394 recognises the following record types:
Record Code Description
Header H Initialises the communication; each request starts
with a header record.
Query Q Sent by EUROLineScan to the LIS, which is
requested to start transmitting information. Mainly
used to initiate the import of a worklist into
EUROLineScan.
Patient P Contains information about a patient. This record is
followed by one or more Order Records.
Order O Specifies the examinations to be performed for the
assigned patient
Result R Sent by EUROLineScan to the LIS and contains the
evaluation results.
Terminator L Informs the communication partner that all data have
been transmitted. Each request ends with a
terminator record.
Table 6 - ASTM requirement, field identifiers
Control characters
The control characters described below are used to indicate the beginning or
end of a transmission or to confirm receipt of a transmitted data set:
Code Hex Decimal Description
<ENQ> 05 5 Instructs the receiver to prepare to accept
information. This is usually the first character
transmitted during a communication process.
<ACK> 06 6 Transmitted in response to a control character
or data set. Indicates that the message has
been received and understood.
<NAK> 15 21 Transmitted in response to a control character
or record. Indicates that the message was
incomplete or not understood. This normally
causes the last transmitted data set to be sent
again.
<STX> 02 2 Indicates that a record (see above) is
transmitted after this control code.
<ETX> 03 3 Indicates the end of a record.
<CR> 0D 13 Carriage return. Indicates the end of a record
together with <ETX>.
<LF> 0A 10 Line break
<EOT> 04 4 Indicates the end of communication ("End of
transmission").
Table 7 - ASTM connection, control characters
Separator
Separators are special characters that appear within a data field and
determine how the receiving system processes the data:
Name Separator Description
Record Carriage return Indicates the end of a record
separator
Field separator Pipe (“|”) Separates the individual fields within a
record (see section “Record
specifications”).
Repeat Backslash (“\”) Marks repeating data within a field.
separator
Component Caret (“^”) Separates the individual components of a
separator composite field, e.g.
FIRSTNAME]^[SURNAME]" for the patient
name.
Masking Ampersand Used to mask separators contained in the
separator (“&”) user data. Informs the receiving system
that the following character is part of the
user data and is not to be interpreted as a
separator.
Table 8 - ASTM connection, separator
Checksums and command counters

As an additional security mechanism, ASTM E1394 allows the use of
checksums and command counters in each record. This allows the receiving
system to detect missing records or records transmitted in the wrong order.
This will be briefly explained in the following example:
<STX>1H|\^&|||EUROLineScan|||||||||<ETX>FD<LF>
This is a header record (see below). The two values printed in bold are
relevant here:
The 1 represents the so-called command counter. The first transmitted data
record receives the number 1; this is increased by 1 for each subsequent data
record until the value 7 is reached. Then the counter starts again at the value
0. This results in the following sequence:
1, 2, 3, 4, 5, 6, 7, 0, 1, 2, 3, 4, 5, 6, 7, 0 …
The value FD, on the other hand, is a check digit that the receiver can use to
verify the correctness and completeness of the data. This corresponds to the
sum of the ASCII values of all the characters in the data set except the control
codes and the checksums themselves. So in the above example, the
checksums would be calculated based on the following characters:
1H|\^&|||EUROLineScan|||||||||
The sum of all ASCII values (in this example 3069) modulo 256 results in an
8-bit integer value (here: 253), which is then output as a hexadecimal value.
When receiving the message, the receiver calculates this checksum again
and compares it with the checksum that the sender attached to the message.
If both values match, the recipient can assume that the message was
transmitted without errors.
4.3.2 Data set specifications
Each record consists of several data fields. The field separator “|” is used to
delimit the individual fields from each other, i.e.:
Field 1|Field 2|Field 3|Field 4
If no data is transmitted in a field, it is left blank. For example, if field 3 in the
above example contained no data, the following would be transmitted:
Field 1|Field 2||Field 4
It should be noted here that the field separator must be transmitted even if the
field does not contain any data (hence the double pipe character in the
example above).
Header record
Example: H|\^&|||EUROLineScan|||||||P|3.4.24|20180601112504
Lfd. No. Field name Description
1 Record type Specifies the type of record; for header
records this is always the value “H”.
2 Separator Indicates which separators (see chapter
4.3.1.3) are used in this transmission.
Default value: “\^&”
3 Control ID Currently not used
4 Password Currently not used
5 Sender Name The name of the software or device from
which the present record was sent.
6 Address of sender Currently not used
7 Reserved field Currently not used
8 Phone number of the Currently not used
sender
9 Characteristics of the Currently not used
sender
10 Recipient ID Currently not used
11 Comment Currently not used
12 Processing ID Always left at the default value “P”, which
indicates that the recipient is to process the
message.
13 Version number The version number of the system from
which the present record was sent.
14 Date of transmission Date and time at which the message was
sent. Format: “YYYYMMDDHHMMSS”.
That means the message in the example
above was transmitted on 01 June 2018 at
11:25:04.
Table 9 - ASTM, Header record
Patient record
Example:
P|1|1105999999|567894||MUSTERMANN^MAX||19580214|M|||||||||||||||||||||||||||
1 Record type Indicates the type of record; for patient
records this is always the value “P”.
2 Sequence number If several patients are transferred in one
request, this field indicates the sequence
number of the current patient in the list
(starting from 1).
3 Practice ID The number used by the requesting doctor
to identify the patient. EUROLineScan
enters this value in the “Patient ID” field.
4 Laboratory ID The number used by the processing
laboratory to identify the patient.
EUROLineScan enters this value in the field
“Laboratory number”.
5 Tertiary Patient ID Currently not used
6 Patient name In the format SURNAME^FIRST NAME
7 Mother's maiden Currently not used
name
8 Date of birth The patient’s date of birth in the format
“YYYYMMDDHHMMSS”.
9 Gender “M” for male, “F” for female, “U” for
unknown
10 Ethnicity of patient Currently not used
11 Patient address Currently not used
13 Patient's telephone Currently not used
number
14 Responsible doctor Currently not used
15 Special field Currently not used
16 Special field Currently not used
17 Patient size Currently not used
18 Patient weight Currently not used
19 Diagnosis Currently not used
20 Medication Currently not used
21 Dietary restrictions Currently not used
22 Practice field Currently not used
23 Practice field Currently not used
24 Date of admission Currently not used
and discharge
25 Referral status Currently not used
26 Location of the Currently not used
patient
27 Diagnostic code Currently not used
28 Diagnostic code Currently not used
29 Religious affiliation Currently not used
30 Marital status Currently not used
31 Isolation status Currently not used
32 Languages spoken Currently not used
33 Hospital Service Currently not used
34 Hospital Institute Currently not used
35 Dosage Currently not used
Table 10 - ASTM, Patient record
Test Order record

Example: O|1|1105999999||^^^464^^^^B^Â5|||||||N||||||||||||||

1 Record type Indicates the type of record; for order
records this is always the value “O”.
2 Sequence number If several test are transmitted in one
request, this field indicates the sequence
number of the current examination in the list
(starting from 1).
3 Sample number ID of the sample with which the test is to be
performed. Must match the patient ID of the
associated patient record.
4 Sample ID in the Currently not used
unit
5 Exam ID Indicates which test is to be performed.
Format:
^^^[EUROLINEScan-
ID]^^^^B^^[EUROLineScan-Code]
Note: The IDs and codes can be viewed in
EUROLineScan under “Help” ->
“Examinations”.
6 Priority Currently not used
7 Date of request Currently not used
8 Date of removal Currently not used
9 Date of the last Currently not used
removal
10 Extraction volume Currently not used
11 ID of the person Currently not used
taking the sample
12 Action Specifies which type of examination is to be
performed. Default value: “N” for “New test”.
13 Labelling of Currently not used
dangerous samples
14 Clinical information Currently not used
15 Sample input Currently not used
16 Sample description Currently not used
17 ID of the requesting Currently not used
doctor
18 Telephone number Currently not used
of the requesting
doctor
19 User field Currently not used
21 Lab field Currently not used
22 Lab field Currently not used
23 Request deadline Currently not used
24 Unit Loading Currently not used
Information
25 Device section Currently not used
26 Report type Currently not used
28 Sample storage Currently not used
location
29 Identification of Currently not used
nosocomial infection
30 Specimen service Currently not used
31 Specimen institution Currently not used
Table 11 - ASTM, Order record
Query record
Example: Q|1|ALL||ALL||||||||O

1 Record type Indicates the type of record; for query
records this is always the value “Q”.
2 Sequence number If multiple requests are transmitted, this
field indicates the sequence number of the
current request in the list (starting from 1).
3 Sample ID start The first sample ID for which examinations
are requested. To receive all open
requests, transmit the string “ALL”.
4 Sample ID end The last sample ID for which examinations
are requested.
5 Sample ID The ID of a specific examination for which
open requirements are to be transmitted. To
receive all requirements, transmit the string
“ALL”.
6 Time limit Currently not used
7 Start time Currently not used
8 End time Currently not used
9 Name of the doctor Currently not used
10 Doctor's telephone Currently not used
number
13 Status code Always contains the character “O”
Table 12 - ASTM, Query record
Result record
Example: R|8|^^^38^^^^B^0^Jo|o|||N||F||MUSTERMANN^DR. MANFRED|||

1 Record type Indicates the type of record; for result
records this is always the value ”R”.
2 Sequence number If several results are transmitted, this field
indicates the sequence number of the
current result in the list (starting from 1).
3 Exam ID Indicates which test was performed.
Format:
^^^[EUROLINEScan-ID]^^^^B^^0^[Band
name]
In the example above, the examination ID is
38 (examination Ana1b), the band name is
“Jo”.
Note: The IDs and codes can be viewed in
EUROLineScan under “Help” ->
“Examinations”.
4 Result The actual evaluation result; in this case
the result is negative (“o”).
Note: It is also possible to transmit the
intensity or concentration values of the
individual bands. For more information, see
the section “Format strings”.
5 Unit of the Currently not used
measured value
6 Reference range Currently not used
7 Unusual result Always the “N” sign
8 Description of the Currently not used
deviation
9 Status of the result Always the character “F” (“Final result”)
10 Date of last change Currently not used
11 Evaluated by Corresponds to the field of the same name
in EUROLineScan. Names are transmitted
in the format [SURNAME]^[FIRST NAME].
12 Start of processing Currently not used
13 End of processing Currently not used
Table 13 - ASTM, Result record
Terminator record
Example: L|1|N
Lfd.
Field name Description
No.
1 Record type Indicates the type of record; for terminator records this
is always the value “L”.
2 Sequence Normally number 1, as usually only one terminator
number record is transmitted.
3 Closing Always the “N” sign
code
Table 14 - ASTM, Terminator record
4.3.3 Importing the requirements
The following table shows an example of communication when importing a
worklist from LIS into EUROLineScan.
Here, an arrow pointing to the right () indicates a message sent from
EUROLineScan to the LIS. Conversely, an arrow pointing to the left ()
indicates a message sent from the LIS to EUROLineScan.
Message

<ENQ>

<ACK>

<STX>1H|\^&|||EUROLineScan|||||||P|3.4.24|20180601140316<ETX>3
<LF>

<ACK>

<STX>2Q|1|ALL||ALL||||||||O<ETX>95<LF>

<ACK>

<STX>3L|1|N<ETX>D3<LF>

<ACK>

<EOT>
Table 15 - ASTM, Example of import of a requirement, part 1
With this transmission, communication was established. EUROLineScan

initiated the communication with an <ENQ> control character (acknowledged
by the LIS with <ACK>) followed by a header record.
In the following query record, “ALL” is transmitted as sample and examination
ID, i.e. all open requests are to be sent by the LIS.
EUROLineScan then transmits the Terminator Record and ends the
transmission with an <EOT> signal. It then waits for the LIS to transmit the
requested worklists.
Message

<ENQ>

<ACK>

<STX>1H|\^&|||SampleLIS|||||EUROLineScan||P|1.0|20171006080913<
CR>
<ETX>5D<CR><LF>

<ACK>

<STX>2P|1|PatID_01|LabNumber_01||Mustermann^Max||
19711217055000|M||||||||||||||||||||||||||||<CR><ETX>F6<CR><LF>

<ACK>
Message

<STX>3O|1|PatID_01||^^^755^^^^B^0ÊBV2.1G|||||||N||||||||||||||F||||||<C
R>
<ETX>E3<CR><LF>

<ACK>

<STX>4O|2|PatID_01||^^^756^^^^B^0ÊBV2.1M|||||||N||||||||||||||F||||||<C
R>
<ETX>EB<CR><LF>

<ACK>

<STX>5L|1|N<CR><ETX>08<CR><LF>

<ACK>

<EOT>
Table 16 - ASTM, Example of import of a requirement, part 2
Here the communication is initiated by the LIS (as EUROLineScan is currently

waiting for the transmission of the requests). After transmitting the <ENQ>
signal and the header, the LIS transmits the patient record to indicate for
which patient the following samples are to be performed.
Subsequently, two “order” data sets are transferred. Two examinations are to
be carried out here: EBV2.1G (ID 755) and EBV2.1M (ID 756).
Finally, the LIS transmits the terminator record and the <EOT> signal.
Thus, all the necessary information has been transmitted so that
EUROLineScan is now ready to read in and evaluate the strips.
4.3.4 Export of the results
Message

<ENQ>

<ACK>

<STX>1H|\^&|||EUROLineScan|||||||P|3.4.24|20180604101252<ETX>3
<LF>

<ACK>

<STX>2P|1|PatID_01|LabNumber_01||Mustermann^Max||19711217|M
|||||||||||||||||||||||||<ETX>B0<LF>

<ACK>

<STX>3O|1|PatID_01||^^^755^^^^B^0ÊBV2.1
EL_IgG|||||||N||||||||||||||F|||||<ETX>27<LF>

<ACK>

<STX>4R|1|^^^755^^^^B^0ÊBV2.1GET|o|||N||F|||||<ETX>C5<LF>
Message

<ACK>

<STX>5R|2|^^^755^^^^B^0ÊBV2.1GCo|+++|||N||F|||||<ETX>F2<LF>

<ACK>

<STX>6R|3|^^^755^^^^B^0ÊBV2.1GM|o|||N||F|||||ETX>7D<LF>

<ACK>

<STX>7R|4|^^^755^^^^B^0ÊBV2.1GG|+++|||N||F|||||<ETX>8B<LF>

<ACK>

<STX>0R|5|^^^755^^^^B^0ÊBV2.1GEAD|++|||N||F|||||<ETX>DD<LF>

<ACK>

<STX>1R|6|^^^755^^^^B^0ÊBV2.1Gp22|+++|||N||F|||||<ETX>1A<LF>

<ACK>

<STX>2R|7|^^^755^^^^B^0ÊBV2.1GEBN|+++|||N||F|||||<ETX>15<LF>

<ACK>

<STX>3R|8|^^^755^^^^B^0ÊBV2.1Gp19|+++|||N||F|||||<ETX>22<LF>

<ACK>

<STX>4R|9|^^^755^^^^B^0ÊBV2.1G125|+++|||N||F|||||<ETX>DA<LF>

<ACK>

<STX>5L|1|N<ETX>D3<LF>

<ACK>

<EOT>
Table 17 - ASTM, example for export of results
In this example, the results of the EBV 2.1 IgG test (ID 755) are transmitted. A
total of 9 result data sets are transferred, one for each antigen band on the
strip (incl. label and control bands).
4.3.5 Settings for the ASTM format

In the “ASTM” section of the settings menu you will find various options for
adjusting the ASTM connection:
Figure 10 - ASTM format settings
Setting Explanation
“Connection Defines the way EUROLineScan communicates with the LIS:
Type”:
TCP/IP: Default setting; both systems
communicated via two-way TCP/IP
messages
File-based: Instead of active two-way
communication, the entire request is
written to a file, which is then read and
processed by the other system.
With this setting, no control codes or
checksums are transmitted. The
worklist request described in chapter
1.3.8 would result in the following file
instead:
1H|\^&|||SampleLIS|||||EUROLineScan||P|1
.0|20171006080913
2P|1|PatID_01|LabNumber_01||Musterma
nn^Max||19711217055000|M||||||||||||||||||||||||||
||
3O|1|PatID_01||^^^755^^^^B^0ÊBV2.1
G|||||||N||||||||||||||F||||||
4O|2|PatID_01||^^^756^^^^B^0ÊBV2.1
M|||||||N||||||||||||||F||||||
5L|1|N
Files via Similar to the “File-based” option, but all
TCP/IP: data is sent to the other system as a
single TCP/IP message.
Setting Explanation
“Import Path”: When using the file-based import, this setting determines in
which directory EUROLineScan searches for the request
files. For all other connection types, this setting has no effect.
“Export path”: When using the file-based import, this setting determines in
which directory EUROLineScan stores the request files. For
all other connection types, this setting has no effect.
“Extension Import When importing files from the "Import Directory" folder,
Files”: EUROLineScan will only look at files with the extension
specified here. Alternatively, use the placeholder "*" to import
all files, regardless of the file extension.
“Extension export When exporting evaluation results, EUROLineScan will use
files”: this extension for the result files.
“Host”: For TCP/IP-based connections, enter the IP address of the

computer on which the LIS is running.
“Port”: The port number used for TCP/IP connections.
“Timeout”: The time period (in milliseconds) after which EUROLineScan

will abort the communication attempt if no response is
received from the LIS.
“Separate files for Only when using file-based communication. If this setting is
each patient”: active, EUROLineScan generates a separate result data for
each patient instead of storing multiple records in the same
file.
“Validate command If this setting is active, EUROLineScan checks the command
number”: counter (see chapter 4.3.1.4). If this does not correspond to
the expected value, EUROLineScan will terminate the
communication with an error message.
“Validate check If this setting is active, EUROLineScan checks the check digit
buzzer” (see chapter 4.3.1.4).
If this does not correspond to the expected value,
EUROLineScan will terminate the communication with an
error message.
“Allow multiple Only for TCP/IP connections. If this setting is active,
requests per EUROLineScan accepts multiple patient requests within one
message”: message without having to close and re-establish
communication between the requests.
“Exporting If this setting is active, EUROLineScan exports concentration
concentrations values, if defined for the examination in question.
instead of
intensities”:
“Test abbreviation If active, EUROLineScan not only uses the abbreviation to

before band identify a band, but precedes the abbreviation of the
abbreviation”: respective examination, e.g:
7R|6|^^^755^^^^B^0ÊBV2.1Gp22|+++|||N||F|||||
In this example, "EBV2.1G" is the study abbreviation and
"p22" is the name of the band. Thus, the LIS can clearly
distinguish between bands with the same name. This can
happen if the same allergen/antigen is present on several
different test strips.
If this setting is deactivated, only the band name is exported:
7R|6|^^^755^^^^B^0^p22|+++|||N||F|||||
Setting Explanation
“Alternating If this setting is deactivated (default), the command counter
command jumps back to 0 after reaching the value 7 and is incremented
counter”: again.
If, on the other hand, it is active, the command counter only
alternates between the values 0 and 7 after reaching the
value 7 for the first time:
1, 2, 3, 4, 5, 6, 7, 0, 7, 0, 7, 0, 7….
“Use sample ID If this setting is active, the sample ID from the “Order”
as patient ID”: record is used as the patient ID.
“Logging If this setting is active, the sent and received messages
communication”: are saved in the file “ASTM.log” in the EUROLineScan
data folder.
“Use query mode By default, EUROLineScan loads all open requests
for import”: from the LIS with each import. However, if this setting is
active, a dialogue will appear when the Import button is
clicked, allowing the user to select one or more patient
IDs. Only the requests for the selected patients are then
loaded.
Table 18 - ASTM format settings
Replacement filter
With the replacement filter, EUROLineScan offers you the possibility to
change the data of imported or exported protocols according to definable
criteria. This can be used, for example, if EUROLineScan and the software to
be connected use different names for bands, results or examinations. In such
a case, you can define a replacement filter to replace the corresponding texts
with a string of your choice directly after the import or directly before the
export. This saves time-consuming changes to the configuration of the
programs involved.
The replacement filter can be configured via the section of the same name in
the settings menu.
Figure 11 - Replacement filter settings
By clicking on the Add button you can create a new replacement rule. The
input fields in the upper part of the window are then activated and you can
start defining the rule.
The following setting options are available:
Setting Explanation
“Original”: The string to be replaced
“Replace with”: The string to be inserted in place of the original text
“Case sensitive”: This setting determines whether case sensitivity is
used when finding the original string.
“Subtext”: If this setting is activated, word parts are also taken
into account when finding the original string (i.e. the
original text “Pos” would be found in both “Positive”
and “Position”).
“Use for import / Here you can decide whether the respective
Use for export“: replacement rule is applied when importing
requirements, when exporting results or in both cases
mentioned.
Setting Explanation
“Use for band By means of these settings, you can determine to
names” / which type of data the respective replacement filter is
“Use for test to be applied. In this way, it can be prevented that a
names” / change such as renaming a band unintentionally
affects other strings (e.g. patient data) which happen
“Use for protocol
to contain the original text being searched for.
data” /
“Use for patient
data” /
“Use for strip results”:
Table 19 - Replacement filter settings
After completing the configuration, save your entries with the Save button or
click Cancel to discard the current rule.
Furthermore, you have the option to Edit or Delete an existing rule via the
buttons in the lower part of the window.
Note
Before the replacement rules defined here take effect, the option “Apply
replacement filter” must also be activated in the settings for the respective
connection format (text format, GDT or EUROLabOffice).
List of abbreviations
To establish an LIS connection, it is usually necessary to match the
requirement and result abbreviations used between EUROLineScan and the
LIS. The information necessary for this can be found under the menu item
Help -> Examinations. To request an examination, use the entry in the
column “Abbreviation”.
Figure 12 - Examination list
When subsequently exporting the results from EUROLineScan, the results of
the individual bands are also transferred. The abbreviations used for this can
be selected by clicking on the Details button.
Figure 13 - Band list
Using the Export button, the band list can be exported to a .CSV file, which
can then be opened e.g. with Microsoft Excel.
5 Network installation
It is possible to access a database with EUROLineScan that is located on a
different system than the one on which the software is installed. In the case of
Oracle and MySQL databases, this is configured via the TNS configuration or
the specification of the MySQL host. In the case of the Firebird database used
by default, proceed as follows:
I) Installing Firebird on the Server
Note
To access a network database it is imperative that the Firebird database

system is installed on the server (i.e. the computer on which the database
file is located). It is not sufficient to merely store the file in a folder shared
on the network.
To install Firebird on the server, use the file “FirebirdInstaller.exe”, which you
will find in the “Applications” folder on the EUROLineScan CD.
II) Configuring the data source
Now you can set up a new database connection (or edit an existing one) as
described in chapter 6.1.2, so that the network database is used. To do this,
enter the following as the database file:
[IP adress of the server]:[Full path of the database on the server]
So for example:
192.168.1.22:C:\ProgramData\EUROIMMUN\EUROLineScan\
Database_UTF8\EUROSCAN.FDB
III) Setting up the necessary permissions
The last thing to ensure is that communication between all computers

involved is possible via TCP/IP on port 3050 (the port used by Firebird by
default).
6 Database management
In the standard installation, EUROLineScan uses a Firebird database in
version 2.5. Further information on this database system can be found on the
website of the Firebird project:
http://www.firebirdsql.org/
Here it is possible to set up several database connections, e.g. for archiving

purposes. In this case, you can switch between the available data sources via
the main menu (File -> Databases).
Figure 14 - Database connection selection
The individual data sources are stored in the configuration file

“Databases.xml”, which is located in the EUROLineScan directory. To edit this
file you can use the utility “DataSourceManager” which can be found in the
folder “Tools” on the EUROLineScan installation CD.
DataSourceManager
By means of this program you have the possibility to edit or remove existing
data sources and to create new database connections.
Figure 15 - DataSourceManager
Under Available data sources all currently existing database connections are
listed. Here the program automatically determines the database configuration
file (“databases.xml”) used by EUROLineScan; if this fails or you want to edit
a file other than the automatically determined one, you can select the desired
file via the function Open data source file (the second button in the menu
bar).
6.1.1 Editing a database connection

By selecting one of the connections and clicking on Edit, you get the
possibility to adjust the connection data of the selected data source:
Figure 16 - Editing a database connection
The following information about a connection can be edited:

Setting Explanation
“Name”: The name under which the data source is displayed in
EUROLineScan. This must be unique (i.e. the same
name may not be used for two data sources), but is
otherwise freely selectable.
“Database type”: Besides the already mentioned Firebird database
system, EUROLineScan also supports Oracle and
MySQL databases. By means of this setting you can
determine which of these systems is to be addressed
with the current database connection.
“User name”: The name used to log on to the database. In the case of
a standard installation of EUROLineScan, the name
“euroscan” is to be used here.
“Password”: The password used when logging into the database.
The default setting is also “euroscan”.
Setting Explanation
“Version”: This entry gives information about the structure of the
database. The value to be entered depends on the
EUROLineScan version to which this database belongs:
EUROLineScan Version Value
3.1.28 and older 0
3.2.1 to 3.2.3 2
3.2.4 to 3.2.6 4
3.2.7 5
3.2.8 to 3.3.1 7
3.3.2 to 3.3.3 9
3.3.4 12
3.3.5 to 3.3.7 13
3.3.8 14
3.3.9 to 3.3.11 15
3.4.0 to 3.4.1 16
3.4.2 17
3.4.3 18
3.4.4 19
3.4.5 22
3.4.6 25
3.4.7 27
3.4.8 to 3.4.11 29
3.4.12 to 3.4.16 31
3.4.17 to 3.4.18 32
3.4.19 34
3.4.20 35
3.4.21 to 3.4.24 36
3.4.25 to 3.4.26 37
3.4.27 to 3.4.28 39
3.4.29 41
3.4.30 42
“Database- For Firebird databases only: The path and file name of
File: the database file (.FDB).
“MySQL Host”: For MySQL databases only: The IP address or host

name of the server on which the database is located.
“MySQL DB”: For MySQL databases only: The name of the database
to be accessed.
“TNS Name”: For Oracle databases only: The TNS name of the
database to be used (cf. “tnsnames.ora”).
“Strip pictures” / Specifies the paths in which the images of the captured
“Stencil strips (if not stored in the database), the stored
Westernblot evaluation templates and the stored
pictures” /
worksheet images are to be stored.
“worksheet pictures”:
It should be noted that different directories are selected
for all database connections; otherwise data may be
lost or corrupted.
Table 20 - Database connection settings
If all entries are complete, you now have the option of using the Test
Connection button to check whether a database connection can be
established. If there are any problems, an error message will be displayed.
You can then accept the changes you have made by clicking on the OK
button or discard them by clicking on Cancel.
6.1.2 Creating a new database connection

To create a new data source, use the New button. This activates the input
fields in the lower half of the window; the available data fields are identical to
those when editing a data source (see chapter 6.1.1).
6.1.3 Importing a Firebird database

If you want to add an existing Firebird database file (e.g. from another PC) to
your EUROLineScan installation, you can use the Import Firebird Database
button (fifth button in the menu bar). A corresponding selection dialogue
allows you to select the desired database file; a new data source is then
automatically created and the program independently determines the
corresponding configuration parameters. Afterwards you only have to enter
the desired database name as well as the image paths (see chapter 6.1.1)
before you can take over the newly created data source into the list by
clicking on OK.
6.1.4 Using Embedded Firebird

If problems occur when using the standard installation of Firebird, the
embedded Firebird server can be used as an alternative. This is a special
version of Firebird which is copied into the directory of an application and is
only available to this program. Since any other Firebird instances are not
affected by this, this approach is particularly suitable if an incompatible
Firebird version is already installed on the system but cannot be removed
(e.g. because it is required by another application).
Note
As Embedded Firebird is not network-compatible, this variant of database

access can only be used if EUROLineScan and the database file are on
the same PC the database file are on the same PC.
You will find all the necessary files on the EUROLineScan CD in the folder
“Tools\EmbeddedFirebird\Data”. Copy the entire contents of this folder into
the EUROLineScan directory (existing files can be overwritten in the process).
The program will then automatically use the Embedded Firebird server
without the need to adjust the program configuration. Conversely, by deleting
these files from the EUROLineScan directory, you can remove the Embedded
Firebird server so that the software works with the standard Firebird
installation again.
7 Import and export of protocols
EUROLineScan offers you the possibility to export evaluated protocols to a
.zip archive or to import protocols collected with another installation.
This function can be used, for example, to transfer evaluation results from one
EUROLineScan installation to another. This function is also important if
problems or ambiguities arise during the evaluation of strips while working
with the software. You can then export the protocols in question and send
them to EUROIMMUN support, so that they can recreate the evaluation and
identify any problems.
There are basically two options for exporting protocols: One is the export
directly from the EUROLineScan program, the other is by means of the
auxiliary program “ImpEx”, which is part of every regular EUROLineScan
installation.
From EUROLineScan
If you only want to export a single protocol, you can do this directly from the
results window. To do this, click on any evaluated strip with the right mouse
button and select Export to file.
Note
The entire protocol is always exported, not just the selected strip.
Figure 17 - Export to file
The export window then opens:
Figure 18 - Export window for file export and upload
There are two options for exporting protocols, which you can choose from
using the tabs at the top of the window:
Settings Explanation
“Export to file”: The protocol is exported to a .zip archive, which can be
transferred to any other system.
“Upload”: The protocol is transferred directly to a EUROIMMUN
server. This variant is especially recommended in case
of possible evaluation problems, as this way, the
EUROIMMUN Support receives all relevant information
promptly and can thus react to your request as quickly
as possible.
Please note, however, that an active internet connection
is required on the PC on which EUROLineScan is
operated in order to use this function.
Table 21 - File export settings, part 1
The following entries must then be made:

Settings Explanation
“Target file”: (Only for file export) Specifies the file to which the log is
to be exported.
“Sender”: (Only when uploading) The name of the laboratory that
carried out the evaluation.
“Worksheet If this option is selected, the scanned image of the
image export”: worksheet (if available) will also be exported. This
makes it easier for the EUROIMMUN Support to
reproduce problems during the evaluation. Please note,
however, that this will increase the size of the export file
and correspondingly the duration of the upload.
“Patient data By means of this setting you can determine that the
Export”: patient data (patient ID, name, date of birth, etc.) should
be exported unchanged. Otherwise, all patients in the
export file will be anonymised so that it is no longer
possible to draw conclusions about the persons
concerned.
“Comment”: Here you can enter additional comments on the
exported protocol, e.g. a precise description of the
problem that occurred, reproduction steps, etc. When
using the upload function, you can also enter contact
details so that EUROIMMUN Support can contact you in
case of any queries.
Table 22 - File export settings, part 2
After you have made all the necessary settings, you can start the actual
export by clicking on the Save to file or Upload button.
ImpEx
The ImpEx program can be used to export one or more protocols into a .zip
archive. In contrast to the export from EUROLineScan presented in the
previous section, ImpEx is therefore also suitable for exporting larger amounts
of data. Conversely, logs can also be imported from such an archive into your
EUROLineScan installation.
ImpEx is automatically installed as part of the EUROLineScan setup and can
be called up via the start menu (“Programs” -> “EUROIMMUN” ->
“EUROLineScan” -> “ImpEx”).
Figure 19 - ImpEx: Main screen
First you can select the data source to be used for the export or import under
Database. The database information below is determined automatically.
Then the following functions are available to you via the buttons at the right-
hand side of the window.
7.2.1 Export protocols

Using this function, you can export protocols from your EUROLineScan
installation into a .zip archive to transfer them to another PC or to send them
to EUROIMMUN support for checking.
After clicking on Export protocols, a selection dialogue opens in which you
can specify the desired target file. The name and storage location of the file
can be selected as desired.
In the following window, you can select the protocols to be exported:
Figure 20 - ImpEx: Protocol selection
Note
Please note that by default only the protocols of the current week are
displayed. If you want to export older protocols, remove the tick in front of
the option “Only within the period” (as shown in the picture above).
Select the desired protocols for export by marking the selection field in the first
table column. If necessary, you can limit the list of displayed protocols using
the selection fields on the right-hand side of the window.
As with the export from EUROLineScan, you can specify whether the
worksheet image (if available) and the patient data should also be exported
(see chapter 4.1).
After you have made all settings, start the export by clicking on OK. Please
note that this process may take a few minutes. Finally, you will be informed
about the progress of the export in an overview window:
Figure 21 - ImpEx: Export Overview
7.2.2 Import protocols
This function allows you to import logs from a .zip archive created with ImpEx
into your EUROLineScan installation. This can be useful, for example, to
migrate protocols from one PC to another or to restore a data backup.
After clicking on Import protocols, a selection dialogue opens with which you
can select the protocol to be imported. Following this, click on Open to start
the import.
After completion of the import, an overview window is displayed in which all
imported protocols are listed:
Figure 22 - ImpEx: Import Overview
7.2.3 Export Lots

This function allows you to export Westernblot lots that have already been
read into EUROLineScan.
Note
When exporting protocols containing Westernblot strips, the lot used are
automatically exported as well, so that a separate export of the lot data is
not necessary.
Analogous to the protocol export, a dialogue appears here as well, with which
you can select the target file for the export.
In the following window, you can specify which lots are to be exported.
Figure 23 - ImpEx: Lot selection
Using the input fields on the right-hand side of the window, you can narrow
down the displayed lots.
By marking the selection field in the first table column, you can select one or
more lots for export. Afterwards, click OK to start the export process.
When the export is complete, a list of the exported lots is displayed.
Figure 24 - ImpEx: Export overview (lots)
7.2.4 Import lots

Via the menu item Import lots you can import a lot archive created with ImpEx
into your EUROLineScan installation. These lots can then be used for the
evaluation of Westernblot strips.
First, a dialogue opens with which you can select the archive to be imported.
Afterwards, click on Open to start the import.
When the import is complete, a summary appears listing all imported lots:
Figure 25 - ImpEx: Import overview (lots)
File upload
Depending on the number of strips included and the settings used during
export, the archives exported via EUROLineScan or ImpEx may become too
large to be sent by email. For this reason, it is possible to upload such files
directly to a EUROIMMUN server. To do this, open the EUROIMMUN website
(http://www.euroimmun.de) and select “Service” -> “Customer Login” from the
navigation bar.
Figure 26 - Calling up the EUROIMMUN Customer Portal
A login form will then appear where you can log in with the following access
data:
Login name: els-upload
Password: euroscan
From the menu bar on the left, select the entry Upload. In the form that
opens, you can select the file that you would like to transfer to EUROIMMUN
Support by clicking on the button Search protocols. In the field “Comment”
you can enter a short description of the incident, the EUROIMMUN Support
employee in charge (if known) and your contact details for possible enquiries.
Figure 27 - Upload form
Afterwards, click on the Upload button to start the file transfer. Please note
that this process may take a few minutes depending on the size of the file and
the speed of your internet connection.
8 Data backup
There are various options available for backing up your configuration and
evaluation data, the two most common of which are briefly presented here.
Manual backup
The easiest way to create a database backup is to use the Firebird data
backup tool “nbackup”. You will find this in the “bin” directory of your Firebird
installation.
nbackup does not have a graphical user interface; instead, the program is
controlled entirely via the command line.
To create a complete backup, call the program with the following parameters:
nbackup -U [user name] –P [password] –B 0 [name of the database to be
backed up] [name of the backup file]
For a standard installation of EUROLineScan, for example, the following call
would be executed (Windows Vista or newer):
nbackup –U euroscan –P euroscan –B 0
“C:\ProgramData\EUROIMMUN\EUROLineScan\Database_UTF8\
EUROSCAN.FDB“ “D:\Backups\EUROSCAN.FBK”
Here the target of the backup (in the above example
"D:\Backups\EUROSCAN.FBK") is freely selectable.
The result of such a backup is a Firebird backup file (.FBK), which can also be
restored with nbackup. A call of the following form is used for this:
nbackup -U [user name] –P [password] –R [name of the target database]
[name of the backup filei]
The file specified under “Name of the target database” does not have to exist
at the time nbackup is called, but is automatically created or overwritten if the
file already exists.
More information on nbackup can be found in the documentation of the
Firebird project at
http://www.firebirdsql.org/manual/de/nbackup-de-backups.html
ImpEx
Alternatively, it is possible to save your evaluated protocols using the “ImpEx”
utility. Please refer to chapter 7.2 for all necessary information.
Please note, however, that ImpEx is not designed for processing large
amounts of data. If you have many evaluated protocols (> 100), it is
recommended to use the software “nbackup” presented in the previous
section instead or to divide the export into several smaller processes (e.g.
2 exports of 50 protocols each).
9 Data migration
To transfer log data from one EUROLineScan installation to another (e.g.
when changing the computer system), EUROLineScan provides you with
three different options to choose from depending on your needs (amount of
data and program version used).
Copying the data using ImpEx

The use of ImpEx is particularly useful if different versions of EUROLineScan
are installed on both systems and you only want to transfer smaller amounts
of data. In this case you can transfer your log data to the new system using
ImpEx as described in Chapter 7.2.
Replacing the database file

This option can be used if the same version of EUROLineScan is used on
both systems and EUROLineScan has not yet been used on the new system
(i.e. the target of the migration), for example when changing a workstation. In
this case you can install EUROLineScan on the new system and then replace
the database file with the one copied from the old system.
Note
Please note that any existing evaluation data on the new system will be
irretrievably overwritten by this.
If necessary, you can use the program “DataSourceManager”, as described in

chapter 6.1, to determine the storage location of the database file.
Adding a new data source

If protocols have already been evaluated on the new system, the database file
from the old system can be added as an additional data source. This allows
you to switch back to the old database file in EUROLineScan at any time via
the main menu (“File” -> “Databases”) to view the protocols stored there.
To add a data source, please use the program “DataSourceManager”. The
steps required for this are shown in Chapter 6.1.
10 List of figures
Figure 1 - Selection of the connection format ............................................................................... 11
Figure 2 - Import of a request list ................................................................................................. 13
Figure 3 - Overview of imported requirements ............................................................................. 14
Figure 4 - Error when importing a request .................................................................................... 14
Figure 5 - Selective import ........................................................................................................... 14
Figure 6 - Information on faulty request file .................................................................................. 15
Figure 7 - Settings for GDT connection ........................................................................................ 17
Figure 8 - Exemplary settings for the text format .......................................................................... 20
Figure 9 - Text format settings ..................................................................................................... 22
Figure 10 - ASTM format settings ................................................................................................ 36
Figure 11 - Replacement filter settings ......................................................................................... 39
Figure 12 - Examination list .......................................................................................................... 40
Figure 13 - Band list ..................................................................................................................... 41
Figure 14 - Database connection selection .................................................................................. 43
Figure 15 - DataSourceManager .................................................................................................. 44
Figure 16 - Editing a database connection ................................................................................... 45
Figure 17 - Export to file ............................................................................................................... 48
Figure 18 - Export window for file export and upload.................................................................... 48
Figure 19 - ImpEx: Main screen ................................................................................................... 50
Figure 20 - ImpEx: Protocol selection........................................................................................... 51
Figure 21 - ImpEx: Export Overview............................................................................................. 51
Figure 22 - ImpEx: Import Overview ............................................................................................. 52
Figure 23 - ImpEx: Lot selection................................................................................................... 53
Figure 24 - ImpEx: Export overview (lots) .................................................................................... 53
Figure 25 - ImpEx: Import overview (lots) ..................................................................................... 54
Figure 26 - Calling up the EUROIMMUN Customer Portal ........................................................... 54
Figure 27 - Upload form ............................................................................................................... 55
11 List of tables
Table 1 - GDT format, field identifiers (import) ............................................................................. 13
Table 2 - GDT format, field identifiers (export) ............................................................................. 16
Table 3 - GDT format, field identifiers (export of band results) ..................................................... 17
Table 4 - Settings for the GDT format .......................................................................................... 20
Table 5 - Text format settings ...................................................................................................... 24
Table 6 - ASTM requirement, field identifiers ............................................................................... 25
Table 7 - ASTM connection, control characters............................................................................ 25
Table 8 - ASTM connection, separator ......................................................................................... 26
Table 9 - ASTM, Header record ................................................................................................... 27
Table 10 - ASTM, Patient record .................................................................................................. 29
Table 11 - ASTM, Order record .................................................................................................... 30
Table 12 - ASTM, Query record ................................................................................................... 31
Table 13 - ASTM, Result record ................................................................................................... 32
Table 14 - ASTM, Terminator record ............................................................................................ 32
Table 15 - ASTM, Example of import of a requirement, part 1 ...................................................... 33
Table 16 - ASTM, Example of import of a requirement, part 2 ...................................................... 34
Table 17 - ASTM, example for export of results ........................................................................... 35
Table 18 - ASTM format settings.................................................................................................. 38
Table 19 - Replacement filter settings .......................................................................................... 40
Table 20 - Database connection settings ..................................................................................... 46
Table 21 - File export settings, part 1 ........................................................................................... 49
Table 22 - File export settings, part 2 ........................................................................................... 49
YG_0006_A_UK_Z03.docx
2021-05-12
EUROIMMUN Medizinische Labordiagnostika AG · E-Mail euroimmun@euroimmun.de · Internet www.euroimmun.de

Addendum Eng

Uploaded by

Document Information

Original Description:

Original Title

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

Addendum Eng

Uploaded by

Copyright:

Available Formats

Addendum

All contents of this document, particularly images, are protected by copyright.

Software version ...................................................................................... 3.4

Document number ...................................................... YG_0006_A_UK_Z03

2 Dealing with software errors ................................................................................................. 8

5 Network installation ............................................................................................................. 42

6 Database management ........................................................................................................ 43

8 Data backup ......................................................................................................................... 56

10 List of figures ................................................................................................................... 58

11 List of tables ..................................................................................................................... 59

Changes to this manual

Observe instructions for use

Tab. 1 Other symbols

General safety instructions

Figure 1 - Selection of the connection format

4.1.1 Structure of the requirements file

A GDT file contains all information relevant to EUROLineScan for a patient

Each line of a requirements file is structured according to the following

8410 Test identification. This value contains the abbreviation of the

8402 Device-specific map (optional). Can be used in EUROLineScan

6333 Name of the sender of the sample; alphanumeric, maximum 32

6337 Contains the designation of the test kit used; alphanumeric,

4.1.2 Importing the requirements

Figure 2 - Import of a request list

Figure 4 - Error when importing a request

4.1.3 Selective import

Figure 5 - Selective import

Figure 6 - Information on faulty request file

4.1.4 Structure of the result file

4.1.5 Settings for the GDT format

Figure 7 - Settings for GDT connection

4.2.1 Structure of the requirements file

For the above example, the following configuration would be selected:

Figure 8 - Exemplary settings for the text format

Furthermore, it is possible to transfer several requests within one file. Each

4.2.3 Text format settings

Use default path

Automatic export – Run name as file name

Automatic export – Consecutively numbered

4.3.1 Structure of an ASTM transmission

Checksums and command counters

Table 10 - ASTM, Patient record

Test Order record

Lfd. No. Field name Description

Table 11 - ASTM, Order record

Lfd. No. Field name Description

Table 12 - ASTM, Query record

Lfd. No. Field name Description

Table 13 - ASTM, Result record

Table 15 - ASTM, Example of import of a requirement, part 1

With this transmission, communication was established. EUROLineScan

Table 16 - ASTM, Example of import of a requirement, part 2

Here the communication is initiated by the LIS (as EUROLineScan is currently

4.3.4 Export of the results

Table 17 - ASTM, example for export of results

4.3.5 Settings for the ASTM format

“Host”: For TCP/IP-based connections, enter the IP address of the

“Timeout”: The time period (in milliseconds) after which EUROLineScan

“Test abbreviation If active, EUROLineScan not only uses the abbreviation to

Table 19 - Replacement filter settings

Figure 12 - Examination list

Figure 13 - Band list