ALI Alimic TM Mic Interfacing-manual-with-Astm 1-3 en

Microbiology Interfacing Manual
Rev.1.3 – 2020.06.15
Interfacing Manual
(Include also ASTM configuration from
Sw 02.11 onward)
 Copyright 2020
This document is exclusive property of ALIFAX s.r.l. confidential and not freely disclosable.
All rights reserved
MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 1

Rev.1.3 – 2020.06.15
General Index
1 INTRODUCTION ...................................................................................................................... 3
2 INSTRUMENT PHSYCAL REAR COM PORTS IDENTIFICATION ................................................ 3
3 PARTS TO INSTALL .................................................................................................................. 3
3.1 SERIAL COMMUNICATION ........................................................................................................... 3
3.2 LAN COMMUNICATION ................................................................................................................ 4
4 COMMUNICATION SET-UP ...................................................................................................... 4
5 SERIAL COMMUNICATION PROTOCOL (ALFRED60 AND HB&L) ............................................. 5
5.1 COMMUNICATION PROTOCOL ..................................................................................................... 7
5.2 INTEGRATED PROTOCOL ............................................................................................................. 7
5.3 FIELD #4 SPECIFICATIONS ......................................................................................................... 8
5.3.1 Completion mode ................................................................................................................... 8
5.3.2 No vial matching..................................................................................................................... 8
5.3.3 Vial matching ......................................................................................................................... 8
5.4 FIELD #6 SPECIFICATIONS ......................................................................................................... 9
5.5 SPECIFICATION OF QUERY PROTOCOL (ONLY FOR ALFRED60) ................................................... 13
5.5.1 Definition of Special Characters ............................................................................................. 13
5.5.2 QUERY PROTOCOL specifications .......................................................................................... 13
5.5.3 QQ Record ........................................................................................................................... 13
5.5.4 QA Record ........................................................................................................................... 14
5.5.5 Query communication protocol .............................................................................................. 14
5.5.6 Start of communication ......................................................................................................... 14
5.5.7 Data exchange ..................................................................................................................... 15
5.5.8 End of communication .......................................................................................................... 15
5.5.9 Communication example ....................................................................................................... 15
6 LAN COMMUNICATION ASTM - PROTOCOL (ALFRED60 AND HB&L) .................................... 16
6.1 RECORDS SUMMARY ................................................................................................................. 16
6.2 RECORDS MANAGEMENT ........................................................................................................... 16
6.3 RECORDS IMPLEMENTATION ..................................................................................................... 17
6.3.1 Message Header Record ........................................................................................................ 17
6.3.2 Patient Information Record ................................................................................................... 17
6.3.3 Test Order Record ................................................................................................................ 18
6.3.4 Result Record ....................................................................................................................... 19
6.3.5 Request Information Record .................................................................................................. 20
6.3.6 Message Terminator Record .................................................................................................. 20
7 CONNECTION OF 2 OR MORE INSTRUMENTS TO THE SAME HOST ...................................... 21
7.1 SERIAL COMMUNICATION ......................................................................................................... 21
7.2 LAN COMMUNICATION .............................................................................................................. 21
8 REFERENCES ......................................................................................................................... 22
Note:
The paragraphs coloured in blue, have been added or modified respect to the previous version
We reserve the right to make changes in the course of technical development without previous
notice.
Neither this manual nor any parts of it may be duplicated or transmitted in any way without the written
approval of Alifax S.r.l.

Rev.1.3 – 2020.06.15
1 INTRODUCTION
This manual is focused to give detailed information about Ports and Connections available on HB&L, Alfred60
and Sidecar and communication protocol features.
It should help Software House Companies during the modification or the installation of their program in
the Host Computer.
2 INSTRUMENT PHSYCAL REAR COM PORTS IDENTIFICATION
Both HB&L and Alfred 60 (till serial numbers: UQ4377W / UQ4203WL and A60304W) have in the rear side 2
DB9 COM Ports identified as:
 COM-1: This is the port used to connect instrument to Host (Serial communication)
 COM-2: This is the port used to interconnect Alfred to HB&L or Sidecar to HB&L [Not more used]
ATTENTION: From SW version 2.11 the interconnection between Alifax‟s instruments is performed
by the LAN Port
 LAN: This is the port used to connect instrument to Host (LAN communication)
Both HB&L and Alfred 60 (from serial numbers: UQ4378W / UQ4204WL and A60305W) have in the rear side
2 DB9 COM Ports identified as:
 COM-3: This is the port used to connect instrument to Host (Serial communication)
 COM-2/4: [Not used]
ATTENTION: From SW version 2.11 the interconnection between Alifax‟s instruments is performed
by the LAN Port
 LAN: This is the port used to connect instrument to Host (LAN communication)
Please notice Sidecar itself does not have any communication port, Sidecar goes through Alfred.
3 PARTS TO INSTALL
3.1 SERIAL COMMUNICATION
Serial DB9/DB9 Null Modem Cable that must have:

D-type 9 pin female connector at one side and a D-type 9 pin female (all the three instruments have a DB9
com port).
Following cable is assumed based on the fact that, also on Host side there is a DB9 port, eventually the Host
side could be different, so depending the configuration on Host side, one edge could be different.
Software House has the responsibility for the cable.

Rev.1.3 – 2020.06.15
3.2 LAN COMMUNICATION
Standard LAN Cable to connect instrument to Host (LAN port), eventually the Host side could be different,
so depending the configuration on Host side, one edge could be different.
Software House has the responsibility for the cable.
4 COMMUNICATION SET-UP
Communication set-up is similar for both Alfred60 and HB&L; parameters are located in Tools  Setup 
Advanced Setting (password)  Host Connection.
This section is divided in 3 pages: “Host Connection”, “Transmission Content” and “Advanced”
Inside “Connection Type”, select one type of protocol, in order to communicate with the Host:
 Integrated protocol: In order to use a Serial communication protocol
 ASTM protocol: In order to use a LAN communication protocol
For further information, please see the appropriate chapter inside the Technical Manual.

Rev.1.3 – 2020.06.15
5 SERIAL COMMUNICATION PROTOCOL (ALFRED60 AND HB&L)
The system is provided with 4 serial ports, these ports are the ones visible in Windows Control Panel
configuration setup, please don‟t confuse COM1 (on back side of the instruments) with COM1 of “Windows”
setup.
Both HB&L and Alfred 60 (till serial numbers: UQ4377W / UQ4203WL and A60304W) have in the rear side
DB9 COM Ports identified as: COM1 to be connected to HOST
COM 1
From serial numbers: UQ4378W / UQ4204WL and A60305W, both HB&L and Alfred 60 have in the rear side
DB9 COM Ports identified as:
 COM-3:This is the port used to connect instrument to Host (Serial communication)
ALFRED stand alone (and ALFRED mounted on Sidecar) from instrument Sn

A60305W:
 Be sure to connect LAN cable to port identified as ETH1

 Be sure to connect the HOST cable to port identified as COM3; to identiìfy the port “COM3”
please refer directely to the string “COM3” prinded near the DB9 port

Rev.1.3 – 2020.06.15
HB&L (from instrument Sn UQ4378W and UQ4204WL):
 Be sure to connect the HOST cable to port identified as COM3

 Be sure to connect LAN cable to port identified as ETH1
Following tables resumes the “Windows” configurations visible from Regedit
HB&L: till instrument Sn UQ4377W and UQ4203WL:
PORT DESCRIPTION SETTINGS

COM1 Communication with host computer 9600,8,n,1
* COM2 Communication with Alfred [Not more used] 2400,8,n,1
COM3 none N/A
COM4 Internal printer 1200,8,n,1
HB&L: from instrument Sn UQ4378W and UQ4204WL:

COM1 Internal printer 9600,8,n,1
COM2 none 2400,8,n,1
COM4 none 9600,8,n,1
ALFRED: from instrument Sn A60304W:

COM9 Internal Communication 2400,8,n,1
* COM8 Communication with HB&L [Not more used] 2400,8,n,1
COM10 Communication with Sidecar 9600,8,n,1
ALFRED: from instrument Sn A60305W:

*: Remember that from Software version 2.11, the interconnection between Alifax‟s instruments is
performed by the LAN Port and not more by the COM Port 2.

Rev.1.3 – 2020.06.15
DATA STRUCTURE
Data may be exchanged in record with two different structures:
Type
# Description Length
1 Sample ID 20
2 Surname 20
3 Name 20
4 Bacterial count 20
5 RAA/MDRO test 20
6 FIELD #6 20
ID code of Integrated Protocol type structure supports up to 15 factual characters
The last character of fields 1,2,3,4,5 must be '@' (ASCII 64 = 0x40)
The last character of field 6 must be LF (ASCII 10 = 0x0A)
DEFINITIONS ABBREVIATION ASCII CODE Hexadecimal
SOH 0x01
ACK 0x06
NAK 0x15
EOT 0x04
LF 0x0A
5.1 COMMUNICATION PROTOCOL

The communication with the host computer may be set in three different modes:
Description Record format Transmission medium
INTEGRATED B Type Serial
5.2 INTEGRATED PROTOCOL

Communication parameters setup
Speed 9600 baud

Parity None
Stop bit 1
Length 8 bit
COM port COM 1
Communication description
HOST sends SOH to INSTRUMENT:
If INSTRUMENT is ready it answers ACK
If INSTRUMENT is NOT ready it answers NAK
If INSTRUMENT is NOT ACTIVE it doesn‟t send any character
Note: Character SOH resets data received by INSTRUMENT, if character SOH is not sent,
the data received by INSTRUMENT are appended to previous ones.
If INSTRUMENT answers NAK, the HOST can repeat the transmission after 5 seconds or more.
If INSTRUMENT answers ACK, the HOST can send the string of 120 bytes, which must terminate
by LF.
INSTRUMENT after reception of string answers ACK, if transmitted data are accepted or NAK if
NOT accepted; if INSTRUMENT answers NAK, the HOST can repeat the transmission of string.
When HOST decides to stop the communication it sends EOT and INSTRUMENT answers ACK.
When the INSTRUMENT sends the results to the HOST computer, it uses the same
control technique. Thus host computer must be provided with a suitable data exchange
program.
Each field is terminated by ‟@‟, while the last field which represents also the end of record is
terminated by LF (hexadecimal &0A).

Rev.1.3 – 2020.06.15
5.3 FIELD #4 SPECIFICATIONS
The FIELD #4 of data record, which wasn't used in previous versions, from Sw version 2.7
onwards is used to send and get additional information about the sample and the analysis that were not
foreseen in the past.
This feature is required in case the Matching ID feature is used by the end user.
This field will be used ONLY in working list delivery from Host to INSTRUMENT (See paragraph “Vial
Matching” here below). The same field is used by the INSTRUMEN to send back the resukt and contains the
Bacterial Count
From the software version 2.7 has been introduced the ID MATCHING function, that allows to
associate (link) a culture vial with an already assigned reference ID (QR bi-dimensional code) to
each primary sample.
5.3.1 Completion mode

Alfred works exclusively in “completion mode”, which means that host sends a pool of patient
information which Alfred can use to complete the information of the samples being analysed.
HB&L must work in “completion mode” if the laboratory needs to keep track of the vials by means of the 2D
barcode printed on the vials themselves (“Vial Matching” feature). For HB&L, the “completion mode” must
be explicitly specified in the Setup.
5.3.2 No vial matching

If the “Vial Matching” feature is not used, the protocol remains the same as before this means Field 4 empty
Field Field Info Description Notes

#
1 Sample ID ID of the original sample MANDATORY
2 Surname Patient surname OPTIONAL
3 Name Patient name OPTIONAL
4 IGNORED
5 IGNORED
6 IGNORED
5.3.3 Vial matching

When working with profiles in “Vial Matching” mode, host must send the following information:
Field Field Info Description Notes

#
1 Sample ID ID of the original sample MANDATORY
2 Surname Patient surname OPTIONAL
3 Name Patient name OPTIONAL
4 Vial ID 2D barcode of the vial MANDATORY with “External Vial Matching”
IGNORED otherwise
5 Patient ID ID of the patient OPTIONAL
6 Not Used
In this case Host must send in the working list the field 4 filled up with a specific numerical sequence here
below explained.

Rev.1.3 – 2020.06.15
The sequence is introduced in the working list by the reading the QR univocal code linked to each colture
vial.
QR code contains all the information about the

 Reagent
 Lot
 Progressive vial number
And it is developed in the below described sequence
Example: 8…16004.12345
CODE OF THE CULTURE KIT VIAL ID NUMBER
SEPARATION POINT SEPARATION POINT
EMPTY FIELDS LOT NUMBER
Host must send in the working list the field 4 filled up with the numerical sequence above explained; the
sequence MUST be fully respected including the dots between the numbers.
5.4 FIELD #6 SPECIFICATIONS
The FIELD #6 of data record, which wasn't used in previous versions, is used in this version to send and get
additional information about the sample and the analysis that were not foreseen in the past.
RECEPTION
During patient data reception, it is possible to fill in the FIELD #6 in order to send information about
the type of test to perform on the sample and the biological material the sample is made of; if this
field is filled in, the software will verify the matching among the type of material communicated and
the one actually inserted; in case of mismatch, the software will issue an error and the introduction
will be refused.
TRANSMISSION
For results transmission, the software provides these options:
URINE AND OTHER HUMAN BIOLOGICAL LIQUIDS:

- Normal transmission (compatible with previous software versions)
- "Rich" transmission (FIELD #6 is filled in)
SUSCEPTIBILITY TEST:
- Results transmission disables
- Results transmission enabled (filling in of FIELD #6 is required)
HUMAN BIOLOGICAL LIQUIDS:

MDRO TEST:

Rev.1.3 – 2020.06.15
RECORDS SEQUENCE
For BACTERIAL GROWTH, RAA TEST and MDRO TEST, each test will be described by one record.
For SUSCEPTIBILITY TEST, each test will be described by N+1 records, where N is the number of antibiotics
tested onto the sample.
Record 1 : relevant to reference vial
Records from 2 to N+1 : relevant to each tested antibiotic
ADDITIONAL FIELD #6 FORMAT

Here follow the specifications for FIELD #6
NAME LEN DESCRIPTION VALUES
Exam Type 1 Type of exam to be 'S': bacterial growth
performed on the sample 'P': bacterial growth + RAA test
'K': susceptibility test
'T': MDRO bacterial growth
'O': MDRO bacterial growth (Primary Tube)
Biological 1 Biological Material Type of FOR ALL TESTS
Material the sample A Urine
Type B Broncho alveolar lavage
C Orotracheal aspiration
D Expectoration
E Cerebrospinal fluid
F Pleural fluid
G Synovial fluid
H Ascitic fluid
I Peritoneal fluid
J Bronchial aspirate
K Positive Hemoculture
M Cutaneous swab (Dry)
N Inguinal swab (Dry)
O Nasal swab (Dry)
P Oral swab (Dry)
Q Pharyngeal swab (Dry)
R Rectal swab (Dry)
S Tracheal swab (Dry)
T Vaginal swab (Dry)
U Wound swab (Dry)
V Other swab (Dry)
W Subculture
X Central Venous Catheter
a Cutaneous swab (Liquid)
b Inguinal swab (Liquid)
c Nasal swab (Liquid)
d Oral swab (Liquid)
e Pharyngeal swab (Liquid)
f Rectal swab (Liquid)
g Tracheal swab (Liquid)
h Vaginal swab (Liquid)
i Wound swab (Liquid)
j Other swab (Liquid)
Antibiotic 3 Antibiotic tested FOR SUSCEPTIBILITY TEST
'#R#' : reference sample
801 Amikacin / CL
802 Amoxicillin-Clavulanate Staphylococci / CL
803 Ampicillin Enterobacteriaceae / CL
804 Ampicillin Enterococci / CL
805 Aztreonam Enterobacteriaceae / CL
806 Aztreonam Pseudomonas / CL
807 Cefotaxime Enterobacteriaceae / CL
809 Cefoxitin Staph. aureus / CL
810 Cefoxitin CNS / CL
811 Ceftazidime Enterobacteriaceae / CL
812 Ceftazidime Pseudomonas / CL
813 Ceftriaxone Enterobacteriaceae / CL
815 Cefuroxime Enterobacteriaceae / CL

Rev.1.3 – 2020.06.15
817 Ciprofloxacin / CL
818 Clindamycin Staphylococci / CL
820 Cotrimoxazole / CL
821 Fosfomycin / CL
822 Gentamicin / CL
823 Levofloxacin / CL
824 Linezolid / CL
825 Meropenem Enterobacteriaceae / CL
826 Meropenem Pseudomonas / CL
828 Norfloxacin / CL
829 Oxacillin Staph. aureus / CL
830 Piperacillin-Tazobactam Enterobacteriaceae / CL
831 Piperacillin-Tazobactam Pseudomonas / CL
832 Teicoplanin Staphylococci / CL
833 Teicoplanin Enterococci / CL
834 Vancomycin Staph. aureus / CL
835 Vancomycin CNS and Enterococci / CL
910 Fosfomycin
911 Cotrimoxazole
912 Amikacin
913 Gentamicin
915 Oxacillin (Staph .aureus)
916 Ciprofloxacin
919 Ceftazidime
922 Ampicillin G+ Enteroc.
925 Piperacillin-Tazobactam
926 Aztreonam
927 Levofloxacin
930 Vancomycin
931 Cefuroxime
932 Norfloxacin
933 Ceftriaxone
934 Linezolid
937 Cefotaxime
938 Amoxicillin-Clavulanate for Staphylococcus
939 Ampicillin
940 Cefoxitin (Staph. aureus)
941 Cefoxitin (SCN)
942 Meropenem
943 Clindamycin for Staphylococcus
945 Teicoplanin
947 Ceftazidime for Enterobacteriaceae
949 Ceftazidime Enterobacteriaceae / EU
950 Ceftazidime Pseudomonas / EU
951 Ceftriaxone / EU
952 Piperacillin-Tazobactam Pseudomonas / EU
953 Piperacillin-Tazobactam Enterobacteriaceae / EU
954 Ampicillin Enterobacteriaceae / EU
955 Ampicillin Enterococci / EU
956 Amikacin Enterobacteriaceae / EU
957 Aztreonam Enterobacteriaceae / EU
959 Cefotaxime / EU
960 Cefuroxime / EU
961 Cefoxitin Staph. aureus / EU
962 Cefoxitin CNS / EU
963 Ciprofloxacin / EU
964 Clindamycin Staphylococci / EU
965 Cotrimoxazole Enterobacteriaceae / EU
967 Gentamicin / EU
968 Gentamicin Staphylococci / EU
969 Levofloxacin / EU
970 Linezolid / EU
971 Meropenem Enterobacteriaceae / EU
973 Vancomycin S. aureus / EU
974 Vancomycin CNS and Enterococci / EU

Rev.1.3 – 2020.06.15
975 Teicoplanin S. aureus and Enterococci / EU

976 Teicoplanin CNS / EU
977 Cotrimoxazole Enterococci / EU
978 Amikacin Pseudomonas / EU
979 Meropenem Pseudomonas / EU
981 Amikacin Staphylococci / EU
982 Cotrimoxazole Staphylococci / EU
983 Colistin Pseudomonas / EU
984 Colistin Enterobacteriaceae / EU
996 Rifampicin / EU
997 Ampicillin-Sulbactam Enterobacteriaceae / EU
999 Gentamicin HLAR / EU
FOR OTHER TEST

''
Time 4 Elapsed analysis time FOR ALL TESTS
'hhmm'
hh = hours
mm = minutes
Charge 4 Bacterial charge detected FOR ALL TESTS
'xyzz'
It corresponds to a charge of
x.yEzz CFU/ml
Ex: 1205 means a
1.2E05 = 120.000 CFU/ml charge
Sample 1 Information on sample FOR ALL TESTS
Information status 'M' : missing sample
'T' : turbid sample
'A' : stirring not ok
'A' : abnormal sample
'E' : cancelled sample
'E' : invalid sample
' ' : normal sample
Analysis 1 Clinical result for RAA test FOR RAA TEST
result and SUSCEPTIBILITY test '#' : at least one of the two vials is missing
'+' : RAA test positive
'-' : RAA test negative
'?' : unknown
SUSCEPTIBILITY TEST
' ' : reference sample
'L' : reference inoculation less that 700.000 CFU/ml
'S' : sensitive
'I' : intermediate
'R' : resistant
'E' : error in calculation of resistance / sensitivity to the antibiotic
'?' : unknown
MDRO TEST
'P' : MDRO test positive
'N' : MDRO test negative
'E' : invalid, error is sample/supplement inoculation
'?' : unknown
OTHERS TESTS
''
Resistance 3 % of resistance of SUSCEPTIBILITY TEST
bacterium against 'xxz' : % expressed as xx.z%
antibiotic Ex: '051' --> 5.1 %
'569' --> 56.9 %
'CCC' : resistance = 100%
'NV ' : error in the calculation of resistance to the antibiotic
OTHER TESTS
''
Spare 1 Not used ''

Rev.1.3 – 2020.06.15
5.5 SPECIFICATION OF QUERY PROTOCOL (ONLY FOR ALFRED60)

The Query communication for Alfred for Windows allows the Alfred instrument to query the LIS in order to
obtain information related to the samples loaded into the instrument itself.
This document defines the specifications of the records used in the communication and the data exchange
protocol.
5.5.1 Definition of Special Characters

STX ASCII Character 0x02
ETX ASCII Character 0x03
SOH ASCII Character 0x01
EOT ASCII Character 0x04
ACK ASCII Character 0x06
NAK ASCII Character 0x15
FIELD_CHAR Field separation character. Character * (ASCII 0x2A)
ESCAPE_CHAR Escape sequence character (see examples for better comprehension)
Character | (ASCII 0x7C)
5.5.2 QUERY PROTOCOL specifications

The communication is based upon the sending of single control characters and records
The records used are:
Record QQ: Question record (from Alfred to LIS)
Record QA: Answer record (from LIS to Alfred)
The two records are composed as follows:
<STX> STX character
<Body of record> Record specific
<CheckSum> Check-sum character, calculated as exclusive OR (XOR) of the characters of the
<Body of record>
Note: if check-sum is equal to ETX, then check-sum must be substituted with ASCII
character 0x7F.
<ETX> ETX character
The <Body of record> is composed by fields; each field is terminated by FIELD_CHAR character.
If it is necessary to transmit the FIELD_CHAR character inside a field (i.e. not as field terminator), the
FIELD_CHAR must be preceded by ESCAPE_CHAR (the sequence then is |*).
If it is necessary to transmit the ESCAPE_CHAR character inside a field, the ESCAPE_CHAR must be
preceded by another ESCAPE_CHAR (the sequence then is ||).
5.5.3 QQ Record
The body of QQ record is composed by the following fields:
Name Meaning Value May be empty Note
Type Indicates QQ record QQ No Fixed
ID Sample ID Alphanumeric No

Rev.1.3 – 2020.06.15
5.5.4 QA Record
The body of QA record is composed by the following fields:
Name Meaning Value May be empty Note
Type Indicates QA record QA No Fixed
ID Sample ID Alphanumeric No
YesNo Indicates whether the Y : process sample No
sample must be N : don‟t process
processed or not sample
Profile The profile to be used Alphanumeric Only if „YesNo‟ is N The profile name must
for analysis be a valid profile name
of the Alfred instrument.
Surname Patient surname Alphanumeric Yes
Name Patient name Alphanumeric Yes
Note
All the record‟s fields must be transmitted, even if they are empty.
E.g.: the body of a QA record related to sample 12345 (sample which must not be processed) has the form
QA*12345*N****
5.5.5 Query communication protocol

The communication protocol can be subdivided in three phases:
1. Begin of communication
2. Data exchange
3. End of communication
The communication flow is diagrammed as follows:
ALFRED LIS
SOH
START of
COMMUNICATION
ACK
Repeated for
each sample Record QQ
ACK
DATA EXCHANGE
Record QA
ACK
EOT END of
COMMUNICATION
ACK
5.5.6 Start of communication

Alfred sends the SOH character, and waits for the LIS to send back the ACK character.
If LIS doesn‟t answer, the SOH is re-transmitted after about 3 seconds, up to 5 times.
If the process doesn‟t go well, the phase is repeated 4 more time, with a pause of about 10 seconds
between attempts.

Rev.1.3 – 2020.06.15
5.5.7 Data exchange

For each sample, the following procedure is followed:
 Alfred sends QQ record and waits the confirmation ACK character from LIS.
If ACK is not sent back within 3 seconds, or if LIS sends back the NAK character, Alfred sends
again QQ record, up to 5 times.
If the record transmission was not possible, Alfred passes to the next sample.
 LIS sends QA record and waits the confirmation ACK character from Alfred.
If ACK is not sent back within 3 seconds, or if Alfred sends back the NAK character, LIS sends
again QA record, up to 5 times.
If the record transmission was not possible, we pass to next sample.
5.5.8 End of communication

Alfred sends the EOT character, and waits for the LIS to send back the ACK character. If LIS doesn‟t
answer, the EOT is re-transmitted after about 3 seconds, up to 5 times.
5.5.9 Communication example

Query on four samples (ID_0001  ID_0004).
ID_0001 : process with profile “Std Screening”; patient data is Mario Rossi
ID_0002 : process with profile “Std Screening + PAR”, patient data not available
ID_0003 : process with profile “Profilo*1”, patient data not available
ID_0004 : do not process sample
Note: with the notation <0xNN> it is intended the character with hex code NN
Sender Message Notes

Alfred <0x01> SOH (begin of comm.)
LIS <0x06> ACK
Alfred <0x02>QQ*ID_0001*S<0x03> Record QQ
LIS <0x06> ACK
LIS <0x02>QA*ID_0001*Y*Std
Screening*Rossi*Mario*9<0x03> Record QA
Alfred <0x06> ACK
Alfred <0x02>QQ*ID_0002*P<0x03>
LIS <0x06>
LIS <0x02>QA*ID_0002*Y*Std Screening + PAR***^<0x03> Name and Surname fields are
empty.
Alfred <0x06>
Alfred <0x02>QQ*ID_0003*Q<0x03>
LIS <0x06>
LIS <0x02>QA*ID_0003*Y*Profilo|*1***><0x03> Escape sequence for *
character in profile name.
Name and Surname fields are
empty.
Alfred <0x06>
Alfred <0x02>QQ*ID_0004*V<0x03>
LIS <0x06>
LIS <0x02>QA*ID_0004*N****<0x08><0x03> Name and Surname fields are
empty.
Alfred <0x06>
Alfred <0x04> EOT (end of comm.)
LIS <0x06> ACK

Rev.1.3 – 2020.06.15
6 LAN COMMUNICATION ASTM - PROTOCOL (ALFRED60 AND HB&L)
ASTMCOM module only uses the control of frames transmitted and received, to verify accuracy of data
exchanged (cf. LIS01A2E chapter 8 “Data Link Layer for TCP/IP Data Exchange”); the logic of transmission
of incorrect records provided in LIS02A2 par. 4.2.2 “Logical Transmission Error Recovery Requirements” is
not implemented. This connection is performed by the LAN port.
LAN
6.1 RECORDS SUMMARY

The following are the only implemented / managed records by the ASTMCOM component; the other records
(like C-Records) are not supported but their presence does not affect the functionality of the system.
The TX/RX columns explain, for each field, the implementation:

- “*” symbol means that the field is implemented and mandatory
- “o” symbol means that the field is optional
- other symbols or characters shown the EXACT value that must be present (on RX) or will be present (on
TX)
- no symbol indicates that the field is not used (generally unused fields are also shown in grayed out).
The USE column explains the way in which the corresponding field has been implemented. It can also
indicate the exact amount that will be sent or expected to be received. Often is used the Backus-Naur Form
syntax, to describe data received or transmitted; briefly this syntax can be explained by the following
examples:
 <surname>^<name> means that surname and name are presents and separated by symbol “^” (eg
taylor^frank)
 <surname>^[<name>] means that surname and symbol “^” are presents but name is optional and can
be missing (eg. taylor^ is correct, and also taylor^frank)
(For more info: https://en.wikipedia.org/wiki/Backus%E2%80%93Naur_Form)
NOTE ABOUT ENGLISH TRANSLATION: please note that some Italian words are not translated because
keywords on ASTM implementation (eg. „percentuale-resistenza‟ is a keyword sent on Result Record).
6.2 RECORDS MANAGEMENT
In addition to the inherent logic of the ASTM protocol, the following algorithm has been implemented:
 If module receives a Patient record where Patient Identifier (field # 3: Practice Assigned Patient ID) is
missing, all related Order Records will be bypassed and discarded.
 On reception, any Order Record can contains any numbers of Profile-Name on field #5 (Universal Test ID
field), separated by the Repetition Delimiter (usually character “\”; see LIS02A2E par. 5.4.3); on
transmission a different Order Record will always be sent for each Profile-Name.
 it is possible to receive any number of Order Records for each Patient Record; in this case please note
that:
a) If two records have the same Specimen ID, from the second record will be acquired only data
relating to Universal Test ID; all other data will be discarded
b) If two records have different Specimen ID, both will be acquired completely.

Rev.1.3 – 2020.06.15
6.3 RECORDS IMPLEMENTATION
6.3.1 Message Header Record
FIELD NAME TX RX USE

Record Type ID H H Record Type Identifier
Delimiter definition |\^& * Characters used to indicate:
1) Field Delimiter
2) Repetition Delimiter
3) Component Delimiter
4) Escape Delimiter
On RX these characters are defined by the user; on TX

default characters are implemented
Message Control ID Not supported
Access Password Not supported
Sender Name Or ID * On TX:
sireAstmCom
Sender Street Address Not supported
Reserved files Not supported
Sender Telephone num. Not supported
Characteristics of sender Not supported
Receiver ID Not supported
Comment or special Not supported
Instructions
Processing ID P P Transmission Type:
P = Normal
Version No LIS02- o ASTM protocol version
A2
Date and Time msg * o YYYYMMDD
6.3.2 Patient Information Record
# FIELD NAME TX RX USE

1 Record type ID P P Record Type Identifier
2 Sequence number * * Sequence Number
3 Practice Assigned Pat. ID * * <Patient ID>
4 Laboratory Ass. ID Not supported
5 Patient ID #3 Not supported
6 Patient Name O O <surname>^<name>
7 Mother’s Maiden Name Not supported
8 Birthdate O O <birthdate>
9 Sex Not supported
10 Patient Race-Etnic Origin Not supported
11 Patient Address Not supported
12 Reserved fields Not supported
13 Telephone number Not supported
14 Attending Physician ID Not supported
15 Special Field 1 Not supported
16 Special Field 2 Not supported
17 Patient Height Not supported
18 Patient Weight Not supported
19 P’s known or suspected Not supported
diagnosis
20 Active medications Not supported
21 Diet Not supported

Rev.1.3 – 2020.06.15
22 Practice Fields 1 -/* Not supported

23 Practice Fields 2 -/* Not supported
24 Admission and discharge Not supported
dates
25 Admission status Not supported
26 Location * o < Department >
27 Nature of alternative Not supported
diagnostic code...
28 A. Diagnostic Code... Not supported
29 Patient religion Not supported
30 Marital status Not supported
31 Isolation status Not supported
32 Language Not supported
33 Hospital Service Not supported
34 Hospital Institution Not supported
35 Dosage Category Not supported
6.3.3 Test Order Record
# NAME TX RX USE
1 Record type ID O O Record Type Identifier
2 Sequence number * * Sequence Number
3 Specimen ID * * <Sample ID>^[<Test Tube ID>]^[<Plate ID>]
NOTE: on TX <Plate ID> is always missing

4 Instrument Specimen ID Not supported
5 Universal test ID * * On RX
^^^<Profile Name>[\^^^<Profile
Name>]…[\^^^<Profile Name>]
On TX
^^^<Profile
Name>^[screening|par|mdro|antibiogramma]^
<other data>
NOTE: <other data> can be:
screening, par:
<other data> = (empty)
mdro:
<other data> = tipo_mdro
antibiogramma:
<other data> = [<code>^<name>|rif]
6 Priority Not supported
7 Requested/Ordered Date Not supported
and Time
8 Specimen coll. Date/time Not supported
9 Collection end time Not supported
10 Collection Volume Not supported
11 Collector ID Not supported
12 Action Code Not supported
13 Danger code Not supported
14 Relevant Clinical Info * <Sample Note>
15 Date/Time Specimen rec. Not supported

Rev.1.3 – 2020.06.15
16 Specimen descriptor O O <Material>^<Sample Type>

17 Ordering Physician Not supported
18 Physician Tel. Number Not supported
19 User Field No.1 * * <Process Number>
20 User Field No. 2 Not supported
21 Lab Field No. 1 * Optional data (explained elsewhere)
22 Lab Field No. 2 * Optional data (explained elsewhere)
23 Date/Time results Not supported
reported or Last Modified
24 Instrument Charge to Not supported
Information System
25 Instrument Section ID Not supported
26 Report Types F On TX:
F = Final Result
27 Reserved Fields Not supported
28 Location of Specimen C. Not supported
29 Nosocomial Infection Not supported
Flag
30 Specimen Service Not supported
31 Specimen Institution Not supported
6.3.4 Result Record
# NAME TX RX USE
1 Record type ID R R Record Type Identifier
2 Sequence number * Sequence Number
3 Universal Test ID * ^^^<Profile
Name>^[screening|par|mdro|antibiogramma]^
<other data>^<parameter>
NOTE: <other data> can be:
screening, par:
<other data> = (empty)
mdro:
<other data> = tipo_mdro
antibiogramma:
<other data> = [<code>^<name>|rif]
<parametr> can be:

tempo-analisi-minuti
carica-alfanumerica
carica-numerica
torbido
anomalo
invalido
assente
fine-anticipata
percentuale-agitazione
risultato-mdro (for mdro)
risultato-antibiogramma (for antibiogramma)
percentuale-resistenza (for antibiogramma)
risultato (for par)
4 Data or Measurement value * <Result>

Rev.1.3 – 2020.06.15
NOTE
If result is a Boolean, will be one of these:
T = true
F = false
5 Units Not supported
6 Reference range Not supported
7 Result Abnormal Flag Not supported
8 Nature of Abnormality T Not supported
9 Result status F Status:
F = Final Result
10 Date of Charge in Not supported
Instrument Normative Val
11 Operator ID Not supported
12 Date/Time test started Not supported
13 Date/Time test completed Not supported
14 Instrument ID Not supported
6.3.5 Request Information Record
# NAME TX RX USE
1 Record type ID Q Record Type Identifier
2 Sequence number * Sequence Number
3 Starting range ID number * <Sample ID>[\<Sample ID>]...[\<Sample ID>]
NOTE: on this field all requested Sample ID are

presents, separated by Repeater Delimiter
4 Ending range ID number Not supported
5 Universal test ID Not supported
6 Nature of Request Time Not supported
Limit
7 B.R.R. date/time Not supported
8 Ending... date/time Not supported
9 Requesting Physician Not supported
Name
10 R.P. Telephone number Not supported
11 User Field No1 Not supported
12 User Field No2 Not supported
13 Request info code status * On Tx:
- “O”: Test Order and Patient Data request
6.3.6 Message Terminator Record
# NAME TX RX USE
1 Record type ID L L Record Type Identifier
2 Sequence number 1 1 Mandatory
3 Termination Code N N Mandatory

Rev.1.3 – 2020.06.15
7 CONNECTION OF 2 OR MORE INSTRUMENTS TO THE SAME HOST
7.1 SERIAL COMMUNICATION
In the event it is necessary to connect two or more instruments to Host and there is only 1 Host Com port
available (Host side) it is possible to use one or more serial switched interconnected in chain between then
and the instruments.
Connections on serial port RS232C on PC and on Automatic Switches for PC
PC-XT Serial Port RS232C PC-AT Serial Port RS232C

Connector DB25M Connector DB9M
PIN Name Direction PIN Name Direction
2 TXD 1 DCD
3 RXD 2 RXD
4 RTS 3 TXD
5 CTS 4 DTR
6 DSR 5 GND
7 GND 6 DSR
8 DCD 7 RTS
20 DTR 8 CTS
22 RI 9 RI
Connecting cable between ATEN AS-251S AutoSwitch and Alfred60 or HB&L

(is obtained from the previous cable replacing the connector DB25F with a DB25M and connecting the wires
with the following scheme, note that signal direction are referred to PC side because on AutoSwitch it is not
documented…)
Serial Cable DB25M - DB9F with 9 wires Serial Cable DB25M - DB9F with 7 wires
DB25M Signal Signal DB9F DB25M Signal Signal DB9F

PIN Name Direction Name PIN PIN Name Direction Name PIN
2 (RXD) TDX 3 2 (RXD) TXD 3

3 (TXD) RXD 2 3 (TXD) RXD 2
4 (CTS) RTS 7 4 (CTS) RTS 7
5 (RTS) CTS 8 5 (RTS) CTS 8
6 (DTR) DSR 6 6 (DTR) DSR 6
7 (GND) GND 5 7 (GND) GND 5
8 (DCD) DCD 1 8 (DCD) DCD 1
20 (DSR) DTR 4 20 (DSR) DTR 4
22 (RI) RI 9 22 (RI) RI 9
(A & B Connectors on ATEN (A and B Connectors on ATEN

AutoSwitch are DB25F) AutoSwitch are DB25F)
7.2 LAN COMMUNICATION
In the event it is necessary to connect two or more instruments to Host and there is only 1 Host Com port
available (Host side), in this case is necessary to use a standard LAN HUB (with LAN cables) and create a
network line between the Host and the instruments.

Rev.1.3 – 2020.06.15
8 REFERENCES
Manufacturer: ALIFAX S.r.l
Production Site:
Via Merano 30 33045
Nimis (UD) Italy
Tel +39 0432 197900
Fax +39 0432 547378
Commercial and Marketing Site:

Via F. Petrarca 2
Isola dell'Abbà
35020 Polverara (PD)
Tel. +39-049-0992000
E-mail info@alifax.com
Web www.alifax.com

ALI Alimic TM Mic Interfacing-manual-with-Astm 1-3 en

Uploaded by

Document Information

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

ALI Alimic TM Mic Interfacing-manual-with-Astm 1-3 en

Uploaded by

Copyright:

Available Formats

Microbiology Interfacing Manual

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 1

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 2

2 INSTRUMENT PHSYCAL REAR COM PORTS IDENTIFICATION

Serial DB9/DB9 Null Modem Cable that must have:

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 3

3.2 LAN COMMUNICATION

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 4

5 SERIAL COMMUNICATION PROTOCOL (ALFRED60 AND HB&L)

ALFRED stand alone (and ALFRED mounted on Sidecar) from instrument Sn

 Be sure to connect LAN cable to port identified as ETH1

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 5

HB&L (from instrument Sn UQ4378W and UQ4204WL):

 Be sure to connect the HOST cable to port identified as COM3

Following tables resumes the “Windows” configurations visible from Regedit

HB&L: till instrument Sn UQ4377W and UQ4203WL:

PORT DESCRIPTION SETTINGS

HB&L: from instrument Sn UQ4378W and UQ4204WL:

PORT DESCRIPTION SETTINGS

ALFRED: from instrument Sn A60304W:

PORT DESCRIPTION SETTINGS

ALFRED: from instrument Sn A60305W:

PORT DESCRIPTION SETTINGS

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 6

5.1 COMMUNICATION PROTOCOL

5.2 INTEGRATED PROTOCOL

Speed 9600 baud

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 7

5.3 FIELD #4 SPECIFICATIONS

5.3.1 Completion mode

5.3.2 No vial matching

Field Field Info Description Notes

5.3.3 Vial matching

Field Field Info Description Notes

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 8

QR code contains all the information about the

And it is developed in the below described sequence

SEPARATION POINT SEPARATION POINT

EMPTY FIELDS LOT NUMBER

5.4 FIELD #6 SPECIFICATIONS

URINE AND OTHER HUMAN BIOLOGICAL LIQUIDS:

HUMAN BIOLOGICAL LIQUIDS:

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 9

ADDITIONAL FIELD #6 FORMAT

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 10

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 11

975 Teicoplanin S. aureus and Enterococci / EU

FOR OTHER TEST

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 12

5.5 SPECIFICATION OF QUERY PROTOCOL (ONLY FOR ALFRED60)

5.5.1 Definition of Special Characters

5.5.2 QUERY PROTOCOL specifications

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 13

5.5.5 Query communication protocol

The communication flow is diagrammed as follows:

5.5.6 Start of communication

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 14

5.5.7 Data exchange

5.5.8 End of communication

5.5.9 Communication example

Sender Message Notes

MICROBIOLOGY INTERFACING MANUAL MIC_TM_ALFRED60 – HB&L -1-3_EN Pag 15

6 LAN COMMUNICATION ASTM - PROTOCOL (ALFRED60 AND HB&L)