cobas® 8000 data manager

Host Interface Manual

©2012 Roche

Roche Diagnostics Ltd

CH-6343Rotkreuz
Switzerland
www.roche.com
 cobas® 8000 data manager
cobas® 8000 instrument

Revision history

Manual version Software version Revision date Main changes

1.00.00 (revision 1) 1.00.00 August 2009 First version
1.00 r2 1.00.01 December 2009 Updated with enhancements and corrections. (Revision 2)
1.01 (revision 1) 1.01.00 June 2010 Support for e602, calibration results, result query, order query, EP-
17A.
1.01 (revision 2) 1.01.00 June 2010 Branding and trademark corrections.
1.01 (revision 3) 1.01.01 August 2010 Enhanced support for acknowledgement messages.
1.01 (revision 4) 1.01.01 September 2010 Revised description of Analytical Unit ID, and other minor
revisions.
1.02 (revision 1) 1.02.00 March 2011 o Further enhanced support for acknowledgement messages.
o Full Analytical Unit ID editing permitted.
o Support for c702
1.02.03 (revision 1) 1.02.03 August 2011 o Sequence mode: identifying samples by sequence number.
o Caution as regards serum index tests.
1.02.05 (revision 1) 1.02.05 March 2012 o Data added to quality control and calibration results to
(preliminary draft) improve traceability. (HL7 only.)

e For a fuller list of changes in this version, and for guidance about changes to the interface,
see Upgrading to version 1.02.05 with HL7 on page E-106.

Check the changes to the host interface before performing the upgrade
Before you upgrade from an earlier version, check everything in the list of difference to the
CAUTION previous versions. Make sure that the host can correctly read the messages from, and
construct messages for, the data manager.

Editor’s note

Every effort has been made to ensure that the information contained in this manual is
accurate at the time of printing.
Roche Diagnostics Ltd. reserves the right to make any further required changes to
software without prior notice. Such changes may not immediately be reflected in this
document.

Intended use This document is intended for the users of cobas® 8000 data manager application,
Version 1.02.05.

Copyright © 2005-2012 Roche Diagnostics Ltd. All rights reserved.

Trademarks Recognized trademarks:

o COBAS, MODULAR, and MODULAR ANALYTICS EVO are trademarks of
Roche.
o All other product names and trademarks are the property of their respective
owners.

Feedback Every effort has been made to ensure that this guide fulfils its intended purpose as
mentioned above. All feedback on any aspect of this guide is welcome and will be
Roche Diagnostics
3 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager
cobas® 8000 instrument

considered during updates. Please contact your Roche representative, should you
have any such feedback.

Complies with the IVD Directive 98/79/EC.

Contact addresses

Manufacturer Roche Diagnostics Ltd.

CH-6343 Rotkreuz
Switzerland
www.roche-diagnostics.com

US Distribution Roche Diagnostics Corporation

9115 Hague Road
PO Box 50457
Indianapolis, IN 46250-0457
USA

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) 4
cobas® 8000 data manager

Table of contents

Host communication settings and cables B–47

Revision history 3
Editor’s note 3 ASTM Reference Part C
Contact addresses 4
Table of contents 5
6 ASTM protocol (LIS2 - A2)
Using this manual 7
Background to the ASTM protocol C–5
Conventions used in this manual 7
Communication processing layers C–5
Safety information classification 9
ASTM lower layer C–6
Safety information 9
ASTM syntax C–8
Checksum calculation / message frame C–11
Introduction Part A
7 ASTM text content (LIS2 - A2)
Record levels C–15
1 Overview
Messages used in host communication C–15
Purpose and scope A–5
Record description C–18
Who this manual is for A–5
Message Header Record C–19
Content A–5
Patient Information Record C–21
Order Record C–22
2 System architecture
Comment Record (following Order Record) C–26
Overview A–9
Result Record C–27
LIS communications A–10
Comment Record (following Result Record) C–31
Sample types A–11
Query Record (Request Information Record) C–33
Processing samples A–11
Photometric Calibration Result M(PCR) C–36
Repeat, rerun, and reflex tests A–14
ISE Calibration Result Record - M(ICR) C–37
E-module (immunology) Calibration Result Record -
Interface description Part B M(ECR) C–39
Message Termination Record C–41
3 Sample Processing
Batch and realtime processing B–5 HL7 Reference Part D
Identifying samples on the instrument B–7
Returning results to the host B–7
8 HL7 protocol
Communication types B–9
HL7 protocol lower level D–5
Message flow batch download from host B–14
Overview of HL7 D–5
Message flow for TS Inquiry from instrument / data
Physical communication D–5
manager B–16
Message flow for batch sample, upload by sample
9 HL7 text content
B–18
HL7 messages D–9
HL7 Segment description D–11
4 Host Communication Settings
Message Header Segment - MSH D–12
Starting and stopping the host connection B–21
Message Acknowledgement Segment - MSA D–14
Configuring the data manager B–23
Patient Identification Segment - PID D–14
Identifier of the analytical unit sent to host B–30
Specimen Segment - SPM for patient and quality
Getting a trace file from the data manager B–32
control results D–15
Configuring the Control Unit B–33
Specimen Segment - SPM for calibration results
Getting a trace file from the Control Unit B–40
D–18
Identifying patient samples by sequence number
Specimen Container Detail Segment - SAC D–19
B–43
Observation Request Segment - OBR D–19
Chart of configuration settings B–44
Timing Quantity Segment - TQ1 D–20
Observation Result Segment - OBX (for patient
5 Physical layer specifications
results) D–22
Text encodings B–47
Observation Result Segment - OBX (for QC results)
Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) 5
 cobas® 8000 data manager

D–26 17 Text encoding tables

Observation Result Segment - OBX (for calibration ASCII table E–111
results) D–29 Western European characters in UTF-8 E–112
Test Code Detail Segment - TCD D–35
Substance Identifier Segment - SID D–35
Comment Segment - NTE D–36
Query Parameter Segment - QPD (for a test selection
inquiry) D–37
Query Parameter Segment - QPD (for a Result Query)
D–39
Query Parameter Segment - QPD (for an Order
Query) D–40
Response Control Parameter Segment - RCP D–41
Equipment Detail Segment - EQU D–41
Equipment Command Segment - ECD D–42

10 HL7 Acknowledgement handling

HL7 acknowledgement messages D–45
Messages from the data manager D–45
Sending messages from host to the data manager
D–49

Appendices Part E

11 Data Alarms
The meaning of the data alarms E–5
Alarms for Routine or STAT samples E–12
Alarms for Control and Calibration samples E–16

12 Instrument alarms
Instrument alarms E–23

13 Using MODULAR PRE-ANALYTICS

Using a MODULAR PRE-ANALYTICS E–41

14 Identifying patient samples by sequence number

Identifying samples E–47
Identifying patient samples by sequence number
E–47
Important information for using sequence numbers
E–49
Using sample sequence numbers in ASTM E–50
Using sample sequence numbers in HL7 E–51

15 Communication examples
Example communication trace files E–57
ASTM trace files E–57
HL7 trace files E–71

16 Preparing the host communication

Differences to the MODULAR ANALYTICS EVO
analyzer / cobas® 6000 analyzer series E–91
Upgrading to version 1.02.05 with ASTM E–106
Upgrading to version 1.02.05 with HL7 E–106

Roche Diagnostics
6 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager
cobas® 8000 instrument

Using this manual

The cobas® 8000 data manager is a core component of the cobas® 8000 modular
analyzer series, which supports several analytical modules. The analytical modules
installed may vary from installation to installation. The functionality available may
depend in some cases on which modules are currently installed.

Conventions used in this manual

Following are symbols and conventions used in this manual.

Symbols The following symbols may be used to draw your attention to important information:

Symbol Meaning
e Cross reference

Note

Abbreviations The following abbreviations are used:

Abbreviation Definition
A
ADC apparent diffusion coefficient
ANSI American National Standards Institute
ASCII American Standard Code for Information Interchange
ASTM ASTM International, originally known as the American Society for
Testing and Materials (ASTM), in particular the LIS2-A2 standards
E1381-91 (Specification for Low-Level Protocol to Transfer Messages
Between Clinical Laboratory Instruments and Computer Systems)
and E1394-91 (Standard Specifications for Transferring Information
Between Clinical Instruments and Computer Systems).
C
cc cubic centimeter
Cl Chlorine
CLSI Clinical and Laboratory Standards Institute (formerly NCCLS)
COI Cut-off index
CU Control Unit
D
data manager Used as a synonym for cobas® 8000 data manager.
DIL Diluent
E
EC European community
e.g. exempli gratia – for example
E.I.U. essential information upload
EMF electromotive force
EP17-A Protocols for Determination of Limits of Detection and Limits of
Quantitation; Approved Guideline (NCCLS standard)
Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) 7
 cobas® 8000 data manager
cobas® 8000 instrument

Abbreviation Definition
F
FIFO First in first out
H
HIS Hospital Information System
HL-7 Health Level 7
I
i.e. id est – that is to say
IS Internal Standard (ISE module)
ISE ion selective electrode
K
K Potassium
L
LIS Laboratory Information System
LoB Limit of Blank
LoD Limit of Detection
LoQ Limit of Quantitation
LLD liquid level detection
N
n/a not applicable
Na sodium
NB Nota bene (note well)
NCCLS National Committee for Clinical Laboratory Standards (former name
for CLSI)
Q
QC Quality control
R
REF Reference solution for ISE module
S
SD standard deviation
SID Sample ID
SOP Standard operating procedure
STAT short turn-around time
T
TCP/IP Transmission Control Protocol/Internet Protocol
TS Test Selection
U
UTF-8 8-bit Unicode Transformation Format
W
WAM Work Area Manager
X
XML Extensible Markup Language
XSLT Extensible Stylesheet Language
XSLT Extensible Stylesheet Language Transformation

Roche Diagnostics
8 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager
cobas® 8000 instrument

Safety information classification

Safety messages are classified according to ANSI Z535.6. The following classifications
are used, according to the level of seriousness of the hazard:
The safety alert symbol by itself (without a signal word) is used to promote awareness
to hazards which are generic or to direct the reader to safety information provided
elsewhere in the document.
The following symbols and signal words are used for specific hazards:

Warning
Indicates a potentially dangerous situation which, if ignored, may lead to fatal or severe
WARNING injuries.

Caution
Indicates a potentially dangerous situation which, if ignored, may lead to injuries and/or
CAUTION damage to property.

NOTICE Notice
Indicates a message not related to personal injury.

According to ANSI Z536.6 there is an additional hazard level: DANGER. Danger

indicates a hazardous situation which, if not avoided, will result in death or serious
injury. This level is not used in Roche Diagnostics Operator’s Manuals. In line with
the Roche Diagnostics Product Risk Management Policy, a risk of this degree or level
of hazard seriousness is not accepted.

Safety information

System safety

Failure to observe the following safety information may result in incorrect results,
data corruption, and data losses.

Incorrect or corrupt data resulting from incorrect operation, the use of wrong
components, or poor security measures
CAUTION o Use only computers, monitors, printers, and accessories recommended by the
manufacturer.
o Service your computer regularly (defragment the hard disk; and check for system error
entries in the event display).
o Install and run a firewall and anti-virus software; keep them up-to-date. This will
require third-party software.

Incorrect or corrupt data due to unauthorized access

Access to your data and the configuration should only be granted to authorized
CAUTION experts.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) 9
 cobas® 8000 data manager
cobas® 8000 instrument

Data security

Data loss
Back up your data at regular intervals (ideally every day).
CAUTION

Maintenance

Data loss or damage to the system due to power failure.

Ensure regular maintenance of the uninterruptible power supply.
CAUTION

Laboratory workflows

Incorrect results due to lack of calibration and quality control

Interrupt the analysis of patient samples if you change the reagent until the
WARNING instrument has been recalibrated and quality-controlled.

Incorrect results due to expired calibration and quality controls

Perform regular quality controls and calibrations.
WARNING

Incorrect results due to incorrect entry

Ensure that manually entered data is correct.
WARNING

Danger of samples being mixed up due to use of tubes not labeled with barcodes
If possible, always use primary and secondary tubes labeled with barcodes in
CAUTION connection with barcode readers, and instruct the laboratory staff as to correct
handling.

Danger of samples being mixed up due to incorrect assignment of the barcode to

the tube
CAUTION Ensure that assignment of the barcode to the tube is correct during aliquoting. Use
the SOP function to alert the laboratory staff to this obligation. For details of the SOP
function, see the cobas® 8000 modular analyzer series Operator’s Manual.

Incorrect results due to lack of knowledge of the Standard Operating Procedures

Use the SOP function of the system to give laboratory staff access to written
CAUTION instructions (SOP) while they work. For details of the SOP function, see the cobas®
8000 modular analyzer series Operator’s Manual.

Roche Diagnostics
10 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager
cobas® 8000 instrument

Incorrect results due to incomplete patient data

Patient results can only be correctly validated if all relevant patient data is stored in
CAUTION the system. In case of incomplete transmission of patient data through the HIS
Hospital Information System, tests may have to be repeated.

Unreliable validation due to unauthorized changes to the validation and

calculation rules.
CAUTION The manufacturer shall not be liable for any consequences whatsoever resulting from
subsequent, unauthorized modifications to accepted medical validation and
calculation rules included in the system upon customer request.

Third-party software

Malfunctions and incorrect results due to third-party software

The installation of third-party software that has not been approved by Roche
CAUTION Diagnostics may lead to malfunctions. Do not install any unapproved software.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) 11
 cobas® 8000 data manager
cobas® 8000 instrument

Roche Diagnostics
12 Host Interface Manual · Version 1.02.05 (revision 1)
 Introduction A

1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
2 System architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
cobas® 8000 data manager 1 Overview
®
cobas 8000 instrument Table of contents

Overview

This section gives a basic overview of the purpose and scope of this manual.

In this chapter Chapter 1

Purpose and scope .......................................................................................................... A-5
Who this manual is for ................................................................................................... A-5
Content ............................................................................................................................. A-5

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) A-3
1 Overview cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
A-4 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 1 Overview
®
cobas 8000 instrument Purpose and scope

Purpose and scope

This document details the specifications for the cobas® 8000 data manager host
interface. This interface regulates data transmissions between the data manager and
the hospital and laboratory information system.
Therefore, this manual gives programmers a description of the basic operational
features of the data manager, in order to enable them to connect to a host system,
such as Laboratory Information Systems, Hospital Information Systems or Work
Area Manager.
Questions concerning this document should be referred to Technical Support. Please
refer to the cobas® 8000 modular analyzer series Operator’s Manual for more detailed
information on the use of cobas® 8000 data manager.
The main part of this document consists of a series of tables that show the
information needed to successfully interface to the system. The basic concept of data
transfer in this interface is the exchange of data and control frames between the host
system and the analyzer.

Who this manual is for

This manual is written for:

o Developers of Hospital Information Systems / Laboratory Information Systems
(HIS/LIS), who need to create programs that connect to the cobas® 8000 data
manager.
o Authorized Roche Diagnostics personnel who need to configure or troubleshoot
the host communications of the cobas® 8000 data manager.

Content

This document gives the reader a basic understanding of the system operation with a
host, and describes the following:
o Basic System Architecture
o Sample Processing
o Sample Types
o Rerun Modes
o Test Selections
o Operational Modes
o Types of messages sent and received
o ASTM and HL7 protocol support

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) A-5
1 Overview cobas® 8000 data manager
Content cobas® 8000 instrument

Roche Diagnostics
A-6 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 2 System architecture
®
cobas 8000 instrument Table of contents

System architecture
Overview of the cobas® 8000 data manager and cobas®
8000 instrument

This chapter describes the basic system architecture of the cobas® 8000 modular
analyzer series, and the role that cobas® 8000 data manager plays in it. This includes
how samples are identified and handled, and how test information is supplied by the
host.

In this chapter Chapter 2

Overview ........................................................................................................................... A-9
System overview ........................................................................................................ A-9
Overview of modules .............................................................................................. A-10
LIS communications ..................................................................................................... A-10
Sample types .................................................................................................................. A-11
Processing samples ........................................................................................................ A-11
Introducing sample tubes and racks .................................................................... A-11
Barcodes ................................................................................................................... A-12
Test selection ........................................................................................................... A-12
Repeat, rerun, and reflex tests ..................................................................................... A-14
Repeat test ................................................................................................................ A-14
Rerun test ................................................................................................................. A-14
Reflex test ................................................................................................................. A-14
Request for rerun or reflex tests ............................................................................ A-14
Handling multiple test results ............................................................................... A-15

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) A-7
2 System architecture cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
A-8 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 2 System architecture
®
cobas 8000 instrument Overview

Overview

The cobas® 8000 data manager is an integral part of the cobas® 8000 modular
analyzer series. The cobas® 8000 modular analyzer series performs medical tests on
sample material taken from patients. It measures the concentration of certain
compounds or other substances in the samples. It sends the results of the medical
tests back to the host, which could be a Laboratory Information System (LIS) or
Work Area Manager (WAM).
This section provides an overview of the basic architecture of the cobas® 8000
modular analyzer series, and discusses some specialized items of interest pertaining
to the analytical system.

System overview

The cobas® 8000 modular analyzer series consists of two types of devices:
o The data manager. This is software which runs on a PC. It allows operators to
view and edit the results of analysis, allows remote operator interaction with the
system, including configuration. The data manager also handles communication
with an external host system such as a LIS.
o An instrument that consists of:
O Several analytical modules, that physically measure the samples using various
reagents
O A Control Unit. This is software, running on a PC, that controls the operation
of the analytical modules. This has a graphical user interface that an operator
or administrator can use to control and configure the instrument and its
modules.
The data manager is also connected to Roche Diagnostics’ e-services via cobas® link.

ASTM / I
A HL7 B C D

J
E

F G H

A Host (LIS, WAM etc.) E cobas® 8000 Control Unit I cobas® 8000 modular analyzer series
®
B cobas 8000 data manager F ®
cobas 8000 analytical modules J cobas® 8000 instrument
® ®
C cobas link G cobas 8000 analytical modules
D Roche Diagnostics e-services H cobas® 8000 analytical modules

Figure A-1 Overview of the cobas® 8000 data manager system

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) A-9
2 System architecture cobas® 8000 data manager
LIS communications cobas® 8000 instrument

Overview of modules

The cobas® 8000 modular analyzer series supports several types of analyzer modules,
as outlined below. Each installation may contain one, none, or several of each type of
module.

ISE module The ISE module, or Ion-Sensitive-Diode module, performs clinical chemistry tests
for analyzing levels of the electrolytes Na, Cl, and K.

C-module The C-modules, c502, c701, and c702, perform clinical chemistry tests using
photometry.

E-module The E-module, e602 or Elecsys, performs immunological tests.

LIS communications

The LIS and data manager can communicate by

o HL7 over a TCP/IP network connection
o ASTM over a TCP/IP network connection
o ASTM over a serial connection

Details e For details of how to select a connection, see Starting and stopping the host connection on
page B-21.
e For details of the connections, see Host communication settings and cables on page B-47.
e For details of the HL7 protocol used, see Chapter 8 HL7 protocol and Chapter 9 HL7 text
content.
e For details of the ASTM protocol used, see Chapter 6 ASTM protocol (LIS2 - A2) and
Chapter 7 ASTM text content (LIS2 - A2).

HL7 over a network connection gives best performance

Using HL7 over a network connection gives the best performance. Especially for existing
ASTM host implementations, an ASTM connection over a network also gives an acceptable
outcome.
However, the serial interface via ASTM is performance-limited and is not recommended for
the cobas® 8000 modular analyzer series and high-throughput systems. Even though
smaller instruments will still work via ASTM over serial connection, this might lead to
potential conflicts of query / request download and result upload.
Network connection is required for systems with more then two C-701 (including ISE)
modules, where the number of samples per hour and tests per sample is very high.

Text encoding Messages are sent using UTF-8 encoding.

Roche Diagnostics
A-10 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 2 System architecture
®
cobas 8000 instrument Sample types

Sample types

The cobas® 8000 data manager supports the use of several types of samples, including
serum, urine, cerebrospinal Fluid, and supernatant. For full information on
supported sample types, see the cobas® 8000 modular analyzer series Operator’s
Manual.
Where required, the sample type is passed in the communication between the
HIS/LIS and data manager.

Processing samples

Sample material is supplied to the instrument in so-called sample containers.

Sample cups, tubes and racks Sample containers are available in different shapes: tubes or cups. These are
mounted, if necessary, on sample tubes of a standard 16mm size. The sample tubes
are placed in racks, which hold up to 5 sample tubes each. These racks allow the
instrument to automate the movement and processing of the samples.
If necessary, the sample’s actual container or cup size is indicated in communications
between the HIS/LIS and the data manager.

Dilution As part of the pre-analytical process, some samples are diluted before being loaded
onto the instrument, or are automatically diluted by the instrument before testing.
Depending on the tests and the results, some samples are diluted before the tests are
repeated. Where necessary, the sample’s dilution factor is passed in communications
between the LIS and the data manager.

Introducing sample tubes and racks

The sample tubes are placed in 5-position racks, which laboratory staff place in the
instrument.
There are different kinds of color-coded racks for routine samples, STAT (Short Turn
Around Time) samples, Quality Control samples, and so on. Complete information
on the types of tubes used, and the types of racks they are mounted in, is given in the
cobas® 8000 modular analyzer series Operator’s Manual.

Routine sample racks Routine sample tubes or cups are placed on gray barcoded racks, which are then
loaded into the loader located on the side of the cobas® 8000 instrument. This loader
consists of two trays, each of which can hold up to 15 5-position racks. Each tray
feeds into a buffer area of the same size. This gives a theoretical maximum of (5 tubes
x 15 racks x 2 trays x 2 in the loading and waiting area =) 300 waiting tubes.

STAT sample racks STAT sample tubes are placed on red barcoded racks, then loaded onto the STAT
port, beside the loader. These racks take a higher priority in the cobas® 8000
instrument than the racks on the loader.

Other sample racks Other rack types, such as for Quality Control samples, Calibration samples, and
manual rerun samples, have their own rack types, which are introduced in the same
way as routine sample racks.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) A-11
2 System architecture cobas® 8000 data manager
Processing samples cobas® 8000 instrument

Barcodes

The cobas® 8000 modular analyzer series reads the barcode of each sample
immediately after the tube is put into the instrument. It identifies the sample from the
combination of the barcode and the sample type (serum, urine etc.). Therefore if any
two samples have the same sample type, they must have different barcodes, even if
they are for the same patient, or they are put onto the instrument at different times.

Barcodes All the racks are passed one-by-one to the input buffer, which feeds them sequentially
into the system. The cobas® 8000 instrument reads the sample’s barcode, which
contains an alphanumeric string up to 22-characters long. The instrument, host and
data manager use the barcode string as a unique identifier for the sample, called the
sample ID (SID).

Missing barcodes By default, if the cobas® 8000 instrument cannot read a sample’s barcode, it generates
an error. The operator of the cobas® 8000 instrument can manually enter
information identifying the sample and its sample ID. For more information on this,
see the cobas® 8000 modular analyzer series Operator’s Manual.

Sequence numbers On request, Roche Diagnostics service personnel can reconfigure the cobas® 8000
modular analyzer series instrument to give each sample a sequential number instead
of a barcode. By default the first sample is then 1, the next 2, and so on up to 60,000.
The number of the first sample is configurable.
e For more information on how to use this function, see Chapter 14 Identifying patient
samples by sequence number.

MODULAR PRE-ANALYTICS If a MODULAR PRE-ANALYTICS is used, the samples may lack barcodes. In this
situation, the cobas® 8000 instrument identifies the sample by its position on the
rack, and the rack identifier. The host needs to identify the sample from this
information, and send the Test Selection, including the rack ID and the sample’s
position on the rack, as well as the sample ID.
e For more information on how to use this function, see Using a MODULAR PRE-
ANALYTICS on page E-41.
e To configure the cobas® 8000 instrument to process samples coming from a MODULAR
PRE-ANALYTICS without barcodes, enable the option on the Control Unit in Utility >
System > Data Manager > Test Selection Inquiry Settings > Test Selection Ask in Barcode
Read Error. This is described in Test Selection Ask in Barcode Read Error on page B-38.

Test selection

The instructions telling the cobas® 8000 instrument which test to perform on each
sample (the Test Selection) can come from several sources, depending on the
configuration of the system:
o The host (LIS or WAM), prior to the sample being loaded onto the cobas® 8000
instrument. (“Batch Download”.)
o The host, in response to a query (Test Selection Information Inquiry) initiated by
the cobas® 8000 instrument via data manager. (“Realtime Download”.)
o The cobas® 8000 instrument, as a result of a manually-programmed Test
Selection on the cobas® 8000 instrument by the operator. The test results can be
uploaded to the host.

Roche Diagnostics
A-12 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 2 System architecture
®
cobas 8000 instrument Processing samples

o The cobas® 8000 data manager, as a result of a manually-programmed Test

Selection on data manager by the operator. The test results can be uploaded to the
host.
As users can reconfigure the cobas® 8000 instrument and data manager, the host
must be able to send test selections in response to a query, and handle results from
tests that it has not ordered. Also, it is best to allow a “Batch Download” host
configuration, which downloads test selections without waiting for a query.
e For more details about the order of messages, see Chapter 3 Sample Processing.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) A-13
2 System architecture cobas® 8000 data manager
Repeat, rerun, and reflex tests cobas® 8000 instrument

Repeat, rerun, and reflex tests

In many cases, the results of a test need to be checked, and in some cases this check
leads to an order of further tests. The cobas® 8000 data manager can be configured to
order such add-on tests automatically. Also, medical staff operating the Control Unit
or the data manager might order add-on tests manually. The LIS can also order any
of these kinds of tests, if required.
e For details of how to set repeat, rerun or reflex tests, see the cobas® 8000 modular analyzer
series Operator’s Manual.

Repeat test

Test measurement is done again under the same conditions. A test result will be
verified by repetition of the test by the same methods or a reference method. This
may be done on the cobas® 8000 instrument manually, or on the data manager
automatically.

Rerun test

Test measurement is done again under different conditions. Typically a dilution

factor is changed automatically or manually. This may be ordered by the instrument
or data manager automatically.

Reflex test

Request to perform additional test(s), based on sample test results by customer-

defined algorithms. The data manager may be configured to order the extra tests
automatically. Also the LIS/HIS can send orders for Reflex tests via data manager to
the cobas® 8000 instrument, if corresponding rules are programmed at the LIS.

Use reflex rules either only on the data manager or only on the host
Reflex rules should only be entered either at the data manager or at the host. Do not use
CAUTION Reflex Rules on both the data manager and the host. Using reflex rules on both may cause
abnormal instrument behavior.

Request for rerun or reflex tests

The Control Unit can be configured so that after it completes a test, it automatically
sends an inquiry to data manager, asking for rerun tests.

a To enable requests for rerun or reflex tests

1 On the Start page, set automatic rerun for routine and STAT samples to “Yes”.
2 Navigate to Utilities > Application, and make sure that for the relevant test the
checkbox Automatic Rerun is selected.
3 Navigate to Utility > System > Data Manager > Test Selection Inquiry Settings,
and make sure Automatic Rerun Test Selection is selected.

Roche Diagnostics
A-14 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 2 System architecture
®
cobas 8000 instrument Repeat, rerun, and reflex tests

Handling multiple test results

Results for the original test and the rerun are reported separately to the LIS. The
database on the data manager stores all the results for a test, including the original
result and any results for a repeated or rerun test.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) A-15
2 System architecture cobas® 8000 data manager
Repeat, rerun, and reflex tests cobas® 8000 instrument

Roche Diagnostics
A-16 Host Interface Manual · Version 1.02.05 (revision 1)
 Interface description B

3 Sample Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

4 Host Communication Settings . . . . . . . . . . . . . . . . . . . . . . . . . B-19
5 Physical layer specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-45
cobas® 8000 data manager 3 Sample Processing
®
cobas 8000 instrument Table of contents

Sample Processing
Samples and message flow

This chapter explains how samples are processed in the cobas® 8000 data manager,
and shows the message flow between the cobas® 8000 instrument, cobas® 8000 data
manager and the host.

In this chapter Chapter 3

Batch and realtime processing ........................................................................................ B-5
Batch and realtime and the data manager .............................................................. B-5
Batch and realtime messages .............................................................................. B-5
Batch and realtime modes .................................................................................. B-5
Multiple test selection messages ........................................................................ B-6
Identifying samples on the instrument ......................................................................... B-7
Returning results to the host .......................................................................................... B-7
Passing results automatically to the host ................................................................ B-7
System time and result handling .............................................................................. B-8
EP-17A and the result abnormal flags .................................................................... B-8
Communication types ..................................................................................................... B-9
Communication and message types ........................................................................ B-9
List of messages .................................................................................................... B-9
Communication scenarios ...................................................................................... B-10
Details of message types .......................................................................................... B-11
Query message ................................................................................................... B-11
Sending test selections ....................................................................................... B-12
Sending patient test results ............................................................................... B-12
Result query ........................................................................................................ B-12
Order query ........................................................................................................ B-12
Sending quality control results ........................................................................ B-13
Calibration Data Results ................................................................................... B-13
Masking ............................................................................................................... B-13
Message flow batch download from host ................................................................... B-14
Message flow for TS Inquiry from instrument / data manager ............................... B-16
Message flow for batch sample, upload by sample .................................................... B-18

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-3
3 Sample Processing cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
B-4 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 3 Sample Processing
®
cobas 8000 instrument Batch and realtime processing

Batch and realtime processing

This section gives an overview of the message flow between the cobas® 8000
instrument, data manager and the host, when they send each other information
about samples.

Batch and realtime and the data manager

For each sample, the data manager must have a list of tests to do on the sample. This
is a “Test selection”.
The data manager can send a message to the host to ask for a test selection for a
sample. This message is called a “test selection inquiry” or a “query message”.

Batch and realtime messages

Batch message The host can, at any time, send an unsolicited test selection message for a sample,
even if the data manager has not previously sent a query message for that sample. An
unsolicited test selection message is called a Batch message, Batch order, Batch test
selection, or Batch download.

Realtime message When a host sends a test selection in response to a query message, this message is
called a Realtime message, Realtime order, Realtime test selection or Realtime
download.

Batch and realtime modes

Host systems handle messages test selection downloads in one of three ways:
o Batch mode: all test selection downloads are batch downloads.
o Realtime mode: and all test selection downloads are realtime downloads.
o Mixed mode: the host can send either batch or realtime test selection downloads.

Batch mode A host in batch mode does not respond to test selection queries, and all test selections
are batch downloads. The host has to download the test selections for the samples
before they arrive at the analyzer’s Barcode Reader. This configuration is not
recommended if auto-rerun or reflex tests are needed.

Realtime mode A host in realtime mode always waits for a test selection query. All test selection
download messages are a reaction to previous inquiry and have to be downloaded
within a timeout. Configure the data manager so that it sends a test selection inquiry:
o whenever the data manager receives a test selection request from the cobas® 8000
modular analyzer series,
or
o whenever an operator enters a manual test selection for a sample at the data
manager.
However the data manager is configured, it always accepts batch downloads without
an error message.

Mixed mode A host in mixed mode can either batch test selection downloads or realtime
downloads in response to a test selection query.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-5
3 Sample Processing cobas® 8000 data manager
Batch and realtime processing cobas® 8000 instrument

To work with mixed mode, configure the data manager to send a query to the host
when:
o the data manager receives a test selection request from the Analyzer,
and
o it can not find any open test selections for the sample in its internal database.
Therefore, if the operator has previously input a manual test selection, or if the host
has previously sent via batch download a test selection for that sample, then the data
manager will not send a query to the host. In mixed mode, some test selections may
be batch downloads, and some may be realtime downloads.

Configuring the data manager To work in these modes, some settings have to be configured in data manager under
for the host modes Service > Service-related configuration > Interface Options.
e For details of setting the modes, see Inquiring for the test selections on page B-27.

The cobas® 8000 instrument also has a similar configuration. It can also be
independently configured so that it always sends a query to data manager, whether or
not there is any information on the sample in its internal database.
e For information on this setting, see Test Selection Inquire Always on page B-37.

No parameter is passed to the host to indicate which mode data manager and cobas®
8000 instrument are configured in. Also, it is possible for operators with
configuration privileges to reconfigure data manager and the instruments to use a
different mode. If the mixed mode is requested, the host must support in parallel
batch and realtime downloads.
e Detailed examples of the order of messages in specific cases is given in Message flow batch
download from host on page B-14, and Message flow for TS Inquiry from instrument / data
manager on page B-16.

Multiple test selection messages

In realtime mode or the mixed mode, it is possible that the data manager will have
test selections for a certain sample ID in its internal database, and then receive further
test selections from the host for the same sample ID. In this situation, the data
manager adds the new test selections from the host to those in its internal database.
The patient data is overwritten, if patient data is sent with the new test selections.

Do not re-use sample IDs

It is important for the host not to reuse a sample ID for different samples. Every sample
CAUTION must have a unique sample ID.

If the data manager has no test selections for a sample ID in its internal database, and
receives none from the host in the specified time or receives an empty test selection,
then the data manager sends an empty test selection to the cobas® 8000 modular
analyzer series. This informs the cobas® 8000 modular analyzer series about this
status.

Roche Diagnostics
B-6 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 3 Sample Processing
®
cobas 8000 instrument Identifying samples on the instrument

Identifying samples on the instrument

Samples are placed on the loader, either in 2 trays each with up to 15 5-position racks,
or inserted into the STAT port. Each rack is passed on to the input buffer, which
consists of two trays. The trays feed racks onto the system sequentially until they are
empty.

Barcodes and sample IDs By default, the cobas® 8000 instrument reads the barcodes on the sample tubes, and
uses the number on the barcode as a sample ID. The sample ID uniquely identifies
the sample in the databases of the Control Unit and the data manager, and uniquely
identifies the sample in messages to and from the host.

Samples missing a barcode If the sample tube’s barcode is missing or unreadable, the cobas® 8000 instrument
generates an error, and the instrument operator gives the sample a barcode or sample
ID. There is no interaction in this case with the data manager or the host. See the
information in the Barcode read error window in cobas® 8000 instrument, described
in the cobas® 8000 modular analyzer series Operator’s Manual.
e For a general overview of barcodes and Test Selection queries, see Processing samples on
page A-11.

One exception to this rule is when working with aliquoted samples from MODULAR
PRE-ANALYTICS. Then the connected host needs to know the original Sample ID,
and the Rack ID and position of the correspondent aliquoted sample.
e For a description of how to implement a connection to a MODULAR PRE-ANALYTICS,
see Using a MODULAR PRE-ANALYTICS on page E-41.

Sequence numbers If it is not possible to use barcodes, the cobas® 8000 modular analyzer series
instrument can give each sample a number. This number increases by 1 for each
sample. The host must then know the sequence of samples, and respond with the test
orders.
e To learn how to use this functionality, see Chapter 14 Identifying patient samples by
sequence number.

Returning results to the host

This section describes important aspects of how the data manager can be configured
to pass test results back to the host.

Passing results automatically to the host

The data manager can be configured to simply “pass through” the result information
that the cobas® 8000 instrument sends to it. This is called pass-through mode.
In this mode, data manager automatically validates patient results, and then passes
them immediately to the host, including any flags. Otherwise, data manager waits for
an operator to release the results before passing them up to the host. This option can
be set independently for patient, quality control, and calibration results. Even if
calibration results are not passed to the host, they are available from the TraceDoc.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-7
3 Sample Processing cobas® 8000 data manager
Returning results to the host cobas® 8000 instrument

e To see how to set “pass-through mode”, see Pass through results automatically to the host
on page B-29.

System time and result handling

The data manager uploads results to the host as soon as they arrive from the
instrument, and have passed any technical validation.
e If results are not being sent to host immediately after they are available, check your Result
Upload Settings in the Control Unit. See Configuring the uploading of results on page B-39.

If the host system time is ahead of the data manager system time there is a delay in
result upload. In this case, once the order is sent from the host to data manager, the
data manager creates the order with a time in the future. When the sample is loaded
on the instrument it will query and it will run the tests. However the data manager
will only upload the results to the host once the time associated with the order has
passed.

EP-17A and the result abnormal flags

As well as the numerical result and any qualitative result, such as “positive” or
“negative”, the data manager also passes “result abnormal” flags, which state whether
the result is unusually high or low, or otherwise needs attention.
These flags follow the ASTM and HL7 standards, except for an enhancement for
specific values defined according to the CLSI EP-17A standard.

The EP-17 flags The data manager provides three flags, Limit of Blank, Limit of Detection, and Limit
of Quantitation, which follow the CLSI standard EP-17A. The meanings of these are
given, in brief, below. Note that these values are not part of the ASTM nor the HL7
definitions for the report abnormal flags, but an enhancement provided by the data
manager.
e For complete details of the EP-17A standards, if required, see NCCLS Protocols for
Determination of Limits of Detection and Limits of Quantitation; Approved Guideline.
NCCLS document EP17-A (ISBN 1-56238-551-8). NCCLS, 940 West Valley Road, Suite
1400, Wayne, Pennsylvania 19087-1898 USA, 2004.

Limit of Blank The“ limit of blank” (LoB) is the highest value we expect to see in a series of results on
a sample that contains no analyte. This is calculated as the 95th percentile value from
at least 60 measurements of analyte-free samples over several independent series.

Limit of Detection The “limit of detection” (LoD) is determined based on the limit of blank and the
standard deviation of low concentration samples.The limit of detection is the lowest
actual concentration at a level such that the 5th percentile of the distribution of the
sample concentration measurements equals the limit of blank.
The limit of detection corresponds to the lowest analyte concentration which can be
detected (value above the limit of blank with a probability of 95 %).

Limit of Quantitation The “limit of quantitation” (LoQ) is the lowest actual concentration at which the
analyte is reliably detected and at which the uncertainty of the observed test result is
less than or equal to the goal set by the laboratory, or by the manufacturer of the
method. Depending on the analyte and the goal, it may be equal to or higher than the
limit of detection.

Roche Diagnostics
B-8 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 3 Sample Processing
®
cobas 8000 instrument Communication types

This provides laboratories with a more sophisticated way of defining the lowest level
of meaningful quantitation of an analyte, in the case of analytes for which the simple
limit of detection measurement is inadequate for any reason.

Configuring the EP-17 flags The EP-17A limits for each analyte are configurable in the data manager. For details,
see the cobas® 8000 Operators Manual.
e For details of the flags passed to the host in ASTM, see Result Record on page C-27.
e For details of the flags passed to the host in HL7, see Observation Result Segment - OBX
(for patient results) on page D-22.

Communication types

This section discusses the different types of communications between the host and
data manager.

Communication and message types

This section describes the types of messages that the cobas® 8000 data manager sends
to the host and receives from the host, and the types of communication those
messages occur in.

List of messages
The message types by the cobas® 8000 data manager host interface are described
below from the host’s viewpoint. That means the host, such as a LIS or Work Area
Manager (WAM), will receive information from the connected data manager and
send information to the data manager.

Message type Direction

Results Receive patient results data manager to host
Receive patient results (realtime) data manager to host in
response to a result query
Receive quality control results data manager to host
Receive calibration results data manager to host
Inquiry Receive test selection inquiry data manager to host
Test selections Send test selections (batch) host to data manager
Send test selection (realtime) host to data manager
Receive test selection (realtime) data manager to host in
response to an order query
Query Send result queries host to data manager
Send order queries host to data manager
Masking Send a command to mask or host to data manager
unmask tests (only HL7)

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-9
3 Sample Processing cobas® 8000 data manager
Communication types cobas® 8000 instrument

Communication scenarios

This section describes the types of communication scenarios that occur between the
host and the data manager.

Realtime test selection download The host sends a realtime test selection download in response to a data manager test
selection query. After receiving the test selection download, the data manager replies
with the relevant patient results once they are available and released.

Figure B-1 Communication scenario for a realtime test selection download

Batch test selection download The host can send a batch test selection download at any time. After receiving the test
selection download, the data manager uploads the relevant patient results once they
are available and released.

Figure B-2 Communication scenario for a batch test selection download

Result query The host can send a result query at any time. The data manager replies with the
relevant patient results, if any. If the sample ID does not exist, or if there are no
results , the data manager does not reply.

Figure B-3 Communication scenario for a result query

Roche Diagnostics
B-10 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 3 Sample Processing
®
cobas 8000 instrument Communication types

Order query The host can send an order query, the data manager replies with the relevant test
selection describing the order.

Figure B-4 Communication scenario for an order query

Only orders on the data manager are returned. The data manager cannot return
details of orders that are only on the Control Unit. If the sample ID does not exist, the
data manager replies, but without any test selections.

Other message scenarios The host can send a masking or unmasking request at any time, independent of other
communication. (Only supported in HL7.)
The data manager can send quality control or calibration results independently of
other messages.

Figure B-5 Communication scenarios for independent messages

Details of message types

This section describes the important types of message in a little more detail.

Query message
The cobas® 8000 data manager sends a query message to the connected host for a
sample’s test selection. The host must respond with a realtime test selection
download message, detailing the tests to be performed on the sample.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-11
3 Sample Processing cobas® 8000 data manager
Communication types cobas® 8000 instrument

Sending test selections

The host can send test selections to the data manager at any time (unsolicited test
selections or “batch mode”). The received test selections are stored in the data
manager database.
When the cobas® 8000 data manager’s Send query to LIS option is selected, it may
send a test selection inquiry to the host. This depends on the data manager’s interface
settings.
e To see how to set these options, see Inquiring for the test selections on page B-27.

The query sent to the host contains always the rack ID and the sample’s position on
the rack and may also contain the sample identifier and specimen information if
provided by the cobas® 8000 instrument.

You must request all three types of serum index tests together.
The order sent by host has to request either all 3 serum index tests (Lipemic, Icteric,
CAUTION Hemolytic), or none. Otherwise the test is not performed, and the following alarm is
displayed on the Control Unit: 994-000013 ‘Data Manager Communication Error, The
orders of the serum index tests (L/H/I) are illegal’. It is easier to create a test profile
for all three tests. See the cobas® 8000 modular analyzer series Operators Manual for
details on test profiles.

Sending patient test results

For results to be sent to the host, they must first pass validation. Validation adds
information, including the validator’s name, used reference values and flags.
Validation can be done manually or automatically. The manual validation is done by
the user on the data manager. Automatic validation is done in two ways: on a system
level, by setting Pass-through mode for patient results, or on a test level by
configuring the test for automatic validation.
e The term “pass-through mode” only refers to sending results to the host and is not related
in retrieving test selection information from the host. For more information, see Pass
through results automatically to the host on page B-29.
e For details of setting a test to automatic validation, see the cobas® 8000 modular analyzer
series User’s Manual.

Result query
The host can send a result query message to the cobas® 8000 data manager to inquire
for all the measurement test results for a given sample. The cobas® 8000 data manager
replies with a Send result message.
The host can ask for all test results for a sample, or only for all that sample’s results
whose status is “final”.

Order query
The host can send an order query message to the cobas® 8000 data manager to inquire
for all the test selections, with or without results, that include a given sample. The
cobas® 8000 data manager replies with a Send test selection message.
The host may ask for all test selections for a sample, or only for open orders with no
results for that sample. The data manager sends only the orders that are available to
it, at the status they have at the data manager (as opposed to the status or availability
at the Control Unit.)

Roche Diagnostics
B-12 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 3 Sample Processing
®
cobas 8000 instrument Communication types

Sending quality control results

The measured quality control results are sent from the data manager to the host. To
send quality control results automatically to the host, enable QC pass-through mode.
e For more information, see Pass through results automatically to the host on page B-29.

Calibration Data Results

The data manager can send unsolicited calibration data results to the connected host.
The data manager can send photometric, ISE and Elecsys calibration result types.

Masking
The host can send an instruction to the data manager to mask results from a certain
test on a certain submodule. There are two different types of masking supported:
o Patient masking. If activated, only patient samples are masked. Quality control
and calibration are still performed.
o Test masking, where the entire test is masked, and no patient sample, quality
control or calibration tests are performed.
The host can also send an instruction to remove masking from masked tests.

Masking messages are only available in HL7

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-13
3 Sample Processing cobas® 8000 data manager
Message flow batch download from host cobas® 8000 instrument

Message flow batch download from host

The following diagram shows an example of message flow (from top down) for
ASTM communications for a batch order of three test applications in the rerun
mode.

Figure B-6 ASTM messages for a batch order of three samples

The host sends unsolicited orders to the data manager, which waits for a Test
Selection inquiry from the Control Unit. When the cobas® 8000 modular analyzer
series has read the barcodes of the samples, it sends a Test Selection inquiry to the
Roche Diagnostics
B-14 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 3 Sample Processing
®
cobas 8000 instrument Message flow batch download from host

data manager, which then replies with the details of the Test Selection. The cobas®
8000 modular analyzer series performs the tests on the first sample, according to the
instructions in the test Selection, and sends every measured result to the data
manager, which performs technical validation, and then sends the results
immediately to the host (assuming pass-thorough mode is enabled). The cobas® 8000
modular analyzer series performs the required tests on the other samples, and sends
the results automatically to the data manager, which handles them in the same way as
the first.
This workflow means that once the Control Unit is ready, the test data is sent to data
manager without delay, and the data is returned to the host as soon as possible.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-15
3 Sample Processing cobas® 8000 data manager
Message flow for TS Inquiry from instrument / data manager cobas® 8000 instrument

Message flow for TS Inquiry from instrument / data manager

The following diagram shows an example of message flow for a test selection
download from the host in response to a Test Selection inquiry from the Control Unit
via data manager, in rerun mode.

Figure B-7 Message flow for a Test Selection Inquiry from instrument / data manager

Roche Diagnostics
B-16 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 3 Sample Processing
®
cobas 8000 instrument Message flow for TS Inquiry from instrument / data manager

Here, the barcode reader at the instrument reads the sample ID before the Test
Selection data has been downloaded to the data manager. Once the host replies with
the test selection data, the workflow proceeds as normal, with the results being
processed and returned to the host as fast as possible. After the instrument has
completed all the tests, it inquires for any rerun/reflex tests, if the instrument is in
rerun/reflex mode, and the function “Automatic Rerun Test Selection” is activated
at the Control Unit. In the example above, no rerun/reflex tests were required.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-17
3 Sample Processing cobas® 8000 data manager
Message flow for batch sample, upload by sample cobas® 8000 instrument

Message flow for batch sample, upload by sample

The following diagram shows an example of message flow (from top down) for:
o the host sends a batch order of three tests
o the Control Unit is in the rerun mode
o the Control Unit uploads results by sample
o the data manager option Send query to LIS is off.

Figure B-8 Batch download, with upload by sample

Roche Diagnostics
B-18 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Table of contents

Host Communication Settings

Setting up data manager and Control Unit for host
communications

This chapter describes how to set up data manager and the Control Unit to enable
host communications.

In this chapter Chapter 4

Starting and stopping the host connection ................................................................. B-21
Starting and stopping the connection ................................................................... B-21
Using the data manager without a host connection ........................................... B-22
Configuring the data manager ..................................................................................... B-23
Configuring the data manager host interface options ........................................ B-24
Identifying the data manager application to the host ................................... B-25
Setting the test selection inquiry timeout ....................................................... B-26
Inquiring for the test selections ....................................................................... B-27
Choosing the connection protocol .................................................................. B-27
Configuring HL7 Acknowledgement handling ............................................. B-28
Uploading messages one-by-one (Throttle instrument) .............................. B-28
Pass through results automatically to the host .............................................. B-29
Setting logging levels ......................................................................................... B-30
Rack and position mode ................................................................................... B-30
Identifier of the analytical unit sent to host ............................................................... B-30
Getting a trace file from the data manager ................................................................. B-32
To get a host communication file .......................................................................... B-32
Other useful logs ...................................................................................................... B-32
Configuring the Control Unit ...................................................................................... B-33
Enabling communication to data manager .......................................................... B-33
Configuring the Control Unit’s communications with data manager ............. B-35
Configuration of text settings ................................................................................. B-36
Test selection inquiry settings ................................................................................ B-37
Configuring the uploading of results .................................................................... B-39
Getting a trace file from the Control Unit .................................................................. B-40

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-19
4 Host Communication Settings cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Identifying patient samples by sequence number ..................................................... B-43

Chart of configuration settings .................................................................................... B-44

Roche Diagnostics
B-20 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Starting and stopping the host connection

Starting and stopping the host connection

This section explains how to start and stop the host connection on a configured
cobas® 8000 data manager system.

Starting and stopping the connection

Control and configuration of the host connection is done in c8000 DM Service >
Service-related configuration > Interface options.

Figure B-9 data manager: Service-related configuration > Interface options

a To connect to a host
1 In c8000 DM Service > Service-related configuration > Interface options, select
your communication protocol (HL7 network, ASTM network, ASTM serial), and
select OK. The data manager opens the requested connection to the host.
2 The data manager remembers this setting, and reopens the connection on restart.

a To stop a host connection

1 In c8000 DM Service > Service-related configuration > Interface options,
select, No host, and then click OK. The data manager closes any host connection.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-21
4 Host Communication Settings cobas® 8000 data manager
Starting and stopping the host connection cobas® 8000 instrument

Using the data manager without a host connection

You can still use the data manager even when you have stopped the host connection.
Messages are then transferred as files. In this case, service personnel can access the
messages in C:/data/in and C:/data/out. HL7 files end with the suffix .hl7, and
ASTM files end with .dat.

Roche Diagnostics
B-22 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Configuring the data manager

Configuring the data manager

This section describes the steps you need to take to set up and configure the host
interface in the data manager and the Control Unit.

a To set up the data manager for host communications

1 If you can, first complete the host interface questionnaire. This collects useful
information for the next steps. You can obtain the questionnaire from your
Authorized Roche Diagnostics personnel or technical support.
2 Make sure the necessary cables and network settings for host communication are
available and configured. This is described in Chapter 5 Physical layer
specifications.
e For details of how the cables and network must be configured, see Text encodings on
page B-47 and Host communication settings and cables on page B-47.

3 Log into the data manager as a user with configuration privileges, who can see the
Service-related configuration workplace.
4 Navigate to c8000 DM Service > Service-related configuration > Interface
options.
5 Work through the sections of this manual that describe the settings in the
Interface options tab. Make sure the settings meet your needs.
e For details of the interface options for the data manager, see Configuring the data
manager host interface options on page B-24.

6 Log onto the Control Unit, and make sure its settings meet your needs.
e For details of how the Control Unit must be configured, see Configuring the Control
Unit on page B-33. This continues from the previous section.

7 Start host communications on the data manager in c8000 DM Service > Service-
related configuration > Interface options.
e For details of starting and stopping host communications, see Starting and stopping
the host connection on page B-21.

8 The data manager is now configured for host communications.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-23
4 Host Communication Settings cobas® 8000 data manager
Configuring the data manager cobas® 8000 instrument

Configuring the data manager host interface options

When configuring the host interface, ensure that the settings in c8000 DM Service >
Service-related configuration > Interface options implement the functionality that
you need. You can work through all these sections in turn to prepare the data
manager for host communications.

Figure B-10 data manager: Service-related configuration > Interface options

Roche Diagnostics
B-24 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Configuring the data manager

Identifying the data manager application to the host

In the header of every message, the data manager sends an identification string to the
host. The user can edit this string in c8000 DM Service > Service-related
configuration > Interface options.

Sending application name This field holds the name that the data manager uses to identify itself. In ASTM this
is the Sender Name or ID, and in HL7, the Sending Application. The data manager
sends this to the host in the header of each message, in ASTM H-5 or HL7 MSH-3.
The default is cobas 8000.

Do not enter ASTM or HL7 reserved characters in the sending application name
Make sure that users never enter characters that are reserved in either communication
CAUTION protocol.
Reserved characters in ASTM are:
o | Field delimiter = vertical bar [ascii 124]
o \ Repeat delimiter = backslash [ascii 92]
o ^ Component delimiter = caret [ascii 94]
o & Escape character = ampersand [ascii 38]
Reserved characters in HL7 are:
o | Field delimiter = vertical bar [ascii 124]
o ~ Repeat delimiter = tilde [ascii 126]
o ^ Component (or sub-field) delimiter = caret [ascii 94]
o \ Escape character = backslash [ascii 92]
o & Sub-component (or sub-sub-field) delimiter = ampersand [ascii 38]

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-25
4 Host Communication Settings cobas® 8000 data manager
Configuring the data manager cobas® 8000 instrument

Setting the test selection inquiry timeout

This section describes how to determine the best setting for the timeout on test
selection inquiry (TSREQ) messages sent to the host. This is configurable in
c8000 DM Service > Service-related configuration > Interface options.

LIS Timeout This is the timeout between data manager and the host, in seconds. More specifically,
it is the timeout to the test selection inquiry for realtime communications and for
Routine, STAT and Rerun samples. See time range E below in Figure B-11.

A B C

D E

A cobas® 8000 Control Unit D Timeout on Control Unit in seconds.

B cobas® 8000 data manager Must be > (E + 2) secs.
C Host (LIS / WAM) Recommended is E + 8 secs.
Default 18 secs.
E Timeout on data manager in seconds.
Must be < (D - 2) secs.
Recommended is D - 8 secs.
Default 10 secs.

Figure B-11 Timeouts on Control Unit and data manager.

The default setting here on data manager is 10 seconds, and the timeout on the
Control Unit is by default 18 seconds. Depending on the communication speed, the
data manager timeout should be at least 2 seconds shorter than the Control Unit
timeout. However, 8 seconds shorter is recommended. This gives enough time for a
message to make the round-trip from the Control Unit to the host and back.

Optimum response time is less than 1.5 seconds

The host must send a test selection to data manager in response to a test selection inquiry
CAUTION on average in less than 1.5 seconds. If it takes the host longer to reply to inquiries, the
performance of the system will gradually degrade.
In addition, for optimum performance, the host must send the low-level ASTM protocol
ACK control characters within 10 milliseconds.

If the data manager’s inquiry for a test selection times out, then data manager sends
an empty Test Selection message to the Control Unit, indicating that there are no
Test Selections for that sample.

Roche Diagnostics
B-26 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Configuring the data manager

Inquiring for the test selections

This section describes how you can configure the test selection inquiry messages.
This is configurable in c8000 DM Service > Service-related configuration >
Interface options.
The options Send query to LIS and Always inquire for test selection configure the data
manager to work with hosts in realtime, batch or mixed mode.
e For details of host in batch, realtime or mixed mode, see Batch and realtime and the data
manager on page B-5.

The table below shows how the query and inquiry settings interact with each other.

Send query Always Behavior

to LIS Inquire
Y Y The host may send unsolicited test selections, nevertheless the
data manager always sends an inquiry message to the host. (Host
in Realtime mode)
Y N The host may send unsolicited test selections.
The data manager sends a query to the host :
o if it has no open test selections for the sample.
o if the Control Unit queries the data manager for rerun tests.
(Host in “Mixed” mode)
N Y Not possible
N N Host has to send unsolicited test selections, the data manager
never sends a query to the host. (Host in Batch mode)

Send query to LIS With Send query to LIS selected, when the Control Unit send a query to the data
manager, then the data manager check its database for relevant test orders. If it finds
none, it queries the host for test orders.

Always inquire for test selection With Always inquire for test selection selected, whenever the data manager receives an
inquiry from the Control Unit, then the data manager always sends an inquiry to the
host for tests, even if it already has test orders for that sample in its database.
Always inquire for test selection can only be enabled if Send query to LIS is also
selected.

Choosing the connection protocol

These options set the communication protocol used in messages between the host
and data manager, and start and stop communications.

ASTM Serial The ASTM Serial option specifies serial communications over the ASTM protocol.
e For technical details of the ASTM protocol, see Chapter 6 ASTM protocol (LIS2 - A2).
e For details of the data fields data manager supports over the ASTM protocol, see Chapter
7 ASTM text content (LIS2 - A2).

ASTM Network The ASTM Network option specifies TCP/IP communications over the ASTM
protocol.
e For technical details of the ASTM protocol, see Chapter 6 ASTM protocol (LIS2 - A2).
e For details of the data fields data manager supports over the ASTM protocol, see Chapter
7 ASTM text content (LIS2 - A2).

HL7 Network The HL7 Network option specifies TCP/IP communications over the HL7 protocol.
Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-27
4 Host Communication Settings cobas® 8000 data manager
Configuring the data manager cobas® 8000 instrument

e For technical details of the HL7 protocol, see Chapter 8 HL7 protocol.
e For details of the data fields data manager supports over the HL7 protocol, see Chapter
9 HL7 text content.

No host If the data manager is running without a host, select No host.

Changing the communication Consult your Authorized Roche Diagnostics service personnel before changing the
protocol communication protocol.
e For details of the cables and other low-level settings required by communication
protocols, see Host communication settings and cables on page B-47.
e For details of configuring the Control Unit for communications, see Configuring the
Control Unit on page B-33.

To change the communication protocol

To change the connectivity type (Network / Serial) further configuration might be
CAUTION necessary. This will be set up by Authorized Roche Diagnostics service personnel.

Configuring HL7 Acknowledgement handling

The data manager supports a limited range of the HL7 application acknowledgement
messages. For result messages sent to the host, the user can set the level of
acknowledgement that the data manager should request from the host. These settings
apply to patient, quality control and calibration results. This is configurable in
c8000 DM Service > Service-related configuration > Interface options.
e For more details on HL7 application acknowledgement messages, see Chapter 10 HL7
Acknowledgement handling.

Code Meaning Required host action

AL Always Send an acknowledgement to every message.
SU Success Send an Accept (AA) acknowledgement if the message is successfully
processed, otherwise send no acknowledgement.
ER Error Send an Error (AE) acknowledgement if the message could not be
processed successfully, otherwise send no acknowledgement.
NE Never Never send an acknowledgement.

HL7 Application From the HL7 Application Acknowledgement drop-down list, choose the level of
Acknowledgement application acknowledgement that the data manager should request from the host.

HL7 acknowledge timeout In the HL7 acknowledge timeout (secs.) field, enter the timeout required. This field
(secs.) is used only with the AL and SU options. The default is 60 seconds.

Uploading messages one-by-one (Throttle instrument)

In production environments, navigate to c8000 DM Service > Service-related
configuration > Interface options, and select Throttle instrument. Turn this off if
the data manager is connected to the Control Unit but not to a host, for example if
only auto-printing reports.
Throttle instrument tells the cobas® 8000 data manager to upload result report
messages from the instrument one at a time. Then, if Test selection priority mode is
selected on the instrument’s Control Unit (mandatory), the instrument prioritizes
Test Selection queries over a queue of result report messages. This means that test
selection queries are not lost.

Roche Diagnostics
B-28 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Configuring the data manager

With Throttle instrument selected, the data manager uploads a result report
message from the instrument, and then sends it to the host. The data manager then
waits:
o ASTM serial or network connection. The data manager waits up to 10 seconds for
the final low-level acknowledgement from the host before sending an
acknowledgment to the instrument.
o HL7 network connection with application acknowledgement set to AL or SU. The
data manager waits up to 10 seconds for the high-level acknowledgement from
the host before sending an acknowledgment to the instrument.
o HL7 network connection with application acknowledgement set to ER or NE. In this
case, the data manager sends an acknowledgment to the instrument immediately
after sending the result report message to the host. If the message cannot be sent
to the host, the acknowledgment is sent to the instrument at the latest after 10
seconds.

Pass through results automatically to the host

You can configure the data manager to automatically validate all results, and pass
them immediately to the host, including any flags. This is configurable in
c8000 DM Service > Service-related configuration > Interface options.

Patient results To forward all patient results automatically to the host, select Pass-through mode >
Patient Results. Otherwise, the data manager validates the results according to its
validation settings.
If selected, this option overrides any manual and automatic validation settings in the
data manager.
If this checkbox is not selected, data manager will only forward patient results which
pass automatic validation. More precisely, the data manager will evaluate the patient
results according its internal automatic validation settings specified in the
Configuration workplace in Test/Reference Ranges. If the results fulfill these
conditions, data manager sends the results automatically to the host. Otherwise, the
results will be held back for manual validation, and the data manager waits for an
operator to release the results before passing them up to the host.
e For details on configuring validation in the data manager, see the cobas® 8000 modular
analyzer series Operator’s Manual.

QC results If the host does the QC analysis, select Pass-through mode > QC Results. If the data
manager does the QC analysis, unselect it.
With the QC results checkbox selected, quality control results are forwarded to the
host automatically. Then the host can do QC analysis: Westgard, Rilibäk etc. If this
checkbox is not selected, the QC results are not forwarded to the host, and QC
analysis is done by data manager.
e For more details on the configuration of quality control analysis, see the Data Manager
section of the cobas® 8000 modular analyzer series Operator’s Manual.

Calibration results With the Calibration results checkbox selected, calibration results are forwarded to
the host automatically.
e For more details on the configuration of calibration settings, see the cobas® 8000 modular
analyzer series Operator’s Manual.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-29
4 Host Communication Settings cobas® 8000 data manager
Identifier of the analytical unit sent to host cobas® 8000 instrument

Setting logging levels

You can configure what information the data manager logs about host
communications in c8000 DM Service > Service-related configuration > Interface
options, from the Trace level drop-down menu. In increasing quantity of
information, the options are No logging, Error, Warning, Information, Debug. For
troubleshooting, Information is recommended. In a production environment, Error
or No logging is recommended. Use other settings only if requested by Roche
Diagnostics technical support.

Rack and position mode

To process samples using the rack ID and position of the tube, navigate to
c8000 DM Service > Service-related configuration > Interface options, and enable
the option Enable rack and position mode.
e For a more detailed description of how to implement this option, and other related
options, see Using a MODULAR PRE-ANALYTICS on page E-41, and Handling batch test
selections with strict rack and position on page E-43.

Identifier of the analytical unit sent to host

The data manager holds a unique ID for each module in your cobas® 8000 modular
analyzer series configuration. This ID is editable.

Viewing and editing the ID You can freely edit the analytical unit IDs in the data manager in Workplaces >
System Configuration > Instrument > [Select instrument] > [Shortcut menu] > Edit
instrument > [field] ID for Host.

Figure B-12 The analytical unit IDs (or instrument ID for host) in the data manager

This field is used by both result and masking messages (HL7)

In HL7, this field is used by both result and masking messages. If you edit this field, make
CAUTION sure the host is updated so that it reads the new identifier in result upload message, and it
sends the new identifier in masking messages, if used.

Using the ID The data manager sends the ID in ASTM in:

o In ASTM Result record, Field 14, component 3. It identifies the module and
instrument that performed the test.

Roche Diagnostics
B-30 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Identifier of the analytical unit sent to host

o In the ASTM calibration records M(PCR) Field 6, M(ICR) Field 5, M(ECR) Field
7. It identifies the module and instrument that performed the test.
The data manager sends the ID in HL7 in:
o In HL7 segment OBX-18, component 3. It identifies the module and instrument
that performed the test. For calibration results from an ISE module, the analytical
unit ID is the only component in the field.
The data manager reads the ID in HL7 in:
o In HL7 segment ECD-5, component 3. Here it identifies the module and
instrument to perform masking on.

Default value The whole field is freely editable. The default values follow the format:
Instrument#ModuleType#Position#SubModule

Instrument String Currently default to MU1, which identifies the first cobas®
8000 modular analyzer series connected to the data manager.
In future, there may be more analyzers connected.
ModuleType String c502, c701, e602, ISE, c702, DM or c8000.
Position Number The position of the module on the cobas® 8000 modular
analyzer series, as an integer.
Submodule Number 0, 1 or 2

Examples of default values:

MU1#e602#1#1
MU1#c8000#0#0

The reserved values in ASTM or HL7 cannot be used: | or ^ or \ or ~ or &.

Otherwise, any unique string can be used as the identifier, for example, the serial
number of the module, such as:
1048-12

In such a case an HL7 OBX segment, this might look like:

OBX|1||991||109.1|mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20101012074509
|bmuser^DMUSER||63|ISE^1^1048-12^3|20101012074525|

In an ASTM Result record, this might look like:

R|1|^^^999/1/not|2.3^|mmol/L|0.5 - 7.5^TECH\^NORM\^CRIT\^USER|N||F||
bmsrv^DMROUTINE|20100711163455|20100711163455|ISE^2^1048-12^4|

The Analytical Unit ID is unique

To uniquely identify the module or analytical unit that performed the test, it is
recommended to use the analytical unit ID and nothing else.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-31
4 Host Communication Settings cobas® 8000 data manager
Getting a trace file from the data manager cobas® 8000 instrument

Getting a trace file from the data manager

Authorized Roche Diagnostics service personnel can collect a set of log files to send
with an issue report.

To get a host communication file

Instead of a whole issue report, it is possible to obtain the communication logs on

their own.

a How to get a data manager host communication trace file

1 Navigate to c:\data\log
2 Select all the logs in the folder, which may include:
o astm-serial.log
o hl7-network.log
o astm-network.log
o ASTM-message.log
o HL7-message.log
3 If you are sending them to a support engineer, save them in a zip archive or
similar convenient compressed format.

The important files for the host communication in c:\data\log are: ASTM-
message.log and HL7-message.log. These files contain the host communication
messages between the data manager and the host, correspondent to the used protocol
(ASTM or HL7). These files may also contain a datestamp in the filename. Logs from
the current day do not have a timestamp.

Other useful logs

Log information on the communication between the data manager and the Control
Unit is in: c:\data\log\InstrumentAdapter\All.yyyy-mm-dd.log

Roche Diagnostics
B-32 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Configuring the Control Unit

Configuring the Control Unit

This section tells you how to configure the Control Unit for communication with
data manager and the host (LIS / WAM). A user with appropriate permissions needs
to be logged into the Control Unit to change these settings.

Enabling communication to data manager

a To enable the Control Unit to communicate with data manager

1 Navigate to the initial screen: Overview > System Overview

A Data Manager button

Figure B-13 The Control Unit screen at Overview > System Overview

2 In the section Module Overview, select the button Data Manager (A). The Data
Manager Host Communication dialog appears.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-33
4 Host Communication Settings cobas® 8000 data manager
Configuring the Control Unit cobas® 8000 instrument

Figure B-14 The Data Manager Host Communication Status dialog on the Control Unit, at
Overview > System Overview > Module Overview > Data Manager

This dialog shows the status of the communications with the data manager, and
what communication channels are currently online.
3 To activate communications between the Control Unit and the data manager,
select the button Communication Setting. The Communication Setting dialog
appears.

Figure B-15 The Communication Setting dialog on the Control Unit, at Overview > System
Overview > Module Overview > Data Manager > Communication Setting

4 Activate communications by setting the Host Communications and Control

Communications both to Online. Then select OK, to return to the Data Manager
Host Communication dialog.
If every setting in the Data Manager Host Communication dialog is not light blue,
meaning “Online”, check the network connections, or contact your technical
support.

Roche Diagnostics
B-34 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Configuring the Control Unit

Configuring the Control Unit’s communications with data manager

To configure the settings that control the Control Unit’s communications with data
manager, go to Utility > System > Data Manager Settings >
Communication Settings.

Figure B-16 Utility > System > Data Manager Settings > Communication Settings

In a production environment, set:

Name ID
System cobas8000 1
Data Manager DataManager 2

Keep your current settings for the other options, unless Authorized Roche
Diagnostics service personnel or technical support instruct you otherwise.
Authorized Roche Diagnostics service personnel can reconfigure the E.I.U. level
(Essential Information Upload). E.I.U. Level determines which kind of data (for
example, "Get Log Data") can be sent to the data manager via a pipe upload to be
stored and further used for troubleshooting (for example, including into the issue
report).
For further details of these settings, see the Control Unit’s online help.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-35
4 Host Communication Settings cobas® 8000 data manager
Configuring the Control Unit cobas® 8000 instrument

Configuration of text settings

To configure the settings of text information sent to data manager, go to Utility >
System > Data Manager Settings > Text Settings.

Figure B-17 Mandatory settings in Utility > System > Data Manager Settings > Text Settings

Send conc. of chemistry In a production environment, select Send conc. of chemistry qualitative tests.
qualitative tests

Send message for Immunoassay In a production environment, select Send message for Immunoassay Quantitative
Quantitative tests tests.

Result message only for In a production environment, clear the Result message only for Immunoassay
Immunoassay Qualitative tests Qualitative tests checkbox.

Unselect ‘Result message only’ to get all data

To get all data in a production environment, the option Result message only for
CAUTION Immunoassay Qualitative tests must be unselected.

Chemistry Test Calibration In a production environment, select Chemistry Test Calibration Result Detail.
Result Detail

Further details For further details of these options, see the Control Unit’s online help.

Roche Diagnostics
B-36 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Configuring the Control Unit

Test selection inquiry settings

The Control Unit can be configured as regards how and when it sends inquiries about
samples, (in other words, Test Selection Inquiries) in Utility > System > Data
Manager Settings> Test Selection Inquiry Settings.

Figure B-18 Test Selection Inquiry Settings tab in the Data Manager Settings section of the
Control Unit, in Utility > System > Data Manager.

Test Selection Inquiry In a production environment, select Test Selection Inquiry.

Test Selection Timeout In a production environment, select Test Selection Timeout.

Default is 18 seconds. In production environments, it is recommended to use the
default, and handle host communications timeouts on the data manager.
e For details of how the data manager handles timeouts from the host and Control Unit, see
Setting the test selection inquiry timeout on page B-26.

Automatic Rerun Test Selection In a production environment, select Automatic Rerun Test Selection.
Automatic Rerun Test Selection must be checked, if Rerun and/or Reflex Orders
from data manager or host are used.
e To enable requests for rerun / reflex tests, other settings have to be done, see Request for
rerun or reflex tests on page A-14.

Manual Rerun Test Selection In a production environment, select Manual Rerun Test Selection.
, the Manual Rerun Test Selection must be checked, if Rerun and Reflex Orders are
used.

STAT Test Selection In a production environment, select STAT Test Selection.

Test Selection Inquire Always In a production environment, select Test Selection Inquire Always.
Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-37
4 Host Communication Settings cobas® 8000 data manager
Configuring the Control Unit cobas® 8000 instrument

Test Selection Priority Mode In a production environment, select Test Selection Priority Mode.

Test Selection Ask in Barcode If your sample tubes have barcodes, keep Test Selection Ask in Barcode Read Error
Read Error unselected.
When Test Selection Ask in Barcode Read Error is unselected, an unreadable
barcode triggers an error on the analyzer. See cobas® 8000 modular analyzer series
Operator’s Manual for details on how the analyzer operator will handle a barcode
read error.
Only select this option if you are using samples without a barcode, for example if
using aliquots from a MODULAR PRE-ANALYTICS.
e For a more detailed description of how to implement this option, see Using a MODULAR
PRE-ANALYTICS on page E-41.

When Test Selection Ask In Barcode Read Error is selected, rerun by gray racks
(racks for 1st run) is not permitted, as the analyzer cannot tell if this is the first or
second presentation of the rack.
When the barcode readers are deactivated on the cobas® 8000 modular analyzer
series instrument, this option is hidden.
e The barcode readers are deactivated, for example, when identifying samples by sequence
number. For details, see Chapter 14 Identifying patient samples by sequence number.

Further details For further details of these options, see the Control Unit’s online help.

Roche Diagnostics
B-38 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Configuring the Control Unit

Configuring the uploading of results

This section describes how to configure the rules for uploading results. These are set
in Utility > System > Result Upload Settings.

Figure B-19 Utility > System > Result upload settings

Upload by test or sampleYou can set the Control Unit to upload results by sample
or by test. Other options are not supported in version 1.02.
o By test means that the Control Unit uploads each result as soon as it is ready.
o By sample means that the Control Unit waits until all the results for a sample are
ready, and then uploads all of them together.

Other options are not supported in version 1.02.05

In version 1.02.05, only the options By test and By sample are supported.

a To configure how the Control Unit uploads results

1 Navigate to Utility > System > Result Upload Settings.
2 From the drop-down list for type of result you want to configure, select “By Test”
or “By Sample”. You can separately configure Routine sample results, STAT
sample results, or Quality control sample results. Calibration results can only be
uploaded “By Test”.
3 Check the As Soon As Setting checkbox.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-39
4 Host Communication Settings cobas® 8000 data manager
Getting a trace file from the Control Unit cobas® 8000 instrument

Getting a trace file from the Control Unit

Authorized Roche Diagnostics service personnel can access trace files on the Control
Unit. The communication trace file records data sent from or received by the Control
Unit. This information is particularly useful for support or debugging purposes. The
Control Unit saves this information internally, and can print it out to a PDF file or a
physical printer.
The Communication Trace file options are available from the Print > Utility >
Communication Trace.

Figure B-20 Print > Utility > Communication Trace

Roche Diagnostics
B-40 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Getting a trace file from the Control Unit

a To get a communication trace file from the Control Unit

1 From the buttons on the right of the Control Unit screen, select Print. The Utility
screen displays.
2 From the list on the left of the Utility screen, select Communication Trace. The
Communication Trace options screen displays.

Figure B-21 Print > Utility > Communication Trace with a Date Range selected

3 Select the radio button Date Range.

4 Consider the date and time range for which you want to see the Communication
Trace. Then enter the start date and time, and the end date and time, for the
Communication Trace data you wish to collect.
5 Select the button Preview. It may take a few seconds for the Control Unit to
generate the file.
6 To display the file in the Control Unit, select the History tab.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-41
4 Host Communication Settings cobas® 8000 data manager
Getting a trace file from the Control Unit cobas® 8000 instrument

Figure B-22 Print > Utility > Communication Trace > Preview > History > Communication
Trace

7 On the left of the screen, in the list of Reports, select the Communication Trace
Report that you created. It displays in the main window on the right.
8 You can view the Report in a number of ways.

Button View
Zoom Zooms in or zooms out of view in the main window on
the right. There are 3 different levels of zoom.
Backup Saves to a PDF file.
Print Out Prints out to a physical printer.

When to use trace files

Due to the trace file size, it is recommended that the Communication Trace report not be
routinely used. When enabled for troubleshooting purposes, it is recommended that the
print buffer be printed prior to printing this report, as the size of it might overwrite other
buffered printouts.

Sending a trace file

If you are sending a trace file by email to support engineers, be aware it can be very large.
Compress it to, for example, a zip file, and consider if possible putting on a shared drive
from where it can be downloaded. You can also save it to a memory stick or similar device,
as with any other file.

Roche Diagnostics
B-42 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 4 Host Communication Settings
®
cobas 8000 instrument Identifying patient samples by sequence number

Identifying patient samples by sequence number

By default, the patient samples are identified by a sample ID, which is encoded on the
barcode on the sample tube. One alternative in the situation where samples lack
barcodes, is to configure the instrument to number the samples in sequence: starting
with 1 or another number, and increasing the number by 1 for each sample, up to a
maximum of 60,000.
The Roche Diagnostics service personnel can configure this on the cobas® 8000
modular analyzer series instrument, the Control Unit, and on the data manager. This
requires a dedicated configuration tool.
To implement this, ask for assistance from the Roche Diagnostics service personnel,
and refer to the relevant service bulletins from August 2011, and the cobas® 8000
modular analyzer series Service Manual from version 1.02.04 (available 2012).
e For details of how to identify patient samples by sequence number, see Chapter
14 Identifying patient samples by sequence number.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-43
4 Host Communication Settings cobas® 8000 data manager
Chart of configuration settings cobas® 8000 instrument

Chart of configuration settings

This chart shows the possible configuration settings of specific options.

data manager Control Unit Control Unit Barcode mode Sequence Mode Aliquots without
sequence number STAT / Routine TS Ask in Barcode barcodes from
support installed barcode reader read Error MODULAR PRE-
ANALYTICS
Installed ON ON OK Not working OK
OFF OK Not working Not working
OFF N/A Not working OK Not working
Not Installed ON ON OK Not working OK
OFF OK Not working Not working
OFF N/A Not working Not working Not working
Table B-1 Table describing setup of data manager infrastructure to work in different modes

Other combinations are not supported.

To set these options:
o Sequence mode in data manager, Control Unit, and the cobas® 8000 modular
analyzer series instrument: ask the authorized Roche Diagnostics service
personnel to implement this.
o STAT / Routine barcode reader on Control Unit: on the Control Unit, navigate to
Utility > System > Barcode Settings > Routine/Stat.
o Test selection ask in barcode read error on the Control Unit:
e For details, see Test Selection Ask in Barcode Read Error on page B-38.

Roche Diagnostics
B-44 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 5 Physical layer specifications
®
cobas 8000 instrument Table of contents

Physical layer specifications

Cables and low-level protocol configuration

This chapter explains how to configure the base and low-level communication
protocol, and gives restrictions on which cables to use.

In this chapter Chapter 5

Text encodings ................................................................................................................ B-47
Host communication settings and cables ................................................................... B-47
Network connection ................................................................................................ B-48
Serial connection ...................................................................................................... B-49

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-45
5 Physical layer specifications cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
B-46 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 5 Physical layer specifications
®
cobas 8000 instrument Text encodings

Text encodings

The data within the message has to be Unicode encoded as UTF-8 characters. UTF-8
and ASCII is similar between 32-127. If characters are used outside this range care
should be taken, and only UTF-8 encoding is supported.

The host needs to handle UTF-8

In situations where the data manager operators will be able to enter UTF-8 characters, the
WARNING host will have to support UTF-8, or be able to recognize and translate from UTF-8. If
necessary, it is possible to prevent operators from entering UTF-8 characters by running
the data manager in pass-through mode.

e For the UTF-8 codes of common Western European characters, see Western European
characters in UTF-8 on page E-112.

Host communication settings and cables

This section describes the cables required for a network or a serial connection, and
where they have to be connected at the data manager’s machine.

C D

A Serial RS232 C LIS or host

B Control Unit connection D cobas Link

Figure B-23 Cables for connecting the PC running data manager

The cables should be connected as above.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-47
5 Physical layer specifications cobas® 8000 data manager
Host communication settings and cables cobas® 8000 instrument

Network connection

An ethernet cable Cat.5e or better can be used for the connection to the customer
host system. Cat.5e is currently defined in TIA/EIA-568-B, and provides
performance of up to 100 MHz, and is frequently used for both 100 MBit/s and
1000BASE-T Gigabit Ethernet networks. A crossover cable and straight-through
cable are both supported.

Figure B-24 Cat.5e ethernet cable

By default the data manager works as a TCP/IP client, so the connected system
(cobas® IT firewall or host) must act as the TCP/IP server. To configure the data
manager can act as a TCP/IP server, please consult your Roche Diagnostics service
personnel, or see the cobas® 8000 data manager Service Manual.

With cobas® IT firewall When using cobas® IT firewall with data manager, these defaults are recommended:
o The IP address (172.20.1.31), the Subnetmask (255.255.255.0) and the default
gateway (172.20.1.1) are fixed
o For ASTM, the TCP port number is fixed to 50001
o For HL7, the TCP port number is fixed to 50002
If there is a non-Roche firewall between the data manager and host, the firewall must
not block the TCP-port for ASTM and HL7 (by default 50001 or 50002 respectively).

Ethernet standard All network and hardware devices between the host and data manager must support
at least 100MBit/s, including the firewall, routers, switches, cables and network
adapters.
If either the host or data manager run on a PC which is connected to a network via a
serial-to-network adapter, the connection is not a supported network connection, but
performs as a serial connection.
e For details of serial connections, see Serial connection on page B-49.

Restart the host task and driver after network problems

If problems occur on the network, or the network connection is lost for some reason, for
CAUTION example if the firewall is rebooted, you may need to restart the host connection on the data
manager and the driver on the host, in order to establish the network connection again.

e For details of restarting the host connection on the data manager, see Starting and
stopping the connection on page B-21.

Roche Diagnostics
B-48 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 5 Physical layer specifications
®
cobas 8000 instrument Host communication settings and cables

Serial connection

For a serial connection, use a cable RS232c, configured as follows.

Figure B-25 Typical serial host interface connection cable for cobas® 8000 data manager

The dashed line indicates that the cable might have these bridges, if the
communication partners are using these signals.

For serial connection, short shielded cable required.

For a serial connections, use a shielded RS232c cable, not longer than 15m.
CAUTION

Communication settings The following diagram shows the recommend default communication settings.

Item Recommend default communication settings

Communication Port 1
Electrical Signal In accordance with EIA-232-D-1986
Cable Length Maximum 15m
Communication speed (Baud 19200
rate)
Parity N
Databits 8
Stopbits 1

Some sites might reconfigure the communication settings

The default settings are as given, and these are recommended for best performance. If a
CAUTION host or LIS cannot use these parameters, it may be possible in certain cases for Authorized
Roche Diagnostics service personnel to reconfigure the communication settings on
individual sites according to individual requirements.

HL7 over a serial connection is not supported

ASTM over a serial connection is supported, but not HL7. For HL7, a network connection is
CAUTION required.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) B-49
5 Physical layer specifications cobas® 8000 data manager
Host communication settings and cables cobas® 8000 instrument

Network connection is recommended

For either ASTM or HL7 protocol, a fast network connection (100 MBit/s or faster) between
the data manager and the host is highly recommended.

Roche Diagnostics
B-50 Host Interface Manual · Version 1.02.05 (revision 1)
 ASTM Reference C

6 ASTM protocol (LIS2 - A2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3

7 ASTM text content (LIS2 - A2) . . . . . . . . . . . . . . . . . . . . . . . . . C-13
cobas® 8000 data manager 6 ASTM protocol (LIS2 - A2)
®
cobas 8000 instrument Table of contents

ASTM protocol (LIS2 - A2)

This chapter presents the lower layers of the ASTM protocol, as used by cobas® 8000
data manager.

In this chapter Chapter 6

Background to the ASTM protocol .............................................................................. C-5
Communication processing layers ............................................................................... C-5
ASTM lower layer ........................................................................................................... C-6
ASTM syntax ................................................................................................................... C-8
Coding rules for the messages ................................................................................. C-8
End of record character ..................................................................................... C-8
Field delimiter = vertical bar ‘|’ ......................................................................... C-8
Repeat delimiter = backslash ‘\’ ........................................................................ C-8
Component delimiter = caret ‘^’ ...................................................................... C-9
Escape character = ampersand ‘&’ ................................................................... C-9
Special characters with escape character ......................................................... C-9
Message transmission phases ................................................................................ C-10
Checksum calculation / message frame ..................................................................... C-11

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-3
6 ASTM protocol (LIS2 - A2) cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
C-4 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 6 ASTM protocol (LIS2 - A2)
®
cobas 8000 instrument Background to the ASTM protocol

Background to the ASTM protocol

The ASTM (American Society of Testing and Materials) provides a standard for
communication between automatic analyzers and host computers for standards
E1381-91 (Specification for Low-Level Protocol to Transfer Messages Between
Clinical Laboratory Instruments and Computer Systems) and E1394-91 (Standard
Specifications for Transferring Information Between Clinical Instruments and
Computer Systems). The basic specifications of the standards are regulated on X12 of
ANSI.

Communication processing layers

The communication process between the data manager and the host is divided into
four layers as shown below.

A Application Layer. Server specification of C ASTM Lower Layer. ASTM E1381-91

host communication. D Physical Layer.
B ASTM Upper Layer. ASTM E1394-91

Figure C-1 Host Communication Processing Layers

Details of the ASTM protocol can be found in the Annual Book of ASTM Standards.
Copyright American Society for Testing and Materials, 100 Barr Harbor Drive, West
Conshohocken, PA 19428-2959, USA.
o ASTM E1381-91 Low Level Protocol
Specification for Low Level Protocol to Transfer Messages Between Clinical
Laboratory Instruments and Computer Systems
o ASTM E1394-91 High Level Protocol
Standard Specification for Transferring Information Between Clinical
Instruments and Computer Systems

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-5
6 ASTM protocol (LIS2 - A2) cobas® 8000 data manager
ASTM lower layer cobas® 8000 instrument

ASTM lower layer

ASTM lower layer receives messages for a transmission request from the upper layer.
These messages are then split into frames and sent to a communication medium to be
transmitted to other parties. ASTM lower layer also constructs frames received from
a communication medium to recreate messages to be transferred to the ASTM upper
layer as reception messages.

ASTM frame maximum size 240 char + 7 control char

For one frame, maximum of 240 characters for text, plus 7 characters for frame control
characters.
Messages equal to or less than 240 characters are transmitted as one final frame.
Messages greater than 240 characters are split into frames that have character lengths
that fall within the 240-character limit. The only or final remaining frame becomes the last
frame and is indicated by <ETX>. All others are intermediate (middle) frames and are
indicated by <ETB>.

Configuration and communication procedures for transmission and reception of

frames are explained in the following sections.

Roche Diagnostics
C-6 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 6 ASTM protocol (LIS2 - A2)
®
cobas 8000 instrument ASTM lower layer

ASTM frame Item Method Explanation

Frame Configurations For Middle Frame o Control character (characters enclosed
<STX> FN text <ETB> in <>):
C1 C2 <CR><LF> <STX> is control character (HEX 02)
For Last Frame <ETB> is control character (HEX 17)
<STX> FN text <ETX> <CR> is control character (HEX 0D)
C1 C2 <CR><LF> <LF> is control character (HEX 0A)
<ETX> is control character (HEX 03)
o FN: FN is a single ASCII number. FN
indicates the sequence number for a
frame (the frame number modulus 8).
Frames of a single transmission phase
are consecutively numbered beginning
with 1, so FN runs from 1 to 7, then
continues with 0, 1, and so on.
o Text: the data content of a frame
(maximum 240 characters). Records
are sub-divided into intermediate
(middle) frames with 240 or fewer
characters. Text is part of a split
message.
o C1 and C2: When 1 byte resulting from
adding each byte, FN to <ETB> for the
middle frame and FN to <EXT> for the
last frame, is expressed in hexadecimal,
the upper character (161) is C1 and the
lower character (160) is C2. Characters
used are ‘0’ to ‘9’ or ‘A’ to ‘F’.
Frame Character Characters other than <SOH> is control character (HEX 01)
Configuration of Text <SOH><STX><ETX> <EOT> is control character (HEX 04)
<EOT><ENQ><ACK> <ENQ> is control character (HEX 05)
<DLE><NAK><SYN> <ACK> is control character (HEX 06)
<ETB><CR><LF> <DLE> is control character (HEX 10)
<DC1><DC2><DC3>< <NAK> is control character (HEX 15)
DC4> <SYN> is control character (HEX 16)
<DC1> ~ <DC4> are control characters
(HEX 11 ~ 14)
Maximum Length of 247 characters For one frame, maximum of 240 characters
the Frame for text, plus 7 characters for frame control
characters.
Messages equal to or less than 240
characters are transmitted as one final
frame. Messages greater than 240
characters are split into frames that have
character lengths that fall within the 240-
character limit. The only or final remaining
frame becomes the last frame and is
indicated by <ETX>. All others are
intermediate (middle) frames and are
indicated by <ETB>.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-7
6 ASTM protocol (LIS2 - A2) cobas® 8000 data manager
ASTM syntax cobas® 8000 instrument

ASTM syntax

The structure of the sentences to be transferred, according to ASTM Communication

Regulation, is explained in this section. Between the analyzer and the host, various
data such as Test Requests and Results are transferred back and forth. All of these
data conform to this syntax.

Message A message is constructed with an arrangement of several

records (refer to the next item). It is the smallest unit of
information transferred between a host and an analyzer.
Messages begin with a ‘Message Header Record’ that
indicates the beginning of a message and end with a
‘Message Termination Record’ that indicates the end of a
message.
Record A record is constructed from several fields and expresses
a single purpose (such as to specify result reports or test
requests). A record may be repeated or used singularly in
a message. Code that indicates the purpose of a record is
noted in the first character of that record.
Field A field is the ASTM’s smallest element to construct
information. Attributes for a field (name, format, and
meanings) are defined in units in a record.

Coding rules for the messages

This section deals with message coding rules as well as special characters, such as
delimiters, used to develop messages provided by records and fields.

End of record character

The ASCII CR character (HEX 0D) is always used to indicate the end of a record.

Field delimiter = vertical bar ‘|’

Field delimiter ‘|’ supported, but no others

The field delimiter ‘|’ is supported in the current version of cobas® 8000 data manager
CAUTION (version 1.02). Other field delimiters are not supported.

A Field delimiter is a character used to separate fields that are next to each other in a
record. This is also a delimiter for the first Record ID (character that appears in the
beginning of a record) and the next field. According to the 2nd character that appears
in the Message Header Record (record that appears in the front of a message), a Field
delimiter can be defined with an optional character through the Message Header
Record; however, the data manager requires a vertical bar ‘|’.

Repeat delimiter = backslash ‘\’

Repeat delimiter ‘\’ supported, but no others

The repeat delimiter ‘\’ is supported in the current version of cobas® 8000 data manager
CAUTION (version 1.02). Other repeat delimiters are not supported.

Roche Diagnostics
C-8 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 6 ASTM protocol (LIS2 - A2)
®
cobas 8000 instrument ASTM syntax

When a field is constructed by the same data repeated several times, it is referred to as
a Repeated Field. The delimiter between the repeated items for the Repeated Field is
called the Repeat delimiter. Repeat delimiters can be defined with an optional
character through the Message Header Record; however, the data manager requires a
backslash ‘\’.

Component delimiter = caret ‘^’

Component delimiter ‘^’ supported, but no others

The component delimiter ‘^’ is supported in the current version of cobas® 8000 data
CAUTION manager (version 1.02). Other component delimiters are not supported.

When a field is constructed by several elements, it is referred to as a Component

Field. The delimiter between these elements is the Component delimiter. The
Component delimiter can be defined with an optional character through the Message
Header Record; however, the data manager requires a caret ‘^’.

Escape character = ampersand ‘&’

Escape character ‘&’ not supported

The escape character is not supported in the current version of cobas® 8000 data
CAUTION manager (version 1.02). This character is reserved for future use.

An Escape character is to be provided to indicate a delimiter for the fields that include
general text. When this character occurs in a relevant field, the next character holds a
special meaning (discussed below). An Escape character can be defined with an
optional character through the Message Header Record, however, the data manager
requires an ampersand ‘&’.

Special characters with escape character

Special characters not supported

The special escape sequences are not supported with special character in the current
CAUTION version of cobas® 8000 data manager (version 1.02). This character is reserved for future
use.

The following escape sequence (starting with & and ending with &) is defined. When
this sequence is detected in a field, it is changed to a corresponding character and
deleted.
Escape sequences other than these are skipped and treated as NULL values.

&F& Indicates field delimiter

&S& Indicates component delimiter
&R& Indicate Repeat delimiter
&E& Indicates Escape

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-9
6 ASTM protocol (LIS2 - A2) cobas® 8000 data manager
ASTM syntax cobas® 8000 instrument

Message transmission phases

To establish which system sends and which system receives information and to
assure the actions of sender and receiver are well coordinated, there are three distinct
phases in transferring information.
o Establishment phase
o Transfer phase
o Termination phase

A Intermediate frame E Establishment phase (ACK must be sent

B End frame within 10 ms.)
C Sender F Transfer phase
D Receiver G Termination phase

Figure C-2 Message Transaction Phases

Acknowledge must be received from the host within 10 ms

The host must send an ACK reply to data manager within 10 ms. Otherwise the
CAUTION performance of the system degrades and cannot reach its maximum throughput.

Within the transfer phase, all records of the corresponding message are grouped into
longer frames to increase speed. The records are separated through a [CR] character.
Therefore, to obtain pure ASTM records again, the receiver must concatenate all the
frames and wait for a [EOT] character. Then, the receiver can process the frame and
split it into different records using the [CR] as the separator.

Roche Diagnostics
C-10 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 6 ASTM protocol (LIS2 - A2)
®
cobas 8000 instrument Checksum calculation / message frame

Checksum calculation / message frame

Figure C-3 The intermediate frame

Figure C-4 The end frame

[STX] The ASCII code 2, indicating the beginning of a frame

transmission.
FN The frame number modulus 8. Frames of a single
Transmission Phase are consecutively numbered
beginning with 1. So FN runs from 1 to 7, continues with
0, 1, and so on. Use ASCII codes for the digits ‘0’ to ‘7’
(48-55).
Text The data content of a frame (max. 240 characters).
Records are sub-divided into intermediate frames with
240 characters.
Maximum is indicated by [ETB]. The only or last
remaining frame is indicated by [ETX]. Different records
must be sent in different frames.
[ETB] The ASCII code 23 (17hex), indicating the end of the text
block of an intermediate frame.
[ETX] The ASCII code 3, indicating the end of the text block of
an end frame.
CH, CL Represents the high nibble (= most significant 4 bit)
respectively, the low nibble (=least significant 4 bit) of the
8-bit checksum. CH and CL are represented as two digits
of hex numbers. The checksum is the modulus 8 of the
sum of ASCII values of the frame characters starting with
and including ‘FN’ and completing with [ETX]
respectively [ETB].

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-11
6 ASTM protocol (LIS2 - A2) cobas® 8000 data manager
Checksum calculation / message frame cobas® 8000 instrument

Example for Checksum [STX]1Test[ETX]

calculation
Character Value (hex) Sum
[STX] 02h 00h
’1’ 31h 31h
’T’ +54h 85h
’e’ +65h EAh
’s’ +73h 15Dh
’t’ +74h 1D1h
[ETX] +03h 1D4h
= 1D4h
Mod 100h
= D4h

Thus the message to be sent is:

[STX]1Test[ETX]D4[CR][LF]

Roche Diagnostics
C-12 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Table of contents

ASTM text content (LIS2 - A2)

ASTM field definitions

This section describes all the ASTM fields used in messages transferred between
cobas® 8000 data manager and the host HIS/LIS system.

In this chapter Chapter 7

Record levels .................................................................................................................. C-15
Messages used in host communication ...................................................................... C-15
Messages transmitted by the data manager ......................................................... C-16
Messages transmitted by the host ......................................................................... C-17
Record description ........................................................................................................ C-18
Field attributes ......................................................................................................... C-18
Text encodings ........................................................................................................ C-19
Message Header Record ............................................................................................... C-19
Patient Information Record ......................................................................................... C-21
Order Record ................................................................................................................. C-22
Comment Record (following Order Record) ............................................................ C-26
Result Record ................................................................................................................. C-27
Comment Record (following Result Record) ............................................................ C-31
Query Record (Request Information Record) .......................................................... C-33
Photometric Calibration Result M(PCR) .................................................................. C-36
ISE Calibration Result Record - M(ICR) ................................................................... C-37
ISE data alarms .................................................................................................. C-37
ISE calibration analytical data ......................................................................... C-38
E-module (immunology) Calibration Result Record - M(ECR) ............................ C-39
Message Termination Record ...................................................................................... C-41

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-13
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
C-14 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Record levels

Record levels

The following table shows the Standard Record types and levels specified by the
protocol ASTM E1394-91.
e For details of ASTM E1394-91, see the information given in Communication processing
layers on page C-5.

Level Record Name Identifier

0 Message Header Record H
1 Patient Information Record P
2 Test Order Record O
3 Result Record R
1 ... 3 Comment Record C
1 ... 3 Manufacturer Specific Record M
0 Message Termination Record L
1 Request Information Record Q

Messages used in host communication

The following section shows detailed descriptions of each of message sent between
the host and data manager, and the ASTM records used in each.

Communication text Communication Realtime Batch

Direction Communication Communication
(a)

Test Selection Information Host to data o o

manager
Order Query Host to data x o
manager
Result Query Host to data x o
manager

Test Selection Inquiry data manager to x o

Host
Patient Sample Analytical data manager to o o
Data Host
Control Sample Analytical data manager to o o
Data Host
Calibration Analytical Data data manager to o x
Host
(a) o = available, x = not available

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-15
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Messages used in host communication cobas® 8000 instrument

Messages transmitted by the data manager

Messages transmitted from data manager to the host are shown in the table below. In
the following charts:
o [ ] Square brackets indicate an optional segment. (0 - 1 times)
o { } Curly brackets indicate a segment or group of segments that may be repeated.
(1 - n times.)
The identifier is set in the Comment or Special Instruction Field (H-11) in the
Message Header Record with the reason for the message.

Messages Syntax / Records Comment or Special Reasons

Instructions
Inquiry for requested tests H TSREQ Inquiry is made for the requested
Q test just after a rack has passed the
ID reader.
L
Test Selection Information H TSUPL Test selection upload for a sample
P as answer to an order query.

O
C
L
Result report H RSUPL Reports on the result at the point
P when the results for the sample
have been accumulated, or when
O
the results for the sample have
C been requested by the host.
{ Transmits results of the selected
R sample(s) by instruction at the
{C} analyzer.

} RSUPL^REAL First transmission of QC results,

from data manager to host.
L
RSUPL^BATCH Manual or repeat upload of QC
results.
Upload of patient sample results in
reply to a result query.
Photometry Calibration Result H PCUPL^REAL Reports at the point when the
Report M-PCR photometry calibration results are
L output.
ISE Calibration Result Report H ICUPL^REAL Reports at the point when the ISE
M-ICR calibration results are output.
L
Elecsys Calibration Result Report H ECUPL^REAL Reports at the point when the
M-ECR Elecsys calibration results are
L output.

Roche Diagnostics
C-16 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Messages used in host communication

Messages transmitted by the host

The data manager can receive the following message from a connected LIS.

Messages Syntax / Records Comment or Special Reasons

Instructions
Test Selection Information H TSDWN Test selection download for a
P sample as an answer to a test
selection inquiry or as unsolicited
O
test selections send in batch mode
[C] by the host
L
Result Query H RSREQ Inquiry for test results for a given
Q sample ID, sent from host.
L
Order Query H TSREQ Inquiry for a given sample ID’s test
Q selections known to the data
L manager, sent from host.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-17
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Record description cobas® 8000 instrument

Record description

Field attributes

Types of attributes held by a field are explained below.

Attribute Description
Field The number of the field in the record.
Reference The paragraph in the ASTM definitions that describes the field. See
NCCLS. Specification for Transferring Information Between Clinical
Laboratory Instruments and Information Systems: Approved
Standard, Second Edition. NCCLS document LIS2-A2 [ISBN 1-
56238-550-X]. NCCLS, 940 West Valley Road, Suite 1400, Wayne,
Pennsylvania 19087-1898 USA, 2004.
Value This shows either:
o The precise text to be sent.
o The format of the field.
The format of the field can take one of the following values:
o Character. A single character.
o String: A character string.
o Number: A numeric value. Positive (+) or negative (-) is indicated
before the numeric value. If it is not indicated, it is treated as
positive (+).
If a decimal point is not included, the numeric value is treated as
an integer. There are no restrictions for placing ‘0’ in the front
and for ‘0s’ placed at the end of numbers with decimal points.
o Date. Always use the 4-digit Gregorian year. The format is
YYYYMMDD (YYYY is the 4-digit Gregorian year, MM is the
month, DD is the day). For example, September 5, 2009 is
indicated 20090905.
o Time: Military time. (24 hour)
The format is HHMMSS (HH is the hour, MM is the minute, and
SS is the second).
o DateTime. A combination of Date and Time.
The format is: YYYYMMDDHHMMSS.
o Complex. A field in which multiple data components are
combined, separated by a component delimiter. Each component
may take one of the other formats.
Host If sent from the host or LIS, this field is either:
o R, required
o O, optional
DM If sent from data manager, this field is either:
o R, required (in other words, always sent)
o O, optional
Length / Max. Size If used, the maximum number of characters supported in the field.
Description A description of the field, including use and permitted values. In the
case of complex fields, this includes a description of individual
components.

Roche Diagnostics
C-18 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Message Header Record

Text encodings

The data within the message has to be Unicode encoded as UTF-8 characters. For
characters from decimal 32 to 127 also ASCII can be used. Characters from 0 to 31
are control characters and therefore not allowed within the ASTM fields.

The host needs to handle UTF-8

In situations where the data manager operators will be able to enter UTF-8 characters, the
WARNING host will have to support UTF-8, or be able to recognize and translate from UTF-8. If
necessary, it is possible to prevent operators from entering UTF-8 characters by running
the data manager in pass-through mode.

Escaping characters as defined for the delimiter characters is not supported (see
Header Record, field no. 2). You should bear in mind, that future versions of
cobas® 8000 data manager may implement further fields or manufacturer-defined
records.

Message Header Record

This record occurs at the front of every message, and shows the sender and receiver
and other important general information about the message.
The Host and DM columns indicate whether the data is Required or Optional when
sent from the Host or data manager respectively.
H|\^&|12345||cobas 8000^1.02|||||host|TSREQ|P|1|20101026142034|
H|\^&|12345||cobas 8000^1.02|||||host|TSUPL|P|1|20101026142034|
H|\^&|12345||cobas 8000^1.02|||||host|RSUPL|P|1|20101026142034|
H|\^&|12345||cobas 8000^1.02|||||host|RSUPL^REAL|P|1|20101026142034|
H|\^&|12345||cobas 8000^1.02|||||host|RSUPL^BATCH|P|1|20101026142034|
H|\^&|12345||cobas 8000^1.02|||||host|PCUPL^REAL|P|1|20101026142034|
H|\^&|12345||cobas 8000^1.02|||||host|ICUPL^REAL|P|1|20101026142034|
H|\^&|12345||cobas 8000^1.02|||||host|ECUPL^REAL|P|1|20101026142034|
H|\^&|12345||host|||||cobas 8000^1.02|TSDWN|P|1|20101026142034|
H|\^&|12345||host|||||cobas 8000^1.02|RSREQ|P|1|20101026142034|
H|\^&|12345||host|||||cobas 8000^1.02|TSREQ|P|1|20101026142034|

Field Ref. Value Host DM Description

1 6.1 H R R Fixed value, identifying Header record
2 6.2 |\^& R R Delimiter definitions. Fixed values:
o | Field delimiter = vertical bar [ascii 124]
o \ Repeat Delimiter = backslash [ascii 92]
o ^ Component Delimiter = caret [ascii 94]
o & Escape character = ampersand [ascii 38]
3 6.3 String O R Message Control Identifier to uniquely identify the message.The cobas® 8000 data
manager sends the internal message ID as integer number; the host can send any
string or number for message identification or leave this field empty.
4 6.4 Field contains no data.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-19
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Message Header Record cobas® 8000 instrument

Field Ref. Value Host DM Description

5 6.5 Complex - R Sender ID. From data manager: Sender^Version
o Sender is ID for the data manager installation, by default: cobas 8000
e To edit the Sender ID, see Configuring the data manager host interface
options on page B-24.
o Version is the data manager version (numeric value).
O - Sender ID. If sent, used only for tracing purposes.
6 6.6 Field contains no data.
7 6.7 Field contains no data.
8 6.8 Field contains no data.
9 6.9 Field contains no data.
10 6.10 String O R Receiver ID. Fixed value. Sent from data manager, is:
o Host
Sent from host, it should match the value sent from the data manager in H-5. By
default, this is cobas 8000. It is used only for tracing purposes.
11 6.11 Complex R R Identifier for the message type and purpose. Format is two strings: Type^Mode.
TSREQ Test selection request, from data manager to host, or from host to
data manager.
TSDWN Test selection download, from host to data manager.
TSUPL Test selection upload, from data manager to host.
RSREQ Result request, from host to data manager.
RSUPL Result upload, from data manager to host.
RSUPL^REAL First transmission of QC results, from data manager to host (or
Patient results in a realtime or batch upload, except as an answer
to a result request).
RSUPL^BATCH o Repeat transmission of QC results, from data manager to
host.
o Patient sample result upload from data manager to host in
reply to a result query.
PCUPL^REAL Photometry calibration report, from data manager to host.
ICUPL^REAL ISE calibration report, from data manager to host.
ECUPL^REAL Elecsys calibration report, from data manager to host.
12 6.12 P O R Processing ID, fixed value P, meaning production.
13 6.13 1 O R Protocol version, fixed value 1. (Meaning LIS2-A2.)
14 6.14 DateTime O R Time and date the message was created.

Roche Diagnostics
C-20 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Patient Information Record

Patient Information Record

This record is used to transfer patient demographic data, such as age and sex.
P|1||SH25111965M||Doe^John||19651125|M|

P|1||||^||||

Field Ref. Value Host DM Description

1 7.1 P R R Fixed value, identifying a Patient record.
2 7.2 1 R R Sequence number, fixed value, showing that only one Patient record is supported per
message.
3 7.3 Field contains no data.
4 7.4 String O/R O/R Laboratory-assigned patient identifier. Max length 16 characters.
This field is mandatory only if some patient demographic data is sent, in other
words, if one or more of fields 6, 8, or 9 contain data. If fields 6, 8 and 9 are empty,
this field is blank.
5 7.5 Field contains no data.
6 7.6 Complex O O Patient surname and first name, in separate string components:
Surname^Firstname
Each component has a max length of 30 characters.
7 7.7 Field contains no data.
8 7.8 Date O O Patient’s birthdate. (YYYYMMDD)
9 7.9 Character O O Patient sex:
o M Male
o F Female
o U Unknown. Any other value defaults to unknown, and is returned to the host
as U.
All following patient record fields contain no data.

The data manager supports only M, F, or U for patient sex.

For male patients, the host must send M, for females, F. Otherwise the wrong reference
WARNING range might be applied. The data manager reads any other value as U, and applies the
reference ranges for a patient of unknown sex.
Make sure the host sends only M, F, or U, as required. Each new configuration must be
tested to ensure the correct data transfer between the data manager and the host.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-21
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Order Record cobas® 8000 instrument

Order Record

This record holds information regarding the analysis request and sample
information. It is sent to the data manager within test selection message, and to the
host within result message.

Order record in TS Download O|1|500169|^50017^3^^S1^SC|^^^8706^|R||||||A||||1||||||||||O

message

Order record in Result Upload O|1|10005|0^110005^2^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|R|

message 20100429161525|20100429161525||||N||||1||||||||||F|

Order record in Quality Control O|1|HBCN^611490^1|0^30001^2^^QC^SC^not|^^^870^1|R||||||Q||||4|

result message |||||||||F|

Order record with sequence O|1||1013^50101^3^^S1^SC^not|^^^8571^1\^^^8413^1\^^^8706^1\|R|

number in TS Download 20110715093311|20110715093311||||A||||1||||||||||O

Order record with sequence O|1||1013^50101^3^^S1^SC^not|^^^8413^1\^^^8571^1\^^^8706^1|R|201107150

number in Result Upload 93311|20110715093311||||N||||1||||||||||F|

Field Ref. Value Host DM Description

1 8.4.1 O R R Fixed value, identifying an Order record.
2 8.4.2 1 O R Sequence number, fixed value, showing that only one Order record is
supported per Patient record.
3 8.4.3 String, R/O R Identifier for the sample, (sample ID).
or for QC, For patient results, this is the sample’s barcode (string of max. 22 characters
Complex padding not allowed). This field is required, when using barcodes. If the patient
sample is identified by the sequence number in O-4.1, this field must be empty.
e For details of sequence numbers, see Chapter 14 Identifying patient
samples by sequence number.
For Quality Control material, Name^Lot^ID
o Name Control name, for example, PNU. (String)
o Lot Control lot (Number)
o ID Control identifier (a unique control ID contained in data manager).
(Number)
Ordering test selections for QC is not possible from host.

Roche Diagnostics
C-22 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Order Record

Field Ref. Value Host DM Description

4 8.4.4 Complex R O/R Instrument sample identifier, with additional information for identifying the
or sample.
Number Sequence_Number^Rack_ID^Position^^Rack_Type^Container^
Diluted
This field is optional in a message sent in response to an order or result query.
Otherwise the field is mandatory.
Note: When samples are identified by sequence number, in a Test selection
upload from the data manager to the host in response to an order query, this is:
o Number field, contains the sequence number.
4.1 Number O R Sequence_ For patient samples identified by sample ID (default), and
Number QC samples, the data manager sends 0 (zero) in this field,
and ignores any value the host sends.
For patient samples identified by sequence number, this
contains the sequence number. (Max. value = 60,000.) If
the host sends a sample ID in O-3, the data manager
ignores any value in this field.
This field was previously known as “Sample number.”
4.2 Number R/O R/O Rack_ID ID of the sample rack with space for 5 samples. Not sent
with result records with manually-entered results. Optional
for messages from host to data manager, if the sample is
identified by sequence number.
4.3 Number R/O R/O Position Sample’s position on the rack. Value 1 to 5. Not sent with
result records with manually-entered results. Optional for
messages from host to data manager, if the sample is
identified by sequence number.
4.4 Component contains no data.
4.5 String R R Rack_Type A two character code, identifying the rack type.
o S1 Serum / Plasma
o S2 Urine
o S3 Cerebrospinal Fluid
o S4 Supernatant
o S5 Other fluids
o S6 Whole blood
o S7 Oral fluids (Saliva)
o S8 Reserved
o S9 Reserved
o SA Reserved
o QC Quality Control
(Note, that this field does not support the S0 used in the
Query record.)
4.6 String R R Container A two-character code, identifying the container.
o MC Micro Cup
o SC Standard Cup
o (No value) Default (Information available at the
instrument is used.)
4.7 String R R Diluted A flag indicating if the sample is diluted or not.
o not Normal sample
o pre-diluted Prediluted sample
o (No value) Normal sample

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-23
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Order Record cobas® 8000 instrument

Field Ref. Value Host DM Description

5 8.4.5 Complex O R/O Testcode with dilution factor.
^^^Testcode^Dilution
If the host has no pending test, the host must send a Test Selection Download
message with this field empty. In a test selection upload, if the data manager
has no information on tests, it will leave this field empty.
You can send multiple tests codes in one message by repeating this field, for
example:
O|1|1234|0^00083^5^^S1^SC|^^^989^1\^^^990^1\^^^991^1|S|2010
1026152611|20101026152611||||A||||1||||||||||O|
For serum index tests, you must send all three test types together (lipemic,
icteric, and hemolytic), or send a test profile that contains all three. Otherwise
the test will not be run.
e For more details on sending serum index orders, see Sending test selections
on page B-12.
5.1 First component contains no data.
5.2 Second component contains no data.
5.3 Third component contains no data.
5.4 Number R R Testcode The fourth component contains the code to identify the
test (in other words, the application code or analyte tested
for). The maximum length is 5 digits: the data manager
takes the last 5 digits and strips any leading zeros.
The host can download the test numbers of calculated tests,
if the test is programmed on the data manager. For details,
see the cobas® 8000 modular analyzer series Operator’s
Manual.
5.5 String (or O O Dilution Dilution factor. Sent also by the data manager if available,
number) but the host has to take the dilution from the Result record
for the test.
The dilution factor is sent as a string:
o By the host in the Order Record, field 5, component 5.
o By the data manager in the Result Record, field 3,
component four, in the second part.
Permitted values are:
o For an ISE module, the only value that can be used is: 1
o For a C-module: Dec, Inc, 1
o For an E-module: 1, 2, 5, 10, 20, 50, 100, 400
The value 1 means no dilution. If the host sends an empty
field, this defaults to 1.
6 8.4.6 String R O/R Priority.
o R Routine
o S STAT
STAT samples must be placed in the STAT racks.
This field is empty in a result or test selection upload message sent in response
to an order or result query. Otherwise the field is mandatory.
7 8.4.7 DateTime O O Date and time of order creation
8 8.4.8 DateTime O O Date and time of sample collection
9 8.4.9 Field contains no data.
10 8.4.10 Field contains no data.
11 8.4.11 Field contains no data.
Roche Diagnostics
C-24 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Order Record

Field Ref. Value Host DM Description

12 8.4.12 Character R R Action code. This is the action to take in response to the message.
From the host:
o A Add or rerun test
o R Add or rerun test
o C Cancel test (The test can only be canceled before it has been downloaded
to the cobas® 8000 modular analyzer series instrument.)
From the data manager:
o N Patient result
o Q Quality Control result
o O Order query response (test selection upload)
13 8.4.13 Field contains no data.
14 8.4.14 Field contains no data.
15 8.4.15 Field contains no data.
16 8.4.16 Character R O/R Specimen type.
The specimen type must match the second character of the rack type (field O-
4.5), except for QC samples. Optional only when sent to the host in response to
an order or result query. Otherwise mandatory.
Note that depending on the version and the modules of the cobas® 8000
modular analyzer series, not all these types may be available on any particular
system.
o 1 Serum / Plasma
o 2 Urine
o 3 Cerebrospinal Fluid
o 4 Supernatant
o 5 Other fluids
o 6 Whole blood
o 7 Oral fluids (Saliva)
o 8 Reserved
o 9 Reserved
o A Reserved
For QC samples, the host should disregard any value in O-16.
17 8.4.17 Field contains no data.
18 8.4.18 Field contains no data.
19 8.4.19 Field contains no data.
20 8.4.20 Field contains no data.
21 8.4.21 Field contains no data
22 8.4.22 Field contains no data.
23 8.4.23 Field contains no data.
24 8.4.24 Field contains no data.
25 8.4.25 Field contains no data.
26 8.4.26 Character R R Report type, indicating source of message.
o O Sent from host.
o F Sent from data manager / cobas® 8000 modular analyzer series.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-25
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Comment Record (following Order Record) cobas® 8000 instrument

Comment Record (following Order Record)

Record to transfer comments. This record is transmitted by the host (within test
selection message) or the data manager (within result message or test selection
upload). These comments are visible at the Control Unit.
C|1|L|Comment1^Comment2^Comment3^Comment4^Comment5|G

Special format of cobas® 8000 data manager comment records

The format of the comment record is not totally in accordance with the LIS2-A2 standard,
CAUTION in order to keep backwards-compatibility with the cobas® 6000 comment record. The
cobas® 6000 comment record was used to transfer patient demographic data.

Field Ref. Value Host DM Description

1 10.1 C R R Record Identifier, fixed value.
2 10.2 Number R R Sequence number. Set to 1, as only one comment is permitted after an order record.
3 10.3 Character R R Comment source. A single-character code.
From the host, this is always set to L.
From the cobas® 8000 modular analyzer series, it is set to I.
4 10.4 Complex O O The format (when sent after an order record):
comment1^comment2^comment3^comment4^comment5
o comment1 String with up to 30 characters
o comment2 String with up to 25 characters
o comment3 String with up to 20 characters
o comment4 String with up to 15 characters
o comment5 String with up to 10 characters
In HL7, this data is passed in SPM-14.
5 10.5 G R R Code for qualifying the comment record type. Following an order record, this is a
fixed value, G, indicating an order comment.

Roche Diagnostics
C-26 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Result Record

Result Record

The data manager uses the result record to upload the details of test results.
A quantitative patient result:
R|1|^^^999/1/not|2.3^|mmol/L|0.5 - 7.5^TECH\^NORM\^CRIT\^USER|N||F||
bmsrv^DMROUTINE|20100711163455|20100711163455|ISE^2^MU1#ISE#1#2^4|

A qualitative patient result:

R|1|^^^101/1/not|1^2.68|mmol/L|^TECH/^^NORM/^^CRIT/^^USER|N||F||bmsrv^
DMROUTINE|20090311163455|20090311163455|ISE^2^MU1#ISE#1#2^4^104|

For an automatically-validated result, the operator is written as “SYSTEM”:

R|3|^^^991/Inc/not|5.5|mmol/L|4.0 - 44.0^TECH\2.0 - 22.0^NORM\
3.0 - 33.0^CRIT\1.0 - 11.0^USER|N||F||bmserv^SYSTEM|
20100718164600|20100729161525|ISE^2^MU1#ISE#1#2^4|

For an automatically-validated QC result:

R|1|^^^870/1/not|17.30|g/dL||||F||bmserv^SYSTEM|20100718164500|
20100729165317|22^1^MU1#c502#2#1^9^0^Current|

This shows a result below the EP-17A level of detection:

R|1|^^^989/1/not|2.1|mmol/L|^TECH\9 - 144^NORM\^CRIT\^USER|LoD||F||bms
erv^SYSTEM|20100621084348|20100621084404|ISE^1^MU1#ISE#1#1^3^28|

Field Ref. Value Host DM Description

1 9.1 R R Record identifier for Result record, fixed value.
2 9.2 Number R Sequence number
The first result relating to the preceding Order record takes the sequence
number 1. The sequence number increments by one for each further result
for that Order record.
3 9.3 Complex R Test request
^^^Testcode/Dilution/Pre-dilution
Note that the fourth component is separated into three parts with a forward-
slash separator /.
3.1 This component contains no data
3.2 This component contains no data
3.3 This component contains no data
3.4 R Testcode Number Identifier (or application code) for the test
(analyte searched for), used by the cobas® 8000
modular analyzer series. (Max. 5 digits)
R Dilution String Dilution factor, as sent by the cobas® 8000
modular analyzer series instrument.
Permitted values are:
o For an ISE module, the only value that can be
used is: 1
o For a C-module test: Dec, Inc, 1
o For an E-module test: 1, 2, 5, 10, 20, 50, 100,
400
O Pre- String Indicates whether sample is pre-diluted:
dilution o pre-diluted
o not

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-27
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Result Record cobas® 8000 instrument

Field Ref. Value Host DM Description

4 9.4 Complex R Measurement value.
The measurement values are only transmitted for patient and QC results.
ReportableResult^AdditionalResultValues
Quantitative results:
4.1 Number R Reportable The result. A missing result is sent as 7 spaces. (ASCII 32 /
Result 0x20).
4.2 Number O Additional Empty or a qualitative flag.
Result
Values
Qualitative results:
4.1 Number R Reportable o For C-module and ISE module: an integer code from -2
Result to 3 inclusive.
o For E-module: an integer code -1, 0, 1.
The codes can be configured on the cobas® 8000 instrument,
under Utility > Application > Range, see cobas® 8000
modular analyzer series Operator’s Manual for details
4.2 Number R Additional The quantitative value, like value for a quantitative result.
Result For E-module qualitative results this contains COI.
Values
5 9.5 String R Units in which result is measured. (for example, mmol/L, etc.)
6 9.6 Complex O For patient results, reference ranges, if defined. Empty for QC results.
Patient results example:
0.5 - 7.5^TECH\3.3 - 5.1^NORM\^CRIT\^USER
These take the format:
RangeDefinitionString^TypeOfRange
6.1 String O The RangeDefinitionString string component can consist of the any of
the following:
o Two numbers (with or without decimal points) separated by space-
hyphen-space, for example,
0.5 - 7.5
Note that either or both of these number may potentially be negative, for
example,
-10 - -7
o A “greater than” or “less than” value, for example,
< 0.1
o A comma-separated string of permissible values, for example,
Y,N,U
-,+,++
6.2 String O/R The TypeOfRange string component can consist of any of four values.
o TECH Hard-coded value to indicate “Technical Range”
o NORM Hard-coded value to indicate “Normal Range”
o CRIT Hard-coded value to indicate “Critical Range”
o USER Hard-coded value to indicate “User-defined Range”
These four values can occur in the same record as a repeat field, for example:
0.5 - 7.5^TECH\3.3 - 5.1^NORM\^CRIT\^USER
Note that the different ranges are separated with the repeat delimiter, a
backslash “\”. If a range is not defined, the RangeDefinitionString is
blank.

Roche Diagnostics
C-28 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Result Record

Field Ref. Value Host DM Description

7 9.7 String O Result abnormal flags for patient results. This is empty for manually-edited
results.
HH Above high critical value
H Above high normal value
N Normal
L Below low normal value
LL Below low critical value
A Alphanumeric result out of normal range
AA Alphanumeric result out of critical range
LoB Below the Limit of Blank
LoD Below the Limit of Detection
LoQ Below the Limit of Quantitation
No data signifies that no validation against ranges has been
performed.
If more than one flag is triggered, only the most extreme flag is sent. The EP-
17 flags, LoB. LoD, and LoQ take precedence over the others.
e For further details on the EP-17A flags, see EP-17A and the result
abnormal flags on page B-8.
8 9.8 Field contains no data.
9 9.9 Character R Result status. This can take:
o F = First run result, or QC result
o C = Corrected result
o M = Manually edited result
o X = Calculated test, but test could not be calculated (for example, divided
by zero)
10 9.10 Field contains no data.
11 9.11 Complex R Active operators in the format:
Instrument operator^Datamanager operator
11.1 String R o Instrument operator
This is the username the operator used to log into the Control Unit.
Empty in the case of a manual or calculated result.
11.2 String R o Datamanager operator
This is the username the operator used to log into the data manager. If
the result is automatically validated, or the data manager is in pass-
through mode, this reads SYSTEM.
12 9.12 DateTime O Pipetting time. This is considered to be the time the test started. (Format:
YYYYMMDDhhmmss.)
Note: For manual and calculated tests, this field is empty.
13 9.13 DateTime R Completion time. This is the time the result is available (in other words, time
of validation at the data manager). (Format: YYYYMMDDhhmmss.)

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-29
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Result Record cobas® 8000 instrument

Field Ref. Value Host DM Description

14 9.14 Complex R Identifier of the measurement unit or module that performed the test.
ModuleType^SubModule^AnalyticalUnitID^InstrumentID^CalID^
Bottle^SBNo
14.1 String R ModuleType o c502, c701, e602, ISE, c702, for results from
measuring modules, or manual results entered on behalf
of a specific module.
o DM for results calculated on the data manager, and for
manual results entered on the data manager, but cannot
be attributed to a module.
o c8000 for results from the cobas® 8000 modular
analyzer series that cannot be mapped to an actual
measuring submodule, for example, sample short.
14.2 Number R SubModule o 1 or 2, for result from a submodule.
o 0 (zero) otherwise.
14.3 String R Analytical Identifier for the module, as sent to the host. This setting is
UnitID configurable in the cobas® 8000 data manager in the
definition of the module, under the heading ID sent to Host
(meaning the identifier that the instrument sends to the
host). The default value is:
Instrument#ModuleType#Position#SubModule
Example: MU1#c502#2#1
e For details, see below, Identifier of the analytical unit
sent to host on page B-30.
14.4 Number R Instrument Instrument number in data manager (A specific identifier
ID inside the data manager which identifies a module. This is a
number which has no relationship to the internal position of
the module in the machine.)
14.5 Number R CalID Calibration ID. Identifier of the calibration the result refers
to, set in the Control Unit. Sent only if available. It is empty
for results that do not have a calibration, for example,
calculated and manual results.
14.6 String R Bottle Used Reagent Set.
o Current
o Standby
o (or empty)
Reserved field, only for QC measurements, otherwise empty.
14.7 Number SBNo An integer showing the standby bottle number, if used. The
standby bottles are numbered sequentially, starting with 1.
Reserved field, only for QC measurements, otherwise empty.

Roche Diagnostics
C-30 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Comment Record (following Result Record)

Comment Record (following Result Record)

Record to transfer comments regarding the measured result. This record is

transmitted by the data manager, either by adding a comment to a result, or by
passing on an instrument comment received from the Control Unit. The first record
is an instrument flag, and is mandatory.
For a test that did not generate any instrument alarms, the instrument flag is:
C|1|I|0|I|

This is: “C-one-i-zero-i”.

An instrument alarm flag is, for example:
C|1|I|23^ISE Sample range over|I|

A comment from the data manager is, for example:

C|2|L|Second comment^DMROUTINE^20101026164339|G|

C|3|L|Test done on instrument^DMROUTINE^20101026164238|G|

Special format of cobas® 8000 data manager comment records

The format of the comment record is not totally in accordance with the LIS2-A2 standard,
CAUTION in order to keep backwards-compatibility with the cobas® 6000 comment record.

Field Ref. Value Host DM Description

1 10.1 C R Record Identifier, fixed value.
2 10.2 Number R Sequence number.
The first comment relating to the preceding Result record takes the sequence
number 1. The sequence number increments by one for each further
comment for that Result record. Multiple comment records for a result
record are permitted.
3 10.3 Character R Comment source:
o I
Result flag, from the instrument or the data manager.
o L
The comment was added on the data manager.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-31
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Comment Record (following Result Record) cobas® 8000 instrument

Field Ref. Value Host DM Description

4 10.4 Complex O This field contains the main part of the comment record. The contents of this
field depend on what type of comment the record is sending. The comment
type is specified in field 5 below.
Comment Type I
If the instrument has returned an error flag, the details of the flag are returned in this field.
Flag^Description
4.1 Number Flag Number showing error status (or alarm status)
o 0 means no error
o a number >0 is an error number.

For details of the error flags, see Chapter 11 Data Alarms.

4.1 String Desc Description of error flag (blank if no error)
Comment Type G after result record
Test^User^Date
4.1 String Text Comment text
4.2 String User User who entered the comment
4.3 Datetime Date Creation date and time in datetime format
5 10.5 Character R Code for qualifying the comment record type. Comments sent by data
manager can have the following types:
o I Result flag
o G Result text comment created in data manager.
The content of the comment is passed in field 4.

Roche Diagnostics
C-32 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Query Record (Request Information Record)

Query Record (Request Information Record)

The data manager and the host both use the Query Record, or Request Information
Record, to request a sample’s open test selections, in a test selection inquiry message
or a order query message (H-11 is TSREQ). It is also used to request test results in a
Result Query message (H-11 is RSREQ).
From data manager to host:
Q|1|^^123^0^10001^2^^S1^SC^R1||ALL|||||||R|O||

Q|1|^^********************^0^10001^2^^S1^SC^R1||ALL|||||||R|O||

From host to data manager :

Q|1|^S1^10001|||||||||||
Q|1|^S2^10001||||||||||O|
Q|1|^^10003|||||||||||

From data manager to host with sample identified by sequence number:

Q|1|^^^1013^50101^3^^S1^SC^R1||ALL|||||||R|O|

From host to data manager with sample identified by sequence number:

Q|1|^S1^^1031||||||||||F|

Field Ref. Value Host DM Max Description

Size
1 11.1 Q R R 1 Record identifier, fixed value.
2 11.2 1 R R 1 Sequence number. Fixed value, showing that only one query record
per message is supported.
3 11.3 Complex R R Query parameters that identify the required information.
From host to data manager (result or order query): From host to data manager in a result or order query message:
^Rack_Type^Sample_ID^Sequence_Number
Note: If sequence number is used, sample ID must be empty.
Otherwise the data manager ignores the sequence number.
3.1 The first component contains no data.
3.2 String R - 2 Rack_Type The rack type as assigned to a specific specimen
type on data manager. Depending on the version
and modules installed, not all of these types may be
available on any particular system.
S1 Serum
S2 Urine
S3 Cerebrospinal Fluid
S4 Supernatant
S5 Other fluids
S6 Whole blood
S7 Oral Fluids (Saliva)
S8 Reserved
S9 Reserved
SA Reserved
S0 A rack with no specimen assigned. (Only
supported for queries sent by the data
manager.)

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-33
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Query Record (Request Information Record) cobas® 8000 instrument

Field Ref. Value Host DM Max Description

Size
3.3 String R/- - 22 Sample_ID This is the barcode label attached to the sample
tube, if used, or the system’s sample ID.
This must be blank if Q-3.4 contains the sequence
number.
3.4 Number R/- - 5 Sequence_ If the sample is identified by sample ID (default),
Number the data manager ignores the value of this field.
If the sample is identified by sequence number, this
contains the sample’s sequence number. (Max.
value = 60,000.)
e To learn how to use this, see Chapter
14 Identifying patient samples by sequence
number.
Previously, this field was known as “Sample
Number.”
The further components contain no data.
From data manager to host: (test selection query) From data manager to host in a test selection query message:
^^Sample_ID^Sequence_Number^Rack_ID^Position^^Rack
_Type^Container^ QueryType
3.1 The first component contains no data.
3.2 The second component contains no data.
3.3 String - R/O 22 Sample_ID This is the barcode label attached to the sample
tube.
This is blank if Q-3.4 contains the sequence
number.
3.4 Number - R 5 Sequence_ If the sample is identified by sample ID (default),
Number always set to 0 (zero).
If the sample is identified by sequence number, this
contains the sample’s sequence number. (Max.
value = 60,000.)
e To learn how to use this, see Chapter
14 Identifying patient samples by sequence
number.
Previously, this field was known as “Sample
Number.”
3.5 String - R 5 Rack_ID Identifier of the rack sent by cobas® 8000
instrument.
3.6 Number - R 1 Position The sample’s position on the rack sent by the
instrument. Takes the value 1 to 5.
3.7 The seventh component contains no data.
3.8 String - R 2 Rack_Type The rack type as assigned to a specific specimen
type on data manager. Depending on the version
and modules installed, not all of these types may be
available on any particular system.
S1 Serum
S2 Urine
S3 Cerebrospinal Fluid
S4 Supernatant
S5 Other fluids
Roche Diagnostics
C-34 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Query Record (Request Information Record)

Field Ref. Value Host DM Max Description

Size
S6 Whole blood
S7 Oral Fluids (Saliva)
S8 Reserved
S9 Reserved
SA Reserved
S0 A rack with no specimen assigned. (Only
supported for queries sent by the data
manager.)
3.9 String - O 2 Container A two-character code:
MC Micro cup
SC Standard cup
An empty value defaults to standard cup.
3.10 String - R 2 QueryType A two-character code:
R1 Query for 1st measurement
R2 Rerun query
4 11.4 Field contains no data.
5 11.5 ALL - R 3 Subselection criteria, fixed value
6 11.6 Field contains no data.
7 11.7 Field contains no data.
8 11.8 Field contains no data.
9 11.9 Field contains no data.
10 11.10 Field contains no data.
11 11.11 Field contains no data.
12 11.12 Character - R 1 o R for Routine samples
o S for STAT samples (Short Turn-Around Time)
13 11.13 Character - R 1 The request information status code.
If sent from the data manager to the host:
o O (capital letter O) for “Request for test selections”.
Character O - 1 The request information status code.
If sent from the host to the data manager in a result inquiry:
o F = send final results
o (empty) = send all results
If sent from the host to the data manager in an order inquiry:
o O = (capital letter O) send only open orders with no results
o (empty) = send all orders

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-35
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Photometric Calibration Result M(PCR) cobas® 8000 instrument

Photometric Calibration Result M(PCR)

The data manager sends calibration data from the C-module (or photometric
module) in the manufacturer-defined Photometric Calibration Result M(PCR)
record.
M|1|PCR|bmserv|^^^8685|MU1#c701#1#1|16|0|22851^4^22866^2^0^\24786^-361
^24149^-362^0^\^^^^^\^^^^^\^^^^^\^^^^^|

Field Ref. Value Host DM Max Description

Size
1 14 M - R 1 Record type ID, fixed value signifying manufacturer record.
2 14 Number - R 6 Sequence Number:
This record appears as the next layer of the Message Header Record. For one
record, the field value is ‘1’; for specifying several, sequence numbers starting
from 1 are assigned.
3 14 PCR - R 3 Record Type Sub ID. Set to ‘PCR’.
4 14 String - R 6 ID of the operator who performed the calibration at the analyzer.
5 14 Complex - R Test Code (Application code).
^^^Testcode
The Test Code is a number type.
The maximum range of test code is 5 digits.
6 14 String - R 20 ID of the analytical unit (module) the test belongs to.
e For details, see Identifier of the analytical unit sent to host on page B-30.
7 14 Number - R 3 Calibration alarm.
e For details, see Chapter 11 Data Alarms.
8 14 Number - O 6 Standard deviation value data.
9 14 Complex - R Repeat field of number types. Repeated from STD1 to STD6 for as many as
there are.
Format:
First Initial Absorbance^First Absorbance^Second Initial
Absorbance^Second Absorbance^Data Alarm^Prozone Value
Number R 6 First Initial
Absorbance
Number R 6 First Absorbance
Number R 6 Second Initial
Absorbance
Number R 6 Second Absorbance
Number R 3 Data Alarm e For details, see Chapter 12 Instrument alarms.
Number - 6 Prozone Value Blank: not sent by the cobas® 8000 modular
analyzer series. Reserved for future use.
The following fields contain no data.

Roche Diagnostics
C-36 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument ISE Calibration Result Record - M(ICR)

ISE Calibration Result Record - M(ICR)

The data manager sends calibration data from the ISE module in the manufacturer-
defined ISE Calibration Result M(ICR) record.
M|1|ICR|bmserv|MU1#ISE#1#1|Valid|Valid|Valid|0^0^0^0^0^0^0^0^0^0|1^2^3
^4^5^6^7^8^9^10|1^2^3^4^5^6^7^8^9^10|-32.7^-34.7^-28.4^-30.2^50.4^
131.5^147.7^0.0^49.9^-4.7|-34.2^-45.5^-24.8^-34.5^56.3^4.76^4.70^0.0^
56.2^-0.17|136.4^138.5^130.6^134.1^-44.9^89.0^100.3^0.0^-45.1^0.7|

Field Ref. Value Host DM Max Description

Size
1 14 M R 1 Record type ID, fixed value signifying manufacturer record.
2 14 Number R 6 Sequence Number:
This record appears as the next layer of the Message Header Record. For one
record, the field value is ‘1’; for specifying several, sequence numbers starting
from 1 are assigned.
3 14 ICR R 3 Record Type Sub ID: set to ‘ICR’.
4 14 String R 6 Operator ID:
ID of the operator who performed the calibration at the Control Unit or
analyzer.
5 14 String R 20 Analytical unit ID:
ID of the analytical unit (module) the test belongs to.
e For details, see Identifier of the analytical unit sent to host on page B-30.
6 14 String O 7 Na Calibration Alarm: Na test calibration status.
o Valid = the calibration was successful.
o Invalid = the calibration was unsuccessful.
7 14 String O 7 K Calibration Alarm: K test calibration status.
o Valid = the calibration was successful.
o Invalid = the calibration was unsuccessful.
8 14 String O 7 Cl Calibration Alarm: Cl test calibration status.
o Valid = the calibration was successful.
o Invalid = the calibration was unsuccessful.
9 14 Complex R Na Data Alarm: Na test data alarm.
e For details, see ISE data alarms on page C-37.
10 14 Complex R K Data Alarm: K test data alarm.
e For details, see ISE data alarms on page C-37.
11 14 Complex R Cl Data Alarm: Cl test data alarm.
e For details, see ISE data alarms on page C-37.
12 14 Complex R Na Data: Na test calibration analytical data.
e For details, see ISE calibration analytical data on page C-38.
13 14 Complex R K Data: K test calibration analytical data.
e For details, see ISE calibration analytical data on page C-38.
14 14 Complex R Cl Data: Cl test calibration analytical data.
e For details, see ISE calibration analytical data on page C-38.

ISE data alarms

The data alarms from the ISE calibration is passed in the following fields.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-37
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
ISE Calibration Result Record - M(ICR) cobas® 8000 instrument

Na (Sodium) Field 9
K (Potassium) Field 10
Cl (Chlorine) Field 11

Each of these fields is a complex type, and contains 10 number type components.
Each component is a Number type, max. length 3.
Internal standard solution electromotive force data alarm^
Low solution electromotive force data alarm^
High solution electromotive force data alarm^
Calibrator solution electromotive force data alarm^
Slope for display data alarm^
Internal standard solution concentration data alarm^
Calibrator solution concentration data alarm^
Carryover rate alarm^
Calculation slope value alarm^
Numbers for compensation data alarm

ISE calibration analytical data

The analytical data from the ISE calibration is passed in the following fields.

Na (Sodium) Field 12
K (Potassium) Field 13
Cl (Chlorine) Field 14

Each of these fields is a complex type and contains 10 number type components.
Each component is a Number type, max. length 6.
Internal standard solution electromotive force data^
Low solution electromotive force data^
High solution electromotive force data^
Calibrator solution electromotive force data^
Slope for display data^
Internal standard solution concentration data^
Calibrator solution concentration data^
Carryover rate^
Calculation slope value^
Numbers for compensations data

Roche Diagnostics
C-38 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument E-module (immunology) Calibration Result Record - M(ECR)

E-module (immunology) Calibration Result Record - M(ECR)

The data manager sends calibration data from the Elecsys immunology E-module in
the manufacturer-defined E-module Calibration Result M(ECR) record.

Example M|1|ECR|bmserv|^^^1|LotCalibration|MU1#e602#2#1|157328||0|158941|O|I^O
^\M^O^\S^O^\R^1.074^\D^O^\L^^\F^O^\Y^O^\B^O^|936.337^888.767\39609.680
^39716.950|||||20101018175819|

Field Ref. Value Host DM Max Description

Size
1 14 M R 1 Record type ID, fixed value ‘M’ signifying manufacturer record.
2 14 Number R 6 Sequence Number:
This record appears as the next layer of the Message Header Record.
For one record, the field value is ‘1’; for specifying several, sequence
numbers starting from 1 are assigned.
3 14 ECR R 3 Record Type Sub ID: set to ‘ECR’.
4 14 String R 6 Operator ID: ID of the operator who performed the calibration at the
analyzer.
5 14 Complex R Test Code (Application Code), the number identifying the analyte.
^^^TestCode
The TestCode is a Number type, max. length 5.
6 14 String R 24 Calibration method. Permitted values:
o NoCalibration
o LotCalibration
o ContainerCalibration
o InheritedLotCalibration
o InheritedItemCalibration
o UserModifiedCalibration
o UnmaskedCalibration
o FailedCalibration
7 14 String O 20 ID of the analytical unit (module) the test belongs to.
e For details, see Identifier of the analytical unit sent to host on
page B-30.
8 14 Number O 8 e Pack Lot No. (Reagent lot number). 1 to 99999999
9 14 Field contains no data.
10 14 Number O 1 Expired e Pack Flag
o 0 Calibration performed with “Not Expired e Pack”
o 1 Calibration performed with “Expired e Pack”
11 14 String R 8 Calibrator Lot No: although a string type, possible values are 1 to
99999999.
12 14 Character O 1 Result Status:
o 0 OK (Capital letter O)
o F Failed

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-39
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
E-module (immunology) Calibration Result Record - M(ECR) cobas® 8000 instrument

Field Ref. Value Host DM Max Description

Size
13 14 Complex O Result Characteristics. Format:
CharacteristicID^Value^Detail
This field is often repeated. Each record describes whether a certain
calibration characteristic was violated or not. For some
characteristics, the actual value is provided. In some cases, the value is
empty, depending on whether a test is qualitative or quantitative.
13.1 Character O CharacteristicID This can take one of the following values:
I Missing Values
M Monotony of Curve
S Minimum Signal
R Calibrator Factor
D Deviation of Duplicate Measurement
F Minimum Acceptance Difference
Y System Error
L Slope
B Min./Max. Signal
13.2 Number / O Value Value can have one of the following values:
Character o a numeric value, showing the actual value of the
result.
o O, (Capital letter O) meaning no violation or no
failure.
o F, meaning a violation or failure.
13.3 - Detail Details are the details for each calibrated level, but
this is not supported in the data manager.
14 14 Complex R Calibration signal values repeated for two levels.
Format:
<Signal1Level1>^<Signal2Level1>\<Signal1Level2>^<Sig
nal2Level2>
Each value is the numeric value sent by the analyzer.
15 14 Field contains no data.
16 14 Field contains no data.
17 14 Field contains no data.
18 14 Field contains no data.
19 14 DateTime O 14 Date and time measurement was performed
(YYYYMMDDHHMMSS).

Roche Diagnostics
C-40 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 7 ASTM text content (LIS2 - A2)
®
cobas 8000 instrument Message Termination Record

Message Termination Record

Use this as the final record in every message, to show that the message is completed.
L|1|N

Field Ref. Value Host DM Description

1 12.1 L R R Record Identifier, fixed value
2 12.2 1 R R Sequence number, fixed value, as there is only ever one termination record in a
message.
3 12.3 N R R Termination code. In this case a fixed value, N, meaning normal termination.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) C-41
7 ASTM text content (LIS2 - A2) cobas® 8000 data manager
Message Termination Record cobas® 8000 instrument

Roche Diagnostics
C-42 Host Interface Manual · Version 1.02.05 (revision 1)
 HL7 Reference D

8 HL7 protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

9 HL7 text content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7
10 HL7 Acknowledgement handling . . . . . . . . . . . . . . . . . . . . . . . D-43
cobas® 8000 data manager 8 HL7 protocol
®
cobas 8000 instrument Table of contents

HL7 protocol

This chapter presents the lower layers of the HL-7 protocol, as used by cobas® 8000
data manager.

In this chapter Chapter 8

HL7 protocol lower level ................................................................................................ D-5
Overview of HL7 ............................................................................................................. D-5
Physical communication ................................................................................................ D-5
Minimal Layer Protocol ........................................................................................... D-6

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-3
8 HL7 protocol cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
D-4 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 8 HL7 protocol
®
cobas 8000 instrument HL7 protocol lower level

HL7 protocol lower level

This chapter gives a low-level description of the HL7 protocol used to communicate
with cobas® 8000 data manager.

Overview of HL7

HL7 or “Health Level 7” is one of the most comprehensive and widely-used protocols
in the healthcare environment. Nevertheless, the standard is so wide and complex
that cobas® 8000 data manager uses only a subset.
The HL7 Standard currently addresses the interfaces among various systems that
send or receive patient admissions/registration, discharge or transfer (ADT) data,
queries, resource and patient scheduling, orders, results, clinical observations, billing,
master file update information, medical records, scheduling, patient referral, and
patient care. It does not try to assume a particular architecture with respect to the
placement of data within applications but is designed to support a central patient care
system as well as a more distributed environment where data resides in departmental
systems.
The cobas® 8000 data manager implementation of HL7 is based on v2.5.

Physical communication

The standard HL7 refers to the highest level of the Open System Interconnection
(OSI) model of the International Standards Organization (ISO). The HL7 Standard is
primarily focused on the issues that occur within the seventh, or application, level.
These are the definitions of the data to be exchanged, the timing of the exchanges,
and the communication of certain application-specific errors between the
applications. This chapter gives some recommendations for how to use HL7 with
cobas® 8000 data manager.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-5
8 HL7 protocol cobas® 8000 data manager
Physical communication cobas® 8000 instrument

Minimal Layer Protocol

Data framing is done using the Minimal Layer Protocol (MLP) defined in the HL7
standard, (sometimes referred to as MLLP, Minimal Lower Layer Protocol).
HL7 messages are enclosed by special characters to form a block. The format is as
follows:
<start_block>data<end_block><CR>

<start_block> Start Block character (1 byte)

ASCII <VT>, in other words, <0x0B>. This should not be confused
with the ASCII characters SOH or STX.
data Data (variable number of bytes)
This is the HL7 data content of the block. The data can contain any
displayable ASCII characters and the carriage return character,
<CR>.
<end_block> End Block character (1 byte)
ASCII <FS>, in other words, <0x1C>. This should not be confused
with the ASCII characters ETX or EOT.
<CR> Carriage Return (1 byte)
The ASCII carriage return character, in other words, <0x0D>.

The values used are <VT> for the start block and <FS> for the end block.

Figure D-1 The HL7 data framed according to the HL7 standard.

Roche Diagnostics
D-6 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Table of contents

HL7 text content

HL7 field definitions

This section describes all the HL7 fields used in messages sent to or from cobas® 8000
data manager.

In this chapter Chapter 9

HL7 messages .................................................................................................................. D-9
Messages sent only by the data manager ............................................................... D-9
Messages transmitted only by the host ................................................................ D-10
Messages sent by either data manager or the host ............................................. D-10
HL7 Segment description ............................................................................................. D-11
HL7 field attributes ................................................................................................. D-11
Text encodings ........................................................................................................ D-12
Message Header Segment - MSH ................................................................................ D-12
Message Acknowledgement Segment - MSA ............................................................ D-14
Patient Identification Segment - PID ......................................................................... D-14
Specimen Segment - SPM for patient and quality control results .......................... D-15
Specimen Segment - SPM for calibration results ..................................................... D-18
Specimen Container Detail Segment - SAC .............................................................. D-19
Observation Request Segment - OBR ........................................................................ D-19
Timing Quantity Segment - TQ1 ................................................................................ D-20
Observation Result Segment - OBX (for patient results) ........................................ D-22
Observation Result Segment - OBX (for QC results) .............................................. D-26
Observation Result Segment - OBX (for calibration results) .................................. D-29
Measurement of C-module photometric Calibration Results .......................... D-31
Measurement of ISE Calibration Results ............................................................. D-32
Measurement of E-module immunological Calibration Results ..................... D-33
Calibration alarm flags ........................................................................................... D-34
Test Code Detail Segment - TCD ............................................................................... D-35
Substance Identifier Segment - SID ............................................................................ D-35
Comment Segment - NTE ........................................................................................... D-36
Types of comment segment ................................................................................... D-37
Query Parameter Segment - QPD (for a test selection inquiry) ............................. D-37
Query Parameter Segment - QPD (for a Result Query) .......................................... D-39
Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-7
9 HL7 text content cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Query Parameter Segment - QPD (for an Order Query) ........................................ D-40

Response Control Parameter Segment - RCP ........................................................... D-41
Equipment Detail Segment - EQU ............................................................................. D-41
Equipment Command Segment - ECD ..................................................................... D-42

Roche Diagnostics
D-8 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument HL7 messages

HL7 messages

This section describes the types of HL7 message transferred by the host or data
manager. In the following charts:
o [ ] Square brackets indicate an optional segment. (0 - 1 times.)
o { } Curly brackets indicate a segment or group of segments that may be optionally
repeated. (1 - n times.)
e For more details on message flow and how messages follow each other, see
Communication scenarios on page B-10.

Messages sent only by the data manager

Only data manager sends the following types of message.

Message Segments Message Type Description

Inquiry for MSH TSREQ Inquiry for test selections
sending test QPD is made after a rack has
RCP
selections passed the ID reader.
Result report MSH OUL^R22 Reports on the sample
PID results.
SPM OUL^R22^REAL QC results passed
SAC through data manager
{ on reception
OBR
OUL^R22^BATCH Manual upload of QC
TQ1
results.
OBX
TCD Upload of patient sample
{[SID]}(a) results in reply to a result
{NTE} query.
}(b)
Calibration MSH OUL^R22^PCUPL Reports calibration
data { OUL^R22^ICUPL results.
SPM
OUL^R22^ECUPL
OBR
OBX
SID
}
(a) For messages containing patient results from the ISE module, no SID segment is sent.
(b) There may be multiple OBR Segments per PID Segment, and multiple SID and NTE Segments per OBX
Segment. However, you may only have one OBX Segment per OBR.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-9
9 HL7 text content cobas® 8000 data manager
HL7 messages cobas® 8000 instrument

Messages transmitted only by the host

The host can send the following types of message.

Message Segments Message Type Description

Result Query MSH RSREQ Inquiry for test results
QPD for a given sample ID
RCP sent by the host.
Order Query MSH TSREQ Inquiry for all test
QPD selections for a given
RCP sample ID sent by the
host.
Masking MSH EAC^U07 Instructs data manager
EQU to mask or unmask
{ certain tests.
ECD
}

Messages sent by either data manager or the host

The data manager and a connected LIS can send an Acknowledge message,
depending on their HL7 settings.
Either can send a test selection information message.

Message Segments Message Type Description

Acknowledge MSH ACK HL7 Application Acknowledge for
MSA incoming orders
Test Selection MSH OML^O33 Test selection sent by the host for
Information PID a sample as answer to a test
(from host) SPM selection inquiry or as unsolicited
SAC order.
[{
[TQ1](a)
OBR
}]
Test Selection MSH OML^O33 Test selection sent by the data
Information SPM manager as response to an order
(from data [SAC] query.
manager if [{
sample found) [TQ1](b)
OBR
}]
Test Selection MSH OML^O33 Test selection sent by the data
Information SPM manager as response to an order
(from data query.
manager if
sample not
found)
(a) TQ1 Segments must be identical for all OBR Segments.
(b) TQ1 Segments must be identical for all OBR Segments.

Roche Diagnostics
D-10 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument HL7 Segment description

HL7 Segment description

This section describes the content of the HL7 fields used in communications between
the host and the cobas® 8000 data manager.

HL7 field attributes

Types of attributes held by a field in an HL7 message are explained below.

Attribute Description
Field The segment header, and the number of the field in the segment.
Value This shows either:
o The precise text to be sent.
o The format of the field.
The format of the field can take one of the following values:
o Character. A single character.
o String: A character string.
o Number: A numeric value. Positive (+) or negative (-) is indicated
before the numeric value. If it is not indicated, it is treated as
positive (+).
If a decimal point is not included, the numeric value is treated as
an integer. There are no restrictions for placing ‘0’ in the front or
for multiple ‘0’ placed at the end of numbers with decimal points.
o Date. Always use the 4-digit Gregorian year. The format is
YYYYMMDD (YYYY is the 4-digit Gregorian year, MM is the
month, DD is the day). For example, September 5, 2009 is
indicated 20090905.
o Time: 24-hour military time.
The format is HHMMSS (HH is the hour, MM is the minute, and
SS is the second).
o DateTime. A combination of Date and Time.
The format is: YYYYMMDDHHMMSS.
o Complex. A field in which multiple data components are
combined, separated by the component delimiter. Each
component may take one of the other formats.
Host If sent from the host or LIS, this field is either:
o R, required
o O, optional
DM If sent from data manager, this field is either:
o R, required (always sent)
o O, optional
Description A description of the field, including use and permitted values. In the
case of complex fields, this includes a description of individual
components.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-11
9 HL7 text content cobas® 8000 data manager
Message Header Segment - MSH cobas® 8000 instrument

Text encodings

The data within the message has to be Unicode encoded as UTF-8 characters. For
characters from decimal 32 to 127 also ASCII can be used. Characters from 0 to 31
are control characters and therefore not allowed within the HL-7 fields.

The host needs to handle UTF-8

In situations where the data manager operators will be able to enter UTF-8 characters, the
WARNING host will have to support UTF-8, or be able to recognize and translate from UTF-8. If
necessary, it is possible to prevent operators from entering UTF-8 characters by running
the data manager in pass-through mode.

Escaping the characters as defined for the delimiter characters is not supported (see
Header Segment, field no. 2).

Message Header Segment - MSH

This segment occurs at the front of every message, and shows the sender and receiver
and other important general information about the message.
Host and DM columns indicate whether the data is Required or Optional when sent
from the Host or data manager respectively.
MSH|^~\&|cobas 8000||host||20090402173655||OUL^R22|13007||2.5||||ER||
UNICODE UTF-8|

Field Value Host DM Description

MSH-1 | R R Field separator, fixed value = vertical bar [124]
MSH-2 ^~\& R R Delimiter definitions, fixed value:
o ^ Component (or sub-field) delimiter = caret [94]
o ~ Repeat delimiter = tilde [126]
o \ Escape character = backslash [92] (not supported)
o & Sub-component (or sub-sub-field) delimiter = ampersand [38]
A carriage return (ASCII 13) marks the end of each segment.
MSH-3 String - R Sending application, by default: cobas 8000
e To edit this, see Identifying the data manager application to the host on page B-25.
O - Sending identifier, if sent used only for tracing information
MSH-4 Field contains no data.
MSH-5 String - R Receiving application, fixed value: host
O - Receiving identifier, sent by host for tracing information
MSH-6 Field contains no data.
MSH-7 DateTime O O Date and time message sent
MSH-8 Field contains no data.

Roche Diagnostics
D-12 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Message Header Segment - MSH

Field Value Host DM Description

MSH-9 Complex R R Message Type. This is the code that defines the message type, according to the HL7
standard:
o TSREQ
o RSREQ
o OML^O33
o OUL^R22
o EAC^U07
o OUL^R22^PCUPL (C-module, or Photometric, Calibration Result)
o OUL^R22^ICUPL (ISE Calibration Result)
o OUL^R22^ECUPL (E-module, or Immunology, Calibration Result)
o ACK
In specific circumstances, the following message type codes are sent by the data manager:
o OUL^R22^REAL (first transmission of the QC results)
o OUL^R22^BATCH (repeat transmission of QC results)
o OUL^R22^BATCH (patient sample results as a reply to result query)
MSH-10 String R R Message Control ID that uniquely identifies the message, for example, a sequence
number or GUID string (as autogenerated by Microsoft programs to uniquely identify
objects etc.).
MSH-11 Field contains no data.
MSH-12 2.5 O R Version ID for HL7 version used, fixed value string.
MSH-13 Field contains no data.
MSH-14 Field contains no data.
MSH-15 Field contains no data.
MSH-16 String O R Application Acknowledgement Type. This field defines the conditions under which the
receiver has to respond with an acknowledgement message.
This field may contain:
o AL
Always send an acknowledgement message.
o SU
Send an acknowledgement message only after the message has been successfully
processed.
o ER
Send in error/reject conditions only.
o NE
Never send an acknowledgement.
e The data manager does not support all these options in all situations. For details see
Chapter 10 HL7 Acknowledgement handling.
MSH-17 Field contains no data.
MSH-18 UNICODE O R String defining the character set. Fixed value.
UTF-8
Further MSH fields contain no data.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-13
9 HL7 text content cobas® 8000 data manager
Message Acknowledgement Segment - MSA cobas® 8000 instrument

Message Acknowledgement Segment - MSA

The host and the data manager use the message acknowledgement segment in a
acknowledgement message.
MSA|AE|38764|ORA-20001: Validation error|
MSA|AA|38764||

Field Value Host DM Description

MSA-1 String R R Acknowledgement code
o AA
Accept. This acknowledges the message is valid and was successfully processed.
o AE
Error. This indicates that the message sent was not valid in format or content, and
could not be processed.
o AR
Reject. The data manager currently does not send this acknowledgement code.
e For details of acknowledgement handling, see HL7 acknowledgement messages on
page D-45.
MSA-2 String R R Message Control ID, from MSH-10 segment of the message that the data manager is
acknowledging.
MSA-3 String O O Text message providing potentially useful diagnostic information. This can be generated
from various sources, including errors passed from databases or the operating system.
The same message is written to the log, where there may be further information.
e For details of logging, see Setting logging levels on page B-30.

Patient Identification Segment - PID

The data manager uses the patient identification segment to send patient information
in a Result Report message. The host uses the patient identification segment to send
patient information in a test selection download message.
PID|1|SH25111965M|||Doe^John||19651125|M
PID|1||||^|||

Field Value Host DM Description

PID-1 1 O R Set ID, fixed value number.
PID-2 String O/R O/R Patient ID.
This field is mandatory only if some patient demographic data is sent, in other words, if
one or more of fields 5, 7, or 8 contain data.
PID-3 Field contains no data.
PID-4 Field contains no data.
PID-5 Complex O O Patient last name and first name: Two string components, each max. 30 characters long:
Last_name^First_name
PID-6 Field contains no data.

Roche Diagnostics
D-14 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Specimen Segment - SPM for patient and quality control results

Field Value Host DM Description

PID-7 Date O O Date of birth (YYYYMMDD)
PID-8 String O O Sex of patient
o M Male
o F Female
o U Unknown. Any other value defaults to unknown, and is returned to the host as U.

The data manager supports only M, F, or U for patient sex.

For male patients, the host must send M, for females, F. Otherwise the wrong reference
WARNING range might be applied. The data manager reads any other value as U, and applies the
reference ranges for a patient of unknown sex.
Make sure the host sends only M, F, or U, as required. Each new configuration must be
tested to ensure the correct data transfer between the data manager and the host.

Specimen Segment - SPM for patient and quality control results

The data manager uses the specimen segment to send information about the
specimen in a Result Report message, and in a test selection upload message. The host
uses the specimen segment to send information about the specimen in a test selection
download message.
e For the use of the Specimen segment SPM with calibration results, see Specimen Segment -
SPM for calibration results on page D-18.

When identifying the sample by sample ID (default):

SPM||10005||S1||not|||||P|||^^^^|||20100503142217||||||||||SC|

When identifying the sample by sequence number:

SPM||^1031||S1||not|||||P|||^^^^|||20110715085411||||||||||SC

For a quality control result:

SPM||PNU^123456^301^20111213||S1||not|||||Q|||^^^^|||20111203142217|||
|||||||SC|

Field Value Host DM Description

SPM-1 Field contains no data.
SPM-2 String R R Sample ID.
For QC or Patient results when using sample IDs (default)
sequence For Patient Results, the number or alphanumeric string read from sample’s
numbers: barcode, (string of max. 22 characters padding not allowed).
Complex
Note this is a simple string field in this situation.
Patient results when the sample is identified by sequence number
SPM-2.1 String - - SampleID If the sample is identified by sequence number, and a sequence
number is sent in SPM-2.2, this is empty.
SPM-2.2 Number R R Sequence If the sample is identified by sequence number, this contains
_Number the sequential number. (Max. value = 60,000.) If the host sends
a sample ID in SPM-2.1, the data manager ignores this
component.
e For details of sequence numbers, see Identifying patient
samples by sequence number on page E-45.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-15
9 HL7 text content cobas® 8000 data manager
Specimen Segment - SPM for patient and quality control results cobas® 8000 instrument

Field Value Host DM Description

Quality control material
For Quality Control material, Name^Lot^ID^ExpDate
SPM-2.1 String O/R R Name For Quality Control results, the control name, for example,:
PNU.
SPM-2.2 Number - O/R Lot Control lot. QC only: not used for patient results.
SPM-2.3 Number - O/R ID Control identifier (a unique control ID contained in data
manager). QC only: not used for patient results.
SPM-2.4 Date O/R ExpDate Expiry date of control lot. Format:YYYYMMDD.
Ordering test solutions for QC is not possible from host.
e For details of how the sample identifier SPM-2 is used with calibration
result messages, see Specimen Segment - SPM for calibration results on
page D-18.
SPM-3 Field contains no data.
SPM-4 String R R Specimen Type
This is a code that identifies the type of specimen. This field is blank for
calibration results
S1 Serum / Plasma
S2 Urine
S3 Cerebrospinal Fluid
S4 Supernatant
S5 Other fluids
S6 Whole blood
S7 Oral fluids (Saliva)
S8 Reserved for future use
S9 Reserved for future use
SA Reserved for future use
Depending on the version and modules installed, not all of these types may
be available on any particular system.
For QC samples, the host should disregard any value in this field.
SPM-5 Field contains no data.
SPM-6 String O O Specimen Additives.
o not
Not a prediluted sample
o pre-diluted
Prediluted sample
o Empty in a test selection upload in response to an order query.
SPM-7 Field contains no data.
SPM-8 Field contains no data.
SPM-9 Field contains no data.
SPM-10 Field contains no data.
SPM-11 Character O O Specimen role. This is a code that identifies what purpose the specimen is
used for.
o P, meaning patient result.
o Q, meaning quality control result. (Only sent by data manager)
o Empty in a test selection upload in response to an order query.
SPM-12 Field contains no data.
Roche Diagnostics
D-16 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Specimen Segment - SPM for patient and quality control results

Field Value Host DM Description

SPM-13 Field contains no data.
SPM-14 Complex O O Specimen description in format:
C1^C2^C3^C4^C5
o C1 Sample Comment 1. String with up to 30 characters
o C2 Sample Comment 2. String with up to 25 characters
o C3 Sample Comment 3. String with up to 20 characters
o C4 Sample Comment 4. String with up to 15 characters
o C5 Sample Comment 5. String with up to 10 characters
These comments are visible on the Control Unit.
In ASTM this data is transferred in the Comment Record that follows the
Order record.
SPM-15 Field contains no data.
SPM-16 Field contains no data.
SPM-17 DateTime O O Specimen collection date / time. (YYYYMMDDHHMMSS)
SPM-18 Field contains no data.
SPM-19 Field contains no data.
SPM-20 Field contains no data.
SPM-21 Field contains no data.
SPM-22 Field contains no data.
SPM-23 Field contains no data.
SPM-24 Field contains no data.
SPM-25 Field contains no data.
SPM-26 Field contains no data.
SPM-27 String O R Container type.
o SC Standard cup
o MC Micro cup

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-17
9 HL7 text content cobas® 8000 data manager
Specimen Segment - SPM for calibration results cobas® 8000 instrument

Specimen Segment - SPM for calibration results

The data manager uses the specimen segment in a calibration result message to send
information about the specimen.
SPM||1^888888^901^1^20111130|||||||||C^P|
e For details of the use of the Specimen segment (SPM) with patient and quality control
results, see Specimen Segment - SPM for patient and quality control results on page D-15.

Field Value Host DM Description

SPM-1 Field contains no data.
SPM-2 Complex - O/R Identifier for the sample.
For C-module and E-module calibration materials,
Level^Lot^Code^Count^ExpDate
SPM-2.1 Number O/R Level Calibrator level
SPM-2.2 Number O/R Lot Calibrator lot
SPM-2.3 Number O/R Code Calibrator material code
SPM-2.4 Number O/R Count The calibrator bottle count number
SPM-2.5 Date O/R ExpDate Expiry date of control lot. Format: YYYYMMDD.
This is a required field, except for ISE calibration results, when it is always
empty.
It is not possible to order test selections for calibration material from the
host.
SPM-3 Field contains no data.
SPM-4 Field contains no data
SPM-5 Field contains no data.
SPM-6 Field contains no data.
SPM-7 Field contains no data.
SPM-8 Field contains no data.
SPM-9 Field contains no data.
SPM-10 Field contains no data.
SPM-11 Complex - R Specimen role. This is a code that identifies what purpose the specimen is
used for.
C^P C-module (Photometric) Calibration
C^I ISE module Calibration
C^E E-module (Immunological) Calibration
SPM-12 Field contains no data.
SPM-13 Field contains no data.
SPM-14 Field contains no data.
SPM-15 Field contains no data.
SPM-16 Field contains no data.
SPM-17 DateTime - O Specimen collection date / time. (YYYYMMDDHHMMSS)
Further SPM fields contain no data for calibration results.

Roche Diagnostics
D-18 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Specimen Container Detail Segment - SAC

Specimen Container Detail Segment - SAC

The data manager uses the specimen container detail (SAC) segment to identify the
location of the sample’s container in a result report or in a test selection request
message.
The host uses the specimen container detail (SAC) segment to identify the location of
the sample’s container in a test selection download message. The host sends this
information if it has it, for example if a pre-analytic system is being used, or if it has
received it from the data manager, for example in the response to a query.
SAC||||||||||50042|2|

Field Value Host DM Description

SAC-1 Field contains no data.
SAC-2 Field contains no data.
SAC-3 Field contains no data.
SAC-4 Field contains no data.
SAC-5 Field contains no data.
SAC-6 Field contains no data.
SAC-7 Field contains no data.
SAC-8 Field contains no data.
SAC-9 Field contains no data.
SAC-10 String O O Rack ID as displayed on the Control Unit. (Uploaded to host only if known to data
manager.)
SAC-11 String O O Position in rack. (Last known position, where available.)

Observation Request Segment - OBR

The data manager uses the observation request segment in a result report message or
a test selection upload message. The host uses the observation request segment in a
test selection download message.
OBR|1|||989^|||||||A
OBR|4|||8717^Inc|||||||A

Field Value Host DM Description

OBR-1 Number O O Set ID. The first segment is 1, then increments by 1 for each subsequent
OBR segment.
OBR-2 Field contains no data.
OBR-3 Field contains no data.
OBR-4 Complex R R Universal service identifier (identifies the test or analyte tested for, often
called the “testcode” or “application code”). If sent from the host, it also
includes the dilution factor.
Testcode^Dilution

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-19
9 HL7 text content cobas® 8000 data manager
Timing Quantity Segment - TQ1 cobas® 8000 instrument

Field Value Host DM Description

OBR-4.1 Number R R Testcode Test code (application code), that identifies the test. The host
can download the test numbers of calculated tests, if the test is
programmed on the data manager. For details, see the cobas®
8000 modular analyzer series Operator’s Manual.
For serum index tests, you must send all three test types
together (lipemic, icteric, and hemolytic), or send a test profile
that contains all three. Otherwise the test will not be run.
e For more details on sending serum index orders, see
Sending test selections on page B-12.
OBR-4.2 String O - Dilution Dilution factor. This is only sent from the host to the data
manager.
Permitted values are:
o For an ISE module, the only permitted factor is 1, meaning
no dilution.
o For a C-module (photometry): Dec, Inc, 1
o For an E-module (immunoassay): 1, 2, 5, 10, 20, 50, 100,
400
No dilution can also be indicated with an empty code.
OBR-5 Field contains no data.
OBR-6 Field contains no data.
OBR-7 Field contains no data.
OBR-8 Field contains no data.
OBR-9 Field contains no data.
OBR-10 Field contains no data.
OBR-11 String R - Action code sent by host:
o A Add test, or rerun test if it already exists.
o R Rerun test (NB: different from HL7 definitions), or add test, if it does
not exist.
o C Cancel test
The other OBR fields contain no data.

Timing Quantity Segment - TQ1

The data manager uses this segment in a test selection message (optionally) and in a
result report message. The host uses this segment in a test selection messages
(optionally).
TQ1|1||||||||R|

Field Value Host DM Description

TQ1-1 1 O R Set ID. Fixed value number.
TQ1-2 Field contains no data.
TQ1-3 Field contains no data.
TQ1-4 Field contains no data.
TQ1-5 Field contains no data.
TQ1-6 Field contains no data.
TQ1-7 Field contains no data.

Roche Diagnostics
D-20 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Timing Quantity Segment - TQ1

Field Value Host DM Description

TQ1-8 Field contains no data.
TQ1-9 String R R Priority
o S STAT sample. STAT samples must be placed on a STAT rack.
o R Routine sample (default)

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-21
9 HL7 text content cobas® 8000 data manager
Observation Result Segment - OBX (for patient results) cobas® 8000 instrument

Observation Result Segment - OBX (for patient results)

This section describes how the data manager uses the observation result segment
(OBX) in a result report message to send the results of patient tests.
e For details of how the data manager uses OBX with quality control results, see
Observation Result Segment - OBX (for QC results) on page D-26.
e For details of how the data manager uses OBX with calibration results, see Observation
Result Segment - OBX (for calibration results) on page D-29.

Patient result examples OBX|1||990||0.99|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||201010200959

05|bmserv^SYSTEM||128|ISE^2^MU1#ISE#1#2^4|20101020095921|
OBX|3||8717||1^-0.02|mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20101019175
614|bmserv^SYSTEM||77|c701^1^MU1#c701#1#1^6|20101019180627|

A Result Segment for a result below the EP-17A level of detection.

OBX|1||989||2.1|mmol/L|^TECH~12 - 144^NORM~^CRIT~^USER|LoD|||F|||20100
621084348|bmserv^SYSTEM||28|ISE^1^MU1#ISE#1#1^3|20100621084404|

Field Value Host DM Description

OBX-1 Number R Set ID. The first segment in a set has the value 1. For each subsequent
segment in the set, this value increments by 1.
OBX-2 Field contains no data.
OBX-3 Number R The test code. (Observation identifier, or Application code) This identifies
the test or analyte which this message relates to.
OBX-4 Field contains no data.
OBX-5 Complex R Result value
The result values are only transmitted for patient and QC results.
ReportableResult^AdditionalResultValues
Quantitative results:
o ReportableResult The result. A missing result is sent as 7 spaces.
(ASCII 32 / 0x20).
o AdditionalResultValues Empty or a qualitative flag.
Qualitative results:
o ReportableResult
For C-module and ISE module: an integer code from -2 to 3 inclusive.
For E-module: an integer code -1, 0, 1.
The codes can be configured on the cobas® 8000 instrument, under
Utility > Application > Range, see cobas® 8000 modular analyzer series
Operator’s Manual for details.
o AdditionalResultValues
The quantitative result, like value for a quantitative result. For E-
module qualitative results this contains COI.
OBX-6 String. R Units of measurement used for measuring the result

Roche Diagnostics
D-22 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Observation Result Segment - OBX (for patient results)

Field Value Host DM Description

OBX-7 Complex R Reference ranges, if defined. For patient results, this consists of two strings:
RangeDefinitionString^TypeOfRange
These can occur as a repeated field, for example:
0.5 - 7.5^TECH~3.3 - 5.1^NORM~^CRIT~^USER
If a range is not defined, the RangeDefinitionString is blank.
A required field for patient results.
OBX-7.1 String O The RangeDefinitionString string component can consist of the any of
the following:
o Two numbers (with or without decimal points) separated by space-
hyphen-space, for example,
0.5 - 7.5
Note that either or both of these number may potentially be negative,
for example,
-10 - -7
o A “greater than” or “less than” value, for example,
< 0.1
o A comma-separated string of permissible values, for example,
Y,N,U
-,+,++
OBX-7.2 String O/R The TypeOfRange string component can consist of any of four values.
o TECH Hard-coded value to indicate “Technical Range”
o NORM Hard-coded value to indicate “Normal Range”
o CRIT Hard-coded value to indicate “Critical Range”
o USER Hard-coded value to indicate “User Range”
Note that the different ranges are separated with the repeat delimiter, a tilde
“~”. If a range is not defined, the RangeDefinitionString is blank.
e For QC and calibration results, see Observation Result Segment - OBX
(for QC results) on page D-26 or Observation Result Segment - OBX (for
calibration results) on page D-29.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-23
9 HL7 text content cobas® 8000 data manager
Observation Result Segment - OBX (for patient results) cobas® 8000 instrument

Field Value Host DM Description

OBX-8 String O Abnormal flags. This gives a code that identifies if the result is normal or
abnormal.
This field is blank for manually-edited and QC results.
HH Above high critical value
H Above high normal value
N Normal
L Below low normal value
LL Below low critical value
A Alphanumeric result out of normal range
AA Alphanumeric result out of critical range
LoB Below the Limit of Blank. (Enhancement to HL7.)
LoD Below the Limit of Detection. (Enhancement to HL7.)
LoQ Below the Limit of Quantitation. (Enhancement to HL7.)
No data signifies that no validation against ranges has been
performed.
If more than one flag is triggered, only the most extreme flag is sent. The
EP-17 flags, LoB. LoD, and LoQ take precedence over the others.
e For further details on the EP-17A flags, see EP-17A and the result
abnormal flags on page B-8.
OBX-9 Field contains no data.
OBX-10 Field contains no data.
OBX-11 String R Result status
o F First run result, or QC or calibration result
o C Corrected result
o M Manually-edited result
o X Calculated test, but test could not be calculated (for example, divided
by zero)
OBX-12 Field contains no data.
OBX-13 Field contains no data.
OBX-14 DateTime R Pipetting time, in other words, the time that is considered to be when the
test was started.
Note: For manually-performed and calculated tests, this field is empty.
OBX-15 Complex R Active operators in the format:
Instrument operator^Datamanager operator
Each component is a string.
o Instrument operator
This is the username the operator used to log into the Control Unit.
Empty in the case of a manual or calculated result.
o Datamanager operator
This is the username the operator used to log into the data manager. If
the result is automatically validated, or the data manager is in pass-
through mode, this reads SYSTEM.
OBX-16 Field contains no data.
OBX-17 Number O Calibration ID as an integer number. This is a unique identifier of the
calibration that the result refers to as it is sent by the instrument.
Sent only if available. It is empty for results that do not have a calibration,
for example, calculated and manual results.

Roche Diagnostics
D-24 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Observation Result Segment - OBX (for patient results)

Field Value Host DM Description

OBX-18 Complex R Measurement unit ID, identifying the module that performed the test.
ModuleType^SubModule^AnalyticalUnitID^InstrumentID^
Bottle^SBNo

OBX-18.1 String R Module One of the following:

Type c502, Results from the specified measuring module,
c701, or manual results entered on behalf of that
e602, module.
ISE, or
c702
DM Results calculated on the data manager, and
for manual results entered on the data
manager, but cannot be attributed to a module.
c8000 Results from the cobas® 8000 modular
analyzer series that cannot be mapped to an
actual measuring submodule, for example,
sample short.
OBX-18.2 Number R SubModule o 1 or 2, for result from a submodule.
o 0 (zero) otherwise.
OBX-18.3 String R Analytical Identifier for the module, as sent to the host. This setting is
UnitID configurable in the cobas® 8000 data manager. Default:
Instrument#ModuleType#Position#SubModule
Example: MU1#c502#2#1
e For details, see Identifier of the analytical unit sent to
host on page B-30.
OBX-18.4 Number R Instrument Instrument number in data manager (A specific identifier
ID inside the data manager which identifies a module. This is a
number which has no relationship to the internal position
of the module in the machine.)
OBX-19 DateTime R Time at which result is available.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-25
9 HL7 text content cobas® 8000 data manager
Observation Result Segment - OBX (for QC results) cobas® 8000 instrument

Observation Result Segment - OBX (for QC results)

This section describes how the data manager uses the observation result segment
(OBX) in a result report message to send the results of quality control tests.
e For details of how the data manager uses OBX with patient results, see Observation Result
Segment - OBX (for patient results) on page D-22.
e For details of how the data manager uses OBX with calibration results, see Observation
Result Segment - OBX (for calibration results) on page D-29.

QC result example OBX|1||8685||121|U/L|120^TARGET~25^SD||||F|||20111019111907|bmserv^SYS

TEM||76|c701^1^MU1#c701#1#1^6^Standby^1|20111019112922|

Field Value Host DM Description

OBX-1 Number R Set ID. The first segment in a set has the value 1. For each subsequent
segment in the set, this value increments by 1.
OBX-2 Field contains no data.
OBX-3 Number R The test code. (Observation identifier, or Application code) This identifies
the test or analyte which this message relates to.
OBX-4 Field contains no data.
OBX-5 Complex R Result value
The result values are only transmitted for patient and QC results.
ReportableResult^AdditionalResultValues
Quantitative results:
o ReportableResult The result. A missing result is sent as 7 spaces.
(ASCII 32 / 0x20).
o AdditionalResultValues Empty or a qualitative flag.
Qualitative results:
o ReportableResult
For C-module and ISE module: an integer code from -2 to 3 inclusive.
For E-module: an integer code -1, 0, 1.
The codes can be configured on the cobas® 8000 instrument, under
Utility > Application > Range, see cobas® 8000 modular analyzer series
Operator’s Manual for details.
o AdditionalResultValues
The quantitative result, like value for a quantitative result. For E-
module qualitative results this contains COI.
OBX-6 String. R Units of measurement used for measuring the result
OBX-7 Complex R Reference ranges, if defined. For quality control results, this consists of two
strings:
RangeDefinition^TypeOfRange
These occur as a repeated field, for example:
120^TARGET~25^SD
OBX-7.1 Number O The RangeDefinition is a decimal or integer value.
OBX-7.2 String O/R The TypeOfRange string components consist of:
o TARGET Hard-coded value to indicate “Expected target value”
o SD Hard-coded value to indicate “Standard deviation”
Note that the different ranges are separated with the repeat delimiter, a tilde
“~”. If a range is not defined, the RangeDefinition is blank.
OBX-8 Field contains no data.

Roche Diagnostics
D-26 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Observation Result Segment - OBX (for QC results)

Field Value Host DM Description

OBX-9 Field contains no data.
OBX-10 Field contains no data.
OBX-11 String R Result status
o F For QC result
OBX-12 Field contains no data.
OBX-13 Field contains no data.
OBX-14 DateTime R Pipetting time, in other words, the time that is considered to be when the
test was started.
Note: For manually-performed and calculated tests, this field is empty.
OBX-15 Complex R Active operators in the format:
Instrument operator^Datamanager operator
Each component is a string.
o Instrument operator
This is the username the operator used to log into the Control Unit.
Empty in the case of a manual or calculated result.
o Datamanager operator
This is the username the operator used to log into the data manager. If
the result is automatically validated, or the data manager is in pass-
through mode, this reads SYSTEM.
OBX-16 Field contains no data.
OBX-17 Number O Calibration ID as an integer number. This is a unique identifier of the
calibration that the result refers to as it is sent by the instrument.
Sent only if available. It is empty for results that do not have a calibration,
for example, calculated and manual results.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-27
9 HL7 text content cobas® 8000 data manager
Observation Result Segment - OBX (for QC results) cobas® 8000 instrument

Field Value Host DM Description

OBX-18 Complex R Measurement unit ID, identifying the module that performed the test.
ModuleType^SubModule^AnalyticalUnitID^InstrumentID^
Bottle^SBNo

OBX-18.1 String R Module One of the following:

Type c502, Results from the specified measuring module,
c701, or manual results entered on behalf of that
e602, module.
ISE, or
c702
DM Results calculated on the data manager, and
for manual results entered on the data
manager, but cannot be attributed to a module.
c8000 Results from the cobas® 8000 modular
analyzer series that cannot be mapped to an
actual measuring submodule, for example,
sample short.
OBX-18.2 Number R SubModule o 1 or 2, for result from a submodule.
o 0 (zero) otherwise.
OBX-18.3 String R Analytical Identifier for the module, as sent to the host. This setting is
UnitID configurable in the cobas® 8000 data manager. Default:
Instrument#ModuleType#Position#SubModule
Example: MU1#c502#2#1
e For details, see Identifier of the analytical unit sent to
host on page B-30.
OBX-18.4 Number R Instrument Instrument number in data manager (A specific identifier
ID inside the data manager which identifies a module. This is a
number which has no relationship to the internal position
of the module in the machine.)
OBX-18.5 String R Bottle Used Reagent Set.
(for o Current
QC) o Standby
o (or empty)
OBX-18.6 Number R SBNo An integer showing the standby bottle number, if used. The
standby bottles are numbered sequentially, starting with 1.
OBX-19 DateTime R Time at which result is available.

Roche Diagnostics
D-28 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Observation Result Segment - OBX (for calibration results)

Observation Result Segment - OBX (for calibration results)

The data manager uses the observation result segment in a result report message to
send the results of calibration results.
e For details of OBX with patient results, see Observation Result Segment - OBX (for patient
results) on page D-22.
e For details of OBX with QC results, see Observation Result Segment - OBX (for QC results)
on page D-26.

Calibration result examples Photometric Calibration Result Segment:

OBX|1||8685||0^3&4&22851&2&22866&|||16|||F||||bmserv||75|c701^1^MU1#c7
01#1#1^6^Standby^1|20111019091421|

ISE Calibration Result Segment:

OBX|1||989||Type-A^0&0&0&0&0&0&0&0&0&0^-32.7&-34.7&-28.4&-30.2&50.4&
131.5&147.7&0.0&49.9&-4.7|||Valid|||F||||bmserv||37|ISE^1^MU1#ISE#1#1
^7|20100316105741|

Immunological Calibration Result Segment:

OBX|1||1||Valid^false^false^false^1.074^false^^false^false^39609.680&3
9716.950^^^^^|||LotCalibration|||F||||bmserv||25|e602^1^MU1#e602#2#1^9
^Current|20101018175819|

Field Value Host DM Description

OBX-1 Number R Set ID. The first segment in a set has the value 1. For each subsequent
segment in the set, this value increments by 1.
OBX-2 Field contains no data.
OBX-3 Number R The test code. (Application code) This identifies the test or analyte which
this message relates to.
OBX-4 Field contains no data.
OBX-5 String R Measurement values
e For photometric calibration results, see Measurement of C-module
photometric Calibration Results on page D-31.
e For ISE calibration results, see Measurement of ISE Calibration
Results on page D-32.
e For Immunological calibration results, see Measurement of E-
module immunological Calibration Results on page D-33.
OBX-6 Field contains no data (for calibration results).
OBX-7 Field contains no data.
OBX-8 String O Calibration alarm flags.
e For details see Calibration alarm flags on page D-34.
OBX-9 Field contains no data (for calibration results).
OBX-10 Field contains no data.
OBX-11 F O Result status.
o F For calibration result
OBX-12 Field contains no data.
OBX-13 Field contains no data.
OBX-14 Field contains no data (for calibration results).
OBX-15 String R This is the username the operator used to log into the Control Unit.
OBX-16 Field contains no data.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-29
9 HL7 text content cobas® 8000 data manager
Observation Result Segment - OBX (for calibration results) cobas® 8000 instrument

Field Value Host DM Description

OBX-17 Number O Calibration ID as an integer number. This is a unique identifier of the
calibration that the result refers to as it is sent by the instrument. Sent
only if available.
OBX-18 Complex R For ISE module:
Analytical unit ID, identifying the module that performed the test.
e The components and values are the same as for patient and QC
results, see Identifier of the analytical unit sent to host on page B-30.
Complex R For C-module (photometric) or E-module (immunological):
Measurement unit ID, identifying the module that performed the test.
ModuleType^SubModule^AnalyticalUnitID^InstrumentID^
Bottle^SBNo
OBX-18.1 String R Module One of the following:
Type c502, Results from the specified measuring module,
c701, or manual results entered on behalf of that
e602, module.
ISE, or
c702
DM Results calculated on the data manager, and
for manual results entered on the data
manager, but cannot be attributed to a
module.
c8000 Results from the cobas® 8000 modular
analyzer series that cannot be mapped to an
actual measuring submodule, for example,
sample short.
OBX-18.2 Number R SubModu o 1 or 2, for result from a submodule.
le o 0 (zero) otherwise.
OBX-18.3 String R Analyti Identifier for the module, as sent to the host. This setting is
calUnit configurable in the cobas® 8000 data manager. Default:
ID Instrument#ModuleType#Position#SubModule
Example: MU1#c502#2#1
e For details, see Identifier of the analytical unit sent to
host on page B-30.
OBX-18.4 Number R Instrum Instrument number in data manager (A specific identifier
entID inside the data manager which identifies a module. This is a
number which has no relationship to the internal position
of the module in the machine.)
OBX-18.5 String O Bottle Used Reagent Set.
(R o Current
for o Standby
QC) o (or empty)
Reserved field for C-module (photometric) and E-module
(immunology) results, empty for ISE results.
OBX-18.6 Number R SBNo An integer showing the standby bottle number, if used. The
standby bottles are numbered sequentially, starting with 1.
Reserved field, only for C-module (photometric)
measurements, otherwise empty.
OBX-19 DateTime R Time at which result is available.

Roche Diagnostics
D-30 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Observation Result Segment - OBX (for calibration results)

Measurement of C-module photometric Calibration Results

For a Photometric Calibration Result from a C-module, the measurement result field
(OBX-5) contains the following components.
SD^STD

Subcomponent Description
SD Number Standard deviation value data.
STD Complex Absorbance values, (number types).
Format:
Absorbance&
FirstAbsorbance&
FirstInitialAbsorbance&
SecondAbsorbance&
SecondInitialAbosorbance&
Prozone Value

Complete example C-module The following is a complete example of a calibration from a C-module (photometry).
calibration result message MSH|^~\&|cobas 8000||host||20101019091421||OUL^R22^PCUPL|||2.5||||ER||
UNICODE UTF-8|
SPM||1^999999^901^1^20120131|||||||||C^P|
OBR|1|||8685|
OBX|1||8685||0^3&4&22851&2&22866&|||16|||F||||bmserv||75|c701^1^MU1#c7
01#1#1^6^Current|20101019091421|
SID||
SPM||2^153314^401^1^20120131|||||||||C^P|
OBR|2|||8685|
OBX|2||8685||0^-362&-361&24786&-362&24149&|||16|||F||||bmserv||75|c701
^1^MU1#c701#1#1^6^Current|20101019091421|
SID||

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-31
9 HL7 text content cobas® 8000 data manager
Observation Result Segment - OBX (for calibration results) cobas® 8000 instrument

Measurement of ISE Calibration Results

For an ISE Calibration Result, measurement result field (OBX-5) contains three
components.
CalType^DataAlarm^Data

Subcomponent Description
CalType String This states what kind of test has been done. Possible
values are:
o Type-A
o Type-B
DataAlarm Complex Data alarm.
e For details, see ISE data alarms on page D-32.
Data Complex Test calibration analytical data.
e For details, see ISE calibration analytical data on
page D-32.

ISE data alarms The data alarms from the ISE calibration contain the following subcomponents,
separated with an ampersand (&). Each component is a Number type.
o Internal standard solution electromotive force data alarm
o Low solution electromotive force data alarm
o High solution electromotive force data alarm
o Calibrator solution electromotive force data alarm
o Slope for display data alarm
o Internal standard solution concentration data alarm
o Calibrator solution concentration data alarm
o Carryover rate alarm
o Calculation slope value alarm
o Compensation value data alarm

ISE calibration analytical data The analytical data from the ISE calibration data contain the following
subcomponents, separated with an ampersand (&). Each component is a Number
type, with Maximum length 6.
o Internal standard solution electromotive force data
o Low solution electromotive force data
o High solution electromotive force data
o Calibrator solution electromotive force data
o Slope for display data
o Internal standard solution concentration data
o Calibrator solution concentration data
o Carryover rate
o Calculation slope value
o Compensation value data alarm

Complete example ISE The following is a complete example of a calibration from an ISE module.
calibration result message MSH|^~\&|cobas 8000||host||20100316105742||OUL^R22^ICUPL|270||2.5||||
ER||UNICODE UTF-8|
SPM|||||||||||C^I|
OBR|1|||989|
OBX|1||989||Type-A^0&0&0&0&0&0&0&0&0&0^-32.7&-34.7&-28.4&-30.2&50.4&
131.5&147.7&0.0&49.9&-4.7|||Valid|||F||||bmserv||37|MU1#ISE#1#1|
20100316105741|
SID||
SPM|||||||||||C^I|
OBR|2|||990|
Roche Diagnostics
D-32 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Observation Result Segment - OBX (for calibration results)

OBX|2||990||Type-A^0&0&0&0&0&0&0&0&0&0^-34.2&-45.5&-24.8&-34.5&56.3&
4.76&4.70&0.0&56.2&-0.17|||Valid|||F||||bmserv||38|MU1#ISE#1#1|
20100316105742|
SID||
SPM|||||||||||C^I|
OBR|3|||991|
OBX|3||991||Type-A^0&0&0&0&0&0&0&0&0&0^136.4&138.5&130.6&134.1&-44.9&
89.0&100.3&0.0&-45.1&0.7|||Valid|||F||||bmserv||39|MU1#ISE#1#1|
20100316105742|
SID||

Measurement of E-module immunological Calibration Results

For an Immunological Calibration Result from an E-module, the measurement result

field (OBX-5) field contains the following components.
CalResultStatus^MissingValue^MinSignal^MaxSignal^CalibratorFactor^
Deviation^Slope^MinAcceptDiff^SystemError^SignalVal1&SignalVal2^
TargetValue^Unit^CUTOff^BorderLineAreaUpperLimit^
BorderLineAreaLowerLimit

Subcomponent Description
CalResultStatus String Result Status:
o Valid
o Invalid
MissingValue String o true if violation
o false if no violation
MinSignal String o true if violation
o false if no violation
MaxSignal String o true if violation
o false if no violation
CalibratorFactor Number Decimal value
Deviation String o true if violation
o false if no violation
Slope String Decimal value (used for qualitative tests)
MinAcceptDiff String o true if violation
o false if no violation
SystemError String o true if violation
o false if no violation
SignalVal1&SignalVal2 Complex Signal value, in two decimal subcomponents:
SignalVal1&SignalVal2
TargetValue Complex Target Value (for quantitative tests). This can
be empty
Level1&Level2&Level3&Level4&Level5
Note that version 1.02 of the data manager
does not send data for this component.
Unit String Unit

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-33
9 HL7 text content cobas® 8000 data manager
Observation Result Segment - OBX (for calibration results) cobas® 8000 instrument

Subcomponent Description
CUTOff String CUT off (for qualitative tests). Note that the
data manager does not send data for this
component.
BorderLineAreaUpperLimit Number (Used for qualitative tests). Note that the data
manager does not send data for this
component.
BorderLineAreaLowerLimit Number (Used for qualitative tests). Note that the data
manager does not send data for this
component.

Complete example E-module The following is a complete example of a calibration from a E-module
calibration result message (immunology).
MSH|^~\&|cobas 8000||host||20111118175844||OUL^R22^ECUPL|14268||2.5|||
|ER||UNICODE UTF-8|
SPM||2^158941^1^None^20111119|||||||||C^E|
OBR|1|||1|
OBX|1||1||Valid^false^false^false^1.064^false^^false^false^38293.490&3
8596.120^^^^^|||LotCalibration|||F||||bmserv||26|e602^2^MU1#e602#2#2^1
0^Current|20111118175844|
SID|1^^^ASY^18^0|157328|5|
SPM||1^158941^1^None^20111119000000|||||||||C^E|
OBR|2|||1|
OBX|2||1||Valid^false^false^false^1.064^false^^false^false^839.413&797
.173^^^^^|||LotCalibration|||F||||bmserv||26|e602^2^MU1#e602#2#2^10^Cu
rrent|20111118175844|
SID|1^^^ASY^18^0|157328|5|

Calibration alarm flags

This section describes the calibration alarms send in field OBX-8.

ISE calibration alarm For ISE calibration results, the OBX-8 field contains the calibration status sent by the
instrument. Possible values are:
o Valid meaning the calibration was successful.
o Invalid meaning calibration failed.

C-module (photometric) For photometric calibration results, this field contains the calibration alarm. Zero (0)
calibration alarm indicates that there is no alarm.

E-module (immunological) For Elecsys calibration results, this field contains the CalibrationMethod. This is a
calibration alarm string with one of the following eight values.

NoCalibration
LotCalibration
ContainerCalibration
InheritedLotCalibration
InheritedItemCalibration
UserModifiedCalibration
UnmaskedCalibration
FailedCalibration

Roche Diagnostics
D-34 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Test Code Detail Segment - TCD

Test Code Detail Segment - TCD

The data manager uses the test code detail segment in result report message to give
dilution factors.
TCD|1|1
TCD|1|Inc|
TCD|1|50|

Field Value Host DM Description

TCD-1 Number - R Universal Service Identifier. (Testcode or Application Code, which identifies the test or
analyte tested for.)
TCD-2 String - R Auto-dilution factor. Permitted values are:
o For an ISE module, the dilution factor is always: 1
o For C-modules (photometry): Dec, Inc, 1
o For E-module (immunoassay): 1, 2, 5, 10, 20, 50, 100, 400

Substance Identifier Segment - SID

The data manager uses the substance identifier segment to identify the reagents used
in a test, when sending the host a result report message.
Patient upload from a C-module (photometric):
SID|8706^^784648^R1^2^0|231478|5|

Calibration result from an E-module (Immunology):

SID|1^^^ASY^14^0|156369|

For messages containing patient results from the ISE module, no SID segment is sent.

Field Value Host DM Description

SID-1 Complex - O/R Test code / Method Identifier. Takes the format:
Test^Type^Code^ReagentType^Position^Expiry
This field is empty for ISE calibration results.
SID-1.1 Number O/R Test Testcode (or Application Code). This is the code number the
host uses for identifying the test or analyte to test for.
SID-1.2 String O/R Type Type of the test, if available.
SID-1.3 Number O/R Code Reagent code. For calibration results from a C or E module,
this is empty.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-35
9 HL7 text content cobas® 8000 data manager
Comment Segment - NTE cobas® 8000 instrument

Field Value Host DM Description

SID-1.4 String O/R Reagent Reagent type. Empty for C module calibration results.
Type R1 Reagent 1 used for a patient or QC test on a C
module.
R2 Reagent 2 used for a patient or QC test on a C
module.
R3 Reagent 3 used for a patient or QC test on a C
module.
SPR Special reagent
ASY Assay, used on immunology (E) modules. An E-
module test will have exactly one ASY segment.
IS Inner standard (ISE - QC results)
DIL Diluent (ISE - QC results)
REF Reference (ISE - QC results)
SID-1.5 Number O/R Position Reagent Position on Disk
SID-1.6 Number O/R Expiry Expiration flag:
o 0 = expired
o 1 = not expired
SID-2 String - O Lot number of the reagent used. Not used for ISE-module calibration results.
SID-3 String - O Serial number of the reagent used. Not used for ISE-module calibration
results.

Reagents on a C module
Note that R1-R3 might not all be present on a C module (photometric).

Comment Segment - NTE

The data manager uses the comment segment in a result report message.
NTE|1|I|23^Sample Short|I|
NTE|2|L|This sample is haemolytic^DMROUTINE^20090402172605|G|

There will always be an instrument flag sent with the result report message. In the
case of a result with no alarm flag (zero), the segment will be as follows:
NTE|1|I|0|I|

This is “NTE-one-i-zero-i”.

Field Value Host DM Description

NTE-1 Number R Set ID
NTE-2 Character R Source of comment text. Fixed string value.
o I
Result flag, from the instrument or the data manager.
o L
The comment was added on the data manager.

Roche Diagnostics
D-36 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Query Parameter Segment - QPD (for a test selection inquiry)

Field Value Host DM Description

NTE-3 Complex O/R Comment. Value depends on value of NTE-4. This is optional if NTE-4 is G. (Result
comment)
e For details of this field, see Types of comment segment on page D-37.
NTE-4 String R Code for qualifying the comment segment type. Comments sent by data manager can
have the following types.
o I Result flag. This is an extension to the HL7 specification.
o G Result comment.

Types of comment segment

The content of the comment segment depends on the type of comment and where it
comes from.

User comments If the user enters a comment, the field NTE-4 has the value G.
Field NTE-3 has details of the comment.
Text^User^Date

Text String Comment text

User String User who entered the comment
Date String Creation date and time in datetime format

Instrument comments If the instrument sends the data manager an data flag (alarm or “error flag”), the data
manager passes this to the host in a comment segment. NTE-4 has the value I.
Field NTE-3 has details of the data flag.
flag^desc

flag Number Number showing the data alarm code of the data flag. If there is
no error, this value is zero: 0.
desc String Description of data flag. Blank if the flag is zero.

e For details of possible error flags, see Chapter 11 Data Alarms

Query Parameter Segment - QPD (for a test selection inquiry)

The data manager uses the query parameter segment in an inquiry for a test selection,
to give details of the sample.
QPD|TSREQ|12896|000137||50042|2||||S1|SC|R1|R|

If the system is not using barcodes (with aliquots from a MODULAR PRE-
ANALYTICS), and is requesting a sample ID from the host:
QPD|TSREQ|12897|**********************||50045|1||||S1|SC|R1|R|

If sample are identified by sequence number:

QPD|TSREQ|563067|^1031||50203|3||||S1|SC|R1|R|

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-37
9 HL7 text content cobas® 8000 data manager
Query Parameter Segment - QPD (for a test selection inquiry) cobas® 8000 instrument

Field Comp. Value Host DM Description

QPD-1 TSREQ R Message name, fixed string TSREQ.
QPD-2 String O Query tag to identify the query.
QPD-3 String / R If using barcodes (default), this is a string field containing the Sample ID.
Complex If samples are identified by sequence number, this is a complex field:
QPD-3.1 String R/O Must be empty if samples are identified by sequence number, and a sequence
number is sent in QPD-3.2.
QPD-3.2 String O/R Sequence number. (Max. value = 60,000.) Only used if samples are identified
by sequence number, and the sample has no barcode.
e For details of sequence numbers, see Chapter 14 Identifying patient
samples by sequence number.
QPD-4 Field contains no data.
QPD-5 String R Rack ID, as visible on Control Unit
QPD-6 String R Position on rack
QPD-7 Field contains no data.
QPD-8 Field contains no data.
QPD-9 Field contains no data.
QPD-10 String R Rack type as assigned to a specific sample type on the cobas® 8000 modular
analyzer series. Depending on the version and modules installed, not all of
these types may be available on any particular system.
S1 Serum / Plasma
S2 Urine
S3 Cerebrospinal Fluid
S4 Supernatant
S5 Other fluids
S6 Whole blood
S7 Oral fluids (Saliva)
S8 Reserved for future use
S9 Reserved for future use
SA Reserved for future use
S0 No specimen assigned (only used for messages from data
manager).
QPD-11 String R Sample container type. A two-character code.
o MC
Micro cup
o SC (or empty)
Standard cup
QPD-12 String R Kind. A two-character code.
o R1 Query for 1st measurement (Initial run)
o R2 Rerun query
QPD-13 String R Code indicating the sample priority.
o S STAT sample
o R Routine sample

Roche Diagnostics
D-38 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Query Parameter Segment - QPD (for a Result Query)

Query Parameter Segment - QPD (for a Result Query)

The host uses the query parameter segment (QPD) in a result query to inquire for the
measurement results for a given sample.
QPD|RSREQ||12896
QPD|RSREQ||12896|
QPD|RSREQ||12896|F
QPD|RSREQ||12896||||||S1

If identifying samples by sequence number:

QPD|RSREQ||^1031||

Field Comp. Value Host DM Description

QPD-1 RSREQ R Message name, fixed string RSREQ.
QPD-2 Field contains no data.
QPD-3 String / R In the default mode using barcodes, this is a string field containing the
Complex Sample ID.
If samples are identified by sequence number, this is a complex field:
QPD-3.1 String R/O Must be empty if samples are identified by sequence number and a sequence
number is sent in QPD-3.2.
QPD-3.2 String O/R Sequence number. (Max. value = 60,000.)Only used if samples are identified
by sequence number, and the sample has no barcode.
e For details of sequence numbers, see Chapter 14 Identifying patient
samples by sequence number.
QPD-4 String O Selection mode
o (empty)
All results
o F
Final results
QPD-5 Field contains no data.
QPD-6 Field contains no data.
QPD-7 Field contains no data.
QPD-8 Field contains no data.
QPD-9 Field contains no data.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-39
9 HL7 text content cobas® 8000 data manager
Query Parameter Segment - QPD (for an Order Query) cobas® 8000 instrument

Field Comp. Value Host DM Description

QPD-10 String O Rack type as assigned to a specific sample type on the cobas® 8000 modular
analyzer series. Depending on the version and modules installed, not all of
these types may be available on any particular system.
S1 Serum / Plasma
S2 Urine
S3 Cerebrospinal Fluid
S4 Supernatant
S5 Other fluids
S6 Whole blood
S7 Oral fluids (Saliva)
S8 Reserved for future use
S9 Reserved for future use
SA Reserved for future use
S0 No specimen assigned (only used for messages from data
manager).
Subsequent fields contain no data.

Query Parameter Segment - QPD (for an Order Query)

The host uses the query parameter segment (QPD) in an order query to inquire for all
test selections with and without results for a given sample.
QPD|TSREQ||12896|O
QPD|TSREQ||12896|||||||S1

If identifying samples by sequence number:

QPD|TSREQ||^1031|||||||S1|

Field Value Host DM Description

QPD-1 TSREQ R Message name, fixed string TSREQ.
QPD-2 Field contains no data.
QPD-3 String / R In the default mode using barcodes, this is a string field containing the
Complex Sample ID.
If samples are identified by sequence number, this is a complex field:
QPD-3.1 String R/O Empty if samples are identified by sequence number and a sequence number
is sent in QPD-3.2.
QPD-3.2 String O/R Sequence number. (Max. value = 60,000.) Only used if samples are identified
by sequence number, and the sample has no barcode.
e For details of sequence numbers, see Chapter 14 Identifying patient
samples by sequence number.
QPD-4 String O Selection mode
o (empty)
All requested tests
o O
(Capital O) Open. (Only test selections with no results yet)
QPD-5 Field contains no data.

Roche Diagnostics
D-40 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 9 HL7 text content
®
cobas 8000 instrument Response Control Parameter Segment - RCP

Field Value Host DM Description

QPD-6 Field contains no data.
QPD-7 Field contains no data.
QPD-8 Field contains no data.
QPD-9 Field contains no data.
QPD-10 String O Rack type as assigned to a specific sample type on the cobas® 8000 modular
analyzer series. Depending on the version and modules installed, not all of
these types may be available on any particular system.
S1 Serum / Plasma
S2 Urine
S3 Cerebrospinal Fluid
S4 Supernatant
S5 Other fluids
S6 Whole blood
S7 Oral fluids (Saliva)
S8 Reserved for future use
S9 Reserved for future use
SA Reserved for future use
S0 No specimen assigned (only used for messages from data
manager).
Subsequent fields contain no data.

Response Control Parameter Segment - RCP

The data manager and the host use the response control parameter segment (RCP)
with a query message (test selection inquiry, result query, order query) to specify the
priority of the message.
RCP|I|1|R|

Field Value Host DM Description

RCP-1 I R R Query priority (immediate), fixed string I.
RCP-2 1 O R Query limited request, fixed value 1.
RCP-3 R O R Response modality, fixed character value R.

Equipment Detail Segment - EQU

The host used the Equipment Detail Segment to instruct the data manager to apply
the instructions in the following ECD segments, in a masking message.
EQU|1|20090402173655|

Field Value Host DM Description

EQU-1 1 R Identifier for the equipment. This is the identifier from an institution's master list of
equipment. Fixed value “1”.
EQU-2 Datetime R The date and time that the masking or unmasking request is sent.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-41
9 HL7 text content cobas® 8000 data manager
Equipment Command Segment - ECD cobas® 8000 instrument

Equipment Command Segment - ECD

The host uses the Equipment Command Segment to instruct the data manager what
masking to perform.
ECD||UC|||989^^MU1#c701#1#1^ALL|
ECD||LK|||989^P^MU1#e602#1#1^ALL|
ECD||LK|||989^T^MU1#ISE#1#1^ALL|

Field Value Host DM Description

ECD-1 This field contains no data.
ECD-2 String R The instruction specifying masking or unmasking.
o LK (for “lock”) to implement masking.
o UC (for “unlock”), to unmask.
ECD-3 This field contains no data.
ECD-4 This field contains no data.
ECD-5 Complex R This field specifies the parameters of the command.
TestCode^MaskTpe^Unit_ID^ALL
ECD-5.1 Number R - TestCode The code identifying the analyte or test. Required field:
masking only possible by test.
ECD-5.2 Character O - MaskType A character flag instructing data manager which kind of
masking to perform:
o P
Mask only patient results. The data manager uploads
quality control and calibration results to the host.
o T
Mask all results, including patient, quality control and
calibration results.
o This field is empty if ECD-2 is UC (unmask).
ECD-5.3 String R - Unit_ID This is the user-editable identifier for the instrument and
module.
e For details, see Identifier of the analytical unit sent to host
on page B-30.
ECD-5.4 ALL R - Hard-coded to ALL.

Roche Diagnostics
D-42 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 10 HL7 Acknowledgement handling
®
cobas 8000 instrument Table of contents

HL7 Acknowledgement handling

This chapter explains how cobas® 8000 data manager implements HL-7
acknowledgment messages.

In this chapter Chapter 10

HL7 acknowledgement messages ............................................................................... D-45
Messages from the data manager ................................................................................ D-45
Inquiry for test selections ....................................................................................... D-46
If the host cannot find a test selection ........................................................... D-46
Result report patient ............................................................................................... D-46
Result report quality control ................................................................................. D-47
Result report calibration data ................................................................................ D-47
Test selection upload from data manager to host .............................................. D-48
If the data manager cannot find a test selection ........................................... D-48
Acknowledgement .................................................................................................. D-48
Sending messages from host to the data manager .................................................... D-49
Result query ............................................................................................................. D-49
If the data manager cannot find a test selection with that sample ID ....... D-49
Order query ............................................................................................................. D-49
If the data manager cannot find a test selection ........................................... D-49
Masking .................................................................................................................... D-50
Test Selection download ........................................................................................ D-50
Acknowledgement .................................................................................................. D-50

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-43
10 HL7 Acknowledgement handling cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
D-44 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 10 HL7 Acknowledgement handling
®
cobas 8000 instrument HL7 acknowledgement messages

HL7 acknowledgement messages

This chapter explains how to handle HL7 acknowledgement messages when sending
and receiving messages to cobas® 8000 data manager.

Messages from the data manager

HL7 messages send a flag instructing the receiver under what conditions to send an
acknowledgement. You can define which flag the data manager sends. This setting
applies to the flag sent in the following messages:
o Result upload messages (patient, QC, or calibration) and
o Test selection uploads.
This is configured in c8000 DM Service > Service-related configuration > Interface
options.
e For details of how to configure the application acknowledge level of the data manager, see
Configuring HL7 Acknowledgement handling on page B-28.

The code in MSH-16 instructs the receiver whether to send an application

acknowledgement reply. Four levels of acknowledgement are supported, as described
below.

MSH-16 Meaning Required host response Timeout (for patient and QC results)
Code
AL Always Send an acknowledgement to every message. Defaults to 60 seconds. The data manager expects
Accept (AA) or Error (AE). Data is marked in
Upload Status as "Pending" in data manager until
acknowledgement received or timeout.
SU Success If message processed, send Accept (AA). Defaults to 60 seconds. The data manager expects
If message cannot be processed, send no Accept (AA). Data is marked in Upload Status as
acknowledgement. "Pending" in data manager until acknowledgement
received or timeout.
ER Error If message processed, send no acknowledgement. The data manager assumes success, unless it receives
If message cannot be processed, send Error (AE). an Error (AE) or Reject (AR) at any time before the
the uploaded message is deleted.
NE Never Never send an acknowledgement. The data manager expects no response.

For acknowledgement message, the level of application acknowledgement is set to

Never (NE).
For other messages from the data manager (inquiry for test selections or test selection
upload), the level of application acknowledgement is set to Error (ER).
If the data manager cannot send a result report message because of a low-level error,
such as a disconnected cable, the results are marked in the column Host Upload
Status as “Failed”.
The data manager only displays the outcome of the most recent attempt to send
results.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-45
10 HL7 Acknowledgement handling cobas® 8000 data manager
Messages from the data manager cobas® 8000 instrument

Inquiry for test selections

The data manager always sends an Error (ER) code with an inquiry for a test
selections.

The data manager sends in MSH-16: The host returns in MSA-1

AA (Accept) AE (Error) AR (Reject) no response
Always (AL) Not sent
Success (SU) Not sent
Error (ER) ER always sent. The data manager currently does not respond to any value returned.
Never (NE) Not sent

If the host cannot find a test selection

If the host cannot find a test selection or if the sample ID is unknown, it should send
a test selection download message with no tests ordered.

Result report patient

The data manager can send AL/SU/ER/NE in a result report.

The data manager sends in MSH-16: The host returns in MSA-1

AA (Accept) AE (Error) AR (Reject) no response
Always (AL) The data manager The data manager The data manager After timeout, the
marks the results in marks the results in marks the results in data manager marks
Upload Status as Upload Status as Upload Status as the results in Upload
“Sent”. “Failed”. “Failed”. Status as “Failed”.
Success (SU) The data manager No allowed No allowed After timeout, the
marks the results in data manager marks
Upload Status as the results in Upload
“Sent”. Status as “Failed”.
Error (ER) No allowed The data manager The data manager The data manager
marks the results in marks the results in marks the results in
Upload Status as Upload Status as Upload Status as
“Failed”. “Failed”. “Sent”.
Never (NE) No allowed No allowed No allowed The data manager
marks the results in
Upload Status as
“Sent”.

If the host sends an Error (AE) or Reject (AR) response, or the message times out:
o the data manager reports an error in Service > Communication messages.
o the data manager writes an error to logs in System Configuration > Log files.
o the data manager writes an error to logs in Routine > System alarms.
o the data manager marks the results in “Upload status” as “Failed”.

Roche Diagnostics
D-46 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 10 HL7 Acknowledgement handling
®
cobas 8000 instrument Messages from the data manager

Result report quality control

The data manager can send AL/SU/ER/NE in a Quality Control result report.

The data manager sends in MSH-16: The host returns in MSA-1

AA (Accept) AE (Error) AR (Reject) no response
Always (AL) The data manager The data manager The data manager After timeout, the
marks the results in marks the results in marks the results in data manager marks
Upload Status as Upload Status as Upload Status as the results in Upload
“Sent”. “Failed”. “Failed”. Status as “Failed”.
Success (SU) The data manager No allowed No allowed After timeout, the
marks the results in data manager marks
Upload Status as the results in Upload
“Sent”. Status as “Failed”.
Error (ER) No allowed The data manager The data manager The data manager
marks the results in marks the results in marks the results in
Upload Status as Upload Status as Upload Status as
“Failed”. “Failed”. “Sent”.
Never (NE) No allowed No allowed No allowed The data manager
marks the results in
Upload Status as
“Sent”.

If the host sends an Error (AE) or Reject (AR) response, or the message times out:
o the data manager reports an error in Service > Communication messages.
o the data manager writes an error to logs in System Configuration > Log files.
o the data manager writes an error to logs in Routine > System alarms.
o the data manager marks the results in “Upload status” as “Failed”.

Result report calibration data

The data manager can send AL/SU/ER/NE in a result report.

The data manager sends in MSH-16: The host returns in MSA-1

AA (Accept) AE (Error) AR (Reject) no response
Always (AL) Message considered Error logged in data Error logged in data After timeout, error
sent successfully. manager. manager. logged in data
manager.
Success (SU) Message considered No allowed No allowed After timeout, error
sent successfully. logged in data
manager.
Error (ER) No allowed Error logged in data Error logged in data Message considered
manager. manager. sent successfully.
Never (NE) No allowed No allowed No allowed Message considered
sent successfully.

If the host sends an Error (AE) or Reject (AR) response, or the message times out:
o the data manager reports an error in Service > Communication messages.
o the data manager writes an error to logs in System Configuration > Log files.
o the data manager writes an error to logs in Routine > System alarms.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-47
10 HL7 Acknowledgement handling cobas® 8000 data manager
Messages from the data manager cobas® 8000 instrument

Test selection upload from data manager to host

The data manager can send AL/SU/ER/NE in a test selection upload.

The data manager sends in MSH-16: The host returns in MSA-1

AA (Accept) AE (Error) AR (Reject) no response
Always (AL) Message considered Error logged in data Error logged in data After timeout, error
sent successfully. manager. manager. logged in data
manager.
Success (SU) Message considered No allowed No allowed After timeout, error
sent successfully. logged in data
manager.
Error (ER) No allowed Error logged in data Error logged in data Message considered
manager. manager. sent successfully.
Never (NE) No allowed No allowed No allowed Message considered
sent successfully.

If the host sends an Error (AE) or Reject (AR) response, or the message times out:
o the data manager reports an error in cobas® 8000 data manager Service >
Communication messages.
o the data manager writes an error to logs in System Configuration > Log Files.
o the data manager writes an error to logs in Routine > System alarms.

If the data manager cannot find a test selection

If the data manager cannot find the requested test selection, it returns a test selection
upload message with a sample ID and sample type, but no orders, containing only the
MSH and SPM segments.

Acknowledgement

The data manager always sends an NE code in an acknowledgement message.

Roche Diagnostics
D-48 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 10 HL7 Acknowledgement handling
®
cobas 8000 instrument Sending messages from host to the data manager

Sending messages from host to the data manager

The data manager responds, as detailed in this section, according to the setting of
MSH-16 in the host messages. The data manager sends either an Accept (AA) or an
Error (AE) response, but does not currently the Reject (AR) response.

Result query

The data manager sends no acknowledgment message or segment in response to a

result query. If the query is successful, the data manager responds with a result
upload. (OUL^R22^BATCH).
For result queries, the data manager only supports the acknowledgement code NE.

If the data manager cannot find a test selection with that sample ID
If the data manager cannot find a test selection that has the sample ID given in the
host’s query, it makes no reply.

Order query

The data manager sends no acknowledgment message or segment in response to an

order query. If the message is successful, the data manager sends a test selection
upload (OML^O33).
For an order query, the data manager only supports the acknowledgement code NE.

If the data manager cannot find a test selection

If the data manager cannot find a test selection with the requested sample ID, it
returns a test selection upload message containing the sample ID and sample type as
requested, but containing no orders, using only the MSH and SPM segments.
e For an example, see No tests found on page E-87.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) D-49
10 HL7 Acknowledgement handling cobas® 8000 data manager
Sending messages from host to the data manager cobas® 8000 instrument

Masking

In reply to a masking or unmasking request, the data manager sends an

acknowledgement message if requested.

The host sends in MSH-16: The data manager returns in MSA-1 in an ACK message
AA (Accept) AE (Error) AR (Reject) no response
Always (AL) Indicates success. Indicates an error, Not sent Not sent
specified in the MSA
segment.
Success (SU) Indicates success. Not sent Not sent Indicates unspecified
error.
Error (ER) Not sent Indicates an error, Not sent Indicates success.
specified in the MSA
segment.
Never (NE) Not sent Not sent Not sent Supported.

Test Selection download

In reply to a test selection download, the data manager sends an acknowledgement

message if requested.

The host sends in MSH-16: . The data manager returns in MSA-1

AA (Accept) AE (Error) AR (Reject) no response
Always (AL) Indicates success. Indicates an error, Not sent Not sent
specified in the MSA
segment.
Success (SU) Indicates success. Not sent Not sent Indicates unspecified
error.
Error (ER) Not sent Indicates an error, Not sent Indicates success.
specified in the MSA
segment.
Never (NE) Not sent Not sent Not sent Supported.

Acknowledgement

The data manager never replies to an acknowledgement message.

Roche Diagnostics
D-50 Host Interface Manual · Version 1.02.05 (revision 1)
 Appendices E

11 Data Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3

12 Instrument alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-21
13 Using MODULAR PRE-ANALYTICS . . . . . . . . . . . . . . . . . . . E-39
14 Identifying patient samples by sequence number . . . . . . . . . . E-45
15 Communication examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-53
16 Preparing the host communication . . . . . . . . . . . . . . . . . . . . . . E-89
17 Text encoding tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-109
cobas® 8000 data manager 11 Data Alarms
®
cobas 8000 instrument Table of contents

Data Alarms
Data alarms and error codes

This chapter gives a reference to the data alarms that cobas® 8000 data manager and
the Control Unit can generate.

In this chapter Chapter 11

The meaning of the data alarms ..................................................................................... E-5
Alarms for Routine or STAT samples ......................................................................... E-12
Alarms for Control and Calibration samples ............................................................. E-16

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-3
11 Data Alarms cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
E-4 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 11 Data Alarms
®
cobas 8000 instrument The meaning of the data alarms

The meaning of the data alarms

This table presents a brief description, the priority and output character of each data
alarm.

No. Name Meaning Priority Output character

HOST UI
PRN SCR
0 (No Alarm)
1 ADC abnormal o Photometry: The ADC value of the primary or secondary 1 1 ADC.E 
wavelength is zero (in monochromatic measurement, the
primary wavelength only).
o ISE: The system cannot read the ADC data properly.
o Immunoassay: The ADC data is abnormal.
2 ABS Cell blank The cell blank value used for measurement exceeds or less than 1 2 >Cuvet 
abnormal the reference value by more than 0.1Abs.
3 Sample short Before sample aspiration, the liquid level cannot be detected in 2 3 Samp.S 
the sample container.
Immunoassay:
o Sample short was detected.
o No sample was placed.
4 Reagent short The liquid level cannot be detected in the reagent container. 2 4 Reag.S 
o c701/e601: Alarm is generated when reagent pipetted by
LLD check
o c501: Alarm is NOT generated because reagent probe does
not have LLD.
5 ABS over The absorbance value to be used for calculation after cell blank 3 5 >Abs 
correction exceeded 3.3. (Check is done for each wavelength)
6 Prozone Error The prozone check value exceeds the specified limit value. 3 6 >Proz 
(Antigen readdition method)
7 Reaction limit over In a rate assay, the main wavelength absorbance in measure 3 7 >React 
points exceeds the specified reaction limit value (the value after
the automatic correction). Depending on the number of
measure points within the limit, there are thee types:
1. All measure points exceed the reaction limit.
8 Reaction limit over 2. The second and subsequent points exceed the reaction limit. 3 8 >React 
(2nd ..)
9 Reaction limit over 3. The third and subsequent points exceed the reaction limit. 3 9 >React 
(3rd ..)
10 Linearity abnormal 1 In rate assay, the reaction linearity exceeds the specified limit 3 10 >Lin 
value. There are two types of checks depending on the number
of measure points:
1. When there are 9 or more measure points for c701, 17 or
more for c502.
11 Linearity abnormal 2 2. When there are 4-8 measure points for c701, 6 to 16 for c502. 3 11 >Lin 
12 S1ABS abnormal During calibration, expected absorbance is outside the S1 Abs 4 12 S1A.E 
Limit.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-5
11 Data Alarms cobas® 8000 data manager
The meaning of the data alarms cobas® 8000 instrument

No. Name Meaning Priority Output character

HOST UI
PRN SCR
13 DUPLICATE error o Photometry: The difference between the first and second 4 13 Dup.E 
measurement (absorbance) of a calibrator is outside the
specified range.
o Immunoassay: The difference between the first and second
measured signals of the calibrator is out of the range
specified in the assay.
14 STANDARD error During photometric calibration, any one of the following 4 14 Std.E 
alarms was encountered:
o ADC abnormal
o cell blank abnormal
o sample short
o reagent short
o absorbance over
o reaction limit over
o linearity abnormal
o prozone error
o duplicate error
o calculation not possible
o standard 1 absorbance abnormal.
Otherwise one of the following errors occurred:
o During calibration, calculation was disabled.
o During nonlinear calibration, an extreme value appeared.
15 SENSITIVITY error Sensitivity is checked for linear (2 to 6 points) or nonlinear 4 15 Sens.E 
calibration. The alarm is issued if the following is smaller than
the sensitivity limit:
Mean Abs of Std (N)* - Mean Abs of Std (1)
Mean Conc of Std (N) - Mean Conc of Std (1)
*N: = Std 2 for 2 Point = span calibrator for multipoint
calibration
16 CALIB error The current calibrator concentration value or slope value differs 5 16 Cal.E 
from the previous one by more than the specified Compensated
Limit.
|(previous value - current
value)/{(previous value + current
value)/2}|*100 < Compensated limit
17 SD limit error During nonlinear or multipoint linear calibration, the SD value 5 17 SD.E 
was larger than the specified SD limit.
18 ISE Noise error The fluctuation in electromotive force exceeds the following 4 18 ISE.N 
value:
o Na+: 0.7 mV
o K+:1.0 mV
o Cl-: 0.8 mV
19 ISE Voltage Level During measurement of internal reference, the mean of the 4 19 ISE.E 
error EMF values was not within the following ranges (Internal
standard solution):
o Na+: -90.0 to -10 mV
o K+: -90.0 to -10 mV
o Cl-: 80.0 to 160 mV

Roche Diagnostics
E-6 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 11 Data Alarms
®
cobas 8000 instrument The meaning of the data alarms

No. Name Meaning Priority Output character

HOST UI
PRN SCR
20 Slope abnormal The slope value is less than 45.0 mV for Na+ or K+ electrodes, 3 20 Slop.E 
or greater than -35 mV for the Cl- electrode.
21 Preparation The slope value is within the following range: 3 21 Prep.E 
abnormal o Na+ or K+ electrodes: 45.0 to 49.9 mV
o Cl- electrodes: -39.9 to -35.0 mV
22 IS concentration The concentration of the Internal Standard solution (ISE IS) 3 22 IStd.E 
abnormal was not within the following ranges*
o Na+: 120.0-160.0 mmol/L,
o K+: 3.0-7.0 mmol/L
o Cl-: 80.0-120.0 mmol/L
23 ISE Sample range The sample concentration was outside the following range: 5 23 < >Test 
over o Na+: 10-250 mmol/L,
o K+: 1-100 mmol/L,
o Cl-: 10-250 mmol/L
24 Data error in comp. o In test-to-test compensation calculation, a data alarm for 5 24 CmpT.E 
Test the compensation test data is indicated.
o Calculation not possible, test-to-test compensation
disabled, overflow, random error, systematic error, QC
error and outside of expected value.
25 Unable to calculate o During test-to-test compensation calculation, the 5 25 CmpT.? 
comp. Test denominator became zero.
o The test used for test-to-test compensation has not been
measured yet.
o Any test used for test-to-test compensation has data alarm
not possible (Calc.?) or test-to-test compensation error
(CmpT.E).
o Any test used in the compensation formula has a data alarm
that leaves the result blank.
26 Technical Limit over The concentration exceeds the specified technical limit range. "4 26 >Test 
(upper) Immunoassay: The concentration exceeds the measuring range.
Measurement data is displayed as Upper Limit Value.
27 Technical Limit over Photometry/ISE: The concentration is below the specified "4 27 <Test 
(lower) technical limit range.
Immunoassay: The concentration is below the measuring range.
Measurement data is displayed as Lower Limit Value.
28 Reserved for former alarm (Random error in real-time QC) -
29 Reserved for former alarm (Systematic error 1 in real-time QC) -
30 Reserved for former alarm (Systematic error 2 in real-time QC) -
31 Reserved for former alarm (Systematic error 3 in real-time QC) -
32 Reserved for former alarm (Systematic error 4 in real-time QC) -
33 Reserved for former alarm (Systematic error 5 in real-time QC) -
34 Reserved for former alarm (Systematic error 6 in real-time QC) -
35 Reserved for former alarm (QC error 1) -
36 Reserved for former alarm (QC error 2) -
37 Calculation test error A data alarm has occurred for the test needed in the calculation. 6 37 ClcT.E 

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-7
11 Data Alarms cobas® 8000 data manager
The meaning of the data alarms cobas® 8000 instrument

No. Name Meaning Priority Output character

HOST UI
PRN SCR
38 Overflow Display is not possible because the output figure exceeds the 6 38 Over.E 
defined number of digits.
39 Calculation not o The denominator becomes zero in calculation. 2 39 Calc.? 
possible o An overflow occurred in logarithmic or exponential
calculation.
o Result was left blank.
40 Reserved for former alarm (Outside of expected value (upper)) -
41 Reserved for former alarm (Outside of expected value (lower)) -
42 Edited test The data has been edited. 0 42 Edited 
Effective when "Edited Data Check" is ON.
43 Calibration result No calibration data or previous calibration data used (The last 7 43 Cal.E 
abnormal (Sample calibration failed due to an Std, or Sens alarm). This alarm is
Flag) attached to routine/rerun/STAT/control samples.
44 Repeat limit over The quantitative result exceeds the upper limit of the specified 7 44 >Rept 
(upper) repeat limit range.
o Effective when "Repeat Limit Check" is ON.
o Auto rerun ON/OFF is depending on the setting.
45 Repeat limit over The quantitative result falls below the lower limit of the 7 45 <Rept 
(lower) specified repeat limit range.
o Effective when "Repeat Limit Check" is ON.
o Auto rerun ON/OFF is depending on the setting.
46 ABS maximum over The absorbance of a sample is found equal or greater than the 3 46 Samp.? 
(nonLin curve) theoretical maximum absorbance (for infinite analyte
concentration).
47 -
48 -
49 -
50 -
51 Response(ISE) "The A Factor is outside the following limits: 3 51 Rsp1.E 
abnormal 1 o Na+: A > 0.154
o K+: A > 0.107
o Cl-: A > 0.330
52 Response(ISE) The A Factor is outside the following limits: 3 52 Rsp2.E 
abnormal 2 o Na+: A > 0.232
o K+: A > 0.160
o Cl-: A > 0.490
53 Conditioning(ISE) The slope value is 68.1 mV or greater for Na+ or K+ electrodes, 3 53 Cond.E 
abnormal or it is -68.1 mV or less for the Cl- electrode.
54 -
55 ISE range over 6 55 >ISE 
56 Kinetic unstable The prozone check value exceeds the specified limit value. 3 56 >Kin 
(Prozone error 2) (reaction rate method)
57 Reserved for former alarm (Serum index 1 interference) -
58 Reserved for former alarm (Serum index multiple interference) -
59 Stop mixing 2 59 MIXSTP 
60 Mixing current low 2 60 MIXLOW 
Roche Diagnostics
E-8 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 11 Data Alarms
®
cobas 8000 instrument The meaning of the data alarms

No. Name Meaning Priority Output character

HOST UI
PRN SCR
61 -
62 System reagent short Shortage in ProCell/CleanCell is detected. 2 62 SysR.S 
63 AB level range over No data alarm could be attached because the detection channel - 63 >AB 
(Assay Buffer) run is masked.
start
64 AB level check error No data alarm could be attached because the detection channel - 64 AB.E 
is masked.
65 Current range over No data alarm could be attached because the detection channel - 65 >Curr 
(run start) is masked.
66 Current range check No data alarm could be attached because the detection channel - 66 Curr.E 
error is masked.
67 Sample hovering The sample probe hovers over the sample. 2 67 Samp.H 
68 Sample air bubble Air bubble is detected in the sample syringe flow path when the 2 68 Samp.B 
sample is aspirated.
69 Reagent hovering The reagent probe hovers over the reaction disk (over reagent / 2 69 Reag.H 
dilution / pretreatment).
70 Reagent film The reagent probe detects a film on the reagent (reagent / 2 70 Reag.F 
detection dilution / pretreatment / ProCell / CleanCell).
71 Potential carry over The signal level of this sample is low (a carryover may have 3 71 CarOvr 
occurred).
72 Sample clot The specified volume of sample is not aspirated: Clogging was 2 72 Samp.C 
detected in the sample probe.
73 Carry over detergent Shortage of detergent for reagent carryover evasion is detected. 2 73 Det.S 
short
74 Reagent disk Reagent disk temperature is out of range 8 74 Reag.T 
temperature
75 Incubator Incubator temperature is out of range. 8 75 Inc.T 
temperature
76 System reagent ProCell/CleanCell temperature is out of range. 8 76 SysR.T 
temperature
77 Cell temperature Measuring cell temperature is out of range. 8 77 Cell.T 
78 Missing value One or more of the calibration results is invalid. 4 ------
79 System errors An error occurs on the system during measurement. 4 (79) Sys.E 
80 Monotony of curve The working curve is not monotonically increasing or 4 (80) Mono.E 
monotonically decreasing.
81 Minimum signal One or two of the calibrator signal values is lower than the 4 (81) <Sig 
specified lower limit value.
82 Maximum signal One or two of the calibrator signal values is higher than the 4 (82) >Sig 
specified lower limit value.
83 Sample carry over for After pipetting at C module, appended test (Reflex) is required 5 (83) Samp.O 
modules sample carry over wash.
84 Minimum/Maximum If one or more effective signal values falls out of the allowable 4 (84) Sig.E 
signal minimum/maximum signal range
85 Minimum acceptable The difference of the signals between each level of calibrators is 4 (85) Diff.E 
difference below the permissible value.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-9
11 Data Alarms cobas® 8000 data manager
The meaning of the data alarms cobas® 8000 instrument

No. Name Meaning Priority Output character

HOST UI
PRN SCR
86 Sample LLD The sample probe does not start LLD or LLD is not completed 2 86 SLLD.E 
abnormal (because of dirt on the tip etc.)
87 Sample LLD noise The sample probe did not detects the liquid surface properly 2 87 SLLD.N 
because of air bubbles on the sample or static electricity.
88 -
89 -
90 -
91 -
92 -
93 Washing buffer PreClean temperature is out of range. 8 93 WB.T 
temperature
94 Washing buffer short The remaining volume for PreClean is 0, or liquid short signal 2 94 WB.S 
is detected.
95 Clot pressure sensor In checking the pressure sensor, underflow data is detected. 2 95 Clot.E 
ADC (underflow)
96 Clot pressure sensor In checking the pressure sensor, overflow data is detected. 2 96 Clot.E 
ADC (overflow)
97 Clot pressure The clot pressure value is abnormal. 2 97 Clot.E 
abnormal
98 Sample pipettor air Air bubble is detected in the sample syringe flowpath when the 2 98 Samp.B 
bubble sample is aspirated.
99 Current range over The measuring cell current is out of range in the determination 2 99 >Curr 
(operation) cucle during operation.
100 Low level signal The effective signal of test is lower than the specified lower limit 2 100 <SigL 
value.
101 Reagent Expired Date The alarm indicates that an expired reagent was used; the test 9 101 ReagEx 
result is not guaranteed.
102 QC error There is an error related to QC. 7 102 QCErr 
103 Serum index The lipaemia value exceeds the specified limit value. 5 103 >I.L 
interference lipaemia o Flag is attached to the data which is assigned Serum Index
check in the Utility -Application -Range" screen.
104 Serum index The hemolysis value exceeds the specified limit value. 5 104 >I.H 
interference o Flag is attached to the data which is assigned Serum Index
hemolysis check in the Utility -Application -Range" screen.
105 Serum index The icteric value exceeds the specified limit value. 5 105 >I.I 
interference icteric o Flag is attached to the data which is assigned Serum Index
check in the Utility -Application -Range" screen.
106 Serum index Both of the lipaemia value and hemolysis value exceed the 5 106 >I.LH 
interference lipaemia specified limit value.
/ hemolysis o Flag is attached to the data which is assigned Serum Index
check in the Utility -Application -Range" screen.
107 Serum index specific Both of the lipaemia value and icteric value exceed the specified 5 107 >I.LI 
interference lipaemia limit value.
/ icteric o Flag is attached to the data which is assigned Serum Index
check in the Utility -Application -Range" screen.

Roche Diagnostics
E-10 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 11 Data Alarms
®
cobas 8000 instrument The meaning of the data alarms

No. Name Meaning Priority Output character

HOST UI
PRN SCR
108 Serum index Both of the hemolysis value and icteric value exceed the 5 108 >I.HI 
interference specified limit value.
hemolysis / icteric o Flag is attached to the data which is assigned Serum Index
check in the Utility -Application -Range" screen.
109 Serum index All of lipaemia, hemolysis and icteric values exceed the 5 109 >I.LHI 
interference lipaemia specified limit value.
/ hemolysis / icteric o Flag is attached to the data which is assigned Serum Index
check in the Utility -Application -Range" screen.
110
111 On board stability On-board stability limit was exceeded on Reagent Manager 8 111 OBS.RM 
limit over on Reagent o This data alarm is attached to results with the reagents
Manager which exceed on board stability limit 30 minutes or more.
112 On board stability On board stability limit was exceeded on Reagent Rotor 8 112 OBS.RR 
limit over on Reagent
Rotor

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-11
11 Data Alarms cobas® 8000 data manager
Alarms for Routine or STAT samples cobas® 8000 instrument

Alarms for Routine or STAT samples

This section tells you how to interpret data alarms when generated with regard to
routine or STAT samples.
The following symbols are used in the chart.

D Data A Alarm R Rerun TS A Auto Rerun

R
 With result  AU = Same volume A Auto rerun
 Without result  Core/PC, AU  Decrease N No auto rerun
 Without result in  Core/PC  Increase + Either
specified conditions
 Upper limit D data manager - No order
 Lower limit

No. Name Routine / STAT(a)

Clinical Chemistry Immuno-
Photometry LHI ISE Calc. Test assay

D A R A D A R A D A R A D A R A D A R A
R R R R R
0 (No Alarm)
1 ADC abnormal   = A   = A   = A      = A
2 ABS Cell blank abnormal   = A   = A       
3 Sample short   = N   = N   = N      = N
4 Reagent short   = N   = N   = N      = N
5 ABS over    A   A         
6 Prozone Error    A            
7 Reaction limit over    A            
8 Reaction limit over (2nd ..)    A            
9 Reaction limit over (3rd ..)    A            
10 Linearity abnormal 1   = A            
11 Linearity abnormal 2   = A            
12 S1ABS abnormal               
13 DUPLICATE error               
14 STANDARD error               
15 SENSITIVITY error               
16 CALIB error               
17 SD limit error               
18 ISE Noise error        = A      
19 ISE Voltage Level error        = A      
20 Slope abnormal               
21 Preparation abnormal               
22 IS concentration abnormal               
23 ISE Sample range over        = A      
24 Data error in comp. Test   = A     = A      
25 Unable to calculate comp. Test   = A     = A      

Roche Diagnostics
E-12 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 11 Data Alarms
®
cobas 8000 instrument Alarms for Routine or STAT samples

No. Name Routine / STAT(a)

Clinical Chemistry Immuno-
Photometry LHI ISE Calc. Test assay
D A R A D A R A D A R A D A R A D A R A
R R R R R
26 Technical Limit over (upper)    A      A       A
27 Technical Limit over (lower)    A     = A      - N
28               
29               
30               
31               
32               
33               
34               
35               
36               
37 Calculation test error            = A   
38 Overflow   N     N   N   N
39 Calculation not possible   = A     = A   = A   = A
40      
41      
42 Edited test   N     N   N   N
43 Calibration result abnormal (Sample Flag)   = N     = N     = N
44 Repeat limit over (upper)   = +     = +   = +   = +
45 Repeat limit over (lower)   = +     = +   = +   = +
46 ABS maximum over (nonLin curve)    A           
47              
48               
49               
50               
51 Response(ISE) abnormal 1               
52 Response(ISE) abnormal 2               
53 Conditioning(ISE) abnormal               
54               
55 ISE range over         A      
56 Kinetic unstable (Prozone error 2)    A            
57             
58             
59 Stop mixing   = A   = A   = A      
60 Mixing current low   = A   = A   = A      
61              
62 System reagent short              = A
63 AB level range over (Assay Buffer) run start              = A
64 AB level check error              = A
65 Current range over (run start)              = A

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-13
11 Data Alarms cobas® 8000 data manager
Alarms for Routine or STAT samples cobas® 8000 instrument

No. Name Routine / STAT(a)

Clinical Chemistry Immuno-
Photometry LHI ISE Calc. Test assay
D A R A D A R A D A R A D A R A D A R A
R R R R R
66 Current range check error              = A
67 Sample hovering              = A
68 Sample air bubble              = N
69 Reagent hovering              = A
70 Reagent film detection              = A
71 Potential carry over              = A
72 Sample clot   = N   = N   = N      = N
o r: If Clot Check count is 99 (in other
words, no check), data will not be
<Space>
73 Carry over detergent short   = N   = N        
74 Reagent disk temperature               = A
75 Incubator temperature               = A
76 System reagent temperature               = A
77 Cell temperature               = A
78 Missing value               
79 System errors               
80 Monotony of curve               
81 Minimum signal               
82 Maximum signal               
83 Sample carry over for modules   - N      - N      - N
84 Minimum/Maximum signal               
85 Minimum acceptable difference               
86 Sample LLD abnormal               = A
87 Sample LLD noise               = A
88              
89              
90              
91              
92              
93 Washing buffer temperature               = A
94 Washing buffer short               = A
95 Clot pressure sensor ADC (underflow)               = A
96 Clot pressure sensor ADC (overflow)               = A
97 Clot pressure abnormal               = A
98 Sample pipettor air bubble               = A
99 Current range over (operation)               = A
100 Low level signal               = A
101 Reagent Expired Date    N            N
102 QC error               
103 Serum index interference lipaemia   - N      - N   - N   - N

Roche Diagnostics
E-14 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 11 Data Alarms
®
cobas 8000 instrument Alarms for Routine or STAT samples

No. Name Routine / STAT(a)

Clinical Chemistry Immuno-
Photometry LHI ISE Calc. Test assay
D A R A D A R A D A R A D A R A D A R A
R R R R R
104 Serum index interference hemolysis   - N      - N   - N   - N
105 Serum index interference icteric   - N      - N   - N   - N
106 Serum index interference lipaemia /   - N      - N   - N   - N
hemolysis
107 Serum index specific interference lipaemia /   - N      - N   - N   - N
icteric
108 Serum index interference hemolysis / icteric   - N      - N   - N   - N
109 Serum index interference lipaemia /   - N      - N   - N   - N
hemolysis / icteric
110
111 On board stability limit over on Reagent   - N   - N   - N
Manager
112 On board stability limit over on Reagent   - N   - N   - N   - N
Rotor
(a) Legend:
D Data:  With result /  Without result /  Without result in specified conditions /  Upper limit /  Lower limit
A Alarm:  AU /  Core/PC, AU /  Core/PC / D data manager
R Rerun test selection: = Same volume /  Decrease /  Increase / - No order
AR Auto rerun: A Auto rerun / N No auto rerun / + Either

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-15
11 Data Alarms cobas® 8000 data manager
Alarms for Control and Calibration samples cobas® 8000 instrument

Alarms for Control and Calibration samples

This section tells you how to interpret data alarms when generated by quality control
or calibration samples.
The following symbols are used in the chart.

D Data A Alarm
 With result  AU
 Without result  Core/PC, AU
 Without result in  Core/PC
specified conditions
 Upper limit D data manager
 Lower limit

No. Name Control(a) Calibration(a)

Clin Chem Imm Clin Chem Imm
Photo ISE Calc Photo ISE
D A D A D A D A D A D A D A
0 (No Alarm)              
1 ADC abnormal              
2 ABS Cell blank abnormal              
3 Sample short              
4 Reagent short              
5 ABS over              
6 Prozone Error              
7 Reaction limit over              
8 Reaction limit over (2nd ..)              
9 Reaction limit over (3rd ..)              
10 Linearity abnormal 1              
11 Linearity abnormal 2              
12 S1ABS abnormal              
13 DUPLICATE error              
14 STANDARD error              
15 SENSITIVITY error              
16 CALIB error              
17 SD limit error              
18 ISE Noise error              
19 ISE Voltage Level error              
20 Slope abnormal              
21 Preparation abnormal              
22 IS concentration abnormal              
23 ISE Sample range over              
24 Data error in comp. Test              
25 Unable to calculate comp. Test              
26 Technical Limit over (upper)              

Roche Diagnostics
E-16 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 11 Data Alarms
®
cobas 8000 instrument Alarms for Control and Calibration samples

No. Name Control(a) Calibration(a)

Clin Chem Imm Clin Chem Imm
Photo ISE Calc Photo ISE
D A D A D A D A D A D A D A
27 Technical Limit over (lower)              
28           
29           
30           
31           
32           
33           
34           
35           
36           
37 Calculation test error             
38 Overflow              
39 Calculation not possible             
40          
41          
42 Edited test              
43 Calibration result abnormal (Sample              
Flag)
44 Repeat limit over (upper)              
45 Repeat limit over (lower)              
46 ABS maximum over (nonLin curve)              
47              
48              
49              
50              
51 Response(ISE) abnormal 1              
52 Response(ISE) abnormal 2              
53 Conditioning(ISE) abnormal              
54              
55 ISE range over              
56 Kinetic unstable (Prozone error 2)              
57              
58              
59 Stop mixing              
60 Mixing current low              
61              
62 System reagent short              
63 AB level range over (Assay Buffer) run              
start
64 AB level check error              
65 Current range over (run start)              
66 Current range check error              
Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-17
11 Data Alarms cobas® 8000 data manager
Alarms for Control and Calibration samples cobas® 8000 instrument

No. Name Control(a) Calibration(a)

Clin Chem Imm Clin Chem Imm
Photo ISE Calc Photo ISE
D A D A D A D A D A D A D A
67 Sample hovering              
68 Sample air bubble              
69 Reagent hovering              
70 Reagent film detection              
71 Potential carry over              
72 Sample clot              
o r: If Clot Check count is 99 (in other
words, no check), data will not be
<Space>
73 Carry over detergent short              
74 Reagent disk temperature              
75 Incubator temperature              
76 System reagent temperature              
77 Cell temperature              
78 Missing value              
79 System errors              
80 Monotony of curve              
81 Minimum signal              
82 Maximum signal              
83 Sample carry over for modules              
84 Minimum/Maximum signal              
85 Minimum acceptable difference              
86 Sample LLD abnormal              
87 Sample LLD noise              
88              
89              
90              
91              
92              
93 Washing buffer temperature              
94 Washing buffer short              
95 Clot pressure sensor ADC (underflow)              
96 Clot pressure sensor ADC (overflow)              
97 Clot pressure abnormal              
98 Sample pipettor air bubble              
99 Current range over (operation)              
100 Low level signal              
101 Reagent Expired Date              
102 QC error  D  D  D  D      
103 Serum index interference lipaemia              
104 Serum index interference hemolysis              
105 Serum index interference icteric              
Roche Diagnostics
E-18 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 11 Data Alarms
®
cobas 8000 instrument Alarms for Control and Calibration samples

No. Name Control(a) Calibration(a)

Clin Chem Imm Clin Chem Imm
Photo ISE Calc Photo ISE
D A D A D A D A D A D A D A
106 Serum index interference lipaemia /              
hemolysis
107 Serum index specific interference              
lipaemia / icteric
108 Serum index interference hemolysis /              
icteric
109 Serum index interference lipaemia /              
hemolysis / icteric
110
111 On board stability limit over on Reagent    
Manager
112 On board stability limit over on Reagent              
Rotor
(a) Legend:
D Data:  With result /  Without result /  Without result in specified conditions /  Upper limit /  Lower limit
A Alarm:  AU /  Core/PC, AU /  Core/PC / D data manager

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-19
11 Data Alarms cobas® 8000 data manager
Alarms for Control and Calibration samples cobas® 8000 instrument

Roche Diagnostics
E-20 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 12 Instrument alarms
®
cobas 8000 instrument Table of contents

Instrument alarms

This chapter describes the alarms generated on the cobas® 8000 instrument by errors
in communication with the data manager or the host.

In this chapter Chapter 12

Instrument alarms .......................................................................................................... E-23

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-21
12 Instrument alarms cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
E-22 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 12 Instrument alarms
®
cobas 8000 instrument Instrument alarms

Instrument alarms

This section has a table of the instrument alarms involving communication between
the Control Unit or the instrument on one side, and the data manager or host on the
other.
If an instrument alarm occurs that is not in this list, consult your RAuthorized Roche
Diagnostics service personnel for more information.

Code Sub- Alarm Message Content Troubleshooting

110 1 Abnormal Text from Contents of the text received 1. Check the connection status of Data Manager on
Data Manager from the Data Manager are System Overview > Data Manager. If it is wait status,
invalid. connect it from Data Manager.
2. Check if the connector was not plugged in during the
data communication.
3. Restart the system.
4. Contact service representative, if alarm recurs.
111 2 Abnormal Test Selection System did not receive a 1. Check the Data Manager's operation or connection
from Data Manager response against its inquiry status.
within a timeout period. 2. Check if the connector got unplugged during the data
communication.
3. Check the inquiry timeout on Utility > System > Data
Manager Settings.
4. Contact service representative, if alarm recurs.
111 51 Abnormal Test Selection Reading error occurred in the 1. Restart the system.
from Data Manager sample management 2. Contact service representative, if alarm recurs.
database.
111 52 Abnormal Test Selection Dilution ratio value is outside 1. Check the Data Manager settings.
from Data Manager the range. 2. Check the dilution ratio.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
111 53 Abnormal Test Selection The received sample 1. Check the Data Manager settings.
from Data Manager information is not requested 2. Check the sample information.
one. Either of the following 3. Refer to the specifications of system interface
items is wrong: communication.
o Sample Type 4. Contact service representative, if alarm recurs.
o Sample ID
o Sequence No.
o Rack ID
o Position No.
111 54 Abnormal Test Selection Writing error occurred in the 1. Restart the system.
from Data Manager sample management 2. Contact service representative, if alarm recurs.
database.
111 55 Abnormal Test Selection Sample data file on the sample 1. Perform Delete All on Workplace > Data Review.
from Data Manager management database is full. 2. Perform Sample Data Clear on System Overview.
111 56 Abnormal Test Selection Result data file on the sample 1. Perform Delete All on Workplace > Data Review.
from Data Manager management database is full. 2. Perform Sample Data Clear on System Overview.
111 57 Abnormal Test Selection The Stat rack ID is out of the Check the orders on System > Rack Assignment.
from Data Manager range.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-23
12 Instrument alarms cobas® 8000 data manager
Instrument alarms cobas® 8000 instrument

Code Sub- Alarm Message Content Troubleshooting

111 58 Abnormal Test Selection The sample position on the 1. Perform System Communication Trace on Print.
from Data Manager Stat rack is out of the range. 2. Check the HL7 text. (Test Selection Download Text -
Batch)
3. Contact service representative, if alarm recurs.
111 59 Abnormal Test Selection The combination of a Stat 1. Perform System Communication Trace on Print.
from Data Manager rack ID and a sample position 2. Check the HL7 text. (Test Selection Download Text)
has been already assigned.
111 60 Abnormal Test Selection The sample ID contains the 1. Perform System Communication Trace on Print.
from Data Manager abnormal code. 2. Check the HL7 text. (Test Selection Download Text)
126 200 Data Manager Communication error 1. Check the connection status of Data Manager on
Communication Error occurred. Communication System Overview > Data Manager. If it is wait status,
line was turned to offline connect it from Data Manager.
status. 2. Check if the connector was not plugged in during the
data communication.
3. Restart the system.
4. Contact service representative, if alarm recurs.
126 201 Data Manager Automatic recovery measures 1. Check the connection status of Data Manager on
Communication Error for connection between the System Overview > Data Manager. If it is wait status,
Data Manager and the system connect it from Data Manager.
were performed 15 times in a 2. Check if the connector was not plugged in during the
row. By this alarm, the data communication.
communication will be 3. Restart the system.
disconnected. 4. Contact service representative, if alarm recurs.
126 202 Data Manager Communication error 1. Check the connection status of Data Manager on
Communication Error occurred during connection. System Overview > Data Manager. If it is wait status,
(Control socket connect it from Data Manager.
communication line) 2. Check if the connector was not plugged in during the
data communication.
3. Restart the system.
4. Contact service representative, if alarm recurs.
126 203 Data Manager Communication error 1. Check the connection status of Data Manager on
Communication Error occurred. When receiving it, System Overview > Data Manager. If it is wait status,
abnormality was detected. connect it from Data Manager.
(Control socket 2. Check if the connector was not plugged in during the
communication line) data communication.
3. Restart the system.
4. Contact service representative, if alarm recurs.
126 204 Data Manager Internal process error 1. Restart the system.
Communication Error occurred. 2. Contact service representative, if alarm recurs.
126 205 Data Manager Communication error 1. Check the connection status of Data Manager on
Communication Error occurred. When receiving it, System Overview > Data Manager. If it is wait status,
abnormality was detected. connect it from Data Manager.
(Control socket 2. Check if the connector was not plugged in during the
communication line) data communication.
3. Restart the system.
4. Contact service representative, if alarm recurs.
126 206 Data Manager Communication error 1. Check the connection status of Data Manager on
Communication Error occurred, due to either of the System Overview > Data Manager. If it is wait status,
following causes: connect it from Data Manager.
o Wire break. 2. Check if the connector was not plugged in during the
o Momentary power failure. data communication.
3. Restart the system.
4. Contact service representative, if alarm recurs.
Roche Diagnostics
E-24 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 12 Instrument alarms
®
cobas 8000 instrument Instrument alarms

Code Sub- Alarm Message Content Troubleshooting

126 207 Data Manager Internal process error 1. Restart the system.
Communication Error occurred. 2. Contact service representative, if alarm recurs.
126 208 Data Manager Internal process error 1. Restart the system.
Communication Error occurred. 2. Contact service representative, if alarm recurs.
126 301 Data Manager No response from Data 1. Check the connection status of Data Manager on
Communication Error Manager within a timeout. System Overview > Data Manager. If it is wait status,
(Control socket connect it from Data Manager.
communication line) 2. Check if the connector was not plugged in during the
data communication.
3. Restart the system.
4. Contact service representative, if alarm recurs.
126 302 Data Manager Message error occurred. 1. Restart the system.
Communication Error (Control socket 2. Contact service representative, if alarm recurs.
communication line)
126 303 Data Manager FTP transmission error 1. Restart the system.
Communication Error occurred. (Control socket 2. Contact service representative, if alarm recurs.
communication line)
126 304 Data Manager Internal process error 1. Restart the system.
Communication Error occurred. (Control socket 2. Contact service representative, if alarm recurs.
communication line)
126 305 Data Manager Database access error 1. Restart the system.
Communication Error occurred. (Control socket 2. Contact service representative, if alarm recurs.
communication line)
126 306 Data Manager Communication was turned 1. Check the connection status of Data Manager on
Communication Error to offline status. (Control System Overview > Data Manager. If it is wait status,
socket communication line) connect it from Data Manager.
2. Check if the connector was not plugged in during the
data communication.
3. Restart the system.
4. Contact service representative, if alarm recurs.
126 401 Data Manager Abnormality connection with 1. Restart the system.
Communication Error Data Manager. (FTP line) 2. Contact service representative, if alarm recurs.
126 402 Data Manager A file cannot be copied. 1. Restart the system.
Communication Error 2. Contact service representative, if alarm recurs.
126 403 Data Manager There is no response from 1. Check the connection status of Data Manager on
Communication Error Data Manager. System Overview > Data Manager. If it is wait status,
connect it from Data Manager.
2. Check if the connector was not plugged in during the
data communication.
3. Restart the system.
4. Contact service representative, if alarm recurs.
126 501 Data Manager The response from the Data 1. Restart the system.
Communication Error manager is wrong. 2. Contact service representative, if alarm recurs.
127 1 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the CI11. 2. Check the CI11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-25
12 Instrument alarms cobas® 8000 data manager
Instrument alarms cobas® 8000 instrument

Code Sub- Alarm Message Content Troubleshooting

127 2 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the UR11. 2. Check the UR11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 3 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the PL11. 2. Check the PL11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 4 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the PD11. 2. Check the PD11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 5 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the CL11. 2. Check the CL11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 6 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the CD11. 2. Check the CD11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 7 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the QL11. 2. Check the QL11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 8 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the QD11. 2. Check the QD11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 9 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the RD11. 2. Check the RD11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 10 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the TQ11. 2. Check the TQ11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 11 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the CV11. 2. Check the CV11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.

Roche Diagnostics
E-26 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 12 Instrument alarms
®
cobas 8000 instrument Instrument alarms

Code Sub- Alarm Message Content Troubleshooting

127 12 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the CQ11. 2. Check the CQ11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 13 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the MR11. 2. Check the MR11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 14 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the MK11. 2. Check the MK11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 15 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the RM11. 2. Check the RM11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 16 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the EI12. 2. Check the EI11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 17 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the EI13. 2. Check the EI13 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 18 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the PU11. 2. Check the PU11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 19 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the PU12. 2. Check the PU12 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 20 Abnormal Text from Abnormal communication ID 1. Perform System Communication Trace on Print.
Data Manager was detected. 2. Check the undefined communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 21 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the EU11. 2. Check the EU11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-27
12 Instrument alarms cobas® 8000 data manager
Instrument alarms cobas® 8000 instrument

Code Sub- Alarm Message Content Troubleshooting

127 22 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the WL11. 2. Check the WL11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 23 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the WD11. 2. Check the WD11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 24 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the ER11. 2. Check the ER11 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 25 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the ER12. 2. Check the ER12 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
127 26 Abnormal Text from Communication ID error was 1. Perform System Communication Trace on Print.
Data Manager detected in the ER13. 2. Check the ER13 communication ID.
3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
300 1 Sample Management Sample data file on the sample 1. Perform Delete All on Workplace > Data Review.
Database Error management database is full. 2. Perform Sample Data Clear on System Overview.
300 2 Sample Management Result data file on the sample 1. Perform Delete All on Workplace > Data Review.
Database Error management database is full. 2. Perform Sample Data Clear on System Overview.
300 3 Sample Management Link data file on the sample Check the test selection on Workplace > Test Selection.
Database Error management database is full.
300 4 Sample Management The sample data file on the 1. Perform Delete All on Workplace > Data Review.
Database Error sample management database 2. Perform Sample Data Clear on System Overview.
is full.
300 5 Warning of Database The sample data file on the 1. Perform Delete All on Workplace > Data Review.
Registration sample management database 2. Perform Sample Data Clear on System Overview.
becomes full.
301 -3 TS Register Error The test selections are not Check the test selections on Workplace > Test Selection
registered because the sample or QC > Status.
test DB is full. The
subcategory code indicates
the rack No. and the cup
position. For example,
Subcategory code No.
(XXXXXY) XXXXX: rack No.
Y: cup

Roche Diagnostics
E-28 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 12 Instrument alarms
®
cobas 8000 instrument Instrument alarms

Code Sub- Alarm Message Content Troubleshooting

302 -3 Rerun TS Register Error The rerun test selections are Check the test selections on Workplace > Test Selection.
not registered because the
sample test DB is full. The
subcategory code indicates
the rack No. and the cup
position. For example,
Subcategory code No.
(XXXXXY) XXXXX: rack No.
Y: cup
321 1 Sample Duplication Error The system cannot analyze a 1. When the system completes the analysis of loaded
sample, because duplicated samples, retry the sample.
date is included in the 2. Check the followings. * Sample Type * Sample ID *
barcode label on the sample. Sequence No. * Rack ID * Rack Position No.
The duplicated data is
followings:
o In case of routine sample
in barcode mode: Sample
Type, Sample ID
o In case of Stat sample in
barcode mode: Sample
Type, Sample ID
o In case of routine sample
in non-barcode mode:
Sample Type
322 -3 Control Sample In the following cases, there 1. Perform Delete All on Workplace > Data Review.
Duplication Error exists same control sample 2. Perform Sample Data Clear on System Overview.
numbers registered in 3. Don't set the same control samples in a same rack
database: groups.
o The same number is
applied to a control
sample because applied
number returned to the
first.
o There are same control
samples in a same rack
group in case of rack
assign mode. The
subcategory code
indicates the rack
323 -3 Control Sequence No. Control samples are not 1. Perform Delete All on Workplace > Data Review.
Register Error registered because the control 2. Contact service representative, if alarm recurs.
sequence No. cannot be
corresponding to the one
which will be registered in the
Sample DB. The subcategory
code indicates the rack No.
and the cup position. For
example, Subcategory code
No. (XXXXXY) XXXXX: rack
No. Y: cup

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-29
12 Instrument alarms cobas® 8000 data manager
Instrument alarms cobas® 8000 instrument

Code Sub- Alarm Message Content Troubleshooting

341 -1 Application Code / When result is uploading, Contact service representative.
testcode Conversion Host code is not registered.
Error (Transmission) The subcategory code
indicates the application code.
342 1 Application Code / When request is Contact service representative.
testcode Conversion downloading, Host code is
Error not registered.
891 -2 Data Manager Communication error was 1. Check the connection status of Data Manager on
Communication Error occurred during connection. System Overview > Data Manager. If it is wait status,
(HL7 communication line) connect it from Data Manager.
The subcategory code 2. Check if the connector was not plugged in during the
indicates communication line data communication.
number. 3. Restart the system.
4. Contact service representative, if alarm recurs.
892 -2 Data Manager Communication error 1. Check the connection status of Data Manager on
Communication Error occurred during connection. System Overview > Data Manager. If it is wait status,
Detected disconnection. The connect it from Data Manager.
subcategory code indicates 2. Check if the connector was not plugged in during the
communication line number. data communication.
3. Restart the system.
4. Contact service representative, if alarm recurs.
893 -2 Data Manager Communication error 1. Check the connection status of Data Manager on
Communication Error occurred. When receiving it, System Overview > Data Manager. If it is wait status,
abnormality was detected. connect it from Data Manager.
(HL7 communication line) 2. Check if the connector was not plugged in during the
The subcategory code data communication.
indicates communication line 3. Restart the system.
number. 4. Contact service representative, if alarm recurs.
894 -2 Data Manager Communication error 1. Check the connection status of Data Manager on
Communication Error occurred. When receiving it, System Overview > Data Manager. If it is wait status,
abnormality was detected. connect it from Data Manager.
(HL7 communication line) 2. Check if the connector was not plugged in during the
The subcategory code data communication.
indicates communication line 3. Restart the system.
number. 4. Contact service representative, if alarm recurs.
895 -2 Data Manager Internal process error 1. Restart the system.
Communication Error occurred. The subcategory 2. Contact service representative, if alarm recurs.
code indicates
communication line number.
901 -2 Abnormal Text from First segment is not a header 1. Perform System Communication Trace on Print.
Data Manager segment (MSH). The 2. Check the MSH segment.
subcategory code indicates 3. Refer to the specifications of system interface
communication line number. communication.
4. Contact service representative, if alarm recurs.
902 -2 Abnormal Text from Undefined segment was 1. Perform System Communication Trace on Print.
Data Manager found. The subcategory code 2. Check the undefined segment.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.

Roche Diagnostics
E-30 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 12 Instrument alarms
®
cobas 8000 instrument Instrument alarms

Code Sub- Alarm Message Content Troubleshooting

903 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager message. The subcategory 2. Check whether '<CR><FS><CR>' (0x0d1c0d) is at
code indicates the end of the message.
communication line number. 3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
904 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager EQU segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates EQU segment.
communication line number. 3. Contact service representative, if alarm recurs.
905 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager INV segment. The 2. Check whether '<CR>' (0x0d) is at the end of the INV
subcategory code indicates segment.
communication line number. 3. Contact service representative, if alarm recurs.
906 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager MSA segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates MSA segment.
communication line number. 3. Contact service representative, if alarm recurs.
907 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager MSH segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates MSH segment.
communication line number. 3. Contact service representative, if alarm recurs.
908 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager NDS segment. The 2. Check whether '<CR>' (0x0d) is at the end of the NDS
subcategory code indicates segment.
communication line number. 3. Contact service representative, if alarm recurs.
909 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager OBR segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates OBR segment.
communication line number. 3. Contact service representative, if alarm recurs.
910 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager OBX segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates OBX segment.
communication line number. 3. Contact service representative, if alarm recurs.
911 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager ORC segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates ORC segment.
communication line number. 3. Contact service representative, if alarm recurs.
912 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager PID segment. The 2. Check whether '<CR>' (0x0d) is at the end of the PID
subcategory code indicates segment.
communication line number. 3. Contact service representative, if alarm recurs.
913 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager QAK segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates QAK segment.
communication line number. 3. Contact service representative, if alarm recurs.
914 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager QID segment. The 2. Check whether '<CR>' (0x0d) is at the end of the QID
subcategory code indicates segment.
communication line number. 3. Contact service representative, if alarm recurs.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-31
12 Instrument alarms cobas® 8000 data manager
Instrument alarms cobas® 8000 instrument

Code Sub- Alarm Message Content Troubleshooting

915 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager QPD segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates QPD segment.
communication line number. 3. Contact service representative, if alarm recurs.
916 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager RCP segment. The 2. Check whether '<CR>' (0x0d) is at the end of the RCP
subcategory code indicates segment.
communication line number. 3. Contact service representative, if alarm recurs.
917 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager SAC segment. The 2. Check whether '<CR>' (0x0d) is at the end of the SAC
subcategory code indicates segment.
communication line number. 3. Contact service representative, if alarm recurs.
918 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager SID segment. The subcategory 2. Check whether '<CR>' (0x0d) is at the end of the SID
code indicates segment.
communication line number. 3. Contact service representative, if alarm recurs.
919 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager SPM segment. The 2. Check whether '<CR>' (0x0d) is at the end of the SPM
subcategory code indicates segment.
communication line number. 3. Contact service representative, if alarm recurs.
920 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager TQ1 segment. The 2. Check whether '<CR>' (0x0d) is at the end of the TQ1
subcategory code indicates segment.
communication line number. 3. Contact service representative, if alarm recurs.
921 -2 Abnormal Text from There is no end code in the 1. Perform System Communication Trace on Print.
Data Manager TCD segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates TCD segment.
communication line number. 3. Contact service representative, if alarm recurs.
922 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager EQU segment. The 2. Check the EQU segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
923 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager INV segment. The 2. Check the INV segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
924 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager MSA segment. The 2. Check the MSA segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
925 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager MSH segment. The 2. Check the MSH segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.

Roche Diagnostics
E-32 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 12 Instrument alarms
®
cobas 8000 instrument Instrument alarms

Code Sub- Alarm Message Content Troubleshooting

926 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager NDS segment. The 2. Check the NDS segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
927 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager OBR segment. The 2. Check the OBR segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
928 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager OBX segment. The 2. Check the OBX segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
929 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager ORC segment. The 2. Check the ORC segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
930 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager PID segment. The 2. Check the PID segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
931 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager QAK segment. The 2. Check the QAK segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
932 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager QID segment. The 2. Check the QID segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
933 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager QPD segment. The 2. Check the QPD segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
934 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager RCP segment. The 2. Check the RCP segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
935 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager SAC segment. The 2. Check the SAC segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-33
12 Instrument alarms cobas® 8000 data manager
Instrument alarms cobas® 8000 instrument

Code Sub- Alarm Message Content Troubleshooting

936 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager SID segment. The subcategory 2. Check the SID segment.
code indicates field number 3. Refer to the specifications of system interface
and communication line communication.
number. 4. Contact service representative, if alarm recurs.
937 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager SPM segment. The 2. Check the SPM segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
938 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager TQ1 segment. The 2. Check the TQ1 segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
939 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager TCD segment. The 2. Check the TCD segment.
subcategory code indicates 3. Refer to the specifications of system interface
field number and communication.
communication line number. 4. Contact service representative, if alarm recurs.
940 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager MSG segment. The message 2. Check the message type [MSH-9] field of the MSH
type of the HL7 text was segment.
abnormal. The subcategory 3. Refer to the specifications of system interface
code indicates communication.
communication line number. 4. Contact service representative, if alarm recurs.
941 -2 Abnormal Text from There is no EQU segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the EQU segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
942 -2 Abnormal Text from There is no MSA segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the MSA segment exits.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
943 -2 Abnormal Text from There is no MSH segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the MSH segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
944 -2 Abnormal Text from There is no OBR segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the OBR segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
945 -2 Abnormal Text from There is no OBX segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the OBX segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.

Roche Diagnostics
E-34 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 12 Instrument alarms
®
cobas 8000 instrument Instrument alarms

Code Sub- Alarm Message Content Troubleshooting

946 -2 Abnormal Text from There is no ORC segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the ORC segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
947 -2 Abnormal Text from There is no PID segment. The 1. Perform System Communication Trace on Print.
Data Manager subcategory code indicates Confirm that the PID segment exists.
communication line number. 2. Refer to the specifications of system interface
communication.
3. Contact service representative, if alarm recurs.
948 -2 Abnormal Text from There is no QAK segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the QAK segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
949 -2 Abnormal Text from There is no QID segment. The 1. Perform System Communication Trace on Print.
Data Manager subcategory code indicates 2. Confirm that the QID segment exists.
communication line number. 3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
950 -2 Abnormal Text from There is no QPD segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the QPD segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
951 -2 Abnormal Text from There is no RCP segment. The 1. Perform System Communication Trace on Print.
Data Manager subcategory code indicates 2. Confirm that the RCP segment exists.
communication line number. 3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
952 -2 Abnormal Text from There is no SPM segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the SPM segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
940 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager MSG segment. The message 2. Check the message type [MSH-9] field of the MSH
type of the HL7 text was segment.
abnormal. The subcategory 3. Refer to the specifications of system interface
code indicates communication.
communication line number. 4. Contact service representative, if alarm recurs.
941 -2 Abnormal Text from There is no EQU segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the EQU segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
942 -2 Abnormal Text from There is no MSA segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the MSA segment exits.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-35
12 Instrument alarms cobas® 8000 data manager
Instrument alarms cobas® 8000 instrument

Code Sub- Alarm Message Content Troubleshooting

943 -2 Abnormal Text from There is no MSH segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the MSH segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
944 -2 Abnormal Text from There is no OBR segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the OBR segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
945 -2 Abnormal Text from There is no OBX segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the OBX segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
946 -2 Abnormal Text from There is no ORC segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the ORC segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
947 -2 Abnormal Text from There is no PID segment. The 1. Perform System Communication Trace on Print.
Data Manager subcategory code indicates 2. Confirm that the PID segment exists.
communication line number. 3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
948 -2 Abnormal Text from There is no QAK segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the QAK segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
949 -2 Abnormal Text from There is no QID segment. The 1. Perform System Communication Trace on Print.
Data Manager subcategory code indicates 2. Confirm that the QID segment exists.
communication line number. 3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
950 -2 Abnormal Text from There is no QPD segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the QPD segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.
951 -2 Abnormal Text from There is no RCP segment. The 1. Perform System Communication Trace on Print.
Data Manager subcategory code indicates 2. Confirm that the RCP segment exists.
communication line number. 3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
952 -2 Abnormal Text from There is no SPM segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the SPM segment exists.
indicates communication line 3. Refer to the specifications of system interface
number. communication.
4. Contact service representative, if alarm recurs.

Roche Diagnostics
E-36 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 12 Instrument alarms
®
cobas 8000 instrument Instrument alarms

Code Sub- Alarm Message Content Troubleshooting

953 -2 Abnormal Text from There is no TQ1 segment. The 1. Perform System Communication Trace on Print.
Data Manager subcategory code indicates 2. Confirm that the TQ1 segment exists.
communication line number. 3. Refer to the specifications of system interface
communication.
4. Contact service representative, if alarm recurs.
992 -1 Abnormal Test Selection One or more tests requested 1. Check if the Item Codes requested by the Host are
from Data Manager by Data Manager are in appropriate.
progress. 2. Contact service representative, if alarm recurs.
994 1 Data Manager Message Control ID of the 1. Perform System Communication Trace on Print.
Communication Error HL7 text received from Data 2. Check the HL7 text. (Test Selection Response Text)
Manager is not the 3. Contact service representative, if alarm recurs.
corresponding one. (Test
Selection Response Text)
994 2 Data Manager Message Control ID of the 1. Perform System Communication Trace on Print.
Communication Error HL7 text received from Data 2. Check the HL7 text. (Patient/QC Result Response
Manager is not the Text - Real)
corresponding one. 3. Contact service representative, if alarm recurs.
(Patient/QC Result Response
Text - Real)
994 3 Data Manager Message Control ID of the 1. Perform System Communication Trace on Print.
Communication Error HL7 text received from Data 2. Check the HL7 text. (Chemistry Calibration Result
Manager is not the Response Text)
corresponding one. 3. Contact service representative, if alarm recurs.
(Chemistry Calibration Result
Response
994 4 Data Manager Message Control ID of the 1. Perform System Communication Trace on Print.
Communication Error HL7 text received from Data 2. Check the HL7 text. (ISE Calibration Result Response
Manager is not the Text)
corresponding one. (ISE 3. Contact service representative, if alarm recurs.
Calibration Result Response
Text)
994 5 Data Manager Message Control ID of the 1. Perform System Communication Trace on Print.
Communication Error HL7 text received from Data 2. Check the HL7 text. (Immune Calibration Result
Manager is not the Response Text)
corresponding one. (Immune 3. Contact service representative, if alarm recurs.
Calibration Result Response
Text)
994 6 Data Manager Message Control ID of the 1. Perform System Communication Trace on Print.
Communication Error HL7 text received from Data 2. Check the HL7 text. (Patient/QC Result Response
Manager is not the Text - Batch)
corresponding one. 3. Contact service representative, if alarm recurs.
(Patient/QC Result Response
Text
994 7 Data Manager Message Control ID of the 1. Perform System Communication Trace on Print.
Communication Error HL7 text received from Data 2. Check the HL7 text. (Reaction Monitor Result
Manager is not the Response Text)
corresponding one. (Reaction 3. Contact service representative, if alarm recurs.
Monitor Result Response
Text)

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-37
12 Instrument alarms cobas® 8000 data manager
Instrument alarms cobas® 8000 instrument

Code Sub- Alarm Message Content Troubleshooting

994 8 Data Manager Message Control ID of the 1. Perform System Communication Trace on Print.
Communication Error HL7 text received from Data 2. Check the HL7 text. (Reaction Monitor Calibration
Manager is not the Result Response Text)
corresponding one. (Reaction 3. Contact service representative, if alarm recurs.
Monitor Calibration Result
Response Text)
994 9 Data Manager Message Control ID of the 1. Perform System Communication Trace on Print.
Communication Error HL7 text received from Data 2. Check the HL7 text. (Raw Data Result Response
Manager is not the Text)
corresponding one. (Raw 3. Contact service representative, if alarm recurs.
Data Result Response Text)
994 10 Data Manager Message Control ID of the 1. Perform System Communication Trace on Print.
Communication Error HL7 text received from Data 2. Check the HL7 text. (Raw Data Calibration Result
Manager is not the Response Text)
corresponding one. (Raw 3. Contact service representative, if alarm recurs.
Data Calibration Result
Response
994 11 Data Manager Message Control ID of the 1. Perform System Communication Trace on Print.
Communication Error HL7 text received from Data 2. Check the HL7 text. (Alarm Response Text)
Manager is not the 3. Contact service representative, if alarm recurs.
corresponding one. (Alarm
Response Text)
994 12 Data Manager The sample No. value is 1. Perform System Communication Trace on Print.
Communication Error invalid. 2. Check the HL7 text. (Test Selection Download Text -
Batch)
3. Contact service representative, if alarm recurs.
994 13 Data Manager The orders of the serum index 1. Perform System Communication Trace on Print.
Communication Error tests (L/H/I) are illegal. 2. Check the HL7 text. (Test Selection Download Text -
Batch)
3. Contact service representative, if alarm recurs.
995 -1 Abnormal Text from The sample type value is Check the sample type.
Data Manager invalid. The subcategory code
indicates the application code.
997 -2 Data Manager Though the system 1. Check the Data Manager settings.
Communication Error transmitted a text, the Data 2. Refer to the system interface communication
Manager did not receive a specifications.
response within 15 seconds.
(Reception timeout) The
subcategory code indicates
communication line number.
999 -1 Data Manager Host code is duplication Contact service representative.
Communication Error defined. The subcategory code
indicates the application code.

Roche Diagnostics
E-38 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 13 Using MODULAR PRE-ANALYTICS
®
cobas 8000 instrument Table of contents

Using MODULAR PRE-ANALYTICS

How to use a MODULAR PRE-ANALYTICS and
aliquoted samples without barcodes with data manager

This chapter describes how to use a MODULAR PRE-ANALYTICS with cobas® 8000
data manager. When using an MODULAR PRE-ANALYTICS, aliquoted samples do
not have barcodes. This chapter describes how samples are identified in this case.

In this chapter Chapter 13

Using a MODULAR PRE-ANALYTICS .................................................................... E-41
Sample IDs and barcodes ........................................................................................ E-41
Handling query messages without barcodes ........................................................ E-41
Configuring the Control Unit .......................................................................... E-41
Rerun without barcodes .................................................................................... E-41
Order of messages .................................................................................................... E-42
Handling batch test selections with strict rack and position ............................. E-43
Configuring data manager ............................................................................... E-43
Identifying the sample ....................................................................................... E-43
Clearing the sample list ..................................................................................... E-43

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-39
13 Using MODULAR PRE-ANALYTICS cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
E-40 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 13 Using MODULAR PRE-ANALYTICS
®
cobas 8000 instrument Using a MODULAR PRE-ANALYTICS

Using a MODULAR PRE-ANALYTICS

This chapter describes how to handle test selection requests, when using a
MODULAR PRE-ANALYTICS with cobas® 8000 data manager. When using an
MODULAR PRE-ANALYTICS, aliquoted samples do not have barcodes. This
chapter describes how such samples are identified, and in which fields data is passed
from data manager to the host and back.

Sample IDs and barcodes

For maximum throughput on the cobas® 8000 instrument, it is necessary to identify

the samples from a barcode. For this reason, and other reasons of efficiency, the
instrument generates the sample identifiers by reading the barcodes on the tubes.
This is the default configuration for the cobas® 8000 instrument.
However, if a MODULAR PRE-ANALYTICS is used in conjunction with the cobas®
8000 instrument, aliquoted sample tubes will not have barcodes. Therefore, it is not
possible to generate the sample identifiers from the barcodes. In this situation, it is
necessary to configure the cobas® 8000 instrument’s Control Unit so that it sends a
query to the data manager if a sample lacks a barcode. It is also necessary to configure
data manager to send the query to the host.

Handling query messages without barcodes

In normal operation, by default, a sample without a barcode generates an error on

cobas® 8000 instrument, and is handled by the instrument operator.

The host should be able to handle a missing sample ID

Because a user with configuration privileges can (intentionally or otherwise) configure the
cobas® 8000 instrument and data manager to send test selection inquiries without
barcode information, the host should be able to handle such a message, either with a test
selection reply or at least with a meaningful error message.

Configuring the Control Unit

To configure the cobas® 8000 instrument to process samples without barcodes with a
MODULAR PRE-ANALYTICS, enable the option on the Control Unit Test Selection
Ask in Barcode Read Error in: Utility > System > Data Manager Settings > Test
Selection Inquiry Settings > Test Selection Ask in Barcode Read Error.
e For details of the GUI settings, see Test Selection Ask in Barcode Read Error on page B-38.

Rerun without barcodes

When working without barcodes, rerun by gray racks (racks for 1st run) is not
permitted, because the analyzer cannot determine whether this is the first or second
presentation of the rack.
If you want to rerun the same routine rack, ensure that the LIS can handle a second
R1 Query correctly. This means that the LIS has to know which tests have already
been downloaded, because the tests should not be downloaded again. If this can not
be guaranteed, use rerun racks.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-41
13 Using MODULAR PRE-ANALYTICS cobas® 8000 data manager
Using a MODULAR PRE-ANALYTICS cobas® 8000 instrument

Order of messages

If a MODULAR PRE-ANALYTICS is connected, and a sample tube lacks a barcode,

and the messages are sent in realtime mode, order of messages is then as follows:
1. The cobas® 8000 instrument recognizes that a sample exists without a barcode. It
sends data manager a query for test selections, identifying the sample by:
o the rack ID
o the sample’s position on the rack (1 to 5)
o the sample type (which is the same as the rack type, as each type of sample
uses a different type of rack)
2. The data manager sends a query to the host asking for test selections for the
sample. The sample is identified to the host through the following information:
o the sample ID is given as a string of 22 asterisk (*) characters. This shows that
the sample tube lacks a barcode. This is passed in:
O ASTM Query Record (Q) field 3, component 3, or
O HL7 Query Parameter Definition Segment QPD-3.
o the rack ID, passed in:
O ASTM Query Record (Q) field 3, component 5, or
O HL7 Query Parameter Definition Segment QPD-5
o the sample’s position on the rack (1 to 5). This is passed in:
O ASTM Query Record (Q) field 3, component 6, or
O HL7 Query Parameter Definition Segment QPD-6
o the sample type (or rack type), in:
O in ASTM in the Query Record (Q) field 3, component 8, or
O in HL7 Query Parameter Definition Segment QPD-10.
3. The host must be programmed so that it looks up the sample’s identifier. It sends
the sample identifier in the order (or test selection) to data manager, as well as the
other identifying information:
o the sample ID is passed in:
O ASTM Order Record (O) field 3, or
O HL7 Specimen Segment (SPM) field SPM-2.
o the rack number, passed in:
O ASTM Order Record (O) field 4, component 2, or
O HL7 Container Information Segment (SAC) fields SAC-10
o the sample’s position on the rack (1 to 5). This is passed in:
O ASTM Order Record (O) field 4, component 3, or
O HL7 Container Information Segment (SAC) field SAC-11
o the sample type (or rack type)
O ASTM the Order Record (O) field 4, component 4, or
O HL7 Specimen Segment (SPM) field SPM-4.
4. The data manager passes this information on to the Control Unit.
5. The Control Unit, data manager and the host then use the sample identifier to
identify the sample in subsequent messages.
e For full information on the content of the supported ASTM and HL7 fields, see the
definitions in ASTM text content (LIS2 - A2) on page C-13, and HL7 text content on
page D-7.

Roche Diagnostics
E-42 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 13 Using MODULAR PRE-ANALYTICS
®
cobas 8000 instrument Using a MODULAR PRE-ANALYTICS

Handling batch test selections with strict rack and position

If you are using a MODULAR PRE-ANALYTICS and working without barcodes, the
recommended procedure is to configure the Control Unit and data manager to send
test selection queries, and to obtain a sample ID. However, if for some reason this
cannot be done, it is possible to configure the data manager to identify a sample tube
by the rack and position given in a batch test selection download. The data manager
then sets up a one-to-one relationship between the sample ID and the rack and
position of the sample tube.

Configuring data manager

To configure data manager to process batch test selection downloads for samples
without barcodes with an MODULAR PRE-ANALYTICS, enable the option Strict
rack and position mode in c8000 DM System Configuration > Service-related
configuration > Interface options.
e To use the Strict rack and position mode, select the data manager option Strict rack and
position mode. See Rack and position mode on page B-30.

By default, the data manager ignores any information about rack and position in a
batch test selection message. The option Strict rack and position mode configures
the data manager so that it uses the information on rack and position.

Identifying the sample

In this situation, the host must be programmed so that it looks up the rack and
position of the sample. It sends the sample identifier in the order (or test selection) to
data manager, as well as the other identifying information:
o the sample ID, passed in:
O ASTM Order Record (O) field 3, or
O HL7 Specimen Segment (SPM) field SPM-2.
o the rack number, passed in:
O ASTM Order Record (O) field 4, component 2, or
O HL7 Container Information Segment (SAC) fields SAC-10
o the sample’s position on the rack (1 to 5). This is passed in:
O ASTM Order Record (O) field 4, component 3, or
O HL7 Container Information Segment (SAC) field SAC-11
o the sample type (or rack type), passed in:
O ASTM the Order Record (O) field 4, component 4, or
O HL7 Specimen Segment (SPM) field SPM-4.
The data manager uses all the same fields to identify the sample in result message.

Do not move the sample to another rack

If you are using the MODULAR PRE-ANALYTICS with Strict rack and position mode, do
WARNING not move the sample to another rack until it is deleted. The tube’s rack and position must
stay the same, for the host, cobas® 8000 modular analyzer series and data manager to
identify it.

Clearing the sample list

In this situation, the data manager keeps an internal list of the rack and position of
each sample. When the samples are off-loaded from the racks, and new samples
Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-43
13 Using MODULAR PRE-ANALYTICS cobas® 8000 data manager
Using a MODULAR PRE-ANALYTICS cobas® 8000 instrument

loaded, it is necessary to clear this list of samples. The host must implement
functionality to do this, and simultaneously, the list of samples must be cleared
manually from the data manager by the laboratory technicians. To clear the list of
samples, navigate to cobas® 8000 data manager Routine Workplace > Sample
Overview , and select Reset Rack. For details see the cobas® 8000 modular analyzer
series Operator’s Manual.

Roche Diagnostics
E-44 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 14 Identifying patient samples by sequence number
®
cobas 8000 instrument Table of contents

Identifying patient samples by sequence

number
Numbering samples in sequence instead of using a
barcode

This chapter describes how the cobas® 8000 modular analyzer series can number
patient samples in sequence, instead of using barcodes and sample IDs.

In this chapter Chapter 14

Identifying samples ........................................................................................................ E-47
Sample IDs and barcodes ........................................................................................ E-47
Patient samples without barcodes ......................................................................... E-47
Identifying patient samples by sequence number ..................................................... E-47
Sequence numbers and sample IDs ....................................................................... E-48
What the data manager understands .................................................................... E-48
Important information for using sequence numbers ............................................... E-49
When using sequence numbers, pay attention to the following ....................... E-49
Using sample sequence numbers in ASTM ................................................................ E-50
Test selection inquiry .............................................................................................. E-50
Test selection download .......................................................................................... E-50
Test result message .................................................................................................. E-50
Using sample sequence numbers in HL7 .................................................................... E-51
Test selection inquiry .............................................................................................. E-51
Test selection download .......................................................................................... E-51
Test result message .................................................................................................. E-51

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-45
14 Identifying patient samples by sequence number cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
E-46 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 14 Identifying patient samples by sequence number
®
cobas 8000 instrument Identifying samples

Identifying samples

This section describes how the cobas® 8000 modular analyzer series instrument,
Control Unit, and data manager identify samples. It gives an outline of the options
available.

Sample IDs and barcodes

For maximum throughput on the cobas® 8000 instrument, it is necessary to identify

the samples from a barcode. For this reason, and other reasons of efficiency, the
instrument generates the sample identifiers by reading the barcodes on the tubes.
This is the default configuration for the cobas® 8000 instrument.

Patient samples without barcodes

However, in some situations, the patient sample tubes will not have barcodes.
Therefore, it is not possible to generate the sample identifiers from the barcodes.
In version 1.02.03 and higher, one way of handling this situation, is to configure the
cobas® 8000 instrument to give each sample a sequence number. This is described
below.

Identifying patient samples by sequence number

This section tells you how to identify patient samples by sequence number.
This setting on the instrument is called “sequence mode”. This works as follows:
o By default the sequence numbers start with 1, and then increase by 1 for each
sample. (1, 2, 3, etc.) The starting number is configurable, but the highest possible
number for a sample is 60,000.
o To implement this on the data manager, the Control Unit and the cobas® 8000
modular analyzer series instrument, ask for assistance from your authorized
Roche Diagnostics service personnel. Implementation requires a dedicated
installation tool. For details of installation, see the relevant service bulletins from
August 2011, and the cobas® 8000 modular analyzer series Service Manual from
version 1.02.04 (available 2012).

NOTICE Sequence numbers can only be used with patient samples

Sequence numbers can only be used with patient samples. Control samples cannot use
sequence numbers, even if patient samples are configured to do so.

NOTICE This configuration does not support a MODULAR PRE-ANALYTICS

Note that sequence numbers cannot be used with samples from a MODULAR PRE-
ANALYTICS.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-47
14 Identifying patient samples by sequence number cobas® 8000 data manager
Identifying patient samples by sequence number cobas® 8000 instrument

Sequence numbers and sample IDs

The data manager database is independent of the setting of the cobas® 8000 modular
analyzer series instrument and the Control Unit. Even if the instrument, the Control
Unit, and the data manager are configured for sequence mode, the host can still send
the data manager:
o order queries for earlier samples which are identified by barcode / sample ID. Any
response is sent at once.
o result queries for earlier samples which are identified by barcode / sample ID. Any
response is sent at once.
o test selection inquiries for samples with barcodes. These test selections will not be
downloaded to the instrument until the instrument is reconfigured to read
barcodes.

Identify a sample by either sample ID or sequence number, but not both.

If you want to identify the sample by sequence number, make sure that the sample ID (O-
3, SPM-2.3) is empty. If you send both a sample ID and a sequence number, the data
manager will use only the sample ID to identify the sample.

What the data manager understands

The data manager interprets each message as a barcode message or a sequence

number message according to how the sample is identified.

Sample ID Sequence number Sample identified by:

Sent in ASTM O-3, Q-3.3, or Sent in ASTM O-4.1, Q-3.4, or
HL7 SPM-2, QPD-3 HL7 QPD-3.2, SPM-2.2
empty empty Not permissible. Sample not
identified.
o ASTM: sample created
with no ID.
o HL7: ORA-2001
validation error
String empty Sample ID
empty Integer up to 60,000 Sequence number
String Integer up to 60,000 Sample ID, but this message
is not recommended nor
supported.
Table E-1 Identifying the sample in messages

Roche Diagnostics
E-48 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 14 Identifying patient samples by sequence number
®
cobas 8000 instrument Important information for using sequence numbers

Important information for using sequence numbers

When setting up or using sequence numbers, please consider the following.

Only service personnel can enable or disable sequence mode

Only authorized Roche Diagnostics service personnel can enable or disable sequence
CAUTION mode on the data manager, the cobas® 8000 modular analyzer series instrument and
Control Unit.

When using sequence numbers, pay attention to the following

Carefully observe the following warnings.

Regular database clean-up required

The data manager and cobas® 8000 modular analyzer series instrument can only handle
WARNING sequence numbers up to 60,000. You must clean up and delete the data in the data
manager’s internal database before the sequence number reaches 60,000. Otherwise
samples will be confused with earlier ones. Consult your Roche Diagnostics service
personnel and the relevant service bulletins starting August 2011 or the cobas® 8000
modular analyzer series Service Manual from version 1.02.04 (available 2012), for more
information.

Do not start sample IDs with the same internal prefix that is used in the data
manager
WARNING The data manager uses an internal prefix to identify sequence numbers, and to
differentiate them from sample IDs. By default, this prefix is set to “seq#”. However, it can
be configured to any other value by the authorized Roche Diagnostics service personnel,
using the relevant installation tool. Find out from them the exact prefix which is used in
your installation of the data manager. Choose a prefix that is different from the
starting characters of any possible sample ID used on your site. These sample IDs
are read from the barcodes affixed to tubes. Ask the administrators of the laboratory
organization for details on how they define the format of barcodes and sample IDs.
Make sure that sample IDs and sequence numbers do not start with the same characters.
Otherwise the data manager could confuse samples with each other.

The sample ID sent by the host takes precedence over the sequence number
If the host sends a sample ID to the data manager, the data manager uses the sample ID in
CAUTION preference to any sequence number in the message. If you are using a sequence number
in the message, make sure that the sample ID is not sent.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-49
14 Identifying patient samples by sequence number cobas® 8000 data manager
Using sample sequence numbers in ASTM cobas® 8000 instrument

Using sample sequence numbers in ASTM

This section compares messages in ASTM using barcode sample IDs and sequence
numbers.

Test selection inquiry

In a test selection inquiry message from the data manager to the host:
o When using the default barcode sample IDs, the data manager sends sample ID
from the barcode in Q-3.3.
o When identifying samples by sequence number, the data manager sends the
sequence number in Q-3.4.

Sample ID inquiry Q|1|^^2110903^0^50094^3^^S1^SC^R1||ALL|||||||R|O|

Sequence number inquiry Q|1|^^^3^50094^3^^S1^SC^R1||ALL|||||||R|O|

These fields are used the same way in an order query from the host to the data
manager.

Test selection download

In a test selection download message from the host to the data manager:
o When using the default barcode sample IDs, the host sends sample ID from the
barcode in O-3.
o When identifying samples by sequence number, the host sends the sequence
number in O-4.1.

Sample ID order record O|1|2110903|^50094^3^^S1^SC^|^^^205^|R|201108…

Sequence number order record Either

O|1||3^^^^S1^SC^|^^^205^|R|201…

or
O|1||3^50094^3^^S1^SC^|^^^205^|R|201…

Note that in a test selection upload from the data manager to the host, the Order
record, field 4 (O-4) is a simple number field, containing the sequence number.
O|1||3|^^^205^|R|201…

Test result message

In a test result message from the data manager to the host:

o When using the default barcode sample IDs, the data manager sends sample ID
from the barcode in O-3.
o When identifying samples by sequence number, the data manager sends the
sequence number in O-4.1.

Sample ID order record O|1|2110903|0^50094^3^^S1^SC^not|^^^112^1|R|201108…

Roche Diagnostics
E-50 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 14 Identifying patient samples by sequence number
®
cobas 8000 instrument Using sample sequence numbers in HL7

Sequence number order record O|1||3^50094^3^^S1^SC^not|^^^991^1|R|201…

Using sample sequence numbers in HL7

This section compares messages in HL7 using barcode sample IDs and sequence
numbers.

Test selection inquiry

In a test selection inquiry message from the data manager to the host:
o When using the default barcode sample IDs, the data manager sends sample ID
from the barcode in QPD-3-1.
o When identifying samples by sequence number, the data manager sends the
sequence number in QPD-3.2.

Sample ID inquiry QPD|TSREQ|4362|2110903||50094|3||||S1|SC|R1|R|

Sequence number inquiry QPD|TSREQ|4565|^3||50094|3||||S1|SC|R1|R|

These fields are used the same way in an order query from the host to the data
manager.

Test selection download

In a test selection download message from the host to the data manager:
o When using the default barcode sample IDs, the host sends sample ID from the
barcode in SPM-2.1.
o When identifying samples by sequence number, the host sends the sequence
number in SPM-2.2, and must send the rack ID in SAC-10, and tube’s position in
SAC-11.

Sample ID specimen segment SPM||2110903||S1||not|||||P|||^^^^|||20110615215424||||||||||SC

Sequence number specimen and SPM||^3||S1||not|||||P|||^^^^|||20110615215424||||||||||SC

container detail segments SAC||||||||||50094|3

These fields are used in the same way in a test selection upload from the data
manager to the host.

Test result message

In a test selection download message from the data manager to the host:
o When using the default barcode sample IDs, the data manager sends sample ID
from the barcode in SPM-2.1, and the rack ID in SAC-10, and tube’s position in
SAC-11.
o When identifying samples by sequence number, the data manager sends the
sequence number in SPM-2.2, and the rack ID in SAC-10, and tube’s position in
SAC-11.
Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-51
14 Identifying patient samples by sequence number cobas® 8000 data manager
Using sample sequence numbers in HL7 cobas® 8000 instrument

Sample ID specimen and SPM||2110903||S1||not|||||P|||^^^^|||20110615215424||||||||||SC|

container detail segments SAC||||||||||50094|3|

Sequence number specimen and SPM||^3||S1||not|||||P|||^^^^|||20110617105639||||||||||SC|

container detail segments SAC||||||||||50094|3|

Roche Diagnostics
E-52 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument Table of contents

Communication examples

This chapter presents some examples of messages generated by cobas® 8000 data
manager, and a connected host system (LIS / WAM).

In this chapter Chapter 15

Example communication trace files ............................................................................ E-57
ASTM trace files ............................................................................................................. E-57
Low level trace file .................................................................................................... E-57
Test selection inquiry from data manager ............................................................ E-58
Routine test selection inquiry and download ................................................ E-58
STAT sample test selection inquiry and download ...................................... E-58
Test selection inquiry and download if no sample found ............................ E-59
Test selection inquiry with sequence number ............................................... E-59
Patient result upload messages .............................................................................. E-60
Realtime ISE result upload ............................................................................... E-60
ISE result upload - sample short ...................................................................... E-60
C-module result upload with no flag .............................................................. E-60
Glucose result with alarm flag .......................................................................... E-61
Batch upload of current results ........................................................................ E-61
Batch upload of current results -sample short ............................................... E-61
Batch upload all previous results ..................................................................... E-62
Result below normal range ............................................................................... E-62
Result below level of detection ......................................................................... E-63
Result with sample identified by sequence number ...................................... E-63
Quality control uploads .......................................................................................... E-64
Realtime quality control upload ...................................................................... E-64
Realtime quality control upload with a standby bottle ................................. E-64
Batch quality control upload ............................................................................ E-64
Batch quality control upload with a standby bottle ...................................... E-65
Calibration result uploads ...................................................................................... E-65
C-module calibration result upload ................................................................ E-65
ISE-module calibration result upload ............................................................. E-65
E-module calibration result upload ................................................................ E-66
Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-53
15 Communication examples cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Result request from host and the data manager result upload .......................... E-66
Request for currently active results ................................................................. E-66
Request for all results ........................................................................................ E-67
Result request but no results ............................................................................ E-67
Result request but sample not found .............................................................. E-68
Result request in with a sequence number ..................................................... E-68
Order query from the host ...................................................................................... E-69
Order query for all tests .................................................................................... E-69
Order query for all open tests .......................................................................... E-69
Order query but no open tests ......................................................................... E-69
Order query but sample not found ................................................................. E-70
Order query with sample identified by sequence number ........................... E-70
HL7 trace files ................................................................................................................. E-71
Test selection inquiry and download .................................................................... E-71
Test selection inquiry for routine rack ........................................................... E-71
Test selection inquiry for STAT rack .............................................................. E-71
Routine rack (AL) with acknowledgement .................................................... E-72
Routine rack invalid test (ER) .......................................................................... E-72
Test selection inquiry no sample found ......................................................... E-73
Test selection inquiry with a sequence number ............................................ E-73
Patient result upload messages .............................................................................. E-74
Single patient result upload .............................................................................. E-74
Batch upload all previous results ..................................................................... E-74
Batch upload all current results ....................................................................... E-76
Batch upload of current results sample short ................................................ E-76
No result as sample short .................................................................................. E-77
Result outside user range .................................................................................. E-77
Result outside normal range ............................................................................ E-77
Result below level of detection ......................................................................... E-78
Quality control result upload messages ................................................................ E-79
Batch QC from C-module ................................................................................ E-79
Batch QC from C-module standby bottle ...................................................... E-79
Realtime QC from C-module ........................................................................... E-80
Realtime QC from C-module standby bottle ................................................. E-80
QC results from E-module ............................................................................... E-80
Calibration result upload messages ....................................................................... E-81
C-module calibration results ............................................................................ E-81
ISE-module calibration results ........................................................................ E-82
E-module calibration results ............................................................................ E-83
Masking messages .................................................................................................... E-83
Successful masking message ............................................................................. E-83
Unsuccessful masking message ....................................................................... E-84
Result requests from the host ................................................................................. E-84
Request for all results ........................................................................................ E-84
Request for active results .................................................................................. E-85
No results found ................................................................................................ E-85
Sample not found ............................................................................................... E-86
Result request with a sequence number ......................................................... E-86
Order requests from the host ................................................................................. E-87
Request for all tests ............................................................................................ E-87

Roche Diagnostics
E-54 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument

Request for open tests ....................................................................................... E-87

No tests found .................................................................................................... E-87
Sample not found ............................................................................................... E-88
Order request with a sequence number .......................................................... E-88

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-55
15 Communication examples cobas® 8000 data manager
cobas® 8000 instrument

Roche Diagnostics
E-56 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument Example communication trace files

Example communication trace files

This section gives example trace files of messages between data manager and the host.
This shows the precise content of the messages sent, including the control characters.

ASTM trace files

This section gives examples of ASTM messages between data manager and the host.

Low level trace file

This section shows a low-level ASTM trace file, showing the control characters, the
acknowledgement handling, and the frames.
c8kDM 18:46:29,145 [ENQ]
HOST 18:46:29,176 [ACK]
c8kDM 18:46:29,317 [STX]1H|\^&|116486||cobas 8000^1.02|||||host|RS
UPL|P|1|20101020184623|[CR]P|1||||^||||[CR]O|1|
10002|0^10002^2^^S4^SC^not|^^^870^1\^^^880^1\^^
^890^1|R|20101016120539|20101016120539||||N||||
4||||||||||F|[CR]C|1|I|^^^^|G|[CR]R|1|^^^870/1/
not|17.30|g/dL|^TECH\^N[ETB]E9[CR][LF]
HOST 18:46:29,333 [ACK]
c8kDM 18:46:29,411 [STX]2ORM\^CRIT\^USER|||F||bmserv^SYSTEM|200912
18164600|20101016120550|c502^1^MU1#c502#2#1^9^0
|[CR]C|1|I|0|I|[CR]R|2|^^^880/1/not|1.50|g/dL|^
TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20091
218164600|20101016120552|c502^1^MU1#c502#2#1^9^
0|[CR]C|1|I|0|I|[CR]R|3[ETB]BA[CR][LF]
HOST 18:46:29,411 [ACK]
c8kDM 18:46:29,426 [STX]3|^^^890/1/not|8.67|%|^TECH\^NORM\^CRIT\^U
SER|||F||bmserv^SYSTEM||20101016120552|c502^1^M
U1#c502#2#1^9^0|[CR]C|1|I|0|I|[CR]L|1|N|[CR][ET
X]F1[CR][LF]
HOST 18:46:29,426 [ACK]
c8kDM 18:46:29,442 [EOT]

Figure E-1 Low-level trace: the message is sent in as few 240-byte frames as possible.

Each frame has a maximum of 240 bytes for text, plus 7 bytes for frame control
characters. The message is sent in as few frames as possible, so the last may be less
than 240 bytes.
The message is sent as unicode UTF-8, so unicode characters may occupy more than
one byte. Also, one unicode character might be split between two frames.
For readability the rest of the examples are displayed on a record level, and not on the
frame level.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-57
15 Communication examples cobas® 8000 data manager
ASTM trace files cobas® 8000 instrument

Test selection inquiry from data manager

This section shows examples of ASTM test selection enquiries sent from the data
manager, and the host’s test selection downloads in reply.

Routine test selection inquiry and download

This section shows an example of an ASTM test selection inquiry for a routine
sample sent from the data manager, and the host’s test selection download in reply.
DM:
H|\^&|15220||cobas 8000^1.02|||||host|TSREQ|P|1|20101020091706|
Q|1|^^321070^0^50094^2^^S1^SC^R1||ALL|||||||R|O|
L|1|N|

Host:
H|\^&|||ASTM-Host^V 6.8g|||||cobas 8000^1.02|TSDWN|P|1|20101020100000
P|1||PatID3||Parker^Bill||19881231|M
O|1|321070|0^50094^2^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|R||||||A||||1||||||||||O
C|1|L|Comm1^Comm2^Comm3^Comm4^Comm5|G
L|1|N

Figure E-2 Routine test selection inquiry and download

STAT sample test selection inquiry and download

This section shows an example of an ASTM test selection inquiry for a STAT sample,
and the host’s test selection download.
DM:
H|\^&|15223||cobas 8000^1.02|||||host|TSREQ|P|1|20101020091724|
Q|1|^^321040^0^40002^3^^S1^SC^R1||ALL|||||||S|O|
L|1|N|

Host:
H|\^&|||ASTM-Host^V 6.8g|||||cobas 8000^1.02|TSDWN|P|1|20101020100000
P|1||PatID3||Parker^Bill||19881231|M
O|1|321040|0^40002^3^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|S||||||A||||1||||||||||O
C|1|L|Comm1^Comm2^Comm3^Comm4^Comm5|G
L|1|N

Figure E-3 STAT sample test selection inquiry and download

Roche Diagnostics
E-58 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument ASTM trace files

Test selection inquiry and download if no sample found

This section shows an example of an ASTM test selection inquiry for a sample, and
the host’s test selection download, saying that it could not find the sample.
DM:
H|\^&|15220||cobas 8000^1.02|||||host|TSREQ|P|1|20101020091706|
Q|1|^^321071^0^50094^1^^S1^SC^R1||ALL|||||||R|O|
L|1|N|

Host:
H|\^&|||ASTM-Host^V 6.8g|||||cobas 8000^1.02|TSDWN|P|1|20101020100000
P|1|
O|1|321071|0^50094^1^^S1^SC||R||||||A||||1||||||||||O
L|1|N

Figure E-4 Test selection inquiry and download if no sample found

Send patient demographic data if sample found with no tests ordered

Take care in the situation where the data manager sends a test selection query, but the
CAUTION host has no patient demographic information nor tests for the sample, although it
recognizes the sample ID. When the host sends its test selection download, the data
manager updates the patient demographic information along with the tests. Therefore, if
the host sends no patient demographic information, the data manager might lose its
current patient demographic data.
In this case, the host should send a normal test selection download, with full patient
information, and comments etc., but no testcodes.
For examples of normal test selections, see Routine test selection inquiry and download on
page E-58 and STAT sample test selection inquiry and download on page E-58.

Test selection inquiry with sequence number

This section shows an example of an ASTM test selection inquiry for a sample,
identified by sequence number.
DM:
H|\^&|563017||cobas 8000^1.02|||||host|TSREQ|P|1|20110720151610|
Q|1|^^^1013^50101^3^^S1^SC^R1||ALL|||||||R|O|
L|1|N|

Host:
H|\^&|||ASTM-Host^V 6.8g|||||cobas 8000^1.02|TSDWN|P|1|20110715093311
P|1||M820101K||Froihofer^Kahila||19831213|F
O|1||1013^50101^3^^S1^SC^not|^^^8571^1\^^^8413^1\^^^8706^1\|R|20110715093311|20110715093311||||A|||
|1||||||||||O
C|1|L|Comm1^Comm2^Comm3^Comm4^Comm5|G
L|1|N

Figure E-5 Test selection inquiry for a sample identified by sequence number

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-59
15 Communication examples cobas® 8000 data manager
ASTM trace files cobas® 8000 instrument

Patient result upload messages

This section shows examples of ASTM patient result upload messages.

Realtime ISE result upload

This section shows an example of an ASTM realtime result upload from an ISE
module.
H|\^&|12927||cobas 8000^1.02|||||host|RSUPL|P|1|20101018185138|
P|1||||^||||
O|1|321088|0^50022^5^^S1^SC^not|^^^990^1|R|20101016183237|20101016183237||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^990/1/not|0.68|mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20101018185121|201010181851
36|ISE^2^MU1#ISE#1#2^4^128|
C|1|I|23^ISE Sample range over|I|
L|1|N|

Figure E-6 Realtime ISE result upload

ISE result upload - sample short

This section shows an example of an ASTM result upload, stating that the result value
is missing because the sample is short.
H|\^&|12835||cobas 8000^1.02|||||host|RSUPL|P|1|20101018183109|
P|1||||^||||
O|1|321042|0^50011^4^^S1^SC^not|^^^991^1|R|20101014115322|20101006162241||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^991/1/not| |mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20101018183051|201010181
83106|ISE^1^MU1#ISE#1#1^3^126|
C|1|I|3^Sample short|I|
L|1|N|

Figure E-7 ISE result upload, result missing as sample is short

C-module result upload with no flag

This section shows an example of an ASTM result upload from a C-module with no
alarm flag.
H|\^&|13815||cobas 8000^1.02|||||host|RSUPL|P|1|20101019100042|
P|1||||^||||
O|1|321042|0^50011^4^^S1^SC^not|^^^8717^1|R|20101019094904|20101019094904||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8717/1/not|4.28|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20101019095027|20101019100
040|c701^1^MU1#c701#1#1^6^77|
C|1|I|0|I|
L|1|N|
Figure E-8 C-module result upload with no flag

Roche Diagnostics
E-60 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument ASTM trace files

Glucose result with alarm flag

This section shows an example of an ASTM result upload from a C-module with an
alarm flag.
H|\^&|13667||cobas 8000^1.02|||||host|RSUPL|P|1|20101019092637|
P|1||||^||||
O|1|321057|0^50007^1^^S1^SC^not|^^^8717^1|R|20101019085027|20101019085027||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8717/1/not|-0.01|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20101019091622|2010101909
2635|c701^1^MU1#c701#1#1^6^77|
C|1|I|27^PANIC value over (lower) Technical Limit|I|
L|1|N|

Figure E-9 Glucose result with alarm flag

Batch upload of current results

This section shows an example of an ASTM batch result upload showing current
results only.
H|\^&|15326||cobas 8000^1.02|||||host|RSUPL|P|1|20101020095834|
P|1||PatID1||Smith^Alan||19451231|M|
O|1|321015|0^50071^1^^S1^SC^not|^^^990^1\^^^991^1\^^^8717^1|R|20101019174209|20101019174209||||N|||
|1||||||||||F|
C|1|I|C1^C2^C3^C4^C5|G|
R|1|^^^990/1/not|0.75|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20101020095735|201010200
95751|ISE^1^MU1#ISE#1#1^3^125|
C|1|I|23^ISE Sample range over|I|
R|2|^^^991/1/not|297.28|mmol/L|^TECH\^NORM\^CRIT\<
0^USER|||F||bmserv^SYSTEM|20101020095735|20101020095751|ISE^1^MU1#ISE#1#1^3^126|
C|1|I|23^ISE Sample range over|I|
R|3|^^^8717/Inc/not|-0.02|mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20101019175614|20101019
180627|c701^1^MU1#c701#1#1^6^77|
C|1|I|27^PANIC value over (lower) Technical Limit|I|
L|1|N|

Figure E-10 Batch upload of current results

Batch upload of current results -sample short

This section shows an example of an ASTM batch result upload stating that the result
value is missing because the sample is short.
H|\^&|12811||cobas 8000^1.02|||||host|RSUPL|P|1|20101018182329|
P|1||||^||||
O|1|321042|0^50011^4^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|R|20101014115322|20101006162241||||N||||
1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^989/1/not| |mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20101018173814|201010181
73829|ISE^1^MU1#ISE#1#1^3^124|
C|1|I|3^Sample short|I|
R|2|^^^990/1/not| |mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20101018173814|201010181
73829|ISE^1^MU1#ISE#1#1^3^125|
C|1|I|3^Sample short|I|
R|3|^^^991/1/not| |mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20101018173814|201010181
73829|ISE^1^MU1#ISE#1#1^3^126|
C|1|I|3^Sample short|I|
L|1|N|
Figure E-11 Batch upload of current results
Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-61
15 Communication examples cobas® 8000 data manager
ASTM trace files cobas® 8000 instrument

Batch upload all previous results

This section shows an example of an ASTM batch upload of all previous results.
H|\^&|15325||cobas 8000^1.02|||||host|RSUPL|P|1|20101020095830|
P|1||PatID1||Smith^Alan||19451231|M|
O|1|321015|0^50071^1^^S1^SC^not|^^^990^1\^^^991^1\^^^8717^1|R|20101019174209|20101019174209||||N|||
|1||||||||||F|
C|1|I|C1^C2^C3^C4^C5|G|
R|1|^^^990/1/not|0.91|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20101019174423|201010191
74439|ISE^2^MU1#ISE#1#2^4^128|
C|1|I|23^ISE Sample range over|I|
R|2|^^^990/1/not|0.70|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||C||bmserv^SYSTEM|20101019174459|201010191
74515|ISE^1^MU1#ISE#1#1^3^125|
C|1|I|23^ISE Sample range over|I|
R|3|^^^990/1/not|0.75|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20101020095735|201010200
95751|ISE^1^MU1#ISE#1#1^3^125|
C|1|I|23^ISE Sample range over|I|
R|4|^^^991/1/not|252.89|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20101019174347|2010101
9174403|ISE^1^MU1#ISE#1#1^3^126|
C|1|I|23^ISE Sample range over|I|
R|5|^^^991/1/not|256.84|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||C||bmserv^SYSTEM|20101019174423|2010101
9174439|ISE^2^MU1#ISE#1#2^4^129|
C|1|I|23^ISE Sample range over|I|
R|6|^^^991/1/not|297.28|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20101020095735|2010102
0095751|ISE^1^MU1#ISE#1#1^3^126|
C|1|I|23^ISE Sample range over|I|
R|7|^^^8717/1/not|-0.04|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20101019174533|2010101917
5547|c701^1^MU1#c701#1#1^6^77|
C|1|I|27^PANIC value over (lower) Technical Limit|I|
R|8|^^^8717/Inc/not|-0.02|mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20101019175614|20101019
180627|c701^1^MU1#c701#1#1^6^77|
C|1|I|27^PANIC value over (lower) Technical Limit|I|
L|1|N|
Figure E-12 Batch upload all previous results

Result below normal range

This section shows an example of an ASTM result upload below the normal reference
range.
H|\^&|10252||cobas|^|8000^1.02|||||host|RSUPL|P|1|20100610200938|
P|1||ES06516622121998||Rister^Wolfgang||19330813|M|
O|1|123|0^50063^2^^S1^SC^not|^^^989^1\^^^991^1\^^^8717^1|R|20100604235148|20100604235148||||N||||1|
|||||||||F|
C|1|I|^^^^|G|
R|1|^^^989/1/not|2.1|mmol/L|^TECH\9 - 144^NORM\^CRIT\^USER|L||F||bmserv^SYSTEM|20100621084348|20100
621084404|ISE^1^MU1#ISE#1#1^3^28|
C|1|I|0|I|
R|2|^^^991/1/not|1.1|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20100621084348|2010062108440
4|ISE^1^MU1#ISE#1#1^3^28|
C|1|I|0|I|
R|3|^^^8717/1/not|14.57|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20100621085921|2010062109
0935|c701^2^MU1#c701#1#2^7^168|
C|1|I|0|I|
L|1|N|

Figure E-13 Result below normal reference range

Roche Diagnostics
E-62 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument ASTM trace files

Result below level of detection

This section shows an example of an ASTM result upload below the EP-17A level of
detection.
H|\^&|10256||cobas|^|8000^1.02|||||host|RSUPL|P|1|20100610201014|
P|1||ES06516622121998||Rister^Wolfgang||19330813|M|
O|1|123|0^50063^2^^S1^SC^not|^^^989^1\^^^991^1\^^^8717^1|R|20100604235148|20100604235148||||N||||1|
|||||||||F|
C|1|I|^^^^|G|
R|1|^^^989/1/not|0.1|mmol/L|^TECH\9 - 144^NORM\^CRIT\^USER|LoD||F||bmserv^SYSTEM|20100621084348|201
00621084404|ISE^1^MU1#ISE#1#1^3^28|
C|1|I|0|I|
R|2|^^^991/1/not|1.1|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20100621084348|2010062108440
4|ISE^1^MU1#ISE#1#1^3^28|
C|1|I|0|I|
R|3|^^^8717/1/not|14.57|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20100621085921|2010062109
0935|c701^2^MU1#c701#1#2^7^168|
C|1|I|0|I|
L|1|N|

Figure E-14 Results upload below level of detection

Result with sample identified by sequence number

This section shows an example of an ASTM result upload with the sample identified
by sequence number.
H|\^&|563030||cobas 8000^1.02|||||host|RSUPL|P|1|20110720152309|
P|1||M820101K||Froihofer^Kahila||19831213|F|
O|1||1013^50101^3^^S1^SC^not|^^^8413^1\^^^8571^1\^^^8706^1|R|20110715093311|20110715093311||||N||||
1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8413/1/not|15|g/dL|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20110715084600|20110715084600|
c702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|
R|2|^^^8571/1/not|16|U/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20110715084600|20110715084600|c
702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|
R|3|^^^8706/1/not|17|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20110715084600|2011071508460
0|c702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|
L|1|N|

Figure E-15 Results upload with sample identified by sequence number

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-63
15 Communication examples cobas® 8000 data manager
ASTM trace files cobas® 8000 instrument

Quality control uploads

This section shows examples of ASTM quality control result uploads.

Realtime quality control upload

This section shows an example of an ASTM realtime quality control upload.
H|\^&|13772||cobas 8000^1.02|||||host|RSUPL^REAL|P|1|20101019094737|
P|1|
O|1|PNU^150403^2|0^30005^1^^QC^SC^not|^^^8685^1|R||||||Q||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8685/1/not|48|U/L||||F||bmserv^SYSTEM|20101019093722|20101019094737|c701^1^MU1#c701#1#1^6^75
^Current|
C|1|I|0|I|
L|1|N|

Figure E-16 Realtime quality control upload

Realtime quality control upload with a standby bottle

This section shows an example of an ASTM realtime quality control upload measured
from the standby bottle.
H|\^&|13791||cobas 8000^1.02|||||host|RSUPL^REAL|P|1|20101019094918|
P|1|
O|1|PNU^150403^2|0^30005^1^^QC^SC^not|^^^8685^1|R||||||Q||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8685/1/not|44|U/L||||F||bmserv^SYSTEM|20101019093903|20101019094918|c701^1^MU1#c701#1#1^6^76
^Standby^1|
C|1|I|0|I|
L|1|N|

Figure E-17 Realtime quality control upload from the standby bottle

Batch quality control upload

This section shows an example of an ASTM batch quality control upload.
H|\^&|14262||cobas 8000^1.02|||||host|RSUPL^BATCH|P|1|20101019124105|
P|1|
O|1|PNU^150403^2|0^30005^1^^QC^SC^not|^^^8685^1|R||||||Q||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8685/1/not|47|U/L||||F||bmserv^SYSTEM|20101019111853|20101019112908|c701^1^MU1#c701#1#1^6^75
^Current|
C|1|I|0|I|
L|1|N|
Figure E-18 Batch quality control upload

Roche Diagnostics
E-64 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument ASTM trace files

Batch quality control upload with a standby bottle

This section shows an example of an ASTM batch quality control upload measured
from the standby bottle.
H|\^&|14261||cobas 8000^1.02|||||host|RSUPL^BATCH|P|1|20101019124103|
P|1|
O|1|PNU^150403^2|0^30005^1^^QC^SC^not|^^^8685^1|R||||||Q||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8685/1/not|48|U/L||||F||bmserv^SYSTEM|20101019111857|20101019112911|c701^1^MU1#c701#1#1^6^76
^Standby^1|
C|1|I|0|I|
L|1|N|

Figure E-19 Batch quality control upload from the standby bottle

Calibration result uploads

This section shows examples of ASTM calibration result uploads.

C-module calibration result upload

This section shows example of ASTM C-module calibration result uploads.
H|\^&|14273||cobas 8000^1.02|||||host|PCUPL^REAL|P|1|20101019091421|
M|1|PCR|bmserv|^^^8685|MU1#c701#1#1|16|0|22851^4^22866^2^0^\24786^-361^24149^-362^0^\^^^^^\^^^^^\^^
^^^\^^^^^|
L|1|N|

Figure E-20 C-module calibration result upload

H|\^&|14274||cobas 8000^1.02|||||host|PCUPL^REAL|P|1|20101019091425|
M|1|PCR|bmserv|^^^8685|MU1#c701#1#1|16|0|22045^4^22237^6^0^\24134^-372^23966^-361^0^\^^^^^\^^^^^\^^
^^^\^^^^^|
L|1|N|

Figure E-21 C-module calibration result upload

H|\^&|14275||cobas 8000^1.02|||||host|PCUPL^REAL|P|1|20101019091432|
M|1|PCR|bmserv|^^^8717|MU1#c701#1#1|16|0|956^31^962^40^0^\8100^6814^8147^6849^0^\^^^^^\^^^^^\^^^^^\
^^^^^|
L|1|N|

Figure E-22 C-module calibration result upload

ISE-module calibration result upload

This section shows examples of ASTM ISE-module calibration result uploads.
H|\^&|14274||cobas 8000^1.02|||||host|ICUPL^REAL|P|1|20101020110002|
M|1|ICR|bmserv|MU1#ISE#1#1|Valid|Valid|Valid|0^0^0^0^0^0^0^0^0^0|0^0^0^0^0^0^0^0^0^0|0^0^0^0^0^0^0^
0^0^0|-33.0^-37.9^-30.4^-33.2^60.0^144.59^143.56^0.0^60.2^-0.56|-34.9^-48.9^-27.3^-37.8^58.7^5.19^4
.64^0.0^59.1^-0.05|137.3^141.6^132.8^136.8^-50.0^97.42^99.75^0.0^-50.3^1.25|
L|1|N|

Figure E-23 ISE-module calibration result upload

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-65
15 Communication examples cobas® 8000 data manager
ASTM trace files cobas® 8000 instrument

H|\^&|14275||cobas 8000^1.02|||||host|ICUPL^REAL|P|1|20101020110008|
M|1|ICR|bmserv|MU1#ISE#1#2|Valid|Valid|Valid|0^0^0^0^0^0^0^0^0^0|0^0^0^0^0^0^0^0^0^0|0^0^0^0^0^0^0^
0^0^0|-37.9^-42.6^-35.3^-38.0^58.4^144.15^143.45^0.0^59.4^-0.45|-38.7^-51.9^-31.2^-41.3^56.3^5.15^4
.63^0.0^57.3^-0.04|131.3^134.6^126.2^130.1^-47.7^93.93^99.57^0.0^-48.3^1.43|
L|1|N|
Figure E-24 ISE-module calibration result upload

E-module calibration result upload

This section shows examples of ASTM E-module calibration result uploads.
H|\^&|14276||cobas 8000^1.02|||||host|ECUPL^REAL|P|1|20101018175819|
M|1|ECR|bmserv|^^^1|LotCalibration|MU1#e602#2#1|157328||0|158941|O|I^O^\M^O^\S^O^\R^1.074^\D^O^\L^^
\F^O^\Y^O^\B^O^|936.337^888.767\39609.680^39716.950|||||20101018175819|
L|1|N|

Figure E-25 E-module calibration result upload

H|\^&|14277||cobas 8000^1.02|||||host|ECUPL^REAL|P|1|20101018175844|
M|1|ECR|bmserv|^^^1|LotCalibration|MU1#e602#2#2|157328||0|158941|O|I^O^\M^O^\S^O^\R^1.064^\D^O^\L^^
\F^O^\Y^O^\B^O^|839.413^797.173\38293.490^38596.120|||||20101018175844|
L|1|N|

Figure E-26 E-module calibration result upload

Result request from host and the data manager result upload

This section shows examples of ASTM result requests from the host and the data
manager’s result upload in reply.

Request for currently active results

This section shows an example ASTM result request from the host for currently
results for a sample, and the data manager’s result upload.
Host:
H|\^&|12345||cobas 8000^1.02|||||host|RSREQ|P|1|20101020075900|
Q|1|^S1^321015||||||||||F|
L|1|N|

DM:
H|\^&|15126||cobas 8000^1.02|||||host|RSUPL^BATCH|P|1|20101020090056|
P|1||PatID1||Smith^Alan||19451231|M|
O|1|321015|0^50071^1^^S1^SC^not|^^^8717^1|R|20101019174209|20101019174209||||N||||1||||||||||F|
C|1|I|C1^C2^C3^C4^C5|G|
R|1|^^^8717/Inc/not|-0.02|mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20101019175614|20101019
180627|c701^1^MU1#c701#1#1^6^77|
C|1|I|27^PANIC value over (lower) Technical Limit|I|
L|1|N|

Figure E-27 Result request from the host for currently results, and the data manager’s result upload

Roche Diagnostics
E-66 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument ASTM trace files

Request for all results

This section shows an example of an ASTM result request from the host for all results
for a sample, and the data manager’s result upload
Host:
H|\^&|12345||cobas 8000^1.02|||||host|RSREQ|P|1|20101020075900|
Q|1|^S1^321015|||||||||||
L|1|N|

DM:
H|\^&|15123||cobas 8000^1.02|||||host|RSUPL^BATCH|P|1|20101020090031|
P|1||PatID1||Smith^Alan||19451231|M|
O|1|321015|0^50071^1^^S1^SC^not|^^^990^1\^^^991^1\^^^8717^1|R|20101019174209|20101019174209||||N|||
|1||||||||||F|
C|1|I|C1^C2^C3^C4^C5|G|
R|1|^^^990/1/not|0.91|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20101019174423|20101019
174439|ISE^2^MU1#ISE#1#2^4^128|
C|1|I|23^ISE Sample range over|I|
R|2|^^^990/1/not|0.70|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||C||bmserv^SYSTEM|20101019174459|20101019
174515|ISE^1^MU1#ISE#1#1^3^125|
C|1|I|23^ISE Sample range over|I|
R|3|^^^991/1/not|252.89|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20101019174347|2010101
9174403|ISE^1^MU1#ISE#1#1^3^126|
C|1|I|23^ISE Sample range over|I|
R|4|^^^991/1/not|256.84|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||C||bmserv^SYSTEM|20101019174423|2010101
9174439|ISE^2^MU1#ISE#1#2^4^129|
C|1|I|23^ISE Sample range over|I|
R|5|^^^8717/1/not|-0.04|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20101019174533|2010101917
5547|c701^1^MU1#c701#1#1^6^77|
C|1|I|27^PANIC value over (lower) Technical Limit|I|
R|6|^^^8717/Inc/not|-0.02|mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20101019175614|20101019
180627|c701^1^MU1#c701#1#1^6^77|
C|1|I|27^PANIC value over (lower) Technical Limit|I|
L|1|N|
Figure E-28 Result request from the host for all results for a sample

Result request but no results

This section shows an example of an ASTM result request from the host, where the
data manager does not have any results for the sample.
Host:
H|\^&|12345||cobas 8000^1.02|||||host|RSREQ|P|1|20101020075900|
Q|1|^S1^321016|||||||||||
L|1|N|

DM:
<No Reply>

Figure E-29 Result request but no reply as no results found

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-67
15 Communication examples cobas® 8000 data manager
ASTM trace files cobas® 8000 instrument

Result request but sample not found

This section shows an example of an ASTM result request from the host, where the
data manager does not have record of the sample.
Host:
H|\^&|12345||cobas 8000^1.02|||||host|RSREQ|P|1|20101020075900|
Q|1|^S1^NOT_A_SAMPLE|||||||||||
L|1|N|

DM:
<No Reply>

Figure E-30 Result request but no reply as no sample found

Result request in with a sequence number

This section shows an example of an ASTM result request from the host, for the
sample with sequence number 1031.
Host:
H|\^&|12345||cobas 8000^1.02|||||host|RSREQ|P|1|20110711093355|
Q|1|^S1^^1031||||||||||F|
L|1|N|

DM:
H|\^&|564735||cobas 8000^1.02|||||host|RSUPL^BATCH|P|1|20110712112553|
P|1||M820101K||Froihofer^Kahila||19831213|F|
O|1||1013^50101^3^^S1^SC^not|^^^8413^1\^^^8571^1\^^^8706^1|R|20110711093311|20110711093311||||N||||
1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8413/1/not|15|g/dL|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20111212104600|20111212104600|
c702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|
R|2|^^^8571/1/not|16|U/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20111212104600|20111212104600|c
702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|
R|3|^^^8706/1/not|17|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20111212104600|2011121210460
0|c702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|
L|1|N|

Figure E-31 Result request with a sequence number

Roche Diagnostics
E-68 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument ASTM trace files

Order query from the host

This section shows examples of ASTM test selection queries (or order queries) from
the host to the data manager.

Order query for all tests

This section shows an example of an ASTM order query for all tests on a sample.
Host:
H|\^&|||cobas 8000^1.02|||||host|TSREQ|P|1|
Q|1|^S1^321015|||||||||||
L|1|N|

DM:
H|\^&|14997||cobas 8000^1.02|||||host|TSUPL|P|1|20101020081756|
P|1||PatID1||Smith^Alan||19451231|M|
O|1|321015||^^^990^1\^^^991^1\^^^8717^1|||||||O||||1||||||||||F|
C|1|I|C1^C2^C3^C4^C5|G|
L|1|N|

Figure E-32 Order query for all open tests

Order query for all open tests

This section shows an example of an ASTM order query for open tests on a sample.
Host:
H|\^&|||cobas 8000^1.02|||||host|TSREQ|P|1|
Q|1|^S1^321015||||||||||O|
L|1|N|

DM:
H|\^&|15002||cobas 8000^1.02|||||host|TSUPL|P|1|20101020082031|
P|1||PatID1||Smith^Alan||19451231|M|
O|1|321015||^^^990^1\^^^991^1|||||||O||||1||||||||||F|
C|1|I|C1^C2^C3^C4^C5|G|
L|1|N|

Figure E-33 Order query for all open tests

Order query but no open tests

This section shows an example of an ASTM order query for all open tests on a
sample, but the data manager does not have any open orders on the sample.
Host:
H|\^&|||cobas 8000^1.02|||||host|TSREQ|P|1|
Q|1|^S1^321016||||||||||O|
L|1|N|

DM:
H|\^&|15005||cobas 8000^1.02|||||host|TSUPL|P|1|20101020082222|
P|1||PatID1||Smith^Alan||19451231|M|
O|1|321016|||||||||O||||1||||||||||F|
C|1|I|^^^^|G|
L|1|N|

Figure E-34 Order query but no open tests

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-69
15 Communication examples cobas® 8000 data manager
ASTM trace files cobas® 8000 instrument

Order query but sample not found

This section shows an example of an ASTM order query for all open tests on a
sample, but the data manager does not have any record of the sample
Host:
H|\^&|||cobas 8000^1.02|||||host|TSREQ|P|1|
Q|1|^S1^NOT_EXISTING|||||||||||
L|1|N|

DM:
H|\^&|14980||cobas 8000^1.02|||||host|TSUPL|P|1|20101020081236|
P|1||||^||||
O|1|NOT_EXISTING|||||||||O||||1||||||||||F|
C|1|I|^^^^|G|
L|1|N|

Figure E-35 Order query but sample not found

Order query with sample identified by sequence number

This section shows an example of an ASTM order query for all open tests on a sample
identified by sequence number. Note that the order record, field 4 (O-4) is a simple
number field, containing the sequence number (1013).
Host:
H|\^&|||cobas 8000^1.02|||||host|TSREQ|P|1|
Q|1|^S1^^1013||||||||||O|
L|1|N|

DM:
H|\^&|563024||cobas 8000^1.02|||||host|TSUPL|P|1|20110720151956|
P|1||M820101K||Froihofer^Kahila||19831213|F|
O|1||1013|^^^8413^1\^^^8571^1\^^^8706^1|||||||O||||1||||||||||F|
C|1|I|Comm1^Comm2^Comm3^Comm4^Comm5|G|
L|1|N|

Figure E-36 Order query for a sample identified by sequence number

Roche Diagnostics
E-70 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument HL7 trace files

HL7 trace files

This section gives examples of HL7 messages between data manager and the host.

Test selection inquiry and download

In the examples in this section shows the data manager sends HL7 test selection
requests, and the host replies with test selection downloads.

Test selection inquiry for routine rack

This section shows an example of an HL7 test selection inquiry for a routine rack.
DM:
MSH|^~\&|cobas 8000||host||20101020091052||TSREQ|15161||2.5||||ER||UNICODE UTF-8|
QPD|TSREQ|15161|321070||50094|2||||S1|SC|R1|R|
RCP|I|1|R|

Host:
MSH|^~\&|host||cobas 8000||20090508135730||OML^O33|38749||2.5||||ER||UNICODE UTF-8
PID|1|PatID3|||Wood^Sara||19881231|F
SPM||321070||S1||not||||||||Comm1^Comm2^Comm3^Comm4^Comm5|||20101020122000||||||||||SC
SAC||||||||||50094|2
TQ1|1||||||||R
OBR|1|||990^|||||||A
TQ1|1||||||||R
OBR|2|||991^|||||||A
TQ1|1||||||||R
OBR|3|||8781^|||||||A
TQ1|1||||||||R
OBR|4|||8717^Inc|||||||A
Figure E-37 Test selection inquiry for routine rack

Test selection inquiry for STAT rack

This section shows an example of an HL7 test selection inquiry for a STAT rack.
DM:
MSH|^~\&|cobas 8000||host||20101020091110||TSREQ|15164||2.5||||ER||UNICODE UTF-8|
QPD|TSREQ|15164|321040||40002|3||||S1|SC|R1|S|
RCP|I|1|R|

Host:
MSH|^~\&|host||cobas 8000||20101020123900||OML^O33|38749||2.5||||ER||UNICODE UTF-8
PID|1|PatID3|||Wood^Sara||19881231|F
SPM||321040||S1||not||||||||Comm1^Comm2^Comm3^Comm4^Comm5|||20101020122000||||||||||SC
SAC||||||||||4000232
TQ1|1||||||||S
OBR|1|||990^|||||||A
TQ1|1||||||||S
OBR|2|||991^|||||||A
TQ1|1||||||||S
OBR|3|||8781^|||||||A

Figure E-38 Test selection inquiry for STAT rack

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-71
15 Communication examples cobas® 8000 data manager
HL7 trace files cobas® 8000 instrument

TQ1|1||||||||S
OBR|4|||8717^Inc|||||||A

Figure E-38 Test selection inquiry for STAT rack

Routine rack (AL) with acknowledgement

This section shows an example of an HL7 test selection inquiry for a routine sample,
with the test selection download. The host requests an acknowledgement (level AL)
and the data manager replies.
DM:
MSH|^~\&|cobas 8000||host||20101020091052||TSREQ|15161||2.5||||ER||UNICODE UTF-8|
QPD|TSREQ|15161|321070||50094|2||||S1|SC|R1|R|
RCP|I|1|R|

Host:
MSH|^~\&|host||cobas 8000||20090508135730||OML^O33|38777||2.5||||AL||UNICODE UTF-8
PID|1|PatID3|||Wood^Sara||19881231|F
SPM||321070||S1||not||||||||Comm1^Comm2^Comm3^Comm4^Comm5|||20101020122000||||||||||SC
SAC||||||||||50094|2
TQ1|1||||||||R
OBR|1|||990^|||||||A
TQ1|1||||||||R
OBR|2|||991^|||||||A
TQ1|1||||||||R
OBR|3|||8781^|||||||A
TQ1|1||||||||R
OBR|4|||8717^Inc|||||||A

DM:
MSH|^~\&|cobas 8000||host||20101020132118||ACK|15831||2.5||||NE||UNICODE UTF-8|
MSA|AA|38777||

Figure E-39 Routine rack (AL) with acknowledgement

Routine rack invalid test (ER)

This section shows an example of an HL7 test selection inquiry, and the host’s test
selection download. In this test selection download there is an invalid sample ID, and
the data manager replies with an acknowledgement that informs the host of the error.
DM:
MSH|^~\&|cobas 8000||host||20101020091052||TSREQ|15161||2.5||||ER||UNICODE UTF-8|
QPD|TSREQ|15161|321070||50094|2||||S1|SC|R1|R|
RCP|I|1|R|

Host:
MSH|^~\&|host||cobas 8000||20090508135730||OML^O33|38777||2.5||||ER||UNICODE UTF-8
PID|1|PatID3|||Wood^Sara||19881231|F
SPM||321070||S1||not||||||||Comm1^Comm2^Comm3^Comm4^Comm5|||20101020122000||||||||||SC
SAC||||||||||50094|2
TQ1|1||||||||R
OBR|1|||990^|||||||A
TQ1|1||||||||R
OBR|2|||991^|||||||A
TQ1|1||||||||R
OBR|3|||8781^|||||||A

Figure E-40 Routine rack invalid test (ER)

Roche Diagnostics
E-72 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument HL7 trace files

TQ1|1||||||||R
OBR|4|||INVALID^Inc|||||||A

DM:
MSH|^~\&|cobas 8000||host||20101020132233||ACK|15834||2.5||||NE||UNICODE UTF-8|
MSA|AE|38777|ORA-20001: Validation error|

Figure E-40 Routine rack invalid test (ER)

Test selection inquiry no sample found

This section shows an example of an HL7 test selection inquiry, but the host cannot
find the sample.
DM:
MSH|^~\&|cobas 8000||host||20101020091052||TSREQ|15167||2.5||||ER||UNICODE UTF-8|
QPD|TSREQ|15167|321071||50094|3||||S1|SC|R1|R|
RCP|I|1|R|

Host:
MSH|^~\&|host||cobas 8000||20090508135730||OML^O33|38749||2.5||||ER||UNICODE UTF-8
PID|1|
SPM||321071||S1|
SAC||||||||||50094|3

Figure E-41 Test selection inquiry no sample found

Send patient demographic data if sample found with no tests ordered

Take care in the situation where the data manager sends a test selection query, but the
CAUTION host has no patient demographic information nor tests for the sample, although it
recognizes the sample ID. When the host sends its test selection download, the data
manager updates the patient demographic information along with the tests. Therefore, if
the host sends no patient demographic information, the data manager might lose its
current patient demographic data.
In this case, the host should send a normal test selection download, with full patient
information, and comments etc., but no testcodes.
For examples of normal test selections, see Routine test selection inquiry and download on
page E-58 and STAT sample test selection inquiry and download on page E-58.

Test selection inquiry with a sequence number

This section shows an example of an HL7 test selection inquiry, when the sample is
identified by sequence number.
DM:
MSH|^~\&|cobas 8000||host||20110720154106||TSREQ|563067||2.5||||ER||UNICODE UTF-8|
QPD|TSREQ|563067|^1031||50203|3||||S1|SC|R1|R|
RCP|I|1|R|

Host:
MSH|^~\&|host||c8000DM||20110715081133||OML^O33|227442||2.5||||ER||UNICODE UTF-8
PID|1|M820092K|||Muller^Urs||19730416|F
SPM||^1031||S1||not|||||P|||^^^^|||20110715085411||||||||||SC
SAC||||||||||50203|3

Figure E-42 Test selection inquiry with sample identified by sequence number

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-73
15 Communication examples cobas® 8000 data manager
HL7 trace files cobas® 8000 instrument

TQ1|1||||||||R
OBR|1|||8571^|||||||A
TQ1|1||||||||R
OBR|2|||8413^|||||||A
TQ1|1||||||||R
OBR|3|||8706^|||||||A

Figure E-42 Test selection inquiry with sample identified by sequence number

Patient result upload messages

In the examples in this section the data manager uploads HL7 patient results.

Single patient result upload

This section shows an example of a single HL7 patient result upload.
Note that the result abnormal flag is blank as there is no reference range defined.
MSH|^~\&|cobas 8000||host||20101019101825||OUL^R22|13890||2.5||||ER||UNICODE UTF-8|
PID|1||||^||||
SPM||321042||S1||not|||||P|||^^^^|||20101019094904||||||||||SC|
SAC||||||||||50011|4|
OBR|1|||8685|
TQ1|1||||||||R|
OBX|1||8685||47|U/L|^TECH~^NORM~^CRIT~^USER||||F|||20101019100810|bmserv^SYSTEM||75|c701^1^MU1#c701
#1#1^6|20101019101824|
TCD|8685|1|
SID|8685^^564957^R1^9^0|616478|924|
SID|8685^^564957^R3^9^0|616478|924|
NTE|1|I|0|I|

Figure E-43 Single patient result upload

Batch upload all previous results

This section show a batch upload of all previous results for a sample.
Note that the result abnormal flag is blank as there is no reference range defined.
MSH|^~\&|cobas 8000^1.02||host||20101020111635||OUL^R22|15593||2.5||||ER||UNICODE UTF-8|
PID|1|PatID1|||Smith^Alan||19451231|M|
SPM||321015||S1||not|||||P|||C1^C2^C3^C4^C5|||20101019174209||||||||||SC|
SAC||||||||||50071|1|
OBR|1|||990|
TQ1|1||||||||R|
OBX|1||990||0.91|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||F|||20101019174423|bmserv^SYSTEM||128|ISE^2^M
U1#ISE#1#2^4|20101019174439|
TCD|990|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|2|||990|
TQ1|1||||||||R|
OBX|2||990||0.70|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||20101019174459|bmserv^SYSTEM||125|ISE^1^M
U1#ISE#1#1^3|20101019174515|
TCD|990|1|
NTE|1|I|23^ISE Sample range over|I|

Figure E-44 Batch upload all previous results

Roche Diagnostics
E-74 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument HL7 trace files

OBR|3|||990|
TQ1|1||||||||R|
OBX|3||990||0.75|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||F|||20101020095735|bmserv^SYSTEM||125|ISE^1^M
U1#ISE#1#1^3|20101020095751|
TCD|990|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|4|||990|
TQ1|1||||||||R|
OBX|4||990||0.99|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||20101020095905|bmserv^SYSTEM||128|ISE^2^M
U1#ISE#1#2^4|20101020095921|
TCD|990|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|5|||991|
TQ1|1||||||||R|
OBX|5||991||252.89|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||F|||20101019174347|bmserv^SYSTEM||126|ISE^1
^MU1#ISE#1#1^3|20101019174403|
TCD|991|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|6|||991|
TQ1|1||||||||R|
OBX|6||991||256.84|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||20101019174423|bmserv^SYSTEM||129|ISE^2
^MU1#ISE#1#2^4|20101019174439|
TCD|991|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|7|||991|
TQ1|1||||||||R|
OBX|7||991||297.28|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||F|||20101020095735|bmserv^SYSTEM||126|ISE^1
^MU1#ISE#1#1^3|20101020095751|
TCD|991|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|8|||991|
TQ1|1||||||||R|
OBX|8||991||304.89|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||20101020095905|bmserv^SYSTEM||129|ISE^2
^MU1#ISE#1#2^4|20101020095921|
TCD|991|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|9|||8717|
TQ1|1||||||||R|
OBX|9||8717||-0.04|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20101019174533|bmserv^SYSTEM||77|c701^1^MU
1#c701#1#1^6|20101019175547|
TCD|8717|1|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
NTE|1|I|27^PANIC value over (lower) Technical Limit|I|
OBR|10|||8717|
TQ1|1||||||||R|
OBX|10||8717||-0.02|mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20101019175614|bmserv^SYSTEM||77|c701^1^M
U1#c701#1#1^6|20101019180627|
TCD|8717|Inc|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
NTE|1|I|27^PANIC value over (lower) Technical Limit|I|

Figure E-44 Batch upload all previous results

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-75
15 Communication examples cobas® 8000 data manager
HL7 trace files cobas® 8000 instrument

Batch upload all current results

This section shows a batch upload of all current results.
Note that the result abnormal flag is blank as there is no reference range defined.
MSH|^~\&|cobas 8000^1.02||host||20101020111632||OUL^R22|15591||2.5||||ER||UNICODE UTF-8|
PID|1|PatID1|||Smith^Alan||19451231|M|
SPM||321015||S1||not|||||P|||C1^C2^C3^C4^C5|||20101019174209||||||||||SC|
SAC||||||||||50071|1|
OBR|1|||990|
TQ1|1||||||||R|
OBX|1||990||0.99|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||20101020095905|bmserv^SYSTEM||128|ISE^2^M
U1#ISE#1#2^4|20101020095921|
TCD|990|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|2|||991|
TQ1|1||||||||R|
OBX|2||991||304.89|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||20101020095905|bmserv^SYSTEM||129|ISE^2
^MU1#ISE#1#2^4|20101020095921|
TCD|991|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|3|||8717|
TQ1|1||||||||R|
OBX|3||8717||-0.02|mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20101019175614|bmserv^SYSTEM||77|c701^1^MU
1#c701#1#1^6|20101019180627|
TCD|8717|Inc|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
NTE|1|I|27^PANIC value over (lower) Technical Limit|I|
Figure E-45 Batch upload all current results.

Batch upload of current results sample short

This section shows an example of an HL7 batch upload of current results, saying that
the measurement could not be done as the sample was short.
MSH|^~\&|cobas 8000||host||20101018174529||OUL^R22|12636||2.5||||ER||UNICODE UTF-8|
PID|1||||^||||
SPM||321042||S1||not|||||P|||^^^^|||20101006162241||||||||||SC|
SAC||||||||||50011|4|
OBR|1|||989|
TQ1|1||||||||R|
OBX|1||989|| |mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20101018173814|bmserv^SYSTEM||124|ISE^1^M
U1#ISE#1#1^3|20101018173829|
TCD|989|1|
NTE|1|I|3^Sample short|I|
OBR|2|||990|
TQ1|1||||||||R|
OBX|2||990|| |mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20101018173814|bmserv^SYSTEM||125|ISE^1^M
U1#ISE#1#1^3|20101018173829|
TCD|990|1|
NTE|1|I|3^Sample short|I|

Figure E-46 Batch upload of current results

Roche Diagnostics
E-76 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument HL7 trace files

OBR|3|||991|
TQ1|1||||||||R|
OBX|3||991|| |mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20101018173814|bmserv^SYSTEM||126|ISE^1^M
U1#ISE#1#1^3|20101018173829|
TCD|991|1|
NTE|1|I|3^Sample short|I|

Figure E-46 Batch upload of current results

No result as sample short

This section shows an example of an HL7 result message, where the measurement
could not be done as the sample was short.
MSH|^~\&|cobas 8000||host||20101018173833||OUL^R22|12624||2.5||||ER||UNICODE UTF-8|
PID|1||||^||||
SPM||321042||S1||not|||||P|||^^^^|||20101006162241||||||||||SC|
SAC||||||||||50011|4|
OBR|1|||991|
TQ1|1||||||||R|
OBX|1||991|| |mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20101018173814|bmserv^SYSTEM||126|ISE^1^M
U1#ISE#1#1^3|20101018173829|
TCD|991|1|
NTE|1|I|3^Sample short|I|

Figure E-47 No result as sample short

Result outside user range

This section shows an example of an HL7 patient result outside the user-defined
reference range.
MSH|^~\&|cobas 8000||host||20101018192600||OUL^R22|13338||2.5||||ER||UNICODE UTF-8|
PID|1||||^||||
SPM||321671||S1||not|||||P|||^^^^|||20101018191906||||||||||SC|
SAC||||||||||50054|5|
OBR|1|||991|
TQ1|1||||||||R|
OBX|1||991||202.52|mmol/L|^TECH~^NORM~^CRIT~< 1^USER||||F|||20101018192542|bmserv^SYSTEM||126|ISE^1
^MU1#ISE#1#1^3|20101018192558|
TCD|991|1|
NTE|1|I|0|I|

Figure E-48 Result outside user range

Result outside normal range

This section shows an example of an HL7 result upload below the normal reference
range.
MSH|^~\&|cobas 8000||host||20100609022505||OUL^R22|8277||2.5||||AL||UNICODE UTF-8|
PID|1|ES06516622121998|||Rister^Wolfgang||19330813|M|
SPM||123||S1||not|||||P|||^^^^|||20100604235148||||||||||SC|
SAC||||||||||50063|2|

Figure E-49 Result below normal reference range

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-77
15 Communication examples cobas® 8000 data manager
HL7 trace files cobas® 8000 instrument

OBR|1|||989|
TQ1|1||||||||R|
OBX|1||989||2.1|mmol/L|^TECH~9 - 144^NORM~^CRIT~^USER|L|||F|||20100621084348|bmserv^SYSTEM||28|ISE^
1^MU1#ISE#1#1^3|20100621084404|
TCD|989|1|
NTE|1|I|0|I|
TQ1|1||||||||R|
OBX|2||991||1.1|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20100621084348|bmserv^SYSTEM||28|ISE^1^MU1#IS
E#1#1^3|20100621084404|
TCD|991|1|
NTE|1|I|0|I|
OBR|3|||8717|
TQ1|1||||||||R|
OBX|3||8717||14.57|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20100621085921|bmserv^SYSTEM||168|c701^2^M
U1#c701#1#2^7|20100621090935|
TCD|8717|1|
NTE|1|I|0|I|

Figure E-49 Result below normal reference range

Result below level of detection

This section shows an example of an HL7 result upload below the EP-17A limit of
detection. (LoD)
MSH|^~\&|cobas 8000||host||20100609022105||OUL^R22|8267||2.5||||AL||UNICODE UTF-8|
PID|1|ES06516622121998|||Rister^Wolfgang||19330813|M|
SPM||123||S1||not|||||P|||^^^^|||20100604235148||||||||||SC|
SAC||||||||||50063|2|
OBR|1|||989|
TQ1|1||||||||R|
OBX|1||989||0.1|mmol/L|^TECH~12 - 144^NORM~^CRIT~^USER|LoD|||F|||20100621084348|bmserv^SYSTEM||28|I
SE^1^MU1#ISE#1#1^3|20100621084404|
TCD|989|1|
NTE|1|I|0|I|
OBR|2|||991|
TQ1|1||||||||R|
OBX|2||991||1.1|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20100621084348|bmserv^SYSTEM||28|ISE^1^MU1#IS
E#1#1^3|20100621084404|
TCD|991|1|
NTE|1|I|0|I|
OBR|3|||8717|
TQ1|1||||||||R|
OBX|3||8717||14.57|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20100621085921|bmserv^SYSTEM||168|c701^2^M
U1#c701#1#2^7|20100621090935|
TCD|8717|1|
NTE|1|I|0|I|

Figure E-50 HL7 results upload below level of detection

Roche Diagnostics
E-78 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument HL7 trace files

Quality control result upload messages

In the examples in this section shows the data manager uploads HL7 quality control
results.

Batch QC from C-module

This section shows an example of a batch HL7 quality control result from a C-
module.
MSH|^~\&|cobas 8000||host||20111119123938||OUL^R22^BATCH|14250||2.5||||ER||UNICODE UTF-8|
PID|1|
SPM||PNU^150403^2^20111121||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||30005|1|
OBR|1|||8717^|
TQ1|1||||||||R|
OBX|1||8717||4.30|mmol/L|4.5^TARGET~0.5^SD||||F|||20111119111900|bmserv^SYSTEM||77|c701^1^MU1#c701#
1#1^6^Current|20111119112915|
TCD|8717|1|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
NTE|1|I|0|I|

Figure E-51 Batch QC from C-module

Batch QC from C-module standby bottle

This section shows an example of a batch HL7 quality control result from a C-module
from a standby bottle.
MSH|^~\&|cobas 8000||host||20111119123853||OUL^R22^BATCH|14249||2.5||||ER||UNICODE UTF-8|
PID|1|
SPM||PNU^150403^2^20111121||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||30005|1|
OBR|1|||8685^|
TQ1|1||||||||R|
OBX|1||8685||48|U/L|50^TARGET~3^SD||||F|||20111119111857|bmserv^SYSTEM||76|c701^1^MU1#c701#1#1^6^St
andby^1|20111119112911|
TCD|8685|1|
SID|8685^^564957^R1^31^0|616478|923|
SID|8685^^564957^R3^31^0|616478|923|
NTE|1|I|0|I|

Figure E-52 Batch QC from C-module standby bottle

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-79
15 Communication examples cobas® 8000 data manager
HL7 trace files cobas® 8000 instrument

Realtime QC from C-module

This section shows an example of a realtime HL7 quality control result from a C-
module.
MSH|^~\&|cobas 8000||host||20111119112926||OUL^R22^REAL|14109||2.5||||ER||UNICODE UTF-8|
PID|1|
SPM||PPU^150415^3^20111121||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||30005|2|
OBR|1|||8717^|
TQ1|1||||||||R|
OBX|1||8717||12.44|mmol/L|12^TARGET~1^SD||||F|||20111119111911|bmserv^SYSTEM||77|c701^1^MU1#c701#1#
1^6^Current|20111119112926|
TCD|8717|1|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
NTE|1|I|0|I|

Figure E-53 Realtime QC from C-module

Realtime QC from C-module standby bottle

This section shows an example of a realtime HL7 quality control result from a C-
module from a standby bottle.
MSH|^~\&|cobas 8000||host||20111119112922||OUL^R22^REAL|14105||2.5||||ER||UNICODE UTF-8|
PID|1|
SPM||PPU^150415^3^20111121||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||30005|2|
OBR|1|||8685^|
TQ1|1||||||||R|
OBX|1||8685||121|U/L|127^TARGET~3^SD||||F|||20111119111907|bmserv^SYSTEM||76|c701^1^MU1#c701#1#1^6^
Standby^1|20111119112922|
TCD|8685|1|
SID|8685^^564957^R1^31^0|616478|923|
SID|8685^^564957^R3^31^0|616478|923|
NTE|1|I|0|I|

Figure E-54 Realtime QC from C-module standby bottle

QC results from E-module

This section shows examples of HL7 quality control results from an E-module.
MSH|^~\&|cobas 8000||host||20111119123353||OUL^R22^REAL|14226||2.5||||ER||UNICODE UTF-8|
PID|1|
SPM||PC U1 ^156227^156227^4^20111121||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||30001|1|
OBR|1|||1^|
TQ1|1||||||||R|
OBX|1||1||1.45|mIU/L|1.5^TARGET^0.15^SD||||F|||20111119121523|bmserv^SYSTEM||0|e602^1^MU1#e602#2#1^
9^Current|20111119123353|
TCD|1|1|
SID|1^^1^ASY^18^0|157328|62769|
NTE|1|I|0|I|

Figure E-55 QC result from an E-module

Roche Diagnostics
E-80 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument HL7 trace files

MSH|^~\&|cobas 8000||host||20111119123413||OUL^R22^REAL|14231||2.5||||ER||UNICODE UTF-8|

PID|1|
SPM||PC U1 ^156227^4^20111121||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||30001|1|
OBR|1|||1^|
TQ1|1||||||||R|
OBX|1||1||1.45|mIU/L|1.5^TARGET^0.15^SD||||F|||20111119121544|bmserv^SYSTEM||0|e602^2^MU1#e602#2#2^
10^Current|20111119123413|
TCD|1|1|
SID|1^^1^ASY^18^0|157328|62769|
NTE|1|I|0|I|

Figure E-56 QC result from an E-module

Calibration result upload messages

In the examples in this section the data manager uploads HL7 calibration results.

C-module calibration results

This section shows examples of an HL7 calibration results from a C-module.
MSH|^~\&|cobas 8000||host||20111119091421||OUL^R22^PCUPL|14262||2.5||||ER||UNICODE UTF-8|
SPM||1^999999^901^1^20111121|||||||||C^P|
OBR|1|||8685|
OBX|1||8685||0^3&4&22851&2&22866&|||0|||F||||bmserv||75|c701^1^MU1#c701#1#1^6^Current|2011111909142
1|
SID|8685^^^^2^1|231478|5|
SPM||2^153314^401^1^20111201|||||||||C^P|
OBR|2|||8685|
OBX|2||8685||0^-362&-361&24786&-362&24149&|||0|||F||||bmserv||75|c701^1^MU1#c701#1#1^6^Current|2011
1119091421|
SID|8685^^^^3^1|231480|9|

Figure E-57 C-module calibration result

MSH|^~\&|cobas 8000||host||20111119091432||OUL^R22^PCUPL|14264||2.5||||ER||UNICODE UTF-8|

SPM||1^999999^901^1^20111121||||||||||C^P|
OBR|1|||8717|
OBX|1||8717||0^36&31&956&40&962&|||0|||F||||bmserv||77|c701^1^MU1#c701#1#1^6^Current|20111119091432
|
SID|8717^^^^2^1|231478|5|
SPM||2^153314^401^1^20111121||||||||||C^P|
OBR|2|||8717|
OBX|2||8717||0^6832&6814&8100&6849&8147&|||0|||F||||bmserv||77|c701^1^MU1#c701#1#1^6^Current|201111
19091432|
SID|8717^^^^3^1|231480|9|

Figure E-58 C-module calibration result

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-81
15 Communication examples cobas® 8000 data manager
HL7 trace files cobas® 8000 instrument

ISE-module calibration results

This section shows examples of an HL7 calibration results from an ISE-module.
MSH|^~\&|cobas 8000||host||20101020110002||OUL^R22^ICUPL|14265||2.5||||ER||UNICODE UTF-8|
SPM|||||||||||C^I|
OBR|1|||989|
OBX|1||989||Type-A^0&0&0&0&0&0&0&0&0&0^-33.0&-37.9&-30.4&-33.2&60.0&144.59&143.56&0.0&60.2&-
0.56|||Valid|||F||||bmserv||130|ISE^1^MU1#ISE#1#1^3|20101020110002|
SID||
SPM|||||||||||C^I|
OBR|2|||990|
OBX|2||990||Type-A^0&0&0&0&0&0&0&0&0&0^-34.9&-48.9&-27.3&-37.8&58.7&5.19&4.64&0.0&59.1&-0.05|||Vali
d|||F||||bmserv||131|ISE^1^MU1#ISE#1#1^3|20101020110002|
SID||
SPM|||||||||||C^I|
OBR|3|||991|
OBX|3||991||Type-A^0&0&0&0&0&0&0&0&0&0^137.3&141.6&132.8&136.8&-50.0&97.42&99.75&0.0&-
50.3&1.25|||Valid|||F||||bmserv||132|ISE^1^MU1#ISE#1#1^3|20101020110002|
SID||
Figure E-59 ISE-module calibration result

MSH|^~\&|cobas 8000||host||20101020110008||OUL^R22^ICUPL|14266||2.5||||ER||UNICODE UTF-8|

SPM|||||||||||C^I|
OBR|1|||989|
OBX|1||989||Type-A^0&0&0&0&0&0&0&0&0&0^-37.9&-42.6&-35.3&-38.0&58.4&144.15&143.45&0.0&59.4&-
0.45|||Valid|||F||||bmserv||133|ISE^2^MU1#ISE#1#2^4|20101020110008|
SID||
SPM|||||||||||C^I|
OBR|2|||990|
OBX|2||990||Type-A^0&0&0&0&0&0&0&0&0&0^-38.7&-51.9&-31.2&-41.3&56.3&5.15&4.63&0.0&57.3&-
0.04|||Valid|||F||||bmserv||134|ISE^2^MU1#ISE#1#2^4|20101020110008|
SID||
SPM|||||||||||C^I|
OBR|3|||991|
OBX|3||991||Type-A^0&0&0&0&0&0&0&0&0&0^131.3&134.6&126.2&130.1&-47.7&93.93&99.57&0.0&-
48.3&1.43|||Valid|||F||||bmserv||135|ISE^2^MU1#ISE#1#2^4|20101020110008|
SID||

Figure E-60 ISE-module calibration result

Roche Diagnostics
E-82 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument HL7 trace files

E-module calibration results

This section shows examples of an HL7 calibration results from an E-module.
MSH|^~\&|cobas 8000||host||20111118175819||OUL^R22^ECUPL|14267||2.5||||ER||UNICODE UTF-8|
SPM||2^158941^1^None^20111119|||||||||C^E|
OBR|1|||1|
OBX|1||1||Valid^false^false^false^1.074^false^^false^false^39609.680&39716.950^^^^^|||LotCalibratio
n|||F||||bmserv||25|e602^1^MU1#e602#2#1^9^Current|20111118175819|
SID|1^^^ASY^18^0|157328|5|
SPM||1^158941^1^None^20111119|||||||||C^E|
OBR|2|||1|
OBX|2||1||Valid^false^false^false^1.074^false^^false^false^936.337&888.767^^^^^|||LotCalibration|||
F||||bmserv||25|e602^1^MU1#e602#2#1^9^Current|20111118175819|
SID|1^^^ASY^18^0|157328|5|

Figure E-61 E-module calibration result

MSH|^~\&|cobas 8000||host||20111118175844||OUL^R22^ECUPL|14268||2.5||||ER||UNICODE UTF-8|

SPM||2^158941^1^None^20111119|||||||||C^E|
OBR|1|||1|
OBX|1||1||Valid^false^false^false^1.064^false^^false^false^38293.490&38596.120^^^^^|||LotCalibratio
n|||F||||bmserv||26|e602^2^MU1#e602#2#2^10^Current|20111118175844|
SID|1^^^ASY^18^0|157328|5|
SPM||1^158941^1^None^20111119|||||||||C^E|
OBR|2|||1|
OBX|2||1||Valid^false^false^false^1.064^false^^false^false^839.413&797.173^^^^^|||LotCalibration|||
F||||bmserv||26|e602^2^MU1#e602#2#2^10^Current|20111118175844|
SID|1^^^ASY^18^0|157328|5|

Figure E-62 E-module calibration result

Masking messages

In the examples in this section the host sends masking messages.

Successful masking message

In this section the host sends a masking command, and the data manager replies with
an Accept acknowledgement message.
Host:
MSH|^~\&|host||cobas 8000||20101007113655||EAC^U07|13010||2.5||||AL||UNICODE UTF-8|
EQU|1|20101007113600|
ECD|1234|LK|||989^P^MU1#ISE#1#1^ALL|

DM:
MSH|^~\&|cobas 8000||host||20101007113946||ACK|19922||2.5||||NE||UNICODE UTF-8|
MSA|AA|13010||

Figure E-63 Successful masking message

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-83
15 Communication examples cobas® 8000 data manager
HL7 trace files cobas® 8000 instrument

Unsuccessful masking message

In this section the host sends a masking command, but the module does not exist.
Host:
MSH|^~\&|host||cobas 8000||20101007113655||EAC^U07|13011||2.5||||AL||UNICODE UTF-8|
EQU|1|20101007113600|
ECD|1234|LK|||989^P^module_X^ALL|

DM:
MSH|^~\&|cobas 8000||host||20101007125554||ACK|19987||2.5||||NE||UNICODE UTF-8|
MSA|AE|13011|Submodule (module_X) not found|
Figure E-64 A masking message that failed as module_X did not exist

Result requests from the host

In the examples in this section the host sends result requests.

Request for all results

In this section the host sends a request for all results for a sample.
Host:
MSH|^~\&|host||cobas 8000||20100430105126||RSREQ|13007||2.5||||NE||UNICODE UTF-8|
QPD|RSREQ||321015||

DM:
MSH|^~\&|cobas 8000||host||20101020084603||OUL^R22^BATCH|15042||2.5||||ER||UNICODE UTF-8|
PID|1|PatID1|||Smith^Alan||19451231|M|
SPM||321015||S1||not|||||P|||C1^C2^C3^C4^C5|||20101019174209||||||||||SC|
SAC||||||||||50071|1|
OBR|1|||990|
TQ1|1||||||||R|
OBX|1||990||0.91|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||F|||20101019174423|bmserv^SYSTEM||128|ISE^2^M
U1#ISE#1#2^4|20101019174439|
TCD|990|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|2|||990|
TQ1|1||||||||R|
OBX|2||990||0.70|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||20101019174459|bmserv^SYSTEM||125|ISE^1^M
U1#ISE#1#1^3|20101019174515|
TCD|990|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|3|||991|
TQ1|1||||||||R|
OBX|3||991||252.89|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||F|||20101019174347|bmserv^SYSTEM||126|ISE^1
^MU1#ISE#1#1^3|20101019174403|
TCD|991|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|4|||991|
TQ1|1||||||||R|
OBX|4||991||256.84|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||20101019174423|bmserv^SYSTEM||129|ISE^2
^MU1#ISE#1#2^4|20101019174439|
TCD|991|1|
NTE|1|I|23^ISE Sample range over|I|

Figure E-65 Result query for all results for a sample and the result upload

Roche Diagnostics
E-84 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument HL7 trace files

OBR|5|||8717|
TQ1|1||||||||R|
OBX|5||8717||-0.04|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20101019174533|bmserv^SYSTEM||77|c701^1^MU
1#c701#1#1^6|20101019175547|
TCD|8717|1|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
NTE|1|I|27^PANIC value over (lower) Technical Limit|I|
OBR|6|||8717|
TQ1|1||||||||R|
OBX|6||8717||-0.02|mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20101019175614|bmserv^SYSTEM||77|c701^1^MU
1#c701#1#1^6|20101019180627|
TCD|8717|Inc|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
NTE|1|I|27^PANIC value over (lower) Technical Limit|I|
Figure E-65 Result query for all results for a sample and the result upload

Request for active results

In this section the host sends a request for active results for a sample.
Host:
MSH|^~\&|host||cobas 8000||20100430105126||RSREQ|13007||2.5||||NE||UNICODE UTF-8|
QPD|RSREQ||321015|F|

DM:
MSH|^~\&|cobas 8000||host||20101020084713||OUL^R22^BATCH|15045||2.5||||ER||UNICODE UTF-8|
PID|1|PatID1|||Smith^Alan||19451231|M|
SPM||321015||S1||not|||||P|||C1^C2^C3^C4^C5|||20101019174209||||||||||SC|
SAC||||||||||50071|1|
OBR|1|||8717|
TQ1|1||||||||R|
OBX|1||8717||-
0.02|mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20101019175614|bmserv^SYSTEM||77|c701^1^MU1#c701#1#1^6|2
0101019180627|
TCD|8717|Inc|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
NTE|1|I|27^PANIC value over (lower) Technical Limit|I|

Figure E-66 Request for active results for a sample

No results found
In this section the host sends a request for active results for a sample, but the data
manager cannot find any results.
Host:
MSH|^~\&|host||cobas 8000||20100430105126||RSREQ|13007||2.5||||NE||UNICODE UTF-8|
QPD|RSREQ||321016|F|

DM:
<No Reply>

Figure E-67 Result request, but no results found

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-85
15 Communication examples cobas® 8000 data manager
HL7 trace files cobas® 8000 instrument

Sample not found

In this section the host sends a request for active results for a sample, but the data
manager cannot find any record of the sample.
Host:
MSH|^~\&|host||cobas 8000||20100430105126||RSREQ|13007||2.5||||NE||UNICODE UTF-8|
QPD|RSREQ||NOT_FOUND|F|

DM:
<No reply>

Figure E-68 Result request, but sample not found

Result request with a sequence number

In this section the host sends a request for results for a sample with sequence number
1031.
Host:
MSH|^~\&|host||cobas 8000||20100430105126||RSREQ|13007||2.5||||NE||UNICODE UTF-8|
QPD|RSREQ||^1031||

DM:
MSH|^~\&|cobas 8000||host||20110712133259||OUL^R22^BATCH|564847||2.5||||NE||UNICODE UTF-8|
PID|1|M820092K|||Muller^Urs||19730416|F|
SPM||^1031||S1||not|||||P|||^^^^|||20110711085411||||||||||SC|
SAC||||||||||50203|3|
OBR|1|||8413|
TQ1|1||||||||R|
OBX|1||8413||19|g/dL|^TECH~^NORM~^CRIT~^USER||||F|||20111212104600|bmserv^SYSTEM||193|c702^2^MU1#c7
02#1#2^7|20111212104600|
TCD|8413|1|
SID|8413^^784648^R1^2^0|231478|5|
SID|8413^^784648^R3^2^0|231478|5|
NTE|1|I|0|I|
OBR|2|||8571|
TQ1|1||||||||R|
OBX|2||8571||21|U/L|^TECH~^NORM~^CRIT~^USER||||F|||20111212104600|bmserv^SYSTEM||193|c702^2^MU1#c70
2#1#2^7|20111212104600|
TCD|8571|1|
SID|8571^^784648^R1^2^0|231478|5|
SID|8571^^784648^R3^2^0|231478|5|
NTE|1|I|0|I|
OBR|3|||8706|
TQ1|1||||||||R|
OBX|3||8706||23|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20111212104600|bmserv^SYSTEM||193|c702^2^MU1#
c702#1#2^7|20111212104600|
TCD|8706|1|
SID|8706^^784648^R1^2^0|231478|5|
SID|8706^^784648^R3^2^0|231478|5|
NTE|1|I|0|I|

Figure E-69 Result request with a sequence number

Roche Diagnostics
E-86 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 15 Communication examples
®
cobas 8000 instrument HL7 trace files

Order requests from the host

In the examples in this section the host sends order requests.

Request for all tests

In this section the host sends a request for all tests for a sample.
Host:
MSH|^~\&|host||cobas 8000||20100825132805||TSREQ|10001||2.5||||NE||UNICODE UTF-8|
QPD|TSREQ||321015|||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000||host||||OML^O33|15023||2.5||||ER||UNICODE UTF-8|
SPM||321015||S1||||||||||C1^C2^C3^C4^C5|
OBR||||990|
OBR||||991|
OBR||||8717|

Figure E-70 Request for all tests

Request for open tests

In this section the host sends a request for open tests for a sample.
Host:
MSH|^~\&|host||cobas 8000||20100825132805||TSREQ|10001||2.5||||NE||UNICODE UTF-8|
QPD|TSREQ||321015|O||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000||host||||OML^O33|15021||2.5||||ER||UNICODE UTF-8|
SPM||321015||S1||||||||||C1^C2^C3^C4^C5|
OBR||||990|
OBR||||991|

Figure E-71 Request for open tests

No tests found
In this section the host sends a request for open tests for a sample, but the data
manager does not find any tests.
Host:
MSH|^~\&|host||cobas 8000||20100825132805||TSREQ|10001||2.5||||NE||UNICODE UTF-8|
QPD|TSREQ||321016|O||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000||host||||OML^O33|15025||2.5||||ER||UNICODE UTF-8|
SPM||321016||S1||||||||||^^^^|

Figure E-72 Request for open tests, but no tests found

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-87
15 Communication examples cobas® 8000 data manager
HL7 trace files cobas® 8000 instrument

Sample not found

In this section the host sends a request for open tests for a sample, but the data
manager does not find the sample.
Host:
MSH|^~\&|host||cobas 8000^1.02||20100825132805||TSREQ|10001||2.5||||NE||UNICODE UTF-8|
QPD|TSREQ||NOT_EXISTING|||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000^1.02||host||||OML^O33|15028||2.5||||ER||UNICODE UTF-8|
SPM||NOT_EXISTING||S1||||||||||^^^^|
Figure E-73 Request for open tests, but sample not found

Order request with a sequence number

In this section the host sends an order request for a sample with sequence number
1031.
Host:
MSH|^~\&|host||cobas 8000||20110711122805||TSREQ|10001||2.5||||NE||UNICODE UTF-8|
QPD|TSREQ||^1031|||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000||host||||OML^O33|564825||2.5||||NE||UNICODE UTF-8|
SPM||^1031||S1||||||||||^^^^|
OBR||||8413^1|
OBR||||8571^1|
OBR||||8706^1|

Figure E-74 Order request with a sequence number

Roche Diagnostics
E-88 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 16 Preparing the host communication
®
cobas 8000 instrument Table of contents

Preparing the host communication

Important preliminary information for the preparation
of the host communication

This chapter explains the differences in functionality as regards the host

communication protocol between Modular / cobas® 6000 and cobas® 8000 data
manager.

In this chapter Chapter 16

Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000
analyzer series ................................................................................................................. E-91
General differences in the ASTM protocol .......................................................... E-91
Message encoding and transport ..................................................................... E-91
Sample identification ........................................................................................ E-92
Sample types ....................................................................................................... E-92
Patient demographics ........................................................................................ E-93
ASTM message types ......................................................................................... E-93
HL7 message types ............................................................................................. E-94
Differences in ASTM message definitions ........................................................... E-95
General differences in the ASTM messages ................................................... E-95
Message Header Record .................................................................................... E-95
Message Termination Record .......................................................................... E-95
Patient Record .................................................................................................... E-96
Order Record ...................................................................................................... E-96
Result Record ..................................................................................................... E-98
Comment Record (following an Order Record) ........................................... E-99
Comment Record (following a Result Record) .......................................... E-100
Query Record .................................................................................................. E-100
Photometric Calibration Result Record ...................................................... E-100
ISE Calibration Result Record ...................................................................... E-101
E-module (Immunology) Calibration Result Record ................................ E-103
Other differences ................................................................................................... E-104
Encoding .......................................................................................................... E-104

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-89
16 Preparing the host communication cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Rerun results .................................................................................................... E-104

LIS communications ............................................................................................. E-104
Identifying samples by sequence number ......................................................... E-105
Traceability information for quality control and calibration results ............. E-105
Upgrading to version 1.02.05 with ASTM ............................................................... E-106
Upgrading to version 1.02.05 with HL7 ................................................................... E-106
The specimen segment SPM ............................................................................... E-106
The observation result segment OBX ................................................................ E-107
The substance identifier segment SID ............................................................... E-107

Roche Diagnostics
E-90 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 16 Preparing the host communication
®
cobas 8000 instrument Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Differences to the MODULAR ANALYTICS EVO analyzer /

cobas® 6000 analyzer series

This section describes the main differences in the ASTM protocols used with
cobas® 8000 data manager and MODULAR ANALYTICS EVO analyzer /
cobas® 6000 analyzer series.

General differences in the ASTM protocol

This section describes the general differences in functionality between the

MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series and the
cobas® 8000 data manager.

Message encoding and transport

Extended ASCII is converted to UTF-8

Extended ASCII values 128 to 255 were supported in MODULAR ANALYTICS EVO
WARNING analyzer / cobas® 6000 analyzer series. However cobas® 8000 data manager uses UTF-8.
You need to use a conversion mechanism to convert extended ASCII value to UTF-8.

Item MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
Character encoding Not specified / Only UTF-8. That means
ASCII can be truly characters up to 127
supported due to are compatible with
possible 7-bit data ASCII
transfer option 8- bit data transfer
used.
ASTM Message ASTM E1381 (low ASTM E1381 (low
Type(s) level), ASTM E1394 level), ASTM E1394
(message) (message)
HL7 Messaging Not supported Minimal Layer Extended
Protocol HL7 2.5
RS232 Variable settings, Fixed to 19200, 8 N 1
editable from (could be changed by
graphical user configuration file)
interface
Network Not supported TCP/IP socket client Extended
(could be changed by
configuration files)

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-91
16 Preparing the host communication cobas® 8000 data manager
Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series cobas® 8000 instrument

Sample identification

Item MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
Sample number Yes (Only for Batch Sequential sample Similar functionality.
mode(a) Download with numbering available See Chapter
Sample Barcode from 1.02.03 for 14 Identifying patient
Reader = OFF) patient samples. samples by sequence
number
Barcode label Yes Yes
Rack & Sample Yes Yes
Position
(a) No real sample identification

Sample types
The sample types (or Rack Types) are used in Query Record and Order Record
(Specimen Types). While all these types are supported by the cobas® 8000 data
manager, their availability on any particular system also depends on the
configuration and modules installed on the cobas® 8000 instrument.

Item Rack Type Specimen MODULAR cobas® 8000 data Comment

Type ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
No specimen assigned S0 Yes Yes
Serum/Plasma S1 1 Yes Yes
Urine S2 2 Yes Yes
Cerebrospinal Fluid S3 3 Yes Yes
Supernatant S4 4 Yes Yes
Other S5 5 Yes Yes
Whole Blood S6 6 No Yes Extended
Oral Fluids (Saliva) S7 7 No Yes Extended
Other 2 S8 8 No Yes Extended
Other 3 S9 9 No Yes Extended
Other 4 SA A No Yes Extended

Roche Diagnostics
E-92 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 16 Preparing the host communication
®
cobas 8000 instrument Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Patient demographics

Item MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
First Name Comment Record Patient Record See, more Details
after Order Record below
Last Name Comment Record Patient Record See, more Details
after Order Record below
Date of Birth Comment Record Patient Record See, more Details
after Order Record below
Patient’s age Patient Record No (coded in Date of See, more Details
Birth) below
Patient’s age unit Patient Record No (coded in Date of See, more Details
Birth) below

ASTM message types

Item MODULAR cobas® 8000 data Direction Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
Inquiry for the Requested Tests TSREQ^REAL TSREQ data manager to host Reduced
Result Report (realtime) RSUPL^REAL RSUPL data manager to host Reduced
Result Report (batch) RSUPL^BATCH RSUPL data manager to host Reduced
Result Report (quality control: for RSUPL^REAL RSUPL^REAL data manager to host (Unchanged for QC
first upload of results) results)
Result Report (quality control: when RSUPL^BATCH RSUPL^BATCH data manager to host (Unchanged for QC
repeating uploads of results results)
previously sent)
Result Report (query) RSUPL^REPLY RSUPL analyzer to host Reduced
Photometry Calibration Result PCUPL^REAL PCUPL^REAL to host Reduced
Report
ISE Calibration Result Report ICPUL^REAL ICPUL^REAL to host Reduced
Calibration Result Report from ECUPL^REAL ECUPL^REAL to host Reduced
Immunology Modules
Photometric Raw Data Report ABUPL^BATCH n/a to host Reduced
Raw Data Report from Immunology EBUPL^BATCH n/a to host Reduced
Modules
Test Selection Download (answer to TSDWN^REPLY TSDWN host to data manager Reduced
inquiry)
Test Selection Download TSDWN^BATCH TSDWN host to data manager Reduced
(unsolicited)
Inquiry of Result RSREQ^BATCH RSREQ host to instrument Reduced
Inquiry for Requested Test n/a TSREQ host to data manager Enhanced

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-93
16 Preparing the host communication cobas® 8000 data manager
Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series cobas® 8000 instrument

HL7 message types

Item MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
Inquiry for the NO TSREQ Extended
Requested Tests
Result Report NO OUL^R22 Extended
(realtime)
Result Report NO OUL^R22 Extended
(batch)
Quality Control NO OUL^R22^REAL Extended
Result Report
(realtime)
Quality Control NO OUL^R22^BATCH Extended
Result Report
(batch)
Test Selection NO OML^O33 Extended
Download
(inquiry)
Test Selection NO OML^O33 Extended
Download
(inquiry)
Photometric NO OUL^R22^PCUPL Extended
Calibration Result
ISE Calibration NO OUL^R22^ICUPL Extended
Result
Immunology NO OUL^R22^ECUPL Extended
Calibration Result
Masking command NO EAC^U07 Extended

Roche Diagnostics
E-94 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 16 Preparing the host communication
®
cobas 8000 instrument Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Differences in ASTM message definitions

This section describes the differences in the ASTM messages used by the MODULAR
ANALYTICS EVO analyzer / cobas® 6000 analyzer series and the cobas® 8000 data
manager.

General differences in the ASTM messages

ASTM message records in cobas® 8000 are terminated by a vertical bar, but in
MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series the vertical bar
is omitted.

Message Header Record

Field Description MODULAR cobas® 8000 data manager Comment

ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
3 Control ID NO YES Extended
5 data manager to host: As specified at host Editable in
Sender ID setting screen Interface options, default
cobas 8000^1
10 data manager to host: As specified at host Fixed to host
Receiver ID setting screen
11 Comment or special See ASTM Msg. See ASTM Msg. Types See above
instruction Types
14 Date/Time of No Yes, YYYYMMDDhhmmss Extended
message

Message Termination Record

Field Description MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
3 Termination Code N, T, R, E, Q, I, T N Reduced

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-95
16 Preparing the host communication cobas® 8000 data manager
Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series cobas® 8000 instrument

Patient Record
The cobas® 8000 data manager supports no patient age information, but uses the
patient’s day of birth instead.
e For more information, see Patient demographics on page E-93.

Field Description MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
6, C1,C2 Patientname NO Name^firstname Other location
8 Date of Birth NO YYYYMMDD Other data and
location
15 C1,C2 Special Field 1 Age^Age Unit NO Other data and
location

The data manager supports only M, F, or U for patient sex.

For male patients, the host must send M, for females, F. Otherwise the wrong reference
WARNING range might be applied. The data manager reads any other value as U, and applies the
reference ranges for a patient of unknown sex.
Make sure the host sends only M, F, or U, as required. Each new configuration must be
tested to ensure the correct data transfer between the data manager and the host.

Order Record
The cobas® 8000 data manager supports:
o application codes (or testcodes) 1 to 5 characters long, as opposed to MODULAR
ANALYTICS EVO analyzer / cobas® 6000 analyzer series which only supported
up to 3 characters.
o rack types S1 to S9 + SA, but MODULAR ANALYTICS EVO analyzer /
cobas® 6000 analyzer series only supports S1 to S5
o dilution factors changed, and no dilution shown by 1, not by an empty
component.
o Action code “R” for reruns: “A” however can also be used for ordering reruns.
o The host may download testcodes for calculated tests, so long as the calculated
tests are programmed on the data manager. For details, see the cobas® 8000
modular analyzer series Operator’s Manual.
Also, cobas® 8000 data manager requires no padding with spaces for the sample ID.

Field Description MODULAR cobas® 8000 data manager Comment

ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
3 Sample ID for Control-SID: Name Name^LotNr^Control-ID Extended, Upload
controls or Lotnumber (if no sample ID)
(Selectable at Host
Information Screen)
4,C2 Rack ID 4 digits 5 digits Extended
4,C5 Rack Type S1-S5,QC S1-SA,QC Extended
4,C7 Diluted Not used not, pre-diluted, no value Extended

Roche Diagnostics
E-96 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 16 Preparing the host communication
®
cobas 8000 instrument Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Field Description MODULAR cobas® 8000 data manager Comment

ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
5,C5 Universal Test ID, Photometry: ISE module: Reduced.
Dilution Inc,Dec,3,5,10,20,50, o 1 Also, the value 1 is
100,empty Clinical chemistry module: now sent for “No
o 1, Inc, Dec dilution”. When sent
from the host (TS
Immunology module:
download), in case of
o 1, 2, 5, 10, 20, 50,
no pending test on
100, 400
the host side this field
has to be empty
7 Requested/ Not used Yes, YYYYMMDDhhmmss Extended
Ordered Date and
Time
12 Action Code By host: By host: Extended
o A=Add, o A=Add or rerun.
o C=Cancel o C=Cancel,
o R=Add or rerun
16 Specimen Descriptor 1,2,3,4,5 1,2,3,4,5,6,7,8,9, A Extended
(According to Racktype)
23 Date/Time Results Yes No Reduced for Result
reported upload

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-97
16 Preparing the host communication cobas® 8000 data manager
Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series cobas® 8000 instrument

Result Record
The cobas® 8000 data manager identifier is different to the MODULAR ANALYTICS
EVO analyzer / cobas® 6000 analyzer series identifier. The cobas® 8000 data manager
consists of a configurable analytical unit ID, the module name and the internal
number as registered in data manager. (Field R-14)
The cobas® 8000 data manager writes the instrument operator username and (when
pass-though mode is off) the data manager operator username into two components
of field 11.
The cobas® 8000 data manager can also indicate a manually edited result in field 9.

Field Description MODULAR cobas® 8000 data manager Comment

ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
3,C5 Universal Test ID Dilution Factor for For an ISE module, : The value 1 is now
Photometry: o 1 sent for “No
Inc,Dec,3,5,10,20,50, dilution”.
For a clinical chemistry module:
100
o 1, Inc, Dec
For an immunology module,
1, 2, 5, 10, 20, 50, 100, 400
4,C1 Measurement value Qualitative Value ReportableResult Change
For quantitative results, this is a
number, up to 6 digits. In case of a
missing result this field contains six
spaces (ASCII 32 / 0x20).
For qualitative results, this contains
an integer code from -2 to 3 inclusive.
4,C2 Measurement value Quantitative Value AdditionalResultValues Change
For quantitative results, this is empty
or contains a qualitative flag.
For qualitative results, this contains
the quantitative result
6 Reference ranges No Reference ranges Extended
7 Result abnormal flags A=Abnormal A=Alphanumeric out of normal Extended
range
AA=Alphanumeric out of critical
range
EP-17 flags also supported
9 Result status F=First Run, F =First Run, Extended
C=Corrective C =Corrected,
M =Manually edited
X = Calculated test, but test could not
be calculated (for example, divided
by zero)
11 Operator Operator at Analyzer Operator at Analyzer^ Extended
Identification Operator at data manager

Roche Diagnostics
E-98 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 16 Preparing the host communication
®
cobas 8000 instrument Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Field Description MODULAR cobas® 8000 data manager Comment

ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
13 Date/Time Test No Yes Extended
completed
14 Measurement unit ID P1,P2,P3,P4,ISE1,ISE ModuleType^SubModule^ Extended
(Module or 2,Exy AnalyticalUnitID^
Instrument ID) InstrumentID^CalID^Bottle^
SBNo
Bottle^SBNo used only for QC.
ModuleTypes: c502, c701, e602,
c702, ISE, DM, c8000

Comment Record (following an Order Record)

Field Description MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
3 Comment Source “I” by Analyzer, “L” “I” by Analyzer, “L”
by Host by Host or data
manager

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-99
16 Preparing the host communication cobas® 8000 data manager
Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series cobas® 8000 instrument

Comment Record (following a Result Record)

A data manager user can enter multiple comments for each result. This was not
possible for the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer
series.

Field Description MODULAR cobas® 8000 data manager Comment

ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
3 Comment source “I” by Analyzer “I” by Analyzer, “L” by data manager Extended
4 Comment Text, if Flagnumber Flagnumber^Description Extended
type I
5 Comment Type, if No Text^User^Date Extended
type G

Query Record

Field Description MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
3, C5 Rack ID 4 Digits 5 Digits Extended
3, C8 Rack Type S0, S1, ... S5 S0, S1, ... S5, S6, ... S9, Extended
SA
12 User Field 2 No Priority: Extended
o R = Routine
o S = STAT
13 Request Information o A=Rejects o O=Request for Reduced
Status Code previous req. Test Request
o O=Request for o F=Final Result
Test Request
o F=Final Result

Photometric Calibration Result Record

Field Description MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
6 Analytical Unit ID P1,P2,P3,P4,ISE1,ISE AnalyticalUnitID, Extended
2,Exy default:
Instrument#
ModuleType#
Position#
SubModule
For example,;
MU1#e602#1#1
Fully safely editable.
9, C6 Prozone value Sent Not sent Reduced
10 Reagent lot number 1 to 99999999 Not sent Reduced

Roche Diagnostics
E-100 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 16 Preparing the host communication
®
cobas 8000 instrument Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Field Description MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
11 Reagent bottle 1 to 19999 Not sent Reduced
number
12 Expired flag 0 or 1 Not sent Reduced
13 Calibrator lot 1 to 99999999 Not sent Reduced
number
14 Pipetting date and YYYYMMDDHHM Not sent Reduced
time MSS

ISE Calibration Result Record

Field Description MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
5 Analytical Unit ID P1,P2,P3,P4,ISE1,ISE AnalyticalUnitID, Extended
2,Exy default:
Instrument#
ModuleType#
Position#
SubModule
For example;
MU1#e602#1#1
Fully editable.
9,C7 Na Data alarms Component 7 Component 7 Extended
contains: contains:
Numbers for Carryover rate alarm
compensation alarm (Numbers for
compensation alarm
passed in Component
10.)
9,C8 Calculation slope Not supported Supported Extended
value alarm
9,C10 Numbers for Passed in Component Passed in Component
compensation alarm 7 10
10,C7 K Data alarms Component 7 Component 7 Extended
contains: contains:
Numbers for Carryover rate alarm
compensation alarm (Numbers for
compensation alarm
passed in Component
10.)
10,C8 Calculation slope Not supported Supported Extended
value alarm
10,C10 Numbers for Passed in Component Passed in Component
compensation alarm 7 10

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-101
16 Preparing the host communication cobas® 8000 data manager
Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series cobas® 8000 instrument

Field Description MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
11,C7 Cl Data alarms Component 7 Component 7 Extended
contains: contains:
Numbers for Carryover rate alarm
compensation alarm (Numbers for
compensation alarm
passed in Component
10.)
11,C8 Calculation slope Not supported Supported Extended
value alarm
11,C10 Numbers for Passed in Component Passed in Component
compensation alarm 7 10
12,C7 Na Calibration Component 7 Component 7 Extended
analytical data contains: contains:
Numbers for Carryover rate
compensation data (Numbers for
compensation data
passed in Component
10.)
12,C8 Calculation slope Not supported Supported Extended
value alarm
12,C10 Numbers for Passed in Component Passed in Component
compensation data 7 10
13,C7 K Calibration Component 7 Component 7 Extended
analytical data contains: contains:
Numbers for Carryover rate
compensation data (Numbers for
compensation data
passed in Component
10.)
13,C8 Calculation slope Not supported Supported Extended
value alarm
13,C10 Numbers for Passed in Component Passed in Component
compensation data 7 10
14,C7 Cl Calibration Component 7 Component 7 Extended
analytical data contains: contains:
Numbers for Carryover rate
compensation data (Numbers for
compensation data
passed in Component
10.)
14,C8 Calculation slope Not supported Supported Extended
value
14,C10 Numbers for Passed in Component Passed in Component
compensation data 7 10

Roche Diagnostics
E-102 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 16 Preparing the host communication
®
cobas 8000 instrument Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

E-module (Immunology) Calibration Result Record

Field Description MODULAR cobas® 8000 data manager Comment

ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
6 Calibration method LOT, RackPack Permitted values: Extended
o NoCalibration
o LotCalibration
o ContainerCalibration
o InheritedLotCalibration
o InheritedItemCalibration
o UserModifiedCalibration
o UnmaskedCalibration
o FailedCalibration
7 Analytical Unit ID P1,P2,P3,P4,ISE1,ISE AnalyticalUnitID, default: Extended
2,Exy Instrument#
ModuleType#
Position#
SubModule
For example; MU1#e602#1#1
Fully editable.
12 Result Status o O o O Reduced
o Q o F
o F
13.3 Result Many values, up to a Not supported Reduced
Characteristics, detail 20 digit code
15 Target value Complex field, five Not supported Reduced
numbers
16 Unit String Not supported Reduced
17 Cut off Number Not supported Reduced
18 Border line area Complex field Not supported Reduced

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-103
16 Preparing the host communication cobas® 8000 data manager
Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series cobas® 8000 instrument

Other differences

Encoding
Extended ASCII values 128 to 255 were supported in MODULAR ANALYTICS EVO
analyzer / cobas® 6000 analyzer series. However, cobas® 8000 data manager uses UTF-
8. This represents greatly extended functionality, but may require a conversion
mechanism from extended ASCII to UTF-8.

Rerun results

Item MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
Stored rerun results Can store and send: Can store and send all Extended
o first result results for a test.
o most recent result
for a test.

LIS communications

Item MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
Communication ASTM over serial. o HL7 over TCP/IP Extended
protocols o ASTM over
TCP/IP
o ASTM over serial

Details e For details of how to select a connection, see Starting and stopping the host connection on
page B-21.
e For details of the physical connections, see Host communication settings and cables on
page B-47.

Roche Diagnostics
E-104 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 16 Preparing the host communication
®
cobas 8000 instrument Differences to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Identifying samples by sequence number

Since version 1.02.03, it is possible to identify samples by a sequential number.

Item MODULAR cobas® 8000 data Comment

ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
Identification of Barcode and sample o Barcode and Extended
samples ID. sample ID
o Sequential
numbering
o Rack and position

Details e For details of how to to identify samples by a sequential number, see Identifying patient
samples by sequence number on page E-47.
e For details of how to to identify samples by a strict rack and position, see Using a
MODULAR PRE-ANALYTICS on page E-41, and Rack and position mode on page B-30.

Traceability information for quality control and calibration results

Since version 1.02.05, there is additional data sent with quality control and
calibration results, that improves traceability. This is only supported in HL7.

Details e For details see Upgrading to version 1.02.05 with HL7 on page E-106.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-105
16 Preparing the host communication cobas® 8000 data manager
Upgrading to version 1.02.05 with ASTM cobas® 8000 instrument

Upgrading to version 1.02.05 with ASTM

There is no change to the ASTM interface when upgrading to 1.02.05.

The previous mandatory upgrade of the cobas® 8000 data manager software was
version 1.02.02, and the previous recommended upgrade was 1.02.03. The new
functionality in version 1.02.05 is only supported in HL7. Therefore, there is no
change to the ASTM interface.

Upgrading to version 1.02.05 with HL7

This section lists the differences to a host interface using the HL7 protocol between
the version 1.02.03 and version 1.02.05 of the data manager.
Version 1.02.02 was the previous mandatory upgrade of the cobas® 8000 data
manager software. Version 1.02.03 was the previous recommended upgrade.

The specimen segment SPM

This section lists the changes to the specimen segment SPM.

e For calibration results, the SPM segment looks quite different, see Specimen Segment -
SPM for calibration results on page D-18.

Field Description 1.02.03 1.02.05

SPM-2 Expiry date of control o For patient results: sample ID o For patient results: sample ID
or calibration lot o For QC: Name^Lot^ID o For QC: Name^Lot^ID^ExpiryDate
added. o For C-module and E-module calibration o For C-module and E-module calibration
materials, materials,
Level^Lot^Code^Count Level^Lot^Code^Count^Expirydate
o For ISE module calibration results: empty. o For ISE module calibration results: empty.
SPM-2.4 Expiry date of control Empty for quality control results For quality control results: expiry date of
lot: used only in control lot.
Quality Control
results
SPM-2.5 Expiry date of control Empty for calibration results For C-module and E-module calibration
lot: used only for C- results: expiry date of calibration lot.
module and E-module
calibration results

Roche Diagnostics
E-106 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 16 Preparing the host communication
®
cobas 8000 instrument Upgrading to version 1.02.05 with HL7

The observation result segment OBX

This section lists the changes to the observation result segment OBX.

Field Description 1.02.03 1.02.05

OBX-7 Reference ranges Not supported for quality control results. Target value and standard deviation supplied.
e Observation Result Segment - OBX (for
QC results) on page D-26.
OBX-18 Measurement Unit ID ModuleType^ ModuleType^
SubModule^ SubModule^
AnalyticalUnitID^ AnalyticalUnitID^
InstrumentID^
InstrumentID^
Bottle^SBNo
Bottle^SBNo
Bottle^SBNo used only for QC.
Bottle^SBNo used only for QC and for C-
Note: ISE module only supports module (photometry) and for E-module
AnalyticalUnitID here. (immunology) results.
Note: ISE module only supports
AnalyticalUnitID here.

The substance identifier segment SID

This section lists the changes to the substance identifier segment SID.

Field Description 1.02.03 1.02.05

SID-1 Substance identifier o Not supported by C-module (photometry) o Supported by C-module calibration
(for calibration or ISE calibration results. results.
results) o Not supported by ISE calibration results.

SID-2 Reagent lot o Not supported by C-module (photometry) o Supported by C-module and E-module
or ISE calibration results. calibration results.
o Supported by E-module (immunology) o Not supported by ISE calibration results.
calibration results.
SID-3 Reagent serial number Not supported by calibration results. o Supported by C-module and E-module
calibration results.
o Not supported by ISE calibration results.

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-107
16 Preparing the host communication cobas® 8000 data manager
Upgrading to version 1.02.05 with HL7 cobas® 8000 instrument

Roche Diagnostics
E-108 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 17 Text encoding tables
®
cobas 8000 instrument Table of contents

Text encoding tables

This chapter shows a table with ASCII codes and another with UTF-8 codes for
common Western European characters, for the convenience of developers.

In this chapter Chapter 17

ASCII table ................................................................................................................... E-111
Western European characters in UTF-8 .................................................................. E-112

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-109
17 Text encoding tables cobas® 8000 data manager
Table of contents cobas® 8000 instrument

Roche Diagnostics
E-110 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 17 Text encoding tables
®
cobas 8000 instrument ASCII table

ASCII table

The ASCII 127 character codes are shown below, with each printed character and
its hexadecimal and decimal value

NUL DLE Space 0 @ P ` p

000 10 16 20 32 30 48 40 64 50 80 60 96 70 112
SOH DC1 ! 1 A Q a q
011 11 17 21 33 31 49 41 65 51 81 61 97 71 113
STX DC2 " 2 B R b r
022 12 18 22 34 32 50 42 66 52 82 62 98 72 114
ETX DC3 # 3 C S c s
033 13 19 23 35 33 51 43 67 53 83 63 99 73 115
EOT DC4 $ 4 D T d t
044 14 20 24 36 34 52 44 68 54 84 64 100 74 116
ENQ NAK % 5 E U e u
055 15 21 25 37 35 53 45 69 55 85 65 101 75 117
ACK SYN & 6 F V f v
066 16 22 26 38 36 54 46 70 56 86 66 102 76 118
BEL ETB ' 7 G W g w
077 17 23 27 39 37 55 47 71 57 87 67 103 77 119
BS CAN ( 8 H X h x
088 18 24 28 40 38 56 48 72 58 88 68 104 78 120
HT EM ) 9 I Y i y
099 19 25 29 41 39 57 49 73 59 89 69 105 79 121
LF SUB * : J Z j z
0A 10 1A 26 2A 42 3A 58 4A 74 5A 90 6A 106 7A 122
VT ESC + ; K [ k {
0B 11 1B 27 2B 43 3B 59 4B 75 5B 91 6B 107 7B 123
FF FS , < L \ l |
0C 12 1C 28 2C 44 3C 60 4C 76 5C 92 6C 108 7C 124
CR GS - = M ] m }
0D 13 1D 29 2D 45 3D 61 4D 77 5D 93 6D 109 7D 125
SO RS . > N ^ n ~
0E 14 1E 30 2E 46 3E 62 4E 78 5E 94 6E 110 7E 126
SI US / ? O _ o DEL
0F 15 1F 31 2F 47 3F 63 4F 79 5F 95 6F 111 7F 127

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-111
17 Text encoding tables cobas® 8000 data manager
Western European characters in UTF-8 cobas® 8000 instrument

Western European characters in UTF-8

This section shows the Unicode code point and the hexadecimal value of common
Western European characters in UTF-8 format. By default, the cobas® 8000 data
manager uses UTF-8.

Unicode Name Unicode Name

UTF-8 (hex.)

UTF-8 (hex.)
Character

Character
code code
point point

U+0000 00 <control> U+0001 01 <control>

U+0002 02 <control> U+0003 03 <control>
U+0004 04 <control> U+0005 05 <control>
U+0006 06 <control> U+0007 07 <control>
U+0008 08 <control> U+0009 09 <control>
U+000A 0a <control> U+000B 0b <control>
U+000C 0c <control> U+000D 0d <control>
U+000E 0e <control> U+000F 0f <control>
U+0010 10 <control> U+0011 11 <control>
U+0012 12 <control> U+0013 13 <control>
U+0014 14 <control> U+0015 15 <control>
U+0016 16 <control> U+0017 17 <control>
U+0018 18 <control> U+0019 19 <control>
U+001A 1a <control> U+001B 1b <control>
U+001C 1c <control> U+001D 1d <control>
U+001E 1e <control> U+001F 1f <control>
U+0020 20 SPACE U+0021 ! 21 EXCLAMATION MARK
U+0022 " 22 QUOTATION MARK U+0023 # 23 NUMBER SIGN
U+0024 $ 24 DOLLAR SIGN U+0025 % 25 PERCENT SIGN
U+0026 & 26 AMPERSAND U+0027 ' 27 APOSTROPHE
U+0028 ( 28 LEFT PARENTHESIS U+0029 ) 29 RIGHT PARENTHESIS
U+002A * 2a ASTERISK U+002B + 2b PLUS SIGN
U+002C , 2c COMMA U+002D - 2d HYPHEN-MINUS
U+002E . 2e FULL STOP U+002F / 2f SOLIDUS
U+0030 0 30 DIGIT ZERO U+0031 1 31 DIGIT ONE
U+0032 2 32 DIGIT TWO U+0033 3 33 DIGIT THREE
U+0034 4 34 DIGIT FOUR U+0035 5 35 DIGIT FIVE
U+0036 6 36 DIGIT SIX U+0037 7 37 DIGIT SEVEN
U+0038 8 38 DIGIT EIGHT U+0039 9 39 DIGIT NINE
U+003A : 3a COLON U+003B ; 3b SEMICOLON
U+003C < 3c LESS-THAN SIGN U+003D = 3d EQUALS SIGN
U+003E > 3e GREATER-THAN SIGN U+003F ? 3f QUESTION MARK
U+0040 @ 40 COMMERCIAL AT U+0041 A 41 LATIN CAPITAL LETTER A
U+0042 B 42 LATIN CAPITAL LETTER B U+0043 C 43 LATIN CAPITAL LETTER C
U+0044 D 44 LATIN CAPITAL LETTER D U+0045 E 45 LATIN CAPITAL LETTER E
U+0046 F 46 LATIN CAPITAL LETTER F U+0047 G 47 LATIN CAPITAL LETTER G
Roche Diagnostics
E-112 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 17 Text encoding tables
®
cobas 8000 instrument Western European characters in UTF-8

Unicode Name Unicode Name

UTF-8 (hex.)

UTF-8 (hex.)
Character

Character
code code
point point

U+0048 H 48 LATIN CAPITAL LETTER H U+0049 I 49 LATIN CAPITAL LETTER I

U+004A J 4a LATIN CAPITAL LETTER J U+004B K 4b LATIN CAPITAL LETTER K
U+004C L 4c LATIN CAPITAL LETTER L U+004D M 4d LATIN CAPITAL LETTER
M
U+004E N 4e LATIN CAPITAL LETTER N U+004F O 4f LATIN CAPITAL LETTER
O
U+0050 P 50 LATIN CAPITAL LETTER P U+0051 Q 51 LATIN CAPITAL LETTER
Q
U+0052 R 52 LATIN CAPITAL LETTER R U+0053 S 53 LATIN CAPITAL LETTER S
U+0054 T 54 LATIN CAPITAL LETTER T U+0055 U 55 LATIN CAPITAL LETTER
U
U+0056 V 56 LATIN CAPITAL LETTER V U+0057 W 57 LATIN CAPITAL LETTER
W
U+0058 X 58 LATIN CAPITAL LETTER X U+0059 Y 59 LATIN CAPITAL LETTER Y
U+005A Z 5a LATIN CAPITAL LETTER Z U+005B [ 5b LEFT SQUARE BRACKET
U+005C \ 5c REVERSE SOLIDUS U+005D ] 5d RIGHT SQUARE BRACKET
U+005E ^ 5e CIRCUMFLEX ACCENT U+005F _ 5f LOW LINE
U+0060 ` 60 GRAVE ACCENT U+0061 a 61 LATIN SMALL LETTER A
U+0062 b 62 LATIN SMALL LETTER B U+0063 c 63 LATIN SMALL LETTER C
U+0064 d 64 LATIN SMALL LETTER D U+0065 e 65 LATIN SMALL LETTER E
U+0066 f 66 LATIN SMALL LETTER F U+0067 g 67 LATIN SMALL LETTER G
U+0068 h 68 LATIN SMALL LETTER H U+0069 i 69 LATIN SMALL LETTER I
U+006A j 6a LATIN SMALL LETTER J U+006B k 6b LATIN SMALL LETTER K
U+006C l 6c LATIN SMALL LETTER L U+006D m 6d LATIN SMALL LETTER M
U+006E n 6e LATIN SMALL LETTER N U+006F o 6f LATIN SMALL LETTER O
U+0070 p 70 LATIN SMALL LETTER P U+0071 q 71 LATIN SMALL LETTER Q
U+0072 r 72 LATIN SMALL LETTER R U+0073 s 73 LATIN SMALL LETTER S
U+0074 t 74 LATIN SMALL LETTER T U+0075 u 75 LATIN SMALL LETTER U
U+0076 v 76 LATIN SMALL LETTER V U+0077 w 77 LATIN SMALL LETTER W
U+0078 x 78 LATIN SMALL LETTER X U+0079 y 79 LATIN SMALL LETTER Y
U+007A z 7a LATIN SMALL LETTER Z U+007B { 7b LEFT CURLY BRACKET
U+007C | 7c VERTICAL LINE U+007D } 7d RIGHT CURLY BRACKET
U+007E ~ 7e TILDE U+007F 7f <control>
U+0080 c2 80 <control> U+0081 c2 81 <control>
U+0082 c2 82 <control> U+0083 c2 83 <control>
U+0084 c2 84 <control> U+0085 c2 85 <control>
U+0086 c2 86 <control> U+0087 c2 87 <control>
U+0088 c2 88 <control> U+0089 c2 89 <control>
U+008A c2 8a <control> U+008B c2 8b <control>
U+008C c2 8c <control> U+008D c2 8d <control>
U+008E c2 8e <control> U+008F c2 8f <control>
U+0090 c2 90 <control> U+0091 c2 91 <control>

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-113
17 Text encoding tables cobas® 8000 data manager
Western European characters in UTF-8 cobas® 8000 instrument

Unicode Name Unicode Name

UTF-8 (hex.)

UTF-8 (hex.)
Character

Character
code code
point point

U+0092 c2 92 <control> U+0093 c2 93 <control>

U+0094 c2 94 <control> U+0095 c2 95 <control>
U+0096 c2 96 <control> U+0097 c2 97 <control>
U+0098 c2 98 <control> U+0099 c2 99 <control>
U+009A c2 9a <control> U+009B c2 9b <control>
U+009C c2 9c <control> U+009D c2 9d <control>
U+009E c2 9e <control> U+009F c2 9f <control>
U+00A0 c2 a0 NO-BREAK SPACE U+00A1 ¡ c2 a1 INVERTED
EXCLAMATION MARK
U+00A2 ¢ c2 a2 CENT SIGN U+00A3 £ c2 a3 POUND SIGN
U+00A4 ¤ c2 a4 CURRENCY SIGN U+00A5 ¥ c2 a5 YEN SIGN
U+00A6 ¦ c2 a6 BROKEN BAR U+00A7 § c2 a7 SECTION SIGN
U+00A8 ¨ c2 a8 DIAERESIS U+00A9 © c2 a9 COPYRIGHT SIGN
U+00AA ª c2 aa FEMININE ORDINAL U+00AB « c2 ab LEFT-POINTING DOUBLE
INDICATOR ANGLE QUOTATION
MARK
U+00AC ¬ c2 ac NOT SIGN U+00AD c2 ad SOFT HYPHEN
U+00AE ® c2 ae REGISTERED SIGN U+00AF ¯ c2 af MACRON
U+00B0 ° c2 b0 DEGREE SIGN U+00B1 ± c2 b1 PLUS-MINUS SIGN
U+00B2 2 c2 b2 SUPERSCRIPT TWO U+00B3 3 c2 b3 SUPERSCRIPT THREE
U+00B4 ´ c2 b4 ACUTE ACCENT U+00B5 μ c2 b5 MICRO SIGN
U+00B6 ¶ c2 b6 PILCROW SIGN U+00B7 · c2 b7 MIDDLE DOT
U+00B8 ¸ c2 b8 CEDILLA U+00B9 1 c2 b9 SUPERSCRIPT ONE
U+00BA º c2 ba MASCULINE ORDINAL U+00BB » c2 bb RIGHT-POINTING
INDICATOR DOUBLE ANGLE
QUOTATION MARK
U+00BC ¼ c2 bc VULGAR FRACTION ONE U+00BD ½ c2 bd VULGAR FRACTION ONE
QUARTER HALF
U+00BE ¾ c2 be VULGAR FRACTION THREE U+00BF ¿ c2 bf INVERTED QUESTION
QUARTERS MARK
U+00C0 À c3 80 LATIN CAPITAL LETTER A U+00C1 Á c3 81 LATIN CAPITAL LETTER A
WITH GRAVE WITH ACUTE
U+00C2 Â c3 82 LATIN CAPITAL LETTER A U+00C3 Ã c3 83 LATIN CAPITAL LETTER A
WITH CIRCUMFLEX WITH TILDE
U+00C4 Ä c3 84 LATIN CAPITAL LETTER A U+00C5 Å c3 85 LATIN CAPITAL LETTER A
WITH DIAERESIS WITH RING ABOVE
U+00C6 Æ c3 86 LATIN CAPITAL LETTER AE U+00C7 Ç c3 87 LATIN CAPITAL LETTER C
WITH CEDILLA
U+00C8 È c3 88 LATIN CAPITAL LETTER E U+00C9 É c3 89 LATIN CAPITAL LETTER E
WITH GRAVE WITH ACUTE
U+00CA Ê c3 8a LATIN CAPITAL LETTER E U+00CB Ë c3 8b LATIN CAPITAL LETTER E
WITH CIRCUMFLEX WITH DIAERESIS
U+00CC Ì c3 8c LATIN CAPITAL LETTER I U+00CD Í c3 8d LATIN CAPITAL LETTER I
WITH GRAVE WITH ACUTE

Roche Diagnostics
E-114 Host Interface Manual · Version 1.02.05 (revision 1)
cobas® 8000 data manager 17 Text encoding tables
®
cobas 8000 instrument Western European characters in UTF-8

Unicode Name Unicode Name

UTF-8 (hex.)

UTF-8 (hex.)
Character

Character
code code
point point

U+00CE Î c3 8e LATIN CAPITAL LETTER I U+00CF Ï c3 8f LATIN CAPITAL LETTER I

WITH CIRCUMFLEX WITH DIAERESIS
U+00D0 Ð c3 90 LATIN CAPITAL LETTER ETH U+00D1 Ñ c3 91 LATIN CAPITAL LETTER
N WITH TILDE
U+00D2 Ò c3 92 LATIN CAPITAL LETTER O U+00D3 Ó c3 93 LATIN CAPITAL LETTER
WITH GRAVE O WITH ACUTE
U+00D4 Ô c3 94 LATIN CAPITAL LETTER O U+00D5 Õ c3 95 LATIN CAPITAL LETTER
WITH CIRCUMFLEX O WITH TILDE
U+00D6 Ö c3 96 LATIN CAPITAL LETTER O U+00D7 × c3 97 MULTIPLICATION SIGN
WITH DIAERESIS
U+00D8 Ø c3 98 LATIN CAPITAL LETTER O U+00D9 Ù c3 99 LATIN CAPITAL LETTER
WITH STROKE U WITH GRAVE
U+00DA Ú c3 9a LATIN CAPITAL LETTER U U+00DB Û c3 9b LATIN CAPITAL LETTER
WITH ACUTE U WITH CIRCUMFLEX
U+00DC Ü c3 9c LATIN CAPITAL LETTER U U+00DD Ý c3 9d LATIN CAPITAL LETTER Y
WITH DIAERESIS WITH ACUTE
U+00DE Þ c3 9e LATIN CAPITAL LETTER U+00DF ß c3 9f LATIN SMALL LETTER
THORN SHARP S
U+00E0 à c3 a0 LATIN SMALL LETTER A U+00E1 á c3 a1 LATIN SMALL LETTER A
WITH GRAVE WITH ACUTE
U+00E2 â c3 a2 LATIN SMALL LETTER A U+00E3 ã c3 a3 LATIN SMALL LETTER A
WITH CIRCUMFLEX WITH TILDE
U+00E4 ä c3 a4 LATIN SMALL LETTER A U+00E5 å c3 a5 LATIN SMALL LETTER A
WITH DIAERESIS WITH RING ABOVE
U+00E6 æ c3 a6 LATIN SMALL LETTER AE U+00E7 ç c3 a7 LATIN SMALL LETTER C
WITH CEDILLA
U+00E8 è c3 a8 LATIN SMALL LETTER E U+00E9 é c3 a9 LATIN SMALL LETTER E
WITH GRAVE WITH ACUTE
U+00EA ê c3 aa LATIN SMALL LETTER E U+00EB ë c3 ab LATIN SMALL LETTER E
WITH CIRCUMFLEX WITH DIAERESIS
U+00EC ì c3 ac LATIN SMALL LETTER I WITH U+00ED í c3 ad LATIN SMALL LETTER I
GRAVE WITH ACUTE
U+00EE î c3 ae LATIN SMALL LETTER I WITH U+00EF ï c3 af LATIN SMALL LETTER I
CIRCUMFLEX WITH DIAERESIS
U+00F0 ð c3 b0 LATIN SMALL LETTER ETH U+00F1 ñ c3 b1 LATIN SMALL LETTER N
WITH TILDE
U+00F2 ò c3 b2 LATIN SMALL LETTER O U+00F3 ó c3 b3 LATIN SMALL LETTER O
WITH GRAVE WITH ACUTE
U+00F4 ô c3 b4 LATIN SMALL LETTER O U+00F5 õ c3 b5 LATIN SMALL LETTER O
WITH CIRCUMFLEX WITH TILDE
U+00F6 ö c3 b6 LATIN SMALL LETTER O U+00F7 ÷ c3 b7 DIVISION SIGN
WITH DIAERESIS
U+00F8 ø c3 b8 LATIN SMALL LETTER O U+00F9 ù c3 b9 LATIN SMALL LETTER U
WITH STROKE WITH GRAVE
U+00FA ú c3 ba LATIN SMALL LETTER U U+00FB û c3 bb LATIN SMALL LETTER U
WITH ACUTE WITH CIRCUMFLEX

Roche Diagnostics
Host Interface Manual · Version 1.02.05 (revision 1) E-115
17 Text encoding tables cobas® 8000 data manager
Western European characters in UTF-8 cobas® 8000 instrument

Unicode Name Unicode Name

UTF-8 (hex.)

UTF-8 (hex.)
Character

Character
code code
point point

U+00FC ü c3 bc LATIN SMALL LETTER U U+00FD ý c3 bd LATIN SMALL LETTER Y

WITH DIAERESIS WITH ACUTE
U+00FE þ c3 be LATIN SMALL LETTER U+00FF ÿ c3 bf LATIN SMALL LETTER Y
THORN WITH DIAERESIS

Roche Diagnostics
E-116 Host Interface Manual · Version 1.02.05 (revision 1)