Atellica® Data Manager

LIS Interface Guide

11314645 Rev. 02 2019-05

© 20182019 Siemens Healthcare Diagnostics Inc. All rights reserved.
No part of this manual or the products it describes may be reproduced
by any means or in any form without prior consent in writing from
Siemens Healthcare Diagnostics.
ADVIA, ADVIA Centaur, Aptio, Atellica, CentraLink, and Dimension
Vista are trademarks of Siemens Healthcare Diagnostics Inc.
All other trademarks and brands are the property of their respective
owners.

The information in this document was correct at the time of printing.

However, Siemens Healthcare Diagnostics continues to improve
products and reserves the right to change specifications, equipment,
and maintenance procedures at any time without notice.
If the system is used in a manner differently than specified by
Siemens Healthcare Diagnostics, the protection provided by the
equipment may be impaired. See warning and hazard statements.
 1 Introduction
LIS Connections Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Accessing Product Information in the Document Library . .7

2 LIS Requirements
Identifying Special Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Upload and Download Connections . . . . . . . . . . . . . . . . . . . . . . . 11

3 Cytogram Image Upload to LIS

4 ASTM 1394 Protocol

ASTM 1394 Protocol and Atellica Data Manager . . . . . . . . .15
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Frame Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Downloading Workorders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Functional Description of Bidirectional Communication . . . . . . . 19
Contention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Translator Specific Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Workorder Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Patient Result Upload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
ASTM Transmission Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5 Technidata LMX 6.0

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Translator Specific Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

6 Specimen Receipt Information and

Archive Location Transmission
Inlabbing Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Archive Location Information Upload . . . . . . . . . . . . . . . . . . . . . . 90
ASTM 1394 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Technidata LMX Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7 Siemens Host Spec. 79 Protocol

Message Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

11314645 Rev. 02 3 / 150

 8 HL7 Version 2.5
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Translator Specific Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Lower Layer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Single and Dual Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Message Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

9 Serial Connection

10 ASCII Character Codes

11 Multiple LIS Connections

Uploading of Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Quality Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
LIS Channel for the Biorad Program. . . . . . . . . . . . . . . . . . . . . . . 146

12 Hard-coded Comments

13 CentraLink Systems
Major Changes from CentraLink Version 15 to
Version 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

4 / 150 11314645 Rev. 02

Atellica Data Manager Introduction

1 Introduction

LIS Connections Support

This document outlines the communication between one or more
laboratory information systems (LIS), or host computer and the
Atellica® Data Manager (Atellica DM) system.
The Atellica DM system receives downloaded workorders from, and
uploads results to, the LIS. Communication is enabled per the following
protocols:
• ASTM 1394
• Technidata LMX
• Siemens Host Spec .79
• HL7 Version 2.5
If the LIS vendor has a choice of protocols, then the ASTM 1394
communication protocol using TCP/IP is the recommended protocol for use
with Atellica DM.
Siemens diagnostic and 3rd party systems perform diagnostic tests using
the communication protocols outlined in this document that are intended
for in vitro diagnostic use. As with all diagnostic tests, a definitive clinical
diagnosis should not be based on the results of a single test, but should
only be made by the physician/clinician after evaluating all clinical and
laboratory findings. Atellica DM only transmits results according to the
protocols in this document and does not alter test results in any way.

11314645 Rev. 02 5 / 150

Introduction Atellica Data Manager

Document Conventions
Convention Description

BIOHAZARD Biohazard statements alert you to

potentially biohazardous conditions.

LASER WARNING Laser Warning statements alert you to the

risk of exposure to lasers.

WARNING Warning statements alert you to conditions

that may cause personal injury.

CAUTION Caution statements alert you to conditions

that may cause product damage or loss of
data. On the system, this symbol indicates
that you should refer to the operator’s guide
for more information.
NOTE: Note statements alert you to important
information that requires your attention.
Bold Bold type indicates commands on the user
interface, keys, or the exact text that an
operator needs to type.
For example, if the word save appears as
Save, it refers to the selecting the Save
button on the user interface.
Another example is typing a specific entry
into a text box. If the word welcome appears
as welcome, it means that you should type
that word into the specified field.
Italic Italic type refers to the title of a document or
a section title in this operator’s guide. For
example, Chapter 2, LIS Requirements refers
to Section 2 of this operator’s guide.

Terminology
Term Description
Select To select an item, use your finger to touch the item on the
touch-screen monitor or select the item with the system
pointing device. The background of the item changes color or
displays a black frame to indicate that you selected the item.
Enter Type the specified information using the keyboard and then
press the Enter key.
Scan Move the hand-held barcode scanner over the specified
barcode to enter the information.

6 / 150 11314645 Rev. 02

Atellica Data Manager Introduction

Accessing Product Information in the Document Library

1. In a browser, such as Internet Explorer, enter
siemens.com/document-library.
2. Login following the on-screen instructions.
3. Search for assay or system information.

11314645 Rev. 02 7 / 150

Introduction Atellica Data Manager

8 / 150 11314645 Rev. 02

2 LIS Requirements

The following are requirements when connecting an LIS to the

Atellica Data Manager:
• The LIS must be capable of batch transmission of workorders to the
Atellica DM system. The Atellica DM system does not support query
mode with the LIS.
• The LIS must support unique Sample ID numbers.
• The Atellica DM software is designed to operate with unique Patient IDs
across all connected LIS. As the LIS is considered the master system
from which the most current data originates, the Atellica DM software
always accepts updates to patient records from the originating LIS.
As such, every patient demographic update that is downloaded from the
LIS to the Atellica DM software must be identified by a unique patient ID
that references the same physical patient.

WARNING
If you reuse a patient ID to reference another physical patient, patient
demographic updates downloaded from the LIS overwrite the original
patient details associated with this patient ID. An erroneous mix of details
that pertain to another physical patient would coexist in the same record
of the Atellica Data Manager database with unrelated details that pertain
to the original physical patient. Do not re-use patient IDs.

• The LIS should specify the Sample Type in the workorder. The
Atellica DM system is designed to operate in an environment in which
the Sample Type is specified in the workorder that is downloaded from
the LIS. If the Sample Type is not included in the workorder, the
Atellica DM system applies the Sample Type for the first test in the
workorder to the entire workorder.
• The LIS must be capable of assigning different Sample ID numbers to
samples of different sample type for the same patient and then
sending the Sample ID numbers to the Atellica DM system as different
workorders. For example, a Serum tube and a Urine tube from the
same patient must not be assigned the same Sample ID number.
• If samples are divided into multiple sample tubes for an aliquot, each
sample tube must have a unique Sample ID.
• You cannot download test panels from the LIS to the
Atellica DM system.

11314645 Rev. 02 9 / 150

LIS Requirements Atellica Data Manager

• The LIS must be capable of separating different Sample Types into

different workorders. The Atellica DM system requires that Sample
Types are not mixed in a given workorder. If a workorder contains tests
for a mixture of Sample Types, the Atellica DM software rejects the
tests that do not match the specified or inferred Sample Type and
process only those requests that match. This rejection is done without
notification to the user, and is only available via Atellica DM log files.
• The units of measure for a given test must be defined identically at the
LIS, in the Atellica DM software, and at the instruments. You must
predefine the units for tests in the Atellica DM software to match the
units for tests on the instrument. If units of measure of results are
manually changed on an instrument, you must change the units of
measure for the test in the Atellica DM software at that time. In
addition, you must purge all existing results for the test from the
Atellica DM software. Units of measure are not uploaded to the LIS
from the Atellica DM software.
• Some instruments have multiple result aspects for 1 result. You can
configure the Atellica DM software to upload 1 aspect or all aspects
related to that result.

Identifying Special Characters

Ensure that special characters within an LIS message are identified and
displayed correctly when sent to the Atellica DM system.
This is important for correct functioning of the application; for example
when unit checking is enabled for LIS Previous Results.
Example: unit of x10^3/uL.
Identify the “^” character with an escape sequence ( &S&) to ensure the
unit is parsed correctly by the Atellica DM system. In this case, &S& is
received and the Atellica DM software knows that this means ^ literally,
rather than as the special ASTM character.
Aptio® Automation systems do not process the ~ (tilde) correctly. When
connecting an Aptio Automation system, do not use the ~ character.

10 / 150 11314645 Rev. 02

Atellica Data Manager LIS Requirements

Upload and Download Connections

Different communication connections can be configured between the LIS
and the Atellica DM system.
You have the option of configuring 1 or more communication connections
with a single LIS.
1-connection configurations allow uploading and downloading data using
a single connection.
2-connection configurations enable downloading test orders from the LIS
through 1 connection, and uploading results from the Atellica DM software
through the other connection.
Multiple-connection configurations enable downloading test orders from
the LIS through multiple connections, and uploading results from the
Atellica DM software through 1 connection.
While the 2 or more communication channel configuration is not required,
the 2 communication connections improve communication efficiency for
LIS that are capable of supporting dual connections.

11314645 Rev. 02 11 / 150

LIS Requirements Atellica Data Manager

12 / 150 11314645 Rev. 02

3 Cytogram Image Upload to LIS

The cytogram image result is referenced by the Hemimage test in a

sample. You can upload cytogram images from the Atellica Data Manager
to the LIS. The following are restrictions on cytogram upload:
• Cytograms must be in bitmap (BMP) format.
• You must upload cytogram images using file transfer protocol (FTP).
You cannot upload images to a folder on the Atellica Data Manager
Server.
• Define output for Cytograms on the LIS Channel window.
• The Atellica DM system uploads cytogram images using anonymous
FTP. The same error message displays in any case of mis-configuration.
• The LIS Vendor must match the cytograms to the sample IDs (SID)
using the value in the result field of the record that has the Hemimage
test code.
In the example below the Hemimage test is uploaded with the test
code 250. The LIS Vendor must match the file 941.bmp in the FTP input
directory to SID 65984. Relevant parts of the code are highlighted in bold.
H|^~\&|||LMXS^ATELLICA DATA MANAGER||ORU|||38-
1^LIS||P|A2.2|20090708100427|
P|1|||||||U||||||||||||||||||
OBR|1|65984||WBC^^L|R||||||||||||||||||||
OBX|1|NM|007||7.25|||*||||19970321113533|||||
OBR|2|65984||RBC^^L|R||||||||||||||||||||
OBX|1|NM|014||4.77|||*||||19970321113533|||||
OBR|3|65984||HGB^^L|R||||||||||||||||||||
OBX|1|NM|035||14.3|||*||||19970321113533|||||
OBR|41|65984||NRBC^^L|R||||||||||||||||||||
OBX|1|CE|044||+|||||||19970321113533|||||
OBR|42|65984||HemImage^^L|R||||||||||||||||||||
OBX|1|ST|250||941|||||||19970321113533|||||
L|||1|87|
NOTE: This example uses LMX communication, and is similar to logic for
other protocols.

11314645 Rev. 02 13 / 150

Cytogram Image Upload to LIS Atellica Data Manager

14 / 150 11314645 Rev. 02

4 ASTM 1394 Protocol

ASTM 1394 Protocol and Atellica Data Manager

This section describes the ASTM 1394 protocol used for the
communication link between the Atellica Data Manager and a laboratory
information system (LIS) or host computer.
NOTE: The ASTM 1394 communication protocol is the recommended
protocol for use with the Atellica DM system.
This section is intended for the information systems professional
responsible for connecting the Atellica DM system and your host
computer. Contact your local technical support provider or distributor for
additional information.
For a more detailed description of the ASTM 1394 protocol, refer to
Standard Specification for Transferring Clinical Observations between
Independent Computer Systems (ASTM Designation: E 1394-97).
NOTE: The LIS must initiate the TCP socket communication in order for
the Atellica DM system to upload results.

Overview
The ASTM 1394 communication protocol, using dual TCP-IP connections, is
the recommended protocol for use with the Atellica DM system.
The ASTM communication protocol supported by the
Atellica Data Manager software is based on ASTM standards E1394-97
(Standard Specification for Transferring Information Between Clinical
Instruments and Computer Systems) and E1381-95 (Standard Specification
for Low-Level Protocol to Transfer Messages Between Clinical Laboratory
Instruments and Computer Systems).
The ASTM communication link allows the LIS to transmit workorders
and multiple previous patient results for the same test to the
Atellica DM software and to accept QC and patient test results transmitted
from the Atellica DM software.

Atellica Data Manager to LIS to

LIS Atellica Data Manager
QC Workorders

Results Previous sample results

Lab Automation location

11314645 Rev. 02 15 / 150

ASTM 1394 Protocol Atellica Data Manager

The LIS initiates the TCP-IP socket connection for sending patient
workorder information to the Atellica DM system before each sample run.
The information will be parsed and stored in the system for download to
the instrument.
The Atellica DM system can be configured to automatically transfer
available results to the host or manually transfer results to permit the
operator time to review the data and release the sample results.
The LIS must support an implementation of ASTM 1394 and individual
fields must be customized to support the Atellica DM implementation.

Frame Size
Messages are sent in frames. Each frame contains a maximum of 247
characters (including frame overhead). Messages longer than 240
characters are divided between two or more frames.
Multiple records are never combined in a single frame. Every record must
begin in a new frame. A frame is one of 2 types, an intermediate frame or
an end frame.
• Intermediate frames terminate with the characters <ETB>, checksum,
<CR> and <LF>.
• End frames terminate with the characters <ETX>, checksum, <CR> and
<LF>.
A record containing 240 characters or fewer is sent in a single end frame.
Longer records are sent in intermediate frames with the last part of the
record sent in an end frame.
The frame structure is illustrated as follows:
<STX> FN text <ETB> C1 C2 <CR> <LF> - intermediate
frame
<STX> FN text <ETX> C1 C2 <CR> <LF> - end frame
where:
<STX> = Start of Text transmission control character
FN = single digit Frame Number 0 to 7
text = Data Content of Message
<ETB> = End of Transmission Block transmission control
character
<ETX> = End of Text transmission control character
C1 = most significant character of checksum 0 to 9 and
A to F

16 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

C2 = least significant character of checksum 0 to 9 and

A to F
<CR> = Carriage Return ASCII character
<LF> = Line Feed ASCII character

Downloading Workorders
The host computer downloads workorders identified by a sample
identification number (SID#). Limit the number of workorders per
Workorder message to approximately 1000 with an average of 10 requests
per workorder. Messages with more than 1000 orders may be subject to a
timeout.
Workorders can be downloaded in any sequence.
When the Atellica DM software receives a request from the analyzer, the
Atellica DM system searches the database for the matching workorder.
About Atellica Data Manager workorders:
• The LIS should specify the sample type in the workorder. The
Atellica DM system is designed to operate in an environment in which
the sample type is specified in the workorder that is downloaded from
the LIS.
• If communication is interrupted during workorder download, the
Atellica DM software correctly processes all records that were correctly
received before the communication interruption. Messages sent after
the communication interruption are not processed.
• The Atellica DM software does not support replicate testing. Only 1
replicate of a test can be ordered for each sample. If the LIS orders a
test multiple times in 1 message, the test will still only run 1 time on
the instrument.

Rejection of Requests in LIS Orders

If an order contains requests that do not match the order sample type or, in
its absence, the first request sample type, these requests are not added to
the order in the Atellica DM system. You are not informed of this through
error messages other than those contained in the LIS internal service log.
When generating orders at the LIS, ensure that requests that have different
sample type definitions in the Atellica DM database are not included in the
same order.

11314645 Rev. 02 17 / 150

ASTM 1394 Protocol Atellica Data Manager

Responding to a Message (ACK or NAK)

To confirm the identity and transmission quality of each message, the
receiving device (Atellica DM system or LIS) must respond to each message
with an acknowledgement (ACK) or not acknowledged (NAK) message.
• If the transmitted record checksum is correct, the receiving device
sends an ACK response of one byte. Upon receiving the ACK response,
the sender continues the dialogue.
• If a NAK is received, the sender retransmits the record. This process
may be repeated for a maximum of seven times.
• During the establishment phase, the sender must set timer when
transmitting the <ENQ>. If a reply of an <ACK>, <NAK>, or <ENQ> is
not received within 15 seconds, a timeout occurs. After a timeout, the
sender enters the termination phase according to the ASTM 1381
protocol. If the Atellica DM software is the sender, however, an ENQ is
transmitted instead of EOT and the 15 second timer starts again. This is
repeated until a response is received from the LIS or until 7 ENQs are
transmitted, at which point an EOT is transmitted to signal the line is in
the neutral state.
• During the establishment phase, if the LIS detects contention, it sets a
timer. If an <ENQ> is not received within 20 seconds, a timeout occurs.
After a timeout, the receiver regards 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 a 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. As with
excessive retransmissions of defective frames, the message must be
stored/remembered so that the transmission can be repeated
completely.
• The Atellica DM software responds with an acknowledgment (ACK) if
the message frame is received without error. The ACK indicates that
the message frame calculated checksum match the checksum sent
with the frame. The ACK does not indicate that the message frame is
part of a syntactically correct message.

18 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Functional Description of Bidirectional Communication

Workorder Download Message Exchange
The Workorder Download Message Exchange Results Transmission Mode,
page 21, outlines the dialogue that occurs between the host computer and
the Atellica DM software during a workorder download. The following
paragraphs describe the message exchanges illustrated in this table.

Initiation Phase (Table 1, A)

At the start of communication, the data link is idle, and both the host and
the Atellica DM system are in the listening mode. For downloading the
workorder, the host computer initiates a communication link by taking
control as the “sender” device and sending an initiation message (ENQ) to
the Atellica DM software. In this way, the Atellica DM system is informed
that the host computer is ready for communication and responds with an
acknowledgement (ACK) indicating that it is ready to receive
communication from the host computer.
The first record transmitted is the “H” or header record which establishes
the rules for delimiting the fields of the subsequent records. After receiving
the “H” record, the Atellica DM system responds with and
acknowledgement (ACK) indicating that the record was received without
error.

Workorder Transmission (Table 1,B)

After the Initiation Phase, the host computer remains the “sender” device
and can start transmitting workorders one at a time in a sequence that
is determined by the host computer. Each workorder is transmitted as
1 records. The first record is the Patient (P) record. The Atellica DM system
responds with an acknowledgement (ACK) if the record is received without
error. The Test Order (O) record is transmitted next by the host computer.
The Atellica DM software responds with an acknowledgment (ACK) if the
record is received without error. The host computer must wait for each
record to be acknowledged by the Atellica DM system before continuing
with the next record. Multiple workorders may be transmitted while the
host computer is acting as “sender” of the channel by simply continuing
with patient and order record pairs until the host computer has completed
downloading workorders.

11314645 Rev. 02 19 / 150

ASTM 1394 Protocol Atellica Data Manager

A workorder must be downloaded to the system before the associated

sample is aspirated by the analyzer. If not, the analyzer attempts a query,
which if unanswered, results in different actions depending on the
instrument. For certain instruments, a query where no work exists causes a
“no work” response to return to the instrument. For other instruments, a
query where no work exists causes the instrument to skip the sample. The
ADVIA® 120/2120 Hematology System, for example, is designed to use a
default profile instead of the profile requested in the workorder.

Data Link Release from Host Computer (Table 1, C)

After the host computer has finished downloading workorders, the host
transmits a Terminator (L) record indicating that the host has completed
transfer of all message blocks to be transmitted in this session. The
Atellica DM system acknowledges (ACK) the record. The host then sends
an end of transmission (EOT) character to the Atellica DM system and both
the Atellica DM system and the host return to the idle state.
An EOT character should always be sent from the LIS after the transmission
of a terminator record.
If the terminator record from one ASTM message is released without an
EOT and is followed by another ASTM message, which consists of a Header,
Patient(s), Order(s) and Terminator record, the Atellica DM translator may
lose the orders while responding to the LIS messages with ACKs. The LIS
considers the orders transmitted.

20 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Table 1: Workorder Download Message Exchange Results Transmission Mode

Operation Atellica Messages Exchanged Host

Data Computer
Manager
System
Initiation Phase Receiver Initiation Message (ENQ) Sender

Acknowledgment (ACK)

Header Message (H)

Acknowledgment (ACK)

Downloading Receiver Patient Record Sender

Workorders

Acknowledgment (ACK)

Order Record

Acknowledgment (ACK)

Release Phase Sender Terminator Record (L) Sender

Acknowledgment (ACK)

End of Transmission (EOT)

11314645 Rev. 02 21 / 150

ASTM 1394 Protocol Atellica Data Manager

Table 2, Result Upload Message Exchange outlines the dialogue that

occurs between the Atellica DM software and a host computer during a
result upload. The following paragraphs describe the message exchanges
outlined in this table.

Sorting of Transmitted Sample Results

When the system automatically transmits sample results to the LIS using
the task scheduler, it automatically sorts the results by priority and sends
STAT samples first. Test results that you manually transmit to the LIS are
not sorted by priority unless you configure the system to do so using the
following procedure:
NOTE: These are instructions for Siemens Service representatives only.
1. On the command Query Parameter Set, in the Sample Query editor
window, enter the sample criteria for the samples for upload and then
select the Advanced tab.
2. In the Sort criterion field, select the sorting method.
Selecting the Priority and Creation Time option enables the display of
STAT samples first.
3. Select OK to run the query.
The samples are uploaded in the order in which they were selected. If all
the samples were selected at once, the STAT samples at the top of the list
are uploaded first.

Initiation Phase (Table 2, D)

NOTE: This section is based on a scenario wherein the LIS has already
initiated TCP-IP socket connection.
At the start of communications, the data link is idle and both the host
computer and the Atellica DM system are in the listening mode. For
uploading the results, the Atellica DM software initiates taking control as
the “sender” device by sending a (ENQ) message to the host. In this way,
the host is informed that the Atellica DM systemis ready for
communication. The host computer responds with an (ACK)
acknowledgement indicating that the host computer is ready to receive
communication from the Atellica DM system.
NOTE: If the Atellica DM software transmits an (ENQ) but does not receive
an (ACK) from the host computer after the initial 15 second timeout, the
Atellica DM software continues to send an (ENQ) every 15 seconds for an
additional 6 times in an attempt to establish communication with the host.
If an additional (ENQ) is not handled and acknowledged by the host after
the initial 15 second timeout, communication with the host could become
out of sync. Only after the sixth attempt to contact the host does the
Atellica DM software transmit an (EOT).

22 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

NOTE: The Atellica DM software does not ignore EOT messages sent from
the LIS in response to an ENQ. An EOT is sent in response and the line is
released. This is not in accordance with section 6.2.4 of the ASTM 1381
protocol.
The first record transmitted is the header (H) record, which establishes the
rules for field delimiting the subsequent records. After receiving the header
record, the host computer responds with an acknowledgement (ACK)
indicating that the record was received without error.

Transmission Results (Table 2, E)

After establishing the Atellica DM system as the sender, the results are
uploaded to the host computer as a series of records. The first record is a
patient (P) record to identify the sample and demographic information
used by the Atellica DM system for normal range criteria. The second
record is a repeat of the order (O) record followed by one result (R) record
for each test reported. The record contains the test name, measured value,
data status, and date and time of the analysis.
Each record transmitted to the host computer must contain a checksum
and be acknowledged (ACK) by the host computer before the next record
may be transmitted.
Single sample results are uploaded while the Atellica DM software is the
sender. The data link is released between sample reports.
NOTE: Result uploads are only made if a previous data link layer initiation
has been made by the LIS. This is how the Atellica DM system determines
the host IP address.

Data Link Release from the Atellica Data Manager (Table 2, F)

After the Atellica DM system has finished uploading results, the
Atellica DM system transmits a terminator (L) record that releases the
communication data link. The host computer acknowledges (ACK) the last
record. The Atellica DM system then transmits an end of transmission
(EOT) character and both it and the host computer return to the idle state.

11314645 Rev. 02 23 / 150

ASTM 1394 Protocol Atellica Data Manager

Table 2: Result Upload Message Exchange

Operation Atellica Messages Exchanged Host

Data Computer
Manager
System
a. Initiation Sender Initiation Message(ENQ) Receiver
Phase

Acknowledgment (ACK)

Header Message (H)

Acknowledgment (ACK)

24 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Operation Atellica Messages Exchanged Host

Data Computer
Manager
System
b. Transmission Sender Patient Record Receiver
Results

Acknowledgment (ACK)

Order Record

Acknowledgment (ACK)

Result Message (R1)

Acknowledgment (ACK)

Result Message (R22)

Acknowledgment (ACK)
c. Release Sender Terminator Record (L) Receiver
Phase

Acknowledgment (ACK)

End of Transmission (EOT)

11314645 Rev. 02 25 / 150

ASTM 1394 Protocol Atellica Data Manager

Contention
For single channel communication, contention may occur during the
initiation phase if the Atellica DM software and the host both try to take
control by simultaneously sending an ENQ. When contention occurs, the
Atellica DM software has priority to transmit information.
Contention is resolved as follows:
1. Upon receiving a reply of <ENQ> to its transmitted <ENQ>, the host
system must stop trying to transmit; the host must prepare to receive.
When the next <ENQ> is received, it replies with an <ACK> or <NAK>
depending on its readiness to receive.
2. Upon receiving a reply of <ENQ> to its transmitted <ENQ>, the
Atellica DM software waits at least 1 second before sending another
<ENQ>.

Specimen Receipt Information with the ASTM Protocol

Specimen receipt (inlabbing) information such as SID, read date and time,
and check-in location are transmitted from the Atellica DM system to the
LIS within the Manufacturer record of the LAS Status Upload message.
For information on the grammar of the inlabbing information contained
within a result file and an example of the inlabbing transmission to the LIS,
refer to Chapter 6, Specimen Receipt Information and Archive Location
Transmission.
NOTE: Inlabbing information will not be forwarded to the LIS for samples
that contain no workorders, unless this option is configured specifically by
Siemens local support.

26 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Translator Specific Options

In the Atellica Data Manager, the driver for the ASTM 1394 LIS translator is
the asts driver. The translator specific options are as follows:

-s <port > <port> set to the TCP/IP port where the LIS translator
listens for socket connections. This port must match
with the port defined on the LIS. The usual setting is
-s 8888. This parameter is mandatory.

-r The -r option is used to remove the dilution and/or

result aspect information from the record field and
only send the test identifier in the result record field.

-c Remove the result aspect info for qc results only.

-e The -e option is used in conjunction with the -i

option and specifies that the <name string> is
substituted only for blank instrument identifiers.

-i <name The -i <name string> option specifies that the <name

string> string> is substituted for the instrument name in the
result record. The name string can be blank.

-p The -p option enables the regrouping of result

messages for each instrument. A separate, complete
message is uploaded for each instrument.

-t <timeout>Inter character timeout between 10 and

300 sec. Default = 30.

-v the -v option allows you to verify the frame

sequence number.

11314645 Rev. 02 27 / 150

ASTM 1394 Protocol Atellica Data Manager

ASTM 1394 Action Codes

Incoming orders are processed based on the Action Code in field 12 of the
order record. This table describes how the action codes are interpreted.

Action Code Action

N (New) or blank • If sample ID exists in the database, a duplicate
sample ID error is generated.
• If sample ID does not exist in the database, create
new sample.
A (Add) • If the workorder sent from the LIS has patient
information that does not match the patient
information that already exists for the sample in
the Atellica Data Manager software, then a
mismatch on Patient Identifier (PID) occurs. An
unmatched patient error is generated.
A (Add) NOTE: When a PID is associated with a sample, the
PID downloaded from the LIS must be consistent with
this PID in order to ensure the integrity of the unique
sample ID and PID environment.
• If the workorder sent from the LIS has patient
information that matches the patient information
that already exists for the sample in the
Atellica DM software, then matching uploaded
database requests are rerun.
• Add new requests.
C (Cancel) • If the workorder sent from the LIS has patient
information that does not match the patient
information that already exists for the sample in
the Atellica DM software, an unmatched patient
error is generated.
• When a test is not defined in the
Atellica DM software and action code C is used to
cancel the associated test request of the work
order, the action code serves as a cancellation
order and all test requests of the work order with
a status less than Review are omitted.
• When a test is defined in the Atellica DM software
and action code C is used to cancel the associated
test request of the work order, only the
associated test request of the work order is
omitted.

28 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Grammar
The grammar, which provides a description of the ASTM interface, is
formally described in the following tables. Each table row represents a
grammar rule. The first rule defines the element “Message” in terms of
smaller elements. Other, smaller elements are defined subsequently.
• Elements in italics indicate that the text is translated (using another
rule, unless obvious).
• Elements in bold indicate that the text is used literally.
• Vertical | bars are field delimiters.
• Square brackets [ ] denote optional inclusion.
• Curly braces { } denote optional repeated inclusion.
• Parentheses ( ) denote grouping.
• Asterisks * denote ignored strings.
• Carets ^ denote subfield separators

Workorder Download

Component Syntax Comment

Message Header { PatientInformationRecord
{ PatientCommentRecord }
{TestOrderRecord
{ TestOrderCommentRecord }
{ ResultRecord } } }Terminator
Header H | \ ^ & | | | | | | | | | | P | 1 |<CR> \ is the repeat delimiter, ^ is the
Record component delimiter, & is the
escape character.

11314645 Rev. 02 29 / 150

ASTM 1394 Protocol Atellica Data Manager

Component Syntax Comment

Patient P | SeqNo | Patient.Identifier | NOTE: If the patient
Information Patient.Identifier | * | birthdate value downloaded
Record Patient.LastName ^ Patient.FirstName from the LIS indicates that the
^ Patient.MiddleName ^ * | * | patient age is greater than
Patient.Birthdate | Patient.Sex | * | * | * 150 years, the birthdate value
| * | * | SpeciesIdentifier | * | * | * | * | * is not accepted and the
| * | * | * | * | * | PatientLocation.Name patient birthdate is not
| * | * | * | * | * | * | * | * | *<CR> populated in the
Maximum Record Length Atellica DM system.
Patient.Identifier: 40 Patient Sex is M or F only.
Patient.LastName: 70 If coding system is active, the
SpeciesIdentifier maximum
Patient.FirstName: 70
record length is 30.
Patient.MiddleName: 70
Patient.Birthdate: 8 (YYYYMMDD)
Patient.Sex: 1
SpeciesIdentifier: 70
PatientLocation.Name: 70
Patient If Patient.Identifier is not
Identifier specified, Patient.LastName,
Patient.FirstName,
Patient.MiddleName,
Patient.Birthdate, Patient.Sex,
SpeciesIdentifier, and
PatientLocation.Name will not
be stored in the Atellica DM
database for this order.
Patient Identifier (PID) is limited
to 40 characters.
Patient Patient Last Name, First Name,
Name and Middle Name fields are
restricted to 70 characters
each.
Species — If a coding system is in effect,
Identifier this is used to identify a species
by SpeciesCode.Value. If not,
this is used to identify a species
by Species.Name.
Patient If no patient location is
Location specified in the order record,
the patient location from the
patient record is used.

30 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Component Syntax Comment

Patient C | SeqNo | * | Patient.Comment | —
Comment *<CR>
Record Maximum Record Length
Patient.Comment: 2500
Test Order O | SeqNo | Sample.Identifier | * | [ Limit the number of workorders
Record Request ] { \ Request } | Priority | * | per Workorder message to
Sample.CollectionTime | * | * ^ * ^ approximately 1000 with an
Sample.ContainerType | * | ActionCode average of 10 requests per
| * | * | * | SampleTypeIdentifier | workorder.
Physician.Identifier | * | * | * | * | * | * | The Atellica DM software does
* | * | * | * | PatientLocation.Name | * | not process ASTM requested/
* | *<CR> ordered date and Time in Order
download messages.
Physician ID is limited to 40
characters.
NOTE: Do not mix Action
Codes in the same message.
The Atellica Data Manager
software does not support the
receipt of different Action
Codes (for example, Cancel
and Add) sent in the same
message.
Example:
Test1 Cancel
Test2 Add-on
Test3 Add-on
Test4 Cancel
In this example Test1 would not
be processed.
Container — If a coding system is in effect,
Type this is used to identify a
Identifier container type by
ContainerTypeCode.
Value. If not, this is used to
identify a container type by
ContainerType.
Name.

11314645 Rev. 02 31 / 150

ASTM 1394 Protocol Atellica Data Manager

Component Syntax Comment

Sample Type — If a coding system is in effect,
Identifier this is used to identify a sample
type by
SampleTypeCode.Value. If not,
this is used to identify a sample
type by SampleType.Name.
Request ^ ^ ^ Test ^ Request.DilutionCondition This is the dilution factor to be
^ Request.DilutionCoefficient forwarded to the instrument.
The Atellica DM software does
not perform calculations based
on this value.
Test Test.Name|TestCode.value| If a coding system is in effect,
this is used to identify a test by
TestCode.Value. If not, this is
used to identify a test by
Test.Name.
Priority S|A|* S (Stat)
A (ASAP)
Anything else is interpreted as
Routine.
NOTE: Priority can be
updated by the LIS in
subsequent workorder
downloads.
Action Code A | C | N | empty Add, cancel, new respectively.
Default is new.
Test Order C | SeqNo | * | Sample.Comment | —
Comment *<CR> LIS aliquotting requests must
Record be sent as sample order
comments in the following
format (up to a maximum of 8
secondary sample aliquot
requests in a single comment
record using repeat delimiters):
C|1||AliqTube^
<Aliquot sample Identifier
1>\AliqTube^
<Aliquot sample ID
2>\...\AliqTube^
<Aliquot sample Identifier
N>

32 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Component Syntax Comment

Result R | SeqNo | * ^ * ^ * ^ Test | Stored as the LIS previous result
Record Request.LISPrevResultValue | * | * | * | for the request in the
*|*|*|*| Atellica DM software.
Request.LISPrevResultTime<CR> Multiple previous patient
Maximum Record Length results for the same test can be
Test: 32 downloaded.
Request.LISPrevResultValue: 240 If previous result time is not
specified, then current time and
Request.LISPrevResultTime: 14
date is provided in the
(YYYYMMDDHHmmSS)
Atellica DM software.
Terminator L | SeqNo | * <CR> —
Record

Patient Result Upload

Component Syntax Comments

Header Record H | \ ^ & | | | | | | | | | | P | 1 | TimeStamp Field 9 contains the value
<CR> Atellica Data Manager
with the current version
of the Atellica DM
Software: ATELLICA DATA
MANAGER <version>
TimeStamp in
YYYYMMDDHHmmSS
format
Message HeaderRecord —
PatientInformationRecord [
PatientCommentRecord ]
TestOrderRecord [
TestOrderCommentRecord ] {
ResultRecord { ResultCommentRecord }
} TerminatorRecord

11314645 Rev. 02 33 / 150

ASTM 1394 Protocol Atellica Data Manager

Component Syntax Comments

Patient P | 1 | Patient.Identifier | | —
Information Patient.LastName ^ Patient.FirstName Patient.Sex record is
Record ^ Patient.MiddleName | | either M or F.
Patient.BirthDate | Patient.Sex | | | | | |
SpeciesIdentifier^Species.Name | | | | |
| | | | | | PatientLocation.Name <CR>
Maximum Record Length
Patient.Identifier: 40
Patient.LastName: 70
Patient.FirstName: 70
Patient.MiddleName: 70
Patient.Birthdate: 8 (YYYYMMDD)
Patient.Sex: 1
SpeciesIdentifier: 70
PatientLocationName: 70
Species — If a coding system is in
Identifier effect and a code for the
given sample type is
available, then the
SpeciesCode.Value is
transmitted. If not,
Species.Name is
transmitted.

Patient C | SeqNo | L | Patient.Comment | —

Comment G<CR>
Record

34 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Component Syntax Comments

Test Order O | 1 | Sample.Identifier | —
Record ^Sample.LastRack
^Sample.LastPosition | | Priority |
Sample.CreationTime |
Sample.CollectionTime | | * ^ * ^
Sample.ContainerTypeIdentifier | | | | |
| SampleTypeIdentifier |
Physician.Identifier | | | | | | | | | F <CR>
Maximum Record Length
Sample.Identifier: 32
Sample.LastRack: 70
Sample.LastPosition: 6
Priority: See comments
Sample.CreationTime: 14 The Priority field allows
(YYYYMMDDHHmmSS) Routine (R), ASAP (A),
SampleCollectionTime: 14 STAT (S) when no coding
(YYYYMMDDHHmmSS) system is active. If the
Sample.ContainerTypeIdentifier: 30 coding system is active,
maximum record length is
SampleTypeIdentifier: 30 30.
PhysicianIdentifier: 40
Sample ID Mandatory. Alphanumeric
code that uniquely
identifies the sample.
Maximum field length is
16 characters.

Sample Last The fields O4.1.2 and

Rack and Last O4.1.3, are the last rack
Position and position data values,
which are separated by
the caret symbol, ^, and
are uploaded to the LIS.

Priority R|A|S Routine, ASAP, or Stat

(Normal, High, or Very
high, respectively)

11314645 Rev. 02 35 / 150

ASTM 1394 Protocol Atellica Data Manager

Component Syntax Comments

Container — If a coding system is in
Type Identifier effect, this field identifies a
container type by
ContainerTypeCode.Value. If
not, this is used to identify a
container type by
ContainerType.Name.
Sample Type — If a coding system is in
Identifier effect and a code for the
given sample type is
available, then
SampleTypeCode.
Value is transmitted. If not,
SampleType.Name is
transmitted.
Test Order C | 1 | L | Sample.Comment | G <CR> Added only if a sample
Comment Maximum Record Length comment is available.
Record
Sample.Comment: 2500

36 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Component Syntax Comments

Result Record R | SeqNo | ^ ^ ^ Test ^ User.LoginName is sent
Result.DilutionCondition only if it is configured on
Result.DilutionCoefficient ^ ^ the system Options menu.
Aspect.Name^ Test.Datatype | The dilution coefficient is
Request.Value | | | Flag | | | | VISTA User the coefficient reported by
^ User.LoginName | the instrument for onboard
Result.AspirationTime | | dilution. This does not
Instrument.Name <CR> incorporate a manual
Maximum Record Length sample dilution because
Test: 32 the Atellica DM system
calculates results when a
ResultDilutionCondition: 16
manual dilution is ordered
ResultDilutionCoefficient: 19 at the Atellica DM user
AspectName: 30 interface.
TestDataType: 1 NOTE: The VISTA User
RequestValue: 240 field is used only for
results from a Dimension
Flag: 64
Vista® 1500 system.
UserLoginName: 128
These are the only
ResultAspirationTime: 14 supported TestDataType
(YYYYMMDDHHmmSS) strings: Numeric (N),
Instrument.Name: 60 Strings (S), Enumerated (E),
Image (I), Complex (C),
Graph (G).

If coding system is active,

the Instrument.Name
maximum record length is
30.
Test Test.name | TestCode If a coding system is in
Test.Value effect and a code for the
the given test is available,
Test.DataType
then TestCode.Value is
transmitted. If not,
Test.Name is transmitted.

Test.DataType N|S|E|I Test.Datatype

values include:
N = Numeric
S = String E = Enumerated
I = Image

11314645 Rev. 02 37 / 150

ASTM 1394 Protocol Atellica Data Manager

Component Syntax Comments

Flag * | Empty Asterisk if Instruments
flag is present.
NOTE: The actual flags
are sent as result
comment records. See
InstrumentFlag for
more details.

InstrumentFlag C | SeqNo | I | InstrumentFlag.Code | Instrument flags and

I<CR> request comments are
sent only if configured on
the system Options menu.

Request C | SeqNo | L | Request.Comment |

Comment G<CR>

Maximum Record Length

Request.comment: 2500

Terminator L|1<CR> —
Record

NOTE: Delimiters (|) are not included for trailing null fields. For example,
if the tenth field is the last field containing data, the record could terminate
after the tenth field, and would contain only nine delimiters.

38 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

QC Result Upload

Component Syntax Comment

Message HeaderRecord —
PatientInformationRecord
TestOrderRecord { ResultRecord {
ResultCommentRecord } }
TerminatorRecord
Header Record H|\^&||||||||||P|1| Field 9 contains the value
TimeStamp <CR> Atellica Data Manager with
the current version of the
Atellica DM Software:
ATELLICA DATA MANAGER
<version>.

TimeStamp in
YYYYMMDDHHmmSS format
Patient P | 1 <CR>
Information
Record
Test Order O | 1 | QCLot.Number | | | R | | | | | | Q
Record | | | | | | | | | | | | | | F <CR>
Maximum Record Length
QCLot.Number: 20

11314645 Rev. 02 39 / 150

ASTM 1394 Protocol Atellica Data Manager

Component Syntax Comment

Result Record R | SeqNo | ^ ^ ^ Test ^ Test.Datatype Test.Datatype value can be
| Value | | | | | | | | numeric or non-numeric.
QCResult.AssessmentTime | | The Atellica DM software can
Instrument.Name <CR> be configured to upload QC
Maximum Record Length results by lot, in which the
QCResult.AssessmentTime: 20 results for multiple
(YYYYMMDDHHmmSS) populations within a lot are
uploaded, or by population, in
which the results for a single
population within a lot are
uploaded.
NOTE: Upload by Lot is not
recommended when
uploading large amounts of
QC results per upload. When
uploading large amounts of
QC results, the value for the
Time out option on the
Translator window should be
increased.
Test Test.name | TestCode.Value If a coding system is in effect
and a code for the given test is
available, then
TestCode.Value is transmitted.
If not, Test.Name is
transmitted.
Test.DataType N|S|E|I Numeric, String, Enumerated,
or Image.
Result FlagCommentRecord |
Comment OtherComment
Record Record
Flag C | SeqNo | I | Flag | I <CR>
Comment
Record
Other C | SeqNo | L | QCResult.Comment | G
Comment <CR>
Record
Terminator L | 1 <CR> —
Record

40 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

LAS Status Upload

Component Syntax ASTM Field

Message HeaderRecord
ManufacturerRecord
TerminatorRecord
Header Record H|\^&||||||||||P|1| Timestamp in
TimeStamp <CR> YYYYMMDDHHmmss format
Manufacturer M | 1 | I | LasStatus ^ LAsStatus is either R or I.
SampleId ^ 1
Record
RegistrationDateTime | TrayId |
Position | Location1 ^
Location2 ^ Location3 ^
Location4 <CR>
Maximum Record Length
LAsStatus: 40
SampleID: 32
RegistrationDateTime: 14
(YYYYMMDDHHmmSS)
TrayID: 70
Position: 240
Location (1-4): 240 each
location
LAS Status I|L|R LAS Status I |L| R
I = Inlabbing
L = Left Equipment (Cold Storage)
R = Rack
Rack upload is not currently
supported in this upload message.
Sample ID
Registration Timestamp in
Date Time2 YYYYMMDDHHmmss format
Tray ID/Rack ID ID of the Tray
(ADVIA Automation) or Rack
(APTIO Automation).

11314645 Rev. 02 41 / 150

ASTM 1394 Protocol Atellica Data Manager

Component Syntax ASTM Field

Pos Position in tray. Position in tray is
identified by a letter/digit
combination:
A1 through J10
where the letters are
A–J and the numbers are
1–10
Position in rack is identified by a
numeric value (1-48)
LAS General ADVIA Automation: ADVIA Automation:
Area - CS CS = Cold Storage
Location 1 MT MT = Main Track
SC SC = Side Car
OT OT = Off Track
Aptio Automation: Node ID
Location 2 Shelf | Gate If General Area = CS3
(ADVIA Automation)
Then Location 2=Shelf

Floor (Aptio Automation)

If General Area = MT, SC, or OT
Then Location 2=Gate
Location 3 Door If General Area = CS3
Then Location 3=Door
Else Location 3 is blank
Location 4 Area Field If General Area = CS3 then
Location 4=Area
Else Location 4 is blank

42 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Notes Explanation
1
Sample ID If the Atellica DM system receives an end of route
message from a sample placed into a SIQ tray within
the Sample Manager before the inlabbing message is
uploaded to the LIS, the Atellica DM system uploads
the information from the end of route message, but
the SID is 'NO READ' instead of the actual SID.
2 Registration Registration date and time are not uploaded if a LAS
Date and Time update query initiates the generation of the sample
LAS information.
3 Location 2, 3, 4 Maximum possible field length is 240.

11314645 Rev. 02 43 / 150

ASTM 1394 Protocol Atellica Data Manager

Field-by-Field Descriptions

Message Header Record

Field Order Patient QC Result LAS Status

Download Result Upload to Upload to
from LIS Upload to LIS LIS
LIS
Record Type ID ‘H’ ‘H’ ‘H’ ‘H’
Delimiter Definition ‘|\^&’ ‘|\^&’ ‘|\^&’ ‘|\^&’
Message Control ID Empty Empty Empty
Access Password Empty Empty Empty
Sender Name or ID Empty Empty Empty
Sender Street Address Empty Empty Empty
Reserved Field Empty Empty Empty
Sender Telephone Empty Empty Empty
Number
Characteristics of Empty Empty Empty
Sender
Receiver ID Empty Empty Empty
Comment or Special Empty Empty Empty
Instructions
Processing ID ‘P’ ‘P’ ‘P’
Version No ‘1’ ‘1’ ‘1’
Date and Time of TimeStamp TimeStamp TimeStamp
Message
Format is
YYYYMMDDmmSS

44 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Patient Information Record

Field Workorder Patient Result QC

Downloaded from Uploaded to LIS Result
LIS Upload
to LIS
Record Type 'P’ 'P' 'P'
Sequence Number SeqNo 1 1
Practice Assigned Patient.Identifier Patient.Identifier Empty
Patient ID
Laboratory Assigned Patient.Identifier Patient.Identifier Empty
Patient ID
(Maximum length: 40)
Patient ID No. 3 Not Used Empty Empty
Patient Name Patient.LastName ^ Patient.LastName ^ Empty
(Maximum 70 Patient.FirstName Patient.First
characters each name) ^Patient.Middle Name
Name ^ Not used ^ ^Patient.Middle
Not used Name
Mother’s Maiden Name Not Used Empty Empty
Birthdate Patient.BirthDate Patient.BirthDate Empty
(Maximum length: 8 NOTE: If the
YYYYMMDD) patient birthdate
value downloaded
from the LIS
indicates that the
patient age is
greater than 150
years, the birthdate
value is not
accepted and the
patient birthdate is
not populated in the
Atellica DM system.
Patient Sex Patient.Sex Patient.Sex Empty
(Either M or F)
Patient Racethnic Origin Not Used Empty Empty
Patient Address Not Used Empty Empty
Reserved Field Not Used Empty Empty
Patient Telephone Not Used Empty Empty
Number
Attending Physician ID Not Used Empty Empty

11314645 Rev. 02 45 / 150

ASTM 1394 Protocol Atellica Data Manager

Field Workorder Patient Result QC

Downloaded from Uploaded to LIS Result
LIS Upload
to LIS
Special Field 1 SpeciesCode. SpeciesCode. Empty
(Maximum 70 Value Value
characters. If coding (No coding system: (No coding
system is active, up to Species.Name) system:
30 characters.) Species.Name)
^Species.Name
Special Field 2 Not Used Empty Empty
Patient Height Not Used Empty Empty
Patient Weight Not Used Empty Empty
Patient’s Known or Not Used Empty Empty
Suspected Diagnosis
Patient Active Not Used Empty Empty
Medications
Patients Diet Not Used Empty Empty
Practice Field No. 1 Not Used Empty Empty
Practice Field No. 2 Not Used Empty Empty
Admission and Not Used Empty Empty
Discharge Dates
Admission Status Not Used Empty Empty
Location PatientLocation. PatientLocation. Empty
(Maximum 70 Name Name
characters)
Nature of Alternative Not Used Empty Empty
Diagnostic Code and
Classifiers
Alternative Diagnostic Not Used Empty Empty
Code and Classification
Patient Religion Not Used Empty Empty
Marital Status Not Used Empty Empty
Isolation Status Not Used Empty Empty
Language Not Used Empty Empty
Hospital Service Not Used Empty Empty
Hospital Institution Not Used Empty Empty
Dosage Category Not Used Empty Empty

46 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Test Order Record

Field Workorder Patient Result QC Result

Downloaded Uploaded to LIS Upload to LIS
from LIS
Record Type ID 'O’ 'O' 'O'
Sequence Number SeqNo 1 1
Specimen ID Sample.Identifier Sample.Identifier QCLot.Number
(Maximum 32 (Maximum 32 (Maximum 20
characters) characters) characters)
Instrument Not used ^ Sample.LastRack ^ Empty
Specimen ID Sample.LastPosition
(Sample.LastRack:
maximum 70
characters)
(Sample.
LastPosition:
maximum 6
characters)
Universal Test ID ^^^ Empty Empty
TestIdentifier ^
Request.Dilution
Condition ^
Request.Dilution
Coefficient
Priority Priority Priority ‘R’
Requested/Ordered Not used Sample.Creation Empty
Date and Time Time
Specimen Collection Sample.Collection Sample.Collection Empty
Date and Time Time Time
(Format is
YYYYMMDDHH
mmSS)
Collection Volume Not used ^ Not Not used ^ Not used Empty
used ^ ^ ContainerType
ContainerType Code.Value
Code.Value (No coding
(No coding system:
system: ContainerType.
ContainerType. Name)
Name)
Collector ID Not used Empty Empty
Action Code A | C | N | empty Empty ‘Q’
Danger Code Not used Empty Empty

11314645 Rev. 02 47 / 150

ASTM 1394 Protocol Atellica Data Manager

Field Workorder Patient Result QC Result

Downloaded Uploaded to LIS Upload to LIS
from LIS
Relevant Clinical Not used Empty Empty
Information
Date/Time Specimen Not used Empty Empty
Received
Specimen Descriptor SampleType SampleType Empty
(Maximum length: Identifier Identifier
30)
Ordering Physician Physician. Physician. Empty
(Maximum length: Identifier Identifier
40)
Physician’s Not used Empty Empty
Telephone Number
User Field No. 1 Not used Empty Empty
Users Field No. 2 Not used Empty Empty
Laboratory Field No. Not used Empty Empty
1
Laboratory Field No. Not used Empty Empty
2
Date/Time Results Not used Empty Empty
Reported or Last
Modified
Instrument Charge to Not used Empty Empty
Computer System
Instrument Section Not used Empty Empty
ID
Report Type Not used 'F' 'F'
Reserved Field Not used Empty Empty
Location or Ward of Not used Empty Empty
Specimen Collection
Nosocomial Infection Not used Empty Empty
Flag
Specimen Service Not used Empty Empty
Specimen Institution Not used Empty Empty

48 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Result Record

Field Workorder Patient Result QC Result

Downloaded from Uploaded to LIS Uploaded to LIS
LIS
Result Upload to LIS ‘R’ 'R' 'R'
Sequence Number SeqNo SeqNo SeqNo
Universal Test ID ^^^ ^^^ ^^^
TestCode.Value TestCode.Value TestCode.Value
(No coding (No coding (No coding
system: Test.Name) system: Test.Name) system: Test.Name)
^ Result.Dilution ^ ^ ^ ^ Aspect.Name
Condition ^ (only without –c
Result.Dilution option)
Coefficient ^ ^ ^Test.DataType
Aspect.Name^Test.
DataType
Data or Measurement Request.LISPrev Request.StringValue QCResult.Value
Value ResultValue
(Maximum 240
characters)
Units Not used Empty Empty
Reference Ranges Not used Empty Empty
Result Abnormal Flags Not used Flag Empty
Nature of Abnormality Not used Empty Empty
Testing
Result Status Not used Empty Empty
Date of Change in Not used Empty Empty
Instrument Normative
Values or Units
Operator Not used ^ User.LoginName Empty
Identification
Date/Time Test Started Request.LISPrev Result.Aspiration QCResult.
(Maximum 14 ResultTime Time AssessmentTime
characters:
YYYYMMDDHHmmSS)
Date/Time Test Not used Empty Empty
Completed
Instrument Not used Instrument.Name Instrument.Name
Identification

11314645 Rev. 02 49 / 150

ASTM 1394 Protocol Atellica Data Manager

Patient Comment Record

Field Workorder Patient Result QC Result

Downloaded from Uploaded to LIS Uploaded to
LIS LIS
Record Type ID 'C’ 'C' Not Used
Sequence Number SeqNo SeqNo Not Used
Comment Source Not used 'L' Not Used
Comment Text Patient.Comment Patient.Comment Not Used
(Maximum length:
2500)
Comment Type Not used 'G' Not Used

Test Order Comment Record

Field Workorder Patient result QC Result

Downloaded from Uploaded to LIS Uploaded to
LIS LIS
Record Type ID 'C’ 'C' Not Used
Sequence Number SeqNo 1 Not Used
Comment Source Not used 'L' Not Used
Comment Text Sample.Comment Sample.Comment Not Used
(Maximum length:
2500)
Comment Type Not used 'G' Not Used

Result Comment Record

When uploading patient and QC results, the Atellica Data Manager
transmits flags as comment records.

Field Workorder Patient Result QC Result

Downloaded Uploaded to LIS Uploaded to
from LIS LIS
Record Type ID — 'C' Not Used
Sequence Number — SeqNo Not Used
Comment Source — 'I' or ‘L’ Not Used
Comment Text — Flag code or other Not Used
comment
Comment Type — 'I' or ‘G’ Not Used

50 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Request Information Record

Field Workorder Patient Result QC Result

Downloaded from Uploaded to LIS Uploaded to
LIS LIS
Record Type ID 'Q’ 'Q' Not Used
Sequence Number Not used Not used Not Used
Starting Range ID Not used Not used Not Used
Number
Ending Range ID Not used Not used Not Used
Number
Universal Test ID Not used Not used Not Used
Nature of Request Not used Not used Not Used
Time Limits
Beginning Request Not used Not used Not Used
Results Date and Time
Ending Request Not used Not used Not Used
Results Date and Time
Request Physician Not used Not used Not Used
Name
Requesting Physician Not used Not used Not Used
Telephone Number
User defined Field Not used Not used Not Used
No. 1
User defined Field Not used Not used Not Used
No. 2
Request Information Not used Not used Not Used
Status Codes

11314645 Rev. 02 51 / 150

ASTM 1394 Protocol Atellica Data Manager

Message Terminator Record

Field Order Patient QC Result LAS Status

Download Result Upload to Upload to
from LIS Upload to LIS LIS
LIS
Record Type ID ‘L’ ‘L’ ‘L’ ‘L’

Sequence Number SeqNo 1 1 1

Termination Code Not used ‘N’ ‘N’ ‘N’

Scientific Record

Field Workorder Patient Result QC Result

Downloaded Uploaded to LIS Uploaded to LIS
from LIS
1. Record Type ID 'S’ 'S' Not Used
2. Sequence Not used Not used Not used
Number
3. Analytical Not used Not used Not used
Method
4. Instrumentation Not used Not used Not used
5. Reagents Not used Not used Not used
6. Units of Not used Not used Not used
Measure
7. Quality Not used Not used Not used
Control
8. Specimen Not used Not used Not used
Descriptor
9. Reserved Field Not used Not used Not used
10. Container Not used Not used Not used
11. Specimen ID Not used Not used Not used
12. Analyte Not used Not used Not used
13. Result Not used Not used Not used
14. Result Units Not used Not used Not used
15. Collection Not used Not used Not used
Date and Time
16. Collection End Not used Empty Empty
Time
17. Result Date Not used Not used Not used
and Time

52 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Field Workorder Patient Result QC Result

Downloaded Uploaded to LIS Uploaded to LIS
from LIS
Analytical Not used Not used Not used
Preprocessing
Steps
Patient Not used Not used Not used
Diagnosis
Patient Not used Not used Not used
BirthDate
Patient Sex Not used Not used Not used
Patient Race Not used Not used Not used

Manufacturer Information Record

Field Order Patient QC Result LAS Status

Download Result Upload to Upload to LIS
from LIS Upload to LIS
LIS
1. Record ‘M’ ‘M’ ‘M’ ‘M’
Type ID
2. Sequence Not used SeqNo SeqNo 1
Number
3. User Not used Not used Not used I
specific
4. User Not used Not used Not used LasStatus ^
specific SampleId ^
Datetime
5. User Not used Not used Not used TrayId
specific
6. User Not used Not used Not used Position
specific
7. User Not used Not used Not used Location1 ^
specific Location2 ^
Location3 ^
Location4

11314645 Rev. 02 53 / 150

ASTM 1394 Protocol Atellica Data Manager

ASTM Transmission Examples

Patient sensitive information was made anonymous within the following
examples; therefore, checksums for records with anonymous information
may not be accurate.
In the examples, the Atellica DM software version has an x. In the released
software version, the x is a number of the software version on your system.

Message from LIS to Atellica Data Manager - LIS Aliquot

functionality
(One Secondary Sample Requested)
H|\^&||||||||||P|1
P|1|2833570|2833570||Vogt^Paul||19700929|M
O|1|9000039904|||R||||||A||||S|500186
C|1||AliqTube^9000039918|
O|2|9000039918||^^^7090^^\^^^7100^^\^^^7140^^\^^^43062^^\^^^
7150^^|R||||||A||||S|500186
L|1
Primary SID: 9000039904
Secondary SID: 9000039918

Message from LIS to Atellica Data Manager - LIS Aliquot

functionality
(Two Secondary Samples Requested in single message)
H|\^&||||||||||P|1
P|1|2833570|2833570||Vogt^Paul||19700929|M
O|1|9000039904|||R||||||A||||S|500186
C|1||AliqTube^9000039918\AliqTube^9000039919|
O|2|9000039918||^^^7090^^\^^^7100^^\^^^7140^^R||||||N||||S|500186
O|3|9000039919||^^^43062^^\^^^7150^^|R||||||N||||S|500186
L|1
Primary SID: 9000039904
Secondary SID 1: 9000039918
Secondary SID 2: 9000039919

54 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Message from LIS to Atellica Data Manager - LIS Aliquot

functionality
(Two Secondary Samples Requested with multiple messages)
H|\^&||||||||||P|1
P|1|2833570|2833570||Vogt^Paul||19700929|M
O|1|9000039904|||R||||||A||||S|500186
C|1||AliqTube^9000039918|
O|2|9000039918||^^^7090^^\^^^7100^^\^^^7140^^|R||||||N||||S|50018
6
L|1
H|\^&||||||||||P|1
P|1|2833570|2833570||Vogt^Paul||19700929|M
O|1|9000039904|||R||||||A||||S|500186
C|1||AliqTube^9000039919|
O|2|9000039919||^^^43062^^\^^^7150^^|R||||||N||||S|500186
L|1
Primary SID: 9000039904
Secondary SID 1: 9000039918
Secondary SID 2: 9000039919

11314645 Rev. 02 55 / 150

ASTM 1394 Protocol Atellica Data Manager

Workorder Download: LIS to the Atellica Data Manager,

New Workorders

Host action Atellica Data Manager response

Host: >ENQ< Atellica Data Manager: >ACK<
Host: Atellica Data Manager: >ACK<
>STX1H|\^&||||||||||P|1<CR>ETXBA<
CR><LF>
Host: Atellica Data Manager: >ACK<
>STX2P|1|1234560|||LASTNAME1^FI
RSTNAME1||19500101|M<CR>ETX5
F<CR><LF>
Host: Atellica Data Manager: >ACK<
>STX3O|1|1111111111||^^^10^\^^
^14^\^^^15^\^^^16^\^^^17^\^^^1
8^|R||20060516091500||||A|||||<CR>
ETXE6<CR><LF>
Host: >STX4P|2|1234561|||LAST Atellica Data Manager: >ACK<
NAME2^FIRST
NAME2||19500202|F<CR>ETX92<CR
><LF>
Host: Atellica Data Manager: >ACK<
>STX5O|1|2222222222||^^^fe^\^^
^trf^|R||20060516000000||||A|||||<C
R>ETX37<CR><LF>
Host: Atellica Data Manager: >ACK<
>STX6L|1|<CR>ETXBB<CR><LF>
Host: >EOT< Atellica Data Manager: >ACK<

Workorder Download: LIS to the Atellica Data Manager, Multiple

Previous LIS Results
The following workorder message orders four tests: ALB, TSH, ALT, and
HGB for Sample ID, MUL2.
Test ALB contains 3 previous LIS results, TSH contains 1 previous LIS result,
ALT contains 2 previous LIS results and HGB does not contain any previous
LIS results.
NOTE: You can view the displayed LIS Results at the LIS Previous Results
tab at the Request window, which you access by double-selecting the
request at the Review and Edit window.
H|\^&||||||||||P|1|

56 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

P|1|125|125||Lastname^Firstname^Mr.||19110707|M||||555
-1212|||||||||||||||||||||
O|1|MUL2||^^^ALB^NEAT^2|||||||A|||||||||ER||||||||||
R|1|^^^ALB|1.21||||||||20050101140000|
R|2|^^^ALB|1.22||||||||20040101152700|
R|3|^^^ALB|1.23||||||||20030101143457|
O|2|MUL2||^^^TSH|||||||A|||||||||ER||||||||||
R|1|^^^TSH|2.22||||||||20050101|
O|3|MUL2||^^^ALT|||||||A|||||||||ER||||||||||
R|1|^^^ALT|3.22||||||||20030303152700|
R|2|^^^ALT|3.23||||||||20030303143457|
O|4|MUL2||^^^HGB|||||||A|||||||||ER||||||||||
L|1F

Workorder Download: LIS to the Atellica Data Manager, Rerun

(action code “A” required)
Host: >ENQ<
Atellica Data Manager: >ACK<
Host: >STX1H|\^&||||||||||P|1<CR>ETXBA<CR><LF>
Atellica Data Manager: >ACK<
Host:
>STX2P|1|1234561|||LASTNAME^FIRSTNAME||19510101|M<CR>E
TXCA<CR><LF>
Atellica Data Manager: >ACK<
Host:
>STX3O|1|3332221111||^^^cl^|R||20060516143000||||A||||
|<CR>ETX26<CR><LF>
Atellica Data Manager: >ACK<
Host: >STX4L|1|<CR>ETX3D<CR><LF>
Atellica Data Manager: >ACK<
Host: >EOT<

Quality Control Result Upload: Atellica Data Manager to LIS

Atellica Data Manager: >ENQ<
Host: >ACK<

11314645 Rev. 02 57 / 150

ASTM 1394 Protocol Atellica Data Manager

Atellica Data Manager:

>STX1H|\^&||||||||||P|1|20060630132618<CR>ETXFC<CR><LF
>
Host: >ACK<
Atellica Data Manager:
>STX2P|1|||||||U<CR>ETXF8<CR><LF>
Host: >ACK<
Atellica Data Manager:
>STX3O|1|110302|||R||||||Q||||||||||||||F<CR>ETXEF<CR>
<LF>
Host: >ACK<
Atellica Data Manager:
>STX4R|1|^^^FolateBA^^^^^N|6.19||||||||20060630133504|
|Centaur_3<CR>ETX22<CR><LF>
Host: >ACK<
Atellica Data Manager: >STX5L|1|N<CR>ETX08<CR><LF>
Host: >ACK<
Atellica Data Manager: >EOT<

Quality Control Result Upload: Atellica Data Manager to LIS By

Lot
Atellica Data Manager:{ENQ}<
LIS:{ACK}<
Atellica Data Manager:{STX}1H|\^&|||||||Atellica Data
Manager 1.x.x.x|||P|1|20090626182922{CR}{ETX}32{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}2P|1|||||||U{CR}{ETX}F8{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}3O|1|40711|||||||||Q||||||||||||||F{CR}{ETX}73
{CR}<
LIS:{ACK}<

Atellica Data Manager:

{STX}4R|1|^^^COR^^^^DOSE^N|150.0||||||||20090626061033
||Centaur XP{CR}{ETX}B4{CR}<

58 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

LIS:{ACK}<
Atellica Data Manager:
{STX}5R|2|^^^COR^^^^DOSE^N|151.0||||||||20090626121033
||Centaur XP{CR}{ETX}B4{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}6R|3|^^^FSH^^^^DOSE^N|15.0||||||||20090626061033|
|Centaur XP{CR}{ETX}85{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}7R|4|^^^FSH^^^^DOSE^N|15.1||||||||20090626121033|
|Centaur XP{CR}{ETX}85{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}0R|5|^^^TSH^^^^DOSE^N|0.80||||||||20090626061033|
|Centaur XP{CR}{ETX}91{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}1R|6|^^^TSH^^^^DOSE^N|0.81||||||||20090626121033|
|Centaur XP{CR}{ETX}91{CR}<
LIS:{ACK}<
Atellica Data Manager:{STX}2L|1{CR}{ETX}3B{CR}<
LIS:{ACK}<
Atellica Data Manager:{EOT}<

Quality Control Result Upload: Atellica Data Manager to LIS By

Population
Atellica Data Manager:{ENQ}<
LIS:{ACK}<
Atellica Data Manager:{STX}1H|\^&|||||||ATELLICA DATA
MANAGER 1.x.x.x|||P|1|20090626183542{CR}{ETX}31{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}2P|1|||||||U{CR}{ETX}F8{CR}<
LIS:{ACK}<

11314645 Rev. 02 59 / 150

ASTM 1394 Protocol Atellica Data Manager

Atellica Data Manager:

{STX}3O|1|40711|||||||||Q||||||||||||||F{CR}{ETX}73
{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}4R|1|^^^COR^^^^DOSE^N|150.0||||||||20090626061033
||Centaur XP{CR}{ETX}B4{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}5R|2|^^^COR^^^^DOSE^N|151.0||||||||20090626121033
||Centaur XP{CR}{ETX}B4{CR}<
LIS:{ACK}<
Atellica Data Manager:{STX}6L|1{CR}{ETX}3F{CR}<
LIS:{ACK}<
Atellica Data Manager:{EOT}<

Atellica Data Manager:{ENQ}<

LIS:{ACK}<
Atellica Data Manager:{STX}1H|\^&|||||||ATELLICA DATA
MANAGER 1.x.x.x|||P|1|20090626183542{CR}{ETX}31{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}2P|1|||||||U{CR}{ETX}F8{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}3O|1|40711|||||||||Q||||||||||||||F{CR}{ETX}73
{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}4R|1|^^^FSH^^^^DOSE^N|15.0||||||||20090626061033|
|Centaur XP{CR}{ETX}81{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}5R|2|^^^FSH^^^^DOSE^N|15.1||||||||20090626121033|
|Centaur XP{CR}{ETX}81{CR}<
LIS:{ACK}<
Atellica Data Manager:{STX}6L|1{CR}{ETX}3F{CR}<

60 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

LIS:{ACK}<
Atellica Data Manager:{EOT}<
Atellica Data Manager:{ENQ}<
LIS:{ACK}<
Atellica Data Manager:{STX}1H|\^&|||||||ATELLICA DATA
MANAGER 1.x.x.x|||P|1|20090626183542{CR}{ETX}31{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}2P|1|||||||U{CR}{ETX}F8{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}3O|1|40711|||||||||Q||||||||||||||F{CR}{ETX}73
{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}4R|1|^^^TSH^^^^DOSE^N|0.80||||||||20090626061033|
|Centaur XP{CR}{ETX}91{CR}<
LIS:{ACK}<
Atellica Data Manager:
{STX}5R|2|^^^TSH^^^^DOSE^N|0.81||||||||20090626121033|
|Centaur XP{CR}{ETX}91{CR}<
LIS:{ACK}<
Atellica Data Manager:{STX}6L|1{CR}{ETX}3F{CR}<
LIS:{ACK}<
Atellica Data Manager:{EOT}<
Result Upload: Atellica Data Manager System to LIS
Atellica Data Manager: >ENQ<
Host: >ACK<
Atellica Data Manager:
>STX1H|\^&||||||||||P|1|20070612003418<CR>ETXF8<CR>
<LF>
Host: >ACK<
Atellica Data Manager:
>STX2P|1|A0000001|A0000001||LASTNAME^FIRSTNAME||192002
02|F||||||Human^Human|||||||||||93434<CR>ETXFA<CR><LF>
Host: >ACK<

11314645 Rev. 02 61 / 150

ASTM 1394 Protocol Atellica Data Manager

Atellica Data Manager:

>STX3O|1|X111111111|||R|20070611164759|20070611133000|
|^^Primary Tube||||||Serum||||||||||F<CR>ETX69<CR><LF>
Host: >ACK<
Atellica Data Manager:
>STX4R|1|^^^ALB^Neat^1.0^^^N|3.8||||||||20070611231253
||2402<CR>ETX59<CR><LF>
Host: >ACK<
Atellica Data Manager:
>STX5R|2|^^^CREA^Neat^1.0^^^N|1.5||||||||2007061123125
3||2402<CR>ETXA2<CR><LF>
Host: >ACK<
Atellica Data Manager:
>STX6R|3|^^^NA^Neat^1.0^^^N|146||||||||20070611231253|
|2402<CR>ETX4C<CR><LF>
Host: >ACK<
Atellica Data Manager:
>STX7R|4|^^^K^Neat^1.0^^^N|4.6||||||||20070611231253||
2402<CR>ETX07<CR><LF>
Host: >ACK<
Atellica Data Manager:
>STX0R|5|^^^CL^Neat^1.0^^^N|110||||||||20070611231253|
|2402<CR>ETX47<CR><LF>
Host: >ACK<
Atellica Data Manager: >STX1R|6|^^^HEMO^Neat^1.0^^^E|-
||||||||20070611231253||2402<CR>ETX71<CR><LF>
Host: >ACK<
Atellica Data Manager: >STX2R|7|^^^ICTE^Neat^1.0^^^E|-
||||||||20070611231253||2402<CR>ETX6F<CR><LF>
Host: >ACK<
Atellica Data Manager: >STX3R|8|^^^LIPE^Neat^1.0^^^E|-
||||||||20070611231253||2402<CR>ETX76<CR><LF>
Host: >ACK<
Atellica Data Manager: >STX4L|1|N<CR>ETX09<CR><LF>
Host: >ACK<
Atellica Data Manager: >EOT<

62 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Result Upload: Atellica Data Manager System to LIS, ID

Assay Algorithm Result
Atellica Data Manager: >ENQ<
Host: >ACK<
Atellica Data Manager:
>STX1H|\^&||||||||||P|1|20080501195056<CR>ETX00<CR><LF
>
Host: >ACK<
Atellica Data Manager:
>STX2P|1|Z111111|Z111111||LASTNAME^FIRSTNAME||19500101
|M||||||Human^Human<CR>ETX15<CR><LF>
Host: >ACK<
Atellica Data Manager:
>STX3O|1|G123456789|^0057^C||R|20080501195020|||||||||
||||||||||F<CR>ETX27<CR><LF>
Host: >ACK<
Atellica Data Manager:
>STX4R|1|^^^HCV^^^^INDX^N|0.8||||||||20060412125859||
Centaur_1<CR>ETX2A<CR><LF>
Host: > ACK <
Atellica Data Manager: >STX5C|1|L|Manual Validation
Required|G<CR>ETX26<CR><LF>
Host: > ACK <
Atellica Data Manager:
>STX6R|2|^^^HCV^^^^RLU^S|800||||||||20060412125859||
Centaur_1<CR>ETXF4<CR><LF>
Host: > ACK <
Atellica Data Manager:
>STX7R|3|^^^HCV^^^^COFF^S|1.0||||||||20060412125859||
Centaur_1<CR>ETX18<CR><LF>
Host: > ACK<
Atellica Data Manager:
>STX0R|4|^^^HCV^^^^INTR^S|Equiv||||||||20060412125859|
|Centaur_1<CR>ETXAC<CR><LF>
Host: >ACK<
Atellica Data Manager:
>STX1R|5|^^^HCV_RVT^^^^^S|N<CR>ETX09<CR><LF>
Host > ACK <

11314645 Rev. 02 63 / 150

ASTM 1394 Protocol Atellica Data Manager

ATELLICA DATA MANAGER:

>STX2R|6|^^^HCV_INTR^^^^^E|EQ<CR>ETX86<CR><LF>
Host: > ACK <
ATELLICA DATA MANAGER:
>STX3R|7|^^^HCV_1_EQ^^^^^S|Y<CR>ETX42<CR><LF>
Host: > ACK <
ATELLICA DATA MANAGER:
>STX4R|8|^^^HCV_2_EQ^^^^^S|Y<CR>ETX45<CR><LF>
Host: >ACK<
ATELLICA DATA MANAGER:
>STX5R|9|^^^HCV_3_R^^^^^S|Y<CR>ETX04<CR><LF>
Host: > ACK <
ATELLICA DATA MANAGER: >STX6L|1|N<CR>ETX09<CR><LF>
Host: >ACK<
ATELLICA DATA MANAGER: >EOT<

EHIV and CHIV Result Upload Examples

NOTE: In the following sections, any references to the ADVIA Centaur
system also includes the ADVIA Centaur® XP system, unless otherwise
stated.
These examples show the records transmitted to an ASTM LIS with the
options set for uploading the validation user and instrument flags.
Atellica DM is configured to accept all ADVIA Centaur result aspects: INDX,
INTR, RLU, COFF.
NOTE: If these aspects are not defined for the instrument in Atellica DM,
they are not sent to the LIS upload data stream.

EHIV Testing Examples

Example 1: EHIV Reactive Result Upload

In this example, the test result is reactive.
The result lines in the data stream are indicated as R|.
Result 1 shows the Index value received from the ADVIA Centaur system
as 2.43.
Result 2 shows the cutoff value as an index of 1.00.
Result 3 shows the interpretive result received from the ADVIA Centaur
system as React.
Result 4 indicates the RLU units as 79985.

64 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

Result 5 shows the interpretive result generated by Atellica DM as R.

Results 6, 7, 8, and 9 are the indicator tests generated from Atellica DM.
NOTE: When you use partial upload, one or all of the indicator tests may
upload in a separate result message before the instrument results upload.
H|\^&||||||||||P|1|20061006134242
P|1|||||||U||||||Human^Human
O|1|SAMPLE1|||R|20061006134203|||||||||||||||||||F
R|1|^^^EHIV^^^^INDX^N|2.43|||*||||^batch|2006100619112
3||Centaur_2
C|1|I|Ctrl Bracketed|I
R|2|^^^EHIV^^^^COFF^S|1.00|||||||^batch|20061006191123
||Centaur_2
R|3|^^^EHIV^^^^INTR^S|React|||||||^batch|2006100619112
3||Centaur_2
R|4|^^^EHIV^^^^RLU^S|79985|||||||^batch|20061006191123
||Centaur_2
R|5|^^^EHIV_INTR^^^^^E|R|||||||^batch
R|6|^^^EHIV_CMPLTE^^^^^S|Y|||||||^batch
R|7|^^^EHIV_1_DR^^^^^S|Y|||||||^batch
R|8|^^^EHIV_2_NR^^^^^S|Y|||||||^batch
R|9|^^^EHIV_3_R^^^^^S|Y|||||||^batch
L|1|N

Example 2: EHIV Non-Reactive Result Upload

In this example, the test result is non-reactive.
The result lines in the data stream begin with R|.
Result 1 shows the Index value received from the ADVIA Centaur system
as < 0.05.
Result 2 shows the cutoff values as an index of 1.00.
Result 3 shows the interpretive result received from the ADVIA Centaur
system as NR.
Result 4 indicates the RLU units as 9356.
Result 5 shows the interpretive result generated by Atellica DM as NR.
Results 6, 7, 8, and 9 are the indicator tests.

11314645 Rev. 02 65 / 150

ASTM 1394 Protocol Atellica Data Manager

NOTE: When you use partial upload, one or all of the indicator tests may
upload in a separate result message before the instrument results upload.
H|\^&||||||||||P|1|20061006134701
P|1|||||||U||||||Human^Human
O|1|SAMPLE2|||R|20061006134633|||||||||||||||||||F
R|1|^^^EHIV^^^^INDX^N|<0.05|||*||||^batch|200610061915
53||Centaur_2
C|1|I|<|I
C|2|I|Below Check|I
C|3|I|Ctrl Bracketed|I
C|4|I|Repeated|I
R|2|^^^EHIV^^^^COFF^S|1.00|||||||^batch|20061006191553
||Centaur_2
R|3|^^^EHIV^^^^INTR^S|NR|||||||^batch|20061006191553||
Centaur_2
R|4|^^^EHIV^^^^RLU^S|9356|||||||^batch|20061006191553|
|Centaur_2
R|5|^^^EHIV_INTR^^^^^E|NR|||||||^batch
R|6|^^^EHIV_CMPLTE^^^^^S|Y|||||||^batch
R|7|^^^EHIV_1_DR^^^^^S|Y|||||||^batch
R|8|^^^EHIV_2_NR^^^^^S|Y|||||||^batch
R|9|^^^EHIV_3_NR^^^^^S|Y|||||||^batch1L|1|N

CHIV Testing Examples

CHIV Examples of Result Upload to an ASTM 1394 LIS

NOTE: In the following sections, any references to the ADVIA Centaur
system also includes the ADVIA Centaur XP system, unless otherwise
stated.
These examples show the records transmitted to an ASTM LIS with the
options set for uploading the validation user and instrument flags.
Atellica DM is configured to accept all ADVIA Centaur result aspects: INDX,
INTR, RLU, COFF.
NOTE: If these aspects are not defined for the instrument in Atellica DM,
they are not sent to the LIS upload data stream.
Example 1: Reactive Result Upload
In this example, the test result is reactive.

66 / 150 11314645 Rev. 02

Atellica Data Manager ASTM 1394 Protocol

The result lines in the data stream are indicated as R|.

Result 1 shows the Index value received from the ADVIA Centaur system
as 2.43.
Result 2 shows the cutoff value as an index of 1.00.
Result 3 shows the interpretive result received from the ADVIA Centaur
system as React.
Result 4 indicates the RLU units as 79985.
Result 5 shows the interpretive result generated by Atellica DM as R.
Results 6, 7, 8, and 9 are the indicator tests generated from Atellica DM.
NOTE: When you use partial upload, one or all of the indicator tests may
upload in a separate result message before the instrument results upload.
H|\^&|||||||ATELLICA DM 1.x.x.x|||P|1|20110327164605
P|1|||||||U||||||Human^Human
O|1|SAMPLE1|||R|20110327112203|||||||||||||||||||F
R|1|^^^CHIV^^^^INDX^N|2.43|||||||^batch|20110327154341
||Centaur_2
R|2|^^^CHIV^^^^COFF^S|1.00|||||||^batch|20110327154341
||Centaur_2
R|3|^^^CHIV^^^^INTR^S|React|||||||^batch|2011032715434
1||Centaur_2
R|4|^^^CHIV^^^^RLU^S|79985|||||||^batch|20110327154341
||Centaur_2
R|5|^^^CHIV_INTR^^^^^E|R|||||||^batch
R|6|^^^CHIV_CMPLTE^^^^^S|Y|||||||^batch
R|7|^^^CHIV_1_DR^^^^^S|Y|||||||^batch
R|8|^^^CHIV_2_NR^^^^^S|Y|||||||^batch
R|9|^^^CHIV_3_R^^^^^S|Y|||||||^batch
L|1|N

Example 2: CHIV Non-Reactive Result Upload

In this example, the test result is non-reactive.
The result lines in the data stream begin with R|.
Result 1 shows the Index value received from the ADVIA Centaur system
as < 0.05.
Result 2 shows the cutoff values as an index of 1.00.

11314645 Rev. 02 67 / 150

ASTM 1394 Protocol Atellica Data Manager

Result 3 shows the interpretive result received from the ADVIA Centaur
system as NR.
Result 4 indicates the RLU units as 9356.
Result 5 shows the interpretive result generated by Atellica DM as NR.
Results 6, 7, 8, and 9 are the indicator tests.
NOTE: When you use partial upload, one or all of the indicator tests may
upload in a separate result message before the instrument results upload.
H|\^&|||||||ATELLICA DM 1.x.x.x|||P|1|20110327164707
P|1|||||||U||||||Human^Human
O|1|SAMPLE2|||R|20110327112209|||||||||||||||||||F
R|1|^^^CHIV^^^^INDX^N|<0.05|||*||||^batch|201103271523
31||Centaur_2
C|1|I|<|I
C|2|I|Below Check|I
C|3|I|Repeated|I
R|2|^^^CHIV^^^^COFF^S|1.00|||||||^batch|20110327152331
||Centaur_2
R|3|^^^CHIV^^^^INTR^S|NR|||||||^batch|20110327152331||
Centaur_2
R|4|^^^CHIV^^^^RLU^S|9356|||||||^batch|20110327152331|
|Centaur_2
R|5|^^^CHIV_INTR^^^^^E|NR|||||||^batch
R|6|^^^CHIV_CMPLTE^^^^^S|Y|||||||^batch
R|7|^^^CHIV_1_DR^^^^^S|Y|||||||^batch
R|8|^^^CHIV_2_NR^^^^^S|Y|||||||^batch
R|9|^^^CHIV_3_NR^^^^^S|Y|||||||^batch
L|1|N

68 / 150 11314645 Rev. 02

5 Technidata LMX 6.0

This section describes the Technidata protocol used for the communication
link between the Atellica Data Manager and a laboratory information
system (LIS) or host computer.
This section is intended for the information systems professional
responsible for connecting the Atellica DM system and your host
computer. Please contact your local technical support provider or
distributor if you need additional information.
The Atellica DM software supports communication with the Technidata.
LMX LIS using FTP as low level protocol and ASTM 1238 as high level
protocol.

Overview
The LMX communication link allows the LIS to transmit workorders
and multiple previous patient results for the same test to the
Atellica DM software and to accept QC and patient test results transmitted
from the Atellica DM software.
The LIS initiates sending patient workorder information to the
Atellica DM system before each sample run. The information will be parsed
and stored in the system for download to the instrument.
The Atellica DM system can be configured to automatically transfer
available results to the host or manually transfer results to permit the
operator time to review the data and release the sample results.

Translator Specific Options

In the Atellica DM system, the driver for the Technidata LMX translator is
the lmxs driver.

11314645 Rev. 02 69 / 150

Technidata LMX 6.0 Atellica Data Manager

The translator specific options are the following:

-b <Order file prefix> The -b <Order file prefix> option specifies the
prefix of the order file name.
The default setting is DEM.
Expected workorder file names are <Order file
prefix><SeqNo>.AST.
<SeqNo> is a configurable sequence number.
Files are processed on receipt by the
Atellica DM system and are deleted afterwards.
-i <incoming file The -i option specifies the directory that is used
directory> to read the incoming workorders. In most cases
this is the FTP root (C:\inetpub\ftproot) or a
subdirectory of it. This is mandatory.
-l The -l option specifies that the patient location
is stored in the OBR.19 field. If it is not set, the
default location is P.26.
-r <Receiver ID> The -r option specifies the receiver ID that will
be in the ASTM message (field 7.10). The
default value is 38-1.

-s <Sender ID> The -s option specifies This specifies the sender

ID that will be in the ASTM message (field 7.5).
The default value is LMXS.
-t <Sleep time> The -t option specifies the number of seconds
the translator will wait between two
consecutive checks for new incoming
workorder files. The default value is 30.

-v <Protocol version> The -v option specifies the protocol version that

will be in the ASTM message (field 7.13). The
default value used for LMX communication is
A2.2.

70 / 150 11314645 Rev. 02

Atellica Data Manager Technidata LMX 6.0

Translator Generic Export Options

LMX 6.0 and later export options are not backward compatible with
previous versions. You enter the following translator generic export
options in the Specific Options field.

[-O <Value>] Export directory.

Result files will be placed in this location.
[-E <Value>] Export file pattern. Subdirectories can be specified
and are created automatically, except when '-U' is
specified.
For example, {Date:%Y}/{Date:%m%d}/
{Time:%H%M%S}-{#*}.txt
Default is 'RES{###}.AST'

Possible patterns:
{DateTime[:format]}
Standard format: %Y%m%d%H%M%S
{Date[:format]}
Standard format: %Y%m%d
{Time[:format]}
Standard format: %H%M%S
{#*}
Counter, unlimited in length, starts from 1
{#..#}
Where a limited amount of '#' characters can be
specified, the target Counter will be of the same
length.
e.g. {####} will start from 0001, 9999 is the last
allowed value
NOTE: The counter increments if the rest of the
filename is not unique. For unique filenames, for
example, filenames based on time, the counter is
set to 1.
If Counter exceeds the amount of allowed digits, an
error is raised, the results are not output to file, but
the driver does not exit.

11314645 Rev. 02 71 / 150

Technidata LMX 6.0 Atellica Data Manager

[-E <Value>] seq[:format]

(cont’d) Similar to {#...#} format, however, the next Counter
is always equal to the last one found + 1.
Standard format: - (starts from 1)
Allowed format: 9.......9'', where the amount of 9-
digits specify the maximum counter length. For
example, seq:9999 starts from 0001.
If Counter exceeds the amount of allowed digits
(for example, after the counter has reached 9999
when seq:9999 is specified), the counter does not
reset. An error is raised and the results are not
output to file, but the driver does not exit.
Examples of result file format: for a date of 04/05/
2008 and time = 14:03:51
-O C:\LMX -E{Date:%Y}/{Date:%m%d}/
{Time:%H%M%S}-{#*}.txt
Filename =140351-1.txt in the folder
C:\LMX\2008\0405\
-O C:\LMX -E {DateTime:%Y%m%d%H%M%S}-
{SEQ:-}.AST
Filename = 20080503135944-1.AST in the C:\LMX
folder

72 / 150 11314645 Rev. 02

Atellica Data Manager Technidata LMX 6.0

[-U <List>] Use FTP when storing files on the export directory:
'Protocol=FTP',''Host='<IP Address>'or
‘<Hostname’>,','['Service='<Value>]','
['User='<Value>]','['Password='<Value>]','
['TransferMode='<'Binary' | 'Ascii'>]','
['ConnectionMode='<'Passive' | 'Active'>]','
['TimeOut='<Value (milliseconds)>]

Default service is 'ftp'

Default user is 'anonymous'. Password not needed
in case of user 'anonymous', ',' characters in a
password should be specified as '~,'.
Default transfer mode is 'Binary'.
Default connection mode 'Passive'.
Default time-out is 0 (no time-out).

For example: -U
Protocol=FTP,Host=172.31.21.22,
TransferMode=Ascii
NOTE: ConnectionMode Passive -> FTP server
opens FTP dataport (FTP PASV)
ConnectionMode Active -> FTP client opens FTP
dataport (FTP PORT)
When a firewall is installed in between FTP client
and server, use Passive, as in this case, the FTP
client session always takes the initiative.
[-Y <Value> ] Storage directory for temporary files.
If unspecified, 'Root-Directory'/tmp is assumed.
On UNIX/Windows platforms, the terminating '/'
character is mandatory.
When using -U FTP, this option is mandatory and
the directory must be specified. For example,
D:\Atellica Data Manager\tmp

11314645 Rev. 02 73 / 150

Technidata LMX 6.0 Atellica Data Manager

[-J <List>] File store method.

<STORE_NORMAL |
STORE_TRUNCATE' |
STORE_APPEND'[',Separators='<Separators>] |
STORE_OKFILE'[',Extension='<OKFileExtension>]>

'STORE_NORMAL'
If the target file exists, an error is generated.
If a file unique making pattern {{#...#} or {seq}) is
specified, a new file is created each time.

'STORE_APPEND'[',Separators='<Separators>]
The target file is appended.
NOTE: The file is appended only if the -E option
does not contain the unique marking patterns
{{#...#} or {seq}). If these patterns are used then
STORE_APPEND is interpreted as STORE_NORMAL.
<Separators> = semi-colon-separated list of
decimal-coded numbers.
Separators added to the target file in between data
appends.
For example, '-J STORE_APPEND,Separators=13;10'
adds a carriage return and a new line between
target file data appends.
STORE_OKFILE'[',Extension='<OKFileExtension>]
The target file is accompanied by an OK file with
the same file name, except for the extension.
When only '-J STORE_OKFILE' is specified, extension
'ok' is assumed.
NOTE: When the -E option specifies a file unique
making pattern ({#...#} or {seq}), then
'STORE_APPEND' is interpreted as
'STORE_NORMAL'.
Default is '-J STORE_NORMAL'

74 / 150 11314645 Rev. 02

Atellica Data Manager Technidata LMX 6.0

Examples of Specific Options

FTP
-i c:\inetpub\ftproot -O Export\ -Y D:\atellica data
manager\tmp\ -U Protocol=FTP,Host=x.x.x.x -J
STORE_NORMAL
where
• Export is a sub-folder on the FTProot folder on the LMX host
• Host =x.x.x.x - replace with the IP address of the LMX host

Shared folder:
-i \\<servername>\<Sharename>\ -O
\\<servername>\<Sharename>\
where \\<servername>\<Sharename>\ defines a shared folder.
NOTE: If you are using a UNIX/LINUX server, verify the proper technique
for specifying addresses.

File Transfer
Communication with the LMX is handled by two programs:
• The LMX translator processes all workorder files and creates results
files.
• The File Transmitter is a separate program, running as a Windows
process, that takes care of the FTP file transfer over the network. It is
not needed when a shared network volume is being used.
The File Transmitter is installed by the Atellica DM installation program. No
configuration is needed afterwards. Specify the –U Protocol=FTP
parameter for the LMX translator. The -i parameter must specify the FTP
folder on the Atellica DM server where the files are put by the LMX. If files
must be put in a specific subdirectory of the LMX FTP server, you should
also specify the -O <Subdirectory name>\ parameter.
NOTE: The “\” after the subdirectory name in the -O <Subdirectory
name>\ parameter is required.
File naming conventions:
• Workorder files: DEMxxx.AST
The prefix, DEM by default, is configurable using the -b switch. xxx is a
configurable sequence number.
• Result files: RESxxx.AST
The prefix, RES by default, can be configured using the -E switch.

11314645 Rev. 02 75 / 150

Technidata LMX 6.0 Atellica Data Manager

Files are processed on receipt by the Atellica DM system and deleted

afterwards. Sequence numbers of the result files are reset each time the
translator is restarted, so ensure that all files are processed on the LMX
before restarting the translator.
The Atellica DM software generates a .OK file after the result file has been
fully transferred or created. Incoming .OK files for the workorder files can
be used, but the Atellica DM software does not use the contents of the .OK
file to verify that the workorder file is completely downloaded. Instead, the
Atellica DM software waits 10 seconds after the last modification time of
the workorder file to process the workorder file.
NOTE: A new workorder for the same patient can be processed at the LIS
before the previous results are validated and uploaded. It is possible that
the previously displayed results are not the most recently validated results.

FTP Error for LMX Transmission

If an error stating
The computer is disconnected from the network
displays on the screen or in the LMX translator log, it may be caused by
Internet Explorer being set to work offline. You can deselect the option
using the Internet Explorer File menu.

Specimen Receipt Information with the Technidata LMX Protocol

Specimen receipt (inlabbing) information such as SID, read date and time,
and check-in location are transmitted from the Atellica DM system to the
LIS in the Order Segment record of the Patient Result Upload message.
For information on the grammar of the inlabbing information contained
within a result file and an example of the inlabbing transmission to the LIS,
refer to Chapter 6, Specimen Receipt Information and Archive Location
Transmission.

76 / 150 11314645 Rev. 02

Atellica Data Manager Technidata LMX 6.0

Action Codes
The behavior of the action code in OBR record 12 is as follows:

Action Action
Code
R 1. If sample available for different patient: unmatched
patient error. If not:
2. Rerun matching uploaded database requests.
3. Delete database requests with status < UPL that are not
in the order.
4. Add requests that are in the order but not in the
database.
5. If sample ID does not exist in the database, add new
sample.
S 1. If sample available for different patient: unmatched
patient error
2. Omit all database requests with status < Review.
NOTE: The Action Code field should not be blank.

Specific Action Code Behavior

The behavior depends on the setting of the Full Sample Download option
on the LIS channel in the Atellica DM system by your local Siemens
representative. There are 2 possible actions the Atellica DM system can
take when receiving a workorder using the LMX protocol:
• Full Sample Download Enabled: When the Atellica DM system
software receives an updated workorder from the LIS using the LMX
communication protocol, any current result in the Atellica DM system
with a status of REV (Review) or VAL (Validated) will be omitted if these
requests are absent from the updated workorder. Results with a status
of UPL (Uploaded) are not affected.
• Full Sample Download Disabled: When the Atellica DM software
receives an updated workorder from the LIS using the LMX
communication protocol, tests that are present in Atellica DM system
but not present in the workorder are not affected.

11314645 Rev. 02 77 / 150

Technidata LMX 6.0 Atellica Data Manager

Mixed Action Codes

Do not mix action codes in the same message. The Atellica DM system
software does not support the receipt of different action codes (for
example, Cancel and Add) sent in the same message.
Test1 Cancel
Test2 Add-on
Test3 Add-on
Test4 Cancel
In this example, Test1 would not be processed.
NOTE: For LMX, a Cancel action code causes all requests in the sample in
status Pending, Rerun, and Scheduled to be omitted. The cancel action is
not limited to the test name in the order.

Grammar
• The grammar, which provides a description of the ASTM interface, is
formally described in the tables below. Each table row represents a
grammar rule. The first rule defines the element “Message” in terms of
smaller elements. Further down the table the smaller elements are
defined, and so on.
• Elements in italics must be translated (using another rule, unless
obvious).
• Elements in bold must be used literally.
• Vertical | bars denote alternative choices.
• Square brackets [ ] denote optional inclusion.
• Curly braces { } denote optional repeated inclusion.
• Parentheses ( ) denote grouping.
• Asterisks * denote ignored strings.

78 / 150 11314645 Rev. 02

Atellica Data Manager Technidata LMX 6.0

Workorder Download

Component Syntax Comment

Message HeaderSegment { —
PatientSegment {
PatientCommentSegment }
{ Order Segment {
OrderCommentSegment } [
ResultSegment ] } }
TerminatorSegment
Header H|^~\&|*|*|*|*| —
Segment ORM | * | * | * | <CR>
Patient P | SeqNo | Patient.Identifier NOTE: If the patient
Segment | * | * | Patient.LastName ^ birthdate value
Patient.FirstName ^ downloaded from the LIS
Patient.MiddleName ^ * ^ * indicates that the patient
^ * | * | Patient.Birthdate | age is greater than 150
Patient.Sex | * | * | * | * | * | years, the birthdate value
*|*|*|*|*|*|*|*|*| is not accepted and the
*|*| patient birthdate is not
Patient.Location.Name | * | populated in the
* | <CR> Atellica DM system.
Patient Patient Identifier (PID) is
Identifier limited to 40 characters.
(P3)
Patient.Identifier1
populates field P3.
Patient.Identifier2
populates field P4.
Patient P3 and P4 must be
Identifier consistent. If P3 is not
(P4) specified, then P4 will be
taken as the patient ID. P3
will be checked first.
Patient Patient Last Name, First
Name Name, and Middle Name
are restricted to 70
characters.
Patient The Patient Location from
Location the patient record is used if
no Patient Location is
specified in the order
record.

11314645 Rev. 02 79 / 150

Technidata LMX 6.0 Atellica Data Manager

Component Syntax Comment

Patient C | SeqNo | L | —
Comment Patient.Comment | <CR>
Segment
Order OBR | SeqNo | This is the dilution factor to
Segment Sample.Identifier ^ * | * | be forwarded to the
Test ^ * ^ L ^ * ^ instrument. The Atellica DM
Request.DilutionCondition ^ software does not perform
Request.DilutionCoefficient calculations based on this
| Priority | * | value.
Sample.CollectionTime | * |
* | * | ActionCode | * | * | * |
*|*|*|*|
PatientLocation.Name * | * |
*|*|*|
Test — If a coding system is in
effect, this is used to
identify a test by
TestCode.Value. If not, this
is used to identify a test by
Test.Mnemonic.
Priority — S = Stat
A = As Soon As Possible
Anything else is interpreted
as Routine.
NOTE: Priority can be
updated by the LIS in
subsequent workorder
downloads.
Action Code S|R Refer to Action Codes on
page 77.
Order C | SeqNo | L | —
Comment Sample.Comment | <CR>
Segment
Result OBX | SeqNo | * |Test | * | Previous result: Field 12
Segment Request.LISPrevResultValue (status) must be set to A
|*|*|*|*|*|A| (Anteriority). Time of day
Request.LISPrevResultTime | defaults to 00:00:00 if not
* | * | * | * | <CR> specified.
Terminator L | * | * | * | * | <CR> —
Segment

80 / 150 11314645 Rev. 02

Atellica Data Manager Technidata LMX 6.0

Patient Result Upload

Component Syntax Comment

Message HeaderSegment —
PatientSegment
[ PatientCommentSegment
] OrderList
TerminatorSegment
Header H | ^ ~ \ & | | | SenderId | | —
Segment ORM | | | | ReceiverId | | |
Version | TimeStamp | <CR>
Sender ID Id ^ ATELLICA DM ID as specified in the -s
startup option of the
translator. The default
setting is lmxs.
Receiver ID Id ^ LIS ID as specified in the -r
startup option of the
translator. The default
setting is 38-1.
Version — As specified in the -v startup
option of the translator. The
default setting for LMX
communication is A2.2.
Time Stamp — Date and time the result
was sent. Format:
YYYYMMDDHHMMSS.
Patient P | 1 | | Patient.Identifier | | Patient.Identifier1
Segment Patient.LastName ^ populates field P3.
Patient.FirstName ^ Patient.Identifier2
Patient.MiddleName | | populates field P4.
Patient.BirthDate |
Patient.Sex | | | | | | | | | | | | | |
| | | Ward ^ Room | | | <CR>
Patient C | SeqNo | L | —
Comment Patient.Comment | <CR>
Segment
Order List Order { Order } —
Order OrderSegment —
[ OrderCommentSegment ]
{ ResultSegment
{ResultCommentSegment }
}

11314645 Rev. 02 81 / 150

Technidata LMX 6.0 Atellica Data Manager

Component Syntax Comment

Order OBR | SeqNo |
Segment SampleIdentifier ^
OrderId | | Test ^ ^ L |
Priority | | | | | | ActionCode |
| | | | | | | | | | | | | <CR>

Priority R|A|S R= Routine

A = As soon as possible
S = Stat
Action Code Blank for patient result
uploads.
Q for QC result uploads
Order C | 1 | L | Sample.Comment | Added only if a sample
Comment <CR> comment is available.
Segment
Result OBX | SeqNo | ResultType | The dilution coefficient is
Segment Test ^ ^ ^ ^ the coefficient reported by
DilutionCondition ^ the instrument for
DilutionCoefficient | | Value onboard dilution. This
| | | Flag | | | Status | does not incorporate a
AvailabilityTime | | | | manual sample dilution
Operator |<CR> because the
Atellica DM system
calculates results when a
manual dilution is ordered
at the Atellica DM user
interface.
AvailabilityTime
corresponds to the
Aspiration time of the
result.
Result Type CE | NM | ST CE = Coded Entry for
enumerated tests.
NOTE: For enumerated
test results, choice codes
must be synchronized
between LMX and the
Atellica DM software.
NM = Numeric Result.
ST = Alphanumerical Result

82 / 150 11314645 Rev. 02

Atellica Data Manager Technidata LMX 6.0

Component Syntax Comment

Test — If a coding system is in
effect and a code for the
given test is available, then
TestCode.Value is
transmitted. If not,
Test.Mnemonic is
transmitted.
Flag * | <empty> Asterisk if Instruments flag
is present.
NOTE: The actual flags
are sent as result comment
records. See Result
Comment Segment for
more details.
Result C | SeqNo | L | Instrument flags and
Comment (Request.Comment | request comments are sent
Segment InstrumentFlag.Code) <CR> only if this action is
configured on the system
Options menu.
Terminator L | | | 1 | LineCount <CR> —
Segment
Seq No — The sequence number of
the segment identifies the
segment within the scope
of its parent segment.
Line Count — The line count is the total
number of segments in a
message, including the
Terminator Segment itself.

11314645 Rev. 02 83 / 150

Technidata LMX 6.0 Atellica Data Manager

QC Result Upload

Component Syntax Comment

Message HeaderSegment —
PatientSegment OrderList
TerminatorSegment
Header H | ^ ~ \ & | | | SenderId | | —
Segment ORU | | | ReceiverId | | P |
Version | TimeStamp | <CR>
Sender ID Id ^ Atellica Data Manager ID as specified in the -s
startup option of the
translator. The default
setting is lmxs.
Receiver ID Id ^ LIS ID as specified in the -r
startup option of the
translator. The default
setting is 38-1.
Version — As specified in the -v
startup option of the
translator. The default
setting for LMX
communication is A2.2.
Time Stamp — Date and time the result
was sent. Format:
YYYYMMDDHHMMSS.
Patient P|1|||||||U||||||||||| —
Segment | | | | | | | <CR>
Order List Order { Order } —
Order OrderSegment { —
ResultSegment
{ResultCommentSegment }
}
Order OBR | SeqNo | —
Segment QCLot.Number | | Test ^ ^ L
|R||||||Q|||||||||||||
| <CR>

84 / 150 11314645 Rev. 02

Atellica Data Manager Technidata LMX 6.0

Component Syntax Comment

Result OBX | SeqNo | ResultType | Value is either
Segment Test | | QCResult.Value | | | | | QCResult.Value or non-
| | Result.AvailabilityTime | | numeric extracted from
| | | <CR> a QCResult.Comment.
NOTE: Upload by Lot is
not recommended
when uploading large
amounts of QC results
per upload. When
uploading large
amounts of QC results,
the value for the Time
out option on the
Translator window
should be increased.
Result Type CE | NM | ST CE = Coded Entry for
enumerated tests.
NOTE: For enumerated
test results, choice
codes must be
synchronized between
LMX and the
Atellica DM software.
NM = Numeric Result.
ST = Alphanumerical
Result
Test — If a coding system is in
effect and a code for
the given test is
available, then
TestCode.Value is
transmitted. If not,
Test.Name is
transmitted.
Terminator L | | | 1 | LineCount <CR> —
Segment

11314645 Rev. 02 85 / 150

Technidata LMX 6.0 Atellica Data Manager

Component Syntax Comment

Seq No — The sequence number
of the segment
identifies the segment
within the scope of its
parent segment.
Line Count — The line count is the
total number of
segments in a message,
including the
Terminator Segment
itself.

LMX Transmission Examples

Patient sensitive information has been made anonymous within the
following examples.

Workorder Download: LIS to Atellica DM system, New Workorders

H|^~\&|||0001^HCSECURG||ORM|||0002^Atellica Data
Manager||P|A2.2|20010118162941|
P|1|PID1234|||LASTNAME^FIRSTNAME^||19500101|M|||||||||
||||||||ICU|
OBR|1|SID1234^||NA^^L^^^|R||||||||||||||||
OBR|2|SID1234^||CL^^L^^^|R||||||||||||||||
OBR|3|SID1234^||CA^^L^^^|R||||||||||||||||
OBR|4|SID1234^||IRON^^L^^^|R||||||||||||||||
OBR|5|SID1234^||TSH^^L^^^|R||||||||||||||||
OBR|6|SID1234^||FSH^^L^^^|R||||||||||||||||
C|1|L|This is only a test.|
L|||1|8||

86 / 150 11314645 Rev. 02

Atellica Data Manager Technidata LMX 6.0

Workorder Download: LIS to Atellica DM system, Rerun

H|^~\&|||0001^HCSECURG||ORM|||0002^Atellica Data
Manager||P|A2.2|20010118162941|
P|1|PID1234|||LASTNAME^FIRSTNAME^||19500101|M|||||||||
||||||||ICU|
OBR|1|SID1234^||NA^^L^^^|R||||||||||||||||
OBR|2|SID1234^||TSH^^L^^^|R||||||||||||||||
OBR|3|SID1234^||FSH^^L^^^|R||||||||||||||||
C|1|L|This is only a test.
|L|||1|5||

Quality Control Result Upload: Atellica DM System to LIS

H|^~\&|||8888^Atellica Data Manager||ORU|||38-
1^LIS||P|A2.2|20071120025446|
P|1|||||||U||||||||||||||||||
OBR|1|Q1234||CL^^L|R||||||Q||||||||||||||
OBX|1|NM|CL||105|||||||20071119025419|||||
OBR|2|Q1234||CL^^L|R||||||Q||||||||||||||
OBX|1|NM|CL||99|||||||20071119025519|||||
OBR|3|Q1234||CL^^L|R||||||Q||||||||||||||
OBX|1|NM|CL||95|||||||20071119025619|||||
OBR|4|Q1234||CL^^L|R||||||Q||||||||||||||
OBX|1|NM|CL||104|||||||20071119025719|||||
OBR|5|Q1234||CL^^L|R||||||Q||||||||||||||
OBX|1|NM|CL||103|||||||20071119025819|||||
OBR|6|Q1234||CL^^L|R||||||Q||||||||||||||
OBX|1|NM|CL||106|||||||20071119025919|||||
OBR|7|Q1234||CL^^L|R||||||Q||||||||||||||
OBX|1|NM|CL||101|||||||20071119030019|||||
L|||1|17|

11314645 Rev. 02 87 / 150

Technidata LMX 6.0 Atellica Data Manager

Result Upload: Atellica Data Manager to LIS

H|^~\&|||8888^Atellica Data
Manager||ORU|||381^LIS||P|A2.2|
20071120030826|
P|1|PID1234|PID1234||LASTNAME^FIRSTNAME||19500101|M|||
||||||||||||||ICU|
OBR|1|SID1234||CA^^L|R||||||||||||||||||||
C|1|L|This is only a test.|
OBX|1|NM|CA||9.2||||||||||||
OBR|2|SID1234||NA^^L|R||||||||||||||||||||
OBX|1|NM|NA||143||||||||||||
OBR|3|SID1234||CL^^L|R||||||||||||||||||||
OBX|1|NM|CL||102||||||||||||
C|2|L|Add-on test requested by phone.|
OBR|4|SID1234||IRON^^L|R||||||||||||||||||||
OBX|1|NM|IRON||67||||||||||||
OBR|5|SID1234||FSH^^L|R||||||||||||||||||||
OBX|1|ST|FSH||POS||||||||||||
OBR|6|SID1234||TSH^^L|R||||||||||||||||||||
OBX|1|NM|TSH||4.23||||||||||||
L|||1|17|

Example: One Result with Multiple Aspects

H|^~\&|||LMXS^Atellica Data Manager||ORU|||38-
1^LIS||P|A2.2|20110522175156|
P|1|CTR8|CTR8||CTR8FIRST^CTR8LAST||19800927|M|||||||||
|||||||||
OBR|1|CTR8||TSH^^L|S||||||||||||||||||||
OBX|1|NM|TSH||898.0|||||||20110522175119|||||
OBR|2|CTR8||TSH^^L|S||||||||||||||||||||
OBX|1|ST|TSH||POS|||||||20110522175119|||||
L|||1|7|

88 / 150 11314645 Rev. 02

6 Specimen Receipt Information and
Archive Location Transmission

Specimen receipt (inlabbing) information transmission is the auto-receipt

registration of samples checked in to the LAS. The SID, registration date
and time stamp, and location of the sample are uploaded from the LAS to
the Atellica DM system and then to the LIS.
Archive location transmission is the upload of the sample cold storage
archive location information as reported by the LAS. The Atellica DM
software can be configured to upload only the inlabbing information, only
the archive location information, or both, depending upon the needs of
the laboratory.
Changes to your LIS interface software can be required to provide the auto-
receipt functionality of uploading accession information or archive location
information to your LIS.

Inlabbing Upload
Your LIS must be able to support the receipt of inlabbing information for
samples that were not created within the LIS. If your LIS cannot support
this, you may not be able to fully integrate this feature.
Inlabbing messages contain the following associated sample information:
• SID
• Registration date and time, when the sample was checked into the LAS
• Checkin location
You can only perform one upload of LAS inlabbed information per sample.
Subsequent LAS inlabbing updates for the sample cannot be sent to
the LIS.
The expectation is that once the LAS sends the initial inlabbing message to
the Atellica DM system, this information is uploaded to the LIS.
NOTE: If results have already been uploaded to the LIS or if there are no
tests ordered for that sample, inlabbing information for that sample cannot
be uploaded.

11314645 Rev. 02 89 / 150

Specimen Receipt Information and Archive Location Transmission Atellica Data Manager

Archive Location Information Upload

Uploaded archive location information messages contain the following
associated sample information:
• LasStatus
• SampleId
• RegistrationDateTime (time, when the sample was archived into cold
storage on the LAS)
• TrayId
• Position
• Location1 ^ Location2 ^ Location3 ^ Location4
The Atellica DM software uploads the LAS archive location information
each time the sample is archived on the LAS. If the sample is removed from
cold storage for additional processing and then archived to a new cold
storage location, the Atellica DM software receives the new archive
location information and uploads the information to the LIS.
Please note the following restrictions and requirements:
• The Siemens Host Spec 79 protocol does not support inlabbing or
archive location information upload.
• The LIS may require configuration changes to accept and process the
inlabbing information or archive location information uploaded from
the Atellica DM system.
• The format used for uploading inlabbing and archive information for
HL7 is described in the HL7 Version 2.5 chapter in SAC Segment, page
120.
The LIS must be capable of handling the uploaded data for all possible
fields described within the grammar structure tables.

90 / 150 11314645 Rev. 02

Atellica Data Manager Specimen Receipt Information and Archive Location Transmission

ASTM 1394 Messages

For the ASTM 1394 protocol, the inlabbing and archive location
information is contained within the Manufacturer record of the LAS Status
Upload message.
The inlabbing archive location message contains the following: header
record, manufacturer record and terminator record.

11314645 Rev. 02 91 / 150

Specimen Receipt Information and Archive Location Transmission Atellica Data Manager

Grammar Structure of the ASTM LAS Status Upload Message

LAS Status Upload

Component Syntax ASTM Field

Message HeaderRecord
ManufacturerRecord
TerminatorRecord
Header Record H|\^&||||||||||P|1| Timestamp in
TimeStamp <CR> YYYYMMDDHHmmss
format
Manufacturer M | 1 | I | LasStatus ^
Record SampleId1^
RegistrationDateTime | TrayId |
Position | Location1 ^
Location2 ^ Location3 ^
Location4 <CR>
LAS Status I|L|R LAS Status I |L| R
I = Inlabbing
L = Left Equipment
(Cold Storage)
R = Rack
Rack upload is not
currently supported
in this upload
message.
Sample ID
Registration Timestamp in
Date Time2 YYYYMMDDHHmmss
format
Tray ID/Rack ID ID of the Tray
(ADVIA Automation)
or Rack (Aptio
Automation).

92 / 150 11314645 Rev. 02

Atellica Data Manager Specimen Receipt Information and Archive Location Transmission

Component Syntax ASTM Field

Pos Position in tray.
Position in tray is
identified by a letter/
digit combination:
A1 through J10
where the letters are
A - J and the numbers
are 1-10
Position in rack is
identified by a
numeric value (1-48)
LAS General ADVIA Automation: ADVIA Automation:
Area - CS CS = Cold Storage
Location 1 MT MT = Main Track
SC SC = Side Car
OT OT = Off Track
Aptio Automation: Node ID
Location 2 Shelf | Gate (ADVIA If General Area = CS3
Automation)
Then Location
2=Shelf
Floor (Aptio Automation)
If General Area = MT,
SC, or OT
Then Location
2=Gate
Location 3 Door If General Area = CS3
Then Location
3=Door
Else Location 3 is
blank
Location 4 Area Field If General Area = CS3
then Location 4=Area
Else Location 4 is
blank
Terminator L | 1 | N <CR>
Record

11314645 Rev. 02 93 / 150

Specimen Receipt Information and Archive Location Transmission Atellica Data Manager

Notes Explanation
1
Sample ID If the Atellica DM system receives an end of route
message from a sample placed into a SIQ tray within
the Sample Manager before the inlabbing message
is uploaded to the LIS, the Atellica DM system
uploads the information from the end of route
message, but the SID is 'NO READ' instead of the
actual SID.
2
Registration Registration date and time are not uploaded if a LAS
Date and Time update query initiates the generation of the sample
LAS information.
3
Location 2, 3, 4 Maximum possible field length is 240.

ASTM Specimen Receipt Information Transmission to LIS

The following two examples represent typical inlabbing messages.

Example 1
Tube 123456789 registered onto the lab automation system on 06-02-
2006 at 17:50
H|\^&||||||||||P|1|20060602193714
M|1|I|I^123456789^20060602175000|||MT
L|1|N

Example 2
Tube 123459876 registered onto the lab automation system on 06-02-
2004 at 9:15:12
H|\^&||||||||||P|1|20060602193518
M|1|I|I^123459876^20060602091512|||MT
L|1|N
The following example is a typical archive location information message.

94 / 150 11314645 Rev. 02

Atellica Data Manager Specimen Receipt Information and Archive Location Transmission

Example 3
In this example, sample 123456781 located in position A1 of unload tray
10027117 was placed into cold storage on 07-19-2007 at 14:06. The cold
storage location information uploaded corresponds to how the user
configured the cold storage names on the LineMaster computer.
H|\^&||||||||||P|1
M|1|I|L^123456781^20070719140624|10027117|A1|CS^Shelf2
^Door2^Area2
L|1

Technidata LMX Files

Sample inlabbing and archive location information from the
Atellica DM system is transmitted to the LIS in the Order Segment record of
the Patient Result Upload message.
Like other result files transferred to the LIS, the inlabbing and archive
location message within the result file contains the following: header
segment, patient segment, order segment, and terminator segment.

11314645 Rev. 02 95 / 150

Specimen Receipt Information and Archive Location Transmission Atellica Data Manager

Grammar Structure of the Inlabbing Upload File

Inlabbing Upload

Component Syntax Comment

Message HeaderSegment —
PatientSegment
[ PatientCommentSegment ]
OrderList TerminatorSegment
Header H | ^ ~ \ & | | | SenderId | | ORU | | —
Segment | ReceiverId | | | Version |
TimeStamp | <CR>
Sender ID Id ^ ATELLICA DATA MANAGER ID as specified in the -s
startup option of the
translator. The default
setting is lmxs.
Receiver ID Id ^ LIS ID as specified in the -r
startup option of the
translator. The default
setting is 38-1.
Version — As specified in the -v
startup option of the
translator. The default
setting for LMX
communication is A2.2.
Time Stamp — Date and time the result
was sent. Format:
YYYYMMDDHHMMSS.
Patient P | 1 | | | | | | | U| | | | | | | | | | | | | | | —
Segment | | | | | <CR>
Order OBR | SeqNo |
Segment SampleIdentifier1^ | | ^ ^ L | | | |
|||
ActionCode | | | | | | | | | LasStatus
^
RegistrationDateTime ^ TrayId ^
Position
^ GeneralArea(Location1) ^
Location2 ^ Location3
^Location4 | | | | | Order Result
Status <CR>
Action Code Blank for inlabbing upload.

96 / 150 11314645 Rev. 02

Atellica Data Manager Specimen Receipt Information and Archive Location Transmission

Component Syntax Comment

LAS Status I|L|R LAS Status I |L| R
I = Inlabbing
L = Left Equipment
(Cold Storage)
R = Rack
Rack upload is not
currently supported in
this upload message.
Registration Timestamp in
Date Time2 YYYYMMDDHHmmss
format
Tray Id ID of the Tray
(ADVIA Automation) or
Rack
(Aptio Automation)
Position Position in tray/rack.
Position in tray is
identified by a letter/
digit combination:
A1 through J10
where the letters are
A - J and the numbers
are 1 - 10
Position in rack is
identified by a numeric
value(1-48)
LAS General ADVIA Automation: ADVIA Automation:
Area - CS CS = Cold Storage
Location 1 MT MT = Main Track
SC SC = Side Car
OT OT = Off Track
Aptio Automation: Node ID
Location 2 Shelf | Gate (ADVIA Automation) If General area = CS3
then Location 2 = Shelf
Floor (Aptio Automation) Else Location 2 = Gate
Location 3 Door If General Area = CS3
then Location 3 = Door
Else Location 3 is blank

11314645 Rev. 02 97 / 150

Specimen Receipt Information and Archive Location Transmission Atellica Data Manager

Component Syntax Comment

Location 4 Area Field If General Area = CS3
then Location 4 = Area
Else Location 4 is blank
Order Result I For an inlabbing
Status message, this value is I.
Terminator L | | | 1 | LineCount <CR> —
Segment
Seq No — The sequence number
of the segment
identifies the segment
within the scope of its
parent segment.
Line Count — The line count is the
total number of
segments in a message,
including the
Terminator Segment
itself.

Notes Explanation
1
Sample ID If the Atellica DM system receives an end of
route message from a sample placed into a SIQ
tray within the Sample Manager before the
inlabbing message is uploaded to the LIS, the
Atellica DM system uploads the information
from the end of route message, but the SID is
'NO READ' instead of the actual SID.
2 Registration Registration date and time are not uploaded if a
Date and Time LAS update query initiates the generation of the
sample LAS information.
3 Location 2, 3, 4 Maximum possible field length is 240.

98 / 150 11314645 Rev. 02

Atellica Data Manager Specimen Receipt Information and Archive Location Transmission

LMX Specimen Receipt Information Transmission to LIS

The following two examples represent typical inlabbing messages.

Example 1
Tube 123456789 registered onto the lab automation system on
06-02-2006 at 17:50
H|^~\&|||LMXS^ATELLICA DATA MANAGER||ORU|||38-1^LIS
||P|A2.2|20060602182901|
P|1|||||||U||||||||||||||||||
OBR|1|123456789||^^L|R|||||||||||||||I^20060602175000^
^^MT|||||I
L|||1|4|

Example 2
In this example, tube 123459876 registered onto the lab automation
system on 06-02-2004 at 9:15:12.
H|^~\&|||LMXS^ATELLICA DATA MANAGER||ORU|||38-
1^LIS||P|A2.2|20060602192057|
P|1|||||||U||||||||||||||||||
OBR|1|123459876||^^L|R|||||||||||||||I^20060602091512^
^^MT|||||I
L|||1|4|
The following example is a typical archive location information message.

Example 3
In this example, sample 123456781 located in position J2 of unload tray
10002784 was placed into cold storage on 05-06-2008 at 19:20. The cold
storage location information uploaded corresponds to how the user
configured the cold storage names on the LineMaster computer.
H|^~\&|||LMXS^ATELLICA DATA MANAGER||ORU|||38-
1^LIS||P|A2.2|20080506183910|
P|1|||||||U||||||||||||||||||
OBR|1|123456781||^^L||||||||||||||||L^20080506184528^1
0002784^J2^CS^Right^Wed^Igloo 2|||||IL|||1|4|

11314645 Rev. 02 99 / 150

Specimen Receipt Information and Archive Location Transmission Atellica Data Manager

Example 4
In this example, tube 12341 registered onto the Input Output Module
(Node 4) of the Aptio Automation system on 04-08-2011 at 12:56:44.
H|\^&||||||||||P|1|20110408131504
M|1|I|I^12341^20110408125644|||04
L|1

100 / 150 11314645 Rev. 02

7 Siemens Host Spec. 79 Protocol

This section describes the Siemens Host Spec. 79 protocol used for the
communication link between the Atellica DM system and a LIS or host
computer.
This section is intended for the information systems professional
responsible for connecting the Atellica DM system and your host
computer. Contact your local technical support provider for additional
information.
NOTE: For a more detailed description of the Host Spec. 79 protocol, refer
to Communication Links Between the Data Manager and a Host Computer
(Customer bulletin 067D0068-xx).
NOTE: Upload of more than 1 patient result aspect is not supported by
this protocol. Instruments such as the ADVIA Centaur system can upload
more than 1 aspect for a result to the Atellica DM software. Although all
result aspects can be stored in the Atellica DM database, the Atellica DM
software uploads only 1 result aspect–the aspect that is specified as the
result selector–to the LIS using the Spec. 79 protocol. Uploading only 1
aspect can impact sites that upload infectious disease results, where both
numerical and interpretative aspects may be required.

Overview
NOTE: The ASTM 1394 communication protocol is the recommended
protocol for use with the Atellica DM system.
The LIS initiates sending patient workorder information to the
Atellica DM system before each sample run. The information will be parsed
and stored in the system for later use. An automatic request for patient
demographics is generated when a measurement cycle starts and no
existing sample ID workorder or patient demographic record exists on the
instrument.
The Atellica DM system can be configured to automatically transfer
available results to the host or manually transfer results to permit the
operator time to review the data and release the sample results.
NOTE: The Siemens Host Spec. 79 protocol does not support the
Atellica DM system inlabbing functions.

11314645 Rev. 02 101 / 150

Siemens Host Spec. 79 Protocol Atellica Data Manager System

Translator Specific Options

In the Atellica DM system, the driver for the Siemens Host Spec. 79 LIS
translator is the s79s driver.
The translator Specific Options are as follows:

-c <Configuration file The -c trame.par option specifies the name of

name> the configuration file. The default setting is
trame.par.
-i <Configuration file The -i specifies the path where the
directory> configuration file is located.
-s <port > The -s xxxx option sets the port number of the
LIS. This is mandatory and is usually entered as
8888.
xxxx is the port number of LIS.
-f The -f option sets the system to upload sample/
system flags.
-p The -p option sets the system to upload
disposition codes.
-u The -u option sets the system to upload the
validation user name.

Trame.par
The Trame.par file defines the structure of Host Spec. 79 messages
exchanged between the Atellica DM system and the LIS. Modifying this file
enables you to change the data stream that is transmitted. You can specify
the position of each item within the stream, as well as specify data
characteristics such as length, justification, and padding. However, you
cannot use the Trame.par file to modify transmission of the actual test
results.
The Trame.par file contains 3 parts:
• The first part of the file is the word HOST.
• The second part of the file lists the data items (keys) that can be
included in the message and specifies their characteristics. Test-related
data items for orders and results are not listed here because they
cannot be modified. Each key has three characteristics that you can
modify. They are enclosed within parentheses and separated by a
comma. Each key definition is terminated by a period.
• The third part of the file defines the sequence (message frame) in
which the data items are transmitted. There are two possible message
frames; one frame is for the workorder "Y" message, and one frame is
for the result "R" message.

102 / 150 11314645 Rev. 02

Atellica Data Manager System Siemens Host Spec. 79 Protocol

Keys and Their Characteristics

Keys are individual items within the data stream. They display in the
following format:
key name = (X,Y,Z)

X The number of characters transmitted for this item

Y L = characters are left aligned
R = characters are right aligned
Z S = each unused character position is filled with a space
Z = each unused character position is filled with a zero

11314645 Rev. 02 103 / 150

Siemens Host Spec. 79 Protocol Atellica Data Manager System

Grammar

Component Syntax Comment

Definition HOST <CR> <LF> { —
KeyDefinition } {
FrameDefinition }
KeyDefinition KeyName = ( Width , —
Alignment , Padding ) . <CR>
<LF>
KeyName WorkOrderKeyName | —
ResultKeyName
WorkOrderKeyName BIRDAY | BIRMONT | BIRYEAR | —
COCOM | COLDAY | COLHOUR
| COLMIN | COLMONT |
COLSEC | COLYEAR | CPCOM |
DOCTOR | IDEE | LOCATIO |
PATNAM | PATNUM | SEX |
SPCODE | URGENT | UPDT |
SLIDE
ResultKeyName ASPDAY | ASPHOUR | ASPMIN —
| ASPMONT | ASPSEC |
ASPYEAR | COCOM | CPCOM |
IDEE | INSTRUMENT |
NUMPOS | NUMRACK |
PATNUM | POSTUBE | SPCODE
| SPTEXT
Width — Number of
characters to be
transmitted
Alignment L|R L = left
R = right
Padding S|Z S = space
Z = zero
FrameDefinition ( WorkOrderFrameDefinition —
| ResultFrameDefinition )
<CR> <LF>
WorkOrderFrameDef TRAME_Y = STX , MT , { —
inition WorkOrderItem , } CRLF , LRC
, ETX .
ResultFrameDefiniti TRAME_R = STX , MT , { —
on ResultItem , } CRLF , LRC , ETX
.

104 / 150 11314645 Rev. 02

Atellica Data Manager System Siemens Host Spec. 79 Protocol

Component Syntax Comment

WorkOrderItem " StringLiteral " | SpaceCount | Colon ( : ) is a
( WorkOrderKeyName ) | : placeholder for
variable-size
request-based
information
ResultItem " StringLiteral " | SpaceCount | Colon ( : ) is a
( ResultKeyName ) | : placeholder for
variable-size
request-based
information
StringLiteral — Transmitted
literally
SpaceCount — Number of space
characters to be
transmitted

11314645 Rev. 02 105 / 150

Siemens Host Spec. 79 Protocol Atellica Data Manager System

Key Name Overview

Key Atellica DM Field Comment Default

ASPDAY Result.AspirationTime (day) In the (2,R,Z)
ASPHOUR Result.AspirationTime (hour) Atellica DM (2,R,Z)
system,
ASPMONT Result.AspirationTime aspiration time is (2,R,Z)
(month) linked to results
ASPMIN Result.AspirationTime and is more (2,R,Z)
(minutes) specific than
ASPSEC Result.AspirationTime these sample- (2,R,Z)
(seconds) based messages
permit. The
ASPYEAR Result.AspirationTime (year) (2,R,Z)
Atellica DM
software copies
the earliest
aspiration time of
any embedded
result into the
message.

BIRDAY Patient.BirthDate (day) — (2,R,S)

BIRMONT Patient.BirthDate (month) — (2,R,S)
BIRYEAR Patient.BirthDate (year) — (4,R,S)
COCOM Sample.Comment — —
COLDAY Sample.CollectionTime (day) — (2,R,Z)
COLHOUR Sample.CollectionTime — (2,R,Z)
(hour)
COLMIN Sample.CollectionTime — (2,R,Z)
(minute)
COLMONT Sample.CollectionTime — (2,R,Z)
(month)
COLSEC Sample.CollectionTime — (2,R,Z)
(second)
COLYEAR Sample.CollectionTime — (2,R,Z)
(year)
CPCOM Patient.Comment — —
DOCTOR Physician.Identifier — (6,L,S)
IDEE Sample.Identifier — (14,R,Z)

106 / 150 11314645 Rev. 02

Atellica Data Manager System Siemens Host Spec. 79 Protocol

Key Atellica DM Field Comment Default

INSTRUMENT Instrument.Name In the (5,R,S)
Atellica DM
system,
instrument
references are
linked to results
and are more
specific than this
sample-based
message permits.
The Atellica DM
software copies
the first
instrument
reference of any
embedded result
into the message.
LOCATIO PatientLocation.Name — (1,R,S)
NUMPOS Sample.LastPosition — —
NUMRACK Sample.LastRack — —
PATNAM Patient.LastName — (30,L,S)
Patient.FirstName
PATNUM Patient.Identifier — (14,L,S)
POSTUBE Sample.LastRack If you specify the (6,R,S)
Sample.LastPosition POSTUBE, the
track transmits as
rack+position
separated by a
space. You can
change this
format by
specifying
NUMRACK and
NUMPOS
separately.
SEX Patient.Sex M, F, or blank. (1,R,S)

11314645 Rev. 02 107 / 150

Siemens Host Spec. 79 Protocol Atellica Data Manager System

Key Atellica DM Field Comment Default

SPCODE SpeciesIdentifier If a coding (4,R,S)
system is in use,
this identifies a
species by
SpeciesCode.Valu
e. If not, this is
identifies a
species by
Species.Name.
SPTEXT Species.Name — —
URGENT Sample.Priority U = Stat (1,L,S)
Anything else is
interpreted as
Routine priority.
UPDT — Update indicator (1,R,S)
that is required
for updates to
existing samples.
SLIDE Manufacturer (1,R,S)
record following
the order
segment with
M.3 =
SlideSuppression
when the value
of SLIDE is ‘N.’

Order Download
The following conditions apply to order download records:
• Patient Identifier (PID) is limited to 40 characters. Patient Last Name,
First Name, and Middle Name are restricted to 70 characters. Physician
First Name and Last Name are restricted to 70 characters.
• Test identifiers contained in the order message are right-aligned with
leading zeros. If a coding system is in use, this is used to identify a test
by TestCode.Value. If not, this is used to identify a test by
Test.Mnemonic.
• Request-based data may include previous result values and times. If no
time is specified, 00:00:00 is the default.

108 / 150 11314645 Rev. 02

Atellica Data Manager System Siemens Host Spec. 79 Protocol

• When the Atellica DM software receives an updated workorder from

the LIS using the Host Spec. 79 communication protocol, any current
result in the Atellica DM system with a status of REV (Review) or VAL
(Validated) will be deleted and the request for that test omitted if these
requests are absent from the updated workorder. Results with a status
of UPL (Uploaded) are not affected.
NOTE: Do not mix action codes in the same message. The Atellica DM
software does not support the receipt of different action codes (for
example, Cancel and Add) sent in the same message.
Test1 Cancel
Test2 Add-on
Test3 Add-on
Test4 Cancel
In this example, Test1 would not be processed.

FTP Error for Image Transmission

If an error stating “The computer is disconnected from the network”
displays on the screen, it may be caused by Internet Explorer being set to
work offline. You can deselect the option using the Internet Explorer File
menu.

Updating Workorders from the LIS using Host Spec. 79 and LMX
When the Atellica DM software receives an updated workorder from the LIS
using the Host Spec. 79 and LMX communication protocols, any current
result in the Atellica DM system with a status of Review (REV) or Validated
(VAL) is deleted and the request for that test omitted if these requests are
absent from the updated workorder. Results with a status of Uploaded
(UPL) are not affected.
NOTE: Use caution when updating a workorder from the LIS using the
Host Spec. 79 or LMX communication protocols. Requests are omitted
without a message or warning. This issue will be address in a future
software release.

Patient Result Upload

The following conditions apply to patient result upload records:
• Up to 110 result records can be transmitted in a single message.
• Test identifiers are right-aligned with leading spaces. If a coding system
is in use, the identifier is set to TestCode.Value. If not, it is set to
Test.Mnemonic.
• Result values are right aligned with leading spaces.

11314645 Rev. 02 109 / 150

Siemens Host Spec. 79 Protocol Atellica Data Manager System

• The Flags field contains an Asterisk (*) only if a flag is present in the
Flag codes field.
• The Spec79 protocol restricts upload of instrument flags to a maximum
of 15 per result and to flags with a 2-character code.
• Result disposition code contains 'E' (Edited) only if the result is not
obtained from an instrument.
• The validation user login name is transmitted only if startup parameter
-u is used and UploadModel.ValidationUser is set.

QC Result Upload
QC result upload is very similar to the patient result upload. The structure
of the message is the same, defined by trame.par. However, the following
key names are substituted differently:

Key Name Atellica DM Field Comment

ASPDAY QCResult.AssessmentTime (day In the Atellica DM
part) system, aspiration
ASPHOUR QCResult.Assessment (hour part) time is linked to
results and is more
ASPMONT QCResult.Assessment (month specific than this
part) sample-based
ASPMIN QCResult.Assessment (minutes message permits. The
part) Atellica DM software
ASPSEC QCResult.Assessment (seconds copies the earliest
part) aspiration time of any
embedded result into
ASPYEAR QCResult.Assessment (year part)
the message.
IDEE QCLot.Number

All other fields are left blank. This means that they are either filled in with
spaces (S in trame.par) or by zeroes (Z in trame.par).

110 / 150 11314645 Rev. 02

Atellica Data Manager System Siemens Host Spec. 79 Protocol

Message Frames
The elements of a message frame are as follows:
Frame name=STX, MT, "Literal character", space indicator, :, space
indicator, (key name), CRLF, LRC, ETX.

Frame name TRAME_Y = Workorder message

TRAME_R = Result message
Literal characters These characters are transmitted
exactly as they display, without the
quotation marks.
Space indicator This number indicates the number of
space characters transmitted.
: This character indicates the position of
test related information that has no
fixed size.

TRAME_Y Workorder Data Stream - with Slide

TRAME_Y=STX,MT,"Y",2,(URGENT),(UPDT),1,(IDEE),8,(SLIDE
),16, (SPCODE),1,(PATNUM),3,(PATNAM),1,(BIRMONT),"/
",(BIRDAY),"/",(BIRYEAR),1,(SEX),1,(COLMONT),"/
",(COLDAY),"/
",(COLYEAR),1,(COLHOUR),(COLMIN),1,(LOCATIO),1,(DOCTOR
),1, CRLF,:,CRLF,LRC,ETX.

TRAME_Y Workorder Data Stream - without Slide

TRAME_Y=STX,MT,"Y",2,(URGENT),(UPDT),1,(IDEE),20,(SPCO
DE),1,
(PATNUM),3,(PATNAM),1,(BIRMONT),"/",(BIRDAY),"/
",(BIRYEAR),
1,(SEX),1,(COLMONT),"/",(COLDAY),"/
",(COLYEAR),1,(COLHOUR),
(COLMIN),1,(LOCATIO),1,(DOCTOR),1,CRLF,:,CRLF,LRC,ETX.

Default “R” (Result) Message

TRAME_R=STX,MT,"R",1,(IDEE),1,(SEX),(POSTUBE),6,(SPCOD
E),1,
(ASPMONT),"/",(ASPDAY),"/
",(ASPYEAR),1,(ASPHOUR),":",(ASPMIN),":",
(ASPSEC),3,CR,LF,:CRLF,LRC,ETX.

11314645 Rev. 02 111 / 150

Siemens Host Spec. 79 Protocol Atellica Data Manager System

112 / 150 11314645 Rev. 02

8 HL7 Version 2.5

Overview
The Atellica DM software provides the mhl7 translator, which implements
a subset of HL7 version 2.5. The HL7 version 2.5 protocol provides the
communication link between the Atellica DM system and a LIS using HL7.
An HL7 version 2.5 implementation is not backward compatible with HL7
version 2.3 implementations. To communicate, a minimal lower layer
protocol must be implemented by the LIS.
The HL7 communication link allows the LIS to transmit workorders
and multiple previous patient results for the same test to the
Atellica DM software and to accept QC and patient test results transmitted
from the Atellica DM software.
NOTE: If the LIS that is connected to the Atellica DM system uses the HL7
protocol, there is a 63-character limit for the upload of instrument flags.

Translator Specific Options

The mhl7 translator has the following specific options:

-i Only applicable for HL-7 OUL R22, result

<sending_application: upload, and HL-7 SSU U03, specimen status
sending_facility> update, message types.
Used to identify the sending application and the
sending facility.
Default values:
sending_application = Atellica Data Manager
sending_facility = ResultExport
-r Only applicable for HL-7 OUL R22, result
<receiving_application: upload, and HL-7 SSU U03, specimen status
receiving_facility> update, message types.
Used to identify the receiving application and
receiving facility.
Default values:
receiving_application = LIMS
receiving_facility = ResultImport
-s <port> Configures the TCP/IP port where the mhl7
translation listens for LIS Communications

11314645 Rev. 02 113 / 150

HL7 Version 2.5 Atellica Data Manager

-c <client idle time out> Configures the time-out value (seconds) after
which the mhl7 translator closes a client
connection that has been idle; that is, no
upload or download operation occurred in that
time interval.
This option is only applicable when mhl7
translator is configured as a TCP/IP listener
service(-s option used).
Default = 86,400 seconds (1 day of idle
operation).
-t <client response time Configures the time-out value (seconds)
out> applied when the mhl7 translator, operating as
a TCP/IP listener, expects a response to a result
upload or sample status update message. If the
timeout value is exceeded then the mhl7
translator issues a reject message and
determines that the result upload or status
update did not succeed.
Default value = 30 seconds.

Lower Layer Protocol

This mhl7 translator uses a minimal lower layer protocol to demarcate the
HL7 messages exchanged with the LIS. The format of this lower level
protocol is as follows:
<SB>message_data<EB><CR>
• The protocol codes are identified as follows:
• <SB> - one byte Start Block character; that is, 0x0b (decimal 11)
• <EB> - one byte End Block character; that is, 0x1c (decimal 28)
• <CR> - carriage return character, 0x0d

Single and Dual Channel

The mhl7 translator is used as a single connection to the LIS or as a dual
connection, where two channels are used to communicate with the LIS.

Single Channel
A single TCP/IP channel is established with the LIS. The translator sends
results and status updated to the LIS on this channel. It also receives orders
from the LIS on this same channel. Transmission by both the Atellica DM
software and the LIS can be simultaneous as the minimal lower layer does
not impose any session establishment requirements, as with ASTM 1381.

114 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

The –s option configures the port at which mhl7 listens for the connection
from the LIS.
Alternatively, the translator can connect to the LIS as a client by placing the
LIS IP address and port number in the translators External Interface.
NOTE: When the Atellica DM system is operating as a TCP socket server,
the client must connect to that socket in order for there to be an available
TCP connection. If the Atellica DM system operates as the TCP Client
instead then it can attempt to establish the TCP connection.

Dual Channel
Separate upload and download channels are configured. This
configuration is established via the Outbound LIS Translator and Inbound
LIS Translator.
The outbound translator uploads results and status updates to the LIS.
Simultaneously, the inbound translator can receive orders from the LIS.
The –s option configures whether the translator serves as a TCP/IP listener
(server). If it does not serve as a TCP/IP listener, it serves as a client, which
connects to a LIS listening socket. If defined as a client, the LIS IP address
and port number must be placed in the translators External Interface.
The dual channel configuration provides for increased bandwidth of
communication with the LIS, but requires that the LIS support separate
upload and download channels.

WARNING Always configure the Atellica DM system as a TCP-IP server.

This allows LIS vendors to change IP addresses without reconfiguration of
the Atellica DM system.

Message Grammar
This section details all of the HL7 message formats that are recognized by
the mhl7 translator and the corresponding acknowledgement that is
expected.
All messages must be in the appropriate message format or they will be
rejected. See Application Processing Rules, page 137 and Handling of
Unrecognized Messages, page 139.

11314645 Rev. 02 115 / 150

HL7 Version 2.5 Atellica Data Manager

Result Upload Message

A Result Upload message is comprised of the following segments:

MSH Segment
MSH segment is detailed in the Application Processing Rules section. See
Application Processing Rules, page 137.

116 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

PID Segment
The PID segment consists of the following:

The applicable fields of the PID segment follow:

• Patient ID Patient identifier from Result.Patient.Identifier. Patient
Identifier (PID) is limited to 40 characters.
• Patient Name Consists of 3 components derived from Result.Patient:
LastName, FirstName, MiddleName respectively. Patient Last Name,
First Name, and Middle Name are restricted to 70 characters.
• BirthDate From Request.Patient.BirthDate and is formatted as
YYYYmmdd.

11314645 Rev. 02 117 / 150

HL7 Version 2.5 Atellica Data Manager

NOTE: If the patient birthdate value downloaded from the LIS indicates
that the patient age is greater than 150 years, the birthdate value is not
accepted and the patient birthdate is not populated in the
Atellica DM system.
• PatientSex From Result.Patient.Sex and values are F (female),
M (male) and U (unknown).
• SpeciesCode From Result.Patient.Species.

NTE Segment
The NTE segment represents notes or comments and is always associated
with the previous segment logically. The NTE segment consists of the
following:

The applicable fields of the NTE segment follow:

• Comment: Comment associated with the previous segment. When the
preceding segment is a PID segment, then Comment is from
Result.Patient.Comment.
• CommentType: Type of the Comment. When the Comment is a PID
comment, then the value is “OC.”

PV1 Segment
The PV1 segment includes patient administration information. While this
segment consists of 50 fields, the mlh7 translator only uses the first 3
fields. The PV1 segment consists of the following:

The applicable fields of the PV1 segment follow:

• SetId: Always populated with the value “1.”
• Patient Class: Always transmitted as “N” (not applicable).
• Patient Location: From Result.Patient.Location.

118 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

SPM segment
The SPM segment contains specimen related information. The SPM
segment consists of the following:

The applicable fields of the SPM segment follow:

• Specimen ID: From Order.Sample. When the sample is a QC result, the
QC Lot information is sent in this field.
• Specimen Type: From Order.SampleType. When the sample is a QC
sample, then the value used is “QC3”, which is reserved for this
purpose.
• Specimen Source: From Sample.SampleSource.
• Specimen Description: From Sample.Comment.

11314645 Rev. 02 119 / 150

HL7 Version 2.5 Atellica Data Manager

• Specimen Collection Time: From Sample.CollectionTime and formatted

as YYYYmmddHHMMSS.
• Container Type: From Sample.ContainerType.

SAC Segment
The SAC segment contains specimen container information and consists of
44 fields. While the following table is truncated; the fields that do not
display are not used.
The SAC segment consists of the following:

120 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

The applicable fields of the SAC segment follow:

• Carrier Identifier: From Sample.InstrumentRack.
• Position in Carrier: From Sample.InstrumentPosition.
• Dilution Factor: From Result.ManualDilutionCoefficient and contains
four components: 29.1 : -, 29.2 : “1”, 29.3 : -, and 29.4, the actual
dilution factor.

OBR Segment
The OBR segment contains information on the ordered tests or
observations and consists of 47 fields. This is a mandatory segment in a
Result Upload message and an Order Download message. There may be
multiple OBR segments associated with a parent SPM segment.
While this segment consists of 47 fields, the mlh7 translator only uses a
subset of these fields.

11314645 Rev. 02 121 / 150

HL7 Version 2.5 Atellica Data Manager

The OBR segment consists of the following:

The applicable fields of the OBR segment follow:

• OBR.2 Placer Order Number: From Sample.Identifier. For QC results,
this value is the QC lot number.
• OBR.3 Filler Order Number: Identical to OBR.2.
• The following is a code example showing OBR.2 and OBR.3 as the same
value:
• OBR|1|324383|324383|FSH|||20090901|

122 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

• OBR.4 Universal Service ID: Identifies the Test. It is a Composite field

which contains the Test optionally followed by the Aspect separated by
a dot: TSH.RLU.
• OBR.15 Specimen Source: See SPM segment.
• OBR.16 Ordering Provider: Sample.Physician if available. Physician
Name is restricted to 70 characters.
• OBR.22 Status Change DateTime: Current time when segment created.
• OBR.25 Result Status: If observation could not be done, then the value
is “X”. Otherwise this field is empty.
• OBR.26 Parent Result: Used in conjunction with OBR.29. OBR.26.1
Indicates a specific parent OBX segment of the parent OBR to which
this current OBR is related to. OBR.26.2 Contains the parent OBX
segment identifier (OBX.4).
• OBR 27: Indicates priority and timing. 27.1.4 indicates
Sample.CollectionTime. 27.1.6 Indicates Sample.Priority as follows: R
for Routine; S for Stat; A for Asap; Empty implies Routine.
• OBR.29: Indicates the parent OBR to which this current OBR is related, if
any.

Mixed Action Codes

Do not mix action codes in the same message. The Atellica DM software
does not support the receipt of different action codes (for example, Cancel
and Add) sent in the same message.
Test1 Cancel
Test2 Add-on
Test3 Add-on
Test4 Cancel
In this example, Test1 would not be processed.

ZOB Segment
The ZOB segment, a site specific segment, specifies the auto dilution of a
result. The ZOB segment consists of the following:

The applicable fields of the ZOB segment follow:

• Auto Dilution Condition: From Result.AutoDilutionCondition
• Auto Dilution Coefficient: From Result.AutoDilutionCoefficient
NOTE: This is the dilution reported by the instrument. This does not
specify a manual sample tube dilution.

11314645 Rev. 02 123 / 150

HL7 Version 2.5 Atellica Data Manager

ORC Segment
The ORC Common order Segment contains information common to all
orders and consists of 25 fields. The mhl7 translator uses a subset of these
fields.
The ORC segment consists of the following:

The applicable fields of the ORC segment follow:

• ORC.1: Always populated with the value “SC”.
• ORC.2,ORC.3: See OBR2 and OBR.3.
• ORC.7: See OBR.27.
• ORC.9: Current date and time when segment is created.
• ORC.12: From Sample.Physician. Physician Name is restricted to 70
characters.

ZBP Segment
The ZBP is an optional segment used to indicate blood product
information. This segment is not supported by the Atellica DM software.

124 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

OBX Segment
The OBX segment is the critical segment used to indicate test result value.
The OBX segment consists of the following:

The applicable fields of the OBX segment follow:

• OBX.2: Data type of the Result Value. Codes include the following: NM
for Numeric; ST for string; and RP for an image.
• OBX.3: Test name and aspect. An example is T3.DOSE.
• OBX.5: Result.Value. Where the result type is RP (image), then the
value is the filename of the image that would be transferred to the LIS
via ftp.
• OBX.11: Result Status. As only Validated results are uploaded this is
always “F”.
• OBX.14: Result.AspirationTime.
• OBX.16: Responsible user. The format is
ValidationUser~InstrumentUser.
• OBX.18: Instrument that produced the result value.
• OBX.19: Test Completion Time, if defined.

11314645 Rev. 02 125 / 150

HL7 Version 2.5 Atellica Data Manager

Result Upload Message Example 1

If there are Comments or Instrument Flags associated with the Result
Value, one or more NTE segments follow an OBX segment. If the NTE
contains a result comment, then the Comment Type is “RC”. If it contains a
Result Flag, then the Comment Type is “RF.”
An example of a Result Upload Message is as follows:
MSH|^~\&|Atellica Data Manager
|ResultExport|LIMS|ResultImport|20071201132448||OUL^R2
2^OUL_R22|1|P|2.5||||||8859/1
PID|1||ND||Patient^Sick||19750110|M|||||||||||||||||||
|||N|||||Human PV1|1|N SPM|1|mov3||Whole blood
SAC||||||||||004|06
OBR|1|mov3|mov3|WBC||||||||||||||||||20071201132448|||
||^^^^^R ORC|SC|mov3|mov3||||^^^^^R||20071201132448
OBX|1|NM|WBC||10.61||||||F|||19981023095217||sysman||I
nst1 NTE|1|L|NC|RF NTE|2|L|WC|RF
OBR|2|mov3|mov3|RBC||||||||||||||||||20071201132448|||
||^^^^^R ORC|SC|mov3|mov3||||^^^^^R||20071201132448
OBX|1|NM|RBC||5.14||||||F|||19981023095217||sysman||In
st1
OBR|3|mov3|mov3|HGB||||||||||||||||||20071201132448|||
||^^^^^R ORC|SC|mov3|mov3||||^^^^^R||20071201132448
OBX|1|NM|HGB||13.9||||||F|||19981023095217||sysman||In
st1

Result Upload Message Example 2

An example of a QC Result Upload Message for a QC lot of 2091 follows:
NOTE: The value QC3 in field 4 of the Specimen segment distinguishes
the result as a QC result. The QC lot number populates the Specimen ID
(Field 2) of the SPM Segment and the Placer Order field (Field 2) of the OBR
segment.
MSH|^~\&|Atellica Data Manager
|ResultExport|LIMS|ResultImport|20080417084931||OUL^R2
2^OUL_R22|5|P|2.5||||||8859/1
PID|1|||||||U||||||||||||||||||||||N
PV1|1|N
SPM|1|2091||QC3
OBR|1|2091|2091|RBC||||||||||||||||||20080417084931|||
||^^^^^R

126 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

ORC|SC|2091|2091||||^^^^^R||20080417084931
OBX|1|NM|RBC||4.88||||||F|||19981023093347||||Advia120
_06

Result Upload Message Example 3

The Atellica DM software supports the upload of all aspects to LIS using
the HL7 protocol. Result comments and flags are only uploaded after the
result selector aspect and not after all aspects.
NOTE: DOSE is the result selector aspect in the following example:
OBR|4|TestSID|TestSID|T3.DOSE||||||||||||||||||2009042
9190107|||||^^^^^R
ORC|SC|TestSID|TestSID||||^^^^^R||20090429190107
OBX|1|NM|T3.DOSE||3.17||||||F|||20010820152907||user1|
|AdviaCentaur_1
NTE|1|L|Result comment T3|RC
NTE|2|L|Diluted|RF
NTE|3|L|High CV|RF
OBR|5|TestSID|TestSID|T3.COFF||||||||||||||||||2009042
9190107|||||^^^^^R
ORC|SC|TestSID|TestSID||||^^^^^R||20090429190107
OBX|1|NM|T3.COFF||1.00||||||F|||20010820152907||user1|
|AdviaCentaur_1
OBR|6|TestSID|TestSID|T3.RLU||||||||||||||||||20090429
190107|||||^^^^^R
ORC|SC|TestSID|TestSID||||^^^^^R||20090429190107
OBX|1|NM|T3.RLU||160815||||||F|||20010820152907||user1
||AdviaCentaur_1

Result Upload Acknowledge Example

The Result Upload acknowledge message is comprised of the MSH and
MSA segments. See Application Processing Rules, page 137.
The Message Type field in MSH.9 is “ACK^R22^ACK”.
An example of a Result Upload Acknowledge message is as follows:
MSH|^~\&|LIMS|ResultImport|Atellica Data
Manager|ResultExport|20070305170957||ACK^R22^ACK|2|P|
2.5||||||8859/1
MSA|AA|1||

11314645 Rev. 02 127 / 150

HL7 Version 2.5 Atellica Data Manager

Order Download Message from LIS to Atellica DM System

An order download (Import) message \ comprises the following segments.
The use of the Batch Protocol mechanism, BHS and BTS segments, is
optional.
The Batch Protocol mechanism is used by a LIS to indicate a loadlist batch
for a particular instrument.

128 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

BHS Segment
The BHS segment indicates the start of a batch of orders. The BHS.6 field
specifies the instrument to be targeted. The BHS segment consists of the
following:

The applicable fields of the BHS segment follow:

• BHS.3: Sending Application. Any value used is returned in batch
acknowledgement.
• BHS.4: Sending Facility. Any value used is returned
• BHS.5: Receiving Application. Not defined, any value used is returned.
• BHS.6: Targeted Instrument to which all orders, between this segment
and the batch closing BTS segment, are to be targeted.
• BHS.11: Unique batch identifier.
• BHS.12: Not relevant on sending.
The response to a Batch or orders is itself a batch of acknowledgement
segments.

MSH Segment
The MSH segment is as detailed in the Application Processing Rules section.
See Application Processing Rules, page 137.
The Message Type is “OML^O33^OML_O33”
The PID, NTE, PV1, SPM, SAC, ORC, OBR, ZOB, ZBP and OBX segments for
the Order Download message are identical to those detailed for the Result
Upload message. See the segment information outlined for each segment
after the following: Result Upload Message, page 116.
NOTE: Patient Identifier (PID) is limited to 40 characters. Patient Last
Name, First Name, and Middle Name are restricted to 70 characters.
Physician First Name and Last Name are restricted to 70 characters.

11314645 Rev. 02 129 / 150

HL7 Version 2.5 Atellica Data Manager

NOTE: In the order download message, the OBX segment contains LIS
previous results. Multiple previous results can be downloaded for an
individual test.
The following detail is unique to an Order Download message:
ORC.1 Control – The applicable values follow: “NW” for a New Order; “XO”
for an Order Update; “CA” to cancel the contained order; and “PR” if child
OBX records exist following the ORC that contains Previous Results.
The difference between using NW and XO are as follows:
• Either NW or XO can be sent if the test is not already on the sample.
• XO must be sent for a rerun
• The first time a sample is sent, use NW. For all subsequent tests or
reruns, use XO
NOTE: When Previous Results are sent, the fields Physician ID, Priority, and
Collection Time are not read from the ORC segment.

BTS Segment
The BTS is the batch trailer segment and indicates the end of a batch of
orders that is targeted to a particular Instrument.
The BHS segment consists of the following:

Order Download Example 1

An example of a single order download message follows:
MSH|^~\&|WPX||DX_LAB|Hematology|20060616150307||OML^O3
3^OML_O33|161|P|2.5||||||8859/1|
PID|1||AE||Elkorbachi^Ann^AA^^H^Dr^L||19740423|F|Kroke
t^^^^^^A||Cederstraat^56^Gent^^9000^B||09234567||BE|||
104000145^^^ASOL|||||Gent|Y|||||20020101000000|Y
SPM|1|Advia120NR1||WHOLE
BLOOD|||||||||||||200608141505||||||||||
ORC|NW|Advia120NR1|||||^^^^^S^^Order
comment||20060814150256
OBR|1|Advia120NR1||WBC^White blood cells
ORC|NW|Advia120NR1|||||^^^^^S^^Order
comment||20060814150256

130 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

OBR|1|Advia120NR1||RBC
ORC|NW|Advia120NR1|||||^^^^^S^^Order
comment||20060814150256
OBR|1|Advia120NR1||HCT
ORC|NW|Advia120NR1|||||^^^^^S^^Order
comment||20060814150256
OBR|1|Advia120NR1||MCV
ORC|NW|Advia120NR1|||||^^^^^S^^Order
comment||20060814150256
OBR|1|Advia120NR1||BLASTS
ORC|NW|Advia120NR1|||||^^^^^S^^Order
comment||20060814150256
OBR|1|Advia120NR1||ATYPS
ORC|NW|Advia120NR1|||||^^^^^S^^Order
comment||20060814150256
OBR|1|Advia120NR1||CH
ORC|NW|Advia120NR1|||||^^^^^S^^Order
comment||20060814150256
OBR|1|Advia120NR1||HDW
ORC|NW|Advia120NR1|||||^^^^^S^^Order
comment||20060814150256
OBR|1|Advia120NR1||HGB
ORC|NW|Advia120NR1|||||^^^^^S^^Order
comment||20060814150256
OBR|1|Advia120NR1||HYPER
SPM|2|Advia120NR2||WHOLE
BLOOD|||||||||||||200608141505||||||||||
ORC|NW|Advia120NR2||4717S|||^^^20030101205959^^S^^Orde
r blabla||20040609150256||||||||||||IHE Cardio
(6400)^^^^^^FI^^^6400
OBR|1|Advia120NR2||WBC||||||||||||1234^Anonymous^A
SPM|3|Advia120NR3||WHOLE
BLOOD|||||||||||||200608141505||||||||||
ORC|NW|Advia120NR3||4717S|||^^^20030101205959^^S^^Orde
r blabla||20040609150256||||||||||||IHE Cardio
(6400)^^^^^^FI^^^6400
OBR|1|Advia120NR3||RBC||||||||||||1234^Anonymous^A

11314645 Rev. 02 131 / 150

HL7 Version 2.5 Atellica Data Manager

Order Download Example 2

An example of a HL7 LIS workorder download when the LIS specifies the
instrument to be targeted for the requests follows:
NOTE: An instrument with ID of VERSANT440_3 is shown as the target for
two new orders.
BHS|^~\&|Atellica Data Manager
|ResultExport|LIMS|VERSANT440_3|20071201132448||||021|
|
MSH|^~\&|Atellica Data Manager
|ResultExport|LIMS|ResultImport|20071201132448||OML^O3
3^OML_O33|1|P|2.5||||||8859/1
PID|1||V440_3Test1||vBHSFirst1^vBHSMid1^vBHSLast1||198
50110|M||||||||||||||||||||||N|||||Human
PV1|1|N|AH
SPM|1|V443Test_1||Serum||||||||||Comment|||20071201124
545||||||||||12 x 75
ORC|NW|V443Test_1|V443Test_1||||^^^20071201124545^^R||
20080401132448|||JF
OBR|1|V443Test_1|V443Test_1|HIV RNA
3.0||20080401132448|20080401132448|||||||||JF||||||200
80401132448|||||^^^20080401132448^^R
MSH|^~\&|Atellica Data Manager
|ResultExport|LIMS|ResultImport|20071201132448||OML^O3
3^OML_O33|2|P|2.5||||||8859/1
PID|1||V440_3Test2||vBHSFirst2^vBHSMid2^vBHSLast2||199
50110|M||||||||||||||||||||||N|||||Human
PV1|1|N|AH
SPM|2|V443Test_2||Serum||||||||||Comment|||20071201124
545||||||||||12 x 75
ORC|NW|V443Test_2|V443Test_2||||^^^20071201124545^^R||
20080401132448|||JF
OBR|1|V443Test_2|V443Test_2|HIV RNA
3.0||20080401132448|20080401132448|||||||||JF||||||200
80401132448|||||^^^20080401132448^^R
BTS||Batch Comment||

132 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

Order Download Example 3: Workorder Download from LIS with

Multiple Previous Results
The following workorder message orders four tests: WBC, RBC, HGB, and
RDW for Sample ID, MUL3.
Test WBC contains 4 previous LIS results, RBC contains 1 previous LIS result,
HGB contains 3 previous LIS results and RDW does not contain any previous
LIS results.
NOTE: You can view the displayed LIS Results at the LIS Previous Results
tab at the Request window, which you access by double-selecting the
request at the Review and Edit window.
MSH|^~\&|Atellica Data Manager
|ResultExport|LIS|ResultImport|20080416160705||OML^O33
^OML_O33|1|P|2.5||||||8859/1
PID|1||MUL3||MULname3^MULname2^MULname1||19820521|M|||
|||||||||||||||||||N|||||Human
NTE|1||OML Patient Comment|OC
PV1|1|N|AH
SPM|1|MUL3||Whole blood||||||||||OML Instrument
Comment|||20080409030000||||||||||12 x 75
ORC|PR|MUL3|||||^^^20080409030000^^S||20080416160705||
|JF
OBR|1|MUL3|MUL3|WBC||20080409030000|20080409030000||||
|||||JF||||||20080416160705|||||^^^20080409030000^^S
OBX|1|NM|WBC||1.31||||||F|||20070404111111
OBX|2|NM|WBC||1.32||||||F|||20060404111111
OBX|3|NM|WBC||1.33||||||F|||20060101111111
OBX|4|NM|WBC||1.34||||||F|||20050404111111
ORC|PR|MUL3|||||^^^20080409030000^^S||20080416160705||
|JF
OBR|1|MUL3|MUL3|RBC||20080409030000|20080409030000||||
|||||JF||||||20080416160705|||||^^^20080409030000^^S
OBX|1|NM|RBC||2.31||||||F|||20070404111111
ORC|PR|MUL3|||||^^^20080409030000^^S||20080416160705||
|JF
OBR|1|MUL3|MUL3|HGB||20080409030000|20080409030000||||
|||||JF||||||20080416160705|||||^^^20080409030000^^S
OBX|1|NM|HGB||3.31||||||F|||20070404111111

11314645 Rev. 02 133 / 150

HL7 Version 2.5 Atellica Data Manager

OBX|2|NM|HGB||3.32||||||F|||20070404101111
OBX|3|NM|HGB||3.33||||||F|||20060404
ORC|NW|MUL3|||||^^^20080409030000^^S||20080416160705||
|JF
OBR|1|MUL3|MUL3|RDW||20080409030000|20080409030000||||
|||||JF||||||20080416160705|||||^^^20080409030000^^S

Order Download Acknowledgement Message

The ORL message type acknowledges an order download. If a batch was
used around the received orders, then a batch or order download
acknowledgement is returned.
The order download acknowledgement message is comprised of the
following segments.

The message type of the MSH segment must be “ORL^O34^ORL_O34”.

Order Download Acknowledgement Example

An example of an order download acknowledgement message follows:
MSH|^~\&|DX_LAB|Hematology|WPX||20070305170957||ORL^O3
4^ORL_O34|2|P|2.5||||||8859/1
MSA|AA|161||

Specimen Status Update Message (U03)

The specimen status update message communicates sample status
information and inlabbing events to the LIS. A specimen status update
message is comprised of the following segments

134 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

MSH Segment
The MSH segment is as detailed in the Application Processing Rules section.
See Application Processing Rules, page 137.
The message Type is “SSU^U03^SSU_U03”.

EQU Segment
The EQU segment identifies equipment. The EQU segment consists of the
following:

The applicable fields of the EQU segment follow:

• EQU.1: Sending information provided by the –s command line option.
• EQU.2: Time of the status updated event represented as
YYYYmmddHHMMSS
• EQU.3: Always populated with the value “OP”.

SAC Segment
The SAC segment consists of the following:

11314645 Rev. 02 135 / 150

HL7 Version 2.5 Atellica Data Manager

The applicable fields of the SAC segment follow:

• SAC.3 Container Identifier: Sample.LASStatus or Identifier.
• SAC.8 Container Status: Applicable values include: “I” for identified; “L”
for Left Equipment; “P” for In Position; “O” for In Process; “R” for Process
Completed; “M” for Missing; “X” for Container Unavailable; “U” for
Unknown.
NOTE: Only the I and L values are supported.
• SAC.13 Tray identifier: Sample.LASTrayID.
• SAC.14 Position In Tray: Sample.LASTRayPosition.
• SAC.15 Location: A repeated field. Field One is always
Sample.LASGeneralArea.
The subsequent fields depend on the first as follows:
st
1 Location field 2nd Location Field 3rd Location Field 4th Location Field

(LAS General Area)

CS Shelf Door Area
MT Gate (or blank)
SC Gate
OT Gate

Shelf |"Shelf"^SampleLASStatus/LASShelf|
Door |"Door"^SampleLASStatus/LASDoor|
Area |"Area"^SampleLASStatus/LASArea|
Gate |"Gate"^SampleLASStatus/LASGate|

Specimen Status Update Message Example

MSH|^~\&|Atellica Data Manager
|ResultExport|LIMS|ResultImport|20070305170957||SSU^U0
3^SSU_U03|12|P|2.5||||||8859/1|ACK^U03^ACK
EQU|Atellica Data Manager|20070305171000|OP|
SAC|||3421388|||||L|||||Tray1|20|CS~Shelf^14~Door^5~Ar
ea^7

136 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

Specimen Status Acknowledgement Message

This message acknowledges a specimen status update. The specimen
status acknowledgement message is comprised of the following segments.

MSH Segment
The MSH segment is as detailed in the Application Processing Rules
section. See Application Processing Rules below.
The MSH message type is “ACK^U03^ACK”.

EQU Segment
The EQU segment would be a copy of that sent in the SSU message.

Specimen Status Acknowledgement Message Example

MSH|^~\&|LIMS|ResultImport|Atellica Data Manager
|ResultExport|20070305170957||ACK^U03^ACK|2|P|2.5|||||
|8859/1 MSA|AA|12||

Application Processing Rules

This mhl7 translator supports the original HL-7 acknowledgement rules.
To transmit an acknowledgement, a message is sent, which consists of an
MSH segment followed by an MSA segment.
The MSH segment consists of and is formatted as follows:
NOTE: In the following table, the value “R” in the OPT column indicates
that the field is required:

SEQ DT OPT RP# Element Name Application

1 ST R Field Separator “I”’
2 ST R Encoding Characters “^~&”’
3 ST O Sending Application Sending
Application
4 ST O Sending Facility Sending Facility
5 ST O Receiving Receiving
Application Application
6 ST O Receiving Facility Receiving Facility

11314645 Rev. 02 137 / 150

HL7 Version 2.5 Atellica Data Manager

SEQ DT OPT RP# Element Name Application

7 ST O Date/Time Of Current Date/
Message Time
8 ST O Security --
9 CM R Message Type Message Type
10 ST R Message Control ID Message control
id
11 ID R Processing ID P
12 ID R Version ID 2.5
13 NM O Sequence Number Sequence
Number
14 ST O Continuation Pointer -
15 ID O Accept
Acknowledgement
Type
16 ID O Application
Acknowledgement
Type
17 ID O Country Code
18 ID O Character Set 8859/1

The applicable fields of the MSH segment are as follows:

• MSH.1 Field Separator: Required. Always populated with the value “I”.
• MSH.2 Encoding Characters: Required. Always populated with the
value “^~\&”.
• MSH.3 Sending Application: See the -i option in Translator Specific
Options, page 113.
• MSH.4 Sending Facility: See the -i option in Translator Specific Options,
page 113.
• MSH.5 Receiving Application: See the -r option in Translator Specific
Options, page 113.
• MSH.6 Receiving Facility: See the -r option in Translator Specific
Options, page 113.
• MSH.9 Message Type: Required. Message type must be
“ACK^message_type^ACK”.
• MSH.10 Message Control ID: Required. Unique identifier for each
message. The mhl7 translator internally maintains a monotonically
incremented counter, which supplies this value. The actual start value
is irrelevant, but each message must use a different value.
• MSH.11 Processing ID: Required. Always populated with the value “P”.

138 / 150 11314645 Rev. 02

Atellica Data Manager HL7 Version 2.5

• MSH.12 Version: Required. Populated with the value “2.5”.

• NOTE: The mhl7 translator echoes the version number of the sender in
response messages. If 2.5 was sent, then 2.5 is sent in response.
• MSH.13 Sequence Number: Not supported.
• MSH.18 Character Set: Required. Populated with the value “8859/1”.

MSA Segment
The MSA segment consists of and is formatted as follows:

SEQ DT OPT RP# Element Name Application

1 ID R Acknowledgement Acknowledge
Code Code
2 ST R Message Control ID Echo Message
Control ID from
initiating
message
3 ST O Text Message Error Message
4 NM O Expected Sequence _
Number
5 ID O Delayed _
Acknowledgement
Type
6 CE O Error Condition _

The applicable field of the MSA segment is:

MSA.1 Acknowledgment Code: Required. Populated with the value “AA” to
indicate acceptance or with “AR” to indicate rejection of the last message.
Any value other than AA indicates non acceptance
NOTE: If an HL7 Acknowledge message is received when one is not
expected then it is simply ignored

Handling of Unrecognized Messages

If the mhl7 translator receives a HL7 message that is not one of those
detailed in the Message Grammar sections above or is not a HL7
acknowledgement message as detailed above, the translator rejects the
message with an acknowledgement code of AR.
If the Version ID received is not “2.5,” then the received message is
rejected.

11314645 Rev. 02 139 / 150

HL7 Version 2.5 Atellica Data Manager

Handling of Timeouts
The following only applies when mhl7 is configured to listen on a TCP/IP
port specified by the –s option
• If Client (LIS) connects to the mhl7 listening port but no message
exchange occurs for the time specified by the client idle timeout, –c,
then the translator closes the socket and reverts to listening for
subsequent connections. The LIS must connect again.
NOTE: The mhl7 only permits one connection to the socket, any
connections made to the LIS when one is already in place are closed
immediately.
• When results are being uploaded, the timeout value specified by the –t
command line option is used. If the LIS does not respond in this time,
then the message is not considered to have been sent.
• If an acknowledgement is received when not expected, the
acknowledgement is ignored.
When the mhl7 is configured as a TCP/IP Client, that is, when it connects to
a socket at which the LIS is listening, the need for timeouts does not exist
because the LIS is providing the connection point.
Two translator record time-out values can be configured:
• Application interface timeout. Required field. Indicates the maximum
time interval between the Atellica DM software requesting something
of the mhl7 translator and the receipt of a response to that request
from the mhl7. When a timeout occurs, the Atellica DM software does
not mark the initiating message (result upload or status updated) as
having been sent. The default is 105.
• Optional external interface timeout. Messages initiated by an external
application. This value must always be less than the application
interface timeout value.
NOTE: The mhl7 translator does not support the HL7 sequence number
protocol. Each message is identified through the Message Control ID value
(MSH.10).
The mhl7 translator does not support the HL7 enhanced acknowledgement
rules.
Observation Priority is not indicated in OBR.5, but is indicated in
OBR.27.1.6.

140 / 150 11314645 Rev. 02

9 Serial Connection

The serial inputs on the multiple port terminal servers require a cable that
terminates with an RJ45 connector. For a serial-connected LIS, it is
necessary to create a custom adapter in order to communicate with the
Terminal Server. RJ45-to-DB9 and RJ45-to-DB25 adapter kits are shipped
with each system. When making these custom adapters, refer to the
following diagram of the pinout for the RJ45 serial ports on the terminal
servers.

Description Part Number SMN Number

LIS Adapter (RJ45-to-DB9) 615-4187-01 10328539
LIS Adapter (RJ45-to-DB25) 615-4187-02 10317239

11314645 Rev. 02 141 / 150

Serial Connection Atellica Data Manager

142 / 150 11314645 Rev. 02

10 ASCII Character Codes

Character ASCII Character ASCII Character ASCII

Code Code Code
(Hexa- (Hexa- (Hexa-
decimal) decimal) decimal)
NUL 00 + 2B V 56
SOH 01 , 2C W 57
STX 02 - 2D X 58
ETX 03 . 2E Y 59
EOT 04 / 2F Z 5A
ENQ 05 0 30 [ 5B
ACK 06 1 31 \ 5C
BEL 07 2 32 ] 5D
BS 08 3 33 ^ 5E
HT 09 4 34 _ 5F
LF 0A 5 35 ‘ 60
VT 0B 6 36 a 61
FF 0C 7 37 b 62
CR 0D 8 38 c 63
SO 0E 9 39 d 64
SI 0F : 3A e 65
DLE 10 ; 3B f 66
DC 1 11 < 3C g 67
(X_ON)
DC 2 12 = 3D h 68
(TAPE)
DC 3 13 > 3E i 69
(X_OFF)
DC 14 ? 3F j 6A
4(TAPE)
NAK 15 @ 40 k 6B
SYN 16 A 41 l 6C
ETB 17 B 42 m 6D
CAN 18 C 43 n 6E

11314645 Rev. 02 143 / 150

ASCII Character Codes Atellica Data Manager

Character ASCII Character ASCII Character ASCII

Code Code Code
(Hexa- (Hexa- (Hexa-
decimal) decimal) decimal)
EM 19 D 44 o 6F
SUB 1A E 45 p 70
ESC 1B F 46 q 71
FS 1C G 47 r 72
GS 1D H 48 s 73
RS 1E I 49 t 74
US 1F J 4A u 75
SP 20 K 4B v 76
! 21 L 4C w 77
" 22 M 4D x 78
# 23 N 4E y 79
$ 24 O 4F z 7A
% 25 P 50 { 7B
& 26 Q 51 | 7C
’ 27 R 52 } (Alt Mod) 7D
( 28 S 53 ~ 7E
) 29 T 54 DEL (Rub 7F
Out)
* 2A U 55 DEFAULT 7F
LRC*

144 / 150 11314645 Rev. 02

11 Multiple LIS Connections

You can connect multiple LIS to one Atellica Data Manager server.
The protocols in this chapter support 1 or multiple LIS. Each LIS connection
can consist of 1 or 2 communication channels. The following connection
options are available with 2 LIS connections:

LIS1 LIS 2

Option 1 1 TCP connection Inbound 1 TCP connection Inbound

and Outbound together and Outbound together
Option 2 2 TCP Connections 2 TCP Connections
• Inbound • Inbound
• Outbound • Outbound
Option 3 1 Serial connection Inbound 1 Serial connection Inbound
and Outbound together and Outbound together
Option 4 2 Serial Connections 2 Serial Connections
• Inbound • Inbound
• Outbound • Outbound

NOTE: Other combinations are possible if LIS 1 uses serial and LIS 2
uses TCP.
Each LIS is fully configurable and independent of the other, except for the
following relationship logic. The term Requesting LIS refers to the LIS from
which a request was sent, or from where the data originated:
• Sample IDs are the unique identifier in the Atellica Data Manager
software, so Sample IDs must be unique for all LIS.
• The Atellica Data Manager software is designed to operate with unique
Patient IDs across all connected LIS. As the LIS is considered the master
system from which the most current data originates, the
Atellica Data Manager software always accepts updates to patient
records from the originating LIS.
NOTE: If Patient IDs might be duplicated from different LIS, then you
should turn off the demographics download to the instrument option.
The following logic is used for Sample IDs reused across multiple LIS:
• If a Sample ID is reused and the Patient ID is different, then the
Atellica Data Manager rejects the order.

11314645 Rev. 02 145 / 150

Multiple LIS Connections Atellica Data Manager

• If the Sample ID is reused and the Patient ID is the same then the
following occurs:
○ If the LIS is the same as the original LIS then the Atellica DM
software updates the Demographics.
○ If the LIS is different than the original LIS then the Atellica DM
software rejects the Demographic updates.

Uploading of Results
Each time a sample is sent from LIS to the Atellica DM system, the sample
is tagged with a Requesting LIS. When results are generated, the
Atellica DM system only uploads the results to the Requesting LIS.
An operator can upload test results to multiple LIS if required. You can
configure this to be done automatically or do it one time only.
NOTE: Once the sample is tagged in the Atellica DM software for a
Requesting LIS this also will accommodate add-ons and reruns. All reruns
and reflex tests will be uploaded to the Requesting LIS.

Quality Control
The Dynamically administer QC Instruments checkbox is selected by
default.
When selected, if an LIS sends a workorder for a sample, the sample is
tagged with the Requesting LIS. Whenever an instrument reports a result
for that test, the result is uploaded to the Requesting LIS and the
Atellica DM software also tags that instrument as a QC Instrument for that
LIS. All subsequent QC results from that instrument are uploaded to that
LIS.
NOTE: QC uploading configuration is automatically set up and controlled
by the Atellica Data Manager software as normal test processing occurs.
For results sent to an LIS from a specific instrument, all QC information
from that instrument is also sent.
An operator can upload QC results to multiple LIS if required. You can
configure this to be done automatically, or do it one time only.

LIS Channel for the Biorad Program

You can purchase an additional LIS communication channel, which allows
the Atellica DM software to communicate with a Biorad program. This
enables QC data to flow from the Atellica DM server to Biorad servers in
real time, as opposed to programming the Atellica Data Manager server to
export files in Biorad format every <n> minutes.

146 / 150 11314645 Rev. 02

12 Hard-coded Comments

In certain instances, the Atellica DM system can add hard-coded

comments. The following sections explain these by comment type.

Sample Comment
• Results discarded - sample reuse time has elapsed for sample
'<SampleIdentifier>' ('<InstrumentName>' - '<DateTime>')
• '<LASChannelName>' (flag code '<LASFlagCode>') :
<LASFlagExpansion>

Result Instrument Comment

• LIS Modified by '<LISChannelName>'

Result Parse Comment & QC Result Parse Comment

• Not a number; no computation performed (<AdditionalText>)
• Unknown result choice (<AdditionalText>)
Possible values of the <AdditionalText> from the comments above are:
• Comma not allowed in numeric result input
• Unit conversion error: source unit not found
• Unit conversion error: Target unit not found
• No unit conversion possible from <UnitName> to <UnitName>
• Cannot determine mantissa and exponent without an input value.
• <Value> is not a valid decimal value
• Cannot determine mantissa and exponent without an error
indication.
• Unit record '<UnitName>' not available
• For test '<TestName>', result choice '<ResultChoice>' is ambiguous.
Legal choices are '<ResultChoiceList>'
• For test '<TestName>', result choice '<ResultChoice>' is illegal. Legal
choices are '<ResultChoiceList>'

Result User Comment

Cancelled on LAS : '<UserSuppliedText>'

Patient Comment, QC Result Instrument Comment, QC Result User

Comment, and Result Range Comment
No hard-coded comments are added by the Atellica DM software.

11314645 Rev. 02 147 / 150

Hard-coded Comments Atellica Data Manager

148 / 150 11314645 Rev. 02

13 CentraLink Systems

If you are migrating from a CentraLink® system to the Atellica DM, the
information in this chapter may be applicable.
In certain instances, the CentraLink system can add hard-coded comments.
The following sections explain these by comment type.

Major Changes from CentraLink Version 15 to

Version 16
The CentraLink system software version 16 does not support the Group
message by Lot option, which allows the upload of QC results to the LIS
grouped by lot. CentraLink software version 16 supports the upload of
QC results grouped by population.

11314645 Rev. 02 149 / 150

 CentraLink Systems Atellica Data Manager

150

150 / 150 11314645 Rev. 02