cobas® 8000 data manager

Host Interface Manual

Version 21

Software version 1.06.08

2

Publication information

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,
EP17-A.
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 acknowledgment 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 acknowledgment 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 April 2012 o Data added to quality control and calibration results to
improve traceability. (HL7 only.)
1.03.00 (revision 1) 1.03.00 February 2013 Minor corrections.
o In Result Queries and Order Queries, the rack type in ASTM
Q-3.2 and HL7 QPD-10 is specified as mandatory, to ensure
consistent responses.
o For calibration results, MSH-7 and H-14 contain the time of
calibration, not time of message creation.
o Warning on network security and resetting sample priority.
o Updated manufacturer address.
o Recommendation to use “By test” setting.
o Notice that instrument alarms are not sent to host.
Additional functionality.
o Sample IDs can be assigned a lifetime, after which they can
be re-used. If sample lifetimes are used, query messages
must include the sample’s rack type / specimen type.
o C-module supports additional dilution factors: 3, 5, 10, 20,
50.
o Support for Generation-6 (G6) servers, and the FortiGate-
40C firewall.
1.03.01 (revision 1) 1.03.01 August 2013 Minor corrections.
o More information on codes used for qualitative results on e-
modules.
Additional functionality.
o Limited STAT handling, to deal with delays caused by too
many STAT samples from a cobas ® 8100 instrument.
Data alarms
o New alarms 47, 100, plus corrections.
12 (Internal draft, not externally released.)
13 1.04 May 2014 o Upgraded data alarms, numbers 23, 26, 55, 59, and 60.
o STAT masking mode may assist certain busy systems with
many STAT samples.
o Generation 8 server. Before upgrading to a generation 8
server, consult your Roche Diagnostics Field Service
Representative or the cobas® 8000 data manager Service
Manual.
y Revision history

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 3

Manual version Software version Revision date Main changes

14 1.05 July 2014 o Forward instrument status mode enables the data manager
to forward instrument status and test availability information
to the host upon receipt from the control unit.
o Support for false bottom and non-standard tubes.
o Support for data point values in ASTM & HL7 result upload
messages.
o Enhanced support for order messages which contain invalid
test codes.
o Enhanced handling of sample container type values.
o Empty container type values no longer default to standard
cup type.
15 1.06 June 2016 o Support for the cobas e 801 module and the
cobas e flow test concept.
o Support for uploading results By cluster as well as By test
and By sample.
o The upload of raw data and data point values can be
manually enabled and disabled.
o Usage of EP17-A flags has changed.
o Three new sample types have been added to the sample list.
o Data alarm information updated and expanded. New alarm
also added: 113
o Several chapters of the manual have undergone a
restructuring and reorganization of information, in order to
improve clarity and consistency.
16 1.06.01 December 2016 The layout, format, and structure of the manual has been
substantially updated.
17 1.06.05 February 2018 For details of changes in this version, see What is new in
publication version 18 and New features in version 1.06.07 in
version 17 of the Host Interface Manual.
18 1.06.06 May 2018 There are no changes to the host interface with the release of
version 1.06.06.
19 1.06.07 January 2019 o OBX-1 description updated
o cobas e flow test result code table updated
20 1.06.08 May 2019 There are no changes to the host interface with the release of
version 1.06.08.
21 1.06.08 December 2019 u See What is new in publication version 21 (18)
y Revision history

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

Edition notice This document is intended for the users of cobas® 8000
data manager application, Software version 1.06.08.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
4

Every effort has been made to ensure that the information

contained in this manual is accurate at the time of
printing.

Roche Diagnostics International 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.

Where to find information For information on the individual components of the

cobas® 8000 data manager see:

The Safety Manual contains important safety

information. You must read the Safety Manual before
operating the instrument.

The Operator’s Manual focuses on routine operation

and maintenance. The chapters are organized according
to the normal operation workflow.

The Online Help contains the content of the Operator’s

Manual, Safety Manual and additionally:
• Troubleshooting information
• A software reference
• Configuration information
• Information about basic analytical principles

The PC manufacturer’s manual contains all information

about the hardware.

Training Do not carry out operation tasks or maintenance actions

unless you have received training from Roche
Diagnostics. Leave tasks that are not described in the
user documentation to trained Roche Service
representatives.

Screenshots The screenshots in this publication have been added

exclusively for illustration purposes. Configurable and
variable data, such as tests, results, or path names visible
therein must not be used for laboratory purposes.

Warranty Any customer modification to the system renders the

warranty or service agreement null and void.

For conditions of warranty, contact your local sales

representative or refer to your warranty contract partner.

Always leave software updates to a Roche Service

representative, or perform such updates with their
assistance.

Copyright © 2009-2019 F. Hoffmann-La Roche Ltd. All rights

reserved.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 5

License information The cobas® 8000 data manager software is protected by

contract law, copyright law, and international treaties. The
cobas® 8000 data manager contains a user license
between F. Hoffmann-La Roche Ltd. and a license holder,
and only authorized users may access the software and
use it. Unauthorized use and distribution may result in
civil and criminal penalties.

Open Source and Commercial Software The cobas® 8000 data manager may include
components or modules of commercial or open-source
software. For further information on the intellectual
property and other warnings, as well as licenses
pertaining to the software programs included in the
cobas® 8000 data manager, refer to the electronic
distribution included with this product.

This open source and commercial software and the

cobas® 8000 data manager as a whole can constitute a
device regulated in accordance with applicable law. For
more detailed information, refer to the user manual and
labeling.

Please note that the respective authorization is no longer

valid according to the corresponding legislation should
any unauthorized changes be made to the cobas® 8000
data manager.

Trademarks The following trademarks are acknowledged:

COBAS, MODULAR, and MODULAR ANALYTICS EVO

are trademarks of Roche.

All other trademarks are the property of their respective

owners.

Feedback Every effort has been made to ensure that this publication
fulfills the intended use. All feedback on any aspect of
this publication is welcome and is considered during
updates. Contact your Roche representative, should you
have any such feedback.

Approvals The following mark demonstrates compliance:

Complies with the IVD directive 98/79/EC on in vitro

diagnostic medical devices.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
6

Contact addresses

Manufacturer

Roche Diagnostics GmbH

Sandhofer Strasse 116
68305 Mannheim
Germany
Made in Switzerland

US distribution

Roche Diagnostics Corporation

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

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Table of contents 7

Table of contents

Publication information 2 Configuration

Contact addresses 6
Table of contents 7
6 Configuring the data manager
Intended use 11
Configuring the data manager 93
Symbols and abbreviations 11
The host connection 95
Safety information classification 14
Configuring the data manager host interface
Safety information 15
options 97
What is new in publication version 21 18
cobas e flow test-related settings 110
Getting a trace file from the data manager 123
Workflow overview Physical layer specifications 124

7 Configuring the control unit

1 Overview
Enabling communication with data
Purpose and scope 23
manager 133
Who this manual is for 24
Settings for communications with data
Content 25
manager 135
Result upload settings 140
2 System architecture
Getting a trace file from the control unit 144
Overview of the system 29
Overview of modules 30
LIS communications 31 ASTM reference
Text encoding 32
8 ASTM protocol (LIS2 - A2)
3 Sample processing
Overview of the ASTM protocol 151
Supported sample types 35
Communication processing layers 152
Processing samples 36
ASTM lower layer 153
Barcodes 37
ASTM message framing 154
Sample tubes and racks 39
ASTM syntax 155
Test selection 40
Message transmission phases 158
Sample container types 41
Checksum calculation / message frame 159
Repeat, rerun, and reflex tests 42
Batch and realtime processing 44
9 ASTM text content (LIS2 - A2)
Multiple test selection messages 47
List of record levels 163
Reusing sample IDs and sample lifetimes 48
List of messages used in host
Sample ID used with different sample types 50
communication 164
Identifying samples on the instrument 51
Description of ASTM records 167
Returning results to the host 52
Message Header Record 168
Patient Information Record 170
4 About cobas e flow tests
Order Record 171
Introducing the cobas e flow test 57
Comment Record (following Order Record) 177
What is a cobas e flow test? 58
Result Record 178
QC for cobas e flow tests 62
Comment Record (following Result Record) 187
About repeat, rerun, and reflex tests with
Query Record (Request Information
cobas e flow tests 70
Record) 189
Photometric Calibration Result M(PCR) 193
5 Communication scenarios and message types
ISE Calibration Result Record - M(ICR) 194
List of communication and message types 73
E-module (immunology) Calibration Result
Communication scenarios 74
Record - M(ECR) 197
Details of message types 77
Message Termination Record 199
Message flow 84

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
8 Table of contents

10 ASTM communication examples 13 HL7 acknowledgment handling

Low level trace file 203 Acknowledgment flags in messages from the
Test selection inquiry from data manager 204 data manager 297
Regular test patient result upload Acknowledgment flags sent in response to host
messages 207 messages 302
cobas e flow test result upload messages 214
Quality control uploads 219 14 HL7 communication examples
Calibration result uploads 221 Test selection inquiry and download 307
Result request from host and the data manager Regular test patient result upload
result upload 223 messages 310
Order query from the host 227 cobas e flow test result upload messages 315
Qualitative and cut-off index result
messages 336
HL7 reference Quality control result upload messages 339
cobas e flow test calculated QC result
11 HL7 protocol messages 344
Overview of HL7 235 Calibration result upload messages 347
Physical communication 236 Masking messages 349
Result requests from the host 350
12 HL7 text content Order requests from the host 354
HL7 messages 239 Instrument status and test availability
HL7 segment description 242 messages 357
Message Header Segment - MSH 243
Message Acknowledgment Segment -
MSA 245
Appendices
Patient Identification Segment - PID 246
Specimen Segment - SPM 247 15 Data alarms
Specimen Container Detail Segment - SAC 251 List of numerical code data alarms and output
Observation Request Segment - OBR 252 characters on the control unit 367
Timing Quantity Segment - TQ1 254 List of data alarms 370
Observation Result Segment - OBX 255 Data alarms of ISE tests 372
Measurement of c-module photometric Data alarms of photometric tests 383
Calibration Results 271 Data alarms of immunology tests 394
Measurement of ISE Calibration Results 272 Alarms for calibrations 406
Measurement of e-module immunological Data alarm for QC materials 417
Calibration Results 274 Rerun test list 419
Calibration alarm flags 276 Alarm priorities 421
Test Code Detail Segment - TCD 277
Substance Identifier Segment - SID 278 16 Instrument alarms
Comment Segment - NTE 280 Instrument alarms 425
Query Parameter Segment - QPD (for a test
selection inquiry) 282 17 Result message codes for cobas e flow tests
Query Parameter Segment - QPD (for a Result Result message codes 441
Query) 284
Query Parameter Segment - QPD (for an Order 18 Using MODULAR PRE-ANALYTICS
Query) 286 Sample IDs and barcodes 447
Response Control Parameter Segment - Handling query messages without
RCP 288 barcodes 448
Equipment Detail Segment - EQU (from host to Order of messages 449
data manager) 289 Handling batch test selections with strict rack
Equipment Command Segment - ECD 290 and position 451
Equipment Detail Segment - EQU (from data
manager to host) 291
Inventory Detail Segment - INV 293

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Table of contents 9

19 Identifying patient samples by sequence number

Identifying samples 457
Identifying patient samples by sequence
number 458
Important information for using sequence
numbers 460
Using sample sequence numbers in ASTM 462
Using sample sequence numbers in HL7 464
List of configuration settings for barcode and
sequence modes 466

20 Preparing the host communication

General differences in the ASTM protocol 469
Differences in ASTM message definitions 473
Other differences 482
LIS communications 483
Identifying samples by sequence number 484
Traceability information for quality control and
calibration results 485

21 Text encoding tables

ASCII character codes 489
Western European characters in UTF-8 490

Glossary

22 Glossary

Index
Index 505

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
10 Table of contents

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 11

Intended use

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.

Symbols and abbreviations

Symbols used in the publication

Symbol Explanation
o List item
u Related topics containing further information
Tip. Extra information on correct use or useful
q
hints.
r Start of a task
I Extra information within a task
f Result of an action within a task.
c Frequency of a task.
n Duration of a task.
d Materials that are required for a task.
j Prerequisites of a task.
u Topic. Used in cross-references to topics.
p Task. Used in cross-references to tasks.
Figure. Used in figure titles and cross-
w
references to figures.
Table. Used in table titles and cross-references
y
to tables.
y Symbols used in the publication

Abbreviations The following abbreviations are used.

Abbreviation Definition
A
ACN Application Code Number. Unique reference
number to identify and to manage
downloaded files across the whole system,
e.g. parameter files for applications, QC
materials, calibrators, etc.
ADC apparent diffusion coefficient
ANSI American National Standards Institute
ASCII American Standard Code for Information
Interchange
y Abbreviations used in the manual

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
12

Abbreviation Definition
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
Embedded test A test which is part of a cobas e flow test. It
cannot be ordered separately.
EMF electromotive force
EP17-A Protocols for Determination of Limits of
Detection and Limits of Quantitation;
Approved Guideline (NCCLS standard)
F
FIFO First in first out
H
HIS Hospital Information System
HL7 Health Level 7
HPE High Priority Elecsys test: first processed in an
e-module, before the sample is moved to a c-
module for further testing.
HU High uncertainty (outside the range in which
results are reliable)
I
i.e. id est – that is to say
IS Internal Standard (ISE module)
ISE ion selective electrode
K
K Potassium
L
y Abbreviations used in the manual

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 13

Abbreviation Definition
LECIS Laboratory Equipment Control Interface
Specification
LIS Laboratory Information System
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 QC refers to methods to ensure the reliability
Control) and consistency of reagents and the results
based on reactions using the reagents, on a
per application basis.
This document distinguishes between 2 types
of QC:
o Single QC (or measured QC)
o Calculated QC
A single QC is measured on the instrument
and refers to an embedded test or regular
test.
A calculated QC is calculated with a
mathematical formula and refers to a
cobas e flow test.
R
REF Reference solution for ISE module
Regular test Test that can be ordered separately. This is
the opposite of an embedded test. Also
known as "normal test".
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
XSL Extensible Stylesheet Language
XSLT Extensible Stylesheet Language
Transformation
y Abbreviations used in the manual

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
14

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
Warning
r Indicates a potentially dangerous situation which, if
ignored, may lead to fatal or severe injuries.

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

NOTICE
Notice
r 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.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 15

Safety information

Pay careful attention to the following safety information.

System safety Failure to observe the following safety information may

result in incorrect results, data corruption, and data
losses.

! CAUTION
Incorrect or corrupt data resulting from incorrect
operation, the use of wrong components, or poor
security measures
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.

! CAUTION
Incorrect or corrupt data due to unauthorized
access
r Access to your data and the configuration should only
be granted to authorized experts.

! CAUTION
Separate the data manager - LIS network from the
laboratory network
r Separate the data manager - LIS network from the
laboratory network and use a protected design of
server software including a multi-layer defense
network setup.

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

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
16

! CAUTION
Maintenance
Data loss or damage to the system due to power
failure.
r Ensure regular maintenance of the uninterruptible
power supply.

! WARNING
Laboratory workflows
Incorrect results due to lack of calibration and
quality control
r Interrupt the analysis of patient samples if you change
the reagent until the instrument has been recalibrated
and quality-controlled.

! WARNING
Incorrect results due to expired calibration and
quality controls
r Perform regular quality controls and calibrations.

! WARNING
Incorrect results due to incorrect entry
r Ensure that manually entered data is correct.

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

! CAUTION
Danger of samples being mixed up due to incorrect
assignment of the barcode to the tube
r 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 data
manager Operator’s Manual and the cobas® 8000
modular analyzer series Operator’s Manual.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 17

! CAUTION
Incorrect results due to lack of knowledge of the
Standard Operating Procedures
r Use the SOP function of the system to give laboratory
staff access to written instructions (SOP) while they
work. For details of the SOP function, see the cobas®
8000 data manager Operator’s Manual and the cobas®
8000 modular analyzer series Operator’s Manual.

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

! CAUTION
Unreliable validation due to unauthorized changes
to the validation and calculation rules.
r 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.

! CAUTION
Third-party software
Malfunctions and incorrect results due to third-
party software
r The installation of third-party software that has not
been approved by Roche Diagnostics may lead to
malfunctions. Do not install any unapproved software.

NOTICE
Supported protocols
The data manager supports a subset of the HL7 and
ASTM LIS2-A2 protocols, with proprietary variations
The data manager supports a specific proprietary
variation from the HL7 and ASTM LIS2-A2 standard
protocols.
r Test your interface to the data manager in a test
environment with a full range of possible messages
before using it live. After reconfiguring the data
manager, fully test the interface again in the same
way.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
18

What is new in publication version 21

cobas e flow test result codes The list of result codes sent with cobas e flow test results
has been updated.
• The wording of the result messages has been aligned
and updated.
• Codes 86-120 have been added.
u Result message codes (441)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Workflow overview

1 Overview .................................................................................................................... 21
2 System architecture............................................................................................... 27
3 Sample processing ................................................................................................ 33
4 About cobas e flow tests ................................................................................... 55
5 Communication scenarios and message types........................................... 71

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 21
Table of contents

Overview 1

This section gives a basic overview of the purpose and

scope of this manual.

In this chapter 1
Purpose and scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Who this manual is for. . . . . . . . . . . . . . . . . . . . . . . . . . 24
Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

1 Overview

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 22
Table of contents
1 Overview

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Purpose and scope 23

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. Refer to the cobas® 8000 data
manager 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.

1 Overview

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 24 Who this manual is for

Who this manual is for

This manual is written for:
• Developers of Hospital Information Systems /
Laboratory Information Systems (HIS/LIS), who need
to create programs that connect to the cobas® 8000
data manager.
• Authorized Roche Diagnostics personnel who need to
configure or troubleshoot the host communications of
the cobas® 8000 data manager.
1 Overview

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Content 25

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

1 Overview

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 26
1 Overview Content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 27
Table of contents

System architecture 2
Overview of the cobas® 8000 data manager and
cobas® 8000 modular analyzer series 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.

In this chapter 2
Overview of the system . . . . . . . . . . . . . . . . . . . . . . . . . 29
Overview of modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
LIS communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Text encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2 System architecture

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 28
Table of contents
2 System architecture

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Overview of the system 29

Overview of the system

The cobas® 8000 data manager is a 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 a Work Area Manager (WAM).

The cobas® 8000 modular analyzer series consists of 2

types of devices:
• 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.
• An instrument that consists of:
- Several analytical modules that physically measure
the samples using various reagents
- 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.

cobas® 8000 modular analyzer series

cobas® 8000 cobas® Roche

Host (LIS,
WAM, etc.) ASTM/HL7 data manager link
Diagnostics
e-services
2 System architecture

cobas® 8000
instrument cobas® 8000
control unit

cobas® cobas® cobas® cobas®

8000 8000 8000 8000
analytical analytical analytical analytical
module module module module

w Overview of the system

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 30 Overview of modules

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

ISE module The ISE module, or Ion-Sensitive-Electrode module,

performs clinical chemistry tests for analyzing levels of
the electrolytes Na, Cl, and K.

C-module The c-modules, c 502, c 701, and c 702, perform clinical

chemistry tests using photometry.

E-module The e-modules, e 602 and e 801 (also known as the

Elecsys modules), perform immunological tests.
2 System architecture

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 LIS communications 31

LIS communications
The LIS and data manager can communicate by
• HL7 over a TCP/IP network connection
• ASTM over a TCP/IP network connection
• ASTM over a serial connection

Details u For details of how to select a connection, see Starting

and stopping the host connection (95).
u For details of the connections, see Physical layer
specifications (124).
u For details of the HL7 protocol used, see HL7
protocol (233) and HL7 text content (237).
u For details of the ASTM protocol used, see ASTM
protocol (LIS2 - A2) (149) and ASTM text content
(LIS2 - A2) (161).

q 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
than two c701 or c702 (including ISE) modules, where the
number of samples per hour and tests per sample is very
high.

2 System architecture

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 32 Text encoding

Text encoding
The data within the message must be Unicode encoded
as UTF-8 characters. The UTF-8 characters between 32-
127 are the same as those used by ASCII. If characters
outside this range are used, care should be taken.
Characters from 0 to 31 are control characters and
therefore cannot be used.

Only UTF-8 encoding is supported.

! WARNING
The host needs to handle UTF-8
r In situations where the data manager operators will be
able to enter UTF-8 characters, the 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.
u For the UTF-8 codes of common Western European
characters, see Western European characters in UTF-
8 (490).
2 System architecture

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 33
Table of contents

Sample processing 3

This chapter explains how samples are processed in the

cobas® 8000 data manager.

In this chapter 3
Supported sample types . . . . . . . . . . . . . . . . . . . . . . . . 35
Processing samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Barcodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Sample tubes and racks . . . . . . . . . . . . . . . . . . . . . . . . 39
Test selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Sample container types . . . . . . . . . . . . . . . . . . . . . . . . . 41
When received from the host . . . . . . . . . . . . . . . . . 41
When received from the control unit . . . . . . . . . . . 41
Repeat, rerun, and reflex tests . . . . . . . . . . . . . . . . . . . 42
Batch and realtime processing . . . . . . . . . . . . . . . . . . . 44
Batch and realtime and the data manager . . . . . . 44
Batch and realtime modes. . . . . . . . . . . . . . . . . . . . 44 3 Sample processing
Configuring the data manager for the host
modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Multiple test selection messages . . . . . . . . . . . . . . . . . 47
Reusing sample IDs and sample lifetimes . . . . . . . . . 48
Sample ID used with different sample types . . . . . . . 50
Identifying samples on the instrument . . . . . . . . . . . . 51
Returning results to the host . . . . . . . . . . . . . . . . . . . . 52
Passing results automatically to the host . . . . . . . 52
System time and result handling . . . . . . . . . . . . . . 52
EP17-A and the result abnormal flags . . . . . . . . . . 53
Result suppression for results outside the
technical limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 34
Table of contents
3 Sample processing

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Supported sample types 35

Supported sample types

The cobas® 8000 data manager supports the use of
several types of samples:
• Serum / Plasma
• Urine
• Cerebrospinal Fluid
• Supernatant
• Other fluids
• Whole blood
• Oral fluids (Saliva)
• Hemolysate (only supported by e 801 module)
• Amniotic fluid (only supported by e 801 module)
• Processed stool (only supported by e 801 module)

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.

For full information on supported sample types, see the

cobas® 8000 data manager Operator’s Manual and 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.

3 Sample processing

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 36 Processing samples

Processing samples
Sample material is supplied to the instrument in “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 16 mm 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. The instrument
identifies the cup or container type from the rack ID.

False bottom and non-standard tubes are also supported.

Rack ranges for all types of tubes are defined on the

control unit. For more information, see the Rack
assignment section of the cobas® 8000 modular analyzer
series Operator’s Manual.

If necessary, the sample’s actual container or cup size is

indicated in communications between the host and the
data manager.
u For more information, see Sample container types (41)

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.
3 Sample processing

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Barcodes 37

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 2 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 modular analyzer series 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 and specimen type
as a unique identifier for the sample.

Missing barcodes By default, if the cobas® 8000 modular analyzer series

instrument cannot read a sample’s barcode, it generates
an error. The operator of the cobas® 8000 modular
analyzer series 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.
u For more information on how to use this function, see
Identifying patient samples by sequence
number (455). 3 Sample processing

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 38 Barcodes

MODULAR PRE-ANALYTICS If a MODULAR PRE-ANALYTICS is used, the samples

may lack barcodes. In this situation, the cobas® 8000
modular analyzer series 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.
u For more information on how to use this function, see
Using MODULAR PRE-ANALYTICS (445).
u To configure the cobas® 8000 modular analyzer
series instrument to process samples coming from a
cobas® 8000 modular analyzer series instrument
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 (137).
3 Sample processing

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Sample tubes and racks 39

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 data manager
Operator’s Manual and 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 (if the
instrument is not connected to cobas® connection
modules). These racks take a higher priority in the
cobas® 8000 modular analyzer series 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.

3 Sample processing

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 40 Test selection

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

As users can reconfigure the cobas® 8000 modular

analyzer series 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.
u For more details about the order of messages, see
Sample processing (33).
3 Sample processing

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Sample container types 41

Sample container types

Both the host and the control unit send values which tell
the data manager the type of container used by a sample
in an order. These values are sent in fields SPM-27 and
QPD-11 (HL7), or fields O-4.6 and Q-3.9 (ASTM). Users
can also define these values on the data manager itself
(if, for example, the host is unavailable).

The data manager handles these values as follows.

When received from the host

The data manager stores values received from the host in
test selection information messages, and forwards them
to the control unit. The control unit will reject an order if
the container type value sent from the data manager is
different to the container type of the corresponding
sample on the instrument.

If a rack contains transferred samples The RFM module (reformatter) of the cobas® 8100
automated workflow series receives samples scheduled
for online analysis and places them into 5-position racks
compatible with analytical instruments.

The control unit accepts any container type values from

the host for racks that contain transferred samples.
However, if the data manager sends no container type
value for a rack that contains transferred samples, the
control unit rejects the order.

If an order contains no container type value The control unit accepts orders which contain no
container type value, unless the order is for a rack which
contains transferred samples.
3 Sample processing
Note that, if the host sends no container type value to
data manager 1.05 or above, then data manager 1.05 or
above sends no value to the control unit. In previous
versions of data manager, empty container type values
defaulted to the standard cup type.

When received from the control unit

The data manager forwards values received in test
selection inquiry messages from the control unit to the
host. However, the data manager does not store these
values.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 42 Repeat, rerun, and reflex tests

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 necessary.
u 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 modular analyzer
series instrument or on the data manager manually or
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 modular
analyzer series instrument, if corresponding rules are
programmed at the LIS.

! CAUTION
Use reflex rules either only on the data manager or
3 Sample processing

only on the host

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

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
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Repeat, rerun, and reflex tests 43

cobas e flow tests Rerun and reflex are not supported for
cobas e flow tests.

Repeat cobas e flow tests can either be ordered via the

LIS, or manually on the data manager. (Automatic
ordering is not possible.)

Repeat, rerun, and reflex cannot be ordered for

cobas e flow tests via the data manager rule engine.
u For more information, see About repeat, rerun, and
reflex tests with cobas e flow tests (70)
u For details of how to configure and execute
cobas e flow tests, see the cobas® 8000 data
manager Operator’s Manual.

3 Sample processing

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 44 Batch and realtime processing

Batch and realtime processing

This section gives an overview of the message flow
between the cobas® 8000 modular analyzer series
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 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 test selection downloads in one of
three ways:
3 Sample processing

• Batch mode: all test selection downloads are batch

downloads.
• Realtime mode: and all test selection downloads are
realtime downloads.
• 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.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Batch and realtime processing 45

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:
• whenever the data manager receives a test selection
request from the cobas® 8000 modular analyzer
series,
or
• 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.

To work with mixed mode, configure the data manager to

send a query to the host when:
• the data manager receives a test selection request
from the analyzer,
and
• 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.

3 Sample processing
Configuring the data manager for the host modes
To work in these modes, some settings have to be
configured in data manager under Workplaces > cobas
8000 data manager Service > Service-related
configuration > Interface Options.
u For details of setting the modes, see Test selection
inquiry message settings (99).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 46 Batch and realtime processing

The cobas® 8000 modular analyzer series 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.
u For information on this setting, see Test Selection
Inquire Always (137).

No parameter is passed to the host to indicate which

mode data manager and cobas® 8000 modular analyzer
series 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.
u Detailed examples of the order of messages in specific
cases is given in Message flow (84).
3 Sample processing

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Multiple test selection messages 47

Multiple test selection messages

In realtime mode or the mixed mode, it is possible that the
data manager will have test selections for an active
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.

If the data manager has no test selections for an active

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.

If the sample’s lifetime has expired, it is no longer active,

and you can reuse the sample ID without combining the
two.
u For configuring sample lifetimes, see the cobas® 8000
data manager Operator’s Manual.

3 Sample processing

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 48 Reusing sample IDs and sample lifetimes

Reusing sample IDs and sample lifetimes

You can set a “sample lifetime” in Workplaces > cobas
8000 System Configuration > System configuration
> Sample lifetime option.

Select or clear the Enable check box to enable or disable

sample lifetimes, and specify the sample lifetime in either
hours or days. You can also disable this feature by
entering a sample lifetime unit of 0.

The sample lifetime feature is disabled by default. When

enabled, the default lifetime value is 12 hours.

Sample lifetime disabled If the samples have an indefinite lifetime, then data
manager stores each sample ID until the database is
cleared. In this situation, you can only use a sample ID
once until the database is cleared again. If the host sends
a test selection for an existing sample ID, the data
manager adds the tests to the existing sample, and
overwrites the previous patient data with the new patient
data.

Sample lifetime enabled If the samples have a limited lifetime, you can reuse a
sample ID after it has expired. The old sample ID is no
longer active, and the tests, results, and patient data are
separate.
u For configuring sample lifetimes, see the cobas® 8000
data manager Operator’s Manual.
u For clearing the database, see the cobas® 8000 data
manager Service Manual.

Cancelation and closure of samples When a sample approaches the end of its lifetime, it
enters the Canceling state. By default, this happens 5
minutes before the end of a sample’s lifetime. When the
sample enters the Canceling state, all previously
3 Sample processing

measured test results are reported to the host. However,

no other host communication takes place while the
sample is in this state.

The Canceling state persists until the sample is closed,

either manually or by the sample reaching the end of its
lifetime. Once closed, the sample is considered inactive.

Closed samples have the following properties:

• The sample cannot be edited
• Repeat, rerun, and reflex tests cannot be performed
on the sample
• No host communication takes place - any new results
received for the sample are not sent to the host

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Reusing sample IDs and sample lifetimes 49

! WARNING
If using sample IDs with limited lifetimes, identify
samples also by timestamp.
r If your sample IDs have a limited lifetime, then there
may be several samples in the data manager database
with the same sample ID. In an answer to an order or
result query, the test selection upload includes the test
orders or results for active samples with that ID.
r The orders for expired samples might be confused
with orders or results for current samples, or with
previous orders for samples that are now expired.
Avoid this, and identify samples, orders, and results by
timestamp, as well as by ID.

u For using sample ID lifetimes with result and order

queries, see Order and result queries with limited
sample lifetime (81).

3 Sample processing

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 50 Sample ID used with different sample types

Sample ID used with different sample types

The data manager treats two samples with the same
sample ID, but different sample types (or “rack types”), as
different samples. Therefore it treats the following as two
separate samples:

Sample ID Sample type (Rack type)

101234 S1
101234 S2
y Two samples with the same sample ID but different sample
types

The following example messages show test selection

inquiry messages sent from the data manager to the host.

A sample with ID 101234, and with rack type S1:

MSH|^~\&|cobas 8000||host||20171201160558||TSREQ|21655||2.5||||ER||UNICODE UTF-8|

QPD|TSREQ|21655|101234||50461|1||||S1|SC|R1|R|
RCP|I|1|R|

is treated as a different sample from this one, which has

the same sample ID, but which has rack type S2:

MSH|^~\&|cobas 8000||host||20171201160603||TSREQ|21655||2.5||||ER||UNICODE UTF-8|

QPD|TSREQ|21655|101234||50461|1||||S2|SC|R1|R|
RCP|I|1|R|

! CAUTION
Always give rack types if using sample lifetime
r If you set sample lifetime to enabled, send the rack
type (“specimen type” or “sample type”) with an order
or result query.

u Related topics
3 Sample processing

• For a graphical example of the workflow described

above, see Order and result queries with limited
sample lifetime (81).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Identifying samples on the instrument 51

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 modular analyzer series
instrument reads the barcodes on the sample tubes, and
uses the number on the barcode as a sample ID. The
barcode string and specimen type uniquely identify 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 modular analyzer series 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 modular analyzer series instrument,
described in the cobas® 8000 modular analyzer series
Operator’s Manual.

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.
u For a general overview of barcodes and Test Selection
queries, see Processing samples (36).
u For a description of how to implement a connection to
a MODULAR PRE-ANALYTICS, see Using MODULAR
PRE-ANALYTICS (445).
3 Sample processing
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.
u To learn how to use this functionality, see Identifying
patient samples by sequence number (455).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 52 Returning results to the host

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
modular analyzer series 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.

Calibration results do not wait for validation, but if not set

to “pass-through mode”, they are not uploaded to the
host. Even if calibration results are not passed to the host,
they are available from the TraceDoc.
u To see how to set “pass-through mode”, see Pass-
through mode (103).

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
3 Sample processing

technical validation.
u If results are not being sent to host immediately after
they are available, check your Result Upload Settings
in the control unit. See Result upload settings (140).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Returning results to the host 53

EP17-A 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 EP17-A standard.

The original EP17-A flags (obsolete as of The EP17-A standard of 2004, created by the CLSI,
version 1.06) provided three flags, Limit of Blank, Limit of Detection,
and Limit of Quantitation. Some older data manager
modules may use the flags from the 2004 EP17-A
standard. The data manager provides an enhancement to
the ASTM and HL7 result abnormal flags, showing a
violation of one of these limits.

In versions of data manager prior to 1.06, the following

result EP17-A flags were used:
• LoB
• LoD
• LoQ
u For details of this EP17-A standard, 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.

The current EP17-A flag The data manager adopted an updated standard in 2014
to replace the older EP17-A flags. This provides one flag,
Higher Uncertainty. Modules use this flag to show that a
result is below the measurable range.
3 Sample processing
Higher Uncertainty ( HU ) shows that the test result is in
the detectable range, but only at a level which is so low
that the result value is highly unreliable. A numeric result
is reported.

Configuring the EP17-A flag The higher uncertainty limit for each analyte is
configurable in the data manager. For details, see the
cobas® 8000 Online Help.

Result abnormal flag for cobas e flow tests An additional generic result abnormal flag is provided for
cobas e flow tests. This flag is sent in the main result of a
cobas e flow test when at least one embedded test
includes additional information, for example, violation of
the higher uncertainty limit.
• eFlow.W

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 54 Returning results to the host

This flag is sent in the same field as the EP17-A flag.

u For details of the flags passed to the host in ASTM,
see Result Record (178).
u For details of the flags passed to the host in HL7, see
Observation Result Segment - OBX (for patient
results) (255).

Result suppression for results outside the technical limit

For regular tests, you can choose whether to suppress
results that are outside the technical limit.

To enable or disable result suppression, navigate to

Workplaces > cobas 8000 data manager System
Configuration > System configuration > Result
suppression [tab], and select or clear the Result
suppression for results outside of technical limit
check box.

Result suppression is disabled by default.

If enabled If result suppression is enabled, the data manager

replaces result values that are outside of the technical
limit with 7 spaces in messages to the host.

Also, a string of 7 asterisks (*******) is shown for these

results on the data manager user interface, on print outs,
and in TraceDoc.

If disabled If result suppression is disabled, the data manager

uploads the result values to the host as they are displayed
on the control unit. These result values are also displayed
on the data manager user interface, on print outs, and in
TraceDoc.
3 Sample processing

For cobas e flow tests Suppressed and omitted results are handled differently
for cobas e flow tests.
u For information about configuring omitted result
reporting for cobas e flow tests, see Configuring
omitted result reporting (114)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 55
Table of contents

About cobas e flow tests 4

This chapter gives a general introduction to the basic

operation of the cobas e flow test functionality.

In this chapter 4
Introducing the cobas e flow test . . . . . . . . . . . . . . . . 57
What is a cobas e flow test? . . . . . . . . . . . . . . . . . . . . 58
QC for cobas e flow tests. . . . . . . . . . . . . . . . . . . . . . . 62
About repeat, rerun, and reflex tests with
cobas e flow tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

4 About cobas e flow tests

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 56
Table of contents
4 About cobas e flow tests

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Introducing the cobas e flow test 57

Introducing the cobas e flow test

This chapter gives a general introduction to the
cobas e flow test feature.

Assumptions and dependencies Only the cobas e 801 module supports

cobas e flow tests. Other cobas® 8000 data manager
modules, for example cobas e 602, do not support
cobas e flow tests.

4 About cobas e flow tests

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 58 What is a cobas e flow test?

What is a cobas e flow test?

The cobas e 801 module supports cobas e flow tests to
improve the turnaround time and minimize the error rate.

A cobas e flow test consists of a pre-defined group of

tests, known as “embedded tests”. These tests are
combined into a sequence or set of sequences connected
by a decision-making algorithm.

Therefore, the operator does not need to order each test

individually, or assess the results of each test to decide
which test to order next. Instead, the operator orders just
one cobas e flow test. The system orders the tests, and
automatically assesses each result to decide on which
tests to order next.

Roche Diagnostics provides the full definition of the

cobas e flow test package. The definition is not editable,
and embedded tests cannot be ordered separately.

Order cobas eÁRZWHVW 2UGHUHPEHGGHGWHVWV

LIS / MW 'DWD &RQWURO
V\VWHP manager XQLW
cobas eÁRZWHVWUHVXOW (PEHGGHGWHVWUHVXOWV
cobas eÁRZWHVW´$%&µ
Measure
(PEHGGHGWHVW'

>1HJDWLYH@ >3RVLWLYH@

Report Measure
0DLQUHVXOWWHVW' (PEHGGHGWHVW$
(PEHGGHGWHVW)

Report
0DLQUHVXOWWHVW)
6XEUHVXOWWHVW$
6XEUHVXOWWHVW'
4 About cobas e flow tests

w cobas e flow test execution

To obtain a cobas e flow test, download them from the

cobas® 8000 data manager.

The following items also have to be installed to be able to

run the cobas e flow test on the cobas e 801 module:
• All required embedded tests on the control unit
• All required calibrators and QC materials on the
control unit before running embedded tests

For more information on obtaining and installing

cobas e flow tests, see the cobas® 8000 data manager
Operator’s Manual.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 What is a cobas e flow test? 59

cobas e flow test results Each cobas e flow test provides a main result and
potentially one or more subresults. Depending on the
embedded test results during execution, a cobas e flow
test can report different result types, units, and/or a
different number of subresults.

cobas eÁRZWHVW´$%&µ

Measure
Embedded test D

>1HJDWLYH@ >3RVLWLYH@

Report Measure
- Main result test D Embedded test A
Embedded test F

Generate
Generated result B1
Generated result B2

Report
- Main result B1
- Subresult: test A
- Subresult: test F

4 About cobas e flow tests

- Subresult: test D
- Subresult: B2

w Example cobas e flow test

The main and subresults of a cobas e flow test can be:

• a measured result of one of its embedded tests
• a generated result of a cobas e flow test

Subresults provide additional information for the user.

Therefore, they can be reported to host systems as
supplementary information, for example, for the following
reasons:
• Traceability
• Archiving of results
• Troubleshooting

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 60 What is a cobas e flow test?

The following diagram shows an example for a

successfully processed cobas e flow test “HIV Duo” with
its main and subresults:

cobas eÁRZWHVW´+,9'XRµ

0DLQUHVXOW +,9'XR  ´5HDFWLYHµ>&2,@

6XEUHVXOW JHQHUDWHGUHVXOW´$QWL+,9µ ´1RQ5HDFWLYHµ>&2,@

6XEUHVXOW JHQHUDWHGUHVXOW´+,9$Jµ ´5HDFWLYHµ>&2,@

6XEUHVXOW HPEHGGHGWHVW´$QWL+,9µ *******

6XEUHVXOW HPEHGGHGWHVW´+,9$Jµ *******

w Example cobas e flow test with main result and subresults

The definition of the cobas e flow test specifies the units

and type of the main result, as well as the units, number,
and types of any subresults. The definition is not
configurable.

NOTICE
Only specified subresults are reported
Subresult values are reported only if the cobas e flow
test, as defined by Roche Diagnostics, calls for them to be
reported. Otherwise they are suppressed.
4 About cobas e flow tests

The following table shows all possible result types of

cobas e flow test main or subresults including their
units:

Result type Example [unit]

A quantitative value as result of a measured embedded test 2.33 [U/mL]
A qualitative value derived from the measured results “Repeatedly reactive”
(without any unit)
A qualitative value derived from the measured results, plus a corresponding quantitative “Non Reactive”, 1.20 [COI]
value as COI (Cut-off index)
A qualitative value derived from the measured results, plus a corresponding quantitative “Avidity High”, 65 [%]
value
A quantitative value as result of a measured embedded test, plus a corresponding qualitative 3.12 [mmol/L], "Non Reactive"
value
y Result types returned by cobas e flow tests

Note that the qualitative/quantitative and

quantitative/qualitative result types are only available for
cobas e flow tests.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 What is a cobas e flow test? 61

NOTICE
Perform calibration and QC tests separately from
the cobas e flow test
r To use cobas e flow tests, be sure to calibrate and
perform QC on all embedded tests and tests involved
in the cobas e flow test.

Generic data alarm When data alarms or errors occur during the
measurement of embedded tests, the data manager flags
the cobas e flow test main result with a generic data
alarm “eFlow.E”. The specific data alarm is visible in the
result message of the embedded test.

Cancellation An error in an embedded test may stop the processing of

the cobas e flow test. For example, if there is a sample
short error, no numeric result value can be determined. In
this case, the system cancels any further actions, and
marks the cobas e flow test with the data alarm
“eFlow.E”. Any available test results or subresults are
reported to the host.

After solving the problem, the operator has to reorder the

cobas e flow test from the host or the data manager.

4 About cobas e flow tests

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 62 QC for cobas e flow tests

QC for cobas e flow tests

In order to ensure the accuracy and quality of patient
results, the system validates the results against the status
of their corresponding QC results.

The data manager calculates the calculated QC value

which is used in cobas e flow tests.

A calculated QC is a result calculated by a defined

formula. It is needed as a combined QC result for
cobas e flow tests.

For QC of a cobas e flow test, the following types of QC

results are considered:
• Single QC
• Calculated QC

Single QC definition Single QC means a single QC result for each measured

embedded test.

cobas eÁRZWHVW Single QC2 (HBSAGQE, MC1): 0.01 [IU/mL]

“HBSAG Q D”
Single QC3 (HBSAGQE, MC1) 0.01 [IU/mL]

w Single QC

Calculated QC definition Calculated QC means QC results for "linked tests" or

"linked kits" within a cobas e flow test. This is provided
by Roche Diagnostics.
4 About cobas e flow tests

Calculated QC3 for “HIV Duo”: 0.650 [COI]

cobas eÁRZWHVW
“HIV Duo” Single QC1 (HIV Ag, MC1): 0.375 [COI]

Single QC4 (Anti HIV, MC2): 0.531 [COI]

w Calculated QC

For details of linked tests and linked kits, see the next
section.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 QC for cobas e flow tests 63

Calculated QC for linked tests or linked kits A cobas e flow test may measure multiple embedded
tests during its execution. The embedded tests can be
specified as a set of combined embedded tests (linked
tests) or combined cobas e packs (linked kits).
Therefore, there are dependencies between embedded
tests or cobas e packs. The definition of the linked tests
or linked kit forces the instrument to measure the tests in
a certain order of pipetting.

The cobas® 8000 data manager can generate a

pipetting sequence calculated QC result using a pre-defined formula based
on a specific cobas e flow test. The calculated result is
based on the single QC results of the embedded tests in
the cobas e flow test. When a cobas e flow test is
ACN 11150 ACN 11151 installed on the cobas® 8000 modular analyzer series,
CMVA IGG CMVA AVI the calculated QC functionality is automatically installed
and enabled with it.

Link However, not all cobas e flow tests have a calculated QC

cobas eÁRZWHVW value. There is only at most one formula for calculated QC
per cobas e flow test. However, more than one
“CMV AVI” ACN 12001
calculated QC value can be reported, depending on the
as “Linked test” assigned measuring cell.

Since the cobas e 801 module has 2 measuring cells, it

pipetting sequence
can happen that different measurements can be
performed on different measuring cells. For example, the
cobas e flow test “HIV Duo” has 2 embedded tests, “HIV
Ag” and “Anti HIV”: the system has to calculate 4
ACN 11014 ACN 11013
calculated QC values, one for each combination of
HIV Ag Anti HIV
module, measuring cell, and QC level (QC lot number).

Link

4 About cobas e flow tests

cobas eÁRZWHVW
´+,9'XRµ$&1
as “Linked kit”

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 64 QC for cobas e flow tests

The following example shows calculated QCs for the

cobas e flow test “HIV Duo” on a cobas e 801 module
with 2 measuring cells, “MC1” and “MC2”:

Calculated QCs for cobas eÁRZWHVW´+,9'XRµ

HPEHGGHGWHVWV´$QWL+,9+,9$Jµ

cobas e 801 module,QVWDOOHGHPEHGGHGWHVWRQPHDVXULQJFHOO 0&

+,9$J $QWL+,9 +,9$J $QWL+,9

0& 0& 0& 0&

6LQJOH4&1 6LQJOH4&2 6LQJOH4&3 6LQJOH4&4

Calculated QC1+,9'XR Calculated QC2+,9'XR

+,9$J0&$QWL+,90& +,9$J0&$QWL+,90&

Calculated QC3+,9'XR Calculated QC4+,9'XR

+,9$J0&$QWL+,90& +,9$J0&$QWL+,90&

w Complete example for all combinations for calculated QC for two embedded tests on different modules

The following diagram shows an example result of a

calculated QC including its corresponding single QC
result values.
4 About cobas e flow tests

Calculated QC3 for “HIV Duo”: 0.650 [COI]

(HIV Ag, MC1 - Anti HIV, MC2)

Single QC1 (HIV Ag, MC1): 0.375 [COI]

Single QC4 (Anti HIV, MC2): 0.531 [COI]

w Example calculated QC and corresponding single QC values

For each measurement of linked tests or embedded tests

referred to linked kits during the cobas e flow test
execution, the appropriate calculated QC result must be
used for cobas e flow test validation.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 QC for cobas e flow tests 65

For each QC result that is used by an embedded test in

the cobas e flow test, the data manager performs a
calculation taking into account the following
components:
• QC material
• Module
• Measuring cell

The calculated QC result is displayed in the Test details

panel on the Additional data tab of the cobas e flow
test.

q If one or both of the measured QC results of the

embedded tests is marked with the status Error, the
calculated final QC result is marked with the status Error
as well.

About QC result validation of a cobas e flow In order to validate cobas e flow test results (if
test result configured), the system considers all relevant QC results
(single QC measurements as well as calculated QCs).

The following diagram shows which QC results are

relevant to validating a cobas e flow test.

4 About cobas e flow tests

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 66 QC for cobas e flow tests

cobas eÁRZWHVW´$%&µ cobas eÁRZWHVW4&

Measure 0HDVXUHG4&IRU
Embedded test D HPEHGGHGWHVW´'µ
&RQWURO/RW1R

>1HJDWLYH@ >3RVLWLYH@

Report Measure &DOFXODWHG4&IRU

- Main result test D Embedded test A cobas eÁRZWHVW´$%&µ
Embedded test F &RQWURO/RW1R

0HDVXUHG4&IRU
HPEHGGHGWHVW´$µ
Generate
&RQWURO/RW1R
Generated result B1
Generated result B2
0HDVXUHG4&IRU
HPEHGGHGWHVW´)µ
&RQWURO/RW1R

Report
- Main result test B1
- Subresult test A
- Subresult test F
- Subresult test D
4 About cobas e flow tests

- Subresult B2

w Calculated QC and measured QC

The diagram below shows the relevant calculated QC

results and single QC results for a particular example
cobas e flow test result. (Note that the diagram
represents the logical structure of the message, rather
than the actual physical structure.)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 QC for cobas e flow tests 67

cobas eÁRZWHVW´+,9'XRµ

0DLQUHVXOW +,9'XR  ´5HDFWLYHµ>&2,@

6XEUHVXOW $QWL+,9 ´1RQ5HDFWLYHµ>&2,@

6XEUHVXOW +,9$J ´5HDFWLYHµ>&2,@

&DOFXODWHG4& IRU´+,9'XRµ >&2,@
+,9$J0&$QWL+,90&
+,9$J0&$QWL+,90&
6XEUHVXOWRIHPEHGGHGWHVW $QWL+,90& ******* 6LQJOH4& +,9$J0& >&2,@

6XEUHVXOWRIHPEHGGHGWHVW +,9$J0& ******* 6LQJOH4& $QWL+,90& >&2,@

w Example QC assignment to patient results

Each measurement of linked tests or embedded tests

referred to linked kits needs to be validated against the
appropriate calculated and single QC results.

The following diagram shows an example for the

cobas e flow test “HIV Duo R (duplicate repeat)” and its
calculated QC results. In order to simplify the diagram,
only a part of the subresults and only one control level are
shown.

4 About cobas e flow tests

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 68 QC for cobas e flow tests

cobas eÁRZWHVW
´+,9'XR5 GXSOLFDWHUHSHDW µ

0DLQUHVXOW +,9'XR5  ´5HSHDWHGO\5HDFWLYHµ

6XEUHVXOW $QWL+,9 ´5HDFWLYHµ>&2,@

6XEUHVXOW +,9$J ´5HDFWLYHµ>&2,@

&DOFXODWHG4& IRU´+,9'XR5µ >&2,@
+,9$J0&$QWL+,90&
+,9$J0&$QWL+,90&
6XEUHVXOWRIHPEHGGHGWHVW $QWL+,9>@0& ******* 6LQJOH4& +,9$J0& >&2,@

6XEUHVXOWRIHPEHGGHGWHVW +,9$J>@0& ******* 6LQJOH4&4 $QWL+,90& >&2,@

•
•
•

6XEUHVXOW $QWL+,9 ´1RQ5HDFWLYHµ>&2,@

6XEUHVXOW +,9$J ´5HDFWLYHµ>&2,@

&DOFXODWHG4& IRU´+,9'XR5µ >&2,@
+,9$J0&$QWL+,90&
+,9$J0&$QWL+,90&
6XEUHVXOWRIHPEHGGHGWHVW $QWL+,9>@0& ******* 6LQJOH4& +,9$J0& >&2,@

6XEUHVXOWRIHPEHGGHGWHVW +,9$J>@0& ******* 6LQJOH4& $QWL+,90& >&2,@

w Example QC for multiple QC assignments to patient results

4 About cobas e flow tests

Sending additional link information The system can provide additional link information to help
the host system to assign calculated QC results to
cobas e flow test patient results correctly. To configure
this, select the option Send additional link information
for calculated QC. Then additional link information is
always sent with the patient result, regardless of whether
calculated QC results are available or not.

(Note that the diagram below represents the logical

structure of the message, rather than the actual physical
structure.)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 QC for cobas e flow tests 69

3DWLHQWUHVXOWV &DOFXODWHG4&UHVXOWV

cobas eÁRZWHVW
´+,9'XR5 GXSOLFDWHUHSHDW µ

0DLQUHVXOW +,9'XR5  ´5HSHDWHGO\5HDFWLYHµ

6XEUHVXOW $QWL+,9 ´5HDFWLYHµ>&2,@

6XEUHVXOW +,9$J ´5HDFWLYHµ>&2,@

&DOFXODWHG4& IRU´+,9'XR5µ >&2,@
+,9$J0&$QWL+,90&
+,9$J0&$QWL+,90&
6XEUHVXOWRIHPEHGGHGWHVW $QWL+,9>@0& ******* 6LQJOH4& +,9$J0& >&2,@

6XEUHVXOWRIHPEHGGHGWHVW +,9$J>@0& ******* 6LQJOH4&4 $QWL+,90& >&2,@

+RVWFRGHRIWKHLQVWDOOHGXQLWRIFREDVHÁRZ +RVWFRGHRIWKHLQVWDOOHGXQLWRIFREDVHÁRZ
5HDJHQWLQIR +/RQO\ UHDJHQWORWQXPEHUOLQNHGNLW,' 
&RPELQDWLRQ,' +,9$J0&$QWL+,90& 5HDJHQWLQIR +/RQO\ UHDJHQWORWQXPEHU
OLQNHGNLW,'
&RPELQDWLRQ,' +,9$J0&$QWL+,9
0&
6XEUHVXOW $QWL+,9 ´1RQ5HDFWLYHµ>&2,@

6XEUHVXOW +,9$J ´5HDFWLYHµ>&2,@

&DOFXODWHG4& IRU´+,9'XR5µ >&2,@
+,9$J0&$QWL+,90&
+,9$J0&$QWL+,90&
6XEUHVXOWRIHPEHGGHGWHVW $QWL+,9>@0& ******* 6LQJOH4& +,9$J0& >&2,@

6XEUHVXOWRIHPEHGGHGWHVW +,9$J>@0& ******* 6LQJOH4& $QWL+,90& >&2,@

+RVWFRGHRIWKHLQVWDOOHGXQLWRIFREDVHÁRZ +RVWFRGHRIWKHLQVWDOOHGXQLWRIFREDVHÁRZ

4 About cobas e flow tests

5HDJHQWLQIR +/RQO\ UHDJHQWORWQXPEHUOLQNHGNLW,' 
&RPELQDWLRQ,' +,9$J0&$QWL+,90& 5HDJHQWLQIR +/RQO\ UHDJHQWORWQXPEHU
OLQNHGNLW,'
&RPELQDWLRQ,' +,9$J0&$QWL+,9
0&

w Additional link information for example multiple QC assignments to patient results

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 70 About repeat, rerun, and reflex tests with cobas e flow tests

About repeat, rerun, and reflex tests with

cobas e flow tests
This section describes the general definitions of terms
“repeat, rerun, and reflex”, and how they can be used with
cobas e flow tests.

Repeat, rerun, and reflex tests You can repeat a test in 2 different ways.
• Repeat test: repeats the measurement of the same
test under the same conditions
• Rerun test: reruns the same test with a different
dilution

It is also possible to trigger a test order according to the

result from another test:
• Reflex test: uses the result of one test to order another
test.

cobas e flow test rules Rules for cobas e flow test:

• You can repeat the whole cobas e flow test manually.
• You cannot repeat an embedded test of a
cobas e flow test.
• You cannot order a rerun with different dilutions for a
cobas e flow test or its embedded tests.
• A test can trigger a cobas e flow test as a reflex test.

q Although the data manager rule engine can use a

test to trigger cobas e flow test as a reflex test, a
cobas e flow test cannot trigger a regular test or a
cobas e flow test as a reflex test.
4 About cobas e flow tests

To trigger a reflex test from a cobas e flow test, program

it on the host system.

Manual and automatic The following table shows which options can be ordered
manually, and which options can be triggered
automatically for cobas e flow tests.

data manager: manual data manager: automatic Host

Repeat Yes No (a) Yes
Rerun No No(1) No
Reflex Yes o No (as trigger) Yes
o Yes (as reflex test)
y Ordering repeat, rerun and reflex tests for cobas e flow tests
(1) No automatic TS inquiry R2, as per definition, automatic rerun for cobas e flow tests is always Off

u Related topics
• Repeat, rerun, and reflex tests (42)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 71
Table of contents

Communication scenarios and

message types 5

This chapter shows the message flow between the

cobas® 8000 data manager and the host, and describes
the types of communication that take place.

5 Communication scenarios and message types

In this chapter 5
List of communication and message types. . . . . . . . . 73
Communication scenarios . . . . . . . . . . . . . . . . . . . . . . . 74
Realtime test selection download. . . . . . . . . . . . . . 74
Batch test selection download . . . . . . . . . . . . . . . . 74
Result query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Order query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Instrument status and test availability messages . 75
Other message scenarios . . . . . . . . . . . . . . . . . . . . 75
Details of message types. . . . . . . . . . . . . . . . . . . . . . . . 77
Query message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Sending test selections . . . . . . . . . . . . . . . . . . . . . . 77
Sending patient test results. . . . . . . . . . . . . . . . . . . 78
Raw data and data points in patient test results . 78
Result query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Order query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Order and result queries with limited sample
lifetime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
QC results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Calculated QC results. . . . . . . . . . . . . . . . . . . . . . . . 82
Calibration data results . . . . . . . . . . . . . . . . . . . . . . 83
Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Instrument status and test availability . . . . . . . . . . 83
Message flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Message flow batch download from host . . . . . . . 84
Message flow for batch download, upload by
sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 72
Table of contents

Message flow for TS Inquiry from instrument /

data manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
5 Communication scenarios and message types

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 List of communication and message types 73

List of communication and message types

The table below outlines 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.

The data manager sends information to the connected

host, such as a LIS or Work Area Manager (WAM), and
receives information from the host.

Message type Direction

Results Patient results data manager to host
Patient results (realtime) data manager to host in response to a
result query
Quality control results data manager to host
Calibration results data manager to host
Inquiry Test selection inquiry data manager to host
Test selections Test selections (batch) host to data manager

5 Communication scenarios and message types

Test selection (realtime) host to data manager
Test selection (realtime) data manager to host in response to an
order query
Query Result queries host to data manager
Order queries host to data manager
Instrument status query (only HL7) host to data manager
Test availability query (only HL7) host to data manager
Masking Command to mask or unmask tests (only HL7) host to data manager
Status Instrument status update (only HL7) data manager to host
Test availability update (only HL7) data manager to host
y Message types

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 74 Communication scenarios

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
Host cobas 8000 response to a data manager test selection query. After
data manager receiving the test selection download, the data manager
replies with the relevant patient results once they are
Test selection inquiry
available and released.
Test selection realtime download

Test selection inquiry

5 Communication scenarios and message types

Batch test selection download

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

Patient results

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

Patient results

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Communication scenarios 75

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

Order query Only orders on the data manager are returned. The data
manager cannot return details of orders that are only on
Test selection upload the control unit. If the sample ID does not exist, the data
manager replies, but without any test selections.

Instrument status and test availability messages

The data manager can send instrument status and test
Host cobas 8000 availability information to the host. (Only supported in
data manager HL7.)

5 Communication scenarios and message types

Instrument status query If forward instrument status mode is enabled, the data
manager automatically forwards instrument status and
Instrument status test availability information to the host as soon as it is
received from the control unit. The data manager will also
send test availability information whenever the availability
of a cobas e flow test changes.

If forward instrument status mode is disabled, the data

Host cobas 8000 manager only sends instrument status and test availability
data manager information in response to requests from the host.

Test availability query

u For more information, see Forward instrument status
mode (HL7 only) (105)

Test availability

Other message scenarios

The host can send a masking or unmasking request at
Host cobas 8000 any time, independent of other communication. (Only
data manager supported in HL7.)
Mask / unmask request Mask test

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 76 Communication scenarios

The data manager can send quality control or calibration

Host cobas 8000 results independently of other messages.
data manager

Quality control results

Host cobas 8000

data manager

Calibaration results
5 Communication scenarios and message types

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Details of message types 77

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.

Sending test selections

5 Communication scenarios and message types

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.
u To see how to set these options, see Test selection
inquiry message settings (99).

The query sent to the host always contains 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 modular analyzer series
instrument.

! CAUTION
You must request all three types of serum index
tests together
r The order sent by host has to request either all 3
serum index tests (Lipemic, Icteric, 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.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 78 Details of message types

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.
u 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 mode (103).
u For details of setting a test to automatic validation, see
the cobas® 8000 data manager Operator’s Manual.
5 Communication scenarios and message types

Raw data and data points in patient test results

The control unit can send raw data and data points to the
data manager (for example, for troubleshooting
purposes). The control unit sends raw data and data
points only when explicitly requested to do so by the user.
The e 801 module always sends raw data, and sends data
points when requested to do so.

Additionally, the upload of raw data and data points from

the data manager to the host can be enabled or disabled
manually.
u For more information, see Enabling/disabling raw data
and data point upload to the host (107)

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. If there is an
active 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”.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Details of message types 79

When the host sends a result query, the data manager

returns the results for whichever unique, current sample
matches the sample ID and rack type, if supplied.

In the chart, “S1” (serum/plasma) and “S2” (urine) are

given as example rack types.

Samples in DM Results which the data manager returns to a result query,

for a given sample ID, and rack type:
Sample ID lifetime status / S1 S2 (no rack type sent)(1)
rack type
No results for given sample ID no response no response no response
current / S1 current / S1 no response current / S1
current / S1 current / S1 current / S2 no response
current / S2
current / S1 current / S1 current / S2 no response
current / S2
expired / S1(2)
current / S1 current / S1 current / S2 no response
current / S2
expired / S1(2)

5 Communication scenarios and message types

expired / S2(2)
y Result query response for a specific sample ID
(1) Rack type is mandatory if sample lifetime is set. Even if not set, it is recommended to include it.
(2) “Expired” sample IDs are possible when a sample ID lifetime is set. Take care to use the timestamp to distinguish expired from current samples.

! WARNING
If using sample IDs with limited lifetimes, identify
samples also by timestamp.
r If your sample IDs have a limited lifetime, then there
may be several samples in the data manager database
with the same sample ID. In an answer to a result
query, the test selection upload includes the test
results for active samples with that ID.

u For details of inactive samples, sample ID lifetimes

and expired sample IDs, see Reusing sample IDs and
sample lifetimes (48).
u For details of using result queries in systems where
sample ID lifetimes are set, see Order and result
queries with limited sample lifetime (81).

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.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 80 Details of message types

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.)

When the host sends a order query, the data manager

returns the orders for whichever unique, current sample
matches the sample ID and rack type, if supplied. Expired
samples cannot be requested.

In the chart, “S1” (serum/plasma) and “S2” (urine) are

given as example rack types.

Samples in DM Test selection which the data manager returns to an order query,
for a given sample ID and rack type:
Sample ID lifetime status / S1 S2 (no rack type sent)(1)
rack type
No orders for given sample ID empty test selection/ S1 empty test selection / S2 empty test selection / (no rack
type)
current / S1 current / S1 empty test selection / S2 current / S1
5 Communication scenarios and message types

current / S1 current / S1 current / S2 empty test selection / (no rack

current / S2 type)
current / S1 current / S1 current / S2 empty test selection / (no rack
current / S2 type)
expired / S1(2)
current / S1 current / S1 current / S2 empty test selection / (no rack
current / S2 type)
expired / S1(2)
expired / S2(2)
y Order query response for a specific sample ID
(1) Rack type is mandatory if sample lifetime is set. Even if not set, it is recommended to include it.
(2) “Expired” sample IDs are possible when a sample ID lifetime is set. Take care to use the timestamp to distinguish expired from current samples.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Details of message types 81

! WARNING
If using sample IDs with limited lifetimes, identify
samples also by timestamp.
r If your sample IDs have a limited lifetime, then there
may be several samples in the data manager database
with the same sample ID. In an answer to an order
query, the test selection upload includes the test
orders or results for active samples with that ID.
r The orders for expired samples might be confused
with orders for current samples, or with previous
orders for samples that are now expired. Avoid this,
and identify samples and orders by timestamp, as well
as by ID.

u For details of sample ID lifetimes and expired sample

IDs, see Reusing sample IDs and sample
lifetimes (48).
u For details of using sample IDs with limited lifetimes
with order queries, see Order and result queries with

5 Communication scenarios and message types

limited sample lifetime (81).

Order and result queries with limited sample lifetime

If you use order and result queries with samples that have
a limited lifetime, the data manager always answers a
query with the order and result details of current samples.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 82 Details of message types

Host cobas 8000

data manager

New sample ID 123, type S1: test

selection download
Sample: ID 123, type S1, created
with timestamp day 1

Results uploaded for sample ID 123

Sample 123 expires

New sample ID 123, type S1: test

selection download
Sample: ID 123, type S1, created
with timestamp day 2
Result query / order query down-
loaded
(Results uploaded only if
Result upload / test selection upload for available.)
current sample.
5 Communication scenarios and message types

QC results
The measured QC results are sent from the data manager
to the host. To send QC results automatically to the host,
enable QC pass-through mode.

q When manually resending QC results from the

control unit
The data manager always uploads manually resent QC
results to the host using the By test upload mode,
regardless of which upload mode is selected on the data
manager and control unit.
u For more information about result upload modes, see Pass-
through mode (103).

u For more information, see Pass-through mode (103).

Calculated QC results
Calculated QC results are used for the validation of
embedded test results in cobas e flow tests. The
calculated QC result is calculated based on a formula of
QC results from embedded tests. It is sent to the host as a
standalone message.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Details of message types 83

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 a certain test on a certain submodule. There are two
different types of masking supported:
• Patient masking. If activated, only patient samples are
masked. Quality control and calibration are still
performed.
• Test masking, where the entire test is masked, and no
patient sample, quality control or calibration tests are
performed.

5 Communication scenarios and message types

Test masking can also be triggered either manually or
automatically (for example, by a failed quality control on
the data manager, or by other triggers defined on the
control unit).

The host can also send an instruction to remove masking

from masked tests.

q Masking messages are only available in HL7.

q For cobas e flow test results, only patient masking

is permitted. If test masking of a cobas e flow test is
attempted, the data manager returns an error message to
the host.

Instrument status and test availability

The data manager can send instrument status and test
availability information to the host.

q Instrument status and test availability messages are

only available in HL7.

u For more information, see Forward instrument status

mode (HL7 only) (105)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 84 Message flow

Message flow

Message flow batch download from host

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

In this example, the setting Always ask for test

selection has been disabled.

Host cobas 8000 cobas 8000

data manager instrument

Test Selections(Sample ID,

Test A, Test B, Test C)
5 Communication scenarios and message types

Load Sample( )

Scan Sample( )
Test Selection Inquiry R1(Sample ID, Rack, Position)

Test Selections(Sample ID, Rack, Position,

Test A, Test B, Test C)

Measure(Sample
ID, Test A)
Result(Test A)

Technical Validation( )

Result(Test A)

Measure(Sample
Result(Test B) ID, Test B)

Technical Validation( )

Result(Test B)

Measure(Sample
Result(Test C)
ID, Test C)

Technical Validation( )

Result(Test C)

Test Selection Inquiry R2(Sample ID, Rack, Position)

No further Test Selections( )

Unload Sample( )

w Message sequence for a batch order of three samples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Message flow 85

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 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-through
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.

5 Communication scenarios and message types

Message flow for batch download, upload by sample
The following diagram shows an example of message
flow (from top down) when:
• the host sends a batch order of three tests
• the control unit is in automatic rerun mode
• the control unit uploads results by sample
• the data manager option Send query to host is off

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 86 Message flow

Host cobas 8000 cobas 8000

data manager instrument
Test Selections(Sample ID,
Test A, Test B, Test C)

Load Sample( )

Scan Sample( )
Test Selection Inquiry R1(Sample ID, Rack, Position)

Test Selections(Sample ID, Rack, Position,

Test A, Test B, Test C)

Measure(Sample
ID, Test A)

Measure(Sample
ID, Test B)
5 Communication scenarios and message types

Result(Test A, Test B, Test C) Measure(Sample

ID, Test C)

Technical Validation( )

Result(Test A, Test B, Test C)

Test Selection Inquiry R2(Sample ID, Rack, Position)

No further Test Selections( )

Unload Sample( )

w Batch download, with upload by sample

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.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Message flow 87

Host cobas 8000 cobas 8000

data manager instrument

Load Sample( )

Scan Sample( )
Test Selection Inquiry R1(Sample ID, Rack, Position)
Test Selection Inquiry R1(Sample
ID, Rack, Position)

Test Selection(Sample ID, Rack,

Position, Test A, B, C)
Test Selections(Sample ID, Rack, Position,
Test A, B, C)

Measure(Sample
ID, Test A)
Result(Test A)

Technical Validation( )

Result(Test A)

5 Communication scenarios and message types

Measure(Sample
ID, Test B)
Result(Test B)

Technical Validation( )

Result(Test B)
Measure(Sample
Result(Test C) ID, Test C)

Technical Validation( )

Result(Test C)

Test Selection Inquiry R2(Sample ID, Rack, Position)

Test Selection Inquiry R2(Sample
ID, Rack, Position)

No further test selections(Sample

ID, Rack, Position)
No further test selections(Sample ID,
Rack, Position)

Unload Sample( )

w Message flow for a Test Selection 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
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 88
5 Communication scenarios and message types Message flow

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Configuration

6 Configuring the data manager .......................................................................... 91

7 Configuring the control unit.............................................................................131

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 91
Table of contents

Configuring the data manager 6

Setting up the data manager for host
communications

This chapter describes how to set up data manager to

enable host communications.

In this chapter 6
Configuring the data manager . . . . . . . . . . . . . . . . . . . 93
The host connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Starting and stopping the host connection. . . . . . 95

6 Configuring the data manager

Using the data manager without a host
connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Configuring the data manager host interface options 97
Identifying the data manager application to the
host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Test selection inquiry timeout settings . . . . . . . . . 98
Test selection inquiry message settings . . . . . . . . 99
Connection protocol settings . . . . . . . . . . . . . . . . . 100
HL7 acknowledgment handling settings. . . . . . . . 102
Throttle instrument settings . . . . . . . . . . . . . . . . . . 102
Pass-through mode . . . . . . . . . . . . . . . . . . . . . . . . . 103
Logging level settings . . . . . . . . . . . . . . . . . . . . . . . 104
Rack and position mode . . . . . . . . . . . . . . . . . . . . . 104
STAT masking mode. . . . . . . . . . . . . . . . . . . . . . . . . 105
Forward instrument status mode (HL7 only) . . . . 105
Viewing result upload settings on the data
manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Enabling/disabling raw data and data point
upload to the host . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Identifier of the analytical unit sent to host . . . . . 108
cobas e flow test-related settings. . . . . . . . . . . . . . . . 110

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 92
Table of contents

Enabling/disabling cobas e flow test subresult

upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Sending single QC results for calculated QC . . . . 111
Sending additional link information for
calculated QC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Using legacy record status . . . . . . . . . . . . . . . . . . . 112
Configuring omitted result reporting . . . . . . . . . . . 114
Assigning result type for cobas e flow test result
upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Assigning host codes to cobas e flow test
results and generated subresults . . . . . . . . . . . . . . 116
About host code assignment . . . . . . . . . . . . . . 116
Activating or deactivating the host code
assignment for a cobas e flow test result . . . 117
Activating or deactivating the host code
assignment for a cobas e flow test
generated subresult . . . . . . . . . . . . . . . . . . . . . . 118
Assigning host codes to cobas e flow test
results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Assigning host codes to cobas e flow test
generated subresults . . . . . . . . . . . . . . . . . . . . . 121
Host code assignment example . . . . . . . . . . . . 122
Getting a trace file from the data manager. . . . . . . . . 123
Physical layer specifications . . . . . . . . . . . . . . . . . . . . . 124
Connecting a Generation 5 server . . . . . . . . . . . . . 124
Connecting a Generation 6 server . . . . . . . . . . . . . 125
Connecting a Generation 8 server . . . . . . . . . . . . . 126
Network connection. . . . . . . . . . . . . . . . . . . . . . . . . 126
Serial connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
6 Configuring the data manager

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Configuring the data manager 93

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.

r 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.

3 Log into the data manager as a user with

configuration privileges, who can see the Service-
related configuration workplace.

4 Navigate to Workplaces > cobas 8000 data

manager Service > Service-related configuration
> Interface options.

5 Work through the sections of this manual that

describe the settings in the Interface options tab.

6 Configuring the data manager

Make sure the settings meet your needs.

6 Log onto the control unit, and make sure its settings
meet your needs.

7 Start host communications on the data manager in

Workplaces > cobas 8000 data manager Service
> Service-related configuration > Interface
options.

8 The data manager is now configured for host

communications.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 94 Configuring the data manager

u Related topics
• For details of how the cables and network must be
configured, see Text encoding (32) and Physical layer
specifications (124).
• For details of the interface options for the data
manager, see Configuring the data manager host
interface options (97).
• For details of how the control unit must be configured,
see Configuring the control unit (131).
• For details of starting and stopping host
communications, see Starting and stopping the host
connection (95).
6 Configuring the data manager

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 The host connection 95

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 host connection

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

You can control and configure the host connection by

navigating to Workplaces > cobas 8000 data
manager Service > Service-related configuration
> Interface options.

6 Configuring the data manager

r To connect a host
1 In Workplaces > cobas 8000 data manager
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.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 96 The host connection

r To stop a host connection

1 Navigate to Workplaces > cobas 8000 data

manager Service > Service-related configuration
> Interface options,

2 Select the No host option, and then choose the OK

button.
f The data manager closes any host connection.

q Disable test selection inquiry completely by

clearing the Send query to host check box.

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.
6 Configuring the data manager

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Configuring the data manager host interface options 97

Configuring the data manager host

interface options

w The Interface options tab

6 Configuring the data manager
When configuring the host interface, ensure that the
settings in Workplaces > cobas 8000 data manager
Service > Service-related configuration > Interface
options implement the functionality that you need. You
can work through all the following sections in turn to
prepare the data manager for host communications.

Identifying the data manager application to the host

In the header of every message, the data manager sends
an identification string to the host. You can edit this string
in Workplaces > cobas 8000 data manager Service
> Service-related configuration > Interface options.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 98 Configuring the data manager host interface options

The Sending application name 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 .

! CAUTION
Do not enter ASTM or HL7 reserved characters in
the sending application name
r Make sure that users never enter characters that are
reserved in either communication protocol.
r 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]
r 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]
6 Configuring the data manager

Test selection inquiry timeout settings

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
Workplaces > cobas 8000 data manager Service
> Service-related configuration > Interface options.

In the Host timeout (sec.) field, you can configure the

timeout between data manager and the host, in seconds.
More specifically, you can configure the timeout to the
test selection inquiry for realtime communications and for
Routine, STAT and Rerun samples.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Configuring the data manager host interface options 99

Host cobas 8000 cobas 8000

data manager instrument

Timeout on data manager Timeout on control unit

Must be 2 s shorter than Must be 2 s longer than
on control unit on data manager
Default is 16 s Default is 18 s

w Timeouts on control unit and data manager

The default setting here on data manager is 16 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.

! CAUTION
Optimum response time is less than 1.5 seconds
r The host must send a test selection to data manager
in response to a test selection inquiry on average in
less than 1.5 seconds. If it takes the host longer to
reply to inquiries, the performance of the system will

6 Configuring the data manager

gradually degrade.
r 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.

Test selection inquiry message settings

This section describes how you can configure the test
selection inquiry messages. This is configurable in
Workplaces > cobas 8000 data manager Service
> Service-related configuration > Interface options.

The options Send query to host and Always ask for

test selection configure the data manager to work with
hosts in realtime, batch or mixed mode.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 100 Configuring the data manager host interface options

The table below shows how the query and inquiry

settings interact with each other.

Send query to Always ask for Behavior

host test selection
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)
y Settings for test selection inquiries

With Send query to host selected, when the control unit

sends 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.

With Always ask 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 ask for test selection can only be enabled if

Send query to host is also selected.
u For details of host in batch, realtime or mixed mode,
6 Configuring the data manager

see Batch and realtime processing (44).

Connection protocol settings

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.
u For technical details of the ASTM protocol, see ASTM
protocol (LIS2 - A2) (149).
u For details of the data fields data manager supports
over the ASTM protocol, see ASTM text content (LIS2
- A2) (161).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Configuring the data manager host interface options 101

ASTM Network The ASTM Network option specifies TCP/IP

communications over the ASTM protocol.
u For technical details of the ASTM protocol, see ASTM
protocol (LIS2 - A2) (149).
u For details of the data fields data manager supports
over the ASTM protocol, see ASTM text content (LIS2
- A2) (161).

HL7 Network The HL7 Network option specifies TCP/IP

communications over the HL7 protocol.
u For technical details of the HL7 protocol, see HL7
protocol (233).
u For details of the data fields data manager supports
over the HL7 protocol, see HL7 text content (237).

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

host.

q When the No host option is selected, the data

manager continues to write all outgoing messages to the
directory c:\data\host\out even though no host is
connected. Be sure to regularly remove unwanted data
from this directory.

Changing the communication protocol Consult your Authorized Roche Diagnostics service
personnel before changing the communication protocol.

CAUTION

6 Configuring the data manager

!

Change the communication protocol only with the

buttons
r When you change the connectivity type (Network /
Serial) or protocol (ASTM/HL7) use these buttons. Do
not edit lower-level configuration files.
r To change the connectivity type (Network / Serial)
further configuration might be necessary. This will be
set up by Authorized Roche Diagnostics service
personnel.

u For details of the cables and other low-level settings

required by communication protocols, see Physical
layer specifications (124).
u For details of configuring the control unit for
communications, see Configuring the control
unit (131).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 102 Configuring the data manager host interface options

HL7 acknowledgment handling settings

The data manager supports a limited range of the HL7
application acknowledgment messages. For result
messages sent to the host, the user can set the level of
acknowledgment that the data manager should request
from the host. These settings apply to patient, quality
control and calibration results. This is configurable in
Workplaces > cobas 8000 data manager Service
> Service-related configuration > Interface options.

Code Meaning Required host action

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

HL7 Application acknowledgment From the HL7 Application acknowledgment drop-

down list, choose the level of application
acknowledgment that the data manager should request
from the host.

HL7 acknowledgment timeout (secs.) In the HL7 acknowledge timeout (secs.) field, enter
the timeout required. This field is used only with the AL
and SU options. The default is 60 seconds.
u For more details on HL7 application acknowledgment
messages, see HL7 acknowledgment handling (295).
6 Configuring the data manager

Throttle instrument settings

In production environments, navigate to Workplaces
> cobas 8000 data manager 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
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Configuring the data manager host interface options 103

With Throttle instrument selected, the data manager

receives a result report message from the instrument, and
then sends it to the host. The data manager then waits:
• ASTM serial or network connection. The data manager
waits up to 10 seconds for the final low-level
acknowledgment from the host before sending an
acknowledgment to the instrument.
• HL7 network connection with application
acknowledgment set to AL or SU. The data manager
waits up to 10 seconds for the high-level
acknowledgment from the host before sending an
acknowledgment to the instrument.
• HL7 network connection with application
acknowledgment set to ER or NE. 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.

If Throttle instrument is disabled, an acknowledgment

message is immediately sent to the control unit.

Pass-through mode
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

6 Configuring the data manager

Workplaces > cobas 8000 data manager Service
> Service-related configuration > Interface options
> Pass-through mode.

Note that pass-through mode is not a by-pass mode. The

data manager processes the data, but sends the results to
the host irrespective of its processing. See below for
details and exceptions.

Patient results If selected, all patient results are forwarded from the data
manager to the host irrespective of data manager
functionality, except for:
• results that have been entered manually
• results blocked by QC errors

If deselected, the data manager holds results back for

manual validation, if the tests are so configured.
u For details on configuring validation in the data
manager, see the cobas® 8000 data manager
Operator’s Manual.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 104 Configuring the data manager host interface options

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 check box selected, quality control

results are forwarded to the host automatically. Then the
host can do QC analysis: Westgard, Rilibäk etc. If this
check box is not selected, the QC results are not
forwarded to the host, and QC analysis is done by data
manager.
u For more details on the configuration of quality control
analysis, see the Data Manager section of the cobas®
8000 data manager Operator’s Manual.

Calibration results With the Calibration results check box selected,

calibration results are forwarded to the host
automatically.
u For more details on the configuration of calibration
settings, see the cobas® 8000 data manager
Operator’s Manual.

Logging level settings

You can configure what information the data manager
logs about host communications in Workplaces
> cobas 8000 data manager Service > Service-
related configuration > Interface options, from the
Trace level drop-down menu. In increasing quantity of
6 Configuring the data manager

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 Workplaces > cobas 8000 data
manager Service > Service-related configuration
> Interface options, and enable the option Enable rack
and position mode.
u For a more detailed description of how to implement
this option, and other related options, seeHandling
batch test selections with strict rack and
position (451), and for an example of use, see Using
MODULAR PRE-ANALYTICS (445).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Configuring the data manager host interface options 105

STAT masking mode

If you are using a cobas® 8100 automated workflow
series instrument, and more than 5% of your samples
have STAT tests on them, navigate to Workplaces
> cobas 8000 data manager Service > Service-
related configuration > Interface options, and select
the option STAT masking mode.

If you are using the cobas® 8100 automated workflow

series instrument to sort samples, some of the routine
samples may be upgraded to STAT samples. If there is an
upgraded sample in a rack, all the samples on the rack
are upgraded to STAT. In some installations, if there are
many STAT samples, the routine samples may be delayed.

When you select the option STAT masking mode, all

upgraded samples are handled as routine on the
instrument. However, the data manager still handles
upgraded samples as STAT, and the instrument still
handles samples on STAT racks as STAT.

STAT Priority CU query to Host TS DM Handled on CU uploads DM uploads

Masking according to DM + DM download / downloads TS Instrument results to DM results to LIS
Mode Rack ID query to host Manual order to CU
to DM
Off Routine Routine Routine Routine Routine Routine Routine
Off Routine Routine STAT STAT STAT Routine STAT
Off STAT STAT Routine Routine STAT STAT Routine
Off STAT STAT STAT STAT STAT STAT STAT

6 Configuring the data manager

On Routine Routine Routine Routine Routine Routine Routine
On Routine Routine STAT Routine Routine Routine STAT
On STAT STAT Routine Routine STAT STAT Routine
On STAT STAT STAT STAT STAT STAT STAT
Notes Identical to SMM Off: STAT upgrade Identical to Identical to TS
Rack ID SMM On: No STAT upgrade Rack ID download
y STAT masking mode sample priorities (Red outline shows differences with STAT masking mode on / off)

Forward instrument status mode (HL7 only)

The data manager can be told to automatically forward
instrument status, test availability information, and
cobas e flow test availability information to the host
whenever it receives updated information from the
control unit. The control unit sends this information to the
data manager whenever the status of the instrument
changes, and whenever a test is manually or
automatically masked.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 106 Configuring the data manager host interface options

To enable this feature, navigate to Workplaces > cobas

8000 data manager Service > Service-related
configuration > Interface options, and select the
check box Enable instrument status forwarding. (This
mode is disabled by default.)

q Forward instrument status mode is not supported by

the ASTM protocol. If you are using the ASTM protocol,
the check box will be unavailable.

When forward instrument status mode is disabled, the

data manager sends instrument status and test
availability information only in response to requests from
the host.

The data manager sends instrument status and test

availability information to the host in the following HL7
messages:
• Instrument status: Equipment Status Update (ESU)
• Test availability: Inventory Status Update (INU)

q The test availability message does not reflect

reagent or calibration masking status.

The host requests this information from the data manager

in the following HL7 messages:
• Instrument status query: Equipment Status Update
6 Configuring the data manager

Request (ESR)
• Test availability query: Inventory Status Update
Request (INR)
u For more information on these messages, see:
HL7 messages (239)
Instrument status and test availability messages (357)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Configuring the data manager host interface options 107

Viewing result upload settings on the data manager

The currently selected result upload settings are
displayed in Workplaces > cobas 8000 data manager
Service > Service-related configuration > Interface
options > Result upload settings. These settings can
only be changed on the control unit, and are displayed on
the data manager for information only. The settings
displayed on the data manager are updated during
startup of the system, after communication has been
established between the control unit and the data
manager.
u For details of the result upload settings and how to
configure them on the control unit, see Result upload
settings (140).

Enabling/disabling raw data and data point upload to the

host
You can manually enable or disable the upload of raw
data and data points from the data manager to the host.
This allows for increased compatibility with host systems
that may be unable to properly handle result messages
containing raw data and data points.

To enable or disable the upload of raw data and data

point values, navigate to Workplaces > cobas 8000

6 Configuring the data manager

data manager Service > Service-related
configuration > Interface options, and select or clear
the Send raw data / data points to host check box
accordingly.

When enabled, the data manager sends the data point

values in field OBX-5 (HL7) or R-4 (ASTM), and sends the
raw data type in OBX-17 (HL7) or R-14.5 (ASTM).

Data points are only included in a cobas e flow test

result if they are requested while the cobas e flow test is
still in progress.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 108 Configuring the data manager host interface options

Identifier of the analytical unit sent to host

The data manager holds a unique ID for each analytical
unit 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 > ID for Host.

! CAUTION
This field is used by both result and masking
messages (HL7)
r In HL7, this field is used by both result and masking
messages. If you edit this field, make 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:

• In ASTM Result record, Field 14, component 3. It
identifies the analytical unit that performed the test.
• 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.
6 Configuring the data manager

The data manager sends the ID in HL7 in:

• In HL7 segment OBX-18, component 3. It identifies the
analytical unit 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:

• In HL7 segment ECD-5, component 3. Here it
identifies the analytical unit to perform masking on.

Default value The whole field is freely editable. The default values
follow the format:

Instrument#ModuleType#Position#SubModule

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Configuring the data manager host interface options 109

Value Type Description

Instrument String Currently defaults to MU1, which identifies the first cobas® 8000 modular analyzer
series connected to the data manager. In the future, there may be more analyzers
connected.
ModuleType String c502, c701, e602, ISE, c702, e801, 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
y

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:

MU1#ISE#1#1

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

OBX|1||989||2.0|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20171127183657|bmserv^SYSTEM|||ISE^1^MU1#ISE#1
#1^3^770|20171127183712|

In an ASTM Result record, this might look like:

R|1|^^^989/1/not|2.0|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171127183657|20171127183712

6 Configuring the data manager

|ISE^1^MU1#ISE#1#1^3^770|

q 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.

When masking cobas e flow tests When masking cobas e flow tests from the host, the data
manager ignores the analytical unit ID. The data manager
reads only the test ID, and masks the test on all e 801
submodules. This is because cobas e flow tests are
defined only on the data manager, and are therefore
module-independent.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 110 cobas e flow test-related settings

cobas e flow test-related settings

This section introduces the settings on the data manager
which have an impact upon cobas e flow tests.

In this section
Enabling/disabling cobas e flow test subresult
upload (110)
Sending single QC results for calculated QC (111)
Sending additional link information for calculated
QC (111)
Using legacy record status (112)
Configuring omitted result reporting (114)
Assigning result type for cobas e flow test result
upload (115)
Assigning host codes to cobas e flow test results and
generated subresults (116)

Enabling/disabling cobas e flow test subresult upload

You can choose whether to report subresults to the host.
To enable or disable reporting of subresults, navigate to
Workplaces > cobas 8000 data manager Service
> Service-related configuration > Interface options,
and select or clear the Send cobas e flow test
subresults check box accordingly.
6 Configuring the data manager

Host cobas eÁRZWHVW´+,9'XRµ

6HQGPDLQUHVXOW
0DLQUHVXOW +,9'XR  ´5HDFWLYHµ>&2,@

6XEUHVXOW $QWL+,9 ´1RQ5HDFWLYHµ>&2,@

6HQGFREDVHÁRZWHVWVXEUHVXOWV
,IVHOHFWHG
6XEUHVXOW +,9$J ´5HDFWLYHµ>&2,@

w Send cobas e flow test subresults to host

u Related topics
• cobas e flow test results (59)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test-related settings 111

Sending single QC results for calculated QC

If the Send single QC results for calculated QC check
box is selected, related single QC results used in a QC
calculation are sent to the host in the calculated QC result
message.

If the check box is cleared, single QC results are not sent

in the same message.

q If the Send single QC results for calculated QC

check box is selected, single QC results are sent twice:
once as an individual result, and once as a part of the
calculated QC result message.

Host

Send calculated QC result Calculated QC 3 for “HIV Duo” 0.650 [COI]

(HIV Ag, MC1 - Anti HIV, MC2)

Single QC1 (HIV Ag, MC1) 0.375 [COI]

Send single QC results for calculated QC
(If selected)
Single QC4 (Anti HIV, MC2) 0.531 [COI]

w Send single QC result for calculated QC

6 Configuring the data manager

u Related topics
• For more information about calculated QC results and
single QC results, see QC for cobas e flow tests (62).

Sending additional link information for calculated QC

If the Send additional link information for calculated
QC check box is selected, the following additional
information is uploaded to the host for a
cobas e flow test.
• Unique test code number of cobas e flow test
• Unique ID from which cobas e pack has been
pipetted for linked tests
• Unique combination kit ID identifying related cobas e
pack of involved embedded tests
• Unique ID on which module has been measured
• Unique ID of embedded test and measuring cell
combination

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 112 cobas e flow test-related settings

The diagram below shows the result upload of a

cobas e flow test. The information highlighted in red is
sent if the Send additional link information for
calculated QC check box is selected. (Note that the
diagram represents the logical structure of the message,
rather than the actual physical structure.)

cobas eÁRZWHVW´+,9'XRµ

0DLQUHVXOW +,9'XR  ´5HDFWLYHµ>&2,@

6XEUHVXOW $QWL+,9 ´1RQ5HDFWLYHµ>&2,@

6XEUHVXOW +,9$J ´5HDFWLYHµ>&2,@

&DOFXODWHG4& IRU´+,9'XRµ >&2,@
+,9$J0&$QWL+,90&
+,9$J0&$QWL+,90&
6XEUHVXOWRIHPEHGGHGWHVW $QWL+,90& ******* 6LQJOH4& +,9$J0& >&2,@

6XEUHVXOWRIHPEHGGHGWHVW +,9$J0& ******* 6LQJOH4& $QWL+,90& >&2,@

This configuration affects the result values sent in OBX-4

(in HL7 result messages) and R-6 (in ASTM result
messages).
u Observation Result Segment - OBX (255)
6 Configuring the data manager

u Result Record (178)

Using legacy record status

When enabled, the Use legacy record status check box
forces the data manager to send legacy result status
values.

A single-character result status value is sent in ASTM R-9

or HL7 OBX-11 for patient results. This value tells the host
the status of the result that is being sent. (For example,
whether the result is a first run, whether it has been
corrected, etc.)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test-related settings 113

With version 1.06.05 of the data manager software, 2

additional result statuses were newly implemented for
cobas e flow tests:
• B : this signifies that the result is a linkage record,
used to link the result to a calculated QC result.
• V : this signifies that the result is a measured
embedded test result upon which the main result of a
cobas e flow test is based.

If your host does not support these new values, you can
enable this check box to force data manager to send the
legacy values F and C instead.

When enabled The legacy values are sent.

• Either F or C is sent for main result, depending on
whether the current run is an initial run
• F is sent for linkage records

When disabled The new result status values are sent.

• V is sent for main results
• B is sent for linkage records

The following table shows how the values which are

affected by the Send additional link information for
calculated QC and Use legacy record status check
boxes.

Send additional link

Use legacy record Main result (when
information for calculated Linkage record

6 Configuring the data manager

status embedded test)
QC
; ; F F (or C)
; B V
; - F (or C)
- V

u Related topics
• Result Record (178)
• Observation Result Segment - OBX (255)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 114 cobas e flow test-related settings

Configuring omitted result reporting

An omitted result is a main result or subresult that is
either missing, or that has been suppressed.

The following are examples of scenarios in which results

are omitted:
• Result values are not reported to the user, e.g. for
confidentiality reasons
• Results are suppressed due to a data alarm indicating
that the result is outside measuring range
• A data alarm without a result value (e.g. Sample short)
has occurred
• The cobas e flow test was canceled

You can configure omitted result reporting on the Host

reporting tab. The setting is global and is applicable for
all installed cobas e flow tests, including test results and
QC results.

The configuration only applies to cobas e flow tests.

u For more information about result suppression for
regular tests, see Result suppression for results
outside the technical limit (54)

r To configure omitted result reporting

1 Navigate to Workplaces > cobas 8000 data

6 Configuring the data manager

manager Service > Service-related

configuration. Choose the Host reporting tab.

2 From the Value for omitted results drop-down list,

choose a reporting option. The 3 options available are:
• 7 spaces: the data manager sends a string of 7
spaces. (ASCII 32 / 0x20)
• Empty: the data manager sends nothing in the
field.
• Custom value: the data manager sends a free text
string that you define. You can define this string in
the Custom value field. This string can be up to
20 alphanumeric characters long.
I The 7 spaces option is selected by default.

u Related topics
• Result suppression for results outside the technical
limit (54)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test-related settings 115

Assigning result type for cobas e flow test result upload

You can assign the type of a cobas e flow test result that
is uploaded to the host.

The following result types are supported:

• Quantitative
• Qualitative
• Quantitative/qualitative
• Qualitative/quantitative

This configuration affects the result values sent in OBX-5

(in HL7 result messages) and R-4 (in ASTM result
messages).
u R-4 description (184)
u OBX-5 description (268)

j m On the Interface options tab, select the Assign host

code by reported lab unit check box.

r To assign result type for

cobas e flow test result upload

1 1 Choose cobas 8000 data manager Test

Configuration > Tests / reference ranges.

6 Configuring the data manager

2
2 In the tests table, double-click the appropriate
cobas e flow test.

3
3 Choose the Host reporting tab.
• From the Test result type for host reporting
drop-down list, choose the appropriate result type.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 116 cobas e flow test-related settings

Assigning host codes to cobas e flow test results and

generated subresults
A generated subresult is a formula or variable of a
cobas e flow test which is defined as reported. The host
code of every cobas e flow test generated subresult can
be overwritten with a custom value.

Furthermore, a host code can be assigned for each

measurement unit of each embedded test which has the
role of a main result.

In this section
About host code assignment (116)
Activating or deactivating the host code assignment for a
cobas e flow test result (117)
Activating or deactivating the host code assignment for a
cobas e flow test generated subresult (118)
Assigning host codes to cobas e flow test results (120)
Assigning host codes to cobas e flow test generated
subresults (121)
Host code assignment example (122)

About host code assignment

Host code assignment functionality is activated by
selecting the Use custom host codes for cobas e flow
6 Configuring the data manager

test generated subresults and Assign host code by

reported lab unit check boxes. Both check boxes are
cleared by default.

You can find the check boxes by navigating to

Workplaces > cobas 8000 data manager Service
> Service-related configuration > Interface options.

If the data manager is configured to send custom host

codes, tests which do not have a host code are not sent to
the host with the sample. If none of the tests have results,
the sample is not sent to the host.

q Any custom host codes you assign must be unique.

You cannot use a code which is used in another
cobas e flow test or in any other test.

q If you deactivate a cobas e flow test, the host code

assignments are removed.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test-related settings 117

Activating or deactivating the host code assignment for a cobas e flow test
result
For cobas e flow tests, you can activate or deactivate the
assignment of host codes for available measurement
units, for example mmol/L, mg/dL, or [COI].

If the host does not support different cobas e flow test

main result types, for example, quantitative/qualitative or
unit, you have to assign the host code for each type of
result.

With the Assign host code by reported lab unit check

box selected, you can assign a host code to any
embedded test unit that can be used as main result for
the cobas e flow test.

If the check box is cleared, the cobas e flow test main

result is sent with the host code which was entered
originally in the Host code field in the Test /reference
ranges dialog box. If no host code is assigned, the
cobas e flow test main result is not sent with the
corresponding laboratory unit to the host.

r To activate or deactivate the host

code assignment for a
cobas e flow test result
1 Choose cobas 8000 data manager Service

6 Configuring the data manager

1
> Service-related configuration.

2
2 On the Interface options tab, select the Assign host
code by reported lab unit check box.
• Choose the OK button.

u Related topics
• Assigning host codes to cobas e flow test
results (120)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 118 cobas e flow test-related settings

Activating or deactivating the host code assignment for a cobas e flow test
generated subresult
For cobas e flow tests, you can activate or deactivate the
assignment of host codes for generated subresults. The
generated subresult is sent to the host with the assigned
host code.

If the host does not support alphanumeric IDs or requires

unique host code IDs, you have to assign a custom host
code to the generated subresults.

If the Use custom host codes for cobas e flow test

generated subresults check box is selected, you can
assign host codes to the generated subresults of an
embedded test on the Assignment of host code tab of
the appropriate Test / reference ranges dialog box. The
maximum length of a host code is 20 characters.
Delimiter characters used by the ASTM and HL7
protocols ( |\^&~ ) cannot be used in the host code.

If the check box is cleared, you cannot assign a host code

to generated subresults. The subresult is sent with the
name of the cobas e flow test generated subresult.

If you try to assign a host code that is already in use, a

dialog box informs you that this host code cannot be
used.

q The Use custom host codes for cobas e flow

6 Configuring the data manager

test generated subresults check box can only be

selected when the Send cobas e flow test subresults
check box is also selected.

r To activate or deactivate the host

code assignment for a
cobas e flow test generated
subresults

1
1 Choose cobas 8000 data manager Service
> Service-related configuration.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test-related settings 119

2
2 On the Interface options tab, select the Use custom
host codes for cobas e flow test generated
subresults check box.
• Choose the OK button.

u Related topics
• Assigning host codes to cobas e flow test generated
subresults (121)

6 Configuring the data manager

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 120 cobas e flow test-related settings

Assigning host codes to cobas e flow test results

If the host does not support alphanumeric IDs or requires
unique host code IDs, you have to assign a custom host
code to the cobas e flow test main result.

If you try to assign a host code that is already in use, a

dialog box informs you that this host code number cannot
be used.

j m On the Interface options tab, you must select the

Assign host code by reported lab unit check box.

r To assign host codes for cobas e flow

test results

1 1 Choose cobas 8000 data manager Test

Configuration > Tests / reference ranges.

2
2 In the tests table, double-click the appropriate
cobas e flow test.
6 Configuring the data manager

3
3 In the Host reporting > cobas e flow units table,
choose the appropriate unit and press the Enter key.

4
4 In the Host code for unit dialog box, enter the host
code number and confirm with the Save button.
I From the Result type drop-down list, choose the
result type that the host supports.

u Related topics
• Activating or deactivating the host code assignment
for a cobas e flow test result (117)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test-related settings 121

Assigning host codes to cobas e flow test generated subresults

You can assign host codes to generated subresults that
are used in cobas e flow tests. The generated subresult
is sent to the host with the assigned host code.

If you try to assign a host code that is already in use, a

dialog box informs you that this host code number cannot
be used.

q Only for cobas e flow tests that generated

qualitative/quantitative subresults, you can modify the
Result type value.

j On the Interface options tab, the following check boxes

have to be selected:
m Send cobas e flow test subresults
m Use custom host codes for cobas e flow test
generated subresults

r To assign a host code to a

cobas e flow test generated subresult

1 1 Choose cobas 8000 data manager Test

Configuration > Tests / reference ranges.

6 Configuring the data manager

2
2 In the tests table, double-click the appropriate
cobas e flow test you want to edit.

3
3 In the cobas e flow generated subresults table,
choose the generated subresult for which you want to
assign the host code, and press the Enter key.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 122 cobas e flow test-related settings

4
4 In the Host code for cobas e flow generated
subresults dialog box, enter the host code number
and confirm with the Save button.
I By default, the name of the generated subresult is
used as host code.
From the Result type drop-down list, choose the
result type that the host supports.

u Related topics
• Activating or deactivating the host code assignment
for a cobas e flow test generated subresult (118)

Host code assignment example

The following example shows a cobas e flow test
configured with generated subresults. Here you can
configure the host code and result type of the main test.
You can also configure result types and host codes for
the generated subresults that the system reports to the
host.

For configuration details, see the user documentation.

6 Configuring the data manager

w The Test/reference ranges window, showing assigned host codes

u For an example result message which uses custom

host codes, see cobas e flow test result with custom
host codes (329)
u For configuration information, refer to the cobas 8000
data manager Operator’s manual.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Getting a trace file from the data manager 123

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.

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

communication logs on their own.

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

r To get a data manager host

communication trace file
1 Navigate to c:\data\log

2 Select all the logs in the folder.

I These logs may include:
astm-serial.log
hl7-network.log
astm-network.log
ASTM-message.log
HL7-message.log

3 If you are sending them to a support engineer, save

them in a zip archive or similar convenient

6 Configuring the data manager

compressed format.
I 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.

u Related topics
• Getting a trace file from the control unit (144)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 124 Physical layer specifications

Physical layer specifications

Connect the cables to the data manager server, as
described below for a G5 (Generation 5), a G6
(Generation 6), and a G8 (Generation 8) server.

Connecting a Generation 5 server

C D

A COM / Serial RS232 connection to LIS or host (if used) C Network connection to LIS or host (if used)
B Network connection control unit D Network connection to cobas® link

w Cables for connecting a Generation 5 PC running data manager

6 Configuring the data manager

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Physical layer specifications 125

Connecting a Generation 6 server

C D

A Network connection control unit C Network connection to cobas® link

B COM / Serial RS232 connection to LIS or host (if used) D Network connection to LIS or host (if used)

w Cables for connecting a Generation 6 PC running data manager

6 Configuring the data manager

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 126 Physical layer specifications

Connecting a Generation 8 server

A B

A Network connection control unit Internal HP Ethernet 1Gb C COM / Serial RS232 connection to LIS or host (if used)
2-port Ethernet Adapter 1
B Network connection to LIS or host (if used) Internal HP D Network connection to cobas® link HP NC112T PCl
Ethernet 1Gb 2-port Ethernet Adapter 2 Express Gigabit Server Adapter

w Cables for connecting a Generation 8 PC running data manager

6 Configuring the data manager

Before upgrading to a generation 8 server, consult your

Roche Diagnostics Field Service Representative or the
cobas® 8000 data manager Service Manual.

Network connection
An ethernet cable Cat.5e or better can be used for the
connection to the customer host system. Cat.5e is 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.

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
to act as a TCP/IP server, consult your Roche Diagnostics
service personnel, or see the cobas® 8000 data manager
Service Manual.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Physical layer specifications 127

With cobas® IT firewall When using cobas® IT firewall with data manager, these
defaults are recommended:
• The IP address (172.20.1.31), the Subnetmask
(255.255.255.0) and the default gateway (172.20.1.1)
are fixed
• For ASTM, the TCP port number is fixed to 50001
• For HL7, the TCP port number is fixed to 50002

With FortiGate-40C firewall When using FortiGate-40C firewall with data manager,
these defaults are recommended:
• The IP address (162.132.241.80), the Subnetmask
(255.255.255.0) and the default gateway
(162.132.241.1) are fixed
• For ASTM, the TCP port number is fixed to 50001
• 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).

Running data manager as a server If you have multiple instances of the data manager, or
wish to set up the data manager as a server, consult your
Roche Diagnostics Field Service Representative or the
cobas® 8000 data manager Service Manual.

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

6 Configuring the data manager

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.

! CAUTION
Restart the host task and driver after network
problems
r If problems occur on the network, or the network
connection is lost for some reason, for 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.

u For details of serial connections, see Serial

connection (128).
u For details of restarting the host connection on the
data manager, see Starting and stopping the host
connection (95).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 128 Physical layer specifications

Serial connection
For a serial connection, use a cable RS232c, configured
as shown here.

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

! CAUTION
For serial connection, short shielded cable required.
r For a serial connections, use a shielded RS232c cable,
not longer than 15m.

Communication settings The following diagram shows the recommended default

communication settings.

Item Recommended default communication settings

Communication Port 1

Electrical Signal In accordance with EIA-232-D-1986

Cable Length Maximum 15m

Communication speed (Baud rate) 19200

Parity N

Databits 8
6 Configuring the data manager

Stopbits 1

! CAUTION
Some sites might reconfigure the communication
settings
r The default settings are as given, and these are
recommended for best performance. If a 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.

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

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Physical layer specifications 129

q 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.

6 Configuring the data manager

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 130
6 Configuring the data manager Physical layer specifications

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 131
Table of contents

Configuring the control unit 7

Setting up the control unit for host communications

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.

In this chapter 7
Enabling communication with data manager . . . . . . . 133
Settings for communications with data manager . . . 135
Text settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Test selection inquiry settings. . . . . . . . . . . . . . . . . 136
Test selection inquiry for rerun tests . . . . . . . . . . . 138

7 Configuring the control unit

Enabling requests for rerun or reflex tests . . . . . . 139
Result upload settings . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Configuring result upload . . . . . . . . . . . . . . . . . . . . 140
Upload by test, sample, or cluster . . . . . . . . . . . . . 141
Automatic rerun timing . . . . . . . . . . . . . . . . . . . . . . 141
When ordering HPE tests. . . . . . . . . . . . . . . . . . . . . 142
Getting a trace file from the control unit. . . . . . . . . . . 144

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 132
Table of contents
7 Configuring the control unit

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Enabling communication with data manager 133

Enabling communication with data

manager

r To enable the control unit to

communicate with data manager
1 Navigate to the initial screen: Overview > System
Overview.

2
2 In the section Module Overview, choose the Data
Manager button. The Data Manager Host
Communication dialog is displayed.

3
3 To activate communications between the control unit
and the data manager, choose the Communication

7 Configuring the control unit

Setting button. The Communication Setting dialog
is displayed.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 134 Enabling communication with data manager

4
4 Activate communications by setting the Host
Communications and Control Communications
both to Online. Then choose the OK button to return
to the Data Manager Host Communication dialog.
I 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.
7 Configuring the control unit

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Settings for communications with data manager 135

Settings for 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.

In a production environment, set:

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.

7 Configuring the control unit

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

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 136 Settings for communications with data manager

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

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

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

! CAUTION
Unselect ‘Result message only’ to get all data
r To get all data in a production environment, the option
Result message only for Immunoassay
Qualitative tests must be unselected.

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

Further details For further details of these options, see the control unit’s
online help.

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.
7 Configuring the control unit

Test Selection Inquiry In a production environment, select Test Selection

Inquiry.

Test Selection Timeout In a production environment, select Test Selection

Timeout.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Settings for communications with data manager 137

Default is 18 seconds. In production environments, it is

recommended to use the default, and handle host
communications timeouts on the data manager.
u For details of how the data manager handles timeouts
from the host and control unit, see Test selection
inquiry timeout settings (98).

Automatic Rerun Test Selection In a production environment, select Automatic Rerun

Test Selection.

Additionally, select this option when the following are

used:
• Rerun and/or Reflex Orders from data manager or
host
• cobas e flow tests
u To enable requests for rerun / reflex tests, other
settings have to be done, see Repeat, rerun, and reflex
tests (42).

Manual Rerun Test Selection In a production environment, select Manual Rerun Test
Selection.

Additionally, select this option when the following are

used:
• Rerun and Reflex Orders
• cobas e flow tests

STAT Test Selection In a production environment, select STAT Test

Selection.

Test Selection Inquire Always In a production environment, select Test Selection

7 Configuring the control unit

Inquire Always.

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

Priority Mode.
u For more information about this setting, see Throttle
instrument settings (102).

Test Selection Ask in Barcode Read Error If your sample tubes have barcodes, keep Test Selection
Ask in Barcode Read Error unselected.

When Test Selection Ask in Barcode Read Error is

unselected, an unreadable barcode triggers an error on
the analyzer. See the cobas® 8000 data manager
Operator’s Manual for details on how the analyzer
operator handles barcode read errors.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 138 Settings for communications with data manager

Only select this option if you are using samples without a

barcode, for example if using aliquots from a MODULAR
PRE-ANALYTICS.
u For a more detailed description of how to implement
this option, see Using MODULAR PRE-
ANALYTICS (445).

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.
u The barcode readers are deactivated, for example,
when identifying samples by sequence number. For
details, see Identifying patient samples by sequence
number (455).

Further details For further details of these options, see the control unit’s
online help.

Test selection inquiry for rerun tests

The time when control unit sends the data manager a test
selection inquiry message for rerun tests, is controlled by
the same settings as result upload.
• By Sample: The control unit sends a test selection
7 Configuring the control unit

inquiry for reruns on a sample basis, after all test

results for the sample become complete.
• By Cluster: The control unit sends a test selection
inquiry for reruns on a cluster basis, after all test
results in a sample that run on a cluster become
complete.
• By Test: The control unit sends a test selection inquiry
for reruns on a cluster basis, the same as By Cluster.
Note that the inquiry is not done on a test basis.

The test selection inquiry for rerun tests is by default sent

as soon as all the tests in the sample or cluster become
complete. This functionality is affected by the result
upload checkbox As Soon As Setting. When the
checkbox As Soon As Setting is enabled, the tests
marked “Autorerun enabled” get priority. They are
treated as if they belonged to a separate sample from the
other tests.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Settings for communications with data manager 139

Automatic rerun is not available for cobas e flow tests.

u For details of the result upload settings, see Result
upload settings (140)
u For details of the By Cluster options, see By cluster
options (141)

Enabling requests 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.

r 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 check box Automatic
Rerun is selected.

3 Navigate to Utility > System > Data Manager

> Test Selection Inquiry Settings > Automatic
Rerun Test Selection is selected.

7 Configuring the control unit

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 140 Result upload settings

Result upload settings

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

The currently selected result upload settings are also

displayed on the data manager. The control unit sends
the current settings to the data manager when the
instrument enters the preparation state. The settings are
displayed in cobas 8000 data manager Service
> Service-related configuration > Interface options
> Result upload settings.

The result upload settings can only be changed on the

control unit, and are displayed on the data manager for
information only.
u For more information on viewing these settings on the
data manager, see Viewing result upload settings on
the data manager (107).

Configuring result upload

r To configure how the control unit

uploads results
1 Navigate to Utility > System > Result Upload
7 Configuring the control unit

Settings.

2 From the drop-down list for the type of result you want
to configure, select one of the available options:
• By Sample
• Chemistry incl. ISE / Immunoassay
• ISE / Chemistry / Immunoassay
• By Test
• No Upload
I You can separately configure routine sample
results, STAT sample results or quality control
results, and calibration results.

3 Select the As Soon As Setting check box.

u Related topics
• For further details, see the following sections Upload
by test, sample, or cluster (141) and Automatic rerun
timing (141).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Result upload settings 141

Upload by test, sample, or cluster

You can set the control unit to upload results by sample,
by test or by cluster.
• By test means that the control unit uploads each
result as soon as it is ready. Calibration results,
manually resent QC results, and calculated QC results
are always uploaded by test.
• By sample means that the control unit waits until all
the results for a sample are ready, and then uploads
all of them together.
• By cluster means that the control unit waits until all
the results for a given sample being measured by a
given cluster are ready, and then uploads all of them
together. A “cluster” in this case can be defined as all
modules of a given type: c-module, e-module, ISE. For
example, if the instrument has 2 e-modules, these
modules would constitute a single cluster.)
• A No result upload option is also available.

! CAUTION
Uploading by test is recommended when ordering
HPE tests
r We recommend using the By Test upload mode for
samples with HPE tests.

u For further details, see When ordering HPE tests (142)

By cluster options There are 2 by cluster options:

• Chemistry incl. ISE / Immunoassay: Chemistry and

7 Configuring the control unit

ISE modules are treated as a single cluster.
• ISE / Chemistry / Immunoassay: Chemistry and ISE
modules are treated as separate clusters.

Automatic rerun timing

The data manager forwards all rerun queries immediately
to the host as soon as it receives them from the control
unit.

To set the control unit to upload the results to the data

manager and to request reruns as soon as possible,
select the As Soon As Setting check box. This can help
prevent overloading on a busy system.

The As Soon As Setting feature sends R2 test inquiries

or uploads test results as soon as all tests with automatic
rerun selected have received their results.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 142 Result upload settings

The As Soon As Setting sets the automatic rerun start

timing.

Result output As Soon As Setting The control unit sends a The control unit marks the test for Automatic Rerun,
setting result to the data manager, and sends a rerun inquiry (R2) to the data
when the sample has: manager(1), when the sample has:
By sample Selected A result for every “Autorerun enabled” test.
Cleared A result for every test.
By cluster Selected A result for every “Autorerun enabled” test in the corresponding cluster.
Cleared A result for every test in the corresponding cluster.
By test Selected A result for a test. A result for every “Autorerun enabled” test in the
corresponding cluster.
Cleared A result for a test. A result for every test in the corresponding cluster.
No upload Selected (Not sent) A result for every “Autorerun enabled” test.
Cleared (Not sent) A result for every test.
y Timing Automatic Rerun requests with As Soon As Setting
(1) The control unit only sends a rerun inquiry (R2) to the data manager if “Autorerun enabled” is set for a test.

Sending the rack to the output buffer If the As Soon As Setting check box is selected, the
analyzer sends the rack to the output buffer after the
control unit has sent the first results to the data manager.
The Autorerun enabled setting does not affect this. This
allows the data manager to make additional requests
after the first results are sent.

If the As Soon As Setting check box is cleared, the

analyzer sends the rack to the output buffer after it has
performed the tests, and determined that no rerun is
required, but before sending the results to the data
manager.
7 Configuring the control unit

When ordering HPE tests

Samples with HPE tests do not support upload By
Sample or disabling the As Soon As Setting, as
explained in the chart below.

The changes in behavior explained below are not

reflected in the actual interface or configuration. They
occur for all HPE tests, whether regular tests,
cobas e flow tests or embedded tests.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Result upload settings 143

Selected upload mode As Soon As Setting HPE test is ordered Changes in behavior
No No changes

Off The data manager uploads results for the current sample
Yes as though By Cluster 1 or By Cluster 2 were selected
with As Soon As Setting on
By Sample
No No changes

On The data manager uploads results for the current sample

Yes as though Chemistry incl. ISE / Immunoassay or ISE /
Chemistry / Immunoassay were selected
No No changes
Off The data manager uploads results for the current sample
Yes
By Cluster as though As Soon As Setting were on
No No changes
On
Yes No changes
No No changes
Off The data manager uploads results for the current sample
Yes
By Test as though As Soon As Setting were on
No No changes
On
Yes No changes
y Changes in upload mode behavior

u For details on the basic upload behavior of the

different upload modes, see Upload by test, sample, or
cluster (141)

7 Configuring the control unit

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 144 Getting a trace file from the control unit

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.

You can find the Communication Trace file options by

navigating to Print > Utility > Communication Trace.

q 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.

q 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.
7 Configuring the control unit

r 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 is displayed.

2 From the list on the left of the Utility screen, select

Communication Trace. The Communication Trace
options screen is displayed.

3
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
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Getting a trace file from the control unit 145

7
7 On the left of the screen, in the list of reports, select
the communication trace report that you created. It is
displayed in the main window on the right.
I You can view the report in a number of ways:
Zoom: Zooms in or out the main window. There
are 3 different levels of zoom.
Backup: Saves to a PDF file.
Print Out: Prints out to a physical printer.

u Related topics
• Getting a trace file from the data manager (123)

7 Configuring the control unit

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 146
7 Configuring the control unit Getting a trace file from the control unit

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 ASTM reference

8 ASTM protocol (LIS2 - A2) ...............................................................................149

9 ASTM text content (LIS2 - A2)........................................................................161
10 ASTM communication examples....................................................................201

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 149
Table of contents

ASTM protocol (LIS2 - A2) 8

This chapter presents the lower layers of the ASTM (or

LIS2-A2) protocol, as used by cobas® 8000 data
manager.

In this chapter 8
Overview of the ASTM protocol . . . . . . . . . . . . . . . . . . 151
Communication processing layers . . . . . . . . . . . . . . . . 152
ASTM lower layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
ASTM message framing . . . . . . . . . . . . . . . . . . . . . . . . 154
ASTM syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Coding rules for the messages . . . . . . . . . . . . . . . . 155
Message transmission phases . . . . . . . . . . . . . . . . . . . 158

8 ASTM protocol (LIS2 - A2)

Checksum calculation / message frame . . . . . . . . . . . 159

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 150
Table of contents
8 ASTM protocol (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Overview of the ASTM protocol 151

Overview of 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.

8 ASTM protocol (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 152 Communication processing layers

Communication processing layers

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

B H|\^&|||H7600^1|...

C <STX>FN Text<ETB>...

D 10011011100110010...

A Application Layer - server specification of host C ASTM Lower Layer - ASTM E1381-91
communication
B ASTM Upper Layer - ASTM E1394-91 D Physical Layer

w 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.
• ASTM E1381-91 Low Level Protocol
Specification for Low Level Protocol to Transfer
Messages Between Clinical Laboratory Instruments
8 ASTM protocol (LIS2 - A2)

and Computer Systems

• ASTM E1394-91 High Level Protocol
Standard Specification for Transferring Information
Between Clinical Instruments and Computer Systems

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 ASTM lower layer 153

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.

q 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.

8 ASTM protocol (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 154 ASTM message framing

ASTM message framing

Item Method Explanation
Frame Configurations For Middle Frame o Control character (characters enclosed in <>):
<STX> FN text <ETB> C1 C2 <STX> is control character (HEX 02)
<CR><LF> <ETB> is control character (HEX 17)
For Last Frame <CR> is control character (HEX 0D)
<STX> FN text <ETX> C1 C2 <LF> is control character (HEX 0A)
<CR><LF> <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><DC4> <NAK> is control character (HEX 15)
<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 for text, plus 7
the Frame 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
8 ASTM protocol (LIS2 - A2)

last frame and is indicated by <ETX>. All others are intermediate

(middle) frames and are indicated by <ETB>.
y ASTM (LIS2-A2) message framing

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 ASTM syntax 155

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.

8 ASTM protocol (LIS2 - A2)

! CAUTION
Field delimiter = vertical bar ‘|’
Field delimiter ‘|’ supported, but no others
r The field delimiter ‘|’ is supported in the current
version of cobas® 8000 data manager. 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 ‘|’.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 156 ASTM syntax

! CAUTION
Repeat delimiter = backslash ‘\’
Repeat delimiter ‘\’ supported, but no others
r The repeat delimiter ‘\’ is supported in the current
version of cobas® 8000 data manager. Other repeat
delimiters are not supported.

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 ‘\’.

! CAUTION
Component delimiter = caret ‘^’
Component delimiter ‘^’ supported, but no others
r The component delimiter ‘^’ is supported in the
current version of cobas® 8000 data manager. 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 ‘^’.
! CAUTION

Escape character = ampersand ‘&’

Escape character ‘&’ not supported
r The escape character is not supported in the current
version of cobas® 8000 data manager. This character
is reserved for future use.
8 ASTM protocol (LIS2 - A2)

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 ‘&’.

! CAUTION
Special characters with escape character
Special characters not supported
r The special escape sequences are not supported with
special character in the current version of
cobas® 8000 data manager. This character is
reserved for future use.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 ASTM syntax 157

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

8 ASTM protocol (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 158 Message transmission phases

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.
• Establishment phase
• Transfer phase
• Termination phase

A B

ENQ EOT
C

D
ACK ACK ACK

E F G

A Intermediate frame E Establishment phase (ACK must be sent within 10 ms.)

B End frame F Transfer phase
C Sender G Termination phase
D Receiver

w Message transmission phases

! CAUTION
Acknowledge must be received from the host within
8 ASTM protocol (LIS2 - A2)

10 ms
r The host must send an ACK reply to data manager
within 10 ms. Otherwise the 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
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Checksum calculation / message frame 159

Checksum calculation / message frame

[STX] FN 7H[WÀUVWFKDU7H[WODVWFKDU ETB CH CL [CR] [LF]

w The intermediate frame

[STX] FN 7H[WÀUVWFKDU7H[WODVWFKDU ETX CH CL [CR] [LF]

w 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].

Example for checksum calculation [STX]1Test[ETX]

8 ASTM protocol (LIS2 - A2)

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
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 160
8 ASTM protocol (LIS2 - A2) Checksum calculation / message frame

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 161
Table of contents

ASTM text content (LIS2 - A2) 9

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 9
List of record levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
List of messages used in host communication . . . . . 164
Messages transmitted by the data manager . . . . 164
Messages transmitted by the host . . . . . . . . . . . . . 165

9 ASTM text content (LIS2 - A2)

Description of ASTM records . . . . . . . . . . . . . . . . . . . . 167
Message Header Record . . . . . . . . . . . . . . . . . . . . . . . . 168
Patient Information Record . . . . . . . . . . . . . . . . . . . . . . 170
Order Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Comment Record (following Order Record) . . . . . . . . 177
Result Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Result Record description . . . . . . . . . . . . . . . . . . . . 178
R-4 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
R-4 for tests with quantitative or
quantitative/qualitative results . . . . . . . . . . . . . 184
R-4 for tests with qualitative or
qualitative/quantitative results . . . . . . . . . . . . . 185
R-4 for tests with data point and raw data
values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
About qualitative results . . . . . . . . . . . . . . . . . . 186
Comment Record (following Result Record) . . . . . . . 187
Query Record (Request Information Record) . . . . . . . 189
Photometric Calibration Result M(PCR) . . . . . . . . . . . 193
ISE Calibration Result Record - M(ICR). . . . . . . . . . . . 194

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 162
Table of contents

ISE data alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

ISE calibration analytical data . . . . . . . . . . . . . . . . . 195
E-module (immunology) Calibration Result Record -
M(ECR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Message Termination Record . . . . . . . . . . . . . . . . . . . . 199
9 ASTM text content (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 List of record levels 163

List of record levels

The following table shows the Standard Record types and
levels specified by the protocol ASTM E1394-91.

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
y ASTM record types and levels

u For details of ASTM E1394-91, see the information

given in Communication processing layers (152).

9 ASTM text content (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 164 List of messages used in host communication

List of 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 Direction Realtime Batch Communication

Communication
Test Selection Information Host to data manager Available Available
Order Query Host to data manager Not available Available
Result Query Host to data manager Not available Available

Test Selection Inquiry data manager to Host Not available Available

Patient Sample Analytical Data data manager to Host Available Available
Control Sample Analytical Data data manager to Host Available Available
Calibration Analytical Data data manager to Host Available Not available
y Messages used in host communication (ASTM)

Messages transmitted by the data manager

Messages transmitted from data manager to the host are
shown in the table below. In the following charts:
• [ ] Square brackets indicate an optional segment. (0 -
9 ASTM text content (LIS2 - A2)

1 times)
• { } 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.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 List of messages used in host communication 165

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
L the ID reader.
Test Selection Information H TSUPL Test selection upload for a
P sample as answer to an order
O query.
C
L
Result report H RSUPL Reports on the result at the point
P when the results for the sample
O have been accumulated, or when
C the results for the sample have
{ been requested by the host.
R Transmits results of the selected
{C} sample(s) by instruction at the
} analyzer.
L RSUPL^REAL First transmission of QC results,
from data manager to host.
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.

9 ASTM text content (LIS2 - A2)

y Messages transmitted by the data manager

Messages transmitted by the host

The data manager can receive the following messages
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
O selection inquiry or as unsolicited
[C] test selections send in batch
L mode by the host
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
Q test selections known to the data
L manager, sent from host.
y Messages transmitted by the host

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 166 List of messages used in host communication

u For details of using result and order queries with

limited sample lifetimes or expired sample IDs, see:
Result query (74)
Order query (75)
Order and result queries with limited sample
lifetime (81).
9 ASTM text content (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Description of ASTM records 167

Description of ASTM records

Each record of the ASTM message is divided into fields
and subfields.

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.

9 ASTM text content (LIS2 - A2)

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.
y Attributes of a field in an ASTM message

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 168 Message Header Record

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.06|||||host|TSREQ|P|1|20171026142034|

H|\^&|12345||cobas 8000^1.06|||||host|TSUPL|P|1|20171026142034|

H|\^&|12345||cobas 8000^1.06|||||host|RSUPL|P|1|20171026142034|

H|\^&|12345||cobas 8000^1.06|||||host|RSUPL^REAL|P|1|20171026142034|

H|\^&|12345||cobas 8000^1.06|||||host|RSUPL^BATCH|P|1|20171026142034|

H|\^&|12345||cobas 8000^1.06|||||host|PCUPL^REAL|P|1|20171026142034|

H|\^&|12345||cobas 8000^1.06|||||host|ICUPL^REAL|P|1|20171026142034|

H|\^&|12345||cobas 8000^1.06|||||host|ECUPL^REAL|P|1|20171026142034|

H|\^&|12345||host|||||cobas 8000^1.06|TSDWN|P|1|20171026142034|

H|\^&|12345||host|||||cobas 8000^1.06|RSREQ|P|1|20171026142034|

H|\^&|12345||host|||||cobas 8000^1.06|TSREQ|P|1|20171026142034|

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]
9 ASTM text content (LIS2 - A2)

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.
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
u To edit the Sender ID, see Configuring the data manager host interface
options (97).
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.
y Message header record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Message Header Record 169

Field Ref. Value Host DM Description

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 o First transmission of QC results, from data manager to host.
o 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.
For a calibration message, the date and time of the calibration.
y Message header record

9 ASTM text content (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 170 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.
y Patient information record
9 ASTM text content (LIS2 - A2)

! WARNING
The data manager supports only M, F, or U for
patient sex.
r For male patients, the host must send M, for females,
F. Otherwise the wrong reference range might be
applied. The data manager reads any other value as U,
and applies the reference ranges for a patient of
unknown sex.
r 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
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Order Record 171

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

Order record in TS Download message

O|1|500169|^50017^3^^S1^SC|^^^8706^|R||||||A||||1||||||||||O

Order record in Result Upload message This example shows 3 ISE tests.

O|1|10005|0^110005^2^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|R|20170429161525|20170429161525||||N||||1
||||||||||F|

Order record in Quality Control result

message
O|1|HBCN^611490^1^20160831^29|0^30001^2^^QC^SC^not|^^^870^1|R||||||Q||||4||||||||||F|

Order record with sequence number in TS

Download
O|1||1013^50101^3^^S1^SC^not|^^^8571^1\^^^8413^1\^^^8706^1\|R|20170715093311|20170715093311||||A||||
1||||||||||O

Order record with sequence number in Result

Upload
O|1||1013^50101^3^^S1^SC^not|^^^8571^1\^^^8413^1\^^^8706^1|R|20170715093311|20170715093311||||N||||1
||||||||||F|

9 ASTM text content (LIS2 - A2)

Order record from cobas e flow test result
message
O|1|101801|0^50461^1^^S1^^not|^^^32000^1\|R|20171201160409|20171201160409||||N| |||1||||||||||F|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 172 Order Record

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, or for R/O R Identifier for the sample, (sample ID).
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.
u For details of sequence numbers, see Identifying patient samples by
sequence number (455).
For Quality Control material, Name^Lot^ID^ExpDate^ControlCode
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)
o ExpDate Expiry date of control lot (Date)
o ControlCode Control code used to uniquely identify the QC material
on the host. (Also contained in data manager.) Populated by the QC
code field of the Insert QC material form
It is not possible to order test selections for QC from the host.
4 8.4.4 Complex or R O/R Instrument sample identifier, with additional information for identifying the
Number sample.
Sequence_Number^Rack_ID^Position^^Rack_Type^Containe
r^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.
y Order record
9 ASTM text content (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Order Record 173

Field Ref. Value Host DM Description

4.1 Number O R Sequence_ For patient samples identified by sample ID (default),
Number and 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 Hemolysate (only supported by e 801 module)
o S9 Amniotic fluid (only supported by e 801 module)
o SA Processed stool (only supported by e 801
module)
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 code identifying the container.

9 ASTM text content (LIS2 - A2)

o SC Standard cup
o MC Micro cup
o NST0 Non-standard tube
o FBT1 False bottom tube 1
o FBT2 False bottom tube 2
o FBT3 False bottom tube 3
o <Empty> Unknown cup type
If the host sends no container type value, then data
manager sends no value to the control unit.
u For details on how these values are handled, see
Sample container types (41).
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
y Order record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 174 Order Record

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|10005|0^110005^2^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|
R|20170429161525|20170429161525||||N||||1||||||||||F|
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.
u For more details on sending serum index orders, see Sending test
selections (77).
Orders with invalid (unknown) test codes are handled by the data manager
as follows:
o If an order contains both valid and invalid test codes, the data manager
accepts the order but logs an error for each invalid test code.
o If an order contains only invalid test codes, the data manager rejects the
order.
o The rejection of invalid test codes and/or orders is shown in the
information window.
5.1 First component contains no data.
5.2 Second component contains no data.
5.3 Third component contains no data.
y Order record
9 ASTM text content (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Order Record 175

Field Ref. Value Host DM Description

5.4 String 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 data manager Operator’s
Manual.
If this field contains an invalid code, the test selection
will be ignored, and an error shown in the LIS Messages
screen of the data manager.
Embedded tests of cobas e flow tests cannot be
ordered. If this field contains the test code of an
embedded test, the data manager will return an error
message.
5.5 String (or O O Dilution Dilution factor. Sent also by the data manager if
number) available, 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: 1 , Inc , Dec , 3 , 5 , 10 , 20 , 50 .
o For an e 602 module test: 1 , 2 , 5 , 10 , 20 , 50 ,
100 , 400
o For a regular e 801 module test: 1 , 1.1 , 2 , 5 , 10 ,
20 , 30 , 50 , 100 , 400 , 900 , 27000
For the above tests, the value 1 means no dilution. If the
host sends an empty field, this defaults to 1 .

9 ASTM text content (LIS2 - A2)

o For an e 801 cobas e flow test: 1 or empty
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.
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 test (or rerun test, if a test with the same number already exists)
o R Rerun test (or add test, if a test with the same number does not
already exist)
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.
y Order record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 176 Order Record

Field Ref. Value Host DM Description

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 Hemolysate (only supported by e 801 module)
o 9 Amniotic fluid (only supported by e 801 module)
o A Processed stool (only supported by e 801 module)
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.
9 ASTM text content (LIS2 - A2)

o O Sent from host.

o F Sent from data manager / cobas® 8000 modular analyzer series.
y Order record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Comment Record (following Order Record) 177

Comment Record (following Order Record)

Record to transfer comments. This record is transmitted
by the host (within test selection messages) or the data
manager (within result messages or test selection
uploads). These comments are visible on the control unit.

From the host:

C|1|L|Comment1^Comment2^Comment3^Comment4^Comment5|G

From the data manager:

C|1|I|Comment1^Comment2^Comment3^Comment4^Comment5|G

! CAUTION
Special format of cobas® 8000 data manager
comment records
r The format of the comment record is not totally in
accordance with the LIS2-A2 standard, 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.

9 ASTM text content (LIS2 - A2)

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 data manager, 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
These comments are visible on the control unit, in Workplace > Data Review.
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.
y Comment record (following Order Record)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 178 Result Record

Result Record
The data manager uses the result record to upload the
details of test results.

In this section
Result Record description (178)
R-4 description (184)

Result Record description

The data manager uses the result record to upload the
details of test results.

For an automatically-validated result, the operator is

written as “SYSTEM”.

A quantitative patient result:

R|1|^^^990/1/not|0.06|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171127183657|2017112718371
2|ISE^1^MU1#ISE#1#1^3^771|

A qualitative and qualitative patient result:

R|17|^^^22001/1/not|15^73.7|%|^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162612|DM^0^DM#DM#0#0^0^
|

For an automatically-validated QC result:

9 ASTM text content (LIS2 - A2)

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

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

R|1|^^^989/1/not|2.1|mmol/L|^TECH\9 - 144^NORM\^CRIT\^USER|HU||F||bmserv^SYSTEM|20170621084348|20170
621084404|ISE^1^MU1#ISE#1#1^3^28|

R|1|^^^12000/1/not|-1^ ||^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162536|DM^0^DM#DM#0#0^0
^|

This shows a quantitative and qualitative subresult of a

cobas e flow test:

R|3|^^^12000/1/not^^HIVAG_01/1|-1^0.185|COI|^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162536|DM^
0^DM#DM#0#0^0^|

This shows an embedded test subresult of a

cobas e flow test:

R|5|^^^12000/1/not^^11014/1|-1^0.712|COI|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20160312114537|2
0160312120410|e801^2^MU1#e801#2#2^10^1017|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Result Record 179

This shows the EFS part of an embedded test subresult

with raw data:

R|6|^^^12000/1/not^^11014/1|840.8573|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20160312114537
|20160312120410|e801^2^MU1#e801#2#2^10^EFS|

u For an example of a result with raw data and data

point values, see e 801 result message with raw data
and data points (212)

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.
y Result record

9 ASTM text content (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 180 Result Record

Field Ref. Value Host DM Description

3 9.3 Complex R Testcode and dilution. Takes the format:
^^^Testcode/Dilution/Pre-dilution/CombinationID
Note that the fourth component is separated into four parts with a forward-
slashseparator /
3.1 This component contains no data
3.2 This component contains no data
3.3 This component contains no data
3.4 Testcode and dilution, separated by forward slashes (ASCII 47 or 2F) in the format:
Testcode/Dilution/Pre-dilution/CombinationID
R Testcode String 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: 1 , Inc , Dec , 3 , 5 , 10 , 20 , 50 .
o For an e 602 module test: 1 , 2 , 5 , 10 , 20 , 50 ,
100 , 400
o For an e 801 module test: 1 , 1.1 , 2 , 5 , 10 , 20 ,
30 , 50 , 100 , 400 , 900 , 27000
O Pre- String Indicates whether sample is pre-diluted:
dilution o pre-diluted
o not
O Combinatio String Only sent in cobas e flow test calculated QC results.
nID This component is omitted in all other cases.
3.5 This component contains no data
3.6 For regular tests: this component contains no data.
For cobas e flow tests: Subresult code including dilution and combination ID,
separated by forward slashes (ASCII 47 or 2F), in the format:
9 ASTM text content (LIS2 - A2)

SubresultCode/Dilution/CombinationID
O SubresultC String Identifier (or testcode) for the subresult reported by a
ode cobas e flow test. This subresult can be the result of
an embedded test, or a generated subresult created
internally by the cobas e flow test.
In the case of linkage records: cobas e flow test
code. For example:
R|28|^^^12001/1/not^^12001/1/5

O Dilution String Dilution factor of the embedded test reported in

Subresultcode .
O Combinatio Number Only sent in cobas e flow test linkage records. The
nID combination ID links a calculated QC result to the
cobas e flow test result.
This component is omitted in all other cases.
u Sending additional link information for calculated
QC (111).
4 9.4 Complex R Result value(s).
The result values are only transmitted for patient and QC results.
Takes the format:
ResultValue1^ResultValue2
The result values that are sent differ depending on the result type of the test. The
differences are explained in a series of separate tables in the next section.
u R-4 description (184).
y Result record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Result Record 181

Field Ref. Value Host DM Description

5 9.5 String O Units in which result is measured. (for example, mmol/L, etc.)
For a data point result, this shows count or COUNT .
6 9.6 Complex O For patient results, reference ranges, if defined. Empty for QC results and raw
data/data point 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.
7 9.7 String O Result abnormal flags for patient results. This is empty for manually-edited
results.
HH Above high critical value

9 ASTM text content (LIS2 - A2)

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
HU High uncertainty (enhancement to ASTM)
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.
u For further details on the EP17-A flags, see EP17-A and the result abnormal
flags (53).
8 9.8 Field contains no data.
y Result record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 182 Result Record

Field Ref. Value Host DM Description

9 9.9 Character R Result status:
o F : First run result, or QC result
o C : Corrected result
o M : Manually-edited result
o X:
o Calculated test, but test could not be calculated (for example, divided by
zero)
o Canceled cobas e flow test. (All measured embedded test results are
transmitted, if enabled.)
o B : Additional record. A linkage record, used to link the result to a calculated
QC result.
o V : Verified. A measured embedded test result which has been propagated to
the result of a cobas e flow test.
For cobas e flow tests, the value that is sent can be affected by the Use legacy
record status check box.
u Using legacy record status (112)
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 Time of measurement. (Format: YYYYMMDDhhmmss.)
y Result record
9 ASTM text content (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Result Record 183

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 This field contains:
o c502 , c701 , e602 , ISE , c702 , e801 for results from
measuring modules, or manual results entered on behalf of a
specific module.
o DM for results or values that cannot be attributed to a
module, i.e.:
o Results calculated on the data manager: formulas, and
calculated results from cobas e flow tests.
o Manual results entered on the data manager, but which
cannot be attributed to a module.
o cobas e flow test results which contain generic alarm
flags.
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
u For details, see Identifier of the analytical unit sent to
host (108).
14.4 Number R Instrument Instrument number in data manager. (A specific identifier inside
ID the data manager which identifies a module. This is a number
which has no relationship to the internal position of the module

9 ASTM text content (LIS2 - A2)

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.
For raw data results, contains one of the following codes,
signifying raw data type:
o EFS Effective signal
o EFV Effective voltage
o EFC Effective current
o PMT PMT spike
14.6 String R Bottle Used Reagent Set.
o Current
o Standby
o (or empty)
Reserved field, only for QC measurements, otherwise not sent.
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 not sent.
y Result record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 184 Result Record

R-4 description
The result values of the test are sent in field R-4. The
format of the field differs depending on the result type of
the test. This section explains the format for each type.

The result values are only transmitted for patient and QC

results.

For cobas e flow tests, the order in which

quantitative/qualitative result values are sent can be
configured. For cobas e flow tests, the following result
types are supported:
• Quantitative
• Qualitative
• Quantitative/qualitative
• Qualitative/quantitative
In this section
R-4 for tests with quantitative or quantitative/qualitative
results (184)
R-4 for tests with qualitative or qualitative/quantitative
results (185)
R-4 for tests with data point and raw data values (185)
About qualitative results (186)

R-4 for tests with quantitative or quantitative/qualitative results

9 ASTM text content (LIS2 - A2)

For regular tests or cobas e flow tests with pure

quantitative results, and for cobas e flow tests with
quantitative/qualitative results, R-4 takes the following
format:

Field Value Host DM Description

4 Complex - R QuantitativeResult^QualitativeResult
4.1 Number - R QuantitativeRes A quantitative result value.
ult For regular tests, if suppression of results outside the technical
limit is enabled, suppressed results are sent as 7 spaces (ASCII 32 /
0x20).
u Result suppression for results outside the technical limit (54)
For omitted cobas e flow test results, a configured value is sent.
u Configuring omitted result reporting (114)
4.2 Number - O QualitativeResu Empty or a qualitative result value.
lt u About qualitative results (186)
For a main result of a quantitative cobas e flow test, this field is
empty.
y R-4 for tests with pure quantitative results, or with quantitative/qualitative results

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Result Record 185

R-4 for tests with qualitative or qualitative/quantitative results

For regular tests or cobas e flow tests with pure
qualitative results, and for cobas e flow tests with
qualitative/quantitative results, R-4 takes the following
format:

Field Value Host DM Description

4 Complex - R QualitativeResult^QuantitativeResult
4.1 Number - R QualitativeResu A qualitative result value.
lt u About qualitative results (186)
For regular tests, if suppression of results outside the technical limit
is enabled, suppressed results are sent as 7 spaces.
u Result suppression for results outside the technical limit (54)
For omitted cobas e flow test results, a configured value is sent.
u Configuring omitted result reporting (114)
4.2 Number - O QuantitativeRes The quantitative value, like value for a quantitative result. For e-
ult module qualitative results this contains COI .
For a main result of an assignment/formula, this field is empty.
For a main result of a qualitative cobas e flow test, this field is
empty.
y R-4 for tests with pure qualitative results, or with qualitative/quantitative results

R-4 for tests with data point and raw data values
If the data manager is configured to send raw data and
data point values for a regular test or cobas e flow test
result, R-4 takes the following format:

9 ASTM text content (LIS2 - A2)

Field Value Host DM Description
4 Complex - R ReportableResult^DataPointValues
4.1 Number - R ReportableResul The result value.
t For regular tests, if suppression of results outside the technical limit
is enabled, suppressed results are sent as 7 spaces (ASCII 32 /
0x20).
u Result suppression for results outside the technical limit (54)
For omitted cobas e flow test results, a configured value is sent.
u Configuring omitted result reporting (114)
4.2 Number - R/O DataPointValues Data points. Up to 200 data point values, separated by backslashes
(\).
y R-4 for tests with data point and raw data results

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 186 Result Record

About qualitative results

A qualitative result value sent in R-4 can take the
following values:
• For c-modules and ISE modules: an integer code from
-2 to 3 inclusive.
• For e-modules: an integer code -1 (non-reactive), 0
(border line), 1 (reactive).
• For cobas e flow tests, this can be a numeric code.
u For cobas e flow test codes, see Result message
codes for cobas e flow tests (439)
u The codes can be configured on the cobas® 8000
modular analyzer series instrument, under Utility
> Application > Range. See the cobas® 8000
modular analyzer series Operator’s Manual for details.
9 ASTM text content (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Comment Record (following Result Record) 187

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^2010102616

4238|G|

! CAUTION
Special format of cobas® 8000 data manager

9 ASTM text content (LIS2 - A2)

comment records
r The format of the comment record is not totally in
accordance with the LIS2-A2 standard, 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.
y Comment record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 188 Comment Record (following Result Record)

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.
u For details of the error flags, see Data alarms (363).
A main test in a cobas e flow test message generates
only this error:
o eFlow.E Standard alarm for cobas e flow tests
4.2 String Descripti Description of error flag (blank if no error)
on
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.
y Comment record
9 ASTM text content (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Query Record (Request Information Record) 189

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||AL
L|||||||R|O||

From host to data manager:

Q|1|^S1^10001|||||||||||

Q|1|^S2^10001||||||||||O|

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:

9 ASTM text content (LIS2 - A2)

Q|1|^S1^^1013||||||||||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.
y Query record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 190 Query Record (Request Information Record)

Field Ref. Value Host DM Max Description

Size
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 Hemolysate (only supported by e 801
module)
S9 Amniotic fluid (only supported by
e 801 module)
SA Processed stool (only supported by
e 801 module)
S0 A rack with no specimen assigned.
(Only supported for queries sent by the
data manager.)
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.
9 ASTM text content (LIS2 - A2)

This must be blank if Q-3.4 contains the sequence

number.
u For details of using result and order queries
with limited sample lifetimes or expired sample
IDs, see:
Result query (74)
Order query (75)
Order and result queries with limited sample
lifetime (81).
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.)
u To learn how to use this, see Identifying patient
samples by sequence number (455).
Previously, this field was known as “Sample
Number.”
The further components contain no data.
y Query record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Query Record (Request Information Record) 191

Field Ref. Value Host DM Max Description

Size
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^R
ack_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.)
u To learn how to use this, see Identifying patient
samples by sequence number (455).
Previously, this field was known as “Sample
Number.”
3.5 String - R 5 Rack_ID Identifier of the rack sent by cobas® 8000 modular
analyzer series 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

9 ASTM text content (LIS2 - A2)

S3 Cerebrospinal Fluid
S4 Supernatant
S5 Other fluids
S6 Whole blood
S7 Oral Fluids (Saliva)
S8 Hemolysate (only supported by e 801
module)
S9 Amniotic fluid (only supported by
e 801 module)
SA Processed stool (only supported by
e 801 module)
S0 A rack with no specimen assigned.
(Only supported for queries sent by the
data manager.)
y Query record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 192 Query Record (Request Information Record)

Field Ref. Value Host DM Max Description

Size
3.9 String - O 2 Container A code identifying the container:
MC Micro cup
SC Standard cup
NST0 Non-standard tube
FBT1 False bottom tube 1
FBT2 False bottom tube 2
FBT3 False bottom tube 3
<Empty> Unknown cup type
If the host sends no container type value, then data
manager sends no value to the control unit.
u For details on how these values are handled,
see Sample container types (41)
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.
9 ASTM text content (LIS2 - A2)

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
y Query record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Photometric Calibration Result M(PCR) 193

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. In the message’s
first M(PCR) record, the field value is ‘1’; the value increments by 1 in
each subsequent M(PCR) record in the message.
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 5 Test Code (Application code).
^^^Testcode
The Test Code is a string type.
The maximum length of the test code is 5 characters.
6 14 String - R 20 ID of the analytical unit (module) the test belongs to.
u For details, see Identifier of the analytical unit sent to host (108).
7 14 Number - R 3 Calibration alarm.
u For details, see Data alarms (363).
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:

9 ASTM text content (LIS2 - A2)

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 u For details, see Instrument alarms (423).
Number - 6 Prozone Value Blank: not sent by the cobas® 8000 modular
analyzer series. Reserved for future use.
The following fields contain no data.
y Photometric Calibration Result M(PCR)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 194 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.
u For details, see Identifier of the analytical unit sent to host (108).
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.
9 ASTM text content (LIS2 - A2)

o Valid = the calibration was successful.

o Invalid = the calibration was unsuccessful.
9 14 Complex R Na Data Alarm: Na test data alarm.
u For details, see ISE data alarms (194).
10 14 Complex R K Data Alarm: K test data alarm.
u For details, see ISE data alarms (194).
11 14 Complex R Cl Data Alarm: Cl test data alarm.
u For details, see ISE data alarms (194).
12 14 Complex R Na Data: Na test calibration analytical data.
u For details, see ISE calibration analytical data (195).
13 14 Complex R K Data: K test calibration analytical data.
u For details, see ISE calibration analytical data (195).
14 14 Complex R Cl Data: Cl test calibration analytical data.
u For details, see ISE calibration analytical data (195).
y ISE Calibration Result Record - M(ICR)

ISE data alarms

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

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 ISE Calibration Result Record - M(ICR) 195

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

9 ASTM text content (LIS2 - A2)

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.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 196 ISE Calibration Result Record - M(ICR)

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
9 ASTM text content (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 E-module (immunology) Calibration Result Record - M(ECR) 197

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 string identifying the analyte.
^^^TestCode
The TestCode is a String type, max. length 5.
6 14 String R 24 Calibration method. Permitted values:
o NoCalibration
o LotCalibration
o ContainerCalibration
o InheritedLotCalibration
o InheritedItemCalibration

9 ASTM text content (LIS2 - A2)

o UserModifiedCalibration
o UnmaskedCalibration
o FailedCalibration
7 14 String O 20 ID of the analytical unit (module) the test belongs to.
u For details, see Identifier of the analytical unit sent to
host (108).
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
y E-module (immunology) Calibration Result Record - M(ECR)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 198 E-module (immunology) Calibration Result Record - M(ECR)

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
>^<Signal2Level2>
9 ASTM text content (LIS2 - A2)

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).
y E-module (immunology) Calibration Result Record - M(ECR)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Message Termination Record 199

Message Termination Record

The data manager uses 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.
y Message termination record

9 ASTM text content (LIS2 - A2)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 200
9 ASTM text content (LIS2 - A2) Message Termination Record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 201
Table of contents

ASTM communication examples 10

This chapter presents some examples of ASTM messages

generated by cobas® 8000 data manager, and a
connected host system (LIS / WAM). These examples
show the precise content of the messages sent, including
the control characters.

In this chapter 10
Low level trace file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Test selection inquiry from data manager . . . . . . . . . . 204
Routine test selection inquiry and download . . . . 204

10 ASTM communication examples

STAT sample test selection inquiry and
download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Test selection inquiry and download if no sample
found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Test selection inquiry with sequence number . . . 205
Regular test patient result upload messages . . . . . . . 207
Realtime ISE result upload . . . . . . . . . . . . . . . . . . . 207
ISE result upload - sample short . . . . . . . . . . . . . . 207
C-module result upload with no flag . . . . . . . . . . . 208
C-module result with alarm flag . . . . . . . . . . . . . . . 208
Batch upload of current results . . . . . . . . . . . . . . . 208
Batch upload of current results - sample short . . 209
Batch upload all previous results . . . . . . . . . . . . . . 209
Result below normal range . . . . . . . . . . . . . . . . . . . 210
Result below level of detection . . . . . . . . . . . . . . . . 210
Result with sample identified by sequence
number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
e 602 result with data point values . . . . . . . . . . . . 211
e 801 result message including raw data . . . . . . . 212
e 801 result message with raw data and data
points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
cobas e flow test result upload messages. . . . . . . . . 214
Result for sample with multiple
cobas e flow tests and embedded tests. . . . . . . . 214

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 202
Table of contents

Result for cobas e flow test with raw data, non-

reported embedded tests and generated
subresult . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
cobas e flow test with qualitative and
quantitative result . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
cobas e flow test calculated QC upload. . . . . . . . 218
Quality control uploads . . . . . . . . . . . . . . . . . . . . . . . . . 219
Realtime quality control upload . . . . . . . . . . . . . . . 219
Realtime quality control upload with a standby
bottle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Batch quality control upload . . . . . . . . . . . . . . . . . . 220
Batch quality control upload with a standby
bottle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Calibration result uploads . . . . . . . . . . . . . . . . . . . . . . . 221
C-module calibration result upload . . . . . . . . . . . . 221
ISE-module calibration result upload. . . . . . . . . . . 221
E-module calibration result upload . . . . . . . . . . . . 221
Result request from host and the data manager
result upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Request for currently active results . . . . . . . . . . . . 223
Request for all results . . . . . . . . . . . . . . . . . . . . . . . 224
Result request but no results or sample not
found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Result request with a sequence number. . . . . . . . 225
Result request with an expired sample . . . . . . . . . 225
Order query from the host. . . . . . . . . . . . . . . . . . . . . . . 227
Order query for all tests . . . . . . . . . . . . . . . . . . . . . . 227
10 ASTM communication examples

Order query for all open tests . . . . . . . . . . . . . . . . . 227

Order query but no open tests . . . . . . . . . . . . . . . . 228
Order query but sample not found. . . . . . . . . . . . . 228
Order query with sample identified by sequence
number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Low level trace file 203

Low level trace file

This section shows a low-level ASTM trace file, showing
the control characters, the acknowledgment 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.06|||||host|RS
UPL|P|1|20171020184623|[CR]P|1||||^||||[CR]O|1|
10002|0^10002^2^^S4^SC^not|^^^870^1\^^^880^1\^^
^890^1|R|20171016120539|20171016120539||||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|201612
18164600|20171016120550|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|20161
218164600|20171016120552|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||20171016120552|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]

10 ASTM communication examples

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
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 204 Test selection inquiry from data manager

Test selection inquiry from data manager

This section shows examples of ASTM test selection
inquiries sent from the data manager, and the host’s test
selection downloads in reply.

In this section
Routine test selection inquiry and download (204)
STAT sample test selection inquiry and download (204)
Test selection inquiry and download if no sample
found (205)
Test selection inquiry with sequence number (205)

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.06|||||host|TSREQ|P|1|20171020091706|
Q|1|^^321070^0^50094^2^^S1^SC^R1||ALL|||||||R|O|
L|1|N|

Host:
10 ASTM communication examples

H|\^&|||host^|||||cobas 8000^1.06|TSDWN|P|1|20171020091707
P|1||PatID1||Doe^John||19651125|M
O|1|321070|0^50094^2^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|R||||||A||||1||||||||||O
C|1|L|^^^^|G
L|1|N

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|\^&|15220||cobas 8000^1.06|||||host|TSREQ|P|1|20171020091706|
Q|1|^^321070^0^50094^2^^S1^SC^R1||ALL|||||||S|O|
L|1|N|

Host:
H|\^&|||host^|||||cobas 8000^1.06|TSDWN|P|1|20171020091707
P|1||PatID1||Doe^John||19651125|M
O|1|321070|0^50094^2^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|S||||||A||||1||||||||||O
C|1|L|^^^^|G
L|1|N

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Test selection inquiry from data manager 205

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.06|||||host|TSREQ|P|1|20171020091706|
Q|1|^^321070^0^50094^2^^S1^SC^R1||ALL|||||||R|O|
L|1|N|

Host:
H|\^&|||host^|||||cobas 8000^1.06|TSDWN|P|1|20171020091707
P|1||PatID1||Doe^John||19651125|M
O|1|321070|0^50094^2^^S1^SC^not|R||||||A||||1||||||||||O
C|1|L|^^^^|G
L|1|N

! CAUTION
Send patient demographic data if sample found with
no tests ordered
r Take care in the situation where the data manager
sends a test selection query, but the 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

10 ASTM communication examples

sends no patient demographic information, the data
manager might lose its current patient demographic
data.
r In this case, the host should send a normal test
selection download, with full patient information, and
comments etc., but no testcodes.
u For examples of normal test selections, see Routine test
selection inquiry and download (204) and STAT sample
test selection inquiry and download (204).

Test selection inquiry with sequence number

This section shows an example of an ASTM test selection
inquiry for a sample, identified by sequence number. (See
fields O-3.4 and O-4.1.) This functionality was introduced
in version 1.02.03.

DM:
H|\^&|15220||cobas 8000^1.06|||||host|TSREQ|P|1|20171020091706|
Q|1|^^^1013^50094^2^^S1^SC^R1||ALL|||||||R|O|
L|1|N|

Host:

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 206 Test selection inquiry from data manager

H|\^&|||host^|||||cobas 8000^1.06|TSDWN|P|1|20171020091707
P|1||PatID1||Doe^John||19651125|M
O|1||1013^50094^2^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|R||||||A||||1||||||||||O
C|1|L|^^^^|G
L|1|N
10 ASTM communication examples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Regular test patient result upload messages 207

Regular test patient result upload

messages
This section shows examples of ASTM patient result
upload messages.

In this section
Realtime ISE result upload (207)
ISE result upload - sample short (207)
C-module result upload with no flag (208)
C-module result with alarm flag (208)
Batch upload of current results (208)
Batch upload of current results - sample short (209)
Batch upload all previous results (209)
Result below normal range (210)
Result below level of detection (210)
Result with sample identified by sequence number (210)
e 602 result with data point values (211)
e 801 result message including raw data (212)
e 801 result message with raw data and data points (212)

Realtime ISE result upload

10 ASTM communication examples

This section shows an example of an ASTM realtime
result upload from an ISE module.

H|\^&|12927||cobas 8000^1.06|||||host|RSUPL|P|1|20171018185138|
P|1||||^||||
O|1|321088|0^50022^5^^S1^SC^not|^^^990^1|R|20171016183237|20171016183237||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^990/1/not|0.68|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171018185121|2017101818513
6|ISE^2^MU1#ISE#1#2^4^128|
C|1|I||I|
L|1|N|

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.06|||||host|RSUPL|P|1|20171018183109|
P|1||||^||||
O|1|321042|0^50011^4^^S1^SC^not|^^^991^1|R|20171014115322|20171006162241||||N||||1||||||||||F|
C|1|I|^^^^|G|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 208 Regular test patient result upload messages

R|1|^^^991/1/not||mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20171018183051|20171018183106|IS
E^1^MU1#ISE#1#1^3^126|
C|1|I|3^Sample short|I|
L|1|N|

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.06|||||host|RSUPL|P|1|20171019100042|
P|1||||^||||
O|1|321042|0^50011^4^^S1^SC^not|^^^8717^1|R|20171019094904|20171019094904||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8717/1/not|4.28|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171019095027|201710191000
40|c701^1^MU1#c701#1#1^6^77|
C|1|I|0|I|
L|1|N|

C-module 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.06|||||host|RSUPL|P|1|20171019092637|
10 ASTM communication examples

P|1||||^||||
O|1|321057|0^50007^1^^S1^SC^not|^^^8717^1|R|20171019085027|20171019085027||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8717/1/not|-0.01|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171019091622|20171019092
635|c701^1^MU1#c701#1#1^6^77|
C|1|I|27^PANIC value over (lower) Technical Limit|I|
L|1|N|

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.06|||||host|RSUPL^BATCH|P|1|20171020095834|
P|1||PatID1||Doe^John||19651125|M|
O|1|321015|0^50071^1^^S1^SC^not|^^^990^1\^^^991^1\^^^8717^1|R|20171019174209|20171019174209||||N||||
1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^990/1/not|0.75|mmol/L|^TECH\^NORM\^CRIT\<^USER|||F||bmserv^SYSTEM|20171020095735|201710200957
51|ISE^1^MU1#ISE#1#1^3^125|
R|2|^^^991/1/not|297.28|mmol/L|^TECH\^NORM\^CRIT\<^USER|||F||bmserv^SYSTEM|20171020095735|2017102009
5751|ISE^1^MU1#ISE#1#1^3^126|
R|3|^^^8717/Inc/not|-0.02|mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20171019175614|201710191
80627|c701^1^MU1#c701#1#1^6^77|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Regular test patient result upload messages 209

L|1|N|

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.06|||||host|RSUPL^BATCH|P|1|20171018182329|
P|1||PatID1||Doe^John||19651125|M|
O|1|321042|0^50011^4^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|R|20171014115322|20171006162241||||N||||1
||||||||||F|
C|1|I|^^^^|G|
R|1|^^^989/1/not| |mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20171018173814|2017101817
3829|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|20171018173814|2017101817
3829|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|20171018173814|2017101817
3829|ISE^1^MU1#ISE#1#1^3^126|
C|1|I|3^Sample short|I|

Batch upload all previous results

10 ASTM communication examples

This section shows an example of an ASTM batch upload
of all previous results.

H|\^&|15325||cobas 8000^1.06|||||host|RSUPL^BATCH|P|1|20171020095830|
P|1||PatID1||Doe^John||19651125|M|
O|1|321015|0^50071^1^^S1^SC^not|^^^990^1\^^^991^1\^^^8717^1|R|20171019174209|20171019174209||||N||||
1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^990/1/not|0.91|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20171019174423|2017101917
4439|ISE^2^MU1#ISE#1#2^4^128|
C|1|I|23^ISE Sample range over|I|
R|2|^^^990/1/not|0.75|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20171020095735|2017102009
5751|ISE^1^MU1#ISE#1#1^3^125|
C|1|I|0|I|
R|3|^^^991/1/not|252.89|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20171019174347|20171019
174403|ISE^1^MU1#ISE#1#1^3^126|
C|1|I|23^ISE Sample range over|I|
R|4|^^^991/1/not|297.28|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20171020095735|20171020
095751|ISE^1^MU1#ISE#1#1^3^126|
C|1|I|0|I|
R|5|^^^8717/1/not|-0.04|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171019174533|20171019175
547|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|20171019175614|2017101918
0627|c701^1^MU1#c701#1#1^6^77|
C|1|I|0|I|
L|1|N|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 210 Regular test patient result upload messages

Result below normal range

This section shows an example of an ASTM result upload
below the normal reference range.

H|\^&|10252||cobas|^|8000^1.06|||||host|RSUPL|P|1|20170610200938|
P|1||PatID1||Doe^John||19651125|M|
O|1|123|0^50063^2^^S1^SC^not|^^^989^1\^^^991^1\^^^8717^1|R|20170604235148|20170604235148||||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|20170621084348|201706
21084404|ISE^1^MU1#ISE#1#1^3^28|
C|1|I|0|I|
L|1|N|

Result below level of detection

This section shows an example of an ASTM result upload
below the EP17-A level of detection.

H|\^&|10256||cobas|^|8000^1.06|||||host|RSUPL|P|1|20170610201014|
P|1||PatID1||Doe^John||19651125|M|
O|1|123|0^50063^2^^S1^SC^not|^^^989^1\^^^991^1\^^^8717^1|R|20170604235148|20170604235148||||N||||1||
||||||||F|
C|1|I|^^^^|G|
R|1|^^^989/1/not|0.1|mmol/L|^TECH\9 - 144^NORM\^CRIT\^USER|HU||F||bmserv^SYSTEM|20170621084348|20170
621084404|ISE^1^MU1#ISE#1#1^3^28|
10 ASTM communication examples

C|1|I|0|I|
R|2|^^^991/1/not|1.1|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20170621084348|20170621084404
|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|20170621085921|20170621090
935|c701^2^MU1#c701#1#2^7^168|
C|1|I|0|I|
L|1|N|

Result with sample identified by sequence number

This section shows an example of an ASTM result upload
with the sample identified by sequence number. (See field
O-4.1.) This functionality was introduced in version
1.02.03.

H|\^&|563030||cobas 8000^1.06|||||host|RSUPL|P|1|20170720152309|
P|1||PatID1||Doe^John||19651125|M|
O|1||1013^50101^3^^S1^SC^not|^^^8413^1\^^^8571^1\^^^8706^1|R|20170715093311|20170715093311||||N||||1
||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8413/1/not|15|g/dL|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20170715084600|20170715084600|c
702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Regular test patient result upload messages 211

R|2|^^^8571/1/not|16|U/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20170715084600|20170715084600|c7
02^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|20170715084600|20170715084600
|c702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|
L|1|N|

e 602 result with data point values

This section shows an example of an ASTM patient result
message with data point values, generated by an e 602
module.

The control unit sends data point values to the data

manager only when they are explicitly requested by the
user (for example, for troubleshooting or research
purposes).
u This example shows only the EFS portion of the
message. For a complete example, see e 801 result
message with raw data and data points (212).

H|\^&|10045||cobas 8000^1.06|||||host|RSUPL|P|1|20180110140317|
P|1||PatID1||Doe^John||19651125|M|
O|1|100751|0^50251^1^^S1^SC^not|^^^224^1|R|20180105144921|20180105144921||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^224/1/not|589.0|pg/mL|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20180105150233|2018010515301

10 ASTM communication examples

1|e602^2^MU1#e602#3#2^10^0|
C|1|I|0|I|
R|2|^^^224/1/not|86933^8958\8980\8987\8998\9071\9016\9007\9011\9033\9008\8999\8984\9014\8982\8989\90
07\9019\9008\9057\9051\9077\9085\9101\9100\9112\9095\9132\9104\9108\9092\9142\9141\9158\9133\9142\91
62\9145\9157\9195\9219\9224\9234\9262\9276\9298\9353\9356\9355\9382\9464\9489\9493\9471\9498\9474\95
13\9517\9482\9459\9423\9404\9410\9457\9447\9391\9470\9527\9474\9454\9449\9425\9442\9473\9429\9515\95
44\9588\9550\9553\9548\10387\35844\38096\38544\38570\38517\38388\38270\38194\38114\37969\37816\37757
\37673\37503\37448\37346\37315\37191\37162\36979\37013\36937\36819\36768\36692\36643\36514\36547\364
65\36342\36323\36235\36210\36211\36146\36034\35968\35946\35908\35891\35780\35759\35768\35634\35673\3
5634\35555\35529\35452\35385\35352\35280\35323\35248\35197\35088\35155\35066\34994\34982\34925\34978
\34859\34816\34783\34789\34764\34689\34592\34658\34595\34556\34621\34525\34401\34388\34383\34364\344
01\34322\34272\34414\34147\34109\34005\34207\34102\34071\34085\34003\33915\34025\33967\33806\33835\3
3814\33756\33752\33710\33700\33689\33635\33583\33682\33503\33524\33456\33338\33369\33348\33368\33233
\33231\33131\33254\33101\33189\33224\33259|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20180105
150233|20180105153011|e602^2^MU1#e602#3#2^10^EFS|
C|1|I|0|I|
L|1|N|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 212 Regular test patient result upload messages

e 801 result message including raw data

This section shows an example message that includes
four raw data values: Effective-Signal (EFS), Effective-
Voltage (EFV), Effective-Current (EFC) and PMT Spike
(PMT). The sequence number (field R-2) increments with
every new result record.

H|\^&|23690||cobas 8000^1.06|||||host|RSUPL|P|1|20180110141506|
P|1||PatID1||Doe^John||19651125|M|
O|1|200404|0^50691^5^^S1^^not|^^^10100^1|R|20180110104238|20180110104238||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^10100/1/not|34.8|pg/mL|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20180110104543|201801101104
15|e801^2^MU1#e801#2#2^10^3502|
C|1|I|0|I|
R|2|^^^10100/1/not|103638.9|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20180110104543|20180110
110415|e801^2^MU1#e801#2#2^10^EFS|
C|1|I|0|I|
R|3|^^^10100/1/not|-117.322|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20180110104543|20180110
110415|e801^2^MU1#e801#2#2^10^EFV|
C|1|I|0|I|
R|4|^^^10100/1/not|234.8504|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20180110104543|20180110
110415|e801^2^MU1#e801#2#2^10^EFC|
C|1|I|0|I|
R|5|^^^10100/1/not|13049.00|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20180110104543|20180110
110415|e801^2^MU1#e801#2#2^10^PMT|
C|1|I|0|I|
L|1|N|
10 ASTM communication examples

e 801 result message with raw data and data points

This section shows an example e 801 result message with
data point values and four raw data records: Effective-
Signal (EFS), Effective-Voltage (EFV), Effective-Current
(EFC) and PMT Spike (PMT). The sequence number (field
R-2) increments with every new result record.

H|\^&|23721||cobas 8000^1.06|||||host|RSUPL|P|1|20180110142407|
P|1||PatID1||Doe^John||19651125|M|
O|1|200404|0^50691^5^^S1^^not|^^^10100^1|R|20180110104238|20180110104238||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^10100/1/not|34.8|pg/mL|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20180110104543|201801101104
15|e801^2^MU1#e801#2#2^10^3502|
C|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Regular test patient result upload messages 213

R|2|^^^10100/1/not|103638.9^12110\11391\12279\11164\11765\11422\12207\12726\12111\11769\12096\11858\
12113\12858\10750\10923\11599\12065\12619\11702\12461\12165\11325\12302\12001\10736\11883\11947\1226
5\11933\11891\12389\12790\12249\10997\10500\12055\12060\11249\11137\10631\11481\11132\11246\10966\11
582\12046\12247\12251\13049\10945\12561\11937\12715\11401\10757\12152\12827\12733\12555\12261\12915\
12629\12138\12860\12689\12726\11982\11782\12021\12520\12176\11118\11049\11733\12394\10473\11566\1162
9\12306\29150\40499\41308\41400\41272\41116\40932\40758\40539\40300\40110\39989\39895\39687\39489\39
384\39209\39176\38938\38848\38674\38570\38457\38414\38334\38199\38044\38044\37857\37693\37612\37623\
37568\37462\37348\37191\37192\37079\36987\36942\36772\36777\36777\36613\36532\36518\36490\36418\3634
0\36303\36278\36100\36065\35994\35915\35763\35773\35770\35707\35685\35576\35544\35473\35486\35426\35
290\35273\35267\35275\35159\35105\34962\35009\34911\34822\34847\34625\34799\34664\34603\34524\34542\
34440\34414\34289\34455\34340\34217\34334\34205\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|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20180110104543|20180110110415|e801^2^MU1#e8
01#2#2^10^EFS|
C|1|I|0|I|
R|3|^^^10100/1/not|-117.322^33390\33390\33388\33388\33387\33390\33387\33385\33387\33387\33385\33386\
33385\33384\33384\33382\33384\33383\33384\33380\33383\33381\33382\33380\33379\33380\33379\33379\3337
8\33380\33379\33379\33378\33378\33379\33377\33377\33377\33377\33378\33376\33376\33376\33374\33375\33
374\33375\33375\33374\33374\33373\33374\33372\33374\33373\33373\33372\33373\33373\33372\33368\33369\
33371\33369\33369\33369\33368\33369\33367\33367\33368\33367\33368\33367\33369\33365\33366\33364\3336
8\33367\26668\25718\25711\25707\25704\25699\25696\25693\25686\25682\25678\25671\25663\25662\25656\25
651\25644\25641\25634\25632\25625\25619\25615\25610\25607\25600\25596\25592\25587\25584\25579\25570\
25567\25565\25558\25553\25549\25546\25539\25535\25529\25523\25519\25515\25508\25506\25501\25495\2549
0\25488\25485\25478\25475\25471\25467\25464\25460\25456\25453\25451\25445\25448\25441\25438\25436\25
431\25431\25427\25432\25437\25441\25446\25448\25457\25469\25479\25487\25490\25490\25495\25495\25494\
25497\25495\25493\25491\25485\25483\25480\25474\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|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20180110104543|20180110110415|e801^2^MU1#e8
01#2#2^10^EFV|
C|1|I|0|I|
R|4|^^^10100/1/not|234.8504^31417\31414\31413\31415\31414\31414\31414\31413\31414\31412\31412\31413\
31413\31414\31412\31412\31412\31411\31410\31409\31411\31409\31409\31408\31409\31409\31408\31408\3140
7\31406\31407\31406\31405\31406\31406\31403\31403\31405\31405\31406\31404\31404\31404\31403\31403\31

10 ASTM communication examples

404\31402\31402\31403\31403\31402\31401\31399\31400\31402\31400\31401\31398\31401\31399\31400\31397\
31401\31399\31400\31399\31399\31399\31395\31398\31398\31396\31399\31396\31397\31397\31397\31396\3139
5\31398\1481\3106\7024\9210\10778\12019\13059\13959\14751\15431\15997\16448\16821\17141\17420\17668\
17895\18104\18293\18470\18630\18783\18924\19059\19183\19303\19415\19521\19621\19720\19810\19898\1998
4\20063\20139\20214\20283\20349\20413\20478\20539\20597\20652\20706\20759\20808\20861\20910\20957\21
007\21052\21098\21148\21189\21233\21279\21321\21365\21407\21452\21495\21538\21583\21621\21664\21688\
21685\21648\21618\21613\21627\21640\21643\21643\21661\21694\21737\21784\21830\21884\21936\21986\2203
9\22077\22102\22117\22130\22144\22156\22170\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|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20180110104543|20180110110415|e801^2^MU1#e801#2
#2^10^EFC|
C|1|I|0|I|
R|5|^^^10100/1/not|13049.00|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20180110104543|20180110
110415|e801^2^MU1#e801#2#2^10^PMT|
C|1|I|0|I|
L|1|N|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 214 cobas e flow test result upload messages

cobas e flow test result upload messages

This section shows examples of ASTM patient result
upload messages.

In this section
Result for sample with multiple cobas e flow tests and
embedded tests (214)
Result for cobas e flow test with raw data, non-reported
embedded tests and generated subresult (216)
cobas e flow test with qualitative and quantitative
result (217)
cobas e flow test calculated QC upload (218)

Result for sample with multiple cobas e flow tests and

embedded tests
This section shows the result of a test with 2
cobas e flow tests. An R record is created for every
cobas e flow test, and an R record is created for every
embedded test (and its raw data) within the
cobas e flow test. In this example, a custom host code
configuration has been used.
10 ASTM communication examples

H|\^&|22417||cobas 8000^1.06|||||host|RSUPL|P|1|20171219094825|
P|1||||^||||
O|1|101801|0^50461^1^^S1^^not|^^^32000^1\^^^22001^1|R|20171201160409|20171201160409||||N||||1|||||||
|||F|
C|1|I|^^^^|G|
R|1|^^^32000/1/not|-1^ ||^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162536|DM^0^DM#DM#0#0^0
^|
C|1|I|0|I|
R|2|^^^32000/1/not^^HIVDuo_01/1|-1^0.203|COI|^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162536|DM
^0^DM#DM#0#0^0^|
C|1|I|0|I|
R|3|^^^32000/1/not^^HIVAG_01/1|-1^0.185|COI|^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162536|DM^
0^DM#DM#0#0^0^|
C|1|I|0|I|
R|4|^^^32000/1/not^^AHIV_01/1|-1^0.0827|COI|^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162536|DM^
0^DM#DM#0#0^0^|
C|1|I|0|I|
R|5|^^^32000/1/not^^11014/1| ^ |COI|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|201712011
60704|20171201162536|e801^2^MU1#e801#2#2^10^3289|
C|1|I|0|I|
R|6|^^^32000/1/not^^11014/1|626.0948|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201160704
|20171201162536|e801^2^MU1#e801#2#2^10^EFS|
C|1|I|0|I|
R|7|^^^32000/1/not^^11014/1|-116.017|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201160704
|20171201162536|e801^2^MU1#e801#2#2^10^EFV|
C|1|I|0|I|
R|8|^^^32000/1/not^^11014/1|221.6544|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201160704
|20171201162536|e801^2^MU1#e801#2#2^10^EFC|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 215

C|1|I|0|I|
R|9|^^^32000/1/not^^11014/1|13658.00|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201160704
|20171201162536|e801^2^MU1#e801#2#2^10^PMT|
C|1|I|0|I|
R|10|^^^32000/1/not^^11013/1| ^ |COI|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201
160652|20171201162524|e801^1^MU1#e801#2#1^9^3286|
C|1|I|0|I|
R|11|^^^32000/1/not^^11013/1|695.0912|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116065
2|20171201162524|e801^1^MU1#e801#2#1^9^EFS|
C|1|I|0|I|
R|12|^^^32000/1/not^^11013/1|-115.852|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116065
2|20171201162524|e801^1^MU1#e801#2#1^9^EFV|
C|1|I|0|I|
R|13|^^^32000/1/not^^11013/1|224.0052|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116065
2|20171201162524|e801^1^MU1#e801#2#1^9^EFC|
C|1|I|0|I|
R|14|^^^32000/1/not^^11013/1|11456.00|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116065
2|20171201162524|e801^1^MU1#e801#2#1^9^PMT|
C|1|I|0|I|
R|15|^^^32000/1/not^^22000/1/3| ^ |COI|^TECH\^NORM\^CRIT\^USER|||B||^SYSTEM|201712011606
52|20171201162536|e801^0^MU1#e801#2#0^8^|
C|1|I|0|I|
R|16|^^^32000/1/not^^22000/1/3| ^ |COI|^TECH\^NORM\^CRIT\^USER|||B||^SYSTEM|201712011606
52|20171201162536|e801^0^MU1#e801#2#0^8^|
C|1|I|0|I|
R|17|^^^22001/1/not|15^73.7|%|^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162612|DM^0^DM#DM#0#0^0^
|
C|1|I|0|I|
R|18|^^^22001/1/not^^11150/1|1^117|U/mL|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201160716|20
171201162548|e801^1^MU1#e801#2#1^9^3314|
C|1|I|0|I|

10 ASTM communication examples

R|19|^^^22001/1/not^^11150/1|479194.3|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116071
6|20171201162548|e801^1^MU1#e801#2#1^9^EFS|
C|1|I|0|I|
R|20|^^^22001/1/not^^11150/1|-115.873|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116071
6|20171201162548|e801^1^MU1#e801#2#1^9^EFV|
C|1|I|0|I|
R|21|^^^22001/1/not^^11150/1|224.3268|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116071
6|20171201162548|e801^1^MU1#e801#2#1^9^EFC|
C|1|I|0|I|
R|22|^^^22001/1/not^^11150/1|11668.00|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116071
6|20171201162548|e801^1^MU1#e801#2#1^9^PMT|
C|1|I|0|I|
R|23|^^^22001/1/not^^11151/1| ^ |U/mL|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120
1160728|20171201162612|e801^1^MU1#e801#2#1^9^3314|
C|1|I|0|I|
R|24|^^^22001/1/not^^11151/1|171198.9|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116072
8|20171201162612|e801^1^MU1#e801#2#1^9^EFS|
C|1|I|0|I|
R|25|^^^22001/1/not^^11151/1|-115.907|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116072
8|20171201162612|e801^1^MU1#e801#2#1^9^EFV|
C|1|I|0|I|
R|26|^^^22001/1/not^^11151/1|224.4484|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116072
8|20171201162612|e801^1^MU1#e801#2#1^9^EFC|
C|1|I|0|I|
R|27|^^^22001/1/not^^11151/1|11031.00|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116072
8|20171201162612|e801^1^MU1#e801#2#1^9^PMT|
C|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 216 cobas e flow test result upload messages

R|28|^^^22001/1/not^^22001/1/5| ^ |%|^TECH\^NORM\^CRIT\^USER|||B||^SYSTEM|20171201160716
|20171201162612|e801^0^MU1#e801#2#0^8^|
C|1|I|0|I|
L|1|N|

Result for cobas e flow test with raw data, non-reported

embedded tests and generated subresult
Embedded tests which are marked as non-reported in the
data manager software are sent to the host in the same
manner as any other test. However, no result value is sent
for non-reported tests. Instead of a result, the omitted
result value configured on the Host reporting tab is sent.

Moreover, a cobas e flow test result can contain a

generated subresult in the embedded tests. This section
shows an example of a result message with a generated
subresult as part of the subresults. The name of the
generated subresult is sent instead of the test code. The
host code for each generated subresult can be
overwritten with a custom value, defined in the data
manager software.
u Assigning host codes to cobas e flow test results and
generated subresults (116)
10 ASTM communication examples

H|\^&|22417||cobas 8000^1.06|||||host|RSUPL|P|1|20171219094825|
P|1||||^||||
O|1|101801|0^50461^1^^S1^^not|^^^32000^1|R|20171201160409|20171201160409||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^32000/1/not|-1^ ||^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162536|DM^0^DM#DM#0#0^0
^|
C|1|I|0|I|
R|2|^^^32000/1/not^^HIVDuo_01/1|-1^0.203|COI|^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162536|DM
^0^DM#DM#0#0^0^|
C|1|I|0|I|
R|3|^^^32000/1/not^^HIVAG_01/1|-1^0.185|COI|^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162536|DM^
0^DM#DM#0#0^0^|
C|1|I|0|I|
R|4|^^^32000/1/not^^AHIV_01/1|-1^0.0827|COI|^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162536|DM^
0^DM#DM#0#0^0^|
C|1|I|0|I|
R|5|^^^32000/1/not^^11014/1| ^ |COI|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|201712011
60704|20171201162536|e801^2^MU1#e801#2#2^10^3289|
C|1|I|0|I|
R|6|^^^32000/1/not^^11014/1|626.0948|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201160704
|20171201162536|e801^2^MU1#e801#2#2^10^EFS|
C|1|I|0|I|
R|7|^^^32000/1/not^^11014/1|-116.017|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201160704
|20171201162536|e801^2^MU1#e801#2#2^10^EFV|
C|1|I|0|I|
R|8|^^^32000/1/not^^11014/1|221.6544|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201160704
|20171201162536|e801^2^MU1#e801#2#2^10^EFC|
C|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 217

R|9|^^^32000/1/not^^11014/1|13658.00|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201160704
|20171201162536|e801^2^MU1#e801#2#2^10^PMT|
C|1|I|0|I|
R|10|^^^32000/1/not^^11013/1| ^ |COI|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201
160652|20171201162524|e801^1^MU1#e801#2#1^9^3286|
C|1|I|0|I|
R|11|^^^32000/1/not^^11013/1|695.0912|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116065
2|20171201162524|e801^1^MU1#e801#2#1^9^EFS|
C|1|I|0|I|
R|12|^^^32000/1/not^^11013/1|-115.852|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116065
2|20171201162524|e801^1^MU1#e801#2#1^9^EFV|
C|1|I|0|I|
R|13|^^^32000/1/not^^11013/1|119.6544|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116065
2|20171201162524|e801^1^MU1#e801#2#1^9^EFC|
C|1|I|0|I|
R|14|^^^32000/1/not^^11013/1|789.6589|count|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|2017120116065
2|20171201162524|e801^1^MU1#e801#2#1^9^PMT|
C|1|I|0|I|

cobas e flow test with qualitative and quantitative result

When the main result of a cobas e flow test is a
qualitative and quantitative result, the unit of the result is
set to the cobas e flow test measurement unit. The main
result in this example is a qualitative code with the value
of 15, which is mapped to the result message “Avidity
high”. In addition, the result has the numeric value 73.7%.

10 ASTM communication examples

In this example, neither raw data nor linkage records are
sent to the host. For the cobas e flow test and for the
embedded test 11150, Test result type for host
reporting is set to Qualitative^quantitative.
u Assigning result type for cobas e flow test result
upload (115)

H|\^&|22417||cobas 8000^1.06|||||host|RSUPL|P|1|20171219094825|
P|1||||^||||
O|1|101801|0^50461^1^^S1^^not|^^^12001^1|R|20171201160409|20171201160409||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^12001/1/not|15^73.7|%|^TECH\^NORM\^CRIT\^USER|||F||^SYSTEM||20171201162612|DM^0^DM#DM#0#0^0^|
C|1|I|0|I|
R|2|^^^12001/1/not^^11150/1|1^117|U/mL|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201160716|201
71201162548|e801^1^MU1#e801#2#1^9^3314|
C|1|I|0|I|
R|3|^^^12001/1/not^^11151/1| ^ |U/mL|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171201160728|20171
201162612|e801^1^MU1#e801#2#1^9^3314|
C|1|I|0|I|
L|1|N|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 218 cobas e flow test result upload messages

cobas e flow test calculated QC upload

This section shows a calculated QC result upload with the
following settings enabled:
• Send additional link information for calculated
QC
• Send single QC results for calculated QC
• Send raw data / data points to host

Additionally, Value for omitted results is set to 7

spaces.

H|\^&|22458||cobas 8000^1.06|||||host|RSUPL^REAL|P|1|20171219100800|
P|1|
O|1|PC CMVAV2^247001^10^20190131^10073|0^^^^QC^SC^not|^^^22001^1\^^^11151^1\^^^11150^1|R||||||Q||||1
||||||||||F|
C|1|I|^^^^|G|
R|1|^^^22001/1/not/6| ^87.9|%||||F||^SYSTEM|20171201155928|20171201161824|e801^0^MU1#e801#2#0^
8^^Current|
C|1|I|0|I|
R|2|^^^22001/1/not/^^11151/1/not| ^11.9|U/mL||||F||bmserv^SYSTEM|20171201155928|20171201161812
|e801^1^MU1#e801#2#1^9^3314^Current|
C|1|I|0|I|
R|3|^^^11151/1/not|38182.05|count||||F||bmserv^SYSTEM|20171201155928|20171201161812|e801^1^MU1#e801#
2#1^9^EFS^Current|
C|1|I|0|I|
R|4|^^^11151/1/not|-116.570|count||||F||bmserv^SYSTEM|20171201155928|20171201161812|e801^1^MU1#e801#
2#1^9^EFV^Current|
C|1|I|0|I|
10 ASTM communication examples

R|5|^^^11151/1/not|224.0380|count||||F||bmserv^SYSTEM|20171201155928|20171201161812|e801^1^MU1#e801#
2#1^9^EFC^Current|
C|1|I|0|I|
R|6|^^^11151/1/not|10751.00|count||||F||bmserv^SYSTEM|20171201155928|20171201161812|e801^1^MU1#e801#
2#1^9^PMT^Current|
C|1|I|0|I|
R|7|^^^22001/1/not/^^11150/1/not| ^25.7|U/mL||||F||bmserv^SYSTEM|20171201155952|20171201161824
|e801^2^MU1#e801#2#2^10^3315^Current|
C|1|I|0|I|
R|8|^^^11150/1/not|91028.27|count||||F||bmserv^SYSTEM|20171201155952|20171201161824|e801^2^MU1#e801#
2#2^10^EFS^Current|
C|1|I|0|I|
R|9|^^^11150/1/not|-117.072|count||||F||bmserv^SYSTEM|20171201155952|20171201161824|e801^2^MU1#e801#
2#2^10^EFV^Current|
C|1|I|0|I|
R|10|^^^11150/1/not|220.8340|count||||F||bmserv^SYSTEM|20171201155952|20171201161824|e801^2^MU1#e801
#2#2^10^EFC^Current|
C|1|I|0|I|
R|11|^^^11150/1/not|13188.00|count||||F||bmserv^SYSTEM|20171201155952|20171201161824|e801^2^MU1#e801
#2#2^10^PMT^Current|
C|1|I|0|I|
L|1|N|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Quality control uploads 219

Quality control uploads

This section shows examples of ASTM quality control
result uploads.

NOTICE
When manually resending QC results from the
control unit
r The data manager always uploads manually resent QC
results to the host using the By test upload mode,
regardless of which upload mode is selected on the
data manager and control unit.
u For more information about result upload modes, see
Result upload settings (140)

In this section
Realtime quality control upload (219)
Realtime quality control upload with a standby
bottle (219)
Batch quality control upload (220)
Batch quality control upload with a standby bottle (220)

Realtime quality control upload

10 ASTM communication examples

This section shows an example of an ASTM realtime
quality control upload.
u Messages transmitted by the data manager (164)

H|\^&|13772||cobas 8000^1.06|||||host|RSUPL^REAL|P|1|20170919094737|
P|1|
O|1|PNU^150403^2^20170831^27|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|20170919093722|20171019094737|c701^1^MU1#c701#1#1^6^75^
Current|
C|1|I|0|I|
L|1|N|

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.06|||||host|RSUPL^REAL|P|1|20170919094918|
P|1|
O|1|PNU^150403^2^20170831^27|0^30005^1^^QC^SC^not|^^^8685^1|R||||||Q||||1||||||||||F|
C|1|I|^^^^|G|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 220 Quality control uploads

R|1|^^^8685/1/not|44|U/L||||F||bmserv^SYSTEM|20170919093903|20170919094918|c701^1^MU1#c701#1#1^6^76^
Standby^1|
C|1|I|0|I|
L|1|N|

Batch quality control upload

This section shows an example of an ASTM batch quality
control upload.
u Messages transmitted by the data manager (164)

H|\^&|14262||cobas 8000^1.06|||||host|RSUPL^BATCH|P|1|20170919124105|
P|1|
O|1|PNU^150403^2^20170831^27|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|20170919111853|20170919112908|c701^1^MU1#c701#1#1^6^75^
Current|
C|1|I|0|I|
L|1|N|

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.
10 ASTM communication examples

H|\^&|14261||cobas 8000^1.06|||||host|RSUPL^BATCH|P|1|20170919124103|
P|1|
O|1|PNU^150403^2^20170831^27|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|20170919111857|20170919112911|c701^1^MU1#c701#1#1^6^76^
Standby^1|
C|1|I|0|I|
L|1|N|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Calibration result uploads 221

Calibration result uploads

This section shows examples of ASTM calibration result
uploads.

In this section
C-module calibration result upload (221)
ISE-module calibration result upload (221)
E-module calibration result upload (221)

C-module calibration result upload

This section shows an example of an ASTM c-module
calibration result upload.

H|\^&|14273||cobas 8000^1.06|||||host|PCUPL^REAL|P|1|20171019091421|
M|1|PCR|bmserv|^^^8685|MU1#c701#1#1|16|0|22851^4^22866^2^0^\24786^-361^24149^-362^0^\^^^^^\^^^^^\^^^
^^\^^^^^|
L|1|N|

ISE-module calibration result upload

This section shows an example of an ASTM ISE-module

10 ASTM communication examples

calibration result upload.

H|\^&|14274||cobas 8000^1.06|||||host|ICUPL^REAL|P|1|20171020110002|
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.6
4^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|

E-module calibration result upload

This section shows examples of ASTM e-module
calibration result uploads.

e 602 example
H|\^&|14276||cobas 8000^1.06|||||host|ECUPL^REAL|P|1|20171018175819|
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|||||20171018175819|
L|1|N|

e 801 example
H|\^&|143416||cobas 8000^1.06|||||host|ECUPL^REAL|P|1|20170414183058|
M|1|ECR|bmserv|^^^17001|LotCalibration|MU1#e801#1#2|243001||0|178191|O|I^O^\M^O^\S^O^\R^1.00^\D^O^\L
^^\F^O^\Y^O^\B^O^|25604^25982^^||||||

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 222 Calibration result uploads

M|2|ECR|bmserv|^^^17001|LotCalibration|MU1#e801#1#2|243001||0|178191|O|I^O^\M^O^\S^O^\R^1.00^\D^O^\L
^^\F^O^\Y^O^\B^O^|570^570^^|||||| L|1|N|
10 ASTM communication examples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Result request from host and the data manager result upload 223

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.

! CAUTION
Always give rack types if using sample lifetime
r If you set sample lifetime to a number greater than
zero, always send the rack type (“specimen type” or
“sample type”) with an order or result query.
Otherwise, the data manager does not reply.

In this section
Request for currently active results (223)
Request for all results (224)
Result request but no results or sample not found (224)
Result request with a sequence number (225)
Result request with an expired sample (225)

Request for currently active results

10 ASTM communication examples

This section shows an example ASTM result request from
the host for currently active results for a sample, and the
data manager’s result upload.
u For an explanation of the request information status
code (sent in Q-13), see Query Record (Request
Information Record) (189)

Host:
H|\^&|||host|||||cobas 8000^1.06|RSREQ|P|1|20171020075900|
Q|1|^S1^321015||||||||||F|
L|1|N|

DM:
H|\^&|15126||cobas 8000^1.06|||||host|RSUPL^BATCH|P|1|20171020090056|
P|1||PatID1||Doe^John||19651125|M|
O|1|321015|0^50071^1^^S1^SC^not|^^^8717^1|R|20171019174209|20171019174209||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8717/Inc/not|-0.02|mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20171019175614|201710191
80627|c701^1^MU1#c701#1#1^6^77|
C|1|I||I|
L|1|N|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 224 Result request from host and the data manager result upload

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|\^&|||host|||||cobas 8000^1.06|RSREQ|P|1|20171020075900|
Q|1|^S1^321015|||||||||||
L|1|N|

DM:
H|\^&|15123||cobas 8000^1.06|||||host|RSUPL^BATCH|P|1|20171020090031|
P|1||PatID1||Doe^John||19651125|M|
O|1|321015|0^50071^1^^S1^SC^not|^^^990^1\^^^991^1\^^^8717^1|R|20171019174209|20171019174209||||N||||
1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^990/1/not|0.91|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20171019174423|2017101917
4439|ISE^2^MU1#ISE#1#2^4^128|
C|1|I||I|
R|2|^^^990/1/not|0.70|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||C||bmserv^SYSTEM|20171019174459|2017101917
4515|ISE^1^MU1#ISE#1#1^3^125|
C|1|I||I|
R|3|^^^991/1/not|252.89|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||F||bmserv^SYSTEM|20171019174347|20171019
174403|ISE^1^MU1#ISE#1#1^3^126|
C|1|I||I|
R|4|^^^991/1/not|256.84|mmol/L|^TECH\^NORM\^CRIT\< 0^USER|||C||bmserv^SYSTEM|20171019174423|20171019
174439|ISE^2^MU1#ISE#1#2^4^129|
C|1|I||I|
R|5|^^^8717/1/not|-0.04|mmol/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171019174533|20171019175
10 ASTM communication examples

547|c701^1^MU1#c701#1#1^6^77|
C|1|I||I|
R|6|^^^8717/Inc/not|-0.02|mmol/L|^TECH\^NORM\^CRIT\^USER|||C||bmserv^SYSTEM|20171019175614|201710191
80627|c701^1^MU1#c701#1#1^6^77|
C|1|I||I|
L|1|N|

Result request but no results or sample not found

This section shows an example of an ASTM result request
from the host, where the data manager does not have any
results for or record of the sample.

Host:
H|\^&|||host|||||cobas 8000^1.06|RSREQ|P|1|20171020075900|
Q|1|^S1^321016|||||||||||
L|1|N|

DM:
<No Reply>

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Result request from host and the data manager result upload 225

Result request with a sequence number

This section shows an example of an ASTM result request
from the host, for the sample with sequence number
1031. (See fields Q-3.4 and O-4.1.) This functionality was
introduced in version 1.02.03.

Host:
H|\^&|||host|||||cobas 8000^1.06|RSREQ|P|1|20170711093355|
Q|1|^S1^^1031||||||||||F|
L|1|N|

DM:
H|\^&|564735||cobas 8000^1.06|||||host|RSUPL^BATCH|P|1|20170712112553|
P|1||PatID1||Doe^John||19651125|M|
O|1||1031^50101^3^^S1^SC^not|^^^8413^1\^^^8571^1\^^^8706^1|R|20170711093311|20170711093311||||N||||1
||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8413/1/not|15|g/dL|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171212104600|20171212104600|c
702^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|20171212104600|20171212104600|c7
02^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|20171212104600|20171212104600
|c702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|
L|1|N|

10 ASTM communication examples

Result request with an expired sample
If your site uses sample lifetime, there may be an expired
sample in the data manager database that has the same
sample ID as a current sample. Normally this will not
cause any confusion. If you send a result request, the
data manager only sends a test result message for a
unique current sample.

Host:
H|\^&|||host|||||cobas 8000^1.06|RSREQ|P|1|20171018135001|
Q|1|^S1^321071||||||||||F|
L|1|N|

DM:
H|\^&|563358||cobas 8000^1.06|||||host|RSUPL^BATCH|P|1|20171018135137|
P|1||||^||||
O|1|321071|0^54312^2^^S1^SC^not|^^^8413^1\^^^8571^1|R|20171018134635|20171018134635||||N||||1|||||||
|||F|
C|1|I|^^^^|G|
R|1|^^^8413/1/not|12.08|g/dL|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171017151615|2017101715161
5|c702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|
R|2|^^^8571/1/not|13.36|U/L|^TECH\^NORM\^CRIT\^USER|||F||bmserv^SYSTEM|20171017151915|20171017151915
|c702^2^MU1#c702#1#2^7^193|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 226 Result request from host and the data manager result upload

C|1|I|0|I|
L|1|N|
10 ASTM communication examples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Order query from the host 227

Order query from the host

This section shows examples of ASTM test selection
queries (or order queries) from the host to the data
manager.

In this section
Order query for all tests (227)
Order query for all open tests (227)
Order query but no open tests (228)
Order query but sample not found (228)
Order query with sample identified by sequence
number (228)

Order query for all tests

This section shows an example of an ASTM order query
for all tests on a sample.

Host:
H|\^&|||host|||||cobas 8000^1.06|TSREQ|P|1|
Q|1|^S1^321015|||||||||||
L|1|N|

DM:

10 ASTM communication examples

H|\^&|14997||cobas 8000^1.06|||||host|TSUPL|P|1|20171020081756|
P|1||PatID1||Doe^John||19651125|M|
O|1|321015||^^^990^1\^^^991^1\^^^8717^1|||||||O||||1||||||||||F|
C|1|I|^^^^|G|
L|1|N|

Order query for all open tests

This section shows an example of an ASTM order query
for open tests on a sample.
u For an explanation of the request information status
code (sent in Q-13), see Query Record (Request
Information Record) (189)

Host:
H|\^&|||host|||||cobas 8000^1.06|TSREQ|P|1|
Q|1|^S1^321015||||||||||O|
L|1|N|

DM:
H|\^&|15002||cobas 8000^1.06|||||host|TSUPL|P|1|20171020082031|
P|1||PatID1||Doe^John||19651125|M|
O|1|321015||^^^990^1\^^^991^1|||||||O||||1||||||||||F|
C|1|I|^^^^|G|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 228 Order query from the host

L|1|N|

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|\^&|||host|||||cobas 8000^1.06|TSREQ|P|1|
Q|1|^S1^321016||||||||||O|
L|1|N|

DM:
H|\^&|15005||cobas 8000^1.06|||||host|TSUPL|P|1|20171020082222|
P|1||PatID1||Doe^John||19651125|M|
O|1|321016|||||||||O||||1||||||||||F|
C|1|I|^^^^|G|
L|1|N|

Order query but sample not found

This section shows an example of an ASTM order query
for all open tests on a sample with the ID 321016, but the
data manager does not have any record of a sample with
10 ASTM communication examples

this ID.

Host:
H|\^&|||host|||||cobas 8000^1.06|TSREQ|P|1|
Q|1|^S1^321016||||||||||O|
L|1|N|

DM:
H|\^&|14980||cobas 8000^1.06|||||host|TSUPL|P|1|20171020081236|
P|1||||^||||
O|1|321016|||||||||O||||1||||||||||F|
C|1|I|^^^^|G|
L|1|N|

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). (See fields Q-3.4 and O-4.1.) This functionality
was introduced in version 1.02.03.

Host:

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Order query from the host 229

H|\^&|||host|||||cobas 8000^1.06|TSREQ|P|1|
Q|1|^S1^^1013||||||||||O|
L|1|N|

DM:
H|\^&|563024||cobas 8000^1.06|||||host|TSUPL|P|1|20170720151956|
P|1||PatID1||Doe^John||19651125|M|
O|1||1013|^^^8413^1\^^^8571^1\^^^8706^1|||||||O||||1||||||||||F|
C|1|I|^^^^|G|
L|1|N|

10 ASTM communication examples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 230
10 ASTM communication examples Order query from the host

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 HL7 reference

11 HL7 protocol...........................................................................................................233
12 HL7 text content ...................................................................................................237
13 HL7 acknowledgment handling......................................................................295
14 HL7 communication examples ........................................................................305

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 233
Table of contents

HL7 protocol 11

This chapter presents the lower layers of the HL7

protocol, as used by cobas® 8000 data manager.

In this chapter 11
Overview of HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Physical communication . . . . . . . . . . . . . . . . . . . . . . . . 236

11 HL7 protocol

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
234
Table of contents
11 HL7 protocol

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Overview of HL7 235

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.

11 HL7 protocol

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
236 Physical communication

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.

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.

VT +/GDWD FS CR
11 HL7 protocol

w The HL7 data framed according to the HL7 standard

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 237
Table of contents

HL7 text content 12

HL7 field definitions

This section describes all the HL7 fields used in messages

sent to or from cobas® 8000 data manager.

In this chapter 12
HL7 messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Messages sent only by the data manager. . . . . . . 239
Messages sent only by the host . . . . . . . . . . . . . . . 240
Messages sent by either data manager or the
host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
HL7 segment description . . . . . . . . . . . . . . . . . . . . . . . 242
Message Header Segment - MSH . . . . . . . . . . . . . . . . 243
Message Acknowledgment Segment - MSA . . . . . . . 245
Patient Identification Segment - PID . . . . . . . . . . . . . . 246
Specimen Segment - SPM . . . . . . . . . . . . . . . . . . . . . . 247
SPM in test selections, patient results and quality
control results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
12 HL7 text content
SPM in calibration results . . . . . . . . . . . . . . . . . . . . 250
Specimen Container Detail Segment - SAC . . . . . . . . 251
Observation Request Segment - OBR . . . . . . . . . . . . . 252
Timing Quantity Segment - TQ1 . . . . . . . . . . . . . . . . . . 254
Observation Result Segment - OBX. . . . . . . . . . . . . . . 255
Observation Result Segment - OBX (for patient
results) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Observation Result Segment - OBX (for QC
results) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Observation Result Segment - OBX (for
calibration results) . . . . . . . . . . . . . . . . . . . . . . . . . . 265
OBX-5 description . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 238
Table of contents

OBX-5 for patient and QC tests with

quantitative or quantitative/qualitative results 268
OBX-5 for patient and QC tests with
qualitative or qualitative/quantitative results. . 269
OBX-5 for patient and QC tests with data
point and raw data results. . . . . . . . . . . . . . . . . 269
About qualitative flags . . . . . . . . . . . . . . . . . . . . 270
Measurement of c-module photometric Calibration
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Measurement of ISE Calibration Results . . . . . . . . . . . 272
Measurement of e-module immunological
Calibration Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Calibration alarm flags. . . . . . . . . . . . . . . . . . . . . . . . . . 276
Test Code Detail Segment - TCD . . . . . . . . . . . . . . . . . 277
Substance Identifier Segment - SID. . . . . . . . . . . . . . . 278
Comment Segment - NTE . . . . . . . . . . . . . . . . . . . . . . . 280
Types of comment segment . . . . . . . . . . . . . . . . . . 280
Query Parameter Segment - QPD (for a test
selection inquiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Query Parameter Segment - QPD (for a Result
Query) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Query Parameter Segment - QPD (for an Order
Query) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Response Control Parameter Segment - RCP . . . . . . 288
Equipment Detail Segment - EQU (from host to data
manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Equipment Command Segment - ECD . . . . . . . . . . . . 290
Equipment Detail Segment - EQU (from data
manager to host) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Inventory Detail Segment - INV . . . . . . . . . . . . . . . . . . 293
12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 HL7 messages 239

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

Messages sent only by the data manager

Only data manager sends the following types of message.

Message Segments Message Type Description

Inquiry for sending MSH TSREQ Inquiry for test selections is made
test selections QPD after a rack has passed the ID
RCP reader.
Result report MSH OUL^R22 Reports on the sample results.
PID OUL^R22^REAL QC results passed through data
SPM manager on reception
SAC
{ OUL^R22^BATCH Manual upload of QC results.
OBR Upload of patient sample results in
TQ1 reply to a result query.
{
OBX
TCD
{[SID]}(1)
{NTE}
(2)
}
}(3)
Calibration data MSH OUL^R22^PCUPL Reports calibration results.
12 HL7 text content
{ OUL^R22^ICUPL
SPM OUL^R22^ECUPL
OBR
OBX
SID
}
Equipment Status MSH ESU^U01 Information about the status of an
Update EQU instrument, sent either unsolicited
or in response to an Equipment
Status Request.
Equipment MSH INU^U05 Information about the availability of
Inventory Update EQU tests, sent in response to an
{INV} Equipment Inventory Request.
y Structure of HL7 messages sent by the data manager
(1) For messages containing patient results from the ISE module, no SID segment is sent.
(2) There may only be multiple OBX segments per OBR in data point result messages.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 240 HL7 messages

(3) There may be multiple OBR segments per PID segment, and multiple SID and NTE segments per OBX segment.

Messages sent 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 for a given
QPD sample ID sent by the host.
RCP
Order Query MSH TSREQ Inquiry for all test selections for a
QPD given sample ID sent by the host.
RCP
Masking MSH EAC^U07 Instructs data manager to mask or
EQU unmask certain tests.
{
ECD
}
Equipment Status MSH ESR^U02 Request for information about
Request EQU instrument status.
The data manager responds to this
message with an Equipment Status
Update.
Equipment MSH INR^U06 Request for information about test
Inventory Request EQU availability.
The data manager responds to this
message with an Equipment
Inventory Update.
y Structure of HL7 messages sent by the host

u For details of using result and order queries with

limited sample lifetimes or expired sample IDs, see:
Result query (74)
Order query (75)
Order and result queries with limited sample
lifetime (81).
12 HL7 text content

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.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 HL7 messages 241

Message Segments Message Type Description

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

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 242 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.
y HL7 field attributes
12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Message Header Segment - MSH 243

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||20170402173655||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
u To edit this, see Identifying the data manager application to the host (97).
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 created.
For a calibration message, this contains the datetime of the calibration.
MSH-8 Field contains no data.
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)
12 HL7 text content
o OUL^R22^ECUPL (e-module, or Immunology, Calibration Result)
o ESU^U01^ESU_U01 (Equipment Status Message)
o ESR^U02^ESR_U02 (Automated Equipment Status Request)
o INU^U05^INU_U05 (Inventory Update Message)
o INR^U06^INR_U06 (Automated Equipment Inventory Request)
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.
y Message header segment - MSH

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 244 Message Header Segment - MSH

Field Value Host DM Description

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 Acknowledgment Type. This field defines the conditions under which the
receiver has to respond with an acknowledgment message.
This field may contain:
o AL
Always send an acknowledgment message.
o SU
Send an acknowledgment message only after the message has been successfully
processed.
o ER
Send in error/reject conditions only.
o NE
Never send an acknowledgment.
u The data manager does not support all these options in all situations. For details
see HL7 acknowledgment handling (295).
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.
y Message header segment - MSH
12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Message Acknowledgment Segment - MSA 245

Message Acknowledgment Segment -

MSA
The host and the data manager use the message
acknowledgment segment in an acknowledgment
message.

MSA|AE|38764|ORA-20001: Validation error|

MSA|AA|38764||

Field Value Host DM Description

MSA-1 String R R Acknowledgment 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 acknowledgment code.
u For details of acknowledgment handling, see HL7 acknowledgment
handling (295).
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.
u For details of logging, see Logging level settings (104).
y Message acknowledgment segment - MSA

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 246 Patient Identification Segment - PID

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|PatID1|||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.
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.
y Patient identification segment

! WARNING
The data manager supports only M, F, or U for
patient sex.
r For male patients, the host must send M, for females,
F. Otherwise the wrong reference range might be
applied. The data manager reads any other value as U,
and applies the reference ranges for a patient of
unknown sex.
12 HL7 text content

r 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
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Specimen Segment - SPM 247

Specimen Segment - SPM

The specimen segment in calibration messages is quite
different to the specimen segment in test selection
messages and patient and quality control result
messages.
u For the use of the Specimen segment SPM with
calibration results, see SPM in calibration
results (250).
u For details of the use of the Specimen segment (SPM)
with patient and quality control results, and with test
selection downloads, see SPM in test selections,
patient results and quality control results (247).

SPM in test selections, patient results 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.

When identifying the sample by sample ID (default):

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

When identifying the sample by sequence number:

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

For a quality control result: 12 HL7 text content

SPM||PNU^123456^301^20160913^27||S1||not|||||Q|||^^^^|||20160903142217||||||||||SC|

Field Value Host DM Description

SPM-1 Field contains no data.
y Specimen Segment - SPM, in test selections, patient results and quality control results

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 248 Specimen Segment - SPM

Field Value Host DM Description

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
numbers: sample’s 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 O O SampleID A value is only sent in this field when the sample is identified
by sample ID. 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 O O Sequence A value is only sent in this field if the sample is identified by
_Number sequence number. If the sample is identified by sequence
number, this contains the sequential number. (Max. value =
60,000.)
If the host sends a sample ID in SPM-2.1, the data manager
ignores this component.
u For details of sequence numbers, see Identifying patient
samples by sequence number (455).
Quality control material
For quality control material, Name^Lot^ID^ExpDate^ControlCode
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.
SPM-2.5 String - O/R ControlC Control code used to uniquely identify the QC material on the
ode host. (Also contained in data manager.) This component is
populated by the QC code field of the Insert QC material
form.
It is not possible to order test selections for QC from the host.
u For details of how the sample identifier SPM-2 is used with calibration
result messages, see SPM in calibration results (250).
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
12 HL7 text content

S2 Urine
S3 Cerebrospinal Fluid
S4 Supernatant
S5 Other fluids
S6 Whole blood
S7 Oral fluids (Saliva)
S8 Hemolysate (only supported by e 801module)
S9 Amniotic fluid (only supported by e 801 module)
SA Processed stool (only supported by e 801 module)
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.
y Specimen Segment - SPM, in test selections, patient results and quality control results

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Specimen Segment - SPM 249

Field Value Host DM Description

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.
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 Workplace > Data
Review.
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.
12 HL7 text content
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
o NST0 Non-standard tube
o FBT1 False Bottom Tube 1
o FBT2 False Bottom Tube 2
o FBT3 False Bottom Tube 3
o <Empty> Unknown cup type
If the host sends no container type value, then data manager sends no
value to the control unit.
u For details on how these values are handled, see Sample container
types (41)
y Specimen Segment - SPM, in test selections, patient results and quality control results

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 250 Specimen Segment - SPM

SPM in calibration results

The data manager uses the specimen segment in a
calibration result message to send information about the
specimen.

SPM||1^814567^901^1^20171130|||||||||C^P|

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 calibrator 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.
12 HL7 text content

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.
y SPM in calibration results

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Specimen Container Detail Segment - SAC 251

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.)
y Specimen container detail segment - SAC

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 252 Observation Request Segment - OBR

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

An OBR is created for every regular test and every

cobas e flow test. For a regular test, there is one OBX per
OBR. For a cobas e flow test, there is one OBR segment,
which has one OBX segment for the cobas e flow test,
and one OBX segment for each associated embedded
test.

The following shows an example OBR segment from a

cobas e flow test:

OBR|1|||15000|

If upload of raw data and data point results is enabled,

results from the e 801 module additionally contain 4 raw
data and data point segments.

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.
y Observation request segment - OBR
12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Observation Request Segment - OBR 253

Field Value Host DM Description

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
OBR-4.1 String 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 data manager 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.
u For more details on sending serum index orders, see
Sending test selections (77).
Orders with invalid (unknown) test codes are handled by the
data manager as follows:
o If an order contains both valid and invalid test codes, the
data manager accepts the order but logs an error for
each invalid test code.
o If an order contains only invalid test codes, the data
manager rejects the order.
o The rejection of invalid test codes and/or orders is shown
in the information window.
Embedded tests of cobas e flow tests cannot be ordered. If
this field contains the test code of an embedded test, the
data manager will return an error message.
OBR-4.2 String O - Dilution Dilution factor.
Permitted values are:
o For an ISE module, the only permitted factor is 1 ,
meaning no dilution
o For a c-module: 1 , Inc , Dec , 3 , 5 , 10 , 20 , 50
o For an e 602 module test: 1 , 2 , 5 , 10 , 20 , 50 , 100 ,
400
o For a regular e 801 module test: 1 , 1.1 , 2 , 5 , 10 , 20 ,
30 , 50 , 100 , 400 , 900 , 27000
o For an e 801 cobas e flow test: 1
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.
12 HL7 text content
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
A message which contains multiple tests cannot contain a combination of
these codes.
The other OBR fields contain no data.
y Observation request segment - OBR

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 254 Timing Quantity Segment - TQ1

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.
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)
y Timing quantity segment - TQ1
12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Observation Result Segment - OBX 255

Observation Result Segment - OBX

The data manager uses the OBX segment to upload the
details of test results. The structure of the segment differs
depending on the type of result being uploaded.

In this section
Observation Result Segment - OBX (for patient
results) (255)
Observation Result Segment - OBX (for QC results) (261)
Observation Result Segment - OBX (for calibration
results) (265)
OBX-5 description (268)

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.

An OBR is created for every test. There is one OBX per

OBR.

For a cobas e flow test, there is one OBR segment, which

has one OBX segment for the cobas e flow test, and one
OBX segment for each associated embedded test.

If upload of raw data and data point results is enabled,

results from the e 801 module additionally contain 4 raw
data and data point OBX segments for each OBR. For a
cobas e flow test, results from the e 801 module
additionally contain 4 raw data and data point OBX
segments for each OBR and each embedded test.
u For details of how the data manager uses OBX with
12 HL7 text content
quality control results, see Observation Result
Segment - OBX (for QC results) (261).
u For details of how the data manager uses OBX with
calibration results, see Observation Result Segment -
OBX (for calibration results) (265).

Regular test patient result examples

OBX|1||990||0.99|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||F|||20171020095905|bmserv^SYSTEM||128|ISE^2^MU
1#ISE#1#2^4|20171020095921|

OBX|3||8717||1^-0.02|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20171019175614|bmserv^SYSTEM||77|c701^1^M
U1#c701#1#1^6|20171019180627|

An observation result segment for a result below the

EP17-A level of detection:

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 256 Observation Result Segment - OBX

OBX|1||989||2.1|mmol/L|^TECH~12 - 144^NORM~^CRIT~^USER|HU|||F|||20170621084348|bmserv^SYSTEM||28|ISE
^1^MU1#ISE#1#1^3|20170621084404|

An observation result segment with data point and raw

data values (this example shows only the EFS portion of
the message):

OBX|2||17025||78492.30^11339&11426&12266&12045&11224&11596&12121&11505&11650&10719&11800&11253&10994
&11087&11489&11211&11460&11110&11643&12015&11198&11351&11802&12139&11191&11603&12194&11641&11356&119
17&11604&11971&12131&11602&12109&12037&11661&11534&10527&12140&12295&12454&12476&12158&12232&10888&1
1762&11624&10826&11160&10542&11178&12099&11658&12083&11488&11434&11775&12317&11497&11515&11778&11233
&10323&11115&11157&10747&11910&11948&11958&11583&11012&11797&11537&11444&10993&12172&11255&11986&107
76&28570&38234&39006&39052&38940&38778&38533&38424&38217&38037&37873&37690&37477&37381&37212&37003&3
6916&36740&36665&36479&36351&36235&36114&36100&35921&35780&35723&35633&35601&35451&35349&35272&35175
&35094&34963&34951&34812&34723&34646&34594&34555&34471&34372&34259&34205&34141&34026&34018&33882&338
45&33759&33743&33704&33682&33611&33495&33432&33416&33342&33265&33151&33143&33163&33022&33035&33040&3
2938&32923&32855&32811&32772&32745&32558&32553&32437&32342&32388&32345&32291&32365&32297&32205&32212
&32171&32158&32137&32008&32124&31985&31957&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|count|^TECH~^NORM~^CRIT~^USER||||F|||20150414140223|bmserv^SYSTEM||EFS|e801^2^MU1#e801#1#2^4|2015
0414142055|

cobas e flow test patient result examples

OBX|1||32000||-1^ ||^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20171201162636|

OBX|4||AHIV_01||-1^0.149|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|201712011626
36|

OBX|10||11013|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||3286
|e801^1^MU1#e801#2#1^9|20171201162636|

An observation result segment for a result below the

EP17-A level of detection:

OBX|10||11013|| ^ |COI|^TECH~^NORM~^CRIT~^USER|HU|||F|||20171201160804|bmserv^SYSTEM||32
86|e801^1^MU1#e801#2#1^9|20171201162636|

An observation result segment for a result from a

cobas e flow test generated subresult:

OBX|2||HIVDuo_01||-1^0.362|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|2017120116
2636|
12 HL7 text content

An observation result segment with data point and raw

data values (this example shows only the EFS portion of
the message):

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Observation Result Segment - OBX 257

OBX|6||11014||769.0851^11339&11426&12266&12045&11224&11596&12121&11505&11650&10719&11800&11253&10994
&11087&11489&11211&11460&11110&11643&12015&11198&11351&11802&12139&11191&11603&12194&11641&11356&119
17&11604&11971&12131&11602&12109&12037&11661&11534&10527&12140&12295&12454&12476&12158&12232&10888&1
1762&11624&10826&11160&10542&11178&12099&11658&12083&11488&11434&11775&12317&11497&11515&11778&11233
&10323&11115&11157&10747&11910&11948&11958&11583&11012&11797&11537&11444&10993&12172&11255&11986&107
76&28570&38234&39006&39052&38940&38778&38533&38424&38217&38037&37873&37690&37477&37381&37212&37003&3
6916&36740&36665&36479&36351&36235&36114&36100&35921&35780&35723&35633&35601&35451&35349&35272&35175
&35094&34963&34951&34812&34723&34646&34594&34555&34471&34372&34259&34205&34141&34026&34018&33882&338
45&33759&33743&33704&33682&33611&33495&33432&33416&33342&33265&33151&33143&33163&33022&33035&33040&3
2938&32923&32855&32811&32772&32745&32558&32553&32437&32342&32388&32345&32291&32365&32297&32205&32212
&32171&32158&32137&32008&32124&31985&31957&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|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||EFS|e801^2^MU1#e801#2#2^10|201
71201162624|

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, and the count resets to 1
following every occurrence of an OBR segment. For example:
OBR|1|…
OBX|1|…
OBX|2|…
OBR|2|…
OBX|1|…

OBX-2 Field contains no data.

OBX-3 String - R The test code. (Observation identifier) This identifies the test or analyte
which this message relates to.
A cobas e flow test can contain an generated subresult. Therefore, in the
case of a cobas e flow test, this field can contain the name of this
generated subresult. This field can also contain the host code assigned to
this generated subresult, if the Assign host code per reported lab unit
option is enabled.
u For more information about host code assignment, see Assigning host
codes to cobas e flow test results and generated subresults (116)
OBX-4 For regular tests: field contains no data.
For cobas e flow tests: Combination ID. Only provided for linkage records,
and only sent if the Send additional link information for calculated QC
check box is selected. Otherwise empty.
The combination ID is highlighted in the following example:
OBX|15||22000|3| ^ |COI|^TECH~^NORM~^CRIT~^USE
R||||B|||20171201160752|^SYSTEM|||e801^0^MU1#e801#2#0^8|20
171201162636|
12 HL7 text content
u For more information, see Sending additional link information for
calculated QC (111).
OBX-5 Complex - R Result value.
The result values are only transmitted for patient and QC results.
Takes the format:
Value1^Value2
The result values that are sent differ depending on the type of test. The
differences are explained in a series of separate tables in the next section.
u OBX-5 description (268).
OBX-6 String - O Units of measurement used for measuring the result
For a data point result, this shows count or COUNT .
For qualitative cobas e flow test results, no value is sent in this field.
y Observation Result Segment - OBX (for patient results)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 258 Observation Result Segment - OBX

Field Value Host DM Description

OBX-7 Complex - O 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.
For patient results, this is a required field.
For raw data and data point results, no data is sent in this field.
OBX-7.1 String - O The RangeDefinitionString string component can consist of 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.
u For QC and calibration results, see Observation Result Segment - OBX
(for QC results) (261)or Observation Result Segment - OBX (for
calibration results) (265).
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
12 HL7 text content

A Alphanumeric result out of normal range

AA Alphanumeric result out of critical range
HU High uncertainty (Enhancement to HL7)
eFlow.E Standard alarm for cobas e flow tests
eFlow.W Generic cobas e flow test warning
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.
u For further details on the EP17-A flags, see EP17-A and the result
abnormal flags (53).
OBX-9 Field contains no data.
OBX-10 Field contains no data.
y Observation Result Segment - OBX (for patient results)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Observation Result Segment - OBX 259

Field Value Host DM Description

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:
o Calculated test, but test could not be calculated (for example,
divided by zero)
o Canceled cobas e flow test. (All measured embedded test results
are transmitted, if this feature is enabled.)
o B : (cobas e flow tests only) Additional record - a linkage record, used
to link the result to a calculated QC result
o V : (cobas e flow tests only) Verified - a measured embedded test
result which has been promoted to the result of a cobas e flow test
For cobas e flow tests, the value that is sent is affected by the Use legacy
record status check box.
u Using legacy record status (112)
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.
If the Send additional link information for calculated QC check box is
selected: pipetting time of linkage record. (A timestamp showing the
earliest pipetting time of the embedded test results linked by this record.)
u Sending additional link information for calculated QC (111).
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 String - O For patient results, contains 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, or linkage records.
12 HL7 text content
For raw data and data point results, contains one of the following codes,
signifying raw data type:
o EFS Effective signal
o EFV Effective voltage
o EFC Effective current
o PMT PMT spike
y Observation Result Segment - OBX (for patient results)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 260 Observation Result Segment - OBX

Field Value Host DM Description

OBX-18 Complex - R Measurement unit ID, identifying the module that performed the test.
ModuleType^SubModule^AnalyticalUnitID^InstrumentID^B
ottle^SBNo
OBX-18.1 String - R ModuleType One of the following:
c502 , Results from the specified measuring
c701 , module, or manual results entered on behalf
e602, of that module.
ISE ,
c702 or
e801
DM Results that cannot be attributed to a module.
o Results calculated on the data manager
o Manual results entered on the data
manager but that cannot be attributed to
a module
o Generic cobas e flow test alarms
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 a result from a submodule.
o 0 (zero) otherwise. (Used for cobas e flow test
generated subresults.)
OBX-18.3 String - R Analytical Identifier for the module, as sent to the host. This setting
UnitID is configurable in the cobas® 8000 data manager.
Default:
Instrument#ModuleType#Position#SubModule
Example: MU1#e801#2#2
u For details, see Identifier of the analytical unit sent to
host (108).
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 - O For regular tests: time at which result is available. In some cases, this field
is empty.
For cobas e flow tests: analysis time of linkage record. (A timestamp
showing the latest analysis time of the embedded test results linked by this
record.)
u Sending additional link information for calculated QC (111).
12 HL7 text content

y Observation Result Segment - OBX (for patient results)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Observation Result Segment - OBX 261

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 quality control results of all tests.
u For details of how the data manager uses OBX with
regular test patient results, see Observation Result
Segment - OBX (for patient results) (255).
u For details of how the data manager uses OBX with
calibration results, see Observation Result Segment -
OBX (for calibration results) (265).

Regular test QC result example

OBX|1||8685||121|U/L|120^TARGET~25^SD||||F|||20171019111907|bmserv^SYSTEM||76|c701^1^MU1#c701#1#1^6^
Standby^1|20171019112922|

QC result with raw data example

OBX|2||15721||28562.32|count|||||F|||20150408125352|bmserv^||EFS|e801^1^MU1#e801#1#1^3^Current|20150
408131225|

cobas e flow test QC result example

OBX|1||22000|1| ^4.18|COI|3.93^TARGET~0.655^SD||||F|||20171124084912|^SYSTEM|||e801^0^MU1#e801
#2#0^8^Standby^1|20171124090809|

Example of raw data from a cobas e flow test

QC result
OBX|3||11013||11615.02|count|||||F|||20171124084912|bmserv^SYSTEM||EFS|e801^1^MU1#e801#2#1^9^Standby
^1|20171124090745|

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, and the count resets to 1
following every occurrence of an OBR segment. For example:
OBR|1|…
OBX|1|…
OBX|2|…
OBR|2|…
12 HL7 text content
OBX|1|…

OBX-2 Field contains no data.

OBX-3 String - R The test code. (Observation identifier, or Application code) This identifies
the test or analyte which this message relates to.
OBX-4 o For regular tests: field contains no data.
o For calculated QC results of cobas e flow tests: combination ID, used
to link a calculated QC result to a cobas e flow test result. This
information is only sent if the Send additional link information for
calculated QC check box is selected.
o For QC results of corresponding embedded tests: field contains no
data.
u Sending additional link information for calculated QC (111).
y Observation Result Segment - OBX (for QC results)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 262 Observation Result Segment - OBX

Field Value Host DM Description

OBX-5 Complex - R Result value.
The result values are only transmitted for patient and QC results.
Takes the format:
Value1^Value2
The result values that are sent differ depending on the result type of the
test. The differences are explained in a series of separate tables in the next
section.
u OBX-5 description (268).
OBX-6 String - R Units of measurement used for measuring the result
OBX-7 Complex - O 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
When either the target value or the standard deviation is null, it is not
included in the result message.
Asymmetric control results have no standard deviation. In the case of
asymmetric control results, this field may contain lower and upper range
values, for example:
0.84^TARGET~0.14^LOWER~0.14^UPPER
When the Use Custom Values flag is enabled, the lower and upper range
values represent custom range limits. If the flag is not enabled, the lower
and upper values are taken from the quality control itself.
Asymmetric control results may also be sent without a target value, for
example:
0.14^LOWER~0.14^UPPER
For raw data/data point messages, this field is empty.
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”
o LOWER Hard-coded value to indicate “Lower range value” (only used
in asymmetric control results)
o UPPER Hard-coded value to indicate “Upper range value” (only used
in asymmetric control results)
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.
OBX-9 Field contains no data.
OBX-10 Field contains no data.
OBX-11 String - R Result status
12 HL7 text content

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.
For cobas e flow tests: Pipetting time of linkage record. (A timestamp
showing the earliest pipetting time of the QC result.)
y Observation Result Segment - OBX (for QC results)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Observation Result Segment - OBX 263

Field Value Host DM Description

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.
y Observation Result Segment - OBX (for QC results)

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 264 Observation Result Segment - OBX

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 ModuleType One of the following:
c502 , Results from the specified measuring
c701 , module, or manual results entered on behalf
e602, of that module.
ISE ,
c702 or
e801
DM Results that cannot be attributed to a module.
o Results calculated on the data manager
o Manual results entered on the data
manager but that cannot be attributed to
a module
o Generic cobas e flow test alarms
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 a result from a submodule.
o 0 (zero) otherwise. (Used for calculated QC and
linkage records.)
OBX-18.3 String - R Analytical Identifier for the module, as sent to the host. This setting
UnitID is configurable in the cobas® 8000 data manager.
Default:
Instrument#ModuleType#Position#SubModule
Example: MU1#e801#2#0
u For details, see Identifier of the analytical unit sent to
host (108).
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
12 HL7 text content

with 1.
OBX-19 DateTime - O For regular test QC results: Time at which result is available. In some cases,
this field is empty.
For cobas e flow test QC results: Pipetting time of the last involved
embedded test QC result.
y Observation Result Segment - OBX (for QC results)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Observation Result Segment - OBX 265

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.
u For details of OBX with patient results, see
Observation Result Segment - OBX (for patient
results) (255).
u For details of OBX with QC results, see Observation
Result Segment - OBX (for QC results) (261).

Calibration result examples Photometric Calibration Result Segment:

OBX|1||8685||0^3&4&22851&2&22866&|||16|||F||||bmserv||75|c701^1^MU1#c701#1#1^6^Current^1|20171019091
421|

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|||Vali
d|||F||||bmserv||37|ISE^1^MU1#ISE#1#1^7|20170316105741|

Immunological Calibration Result Segment:

OBX|1||1||Valid^false^false^false^1.074^false^^false^false^39609.680&39716.950^^^^^|||LotCalibration
|||F||||bmserv||25|e602^1^MU1#e602#2#1^9^Current|20171018175819|

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, and the count resets to 1
following every occurrence of an OBR segment. For example:
OBR|1|…
OBX|1|…
OBX|2|…
OBR|2|…
OBX|1|…

OBX-2 Field contains no data.

OBX-3 String - R The test code (application code). This identifies the test or analyte which
12 HL7 text content
this message relates to.
OBX-4 Field contains no data.
y Observation Result Segment - OBX (for calibration results)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 266 Observation Result Segment - OBX

Field Value Host DM Description

OBX-5 String - R Result values.
u For photometric calibration results, see Measurement of c-module
photometric Calibration Results (271).
u For ISE calibration results, see Measurement of ISE Calibration
Results (272).
If suppression of results outside the technical limit is enabled,
suppressed results are sent as 7 spaces.
u Result suppression for results outside the technical limit (54)
For omitted cobas e flow test results, a user-defined value is sent.
u Configuring omitted result reporting (114)
For cobas e flow tests, the order in which quantitative/qualitative result
values are sent can be configured.
u Assigning result type for cobas e flow test result upload (115)
OBX-6 Field contains no data (for calibration results).
OBX-7 Field contains no data.
OBX-8 String - O Calibration alarm flags.
u For details see Calibration alarm flags (276).
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.
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.
y Observation Result Segment - OBX (for calibration results)
12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Observation Result Segment - OBX 267

Field Value Host DM Description

OBX-18 Complex - R For ISE module:
Analytical unit ID, identifying the module that performed the test.
u The components and values are the same as for patient and QC
results, see Identifier of the analytical unit sent to host (108).
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 ModuleType One of the following:
c502 , Results from the specified measuring
c701 , module, or manual results entered on behalf
e602, of that module.
ISE ,
c702 or
e801
DM Results that cannot be attributed to a
module.
o Results calculated on the data manager
o Manual results entered on the data
manager but that cannot be attributed
to a module
o Generic cobas e flow test alarms
c8000 Results from the cobas® 8000 modular
analyzer series instrument that cannot be
mapped to an actual measuring submodule,
for example, sample short.
OBX-18.2 Number - R SubModule o 1 or 2 , for a result from a submodule.
o 0 (zero) otherwise. (Used for calculated QC and
linkage records.)
OBX-18.3 String - R Analytical Identifier for the module, as sent to the host. This setting
UnitID is configurable in the cobas® 8000 data manager.
Default:
Instrument#ModuleType#Position#SubModul
e
Example: MU1#c502#2#1
u For details, see Identifier of the analytical unit sent
to host (108).
OBX-18.4 Number - R Instrument Instrument number in data manager (A specific
ID identifier inside the data manager which identifies a
module. This is a number which has no relationship to
12 HL7 text content
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 - O Time at which result is available. In some cases, this field is empty.
y Observation Result Segment - OBX (for calibration results)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 268 Observation Result Segment - OBX

OBX-5 description
The result values of the test are sent in field OBX-5. The
format of the field differs depending on the result type of
the test. This section explains the format for each type.

The result values are only transmitted for patient and QC

results.

For cobas e flow tests, the order in which

quantitative/qualitative result values are sent can be
configured. For cobas e flow tests, the following result
types are supported:
• Quantitative
• Qualitative
• Quantitative/qualitative
• Qualitative/quantitative
u Assigning result type for cobas e flow test result
upload (115)

Only patient and QC results are covered in this section.

u For OBX-5 in calibration results, see Observation
Result Segment - OBX (for calibration results) (265)

In this section
OBX-5 for patient and QC tests with quantitative or
quantitative/qualitative results (268)
OBX-5 for patient and QC tests with qualitative or
qualitative/quantitative results (269)
OBX-5 for patient and QC tests with data point and raw
data results (269)
About qualitative flags (270)

OBX-5 for patient and QC tests with quantitative or quantitative/qualitative

results
12 HL7 text content

For regular tests or cobas e flow tests with pure

quantitative results, and for cobas e flow tests with
quantitative/qualitative results, OBX-5 takes the following
format:

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Observation Result Segment - OBX 269

Field Value Host DM Description

OBX-5 Complex - R For quantitative results from ISE and e-modules, the components take the following
values:
QuantitativeResult^QualitativeResult
For quantitative results from c-modules, only the QuantitativeResult
component is sent, without any other components or delimiters.
OBX-5.1 Number - R Quantitative The quantitative result.
Result For regular tests, if suppression of results outside the technical
limit is enabled, suppressed results are sent as 7 spaces (ASCII 32
/ 0x20).
u Result suppression for results outside the technical limit (54)
For omitted cobas e flow test results, a configured value is sent.
u Configuring omitted result reporting (114)
OBX-5.2 Number - O QualitativeR Empty or a qualitative flag.
esult u About qualitative results (186)
y OBX-5 for tests with pure quantitative results, or with quantitative/qualitative results

OBX-5 for patient and QC tests with qualitative or qualitative/quantitative

results
For regular tests or cobas e flow tests with pure
qualitative results, and for cobas e flow tests with
qualitative/quantitative results, OBX-5 takes the following
format:

Field Value Host DM Description

OBX-5 Complex - R QualitativeResult^QuantitativeResult
OBX-5.1 Number - R QualitativeR Empty or a qualitative flag.
esult u About qualitative results (186)
For omitted cobas e flow test results, a configured value is sent.
u Configuring omitted result reporting (114)
OBX-5.2 Number - O Quantitative The quantitative result, like value for a quantitative result. For e-
Result module qualitative results this contains COI .
The quantitative result.
For e-module qualitative and quantitative results, this contains
COI or percent.
For missing qualitative results from c- and e-modules, 7 spaces
12 HL7 text content
(ASCII 32 / 0x20) are sent in both sub-components.
y OBX-5 for tests with pure qualitative results, or with qualitative/quantitative results

OBX-5 for patient and QC tests with data point and raw data results
If the data manager is configured to send raw data and
data point values for a regular test or cobas e flow test
result, OBX-5 takes the following format:

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 270 Observation Result Segment - OBX

Field Value Host DM Description

OBX-5 Complex - R ReportableResult^DataPointValues
OBX-5.1 Number - R ReportableRes The result value.
ult For regular tests, if suppression of results outside the technical
limit is enabled, suppressed results are sent as 7 spaces.
u Result suppression for results outside the technical
limit (54)
For omitted cobas e flow test results, a configured value is
sent.
u Configuring omitted result reporting (114)
OBX-5.2 Number - O DataPointValu Data points. Up to 200 data point values, separated by
es backslashes (\).
y OBX-5 for tests with data point and raw data values

About qualitative flags

A qualitative result value sent in OBX-5 can take the
following values:
• For c-modules and ISE modules: an integer code from
-2 to 3 inclusive.
• For e-modules: an integer code -1 (non-reactive), 0
(border line), 1 (reactive).
• For cobas e flow tests, this can be a numeric code.
u For cobas e flow test codes, see Result message
codes for cobas e flow tests (439)
u The codes can be configured on the cobas® 8000
modular analyzer series instrument, under Utility
> Application > Range. See the cobas® 8000
modular analyzer series Operator’s Manual for details.
12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Measurement of c-module photometric Calibration Results 271

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
y Field OBX-5 for photometric calibration results from a c-module

Complete example c-module calibration The following is a complete example of a calibration from
result message a c-module (photometry).

MSH|^~\&|cobas 8000||host||20171019091421||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&|||0|||F||||bmserv||75|c701^1^MU1#c701#1#1^6^Current|20171019091421
|
SID||
SPM||2^153314^401^1^20120131|||||||||C^P|
OBR|2|||8685|
OBX|1||8685||0^-362&-361&24786&-362&24149&|||0|||F||||bmserv||75|c701^1^MU1#c701#1#1^6^Current|20171
019091421|
SID||

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 272 Measurement of ISE Calibration Results

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.
u For details, see ISE data alarms (272).
Data Complex Test calibration analytical data.
u For details, see ISE calibration analytical data (272).
y Measurement of ISE Calibration Results

ISE data alarms The data alarms from the ISE calibration contain the
following subcomponents, separated with an ampersand
( & ). Each component is a Number type.
• 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
• 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.
12 HL7 text content

• 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
• Compensation value data alarm

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Measurement of ISE Calibration Results 273

Complete example ISE calibration result The following is a complete example of a calibration from
message an ISE module.

MSH|^~\&|cobas 8000||host||20170316105742||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|||Vali
d|||F||||bmserv||37|ISE^1^MU1#ISE#1#1^3|20170316105741|
SID||
SPM|||||||||||C^I|
OBR|2|||990|
OBX|1||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|ISE^1^MU1#ISE#1#1^3|20170316105742|
SID||
SPM|||||||||||C^I|
OBR|3|||991|
OBX|1||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|||Vali
d|||F||||bmserv||39|ISE^1^MU1#ISE#1#1^3|20170316105742|
SID||

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 274 Measurement of e-module immunological Calibration Results

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^M
axSignal^CalibratorFactor^Deviation^Slop
e^MinAcceptDiff^SystemError^SignalVal1^S
ignalVal2^TargetValue^Unit^CUTOff^Border
LineAreaUpperLimit^BorderLineAreaLowerLi
mit

Subcomponent Description Sent in result type

CalResultStatus String Result Status: Qualitative and quantitative
o Valid
o Invalid
MissingValue String o true if violation Qualitative and quantitative
o false if no violation
MinSignal String o true if violation Qualitative and quantitative
o false if no violation
MaxSignal String o true if violation Qualitative and quantitative
o false if no violation
CalibratorFactor Number Decimal value Quantitative
Deviation String o true if violation Qualitative and quantitative
o false if no violation
Slope String o true if violation Qualitative
o false if no violation
MinAcceptDiff String o true if violation Quantitative
o false if no violation
SystemError String o true if violation Qualitative and quantitative
o false if no violation
SignalVal1&SignalVal2 Complex Signal value, in two decimal Qualitative and quantitative
subcomponents:
SignalVal1&SignalVal2
12 HL7 text content

TargetValue Complex Target Value (for quantitative tests). This

can be empty
Level1&Level2&Level3&Level4&
Level5
Note that the data manager does not
send data for this component.
Unit String Unit
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.
y Measurement of e-module immunological Calibration Results

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Measurement of e-module immunological Calibration Results 275

Complete example e-module calibration The following is a complete example of a calibration from
result message an e-module (immunology).

MSH|^~\&|cobas 8000||host||20171118175844||OUL^R22^ECUPL|14268||2.5||||ER||UNICODE UTF-8|

SPM||2^158941^1^None^20171119|||||||||C^E|
OBR|1|||1|
OBX|1||1||Valid^false^false^false^1.064^false^^false^false^38293.490&38596.120^^^^^|||LotCalibration
|||F||||bmserv||26|e602^2^MU1#e602#2#2^10^Current|20171118175844|
SID|1^^^ASY^18^0|157328|5|
SPM||1^158941^1^None^20171119000000|||||||||C^E|
OBR|2|||1|
OBX|1||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|20171118175844|
SID|1^^^ASY^18^0|157328|5|

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 276 Calibration alarm flags

Calibration alarm flags

This section describes the calibration alarms sent 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:
• Valid meaning the calibration was successful.
• Invalid meaning calibration failed.

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

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

NoCalibration

LotCalibration

ContainerCalibration

InheritedLotCalibration

InheritedItemCalibration

UserModifiedCalibration

UnmaskedCalibration

FailedCalibration
12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Test Code Detail Segment - TCD 277

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 String - R Universal Service Identifier. (Testcode or Application Code, which identifies the test or
analyte tested for.)
For a cobas e flow test, this field can contain the name of the generated subresult.
TCD-2 String - R Auto-dilution factor. Permitted values are:
o For an ISE module, the dilution factor is always: 1
o For a c-module: 1 , Inc , Dec , 3 , 5 , 10 , 20 , 50 .
o For the e 602 module (immunoassay): 1 , 2 , 5 , 10 , 20 , 50 , 100 , 400
o For the e 801 module (immunoassay): 1 , 2 , 5 , 10 , 20 , 50 , 100 , 400 , 900 ,
27000
y Test code detail segment - TCD

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 278 Substance Identifier Segment - SID

Substance Identifier Segment - SID

The data manager uses the substance identifier segment
to identify the reagents used in a test, when sending 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.
12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Substance Identifier Segment - SID 279

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 String - O/R Test Testcode. This is the code number the host uses for
identifying the test or analyte to test for.
For linkage records, this field contains the host code of the
installation unit of the cobas e flow test.
SID-1.2 String - O/R Type Type of the test, if available.
For cobas e flow test kits, this is empty.
SID-1.3 Number - O/R Code Reagent code. For calibration results from a c- or e-module,
this is empty.
For cobas e flow test kits, this field contains the Application
Code of the cobas e flow test.
SID-1.4 String - O/R ReagentT Reagent type. Empty for c-module calibration results.
ype 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)
KIT Reagent kit used for cobas e flow tests.
This value is used in cobas e flow test
calculated QC results, and in linkage records
with embedded tests linked by strict combo kit.
SID-1.5 Number - O/R Position Reagent Position on Disk.
For cobas e flow test kits, this is empty.
SID-1.6 Number - O/R Expiry Expiration flag:
o 0 = not expired
o 1 = expired
SID-2 String - O Lot number of the reagent or kit used. Not used for ISE-module calibration
results, nor with non-Roche material.
SID-3 String - O o Serial number of the reagent used. Not used for ISE-module
12 HL7 text content
calibration results, nor with non-Roche material.
o If SID-1.4 contains the value KIT : Unique kit ID. (This ID is unique for
one given instrument.)
y Substance identifier segment - SID

q Note that R1-R3 might not all be present on a c-

module (photometric).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 280 Comment Segment - NTE

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^20170402172605|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.
NTE-3 Complex - O/R Comment. Value depends on value of NTE-4. This is optional if NTE-4 is G (Result
comment)
u For details of this field, see Types of comment segment (280).
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.
y Comment segment - NTE

Types of comment segment

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

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

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Comment Segment - NTE 281

If the instrument sends the data manager a 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.

An additional data alarm is available for the main result of

a cobas e flow test:
• eFlow.E^Standard alarm for e801
workflow tests
u For details of possible error flags, see Data
alarms (363)

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 282 Query Parameter Segment - QPD (for a test selection inquiry)

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), or if a barcode read
error occurs, QPD-3 contains a string 22 asterisks (*):

QPD|TSREQ|12897|**********************||50045|1||||S1|SC|R1|R|

If samples are identified by sequence number:

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

u For more information, see Handling query messages

without barcodes (448)

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.
u For details of sequence numbers, see Identifying patient samples by
sequence number (455).
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.
12 HL7 text content

QPD-8 Field contains no data.

QPD-9 Field contains no data.
y Query parameter segment - QPD - for a test selection inquiry

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Query Parameter Segment - QPD (for a test selection inquiry) 283

Field Comp. Value Host DM Description

QPD-10 String - R Rack type as assigned to a specific sample type on the cobas® 8000
modular analyzer series instrument. 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 Hemolysate (only supported by e 801 module)
S9 Amniotic fluid (only supported by e 801 module)
SA Processed stool (only supported by e 801 module)
S0 No specimen assigned (only used for messages from data
manager).
QPD-11 String - R Sample container type.
o SC Standard cup
o MC Micro cup
o NST0 Non-standard tube
o FBT1 False bottom tube 1
o FBT2 False bottom tube 2
o FBT3 False bottom tube 3
o <Empty> Unknown cup type
If the host sends no container type value, then data manager sends no
value to the control unit.
u For details on how these values are handled, see Sample container
types (41)
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
y Query parameter segment - QPD - for a test selection inquiry

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 284 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|||||||S1

QPD|RSREQ||12896|F||||||S1

If identifying samples by sequence number:

QPD|RSREQ||^1031||||||S1

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.
The data manager returns results for whichever unique current sample
matches the combination of sample ID and rack type, if given. If there is
no current sample, no answer is sent.
u For details of sample ID lifetimes, see Reusing sample IDs and sample
lifetimes (48).
u For details of using result and order queries with limited sample
lifetimes or expired sample IDs, see:
Result query (74)
Order and result queries with limited sample lifetime (81).
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.
u For details of sequence numbers, see Identifying patient samples by
sequence number (455).
QPD-4 String O - Selection mode
12 HL7 text content

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.
y Query parameter segment - QPD - for result query

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Query Parameter Segment - QPD (for a Result Query) 285

Field Comp. Value Host DM Description

QPD-10 String O/R - Rack type as assigned to a specific sample type on the cobas® 8000
modular analyzer series instrument.
This field is optional only if there is only one sample with the sample ID. If
there is a sample in the database with the same sample ID but a different
rack type, or an expired sample ID, this field is mandatory. It is
recommended to always include it.
The data manager returns results for whichever unique current sample
matches the combination of sample ID and rack type, if given. If there is
no current sample, no answer is sent.
u For details of sample ID lifetimes, see Reusing sample IDs and sample
lifetimes (48).
u For details of using result and order queries with limited sample
lifetimes or expired sample IDs, see:
Result query (74)
Order and result queries with limited sample lifetime (81).
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 Hemolysate (only supported by e 801 module)
S9 Amniotic fluid (only supported by e 801 module)
SA Processed stool (only supported by e 801 module)
S0 No specimen assigned (only used for messages from data
manager).
Subsequent fields contain no data.
y Query parameter segment - QPD - for result query

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 286 Query Parameter Segment - QPD (for an Order Query)

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||||||S1

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.
The data manager returns order details for whichever unique current
sample matches the combination of sample ID and rack type, if given. If
there is no current sample, an empty test selection is sent.
u For details of sample ID lifetimes, see Reusing sample IDs and sample
lifetimes (48).
u For details of using result and order queries with limited sample
lifetimes or expired sample IDs, see:
Order query (75)
Order and result queries with limited sample lifetime (81).
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.
u For details of sequence numbers, see Identifying patient samples by
sequence number (455).
QPD-4 String O - Selection mode
12 HL7 text content

o (empty)
All requested tests
o O (Capital O): Open. (Only test selections with no results yet)
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.
y Query parameter segment - QPD - for an order query

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Query Parameter Segment - QPD (for an Order Query) 287

Field Value Host DM Description

QPD-10 String R - Rack type as assigned to a specific sample type on the cobas® 8000
modular analyzer series.
The data manager returns order details for whichever unique current
sample matches the combination of sample ID and rack type, if given. If
there is no current sample, an empty test selection is sent.
u For details of sample ID lifetimes, see Reusing sample IDs and sample
lifetimes (48).
u For details of using result and order queries with limited sample
lifetimes or expired sample IDs, see:
Result query (74)
Order and result queries with limited sample lifetime (81).
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 Hemolysate (only supported by e 801 module)
S9 Amniotic fluid (only supported by e 801 module)
SA Processed stool (only supported by e 801 module)
S0 No specimen assigned (only used for messages from data
manager).
Subsequent fields contain no data.
y Query parameter segment - QPD - for an order query

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 288 Response Control Parameter Segment - RCP

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 .
y Response control parameter segment - RCP
12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Equipment Detail Segment - EQU (from host to data manager) 289

Equipment Detail Segment - EQU (from

host to data manager)
The host uses the Equipment Detail Segment to instruct
the data manager to apply the instructions in the
following ECD segments, in a masking message.

EQU|1|20160402173655|

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.
y Equipment detail segment - EQU

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 290 Equipment Command Segment - ECD

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^MaskType^Unit_ID^ALL
ECD-5.1 String 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).
For cobas e flow tests, only patient masking is available.
ECD-5.3 String R - Unit_ID This is the user-editable identifier for the instrument and
module.
u For details, see Identifier of the analytical unit sent to
host (108).
For cobas e flow tests, the data manager ignores any value
in this field, and masks the test on all e 801 sub-modules..
ECD-5.4 ALL R - Hard-coded to ALL .
y Equipment command segment - ECD
12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Equipment Detail Segment - EQU (from data manager to host) 291

Equipment Detail Segment - EQU (from

data manager to host)
The data manager uses the Equipment Detail Segment to
tell the host the current instrument status and the
date/time of a masking or unmasking request.

EQU|DM#DM#0#0|20140630123849|PU^POWERED_UP^LECIS^1^Power up^Hitachi|

EQU|DM#DM#1#2|20140405091052|OP^NORMAL_OPERATION^LECIS^7^Operation^Hitachi|

EQU|DM#DM#1#2|20140217075453|ES^E-STOPPED^LECIS^21^Shutdown^Hitachi|

Field Value Host DM Description

EQU-1 String - R Identifier for the equipment. Takes the format:
Instrument#ModuleType#Position#SubModule
EQU-2 Datetime - R The date and time that the masking or unmasking request is sent.
EQU-3 Complex - R/O Instrument status. Contains a state value defined by the HL7 protocol, and an
additional state value defined by the instrument.
State value^State description^Coding system^Instrument
state^Instrument state description^Instrument coding
system
Required for ESU messages, optional for all others.
EQU-3.1 String - State value Instrument state value. Values in this field are defined by
the HL7 protocol and based on LECIS.
Possible values are:
o PU Powered up
o IN Initializing
o ID Idle
o CO Configuring
o OP Normal operation
o CL Clearing
o PA Pausing
o PD Paused
o ES E-stopped
EQU-3.2 String - State Description of current instrument state.
description
EQU-3.3 LECIS - Coding State value coding system. Fixed value.
system
EQU-3.4 String - Instrument Instrument-defined state value.
12 HL7 text content
state u For a complete list of instrument-defined state values,
see Instrument-defined states (291)
EQU-3.5 String - Instrument Description of instrument-defined state value.
state u For a complete list of instrument-defined state values,
description
see Instrument-defined states (291)
EQU-3.6 Hitachi - Instrument Coding system of instrument-defined state value. Fixed
coding value.
system
y Equipment detail segment - EQU

Instrument-defined states Below are listed all possible instrument-defined state

values (EQU-3.4), with the equivalent official HL7 state
values (based on LECIS), and the corresponding
instrument-defined state descriptions (EQU-3.5).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 292 Equipment Detail Segment - EQU (from data manager to host)

Instrument state (EQU-3.4) HL7 (LECIS) state value Instrument state description (EQU-3.5)
1 PU Power up
2 IN Initialize
3 ID Stand by
4 ID Stop
5 ES Emergency stop
6 IN Preparation
7 OP Operation
8 ID Rack supply complete
9 ID Rack collection complete (restart disabled)
10 ID Rack supply complete (restart disabled)
11 ID Rack collection complete (restart disabled)
12 ID Line stop
13 ID S.Stop
14 ID TM with rack supply
15 ID TM without rack supply
16 ID Reagent registration
17 ID Pipe
18 IN Powerup pipe
19 IN Startup pipe
20 ID Reconnection
21 DO Shutdown
22 ID Pipe interrupted
26 OP Rack Reception
27 OP Operation(CLAS)
28 OP Backup Operation
29 IN Start
30 ID Post Operation
31 Conditional
y Instrument-defined state and state description values
12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Inventory Detail Segment - INV 293

Inventory Detail Segment - INV

The data manager uses the Inventory Detail Segment to
communicate the availability of a test or
cobas e flow test to the host. Within an equipment
inventory update message, an INV segment is sent for
each test installed on the data manager.

INV|18571|OK^OK_STATUS|

INV|8707|NW^NOT_AVAILABLE_WARNING|

INV|8433|OK^OK_STATUS|

Field Value Host DM Description

INV-1 String - R Test code. Identifies the test or analyte this segment relates to.
INV-2 Complex - R Test status. Specifies whether the test is masked (unavailable) or unmasked
(available). In the case of cobas e flow tests, an embedded test can also be flagged
as unavailable if it is not installed.
Takes the following format:
Value^Description
Can contain the following values:
o NW^NOT_AVAILABLE_WARNING
o OK^OK_STATUS
y Inventory detail segment - INV

12 HL7 text content

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 294
12 HL7 text content Inventory Detail Segment - INV

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 295
Table of contents

HL7 acknowledgment handling 13

This chapter explains how cobas® 8000 data manager

handles HL7 acknowledgment messages.

In this chapter 13
Acknowledgment flags in messages from the data
manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Inquiry for test selections . . . . . . . . . . . . . . . . . . . . 298
Result report patient. . . . . . . . . . . . . . . . . . . . . . . . . 298
Result report quality control . . . . . . . . . . . . . . . . . . 299
Result report calibration data . . . . . . . . . . . . . . . . . 300
Test selection upload from data manager to host 300

13 HL7 acknowledgment handling

Acknowledgment message from data manager
to host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Acknowledgment flags sent in response to host
messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Result query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Order query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Test selection download . . . . . . . . . . . . . . . . . . . . . 303
Acknowledgment message . . . . . . . . . . . . . . . . . . . 304

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 296
Table of contents
13 HL7 acknowledgment handling

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Acknowledgment flags in messages from the data manager 297

Acknowledgment flags in messages from

the data manager
HL7 messages send a flag instructing the receiver under
what conditions to send an acknowledgment. You can
define which flag the data manager sends. This setting
applies to the flag sent in the following messages:
• Result upload messages (patient, QC, or calibration)
and
• Test selection uploads.

This is configured in Workplaces > cobas 8000 data

manager Service > Service-related configuration
> Interface options.
u For details of how to configure the application
acknowledge level of the data manager, see HL7
acknowledgment handling settings (102).

The code in MSH-16 instructs the receiver whether to

send an application acknowledgment reply.

MSH|^~\&|cobas 8000||host||20170713095453||OUL^R22|132302||2.5||||ER||UNICODE UTF-8|

PID|1||||^||||
SPM||1096||S1||not|||||P|||^?^^^?|||20170712152629|||||||||||
...

Four levels of acknowledgment are supported, as

13 HL7 acknowledgment handling

described below.

MSH- Meaning Required host response Timeout (for patient and QC results)
16 Code
AL Always Send an acknowledgment 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
acknowledgment 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
acknowledgment. "Pending" in data manager until acknowledgment
received or timeout.
ER Error If message processed, send no acknowledgment. The data manager assumes success, unless it
If message cannot be processed, send Error (AE). receives an Error (AE) or Reject (AR) at any time
before the uploaded message is deleted.
NE Never Never send an acknowledgment. The data manager expects no response.
y Codes for level of application acknowledgment, sent in MSH-16

For acknowledgment message, the level of application

acknowledgment is set to Never (NE).

For other messages from the data manager (inquiry for

test selections or test selection upload), the level of
application acknowledgment is set to Error (ER).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 298 Acknowledgment flags in messages from the data manager

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.

Inquiry for test selections

The data manager always sends an Error (ER) code in
response to an inquiry for a test selection.

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

16: AA (Accept) AE (Error) AR (Reject) no response
Always (AL) Not sent
Success (SU) Not sent
Error (ER) ER always sent.
Never (NE) Not sent
y Acknowledgment codes responding to a test selection inquiry

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.
13 HL7 acknowledgment handling

Result report patient

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

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

16: 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 Not allowed Not allowed After timeout, the
marks the results in data manager marks
Upload Status as the results in Upload
“Sent”. Status as “Failed”.
Error (ER) Not 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) Not allowed Not allowed Not allowed The data manager
marks the results in
Upload Status as
“Sent”.
y Acknowledgment codes responding to a patient result report

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Acknowledgment flags in messages from the data manager 299

If the host sends an Error (AE) or Reject (AR) response, or

the message times out:
• the data manager reports an error in Service
> System message.
• the data manager writes an error to logs in System
Configuration > Log files.
• the data manager writes an error to logs in Routine
> System alarms.
• the data manager marks the results in “Upload status”
as “Failed”.

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- The host returns in MSA-1

16: 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
“Sent”. “Failed”. “Failed”. Upload Status as
“Failed”.
Success (SU) The data manager Not allowed Not allowed After timeout, the
marks the results in data manager marks
Upload Status as the results in
“Sent”. Upload Status as

13 HL7 acknowledgment handling

“Failed”.
Error (ER) Not 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) Not allowed Not allowed Not allowed The data manager
marks the results in
Upload Status as
“Sent”.
y Acknowledgment codes responding to a quality control result report

If the host sends an Error (AE) or Reject (AR) response, or

the message times out:
• the data manager reports an error in Service
> System message.
• the data manager writes an error to logs in System
Configuration > Log files.
• the data manager writes an error to logs in Routine
> System alarms.
• the data manager marks the results in “Upload status”
as “Failed”.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 300 Acknowledgment flags in messages from the data manager

Result report calibration data

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

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

16: 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 Not allowed Not allowed After timeout, error
sent successfully. logged in data
manager.
Error (ER) Not allowed Error logged in data Error logged in data Message considered
manager. manager. sent successfully.
Never (NE) Not allowed Not allowed Not allowed Message considered
sent successfully.
y Acknowledgment codes responding to a calibration result report

If the host sends an Error (AE) or Reject (AR) response, or

the message times out:
• the data manager reports an error in Service
> System message.
• the data manager writes an error to logs in System
Configuration > Log files.
• the data manager writes an error to logs in Routine
> System alarms.
13 HL7 acknowledgment handling

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- The host returns in MSA-1

16: 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 Not allowed Not allowed After timeout, error
sent successfully. logged in data
manager.
Error (ER) Not allowed Error logged in data Error logged in data Message considered
manager. manager. sent successfully.
Never (NE) Not allowed Not allowed Not allowed Message considered
sent successfully.
y Acknowledgment codes responding to a test selection upload

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Acknowledgment flags in messages from the data manager 301

If the host sends an Error (AE) or Reject (AR) response, or

the message times out:
• the data manager reports an error in Service
> System message.
• the data manager writes an error to logs in System
Configuration > Log files.
• the data manager writes an error to logs in Routine
> System alarms.

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.

Acknowledgment message from data manager to host

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

13 HL7 acknowledgment handling

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 302 Acknowledgment flags sent in response to host messages

Acknowledgment flags sent in response to

host messages
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

acknowledgment code NE .

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
13 HL7 acknowledgment handling

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

acknowledgment code NE .

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.
u For an example, see In this section the host sends a
request for open tests for a sample, but the data
manager does not find any tests. Note that rack type is
required in QPD-10. (355).

If the data manager receives a test selection from the host

which does not have a valid application number, it sends
an acknowledgment message if requested:

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Acknowledgment flags sent in response to host messages 303

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) Not sent Indicates a Not sent Not sent
validation error.
Success (SU) Not sent Not sent Not sent Indicates a validation
error.
Error (ER) Not sent Indicates a Not sent Not sent
validation error.
Never (NE) Not sent Not sent Not sent Indicates a validation
error.
y Acknowledgment codes sent in response to an invalid test selection

Masking
In reply to a masking or unmasking request, the data
manager sends an acknowledgment 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

13 HL7 acknowledgment handling

segment.
Never (NE) Not sent Not sent Not sent Supported.
y Acknowledgment codes sent in response to a masking command

Test selection download

In reply to a test selection download, the data manager
sends an acknowledgment 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.
y Acknowledgment codes sent in response to a test selection download

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 304 Acknowledgment flags sent in response to host messages

Acknowledgment message
The data manager never replies to an acknowledgment
message.
13 HL7 acknowledgment handling

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 305
Table of contents

HL7 communication examples 14

This chapter presents some examples of HL7 messages

generated by cobas® 8000 data manager, and a
connected host system (LIS / WAM). These examples
show the precise content of the messages sent, including
the control characters.

In this chapter 14
Test selection inquiry and download . . . . . . . . . . . . . . 307
Test selection inquiry for routine rack . . . . . . . . . . 307
Test selection inquiry for STAT rack . . . . . . . . . . . . 307
Routine rack (AL) with acknowledgment . . . . . . . 308
Routine rack invalid test (ER) . . . . . . . . . . . . . . . . . 308

14 HL7 communication examples

Test selection inquiry no sample found . . . . . . . . . 308
Test selection inquiry with a sequence number . . 309
Regular test patient result upload messages . . . . . . . 310
Single patient result upload . . . . . . . . . . . . . . . . . . 310
Batch upload all previous results . . . . . . . . . . . . . . 310
Batch upload all current results . . . . . . . . . . . . . . . 311
Batch upload of current results sample short . . . 312
Result outside user range . . . . . . . . . . . . . . . . . . . . 312
Result outside normal range . . . . . . . . . . . . . . . . . . 312
Quantitative test result . . . . . . . . . . . . . . . . . . . . . . . 313
e 602 result message with data point values . . . . 313
cobas e flow test result upload messages. . . . . . . . . 315
cobas e flow test EP17-A messages with flags . . 315
cobas e flow test result with EP17-A data alarm 319
Sample with multiple cobas e flow tests and
embedded tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
cobas e flow test with qualitative and
quantitative result . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
cobas e flow test with generated subresult. . . . . 324
cobas e flow test with non-reported embedded
tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
cobas e flow test with data alarms and non-
reported embedded tests . . . . . . . . . . . . . . . . . . . . 328

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 306
Table of contents

cobas e flow test result with custom host codes 329

cobas e flow test result message with raw data
and data points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Qualitative and cut-off index result messages . . . . . . 336
Qualitative/cut-off index result for regular test . . 336
Qualitative/cut-off index result for
cobas e flow test . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Embedded test result with qualitative result in
cobas e flow test . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Quality control result upload messages . . . . . . . . . . . 339
Realtime QC from c-module . . . . . . . . . . . . . . . . . . 339
Realtime QC from c-module standby bottle . . . . . 339
Batch QC from c-module. . . . . . . . . . . . . . . . . . . . . 340
Batch QC from c-module standby bottle. . . . . . . . 340
QC results from e-module . . . . . . . . . . . . . . . . . . . . 341
Symmetric quality control result message . . . . . . 341
Asymmetric quality control result message . . . . . 342
cobas e flow test calculated QC result messages . . 344
Calculated QC result message . . . . . . . . . . . . . . . . 344
Calculated QC result flagged with generic alarm 345
Calculated QC result with raw data . . . . . . . . . . . . 345
Calibration result upload messages. . . . . . . . . . . . . . . 347
C-module calibration result. . . . . . . . . . . . . . . . . . . 347
ISE-module calibration result . . . . . . . . . . . . . . . . . 347
E-module calibration results . . . . . . . . . . . . . . . . . . 348
Masking messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Result requests from the host. . . . . . . . . . . . . . . . . . . . 350
14 HL7 communication examples

Request for all results . . . . . . . . . . . . . . . . . . . . . . . 350

Request for final results. . . . . . . . . . . . . . . . . . . . . . 351
No results found . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Sample not found . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Result request with a sequence number. . . . . . . . 352
Result request with an expired sample . . . . . . . . . 353
Order requests from the host . . . . . . . . . . . . . . . . . . . . 354
Request for all tests . . . . . . . . . . . . . . . . . . . . . . . . . 354
Request for open tests. . . . . . . . . . . . . . . . . . . . . . . 354
No tests found. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Sample not found . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Order request with a sequence number . . . . . . . . 355
Instrument status and test availability messages . . . . 357
Test availability request . . . . . . . . . . . . . . . . . . . . . . 357
Test availability update . . . . . . . . . . . . . . . . . . . . . . . 357
Instrument status request . . . . . . . . . . . . . . . . . . . . 359
Instrument status update. . . . . . . . . . . . . . . . . . . . . 359

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Test selection inquiry and download 307

Test selection inquiry and download

In the examples in this section, the data manager sends
HL7 test selection requests, and the host replies with test
selection downloads.

In this section
Test selection inquiry for routine rack (307)
Test selection inquiry for STAT rack (307)
Routine rack (AL) with acknowledgment (308)
Routine rack invalid test (ER) (308)
Test selection inquiry no sample found (308)
Test selection inquiry with a sequence number (309)

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||20171124091510||TSREQ|2747||2.5||||ER||UNICODE UTF-8|
QPD|TSREQ|2747|400172||50690|2||||S1|SC|R1|R|
RCP|I|1|R|

Host:
MSH|^~\&|host||cobas 8000||20171124091431||OML^O33|6259||2.5||||NE||8859/1

14 HL7 communication examples

PID|1|PatID1|||Doe^John||19651125|M
SPM||400172||S1||not|||||P|||^^^^|||||||||||||
SAC||||||||||50690|2
TQ1|1||||||||R
OBR|4|||8717^Inc|||||||A

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||20171124091510||TSREQ|2747||2.5||||ER||UNICODE UTF-8|
QPD|TSREQ|2747|400172||50690|2||||S1|SC|R1|S|
RCP|I|1|R|

Host:
MSH|^~\&|host||cobas 8000||20171124091431||OML^O33|6259||2.5||||NE||8859/1
PID|1|PatID1|||Doe^John||19651125|M
SPM||400172||S1||not|||||P|||^^^^|||||||||||||
SAC||||||||||50690|2
TQ1|1||||||||R
OBR|4|||8717^Inc|||||||A

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 308 Test selection inquiry and download

Routine rack (AL) with acknowledgment

This section shows an example of an HL7 test selection
inquiry for a routine sample, with the test selection
download. The host requests an acknowledgment (level
AL) and the data manager replies.

Host:
MSH|^~\&|host||cobas 8000||20171124091431||OML^O33|6259||2.5||||AL||8859/1
PID|1|PatID1|||Doe^John||19651125|M
SPM||400172||S1||not|||||P|||^^^^|||||||||||||
SAC||||||||||50690|2
TQ1|1||||||||R
OBR|4|||8717^Inc|||||||A

DM:
MSH|^~\&|cobas 8000||host||20171124091433||ACK|8260||2.5||||NE||UNICODE UTF-8|
MSA|AA|6259||

Routine rack invalid test (ER)

This section shows an example of a host’s test selection
download. In this test selection download there is an
invalid ACN, and the data manager replies with an
acknowledgment that informs the host of the error.

Host:
MSH|^~\&|host||cobas 8000||20170508135730||OML^O33|38777||2.5||||ER||UNICODE UTF-8
14 HL7 communication examples

PID|1|PatID1|||Doe^John||19651125|M
SPM||321070||S1||not||||||||^^^^|||20171020122000||||||||||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|||(INVALID ACN)^Inc|||||||A

DM:
MSH|^~\&|cobas 8000||host||20101020132233||ACK|15834||2.5||||NE||UNICODE UTF-8|
MSA|AE|38777|ORA-20001: Validation error|

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||20171020091052||TSREQ|15167||2.5||||ER||UNICODE UTF-8|
QPD|TSREQ|15167|321071||50094|3||||S1|SC|R1|R|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Test selection inquiry and download 309

RCP|I|1|R|

Host:
MSH|^~\&|host||cobas 8000||20171020091055||OML^O33|38749||2.5||||ER||UNICODE UTF-8
PID|1|PatID1|||Doe^John||19651125|M
SPM||321071||S1|
SAC||||||||||50094|3

! CAUTION
Send patient demographic data if sample found with
no tests ordered
r Take care in the situation where the data manager
sends a test selection query, but the 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.
r In this case, the host should send a normal test
selection download, with full patient information, and
comments etc., but no testcodes.
u For examples of normal test selections, see Routine test
selection inquiry and download (204) and STAT sample
test selection inquiry and download (204).

14 HL7 communication examples

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. (See fields QPD-3.2 and SPM-2.2.) This
functionality was introduced in version 1.02.03.

DM:
MSH|^~\&|cobas 8000||host||20170720154106||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||cobas 8000||20170715081133||OML^O33|227442||2.5||||ER||UNICODE UTF-8
PID|1|PatID1|||Doe^John||19651125|M
SPM||^1031||S1||not|||||P|||^^^^|||20170715085411||||||||||SC
SAC||||||||||50203|3
TQ1|1||||||||R
OBR|1|||8571^|||||||A
TQ1|1||||||||R
OBR|2|||8413^|||||||A
TQ1|1||||||||R
OBR|3|||8706^|||||||A

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 310 Regular test patient result upload messages

Regular test patient result upload

messages
In the examples in this section the data manager uploads
HL7 patient results.

In this section
Single patient result upload (310)
Batch upload all previous results (310)
Batch upload all current results (311)
Batch upload of current results sample short (312)
Result outside user range (312)
Result outside normal range (312)
Quantitative test result (313)
e 602 result message with data point values (313)

Single patient result upload

This section shows an example of a single HL7 patient
result upload.

MSH|^~\&|cobas 8000^1.06||host||20171019101825||OUL^R22|13890||2.5||||ER||UNICODE UTF-8|

PID|1||||^||||
SPM||321042||S1||not|||||P|||^^^^|||20171019094904||||||||||SC|
14 HL7 communication examples

SAC||||||||||50011|4|
OBR|1|||8685|
TQ1|1||||||||R|
OBX|1||8685||47|U/L|^TECH~^NORM~^CRIT~^USER||||F|||20171019100810|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|

Batch upload all previous results

This section shows a batch upload of all previous results
for a sample.

MSH|^~\&|cobas 8000^1.06||host||20171020111635||OUL^R22^BATCH|15593||2.5||||ER||UNICODE UTF-8|

PID|1|PatID1|||Doe^John||19651125|M|
SPM||321015||S1||not|||||P|||^^^^|||20101019174209||||||||||SC|
SAC||||||||||50071|1|
OBR|1|||990|
TQ1|1||||||||R|
OBX|1||990||0.91|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||F|||20171019174423|bmserv^SYSTEM||128|ISE^2^MU
1#ISE#1#2^4|20171019174439|
TCD|990|1|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Regular test patient result upload messages 311

NTE|1|I||I|
OBR|2|||990|
TQ1|1||||||||R|
OBX|1||990||0.70|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||20171019174459|bmserv^SYSTEM||125|ISE^1^MU
1#ISE#1#1^3|20171019174515|
TCD|990|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|3|||990|
TQ1|1||||||||R|
OBX|1||990||0.75|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||F|||20171020095735|bmserv^SYSTEM||125|ISE^1^MU
1#ISE#1#1^3|20171020095751|
TCD|990|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|4|||990|
TQ1|1||||||||R|
OBX|1||990||0.99|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||20171020095905|bmserv^SYSTEM||128|ISE^2^MU
1#ISE#1#2^4|20171020095921|
TCD|990|1|
NTE|1|I|23^ISE Sample range over|I|

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.06||host||20171020111632||OUL^R22^BATCH|15591||2.5||||ER||UNICODE UTF-8|

PID|1|PatID1|||Doe^John||19651125|M|

14 HL7 communication examples

SPM||321015||S1||not|||||P|||^^^^|||20171019174209||||||||||SC|
SAC||||||||||50071|1|
OBR|1|||990|
TQ1|1||||||||R|
OBX|1||990||0.99|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||20171020095905|bmserv^SYSTEM||128|ISE^2^MU
1#ISE#1#2^4|20171020095921|
TCD|990|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|2|||991|
TQ1|1||||||||R|
OBX|1||991||304.89|mmol/L|^TECH~^NORM~^CRIT~< 0^USER||||C|||20171020095905|bmserv^SYSTEM||129|ISE^2^
MU1#ISE#1#2^4|20171020095921|
TCD|991|1|
NTE|1|I|23^ISE Sample range over|I|
OBR|3|||8717|
TQ1|1||||||||R|
OBX|1||8717||-0.02|mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20171019175614|bmserv^SYSTEM||77|c701^1^MU1
#c701#1#1^6|20171019180627|
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|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 312 Regular test patient result upload messages

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||20171018174529||OUL^R22|12636||2.5||||ER||UNICODE UTF-8|

PID|1|PatID1|||Doe^John||19651125|M
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^MU
1#ISE#1#1^3|20101018173829|
TCD|989|1|
NTE|1|I|3^Sample short|I|
OBR|2|||990|
TQ1|1||||||||R|
OBX|1||990|| |mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20101018173814|bmserv^SYSTEM||125|ISE^1^MU
1#ISE#1#1^3|20101018173829|
TCD|990|1|
NTE|1|I|3^Sample short|I|
OBR|3|||991|
TQ1|1||||||||R|
OBX|1||991|| |mmol/L|^TECH~^NORM~^CRIT~^USER||||C|||20101018173814|bmserv^SYSTEM||126|ISE^1^MU
1#ISE#1#1^3|20101018173829|
TCD|991|1|
NTE|1|I|3^Sample short|I|

Result outside user range

14 HL7 communication examples

This section shows an example of an HL7 patient result

outside the user-defined reference range.

MSH|^~\&|cobas 8000||host||20180110121130||OUL^R22|9921||2.5||||SU||UNICODE UTF-8|

PID|1||||^||||
SPM||100548||S1||not|||||P|||^^^^|||20180110120633||||||||||SC|
SAC||||||||||50210|4|
OBR|1|||989|
TQ1|1||||||||R|
OBX|1||989||9.3|mmol/L|^TECH~^NORM~^CRIT~10 - 20^USER||||F|||20180110121111|bmserv^SYSTEM||46|ISE^1^
MU1#ISE#1#1^3|20180110121127|
TCD|989|1|
NTE|1|I|23^ISE Sample range over|I|

Result outside normal range

This section shows an example of an HL7 result upload
below the normal reference range.

MSH|^~\&|cobas 8000||host||20180110121135||OUL^R22|9924||2.5||||SU||UNICODE UTF-8|

PID|1||||^||||

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Regular test patient result upload messages 313

SPM||100549||S1||not|||||P|||^^^^|||20180110120657||||||||||SC|
SAC||||||||||50210|5|
OBR|1|||990|
TQ1|1||||||||R|
OBX|1||990||0.24|mmol/L|^TECH~20 - 30^NORM~^CRIT~^USER|L|||F|||20180110121117|bmserv^SYSTEM||50|ISE^
2^MU1#ISE#1#2^4|20180110121133|
TCD|990|1|
NTE|1|I|23^ISE Sample range over|I|

Quantitative test result

This section shows an example of an HL7 patient result
with a quantitative test result.

MSH|^~\&|cobas 8000||host||20170106152338||OUL^R22|150385||2.5||||ER||UNICODE UTF-8|

PID|1||||^||||
SPM||81004||S1||not|||||P|||^^^^|||20170106152324||||||||||SC|
SAC|||||||||||0|
OBR|1|||24|
TQ1|1||||||||R|
OBX|1||24||0.760|nmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20170106152333|bmserv^SYSTEM||24|e602^1^MU1#e
602#3#1^11|20170106152333|
TCD|24|1|
NTE|1|I|0|I|

e 602 result message with data point values

14 HL7 communication examples

This section shows an example of an HL7 patient result
message with data point values, generated by an e 602
module.

The control unit sends data point values to the data

manager only when they are explicitly requested by the
user (for example, for troubleshooting or research
purposes).
u For an example of a cobas e flow test result message
with raw data and data point values, see
cobas e flow test result message with raw data and
data points (333).

MSH|^~\&|cobas 8000||host||20170725105415||OUL^R22|237||2.5||||ER||UNICODE UTF-8|

PID|1||||^||||
SPM||234031||S1||not|||||P|||^^^^|||20170707093721|||||||||||
SAC||||||||||50089|5|
OBR|1|||64|
TQ1|1||||||||R|
OBX|1||64||3.50|IU/L|^TECH~^NORM~^CRIT~^USER||||F|||20170707092617|bmserv^SYSTEM||0|e602^2^MU1#e602#
3#2^12|20170707092617|
TCD|64|1|
SID|64^^64^ASY^4^0|175377|60703|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 314 Regular test patient result upload messages

OBR|2|||64|
TQ1|1||||||||R|
OBX|1||64||1315^8427&8428&8435&8497&8504&8537&8604&8641&8680&8683&8650&8671&8653&8654&8681&8685&8729
&8794&8803&8834&8878&8880&8908&8912&8943&8939&8973&8965&8955&8964&8929&8926&8935&8938&8945&8964&8949
&9029&9008&9008&8992&8983&8997&9027&9025&9064&9047&9018&9099&9117&9071&9020&9046&9074&9067&9058&9065
&9053&9087&9053&9047&9016&9040&9015&9017&9001&9069&9084&9094&9126&9166&9127&9170&9170&9202&9216&9178
&9167&9184&9170&9241&10506&13668&17183&20213&22113&22997&22950&23041&23148&22863&22863&22635&22550&2
2661&22446&22387&22299&22260&22176&22092&21966&22012&21868&21855&21813&21757&21821&21846&21516&21535
&21651&21455&21439&21363&21436&21340&21303&21325&21432&21215&21271&21207&21094&21070&21148&21113&212
47&21186&21112&21069&21006&20992&20932&20833&20823&20714&20937&20854&20747&20723&20734&20699&20750&2
0928&20744&20704&20715&20654&20605&20639&20718&20455&20480&20411&20390&20578&20554&20572&20653&20535
&20437&20473&20466&20324&20366&20376&20341&20546&20493&20565&20627&20508&20496&20589&20543&20503&204
68&20414&20299&20151&20230&20301&20301&20243&20277&20306&20206&20242&20130&20121&20133&20169&20069&2
0002&20195&20116&20116&20026&20079|count|^TECH~^NORM~^CRIT~^USER||||F|||20140707092617|^||EFS|e602^2
^MU1#e602#3#2^12|20140707092617|
TCD|64|1|
NTE|1|I|0|I|
14 HL7 communication examples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 315

cobas e flow test result upload messages

In the examples in this section the data manager uploads
HL7 patient results for cobas e flow tests.

In this section
cobas e flow test EP17-A messages with flags (315)
cobas e flow test result with EP17-A data alarm (319)
Sample with multiple cobas e flow tests and embedded
tests (320)
cobas e flow test with qualitative and quantitative
result (322)
cobas e flow test with generated subresult (324)
cobas e flow test with non-reported embedded
tests (327)
cobas e flow test with data alarms and non-reported
embedded tests (328)
cobas e flow test result with custom host codes (329)
cobas e flow test result message with raw data and data
points (333)

cobas e flow test EP17-A messages with flags

For EP17-A range checking in cobas e flow test results,
two additional flags have been defined, which are sent in

14 HL7 communication examples

the OBX-8 segment:
• HU (High Uncertainty)
• eFlow.W (generic cobas e flow test warning)

HL7 message with HU flag

MSH|^~\&|cobas 8000||host||20180111111104||OUL^R22|2183||2.5||||ER||UNICODE UTF-8|
PID|1|PatID1|||Doe^John||19651125|M|
SPM||page_335_01||S1||not|||||P|||^^^^|||20140210085411||||||||||SC|
SAC||||||||||50001|1|
OBR|1|||30200|
TQ1|1||||||||R|
OBX|1||30200||55.0|mg/L|^TECH~^NORM~^CRIT~^USER|HU|||F|||20180111111100|bmserv^SYSTEM||805|e801^2^MU
1#e801#3#2^9|20180111111103|
TCD|30200|1|
NTE|1|I|0|I|
OBX|2||30200||87112|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111100|bmserv^SYSTEM||EFS|e801^2^MU
1#e801#3#2^9|20180111111103|
TCD|30200|1|
NTE|1|I|0|I|
OBX|3||30200||45542|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111100|bmserv^SYSTEM||EFV|e801^2^MU
1#e801#3#2^9|20180111111103|
TCD|30200|1|
NTE|1|I|0|I|
OBX|4||30200||252|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111100|bmserv^SYSTEM||EFC|e801^2^MU1#
e801#3#2^9|20180111111103|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 316 cobas e flow test result upload messages

TCD|30200|1|
NTE|1|I|0|I|
OBX|5||30200||1001|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111100|bmserv^SYSTEM||PMT|e801^2^MU1
#e801#3#2^9|20180111111103|
TCD|30200|1|
NTE|1|I|0|I|
OBX|6||12002||55.0|mg/L|^TECH~^NORM~^CRIT~^USER|HU|||V|||20180111111100|bmserv^SYSTEM||805|e801^2^MU
1#e801#3#2^9|20180111111103|
TCD|12002|1|
SID|12002^^1312002^ASY^32^0|188548|32|
NTE|1|I|0|I|
OBX|7||12002||87112|count|^TECH~^NORM~^CRIT~^USER||||V|||20180111111100|bmserv^SYSTEM||EFS|e801^2^MU
1#e801#3#2^9|20180111111103|
TCD|12002|1|
NTE|1|I|0|I|
OBX|8||12002||45542|count|^TECH~^NORM~^CRIT~^USER||||V|||20180111111100|bmserv^SYSTEM||EFV|e801^2^MU
1#e801#3#2^9|20180111111103|
TCD|12002|1|
NTE|1|I|0|I|
OBX|9||12002||252|count|^TECH~^NORM~^CRIT~^USER||||V|||20180111111100|bmserv^SYSTEM||EFC|e801^2^MU1#
e801#3#2^9|20180111111103|
TCD|12002|1|
NTE|1|I|0|I|
OBX|10||12002||1001|count|^TECH~^NORM~^CRIT~^USER||||V|||20180111111100|bmserv^SYSTEM||PMT|e801^2^MU
1#e801#3#2^9|20180111111103|
TCD|12002|1|
NTE|1|I|0|I|
OBX|11||assignQual||1||^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20180111111104|
TCD|assignQual|1|
NTE|1|I|0|I|
OBX|12||12001|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20180111111059|bmserv^SYSTEM||805|
e801^1^MU1#e801#3#1^8|20180111111102|
14 HL7 communication examples

TCD|12001|1|
SID|12001^^1312001^ASY^32^0|188548|32|
NTE|1|I|0|I|
OBX|13||12001||87112|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111059|bmserv^SYSTEM||EFS|e801^1^M
U1#e801#3#1^8|20180111111102|
TCD|12001|1|
NTE|1|I|0|I|
OBX|14||12001||45542|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111059|bmserv^SYSTEM||EFV|e801^1^M
U1#e801#3#1^8|20180111111102|
TCD|12001|1|
NTE|1|I|0|I|
OBX|15||12001||252|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111059|bmserv^SYSTEM||EFC|e801^1^MU1
#e801#3#1^8|20180111111102|
TCD|12001|1|
NTE|1|I|0|I|
OBX|16||12001||1001|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111059|bmserv^SYSTEM||PMT|e801^1^MU
1#e801#3#1^8|20180111111102|
TCD|12001|1|
NTE|1|I|0|I|
OBX|17||12003|| ^ |μg/L|^TECH~^NORM~^CRIT~^USER||||F|||20180111111101|bmserv^SYSTEM||805
|e801^2^MU1#e801#3#2^9|20180111111104|
TCD|12003|1|
SID|12003^^1312003^ASY^32^0|188548|32|
NTE|1|I|0|I|
OBX|18||12003||87112|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111101|bmserv^SYSTEM||EFS|e801^2^M
U1#e801#3#2^9|20180111111104|
TCD|12003|1|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 317

NTE|1|I|0|I|
OBX|19||12003||45542|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111101|bmserv^SYSTEM||EFV|e801^2^M
U1#e801#3#2^9|20180111111104|
TCD|12003|1|
NTE|1|I|0|I|
OBX|20||12003||252|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111101|bmserv^SYSTEM||EFC|e801^2^MU1
#e801#3#2^9|20180111111104|
TCD|12003|1|
NTE|1|I|0|I|
OBX|21||12003||1001|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111101|bmserv^SYSTEM||PMT|e801^2^MU
1#e801#3#2^9|20180111111104|
TCD|12003|1|
NTE|1|I|0|I|

HL7 message with generic warning

MSH|^~\&|cobas 8000||host||20180111111110||OUL^R22|2188||2.5||||ER||UNICODE UTF-8|
PID|1|PatID1|||Doe^John||19651125|M|
SPM||page_335_02||S1||not|||||P|||^^^^|||20140210085411||||||||||SC|
SAC||||||||||50001|1|
OBR|1|||30200|
TQ1|1||||||||R|
OBX|1||30200||59.5|mg/L|^TECH~^NORM~^CRIT~^USER|eFlow.W|||F|||20180111111106|bmserv^SYSTEM||805|e801
^2^MU1#e801#3#2^9|20180111111109|
TCD|30200|1|
NTE|1|I|0|I|
OBX|2||30200||87112|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111106|bmserv^SYSTEM||EFS|e801^2^MU
1#e801#3#2^9|20180111111109|
TCD|30200|1|
NTE|1|I|0|I|
OBX|3||30200||45542|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111106|bmserv^SYSTEM||EFV|e801^2^MU
1#e801#3#2^9|20180111111109|
TCD|30200|1|

14 HL7 communication examples

NTE|1|I|0|I|
OBX|4||30200||252|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111106|bmserv^SYSTEM||EFC|e801^2^MU1#
e801#3#2^9|20180111111109|
TCD|30200|1|
NTE|1|I|0|I|
OBX|5||30200||1001|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111106|bmserv^SYSTEM||PMT|e801^2^MU1
#e801#3#2^9|20180111111109|
TCD|30200|1|
NTE|1|I|0|I|
OBX|6||12002||59.5|mg/L|^TECH~^NORM~^CRIT~^USER||||V|||20180111111106|bmserv^SYSTEM||805|e801^2^MU1#
e801#3#2^9|20180111111109|
TCD|12002|1|
SID|12002^^1312002^ASY^32^0|188548|32|
NTE|1|I|0|I|
OBX|7||12002||87112|count|^TECH~^NORM~^CRIT~^USER||||V|||20180111111106|bmserv^SYSTEM||EFS|e801^2^MU
1#e801#3#2^9|20180111111109|
TCD|12002|1|
NTE|1|I|0|I|
OBX|8||12002||45542|count|^TECH~^NORM~^CRIT~^USER||||V|||20180111111106|bmserv^SYSTEM||EFV|e801^2^MU
1#e801#3#2^9|20180111111109|
TCD|12002|1|
NTE|1|I|0|I|
OBX|9||12002||252|count|^TECH~^NORM~^CRIT~^USER||||V|||20180111111106|bmserv^SYSTEM||EFC|e801^2^MU1#
e801#3#2^9|20180111111109|
TCD|12002|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 318 cobas e flow test result upload messages

OBX|10||12002||1001|count|^TECH~^NORM~^CRIT~^USER||||V|||20180111111106|bmserv^SYSTEM||PMT|e801^2^MU
1#e801#3#2^9|20180111111109|
TCD|12002|1|
NTE|1|I|0|I|
OBX|11||assignQual||1||^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20180111111110|
TCD|assignQual|1|
NTE|1|I|0|I|
OBX|12||12001|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20180111111105|bmserv^SYSTEM||805|
e801^1^MU1#e801#3#1^8|20180111111108|
TCD|12001|1|
SID|12001^^1312001^ASY^32^0|188548|32|
NTE|1|I|0|I|
OBX|13||12001||87112|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111105|bmserv^SYSTEM||EFS|e801^1^M
U1#e801#3#1^8|20180111111108|
TCD|12001|1|
NTE|1|I|0|I|
OBX|14||12001||45542|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111105|bmserv^SYSTEM||EFV|e801^1^M
U1#e801#3#1^8|20180111111108|
TCD|12001|1|
NTE|1|I|0|I|
OBX|15||12001||252|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111105|bmserv^SYSTEM||EFC|e801^1^MU1
#e801#3#1^8|20180111111108|
TCD|12001|1|
NTE|1|I|0|I|
OBX|16||12001||1001|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111105|bmserv^SYSTEM||PMT|e801^1^MU
1#e801#3#1^8|20180111111108|
TCD|12001|1|
NTE|1|I|0|I|
OBX|17||12003|| ^ |μg/L|^TECH~^NORM~^CRIT~^USER|HU|||F|||20180111111107|bmserv^SYSTEM||8
05|e801^2^MU1#e801#3#2^9|20180111111110|
TCD|12003|1|
SID|12003^^1312003^ASY^32^0|188548|32|
14 HL7 communication examples

NTE|1|I|0|I|
OBX|18||12003||87112|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111107|bmserv^SYSTEM||EFS|e801^2^M
U1#e801#3#2^9|20180111111110|
TCD|12003|1|
NTE|1|I|0|I|
OBX|19||12003||45542|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111107|bmserv^SYSTEM||EFV|e801^2^M
U1#e801#3#2^9|20180111111110|
TCD|12003|1|
NTE|1|I|0|I|
OBX|20||12003||252|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111107|bmserv^SYSTEM||EFC|e801^2^MU1
#e801#3#2^9|20180111111110|
TCD|12003|1|
NTE|1|I|0|I|
OBX|21||12003||1001|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111111107|bmserv^SYSTEM||PMT|e801^2^MU
1#e801#3#2^9|20180111111110|
TCD|12003|1|
NTE|1|I|0|I|

u For details of EP17-A flags, see EP17-A and the result

abnormal flags (53).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 319

cobas e flow test result with EP17-A data alarm

This section shows a result message for a
cobas e flow test with embedded tests which have pre-
defined EP17-A ranges.

The received results are validated against the EP17-A

ranges. The following rules are applied to the
cobas e flow test:
• If the result of a embedded test is outside the range, a
generic alarm ( eFlow.E ) is sent to the host.
• If a result cannot be calculated, the result is displayed
as 7 blank spaces, or as configured on the Host
reporting tab.
MSH|^~\&|cobas 8000||host||20180111112450||OUL^R22|2206||2.5||||ER||UNICODE UTF-8|
PID|1|PatID1|||Doe^John||19651125|M|
SPM||page_336_01||S1||not|||||P|||^^^^|||20140210085411||||||||||SC|
SAC||||||||||50001|1|
OBR|1|||30200|
TQ1|1||||||||R|
OBX|1||30200|| ^ ||^TECH~^NORM~^CRIT~^USER||||X||||^SYSTEM|||DM^0^DM#DM#0#0^0|2018011111
2451|
TCD|30200|1|
NTE|1|I|eFlow.E^Standard alarm for e 801 cobas e flow tests|I|
OBX|2||12001||-1^100|COI|^TECH~^NORM~^CRIT~^USER||||F|||20180111112446|bmserv^SYSTEM||805|e801^1^MU1
#e801#3#1^8|20180111112449|
TCD|12001|1|
SID|12001^^1312001^ASY^32^0|188548|32|
NTE|1|I|0|I|
OBX|3||12001||87112|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111112446|bmserv^SYSTEM||EFS|e801^1^MU

14 HL7 communication examples

1#e801#3#1^8|20180111112449|
TCD|12001|1|
NTE|1|I|0|I|
OBX|4||12001||45542|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111112446|bmserv^SYSTEM||EFV|e801^1^MU
1#e801#3#1^8|20180111112449|
TCD|12001|1|
NTE|1|I|0|I|
OBX|5||12001||252|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111112446|bmserv^SYSTEM||EFC|e801^1^MU1#
e801#3#1^8|20180111112449|
TCD|12001|1|
NTE|1|I|0|I|
OBX|6||12001||1001|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111112446|bmserv^SYSTEM||PMT|e801^1^MU1
#e801#3#1^8|20180111112449|
TCD|12001|1|
NTE|1|I|0|I|
OBX|7||12002||2500|mg/L|^TECH~^NORM~^CRIT~^USER||||F|||20180111112447|bmserv^SYSTEM||805|e801^2^MU1#
e801#3#2^9|20180111112450|
TCD|12002|1|
SID|12002^^1312002^ASY^32^0|188548|32|
NTE|1|I|26^Technical limit over (upper)|I|
OBX|8||12002||87112|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111112447|bmserv^SYSTEM||EFS|e801^2^MU
1#e801#3#2^9|20180111112450|
TCD|12002|1|
NTE|1|I|26^Technical limit over (upper)|I|
OBX|9||12002||45542|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111112447|bmserv^SYSTEM||EFV|e801^2^MU
1#e801#3#2^9|20180111112450|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 320 cobas e flow test result upload messages

TCD|12002|1|
NTE|1|I|26^Technical limit over (upper)|I|
OBX|10||12002||252|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111112447|bmserv^SYSTEM||EFC|e801^2^MU1
#e801#3#2^9|20180111112450|
TCD|12002|1|
NTE|1|I|26^Technical limit over (upper)|I|
OBX|11||12002||1001|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111112447|bmserv^SYSTEM||PMT|e801^2^MU
1#e801#3#2^9|20180111112450|
TCD|12002|1|
NTE|1|I|26^Technical limit over (upper)|I|
OBX|12||12003||1^200|μg/L|^TECH~^NORM~^CRIT~^USER|HU|||F|||20180111112448|bmserv^SYSTEM||805|e801^2^
MU1#e801#3#2^9|20180111112451|
TCD|12003|1|
SID|12003^^1312003^ASY^32^0|188548|32|
NTE|1|I|0|I|
OBX|13||12003||87112|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111112448|bmserv^SYSTEM||EFS|e801^2^M
U1#e801#3#2^9|20180111112451|
TCD|12003|1|
NTE|1|I|0|I|
OBX|14||12003||45542|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111112448|bmserv^SYSTEM||EFV|e801^2^M
U1#e801#3#2^9|20180111112451|
TCD|12003|1|
NTE|1|I|0|I|
OBX|15||12003||252|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111112448|bmserv^SYSTEM||EFC|e801^2^MU1
#e801#3#2^9|20180111112451|
TCD|12003|1|
NTE|1|I|0|I|
OBX|16||12003||1001|count|^TECH~^NORM~^CRIT~^USER||||F|||20180111112448|bmserv^SYSTEM||PMT|e801^2^MU
1#e801#3#2^9|20180111112451|
TCD|12003|1|
NTE|1|I|0|I|
14 HL7 communication examples

Sample with multiple cobas e flow tests and embedded

tests
This section shows the result of a test with multiple
cobas e flow tests. An OBR record is created for every
cobas e flow test, and an OBX record is created for every
embedded test within the cobas e flow test.

In this example, the sending of raw data has been

enabled, and the Send additional link information for
calculated QC option has been disabled.

MSH|^~\&|cobas 8000||host||20171222151226||OUL^R22|22412||2.5||||AL||UNICODE UTF-8|

PID|1||||^||||
SPM||101801||S1||not|||||P|||^^^^|||20171201160409|||||||||||
SAC||||||||||50461|1|
OBR|1|||22000|
TQ1|1||||||||R|
OBX|1||22000||-1^ |COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|201712011625
36|
TCD|22000|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 321

OBX|2||HIVDuo_01||-1^0.203|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|2017120116
2536|
TCD|HIVDuo_01|1|
NTE|1|I|0|I|
OBX|3||HIVAG_01||-1^0.185|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20171201162
536|
TCD|HIVAG_01|1|
NTE|1|I|0|I|
OBX|4||AHIV_01||-1^0.0827|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20171201162
536|
TCD|AHIV_01|1|
NTE|1|I|0|I|
OBX|5||11014|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20171201160704|bmserv^SYSTEM||3289|
e801^2^MU1#e801#2#2^10|20171201162536|
TCD|11014|1|
SID|11014^^1311014^ASY^19^0|246999|2012|
NTE|1|I|0|I|
OBX|6||11014||626.0948|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160704|bmserv^SYSTEM||EFS|e801^2
^MU1#e801#2#2^10|20171201162536|
TCD|11014|1|
NTE|1|I|0|I|
OBX|7||11014||-116.017|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160704|bmserv^SYSTEM||EFV|e801^2
^MU1#e801#2#2^10|20171201162536|
TCD|11014|1|
NTE|1|I|0|I|
OBX|8||11014||221.6544|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160704|bmserv^SYSTEM||EFC|e801^2
^MU1#e801#2#2^10|20171201162536|
TCD|11014|1|
NTE|1|I|0|I|
OBX|9||11014||13658.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160704|bmserv^SYSTEM||PMT|e801^2
^MU1#e801#2#2^10|20171201162536|
TCD|11014|1|

14 HL7 communication examples

NTE|1|I|0|I|
OBX|10||11013|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20171201160652|bmserv^SYSTEM||3286
|e801^1^MU1#e801#2#1^9|20171201162524|
TCD|11013|1|
SID|11013^^1311013^ASY^9^0|246999|2012|
NTE|1|I|0|I|
OBX|11||11013||695.0912|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160652|bmserv^SYSTEM||EFS|e801^
1^MU1#e801#2#1^9|20171201162524|
TCD|11013|1|
NTE|1|I|0|I|
OBX|12||11013||-115.852|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160652|bmserv^SYSTEM||EFV|e801^
1^MU1#e801#2#1^9|20171201162524|
TCD|11013|1|
NTE|1|I|0|I|
OBX|13||11013||224.0052|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160652|bmserv^SYSTEM||EFC|e801^
1^MU1#e801#2#1^9|20171201162524|
TCD|11013|1|
NTE|1|I|0|I|
OBX|14||11013||11456.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160652|bmserv^SYSTEM||PMT|e801^
1^MU1#e801#2#1^9|20171201162524|
TCD|11013|1|
NTE|1|I|0|I|
OBR|2|||22001|
TQ1|1||||||||R|
OBX|1||22001||15^73.7|%|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20171201162612|
TCD|22001|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 322 cobas e flow test result upload messages

OBX|2||11150||1^117|U/mL|^TECH~^NORM~^CRIT~^USER||||F|||20171201160716|bmserv^SYSTEM||3314|e801^1^MU
1#e801#2#1^9|20171201162548|
TCD|11150|1|
SID|11150^^1011151^ASY^28^0|252315|498|
NTE|1|I|0|I|
OBX|3||11150||479194.3|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160716|bmserv^SYSTEM||EFS|e801^1
^MU1#e801#2#1^9|20171201162548|
TCD|11150|1|
NTE|1|I|0|I|
OBX|4||11150||-115.873|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160716|bmserv^SYSTEM||EFV|e801^1
^MU1#e801#2#1^9|20171201162548|
TCD|11150|1|
NTE|1|I|0|I|
OBX|5||11150||224.3268|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160716|bmserv^SYSTEM||EFC|e801^1
^MU1#e801#2#1^9|20171201162548|
TCD|11150|1|
NTE|1|I|0|I|
OBX|6||11150||11668.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160716|bmserv^SYSTEM||PMT|e801^1
^MU1#e801#2#1^9|20171201162548|
TCD|11150|1|
NTE|1|I|0|I|
OBX|7||11151|| ^ |U/mL|^TECH~^NORM~^CRIT~^USER||||F|||20171201160728|bmserv^SYSTEM||3314
|e801^1^MU1#e801#2#1^9|20171201162612|
TCD|11151|1|
SID|11151^^1011151^ASY^28^0|252315|498|
NTE|1|I|0|I|
OBX|8||11151||171198.9|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160728|bmserv^SYSTEM||EFS|e801^1
^MU1#e801#2#1^9|20171201162612|
TCD|11151|1|
NTE|1|I|0|I|
OBX|9||11151||-115.907|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160728|bmserv^SYSTEM||EFV|e801^1
^MU1#e801#2#1^9|20171201162612|
14 HL7 communication examples

TCD|11151|1|
NTE|1|I|0|I|
OBX|10||11151||224.4484|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160728|bmserv^SYSTEM||EFC|e801^
1^MU1#e801#2#1^9|20171201162612|
TCD|11151|1|
NTE|1|I|0|I|
OBX|11||11151||11031.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160728|bmserv^SYSTEM||PMT|e801^
1^MU1#e801#2#1^9|20171201162612|
TCD|11151|1|
NTE|1|I|0|I|

cobas e flow test with qualitative and quantitative result

When the main result of a cobas e flow test is a
qualitative and quantitative result, the unit of the result is
set to the cobas e flow test measurement unit. The main
result in this example is a qualitative code with the value
of -1, which is mapped to the result message “non reac.”.
In addition, the result has the numeric value 0.0859.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 323

The same applies if the record is a result of an embedded

test of the cobas e flow test.
u For a list of result codes sent with qualitative results,
see Result message codes for
cobas e flow tests (439)

MSH|^~\&|cobas 8000||host||20171128095112||OUL^R22|11953||2.5||||ER||UNICODE UTF-8|

PID|1||||^||||
SPM||100910||S1||not|||||P|||^^^^|||20171128082922|||||||||||
SAC||||||||||50761|1|
OBR|1|||12019|
TQ1|1||||||||R|
OBX|1||12019||-1^0.0859|COI|^TECH~^NORM~^CRIT~^USER||||F|||20171128083140|bmserv^SYSTEM||3331|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|12019|1|
NTE|1|I|0|I|
OBX|2||12019||921.6664|count|^TECH~^NORM~^CRIT~^USER||||F|||20171128083140|bmserv^SYSTEM||EFS|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|12019|1|
NTE|1|I|0|I|
OBX|3||12019||-117.960|count|^TECH~^NORM~^CRIT~^USER||||F|||20171128083140|bmserv^SYSTEM||EFV|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|12019|1|
NTE|1|I|0|I|
OBX|4||12019||229.3872|count|^TECH~^NORM~^CRIT~^USER||||F|||20171128083140|bmserv^SYSTEM||EFC|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|12019|1|
NTE|1|I|0|I|
OBX|5||12019||13631.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171128083140|bmserv^SYSTEM||PMT|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|12019|1|
NTE|1|I|0|I|

14 HL7 communication examples

OBX|6||11074||-1^0.0859|COI|^TECH~^NORM~^CRIT~^USER||||V|||20171128083140|bmserv^SYSTEM||3331|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|11074|1|
SID|11074^^1310074^ASY^13^0|247710|812|
NTE|1|I|0|I|
OBX|7||11074||921.6664|count|^TECH~^NORM~^CRIT~^USER||||V|||20171128083140|bmserv^SYSTEM||EFS|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|11074|1|
NTE|1|I|0|I|
OBX|8||11074||-117.960|count|^TECH~^NORM~^CRIT~^USER||||V|||20171128083140|bmserv^SYSTEM||EFV|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|11074|1|
NTE|1|I|0|I|
OBX|9||11074||229.3872|count|^TECH~^NORM~^CRIT~^USER||||V|||20171128083140|bmserv^SYSTEM||EFC|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|11074|1|
NTE|1|I|0|I|
OBX|10||11074||13631.00|count|^TECH~^NORM~^CRIT~^USER||||V|||20171128083140|bmserv^SYSTEM||PMT|e801^
2^MU1#e801#2#2^10|20171128085013|
TCD|11074|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 324 cobas e flow test result upload messages

cobas e flow test with generated subresult

A cobas e flow test result can contain a generated
subresult in the subresult list. This section shows an
example of a result message with an internally calculated
formula result. The name of the formula is sent instead of
the test code. The host code for each formula can be
overwritten with a custom value, defined in the data
manager software.

In this example, the Send additional link information

for calculated QC option has been disabled. In some
cases, the result type has also been changed from the
default.

MSH|^~\&|cobas 8000||host||20180110175216||OUL^R22|24502||2.5||||SU||UNICODE UTF-8|

PID|1|PatID1|||Doe^John||19651125|M|
SPM||200418||S1||not|||||P|||^^^^|||20180110104344|||||||||||
SAC||||||||||50694|4|
OBR|1|||12000|
TQ1|1||||||||R|
OBX|1||12000||34^ ||^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20180110113315|
TCD|12000|1|
NTE|1|I|0|I|
OBX|2||HIVDuo_01||2.14^1|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|201801101133
15|
TCD|HIVDuo_01|1|
NTE|1|I|0|I|
OBX|3||HIVDuo_02||2.15^1|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|201801101133
15|
TCD|HIVDuo_02|1|
14 HL7 communication examples

NTE|1|I|0|I|
OBX|4||HIVDuo_03||2.12^1|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|201801101133
15|
TCD|HIVDuo_03|1|
NTE|1|I|0|I|
OBX|5||HIVAG_01||1.55^1|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|2018011011331
5|
TCD|HIVAG_01|1|
NTE|1|I|0|I|
OBX|6||HIVAG_02||1.53^1|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|2018011011331
5|
TCD|HIVAG_02|1|
NTE|1|I|0|I|
OBX|7||HIVAG_03||1.55^1|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|2018011011331
5|
TCD|HIVAG_03|1|
NTE|1|I|0|I|
OBX|8||AHIV_01||1.48^1|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20180110113315
|
TCD|AHIV_01|1|
NTE|1|I|0|I|
OBX|9||AHIV_02||1.51^1|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20180110113315
|
TCD|AHIV_02|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 325

OBX|10||AHIV_03||1.45^1|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|2018011011331
5|
TCD|AHIV_03|1|
NTE|1|I|0|I|
OBX|11||11014|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20180110105255|bmserv^SYSTEM||3514
|e801^2^MU1#e801#2#2^10|20180110111127|
TCD|11014|1|
SID|11014^^1311014^ASY^19^0|246999|2012|
NTE|1|I|0|I|
OBX|12||11014||2095.132|count|^TECH~^NORM~^CRIT~^USER||||F|||20180110105255|bmserv^SYSTEM||EFS|e801^
2^MU1#e801#2#2^10|20180110111127|
TCD|11014|1|
NTE|1|I|0|I|
OBX|13||11014||-117.729|count|^TECH~^NORM~^CRIT~^USER||||F|||20180110105255|bmserv^SYSTEM||EFV|e801^
2^MU1#e801#2#2^10|20180110111127|
TCD|11014|1|
NTE|1|I|0|I|
OBX|14||11014||237.7264|count|^TECH~^NORM~^CRIT~^USER||||F|||20180110105255|bmserv^SYSTEM||EFC|e801^
2^MU1#e801#2#2^10|20180110111127|
TCD|11014|1|
NTE|1|I|0|I|
OBX|15||11014||13312.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20180110105255|bmserv^SYSTEM||PMT|e801^
2^MU1#e801#2#2^10|20180110111127|
TCD|11014|1|
NTE|1|I|0|I|
OBX|16||11013|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20180110105243|bmserv^SYSTEM||3511
|e801^1^MU1#e801#2#1^9|20180110111115|
TCD|11013|1|
SID|11013^^1311013^ASY^9^0|246999|2012|
NTE|1|I|0|I|
OBX|17||11013||4470.002|count|^TECH~^NORM~^CRIT~^USER||||F|||20180110105243|bmserv^SYSTEM||EFS|e801^
1^MU1#e801#2#1^9|20180110111115|

14 HL7 communication examples

TCD|11013|1|
NTE|1|I|0|I|
OBX|18||11013||-117.422|count|^TECH~^NORM~^CRIT~^USER||||F|||20180110105243|bmserv^SYSTEM||EFV|e801^
1^MU1#e801#2#1^9|20180110111115|
TCD|11013|1|
NTE|1|I|0|I|
OBX|19||11013||238.2112|count|^TECH~^NORM~^CRIT~^USER||||F|||20180110105243|bmserv^SYSTEM||EFC|e801^
1^MU1#e801#2#1^9|20180110111115|
TCD|11013|1|
NTE|1|I|0|I|
OBX|20||11013||11277.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20180110105243|bmserv^SYSTEM||PMT|e801^
1^MU1#e801#2#1^9|20180110111115|
TCD|11013|1|
NTE|1|I|0|I|
OBX|21||11014|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||C|||20180110111419|bmserv^SYSTEM||3513
|e801^1^MU1#e801#2#1^9|20180110113251|
TCD|11014|1|
SID|11014^^1311014^ASY^19^0|246999|2012|
NTE|1|I|0|I|
OBX|22||11014||2064.796|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111419|bmserv^SYSTEM||EFS|e801^
1^MU1#e801#2#1^9|20180110113251|
TCD|11014|1|
NTE|1|I|0|I|
OBX|23||11014||-117.476|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111419|bmserv^SYSTEM||EFV|e801^
1^MU1#e801#2#1^9|20180110113251|
TCD|11014|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 326 cobas e flow test result upload messages

OBX|24||11014||238.4124|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111419|bmserv^SYSTEM||EFC|e801^
1^MU1#e801#2#1^9|20180110113251|
TCD|11014|1|
NTE|1|I|0|I|
OBX|25||11014||11325.00|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111419|bmserv^SYSTEM||PMT|e801^
1^MU1#e801#2#1^9|20180110113251|
TCD|11014|1|
NTE|1|I|0|I|
OBX|26||11013|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||C|||20180110111407|bmserv^SYSTEM||3512
|e801^2^MU1#e801#2#2^10|20180110113239|
TCD|11013|1|
SID|11013^^1311013^ASY^9^0|246999|2012|
NTE|1|I|0|I|
OBX|27||11013||4521.222|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111407|bmserv^SYSTEM||EFS|e801^
2^MU1#e801#2#2^10|20180110113239|
TCD|11013|1|
NTE|1|I|0|I|
OBX|28||11013||-117.889|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111407|bmserv^SYSTEM||EFV|e801^
2^MU1#e801#2#2^10|20180110113239|
TCD|11013|1|
NTE|1|I|0|I|
OBX|29||11013||238.4576|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111407|bmserv^SYSTEM||EFC|e801^
2^MU1#e801#2#2^10|20180110113239|
TCD|11013|1|
NTE|1|I|0|I|
OBX|30||11013||13499.00|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111407|bmserv^SYSTEM||PMT|e801^
2^MU1#e801#2#2^10|20180110113239|
TCD|11013|1|
NTE|1|I|0|I|
OBX|31||11014|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||C|||20180110111443|bmserv^SYSTEM||3513
|e801^1^MU1#e801#2#1^9|20180110113315|
TCD|11014|1|
14 HL7 communication examples

SID|11014^^1311014^ASY^19^0|246999|2012|
NTE|1|I|0|I|
OBX|32||11014||2077.824|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111443|bmserv^SYSTEM||EFS|e801^
1^MU1#e801#2#1^9|20180110113315|
TCD|11014|1|
NTE|1|I|0|I|
OBX|33||11014||-117.477|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111443|bmserv^SYSTEM||EFV|e801^
1^MU1#e801#2#1^9|20180110113315|
TCD|11014|1|
NTE|1|I|0|I|
OBX|34||11014||238.6900|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111443|bmserv^SYSTEM||EFC|e801^
1^MU1#e801#2#1^9|20180110113315|
TCD|11014|1|
NTE|1|I|0|I|
OBX|35||11014||11368.00|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111443|bmserv^SYSTEM||PMT|e801^
1^MU1#e801#2#1^9|20180110113315|
TCD|11014|1|
NTE|1|I|0|I|
OBX|36||11013|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||C|||20180110111431|bmserv^SYSTEM||3512
|e801^2^MU1#e801#2#2^10|20180110113303|
TCD|11013|1|
SID|11013^^1311013^ASY^9^0|246999|2012|
NTE|1|I|0|I|
OBX|37||11013||4347.092|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111431|bmserv^SYSTEM||EFS|e801^
2^MU1#e801#2#2^10|20180110113303|
TCD|11013|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 327

OBX|38||11013||-117.895|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111431|bmserv^SYSTEM||EFV|e801^
2^MU1#e801#2#2^10|20180110113303|
TCD|11013|1|
NTE|1|I|0|I|
OBX|39||11013||238.2596|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111431|bmserv^SYSTEM||EFC|e801^
2^MU1#e801#2#2^10|20180110113303|
TCD|11013|1|
NTE|1|I|0|I|
OBX|40||11013||13733.00|count|^TECH~^NORM~^CRIT~^USER||||C|||20180110111431|bmserv^SYSTEM||PMT|e801^
2^MU1#e801#2#2^10|20180110113303|
TCD|11013|1|
NTE|1|I|0|I|

cobas e flow test with non-reported embedded tests

Embedded tests which are marked as non-reported in the
data manager software are sent to the host in the same
manner as any other test. However, no result value is sent
for non-reported tests. Instead of a result, seven spaces
or the value configured on the Host reporting tab are
sent.

MSH|^~\&|cobas 8000||host||20171201165015||OUL^R22|21960||2.5||||ER||UNICODE UTF-8|

PID|1||||^||||
SPM||101802||S1||not|||||P|||^^^^|||20171201160432||||||||||SC|
SAC||||||||||50461|2|
OBR|1|||32000|
TQ1|1||||||||R|
OBX|1||32000||-1^ ||^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20171201162636|

14 HL7 communication examples

TCD|32000|1|
NTE|1|I|0|I|
OBX|2||HIVDuo_01||-1^0.362|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|2017120116
2636|
TCD|HIVDuo_01|1|
NTE|1|I|0|I|
OBX|3||HIVAG_01||-1^0.330|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20171201162
636|
TCD|HIVAG_01|1|
NTE|1|I|0|I|
OBX|4||AHIV_01||-1^0.149|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|201712011626
36|
TCD|AHIV_01|1|
NTE|1|I|0|I|
OBX|5||11014|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||3289|
e801^2^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
SID|11014^^1311014^ASY^19^0|246999|2012|
NTE|1|I|0|I|
OBX|6||11014||769.0851|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||EFS|e801^2
^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
NTE|1|I|0|I|
OBX|7||11014||-116.166|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||EFV|e801^2
^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 328 cobas e flow test result upload messages

NTE|1|I|0|I|
OBX|8||11014||221.7696|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||EFC|e801^2
^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
NTE|1|I|0|I|
OBX|9||11014||13813.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||PMT|e801^2
^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
NTE|1|I|0|I|
OBX|10||11013|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||3286
|e801^1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
SID|11013^^1311013^ASY^9^0|246999|2012|
NTE|1|I|0|I|
OBX|11||11013||872.4586|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||EFS|e801^
1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
NTE|1|I|0|I|
OBX|12||11013||-115.897|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||EFV|e801^
1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
NTE|1|I|0|I|
OBX|13||11013||224.8192|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||EFC|e801^
1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
NTE|1|I|0|I|
OBX|14||11013||10646.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||PMT|e801^
1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
NTE|1|I|0|I|
OBX|15||22000|3| ^ |COI|^TECH~^NORM~^CRIT~^USER||||B|||20171201160752|^SYSTEM|||e801^0^M
U1#e801#2#0^8|20171201162636|
14 HL7 communication examples

TCD|22000||
SID|22000^^12000^KIT^^0|246999|600000000230|
NTE|1|I|0|I|
OBX|16||22000|3| ^ |COI|^TECH~^NORM~^CRIT~^USER||||B|||20171201160752|^SYSTEM|||e801^0^M
U1#e801#2#0^8|20171201162636|
TCD|22000||
SID|22000^^12000^KIT^^0|246999|600000000230|
NTE|1|I|0|I|

cobas e flow test with data alarms and non-reported

embedded tests
A cobas e flow test result is based on an embedded test
or generated subresult. Data alarms can be assigned to
embedded tests, and thus assigned to the
cobas e flow test.

If a data alarm occurs for an embedded test which is

defined as the main result, then the result of this test is
not reported. However, the data alarm is assigned to the
cobas e flow test result.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 329

An additional data alarm is available for the main result:

• eFlow.E : standard alarm for e 801
cobas e flow tests

If a data alarm occurs for any embedded test other than

the main result test, then the standard alarm is assigned
to the cobas e flow test.
u Generic data alarm (61)

This section shows an example result message from an

HIV DUO cobas e flow test, including a data alarm and
non-reported embedded tests.

MSH|^~\&|cobas 8000||host||20180110174831||OUL^R22|24490||2.5||||SU||UNICODE UTF-8|

PID|1|PatID1|||Doe^John||19651125|M|
SPM||200419||S1||not|||||P|||^^^^|||20180110104347|||||||||||
SAC||||||||||50694|5|
OBR|1|||12016|
TQ1|1||||||||R|
OBX|1||12016|| ^ ||^TECH~^NORM~^CRIT~^USER||||X||||^SYSTEM|||DM^0^DM#DM#0#0^0|2018011010
5343|
TCD|12016|1|
NTE|1|I|eFlow.E^Standard alarm for e 801 cobas e flow tests|I|
OBX|2||11014|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F||||bmserv^SYSTEM||0|c8000^0^MU1#c8000
#0#0^1||
TCD|11014|1|
NTE|1|I|3^Sample short|I|
OBX|3||11013|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20180110105343|bmserv^SYSTEM||0|e80
1^2^MU1#e801#2#2^10|20180110105343|
TCD|11013|1|
NTE|1|I|3^Sample short|I|

14 HL7 communication examples

OBX|4||11013||0.000000|count|^TECH~^NORM~^CRIT~^USER||||F|||20180110105343|bmserv^SYSTEM||EFS|e801^2
^MU1#e801#2#2^10|20180110105343|
TCD|11013|1|
NTE|1|I|3^Sample short|I|
OBX|5||11013||0.000000|count|^TECH~^NORM~^CRIT~^USER||||F|||20180110105343|bmserv^SYSTEM||EFV|e801^2
^MU1#e801#2#2^10|20180110105343|
TCD|11013|1|
NTE|1|I|3^Sample short|I|
OBX|6||11013||0.000000|count|^TECH~^NORM~^CRIT~^USER||||F|||20180110105343|bmserv^SYSTEM||EFC|e801^2
^MU1#e801#2#2^10|20180110105343|
TCD|11013|1|
NTE|1|I|3^Sample short|I|
OBX|7||11013||0.000000|count|^TECH~^NORM~^CRIT~^USER||||F|||20180110105343|bmserv^SYSTEM||PMT|e801^2
^MU1#e801#2#2^10|20180110105343|
TCD|11013|1|
NTE|1|I|3^Sample short|I|

cobas e flow test result with custom host codes

This section shows an HL7 result message for a
cobas e flow test with host codes that have been
manually assigned.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 330 cobas e flow test result upload messages

In this example, custom host codes have been assigned

to the generated subresult and measurement unit values.

In this example, the custom host code values have been

configured as shown in the following screenshot.

w The custom host code configuration used in this example

u For information about assigning host codes and

enabling this functionality, see Assigning host codes
14 HL7 communication examples

to cobas e flow test results and generated

subresults (116).

MSH|^~\&|cobas 8000||host||20171201165015||OUL^R22|21960||2.5||||ER||UNICODE UTF-8|

PID|1||||^||||
SPM||101802||S1||not|||||P|||^^^^|||20171201160432||||||||||SC|
SAC||||||||||50461|2|
OBR|1|||32000|
TQ1|1||||||||R|
OBX|1||32000||-1^ ||^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20171201162636|
TCD|32000|1|
NTE|1|I|0|I|
OBX|2||HIVDuo_01||-1^0.362|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|2017120116
2636|
TCD|HIVDuo_01|1|
NTE|1|I|0|I|
OBX|3||HIVAG_01||-1^0.330|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20171201162
636|
TCD|HIVAG_01|1|
NTE|1|I|0|I|
OBX|4||AHIV_01||-1^0.149|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|201712011626
36|
TCD|AHIV_01|1|
NTE|1|I|0|I|
OBX|5||11014|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||3289|
e801^2^MU1#e801#2#2^10|20171201162624|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 331

TCD|11014|1|
SID|11014^^1311014^ASY^19^0|246999|2012|
NTE|1|I|0|I|
OBX|6||11014||769.0851|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||EFS|e801^2
^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
NTE|1|I|0|I|
OBX|7||11014||-116.166|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||EFV|e801^2
^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
NTE|1|I|0|I|
OBX|8||11014||221.7696|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||EFC|e801^2
^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
NTE|1|I|0|I|
OBX|9||11014||13813.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||PMT|e801^2
^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
NTE|1|I|0|I|
OBX|10||11013|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||3286
|e801^1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
SID|11013^^1311013^ASY^9^0|246999|2012|
NTE|1|I|0|I|
OBX|11||11013||872.4586|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||EFS|e801^
1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
NTE|1|I|0|I|
OBX|12||11013||-115.897|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||EFV|e801^
1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
NTE|1|I|0|I|

14 HL7 communication examples

OBX|13||11013||224.8192|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||EFC|e801^
1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
NTE|1|I|0|I|
OBX|14||11013||10646.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||PMT|e801^
1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
NTE|1|I|0|I|

If custom host code functionality had not been enabled in

the case of the above example, the message would
appear as follows.

MSH|^~\&|cobas 8000||host||20180104154400||OUL^R22|23147||2.5||||AL||UNICODE UTF-8|

PID|1||||^||||
SPM||101802||S1||not|||||P|||^^^^|||20171201160432||||||||||SC|
SAC||||||||||50461|2|
OBR|1|||22000|
TQ1|1||||||||R|
OBX|1||22000||-1^ ||^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20171201162636|
TCD|22000|1|
NTE|1|I|0|I|
OBX|2||HIVDuo_01||-1^0.362|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|2017120116
2636|
TCD|HIVDuo_01|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 332 cobas e flow test result upload messages

OBX|3||HIVAG_01||-1^0.330|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20171201162
636|
TCD|HIVAG_01|1|
NTE|1|I|0|I|
OBX|4||AHIV_01||-1^0.149|COI|^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|201712011626
36|
TCD|AHIV_01|1|
NTE|1|I|0|I|
OBX|5||11014|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||3289|
e801^2^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
SID|11014^^1311014^ASY^19^0|246999|2012|
NTE|1|I|0|I|
OBX|6||11014||769.0851|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||EFS|e801^2
^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
NTE|1|I|0|I|
OBX|7||11014||-116.166|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||EFV|e801^2
^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
NTE|1|I|0|I|
OBX|8||11014||221.7696|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||EFC|e801^2
^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
NTE|1|I|0|I|
OBX|9||11014||13813.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160752|bmserv^SYSTEM||PMT|e801^2
^MU1#e801#2#2^10|20171201162624|
TCD|11014|1|
NTE|1|I|0|I|
OBX|10||11013|| ^ |COI|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||3286
|e801^1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
14 HL7 communication examples

SID|11013^^1311013^ASY^9^0|246999|2012|
NTE|1|I|0|I|
OBX|11||11013||872.4586|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||EFS|e801^
1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
NTE|1|I|0|I|
OBX|12||11013||-115.897|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||EFV|e801^
1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
NTE|1|I|0|I|
OBX|13||11013||224.8192|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||EFC|e801^
1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
NTE|1|I|0|I|
OBX|14||11013||10646.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201160804|bmserv^SYSTEM||PMT|e801^
1^MU1#e801#2#1^9|20171201162636|
TCD|11013|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 333

cobas e flow test result message with raw data and data
points
This section shows a result message for a
cobas e flow test with embedded tests and both raw
data and data point values.

Data points are only included in the cobas e flow test

result if they are requested while the cobas e flow test is
still in progress.

The message also contains four raw data records:

Effective-Signal (EFS), Effective-Voltage (EFV), Effective-
Current (EFC) and PMT Spike (PMT).

MSH|^~\&|cobas 8000||host||20180110174438||OUL^R22|24477||2.5||||SU||UNICODE UTF-8|

PID|1|PatID1|||Doe^John||19651125|M|
SPM||100902||S1||not|||||P|||^^^^|||20180109134918||||||||||SC|
SAC||||||||||50862|2|
OBR|1|||22001|
TQ1|1||||||||R|
OBX|1||22001||57^ ||^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20180109164832|
TCD|22001|1|
NTE|1|I|0|I|
OBX|2||11150||0.767^0|U/mL|^TECH~^NORM~^CRIT~^USER||||C|||20180109162936|bmserv^SYSTEM||3432|e801^2^
MU1#e801#2#2^10|20180109164808|
TCD|11150|1|
SID|11150^^1011151^ASY^7^0|252315|459|
NTE|1|I|0|I|
OBX|3||11150||2195.272^9608&11752&11767&11928&11799&11238&11124&10586&10411&10225&10986&11826&11665&

14 HL7 communication examples

10869&11848&12174&11782&12420&11345&10964&11712&12020&10459&10567&9852&11419&12563&12256&11095&10614
&11051&10911&10452&11276&11376&10897&11202&12395&12054&11620&11999&12368&12220&10564&12261&11478&103
19&10725&12440&11989&12652&11041&10890&11556&10698&11651&11278&11435&11227&11836&12785&10592&10059&1
2525&10779&11200&10936&12171&12074&11736&11352&11395&11983&10512&11041&11975&12278&11991&11299&12166
&17852&26900&27402&27401&27227&26962&26703&26675&26322&26081&26097&25869&25872&25542&25315&25214&248
89&25022&24895&24764&24727&24413&24183&24333&24148&24063&24030&23861&23595&23686&23986&23500&23542&2
3745&23497&23298&23461&23071&23334&23206&23601&23268&23099&23085&23165&23186&22998&22822&22788&22938
&22942&22482&22777&22559&22585&22623&22215&22784&22614&22271&22594&22320&22395&22411&22207&22341&221
74&22425&22136&22448&22219&22340&22499&22127&21996&22365&21989&21817&22320&21903&21800&21585&21944&2
1734&21905&21754&21786&21763&21738&21612&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
|count|^TECH~^NORM~^CRIT~^USER||||C|||20180109162936|bmserv^SYSTEM||EFS|e801^2^MU1#e801#2#2^10|20180
109164808|
TCD|11150|1|
NTE|1|I|0|I|
OBX|4||11150||-118.131^33435&33434&33434&33433&33432&33429&33430&33431&33431&33430&33430&33429&33430
&33430&33430&33427&33427&33427&33428&33427&33425&33425&33425&33424&33427&33423&33424&33424&33421&334
22&33422&33424&33423&33422&33422&33421&33421&33421&33421&33420&33421&33419&33421&33418&33420&33418&3
3417&33417&33418&33417&33417&33417&33419&33418&33415&33417&33415&33414&33416&33415&33415&33413&33414
&33412&33412&33414&33412&33414&33414&33412&33412&33411&33412&33411&33413&33411&33412&33412&33411&334
11&26744&25721&25708&25702&25703&25695&25691&25685&25680&25673&25669&25663&25657&25651&25645&25640&2
5634&25629&25622&25619&25615&25608&25603&25597&25594&25589&25583&25579&25575&25565&25563&25555&25553
&25547&25540&25536&25532&25524&25522&25516&25510&25505&25501&25496&25490&25486&25483&25474&25472&254
66&25463&25459&25455&25449&25445&25444&25441&25437&25434&25429&25429&25424&25422&25417&25415&25411&2
5409&25408&25410&25413&25421&25422&25423&25429&25439&25447&25454&25453&25456&25454&25452&25452&25455
&25449&25448&25447&25444&25441&25437&25432&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|count|^TECH~^NORM~^CRIT~^USER||||C|||20180109162936|bmserv^SYSTEM||EFV|e801^2^MU1#e801#2#2^10|201
80109164808|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 334 cobas e flow test result upload messages

TCD|11150|1|
NTE|1|I|0|I|
OBX|5||11150||239.2032^31429&31425&31428&31425&31424&31422&31424&31423&31424&31424&31424&31423&31422
&31423&31422&31421&31422&31420&31421&31418&31419&31418&31418&31418&31419&31419&31418&31415&31416&314
17&31417&31416&31416&31415&31415&31414&31414&31411&31413&31414&31414&31414&31413&31411&31413&31412&3
1414&31412&31412&31411&31413&31409&31412&31409&31411&31407&31409&31408&31409&31408&31409&31407&31408
&31409&31408&31409&31407&31407&31407&31407&31406&31407&31407&31406&31405&31405&31406&31406&31406&314
03&2214&2762&6537&8727&10322&11598&12674&13612&14440&15143&15707&16157&16528&16849&17133&17384&17614
&17827&18020&18199&18365&18518&18667&18802&18929&19051&19169&19273&19378&19475&19570&19658&19745&198
25&19902&19979&20049&20115&20184&20247&20310&20368&20427&20483&20537&20590&20644&20696&20747&20798&2
0846&20895&20943&20989&21038&21083&21128&21176&21221&21266&21314&21359&21407&21452&21494&21518&21513
&21480&21443&21431&21436&21443&21438&21422&21416&21431&21456&21490&21524&21566&21607&21651&21696&217
38&21766&21788&21808&21828&21845&21866&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|c
ount|^TECH~^NORM~^CRIT~^USER||||C|||20180109162936|bmserv^SYSTEM||EFC|e801^2^MU1#e801#2#2^10|2018010
9164808|
TCD|11150|1|
NTE|1|I|0|I|
OBX|6||11150||12785.00|count|^TECH~^NORM~^CRIT~^USER||||C|||20180109162936|bmserv^SYSTEM||PMT|e801^2
^MU1#e801#2#2^10|20180109164808|
TCD|11150|1|
NTE|1|I|0|I|
OBX|7||11151|| ^ |U/mL|^TECH~^NORM~^CRIT~^USER||||C|||20180109162948|bmserv^SYSTEM||3432
|e801^2^MU1#e801#2#2^10|20180109164832|
TCD|11151|1|
SID|11151^^1011151^ASY^7^0|252315|459|
NTE|1|I|0|I|
OBX|8||11151||859.6854^10317&10995&11779&10618&10936&11788&12173&12535&11754&11381&11411&11179&11128
&11640&11215&11550&11803&12493&11529&13267&12603&13448&12157&10994&11342&11957&11385&12314&11585&113
50&11825&11635&11170&11570&10673&10842&12013&12511&11642&11138&11745&13076&12078&11811&11119&10932&1
0412&10652&10186&11921&11613&11888&11845&12168&12410&12448&12796&11359&10519&11692&12666&11926&11513
&11392&11938&12112&13273&11937&11502&11724&11206&11419&10081&11714&11598&11077&12083&11345&10406&108
93&13840&21580&22828&22546&22923&22759&22468&22437&22603&21812&21642&21893&22140&21424&20919&21338&2
14 HL7 communication examples

1382&21467&21442&21541&22033&20901&21162&21135&21343&21008&21257&21350&20889&21051&21161&20720&21502
&21336&21114&21158&20946&20907&20838&21074&20793&21202&21126&20784&20755&21315&20686&20889&20881&208
89&20681&20627&21493&21165&20820&20897&20961&20494&21154&20365&20751&19985&20375&20488&20515&20951&2
0845&20882&20841&21024&20337&20827&20779&20695&20744&20245&21113&20533&20650&20767&20587&20776&20819
&20508&20556&20579&20703&21017&20198&20513&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|count|^TECH~^NORM~^CRIT~^USER||||C|||20180109162948|bmserv^SYSTEM||EFS|e801^2^MU1#e801#2#2^10|201
80109164832|
TCD|11151|1|
NTE|1|I|0|I|
OBX|9||11151||-118.329^33443&33443&33441&33442&33440&33441&33440&33440&33441&33439&33438&33437&33439
&33440&33438&33437&33437&33438&33437&33437&33439&33435&33437&33434&33435&33438&33435&33433&33434&334
34&33433&33433&33432&33434&33432&33433&33432&33431&33431&33432&33431&33433&33431&33431&33428&33430&3
3429&33429&33426&33427&33428&33430&33427&33426&33429&33428&33426&33425&33425&33428&33424&33427&33423
&33423&33424&33423&33423&33422&33424&33425&33421&33424&33422&33423&33420&33422&33424&33423&33420&334
20&26744&25722&25706&25702&25697&25693&25690&25686&25680&25675&25667&25661&25655&25651&25644&25639&2
5631&25628&25621&25619&25609&25606&25600&25597&25591&25585&25579&25576&25569&25565&25559&25553&25547
&25542&25537&25532&25526&25522&25514&25511&25504&25500&25493&25490&25484&25479&25474&25472&25465&254
63&25458&25454&25449&25447&25440&25438&25433&25431&25424&25424&25420&25418&25416&25412&25407&25408&2
5404&25402&25404&25411&25414&25417&25419&25429&25436&25444&25447&25449&25450&25451&25449&25450&25451
&25451&25447&25443&25439&25436&25432&25430&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|count|^TECH~^NORM~^CRIT~^USER||||C|||20180109162948|bmserv^SYSTEM||EFV|e801^2^MU1#e801#2#2^10|201
80109164832|
TCD|11151|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test result upload messages 335

OBX|10||11151||239.2228^31430&31429&31428&31428&31427&31427&31427&31426&31426&31427&31424&31424&3142
5&31426&31425&31423&31423&31422&31421&31421&31421&31422&31420&31421&31421&31421&31419&31420&31420&31
420&31418&31417&31416&31418&31417&31416&31415&31417&31416&31417&31416&31416&31416&31416&31415&31414&
31415&31414&31412&31411&31411&31414&31412&31412&31412&31413&31409&31411&31410&31409&31409&31410&3140
9&31409&31410&31409&31409&31410&31407&31410&31407&31409&31409&31407&31408&31408&31406&31409&31406&31
407&2220&2767&6542&8730&10322&11594&12667&13598&14421&15124&15694&16151&16527&16853&17136&17390&1762
0&17833&18024&18205&18371&18528&18671&18807&18935&19055&19169&19280&19380&19482&19573&19663&19745&19
828&19902&19975&20047&20115&20181&20244&20303&20365&20419&20482&20534&20586&20637&20691&20738&20789&
20837&20886&20934&20982&21027&21075&21120&21166&21211&21259&21308&21352&21401&21445&21486&21514&2150
7&21468&21427&21416&21426&21431&21427&21414&21404&21421&21449&21480&21515&21559&21600&21644&21698&21
745&21770&21792&21806&21826&21843&21861&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|
count|^TECH~^NORM~^CRIT~^USER||||C|||20180109162948|bmserv^SYSTEM||EFC|e801^2^MU1#e801#2#2^10|201801
09164832|
TCD|11151|1|
NTE|1|I|0|I|
OBX|11||11151||13448.00|count|^TECH~^NORM~^CRIT~^USER||||C|||20180109162948|bmserv^SYSTEM||PMT|e801^
2^MU1#e801#2#2^10|20180109164832|
TCD|11151|1|
NTE|1|I|0|I|

14 HL7 communication examples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 336 Qualitative and cut-off index result messages

Qualitative and cut-off index result

messages
The data manager handles combined qualitative and cut-
off index results, and displays the results in the
corresponding columns on the result screen.

In this section
Qualitative/cut-off index result for regular test (336)
Qualitative/cut-off index result for
cobas e flow test (336)
Embedded test result with qualitative result in
cobas e flow test (337)

Qualitative/cut-off index result for regular test

The qualitative result is displayed in the column Test
result as "NonReac" and is mapped to -1. The cut-off
index result is displayed in the Previous result column.

MSH|^~\&|cobas 8000||host||20170106134144||OUL^R22|148839||2.5||||ER||UNICODE UTF-8|

PID|1||||^||||
SPM||98125||S1||not|||||P|||^^^^|||20170106134133||||||||||SC|
SAC|||||||||||0|
OBR|1|||95|
14 HL7 communication examples

TQ1|1||||||||R|
OBX|1|CE|95||-1^3.12|COI|^TECH~^NORM~^CRIT~^USER||||F|||20170106134142|bmserv^SYSTEM|||e602^1^MU1#e6
02#3#1^11|20170106134142|
TCD|95|1|
NTE|1|I|0|I|

Qualitative/cut-off index result for cobas e flow test

The qualitative result -1 is mapped to "NonReac", and the
cut-off index result 0.0859 is displayed in the Previous
result column. Both results are sent to the host.

MSH|^~\&|cobas 8000||host||20171128095112||OUL^R22|11953||2.5||||ER||UNICODE UTF-8|

PID|1||||^||||
SPM||100910||S1||not|||||P|||^^^^|||20171128082922|||||||||||
SAC||||||||||50761|1|
OBR|1|||12019|
TQ1|1||||||||R|
OBX|1||12019||-1^0.0859|COI|^TECH~^NORM~^CRIT~^USER||||F|||20171128083140|bmserv^SYSTEM||3331|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|12019|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Qualitative and cut-off index result messages 337

OBX|2||12019||921.6664|count|^TECH~^NORM~^CRIT~^USER||||F|||20171128083140|bmserv^SYSTEM||EFS|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|12019|1|
NTE|1|I|0|I|
OBX|3||12019||-117.960|count|^TECH~^NORM~^CRIT~^USER||||F|||20171128083140|bmserv^SYSTEM||EFV|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|12019|1|
NTE|1|I|0|I|
OBX|4||12019||229.3872|count|^TECH~^NORM~^CRIT~^USER||||F|||20171128083140|bmserv^SYSTEM||EFC|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|12019|1|
NTE|1|I|0|I|
OBX|5||12019||13631.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171128083140|bmserv^SYSTEM||PMT|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|12019|1|
NTE|1|I|0|I|
OBX|6||11074||-1^0.0859|COI|^TECH~^NORM~^CRIT~^USER||||V|||20171128083140|bmserv^SYSTEM||3331|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|11074|1|
SID|11074^^1310074^ASY^13^0|247710|812|
NTE|1|I|0|I|
OBX|7||11074||921.6664|count|^TECH~^NORM~^CRIT~^USER||||V|||20171128083140|bmserv^SYSTEM||EFS|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|11074|1|
NTE|1|I|0|I|
OBX|8||11074||-117.960|count|^TECH~^NORM~^CRIT~^USER||||V|||20171128083140|bmserv^SYSTEM||EFV|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|11074|1|
NTE|1|I|0|I|
OBX|9||11074||229.3872|count|^TECH~^NORM~^CRIT~^USER||||V|||20171128083140|bmserv^SYSTEM||EFC|e801^2
^MU1#e801#2#2^10|20171128085013|
TCD|11074|1|

14 HL7 communication examples

NTE|1|I|0|I|
OBX|10||11074||13631.00|count|^TECH~^NORM~^CRIT~^USER||||V|||20171128083140|bmserv^SYSTEM||PMT|e801^
2^MU1#e801#2#2^10|20171128085013|
TCD|11074|1|
NTE|1|I|0|I|

Embedded test result with qualitative result in

cobas e flow test
This section shows a result message with embedded tests
in a cobas e flow test.

A cobas e flow test can have a generated subresult with

a qualitative result as the main result. The result in this
example is a code with the value of 34, which is mapped
in the data manager to the result message "Repeatedly
reactive". Also, when the main result is a qualitative result,
no value is sent for the unit.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 338 Qualitative and cut-off index result messages

This example uses the cobas e flow test SYPH R.

u For a list of result codes sent with qualitative results,
see Result message codes for
cobas e flow tests (439)

MSH|^~\&|cobas 8000||host||20171128095107||OUL^R22|11952||2.5||||ER||UNICODE UTF-8|

PID|1||||^||||
SPM||100311||S1||not|||||P|||^^^^|||20171128082800|||||||||||
SAC||||||||||50761|2|
OBR|1|||32019|
TQ1|1||||||||R|
OBX|1||32019||34^ ||^TECH~^NORM~^CRIT~^USER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20171128090949|
TCD|32019|1|
NTE|1|I|0|I|
OBX|2||11074||1^4.35|COI|^TECH~^NORM~^CRIT~^USER||||F|||20171128083152|bmserv^SYSTEM||3330|e801^1^MU
1#e801#2#1^9|20171128085025|
TCD|11074|1|
SID|11074^^1310074^ASY^13^0|247710|812|
NTE|1|I|0|I|
OBX|3||11074||1^4.47|COI|^TECH~^NORM~^CRIT~^USER||||C|||20171128085104|bmserv^SYSTEM||3330|e801^1^MU
1#e801#2#1^9|20171128090937|
TCD|11074|1|
SID|11074^^1310074^ASY^13^0|247710|812|
NTE|1|I|0|I|
OBX|4||11074||1^4.44|COI|^TECH~^NORM~^CRIT~^USER||||C|||20171128085116|bmserv^SYSTEM||3331|e801^2^MU
1#e801#2#2^10|20171128090949|
TCD|11074|1|
SID|11074^^1310074^ASY^13^0|247710|812|
NTE|1|I|0|I|
14 HL7 communication examples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Quality control result upload messages 339

Quality control result upload messages

In the examples in this section, the data manager uploads
HL7 quality control results.

q The data manager always uses By test mode to

upload QC results which have been manually resent from
the control unit to the host, regardless of which upload
mode is selected on the data manager and control unit.
u For more information about result upload modes, see Result
upload settings (140)

In this section
Realtime QC from c-module (339)
Realtime QC from c-module standby bottle (339)
Batch QC from c-module (340)
Batch QC from c-module standby bottle (340)
QC results from e-module (341)
Symmetric quality control result message (341)
Asymmetric quality control result message (342)

Realtime QC from c-module

This section shows an example of a realtime HL7 quality

14 HL7 communication examples

control result from a c-module.

MSH|^~\&|cobas 8000||host||20160919112926||OUL^R22^REAL|14109||2.5||||ER||UNICODE UTF-8|

PID|1|
SPM||PPU^150415^3^20160921^48||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|||20160919111911|bmserv^SYSTEM||77|c701^1^MU1#c701#1#
1^6^Current|20160919112926|
TCD|8717|1|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
NTE|1|I|0|I|

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||20160919112922||OUL^R22^REAL|14105||2.5||||ER||UNICODE UTF-8|

PID|1|
SPM||PPU^150415^3^20160921^48||S1||not|||||Q|||^^^^|||||||||||||SC|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 340 Quality control result upload messages

SAC||||||||||30005|2|
OBR|1|||8685^|
TQ1|1||||||||R|
OBX|1||8685||121|U/L|127^TARGET~3^SD||||F|||20160919111907|bmserv^SYSTEM||76|c701^1^MU1#c701#1#1^6^
Standby^1|20160919112922|
TCD|8685|1|
SID|8685^^564957^R1^31^0|616478|923|
SID|8685^^564957^R3^31^0|616478|923|
NTE|1|I|0|I|

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||20160919123938||OUL^R22^BATCH|14250||2.5||||ER||UNICODE UTF-8|

PID|1|
SPM||PNU^150403^2^20160921^27||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|||20160919111900|bmserv^SYSTEM||77|c701^1^MU1#c701#1
#1^6^Current|20160919112915|
TCD|8717|1|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
NTE|1|I|0|I|
14 HL7 communication examples

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||20160919123853||OUL^R22^BATCH|14249||2.5||||ER||UNICODE UTF-8|

PID|1|
SPM||PNU^150403^2^20160921^27||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||30005|1|
OBR|1|||8685^|
TQ1|1||||||||R|
OBX|1||8685||48|U/L|50^TARGET~3^SD||||F|||20160919111857|bmserv^SYSTEM||76|c701^1^MU1#c701#1#1^6^Sta
ndby^1|20160919112911|
TCD|8685|1|
SID|8685^^564957^R1^31^0|616478|923|
SID|8685^^564957^R3^31^0|616478|923|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Quality control result upload messages 341

QC results from e-module

This section shows examples of HL7 quality control
results from an e-module.

MSH|^~\&|cobas 8000||host||20160919123353||OUL^R22^REAL|14226||2.5||||ER||UNICODE UTF-8|

PID|1|
SPM||PC U1^156227^4^20160921^86||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|||20160919121523|bmserv^SYSTEM||0|e602^1^MU1#e602#2#1^
9^Current|20160919123353|
TCD|1|1|
SID|1^^1^ASY^18^0|157328|62769|
NTE|1|I|0|I|

Symmetric quality control result message

Quality control result messages are sent to the host for
master QC results and copy QC results. Raw data for each
test is sent to the host.

The OBX-7 segment contains the target value and

standard deviation associated with symmetric quality
controls. When either the target value or the standard
deviation is null, it is not included in the result message.
u For more information about the copy QC concept, see

14 HL7 communication examples

the cobas® 8000 data manager Operator’s Manual.

MSH|^~\&|cobas 8000||host||20180105081717||OUL^R22^REAL|23879||2.5||||AL||UNICODE UTF-8|

PID|1|
SPM||PC HIV5^202154^26^20180331^641||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||30014|5|
OBR|1|||11013|
TQ1|1||||||||R|
OBX|1||11013||1^4.44|COI|6.35^TARGET~1.06^SD||||F|||20171124085136|bmserv^SYSTEM||3290|e801^1^MU1#e8
01#2#1^9^Current|20171124091009|
TCD|11013|1|
SID|11013^^1311013^ASY^20^0|257666|2013|
NTE|1|I|0|I|
OBX|2||11013||12097.24|count|||||F|||20171124085136|bmserv^SYSTEM||EFS|e801^1^MU1#e801#2#1^9^Current
|20171124091009|
TCD|11013|1|
NTE|1|I|0|I|
OBX|3||11013||-116.587|count|||||F|||20171124085136|bmserv^SYSTEM||EFV|e801^1^MU1#e801#2#1^9^Current
|20171124091009|
TCD|11013|1|
NTE|1|I|0|I|
OBX|4||11013||219.7976|count|||||F|||20171124085136|bmserv^SYSTEM||EFC|e801^1^MU1#e801#2#1^9^Current
|20171124091009|
TCD|11013|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 342 Quality control result upload messages

OBX|5||11013||10876.00|count|||||F|||20171124085136|bmserv^SYSTEM||PMT|e801^1^MU1#e801#2#1^9^Current
|20171124091009|
TCD|11013|1|
NTE|1|I|0|I|

Asymmetric quality control result message

Standard deviation values are not sent to the host for
asymmetric quality control results, as asymmetric controls
have no standard deviation. However, if an asymmetric
control is configured with a target value, results are sent
to the host together with the target values.

For asymmetric control results, OBX-7 is formatted as

follows:
• With target value:
targetvalue^TARGET~lowerrangevalue^LO
WER~upperrangevalue^UPPER
• Without target value:
lowerrangevalue^LOWER~upperrangevalue
^UPPER

If the Use Custom Values flag is enabled, the LOWER

and UPPER values in the above examples are taken from
the custom range limits. If the flag is not enabled, the
values are taken from the quality control itself.
14 HL7 communication examples

Example without target value

MSH|^~\&|cobas 8000||host||20171201162114||OUL^R22^REAL|21826||2.5||||ER||UNICODE UTF-8|
PID|1|
SPM||PC HIV4^202153^25^20180331^640||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||30007|4|
OBR|1|||11014|
TQ1|1||||||||R|
OBX|1||11014||-1^0.185|COI|0.025^LOWER~0.5^UPPER||||F|||20171201160240|bmserv^SYSTEM||3289|e801^2^MU
1#e801#2#2^10^Current|20171201162112|
TCD|11014|1|
SID|11014^^1311014^ASY^19^0|246999|2012|
NTE|1|I|0|I|
OBX|2||11014||626.7169|count|||||F|||20171201160240|bmserv^SYSTEM||EFS|e801^2^MU1#e801#2#2^10^Curren
t|20171201162112|
TCD|11014|1|
NTE|1|I|0|I|
OBX|3||11014||-115.839|count|||||F|||20171201160240|bmserv^SYSTEM||EFV|e801^2^MU1#e801#2#2^10^Curren
t|20171201162112|
TCD|11014|1|
NTE|1|I|0|I|
OBX|4||11014||221.1472|count|||||F|||20171201160240|bmserv^SYSTEM||EFC|e801^2^MU1#e801#2#2^10^Curren
t|20171201162112|
TCD|11014|1|
NTE|1|I|0|I|
OBX|5||11014||13620.00|count|||||F|||20171201160240|bmserv^SYSTEM||PMT|e801^2^MU1#e801#2#2^10^Curren
t|20171201162112|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Quality control result upload messages 343

TCD|11014|1|
NTE|1|I|0|I|

Example with target value (OBX segment

only)
OBX|1||10444||0.53|IU/mL|0.84^TARGET~0.14^LOWER~0.14^UPPER||||F|||20170507113925|bmserv^SYSTEM||12|e
801^1^MU1#e801#4#1^14^Current|20170507113930|

14 HL7 communication examples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 344 cobas e flow test calculated QC result messages

cobas e flow test calculated QC result

messages
In the examples in this section, the data manager uploads
HL7 cobas e flow test calculated QC results.

In this section
Calculated QC result message (344)
Calculated QC result flagged with generic alarm (345)
Calculated QC result with raw data (345)

Calculated QC result message

Calculated QC results are used for the validation of
cobas e flow test results. The calculated QC result is
calculated based on a formula of quality control results
from embedded tests. It is sent to the host as a
standalone message.

This section shows an example of a calculated QC result

message.
u For more information about calculated QC, see the
cobas® 8000 data manager Operator’s Manual.
14 HL7 communication examples

MSH|^~\&|cobas 8000||host||20180104182126||OUL^R22^BATCH|23431||2.5||||AL||UNICODE UTF-8|

PID|1|
SPM||PC HIV4^202153^25^20180331^640||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||||
OBR|1|||12000|
TQ1|1||||||||R|
OBX|1||12000|5| ^4.34|COI|4.52^TARGET~0.753^SD||||F|||20171124085000|^SYSTEM|||e801^0^MU1#e801#2#0^8
^Current|20171124090857|
TCD|12000|1|
SID|12000^^12000^KIT^^0|257666|600000000231|
NTE|1|I|0|I|
OBX|2||11013||1^4.34|COI|4.51^TARGET~0.752^SD||||F|||20171124085000|bmserv^SYSTEM||3290|e801^1^MU1#e
801#2#1^9^Current|20171124090833|
TCD|11013|1|
SID|11013^^1311013^ASY^20^0|257666|2013|
NTE|1|I|0|I|
OBX|3||11014||-1^0.176|COI|0.025^LOWER~0.5^UPPER||||F|||20171124085024|bmserv^SYSTEM||3292|e801^1^MU
1#e801#2#1^9^Current|20171124090857|
TCD|11014|1|
SID|11014^^1311014^ASY^21^0|257666|2013|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 cobas e flow test calculated QC result messages 345

Calculated QC result flagged with generic alarm

If one or more of the embedded tests used in the
calculation of a calculated QC result is either flagged with
an alarm or is in violation of a QC rule, the
cobas e flow test result is also flagged.

In this example, the Send single QC results for

calculated QC option has been disabled.

MSH|^~\&|cobas 8000||host||20171205080012||OUL^R22^REAL|23847||2.5||||AL||UNICODE UTF-8|

PID|1|
SPM||PC HIV5^202154^26^20180331^641||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||||
OBR|1|||12000|
TQ1|1||||||||R|
OBX|1||12000|6| ^4.44|COI|6.35^TARGET~1.06^SD||||F|||20171124085136|^SYSTEM|||e801^0^MU1#e801#2#0^8^
Current|20171124091045|
TCD|12000|1|
SID|12000^^12000^KIT^^0|257666|600000000231|
NTE|1|I|eFlow.E^Standard alarm for e 801 cobas e flow tests|I|

Calculated QC result with raw data

This section shows an example of a calculated QC result
with raw data values, from an e 801 module.

MSH|^~\&|cobas 8000||host||20171201162202||OUL^R22^REAL|21855||2.5||||ER||UNICODE UTF-8|

14 HL7 communication examples

PID|1|
SPM||PC HIV5^202154^26^20180331^641||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||||
OBR|1|||22000|
TQ1|1||||||||R|
OBX|1||22000|3| ^4.93|COI|5.34^TARGET~0.89^SD||||F|||20171201160252|^SYSTEM|||e801^0^MU1#e801#
2#0^8^Current|20171201162200|
TCD|22000|1|
SID|22000^^12000^KIT^^0|246999|600000000230|
NTE|1|I|0|I|
OBX|2||11013||1^4.93|COI|5.34^TARGET~0.89^SD||||F|||20171201160252|bmserv^SYSTEM||3286|e801^1^MU1#e8
01#2#1^9^Current|20171201162124|
TCD|11013|1|
SID|11013^^1311013^ASY^9^0|246999|2012|
NTE|1|I|0|I|
OBX|3||11013||13618.75|count|||||F|||20171201160252|bmserv^SYSTEM||EFS|e801^1^MU1#e801#2#1^9^Current
|20171201162124|
TCD|11013|1|
NTE|1|I|0|I|
OBX|4||11013||-115.482|count|||||F|||20171201160252|bmserv^SYSTEM||EFV|e801^1^MU1#e801#2#1^9^Current
|20171201162124|
TCD|11013|1|
NTE|1|I|0|I|
OBX|5||11013||223.5704|count|||||F|||20171201160252|bmserv^SYSTEM||EFC|e801^1^MU1#e801#2#1^9^Current
|20171201162124|
TCD|11013|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 346 cobas e flow test calculated QC result messages

OBX|6||11013||10558.00|count|||||F|||20171201160252|bmserv^SYSTEM||PMT|e801^1^MU1#e801#2#1^9^Current
|20171201162124|
TCD|11013|1|
NTE|1|I|0|I|
OBX|7||11014||-1^0.199|COI|0.025^LOWER~0.5^UPPER||||F|||20171201160328|bmserv^SYSTEM||3289|e801^2^MU
1#e801#2#2^10^Current|20171201162200|
TCD|11014|1|
SID|11014^^1311014^ASY^19^0|246999|2012|
NTE|1|I|0|I|
OBX|8||11014||640.5725|count|||||F|||20171201160328|bmserv^SYSTEM||EFS|e801^2^MU1#e801#2#2^10^Curren
t|20171201162200|
TCD|11014|1|
NTE|1|I|0|I|
OBX|9||11014||-115.732|count|||||F|||20171201160328|bmserv^SYSTEM||EFV|e801^2^MU1#e801#2#2^10^Curren
t|20171201162200|
TCD|11014|1|
NTE|1|I|0|I|
OBX|10||11014||221.4784|count|||||F|||20171201160328|bmserv^SYSTEM||EFC|e801^2^MU1#e801#2#2^10^Curre
nt|20171201162200|
TCD|11014|1|
NTE|1|I|0|I|
OBX|11||11014||13263.00|count|||||F|||20171201160328|bmserv^SYSTEM||PMT|e801^2^MU1#e801#2#2^10^Curre
nt|20171201162200|
TCD|11014|1|
NTE|1|I|0|I|
14 HL7 communication examples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Calibration result upload messages 347

Calibration result upload messages

In the examples in this section, the data manager uploads
HL7 calibration results.

In this section
C-module calibration result (347)
ISE-module calibration result (347)
E-module calibration results (348)

C-module calibration result

This section shows an example of an HL7 calibration
result from a c module.

MSH|^~\&|cobas 8000||host||20171127142550||OUL^R22^PCUPL|9285||2.5||||ER||UNICODE UTF-8|

SPM||1^999999^901^1^20301231|||||||||C^P|
OBR|1|||8731|
OBX|1||8731||0^6&7&788&5&783&|||16|||F||||bmserv||1878|c702^1^MU1#c702#1#1^6^Current|20171127142550|
SID|8731^^^^3^0|274393|5212|
SPM||2^186426^401^1^20171231|||||||||C^P|
OBR|2|||8731|
OBX|1||8731||0^574&571&1662&577&1665&|||16|||F||||bmserv||1878|c702^1^MU1#c702#1#1^6^Current|2017112
7142550|
SID|8731^^^^3^0|274393|5212|

14 HL7 communication examples

ISE-module calibration result
This section shows an example of an HL7 calibration
result from an ISE-module.

MSH|^~\&|cobas 8000||host||20171127141555||OUL^R22^ICUPL|9240||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^-35.6&-39.6&-32.6&-32.3&56.0&141.3&162.0&0.0&55.3&-2.0|||Vali
d|||F||||bmserv||770|ISE^1^MU1#ISE#1#1^3|20171127141554|
SID||
SPM|||||||||||C^I|
OBR|2|||990|
OBX|1||990||Type-A^0&0&0&0&0&0&0&0&0&0^-40.3&-53.5&-32.4&-32.1&57.3&5.11&7.10&0.0&57.6&-0.10|||Valid
|||F||||bmserv||771|ISE^1^MU1#ISE#1#1^3|20171127141555|
SID||
SPM|||||||||||C^I|
OBR|3|||991|
OBX|1||991||Type-A^0&0&0&0&0&0&0&0&0&0^134.1&138.1&129.7&129.5&-47.7&97.0&121.0&0.0&-49.3&-1.0|||Val
id|||F||||bmserv||772|ISE^1^MU1#ISE#1#1^3|20171127141555|
SID||

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 348 Calibration result upload messages

E-module calibration results

This section shows examples of HL7 calibration results
from e-modules.

e 602 example
MSH|^~\&|cobas 8000||host||20171118175819||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^^^^^|||LotCalibration
|||F||||bmserv||25|e602^1^MU1#e602#2#1^9^Current|20171118175819|
SID|1^^^ASY^18^0|157328|5|
SPM||1^158941^1^None^20171119|||||||||C^E|
OBR|2|||1|
OBX|1||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|20171118175819|
SID|1^^^ASY^18^0|157328|5|

e 801 example
MSH|^~\&|cobas 8000||host||20171127151640||OUL^R22^ECUPL|9503||2.5||||ER||UNICODE UTF-8|
SPM||2^258898^10100^None^|||||||||C^E|
OBR|1|||10100|
OBX|1||10100||Valid^false^false^false^1.00^false^^false^false^3639&3564^^^^^|||LotCalibration|||F|||
|bmserv||3358|e801^2^MU1#e801#2#2^10^Current|20171127151640|
SID|10100^^^ASY^40^0|217308|1950|
SPM||1^258898^10100^None^|||||||||C^E|
OBR|2|||10100|
OBX|1||10100||Valid^false^false^false^1.00^false^^false^false^112906&113289^^^^^|||LotCalibration|||
F||||bmserv||3358|e801^2^MU1#e801#2#2^10^Current|20171127151640|
SID|10100^^^ASY^40^0|217308|1950|
14 HL7 communication examples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Masking messages 349

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
acknowledgment message.

Host:
MSH|^~\&|host||cobas 8000||20171007113655||EAC^U07|13010||2.5||||AL||UNICODE UTF-8|
EQU|1|20171007113600|
ECD||LK|||994^P^MU1#c702#1#1^ALL|

DM:
MSH|^~\&|cobas 8000||host||20171007113946||ACK|19922||2.5||||NE||UNICODE UTF-8|
MSA|AA|13010||

Unsuccessful masking message In this section the host sends a masking command, but
the module ( MU1#c701#1#1 ) does not exist.

Host:
MSH|^~\&|host||cobas 8000||20171007113655||EAC^U07|13011||2.5||||AL||UNICODE UTF-8|
EQU|1|20171007113600|
ECD||LK|||989^P^MU1#c701#1#1^ALL|

DM:
MSH|^~\&|cobas 8000||host||20171007125554||ACK|13011||2.5||||NE||UNICODE UTF-8|
MSA|AE|13011|Submodule (MU1#c701#1#1) not found

14 HL7 communication examples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 350 Result requests from the host

Result requests from the host

In the examples in this section the host sends result
requests.

! CAUTION
Always give rack types if using sample lifetime
r If you set sample lifetime to a number greater than
zero, always send the rack type (“specimen type” or
“sample type”) with an order or result query.
Otherwise, the data manager does not reply.

In this section
Request for all results (350)
Request for final results (351)
No results found (351)
Sample not found (352)
Result request with a sequence number (352)
Result request with an expired sample (353)

Request for all results

In this section the host sends a request for all results for a
sample.
14 HL7 communication examples

Host:
MSH|^~\&|host||cobas·8000||20180105090932||RSREQ|10006||2.5||||NE||UNICODE·UTF-8|
QPD|RSREQ|10006|200010|||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000||host||20180105091456||OUL^R22^BATCH|22479||2.5||||AL||UNICODE UTF-8|
PID|1||||^||||
SPM||200010||S1||not|||||P|||^^^^|||20171201102738||||||||||SC|
SAC||||||||||50480|1|
OBR|1|||10001|
TQ1|1||||||||R|
OBX|1||10001||0.0213|μIU/mL|^TECH~^NORM~^CRIT~^USER||||F|||20171201102826|bmserv^SYSTEM||3334|e801^1
^MU1#e801#2#1^9|20171201104659|
TCD|10001|1|
SID|10001^^1310001^ASY^18^0|226387|44872|
NTE|1|I|0|I|
OBX|2||10001||865.5250|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201102826|bmserv^SYSTEM||EFS|e801^1
^MU1#e801#2#1^9|20171201104659|
TCD|10001|1|
NTE|1|I|0|I|
OBX|3||10001||-117.195|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201102826|bmserv^SYSTEM||EFV|e801^1
^MU1#e801#2#1^9|20171201104659|
TCD|10001|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Result requests from the host 351

OBX|4||10001||209.6324|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201102826|bmserv^SYSTEM||EFC|e801^1
^MU1#e801#2#1^9|20171201104659|
TCD|10001|1|
NTE|1|I|0|I|
OBX|5||10001||11728.00|count|^TECH~^NORM~^CRIT~^USER||||F|||20171201102826|bmserv^SYSTEM||PMT|e801^1
^MU1#e801#2#1^9|20171201104659|
TCD|10001|1|
NTE|1|I|0|I|

Request for final results

In this section the host sends a request for final results for
a sample.

Host:
MSH|^~\&|host||cobas 8000||20180105100007||RSREQ|10020||2.5||||NE||UNICODE UTF-8|
QPD|RSREQ|10020|120002|F||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000||host||20180105100007||OUL^R22^BATCH|22533||2.5||||AL||UNICODE UTF-8|
PID|1||||^||||
SPM||120002||S1||not|||||P|||^^^^|||20171127183629||||||||||SC|
SAC||||||||||50749|1|
OBR|1|||990|
TQ1|1||||||||R|
OBX|1||990||0.06|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20171127183657|bmserv^SYSTEM||771|ISE^1^MU1#I
SE#1#1^3|20171127183712|
TCD|990|1|

14 HL7 communication examples

NTE|1|I|0|I|
OBR|3||||
TQ1|1||||||||R|
OBX|1||989||2.0|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20171127183657|bmserv^SYSTEM||770|ISE^1^MU1#IS
E#1#1^3|20171127183712|
TCD|989|1|
NTE|1|I|0|I|

No results found
In this section the host sends a request for final results for
a sample, but the data manager cannot find any results.

Host:
MSH|^~\&|host||cobas 8000||20180105100009||RSREQ|10018||2.5||||NE||UNICODE UTF-8|
QPD|RSREQ|10018|120002|F||||||S1|
RCP|I|1|R|

DM:
<No Reply>

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 352 Result requests from the host

Sample not found

In this section the host sends a request for final results for
a sample, but the data manager cannot find any record of
the sample.

Host:
MSH|^~\&|host||cobas 8000||20180105100009||RSREQ|10018||2.5||||NE||UNICODE UTF-8|
QPD|RSREQ|10017|120002|F||||||S1|
RCP|I|1|R|

DM:
<No Reply>

Result request with a sequence number

In this section the host sends a request for results for a
sample with sequence number 1031. (See fields QPD-3.2
and SPM-2.2.) This functionality was introduced in
version 1.02.03.

Host:
MSH|^~\&|host||cobas 8000||20180105105142||RSREQ|10022||2.5||||NE||UNICODE UTF-8|
QPD|RSREQ|^1031|120002|||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000||host||20180105105142||OUL^R22^BATCH|22578||2.5||||AL||UNICODE UTF-8|
14 HL7 communication examples

PID|1||||^||||
SPM||^1031||S1||not|||||P|||^^^^|||20171127183629||||||||||SC|
SAC||||||||||50749|1|
OBR|1|||990|
TQ1|1||||||||R|
OBX|1||990||0.06|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20171127183657|bmserv^SYSTEM||771|ISE^1^MU1#I
SE#1#1^3|20171127183712|
TCD|990|1|
NTE|1|I|0|I|
OBR|3||||
TQ1|1||||||||R|
OBX|1||989||2.0|mmol/L|^TECH~^NORM~^CRIT~^USER||||F|||20171127183657|bmserv^SYSTEM||770|ISE^1^MU1#IS
E#1#1^3|20171127183712|
TCD|989|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Result requests from the host 353

Result request with an expired sample

If your site uses sample lifetime, there may be an expired
sample in the data manager database that has the same
sample ID as a current sample. Normally this will not
cause any confusion. If you send a result request, the
data manager only sends a test result message for a
unique current sample.

Host:
MSH|^~\&|host||cobas 8000||20180105105744||RSREQ|10024||2.5||||NE||UNICODE UTF-8|
QPD|RSREQ|10024|120011|||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000||host||20180105105744||OUL^R22^BATCH|22589||2.5||||AL||UNICODE UTF-8|
PID|1||||^||||
SPM||120011||S1||not|||||P|||^^^^|||20171127193726||||||||||SC|
SAC||||||||||50731|5|
OBR|1|||10001|
TQ1|1||||||||R|
OBX|1||10001||0.0129|μIU/mL|^TECH~^NORM~^CRIT~^USER||||C|||20171129165937|bmserv^SYSTEM||3334|e801^1
^MU1#e801#2#1^9|20171129171810|
TCD|10001|1|
SID|10001^^1310001^ASY^18^0|226387|44872|
NTE|1|I|0|I|
OBX|2||10001||725.5584|count|^TECH~^NORM~^CRIT~^USER||||C|||20171129165937|bmserv^SYSTEM||EFS|e801^1
^MU1#e801#2#1^9|20171129171810|
TCD|10001|1|
NTE|1|I|0|I|
OBX|3||10001||-117.694|count|^TECH~^NORM~^CRIT~^USER||||C|||20171129165937|bmserv^SYSTEM||EFV|e801^1

14 HL7 communication examples

^MU1#e801#2#1^9|20171129171810|
TCD|10001|1|
NTE|1|I|0|I|
OBX|4||10001||214.7800|count|^TECH~^NORM~^CRIT~^USER||||C|||20171129165937|bmserv^SYSTEM||EFC|e801^1
^MU1#e801#2#1^9|20171129171810|
TCD|10001|1|
NTE|1|I|0|I|
OBX|5||10001||11608.00|count|^TECH~^NORM~^CRIT~^USER||||C|||20171129165937|bmserv^SYSTEM||PMT|e801^1
^MU1#e801#2#1^9|20171129171810|
TCD|10001|1|
NTE|1|I|0|I|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 354 Order requests from the host

Order requests from the host

In the examples in this section, the host sends order
requests.

In this section
Request for all tests (354)
Request for open tests (354)
No tests found (355)
Sample not found (355)
Order request with a sequence number (355)

Request for all tests

In this section the host sends a request for all tests for a
sample.

Host:
MSH|^~\&|host||cobas 8000||20180105111033||TSREQ|10028||2.5||||NE||UNICODE UTF-8|
QPD|TSREQ|10028|100903|||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000||host||||OML^O33|22603||2.5||||AL||UNICODE UTF-8|
SPM||100903||S1||||||||||^^^^|||||||||||||SC|
OBR||||22000^1|
OBR||||22001^1|
14 HL7 communication examples

Request for open tests

In this section the host sends a request for open tests for
a sample. Note that rack type is required in QPD-10.

Host:
MSH|^~\&|host||cobas 8000||20180105111033||TSREQ|10028||2.5||||NE||UNICODE UTF-8|
QPD|TSREQ|10028|100903|O||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000||host||||OML^O33|22603||2.5||||AL||UNICODE UTF-8|
SPM||100903||S1||||||||||^^^^|||||||||||||SC|
OBR||||22001^1|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Order requests from the host 355

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.
Note that rack type is required in QPD-10.

Host:
MSH|^~\&|host||cobas 8000||20180105112255||TSREQ|10030||2.5||||NE||UNICODE UTF-8|
QPD|TSREQ|10030|100904|||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000||host||||OML^O33|22618||2.5||||AL||UNICODE UTF-8|
SPM||1009035||S1||||||||||^^^^||||||||||||||

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||20180105112255||TSREQ|10031||2.5||||NE||UNICODE UTF-8|
QPD|TSREQ|10031|100888|||||||S1|
RCP|I|1|R|

DM:
MSH|^~\&|cobas 8000||host||||OML^O33|22619||2.5||||AL||UNICODE UTF-8|
SPM||100888||S1||||||||||^^^^||||||||||||||

14 HL7 communication examples

Order request with a sequence number
In this section the host sends an order request for a
sample with sequence number 1031. (See fields QPD-3.2
and SPM-2.2.) This functionality was introduced in
version 1.02.03.

q Orders with a sequence number are handled the

same way as orders with a sample ID, in respect of test or
sample not found etc.

Host:
MSH|^~\&|host||cobas 8000||20170711122805||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|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 356 Order requests from the host

OBR||||8706^1|
14 HL7 communication examples

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Instrument status and test availability messages 357

Instrument status and test availability

messages
In the examples in this section, the host sends requests
for instrument status and test availability information, and
the data manager sends this information. If forward
instrument status mode is enabled, the data manager will
send this information unsolicited.
u For more information, see Forward instrument status
mode (HL7 only) (105)
u For more information on masking, see Masking (83)

In this section
Test availability request (357)
Test availability update (357)
Instrument status request (359)
Instrument status update (359)

Test availability request

The host sends this message to the data manager to
request test availability information. The data manager
responds with an equipment inventory update message.

14 HL7 communication examples

MSH|^~\&|host||cobas 8000||20180105113727||INR^U06|30115042493||2.5||||NE||UNICODE UTF-8|
EQU|DM#DM#0#0|20180105113727|

Test availability update

This message contains test availability information, and is
sent by the data manager to the host. The message lists
the availability status of all tests currently installed on the
data manager.

If forward instrument status mode is disabled, the data

manager sends this message in response to an
equipment inventory request message from the host. If
enabled, the data manager sends this message as soon
as it receives updated test availability information from
the control unit.

When a cobas e flow test is masked or unmasked in the

data manager, a test availability update message is sent
showing the status of the embedded tests.

MSH|^~\&|cobas 8000||host||20180105113727||INU^U05|22633||2.5||||AL||UNICODE UTF-8|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 358 Instrument status and test availability messages

EQU|DM#DM#0#0|20180105113727|
INV|10001|OK^OK_STATUS|
INV|10002|OK^OK_STATUS|
INV|10003|OK^OK_STATUS|
INV|10009|OK^OK_STATUS|
INV|10015|OK^OK_STATUS|
INV|10018|OK^OK_STATUS|
INV|10026|OK^OK_STATUS|
INV|10039|OK^OK_STATUS|
INV|10049|OK^OK_STATUS|
INV|10055|OK^OK_STATUS|
INV|10070|OK^OK_STATUS|
INV|10074|OK^OK_STATUS|
INV|10079|OK^OK_STATUS|
INV|10083|OK^OK_STATUS|
INV|10088|OK^OK_STATUS|
INV|10092|OK^OK_STATUS|
INV|10095|OK^OK_STATUS|
INV|10100|OK^OK_STATUS|
INV|10104|OK^OK_STATUS|
INV|10121|NW^NOT_AVAILABLE_WARNING|
INV|10126|OK^OK_STATUS|
INV|11004|OK^OK_STATUS|
INV|11005|OK^OK_STATUS|
INV|11006|OK^OK_STATUS|
INV|11013|OK^OK_STATUS|
INV|11014|NW^NOT_AVAILABLE_WARNING|
INV|11039|OK^OK_STATUS|
INV|11055|OK^OK_STATUS|
INV|11074|OK^OK_STATUS|
INV|11104|OK^OK_STATUS|
INV|11149|OK^OK_STATUS|
14 HL7 communication examples

INV|11150|OK^OK_STATUS|
INV|11151|OK^OK_STATUS|
INV|11155|OK^OK_STATUS|
INV|12001|OK^OK_STATUS|
INV|12008|OK^OK_STATUS|
INV|12019|OK^OK_STATUS|
INV|16004|OK^OK_STATUS|
INV|16007|OK^OK_STATUS|
INV|17016|OK^OK_STATUS|
INV|20001|OK^OK_STATUS|
INV|22000|OK^OK_STATUS|
INV|22001|OK^OK_STATUS|
INV|8057|OK^OK_STATUS|
INV|8059|OK^OK_STATUS|
INV|8060|OK^OK_STATUS|
INV|8220|OK^OK_STATUS|
INV|8253|OK^OK_STATUS|
INV|8418|OK^OK_STATUS|
INV|8480|OK^OK_STATUS|
INV|8552|OK^OK_STATUS|
INV|8571|OK^OK_STATUS|
INV|8661|OK^OK_STATUS|
INV|8685|OK^OK_STATUS|
INV|8690|OK^OK_STATUS|
INV|8698|OK^OK_STATUS|
INV|8700|OK^OK_STATUS|
INV|8704|OK^OK_STATUS|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Instrument status and test availability messages 359

INV|8714|OK^OK_STATUS|
INV|8717|OK^OK_STATUS|
INV|8731|OK^OK_STATUS|
INV|8734|OK^OK_STATUS|
INV|8781|OK^OK_STATUS|
INV|989|OK^OK_STATUS|
INV|990|OK^OK_STATUS|
INV|991|OK^OK_STATUS|

Instrument status request

The host sends this message to the data manager to
request instrument status information. The data manager
responds with an equipment status update message.

MSH|^~\&|host||cobas 8000||20180105114134||ESR^U02|30123830908||2.5||||AL||UNICODE UTF-8|

EQU|DM#DM#0#0|20180105114134|

Instrument status update

This message contains instrument status information, and
is sent by the data manager to the host.

If forward instrument status mode is disabled, the data

manager sends this message in response to an
equipment status request message from the host. If

14 HL7 communication examples

enabled, the data manager sends this message as soon
as it receives updated instrument status information from
the control unit.

MSH|^~\&|cobas 8000||host||20180105114134||ESU^U01|22637||2.5||||AL||UNICODE UTF-8|

EQU|DM#DM#0#0|20180105114134|OP^NORMAL_OPERATION^LECIS^27^Operation^Hitachi|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 360
14 HL7 communication examples Instrument status and test availability messages

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Appendices

15 Data alarms.............................................................................................................363
16 Instrument alarms ................................................................................................423
17 Result message codes for cobas e flow tests..........................................439
18 Using MODULAR PRE-ANALYTICS...............................................................445
19 Identifying patient samples by sequence number...................................455
20 Preparing the host communication ...............................................................467
21 Text encoding tables ...........................................................................................487

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 363
Table of contents

Data alarms 15

In this chapter 15
List of numerical code data alarms and output
characters on the control unit . . . . . . . . . . . . . . . . . . . 367
List of data alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Data alarms of ISE tests. . . . . . . . . . . . . . . . . . . . . . . . . 372
ADC.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Calc.? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Cal.E (sample flag) . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Cal.I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
ClcT.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
CmpT.? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
CmpT.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Edited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
< >ISE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
>I.H. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
>I.HI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
>I.I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
>I.L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
>I.LH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
>I.LHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
>I.LI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
ISE.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
ISE.N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
MIXLOW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
na.LHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Over.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Reag.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
>Rept/<Rept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Samp.C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Samp.O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
15 Data alarms

Samp.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
< >Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
>Test/<Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Data alarms of photometric tests . . . . . . . . . . . . . . . . . 383
>Abs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
ADC.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Calc.? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Cal.E (sample flag) . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Cal.I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
ClcT.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
CmpT.? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
364
Table of contents

CmpT.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
>Cuvet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Det.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Edited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
>I.H. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
>I.HI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
>I.I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
>I.L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
>I.LH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
>I.LHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
>I.LI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
>Kin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
>Lin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
MIXLOW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
MIXSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
na.LHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
OBS.RM (c 702 module only) . . . . . . . . . . . . . . . . . 389
OBS.RR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Over.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
>Proz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
>React . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
ReagEx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Reag.S (c 701/c 702 modules only) . . . . . . . . . . . . 391
>Rept/<Rept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Samp.? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Samp.C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Samp.O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Samp.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
>Test/<Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Data alarms of immunology tests. . . . . . . . . . . . . . . . . 394
ADC.E (e 801 module only) . . . . . . . . . . . . . . . . . . . 394
Calc.? (e 602 module only) . . . . . . . . . . . . . . . . . . . 394
Cal.E (sample flag) . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Cal.I (e 602 module only). . . . . . . . . . . . . . . . . . . . . 395
CarOvr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Cell.T. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Clot.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
>Curr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Curr.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Edited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
15 Data alarms

eFlow.E (e 801 module only) . . . . . . . . . . . . . . . . . . 397

eFlow.W (e 801 module only) . . . . . . . . . . . . . . . . . 397
>I.H (e 602 module only) . . . . . . . . . . . . . . . . . . . . 397
>I.HI (e 602 module only) . . . . . . . . . . . . . . . . . . . . 398
>I.I (e 602 module only) . . . . . . . . . . . . . . . . . . . . . 398
>I.L (e 602 module only) . . . . . . . . . . . . . . . . . . . . . 398
>I.LH (e 602 module only) . . . . . . . . . . . . . . . . . . . 398
>I.LHI (e 602 module only) . . . . . . . . . . . . . . . . . . . 398
>I.LI (e 602 module only) . . . . . . . . . . . . . . . . . . . . 399
Inc.T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
na.LHI (e 602 module only). . . . . . . . . . . . . . . . . . . 399
OBS.RR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 365
Table of contents

Over.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
ReagEx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Reag.F. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Reag.H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Reag.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Reag.T. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
>Rept/<Rept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Samp.B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Samp.C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Samp.O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Samp.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
<SigL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
SLLD.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
SLLD.N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
SysR.S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
SysR.T. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
>Test/<Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
WB.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
WBSS.T (e 801 module only). . . . . . . . . . . . . . . . . . 405
WB.T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Alarms for calibrations. . . . . . . . . . . . . . . . . . . . . . . . . . 406
Cal.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Cond.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Diff.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Duplicate error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Dup.E (cobas c modules) . . . . . . . . . . . . . . . . . 409
Dup.E (cobas e modules) . . . . . . . . . . . . . . . . . 409
IStd.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Mono.E (e 602 module only) . . . . . . . . . . . . . . . . . . 410
Prep.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Rsp1.E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Rsp2.E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
S1A.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
SD.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Sens.E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
>Sig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
<Sig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Sig.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Slop.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Std.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
15 Data alarms

Std.E (ISE module) . . . . . . . . . . . . . . . . . . . . . . . 414

Std.E (cobas c modules). . . . . . . . . . . . . . . . . . 415
Sys.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Data alarm for QC materials . . . . . . . . . . . . . . . . . . . . . 417
QCErr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
List of data alarms for QC measurements. . . . . . . 417
Rerun test list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Alarm priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
366
Table of contents
15 Data alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 List of numerical code data alarms and output characters on the control unit 367

List of numerical code data alarms and

output characters on the control unit
This table presents a brief description of each data alarm,
and the output character of each data alarm on the
control unit.
u For alarm priorities, see Alarm priorities (421).

No. Name Output character on control unit

0 (No Alarm)
1 ADC abnormal ADC.E
2 ABS Cell blank abnormal >Cuvet
3 Sample short Samp.S
4 Reagent short Reag.S
5 ABS over >Abs
6 Prozone Error >Proz
7 Reaction limit over >React
8 Reaction limit over (2nd ..) >React
9 Reaction limit over (3rd ..) >React
10 Linearity abnormal 1 >Lin
11 Linearity abnormal 2 >Lin
12 S1ABS abnormal S1A.E
13 DUPLICATE error Dup.E
14 STANDARD error Std.E
15 SENSITIVITY error Sens.E
16 CALIB error Cal.E
17 SD limit error SD.E
18 ISE Noise error ISE.N
19 ISE Voltage Level error ISE.E
20 Slope abnormal Slop.E
21 Preparation abnormal Prep.E
22 IS concentration abnormal IStd.E
23 ISE Sample range over < >Test
24 Data error in comp. Test CmpT.E
25 Unable to calculate comp. Test CmpT.?
15 Data alarms

26 Technical Limit over (upper) >Test

27 Technical Limit over (lower) <Test
35 QC error 1 Q3SD
36 QC error 2 Q2.5SD
37 Calculation test error ClcT.E
38 Overflow Over.E
39 Calculation not possible Calc.?
40 Outside of expected value (upper) [Obsolete] H
41 Outside of expected value (lower) [Obsolete] L
42 Edited test Edited
y Meaning of data alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
368 List of numerical code data alarms and output characters on the control unit

No. Name Output character on control unit

43 Calibration result abnormal (Sample Flag) Cal.E
44 Repeat limit over (upper) >Rept
45 Repeat limit over (lower) <Rept
46 ABS maximum over (nonLin curve) Samp.?
47 Calibration result invalid Cal.I
48
49
50
51 Response(ISE) abnormal 1 Rsp1.E
52 Response(ISE) abnormal 2 Rsp2.E
53 Conditioning(ISE) abnormal Cond.E
54
55 ISE range over <>ISE
56 Kinetic unstable (Prozone error 2) >Kin
57 Serum index 1 interference >Index
58 Serum index multiple interference >Index
59 Stop mixing MIXSTP
60 Mixing current low MIXLOW
61
62 System reagent short SysR.S
63 AB level range over (Assay Buffer) run start >AB
64 AB level check error AB.E
65 Current range over (run start) >Curr
66 Current range check error Curr.E
67 Sample hovering Samp.H
68 Sample air bubble Samp.B
69 Reagent hovering Reag.H
70 Reagent film detection Reag.F
71 Potential carry over CarOvr
72 Sample clot Samp.C
73 Carry over detergent short Det.S
74 Reagent disk temperature Reag.T
75 Incubator temperature Inc.T
76 System reagent temperature SysR.T
77 Cell temperature Cell.T
15 Data alarms

78 Missing value ------

79 System errors Sys.E
80 Monotony of curve Mono.E
81 Minimum signal <Sig
82 Maximum signal >Sig
83 Sample carry over for modules Samp.O
84 Minimum/Maximum signal Sig.E
85 Minimum acceptable difference Diff.E
86 Sample LLD abnormal SLLD.E
87 Sample LLD noise SLLD.N
y Meaning of data alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 List of numerical code data alarms and output characters on the control unit 369

No. Name Output character on control unit

88
89
90
91
92
93 Washing buffer temperature WB.T
94 Washing buffer short WB.S
95 Clot pressure sensor ADC (underflow) Clot.E
96 Clot pressure sensor ADC (overflow) Clot.E
97 Clot pressure abnormal Clot.E
98 Sample pipettor air bubble Samp.B
99 Current range over (operation) >Curr
100 Low level signal <SigL
101 Reagent Expired Date ReagEx
102 QC error QCErr
103 Serum index interference lipaemia >I.L
104 Serum index interference hemolysis >I.H
105 Serum index interference icteric >I.I
106 Serum index interference lipaemia / hemolysis >I.LH
107 Serum index specific interference lipaemia / icteric >I.LI
108 Serum index interference hemolysis / icteric >I.HI
109 Serum index interference lipaemia / hemolysis / icteric >I.LHI
110 Serum index measurement not performed na.LHI
111 On board stability limit over on Reagent Manager OBS.RM
112 On board stability limit over on Reagent Rotor OBS.RR
113 Embedded test in cobas e flow test has been masked Mask
y Meaning of data alarms

15 Data alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
370 List of data alarms

List of data alarms

The following table displays the data alarms applicable to
test results and modules, and their presentation (flag) in
the user interface and on reports.

q Calibration and QC alarms are not included in the

table below.
u For overviews about calibration and QC alarms, see:
Alarms for calibrations (406)
Data alarm for QC materials (417)

Data alarm Alarm ISE c 701 c 702 c 502 e 801 e 602

>Abs ABS over – l l l – –
ADC.E ADC abnormal l l l l l –
Calc.? Calculation not possible l l l l l l
Cal.E (sample flag) Calibration result abnormal (sample flag) l l l l l l
Cal.I Calibration result invalid l l l l – l
CarOvr Potential carry over – – – – l l
Cell.T Cell temperature – – – – l l
ClcT.E Calculation test error l l l l – –
Clot.E Clot pressure abnormal – – – – l l
CmpT.? Unable to calculate comp. test (compensation test) l l l l – –
CmpT.E Data error in comp. test (compensation test) l l l l – –
>Curr Current range over – – – – l l
Curr.E Current range check error – – – – l l
>Cuvet ABS Cell blank abnormal – l l l – –
Det.S Carry over detergent short – l l l – –
Edited Edited test l l l l l l
EFlow.E Standard alarm for cobas e flow tests – – – – l –
EFlow.W Generic cobas e flow test warning – – – – l –
< >ISE ISE range over l – – – – –
>I.H Serum index interference hemolysis l l l l – l
>I.HI Serum index interference hemolysis/icteric l l l l – l
>I.I Serum index interference icteric l l l l – l
>I.L Serum index interference lipaemia l l l l – l
15 Data alarms

>I.LH Serum index interference lipaemia/hemolysis l l l l – l

>I.LHI Serum index interference lipaemia/hemolysis/icteric l l l l – l
>I.LI Serum index interference lipaemia/icteric l l l l – l
Inc.T Incubator temperature – – – – l l
ISE.E ISE voltage level error l – – – – –
ISE.N ISE noise error l – – – – –
>Kin Kinetic unstable (Prozone error 2) – l l l – –
>Lin Linearity abnormal – l l l – –
MIXLOW Mixing current low l l l l – –
MIXSTP Stop mixing l l l l – –
y List of sample flags
Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 List of data alarms 371

Data alarm Alarm ISE c 701 c 702 c 502 e 801 e 602

na.LHI Serum index measurement not performed l l l l – l
OBS.RM On-board stability limit over on reagent manager – – l – – –
OBS.RR On-board stability limit over on reagent rotor – l l l l l
Over.E Overflow l l l l l l
>Proz Prozone error – l l l – –
>React Reaction limit over – l l l – –
ReagEx Reagent expired date – l l l l l
Reag.F Reagent film detection – – – – l l
Reag.H Reagent hovering – – – – l l
Reag.S Reagent short l l l – l l
Reag.T Reagent disk temperature – – – – l l
>Rept/<Rept Repeat limit over (upper)/(lower) l l l l l l
Samp.? ABS maximum over (non-lin curve) – l l l – –
Samp.B Sample air bubble – – – – l l
Samp.C Sample clot l l l l l l
Samp.O Sample carry over for modules l l l l l l
Samp.S Sample short l l l l l l
<SigL Minimum signal – – – – l l
SLLD.E Sample LLD abnormal – – – – l l
SLLD.N Sample LLD noise – – – – l l
SysR.S System reagent short – – – – l l
SysR.T System reagent temperature – – – – l l
< >Test ISE sample range over l – – – – –
>Test/<Test Technical limit over (upper)/(lower) l l l l l l
WB.S Washing buffer short – – – – l l
WB.T Washing buffer temperature – – – – l l
y List of sample flags

15 Data alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
372 Data alarms of ISE tests

Data alarms of ISE tests

Data alarm ISE Data alarm ISE

ADC.E l >I.LHI l
Calc.? l >I.LI l
Cal.E (sample flag) l ISE.E l
Cal.I l ISE.N l
ClcT.E l MIXLOW l
CmpT.? l na.LHI l
CmpT.E l Over.E l
Edited l Reag.S l
< >ISE l >Rept/<Rept l
>I.H l Samp.C l
>I.HI l Samp.O l
>I.I l Samp.S l
>I.L l < >Test l
>I.LH l >Test/<Test l
y Data alarm list ISE

ADC.E
Alarm ADC abnormal

Description The analog/digital converter is not working normally.

Cause Numerical conversion of the electromotive force is

abnormal.

Calc.?
Alarm Calculation not possible
15 Data alarms

Description The denominator becomes zero in calculation.

1. During calculation, the denominator became zero.
2. An overflow occurred in logarithmic or exponential
calculation.
3. Result was left blank.

Cause Internal calculation error has occurred.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of ISE tests 373

Cal.E (sample flag)

Alarm Calibration result abnormal (sample flag)

Description No calibration data or previous calibration data used.

q Cal.E appears on each QC and patient sample for

the affected test until the problem is resolved.

Cause An alarm, for example, Std.E, ISE.E, ISE.N, occurred during

calibration.

Cal.I
Alarm Calibration result invalid

Description The result was generated with an invalid transferred

calibration.

Cause The instrument requested a changeover calibration due to

a change in a reagent cassette for this test, but the
calibration was not performed. Therefore, the reagent
cassette has an Invalid calibration until the calibration is
successfully performed.

This flag is attached to results if a test requires to be

calibrated after replacement of a reagent cassette and
the automatic calibration masking is switched off.

ClcT.E
Alarm Calculation test error

Description Calculation error has occurred.

15 Data alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
374 Data alarms of ISE tests

Cause A data alarm has occurred for a test needed in the

calculation. However, the ClcT.E alarm is not attached to
the calculated test if one of the following alarms occurred
for a test needed in the calculation:
• Overflow (Over.E)
• Sample carry over for modules (Samp.O)
• Reagent expired date (ReagEx)
• On-board stability limit over on reagent manager
(OBS.RM)
• On-board stability limit over on reagent rotor
(OBS.RR)
• Serum index data alarms

CmpT.?
Alarm Unable to calculate comp. test (compensation test)

Description During test-to-test compensation calculation, the

denominator became zero. Blank space is left in the
report.

Cause 1. The test used for test-to-test compensation has not

been measured yet.
2. A test used for test-to-test compensation has a data
alarm Calculation not possible (Calc.?) or Data error in
comp. test (compensation test) (CmpT.E).
3. A test used in the compensation formula has a data
alarm that leaves the result blank (for example,
Samp.S, Reag.S).

CmpT.E
Alarm Data error in comp. test (compensation test)

Description 1. In test-to-test compensation calculation, a data alarm

other than those shown below is indicated for the
15 Data alarms

compensation test data.

2. Calculation not possible, Unable to calculate comp.
test (compensation test), Overflow, QC error and
outside of expected value.

Cause The test to be used for compensation has a data alarm.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of ISE tests 375

Edited
Alarm Edited test

Description An edited first result or rerun result is marked with an

Edited alarm on the Data Review submenu. The alarm is
also printed on the patient report.

Cause The result has been manually changed.

15 Data alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
376 Data alarms of ISE tests

< >ISE
Alarm ISE range over

Description If the result is inside the following ranges, the < >ISE flag
is attached to the result. This alarm is effective for urine
sample only.

Na+ 10 to 60 mmol/L

K+ This alarm is not issued.

Cl- 10 to 60 mmol/L

Cause The sample concentration is low.

>I.H
Alarm Serum index interference hemolysis

Description The hemolytic value is greater than the specified

reference value.

Cause A highly hemolytic sample was measured.

>I.HI
Alarm Serum index interference hemolysis/icteric

Description The hemolytic and icteric values are greater than the
specified reference values.

Cause A highly hemolytic and icteric sample was measured.

>I.I
15 Data alarms

Alarm Serum index interference icteric

Description The icteric value is greater than the specified reference

value.

Cause A highly icteric sample was measured.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of ISE tests 377

>I.L
Alarm Serum index interference lipaemia

Description The lipemic value is greater than the specified reference

value.

Cause A highly lipemic sample was measured.

>I.LH
Alarm Serum index interference lipaemia/hemolysis

Description The lipemic and hemolytic values are greater than the
specified reference values.

Cause A highly lipemic and hemolytic sample was measured.

>I.LHI
Alarm Serum index interference lipaemia/hemolysis/icteric

Description The lipemic, hemolytic and icteric values are greater than
the specified reference values.

Cause A highly lipemic, hemolytic and icteric sample was

measured.

>I.LI
Alarm Serum index interference lipaemia/icteric

Description The lipemic and icteric values are greater than the
specified reference values.
15 Data alarms

Cause A highly lipemic and icteric sample was measured.

ISE.E
Alarm ISE voltage level error

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
378 Data alarms of ISE tests

Description During measurement of internal reference, the measured

voltages were not within the following ranges for ISE IS:

Na+ -90.0 to -10 mV

K+ -90.0 to -10 mV

Cl- 80.0 to 160 mV

If an ISE.E data alarm is detected during an ISE

measurement, the results of the 2 other ISE tests may also
be effected. Therefore, the ISE.E data alarm is attached to
all ISE test results for this sample.

Cause • The reference electrode is deteriorated.

• Insulation is poor due to liquid leakage from the
reference electrode mounting section.
• ISE IS is deteriorated.

ISE.N
Alarm ISE noise error

Description In ISE measurement, the fluctuation in electromotive force

exceeds the following value:

Na+ 0.7 mV

K+ 1.0 mV

Cl- 0.8 mV

If an ISE.N data alarm is detected during an ISE

measurement, the results of the 2 other ISE tests may also
be effected. Therefore, the ISE.N data alarm is attached to
all ISE test results for this sample. The ISE.N data alarm
takes priority over ISE.E.

Cause • Entry of air bubbles for lack of reagent

• Entry of air bubbles due to improper attachment of
15 Data alarms

electrode
• Entry of air bubbles through aspiration tube
• Poor insulation of waste solution block
• Poor insulation due to liquid leakage from sipper
pipetter

MIXLOW
Alarm Mixing current low

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of ISE tests 379

Description The ultrasonic monitor value is lower than the reference

value.

Cause The mixer is deteriorated.

Remedy Contact your Roche Service representative.

na.LHI
Alarm Serum index measurement not performed

Description The serum index measurement could not be performed

for the test.

Cause The serum index measurement could not be performed

for the test for some reason.

Example 1: The remaining reagent volume for serum

index testing is insufficient.

Example 2: The test is a high-priority immunology test

and the system is in the auto rerun mode. In that case, the
serum index measurement cannot be performed before
the measurement of the high-priority immunology test.

Over.E
Alarm Overflow

Description Display is not possible because the result exceeds 6 digits

Cause The result contains more than 4 digits without decimal

point and minus sign.

Examples for the maximum number of digits that can be

presented: -0.001 or 12.34 or 9999.
15 Data alarms

Reag.S
Alarm Reagent short

Description There is insufficient ISE reagent volume. The liquid level

cannot be detected in the reagent bottle.

Cause There is not enough reagent in the reagent bottle.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
380 Data alarms of ISE tests

>Rept/<Rept
Alarm Repeat limit over (upper)/(lower)

Description The result falls outside the repeat limit range

programmed on Utility > Application > Range.

Cause The sample concentration is higher (>Rept) or lower

(<Rept) than the set value.

Samp.C
Alarm Sample clot

Description The specified volume of sample is not aspirated.

Cause A clot is detected.

Samp.O
Alarm Sample carry over for modules

Description Possible sample carryover must be considered when you

check the results of the additional test(s) because special
wash was not performed in the first run.

Cause An additional test that requires a special wash was

performed and the module did not perform any special
wash for the sample in the first run.

Samp.S
Alarm Sample short
15 Data alarms

Description The liquid level cannot be detected in the sample

container.

Cause The sample volume is insufficient in the sample container.

< >Test
Alarm ISE sample range over

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of ISE tests 381

Description If the result is outside the following ranges, the flag ISE
sample range over is issued.

For serum/plasma samples:

Na+ 10–250 mmol/L

K+ 1–100 mmol/L

Cl- 10–250 mmol/L

For urine samples with normal sample volume:

Na+ 10–350 mmol/L

K+ 3–100 mmol/L

Cl- 10–350 mmol/L

For urine samples with increased sample volume:

Na+ 20–60 mmol/L

K+ The alarm is always attached independent of the

result level.

Cl- 20–60 mmol/L

Cause • The electrode is deteriorated.

• The flow path is contaminated.
• Sample concentration is too high or too low.

>Test/<Test
Alarm Technical limit over (upper)/(lower)

15 Data alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
382 Data alarms of ISE tests

Description The sample concentration is outside the technical limit

entered on Utility > Application > Range (ISE tests
only).

For serum/plasma samples:

• Over the technical limit: If the result is greater than the
upper limit, a >Test flag is attached to the result.
• Under the technical limit: If the result is less than the
lower limit, a <Test flag is attached to the result.
• In both cases, a rerun test selection is generated and
an automatic rerun is executed with normal sample
volume (15 μL).

For urine samples, this alarm is not generated as long as

no values are entered in the Technical Limit fields on
Utility > Application > Range. Instead, an < >ISE
alarm is attached if the result is outside the measuring
range.

Cause Sample concentration is too high or too low.

15 Data alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of photometric tests 383

Data alarms of photometric tests

Data alarm c 701/c 702 c 502 Data alarm c 701/c 702 c 502
>Abs l l >Kin l l
ADC.E l l >Lin l l
Calc.? l l MIXLOW l l
Cal.E (sample flag) l l MIXSTP l l
Cal.I l l na.LHI l l
ClcT.E l l OBS.RM c 702: l –
c 701: –
CmpT.? l l OBS.RR l l
CmpT.E l l Over.E l l
>Cuvet l l >Proz l l
Det.S l l >React l l
Edited l l ReagEx l l
>I.H l l Reag.S l –
>I.HI l l >Rept/<Rept l l
>I.I l l Samp.? l l
>I.L l l Samp.C l l
>I.LH l l Samp.O l l
>I.LHI l l Samp.S l l
>I.LI l l >Test/<Test l l
y Data alarm list c 701/c 702 and c 502

>Abs
Alarm ABS over

Description The absorbance value is checked for each wavelength. If

a measured absorbance is beyond the limit of 33 000
absorbance units, this data alarm is attached to the result.

Cause • The sample concentration is too high or the sample is

lipemic.
15 Data alarms

• The reagent has not been stored or handled properly.

• Obstructions are in the optical path of the photometer.

ADC.E
Alarm ADC abnormal

Description The analog-digital converter is not working normally.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
384 Data alarms of photometric tests

Cause 1. Numerical conversion is abnormal.

2. The cell count is abnormal.

Calc.?
Alarm Calculation not possible

Description The denominator becomes zero in calculation.

• During calculation the denominator became zero.
• An overflow occurred in logarithmic or exponential
calculation.
• Result was left blank.

Cause Internal calculation error has occurred.

Cal.E (sample flag)

Alarm Calibration result abnormal (sample flag)

Description No calibration data or previous calibration data used.

q Cal.E appears on each QC and patient sample for

the affected test until the problem is resolved.

Cause Any alarm (for example, Std.E) occurred during

calibration.

Cal.I
Alarm Calibration result invalid

Description The result was generated with an invalid transferred

15 Data alarms

calibration.

Cause The instrument requested a changeover calibration due to

a change in a reagent cassette for this test, but the
calibration was not performed. Therefore, the reagent
cassette has an Invalid calibration until the calibration is
successfully performed.

This flag is attached to results if a test requires to be

calibrated after replacement of a reagent cassette and
the automatic calibration masking is switched off.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of photometric tests 385

ClcT.E
Alarm Calculation test error

Description Calculation error has occurred.

Cause A data alarm has occurred for a test needed in the

calculation. However, the ClcT.E alarm is not attached to
the calculated test if one of the following alarms occurred
for a test needed in the calculation:
• Overflow (Over.E)
• Sample carry over for modules (Samp.O)
• Reagent expired date (ReagEx)
• On-board stability limit over on reagent manager
(OBS.RM)
• On-board stability limit over on reagent rotor
(OBS.RR)
• Serum index data alarms

CmpT.?
Alarm Unable to calculate comp. test (compensation test)

Description During test-to-test compensation calculation, the

denominator became zero. Blank space is left in the
report.

Cause 1. The test used for test-to-test compensation has not

been measured yet.
2. A test used for test-to-test compensation has a data
alarm Calculation not possible (Calc.?) or Data error in
comp. test (compensation test) (CmpT.E).
3. A test used in the compensation formula has a data
alarm that leaves the result blank (for example,
Samp.S, Reag.S).
15 Data alarms

CmpT.E
Alarm Data error in comp. test (compensation test)

Description 1. In test-to-test compensation calculation, a data alarm

for the compensation test data is indicated.
2. Calculation not possible, Unable to calculate comp.
test (compensation test), Overflow, QC error and
outside of expected value.

Cause The test to be used for compensation has a data alarm.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
386 Data alarms of photometric tests

>Cuvet
Alarm ABS Cell blank abnormal

Description For a diluted test, the cell blank value of the second
reaction cell exceeds the reference by more than 0.1 Abs.
The reference is the stored value from the (4) Cell Blank
Measurement.

If a reaction cell fails the cell blank measurement, the

system excludes it from any measurements.

For diluted tests, however, the system uses 2 reaction

cells:
• 1st cell: Contains sample and diluent.
• 2nd cell: Used for discharging diluted sample from the
1st cell, adding reagent, and performing the
measurement.

The >Cuvet alarm indicates a failed cell blank

measurement for the 2nd cell.

Cause Reaction cells are contaminated or damaged.

Det.S
Alarm Carry over detergent short

Description If a special wash for the reagent probe is defined, the

reagent probe is immersed in the specified detergent
pack. This alarm occurs if the test is carried out even
though the detergent volume is insufficient.

Cause The residual volume of the special wash detergent is

insufficient.

Edited
15 Data alarms

Alarm Edited test

Description An edited first result or rerun result is marked with an

Edited alarm on the Data Review submenu. This also
prints on the patient report.

Cause The result has been manually changed.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of photometric tests 387

>I.H
Alarm Serum index interference hemolysis

Description The hemolytic value is larger than the specified reference

value.

Cause A highly hemolytic sample was measured.

>I.HI
Alarm Serum index interference hemolysis/icteric

Description The hemolytic and icteric values are larger than the
specified reference values.

Cause A highly hemolytic and icteric sample was measured.

>I.I
Alarm Serum index interference icteric

Description The icteric value is larger than the specified reference

value.

Cause A highly icteric sample was measured.

>I.L
Alarm Serum index interference lipaemia

Description The lipemic value is larger than the specified reference

value.
15 Data alarms

Cause A highly lipemic sample was measured.

>I.LH
Alarm Serum index interference lipaemia/hemolysis

Description The lipemic and hemolytic values are larger than the
specified reference values.

Cause A highly lipemic and hemolytic sample was measured.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
388 Data alarms of photometric tests

>I.LHI
Alarm Serum index interference lipaemia/hemolysis/icteric

Description The lipemic, hemolytic and icteric values are larger than
the specified reference values.

Cause A highly lipemic, hemolytic and icteric sample was

measured.

>I.LI
Alarm Serum index interference lipaemia/icteric

Description The lipemic and icteric values are larger than the
specified reference values.

Cause A highly lipemic and icteric sample was measured.

>Kin
Alarm Kinetic unstable (Prozone error 2)

Description The prozone check value exceeds the specified limit

value. (Reaction rate method)

Cause • The sample concentration is too high. The monotone

kinetic check value exceeds the specified limit for
other tests.
• The limit value is not set properly.

>Lin
Alarm Linearity abnormal
15 Data alarms

Description In a rate assay, the reaction linearity exceeds the

specified limit value.

Cause • The photometer lamp has deteriorated.

• The linearity check value is not set properly.
• The sample is extremely lipemic.
• The ultrasonic mixers are defective.
• Debris in the incubator bath.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of photometric tests 389

MIXLOW
Alarm Mixing current low

Description The ultrasonic monitor value is lower than the reference

value.

Cause The ultrasonic mixer is deteriorated.

MIXSTP
Alarm Stop mixing

Description There is no ultrasonic output for mixing.

Cause • The water level in the incubator bath is too low.

• The water level sensor of the incubator bath is
abnormal.

na.LHI
Alarm Serum index measurement not performed

Description The serum index measurement could not be performed

for the test.

Cause The serum index measurement could not be performed

for the test for some reason.

Example 1: The remaining reagent volume for serum

index testing is insufficient.

Example 2: The test is a high-priority immunology test

and the system is in the auto rerun mode. In that case, the
serum index measurement cannot be performed before
the measurement of the high-priority immunology test.
15 Data alarms

OBS.RM (c 702 module only)

Alarm On-board stability limit over on reagent manager

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
390 Data alarms of photometric tests

Description The on-board stability time for reagent packs in the buffer
rotor is set on Utility > Application > Range. The
setting is fixed for each test, for example, 24 hours (which
is the maximum value). The OBS.RM alarm is attached to
results if the on-board stability time of a reagent used for
this test expired for more than 30 minutes (e.g., 24 hours
+ 30 minutes).

Cause The system detected that the on-board stability time of

the reagent pack on the reagent manager expired.

OBS.RR
Alarm On-board stability limit over on reagent rotor

Description The on-board stability time of the reagent cassette used

for this test has expired while it was on the reagent disk.

Cause The system detected that the on-board stability time of

the reagent cassette expired.

Over.E
Alarm Overflow

Description Display is not possible because the result exceeds 6 digits

Cause • The K factor has more than 6 digits due to the use of a
wrong calibrator decimal point.
• The result contains more than 4 digits without decimal
point and minus sign.
Examples for the maximum number of digits that can
be presented: -0.001 or 12.34 or 9999.

>Proz
15 Data alarms

Alarm Prozone error

Description The prozone check value exceeds the specified limit

value. (Antigen readdition method)

Cause • The sample concentration is too high.

• The limit value is not set properly.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of photometric tests 391

>React
Alarm Reaction limit over

Description In a rate assay, the rate of change in main wavelength

absorbance exceeds the automatically corrected limit
value.

Cause • The sample concentration is too high.

• The reagent has been prepared improperly or
deteriorated.
• On Utility > Application > Analyze there is an
improper setting in the Abs. Limit drop-down list.

ReagEx
Alarm Reagent expired date

Description The alarm indicates that an expired reagent was used; the
test result is not guaranteed. The alarm can be inactivated
under Utility > System > Alarm Settings.

Cause The system detected an expired reagent onboard the

instrument.

Reag.S (c 701/c 702 modules only)

Alarm Reagent short

Description For photometric tests, there is insufficient reagent volume

in the cobas c pack, or the liquid level cannot be
detected in the cobas c pack.

Cause • The reagent volume remaining on board is insufficient.

• The reagent probe is not correctly aligned.
• The reagent probe wire is not correctly attached.
15 Data alarms

>Rept/<Rept
Alarm Repeat limit over (upper)/(lower)

Description The result falls outside the repeat limit range

programmed on Utility > Application > Range.

Cause The sample concentration is higher (>Rept) or lower

(<Rept) than the set value.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
392 Data alarms of photometric tests

Samp.?
Alarm ABS maximum over (non-lin curve)

Description The absorbance of a sample is found to be equal or

greater than the theoretical maximum absorbance (for
infinite analyte concentration). The result field will be left
blank on the report and Data Review submenu.

Cause The sample concentration is too high.

Samp.C
Alarm Sample clot

Description The specified volume of sample is not aspirated.

u For more information see Samp.C (380).

Samp.O
Alarm Sample carry over for modules.

Description Possible sample carryover must be considered when you

check the results of the additional test(s) because special
wash was not performed in the first run.

Cause An additional test that requires a special wash was

performed and the module did not perform any special
wash for the sample in the first run.

Samp.S
Alarm Sample short
15 Data alarms

Description The liquid level cannot be detected in the sample

container.
u For more information see Samp.S (380).

>Test/<Test
Alarm Technical limit over (upper)/(lower)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of photometric tests 393

Description The sample concentration is outside the technical range

entered on Utility > Application > Range.
• Over the technical limit: Value is greater than the
upper limit (>Test).
• Under the technical limit: Value is less than the lower
limit (<Test).

Cause Sample concentration is too high or too low.

15 Data alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
394 Data alarms of immunology tests

Data alarms of immunology tests

Data alarm e 801 e 602 Data alarm e 801 e 602

ADC.E l – ReagEx l l
Calc.? – l Reag.F l l
Cal.E (sample flag) l l Reag.H l l
Cal.I – l Reag.S l l
CarOvr l l Reag.T l l
Cell.T l l >Rept/<Rept l l
Clot.E l l Samp.B l l
>Curr l l Samp.C l l
Edited l l Samp.O l l
eFlow.E l – Samp.O l l
eFlow.W l – Samp.S l l
>I.H – l Samp.S l l
>I.HI – l <SigL l l
>I.I – l SLLD.E l l
>I.L – l SLLD.N l l
>I.LH – l SysR.S l l
>I.LHI – l SysR.T l l
>I.LI – l >Test/<Test l l
Inc.T l l WB.S l l
na.LHI – l WBSS.T l –
OBS.RR l l WB.T l l
Over.E l l
y Data alarm list for e 801/e 602 modules

ADC.E (e 801 module only)

Alarm ADC abnormal

Description The analog/digital converter is not working normally.

Cause Numerical conversion of the output from the

15 Data alarms

photomultiplier in a measuring channel is abnormal.

Calc.? (e 602 module only)

Alarm Calculation not possible

Description The denominator becomes zero in calculation.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of immunology tests 395

Cause Internal calculation error occurred.

Cal.E (sample flag)

Alarm Calibration result abnormal (sample flag)

Description No calibration data or previous calibration data used.

q Cal.E appears on each QC and patient sample for

the affected test until the problem is resolved.

Cause • There is no valid calibration stored in the system.

• The attempted calibration has failed.
• Previous calibration data was used to calculate this
result.

Cal.I (e 602 module only)

Alarm Calibration result invalid

Description The result was generated with an invalid transferred

calibration.

Cause The instrument requested a changeover calibration due to

a change in a reagent cassette for this test, but the
calibration was not performed. Therefore, the reagent
cassette has an Invalid calibration until the calibration is
successfully performed.

This flag is attached to results if a test requires to be

calibrated after replacement of a reagent cassette and
the automatic calibration masking is switched off.

CarOvr
15 Data alarms

Alarm Potential carry over

Description The signal level of this sample is low, a carryover in the

measuring cell may have occurred.

Cause Microbead carryover from the previous test may have

occurred.

Exception: The potential microbead carryover flag was

set, yet had no impact on a clinical decision.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
396 Data alarms of immunology tests

Cell.T
Alarm Cell temperature

Description Measuring cell temperature is out of range. The system

performs an initial check 30 minutes after start-up. The
temperature is checked continuously thereafter.

Cause • The reagent disk cover is open. Radiation of heat does

not work normally.
• The room temperature is out of range.

Clot.E
Alarm Clot pressure abnormal

Description In checking the pressure sensor, overflow data is

detected.

Cause There are air bubbles in the water flow tube.

>Curr
Alarm Current range over

Description The current from the measuring cell is out of range when
checked during operation.

Cause Abnormal measuring cell condition.

• There are air bubbles in the ProCell reservoir.
• The electrode of the measuring cell is contaminated or
deteriorated.

Curr.E
15 Data alarms

Alarm Current range check error

Description The measuring cell current check failed.

Cause ProCell liquid level check failed. The ProCell volume is

inadequate for run preparation.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of immunology tests 397

Edited
Alarm Edited test

Description An edited first result or rerun result is marked with an

Edited alarm on the Data Review submenu. This also
prints on the patient report.

Cause The result has been manually changed.

eFlow.E (e 801 module only)

Alarm Status of alarm

Description The cobas e flow test received an instrument status

information during the measurement or the result
calculation failed. This also prints on the patient report.

Cause At least one embedded test result is marked with a data

alarm or an instrument status was sent, for example,
System reagent temperature limit exceeded.

eFlow.W (e 801 module only)

Alarm Status of warning

Description The cobas e flow test result is marked with a warning.

This also prints on the patient report.

Cause At least one embedded test result includes additional

information, for example, violation of the Higher
uncertainty limit.

>I.H (e 602 module only)

15 Data alarms

Alarm Serum index interference hemolysis

Description The hemolytic value is greater than the specified

reference value.

Cause A highly hemolytic sample was measured.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
398 Data alarms of immunology tests

>I.HI (e 602 module only)

Alarm Serum index interference hemolysis/icteric

Description The hemolytic and icteric values are greater than the
specified reference values.

Cause A highly hemolytic and icteric sample was measured.

>I.I (e 602 module only)

Alarm Serum index interference icteric

Description The icteric value is greater than the specified reference

value.

Cause A highly icteric sample was measured.

>I.L (e 602 module only)

Alarm Serum index interference lipaemia

Description The lipemic value is greater than the specified reference

value.

Cause A highly lipemic sample was measured.

>I.LH (e 602 module only)

Alarm Serum index interference lipaemia/hemolysis

Description The lipemic and hemolytic values are greater than the
specified reference values.
15 Data alarms

Cause A highly lipemic and hemolytic sample was measured.

>I.LHI (e 602 module only)

Alarm Serum index interference lipaemia/hemolysis/icteric

Description The lipemic, hemolytic, and icteric values are greater than
the specified reference values.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of immunology tests 399

Cause A highly lipemic, hemolytic, and icteric sample was

measured.

>I.LI (e 602 module only)

Alarm Serum index interference lipaemia/icteric

Description The lipemic and icteric values are greater than the
specified reference values.

Cause A highly lipemic and icteric sample was measured.

Inc.T
Alarm Incubator temperature

Description Incubator temperature is out of range. The system

performs an initial check 30 minutes after start-up. The
temperature is checked continuously thereafter.

Cause • Radiation of heat does not work normally.

• The room temperature is out of range

na.LHI (e 602 module only)

Alarm Serum index measurement not performed

Description The serum index measurement could not be performed

for the test.

Cause The serum index measurement could not be performed

for the test for some reason.

Example 1: The remaining reagent volume for serum

index testing is insufficient.
15 Data alarms

Example 2: The test is a high-priority immunology test

and the system is in the auto rerun mode. In that case, the
serum index measurement cannot be performed before
the measurement of the high-priority immunology test.

OBS.RR
Alarm On-board stability limit over on the reagent cassettes and
ProCell II M bottle

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
400 Data alarms of immunology tests

Description The onboard stability of a reagent cassette (e 801 or

e 602 module) or a ProCell II M bottle used for this test
has expired.

Cause The system detected that the onboard stability of a

reagent cassette or a ProCell II M bottle expired.

Over.E
Alarm Overflow

Description Display is not possible because the result exceeds 8 digits

Cause The result contains more than 6 digits without decimal

point and minus sign.

Examples for the maximum number of digits that can be

presented: -0.00123 or 12.3456 or 999777.

ReagEx
Alarm Reagent expired date

Description The alarm indicates that an expired reagent was used; the
test result is not guaranteed. The alarm can be inactivated
under Utility > System > Alarm Settings.

Cause The system detected an expired reagent onboard the

instrument.

Reag.F
Alarm Reagent film detection

Description The reagent probe detects a film or air bubbles in the

15 Data alarms

cobas e pack.

Cause There is foam or film in the cobas e pack, the diluent

reagent pack, or the pretreatment reagent pack.

Reag.H
Alarm Reagent hovering

Description The reagent probe hovers over the reagent disk.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of immunology tests 401

Cause A premature LLD signal is detected during reagent

pipetting.

Reag.S
Alarm Reagent, diluent, or pretreatment short

Description The liquid level cannot be detected in the cobas e pack.

Cause • There is no reagent in the cobas e pack.

• The volume of diluent or pretreatment is insufficient.
• The lead wire for the liquid level sensor is
disconnected.

Reag.T
Alarm Reagent disk temperature

Description Reagent disk temperature is out of range. The system

performs an initial check 30 minutes after start-up. The
temperature is checked continuously thereafter.

Cause • Radiation of heat does not work normally.

• The room temperature is out of range.

>Rept/<Rept
Alarm Repeat limit over (upper)/(lower)

Description The result is greater than the specified upper limit value
(>Rept) or smaller than the lower limit value (<Rept)
programmed on Utility > Application > Range.

Cause • The sample concentration is higher than the set value

15 Data alarms

(>Rept).
• The sample concentration is lower than the set value
(<Rept).
• An improper repeat limit range is specified.

Samp.B
Alarm Sample air bubble

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
402 Data alarms of immunology tests

Description • Air bubble/foam is detected in the sample when the

sample is aspirated.
• Air bubble is detected in the sample pump flow path
when the sample is aspirated (e 602 module only).
• Foam is detected in the sample with the camera
(e 801 module only).

Cause • There are air bubbles/foam in the sample container.

• There are droplets on the sample container wall.
• There are air bubbles/foam in the water flow tubing.
• There are clots or other particles in the sample
container (e 801 module only).
• The sample volume is insufficient.
• The sample container type is not supported.
• The sample container is tilted or not centered.

Samp.C
Alarm Sample clot

Description A sample clot is detected during aspiration.

Cause • The sample volume is insufficient.

• There are clots in the sample.

Samp.O
Alarm Sample carry over for modules.

Description Possible sample carryover must be considered when you

check the results of the additional test(s) because no
special wash was performed in the first run.

Cause An additional test that requires a special wash was

performed and the module did not perform any special
wash for the sample in the first run.
15 Data alarms

Samp.S
Alarm Sample short

Description The liquid level cannot be detected in the sample

container.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of immunology tests 403

Cause • The sample volume in the sample container is

insufficient.
• The sample container is missing on the rack.

<SigL
Alarm Minimum signal

Description The signal level is extraordinarily low.

Cause • The volume of the reaction mixture in the AssayCup is

insufficient
• Reaction mixture contains clots
• Extremely high sample concentration for a competitive
assay
• Abnormal measuring cell condition of detection unit
(sipper/tubing/MC)
• ProCell is expired

SLLD.E
Alarm Sample LLD abnormal

Description The sample probe does not start LLD or LLD is not
completed.

Cause 1. The tip of the sample probe is dirty.

2. The tip of the sample probe is wet.

SLLD.N
Alarm Sample LLD noise

Description The sample probe detects noise or air bubbles on the

15 Data alarms

sample.

Cause 1. The sample volume is insufficient.

2. There are bubbles in the sample container.

SysR.S
Alarm System reagent short

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
404 Data alarms of immunology tests

Description The counted remaining number becomes 0, liquid short

signal is detected, or the liquid level cannot be detected
in the ProCell reservoir.

Cause The volumes in the auxiliary reagent bottles (ProCell and

CleanCell) are insufficient.

SysR.T
Alarm System reagent temperature

Description ProCell/CleanCell temperature is out of range. The system

performs an initial check 30 minutes after start-up. The
temperature is checked continuously thereafter.

Cause 1. Radiation of heat does not work normally.

2. The room temperature is out of range.

>Test/<Test
Alarm Technical limit over (upper)/(lower)

Description • Upper technical limit exceeded:

The measured value is higher than the measuring
range (>Test).
• Lower technical limit exceeded:
The measured value is lower than the measuring
range (<Test).

Cause • The sample concentration is above the upper limit of

the measuring (reportable) range (>Test).
• The sample concentration is below the lower limit of
the measuring (reportable) range (<Test).
15 Data alarms

WB.S
Alarm Washing buffer short

Description The remaining volume for PreClean is 0, or liquid short

signal is detected.

Cause There is no reagent in the reagent bottle.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarms of immunology tests 405

WBSS.T (e 801 module only)

Alarm Washing buffer SS temperature

Description The temperature of PreClean II M solution at the

separation station is out of range.The instrument
performs an initial check 30 minutes after startup. The
temperature is checked continuously thereafter.

Cause 1. Radiation of heat does not work normally.

2. The room temperature is out of range.

Remedy 1. Check that the fans at the rear of the module are
operating normally and are unobstructed.
2. Check that room temperature is 18–32 °C.
3. If the alarm recurs, contact your Roche Service
representative.

WB.T
Alarm Washing buffer temperature

Description PreClean temperature is out of range. The system

performs an initial check 30 minutes after start-up. The
temperature is checked continuously thereafter.

Cause 1. Radiation of heat does not work normally.

2. The room temperature is out of range.

15 Data alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
406 Alarms for calibrations

Alarms for calibrations

The following table displays all calibration data alarms
applicable for the modules.

q Calibration data alarms are indicated on the

Calibration Trace window and on the Calibration
Monitor report.
For the e 801/e 602 module, calibration alarms are always
indicated by an asterisk (*) on the Calibration Trace
window. This is used as a wildcard for all calibration data
alarm. Check the Calibration Monitor report to find out
which calibration data alarm occurred.

Data alarm Data alarm (long name) ISE c 701/ c 502 e 801 e 602
c 702
Cal.E CALIB error (Calib flag) l l l – –
Cond.E Conditioning (ISE) abnormal l – – – –
Diff.E Minimum acceptable difference – – – l l
Dup.E Duplicate error – l l l l
IStd.E IS concentration abnormal l – – – –
Mono.E Monotony of curve – – – – l
Prep.E Preparation abnormal l – – – –
Rsp1.E Response (ISE) abnormal 1 l – – – –
Rsp2.E Response (ISE) abnormal 2 l – – – –
S1A.E S1ABS abnormal – l l – –
SD.E SD limit error – l l – –
Sens.E Sensitivity error – l l – –
>Sig Maximum Signal – – – l l
<Sig Minimum Signal – – – l l
Sig.E Minimum/Maximum Signal – – – l l
Slop.E Slope abnormal l – – – –
Std.E Standard error l l l – –
Sys.E System errors – – – l l
y Data alarm list
15 Data alarms

Cal.E
Alarm CALIB error (Calib flag)

Displayed in Calibration > Status > Calibration Trace.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Alarms for calibrations 407

Description The current slope value differs from the previous one by
more than the specified compensated limit on Utility
> Application > Calib.. The Compensated Limit field
is a limit for the difference
| previous value – current value | expressed as
percentage of the average (previous value + current
value)/2.

For ISE calibrations, the S3 concentration is checked

additionally by applying a limit to the Compensated
Limit field multiplied by a fixed factor of 0.25. If this check
fails, the Cal.E alarm is also issued.

q The Cal.E alarm is a warning only, and does not

necessarily indicate a calibration problem. Check the
test’s control recovery before accepting the new
calibration result.

Cause • The standard solution or reagent is not placed in

proper position.
• The reagent has deteriorated or the standard solution
has become concentrated due to evaporation.

Cond.E
Alarm Conditioning (ISE) abnormal

Description The slope value is 68.1 mV or greater for Na+ or K+

electrodes, or it is -68.1 mV or less for the Cl- electrode.
The conditioning is inadequate.

Slope value Alarm message

Cl- K+ Na+
-68.1 mV or less 68.1 mV or more 68.1 mV or more Conditioning inadequate Cond.E
-68.0 mV to -40.0 mV 68.0 mV to 50.0 mV 68.0 mV to 50.0 mV (Normal range)
-39.9 mV to -35.0 mV 49.9 mV to 45.0 mV 49.9 mV to 45.0 mV ISE prepare error Prep.E
-34.9 mV or more 44.9 mV or less 44.9 mV or less ISE slope error Slop.E
15 Data alarms

y Slope values for ISE electrodes

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
408 Alarms for calibrations

1D.

6ORSH( 3UHS( 1RUPDOUDQJH  &RQG(

       P9

&O

&RQG( 1RUPDOUDQJH 3UHS( 6ORSH(

       P9

w ISE data alarms and corresponding slope values (electrode voltage)

q Judgement on ISE electrode replacement

o If one of the alarms Preparation abnormal (Prep.E) or
ISE slope error (Slop.E) appear during calibration,
replace the electrodes at once.
o Normally, the slope values slightly decrease with time
and use. If there is a large change compared to the
value of the previous day, the cause may be other than
deteriorated electrodes. Check for air bubbles in or
leakage from the flow path, an error in substitution of
standard solution, contamination of the flow path, etc.

Cause • Conditioning of a new electrode is unsatisfactory.

• The concentration of standard solution LOW/HIGH is
improper.

Diff.E
Alarm Minimum acceptable difference

Description If the difference between the mean of level 1 and level 2

calibrator is below the permissible value, the calibration is
failed.

Cause • The ProCell is expired.

• The calibrator does not reach room temperature.
15 Data alarms

Duplicate error
This section describes the duplicate error for
cobas c modules and for cobas e modules.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Alarms for calibrations 409

Dup.E (cobas c modules)

Alarm Duplicate error

Displayed on Calibration > Status > Calibration

Trace.

Description The difference between the first and second

measurement (absorbance) of a calibrator is outside the
specified range.

The following steps describe how a decision is made to

flag a calibration for violating the duplication limit.
1. The absorbance for a calibrator (N) is measured twice.
2. The % of error and absorbance error are computed.
3. Is the absorbance error smaller than the set
Duplicate Limit Abs. field on Utility > Application
> Calib.?
If no, go to step 5.
If yes, go to step 4.
4. Continue with result calculations. No Dup.E alarm is
issued.
5. Is the % error < the % Duplicate Limit?
If no, go to step 6.
If yes, go to step 4.
6. Dup.E alarm is issued for this result.

Cause The difference between the first and second

measurement (absorbance) of a calibrator is greater than
Duplicate Limit Abs and greater than the % Duplicate
Limit.

Dup.E (cobas e modules)

Alarm Duplicate error (e 801/e 602)

Displayed on Calibration > Status > Calibration

15 Data alarms

Result.

Description The difference between the first and second measured

signal of the calibrator is out of the specified range.
For e 801 modules: The duplicate limit is defined lot-
specific in the container parameter file.
For e 602 modules: The duplicate limit is defined on
Utility > Application > Calib..

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
410 Alarms for calibrations

Cause • Air was aspirated during the first determination due to

air bubbles on the corresponding calibrator. During
the second determination no air was aspirated.
• Consequence: The signal values of the first and
second determination differ more than the specified
percentage.

IStd.E
Alarm IS concentration abnormal

Displayed on Calibration > Status > Calibration

Trace.

Description The concentration of the Internal Standard solution

(ISE IS) was not within the following ranges:

Na+ 120.0–160.0 mmol/L

K+ 3.0–7.0 mmol/L

Cl- 80.0–120.0 mmol/L

Cause • The flow path is contaminated.

• The reagent has deteriorated.

Mono.E (e 602 module only)

Alarm Monotony of curve

Description The working curve is not monotonically increasing or

monotonically decreasing.

This is a calibration quality criteria only for quantitative

immunology tests.

Cause • The ProCell is expired.

15 Data alarms

• The calibrator did not reach room temperature.

Prep.E
Alarm Preparation abnormal

Displayed on Calibration > Status > Calibration

Trace.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Alarms for calibrations 411

Description The slope value is within the following range: 45.0 to 49.9
mV for Na+ or K+ electrodes, -39.9 to -35.0 mV for the Cl-
electrode. This alarm causes a failed calibration.

1D.

6ORSH( 3UHS( 1RUPDOUDQJH  &RQG(

       P9

&O

&RQG( 1RUPDOUDQJH 3UHS( 6ORSH(

       P9

w ISE data alarms and corresponding slope values (electrode voltage)

Cause • The electrode is deteriorated.

• The flow path is contaminated.

Rsp1.E
Alarm Response (ISE) abnormal 1

Description The compensation factor is over the limits (narrower

range).

Cause • The flow path is contaminated.

• The electrode is contaminated or deteriorated.

Rsp2.E
Alarm Response (ISE) abnormal 2

Description The compensation factor is over the limits (wider range).

Cause • The flow path is contaminated.

15 Data alarms

• The electrode is contaminated or deteriorated.

S1A.E
Alarm S1ABS abnormal

Displayed on Calibration > Status > Calibration

Trace.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
412 Alarms for calibrations

Description During calibration, expected absorbance is outside the S1

Abs Limit. S1 is read bichromatically for endpoint assays,
monochromatically for rate assays.

Cause • The reagent has been stored or handled improperly or

has deteriorated.
• An improper absorbance range is specified for
calibrator 1.

SD.E
Alarm SD limit error

Description During nonlinear or multipoint linear calibration, the SD

value was greater than the SD limit programmed on
Utility > Application > Calib.

Cause • The calibrator is not placed in a correct position.

• An improper SD limit value is specified.

Sens.E
Alarm Sensitivity error

Description Sensitivity is checked for linear (2 to 6 points), nonlinear,

or isozyme-P calibration. This alarm is indicated if the
sensitivity value obtained in a calibration falls out of the
Sensitivity Limit fields specified on Utility
> Application > Calib.

q For span calibration, the previous S1 Abs (linear) or

previous mean absorbance (nonlinear) of calibrator (1) is
used for the sensitivity check.

Cause • The calibrator is not placed in a proper position.

15 Data alarms

• The reagent has been prepared improperly or has

deteriorated.
An improper sensitivity limit is specified.

>Sig
Alarm Maximum Signal

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Alarms for calibrations 413

Description The calibrator signal is greater than the specified upper

limit.

For e 801 modules: For qualitative and quantitative

immunology tests.
For e 602 modules: Only for qualitative immunology tests.

Cause • ProCell is expired.

• The calibrator does not reach room temperature.
• The calibrator was mixed up.

<Sig
Alarm Minimum Signal

Description The calibrator signal is lower than the specified lower

limit value. For qualitative and quantitative assays.

Cause • The ProCell is expired.

• The calibrator was mixed up.
• Failure during reconstitution of the calibrator.

Sig.E
Alarm Minimum/Maximum Signal

Description The measured signal of a calibrator for a qualitative test

should fall between the designated minimum and
maximum signal. If one or more values fall out of the
allowable minimum/maximum signal range, the
calibration fails.

Cause The measured signal of a calibrator for a qualitative test

lies outside the designated minimum/maximum signal
range.
15 Data alarms

Slop.E
Alarm Slope abnormal (ISE only)

Displayed on Calibration > Status > Calibration

Trace.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
414 Alarms for calibrations

Description The slope value is less than 45.0 mV for Na+ or K+

electrodes, or greater than -35 mV for the Cl- electrode.
This alarm causes a failed calibration.

1D.

6ORSH( 3UHS( 1RUPDOUDQJH  &RQG(

       P9

&O

&RQG( 1RUPDOUDQJH 3UHS( 6ORSH(

       P9

w ISE data alarms and corresponding slope values (electrode voltage)

Cause • The electrode is deteriorated.

• Standard solutions Low and High are not placed in the
proper positions.
• The sample probe is clogged.

Std.E
This section describes the Std.E flag for the ISE module
and for cobas c modules.

Std.E (ISE module)

Alarm Standard error

Description 2 cases must be distinguished:

• Case 1: During ISE calibration, one of the alarms listed
in table occurred.
• Case 2: During calibration, calculation was disabled.

Table for case 1:

15 Data alarms

Data alarm Data flag

ADC abnormal ADC.E
Calculation not possible Calc.?
ISE voltage level error ISE.E
ISE noise error ISE.N
Mixing current low MIXLOW
Sample short Samp.S
y Data alarms causing a Std.E alarm when occurring in
calibration

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Alarms for calibrations 415

q The calibration is not updated if this alarm is issued;

i.e., the prior calibration remains in effect.

Cause • The reagent is empty and has to be replaced.

• The concentration of calibrator is incorrect or the
calibrator is not placed in the proper position.
• An improper check value is specified.

Std.E (cobas c modules)

Alarm Standard error

Description 3 cases must be distinguished:

• Case 1: During photometric calibration, one of the
alarms listed in the table occurred.
• Case 2: During calibration, calculation was disabled.
• Case 3: During nonlinear calibration, an extreme value
appeared.

Table for case 1:

Data alarm Data flag
ABS over >Abs
ADC abnormal ADC.E
Calculation not possible Calc.?
ABS Cell blank abnormal >Cuvet
Duplicate error Dup.E
Linearity abnormal >Lin
Mixing current low MIXLOW
Stop mixing MIXSTP
Prozone error, Kinetic unstable >Proz, >Kin(1)
(Prozone error 2)
Reaction limit over >React
Reagent short Reag.S
S1ABS abnormal S1A.E
Sample short Samp.S
15 Data alarms

y Data alarms causing a Std.E alarm when occurring in

calibration
(1) Not for Std.1

q The calibration is not updated if this alarm is issued;

i.e., the prior calibration remains in effect.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
416 Alarms for calibrations

Cause • The reagent has not been stored or handled properly

or is empty and has to be replaced.
• The concentration of calibrator is incorrect or the
calibrator is not placed in the proper position.
• An improper check value is specified.

Sys.E
Alarm System errors

Description An error occurred on the system during measurement.

Cause Check the Alarm window.

15 Data alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Data alarm for QC materials 417

Data alarm for QC materials

QC results are validated on the data manager regarding
the set rules. After validation is performed, the QC results
are transferred back to the instrument.

q On the instrument, invalid QC results are always

indicated by the QCErr flag.

Data Alarm ISE c 701/ c 502 e 801/

alarm c 702 e 602
QCErr QC error l l l l
y Data alarm list

QCErr
Alarm QC error

Description • The QC result is not within the defined range.

• No QC rule is assigned to the test.
• There are not enough QC values available for applying
the assigned QC rule.

Cause • Reagent is deteriorated.

• Poor precision due to leakage of the pipetter joint.
• Proper control values (mean value, standard
deviation) are not specified.
• Improper preparation or storage of controls.
• Missing QC rule assignment.
• Missing QC values.

List of data alarms for QC measurements

The following table displays the data alarms that can be
15 Data alarms

attached to QC results in addition to the QCErr alarm.

Data alarm Data alarm (long name) ISE c 701 c 702 c 502 e 801 e 602
>Abs ABS over – l l l – –
ADC.E ADC abnormal l l l l l –
Calc.? Calculation not possible l l l l – l
Cal.E (sample flag) Calibration result abnormal (sample flag) l l l l l l
Cal.I Calibration result invalid l l l l l l
CarOvr Potential carry over – – – – l l
y List of data alarms for tests

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
418 Data alarm for QC materials

Data alarm Data alarm (long name) ISE c 701 c 702 c 502 e 801 e 602
Cell.T Cell temperature – – – – l l
Clot.E Clot pressure abnormal – – – – l l
CmpT.? Unable to calculate comp. test (compensation test) l l l l – –
CmpT.E Data error in comp. test (compensation test) l l l l – –
>Curr Current range over – – – – l l
>Cuvet ABS Cell blank abnormal – l l l – –
Det.S Carry over detergent short – l l l – –
Inc.T Incubator temperature – – – – l l
ISE.E ISE voltage level error l – – – – –
ISE.N ISE noise error l – – – – –
>Lin Linearity abnormal – l l l – –
MIXLOW Mixing current low l l l l – –
MIXSTP Stop mixing l l l l – –
OBS.RM On-board stability limit over on reagent manager – – l – – –
OBS.RR On-board stability limit over on reagent rotor – l l l l l
Over.E Overflow l l l l l l
>React Reaction limit over – l l l – –
ReagEx Reagent expired date – l l l l l
Reag.F Reagent film detection – – – – l l
Reag.H Reagent hovering – – – – l l
Reag.S Reagent short l l l – l l
Reag.T Reagent disk temperature – – – – l l
Samp.? ABS maximum over (non-lin curve) – l l l – –
Samp.B Sample air bubble – – – – l l
Samp.C Sample clot l l l l l l
Samp.O Sample carry over for modules l l l l l l
Samp.S Sample short l l l l l l
<SigL Minimum signal – – – – l l
SLLD.E Sample LLD abnormal – – – – l l
SLLD.N Sample LLD noise – – – – l l
SysR.S System reagent short – – – – l l
SysR.T System reagent temperature – – – – l l
< >Test ISE sample range over l – – – – –
>Test/<Test Technical limit over (upper)/(lower) – – – – l l
WB.S Washing buffer short – – – – l l
15 Data alarms

WBSS.T Washing buffer SS temperature – – – – l –

WB.T Washing buffer temperature – – – – l l
y List of data alarms for tests

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Rerun test list 419

Rerun test list

The following table indicates whether a rerun test is
automatically requested by the system when a data alarm
is attached to a test result. The rerun test conditions are
displayed for each module. The automatic rerun column
indicates whether a rerun test is automatically performed
by the system.

I Sample is rerun with an increased pipetting

volume.

N Sample is rerun with the same (normal) pipetting

volume (repeat test).

D Sample is rerun with a decreased pipetting volume.

NR No test rerun is performed on this module.

- Not applicable

Data alarm Data alarm (long name) ISE c 701 c 702 c 502 e 801 e 602 Automatic rerun
>Abs ABS over - D D D - - Yes
ADC.E ADC abnormal N N N N - - Yes
Calc.? Calculation not possible N N N N - N Yes
Cal.E (sample Calibration result abnormal (sample flag) N N N N N N No
flag)
Cal.I Calibration result invalid N N N N N N No
CarOvr Potential carry over - - - - N N Yes
Cell.T Cell temperature - - - - N N Yes
ClcT.E Calculation test error N N N N - - Yes
Clot.E Clot pressure abnormal - - - - N N Yes
CmpT.? Unable to calculate comp. test (compensation N N N N - - Yes
test)
CmpT.E Data error in comp. test (compensation test) N N N N - - Yes
>Curr Current range over - - - - N N Yes
>Cuvet ABS Cell blank abnormal - N N N - - Yes
Det.S Carry over detergent short - N N N - - No
Edited Edited test NR NR NR NR NR NR No
15 Data alarms

< >ISE ISE range over I(1) - - - - - Yes

>I.H Serum index interference hemolysis NR NR NR NR - NR No
>I.HI Serum index interference hemolysis/icteric NR NR NR NR - NR No
>I.I Serum index interference icteric NR NR NR NR - NR No
>I.L Serum index interference lipaemia NR NR NR NR - NR No
>I.LH Serum index interference lipaemia/hemolysis NR NR NR NR - NR No
>I.LHI Serum index interference NR NR NR NR - NR No
lipaemia/hemolysis/icteric
>I.LI Serum index interference lipaemia/icteric NR NR NR NR - NR No
Inc.T Incubator temperature - - - - N N Yes
y Rerun test list

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
420 Rerun test list

Data alarm Data alarm (long name) ISE c 701 c 702 c 502 e 801 e 602 Automatic rerun
ISE.E ISE voltage level error N - - - - - Yes
ISE.N ISE noise error N - - - - - Yes
>Kin Kinetic unstable (Prozone error 2) - D D D - - Yes
>Lin Linearity abnormal - N N N - - Yes
MIXLOW Mixing current low N N N N - - Yes
MIXSTP Stop mixing N N N N - - Yes
na.LHI Serum index measurement not performed NR NR NR NR - NR No
OBS.RM On-board stability limit over on reagent - - NR - - - No
manager
OBS.RR On-board stability limit over on reagent rotor - NR NR NR NR NR No
Over.E Overflow - NR NR NR NR NR No
>Proz Prozone error - D D D - - Yes
>React Reaction limit over - D D D - - Yes
ReagEx Reagent expired date - NR NR NR NR NR No
Reag.F Reagent film detection - - - - N N Yes
Reag.H Reagent hovering - - - - N N Yes
Reag.S Reagent short N N N N N N No
Reag.T Reagent disk temperature - - - - N N Yes
>Rept/<Rept Repeat limit over (upper)/(lower) N N N N N N Due to setting
Samp.? ABS maximum over (non-lin curve) - D D D - - Yes
Samp.B Sample air bubble - - - - N N Yes
Samp.C Sample clot N N N N N N No
Samp.O Sample carry over for modules NR NR NR NR NR NR No
Samp.S Sample short N N N N N N No
<SigL Minimum signal - - - - N N Yes
SLLD.E Sample LLD abnormal - - - - N N Yes
SLLD.N Sample LLD noise - - - - N N Yes
SysR.S System reagent short - - - - N N Yes
SysR.T System reagent temperature - - - - N N Yes
< >Test ISE sample range over N - - - - - No
>Test Technical limit over (upper) N(2) D D D D D Yes
<Test Technical limit over (lower) N(2) I I I NR NR ISE: Yes
c 701/c 702/
c 502: Yes
e 801/e 602: No
WB.S Washing buffer short - - - - N N Yes
15 Data alarms

WBSS.T Washing buffer SS temperature - - - - N - Yes

WB.T Washing buffer temperature - - - - N N Yes
y Rerun test list
(1) Increased pipetting volume for Na+ and Cl- tests. This alarm is effective for urine samples only and is not applicable to K+ tests.
(2) Normal pipetting volume for serum/pl samples. For urine samples, it depends on the technical limit setting whether a rerun test is requested
with normal pipetting volume or whether this alarm is issued at all.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Alarm priorities 421

Alarm priorities
If more than one alarm exists for a result, the analyzer
displays the alarm with the highest priority, and sends it
to the data manager. The data manager forwards this
alarm to the host.

w Priority of alarms on routine or STAT samples

Each module has certain specific alarms.

15 Data alarms

w Priority of alarms from an ISE module

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
422 Alarm priorities

w Priority of alarms from a c-module

w Priority of alarms from an e602 module

Priority of alarms from an e 801 module Alarms from an e 801 module have the following priority,
from highest to lowest.
• eFlow.E
• eFlow.W
15 Data alarms

• All other numerical code alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 423
Table of contents

Instrument alarms 16

This chapter describes the alarms generated on the

cobas® 8000 modular analyzer series instrument by
errors in communication with the data manager or the
host.

In this chapter 16
Instrument alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

16 Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 424
Table of contents
16 Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Instrument alarms 425

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 on the
other. Instrument alarms are not uploaded to the host.

If an instrument alarm occurs that is not in this list,

consult your authorized 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
invalid. 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.
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 1. Restart the system.
from Data Manager the 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 16 Instrument alarms
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 1. Perform Delete All on Workplace > Data Review.
from Data Manager sample management 2. Perform Sample Data Clear on System Overview.
database is full.
111 56 Abnormal Test Selection Result data file on the 1. Perform Delete All on Workplace > Data Review.
from Data Manager sample management 2. Perform Sample Data Clear on System Overview.
database is full.
111 57 Abnormal Test Selection The Stat rack ID is out of the Check the orders on System > Rack Assignment.
from Data Manager range.
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 426 Instrument alarms

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 2. Check the HL7 text. (Test Selection Download Text)
position 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
line was turned to offline status, 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 1. Check the connection status of Data Manager on
Communication Error measures for connection System Overview > Data Manager. If it is wait
between the Data Manager status, connect it from Data Manager.
and the system were 2. Check if the connector was not plugged in during
performed 15 times in a row. the data communication.
By this alarm, the 3. Restart the system.
communication will be 4. Contact service representative, if alarm recurs.
disconnected.
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
(Control socket status, 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
abnormality was detected. status, connect it from Data Manager.
(Control socket 2. Check if the connector was not plugged in during
communication line) the data communication.
3. Restart the system.
4. Contact service representative, if alarm recurs.
126 204 Data Manager Internal process error 1. Restart the system.
16 Instrument alarms

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
abnormality was detected. status, connect it from Data Manager.
(Control socket 2. Check if the connector was not plugged in during
communication line) the 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
following causes: status, connect it from Data Manager.
o Wire break. 2. Check if the connector was not plugged in during
o Momentary power the data communication.
failure. 3. Restart the system.
4. Contact service representative, if alarm recurs.
126 207 Data Manager Internal process error 1. Restart the system.
Communication Error occurred. 2. Contact service representative, if alarm recurs.
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Instrument alarms 427

Code Sub- Alarm Message Content Troubleshooting

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
(Control socket status, 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
socket communication line) 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 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. 16 Instrument alarms
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.
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.
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 428 Instrument alarms

Code Sub- Alarm Message Content Troubleshooting

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.
16 Instrument alarms

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.
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Instrument alarms 429

Code Sub- Alarm Message Content Troubleshooting

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.
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.
16 Instrument alarms
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.
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 430 Instrument alarms

Code Sub- Alarm Message Content Troubleshooting

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 1. Perform Delete All on Workplace > Data Review.
Database Error sample management 2. Perform Sample Data Clear on System Overview.
database is full.
300 2 Sample Management Result data file on the 1. Perform Delete All on Workplace > Data Review.
Database Error sample management 2. Perform Sample Data Clear on System Overview.
database is full.
300 3 Sample Management Link data file on the sample Check the test selection on Workplace > Test
Database Error management database is Selection.
full.
300 4 Sample Management The sample data file on the 1. Perform Delete All on Workplace > Data Review.
Database Error sample management 2. Perform Sample Data Clear on System Overview.
database is full.
300 5 Warning of Database The sample data file on the 1. Perform Delete All on Workplace > Data Review.
Registration sample management 2. Perform Sample Data Clear on System Overview.
database becomes full.
301 -3 TS Register Error The test selections are not Check the test selections on Workplace > Test
registered because the Selection or QC > Status.
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
302 -3 Rerun TS Register Error The rerun test selections are Check the test selections on Workplace > Test
not registered because the Selection.
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 The system cannot analyze a 1. When the system completes the analysis of loaded
Error sample, because duplicated samples, retry the sample.
16 Instrument alarms

data is included in the 2. Check the following. * Sample Type * Sample ID *

barcode label on the sample. Sequence No. * Rack ID * Rack Position No.
The duplicated data is the
following:
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
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Instrument alarms 431

Code Sub- Alarm Message Content Troubleshooting

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 2. Contact service representative, if alarm recurs.
control 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
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
(HL7 communication line) status, connect it from Data Manager.
The subcategory code 2. Check if the connector was not plugged in during
indicates communication the data communication.
line number. 3. Restart the system.
4. Contact service representative, if alarm recurs. 16 Instrument alarms
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
Detected disconnection. The status, connect it from Data Manager.
subcategory code indicates 2. Check if the connector was not plugged in during
communication line number. the 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
abnormality was detected. status, connect it from Data Manager.
(HL7 communication line) 2. Check if the connector was not plugged in during
The subcategory code the data communication.
indicates communication 3. Restart the system.
line number. 4. Contact service representative, if alarm recurs.
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 432 Instrument alarms

Code Sub- Alarm Message Content Troubleshooting

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
abnormality was detected. status, connect it from Data Manager.
(HL7 communication line) 2. Check if the connector was not plugged in during
The subcategory code the data communication.
indicates communication 3. Restart the system.
line 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 3. Refer to the specifications of system interface
line number. communication.
4. Contact service representative, if alarm recurs.
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
code indicates at 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
subcategory code indicates INV 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.
16 Instrument alarms

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
subcategory code indicates NDS 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.
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Instrument alarms 433

Code Sub- Alarm Message Content Troubleshooting

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
subcategory code indicates PID 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
subcategory code indicates QID segment.
communication line number. 3. Contact service representative, if alarm recurs.
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
subcategory code indicates RCP 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
subcategory code indicates SAC 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 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates SID 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
subcategory code indicates SPM 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
subcategory code indicates TQ1 segment.
communication line number. 3. Contact service representative, if alarm recurs. 16 Instrument alarms
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.
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 434 Instrument alarms

Code Sub- Alarm Message Content Troubleshooting

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.
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.
16 Instrument alarms

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.
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Instrument alarms 435

Code Sub- Alarm Message Content Troubleshooting

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.
936 -2 Abnormal Text from An error was detected in the 1. Perform System Communication Trace on Print.
Data Manager SID segment. The 2. Check the SID 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.
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 3. Refer to the specifications of system interface
line 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 3. Refer to the specifications of system interface
line number. communication.
4. Contact service representative, if alarm recurs. 16 Instrument alarms
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 3. Refer to the specifications of system interface
line 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 3. Refer to the specifications of system interface
line 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 3. Refer to the specifications of system interface
line number. communication.
4. Contact service representative, if alarm recurs.
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 436 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 3. Refer to the specifications of system interface
line number. communication.
4. Contact service representative, if alarm recurs.
947 -2 Abnormal Text from There is no PID segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code Confirm that the PID segment exists.
indicates communication 2. Refer to the specifications of system interface
line number. 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 3. Refer to the specifications of system interface
line number. communication.
4. Contact service representative, if alarm recurs.
949 -2 Abnormal Text from There is no QID segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the QID segment exists.
indicates communication 3. Refer to the specifications of system interface
line number. 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 3. Refer to the specifications of system interface
line number. communication.
4. Contact service representative, if alarm recurs.
951 -2 Abnormal Text from There is no RCP segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the RCP segment exists.
indicates communication 3. Refer to the specifications of system interface
line number. 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 3. Refer to the specifications of system interface
line number. communication.
4. Contact service representative, if alarm recurs.
953 -2 Abnormal Text from There is no TQ1 segment. 1. Perform System Communication Trace on Print.
Data Manager The subcategory code 2. Confirm that the TQ1 segment exists.
indicates communication 3. Refer to the specifications of system interface
line number. communication.
4. Contact service representative, if alarm recurs.
16 Instrument alarms

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)
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Instrument alarms 437

Code Sub- Alarm Message Content Troubleshooting

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
Manager is not the Response 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. 3. Contact service representative, if alarm recurs.
(Reaction Monitor Result
Response Text)
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. 3. Contact service representative, if alarm recurs.
(Reaction 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. 16 Instrument alarms
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.
y Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 438 Instrument alarms

Code Sub- Alarm Message Content Troubleshooting

994 13 Data Manager The orders of the serum 1. Perform System Communication Trace on Print.
Communication Error index 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.
y Instrument alarms
16 Instrument alarms

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 439
Table of contents

Result message codes for

cobas e flow tests 17
Codes for qualitative cobas e flow test results

This chapter describes the result codes sent with

qualitative results sent by cobas e flow tests from an

17 Result message codes for cobas e flow tests

e 801 module.

In this chapter 17
Result message codes . . . . . . . . . . . . . . . . . . . . . . . . . . 441

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 440
Table of contents
17 Result message codes for cobas e flow tests

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Result message codes 441

Result message codes

A cobas e flow test can send a code number as the
result of a test, in the field OBX-5 (HL7) or R-4.1 (ASTM).
This table shows the supported codes and their
meanings.

Code Result Message Suggested assay type

-1 NonReac Qualitative
0 Border Qualitative
1 Reac. Qualitative
2 <empty> n.a.
3 <empty> n.a.
4 Gray zone Qualitative
5 Indeterminate Qualitative
6 Above measuring range Quantitative
7 Below measuring range Quantitative
8 Result between LoB and LoD Quantitative

17 Result message codes for cobas e flow tests

9 Result between LoD and LoQ Quantitative
10 Result between LoB and LoQ Quantitative
11 Close to medical decision point Quantitative
12 Close to medical decision point 1 Quantitative
13 Close to medical decision point 2 Quantitative
14 Close to medical decision point 3 Quantitative
15 Avidity high Avi cobas e flow tests
16 Avidity low Avi cobas e flow tests
17 Confirmatory test possible Subsequent action recommended
18 Confirmatory test recommended Subsequent action recommended
19 Confirmation recommended Subsequent action recommended
20 NAT recommended Subsequent action recommended
21 PCR recommended Subsequent action recommended
22 Duplicate repeat test recommended Subsequent action recommended
23 Retesting recommended Subsequent action recommended
24 Limited precision Quantitative
25 Automated dilution recommended Quantitative
26 Dilution recommended Quantitative
27 Manual dilution recommended Quantitative
28 Testing with an additional method recommended Any
29 Follow-up sample recommended Any
30 Confirmed non-reactive cobas e flow w repeat(s)
31 Confirmed positive cobas e flow w repeat(s)
32 Confirmation not valid cobas e flow w repeat(s)
33 Intermediate Qualitative
34 Repeatedly reactive cobas e flow w repeat(s)
35 Repeatedly reactive, investigated using an cobas e flow w repeat(s), neutralization
independent neutralization test cobas e flow tests
y cobas e flow test result codes (OBX-5)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 442 Result message codes

Code Result Message Suggested assay type

36 Acute phase Serology cobas e flow tests
37 Early phase of recovery Serology cobas e flow tests
38 Chronic infection Serology cobas e flow tests
39 Recovered infection Serology cobas e flow tests
40 Avidity medium Avi cobas e flow tests
41 Presumed acute phase Serology cobas e flow tests
42 Late acute phase Serology cobas e flow tests
43 Remote infection Serology cobas e flow tests
44 Persisting IgM Serology cobas e flow tests
45 Antibody titer protective Vaccination cobas e flow tests
46 Immunocomplex detected Confirmatory
47 Neutralization successful Confirmatory
48 Equivocal Qualitative
49 Immunity likely Vaccination cobas e flow tests
50 Immunity unlikely Vaccination cobas e flow tests
51 Immunity unlikely - consider vaccination Vaccination cobas e flow tests
52 Immunity unlikely - immunoblot recommended Vaccination cobas e flow tests
17 Result message codes for cobas e flow tests

53 Risk score high Oncology cobas e flow tests

54 Risk score low Oncology cobas e flow tests
55 Risk score borderline Oncology cobas e flow tests
56 No risk calculation possible Oncology cobas e flow tests
57 No avidity calculation possible Avi cobas e flow tests
58 Invalid Any cobas e flow w range switch
59 Below dilution range Dilution
60 No reliable avidity score Avi cobas e flow tests
61 Avidity gray zone Avi cobas e flow tests
62 Avidity borderline Avi cobas e flow tests
63 Avidity determination failed Avi cobas e flow tests
64 No avidity determination possible - IgG titer too low Avi cobas e flow tests
65 Confirmed reactive Confirmatory
66 Confirmed negative Confirmatory
67 cobas e flow aborted Any cobas e flow test
68 Inconsistent result in cobas e flow Any cobas e flow test
69 Implausible Any cobas e flow test
70 Risk high Preeclampsia
71 Risk low Preeclampsia
72 Risk borderline Preeclampsia
73 No avidity determination possible - IgG titer too high Avi cobas e flow tests
74 Analyte concentration too low Quantitative
75 Analyte concentration too high Quantitative
76 Logical cobas e flow error - invalid result calculation Any cobas e flow test
77 Error after avidity triggered dilution Avi cobas e flow tests
78 Error after analyte triggered dilution Avi cobas e flow tests
79 Below measuring range - retesting without dilution Dilution, subseq action
recommended
y cobas e flow test result codes (OBX-5)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Result message codes 443

Code Result Message Suggested assay type

80 Retesting without dilution recommended Dilution, subseq action
81 No confirmation testing possible - insufficient analyte Confirmatory
82 Antigen test positive, antibody test negative Duo cobas e flow tests
83 Antigen test positive, antibody test positive Duo cobas e flow tests
84 Antigen test negative, antibody test positive Duo cobas e flow tests
85 Antigen test negative, antibody test negative Duo cobas e flow tests
86 No calculation possible Any cobas e flow test
87 No score calculation possible Any cobas e flow test
88 Seronegative Serology cobas e flow tests
89 Early phase of infection Serology cobas e flow tests
90 Acute phase of infection Serology cobas e flow tests
91 Transient phase of infection Serology cobas e flow tests
92 Late phase of infection Serology cobas e flow tests
93 Past infection Serology cobas e flow tests
94 Isolated IgG reactivity observed Serology cobas e flow tests
95 Isolated IgM reactivity observed Serology cobas e flow tests
96 Uncertain serologic status Serology cobas e flow tests

17 Result message codes for cobas e flow tests

97 Reactivated infection Serology cobas e flow tests
98 Non-primary infection Serology cobas e flow tests
99 Reactivated or non-primary infection Serology cobas e flow tests
100 Reactivated or persisting IgM titer Serology cobas e flow tests
101 Presumed seronegative Serology cobas e flow tests
102 Presumed early phase of infection Serology cobas e flow tests
103 Presumed acute phase of infection Serology cobas e flow tests
104 Presumed transient phase of infection Serology cobas e flow tests
105 Presumed late phase of infection Serology cobas e flow tests
106 Presumed past infection Serology cobas e flow tests
107 Presumed reactivated infection Serology cobas e flow tests
108 Presumed non-primary infection Serology cobas e flow tests
109 Presumed reactivated or non-primary infection Serology cobas e flow tests
110 Reactivated or persisting IgM titer likely Serology cobas e flow tests
111 May indicate a seronegative status Serology cobas e flow tests
112 May indicate an early phase of infection Serology cobas e flow tests
113 May indicate an acute phase of infection Serology cobas e flow tests
114 May indicate a transient phase of infection Serology cobas e flow tests
115 May indicate a late phase of infection Serology cobas e flow tests
116 May indicate a past infection Serology cobas e flow tests
117 May indicate a reactivated infection Serology cobas e flow tests
118 May indicate a non-primary infection Serology cobas e flow tests
119 May indicate a reactivated or non-primary infection Serology cobas e flow tests
120 May indicate a reactivated or persisting IgM titer Serology cobas e flow tests
y cobas e flow test result codes (OBX-5)

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 444
17 Result message codes for cobas e flow tests Result message codes

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 445
Table of contents

Using MODULAR PRE-ANALYTICS 18

How to use a MODULAR PRE-ANALYTICS and
aliquoted samples without barcodes with data
manager

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.

18 Using MODULAR PRE-ANALYTICS

In this chapter 18
Sample IDs and barcodes . . . . . . . . . . . . . . . . . . . . . . . 447
Handling query messages without barcodes . . . . . . . 448
Configuring the control unit . . . . . . . . . . . . . . . . . . 448
Rerun without barcodes . . . . . . . . . . . . . . . . . . . . . 448
Order of messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Handling batch test selections with strict rack and
position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Configuring data manager . . . . . . . . . . . . . . . . . . . 451
Identifying the sample . . . . . . . . . . . . . . . . . . . . . . . 452
Clearing the sample list . . . . . . . . . . . . . . . . . . . . . . 453

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 446
Table of contents
18 Using MODULAR PRE-ANALYTICS

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Sample IDs and barcodes 447

Sample IDs and barcodes

For maximum throughput on the cobas® 8000 modular
analyzer series 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
modular analyzer series instrument.

However, if a MODULAR PRE-ANALYTICS is used in

conjunction with the cobas® 8000 modular analyzer
series 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 modular
analyzer series 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.

18 Using MODULAR PRE-ANALYTICS

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 448 Handling query messages without barcodes

Handling query messages without

barcodes
In normal operation, by default, a sample without a
barcode generates an error on cobas® 8000 modular
analyzer series instrument, and is handled by the
instrument operator.

NOTICE
The host should be able to handle a missing sample
ID
r Because a user with configuration privileges can
(intentionally or otherwise) configure the
cobas® 8000 modular analyzer series 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

18 Using MODULAR PRE-ANALYTICS

To configure the cobas® 8000 modular analyzer series

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.
u For details of the GUI settings, see Test Selection Ask
in Barcode Read Error (137).

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
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Order of messages 449

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 modular analyzer series instrument
recognizes that a sample exists without a barcode. It
sends data manager a query for test selections,
identifying the sample by:
- the rack ID
- the sample’s position on the rack (1 to 5)
- 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:
- 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 ASTM Query Record
(Q) field 3, component 3, or HL7 Query Parameter
Definition Segment QPD-3.
- the rack ID, passed in ASTM Query Record (Q)
field 3, component 5, or HL7 Query Parameter
Definition Segment QPD-5.

18 Using MODULAR PRE-ANALYTICS

- the sample’s position on the rack (1 to 5). This is
passed in ASTM Query Record (Q) field 3,
component 6, or HL7 Query Parameter Definition
Segment QPD-6.
- the sample type (or rack type), in ASTM in the
Query Record (Q) field 3, component 8, or 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:
- the sample ID is passed in ASTM Order Record (O)
field 3, or HL7 Specimen Segment (SPM) field
SPM-2.
- the rack number, passed in ASTM Order Record
(O) field 4, component 2, or HL7 Container
Information Segment (SAC) fields SAC-10.
- the sample’s position on the rack (1 to 5). This is
passed in ASTM Order Record (O) field 4,
component 3, or HL7 Container Information
Segment (SAC) field SAC-11
- the sample type (or rack type): ASTM the Order
Record (O) field 4, component 4, or HL7 Specimen
Segment (SPM) field SPM-4.
4. The data manager passes this information on to the

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 450 Order of messages

control unit.
5. The control unit, data manager and the host then use
the sample identifier to identify the sample in
subsequent messages.
u For full information on the content of the supported
ASTM and HL7 fields, see the definitions in ASTM text
content (LIS2 - A2) (161), and HL7 text content (237).
18 Using MODULAR PRE-ANALYTICS

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Handling batch test selections with strict rack and position 451

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 a
MODULAR PRE-ANALYTICS, navigate to Workplaces
> cobas 8000 data manager Service > Service-
related configuration > Interface options and select
the option Enable rack and position mode.

18 Using MODULAR PRE-ANALYTICS

By default, the data manager ignores any information
about rack and position in a batch test selection
message. The option Enable rack and position mode
configures the data manager so that it uses the
information on rack and position.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 452 Handling batch test selections with strict 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:
• the sample ID, passed in:
- ASTM Order Record (O) field 3, or
- HL7 Specimen Segment (SPM) field SPM-2.
• the rack number, passed in:
- ASTM Order Record (O) field 4, component 2, or
- HL7 Container Information Segment (SAC) fields
SAC-10
• the sample’s position on the rack (1 to 5). This is
passed in:
- ASTM Order Record (O) field 4, component 3, or
- HL7 Container Information Segment (SAC) field
SAC-11
• the sample type (or rack type), passed in:
- ASTM the Order Record (O) field 4, component 4,
or
- HL7 Specimen Segment (SPM) field SPM-4.

The data manager uses all the same fields to identify the
sample in result message.
18 Using MODULAR PRE-ANALYTICS

! WARNING
Do not move the sample to another rack
r If you are using the MODULAR PRE-ANALYTICS with
Rack and position mode, do 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.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Handling batch test selections with strict rack and position 453

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 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 data
manager Operator’s Manual.

18 Using MODULAR PRE-ANALYTICS

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 454
18 Using MODULAR PRE-ANALYTICS Handling batch test selections with strict rack and position

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 455
Table of contents

Identifying patient samples by

sequence number 19
Numbering samples in sequence instead of using a
barcode

19 Identifying patient samples by sequence number

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 19
Identifying samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Sample IDs and barcodes . . . . . . . . . . . . . . . . . . . . 457
Patient samples without barcodes . . . . . . . . . . . . . 457
Identifying patient samples by sequence number . . . 458
Sequence numbers and sample IDs . . . . . . . . . . . 459
What the data manager understands . . . . . . . . . . 459
Important information for using sequence numbers . 460
Using sample sequence numbers in ASTM . . . . . . . . 462
Test selection inquiry . . . . . . . . . . . . . . . . . . . . . . . . 462
Test selection download . . . . . . . . . . . . . . . . . . . . . 462
Test result message . . . . . . . . . . . . . . . . . . . . . . . . . 463
Using sample sequence numbers in HL7 . . . . . . . . . . 464
Test selection inquiry . . . . . . . . . . . . . . . . . . . . . . . . 464
Test selection download . . . . . . . . . . . . . . . . . . . . . 464
Test result message . . . . . . . . . . . . . . . . . . . . . . . . . 465
List of configuration settings for barcode and
sequence modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 456
Table of contents
19 Identifying patient samples by sequence number

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Identifying samples 457

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 modular
analyzer series 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.

19 Identifying patient samples by sequence number

This is the default configuration for the cobas® 8000
modular analyzer series 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 modular
analyzer series instrument to give each sample a
sequence number. This is described below.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 458 Identifying patient samples by sequence number

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:
• 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.
• To implement this on the data manager, the control
unit and the cobas® 8000 modular analyzer series
instrument, ask for assistance from your authorized
19 Identifying patient samples by sequence number

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.

NOTICE
Sequence numbers can only be used with patient
samples
r 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
r Note that sequence numbers cannot be used with
samples from a MODULAR PRE-ANALYTICS.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Identifying patient samples by sequence number 459

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:
• order queries for earlier samples which are identified
by barcode / sample ID. Any response is sent at once.
• result queries for earlier samples which are identified
by barcode / sample ID. Any response is sent at once.
• 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.

19 Identifying patient samples by sequence number

NOTICE
Identify a sample by either sample ID or sequence
number, but not both.
r 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 HL7 SPM-2, Sent in ASTM O-4.1, Q-3.4, or HL7 QPD-
QPD-3 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.
y Identifying the sample in messages

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 460 Important information for using sequence numbers

Important information for using sequence

numbers
When setting up or using sequence numbers, consider
the following.

! CAUTION
Only service personnel can enable or disable
sequence mode
r Only authorized Roche Diagnostics service personnel
can enable or disable sequence mode on the data
manager, the cobas® 8000 modular analyzer series
instrument and control unit.
19 Identifying patient samples by sequence number

Carefully observe the following warnings.

! WARNING
Regular database clean-up required
r The data manager and cobas® 8000 modular
analyzer series instrument can only handle 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 data manager
Service Manual from version 1.02.04 (available 2012),
for more information.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Important information for using sequence numbers 461

! WARNING
Do not start sample IDs with the same internal
prefix that is used in the data manager
r 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.

19 Identifying patient samples by sequence number

r 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.

! CAUTION
The sample ID sent by the host takes precedence
over the sequence number
r If the host sends a sample ID to the data manager, the
data manager uses the sample ID in 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
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 462 Using sample sequence numbers in ASTM

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:
• When using the default barcode sample IDs, the data
manager sends sample ID from the barcode in Q-3.3.
• When identifying samples by sequence number, the
data manager sends the sequence number in Q-3.4.
19 Identifying patient samples by sequence number

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:
• When using the default barcode sample IDs, the host
sends sample ID from the barcode in O-3.
• 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|201708…

Sequence number order record: either

O|1||3^^^^S1^SC^|^^^205^|R|201…

or

O|1||3^50094^3^^S1^SC^|^^^205^|R|201…

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Using sample sequence numbers in ASTM 463

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:
• When using the default barcode sample IDs, the data
manager sends sample ID from the barcode in O-3.
• When identifying samples by sequence number, the
data manager sends the sequence number in O-4.1.

Sample ID order record:

19 Identifying patient samples by sequence number

O|1|2110903|0^50094^3^^S1^SC^not|^^^112^1|R|201708
…

Sequence number order record:

O|1||3^50094^3^^S1^SC^not|^^^991^1|R|201…

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 464 Using sample sequence numbers in HL7

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:
• When using the default barcode sample IDs, the data
manager sends sample ID from the barcode in QPD-
3-1.
• When identifying samples by sequence number, the
data manager sends the sequence number in QPD-
19 Identifying patient samples by sequence number

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:
• When using the default barcode sample IDs, the host
sends sample ID from the barcode in SPM-2.1.
• 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|||^^^^|||2017061521542
4||||||||||SC

Sequence number specimen and container detail

segments:

SPM||^3||S1||not|||||P|||^^^^|||20170615215424||||
||||||SC

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Using sample sequence numbers in HL7 465

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:
• 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.
• When identifying samples by sequence number, the
data manager sends the sequence number in SPM-

19 Identifying patient samples by sequence number

2.2, and the rack ID in SAC-10, and tube’s position in
SAC-11.

Sample ID specimen and container detail segments:

SPM||2110903||S1||not|||||P|||^^^^|||2017061521542
4||||||||||SC|

SAC||||||||||50094|3|

Sequence number specimen and container detail

segments:

SPM||^3||S1||not|||||P|||^^^^|||20170617105639||||
||||||SC|

SAC||||||||||50094|3|

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 466 List of configuration settings for barcode and sequence modes

List of configuration settings for barcode

and sequence modes
This chart shows how the availability of sequence mode
and barcode mode differs in accordance with the
configuration.

Configuration Availability
data manager Control unit Control unit Barcode mode Sequence mode Aliquots without
sequence number STAT / Routine TS Ask in Barcode barcodes from data
support installed barcode reader read Error manager
ON Available Not available Available
ON
Installed OFF Available Not available Not available
OFF N/A Not available Available Not available
ON Available Not available Available
ON
19 Identifying patient samples by sequence number

Not Installed OFF Available Not available Not available

OFF N/A Not available Not available Not available
y Table describing setup of data manager infrastructure to work in different modes

Other combinations are not supported.

To set these options:

• 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.
• STAT / Routine barcode reader on control unit: on the
control unit, navigate to Utility > System > Barcode
Settings > Routine/Stat.
• Test selection ask in barcode read error on the control
unit:
u For details, see Test Selection Ask in Barcode Read
Error (137).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 467
Table of contents

Preparing the host communication20

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 ANALYTICS EVO analyzer / cobas® 6000
analyzer series and cobas® 8000 data manager.

20 Preparing the host communication

In this chapter 20
General differences in the ASTM protocol . . . . . . . . . 469
Message encoding and transport . . . . . . . . . . . . . 469
Sample identification . . . . . . . . . . . . . . . . . . . . . . . . 470
Sample types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Patient demographics . . . . . . . . . . . . . . . . . . . . . . . 471
ASTM message types. . . . . . . . . . . . . . . . . . . . . . . . 471
HL7 message types . . . . . . . . . . . . . . . . . . . . . . . . . 472
Differences in ASTM message definitions . . . . . . . . . 473
General differences in the ASTM messages. . . . . 473
Message Header Record . . . . . . . . . . . . . . . . . . . . . 473
Message Termination Record . . . . . . . . . . . . . . . . . 473
Patient Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Order Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Result Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Comment Record (following an Order Record) . . 478
Comment Record (following a Result Record) . . . 478
Query Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Photometric Calibration Result Record . . . . . . . . . 479
ISE Calibration Result Record . . . . . . . . . . . . . . . . . 479
E-module (Immunology) Calibration Result
Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Other differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 468
Table of contents

Rerun results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

LIS communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Identifying samples by sequence number . . . . . . . . . 484
Traceability information for quality control and
calibration results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
The specimen segment SPM with quality control
results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
The specimen segment SPM with calibration
results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
The substance identifier segment SID. . . . . . . . . . 486
Data points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
20 Preparing the host communication

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 General differences in the ASTM protocol 469

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

! WARNING
Extended ASCII is converted to UTF-8
r 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. You need to use a conversion
mechanism to convert extended ASCII value to UTF-8.

Item MODULAR ANALYTICS EVO cobas® 8000 data manager Comment

analyzer / cobas® 6000
analyzer series
Character encoding Not specified / Only ASCII can UTF-8. That means characters
be truly supported due to up to 127 are compatible with

20 Preparing the host communication

possible 7-bit data transfer ASCII
option 8- bit data transfer used.
ASTM Message Type(s) ASTM E1381 (low level), ASTM E1381 (low level),
ASTM E1394 (message) ASTM E1394 (message)
HL7 Messaging Not supported Minimal Layer Protocol HL7 Extended
2.5
RS232 Variable settings, editable Fixed to 19200, 8 N 1 (could
from graphical user interface be changed by configuration
file)
Network Not supported TCP/IP socket client (could be Extended
changed by configuration
files)
y Message encoding, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 470 General differences in the ASTM protocol

Sample identification
Item MODULAR ANALYTICS EVO cobas® 8000 data manager Comment
analyzer / cobas® 6000
analyzer series

Sample number mode(1) Yes (Only for Batch Download Sequential sample numbering Similar functionality.
with Sample Barcode Reader available from 1.02.03 for u See Identifying patient
= OFF) patient samples.
samples by sequence
number (455)
Barcode label Yes Yes
Rack & Sample Position Yes Yes
y Sample identification, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series
(1) 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 modular analyzer series instrument.
20 Preparing the host communication

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
®
y Sample types, compared to the MODULAR ANALYTICS EVO analyzer / cobas 6000 analyzer series

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 General differences in the ASTM protocol 471

Patient demographics
Item MODULAR ANALYTICS EVO cobas® 8000 data manager Comment
analyzer / cobas® 6000
analyzer series
First Name Comment Record after Order Patient Record See, more Details below
Record
Last Name Comment Record after Order Patient Record See, more Details below
Record
Date of Birth Comment Record after Order Patient Record See, more Details below
Record
Patient’s age Patient Record No (coded in Date of Birth) See, more Details below
Patient’s age unit Patient Record No (coded in Date of Birth) See, more Details below
®
y Patient demographics, compared to the MODULAR ANALYTICS EVO analyzer / cobas 6000 analyzer series

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 Reduced
host

20 Preparing the host communication

Result Report (realtime) RSUPL^REAL RSUPL data manager to Reduced
host
Result Report (batch) RSUPL^BATCH RSUPL data manager to Reduced
host
Result Report (quality control: for RSUPL^REAL RSUPL^REAL data manager to (Unchanged for QC
first upload of results) host results)
Result Report (quality control: when RSUPL^BATCH RSUPL^BATCH data manager to (Unchanged for QC
repeating uploads of results host 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 Reduced
inquiry) manager
Test Selection Download TSDWN^BATCH TSDWN host to data Reduced
(unsolicited) manager
Inquiry of Result RSREQ^BATCH RSREQ host to instrument Reduced
Inquiry for Requested Test n/a TSREQ host to data Enhanced
manager
y ASTM message types, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 472 General differences in the ASTM protocol

HL7 message types

Item MODULAR ANALYTICS EVO cobas® 8000 data manager Comment
analyzer / cobas® 6000
analyzer series
Inquiry for the Requested NO TSREQ Extended
Tests
Result Report (realtime) NO OUL^R22 Extended
Result Report (batch) NO OUL^R22 Extended
Quality Control Result Report NO OUL^R22^REAL Extended
(realtime)
Quality Control Result Report NO OUL^R22^BATCH Extended
(batch)
Test Selection Download NO OML^O33 Extended
(inquiry)
Test Selection Download NO OML^O33 Extended
(inquiry)
Photometric Calibration Result NO OUL^R22^PCUPL Extended
ISE Calibration Result NO OUL^R22^ICUPL Extended
Immunology Calibration NO OUL^R22^ECUPL Extended
Result
Masking command NO EAC^U07 Extended
Equipment Status Request NO ESR^U02 Extended
Equipment Status Update NO ESU^U01 Extended
Inventory Status Request NO INR^U06 Extended
20 Preparing the host communication

Inventory Status Update NO INU^U05 Extended

y HL7 message types, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Differences in ASTM message definitions 473

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

20 Preparing the host communication

3 Control ID NO YES Extended
5 data manager to As specified at host Editable in Interface options,
host: setting screen default cobas 8000^1
Sender ID
10 data manager to As specified at host Fixed to host
host: setting screen
Receiver ID
11 Comment or special See ASTM Msg. See ASTM Msg. Types See above
instruction Types
14 Date/Time of No Yes, YYYYMMDDhhmmss Extended
message
y Header record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Message Termination Record

Field Description MODULAR cobas® 8000 data manager Comment
ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
3 Termination Code N, T, R, E, Q, I, T N Reduced
y Termination record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 474 Differences in ASTM message definitions

Patient Record
The cobas® 8000 data manager supports no patient age
information, but uses the patient’s day of birth instead.

Field Description MODULAR cobas® 8000 data manager Comment

ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
6, C1,C2 Patient name 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
y Patient record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

! WARNING
The data manager supports only M, F, or U for
patient sex.
r For male patients, the host must send M, for females,
F. Otherwise the wrong reference range might be
applied. The data manager reads any other value as U,
and applies the reference ranges for a patient of
unknown sex.
r Make sure the host sends only M, F, or U, as required.
20 Preparing the host communication

Each new configuration must be tested to ensure the

correct data transfer between the data manager and
the host.

u For more information, see Patient demographics (471).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Differences in ASTM message definitions 475

Order Record
The cobas® 8000 data manager supports:
• 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.
• rack types S1 to S9 + SA, but MODULAR
ANALYTICS EVO analyzer / cobas® 6000 analyzer
series only supports S1 to S5
• dilution factors changed, and no dilution shown by 1,
not by an empty component.
• Action code “R” for reruns: “A” however can also be
used for ordering reruns.
• 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

20 Preparing the host communication

analyzer series
3 Sample ID for Control-SID: Name Name^LotNr^Control- Extended, Upload
controls or Lotnumber ID^ExpDate^ControlCode
(Selectable at Host (if no sample ID)
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
5,C5 Universal Test ID, Photometry: ISE module: Reduced for
Dilution Inc,Dec,3,5,10,20,50, o 1 photometry (c-
100,empty c-module: modules).
o 1, Inc, Dec, 3, 5, Otherwise, extended
10, 20, 50 Also, the value 1 is
e 602 module: now sent for “No
o 1, 2, 5, 10, 20, 50, dilution”. When sent
100, 400 from the host (TS
e 801 module download), in case
o 1 , 1.1 , 2 , 5 , 10 , 20 , 30 , of no pending test
50 , 100 , 400 , 900 , on the host side this
27000 field has to be empty
7 Requested/ Not used Yes, YYYYMMDDhhmmss Extended
Ordered Date and
Time
y Order record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 476 Differences in ASTM message definitions

Field Description MODULAR cobas® 8000 data manager Comment

ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
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
y Order record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

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

20 Preparing the host communication

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.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Differences in ASTM message definitions 477

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, For a c-module, dilution”.
100 o 1, Inc, Dec, 3, 5, 10, 20, 50
For an e 602 module,
o 1, 2, 5, 10, 20, 50, 100, 400
For an e 801 module,
o 1, 1.1, 2, 5, 10, 20, 30, 50, 100,
400, 900, 27000
4,C1 Measurement value Qualitative Value ReportableResult Change, extended
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.
For e 801 cobas e flow tests in
HL7, over 50 comment codes are
available.
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

20 Preparing the host communication

6 Reference ranges No Reference ranges Extended
7 Result abnormal A=Abnormal A=Alphanumeric out of normal Extended
flags range
AA=Alphanumeric out of critical
range
EP17-A 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
13 Date/Time Test No Yes Extended
completed
14 Measurement unit P1,P2,P3,P4,ISE1,ISE ModuleType^SubModule^ Extended
ID (Module or 2,Exy AnalyticalUnitID^
Instrument ID) InstrumentID^CalID^Bottle
^SBNo
Bottle^SBNo used only for QC.
ModuleTypes: c502 , c701 ,
e602 , c702 , ISE , e801 , DM ,
c8000
y Result record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 478 Differences in ASTM message definitions

Comment Record (following an Order Record)

Field Description MODULAR cobas® 8000 data manager Comment
ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
3 Comment Source “I” by Analyzer, “L” “I” by Analyzer, “L” by Host or data
by Host manager
y Comment record, after order record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

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 Extended
manager
20 Preparing the host communication

4 Comment Text, if Flagnumber Flagnumber^Description Extended

type I
5 Comment Type, if No Text^User^Date Extended
type G
y Comment record, after result record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Query Record
Field Description MODULAR cobas® 8000 data manager Comment
ANALYTICS EVO
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, SA Extended
12 User Field 2 No Priority: Extended
o R = Routine
o S = STAT
13 Request Information o A=Rejects o O=Request for Test Request Reduced
Status Code previous req. o F=Final Result
o O=Request for
Test Request
o F=Final Result
y Query record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Differences in ASTM message definitions 479

Photometric Calibration Result Record

Field Description MODULAR cobas® 8000 data manager Comment
ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
6 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 safely editable.
9, C6 Prozone value Sent Not sent Reduced
10 Reagent lot number 1 to 99999999 Sent in HL7 SID-2 Reduced in ASTM,
available in HL7
11 Reagent bottle 1 to 19999 Sent in HL7 SPM-2.4 Reduced in ASTM,
number available in HL7
12 Expired flag 0 or 1 Not sent Reduced
13 Calibrator lot 1 to 99999999 Sent in HL7 SPM-2.2 Reduced
number
14 Pipetting date and YYYYMMDDHHMM Not sent Reduced
time SS
y Photometric calibration result record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

20 Preparing the host communication

ISE Calibration Result Record
Field Description MODULAR cobas® 8000 data manager Comment
ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
5 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.
9,C7 Na Data alarms Component 7 Component 7 contains: Extended
contains: Carryover rate alarm
Numbers for (Numbers for compensation alarm
compensation alarm passed in Component 10.)
9,C8 Calculation slope Not supported Supported Extended
value alarm
9,C10 Numbers for Passed in Passed in Component 10
compensation alarm Component 7
10,C7 K Data alarms Component 7 Component 7 contains: Extended
contains: Carryover rate alarm
Numbers for (Numbers for compensation alarm
compensation alarm passed in Component 10.)
y ISE calibration result record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 480 Differences in ASTM message definitions

Field Description MODULAR cobas® 8000 data manager Comment

ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
10,C8 Calculation slope Not supported Supported Extended
value alarm
10,C10 Numbers for Passed in Passed in Component 10
compensation alarm Component 7
11,C7 Cl Data alarms Component 7 Component 7 contains: Extended
contains: Carryover rate alarm
Numbers for (Numbers for compensation alarm
compensation alarm passed in Component 10.)
11,C8 Calculation slope Not supported Supported Extended
value alarm
11,C10 Numbers for Passed in Passed in Component 10
compensation alarm Component 7
12,C7 Na Calibration Component 7 Component 7 contains: Extended
analytical data contains: Carryover rate
Numbers for (Numbers for compensation data
compensation data passed in Component 10.)
12,C8 Calculation slope Not supported Supported Extended
value alarm
12,C10 Numbers for Passed in Passed in Component 10
compensation data Component 7
13,C7 K Calibration Component 7 Component 7 contains: Extended
analytical data contains: Carryover rate
Numbers for (Numbers for compensation data
compensation data passed in Component 10.)
20 Preparing the host communication

13,C8 Calculation slope Not supported Supported Extended

value alarm
13,C10 Numbers for Passed in Passed in Component 10
compensation data Component 7
14,C7 Cl Calibration Component 7 Component 7 contains: Extended
analytical data contains: Carryover rate
Numbers for (Numbers for compensation data
compensation data passed in Component 10.)
14,C8 Calculation slope Not supported Supported Extended
value
14,C10 Numbers for Passed in Passed in Component 10
compensation data Component 7
y ISE calibration result record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

E-module (Immunology) Calibration Result Record

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Differences in ASTM message definitions 481

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 InheritedLotCalibratio
n
o InheritedItemCalibrati
on
o UserModifiedCalibratio
n
o UnmaskedCalibration
o FailedCalibration
7 Analytical Unit ID P1,P2,P3,P4,ISE1,ISE2, AnalyticalUnitID, default: Extended
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

20 Preparing the host communication

numbers
16 Unit String Not supported Reduced
17 Cut off Number Not supported Reduced
18 Border line area Complex field Not supported Reduced
y E-module (immunology) calibration result record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000
analyzer series

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 482 Other differences

Other differences
There are differences between the cobas® 8000 data
manager and the compared to the MODULAR
ANALYTICS EVO analyzer / cobas® 6000 analyzer
series in character encoding, handling of reruns, LIS
communication protocols, and other areas.

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 ANALYTICS EVO cobas® 8000 data manager Comment
20 Preparing the host communication

analyzer / cobas® 6000

analyzer series
Stored rerun results Can store and send: Can store and send all results Extended
o first result for a test.
o most recent result
for a test.
y Rerun results, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 LIS communications 483

LIS communications
Item MODULAR ANALYTICS EVO cobas® 8000 data manager Comment
analyzer / cobas® 6000
analyzer series
Communication protocols ASTM over serial. o HL7 over TCP/IP Extended
o ASTM over TCP/IP
o ASTM over serial
y LIS communication protocols, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Details u For details of how to select a connection, see Starting

and stopping the host connection (95).
u For details of the physical connections, see Physical
layer specifications (124).

20 Preparing the host communication

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 484 Identifying samples by sequence number

Identifying samples by sequence number

Since version 1.02.03, it is possible to identify samples by
a sequential number.

Item MODULAR ANALYTICS EVO cobas® 8000 data manager Comment

analyzer / cobas® 6000
analyzer series
Identification of samples Barcode and sample ID. o Barcode and sample ID Extended
o Sequential numbering
o Rack and position
y Sequence numbers, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series

Details u For details of how to identify samples by a sequential

number, see Identifying patient samples by sequence
number (455).
u For details of how to identify samples by a strict rack
and position, see Using MODULAR PRE-
ANALYTICS (445), and Rack and position mode (104).
20 Preparing the host communication

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Traceability information for quality control and calibration results 485

Traceability information for quality control

and calibration results
Since version 1.02.05, data manager sends traceability
data with quality control and calibration results. This is
only supported in HL7.

The specimen segment SPM with quality control results

Item MODULAR ANALYTICS EVO cobas® 8000 data manager Comments
analyzer / cobas® 6000
analyzer series
Control identification. Control name in record O-4. SPM-2: Extended
Name^Lot^ID^ExpiryDat
e^ControlCode
Control lot (Number) Not available SPM-2.2 Extended
Control identifier (a unique Not available SPM-2.3 Extended
control ID contained in data
manager). (Number)
Expiry date of control lot. Not available SPM-2.4 Extended
Control code (an additional Not available SPM-2.5 Extended
unique identifier in data

20 Preparing the host communication

manager).
y Comparison of specimen segment SPM fields for quality control results in recent versions

The specimen segment SPM with calibration results

Item MODULAR ANALYTICS EVO cobas® 8000 data manager Comments
analyzer / cobas® 6000
analyzer series
Calibration identification. Not available. SPM-2: For c-module and e- Extended
module calibration materials,
Level^Lot^Code^Count^
Expirydate
For ISE module calibration
results: empty.
y Comparison of specimen segment SPM fields for quality control results in recent versions

u In calibration results, the SPM segment is used

differently than in other messages, see SPM in
calibration results (250).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 486 Traceability information for quality control and calibration results

The substance identifier segment SID

This section lists the changes to the substance identifier
segment SID.

Item MODULAR ANALYTICS EVO cobas® 8000 data manager Comments

analyzer / cobas® 6000
analyzer series
Substance identifier o Not supported by c- SID-1 Extended
(for calibration results) module (photometry) or o Supported by c-module
ISE calibration results. calibration results.
o Not supported by ISE
calibration results.
Reagent lot o Not supported by c- SID-2 Extended
module (photometry) or o Supported by c-module
ISE calibration results. and e-module calibration
o Supported by e-module results.
(immunology) calibration o Not supported by ISE
results. calibration results.
Reagent serial number Not supported by calibration SID-3 Extended
results. o Supported by c-module
and e-module calibration
results.
o Not supported by ISE
calibration results.
y Comparison of substance identifier segment SID fields in recent versions
20 Preparing the host communication

Data points
The cobas® 8000 modular analyzer series also supports
data point results. The laboratory user can manually
instruct the control unit to send a data point result
message.
u ASTM:
Result Record (178)
e 602 result with data point values (211)
u HL7:
Observation Result Segment - OBX (255)
e 602 result message with data point values (313)
u cobas® 8000 data manager Operator’s Manual

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 487
Table of contents

Text encoding tables 21

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 21
ASCII character codes . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Western European characters in UTF-8 . . . . . . . . . . . . 490

21 Text encoding tables

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 488
Table of contents
21 Text encoding tables

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 ASCII character codes 489

ASCII character codes

The 127 ASCII character codes are shown below, with
each hexadecimal and decimal value.

NUL DLE Space 0 @ P ‘ p

00 0 10 16 20 32 30 48 40 64 50 80 60 96 70 112
SOH DC1 ! 1 A Q a q
01 1 11 17 21 33 31 49 41 65 51 81 61 97 71 113
STX DC2 " 2 B R b r
02 2 12 18 22 34 32 50 42 66 52 82 62 98 72 114
ETX DC3 # 3 C S c s
03 3 13 19 23 35 33 51 43 67 53 83 63 99 73 115
EOT DC4 $ 4 D T d t
04 4 14 20 24 36 34 52 44 68 54 84 64 100 74 116
ENQ NAK % 5 E U e u
05 5 15 21 25 37 35 53 45 69 55 85 65 101 75 117
ACK SYN & 6 F V f v
06 6 16 22 26 38 36 54 46 70 56 86 66 102 76 118
BEL ETB ’ 7 G W g w
07 7 17 23 27 39 37 55 47 71 57 87 67 103 77 119
BS CAN ( 8 H X h x
08 8 18 24 28 40 38 56 48 72 58 88 68 104 78 120
HT EM ) 9 I Y i y
09 9 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

21 Text encoding tables

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
y ASCII table

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 490 Western European characters in UTF-8

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 Char UTF-8 Name Unicode Chara UTF-8 Name

code acter (hex.) code cter (hex.)
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
21 Text encoding tables

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
y Western european characters in UTF-8

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Western European characters in UTF-8 491

Unicode Char UTF-8 Name Unicode Chara UTF-8 Name

code acter (hex.) code cter (hex.)
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
U+0084
c2 82 <control>
c2 84 <control>
U+0083
U+0085
c2 83
c2 85
<control>
<control>
21 Text encoding tables
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>
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>
y Western european characters in UTF-8

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 492 Western European characters in UTF-8

Unicode Char UTF-8 Name Unicode Chara UTF-8 Name

code acter (hex.) code cter (hex.)
point point
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 ² c2 b2 SUPERSCRIPT TWO U+00B3 ³ 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 ¹ c2 b9 SUPERSCRIPT ONE
U+00BA º c2 ba MASCULINE ORDINAL U+00BB » c2 bb RIGHT-POINTING DOUBLE
INDICATOR 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 WITH U+00C1 Á c3 81 LATIN CAPITAL LETTER A
GRAVE WITH ACUTE
U+00C2 Â c3 82 LATIN CAPITAL LETTER A WITH U+00C3 Ã c3 83 LATIN CAPITAL LETTER A
CIRCUMFLEX WITH TILDE
U+00C4 Ä c3 84 LATIN CAPITAL LETTER A WITH U+00C5 Å c3 85 LATIN CAPITAL LETTER A
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 WITH U+00C9 É c3 89 LATIN CAPITAL LETTER E
21 Text encoding tables

GRAVE WITH ACUTE

U+00CA Ê c3 8a LATIN CAPITAL LETTER E WITH U+00CB Ë c3 8b LATIN CAPITAL LETTER E
CIRCUMFLEX WITH DIAERESIS
U+00CC Ì c3 8c LATIN CAPITAL LETTER I WITH U+00CD Í c3 8d LATIN CAPITAL LETTER I
GRAVE WITH ACUTE
U+00CE Î c3 8e LATIN CAPITAL LETTER I WITH U+00CF Ï c3 8f LATIN CAPITAL LETTER I
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 WITH U+00D3 Ó c3 93 LATIN CAPITAL LETTER O
GRAVE WITH ACUTE
U+00D4 Ô c3 94 LATIN CAPITAL LETTER O WITH U+00D5 Õ c3 95 LATIN CAPITAL LETTER O
CIRCUMFLEX WITH TILDE
U+00D6 Ö c3 96 LATIN CAPITAL LETTER O WITH U+00D7 × c3 97 MULTIPLICATION SIGN
DIAERESIS
U+00D8 Ø c3 98 LATIN CAPITAL LETTER O WITH U+00D9 Ù c3 99 LATIN CAPITAL LETTER U
STROKE WITH GRAVE
y Western european characters in UTF-8

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Western European characters in UTF-8 493

Unicode Char UTF-8 Name Unicode Chara UTF-8 Name

code acter (hex.) code cter (hex.)
point point
U+00DA Ú c3 9a LATIN CAPITAL LETTER U WITH U+00DB Û c3 9b LATIN CAPITAL LETTER U
ACUTE WITH CIRCUMFLEX
U+00DC Ü c3 9c LATIN CAPITAL LETTER U WITH U+00DD Ý c3 9d LATIN CAPITAL LETTER Y
DIAERESIS WITH ACUTE
U+00DE Þ c3 9e LATIN CAPITAL LETTER THORN U+00DF ß c3 9f LATIN SMALL LETTER
SHARP S
U+00E0 à c3 a0 LATIN SMALL LETTER A WITH U+00E1 á c3 a1 LATIN SMALL LETTER A
GRAVE WITH ACUTE
U+00E2 â c3 a2 LATIN SMALL LETTER A WITH U+00E3 ã c3 a3 LATIN SMALL LETTER A
CIRCUMFLEX WITH TILDE
U+00E4 ä c3 a4 LATIN SMALL LETTER A WITH U+00E5 å c3 a5 LATIN SMALL LETTER A
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 WITH U+00E9 é c3 a9 LATIN SMALL LETTER E
GRAVE WITH ACUTE
U+00EA ê c3 aa LATIN SMALL LETTER E WITH U+00EB ë c3 ab LATIN SMALL LETTER E
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 WITH U+00F3 ó c3 b3 LATIN SMALL LETTER O
GRAVE WITH ACUTE
U+00F4 ô c3 b4 LATIN SMALL LETTER O WITH U+00F5 õ c3 b5 LATIN SMALL LETTER O
CIRCUMFLEX WITH TILDE
U+00F6 ö c3 b6 LATIN SMALL LETTER O WITH U+00F7 ÷ c3 b7 DIVISION SIGN
DIAERESIS
U+00F8 ø c3 b8 LATIN SMALL LETTER O WITH U+00F9 ù c3 b9 LATIN SMALL LETTER U
STROKE WITH GRAVE
U+00FA ú c3 ba LATIN SMALL LETTER U WITH U+00FB û c3 bb LATIN SMALL LETTER U

21 Text encoding tables

ACUTE WITH CIRCUMFLEX
U+00FC ü c3 bc LATIN SMALL LETTER U WITH U+00FD ý c3 bd LATIN SMALL LETTER Y
DIAERESIS WITH ACUTE
U+00FE þ c3 be LATIN SMALL LETTER THORN U+00FF ÿ c3 bf LATIN SMALL LETTER Y
WITH DIAERESIS
y Western european characters in UTF-8

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 494
21 Text encoding tables Western European characters in UTF-8

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Glossary

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Glossary 497
across controls - laboratory information system

Glossary 22
data alarm Additional piece of information
associated with a test, QC or calibration result. It is
across controls Option on a Westgard rule. It caused by an abnormal condition with regard to a
specifies that a rule is applied across several QC measurement.
materials for the same test.
data point During a measurement, on every cobas®
calculated QC A calculated QC is a result calculated 8000 modular analyzer series, the instrument provides
by a defined formula. It is needed as a combined QC a series of single measuring points (approximately 200
result for cobas e flow tests. values for each test result). With the corresponding
calculated test Test for which the result is configuration only, these data points are sent from the
calculated on the basis of other measured test results, control unit to the data manager. Data points are not
with the help of algorithms and formulas. displayed on the data manager or in TraceDoc.

carryover Contamination of a test by reagents or a development channel Feature which allows an

sample of a previous test. operator to run tests not provided by Roche on the
system. For such tests parameters must be set
c-module The c-modules, c 502, c 701, and c 702, manually.
perform clinical chemistry tests using photometry.
diluent Liquid used to dilute samples or to affect an
cobas e flow test Product name for a test that analytical reaction.
consists of a pre-defined combination and sequence
of embedded tests. The combinations are provided by dilution factor Ratio of final volume of
Roche and are not editable by the customer. sample/aliquot volume. Final volume = aliquot +
diluent.
cobas e flow test result Main and subresults
reported by cobas e flow test in the form of a embedded test Test that is required for calculating a
calculated, qualitative value, or measured embedded cobas e flow test and can be ordered exclusively by a
tests. cobas e flow test. It cannot be ordered by the host or
manually by the user.
cobas e pack Product name for the reagent
cassettes used for immunology testing on cobas e e-module The e-modules, e 602 or Elecsys, and
modules and Elecsys® systems. The cobas e pack is e 801 perform immunological tests.
an integrated reagent carrier consisting of 3 reagent host A Laboratory Information System (LIS) or other
bottles. IT solutions (middle ware) which is connected to the
system.
cobas e packs for the cobas e 801 module are
delivered with an RFID tag, which contains references instrument group Group of instruments that are
to the parameter file. listed together based on a predefined parameter.
ISE module The ISE module, or Ion-Sensitive-
The following data is needed for a unique Electrode module, performs clinical chemistry tests for
identification of a cobas e pack: analyzing levels of the electrolytes Na, Cl, and K.
• Reagent cassette lot number laboratory information system Computer system
• Reagent container code that supports the automation of laboratory
• Container count number (bottle sequence number) management.
• Reagent expiry date
Glossary

comment group Group of comments that can be

assigned to data in specified contexts.
copy QC Feature which allows to copy QC data from
master ACN to the additional ACN of the same type
(on the same cobas e pack).

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
498 Glossary
linked tests, linked kits - reference range

linked tests, linked kits Roche-internal dependency QC Measure of precision or how well the
rule for certain embedded tests and cobas e packs measurement system reproduces the same result over
which specifies the sequence of pipetting during the time and under varying operating conditions. It is
measurement procedure. designed to detect, reduce, and correct deficiencies in
a laboratory's internal analytical process prior to the
A reagent kit consists of 2 to 10 cobas e packs release of patient results and improve the quality of
inclusive. These are logically linked during loading into the results reported by the laboratory.
the instrument by the software via the same reagent
lot number. QC refers to methods to ensure the reliability and
consistency of reagents and the results based on
Linked tests are linked by cobas e pack. reactions using the reagents, on a per application
basis.
LIS Computer system that supports the automation of
laboratory management.
This document distinguishes between 2 types of QC:
log file File that contains records of specific events
• Single QC (or measured QC)
that have occurred on a system.
• Calculated QC
lower limit The lowest allowed or available value of a
variable. A single QC is measured on the instrument and refers
masking Temporarily preventing the system from to an embedded test or regular test.
performing activities on, or accessing a selected item,
A calculated QC is calculated with a mathematical
for example module, instrument, test.
formula and refers to a cobas e flow test.
measurement unit Real scalar quantity, defined and
QC bracketing Setting in which a test result must be
adopted by convention, with which any other quantity
preceded by, and followed by, a successful QC result
of the same kind can be compared to express the ratio
before it is released.
of the two quantities as a number. NOTE 1
Measurement units are designated by conventionally QC material A substance, material or article
assigned names and symbols. NOTE 2 For a given intended by its manufacturer to be used to verify the
quantity, the short term unit is often combined with the performance characteristics of an in vitro diagnostic
quantity name, such as mass unit or unit mass. NOTE 3 medical device (ISO 15197). Note: A device, material,
Measurement units of quantities of dimension one are solution, or lyophilized preparation intended for use in
numbers. In some cases these measurement units are the quality control process. It should be similar to, and
given special names, e.g. radian, steradian and is analyzed along with, patient samples. If different, it
decibel, or are expressed by quotients such as should have a recognized, defined response to
millimole per mole equal to 10-3 and microgram per analytical measurements. QC materials may or may not
kilogram equal to 10-9. (ISO/lEG Guide 99:2007, have known measurand concentration (i.e. assigned
definition 1.9) values) within specified limits (e.g. target value,
standard deviation). They are not used for calibration
measuring cell A set of hardware components for
purposes.
performing a test. The analytical cobas e 801 module
and the cobas e 602 module have 2 measuring cells QC result Result of a QC test.
(“cell” for short).
QC test Test which is run with QC material.
pass-through mode Operation mode that allows the
rack reception mode Operation mode in which the
system software to send results to another system
system remains in operation after the last test result
without any assessment, modification, or validation.
has been generated and until one of the following
Glossary

conditions occurs: this operating mode was

terminated or the system entered the standby mode
regularly.
reference range Range of test results expected for a
defined group of healthy patients or materials.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Glossary 499
RRM - within control

RRM Operation mode in which the system remains in

operation after the last test result has been generated
and until one of the following conditions occurs: this
operating mode was terminated or the system entered
the standby mode regularly.
software update installer Component of
cobas® 8000 data manager which enables users to
install new software packages.
SUI Component of cobas® 8000 data manager which
enables users to install new software packages.
test masking Temporarily preventing the system
from performing a test. This includes QC runs and
calibrations.
test order Record or data structure defining a test to
be performed by the instrument, using an order or lab
test code that might need to be mapped to an
instrument code.
test selection download A message containing test
orders that the host downloads to the cobas® 8000
data manager.
UL Underwriters Laboratories Inc. is an independent,
product safety testing and certification organization.
Underwriters Laboratories Inc. Independent,
product safety testing and certification organization.
unit Real scalar quantity, defined and adopted by
convention, with which any other quantity of the same
kind can be compared to express the ratio of the two
quantities as a number. NOTE 1 Measurement units
are designated by conventionally assigned names and
symbols. NOTE 2 For a given quantity, the short term
unit is often combined with the quantity name, such as
mass unit or unit mass. NOTE 3 Measurement units of
quantities of dimension one are numbers. In some
cases these measurement units are given special
names, e.g. radian, steradian and decibel, or are
expressed by quotients such as millimole per mole
equal to 10-3 and microgram per kilogram equal to
10-9. (ISO/lEG Guide 99:2007, definition 1.9)
upper limit The highest allowed or available value of
a variable.
virtual keyboard Keyboard displayed and used on a
Glossary

touch screen.
within control Option on a Westgard rule. It specifies
that a rule only applies to one QC material of a test.

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
500 Glossary
within control - within control
Glossary

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Glossary 501
within control - within control

Glossary

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
502 Glossary
within control - within control
Glossary

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Index

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Index 505

Index

Symbols Numerics

< >Test (data alarm) 8100, see cobas® 8100 instrument, 105
– ISE, 380
<SigL (data alarm)
– e 602, 403
A
>Abs (data alarm)
AA, HL7 acknowledgment, 297
– c modules, 383
Absorbance
>Curr (data alarm)
– photometric calibration results ASTM, 193
– e 602, 396
– photometric calibration results HL7, 271
>I.H (data alarm)
ACK
– c modules, 387
– message structure HL7, 241
– e 602, 397
– MSH segment, 243
– ISE, 376
Acknowledgment
>I.HI (data alarm)
– application, MSH segment, 244
– c modules, 387
– ASTM, 158
– e 602, 398
– code, MSA segment, 245
– ISE, 376
– example test selection messages, 308
>I.I (data alarm)
– HL7 overview, 102
– c modules, 387
– message structure in HL7, 241
– e 602, 398
– message type, 243
– ISE, 376
Action code
>I.L (data alarm)
– ASTM, 175
– c modules, 387
– HL7, 253
– e 602, 398
ADC.E (data alarm)
– ISE, 377
– c modules, 383
>I.LH (data alarm)
– ISE, 372
– c modules, 387
Addresses, 6
– e 602, 398
AE, HL7 acknowledgment, 297
– ISE, 377
Alarm
>I.LHI (data alarm)
– data alarm, 363
– c modules, 388
Alarms
– e 602, 398
– calibration alarm photometric ASTM, 193
– ISE, 377
– calibration alarms ISE ASTM, 194
>I.LI (data alarm)
– calibration flags HL7, 266
– c modules, 388
– data alarms HL7, 280
– e 602, 399
– data alarms list, 367
– ISE, 377
– data alarms, ASTM, 188
>Kin (data error)
– data alarms, ISE calibration results ASTM, 194
– c modules, 388
– data alarms, ISE calibration results HL7, 272
>Lin (data alarm)
– instrument alarms list, 425
– c modules, 388
– instrument alarms, calibration results HL7, 276
>Proz (data alarm)
– instrument alarms, photometric calibration results
– c modules, 390
ASTM, 193
>React (data alarm)
– result abnormal examples ASTM, 210
– c modules, 391
– result abnormal examples HL7, 312
>Rept / <Rept (data alarm)
– result abnormal flags ASTM, 181
– e 602, 401
– result abnormal flags HL7, 258
Index

>Sig (calibration alarm)

Always ask for test selection, 99
– e 602, 412
Analytical data
>Test / <Test (data alarm)
– calibration ASTM, 194
– c modules, 392
– calibration HL7, 272
– e 602, 404
Analytical Unit ID
– ISE, 381
– configuration, 108
– E-module calibration results ASTM, 197

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
506 Index

– ISE calibration ASTM, 193 – ASTM, 183

– ISE calibration results ASTM, 194 – HL7 calibration, 267
– ISE calibration results HL7, 267 – HL7, QC, 264
– masking message HL7, 290 – standby, ASTM, 183
– OBX segment HL7, 260 – standby, HL7, 264
– OBX segment HL7 QC, 264 – standby, HL7 calibration, 267
– overview, 108
– photometric and E-module calibration results HL7,
267
C
– result record ASTM, 183
c modules
Analyzer
– data alarms, 383
– cobas® 8000 modular analyzer series, 29
c702, 30
– MODULAR ANALYTICS EVO analyzer / cobas®
Cables
6000 analyzer series, upgrading from, 469
– diagram, 124
Application Code. See Testcode, 277
– recommendations, 126
AR, HL7 acknowledgment, 297
Cal.I (data alarm)
As soon as setting, 140, 141
– c modules, 384
ASCII 127 table, 489
– e 602, 395
ASTM
– ISE, 373
– checksum, 159
Calc.? (data alarm)
– connections, 100
– ISE, 372
– delimiters, 155
Calculated QC
– E1381-91 Low Level Protocol, 153
– cobas e flow tests, 62
– escape character, 156
– definition, 62
– field attributes, 167
– sending additional link information, 111
– field types, 167
– sending single QC results, 111
– frames, 154, 159
Calculated QC results
– low-level examples messages, 203
– example HL7 messages, 344
– message transmission phases, 158
Calculated test
– repeat delimiter, 156
– data alarm, c modules, 385
Attributes, ASTM fields, 167
– data alarm, ISE, 373
Auto-dilution factor HL7, 277
Calculation
Automatic rerun
– not possible, c modules, 384
– timing, 141
– not possible, e 602, 394
Automatic Rerun Test Selection, 137
– not possible, ISE, 372
Autorerun enabled, 142
Calibration
– analytical data ISE ASTM, 194, 195
B – analytical data ISE HL7, 272
– calibration ID in calibration results, HL7, 266
Barcodes – calibration ID in patient and QC results, ASTM, 183
– introduction, 37 – calibration ID in patient results, HL7, 259
– order sample ID ASTM, 172 – calibration ID in QC results, HL7, 263
– sample IDs, 51 – calibration type, HL7, 272
– samples without barcodes, 51, 137 – failure data, c modules, 384
Batch mode (result upload message) – failure data, ISE, 373
– example messages HL7, 310 – invalid (data alarm), e 602, 395
– example QC result HL7, 340 – invalid (data alarm), ISE, 373, 384
Batch mode (test selection download message) – method E-module ASTM, 197
– configuring, 100 Calibration error
– definition, 40, 44 – c modules, 406
– diagram, 74 – e 602, 395
Index

– example messages ASTM, 208 Calibration results

– message flow diagram, 84 – ASTM message structure, 165
– messages, 164 – code in ASTM header, 169
Birthdate – examples ASTM, 221
– patient in ASTM, 170 – examples HL7, 347
– patient in HL7, 246 – HL7 message structure, 239
Bottle – photometric calibration alarm ASTM, 193

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Index 507

– status E-module HL7, 274 codes

– value E-module result HL7, 274 – cobas e flow results, 441
– value ISE result HL7, 272 Comment
– value of E-module result, ASTM, 198 – comment type flag ASTM, 177
– values, HL7, 266 – comment type flag HL7, 280
Calibrator Factor – record format in data manager ASTM, 177
– calibration result ASTM, 198 – source of comment, HL7, 280
– calibration result HL7, 274 – source of result comment, ASTM, 187
Calibrator lot number Communication trace file, Control Unit, 144
– ASTM, 197 Compensation error
– HL7, 250 – calculation error, c modules, 385
Cancellation of cobas e flow tests, 61 – calculation error, ISE, 374
CarOvr (data alarm), e 602, 395 – data error, c modules, 385
Carryover – data error, ISE, 374
– Det.S (data alarm), 386 Complex
Cat.5e cable, 126 – ASTM field type, 167
Caution, definition, 14 – data type HL7, 242
Cell blank Conditioning error (calibration alarm), 407
– abnormal (data alarm), 386 Configuration settings chart, 466
Cell.T (data alarm), e 602, 396 Connections
Character – configuring, 100
– data type ASTM, 167 – recommendations, 128
– data type in HL7, 242 – serial, 128
Chart Contact, 6
– European characters in UTF-8, 490 Container
– sequence numbers and sample IDs, 459 – HL7 QPD segment, 283
Charts – HL7 SPM segment, 249
– configuration settings, 466 – sample ASTM order, 173
– modes, configuring, 99 – sample ASTM query, 192
Chemistry Test Calibration Result Detail, 136 Control lot, 485
ClcT.E (data alarm) Control Unit
– c modules, 385 – communication trace file, 144
Clinical chemistry modules, 30 – definition, 29
Clot.E (data alarm) – host communication, 133
– e 602, 396 Conventions used in this publication
C-module, definition, 30 – abbreviations, 11
cobas e 801 module, 57 – symbols, 11
cobas e flow, 115, 120 Copyright, 4
– activating or deactivating host code for generated CR, HL7 framing, 236
subresults, 118 Cup
– activating or deactivating host code for test result, – ASTM order, 173
117 – ASTM query, 192
– assigning host code to generated subresults, 121 – HL7 SPM segment, 249
– assigning host code to test result, 120 – QPD segment HL7, 283
– assigning result type, 115 Curr.E (data alarm)
– configuring omitted result reporting, 114 – e 602, 396
– enabling/disabling subresult upload, 110
– example result messages, 214, 320
– result codes, 441
D
– sending additional link information for calculated QC,
Danger (hazard level), 14
111
Data
– sending single QC results for calculated QC, 111
Index

– calibration analytical data ASTM, 194

– using legacy result status, 112
– collecting all, 136
cobas e flow test (error)
– ISE calibration analytical data HL7, 272
– e 801, 397
Data alarm, 363
cobas e flow test (warning)
– e 602 module, 394
– e 801, 397
– ISE module, 372
cobas® 8100 instrument, 105
Data alarms
cobas® IT firewall, 127

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
508 Index

– ASTM, 188 – factor in order record ASTM, 174

– calibration results ISE ASTM, 194 – factor TCD segment HL7, 277
– cobas e flow tests, 61 – flag ASTM order, 173
– list, 367 – flag in HL7 SPM segment, 249
– photometric calibration results ISE HL7, 272 – OBR segment HL7, 253
data manager – result record ASTM, 180
– definition, 29 Downloads
– version in ASTM, 168 – batch, 44
Data point results – realtime, 44
– example result, ASTM, 211 Duplicate limit
– example result, HL7, 313 – Dup.E calibration alarm, c modules, 409
Databits, 128 – Dup.E calibration alarm, e 602, 409
Date
– data type ASTM, 167
– data type HL7, 242
E
DateTime
e Pack expired flag, ASTM, 197
– calibration result E-module ASTM, 198
e Pack Lot No., 197
– data type ASTM, 167
e 602 module
– data type HL7, 242
– calibration alarm list, 406
– masking message, 289, 291, 293
– data alarm list, 370, 417
– message creation ASTM, 169
– data alarms, 394
– message creation HL7, 243
E.I.U. Level (Essential Information Upload), 135
– order creation ASTM, 175
e801
– pipetting ASTM, 182
– calculated QC results, example HL7 messages, 344
– pipetting HL7, 259
– EP-17A, 53
– pipetting HL7, QC, 262
– module type OBX segment, 260, 267
– result available, HL7, 260
– module type OBX segment, QC, 264
– result available, HL7, QC, 264
– module type, ASTM result record, 183
– results available, HL7, calibration, 267
– sample types, 35
– results, ASTM, 182
EAC^U07
– sample collection ASTM, 175
– MSH segment, 243
– specimen collection HL7, 249
– structure, 240
Decreased sample volume, 419
ECUPL^REAL
Delimiters
– ASTM header, 169
– ASTM, 155
– structure, 165
– HL7, 243
Edited (data alarm)
– location in ASTM message, 168
– c modules, 386
Demographic data, no sample found, 205, 309
– e 602, 397
Detergent
– ISE, 375, 376
– short (data alarm), 386
Edition notice, 3
Deviation of Duplicate Measurement
Elecsys, 30
– calibration result ASTM, 198
Electrolytes, 30
– calibration result HL7, 274
embedded tests, 58
Diagram
E-module, definition, 30
– ASTM transmission phases, 158
Encoding, UTF-8, 32
– batch test selection download, 74
End block, HL7, 236
– cables, 124
EP-17A
– HL7 data framing, 236
– example ASTM, 210
– message flow in batch test selection download, 84
– with e801 and new modules, 53
– message flow in realtime test selection download, 86
Equipment Inventory
– message flow with upload by sample, 85
– see Test availability
– order query, 75
Index

Equipment status
– realtime test selection download, 74
– see Instrument status
– result query, 74
Error
– timeouts, 98
– calibration, c modules, 406
Diff.E (calibration alarm)
– calibration, e 602, 395
– e 602, 408
Error acknowledgment, HL7, 244
Dilution, 36
Escape character
– factor in ASTM, 175

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Index 509

– ASTM, 156 H
– HL7, 243
ESR^U02 Hazard levels, 14
– structure in HL7, 240 Hemolysis, 77
ESU^U01 HL7
– structure in HL7, 239 – network, 100
Ethernet, 127 – recommendations, 31
Expiry date of control lot – version, 244
– calibration results HL7, 250 Host timeout, 98
– upgrading to 1.04, 485 Host Upload Status, 297
Expiry date of control lot, HL7, 248 Hosts
Expiry date of reagent HL7, 279 – communication log file, 123
Extended ASCII in UTF-8, 490 – Control Unit configuration, 133
– no host, 100
F
I
False bottom tubes
– ASTM order record, 173 Icterus, 77
– ASTM query record, 192 ICUPL^REAL
– HL7 QPD segment, 283 – ASTM header, 169
– HL7 SPM segment, 249 – structure, 165
Feedback, 5 ID for host, of instrument. See Analytical Unit ID, 108
Flags IDs
– c8000, ASTM, 183 – See Analytical Unit ID
– c8000, HL7, 260 – See Calibration ID
– c8000, HL7, calibration, 267 – See Operator
– c8000, HL7, QC, 264 – See Patient ID
– calibration alarms HL7, 266 – See Quality control, control ID
– comment type ASTM, 177 Immunology module, 30
– comment type HL7, 280 Inc.T (data alarm)
– data alarm in ASTM, 188 – e 602, 399
– data alarms HL7, 280 Increased sample volume, 419
– dilution ASTM order, 173 Incubator
– dilution HL7 order, 249 – temperature, data alarm, e 602, 399
– DM, ASTM, 183 Inquiry for test selection. See Test selection inquiries
– DM, HL7, 260, 267 INR^U06
– DM, HL7, QC, 264 – structure in HL7, 240
– e Pack expired flag, 197 Instrument
– module type, ASTM, 183 – Analytical Unit ID. See Analytical Unit ID, 183
– module type, HL7, 260 – data alarms HL7, 280
– module type, HL7, QC, 264 – ID for host. See Analytical Unit ID
– qualitative result flag ASTM, 270 – ID in data manager, ASTM, 183
– qualitative result flag HL7, 186 – instrument alarms list, 425
– result abnormal examples ASTM, 210 – number, ASTM, 183
– result abnormal examples HL7, 312 – number, HL7, 260
– result abnormal flags ASTM, 181 – number, HL7 calibration, 267
– result abnormal flags HL7, 258 – number, HL7 QC, 264
– result comment, 187, 188 – operator, ASTM, 182
– sender, host / data manager ASTM, 176 – operator, HL7, 259
Frames – operator, HL7, QC, 263
– ASTM, 154, 159 – sample ID ASTM, 172
Index

FS, HL7 framing, 236 – throttle, 102

Instrument status
– Equipment Status Request message, 240
G – Equipment Status Update message, 239
– Instrument status message, 291
Gender. See Sex
Insufficient reagent
– Reag.S alarm, c 701/c 702, 391

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
510 Index

– Reag.S alarm, e 602, 401 – HL7, 257

Intended use, 11 – HL7, QC, 262
International Standards Organization (ISO), HL7, 236 Measuring cell
INU^U05 – temperature alarm, 396
– structure in HL7, 239 Messages
IP addresses, recommendations, 127 – ASTM low-level, 158
ISE module – batch, 44
– data alarms, 372 – batch communication, 164
ISE module (Ion-Sensitive-Diode), definition, 30 – date and time of ceration, HL7, 243
ISE.E (data alarm), 377 – date and time of creation, ASTM, 169
ISE.N (data alarm), 378 – flag for host / data manager, ASTM, 176
IStd.E (calibration alarm), 410 – Message Control Identifier ASTM, 168
– Message Control Identifier HL7, 243
– Message Control identifier, HL7 acknowledgment,
K 245
– realtime, 44
Kind, of HL7 query, 283
– realtime communication, 164
– structure ASTM, 155
L – structure in HL7, 239
– types, 73
Linearity, data alarm, 388 – types in HL7, 243
Linked kits – upload one-by-one, 102
– cobas e flow tests, 62 Micro cups
Linked tests – ASTM order, 173
– cobas e flow tests, 62 – ASTM query, 192
Lipemia, 77 – HL7 SPM segment, 249
Liquid level detection – QPD segment HL7, 283
– Sample LLD data alarms, e 602, 403 Minimal Layer Protocol (MLP), 236
LIS timeout, 98 Minimal Lower Layer Protocol (MLLP), 236
LIS2-A2, see ASTM Minimum Acceptance Difference
List – calibration result ASTM, 198
– rerun, 419 – calibration result HL7, 274
LoB. See Limit of Blank Missing Values
LoD. See Limit of Detection, 53 – calibration result ASTM, 198
Log files – calibration result HL7, 274
– Control Unit communication, 123, 144 Mixed mode
– host communication, 123 – configuring, 100
Log levels, data manager, 104 – definition, 45
LoQ. See Limit of Quantitation, 53 MIXLOW (data alarm)
Lot – ISE, 378
– calibrator lot number ASTM, 197 Modes
– quality control ASTM, 172 – batch, 44
– quality control HL7, 248 – configuring, 99
– reagent lot number, calibration ASTM, 197 – mixed, 45
– reagent lot number, calibration HL7, 279 – order query HL7, 286
Low level – pass-through, 103
– of signal (data alarm), 403 – rack and position, 104
– rack and position with batch mode, 451
– realtime, 45
M MODULAR PRE-ANALYTICS
– barcodes, 51
Manual Rerun Test Selection, 137
Modules
Index

Masking
– dilution factors ASTM, 175
– ECD segment HL7, 290
– IDs, 108
– EQU segment HL7, 289, 291
– list, 30
– example messages, 349
– module type, ASTM, 183
– message structure, 240
– module type, HL7, 260
– patient results, 290
– module type, HL7, calibration, 267
Measurement units
– module type, HL7, QC, 264

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Index 511

Mono.E (calibration alarm) – MSH segment, 243

– e 602, 410 – structure in HL7, 239
Monotony Over.E (data alarm)
– of curve, 410 – c modules, 390
Monotony of Curve, calibration result ASTM, 198 – e 602, 400
– ISE, 379
N
P
na.LHI (data alarm)
– c modules, 389 Parity, 128
– e 602, 399 Pass-through, 103
– ISE, 379 Patient ID
Name – ASTM, 170
– patient in ASTM, 170 – HL7, 246
– patient in HL7, 246 PCUPL^REAL
New in version, 18 – ASTM header, 169
No host configuration, 100 – structure, 165
Notice, definition, 14 Photometry, module, 30
Number Pipetting time
– data type ASTM, 167 – ASTM, 182
– data type in HL7, 242 – HL7, 259
– See also Samples, sample numbers, Sequence – HL7, QC, 262
numbers Port numbers, recommendations, 127
Position
– sample in ASTM query, 191
O – sample in HL7 query, 282
– sample on rack, ASTM order, 173
OBS.RR (data alarm)
– sample on rack, SAC segment HL7, 251
– e 602, 399
PreClean
OML^O33
– insufficient, 404
– MSH segment, 243
– temperature out of range, 405
– structure in HL7, 241
Pre-dilution, result record ASTM, 180
On-board stability
Prep.E (calibration alarm), ISE, 410
– OBS.RM (data alarm), c 702, 389
Priority
– OBS.RR (data alarm), c modules, 390
– order record ASTM, 175
– OBS.RR (data alarm), e 602, 399
– query record ASTM, 192
Open System Interconnection (OSI), HL7, 236
– query record HL7, 283
Operator
– TQ-1 segment HL7, 254
– data manager, ASTM, 182
Protocols
– data manager, HL7, 259
– ASTM E1381-91 Low Level, 153
– data manager, HL7, QC, 263
– host connection, 100
– instrument, ASTM, 182
– recommendations, 31
– instrument, HL7, 259
– version ASTM, 169
– instrument, HL7, QC, 263
– version HL7, 244
– ISE calibration ASTM, 194
Prozone value
– photometric calibration ASTM, 193
– photometric calibration results ASTM, 193
Order query
– photometric calibration results HL7, 271
– ASTM message structure, 165
– diagram, 75
– example with sequence number ASTM, 228 Q
– example with sequence number HL7, 355
– examples ASTM, 227–228 QCErr (QC alarm), 417
Index

– HL7 message structure, 240 Qualitative and quantitative results

– QPD segement HL7, 286 – HL7 patient, 257
Orders Quality control
– batch, 44 – control ID HL7, 248
– datetime of creation ASTM, 175 – control ID, ASTM, 172
– realtime, 44 – lot ASTM, 172
OUL^R22 – lot HL7, 248

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
512 Index

– name ASTM, 172 – HL7, 279

– name HL7, 248 – upgrading to 1.04, 486
Quantitative results. See Qualitative and quantitative Reagent set
results, 180 – ASTM, 183
Query – HL7, QC, 264
– order query QPD segment HL7, 286 Reagent type HL7, 279
– query type code ASTM, 192 ReagEx (data alarm)
– query type code HL7, 283 – c modules, 391
– result query QPD segment HL7, 284 – e 602, 400
– test selection in ASTM, 165 Realtime mode (result upload message)
– test selection in HL7, 239 – example QC result HL7, 339
– test selection QPD segment HL7, 282 Realtime mode (test selection dowload message)
– See also Order Query, Result Query, Test selection – configuring, 100
inquiries – definition, 40, 44, 45
– diagram, 74
– diagram, message flow, 86
R – example messages ASTM, 207
– example QC result ASTM, 219
Rack and position mode
– messages, 164
– batch test selections, 451
Receiver ID
– configuring data manager, 104
– ASTM, 168
– sample position, 452
– HL7, 243
Rack ID
Reference ranges
– ASTM query, 191
– ASTM, 181
– HL7 SAC segment, 251
– HL7, 258
– QPD segment HL7, 282
– QC, HL7, 262
Rack type
Reflex test, 42
– ASTM query, 190, 191
Repeat delimiter
– QPD segment HL7, order query, 287
– ASTM, 156
– QPD segment HL7, result query, 285
– HL7, 243
– QPD segment HL7, test selection, 283
Repeat limit (data alarm)
– sample lifetime, 50
– c modules, 391
Racks
– e 602, 401
– calibration, 39
– ISE, 380
– ID. See Rack ID
Repeat test, definition, 42
– manual rerun, 39
Request information status code, ASTM, 192
– quality control, 39
Rerun
– routine, 39
– list, 419
– STAT, 39
– query type code ASTM, 192
– type. See Rack type
– query type code HL7, 283
Reag.F (data alarm)
– test, 42
– e 602, 400
– without barcodes, 448
Reag.H (data alarm)
Response times, optimum., 99
– e 602, 400
Result message only for Immunoassay Qualitative
Reag.S (data alarm)
tests, 136
– c 701/c 702, 391
Result query
– e 602, 401
– ASTM message structure, 165
– ISE, 379
– diagram, 74
Reag.T (data alarm)
– example ASTM, 223–??
– e 602, 401
– example with sequence number ASTM, 225
Reagent code HL7, 279
– example with sequence number HL7, 352
Reagent disk
– examples HL7, 350–??
Index

– temperature abnormal, e 602, 401

– HL7 message structure, 240
Reagent expiry date, 279
– QPD segment HL7, 284
Reagent lot number
Results
– ASTM, 197
– abnormal flag examples ASTM, 210
– HL7, 279
– abnormal flag examples HL7, 312
– upgrading to 1.04, 486
– abnormal flags ASTM, 181
Reagent serial number
– abnormal flags HL7, 258

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Index 513

– calibration result code in ASTM header, 169 – c modules, 411

– Calibration. See Calibration results Safety information, 14
– cobas e flow codes, 441 safety information, 15
– code in ASTM header record, QC, 169 Samp.? (data alarm)
– completion time, ASTM, 182 – c modules, 392
– example messages ASTM, 207 Samp.B (data alarm)
– example messages HL7, 310 – e 602, 401
– masking, 290 Samp.C (data alarm)
– message structure ASTM, 165 – c modules, 392
– message structure in HL7, 239 – e 602, 402
– qualitative and quantatitive HL7, 257 – ISE, 380
– query. See Result query Samp.O (data alarm)
– result comment flag, 187, 188 – c modules, 392
– result request code in ASTM header, 169 – e 602, 402
– result upload code in ASTM header, 169 – ISE, 380
– status ASTM, 182 Samp.S (data alarm)
– status E-module calibration result ASTM, 197 – c modules, 392
– status HL7, 259 – e 602, 402
– status, QC, HL7, 262 – ISE, 380
– time available, HL7, 260 Sample
– time available, HL7, calibration, 267 – clot (data alarm), e 602, 402
– time available, HL7, QC, 264 – volume, decreased/increased, 419
– units HL7, 257 Sample clogging (data alarm)
– units, HL7, QC, 262 – e 602, 402
– upload by sample, 141 – ISE, 380
– upload by test, 141 Sample IDs
– validation, 78 – barcodes, 51
– value in HL7, patient results, 257 – instrument sample ID ASTM, 172
– value in HL7, QC results, 262 – lifetime, 48
Revision history, 2 – order ASTM, 172
Routine – QPD segment HL7, order query, 286
– order record ASTM, 175 – QPD segment HL7, result query, 284
– query record ASTM, 192 – QPD segment HL7, test selection, 282
– query record HL7, 283 – query record ASTM, 190, 191
– sample racks, 39 – re-using, 48
RS232c cable, 128 – samples with same ID, 50
Rsp1.E (calibration alarm) – SPM segment HL7, patient results, 248
– ISE, 411 – SPM, patient messages, 248
Rsp2.E (calibration alarm) Sample types, 35
– ISE, 411 Samples
RSREQ – barcodes missing, 137
– ASTM header, 169 – clear sample list in rack and position mode, 453
– HL7, 243 – container in query HL7, 283
– structure in ASTM, 165 – datetime of collection ASTM, 175
– structure in HL7, 240 – expired, 48
RSUPL – identifying by sequence number. See Sequence
– ASTM header, 169 numbers
– structure in ASTM, 165 – IDs. See Sample IDs
RSUPL^BATCH – keep position in rack and position mode, 452
– ASTM header, 169 – lifetime, 48
– structure in ASTM, 165 – not found, message in HL7, 241
RSUPL^REAL – position in HL7 query, 282
Index

– ASTM header, 169 – rack and position batch mode, 451

– structure in ASTM, 165 – rack and position identification, 104
– sample container in ASTM order, 173
– sample container in ASTM query, 192
S – sample numbers, 51
– sample position in ASTM query, 191
S1A.E (calibration alarm)
– upload by sample, 141

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
514 Index

– upload by sample message flow, 85 Single QC

– without barcodes, 51 – cobas e flow tests, 62
Screenshot disclaimer, 4 SLLD.E (data alarm)
SD.E (calibration alarm) – e 602, 403
– c modules, 412 SLLD.N (data alarm)
Selection mode, order query HL7, 286 – e 602, 403
Send conc(entration) of chemistry qualitative tests, Slop.E (calibration alarm)
136 – ISE, 413
Send message for Immunoassay Quantitative tests, Slope
136 – calibration result ASTM, 198
Send query to host, 99 – calibration result HL7, 274
Sender ID, ASTM, 168 Specimen type
Sending application name – ASTM, 176
– configuring, 97 – HL7, 248
– HL7, 243 Standard deviation
Sens.E (calibration alarm) – photometric calibration results ASTM, 193
– c modules, 412 – photometric calibration results HL7, 271
Sequence numbers Standby bottle
– ASTM examples, 462 – ASTM, 183
– configuring on system, 458 – HL7 calibration, 267
– example order query ASTM, 228 – HL7, QC, 264
– example order query HL7, 355 Start block, HL7, 236
– example result ASTM, 210 STAT
– example result query ASTM, 225 – cobas® 8100 instrument, 105
– example result query HL7, 352 – limited STAT handling, 105
– example test selection ASTM, 205 – order record ASTM, 175
– example test selection HL7, 309 – query record ASTM, 192
– HL7 examples, 464 – query record HL7, 283
– instead of barcodes, 37 – sample racks, 39
– order record ASTM, 173 – STAT Test Selection, 137
– QPD segment HL7, 282, 284, 286 Status code, request information, ASTM, 192
– query record ASTM, 190, 191 Std.E (calibration alarm)
– sample IDs compared, 459 – c modules, 415
– SPM, patient messages, 248 – ISE, 414
– warnings and cautions, 460 Stopbits, 128
Serial connections String
– data manager settings, 100 – data type ASTM, 167
– hardware and low-level, 128 – data type in HL7, 242
Serial number, reagent HL7, 279 Submodule
Serum index check (data alarms) – ASTM, 183
– c modules, 387 – HL7, 260
– e 602, 397 – HL7, calibration, 267
– ISE, 376 – HL7, QC, 264
Serum index tests Sys.E (calibration alarm)
– ASTM, 174 – e 602, 416
– request together, 77 SysR.S (data alarm)
Settings, configuration chart, 466 – e 602, 403
Sex SysR.T (data alarm)
– patient in ASTM, 170 – e 602, 404
– patient in HL7, 246 System Error
Short Turn-Around Time. See STAT – calibration result ASTM, 198
Sig.E (calibration alarm) – calibration result HL7, 274
Index

– e 602, 413 System time, 52

Signal
– maximum (calibration alarm), e 602, 412
– minimum (calibration alarm), e 602, 413
T
Signal values
TCP/IP
– calibration E-module ASTM, 198
– connections, 100
– calibration E-module HL7, 274

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
 Index 515

– recommendations, 31 – order creation ASTM, 175

Technical limit – pipetting HL7, 259
– data alarm, e 602, 404 – pipetting, ASTM, 182
Test availability – pipetting, HL7, QC, 262
– Equipment Inventory Request message, 240 – response times, optimum, 99
– Equipment Inventory Update message, 239 – result available, HL7, 260
Test selection – result available, HL7, QC, 264
– batch, 44 – results available, HL7, calibration, 267
– definition, 40 – results, ASTM, 182
– download message structure ASTM, 165 – sample collection ASTM, 175
– download message structure in HL7, 241 – specimen collection HL7, 249
– download message type in ASTM header, 169 – system time, 52
– message timeout, 98 Timeouts
– not found in HL7, 298 – diagram, 98
– realtime, 44 – Host, 98
– upload message structure ASTM, 165 – LIS, 98
– upload message type in ASTM header, 169 – test selection, 98
– upload messge structure in HL7, 241 – test selection, on Control Unit, 136
– See also Test selection inquiries Trace file, on Control Unit, 144
Test Selection Ask in Barcode Read Error, 137 Trademarks, 5
Test Selection Inquire Always, 137 TSDWN
Test selection inquiries – ASTM header, 169
– examples in ASTM, 204 – structure in ASTM, 165
– examples in HL7, 307 TSREQ
– HL7 acknowledgment, 298 – ASTM header, 169
– message structure ASTM, 165 – HL7 MSH segment, 243
– message structure HL7, 239 – structure in ASTM, 165
– Test selection inquiry, Control Unit option, 136 – structure in HL7, 239, 240
– test selection query code in ASTM header, 169 TSUPL
Test Selection Priority Mode, 137 – ASTM header, 169
Test Selection Timeout, 136 – structure in ASTM, 165
Test status
– test availability message, 293
Testcode
U
– E-module calibration results ASTM, 197
Ultrasonic mixer
– masking message HL7, 290
– MIXLOW (data alarm), 389
– OBR segment HL7, 253
– MIXSTP (data alarm), 389
– OBX segment, QC results, HL7, 261
Units of measurement
– order record ASTM, 174, 175
– HL7, 257
– photometric calibration results ASTM, 193
– HL7, E-module calibration, 274
– result record ASTM, 180
– HL7, QC, 262
– SID segment HL7, 279
Universal Service Identifier. See Testcode
– TCD segment HL7, 277
Unmask message, 290
Tests
Uploading messages one-by-one, 102
– reflex, 42
UTF-8, 32
– repeat, 42
– rerun, 42
– testcode. See Testcode V
– type HL7, 279
– upload by test, 141 Version
Third-party software, 17 – data manager ASTM, 168
Throttle instrument, 102 – HL7, 244
Index

Time VT, HL7 framing, 236

– calibration result E-module ASTM, 198
– data type ASTM, 167
– data type HL7, 242
W
– masking message, 289, 291, 293
Warning
– message creation ASTM, 169
– definition, 14
– message creation HL7, 243

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21
516 Index

Warranty, 4
WB.S (data alarm)
– e 602, 404
WB.T (data alarm)
– e 602, 405

X12 of ANSI, 151

Index

Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.08 · Host Interface Manual · Version 21