Host Service GB v32

H 009007 10.
04
Micro Typing System
Host - Connections
For :
Network or RS-232
PC
Video
RS-232
Network
Video
RS-232 Special
I-2 Identification
AT THE READER’S ATTENTION
From now, the ID-Reader SA branded instrument will bear the name s. Only
the name is being changed. The instrument features still remain identical.
Whatever the term ID-Reader SA or s is used on this document designates the
same instrument.
From now, the IHMP-Reader branded instrument will bear the name x. Only
Whatever the term IHMP-Reader or x is used on this document designates the
same instrument.
From now, the ID-Reader M branded instrument will bear the name b. Only
Whatever the term ID-Reader M or b is used on this document designates the
same instrument.
From now, the ID-Sampler III M branded instrument will bear the name J.
Only the name is being changed. The instrument features still remain identical.
Whatever the term ID-Sampler III M or J is used on this document designates
the same instrument.
Copyright ©
The reproduction, even partially, of this document is forbidden. No part can be copied in any form, and
cannot be used, edited nor transmitted by any electronic means (photocopy, photography, magnetic
supports or other recording processes), without the written authorization of DiaMed AG. All rights and
particularly reproduction, translation, edition, distribution and also industrial property and recording are
reserved.
Printed in Switzerland
Host - Connections for M

Table of Contents I-3
Table of Contents
1 GENERAL ............................................................................................. 1 - 1
1.1 Identification ...................................................................................................... 1 - 1
1.1.1 Document ........................................................................................................ 1 - 1
1.1.2 Limited warranty .............................................................................................. 1 - 1
1.2 Chapter overview .............................................................................................. 1 - 2
1.3 Appropriate use ................................................................................................. 1 - 2
1.4 Glossary ............................................................................................................ 1 - 2
1.4.1 Persons ............................................................................................................ 1 - 2
1.4.2 Product ............................................................................................................ 1 - 2
1.5 Typographic conventions .................................................................................. 1 - 3
2 HOST HOOK-UP ................................................................................... 2 - 1

2.1 Hardware connection ........................................................................................ 2 - 1
2.1.1 RS 232 line ...................................................................................................... 2 - 1
2.1.2 Network ............................................................................................................ 2 - 1
2.2 Software communication ................................................................................... 2 - 2
2.2.1 File structure .................................................................................................... 2 - 2
2.2.2 Selection of the configuration windows ............................................................ 2 - 4
2.2.3 Import ............................................................................................................... 2 - 5
2.2.3.1 File description for import.......................................................................... 2 - 5
2.2.3.2 Procedure ................................................................................................. 2 - 6
2.2.3.3 DBASE...................................................................................................... 2 - 7
2.2.3.4 DELIMITED............................................................................................... 2 - 7
2.2.3.5 PARADOX ................................................................................................ 2 - 7
2.2.3.6 SERIAL LINK ............................................................................................ 2 - 8
2.2.4 Export ............................................................................................................ 2 - 10
2.2.4.1 File description for export........................................................................ 2 - 10
2.2.4.2 Procedure ............................................................................................... 2 - 21
2.2.4.3 DBASE.................................................................................................... 2 - 23
2.2.4.4 DELIMITED............................................................................................. 2 - 23
2.2.4.5 PARADOX .............................................................................................. 2 - 23
2.2.4.6 SERIAL LINK .......................................................................................... 2 - 24
2.2.4.7 Segment results codes ........................................................................... 2 - 25
Doc N° H 009007 10.04 V3.2

I-4 Table of Contents

General 1-1
1. GENERAL
1.1 Identification
1.1.1 Document
Host connections for M.
Version 3.2 October 2004
Document No. : H 009007
Manufacturer
DiaMed AG
CH-1785 Cressier sur Morat
Suisse
Tel. ++41 (0)26 / 674 51 11
Fax ++41 (0)26 / 674 51 45
1.1.2 Limited warranty
If a DiaMed system is connected to a central information system (Host), the user takes on full responsibility
for ensuring correct data transmission to this system (hardware and software aspects).
Doc N° H 009007 10.04 V3.2

1-2 General
1.2 Chapter overview

This chapter gives basic information on system functions, specifications and documentation.
1.3 Appropriate use

The indications in the present manual, in particular the safety instructions must be complied with. This
document must be used by the technician who is making a connection between a DiaMed system and a
host.
1.4 Glossary
The following terms, among others, are used in this service manual.
1.4.1 Persons
Operator
The operator is the respective proprietor of the M, regardless of whether he operates it as the
owner or transfers it on to third parties.
Technician
The technician is the person who is making the connection between a DiaMed system and a host.
1.4.2 Product
Software
The software is the M.

General 1-3
1.5 Typographic conventions

The following styles are used in this manual.
Description style
This style, used in relation with a number in illustrations (figures) is preceded by the corresponding
number:
Example:
(1) First item

(2) Second item
(3) Etc...
Commands style
All software commands, buttons, function keys, windows, icons, options, tabs, check boxes, select boxes,
items, menus, tool bars, sections and fields used in this documentation will be shown with a bold italic font.
Example:
The Add one item command permits to select a field for the export.
Procedure style
The steps of a procedure to be carried out step by step by the technician are preceded with numbers
placed in brackets.
Example:
[1] Select in the available fields area the field you want to export.
[2] Click on the Add one item button to select it.
Procedure effects style
The procedure effects are described by using the following symbol !.
Example:
[1] Click on the Add one item button to select it.

! The field is moved to the selected fields area.
Doc N° H 009007 10.04 V3.2

1-4 General
Cross references style
This style is used to help the technician to find other information about the current subject.
Example:
" See page x-y.
Troubleshooting style
The complete description with the problem, the possible cause and the solution will be shown like
described below:
Problem
- Possible cause
Solution
List of items style
This style is used to give a list of items.
Example:
• item 1;
• item 2;
• item 3.
Note style
Used when the technician attention must be attracted about a particular operation or information.
Example:
# Note: With this type of format, the field 22 - Image Wells cannot be chosen.

General 1-5
Caution style
Used to prevent the technician from any danger or hazardous situation. Non-compliance with such
instructions may lead to damage parts or environment.
Example:
$ Take care about ...
Warning style
Used to prevent the technician from any important danger or hazardous situation. Non-compliance with
such instructions may lead to death or serious injury.
Example:
% Never open this cover
Doc N° H 009007 10.04 V3.2

1-6 General

Host hook-up 2-1
2. HOST HOOK-UP
2.1 Hardware connection
You can hook up a DiaMed system up to a “Host” via the RS232 port of the PC or via the network.
2.1.1 RS 232 line
9-pin connector
The wiring between the 9-pin RS232 connectors is

shown in the Fig. 1.
25-pin connector
On a 25-pin RS232 connector, the wiring is as

follows:
• RxD pin 3;
Fig. 1: RS 232 line
• TxD pin 2;
• 0V pin 7.
# If you enable hardware flow control (by checking the

DTR/DSR or RTS/CTS check boxes (1) in the
System Settings window, the CTS, RTS, DSR and
DTR pins must also be wired.
(1)
Fig. 2: Flow control
2.1.2 Network
It is also possible to transfer data from your DiaMed system via the network.
# Note: This solution permits to use DBASE or PARADOX output/input file type and also to transfer pictures
(see section “2.2.3.3 DBASE” on page 2-7 and section “2.2.4.3 DBASE” on page 2-23).
Doc N° H 009007 10.04 V3.2

2-2 Host hook-up
2.2 Software communication

2.2.1 File structure
Files start with [STX] (ASCII code 2), followed by data, checksum and [ETX] (ASCII code 3).
- Data transfer from Readers or M :
STX Data Checksum ETX
- Reply from host computer if data is correct.
STX OK Checksum ETX
- Reply from host computer if data is incorrect.
STX ER Checksum ETX
Example:
[STX]50601212121299748596|||||||||12.04.99|1|3|M081|00310030|0|3F||Operator|-|-|-|-|-|-|1|1|0|||||||||||||||||
1|1|12.04.99|0|Crossmatch: A-B-D-Enz-AHG-AHG (DiaClon)|Blood Group: compatible Crossmatch:
compatible|[CR][LF]CC[ETX]
# Note: Each sender data stream is followed by the transfer of a confirmation message from the receiver.
Checksum
To check data validity, the software computes a checksum by simply adding all the ASCII characters in the
data stream, in base 256, then converting the result into an hexadecimal code, of which the last two bytes
are taken. If the checksum computed by the receiver matches with that was originally computed by the
sender, then the data is considered valid.

Host hook-up 2-3
Example: [STX] PR13C|45516256|+++|++|+++|-|-|-|08/07/1999 13:36|[CR][LF] 6D [ETX]
P = 80 + = 43 / = 47
R = 82 I = 124 0 = 48
1 = 49 + = 43 7 = 55
3 = 51 + = 43 / = 47
C = 67 I = 124 1 = 49
I = 124 + = 43 9 = 57
4 = 52 + = 43 9 = 57
5 = 53 + = 43 9 = 57
5 = 53 I = 124 = 32
1 = 49 - = 45 1 = 49
6 = 54 I = 124 3 = 51
2 = 50 - = 45 : = 58
5 = 53 I = 124 3 = 51
6 = 54 - = 45 6 = 54
I = 124 I = 124 I = 124
+ = 43 0 = 48 [CR] = code ASCII $0D = 13
+ = 43 8 = 56 [LF] = code ASCII $0A = 10
Total : 3181
3181 = C6D = 6D (Checksum)
# Note: CR and LF are also taken in the addition
Doc N° H 009007 10.04 V3.2

2-4 Host hook-up
2.2.2 Selection of the configuration windows
To configure the import and/or export settings,

proceed as follows :
[1] Select the System Settings command from the

File menu of the Samples module.
! The window below appears.
[2] Select the Export Settings or Import Settings
tab.
[3] Follow the instructions according to section “2.2.3
Import” on page 2-5 for import and to section “2.2.4
Export” on page 2-10 for export.
Fig. 3: System Settings window

Host hook-up 2-5
2.2.3 Import
2.2.3.1 File description for import
Below we outline the content of each field available for selection which corresponds to the fields of the
Patient’s database (General Settings).
Obligatory added fields :
• First field : Test identification

• Second field : Sample identification
• Third field : Donor identification
" See also section “2.2.3.2 Procedure” on page 2-6
Obligatory selected fields :
01 - Name : This field contains the name of the patient.
02 - Identification : This field contains an identification of the patient (unique).
Optional selected fields :
03 - Birth date : This field contains the patient’s date of birth.
04 - ABO : Bloodgroup (A/B/AB/O).
05 - Rh(D) : Rhesus (positive/negative).
06 - Sex : This field contains the sex of the patient (male/female). In the import file 1 has to be used for
female and 0 for male.
07 - Information : This field contains any information desired.
# Note: The design of the Patient’s data fields is totally free ! When using radio groups the import file has
to contain 0 to select the first item of a radio group, 1 to select the second item, etc.
Doc N° H 009007 10.04 V3.2

2-6 Host hook-up
2.2.3.2 Procedure
You can import the work list and patient’s data from
the Host (See Fig. 4). (1) (2) (3)
# Note: Three fields are automatically selected at the

beginning of the data frame :
• First field : Test identification

• Second field : Sample identification
• Third field : Donor identification
To select the other fields in the order you want to

import to, use the following procedure : (9) (8) (7) (6) (5) (4)
Fig. 4: Import data
[1] Select in the available fields area (1) the field you want to import (see section “2.2.3.1 File description for
import” on page 2-5).
# Note: The fields 01 and 02 are obligatory to select.
[2] Click on the Select button (9).

! The field is moved to the selected fields area (8).
[3] Repeat the steps [1] and [2] until you have selected all the fields you want to import.
# Note: It is possible to select all the fields at one time with the Select All button (7).
In the selected fields area (8), the order can be changed with the arrow buttons (2 and 3), to move a
selected field up or down.
If you want to remove one field of the selected fields area (8), select the desired field and click on the
Delete button (6).
If you want to remove all the selected fields of the selected fields area (8), click on the Delete All button
(4).
[4] Click on the Input file type field (5) to choose DBASE (see section “2.2.3.3 DBASE” on page 2-7),
DELIMITED (see section “2.2.3.4 DELIMITED” on page 2-7), PARADOX (see section “2.2.3.5 PARADOX”
on page 2-7) or SERIAL LINK (see section “2.2.3.6 SERIAL LINK” on page 2-8).

Host hook-up 2-7
2.2.3.3 DBASE
The data will be imported as a DBASE file. You must

have a network connection.
With this type of input file, it is possible to transfer

pictures.
You must define the path and the name of the file to
be imported in the Path and file name field (1).
(1)
Fig. 5: Import with DBASE format
2.2.3.4 DELIMITED
The data will be imported as a file with a character of

delimitation. You can use a RS232 or a network
connection.
With this type of input file, it is not possible to

transfer pictures. You must define the path and the
name of the file to be imported in the Path and file
name field (2) plus the character of delimitation in
the Separator char field (3).
(2) (3)
Fig. 6: Import with DELIMITED format
2.2.3.5 PARADOX
The data will be imported as a PARADOX file. You

must have a network connection.
With this type of input file, it is possible to import

pictures. You must define the path and the name of
the file to be imported in the Path and file name
field (4).
(4)
Fig. 7: Import with PARADOX format
Doc N° H 009007 10.04 V3.2

2-8 Host hook-up
2.2.3.6 SERIAL LINK
The data will be imported through the RS232 connection.
With this type of format, it is not possible to transfer pictures. You can choose the same options as for the
DELIMITED format (see section “2.2.3.4 DELIMITED” on page 2-7). No file will be created on the hard disk
as with DELIMITED.
# Note: The following parameters have to be identical as for export if you use the same connection.
You can set the serial port communication protocol

as described below. (1) (2) (3) (4) (5) (6)
(1) COM Port : Serial port of the PC. You can select the
values COM 1, COM 2, COM 3, COM 4, COM 5 and
COM 6.
(2) Speed : Baudrate in bytes/second. You can select
the values 300, 400, 1200, 2400, 4800, 9600, 19200,
38400, 57600 and 115200.
(3) Buffer size : It defines the size in bytes of the buffer
for the communication. You can select the values
1024, 2048, 4096, 8192, 16384 and 32768.
(4) Parity :
The parity describes a bit checking scheme. When
used, all of the bits in each data byte are added
together. A final bit, called the parity bit, is added so
(12) (11) (10) (9) (8) (7)
that the sum of all bits is either odd or even,
whichever you specify. The transmitter calculates Fig. 8: Import with SERIAL LINK format
and transmits a parity bit. The receiver also
calculates a parity bit and compares it to the parity
bit received. If the bits are equal, it is assumed that the character was received without error. Otherwise, it
is assumed that there was an error during the transmission. The possible values for parity are :
• None : In this case, no flow control is used, no parity bit is added.
• Odd : The flow control is made by means of RTS and CTS streams. The M use the RTS stream
when it is able to receive and transmit when the CTS stream is activated. This flow control needs a 5
wires cable: ground; transmission; cross reception; CTS; RTS crossed. A parity bit is added so that the
bit sum is always odd.
• Even : The characters Xon (ASCII code 17) (8) and Xoff (ASCII code 19) (7) must be sent by the
receiver to the emitter to control the character emission flow. A parity bit is added so that the bit sum is
always even.
Xon : Starts data emission.
Xoff : Stops data emission.
• Mark : A parity bit of value one is always added.
• Space : A parity bit of value zero is always added.
(5) Word size : 5, 6, 7 or 8
(6) Stop bits : 1 or 2

Host hook-up 2-9
Information about the flow control

(1) (2) (3) (4) (5) (6)
“Receive flow control” (9) stops a remote device from
transmitting while the local receive buffer is too full.
“Transmit flow control" (10) stops the local device
from transmitting while the remote receive buffer is
too full.
Receive flow control is enabled by including the

UseRTS and/or UseDTR elements in the options
set. When enabled, the corresponding modem
control signals (RTS and/or DTR) are lowered when
the input buffer reaches the level set by the
BufferFull property. The remote must recognize
these signals and stop sending data while they are
held low. Because there is usually little delay before
the remote can react (as there is with software flow
control) you can set BufferFull close to the input (12) (11) (10) (9) (8) (7)
buffer size, perhaps at the 90% level.
Fig. 9: Import with SERIAL LINK format
As the application processes received characters,
buffer usage eventually drops below the value set by
the BufferResume property. At that point, the corresponding modem control signals are raised again. The
remote must recognize these signals and start sending data again. Again, because there is usually little
delay you can set BufferResume close to zero, perhaps at 10% of the input buffer size.
Transmit flow control is enabled by including the hwfRequireCTS and/or hwfRequireDSR elements in the
options set. With one or both of these options enabled, the Windows communications driver doesn’t
transmit data unless the remote device is providing the corresponding modem status signal (CTS and/or
DSR). The remote must raise and lower these signals when needed to control the flow of transmitted
characters.
# Note: Flow control using RTS and CTS (11) is much more common than flow control using DTR and
DSR (12).
Doc N° H 009007 10.04 V3.2

2-10 Host hook-up
2.2.4 Export
2.2.4.1 File description for export
Below we outline the content of each of the fields available for selection.
00 - Bar code : This field contains the barcode reference for the card used in the current test.
# Note: If you select this field and the test involves two ID cards, the M sends an additional field for
the second ID card in the same data stream.
01 - Patient’s data : This parameter contains one to x fields (depending of the database “Patient’s data”
configuration). It contains the administrative data of the patient ( for example “Date of birth”, “Sex”, etc.).
When using radio groups (like “Sex”) the export file will contain 0 when the first item is selected, 1 when
the second item is selected, etc.
02 - Sample’s last modification date : This field contains the date when the respective reading was
carried out.
03 - Sample identification : This field contains the sample ID.
04 - Donor identification (Crossmatch) : This field contains the donor name or ID (the exact form will
depend on the user).
# Note: If this field is empty, it will also be sent if the corresponding check box is selected (see section “
Check boxes :” on page 2-22).
05 - Test identification : This field contains a code identifying the test (see column Code of the
interpretation list below).
Antibody Screening
CH05 Ab.screening :I-II-III-IV (IAT) 5053
CH05A Ab.screening: I-II-III-IV (IAT) (IV on separate card)5053
CH06 Ab.screening: I-II-III-IV-AC (IAT) 5053
CH08 Ab.screening: DiaCell Pool I + II (IAT) 5053
CH09 Ab.screening: I + II DiaCell Pool (IAT Anti-IgG) 5054
CH12 Ab.screening: I-II-III-IV-DC Pool-DAT (IAT) 5053
CH13 Ab.screening: I-II-III-IV-DC Pool-AC (IAT) 5053
CH14 Ab.screening:I-II-III-IV- DC Pool (5053)
GE01 Ab. screening: I (IAT) 5053
GE15I Ab.screening:IP-IIP-IIIP IAT (5053)
GE45 Ab.screening: I-AC (IAT)5053
LUZ1 Ab.screening: I (IAT Anti-IgG) 5054
PR13C Ab. screening: I-II-III/IP-IIP-IIIP (IAT/ Enzyme) 5058

Host hook-up 2-11
PR13D Ab. screening: I-II-III/Ib-IIb-IIIb (IAT/Enzyme) 5058
PR13E Ab. screening: DiaScreen I-II-III-IV/VP-VIP (5057)
PR13G Ab.screening:Ib-IIb-IIIIb/I-III-III (Enz.bromeline/IAT) 5051
PR13H Ab.screening: IP-IIP-IIIP/I-II-III (Enzyme/IAT) 5051
PR13I Ab.screening: I-II-III/IP-IIP-IIIP (5053)
PR13J Ab.screening: IP-IIP-IIIP / I-II-III (5053)
PR15A Ab.screening: I-II (IAT) 5053
PR15B Ab. screening: I-II-III (IAT) 5053
PR15C Ab. screening: Ib-IIb-IIIb (Enzyme bromeline) 5052
PR15D Ab. screening: IP-IIP-IIIP (Enzyme papanized cells) 5052
PR15E Ab. screening: Ib-IIb (Enzyme bromeline) 5052
PR15F Ab. screening: Ip-IIp (Enzyme papaine) 5052
PR15G Ab. screening: Is-IIs (Saline) 5052
PR15H Ab. screening: Is-IIs-IIIs (Saline) 5052
PR15I Ab.screening: DiaCell Pool (I+IIp) (Enzyme papaine) 5052
PR20 Ab.screening: I-II-AC (IAT) 5053
PR20A Ab.screening: Ip-IIp+ACp (Enzyme papaine) 5052
PR20B Ab.screening: Ib-IIb+ACb (Enzyme bromeline) 5052
PR21A Ab.screening: I-II+AC/Ip-IIp +ACp (IAT/Enzyme papaine)5058
PR21B Ab.screening: I-II-AC/Ib-IIb+ACb (IAT/Enz.bromeline)5058
PR21C Ab.screening: Ib-IIb+ACb/I-II+AC(Enz.bromeline/IAT) 5051
PR21D Ab.screening : Ip-IIp+ ACp/I-II+AC (Enzyme papaine/IAT) 5051
PR22 Ab.screening:I-II (IAT)+ DAT 5053
PR23 Ab.screening: I-II-III-AC (IAT) 5053
PY15A Ab.screening : I-II (IAT Anti-IgG) 5054
PY15B Ab.screening: I-II-III (IAT Anti-IgG) 5054
SP01 Ab.screening: DiaCell Pool (I+II) Enzyme (5052)
SP02 Ab.screening: Is-IIs-IIs-IVs Saline(IV on separate card)5052
SP03 Ab.screening: Is-IIs-ACs Saline (5052)
SP04 Ab.screening: Is-IIs-ACs/I-II-AC (5051)
SV01 Ab. screening: I-II (IAT)/IIIp (Enzyme papaine) 5053/5052
Doc N° H 009007 10.04 V3.2

2-12 Host hook-up
Antigen
MO09E Antigen: Anti-D Monoclonal (5017)
MO44D Antigen: Anti-K Monoclonal (5020)
PR09C Antigen: Anti-A1 Absorbed (5014)
PR09D Antigen: Anti-H Monoclonal (5015)
PR09E Antigen: Anti-D (5016)
PR09F Antigen: Anti-A1 (Lectine) (5063
PR09G Antigen: Anti-H (Lectine) (5064)
PR09H Antigen: Anti-D for Dweak confirmation (5054)
PR09I Antigen: ID-Typing of partial D (5111)
PR09X Antigen: Anti-D for Dweak confirmation (IAT) 5053
PR44A Antigen: Anti-P1 (5023)
PR44B Antigen: Anti-Lea (5024)
PR44C Antigen: Anti-Leb (5025)
PR44D Antigen: Anti-K (5019)
PR44E Antigen: Anti-k (5026)
PR44F Antigen: Anti-Kpa (5029)
PR44G Antigen: Anti-Kpb (5030)
PR44H Antigen: Anti-Lua (5031)
PR44I Antigen: Anti-Lub (5032)
PR44J Antigen: Anti-Jka (5027)
PR44K Antigen: Anti-Jkb (5028)
PR44M Antigen: Anti-M (5021)
PR44N Antigen: Anti-N (5022)
PR44O Antigen: Anti-S (5033)
PR44P Antigen: Anti-s (5034)
PR44Q Antigen: Anti-Fya (5035)
PR44R Antigen: Anti-Fyb (5036)
PR44S Antigen: Anti-Cw (5018)
PR44T Antigen: Parvovirus B19 (5047)
PR44U Antigen:Anti-Xga (5053)
PR44V Antigen: Anti-Vel (5053)

Host hook-up 2-13
PR44W Antigen: Anti-U (5053)
PR44X Antigen: Anti-Tja (5053)
Antigen Profile
PO07 Antigen profile: K-k-Jka-Jkb-Fya-Fyb (5045)
PR41A Antigen profile: k-Kpa-Kpb-Jka-Jkb-ctl (5038)
PR42A Antigen profile: P1-Lea-Leb-Lua-Lub-ctl (5037)
PR43 Antigen profile: M-N-S-s-Fya-Fyb (5039)
Autocontrol
PR70 Autocontrol: (IAT) 5053
PR70A Autocontrol : Enzyme papaine (5052)
PR70B Autocontrol: Enzyme (bromeline) (5052)
PR70C Autocontrol: (IAT/Enzyme)(papaine))5058
PR70D Autocontrol: (IAT/Enzyme (bromeline)) 5058
PR70E Autocontrol: (Enzyme (bromeline)/IAT) 5051
PR70F Autocontrol: (Enzyme (papaine)/IAT) 5051
PR70H Autocontrol: Saline (5052)
PY70 Autocontrol: (IAT/ IgG) 5054
Blood Group
CH02 ABD for donors (5004)
MO01 Bloodgroup: ABO/Rh (DiaClon) (5001)
MO01A Bloodgroup: ABO/D (DiaClon) (5048)
MO01B Bloodgroup: ABO/D + DAT (DiaClon) (5049)
MO01C Bloodgroup: ABO/D + AHG (DiaClon) (5050)
MO01D Bloodgroup: ABO/Rh for patients (DiaClon)(5094)
MO02 Bloodgroup: ABO/Rh for donors (DiaClon) (5101)
Doc N° H 009007 10.04 V3.2

2-14 Host hook-up
MO10 Bloodgroup: A-B-D Confirmation for patients (Diaclon) (5005)
MO10A Bloodgroup: A-B-D Confirmation for patients (DiaClon) (5092)
MO12 Bloodgroup: A-B-DConfirmation for donors (DiaClon) (5105)
MP6148 MP-Test: A-B-D-ctl (6148)
MP6749 MP-Test: A-B-D-Confirmation (6536)
PR01 Bloodgroup: ABO/Rh (5000)
PR01B Bloodgroup: ABO/D (5003)
PR01C Bloodgroup : ABO/Rh + A1 (Lectine) (5084)
PR10 Bloodgroup A-B-D Confirmation (5004)
SV06 Bloodgroup: A-B-DConfirmation for patients (DiaClon) (5093)
Blood Group + AS
MO11 Type and Screen: A-B-D/I-II-III (DiaClon) (5068)
PR11 Type and Screen: A-B-D/I-II-III (5067)
SV03 BAS-Test: A-B/I-II-III-IV (5066)
SV04 BAC-Test: B-A-D/I-II-III (DiaClon) (5076)
SV05 DiaClon BAS-Test: A-B/I-II-III-IV (5077)
SV08 Bloodgr.+AS: A-B-D/I-II (Whthout III ) 5068
Blood Group + Reverse Group
MO31 Bloodgr. + Rev.gr.: A-B-D-ctl/A1-B (DiaClon) (5009)
MO31A Bloodgroup+Rev.gr.:A-B-D(VI-)-D(VI-)/A1-B (5074)
MO32 Bloodgroup+Rev.gr.: A-B-D(VI+)-D(VI-)/A1-B DiaClon (5098)
MP6040 MP-Test: A-B-D(VI-)-D(VI+)-ctl/A1-A2-B (6040)
MP6147 MP Test: A-B-AB-D(VI-)-D(VI+)-ctl/A1-B (6147)
MP6238 MP Test: A-B-AB-D(VI-)-D(VI+)-ctl/A1-A2-B-O (6238)
MP6339 MP Test: A-B-D(VI-)-D(VI+)-ctl-/A1-A2-B-O (6339)
MP6437 MP Test: A-B-AB-D(VI-)-ctl/A1-A2-B (6437)
MP6537 MP-Test: A-B-AB-D(VI-)-ctl/A1-A2-B (6536)
MP6540 MP-Test: A-B-D(VI-)-D(VI+)-ctl /A1-A2-B (6536)

Host hook-up 2-15
MP6547 MP-Test: A-B-AB-D(VI-)-D(VI+)-ctl/A1-B (6536)
MP6557 MP-Test:A-B-AB-D-ctl/A1-B-O(6557)
PR31 Bloodgr. + Rev.gr.: A-B-D-ctl/A1-B (5008)
Crossmatch
GE26 Bloodgroup: ABD Confirmation (5004)
GE44 ABD Confirmation for donors (DiaClon) (5005)
GE44A ABD (VI+) Confirmation for donors (DiaClon) (5105)
MO81 Crossmatch. A-B-D(VI-)/Enz/AHG-AHG DiaClon (5060)
MO82 Crossmatch :A-B-D(VI+)/Enz/AHG-AHG Diaclon (5091)
PR80 Crossmatch: (IAT)5053
PR80A Crossmatch: Saline (5052)
PR80B Crossmatch: Enzyme (bromeline) (5052)
PR80D Crossmatch :IAT + AC (5053)
PR80E Crossmatch: Saline+ AC (5052)
PR80F Crossmatch: Enzyme (bromeline) + AC (5052)
PR80G Minor Crossmatch IAT (5053)
PR80H Crossmatch : Enzyme papaine+ACp (5052)
PR80I Crossmatch :Enzyme papaine (5052)
PR81 Crossmatch: Complete A-B-D-ENZ-AHG-AHG (5059)
PY80 Crossmatch: IAT/ IgG (5054)
PY80D Crossmatch: IAT/ IgG + AC (5054)
PY80G Minor Crossmatch : IAT/IgG (5054)
Doc N° H 009007 10.04 V3.2

2-16 Host hook-up
Direct Antiglobulin Test (DAT)
CH03 Direct Antiglobulin test(IAT/IgG) 5054
PR16A DC Screening II: IgG-C3d-ctl (5056)
PR16D DC Screening I : IgG-IgA-IgM-C3c-C3d-ctl (5083)
PR17 Direct Antiglobulin test (IAT) 5053
PY17 Determination of IgG (5087)
PY18 Determination of IgG subclasses (5089)
Haemoglobinemia
PR50 ID-Sickle Cell Test (HbS) (5061)
PR51 PNH Test (5062)
Identification
CH10 Identification: 8 cells IAT(7 + 8 on separate card)(5053)
CH11 Identification:8cells P Enzyme (7+ 8 on separate card)(5053)
PR93 Identification: 11 test cells (IAT) 5053
PR93A Identification: 11 test cells IAT+ AC (5053)
PR93B Identification: 11 test cells IAT + I neg. (5053)
PR93C Identification: 10 test cells IAT (5053)
PR94A Identification: 11 test cellsP Enzyme (5052/5052)
PR94B Identification: 11 test cells (bromeline) (5052)
PR94C Identification: 11 test cells (papaine) (5052)
PR94E Identification: 11 test cells + AC (bromeline) (5052)
PR94F Identification: 11 test cells + AC (papaine) (5052)
PR94G Identification: 11 test cells + Ineg (bromeline) (5052)
PR94H Identification: 11 test cellsP + ACp (5052)
PR94I Identification: 11 cellsP + ACp IAT(5053)
PR94J Identification 11 cellsP IAT (5053)
PR95 Identification: 11 test cells saline (5052)

Host hook-up 2-17
PR95B Identification: 11 cells + AC Saline (5052/5052)
PY93 Identification: 11 test cells (IAT Anti- IgG ) (5054)
PY93A Identification:11 cells+AC (IAT Anti-IgG) 5054
SV02A Identification: Minipanel I-II-III-IV-V-VI IAT (5053)
SV02B Identification : Minipanel Ip-IIp-IIIp-IVp-Vp-VIp (5052)
ID-PaGIA Infectious disease tests
CHA1 Chagas Antibody (5046)
DIPH1 ID-Diphtheria toxin test (5080)
DSDNA ID-dsDNA Antibody test (5078)
HPF4 ID-Heparin/PF4 (5086)
SYPH1 ID-Syphilis Antibody Test (5100)
Newborns
MO30B Newborns: A-B-AB-D-ctl/AHG (DiaClon) (5007)
PR30B Newborns: A-B-AB-D-ctl/AHG (5006)
SV07 Newborns: A-B-AB-D-ctl/AHG (DiaClon) (5096)
Phenotyping
MO09A Phenotype : C-c-E-e-K-ctl DiaClon (5011)
MP6030 MP-Test : C-c-E-e-K-ctl (6030)
PR09 Phenotype: C-Cw-c-E-e-K (5012)
PR09A Phenotype: C-c-E-e-K-ctl (5010)
PR09B Phenotype: C-c-D-E-e-ctl (5013)
Doc N° H 009007 10.04 V3.2

2-18 Host hook-up
Reverse Group
PO04 Rev.group: A1-A2-B-O (O separate Coombs card) (5052/5053)
PR07 Rev.group: A1-A2-B (NaCl/Enzyme) 5052
PR07A Rev.group: A1-A2-B-O (O separate Card) (5052/5052)
PR07B Rev.group: A2-B-O (NaCl/Enzyme) 5052
PR07C Rev. group: A1-B-O (NaCl/Enzyme) 5052
PR08 Rev.group: A1-B (NaCl/Enzyme) 5052
SC02 Rev. group: B-A1(NaCl/Enzyme) 5052
Reverse Group + AS
CH04 Rev.group+AS : A1-A2-B/I-II-AHG (Enzyme/IAT) 5051
PO01 Rev.group + AS: A1-B-O/I-II-AHG (Enzyme/IAT) 5051
PR18 Rev.group + AS: A1-A2-B/O-I-II (Enzyme/IAT) (5051)
PR18A Rev.group+AS : A1-A2-B/I-II-III (Enzyme/IAT) (5051)
PR18C Rev.group + AS: A1-A2/B-Is-IIs-IIIs (NaCl/Enzyme) 5052
PR32A Rev.group. +AS: A1-A2/B-I-II-AC (Enzyme/IAT) (5051)
PR32B Rev.group + AS: A1-B-ACs/I-II-III (Enzyme/IAT) (5051)
06 - Card’s Results interpretation : This field contains a code identifying the interpretation of each
result segment used in the test. For valid identification tests 11 codes will be created. (see explanation
section “2.2.4.7 Segment results codes” on page 2-25).
07 - Microtubes modified in the reading : This field contains a code identifying microtubes, whose
results were modified by the operator. The format is the same as for the field 08. For each card used in the
current test one field is created.

Host hook-up 2-19
08 - Microtubes used in the test : This field identifies which microtube(s) of the ID card were used for
the test with the current sample. The software sends the results for all the microtubes on the ID card, even
if these are for different patients.
For example, one ID card can be used to perform the PR10 test (ABD-ABD) for samples of two patients.
Microtubes used in the test are referenced in a six-digit binary code as shown in the middle column in the
table below. In this code, the right-most digit corresponds to tube 1 and the left-most digit to tube 6. If a
digit has a value, this indicates that the corresponding microtube is assigned to the sample in question.
Hexadecimal code Binary code Tube position and number
01 000001 1
02 000010 2
03 000011 1 and 2
04 000100 3
05 000101 1 and 3
06 000110 2 and 3
07 000111 1, 2 and 3
08 001000 4
09 001001 1 and 4
0C 001100 3 and 4
0F 001111 1, 2, 3 and 4
10 010000 5
1F 011111 1, 2, 3, 4 and 5
20 100000 6
30 110000 5 and 6
38 111000 4, 5 and 6
3F 111111 all
The software sends one hexadecimal code representing this binary code (see left-hand column). For
example, if the first three microtubes are used for sample 1 and the last three for sample 2, it will send code
07 for sample 1 and code 38 for sample 2.
# Note: If you select this field and the test uses more than one ID card, the software will send an additional
field for the second ID card in the same data stream.
Doc N° H 009007 10.04 V3.2

2-20 Host hook-up
09 - Reading’s remarks : This field contains eventual remarks of the operator entered during validation.
10 - Operator : This field identifies the technician who performed the reading and validation.
11 - Microtubes result : This field contains the results for each of the microtubes in the current ID card.
If you select this field, the software sends six fields, one for each of the six microtubes. Empty microtubes
are tagged with “?”. If there are samples of two patients on the current card, the software sends the results
for both. To determine which microtubes were related to the test with the current sample, you must select
the Microtubes used in the test field (See field 08 on page 2-19).
# Notes :
• If you select this field using two cards for a test, the software sends six extra fields, one for each of the
microtubes for the second ID card.
• If the check box “Send * to modified ” is selected, the results which were modified by the operator will be
tagged with an asterisk (e.g.: |++++*|).
15 - Pipeting date and time : After importation of sampler data, this field contains the date of the
pipetting operation for the current ID card (format : dd/mm/ 00:00).
16 - Pipeting batch number : After importation of sampler data, this field contains the pipetting batch
number. For full details on the batch number, see the ID-Sampler manual.
17 - Reagents : This field consists of three kinds of fields :
• Reagent fields as much as used during pipetting with the sampler (No reagents ⇒ no field).
• Field for diluent 1 (No diluent 1 ⇒ empty field).
• Field for diluent 2 (No diluent 2 ⇒ empty field).

This parameter is combined with parameter 21 - Number of reagents used.
Example :
2|TypeR1 Code R1|TypeR2 Code R2| | |
18 - Card Order : If one ID card is used for the current test this field is |1|. If more ID cards are used, for
each card one field is created with the card number in the test (always in correct order, e.g.:|1|2|).
19 - Number of Cards Used : This field contains the number of ID cards used for the current test. Most
tests require a single ID card, but some tests (e.g. identification) require two. Cross-referenced tests with
auto-control (AC) also require two cards if the AC is not on the same ID card as the test itself.
20 - Date of Card interpretation : This field contains the date when the first reading of the current card
was carried out, and 00:00 (in order to be compatible with previous ID-Reader M versions which exported
also the time).
21- Number of reagents Used : This field contains the number of reagents used. (See example below
for 2 reagents used). This parameter is combined with parameter 17 - Reagents.
Example :
2|TypeR1 Code R1|TypeR2 Code R2|

Host hook-up 2-21
22 - Image Wells : This parameter contains six microtubes black and white pictures for the b and six
microtubes color pictures for the s. The format used is “jpeg”.
23 - Test Name : This field contains the name of the test performed on the current ID card (see the
second column of the interpretation list on page 2-10).
24 - Text of overall interpretation result : This field contains the overall interpretation result for the
current test. This will be the same as that printed by the software (e.g.: Group: 0 Rh (D) negative).
25 - Number of Test’s Segments : Field containing the number of segments of which the test
constitutes.
26 - Microplate’s line or column number : This field contains :

- The microplate's line number (1 to 12) for an horizontal type.
- The microplate's column number (1 to 8) for a vertical type.
2.2.4.2 Procedure
(1) (2) (3)
You can export data to the Host (see Fig. 10). To
select the fields in the order you want to export to,
use the following procedure.
[1] Select in the available fields area (1) the field you
want to export (see section “2.2.4.1 File description
for export” on page 2-10).
[2] Click on the Select (9) button.
! The field is moved to the selected fields area (8).
[3] Repeat the steps [1] and [2] until you have selected
all the fields you want to export.
# Notes: It is possible to select all the fields at one time

with the Select All button (7).
(9) (8) (7) (6) (5) (4)
Fig. 10: Export data
In the selected fields area (8), the order can be
changed with the arrow buttons (2) and (3), to move
a selected field up or down.
If you want to remove one field of the selected fields area (8), select the desired field and click on the
Delete button (6).
If you want to remove all the selected fields of the selected fields area (8), click on the Delete All button
(4).
[4] Click on the Output file type field (5) to choose DBASE (section “2.2.4.3 DBASE” on page 2-23),
DELIMITED (section “2.2.4.4 DELIMITED” on page 2-23), PARADOX (section “2.2.4.5 PARADOX” on
page 2-23) or SERIAL LINK (section “2.2.4.6 SERIAL LINK” on page 2-24).
Doc N° H 009007 10.04 V3.2

2-22 Host hook-up
Check boxes :
(10) (11)
• Automatic Export (10) : To export the data
automatically after each validation.
• Export Secondary Reading (14) : To export the
selected fields 02, 06, 07, 10, 11 and 24 with the
data obtained during secondary reading at the
end of the export file. Export after “primary
reading” means creation of empty fields.
• Send * to modified microtubes (11) : To tag the
data stream with an asterisk if a result for a
microtube has been modified by the operator.
• Send the empty donor field (13) : To send every
test with a donor field, either with donor ID or
empty (for example for tests which don’t use
donors).
(14) (13) (12)
• ASTM (American Society for Testing and
Fig. 11: Export data check boxes
Materials) (14). For more information about this
standard protocol, see www.astm.org.
# Note : If ASTM is checked, the selection of fields will be disabled.

Host hook-up 2-23
2.2.4.3 DBASE
The data will be exported as a DBASE file. You must

have a network connection.
With this type of output file, it is possible to transfer

pictures.
You must define the path and the name of the file to
be exported in the Path and file name field (1).
(1)
Fig. 12: Export with DBASE format
2.2.4.4 DELIMITED
The data will be exported as a file with a character of

delimitation. You can use a RS232 or a network
connection.
With this type of output file, it is not possible to

transfer pictures. You must define the path and the
name of the file to be exported in the Path and file
name field (3) plus the character of delimitation in
the Separator char field (2).
# Note : With this type of format, the field 22 - Image

Wells cannot be chosen.
(3) (2)
Fig. 13: Export with DELIMITED format
2.2.4.5 PARADOX
The data will be exported as a PARADOX file. You

must have a network connection.
With this type of output file, it is possible to transfer

pictures. You must define the path and the name of
the file to be exported in the Path and file name
field (4).
(4)
Fig. 14: Export with PARADOX format
Doc N° H 009007 10.04 V3.2

2-24 Host hook-up
2.2.4.6 SERIAL LINK
The data will be exported through the RS232 connection.
With this type of format, it is not possible to transfer pictures. You can choose the same options as for the
DELIMITED format (see section “2.2.4.4 DELIMITED” on page 2-23). No file will be created on the hard
disk as with DELIMITED.
# Note: With this type of format, the field 22 - Image Wells cannot be chosen.
You can set the serial port communication protocol

as described below. (1) (2) (3) (4) (5) (6)
(1) COM Port: Serial port of the PC. You can select the
values COM 1, COM 2, COM 3, COM 4, COM 5, and
COM 6.
(2) Speed : Baudrate in bytes/second. You can select
the values 300, 400, 1200, 2400, 4800, 9600, 19200,
38400, 57600 and 115200.
(3) Buffer size : It defines the size in bytes of the buffer
for the communication. You can select the values
1024, 2048, 4096, 8192, 16384 and 32768.
(4) Parity :
The parity describes a bit checking scheme. When
used, all of the bits in each data byte are added
together. A final bit, called the parity bit, is added so (13) (12) (11) (10) (9) (8) (7)
that the sum of all bits is either odd or even,
Fig. 15: Export with SERIAL LINK format
whichever you specify. The transmitter calculates
and transmits a parity bit. The receiver also
calculates a parity bit and compares it to the parity
bit received. If the bits are equal, it is assumed that the character was received without error. Otherwise, it
is assumed that there was an error during the transmission. The possible values for parity are :
• None : In this case, no flow control is used, no parity bit is added.

• Odd : The flow control is made by means of RTS and CTS streams. The M use the RTS stream
when it is able to receive and transmit when the CTS stream is activated. This flow control needs a 5
wires cable : ground; transmission; cross reception; CTS; RTS crossed. A parity bit is added so that the
bit sum is always odd.
• Even : The characters Xon (ASCII code 17) (8) and Xoff (ASCII code 19) (7) must be sent by the
receiver to the emitter to control the character emission flow. A parity bit is added so that the bit sum is
always even.
Xon : Starts data emission.
Xoff : Stops data emission.
A parity bit is added such that the bit sum is always even.
• Mark : A parity bit of value one is always added.
• Space : A parity bit of value zero is always added.
(5) Word size: 5, 6, 7 or 8
(6) Stop bits: 1 or 2

Host hook-up 2-25
Information about the flow control

(1) (2) (3) (4) (5) (6)
“Receive flow control” (9) stops a remote device from
transmitting while the local receive buffer is too full.
“Transmit flow control" (10) stops the local device
from transmitting while the remote receive buffer is
too full.
Receive flow control is enabled by including the

UseRTS and/or UseDTR elements in the options
set. When enabled, the corresponding modem
control signals (RTS and/or DTR) are lowered when
the input buffer reaches the level set by the
BufferFull property. The remote must recognize
these signals and stop sending data while they are
held low. Because there is usually little delay before
the remote can react (as there is with software flow
control) you can set BufferFull close to the input (13) (12) (11) (10) (9) (8) (7)
buffer size, perhaps at the 90% level.
Fig. 16: Export with SERIAL LINK format
As the application processes received characters,
buffer usage eventually drops below the value set by
the BufferResume property. At that point, the corresponding modem control signals are raised again. The
remote must recognize these signals and start sending data again. Again, because there is usually little
delay you can set BufferResume close to zero, perhaps at 10% of the input buffer size.
Transmit flow control is enabled by including the hwfRequireCTS and/or hwfRequireDSR elements in the
options set. With one or both of these options enabled, the Windows communications driver doesn’t
transmit data unless the remote device is providing the corresponding modem status signal (CTS and/or
DSR). The remote must raise and lower these signals when needed to control the flow of transmitted
characters.
# Note: Flow control using RTS and CTS (11) is much more common than flow control using DTR and
DSR (12).
Answer Time (13) : Determines how many seconds (30, 60, 90 or 120) the system waits for an answer
from the host before it gives the Time out message.
2.2.4.7 Segment results codes
Code structures
Results are coded on four characters. If the test result includes two segments, the software sends two
codes.
Example : For a PR01 test (group A-B-AB-D-CDE-ctl), there is a blood group result and a Rh result (D).
Here, then, we have two codes. Thus, if the result text reads, Group A Rh (D) positive, we would have a
result code of “1000 1001” (”1000” indicating “group A”, and “1001” indicating “Rh (D) positive”).
# Note: If the control or auto-control is positive or non-interpretable, the M sends a single code (e.g.
|ctl| non-interpretable! result invalid |??09)
Doc N° H 009007 10.04 V3.2

2-26 Host hook-up
Test-type codes
The first two characters (XX) in the code represent the result and the last two represent the type of test.
The following table lists all possible test-type codes (last two characters).
XX00 All Blood groups XX27 Poly
XX01 Rh (D) XX28 Direct Coombs (IgG)
XX02 Phenotype XX29 Not used
XX03 Kell XX30 Crossmatch
XX04 A1 XX31 Blood groups in crossmatch
XX05 H XX32 Minor crossmatch
XX06 Not used XX33 Syphilis
XX07 Not used XX34 HPF4
XX08 Not used XX35 Visceral Leishmaniasis
XX09 ctl XX36 Diphteria Toxin
XX10 Ab. screening Coombs XX37 dsDNA
XX11 Ab. screening Enzyme XX38 MDJ8
XX12 Ab. screening saline XX39 ID-PNH
XX13 Ab. screening (General) XX40 Identification
XX14 Not used XX50 ID sickle test
XX15 BAS test XX60 Antigen P1
XX16 Chagas XX61 Angigen Lea
XX17 Not used XX62 Antigen Leb
XX18 Autocontrol XX63 Antigen k (cellano)
XX19 Autocontrols XX64 Antigen Kpa
XX20 Direct Coombs XX65 Antigen Kpb
XX21 IgG XX66 Antigen Lua
XX22 IgA XX67 Antigen Lub
XX23 C3 XX68 Antigen Jka
XX24 C3d XX69 Antigen Jkb
XX25 C3c XX70 Antigen M
XX26 IgM XX71 Antigen N

Host hook-up 2-27
XX72 Antigen S XX100 Anti-D(II)
XX73 Antigen s XX101 D(III)/Dweak/D(+)(verify)
XX74 Antigen Fya XX102 Anti-D(IV)
XX75 Antigen Fyb XX103 Anti-D(V)
XX76 Antigen Cw XX104 Anti-D(VI)
XX77 Antigen B19 XX105 Anti-D(VII)
XX78 Antigen Xga XX106 Anti-D(FR)
XX79 Antigen Vel XX107 Anti-D(BT)
XX80 Antigen U XX108 Anti-RoHar
XX81 Antigen Tja XX109 Anti-RoHar/D(-)(verify)
XX82 Antigen Bg
XX83 Antigen Jsa
XX84 Antigen Jsb
XX85 Antigen Cob
XX86 Antigen Vw
XX87 Antigen Wra
XX88 Antigen Dia
XX89 Antigen Mia
XX90 IgG1
XX91 IgG3
XX92 Not used
XX93 Not used
XX94 Not used
XX95 Not used
XX96 Not used
XX97 Not used
XX98 Not used
XX99 Not used
Doc N° H 009007 10.04 V3.2

2-28 Host hook-up
Result codes, for all tests
Codes for blood group
The following tests use these codes : CH02, MO01, MO01B, MO01A, MO01C, MO02, MO10, MO10A,
MO12, PR01, PR01B, PR01C, PR10, SV06, MO11, PR11, SV03, SV04, SV05, SV08, MP6148, MP6749,
MO31, M031A, MO32, MP6040, MP6147, MP6238, MP6339, MP6437, MP6557, MP6540, MP6547,
MP6557, PR31, GE26, GE44, GE44A.
0000 Group: O
1000 Group: A
2000 Group: B
3000 Group: AB
1100 Group: A weak (verify)
2100 Group: B weak (verify)
3100 Group: AB (A weak) (verify)
3200 Group: AB (B weak) (verify)
3300 Group: AB weak (verify)
DP00 Group: double population (verify)
??00 Group : not interpretable
9009 ctl: positive! Result not valid
??09 ctl not interpretable !Result not valid
?100 Double population! (verify) Reverse Group: Group A
?200 Double population! (verify) Reverse Group: Group B
?300 Double population! (verify) Reverse Group: Group AB
3400 Group:A1
3500 Group: A2
3600 Group: A1B
3700 Group: A2B
3800 Group: A1B (B weak verify!)
3900 Group: A2B (B weak verify!)

Host hook-up 2-29
Codes for reverse group
The following tests use these codes : CH04, PO04, PR07, PR07A, PR07B, PR07C, PR08, SC02, PO01,
PR18, PR18A, PR18C, PR32A, PR32B.
0000 Group: O
1000 Group: A
2000 Group: B
3000 Group: AB
?000 Atypical reactions ! (verify)
9018 Autocontrol: positive! Result not valid
??18 Autocontrol : not interpretable !Result not valid
Doc N° H 009007 10.04 V3.2

2-30 Host hook-up
Codes for Rh(D)
The following tests use these codes : MO09E, PR09E, PR09H, PR09X, CH02, MO01, MOO1B, MO01C,
MOO1D, MO02, MO10A, MO12, PR01, PR01B, PR01C, PR10, SV06, MO11, PR11, SV04, SV08,
MP6148, MP6749, MO31, MO31A, MO32, MP6040, MP6147, MP6238, MP6339, MP6437, MP6537,
MP6540, MP6547, MP6557, PR31, GE26, GE44, GE44A.
0001 Rh (D): negative
1001 Rh (D): positive
0101 Rh (D): negative (C/E: positive)
2001 Rh (D): weak (Du!)
2101 Rh (D): weak! (Du!) (C/E: positive)
3001 Rh (D): probable DVI (verify)
3101 Rh (D): weak! (Du/DVI) (verify)
3201 Rh (D): positive, probable Dweak (Du) (verify!)
3401 Rh (D): weak! (Du!/DVI) verify , (C/E: positive)
DP01 Rh (D): double population! (verify)
0D01 Rh (D): negative ,C/E double population! (verify)
??01 Rh(D) : not interpretable
3701 Rh (D) : positive,probable DVI (verify)
3501 Rh(D) : (DVI-)
3801 Rh(D): weak (Du!) , probable DVI (verify)

Host hook-up 2-31
Codes for phenotype
The following tests use these codes : MO09A, PR09, MP6030, PR09A, PR09B.
??02 Phenotype : not interpretable
.002 Phenotype: cc..ee
.102 Phenotype: cc..Ee
.202 Phenotype: cc..EE
.302 Phenotype: Cc..ee
.402 Phenotype: Cc..Ee
.502 Phenotype: Cc..EE
.602 Phenotype: CC..ee
.702 Phenotype: CC..Ee
.802 Phenotype: CC..EE
1002 Phenotype: ccD.ee
1102 Phenotype: ccD.Ee
1202 Phenotype: ccD.EE
1302 Phenotype: CcD.ee
1402 Phenotype: CcD.Ee
1502 Phenotype: CcD.EE
1602 Phenotype: CCD.ee
1702 Phenotype: CCD.Ee
1802 Phenotype: CCD.EE
0002 Phenotype: ccddee
0102 Phenotype: ccddEe
0202 Phenotype: ccddEE
0302 Phenotype: Ccddee
0402 Phenotype: CcddEe
0502 Phenotype: CcddEE
0602 Phenotype: Ccddee
0702 Phenotype: CcddEe
0802 Phenotype: CcddEE
2002 Phenotype: ccDuee
2102 Phenotype: ccDuEe
Doc N° H 009007 10.04 V3.2

2-32 Host hook-up
2202 Phenotype: ccDuEE
2302 Phenotype: CcDuee
2402 Phenotype: CcDuEe
2502 Phenotype: CcDuEE
2602 Phenotype: CCDuee
2702 Phenotype: CCDuEe
2802 Phenotype: CCDuEE
.B02 Phenotype: CCw..ee
.A02 Phenotype: CCw..Ee
.902 Phenotype: CCw..EE
.E02 Phenotype: CCwc..ee
.D02 Phenotype: CCwc..Ee
.C02 Phenotype: CCwc..EE
DP02 Phenotype: double population! (verify)
Explanation :
The first character is for (D) 0 = negative,1 =positive,2 =low(Du!).
The second character is for the phenotype, and the same code is used for this list and the first phenotype
.0 = cc..ee
.1 = cc. Ee
.2 = Cc..EE
.3 = Cc..ee
.4 = Cc..Ee
.5 = Cc..EE
.6 = CC..ee
.7 = CC..Ee
.8 = CC..EE
Example 2502: 2 = Du! 5 = Cc..EE. Result = CcDuEE

Host hook-up 2-33
Codes for kell
The following tests use these codes : MO09A, MP6030, PR09, PR09A.
0003 Kell antigen: negative
1003 Kell antigen: positive
DP03 Kell: double population! (verify)
??03 Kell antigen : not interpretable
Doc N° H 009007 10.04 V3.2

2-34 Host hook-up
Codes for A1
The following tests use these codes : PR09C, PR09F.
0004 A1: negative
1004 A1: Possibly A1 negative, verify for A2
2004 A1: positive ++
3004 A1: positive +++
4004 A1: positive ++++
DP04 A1: double population! (verify)
???? Result : not interpretable

Host hook-up 2-35
Codes for H
The following tests use these codes : PR09D, PR09G.
0005 H: negative
1005 H: positive +
2005 H: positive ++
3005 H: positive +++
4005 H: positive ++++
DP05 H: double population! (verify)
Doc N° H 009007 10.04 V3.2

2-36 Host hook-up
Codes for antibody screening IAT
The following tests use these codes : CH04,CH05, CH05A, CH06, CH08, CH09, CH12, CH13, CH14,
GE01, GE15I, GE45, LUZ1, MO11, PR11, PR18A, PR21A, PR32A, PR32B, PR13C, PR13D, PR13E,
PR13G, PR13H, PR13I, PR13J, PR15A, PR15B, PR20, PR21A, PR21B, PR21C, PR21D, PR22, PR23,
PY15A, PY15B, SP04, SVO1, SV03, SV04, SV05, SVO8.
0010 Ab. screening IAT: negative
1010 Ab. screening IAT: positive
??10 Ab.screening IAT : not interpretable
0015 Bas-test negative
??15 Bas-test not interpretable
1015 Bas-test positiv

Host hook-up 2-37
Codes for antibody screening enzyme
The following tests use these codes : PR13C, PR13D, PR13E, PR13G, PR13H, PR15C, PR15D, PR15E,
PR15F, PR15I, PR20A, PR20B, PR21A, PR21B, PR21C, PR21D, SP01, SV01.
0011 Ab.screening Enzyme test:negative
1011 Ab.screening Enzyme test: positive
??11 Ab.screening Enzyme test : not interpretable
Doc N° H 009007 10.04 V3.2

2-38 Host hook-up
Codes for antibody screening saline test
The following tests use these codes : PR15G, PR15H, SPO2, SP03, PR18C.
1012 Ab.screening Saline test: positive
0012 Ab.screening Saline test : negative
??12 Ab.screening Saline test : not interpretable

Host hook-up 2-39
Codes for reverse group + AS
The following tests use these codes : PR18A, PR32A, PR32B.
??13 Ab.screening IAT : not interpretable
0013 Ab.screening IAT: negative
1013 Ab.screening IAT: positive
Doc N° H 009007 10.04 V3.2

2-40 Host hook-up
Codes for autocontrol
The following tests use these codes : PR70, PR70A, PR70B, PR70C, PR70D, PR70E, PR70F, PR70H,
PY70.
0018 Autocontrol : negative
1018 Autocontrol : positive
0019 Autocontrols: negative
0119 Autocontrol Enzyme: positive!
1019 Autocontrol IAT: positive!
1119 Autocontrols: positive!

Host hook-up 2-41
Codes for Direct Antiglobulin Test
The following tests use these codes : PR22, MO01B, MO01C, CH03, PR16A, PR16D, PR17, PY17, PY18,
CH04.
0020 DAT: negative
1020 DAT: positive
??20 DAT: not interpretable
0021 IgG: negative
1021 IgG: positive
??21 IgG : not interpretable
0022 IgA: neg./
1022 IgA: pos./
??22 IgA : not interpretable
0024 C3d: neg./
1024 C3d: pos./
??24 C3d : not interpretable
0025 C3c: neg./
1025 C3c: pos./
??25 C3c : not interpretable
0026 IgM: neg./
1026 IgM: pos./
??26 IgM : not interpretable
0028 DAT(IgG): negative
1028 DAT (IgG): positive
??28 DAT IgG : not interpretable
1121 Weak positive IgG: Low risk of haemolysis
2121 DAT IgG+: important risk of haemolysis
1190 Moderate risk of haemolysis (IgG1 weak concentration)
1191 Moderate risk of haemolysis (IgG3,weak concentration)
2190 Important risk of haemolysis (IgG1, high concentration)
2191 Important risk of haemolysis (IgG3,high concentration)
Doc N° H 009007 10.04 V3.2

2-42 Host hook-up
Codes for cross-referenced tests
The following tests use these codes : MO81, MO82, PR80, PR80A, PR80B, PR80D, PR80E, PR80F,
PR80H, PR80I, PR81, PY80, PY80D.
0030 Crossmatch: compatible
1030 Crossmatch: not compatible
?030 Crossmatch :not interpretable
By blood group tests codes
The following tests use these codes : MO82, MO81, PR81.
0031 Blood Group: compatible
1031 Blood Group: not compatible
Codes for minor crossmatch
The following tests use these codes : PR80G, PY80G.
0032 Minor crossmatch : compatible
/032 Minor crossmatch : not compatible
?032 Minor crossmatch : not interpretable

Host hook-up 2-43
Identification codes
The following tests use these codes : CH10, CH11, PR93, PR93A, PR93B, PR93C, PR94A, PR94B,
PR94C, PR94E, PR94F, PR94G, PR94H, PR94I, PR94J, PR95, PR95B, PY93, PY93A, SV02A, SV02B.
0040 Test cell negative
1040 Test cell positive
Doc N° H 009007 10.04 V3.2

2-44 Host hook-up
Codes for Haemoglobinemia
The following tests use this codes : PR50, PR51.
0050 Hbs: negative
1050 Hbs: positive
DP50 Hbs: double population! (verify)
??50 Hbs : not interpretable
??39 PNH : not interpretable
0039 PNH negative
1039 PNH positive
2039 PNH weak
# Note: The b and the s cannot interpret double population (for security reasons). If a microtube
contains a double population, the M will register a question mark, and the user will be asked to click
on the microtube to give the result. A double population in this test will be considered as positive.

Host hook-up 2-45
Codes for single antigen
The following tests use these codes : MO44D, PR44A, PR44B, PR44C, PR44D, PR44E, PR44F, PR44G,
PR44H, PR441, PR44J, PR44K, PR44M, PR44N, PR44O, PR44P, PR44S, PR44T, PR44U, PR44V,
PR44W, PR44X, PO07, PR41A, PR42A, PR43, PR44Q, PR44R.
??76 Cw antigen : not interpretable
0076 Cw antigen: negative
1076 Cw antigen: positive
??74 Fya antigen : not interpretable
0074 Fya antigen: negative
1074 Fya antigen: positive
??75 Fyb antigen : not interpretable
0075 Fyb antigen: negative
1075 Fyb antigen: positive
??68 Jka antigen : not interpretable
0068 Jka antigen: negative
1068 Jka antigen: positive
??69 Jkb antigen : not interpretable
0069 Jkb antigen: negative
1069 Jkb antigen: positive
0063 k (cellano) antigen: negative
1063 k (cellano) antigen: positive
??63 k(cellano) antigen:not interpretable
??03 Kell antigen : not interpretable
0003 Kell antigen: negative
1003 Kell antigen: positive
DP03 Kell: double population! (verify)
??64 Kpa antigen : not interpretable
0064 Kpa antigen: negative
1064 Kpa antigen: positive
0065 Kpb antigen: negative
1065 Kpb antigen: positive
??65 Kpb antigen:not interpretable
0061 Lea antigen: negative
Doc N° H 009007 10.04 V3.2

2-46 Host hook-up
1061 Lea antigen: positive
??61 Lea antigen:not interpretable
0062 Leb antigen: negative
1062 Leb antigen: positive
??62 Leb antigen:not interpretable
0066 Lua antigen: negative
1066 Lua antigen: positive
??66 Lua antigen:not interpretable
??67 Lub antigen : not interpretable
0067 Lub antigen: negative
1067 Lub antigen: positive
??70 M antigen : not interpretable
0070 M antigen: negative
1070 M antigen: positive
??71 N antigen : not interpretable
0071 N antigen: negative
1071 N antigen: positive
??60 P1 antigen : not interpretable
1060 P1 antigen : positive
0060 P1 antigen: negative
??73 s antigen : not interpretable
??72 S antigen : not interpretable
0073 s antigen: negative
0072 S antigen: negative
1073 s antigen: positive
1072 S antigen: positive
??81 Tja antigen : not interpretable
0081 Tja antigen: negative
1081 Tja antigen: positive
??80 U antigen : not interpretable
0080 U antigen: negative
1080 U antigen:positive
??79 Vel antigen : not interpretable

Host hook-up 2-47
0079 Vel antigen: negative
1079 Vel antigen: positive
??78 Xga antigen : not interpretable
0078 Xga antigen: negative
1078 Xga antigen: positive
0077 B19 antigen : negative
??77 B19 antigen : not interpretable
1077 B19 antigen : positive
Doc N° H 009007 10.04 V3.2

2-48 Host hook-up
Codes for Newborns
The following tests use these codes : MO30B, PR30B, SV07.
0000 Group: O
1000 Group: A
2000 Group: B
3000 Group: AB
0001 Rh (D): negative
1001 Rh (D): positive
2001 Rh (D): weak (Du!)
DP01 Rh (D): double population! (verify)
??01 Rh(D) : not interpretable
0020 DAT: negative
1020 DAT: positive
??20 DAT: not interpretable

Host hook-up 2-49
Codes for Pagia infectious diseases tests
The following tests use these codes : CHA1, DIPH1, DSDNA, HPF4, SYPH1.
??16 Chagas : not interpretable
0016 Chagas: negative
1016 Chagas: positive
2016 Chagas: weak positive
0036 Diphteria toxin : negative
??36 Diphteria toxin : not interpretable
1036 Diphteria toxin : positive
2036 Diphteria toxin : strong positive
0037 dsDNa antibody : negative
??37 dsDNA antibody : not interpretable
1037 dsDNA antibody : positive
2037 dsDNA antibody : strong positive
0034 HPF4 : negative
??34 HPF4 : not interpretable
1034 HPF4 : positive
2034 HPF4 : strong positive
0033 Syphillis : negative
??33 Syphillis : not interpretable
1033 Syphillis : positive
2033 Syphillis : strong positive
Doc N° H 009007 10.04 V3.2

2-50 Host hook-up

Index X-1
A Identification 2-16
Reverse Group 2-18
R
A1 2-34 Reverse Group + AS 2-18 Reverse Group 2-14, 2-18
Antibody screening 2-10, 2-36, Test-type codes 2-26 AS 2-18, 2-39
2-37, 2-38 Export 2-10 Code for 2-28
Antigen 2-12 DBASE 2-23 Rh (D) 2-21, 2-25
profile 2-13 DELIMITED 2-23 Codes for 2-30
single 2-45 PARADOX 2-23 Test-type codes 2-26
ASTM 2-22 SERIAL LINK 2-24 RS232 2-1, 2-7, 2-8, 2-23, 2-24
Auto-control 2-20, 2-25
F S
B File structure 2-2 Saline
Blood group 2-2, 2-13, 2-14, Autocontrol 2-13
2-25, 2-26, 2-42
codes for 2-28
H Codes for antibody scree-
ning 2-38
H Sickle
C Codes for 2-35 Haemoglobinemia 2-16
Hardware connection 2-1 Software
Chagas 2-17
Communication 2-2
codes for 2-49
Test-type codes 2-26
I Product 1-2
Syphilis
Checksum 2-2, 2-3 Identification 2-16
ID-PaGIA Infectious disease
Coombs Card’s Results interpretation tests 2-17
Ab.screening 2-26 2-18
Test-type codes 2-26
Direct 2-26 Codes 2-43
Document 1-1
Reverse Group 2-18
Donor field 2-5 T
Copyright I-2
Number of Cards Used 2-20 Typographic conventions 1-3
Crossmatch 2-15
Sample field 2-5
Codes for cross-referenced
tests 2-42 Test field 2-5
Codes for minor crossmatch Test-type codes 2-26
2-42 Import 2-5
Donor identification 2-10 DBASE 2-7
File structure 2-2 DELIMITED 2-7
Test-type codes 2-26 PARADOX 2-7
SERIAL LINK 2-8
D
Diphtheria
K
ID-PaGIA Infectious disease Kell 2-26, 2-33
tests 2-17
Document number 1-1
N
E Network 2-1, 2-7, 2-23
Newborns 2-17, 2-48
Enzyme 2-10
Antibody Screening 2-10
Autocontrol 2-13
P
Codes for antibody scree- Phenotype 2-17, 2-26, 2-31
ning 2-37
Codes for autocontrol 2-40
Crossmatch 2-15
Doc N° H 009007 10.04 V3.2

Host Service GB v32

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Host Service GB v32

Transféré par

Droits d'auteur :

Formats disponibles

H 009007 10.

Micro Typing System

AT THE READER’S ATTENTION

Host - Connections for M

2 HOST HOOK-UP ................................................................................... 2 - 1

Doc N° H 009007 10.04 V3.2

Host - Connections for M

Host connections for M.

Version 3.2 October 2004

Document No. : H 009007

CH-1785 Cressier sur Morat

Tel. ++41 (0)26 / 674 51 11

Fax ++41 (0)26 / 674 51 45

1.1.2 Limited warranty

Doc N° H 009007 10.04 V3.2

1.2 Chapter overview

1.3 Appropriate use

The software is the M.

Host - Connections for M

1.5 Typographic conventions

(1) First item

Procedure effects style

The procedure effects are described by using the following symbol !.

[1] Click on the Add one item button to select it.

Doc N° H 009007 10.04 V3.2

Cross references style

" See page x-y.

List of items style

This style is used to give a list of items.

Host - Connections for M

$ Take care about ...

% Never open this cover

Doc N° H 009007 10.04 V3.2

Host - Connections for M

2.1.1 RS 232 line

The wiring between the 9-pin RS232 connectors is

On a 25-pin RS232 connector, the wiring is as

# If you enable hardware flow control (by checking the

Doc N° H 009007 10.04 V3.2

2.2 Software communication

- Data transfer from Readers or M :

STX Data Checksum ETX

- Reply from host computer if data is correct.

STX OK Checksum ETX

- Reply from host computer if data is incorrect.

STX ER Checksum ETX

Host - Connections for M

Example: [STX] PR13C|45516256|+++|++|+++|-|-|-|08/07/1999 13:36|[CR][LF] 6D [ETX]

I = 124 I = 124 I = 124

+ = 43 0 = 48 [CR] = code ASCII $0D = 13

+ = 43 8 = 56 [LF] = code ASCII $0A = 10

3181 = C6D = 6D (Checksum)

# Note: CR and LF are also taken in the addition

Doc N° H 009007 10.04 V3.2

2.2.2 Selection of the configuration windows

To configure the import and/or export settings,

[1] Select the System Settings command from the

Fig. 3: System Settings window

Host - Connections for M

2.2.3.1 File description for import

Obligatory added fields :

• First field : Test identification