80000456-102 Alinity ASTM LIS Interface

Alinity ci‑series LIS Interface
Manual (ASTM)
80000456-102
Table of contents
Read me first.......................................................................................... 5
Customer service....................................................................................................................... 6
Proprietary statement.................................................................................................................7
Disclaimers................................................................................................................................. 8
Alinity ci‑series warranty statement for USA customers only..................................................9
Alinity ci‑series agency approvals........................................................................................... 10
Intellectual Property statement................................................................................................11
Key to symbols......................................................................................................................... 12
Comparison between available LIS interfaces: CLSI (ASTM) vs. HL7................................. 15
References............................................................................................................................... 18
CLSI (ASTM) implementation notes..........................................................19
Low-level protocol (CLSI LIS01-A2)........................................................................................20
TCP/IP support only......................................................................................................20
Network connection...................................................................................................... 20
Receiver interrupts........................................................................................................21
Frames...........................................................................................................................21
Character set................................................................................................................ 21
Messaging protocol (CLSI LIS2-A2)........................................................................................22
Logical information storage and transmission error recovery requirements.............22
Outgoing messages...................................................................................................... 22
Incoming messages...................................................................................................... 24
Delimiters.......................................................................................................................25
Record construction......................................................................................................26
Dates and times............................................................................................................ 26
Message buffering........................................................................................................ 26
Outgoing messages............................................................................... 27
Order query.............................................................................................................................. 28
Message structure........................................................................................................ 29
Notes on message structure........................................................................................ 29
Message granularity..................................................................................................... 29
Specimen and QC results upload........................................................................................... 30
Message structure: Specimen results......................................................................... 30
Message structure: QC results.................................................................................... 31
Outgoing record format........................................................................................................... 33
Message Header record (H)........................................................................................ 33
Patient Information record (P)..................................................................................... 34
Test Order record (O).................................................................................................. 35
Result record (R).......................................................................................................... 36
Comment record (C).....................................................................................................39
Request Information record (Q)...................................................................................39
Alinity ci‑series LIS Interface Manual (ASTM) 3

80000456-102 - 2018-05-21
Table of contents
Message Terminator record (L)...................................................................................39

Manufacturer Information record (M)..........................................................................40
Incoming messages............................................................................... 43
Order download........................................................................................................................44
Order processing rules................................................................................................. 46
Negative query response......................................................................................................... 47
Incoming record format............................................................................................................49
Message Header record (H)........................................................................................ 49
Patient Information record (P)..................................................................................... 49
Test Order record (O).................................................................................................. 50
Comment record (C).....................................................................................................52
Request Information record (Q)...................................................................................52
Message Terminator record (L)...................................................................................53
Example messages................................................................................ 55
Outgoing messages................................................................................................................. 56
Incoming messages................................................................................................................. 58
Alinity ci‑series to ARCHITECT comparison...............................................61
Functional comparison.............................................................................................................62
Message record comparison...................................................................................................64
System-specific outgoing messages........................................................................... 64
System-specific incoming messages...........................................................................69
4 Alinity ci‑series LIS Interface Manual (ASTM)

80000456-102 - 2018-05-21
Read me first
Foreword
The Alinity ci‑series LIS (Laboratory Information System) Interface Manual (ASTM) is a
messaging specification intended to specify the electronic communication between the
Alinity ci‑series (instrument) and a Laboratory Information System based on CLSI LIS01-A2
(ASTM 1381) and CLSI LIS2-A2 (ASTM 1394). (CLSI: Clinical and Laboratory Standards
Institute) (ASTM: American Society for Testing and Materials)
This manual assumes that the reader is familiar with the basics of the CLSI LIS01-A2 and LIS2-
A2 standards.
The remainder of this manual specifies the dynamic and static aspects of the Alinity ci‑series
CLSI (ASTM) LIS interface in detail. The dynamic aspects of information interchange include
discussions of the systems that participate in interchanges and the real-world events that trigger
messaging. The static aspects of messaging include the structure and contents of the electronic
messages that are exchanged.
Although this manual describes the elements of CLSI (ASTM) messages and messaging
interactions as they relate to this specification, it does not constitute an introduction to CLSI
LIS01-A2 and LIS2-A2 standards.
Related information...
Customer service, page 6
Proprietary statement, page 7
Disclaimers, page 8
Alinity ci‑series warranty statement for USA customers only, page 9
Alinity ci‑series agency approvals, page 10
Intellectual Property statement, page 11
Key to symbols, page 12
Comparison between available LIS interfaces: CLSI (ASTM) vs. HL7, page 15
References, page 18

80000456-102 - 2018-05-21
Customer service Read me first
Customer service
For questions about the Alinity ci‑series, contact the local representative or find country-specific
contact information at abbottdiagnostics.com.
Read me first, page 5

80000456-102 - 2018-05-21
Read me first Proprietary statement
Proprietary statement
The Alinity ci‑series software programs and system documentation are protected by copyright
(©2016, 2018 Abbott Laboratories, Abbott Park, Illinois). All rights are reserved.
The software and manual were developed solely for use with the Alinity ci‑series as specified in
the operating instructions.
The information, documents, and related graphics published herein (the "Information") are the
sole property of Abbott Laboratories. Permission to use the Information is granted, provided that:
• the copyright notice appears on all copies;
• use of the Information is for operation of ABBOTT products by Abbott trained personnel or
informational use only;
• the Information is not modified in any way; and
• no graphics are used separate from accompanying text.
Each person assumes full responsibility and all risks arising from use of the Information herein.
The Information is presented "AS IS" without warranties, either express or implied, and may
include technical inaccuracies or typographical errors. Abbott Laboratories reserves the right to
make additions, deletions, or modifications to the Information at any time without any prior
notification.

80000456-102 - 2018-05-21
Disclaimers Read me first
Disclaimers
All samples (printouts, graphics, displays or screens, etc.) are for information and illustration
purposes only and shall not be used for clinical or maintenance evaluations. Data shown in
sample printouts and screens do not reflect actual patient names or test results.
The Information was developed to be used by Abbott Laboratories-trained personnel, by other
persons knowledgeable or experienced with the operation and service of the product identified,
under the supervision and with cooperation from Abbott Laboratories technical support or service
representatives.
In no event shall Abbott Laboratories or its affiliates be liable for any damages or losses incurred
in connection with or arising from the use of the information by persons not fully trained by
Abbott Laboratories.
No confidential relationship shall be established in the event that any user of the Information
should make any oral, written or electronic response to Abbott Laboratories (such as feedback,
questions, comments, suggestions, ideas, etc.). Such response and any information submitted
therewith shall be considered non-confidential, and Abbott shall be free to reproduce, publish or
otherwise use such information for any purposes whatsoever including, without limitation, the
research, development, manufacture, service, use, or sale of products incorporating such
information. The sender of any information to Abbott is fully responsible for its content, including
its truthfulness and accuracy and its non-infringement of any other person's proprietary rights.
Abbott Laboratories is not engaged in rendering medical advice or services.
Updates to the Information may be provided in either paper or electronic format. Always refer to
the latest documents for the most current information.
Master Table of Contents and / or Index - Incremental manual updates may cause the Master
Table of Contents or Master Index page numbering to change.
No part of this media may be reproduced, stored, retrieved, or transmitted in any form or by any
means without the prior written permission of Abbott Laboratories.

80000456-102 - 2018-05-21
Read me first Alinity ci‑series warranty statement for USA
customers only
Alinity ci‑series warranty statement for USA

customers only
Abbott Laboratories warrants new instruments sold by Abbott Diagnostics Division to be free from
defects in workmanship and materials during normal use by the original purchaser. This warranty
shall continue for a period of one year from the date of shipment to the original purchaser, or
until title is transferred from the original purchaser, whichever occurs first (the "Warranty
Period").
If any defects occur during the Warranty period, contact your Abbott Customer Service
Representative immediately, and be prepared to furnish information including the serial number,
the model number, and pertinent details concerning the defect.
This Warranty does not cover defects or malfunctions which: (1) are not reported to Abbott
during the Warranty Period and within one week of occurrence; (2) result from chemical
decomposition or corrosion; (3) are caused primarily by misuse, alteration, damage or failure to
comply with any requirements or instruction contained in the applicable Abbott Operations
Manual (including the substitution of any reagent not authorized by Abbott); or (4) result from
maintenance, repair, or modification, performed or attempted by personnel not authorized by
Abbott without Abbott's authorization.
Abbott's liability for all matters arising from the supply, installation, use, repair, and maintenance
of the instrument, whether arising under this Warranty or otherwise, shall be limited solely to the
repair or (at Abbott's sole discretion) replacement of the instrument or of components thereof.
Replaced parts shall become the property of Abbott Laboratories. In no event shall Abbott be
liable for injuries sustained by third parties.
The ICT module Warranty is 20,000 samples or three months post-installation, whichever occurs
first.
The cuvette warranty is one year post-installation.
EXCEPT AS EXPRESSLY PROVIDED ABOVE, ABBOTT LABORATORIES HEREBY DISCLAIMS
ALL REPRESENTATIONS AND WARRANTIES, WHETHER EXPRESS OR IMPLIED, CREATED BY
LAW, CONTRACT OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON-INFRINGEMENT.
IN NO EVENT SHALL ABBOTT LABORATORIES BE LIABLE FOR ANY INDIRECT, SPECIAL,
PUNITIVE, CONSEQUENTIAL OR INCIDENTAL DAMAGES (INCLUDING WITHOUT LIMITATION
LOST REVENUES, PROFITS, OR DATA) ARISING FROM OR IN CONNECTION WITH THE USE
OF THE INSTRUMENT, REGARDLESS OF WHETHER ABBOTT LABORATORIES HAS BEEN
ADVISED AS TO THE POSSIBILITY OF SUCH DAMAGES.

80000456-102 - 2018-05-21
Alinity ci‑series agency approvals Read me first
Alinity ci‑series agency approvals

The Alinity c processing module and the Alinity i processing module have been tested and found
to comply with the following agency standards and European Union (EU) directives:
• UL 61010-1 Safety Requirements for Electrical Equipment for Measurement, Control, and
Laboratory Use - Part 1: General Requirements
• IEC/EN 61010-1 Safety Requirements for Electrical Equipment for Measurement, Control,
and Laboratory Use - Part 1: General Requirements
• CAN/CSA-C22.2 No. 61010-1 Safety Requirements for Electrical Equipment for
Measurement, Control, and Laboratory Use - Part 1: General Requirements
• IEC/EN 61010-2-101 Safety requirements for electrical equipment for measurement, control
and laboratory use - Part 2-101: Particular requirements for in vitro diagnostic (IVD) medical
equipment
and laboratory use - Part 2-081: Particular requirements for automatic and semi-automatic
laboratory equipment for analysis and other purposes
and laboratory use - Part 2-010: Particular requirements for laboratory equipment for the
heating of materials
• Directive 2012/19/EU: Waste Electrical and Electronic Equipment (WEEE)
• Directive 2011/65/EU: Restriction of the Use of Certain Hazardous Substances in Electrical
and Electronic Equipment (RoHS 2)
• Directive 98/79/EC: In Vitro Diagnostic Medical Devices (IVD)
• IEC/BS EN 61326-1 Electrical equipment for measurement, control and laboratory use -
EMC requirements - Part 1: General requirements
• IEC/BS EN 61326-2-6 Electrical equipment for measurement, control and laboratory use -
EMC requirements - Part 2-6: Particular requirements - In vitro diagnostic (IVD) medical
equipment
Legal Manufacturer Abbott GmbH & Co. KG

Max-Planck-Ring 2
65205 Wiesbaden
Germany
+49-6122-580

80000456-102 - 2018-05-21
Read me first Intellectual Property statement
Intellectual Property statement

The green and blue striping, ALINITY, and related brand marks are trademarks of Abbott
Laboratories in various jurisdictions.
Other trademarks are the property of their respective owners. No use of any Abbott trademark,
trade name, or trade dress may be made without the prior written authorization of Abbott
Laboratories, except to identify the product or services of Abbott Laboratories.
For U.S. patent information, see abbott.us/patents.

80000456-102 - 2018-05-21
Key to symbols Read me first
Key to symbols
The following symbols are used on Alinity ci‑series labels and labeling.
Symbol Description
Authorized Representative in the European
Community
Caution: Biological RISKS
Caution: Consult accompanying documents
Caution: Hot surface
Caution: Possibility of electric shock
Caution: Probe stick hazard
Consult operating instructions
Date of manufacture
Disconnect Mains Plug
Interior light
Manufacturer
Temperature limitation
UL Recognized Component Mark

80000456-102 - 2018-05-21
Read me first Key to symbols
Symbol Description
Use by/Expiration date
WEEE: Waste Electrical and Electronic Equipment

NOTE: Indicates that the item needs to be disposed
of in a separate waste collection for electrical and
electronic equipment and must not be disposed of
in the general waste or trash.
Acid Wash
Alkaline Wash
Concentrated Wash Buffer
Detergent A
Detergent B
Distributed by
Distributed in the USA by
For use with
ICT Reference Solution
In Vitro Diagnostic Medical Device
Kit
Batch code/Lot number
Manufactured by
Manufactured for
Pre-Trigger Solution
Produced by
Produced for Abbott by
Product of Japan

80000456-102 - 2018-05-21
Key to symbols Read me first
Symbol Description
Product of Singapore
Product of USA
Quantity
Reaction vessels
Catalog number/List number
Revision
Sample cups
Sequence number
Serial number
Trigger Solution
Unit
Wash buffer
Water Bath Additive

80000456-102 - 2018-05-21
Read me first Comparison between available LIS interfaces: CLSI
(ASTM) vs. HL7
Comparison between available LIS interfaces:

CLSI (ASTM) vs. HL7
The Alinity ci‑series supports two types of LIS interfaces: CLSI (ASTM) and Health Level 7 (HL7).
The instrument can be configured to use one or the other. This section compares and contrasts
the interfaces to provide information to help select which interface type to use.
The HL7 interface is the recommended interface based on additional messaging capabilities,
more robust messaging, and conformance with the most current In Vitro Diagnostic (IVD) industry
standards [developed in partnership with Integrating the Healthcare Enterprise (IHE) Laboratory].
The CLSI (ASTM) interface is provided for legacy reasons to support LIS or host systems that do
not have support for HL7-based interfaces. (CLSI: Clinical and Laboratory Standards Institute)
(ASTM: American Society for Testing and Materials)
Capability HL7 CLSI Comment
(ASTM)
Connections
TCP/IP X X Both types support connections over TCP/IP only
Dual TCP/IP Connection X Separate TCP/IP connections: One for incoming
messages and one for outgoing messages
Single TCP/IP Connection X Single TCP/IP connection used for both incoming
and outgoing messages
Baseline Standards
CLSI LIS01, LIS2 X Communication based on CLSI standards
HL7 Messaging Standard X Communication based on HL7 v2.5.1 and the IHE
Version 2.5.1, IHE LAW LAW messaging profiles
Supported Messages
Order Download X X
Order Query X X
Results Upload X X HL7 supports specimen, control, and calibrator
results
CLSI supports specimen and control results only
Test Status Update X Test status update message triggered upon:
• Test started
• Test exception
• Test pending transmission until other tests for
the sample are completed (Collation)
Sample Status Update X Sample status update message triggered upon:
• Sample scan by instrument
• Sample processing started
• Sample processing completed
• Sample removal from instrument

80000456-102 - 2018-05-21
Comparison between available LIS interfaces: CLSI Read me first
(ASTM) vs. HL7

(ASTM)
Assay Availability X Assay availability message triggered upon time
interval.
Messaging Layer
Application Level X HL7 requires application level acknowledgment of
Acknowledgment received messages (for example, the message is
valid and has been accepted by the receiving
application). CLSI supports only transmission level
acknowledgment (for example, a message
transmission was received). There is no
acknowledgment that the message is valid or has
been accepted by the received application.
Message ID X Unique message ID for each sent message and
included in the message acknowledgment.
Application Layer
Test Management by AWOS X All tests are referenced by AWOS ID. AWOS ID
ID (generated by the LIS) uniquely identifies each test
requested on a specific specimen. (AWOS = IHE
LAW term: Analytical Work Order Step)
For orders: Unambiguous support for order cancel,
order add-ons, order replicates, and detection of
duplicate orders.
For results: Identification of results for specific
orders, reruns, reflex tests, and unsolicited results.
Test Management by X All tests are referenced by Specimen ID and Assay
Specimen ID and Assay ID ID only.
For orders: Using order action code, can support
order cancel, order add-ons, order replicates, and
detection of duplicate orders.
For results: No association of results to specific
orders, no identification of reruns and reflex tests,
cannot distinguish unsolicited results from results
for requested orders.
Asynchronous Queries X In HL7 LAW, multiple queries can be sent by the
instrument before the LIS sends the orders for the
queries. In ASTM, the instrument must wait for the
query response before sending the next query (only
one query at a time can be in process).
Order Acceptance X In HL7 LAW, each individual test order or test
cancel is accepted or rejected by the instrument in
an application acknowledgment message. Not
supported by CLSI.

80000456-102 - 2018-05-21
Read me first Comparison between available LIS interfaces: CLSI
(ASTM) vs. HL7

(ASTM)
Order Status with Results X In HL7 LAW, when the instrument sends a test
result, the message indicates if the instrument
considers the order request as completed or if
reruns are still pending. Not supported by CLSI.
Run Identification with Results X In HL7 LAW, test result messages indicate a unique
run number to distinguish reruns from initial runs of
a test order request. Not supported by CLSI.
Identification of Instrument- X In HL7 LAW, test result messages identify if the
Initiated Reflex Tests result is from a reflex test initiated by the instrument
and identify the test orders that caused the reflex
test. Not supported by CLSI.

80000456-102 - 2018-05-21
References Read me first
References
This manual is based on the following standards:
• CLSI LIS01-A2: Specification for Low-Level Protocol to Transfer Messages Between Clinical
Laboratory Instruments and Computer Systems
• CLSI LIS2-A2: Specification for Transferring Information Between Clinical Laboratory
Instruments and Information Systems
• IHE Laboratory Technical Framework, Laboratory Analytical Workflow (LAW) profile

80000456-102 - 2018-05-21
Section 1 CLSI (ASTM) implementation notes
Introduction
This section specifies implementation notes related to the CLSI (ASTM) interface supported by
the instrument.
Low-level protocol (CLSI LIS01-A2), page 20
Messaging protocol (CLSI LIS2-A2), page 22

80000456-102 - 2018-05-21
CLSI (ASTM) implementation notes
Low-level protocol (CLSI LIS01-A2) Section 1
Low-level protocol (CLSI LIS01-A2)

The instrument uses the low-level protocol as defined in CLSI LIS01-A2.
This manual does not fully specify the CLSI LIS01-A2 protocol but provides only some important
characteristics of the instrument's implementation.
CLSI (ASTM) implementation notes, page 19
TCP/IP support only, page 20
Network connection, page 20
Receiver interrupts, page 21
Frames, page 21
Character set, page 21
TCP/IP support only

The CLSI LIS01-A2 specification addresses the low-level protocol (physical layer and data link
layer) used for both serial binary data exchange and TCP/IP data exchange. However, the
instrument supports TCP/IP data exchange only.
Network connection
Per CLSI LIS01-A2, section 8.2.1.1, the instrument is defined to be the "client" and supports an
active connection while the LIS/host system is defined as the "server" and offers a socket for
connection. The instrument is configurable for both the port and IP address of the LIS and is
defined to be the "client" to request a connection to the LIS offered socket. The instrument
supports an active persistent connection as described below.
Active persistent connection
The following steps are performed by the instrument for an active persistent network connection.
1. At startup, attempt to connect to the configured IP address and port of the LIS.
2. If connection is unsuccessful, wait for a short time period and retry one or more times.
3. Keep the connection open at all times, even if no more messages remain to be exchanged.
4. If a disconnection is detected outside of a data exchange, retry the connection.

80000456-102 - 2018-05-21
Section 1 Low-level protocol (CLSI LIS01-A2)
Receiver interrupts
The instrument does not support receiver interrupts specified in section 8.3.5 of the CLSI LIS01-
A2 specification. During the Transfer Phase the instrument does the following:
• When acting as a receiver during the Transfer Phase, the instrument does not issue a
receiver interrupt request (that is, send an <EOT> in place of the usual <ACK>).
• When acting as a sender during the Transfer Phase, the instrument ignores receiver
interrupt requests and processes the <EOT> character the same as a received <ACK>
character.
Frames
Per the CLSI LIS01-A2 section 8.3.1.1 and section 3.3.2, each LIS01-A2 frame transmitted by the
instrument contains only a single LIS2-A2 record, and each frame received by the instrument
must contain only a single LIS2-A2 record.
Character set
Per section 4.3 of CLSI LIS2-A2, the standard does not define transmission of character
encodings that require greater than 8 bits; however, character encodings greater than 8 bits can
be transmitted through the use of appropriate algorithmic transformations.
The instrument transmits and receives characters using one of the following encodings
(instrument configuration setting):
• Windows-1252
• UTF-8
• Shift-JIS
• ASCII

80000456-102 - 2018-05-21
Messaging protocol (CLSI LIS2-A2) Section 1
Messaging protocol (CLSI LIS2-A2)

The instrument supports the messaging protocol defined in CLSI LIS2-A2. This manual does not
attempt to fully specify the CLSI LIS2-A2 protocol, but only provides some important key
characteristics of the instrument implementation.
CLSI (ASTM) implementation notes, page 19
Logical information storage and transmission error recovery requirements, page 22
Outgoing messages, page 22
Incoming messages, page 24
Delimiters, page 25
Record construction, page 26
Dates and times, page 26
Message buffering, page 26
Logical information storage and transmission error recovery

requirements
Per CLSI LIS2-A2 section 4.2, data is presumed to be saved by the receiver whenever a
decremental change in the hierarchical level is observed. According to the hierarchical record
level requirements, all logical records necessary to reach the point where the transmission
failure occurred must be retransmitted.
Outgoing messages
For outgoing messages, the instrument supports these requirements as follows:
• For Order Query messages, each message contains data for only a single specimen. The
only decremental change in the hierarchical level is achieved only when the Terminator
record is successfully sent. Therefore, if a transmission failure occurs within a message, all
records in the message must be retransmitted.
• For Test Results Upload, the message contains only a single specimen but can contain
multiple results for that single specimen. The instrument presumes data to be saved
according to the following criteria:
At successful receipt of a test order record or terminator record, any unsaved test order
record and associated result and comment records prior to this order record are saved.

80000456-102 - 2018-05-21
Section 1 Messaging protocol (CLSI LIS2-A2)
NOTE: A new Order record marks the end of the complete set of records needed for result
information for a single run of a test request (also indicates the beginning of the result
information for the next test run).
An example result message, showing presumed save points, is provided below. In addition, a list
of which records are resent, in the case of transmission failure, is provided.
Example: Initial segments of a Message Structure
Line # Record Type Level Increment Action of Instrument

A Header Level 0 0
B Patient Level 1 +1
C Order Level 2 +1
D Result Level 3 +1
E Comment Level 4 +1
F Manufacturer Level 4 0
G Result Level 3 -1
H Result Level 3 0
I Order Level 2 -1 at this point, saves A through H (test result)
J Result Level 3 +1
K Order Level 2 -1 at this point, saves I through J (test exception)
L Result Level 3 +1
M Comment Level 4 +1
N Manufacturer Level 4 0
O Result Level 3 -1
P Result Level 3 -0
Q Terminator Level 0 -3 at this point, saves K through P
Records requiring retransmission
Line # where failure occurred Instrument would require retransmission of:

A A
B AB
C ABC
D ABCD
E ABCDE
F ABCDEF
G ABCDEFG
H ABCDEFGH
I ABCDEFGHI

80000456-102 - 2018-05-21

J ABIJ
K ABIJK
L ABKL
M ABKLM
N ABKLMN
O ABKLMNO
P ABKLMNOP
Q ABKLMNOPQ
Incoming messages
For incoming messages, the instrument supports these requirements as follows:
• For Negative Order Query messages, each message contains data for only a single
specimen. The only decremental change in the hierarchical level is achieved only when the
Terminator record is successfully sent. Therefore, if a transmission failure occurs within a
message (Message Header record through Message Terminator record), all records in the
message must be retransmitted.
• For Test Order downloads, the instrument stores segments of the message as received,
according to the following criteria:
– At successful receipt of a record that is a decremental change in the hierarchical level,
all unsaved data is saved prior to this record (per CLSI LIS2-A2).
– At successful receipt of a test order record, any unsaved test order record and
associated comment record prior to this order record are saved.
An example result order message, showing save points, is provided below. In addition, a list of
which records would need to be resent in the case of transmission failure is provided.
Example: Test Order Message with Save Points

A Header Level 0 0
B Patient Level 1 +1
C Order Level 2 +1
D Order Level 2 0 at this point, saves A through C
E Comment Level 3 +1
F Order Level 2 -1 at this point, saves D through E

80000456-102 - 2018-05-21
Section 1 Messaging protocol (CLSI LIS2-A2)

G Comment Level 3 +1
H Patient Level 1 -2 at this point, saves F through G
I Order Level 2 +1
J Order Level 2 0 at this point, saves H through I
K Comment Level 3 +1
L Terminator Level 0 -3 at this point, saves J through K
Records requiring retransmission

A A
B AB
C ABC
D ABCD
E ABDE
F ABDEF
G ABFG
H ABFGH
I AHI
J AHIJ
K AHJK
L AHJKL
Delimiters
For outgoing messages, the delimiters used are:
Delimiter Type Character Description
Field | Separates fields within records.
Repeat \ Separates multiple occurrences for the same type of
information within a field.
Component ^ Separates data elements within a field.
Escape & Allows embedding of special characters within the data.
For incoming messages, any characters defined in the header record and transmitted by the
external system are used as the delimiters for that message.

80000456-102 - 2018-05-21
Record construction
When generating outgoing messages, the instrument only transmits each record, up to and
including the last populated field of the record and then the trailing carriage return. All empty
fields subsequent to the last populated field of the record are suppressed from transmission to
the LIS. For example, when transmitting a Patient record, the instrument does not populate any
fields beyond the Sequence Number, so the record is transmitted as P|1.
Dates and times

All date and time fields are transmitted by the instrument in the local time as set in the
instrument application. Indication of the time zone is provided only in the Message Header
Record (H), Date and Time of Message field. All other time stamps in the message do not have
the time zone specified and can be assumed to be in the same time zone indicated in the
Message Header Record, Date and Time of Message field.
Message buffering
Because of sample-processing requirements, Order Query messages take priority over any other
outgoing messages. However, it will not interrupt a message that is in progress (for example,
waiting for an acknowledgment to a results upload message).
For outgoing messages (for example, Result Upload), the instrument supports the queuing of
multiple messages. As an example, the operator can request that results for N samples be sent
to the LIS. This results in N result messages being queued for transmission. For situations like
this that allow for multiple message transactions to be queued for processing in the background,
the instrument supports a message buffer to hold outgoing messages. This message buffering
also accounts for times when the network connection cannot be made to the LIS. This message
buffer operates as a FIFO queue that allows new Order Query messages to go to the front of
the queue. If the FIFO reaches its maximum capacity, no more messages, including query
messages, are queued for transmission. A buffer-full indication is generated on the instrument
user interface, and the instrument disables the connection.

80000456-102 - 2018-05-21
Section 2 Outgoing messages
Introduction
Transmission of Specimen test results, Quality control results, and Order Query Requests use
the high-level CLSI records and fields described in this section. Unused fields are not listed.
Order query, page 28
Specimen and QC results upload, page 30
Outgoing record format, page 33

80000456-102 - 2018-05-21
Outgoing messages
Order query Section 2
Order query
When the instrument identifies a specimen (bar code read) and finds no existing orders for that
specimen in its database, the instrument queries the LIS for orders against the specimen. The
LIS responds with any test orders for that specimen.
Figure 1: Interaction diagram
Interaction model
Trigger event The query is sent by the instrument when all the following conditions are met:
• A specimen is recognized (bar code read) as being introduced to the
instrument [will not query based on Sample location, but only based on
Specimen Identification (ID)].
• There are no existing test orders found in its database for that specimen.
• The sample is not configured as a Control or Calibrator sample on the
instrument.
• A batch is not In Progress on the system.
• Query mode is enabled for the instrument.
Only one Order Query is issued by the instrument to the LIS at any given time. An
existing Order Query must complete prior to initiating a new request. Order Query
requests are only made for a single sample.
An Order Query request is considered complete under any of the following
conditions:
• receipt of a negative query response
• receipt of test orders for the specimen
• time-out waiting for a response (and retry attempts exhausted)
• error in transmission of query (and retry attempts exhausted)

80000456-102 - 2018-05-21
Outgoing messages
Section 2 Order query
When an Order Query message is transmitted to the host, no other outgoing

messages are sent until the Order Query Request is completed. This allows the LIS
the opportunity to download Test Orders to the instrument in response to the query.
Direction Instrument to LIS
Message structure, page 29
Notes on message structure, page 29
Message granularity, page 29
Message structure
The record hierarchy for an Order Query is as follows:
Message Header Record

Request Information Record
Message Termination Record
Notes on message structure

1. All records are required and always provided.
2. The query parameter in the Request Information record is the Specimen ID as identified on
the specimen bar code.
Message granularity
Each unique message contains:
• one specimen (therefore only one Request Information record).

80000456-102 - 2018-05-21
Outgoing messages
Specimen and QC results upload Section 2
Specimen and QC results upload

The instrument provides the ability to transmit the outcome (result or exception) of Specimen
and Control test orders to the LIS.
Interaction model
Trigger event The results are sent when the results are completed and released by the
instrument. A completed result can either be a successfully completed test or a test
that was attempted to be run but did not produce a result due to some condition
(test exception).
Direction Instrument to LIS
Message structure: Specimen results, page 30
Message structure: QC results, page 31
Message structure: Specimen results

The record hierarchy for Specimen results is as follows:

80000456-102 - 2018-05-21
Outgoing messages
Section 2 Specimen and QC results upload

Patient Information Record
Test Order Record (Result - Test #1)
Result Record (Final)
Manufacturer Information Record(s)
Comment Record (optional)
Result Record (Interpretation)
Result Record (Preliminary)
Result Record (GUID)
Test Order Record (Exception - Test #2)
Result Record (Exception)
Message structure: QC results

The record hierarchy for QC results is as follows:
Manufacturer Information Record (Control Material Info)
Test Order Record (Exception - Test #2)
Result Record (Exception)

80000456-102 - 2018-05-21
Outgoing messages
Specimen and QC results upload Section 2


1. A Test Order record is included for each test (assay) result being reported in the message.
2. If the test outcome is a result, multiple result records are sent underneath the Test Order
record, each for a different part of the result. The different parts of a result include the final
numeric result value, the interpretation, the raw instrument response value, and the result
Globally Unique Identifier (GUID).
3. If the test outcome is an exception, a Result record containing the exception code and text,
is sent underneath the Test Order record. There will also be a result record for the GUID.
4. The Manufacturer record underneath the Test Order record is sent only for Control results
and contains information about the control material (for example, lot number).
5. The Manufacturer records underneath the Result record contain information on each
contributing item used to produce the result. Contributing items can include assay-specific
reagents and assay calibration information. Calculated results are transmitted without
contributing item information.
6. The Comment record underneath a Result record is sent only when there is a result
comment for the test result.
7. With multiple Result records being sent for a result (each for a different part of the result),
the Comment and Manufacturer records, if any, are included only after the first result
record.
Message granularity
Each unique result message can contain:
1. one specimen.
2. one or more results (or exceptions) for the one specimen.

80000456-102 - 2018-05-21
Outgoing messages
Section 2 Outgoing record format
Outgoing record format

The following topics detail the outgoing CLSI record formats.
Message Header record (H), page 33
Patient Information record (P), page 34
Test Order record (O), page 35
Result record (R), page 36
Comment record (C), page 39
Request Information record (Q), page 39
Message Terminator record (L), page 39
Manufacturer Information record (M), page 40
Message Header record (H)

The Message Header record is always the first record in a transmission.
CLSI Field Name Maximum Field Contents Field Description
Field Characters
6.1 Record 1 H Header record
Type ID
6.2 Delimiter 4 | Field delimiter: vertical bar
Definition \ Repeat delimiter: backslash
^ Component delimiter: caret
& Escape delimiter: ampersand
20 Alinity ci‑series Instrument Name
Sender 10 ^Version Number
6.5 Instrument Software Version Number
Name or ID (string)
11 ^Serial Number Instrument Serial Number
6.12 Processing 1 P Production: Treat message as an active message to be
ID completed according to standard processing.
6.13 Version 7 LIS2-A2 Version level of the CLSI specification
Number
6.14 Date and 19 YYYYMMDDHH Date and Time of Message in CLSI date format.
Time of MMSS+/-HHMM Indication of time zone is provided and represents the
Message configured time zone in the instrument application. All
other time stamps in the message do not have the time
zone specified and can be assumed to be in the same
time zone indicated in this field. The time zone (+/-

80000456-102 - 2018-05-21
Outgoing messages
Outgoing record format Section 2

Field Characters
HHMM) is represented as +/-HHMM offset from
Coordinated Universal Time (UTC) [formerly Greenwich
Mean Time (GMT), where +0000 or -0000 both
represent UTC (without offset)].
Patient Information record (P)

The Patient record contains information about the Patient associated with the test results.
Field Characters
7.1 Record Type 1 P Patient record
7.2 Sequence 5 1 to 65536 Consistent with sequence number rules described
Number in CLSI LIS2-A2
7.4 Laboratory 20 Patient ID (string) Patient ID (PID)
Assigned Patient Optional for Specimen results
ID Empty for Control results
20 Last name (string)
20 First name Last, first, and middle patient names
(string) Optional for Specimen results
7.6 Patient Name
Empty for Control results
12 Middle name
(string)
7.8 Birth Date 8 YYYYMMDDHH Patient date of birth
Optional for Specimen results
7.9 Patient Gender 1 M, F, U Patient Gender (Male, Female, Unknown)
7.14 Doctor 20 String Patient Doctor's name
7.26 Location 20 String The patient general clinic location or nursing unit,
or ward, or bed, or both.

80000456-102 - 2018-05-21
Outgoing messages
Test Order record (O)

The Test Order record contains information about the Specimen and test order requested when
transmitting results.
Field Characters
8.4.1 Record 1 O Test Order record
Type
8.4.2 Sequence 5 1 to 65536 Consistent with sequence number rules described in
Number CLSI LIS2-A2
8.4.3 Specimen 20 Specimen ID Specimen ID downloaded from the host, for host-
ID (string) originated orders, or entered on the system for user-
originated orders.
20 Specimen ID Same field as 8.4.3 above
(string)
5 ^Rack ID (string) Sample Rack Bar Code ID for samples loaded on a
sample rack.
"LAS" (without quotes) for samples introduced from a
Lab Automation track.
LAS: Laboratory Automation System
1 ^Position (numeric) Position in sample rack for sample loaded on a sample
Instrument
rack.
8.4.4 Specimen
LAS sampling position for samples introduced from a
ID
Lab Automation track (always 1).
1 ^Module (numeric) Module section where the sample rack was loaded.
Blank for samples introduced from a Lab Automation
track, or samples in onboard storage area.
2 ^Position (numeric) Reagent and sample manager (RSM) Position within
Module section where the sample rack was loaded.
Blank for samples introduced from a Lab Automation
track, or samples in onboard storage area.
0 Empty Universal Test ID (part 1) - not used
0 Êmpty Universal Test ID (part 2) - not used
Universal
8.4.5 4 Âssay Number Assay number that identifies the test.
Test ID
(numeric)
15 Âssay Name Assay name of the test.
(string)

80000456-102 - 2018-05-21
Outgoing messages

Field Characters
10 ^Dilution (string) Sample Dilution protocol name used for the test.
8.4.6 Priority 1 R or S R = Routine
S = Stat Priority
8.4.8 Collection 14 YYYYMMDDHH Date and time of sample collection
Date and MMSS Optional for Specimen results
Time Empty for Control results
8.4.12 Action Code 1 Q or (Empty) Q = Quality Control Sample
(Empty) = Specimen Sample
8.4.26 Report Type 1 F or X F = Final Result
X = Test could not be performed (Exception)
Result record (R)

The Result record contains the actual test results for Specimen and QC results. Results include
the final result numeric value (Result type "F"), result interpretation (Result type "I"), result GUID
(Result type "G"), and raw instrument response value used to calculate the result value (Result
type "P").
Field Characters
9.1 Record Type 1 R Result record
9.2 Sequence 5 1 to 65536 Consistent with the sequence number rules
Number described in CLSI LIS2-A2
4 Âssay Number Assay number that identifies the test
(numeric)
15 Âssay Name Assay name of the test
9.3 Universal Test ID (string)
10 ^Dilution (string) Sample Dilution protocol name used for the test
1 ^Result Type F = final numeric result value
I = interpretation result
P = raw preliminary result value
G = result GUID
X = exception code and text

80000456-102 - 2018-05-21
Outgoing messages

Field Characters
For result type "F", numeric value - may include "<"
or ">", as well as decimal and thousands
separators.
For result type "I", interpretation string
For result type "P", numeric instrument response
For result type "G", GUID string
9.4 Data Value 260 String
For result type "X", Exception code (four digits) and
an optional subcode (four characters) separated by
a dash (for example, 1234-B001), a component
delimiter, and an exception string of up to 250
characters (for example, 1234-
B001^TestExceptionString).
For result type "F", result units
For result type "I", empty
For result type "P", [relative light unit (RLU), Abs, or
9.5 Unit 8 String
mV]
For result type "G", empty
For result type "X", empty
For result type "F" (for QC results), populated with
control min-max range as configured on the
instrument
For result type "F" (for Specimen results),
Reference populated with normal min-max range as configured
9.6 60 String on the instrument, if defined
Ranges
For result type "P", empty
For result type "F", this field can be blank or
contain one or more of the following flags:
• IUO = Investigational Use Only
• RUO = Research Use Only
• EDIT = result has been edited or recalculated
• EXP = Expired material
• EXPC = Expired calibration or expired
Result Abnormal
9.7 20 String calibrator lot
Flags
• A#1 = only 1 read within Absorbance limit
• A#2 = only 2 reads within Absorbance limit
• CNTL = Result produced after a control had a
Westgard failure rating, or control result
outside range
• < = result below assay dynamic range
• > = result above assay dynamic range

80000456-102 - 2018-05-21
Outgoing messages

Field Characters
• INDX = interfering substances
• FLEX = flexible read time data used
• LL = result below extreme range
• HH = result above extreme range
• PSHH = previous sample extreme high
• LOW = result below normal range
• HIGH = result above normal range
• CORR = Correlation Assay version
• 1-2s = control result fails Westgard rule
• 1-3s = control result fails Westgard rule
• 2-2s1R1M = control result fails Westgard rule
• 2-2s1RxM = control result fails Westgard rule
• 2-2sxR1M = control result fails Westgard rule
• R-4s = control result fails Westgard rule
• 4-1s1M = control result fails Westgard rule
• 4-1sxM = control result fails Westgard rule
• 10-x1M = control result fails Westgard rule
• 10-xxM = control result fails Westgard rule
NOTE: Multiple flags can be sent and are
separated by a repeat delimiter.
For result type "P", empty
9.9 Result Status 1 F or R F = Final Result, initial transmission
R = Previously transmitted final result
9.11 Operator 12 String Username of user logged into the instrument at the
Identification time the result was produced
12 String Username of user logged into the instrument at the
time the result was released
9.13 Date/Time Test 14 YYYYMMDDHH Date and time the test processing completed (in
Completed MMSS CLSI date format)
9.14 Instrument 11 String Serial Number of the module which performed the
Identification test. For calculated test results (and some test
exceptions), contains the System Control Module
serial number.

80000456-102 - 2018-05-21
Outgoing messages
Comment record (C)

A Comment record follows a Result record if a result comment was entered for the test result.
CLSI Field Name Maximum Field Field Description
Field Characters Contents
10.1 Record Type 1 C Comment record
10.2 Sequence 5 1 to 65536 Consistent with sequence number rules described in
Number CLSI LIS2-A2
10.3 Comment Source 1 I I = Instrument
10.4 Comment Text 50 String Result comment
10.5 Comment Type 1 G G = Generic comment for the result
Request Information record (Q)

A Request Information record is used to request the LIS to send any outstanding orders for a
single specified Specimen ID.
11.1 Record Type 1 Q Request Information record
11.2 Sequence 1 1 Sequence number is always 1. Only one Request
Number Information record is sent at any one time.
11.3 ID Number 0 Empty LIS Patient ID - not supported
20 ^Specimen Specimen ID read from the bar code label on the
ID specimen container (for example, tube).
11.5 Universal Test ID 3 ^^ÂLL Instrument always requests that ALL outstanding orders
are sent (as the fourth component of the field).
11.13 Status Code 1 O Instrument only requests Orders.
Message Terminator record (L)

The Message Terminator record is always the last record in a transmission.

80000456-102 - 2018-05-21
Outgoing messages

12.1 Record Type 1 L Terminator (last) record
12.2 Sequence 1 1 Always set as 1
Number
Manufacturer Information record (M)

The Manufacturer Information record is used to send contributing item information for the test
result or exception. It carries:
• substance information for assay-specific reagent material used.
• assay calibration information.
• substance information for QC material used only for QC results.
NOTE: CLSI-LIS2 does not define fields after CLSI field number 14.2. The notation *.N in the
table below indicates the field number in the record defined for use in the interface.
Field Characters
14.1 Record Type 1 M Manufacturer record
14.2 Sequence 5 1 to 65536 Consistent with the sequence number rules
Number described in CLSI LIS2-A2
*.3 Record Type 3 INV Record containing contributing item information.
Sub ID Modeled after fields in the HL7 v2.5.1 INV
segment.
*.4 Substance 20 String The identifier of the contributing item varies based
Identifier on Substance Type (see the table below).
*.5 Substance 2 String The type of contributing item is one of:
Type • SR = Assay-specific Reagent information
• CO = Control specimen information
• CA = Assay Calibration information
*.6 Inventory 20 String The serial number of the reagent.
Container Only present for Substance Type: SR.
Identifier Blank for all other Substance Types.
*.7 Expiration 14 YYYYMMDD[HHMMSS] Calibration Expiration Date and time (may be
Date/Time blank) for Substance Type: CA.
Lot Expiration Date (may be blank) for all other
Substance Types.

80000456-102 - 2018-05-21
Outgoing messages

Field Characters
*.8 Calibration 14 YYYYMMDDHH Date and time the assay was calibrated (in CLSI
Date/Time MMSS date format).
Only present for Substance Type: CA.
Blank for all other Substance Types.
*.9 Lot Number 20 String The lot number of the contributing substance. For
assay calibration information, this is the lot number
of the calibrated reagent.
Present for all Substance Types.
Substance Identifiers for Substance Types
Substance Substance Example Field Description

Type Identifier Field
Contents
SR Reagent ID - 165-1 For assay-specific reagents, the Reagent Configuration
Version ID and version, separated by a dash (-), of the reagent
as defined on the system.
CO Control Name HCV_Positive For assay controls, the name of the control as defined on
the instrument. This is the concatenation of a Control Set
Name and a Control Name.
CA Assay Number 165 For assay calibration, the assay number for the test.

80000456-102 - 2018-05-21
Outgoing messages
NOTES

80000456-102 - 2018-05-21
Section 3 Incoming messages
Introduction
This section outlines the messages, records, and field contents for communications from the LIS
host computer to the Alinity ci‑series. Unsupported fields are not listed.
Order download, page 44
Negative query response, page 47
Incoming record format, page 49

80000456-102 - 2018-05-21
Incoming messages
Order download Section 3
Order download
This message is used to issue a new order to the instrument or to cancel an existing order
previously sent.
Interaction model
Trigger event Any change to an order which then causes the order to be allocated or scheduled
on the instrument by the LIS. Such changes include submission of new orders,
cancellations, updates, etc., where multiple orders are associated with a single
sample.
The message can also be sent from the LIS in response to an order query from the
instrument. The response can contain orders to be performed by the instrument.
The instrument accepts unsolicited test orders from the LIS, regardless of whether
the Host Query option is enabled or not.
This message also covers the case where a previously downloaded order will need
to be canceled or modified on the instrument. To affect an order modification, the
combination of an order cancel and a new order must be used.
Direction LIS to Instrument

80000456-102 - 2018-05-21
Incoming messages
Section 3 Order download

Order processing rules, page 46
Message structure
The record hierarchy for an Order Download is as follows:

Test Order Record
Test Order Record
Test Order Record
Comment Order Record (optional)
Test Order Record
Test Order Record
Test Order Record

1. Multiple tests can be ordered for a specimen using either of the following methods:
a. Use of a Repeat Delimiter in the Universal Test ID field of the Test Order Record.
b. Use of multiple Test Order records beneath a Patient Information Record.
2. An optional Comment record, containing a test order comment, may be included after a Test
Order record. The comment text is limited to 50 characters. If multiple Comment records are
received under the same Test Order record, only the first Comment record is processed.
Message granularity
Each unique message can contain:
1. one or more specimens.
2. one or more test orders against each specimen.

80000456-102 - 2018-05-21
Incoming messages
Order download Section 3
Order processing rules

Each individual test ordered (or canceled) is further processed and validated as described
below:
1. A test on the instrument is fully specified as an "Assay Number" plus an optional sample
dilution.
2. A sample dilution is specified by a dilution protocol name. If a sample dilution is not
specified in the message, it defaults to the default (dilution) protocol configured for the
assay.
3. If the test order request specifies an assay that is not defined (or is not enabled) on the
instrument, the instrument ignores the test order request and notifies the user.
4. If the test order request specifies a dilution protocol name (protocol names are case
sensitive), or that protocol is a hidden calibration dilution protocol, the instrument ignores the
test order request and notifies the user.
5. If the test order request indicates a new order (Test Order Record, Action Code field = N)
but that same test order for the sample ID already exists (Pending, Onboard, Scheduled,
Running), the instrument ignores the test order request and notifies the user. If the test order
does not already exist for the specified sample ID, then the test order is created.
6. If the test order request indicates an add order (Test Order Record, Action Code field = A),
the test order is processed as a mandatory added test order. It is added to the test order
regardless of whether or not the same test order already exists (Pending, Onboard,
Scheduled, Running) for the sample ID.
7. If the test order request indicates a cancel order (Test Order Record, Action Code field =
C), the test order is processed as a cancel request. The instrument cancels the first
Pending test order found from its pending test order list that has the same Specimen ID and
Assay Number. If no test is found or if the test order is already in progress or complete, the
cancel request is ignored.

80000456-102 - 2018-05-21
Incoming messages
Section 3 Negative query response
Negative query response

This message is used in response to an order query to indicate there are no test orders to
perform.
Interaction model
Trigger event The message is sent from the LIS in response to an order query from the
instrument. The response indicates that there are no outstanding orders for the
requested Specimen ID.
Direction LIS to Instrument
Message structure
The record hierarchy for a Negative Query Response is as follows:

80000456-102 - 2018-05-21
Incoming messages
Negative query response Section 3
Request Information Record


The Request Information record is a copy of the original record sent from the instrument with the
Status Code field set to X.
Message granularity
Each unique message can contain a negative query response for one specimen.

80000456-102 - 2018-05-21
Incoming messages
Section 3 Incoming record format
Incoming record format

For all record formats described in this section, any field not specified is ignored if present in an
incoming record.
Message Header record (H), page 49
Test Order record (O), page 50
Comment record (C), page 52
Request Information record (Q), page 52
Message Terminator record (L), page 53
Message Header record (H)

The Message Header record is always the first record in a transmission.
6.1 Record Type 1 H or h Header record
6.2 Delimiter 4 Characters 2 and 6 of the record must be the same and
Definition characters 2, 3, 4, and 5 must be different.
6.12 Processing ID 1 P Production: Treat message as an active message to be
completed according to standard processing.
Notes:
1. Processing ID must be P (or p) in the incoming message or the message "Message Header
Record to Terminator Record" is ignored.

The Patient record contains information about the Patient associated with the test orders.
Field Characters
7.1 Record Type 1 P or p Patient record
7.2 Sequence 5 1 to 65536 Consistent with sequence number rules described

80000456-102 - 2018-05-21
Incoming messages
Incoming record format Section 3

Field Characters
7.4 Laboratory 20 Patient ID (string) Patient ID (PID)
Assigned Patient Optional for Specimen test orders
ID
20 Last name (string)
20 First name Last, first, and middle patient names
7.6 Patient Name (string) Optional for Specimen test orders
12 Middle name
(string)
7.8 Birth Date 8 YYYYMMDDHH Patient date of birth
Optional for Specimen test orders
7.9 Patient Gender 1 M, F, U Patient Gender (Male, Female, Unknown)
7.14 Doctor 20 String Patient Doctor's name
7.26 Location 20 String The patient general clinic location or nursing unit,
or ward, or bed, or both.
Test Order record (O)

The Test Order record contains information about the Specimen and test order requested when
downloading test order requests.
Field Characters
8.4.1 Record Type 1 O or o Test Order record
8.4.2 Sequence 5 1 to 65536 Consistent with sequence number rules described
8.4.3 Specimen ID 20 Specimen ID Specimen ID downloaded from the host. Valid
(string) characters include byte codes 32 through 126
(decimal), excluding 124 (vertical pipe "|"). It is
recommended that the Specimen ID field does not
contain any trailing or leading white space
characters, as they are not easily discernible as
part of the Specimen ID when displayed on the
instrument user interface.
8.4.4 Instrument N/A N/A Field ignored on input
Specimen ID

80000456-102 - 2018-05-21
Incoming messages

Field Characters
4 Âssay Number Assay number that identifies the test.
(numeric)
15 Âssay Name Assay name of the test - optional for all test orders.
8.4.5 Universal Test ID
(string) The instrument ignores the assay name sent with
test orders and creates the order according to the
assay number. This field can be blank.
10 ^Dilution (string) Sample Dilution protocol name (case sensitive) -
optional for all test orders. If left blank, the
instrument creates the test order using the default
dilution.
8.4.6 Priority 1 S S = Stat Priority
NOTE: Blank or any other character = Routine
8.4.8 Collection Date 14 YYYYMMDDHH Date and time of sample collection

and Time MMSS Optional for Specimen test orders
N = New order for a specimen - only create new
order if the specified assay in 8.4.5 does not
already exist for the specimen
A = Add (unconditional) order for a specimen -
8.4.12 Action Code 1 N, A, or C
create order for the specified assay in 8.4.5, even if
an order already exists for that assay
C - Cancel (delete) pending order for the assay
specified in 8.4.5
8.4.26 Report Type 1 O or Q O = Order record; asking that analysis be
performed
Q = response to Query (this record is a response to
an order query request)
Notes:
1. The instrument supports repeat delimiters in the Universal Test ID field on incoming requests
in support of ordering multiple tests for a specimen. (In addition, multiple tests may be
ordered by sending multiple Order records, each with a single Universal Test ID specified.)
2. Replicates for an assay may be ordered using one of these two methods:
a. Use of Repeat Delimiters in Universal Test ID field of Test Order Record
b. Multiple Order records containing Action Code "A"

80000456-102 - 2018-05-21
Incoming messages
Comment record (C)

For incoming test order requests, a Comment record following an Order contains the optional
test order comment for the test requests in the preceding Order record.
10.1 Record Type 1 C or c Comment record
10.2 Sequence 5 1 to 65536 Consistent with sequence number rules described in
Number CLSI LIS2-A2
10.3 Comment Source 1 L L = information system (LIS)
10.4 Comment Text 50 String Order comment text. Instrument truncates any text in
excess of 50 characters.
10.5 Comment Type 1 G G = Generic comment for the test order
Request Information record (Q)

A Request Information record is used to send a negative query response from the LIS. The
negative query response is used to indicate that an earlier Query Request from the instrument
resulted in no orders to send.
11.1 Record Type 1 Q or q Request Information record.
11.2 Sequence 1 1 Sequence number is always 1. Only one
Number Request Information record is sent at any one
time.
11.3 ID Number 0 Empty LIS Patient ID - not supported.
20 ^Specimen ID Specimen ID read from the bar code label on
the specimen container (for example, tube)
originally sent by the instrument with the query
request.
11.5 Universal Test 3 ^^ÂLL Field contents originally sent by the instrument
ID with the query request.
11.13 Status Code 1 X X = Negative query response - Indicates that
either the Specimen ID is unknown to the LIS

80000456-102 - 2018-05-21
Incoming messages

or there are no outstanding orders for the
specified Specimen ID.
Message Terminator record (L)

The Message Terminator record is always the last record in a transmission.
12.1 Record Type 1 L or l Terminator (last) record
12.2 Sequence 1 1 Always set as 1
Number

80000456-102 - 2018-05-21
Incoming messages
NOTES

80000456-102 - 2018-05-21
Appendix A Example messages
Introduction
This appendix contains example messages for outgoing and incoming messages.

80000456-102 - 2018-05-21
Example messages
Outgoing messages Appendix A
Outgoing messages
Order Query
H|\^&|||Alinity ci-series^1.0^s00123|||||||P|LIS2-A2|20151103103758-0600
Q|1|^002111522041500||^ÂLL||||||||O
L|1
Specimen result
P|1
O|1|002231522041700|002231522041700^F5678^3^1^10|^^^25Ânti-HCVÛNDILUTED|
R||||||||||||||||||||F
R|1|^^^25Ânti-HCVÛNDILUTED^F|0.21|S/CO||RUO||F||AdminÂdmin||
20151103104756|i12345
M|1|INV|25|CA|||20151030110131|21544MU52
M|2|INV|25-0|SR|42514|20241231||21544MU52
R|2|^^^25Ânti-HCVÛNDILUTEDÎ|NonReactive|||||F||AdminÂdmin||
20151103104756|i12345
R|3|^^^25Ânti-HCVÛNDILUTED^P|15000|RLU||||F||AdminÂdmin||20151103104756|
i12345
R|4|^^^25Ânti-HCVÛNDILUTED^G|6d9fc45f-1512-4141-8a82-3a90fa63f542|||||F||
AdminÂdmin||20151103104756|i12345
L|1
Specimen exception
P|1
O|1|00256114041500|00256114041500^H8878^1^1^8|^^^25Ânti-HCVÛNDILUTED|
R||||||||||||||||||||X
R|1|^^^25Ânti-HCVÛNDILUTED^X|1401^TestException - Unable to process test.
Background read failure.|||||F||AdminÂdmin||20151103112204|i12345
M|1|INV|25|CA|||20151030110024|21544MU52
M|2|INV|25-0|SR|42514|20241231||21544MU52
C|1|I|Example comment.|G
R|2|^^^25Ânti-HCVÛNDILUTED^G|4fd3f19f-0052-441f-963f-a314c8c123ba|||||F||
AdminÂdmin||20151103112204|i12345
L|1
Control result
P|1

80000456-102 - 2018-05-21
Example messages
Appendix A Outgoing messages
O|1|CMV IgG Neg|CMV IgG Neg^X5459^1^1^3|^^^65^CMV IgGÛNDILUTED|R||||||

Q||||||||||||||F
M|1|INV|CMV IgG Neg|CO||20300730||22549OI33
R|1|^^^65^CMV IgGÛNDILUTED^F|8.00|S/CO|0 - 30.3|RUO||F||AdminÂdmin||
20151103110348|i12345
M|1|INV|65|CA|||20151030105800|58965KF25
M|2|INV|65-0|SR|08547|20230910||58965KF25
R|2|^^^65^CMV IgGÛNDILUTED^P|248|RLU||||F||AdminÂdmin||20151103110348|
i12345
R|3|^^^65^CMV IgGÛNDILUTED^G|f66ee4d3-3867-4233-8005-dc75adf05aa8|||||F||
AdminÂdmin||20151103110348|i12345
L|1
Example messages, page 55

80000456-102 - 2018-05-21
Example messages
Incoming messages Appendix A
Incoming messages
Order Download for Single Specimen
H|\^&||||||||||P
P|1|||PID0001|Doe^John^Q||19610722|M|||||Dr. Smith||||||||||||ParkClinic
O|1|002111522041500||^^^65|||||||A||||||||||||||O
C|1|L|Order comment.|G
L|1
Order Download for Multiple Specimens with Multiple Orders per Specimen
H|\^&||||||||||P
P|1
O|1|009986522317500||^^^65|||||||A||||||||||||||O
O|2|009986522317500||^^^85|||||||A||||||||||||||O
O|3|009986522317500||^^^25|||||||A||||||||||||||O
P|2
O|1|009986522317600||^^^65|||||||A||||||||||||||O
O|2|009986522317600||^^^85|||||||A||||||||||||||O
O|3|009986522317600||^^^25|||||||A||||||||||||||O
P|3
O|1|009986522317700||^^^65|||||||A||||||||||||||O
O|2|009986522317700||^^^85|||||||A||||||||||||||O
O|3|009986522317700||^^^25|||||||A||||||||||||||O
P|4
O|1|009986522317800||^^^65|||||||A||||||||||||||O
O|2|009986522317800||^^^85|||||||A||||||||||||||O
O|3|009986522317800||^^^25|||||||A||||||||||||||O
L|1
Order Cancel for Single Specimen
H|\^&||||||||||P
P|1
O|1|002111522041500||^^^65|||||||C||||||||||||||O
L|1
Negative Query Response
H|\^&||||||||||P
Q|1|^44576114055699||^^ÂLL||||||||X

80000456-102 - 2018-05-21
Example messages
Appendix A Incoming messages
L|1
Example messages, page 55

80000456-102 - 2018-05-21
Example messages
Incoming messages Appendix A
NOTES

80000456-102 - 2018-05-21
Appendix B Alinity ci‑series to ARCHITECT comparison
Introduction
This appendix contains a functional comparison and a message record comparison of the
Alinity ci‑series and the ARCHITECT system.
Functional comparison, page 62
Message record comparison, page 64

80000456-102 - 2018-05-21
Alinity ci‑series to ARCHITECT comparison
Functional comparison Appendix B
Functional comparison
The following is a brief description of the major functional differences between the LIS (ASTM/
CLSI) interfaces of the Alinity ci‑series and ARCHITECT System. This comparison is provided in
support of customers that are replacing an ARCHITECT System with an Alinity ci‑series.
Capability Alinity ci‑series ARCHITECT
Physical Layer
Data Exchange TCP/IP RS-232
Data Link Layer
Maximum Frame 64,000 characters 247 characters
Size
Message Content Layer
Character Encoding • ASCII (English characters only) • ASI - Abbott Standard Interface
Options • Windows-1252 (Abbott only encoding scheme
• Windows-932 (Shift-JIS) dating back to Abbott AxSYM
• UTF-8 instrument system)
• Windows-1252
• Windows-932 (Shift-JIS)
• Windows-936 (Simplified Chinese
GBK)
• UTF-8
Patient Sends all available patient demographic Enable/disable feature for transmission
Demographic Data data of select patient demographic data
Transmission (Collection Date/Time, Patient Location,
Doctor)
Control Orders Does not accept Control orders Accepts Control orders
Error Code and Sends both Code and Text. (If LIS cannot Enable/disable feature for transmission
Text for Test handle non-English characters, use of the Error Text in support of LIS (that
Exceptions ASCII.) cannot accept non-English characters)
Transmission
Sending Test Sent within Result record under Order Sent within Comment record under Order
Exceptions record record
Test Order Single comment up to 50 characters: Concatenation of multiple optional ASTM
Comments Comment record under Order record fields to form a single comment up to 50
characters:
• Comment record under Patient
record
• Danger Code field
• Clinical information field
• Specimen type field
• Specimen source field
• Comment record under Order record
Multiple Result Flags separated by repeat delimiter Flags separated by component delimiter
Flags

80000456-102 - 2018-05-21
Appendix B Functional comparison
Capability Alinity ci‑series ARCHITECT

Multiple PIDs per Single PID field Three different PID fields; complex rules
Patient for mapping
Location of Sample Sent within Test Results/Exceptions Not sent
Rack in RSM
Contributing Substances
Calibration Date/ Sent with Test Results/Exceptions in M Not sent
Time record (identifies what calibration was
used to produce the result)
Reagent Information Sent using M record in Test Results Sent in R record of Test Results (in
component of Universal Test ID field)
Control Lot Number Sent using M record of Control Test Sent in R record of Control Test Results
Results (in component of Universal Test ID field)
Alinity ci‑series to ARCHITECT comparison, page 61

80000456-102 - 2018-05-21
Message record comparison Appendix B
Message record comparison

The following includes a comparison of the fields within message records which contain
differences between the LIS (ASTM/CLSI) interfaces of the Alinity ci‑series and ARCHITECT
System. This comparison is provided in support of customers that are replacing an ARCHITECT
System with an Alinity ci‑series.
Alinity ci‑series to ARCHITECT comparison, page 61
System-specific outgoing messages, page 64
System-specific incoming messages, page 69
System-specific outgoing messages

Differences are provided regarding the format of the records sent by the Alinity ci‑series or the
ARCHITECT System to the host.
Message Header record, page 64
Test Order record, page 65
Results record, page 66
Comment record, page 68
Request Information record (Q), Alinity ci‑series, page 68
Manufacturer Information record (Alinity ci‑series only), page 68
Message Header record

The following table details the differences in format of the Message Header record sent by the
Alinity ci‑series or ARCHITECT System to the host.
CLSI Field Name Maximum Characters Field Contents Field Description
Field
Sender Name Alinity ci‑series 20 Instrument
Instrument Model Name
or ID ARCHITECT 9 Name
Software Alinity ci‑series 10 ^Version

Instrument Software Version Number
Version ARCHITECT 4 Number
6.5
Serial Alinity ci‑series 11
^Serial Number System Control Serial Number
Number ARCHITECT 25
Interface Alinity ci‑series Înterface
Record types the system supports
Version (Not Supported) Version

80000456-102 - 2018-05-21
Appendix B Message record comparison

Field
ARCHITECT 16 NOTE: Not supported or provided in
Alinity ci‑series.
6.13 Version Alinity ci‑series 7 LIS2-A2 Version level of the CLSI specification
Number ARCHITECT 14 1 ARCHITECT LIS Interface Version
Alinity ci‑series 19 YYYYMMDD Date and Time of Message in CLSI
Date and HHMMSS+/- date format.
6.14 Time of HHMM
NOTE: Alinity ci‑series provides the
Message ARCHITECT 14 YYYYMMDDHH
time zone.
MM SS

The following table details the differences in the format of the Patient Information sent by the
CLSI Field Name Maximum Characters Field Field Description
Field Contents
Alinity ci‑series
Practice-Assigned
7.3 (Not Supported) Patient ID Patient ID
Patient ID
ARCHITECT 20
Alinity ci‑series
Patient ID No.
7.5 Patient ID No.3 (Not Supported) Patient ID No. 3
3
ARCHITECT 20
Test Order record

The following table details the differences in the format of the Test Order record sent by the
Field Contents
Instrument 20 Specimen ID Specimen ID
Specimen ID
8.4.4
Alinity ci‑series 5 Sample Rack Bar Code ID for samples
Rack ID ^Rack ID
ARCHITECT 4 loaded on a sample rack

80000456-102 - 2018-05-21

Field Contents
Alinity ci‑series 1 Position in sample rack for sample
Position ^Position
ARCHITECT 2 loaded on a sample rack
Alinity ci‑series 1
Module section where the sample rack
Module ARCHITECT ^Module
was loaded
(Not Supported)
RSM Position within Module section
Position ARCHITECT ^Position
where the sample rack was loaded
(Not Supported)
4 Âssay Assay number that identifies the test
Number
Âssay Name Assay name of the test
Universal ARCHITECT 10
8.4.5
Test ID 10 ^Dilution Sample Dilution protocol name used
for the test.
Alinity ci‑series Assay status: P if assay is installed as
(Not supported) the primary version; C if the assay is
^Status installed as the correlation version
ARCHITECT 1
(P or C)
NOTE: Alinity ci‑series does not
support Assay Status component.
Results record
The following table details the differences in the format of the Results record sent by the
Field Contents
Alinity ci‑series
9.3 Universal Test
ID 4 Âssay Assay number that identifies the test.
Number
Alinity ci‑series 15 Âssay Name Assay name of the test.

80000456-102 - 2018-05-21

Field Contents
ARCHITECT 10
10 ^Dilution Sample Dilution protocol name used
for the test.
Alinity ci‑series Assay status: P if assay is installed as
^Status
(Not supported) the primary version; C if the assay is
(P or C)
ARCHITECT 1 installed as the correlation version
Alinity ci‑series
(Not supported) ^Reagent Lot Reagent Master Lot Number
ARCHITECT 15
Alinity ci‑series
^Reagent Serial number of reagent kit used to
(Not supported)
serial number process the test result
ARCHITECT 5
Alinity ci‑series
^Control lot
(Not supported) Lot number of the control material
number
ARCHITECT 20
1 ^Result Type F = final numeric result value
I = interpretation result
P = raw preliminary result value
NOTE: Additional in Alinity ci‑series:
G = result GUID
X = exception code and text
9.4 Data Value Alinity ci‑series 260 Result Result Value

ARCHITECT 20
9.5 Unit Alinity ci‑series 8 Units Result Units
ARCHITECT 7
9.6 Reference Alinity ci‑series 60 Reference Reference Range
Ranges ARCHITECT Range
At least 35
9.7 Result Alinity ci‑series 20 Result Flags Result Flags
Abnormal Flags ARCHITECT Alinity ci‑series uses repeat delimiter to
At least 35 separate multiple result flags;
ARCHITECT uses component delimiter.
9.11 Operator 12 Order ID of operator logged into system at
Identification Operator ID time of order
NOTE: Different in Alinity ci‑series:
Username of user logged into the

80000456-102 - 2018-05-21

Field Contents
instrument at the time the result was

produced.
12 ^Release Username of user logged into the

Operator ID instrument at the time the result was
released.
9.14 Instrument Alinity ci‑series 11 Instrument ID Serial Number of the module which
Identification ARCHITECT 25 performed the test.
Comment record
The following table details the differences in the format of the Comment record sent by the
Field
Comment Result Comment or Exception
10.4 ARCHITECT Comment
Text String
At least 260
Comment Alinity ci‑series G Result Comment or Exception
10.5 1
Type ARCHITECT G or I String
Request Information record (Q), Alinity ci‑series

Negative Query Response record, ARCHITECT
There are no differences in the Request Information record sent by the Alinity ci‑series to the
host and the Negative Query Response record sent by the ARCHITECT System to the host.
Manufacturer Information record (Alinity ci‑series only)

The Manufacturing Information record is included in Alinity ci‑series; ARCHITECT does not
support this record. Record sent by the Alinity ci‑series to the host.

80000456-102 - 2018-05-21
System-specific incoming messages

Differences are provided regarding the format of the records sent by the Alinity ci‑series or the
ARCHITECT System to the host.
Message Header record, page 69
Test Order record, page 70
Comment record, page 72
Request Information record (Q), Alinity ci‑series, page 72
Message Terminator record, page 72
Message Header record

The following table details the differences in the format of the Message Header record sent by
the host to the Alinity ci‑series or ARCHITECT System.
Field Characters
Alinity ci‑series P Production: Treat message as an
6.12 Processing ID 1 ARCHITECT active message to be completed
P or p according to standard processing.
Alinity ci‑series
6.13 Version Number (Not Supported) 1 Must be 1
ARCHITECT 1

The following table details the differences in the format of the Patient Information record sent by
the host to the Alinity ci‑series or ARCHITECT System.
Field
7.3 Practice-Assigned Alinity ci‑series Practice-Assigned Returned unchanged during
Patient ID (Not Supported) Patient ID transmission to the host
ARCHITECT 20

80000456-102 - 2018-05-21

Field
Optional for Patient test orders
Default = empty field
The system does not use
contents of this field for
Control test orders.
7.5 Patient ID No. 3 Alinity ci‑series Patient ID No. 3 Optional for Patient test orders
(Not Supported) Empty for Control test orders
ARCHITECT 20
Test Order record

The following table details the differences in the format of the Test Order record sent by the
host to the Alinity ci‑series or ARCHITECT System.
Field Characters
8.4.5 Universal 0 Empty Universal Test ID (part 1) - not used
Test ID 0 Êmpty Universal Test ID (part 2) - not used
4 Âssay Number Assay number that identifies the test
Alinity ci‑series 15 Âssay Name Assay name of the test
ARCHITECT 10
10 ^Dilution Sample Dilution protocol name used
for the test
Alinity ci‑series ^Status Assay status:
(Not Supported) (P, p, C, or c) P or p if assay is installed as the
ARCHITECT 1 primary version.
C or c if the assay is installed as the
correlation version (optional for all
test orders. If left blank, the system
places the test order for the primary
version of the assay).
support Assay Status component.
8.4.6 Priority 1 Alinity ci‑series S or s = Stat Priority Blank or any

S other character = Routine
ARCHITECT

80000456-102 - 2018-05-21

Field Characters
S or s NOTE: Alinity ci‑series does not
support "s".
8.4.12 Action Code 1 Alinity ci‑series N = New order for a specimen - only
N, A, or C create new order if the specified
assay in 8.4.5 does not already exist
ARCHITECT
for the specimen
N, A, C or Q
A = Add (unconditional) order for a
specimen - create order for the
specified assay in 8.4.5 even if an
order already exists for that assay
C - Cancel (delete) pending order for
the assay specified in 8.4.5
support "Q" = Control Sample.
8.4.13 Danger Code Alinity ci‑series Danger Code Part of the Test Order Comment
(Not Supported) Field (optional)
ARCHITECT 15
8.4.14 Clinical Alinity ci‑series Clinical Information Part of the Test Order Comment
Information (Not Supported) Field (optional)
ARCHITECT 15
8.4.16 Specimen Alinity ci‑series Specimen Type Part of the Test Order Comment
Type (Not Supported) Field (optional)
5
Specimen Alinity ci‑series ^Specimen Source
Source (Not Supported)
15
8.4.26 Report Types 1 Alinity ci‑series O (or o) = Order record; asking that
O or Q analysis be performed.
ARCHITECT Q (or q) = response to Query. (This
record is a response to an order
O or o
query request.)
Q or q
support "o" or "q".

80000456-102 - 2018-05-21
Comment record
The following table details the differences in the format of the Comment record sent by the host
to the Alinity ci‑series or ARCHITECT System.
Field Characters
10.4 Comment 50 Alinity ci‑series String Order comment text.
Text ARCHITECT NOTE: Alinity ci‑series truncates
Printable characters any text in excess of 50
characters.
Request Information record (Q), Alinity ci‑series

There are no differences in the Request Information record sent by the host to the
Alinity ci‑series and a Negative Query Response record sent by the host to the ARCHITECT
System.
Message Terminator record

There are no differences between the fields in the message terminator record.

80000456-102 - 2018-05-21
Revision history
Document control numbers Revision date Content revised

80000456-101 2016-12-12 Original release
80000456-102 2018-05-21 • Read me first: Updated the
copyright information for
Proprietary statement.
• Read me first: Updated the text
for Disclaimers.
• Read me first: Updated the
biological risk graphics, date of
manufacture graphic,
manufacturer graphic,
temperature limitation graphic,
and WEEE description for Key to
symbols.
• Read me first: Added the interior
light symbol and description for
Key to symbols.
• Read me first: Added the Assay
Availability row for Comparison
between available LIS interfaces:
CLSI (ASTM) vs. HL7.

80000456-102 - 2018-05-21
Revision history
NOTES

80000456-102 - 2018-05-21
Index
Index
A K
agency approvals key to symbols
description of, 10 descriptions of, 12
illustrations of, 12
C
S
customer service
contacting, 6 symbols
key to, 12
I
W
Intellectual Property statement
description of, 11 warranty
description of, 9

80000456-102 - 2018-05-21
Index

80000456-102 - 2018-05-21

80000456-102 Alinity ASTM LIS Interface

Uploaded by

Document Informationclick to expand document informationalinity manual

Document Informationclick to expand document information

Copyright:

Available Formats

80000456-102 Alinity ASTM LIS Interface

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

80000456-102 Alinity ASTM LIS Interface

Uploaded by

Copyright:

Available Formats

Alinity ci‑series LIS Interface

Alinity ci‑series LIS Interface Manual (ASTM) 3

Message Terminator record (L)...................................................................................39

4 Alinity ci‑series LIS Interface Manual (ASTM)

Alinity ci‑series LIS Interface Manual (ASTM) 5

6 Alinity ci‑series LIS Interface Manual (ASTM)

Alinity ci‑series LIS Interface Manual (ASTM) 7

8 Alinity ci‑series LIS Interface Manual (ASTM)

Alinity ci‑series warranty statement for USA

Alinity ci‑series LIS Interface Manual (ASTM) 9

Alinity ci‑series agency approvals

Legal Manufacturer Abbott GmbH & Co. KG

10 Alinity ci‑series LIS Interface Manual (ASTM)

Intellectual Property statement

Alinity ci‑series LIS Interface Manual (ASTM) 11

Caution: Consult accompanying documents

Caution: Hot surface

Caution: Possibility of electric shock

Caution: Probe stick hazard

Consult operating instructions

Disconnect Mains Plug

UL Recognized Component Mark

12 Alinity ci‑series LIS Interface Manual (ASTM)

WEEE: Waste Electrical and Electronic Equipment

Concentrated Wash Buffer

Distributed in the USA by

For use with

ICT Reference Solution

In Vitro Diagnostic Medical Device

Batch code/Lot number

Produced for Abbott by

Alinity ci‑series LIS Interface Manual (ASTM) 13

Catalog number/List number

Water Bath Additive

14 Alinity ci‑series LIS Interface Manual (ASTM)

Comparison between available LIS interfaces:

Alinity ci‑series LIS Interface Manual (ASTM) 15

Capability HL7 CLSI Comment

16 Alinity ci‑series LIS Interface Manual (ASTM)

Capability HL7 CLSI Comment

Alinity ci‑series LIS Interface Manual (ASTM) 17

18 Alinity ci‑series LIS Interface Manual (ASTM)

Alinity ci‑series LIS Interface Manual (ASTM) 19

Low-level protocol (CLSI LIS01-A2)

TCP/IP support only

Active persistent connection

20 Alinity ci‑series LIS Interface Manual (ASTM)

Alinity ci‑series LIS Interface Manual (ASTM) 21

Messaging protocol (CLSI LIS2-A2)

Logical information storage and transmission error recovery

22 Alinity ci‑series LIS Interface Manual (ASTM)

Example: Initial segments of a Message Structure

Line # Record Type Level Increment Action of Instrument

Records requiring retransmission

Line # where failure occurred Instrument would require retransmission of:

Alinity ci‑series LIS Interface Manual (ASTM) 23

Line # where failure occurred Instrument would require retransmission of: