Bidirectional Computer Interface

Specification (RS232)
514724-1EN1 – (08/2012)

For Internal Use Only

[06]
Liability Disclaimer

bioMérieux, Inc. makes no express or implied warranty regarding this manual, its quality,
performance, or appropriate use regarding any type of specific procedure.

Furthermore, this manual may be modified by bioMérieux without notice and without implying
any obligation or liability on the part of the company.

Intellectual Property

bioMérieux, the blue logo, Advanced Expert System, BacT/ALERT, BacT/View, bioLIAISON,
OBSERVA, and VITEK are used, pending, and/or registered trademarks belonging to
bioMérieux, Inc.

AIX is a registered trademark of International Business Machines Corporation.

CLSI is a registered trademark of Clinical Laboratory and Standards Institute, Inc.

© 2012 bioMérieux, Inc. All rights reserved.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval

system, or translated into any language (human or computer) in any form, or by any means
whatsoever, without the prior express written permission of bioMérieux, Inc.

Intended Audience

This manual is intended for bioMérieux staff only.

 Table of Contents

1 Overview of BCI.......................................................................................... 1-1

1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.1.1 Product References and Terminology . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.2 System Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.2.1 Communications Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.2.2 Applications Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.3 Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.3.1 Communications Layer Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
1.3.2 Demographics Download Program . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.3.3 Result Upload Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.3.4 Utilities Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.4 Level-to-Level Message Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
1.4.1 Communications Level Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.4.2 Applications Level Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.5 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

2 bioMérieux Communications Protocol .................................................... 2-1

2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2 Basic Message Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.2.1 Records and Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.3 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.4 Communications Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.4.1 Communications Level Message Exchange Protocol . . . . . . . . . . . . 2-4
2.4.2 Protocol Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.4.3 Alternate Communications Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.4.4 ASTM E1381 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.5 Checksum Field Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
2.6 Examples of Message Exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
2.7 Cable Specifications for the BMX Computer Host Port. . . . . . . . . . . . . . . . . 2-13

3 Download Specifics ................................................................................... 3-1

3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 Download Applications Layer Message Types . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2.1 Patient Demographic Message Type (mpr) . . . . . . . . . . . . . . . . . . . . 3-2
3.2.2 Out of Service (oos) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2.3 Back in Service (bis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.3 Download Applications Layer Field Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.3.1 Table Field Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3.3.2 Demographic Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.3.3 Blood Culture Order Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.3.4 Test Result Fields (All Test Types) . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.3.5 Test Result Fields for Specific Tests . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.4 Message Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

514724-1EN1 Table of Contents i

Bidirectional Computer Interface Specification for VITEK® Systems

4 Upload Specifics ........................................................................................ 4-1

4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Upload Applications Layer Message Types . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2.1 Test Results Literal Format (rsl). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2.2 Out of Service (oos) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.3 Back in Service (bis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.4 Auto-synchronize Organisms (org) . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.5 Auto-synchronize Antibiotics (abx). . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.3 Upload Applications Layer Field Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.3.1 Demographic Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.3.2 Test Result Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.3.3 Test Result Fields for Specific Tests . . . . . . . . . . . . . . . . . . . . . . . . 4-12
4.3.4 Upload Applications Message Format . . . . . . . . . . . . . . . . . . . . . . 4-16
4.3.5 Descriptions of Fields in the Record Format . . . . . . . . . . . . . . . . . . 4-17
4.4 Test Result Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

5 BCI Utilities (VITEK® and VITEK® 2 Only)................................................ 5-1

5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.2 BCI Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.3 Port Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.3.1 Possible Port Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
5.4 Protocol Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.4.1 Communications Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5.4.1.1 Record and Field Separators . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.4.2 bioMérieux Literal Protocol Parameters . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.4.2.1 End of Record <CR> <LF>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.4.2.2 Delays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.4.2.3 Retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.4.2.4 Timeouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.4.2.5 Character Set Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.4.2.6 Modem Dial String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.5 BCI Upload Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.5.1 Upload Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.5.1.1 Field Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.5.1.2 Case of Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.5.1.3 Miscellaneous Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.5.1.4 CAR Rules (bioLIAISON®). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.5.1.5 Deduced Drugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.5.1.6 Leading Zeros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.5.1.7 Date Format Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.5.2 Upload Fields to Transmit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.5.3 BMX Data Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.5.4 Enable Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.5.5 Disable Upload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.5.6 Host In Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.5.7 Host Out Of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.6 BCI Download Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

514724-1EN1 Table of Contents ii

Bidirectional Computer Interface Specification for VITEK® Systems

5.6.1 Download Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

5.6.1.1 Duplicate Demographics Update . . . . . . . . . . . . . . . . . . . . . . . . 5-9
5.6.1.2 Initialize Specimen Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
5.6.1.3 Date Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.6.2 Download Fields to Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.7 Running BCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.7.1 Start BCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.7.2 Stop BCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.7.3 View Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.8 Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.8.1 Upload Transaction Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.8.2 Download Transaction Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.8.3 Status Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.8.4 Communications Data Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.8.5 Download Error Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.9 Configuration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.9.1 Host Field Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.9.1.1 Drug Field Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.9.1.2 Organism Field Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.9.1.3 Physicians and Specimen Source Translations . . . . . . . . . . . . 5-13
5.9.2 Transaction Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

A Field Type Definitions ................................................................................A-1

B ASCII Characters and Other Values .........................................................B-1

C Recommended Host Features...................................................................C-1

D Antimicrobial MICs and Categories..........................................................D-1

E Bionumber Descriptions............................................................................E-1

F Reference Tables........................................................................................ F-1

F.1 Test Group Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1
F.2 Instrument Code Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1
F.3 Blood Test Download Result Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1

514724-1EN1 Table of Contents iii

Bidirectional Computer Interface Specification for VITEK® Systems

514724-1EN1 Table of Contents iv

 1 Overview of BCI

1.1 Introduction

bioMérieux manufactures instruments for microbiological analysis and data collection. This
document contains detailed information about the bidirectional software used to interface
between VITEK®, VITEK® 2, VITEK® 2 Systems, and OBSERVA® systems and Laboratory
Information System (LIS) host computers.

Except where noted, this document applies to VITEK®, VITEK® 2, VITEK® 2 Systems, and
OBSERVA® systems.

IMPORTANT: For VITEK® and VITEK® 2, this specification covers BCI versions R06.01
and higher. For VITEK® 2 Systems, BCI is integrated into the VITEK® 2
Systems software and this specification covers VITEK® 2 Systems
software version 05.01 and higher. For OBSERVA®, this specification
covers OBSERVA® 04.02 and higher.

Instruments mentioned in this specification can be interfaced as stand-alone systems or in

combination with several bioMérieux or other vendor instruments.

1.1.1 Product References and Terminology

This is a partial listing of product names and acronyms used throughout this specification.

Table 1-1: bioMérieux Acronyms

TERM DEFINITION

BacT/ALERT® bioMérieux blood culture diagnostic system. Consists of both

instrument and software (BacT/VIEW® or OBSERVA®) components.

BacT/VIEW® bioMérieux database software (BacT/ALERT® only). With the

MicroNET option (BacT/VIEW® only), BacT/VIEW® can send blood
culture results to bioLIAISON® using BCI.

BCI Bidirectional Computer Interface. bioMérieux computer interface

software.

bioLIAISON® bioMérieux database software (VITEK® and VITEK® 2 only).

bmx bioMérieux

Download Data transfer from the host computer to a bioMérieux computer.

OBSERVA® bioMérieux database software (VITEK® 2 Systems and

BacT/ALERT® only).

Upload Data transfer from a bioMérieux computer or instrument to a host

computer.

VITEK® (VTK) bioMérieux system for bacteriological analysis. Consists of both

instrument and software components.

514724-1EN1 Overview of BCI 1-1

Bidirectional Computer Interface Specification for VITEK® Systems

Table 1-1: bioMérieux Acronyms (Continued)

TERM DEFINITION

VITEK® 2 bioMérieux system for microorganism identification and antimicrobial

susceptibility testing (ID/AST). Consists of both instrument and
software components.

VITEK® 2 bioMérieux system for microorganism identification and antimicrobial

Systems susceptibility testing (ID/AST). Consists of both instrument and
software components. Includes VITEK® or VITEK® 2 Compact with a
personal computer (PC) workstation.

Workstation IBM computer with an AIX® operating system (VITEK® and

VITEK® 2) or a personal computer with a Windows® operating system
(VITEK® 2 Systems and OBSERVA®).

1.2 System Design

Figure 1-1: Overview of System Design

Host 2 Host 3
Host 1

bioMérieux Computer

BCI is organized into two independent layers. The lowest is a communications layer which
establishes sessions and ensures that raw data transmissions are free of errors.

Above that is an applications layer responsible for transmitted message content and for
updating the database on the bioMérieux computer. Between these two layers is an interface
that defines the interaction of the layers with each other.

514724-1EN1 Overview of BCI 1-2

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 1-2: Two Layers of the BCI Interface

bioMérieux Computer Host

Applications Applications
Layer Layer

Messages from Host Messages from Host Messages from Messages from
bmx Computer bmx Computer

Communications Communications
Layer Layer

1.2.1 Communications Layer

This layer controls the physical and logical communication with a host computer. It includes a
set of rules (the protocol) for error free exchange of messages between the bioMérieux
computer and the host. Checksums in the communications layer detect transmission errors.

1.2.2 Applications Layer

Virtual communication between the bioMérieux computer and host is established through the
applications layer. Because this layer is only concerned with transmitted message content, the
details of the communications protocol are transparent.

1.3 Software Components

1.3.1 Communications Layer Program

This program controls the actual data transfer process. All data is presented as eight-bit
values within a range of 0 to 255. Values between 0 and 127 are defined by the ASCII
standard. Values between 128 and 255 are defined by either ISO-8859-1 or IBM-850 (VITEK®
and VITEK® 2 only).

Note: Kanji character sets in VITEK® and VITEK® 2 use the extended UNIX codes
(EUC) although Japanese customers should still select ISO-8859-1.

Note: In VITEK® 2 Systems and OBSERVA®, data is transferred in either

ISO-8859-1, Shift-JIS, or UTF-8. Kanji character sets should typically
choose Shift-JIS as the encoding.

BCI users can modify configuration items such as baud rate, time outs, and field separators.

514724-1EN1 Overview of BCI 1-3

Bidirectional Computer Interface Specification for VITEK® Systems

1.3.2 Demographics Download Program

The demographics download program controls the processing of data downloaded from a
host. Patient, specimen, and exam information is stored in the bioMérieux computer database.

Note: In VITEK® and VITEK® 2, information can be routed to other systems.

Note In VITEK® and VITEK® 2, ID, susceptibility, and smear tests and results that
follow an exam can be downloaded and transferred to the bioLIAISON®
database.

Downloaded data can be sent to the bioMérieux computer at any time. Updates to existing
patient, specimen, exam demographics, tests, and results are allowed, but specimen
demographics must always have corresponding patient and exam identifiers.

Note: It is assumed that all information from the host computer is correct, except
that in OBSERVA®, the host computer can add to, but cannot change,
existing results.

1.3.3 Result Upload Program

The result upload program controls transmission of results to the host computer(s). Results
upload to the host with enough demographic information to link with the correct patient,
specimen, exam, or test on the host computer(s). If necessary, results can be retransmitted.

1.3.4 Utilities Program

This program allows BCI users to configure a bioMérieux computer with the appropriate
communications settings for compatibility with a host. It also allows them to transmit test
patterns, display communications data on the screen, and access status and error logs.

1.4 Level-to-Level Message Definitions

The bioMérieux and host computers exchange messages between both the communications
and applications layers.

514724-1EN1 Overview of BCI 1-4

Bidirectional Computer Interface Specification for VITEK® Systems

1.4.1 Communications Level Messages

Table 1-2: BCI Supported Protocols

Communication Applicable
Documentation
Protocol Instruments
ASTM E1381 VITEK® and VITEK® 2 Documentation for the ASTM E1381
protocol is available in the ASTM
Standards.
bioMérieux Literal VITEK®, VITEK® 2, For information about bioMérieux
and bioMérieux VITEK® 2 Systems, communication protocols, see the
Alternate and OBSERVA® bioMérieux Communications Protocol
section of this document.

1.4.2 Applications Level Messages

Applications level messages can be sent from the host computer to the bioMérieux computer
or from the bioMérieux computer to the host.

There are three types of applications messages from the host to a bioMérieux computer:
patient information (mpr), out of service (oos), and back in service (bis).

Table 1-3: Host to bioMérieux Computer Messages

Message Type Description

Patient This message indicates a download of patient, specimen, and exam
Information demographics. It can also include tests and results if programmed
(mtmpr) optionally by an LIS.
Out of Service This message tells the bioMérieux computer that the host is going out
(mtoos) of service and will not respond to any messages. The bioMérieux
computer can continue to receive messages from the host, but it will
not attempt to transmit.
Application messages from the bioMérieux computer to the host
queue up for later transmission.
Back in Service This message tells the bioMérieux computer that the host is back in
(mtbis) service. Upon receiving this message, the bioMérieux computer
resumes transmission and sends any queued messages.

There are also three types of messages a bioMérieux computer can send to the host: results
(rsl), out of service (oos), and back in service (bis).

Table 1-4: bioMérieux Computer to Host Messages

Message Type Description

Results Results from instruments transmit in a literal format. Demographics
(mtrsl) can be sent with results.
Out of Service This message tells the host that the bioMérieux computer is going out
(mtoos) of service. During this time, the bioMérieux computer will not respond
to downloads from the host, but it can continue sending messages to
the host.
Back in Service This message tells the host that the bioMérieux computer is ready to
(mtbis) receive downloads.

514724-1EN1 Overview of BCI 1-5

Bidirectional Computer Interface Specification for VITEK® Systems

Note: For VITEK® or VITEK® 2, BCI R06.01 and higher have a routing feature. A
downloaded mtmpr can be routed back to another port as an upload. Neither
VITEK® 2 Systems nor OBSERVA® support this feature.

1.5 Hardware Requirements

For VITEK® or VITEK® 2, BCI runs on any bioMérieux workstation that has one or more
available RS-232 serial TTY ports.

For VITEK® 2 Systems and OBSERVA®, BCI runs on a bioMérieux PC that has one or more
serial COM ports.

Note: BCI can use one or more ports, with each capable of uploading and
downloading.

Note: VITEK® 2 Systems is only validated for connection to a single LIS.

514724-1EN1 Overview of BCI 1-6

 2 bioMérieux Communications Protocol

2.1 Introduction

BCI uses either the ASTM E1381 protocol (VITEK® and VITEK® 2 only) or its own bioMérieux
communications protocol. This specification only describes the bioMérieux communications
protocol.

Note: VITEK® 2 Systems and OBSERVA® do not support the ASTM E1381
protocol for BCI Communication.

Note: For information on the ASTM E1381 protocol, see the ASTM E1381
documentation or the CLSI® standard LIS1-A.

The bioMérieux communications protocol works with BCI to ensure an accurate data flow
between a bioMérieux computer and instruments and a host (LIS) computer. It is responsible
for establishing sessions, data transfer, and error detection.

2.2 Basic Message Content

• Either computer can begin a session by transmitting the ASCII control character <ENQ>. If
the computer receiving the inquiry is ready to receive data, it responds with the
acknowledgment character <ACK>. If it is not ready, it sends a <NAK> character.
Sessions end when one of the computers receives an <EOT> character.
• Data transfer between the host and bioMérieux computer takes place using
communications messages (data packets). A communications message begins with the
ASCII start character <STX>.
• Subsequent records begin with the ASCII record separator character <RS> or the group
separator <GS>. The <RS> records contain the text of the message. A checksum must
follow the <GS> separator.
• Communications messages end with the <ETX> character.
• There can be only one <STX> and <ETX> character per data packet. At least one <RS>
record must be in the packet. There will always be one <GS> record per packet.
• Records can be terminated with the ASCII carriage return/line feed characters
<CR><LF>. Each record type has a fixed format as shown in the following diagram.

514724-1EN1 bioMérieux Communications Protocol 2-1

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 2-1: BCI Protocol

STX CR LF

RS CR LF
Message Text

RS CR LF
Message Text

RS CR LF
Message Text

GS Checksum CR LF

ETX CR LF

2.2.1 Records and Characters

Table 2-1: Record and Character Descriptions

Record/
Description
Character
STX (CR/LF) Signals the start of a message packet. It is a single character record that
expects no response from the target computer.
ETX (CR/LF) Signals the end of a message packet. It is also a single character record
that expects no response from the target computer.
RS (CR/LF) This record contains specific message information of up to 80 printable
ASCII characters per record. There can be any number of <RS> records in
a data packet. It does not expect a response from the target computer.
GS (CR/LF) This record contains a checksum that determines if the packet was received
properly. Calculation of checksums begin with the first <RS> and end with
the <GS> character.
Checksums are calculated by adding the values of appropriate characters,
truncating the most significant part of the result (leaving an 8-bit number),
and converting this value to two ASCII characters representing the
hexadecimal value of the number. An <ACK> or <NAK> is always expected
in response to this record type.
See Checksum Field Format on page 2-10 for more information.
ENQ (CR/LF) This is the line request character. It establishes a session between the
sending and receiving computers.
EOT (CR/LF) The sending computer sends this character to the receiver to signal the end
of the session.
ACK Upon receipt of a <GS> record, this character is sent to indicate successful
transmission of the data packet. It is also used by the receiver to respond to
receipt of an <ENQ>.
NAK This signals a negative response when a session is not possible or when a
transmission error was detected by a bad checksum or parity error.

514724-1EN1 bioMérieux Communications Protocol 2-2

Bidirectional Computer Interface Specification for VITEK® Systems

2.3 Terminology

Table 2-2 lists basic and bioMérieux-specific terms and concepts used throughout this
specification.

Table 2-2: Terms and Descriptions

Term Description
Session A session consists of a connection between the host and a bioMérieux
computer. Data transfer in a single session can only go in one direction at
a time. The initiator of the session is the sender and the other computer is
the receiver. The ASCII line request character <ENQ> starts the session.
<EOT> signals the end of the message and session.
Applications Level The bioMérieux computer will never send more than one applications level
Message message per session, but it can receive more than one per session.
An applications level message contains patient, specimen, and exam
demographics and results. It must always be complete so that the
receiving applications layer can process the message correctly. The
applications level message starts with mt and ends with either the next mt
(if there are multiple applications level messages per session) or with an
<EOT>, zz, or <GS>.
Communications The communications layer sends an applications level message through
Level Message one or more communications level messages. The communications layer
divides the applications message into 1,920 character blocks and sends
each block consecutively. Adding the ASCII control characters <STX>,
<RS>, <GS>, and <ETX> to each block of the applications level message
creates the communications level messages. These characters describe
the beginning and end of a communications level message and establish
control of transmission errors.
A communications level message always has an <STX> indicating the
start of the message and one <ETX> indicating the end. Each block is
further subdivided by the <RS> character into records from one to 80
characters long. The <GS> character marks the beginning of transmission
error control information. In order to handle transmission errors effectively,
there is always one <GS> character in a communications level message.
Record A communications level message consists of one or more records. All
records begin with one of the following ASCII control characters: <STX>,
<ETX>, <RS>, or <GS>. A <RS> record contains 1 to 80 ASCII
characters. Each record type can be terminated by the new line sequence
<CR><LF>.
The new line sequence is optional and not included in the size of the
record.
Packet All records associated with a <GS> record are called a packet. At the end
of a packet, the sending computer waits for the receiver to send an
acknowledgment that it received the packet.
Field A field is a discrete unit of information such as a patient name, sex, or
primary physician. Each field is preceded by a code that describes the
type of field and also implies its length. All fields end with one to three
user-defined terminating characters (chosen from a subset of ASCII
characters). Each field has a maximum length in characters. BCI will
accept data that is less than or equal to the maximum number of allowable
characters. Most fields that are longer than the number of significant
characters are truncated and the text left-justified.
The only exception is the exam ID (ci), which is truncated and right-
justified.

514724-1EN1 bioMérieux Communications Protocol 2-3

Bidirectional Computer Interface Specification for VITEK® Systems

2.4 Communications Protocol

2.4.1 Communications Level Message Exchange Protocol

• The session-oriented protocol used for communication between the host and bioMérieux
computer permits transmission in one direction at a time.
• A session is established in a given direction and must end before the initiation of another
session. This creates a half-duplex communication.
• Either computer can initiate a session by sending the ASCII line request character
<ENQ>. When the receiving computer gets the <ENQ>, it responds with the positive
acknowledgment character <ACK> or the negative acknowledgment <NAK>.
• BCI uses a “last master delay” protocol where the BCI computer waits before transmission
of another <ENQ>. This prevents BCI from continuously controlling the line. The time is in
seconds and can be defined by the user.
• The bioMérieux computer expects the host to implement a last master delay time to allow
the bioMérieux computer to request the line between each host downloaded message.
• All sessions end when the initiating computer sends the ASCII end of transmission
character <EOT>.

2.4.2 Protocol Examples

In the following examples, mtxxx refers to the beginning of a generic applications level
message. The Xs which follow represent the rest of the application message.

Example 1: Successful Transmission by the Host Computer

In this example, the host computer initiates a session by sending an <ENQ> to and receiving
an <ACK> from the bioMérieux computer. The host then begins transmitting data records
<RS>. The bioMérieux computer sends an <ACK> for every checksum record received
correctly. This example shows only a single applications level and communications level
message transmitted in the session.

Figure 2-2: Successful Transmission by Host Computer

<ENQ>
<ACK>
<STX>
<RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

<RS> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

<GS>nn
Host bioMérieux
<ACK>
Computer Computer
<ETX>
<EOT>

514724-1EN1 bioMérieux Communications Protocol 2-4

Bidirectional Computer Interface Specification for VITEK® Systems

Example 2: Successful Transmission by the bioMérieux Computer

A successful transmission by the bioMérieux computer proceeds the same way as one
initiated by the host. This also shows a single applications level and communications level
message session.

Figure 2-3: Successful Transmission by bioMérieux Computer

<ENQ>
<ACK>
Communications Level Message 1
<STX>
<RS>mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

<RS> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
<GS>nn
<ACK>
<ETX>
Communications Level Message 2
<STX>
bioMérieux Host
Computer <RS> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Computer

<RS> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
<GS>nn
<ACK>
<ETX>
<EOT>

Example 3: Multiple Communications Level Messages in a Session

This example shows two communications level messages for one application packet.

IMPORTANT: If sending multiple packets per session that are > 1920 characters, please
contact your local bioMerieux Support representative. Additional information
may be necessary if utilizing this feature.

Figure 2-4: Multiple Communications Level Messages in a Session

<ENQ>
<ACK>
<STX>
<RS>mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

<RS> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

<GS>nn bioMérieux
Host <ACK> Computer
Computer <ETX>

<EOT>

514724-1EN1 bioMérieux Communications Protocol 2-5

Bidirectional Computer Interface Specification for VITEK® Systems

Example 4: Multiple Application Messages in a Session

This example shows two applications level messages in one communications packet.

IMPORTANT: If sending multiple messages per session that are > 1920 characters, please
contact your local bioMerieux Support representative. Additional information
may be necessary if utilizing this feature.

Figure 2-5: Multiple Application Messages in a Session

<ENQ>
<ACK>
<STX>
Applications Level Message 1
<RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Applications Level Message 2

<RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
bioMérieux
<GS>nn Host
Computer
<ACK> Computer
<ETX>
<EOT>

Example 5: Transmission Collision

A collision occurs when both computers try to establish a session simultaneously. When this
happens, the bioMérieux computer drops its request and responds to the host with an <ACK>.

Figure 2-6: Transmission Collision

<ENQ> <ENQ>
<ACK>
<STX>
<RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

<RS> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

<GS>nn
Host <ACK> bioMérieux
Computer <ETX> Computer
<EOT>

Example 6: Transmission Failure — Negative Acknowledgment to an Inquiry

If either computer receives a <NAK> to an <ENQ>, it should wait for a specified time and try
again. The computer reports a failure after a user specified number of unsuccessful attempts.

514724-1EN1 bioMérieux Communications Protocol 2-6

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 2-7: Negative Acknowledgement to an Inquiry

<ENQ>
<NAK>
Waiting
<ENQ>
<NAK>
Waiting
Host bioMérieux
<ENQ>
Computer <NAK>
Computer

Report Failure

Example 7: Transmission Failure — No Response to an Inquiry

When neither computer receives an <ACK> or <NAK> to an <ENQ>, it should wait for a
specified time and try again. After a user specified number of unsuccessful attempts, it should
report a failure.

Figure 2-8: No Response to an Inquiry

<ENQ>
Waiting
<ENQ>
Waiting

<ENQ> bioMérieux
Host Waiting
Computer
Computer
Report Failure

Example 8: Transmission Failure — Faulty Checksum with Literal Protocol

When a checksum is incorrect, the receiving computer responds to the checksum record with
a <NAK>. Upon receiving this, the sender retransmits the entire data packet. If the checksum
fails again, the sender tries again. The sender abandons the transmission and logs an error
after a set number of unsuccessful attempts.

Figure 2-9: Faulty Checksum with Literal Protocol

<ENQ>
<ACK>
<STX>
<RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
<GS>nn
<NAK>
Waiting
<RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Host bioMérieux
Computer <GS>nn Computer
<ACK>
<ETX>
<EOT>

514724-1EN1 bioMérieux Communications Protocol 2-7

Bidirectional Computer Interface Specification for VITEK® Systems

Example 9: Faulty Checksum with Alternate Protocol

The bioMérieux computer will accept transmissions in this format from the host computer. It
allows the host to repeat an alternate protocol <STX> when it receives a <NAK> to a <GS>
record.

Figure 2-10: Faulty Checksum with Alternate Protocol

<ENQ>
<ACK>
<STX>
<RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
<GS>nn
<ETK>
<NAK>
Waiting
<STX> bioMérieux
Host Computer
Computer <RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
<GS>nn
<ETX>
<ACK>
<EOT>

Example 10: End of Transmission by the bioMérieux Computer

When the bioMérieux computer encounters certain error conditions, it may respond with an
<EOT>. This is a signal to the host that the bioMérieux computer is ending the current
session.

Figure 2-11: End of Transmission

Condition 1
<ENQ>
<ACK>
Time Out
<EOT>

Condition 2
<ENQ>
<ACK>
<STX>
<RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
<GS>nn
<NAK>
Waiting

<RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX bioMérieux
Host
Computer <GS>nn Computer
<NAK>
Retry Limit Reached
<EOT>

Condition 3
<ENQ>
Time Out
<EOT>
<ENQ>
Time Out
<EOT>

514724-1EN1 bioMérieux Communications Protocol 2-8

Bidirectional Computer Interface Specification for VITEK® Systems

2.4.3 Alternate Communications Protocol

To accommodate some LIS computers, BCI provides an alternate communications protocol
and uses a different <STX> and <ETX> checksum sequence.

When a checksum is incorrect and one of the computers receives a <NAK> or no response,
the retransmission begins with an <STX>.

The <ETX> is sent immediately after the checksum <GS> record instead of after receipt of an
<ACK>.

Figure 2-12: Alternate Protocol with Correct Checksum

<ENQ>
<ACK>
<STX>
<RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
<GS>nn
<ETX>
Host <ACK> bioMérieux
Computer Computer
<EOT>

Figure 2-13: Alternate Protocol with Faulty Checksum

<ENQ>
<ACK>
<STX>
<RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
<GS>nn
<ETX>
<NAK>
Waiting
<STX>
bioMérieux
Host <RS> mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Computer
Computer <GS>nn
<ETX>
<ACK>
<EOT>

2.4.4 ASTM E1381 Protocol

Note: This protocol is only available for VITEK® and VITEK® 2.

514724-1EN1 bioMérieux Communications Protocol 2-9

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 2-14: ASTM 1381 Protocol (VITEK® and VITEK® 2 Only)

<ENQ>
<ACK>
<STX> fn
mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ( 1-7, 0)
<ETB>nn <CR><CF>
<ACK>
<STX> fn
mtXXX|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX bioMérieux
Host XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Computer
Computer <ETX><nn><CR>CLF>
<ACK>
<EOT>

Note: fn = frame number (1-9, then 0-9); nn = checksum

2.5 Checksum Field Format

The checksum consists of a two-digit ASCII representation of an eight-bit number. This

number is calculated by adding the value of all characters beginning with the first <RS> record
and ending with the <GS> character. The number is then truncated, leaving the least
significant eight bits which convert to two ASCII hexadecimal characters.

Figure 2-15 applies to incoming and outgoing checksums. (It also shows the use of record
terminators.)

514724-1EN1 bioMérieux Communications Protocol 2-10

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 2-15: Checksum Field Format

Received data:
<STX> <CR> <LF> 8 bit Binary
Character
<RS> <HELLO> <CR> <LF> Code
<GS> c6 <CR> <LF>
5 00011110

Characters in the checksum calculation: H 01001000

<RS>< HELLO> <CR> <LF> E 01000101

<GS>
L 01001100
L 01001100
Checksum Calculation:
O 01001111
<CR> 00001101
<RS> + H =
0000000000011110 + 01001000 = 0000000001100110 <LF> 00001010
0000000001100110 + E =
0000000001100110 + 01000101 = 0000000010101011 <GS> 00011101
0000000010101011 + L =
0000000010101011 + 01001100 = 0000000011110111
0000000011110111 + L =
0000000011110111 + 01001100 = 0000000101000011
0000000101000011 + O =
0000000101000011 + 01001111 = 0000000110010010
0000000110010010 + <CR> =
0000000110010010 + 00001101 = 0000000110011111
0000000110011111 + <LF> =
0000000110011111 + 00001010 = 0000000110101001
0000000110101001 + <GS> =
0000000110101001 + 00011101 = 0000000111000110

Truncated 8 bit result = 11000110

Note: The bioMérieux computer always sends checksum characters in lower case,
but it can accept both upper and lower case.

2.6 Examples of Message Exchanges

The following examples show the complete exchange that takes place during message
transmission. Each example contains one applications level message and one
communications level message per session. (These are bracketed by <STX> and <ETX>.)

In Figure 2-18, the applications level message has more than 80 characters, so the
communications layer must send multiple <RS> records. The applications layer associated
with the <RS> record is shown to its left and follows the <RS> character in the data flow.

514724-1EN1 bioMérieux Communications Protocol 2-11

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 2-16: Patient Demographics Sent from Host to bioMérieux Computer for ID or
Susceptibility Test
<ENQ>
<ACK>
<STX>

<RS> mtmpr|pi123|pnDoe,Jane|si|ci1234|ctbcilnk|

<GS>nn
Host <ACK> bioMérieux
Computer
Computer <ETX>
<EOT>

Figure 2-17: Patient Test Information Sent from Host to bioMérieux Computer for a
Blood Culture (VITEK® and VITEK® 2 Only)
<ENQ>
<ACK>
<STX>

<RS> mtmpr|pi123|pnDoe,John|si|ci1234|tbA0025H0|

<GS>nn bioMérieux
Host <ACK> Computer
Computer
<ETX>

<EOT>

Figure 2-18: VITEK® ID Test Results Sent to Host from bioMérieux Computer
<ENQ>
<ACK>
<STX>

<RS> mtrsl|pi123|pnDoe,Jane|si|ci1234|ctbcilnk|
rtgni|rnGram Negative Identification|
<RS>o1promir|o2Proteus mirabilis|zz|

<GS>nn
Host bioMérieux
Computer <ACK> Computer
<ETX>
<EOT>

514724-1EN1 bioMérieux Communications Protocol 2-12

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 2-19: Blood Test Results Sent to Host from bioMérieux Computer (VITEK® and
VITEK® 2 Only)
<ENQ>
<ACK>
<STX>

<RS>mtrsl|pi123|pnDoe,John|si|ci1234|ta|
tbA0025H0|rd02/03/1994|re10|ripositive|zz|

<GS>nn
Host bioMérieux
<ACK>
Computer Computer
<ETX>
<EOT>

Figure 2-20: Susceptibility Test Results Sent to Host from bioMérieux Computer
<ENQ>
<ACK>
<STX>

<RS> mtmpr|pi123|pnDoe,Jane|si|ci1234|ctextypl|
rtgns-ua|a1am|a332|a4S|a1cf|a316|a4R|

<GS>nn
Host bioMérieux
<ACK>
Computer Computer
<ETX>
<EOT>

2.7 Cable Specifications for the BMX Computer Host Port

Data transmits on an asynchronous serial line that conforms to RS-232 voltage specifications.
bioMérieux supplies the interface cabling, but LIS vendors may provide their own. The
interface to the host computer determines cable configurations.

514724-1EN1 bioMérieux Communications Protocol 2-13

Bidirectional Computer Interface Specification for VITEK® Systems

Table 2-3 shows designated uses for pins on the bioMérieux cable.

Table 2-3: bioMérieux Cable Pins

DB 25 - CC1 or
Code Name bioMérieux Computer Use
higher
2 TD Transmit Data bioMérieux computer transmitted data
3 RD Receive Data bioMérieux computer received data
4 RTS Request to Send Asserted by bioMérieux computer1
5 CTS Clear to Send
6 DSR Data Set Ready
7 SG Signal Ground Common ground with host
8 CD Carrier Detect
20 DTR Data Term Ready Asserted by bioMérieux computer1

1
Asserted (positive) means greater than +3 V with respect to Signal Ground.

Note: Pins 2 and 3 may need to be crossed to ensure that what is transmitted data
for the bioMérieux computer is received data for the host. To do this, use a
null modem.

514724-1EN1 bioMérieux Communications Protocol 2-14

 3 Download Specifics

3.1 Introduction

When setting up systems to work with BCI, keep these points in mind:

• Download applications messages are divided into fields and must be logically complete.
The first field is the message type, which dictates the number and types of remaining
fields in a message.
• A complete message is made up of the message type and all its related fields.
• Data is separated into five groups: patient, specimen, culture (or exam), tests, and results.
Each group contains a specific set of fields.
• Each field has a fixed size in the database. If the database receives a value larger than its
fixed size, the field will be truncated to fit. All fields are left-justified and truncated except
the exam id (ci) field. It is right-justified and truncated.
• Fields from one group cannot be used in another. The beginning of each group is marked
by a specific field, a patient ID (pi) for patient demographics, a specimen separator (si) for
specimen data, (ci) for culture/exam data, (ta) for tests (VITEK®, VITEK® 2, and
OBERVA® only), (ra) for results (VITEK®, VITEK® 2, and OBSERVA® only), and (tb) for
blood culture tests (VITEK® and VITEK® 2).
• Field values shorter than defined do not need to be padded to the maximum size.
• A terminator ends each field. The default terminator is the vertical bar ( | ). For VITEK®
and VITEK® 2 only, the terminator can be one of three user-defined ASCII characters.
• For VITEK® and VITEK® 2 only, if a host sends a physician or source field with values that
match a host code, BCI’s host field translations change the host code to match the
bioMérieux code that goes to bioLIAISON®. This is in addition to any existing antimicrobial
or organism translations.
• OBSERVA® dynamically updates its code tables based on what the host sends, as
follows:
• If the host sends a BCI code field with its associated text field, and neither the code
nor the text exist in the code table, then the code table is updated with a new entry
where the code equals the received code and the text equals the received text.
• If the host sends a BCI code field with its associated text field, and the code exists in
the code table but with a different text, then the code is used and the text is ignored,
except for the organism and antibiotic tables, which are updated to reflect the
received text.
• If the host sends a BCI code field without its associated text field, and the code does
not exist in the code table, then the code table is updated with a new entry where
both the code and text equal the received code.
• If the host sends a BCI text field without its associated code field, and the text does
not exist in the code table, then the code table is updated with a new entry where
the code is blank and the text equals the received text.
• OBSERVA® resolves code table conflicts in host downloads as follows:

514724-1EN1 Download Specifics 3-1

Bidirectional Computer Interface Specification for VITEK® Systems

• If the host sends a BCI code field and its associated text field, and the text exists in
the code table but with a different code, then the code is ignored and the text is
used.
• If the host sends a BCI code and its associated text field, and both exist in the code
table but are not assigned to each other, then the code is used and the text is
ignored. Exception: If the host is connected via the OBSERVA® IMPORT link (as
would be the case for a LSN to OBSERVA® data migration), the incoming message
is rejected.

3.2 Download Applications Layer Message Types

An application layer message type is a three-letter code which identifies information contained
in the message. Message types indicate the beginning of a new message and must precede
any information related to the message.

Messages must contain certain field types. Additional field types may be included.

If a bioMérieux computer cannot handle or recognize a particular field type, it ignores the field
and logs a message. It also blanks out any empty, non-required fields.

Table 3-1 lists required download field types.

Table 3-1: Download Messages and Required Field Types

Message
Description Required Field Types
Type
mpr Patient Demographics (For all test types)
mt, pi, si, and ci
(For blood test orders)
mt, pi, si, ci, and tb
If test results are downloaded... (For ID or blood test results)
mt, pi, si, ci, tb, and ta
(For susc and smear results)
mt, pi, si, ci, ta, and ra
oos Out of Service mt
bis Back in Service mt

3.2.1 Patient Demographic Message Type (mpr)

This message type indicates that patient demographics (and, optionally, tests and results)
follow. The minimum required fields for a download message are: message type (mt), patient
ID (pi), specimen separator (si), and exam ID (ci).

The bottle barcode can also be downloaded for blood test orders. If this is the case, required
fields are mt, pi, si, ci, and tb (bottle barcode).

3.2.2 Out of Service (oos)

This message is an indication to the bioMérieux computer that the host is not ready to receive
messages. The bioMérieux computer will then stop sending messages to the host and queue
them for later transmission. The bioMérieux computer can continue to receive and process all

514724-1EN1 Download Specifics 3-2

Bidirectional Computer Interface Specification for VITEK® Systems

messages from the host during this time. This message does not require any additional fields.
An example of an out of service message is: mtoos|

3.2.3 Back in Service (bis)

When the host resumes normal operation after being out of service, it sends a bis message.
When the bioMérieux computer receives this message, it transmits any queued messages. It
does not require any additional fields. An example of a back in service message is: mtbis|

3.3 Download Applications Layer Field Types

This section lists all the field types that can be in downloaded messages. If the applications
layer encounters an unknown field type, it ignores it and continues to process the message.
Each field type has a maximum length that refers to the maximum size of the field within the
database. If a message contains fields with information exceeding the maximum size, they are
truncated to fit in the database.

3.3.1 Table Field Types

Note: This feature is only available in VITEK®, VITEK® 2, and OBSERVA®.

Some BCI fields are "table-driven", which means that a predefined alphanumeric code is sent
as a lookup value for a table entry. An example of this is a code representing a physician. In
VITEK® and VITEK® 2, the bioMérieux computer user has the responsibility of maintaining
user tables in the bioLIAISON® database with codes used by the host computer. In
OBSERVA®, all code tables, with the exception of Test Type, are dynamically updated. User-
defined fields are noted by US, UT, or BU in the source column of the following tables.

Use these data classification and source descriptions to determine field types and their
contents. Required fields are only necessary if the other data in the table will be sent. For
example, Patient ID is only required if Demographic data is being downloaded.

Table 3-2: Download Data Classification Codes

Code Data Classification

G General fields
P Patient demographics fields
S Specimen demographics fields
C Culture (exam) demographics fields
T Test fields
R Result fields
A All

Table 3-3: Download Source Description Codes

Code Source Description

UT VITEK®, VITEK® 2, and OBSERVA®: User-defined table (only)
VITEK® 2 Systems1

514724-1EN1 Download Specifics 3-3

Bidirectional Computer Interface Specification for VITEK® Systems

Table 3-3: Download Source Description Codes (Continued)

Code Source Description

US User-supplied data
BT bioMérieux-defined table
BU bioMérieux-defined, user-modifiable table
HO Host-computer supplied data
UR VITEK® and VITEK® 2; User-supplied data, BCI translation utility
OBSERVA®: same as UT
VITEK® 2 Systems1

1
The UT and UR codes are treated as free text in VITEK® 2 Systems. The code is not table driven.

3.3.2 Demographic Fields

Demographic Fields show the fields that bioMérieux computers recognize in a demographics
(mpr) message type.

For VITEK® and VITEK® 2, the first maximum field size shown is bioLIAISON’s maximum size
and the second is the size determined by the host in Host Field Translations.

For OBSERVA®, if two maximum field sizes are shown, OBSERVA® always uses the larger
number.

Table 3-4: Download Demographic Fields

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Code Class Length Description (R)
Description Description
mt G 3 BT Message Type Message Type Message Type R
id G 3 HO Instrument ID NA NA
is G 80 BT NA NA Organism
Instrument Serial
Number
it G 2 BT NA NA Organism Test
Group
pi P 16 US Patient ID Patient ID Patient ID R
pv P 16 US NA Patient Visit Patient Visit
Number Number
(Alternate (Alternate Patient
Patient ID) ID)1
pn P 40 US Patient Name Patient Name Patient Last
Name Patient
First Name2
pb P Date US Patient Date of NA Patient Birth
Birth Date
ps P 10 US Patient Sex NA Patient Gender
pl P 6 UT Patient Patient Patient Visit
Location Code Location Code Nursing Unit

514724-1EN1 Download Specifics 3-4

Bidirectional Computer Interface Specification for VITEK® Systems

Table 3-4: Download Demographic Fields (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Code Class Length Description (R)
Description Description
p2 P 32 UT NA NA Patient Visit
Nursing Unit
px P 6 UT Patient Hospital NA Patient Visit
Service Code Clinical Service
p3 P 20 UT NA NA Patient Visit
Clinical Service
po P 6 UT Patient NA Patient Visit
Admitting Diagnosis
Diagnosis Code
p4 P 40 UT NA NA Patient Visit
Diagnosis
pp P 6/153 UT/UR Patient Primary Patient Patient Visit
Physician Code Primary Admitting
Physician Physician Code
Code
p5 P 30 UT/UR NA NA Patient Visit
Admitting
Physician
pa P Date UT Patient NA Patient Visit
Admitting Date Admission Date
pd P 6 BA Patient Dosage NA See Note 6
Group Code
pc P 6 UT Patient Patient Patient Comment
Comment Code Comment (Repeatable)
(Repeatable) Code
(Not
Repeatable)
pt P 800 NA NA Patient Comment
(Pepeatable)
w1 P 40 US Patient Wild Patient Wild See Note 6
Field 1 Field 1
(Alternate (Alternate
Patient ID) Patient ID)
w2 P 40 US Patient Wild NA See Note 6
Field 2
w3 P 40 US Patient Wild NA See Note 6
Field 3
w4 P 40 US Patient Wild NA See Note 6
Field 4
w5 P 40 US Patient Wild NA See Note 6
Field 5
w6 P 40 US Patient Wild NA See Note 6
Field 6
w7 P 40 US Patient Wild NA See Note 6
Field 7

514724-1EN1 Download Specifics 3-5

Bidirectional Computer Interface Specification for VITEK® Systems

Table 3-4: Download Demographic Fields (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Code Class Length Description (R)
Description Description
w8 P 40 US Patient Wild NA See Note 6
Field 8
ua P 6 UT Patient User NA See Note 6
Field 1 Code
uc P 6 UT Patient User NA See Note 6
Field 2 Code
ue P 6 UT Patient User NA See Note 6
Field 3 Code
u1 P 6 UT Patient User NA See Note 6
Field 4 Code
u3 P 6 UT Patient User NA See Note 6
Field 5 Code
si S 0 – Specimen Specimen Specimen R
Separator Separator Separator
ss S 6/153 UT/UR Specimen Specimen Specimen
Source Code Source Code Source
s5 S 26 UT/UR NA NA Specimen
Source
st S 6 UT Specimen Site NA Specimen Site
Code
s6 S 26 UT NA NA Specimen Site
sl S 6 UT Specimen NA Specimen
Location Code Location
(Collection)
s7 S 32 UT NA NA Specimen
Location
(Collection)
sp S 6/153 UT/UR Specimen NA Specimen
Requesting Requesting
Physician Code Physician
s8 S 30 UT/UR NA NA Specimen
Requesting
Physician
sx S 6 UT Specimen NA Specimen
Service Code Nursing Service
(Collection)
s9 S 20 UT NA NA Specimen
Nursing Service
(Collection)
sy S 2 BU Specimen NA See Note 6
Status Code
s1 S Date US Specimen Specimen Specimen Date
Collection Date Collection Collected-
Date Date/Time

514724-1EN1 Download Specifics 3-6

Bidirectional Computer Interface Specification for VITEK® Systems

Table 3-4: Download Demographic Fields (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Code Class Length Description (R)
Description Description
s2 S Time US Specimen Specimen Specimen Date
Collection Collection Collected-
Time4 Time 4 Date/Time
s3 S Date US Specimen NA Specimen Date
Receipt Date Received-
Date/Time
s4 S Time US Specimen NA Specimen Date
Receipt Time4 Received-
Date/Time
sf S 5 US Patient NA See Note 6
Temperature
so S 8 US Collection NA See Note 6
Number
sc S 6 US Specimen Specimen Specimen
Comment Code Comment Comment
(Repeatable) Code (Repeatable)
(Not
Repeatable)
sn S 800 US NA NA Specimen
Comment
(Repeatable)
ug S 6 UT Specimen User NA See Note 6
Field 1 Code
ui S 6 UT Specimen User NA See Note 6
Field 2 Code
uk S 6 UT Specimen User NA See Note 6
Field 3 Code
um S 6 UT Specimen User NA See Note 6
Field 4 Code
uo S 6 UT Specimen User NA See Note 6
Field 5 Code
uq S 6 UT Specimen User NA See Note 6
Field 6 Code
us S 6 UT Specimen User NA See Note 6
Field 7 Code
uu S 6 UT Specimen User NA See Note 6
Field 8 Code
wa S 40 US Specimen Wild NA See Note 6
Field 1
wb S 40 US Specimen Wild NA See Note 6
Field 2
wc S 40 US Specimen Wild NA See Note 6
Field 3
wd S 40 US Specimen Wild NA See Note 6
Field 4

514724-1EN1 Download Specifics 3-7

Bidirectional Computer Interface Specification for VITEK® Systems

Table 3-4: Download Demographic Fields (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Code Class Length Description (R)
Description Description
we S 40 US Specimen Wild NA See Note 6
Field 5
ci C 20 – Exam ID Exam ID Accession R
(Culture ID and (Culture ID Number
Lab ID) and Lab ID)
ct C 6 UT Exam Type Exam Type Accession Test
Code Code Ordered
cn C 26 UT NA NA Accession Test
Ordered
c1 C Date US Exam NA Accession Date
Completion Completed –
Date Date/Time
c2 C Time US Exam NA Accession Date
Completion Completed –
Time4 Date/Time
x1 C 40 US Exam Wild NA See Note 6
Field 1
x2 C 40 US Exam Wild NA See Note 6
Field 2
na5 C 6 UT Exam NA Accession
Comment Code Comment
(Repeatable) (Repeatable)
nb5 C 800 UT NA NA Accession
Comment
(Repeatable)
zz G 0 NA Message Message Message
Terminator Terminator Terminator

1
In OBSERVA®, Alternate Patient ID may be re-assigned to the w1 field.
2
The pn field contains the entire patient name. In many cases, the pn field is downloaded with the last
name followed by a comma and then the first name. Example: ...|pnDoe, Jane|... When OBSERVA®
downloads the pn field, the characters preceding the first comma in the pn field go into the OBSERVA®
Patient Last Name data field, and characters after the first comma go into the OBSERVA® Patient First
Name data field.
3
VITEK® 2 Systems has a maximum length of 6. VITEK® and VITEK® 2 have a maximum length of 15
(if the translation table is used). OBSERVA® has a maximum length of 15.
4
Time format is HH:MM using a 24-hour clock.
5
For VITEK® and VITEK® 2, the Blood Culture Order Field and/or Test Result Fields follow the na field.
6
In OBSERVA®, an unused BCI field may be assigned to a user-defined data field of the same data
class.

514724-1EN1 Download Specifics 3-8

Bidirectional Computer Interface Specification for VITEK® Systems

Note: Values downloaded in the Culture ID field must match the ID that the user
assigned to the card in the VITEK®, VITEK® 2, VITEK® 2 Systems, or
OBSERVA® system. Do not download the VITEK® card’s isolate (dash)
number in the culture ID field. Always use the t1 field for the isolate number
if you are downloading results.

Note: In OBSERVA®, BCI fields are table driven only if:

• Both the BCI code field and its associated BCI text field are assigned
to the same OBSERVA® data field, and
• the OBSERVA® data field is configured to have a table.

Note: For Information about configuring data fields and BCI fields in OBSERVA®,
see the OBSERVA® User Manual.

3.3.3 Blood Culture Order Field

Note: This section is only applicable to VITEK® and VITEK® 2.

For blood tests, the test type field (rt) is required. However, only the bottle barcode is required
for downloaded test orders.

Table 3-5: Blood Culture Order Field

VITEK® and VITEK® and

Field Data Max.
Source VITEK® 2 VITEK® 2 Required
Code Class Length
Description (R)
tb T 10 BT Bottle Barcode

3.3.4 Test Result Fields (All Test Types)

Note: This section is only applicable to VITEK®, VITEK® 2, and OBSERVA®

systems.

The fields shown in Test Results Fields are allowed in each test type.

Table 3-6: Download Test Result Fields

VITEK® and
Field Data Max. OBSERVA®
Source VITEK® 2 Required (R)
Code Class Length Description
Description
ta T 0 – Test Separator Test Separator R
rt T 8 BT Test Type Code Organism Test R
Type
rn T 40 BT NA Organism Test R
Type

514724-1EN1 Download Specifics 3-9

Bidirectional Computer Interface Specification for VITEK® Systems

Table 3-6: Download Test Result Fields (Continued)

VITEK® and
Field Data Max. OBSERVA®
Source VITEK® 2 Required (R)
Code Class Length Description
Description
t4 T 2 BT Test Status Code See Note 2
m3 T 6 UT Technologist Code See Note 2
nc T 6 UT Test Comment Organism
Code (Repeatable) Comment
(repeatable)
nd T 800 UT NA Organism
Comment
(repeatable)
y1 T 40 UT Test Wild Text See Note 2
y2 T 40 UT Test Wild Text See Note 2
y3 T 40 UT Test Wild Text See Note 2
y41 T 40 UT Test Wild Text See Note 2

1 Test type specific result fields follow the y4 field.

2 In OBSERVA®, an unused BCI field may be assigned to a user-defined data field of the same data

class.

3.3.5 Test Result Fields for Specific Tests

Table 3-7 lists each test type and their allowable fields.

In VITEK® and VITEK® 2, the first maximum field size shown is the bioLIAISON® maximum
size and the second is the size determined by the host in Host Field Translations.

For OBSERVA®, if two maximum field sizes are shown, OBSERVA® always uses the larger
number.

Table 3-7: Download Test Result Fields for Specific Tests

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
VITEK® 2 Systems
Code Class Length Description (R)
Description Description

ID Test
t1 T 2 Isolate Number Isolate Number Isolate R
Number
tb T 10 Bottle Barcode NA NA
t6 T 6/15 Preliminary NA NA
Organism Code
t8 T 6 Preliminary NA NA
Modifier Code
o1 T 6/15 Final Organism Organism Final R
Code Organism
Code

514724-1EN1 Download Specifics 3-10

Bidirectional Computer Interface Specification for VITEK® Systems

Table 3-7: Download Test Result Fields for Specific Tests (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
VITEK® 2 Systems
Code Class Length Description (R)
Description Description
o2 T 60 NA Organism Final
Organism
Name
o3 T 16 Final Bionumber NA NA
o4 T 6 Final Modifier Organism NA
Code Modifier
o5 T 20 NA Organism NA
Modifier
o9 8 Percent Probability NA NA

Susc. Test
t1 T 2 Isolate Number Isolate Number Isolate R
Number
tb T 10 Bottle Barcode NA NA
t6 T 6/15 Preliminary NA NA
Organism Code
t8 T 6 Preliminary NA NA
Modifier Code
o1 T 6/15 Final Organism Organism Final R
Code Organism
Code
o2 T 60 NA Organism Final
Organism
Name
o4 T 6 Final Modifier Organism NA
Code Modifier
ra R 0 Result Separator1 Result NA
Separator1
ad R 0 Deduced Drug How Determined1 NA
Indicator1
a1 R 8/15 Drug code1 Antibiotic1 NA
a2 R 60 NA Antibotic NA
a3 R 8 Final MIC1 Final MIC1 NA
a4 R 2 Final Result1 Final Category1 NA

Smear Test
tb T 10 Bottle Barcode NA NA
2
ra R 0 Result Separator NA NA R
rs R 6 Smear Code2 NA NA
2
o4 R 6 Modifier Code NA NA

514724-1EN1 Download Specifics 3-11

Bidirectional Computer Interface Specification for VITEK® Systems

Table 3-7: Download Test Result Fields for Specific Tests (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
VITEK® 2 Systems
Code Class Length Description (R)
Description Description

ID/Offline Test
t1 T 2 NA NA Isolate
Number
o1 T 6/15 NA NA Final
Organism
Code
o2 T 60 NA NA Final
Organism
Name
ba T 0 NA NA Offline Test
Separator
b1 T 8/15 NA NA Offline Test
Code
b2 T 60 NA NA Offline Test
Name
b3 T 8/15 NA NA Offline Test
Result Code

1
Fields ra through a4 are repeatable as a group.
2
Fields ra through o4 are repeatable as a group.

3.4 Message Examples

Applications layer messages can be any of the types described in Download Messages and
Required Field Types. They will have one or more field types associated with the patient,
specimen, and exam data and must be in this order:

1. Patient ID and optional patient demographics

2. Specimen separator and optional specimen data
3. Culture ID and optional exam data
4. Bottle barcode for a blood test order (VITEK® and VITEK® 2 only)

Note: If there are additional test or result fields, then the ta field must precede the
tb field.

5. Test information may be included in the download, followed by the repeating results of the
test. Each result for the same test must be preceded by a result separator, and different
tests must be preceded by a test separator. Multiple tests are allowed.

514724-1EN1 Download Specifics 3-12

Bidirectional Computer Interface Specification for VITEK® Systems

To download multiple specimens for a single patient, repeat items two through five in
sequence. To download multiple exams for a single specimen (VITEK® and VITEK® 2 only),
repeat items three through five. To download multiple tests, repeat item five.

Note: VITEK® 2 Systems and OBSERVA® only support one exam (i.e. accession)
per specimen.

Note: There can be only one patient per mpr message.

The following examples contain sample packets of test data. Line breaks are for example
purposes only. There are no line breaks or carriage returns in a data packet unless
<CR><LF> characters are entered.

Figure 3-1: Patient Demographics Only

mtmpr|pi193301|pnHo, Ida|pl4|ppsu|pda|w1475|uaf|
si|ssu|slzer|spsor|s102/21/1994|s208:40|s302/21/94|
s411:04|
ci020517|ctr|zz|

Figure 3-2: Identification Test Results (VITEK® and VITEK® 2 Only)

mtmpr|pi193301|pnHo, Ida|pl4|ppsu|pda|w1475|uaf|
si|ssu|slzer|spsor|s102/21/1994|s208:40|s302/21/94|
s411:04|
ci020517|ctr|na>|na5|nagnb|ta|rtgni|t4P|t11|o1promir|
o36003200001220|zz|

Figure 3-3: Identification Test Results from a Blood Culture (VITEK® and VITEK® 2
Only)

mtmpr|pi193301|pnHo, Ida|pl4|ppsu|pda|w1475|uaf|
si|ssu|slzer|spsor|s102/21/1994|s208:40|s302/21/94|
s411:04|
ci020517|ctr|na>|na5|nagnb|ta|rtgni|t4P|t11|tb123456|
o1promir|o36003200001220|zz|

Figure 3-4: Susceptibility Test Results (VITEK® and VITEK® 2 Only)

mtmpr|pi960297|pnSmith, John|pb09/27/1996|
si|s109/27/96|s214:55|s309/27/1996|s414:55|sf 99.8|
ci000064|ctauto|c109/27/96|c214:55|ta|rtgns-1s|t11|
t4p|o1provul|ra|a1cz|a3>=32|a4R|ra|a1tax|a3>=64|a4R|
ra|a1taz|a3>=32|a4R|ra|a1roxa|a38|a4I|ra|a1rox|a38|
a4S|ra|alcip|a3<=0.5|a4S|ra|alam|a3>=32|a4R|zz|

514724-1EN1 Download Specifics 3-13

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 3-5: Susceptibility Test Results from a Blood Culture (VITEK® and VITEK® 2
Only)

mtmpr|pi960297|pnSmith, Jane|pb09/27/1996|
si|s109/27/96|s214:55|s309/27/1996|s414:55|sf 99.8|
ci000064|ctauto|c109/27/1996|c214:55|ta|rtgns-
1s|t11|
tb654321|t4P|o1provul|ra|a1cz|a3>=32|a4R|ra|a1tax|
a3>=64|a4R|ra|a1taz|a3>=32|a4R|ra|a1roxa|a38|a4I|ra|
a1rox|a38|a4S|ra|a1cip|a3<=0.5|a4S|ra|a1am|a3>=32|
a4R|zz|

Figure 3-6: Smear Test Results (VITEK® and VITEK® 2 Only)

mtmpr|pi193301|pnBrown, James|pl7|ppowe|pda|w177|uam|
si|ssw|s17|spowe|s111/15/96|s209:45|s311/15/1996|
s411:55|
ci110333|ctr|c111/18/96|x2Back mass|nang3d|ta|
rtvitest|t4P|ra|rssmear|o41|ra|rssmear|o42|zz|

Figure 3-7: Smear Test Results from a Blood Culture (VITEK® and VITEK® 2 Only)

mtmpr|pi193301|pnBrown, James|pl7|ppowe|pda|w177|uam|
si|ssw|s17|spowe|s111/15/1996|s209:45|s311/15/1996|
s411:55|
ci110333|ctr|c111/18/96|x2Back mass|nang3d|ta|
rtvitest|tb98765|t4P|ra|rssmear|o41|ra|rssmear|o42|zz|

Figure 3-8: VITEK® 2 Systems Sample Download (VITEK® 2 Systems Only)

mtmpr|piA10001|pv123444|pnDoe,
John|plloc1|ppph1|pccom1|si|sssrc1|s101/21
2004|s201:01|sccom2|ci123111|ctet|zz

514724-1EN1 Download Specifics 3-14

 4 Upload Specifics

4.1 Introduction

When setting up systems to work with BCI, keep these points in mind:

• A BCI upload is when test results are sent from the bioMérieux computer to the host LIS
computer. All BCI application messages are complete, with each message divided into
fields.
• The first field is the message type. It establishes the number and types of remaining fields
within the message. A complete message contains a message type and all the fields that
message type requires.
• Each field is assigned a unique two-character code. A field cannot be larger than its
maximum size. Depending on the needs of the host LIS computer, each field may or may
not be padded with spaces to fill out its maximum size.
• For VITEK® and VITEK® 2, terminator characters ending each field are user-defined and
use one to three ASCII characters. The default terminator character is a vertical bar ( | ).
• VITEK® 2 Systems and OBSERVA® support only the ( | ) terminator character.

4.2 Upload Applications Layer Message Types

Applications layer message types describe information contained in a message. Message

types indicate the beginning of a new message and must precede any information related to
that message. There are certain fields required in messages, although a message may
contain other fields types as well.

If the host computer receives a field type it doesn’t recognize or if the field is empty, it should
ignore the field.

Note: It may be useful to log and report these errors.

Table 4-1: Applications Layer Messages, Descriptions, and Required Field Types

Message
Description Required Field Types
Type
rsl Test Results mt, pi, si, ci
oos Out of Service mt
bis Back in Service mt
org Auto-synchronize Organisms mt
abx Auto-synchronize Antibiotics mt

4.2.1 Test Results Literal Format (rsl)

The bioMérieux computer uses this message type to report test results. Results include
organism identifications, antimicrobial susceptibilities, smear and blood test results. Fields

514724-1EN1 Upload Specifics 4-1

Bidirectional Computer Interface Specification for VITEK® Systems

required for this message type are the patient ID (pi), specimen separator (si), and culture ID
(ci).

4.2.2 Out of Service (oos)

The bioMérieux computer sends this message to the host computer indicating it is going to be
out of service. No additional fields are required for this message type. The host should
continue to receive and process any message from the bioMérieux computer. The message
will not have any additional fields. An example of an out of service message is: mtoos|

4.2.3 Back in Service (bis)

When the bioMérieux computer resumes normal operation after being out of service, it sends
a bis message. The host computer should then transmit any queued messages. The message
will not have any additional fields. An example of a back in service message is: mtbis|

4.2.4 Auto-synchronize Organisms (org)

The bioMérieux computer sends this message type to notify OBSERVA® of possible changes
in the VITEK® 2 Systems organism names and codes. Fields required for this message type
are o1 and o2. An example of an auto-synchronize organisms message is:
mtorg|o1abidef|o2Abiotrophia defectiva|

Note: The auto-synchronize organisms (org) and auto-synchronize antibiotics

(abx) messages are intended for use by OBSERVA® only.

4.2.5 Auto-synchronize Antibiotics (abx)

The bioMérieux computer sends this message type to notify OBSERVA® of possible changes
in the VITEK® 2 Systems antibiotic names and codes as well as antibiotic family hierarchy
information. Fields required for this message type are af, a1, and a2. An example of an auto-
synchronize antibiotics message is: mtabx|afBeta-Lactams|a1amx|a2Amoxicillin|

Note: The auto-synchronize organisms (org) and auto-synchronize antibiotics

(abx) messages are intended for use by OBSERVA® only.

4.3 Upload Applications Layer Field Types

Some BCI fields are “table-driven”, which means that a predefined alphanumeric code is sent
as a lookup value for a table entry. An example of this is a code representing a physician.

In VITEK® and VITEK® 2, the bioMérieux computer user has the responsibility of maintaining
user tables in the bioLIAISON® database with codes used by the host computer.

514724-1EN1 Upload Specifics 4-2

Bidirectional Computer Interface Specification for VITEK® Systems

In OBSERVA®, all code tables with the exception of Test Type are dynamically updated. User-
defined fields are noted by US, UT, or BU in the source column of the following tables.

Note: In OBSERVA®, a BCI field is table driven only if:

• Both the BCI code field and its associated BCI text field are assigned
to the same OBSERVA® data field, and
• The OBSERVA® data field is configured to have a table. For a
description of how to configure data fields and BCI fields in
OBSERVA®, see the OBSERVA® User Manual.

Use the data classification and source descriptions to determine field types and their contents.

Table 4-2: Upload Data Classification Codes

Code Data Classification

G General Fields
P Patient Demographics Fields
S Specimen Demographics Fields
C Culture (Exam) Demographics Fields
T Test Fields
R Result Fields
A All

Table 4-3: Upload Source Description Codes

Code Source Description

UT VITEK®, VITEK® 2, and OBSERVA®: User-Defined Table
VITEK® 2 Systems: Treated as free text (the code is not table driven)
US User-Supplied Data
BT bioMérieux-Defined Table
BU bioMérieux-Defined, User-Modifiable Table
BR bioMérieux-Defined Table, BCI Utilities Translation
UR VITEK® and VITEK® 2: User-supplied data, BCI translation utility
OBSERVA®: same as UT
VITEK® 2 Systems: Treated as free text (the code is not table driven)

4.3.1 Demographic Fields

Table 4-4 lists all of the valid upload fields. Any of them can be transmitted to a host as part of
results.

For VITEK® and VITEK® 2, the utility menu in BCI is where users select and enable reported
fields.

For VITEK® 2 Systems and OBSERVA®, please refer to their respective software user
manuals.

514724-1EN1 Upload Specifics 4-3

Bidirectional Computer Interface Specification for VITEK® Systems

For VITEK® and VITEK® 2, the first maximum field size shown is the bioLIAISON® maximum
size and the second is the size determined by the host in Host Field Translations.

For OBSERVA®, if two maximum field sizes are shown, OBSERVA® uses the larger number.

Table 4-4: Upload Demographic Fields

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Code Class Length Description (R)
Description Description
mt G 3 BT Message Message Message Type R
Type Type
id G 3 BT Instrument ID NA See Note 4
ii G 2 BT Instrument Instrument Organism
Code Code Instrument Code
is G 80 BT NA Instrument See Note 4
Serial Number
it G 2 BT Test Group Test Group Organism Test
Code Code Group
pi P 16 US Patient ID Patient ID Patient ID R
pv P 16 US NA Patient Patient Visit
Alternate ID Number
(Alternate Patient
ID)1
pn P 40 US Patient Name Patient Name Patient Last
Name Patient
First Name2
pb P Date US Patient Date NA Patient Birth Date
of Birth
ps P 10 US Patient Sex NA Patient Gender
pl P 6 UT Patient Patient Patient Visit
Location Location Code Nursing Unit
Code
p2 P 32 UT Patient Patient Patient Visit
Location Text Location Nursing Unit
Name
px P 6 UT Patient NA Patient Visit
Hospital Clinical Service
Service Code
p3 P 20 UT Patient NA Patient Visit
Hospital Clinical Service
Service Text
po P 6 UT Patient NA See Note 4
Admitting
Diagnosis
Code
p4 P 40 UT Patient NA Patient Visit
Admitting Diagnosis
Diagnosis
Text

514724-1EN1 Upload Specifics 4-4

Bidirectional Computer Interface Specification for VITEK® Systems

Table 4-4: Upload Demographic Fields (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Code Class Length Description (R)
Description Description
pp P 6/153 UT/UR Patient Patient Patient Visit
Primary Physician Admitting
Physician Code Physician
Code
p5 P 30 UT Patient Patient Patient Visit
Primary Physician Admitting
Physician Name Physician
Text
pa P Date US Patient NA Patient Visit
Admission Admission Date
Date
pd P 6 BU Patient NA See Note 4
Dosage
Group Code
p6 P 40 BU Patient NA See Note 4
Dosage
Group Text
pc P 6 UT Patient Patient Patient Comment
Comment Comment (Repeatable)
Code Code
(Repeatable) (Not
Repeatable)
pt P 800 UT Patient Patient Patient Comment
Comment Comment (Repeatable)
Text Text
(Repeatable) (Not
Repeatable)
w1 P 40 US Patient Wild Patient Wild 1 See Note 1
Field 1 (Patient
Alternate ID)
w2 P 40 US Patient Wild NA See Note 4
Field 2
w3 P 40 US Patient Wild NA See Note 4
Field 3
w4 P 40 US Patient Wild NA See Note 4
Field 4
w5 P 40 US Patient Wild NA See Note 4
Field 5
w6 P 40 US Patient Wild NA See Note 4
Field 6
w7 P 40 US Patient Wild NA See Note 4
Field 7
w8 P 40 US Patient Wild NA See Note 4
Field 8
ua P 6 UT Patient User NA See Note 4
Field 1 code

514724-1EN1 Upload Specifics 4-5

Bidirectional Computer Interface Specification for VITEK® Systems

Table 4-4: Upload Demographic Fields (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Code Class Length Description (R)
Description Description
ub P 40 UT Patient User NA See Note 4
Field 1 text
uc P 6 UT Patient User NA See Note 4
Field 2 code
ud P 40 UT Patient User NA See Note 4
Field 2 text
ue P 6 UT Patient User NA See Note 4
Field 3 code
uf P 40 UT Patient User NA See Note 4
Field 3 text
u1 P 6 UT Patient User NA See Note 4
Field 4 code
u2 P 40 UT Patient User NA See Note 4
Field 4 text
u3 P 6 UT Patient User NA See Note 4
Field 5 code
u4 P 40 UT Patient User NA See Note 4
Field 5 text
p7 P 40 UT Physician NA See Note 4
Address Line
1
p8 P 40 UT Physician NA See Note 4
Address Line
2
p9 P 40 UT Physician NA See Note 4
Address Line
3
p0 P 40 UT Physician NA See Note 4
Address Line
4
si S 0 — Specimen Specimen Specimen R
Separator Separator Separator
s0 S 8 BT Relative Specimen Specimen
Specimen System Code System Code
Number
ss S 6/153 UT/UR Specimen Specimen Specimen Source
Source Code Source Code
s5 S 26 UT Specimen Specimen Specimen Source
Source Text Source Name
st S 6 UT Specimen NA Specimen Site
Site Code
s6 S 26 UT Specimen NA Specimen Site
Site Text

514724-1EN1 Upload Specifics 4-6

Bidirectional Computer Interface Specification for VITEK® Systems

Table 4-4: Upload Demographic Fields (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Code Class Length Description (R)
Description Description
sl S 6 UT Specimen NA Specimen
Location Location
Code (Collection)
s7 S 32 UT Specimen NA Specimen
Location Text Location
(Collection)
sp S 6/15 UT/UR Specimen NA Specimen
Requesting Requesting
Physician Physician
Code
s8 S 30 UT Specimen NA Specimen
Requesting Requesting
Physician Physician
Text
sx S 6 UT Specimen NA Specimen
Service Code Nursing Service
(Collection)
s9 S 20 UT Specimen NA Specimen
Service Text Nursing Service
(Collection)
sy S 2 BU Specimen NA See Note 4
Status Code
sz S 16 BU Specimen NA See Note 4
Status Text
s1 S Date US Specimen Specimen Specimen Date
Collection Collection Collected – Date/
Date Date Time
s2 S Time US Specimen Specimen Specimen Date
Collection Collection Collected – Date/
Time Time Time
s3 S Date US Specimen Specimen Specimen Date
Receipt Date Receipt Date Received – Date/
(Same Value Time
as Specimen
Collection
Date)
s4 S Time US Specimen Specimen Specimen Date
Receipt Time Receipt Time Received – Date/
(Same Value Time
as Specimen
Collection
Time)
sf S 5 US Patient NA See Note 4
Temperature
so S 8 US Collection NA See Note 4
Number
(Blood Test)

514724-1EN1 Upload Specifics 4-7

Bidirectional Computer Interface Specification for VITEK® Systems

Table 4-4: Upload Demographic Fields (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Code Class Length Description (R)
Description Description
sc S 6 UT Specimen Specimen Specimen
Comment Comment Comment
Code Code (Repeatable)
(Repeatable) (Not
Repeatable)
sn S 800 UT Specimen Specimen Specimen
Comment Comment Comment
Text Text (Repeatable)
(Repeatable) (Not
Repeatable)
ug S 6 UT Specimen NA See Note 4
User Field 1
Code
uh S 40 UT Specimen NA See Note 4
User Field 1
Text
ui S 6 UT Specimen NA See Note 4
User Field 2
Code
uj S 40 UT Specimen NA See Note 4
User Field 2
Text
uk S 6 UT Specimen NA See Note 4
User Field 3
Code
ul S 40 UT Specimen NA See Note 4
User Field 3
Text
um S 6 UT Specimen NA See Note 4
User Field 4
Code
un S 40 UT Specimen NA See Note 4
User Field 4
Text
uo S 6 UT Specimen NA See Note 4
User Field 5
Code
up S 40 UT Specimen NA See Note 4
User Field 5
Text
uq S 6 UT Specimen NA See Note 4
User Field 6
Code
ur S 40 UT Specimen NA See Note 4
User Field 6
Text

514724-1EN1 Upload Specifics 4-8

Bidirectional Computer Interface Specification for VITEK® Systems

Table 4-4: Upload Demographic Fields (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Code Class Length Description (R)
Description Description
us S 6 UT Specimen NA See Note 4
User Field 7
Code
ut S 40 UT Specimen NA See Note 4
User Field 7
Text
uu S 6 UT Specimen NA See Note 4
User Field 8
Code
uv S 40 UT Specimen NA See Note 4
User Field 8
Text
sa S 40 UT Physician NA See Note 4
Address Line
1
sb S 40 UT Physician NA See Note 4
Address Line
2
se S 40 UT Physician NA See Note 4
Address Line
3
sd S 40 UT Physician NA See Note 4
Address Line
4
wa S 40 US Specimen NA See Note 4
Wild Field 1
wb S 40 US Specimen NA See Note 4
Wild Field 2
wc S 40 US Specimen NA See Note 4
Wild Field 3
wd S 40 US Specimen NA See Note 4
Wild Field 4
we S 40 US Specimen NA See Note 4
Wild Field 5
ci C 20 — Culture ID Lab ID Accession R
(Examination Number
ID)
c0 C 8 BT Relative Lab ID System See Note 4
Culture/Exam Code
Number
ct C 6 UT Culture Type Culture Type Accession Test
Code Code Ordered
cn C 26 UT Culture Type Culture Type Accession Test
Text Name Ordered

514724-1EN1 Upload Specifics 4-9

Bidirectional Computer Interface Specification for VITEK® Systems

Table 4-4: Upload Demographic Fields (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Code Class Length Description (R)
Description Description
c1 C Date US Culture NA Accession Date
Completion Completed –
Date Date/Time
c2 C Time US Culture NA Accession Date
Completion Completed –
Time Date/Time
c3 C 2 BU Culture Status NA See Note 4
Code
c4 C 16 BU Culture Status NA See Note 4
Text
x1 C 40 US Culture Wild NA See Note 4
Field 1
x2 C 40 US Culture Wild NA See Note 4
Field 2
na C 6 UT Culture NA Accession
Comment Comment
Code (Repeatable)
(Repeatable)
nb C 800 UT Culture NA Accession
Comment Comment
Text (Repeatable)
(Repeatable)

1
In OBSERVA®, Alternate Patient ID may be re-assigned to the w1 field.
2
In OBSERVA®, pn will contain last name, first name unless the patient’s first name is blank, in
which case pn will contain only the patient’s last name.
3 VITEK® 2 Systems has a maximum length of 6. VITEK® and VITEK® 2 have a maximum length of

15 (if the translation table is used). OBSERVA® has a maximum length of 15.
4 In OBSERVA®, an unused BCI field may be assigned to a user-defined data field in OBSERVA® of

the same data class.

4.3.2 Test Result Fields

The fields listed in Table 4-5 are included in each test type, if they are enabled by users.

Table 4-5: Upload Test Result Field Types

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Type Class Length Description (R)
Description Description
ta T 0 – Test Separator Test Test
Separator Separator
rt T 8 BT Test Type Test Type Organism
Code Code Test Type
rn T 40 BU Test Type NA Organism
Name Test Type

514724-1EN1 Upload Specifics 4-10

Bidirectional Computer Interface Specification for VITEK® Systems

Table 4-5: Upload Test Result Field Types (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Type Class Length Description (R)
Description Description
rr T 8 BT Relative Test Isolate Organism
Number System Code Isolate
System Code
ti T 2 BT Instrument NA See Note 2
System Code
tj T 16 BT Instrument NA See Note 2
Name
tc T 8 BT Instrument NA See Note 2
Comment
Code
(Repeatable)
tn T 800 BT Instrument NA See Note 2
Comment Text
(Repeatable)
t2 T 2 BT Test Group NA See Note 2
Code
t3 T 16 BT Test Group NA See Note 2
Name
t4 T 2 BT Test Status Test Status See Note 2
Code Code 3
t5 T 16 BT Test Status Test Status See Note 2
Name Name
m3 T 6 UT Technologist NA See Note 2
Code
m4 T 30 UT Technologist NA See Note 2
Name
r1 T Date – NA Isolate Initial NA
Reading Date
r2 T Time – NA Isolate Initial NA
Reading Time
r3 T Date – NA Isolate Final NA
Call Date
r4 T Time – NA Isolate Final NA
Call Time
ts T 0 – NA Card Data NA
Separator
tu T 8 – NA Card Type NA
Code
tp T 18 – NA Card Barcode NA
tg T 10 – NA Card Lot NA
Number
te T Date – NA Card NA
Expiration
Date

514724-1EN1 Upload Specifics 4-11

Bidirectional Computer Interface Specification for VITEK® Systems

Table 4-5: Upload Test Result Field Types (Continued)

VITEK® and VITEK® 2

Field Data Max. OBSERVA® Required
Source VITEK® 2 Systems
Type Class Length Description (R)
Description Description
th T Date – NA Card Initial NA
Reading Date
tk T Time – NA Card Initial NA
Reading Time
td T Date – NA Card Final NA
Call Date
tm T Time – NA Card Final NA
Call Time
tq T 20 – NA Card Setup NA
Tech Code
tr T 30 – NA Card Setup NA
Tech Name
nc T 6 UT Test Comment NA See Note 2
Code
(Repeatable)
nd T 800 UT Test Comment NA See Note 2
Text
(Repeatable)
y1 T 40 UT Test Wild Text NA See Note 2
y2 T 40 UT Test Wild Text NA See Note 2
y3 T 40 UT Test Wild Text NA See Note 2
y41 T 40 UT Test Wild Text NA See Note 2

zz G 0 – Test Result End Result End

Terminator

1 Test type specific results follow the y4 field.

2 In
OBSERVA®, an unused BCI field may be assigned to a user-defined data field of the same data
class.
3 “P” = Preliminary test results; “F” = Final test results; “U” = User-defined test results (OBSERVA®

only).

IMPORTANT: If the t4 code is set to “P”, the results display as preliminary. It is

recommended that specific laboratory guidelines be followed when
displaying preliminary results.

4.3.3 Test Result Fields for Specific Tests

Table 4-6 lists each test type and their allowable fields. Some of the fields within the table
below are repeatable as a group. See the footnote at the bottom of this table for details.

If two maximum field sizes are shown, OBSERVA® uses the larger number. For VITEK® and
VITEK® 2, the first maximum field size shown is the bioLIAISON® maximum size and the
second is the size determined by the host in Host Field Translations. VITEK® and VITEK® 2

514724-1EN1 Upload Specifics 4-12

Bidirectional Computer Interface Specification for VITEK® Systems

supports Host Field Translations for Organism Code, Drug Code, Physician Code, and
Specimen Source Code.

VITEK® 2 Systems supports Host Field Translations for Organism Code and Drug Code.

OBSERVA® supports Host Field Translations for all tables.

Table 4-6: Upload Test Result Fields for Specific Tests

Test Type VITEK® and VITEK® 2

Data Max. OBSERVA® Required
/ Field VITEK® 2 Systems
Class Length Description (R)
Type Description Description

ID Test
t1 T 2 Isolate Number Isolate Number Isolate Number 5 R
tb T 10 Bottle Barcode NA NA
t6 T 6/15 Preliminary NA See Note 4
Organism Code
t7 T 60 Preliminary NA See Note 4
Organism Name
t8 T 6 Preliminary NA See Note 4
Modifier Code
t9 T 20 Preliminary NA See Note 4
Modifier Name
o1 T 6/15 Final Organism Final Organism Organism
Code Code
o2 T 60 Final Organism Final Organism Organism
Name Name
o3 T 16 Final Bionumber Final Organism
Bionumber Bionumber
o4 T 6 Final Modifier NA See Note 4
Code
o5 T 20 Final Modifier NA Organism Modifier
Name
o6 T 6 Organism Group NA See Note 4
Code
o7 T 30 Organism Group NA See Note 4
Name
o9 T 8 Percent Percent Organism
Probability Probability Probability
oc T 40 NA ID Confidence NA
Name

Susc. Test
t1 T 2 Isolate Number Isolate Number Isolate Number 5 R
tb T 10 Bottle Barcode NA NA
tt T 10,000 Test Free Text NA AST AES
(VITEK® 2 Only) Comment
(AES Result
Comment)

514724-1EN1 Upload Specifics 4-13

Bidirectional Computer Interface Specification for VITEK® Systems

Table 4-6: Upload Test Result Fields for Specific Tests (Continued)

Test Type VITEK® and VITEK® 2

Data Max. OBSERVA® Required
/ Field VITEK® 2 Systems
Class Length Description (R)
Type Description Description
t6 T 6/15 Preliminary NA See Note 4
Organism Code
t7 T 60 Preliminary NA See Note 4
Organism Name
t8 T 6 Preliminary NA See Note 4
Modifier Code
t9 T 20 Preliminary NA See Note 4
Modifier Name
o1 T 6/15 Final Organism Final Organism Organism
Code Code
o2 T 60 Final Organism Final Organism Organism
Name Name
o4 T 6 Final Modifier NA See Note 4
Code
o5 T 20 Final Modifier NA Organism Modifier
Name
o6 T 6 Organism Group NA See Note 4
Code
o7 T 30 Organism Group NA See Note 4
Name
ac T 40 NA AES NA
Confidence
Name
af T 40 NA Antibiotic AST Antibiotic
Family Name Family
(Repeatable) (Repeatable)
ap T 800 NA Phenotype AST Phenotype
Names (Repeatable
(Repeatable Within an
Within an Antibiotic Family
Antibiotic [af])
Family [af])
ra1, 2 R 0 Result Separator Result Result Separator
Separator
ar1 R 0 CAR Advanced CAR Suppression
Suppression Reporting Tool Indicator
Indicator Suppression
Indicator
ad1, 2 R 0 Deduced Drug Deduced AST How
(AES) Antibiotic Flag Determined
(VITEK® 2 Only)
a11, 2 R 8/15 Drug Code Antibiotic Code AST Antibiotic
a21, 2 R 60 Drug Name Antibiotic AST Antibiotic
Name

514724-1EN1 Upload Specifics 4-14

Bidirectional Computer Interface Specification for VITEK® Systems

Table 4-6: Upload Test Result Fields for Specific Tests (Continued)

Test Type VITEK® and VITEK® 2

Data Max. OBSERVA® Required
/ Field VITEK® 2 Systems
Class Length Description (R)
Type Description Description
at1, 2 R 0 NA Suppressed NA
MIC Flag
a31, 2 R 8 Final MIC Result MIC AST Final MIC
a41, 2 R 2 Final Result Final AST Final
Interpretation Category
a51 R 26 Dosage Column NA See Note 4
1 (Repeatable)
a61 R 16 Dosage Column NA See Note 4
2 (Repeatable)
a71 R 16 Dosage Column NA See Note 4
3 (Repeatable)
an2 R 16 NA Non- See Note 4
expertised
Interpretation

Smear Test
tb T 10 Bottle Barcode NA NA
3
ra R 0 Result Separator NA NA
rs3 R 6 Smear Code NA NA
3
rm R 60 Smear Name NA NA
3
o4 R 6 Final Modifier NA NA
Code
o53 R 20 Final Modifier NA NA
Name

Screen Test
ra R 0 Result Separator NA NA
o1 R 6/15 Final Organism NA NA
Code
o2 R 60 Final Organism NA NA
Name
o4 R 6 Final Modifier NA NA
Code
o5 R 20 Final Modifier NA NA
Name
o6 R 6 Organism Group NA NA
Code
o7 R 30 Organism Group NA NA
Name
o8 R 20 Total Count Text NA NA
o3 R 6 Total Count Code NA NA
rh R Time Hours to Positive NA NA

514724-1EN1 Upload Specifics 4-15

Bidirectional Computer Interface Specification for VITEK® Systems

Table 4-6: Upload Test Result Fields for Specific Tests (Continued)

Test Type VITEK® and VITEK® 2

Data Max. OBSERVA® Required
/ Field VITEK® 2 Systems
Class Length Description (R)
Type Description Description

Blood Test
t1 T 2 Isolate Number NA NA
(Repeatable)
o1 T 6/15 Final Organism NA NA
Code
(Repeatable)
tb T 10 Bottle Barcode NA NA
rd T Date Result Date NA NA
ru T Time Result Time NA NA
re T 8 Elapsed Hours NA NA
rc T 2 Instrument Result NA NA
Code
ri T 20 Instrument Result NA NA
Name
rj T 2 Blood Test Final NA NA
Result Code
rk T 20 Blood Test Final NA NA
Result Name

1
For Susceptibility results, the ra through a7 fields are repeatable as a group (VITEK®, VITEK® 2,
and OBERVA®).
2 For Susceptibility results, the ra through an fields are repeatable as a group (VITEK® 2 Systems).
3 For Smear results, the ra through 05 fields are repeatable as a group (VITEK® and VITEK® 2).
4 In OBSERVA®, an unused BCI field may be assigned to a user-defined data field in OBSERVA® of

the same data class.

4.3.4 Upload Applications Message Format

The first field in a message is a message type which describes the content and format. When
a rsl message is indicated, the rest of the message follows this format:

1. First are patient demographics, followed by specimen, exam, tests, and results (if
available).
2. Each level down through test will have a complete set of levels above it. Each level uses
one field to mark its beginning.
3. Only one set of specimen demographics will follow patient demographics. Specimens will
only have one set of culture demographics, and exams will only have one set of test
demographics.
4. Result information may be sent, but is always treated as an update. For example, consider
a culture with two isolates. The first gets tested on day one, while the other gets tested on
day two. When the report for isolate two prints out, so does a repeat of isolate one.
5. When the a3 and a4 fields are both null (with no MIC or category call), they cause a
suppression of the a1 through a7 fields in VITEK® and VITEK® 2 and the a1 through an

514724-1EN1 Upload Specifics 4-16

Bidirectional Computer Interface Specification for VITEK® Systems

fields in VITEK® 2 Systems. When either field is null, it is sent without a value along with
the other fields.
6. Susceptibility test results are not divided between application messages. All results for a
test are sent in the same application message, even if the results come from more than
one AST card.

4.3.5 Descriptions of Fields in the Record Format

This table describes required components of fields in the basic record format.

Table 4-7: Component Requirements of the Record Format Fields

Record Component Requirements

Patient Demographic Always begin with the patient identification (pi) field. Any of the
Fields other patient demographic fields can follow. The specimen
demographics (si) field terminates this group.
Specimen Demographic This set of demographics always begins with the specimen
Fields separator (si) field. The si field is always null. Any of the other
specimen demographics may follow. The culture ID field (ci)
terminates this group.
Exam (Culture) Fields This set of information will begin with the culture ID field (ci) and
can be followed by any of the culture fields. The test separator (ta)
field terminates this group if enabled.
Test Fields One set of tests can accompany a set of exam fields. Test groups
begin with the ta field (if enabled), followed by the rt and t1 fields,
which indicate the test type and isolate number. The result
separator (ra) or message terminator (zz) terminates this group if
enabled.
Result Fields Organism fields transmit in numerical order beginning with o1 and
ending with o9. When enabled for transmission, the ar field
precedes antimicrobial (a1 through a7) fields, if appropriate.
Antimicrobial fields also transmit in numerical order.

Note: If users enable deduced drug information, the ad code will precede the
antimicrobial field (a1).

Note: Users can configure the zz field to mark the end of the results. If they do not,
the end of the packet indicates the end of the message.

4.4 Test Result Examples

In the following upload packet examples, line breaks are for sample purposes only. There are
no added line breaks in actual packets.

514724-1EN1 Upload Specifics 4-17

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 4-1: Identification Test

mtrsl|pi193301|pnHo, Ida|pl4|p24 St. Vincent|ppsu|

p5Spuds, W.
Prettigrew|pda|p6Adult|w1475|uaf|ubFemale|
si|ssu|s5Urine|s1zer|s7EU|spsor|s8Sorrell, John|
s102/21/1996|s208:45|s302/21/1996|s411:10|
ci020517|ctr|cnRoutine C&S|c3F|c4Final|na>|na5|nangb|
nbColony count > 100,000col/ml|nb5%|nb Gram negative
bacilli|ta|rtgni|t11|rr2|rn Gram Negative
Identification|rr22|t11|t2ID|t3Identification|t4F|
t5Final|tb123456|o1promir|o2proteus mirabilis|

Figure 4-2: Identification Test from a Blood Culture with ra and ta Fields Enabled

mtrs|pi193301|pnHo, Ida|pl4|St. Vincent|ppsu|p5Spuds,W.

Prettigrew|pda|p6Adult|w1475|uaf|ubFemale|si|ssu|s5Uri
ne|slzer|s7EU|spor|s8Sorrell, John|s102/21/
1996|s208:45|s302/21/
1996|s411:10|ci020517|ctr|cnRoutine
C&S|c3F|c4Final|na>|na5|nangb|nbColony count >
100,000col/ml|nb5%|nb Gram Negative
bacilli|ta|rtgni|t11|rr22|rn Gram Negative
Identification|rr22|t11|t21D|t3Identification|t4F|t5Fi
nal|tb123456|o1promir|o2proteus
mirabilis|o3360320001220|zz|

Figure 4-3: Susceptibility Test

mtrsl|pi118962|pnGentley, Dirk|pl2|p22nd J E|pprast|

p5Rastling, Fred|pda|p6Adult|w1277|
si|ssw|s5Nonsurgical Wound/Abscess|slicu|s7ICU|sprast|
s8Rastling, Fred|s106/06/1996|s222:45|
ci1759|ctr|cnRoutine C&S|c106/06/96|c3F|c4Final|x2Gall
bladder|nah|nbHeavy growth|rtkb|rnGram positive Kirby-
Bauer|rr1|ti1|tjVitek2-Wounds|tnInstrument Comments|
t2KB|t3Kirby-
Bauer|t4F|t5Final|o1strvir|o2streptococcus
viridans group|o6nes|o7Non-enterococcal Strep|nckb|
ndSensitivity performed by disk testing|y12
morphologies
isolated.|a1cf|a2Cephalothin|a3|a4S|a1c|
a2Chloramphenicol|a3|a4S|a1cc|a2Clindamycin|a3|a4S|a1
e|

514724-1EN1 Upload Specifics 4-18

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 4-4: Susceptibility Test from a Blood Culture / ra and ta enabled (VITEK® and
VITEK® 2 Only)

mtrsl|pi118962|pnGentley, Dirk|pl2|p22nd J E|pprast|

p5Rastling, Fred|pda|p6Adult|w1277|
si|ssw|s5Nonsurgical Wound/Abscess|slicu|s7ICU|sprast|
s8Rastling, Fred|s106/06/1996|s222:45|
ci1759|ctr|cnRoutine C&S|c106/06/96|c3F|c4Final|x2Gall
bladder|nah|nbHeavy growth|ta|rtkb|rnGram positive
Kirby-Bauer|rr1|ti1|tjVitek2-Wounds|tn|Instrument
Comments|t2KB|t3KirbyBauer|t4F|t5Final|o1strvir|o2str
eptococcusviridans group|o6nes|o7Non-enterococcal
Strep|nckb|ndSensitivity performed by disk testing|
y12morphologiesisolated.|ra|a1cf|a2Cephalothin|a3|a4S
|ra|a1c|a2Chloramphenicol|a3|a4S|ra|a1cc|a2Clindamyci
n|a3|a4S|ra|a1e|a2Erythromycin|a3|a4S|ra|a1peng|a2Pen
icillin-
G|a3|a4S|ra|a1tet|a2Tetracycline|a3|a4S|ra|a1va|
a2Vancomycin|a3|a4S|zz|

Figure 4-5: Screen Test (VITEK® and VITEK® 2 Only)

mtrsl|iiAM|itSC|pi299817|pnJones, Louise|plzop|p2Out
Patient|ppsco|p5Scott, Graham|pda|p6Adult|w10P|uaf|
ubFemale|
si|s02|ssear|s5Ear|s102/02/1996|s218:48|
ci54698|c3P|c4Preliminary|
nasns|nbSensitivity not by standardized method.
Confirm-ation of sensitivities to follow.|rtuid-
3|rr2|rnUrine
Identification|tiAM|tjVITEK|t2SC|t3Screen|t4F|t5Final|
o1PC|o2Positive Control|o4cnt0|o1prospe|o2Proteus
species|o4cnt0|o8> 50,000 cfu/ml|o3cnt2|zz|

Figure 4-6: Smear Test from a Blood Culture / ra and ta enabled (VITEK® and VITEK® 2
Only)

mtrsl|pi219513|pnBrown, James|pl7|p27 St.

Luke’s|ppowe|
p5Owens, C. Jesse|pda|p6Adult|w1774|uam|ubMale|
si|ssw|s5Nonsurgical Wound/Abscess|s17|s77 St. Luke’s|
spowe|s8Owens, C. Jesse|sl11/15/1996|s211:55|
ci110333|ctr|cnRoutine C&S|c111/18/1996|c3F|c4Final|
x2Back mass|nang3d|nbNo growth in 3 days|ta|rtvitest|
rr1|rnVitekTest|t2SM|t3Smear|t4F|t5Final|tb444|ra|
rssmear|o41|o51+|ra|rssmear|o42|o52+|zz|

514724-1EN1 Upload Specifics 4-19

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 4-7: Demographics Only

mtrsl|pi193301|pnHo, Ida|pl4|p24 St. Vincent|ppsu|

p5Spuds, W. Prettigrew|pda|p6Adult|w1475|uaf|ubFemale|
si|ssgf|s5Genital - Female|slzer|s7EU|spsor|s8Sorrel,
John|s102/21/1996|s210:20|s302/21/1996|s411:45|
ci020506|ctr|cnRoutine C&S|c102/23/1996|c3F|c4Final|
x2vagina|nah|na100|nanvf|nbHeavy growth|nb100%|
nbNormal vaginal flora|zz|

Figure 4-8: Blood Culture Test (VITEK® and VITEK® 2 Only)

mtrsl|idBMX|iiOT|itBC|pibcitest600|pnGallant, Hazel|
psf|pl4|p24 St. Vincent|pprich|pda|p6Adult|w1471|uaf|
si|s07|ssu|slsicu|s7SICU|sprich|s110/07/1992|s214:00|
sf0.0|
ci100167|c01|ctser|c110/11/1992|c211:08|c3P|na>|ta|
rtaer|rr7|tiOT|t2BC|t3Blood Culture|t4I|m3rm|tb943628|
rd12/25/
1996|ru14:30|re40|rc+|riPositive|rj+|rkPositive|
zz|

514724-1EN1 Upload Specifics 4-20

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 4-9: Sample AST (VITEK® 2 Systems)

mtrsl|iiV2|is123456789012|itSU|pi49562999|pv123456|pnDoe,
John A.|plicu|p2icu|pp
JJ12|p5JJ12|pcPatien|ptPatient comment goes
here|w1123456|si|s066|ssarm|s5arm|s1
04/01/2004|s304/01/2004|scSpecim|snSpecimen comment goes
here|ci9910123|c066|ctw
ound|cnwound|ta|rtAST-GN04|rr70|t11|o1entclo|o2Enteroba
cter cloacae|afBETA-LACTAMS|apHIGH LEVEL
CEPHALOSPORINASE|apEXTENDED SPECTRUM BE
TA-
LACTAMASE|afAMINOGLYCOSIDES|apWILD|afQUINOLONES|apPARTIALLY
RESISTANT|apRESIS
TANT QUIN-
1|apWILD|afFURANES|apRESISTANT|apWILD|afTRIMETHOPRIM/
SULFONAMIDES|apWI
LD|ra|a1am|a2Ampicillin|a3>=32|a4R|anR|ra|a1ams|a2Ampicilli
n/Sulbactam|a3>=32|a4
R|anR|ra|a1tcc|a2Ticarcillin/Clavulanic
Acid|a3>=128|a4R|anR|ra|a1pip|a2Piperaci
llin|a332|a4I|anI|ra|a1tzp|a2Piperacillin/
Tazobactam|a316|a4S|anS|ra|a1cz|a2Cefa
zolin|a3>=64|a4R|anR|ra|a1rox|a2Cefuroxime|a3>=64|a4R|anR|r
a|a1roxa|a2Cefuroxime

Axetil|a3>=64|a4R|anR|ra|a1cte|a2Cefotetan|a3>=64|a4R|anR|r
a|a1taz|a2Ceftazidim
e|a3>=64|a4R|anR|ra|a1ctr|a2Ceftriaxone|a332|a4I|anR|ra|a1f
ep|a2Cefepime|a3<=1|a
4S|anS|ra|a1azm|a2Aztreonam|a316|a4I|anI|ra|a1imi|a2Imipene
m|a3<=0.5|a4S|anS|ra|
a1an|a2Amikacin|a3<=2|a4S|anS|ra|a1gm|a2Gentamicin|a3<=1|a4
S|anS|ra|a1tob|a2Tobr
amycin|a3<=1|a4S|anS|ra|a1cip|a2Ciprofloxacin|a3<=0.25|a4S|
anS|ra|a1lev|a2Levofl
oxacin|a3<=0.25|a4S|anS|ra|a1ftn|a2Nitrofurantoin|a364|a4I|
anR|ra|a1sxt|a2Trimet
hoprim/
Sulfamethoxazole|a3<=20|a4S|anS|ra|ad|a1amx|a2Amoxicillin|a
3|a4R|an|ra|ad
a1amc|a2Amoxicillin/Clavulanic
Acid|a3|a4R|an|ra|ad|a1mz|a2Mezlocillin|a3|a4I|a
n|ra|ad|a1cid|a2Cefonicid|a3|a4R|an|ra|ad|a1cm|a2Cefamandol
e|a3|a4R|an|ra|ad|a1t
ax|a2Cefotaxime|a3|a4I|an|ra|ad|a1zox|a2Ceftizoxime|a3|a4I|
an|ra|ad|a1mem|a2Mero
penem|a3|a4S|an|zz|

514724-1EN1 Upload Specifics 4-21

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 4-10: Sample ID (VITEK® 2 Systems)

mtrsl|iiV2|is123456789012|itID|pi49562999|pv123456|pn
Doe, John A.|plicu|p2icu|pp
JJ12|p5JJ12|pcPatien|ptPatient comment goes
here|w1123456|si|s067|ssarm|s5arm|s1
04/01/2004|s304/01/
2004|ci99109|c067|ctwound|cnwound|ta|rtGP|rr12|t11|o1
gember|o
2Gemella bergeri|o3000022000401001|o996|zz|

514724-1EN1 Upload Specifics 4-22

 5 BCI Utilities (VITEK® and VITEK® 2 Only)

5.1 Introduction

Note: To learn about BCI utilities that relate to VITEK® 2 Systems, see the
VITEK® 2 Systems Software User Manual.

Note: To learn about BCI utilities that relate to OBSERVA®, see the OBSERVA®
Software User Manual.

BCI utilities allow users to customize the interface. This provides the flexibility a bioMérieux
computer needs to communicate simultaneously with a variety of host computers. BCI
recognizes and uses several protocols and port parameters depending on the needs of the
host system.

BCI allows the configuration of one or more ports for various upload and download options. It
also lets users view data transmissions, transaction logs, and status logs.

5.2 BCI Main Window

To access BCI utilities, open the BCI window by clicking BCI in the bioLIAISON® Main Menu.

Figure 5-1 shows two ports assigned to use BCI. One is connected to an unnamed computer
and the other to a BacT/VIEW® system in the microbiology laboratory. The fields in the main
window provide information about the status of each port and how they are being used.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-1

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 5-1: BCI Main Menu

1 2 3 4 5

1 — User Port Name — This is the user-assigned name that identifies the host computer the
port serves.
2 — BCI Status — This shows the status of communications on each port. Values are:
• Started — BCI allows communications to occur on the port.
• Stopped — Communications do not occur on the port.
3 — Host Status — This shows the status of the host computer connected to the port. Values
are:
• In Service — The host is available for uploads.
• Out of Service — The host is not available for uploads.
• No Response — The bioMérieux computer tries to send data to the host but
receives no confirmation.
4 — Upload — Shows whether or not the port can receive uploads. Values are:
• Enabled — BCI will allow bioMérieux programs to upload to the host.
• Disabled — BCI will not accept data from bioMérieux programs but will allow
uploads of data already queried for upload.
5 — Download — Shows whether or not the port can process downloads. Values are:
• Enabled — BCI will process downloaded transactions.
• Disabled — BCI will not process downloaded transactions, but will allow
downloads.

5.3 Port Configuration Options

The Port Configuration utility lets users set parameters for each BCI port. To access the utility,
select a port in the BCI window and click the Ports button.

Note: You can get a printout of current configuration settings by selecting File >
Print Configuration in the BCI window.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-2

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 5-2: Port Configuration Options

The selection window lists each port and its configuration currently on the bioMérieux
computer. To configure a BCI port, click on a port in the list.

Figure 5-3: Configuring a BCI Port

5.3.1 Possible Port Configuration Settings

Table 5-1: Configuration and Setting Description

Configuration Setting Description

Product Set to BCI.
Unique ID This is the user-defined name for the port.
Login State Set to Disable.
BAUD Rate Set as required. Available settings are 300, 1200, 2400,
9600, and 19,200. The default is 9600.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-3

Bidirectional Computer Interface Specification for VITEK® Systems

Table 5-1: Configuration and Setting Description (Continued)

Configuration Setting Description

Parity Set as required. Available settings are Even, Odd, and
None. The default is None.
Bits per Character Set as required. Available settings are 7 and 8. The default
is 8.
Number of Stop Bits Set as required. Available settings are 1 and 2. The default
is 1.

Clicking Execute saves the settings.

5.4 Protocol Configuration

The Protocol Configuration utility sets the communications protocol, data separators, and
other protocol specific parameters for a port. To access the utility, select a user port name and
click Protocol in the BCI main window.

Figure 5-4: Protocol Configuration

5.4.1 Communications Protocols

BCI supports three communications protocols plus a manual mode for testing purposes.

• bioMérieux Literal. A proprietary protocol developed by bioMérieux.

• bioMérieux Literal (Alternate). This is the same as the Literal protocol except all
messages must be framed with an <STX> and <ETX>. It expects responses to the
checksum <GS> record after the <ETX>. See the bioMérieux Communications
Protocol section for details.
• ASTM E1381. A low level protocol that complies with ASTM E1381.
• Manual. A tool that helps establish initial connections to a host.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-4

Bidirectional Computer Interface Specification for VITEK® Systems

5.4.1.1 Record and Field Separators

This is a listing of the record and field separators available for data transmissions. See BCI
Upload Options on page 5-6 and BCI Download Options on page 5-9 for descriptions of data
sent with BCI.

Field Terminator Characters — These can be one to three characters. The default is a
vertical bar ( | ). Valid characters listed in Table 5-2.

Table 5-2: Field Terminator Characters

! @ # $ % ^
& * ( ) - +
| = < > / ?
[ ] { } \ .

Note: Commas are not allowed and separators must be unique. It is recommended
that you use only / : or - as the date separator.

Date — These are single characters only which separate month, day, and year data. The
default character is a slash (/).

Time — These are single characters that separate hour, minute, and second data. The default
character is a colon (:).

5.4.2 bioMérieux Literal Protocol Parameters

These parameters apply only to the bioMérieux Literal and Literal (Alternate) protocols.

5.4.2.1 End of Record <CR> <LF>

This option appends a <CR><LF> sequence to each record in the packet. Each record type
can also be toggled so they can apply on a per record basis. The default end of record does
not append <CR><LF>.

5.4.2.2 Delays

There are three types of delays:

Last Master (Seconds) — This lets users set the amount of time BCI will wait before starting
another session. (It sends an <ENQ> when it was master of the last session.) Values can be
from 0 to 99 seconds. The default is two seconds.

Note: The host should have a similar delay to prevent it from controlling the line
continuously.

InterRecord (Seconds) — If the host system requires additional time to clear its input buffers,
users can adjust the delay time an instrument uses between record transmissions. Values can
be from 0 to 99 seconds. The default is zero.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-5

Bidirectional Computer Interface Specification for VITEK® Systems

InterMessage (Seconds) — Users can also insert a delay time between communications
messages using this option. Values can be from 0 to 99 seconds. The default is two seconds.

5.4.2.3 Retries

<ENQ> Limit — This is the number of times BCI will try to contact the host to begin a session.
When the retry limit is reached, BCI logs an error and begins queueing data for upload and
notifies the user with a message. If the host responds, BCI sends any queued data and adds a
note to the message log that the host responded.

Values can be from 0 to 99 tries. Choosing zero means BCI will not log an error or send a
message to the message beeper. In all cases BCI will continue trying to send. The default is
three tries.

<ENQ> Interval (Seconds) — This is the amount of time BCI will wait before the next
transmission of an <ENQ> following a no response or <NAK>. Values can be from 0 to 99
seconds. The default is 10 seconds.

Checksum Limit — The communications layer will retransmit an entire packet if it receives a
<NAK> to a <GS> record or the checksum <ACK> time out expires. When this limit is
reached, BCI logs an error and tosses the packet. Values can be from 0 to 99. The default is
three tries.

Checksum Interval (Seconds) — This is the amount of time BCI will wait before
retransmitting a packet after receiving a bad or no checksum. Values can be from 0 to 99
seconds. The default is 10 seconds.

5.4.2.4 Timeouts

Checksum (Seconds) — This is the amount of time BCI will wait for an <ACK> to a <GS>
record. If the time expires and BCI still has not received either an <ACK> or a <NAK>, it will
retransmit the entire packet. Values can be from 0 to 99. The default is three seconds.

Host Response (Seconds) — During a host-initiated session, BCI waits for data from the
host. If it does not receive any data during a specified time, it times out and sends an <EOT>
to the host and terminates the session. It also logs an error and assumes the host has ended
the session. Values can be from 0 to 99 seconds. The default is three seconds.

5.4.2.5 Character Set Options

BCI supports the ISO8859-1 and IBM-850 character sets.

5.4.2.6 Modem Dial String

Use this option to enter the modem number if there is a remote connection to a device via
modem.

5.5 BCI Upload Options

To access upload options, select Upload > Configuration in the BCI Main Menu.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-6

Bidirectional Computer Interface Specification for VITEK® Systems

5.5.1 Upload Configurations

5.5.1.1 Field Length

When this option is set to Fixed, BCI pads fields with spaces if necessary to send their
maximum size. When set to Variable, BCI does not pad with spaces. The default setting is
Variable.

5.5.1.2 Case of Data

This option lets users select either all upper case or all lower case letters for alphabetic data.
The As Is setting does not modify characters. If set to upper case, all characters except the
checksum transmit in upper case. The default setting is As Is.

5.5.1.3 Miscellaneous Tests

There are several sensitivity results which have atypical susceptibility result formats. If
enabled, the literal upload transmits these results as if they were antibiotics in the a1–a7
fields. Suppressing a particular test means its results are not sent. See Appendix D,
Antimicrobial MICs and Categories.

5.5.1.4 CAR Rules (bioLIAISON®)

When this option is set to Applied, the bioLIAISON® Conditional Antimicrobial Reporting
Rules are enforced during uploads. Only specified antimicrobials transmit to the host. If the
option is set to Not Applied, all antimicrobial results transmit but some may be marked by the
(ar) field to indicate to the host that the user has CAR rules and if set to Applied, the drug
would not be sent. The default setting is Not Applied.

5.5.1.5 Deduced Drugs

The VITEK® 2 has a method to deductively analyze susceptibility results that uses a special
antimicrobial table. Even if a laboratory chooses to use this VITEK® 2 feature, it may not want
deduced results to upload to a host. This option tells BCI whether or not to allow the upload of
deduced results. The default is Allowed.

5.5.1.6 Leading Zeros

Because some LIS systems require a certain number of digits in an exam ID, this option lets
users designate the size in characters of exam IDs by inserting zeros in front of the first digit.
Using the slider bar, they can force the exam ID to be up to twenty characters long. The
default is zero indicating no added zeros.

5.5.1.7 Date Format Options

BCI contains six date format options. They include both two-and four-digit year formats.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-7

Bidirectional Computer Interface Specification for VITEK® Systems

Figure 5-5: Date Format

5.5.2 Upload Fields to Transmit

This window lets users select the fields they want to upload. Clicking buttons to the left of the
field code toggles the field on and off. BCI uploads toggled fields.

5.5.3 BMX Data Configuration

This window lets users specify which bioLIAISON® programs can upload information to the
host for a specific port.

Figure 5-6: BMX Data Configuration

5.5.4 Enable Upload

This option enables uploads for the port selected in the main window. The current status for
each port appears under the UPLOAD column.

5.5.5 Disable Upload

This option disables uploads for the port selected in the main window. The current status for
each port appears under the UPLOAD column.

5.5.6 Host In Service

This option changes the host status to In Service making it unnecessary for the host to
transmit a Back in Service <BIS> message.

5.5.7 Host Out Of Service

This option changes the host status to Out of Service making it unnecessary for the host to
transmit an out of service <OOS> message.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-8

Bidirectional Computer Interface Specification for VITEK® Systems

5.6 BCI Download Options

To select download options, click Download > Configuration in the BCI main window.

5.6.1 Download Configuration

This window provides several options for configuring data downloaded from the host to the
bioMérieux computer.

5.6.1.1 Duplicate Demographics Update

This option lets users decide whether or not they want BCI to update records in the
bioLIAISON® database when downloads contain new information. If enabled, this option
updates existing patient, specimen, and exam demographics if the download contains a
matching exam and patient ID and the exam status is preliminary.

If the update changes the exam type, the update still occurs, but a notation about the change
goes to the download error log. Successful updates depend on the following conditions:

1. The exam must have a preliminary status.

2. Final exams never update, even if the exam and patient IDs match the input packet.
3. Only one preliminary exam can have matching exam and patient IDs. If more than one
preliminary exam matches, BCI rejects the update and issues an error message.
For either setting, if there is no match bioLIAISON® creates a new specimen and exam record
in the database, including tests and results if sent. Even if a final exam matches the input
packet, bioLIAISON® still creates the new records because final exams are not considered
during the matching process.

When disabled, BCI does not update existing exam, patient, and specimen records. Instead, it
issues a message.

Table 5-3: Duplicate Demographics Updating Options

Enabled Disabled
if preliminary... the database if preliminary... the database gives a
updates demographics message
if final... the database inserts a new if final... the database inserts a new
specimen and exam specimen and exam

5.6.1.2 Initialize Specimen Data

When enabled, this option uses the location (pl), service (px), and physician (pp) fields in the
patient block to update the corresponding specimen fields in the database when the host does
not download the specimen fields s1, sx, and sp.

When disabled, these specimen fields are left blank.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-9

Bidirectional Computer Interface Specification for VITEK® Systems

5.6.1.3 Date Formats

Figure 5-7: Date Format

Dates are configurable to comply with requirements for four-digit date formats. If the LIS is
downloading two-digit years, BCI will interpret them so they fall in the range between 90 years
in the past to 10 years in the future. An example is shown in Table 5-4.

Table 5-4: Date Configurations

Today’s LIS BCI LIS LIS BCI

BCI Says
Date Sends Says Sends Sends Says
1998 98 1998 08 1908 07 2007
1999 98 1998 09 1909 08 2008
2000 98 1998 10 1910 09 2009

5.6.2 Download Fields to Process

This window gives users the ability to select the fields they want to process from the host
computer. Clicking the buttons to the left of the field code toggles the field on and off. BCI
processes any fields with depressed shaded buttons. Disabled fields cannot be toggled off.

5.7 Running BCI

After users set configuration options for the port and select upload and download options, they
can start communications. This section describes the operating functions accessed in the
main window.

5.7.1 Start BCI

Clicking Start BCI begins communications for the selected port(s). The status for the port(s)
changes to Started in the main window.

5.7.2 Stop BCI

Clicking Stop BCI stops communications for the selected port(s). The status for the port(s)
changes to Stopped in the main window.

5.7.3 View Data

When communications are running, users can view transmissions online by clicking View
Data.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-10

Bidirectional Computer Interface Specification for VITEK® Systems

Messages scroll across the window as data transmits between the two computers. Host data
highlights in reverse video and bioMérieux data appears in black text. Functions available in
this window are listed in Table 5-5.

Table 5-5: View Data Window Buttons

Button Function
CLEAR Clears messages from the window (but not the data file)
BIS Sends a back in service message to the host
OOS Sends an out of service message to the host
TEST Sends a test pattern to the host

When a port is configured for manual mode, the View Data window displays automatically.
The BIS, OOS, and TEST buttons are disabled and the following functions become active.

Table 5-6: View Data Window Buttons in Manual Mode

Button Function
ENQ Sends line request signal to the host
ACK Sends an acknowledgment signal to the host
NAK Sends a negative acknowledgment signal to the host
Send Text Sends a text string to the host

5.8 Logs

To access BCI logs, click Logs in the BCI main window.

5.8.1 Upload Transaction Log

The upload transaction log provides information on data transmitting from an instrument to the
host computer.

The upload transaction log lists transmitted data by:

Date/Time — This is the date and time the data received its current status.

Port — This is the port to which the data uploaded.

Instrument — This is the type of instrument from which the data uploaded. See Appendix H
for a listing of instruments and codes.

Patient/Exam ID — This is the patient and exam ID for the transmitted test data.

Iso — This is the isolate number for the test result.

Test Type — This is the type of test transmitted. See Appendix F for a listing of test types.

Status — This is the status of the upload determined by BCI. Possible statuses are:

• To Be Processed — This means BCI received data from a bioMérieux program,

but has not yet processed it into the bioMérieux literal format.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-11

Bidirectional Computer Interface Specification for VITEK® Systems

• To Be Sent — This means BCI has processed the data for upload and is waiting to
send it to the host.
• Sent — The host received and acknowledged the upload.
• Failed — The transaction was not transmitted to the host and the packet discarded.
The log also has search and filtering functions for finding and deleting transactions.

Note: See the BCI Operator’s Manual for more information.

5.8.2 Download Transaction Log

The download transaction log provides information about data transmitting from the host to the
bioMérieux computer.

This window functions similarly to the Upload Transaction log except that its status field has
different meanings.

• To Be Processed — This means BCI received data downloaded from the host.
• To Be Sent — This means BCI processed the downloaded data from the host and
is waiting to send it to the bioMérieux product database.
• Sent — This means BCI has transmitted downloaded data to the bioLIAISON®
database.

Note: See the BCI Operator’s Manual for more information.

5.8.3 Status Log

The Status Log shows messages from the BCI program.

Note: See the Bidirectional Computer Interface Operator Manual for bioLIAISON®
for more information.

5.8.4 Communications Data Log

This log shows data transmitted across a port.

5.8.5 Download Error Log

The download error log maintains a listing of error messages and problems BCI encountered
while processing data in a download transaction. Date errors are logged in the Status Log.

Note: Messages in the download log purge automatically as the log fills. Older data
is an indication that there were relatively few errors.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-12

Bidirectional Computer Interface Specification for VITEK® Systems

5.9 Configuration Options

5.9.1 Host Field Translations

This utility lets users select the bioLIAISON® drug, organism, physician and source tables and
specify either default bioLIAISON® or special host codes for drug and organism fields. Users
can also translate the physician and specimen source tables. BCI uses all four translation
tables for downloads and uploads.

5.9.1.1 Drug Field Translations

bioMérieux provides a default drug table in bioLIAISON® which contains drug names and
codes. This window lets users set different codes for those drugs if required by the host
system. When transmitting a drug code field (a1), the bioMérieux computer checks this table
for user-defined codes. If there are none, it transmits the bioMérieux default code. Codes
defined by the user in this window can be up to 15 characters long.

Note: The vertical pipe ( | ) may not be used in a host code.

5.9.1.2 Organism Field Translations

Similar to the drug field table, bioMérieux provides a default organism table in bioLIAISON®
which contains organism names and codes. This window lets users set new codes for those
organisms if required by the host system. When transmitting an organism code field, the
bioMérieux computer checks this table for user-defined codes. If there are none, it transmits
the bioMérieux default code. Codes defined by the user in this window can be up to 15
characters long.

5.9.1.3 Physicians and Specimen Source Translations

There are two other translation menus — one for physicians and one for specimen source.
They work the same way as the drug and organism field menus.

5.9.2 Transaction Routing

The transaction routing program displays the routing paths of downloads from each port and
allows users to change settings on a port by port basis. This option was designed specifically
for users who want blood culture results to transfer to the host from a blood culture instrument
as soon as they become available.

There have to be at least two designated BCI ports in order to use transaction routing.

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-13

Bidirectional Computer Interface Specification for VITEK® Systems

514724-1EN1 BCI Utilities (VITEK® & VITEK® 2 Only) 5-14

 A Field Type Definitions

These are descriptions of valid upload and download fields.

Table A-1: Field Type Definitions

VITEK® and
VITEK® 2
Field VITEK® 2 Type Upload/
Systems Definition and Use
Code and Name Download
Description
Description
mt Message Type Message Type U/D A unique code identifying the
type of message that is being
sent.
id Instrument ID NA U/D A unique code assigned by an
instrument system. BCI uses it
to determine from where data
was sent.
ii Instrument System Instrument U A unique code assigned to an
Code Code instrument system.
bioLIAISON® uses it to
determine where a test came
from.
This field is useful for hosts that
need immediate identifications in
a packet, so it can route the
packet to a desired destination.
(This is the same data as the ti
field. It is not applicable if there
are no tests or results.)
is NA Instrument U A unique code assigned to the
Serial Number VITEK® 2 Compact instrument
that processed the test.
it Test Group System Test Group U A unique code assigned to an
Code Code instrument system which
contains a unique set of codes
for grouping tests. It is used to
determine which test and result
table should hold test data. Is
also an optional field that follows
the instrument code field.
pi Patient.System Code Patient ID U/D A unique code assigned by an
instrument system to identify a
patient.
pn Patient.Name Patient Name U/D Identifies the patient by name.
pb Patient.Birthdate NA U/D Specifies the patient date of
birth.
ps Patient.Sex NA U/D Specifies the patient gender. Is a
free text field.

514724-1EN1 Field Type Definitions A-1

Bidirectional Computer Interface Specification for VITEK® Systems

Table A-1: Field Type Definitions (Continued)

VITEK® and
VITEK® 2
Field VITEK® 2 Type Upload/
Systems Definition and Use
Code and Name Download
Description
Description
pl – p2 Patient.Location User Patient U/D Usually indicates a patient
Code and Name Location Name location by ward, floor, unit, or
room. BCI uploads and
downloads the codes, but only
uploads the name.
px, p3 Patient.Service User NA U/D Usually indicates an institution’s
Code and Name functional service area (for
example surgery, ICU,
obstetrics, etc.). BCI uploads
and downloads the codes, but
only uploads the name.
po, p4 Patient.Diagnosis NA U/D Indicates a standard diagnosis.
User Code and Name BCI uploads and downloads the
codes, but only uploads the
name.
pp, p5 Patient.Physician Patient U/D Identifies the physician
User Code and Name Physician responsible for the patient or
Code and case. BCI uploads and
Patient downloads the codes, but only
Physician ID uploads the name. For VITEK®
and VITEK® 2, these are
translatable fields.
pa Patient.Admission NA U/D Indicates the date a patient was
Date admitted to an institution.
pd, p6 Patient.Dosage Group NA U/D Identifies the dosage group —
User Code and Name usually adult or pediatric. Code
selected from the dosage group
table in bioLIAISON®. BCI
uploads and downloads the
codes, but only uploads the
name.
pc, pt Patient.Comment NA U/D These fields contain patient
User Code and Text comments. In VITEK® and
VITEK® 2, they can repeat
multiple times in a single record.
BCI uploads and downloads the
codes, but only uploads the text.
pv NA Patient U/D Identifier for patient visits.
Alternate ID
w1 – Patient.User Text Patient Wild 1 U/D These fields contain free text.
w8 Users can enter any data they
want here.
Note: VITEK® 2 Systems maps
w1 to pv.
ua – Patient.Extra User NA U/D These codes and fields contain
uf, Codes and Names user defined information about
u1 – patients. BCI uploads and
u4 downloads the codes, but only
uploads the names.

514724-1EN1 Field Type Definitions A-2

Bidirectional Computer Interface Specification for VITEK® Systems

Table A-1: Field Type Definitions (Continued)

VITEK® and
VITEK® 2
Field VITEK® 2 Type Upload/
Systems Definition and Use
Code and Name Download
Description
Description
p7 – Patient.Address NA U Contains address information for
p0 Lines 1 thru 4 the primary physician.
si Specimen Separator Specimen U/D This field separates patient
Separator demographics from specimen
data. Is always sent as a null
field.
s0 Specimen.Specimen Specimen U This field contains a relative
System Code System Code specimen number.
ss, s5 Specimen.Source Specimen U/D Contains a basic specimen type
User Code and Name Source Code (for example blood, urine, or
and Specimen stool). Fields are host
Source Name translatable. BCI uploads and
downloads the codes, but only
uploads the names.
st, s6 Specimen.Site User NA U/D Indicates the place on a patient’s
Code and Name body where specimens were
taken. BCI uploads and
downloads the codes, but only
uploads the names.
sl, s7 Specimen.Location Specimen U/D Identifies the institution location
User Code and Name Collection Date where the specimen was taken,
which is often the same as the
patient location. BCI uploads
and downloads the codes, but
only uploads the name.
sp, s8 Specimen.Physician NA U/D Identifies the physician
User Code and Name requesting specimens taken for
an exam. BCI uploads and
downloads the codes, but only
uploads the name. Fields can be
translated.
sx, s9 Specimen.Service NA U/D Identifies functional areas within
User Code and Name an institution, as opposed to a
specific location (for example,
pediatrics, oncology, etc.). BCI
uploads and downloads the
codes, but only uploads the
name.
sy – Specimen.Status NA U/D Indicates the status (preliminary,
sz System Code and final, etc.) of a specimen. BCI
Name uploads and downloads the
codes, but only uploads the
name.
s1 Specimen.Collection Specimen U/D Indicates the date on which a
Date Collection Date specimen was collected.
s2 Specimen.Collection Specimen U/D Indicates the time a specimen
Time Collection was collected.
Time

514724-1EN1 Field Type Definitions A-3

Bidirectional Computer Interface Specification for VITEK® Systems

Table A-1: Field Type Definitions (Continued)

VITEK® and
VITEK® 2
Field VITEK® 2 Type Upload/
Systems Definition and Use
Code and Name Download
Description
Description
s3 Specimen.Receipt Specimen U/D Indicates the date a specimen
Date Receipt Date was received in the lab.
Note: VITEK® 2 Systems does
not download this field. Instead,
it copies the Collection Date into
this field for uploads.
s4 Specimen.Receipt Specimen U/D Indicates the time a specimen
Time Receipt Time was received in the lab.
Note: VITEK® 2 Systems does
not download this field. Instead,
it copies the Collection Time into
this field for uploads.
sf Specimen.Patient NA U/D Usually indicates a patient’s
Temp body temperature at the time of
specimen collection.
so Specimen.Collection NA U/D This field is used in place of the
Number collection date and time fields to
order and sort collected
specimens.
sc – Specimen.Comment Specimen U/D Contains user-entered
sn User Code and Text Comment comments about the specimen.
Code and In VITEK® and VITEK® 2, the sc
Specimen and sn fields can repeat multiple
Comment Text times in a single record. BCI
uploads and downloads the
codes, but only uploads the text.
ug – Specimen.Extra User NA U/D These are additional coded
uv Codes and Text fields for miscellaneous
specimen information. BCI can
upload and download the codes,
but only uploads the text.
sa, sb, Specimen.Address NA U Contains address information for
se, sd Lines 1 - 4 the specimen requesting
physician.
wa – Specimen.User Text 1 NA U/D These fields contain free text.
we -5 Users can enter any data they
want here.
ci Exam.User Code Lab ID U/D Also referred to as the lab ID,
exam ID, or accession number.
This is a unique number
assigned by the instrument
system to link test results with
the correct patient record. In a
results message, the culture ID
precedes test results.
c0 Exam.Exam System Lab ID System U This is an exam counter field.
Code Code

514724-1EN1 Field Type Definitions A-4

Bidirectional Computer Interface Specification for VITEK® Systems

Table A-1: Field Type Definitions (Continued)

VITEK® and
VITEK® 2
Field VITEK® 2 Type Upload/
Systems Definition and Use
Code and Name Download
Description
Description
ct, cn Exam.Exam Type Culture Type U/D Indicates the culture (exam) type
User Code and Name Code and (for example, routine, AFB, or
Culture Type yeast). BCI uploads and
Name downloads the codes, but only
uploads the text.
c1 Exam.Completion NA U/D Indicates the date an exam was
Date completed.
c2 Exam.Completion NA U/D Indicates the time an exam was
Time completed.
c3, c4 Exam.Status System NA U Identifies the status of a culture
Code and Name as Preliminary or Final.
x1 – Exam.User Text 1 - 2 NA U/D These fields contain free text.
x2 Users can enter any data they
want here.
na – Exam.Comment User NA U/D Contains comments about
nb Code and Text cultures. These fields can repeat
multiple times in a single record.
BCI uploads and downloads the
codes, but only uploads the text.
ta Test Separator Test Separator U/D Test separator field. Required
for downloads.
rt – rn Test.Test Type Code Card Type U/D This is the first field in a test
and Name result. It indicates the type of
results a host computer can
expect. BCI uploads and
downloads the codes, but only
uploads the name. VITEK® 2
Systems does not upload the
name.
rr Test.Test System Isolate System U This is a relative test number
Code Code field. It allows for a unique
identification of each test
associated with a particular
exam. If users modify and
retransmit results, the relative
test number allows the host to
make changes to the correct
result record.
ti – tj Test.Instrument NA U A unique code assigned by the
System Code and instrument system to identify
Name itself to a host. Also contains the
name of a bioMérieux instrument
system.
tc, tn Test.Instrument NA U Contains an instrument analysis
Comment Code and generated code and comment.
Text Users cannot modify the code or
text.

514724-1EN1 Field Type Definitions A-5

Bidirectional Computer Interface Specification for VITEK® Systems

Table A-1: Field Type Definitions (Continued)

VITEK® and
VITEK® 2
Field VITEK® 2 Type Upload/
Systems Definition and Use
Code and Name Download
Description
Description
t2 – t3 Test.Test Group NA U Contains a unique set of codes
System Code and for grouping tests. They
Name determine which test and result
tables should hold test data.
(See the ti definition.)
t4 – t5 Test.Status System NA U/D Indicates the status of individual
Code and Name tests. Users can modify or add to
the bioLIAISON® default
statuses of Final, Preliminary,
and Duplicate. BCI uploads and
downloads the codes, but only
uploads the name.
m3 – Test.Technician User NA U/D Contains the name of the
m4 Code and Name laboratory technologist who ran
a test. BCI uploads and
downloads the codes, but only
uploads the name.
nc – Test.Comment User NA U/D Contains comments concerning
nd Code and Text tests. BCI uploads and
downloads the codes, but only
uploads the text.
y1 – 4 Test.User Text 1 - 4 NA U/D These fields contain free text.
Users can enter any data they
want here.
t1 Test.Isolate Number Isolate Number U/D This field indicates the isolate
results belong to. Is also called
the dash number on VITEK®
cards.
tb Test.Bottle Barcode NA U/D This is the barcode for a blood
culture bottle.
tt AES Free Text NA U Contains therapeutic comments
from the Advanced Expert
System™.
t6 – t7 Test.Preliminary NA U/D Contains a user-defined
Organism Code and preliminary organism
Name identification. Can be translated
using BCI’s host field translation
utility. BCI uploads and
downloads the codes, but only
uploads the name.
t8 – t9 Test.Preliminary NA U/D Contains a user-defined
Modifier User Code preliminary organism modifier.
and Name BCI uploads and downloads the
codes, but only uploads the
name.

514724-1EN1 Field Type Definitions A-6

Bidirectional Computer Interface Specification for VITEK® Systems

Table A-1: Field Type Definitions (Continued)

VITEK® and
VITEK® 2
Field VITEK® 2 Type Upload/
Systems Definition and Use
Code and Name Download
Description
Description
o1 – Test.Final Organism Final Organism U/D Contains the code and name of
o2 User Code and Name Code and Final the final organism identification.
Organism Can be translated using BCI’s
Name host field translation utility. BCI
uploads and downloads the
codes, but only uploads the
name.
o3 Test.Final Bionumber Final U/D Contains a calculated
Bionumber bionumber from the VITEK®
computer. Interpretation is
dependent on the VITEK® test
type. VITEK® and VITEK® 2
Systems use bionumbers in
organism identifications. VITEK®
2 does not.
For VITEK® urine identification
cards, the o3 field acts as the
total count code.
o4 – Test.Final Modifier NA U/D Contains additional information
o5 User Code and Name from the lab about tests and
organisms (for example, Heavy
Growth, or 100.000 col/mL). BCI
uploads and downloads the
codes, but only uploads the
name.
o6 – Test.Organism Group NA U Contains user-defined entries
o7 User Code and Name from the bioLIAISON® table that
helps organize organisms by
class.
o9 Test.Percent Percent U This field supplies the percent
Probability Probability probability calculation of an
identification.
rd, ru Test.Result Date and NA U/D Indicates the date and time a
Time blood culture instrument
determined a test result.
re Test.Elapsed Hours NA U/D Indicates the number of hours a
blood culture bottle was in the
instrument before determining a
result.
rc, ri Test.Instrument NA U/D This field contains the reaction
Result System Code determined by an instrument for
and Name a blood culture test. Users
cannot modify the value. BCI
uploads and downloads the
codes, but only uploads the
name.

514724-1EN1 Field Type Definitions A-7

Bidirectional Computer Interface Specification for VITEK® Systems

Table A-1: Field Type Definitions (Continued)

VITEK® and
VITEK® 2
Field VITEK® 2 Type Upload/
Systems Definition and Use
Code and Name Download
Description
Description
rj – rk Test.Final Result NA U/D Contains the confirmed result for
System Code and a blood culture as determined by
Final Bottle Result the laboratory technician. BCI
Name uploads and downloads the
codes, but only uploads the
name.
af NA Antibiotic U This field contains the higher
Family level Drug Family name that the
Antibiotic(s) belong to. This field
may occur one to many times for
each upload transaction.
ap NA Phenotype U This field contains the name of
Name the resistance mechanism (for
example, Phenotype) for the
Drug(s) belonging to the
Antibiotic Family. This field may
occur one to many times for
each Antibiotic Family.
ra Result Separator Result U/D Result separator field. Required
Separator for downloads.
rs – Result.Smear User NA U/D Contains user-defined codes
rm Code and Name and text describing a smear
observation. BCI uploads and
downloads the codes, but only
uploads the name.
o8 Result.Total Count NA U Contains the total count text for
a VITEK® Urine Identification
card.
rh Result.Hours to NA U Indicates the number of hours a
Positive blood culture bottle processed
before determining positive
results.
ar Result.Indicator NA U This field suppresses reporting
Character of antimicrobials. If the field
precedes an antimicrobial code
or name field (a1 or a2), it
indicates to the host that the
bioMérieux user does not want
that drug’s results on patient
reports.
ad Deduced Drug Deduced U/D This is the deduced drug
Antibiotic Flag indicator.

514724-1EN1 Field Type Definitions A-8

Bidirectional Computer Interface Specification for VITEK® Systems

Table A-1: Field Type Definitions (Continued)

VITEK® and
VITEK® 2
Field VITEK® 2 Type Upload/
Systems Definition and Use
Code and Name Download
Description
Description
a1 – Result.Drug User Antibiotic Code U/D These fields contain either the
a2 Code and Name and Antibiotic mnemonic or name of drugs
Name reporting from the bioMérieux
computer. Either field can upload
to the host. Can be translated
using BCI’s host field translation
utility. BCI uploads and
downloads the codes, but only
uploads the name.
a3 Result.Final MIC Result MIC U/D This field contains an
antimicrobial’s MIC value. The
value relates to the previous
drug as defined by the a1 and a2
fields. Users can modify MICs
and calls in bioLIAISON®.
a4 Result.Final Result Final U/D This field contains the category
Interpretation interpretation call for the drug
defined by the a1 and a2 fields.
Users can modify categories
using the bioLIAISON® table
maintenance.
a5 – Result.Dosage NA U These fields contain additional
a7 Columns 1 - 3 user-defined drug information
and follow the a1 and a2 fields.
an NA Non-expertized U This field contains the
Results Instrument Interpretation result
before AES expertization (the
final Expertized Interpretation is
sent in the a4 field). If enabled,
the an field will be sent with
each Antibiotic. In some cases it
will contain a result, in other
cases it will contain a null field.
zz Result.End Result End U/D This is the separator that ends a
data packet. BCI prefers to
receive it, but it is not a required
field.

Note: When autolinking, test results from an instrument automatically go to a

corresponding patient demographic record, if the pi and ci fields are
present. For VITEK® and VITEK® 2, a culture must also have preliminary
status. Exams downloaded through BCI automatically receive a preliminary
exam status.

514724-1EN1 Field Type Definitions A-9

Bidirectional Computer Interface Specification for VITEK® Systems

514724-1EN1 Field Type Definitions A-10

 B ASCII Characters and Other Values

Table B-1: ASCII Characters and Other Values

Hex ASCII Hex Octal

Octal Value ASCII Character
Value Character Value Value
00 000 NUL 1A 032 SUB
01 001 SOH 1B 033 ESC
02 002 STX 1C 034 FS
03 003 ETX 1D 035 GS
04 004 EOT 1E 036 RS
05 005 ENQ 1F 037 US
06 006 ACK 20 040 SPACE
07 007 BEL 21 041 !
08 010 BS 22 042 “
09 011 HT 23 043 #
0A 012 LF 24 044 $
0B 013 VT 25 045 %
0C 014 FF 26 046 &
0D 015 CR 27 047 ‘
0E 016 SO 28 050 (
0F 017 SI 29 051 )
10 020 DLE 2A 052 *
11 021 DC1 2B 053 +
12 022 DC2 2C 054 ‘
13 023 DC3 2D 055 -
14 024 DC4 2E 056 .
15 025 NAK 2F 057 /
16 026 SYN 30 060 0
17 027 ETB 31 061 1
18 030 CAN 32 062 2
19 031 EM 33 063 3
34 064 4 50 120 P
35 065 5 51 121 Q
36 066 6 52 122 R
37 067 7 53 123 S
38 070 8 54 124 T
39 071 9 55 125 U
3A 072 : 56 126 V
3B 073 ; 57 127 W

514724-1EN1 ASCII Characters and Other Values B-1

Bidirectional Computer Interface Specification for VITEK® Systems

Table B-1: ASCII Characters and Other Values (Continued)

Hex ASCII Hex Octal

Octal Value ASCII Character
Value Character Value Value
3C 074 < 58 130 X
3D 075 = 59 131 Y
3E 076 > 5A 132 Z
3F 077 ? 5B 133 [
40 100 @ 5C 134 \
41 101 A 5D 135 ]
42 102 B 5E 136 ^
43 103 C 5F 137 _
44 104 D 60 140
45 105 E 61 141 a
46 106 F 62 142 b
47 107 G 63 143 c
48 110 H 64 144 d
49 111 I 65 145 e
4A 112 J 66 146 f
4B 113 K 67 147 g
4C 114 L 68 150 h
4D 115 M 69 151 i
4E 116 N 6A 152 j
4F 117 O 6B 153 k
6C 154 l 76 166 v
6D 155 m 77 167 w
6E 156 n 78 170 x
6F 157 o 79 171 y
70 160 p 7A 172 z
71 161 q 7B 173 {
72 162 r 7C 174 |
73 163 s 7D 175 }
74 164 t 7E 176 ~
75 165 u 7F 177 DEL

514724-1EN1 ASCII Characters and Other Values B-2

 C Recommended Host Features

For BCI to upload and download data efficiently, bioMérieux recommends that the host
computer support the following features.

Table C-1: Recommended Download Features

Feature Condition or Explanation

XON/XOFF XON/XOFF is a required protocol. This pacing discipline controls data
flow using the special control characters 0x11 (XON) and 0x13 (XOFF).
Test Types The host should only send patient, specimen, and exam demographics
for bioMérieux related tests. Since all demographics sent are stored in
the bioLIAISON® database, non-bioMérieux demographics will waste
database space.
Automatic To make full use of the BCI, the host should be able to transmit patient
Transmission of Patient demographics automatically.
Demographics
Manual Transmission The host should support a method of manually transmitting patient
of Patient demographics. This will allow the user to request the download of
Demographics demographics for a specific patient or group of patients.
Demographics Updates The host may update patient demographics by simply retransmitting the
appropriate pieces of information. There is a user-configurable option
that determines if updates are allowed. (See the BCI Utilities section.) If
this option is enabled, the bioMérieux computer considers any
retransmissions of a patient’s demographics as an update.
Field Terminator Due to a conflict with the default time and date separator characters ( :
Characters and / ), bioMérieux recommends that the host not use these as field
terminators.

Table C-2: Recommended Upload Features

Feature Condition or Explanation

Upload of Patient BCI’s upload program is designed to only upload essential information
Demographics to an LIS computer. It is the responsibility of the LIS/HIS vendors to
determine which demographics are needed by the host.
Updates bioMérieux recommends that retransmissions to a host be treated as
updates.

514724-1EN1 Recommended Host Features C-1

Bidirectional Computer Interface Specification for VITEK® Systems

514724-1EN1 Recommended Host Features C-2

 D Antimicrobial MICs and Categories

The following tables list MIC values and category calls a bioMérieux computer can report for
the a1–a4 fields. For example, if the bioMérieux computer were to report ampicillin with an
MIC <16 and a category of S, this part of the upload message would be:

|a1am|a2Ampicillin|a3<=16|a4S|

Table D-1: Sample MIC and Category Designations

Doubling Category
Dilution (a3) (a4)
< 16 S
32 I
64 R
128 R
256 R
> 512 R

There are 14 exceptions to the previous list of antimicrobial susceptibility codes.

Table D-2: Possible Field Entries

Possible a4 Field
Possible a3 Field
a1 a2 (Category)
(MIC) Entries
Entries
oxid oxidase Pos / Neg +/–
Bla beta-lactamase Pos / Neg +/–
cata catalase Pos / Neg +/–
gm500 Gentamicin 500 SYN-S / SYN-R blank
st2000 Streptomycin 2000 SYN-S / SYN-R blank
esbl ESBL Pos / Neg +/–
hlg Gentamicin High Level (synergy) SYN-S / SYN-R S or R
hls Streptomycin High Level (synergy) SYN-S / SYN-R S or R
hlk Kanamycin High Level (synergy) SYN-S / SYN-R S or R
oxs Oxacillin Screen blank S or R
oxsf Cefoxitin Screen Pos / Neg +/–
icr Inducible Clindamycin Resistance Pos / Neg +/–
vas VRSA screen Pos / Neg +/–
Deduced drugs blank S, I, R

Note: See also Miscellaneous Tests in Chapter 5 of this specification.

514724-1EN1 Antimicrobial MICs and Categories D-1

Bidirectional Computer Interface Specification for VITEK® Systems

514724-1EN1 Antimicrobial MICs and Categories D-2

 E Bionumber Descriptions

VITEK® and VITEK® 2 Systems identification tests produce individual biochemical test results
for each well in the card. These results can be either positive or negative. Biochemical results
are then put into groups of three so the analysis programs can calculate a single octal number.
This example shows how a bionumber (o3 field) is created for a GNI card.

Note: This is only an example and not meant to be a biopattern for any particular
organism. See the package insert or technical bulletin for biochemicals used
with other VITEK® or VITEK® 2 Systems ID cards.

Table E-1: Card Well and Biochemical Result Values

Well Biochemical Well Biochemical

Result Result
Position Code Name Position Code Name
1 DP3 – 17 SOR –
2 OFG – 18 SUC +
3 PC – 19 INO +
4 ACE – 20 ADO +
5 ESC – 21 COU –
6 PLI + 22 H2S +
7 URE – 23 ONP +
8 CIT + 24 RHA +
9 MAL – 25 ARA –
10 TDA – 26 GLU –
11 PXB + 27 ARG –
12 LAC + 28 LYS –
13 MLT + 29 ORN –
14 MAN – 30 OXI +
15 XYL – 31 TLA +
16 RAF +

Table E-2: Result Patterns and Bionumber Calculation

Calculated
Well Position Results
Bionumber
1–3 ––– 0
000
4–6 ––+ 4
004
7–9 –+– 2
020
10–12 –++ 6
024

514724-1EN1 Bionumber Descriptions E-1

Bidirectional Computer Interface Specification for VITEK® Systems

Table E-2: Result Patterns and Bionumber Calculation (Continued)

Calculated
Well Position Results
Bionumber
13–15 +–– 1
100
16–18 +–+ 5
104
19–21 ++– 3
120
22–24 +++ 7
124
25–27 ––– 0
000
28–30 ––+ 4
004
31 + 1
1

Resulting biopattern: 04261537041

514724-1EN1 Bionumber Descriptions E-2

 F Reference Tables

F.1 Test Group Table

Note: This section is only applicable to VITEK® and VITEK® 2.

This table lists current test group codes (t2 field) and their descriptions.

Table F-1: Test Group Codes and Descriptions

Test Group Code Test Description

ID Identification
SU Susceptibility
KB Kirby-Bauer
SC Screen
SM Smear
BC Blood Culture
NA No Test Group Available

F.2 Instrument Code Table

Table F-2: Instrument Codes and Descriptions

Instrument Code Instrument Description

AM VITEK®
AT ATB
NA No instrument available
OT BacT/ALERT®
UD User defined
VT VITAL
V2 VITEK® 2 and VITEK® 2 Systems

F.3 Blood Test Download Result Fields

Note: This section is only applicable to VITEK® and VITEK® 2.

Table F-3: Blood Test Download Result Fields

Field Data Max.

Description
Type Class Length
t1 T 2 Isolate Number (Repeatable Only for Blood
Tests)
o1 T 6/15 Final Organism Code (Repeatable)

514724-1EN1 Reference Tables F-1

Bidirectional Computer Interface Specification for VITEK® Systems

Table F-3: Blood Test Download Result Fields (Continued)

Field Data Max.

Description
Type Class Length
tb T 10 Bottle Barcode
rd T Date Result Date
ru T Time Result Time
re T 8 Elapsed Hours
rc T 2 Instrument Result Code
rj T 2 Blood Test Final Result Code

514724-1EN1 Reference Tables F-2

 Change Summary

This section contains a summary of significant changes made to each released revision of this
document.

Part
CR # Originated/Revised By:
Number

514724-1EN1 SC11-0743 Tamy Brooks

Description of Change:

Overview of BCI - N/A

bioMérieux Communications Protocol - Table 2-1, Record and Character Descriptions - Corrected
the cross reference to Checksum Field Format on page 2-10 in the GS (CR/LF) column. Revise
information regarding communications and application level messages are limited to 1,920 characters
in Example 3: Multiple Communications Level Messages in a Session and Example 4: Multiple
Application Messages in a Session.

Download Specifics - N/A

Upload Specifics - Table 4-5, Upload Test Result Field Types - change the max length of card lot
number from 9 to 10 for tg field.

BCI Utilities (VITEK® & VITEK® 2 Only)

Field Type Definitions - Table A-1, Field Type Definitions - Corrected Field Code pl for
Patient.Location User Code and Name.

ASCII Characters and Other Values - N/A

Recommended Host Features - N/A

Antimicrobial MICs and Categories - N/A

Bionumber Descriptions - N/A

Reference Tables - N/A

514724-1EN1 Change Summary 1

Bidirectional Computer Interface Specification for VITEK® Systems

514724-1EN1 Change Summary 2

Recommended Changes

You can improve this manual by recommending improvements using the Recommended
Changes to Service Documentation Form. Fill it out as shown on the sample below and send it
to the e-mail, fax number, or address shown in the table below.

Recommended Changes to Service Documentation Forms can be accessed by double-

clicking the paperclip next to the sample form to open the form as a Microsoft® Word
document. A blank form is also included in this chapter for FSEs that would rather print the
form without using Microsoft® Word and complete it manually.

Note: The Recommended Changes to Service Documentation Forms may only be used for service
documentation for the VITEK® 2, VITEK® 2 Compact, BacT/ALERT® 3D, OBSERVA®, and
PREVI® Isola product lines.

Fax Number E-mail Address Mail Address

314-731-8689 [email protected] bioMérieux
Attn: PL&D RCSD Attn: PL&D RCSD
595 Anglum Rd
Hazelwood, MO 63042

Recommended Changes to Service DATE: 12JUN09

Documentation
TO:
Fax No. 123-456-7899
FROM:
John Doe Recommended
55 bioMérieux Way
Anytown, CA, 123456 USA
Changes to Service
MANUAL NUMBER
510726-4EN1
REVISION DATE
07/2006
MANUAL TITLE
VITEK® 2 and VITEK® 2 XL Integrated System
Documentation
Service Manual Form
CHAPTER SECTION PAGE FIGURE TABLE RECOMMENDED CHANGES AND REASON
NO. NO. NO. NO. NO. (Provide exact wording of changes, if possible.)
2 2.3.2 2-4 2-2 The black plastic card part number is listed
incorrectly. It should be XXXXX-XX.

SAMPLE

NAME AND JOB TITLE TELEPHONE NO. SIGNATURE

John Doe
John Doe, Field Service Engineer 123-456-7890

FOR PL&D USE ONLY

Date Received TTP # Entered By Date Entered

03/2010
Recommended Changes to Service DATE:
Documentation
TO: FROM:

MANUAL NUMBER REVISION DATE MANUAL TITLE

CHAPTER SECTION PAGE FIGURE TABLE RECOMMENDED CHANGES AND REASON

NO. NO. NO. NO. NO. (Provide exact wording of changes, if possible.)

NAME AND JOB TITLE TELEPHONE NO. SIGNATURE

FOR PL&D USE ONLY

Date Received TTP # Entered By Date Entered

03/2010