Cobas 8000 Host Interface Manual (1.06.01)

cobas® 8000 data manager
Host Interface Manual

Version 16
Software version 1.06.01

2
Roche Diagnostics
cobas® 8000 data manager · Software version 1.06.01 · Host Interface Manual · Version 16
3
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.)
y Revision history
Roche Diagnostics
4
Manual version Software version Revision date Main changes

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.
u Data alarms (p. 335)
u STAT masking mode (p. 110)
u Connecting a Generation 8 server (p. 120)
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.
u Forward instrument status mode (HL7 only) (p. 110)
u Data points (p. 456)
u Sample container types (p. 57)
u Upgrading from version 1.04.00 to version 1.05.00 (p. 18)
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.
u Result upload settings (p. 131)
Automatic rerun timing (p. 132)
u Enabling/disabling raw data and data point upload to the host
(p. 114)
u EP17-A and the result abnormal flags (p. 70)
u Supported sample types (p. 51)
16 1.06.01 December 2016 The layout, format, and structure of the manual has been
substantially updated.
u For details of changes to the software and the host interface,
see Differences between version 1.06 and version 1.06.01
(p. 21)
y Revision history
Roche Diagnostics
5
! 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.
u For guidance about changes to the interface, see:

Differences between version 1.06 and version 1.06.01
(p. 21)
Edition notice This document is intended for the users of cobas® 8000
data manager application, Software version 1.06.01.
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.
Roche Diagnostics
6
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-2016 F. Hoffmann-La Roche Ltd. All rights

reserved.
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.
Roche Diagnostics
7
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.
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
8
Roche Diagnostics
Table of contents 9
Table of contents
Publication information 3 Configuration

Contact addresses 7
Table of contents 9
5 Configuring the data manager
Intended use 13
Configuring the data manager 97
Symbols and abbreviations 13
The host connection 99
Safety information classification 15
Configuring the data manager host
Safety information 17
interface options 101
What is new in publication version 16 20
Getting a trace file from the data manager 117
Differences between version 1.06 and
Physical layer specifications 118
version 1.06.01 21
Differences between version 1.05.xx and
6 Configuring the control unit
version 1.06.00 22
Enabling communication with data
Upgrading from version 1.04.00 to version
manager 125
1.05.00 27
Settings for communications with data
Upgrading from version 1.03.xx to version
manager 126
1.04.00 31
Result upload settings 131
Getting a trace file from the control unit 135
Workflow overview
ASTM reference
1 Overview
Purpose and scope 37
7 ASTM protocol (LIS2 - A2)
Who this manual is for 38
Overview of the ASTM protocol 141
Content 39
Communication processing layers 142
ASTM lower layer 143
2 System architecture
ASTM message framing 144
Overview of the system 43
ASTM syntax 145
Overview of modules 45
Message transmission phases 148
LIS communications 46
Checksum calculation / message frame 149
Text encoding 47
8 ASTM text content (LIS2 - A2)
3 Sample processing
List of record levels 153
Supported sample types 51
List of messages used in host
Processing samples 52
communication 154
Barcodes 53
Description of ASTM records 157
Sample tubes and racks 55
Message Header Record 158
Test selection 56
Patient Information Record 160
Sample container types 57
Order Record 161
Repeat, rerun, and reflex tests 59
Comment Record (following Order Record) 166
Batch and realtime processing 61
Result Record 167
Multiple test selection messages 64
Comment Record (following Result Record) 174
Reusing sample IDs and sample lifetimes 65
Query Record (Request Information
Sample ID used with different sample types 67
Record) 176
Identifying samples on the instrument 68
Photometric Calibration Result M(PCR) 180
Returning results to the host 69
ISE Calibration Result Record - M(ICR) 181
E-module (immunology) Calibration Result
4 Communication scenarios and message types
Record - M(ECR) 184
List of communication and message types 75
Message Termination Record 186
Communication scenarios 76
Details of message types 79
Message flow 87
Roche Diagnostics
10 Table of contents
9 ASTM communication examples 12 HL7 acknowledgment handling

Low level trace file 189 Acknowledgment flags in messages from
Test selection inquiry from data manager 190 the data manager 277
Patient result upload messages 192 Acknowledgment flags sent in response to
Raw data and data point messages 199 host messages 282
Quality control uploads 204
Calibration result uploads 207 13 HL7 communication examples
Result request from host and the data Test selection inquiry and download 289
manager result upload 209 Patient result upload messages 293
Order query from the host 213 Qualitative and cut-off index result
messages 305
Raw data and data point result messages 308
HL7 reference Quality control result upload messages 313
Calibration result upload messages 319
10 HL7 protocol Masking messages 322
Overview of HL7 219 Result requests from the host 323
Physical communication 220 Order requests from the host 327
Instrument status and test availability
11 HL7 text content messages 329
HL7 messages 223
HL7 segment description 226
Message Header Segment - MSH 227
Appendices
Message Acknowledgment Segment -
MSA 229 14 Data alarms
Patient Identification Segment - PID 230 List of numerical code data alarms and
Specimen Segment - SPM 231 output characters on the control unit 339
Specimen Container Detail Segment - SAC 235 List of data alarms 342
Observation Request Segment - OBR 236 Data alarms of ISE tests 344
Timing Quantity Segment - TQ1 238 Data alarms of photometric tests 355
Observation Result Segment - OBX (for Data alarms of immunology tests 366
patient results) 239 Alarms for calibrations 378
Observation Result Segment - OBX (for QC Data alarm for QC materials 389
results) 245 Rerun test list 391
Observation Result Segment - OBX (for Alarm priorities 393
calibration results) 249
Measurement of c-module photometric 15 Instrument alarms
Calibration Results 252 Instrument alarms 397
Measurement of ISE Calibration Results 253
Measurement of e-module immunological 16 Result message codes for cobas e flow tests
Calibration Results 255 Result codes 413
Calibration alarm flags 257
Test Code Detail Segment - TCD 258 17 Using MODULAR PRE-ANALYTICS
Substance Identifier Segment - SID 259 Sample IDs and barcodes 417
Comment Segment - NTE 260 Handling query messages without
Query Parameter Segment - QPD (for a test barcodes 418
selection inquiry) 262 Order of messages 419
Query Parameter Segment - QPD (for a Handling batch test selections with strict
Result Query) 264 rack and position 421
Query Parameter Segment - QPD (for an
Order Query) 266 18 Identifying patient samples by sequence number
Response Control Parameter Segment - Identifying samples 427
RCP 268 Identifying patient samples by sequence
Equipment Detail Segment - EQU (from host number 428
to data manager) 269 Important information for using sequence
Equipment Command Segment - ECD 270 numbers 430
Equipment Detail Segment - EQU (from Using sample sequence numbers in ASTM 432
data manager to host) 271 Using sample sequence numbers in HL7 434
Inventory Detail Segment - INV 273 List of configuration settings for barcode
and sequence modes 436
Roche Diagnostics
Table of contents 11
19 Preparing the host communication

General differences in the ASTM protocol 439
Differences in ASTM message definitions 443
Other differences 452
LIS communications 453
Identifying samples by sequence number 454
Traceability information for quality control
and calibration results 455
20 Text encoding tables

ASCII character codes 459
Western European characters in UTF-8 460
Roche Diagnostics
12
Roche Diagnostics
· · ·
13
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
ADC apparent diffusion coefficient
ANSI American National Standards Institute
ASCII American Standard Code for Information
Interchange
y Abbreviations used in the manual
Roche Diagnostics
14
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
Roche Diagnostics
15
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 control
R
REF Reference solution for ISE module
S
SD standard deviation
SID Sample ID
SOP Standard operating procedure
STAT short turn-around time
T
TCP/IP Transmission Control Protocol/Internet
Protocol
TS Test Selection
U
UTF-8 8-bit Unicode Transformation Format
W
WAM Work Area Manager
X
XML Extensible Markup Language
XSL Extensible Stylesheet Language
XSLT Extensible Stylesheet Language
Transformation
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.
Roche Diagnostics
16
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
17
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
18
! 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
19
! 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.
Roche Diagnostics
20
What is new in publication version 16
New layout and structure Resulting from customer feedback, we have updated the
layout and the structure of this publication to help you
find information easier and perform tasks quicker.
u For guidance about changes to the interface, see:
Differences between version 1.06 and version 1.06.01
(p. 21)
Roche Diagnostics
21
Differences between version 1.06 and

version 1.06.01
This section gives an overview of all major host interface-
relevant differences between version 1.06 and version
1.06.01 of the data manager.
Custom host code assignment for formulas The Use custom host codes for formulas and
and variables variables check box has been added to Workplaces
> cobas 8000 data manager Service > Service-
related configuration > Interface options. With the
addition of this check box, it is now possible to
independently enable or disable the assignment of
custom host codes for formulas and variables, and the
assignment of host codes by reported lab unit. (In
previous versions, both features were enabled by
selecting the Assign host code by reported lab unit
check box.)
u Assignment of host codes to cobas e flow test results
(p. 112)
Control codes in QC result messages QC result messages now contain an additional control
code, to uniquely identify the quality control material. The
code is sent in segment SPM-2.5 (HL7) and field O-3
(ASTM).
u SPM in test selections, patient results and quality
control results (p. 231)
u Order Record (p. 161)
Sample lifetime The handling of sample lifetime (i.e. sample ID reuse) has
changed.
u Reusing sample IDs and sample lifetimes (p. 65)
New quality control rules New quality control rules have been implemented for
calculated QC and asymmetric QC. Data alarms 40 and 41
are no longer sent in asymmetric and calculated QC
results.
u List of numerical code data alarms and output
characters on the control unit (p. 339)
Result suppression for results outside of the The Result suppression for results outside of
technical limit technical limit check box has been added to
Workplaces > cobas 8000 data manager System
Configuration > System configuration > Result
suppression [tab]. When enabled, the data manager
uploads results that are outside the technical limit to the
host as 7 spaces.
u Result suppression for results outside the technical
limit (p. 71)
Roche Diagnostics
22 Differences between version 1.05.xx and version 1.06.00
Differences between version 1.05.xx and

version 1.06.00
This section gives an overview of the differences between
version 1.05 and 1.05.01 and version 1.06 of the data
manager.
• The cobas e 801 module and the cobas e flow test
concept is supported.
- Additional data alarms for cobas e flow tests are
sent in NTE-3 (HL7) and C-4.1 (ASTM).
- Forward Instrument Status mode now also
provides status information for cobas e flow tests.
- Host codes can be assigned to formulas, variables,
and measurement units of embedded tests in
cobas e flow tests.
• Results can be uploaded By cluster as well as By
test and By sample. A No result upload option is
also available. Result upload settings are displayed on
the data manager.
• The upload of raw data and data point values in result
messages from the data manager to the host can be
manually enabled and disabled.
• Test results can only be validated against the Higher
Uncertainty limit. Accordingly, the use of the following
EP-17A flags has been discontinued:
- LoB (Limit of Blank)
- LoD (Limit of Detection)
- LoQ (Limit of Quantitation)
The data manager software now handles only the
following EP17-A flags:
- HU (Higher Uncertainty)
- eFlow.W (generic cobas e flow test warning)
• Three new sample types are added to the sample list:
- Hemolysate
- Amniotic fluid
- Processed stool
u Assignment of host codes to cobas e flow test results
(p. 112)
u Result upload settings (p. 131)
u Automatic rerun timing (p. 132)
u Enabling/disabling raw data and data point upload to
the host (p. 114)
u EP17-A and the result abnormal flags (p. 70)
u Supported sample types (p. 51)
Roche Diagnostics
23
Changes to ASTM messages The behavior of the following ASTM fields has changed.
Field Description Version 1.05.xx Version 1.06

O-4.5 Rack type The codes S8 , S9 , and SA are The codes S8 , S9 , and SA are used and supported
supported but not used. (only by the e 801 module).
O-5.5 Dilution Only the following values are The following values are additionally permitted:
permitted: o For a regular e 801 module test: 1 , 1.1 , 2 , 5 , 10 ,
o For an ISE module, the only value 20 , 30 , 50 , 100 , 400 , 900 , 27000
that can be used is: 1 o For an e 801 cobas e flow test: 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-16 Specimen type The codes 8 , 9 , and A are The codes 8 , 9 , and A are used and supported (only by
supported but not used. the e 801 module).
R-3 Test request Has the following structure: If the result corresponds to a subresult or embedded
^^^Testcode/Dilution/Pre- test result of a cobas e flow test, and the system is
dilution configured to report subresults to the host, the test
request has the following structure:
^^^Testcode/Dilution/Pre-dilution^^Sub
resultCode/Dilution
Note that the sixth component is separated into two
parts with a forward-slash separator / . In this case,
segment 3.4 also takes the main result of the
cobas e flow test.
R-3.4 Dilution Only the following values are The following values are additionally permitted:
permitted: o For a regular e 801 module test: 1 , 1.1 , 2 , 5 , 10 ,
o For an ISE module, the only value 20 , 30 , 50 , 100 , 400 , 900 , 27000
that can be used is: 1 o For an e 801 cobas e flow test: 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 No value
R-4.1 Reportable This field can contain the following For a cobas e flow test, this field can additionally
result codes: contain a numeric code.
o For c-module and ISE module: an u For a list of cobas e flow test codes, see Result
integer code from -2 to 3
message codes for cobas e flow tests (p. 411)
inclusive.
o For e-module: an integer code -1
(non-reactive), 0 (border line), 1
(reactive).
R-4.2 Additional o For a quantitative result, this field For a main result of a quantitative or qualitative
result values contains a quantitative value. cobas e flow test, this field is empty.
o For e-module qualitative results, For a main result of an assignment/formula, this field is
this field contains COI . empty.
R-5 Units o This field contains the units in For a quantitative cobas e flow test, this field shows
which result is measured. (for units of measure.
example, mmol/L, etc.)
o For a data point result, this shows
count or COUNT .
y Changes to ASTM messages in data manager 1.06
Roche Diagnostics

R-7 Result The following values are permitted: The following values are permitted:
abnormal flag o HH o HH
o H o H
o N o N
o L o L
o LL o LL
o A o A
o AA o AA
o LoB o HU
o LoD o eFlow.W
o LoQ
R-14.1 Module type The following values are permitted: The following value is additionally permitted: e801
o c502
o c701
o e602
o ISE
o c702
o DM
o c8000
C-4.1 Flag Permitted values: a number showing The following values are additionally permitted (they are
error or alarm status, or 0 (signifying generated only by the main test of a cobas e flow test:
no error) o eFlow.E
o CalcError
Q-3.2 (in Rack type The codes S8 , S9 , and SA are The codes S8 , S9 , and SA are used and supported
result or supported but not used. (only by the e 801 module).
order queries
from host to
data
manager)
Q-3.8 (in test Rack type The codes S8 , S9 , and SA are The codes S8 , S9 , and SA are used and supported
selection supported but not used. (only by the e 801 module).
queries from
data manager
to host)
Changes to HL7 messages The behavior of the following HL7 fields has changed, or
the fields have been newly implemented.

SPM-4 Specimen type The codes S8 , S9 , and SA are The codes S8 , S9 , and SA are used and supported (only
supported but not used. by the e 801 module).
OBR-4.2 Dilution Only the following values are The following values are additionally permitted:
permitted: o For a regular e 801 module test: 1 , 1.1 , 2 , 5 , 10 , 20 ,
o For an ISE module, the only 30 , 50 , 100 , 400 , 900 , 27000
value that can be used is: 1 o For an e 801 cobas e flow test: 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 No value
OBX-3 (for Test code This field contains the test code. In the case of a cobas e flow test, this field can contain
patient the name of an internally-calculated formula.
results)
y Changes to HL7 messages in data manager 1.06
Roche Diagnostics
25

OBX-3 (for Test code This field contains the test code. In the case of e-module calibration results with raw data,
calibration this field can contain the sub-component RDSX , where X
results) is an incremental value signifying the repetition of the raw
data node.
OBX-5 (for Result value This field contains the reportable For a cobas e flow test, this field can contain a numeric
patient result value and additional result code.
results) values. u For cobas e flow test codes, see Result message codes
for cobas e flow tests (p. 411)
For missing qualitative results from c- and e-modules, 7
spaces (ASCII 32 / 0x20) are sent in both sub-components
of this field.
OBX-7 (for Reference This field takes the following Asymmetric control results are additionally supported.
QC results) ranges format: These may be sent with lower and upper range limits, for
RangeDefinition^TypeOf example:
Range 0.84^TARGET~0.14^LOWER~0.14ÛPPER
These occur as a repeated field, Asymmetric control results may also be sent without a
for example: target value, for example:
120^TARGET~25^SD 0.14^LOWER~0.14ÛPPER
When either the target value or
the standard deviation is null, it
is not included in the result
message.
OBX-7.2 (for Type of range The following values are The following values are additionally permitted (only used
QC results) permitted: in asymmetric control results):
o TARGET o LOWER
o SD o UPPER
OBX-8 Result abnormal The following values are The following values are permitted:
flag permitted: o HH
o HH o H
o H o N
o N o L
o L o LL
o LL o A
o A o AA
o AA o HU
o LoB o eFlow.W
o LoD
o LoQ
OBX-18.1 Module type The following values are The following value is additionally permitted: e801
permitted:
o c502
o c701
o e602
o ISE
o c702
o DM
o c8000
Roche Diagnostics

TCD-1 Universal This field contains the test code In the case of a cobas e flow test, this field can contain
Service Identifier or application code. the name of an internally-calculated formula.
NTE-3 Comment This field can contain user This field can additionally contain two data alarms for the
comments, in the following main result of a cobas e flow test:
format: o eFlow.E^Standard alarm for e801
TextÛser^Date workflow tests
As well as instrument o CalcError (EP17-A error alarm for
comments, in the following cobas e flow tests)
format:
flag^desc
QPD-10 Rack type The codes S8 , S9 , and SA are The codes S8 , S9 , and SA are used and supported (only
supported but not used. by the e 801 module).
Roche Diagnostics
27
Upgrading from version 1.04.00 to version

1.05.00
This section gives an overview of the differences between
version 1.04 and version 1.05 of the data manager.
• The data manager sends instrument status and test
availability information to the host. (HL7 only.)
• Four new message types for instrument status and
test availability information are supported (HL7 only):
- Instrument status: Equipment Status Update (ESU)
- Test availability: Inventory Status (INU)
- Instrument status query: Equipment Status Update
Request (ESR)
- Test availability query: Inventory Status Update
Request (INR)
• False bottom and non-standard tubes are supported
in both HL7 and ASTM.
• Raw data points in patient result messages are
supported in both HL7 and ASTM. Accordingly,
multiple OBX segments per OBR segment can be sent
in a result report message.
• Orders which contain invalid (unknown) test codes
are supported in both HL7 and ASTM. Such orders are
now handled as follows:
- 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.
- If an order contains only invalid test codes, the
data manager rejects the order.
- The rejection of invalid test codes and/or orders is
shown in the information window.
• The way in which data manager handles sample
container type values received from the instrument
and the host has changed in both HL7 and ASTM.
• Empty container type values no longer default to
standard cup type in both HL7 and ASTM.
u For an example ASTM data point message, see e 602
result with data point values (p. 199)
u For an example HL7 data point message, see e 602
result message with data point values (p. 308)
u Messages sent only by the data manager (p. 223)
u Sample container types (p. 57)
Roche Diagnostics
28 Upgrading from version 1.04.00 to version 1.05.00
Changes to ASTM messages The behavior of the following ASTM fields has changed.
Field Description Version 1.04 Version 1.05

O-4.6 Container type Only the following values are The following values are additionally supported in test
supported: selections, patient results and quality control results:
o SC Standard cup o NST0 Non-standard tube
o MC Micro cup o FBT1 False bottom tube 1
An empty value defaults to standard o FBT2 False bottom tube 2
cup type. (If the host sends no o FBT3 False bottom tube 3
container type value, then data o <Empty> Unknown cup type
manager sends SC to the control These new values provide support for false bottom and
unit.) non-standard tubes.
Empty values no longer default to standard cup type. (If
the host sends no container type value, then data manager
sends no value to the control unit.)
O-5 Test code The data manager rejects an order o If an order contains both valid and invalid test codes,
if it contains any invalid (unknown) the data manager accepts the order but logs an error
test codes in this field. 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
R-4 Measurement Quantitative and qualitative results Data point results are additionally supported.
value only. Up to 200 data point values can be sent in field R-4.2,
separated by backslashes (\).
R-5 Units of Units in which the result is For data point results, this field contains count or
measurement measured. (For example, mmol/L, COUNT .
etc.)
R-14.5 Calibration ID Number data type. String data type. For data point results, this field contains
one of the following codes:
o EFS
o EFV
o EFC
o PMT
Q-3.9 Container type Only the following values are The following values are additionally supported in test
An empty value defaults to standard o FBT2 False bottom tube 2
cup type. (If the host sends no o FBT3 False bottom tube 3
container type value, then data o <Empty> Unknown cup type
manager sends SC to the control These new values provide support for false bottom and
unit.) non-standard tubes.
Empty values no longer default to standard cup type. (If
the host sends no container type value, then data manager
Changes to HL7 messages The behavior of the following HL7 fields has changed, or
the fields have been newly implemented.
Roche Diagnostics
29

MSH-9 Message type The following values are The following values are additionally supported:
supported: o ESUÛ01ÊSU_U01
o TSREQ o ESRÛ02ÊSR_U02
o RSREQ o INUÛ05ÎNU_U05
o OMLÔ33 o INRÛ06ÎNR_U06
o OUL^R22 These new values provide support for instrument status
o EACÛ07 and test availability messages.
o OUL^R22^PCUPL
o OUL^R22ÎCUPL
o OUL^R22ÊCUPL
o ACK
o OUL^R22^REAL
o OUL^R22^BATCH
o OUL^R22^BATCH
SPM-27 Container type Only the following values are The following values are additionally supported in test
An empty value defaults to o FBT2 False bottom tube 2
standard cup type. (If the host o FBT3 False bottom tube 3
sends no container type value, o <Empty> Unknown cup type
then data manager sends SC to These new values provide support for false bottom and
the control unit.) non-standard tubes.
Empty values no longer default to standard cup type. (If the
host sends no container type value, then data manager
OBR-4.1 Test code The data manager rejects an o If an order contains both valid and invalid test codes,
order if it contains any invalid the data manager accepts the order but logs an error
(unknown) test codes in this for each invalid test code.
field. o If an order contains only invalid test codes, the data
o The rejection of invalid test codes and/or orders is
OBX-5 Result value Quantitative and qualitative Data point results are additionally supported.
results only. Up to 200 data point values can be sent, separated by
ampersands (&).
OBX-6 Units of Units in which the result is For data point results, this field contains count or
measurement measured. (For example, COUNT .
mmol/L, etc.)
OBX-17 Calibration ID Number data type. String data type. For data point results, this field contains
one of the following codes:
o EFS
o EFV
o EFC
o PMT
QPD-11 Sample Only the following values are The following values are additionally supported in test
container type supported: selections, patient results and quality control results:
An empty value defaults to o FBT2 False bottom tube 2
standard cup type. (If the host o FBT3 False bottom tube 3
sends no container type value, o <Empty> Unknown cup type
then data manager sends SC to These new values provide support for false bottom and
the control unit.) non-standard tubes.
Empty values no longer default to standard cup type. (If the
host sends no container type value, then data manager
Roche Diagnostics
30 Upgrading from version 1.04.00 to version 1.05.00

EQU-3 Instrument Not supported. This field is used to send instrument status information to
status the host.
INV-1 Test code Not supported. The INV (Inventory Detail) segment is used to send test
INV-2 Test status availability information to the host.
Roche Diagnostics
31
Upgrading from version 1.03.xx to version

1.04.00
This section lists the differences to be careful of, when
upgrading from version 1.03.00 or 1.03.01 to version
1.04.00 of the data manager.
• The usage of data alarms, numbers 23, 26, 55, 59, and
60 have been slightly changed.
• STAT masking mode is available to assist certain busy
systems with many STAT samples.
• The cobas® 8000 data manager version 1.04.00 uses
a 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.
u STAT masking mode (p. 110)
u Connecting a Generation 8 server (p. 120)
q There is no difference in the values of the HL7 or

ASTM fields in the host interface in version 1.04.00,
compared to version 1.03.00 or 1.03.01.
Version 1.03.00 was the previous mandatory upgrade of

the cobas® 8000 data manager software. Version 1.03.01
was a recommended upgrade.
Roche Diagnostics
32 Upgrading from version 1.03.xx to version 1.04.00
Roche Diagnostics
Workflow overview
1 Overview .................................................................................................................... 35
2 System architecture............................................................................................... 41
3 Sample processing ................................................................................................ 49
4 Communication scenarios and message types........................................... 73
Roche Diagnostics
35
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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Who this manual is for. . . . . . . . . . . . . . . . . . . . . . . . . . 38
Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1 Overview
Roche Diagnostics
36
Table of contents
1 Overview
Roche Diagnostics
Overview 37
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
38 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
Overview 39
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
40
1 Overview Content
Roche Diagnostics
41
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 . . . . . . . . . . . . . . . . . . . . . . . . . 43
Overview of modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
LIS communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Text encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Roche Diagnostics
42
Table of contents
Roche Diagnostics
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.
Roche Diagnostics
44 Overview of the system
J
A B C D
ASTM/HL7
K
E
F G H I
A Host (LIS, WAM etc.) E cobas® 8000 control unit I cobas® 8000 analytical modules
B cobas® 8000 data manager F cobas® 8000 analytical modules J cobas® 8000 modular analyzer
series
C cobas® link G cobas® 8000 analytical modules K cobas® 8000 instrument
D Roche Diagnostics e-services H cobas® 8000 analytical modules
Roche Diagnostics
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 or Elecsys, and e 801 perform

immunological tests.
Roche Diagnostics
46 LIS communications
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 (p. 99).
u For details of the connections, see Physical layer
specifications (p. 118).
u For details of the HL7 protocol used, see HL7 protocol
(p. 217) and HL7 text content (p. 221).
u For details of the ASTM protocol used, see ASTM
protocol (LIS2 - A2) (p. 139) and ASTM text content
(LIS2 - A2) (p. 151).
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.
Roche Diagnostics
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
(p. 460).
Roche Diagnostics
48
2 System architecture Text encoding
Roche Diagnostics
49
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 . . . . . . . . . . . . . . . . . . . . . . . . 51
Processing samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Barcodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Sample tubes and racks . . . . . . . . . . . . . . . . . . . . . . . . 55
Test selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Sample container types . . . . . . . . . . . . . . . . . . . . . . . . . 57
Repeat, rerun, and reflex tests . . . . . . . . . . . . . . . . . . . 59
Batch and realtime processing . . . . . . . . . . . . . . . . . . . 61
Batch and realtime and the data manager . . . . . . 61
Batch and realtime modes. . . . . . . . . . . . . . . . . . . . 61
Configuring the data manager for the host
modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3 Sample processing
Multiple test selection messages . . . . . . . . . . . . . . . . . 64
Reusing sample IDs and sample lifetimes . . . . . . . . . 65
Sample ID used with different sample types . . . . . . . 67
Identifying samples on the instrument . . . . . . . . . . . . 68
Returning results to the host . . . . . . . . . . . . . . . . . . . . 69
Passing results automatically to the host . . . . . . . 69
System time and result handling . . . . . . . . . . . . . . 69
EP17-A and the result abnormal flags . . . . . . . . . . 70
Result suppression for results outside the
technical limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Roche Diagnostics
50
Table of contents
3 Sample processing
Roche Diagnostics
Sample processing 51
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
52 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
(p. 57)
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
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 as a unique
identifier for the sample, called the sample ID (SID).
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
(p. 425). 3 Sample processing
Roche Diagnostics
54 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 (p. 415).
u To configure the cobas® 8000 modular analyzer
series instrument to process samples coming from a
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 (p. 128).
3 Sample processing
Roche Diagnostics
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. 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
56 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 programmed 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 programmed Test Selection
on data manager by the operator. The test results can
be uploaded to the host.
As users can reconfigure the cobas® 8000 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 (p. 49).
3 Sample processing
Roche Diagnostics
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.
Roche Diagnostics
58 Sample container types
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.
The data manager ignores values received in test

selection information messages and result report
messages from the control unit, unless they correspond
with the values received from the host.
3 Sample processing
Roche Diagnostics
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
60 Repeat, rerun, and reflex tests
cobas e flow tests Rerun and reflex can only be ordered for
cobas e flow tests via the LIS. However, a
cobas e flow test can be assigned as a reflex test of a
regular test.
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 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
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
62 Batch and realtime processing
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 (p. 104).
Roche Diagnostics
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 (p. 128).
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 (p. 87).
3 Sample processing
Roche Diagnostics
64 Multiple test selection messages
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
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
66 Reusing sample IDs and sample lifetimes
! 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 (p. 83).
3 Sample processing
Roche Diagnostics
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
This sample, with rack type S1:
MSH|^~\&|c8k||host||20121020091052||TSREQ|15161||2.5||||ER||UNICODE UTF-8|
QPD|TSREQ|15161|321070||50094|2||||S1|SC|R1|R|
RCP|I|1|R|
is treated as a different sample from this one, with rack

type S2:
MSH|^~\&|c8k||host||20121020091052||TSREQ|15161||2.5||||ER||UNICODE UTF-8|
QPD|TSREQ|15161|321070||50650|2||||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.
3 Sample processing
Roche Diagnostics
68 Identifying samples on the instrument
Identifying samples on the instrument

Samples are placed on the loader, either in 2 trays each
with up to 15 5-position racks, or inserted into the STAT
port. Each rack is passed on to the input buffer, which
consists of two trays. The trays feed racks onto the system
sequentially until they are empty.
Barcodes and sample IDs By default, the cobas® 8000 modular analyzer series
instrument reads the barcodes on the sample tubes, and
uses the number on the barcode as a sample ID. The
sample ID uniquely identifies the sample in the databases
of the control unit and the data manager, and uniquely
identifies the sample in messages to and from the host.
Samples missing a barcode If the sample tube’s barcode is missing or unreadable, the
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
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 (p. 52).
u For a description of how to implement a connection to
a MODULAR PRE-ANALYTICS, see Using MODULAR
PRE-ANALYTICS (p. 415).
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 (p. 425).
Roche Diagnostics
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-though 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 (p. 108).
System time and result handling

The data manager uploads results to the host as soon as
they arrive from the instrument, and have passed any
technical validation.
3 Sample processing
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 (p. 131).
Roche Diagnostics
70 Returning results to the host
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. The e 801 module and other newer
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
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 (p. 167).
u For details of the flags passed to the host in HL7, see
Observation Result Segment - OBX (for patient results)
(p. 239).
Result suppression for results outside the technical limit

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.
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 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.
Result suppression is disabled by default.
3 Sample processing
Roche Diagnostics
72
3 Sample processing Returning results to the host
Roche Diagnostics
73
Table of contents
Communication scenarios and

message types 4
This chapter shows the message flow between the

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

In this chapter 4
List of communication and message types. . . . . . . . . 75
Communication scenarios . . . . . . . . . . . . . . . . . . . . . . . 76
Realtime test selection download. . . . . . . . . . . . . . 76
Batch test selection download . . . . . . . . . . . . . . . . 76
Result query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Order query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Instrument status and test availability messages . 77
Other message scenarios . . . . . . . . . . . . . . . . . . . . 77
Details of message types. . . . . . . . . . . . . . . . . . . . . . . . 79
Query message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Sending test selections . . . . . . . . . . . . . . . . . . . . . . 79
Sending patient test results. . . . . . . . . . . . . . . . . . . 80
Raw data and data points in patient test results . 80
Result query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Order query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Order and result queries with limited sample
lifetime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
QC results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Calculated QC results. . . . . . . . . . . . . . . . . . . . . . . . 85
Calibration data results . . . . . . . . . . . . . . . . . . . . . . 85
Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Instrument status and test availability . . . . . . . . . . 86
Message flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Message flow batch download from host . . . . . . . 87
Message flow for TS Inquiry from instrument /
data manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Roche Diagnostics
74
Table of contents
Message flow for batch download, upload by

sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Roche Diagnostics
Communication scenarios and message types 75
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

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
76 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

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

data The host can send a batch test selection download at any
LIS manager time. After receiving the test selection download, the data
manager uploads the relevant patient results once they
Test selection batch download
are available and released.
Patient results
Result query
data The host can send a result query at any time. The data
LIS manager manager replies with the relevant patient results, if any. If
the sample ID does not exist, or if there are no results, the
Result query
data manager does not reply.
Patient results
Roche Diagnostics
Order query
data The host can send an order query, the data manager
LIS manager replies with the relevant test selection describing the
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

data The data manager can send instrument status and test
LIS manager availability information to the host. (Only supported in
HL7.)
Instrument status query

If forward instrument status mode is enabled, the data
manager will automatically forward this information to the
Instrument status
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.
data If forward instrument status mode is disabled, the data

LIS manager manager will only send this information in response to
requests from the host.
Test availability query
u For more information, see Forward instrument status
mode (HL7 only) (p. 110)
Test availability
Other message scenarios

The host can send a masking or unmasking request at
data any time, independent of other communication. (Only
LIS manager supported in HL7.)
Mask/unmask request
Roche Diagnostics
78 Communication scenarios
The data manager can send quality control or calibration

data results independently of other messages.
LIS manager
Quality control results
data
LIS manager
Calibration results
Roche Diagnostics
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

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.
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.
u To see how to set these options, see Test selection

inquiry message settings (p. 104).
Roche Diagnostics
80 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 (p. 108).
u For details of setting a test to automatic validation, see
the cobas® 8000 data manager Operator’s Manual.
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 (p. 114)
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
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)(a)
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 / S2
expired / S1(b)
current / S2
expired / S1(b)

expired / S2(b)
y Result query response for a specific sample ID
(a) Rack type is mandatory if sample lifetime is set. Even if not set, it is recommended to include it.
(b) “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
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.
r The results for expired samples might be confused
with results for current samples, or with previous
results for samples that are now expired. Avoid this,
and identify samples and results by timestamp, as well
as by ID.
u For details of inactive samples, sample ID lifetimes

and expired sample IDs, see Reusing sample IDs and
sample lifetimes (p. 65).
u For details of using result queries in systems where
sample ID lifetimes are set, see Order and result
queries with limited sample lifetime (p. 83).
Roche Diagnostics
Order query
The host can send an order query message to the
cobas® 8000 data manager to inquire for all the test
selections, with or without results, that include a given
sample. The cobas® 8000 data manager replies with a
Send test selection message.
The host may ask for all test selections for a sample, or
only for open orders with no results for that sample. The
data manager sends only the orders that are available to
it, at the status they have at the data manager (as
opposed to the status or availability at the control unit.)
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.
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)(a)
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
current / S1 current / S1 current / S2 empty test selection / (no rack
current / S2 type)
current / S2 type)
expired / S1(b)
current / S2 type)
expired / S1(b)
expired / S2(b)
y Order query response for a specific sample ID
(a) Rack type is mandatory if sample lifetime is set. Even if not set, it is recommended to include it.
(b) “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
! WARNING
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
(p. 65).
u For details of using sample IDs with limited lifetimes
with order queries, see Order and result queries with

limited sample lifetime (p. 83).
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
84
4 Communication scenarios and message types Details of message types
Roche Diagnostics
A Host: HIS, LIS H Sample: ID 123, type S1, created with timestamp day 2.
®
B cobas 8000 data manager I Results uploaded for sample ID 123.
C New sample ID 123, type S1: test selection download J Sample 123 expires
D Sample: ID 123, type S1, created with timestamp day 1. K New sample ID 123, type S1: test selection download.
E Results uploaded for sample ID 123. L Sample: ID 123, type S1, created with timestamp day 3.
F Sample 123 expires M Result query / order query downloaded.
G New sample ID 123, type S1: test selection download. N Result upload / test selection upload for current sample.
(Results uploaded only if available.)
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 Result
upload settings (p. 98)
u For more information, see Pass-through mode (p. 108).
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.
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.
Roche Diagnostics
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.
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.

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.

Roche Diagnostics
Message flow
Message flow batch download from host

The following diagram shows an example of message
flow (from top down) for ASTM communications for a
batch order of three test applications in the rerun mode.
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)

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

Measure(Sample
ID, Test A)
Result(Test A)
Technical Validation( )
Result(Test A)
Measure(Sample
Result(Test B) ID, Test B)
Result(Test B)
Measure(Sample
Result(Test C)
ID, Test C)
Result(Test C)
No further Test Selections( )
Unload Sample( )
w ASTM messages for a batch order of three samples
Roche Diagnostics
88 Message flow
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.
Message flow for TS Inquiry from instrument / data

manager
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

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

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

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

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
Roche Diagnostics
90 Message flow
tests were required.
Message flow for batch download, upload by sample

flow (from top down) when:
• the host sends a batch order of three tests
• the control unit is in the rerun mode
• the control unit uploads results by sample
• the data manager option Send query to host is off
• the test is not an HPE test.
Roche Diagnostics

Test Selections(Sample ID,

Load Sample( )
Scan Sample( )

Measure(Sample
ID, Test A)

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

ID, Test C)
Result(Test A, Test B, Test C)
No further Test Selections( )
Unload Sample( )
w Batch download, with upload by sample
Roche Diagnostics
92
4 Communication scenarios and message types Message flow
Roche Diagnostics
Configuration
5 Configuring the data manager .......................................................................... 95

6 Configuring the control unit.............................................................................123
Roche Diagnostics
95
Table of contents

Setting up the data manager for host
communications
This chapter describes how to set up data manager to

enable host communications.
In this chapter 5
Configuring the data manager . . . . . . . . . . . . . . . . . . . 97
The host connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Starting and stopping the host connection. . . . . . 99

Using the data manager without a host
connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Configuring the data manager host interface options 101
Identifying the data manager application to the
host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Test selection inquiry timeout settings . . . . . . . . . 102
Test selection inquiry message settings . . . . . . . . 104
Connection protocol settings . . . . . . . . . . . . . . . . . 104
HL7 acknowledgment handling settings. . . . . . . . 106
Throttle instrument settings . . . . . . . . . . . . . . . . . . 107
Pass-through mode . . . . . . . . . . . . . . . . . . . . . . . . . 108
Logging level settings . . . . . . . . . . . . . . . . . . . . . . . 109
Rack and position mode . . . . . . . . . . . . . . . . . . . . . 109
STAT masking mode. . . . . . . . . . . . . . . . . . . . . . . . . 110
Forward instrument status mode (HL7 only) . . . . 110
Configuring result upload settings. . . . . . . . . . . . . 112
Enabling/disabling cobas e flow test subresult
upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Assignment of host codes to cobas e flow test
results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Enabling/disabling raw data and data point
upload to the host . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Roche Diagnostics
96
Table of contents
Identifier of the analytical unit sent to host . . . . . 115

Getting a trace file from the data manager. . . . . . . . . 117
Physical layer specifications . . . . . . . . . . . . . . . . . . . . . 118
Connecting a Generation 5 server . . . . . . . . . . . . . 118
Network connection. . . . . . . . . . . . . . . . . . . . . . . . . 120
Serial connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Roche Diagnostics
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.

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
u Related topics
• For details of how the cables and network must be
configured, see Text encoding (p. 47) and Physical
layer specifications (p. 118).
• For details of the interface options for the data
manager, see Configuring the data manager host
interface options (p. 101).
• For details of how the control unit must be configured,
see Configuring the control unit (p. 123).
• For details of starting and stopping host
communications, see Starting and stopping the host
connection (p. 99).
Roche Diagnostics
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

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
100 The host connection
r To stop a host connection
1 Navigate to Workplaces > cobas 8000 data

> Interface options,
2 Select the No host option, and then choose the OK

button.
f The data manager closes any host connection.
q When the host connection is set to No host, the

data manager waits for 16 seconds before replying to
any inquiries from the control unit.
Using the data manager without a host connection

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

interface options
w The Interface options tab

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
102 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 ~ 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]
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
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
A B C
D E
A cobas® 8000 control unit D Timeout on control unit in seconds.

Must be > (E + 2) secs.
Recommended is E + 8 secs.
Default 18 secs.
B cobas® 8000 data manager E Timeout on data manager in seconds.
C Host (LIS / WAM) Must be < (D - 2) secs.
Recommended is D - 8 secs.
Default 16 secs.
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. However, 8 seconds

shorter is recommended. This gives enough time for a
message to make the round-trip from the control unit to
the host and back.
! 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
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.
Roche Diagnostics
Test selection inquiry message settings

This section describes how you can configure the test
selection inquiry messages. This is configurable in
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.
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,
see Batch and realtime processing (p. 61).
Connection protocol settings

These options set the communication protocol used in
messages between the host and data manager, and start
and stop communications.
Roche Diagnostics
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) (p. 139).
u For details of the data fields data manager supports
over the ASTM protocol, see ASTM text content (LIS2
- A2) (p. 151).
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) (p. 139).
over the ASTM protocol, see ASTM text content (LIS2
- A2) (p. 151).
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 (p. 217).
over the HL7 protocol, see HL7 text content (p. 221).
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.
Roche Diagnostics
Changing the communication protocol Consult your Authorized Roche Diagnostics service
personnel before changing the communication protocol.
! CAUTION
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
u For details of configuring the control unit for
communications, see Configuring the control unit
(p. 123).
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
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.
Roche Diagnostics
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
(p. 275).
Throttle instrument settings

In production environments, navigate to Workplaces
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.
With Throttle instrument selected, the data manager

uploads a result report message from the instrument, and
then sends it to the host. The data manager then waits:
• 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.
Roche Diagnostics
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
> 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
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
Roche Diagnostics
Logging level settings

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

To process samples using the rack ID and position of the
tube, navigate to Workplaces > cobas 8000 data
> 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, see Handling
batch test selections with strict rack and position
(p. 421), and for an example of use, see Using
MODULAR PRE-ANALYTICS (p. 415).
Roche Diagnostics
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
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
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
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 (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

Request (ESR)
• Test availability query: Inventory Status Update
Request (INR)
u For more information on these messages, see:
HL7 messages (p. 223)
Instrument status and test availability messages
(p. 329)
Roche Diagnostics
Configuring result upload settings

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 (p. 131).
Enabling/disabling cobas e flow test subresult upload

The results generated by the embedded tests of a
cobas e flow test are called subresults. Subresults are
used to generate a main result.
You can choose whether or not to report subresults to the

host. To enable or disable reporting of subresults, select
or clear the Send subresults to host check box
accordingly.
Assignment of host codes to cobas e flow test results

The host code of every formula or variable which is
reported as a subresult within a cobas e flow test 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. This
functionality can be useful in ensuring compatibility when
installing new host connections.
You can enable this functionality by navigating to

> Service-related configuration > Interface options,
and selecting the check boxes Use custom host codes
for formulas and variables and Assign host code by
reported lab unit. Both check boxes are cleared by
default.
Roche Diagnostics
The Use custom host codes for formulas and

variables option can be useful if, for example, you need
to assign a numeric host code to a variable. (Variable host
codes are normally alphanumeric.) This check box can
only be selected when the Send subresults to host
check box is also selected.
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 all tests are empty, the sample
is not sent to the host.
You can assign host codes to the measurement units and

formula(s)/variable(s) of an embedded test by navigating
to the Assignment of host code tab of the appropriate
Test / reference ranges window. 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.
q Any custom host codes you assign must be unique

to that cobas e flow test. You cannot use a code which is
used in another cobas e flow test or normal test.
q If you deactivate a cobas e flow test, any assigned

host codes will be lost.
Roche Diagnostics
Host code assignment example The following example shows a formula ("Formula1")
which has been assigned the host code 90000. The
measurement units mg/dL and mmol/L have also been
assigned the host codes D128 and D126, respectively.
w The Test/reference ranges window, showing assigned host codes
u For result messages which use the custom host codes

configured in this example, see cobas e flow test
result with custom host codes (p. 303)
u For more information on how to use this functionality,
refer to the cobas 8000 data manager Operator’s
manual.
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
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 values in OBX-17 (HL7) or R-14.5 (ASTM).
Roche Diagnostics
Identifier of the analytical unit sent to host

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

You can freely edit the analytical unit IDs in the data
manager in Workplaces > System Configuration >
Instrument > [Select instrument] > [Shortcut
menu] > Edit instrument > 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 module and instrument 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.
The data manager sends the ID in HL7 in:

• In HL7 segment OBX-18, component 3. It identifies the
module and instrument that performed the test. For
calibration results from an ISE module, the analytical
unit ID is the only component in the field.
The data manager reads the ID in HL7 in:

• In HL7 segment ECD-5, component 3. Here it
identifies the module and instrument to perform
masking on.
Default value The whole field is freely editable. The default values
follow the format:
Instrument#ModuleType#Position#SubModule
Roche Diagnostics
Instrument String Currently default to MU1, which identifies the first cobas® 8000 modular analyzer
series connected to the data manager In future, there may be more analyzers
connected.
ModuleType String c502, c701, e602, ISE, c702, 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
Examples of default values:
MU1#e602#1#1
MU1#c8000#0#0
The reserved values in ASTM or HL7 cannot be used: |

or ^ or \ or ~ or & . Otherwise, any unique string
can be used as the identifier, for example, the serial
number of the module, such as:
1048-12
In such a case an HL7 OBX segment might look like:
OBX|1||991||109.1|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||C|||20101012074509|bmuser^DMUSER||63|ISE^1^1048-
12^3|20101012074525|
In an ASTM Result record, this might look like:
R|1|^^^999/1/not|2.3^|mmol/L|0.5 - 7.5^bmsrv^DMROUTINE|20100711163455|20100711163455|ISE^2^1048-12^4
|TECH\^NORM\^CRIT\ÛSER|N||F||
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
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

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 (p. 135)
Roche Diagnostics
118 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

Roche Diagnostics
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)
Roche Diagnostics
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

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

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

(p. 122).
u For details of restarting the host connection on the
data manager, see Starting and stopping the host
connection (p. 99).
Roche Diagnostics
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
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.
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.
Roche Diagnostics
123
Table of contents
Configuring the control unit 6

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 6
Enabling communication with data manager . . . . . . . 125
Settings for communications with data manager . . . 126
Text settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Test selection inquiry settings. . . . . . . . . . . . . . . . . 127
Test selection inquiry for rerun tests . . . . . . . . . . . 129

Enabling requests for rerun or reflex tests . . . . . . 130
Result upload settings . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Upload by test, sample, or cluster . . . . . . . . . . . . . 131
Automatic rerun timing . . . . . . . . . . . . . . . . . . . . . . 132
When ordering HPE tests. . . . . . . . . . . . . . . . . . . . . 133
Configuring result upload . . . . . . . . . . . . . . . . . . . . 134
Getting a trace file from the control unit. . . . . . . . . . . 135
Roche Diagnostics
124
Table of contents
Roche Diagnostics
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
Setting button. The Communication Setting dialog

is displayed.
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.
Roche Diagnostics
126 Settings for communications with data manager
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.

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.
Text settings
To configure the settings of text information sent to data

manager, go to Utility > System > Data Manager
Settings > Text Settings.
Send conc. of chemistry qualitative tests In a production environment, select Send conc. of
chemistry qualitative tests.
Roche Diagnostics
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.
Test Selection Inquiry In a production environment, select Test Selection

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

Timeout.
Roche Diagnostics
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 (p. 102).
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 (p. 59).
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

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

Priority Mode.
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.
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
(p. 415).
Roche Diagnostics
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 (p. 425).
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
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.
Automatic rerun is not available for cobas e flow tests.

u For details of the result upload settings, see Result
u For details of the By Cluster options, see By cluster
options (p. 132)
Roche Diagnostics
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.
Roche Diagnostics
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.
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

(p. 133)
Roche Diagnostics
132 Result upload settings
By cluster options There are 2 by cluster options:

• Chemistry incl. ISE / Immunoassay: Chemistry and
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 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(a), when the sample has:
By sample Selected A result for every “Autorerun enabled” test.
Cleared A result for every test.
Chemistry incl. ISE Selected A result for every “Autorerun enabled” test in the corresponding cluster.
/ Immunoassay or Cleared A result for every test in the corresponding cluster.
ISE / Chemistry /
Immunoassay
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.
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
(a) 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.
Roche Diagnostics
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.
Selected upload mode As Soon As Setting HPE test is ordered Changes in behavior
No No changes
The data manager uploads results for the current sample
Off as though Chemistry incl. ISE / Immunoassay or ISE /
Yes
Chemistry / Immunoassay were selected with As Soon
By Sample As Setting on
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
Chemistry incl. ISE / Off The data manager uploads results for the current sample
Immunoassay or ISE / Yes
as though As Soon As Setting were on
Chemistry /
Immunoassay 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 (p. 131)
Roche Diagnostics
134 Result upload settings
Configuring result upload
r To configure how the control unit

uploads results
1 Navigate to Utility > System > Result Upload
Settings.
2 From the drop-down list for type of result you want to

configure, select By Test, By Sample, Chemistry
incl. ISE / Immunoassay or ISE / Chemistry /
Immunoassay. 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.

Roche Diagnostics
Getting a trace file from the control unit

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.

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
136 Getting a trace file from the control unit
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 (p. 117)
Roche Diagnostics
ASTM reference
7 ASTM protocol (LIS2 - A2) ...............................................................................139

8 ASTM text content (LIS2 - A2)........................................................................151
9 ASTM communication examples....................................................................187
Roche Diagnostics
139
Table of contents
ASTM protocol (LIS2 - A2) 7
This chapter presents the lower layers of the ASTM (or

LIS2-A2) protocol, as used by cobas® 8000 data
manager.
In this chapter 7
Overview of the ASTM protocol . . . . . . . . . . . . . . . . . . 141
Communication processing layers . . . . . . . . . . . . . . . . 142
ASTM lower layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
ASTM message framing . . . . . . . . . . . . . . . . . . . . . . . . 144
ASTM syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Coding rules for the messages . . . . . . . . . . . . . . . . 145
Message transmission phases . . . . . . . . . . . . . . . . . . . 148

Checksum calculation / message frame . . . . . . . . . . . 149
Roche Diagnostics
140
Table of contents
Roche Diagnostics
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.
Roche Diagnostics
142 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
and Computer Systems

• ASTM E1394-91 High Level Protocol
Standard Specification for Transferring Information
Between Clinical Instruments and Computer Systems
Roche Diagnostics
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.
Roche Diagnostics
144 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
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
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.
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
146 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.
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
The following escape sequence (starting with & and

ending with &) is defined. When this sequence is
detected in a field, it is changed to a corresponding
character and deleted.
Escape sequences other than these are skipped and

treated as NULL values.
&F& Indicates field delimiter

&S& Indicates component delimiter
&R& Indicate repeat delimiter
&E& Indicates escape
Roche Diagnostics
148 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
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
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]
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
150
7 ASTM protocol (LIS2 - A2) Checksum calculation / message frame
Roche Diagnostics
151
Table of contents
ASTM text content (LIS2 - A2) 8

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 8
List of record levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
List of messages used in host communication . . . . . 154
Messages transmitted by the data manager . . . . 154
Messages transmitted by the host . . . . . . . . . . . . . 155

Description of ASTM records . . . . . . . . . . . . . . . . . . . . 157
Message Header Record . . . . . . . . . . . . . . . . . . . . . . . . 158
Patient Information Record . . . . . . . . . . . . . . . . . . . . . . 160
Order Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Comment Record (following Order Record) . . . . . . . . 166
Result Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Comment Record (following Result Record) . . . . . . . 174
Query Record (Request Information Record) . . . . . . . 176
Photometric Calibration Result M(PCR) . . . . . . . . . . . 180
ISE Calibration Result Record - M(ICR). . . . . . . . . . . . 181
ISE data alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
ISE calibration analytical data . . . . . . . . . . . . . . . . . 182
E-module (immunology) Calibration Result Record -
M(ECR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Message Termination Record . . . . . . . . . . . . . . . . . . . . 186
Roche Diagnostics
152
Table of contents
Roche Diagnostics
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 (p. 142).
Roche Diagnostics
154 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(a)
Test Selection Information Host to data manager o o
Order Query Host to data manager x o
Result Query Host to data manager x o
Test Selection Inquiry data manager to Host x o

Patient Sample Analytical Data data manager to Host o o
Control Sample Analytical Data data manager to Host o o
Calibration Analytical Data data manager to Host o x
y Messages used in host communication (ASTM)
(a) o = available, x = not available
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 -

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

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
156 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 (p. 76)
Order query (p. 77)
(p. 83).
Roche Diagnostics
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.

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
158 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|20141026142034|
H|\^&|12345||cobas 8000^1.06|||||host|TSUPL|P|1|20141026142034|
H|\^&|12345||cobas 8000^1.06|||||host|RSUPL|P|1|20141026142034|
H|\^&|12345||cobas 8000^1.06|||||host|RSUPL^REAL|P|1|20141026142034|
H|\^&|12345||cobas 8000^1.06|||||host|RSUPL^BATCH|P|1|20141026142034|
H|\^&|12345||cobas 8000^1.06|||||host|PCUPL^REAL|P|1|20141026142034|
H|\^&|12345||cobas 8000^1.06|||||host|ICUPL^REAL|P|1|20141026142034|
H|\^&|12345||cobas 8000^1.06|||||host|ECUPL^REAL|P|1|20141026142034|
H|\^&|12345||host|||||cobas 8000^1.06|TSDWN|P|1|20141026142034|
H|\^&|12345||host|||||cobas 8000^1.06|RSREQ|P|1|20141026142034|
H|\^&|12345||host|||||cobas 8000^1.06|TSREQ|P|1|20141026142034|
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 \ Repeat Delimiter = backslash [ASCII 92]
o ^ Component Delimiter = caret [ASCII 94]

o & Escape character = ampersand [ASCII 38]
3 6.3 String O R Message Control Identifier to uniquely identify the message. The cobas® 8000
data manager sends the internal message ID as integer number; the host can
send any string or number for message identification or leave this field empty.
4 6.4 Field contains no data.
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 (p. 101).
o Version is the data manager version (numeric value).
O - Sender ID. If sent, used only for tracing purposes.
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

11 6.11 Complex R R Identifier for the message type and purpose. Format is two strings:
Type^Mode.
TSREQ Test selection request, from data manager to host, or from host
to data manager.
TSDWN Test selection download, from host to data manager.
TSUPL Test selection upload, from data manager to host.
RSREQ Result request, from host to data manager.
RSUPL Result upload, from data manager to host.
RSUPL^REAL First transmission of QC results, from data manager to host (or
Patient results in a realtime or batch upload, except as an
answer to a result request).
RSUPL^BATCH o Repeat transmission of QC results, from data manager to
host.
o Patient sample result upload from data manager to host in
reply to a result query.
PCUPL^REAL Photometry calibration report, from data manager to host.
ICUPL^REAL ISE calibration report, from data manager to host.
ECUPL^REAL Elecsys calibration report, from data manager to host.
12 6.12 P O R Processing ID, fixed value P , meaning production.
13 6.13 1 O R Protocol version, fixed value 1 . (Meaning LIS2-A2.)
14 6.14 DateTime O R Time and date the message was created.
For a calibration message, the date and time of the calibration.
y Message header record
Roche Diagnostics
160 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||||^||||

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.
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.
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.
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
! 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
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|20100429161525|20100429161525||||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|20110715093311|20110715093311||||A||||
1||||||||||O
Order record with sequence number in Result

Upload
O|1||1013^50101^3^^S1^SC^not|^^^8413^1\^^^8571^1\^^^8706^1|R|20110715093311|20110715093311||||N||||1
||||||||||F|

Order record from cobas e flow test
O|1|100011|0^40005^1^^S1^^not|^^^15000^1|S|20150414165312|20150414165312||||N||||1||||||||||F|

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 (p. 425).
For Quality Control material, Name^LotÎDÊxpDate^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.
y Order record
Roche Diagnostics
162 Order Record

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.
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.
o SC Standard cup
o MC Micro cup
o NST0 Non-standard tube
o FBT1 False bottom tube 1
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 (p. 57).
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

5 8.4.5 Complex O R/O Testcode with dilution factor.
^^^Testcode^Dilution
If the host has no pending test, the host must send a Test Selection
Download message with this field empty. In a test selection upload, if the
data manager has no information on tests, it will leave this field empty.
You can send multiple tests codes in one message by repeating this field,
for example:
O|1|1234|0^00083^5^^S1^SC|^^^989^1\^^^990^1\^^^991^1
|S|20101026152611|20101026152611||||A||||1||||||||||
O|
For serum index tests, you must send all three test types together (lipemic,
icteric, and hemolytic), or send a test profile that contains all three.
Otherwise the test will not be run.
u For more details on sending serum index orders, see Sending test
selections (p. 79).
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
Roche Diagnostics
164 Order Record

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 .
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.
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)
y Order record
Roche Diagnostics

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.
21 8.4.21 Field contains no data
26 8.4.26 Character R R Report type, indicating source of message.

o O Sent from host.
o F Sent from data manager / cobas® 8000 modular analyzer series.
y Order record
Roche Diagnostics
166 Comment Record (following Order Record)
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.
C|1|L|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.

1 10.1 C R R Record Identifier, fixed value.
2 10.2 Number R R Sequence number. Set to 1 , as only one comment is permitted after an order
record.
3 10.3 Character R R Comment source. A single-character code.
From the host, this is always set to L .
From the cobas® 8000 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

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
Roche Diagnostics
Result Record
The data manager uses the result record to upload the
details of test results.
A quantitative patient result:
R|1|^^^999/1/not|2.3^|mmol/L|0.5 - 7.5^TECH\^NORM\^CRIT\ÛSER|N||F||bmsrv^DMROUTINE|20100711163455|2
0100711163455|ISE^2^MU1#ISE#1#2^4|
A qualitative patient result:
R|1|^^^101/1/not|1^2.68|mmol/L|^TECH/^^NORM/^^CRIT/^ÛSER|N||F||bmsrv^DMROUTINE|20090311163455|20090
311163455|ISE^2^MU1#ISE#1#2^4^104|
For an automatically-validated result, the operator is

written as “SYSTEM”:
R|3|^^^991/Inc/not|5.5|mmol/L|4.0 - 44.0^TECH\2.0 - 22.0^NORM\3.0 - 33.0^CRIT\1.0 - 11.0ÛSER|N||F||

bmserv^SYSTEM|20100718164600|20100729161525|ISE^2^MU1#ISE#1#2^4|
For an automatically-validated QC result:
R|1|^^^870/1/not|17.30|g/dL||||F||bmserv^SYSTEM|20100718164500|20100729165317|22^1^MU1#c502#2#1^9^0^
Current|
This shows a result below the EP17-A level of detection:
R|1|^^^989/1/not|2.1|mmol/L|^TECH\9 - 144^NORM\^CRIT\ÛSER|HU||F||bmserv^SYSTEM|20100621084348|20100
621084404|ISE^1^MU1#ISE#1#1^3^28|

This shows the main result of a cobas e flow test:
R|1|^^^12000/1/not|-1||^TECH\^NORM\^CRIT\ÛSER|||F||^SYSTEM||20160312120410|DM^0^DM#DM#0#0^0^|
This shows a variable subresult of a cobas e flow test:
R|2|^^^12000/1/not^^HIVDuo_01/1|0.421^-1|COI|^TECH\^NORM\^CRIT\ÛSER|||F||^SYSTEM||20160312120410|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||COI|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20160312114537|201603121
20410|e801^2^MU1#e801#2#2^10^1017|
This shows an embedded test subresult of a

cobas e flow test with data points:
R|6|^^^12000/1/not^^11014/1|840.8573|count|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20160312114537
|20160312120410|e801^2^MU1#e801#2#2^10ÊFS|
Roche Diagnostics
168 Result Record
Below is an example of a result with raw data and data

point values, generated by an e 801 module. This example
shows only the EFS portion of the message.
R|2|^^^16013//not^^16013/1|4117.485^12842\13777\13857\13858\13475\13231\13477\13326\13203\13619\1315
9\14348\13831\13535\14450\13650\13468\13446\12956\12729\12709\12860\12596\14045\13763\12800\12927\12
327\13228\13016\11910\13610\13850\13670\13335\12820\12964\12818\12588\13056\12658\12909\12523\12733\
13468\13409\13420\13104\12313\12222\12375\12865\13620\13388\13629\13472\12897\13659\13384\12942\1310
0\12526\12437\13208\12421\12479\12815\13298\13544\13628\12675\12995\13384\13061\13221\13600\13932\13
525\13533\13286\19892\27440\27960\28335\28088\28012\27754\27577\27629\27544\27423\27298\27200\27101\
26976\26895\26971\26871\26886\26686\26534\26197\26313\26318\26124\26155\26048\26212\25961\25906\2569
5\25683\25614\25807\25692\25711\25615\25565\25709\25582\25261\25466\25444\25187\25090\25111\25096\25
232\25101\24990\24970\25258\24823\24929\24610\24823\24966\24956\24941\24503\24680\24645\24433\24487\
24319\24538\24606\24444\24379\24497\24466\24414\24252\24421\24343\24246\24151\24158\24265\24121\2427
7\24205\24196\24293\24109\24263\24017\24082\23995\23960\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\ÛSER|||F||bmserv^|20150415172021|20150415173854|e801^1^MU1#
e801#1#1^3ÊFS|

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

3 9.3 Complex R Test request
^^^Testcode/Dilution/Pre-dilution
Note that the fourth component is separated into three parts with a
forward-slash separator / .
If the result corresponds to a subresult or embedded test result of a
cobas e flow test, and the system is configured to report subresults to the
host, the test request has the following structure:
^^^Testcode/Dilution/Pre-dilution^^SubresultCode/Di
lution
Note that the sixth component is separated into two parts with a forward-
slash separator / . In this case, segment 3.4 also takes the main result of
the cobas e flow test.
3.1 This component contains no data
3.4 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.
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 For an e 801 cobas e flow test: 1 or empty
O Pre- String Indicates whether sample is pre-diluted:

dilution o pre-diluted
o not
3.6 O SubresultC String Identifier (or application code) for the subresult
ode reported by a cobas e flow test. This subresult
can be the result of an embedded test, or a
variable created internally by the
cobas e flow test.
O Dilution String Dilution factor of the embedded test reported
in Subresultcode .
y Result record
Roche Diagnostics
170 Result Record

4 9.4 Complex R Measurement value.
The measurement values are only transmitted for patient and QC results.
ReportableResultÂdditionalResultValues
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 (71)
Quantitative results:
4.1 Number R Reportable The result. A missing or suppressed result is sent as 7
Result spaces. (ASCII 32 / 0x20).
4.2 Number O Additional Empty or a qualitative flag.
Result For a main result of a quantitative cobas e flow test, this
Values field is empty.
Qualitative results:
4.1 Number R Reportable o For c-module and ISE module: an integer code from -
Result 2 to 3 inclusive.
o For e-module: an integer code -1 (non-reactive), 0
(border line), 1 (reactive).
o For a cobas e flow test, this can be a numeric code.
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.
u For cobas e flow test codes, see Result codes
(p. 413)
Suppressed results are sent as 7 spaces.
4.2 Number R Additional The quantitative value, like value for a quantitative result.
Result For e-module qualitative results this contains COI .
Values For a main result of a qualitative cobas e flow test, this
field is empty.
For a main result of an assignment/formula, this field is
empty.
Data point results:

4.1 Number R Reportable The result. A missing or suppressed result is
Result sent as 7 spaces. (ASCII 32 / 0x20).
4.2 Number R/O Additional Data points. Up to 200 data point values,
Result separated by backslashes (\).
Values
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 .
For a quantitative cobas e flow test, this field shows units of measure..
For qualitative cobas e flow test results, no value is sent in this field.
y Result record
Roche Diagnostics

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\ÛSER
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\ÛSER
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
Above high normal value

H
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)
eFlow.E Standard alarm for cobas e flow tests
eFlow.W Generic cobas e flow test warning (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 (p. 70).
9 9.9 Character R Result status. This can take:
o F = First run result, or QC result
o C = Corrected result
o M = Manually edited result
o X = Calculated test, but test could not be calculated (for example,
divided by zero)
y Result record
Roche Diagnostics
172 Result Record

11 9.11 Complex R Active operators in the format:
Instrument operator^Datamanager operator
11.1 String R o Instrument operator
This is the username the operator used to log into the control unit.
Empty in the case of a manual or calculated result.
11.2 String R o Datamanager operator
This is the username the operator used to log into the data manager. If
the result is automatically validated, or the data manager is in pass-
through mode, this reads SYSTEM.
12 9.12 DateTime O Pipetting time. This is considered to be the time the test started. (Format:
YYYYMMDDhhmmss.)
Note: For manual and calculated tests, this field is empty.
13 9.13 DateTime R Completion time. This is the time the result is available (in other words,
time of validation at the data manager). (Format: YYYYMMDDhhmmss.)
y Result record
Roche Diagnostics

14 9.14 Complex R Identifier of the measurement unit or module that performed the test.
ModuleType^SubModuleÂnalyticalUnitIDÎnstrumentID^
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
UnitID is 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:
Example: MU1#c502#2#1
u For details, see Identifier of the analytical unit sent to
host (p. 115).
14.4 Number R Instrument Instrument number in data manager (A specific identifier
ID inside the data manager which identifies a module. This is
a number which has no relationship to the internal

position of the module in the machine.)
14.5 Number R CalID Calibration ID. Identifier of the calibration the result refers
to, set in the control unit. Sent only if available. It is empty
for results that do not have a calibration, for example,
calculated and manual results.
For raw data results, contains one of the following codes:
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
empty.
14.7 Number SBNo An integer showing the standby bottle number, if used.
The standby bottles are numbered sequentially, starting
with 1.
Reserved field, only for QC measurements, otherwise
empty.
y Result record
Roche Diagnostics
174 Comment Record (following Result Record)
Comment Record (following Result

Record)
Record to transfer comments regarding the measured
result. This record is transmitted by the data manager,
either by adding a comment to a result, or by passing on
an instrument comment received from the control unit.
The first record is an instrument flag, and is mandatory.
For a test that did not generate any instrument alarms,

the instrument flag is:
C|1|I|0|I|
This is: “C-one-i-zero-i”.
An instrument alarm flag is, for example:
C|1|I|23ÎSE 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
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.

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

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 (p. 335).
A main test in a cobas e flow test message generates
only these errors:
o eFlow.E Standard alarm for cobas e flow tests
o CalcError EP17-A error alarm for
cobas e flow tests
4.1 String Desc Description of error flag (blank if no error)
Comment Type G after result record
TestÛser^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
Roche Diagnostics
176 Query Record (Request Information Record)
Query Record (Request Information

Record)
The data manager and the host both use the Query
Record, or Request Information Record, to request a
sample’s open test selections, in a test selection inquiry
message or a order query message (H-11 is TSREQ ). It is
also used to request test results in a Result Query
message (H-11 is RSREQ ).
From data manager to host:
Q|1|^^123^0^10001^2^^S1^SC^R1||ALL|||||||R|O||
Q|1|^^********************^0^10001^2^^S1^SC^R1||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:
Q|1|^S1^^1031||||||||||F|
Field Ref. Value Host DM Max Description

Size
1 11.1 Q R R 1 Record identifier, fixed value.
2 11.2 1 R R 1 Sequence number. Fixed value, showing that only one query
record per message is supported.
y Query record
Roche Diagnostics

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.

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:
Order query (p. 77)
Order and result queries with limited sample
lifetime (p. 83).
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 (p. 425).
Previously, this field was known as “Sample
Number.”
The further components contain no data.
y Query record
Roche Diagnostics
178 Query Record (Request Information Record)

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

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
<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 (p. 57)
3.10 String - R 2 QueryType A two-character code:
R1 Query for 1st measurement
R2 Rerun query
5 11.5 ALL - R 3 Subselection criteria, fixed value
12 11.12 Character - R 1 o R for Routine samples
o S for STAT samples (Short Turn-Around Time)
13 11.13 Character - R 1 The request information status code.

If sent from the data manager to the host:
o O (capital letter O) for “Request for test selections”.
Character O - 1 The request information status code.
If sent from the host to the data manager in a result inquiry:
o F = send final results
o (empty) = send all results
If sent from the host to the data manager in an order inquiry:
o O = (capital letter O) send only open orders with no results
o (empty) = send all orders
y Query record
Roche Diagnostics
180 Photometric Calibration Result M(PCR)
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^\^^^^^\^^^^^\^^^
^^\^^^^^|

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 (p. 115).
7 14 Number - R 3 Calibration alarm.
u For details, see Data alarms (p. 335).
8 14 Number - O 6 Standard deviation value data.
9 14 Complex - R Repeat field of number types. Repeated from STD1 to STD6 for as many
as there are.
Format:
First Initial Absorbance^First Absorbance^Second Initial Absorbance^Second

Absorbance^Data Alarm^Prozone Value
Number R 6 First Initial
Absorbance
Number R 6 First
Absorbance
Number R 6 Second Initial
Absorbance
Number R 6 Second
Absorbance
Number R 3 Data Alarm u For details, see Instrument alarms (p. 395).
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
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|

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 (p. 115).
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.
8 14 String O 7 Cl Calibration Alarm: Cl test calibration status.

9 14 Complex R Na Data Alarm: Na test data alarm.
u For details, see ISE data alarms (p. 181).
10 14 Complex R K Data Alarm: K test data alarm.
11 14 Complex R Cl Data Alarm: Cl test data alarm.
12 14 Complex R Na Data: Na test calibration analytical data.
u For details, see ISE calibration analytical data (p. 182).
13 14 Complex R K Data: K test calibration analytical data.
14 14 Complex R Cl Data: Cl test calibration analytical data.
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
182 ISE Calibration Result Record - M(ICR)
Na (Sodium) Field 9
K (Potassium) Field 10
Cl (Chlorine) Field 11
Each of these fields is a complex type, and contains 10

number type components.
Each component is a Number type, max. length 3.
Internal standard solution electromotive

force data alarm^
Low solution electromotive force data
alarm^
High solution electromotive force data
alarm^
Calibrator solution electromotive force
data alarm^
Slope for display data alarm^
Internal standard solution concentration
data alarm^
Calibrator solution concentration data
alarm^
Carryover rate alarm^
Calculation slope value alarm^
Numbers for compensation data alarm
ISE calibration analytical data

The analytical data from the ISE calibration is passed in

the following fields.
Na (Sodium) Field 12
K (Potassium) Field 13
Cl (Chlorine) Field 14
Each of these fields is a complex type and contains 10

number type components.
Roche Diagnostics
Each component is a Number type, max. length 6.
Internal standard solution electromotive

force data^
Low solution electromotive force data^
High solution electromotive force data^
Calibrator solution electromotive force
data^
Slope for display data^
Internal standard solution concentration
data^
Calibrator solution concentration data^
Carryover rate^
Calculation slope value^
Numbers for compensations data
Roche Diagnostics
184 E-module (immunology) Calibration Result Record - M(ECR)
E-module (immunology) Calibration Result

Record - M(ECR)
The data manager sends calibration data from the Elecsys
immunology e-module in the manufacturer-defined e-
module Calibration Result M(ECR) record.
Example
M|1|ECR|bmserv|^^^1|LotCalibration|MU1#e602#2#1|157328||0|158941|O|IÔ^\MÔ^\SÔ^\R^1.074^\DÔ^\L^^\
FÔ^\YÔ^\BÔ^|936.337^888.767\39609.680^39716.950|||||20101018175819|

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
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
(p. 115).
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

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>

Each value is the numeric value sent by the analyzer.
19 14 DateTime O 14 Date and time measurement was performed
(YYYYMMDDHHMMSS).
y E-module (immunology) Calibration Result Record - M(ECR)
Roche Diagnostics
186 Message Termination Record
Message Termination Record

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

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
Roche Diagnostics
187
Table of contents
ASTM communication examples 9
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 9
Low level trace file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Test selection inquiry from data manager . . . . . . . . . . 190
Routine test selection inquiry and download . . . . 190
STAT sample test selection inquiry and
9 ASTM communication examples

download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Test selection inquiry and download if no sample
found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Test selection inquiry with sequence number . . . 191
Patient result upload messages . . . . . . . . . . . . . . . . . . 192
Realtime ISE result upload . . . . . . . . . . . . . . . . . . . 192
ISE result upload - sample short . . . . . . . . . . . . . . 192
C-module result upload with no flag . . . . . . . . . . . 192
Glucose result with alarm flag . . . . . . . . . . . . . . . . 193
Batch upload of current results . . . . . . . . . . . . . . . 193
Batch upload of current results - sample short . . 193
Batch upload all previous results . . . . . . . . . . . . . . 194
Result below normal range . . . . . . . . . . . . . . . . . . . 194
Result below level of detection . . . . . . . . . . . . . . . . 195
Result with sample identified by sequence
number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Result for sample with multiple
cobas e flow tests and embedded tests . . . . . . . . 196
Result for cobas e flow test with non-reported
embedded tests and formula or variable result . . 197
cobas e flow test with qualitative and
quantitative result . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Raw data and data point messages . . . . . . . . . . . . . . . 199
e 602 result with data point values. . . . . . . . . . . . . 199
Roche Diagnostics
188
Table of contents
e 801 result message including raw data . . . . . . . 199

e 801 result message with raw data and data
points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Quality control uploads . . . . . . . . . . . . . . . . . . . . . . . . . 204
Realtime quality control upload . . . . . . . . . . . . . . . 204
Realtime quality control upload with a standby
bottle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Batch quality control upload . . . . . . . . . . . . . . . . . . 205
Batch quality control upload with a standby
bottle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
e 801 quality control upload with raw data . . . . . . 205
Calibration result uploads . . . . . . . . . . . . . . . . . . . . . . . 207
C-module calibration result upload . . . . . . . . . . . . 207
ISE-module calibration result upload. . . . . . . . . . . 207
E-module calibration result upload . . . . . . . . . . . . 207
Result request from host and the data manager
result upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Request for currently active results . . . . . . . . . . . . 209
Request for all results . . . . . . . . . . . . . . . . . . . . . . . 209
Result request but no results . . . . . . . . . . . . . . . . . 210
Result request but sample not found. . . . . . . . . . . 210
Result request with a sequence number. . . . . . . . 211
Result request with an expired sample . . . . . . . . . 211
Order query from the host. . . . . . . . . . . . . . . . . . . . . . . 213
Order query for all tests . . . . . . . . . . . . . . . . . . . . . . 213
Order query for all open tests . . . . . . . . . . . . . . . . . 213
Order query but no open tests . . . . . . . . . . . . . . . . 213
Order query but sample not found. . . . . . . . . . . . . 214

Order query with sample identified by sequence
number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Roche Diagnostics
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.04|||||host|RS
UPL|P|1|20101020184623|[CR]P|1||||^||||[CR]O|1|
10002|0^10002^2^^S4^SC^not|^^^870^1\^^^880^1\^^
^890^1|R|20101016120539|20101016120539||||N||||
4||||||||||F|[CR]C|1|I|^^^^|G|[CR]R|1|^^^870/1/
not|17.30|g/dL|^TECH\^N[ETB]E9[CR][LF]
HOST 18:46:29,333 [ACK]
c8kDM 18:46:29,411 [STX]2ORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|200912
18164600|20101016120550|c502^1^MU1#c502#2#1^9^0
|[CR]C|1|I|0|I|[CR]R|2|^^^880/1/not|1.50|g/dL|^
TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20091
218164600|20101016120552|c502^1^MU1#c502#2#1^9^
0|[CR]C|1|I|0|I|[CR]R|3[ETB]BA[CR][LF]
HOST 18:46:29,411 [ACK]
c8kDM 18:46:29,426 [STX]3|^^^890/1/not|8.67|%|^TECH\^NORM\^CRIT\Û
SER|||F||bmserv^SYSTEM||20101016120552|c502^1^M
U1#c502#2#1^9^0|[CR]C|1|I|0|I|[CR]L|1|N|[CR][ET
X]F1[CR][LF]
HOST 18:46:29,426 [ACK]
c8kDM 18:46:29,442 [EOT]
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
190 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.
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:
Q|1|^^321070^0^50094^2^^S1^SC^R1||ALL|||||||R|O|
L|1|N|
Host:
H|\^&|||ASTM-Host^V 6.8g|||||cobas 8000^1.04|TSDWN|P|1|20101020100000
P|1||PatID3||Lastname^Firstname||19881231|M
O|1|321070|0^50094^2^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|R||||||A||||1||||||||||O
C|1|L|Comm1^Comm2^Comm3^Comm4^Comm5|G
L|1|N
STAT sample test selection inquiry and download


inquiry for a STAT sample, and the host’s test selection
download.
DM:
Q|1|^^321040^0^40002^3^^S1^SC^R1||ALL|||||||S|O|
L|1|N|
Host:
P|1||PatID3||Lastname^Firstname||19881231|M
O|1|321040|0^40002^3^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|S||||||A||||1||||||||||O
L|1|N
Test selection inquiry and download if no sample found

inquiry for a sample, and the host’s test selection
download, saying that it could not find the sample.
Roche Diagnostics
DM:
Q|1|^^321071^0^50094^1^^S1^SC^R1||ALL|||||||R|O|
L|1|N|
Host:
P|1|
O|1|321071|0^50094^1^^S1^SC||R||||||A||||1||||||||||O
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
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 (p. 190) and STAT sample
test selection inquiry and download (p. 190).
Test selection inquiry with sequence number

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:
Q|1|^^^1013^50101^3^^S1^SC^R1||ALL|||||||R|O|
L|1|N|
Host:
P|1||M820101K||Lastname^Firstname||19831213|F
O|1||1013^50101^3^^S1^SC^not|^^^8571^1\^^^8413^1\^^^8706^1\|R|20110715093311|20110715093311||||A||||
1||||||||||O
L|1|N
Roche Diagnostics
192 Patient result upload messages
Patient result upload messages

This section shows examples of ASTM patient result
upload messages.
Realtime ISE result upload

This section shows an example of an ASTM realtime
result upload from an ISE module.
P|1||||^||||
O|1|321088|0^50022^5^^S1^SC^not|^^^990^1|R|20101016183237|20101016183237||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^990/1/not|0.68|mmol/L|^TECH\^NORM\^CRIT\ÛSER|||C||bmserv^SYSTEM|20101018185121|2010101818513
6|ISE^2^MU1#ISE#1#2^4^128|
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.
P|1||||^||||
O|1|321042|0^50011^4^^S1^SC^not|^^^991^1|R|20101014115322|20101006162241||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^991/1/not| |mmol/L|^TECH\^NORM\^CRIT\ÛSER|||C||bmserv^SYSTEM|20101018183051|2010101818
3106|ISE^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.
P|1||||^||||
O|1|321042|0^50011^4^^S1^SC^not|^^^8717^1|R|20101019094904|20101019094904||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8717/1/not|4.28|mmol/L|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20101019095027|201010191000
40|c701^1^MU1#c701#1#1^6^77|
C|1|I|0|I|
L|1|N|
Roche Diagnostics
Glucose result with alarm flag

from a c-module with an alarm flag.
P|1||||^||||
O|1|321057|0^50007^1^^S1^SC^not|^^^8717^1|R|20101019085027|20101019085027||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8717/1/not|-0.01|mmol/L|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20101019091622|20101019092
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.
P|1||PatID1||Lastname^Firstname||19451231|M|
O|1|321015|0^50071^1^^S1^SC^not|^^^990^1\^^^991^1\^^^8717^1|R|20101019174209|20101019174209||||N||||
1||||||||||F|
C|1|I|C1^C2^C3^C4^C5|G|
R|1|^^^990/1/not|0.75|mmol/L|^TECH\^NORM\^CRIT\< 0ÛSER|||F||bmserv^SYSTEM|20101020095735|2010102009
5751|ISE^1^MU1#ISE#1#1^3^125|

095751|ISE^1^MU1#ISE#1#1^3^126|
R|3|^^^8717/Inc/not|-0.02|mmol/L|^TECH\^NORM\^CRIT\ÛSER|||C||bmserv^SYSTEM|20101019175614|201010191
80627|c701^1^MU1#c701#1#1^6^77|
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.
P|1||||^||||
O|1|321042|0^50011^4^^S1^SC^not|^^^989^1\^^^990^1\^^^991^1|R|20101014115322|20101006162241||||N||||1
||||||||||F|
C|1|I|^^^^|G|
3829|ISE^1^MU1#ISE#1#1^3^124|
3829|ISE^1^MU1#ISE#1#1^3^125|
Roche Diagnostics
3829|ISE^1^MU1#ISE#1#1^3^126|
Batch upload all previous results

This section shows an example of an ASTM batch upload
of all previous results.
O|1|321015|0^50071^1^^S1^SC^not|^^^990^1\^^^991^1\^^^8717^1|R|20101019174209|20101019174209||||N||||
1||||||||||F|
C|1|I|C1^C2^C3^C4^C5|G|
4439|ISE^2^MU1#ISE#1#2^4^128|
R|2|^^^990/1/not|0.70|mmol/L|^TECH\^NORM\^CRIT\< 0ÛSER|||C||bmserv^SYSTEM|20101019174459|2010101917
4515|ISE^1^MU1#ISE#1#1^3^125|
5751|ISE^1^MU1#ISE#1#1^3^125|
174403|ISE^1^MU1#ISE#1#1^3^126|
174439|ISE^2^MU1#ISE#1#2^4^129|
095751|ISE^1^MU1#ISE#1#1^3^126|
547|c701^1^MU1#c701#1#1^6^77|
80627|c701^1^MU1#c701#1#1^6^77|
L|1|N|
Result below normal range

below the normal reference range.
H|\^&|10252||cobas|^|8000^1.04|||||host|RSUPL|P|1|20100610200938|
P|1||ES06516622121998||Lastname^Firstname||19330813|M|
O|1|123|0^50063^2^^S1^SC^not|^^^989^1\^^^991^1\^^^8717^1|R|20100604235148|20100604235148||||N||||1||
||||||||F|
C|1|I|^^^^|G|
R|1|^^^989/1/not|2.1|mmol/L|^TECH\9 - 144^NORM\^CRIT\ÛSER|L||F||bmserv^SYSTEM|20100621084348|201006
21084404|ISE^1^MU1#ISE#1#1^3^28|
C|1|I|0|I|
Roche Diagnostics
|ISE^1^MU1#ISE#1#1^3^28|
C|1|I|0|I|
935|c701^2^MU1#c701#1#2^7^168|
C|1|I|0|I|
L|1|N|
Result below level of detection

below the EP17-A level of detection.
H|\^&|10256||cobas|^|8000^1.04|||||host|RSUPL|P|1|20100610201014|
P|1||ES06516622121998||Lastname^Firstname||19330813|M|
O|1|123|0^50063^2^^S1^SC^not|^^^989^1\^^^991^1\^^^8717^1|R|20100604235148|20100604235148||||N||||1||
||||||||F|
C|1|I|^^^^|G|
R|1|^^^989/1/not|0.1|mmol/L|^TECH\9 - 144^NORM\^CRIT\ÛSER|LoD||F||bmserv^SYSTEM|20100621084348|2010
0621084404|ISE^1^MU1#ISE#1#1^3^28|
C|1|I|0|I|
|ISE^1^MU1#ISE#1#1^3^28|
C|1|I|0|I|
935|c701^2^MU1#c701#1#2^7^168|
C|1|I|0|I|
L|1|N|

Result with sample identified by sequence number
with the sample identified by sequence number. (See field
O-4.1.) This functionality was introduced in version
1.02.03.
P|1||M820101K||Lastname^Firstname||19831213|F|
O|1||1013^50101^3^^S1^SC^not|^^^8413^1\^^^8571^1\^^^8706^1|R|20110715093311|20110715093311||||N||||1
||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8413/1/not|15|g/dL|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20110715084600|20110715084600|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\ÛSER|||F||bmserv^SYSTEM|20110715084600|20110715084600|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\ÛSER|||F||bmserv^SYSTEM|20110715084600|20110715084600
|c702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|
L|1|N|
Roche Diagnostics
Result for 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 R record is created for every
cobas e flow test, and an R record is created for every
embedded test within the cobas e flow test.
P|1||||^||||
O|1|81003|0^50060^1^^S1^SC^not|^^^604^1\^^^171^1\^^^24^1\^^^8060^1\^^^8435^1|R|20141008163717|201410
08163717||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^604/1/not|0.87|μIU/mL|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20141008163720|2014100816372
3|e801^1^MU1#e801#4#1^14^|
C|1|I|eFlow.E^Standard alarm for e801 workflow tests|I|
R|2|^^^604/1/not^^20120/30|0.87|mmol/L|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^|20141008163720|201410081
63723|e801^1^MU1#e801#4#1^14^|
C|1|I|0|I|
R|3|^^^604/1/not^^20040/30|0.87|μIU/mL|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^|20141008163719|201410081
63722|e801^1^MU1#e801#4#1^14^|
C|1|I|0|I|
R|4|^^^604/1/not^^20130/20|0.87|g/L|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^|20141008163719|201410081637
22|e801^1^MU1#e801#4#1^14^|
C|1|I|0|I|
R|5|^^^604/1/not^^20050/50|0.87|μIU/mL|^TECH\^NORM\^CRIT\ÛSER|HU||F||bmserv^|20141008163719|2014100
8163722|e801^1^MU1#e801#4#1^14^|
C|1|I|0|I|
R|6|^^^604/1/not^^20090/20|9.26|μIU/mL|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^|20141008163719|201410081
63722|e801^1^MU1#e801#4#1^14^|
C|1|I|0|I|
R|7|^^^604/1/not^^20140/10|9.26|μmol/L|^TECH\^NORM\^CRIT\ÛSER|HU||F||bmserv^|20141008163719|2014100
8163722|e801^1^MU1#e801#4#1^14^|
C|1|I|0|I|
R|8|^^^171/1/not|0.87|μIU/mL|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20141008163721|2014100816372
4|e801^1^MU1#e801#4#1^14^|
C|1|I|eFlow.E^Standard alarm for e801 workflow tests|I|
R|9|^^^171/1/not^^20120/30|0.87|mmol/L|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^|20141008163721|201410081
63724|e801^1^MU1#e801#4#1^14^|
C|1|I|0|I|
R|10|^^^24/1/not|2.64|nmol/L|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20141008163719|2014100816372
2|e602^1^MU1#e602#3#1^11^24|
C|1|I|0|I|
R|11|^^^8060/1/not|9.26|U/L|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20141008163719|20141008163722
|c702^1^MU1#c702#1#1^6^402|
C|1|I|0|I|
722|c702^1^MU1#c702#1#1^6^424|
C|1|I|0|I|
L|1|N|
Roche Diagnostics
Result for cobas e flow test with non-reported embedded

tests and formula or variable result
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
are sent.
Moreover, a cobas e flow test result can contain an

internally calculated formula or a variable value result in
the embedded tests. This section shows an example of a
result message with an internally calculated formula
result in one of the embedded tests. 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.
P|1||S100||Lastname^Firstname||19500112|M|
O|1|100011|0^40005^1^^S1^^not|^^^15000^1|S|20150414165312|20150414165312||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^15000/1/not|34|COI|^TECH\^NORM\^CRIT\ÛSER|||F||^SYSTEM||20150414173227|DM^0^DM#DM#0#0^0^|
C|1|I|eFlow.E^Standard alarm for e 801 cobas e flow tests|I|
R|2|^^^15000/1/not^^HIVDuo_COI_01/1|3.00|COI|^TECH\^NORM\^CRIT\ÛSER|||F||^SYSTEM||20150414173227|DM
^0^DM#DM#0#0^0^|
C|1|I|0|I|
^0^DM#DM#0#0^0^|

C|1|I|0|I|
^0^DM#DM#0#0^0^|
C|1|I|0|I|
R|5|^^^15000/1/not^^HIVAgResult01/1|1.02|COI|^TECH\^NORM\^CRIT\ÛSER|||F||^SYSTEM||20150414173227|DM
^0^DM#DM#0#0^0^|
C|1|I|0|I|
^0^DM#DM#0#0^0^|
C|1|I|0|I|
^0^DM#DM#0#0^0^|
C|1|I|0|I|
R|8|^^^15000/1/not^^16014/1| |COI|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20150414165351|20
150414171224|e801^1^MU1#e801#1#1^3^2447|
C|1|I|0|I|
150414171212|e801^2^MU1#e801#1#2^4^2446|
C|1|I|0|I|
R|10|^^^15000/1/not^^16014/1| |COI|^TECH\^NORM\^CRIT\ÛSER|||C||bmserv^SYSTEM|20150414171315|2
0150414173148|e801^2^MU1#e801#1#2^4^2448|
C|1|I|0|I|
0150414173136|e801^1^MU1#e801#1#1^3^2445|
C|1|I|0|I|
0150414173212|e801^2^MU1#e801#1#2^4^2448|
Roche Diagnostics
C|1|I|0|I|
0150414173200|e801^1^MU1#e801#1#1^3^2445|
C|1|I|0|I|
L|1|N|
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 21, which is mapped to the result message “PCR
recommended”. In addition, the main result has the
numeric value 6.24.
P|1||||^||||
O|1|8_QQ_MF_OO2|0^50060^1^^S1^SC^not|^^^21060^1|R|20140825093657|20140825093657||||N||||1||||||||||F
|
C|1|I|^^^^|G|
R|1|^^^21060/1/not|6.24^21|μIU/mL|^TECH\^NORM\^CRIT\ÛSER|||F||^SYSTEM||20140825093702|DM^0^DM#DM#0#
0^0^|
C|1|I|0|I|
L|1|N|
Roche Diagnostics
Raw data and data point messages

The examples in this section show result messages
containing raw data and data point values.
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).
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.
P|1||||^||||
O|1|234001|0^50089^5^^S1^^not|^^^64^1|R|20140725105326|20140707093721||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^64/1/not|3.50|IU/L|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20140707092617|20140707092617|e
602^2^MU1#e602#3#2^12^0|
C|1|I|0|I|
R|2|^^^64/1/not|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\22
550\22661\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\2111
3\21247\21186\21112\21069\21006\20992\20932\20833\20823\20714\20937\20854\20747\20723\20734\20699\20
750\20928\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\2050
3\20468\20414\20299\20151\20230\20301\20301\20243\20277\20306\20206\20242\20130\20121\20133\20169\20
069\20002\20195\20116\20116\20026\20079|count|^TECH\^NORM\^CRIT\ÛSER|||F||^|20140707092617|20140707
092617|e602^2^MU1#e602#3#2^12ÊFS|
C|1|I|0|I|
L|1|N|
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 (p. 202)
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.
Roche Diagnostics
200 Raw data and data point messages
P|1||||^||||
O|1|400225|0^50085^4^^S1^SC^not|^^^15000^1|R|20150415162511|20150415162511||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^15000/1/not|34|COI|^TECH\^NORM\^CRIT\ÛSER|||F||^SYSTEM||20150415180014|DM^0^DM#DM#0#0^0^|
C|1|I|eFlow.E^Standard alarm for e 801 cobas e flow tests|I|
R|2|^^^15000/1/not^^HIVDuo_COI_01/1|126|COI|^TECH\^NORM\^CRIT\ÛSER|||F||^SYSTEM||20150415180014|DM^
0^DM#DM#0#0^0^|
C|1|I|0|I|
0^DM#DM#0#0^0^|
C|1|I|0|I|
0^DM#DM#0#0^0^|
C|1|I|0|I|
R|5|^^^15000/1/not^^HIVAgResult01/1|126|COI|^TECH\^NORM\^CRIT\ÛSER|||F||^SYSTEM||20150415180014|DM^
0^DM#DM#0#0^0^|
C|1|I|0|I|
0^DM#DM#0#0^0^|
C|1|I|0|I|
0^DM#DM#0#0^0^|
C|1|I|0|I|
150415173906|e801^2^MU1#e801#1#2^4^2448|
C|1|I|0|I|
R|9|^^^15000/1/not^^16014/1|91338.54|count|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^|20150415172033|20150
415173906|e801^2^MU1#e801#1#2^4ÊFS|
C|1|I|0|I|
R|10|^^^15000/1/not^^16014/1|-112.365|count|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^|20150415172033|2015
0415173906|e801^2^MU1#e801#1#2^4ÊFV|
C|1|I|0|I|
0415173906|e801^2^MU1#e801#1#2^4ÊFC|
C|1|I|0|I|
0415173906|e801^2^MU1#e801#1#2^4^PMT|
C|1|I|0|I|
0150415173854|e801^1^MU1#e801#1#1^3^2445|
C|1|I|0|I|
0415173854|e801^1^MU1#e801#1#1^3ÊFS|
C|1|I|0|I|
R|15|^^^15000/1/not^^16013/1|-113.197|count|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^|20150415172021|2015
0415173854|e801^1^MU1#e801#1#1^3ÊFV|
C|1|I|0|I|
0415173854|e801^1^MU1#e801#1#1^3ÊFC|
C|1|I|0|I|
0415173854|e801^1^MU1#e801#1#1^3^PMT|
C|1|I|0|I|
0150415175930|e801^2^MU1#e801#1#2^4^2448|
C|1|I|0|I|
R|19|^^^15000/1/not^^16014/1|89716.70|count|^TECH\^NORM\^CRIT\ÛSER|||C||bmserv^|20150415174057|2015
0415175930|e801^2^MU1#e801#1#2^4ÊFS|
Roche Diagnostics
C|1|I|0|I|
R|20|^^^15000/1/not^^16014/1|-114.792|count|^TECH\^NORM\^CRIT\ÛSER|||C||bmserv^|20150415174057|2015
0415175930|e801^2^MU1#e801#1#2^4ÊFV|
C|1|I|0|I|
0415175930|e801^2^MU1#e801#1#2^4ÊFC|
C|1|I|0|I|
0415175930|e801^2^MU1#e801#1#2^4^PMT|
C|1|I|0|I|
0150415175918|e801^1^MU1#e801#1#1^3^2445|
C|1|I|0|I|
0415175918|e801^1^MU1#e801#1#1^3ÊFS|
C|1|I|0|I|
0415175918|e801^1^MU1#e801#1#1^3ÊFV|
C|1|I|0|I|
0415175918|e801^1^MU1#e801#1#1^3ÊFC|
C|1|I|0|I|
0415175918|e801^1^MU1#e801#1#1^3^PMT|
C|1|I|0|I|
0150415175954|e801^2^MU1#e801#1#2^4^2448|
C|1|I|0|I|
0415175954|e801^2^MU1#e801#1#2^4ÊFS|
C|1|I|0|I|

0415175954|e801^2^MU1#e801#1#2^4ÊFV|
C|1|I|0|I|
0415175954|e801^2^MU1#e801#1#2^4ÊFC|
C|1|I|0|I|
0415175954|e801^2^MU1#e801#1#2^4^PMT|
C|1|I|0|I|
0150415175942|e801^1^MU1#e801#1#1^3^2445|
C|1|I|0|I|
0415175942|e801^1^MU1#e801#1#1^3ÊFS|
C|1|I|0|I|
0415175942|e801^1^MU1#e801#1#1^3ÊFV|
C|1|I|0|I|
0415175942|e801^1^MU1#e801#1#1^3ÊFC|
C|1|I|0|I|
0415175942|e801^1^MU1#e801#1#1^3^PMT|
C|1|I|0|I|
L|1|N|
Roche Diagnostics
202 Raw data and data point messages
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.
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.
P|1||||^||||
O|1|400225|0^50085^4^^S1^SC^not|^^^16013^1|R|20150415162511|20150415162511||||N||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^16013//not^^16013/1| |COI|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20150415172021|201
50415173854|e801^1^MU1#e801#1#1^3^2445|
C|1|I|0|I|
R|2|^^^16013//not^^16013/1|4117.485^12842\13777\13857\13858\13475\13231\13477\13326\13203\13619\1315
9\14348\13831\13535\14450\13650\13468\13446\12956\12729\12709\12860\12596\14045\13763\12800\12927\12
327\13228\13016\11910\13610\13850\13670\13335\12820\12964\12818\12588\13056\12658\12909\12523\12733\
13468\13409\13420\13104\12313\12222\12375\12865\13620\13388\13629\13472\12897\13659\13384\12942\1310
0\12526\12437\13208\12421\12479\12815\13298\13544\13628\12675\12995\13384\13061\13221\13600\13932\13
525\13533\13286\19892\27440\27960\28335\28088\28012\27754\27577\27629\27544\27423\27298\27200\27101\
26976\26895\26971\26871\26886\26686\26534\26197\26313\26318\26124\26155\26048\26212\25961\25906\2569
5\25683\25614\25807\25692\25711\25615\25565\25709\25582\25261\25466\25444\25187\25090\25111\25096\25
232\25101\24990\24970\25258\24823\24929\24610\24823\24966\24956\24941\24503\24680\24645\24433\24487\
24319\24538\24606\24444\24379\24497\24466\24414\24252\24421\24343\24246\24151\24158\24265\24121\2427
7\24205\24196\24293\24109\24263\24017\24082\23995\23960\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
e801#1#1^3ÊFS|
C|1|I|0|I|
R|3|^^^16013//not^^16013/1|-116.089^33405\33391\33390\33386\33404\33394\33399\33391\33396\33398\3339
3\33395\33387\33386\33385\33391\33401\33378\33399\33390\33399\33390\33392\33373\33378\33396\33380\33
392\33386\33383\33403\33383\33381\33380\33390\33376\33372\33396\33383\33388\33380\33389\33385\33378\
33379\33377\33369\33380\33384\33382\33389\33393\33376\33366\33375\33365\33372\33355\33370\33367\3337
9\33374\33380\33376\33375\33377\33374\33369\33372\33360\33370\33371\33373\33373\33363\33365\33359\33
347\33367\33361\26693\25766\25759\25761\25755\25755\25750\25749\25744\25754\25739\25736\25739\25728\
25734\25728\25721\25717\25718\25721\25705\25706\25714\25711\25710\25695\25687\25698\25693\25685\2568
7\25664\25680\25674\25659\25666\25671\25654\25648\25645\25645\25636\25628\25626\25624\25638\25635\25
617\25615\25620\25617\25607\25604\25598\25592\25594\25604\25595\25575\25575\25572\25575\25577\25567\
25556\25561\25568\25550\25554\25541\25555\25548\25552\25574\25567\25579\25593\25579\25593\25589\2558
8\25594\25579\25579\25580\25591\25586\25569\25582\25572\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
e801#1#1^3ÊFV|
C|1|I|0|I|
Roche Diagnostics
R|4|^^^16013//not^^16013/1|233.7228^31339\31326\31328\31323\31323\31339\31330\31313\31328\31334\3132
4\31322\31332\31328\31322\31316\31318\31326\31322\31330\31324\31332\31324\31311\31320\31319\31309\31
326\31317\31310\31314\31317\31327\31308\31311\31303\31314\31311\31321\31319\31320\31316\31314\31314\
31330\31302\31324\31317\31301\31316\31319\31315\31308\31316\31328\31296\31328\31303\31297\31291\3129
0\31312\31301\31310\31315\31317\31301\31310\31311\31302\31300\31324\31303\31313\31317\31322\31302\31
297\31297\31307\1116\2391\6532\8865\10490\11727\12734\13563\14278\14917\15471\15971\16407\16833\1719
4\17528\17812\18092\18341\18563\18752\18927\19092\19266\19406\19537\19660\19782\19901\19997\20107\20
202\20302\20382\20464\20562\20622\20695\20786\20832\20892\20971\21027\21098\21138\21197\21261\21313\
21349\21396\21441\21508\21550\21590\21610\21657\21696\21750\21774\21839\21854\21892\21919\21963\2198
2\22005\22023\21977\21924\21877\21853\21829\21797\21791\21768\21782\21810\21837\21885\21948\22014\22
070\22117\22143\22147\22150\22203\22216\22235\22249\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\ÛSER|||F||bmserv^|20150415172021|20150415173854|e801^1^MU1#e801
#1#1^3ÊFC|
C|1|I|0|I|
R|5|^^^16013//not^^16013/1|14450.00|count|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^|20150415172021|201504
15173854|e801^1^MU1#e801#1#1^3^PMT|
C|1|I|0|I|
L|1|N|
Roche Diagnostics
204 Quality control uploads
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 (p. 131)
Realtime quality control upload

quality control upload.
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|20160919093722|20101019094737|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

quality control upload measured from the standby bottle.
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|
Standby^1|
C|1|I|0|I|
L|1|N|
Roche Diagnostics
Batch quality control upload

This section shows an example of an ASTM batch quality
control upload.
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|
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.
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|
Standby^1|
C|1|I|0|I|
L|1|N|

e 801 quality control upload with raw data
This section shows an e 801 quality control upload with
raw data values.
P|1|
O|1|PC U2^171399^2|0^30011^5^^QC^SC^not|^^^17001^1|R||||||Q||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^17001/1/not|9.40|μIU/mL||||F||bmserv^SYSTEM|20150416095321|20150416101213|e801^1^MU1#e801#1#1
^3^2769^Current|
C|1|I|0|I|
R|2|^^^17001/1/not|147108.5|count||||F||bmserv^|20150416095321|20150416101213|e801^1^MU1#e801#1#1^3^
EFS^Current|
C|1|I|0|I|
R|3|^^^17001/1/not|-112.146|count||||F||bmserv^|20150416095321|20150416101213|e801^1^MU1#e801#1#1^3^
EFV^Current|
C|1|I|0|I|
EFC^Current|
C|1|I|0|I|
PMT^Current|
C|1|I|0|I|
Roche Diagnostics
206 Quality control uploads
O|1|PC U2^171399^2|0^30011^5^^QC^SC^not|^^^17001^1|R||||||Q||||1||||||||||F|
C|1|I|^^^^|G|
R|1|^^^17001/1/not|9.26|μIU/mL||||F||bmserv^SYSTEM|20150416095309|20150416101214|e801^2^MU1#e801#1#2
^4^2770^Current|
C|1|I|0|I|
EFS^Current|
C|1|I|0|I|
R|3|^^^17001/1/not|-112.252|count||||F||bmserv^|20150416095309|20150416101214|e801^2^MU1#e801#1#2^4^
EFV^Current|
C|1|I|0|I|
EFC^Current|
C|1|I|0|I|
PMT^Current|
C|1|I|0|I|
L|1|N|
Roche Diagnostics
Calibration result uploads

This section shows examples of ASTM calibration result
uploads.
C-module calibration result upload

This section shows example of ASTM c-module
calibration result uploads.
M|1|PCR|bmserv|^^^8685|MU1#c701#1#1|16|0|22851^4^22866^2^0^\24786^-361^24149^-362^0^\^^^^^\^^^^^\^^^
^^\^^^^^|
L|1|N|
M|1|PCR|bmserv|^^^8685|MU1#c701#1#1|16|0|22045^4^22237^6^0^\24134^-372^23966^-361^0^\^^^^^\^^^^^\^^^
^^\^^^^^|
L|1|N|
M|1|PCR|bmserv|^^^8717|MU1#c701#1#1|16|0|956^31^962^40^0^\8100^6814^8147^6849^0^\^^^^^\^^^^^\^^^^^\^
^^^^|
L|1|N|
ISE-module calibration result upload

This section shows examples of ASTM ISE-module
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|
M|1|ICR|bmserv|MU1#ISE#1#2|Valid|Valid|Valid|0^0^0^0^0^0^0^0^0^0|0^0^0^0^0^0^0^0^0^0|0^0^0^0^0^0^0^0
^0^0|-37.9^-42.6^-35.3^-38.0^58.4^144.15^143.45^0.0^59.4^-0.45|-38.7^-51.9^-31.2^-41.3^56.3^5.15^4.6
3^0.0^57.3^-0.04|131.3^134.6^126.2^130.1^-47.7^93.93^99.57^0.0^-48.3^1.43|
L|1|N|
E-module calibration result upload

This section shows examples of ASTM e-module
e 602 examples
Roche Diagnostics
208 Calibration result uploads
FÔ^\YÔ^\BÔ^|936.337^888.767\39609.680^39716.950|||||20101018175819|
L|1|N|
FÔ^\YÔ^\BÔ^|839.413^797.173\38293.490^38596.120|||||20101018175844|
L|1|N|
e 801 examples:
M|1|ECR|bmserv|^^^17001|LotCalibration|MU1#e801#1#2|243001||0|178191|O|IÔ^\MÔ^\SÔ^\R^1.00^\DÔ^\L
^^\FÔ^\YÔ^\BÔ^|25604^25982^^||||||
M|2|ECR|bmserv|^^^17001|LotCalibration|MU1#e801#1#2|243001||0|178191|O|IÔ^\MÔ^\SÔ^\R^1.00^\DÔ^\L
^^\FÔ^\YÔ^\BÔ^|570^570^^|||||| L|1|N|
M|1|ECR|bmserv|^^^16030|ContainerCalibration|MU1#e801#1#2|173030||0|178611|O|IÔ^\MÔ^\SÔ^\R^0.862^
\DÔ^\L^^\FÔ^\YÔ^\BÔ^|86954^85778^^||||||
M|2|ECR|bmserv|^^^16030|ContainerCalibration|MU1#e801#1#2|173030||0|178611|O|IÔ^\MÔ^\SÔ^\R^0.862^
\DÔ^\L^^\FÔ^\YÔ^\BÔ^|588^591^^|||||| L|1|N|
Roche Diagnostics
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
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.
Request for currently active results

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.
Host:
H|\^&|12345||cobas 8000^1.04|||||host|RSREQ|P|1|20101020075900|
Q|1|^S1^321015||||||||||F|

L|1|N|
DM:
O|1|321015|0^50071^1^^S1^SC^not|^^^8717^1|R|20101019174209|20101019174209||||N||||1||||||||||F|
C|1|I|C1^C2^C3^C4^C5|G|
80627|c701^1^MU1#c701#1#1^6^77|
L|1|N|
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:
Q|1|^S1^321015|||||||||||
L|1|N|
DM:
Roche Diagnostics
210 Result request from host and the data manager result upload
O|1|321015|0^50071^1^^S1^SC^not|^^^990^1\^^^991^1\^^^8717^1|R|20101019174209|20101019174209||||N||||
1||||||||||F|
C|1|I|C1^C2^C3^C4^C5|G|
4439|ISE^2^MU1#ISE#1#2^4^128|
4515|ISE^1^MU1#ISE#1#1^3^125|
174403|ISE^1^MU1#ISE#1#1^3^126|
174439|ISE^2^MU1#ISE#1#2^4^129|
547|c701^1^MU1#c701#1#1^6^77|
80627|c701^1^MU1#c701#1#1^6^77|
L|1|N|
Result request but no results

from the host, where the data manager does not have any
results for the sample.
Host:
Q|1|^S1^321016|||||||||||
L|1|N|
DM:
<No Reply>
Result request but sample not found

from the host, where the data manager does not have
record of the sample.
Host:
Q|1|^S1^NOT_A_SAMPLE|||||||||||
L|1|N|
DM:
<No Reply>
Roche Diagnostics
Result request with a sequence number

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:
Q|1|^S1^^1031||||||||||F|
L|1|N|
DM:
O|1||1031^50101^3^^S1^SC^not|^^^8413^1\^^^8571^1\^^^8706^1|R|20110711093311|20110711093311||||N||||1
||||||||||F|
C|1|I|^^^^|G|
R|1|^^^8413/1/not|15|g/dL|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20111212104600|20111212104600|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\ÛSER|||F||bmserv^SYSTEM|20111212104600|20111212104600|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\ÛSER|||F||bmserv^SYSTEM|20111212104600|20111212104600
|c702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|
L|1|N|

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|\^&|12345||cobas 8000^1.02|||||host|RSREQ|
P|1|20121018135001|
Q|1|^S1^321071||||||||||F|
L|1|N|
DM:
P|1||||^||||O|1|321071|0^54312^2^^S1^SC^not|^^^8413^1\^^^8571^1|R|20121018134635|20121018134635||||N
||||1||||||||||F|C|1|I|^^^^|G|
R|1|^^^8413/1/not|12.08|g/dL|^TECH\^NORM\^CRIT\ÛSER|||F||bmserv^SYSTEM|20121017151615|2012101715161
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\ÛSER|||F||bmserv^SYSTEM|20121017151915|20121017151915
|c702^2^MU1#c702#1#2^7^193|
C|1|I|0|I|
Roche Diagnostics
212 Result request from host and the data manager result upload
L|1|N|
Roche Diagnostics
Order query from the host

This section shows examples of ASTM test selection
queries (or order queries) from the host to the data
manager.
Order query for all tests

This section shows an example of an ASTM order query
for all tests on a sample.
Host:
H|\^&|||cobas 8000^1.04|||||host|TSREQ|P|1|
Q|1|^S1^321015|||||||||||
L|1|N|
DM:
O|1|321015||^^^990^1\^^^991^1\^^^8717^1|||||||O||||1||||||||||F|
C|1|I|C1^C2^C3^C4^C5|G|
L|1|N|
Order query for all open tests

for open tests on a sample.
Host:
Q|1|^S1^321015||||||||||O|
L|1|N|
DM:
O|1|321015||^^^990^1\^^^991^1|||||||O||||1||||||||||F|
C|1|I|C1^C2^C3^C4^C5|G|
L|1|N|
Order query but no open tests

for all open tests on a sample, but the data manager does
not have any open orders on the sample.
Host:
Roche Diagnostics
214 Order query from the host
Q|1|^S1^321016||||||||||O|
L|1|N|
DM:
O|1|321016|||||||||O||||1||||||||||F|
C|1|I|^^^^|G|
L|1|N|
Order query but sample not found

for all open tests on a sample, but the data manager does
not have any record of the sample.
Host:
Q|1|^S1^NOT_EXISTING|||||||||||
L|1|N|
DM:
P|1||||^||||
O|1|NOT_EXISTING|||||||||O||||1||||||||||F|
C|1|I|^^^^|G|
L|1|N|
Order query with sample identified by sequence number

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:
Q|1|^S1^^1013||||||||||O|
L|1|N|
DM:
O|1||1013|^^^8413^1\^^^8571^1\^^^8706^1|||||||O||||1||||||||||F|
C|1|I|Comm1^Comm2^Comm3^Comm4^Comm5|G|
L|1|N|
Roche Diagnostics
HL7 reference
10 HL7 protocol...........................................................................................................217
11 HL7 text content ...................................................................................................221
12 HL7 acknowledgment handling......................................................................275
13 HL7 communication examples ........................................................................285
Roche Diagnostics
217
Table of contents
HL7 protocol 10
This chapter presents the lower layers of the HL7

protocol, as used by cobas® 8000 data manager.
In this chapter 10
Overview of HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Physical communication . . . . . . . . . . . . . . . . . . . . . . . . 220
10 HL7 protocol
Roche Diagnostics
218
Table of contents
10 HL7 protocol
Roche Diagnostics
HL7 protocol 219
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.
10 HL7 protocol
Roche Diagnostics
220 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
w The HL7 data framed according to the HL7 standard

10 HL7 protocol
Roche Diagnostics
221
Table of contents
HL7 text content 11

HL7 field definitions
This section describes all the HL7 fields used in messages

sent to or from cobas® 8000 data manager.
In this chapter 11
HL7 messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Messages sent only by the data manager. . . . . . . 223
Messages sent only by the host . . . . . . . . . . . . . . . 224
Messages sent by either data manager or the
host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
HL7 segment description . . . . . . . . . . . . . . . . . . . . . . . 226
Message Header Segment - MSH . . . . . . . . . . . . . . . . 227
Message Acknowledgment Segment - MSA . . . . . . . 229
Patient Identification Segment - PID . . . . . . . . . . . . . . 230
Specimen Segment - SPM . . . . . . . . . . . . . . . . . . . . . . 231
SPM in test selections, patient results and quality
control results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
11 HL7 text content
SPM in calibration results . . . . . . . . . . . . . . . . . . . . 234
Specimen Container Detail Segment - SAC . . . . . . . . 235
Observation Request Segment - OBR . . . . . . . . . . . . . 236
Timing Quantity Segment - TQ1 . . . . . . . . . . . . . . . . . . 238
Observation Result Segment - OBX (for patient
results) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Observation Result Segment - OBX (for QC results). 245
Observation Result Segment - OBX (for calibration
results) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Measurement of c-module photometric Calibration
Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Roche Diagnostics
222
Table of contents
Measurement of ISE Calibration Results . . . . . . . . . . . 253

Measurement of e-module immunological
Calibration Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Calibration alarm flags. . . . . . . . . . . . . . . . . . . . . . . . . . 257
Test Code Detail Segment - TCD . . . . . . . . . . . . . . . . . 258
Substance Identifier Segment - SID. . . . . . . . . . . . . . . 259
Comment Segment - NTE . . . . . . . . . . . . . . . . . . . . . . . 260
Types of comment segment . . . . . . . . . . . . . . . . . . 260
Query Parameter Segment - QPD (for a test
selection inquiry) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Query Parameter Segment - QPD (for a Result
Query) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Query Parameter Segment - QPD (for an Order
Query) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Response Control Parameter Segment - RCP . . . . . . 268
Equipment Detail Segment - EQU (from host to data
manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Equipment Detail Segment - EQU (from data
manager to host) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Equipment Command Segment - ECD . . . . . . . . . . . . 270
Inventory Detail Segment - INV . . . . . . . . . . . . . . . . . . 273
11 HL7 text content
Roche Diagnostics
HL7 text content 223
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
(p. 76).
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]}(a)
{NTE}
}(b)
}(c)
11 HL7 text content
Calibration data MSH OUL^R22^PCUPL Reports calibration results.
{ OUL^R22ÎCUPL
SPM OUL^R22ÊCUPL
OBR
OBX
SID
}
Equipment Status MSH ESUÛ01 Information about the status of an
Update EQU instrument, sent either unsolicited
or in response to an Equipment
Status Request.
Equipment MSH INUÛ05 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
(a) For messages containing patient results from the ISE module, no SID segment is sent.
Roche Diagnostics
224 HL7 messages
(b) There may only be multiple OBX segments per OBR in data point result messages.
(c) 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.

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Û07 Instructs data manager to mask or
EQU unmask certain tests.
{
ECD
}
Equipment Status MSH ESRÛ02 Request for information about
Request EQU instrument status.
The data manager responds to this
message with an Equipment Status
Update.
Equipment MSH INRÛ06 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:
Order query (p. 77)
(p. 83).
11 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

Acknowledge MSH ACK HL7 Application Acknowledge for incoming
MSA orders
Test Selection MSH OMLÔ33 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](a)
OBR
}]
Test Selection MSH OMLÔ33 Test selection sent by the data manager as
Information SPM response to an order query.
(from data manager if [SAC]
sample found) [{
[TQ1](b)
OBR
}]
Test Selection MSH OMLÔ33 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
(a) TQ1 Segments must be identical for all OBR Segments.
(b) TQ1 Segments must be identical for all OBR Segments.
11 HL7 text content
Roche Diagnostics
226 HL7 segment description
HL7 segment description

This section describes the content of the HL7 fields used
in communications between the host and the
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
11 HL7 text content
Roche Diagnostics
Message Header Segment - MSH

This segment occurs at the front of every message, and
shows the sender and receiver and other important
general information about the message.
Host and DM columns indicate whether the data is

Required or Optional when sent from the Host or data
manager respectively.
MSH|^~\&|cobas 8000||host||20090402173655||OUL^R22|13007||2.5||||ER||UNICODE UTF-8|
Field Value Host DM Description

MSH-1 | R R Field separator, fixed value = vertical bar [124]
MSH-2 ^~\& R R Delimiter definitions, fixed value:
o ^ Component (or sub-field) delimiter = caret [94]
o ~ Repeat delimiter = tilde [126]
o \ Escape character = backslash [92] (not supported)
o & Sub-component (or sub-sub-field) delimiter = ampersand [38]
A carriage return (ASCII 13) marks the end of each segment.
MSH-3 String - R Sending application, by default: cobas 8000
u To edit this, see Identifying the data manager application to the host (p. 101).
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-7 DateTime O O Date and time message created.
For a calibration message, this contains the datetime of the calibration.
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Ô33
o OUL^R22
o EACÛ07
o OUL^R22^PCUPL (c-module, or Photometric, Calibration Result)
o OUL^R22ÎCUPL (ISE Calibration Result)
11 HL7 text content
o OUL^R22ÊCUPL (e-module, or Immunology, Calibration Result)
o ESUÛ01ÊSU_U01 (Equipment Status Message)
o ESRÛ02ÊSR_U02 (Automated Equipment Status Request)
o INUÛ05ÎNU_U05 (Inventory Update Message)
o INRÛ06ÎNR_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.).
y Message header segment - MSH
Roche Diagnostics
228 Message Header Segment - MSH

MSH-12 2.5 O R Version ID for HL7 version used, fixed value string.
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 (p. 275).
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
11 HL7 text content
Roche Diagnostics
Message Acknowledgment Segment -

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

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
(p. 275).
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 (p. 109).
y Message acknowledgment segment - MSA
11 HL7 text content
Roche Diagnostics
230 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|SH25111965M|||Doe^John||19651125|M
PID|1||||^|||

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-5 Complex O O Patient last name and first name: Two string components, each max. 30 characters
long:
Last_name^First_name
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
patient sex.
unknown sex.
11 HL7 text content

the host.
Roche Diagnostics
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
(p. 234).
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 (p. 231).
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|||^^^^|||20100503142217||||||||||SC|
When identifying the sample by sequence number:
SPM||^1031||S1||not|||||P|||^^^^|||20110715085411||||||||||SC
For a quality control result: 11 HL7 text content

SPM||PNU^123456^301^20160913^27||S1||not|||||Q|||^^^^|||20160903142217||||||||||SC|

SPM-1 Field contains no data.
y Specimen Segment - SPM, in test selections, patient results and quality control results
Roche Diagnostics
232 Specimen Segment - SPM

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
Quality control material
For quality control material, Name^LotÎDÊxpDate^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 (p. 234).
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
11 HL7 text content
S2 Urine
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
For QC samples, the host should disregard any value in this field.
Roche Diagnostics

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-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-14 Complex O O Specimen description in format:
C1^C2^C3^C4^C5
o C1 Sample Comment 1. String with up to 30 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-17 DateTime O O Specimen collection date / time. (YYYYMMDDHHMMSS)
11 HL7 text content
SPM-27 String O R Container type.
o SC Standard cup
o MC Micro cup
o FBT1 False Bottom Tube 1
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 (p. 57)
Roche Diagnostics
234 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^888888^901^1^20111130|||||||||C^P|

SPM-2 Complex - O/R Identifier for the sample.
For c-module and e-module calibration materials,
Level^Lot^Code^CountÊxpDate
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-4 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Î ISE module Calibration
CÊ E-module (Immunological) Calibration
11 HL7 text content

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

SAC-1 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
11 HL7 text content
Roche Diagnostics
236 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Înc|||||||A
An OBR is created for every normal test and every

cobas e flow test. For a normal 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.

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.
y Observation request segment - OBR
11 HL7 text content
Roche Diagnostics

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 (p. 79).
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
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.
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.
11 HL7 text content
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
238 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|

TQ1-1 1 O R Set ID. Fixed value number.
TQ1-2 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
11 HL7 text content
Roche Diagnostics
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 normal test and every

cobas e flow test. For a normal 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.
u For details of how the data manager uses OBX with
quality control results, see Observation Result
Segment - OBX (for QC results) (p. 245).
calibration results, see Observation Result Segment -
OBX (for calibration results) (p. 249).
Patient result examples

OBX|1||990||0.99|mmol/L|^TECH~^NORM~^CRIT~< 0ÛSER||||C|||20101020095905|bmserv^SYSTEM||128|ISE^2^MU
1#ISE#1#2^4|20101020095921|
OBX|3||8717||1^-0.02|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||C|||20101019175614|bmserv^SYSTEM||77|c701^1^M
U1#c701#1#1^6|20101019180627|
An observation result segment for a result below the

EP17-A level of detection:
OBX|1||989||2.1|mmol/L|^TECH~12 - 144^NORM~^CRIT~ÛSER|HU|||F|||20100621084348|bmserv^SYSTEM||28|ISE
^1^MU1#ISE#1#1^3|20100621084404| 11 HL7 text content
An observation result segment for a result from a
cobas e flow test:
OBX|2||Formula1||3.64|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F||||^|||e801^0^MU1#e801#4#0^22|201401061535
51|
Roche Diagnostics
240 Observation Result Segment - OBX (for patient results)
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~ÛSER||||F|||20150414140223|bmserv^||EFS|e801^2^MU1#e801#1#2^4|2015041414
2055|

OBX-1 Number - R Set ID. The first segment in a set has the value 1. For each subsequent
segment in the set, this value increments by 1.
OBX-2 Field contains no data.
OBX-3 String - R The test code. (Observation identifier, or Application code.) This identifies
the test or analyte which this message relates to.
A cobas e flow test can contain an internally-calculated formula result.
Therefore, in the case of a cobas e flow test, this field can contain the
name of this formula. This field can also contain the host code assigned to
this formula, if the Assign host code per reported lab unit option is
enabled.
u For more information about host code assignment, see Assignment of
host codes to cobas e flow test results (p. 112)
y Observation Result Segment - OBX (for patient results)
11 HL7 text content
Roche Diagnostics

OBX-5 Complex - R Result value.
The result values are only transmitted for patient and QC results.
For quantitative results from ISE and e-modules, the components take the
following values:
o ReportableResult The quantitative result
o AdditionalResultValues Empty or a qualitative flag (see below)
A missing or suppressed quantitative result is sent as 7 spaces. (ASCII 32 /
0x20).
For quantitative results from c-modules, only the ReportableResult
component is sent, without any other components or delimiters.
For qualitative results, the components take the following values:
o ReportableResult Empty or a qualitative flag (see below)
o AdditionalResultValues The quantitative result, like value for a
quantitative result. For e-module qualitative results this contains COI .
For missing qualitative results from c- and e-modules, 7 spaces (ASCII 32 /
0x20) are sent in both sub-components.
For raw data/data point results, the components take the following values:
o AdditionalResultValues Data point values
The qualitative flags contain the following values:
o For c-modules and ISE modules: an integer code from -2 to 3 inclusive.
o For e-modules: an integer code -1 (non-reactive), 0 (border line), 1
(reactive).
o 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 (p. 411)
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.
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) 11 HL7 text content
Roche Diagnostics

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~ÛSER
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”
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) (p. 245)or Observation Result Segment - OBX (for
calibration results) (p. 249).
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
11 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
Roche Diagnostics

OBX-11 String - R Result status
o F First run result, or QC or calibration result
o C Corrected result
o M Manually-edited result
o X Calculated test, but test could not be calculated (for example,
divided by zero)
OBX-14 DateTime - R Pipetting time, in other words, the time that is considered to be when the
test was started.
Note: For manually-performed and calculated tests, this field is empty.
OBX-15 Complex - R Active operators in the format:
Each component is a string.
o Instrument operator
o Datamanager operator
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.
For raw data and data point results, contains one of the following codes:
o EFS Effective signal
o EFV Effective voltage
o EFC Effective current
o PMT PMT spike
11 HL7 text content
Roche Diagnostics

OBX-18 Complex - R Measurement unit ID, identifying the module that performed the test.
ModuleType^SubModuleÂnalyticalUnitIDÎnstrumentID^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 result from a submodule.
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:
host (p. 115).
OBX-18.4 Number - R Instrument Instrument number in data manager (A specific identifier
OBX-19 DateTime - O Time at which result is available. In some cases, this field is empty.
11 HL7 text content
Roche Diagnostics
Observation Result Segment - OBX (for QC

results)
This section describes how the data manager uses the
observation result segment (OBX) in a result report
message to send the results of quality control tests.
patient results, see Observation Result Segment - OBX
(for patient results) (p. 239).
calibration results, see Observation Result Segment -
OBX (for calibration results) (p. 249).
QC result example
OBX|1||8685||121|U/L|120^TARGET~25^SD||||F|||20111019111907|bmserv^SYSTEM||76|c701^1^MU1#c701#1#1^6^
Standby^1|20111019112922|
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|

OBX-3 String - R The test code. (Observation identifier, or Application code) This identifies
the test or analyte which this message relates to.
y Observation Result Segment - OBX (for QC results)
11 HL7 text content
Roche Diagnostics
246 Observation Result Segment - OBX (for QC results)

OBX-5 Complex - R Result value.
The result values are only transmitted for patient and QC results.
For quantitative results from ISE and e-modules, the components take the
following values:
o AdditionalResultValues Empty or a qualitative flag (see
below)
A missing or suppressed quantitative result is sent as 7 spaces. (ASCII 32 /
0x20).
For quantitative results from c-modules, only ReportableResult is
sent, without any other sub-components.
For qualitative results, the components take the following values:
o ReportableResult Empty or a qualitative flag (see below)
o AdditionalResultValues The quantitative result, like value for a
quantitative result. For e-module qualitative results this contains COI .
For missing qualitative results from c- and e-modules, 7 spaces (ASCII 32 /
0x20) are sent in both sub-components.
For raw data/data point results, the components take the following values:
o AdditionalResultValues Data point values
The qualitative flags contain the following values:
o For c-modules and ISE modules: an integer code from -2 to 3 inclusive.
o For e-modules: an integer code -1 (non-reactive), 0 (border line), 1
(reactive).
o 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 (p. 411)
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.
OBX-6 String - R Units of measurement used for measuring the result
11 HL7 text content
Roche Diagnostics

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ÛPPER
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ÛPPER
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)
tilde “ ~ ”. If a range is not defined, the RangeDefinition is blank.
OBX-11 String - R Result status
o F For QC result
OBX-14 DateTime - R Pipetting time, in other words, the time that is considered to be when the
test was started.
Note: For manually-performed and calculated tests, this field is empty.
OBX-15 Complex - R Active operators in the format:
11 HL7 text content
Each component is a string.
o Instrument operator
o Datamanager operator
OBX-17 Number - O Calibration ID as an integer number. This is a unique identifier of the
calibration that the result refers to as it is sent by the instrument.
Sent only if available. It is empty for results that do not have a calibration,
for example, calculated and manual results.
Roche Diagnostics
248 Observation Result Segment - OBX (for QC results)

OBX-18 Complex - R Measurement unit ID, identifying the module that performed the test.
ModuleType^SubModuleÂnalyticalUnitIDÎnstrumentID^
Bottle^SBNo
ISE ,
c702 or
e801
DM Results that cannot be attributed to a module.
manager but that cannot be attributed to
a module
analyzer series that cannot be mapped to an
actual measuring submodule, for example,
sample short.
Default:
host (p. 115).
OBX-18.4 Number - R Instrument Instrument number in data manager (A specific identifier
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.
with 1.
11 HL7 text content
Roche Diagnostics
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
(p. 239).
u For details of OBX with QC results, see Observation
Result Segment - OBX (for QC results) (p. 245).
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^Standby^1|20111019091
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|20100316105741|
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|20101018175819|

OBX-3 String - R The test code (application code). This identifies the test or analyte which
this message relates to.
OBX-5 String - R Measurement values.
u For photometric calibration results, see Measurement of c-module
11 HL7 text content
photometric Calibration Results (p. 252).
u For ISE calibration results, see Measurement of ISE Calibration
Results (p. 253).
If suppression of results outside the technical limit is enabled,
suppressed results are sent as 7 spaces.
OBX-6 Field contains no data (for calibration results).
OBX-8 String - O Calibration alarm flags.
u For details see Calibration alarm flags (p. 257).
y Observation Result Segment - OBX (for calibration results)
Roche Diagnostics
250 Observation Result Segment - OBX (for calibration results)

OBX-11 F - O Result status.
o F For calibration result
OBX-15 String - R This is the username the operator used to log into the control unit.
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.
11 HL7 text content
Roche Diagnostics

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 (p. 115).
Complex - R For c-module (photometric) or e-module (immunological):
Measurement unit ID, identifying the module that performed the test.
ModuleType^SubModuleÂnalyticalUnitIDÎnstrumentID
^Bottle^SBNo
ISE ,
c702 or
e801
DM Results that cannot be attributed to a
module.
manager but that cannot be attributed
to a module
analyzer series instrument that cannot be
mapped to an actual measuring submodule,
for example, sample short.
Default:
Instrument#ModuleType#Position#SubModul
e
host (p. 115).
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
the internal position of the module in the machine.)
11 HL7 text content
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.
with 1.
Reserved field, only for c-module (photometric)
measurements, otherwise empty.
Roche Diagnostics
252 Measurement of c-module photometric Calibration Results
Measurement of c-module photometric

Calibration Results
For a Photometric Calibration Result from a c-module, the
measurement result field (OBX-5) contains the following
components.
SD^STD
Subcomponent Description
SD Number Standard deviation value data.
STD Complex Absorbance values, (number types).
Format:
Absorbance&
FirstAbsorbance&
FirstInitialAbsorbance&
SecondAbsorbance&
SecondInitialAbosorbance&
Prozone Value
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||20101019091421||OUL^R22^PCUPL|||2.5||||ER||UNICODE UTF-8|

SPM||1^999999^901^1^20120131|||||||||C^P|
OBR|1|||8685|
OBX|1||8685||0^3&4&22851&2&22866&|||16|||F||||bmserv||75|c701^1^MU1#c701#1#1^6^Current|2010101909142
1|
SID||
SPM||2^153314^401^1^20120131|||||||||C^P|
OBR|2|||8685|
OBX|2||8685||0^-362&-361&24786&-362&24149&|||16|||F||||bmserv||75|c701^1^MU1#c701#1#1^6^Current|2010
1019091421|
SID||
11 HL7 text content
Roche Diagnostics
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.
Data Complex Test calibration analytical data.
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.
11 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
254 Measurement of ISE Calibration Results
Complete example ISE calibration result The following is a complete example of a calibration from
message an ISE module.
MSH|^~\&|cobas 8000||host||20100316105742||OUL^R22ÎCUPL|270||2.5||||
ER||UNICODE UTF-8|
SPM|||||||||||CÎ|
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
SID||
SPM|||||||||||CÎ|
OBR|2|||990|
OBX|2||990||Type-A^0&0&0&0&0&0&0&0&0&0^-34.2&-45.5&-24.8&-34.5&56.3&4.76&4.70&0.0&56.2&-0.17|||Valid
|||F||||bmserv||38|ISE^1^MU1#ISE#1#1^3|20100316105742|
SID||
SPM|||||||||||CÎ|
OBR|3|||991|
OBX|3||991||Type-A^0&0&0&0&0&0&0&0&0&0^136.4&138.5&130.6&134.1&-44.9&89.0&100.3&0.0&-45.1&0.7|||Vali
SID||
11 HL7 text content
Roche Diagnostics
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Ûnit^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
MaxSignal String o true if violation Qualitative and quantitative
CalibratorFactor Number Decimal value Quantitative
Deviation String o true if violation Qualitative and quantitative
Slope String o true if violation Qualitative
MinAcceptDiff String o true if violation Quantitative
SystemError String o true if violation Qualitative and quantitative
SignalVal1&SignalVal2 Complex Signal value, in two decimal Qualitative and quantitative
subcomponents:
SignalVal1&SignalVal2 11 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
256 Measurement of e-module immunological Calibration Results
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||20111118175844||OUL^R22ÊCUPL|14268||2.5||||ER||UNICODE UTF-8|

SPM||2^158941^1^None^20111119|||||||||CÊ|
OBR|1|||1|
SID|1^^ÂSY^18^0|157328|5|
SPM||1^158941^1^None^20111119000000|||||||||CÊ|
OBR|2|||1|
OBX|2||1||Valid^false^false^false^1.064^false^^false^false^839.413&797.173^^^^^|||LotCalibration|||F
||||bmserv||26|e602^2^MU1#e602#2#2^10^Current|20111118175844|
SID|1^^ÂSY^18^0|157328|5|
11 HL7 text content
Roche Diagnostics
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
11 HL7 text content
Roche Diagnostics
258 Test Code Detail Segment - TCD
Test Code Detail Segment - TCD

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

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 internally-calculated
formula.
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
11 HL7 text content
Roche Diagnostics
Substance Identifier Segment - SID

The data manager uses the substance identifier segment
to identify the reagents used in a test, when sending the
host a result report message.
Patient upload from a c-module (photometric):
SID|8706^^784648^R1^2^0|231478|5|
Calibration result from an e-module (Immunology):
SID|1^^ÂSY^14^0|156369|
For messages containing patient results from the ISE

module, no SID segment is sent.

SID-1 Complex - O/R Test code / Method Identifier. Takes the format:
Test^Type^Code^ReagentType^PositionÊxpiry
This field is empty for ISE calibration results.
SID-1.1 String - O/R Test Testcode (or Application Code). This is the code number the
host uses for identifying the test or analyte to test for.
SID-1.2 String - O/R Type Type of the test, if available.
SID-1.3 Number - O/R Code Reagent code. For calibration results from a c- or e-module,
this is empty.
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)
11 HL7 text content
REF Reference (ISE - QC results)
SID-1.5 Number - O/R Position Reagent Position on Disk
SID-1.6 Number - O/R Expiry Expiration flag:
o 0 = not expired
o 1 = expired
SID-2 String - O Lot number of the reagent used. Not used for ISE-module calibration
results, nor with non-Roche material.
SID-3 String - O Serial number of the reagent used. Not used for ISE-module calibration
results, nor with non-Roche material.
y Substance identifier segment - SID
q Note that R1-R3 might not all be present on a c-

module (photometric).
Roche Diagnostics
260 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^20090402172605|G|
There will always be an instrument flag sent with the

result report message. In the case of a result with no
alarm flag (zero), the segment will be as follows:
NTE|1|I|0|I|
This is “NTE-one-i-zero-i”.

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 (p. 260).
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.
11 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Ûser^Date
Text String Comment text

User String User who entered the comment
Date String Creation date and time in datetime format
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 .
Roche Diagnostics
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.
Two additional data alarms are available for the main

result of a cobas e flow test:
o eFlow.E^Standard alarm for e801
workflow tests
• CalcError (EP17-A error alarm for
cobas e flow tests)
u For details of possible error flags, see Data alarms
(p. 335)
11 HL7 text content
Roche Diagnostics
262 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), and is requesting a
sample ID from the host:
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|
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.
QPD-4 Field contains no data.
QPD-5 String - R Rack ID, as visible on control unit
QPD-6 String - R Position on rack
11 HL7 text content
y Query parameter segment - QPD - for a test selection inquiry
Roche Diagnostics

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
S4 Supernatant
S5 Other fluids
S6 Whole blood
S8 Hemolysate (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
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 (p. 57)
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
11 HL7 text content
Roche Diagnostics
264 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

QPD-1 RSREQ R - Message name, fixed string RSREQ .
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 (p. 51).
u For details of using result and order queries with limited sample
lifetimes or expired sample IDs, see:
Order and result queries with limited sample lifetime (p. 83).
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
QPD-4 String O - Selection mode
11 HL7 text content
o (empty)
All results
o F
Final results
y Query parameter segment - QPD - for result query
Roche Diagnostics

QPD-10 String O/R - Rack type as assigned to a specific sample type on the cobas® 8000
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.
lifetimes (p. 65).
S1 Serum / Plasma
S2 Urine
S4 Supernatant
S5 Other fluids
S6 Whole blood
manager).
Subsequent fields contain no data.
y Query parameter segment - QPD - for result query
11 HL7 text content
Roche Diagnostics
266 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|

QPD-1 TSREQ R - Message name, fixed string TSREQ.
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.
lifetimes (p. 65).
Order query (p. 77)
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
QPD-4 String O - Selection mode
11 HL7 text content
o (empty)
All requested tests
o O
(Capital O) Open. (Only test selections with no results yet)
y Query parameter segment - QPD - for an order query
Roche Diagnostics

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.
lifetimes (p. 65).
S1 Serum / Plasma
S2 Urine
S4 Supernatant
S5 Other fluids
S6 Whole blood
manager).
Subsequent fields contain no data.
y Query parameter segment - QPD - for an order query
11 HL7 text content
Roche Diagnostics
268 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|

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
11 HL7 text content
Roche Diagnostics
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|20090402173655|

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
11 HL7 text content
Roche Diagnostics
270 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ÂLL|
ECD||LK|||989^P^MU1#e602#1#1ÂLL|
ECD||LK|||989^T^MU1#ISE#1#1ÂLL|

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-5 Complex R - This field specifies the parameters of the command.
TestCode^MaskTypeÛnit_IDÂLL
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
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
(p. 115).
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
11 HL7 text content
Roche Diagnostics
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Ôperation^Hitachi|
EQU|DM#DM#1#2|20130217075453|ESÊ-STOPPED^LECIS^21^Shutdown^Hitachi|

EQU-1 String - R Identifier for the equipment. Takes the format:
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Înstrument
stateÎnstrument state descriptionÎnstrument 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.
11 HL7 text content
state u For a complete list of instrument-defined state values,
see Instrument-defined states (p. 271)
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 (p. 271)
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
272 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
11 HL7 text content
Roche Diagnostics
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ÔK_STATUS|
INV|8707|NW^NOT_AVAILABLE_WARNING|

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ÔK_STATUS
y Inventory detail segment - INV
11 HL7 text content
Roche Diagnostics
274
11 HL7 text content Inventory Detail Segment - INV
Roche Diagnostics
275
Table of contents
HL7 acknowledgment handling 12
This chapter explains how cobas® 8000 data manager

handles HL7 acknowledgment messages.
In this chapter 12
Acknowledgment flags in messages from the data
manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Inquiry for test selections . . . . . . . . . . . . . . . . . . . . 278
Result report patient. . . . . . . . . . . . . . . . . . . . . . . . . 278
Result report quality control . . . . . . . . . . . . . . . . . . 279
Result report calibration data . . . . . . . . . . . . . . . . . 280
Test selection upload from data manager to host 280
12 HL7 acknowledgment handling

Acknowledgment message from data manager
to host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Acknowledgment flags sent in response to host
messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Result query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Order query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Test selection download . . . . . . . . . . . . . . . . . . . . . 283
Acknowledgment message . . . . . . . . . . . . . . . . . . . 284
Roche Diagnostics
276
Table of contents
Roche Diagnostics
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

u For details of how to configure the application
acknowledge level of the data manager, see HL7
acknowledgment handling settings (p. 106).
The code in MSH-16 instructs the receiver whether to

send an application acknowledgment reply. Four levels of
acknowledgment are supported, as 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).
If the data manager cannot send a result report message

because of a low-level error, such as a disconnected
cable, the results are marked in the column Host Upload
Status as “Failed”.
The data manager only displays the outcome of the most

recent attempt to send results.
Roche Diagnostics
278 Acknowledgment flags in messages from the data manager
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. The data manager currently does not respond to any value returned.
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.
Result report patient

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

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

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

“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

> System message.
> System alarms.
• the data manager marks the results in “Upload status”
as “Failed”.
Roche Diagnostics
280 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.

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

> System message.
> System alarms.
Test selection upload from data manager to host

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

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

> System message.
> 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.
Roche Diagnostics
282 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
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Ô33 ).
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. (p. 327).
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
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
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.

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

Always (AL) Indicates success. Indicates an error, Not sent Not sent
segment.
Success (SU) Indicates success. Not sent Not sent Indicates unspecified
error.
Error (ER) Not sent Indicates an error, Not sent Indicates success.
segment.
Never (NE) Not sent Not sent Not sent Supported.
y Acknowledgment codes sent in response to a test selection download
Roche Diagnostics
284 Acknowledgment flags sent in response to host messages
Acknowledgment message
The data manager never replies to an acknowledgment
message.
Roche Diagnostics
285
Table of contents
HL7 communication examples 13
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 13
Test selection inquiry and download . . . . . . . . . . . . . . 289
Test selection inquiry for routine rack . . . . . . . . . . 289
Test selection inquiry for STAT rack . . . . . . . . . . . . 289
Routine rack (AL) with acknowledgment . . . . . . . 290
Routine rack invalid test (ER) . . . . . . . . . . . . . . . . . 290
13 HL7 communication examples

Test selection inquiry no sample found . . . . . . . . . 291
Test selection inquiry with a sequence number . . 292
Patient result upload messages . . . . . . . . . . . . . . . . . . 293
Single patient result upload . . . . . . . . . . . . . . . . . . 293
Batch upload all previous results . . . . . . . . . . . . . . 293
Batch upload all current results . . . . . . . . . . . . . . . 294
Batch upload of current results sample short . . . 295
No result as sample short . . . . . . . . . . . . . . . . . . . . 296
Result outside user range . . . . . . . . . . . . . . . . . . . . 296
Result outside normal range . . . . . . . . . . . . . . . . . . 296
cobas e flow test EP17-A message with flag . . . . 297
cobas e flow test EP17-A message with data
alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Sample with multiple cobas e flow tests and
embedded tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
cobas e flow test with formula or variable result . 300
cobas e flow test with non-reported embedded
tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
cobas e flow test formula result with data alarm
and non-reported embedded tests . . . . . . . . . . . . 302
Numeric test result . . . . . . . . . . . . . . . . . . . . . . . . . . 303
cobas e flow test result with custom host codes . 303
Qualitative and cut-off index result messages . . . . . . 305
Roche Diagnostics
286
Table of contents
Qualitative/cut-off index result for normal test. . . 305

Qualitative/cut-off index result for
cobas e flow test. . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Embedded test result with qualitative result in
cobas e flow test. . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
cobas e flow test with quantitative and
qualitative result . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Raw data and data point result messages . . . . . . . . . 308
e 602 result message with data point values . . . . 308
e 801 result message with raw data. . . . . . . . . . . . 308
e 801 result message with raw data and data
points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
e 801 result message with raw data and
instrument alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Quality control result upload messages . . . . . . . . . . . 313
Batch QC from c-module. . . . . . . . . . . . . . . . . . . . . 313
Batch QC from c-module standby bottle. . . . . . . . 313
Realtime QC from c-module . . . . . . . . . . . . . . . . . . 314
Realtime QC from c-module standby bottle . . . . . 314
QC results from e-module . . . . . . . . . . . . . . . . . . . . 314
Calculated QC result message . . . . . . . . . . . . . . . . 315
Calculated QC result flagged with generic alarm 315
Calculated QC result flagged with out-of-range
alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Quality control result with raw data . . . . . . . . . . . . 316
Symmetric quality control results message. . . . . . 316
Asymmetric quality control results message . . . . 317
Calibration result upload messages. . . . . . . . . . . . . . . 319
C-module calibration results. . . . . . . . . . . . . . . . . . 319

ISE-module calibration results . . . . . . . . . . . . . . . . 319
E-module calibration results . . . . . . . . . . . . . . . . . . 320
Masking messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Result requests from the host. . . . . . . . . . . . . . . . . . . . 323
Request for all results . . . . . . . . . . . . . . . . . . . . . . . 323
Request for active results . . . . . . . . . . . . . . . . . . . . 324
No results found . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Sample not found . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Result request with a sequence number. . . . . . . . 325
Result request with an expired sample . . . . . . . . . 326
Order requests from the host . . . . . . . . . . . . . . . . . . . . 327
Request for all tests . . . . . . . . . . . . . . . . . . . . . . . . . 327
Request for open tests. . . . . . . . . . . . . . . . . . . . . . . 327
No tests found. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Sample not found . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Order request with a sequence number . . . . . . . . 328
Instrument status and test availability messages . . . . 329
Test availability update . . . . . . . . . . . . . . . . . . . . . . . 329
Test availability request . . . . . . . . . . . . . . . . . . . . . . 329
Instrument status update. . . . . . . . . . . . . . . . . . . . . 330
Instrument status request . . . . . . . . . . . . . . . . . . . . 330
Roche Diagnostics
Test availability update for available

cobas e flow test. . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Test availability update for unavailable
cobas e flow test. . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Roche Diagnostics
288
Roche Diagnostics
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.
Test selection inquiry for routine rack

This section shows an example of an HL7 test selection
inquiry for a routine rack.
DM:
MSH|^~\&|cobas 8000||host||20101020091052||TSREQ|15161||2.5||||ER||UNICODE UTF-8|
QPD|TSREQ|15161|321070||50094|2||||S1|SC|R1|R|
RCP|I|1|R|
Host:
MSH|^~\&|host||cobas 8000||20090508135730||OMLÔ33|38749||2.5||||ER||UNICODE UTF-8
PID|1|PatID3|||Lastname^Firstname||19881231|F
SPM||321070||S1||not||||||||Comm1^Comm2^Comm3^Comm4^Comm5|||20101020122000||||||||||SC
SAC||||||||||50094|2
TQ1|1||||||||R
OBR|1|||990^|||||||A
TQ1|1||||||||R
OBR|2|||991^|||||||A
TQ1|1||||||||R
OBR|3|||8781^|||||||A
TQ1|1||||||||R

OBR|4|||8717Înc|||||||A
Test selection inquiry for STAT rack

inquiry for a STAT rack.
DM:
QPD|TSREQ|15164|321040||40002|3||||S1|SC|R1|S|
RCP|I|1|R|
Host:
SAC||||||||||4000232
TQ1|1||||||||S
OBR|1|||990^|||||||A
TQ1|1||||||||S
OBR|2|||991^|||||||A
TQ1|1||||||||S
OBR|3|||8781^|||||||A
Roche Diagnostics
290 Test selection inquiry and download
TQ1|1||||||||S
OBR|4|||8717Înc|||||||A
Routine rack (AL) with acknowledgment

inquiry for a routine sample, with the test selection
download. The host requests an acknowledgment (level
AL) and the data manager replies.
DM:
QPD|TSREQ|15161|321070||50094|2||||S1|SC|R1|R|
RCP|I|1|R|
Host:
MSH|^~\&|host||cobas 8000||20090508135730||OMLÔ33|38777||2.5||||AL||UNICODE UTF-8
SAC||||||||||50094|2
TQ1|1||||||||R
OBR|1|||990^|||||||A
TQ1|1||||||||R
OBR|2|||991^|||||||A
TQ1|1||||||||R
OBR|3|||8781^|||||||A
TQ1|1||||||||R
OBR|4|||8717Înc|||||||A
DM:
MSH|^~\&|cobas 8000||host||20101020132118||ACK|15831||2.5||||NE||UNICODE UTF-8|
MSA|AA|38777||
Routine rack invalid test (ER)

inquiry, and the host’s test selection download. In this test
selection download there is an invalid sample ID, and the
data manager replies with an acknowledgment that
informs the host of the error.
DM:
QPD|TSREQ|15161|321070||50094|2||||S1|SC|R1|R|
RCP|I|1|R|
Host:
SAC||||||||||50094|2
TQ1|1||||||||R
Roche Diagnostics
OBR|1|||990^|||||||A
TQ1|1||||||||R
OBR|2|||991^|||||||A
TQ1|1||||||||R
OBR|3|||8781^|||||||A
TQ1|1||||||||R
OBR|4|||INVALIDÎnc|||||||A
DM:
MSA|AE|38777|ORA-20001: Validation error|
Test selection inquiry no sample found

inquiry, but the host cannot find the sample.
DM:
QPD|TSREQ|15167|321071||50094|3||||S1|SC|R1|R|
RCP|I|1|R|
Host:
PID|1|
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 (p. 190)and .STAT sample
test selection inquiry and download (p. 190)
Roche Diagnostics
292 Test selection inquiry and download
Test selection inquiry with a sequence number

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:
QPD|TSREQ|563067|^1031||50203|3||||S1|SC|R1|R|
RCP|I|1|R|
Host:
MSH|^~\&|host||c8000DM||20110715081133||OMLÔ33|227442||2.5||||ER||UNICODE UTF-8
PID|1|M820092K|||Lastname^Firstname||19730416|F
SPM||^1031||S1||not|||||P|||^^^^|||20110715085411||||||||||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
Patient result upload messages

In the examples in this section the data manager uploads
HL7 patient results.
Single patient result upload

This section shows an example of a single HL7 patient
result upload.
Note that the result abnormal flag is blank as there is no

reference range defined.

PID|1||||^||||
SPM||321042||S1||not|||||P|||^^^^|||20101019094904||||||||||SC|
SAC||||||||||50011|4|
OBR|1|||8685|
TQ1|1||||||||R|
OBX|1||8685||47|U/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20101019100810|bmserv^SYSTEM||75|c701^1^MU1#c701#
1#1^6|20101019101824|
TCD|8685|1|
SID|8685^^564957^R1^9^0|616478|924|
SID|8685^^564957^R3^9^0|616478|924|
NTE|1|I|0|I|

Batch upload all previous results
This section shows a batch upload of all previous results
for a sample.

MSH|^~\&|cobas 8000^1.04||host||20101020111635||OUL^R22|15593||2.5||||ER||UNICODE UTF-8|

PID|1|PatID1|||Lastname^Firstname||19451231|M|
SPM||321015||S1||not|||||P|||C1^C2^C3^C4^C5|||20101019174209||||||||||SC|
SAC||||||||||50071|1|
OBR|1|||990|
TQ1|1||||||||R|
OBX|1||990||0.91|mmol/L|^TECH~^NORM~^CRIT~< 0ÛSER||||F|||20101019174423|bmserv^SYSTEM||128|ISE^2^MU
1#ISE#1#2^4|20101019174439|
TCD|990|1|
NTE|1|I|23ÎSE Sample range over|I|
OBR|2|||990|
TQ1|1||||||||R|
1#ISE#1#1^3|20101019174515|
TCD|990|1|
OBR|3|||990|
Roche Diagnostics
TQ1|1||||||||R|
1#ISE#1#1^3|20101020095751|
TCD|990|1|
OBR|4|||990|
TQ1|1||||||||R|
1#ISE#1#2^4|20101020095921|
TCD|990|1|
OBR|5|||991|
TQ1|1||||||||R|
OBX|5||991||252.89|mmol/L|^TECH~^NORM~^CRIT~< 0ÛSER||||F|||20101019174347|bmserv^SYSTEM||126|ISE^1^
MU1#ISE#1#1^3|20101019174403|
TCD|991|1|
OBR|6|||991|
TQ1|1||||||||R|
OBX|6||991||256.84|mmol/L|^TECH~^NORM~^CRIT~< 0ÛSER||||C|||20101019174423|bmserv^SYSTEM||129|ISE^2^
MU1#ISE#1#2^4|20101019174439|
TCD|991|1|
OBR|7|||991|
TQ1|1||||||||R|
MU1#ISE#1#1^3|20101020095751|
TCD|991|1|
OBR|8|||991|
TQ1|1||||||||R|
MU1#ISE#1#2^4|20101020095921|
TCD|991|1|
OBR|9|||8717|
TQ1|1||||||||R|
OBX|9||8717||-0.04|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20101019174533|bmserv^SYSTEM||77|c701^1^MU1
#c701#1#1^6|20101019175547|
TCD|8717|1|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
NTE|1|I|27^PANIC value over (lower) Technical Limit|I|
OBR|10|||8717|
TQ1|1||||||||R|
OBX|10||8717||-0.02|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||C|||20101019175614|bmserv^SYSTEM||77|c701^1^MU
1#c701#1#1^6|20101019180627|
TCD|8717|Inc|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
Batch upload all current results

This section shows a batch upload of all current results.
Roche Diagnostics

MSH|^~\&|cobas 8000^1.04||host||20101020111632||OUL^R22|15591||2.5||||ER||UNICODE UTF-8|

SAC||||||||||50071|1|
OBR|1|||990|
TQ1|1||||||||R|
1#ISE#1#2^4|20101020095921|
TCD|990|1|
OBR|2|||991|
TQ1|1||||||||R|
MU1#ISE#1#2^4|20101020095921|
TCD|991|1|
OBR|3|||8717|
TQ1|1||||||||R|
OBX|3||8717||-0.02|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||C|||20101019175614|bmserv^SYSTEM||77|c701^1^MU1
#c701#1#1^6|20101019180627|
TCD|8717|Inc|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
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.

PID|1||||^||||
SPM||321042||S1||not|||||P|||^^^^|||20101006162241||||||||||SC|
SAC||||||||||50011|4|
OBR|1|||989|
TQ1|1||||||||R|
OBX|1||989|| |mmol/L|^TECH~^NORM~^CRIT~ÛSER||||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|
1#ISE#1#1^3|20101018173829|
TCD|990|1|
OBR|3|||991|
TQ1|1||||||||R|
1#ISE#1#1^3|20101018173829|
TCD|991|1|
Roche Diagnostics
No result as sample short

This section shows an example of an HL7 result message,
where the measurement could not be done as the sample
was short.

PID|1||||^||||
SPM||321042||S1||not|||||P|||^^^^|||20101006162241||||||||||SC|
SAC||||||||||50011|4|
OBR|1|||991|
TQ1|1||||||||R|
1#ISE#1#1^3|20101018173829|
TCD|991|1|
Result outside user range

This section shows an example of an HL7 patient result
outside the user-defined reference range.

PID|1||||^||||
SPM||321671||S1||not|||||P|||^^^^|||20101018191906||||||||||SC|
SAC||||||||||50054|5|
OBR|1|||991|
TQ1|1||||||||R|
MU1#ISE#1#1^3|20101018192558|
TCD|991|1|
NTE|1|I|0|I|
Result outside normal range

This section shows an example of an HL7 result upload
below the normal reference range.
MSH|^~\&|cobas 8000||host||20100609022505||OUL^R22|8277||2.5||||AL||UNICODE UTF-8|

PID|1|ES06516622121998|||Lastname^Firstname||19330813|M|
SPM||123||S1||not|||||P|||^^^^|||20100604235148||||||||||SC|
SAC||||||||||50063|2|
OBR|1|||989|
TQ1|1||||||||R|
OBX|1||989||2.1|mmol/L|^TECH~9 - 144^NORM~^CRIT~ÛSER|L|||F|||20100621084348|bmserv^SYSTEM||28|ISE^1
^MU1#ISE#1#1^3|20100621084404|
TCD|989|1|
NTE|1|I|0|I|
TQ1|1||||||||R|
OBX|2||991||1.1|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20100621084348|bmserv^SYSTEM||28|ISE^1^MU1#ISE
#1#1^3|20100621084404|
TCD|991|1|
Roche Diagnostics
NTE|1|I|0|I|
OBR|3|||8717|
TQ1|1||||||||R|
OBX|3||8717||14.57|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20100621085921|bmserv^SYSTEM||168|c701^2^MU
1#c701#1#2^7|20100621090935|
TCD|8717|1|
NTE|1|I|0|I|
cobas e flow test EP17-A message with flag

For EP17-A range checking in cobas e flow test results,
two additional flags have been defined, which are sent in
the OBX-8 segment:
• HU (High Uncertainty)
• eFlow.W (generic cobas e flow test warning)
HL7 message with HU flag

PID|1||||^||||
SPM||20-EP-RC2||S1||not|||||P|||^^^^|||20131004130048||||||||||SC|
SAC|||||||||||0|
OBR|1|||21000|
TQ1|1||||||||R|
OBX|1||21000||3.12|μIU/mL|^TECH~^NORM~^CRIT~ÛSER|HU|||F|||20131004130056|bmserv^SYSTEM|||e801^1^MU1
#e801#4#1^14|20131004130056|
TCD|21000|1|
NTE|1|I|0|I|

HL7 message with generic warning
PID|1||||^||||
SPM||20-EP-RC8||S1||not|||||P|||^^^^|||20150115122522||||||||||SC|
SAC||||||||||50060|1|
OBR|1|||30109|
TQ1|1||||||||R|
OBX|1||30109||8.00|μIU/mL|^TECH~^NORM~^CRIT~ÛSER|eFlow.W|||F|||20150115122519|bmserv^SYSTEM|||e801^
1^MU1#e801#4#1^14|20150115122522|
TCD|30109|1|
NTE|1|I|0|I|
u For details of EP17-A flags, see EP17-A and the result

cobas e flow test EP17-A message with data alarm

This section shows a result message for a
cobas e flow test with embedded tests which have pre-
defined EP17-A ranges.
Roche Diagnostics
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. This
alarm overrides the CalcError alarm.
• If a result cannot be calculated, the result is displayed
as 7 blank spaces.
PID|1||||^||||
SPM||80-EP01||S1||not|||||P|||^^^^|||20140106121719||||||||||SC|
SAC|||||||||||0|
OBR|1|||30800|
TQ1|1||||||||R|
OBX|1||30800|| |mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F||||^SYSTEM|||e801^0^MU1#e801#4#0^22|201401
06121731|
TCD|30800|1|
NTE|1|I|eFlow.E^Standard alarm for e801 workflow tests|I|
OBX|2||Formula3||-5.50|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F||||^|||e801^0^MU1#e801#4#0^22|20140106121
731|
TCD|Formula3|1|
NTE|1|I|0|I|
OBX|3||20010|| |μIU/mL|^TECH~^NORM~^CRIT~ÛSER|HU|||F|||20140106121731|bmserv^SYSTEM|||e801^1^
MU1#e801#4#1^23|20140106121731|
TCD|20010|1|
NTE|1|I|0|I|
OBX|4||20040||5.00|μIU/mL|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106121731|bmserv^SYSTEM|||e801^1^MU1#e
801#4#1^23|20140106121731|
TCD|20040|1|
NTE|1|I|0|I|
OBX|5||20070||2.00|μIU/mL|^TECH~^NORM~^CRIT~ÛSER|HU|||F|||20140106121731|bmserv^SYSTEM|||e801^1^MU1
#e801#4#1^23|20140106121731|
TCD|20070|1|
NTE|1|I|0|I|
32|
TCD|Formula2|1|
NTE|1|I|0|I|
32|
TCD|Formula1|1|
NTE|1|I|0|I|
801#4#1^23|20140106121730|
TCD|20010|1|
NTE|1|I|0|I|
OBX|9||20130||1.00|g/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106121730|bmserv^SYSTEM|||e801^1^MU1#e801
#4#1^23|20140106121730|
TCD|20130|1|
NTE|1|I|0|I|
OBX|10||20060||3.00|μIU/mL|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106121730|bmserv^SYSTEM|||e801^1^MU1#
e801#4#1^23|20140106121730|
TCD|20060|1|
NTE|1|I|0|I|
Roche Diagnostics
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.

PID|1||||^||||
SPM||81003||S1||not|||||P|||^^^^|||20140106150953||||||||||SC|
SAC|||||||||||0|
OBR|1|||604|
TQ1|1||||||||R|
OBX|1||604||6.97|μIU/mL|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106151019|bmserv^SYSTEM|||e801^0^MU1#e80
1#4#0^22|20140106151019|
TCD|604|1|
OBX|2||20120||6.97|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106151019|bmserv^SYSTEM|||e801^1^MU1#e
801#4#1^23|20140106151019|
TCD|20120|1|
NTE|1|I|0|I|
OBX|3||20040||6.97|μIU/mL|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106151019|bmserv^|||e801^1^MU1#e801#4#
1^23|20140106151019|
TCD|20040|1|
NTE|1|I|0|I|
OBX|4||20130||6.97|g/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106151019|bmserv^|||e801^1^MU1#e801#4#1^2
3|20140106151019|
TCD|20130|1|
NTE|1|I|0|I|
OBX|5||20050||0.560|μIU/mL|^TECH~^NORM~^CRIT~ÛSER|HU|||F|||20140106151019|bmserv^|||e801^1^MU1#e801

#4#1^23|20140106151019|
TCD|20050|1|
NTE|1|I|0|I|
1^23|20140106151013|
TCD|20090|1|
NTE|1|I|0|I|
OBX|7||20140|| |μmol/L|^TECH~^NORM~^CRIT~ÛSER|HU|||F|||20140106151013|bmserv^|||e801^1^MU1#e8
01#4#1^23|20140106151013|
TCD|20140|1|
NTE|1|I|0|I|
OBR|2|||171|
TQ1|1||||||||R|
01#4#0^22|20140106151019|
TCD|171|1|
OBX|2||20120||0.560|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106151019|bmserv^|||e801^1^MU1#e801#4
#1^23|20140106151019|
TCD|20120|1|
NTE|1|I|0|I|
OBR|3|||213|
TQ1|1||||||||R|
01#4#0^22|20140106151019|
TCD|213|1|
Roche Diagnostics

OBX|2||20140|| |μmol/L|^TECH~^NORM~^CRIT~ÛSER|HU|||F|||20140106151013|bmserv^|||e801^1^MU1#e8
01#4#1^23|20140106151013|
TCD|20140|1|
NTE|1|I|0|I|
1^23|20140106151013|
TCD|20030|1|
NTE|1|I|0|I|
OBR|4|||24|
TQ1|1||||||||R|
OBX|1||24||1.07|nmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106151013|bmserv^SYSTEM||24|e602^1^MU1#e6
02#3#1^11|20140106151013|
TCD|24|1|
NTE|1|I|0|I|
OBR|5|||8060|
TQ1|1||||||||R|
OBX|1||8060||1.07|U/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106151013|bmserv^SYSTEM||402|c702^1^MU1#c7
02#1#1^6|20140106151013|
TCD|8060|1|
NTE|1|I|0|I|
OBR|6|||8435|
TQ1|1||||||||R|
OBX|1||8435||2.7|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106151013|bmserv^SYSTEM||424|c702^1^MU1#
c702#1#1^6|20140106151013|
TCD|8435|1|
NTE|1|I|0|I|
OBR|7|||8685|
TQ1|1||||||||R|
OBX|1||8685||1.07|U/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106151013|bmserv^SYSTEM||401|c702^1^MU1#c7
02#1#1^6|20140106151013|
TCD|8685|1|
NTE|1|I|0|I|
OBR|8|||8717|
TQ1|1||||||||R|
OBX|1||8717||1.07|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106151013|bmserv^SYSTEM||401|c702^1^MU1
#c702#1#1^6|20140106151013|
TCD|8717|1|
NTE|1|I|0|I|
cobas e flow test with formula or variable result

A cobas e flow test result can contain an internally
calculated formula or a variable value result in the
embedded tests. This section shows an example of a
result message with an internally calculated formula
result in one of the embedded tests. 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.

PID|1||||^||||
SPM||7006||S1||not|||||P|||^^^^|||20140106153539||||||||||SC|
SAC|||||||||||0|
Roche Diagnostics
OBR|1|||30300|
TQ1|1||||||||R|
#4#0^22|20140106153550|
TCD|30300|1|
NTE|1|I|0|I|
OBX|2||Formula1||3.64|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F||||bmserv^SYSTEM|||e801^0^MU1#e801#4#0^22|
20140106153551|
TCD|Formula1|1|
NTE|1|I|0|I|
OBX|3||20070||0.860|μIU/mL|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106153550|bmserv^SYSTEM|||e801^1^MU1#
e801#4#1^23|20140106153550|
TCD|20070|1|
NTE|1|I|0|I|
OBX|4||Qualitative1||16| |^TECH~^NORM~^CRIT~ÛSER||||F||||bmserv^SYSTEM|||e801^0^MU1#e801#4#0^22|201
40106153551|
TCD|Qualitative1|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
are sent.

PID|1||||^||||

SPM||81003||S1||not|||||P|||^^^^|||20140106150953||||||||||SC|
SAC|||||||||||0|
OBR|1|||171|
TQ1|1||||||||R|
01#4#0^22|20140106151019|
TCD|171|1|
OBX|2||20120||0.560|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106151019|bmserv^SYSTEM|||e801^1^MU1#
e801#4#1^23|20140106151019|
TCD|20120|1|
NTE|1|I|0|I|
OBX|3||20130|| |mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106151019|bmserv^SYSTEM|||e801^1^MU
1#e801#4#1^23|20140106151019|
TCD|20130|1|
NTE|1|I|0|I|
1#e801#4#1^23|20140106151019|
TCD|20080|1|
NTE|1|I|0|I|
1#e801#4#1^23|20140106151019|
TCD|20070|1|
NTE|1|I|0|I|
1#e801#4#1^23|20140106151019|
TCD|20010|1|
Roche Diagnostics
NTE|1|I|0|I|
cobas e flow test formula result with data alarm and non-
reported embedded tests
A cobas e flow test result is based on an embedded test
or formula. 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.
Two additional data alarms are available for the main

result:
• eFlow.E : standard alarm for e 801
cobas e flow tests
• CalcError : EP-17 calculation error 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.
If data alarms occur for both the main result test and any
other restricted test, then the alarm which occurred for

the main result test is assigned to the cobas e flow test.
This section shows an example result message from an

HIV DUO workflow, including a formula, a data alarm and
non-reported embedded tests.
MSH|^~\&|cobas 8000||host||20150409114843||OUL^R22|128807||2.5||||AL||UNICODE UTF-8|

PID|1|1|||Eins^|||U| SPM||200300||S1||not|||||P|||^^^^|||20150409101801|||||||||||
SAC||||||||||50098|1|
OBR|1|||15000|
TQ1|1||||||||R|
OBX|1||15000||-1|COI|^TECH~^NORM~^CRIT~ÛSER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|20150409114841|
TCD|15000|1|
NTE|1|I|eFlow.E^Standard alarm for e 801 cobas e flow tests|I|
OBX|2||HIVAgResult01||0.368|COI|^TECH~^NORM~^CRIT~ÛSER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|201504091
14841|
TCD|HIVAgResult01|1|
NTE|1|I|0|I|
OBX|3||16014|| |COI|^TECH~^NORM~^CRIT~ÛSER||||F|||20150409113010|bmserv^SYSTEM||2447|e801^1^M
U1#e801#1#1^3|20150409114842|
TCD|16014|1|
SID|16014^^1016014ÂSY^26^0|174998|182|
NTE|1|I|0|I|
OBX|4||16013|| |COI|^TECH~^NORM~^CRIT~ÛSER||||F|||20150409112958|bmserv^SYSTEM||2446|e801^2^M
U1#e801#1#2^4|20150409114830|
TCD|16013|1| SID|16013^^1016013ÂSY^27^0|174998|1438|
Roche Diagnostics
NTE|1|I|0|I|
Numeric test result

with a numeric test result.

PID|1||||^||||
SPM||81004||S1||not|||||P|||^^^^|||20140106152324||||||||||SC|
SAC|||||||||||0|
OBR|1|||24|
TQ1|1||||||||R|
OBX|1||24||0.760|nmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106152333|bmserv^SYSTEM||24|e602^1^MU1#e
602#3#1^11|20140106152333|
TCD|24|1|
NTE|1|I|0|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.
In this example, custom host codes have been assigned

to the formula and measurement unit values. The custom

host code for the formula is 90000, and the custom host
codes for the measurement units are D126 and D128.
u In these examples, the custom host code values have
been configured as described in Host code
assignment example (p. 114)
MSH|^~\&|cobas 8000||host||20141106161512||OUL^R22|201||2.5||||NE||UNICODE UTF-8|

PID|1||||^||||
SPM||86972887||S1||not|||||P|||^^^^|||20141106161410||||||||||SC|
SAC||||||||||50060|1|
OBR|1|||D128|
TQ1|1||||||||R|
OBX|1||D126||2.12|mg/dL|^TECH~^NORM~^CRIT~ÛSER||||F|||20141106161506|bmserv^SYSTEM|||e801^1^MU1#e80
1#4#1^14|20141106161509|
TCD|D126|1|
NTE|1|I|0|I|
OBX|2||90000||4.69|mg/dL|^TECH~^NORM~^CRIT~ÛSER||||F|||20141106161506|bmserv^SYSTEM|||e801^1^MU1#e8
01#4#1^14|20141106161509|
TCD|2|1|
SID|2^^1091963^R3^10^0|100304|16|
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.
Roche Diagnostics

PID|1||||^||||
SPM||86972887||S1||not|||||P|||^^^^|||20141106161410||||||||||SC|
SAC||||||||||50060|1|
OBR|1|||30982|
TQ1|1||||||||R|
OBX|1||21070||2.12|mg/dL|^TECH~^NORM~^CRIT~ÛSER||||F|||20141106161506|bmserv^SYSTEM|||e801^1^MU1#e8
01#4#1^14|20141106161509|
TCD|D126|1|
NTE|1|I|0|I|
OBX|2||Formula1||4.69|mg/dL|^TECH~^NORM~^CRIT~ÛSER||||F|||20141106161506|bmserv^SYSTEM|||e801^1^MU1
#e801#4#1^14|20141106161509|
TCD|2|1|
SID|2^^1091963^R3^10^0|100304|16|
NTE|1|I|0|I|
u For information about assigning host codes and

enabling this functionality, see Assignment of host
codes to cobas e flow test results (p. 112)
Roche Diagnostics
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.
Qualitative/cut-off index result for normal 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.

PID|1||||^||||
SPM||80-Result-QQ2||S1||not|||||P|||^^^^|||20140106134133||||||||||SC|
SAC|||||||||||0|
OBR|1|||95|
TQ1|1||||||||R|
OBX|1|CE|95||-1^3.12|COI|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106134142|bmserv^SYSTEM|||e602^1^MU1#e6
02#3#1^11|20140106134142|
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 3.12 is displayed in the Original
result column. Both results are sent to the host.

PID|1||||^||||
SPM||1_RF_WF_QL1||S1||not|||||P|||^^^^|||20140106143448||||||||||SC|
SAC|||||||||||0|
OBR|1|||22003|
TQ1|1||||||||R|
OBX|1|CE|22003||-1^3.12|COI|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106143501|bmserv^SYSTEM|||e801^0^MU1
#e801#4#0^22|20140106143501|
TCD|22003|1|
NTE|1|I|0|I|
OBX|2|NM|20020||4.53|μIU/mL|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106143501|bmserv^|||e801^1^MU1#e801#
4#1^23|20140106143501|
TCD|20020|1|
NTE|1|I|0|I|
OBX|3|NM|20010||4.53|μIU/mL|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106143501|bmserv^|||e801^1^MU1#e801#
4#1^23|20140106143501|
TCD|20010|1|
NTE|1|I|0|I|
OBX|4|NM|FormulaM||9.06|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F||||^|||e801^0^MU1#e801#4#0^22|2014010614
3501|
Roche Diagnostics
306 Qualitative and cut-off index result messages
TCD|FormulaM|1|
NTE|1|I|0|I|
OBX|5|NM|FormulaQL||6.24|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F||||^|||e801^0^MU1#e801#4#0^22|201401061
43502|
TCD|FormulaQL|1|
NTE|1|I|0|I|
OBX|6|CE|22002||1^1.24|COI|^TECH~^NORM~^CRIT~ÛSER||||F|||20140106143501|bmserv^|||e801^1^MU1#e801#4
#1^23|20140106143501|
TCD|22002|1|
NTE|1|I|0|I|
OBX|7|NM|FormulaQQ||4.90|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F||||^|||e801^0^MU1#e801#4#0^22|201401061
43502|
TCD|FormulaQQ|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 an embedded test with a

qualitative result as the main result. The result in this
example is a code with the value of 16, which is mapped
in the data manager to the result message "Avidity low".
Also, when the main result is a qualitative result, no value
is sent for the unit.

PID|1||||^||||
SPM||7007||S1||not|||||P|||^^^^|||20140106154413||||||||||SC|
SAC|||||||||||0|
OBR|1|||30400|
TQ1|1||||||||R|
OBX|1||30400||16| |^TECH~^NORM~^CRIT~ÛSER||||F||||^SYSTEM|||e801^0^MU1#e801#4#0^22|20140106154424|
TCD|30400|1|
NTE|1|I|0|I|
OBX|2||Formula1||1.09|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F||||bmserv^SYSTEM|||e801^0^MU1#e801#4#0^22|
20140106154424|
TCD|Formula1|1|
NTE|1|I|0|I|
#4#1^23|20140106154423|
TCD|20130|1|
NTE|1|I|0|I|
801#4#1^23|20140106154423|
TCD|20070|1|
NTE|1|I|0|I|
u For a list of result codes sent with qualitative results,

see Result message codes for cobas e flow tests
(p. 411)
Roche Diagnostics
cobas e flow test with quantitative and qualitative result

When the main result of a cobas e flow test is a
quantitative and qualitative 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 21, which is mapped to the result message “PCR
recommended”. In addition, the main result has the
numeric value 6.24.
The same applies if the record is a result of an embedded

test of the cobas e flow test.

PID|1||||^||||
SPM||7008||S1||not|||||P|||^^^^|||20140825093657||||||||||SC|
SAC||||||||||50060|1|
OBR|1|||21060|
TQ1|1||||||||R|
OBX|1||21060||21^6.24|μIU/mL|^TECH~^NORM~^CRIT~ÛSER||||F||||^SYSTEM|||DM^0^DM#DM#0#0^0|201408250937
02|
TCD|21060|1|
NTE|1|I|0|I|
OBX|2||MFQual||24|μIU/mL|^TECH~^NORM~^CRIT~ÛSER||||F||||^|||DM^0^DM#DM#0#0^0|20140825093702|
TCD|MFQual|1|
NTE|1|I|0|I|
1^14|20140825093700|
TCD|20020|2|
SID|20020^^1091963^R3^3^0|100304|14100|
NTE|1|I|0|I|

1^14|20140825093700|
TCD|20010|1|
SID|20010^^1091963^R3^3^0|100304|14100|
NTE|1|I|0|I|
Roche Diagnostics
308 Raw data and data point result messages
Raw data and data point result messages

The examples in this section show result messages
containing raw data and data point values.
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).
e 602 result message with data point values

message with data point values, generated by an e 602
module. (This example shows only the EFS portion of the
message.)

PID|1||||^||||
SPM||234031||S1||not|||||P|||^^^^|||20140707093721|||||||||||
SAC||||||||||50089|5|
OBR|1|||64|
TQ1|1||||||||R|
OBX|1||64||3.50|IU/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140707092617|bmserv^SYSTEM||0|e602^2^MU1#e602#
3#2^12|20140707092617|
TCD|64|1|
SID|64^^64ÂSY^4^0|175377|60703|
NTE|1|I|0|I|
OBR|2|||64|
TQ1|1||||||||R|
OBX|2||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~ÛSER||||F|||20140707092617|^||EFS|e602^2
^MU1#e602#3#2^12|20140707092617|
TCD|64|1|
NTE|1|I|0|I|
e 801 result message with raw data

In this section the data manager uploads HL7 patient
results with raw data values.
Roche Diagnostics
This section shows an example message for an e 801 test

with four raw data records: Effective-Signal (EFS),
Effective-Voltage (EFV), Effective-Current (EFC) and PMT
Spike (PMT).

PID|1||||^||||
SPM||00106||S1||not|||||P|||^^^^|||20150331080031|||||||||||
SAC||||||||||50096|3|
OBR|1|||15723|
TQ1|1||||||||R|
OBX|1||15723||1.36|μIU/mL|^TECH~^NORM~^CRIT~ÛSER||||F|||20150327142601|bmserv^SYSTEM||2455|e801^2^M
U1#e801#1#2^4|20150327144434|
TCD|15723|1|
SID|15723^^1015723ÂSY^30^0|141414|134|
NTE|1|I|0|I|
OBX|2||15723||22446.16|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20150327142601|bmserv^||EFS|e801^2^MU1#e
801#1#2^4|20150327144434|
TCD|15723|1|
NTE|1|I|0|I|
OBX|3||15723||-113.027|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20150327142601|bmserv^||EFV|e801^2^MU1#e
801#1#2^4|20150327144434|
TCD|15723|1|
NTE|1|I|0|I|
OBX|4||15723||240.8188|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20150327142601|bmserv^||EFC|e801^2^MU1#e
801#1#2^4|20150327144434|
TCD|15723|1|
NTE|1|I|0|I|
OBX|5||15723||13050.00|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20150327142601|bmserv^||PMT|e801^2^MU1#e
801#1#2^4|20150327144434|
TCD|15723|1|
NTE|1|I|0|I|

e 801 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.

PID|1||||^||||
SPM||100012||S1||not|||||P|||^^^^|||20150414162839|||||||||||
SAC||||||||||50103|3|
OBR|1|||17025|
TQ1|1||||||||R|
OBX|1||17025||40.2|pg/mL|^TECH~^NORM~^CRIT~ÛSER||||F|||20150414140223|bmserv^SYSTEM||2654|e801^2^MU
1#e801#1#2^4|20150414142055|
TCD|17025|1|
NTE|1|I|0|I|
Roche Diagnostics
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~ÛSER||||F|||20150414140223|bmserv^||EFS|e801^2^MU1#e801#1#2^4|2015041414
2055|
TCD|17025|1|
NTE|1|I|0|I|
OBX|3||17025||-117.799^33412&33425&33386&33377&33395&33399&33399&33401&33395&33401&33394&33402&33402
&33396&33392&33398&33402&33399&33396&33377&33395&33389&33393&33387&33379&33399&33382&33390&33389&333
72&33391&33380&33389&33385&33374&33374&33384&33392&33398&33374&33369&33371&33380&33376&33387&33380&3
3378&33384&33398&33390&33399&33377&33373&33381&33392&33378&33379&33384&33377&33373&33375&33360&33371
&33393&33378&33375&33366&33365&33349&33344&33367&33346&33355&33363&33369&33365&33374&33371&33356&333
58&26696&25686&25656&25647&25660&25656&25656&25653&25631&25650&25613&25616&25634&25622&25623&25626&2
5619&25610&25605&25601&25583&25572&25572&25582&25583&25568&25567&25571&25552&25550&25561&25552&25561
&25592&25554&25540&25542&25518&25520&25528&25527&25535&25522&25519&25520&25516&25501&25489&25507&254
97&25489&25490&25474&25477&25462&25479&25468&25461&25454&25456&25452&25445&25445&25435&25435&25419&2
5446&25413&25421&25436&25427&25413&25439&25441&25462&25454&25463&25475&25484&25498&25492&25481&25483
&25476&25468&25483&25483&25477&25458&25468&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~ÛSER||||F|||20150414140223|bmserv^||EFV|e801^2^MU1#e801#1#2^4|2015041414
2055|
TCD|17025|1|
NTE|1|I|0|I|
OBX|4||17025||240.5428^31487&31480&31478&31489&31496&31495&31476&31478&31493&31494&31475&31474&31491
&31489&31487&31489&31476&31488&31482&31468&31480&31494&31480&31483&31482&31485&31487&31478&31472&314
63&31467&31466&31478&31454&31468&31450&31455&31469&31470&31455&31464&31450&31476&31470&31454&31462&3
1462&31457&31462&31460&31467&31450&31451&31466&31453&31457&31471&31443&31453&31467&31470&31459&31454
&31463&31458&31450&31447&31459&31456&31453&31451&31453&31457&31474&31469&31461&31470&31461&31457&314
77&1819&2127&6099&8401&9998&11259&12257&13123&13896&14527&15073&15618&16175&16598&16959&17316&17598&
17876&18128&18332&18425&18609&18807&18929&19142&19262&19396&19512&19610&19738&19843&19956&20047&2016
2&20206&20294&20376&20444&20525&20575&20643&20708&20774&20863&20994&21031&21110&21153&21169&21253&21
288&21325&21368&21423&21475&21494&21548&21591&21637&21672&21710&21751&21806&21824&21863&21906&21916&
21888&21906&21873&21834&21782&21738&21758&21776&21791&21830&21860&21901&21970&22055&22091&22147&2217
8&22197&22202&22218&22243&22251&22283&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|co
unt|^TECH~^NORM~^CRIT~ÛSER||||F|||20150414140223|bmserv^||EFC|e801^2^MU1#e801#1#2^4|20150414142055|
TCD|17025|1|
NTE|1|I|0|I|
OBX|5||17025||12476.00|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20150414140223|bmserv^||PMT|e801^2^MU1#e
801#1#2^4|20150414142055|
TCD|17025|1|
NTE|1|I|0|I|
Roche Diagnostics
e 801 result message with raw data and instrument

alarms
This section shows a result message for the
cobas e flow test 31726, which has 2 embedded tests
(17194 and 17226).
Both embedded tests have raw data values, and the main
result of the cobas e flow test is based on the embedded
test 17194.
The embedded tests have been measured on instruments

with data alarms 66 and 67. Instrument alarm information
is sent in the NTE segments of each OBX. The information
consists of the alarm code and a description of the alarm.

PID|1||||^||||
SPM||8174ZZ||S1||not|||||P|||^^^^|||20140709092738||||||||||SC|
SAC||||||||||50060|1|
OBR|1|||31726|
TQ1|1||||||||R|
OBX|1||31726||1|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140709092850|bmserv^SYSTEM|||e801^1^MU1#e801
#4#1^14|20140709092850|
TCD|31726|1|
NTE|1|I|66^Current range check error|I|
OBX|2||31726||17|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20140709092850|bmserv^SYSTEM||EFS|e801^1^MU1#e
801#4#1^14|20140709092850|
TCD|31726|1|

OBX|3||31726||165|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20140709092850|bmserv^SYSTEM||EFV|e801^1^MU1#
e801#4#1^14|20140709092850|
TCD|31726|1|
OBX|4||31726||11|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20140709092850|bmserv^SYSTEM||EFC|e801^1^MU1#e
801#4#1^14|20140709092850|
TCD|31726|1|
OBX|5||31726||703|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20140709092850|bmserv^SYSTEM||PMT|e801^1^MU1#
e801#4#1^14|20140709092850|
TCD|31726|1|
OBX|6||17226||1|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20140709092853|bmserv^SYSTEM|||e801^1^MU1#e801
#4#1^14|20140709092853|
TCD|17226|50|
NTE|1|I|67^Sample hovering|I|
OBX|7||17226||18|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20140709092853|bmserv^SYSTEM||EFS|e801^1^MU1#e
801#4#1^14|20140709092853|
TCD|17226|1|
OBX|8||17226||166|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20140709092853|bmserv^SYSTEM||EFV|e801^1^MU1#
e801#4#1^14|20140709092853|
TCD|17226|1|
OBX|9||17226||12|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20140709092853|bmserv^SYSTEM||EFC|e801^1^MU1#e
801#4#1^14|20140709092853|
Roche Diagnostics
TCD|17226|1|
OBX|10||17226||704|count|^TECH~^NORM~^CRIT~ÛSER||||F|||20140709092853|bmserv^SYSTEM||PMT|e801^1^MU1
#e801#4#1^14|20140709092853|
TCD|17226|1|
Roche Diagnostics
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
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|
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.

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^St
andby^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
314 Quality control result upload messages
Realtime QC from c-module

This section shows an example of a realtime HL7 quality
control result from a c-module.
MSH|^~\&|cobas 8000||host||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.

PID|1|
SPM||PPU^150415^3^20160921^48||S1||not|||||Q|||^^^^|||||||||||||SC|
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|
QC results from e-module

This section shows examples of HL7 quality control
results from an e-module.

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ÂSY^18^0|157328|62769|
NTE|1|I|0|I|
Roche Diagnostics
Calculated QC result message

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

PID|1|
SPM||PC TIgG5^171961^22^20150228||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||||
OBR|1|||29000^|
TQ1|1||||||||R|
OBX|1||29000||1.83|μIU/mL|0.84^TARGET~0.14^SD||||F||||^SYSTEM|||e801^0^MU1#e801#4#0^22^Current|20140
106164342|
TCD|29000|1|
NTE|1|I|0|I|
u For more information about calculated QC, see the

cobas® 8000 data manager Operator’s Manual.
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.
MSH|^~\&|cobas 8000||host||20160930175241||OUL^R22^REAL|1317||2.5||||NE||UNICODE UTF-8|

PID|1|
SPM||PC HIV1^173233^5^20170631^65||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||||
OBR|1|||15000|
TQ1|1||||||||R|
OBX|1||15000||.339|COI|0.25^TARGET~||||F||||^SYSTEM|||e801^0^MU1#e801#1#0^2^Current|20160930175241|
TCD|15000|1|
NTE|1|I|eFlow.E^Standard alarm for e 801 cobas e flow tests|I|
Calculated QC result flagged with out-of-range alarm

If the calculated QC result is out of the defined ranges, an
out-of-range alarm is sent to the host.
The possible values for the out-of-range alarms are:

• 26^Technical limit over (upper)
• 27^Technical limit over (lower)
Roche Diagnostics

PID|1|
SPM||PC TIgG5^171961^2^20170528^69||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||||
OBR|1|||29000|
TQ1|1||||||||R|
OBX|1||29000||2.7|μIU/mL|0.84^TARGET~0.14^SD||||F||||^SYSTEM|||e801^0^MU1#e801#4#0^13^Current|201606
03145020|
TCD|29000|1|
NTE|1|I|26^Technical limit over (upper)|I|
Quality control result with raw data

This section shows an example of a quality control result
with raw data values, from an e 801 module.
MSH|^~\&|cobas 8000||host||20150408131226||OUL^R22^REAL|127309||2.5||||NE||UNICODE UTF-8|

PID|1|
SPM||CM01^151511^22^20151231||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC||||||||||30006|1|
OBR|1|||15721|
TQ1|1||||||||R|
OBX|1||15721||355|pg/mL|104^TARGET~10.4^SD||||F|||20150408125352|bmserv^SYSTEM||2677|e801^1^MU1#e801
#1#1^3^Current|20150408131225|
TCD|15721|1| SID|15721^^1015721ÂSY^8^0|131313|121|
NTE|1|I|0|I|
OBX|2||15721||28562.32|count|||||F|||20150408125352|bmserv^||EFS|e801^1^MU1#e801#1#1^3^Current|20150
408131225|
TCD|15721|1|
NTE|1|I|0|I|
OBX|3||15721||-116.997|count|||||F|||20150408125352|bmserv^||EFV|e801^1^MU1#e801#1#1^3^Current|20150
408131225|
TCD|15721|1|
NTE|1|I|0|I|
OBX|4||15721||240.7808|count|||||F|||20150408125352|bmserv^||EFC|e801^1^MU1#e801#1#1^3^Current|20150
408131225|
TCD|15721|1|
NTE|1|I|0|I|
OBX|5||15721||14112.00|count|||||F|||20150408125352|bmserv^||PMT|e801^1^MU1#e801#1#1^3^Current|20150
408131225|
TCD|15721|1|
NTE|1|I|0|I|
Symmetric quality control results message

Quality control results messages are sent to the host for
master QC results and copy QC results. Raw data for each
test is sent to the host.
Roche Diagnostics
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.

PID|1|
SPM||PC TIgG1^171956^7^20140228||S1||not|||||Q|||^^^^|||||||||||||SC|
SAC|||||||||||0|
OBR|1|||10444|
TQ1|1||||||||R|
OBX|1||10444||0.53|IU/mL|0.84^TARGET~0.14^SD||||F|||20140507113925|bmserv^SYSTEM||12|e801^1^MU1#e801
#4#1^14^Current|20140507113930|
TCD|10444|1|
SID|10444^^868723^R1^1^0|400|1238|
NTE|1|I|0|I|
OBX|2||10444||33626.40|count|^TARGET~^SD||||F|||20140507113925|^||EFS|e801^1^^14^Current|20140507113
925|
TCD|10444|1|
NTE|1|I|0|I|
OBX|3||10444||-120.656|count|^TARGET~^SD||||F|||20140507113925|^||EFV|e801^1^^14^Current|20140507113
925|
TCD|10444|1|
NTE|1|I|0|I|
OBX|4||10444||220.8216|count|^TARGET~^SD||||F|||20140507113925|^||EFC|e801^1^^14^Current|20140507113
925|
TCD|10444|1|
NTE|1|I|0|I|
OBX|5||10444||16155.00|count|^TARGET~^SD||||F|||20140507113925|^||PMT|e801^1^^14^Current|20140507113
925|
TCD|10444|1|
NTE|1|I|0|I|

u For more information about the copy QC concept, see
the cobas® 8000 data manager Operator’s Manual.
Asymmetric quality control results 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ÛPPER
• Without target value:
lowerrangevalue^LOWER~upperrangevalue
ÛPPER
Roche Diagnostics
Example OBX segment with target value

OBX|1||10444||0.53|IU/mL|0.84^TARGET~0.14^LOWER~0.14ÛPPER||||F|||20140507113925|bmserv^SYSTEM||12|e
801^1^MU1#e801#4#1^14^Current|20140507113930|
Example OBX segment without target value

OBX|1||10444||0.53|IU/mL|0.14^LOWER~0.14ÛPPER||||F|||20140507113925|bmserv^SYSTEM||12|e801^1^MU1#e8
01#4#1^14^Current|20140507113930|
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.
Roche Diagnostics
Calibration result upload messages

In the examples in this section, the data manager uploads
HL7 calibration results.
C-module calibration results

This section shows examples of HL7 calibration results
from a c module.
MSH|^~\&|cobas 8000||host||20111119091421||OUL^R22^PCUPL|14262||2.5||||ER||UNICODE UTF-8|

SPM||1^999999^901^1^20111121|||||||||C^P|
OBR|1|||8685|
|
SID|8685^^^^2^1|231478|5|
SPM||2^153314^401^1^20111201|||||||||C^P|
OBR|2|||8685|
OBX|2||8685||0^-362&-361&24786&-362&24149&|||0|||F||||bmserv||75|c701^1^MU1#c701#1#1^6^Current|20111
119091421|
SID|8685^^^^3^1|231480|9|
MSH|^~\&|cobas 8000||host||20111119091432||OUL^R22^PCUPL|14264||2.5||||ER||UNICODE UTF-8|

SPM||1^999999^901^1^20111121||||||||||C^P|
OBR|1|||8717|
OBX|1||8717||0^36&31&956&40&962&|||0|||F||||bmserv||77|c701^1^MU1#c701#1#1^6^Current|20111119091432|
SID|8717^^^^2^1|231478|5|
SPM||2^153314^401^1^20111121||||||||||C^P|

OBR|2|||8717|
9091432|
SID|8717^^^^3^1|231480|9|
ISE-module calibration results

from an ISE-module.
MSH|^~\&|cobas 8000||host||20101020110002||OUL^R22ÎCUPL|14265||2.5||||ER||UNICODE UTF-8|

SPM|||||||||||CÎ|
OBR|1|||989|
OBX|1||989||Type-A^0&0&0&0&0&0&0&0&0&0^-33.0&-37.9&-30.4&-33.2&60.0&144.59&143.56&0.0&60.2&-0.56|||V
alid|||F||||bmserv||130|ISE^1^MU1#ISE#1#1^3|20101020110002|
SID||
SPM|||||||||||CÎ|
OBR|2|||990|
OBX|2||990||Type-A^0&0&0&0&0&0&0&0&0&0^-34.9&-48.9&-27.3&-37.8&58.7&5.19&4.64&0.0&59.1&-0.05|||Valid
SID||
SPM|||||||||||CÎ|
OBR|3|||991|
Roche Diagnostics
320 Calibration result upload messages
OBX|3||991||Type-A^0&0&0&0&0&0&0&0&0&0^137.3&141.6&132.8&136.8&-50.0&97.42&99.75&0.0&-50.3&1.25|||Va
lid|||F||||bmserv||132|ISE^1^MU1#ISE#1#1^3|20101020110002|
SID||
MSH|^~\&|cobas 8000||host||20101020110008||OUL^R22ÎCUPL|14266||2.5||||ER||UNICODE UTF-8|

SPM|||||||||||CÎ|
OBR|1|||989|
OBX|1||989||Type-A^0&0&0&0&0&0&0&0&0&0^-37.9&-42.6&-35.3&-38.0&58.4&144.15&143.45&0.0&59.4&-0.45|||V
alid|||F||||bmserv||133|ISE^2^MU1#ISE#1#2^4|20101020110008|
SID||
SPM|||||||||||CÎ|
OBR|2|||990|
OBX|2||990||Type-A^0&0&0&0&0&0&0&0&0&0^-38.7&-51.9&-31.2&-41.3&56.3&5.15&4.63&0.0&57.3&-0.04|||Valid
SID||
SPM|||||||||||CÎ|
OBR|3|||991|
OBX|3||991||Type-A^0&0&0&0&0&0&0&0&0&0^131.3&134.6&126.2&130.1&-47.7&93.93&99.57&0.0&-48.3&1.43|||Va
lid|||F||||bmserv||135|ISE^2^MU1#ISE#1#2^4|20101020110008|
SID||
E-module calibration results

from an e-module.
e 602 examples
SPM||2^158941^1^None^20111119|||||||||CÊ|
OBR|1|||1|
SID|1^^ÂSY^18^0|157328|5|
SPM||1^158941^1^None^20111119|||||||||CÊ|
OBR|2|||1|
SID|1^^ÂSY^18^0|157328|5|

SPM||2^158941^1^None^20111119|||||||||CÊ|
OBR|1|||1|
SID|1^^ÂSY^18^0|157328|5|
SPM||1^158941^1^None^20111119|||||||||CÊ|
OBR|2|||1|
SID|1^^ÂSY^18^0|157328|5|
e 801 examples
MSH|^~\&|cobas 8000||host||20150331121143||OUL^R22ÊCUPL|2761||2.5||||NE||UNICODE UTF-8|
SPM||2^175949^17009^None^|||||||||CÊ|
OBR|1|||17009| OBX|1||17009||Valid^false^false^false^1.00^false^^false^false^27790&28697&&^|||LotCal
ibration|||F||||bmserv||2581|e801^1^MU1#e801#1#1^3^Current|20150331121143|
Roche Diagnostics
SID|17009^^ÂSY^6^0|132205|349| SPM||1^175949^17009^None^|||||||||CÊ|
OBR|2|||17009| OBX|1||17009||Valid^false^false^false^1.00^false^^false^false^95136&95024&&^|||LotCal
ibration|||F||||bmserv||2581|e801^1^MU1#e801#1#1^3^Current|20150331121143|
SID|17009^^ÂSY^6^0|132205|349|
MSH|^~\&|cobas 8000||host||20150330173918||OUL^R22ÊCUPL|1242||2.5||||NE||UNICODE UTF-8|

SPM||2^174843^15723^None^|||||||||CÊ|
OBR|1|||15723|
OBX|1||15723||Valid^false^false^false^0.929^false^^false^false^27976&28126&&^|||ContainerCalibration
SID|15723^^ÂSY^30^0|141414|134|
SPM||1^174843^15723^None^|||||||||CÊ|
OBR|2|||15723|
OBX|1||15723||Valid^false^false^false^0.929^false^^false^false^604&618&&^|||ContainerCalibration|||F
SID|15723^^ÂSY^30^0|141414|134|
Roche Diagnostics
322 Masking messages
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||20101007113655||EACÛ07|13010||2.5||||AL||UNICODE UTF-8|
EQU|1|20101007113600|
ECD|1234|LK|||989^P^MU1#ISE#1#1ÂLL|
DM:
MSA|AA|13010||
Unsuccessful masking message In this section the host sends a masking command, but
the module does not exist.
Host:
MSH|^~\&|host||cobas 8000||20101007113655||EACÛ07|13011||2.5||||AL||UNICODE UTF-8|
EQU|1|20101007113600|
ECD|1234|LK|||989^P^module_XÂLL|
DM:
MSA|AE|13011|Submodule (module_X) not found|
Roche Diagnostics
Result requests from the host

In the examples in this section the host sends result
requests.
! CAUTION
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.
Request for all results

In this section the host sends a request for all results for a
sample.
Host:
MSH|^~\&|host||cobas 8000||20100430105126||RSREQ|13007||2.5||||NE||UNICODE UTF-8|
QPD|RSREQ||321015|
DM:

SAC||||||||||50071|1|
OBR|1|||990|
TQ1|1||||||||R|
1#ISE#1#2^4|20101019174439|
TCD|990|1|
OBR|2|||990|
TQ1|1||||||||R|
1#ISE#1#1^3|20101019174515|
TCD|990|1|
OBR|3|||991|
TQ1|1||||||||R|
MU1#ISE#1#1^3|20101019174403|
TCD|991|1|
OBR|4|||991|
TQ1|1||||||||R|
MU1#ISE#1#2^4|20101019174439|
TCD|991|1|
OBR|5|||8717|
TQ1|1||||||||R|
Roche Diagnostics
324 Result requests from the host
OBX|5||8717||-0.04|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20101019174533|bmserv^SYSTEM||77|c701^1^MU1
#c701#1#1^6|20101019175547|
TCD|8717|1|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
OBR|6|||8717|
TQ1|1||||||||R|
#c701#1#1^6|20101019180627|
TCD|8717|Inc|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
Request for active results

In this section the host sends a request for active results
for a sample.
Host:
QPD|RSREQ||321015|F|
DM:
SAC||||||||||50071|1|
OBR|1|||8717|
TQ1|1||||||||R|
#c701#1#1^6|20101019180627|
TCD|8717|Inc|
SID|8717^^568316^R1^30^0|616731|674|
SID|8717^^568316^R3^30^0|616731|674|
No results found
for a sample, but the data manager cannot find any
results.
Host:
QPD|RSREQ||321016|F|
DM:
<No Reply>
Roche Diagnostics
Sample not found

for a sample, but the data manager cannot find any
record of the sample.
Host:
QPD|RSREQ||NOT_FOUND|F|
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:
QPD|RSREQ||^1031|
DM:
MSH|^~\&|cobas 8000||host||20110712133259||OUL^R22^BATCH|564847||2.5||||NE||UNICODE UTF-8|
PID|1|M820092K|||Lastname^Firstname||19730416|F|
SPM||^1031||S1||not|||||P|||^^^^|||20110711085411||||||||||SC|

SAC||||||||||50203|3|
OBR|1|||8413|
TQ1|1||||||||R|
OBX|1||8413||19|g/dL|^TECH~^NORM~^CRIT~ÛSER||||F|||20111212104600|bmserv^SYSTEM||193|c702^2^MU1#c70
2#1#2^7|20111212104600|
TCD|8413|1|
SID|8413^^784648^R1^2^0|231478|5|
SID|8413^^784648^R3^2^0|231478|5|
NTE|1|I|0|I|
OBR|2|||8571|
TQ1|1||||||||R|
OBX|2||8571||21|U/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20111212104600|bmserv^SYSTEM||193|c702^2^MU1#c702
#1#2^7|20111212104600|
TCD|8571|1|
SID|8571^^784648^R1^2^0|231478|5|
SID|8571^^784648^R3^2^0|231478|5|
NTE|1|I|0|I|
OBR|3|||8706|
TQ1|1||||||||R|
OBX|3||8706||23|mmol/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20111212104600|bmserv^SYSTEM||193|c702^2^MU1#c
702#1#2^7|20111212104600|
TCD|8706|1|
SID|8706^^784648^R1^2^0|231478|5|
SID|8706^^784648^R3^2^0|231478|5|
NTE|1|I|0|I|
Roche Diagnostics
326 Result requests from the host
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:
QPD|RSREQ||321071|F||||||S1
DM:
MSH|^~\&|cobas 8000||host||20121018133131||OUL^R22^BATCH|563326||2.5||||ER||UNICODE UTF-8|PID|1||||^
||||
SPM||321071||S1||not|||||P|||^^^^|||20121017153615||||||||||SC|
SAC||||||||||54312|2|
OBR|1|||8413|TQ1|1||||||||R|
OBX|1||8413||12.08|g/dL|^TECH~^NORM~^CRIT~ÛSER||||F|||20121017151615|bmserv^SYSTEM||193|c702^2^MU1#
c702#1#2^7|20121017151615|
TCD|8413|1|
SID|8413^^784648^R1^2^0|231478|5|SID|8413^^784648^R3^2^0|231478|5|
NTE|1|I|0|I|
OBR|2|||8571|
TQ1|1||||||||R|
OBX|2||8571||13.36|U/L|^TECH~^NORM~^CRIT~ÛSER||||F|||20121017151915|bmserv^SYSTEM||193|c702^2^MU1#c
702#1#2^7|20121017151915|
TCD|8571|1|
SID|8571^^784648^R1^2^0|231478|5|
SID|8571^^784648^R3^2^0|231478|5|
NTE|1|I|0|I|
Roche Diagnostics
Order requests from the host

In the examples in this section, the host sends order
requests.
Request for all tests

In this section the host sends a request for all tests for a
sample.
Host:
MSH|^~\&|host||cobas 8000||20100825132805||TSREQ|10001||2.5||||NE||UNICODE UTF-8|
QPD|TSREQ||321015|||||||S1|
RCP|I|1|R|
DM:
MSH|^~\&|cobas 8000||host||||OMLÔ33|15023||2.5||||ER||UNICODE UTF-8|
SPM||321015||S1||||||||||C1^C2^C3^C4^C5|
OBR||||990|
OBR||||991|
OBR||||8717|
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:
QPD|TSREQ||321015|O||||||S1|
RCP|I|1|R|
DM:
SPM||321015||S1||||||||||C1^C2^C3^C4^C5|
OBR||||8717|
No tests found
a sample, but the data manager does not find any tests.
Note that rack type is required in QPD-10.
Host:
QPD|TSREQ||321016|O||||||S1|
RCP|I|1|R|
Roche Diagnostics
328 Order requests from the host
DM:
SPM||321016||S1||||||||||^^^^|
Sample not found

a sample, but the data manager does not find the sample.
Host:
MSH|^~\&|host||cobas 8000^1.04||20100825132805||TSREQ|10001||2.5||||NE||UNICODE UTF-8|
QPD|TSREQ||NOT_EXISTING|||||||S1|
RCP|I|1|R|
DM:
MSH|^~\&|cobas 8000^1.04||host||||OMLÔ33|15028||2.5||||ER||UNICODE UTF-8|
SPM||NOT_EXISTING||S1||||||||||^^^^|
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:
QPD|TSREQ||^1031|||||||S1|
RCP|I|1|R|
DM:
MSH|^~\&|cobas 8000||host||||OMLÔ33|564825||2.5||||NE||UNICODE UTF-8|
SPM||^1031||S1||||||||||^^^^|
OBR||||8413^1|
OBR||||8571^1|
OBR||||8706^1|
Roche Diagnostics

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 on masking, see Masking (p. 86)
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.
MSH|^~\&|cobas 8000||host||20140630115511||INUÛ05|1290||2.5||||ER||UNICODE UTF-8|

EQU|DM#DM#0#0|20140630115511|
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.
MSH|^~\&|host||cobas 8000||20140630115042||INRÛ06|30115042493||2.5||||NE||UNICODE UTF-8|
Roche Diagnostics
330 Instrument status and test availability messages
EQU|DM#DM#0#0|20140630115042|
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
enabled, the data manager sends this message as soon
as it receives updated instrument status information from
the control unit.
MSH|^~\&|cobas 8000||host||20140630123849||ESUÛ01|1535||2.5||||ER||UNICODE UTF-8|

EQU|DM#DM#0#0|20140630123849|PU^POWERED_UP^LECIS^1^Power up^Hitachi|
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||20140630123830||ESRÛ02|30123830908||2.5||||AL||UNICODE UTF-8|

EQU|DM#DM#0#0|20140630123830|
Test availability update for available cobas e flow test

When a cobas e flow test is unmasked in the data
manager, a test availability update message is sent
showing the status of the embedded tests.

EQU|DM#DM#0#0|20141205132241|
…
Roche Diagnostics
Test availability update for unavailable cobas e flow test

When a cobas e flow test is masked in the data
manager, a test availability update message is sent
showing the status of the embedded tests.

EQU|DM#DM#0#0|20141205132241|
…
Roche Diagnostics
332
13 HL7 communication examples Instrument status and test availability messages
Roche Diagnostics
Appendices
14 Data alarms.............................................................................................................335
15 Instrument alarms ................................................................................................395
16 Result message codes for cobas e flow tests............................................411
17 Using MODULAR PRE-ANALYTICS...............................................................415
18 Identifying patient samples by sequence number...................................425
19 Preparing the host communication ...............................................................437
20 Text encoding tables ...........................................................................................457
Roche Diagnostics
335
Table of contents
Data alarms 14
In this chapter 14
List of numerical code data alarms and output
characters on the control unit . . . . . . . . . . . . . . . . . . . 339
List of data alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Data alarms of ISE tests. . . . . . . . . . . . . . . . . . . . . . . . . 344
ADC.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Calc.? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Cal.E (sample flag) . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Cal.I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
ClcT.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
CmpT.? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
CmpT.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Edited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
< >ISE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
>I.H. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
>I.HI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
>I.I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
>I.L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
>I.LH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
>I.LHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
14 Data alarms
>I.LI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
ISE.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
ISE.N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
MIXLOW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
na.LHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Over.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Reag.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
>Rept/<Rept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Samp.C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Samp.O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Samp.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
< >Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Roche Diagnostics
336
Table of contents
>Test/<Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Data alarms of photometric tests . . . . . . . . . . . . . . . . . 355
>Abs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
ADC.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Calc.? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Cal.E (sample flag) . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Cal.I. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
ClcT.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
CmpT.? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
CmpT.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
>Cuvet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Det.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Edited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
>I.H. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
>I.HI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
>I.I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
>I.L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
>I.LH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
>I.LHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
>I.LI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
>Kin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
>Lin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
MIXLOW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
MIXSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
na.LHI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
OBS.RM (c 702 module only) . . . . . . . . . . . . . . . . . 361
OBS.RR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Over.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
>Proz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
>React . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
ReagEx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Reag.S (c 701/c 702 modules only) . . . . . . . . . . . . 363
>Rept/<Rept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Samp.? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Samp.C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Samp.O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Samp.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
>Test/<Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Data alarms of immunology tests. . . . . . . . . . . . . . . . . 366
14 Data alarms
ADC.E (e 801 module only) . . . . . . . . . . . . . . . . . . . 366

Calc.? (e 602 module only) . . . . . . . . . . . . . . . . . . . 366
Cal.E (sample flag) . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Cal.I (e 602 module only). . . . . . . . . . . . . . . . . . . . . 367
CarOvr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Cell.T. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Clot.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
>Curr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Curr.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Edited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
eFlow.E (e 801 module only) . . . . . . . . . . . . . . . . . . 369
eFlow.W (e 801 module only) . . . . . . . . . . . . . . . . . 369
Roche Diagnostics
337
Table of contents
>I.H (e 602 module only). . . . . . . . . . . . . . . . . . . . . 369

>I.HI (e 602 module only) . . . . . . . . . . . . . . . . . . . . 370
>I.I (e 602 module only) . . . . . . . . . . . . . . . . . . . . . 370
>I.L (e 602 module only) . . . . . . . . . . . . . . . . . . . . . 370
>I.LH (e 602 module only) . . . . . . . . . . . . . . . . . . . 370
>I.LHI (e 602 module only) . . . . . . . . . . . . . . . . . . . 370
>I.LI (e 602 module only) . . . . . . . . . . . . . . . . . . . . 371
Inc.T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
na.LHI (e 602 module only) . . . . . . . . . . . . . . . . . . . 371
OBS.RR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Over.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
ReagEx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Reag.F. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Reag.H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Reag.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Reag.T. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
>Rept/<Rept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Samp.B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Samp.C. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Samp.O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Samp.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
<SigL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
SLLD.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
SLLD.N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
SysR.S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
SysR.T. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
>Test/<Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
WB.S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
WBSS.T (e 801 module only). . . . . . . . . . . . . . . . . . 376
WB.T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Alarms for calibrations. . . . . . . . . . . . . . . . . . . . . . . . . . 378
Cal.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Cond.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Diff.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Duplicate error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Dup.E (cobas c modules) . . . . . . . . . . . . . . . . . 381
Dup.E (cobas e modules) . . . . . . . . . . . . . . . . . 381
IStd.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Mono.E (e 602 module only) . . . . . . . . . . . . . . . . . . 382
Prep.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
14 Data alarms
Rsp1.E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Rsp2.E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
S1A.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
SD.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Sens.E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
>Sig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
<Sig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Sig.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Slop.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Std.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Std.E (ISE module) . . . . . . . . . . . . . . . . . . . . . . . 386
Std.E (cobas c modules) . . . . . . . . . . . . . . . . . . 387
Roche Diagnostics
338
Table of contents
Sys.E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Data alarm for QC materials . . . . . . . . . . . . . . . . . . . . . 389
QCErr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
List of data alarms for QC measurements. . . . . . . 389
Rerun test list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Alarm priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
14 Data alarms
Roche Diagnostics
Data alarms 339
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 (p. 393).
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.?
14 Data alarms
26 Technical Limit over (upper) >Test

27 Technical Limit over (lower) <Test
28 Random error in real-time QC R4SD
29 Systematic error 1 in real-time QC S2-2Sa
30 Systematic error 2 in real-time QC S2-2Sw
31 Systematic error 3 in real-time QC S4-1Sa
32 Systematic error 4 in real-time QC S4-1Sw
33 Systematic error 5 in real-time QC S10Xa
34 Systematic error 6 in real-time QC S10Xw
35 QC error 1 Q3SD
y Meaning of data alarms
Roche Diagnostics
340 List of numerical code data alarms and output characters on the control unit

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
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
14 Data alarms
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
78 Missing value ------
79 System errors Sys.E
80 Monotony of curve Mono.E
Roche Diagnostics
Data alarms 341

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
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
14 Data alarms
Roche Diagnostics
342 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 (p. 378)
Data alarm for QC materials (p. 389)
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
14 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
Data alarms 343
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
14 Data alarms
Roche Diagnostics
344 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
14 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
Data alarms 345
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 pack for this test, but the
calibration was not performed. Therefore, the reagent
pack has an Invalid calibration until the calibration is
performed.
This flag is attached to results if a test requires to be

calibrated after replacement of a reagent pack and the
automatic calibration masking is switched off.
ClcT.E
Alarm Calculation test error
Description Calculation error has occurred.

14 Data alarms
Roche Diagnostics
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
14 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
Data alarms 347
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.
14 Data alarms
Roche Diagnostics
< >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
14 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
Data alarms 349
>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
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
14 Data alarms
Cause A highly lipemic and icteric sample was measured.
ISE.E
Alarm ISE voltage level error
Roche Diagnostics
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
14 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
Data alarms 351
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.
14 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
>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
14 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
Data alarms 353
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)
14 Data alarms
Roche Diagnostics
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.

14 Data alarms
Roche Diagnostics
Data alarms 355
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.
14 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
356 Data alarms of photometric tests
Cause 1. Numerical conversion is abnormal.

2. The cell count is abnormal.
Calc.?

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


Cause Any alarm (for example, Std.E) occurred during

calibration.
Cal.I

14 Data alarms
calibration.

performed.

Roche Diagnostics
Data alarms 357
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).
14 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
>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
14 Data alarms
Alarm Edited test

Edited alarm on the Data Review submenu. This also
prints on the patient report.
Roche Diagnostics
Data alarms 359
>I.H
Description The hemolytic value is larger than the specified reference

value.
>I.HI
Description The hemolytic and icteric values are larger than the
>I.I
Description The icteric value is larger than the specified reference

value.
>I.L
Description The lipemic value is larger than the specified reference

value.
14 Data alarms
>I.LH
Description The lipemic and hemolytic values are larger than the
Roche Diagnostics
>I.LHI
Description The lipemic, hemolytic and icteric values are larger than
Cause A highly lipemic, hemolytic and icteric sample was

measured.
>I.LI
Description The lipemic and icteric values are larger than the
>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
14 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
Data alarms 361
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

for the test.



14 Data alarms
OBS.RM (c 702 module only)

Alarm On-board stability limit over on reagent manager
Roche Diagnostics
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 pack 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 pack expired.
Over.E
Alarm Overflow
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
Examples for the maximum number of digits that can
be presented: -0.001 or 12.34 or 9999.
>Proz
14 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
Data alarms 363
>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.
14 Data alarms
>Rept/<Rept
Description The result falls outside the repeat limit range

Cause The sample concentration is higher (>Rept) or lower

(<Rept) than the set value.
Roche Diagnostics
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 (352).
Samp.O
Alarm Sample carry over for modules.

check the results of the additional test(s) because special
wash was not performed in the first run.

Samp.S
Alarm Sample short
14 Data alarms

container.
u For more information see Samp.S (352).
>Test/<Test
Roche Diagnostics
Data alarms 365
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.
14 Data alarms
Roche Diagnostics
366 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

14 Data alarms
photomultiplier in a measuring channel is abnormal.
Calc.? (e 602 module only)

Roche Diagnostics
Data alarms 367
Cause Internal calculation error occurred.
Cal.E (sample flag)


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)


calibration.

performed.

CarOvr
14 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
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
14 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
Data alarms 369
Edited
Alarm Edited test

Edited alarm on the Data Review submenu. This also
prints on the patient report.
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)

14 Data alarms
Description The hemolytic value is greater than the specified

reference value.
Roche Diagnostics
>I.HI (e 602 module only)

Description The hemolytic and icteric values are greater than the
>I.I (e 602 module only)

Description The icteric value is greater than the specified reference

value.
>I.L (e 602 module only)

Description The lipemic value is greater than the specified reference

value.
>I.LH (e 602 module only)

Description The lipemic and hemolytic values are greater than the
14 Data alarms
>I.LHI (e 602 module only)

Description The lipemic, hemolytic, and icteric values are greater than
Roche Diagnostics
Data alarms 371
Cause A highly lipemic, hemolytic, and icteric sample was

measured.
>I.LI (e 602 module only)

Description The lipemic and icteric values are greater than the
Inc.T
Alarm Incubator temperature
Description Incubator temperature is out of range. The system

Cause • Radiation of heat does not work normally.

• The room temperature is out of range
na.LHI (e 602 module only)


for the test.


14 Data alarms

OBS.RR
Alarm On-board stability limit over on the reagent cassettes and
ProCell II M bottle
Roche Diagnostics
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
Cause The result contains more than 6 digits without decimal

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

14 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
Data alarms 373
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

Cause • Radiation of heat does not work normally.

• The room temperature is out of range.
>Rept/<Rept
Description The result is greater than the specified upper limit value
(>Rept) or smaller than the lower limit value (<Rept)
Cause • The sample concentration is higher than the set value

14 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
Description • Air bubble is detected in the sample when the sample

is aspirated.
• Air bubble is detected in the sample syringe flow path
when the sample is aspirated.
Cause • There are bubbles in the sample container.

• There are air bubbles in the water flow tube.
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.

check the results of the additional test(s) because no
special wash was performed in the first run.

Samp.S
Alarm Sample short

14 Data alarms
container.
Cause • The sample volume in the sample container is

insufficient.
• The sample container is missing on the rack.
Roche Diagnostics
Data alarms 375
<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

sample.
Cause 1. The sample volume is insufficient.

2. There are bubbles in the sample container.
14 Data alarms
SysR.S
Alarm System reagent short
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.
Roche Diagnostics
SysR.T
Alarm System reagent temperature
Description ProCell/CleanCell temperature is out of range. The system

Cause 1. Radiation of heat does not work normally.

2. The room temperature is out of range.
>Test/<Test
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).
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.

14 Data alarms
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
Roche Diagnostics
Data alarms 377

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


14 Data alarms
Roche Diagnostics
378 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
14 Data alarms
Cal.E
Alarm CALIB error (Calib flag)
Displayed in Calibration > Status > Calibration Trace.
Roche Diagnostics
Data alarms 379
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
14 Data alarms
y Slope values for ISE electrodes
Roche Diagnostics
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.
14 Data alarms
Duplicate error
This section describes the duplicate error for
cobas c modules and for cobas e modules.
Roche Diagnostics
Data alarms 381
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)

14 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
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

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.

14 Data alarms
• The calibrator did not reach room temperature.
Prep.E
Alarm Preparation abnormal

Trace.
Roche Diagnostics
Data alarms 383
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.
P9
&O
P9

• The flow path is contaminated.
Rsp1.E
Alarm Response (ISE) abnormal 1
Description The compensation factor is over the limits (narrower

range).

• The electrode is contaminated or deteriorated.
Rsp2.E
Alarm Response (ISE) abnormal 2
Description The compensation factor is over the limits (wider range).

14 Data alarms
• The electrode is contaminated or deteriorated.
S1A.E
Alarm S1ABS abnormal

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

14 Data alarms
• The reagent has been prepared improperly or has

deteriorated.
An improper sensitivity limit is specified.
>Sig
Alarm Maximum Signal
Roche Diagnostics
Data alarms 385
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.

• 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.
14 Data alarms
Slop.E
Alarm Slope abnormal (ISE only)

Trace.
Roche Diagnostics
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.
P9
&O
P9

• 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:

14 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
Data alarms 387
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
14 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
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.

14 Data alarms
Roche Diagnostics
Data alarms 389
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
14 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
390 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
14 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
Data alarms 391
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
14 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
392 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
14 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
Data alarms 393
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.
w Priority of alarms from an ISE module

14 Data alarms
Roche Diagnostics
394 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
14 Data alarms
• All other numerical code alarms
Roche Diagnostics
395
Table of contents
Instrument alarms 15
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 15
Instrument alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
15 Instrument alarms
Roche Diagnostics
396
Table of contents
Roche Diagnostics
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.
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.
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 15 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

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)
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
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.
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
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.
126 204 Data Manager Internal process error 1. Restart the system.
Communication Error occurred. 2. Contact service representative, if alarm recurs.

(Control socket 2. Check if the connector was not plugged in during
communication line) the data communication.
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.
y Instrument alarms
Roche Diagnostics

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
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)
communication line)
126 305 Data Manager Database access error 1. Restart the system.
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.
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.
126 501 Data Manager The response from the Data 1. Restart the system. 15 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.
communication.
Data Manager detected in the UR11. 2. Check the UR11 communication ID.
communication.
Data Manager detected in the PL11. 2. Check the PL11 communication ID.
communication.
y Instrument alarms
Roche Diagnostics

Data Manager detected in the PD11. 2. Check the PD11 communication ID.
communication.
Data Manager detected in the CL11. 2. Check the CL11 communication ID.
communication.
Data Manager detected in the CD11. 2. Check the CD11 communication ID.
communication.
Data Manager detected in the QL11. 2. Check the QL11 communication ID.
communication.
Data Manager detected in the QD11. 2. Check the QD11 communication ID.
communication.
Data Manager detected in the RD11. 2. Check the RD11 communication ID.
communication.
Data Manager detected in the TQ11. 2. Check the TQ11 communication ID.
communication.
Data Manager detected in the CV11. 2. Check the CV11 communication ID.
communication.
Data Manager detected in the CQ11. 2. Check the CQ11 communication ID.
communication.
Data Manager detected in the MR11. 2. Check the MR11 communication ID.
communication.
Data Manager detected in the MK11. 2. Check the MK11 communication ID.
communication.
y Instrument alarms
Roche Diagnostics

Data Manager detected in the RM11. 2. Check the RM11 communication ID.
communication.
Data Manager detected in the EI12. 2. Check the EI11 communication ID.
communication.
Data Manager detected in the EI13. 2. Check the EI13 communication ID.
communication.
Data Manager detected in the PU11. 2. Check the PU11 communication ID.
communication.
Data Manager detected in the PU12. 2. Check the PU12 communication ID.
communication.
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.
communication.
Data Manager detected in the EU11. 2. Check the EU11 communication ID.
communication.
Data Manager detected in the WL11. 2. Check the WL11 communication ID.
communication.
Data Manager detected in the WD11. 2. Check the WD11 communication ID.
communication.
Data Manager detected in the ER11. 2. Check the ER11 communication ID.
communication.
communication.
y Instrument alarms
Roche Diagnostics

communication.
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 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 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
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.
date is included in the 2. Check the followings. * Sample Type * Sample ID *

barcode label on the sample. Sequence No. * Rack ID * Rack Position No.
The duplicated data is
followings:
o In case of routine sample
in barcode mode:
Sample Type, Sample ID
o In case of Stat sample in
barcode mode: Sample
Type, Sample ID
o In case of routine sample
in non-barcode mode:
Sample Type
y Instrument alarms
Roche Diagnostics

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
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
(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. 15 Instrument alarms
892 -2 Data Manager Communication error 1. Check the connection status of Data Manager on
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.
(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

(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.
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.
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.
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.
Data Manager INV segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates INV segment.
Data Manager MSA segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates MSA segment.
Data Manager MSH segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates MSH segment.
Data Manager NDS segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates NDS segment.
Data Manager OBR segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates OBR segment.
Data Manager OBX segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates OBX segment.
y Instrument alarms
Roche Diagnostics

Data Manager ORC segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates ORC segment.
Data Manager PID segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates PID segment.
Data Manager QAK segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates QAK segment.
Data Manager QID segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates QID segment.
Data Manager QPD segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates QPD segment.
Data Manager RCP segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates RCP segment.
Data Manager SAC segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates SAC segment.
Data Manager SID segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates SID segment.
Data Manager SPM segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates SPM segment.
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. 15 Instrument alarms
Data Manager TCD segment. The 2. Check whether '<CR>' (0x0d) is at the end of the
subcategory code indicates TCD segment.
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.
field number and communication.
Data Manager INV segment. The 2. Check the INV segment.
y Instrument alarms
Roche Diagnostics

Data Manager MSA segment. The 2. Check the MSA segment.
Data Manager MSH segment. The 2. Check the MSH segment.
Data Manager NDS segment. The 2. Check the NDS segment.
Data Manager OBR segment. The 2. Check the OBR segment.
Data Manager OBX segment. The 2. Check the OBX segment.
Data Manager ORC segment. The 2. Check the ORC segment.
Data Manager PID segment. The 2. Check the PID segment.
Data Manager QAK segment. The 2. Check the QAK segment.
Data Manager QID segment. The 2. Check the QID segment.
Data Manager QPD segment. The 2. Check the QPD segment.
Data Manager RCP segment. The 2. Check the RCP segment.
y Instrument alarms
Roche Diagnostics

Data Manager SAC segment. The 2. Check the SAC segment.
Data Manager SID segment. The 2. Check the SID segment.
Data Manager SPM segment. The 2. Check the SPM segment.
Data Manager TQ1 segment. The 2. Check the TQ1 segment.
Data Manager TCD segment. The 2. Check the TCD segment.
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.
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.
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.
4. Contact service representative, if alarm recurs. 15 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.
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.
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.
y Instrument alarms
Roche Diagnostics

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

Communication Error HL7 text received from Data 2. Check the HL7 text. (Chemistry Calibration Result
Manager is not the Response Text)
(Chemistry Calibration
Result Response)
Communication Error HL7 text received from Data 2. Check the HL7 text. (ISE Calibration Result
corresponding one. (ISE 3. Contact service representative, if alarm recurs.
Calibration Result Response
Text)
Communication Error HL7 text received from Data 2. Check the HL7 text. (Immune Calibration Result
corresponding one. (Immune 3. Contact service representative, if alarm recurs.
Text)
Communication Error HL7 text received from Data 2. Check the HL7 text. (Patient/QC Result Response
Manager is not the Text - Batch)
(Patient/QC Result Response
Text)
Communication Error HL7 text received from Data 2. Check the HL7 text. (Reaction Monitor Result
(Reaction Monitor Result
Response Text)
Communication Error HL7 text received from Data 2. Check the HL7 text. (Reaction Monitor Calibration
Manager is not the Result Response Text)
(Reaction Monitor
Text)
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. 15 Instrument alarms
Data Result Response Text)
Communication Error HL7 text received from Data 2. Check the HL7 text. (Raw Data Calibration Result
corresponding one. (Raw 3. Contact service representative, if alarm recurs.
Data Calibration Result
Response)
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)
y Instrument alarms
Roche Diagnostics

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)
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
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
Roche Diagnostics
411
Table of contents
Result message codes for

cobas e flow tests 16
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
16 Result message codes for cobas e flow tests

e 801 module.
In this chapter 16
Result codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Roche Diagnostics
412
Table of contents
Roche Diagnostics
Result message codes for cobas e flow tests 413
Result codes
A cobas e flow test can send a code number as the
result of a qualitative test, in the field OBX-5 (HL7) or R-
4.1 (ASTM). This table shows the supported codes and
their meanings.
Code Result Message

-1 non reac.
0 border
1 reac.
2 n.a.
3 n.a.
4 gray-zone
5 indeterminate
6 above measuring range
7 below measuring range
8 result between LoB and LoD

9 result between LoD and LoQ
10 result between LoB and LoQ
11 close to medical decision point
12 close to medical decision point 1
15 Avidity high
16 Avidity low
17 confirmatory test possible
18 confirmatory test recommended
19 confirmation recommended
20 NAT-testing recommended
21 PCR recommended
22 repeat in duplicate recommended
23 retesting recommended
24 limited precision
25 dilution automatically or manually
26 dilution recommended
27 manual dilution recommended
28 additional diagnostic testing recommended
29 follow up sample recommended
30 Confirmed non-reactive
31 Confirmed positive
32 Confirmation not valid
33 Intermediate
34 Repeatedly reactive
35 Repeatedly reactive, investigated using an
independent neutralization test
y cobas e flow test quantitative result codes (OBX-5)
Roche Diagnostics
414 Result codes
Code Result Message

36 acute
37 early recovery
38 chronic infection
39 recovered infection
40 Avidity medium
41 acute
42 late-acute
43 remote
44 persisting IgM
45 antibody titer protective
46 immunocomplex detectable
47 Neutralization positive
48 equivocal
49 Immunity likely
50 Immunity unlikely
51 Immunity unlikely - (Re)Vaccination might be
considered
52 Immunity questionable - Blot recommended

53 risk score "high"
54 risk score "low"
55 risk score "borderline" + (follow up sample
recommended)
56 no risk calculation possible
57 no avidity calculation possible
58 invalid
59 below dilution range
60 no reliable avidity score
61 Avidity gray-zone
62 Avidity borderline
63 avidity determination failed
64 no avidity determination possible, IgG titer too low
65 confirmed reactive
66 confirmed negative
67 error, multiflow aborted
68 inconsistent result in multiflow
69 implausible
70 risk "high"
71 risk "low"
72 risk "borderline"
y cobas e flow test quantitative result codes (OBX-5)
Roche Diagnostics
415
Table of contents
Using MODULAR PRE-ANALYTICS 17

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.
17 Using MODULAR PRE-ANALYTICS

In this chapter 17
Sample IDs and barcodes . . . . . . . . . . . . . . . . . . . . . . . 417
Handling query messages without barcodes . . . . . . . 418
Order of messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Handling batch test selections with strict rack and
position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Roche Diagnostics
416
Table of contents
Roche Diagnostics
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
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.
Roche Diagnostics
418 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

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 (p. 128).
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
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.

- 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
420 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) (p. 151), and HL7 text content
(p. 221).
Roche Diagnostics
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
related configuration > Interface options and select
the option Enable rack and position mode.

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
422 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.
! 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
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.
Roche Diagnostics
424
17 Using MODULAR PRE-ANALYTICS Handling batch test selections with strict rack and position
Roche Diagnostics
425
Table of contents
Identifying patient samples by

sequence number 18
Numbering samples in sequence instead of using a
barcode
18 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 18
Identifying samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Sample IDs and barcodes . . . . . . . . . . . . . . . . . . . . 427
Patient samples without barcodes . . . . . . . . . . . . . 427
Identifying patient samples by sequence number . . . 428
Sequence numbers and sample IDs . . . . . . . . . . . 429
What the data manager understands . . . . . . . . . . 429
Important information for using sequence numbers . 430
Using sample sequence numbers in ASTM . . . . . . . . 432
Test selection inquiry . . . . . . . . . . . . . . . . . . . . . . . . 432
Test result message . . . . . . . . . . . . . . . . . . . . . . . . . 433
Using sample sequence numbers in HL7 . . . . . . . . . . 434
Test selection inquiry . . . . . . . . . . . . . . . . . . . . . . . . 434
Test result message . . . . . . . . . . . . . . . . . . . . . . . . . 435
List of configuration settings for barcode and
sequence modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Roche Diagnostics
426
Table of contents
Roche Diagnostics
Identifying patient samples by sequence number 427
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.

This is the default configuration for the cobas® 8000
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
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
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
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.

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
430 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.
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
! 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.

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

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

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.
host sends the sequence number in O-4.1.
Sample ID order record:
O|1|2110903|^50094^3^^S1^SC^|^^^205^|R|201108…
Sequence number order record: either
O|1||3^^^^S1^SC^|^^^205^|R|201…
or
O|1||3^50094^3^^S1^SC^|^^^205^|R|201…
Roche Diagnostics
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:
manager sends sample ID from the barcode in O-3.
data manager sends the sequence number in O-4.1.
Sample ID order record:

O|1|2110903|0^50094^3^^S1^SC^not|^^^112^1|R|201108
…
Sequence number order record:
O|1||3^50094^3^^S1^SC^not|^^^991^1|R|201…
Roche Diagnostics
434 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.

In a test selection inquiry message from the data
manager to the host:
manager sends sample ID from the barcode in QPD-
3-1.
data manager sends the sequence number in QPD-
3.2.
Sample ID inquiry:
QPD|TSREQ|4362|2110903||50094|3||||S1|SC|R1|R|
Sequence number inquiry:
QPD|TSREQ|4565|^3||50094|3||||S1|SC|R1|R|
These fields are used the same way in an order query

from the host to the data manager.

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.
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|||^^^^|||2011061521542
4||||||||||SC
Sequence number specimen and container detail

segments:
SPM||^3||S1||not|||||P|||^^^^|||20110615215424||||
||||||SC
Roche Diagnostics
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:
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.
data manager sends the sequence number in SPM-

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|||^^^^|||2011061521542
4||||||||||SC|
SAC||||||||||50094|3|
Sequence number specimen and container detail

segments:
SPM||^3||S1||not|||||P|||^^^^|||20110617105639||||
||||||SC|
SAC||||||||||50094|3|
Roche Diagnostics
436 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
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 (p. 128).
Roche Diagnostics
Preparing the host communication 437
Preparing the host communication19

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.

In this chapter 19
General differences in the ASTM protocol . . . . . . . . . 439
Message encoding and transport . . . . . . . . . . . . . 439
Sample identification . . . . . . . . . . . . . . . . . . . . . . . . 440
Sample types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Patient demographics . . . . . . . . . . . . . . . . . . . . . . . 441
ASTM message types. . . . . . . . . . . . . . . . . . . . . . . . 441
HL7 message types . . . . . . . . . . . . . . . . . . . . . . . . . 442
Differences in ASTM message definitions . . . . . . . . . 443
General differences in the ASTM messages. . . . . 443
Message Header Record . . . . . . . . . . . . . . . . . . . . . 443
Message Termination Record . . . . . . . . . . . . . . . . . 443
Patient Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Order Record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Result Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Comment Record (following an Order Record) . . 448
Comment Record (following a Result Record) . . . 448
Query Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Photometric Calibration Result Record . . . . . . . . . 449
ISE Calibration Result Record . . . . . . . . . . . . . . . . . 449
E-module (Immunology) Calibration Result
Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Other differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
Roche Diagnostics
438
Rerun results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452

LIS communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Identifying samples by sequence number . . . . . . . . . 454
Traceability information for quality control and
calibration results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
The specimen segment SPM with quality control
results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
The specimen segment SPM with calibration
results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
The substance identifier segment SID. . . . . . . . . . 456
Data points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Roche Diagnostics
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
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

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
440 General differences in the ASTM protocol
Sample identification
analyzer series
Sample number mode(a) 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 (p. 425)
Barcode label Yes Yes
Rack & Sample Position Yes Yes
y Sample identification, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series
(a) No real sample identification
Sample types
The sample types (or Rack Types) are used in Query
Record and Order Record (Specimen Types). While all
these types are supported by the cobas® 8000 data
manager, their availability on any particular system also
depends on the configuration and modules installed on
the cobas® 8000 modular analyzer series instrument.
Item Rack Type Specimen MODULAR cobas® 8000 data Comment

Type ANALYTICS EVO manager
analyzer /
cobas® 6000
analyzer series
No specimen assigned S0 Yes Yes
Serum/Plasma S1 1 Yes Yes
Urine S2 2 Yes Yes
Cerebrospinal Fluid S3 3 Yes Yes
Supernatant S4 4 Yes Yes
Other S5 5 Yes Yes
Whole Blood S6 6 No Yes Extended
Oral Fluids (Saliva) S7 7 No Yes Extended
Other 2 S8 8 No Yes Extended
Other 3 S9 9 No Yes Extended
Other 4 SA A No Yes Extended
®
y Sample types, compared to the MODULAR ANALYTICS EVO analyzer / cobas 6000 analyzer series
Roche Diagnostics
Patient demographics
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

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
442 General differences in the ASTM protocol
HL7 message types

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Ô33 Extended
(inquiry)
Test Selection Download NO OMLÔ33 Extended
(inquiry)
Photometric Calibration Result NO OUL^R22^PCUPL Extended
ISE Calibration Result NO OUL^R22ÎCUPL Extended
Immunology Calibration NO OUL^R22ÊCUPL Extended
Result
Masking command NO EACÛ07 Extended
Equipment Status Request NO ESRÛ02 Extended
Equipment Status Update NO ESUÛ01 Extended
Inventory Status Request NO INRÛ06 Extended
Inventory Status Update NO INUÛ05 Extended

y HL7 message types, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series
Roche Diagnostics
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
General differences in the ASTM messages

ASTM message records in cobas® 8000 are terminated
by a vertical bar, but in MODULAR ANALYTICS EVO
analyzer / cobas® 6000 analyzer series the vertical bar is
omitted.
Message Header Record

Field Description MODULAR cobas® 8000 data manager Comment
ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series

3 Control ID NO YES Extended
5 data manager to 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

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

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Âge Unit NO Other data and
location
y Patient record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series
! WARNING
patient sex.
unknown sex.

the host.
u For more information, see Patient demographics

(p. 441).
Roche Diagnostics
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.

ANALYTICS EVO
analyzer /
cobas® 6000

analyzer series
3 Sample ID for Control-SID: Name Name^LotNr^Control- Extended, Upload
controls or Lotnumber IDÊxpDate^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

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

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

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

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
Comment Record (following an Order Record)

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

ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
3 Comment source “I” by Analyzer “I” by Analyzer, “L” by data Extended
manager
4 Comment Text, if Flagnumber Flagnumber^Description Extended

type I
5 Comment Type, if No TextÛser^Date Extended
type G
y Comment record, after result record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series
Query Record
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
Photometric Calibration Result Record

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

ISE Calibration Result Record
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
y ISE calibration result record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series
Roche Diagnostics

ANALYTICS EVO
analyzer /
cobas® 6000
analyzer series
value alarm
11,C7 Cl Data alarms Component 7 Component 7 contains: Extended
value alarm
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.)
value alarm
compensation data Component 7
13,C7 K Calibration Component 7 Component 7 contains: Extended

value alarm
14,C7 Cl Calibration Component 7 Component 7 contains: Extended
value
y ISE calibration result record, compared to the MODULAR ANALYTICS EVO analyzer / cobas® 6000 analyzer series
E-module (Immunology) Calibration Result Record
Roche Diagnostics

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

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
452 Other differences
Other differences
There are differences between the cobas® 8000 data
manager and the compared to the MODULAR
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

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
LIS communications
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 (p. 99).
u For details of the physical connections, see Physical
Roche Diagnostics
454 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.

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 (p. 425).
u For details of how to identify samples by a strict rack
and position, see Using MODULAR PRE-ANALYTICS
(p. 415), and Rack and position mode (p. 109).
Roche Diagnostics
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 series
Control identification. Control name in record O-4. SPM-2: Extended
Name^LotÎDÊxpiryDat
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

manager).
y Comparison of specimen segment SPM fields for quality control results in recent versions
The specimen segment SPM with calibration results

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 (p. 234).
Roche Diagnostics
456 Traceability information for quality control and calibration results
The substance identifier segment SID

This section lists the changes to the substance identifier
segment SID.

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
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
y Comparison of substance identifier segment SID fields in recent versions
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 (p. 167)
e 602 result with data point values (p. 199)
u HL7:
(p. 239)
e 602 result message with data point values (p. 308)
u cobas® 8000 data manager Operator’s Manual
Roche Diagnostics
Text encoding tables 457
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 20
ASCII character codes . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Western European characters in UTF-8 . . . . . . . . . . . . 460
Roche Diagnostics
458
Roche Diagnostics
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

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
460 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+000A 0a <control> U+000B 0b <control>
U+000C 0c <control> U+000D 0d <control>
U+000E 0e <control> U+000F 0f <control>
U+001A 1a <control> U+001B 1b <control>
U+001C 1c <control> U+001D 1d <control>
U+001E 1e <control> U+001F 1f <control>
U+0020 20 SPACE U+0021 ! 21 EXCLAMATION MARK
U+0022 " 22 QUOTATION MARK U+0023 # 23 NUMBER SIGN
U+0024 $ 24 DOLLAR SIGN U+0025 % 25 PERCENT SIGN
U+0026 & 26 AMPERSAND U+0027 ' 27 APOSTROPHE
U+0028 ( 28 LEFT PARENTHESIS U+0029 ) 29 RIGHT PARENTHESIS
U+002A * 2a ASTERISK U+002B + 2b PLUS SIGN
U+002C , 2c COMMA U+002D - 2d HYPHEN-MINUS

U+002E . 2e FULL STOP U+002F / 2f SOLIDUS
U+0030 0 30 DIGIT ZERO U+0031 1 31 DIGIT ONE
U+0032 2 32 DIGIT TWO U+0033 3 33 DIGIT THREE
U+0034 4 34 DIGIT FOUR U+0035 5 35 DIGIT FIVE
U+0036 6 36 DIGIT SIX U+0037 7 37 DIGIT SEVEN
U+0038 8 38 DIGIT EIGHT U+0039 9 39 DIGIT NINE
U+003A : 3a COLON U+003B ; 3b SEMICOLON
U+003C < 3c LESS-THAN SIGN U+003D = 3d EQUALS SIGN
U+003E > 3e GREATER-THAN SIGN U+003F ? 3f QUESTION MARK
U+0040 @ 40 COMMERCIAL AT U+0041 A 41 LATIN CAPITAL LETTER A
U+0042 B 42 LATIN CAPITAL LETTER B U+0043 C 43 LATIN CAPITAL LETTER C
U+0044 D 44 LATIN CAPITAL LETTER D U+0045 E 45 LATIN CAPITAL LETTER E
U+0046 F 46 LATIN CAPITAL LETTER F U+0047 G 47 LATIN CAPITAL LETTER G
y Western european characters in UTF-8
Roche Diagnostics

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>
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+009A c2 9a <control> U+009B c2 9b <control>
U+009C c2 9c <control> U+009D c2 9d <control>
Roche Diagnostics
462 Western European characters in UTF-8

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

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

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
Roche Diagnostics
464
20 Text encoding tables Western European characters in UTF-8
Roche Diagnostics
465
Symbols A
< >Test (data alarm) AA, HL7 acknowledgment, 277

– ISE, 352 Absorbance
<SigL (data alarm) – photometric calibration results ASTM, 180
– e 602, 375 – photometric calibration results HL7, 252
>Abs (data alarm) ACK
– c modules, 355 – message structure HL7, 225
>Curr (data alarm) – MSH segment, 227
– e 602, 368 Acknowledgment
>I.H (data alarm) – application, MSH segment, 228
– c modules, 359 – ASTM, 148
– e 602, 369 – code, MSA segment, 229
– ISE, 348 – example test selection messages, 290
>I.HI (data alarm) – HL7 overview, 106
– c modules, 359 – message structure in HL7, 225
– e 602, 370 – message type, 227
– ISE, 348 Action code
>I.I (data alarm) – ASTM, 164
– c modules, 359 – HL7, 237
– e 602, 370 ADC.E (data alarm)
– ISE, 348 – c modules, 355
>I.L (data alarm) – ISE, 344
– c modules, 359 Addresses, 7
– e 602, 370 AE, HL7 acknowledgment, 277
– ISE, 349 Alarm
>I.LH (data alarm) – data alarm, 335
– c modules, 359 Alarms
– e 602, 370 – calibration alarm photometric ASTM, 180
– ISE, 349 – calibration alarms ISE ASTM, 181
>I.LHI (data alarm) – calibration flags HL7, 249
– c modules, 360 – data alarms HL7, 260
– e 602, 370 – data alarms list, 339
– ISE, 349 – data alarms, ASTM, 175
>I.LI (data alarm) – data alarms, ISE calibration results ASTM, 181
– c modules, 360 – data alarms, ISE calibration results HL7, 253
– e 602, 371 – instrument alarms list, 397
– ISE, 349 – instrument alarms, calibration results HL7, 257
>Kin (data error) – instrument alarms, photometric calibration results
– c modules, 360 ASTM, 180
>Lin (data alarm) – result abnormal examples ASTM, 194
– c modules, 360 – result abnormal examples HL7, 296
>Proz (data alarm) – result abnormal flags ASTM, 171
– c modules, 362 – result abnormal flags HL7, 242
>React (data alarm) Always ask for test selection, 104
– c modules, 363 Analytical data
>Rept / <Rept (data alarm) – calibration ASTM, 181
– e 602, 373 – calibration HL7, 253
>Sig (calibration alarm) Analytical Unit ID
– e 602, 384 – configuration, 115
>Test / <Test (data alarm) – E-module calibration results ASTM, 184
– c modules, 364 – ISE calibration ASTM, 180
– e 602, 376 – ISE calibration results ASTM, 181
– ISE, 353 – ISE calibration results HL7, 251
– masking message HL7, 270
– OBX segment HL7, 244
Numerics – OBX segment HL7 QC, 248
– overview, 115
8100, see cobas® 8100 instrument, 110
Roche Diagnostics
466
– photometric and E-module calibration results HL7, C

251
– result record ASTM, 173 c modules
Analyzer – data alarms, 355
– cobas® 8000 modular analyzer series, 43 c702, 45
– MODULAR ANALYTICS EVO analyzer / cobas® Cables
6000 analyzer series, upgrading from, 439 – diagram, 118
Application Code. See Testcode, 258 – recommendations, 120
AR, HL7 acknowledgment, 277 Cal.I (data alarm)
As soon as setting, 131, 132 – c modules, 356
ASCII 127 table, 459 – e 602, 367
ASTM – ISE, 345
– checksum, 149 Calc.? (data alarm)
– connections, 104 – ISE, 344
– delimiters, 145 Calculated QC results
– E1381-91 Low Level Protocol, 143 – example HL7 messages, 315
– escape character, 146 Calculated test
– field attributes, 157 – data alarm, c modules, 357
– field types, 157 – data alarm, ISE, 345
– frames, 144, 149 Calculation
– low-level examples messages, 189 – not possible, c modules, 356
– message transmission phases, 148 – not possible, e 602, 366
– repeat delimiter, 146 – not possible, ISE, 344
Attributes, ASTM fields, 157 Calibration
Auto-dilution factor HL7, 258 – analytical data ISE ASTM, 181, 182
Automatic rerun – analytical data ISE HL7, 253
– timing, 132 – calibration ID in calibration results, HL7, 250
Automatic Rerun Test Selection, 128 – calibration ID in patient and QC results, ASTM, 173
Autorerun enabled, 132 – calibration ID in patient results, HL7, 243
– calibration ID in QC results, HL7, 247
– calibration type, HL7, 253
B – failure data, c modules, 356
– failure data, ISE, 345
Barcodes
– invalid (data alarm), e 602, 367
– introduction, 53
– invalid (data alarm), ISE, 345, 356
– order sample ID ASTM, 161
– method E-module ASTM, 184
– sample IDs, 68
Calibration error
– samples without barcodes, 68, 128
– c modules, 378
Batch mode (result upload message)
– e 602, 367
– example messages HL7, 293
Calibration results
– example QC result HL7, 313
– ASTM message structure, 155
Batch mode (test selection download message)
– code in ASTM header, 159
– configuring, 104
– examples ASTM, 207
– definition, 56, 61
– examples HL7, 319
– diagram, 76
– HL7 message structure, 223
– example messages ASTM, 193
– photometric calibration alarm ASTM, 180
– message flow diagram, 87
– status E-module HL7, 255
– messages, 154
– value E-module result HL7, 255
Birthdate
– value ISE result HL7, 253
– patient in ASTM, 160
– value of E-module result, ASTM, 185
– patient in HL7, 230
– values, HL7, 249
Bottle
Calibrator Factor
– ASTM, 173
– calibration result ASTM, 185
– HL7 calibration, 251
– calibration result HL7, 255
– HL7, QC, 248
Calibrator lot number
– standby, ASTM, 173
– ASTM, 184
– standby, HL7, 248
– HL7, 234
– standby, HL7 calibration, 251
CarOvr (data alarm), e 602, 367
Carryover
Roche Diagnostics
467
– Det.S (data alarm), 358 – sample ASTM query, 179

Cat.5e cable, 120 Control lot, 455
Caution, definition, 16 Control Unit
Cell blank – communication trace file, 135
– abnormal (data alarm), 358 – definition, 43
Cell.T (data alarm), e 602, 368 – host communication, 125
Character Conventions used in this publication
– data type ASTM, 157 – abbreviations, 13
– data type in HL7, 226 – symbols, 13
Chart Copyright, 6
– European characters in UTF-8, 460 CR, HL7 framing, 220
– sequence numbers and sample IDs, 429 Cup
Charts – ASTM order, 162
– configuration settings, 436 – ASTM query, 179
– modes, configuring, 104 – HL7 SPM segment, 233
Chemistry Test Calibration Result Detail, 127 – QPD segment HL7, 263
ClcT.E (data alarm) Curr.E (data alarm)
– c modules, 357 – e 602, 368
Clinical chemistry modules, 45
Clot.E (data alarm)
– e 602, 368
D
C-module, definition, 45
Danger (hazard level), 16
cobas e flow
Data
– example result messages, 196, 299
– calibration analytical data ASTM, 181
– result codes, 413
– collecting all, 127
cobas e flow test (error)
– ISE calibration analytical data HL7, 253
– e 801, 369
Data alarm, 335
cobas e flow test (warning)
– e 602 module, 366
– e 801, 369
– ISE module, 344
cobas® 8100 instrument, 110
Data alarms
cobas® IT firewall, 121
– ASTM, 175
codes
– calibration results ISE ASTM, 181
– cobas e flow results, 413
– list, 339
Comment
– photometric calibration results ISE HL7, 253
– comment type flag ASTM, 166
data manager
– comment type flag HL7, 260
– definition, 43
– record format in data manager ASTM, 166
– version in ASTM, 158
– source of comment, HL7, 260
Data point results
– source of result comment, ASTM, 174
– ASTM result record, 170
Communication trace file, Control Unit, 135
– example result, ASTM, 199
Compensation error
– example result, HL7, 308
– calculation error, c modules, 357
Databits, 122
– calculation error, ISE, 346
Date
– data error, c modules, 357
– data type ASTM, 157
– data error, ISE, 346
– data type HL7, 226
Complex
DateTime
– ASTM field type, 157
– calibration result E-module ASTM, 185
Conditioning error (calibration alarm), 379
Configuration settings chart, 436
– masking message, 269, 271, 273
Connections
– message creation ASTM, 159
– message creation HL7, 227
– recommendations, 122
– order creation ASTM, 164
– serial, 122
– pipetting ASTM, 172
Contact, 7
– pipetting HL7, 243
Container
– pipetting HL7, QC, 247
– HL7 QPD segment, 263
– result available, HL7, 244
– HL7 SPM segment, 233
– result available, HL7, QC, 248
– sample ASTM order, 162
Roche Diagnostics
468
– results available, HL7, calibration, 251 – sample types, 51

– results, ASTM, 172 EACÛ07
– sample collection ASTM, 164 – MSH segment, 227
– specimen collection HL7, 233 – structure, 224
Decreased sample volume, 391 ECUPL^REAL
Delimiters – ASTM header, 159
– ASTM, 145 – structure, 155
– HL7, 227 Edited (data alarm)
– location in ASTM message, 158 – c modules, 358
Demographic data, no sample found, 191, 291 – e 602, 369
Detergent – ISE, 347, 348
– short (data alarm), 358 Edition notice, 5
Deviation of Duplicate Measurement Elecsys, 45
– calibration result ASTM, 185 Electrolytes, 45
– calibration result HL7, 255 E-module, definition, 45
Diagram Encoding, UTF-8, 47
– ASTM transmission phases, 148 End block, HL7, 220
– batch test selection download, 76 EP-17A
– cables, 118 – example ASTM, 195
– HL7 data framing, 220 – with e801 and new modules, 70
– message flow in batch test selection download, 87 Equipment Inventory
– message flow in realtime test selection download, 88 – see Test availability
– message flow with upload by sample, 90 Equipment status
– order query, 77 – see Instrument status
– realtime test selection download, 76 Error
– result query, 76 – calibration, c modules, 378
– timeouts, 102 – calibration, e 602, 367
Diff.E (calibration alarm) Error acknowledgment, HL7, 228
– e 602, 380 Escape character
Dilution, 52 – ASTM, 146
– factor in ASTM, 164 – HL7, 227
– factor in order record ASTM, 163 ESRÛ02
– factor TCD segment HL7, 258 – structure in HL7, 224
– flag ASTM order, 162 ESUÛ01
– flag in HL7 SPM segment, 233 – structure in HL7, 223
– OBR segment HL7, 237 Ethernet, 121
– result record ASTM, 169 Expiry date of control lot
Downloads – calibration results HL7, 234
– batch, 61 – upgrading to 1.04, 455
– realtime, 61 Expiry date of control lot, HL7, 232
Duplicate limit Expiry date of reagent HL7, 259
– Dup.E calibration alarm, c modules, 381 Extended ASCII in UTF-8, 460
– Dup.E calibration alarm, e 602, 381
F
E
False bottom tubes
e Pack expired flag, ASTM, 184 – ASTM order record, 162
e Pack Lot No., 184 – ASTM query record, 179
e 602 module – HL7 QPD segment, 263
– calibration alarm list, 378 – HL7 SPM segment, 233
– data alarm list, 342, 389 Feedback, 7
– data alarms, 366 Flags
E.I.U. Level (Essential Information Upload), 126 – c8000, ASTM, 173
e801 – c8000, HL7, 244
– calculated QC results, example HL7 messages, 315 – c8000, HL7, calibration, 251
– EP-17A, 70 – c8000, HL7, QC, 248
– module type OBX segment, 244, 248, 251 – calibration alarms HL7, 249
– module type, ASTM result record, 173 – comment type ASTM, 166
Roche Diagnostics
469
– comment type HL7, 260 Increased sample volume, 391

– data alarm in ASTM, 175 Incubator
– data alarms HL7, 260 – temperature, data alarm, e 602, 371
– dilution ASTM order, 162 Inquiry for test selection. See Test selection inquiries
– dilution HL7 order, 233 INRÛ06
– DM, ASTM, 173 – structure in HL7, 224
– DM, HL7, 244, 248, 251 Instrument
– e Pack expired flag, 184 – Analytical Unit ID. See Analytical Unit ID, 173
– module type, ASTM, 173 – data alarms HL7, 260
– module type, HL7, 244 – ID for host. See Analytical Unit ID
– module type, HL7, QC, 248 – ID in data manager, ASTM, 173
– qualitative result flag ASTM, 170 – instrument alarms list, 397
– result abnormal examples ASTM, 194 – number, ASTM, 173
– result abnormal examples HL7, 296 – number, HL7, 244
– result abnormal flags ASTM, 171 – number, HL7 calibration, 251
– result abnormal flags HL7, 242 – number, HL7 QC, 248
– result comment, 174, 175 – operator, ASTM, 172
– sender, host / data manager ASTM, 165 – operator, HL7, 243
Frames – operator, HL7, QC, 247
– ASTM, 144, 149 – sample ID ASTM, 162
FS, HL7 framing, 220 – throttle, 107
Instrument status
– Equipment Status Request message, 224
G – Equipment Status Update message, 223
– Instrument status message, 271
Gender. See Sex
Insufficient reagent
– Reag.S alarm, c 701/c 702, 363
H – Reag.S alarm, e 602, 373
Intended use, 13
Hazard levels, 15 International Standards Organization (ISO), HL7, 220
Hemolysis, 79 INUÛ05
HL7 – structure in HL7, 223
– network, 104 IP addresses, recommendations, 121
– recommendations, 46 ISE module
– version, 228 – data alarms, 344
Host timeout, 102 ISE module (Ion-Sensitive-Diode), definition, 45
Host Upload Status, 277 ISE.E (data alarm), 349
Hosts ISE.N (data alarm), 350
– communication log file, 117 IStd.E (calibration alarm), 382
– Control Unit configuration, 125
– no host, 104
K
I Kind, of HL7 query, 263
Icterus, 79
ICUPL^REAL
L
– ASTM header, 159
Linearity, data alarm, 360
– structure, 155
Lipemia, 79
ID for host, of instrument. See Analytical Unit ID, 115
Liquid level detection
IDs
– Sample LLD data alarms, e 602, 375
– See Analytical Unit ID
LIS timeout, 102
– See Calibration ID
LIS2-A2, see ASTM
– See Operator
List
– See Patient ID
– rerun, 391
– See Quality control, control ID
LoB. See Limit of Blank
Immunology module, 45
LoD. See Limit of Detection, 70
Inc.T (data alarm)
Log files
– e 602, 371
– Control Unit communication, 117, 135
Roche Diagnostics
470
– host communication, 117 Mixed mode

Log levels, data manager, 109 – configuring, 104
LoQ. See Limit of Quantitation, 70 – definition, 62
Lot MIXLOW (data alarm)
– calibrator lot number ASTM, 184 – ISE, 350
– quality control ASTM, 161 Modes
– quality control HL7, 232 – batch, 61
– reagent lot number, calibration ASTM, 184 – configuring, 104
– reagent lot number, calibration HL7, 259 – mixed, 62
Low level – order query HL7, 266
– of signal (data alarm), 375 – pass-through, 108
– rack and position, 109
– rack and position with batch mode, 421
M – realtime, 62
MODULAR PRE-ANALYTICS
Manual Rerun Test Selection, 128
– barcodes, 68
Masking
Modules
– ECD segment HL7, 270
– dilution factors ASTM, 164
– EQU segment HL7, 269, 271
– IDs, 115
– example messages, 322
– list, 45
– message structure, 224
– module type, ASTM, 173
– patient results, 270
– module type, HL7, 244
Measurement units
– module type, HL7, calibration, 251
– ASTM, 170
– module type, HL7, QC, 248
– HL7, 241
Mono.E (calibration alarm)
– HL7, QC, 246
– e 602, 382
Measuring cell
Monotony
– temperature alarm, 368
– of curve, 382
Messages
Monotony of Curve, calibration result ASTM, 185
– ASTM low-level, 148
– batch, 61
– batch communication, 154 N
– date and time of ceration, HL7, 227
– date and time of creation, ASTM, 159 na.LHI (data alarm)
– flag for host / data manager, ASTM, 165 – c modules, 361
– Message Control Identifier ASTM, 158 – e 602, 371
– Message Control Identifier HL7, 227 – ISE, 351
– Message Control identifier, HL7 acknowledgment, Name
229 – patient in ASTM, 160
– realtime, 61 – patient in HL7, 230
– realtime communication, 154 New in version, 20
– structure ASTM, 145 No host configuration, 104
– structure in HL7, 223 Notice, definition, 16
– types, 75 Number
– types in HL7, 227 – data type ASTM, 157
– upload one-by-one, 107 – data type in HL7, 226
Micro cups – See also Samples, sample numbers, Sequence
– ASTM order, 162 numbers
– ASTM query, 179
– HL7 SPM segment, 233
– QPD segment HL7, 263
O
Minimal Layer Protocol (MLP), 220
OBS.RR (data alarm)
Minimal Lower Layer Protocol (MLLP), 220
– e 602, 371
Minimum Acceptance Difference
OMLÔ33
– MSH segment, 227
– structure in HL7, 225
Missing Values
On-board stability
– OBS.RM (data alarm), c 702, 361
– OBS.RR (data alarm), c modules, 362
Roche Diagnostics
471
– OBS.RR (data alarm), e 602, 371 – order record ASTM, 164

Open System Interconnection (OSI), HL7, 220 – query record ASTM, 179
Operator – query record HL7, 263
– data manager, ASTM, 172 – TQ-1 segment HL7, 238
– data manager, HL7, 243 Protocols
– data manager, HL7, QC, 247 – ASTM E1381-91 Low Level, 143
– instrument, ASTM, 172 – host connection, 104
– instrument, HL7, 243 – recommendations, 46
– instrument, HL7, QC, 247 – version ASTM, 159
– ISE calibration ASTM, 181 – version HL7, 228
– photometric calibration ASTM, 180 Prozone value
Order query – photometric calibration results ASTM, 180
– ASTM message structure, 155 – photometric calibration results HL7, 252
– diagram, 77
– example with sequence number ASTM, 214
– example with sequence number HL7, 328
Q
– examples ASTM, 213–214
QCErr (QC alarm), 389
– HL7 message structure, 224
Qualitative and quantitative results
– QPD segement HL7, 266
– HL7 patient, 241, 246
Orders
Quality control
– batch, 61
– control ID HL7, 232
– datetime of creation ASTM, 164
– control ID, ASTM, 161
– realtime, 61
– lot ASTM, 161
OUL^R22
– lot HL7, 232
– MSH segment, 227
– name ASTM, 161
– structure in HL7, 223
– name HL7, 232
Over.E (data alarm)
Quantitative results. See Qualitative and quantitative
– c modules, 362
results, 170
– e 602, 372
Query
– ISE, 351
– order query QPD segment HL7, 266
– query type code ASTM, 179
P – query type code HL7, 263
– result query QPD segment HL7, 264
Parity, 122 – test selection in ASTM, 155
Pass-through, 108 – test selection in HL7, 223
Patient ID – test selection QPD segment HL7, 262
– ASTM, 160 – See also Order Query, Result Query, Test selection
– HL7, 230 inquiries
PCUPL^REAL
– structure, 155
R
Photometry, module, 45
Rack and position mode
Pipetting time
– batch test selections, 421
– ASTM, 172
– configuring data manager, 109
– HL7, 243
– sample position, 422
– HL7, QC, 247
Rack ID
Port numbers, recommendations, 121
– ASTM query, 178
Position
– HL7 SAC segment, 235
– sample in ASTM query, 178
– QPD segment HL7, 262
– sample in HL7 query, 262
Rack type
– sample on rack, ASTM order, 162
– ASTM query, 177, 178
– sample on rack, SAC segment HL7, 235
– QPD segment HL7, order query, 267
PreClean
– QPD segment HL7, result query, 265
– insufficient, 376
– QPD segment HL7, test selection, 263
– temperature out of range, 376, 377
– sample lifetime, 67
Pre-dilution, result record ASTM, 169
Racks
Prep.E (calibration alarm), ISE, 382
– calibration, 55
Priority
– ID. See Rack ID
Roche Diagnostics
472
– manual rerun, 55 Request information status code, ASTM, 179

– quality control, 55 Rerun
– routine, 55 – list, 391
– STAT, 55 – query type code ASTM, 179
– type. See Rack type – query type code HL7, 263
Reag.F (data alarm) – test, 59
– e 602, 372 – without barcodes, 418
Reag.H (data alarm) Response times, optimum., 103
– e 602, 372 Result message only for Immunoassay Qualitative
Reag.S (data alarm) tests, 127
– c 701/c 702, 363 Result query
– e 602, 373 – ASTM message structure, 155
– ISE, 351 – diagram, 76
Reag.T (data alarm) – example ASTM, 209–210
– e 602, 373 – example with sequence number ASTM, 211
Reagent code HL7, 259 – example with sequence number HL7, 325
Reagent disk – examples HL7, 323–??
– temperature abnormal, e 602, 373 – HL7 message structure, 224
Reagent expiry date, 259 – QPD segment HL7, 264
Reagent lot number Results
– ASTM, 184 – abnormal flag examples ASTM, 194
– HL7, 259 – abnormal flag examples HL7, 296
– upgrading to 1.04, 456 – abnormal flags ASTM, 171
Reagent serial number – abnormal flags HL7, 242
– HL7, 259 – calibration result code in ASTM header, 159
– upgrading to 1.04, 456 – Calibration. See Calibration results
Reagent set – cobas e flow codes, 413
– ASTM, 173 – code in ASTM header record, QC, 159
– HL7, 248 – completion time, ASTM, 172
Reagent type HL7, 259 – example messages ASTM, 192
ReagEx (data alarm) – example messages HL7, 293
– c modules, 363 – masking, 270
– e 602, 372 – message structure ASTM, 155
Realtime mode (result upload message) – message structure in HL7, 223
– example QC result HL7, 314 – qualitative and quantatitive HL7, 241, 246
Realtime mode (test selection dowload message) – query. See Result query
– configuring, 104 – result comment flag, 174, 175
– definition, 56, 61, 62 – result request code in ASTM header, 159
– diagram, 76 – result upload code in ASTM header, 159
– diagram, message flow, 88 – status ASTM, 171
– example messages ASTM, 192 – status E-module calibration result ASTM, 184
– example QC result ASTM, 204 – status HL7, 243
– messages, 154 – status, QC, HL7, 247
Receiver ID – time available, HL7, 244
– ASTM, 158 – time available, HL7, calibration, 251
– HL7, 227 – time available, HL7, QC, 248
Reference ranges – units ASTM, 170
– ASTM, 171 – units HL7, 241
– HL7, 242 – units, HL7, QC, 246
– QC, HL7, 247 – upload by sample, 131
Reflex test, 59 – upload by test, 131
Repeat delimiter – validation, 80
– ASTM, 146 – value in HL7, patient results, 241, 246
– HL7, 227 Revision history, 3
Repeat limit (data alarm) Routine
– c modules, 363 – order record ASTM, 164
– e 602, 373 – query record ASTM, 179
– ISE, 352 – query record HL7, 263
Repeat test, definition, 59 – sample racks, 55
Roche Diagnostics
473
RS232c cable, 122 – samples with same ID, 67

Rsp1.E (calibration alarm) – SPM segment HL7, patient results, 232
– ISE, 383 – SPM, patient messages, 232
Rsp2.E (calibration alarm) Sample types, 51
– ISE, 383 Samples
RSREQ – barcodes missing, 128
– ASTM header, 159 – clear sample list in rack and position mode, 423
– HL7, 227 – container in query HL7, 263
– structure in ASTM, 155 – datetime of collection ASTM, 164
– structure in HL7, 224 – expired, 65
RSUPL – identifying by sequence number. See Sequence
– ASTM header, 159 numbers
– structure in ASTM, 155 – IDs. See Sample IDs
RSUPL^BATCH – keep position in rack and position mode, 422
– ASTM header, 159 – lifetime, 65
– structure in ASTM, 155 – not found, message in HL7, 225
RSUPL^REAL – position in HL7 query, 262
– ASTM header, 159 – rack and position batch mode, 421
– structure in ASTM, 155 – rack and position identification, 109
– sample container in ASTM order, 162
– sample container in ASTM query, 179
S – sample numbers, 68
– sample position in ASTM query, 178
S1A.E (calibration alarm)
– upload by sample, 131
– c modules, 383
– upload by sample message flow, 90
Safety information, 15
– without barcodes, 68
safety information, 17
Screenshot disclaimer, 6
Samp.? (data alarm)
SD.E (calibration alarm)
– c modules, 364
– c modules, 384
Samp.B (data alarm)
Selection mode, order query HL7, 266
– e 602, 373
Send conc(entration) of chemistry qualitative tests,
Samp.C (data alarm)
126
– c modules, 364
Send message for Immunoassay Quantitative tests,
– e 602, 374
127
– ISE, 352
Send query to host, 104
Samp.O (data alarm)
Sender ID, ASTM, 158
– c modules, 364
Sending application name
– e 602, 374
– ISE, 352
– HL7, 227
Samp.S (data alarm)
Sens.E (calibration alarm)
– c modules, 364
– c modules, 384
– e 602, 374
Sequence numbers
– ISE, 352
– ASTM examples, 432
Sample
– configuring on system, 428
– clot (data alarm), e 602, 374
– example order query ASTM, 214
– volume, decreased/increased, 391
– example order query HL7, 328
Sample clogging (data alarm)
– example result ASTM, 195
– e 602, 374
– example result query ASTM, 211
– ISE, 352
– example result query HL7, 325
Sample IDs
– example test selection ASTM, 191
– barcodes, 68
– example test selection HL7, 292
– instrument sample ID ASTM, 162
– HL7 examples, 434
– lifetime, 65
– instead of barcodes, 53
– order ASTM, 161
– order record ASTM, 162
– QPD segment HL7, order query, 266
– QPD segment HL7, 262, 264, 266
– QPD segment HL7, result query, 264
– query record ASTM, 177, 178
– QPD segment HL7, test selection, 262
– sample IDs compared, 429
– query record ASTM, 177, 178
– SPM, patient messages, 232
– re-using, 65
– warnings and cautions, 430
Roche Diagnostics
474
Serial connections – data type in HL7, 226

– data manager settings, 104 Submodule
– hardware and low-level, 122 – ASTM, 173
Serial number, reagent HL7, 259 – HL7, 244
Serum index check (data alarms) – HL7, calibration, 251
– c modules, 359 – HL7, QC, 248
– e 602, 369 Sys.E (calibration alarm)
– ISE, 348 – e 602, 388
Serum index tests SysR.S (data alarm)
– ASTM, 163 – e 602, 375
– request together, 79 SysR.T (data alarm)
Settings, configuration chart, 436 – e 602, 376
Sex System Error
– patient in ASTM, 160 – calibration result ASTM, 185
– patient in HL7, 230 – calibration result HL7, 255
Short Turn-Around Time. See STAT System time, 69
Sig.E (calibration alarm)
– e 602, 385
Signal
T
– maximum (calibration alarm), e 602, 384
TCP/IP
– minimum (calibration alarm), e 602, 385
– connections, 104
Signal values
– recommendations, 46
– calibration E-module ASTM, 185
Technical limit
– calibration E-module HL7, 255
– data alarm, e 602, 376
SLLD.E (data alarm)
Test availability
– e 602, 375
– Equipment Inventory Request message, 224
SLLD.N (data alarm)
– Equipment Inventory Update message, 223
– e 602, 375
Test selection
Slop.E (calibration alarm)
– batch, 61
– ISE, 385
– definition, 56
Slope
– download message structure ASTM, 155
– download message structure in HL7, 225
– download message type in ASTM header, 159
Specimen type
– message timeout, 102
– ASTM, 165
– not found in HL7, 278
– HL7, 232
– realtime, 61
Standard deviation
– upload message structure ASTM, 155
– photometric calibration results ASTM, 180
– upload message type in ASTM header, 159
– photometric calibration results HL7, 252
– upload messge structure in HL7, 225
Standby bottle
– See also Test selection inquiries
– ASTM, 173
Test Selection Ask in Barcode Read Error, 128
– HL7, 248
Test Selection Inquire Always, 128
– HL7 calibration, 251
Test selection inquiries
Start block, HL7, 220
– examples in ASTM, 190
STAT
– examples in HL7, 289
– cobas® 8100 instrument, 110
– HL7 acknowledgment, 278
– limited STAT handling, 110
– message structure ASTM, 155
– order record ASTM, 164
– message structure HL7, 223
– query record ASTM, 179
– Test selection inquiry, Control Unit option, 127
– query record HL7, 263
– test selection query code in ASTM header, 159
– sample racks, 55
Test Selection Priority Mode, 128
– STAT Test Selection, 128
Test Selection Timeout, 127
Status code, request information, ASTM, 179
Test status
Std.E (calibration alarm)
– test availability message, 273
– c modules, 387
Testcode
– ISE, 386
– E-module calibration results ASTM, 184
Stopbits, 122
– masking message HL7, 270
String
– OBR segment HL7, 237
Roche Diagnostics
475
– OBX segment, QC results, HL7, 245 – MIXSTP (data alarm), 361

– order record ASTM, 163, 164 Units of measurement
– photometric calibration results ASTM, 180 – ASTM, 170
– result record ASTM, 169 – HL7, 241
– SID segment HL7, 259 – HL7, E-module calibration, 255
– TCD segment HL7, 258 – HL7, QC, 246
Tests Universal Service Identifier. See Testcode
– reflex, 59 Unmask message, 270
– repeat, 59 Uploading messages one-by-one, 107
– rerun, 59 UTF-8, 47
– testcode. See Testcode
– type HL7, 259
– upload by test, 131
V
Third-party software, 19
Version
Throttle instrument, 107
– data manager ASTM, 158
Time
– HL7, 228
– calibration result E-module ASTM, 185
VT, HL7 framing, 220
– masking message, 269, 271, 273 W
– message creation ASTM, 159
– message creation HL7, 227 Warning
– order creation ASTM, 164 – definition, 16
– pipetting HL7, 243 Warranty, 6
– pipetting, ASTM, 172 WB.S (data alarm)
– pipetting, HL7, QC, 247 – e 602, 376
– response times, optimum, 103 WB.T (data alarm)
– result available, HL7, 244 – e 602, 376, 377
– result available, HL7, QC, 248
– results available, HL7, calibration, 251
– results, ASTM, 172
X
– sample collection ASTM, 164
X12 of ANSI, 141
– specimen collection HL7, 233
– system time, 69
Timeouts
– diagram, 102
– Host, 102
– LIS, 102
– test selection, 102
– test selection, on Control Unit, 127
Trace file, on Control Unit, 135
Trademarks, 6
TSDWN
– structure in ASTM, 155
TSREQ
– HL7 MSH segment, 227
– structure in HL7, 223, 224
TSUPL
Ultrasonic mixer
– MIXLOW (data alarm), 361
Roche Diagnostics

Cobas 8000 Host Interface Manual (1.06.01)

Uploaded by

Copyright:

Available Formats

Cobas 8000 Host Interface Manual (1.06.01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cobas 8000 Host Interface Manual (1.06.01)

Uploaded by

Copyright:

Available Formats

cobas® 8000 data manager

Host Interface Manual

Software version 1.06.01

Manual version Software version Revision date Main changes

Manual version Software version Revision date Main changes

u For guidance about changes to the interface, see:

Every effort has been made to ensure that the information

Roche Diagnostics International Ltd. reserves the right to

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

The Safety Manual contains important safety

The Operator’s Manual focuses on routine operation

The Online Help contains the content of the Operator’s

The PC manufacturer’s manual contains all information

Training Do not carry out operation tasks or maintenance actions

Screenshots The screenshots in this publication have been added

Warranty Any customer modification to the system renders the

For conditions of warranty, contact your local sales

Always leave software updates to a Roche Service

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

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

This open source and commercial software and the

Please note that the respective authorization is no longer

Trademarks The following trademarks are acknowledged:

COBAS, MODULAR, and MODULAR ANALYTICS EVO

All other trademarks are the property of their respective

Approvals The following mark demonstrates compliance:

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

Roche Diagnostics GmbH

Roche Diagnostics Corporation

Publication information 3 Configuration

9 ASTM communication examples 12 HL7 acknowledgment handling

19 Preparing the host communication

20 Text encoding tables

The cobas® 8000 data manager is a core component of

Symbols and abbreviations

Symbols used in the publication

Abbreviations The following abbreviations are used.

Safety information classification

Safety messages are classified according to ANSI Z535.6.

The safety alert symbol by itself (without a signal word) is

The following symbols and signal words are used for

According to ANSI Z536.6 there is an additional hazard

Pay careful attention to the following safety information.

System safety Failure to observe the following safety information may

What is new in publication version 16

Differences between version 1.06 and

Differences between version 1.05.xx and

Field Description Version 1.05.xx Version 1.06

Field Description Version 1.05.xx Version 1.06

Field Description Version 1.05.xx Version 1.06

Field Description Version 1.05.xx Version 1.06

Field Description Version 1.05.xx Version 1.06

Upgrading from version 1.04.00 to version

Field Description Version 1.04 Version 1.05

Field Description Version 1.04 Version 1.05

Field Description Version 1.04 Version 1.05

y Changes to HL7 messages in data manager 1.05

Upgrading from version 1.03.xx to version

q There is no difference in the values of the HL7 or