BA400 LIS Protocol - ASTM+HL7 (v2.1.1) - FINAL

BA 400 LIS PROTOCOL SPECIFICATION
LIS2-A2 (ASTM) + HL7
version. 0.3
BA400 LIS PROTOCOL SPECIFICATION
June 19, 2013
TABLE OF CONTENTS
1
Introduction ............................................................................................................................... 9
1.1
Purpose .............................................................................................................................. 9
1.2
Overview ............................................................................................................................ 9
1.3
Definitions and Acronyms .................................................................................................. 9
1.4
References ........................................................................................................................ 10
1.5
Background and Terminology .......................................................................................... 10
Physical Layer ........................................................................................................................... 12

2.1
LIS01-A2 (ASTM) ............................................................................................................... 12
2.2
HL7.................................................................................................................................... 12
Transport Layer ........................................................................................................................ 15

3.1
Background....................................................................................................................... 15
3.2
Minimal Lower Layer Protocol ......................................................................................... 15
3.3
LIS01-A2............................................................................................................................ 16
3.3.1
Overview .................................................................................................................. 16
3.3.2
Establishment Phase (Link Connection) ................................................................... 16
3.3.3
Transfer Phase .......................................................................................................... 17
3.3.4
Termination Phase (link release) .............................................................................. 19
3.3.5
Error Recovery .......................................................................................................... 19
3.3.6
Valid Characters in the Text part .............................................................................. 20
Message Layer .......................................................................................................................... 21

4.1
Notation ........................................................................................................................... 21
4.2
Message length ................................................................................................................ 21
4.3
Records/Segments ........................................................................................................... 21
4.3.1
LIS2-A2 Records ........................................................................................................ 21
4.3.2
HL7 Segments ........................................................................................................... 23
4.4
Fields ................................................................................................................................ 23
4.4.1
Structure................................................................................................................... 23
4.4.2
Lengths ..................................................................................................................... 24
4.4.3
Character codes........................................................................................................ 24
4.4.4
Data Types ................................................................................................................ 24
4.4.5
Delimiters ................................................................................................................. 25
2 of 100
Biosystems. S.A.
Costa Brava, 30 - 08030 Barcelona, Spain Tel. +34 933110000 www.biosystems.es
Copyright 2013 Biosystems S.A. All rights reserved.
version. 0.3

4.4.6
Hexadecimal escaping .............................................................................................. 27
4.4.7
Local escape sequence ............................................................................................. 27
4.5
Acknowledge and error recovery ..................................................................................... 27
4.5.1
HL7............................................................................................................................ 27
4.5.2
LIS2-A2 ...................................................................................................................... 28
Workflow Scenarios ................................................................................................................. 31

5.1
AWOS transfer to the BA 400 before specimen arrival ................................................... 31
5.1.1
AWOS broadcast by the LIS before specimen arrival ............................................... 31
5.1.2
AWOS query by the BA 400 for ALL specimens before specimen arrival ................ 32
5.2
AWOS created at the BA 400 ........................................................................................... 32
5.3
AWOS Query by the Analyzer at specimen arrival ........................................................... 33
5.4
Rerun ................................................................................................................................ 33
5.4.1
Rerun decided on the BA 400 immediately after the first run................................. 33
5.4.2
Rerun decided during technical validation on the LIS .............................................. 34
5.4.3
Rerun decided during clinical validation on the Order Filler ................................... 34
5.5
June 19, 2013
Reflex [v2]......................................................................................................................... 35
5.5.1
Reflex decided on the BA 400 immediately after the first run ................................ 35
5.5.2
Reflex decided during clinical validation on the LIS ................................................. 36
5.5.3
Reflex decided during clinical validation on the Order Filler ................................... 36
5.6
Retransmit results from BA 400 ....................................................................................... 37
5.7
QC performed on an analyzer .......................................................................................... 37
5.8
Pooling of patient specimens [v2] .................................................................................... 37
5.9
Reason for Rejection orders (BA400 sends a rejection message for related order) ........ 38
5.9.1
Due to wrong syntax or unmapped values .............................................................. 38
5.9.2
Due to incorrect field content .................................................................................. 38
5.9.3
Due to Reruns requests ............................................................................................ 39
5.9.4
Due to Cancellations requested by LIS (Cancel message sent by LIS) ..................... 39
5.9.5
Due to Users actions ............................................................................................... 39
HL7 IHE-LAW Transaction LAB-27: Query for AWOS................................................................ 40

6.1
Introduction ..................................................................................................................... 40
6.2
Scope ................................................................................................................................ 40
6.3
Use Case Roles.................................................................................................................. 40
6.4
Referenced Standard........................................................................................................ 40
6.5
Interaction Diagram ......................................................................................................... 41

3 of 100
Biosystems. S.A.
version. 0.3

6.6
June 19, 2013
Message Static Definitions ............................................................................................... 41
6.6.1
Trigger Events ........................................................................................................... 41
6.6.2
Message Semantics .................................................................................................. 41
6.6.3
Expected Actions ...................................................................................................... 42
6.6.4
QPD Segment ........................................................................................................... 42
6.6.5
RCP Segment ............................................................................................................ 43
6.6.6
QAK Segment............................................................................................................ 44
HL7 IHE-LAW Transaction LAB-28: Analytical Work Order Step Broadcast ............................. 45
7.1
Scope ................................................................................................................................ 45
7.2
Use Case Roles.................................................................................................................. 45
7.3
7.4
7.5
7.5.1
Trigger Events ........................................................................................................... 46
7.5.2
7.5.3
HL7 IHE-LAW Transaction LAB-29: AWOS Status Change ........................................................ 52

8.1
Scope ................................................................................................................................ 52
8.2
Use Case Roles.................................................................................................................. 52
8.3
8.4
8.5
8.5.1
Trigger Events ........................................................................................................... 53
8.5.2
8.5.3
8.6
Common HL7 Segments ................................................................................................... 56
8.6.1
ERR Segment ............................................................................................................ 56
8.6.2
INV Segment ............................................................................................................. 57
8.6.3
MSA Segment ........................................................................................................... 58
8.6.4
MSH Segment ........................................................................................................... 58
8.6.5
NTE Segment ............................................................................................................ 60
8.6.6
OBR Segment............................................................................................................ 61
8.6.7
OBX Segment ............................................................................................................ 62
8.6.8
ORC Segment............................................................................................................ 66
4 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
8.6.9
PID Segment ............................................................................................................. 68
8.6.10
PV1 Segment ............................................................................................................ 69
8.6.11
SAC Segment ............................................................................................................ 69
8.6.12
SPM Segment ........................................................................................................... 70
8.6.13
TCD Segment ............................................................................................................ 72
8.6.14
TQ1 Segment ............................................................................................................ 73
LIS2-A2 Scenarios and Messages.............................................................................................. 74

9.1
AWOS query for all available orders. ............................................................................... 74
9.1.1
Analyzer sends query message to the LIS ................................................................ 74
9.1.2
LIS answers without orders ...................................................................................... 74
9.1.3
LIS answers with new orders or cancellation of orders ........................................... 75
9.2
AWOS broadcasted by the LIS .......................................................................................... 77
9.2.1
9.3
AWOS queried by the Analyzer at specimen arrival ........................................................ 78
9.3.1
Analyzer sends query message to the LIS ................................................................ 79
9.3.2
LIS answers without orders ...................................................................................... 79
9.3.3
9.4
AWOS acceptance/rejection by the Analyzer .................................................................. 80
9.4.1
Analyzer accepts the actions proposed by the LIS .................................................. 80
9.4.2
Analyzer rejects the actions proposed by the LIS .................................................... 81
9.5
Analyzer cancel orders already accepted......................................................................... 82
9.5.1
9.6
Analyzer cancel orders previously accepted ............................................................ 82
Upload of results .............................................................................................................. 83
9.6.1
Analyzer upload results for the first time ................................................................ 84
9.7
Rerun ................................................................................................................................ 85
9.8
Reflex ................................................................................................................................ 85
9.9
Retransmission ................................................................................................................. 85
10
LIS2-A2 Segments ................................................................................................................. 86
10.1
Header record .................................................................................................................. 86
10.1.1
Record Type ID ......................................................................................................... 86
10.1.2
Delimiter Definition .................................................................................................. 86
10.1.3
Message Control ID .................................................................................................. 86
10.1.4
Sender ID .................................................................................................................. 86
10.1.5
Receiver ID................................................................................................................ 86
5 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
10.1.6
Processing ID ............................................................................................................ 86
10.1.7
Version Number ....................................................................................................... 86
10.1.8
Date and Time of the Message ................................................................................ 86
10.2
Request record ................................................................................................................. 87
10.2.1
Record Type ID ......................................................................................................... 87
10.2.2
Sequence Number .................................................................................................... 87
10.2.3
Starting Range ID Number........................................................................................ 87
10.2.4
Request Information Status Code ............................................................................ 87
10.3
Termination record .......................................................................................................... 87
10.3.1
Record Type ID ......................................................................................................... 87
10.3.2
Sequence Number .................................................................................................... 87
10.3.3
Termination Code ..................................................................................................... 87
10.4
Patient record................................................................................................................... 88
10.4.1
Record Type ID ......................................................................................................... 88
10.4.2
Sequence Number .................................................................................................... 88
10.4.3
Laboratory-Assigned Patient ID................................................................................ 88
10.4.4
Patient Name............................................................................................................ 88
10.4.5
Birth date.................................................................................................................. 88
10.4.6
Patient Sex ................................................................................................................ 88
10.4.7
Location .................................................................................................................... 88
10.5
Order record ..................................................................................................................... 89
10.5.1
Record Type ID ......................................................................................................... 89
10.5.2
Sequence Number .................................................................................................... 89
10.5.3
Specimen ID.............................................................................................................. 89
10.5.4
Universal Test ID....................................................................................................... 89
10.5.5
Order Group ID ......................................................................................................... 90
10.5.6
Priority ...................................................................................................................... 90
10.5.7
Ordered Date and Time ............................................................................................ 90
10.5.8
Specimen Collection Date and Time ........................................................................ 90
10.5.9
Action Code .............................................................................................................. 90
10.5.10
Specimen Descriptor ............................................................................................ 90
10.5.11
Ordering Physician ............................................................................................... 90
10.5.12
Date/Time Results Reported ................................................................................ 90
10.5.13
User Field #1, QC Identifier .................................................................................. 90

6 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
10.5.14
User Field #1, QC Expiration date......................................................................... 90
10.5.15
User Field #1, QC Lot Number .............................................................................. 91
10.5.16
Lab. Field #1, Ordering Facility ............................................................................. 91
10.5.17
Lab. Field #1, Specimen Dilution Factor ............................................................... 91
10.5.18
Lab. Field #1, Automatic Rerun Allowed .............................................................. 91
10.5.19
Lab. Field #1, Automatic Reflex Allowed .............................................................. 91
10.5.20
Lab. Field #1, Parent Specimen ID ........................................................................ 91
10.5.21
Date /Time Results Reported ............................................................................... 91
10.5.22
Report Types ........................................................................................................ 91
10.6
Result record .................................................................................................................... 91
10.6.1
Record Type ID ......................................................................................................... 92
10.6.2
Sequence Number .................................................................................................... 92
10.6.3
Universal Test ID....................................................................................................... 92
10.6.4
Data or Measurement Value .................................................................................... 92
10.6.5
Units ......................................................................................................................... 92
10.6.6
Reference Ranges ..................................................................................................... 92
10.6.7
Result Abnormal Flags .............................................................................................. 92
10.6.8
Result Status ............................................................................................................. 92
10.6.9
Operator ID............................................................................................................... 93
10.6.10
Date/Time test completed ................................................................................... 93
10.6.11
Instrument ID ....................................................................................................... 93
10.7
Comment record .............................................................................................................. 93
10.7.1
Record Type ID ......................................................................................................... 93
10.7.2
Sequence Number .................................................................................................... 93
10.7.3
Comment Source ...................................................................................................... 93
10.7.4
Comment Text .......................................................................................................... 93
10.7.5
Comment Type ......................................................................................................... 93
11
Appendix A. Code Tables ...................................................................................................... 94
11.1
Error codes (To edit by Biosystems) ................................................................................. 94
11.2
Flag codes [v2.1] ............................................................................................................... 94
12
Appendix B. Example Traces ................................................................................................ 95
12.1
LIS2-A2 Query ................................................................................................................... 96
12.2
LIS2-A2 Positive Response Patient (Orders send from LIS) ........................................... 96
12.3
LIS2-A2 Positive Response External QC (Orders send from LIS).................................... 96

7 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
12.4
LIS2-A2 Positive Response Internal QC (Orders send from LIS) .................................... 96
12.5
LIS2-A2 Negative Response to a Query All Message ........................................................ 97
12.6
LIS2-A2 Negative Response to a Query by specimen (Host Query Message) .................. 97
12.7
LIS2-A2 Upload Result Patient (without Flags)................................................................. 97
12.8
LIS2-A2 Upload Result Patient (with Flags) ...................................................................... 97
12.9
LIS2-A2 Upload Result External QC .................................................................................. 98
12.10
LIS2-A2 Upload Result Internal QC ............................................................................... 98
12.11
HL7 Query All ................................................................................................................ 99
12.12
HL7 Host Query ............................................................................................................ 99
12.13
HL7 Order Download .................................................................................................... 99
12.14
HL7 Upload Results (patient with flags) ..................................................................... 100
12.15
HL7 Upload Results (QC without flags) ...................................................................... 100
12.16
HL7 Error message...................................................................................................... 100
8 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
1 Introduction
1.1 Purpose
This document specifies the interface protocol that provides BA 400 system to a Laboratory
Information Systems (LIS) software application. This interface forms the basis for the exchange of
healthcare information between BA 400 instrument and outside LIS, e.g., receiving laboratory
orders and generating laboratory results information.
This document is intended to be a guide for implementing the protocol to communicate to BA 400
instrument. In this guide, you will find detailed information of all the data that can be exchanged
between BA 400 and a Laboratory Information System (LIS).
1.2 Overview
The BA 400 supports two different messaging workflows or protocols:
HL7 implementation based on the recommendation described on the IHE Technical

Framework Laboratory Analytical Workflow Profile (IHE-LAW) v1.1.1 The
implementation of the HL7 protocol is compliant with the rules defined for IHE regarding
the LAW Profile version 1.1. In those cases where the Profile describes optional behaviour
the one chosen by the implementation is described.
Traditional LIS2-A2 (formerly ASTM 1394) protocol. The implementation of the LIS2-A2
protocol is compliant with the LIS2-A2 and LIS1-A2 communications standard.
This document intends to be descriptive enough for not requiring the reading of the IHE LAW
specifications document or the LIS2-A2/LIS01-A2 specifications document.
1.3 Definitions and Acronyms

Acronym
ANSI
ASCII
ASTM
HL7
IHE
LAW
LIS
LIS2-
Definition
American National Standards Institute (www.ansi.org)
American Standard Code for Information Interchange
American Society for Testing and Materials ( www.astm.org)
Health Level Seven (www.hl7.org)
Integrating the Healthcare Enterprise (www.ihe.net)
Laboratory Analytical Workflow
Laboratory Information System
Communication Protocol (High Level)
A
2
L
I
For those LIS which they are not able to be fully IHE-LAW compliant, the instrument offers a relaxed
version of the protocol
9 of 100
Biosystems. S.A.
version. 0.3
LIS1A
OSI
QC
TBC
TBD
UTF
June 19, 2013
S
2
A
2
Communication Protocol (Low Level)
Open System Interconnection
Quality Control
To be completed
To be defined
Unicode Transformation Format
1.4 References
NCCLS, NCCLS document LIS2-A2. Specification for Transferring Information Between Clinical
Laboratory Instruments and Information Systems; Approved Standard - Second Edition,
2004.
CLSI, CLSI document LIS01-A2. Specification for Low-Level Protocol to Transfer Messages
Between Clinical Laboratory instruments and Computer Systems; Approved StandardSecond Edition, 2008.
IHE Laboratory Technical Committee, IHE Laboratory Technical Supplement - Laboratory
Analytical Workflow (LAW) v1.1, March 9, 2012.
[1]
[2]
[3]
1.5 Background and Terminology

This document covers the exchange information between BA 400, acting as Analyzer, and an
Analyzer Manager (typically a LIS). In this context data transmission from BA 400 to a LIS is called
download and data transmission from BA 400 system to a LIS is called upload.
Since the HL7 implementation is based on IHE-LAW Profile, some concepts specific to this profile
shall be noted:
AWOS. Analytical Work Order Step. A Work Order Step in the LAW profile, representing a
test or panel to be performed on a specimen by an Analyzer, producing observations.
Battery. A set of one or more laboratory tests, identified by a single name and code, that
can be ordered to a laboratory. Synonym: Panel.
Order. A battery or test ordered by a ward and/or a physician to a laboratory, to be
performed on one or more specimens collected from a patient.
Order Filler. A system which manages orders on the laboratory side.
Order Group. Also called the Laboratory Request: A set of orders placed together by a
ward and/or a physician to one or more laboratories for a patient, to be performed on
one or more specimens collected from this patient.
Order Placer. A system that generates, places and manages orders.
Panel. Synonym for Battery.
Work Order. The testing of a battery or a test requested by the Order Filler to the
Analyzer Manager.
10 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
WOS. Work Order Step. A battery or test requested by the Analyzer Manager to the
Analyzer.
11 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
2 Physical Layer
BA 400 interface is TCP/IP based. Depending on the protocol used, a different usage of the TCP/IP
Sockets is performed.
2.1 LIS01-A2 (ASTM)

For LIS01-A2, a TCP/IP connection will be established during system start-up and maintained
permanently as long as the system is up.
BA 400 supports two configurable modes of operation:
TCP/IP-Server (LIS as Client).

TCP/IP-Client (BA 400 as Client).
2.2 HL7
The HL7 2.5 standard does not define a network communications protocol. In this implementation
the Minimal Lower Layer Protocol is required (See Section 3.2).
For compatibility with IHE-LAW profile and other HL7 implementations, two modes of operations
are supported.
A TCP/IP connection will be established during system start-up and maintained

permanently as long as the system is up. BA 400 supports two configurable modes of
operation:
o TCP/IP (LIS as Client).
TCP/IP-Transitory Connection. Two TCP/IP connections will be used:
o When BA 400 wants to initiate a conversation, a network connection is initiated (a
socket is opened to the LIS IP and port). The messages related to that
conversation are sent and received through this socket. In the conversation ends
the socket is closed by any of the peers.
o When the LIS wants to initiate a conversation, a network connection is initiated (a
socket is opened, a socket is opened from the LIS to BA 400 IP and port). The
messages related to that conversation are sent and received through this socket.
If the conversation ends the socket is closed by any of the peers.
Please refer to BA 400 configuration manual for information on how to configure either of the
two modes.
The two modes are illustrated in the following figure:
12 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
Single TCP/IP Connection:
Analyzer Manager
Analyzer
Message 1
TCP/IP
Connection
ACK / Response to Message 1
Message 2
Where the connection is configured as follows:
One actors will be the TCP/IP server and which one the TCP/IP client. This decision does
not affect the message flow. In any case, the connection is open between the LIS and the
Analyzer. The messages are sent from one to the other in sequence, using always the
same connection. Usually this connection is open permanently as long as both systems
are online.
13 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
Double TCP/IP Connection:
TCP/IP
Connection
#1
Analyzer Manager
Analyzer
Message 1
TCP/IP
Connection
#2
Message 2
Where the connections are configured as follows:
TCP/IP Connection #1. The LIS listens to a specific TCP port. The Analyzer connects to the
LIS IP Address and port. The Analyzer opens the connection, sends the Message 1 and
waits for the response. The LIS answers backs using the same connection. The connection
is closed once the response message has been received by the Analyzer or in case of
timeout waiting for the response message.
TCP/IP Connection #2. The Analyzer listens to a specific TCP port. The LIS connects to the
Analyzer IP Address and port. It follows the same flow as the previous one, except that in
this case the initiator is the LIS and the receiver is the Analyzer.
14 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
3 Transport Layer
This is the Lower Layer Protocol used to communicate with the LIS. The following chapters are
dedicated to explain the message structure and content.
3.1 Background
The data link layer has procedures for connection establishment and release, delimiting and
synchronism, sequential control, error detection and error recovery. The application messages
passed from the upper layer are framed and then transmitted. The frames received are packaged
and then passed to the upper layer.
The Data Link Layer protocols supported by BA 400 are:
Minimal Lower Layer Protocol (MLLP) when using HL7 protocol.

LIS01-A2, when using LIS2-A2 as the high level protocol.
3.2 Minimal Lower Layer Protocol

The goal of the MLLP Message Transport protocol is to provide an interface between the
Application and the transport protocol that uses minimal overhead. MLLP is based on a
minimalistic OSI-session layer framing protocol. It is assumed that MLLP will be used only in a
network environment. Most of the details of error detection and correction are handled by the
lower levels of TCP/IP transport protocol and do not require any supplementation.
Message content is enclosed by special characters to form a Block. The Block format is as follows:
<SB>dddd<EB><CR>
<SB>: Start Block character (1 byte). ASCII <VT>: <0x0B>.

dddd: Data (variable number of bytes). This is the data content of the Block. The data can
contain any UTF-8 character values greater than 0x1F and the carriage return character,
<CR>.
<EB>: End Block character (1 byte). ASCII <FS>: <0x1C>.
<CR>: Carriage Return (1 byte). ASCII <CR> character: <0x0D>.
In pseudo BNF-notation the Content Block Format is as follows: Content-Block = SB, dddd, EB, CR.
dddd = ( printableChar | CR )-sequence.
printableChar = 0x20 | 0x21 | 0x22 | .. | 0xFF.
SB = 0x0B.
EB = 0x1C.
CR = 0x0D.
15 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
3.3 LIS01-A2
3.3.1 Overview
This standard uses a character-oriented protocol to send messages between directly connected
systems. The coding is the ANSI X3.4-1986 and some restrictions are placed on the characters that
can appear in the message content.
The data link mode of operation is a one-way transfer of information with alternate supervision.
Information flows in one direction at a time. Replies occur after information is sent, never at the
same time. It is a simple stop-and-wait protocol. The sender and receiver use timeouts to detect
the loss of coordination between them and provide a method for recovery the communication.
The two systems operate actively to transfer information. The remainder of the time the data link
is in a Neutral State. There are three phases involved in the transmission of message frames:
Establishment Phase (or Link Connection). Determines the direction of information flow
and prepares the receiver to accept information.
Transfer Phase in which the sender transmits messages to the receiver using frames.
Termination Phase in which the link is released and the sender notifies the receiver that
all messages are sent.
3.3.2 Establishment Phase (Link Connection)

3.3.2.1 Operation
The establishment phase determines the direction of the information flow and prepares the
receiver to accept the information.
The system with information available, the sender, initiates the establishment phase to notify the
receiver that information is available.
A system that does not have information to send monitors the data link to detect the
Establishment Phase. It acts as a receiver, waiting for the other system.
The sequence is as follows:
1. The sender determines that the data line is in a Neutral State.
2. The sender sends the <ENQ> transmission control character to the receiver. Sender will
ignore all responses other than <ACK>, <NAK> or <ENQ>.
3. At this point, there are two cases:
a. If the receiver is prepared to receive data, it responds with the <ACK> character to the
sender. The link connection is established, entering the Transfer Phase.
b. If the receiver is not ready to receive data it responds with the <NAK> character.
Upon receiving a <NAK>, the sender shall wait at least 10 seconds before transmitting
another <ENQ> transmission control character.
16 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
3.3.2.2 Contention
When the two systems simultaneously transmit <ENQ> the data link is in contention. In such
cases, the device has priority.
So, when an <ENQ> is received in response to an <ENQ>, the situation is solved as follows:
The system with priority waits at least 1 second before sending another <ENQ>.
The system without priority must stop trying to transmit and prepare to receive. When
the next <ENQ> is received it replies with an <ACK> or <NAK> depending on its readiness
to receive.
3.3.3 Transfer Phase

During the Transfer Phase, the sender shall transmit messages to the receiver until all messages
are sent.
3.3.3.1 Frames
Messages are sent in frames, each frame contains a maximum of 64000 bytes (including frame
overhead).
Messages longer than 64000 bytes are divided between two or more frames.
Multiple messages are never merged in a single frame. Every message must begin in a new frame.
A frame is one of two types: the Intermediate Frame (IF) and the End Frame (EF). Their only
difference relies on one transmission control character, but they are semantically different (see
below for details).
Intermediate frame
<STX> FN Text <ETB> C1 C2 <CR> <LF>
End frame
<STX> FN Text <ETX> C1 C2 <CR> <LF>
The last frame of a message always is an End Frame. All previous frames are sent as Intermediate
Frames.
A message containing 64000 bytes or less is sent in a single End Frame.
Longer messages are sent in intermediate frames with the last part of the message sent in an end
frame.
A brief description for every part of a frame is given in the table below:
Frame Part
<STX>
FN
Text
<ETB>
<ETX>
C1
Frame Part Description

Start of Text transmission control character
Frame Number (single digit comprised in the range 0-7) See
details in section Frame Number
Data content of Message
End of Transmission Block transmission control character
End of Text transmission control character
Most significant character of checksum (belonging to {0-9, A-F})
17 of 100
Biosystems. S.A.
version. 0.3

C2
<CR>
<LF>
June 19, 2013
See details in section Checksum

Least significant character of checksum (belonging to {0-9, A-F})
See details in section Checksum
Carriage Return ASCII character
Line Feed ASCII character
3.3.3.2 Frame number

The frame number (FN) permits the receiver to distinguish between new and retransmitted
frames.
The frame number begins at 1 with the first frame of the Transfer phase (see below). The frame
number is incremented by one for every new frame transmitted. After 7, the frame number rolls
over to 0, and continues in this fashion.
3.3.3.3 Checksum
The checksum permits the receiver to detect a defective frame. The checksum is encoded as two
characters.
The checksum is computed by adding the binary values of the characters, and keeping the least
significant eight bits of the result. It is an addition module 256.
The checksum is initialized to zero with the <STX> character. The checksum computation uses the
FN, all characters belonging to Text and <ETB> or <ETX>. The computation for the checksum does
not include <STX>, the checksum characters, or the trailing <CR> and <LF>.
The checksum is an integer of eight bits, and can be considered as two groups of four bits. Both
groups of four bits are converted to the ASCII characters of the hexadecimal representation, and
transmitted as the message checksum.
Example: A checksum of 89 can be represented as 01011011 in binary or 5B in hexadecimal. The
checksum is transmitted as the ASCII character 5 followed by the ASCII character B.
3.3.3.4 Acknowledgements
After a frame is sent, the sender stops transmitting until a reply is received (stop-and-wait
protocol). The receiver can reply to each frame in three ways:
A reply of <ACK> means the last frame was successfully received and the receiver is ready
to receive the next one. The sender must send a new frame or terminate.
A reply of <NAK> signifies the last frame was not successfully received and the receiver is
prepared to receive the frame again.
A reply of <EOT> means the last frame was successfully received, but the receiver
requests the sender to stop transmitting.
18 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
This reply must be transmitted within the timeout period specified in the timeouts section.
3.3.3.5 Receiver Interrupts
During the transfer phase, if the receiver responds to a frame with an <EOT> in place of the usual
<ACK>, the sender must interpret this reply as a receiver interrupt request. The <EOT> is a
positive acknowledgement of the end frame, signifies the receiver is prepared to receive next
frame and is a request to the sender to stop transmitting.
If the sender chooses to ignore the <EOT>, the receiver must re-request the interrupt for the
request to remain valid.
If the sender chooses to honor the <EOT>, it must first enter the termination phase to return the
data link to the neutral state. The original sender must not enter the establishment phase for at
least 15 seconds or until the receiver has sent a message and returned the data link to the neutral
state.
BA 400 usage: BA 400 shall ignore the interrupt request. The instrument system ignores the
<EOT> until the message transmission is completed. If the instrument system receives and <EOT>
as an answer to the last frame, it waits 15 seconds until it goes to the establishment phase.
3.3.4 Termination Phase (link release)
The Termination Phase returns the data link to the neutral state. The sender initiates the
Termination Phase by transmitting the <EOT> character and then regards the line to be in the
Neutral State. After receiving the <EOT> the receiver also regards the line to be in the neutral
state.
3.3.5 Error Recovery
3.3.5.1 Defective frames
A receiver checks every frame to guarantee it is valid. A reply of <NAK> is transmitted for invalid
frames. Upon receiving the <NAK>, the sender retransmits the last frame with the same frame
number.
A frame should be rejected because take place some of the following situations:
Any character errors are detected (parity errors, framing error).

The frame checksum does not match the checksum computed on the received frame.
The frame number is not the same as the last accepted frame or one number higher
(modulo 8).
There are invalid characters in the message body.
Any characters occurring before <STX> or <EOT>, or after the end of the block characters (<ETB>
or <ETX>), are ignored by the receiver when checking for frame validity.
19 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
Every time the sender tries to transmit a particular frame, and receives a <NAK> or any other
character different from <ACK> or <EOT> (a <NAK> condition), a retransmission counter for the
given frame is increased. If this counter shows a single frame was sent and not accepted six times,
the sender must abort this message by proceeding to the termination phase.
3.3.5.2 Timeouts
The sender and the receiver use timers to detect loss of coordination between them:
During the establishment phase, the sender sets a timer when transmitting the <ENQ>. A
timeout occurs if a reply of an <ACK>, <NAK> or <ENQ> is not received within 15 seconds.
After a timeout, the sender enters the termination phase.
During the establishment phase, if the system without priority detects contention, it sets
a timer. If the subsequent <ENQ> is not received within 20 seconds, it will regard the line
to be in the neutral state.
During the transfer phase, the sender sets a timer when transmitting the last character of
a frame. If the reply is not received within 15 seconds, a timeout occurs. After a timeout,
the sender aborts the message transfer by proceeding to the termination phase.
During the transfer phase, the receiver sets a timer when first entering the transfer phase
or when replying to a frame. If a frame or an <EOT> is not received within 30 seconds, a
timeout occurs. After a timeout, the receiver discards the last incomplete message and
regards the line to be in the neutral state.
A receiver must reply to a frame within 15 seconds or the sender will timeout.
3.3.6 Valid Characters in the Text part

The data link protocol is designed for sending character based message text. There are restrictions
on which characters may appear in the message text. These restrictions make it simpler to
recognize frames, replies and avoid interfering with software controls for devices.
The restricted characters are: <SOH>, <STX>, <ETX>, <EOT>, <ENQ>, <ACK>, <DLE>, <NAK>,
<SYN>, <ETB>, <LF>, <DC1>, <DC2>, <DC3> and <DC4>.
3.3.6.1 Checking channel status
To test the connection, the BA400 transmits the ASCII <ENQ> transmission control character,
decimal value 5. If the receiving system responds within fifteen seconds with one of the following:
The ASCII <ACK> transmission control character, decimal value 6,

The ASCII <NAK> transmission control character, decimal value 21, or
<ENQ>.
The instrument system enters the Termination phase and the result of the connection test is
success. If the instrument system does not receive one of the above responses within 15 seconds,
the instrument system enters the Termination phase and the result of the connection test is
failure.
20 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
4 Message Layer
Messages consist of a hierarchy of records of various types. A record can be defined as an
aggregate of fields describing one aspect of the complete message. A field can be seen as a
specific attribute of a record, which may contain aggregates of data elements further refining the
basic attribute.
4.1 Notation
Each message is defined in special notation that lists the record (for LIS2-A2) / segment (for HL7)
in the order they would appear in the message.
Braces, { . . . }, indicate one or more repetitions of the enclosed group of segments. Of course, the
group may contain only a single segment.
Brackets, [ . . . ], show that the enclosed group of segments is optional. If a group of segments is
optional and may repeat it should be enclosed in brackets and braces, [{...}]
4.2 Message length

The standard does not impose a maximum record length. Outgoing messages can be of any size.
4.3 Records/Segments
Both LIS2-A2 and HL7 protocols organize the information in records or segments. Each of them is
responsible of carrying some type of information within the message
4.3.1 LIS2-A2 Records
In LIS2-A2 the records have a hierarchical relationship. The hierarchy of records is composed by
several levels. The record types allowed in each hierarchy level, and the hierarchical dependencies
between record types, are showed below.
Level 0 records
Message Header (H)
Level 1 records
Level 2 records
Level 3 records
Level 4 records
Comment (C)
Request Information (Q)
Comment(C)
Patient Information (P)
Comment (C)
Test Order (O)
Comment (C)
Result (R)
Comment (C)
Message Terminator (L)
Due to the use of this hierarchical structure, some rules have been established:
21 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
A message shall be always headed by a message header record (H), and finished by a
message terminator record (L).
An order record (O) may never appear without a preceding patient information record (P).
A result record (R) may never appear without a preceding order record (O).
Comment records (C) may be inserted at any level in the hierarchy (except after a
Message Terminator), and it refers to the prior higher-level record.
An example of a message structure and content, according to the records hierarchy described
before, is the following:
(Level 0)
MESSAGE HEADER
(Level 1)
PATIENT_1
(Level 2)
COMMENT_1
(Level 2)
ORDER_1
(Level 3)
COMMENT_1
(Level 3)
RESULT_1
(Level 3)
RESULT_2
(Level 4)
COMMENT_1
(Level 4)
COMMENT_2
.
.
(Level 3)
(Level 2)
RESULT_N
ORDER_2
(Level 3)
RESULT_1
(Level 3)
RESULT_2
.
.
(Level 3)
RESULT_N
.
.
(Level 2)
ORDER_N
22 of 100
Biosystems. S.A.
version. 0.3

(Level 3)
June 19, 2013
RESULT_1
.
.
(Level 1)
PATIENT_2
.
.
(Level 1)
(Level 0)
PATIENT_N
MESSAGE TERMINATOR
A sequence of patient information records, order records, or result records at one level, is
terminated by the appearance of a record type of the same or higher level.
4.3.2 HL7 Segments
A message is the atomic unit of data transferred between systems. It is comprised of a group of
segments in a defined sequence. Each message has a message type that defines its purpose. A
three-character code contained within each message identifies its type.
The real-world event that initiates an exchange of messages is called a trigger event. These events
(a three letter code) represent values such as A patient is admitted or An order event occurred.
There is a one-to-many relationship between message types and trigger event codes. The same
trigger event code may not be associated with more than one message type; however a message
type may be associated with more than one trigger event.
A segment is a logical grouping of data fields. Segments of a message may be required or optional.
They may occur only once in a message or they may be allowed to repeat. Each segment is given a
name. For example, the ADT message may contain the following segments: Message Header
(MSH), Event Type (EVN), Patient ID (PID), and Patient Visit (PV1). Each segment is identified by a
unique three-character code known as the Segment ID.
4.4 Fields
4.4.1 Structure
A field can be seen as a specific attribute of a record, which may contain aggregates of data
elements further refining the basic attribute. There are two kinds of aggregates within a message,
the repeat field and the component field. HL7 specifications adds another level of detail, the
subcomponent field
Repeat field a single data element that expresses a duplication of the field definition. Each
element of a repeat field is to be treated as having equal priority to associated repeat fields.
23 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
Component field single data element or data elements that express a finer aggregate or
extension of data elements, which precede it.
Subcomponent field (HL7 only) an even finer aggregate or extension of data expressed in a
component.
Example: A patients name is recorded as last name, first name, and middle initial, each of which is
separated by a component delimiter.
4.4.2 Lengths
The standard does not impose a maximum field length, and assumes that all fields are variables in
length. The instrument system implementation restricts the maximum field length to a concrete
value depending on the field, but never uses more characters than required by the given field
value (according to the standard).
Example: For a ten characters length field, only ten characters space will be used in the message to
allow the field content, delimiters space apart.
4.4.3 Character codes
All data is represented as eight bit values and single-byte as defined in ISO 8859-1:1987. The
eight-bit values within the range from 0 to 127 of ISO 8859-1:1987 correspond to the ASCII
standard character set (ANSI X3.4-1986). Values between 128 and 255 are undefined by this
standard and are sent using the codepage specified in the instrument system configuration. The
use of different codepages allows characters from different cultures to be exchanged without
problems. Other characters not represented using the specified codepage are sent escaped using
UTF-16 as described in 4.4.6.
Allowed characters in the message:
9, 13, 32-126, 128-254
Disallowed characters in the message: 0-8, 10-12, 14-31, 127, 255

The Latin-1 character 13 is reserved as the record terminator.
Although ISO 8859-1:1987 is the character set used by the standard to encode the message sets
can be used. The message carry on the header record the character set used to encode the
message.
4.4.4 Data Types
Data type is the basic building block used to restrict the contents of a data field. There are
differences between LIS2-A2 and HL7 data types. In fact, HL7 types are much more restrictive
than LIS2-A2 types. These are the data types in the messages used by the instrument system.
LIS2-A2 Data Types used
Name
String
Numeric
Description
String. Can have a maximum length
Number coded as string. Can have a maximum and minimum
value.
Default Length
24 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
LIS2-A2 Data Types used

LIS2-A2
Date
Timestamp (Date and Time) YYYYMMDD[HHMMSS]
HL7 Data Types used

Name Description
ST
String. Can have a maximum length
NM
Numeric. Formatted with English
HD
System identifier. Coded as string (can have several components)
ID
Identifier. Coded as string with a limited number of valid values.
TS
Timestamp (Date and Time) YYYYMMDD[HHMMSS]
SI
Sequence Integer. Positive integer.
MSG
Message Type. Composed by two or three strings that identifies a
HL7 message
14
Default Length
14
4
4.4.5 Delimiters
4.4.5.1 Types
Delimiters are used to establish separate sections within a message. There are five different
delimiters.
Record delimiter: It signals the end of any of the defined record types. It is fixed to
carriage return character Latin-1 (13) (ASCII 13).
Field delimiter: It is used to separate adjacent fields. It is configurable, and is specified in
the message header record. It shall be a single character excluding Latin-1 (13) (ASCII 13).
Repeat delimiter: Used to separate variable number of descriptors for fields containing
parts of equal members of the same set. It is configurable, and is specified in the message
header record. It shall be a single character, excluding Latin-1 (13) (ASCII 13) and the value
used by the field delimiter.
Component delimiter: It is used to separate data elements of fields of a hierarchical or
qualifier nature. It is configurable, and is specified in the message header record. It shall
be a single character, excluding Latin-1 (13) (ASCII 13), the value used by the field
delimiter and the value used by the repeat delimiter.
Subcomponent delimiter (HL7 only): Separates adjacent subcomponents of data fields
where allowed. If there are no subcomponents, this character may be omitted.
Escape delimiter: Used within text fields to signify special case operations. It is
configurable, and is specified in the message header record. It has a complex structure,
but mainly use a single character. The chosen character shall be different from Latin-1
(13) (ASCII 13) and the field, repeat, and component delimiter values.
4.4.5.2 Considerations
Alphanumeric characters should not be used as delimiters, according to the standard. The
instrument system implementation allows the use of the following characters as delimiters.
(Boundary values are also included)
25 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
Any value from ASCII (33) to ASCII (47)

The instrument system default delimiters are the following set for ASTM:
Field delimiter vertical bar

Repeat delimiter backslash
Component delimiter caret
Escape delimiter
( | ) Latin-1 (124)
(\ ) Latin-1 (92)
( ^ ) Latin-1 (94)
(& ) Latin-1 (38)
(ASCII 124)
(ASCII 92)
(ASCII 94)
(ASCII 38)
The instrument system default delimiters are the following set for HL7:
Field delimiter vertical bar

Component delimiter caret
Repeat delimiter tilde
Escape delimiter backslash
Subcomponent delimiter
( | ) Latin-1 (124)
( ^ ) Latin-1 (94)
( ~ ) Latin-1 (126)
( \ ) Latin-1 (92)
( & ) Latin-1 (38)
(ASCII 124)
(ASCII 94)
(ASCII 126)
(ASCII 92)
(ASCII 38)
Fields shall be identified by their position, obtained by counting field delimiters from the front of
the record. This position-sensitive identification procedure requires that when the contents of the
field are null, its corresponding field delimiter must be included in the record to ensure that the
field can be found by counting (i-1) delimiters. Delimiters are not included for trailing null fields.
Ex:
For ASTM: |\^&
For HL7: |^~\&
The following escape sequences are pre-defined.
\H\ (*)
\N\ (*)
\F\
\S\
\R\
\E\
\T\
\Xhhhh\
\Zcccc\
start highlighting text

normal text (end highlighting)
embedded field delimiter character
embedded component field delimiter character
embedded repeat field delimiter character
embedded escape delimiter character
embedded subcomponent delimiter character (HL7 only)
hexadecimal data See 4.4.6 for more information
Local defined escape sequences, used to send characters not represented
in the configured codepage. See 4.4.7 for more information.
No escape sequence contains a nested escape sequence, according to the standard.

(*) The escape sequences marked above with an asterisk are ignored by the instrument system
26 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
4.4.6 Hexadecimal escaping

The escaping of LIS2-A2 or HL7 disallowed characters happens when the instrument system wants
to send a character that is not allowed in LIS2-A2 or HL7. Characters that can be escaped are the
ASCII characters 10, 13, 127, 255. In this case, the character will be escaped using the hexadecimal
escaping. For example, if the instrument system wants to send the character 127 it will be
escaped to \X7F\.
4.4.7 Local escape sequence
Local escape sequence is used to exchange characters not represented using the configured
codepage. For example, if the instrument system wants to send a Japanese character (for example
the Unicode character U+34C8) using the English codepage, the character would be lost in a
normal transmission because it cannot be represented in that specific codepage.
To avoid losing any character, characters not represented in the selected codepage are escaped
using the local escape sequence. In that case, the Japanese character will be sent in four
hexadecimal digits as \Z34C8\. Also note, that many non-represented codepage characters can be
added in the same escape sequence.
4.5 Acknowledge and error recovery

The acknowledge and error recovery is different in HL7 and LIS2-A2.
4.5.1 HL7
The Message Header Segment (MSH) contains several fields that control the later message flow.
The sending application shall populate the MSH fields in the following manner:
MSH.10 populated with a unique identifier for the message. Acknowledgements in

response to this message shall refer to this ID.
MSH.15 is set to ER, thus instructing the receiving application to send an Accept
Acknowledgement only in case of error at this level (e.g. syntactical error, communication
error)
MSH.16 is set to AL: The message requires an application acknowledgement.
Thus there shall be always one and only one acknowledgement message coming back to the
sending application.
Upon receipt of the message the receiving application can make an initial determination as to
whether or not the message can be accepted. If this acceptance validation fails the system shall
reject the message with an accept acknowledgment populating the acknowledgment code
(MSA.1) with:
1. CR Commit reject if the one of the values of message type (MSH.9), version ID (MSH.12)
or processing ID (MSH.11) is not acceptable to the receiving application.
2. CE Commit error if the message cannot be accepted for any other reason (e.g., required
field is not present).
The Accept Acknowledgment message shall populate fields MSH.15 and MSH.16 with an NE.
27 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
If the message is accepted the receiving application shall then process it. In case the header
indicates it (MSH.16) the receiving application shall reply with an Application Acknowledgment.
The Acknowledgement Code (MSA.1) of the acknowledgment shall be one of the following:
1. AA indicates the message has been processed successfully.
2. AE indicates application error. The response message shall provide additional error
information.
3. AR indicates failure to process (reject) the message for reasons unrelated to its content
or format (analyzer busy, system down, internal error, etc.).
In case of application error or reject, the message is not resent anymore.
4.5.2 LIS2-A2
In order to ensure proper error logging and error recovery, the next rule is followed according to
the standard.
Storage Rule: Since data content is structured in hierarchical fashion, any decreasing change in the
hierarchical level triggers storage of all data transmitted prior to said level change,
and not previously saved.
An example of the prior rule application is the following.
Record #
Record Type
Storage action
Level
(level variation)
Message Header
L0
(0)
L1
(+1)
L2
(+1)
L3
(+1)
Order2
L2
(-1)
Order3
L2
(0)
L1
(-1)
L2
(+1)
Patient1
Order1
Result1
{Save 1
4}
6
7
Patient2
{Save 5
6}
8
Order1
Comment1
L3
(+1)
10
Result1
L3
(0)
L4
(+1)
11
Comment1
28 of 100
Biosystems. S.A.
version. 0.3

12
June 19, 2013
Result2
L3
(-1)
{Save 7
L2
(-1)
{Save 12}
L1
(-1)
{Save 13}
L2
(+1)
L3
(+1)
L0
(-3)
11}
13
Order2
14
Patient3
15
Order1
16
17
Result1
Message Terminator
16}
{Save 14
Note: Record # 17 is assumed as saved by virtue of the record type function.

If a transmission failure occurs, transmission starts at the last record not presumed saved. In order
to fulfil hierarchical record level requirements, all records necessary to reach the restart record
point are repeated prior to transmitting the record where the line failure originally occurred.
An example of required retransmissions is showed below.
Line failure at
Record Type
of
Message Header
Level (variation)
Patient1
Order1
Result1
Storage action
Retransmission
L0
(0)
L1
(+1)
1, 2
L2
(+1)
1, 2, 3
L3
(+1)
1, 2, 3, 4
Order2
L2
(-1)
Order3
L2
(0)
L1
(-1)
L2
(+1)
1, 7, 8
Patient2
Order1
{Save 1 4}
1, 2, 3, 4, 5
1, 2, 5, 6
{Save 5 6}
1, 2, 5, 6, 7
Comment1
L3
(+1)
1, 7, 8, 9
10
Result1
L3
(0)
1, 7, 8, 9, 10
(+1)
1, 7, 8, 9, 10, 11
11
Comment1 L4
12
Result2
L3
(-1)
{Save 7 11}
1, 7, 8, 9, 10,
11, 12
29 of 100
Biosystems. S.A.
version. 0.3

13
14
15
16
17
Order2
Patient3
Order1
Result1
Message Terminator
17
June 19, 2013
L2
(-1)
{Save 12}
1, 7, 8, 12, 13
L1
(-1)
{Save 13}
1, 7, 13, 14
L2
(+1)
1, 14, 15
L3
(+1)
1, 14, 15, 16
L0
(-3)
{Save 14 16}
1, 14, 15, 16,
30 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
5 Workflow Scenarios
5.1 AWOS transfer to the BA 400 before specimen arrival
In this use case the LIS sends to the BA 400 the scheduled list of AWOS prior to the specimen
arriving at the BA 400. The delivery to the BA 400, solicited or unsolicited, will be described in the
following two sub-cases.
Since the work list is transmitted before the specimen is present on the BA 400, in some cases it
may not be known which device will receive the specimen. Laboratories may have multiple BA
400 with similar analytical capabilities for fault tolerance redundancy or to keep up with the
workload. When an AWOS is scheduled on more than one BA 400, upon notification of AWOS
completion by one of the BA 400 who transmits back the results, the LIS shall cancel the other
redundant AWOS awaiting execution on the other BA 400.
5.1.1 AWOS broadcast by the LIS before specimen arrival
Initial part of the scenario:
1. The LIS sends the scheduled AWOS to the BA 400. Multiple AWOS may be grouped into a
single work list provided to the BA 400. Each AWOS represents an analytical service
requested on a specimen. In response to the AWOS broadcast, the BA 400 will notify the
LIS that the AWOS has been accepted. This is done implicitly, only rejections are explicitly
referenced in the message.
2. The BA 400 recognizes the specimen container (through barcode ID scanning or manual
entry) and selects the set of AWOS related to that specimen from its memory.
Final part of the scenario:
1. The BA 400 performs the AWOS (one or more) on that specimen.
2. The BA 400 notifies the LIS of the completion of the AWOS (one or more). This notification
message contains the results of the performed tests, fulfilling one or more AWOS, with
their related properties.
Exceptions handling:
1. In the case where the AWOS has not been received when the specimen container is
recognized, the BA 400 queries the LIS with the specimen container ID (transition to use
case 5.1.1 step b).
2. In the time between receipt of the AWOS and the specimen recognition by the BA 400,
the content of the Order Group, Order or Work Order may be modified (correcting
patient data, suppressing some tests, adding some new tests, shifting to another target
Analyzer) or even cancelled. Such events will require the cancellation of the original
AWOS on the LIS. Therefore, the LIS shall notify the cancellation to all BA 400 that
received the AWOS.
a. The LIS notifies the BA 400 to cancel the AWOS.
31 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
b. Each BA 400 notifies the LIS if the AWOS cancel is accepted. BA 400 will evaluate
the state of the AWOS and determine if cancellation is possible. If a BA 400
cannot cancel the AWOS, it will notify the LIS that it is unable to cancel. One of
the following actions will occur:
i. If processing on the AWOS has not started, the BA 400 will notify the LIS
that the cancel was accepted and discard the AWOS.
ii. If processing on the AWOS has started but the BA 400 cannot stop the
processing, then the cancellation is rejected. The BA 400 will then
transition to step b, Final part of the scenario of this use case.
5.1.2 AWOS query by the BA 400 for ALL specimens before specimen arrival
1. The BA 400 queries the LIS for all the scheduled AWOS assigned to it.
2. The LIS responds by sending the complete AWOS work list assigned to the BA 400,
and the BA 400 updates its local work list. In response to the AWOS receipt, the BA
400 will notify the LIS that the AWOS has been accepted or rejected. The acceptance
is done implicitly, only rejections are explicitly referenced in the message
3. Continue with step b) of the Initial part of the scenario from use case 5.1.1.
Same as use case 5.1.1.
Exception handling:
5.2 AWOS created at the BA 400

1. The AWOS is created at the BA 400. The laboratory technical staff manually entering the
AWOS on BA 400.
a. By using information printed from the LIS.
b. By using information: label on sample, information provided through a phone
conversation (in emergency cases for example), etc. The BA 400 does not create
an AWOS ID for the AWOS.
2. The BA 400 recognizes the specimen container (through barcode ID scanning, position
identification on the carrier, or manual entry) and selects the set of AWOS related to that
specimen from its memory.
1. The BA 400 performs the AWOS on that specimen.
2. The BA 400 notifies the LIS, with the status of the performed step. This notification
message contains the results and status of the performed clinical tests.
32 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
5.3 AWOS Query by the Analyzer at specimen arrival

1. The LIS schedules the AWOS but does not send it to the BA 400.
2. In the case where the LIS receives a Work Order update or cancellation, it cancels the
related AWOS appropriately, and creates a new one if needed.
3. The BA 400 system recognizes the specimen container (barcode scanning, location
information, or manual entry); afterwards it queries the LIS with the specimen container
ID or location information.
4. The LIS replies to the query with the AWOS to be performed.
Exceptions handling:
1. The specimen may be placed on the BA 400, before the Work Order has been received by
the LIS, and before the AWOS exist. In that case the query in step 3 is unsuccessful. The
answer sent in step 4 will be unknown specimen, no pending AWOS for it. Two events
may occur:
a. The BA 400 suspends processing of the specimen and tries the query later.
b. The AWOS is created at the Analyzer (transition to use case 5.2).
2. In this use case, the step to be performed on the BA 400 is sent by the LIS just in time,
when the BA 400 is ready to perform it on the specimen. Thus, there is no need to cancel
an AWOS that has been transferred to a BA 400.
5.4 Rerun
An AWOS usually needs one analytic run on the BA 400. In some circumstances the results
obtained from this first run need to be controlled by subsequent runs or reruns.
The need for a rerun may be decided:
Immediately after the first run on the BA 400, before uploading the results to the LIS.
During the technical validation of the Analytical Work Order with the first run results, on
the LIS application.
During the clinical validation of the order with the first run results, on the Order Filler
application.
Thus, three use cases to be considered:

5.4.1 Rerun decided on the BA 400 immediately after the first run
The rerun is decided automatically at the end of the first run or manually at any time during the
working session. The reason may be:
Results out of range, triggering a rerun with automatic dilution of the specimen.
33 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013

The initial part of the scenario can be from use case 5.1, 5.2 or 5.3.
1. The BA 400 performs the ordered step on that specimen (first run).
2. Based on the results obtained, the BA 400 schedules a second run.
3. After the appropriate fix (dilution, reagent refill, needle wash, calibration) the BA 400
performs the second run.
4. The BA 400 notifies the LIS, with the results and status of the second run. The extra test
results may be unexpected by the LIS, because more than one final test result is reported
for the same test. The AWOS ID is included when reporting test results for a rerun, as the
AWOS ID clearly identifies that the extra test results are associated with the original
AWOS request. When rerun test results are reported, it is up to the LIS and operator to
determine which test result (original or rerun) to report as the "clinically valid" test result.
5.4.2 Rerun decided during technical validation on the LIS

The control (rerun) is decided during the technical validation of the results of the first run,
compared with normal ranges, patients prior results, and other clinical information, or technical
information such as drifting or out of range quality control detected. This decision is taken by the
technical staff, or automatically by the LIS application.
2. The BA 400 notifies the LIS, with the results and status of the first run for this AWOS.
3. The technical validation of the results is performed on the LIS, resulting in a new run
requested with the same tests on the same specimen. This new run may be requested on
the same BA 400 or on another one (to confirm the results obtained on the first one).
The rerun picks up the scenario appropriate to the working mode of the BA 400 chosen for the
second run:
The LIS may send a new AWOS to it, for the same specimen and the same tests. This starts
a new 5.1.1 scenario.
Or if the BA 400 is working in query mode, the LIS schedules the new AWOS and waits for
the query from the BA 400. This starts a new 5.3 scenario.
5.4.3 Rerun decided during clinical validation on the Order Filler

The control (rerun) is decided during the clinical validation of the results of the whole order
group, considering the clinical consistency of this whole set of results, together with normal
34 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
ranges, patients prior results, and other clinical and technical information, or technical
information such as drifting or out of range quality control detected. This decision is taken by the
laboratory clinical expert, or by an automated expert system assisting the clinical expert.
In this situation, the final part of the first three scenarios ends normally. After the clinical
validation the Order Filler generates a new Work Order for the same patient, same specimen,
requesting the LIS to schedule the tests, on one of its Analyzers. This new Work Order may carry
some additional tests ordered in the meantime. It may possibly require a new aliquot.
This kind of rerun is supported and described by the use case 5.1, 5.2 and 5.3.
5.5 Reflex [v2]

An AWOS usually needs one analytic run on the BA 400. In some circumstances the results
obtained from this first run will trigger (manually) the need for one (or several) different test (i.e.
a reflex test).
The need for a reflex may be decided:
Either immediately after the initial test run on the BA 400, before uploading the results to
the LIS.
Or during the technical validation of the Analytical Work Order with the first run results,
on the LIS application.
Or later, during the clinical validation of the order with the first run results, on the Order
Filler application.
Thus, three use cases are to be considered:

5.5.1 Reflex decided on the BA 400 immediately after the first run
The reflex is decided manually, at the end of the first run. The reason may be:
Results in a particular range, triggering a reflex of a different test on the same specimen.
This reflex decision happens before the initial test results are uploaded to the LIS. The results of
the first run may be sent either before the results from the reflex test or may be held and sent
when the reflex test is complete.
The LIS may be notified of both the initial and reflex testing in order to track the BA 400
operations, and to register the reagent consumption.

35 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
2. Considering the results obtained, a second run is scheduled. The BA 400 sends the results
of the first test.
3. After the appropriate specimen is made available, the BA 400 performs the reflex test.
4. The BA 400 notifies the LIS, with the results and status of the first tests and reflex test
with all known information (patient, specimen, container, test).
5.5.2 Reflex decided during clinical validation on the LIS

The reflex is decided during the technical validation of the results of the first run, compared with
normal ranges, patients prior results, and other clinical information, or technical information.
This decision is taken by the technical staff, or automatically by the LIS application.
2. The BA 400 notifies the LIS, with the results and status of the first run for this AWOS.
3. The technical validation of the results is performed on the LIS, resulting in a new run
requested with different tests on the same specimen. This new run may be requested
on the same analyzer or on another one.
The reflex picks up the scenario appropriate to the working mode of the BA 400 chosen for the
second run:
The LIS may send a new AWOS to it, for the same specimen and new tests. This starts a
new 5.1.1 scenario.
If the BA 400 is working in query mode, the LIS schedules the new AWOS and waits for the
query from the BA 400. This starts a new 5.3 scenario
5.5.3 Reflex decided during clinical validation on the Order Filler

The reflex is decided during the clinical validation of the results of the whole order group,
considering the clinical consistency of this whole set of results, together with normal ranges,
patients prior results, and other clinical and technical information. This decision is taken by the
laboratory clinical expert, or by an automated expert system assisting the clinical expert.
In this situation, the final part of the first three scenarios ends normally. After the clinical
validation the Order Filler generates a new Work Order for the same patient, same specimen,
requesting the LIS to schedule the reflex tests on one of its BA 400. It may possibly require a new
aliquot.
This kind of reflex is supported and described by the first three scenarios.
36 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
5.6 Retransmit results from BA 400

Usually at the completion of a run, the BA 400 notifies the LIS one time with the status and the
test results of the performed AWOS. In some circumstances the AWOS results may be sent again
by the BA 400 to the LIS. This decision to send the results again is generally made manually by the
operator of the BA 400 in cases where the LIS was unable to receive and store the results of the
initial transmission, or in the case when a manual send of the results is used for testing purposes
of the connection between the BA 400 and the LIS.
In this situation, the LIS is responsible for determining if the results are the same as it has seen
previously (same AWOS, same BA 400, same test, same results) and acting accordingly. It shall not
reject the message from the BA 400 in the case of a retransmission, but shall either record the
event or ignore the retransmission, depending on application design.
5.7 QC performed on an analyzer

This use case is a specialization of the following use cases:
5.1 AWOS transfer to the BA 400 before specimen arrival.

5.2 AWOS created at the BA 400.
5.3 AWOS Query by the BA 400 at specimen arrival.
5.6 Retransmit results from BA 400.
In all these use cases the specimen is a QC specimen.
5.8 Pooling of patient specimens [v2]

This use case is a specialization of the following use cases:
5.1 AWOS transfer to the BA 400 before specimen arrival.

5.2 AWOS created at the BA 400.
5.3 AWOS Query by the BA 400 at specimen arrival.
5.4 Rerun
5.5 Reflex [v2]
5.6 Retransmit results from BA 400.
In some cases (molecular biology for example), the sample transmitted to the BA 400 is mixture of
several patient specimen.
If the BA 400 return a negative result all the patient specimen of the pool are considered
negative.
If the BA 400 returns a positive result, all the patient specimen of the pool have to be
tested individually.
The preceding uses cases, the following points have to be taken in account:
37 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
The ordering of pooled specimens assumes the LIS managing the specimen pool (e.g., by
connection to a pooling device) and the BA 400 responsible for measurement and
calculation of the result of the pooled specimen.
The Order send to the BA 400 should include the following information:
a. It is a pooled specimen.
b. The pool size, i.e., the number of specimens used for this specific sample. This
information is used in the calculation of the result (the negative specimens generally
"dilute" the result of positive specimens).
c. Optional list of specimen IDs used in the pool (for informational purpose at the BA
400).
5.9 Reason for Rejection orders (BA400 sends a rejection message for
related order)
5.9.1 Due to wrong syntax or unmapped values
Reason
Missing mandatory field
Field with data type different

than the expected
Field with length greater than the
allowed
Description
Missing value in a field marked as
REQUIRED in BA400 LIS Protocol
Specification document
Field with data type different of
the defined for it in BA400 LIS
Protocol Specification
Field with length greater than the
maximum value allowed for it in
BA400 LIS Protocol Specification
Field with incorrect format
Field with a format different than

the defined for it in BA400 LIS
Field with incorrect value
Field with a value different of the

list defined for it in BA400 LIS
Field with a value that is unknown
for BA400 (bad mapped fields)
Field with unknown value
ASTM example
Specimen ID (O3 segment)
not informed
Patient DOB (P8 segment)
does not contain a date
Patient Last Name (P6.1
segment) contains a value
with more than 30
characters
Patient DOB (P8 segment)
contains a valid date but
expressed with a format
different of YYYYMMDD
Priority (O6 segment) has a
value different of R and S
Sample Type (O16 segment)
or Test ID (O5.4 segment)
contain a value not mapped
in BA400
5.9.2 Due to incorrect field content

Unknown Test/Sample Type
Calculated Test that requires
more than one Sample Type
Duplicate Specimen
Duplicate request
Internal QC for a wrong
Test/Sample Type
Both fields Test ID and Sample Type are known for BA400, but the
Test has not programming defined for the Sample Type
Calculated Tests composed of Tests programmed with different
Sample Types
The same Specimen ID is sent for several different Patients
The same Test ID / Sample Type has been previously requested for
the same Patient and the result has not been still uploaded to LIS
Internal QC for Calculated or External Tests
Internal QC for Standard or ISE Tests that have not Quality
Control defined in BA400
38 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
5.9.3 Due to Reruns requests

Reruns requested by LIS are not
allowed
LIS requests a rerun for an
Internal QC
LIS requests a rerun for a wrong
Test/Sample Type
LIS requests a rerun for a different
Specimen ID
Rerun working mode has been set to: Analyzer Only into LIS
Configuration screen of BA400 Sw
LIS requests for Rerun of Internal Controls are not allowed in BA400
LIS requests for Rerun of Calculated and/or External Tests are not
allowed in BA400
LIS requests a Rerun after receiving the results of the previous
request, but sends it for a different Specimen
5.9.4 Due to Cancellations requested by LIS (Cancel message sent by LIS)

Unknown Test/Sample Type for
the Patient
The Test/Sample Type to cancel is
finished
The Test/Sample Type to cancel for a Patient does not exist in

BA400
Execution of the Test/Sample Type to cancel has finished (result has
been already obtained for it)
5.9.5 Due to Users actions

User deletes accepted LIS orders
that are pending of execution in
BA400
Required Specimen is not received

Lack of required Reagents
Other reasons
39 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
6 HL7 IHE-LAW Transaction LAB-27: Query for AWOS

6.1 Introduction
This transaction is used between a LIS and BA 400 working in query mode. It enables the LIS to
issue a new AWOS to the BA 400. This is a two-part transaction that requires two message
exchanges between the LIS and BA 400.
This transaction is used by the BA 400 to get the AWOS to perform for each specimen by querying
the LIS after specimen container recognition. The transaction provides an initial message
exchange of a query for one specimen or all specimens and the reply will carry the
acknowledgement status of the request. The LIS will follow the query exchange with a second
message exchange consisting of a LAB-28 AWOS Broadcast that provides the work to perform or
an indication there is no work for that specimen.
The BA 400 can send multiple queries prior to receiving the AWOS Broadcast from the LIS. This
allows the BA 400 to send a batch of queries, or asynchronous queries, without waiting for the
AWOS Broadcast of the two-part message exchange.
6.2 Scope
This transaction supports the use cases:
AWOS Query by the Analyzer for ALL specimens before specimen arrival.
AWOS Query by the Analyzer at specimen arrival.
It is used by the LIS and the BA 400 in "Query Mode".
6.3 Use Case Roles

ACTOR
ROLE
LIS
Manages the Work Orders and AWOS. Responds with to a query from
the Analyzer and sends the appropriate (positive acknowledgement,
negative acknowledgment) response. When the acknowledgement
response is positive, sends a LAB-28 AWOS Broadcast to the Analyzer.
Analyzer
Queries the LIS for a WOS related to the specimen, and receives the
query response. Waits for the LAB-28 AWOS Broadcast when a
positive query response is received. If no LAB-28 AWOS Broadcast for
the queried specimen is received by an Analyzer-specific period of
time, the Analyzer may notify the user that no AWOS was received.
6.4 Referenced Standard

HL7 version 2.5.1:
Chapter 5: Query QBP and RSP messages.

40 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
Chapter 5: Query QPD, RCP and QAK segments.
6.5 Interaction Diagram
LIS
BA 400
QBP^WOS^QBP_Q11
RSP^WOS^RSP_K11
6.6 Message Static Definitions

After the BA 400 working in query mode recognizes one or more specimens, the Analyzer sends a
WOS Query Message (QBP^WOS^QBP_Q11) for each specimen to the LIS.
The LIS replies with the response message (RSP^WOS^RSP_K11) containing the acknowledgement
of specimen query. The LIS will then respond with a LAB-28 AWOS Broadcast containing the work
for the specimen.
6.6.1 Trigger Events
QBP (Q11): Query for the WOS sent by the BA 400.
RSP (K11): Response including the WOS sent by the Automation Manager.
6.6.2 Message Semantics
6.6.2.1 QBP^WOS^QBP_Q11:
SEGMENT
MSH
MEANING
Message Header
USAGE
R
CARD.
[1..1]
HL7 CHAPTER
2
[{SFT}]
Software Segment
O1
[0..*]
QPD
RCP
Query Parameter Definition

Response Control Parameter
R
R
[1..1]
[1..1]
5
5
For BA 400 X.
41 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
MSH.9: QBP^Q11^QBP_Q11.
MSH.21: LAB-27ÎHE.
MSH|^~\&|BA400|Biosystems|Modulab|Systelab|20130416063226||QBP^Q11^QBP_Q1
1|822cc8b5-5f83-4f77-8173-66e3d942cb01|P|2.5.1|||ER|AL||UNICODE UTF8|||LAB-27ÎHE
QPD|WOS^Work Order
StepÎHE_LABTF|822cc8b55f834f77817366e3d942cb01|001000003
6.6.2.2 RCP|I||R<CR><FS><CR>RSP^WOS^RSP_K11:
SEGMENT
MEANING
USAGE
CARD.
HL7 CHAPTER
MSH
Message Header
[1..1]
[{SFT}]
Software Segment
O1
[0..*]
MSA
Message Acknowledgement
[1..1]
[ERR]
Error
[0..1]
QAK
Query Acknowledgement
[1..1]
QPD
Query Parameter Definition
[1..1]
Ignored by BA 400.
MSH.9: RSP^K11^RSP_K11.
MSH.21: LAB-27ÎHE.
QPD shall be the same as the QPD sent in QBP^WOS^QBP_Q11.
MSH|^~\&|Modulab|Systelab|BA400|Biosystems|20130129102030||RSP^K11^RSP_K1
1|67F2746D24014F21AD7139756F64CAD8|P|2.5.1|||ER|NE||UNICODE UTF-8|||LAB27ÎHE
MSA|AA|65F2746D24014F21AD7139756F64CAD8
QAK|65F2746D24014F21AD7139756F64CAD8|OK|WOS^Work Order StepÎHE_LABTF
QPD|WOS^Work Order StepÎHE_LABTF|67F2746D24014F21AD7139756F64CAD8|SPM01
6.6.3 Expected Actions

When specimen arrives on the BA 400 it sends a QBP message to the LIS to get the AWOS. This
QBP message may be for one specimen or for all specimens.
The LIS receives the QBP message and returns the RSP message with the query acknowledgment
status. The LIS prepares the AWOS by checking the container ID contained in the QBP message,
and initiates the LAB-28 AWOS Broadcast. The BA 400 receives the AWOS(s) and performs
processing for the specimen.
6.6.4 QPD Segment
SEQ LEN DT
USAGE
USAGE
CARD.
TBL#
NAME
42 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
ANALYZER ANALYZER
MGR.
1
60
CE
[1..1]
Message Query Name
32
ST
[1..1]
Query Tag
80
EI
[0..*]
SAC-3: Container Identifier
QPD.1 Message Query Name (CE), mandatory.

This field contains the value of the query for either a single sample or for all samples. The
contents for each query type are described below.
Query for a single sample
SEQ
1.1
1.2
1.3
COMPONENT/SUBCOMPONENT
Identifier
Text
Name of Coding System
LEN
DT
USAGE
3
15
9
ST
ST
ID
R
R
R
LEN
DT
USAGE
7
19
9
ST
ST
ID
R
R
R
COMMENT
WOS
Work Order Step
IHE_LABTF
Query for all samples samples

SEQ
1.1
1.2
1.3
Identifier
Text
COMMENT
WOS_ALL
Work Order Step All
IHE_LABTF
QPD-2: Query Tag (ST), mandatory.

A unique identifier assigned to each query message instance.
QPD-3 Container Identifier (EI), conditional.
The Analyzer is querying for the container id field identifies the container. It is expected that the
Container Identifier is the valued encoded on the container.
Predicate: When QPD.1.1 is WOS, QPD.3 must be populated if QPD.4 or QPD.6 is not populated.
Usage is Not Supported when QPD.1.1 is WOS_ALL.
SEQ
3.1
Entity Identifier
LEN
DT
USAGE
20
ST
COMMENT
6.6.5 RCP Segment

SEQ
LEN
DT
ID
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
M
CARD.
[0..1]
TBL#
0091
NAME
Query Priority
43 of 100
Biosystems. S.A.
version. 0.3

60
CE
June 19, 2013
[0..1]
0394
Response Modality
RCP-1 Query Priority (ID), mandatory.

This field is always set to the value of I for Immediate.
RCP-3 Response Modality (CE), mandatory.
This field is always set to the value of R for Realtime.
SEQ
3.1
Identifier
LEN
DT
USAGE
ST
COMMENT
Always set to R
6.6.6 QAK Segment

USAGE
USAGE
ANALYZER
ANALYZER
MGR.
SEQ
LEN
DT
CARD.
TBL#
NAME
32
ST
[1..1]
ID
[1..1]
0208
Quantity Response Status
38
CE
[1..1]
0471
Message Query Name
Query Tag
QAK-1 Query Tag (ST), mandatory.

This field contains QPD.2 Query Tag from the query message.
QAK-2 Query Response 2540 Status (ID), mandatory.
This field contains one of the following codes from the HL7 Table 0208.
VALUE
DESCRIPTION
OK
Data found: no errors
NF
No data found: no errors
AE
Application Error
AR
Application Rejects
COMMENTS
QAK-3 Message Query Name (CE), mandatory.

This field contains QPD.1 Message Query Name from the query message.
SEQ
3.1
Identifier
LEN
DT
USAGE
20
ST
COMMENT
Contains value from QPD.1
44 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
7 HL7 IHE-LAW Transaction LAB-28: Analytical Work Order Step

Broadcast
7.1 Scope
This transaction is used between a LIS and an Analyzer working in broadcast mode. It enables the
LIS to issue a new AWOS to the Analyzer or cancel an existing AWOS previously sent to the
Analyzer. Modification is achieved by combining cancellation and sending of a new AWOS.
7.2 Use Case Roles

ACTOR
ROLE
LIS
Translates a Work Order into a series of AWOS assigned to the

Analyzers.
Analyzer
Performs the AWOS on the specimen.

HL7 v2.5.1, Chapter 4 and Chapter 13:
OMLÔ33 and ORL^R34 message and response.

PID, PV1, SPM, SAC, ORC, TQ1, OBR, TCD, and NTE segments.
45 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
LIS
BA 400
OMLÔ33
New Order (ORC-1 : NW)
ORLÔ34
Order Accepted (ORC-1: OK)
Unable to Accept (ORC-1;UA)
OMLÔ33
Order Cancel (ORC-1: CA)
ORLÔ34
Order Cancelled (ORC-1: CR)
Unable to Cancel (ORC-1; UC)

This transaction contains the messages used to broadcast an Analytical Work Order Step (AWOS)
from the LIS to the Analyzer. It includes new AWOS, cancel AWOS and the related application
acknowledgements.
The message contains zero or more AWOSs for one or more Specimens. The AWOSs are grouped
by specimen.
OML (O33): AWOS sent by the LIS.
ORL (O34): Acknowledgement sent by the Analyzer.
46 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013

7.5.2.1 OMLÔ33
SEGMENT
MEANING
USAGE
CARD.
HL7 CHAPTER
2
MSH
Message Header
[1..1]
--- PATIENT BEGIN
[0..1]
PID
Patient Identification
[1..1]
[PV1]
Patient Visit
[0..1]
SPECIMEN begin
[1..*]
SPM
Specimen
[1..1]
[{SAC}]
Specimen Container
[1..1]
13
--- ORDER begin
[1..*]
ORC
Common Order (for one

battery)
[1..1]
[{TQ1}]
Timing Quantity
RE
[0..1]
--- OBSERVATION REQUEST

begin
RE
[0..1]
OBR
Observation Request
[1..1]
[{TCD}]
Test Code Details
[0..1]
13
[{
--- PRIOR RESULT begin
[0..*]
PV1
Patient Visit previous result
[1..1]
--- ORDER PRIOR begin
[1..*]
ORC
Common Order prior result
[1..1]
OBR
Order detail prior result
[1..1]
--- OBSERVATION PRIOR

begin
[1..*]
OBX
Observation/Result prior
result
[1..*]
[{NTE}]
Comment of the result
C1
[0..*]
--- PATIENT end

{
}
}
--- OBSERVATION PRIOR end

--- ORDER PRIOR end
47 of 100
Biosystems. S.A.
version. 0.3

SEGMENT
MEANING
}]
USAGE
CARD.
HL7 CHAPTER
--- PRIOR RESULT end

--- OBSERVATION REQUEST
end
]
}
--- ORDER end
}
1
June 19, 2013
--- SPECIMEN END
Ignored by BA 400.
MSH.9: OMLÔ33ÔML_O33.
MSH.21: LAB-28ÎHE.
SPM.11: Q (Control specimen) in the case of a QC AWOS, P (Patient) in the case of a patient
AWOS, and L (Pooled patient specimens) in the case of a pooled patient samples AWOS.
The OBSERVATION REQUEST group will not be present when ORC.1 = DC, which is Discontinue
Request. This indicates the message is in reply to a LAB-27 Query for AWOS and that there is no
work to perform for the sample container.
The PRIOR RESULT segment group provides the prior results obtained for the same patient.
Segment PID is not provided in this segment group because it is the same patient, and the
laboratory is not concerned by the fact that this patient might have had a different identification
when the prior results were produced.
Segment PV1, which is the first segment of the segment group PRIOR RESULT, is mandatory. The
presence of this segment at this point in the message structure announces unambiguously a set of
prior orders with related prior observations. The segment PV1 represents the patient visit (or
encounter) during which these prior observations were produced. The only field mandatory in the
segment PV1 is PV1.2 Patient Class. The sender of this message SHALL set the value the field
PV1.2 to U, which stands for patient class unknown.
The ORC appearing in the PRIOR RESULT segment group is mandatory and SHALL have its first
field Order Control populated with PR (Prior results).
Some Analyzers need Observation OBX, TCD, and NTE segments. Therefore, the message carries
an optional OBSERVATION segment group to provide the analyzer with results related to the tests
to be performed.
48 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
MSH|^~\&|Modulab|Systelab|BA400|Biosystems|20130129102030||OMLÔ33ÔML_O3
3|69F2746D24014F21AD7139756F64CAD8|P|2.5.1|||ER|AL||UNICODE UTF-8|||LAB28ÎHE
PID|||PID2||SURNAME^NAME2^^^^^L||19850819|M
SPM|1|SPECIMEN2||SER|||||||P||||||20130129092030|20130129112030
SAC|||||||||||||||||||||||||||||5
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||ALBUMIN^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||Na+^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||Li+^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||CK^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||CHOL HDL DIRECT^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||CALCIUM ARSENAZO^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||BILIRUBIN TOTAL^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||BILIRUBIN DIRECT^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||AMYLASE PANCREAT^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||AMYLASE EPS^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||AMYLASE DIRECT^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||ALP-DEA^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||ALP-AMP^T1^BA400
ORC|NW||||||||20130129101530
TQ1|||||||||R
OBR||AWOS2||ACID GLYCOPROTEI^T1^BA400
49 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
7.5.2.2 ORLÔ34
SEGMENT
MEANING
USAGE
CARD.
HL7 CHAPTER
MSH
Message Header
[1..1]
MSA
[1..1]
[{ERR}]
Error
[0..*]
--- RESPONSE begin
[0..1]
--- PATIENT begin
[0..1]
PID
[0..1]
--- SPECIMEN begin
[1..*]
SPM
Specimen
[1..1]
[{SAC}]
Specimen Container
[1..1]
13
[{
--- ORDER begin
[1..*]
ORC
Common Order (for one

battery)
[1..1]
}]
--- ORDER end
--- SPECIMEN end
--- PATIENT end
--- RESPONSE end
MSH-9: ORLÔ34ORL_O34.
MSH.21: LAB-28ÎHE.
ORC.2, Placer Order Number, will be used to uniquely identify the AWOS to the LIS when the
RESPONSE group is included.
The RESPONSE group may be used by the Analyzer to inform the LIS about the intent to perform
an individual AWOS contained in the OML message:
For accepted AWOS:

o ORC.1: OK.
o ORC.5: IP.
For rejected AWOS:
o ORC.1: UA.
o ORC.5: CA.
50 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
The RESPONSE group will be used by the Analyzer to respond to a cancellation request from the
LIS for each AWOS contained in the OML message:
In case of successful cancellation:

o ORC.1: CR.
o ORC.5: CA.
In case of not being able to cancel:
o ORC.1: UC.
o ORC.5: IP.
MSH|^~\&|BA400|Biosystems|Modulab|Systelab|20130416105615||ORLÔ34ÔRL_O3
4|af899d09-531c-4df7-9ff1-8aef1929b8eb|P|2.5.1|||ER|NE||UNICODE UTF8|||LAB-28ÎHE
MSA|AA|69F2746D24014F21AD7139756F64CAD8

The Analyzer receives the OMLÔ33 message from the LIS.
If the OML message contains the Order Control Code NW, the Analyzer will receive and register
the order information. As part of the ORLÔ34 response, it may transmit either Notification or
request accepted or Unable to accept order/service for each AWOS contained in the OML
message. See the ORC.1/ORC.5 discussion above for further details. The LIS will consider the
absence of a response for an individual AWOS the same as receiving a Notification or request
accepted for the AWOS from the Analyzer.
If the OML message contains the Order Control Code CA, the Analyzer will evaluate the cancel
request. As part of the ORLÔ34 response, the Analyzer will transmit either Cancel as requested
or Unable to cancel for each AWOS contained in the OML message. See the ORC.1/ORC.5
discussion above for further details.
51 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
8 HL7 IHE-LAW Transaction LAB-29: AWOS Status Change

8.1 Scope
This transaction is used by the Analyzer to send test results to the LIS.
8.2
Use Case Roles

ACTOR
ROLE
LIS
Manages Analyzer in order to implement the AWOS. Receives the test

results from Analyzer, performs technical validation, then sends the
validated results to Order filler.
Analyzer
Analyzes the specimen and outputs the test results.

HL7 Version 2.5 Chapter 7 and Chapter 13:
OUL^R22 message.
PID, PV1, SPM, OBX, SAC, INV, OBR, ORD, TCD, SID, and NTE Segments.
LIS
BA 400
OUL^R22
ACK^R22
52 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013

This transaction contains the messages used by the Analyzer to send the tests results when the
AWOS is complete. It also includes the related application acknowledgements from the LIS.
The message contains zero or more observations for one or more AWOSs for one or more
specimens. The observations are grouped by AWOS, and the AWOSs are grouped by specimen.
Analyzer sends test results. LIS returns acknowledgement.
8.5.2.1 OUL^R22
SEGMENT
MEANING
USAGE
CARD.
HL7
CHAPTER
2
MSH
Message Header
[1..1]
--- PATIENT begin
[0..1]
[1..1]
PID
--- PATIENT end
--- VISIT begin
[0..1]
Patient Visit
[0..1]
SPECIMEN begin
[1..*]
SPM
Specimen
[1..1]
[{OBX}]
Observation result (for

specimen)
[0..*]
[{
--- CONTAINER begin
[0..1]
SAC
Container information
[1..1]
13
[INV]
Detailed Substance
information
[0..1]
13
[PV1]
]
--- PATIENT end

{
}]
--- CONTAINER end
--- ORDER begin
[1..*]
OBR
Observation Order
[1..1]
[ORC]
Common Order
[0..1]
[{
--- Result begin
[0..*]
53 of 100
Biosystems. S.A.
version. 0.3

SEGMENT
MEANING
June 19, 2013
USAGE
CARD.
HL7
CHAPTER
OBX
Observation Result
[1..1]
[TCD]
Test Code Detail
[0..1]
13
[{SID}]
Substance Identifier (e.g.

reagent for testing)
[0..*]
13
[{NTE}]
Notes and comments
[0..*]
}]
--- RESULT end
--- ORDER end
--- SPECIMEN end
MSH.9: OUL^R22ÔUL_R22.
MSH.21: LAB-29ÎHE.
SPM.11: Q (Control specimen) in the case of a QC AWOS, P (Patient) in the case of a patient
AWOS, and L (Pooled patient specimens) in the case of a pooled patient samples AWOS.
MSH|^~\&|BA400|Biosystems|Modulab|Systelab|20130416071828||OUL^R22ÔUL_R2
2|80f1a9fe-cd54-41d4-87ca-4c30b059ac2b|P|2.5.1|||ER|AL||UNICODE UTF8|||LAB-29ÎHE
SPM|1|#201304150002||SER|||||||P|||||||
OBR||""||UREA-BUN-UVÛREA-BUN-UVÂ400|||||||||||||||||||||||||
ORC|OK||||CM||||20130416071828OBX|1|ST|UREA-BUN-UVÛREA-BUN-UVÂ400||1.351948|mg/dL^mg/dLÂ400||See Analyzer remarks for this LIS
order|||F|||||BIOSYSTEMS||A400^Biosystems~834000114^Biosystems|2013041514
5415
OBR||""||ALP-DEAÂLP-DEAÂ400|||||||||||||||||||||||||
ORC|OK||||CM||||20130416071828
OBX|1|ST|ALP-DEAÂLP-DEAÂ400||-0.8337101|U/LÛ/LÂ400||See Analyzer
remarks for this LIS
1412
OBR||""||BUN MOD^BUN MODÂ400|||||||||||||||||||||||||
ORC|OK||||CM||||20130416071828
OBX|1|ST|BUN MOD^BUN MODÂ400||-0.6317512|mg/dL^mg/dLÂ400||See Analyzer
remarks for this LIS
1702
8.5.2.2 ACK^R22
SEGMENT
MSH
MEANING
Message Header
USAGE
CARD.
HL7
CHAPTER
[1..1]
2
54 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
MSA
[1..1]
[ERR]
Error
[0..1]
MSH.9: ACK^R22ÂCK.
MSH.21: LAB-29ÎHE.
MSH|^~\&|Modulab|Systelab|BA400|Biosystems|20130129102030||ACK^R22ÂCK|71
F2746D24014F21AD7139756F64CAD8|P|2.5.1|||ER|NE||UNICODE UTF-8|||LAB29ÎHE
MSA|AA|88F2746D24014F21AD7139756F64CAD8

The Analyzer notifies the LIS of the test results using the OUL^R22 message. The LIS accepts and
registers information, and responds to the Analyzer with the ACK^R22 message.
55 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
8.6 Common HL7 Segments

8.6.1 ERR Segment
SEQ
LEN
2
3
4
18
705
2
1
2
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
ERL
C (M/X)1
C (M/X)2
CWE
M
M
ID
M
M
DT
CARD.
[1..*]
[1..1]
[1..1]
TBL#
0357
0516
NAME
Error Location
HL7 Error Code
Severity
For BA 400 X.
Ignored by BA 400.
ERR.3 HL7 Error Code (CWE), mandatory.

Identifies the HL7 (communications) error code. Only the first component (Identifier) is supported
using codes from the following subset of codes in HL7 Table 0357.
SEQ
3.1
Identifier
VALUE
DT
USAGE
ST
DESCRIPTION
100
Segment sequence error
101
Required field missing
102
Data type error
103
Table value not found
200
201
202
203
Unsupported message type

Unsupported event code
Unsupported processing id
Unsupported version id
204
Unknown key identifier
205
Duplicate key identifier
206
Application record locked
207
Application internal error
COMMENT
COMMENTS
Error: The message segments were not in the
proper order, or required segments are missing.
Error: A required field is missing from a segment
Error: The field contained data of the wrong data
type, e.g., an NM field contained "FOO".
Error: A field of data type ID or IS was compared
against the corresponding table, and no match
was found.
Rejection: The Message Type is not supported.
Rejection: The Event Code is not supported.
Rejection: The Processing ID is not supported.
Rejection: The Version ID is not supported.
Rejection: The ID of the patient, order, etc., was
not found. Used for transactions other than
additions, e.g. transfer of a non-existent patient.
Rejection: The ID of the patient, order, etc.,
already exists. Used in response to addition
transactions (Admit, New Order, etc.).
Rejection: The transaction could not be
performed at the application storage level, e.g.
Rejection: A catchall for internal errors not
explicitly covered by other codes.
ERR.4 Severity (ID), mandatory.

This field identifies the severity of an application error. The value of this field will always be E for
Error.
56 of 100
Biosystems. S.A.
version. 0.3

8.6.2 INV Segment
USAGE
SEQ LEN DT
ANALYZER
1
250 CE
M
2
250 CE
M
3
250 CE
M
12
26
TS
O
16 200 ST
O
June 19, 2013
CARD.
TBL#
NAME
[1..1]
[1..1]
[0..1]
[0..1]
[0..1]
0451
0383
0384
Substance Identifier
Substance Status
Substance Type
Expiration Date/Time
Manufacturer Lot Number
INV.1 Substance Identifier (CE), mandatory.

This is a manufacturer-specific unique identifier for the control material. If the control material is
in a bar-coded tube, this is also what is encoded in the barcode to identify the material.
SEQ
1.1
Identifier
LEN
DT
USAGE
20
ST
CONTENTS
Identifier of substance
INV.2 HL7 Substance Status (CE), mandatory.

This field contains a subset of values taken from HL7 Table 0383 as described below to identify
the current status of the substance.
SEQ
2.1
Identifier
LEN
DT
USAGE
ST
CONTENTS
Substance status
The value of this field will always be OK for OK Status.

INV.3 Substance Type (CE), mandatory.
This field contains a subset of values taken from HL7 Table 0384 to identify the material as
control material.
SEQ
3.1
Identifier
LEN
DT
USAGE
CONTENTS
ST
Type of substance (e.g.,

Control, Reagent, Bulk Supply,
Waste)
The value of this field will always be CO for Quality Control Specimen.
INV.12 Expiration Date/Time (TS), optional.
This is the expiration date of the material. Precision supported is to the day.
SEQ
12.1
YYYYMMDD
USAGE
COMMENT
INV.16 Manufacturer Lot Number

This is a manufacturer-specific lot number of the control material.
57 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
8.6.3 MSA Segment

SEQ
LEN
DT
1
2
2
50
ID
ST
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
M
M
M
M
CARD.
TBL#
[1..1]
[1..1]
00008
NAME
Acknowledgement Code
Message Control Id
MSA.1 Acknowledgement Code (ID), mandatory.

This element contains the acknowledgment code, per the HL7 message processing rules. The
following subset of codes from HL7 Table 0008 is supported.
VALUE
AA
DESCRIPTION
Original mode: Application Accept
AE
Original mode: Application Error
AR
Original mode: Application Reject
COMMENTS
Message processed and accepted
Message processed and was rejected
due to and error in either content of
format
Message rejected due to MSH error(s)
Note: the accompanying ERR segment to the MSA segment in the acknowledgement message will indicate the location
of the error.
MSA.2 Message Control Id (ST), mandatory.

This field contains the value in MSH-10 Message Control ID from the message being
acknowledged.
8.6.4 MSH Segment

USAGE
USAGE
DT
ANALYZER
ANALYZER
MGR.
SI
M
M
ST
M
M
HD
M
M
HD
M
M
HD
M
M
HD
M
M
TS
M
M
MSG
M
M
ST
M
M
PT
M
M
VID
M
M
SEQ
LEN
CARD.
TBL#
1
2
3
4
5
6
7
9
10
11
12
1
4
227
227
227
227
26
15
50
3
60
15
ID
[1..1]
0155
16
ID
[1..1]
0155
18
21
16
427
ID
EI
M
M
M
M
[1..1]
[1..1]
0211
01598
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
NAME
Field Separator
Encoding Characters
Sending Application
Sending Facility
Receiving Application
Receiving Facility
Date/Time of Message
Message Type
Message Control Id
Processing Id
Version Id
Accept Acknowledgement
Type
Application Acknowledgement
Type
Character Set
Message Profile Identifier
58 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
MSH.1 Field Separator (SI), mandatory.

This profile supports the HL7-recommended value; that is | (ASCII 124).
MSH.2 Encoding Characters (ST), mandatory.
This field must contain the four characters in the following 1625 order: the component separator,
repetition separator, escape character, and subcomponent separator. This profile supports the
HL7-recommended values ^~\& (ASCII 94, 126, 92, and 38, respectively).
MSH.3 Sending Application (HD), mandatory.
This field contains the name of the sending application.
SEQ
3.1
Namespace Id
LEN
DT
USAGE
20
IS
LEN
DT
USAGE
20
IS
CONTENTS
Vendor specified value
MSH.4 Sending Facility (HD), mandatory.

This field contains the name of the sending facility.
SEQ
4.1
Namespace Id
CONTENTS
Laboratory specified value
MSH.5 Receiving Application (HD), mandatory.

This field contains the name of the receiving application.
SEQ
5.1
Namespace Id
LEN
DT
USAGE
20
IS
CONTENTS
MSH.6 Receiving Facility (HD), mandatory.

This field contains the name of the receiving facility.
SEQ
6.1
Namespace Id
LEN
DT
USAGE
20
IS
RE
CONTENTS
MSH.7 Date/Time of Message (TS), mandatory.

This field contains the date/time that the sending system created the message. This element shall
be reported to a precision of seconds. This is the only date/time field in the message mandating
the time zone. All other time stamps in the message do not support a specific time zone and are
assumed to be in the same time zone as specified in this MSH-7 element.
SEQ
7.1
YYYYMMDDHHMMSS+/ZZZZ
LEN
USAGE
19
COMMENT
Time zone is used for all other time
stamps in the message
MSH.9 Message Type (MSG), mandatory.

This field contains the message type, trigger event, and the message structure ID for the message.
59 of 100
Biosystems. S.A.
version. 0.3

SEQ
9.1
9.2
9.3
Message Code
Trigger Event
Message Structure
June 19, 2013
DT
USAGE
ID
ID
ID
R
R
R
COMMENT
MSH.10 Message Control Id (ST), mandatory.

This field contains a number or other identifier that uniquely identifies the message. Each
message should be given a unique identifier by the sending system. The receiving system will echo
this ID back to the sending system in the Message Acknowledgment segment (MSA).
MSH.11 Processing Id (PT), mandatory.
This field indicates whether to process the message as defined in HL7 Application (level 7)
Processing rules.
11.1 Processing Id
SEQ
DT
USAGE
ID
COMMENT
The value of this field will always be P for Production.

MSH.12 Version Id (VID), mandatory.
The version number sent and supported is 2.5.1.
MSH.15 Accept Acknowledgement Type (ID), mandatory.
This field identifies the conditions under which accept acknowledgements are required to be
returned in response to a message. The LAW profile uses Enhanced Acknowledgement mode to
have the accept acknowledgement report errors. MSH.15 will contain the value ER.
MSH.16 Application Acknowledgement Type (ID), mandatory.
This field identifies the conditions under which application acknowledgements are required to be
returned in response to a message. Application acknowledgements are always required, so
MSH.16 will contain the value AL.
MSH.18 Character Set (ID), mandatory.
This field contains the character set for the entire message. The value of this field will always be
UNICODE UTF-8, UCS Transformation Format, 8-bit form.
MSH.21 Message Profile Identifier (EI), mandatory.
The field contains one repetition with a value representing the IHE transaction identifier.
21.1 Entity Identifier
21.2 Namespace Id
SEQ
8.6.5 NTE Segment

SEQ
LEN
DT
USAGE
DT
USAGE
ST
IS
R
R
CARD.
COMMENT
<domain>-<transaction number>
IHE
TBL#
NAME
60 of 100
Biosystems. S.A.
version. 0.3

1
3
1
4
65536
SI
FT
ANALYZER
O1
O1
June 19, 2013
[1..1]
[1..n]
Set ID
Comment
For BA 400 M.
NTE.1 Set ID (SI), optional.

This field may be used where multiple NTE segments are included in a message. Their numbering
must be described in the application message definition.
NTE.3 Comment (FT), optional.
This field contains the result comment contained in the segment.
8.6.6 OBR Segment
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
SEQ
LEN
DT
50
EI
M2
[1..1]
3
4
17
29
50
250
250
200
EI
CE
XTN
EIP
O1
M
O1
O
X
M
RE2
X
[0..1]
[1..1]
[0..2]
[0..1]
1
2
CARD.
TBL#
NAME
Placer Order Number (AWOS
ID)
Filler Order Number
Universal Service Identifier
Order Callback Phone
Parent
For BA 400 X.
Ignored by BA 400.
OBR.2 Placer Order Number (EI), mandatory.

Each ordered battery/test is assigned to a unique Order, identified by a unique AWOS ID. The
Placer Order Number is generated by the LIS actor and should be unique across all OBR segments
across all messages. For the Analyzer, if the AWOS ID is unknown, then the value should be ,
which is the NULL value.
SEQ
2.1
Entity Identifier
LEN
DT
USAGE
50
ST
R3
COMMENT
AWOS ID
OBR.4 Universal Service Identifier (CE), mandatory.

This field contains one ordered battery or test. A battery is composed of one or more tests or one
or more batteries.
SEQ
4.1
4.2
4.3
2
3
Identifier
Text
LEN
DT
USAGE
20
199
20
ST
ST
ID
R
R
R
COMMENT
Test/Battery Identifier
Name for the test/battery
Analyzer Model
If instrument is configured to have a relaxed LAW compliant it will be optional

If instrument is configured to have a relaxed IHE-LAW compliant it will be optional
61 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
OBR.29 Parent (EIP), optional (Analyzer).

This field relates a child AWOS to its parent AWOS when a parent/child relationship exists. In
reflex test decided in the instrument, this can be used to contain the reference to an AWOS ID
that was used as part of the evaluation that determined a reflex was necessary.
29.1 Entity identifier
SEQ
DT
USAGE
ST
COMMENT
AWOS ID of Parent
8.6.7 OBX Segment

SEQ
1
2
3
4
5
6
7
8
11
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
4
SI
M
M
2
ID
C(M/X)
C(M/X)2
250
CE
M
M
1
20
ST
C(M/RE)
C(M/X)2
99999 Varies
C(M/X)
C(M/X)
250
CE
C(M/X)
C(M/X)
70
ST
O
RE
5
ID
M
M
1
ID
M
M
LEN
DT
CARD.
[1..1]
[1..1]
[1..1]
[0..1]
[1..1]
[0..1]
[0..1]
[1..*]
[1..1]
14
26
TS
O1
RE2
[0..1]
16
250
XCN
[1..1]
18
427
EI
M2
[1..n]
19
26
TS
[1...1]
TBL#
0125
0085
NAME
Set ID OBX
Value Type
Observation Identifier
Observation Sub-ID
Observation Value
Units
Reference Range
Abnormal Flags
Observation Result Status
Date/Time of the
Observation
Responsible Observer
Equipment Instance
Identifier
Date/Time of the Analysis
For BA 400 X.
2
Ignored by BA 400.
OBX.1 Set ID (SI), mandatory.

If the segment occurs only one time within a message structure, then its value will be 1. If the
message structure (e.g., segment group) repeats, then the first occurrence of the segment in each
segment group will be 1.
OBX.2 Value Type (ID), optional.
This field contains the format of the observation value in OBX.
Predicate: Usage is Mandatory if OBX-5 (Observation Value) is populated. Otherwise, usage is Not
Supported.
The profile supports the following subset of values from HL7 Table 0125.
VALUE
DESCRIPTION
CE
Coded Entry
ED
Encapsulated Data
COMMENTS
Used to report exception code (reason test failed
to produce a final result yet)
Used to report graphs, plots, etc.
62 of 100
Biosystems. S.A.
version. 0.3

NM
NA
RP
Numeric
Numerical Array
Reference Pointer
SN
Structured Numeric
ST
String
June 19, 2013
Numeric result value only

n-dimensional set of plot values
Reference to a location of the observation
Used when result is above or below dynamic
range of assay. (> or <)
Interpretation string result
OBX.3 Observation Identifier (CE), mandatory.

This field contains a unique identifier for the observation.
SEQ
3.1
3.2
3.3
Identifier
Text
LEN
DT
USAGE
20
199
20
ST
ST
ID
R
R
R
COMMENT
Test Identifier
Name for the test
Analyzer Model
OBX.5 Observation Value (varies), conditional.

The observation value shall be reported using one of the allowed value types as specified in OBX2; contains the result value for the test result part identified in OBX-3 Observation Identifier.
Predicate: Usage is Mandatory when the value of OBX-11 Observation Result Status is not "D.
Otherwise usage is Not Supported.
If the result type is for an exception result, then the CE data type is used to report the exception
code as the reason the test failed to run. The following table defines how to use the CE
components to report exception.
5.1
Identifier
5.2
Text
260
ST
5.3
20
ID
SEQ
LEN
DT
USAGE
COMMENT
ST
4 digit exception/error code

Text message associated with
exception
Analyzer Model
OBX.6 Units (CE), conditional.

This field is populated with the unit of measure for the result. UCUM shall be used to define the
unit of measure.
Predicate: Usage is Mandatory if OBX-2 is valued with either with NM or SN. Otherwise usage
is Not Supported.
SEQ
6.1
6.2
6.3
Identifier
Text
LEN
DT
USAGE
20
199
20
ST
ST
ID
R
R
R
COMMENT
Unit of measure
Analyzer Model
OBX.7 Reference Range (ST), required if available (LIS), optional (Analyzer).

For numeric values, the suggested format of reference ranges is lower limit-upper limit when both
lower and upper limits are defined (e.g., 3.5 - 4.5).
63 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
OBX.8 Abnormal Flags (IS), mandatory.

The field contains analyzer defined result flags (if any) assigned to the result. The field is set to
NONE if no flags apply. Multiple flags can be assigned to a result, thus this field can repeat.
This field is intended to convey a categorical assessment of OBX-5 Observation Value, such as
"Normal", "Abnormal", Positive, Negative, etc. This field may also be used to convey an
assessment of an observation where no legitimate result may be obtained. This includes
laboratory assays that are rejected due to the presence of interfering substances, specimen
toxicity or failure of quality control. In addition, it may also be used to convey an analysis warning,
such as not enough sample volume to be confident of the result.
The required flags defined in HL7 defined BA400 cases are defined in the table below.
VALUE
001
002
003
004
005
006
007
008
009
010
011
012
013
014
015
016
017
018
019
020
021
022
023
024
025
026
027
028
029
030
031
032
033
034
DESCRIPTION
Abs > optical limit
Sample Abs < Blank Abs
Sample Abs > Blank Abs
Non Linear Kinetics
Absorbance < 0
Absorbance increase < 0
Substrate depletion
Possible prozone (it requires manual dilution and repetition)
Reactions rotor thermo warning
Possible clot in sample
Clot detected in sample
Sample arm fluidic system blocked
Completed with optical errors
Main Abs > Blank Abs limit
Main Abs < Blank Abs limit
Abs Work Reagent > Blank Abs limit
Abs Work Reagent < Blank Abs limit
Initial Blank Abs > Blank Abs limit
Initial Blank Abs < Blank Abs limit
Kinetic Blank > Kinetic Blank limit
(Abs T2 - Abs T1) * RT > Kinetic Blank limit
Incorrect calibration curve
Calculated factor out of limits
Calibration factor can't be calculated
Expired calibrator lot
Conc. not calculated
Conc. out of calibration curve (HIGH)
Conc. out of calibration curve (LOW)
Conc < 0
Conc > Linearity limit
Conc < Detection limit
Conc < Normality Min
Conc > Normality Max
Conc < Panic Min
64 of 100
Biosystems. S.A.
version. 0.3

VALUE
035
036
037
038
039
040
041
042
043
044
045
NONE
June 19, 2013
DESCRIPTION
Conc > Panic max
Some standard tests with remarks
Drift in calibrator A
Noise in measuring calibrator A
Noise in measuring calibrator B
Noise measuring calibrator B
Voltage out of limit measuring calibrator A
Drift out of limits
Voltage out of limit measuring calibrator B
Result out of range
No flags
OBX.11 Observation Result Status (ID), mandatory.

This field supports a subset of values taken from HL7 User-defined Table 0085 as described 1870
below:
VALUE
DESCRIPTION
Final results
Results cannot be
obtained
COMMENTS
Primary result value for the test run the
quantitative result
Test Exception. The reason for failure is being
reported.
OBX.16 Responsible Observer (XCN), mandatory.

This field contains the identity of the observer that causes the change of the observation result
status. Only the first component (ID number) of this field is necessary. If the value is unknown,
then a NULL value will be used for the ID number.
16.1 ID number
SEQ
LEN
DT
USAGE
20
ST
COMMENT
Locally defined identifier
OBX.18 Equipment Instance Identifier (EI), mandatory.

This field specifies the manufacturer, model, serial number/ID, and optional UID of the analyzer
that performed the test. It may also contain additional manufacturer or site specific identifiers.
OBX-18 is repeatable in v2.5.1. The first instance is mandatory and will be used to carry the
instrument model, manufacturer, and optional UDI information.
First Instance of Element: OBX-18 Equipment Instance Identifier:
18.2 Namespace
SEQ
USAGE
R
R
COMMENT
Model
Manufacturer
Second Instance of Element: OBX-18 Equipment Instance Identifier:

65 of 100
Biosystems. S.A.
version. 0.3

18.2 Namespace
SEQ
June 19, 2013
USAGE
R
R
COMMENT
Serial Number
Manufacturer
The optional third and subsequent instance of OBX-18 will be used to carry manufacturer or site
specific information to allow for the identification of the hierarchical configuration of the
equipment (cluster of modules, etc.) and site specific identification. BA 400 will not send this
information, and will ignore it in case of receiving such information from the LIS.
OBX.19 Date/Time of the Analysis (TS), required if available (LIS), optional (Analyzer).
This field contains the date and time the test processing completed. Time zone indicator is not
supported. Degree of precision component is not supported.
19.1 YYYYMMDDHHMMSS
SEQ
USAGE
COMMENT
8.6.8 ORC Segment

SEQ
LEN
1
2
4
5
9
21
2
50
20
2
26
250
27
26
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
ID
M
M
1
EI
C(M/X)
X
EI
O
RE
ID
M
X
TS
M
M
XON
O
RE
DT
TS
O1
CARD.
[1..1]
[0..1]
[0..1]
[1..1]
[1..1]
[0..1]
TBL#
0038
[0..1]
NAME
Order Control
Placer Order Number
Placer Group Number
Order Status
Date/Time of Transaction
Ordering Facility Name
Filler Expected Availability
Date/Time
For BA 400 X.
ORC.1 Order Control (ID), mandatory.

This field may be considered the "trigger event" identifier for orders. The IHE Laboratory Technical
Framework allows only the following subset for the LAW profile:
VALUE
NW
OK
UA
CA
DESCRIPTION
New Order
Notification or request accepted
Unable to accept order/service
Cancel order/service request
CR
Cancelled as requested
UC
Unable to cancel
DC
PR
Discontinue Request
Prior Results
COMMENTS
Event acknowledgement in ORL message
Event request in OML.
responding to OML (CA)
responding to OML (CA)
Used to indicate a negative query response
66 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
ORC.2 Placer Order Number (EI), not supported (LIS), conditional (Analyzer).
The field is used by the Analyzer to uniquely identify an AWOS when used as part of an ORLÔ34
response to the LIS.
Predicate: Usage is Mandatory if MSH-9.1 (Message type) is populated with ORL and MSH-9.2
(Event type) is populated with O34. Otherwise, usage is Not Supported because the placer order
number is only carried by field OBR-2 Placer Order Number.
ORC.4 Placer Group Number (EI), required if available (LIS), optional (Analyzer)
The Placer Group Number represents an identification of a set of closely related batteries and/or
tests for one subject ordered together and for the same diagnostic purpose. This field contains
the Work Order identifier that groups AWOS ordered together by the LIS and sent to one or more
Analyzers. The Work Order can encompass more than one sample from the same patient. Only
the LIS establishes a Work Order identifier, therefore only the first identifier of the EIP data type is
supported.
In cases where AWOS are not grouped under a common Work Order, this field is empty.
ORC.5 Order Status (ID), mandatory (Analyzer)
The allowed values for this field within IHE Laboratory Technical Framework are a subset of 1935
HL7 table 0038 - Order Status as shown below:
VALUE
CA
CM
IP
DESCRIPTION
Order was cancelled
Order is completed
In process, unspecified
COMMENTS
ORC.9 Date/Time of Transaction (TS), mandatory.

This field contains the date and time of the event that initiated the current transaction as
reflected in ORC-1 Order Control Code. This field is not equivalent to MSH-7 Date and Time of
Message that reflects the date/time of the creation of the physical message.
In OML messages "Status changed", this field contains the date/time of the last status change of
the unit of work (ORC-5).
SEQ
9.1
YYYYMMDD
USAGE
COMMENT
ORC.21 Ordering Facility Name (XON), required if available (LIS), optional (Analyzer).
This field contains the name of the facility placing the order.
SEQ
21.1
Organization Name
DT
USAGE
ST
COMMENT
67 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
8.6.9 PID Segment

SEQ
LEN
3
5
6
7
8
30
250
250
26
1
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
CE
M
M
XPN
O
RE
1
XPN
O
RE2
TS
O
RE
IS
O
RE
DT
CARD.
[1..1]
[0..1]
[0..1]
[0..1]
[0..1]
TBL#
0001
NAME
Patient Identifier List
Patient Name
Mothers Maiden Name
Date/Time of Birth
Administrative Sex
For BA 400 X.
2
Ignored by BA 400.
PID.3 Patient Identifier List (CX), mandatory.

This element supports the list of identifiers (one or more) used by the healthcare facility to
uniquely identify a patient (e.g., medical record number, billing number, birth registry, national
unique individual identifier, etc.). Additional characteristics of the identifier are not necessary
because only the identifier value is required for the Analyzer to identify the patient. The Analyzer
should not receive multiple identifiers for the same patient.
SEQ
3.1
Entity Identifier
DT
USAGE
ST
COMMENT
Locally defined
PID.5 Patient Name (XPN), required if available (LIS), optional (Analyzer).

This element contains the primary or legal name of the patient.
SEQ
5.1
5.1.1
5.2
5.7
Family Name
Surname (a.k.a. last name)
Given name (a.k.a. first name)
Name type code
LEN
DT
USAGE
30
30
1
FN
ST
ST
ID
RE
RE
RE
R
COMMENT
Always L
PID.7 Date/Time of Birth (TS), required if available (LIS), optional (Analyzer).

This field contains the patients date and time of birth. Only the birth date is supported. Time of
birth and time zone indicator are not supported. Degree of precision component is not supported.
SEQ
7.1
YYYYMMDD
USAGE
COMMENT
PID.8 Administrative Sex (IS), required if available (LIS), optional (Analyzer).

This field contains the patients sex. Can be blank or contain only a value from HL7 User-defined
Table 0001.
VALUE
F
M
U
DESCRIPTION
COMMENTS
Female
Male
Unknown
68 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
8.6.10 PV1 Segment

SEQ
LEN
DT
IS
80
PL
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
M
M
M1
O
CARD.
TBL#
[1..1]
0004
[0..1]
NAME
Patient Class
Assigned Patient Location
When PV1 is in the PRIOR RESULT segment group, the only mandatory field is PV1.2 and its value should be U.
PV1.2 Patient Class (IS), mandatory.

This field is used by systems to categorize patients by site. The field must contain a value taken
from HL7 User-defined Table 0004 Patient Class.
VALUE
B
C
E
I
N
O
P
R
U
DESCRIPTION
COMMENTS
Obstetrics
Commercial Account
Emergency
Inpatient
Not Applicable
Outpatient
Preadmit
Recurring Patient
Unknown
PV1.3 Assigned Patient Location (PL), required if available (LIS), optional (Analyzer).
This field contains the patients initial assigned location or the location to which the patient is
being moved. Only a single patient location element is supported.
SEQ
3.2
Room
LEN
DT
USAGE
20
IS
RE
COMMENT
8.6.11 SAC Segment

SEQ
LEN
DT
30
EI
29
20
SN
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
C
(M/X)1
C (M/X)1
O2
RE3
CARD.
TBL#
NAME
[0..1]
Container Identifier
[0..1]
Dilution Factor
For BA 400 M.
For BA 400 X.
3
Ignored by BA 400.
2
SAC.3 Container Identifier (EI), conditional.

This field identifies the container. This field is the container's unique identifier assigned by the
corresponding equipment. A container may contain the primary (original) specimen or an aliquot
69 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
(secondary sample) of that specimen. For primary sample this field contains Primary Container ID;
for bar-coded aliquot samples this field contains Aliquot Container ID; for non-bar-coded aliquot
samples (e.g., microtiter plate) this field is empty.
It is expected that the Container ID here is normally encoded as the ID (barcode, RFID) on the
sample container.
Predicate: Either SAC-3 or SAC-4 or both must be populated.
Entity Identifier
SEQ
3.1
LEN
DT
USAGE
30
ST
COMMENT
8.6.12 SPM Segment

USAGE
USAGE
ANALYZER
ANALYZER
MGR.
SI
M
M
EIP
O
RE
EIP
C
C (M/X)
CWE
O
M
CWE
M
M
NM
C
C (M/X)
SEQ
LEN
DT
CARD.
1
2
3
4
11
13
4
30
80
250
250
6
17
26
DR
C (O/X)
C (RE/X)
[0..1]
18
26
TS
C (O/X)
C (RE/X)
[0..1]
[1..1]
[0..1]
[0..*]
[1..1]
[0..1]
[0..1]
TBL#
0487
0369
NAME
Set ID SPM
Specimen Id
Specimen Parent Ids
Specimen Type
Specimen Role
Grouped Specimen Count
Specimen Collection
Date/Time
Specimen Received Date/Time
SPM.1 Set ID (SI), mandatory.

This field contains the sequence number. This field is used to identify segment instances in
message structures (e.g., segment group) where the segment repeats within that structure. For
the first occurrence of the segment, the sequence number shall be one, for the second
occurrence, the sequence number shall be two, etc.
If the segment occurs only one time within a message structure (e.g., segment group), then its
value will be 1. If the message structure (e.g., segment group) repeats, then the first occurrence
of the segment in each segment group will be 1.
SPM.2 Specimen Id (EIP), required if available (LIS), optional (Analyzer).
This field contains the specimen identifier. It may be the enterprise-wide unique specimen
identifier.
SEQ
2.1
2.1.1
COMPONENT/SUB-COMPONENT
Placer Assigned Identifier
Entity Identifier
LEN
30
DT
EI
ST
USAGE
R
R
COMMENT
70 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
SPM.3 Specimen Parent ID (EIP), conditional.

This field contains the identifiers for the specimen or specimens that contributed to the specimen
that is described by the segment instance. For pooled patient samples indicated by SPM-11 equal
to L, this field will contain the specimen identifiers of the specimens that were pooled.
Predicate: Usage is Mandatory if SPM-11 Specimen Role is L. Otherwise usage is Not Supported.
SEQ
3.1
3.1.1
Placer Assigned Identifier
Entity Identifier
LEN
20
DT
EI
ST
USAGE
R
R
COMMENT
SPM.4 Specimen Type (CWE), mandatory (LIS), optional (Analyzer).

This field describes the precise nature of the entity that will be the source material for the
observation. The values defined in HL7 Table 0487 Specimen Type will be used. The Analyzer
may define extensions to the table, and the Analyzer may identify a subset of specimen types that
are supported.
This field is required if the Specimen Role (SPM-11) is Patient. It will be NULL if the Specimen Role
(SPM-11) is QC.
Only the first component is used.
SEQ
DT
USAGE
4.1
Identifier
ST
COMMENT
Code from HL7 Table 0487
Specimen Type.
SPM.11 Specimen Role (CWE), mandatory.

This identifies the role of the specimen to be a Patient, Pooled Patient, or QC specimen. Only the
first component (i.e. Identifier) is supported.
VALUE
P
Q
L
DESCRIPTION
COMMENTS
Patient
Control specimen
Pooled patient specimens
Specimens from multiple patients,

number of pooled specimens is provided
in SPM-13
SPM.13 Grouped Specimen Count (NM), conditional.

This field identifies the number patient specimens that were pooled.
Predicate: Usage is Mandatory if SPM-11 Specimen Role is L. Otherwise usage is Not Supported.
SPM.17 Specimen Collection Date/Time (DR), conditional.
The date and time when the specimen was acquired from the source. Only the start date/time
component is supported (i.e. first component).
LIS Predicate: Usage is Required if Available when SPM-11 is P. Otherwise usage is Not
Supported.
Analyzer Predicate: Usage is Optional when SPM-11 is P. Otherwise usage is Not Supported.
71 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
This element shall be reported to a precision of seconds. Indication of the time zone is not
supported. The degree of precision component is not supported.
SEQ
17.1
YYYYMMDDHHMMSS
USAGE
R
COMMENT
SPM.18 Specimen Collection Date/Time (DR), conditional.

The specimen received date/time is the time that the specimen is received at the diagnostic
service. The actual time that is recorded is based on how specimen receipt is managed and may
correspond to the time the sample is logged in. This is fundamentally different from SPM-17
Specimen Collection Date/Time. Only the start date/time component is supported (i.e. first
component).
LIS Predicate: Usage is Required if Available when SPM-11 is P. Otherwise usage is Not
Supported.
Analyzer Predicate: Usage is Optional when SPM-11 is P. Otherwise usage is Not Supported.
This element shall be reported to a precision of seconds. Indication of the time zone is not
supported. The degree of precision component is not supported
SEQ
18.1
YYYYMMDDHHMMSS
8.6.13 TCD Segment

USAGE
SEQ LEN DT ANALYZER
MGR.
1
250 CE
M1
2
20
SN
RE1
3
20
SN
RE1
4
20
SN
RE1
5
20
SN
RE1
6
1
ID
RE
7
1
ID
RE
8
250 CE
RE1
1
CARD.
[1..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
USAGE
R
TBL#
0136
0136
0389
COMMENT
NAME
Universal Service Identifier
Auto-Dilution Factor
Rerun Dilution Factor
Pre-Dilution Factor
Endogenous Content of Pre-Dilution Diluent
Automatic Repeat Allowed
Reflex Allowed
Analyte Repeat Status
Ignored by BA 400.
TCD.6 Automatic Repeat Allowed (ID), required if available.

This field identifies whether or not automatic repeats are to be initiated for this particular
specimen for this particular test code. Refer to HL7 Table 0136 -Yes/no indicator for valid values.
VALUE
Y
N
DESCRIPTION
COMMENTS
Yes
No
72 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
TCD.7 Reflex Allowed (ID), required if available.

Definition: This field identifies whether or not automatic or manual reflex testing is to be initiated
for this particular specimen. Refer to HL7 Table 0136 -Yes/no indicator for valid values.
VALUE
Y
N
DESCRIPTION
COMMENTS
Yes
No
8.6.14 TQ1 Segment

USAGE
SEQ LEN DT ANALYZER
MGR.
9
250 CWE
M
CARD.
TBL#
[1..1]
0485
NAME
Priority
TQ1.9 Priority (CWE), mandatory.

This field identifies the priority of the order. Only the first component (i.e. Identifier) is supported
and it can contain only values taken from HL7 User-defined Table 0485 (see below).
SEQ
DT
USAGE
9.1
Identifier
ST
VALUE
R
S
DESCRIPTION
COMMENT
Code from HL7 User-defined
Table 0485
COMMENTS
Routine
Stat
73 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
9 LIS2-A2 Scenarios and Messages

9.1 AWOS query for all available orders.
Analyzer Manager
Analyzer
Timer
Query all orders
Orders / No orders
Accept/Reject orders
9.1.1 Analyzer sends query message to the LIS

The message has the following structure
LEVEL 0
LEVEL 1
LEVEL 2
LEVEL 3
LEVEL 4
LEVEL 5
H
Q
L
The Header record follows the structure described in Section 10.1 with the following details:
H-5. Analyzer ID (BAx00).

H-10. LIS ID (configurable at the Analyzer).
The Request record follows the structure described in Section 10.2 with the following details:
Q-3. Contains the text ALL, only once.
The Termination record follows the structure described in Section 10.3 with the following details:
L-3. N, normal termination.
H|\^&|64F2746D24014F21AD7139756F64CAD8||BA400|||||Modulab||P|LIS2A|201301
29102030
Q|1|ALL||O
L|1|N
9.1.2 LIS answers without orders

The message has the following structure
74 of 100
Biosystems. S.A.
version. 0.3

LEVEL 0
LEVEL 1
June 19, 2013
LEVEL 2
LEVEL 3
LEVEL 4
LEVEL 5
H
L
H-5. LIS ID.

H-10. Analyzer ID.
L-3. I, no information available from last query.
H|\^&|69F2746D24014F21AD7139756F64CAD8||Modulab|||||BA400||P|LIS2A|201301
29102030
L|1|I
9.1.3 LIS answers with new orders or cancellation of orders

The message has the following structure. There can be one or more patients, one or more orders
per patient and optionally, an order can contain one or more previous results.
LEVEL 0
LEVEL 1
LEVEL 2
LEVEL 3
LEVEL 4
LEVEL 5
H
{
P
{
O
[{
R
[
C
]
}]
}
}
L
H-5. LIS ID.

The Patient record follows the structure described in Section 10.4.

The Order record follows the structure described in Section 10.5 with the following details:
O-3. Specimen ID that is the subject of the test to perform.

75 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
In case of actions (add/cancel orders) to perform on this specimen

- O-5.4. Test or battery to perform, using the Analyzer coding system.
- O-12. This field identifies the action to perform. Several options may be possible:
To program a new order on a patient sample, the value shall be A.
To program a new order on a QC sample, the value shall be A and Q
(the field is repeated).
To cancel an existing order on a patient sample, the value shall be C.
To cancel an existing order on a QC sample, the value shall be C and Q
(the field is repeated).
- O-26. This field identifies the type of report. The values shall be O and Q (the
field is repeated).
In case no action has to be performed on this specimen
- O-26. This field identifies the type of report. The values shall be Y and Q (the
field is repeated).
The Result record follows the structure described in Section 10.6 with the following details:
R-9. This field shall contain the value N and also:

o F If the result sent to the analyzer is valid.
o X If the result sent to the analyzer was invalid.
The Comment record follows the structure defined in Section 10.7 with the following details:
C-2 can only be 1, since only one record is allowed.

C-3 shall be L, because the sender is the LIS.
C-4.1 is the error code.
C-4.2 is the error description.
C-5 shall be I because the provided information is an instrument code.
L-3. F, last request for information processed.
76 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
29102030
P|1||PID01||Campeny^Ricard||19850819|M
O|1|SPM01||^^^Test
1|R|20130129101530|20130129092030||||A||||HBLUD|||||^56|||||O\Q
O|2|SPM02||^^^|||20130129092530||||||||HBLUD|||||^57|||||Y\Q
L|1|F
9.2 AWOS broadcasted by the LIS
Analyzer Manager
Analyzer
Orders

per patient and optionally, an order can contain one or more previous results. Each result can
contain a Comment record to carry error information if any.
LEVEL 0
LEVEL 1
LEVEL 2
LEVEL 3
LEVEL 4
LEVEL 5
H
{
P
{
O
[{
R
[
C
]
}]
}
}
L
H-5. LIS ID.

77 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013


O-5.4. Test or battery to perform, using the Analyzer coding system.
O-12. This field identifies the action to perform. Several options may be possible:
- To program a new order on a patient sample, the value shall be A.
- To program a new order on a QC sample, the value shall be A and Q (the field is
repeated).
- To cancel an existing order on a patient sample, the value shall be C.
- To cancel an existing order on a QC sample, the value shall be C and Q (the field
is repeated).
O-26. This field identifies the type of report. The values shall be only O.
R-9. This field shall contain the value N and also:

o F If the result sent to the analyzer is valid.
o X If the result sent to the analyzer was invalid.
The Comment record follows the structure defined in Section 10.7 with the following details:
C-2 can only be 1, since only one record is allowed.

C-3 shall be L, because the sender is the LIS.
C-4.1 is the error code.
C-4.2 is the error description.
C-5 shall be I because the provided information is an instrument code.
L-3. N, last request for information processed.
29102030
O|1|SPM01||^^^Test
1|R|20130129101530|20130129092030||||A||||HBLUD|||||^56|||||O
O|2|SPM01||^^^Test
2|R|20130129101530|20130129092030||||A||||HBLUD|||||^56|||||O
O|3|SPM02||^^^Test
3|R|20130129101730|20130129092031||||A||||HBLUD|||||^57|||||O
L|1|N
9.3 AWOS queried by the Analyzer at specimen arrival

78 of 100
Biosystems. S.A.
version. 0.3
Analyzer Manager
June 19, 2013
Analyzer
Specimen Identification
Query by Specimen ID
Orders / No orders
9.3.1 Analyzer sends query message to the LIS

The message has the following structure.
LEVEL 0
LEVEL 1
LEVEL 2
LEVEL 3
LEVEL 4
LEVEL 5
H
Q
L

H-10. LIS ID (configurable at the Analyzer).
The Request record follows the structure described in Section 10.2 with the following details:
Q-3. Contains the Specimen ID, repeated for as many specimens are requested.
L-3. N, normal termination.
29102030
Q|1|SPM01\SPM02||O
L|1|N
9.3.2 LIS answers without orders

per patient and optionally, an order can contain one or more previous results.
LEVEL 0
LEVEL 1
LEVEL 2
LEVEL 3
LEVEL 4
LEVEL 5
H
{
P
79 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
{
O
}
}
L
H-5. LIS ID.

The Patient record follows the structure described in Section 10.4. All the fields except the second
can be empty
O-3. Specimen ID that is the subject of the original query.

O-26. This field identifies the type of report. The values shall be Y and Q (the field is
repeated).
L-3. F, last request for information processed.

This message is exactly the same as the one described in Section 9.1.3.
9.4 AWOS acceptance/rejection by the Analyzer
Analyzer Manager
Analyzer
Orders
9.4.1 Analyzer accepts the actions proposed by the LIS

The message the following structure. The analyzer just reports to the LIS a message with the
Header and Termination records.
80 of 100
Biosystems. S.A.
version. 0.3

LEVEL 0
LEVEL 1
LEVEL 2
June 19, 2013
LEVEL 3
LEVEL 4
LEVEL 5
H
L
29102030
L|1|N
9.4.2 Analyzer rejects the actions proposed by the LIS

The message has the following structure. The Analyzer reports to the LIS the outcome of the
programming or cancellation of the orders. This message always follows to one of the messages
described in sections 9.1.3 or 9.3.3.
LEVEL 0
LEVEL 1
LEVEL 2
LEVEL 3
LEVEL 4
LEVEL 5
H
{
P
{
O
}
}
L

H-10. LIS ID.


O-12 / O-26. These fields identify the action to perform and the report type. Several
options may be possible:
- If the action requested was to program a new order on a patient sample and
The action cannot be performed,
O-12 has the value A.
O-26 has the value X.
- If the action requested was to program a new order on a QC sample and
The action was successful at the Analyzer,
O-12 has the value A and Q (the field is repeated).
81 of 100
Biosystems. S.A.
version. 0.3

-
June 19, 2013
If the action requested was to program a new order on a Pooled Patient sample
and the action was successful at the Analyzer,
O-12 has the value A and D (the field is repeated).
If the action requested was to cancel an existing order on a patient sample and
O-12 has the value C.
O-26 has the value I.
If the action requested was to cancel an existing order on a QC sample and
O-12 has the value C and Q (field is repeated).
If the action requested was to cancel an existing order on a Pooled Patient sample
and the action cannot be performed,
O-12 has the value C and D (field is repeated).
29102030
O|1|SPM01||^^^Test
1|R|20130129101530|20130129092030||||C||||HBLUD|||||^56|||||O
L|1|N
9.5 Analyzer cancel orders already accepted
Analyzer Manager
Analyzer
Orders
Cancel orders
9.5.1 Analyzer cancel orders previously accepted

The message has the following structure. The Analyzer reports to the LIS the cancellation of the
orders that previously have been accepted.
82 of 100
Biosystems. S.A.
version. 0.3

LEVEL 0
LEVEL 1
LEVEL 2
June 19, 2013
LEVEL 3
LEVEL 4
LEVEL 5
H
P
{
O
}
L

H-10. LIS ID.


O-12. In this case it must be empty
O-26. These field identify the action to perform and the report type. In this case always
has the value X to cancel the order.
The Termination record follows the structure described in Section 10.3 with the following
details:
29102030
O|1|SPM01||^^^Test 1|R||||||||||||||||||||X
L|1|N
9.6 Upload of results
Analyzer Manager
Analyzer
Upload result
83 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
9.6.1 Analyzer upload results for the first time

The message has the following structure. The Analyzer reports to the LIS the outcome of the runs
it has performed on some samples.
LEVEL 0
LEVEL 1
LEVEL 2
LEVEL 3
LEVEL 4
LEVEL 5
H
{
P
{
O
{[
R
{[
C
]}
]}
}
}
L

H-10. LIS ID.


O-5.4. Test or battery ordered, using the Analyzer coding system.
O-12. Shall be empty if this is a patient sample, or has the value Q if this is a QC sample.
O-26. The allowed value is F.
R-3.4 . The test code of the analyte.

R-9. This field may contains one of the following:
o F If the run was successful and there is a valid result.
o X If the run was unsuccessful and there were some error.
The Comment record follows the structure described in Section 10.7 with the following details:
C-3. Always I.
If the comment is a general comment by the operator,
o C-4.1. Contains the value COMMENT.
o C-4.2. Contains the comment text.
84 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
o C-5. The value is G.

If the comment is the report of an error,
o C-4.1. Contains the Error code.
o C-4.2. Contains a description of the error.
o C-5. The value is I.
29102030
O|1|SPM01||^^^Test
1|R|20130129101530|20130129092030||||||||HBLUD|||||||20130129092031|||F
R|1|^^^Test 1|50|degree||||F||||20130129092031|BA400^SN-BA400-01
L|1|N
9.7 Rerun
The structure of this message is the same as the section above. The result values reported are the
latest ones. This correction in the results is reported in the following field:
R-9. The value shall be,

o F and C if the analyzer successfully performed the run.
X and C if the run was not successful for that analyte.
29102030
O|1|SPM01||^^^Test
1|R|20130129101530|20130129092030||||||||HBLUD|||||||20130129092031|||F
R|1|^^^Test 1|50|degree||||F\C||||20130129092031|BA400^SN-BA400-01
L|1|N
9.8 Reflex
If there is a reflex test it is transmitted as a new result.
9.9 Retransmission
The message in case of retransmission is the same as the original one except for the following
fields:
H.3. The Message Control ID can be different than the original message.
H.14. The date and time of the message is updated.
85 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
10 LIS2-A2 Segments
10.1 Header record
SEQ
LEN
DT
1
2
3
5
10
12
13
14
1
5
50
227
227
1
10
14
ST
ST
ST
ST
ST
ST
ST
DT
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
R
CARD.
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
[1..1]
NAME
Record Type ID
Delimiter Definition
Message Control ID
Sender ID
Receiver ID
Processing ID
Version Number
Date and Time of Message
10.1.1 Record Type ID

It must be valued to H.
10.1.2 Delimiter Definition
The standard set of delimiters will be used: |\^&|.
10.1.3 Message Control ID
Unique identifier of the message.
10.1.4 Sender ID
Sender name, it is a site-configurable parameter at the analyzer.
10.1.5 Receiver ID
Receiver name, it is a site-configurable parameter at the analyzer.
10.1.6 Processing ID
The value of this field will be always P for Production.
10.1.7 Version Number
The version number sent and supported is LIS2A.
10.1.8 Date and Time of the Message
The date and time of the message if the LIS2-A2 date/time format: YYYYMMDDHHmmSS where,
YYYY : year, four digits.

MM: month, two digits, (01 = January).
DD: day of the month, two digits (01-31).
HH: hour of the day (24-hour format).
mm: minutes of the hour (00-59).
SS: seconds of the minute (00-59).
Milliseconds or timezones are not supported.

86 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
10.2 Request record

SEQ
LEN
DT
1
2
3
5
1
1
100
1
ST
ST
ST
ST
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
R
X
R
X
R
X
R
X
CARD.
[1..1]
[1..1]
[1..*]
[1..1]
NAME
Record Type ID
Sequence Number
Starting Range ID Number
Request Information Status Code

The value of this field is set to Q.
10.2.2 Sequence Number
This field represents the sequence number of all the requests records within this message.
10.2.3 Starting Range ID Number
This field contains the Specimen ID used for request. This field is repeatable.
10.2.4 Request Information Status Code
The value of this field is set to O since the analyzer only requests for orders.
10.3 Termination record

SEQ
LEN
DT
1
2
3
1
1
1
ST
ST
ST
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
R
R
R
R
R
R
CARD.
[1..1]
[1..1]
[1..1]
NAME
Record Type ID
Sequence Number
Terminator code

The value of this field is set to L.
This field represents the sequence number of all the termination records within this message.
10.3.3 Termination Code
This field provides an explanation of the end of the session.
Allowed values:
N, normal termination.
I, no information available from last query.
F, last request for information processed.
87 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
10.4 Patient record

SEQ
LEN
DT
1
2
4
6.1
6.2
8
9
26
1
1
30
30
30
8
1
20
ST
ST
ST
ST
ST
DT
ST
ST
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
R
R
R
R
O
O
O
O
O
O
O
O
O
O
O
O
CARD.
[1..1]
[1..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
NAME
Record Type ID
Sequence Number
Laboratory-Assigned Patient ID
Patient Last Name
Patient First Name
Patient Birth date
Patient Sex
Location

The value of this field is set to P.
This field represents the sequence number of all the patient records within this message.
10.4.3 Laboratory-Assigned Patient ID
Patient identifier assigned by the laboratory. First time this value is received in BAx00, if
additional demographic data is also received, it is added as new Patient. Once the patient has
been added, each time the same identifier is received, its demographic data is updated with the
last values received. Patient Identifiers should not be re-used.
10.4.4 Patient Name
The patient name is represented in two components:
First component, last name.

Second component, first name.
10.4.5 Birth date

Patients birth date in the standard date format YYYYMMDD:
YYYY: year, four digits.

MM: month, two digits, (01 = January).
DD: day of the month, two digits (01-31).
10.4.6 Patient Sex

The following values are supported:
M, male.
F, female.
U, unknown.
10.4.7 Location
This field contains the description or identification of the clinic location, ward or bed of the
patient.
88 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
10.5 Order record

SEQ
LEN
DT
1
2
3
5.4
5.5
6
7
8
12
16
17
19.1
1
1
30
50
50
1
14
14
1
50
50
80
8
ST
ST
ST
ST
ST
ST
DT
DT
ST
ST
ST
ST
19.2
19.3
21.1
21.2
21.3
21.4
22
23
26
80
80
80
1
1
30
14
1
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
R
R
R
R
R
R
O
O
O
O
O
R
X
O
X
O
O
O
O
O
X
O
O
X
CARD.
NAME
[1..1]
[1..1]
[1..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..1]
[0..*]
[0..1]
[0..1]
[0..1]
Record Type ID
Sequence Number
Specimen ID
Universal Test ID
Order Group ID
Priority
Ordered Date and Time
Specimen Collection Date and Time
Action Code
Specimen Descriptor
Ordering Physician
User Field #1: Quality Control ID
DT
[0..1]
User Field #1: QC Expiration Date
ST
[0..1]
User Field #1: QC Lot Number
ST
[0..1]
Lab. Field #1: Ordering Facility
ST
[0..1]
Lab. Field #1: Specimen dilution factor
ST
ST
ST
DT
ST
X
X
O
O
R
O
O
O
X
R
[0..1]
[0..1]
[0..*]
[0..1]
[1..*]
Automatic Rerun Allowed

Automatic Reflex Allowed
Parent Specimen ID
Date/Time Results Reported
Report Types

The value of this field is set to O.
This field represents the sequence number of all the order records within this message.
10.5.3 Specimen ID
This field contains the Specimen ID used for the order.
10.5.4 Universal Test ID
This field identifies the test/profile in the message.
The fourth component is the test code defined at the analyzer.

The fifth component is an identifier to group all the orders that are closely related. For
instance when doing a Creatinine Clearance test or a Glucose test, where more than one
sample is involved.
89 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
10.5.5 Order Group ID

This field represents the identifier of the Work Order from the LIS. This is only provided when
several tests are related with the same Work Order.
10.5.6 Priority
Test priority. Allowed values:
S, for STAT.
R, for routine samples.
10.5.7 Ordered Date and Time

This field represents the date and time when the test was ordered.
10.5.8 Specimen Collection Date and Time
This field records the date and time the specimen was collected.
10.5.9 Action Code
This field indicates the action to be taken with respect the specimens that are referenced in this
order:
C, cancel request for the battery or tests referenced.

A, add the requested tests or batteries to the specimen referenced.
Q treat specimen as a QC test specimen.
D treat specimen as a Pooled Patient specimen4.
X, specimen or test already in process.
P, pending specimen.
10.5.10
Specimen Descriptor
The first component of this field contains the specimen type. The set of sample codes is
configurable at the BA 400.
10.5.11
Ordering Physician
This field contains the identifier of the ordering physician.
10.5.12
Date/Time Results Reported
This field is used to indicate the date and time of the reported results.
10.5.13
User Field #1, QC Identifier
This field contains the identifier of the control or substance used for Quality Controls. This field is
only populated when the result to upload is a QC.
10.5.14
User Field #1, QC Expiration date
This field contains the expiration date of the control or substance used for Quality Controls. This
field is only populated when the result to upload is a QC.
O-22 field become mandatory if the specimen is pooled patient
90 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
10.5.15
User Field #1, QC Lot Number
This field contains the lot number of the control or substance used for Quality Controls. This field
is only populated when the result to upload is a QC.
10.5.16
Lab. Field #1, Ordering Facility
This custom field is used to notify about the ordering facility.
10.5.17
Lab. Field #1, Specimen Dilution Factor
This custom field is used to notify about the dilution factor of the sample used at the analyzer.
10.5.18
Lab. Field #1, Automatic Rerun Allowed
Y to allow automatic rerun.
N to deny automatic rerun.
10.5.19
Lab. Field #1, Automatic Reflex Allowed
Y to allow automatic reflex.
N to deny automatic reflex.
10.5.20
Lab. Field #1, Parent Specimen ID
This field contains the parent specimen ID used for the specimen under test. This field is
repeatable. If the sample is no pooled, this field is empty.
10.5.21
Date /Time Results Reported
If the message contains results, this date is the same as the execution date of the results.
10.5.22
Report Types
The following codes may be used. This field is repeatable, so more than one option may be
supported:
O, request for tests.

C, correction of previously transmitted results.
F, final results.
X, order cannot be done, cancelled.
Q, response to query.
Y, no order on record for this test
I, in instrument pending
10.6 Result record

SEQ
LEN
DT
1
2
3.4
4
1
1
50
99999
ST
ST
ST
ST
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
R
R
R
R
R
R
O
O
CARD.
[1..1]
[1..1]
[0..1]
[0..1]
NAME
Record Type ID
Sequence Number
Universal Test ID
Data or Measurement Value
91 of 100
Biosystems. S.A.
version. 0.3

SEQ
LEN
DT
5
6
7
9
11
13
14.1
14.2
50
70
5
1
16
14
50
50
ST
ST
ST
ST
ST
DT
ST
ST
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
O
O
O
O
O
O
R
R
O
X
O
O
R
X
R
X
June 19, 2013
CARD.
[0..1]
[0..1]
[0..*]
[1..*]
[0..1]
[0..1]
[0..1]
[0..1]
NAME
Units
Reference Ranges
Result Abnormal Flags
Result Status
Operator ID
Date/Time test completed
Instrument ID (Model)
Instrument ID (Serial Number)

The value of this field is set to R.
This field represents the sequence number of all the result records under the referenced order.
10.6.3 Universal Test ID
This field identifies the test in the message. The only component used is the fourth one:
Manufacturer or local code.
10.6.4 Data or Measurement Value
This field contains the measurement of the test.
10.6.5 Units
Units of measure reported by the analyzer.
10.6.6 Reference Ranges
This field contains a representation of the reference ranges of the test in the following format:
lower limit to upper limit.
Examples:
0.7 to 1.0
-1.0 to 1.0
10.6.7 Result Abnormal Flags

This field indicates the normalcy status of the result. The list of flags supported by the analyzer is
described at Section 11.2. This field is repeatable.
10.6.8 Result Status
The following codes are used:
C, correction of previously transmitted results.

F, final results.
X, order cannot be done.
N, this result record contains necessary information to run a new order. This value is the
one used when the LIS transmits orders with previous results to the analyzer.
92 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
10.6.9 Operator ID
This field contains the ID of the operator that performed the test.
10.6.10
Date/Time test completed
This value contains the date and time of the completed test.
10.6.11
Instrument ID
This field identifies the instrument using the model as the first component and the serial number
as the second component.
10.7 Comment record

SEQ
LEN
DT
1
2
3
4.1
4.2
5
1
1
1
50
500
1
ST
ST
ST
ST
ST
ST
USAGE
USAGE
ANALYZER
ANALYZER
MGR.
R
R
R
R
R
R
R
R
O
O
R
R
CARD.
[1..1]
[1..1]
[1..1]
[1..1]
[0..1]
[1..1]
NAME
Record Type ID
Sequence Number
Comment Source
Comment Text (Code)
Comment Text (Description)
Comment Type

The value of this field is set to C.
This field represents the sequence number of all the comments records under the reference
record.
10.7.3 Comment Source
This field identifies the source of the comment.
I (clinical instrument system).

L (laboratory information system).
10.7.4 Comment Text

This field contains the text of the comment. The field is structured in two components. The first
one contains the comment code and the second the description.
10.7.5 Comment Type
Depending on the information contained in the comment the following types can be used:
G, generic/free result comment.

I, instrument flag(s) comment.
93 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
11 Appendix A. Code Tables

11.1 Error codes (To edit by Biosystems)
ID
ERROR 1
ERROR2
ERROR3
DESCRIPTION
11.2 Flag codes [v2.1]

ID
001
002
003
004
005
006
007
008
009
010
011
012
027
028
029
030
031
032
033
034
035
036
037
038
039
040
041
042
043
044
045
DESCRIPTION
Abs > optical limit
Sample Abs < Blank Abs
Sample Abs > Blank Abs
Non Linear Kinetics
Absorbance < 0
Absorbance increase < 0
Substrate depletion
Possible prozone (it requires manual dilution and repetition)
Reactions rotor thermo warning
Possible clot in sample
Clot detected in sample
Sample arm fluidic system blocked
Conc. out of calibration curve (HIGH)
Conc. out of calibration curve (LOW)
Conc < 0
Conc > Linearity limit
Conc < Detection limit
Conc < Normality Min
Conc > Normality Max
Conc < Panic Min
Conc > Panic max
Calculated Test with some partial tests with remarks
Noise in measuring calibrator A
Noise in measuring calibrator B
Noise measuring calibrator B
Voltage out of limit measuring calibrator A
Drift out of limits
Voltage out of limit measuring calibrator B
Result out of range
94 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
12 Appendix B. Example Traces

The following appendix collects traces from the instrument to a LIS in all the protocols described
in this document.
The direction of the data is represented by the words Send and Recv from the BA400 point of
view.
The non-printable characters are represented enclosed in less-than, greater-than signs. (e.g.
<ENQ> is the character with the ASCII code number 6)
95 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
12.1 LIS2-A2 Query

Send: <ENQ>
Recv: <ACK>
Send: <STX>H|\^&|21ec6ea0-5c78-4818-96d259dbdf84b1e2||BA400|||||Modulab||P|LIS2A|20130419064309<CR>
Q|1|0010079||O<CR>
L|1|N<CR><ETX>84<CR><LF>
Recv: <ACK>
Send: <EOT>
12.2 LIS2-A2 Positive Response Patient (Orders send from LIS)

Recv: <ENQ>
Send: <ACK>
Recv: <STX>H|\^&|69F2746D24014F21AD7139756F64CAD8||Modulab|||||BA400||
P|LIS2A|20130129102030<CR>
P|1||PID01||Campeny^Ricard||19850819|M<CR>
O|1|0010079||^^ÂSO|R|20130129101530|20130129092030||||A||||SER|||||^56||
|||O<CR>
L|1|N<CR><ETX>OB<CR><LF>
Send: <ACK>
Recv: <EOT>
12.3 LIS2-A2 Positive Response External QC (Orders send from LIS)

Recv: <ENQ>
Send: <ACK>
P|LIS2A|20130129102030<CR>
P|1<CR>
O|1|SPM01||^^ÂSO|R|20130129101530|20130129092030||||A\Q||||SER|||||^56||
|||O<CR>
Send: <ACK>
Recv: <EOT>
12.4 LIS2-A2 Positive Response Internal QC (Orders send from LIS)

Recv: <ENQ>
Send: <ACK>
P|LIS2A|20130129102030<CR>
P|1<CR>
O|1|CONTROL||^^ÂLP-AMP|R|20130129101530|20130129092030||||A\Q||||SER|
||||^56|||||O<CR>
Send: <ACK>
Recv: <EOT>
96 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
12.5 LIS2-A2 Negative Response to a Query All Message

Recv: <ENQ>
Send: <ACK>
Recv: <STX>H|\^&|69F2746D24014F21AD7139756F64CAD8||Modulab|||||BA400
||P|LIS2A|20130129102030<CR>
L|1|I<CR><ETX>CC<CR><LF>
Send: <ACK>
Recv: <EOT>
12.6 LIS2-A2 Negative Response to a Query by specimen (Host Query

Message)
Recv: <ENQ>
Send: <ACK>
Recv: <STX>H|\^&|69F2746D24014F21AD7139756F64CAD8||Modulab|||||BA400|
|P|LIS2A|20130129102030<CR>
P|1<CR>
O|1|0010079|||R||||||||||||||||||||Y\Q<CR>
L|1|F<CR><ETX>35<CR><LF>
Send: <ACK>
Recv: <EOT>
12.7 LIS2-A2 Upload Result Patient (without Flags)

Send: <ENQ>
Recv: <ACK>
Send: <STX>H|\^&|29ab52fb-9862-4b4e-b3dd4576fac50cbf||BA400|||||Host||P|LIS2A|20130628143243<CR>
P|1||XB000|||||<CR>
O|1|2400007003||^^ÂLBUMIN^|R||||||||||SER|||||||20130628155323|||F<CR>
R|1|^^ÂLBUMINMAU|97.61501|mg/L||||F||BIOSYSTEMS||20130214161251|A400^834000103<CR>
Recv: <ACK>
Send: <EOT>
12.8 LIS2-A2 Upload Result Patient (with Flags)

Send: <ENQ>
Recv: <ACK>
Send: <STX>H|\^&|4036d0d4-c106-4514-927d721dde639835||BA400|||||Host||P|LIS2A|20130711150902<CR>
P|1||AG001|||||<CR>
O|1|P016||^^ÂLBUMIN|R||||||||||SER|||||||20130628114243|||F<CR>
R|1|^^ÂLBUMIN|-3.33903837||1 to 2|002\029\032||F||BIOSYSTEMS||
20130628114243|A400^834000134<CR>
Recv: <ACK>
Send: <EOT>
97 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
12.9 LIS2-A2 Upload Result External QC

Send: <ENQ>
Recv: <ACK>
Send: <STX>H|\^&|1423283c-c842-4450-89bc2bf4f2a9fe6f||BA400|||||Host||P|LIS2A|20130628121144<CR>
P|1<CR>
O|1|SPM01||^^ÂSO^|R||||||Q|||||||||||20130628115219|||F<CR>
R|1|^^ÂSO|-0.104455717|IU/mL|-1 to -1|033||F||BIOSYSTEMS
||20130628115219|A400^834000815<CR>
L|1|N<CR><ETX>6B<CR><LF>
Recv: <ACK>
Send: <EOT>
12.10 LIS2-A2 Upload Result Internal QC

Send: <ENQ>
Recv: <ACK>
Send: <STX>H|\^&|9b815a8f-18c1-4aaf-bc4a3b86c3836e53||BA400|||||Host||P|LIS2A|20130628121601<CR>
P|1<CR>
O|1|C1||^^ÂSO|R||||||Q|||||||C1^20130928^123||||20130628115107|||F<CR>
R|1|^^ÂSO|2.80751252|IU/mL|1 to 2|029||F||BIOSYSTEMS
||20130628115107|A400^834000815<CR>
O|2|C2||^^ÂSO|R||||||Q|||||||C2^20130928^321||||20130628115116|||F<CR>
R|1|^^ÂSO|1.05881464|IU/mL|3 to 4|029||F||BIOSYSTEMS
||20130628115116|A400^834000815<CR>
L|1|N<CR><ETX>6B<CR><LF>
Recv: <ACK>
Send: <EOT>
98 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
12.11 HL7 Query All

Send:
<VT>MSH|^~\&|BA400|Biosystems|Host|Host
provider|20130704121800||QBP^Q11^QBP_Q11|8706f33c-fbc2-4360-b5f325438c445933|P|2.5.1|||ER|AL||UNICODE UTF-8|||LAB-27ÎHE<CR>
QPD|WOS_ALL^Work Order Step
AllÎHE_LABTF|8706f33cfbc24360b5f325438c445933<CR>
RCP|I||R<CR><FS><CR>
Recv: (No info example)
<VT>MSH|^~\&|MODULAB|MODULAB|BA400|BA400|20130704121801||OMLÔ33ÔML_O33|
201307041218011|P|2.5.1|||ER|AL||UNICODE UTF-8|||LAB-28ÎHE<CR>
SPM|1|""||""|||||||UÛnknown^1.3.6.1.4.1.21367.100.1|||||||+||Y||||||1<CR
>
SAC|||""<CR>
ORC|DC||||||||20130704121801<CR><FS><CR>
12.12 HL7 Host Query

Send:
<VT>MSH|^~\&|BA400|Biosystems|Host1|Host
provider|20130704124210||QBP^Q11^QBP_Q11|1553dee3-27de-4aef-a4a1cbb919c9b945|P|2.5.1|||ER|AL||UNICODE UTF-8|||LAB-27ÎHE<CR>
QPD|WOS^Work Order
StepÎHE_LABTF|1553dee327de4aefa4a1cbb919c9b945|2400007004<CR>
RCP|I||R<CR><FS><CR>
Recv:
<VT>MSH|^~\&|Host|Host
provider|BA400|Biosystems|20130704124210||RSP^K11^RSP_K11|20130704124210|
P|2.5.1|||NE|NE||UNICODE UTF-8|||LAB-27ÎHE<CR>
MSA|AA|1553dee3-27de-4aef-a4a1-cbb919c9b945<CR>
QAK|1553dee327de4aefa4a1cbb919c9b945|OK|WOS^Work Order StepÎHE_LABTF<CR>
QPD|WOS^Work Order
StepÎHE_LABTF|1553dee327de4aefa4a1cbb919c9b945|2400007004<CR><FS><CR>
12.13 HL7 Order Download

<VT>MSH|^~\&|MODULAB|MODULAB|BA400|BA400|20130703111604||OMLÔ33ÔML_O33|
201307031116041|P|2.5.1|||ER|AL||UNICODE UTF-8|||LAB-28ÎHE<CR>
PID|1||xb005||fulanito|flungencia|19770703|F||2106-3<CR>
SPM|1|4800007005|PSPM_A~PSPM_B~PSPM_C|URIÛRI^2.16.840.1.113883.12.70||||
|||P||3||||20130703111604|20130703111605||Y||||||1|
SAC|||4800007005||||||||||||||||||||||||||^1^1^22<CR>
ORC|NW|||AWOSID05|IP||||20130703111604||||||||||||SERVICIO<CR>
I+D^^^^^^FI^^^1||||||20130703111605<CR>
TQ1|||||||||S<CR>
OBR|1|AWOSID05||K+^K+^1.3.6.1.4.1.21367.100.1||||||||||||123456^NOMBRE
DOCTOR<CR><FS><CR>
99 of 100
Biosystems. S.A.
version. 0.3
June 19, 2013
12.14 HL7 Upload Results (patient with flags)

provider|20130705093914||OUL^R22ÔUL_R22|b023f4e1-dd4b-4ef5-918181babdd3eea3|P|2.5.1|||ER|AL||UNICODE UTF-8|||LAB-29ÎHE<CR>
PID|||xb004||^^|||<CR>
SPM|1|2400007004||SER|||||||P|||||||<CR>
OBR||20130628083831163IDALRIME||CHOLESTEROL^CHOLESTEROLÂ400|||||||||||||
||||||||||||<CR>
ORC|OK||||CM||||20130705093914<CR>
OBX|1|NM|CHOLESTEROL^CHOLESTEROLÂ400||0.0191002265|mg/dL^mg/dLÂ400||002~029|||F|||||BIOSYSTEMS||A400^Biosystem
s~834000815^Biosystems|20130628114722<CR>
OBR||20130628083831163IDA0RIME||CK^CKÂ400|||||||||||||||||||||||||<CR>
ORC|OK||||CM||||20130705093914<CR>
OBX|1|NM|CK^CKÂ400||4.2266469|U/LÛ/LÂ400||002~029|||F|||||BIOSYSTEMS||
A400^Biosystems~834000815^Biosystems|20130628115237<CR><FS><CR>
12.15 HL7 Upload Results (QC without flags)

provider|20130705094755||OUL^R22ÔUL_R22|1298f4ab-8435-4633-8020f6e7dbe0cd47|P|2.5.1|||ER|AL||UNICODE UTF-8|||LAB-29ÎHE<CR>
SPM|1|C1||NULL|||||||Q|||||||<CR>
INV|C1|OK|CO|||||||||20130928102426||||123<CR>
OBR||""||ASOÂSOÂ400|||||||||||||||||||||||||<CR>
ORC|OK||||CM||||20130705094755<CR>
OBX|1|NM|ASOÂSOÂ400||2.80751252|IU/mLÎU/mLÂ400|1 2|NONE|||F|||||BIOSYSTEMS||A400^Biosystems~834000815^Biosystems|201306281
15107<CR>
SPM|1|C2||NULL|||||||Q|||||||<CR>
INV|C2|OK|CO|||||||||20130928102437||||321<CR>
OBR||""||ASOÂSOÂ400|||||||||||||||||||||||||<CR>
ORC|OK||||CM||||20130705094755<CR>
OBX|1|NM|ASOÂSOÂ400||1.05881464|IU/mLÎU/mLÂ400|3 4|NONE|||F|||||BIOSYSTEMS||A400^Biosystems~834000815^Biosystems|201306281
15116<CR><FS><CR>
12.16 HL7 Error message

Send:
provider|20130708074756||NACK^NACK|80|P|2.5.1||||||UNICODE UTF-8||<CR>
MSA|AR|<CR>
ERR|||207|E|invalidMessage||Message rejected<CR><FS><CR>
100 of 100
Biosystems. S.A.

BA400 LIS Protocol - ASTM+HL7 (v2.1.1) - FINAL

Uploaded by

Copyright:

Available Formats

BA400 LIS Protocol - ASTM+HL7 (v2.1.1) - FINAL

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

BA400 LIS Protocol - ASTM+HL7 (v2.1.1) - FINAL

Uploaded by

Copyright:

Available Formats

BA 400 LIS PROTOCOL SPECIFICATION

LIS2-A2 (ASTM) + HL7

BA400 LIS PROTOCOL SPECIFICATION

June 19, 2013

Definitions and Acronyms .................................................................................................. 9

Background and Terminology .......................................................................................... 10

Physical Layer ........................................................................................................................... 12

LIS01-A2 (ASTM) ............................................................................................................... 12

Transport Layer ........................................................................................................................ 15

Minimal Lower Layer Protocol ......................................................................................... 15

Establishment Phase (Link Connection) ................................................................... 16

Transfer Phase .......................................................................................................... 17

Termination Phase (link release) .............................................................................. 19

Error Recovery .......................................................................................................... 19

Valid Characters in the Text part .............................................................................. 20

Message Layer .......................................................................................................................... 21

Message length ................................................................................................................ 21

LIS2-A2 Records ........................................................................................................ 21

HL7 Segments ........................................................................................................... 23

Data Types ................................................................................................................ 24

BA400 LIS PROTOCOL SPECIFICATION

Hexadecimal escaping .............................................................................................. 27

Local escape sequence ............................................................................................. 27

Acknowledge and error recovery ..................................................................................... 27

Workflow Scenarios ................................................................................................................. 31

AWOS transfer to the BA 400 before specimen arrival ................................................... 31

AWOS broadcast by the LIS before specimen arrival ............................................... 31

AWOS created at the BA 400 ........................................................................................... 32

AWOS Query by the Analyzer at specimen arrival ........................................................... 33

Rerun decided on the BA 400 immediately after the first run................................. 33

Rerun decided during technical validation on the LIS .............................................. 34

Rerun decided during clinical validation on the Order Filler ................................... 34

June 19, 2013

Reflex decided during clinical validation on the LIS ................................................. 36

Reflex decided during clinical validation on the Order Filler ................................... 36

Retransmit results from BA 400 ....................................................................................... 37

QC performed on an analyzer .......................................................................................... 37

Pooling of patient specimens [v2] .................................................................................... 37

Due to wrong syntax or unmapped values .............................................................. 38

Due to incorrect field content .................................................................................. 38

Due to Reruns requests ............................................................................................ 39

Due to Cancellations requested by LIS (Cancel message sent by LIS) ..................... 39

Due to Users actions ............................................................................................... 39

HL7 IHE-LAW Transaction LAB-27: Query for AWOS................................................................ 40

Use Case Roles.................................................................................................................. 40

Interaction Diagram ......................................................................................................... 41

BA400 LIS PROTOCOL SPECIFICATION

June 19, 2013

Message Static Definitions ............................................................................................... 41

Trigger Events ........................................................................................................... 41

Message Semantics .................................................................................................. 41

Expected Actions ...................................................................................................... 42

QPD Segment ........................................................................................................... 42

RCP Segment ............................................................................................................ 43

Use Case Roles.................................................................................................................. 45

Interaction Diagram ......................................................................................................... 46

Message Static Definitions ............................................................................................... 46

Trigger Events ........................................................................................................... 46

Message Semantics .................................................................................................. 47