®

MYLA 4.9 - BCI

Connectivity Service
Manual
LIS Interface Driver
Development Guide
161150-1283 - D - en - 2021-02 – 161150-1671

EN
Intellectual Property

BIOMERIEUX, the BIOMERIEUX logo and MYLA are used, pending and/or registered
trademarks belonging to bioMérieux, or one of its subsidiaries, or one of its companies.

Any other name or trademark is the property of its respective owner.

The MYLA character is used, pending and/or registered Design belonging to

bioMérieux, or one of its subsidiaries, or one of its companies.

© 2021 bioMérieux SA

bioMérieux SA 673 620 399 RCS Lyon
Table of Contents

Introduction.................................................................................................................. 1-1
Intended Use and Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Warning and Safety Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Statement Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Communication Protocols .......................................................................................... 2-1

Communication Protocols/Message Format Combinations . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Message Format/Functional Scope Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
MYLA®–LIS Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Connection without MYLA® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Connection Through MYLA® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Connection to One LIS Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Connection to Several LIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Connection to Several LIS and a "Data Management" System . . . . . . . . . . . . . . . . . . . . . . . 2-4

Transport of FTP Messages........................................................................................ 3-1

Principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Managing FTP Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Opening a Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Configuring Connections for Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Shutting Down a Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Configuring FTP Over SSL (FTPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Disable Secure FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Managing Analysis Requests (LIS to BCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Description of the "STOR" Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Examples of How the "STOR" Command is Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Algorithm for Sending Analysis Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Managing Results (BCI to LIS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Description of the "RETR" Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Examples of How the "RETR" Command is Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Algorithm for Receipt of Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

XML Files Usage Conventions .................................................................................. 4-1

Principle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Rule Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Analysis Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Analysis Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

FTP Configuration - Additional Information .............................................................. 5-1

List of FTP Commands Supported by the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

161150-1283 - D i MYLA® V4.9

 Table of Contents

FTP Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Conventions to Follow in Writing Pseudocode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Introduction to XML-Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Declaration of Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Occurrence Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
XML-Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Protocol for Legacy bioMerieux Format Messages.................................................. 6-1

Principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
bioMérieux Literal Protocol/"Download" Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
bioMérieux Literal (Alternate) Protocol/"Download" Mode . . . . . . . . . . . . . . . . . . . . . . . 6-3
bioMérieux Literal Protocol/"Upload" Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
bioMérieux Literal (Alternate) Protocol/"Upload" Mode . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Frame Message Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Carriage Return/Line Feed Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Checksum Field Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Configuration of the Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

XML Message Format .................................................................................................. 7-1

Message Structure and Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
LIS Messages are Sent by a LIS to MYLA® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
AI Messages are Sent From MYLA® to One or More LIS . . . . . . . . . . . . . . . . . . . . . . . 7-2
Field List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Additional Information: XML Encoding of Special Characters . . . . . . . . . . . . . . . . . . . . . . . 7-2
Specificities of XML Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

BMX Message Format ................................................................................................. 8-1

Message Structure and Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
LIS Messages are Sent by a LIS to MYLA® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
AI Messages are Sent from MYLA® to One or More LIS . . . . . . . . . . . . . . . . . . . . . . . 8-2
Field List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Field Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Date/Time Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

CLSI LIS2-A2 Message Format................................................................................... 9-1

Message Structure and Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
LIS Messages are sent by a LIS to MYLA®. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
AI Messages are Sent from MYLA® to the LIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Field List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Deviation from the Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

161150-1283 - D ii MYLA® V4.9

 Table of Contents

HL7 Message Format................................................................................................. 10-1

Transport and Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Laboratory Analytical Workflow Actors and Transactions . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Supported LAW Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
AWOS Broadcast Use Case Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
AWOS Created On Analyzer Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
AWOS Broadcast [LAB 28] Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
AWOS Broadcast [LAB 28] Interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Rejection rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

Additional Information .............................................................................................. 11-1

Code Name Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Erroneous Fields Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Number of Results per Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Decimal Separator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Time Zone/Date Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Legacy Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Differences with VITEK® Legacy LIS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Differences with BACT/ALERT® Legacy LIS Messages . . . . . . . . . . . . . . . . . . . . . . . 11-3
Differences between MYLA® V3 Messages and MYLA® V4.0 Messages . . . . . . . . . 11-3
Differences between MYLA® V4.0 Messages and MYLA® V4.1 Messages. . . . . . . . 11-4
Differences between MYLA® V4.1 Messages and MYLA® V4.3 Messages. . . . . . . . 11-4
Differences between MYLA® V4.3 Messages and MYLA® V4.4 Messages. . . . . . . . 11-4
Differences between MYLA® V4.4 Messages and MYLA® V4.5 Messages. . . . . . . . 11-5
Differences between MYLA® V4.5 Messages and MYLA® V4.6 Messages. . . . . . . . 11-5
Differences between MYLA® V4.6 Messages and MYLA® V4.7 Messages. . . . . . . . 11-6
Differences between MYLA® V4.7 Messages and MYLA® V4.7.1 Messages . . . . . . 11-7
"VITEK® MS 3.0 compatibility" user mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Differences between MYLA® V4.7.1 Messages and MYLA® V4.8 Messages . . . . . . 11-8
Differences between MYLA® V4.8 Messages and MYLA® V4.9 Messages. . . . . . . . 11-8
Patient Duplication Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Patient “activity” time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Rules for detecting a new patient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Rules for updating patient fields (from LIS request) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Specimen Duplication Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Specimen “activity” time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Rules for detecting a new specimen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Rules for updating specimen fields (from LIS request). . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Test Order Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Rules for detecting new test orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Dispatching Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
LIS Result Sending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
Typical Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13

161150-1283 - D iii MYLA® V4.9

 Table of Contents

Blood Culture Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13

Generalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
Typical Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14
Blood Culture Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17
ID/AST Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18
Generalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18
Typical Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19
Workflow with Offline Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19
Workflow with Offline Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19
Other Results sent by the LIS to MYLA® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-20
ID/AST Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21
MYLA® Messages Identification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-23

MESSAGE SAMPLE ................................................................................................... 12-1

Basic Request with Test Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
BMX format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
CLSI LIS2-A2 – Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Basic Request with Specimen Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
CLSI LIS2-A2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Non Basic Request (patient and specimen info) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
CLSI LIS2-A2 – Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Request Allowing Optimum Use of Statistical Reporting Module . . . . . . . . . . . . . . . . . . . . 12-5
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
CLSI LIS2-A2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Message from LIS with an identification result only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
CLSI LIS2-A2 - Not Applicable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Message from LIS with a (presumptive) identification result only. . . . . . . . . . . . . . . . . . . 12-10
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
CLSI LIS2-A2 - Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11

161150-1283 - D iv MYLA® V4.9

 Table of Contents

HL7 - Not Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11

Message from LIS with an AST Result only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
CLSI LIS2-A2 - Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Full request with offline identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-15
Full request using specimen type dispatching with identification offline result. . . . . . . . . . 12-15
Full request using test group code dispatching with identification offline test result. . . . . . 12-16
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
Full request with an offline identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
CLSI LIS2-A2 – Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18
Request Containing Clinical information for MYLA® AST Filter feature . . . . . . . . . . . . . . 12-18
Request Containing a Blood Culture Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-19
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21
CLSI LIS2-A2 – Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21
Request Containing a Gram Staining Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
Format Only Supported by BCI Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
New Format Only Supported by BCI Connect from MYLA® V4.7 . . . . . . . . . . . . . . . . . . . 12-23
Codes Supported by MYLA for Gram Staining Results . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Legacy Format Supported by BCI Link and BCI Connect . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
New Format Only Supported by BCI Connect from MYLA® V4.7 . . . . . . . . . . . . . . . . . . . 12-24
CLSI LIS2-A2 – Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-25
Request with optional DisposableIdentifier and optional expected duration . . . . . . . . . . 12-25
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27
CLSI LIS2-A2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27
Request Containing an Offline Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-28
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-28
Format Supported by BCI Link and BCI Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-28
New Format Only Supported by BCI Connect from MYLA® V4.7 . . . . . . . . . . . . . . . . . . . 12-30
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31
Format Supported by BCI Link and BCI Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31
New Format Only Supported by BCI Connect from MYLA® V4.7 . . . . . . . . . . . . . . . . . . . 12-31
CLSI LIS2-A2 – Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31

161150-1283 - D v MYLA® V4.9

 Table of Contents

HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31
Result for Blood Culture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-32
One Bottle Result per Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-33
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-33
Request Cancelation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-35
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-35
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-36
CLSI LIS2-A2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-36
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-36
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-36
CLSI LIS2-A2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-37
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-38
Several Bottle Results in the Same Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-39
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-39
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-41
CLSI LIS2-A2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-42
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-42
Result for Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-46
Standard Identification Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-46
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-46
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-47
CLSI LIS2-A2 – Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-47
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-48
Specificities of VITEK® MS Results Regarding “Standard” Identification Results . . . 12-48
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-49
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-50
CLSI LIS2-A2 – Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-50
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-51
Manual Identification Specificities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-51
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-51
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-52
CLSI_LIS2_A2 - not applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-52
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-53
Result for Antibiogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-53
Standard Antibiogram Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-53
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-53
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-59
CLSI LIS2-A2 – Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-59
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-59
Antibiogram with an Offline Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-62
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-63
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-69
CLSI LIS2-A2 – Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-69
HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-69
Manual Antibiogram Specificities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-71
XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-72
BMX Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-73
CLSI LIS2-A2 – Not Applicable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-73

161150-1283 - D vi MYLA® V4.9

 Table of Contents

HL7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-74
Result for Gram Staining . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-74

Appendix - Message Mapping Table ..........................................................................A-1

Appendix - Glossary....................................................................................................B-1
Abbreviations and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1
Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Revision History

161150-1283 - D vii MYLA® V4.9

1 Introduction

Intended Use and Users

IMPORTANT: This manual is particularly intended for the computer service companies which are
responsible for developing the interface between the bioMérieux analysis systems and
the laboratory information systems.

IMPORTANT: This documentation only applies to analysis systems which integrate the bioMérieux
MYLA® product.

This manual describes the interface between the MYLA® system and a LIS. It includes the
structures and data types of the BCI messages exchanged between the LIS and the MYLA®
system.

IMPORTANT: We recommend using HL7 for new LIS drivers development.

Warning and Safety Messages

The user documentation uses several types of statements to alert you to important
information. Important information is labeled in text and identified using symbols.

Statement Types
The statement types are Warning, Caution, Important, and Note. The following examples
define each statement type. The general caution symbol is used in these examples, but other
symbols (see A Note statement supplies additional information about a topic. on page 1-1)
may be used instead.

The warning messages in this document mainly refer to:

WARNING

A Warning statement alerts the user to the possibility of injury, death, or

other serious adverse reactions associated with the use or misuse of the
device.

CAUTION: A Caution statement alerts the user to the possibility of a problem with
the device associated with its use or misuse. Such problems include device
malfunction, device failure, damage to the device, or damage to other property.
Where applicable, a Caution statement may include a precaution that should be
taken to avoid the hazard.

IMPORTANT: An Important statement relates to content presented in the user documentation. It is

used to reinforce the user’s understanding of selected information.

Note: A Note statement supplies additional information about a topic.

161150-1283 - D 1-1 MYLA® V4.9

2 Communication Protocols

Four different communication protocols can be used for the communication between MYLA®
and the LIS:

• bMx “BCI RS232” Proprietary Protocol

This protocol uses bioMerieux legacy format currently used by systems like VITEK® or
VIDAS®.

For more details on this protocol, please see Protocol for Legacy bioMerieux Format
Messages on page 6-1 or refer to the Bidirectional Computer Interface Specification for
VITEK® Systems document section “bioMérieux Communication Protocol”.

• FTP Protocol
This is a network protocol based on the standard FTP protocol with a message format based
on XML. Only folder naming conventions are specific to bioMérieux.
For more details on this protocol, please refer to the Transport of FTP Messages on page 3-1.

• CLSI LIS01-A2 (former ASTM E1381) Standard

This protocol can be Serial or TCP/IP based (for more details, refer to the CLSI LIS01-A2
standard for Electronic Exchanges of Data). The MYLA® interface implements the CLSI
standards.

The transport layer does not interpret the message. This means that for CLSI LIS2-A2
messages, if there is a transmission failure in the middle of a message, the whole message is
resent (from the Header to the Terminator record).
This protocol is limited to blood culture request and result. It is not usable for ID/AST analyses.

• HL7, IHE LAW

Communication Protocols/Message Format Combinations

For technical reasons and to ensure compatibility with the legacy connection, various possible
combinations for the communication between MYLA® and the LIS are given below.

Message format
BMX XML LIS2-A2 HL7
Protocol / Transport
CLSI LIS01-A2 Protocol, Serial data exchange    
CLSI LIS01-A2 Protocol, TCP/IP data exchange    
bioMérieux (BCI RS232 Compatibility mode) protocol Serial    
data exchange
bioMérieux (BCI RS232 Compatibility mode) protocol TCP/    
IP data exchange
FTP(S) protocol / FTP    
Shared Folder (Supported but not recommended for new    
connection) / Shared Folder
HL7 / MLPP    

161150-1283 - D 2-1 MYLA® V4.9

Message Format/Functional Scope Supported Communication Protocols

Message Format/Functional Scope Supported

The message types and their corresponding functional scope are given below.

Message format
BMX XML LIS2-A2 HL7
Protocol
Patient    
Specimen    
Order    
Offline result    
Blood culture result    
Identification result    
Antibiogram result    
Gram staining result    
"Simple" result    

MYLA®–LIS Connection

This section describes two possibilities for a connection to the LIS:

- connection without MYLA® (not documented in this manual)

- connection through MYLA®

Note: The following configuration diagrams only focus on the main differences between the two
deployments from an LIS point of view. In this respect, all the components involved may not be
shown. Refer to the MYLA® documentation for a complete picture of the MYLA® deployment.

Connection without MYLA®

Figure 2-1: Example of the Protocols/Messages Managed by the LIS

The LIS has to manage several communication protocols and message formats.

Connection Through MYLA®

Depending on the configuration of the target deployment, connection to one or more LIS is
possible.

161150-1283 - D 2-2 MYLA® V4.9

MYLA®–LIS Connection Communication Protocols

Connection to One LIS Only

The MYLA® server manages the communication with the bioMérieux microbiology systems.
This communication is network-based: the bioMérieux microbiology systems and the MYLA®
server must be on a network.

The LIS only manages the link with MYLA®. Requests and results will be sent through the
same link, i.e. the ID, AST and blood culture requests and results.

Figure 2-2: Example of Target Deployment Using a Single LIS

Connection to Several LIS

The following example shows a two-LIS connection (e.g. LIS A and LIS B).

Each LIS can send requests and receive results according to the following communication
schemes:

- LIS A sends a request for specimen “Spec A123””

- LIS B sends a request for specimen “Spec B456"

- analysis systems perform an analysis for each specimen

- MYLA® sends all the results for "Spec A123” to LIS A only

- MYLA® sends all the results for "Spec B456" to LIS B only

Note: If request has not been sent by the LIS (orphan), the result is sent to both.

Note: It is very important to use different ranges of number for each LIS to prevent specimen number
collision in MYLA®.

Note: Results received by MYLA® before request are sent to all LIS connected. For blood culture
"negative to date" this behavior is configurable in MYLA®.

161150-1283 - D 2-3 MYLA® V4.9

MYLA®–LIS Connection Communication Protocols

Figure 2-3: Example of Target Deployment Using Several LIS

Note: If a specimen is analyzed on the system without any LIS requests (emergency for example)
and no LIS request is sent later, the associated results will be sent to all the connected LIS.

Connection to Several LIS and a "Data Management" System

The following example shows a connection to several LIS and a "Data Management" System.

The “Data Management” System (example: Observa) receives the requests and results for all
the specimens. The “Data Management” System communication does not allow bidirectional
communication: it does not send requests or results to MYLA®.

The configuration of a "Data Management" System is done in the MYLA® user interface.

Figure 2-4: Example of Target Deployment Using a "Data Management" System

Note: BACT/ALERT® includes 3D and VIRTUO™.

IMPORTANT: For more information regarding the availability of the bioMérieux “Data Management”
System and MYLA® refer to the MYLA® documentation or contact your bioMérieux
representative.

161150-1283 - D 2-4 MYLA® V4.9

3 Transport of FTP Messages

Principle

Messages are transported by TCP/IP using the standard FTP protocol. From a strictly
"communications" point of view, the BCI Link/BCI Connect software is an FTP server and the
LIS is an FTP client. In other words, the interface driver should integrate an FTP client who is
capable of downloading files containing the analysis requests and uploading files containing
the results.

The FTP protocol requires two connections for communication, a "control connection" and a
"data connection". The control connection is used to exchange FTP commands and the data
connection to transfer data.

The transmission mode is a "Stream" mode, i.e. the file is simply transferred as a series of
bytes. There are no limitations for the data representation.

The “file type” structure is used. The EOF (End Of File) sequence is implicitly marked by the
closing of the connection. All the transmitted bytes are therefore data bytes.

There is no existing mechanism to detect lost or erroneous bits for a transferred file; this
type of error is managed at TCP level. The FTP server does not implement a recovery
procedure following an error. If transfer is interrupted, the client must resend the complete
file.

IMPORTANT: The aim of this chapter is to define the specificities of the FTP protocol as part of the
LIS – BCI interface. It does not provide information on the FTP protocol.
For further details on the FTP protocols, refer to the RFC0959 standard.

Managing FTP Sessions

Opening a Session
The FTP Client connects to the FTP BCI server using an identifier and a password which are
recognized (i.e. defined as an active FTP account: refer to the BCI Link/BCI Connect User
Manual, for more detailed information).

A session can be opened by sending the command: FTP <BCI IP Address>

Connecting to the < FTP server>

< 220 Service ready for new user
1. USER <user name>
< 331 User name okay, need password
2. PASS <user password>
< 230 User logged in, proceed

Note: Only valid FTP accounts are authorized to connect to BCI Link/BCI Connect, anonymous FTP
accounts do not exist.

161150-1283 - D 3-1 MYLA® V4.9

Managing FTP Sessions Transport of FTP Messages

The following table describes the command sequence that an FTP client should use to set up
a new FTP session.

# Command Setting Return code

1 TCP/IP • IP address or computer name • 220: Connection established

Connection • Port number (21 by default) • 221: Connection error
• 421: Connection refused – Too many
sessions open
(maximum: 10 sessions) or unexpected
error
2 USER • FTP account identifier • 331: Identifier ok, need password
• 221 or 421 if unexpected error
3 PASS • FTP account password • 230: Session created
• 530: Incorrect identifier or password
• 221 or 421 if unexpected error

Configuring Connections for Data Transfer

Type of transfer:

To optimize transfer time and avoid encoding problems, it is preferable to use binary transfers
rather than ASCII transfers by sending the following command to the FTP server after
connection: TYPE I.

If this is successful, the return code is 200. If an error occurs, the return code is 501. This
configuration is valid for the duration of the session or until the command TYPE A is sent to
return to ASCII mode.

Transfer mode (active/passive):

The BCI allows connections in active or passive mode for the transfer of files.

In active mode, opening of the data connection is initiated by the BCI Link/BCI Connect
server using the parameters of the PORT command previously transmitted by the client.

This command has the following parameters: h1, h2, h3, h4, p1, p2. The first 4 parameters
represent the internet address and the last 2 represent the port for a byte in ASCII
representation (refer to standard RFC0959).

Note: The server does not implement a default port for the data connection. The client has to send
the PORT command beforehand.

In passive mode, opening of the data connection is initiated by the client for data transfer. To
initiate transfer in passive mode, the FTP client must send the following command to the FTP
server: PASV. The server will then return the IP address and the port number on which the
client should establish the connection for data transfer.

161150-1283 - D 3-2 MYLA® V4.9

Managing FTP Sessions Transport of FTP Messages

Note: By default, the server runs in active mode which may cause problems with systems which are
behind firewalls. Only use passive mode for configurations with a firewall.

The PASV command is only valid for the coming data transfer session; this is why it must
systematically be sent before each data transfer.

Shutting Down a Session

The FTP server does not manage session "time outs". In theory, an FTP session can remain
open indefinitely. In practice, it is recommended to open a session each time an analysis
request is downloaded to the server (refer to the following section about Managing Analysis
Requests (LIS to BCI) on page 3-4), and to have a "permanent" session for downloading
results (refer to the section about Managing Results (BCI to LIS) on page 3-7).

A session can be shut down by sending the QUIT command to the FTP server.

Note: Shutting down a session enables only the control connection to be shut down; transfer
connection shutdown is initiated by the server following data transfer.

Configuring FTP Over SSL (FTPS)

The following procedure is applicable for BCI Link only.

If MYLA® is connected to the LIS through BCI Connect, please refer to the BCI Connect
Service Manual for MYLA®.

Enable Secure FTP:

• Set the ftps.active property to “true” in the

{BIOMERIEUX_PROGRAM}\BCILink\lib_server\properties\bcinet.properties file.

Configure Explicit or Implicit FTP mode:

The Implicit mode is activated by default.

• Set the ftps.implicit-ssl property to “false” in the

BCILink\lib_server\properties\bcinet.properties file to enable the Explicit mode.

161150-1283 - D 3-3 MYLA® V4.9

Managing Analysis Requests (LIS to BCI) Transport of FTP Messages

Disable Secure FTP

• Set the ftps.active property to “false” in the
BCILink\lib_server\properties\bcinet.properties file.

• Restart the “bciNetServer” Windows service to apply configuration changes.

Managing Analysis Requests (LIS to BCI)

Description of the "STOR" Command

The analysis requests must be downloaded in the "\download" directory on the FTP server.
Any attempt to write in a directory other than the "download" directory will be refused by the
server.

To download the contents of a file to the server’s current directory, use the command FTP:
STOR <Name of file>. After the "STOR" command has been issued, the FTP server may
send one of the following return codes:

Code Message Explanation

550 Requested action not This error occurs when you try to send a file which has the same name as a
directory on the server, e.g. STOR/download.
taken, not a file
550 Requested action not This error occurs when you try to download a file to a directory other than the
"download" directory, e.g. STOR/upload/myFile
taken, no access
451 Requested action BCI Link: This error occurs when you send a file without respecting the rules
for naming it as defined in BCI. The format for naming a file should be < FTP
aborted: Incorrect
account>_yymmdd_hhmmss_<sequence>.xml. The FTP account is the
format, waited for: name of the account validated in the BCI configuration and the sequence is
< FTP account> an integer between 0 and 99 which is used to identify several files sent in the
_yymmdd_hhmmss_ same second. For example, the LIS sends 3 separate files on December 31
<sequence>.xml file 2004 at 12h30 and 20 seconds, the files should be named as follows:
• <account FTP>_041231_123020_0.xml
name and received:
• <account FTP>_041231_123020_1.xml
<myFile>
• <account FTP>_041231_123020_2.xml
Since the FTP server does not manage file uniqueness, naming them in this
way define for BCI Link avoid involuntary overwriting of files in the Download
folder.

BCI Connect: This error can't occur All.xml files are accepted. All other files
are ignored without error. Nevertheless, it is recommended to follow the rules
set for BCI Link.

161150-1283 - D 3-4 MYLA® V4.9

Managing Analysis Requests (LIS to BCI) Transport of FTP Messages

Code Message Explanation

421 Service not This error occurs in cases where:

• Connection for data transfer failed (in active or passive mode). Check that
available, closing
the parameters defined during creation of the connection (internet address
control connection and port number) are correct.
• Connection for data transfer is suddenly cut off (power cut, connection
shut down by the client, etc.).
150 Opening data This message is sent to the client before transfer begins. It indicates that
connection has been correctly established and that the transfer mode will be
connection -
binary or ASCII.
transfer mode:
<Binary mode or
Ascii mode>:
226 Transfer complete : The server sends this code to indicate that transfer is complete and that the
connection will soon be shut down.

Examples of How the "STOR" Command is Used

Example 1:

The FTP command sequence below enables the following actions to occur in succession:

· Establish an FTP session in active mode.

· Send an analysis request, following the BCI rules for naming files.
· Shut down the session.

Connecting to the < FTP server>

< 220 Service ready for new user
1. USER <user name>
< 331 User name okay, need password
2. PASS <user password>
< 230 User logged in, proceed

3. CWD /download
< 250 Requested file action okay, completed
4. TYPE I
< 200 Command okay
5. PORT h1,h2,h3,h4,p1,p2
< 200 Command okay
6. STOR labo_030909_153020_0.xml
< 150 Opening data connection - transfer mode: Binary mode
< 226 Transfer complete
7. QUIT
< 221 Service closing control connection

161150-1283 - D 3-5 MYLA® V4.9

Managing Analysis Requests (LIS to BCI) Transport of FTP Messages

Example 2:

The FTP command sequence below enables the following actions to occur in succession:

· Establish an FTP session in passive mode.

· Send an analysis request, following the BCI rules for naming files, with the complete path.
· Shut down the session.

Connecting to the < FTP server>

< 220 Service ready for new user
USER <user name>
< 331 User name okay, need password
PASS <user password>
< 230 User logged in, proceed

TYPE I
< 200 Command okay
PASV
< 227 Entering Passive Mode (h1,h2,h3,h4,p1,p2)
STOR /download/labo_030909_153020_0.xml
< 150 Opening data connection - transfer mode: Binary
mode
< 226 Transfer complete
QUIT
< 221 Service closing control connection

Algorithm for Sending Analysis Requests

The following algorithm describes the main steps for managing transfer of analysis requests
coming from the LIS. This algorithm is written in pseudocode, i.e. the algorithm gives a
description of the tasks to be performed but without language syntax. The conventions for
writing in pseudocode are described in the section Conventions to Follow in Writing
Pseudocode on page 5-4.

The principle of this algorithm consists in finding, in a given reference system, all the analysis
requests to be transferred. If new requests exist, an FTP session is initiated and the files are
sent following the rules for naming files. This algorithm does not take into account the possible
errors that the server may return.

161150-1283 - D 3-6 MYLA® V4.9

Managing Results (BCI to LIS) Transport of FTP Messages

// Finding the analysis requests in a table

File[] fileList = getWorkListToSend() ;
IF fileList not empty THEN {
// Opening an FTP connection
openFTPConnection(ftpHostname, portNumber);
// Opening a new session
startFTPSession(login, pwd);
// Transfer: binary mode
setBinaryMode();
// finding current date and time
DateTime dateAndTime = getSystemDateTime();
// Managing sequence number using a counter
Integer counter = 0;
// sending files
FOR i=0 to fileList.length() {
// creating a file name to send to the FTP server
String fileName = ftpAccountName + “_” + dateAndTime.getYear() +
dateAndTime.getMonth()+ dateAndTime.getDay() + “_” + dateAndTime.getHours() +
dateAndTime.getMinutes() + dateAndTime.getSeconds() + “_” + counter + “.xml”;
// Sending the file: give the file name and its content
sendFileByFTP(filename, fileList[i].getContentAsBytes());
IF (getSystemDateTime().getSeconds() == dateAndTime.getSeconds())
THEN {counter = counter + 1;
} } ELSE {
counter = 0;
} // end FOR
// send QUIT command
endFtpSession();
} // end IF

Managing Results (BCI to LIS)

Description of the "RETR" Command

The results are available in the "\upload" directory on the FTP server. Any attempt to upload
from a directory other than the "upload" directory will be refused by the server.

161150-1283 - D 3-7 MYLA® V4.9

Managing Results (BCI to LIS) Transport of FTP Messages

To upload the contents of a file to the server’s current directory, use the FTP command: RETR
<File name>. Following a "RETR" command, the FTP server may send one of the following
return codes:

Code Message Explanation

550 Requested action not This error occurs when you try to upload a file which has the same
name as a directory on the server, e.g. RETR/upload
taken, not a file
550 Requested action not This error occurs when you try to upload a file from a directory other
than the "upload" directory, e.g. RETR/download/monFichier.
taken, no access
550 Requested action not This error occurs when you try to upload a file which cannot be found on
the server.
taken, file not found
451 Requested action This error occurs when you try to upload a file whose name does not
match the naming rules, as defined in BCI.
aborted: Illegal upload
- should uploaded files
having the following
definition: <analysis
system
name>_yymmdd_hhmmss_<s
equence>.xml
421 Service not available, This error occurs in cases where:
• Connection for data transfer failed (in active or passive mode).
closing control
Check that the parameters defined during creation of the connection
connection (internet address and port number) are correct.
• Connection for data transfer is suddenly cut off (power cut,
connection shut down by the client, etc.).
150 Opening data connection This message is sent to the client before transfer begins. It indicates
that connection has been correctly established and that the transfer
- transfer mode:
mode will be binary or ASCII.
<Binary mode or Ascii
mode>
226 Transfer complete The server sends this code to indicate that transfer is complete and that
the connection will soon be shut down.

Examples of How the "RETR" Command is Used

Example 1:

The FTP command sequence below enables the following actions to occur in succession:

· Establish an FTP session in active mode.

· Download a result, following the BCI rules for naming files.
· Shut down the session.

161150-1283 - D 3-8 MYLA® V4.9

Managing Results (BCI to LIS) Transport of FTP Messages

Connecting to < FTP server>

< 220 Service ready for new user
USER <user name>
< 331 User name okay, need password
PASS <user password>
< 230 User logged in, proceed
CWD /upload
< 250 Requested file action okay, completed
TYPE I
< 200 Command okay
PORT h1,h2,h3,h4,p1,p2
< 200 Command okay
RETR system1_030909_153020_0.xml
< 150 Opening data connection - transfer mode: Binary mode
< 226 Transfer complete
QUIT
< 221 Service closing control connection

Example 2:

The FTP command sequence below enables the following actions to occur in succession:

· Establish an FTP session in passive mode.

· Upload a result, following the BCI rules for naming files, with the complete path.
· Shut down the session.

Connecting to < FTP server>

< 220 Service ready for new user
1. USER <user name>
< 331 User name okay, need password
2. PASS <user password>
< 230 User logged in, proceed
3. TYPE I
< 200 Command okay
4. PASV
< 227 Entering Passive Mode (h1,h2,h3,h4,p1,p2)
5. RETR /upload/system1_030909_153020_0.xml
< 150 Opening data connection - transfer mode: Binary mode
< 226 Transfer complete
6. QUIT
< 221 Service closing control connection

161150-1283 - D 3-9 MYLA® V4.9

Managing Results (BCI to LIS) Transport of FTP Messages

Algorithm for Receipt of Results

The following algorithm describes the main steps for managing the receipt of results. This
algorithm is written in pseudocode, i.e. the algorithm gives a description of the tasks to be
performed but without language syntax. The conventions for writing in pseudocode are
described in the section Conventions to Follow in Writing Pseudocode on page 5-4.

The principle of this algorithm consists in opening a session, periodically scanning the
"upload" directory, and uploading new results.

endFtpSession();
// Opening an FTP connection
openFTPConnection(ftpHostname, portNumber);
// Opening a new session
startFTPSession(login, pwd);
// Transfer: binary mode
setBinaryMode();
LOOP {
// Scanning file names in the upload directory
// Send FTP command : NLST /upload
String[] fileNames = getResultFileNames();
// Transfer all the available files
FOR i=0 to fileNames.length() {
// transfering the file using the RETR upload/filename[i] command
getFile(fileNames[i]);
} // end FOR
// Waiting for a time period (in seconds) shorter than the time required
for //scanning the FTP account. This period depends on the BCI Net //
configuration
wait(30);
} // end LOOP
// send QUIT command
endFtpSession();

161150-1283 - D 3-10 MYLA® V4.9

4 XML Files Usage Conventions

Principle

XML messages are based on a subset of ASTM attributes defined in the specification ASTM
1394-97 and structured using XML formalism. To avoid any ambiguity in the interpretation of
messages, an XML schema is used to check the syntax and ensure that the messages follow
several semantic rules.

For further details on the XML schema, refer to the Conventions to Follow in Writing
Pseudocode on page 5-4.

The purpose of the XML schema is to define two main elements which are
"LisMessageType", for the definition of analysis requests, and "AIMessageType" for the
definition of results.

Each XML element derived from the ASTM specification is preceded by a comment indicating
the section in which the attribute definition can be found. For example, the definition of the
patient identifier is presented as follows:

 Chapter 8.1.4 of the ASTM specification describes the patient identifier

<!-- ASTM chapter 8.1.4 -->

<xsd:element name="patientIdentifier" type="StringL12"/>

IMPORTANT: Character encoding forms such as UTF-16 or UCS-2, which use two or more fixed
bytes, are not supported by BCI Link/BCI Connect for optimization reasons. Only
variable width encoding forms which can code the first 255 characters on a single-byte
are accepted by BCI Link (Shift-JIS, UTF-8, ISO-8859-1, etc.).

Note: The XML parser in charge of interpreting the bioMérieux result frame must manage:

• The CDATA section.

• The 5 predefined XML entity references (&lt; &gt;&amp;&apos;&quot;) to replace the
illegal XML characters.
• The references to Unicode entities ("&#nnn;").

161150-1283 -D 4-1 MYLA® V4.9

Rule Names XML Files Usage Conventions

Rule Names

Analysis Request
For BCI Link, the rules of the Analysis Request file name sent by the LIS are:

“FTP Account name”_YYMMDD_HHMMSS_s.xml

FTP Account name: Name of the FTP Account created in the BCI Link configuration menu.

• YYMMDD: Year, Month, Day

• HHMMSS: Hour, Minute, Second
• s: Sequence between 0 and 99. This is used if the LIS sends more than one analysis
request (in the same second).

Note: For BCI Connect, the file name pattern is not checked. 
Only the suffix xml is checked (file type).

Analysis Result
The rules of the Analysis Result file name sent by the AI are:

“AI name”_YYMMDD_HHMMSS_s.xml

• AI name: Name of the Analyzer connected to BCI (myla).

• YYMMDD: Year, Month, Day.
• HHMMSS: Hour, Minute, Second.
• s: Sequence between 0 and 99. This is used if the AI sends more than one analysis result
(in the same second).

161150-1283 -D 4-2 MYLA® V4.9

5 FTP Configuration - Additional Information

List of FTP Commands Supported by the Server

The following table lists all the commands.

FTP
Com- Description
mand
CHANGE WORKING DIRECTORY
CWD This command allows the user to change the working directory of the remote system (retrieval or
downloading of files) without altering the current session parameters. The transfer parameters also
remain unchanged. The argument is a valid access path in the local file system language.
LIST
This command causes the server to send a list. If the pathname specifies a directory or another group
LIST of files, the server should transfer a list of files in the specified directory or group. If the pathname
specifies a file, then the server should send current information on the file. A null argument implies the
user’s current working directory. The data transfer is over the data connection in ASCII type. These
data may be hard to use automatically in a program, but may be useful to a human user.
NAME LIST
This command causes a directory listing to be sent from server to user site. The pathname should
specify a directory or other system-specific file group descriptor; a null argument implies the current
NLST directory. The server will return a stream of file names and no other information. The data will be
transferred in ASCII type over the data connection as valid pathname strings separated by <CRLF> or
<NL>. This command is intended to return information that can be used by a program to further
process the files automatically.
NO ACTION
NOOP It simply prompts the server to send an "OK" reply. This command is useful for checking that the server
is operating correctly.
PASSWORD
The argument field is a Telnet string specifying the user’s password. This command must immediately
be preceded by the USER command, and completes the user’s identification for access control. Since
PASS the password is "sensitive" information, it is preferable to "mask" it as the user types it, and to avoid it
being displayed on the screen. However, it seems that the server has no means of preventing the
password from being disclosed. It is therefore the responsibility of FTP clients to avoid explicit storage
of the password and its display.
PASSIVE
PASV This command requests the server to "listen" on a data port and to wait for a connection rather than
initiate one upon receipt of a transfer command. The response to this command includes the host and
port address this server is listening to.
DATA PORT
The argument is a host port specification for the data port to be used in data connection. This
command and its associated responses are obligatory before transfer in active mode. The argument is
the concatenation of a fully qualified TCP/IP address, i.e. a 32-bit internet address and a 16-bit TCP
PORT port address. This address information is divided into 8-bit fields, and the value of each field is
transmitted as a decimal number (in character string representation). The fields are separated by
commas. A PORT command is thus of the general form:
PORT h1,h2,h3,h4,p1,p2
where h1 is the high order 8 bits of the internet host address.
PWD PRINT WORKING DIRECTORY
This command causes the name of the current working directory to be returned in the reply.
XPWD Identical to the PWD command.

QUIT LOGOUT
This command terminates a USER session and closes the control connection.

161150-1283 - D 5-1 MYLA® V4.9

List of FTP Commands Supported by the Server FTP Configuration - Additional Information

FTP
Com- Description
mand
RETRIEVE
RETR This command causes the server to transfer a copy of the file, specified in the pathname, to the server
at the other end of the data connection. The status and contents of the file at the server site will be
unaffected.
STORE
This command causes the server to accept the data transferred via the data connection and to store
STOR the data as a file at the server site. If the file specified in the pathname exists at the server site, then its
contents will be replaced by the data being transferred. A new file is created at the server site if the file
specified in the pathname does not already exist.
SYSTEM
SYST This command is used to return the type of operating system which hosts the FTP server. Whatever
the OS, this command returns a single "UNIX" value.
TYPE
This argument specifies the type of representation for data used. This command manages a single
TYPE parameter:
I: binary transfer
A: ASCII transfer
USER NAME
This argument field is a Telnet string identifying the user. The user identifier is that which is required by
the server for access to the file system of the server host. This command will normally be the first
USER command transmitted by the user after the control connections are made. The password is also
required by the server. The server will accept a new USER command at any time. This cancels any
reference to the user, the password and the previous account by restarting the session opening
sequence. All the transfer parameters remain unchanged and any file transfer in progress will be
completed with the old session parameters.

HELP
HELP
Returns the list of commands accepted by the server.

CAUTION: Connection to an FTP server for transferring data must be done with
the use of a client. The client may seemingly use a set of commands which differs
from the server’s ones; these commands are Command Aliases, a shorthand for
actual commands.

For example, the command LIST is often shortened to Is by many clients. This is done to
simplify complex tasks on the server. When you send the command ls, the client actually
sends the command LIST which is what the server recognizes. These command aliases vary
from one client to another.

161150-1283 - D 5-2 MYLA® V4.9

FTP Return Codes FTP Configuration - Additional Information

Here is a list of common Command aliases contained in many Clients and their equivalents:

Equiva-
Alias Alias Equivalent
lent
! QUIT mget RETR (used to automate the retrieval of multiple files)
Ascii TYPE A Mls LIST (list contents of multiple directories)
Binary TYPE I mdir LIST (list contents of multiple directories)
Bye QUIT mput STOR (Stores multiple files)
cd CWD Put STOR
dir LIST Pwd PWD
get RETR Quit QUIT
ls NLIST Recv RETR
send STOR Type TYPE
remotehelp HELP user USER

FTP Return Codes

Below is a list of the FTP return codes with an explanation of what each means.

Code Explanation
150 File status okay; about to open data connection.
200 Command okay.
202 Command not implemented, superfluous at this site.
Name system type. Where name is an official system name from the list in the Assigned Numbers
215 document.
220 Service ready for new user.
221 Service closing control connection.
226 Closing data connection. Requested file action successful (for example, file transfer or abort).
227 Entering Passive Mode (h1,h2,h3,h4,p1,p2).
230 User logged in.
250 Requested file action completed.
257 "PATHNAME" created.
331 User name okay, need password.
Service not available, closing control connection. This may be a reply to any command if the
421 service knows it must shut down.
425 Can’t open data connection.
451 Requested action aborted. Local error in processing.
500 Syntax error, command unrecognized. This may include errors such as command line too long.
501 Syntax error in parameters or arguments.
530 Not logged in.
550 Requested action not taken. File unavailable (e.g., file not found, no access).

161150-1283 - D 5-3 MYLA® V4.9

Conventions to Follow in Writing Pseudocode FTP Configuration - Additional Information

Conventions to Follow in Writing Pseudocode

Below is a list of the conventions to follow.

Characters / keywords Explanation

Describes an infinite loop, the code executed in the loop is enclosed in
LOOP
brackets.
Iteration on a variable var initialized at a minimum value (MinValue) and
FOR var=MinValue to MaxValue iterated until the MaxValue (MaxValue exclusive) is reached.
The code to be executed for each iteration is enclosed in brackets.
The code enclosed in brackets which follows the THEN clause is only executed
if the condition is checked.
IF condition THEN..ELSE
If the condition is not checked and an ELSE clause exists, the code enclosed in
brackets which follows the ELSE clause is executed.
var = value Assigns a value "value" to a variable "var".
A == B Tests equality between two variables A and B.
// comment A green line preceded by the character "//" represents a comment.
The functions that perform operations can be defined with or without
Return = function (argument1,
arguments and can return a value. For functions without an argument, the
argument2, ...)
syntax is MyFunction().
Syntax applied to object-oriented languages. The "function" function is
object.function(argument1, ...)
applied to the "object" object.

Introduction to XML-Schema

XML-schema is a language used to formally describe the content of an XML message. It is

derived from the works of the W3C consortium (World Wide Web); all the publications
(specifications, tutorials, etc.) are available at http://www.w3.org/XML/Schema.

The following two sections describe the notation used for the declaration of XML element
types and cardinalities.

Declaration of Types
In XML Schema, there is a basic difference between complex types, which allow elements in
their content and may carry attributes, and simple types which cannot have element content
and cannot carry attributes.

New complex types are defined using the complexType element and such definitions typically
contain a set of element declarations, element references, and attribute declarations. The
declarations are not themselves types, but rather an association between a name and the
constraints which govern the appearance of that name in documents governed by the
associated schema. Elements are declared using the element element and attributes are
declared using the attribute element.

161150-1283 - D 5-4 MYLA® V4.9

XML-Schema FTP Configuration - Additional Information

For example, USAddress is defined as a complex type, and within the definition of USAddress
we see five element declarations and each element is simple type: (string or decimal):

· <xsd:complexType name="USAddress" >

· <xsd:sequence>
· <xsd:element name="name" type="xsd:string"/>
· <xsd:element name="street" type="xsd:string"/>
· <xsd:element name="city" type="xsd:string"/>
· <xsd:element name="state" type="xsd:string"/>
· <xsd:element name="zip" type="xsd:decimal"/>
· </xsd:sequence>
· </xsd:complexType>

Occurrence Constraints
An element is defined as optional by means of the value of the minOccurs attribute which is 0.
In general, an element is required to appear when the value of minOccurs is 1 or more. The
maximum number of times an element may appear is determined by the value of a maxOccurs
attribute in its declaration.

This value may be a positive integer such as 41, or the term unbounded to indicate there is no
maximum number of occurrences. The default value for both the minOccurs and maxOccurs
attributes is 1. Thus, when an element is declared without a maxOccurs attribute, the element
may not occur more than once. If both attributes are omitted, the element must appear exactly
once.

XML-Schema

The XML schema can be found in the astm.xsd file attached to this manual.

Click in the left-hand side of the screen to access this XSD file and open it with a text editor.

161150-1283 - D 5-5 MYLA® V4.9

6 Protocol for Legacy bioMerieux Format
Messages

Principle

Control character list

Eight control characters are available for transporting messages. They are given in the table
below.

Record or
Description
Character

ENQ This is the line request character. It establishes a session between the sending and
receiving computers.

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.

STX This signals the start of a message packet. It is a single character record that expects no
response from the target computer.

RS This record contains specific message information of up to N printable ASCII characters

per record (N number depends on configuration parameter Max Record Size in BCI
Connect, property bmx_messages.max_record_size for BCI Link). There can be any
number of <RS> records in a data packet. It does not expect a response from the target
computer.

GS This record contains a checksum that determines whether the packet was received
properly. Calculation of checksums begins with the first <RS> and ends 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.

NOTE:See Checksum Field Format on page 6-6 for a description of

the checksum.

ETX This signals the end of a message packet. It is also a single character record that
expects no response from the target computer.

EOT The sending computer sends this character to the receiver to signal the end of the
session.

Protocols

There are 2 types of protocols:

· bioMérieux Literal,
· bioMérieux Literal (Alternate).

161150-1283 - D 6-1 MYLA® V4.9

Principle Protocol for Legacy bioMerieux Format Messages

bioMérieux Literal Protocol/"Download" Mode

Case #1: one analysis request

Basic message contents

Opening of a session by transmitting the

ASCII control character <ENQ>.

If the computer receiving the inquiry is

ready to receive data, it responds with the
acknowledgement character <ACK>. If it is
not ready, it sends a <NAK> character.

A communications message begins with the

ASCII start character <STX>.

Subsequent records begin with the ASCII

record separator character <RS>. The
<RS> records contain the text of the
message (max size of an RS block 80
bytes –Total of all RSs= 1920 bytes max.).

A checksum checks that all the messages

sent have been received. The checksum
must follow the <GS> separator.

The <ACK> character indicates successful

transmission of the data packet.

Communications messages end with the

<ETX> character.

Sessions end when one of the computers

receives an <EOT> character.

NOTE:There can only be 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.

Case #2: more than one analysis request

There are 2 possibilities:

· ProtocolMode=0 (Multiple sessions): The user opens a complete session for each
analysis request (e.g. for 10 analysis requests: 10 <ENQ> to <EOT>-type sessions).
Or,

· protocolMode=1 (Single session): The user opens an <ENQ> session, sends as many
complete <STX> to <ETX> blocks as there are analysis requests, and then closes the
session (e.g. for 10 requests: 1 <ACK> session is opened, 10 <STX> to <ETX> blocks are
sent and the <EOT> session is closed).

161150-1283 - D 6-2 MYLA® V4.9

Principle Protocol for Legacy bioMerieux Format Messages

The protocolMode property can be modified in the following lines, in the

<BCILink>\lib_server\properties\bcinet.properties file:
####========== RS232 Protocol mode
..
bcinet.rs232.protocolMode=0

The default property is protocolMode=0

bioMérieux Literal (Alternate) Protocol/"Download" Mode

This protocol works like the bioMérieux Literal Protocol/"Download" Mode on page 6-2, apart
from the <ACK> control which is sent AFTER the <ETX> control (and not before). See
bioMérieux Literal Protocol/"Download" Mode on page 6-2.

bioMérieux Literal Protocol/"Upload" Mode

Case #1: one result

Upload from BCI to LIS

161150-1283 - D 6-3 MYLA® V4.9

Principle Protocol for Legacy bioMerieux Format Messages

Case #2: more than one result

The Upload mode always functions in multiple sessions, that is to say with one result after
another. A complete <ENQ> to <EOT>-type message is systematically sent for each result.

If there are several results, each one is sent individually.

If the LIS is not ready, BCI will attempt to establish communication as described in the
previous case.

bioMérieux Literal (Alternate) Protocol/"Upload" Mode

This protocol works like the bioMérieux Literal Protocol/"Upload" Mode on page 6-3, apart
from the <ACK> control which is sent AFTER the <ETX> control (and not before). See
bioMérieux Literal Protocol/"Upload" Mode on page 6-3.

Frame Message Examples

Here are some examples of conform and non-conform frames:

Example 1: valid upload frame from LIS to Myla (bmx_literal mode).

17:24:24 <= <ENQ>

17:24:24 => <ACK>

17:24:24 <= <STX>

17:24:24 <= <RS>mtmpr|piG406270/A|si|ciid12345|t12|rcPos|zz|

17:24:24 <= <GS>85

17:24:24 => <ACK>

17:24:24 <= <ETX>

17:24:24 <= <EOT>

Example 2: corresponding answer from Myla to LIS.

17:26:10 => <ENQ>

17:26:10 <= <ACK>

17:26:10 => <STX>

17:26:10 => <RS>mtrsl|idSIMON|iiSIMON|isSIMON|itBC|piPID135001|pvPIV135001|pnJane|

pb1978/12/12|p

17:26:11 => <RS>sF|plROOM300|p2Room 300|pxOncto Service|pa2019/11/

07|qcCare|qeDuport Lyon 69000

161150-1283 - D 6-4 MYLA® V4.9

Carriage Return/Line Feed Option Protocol for Legacy bioMerieux Format Messages

17:26:11 => <RS>France|qfLyon|qg69000|qhFrance|qiInstitution code|qv2019/12/

05|q3S|si|ssLAC|s5Le

17:26:11 => <RS>ft Anterior Chest|stCATH|s6Catheterized|spOPID3|s8Dubol|s32019/09/

29|s415:35:53|

17:26:11 => <RS>db0033689745612|dhBILL01|dlBILL|doP|dpPatient|ciSPE135001|ctACNE|

cnTissu|ta|rr21

17:26:11 => <RS>00|tiSIMON|tjSIMON|t4P|ol7|r12019/11/07|r213:16:12|ff|rd2019/11/07|ru

13:20:02|rc

17:26:11 => <RS>Pos|zz|

17:26:11 => <GS>ba

17:26:11 <= <ACK>

17:26:11 => <ETX>

17:26:11 => <EOT>

Example 3: invalid frame from LIS to Myla:

same frame as example 1 except that the checksum <GS> is situated before the <RS>. BCI
does not reply <ACK>, then BCI does not transmit the request to MYLA®.

17:40:12 <= <ENQ>

17:40:12 => <ACK>

17:40:12 <= <STX>

17:40:12 <= <GS>85

17:40:12 <= <RS>mtmpr|piG406270/A|si|ciid12345|t12|rcPos|zz|

17:40:12 <= <ETX>

17:40:12 <= <EOT>

Carriage Return/Line Feed Option

Reminder: each message contains control characters that are critical for LIS  BCI
communication (refer to the Control character list on page 6-1).

The "<CR><LF>" (Carriage Return/Line Feed) option adds two additional control characters
after each control character so that certain characters can be recognized (e.g.: <ENQ>
<CR><LF>).

This is not the default option. If you want to use it, select it from the BCI application:

1-Select "Link Configuration".

2-Then, in the RS232 folder, highlight the link to be modified and click Update.
3-In the <CR><LF> field, select the control characters to be followed by <CR><LF>.

161150-1283 - D 6-5 MYLA® V4.9

Checksum Field Format Protocol for Legacy bioMerieux Format Messages

NOTE: This option does not apply to the characters <ACK> and <NAK>.

Figure 6-1: <CR><LF> option

IMPORTANT: When the <CR><LF> option is selected, it should always be used.

4-Click to save the configuration.

NOTE:For BCI Connect, refer to document “Service Manual BCI Connect for Myla”.

Checksum Field Format

The checksum is a control value calculated to ensure that all characters transmitted have
been received.

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

number is calculated by adding the value of all the 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.

This example applies to incoming and outgoing checksums. (It also shows the use of record
terminators.)

161150-1283 - D 6-6 MYLA® V4.9

Configuration of the Connection Protocol for Legacy bioMerieux Format Messages

Checksum Calculation:

NOTE:Checksum characters sent by the bioMérieux computer are always lower case, but both upper
and lower case characters are accepted.

Configuration of the Connection

Connection configuration is performed on the serial port.

For more information, refer to the BCI Link User Manual.

161150-1283 - D 6-7 MYLA® V4.9

Configuration of the Connection Protocol for Legacy bioMerieux Format Messages

IMPORTANT: The LIS and IA must have identical serial port parameter settings
(parity, speed, stop bit).

The table below gives the parameters required for the configuration.

Default
Parameters Description Possible values
value
Between COM1 and
Port Serial port used by the link Com 3
COMX
Between 110 and
Baud Transfer speed 9600
256000 baud

Data bits Number of bits per character Between 4 and 8 bits. 8

This bit is included as a simple means of None, Even, Odd,

Parity none
error checking Forced to 1, Forced to 0

These bits are always represented by a

negative voltage. If no further characters
are transmitted, the line stays in the
Stop bits negative (MARK) condition. The 1, 1.5 and 2. 1
transmission of the next character frame, if
any, is heralded by a start bit of positive
(SPACE) voltage.

161150-1283 - D 6-8 MYLA® V4.9

7 XML Message Format

Message Structure and Data Types

The LIS and AI message structure and data types are detailed in the following figures.

LIS Messages are Sent by a LIS to MYLA®

This message is sent by a LIS to MYLA®. This message contains one or more analysis
request(s) to be performed.

The “Result data” part can be used by the LIS to send results associated with the request.

- A request contains the following parts: Header, Patient Data, LIS Test Order, Sample Data
and optionally a LIS Test.

- A request with a result contains elements similar to those for the request and other LIS
Test data with associated Result Data.

See the Message mapping table attached to this document for the exhaustive list of fields as
referred to in Appendix - Message Mapping Table on page A-1.

Figure 7-1: LIS Message Structure

161150-1283 - D 7-1 MYLA® V4.9

Additional Information: XML Encoding of Special Characters XML Message Format

AI Messages are Sent From MYLA® to One or More LIS

This message is sent from MYLA® to the LIS to report one or more result(s).

See the Message mapping table attached to this document for the exhaustive list of fields as
referred to in Appendix - Message Mapping Table on page A-1.

Figure 7-2: AI Message Structure

Field List
See the Message mapping table attached to this document for the exhaustive list of fields as
referred to in Appendix - Message Mapping Table on page A-1.

Additional Information: XML Encoding of Special Characters

In XML, certain characters such as ‘<’ (lower than), ‘>’ (greater than) or ‘“’ (double quotes), can
be encoded in several ways. You must support the various encoding types to understand
MYLA® messages correctly.

For example: "< 16" can be encoded as "<![CDATA[< 16]]>" or as "&lt; 16". The LIS XML
parser has to support both configurations.

See http://www.w3.org/TR/REC-xml/ for more details.

Note: We recommend using a standard XML parser.

161150-1283 - D 7-2 MYLA® V4.9

Specificities of XML Format XML Message Format

Specificities of XML Format

The XML parser in charge of interpreting the bioMérieux results frame must manage:

- The CDATA section.

- The 5 predefined XML entity references (&lt; &gt;&amp;&apos;&quot;) to replace the

illegal XML characters.

- The references to Unicode entities ("&#nnn;").


Example 1: result with a value at "<0.5 ng/ml" - sent by the AI to the LIS

<result>
<value><![CDATA[< 0.5|]]></value>
<unit>UI/ml</unit>
<comment>
<source>I</source>
<text><![CDATA[The result contains a "< ", so it is surrounded with a
CDATA clause]]></text>
<type>G</type>
</comment>
</result>

Example 2: result with a value at ">0.5 ng/ml" – sent by the AI to the LIS

<result>
<value>&gt; 0.5</value>
<unit>UI/ml</unit>
<comment>
<source>I</source>
<text>The result contains a character "greater than",it is replaced
by its entity: &gt;</text>
<type>G</type>
</comment>
</result>

161150-1283 - D 7-3 MYLA® V4.9

8 BMX Message Format

Message Structure and Data Types

LIS Messages are Sent by a LIS to MYLA®

This message is sent by a LIS to MYLA®. This message contains one analysis request to be
performed.

Figure 8-1: LIS Message Structure

161150-1283 - D 8-1 MYLA® V4.9

Message Structure and Data Types BMX Message Format

AI Messages are Sent from MYLA® to One or More LIS

This message is sent from MYLA® to the LIS to report one or more result(s).

Figure 8-2: AI Message Structure

Field List
Messages exchanged in both directions are formatted according to well-defined formatting
rules.

Messages are composed as follows:

- A message type (a text mnemonic).

- A set of message fields each composed of:

· a field tag (a text mnemonic) that is a unique two-character code,

· a value (but empty values are allowed for some fields),
· a vertical bar (|) terminator ends each field.

NOTE: Refer to the Date/Time Format on page 8-3 below for further information on date and time
format.

161150-1283 - D 8-2 MYLA® V4.9

Additional Information BMX Message Format

- Field length is variable with a maximum size.

- Case of data is “as is”. This means the values are not changed to uppercase or lowercase.

- The encoding table is the one specified in the BCI configuration (on the “General
configuration” panel). The available values are: “ISO-8859-1”, “ISO-8859-2”, “Shift_JIS”,
“US-ASCII”, “UTF-8”

- The “zz” field marks the end of the message. However, this field is optional in download.

NOTE: See the attached Excel spreadsheet for the exhaustive list of fields.

Additional Information

Field Order
LIS to MYLA® messages: the field order is flexible.

MYLA® to LIS messages: no flexibility. The field order must follow the specification (see the
attached Excel spreadsheet), that is to say the field order defined in the column: Order.1 value
means that the field is not managed in bioMérieux messages.

Date/Time Format
The date format for the BMX format has been set to "yyyy/mm/dd", i.e. year on four digits/
month on two digits/day on two digits.

The time format for the BMX format has been set to "hh:mm:ss", i.e. hour on two digits (00-
23): minutes on two digits: seconds on two digits.

NOTE: The date format can be modified in the file

<BCILink>\lib_server\properties\bcinet.properties in the following lines:

· # Can be used to change the rs232 date format (eg. MM/dd/yyyy, MM/dd/yy, dd/MM/yyyy,
dd/MM/yy) Default: yyyy/MM/dd
· #bcinet.fmla.rs232.dateFormat = yyyy/MM/dd
· # Can be used to change the rs232 time format (eg. HH:mm) Default: HH:mm:ss
· #bcinet.fmla.rs232.timeFormat = HH:mm:ss


You have to uncomment (remove the # at the beginning) the line(s)
bcinet.fmla.rs232.dateFormat and/or bcinet.fmla.rs232.timeFormat as needed. You also have
to set the value as expected (see example in the properties file comment).

NOTE: For BCI Connect, refer to document "Service manual BCI Connect for Myla".

161150-1283 - D 8-3 MYLA® V4.9

9 CLSI LIS2-A2 Message Format

A code name is a set of two fields where one field is used as a code and one field is used as a
name or a value.

The aim of these messages is to provide an CLSI LIS2-A2 connection compatible, as far as
possible, with the BACTLINK ASTM connection. As a consequence, the scope of the
messages is limited to blood culture.

IMPORTANT: The chapter numbers used in this document are the CLSI LIS2-A2 ones. The
correspondence table below shows the differences with the ASTM E1394 chapter
numbers.

ASTM E1394 CLSI LIS2-A2

Header 7 Fields: 7.1.1 to 7.1.14 6 Fields: 6.1 to 6.14
Patient 8 Fields: 8.1.1 to 8.1.35 7 Fields: 7.1 to 7.35
Test Order 9 Fields: 9.4.1 to 9.4.31 8 Fields: 8.4.1 to 8.4.31
Result 10 Fields: 10.1.1 to 10.1.14 9 Fields: 9.1 to 9.14
Comment 11 Fields: 11.1.1 to 11.1.5 10 Fields: 10.1 to 10.5
Request Information 12 Fields: 12.1.1 to 12.1.13 11 Fields: 11.1 to 11.13
Message terminator 13 Fields 13.1.1 to 13.1.3 12 Fields: 12.1 to 12.3
Manufacturer
15 Fields: 15.1 to 15.4 14 Fields: 14.1 to 14.4
Information

Message Structure and Data Types

LIS Messages are sent by a LIS to MYLA®

Figure 9-1: LIS Message Structure

NOTE: The result record can be used to send the Universal Test ID for a preceding Order
Record.

161150-1283 - D 9-1 MYLA® V4.9

Additional Information CLSI LIS2-A2 Message Format

AI Messages are Sent from MYLA® to the LIS

Figure 9-2: AI Message Structure

Field List
The field mapping is done as defined in the attached Excel spreadsheet.

In the spreadsheet, we use the CLSI LIS2-A2 Standard specification chapter number as field
identification:

· 8.1.6 means field defined in paragraph 8.1.6 of the specification (Patient Name).
· 8.1.6^1 means 1st component of the field defined in paragraph 8.1.6
(Patient last name),
· 8.1.6^2 means 2nd component of the field defined in paragraph 8.1.6
(Patient first name), etc.
· 8.1.24\1 means 1st repetition of the field defined in paragraph 8.1.24
(Admission Date),
· 8.1.24\2 means 2nd repetition of the field defined in paragraph 8.1.24
(Discharge Date), etc.

Additional Information

For several fields, we managed a code name mapping by using the CLSI LIS2-A2
components, these fields are identified in the spreadsheet, the code is mapped on x.y.z^1 and
the name is mapped on x.y.z^2.

161150-1283 - D 9-2 MYLA® V4.9

Additional Information CLSI LIS2-A2 Message Format

Refer to the section Code Name Rule on page 11-1 for more details on the code/name
constraints.

If for some fields, components and/or repetition not managed by MYLA® are sent in the
request, they will be silently ignored.

Field repetitions are managed on two fields:

- 9.4.5 Universal Test ID. This field can be used to indicate multiple tests by the use of the
repeat delimiter which separates the Universal Test ID for each test.

- 7.24 A repeat delimiter (\) is used to separate the admission and discharge dates if both
dates are being transmitted.

The message character set is configurable in the BCI GUI.

The message delimiters used are:

- The one defined in the message for the messages received by BCI.

- The one defined in the CLSI LIS2-A2 specification for the message sent by BCI.

·Field delimiter: vertical bar (|)

·Repeat delimiter: backslash (\)
·Component delimiter: caret (^)
·Escape delimiter: ampersand (&)
The date and time format is the format defined by the specification. The timezone will be
ignored if received by BCI and will never be sent by BCI.

Date format YYYYMMDD and time format HHMMSS where

- YYYY=4-digit year

- MM=2-digit month

- DD= the 2-digit day

- HH=the 2-digit hour using the 24-hour time clock

- MM= the 2-digit minute

- SS=the 2-digit second

Deviation from the Standard

The field 7.1.13 (version number) has the value “1”. The value defined in the standard is “one”.

161150-1283 - D 9-3 MYLA® V4.9

10 HL7 Message Format

BCI Connect support HL7® connection compliant with IHE Laboratory Analytical Workflow
(LAW) Profile described in IHE Pathology and Laboratory Medicine (PaLM) Technical
Framework.

ID (1) Name
IHE Pathology and Laboratory Medicine (PaLM) 5 Technical
#Doc1-PaLM TF-1 Framework - Volume 1
(PaLM TF-1) Profiles
IHE Pathology and Laboratory Medicine (PaLM) 5 Technical
#Doc2- PaLM TF-2b Framework - Volume 2b
(PaLM TF-2b) Transactions
#Doc3-MLLP Transport Specification: MLLP, Release 1
CLSI AUTO16, Next-Generation In Vitro Diagnostic,
#Doc4-AUTO16
Instrument Interface, 1st Edition

(1) Used to identify the document in this section.

This connection is used to establish communications between bioMérieux® Analysis

Instruments (AI) and Laboratory Information System (LIS or Middleware) host computers. The
connection has been tested during three different testing events with multiple analyzer
managers (Connectathon). The results of these testing events are available at https://
connectathon-results.ihe.net/index.php?highlight=1_0

IMPORTANT: Users must be familiar with conventions described in Chapter 2 - Pathology and
Laboratory Medicine Integration Profiles in IHE Pathology and Laboratory Medicine
(PaLM) 5 Technical Framework - Volume 1 (PaLM TF-1) Profiles. The same conventions
has been adopted for this manual.

Transport and Protocol

The LAW profile requires the use of network connections.

Two bidirectional networks connections are used to implement the communication supporting
trigger events for the analyzer and analyzer manager.

Please refer #Doc2- PaLM TF-2b document section 3.3.2.6 and #Doc3-MLLP for the protocol
used by BCI Connect.

Laboratory Analytical Workflow Actors and Transactions

HL7 protocol provided by BCI Connect is a partial implementation of IHE LAW profile. The
uses cases and transactions supported by BCI Connect are listed below.

161150-1283 - D 10-1 MYLA® V4.9

Laboratory Analytical Workflow Actors and Transactions HL7 Message Format

BCI Connect 2.2 for MYLA® 4.8 will support LAW profile and will act as analyzer. BCI Connect
for MYLA® supports only the transaction [LAB-27] and [LAB-28], query for AWOS (Analytical
Work Order Step) is not yet supported.

Table 10-1: Laboratory Analytical Workflow – Options supported by BCI Connect for Myla

Subchapters in #Doc4-AUTO16
Option Name Transactions Profile Option Identifier
document
Contributing LAB-29 3.1.2.6, 3.2.2.4.3 LAW_CONTRIB_SUB
Substances
Patient LAB-281 3.1.2.8, 3.2.2.4.5 LAW_PAT_DEM
Demographics LAB-29
Specimen Details LAB-281 3.1.2.14, 3.2.2.4.11 LAW_SPECIMEN
Container Details LAB-281 3.1.2.15, 3.2.2.4.12 LAW_CONTAINER

1: The Analyzer Manager SHOULD send the enhanced information associated with the profile option in this
transaction only when the Analyzer supports the profile option.

Supported LAW Use Cases

Laboratory Analytical Workflow Actor Options

Note: Please refer to #Doc2- PaLM TF-2b.

AWOS Broadcast Use Case Process Flow

Note: Please refer to #Doc2- PaLM TF-2b.

161150-1283 - D 10-2 MYLA® V4.9

Laboratory Analytical Workflow Actors and Transactions HL7 Message Format

BCI Connect for Myla is not always able to determine if the cancellation is possible. By default
a cancel event will be accepted. If Myla receives a result for instrument for a canceled AWOS,
the result will be sent to LIS with NULL AWOS ID ( OBR-2 ). For the LIS this scenario is similar
to a AWOS Created on Analyzer.

AWOS Created On Analyzer Use Case

Note: Please refer to #Doc2- PaLM TF-2b.

If Myla receives result from instrument on that specimen without AWOS, the observation
results is sent to the LIS with NULL AWOS ID (OBR-2).

AWOS Broadcast [LAB 28] Transaction

161150-1283 - D 10-3 MYLA® V4.9

Laboratory Analytical Workflow Actors and Transactions HL7 Message Format

AWOS Broadcast [LAB 28] Interaction

Rejection rules

The list of required fields is defined in CLSI AUTO16 Standard. Some of them are not
mandatory in Myla and no control are done yet in BCI Connect. But fields listed below are
mandatory in the standard and in BCI Connect all OML^O33^OML_O33 messages without
this fields will be rejected. In this case, a negative acknowledgment is sent with: 
ORC-1=UA.

Segment MSH

• MSH-2: set to ^~\&

• MSH-9-1: set to OML
• MSH-9-2: set to O36
• MSH-9-3: set to OML_O33
• MSH-10: not empty
• MSH-11: set to P
• MSH-12: start by 2.5
• MSH-18: set to UNICODE UTF-8
Segment PV1 ( if any )

• PV1-2: not empty

Segment SPM

• SPM-2: free
• SPM-4: free
• SPM-7: set to P

161150-1283 - D 10-4 MYLA® V4.9

Laboratory Analytical Workflow Actors and Transactions HL7 Message Format

Segment ORC

• ORC-1: Not empty. Possible values: NW = «New order», CA = «Cancel order request»,
PR = «Previous result» (offline test)
• ORC-9: not empty, date of the request
Segment OBR

• OBR-2: not empty, unique order ID

For NTE segment, the fields listed below are mandatory: without these fields, the message is
accepted but the NTE segment is ignored.

• NTE-1: not empty, sequence number

• NTE-2: not empty, (should be set to “A” value of HL70105)
• NTE-3: free, not empty
• NTE-4: not empty
For PID segment the fields listed below are mandatory: without these fields the message is
accepted but the PID segment is ignored.

• PID-3: not empty

161150-1283 - D 10-5 MYLA® V4.9

11 Additional Information

Code Name Rule

A code name is a set of two fields where one field is used as a code and the other field is used
as a name or a value.

The code/name rule can be:

- a code only,

- a code AND name,

- a name only is not allowed. If the LIS sends a name only (without any code), the
message will be rejected by MYLA®.

When a code is used for the first time in MYLA®, it is associated with the value.

Example:

• a user transmits code "BLA", value "Beta Lactamase",

• then later code "BLA", value "BETA LACTAMASE".
• The value associated with BLA in MYLA® is: "Beta Lactamase" (i.e. the first value
received by MYLA®) and not the latest value.

Erroneous Fields Management

For mandatory fields:

- If the field is missing: the message is rejected.

- If the field has a wrong format (too long, bad date/time format, etc.): the message is
rejected.

- If the field is empty, the message is accepted by MYLA®.

For non-mandatory fields:

- If the field is missing: the message is accepted.

- If the field has a wrong format (too long, bad date/time format, etc.): the erroneous field is
ignored and the message is accepted.

- If the field is empty, the message goes through MYLA® and the appropriate business rules
are applied.

161150-1283 -D 11-1 MYLA® V4.9

Number of Results per Message Additional Information

NOTE: CLSI LIS2-A2 and HL7 messages:

- A missing field is for example 7.3 (Patient Practice Assigned Patient ID) or 7.5 and
following:

•P|1||9500000755
•P|1||9500000755|||||||||||
- A Null value ( "" ) field is for example 8.1.6 (Patient Name):

•P|1||9500000755||””||||||

NOTE:For HL7, "" can be used as NULL value example SAC-3 Container Identifier null:
SAC|||""

Number of Results per Message

The result messages sent by MYLA® will contain one result only:

- one blood culture result (one message per specimen or one message per bottle),

- or one identification,

- or one antibiogram and the corresponding identification,

- or one gram stain,

- or one simple result,

- AND none, one or several offline tests results.

Example:

The LIS sends a request for a “blood” specimen:

- one result is sent back for blood culture,

- then, one result is sent back for identification,

- and then, one result is sent back for antibiogram. In the message, the identification will be
repeated.

Decimal Separator

The decimal separator MUST always be a dot (.), regardless of the location. The comma (,)
separator MUST NOT be used.

Time Zone/Date Conversion

We assume that the timezone is the one configured on the MYLA® server (French by default).

If necessary, date conversions are performed on a Gregorian calendar.

161150-1283 -D 11-2 MYLA® V4.9

Legacy Compatibility Additional Information

Legacy Compatibility

Differences with VITEK® Legacy LIS Messages

The VITEK® Legacy LIS message formats are:

- Bmx

- ASTM-XML since VITEK® 5.01

Messages from MYLA® are compatible with the VITEK® messages as much as possible, both
in BMX and in XML mode.

However, some differences still remain. The identified differences are listed below:

- In the results, the ResultStatusText (BMX: t5, XML: resultStatusText) is not managed by
MYLA®.

- In the results, the RelativeSpecimenNumber (BMX:S0, XML: specimenRelativeIdentifier)

is not managed by MYLA®.

- In RS232: MYLA® sends c1 and c2 but VITEK® does not.

Differences with BACT/ALERT® Legacy LIS Messages

The BACT/ALERT® legacy LIS message format is CLSI LIS2-A2.

The MYLA® CLSI LIS2-A2 messages are compatible as much as possible with the BACT/
ALERT® messages, as described in the document [BACT/LINK® Interfacing Software for
bioMérieux’s BACT/ALERT Microbial Detection Systems – External Specifications April 2003].

NOTE:BCI is less permissive than BACT/ALERT. This means that some malformed messages that
were accepted by BACT/ALERT may be refused by BCI.

For more details, refer to the section Additional Information on page 9-2.

A sample request message is available as follows: 7.3.3 CLSI LIS2-A2.

A sample result message is available as follows: 7.9.1.3 CLSI LIS2-A2.

Differences between MYLA® V3 Messages and MYLA® V4.0 Messages

- Several field lengths extended in BMX message format:

•“pl” (Patient ward location) increased from 6 to 40 characters.

•“p2” (Patient ward location text) increased from 32 to 40 characters.
•“p5” (Patient Physician Name) increased from 30 to 40 characters.
•“cn” (Specimen Type Name) increased from 26 to 40 characters.
•“tg” (Disposable Lot Number) increased from 9 to 40 characters.

161150-1283 -D 11-3 MYLA® V4.9

Legacy Compatibility Additional Information

- Field length extended in XML message format: “es” (Confidence Code) increased from 20
to 40 characters.

- Management of the incubation time sent by the LIS for blood culture:

•Existing field in ASTM

•Added field in XML message format: “test.expectedDuration”
•Added field in BMX message format: “ol”
The value of this expected duration field MUST be expressed in days and decimal separator
must always be a dot (.).

NOTE:The “test.expectedDuration” and “ol” fields are also sent by MYLA® to the LIS.

- AST Results: the following new values can be sent by MYLA® for the Final Category
(BMX: an and a4, XML: ast.antibiotic.nonExpertCategory and
ast.antibiotic.nonExpertCategory): MS and X.

- The decimal separator MUST always be a dot (.), regardless of the location.

- The MIC value format always contains a decimal (for example: 15.0 instead of 15
previously).

- For VITEK® 2 antibiogram results, the “suppressedDrug”, “deducedDrug” and

“suppressedMic” flags are only sent if their value is true. For manual AST, they are
always sent.

Differences between MYLA® V4.0 Messages and MYLA® V4.1 Messages

- New dispatching rule option (refer to the section Dispatching Rules on page 11-11).

- For requests containing a blood culture result, a different testIdentifier has to be sent for
each bottle if you want to send several bottle results (refer to section Request Containing
a Blood Culture Result on page 12-19).

Differences between MYLA® V4.1 Messages and MYLA® V4.3 Messages

There is no difference between MYLA® V4.1 and MYLA® V4.3 messages.

Differences between MYLA® V4.3 Messages and MYLA® V4.4 Messages

- Bottle volume and Bottle traceability information is now included in blood culture results
(refer to Result for Blood Culture on page 12-32 for more details).

- New value for the "Abnormal Flags" field sent with blood culture results. This new value
"M" is sent if a bottle reloading error is detected.

This flag is sent with all bottle result messages. A bottle reload error is raised when a bottle
that has initially been loaded into an instrument is then reloaded into a different Bank.

NOTE:Because of these modifications, the astm.xsd file and the Excel message mapping table
have been modified (they are both attached to this document).

161150-1283 -D 11-4 MYLA® V4.9

Legacy Compatibility Additional Information

Differences between MYLA® V4.4 Messages and MYLA® V4.5 Messages

To eliminate differences between direct VITEK® 2 to LIS and MYLA® to LIS connections, the
fields used to send Identification result comments and AST results comments have been
modified.

RS232:

• Identification and AST comments are now in fields “nc” and “nd” instead of fields “eo” and
“er” which are no longer used.
• “nc” and “nd” fields are now repeatable.
Example of a MYLA® Message:
...|ta|rtSU_V2_NA|rnAST-PT22|rr63384|tiHospital|tjV2S|t4F|nccode1|ndcomment
for code 1|nccode2|ndcomment for code 2|r12013/11/22|r211:24:23|r32013/11/
22|r417:54:23|ts|…

XML:

• Until MYLA® V4.5, a VITEK® 2 AST result comment was sent in the
“userAstCommentList” field, a VITEK® 2 Identification result comment was sent in
the“userIdCommentList” field, and a manual ID/AST comment was sent in the
“comment.code/text” field.

Since MYLA® V4.5, a new field structure has been added to be aligned with the VITEK® 2
LIS direct connection. The structure is now:
<userComment>
<comment>
<code>code1</code>
<text>comment for code1</text>
<source>P</source>
<type>G</type>
</comment>
<comment>
<code>BMX009</code>
<text>Comment for BMX009</text>
<source>P</source>
<type>G</type>
</comment>
</userComment>

• No change to the MYLA® Manual ID/AST comments.

The ID and AST comments sent by the LIS to MYLA® in offline test results are archived but not
displayed in the MYLA® Patient view screen.

Differences between MYLA® V4.5 Messages and MYLA® V4.6 Messages

- There is no difference between MYLA® V4.5 and MYLA® V4.6 messages.

- Errors in chapters BMX Format on page 11-12 and BMX format on page 12-1 have been
corrected.

161150-1283 -D 11-5 MYLA® V4.9

Legacy Compatibility Additional Information

Differences between MYLA® V4.6 Messages and MYLA® V4.7 Messages

- Until MYLA® V4.6, the “Manufacturer Information Record” was linked to the “Patient”
record. Consequently, when the “Patient” record was not present, the first “M” record
sequence number was set to 0. To fix this issue and to be aligned with the LIS2-A2
specification, the “M” record is now linked to the “Result” record. 
This difference compared to the previous versions of MYLA® can be visible in blood
culture results if the treaceability report is enabled and if several bottles are linked to a
single specimen. In this case, the "M" record sequence number was incremented by 1,
from 1 to N until MYLA® V4.6 as shown below. From MYLA® V4.7, this sequence number
restarts at 1 for each bottle result.

Until MYLA® V4.6

P|1|RES_P8
O|1|RES_S8||||||||||||||||||||20180207165702
R|1|^^^BC^BSN^SNQJMC05|Neg|||||F|||20180207165210|20180207165702|1B1
R|2|^^^TTD^BSN^SNQJMC05|0.1|||||F|||20180207165210|20180207165702|1B1
R|3|^^^SVM^BSN^SNQJMC05|1.0|mL||||F|||20180207165210|20180207165702|1B1
M|1|SNQJMC05|^BOTTLE^BSN^^^20180207^165210^20180207^165730|1B1
R|4|^^^BC^BSN^SNQJMC09|Pos|||||P|||20180207165238|20180207165714|1B4
R|5|^^^TTD^BSN^SNQJMC09|0.1|||||P|||20180207165238|20180207165714|1B4
R|6|^^^SVM^BSN^SNQJMC09|1.2|mL||||P|||20180207165238|20180207165714|1B4
M|2|SNQJMC09|^BOTTLE^BSN^^^20180207^165238^20180207^165725|1B4
L|

From MYLA® V4.7

P|1|RES_P8
O|1|RES_S8||||||||||||||||||||20180207165702
R|1|^^^BC^BSN^SNQJMC05|Neg|||||F|||20180207165210|20180207165702|1B1
R|2|^^^TTD^BSN^SNQJMC05|0.1|||||F|||20180207165210|20180207165702|1B1
R|3|^^^SVM^BSN^SNQJMC05|1.0|mL||||F|||20180207165210|20180207165702|1B1
M|1|SNQJMC05|^BOTTLE^BSN^^^20180207^165210^20180207^165730|1B1
R|4|^^^BC^BSN^SNQJMC09|Pos|||||P|||20180207165238|20180207165714|1B4
R|5|^^^TTD^BSN^SNQJMC09|0.1|||||P|||20180207165238|20180207165714|1B4
R|6|^^^SVM^BSN^SNQJMC09|1.2|mL||||P|||20180207165238|20180207165714|1B4
M|1|SNQJMC09|^BOTTLE^BSN^^^20180207^165238^20180207^165725|1B4
L|
- When MYLA® V4.7 is connected to the LIS through BCI Connect:

•The request messages may possibly be in a new format containing Gram Staining
result (refer to the Request Containing a Gram Staining Result on page 12-22).
•BCI Connect also supports new offline test formats (see Request Containing an
Offline Result on page 12-28).
•BCI Connect for MYLA® V4.7 no longer supports xml request messages with
several <testOrder> blocks or several <test> blocks. Same limitation for CLSI LIS2-A2
format, the sequence HPOOL is no longer supported, the sequence HPOPOL is still
possible (this issue is solved with version 4.7.1).
•The xml result messages sent by BCI Connect to the LIS contain the
<senderName> header field containing the "myla" value.

161150-1283 -D 11-6 MYLA® V4.9

Legacy Compatibility Additional Information

NOTE:The <senderName> header field can be disabled or changed from the BCI Connect Scripting
screen.

Differences between MYLA® V4.7 Messages and MYLA® V4.7.1 Messages

When MYLA® V4.7.1 is connected to the LIS through BCI Connect, request message with
several <testOrder> blocks or several <test> blocks are now supported. It means that BCI
Connect and BCI Link have the same behavior.

The VITEK® MS identification result messages differ depending on the version of VITEK® MS
system. The table below lists the differences between a result provided with VITEK® MS 3.0
and a result provided with VITEK® MS 3.1. To reduce these differences, some user mapping
functions are available for BCI Link and BCI Connect. When user mapping functions are
required, it is strongly recommended to use BCI Connect.The differences between the result
provided with VITEK® MS 3.0 and the result provided by VITEK® MS 3.1 with 3.0 compatibility
user mapping enabled are also available in table below.

VITEK MS 3.1 with 3.0

BMX
XML format VITEK MS 3.0 VITEK MS 3.1 compatibility user
format
mapping enabled
Specimen.isolateRelativ rr Not sent Sent with unique identifier Not sent
eIdentifier

universalIdentifier.testGr it ID Not sent ID

oupCode

universalIdentifier.testId rt MALDI-TOF 76346-6 (LOINC® Code) MALDI-TOF

entifier
Configurable in MYLA®
universalIdentifier.testNa rn MALDI-TOF test Bacteria identification MALDI-TOF test
me

test.instrumentCharge ok Send with numerical value Not sent Not sent

test.action.actionName ed Not sent Sent, possible values: Not sent
• prepare
• validate
test.action.actionDate eh Not sent Sent with action date value Not sent
test.action.actionOperat ee Not sent Sent with action date value Not sent
or

bmxResultData.disposab dt AXIMA_SLIDE_REF AXIMA_SLIDE AXIMA_SLIDE_REF

le.disposableType
Or Or Or
MATRIX MATRIX MATRIX
bmxResultData.disposab tu Disposable text identifier Not sent when disposableType Disposable text identifier
le.reference
equals MATRIX.
Disposable numeric identifier
when disposableType equals
AXIMA_SLIDE
bmxResultData.disposab tp Disposable numeric Disposable text identifier Disposable numeric
le.disposableIdentifier
identifier identifier
bmxResultData.disposab N/A Sent Not sent, replaced by test. Sent
le.disposableSetupTech
nologist
action.actionOperator for
action prepare
disposableFinalDateTim td Sent Not sent Sent
e

tracabilityResult.extraRe N/A Sent (Numeric value) Not sent Not sent

sultData

161150-1283 -D 11-7 MYLA® V4.9

Legacy Compatibility Additional Information

"VITEK® MS 3.0 compatibility" user mapping

"VITEK® MS 3.0 compatibility" user mapping scripts are available for BCI Link and BCI
Connect. For BCI Link, please contact your GCS representative. For BCI Connect, this user
mapping script can be activated in "Scripting configuration" view.

"VITEK® MS 3.0 Compatibility" user transformation is available in BCI Connect scripting

library version 2.2.2 and above.

Differences between MYLA® V4.7.1 Messages and MYLA® V4.8 Messages

- Support of IHE / HL7 protocol. This protocol is now supported by MYLA® V4.8 for all types of
request and all types of results: identification, susceptibility and blood culture.

- Possibility to cancel request: from MYLA 4.8 and BCI Connect (not supported by BCI Link), the LIS
is able to cancel a request.

To cancel a request the LIS have to send request message with "Action Code" field set to
"CA".

Protocol Field

RS232 oe

XML test.actionCode

HL7 ORC-1

LIS2-A2 8.4.12

- Possibility to send clinical information for MYLA® AST Filter function, see Request Containing
Clinical information for MYLA® AST Filter feature on page 12-18 for more details.

- The VITEK® MS identification result messages contain the field «universalIdentifier».

«testGroupCode» with the value: 'ID'. This is true for all versions of VITEK® MS. With MYLA® 4.7.1
and VITEK® MS 3.1, this field was not sent.

Differences between MYLA® V4.8 Messages and MYLA® V4.9 Messages

- There is no difference between MYLA® V4.8 and MYLA® V4.9 messages.

- Request message fields:

• admission date (PV1-44)

• discharge date (PV1-45)
are now supported in HL7 format.

161150-1283 -D 11-8 MYLA® V4.9

Legacy Compatibility Additional Information

Patient Duplication Management

Patient “activity” time

By default, a patient is considered as “active” for 52 weeks. This means that the LIS can reuse
the patient identifiers after 52 weeks (by default). This timeframe can be changed in the
MYLA® configuration.

For traceability safety, we recommend not to reuse patient identifiers.

Rules for detecting a new patient

Let us assume P1 is the patient sent by the LIS:

- If P1.identifier is not present in the MYLA® patient database or if P1.identifier is present

but not active (see the previous section about Patient Duplication Management on page
11-9, the patient P1 is considered as a new patient.

- If P1.identifier is already present in the MYLA® patient database, the patient P1 is

considered as equal to the existing patient if:

Pi.lastname = P1.lastname and,

Pi.firstname = P1.firstname and,

Pi.birthdate = P1.birthdate and,

Pi.gender = P1.gender

- Otherwise the patient P1 is considered as undetermined and the user must determine
whether the identified Pi(s) are equal to P1 or not.

- When the same patient information is detected (same lastname, firstname, birthdate and
gender) on different patient IDs, a duplicate is reported. The user can resolve the patient
duplicate by analyzing the differences between the patient record stored in MYLA® and
patient data sent by the LIS (Fix Inconsistency screen in MYLA®).

Rules for updating patient fields (from LIS request)

By default, all the fields related to the patient, except the fields used for detecting a new
patient, are automatically updated (the history is not managed).

The LIS is the master for all patient information, and this information can be updated from the
LIS (Patient Demography, Patient Visit, Patient Prescription).

Examples

Current MYLA® status

Date created/
Patient ID Lastname Firstname Birthdate Gender
updated
XX-123 Abc Bob 2000/jan/01 M 2010/jan/03
XX-124 Def Clara 2000/jun/10 F 2010/feb/10

161150-1283 -D 11-9 MYLA® V4.9

Legacy Compatibility Additional Information

XX-125 Ghi Bob 2000/apr/17 M 2010/mar/18

The timeframe for the patient is 52 weeks.

What we receive from the LIS:

On 2010/apr/01 data are received:

Patient ID Lastname Firstname Birthdate Gender
XX-126 Klm Bob 2000/oct/20 M

• Create a new patient.

On 2010/july/01 data are received:
Patient ID Lastname Firstname Birthdate Gender
XX-125 Ghi Bob 2000/apr/17 M

• Update the patient “XX-125”.

On 2010/oct/01 data are received:
Patient ID Lastname Firstname Birthdate Gender
XX-123 Abc Bob 2000/jan/01 M

• Update the patient “XX-123”.

On 2010/dec/01 data are received:
Patient ID Lastname Firstname Birthdate Gender
XX-124 Def Ghi Clara 2000/jun/10 F

• Undetermined, the user must inform MYLA® if it is the same patient or not.
On 2011/jan/25 data are received:
Patient ID Lastname Firstname Birthdate Gender
XX-123 Abc Bob 2000/jan/01 M

• Create a new patient (we are out of the timeframe of 52 weeks).

Two different patients with the same patient ID are in the MYLA® database.
Duplicate Example

Current MYLA® status:

Patient ID Lastname Firstname Birthdate Gender

XX-456 Def Mike 1978/nov/01 M

On 2012/jan/15 data are received:

Patient ID Lastname Firstname Birthdate Gender
XX-789 Def Mike 1978/nov/01 M

• A duplicate is detected and needs to be fixed manually in MYLA®.

Specimen Duplication Management

NOTE:Specimen rules are applied even if the requests are sent from several LIS.

161150-1283 -D 11-10 MYLA® V4.9

Legacy Compatibility Additional Information

Specimen “activity” time

By default, a specimen is considered as “active” for one month. This means that the LIS
reuses the specimen identifiers after one month (by default). This timeframe can be changed
in the MYLA® configuration.

Rules for detecting a new specimen

Let us assume that S1 is the specimen sent by the LIS and P1 the patient linked to this
specimen:

- If a specimen Si such as Si.identifier does not exist in the database = S1.identifier, and
Pi.identifier = P1.identifier over a period of time (refer to the previous section about
Specimen “activity” time on page 11-11, specimen S1 is considered as a New specimen.

NOTE:If VITEK® is configurated in demo less mode, the test is based only on the specimen identifier.

- Otherwise, if a specimen such as Si.identifier = S1.identifier, and Pi.identifier different

than P1.identifier over a period of time exists in the database, the request is rejected. If
it is the same patient, the specimen data will be updated (null values will be ignored).

NOTE:Two specimens with the same ID cannot be linked to different patients within the same activity
time period.

Rules for updating specimen fields (from LIS request)

All the fields related to the specimen except the fields used for detecting a new specimen
unicity (see previous rule) are automatically updated.

Test Order Management

Rules for detecting new test orders

The “action code” defined in the ASTM standard (field 8.4.12) is not taken into account (does
not correspond to the bacteriology domain where test requests are not managed explicitly,
only specimen and patient information are downloaded).

The following rules are applied:

- If a test order is found with the same patient identifier (if available) and same specimen
identifier within the same activity period and specimen activity time (refer to previous
sections about Differences between MYLA® V4.8 Messages and MYLA® V4.9
Messages on page 11-8 and Specimen Duplication Management on page 11-10, it is
considered as an Update.

- Otherwise it is a new test order

Dispatching Rules
Option 1: LIS Dispatching - MYLA® dispatches test orders to instrument systems based on
the <testGroupCode> field sent by the LIS.

161150-1283 -D 11-11 MYLA® V4.9

Legacy Compatibility Additional Information

The values are: ID, SU, BC

- ID/SU: Sent to VITEK® systems

- BC: Sent to 3D and/or VIRTUOTM systems

IMPORTANT!Compared to MYLA® V4.4, all messages without element <testGroupCode>

are no longer treated as a request but as an update of patient and specimen
data.
The result will be that no request will be sent to the instrument connected to
MYLA®.
All message with emtpy <testGroupCode> or with the value “NA” are treated
as request send to all instruments connected to MYLA®.

Example:

…
<test>
<universalIdentifier>
<testGroupCode>SU</testGroupCode>
</universalIdentifier>
</test>
…

Option 2: MYLA® dispatching - Patient and specimen data are sent to the connected systems
depending on the <specimenType> field value.

- Blood: 3D and/or VIRTUOTM + VITEK®: If the LIS manages the bottle IDs, the first time a
specimen ID + bottle ID are received, the test order is sent to all systems. If the LIS sends
a second bottle for the same specimen ID over a period of time, the request is sent to the
3D and/or VIRTUOTM systems only.

- Otherwise VITEK® only.

Exception case: If the <specimenType> is unknown (not defined in the MYLA® system) or
empty, the request is sent to all the connected systems.

The 2 options are a part of MYLA® settings. Option 1 is the most efficient dispatching method
and is the recommended setting.

LIS Result Sending

• Rule 1: A LIS receives the results for which it sent requests. If there is no initial test
request linked to the results, it is sent to all LIS.
• Rule 2: External data management (seen as special LIS) does not send requests and
receive all results.
• Rule 3: If a LIS sends its request after the results are obtained, the MYLA® system links
the results to the demographic data and sends all the results back to the LIS (in the same
order in which they were acquired/reviewed).
• Rule 4: Any request modifications (LIS sending a known request or MYLA® correcting
inconsistent information) initiate the sending of the result to the LIS.

161150-1283 -D 11-12 MYLA® V4.9

Typical Workflow Additional Information

NOTE:If this test request was created without any patient information on the instrument, the results
will be associated with the special patient id: “!oRPHaN!”.

Typical Workflow

According to the dispatching mode used (refer to the section Dispatching Rules on page
11-11), one analysis request can initiate different workflows.

Example: If the dispatching mode is done by using “specimen type” and that specimen type is
blood, both a blood culture workflow and an id/ast workflow will be initiated.

Blood Culture Workflow

This workflow mainly applies to the MYLA® V2 messages (refer to the section Result for Blood
Culture on page 12-32).

A MYLA® V1 message has no “specimen” status, the message is for one bottle and it is sent
each time there is a change on this bottle’s result/status.

Generalities

Analysis requests can be sent to MYLA® in two ways:

- One request with the specimen identifier only or with one or several disposable (bottle)
identifiers.

- Several requests with the same specimen identifier and each with different disposable
(bottle) identifiers.

The specimen result can be:

- “Positive” if at least one bottle is positive.

- “Negative” if all the bottles are negative and have completed their test period.

- “Unknown” in all other cases (even if a bottle has a W status).

The result status code for the specimen can be:

- F (Final) if all the bottles have a “Negative” result ( unloaded) and “Final” status.

- P (Preliminary) if at least one bottle has a “Positive” result or a W result Status.

- I (In instrument, result pending) if there are no bottles with a “Positive” result and at least
one bottle with a “Negative to date” result, or one negative bottle still loaded in the
instrument.

The bottle result can be:

- “Positive” if positive.

- “Negative” if negative and the bottles have completed their test period and are unloaded.

- “Negative to date” (Unknown) if negative and the bottle has not completed its test period.

161150-1283 -D 11-13 MYLA® V4.9

Typical Workflow Additional Information

The result status code of a bottle can be:

- P (Preliminary) if the bottle is positive.

- F (Final) if the bottle is negative. The incubation time has been reached, the bottle has
been unloaded.

- I (In instrument, result pending). The bottle is not positive and the incubation time has not
been reached.

- W (Warning). A problem has occurred with the bottle: The result is questionable.

The date on which the result was determined (field ID 298 in the attached Excel spreadsheet
file) is:

- The date on which the result was determined for Positive and Negative bottles (bottle still
loaded or not).

- The current Date/Time “Negative to date” bottle.

Typical Workflow

NOTE:On some message formats, the specimen results are not sent. (Only the bottle results are
sent).

- For requests, see sample message in Request with optional DisposableIdentifier and
optional expected duration on page 12-25.

- For results, see sample message in Several Bottle Results in the Same Message on page
12-39.

Sample workflow 1:

Negative bottles

Bottle A Bottle B LIS message

Time 0 N/A N/A MYLA® receives a request from the LIS
Time 1 Loaded Loaded No message
No message
Time 2 Still Negative to date Still Negative to date
(if “Periodic sending” mode disabled).
End of incubation time: End of incubation time:
Time 3 No message
Bottle A is Negative Bottle B is Negative
MYLA® sends a message:
Specimen, status: I, result: Unknown
Time 4 Unload N/A
Bottle A: status: F, result: Negative
Bottle B: status: I, result: Negative to date

161150-1283 -D 11-14 MYLA® V4.9

Typical Workflow Additional Information

MYLA® sends a message:

Specimen, status: F, result: Negative
Time 5 N/A Unload
Bottle A: status: F, result: Negative
Bottle B: status: F, result: Negative.

Sample workflow 2:

One positive bottle, one negative bottle

Bottle A Bottle B LIS message

Time 0 N/A N/A MYLA® receives a request from the LIS

Time 1 Loaded Loaded No message

MYLA® sends a message:

Specimen, status: P, result: Positive
Time 2 Bottle becomes Positive Still Negative to date
Bottle A: status: P, result: Positive
Bottle B: status: I, result: Negative to date

End of incubation
End of incubation time:
Time 3 Bottle is Positive
time: Bottle is No message
Negative

Time 4 Unload N/A No message

MYLA® sends a message:

Specimen, status: P, result: Positive
Time 5 N/A Unload
Bottle A: status: P, result: Positive
Bottle B: status: F, result: Negative

Sample workflow 3:

Both bottles unloaded before the end of the analysis:----

Bottle A Bottle B LIS message

Time 0 N/A N/A MYLA® receives a request from the LIS

Time 1 Loaded Loaded No message

Time 2 Still Negative to date Still Negative to date No message

Stop sending Negative to date for bottle A if

Time 3 Unload N/A
“Periodic sending” mode enabled

161150-1283 -D 11-15 MYLA® V4.9

Typical Workflow Additional Information

Stop sending Negative to date for bottle B if

Time 4 N/A Unload
“Periodic sending” mode enabled

Sample workflow 4:

One bottle unloaded before end of analysis – other bottle completes analysis

Bottle A Bottle B LIS message

Time 0 N/A N/A MYLA® receives a request from the LIS

Time 1 Loaded Loaded No message

Time 2 Still Negative to Date Still Negative to Date No message

Stop sending Negative to date for bottle A if
Time 3 Unload N/A
“Periodic sending” mode enabled
End of incubation time
Time 4 N/A
bottle is still Negative
No message

MYLA® sends a message to the LIS:

Specimen, status: I, result: Unknown
Time 5 N/A Unload
Bottle B: status: F, result: Negative
NOTE:Note: No information for Bottle A

Sample workflow 5:

One positive bottle with a sub-culture

Bottle A Bottle B LIS message

Time 0 N/A N/A MYLA® receives a request from the LIS

Time 1 Loaded Loaded No message

MYLA® sends a message:

Specimen, status: P, result: Positive

Time 2 Bottle became Positive Still Negative to date · Bottle A: status: P, result: Positive
· Bottle B: status: I, result: Negative to
date
Unload – Gram stain
Time 3 shows no organisms, N/A No message
bottle is subcultured
Bottle reloaded and
Time 4 instrument assigns a N/A No message
“Negative to date” status
End of incubation time: End of incubation time:
Time 5 Bottle is Negative Bottle is Negative
No message

MYLA® sends a message:

Specimen, status: I, result: Unknown
Time 6 N/A Unload
Bottle A: status: I, result: Negative to date
Bottle B: status: F, result: Negative

161150-1283 -D 11-16 MYLA® V4.9

Typical Workflow Additional Information

MYLA® sends a message:

Specimen, status: F, result: Negative
Time 7 Unload N/A
Bottle A: status: F, result: Negative
Bottle B: status: F, result: Negative

Blood Culture Codes

Blood culture bottle type

Type Code Bottle Name LIS code Suggested usage

0 Generic G CLINICAL/INDUSTRY
1 Unknown U CLINICAL/INDUSTRY
11 BACT/ALERT SA BSA CLINICAL
12 BACT/ALERT SN BSN CLINICAL
13 BACT/ALERT FA BFA CLINICAL
14 BACT/ALERT FN BFN CLINICAL
15 BACT/ALERT PF BPF CLINICAL
17 BACT/ALERT MP BMP CLINICAL
18 BACT/ALERT MB BMB CLINICAL
50 BTA I-AST BIA INDUSTRY
51 BTA I-NST BIN INDUSTRY
52 BTA I-LYM BIL INDUSTRY
53 BACT/ALERT BPA BPA INDUSTRY BLOOD BANK
NOTE: Not used in USA
54 BACT/ALET BPN BPN INDUSTRY BLOOD BANK
NOTE: Not used in USA
55 BACT/ALERT- I FA BIFA INDUSTRY
56 BACT/ALERT- I FN BIFN INDUSTRY
57 BACT/ALERT- I PF BIPF INDUSTRY
58 BACT/ALERT FA Plus BFA+ CLINICAL
59 BACT/ALERT FN Plus BFN+ CLINICAL
60 BACT/ALERT PF Plus BPF+ CLINICAL
61 BACT/ALERT iFA Plus BIFA+ INDUSTRY
62 BACT/ALERT iFN Plus BIFN+ INDUSTRY

If necessary, the bottle type can be sent by the LIS in the blood culture request, as shown in
the following examples.

This information is sent only to VIRTUOTM and not to BACT/ALERT® 3D. Please refer to the
VIRTUOTM documentation for more details.

161150-1283 -D 11-17 MYLA® V4.9

Typical Workflow Additional Information

XML

...
<testOrder>
<test>
…
<universalIdentifier>
<testGroupCode>BC</testGroupCode>
<testIdentifier>BSN</testIdentifier>
</universalIdentifier>
<expectedDuration>7</expectedDuration>
<disposableIdentifier>BNS17S7J5</disposableIdentifier>
…
</test>
</testOrder>
...

RS232

mtmpr|itBC|piG406270/A|si|ciid12345|rtBSN|zz|

CLSI LIS2-A2

H|\^&|||LIS|||||BacT/
ALERT||P|1|20110128131400O|1|AC0302||^^^BC^BSN^SA003003^7|S|20110128155020|2011
0128164530|||COLLECTOR|N|||20110128170000|BLOOD^LeftArm|DRHARRIS^Harris^Steve^^
^Dr.||||||||||||||L|1

ID/AST Workflow

Generalities

Some of the test results required for the ID/AST can be done offline and transmitted to the
MYLA® system by the LIS. Offline means that the result has been obtained outside of the
MYLA® system. 
Identification results sent to MYLA® as Offline test is transmited to all AST systems connected
to MYLA®. 
Beta Lactamase offline test result is transmited to all Vitek 2 systems connected to MYLA®.

All others offline tests are only displayed in MYLA®.

Remark for VITEK® MS results:

The following VITEK® MS results are not sent to the LIS:

- “discarded” results;

- Result status “X” (due to Calibration Failed);

- In all other cases (Bad spectrum, NoID, Control Failed, or even a discarded good ID);

161150-1283 -D 11-18 MYLA® V4.9

Typical Workflow Additional Information

- For non-clinically validated species, results are not sent to the LIS (non-clinically validated
species include organisms with insufficient clinical performance data and organisms not
found in human clinical samples).

Typical Workflow

1-The LIS sends an analysis request for one sample.

See sample message in Basic Request with Test Group on page 12-1, in Basic Request with
Specimen Type on page 12-2 or in Non Basic Request (patient and specimen info) on page
12-4.

2-The identification is performed on one instrument. MYLA® sends an identification result

message to the LIS. See sample message in Result for Identification on page 12-46.
3-The antibiogram is performed on one instrument. MYLA® sends an antibiogram result
message to the LIS. See sample message in Result for Antibiogram on page 12-53.

NOTE:This message will also contain the identification.

Some offline test information may have to be filled in to perform the ID/AST.

Workflow with Offline Test

1-The LIS sends an analysis request for one sample.

See sample message in Basic Request with Test Group on page 12-1, in Basic Request with
Specimen Type on page 12-2 or in Non Basic Request (patient and specimen info) on page
12-4.

2-The LIS sends offline test result information for the previously sent sample.
See sample message in Request Containing an Offline Result on page 12-28

NOTE:Some message formats (XML for example) allow the analysis request and the offline test result
to be sent in a single message.

3-The identification is performed on one instrument. MYLA® sends an identification result

message to the LIS. See sample message in Result for Identification on page 12-46.
4-The antibiogram is performed on one instrument. MYLA® sends an antibiogram result
message to the LIS. See sample message in Result for Antibiogram on page 12-53.

NOTE:This message will also contain the identification.

Workflow with Offline Identification

1-The LIS sends an analysis request for one sample.

See sample message in Basic Request with Test Group on page 12-1, in Basic Request with
Specimen Type on page 12-2 or in Non Basic Request (patient and specimen info) on page
12-4.

2-The LIS sends offline identification result information for the previously sent sample.
See sample message in Full request with offline identification on page 12-15.

161150-1283 -D 11-19 MYLA® V4.9

Typical Workflow Additional Information

NOTE:Some message formats (XML for example) allow the analysis request and the offline test result
to be sent in a single message.

NOTE:If an ID comment field ‘userIdCommentList” is sent to MYLA®, it will be saved in MYLA® but it
will not be displayed in the MYLA® ”Patient View” screen.

3-The antibiogram is performed on one instrument. MYLA® sends an antibiogram result

message to the LIS. See sample message in Result for Antibiogram on page 12-53. 
The AST result always contains the organism used to calculated it. This organism can be
the one sent by the LIS, OR an other one performed on identification analyzer connected
to MYLA®, OR identification result entered manually in MYLA®.

Other Results sent by the LIS to MYLA®

In addition to offline test results and identification results, MYLA® is able to receive blood
culture results and AST results provided by instruments directly connected to the LIS.

See sample message in Message from LIS with an AST Result only on page 12-11 and
Request Containing a Blood Culture Result on page 12-19.

For the offline blood culture, it is possible to specify the type of bottle used for the test.

The types of blood cultures supported by MYLA® are Anaerobic, Aerobic, Pediatric and
Unknown. The value can be sent to MYLA® thanks to the <testIdentifier> field included in the
<universalIdentifier> block after the <testGroupCode> field. See sample message in Request
Containing a Blood Culture Result on page 12-19.

List of Supported Instruments:

- Microflex LT (Bruker Daltonics)

- SIRSCAN (I2A)

- ADAGIOTM (Bio-Rad)

- BD PhoenixTM (Becton Dickinson)

- Microscan® WalkAway® (Beckman Coulter)

- BACTEC® (Becton Dickinson)

- VersaTREK® (Thermo Scientific)

If the instrument connected to the LIS is not in this list, a generic code should be used.

There is one generic code per type of results: SU, ID, BC.

MYLA® Test Code Result Bottle

Module Type
Identifier Type Type
Ref ID in the knowledge base of the PHOENIX
ID_PHOENIX ID
type module
Ref ID in the knowledge base of the PHOENIX
SU_PHOENIX SU
type module
Ref ID in the knowledge base of the SIRSCAN
ID_SIRSCAN ID
type module

161150-1283 -D 11-20 MYLA® V4.9

Typical Workflow Additional Information

Ref ID in the knowledge base of the SIRSCAN

SU_SIRSCAN SU
type module
Ref ID in the knowledge base of the
ID_LABPRO ID
MICROSCAN type module
Ref ID in the knowledge base of the
SU_LABPRO SU
MICROSCAN type module
Ref ID in the knowledge base of the ADAGIO
SU_OSIRIS SU
type module
Ref ID in the knowledge base of the BRUKER
ID_MALDI ID
type module
Ref ID in the knowledge base of the BACTEC
BC_BACTEC_NA BC NA
type module
Ref ID in the knowledge base of the BACTEC
BC_BACTEC_AN BC AN
type module
Ref ID in the knowledge base of the BACTEC
BC_BACTEC_AE BC AE
type module
Ref ID in the knowledge base of the BACTEC
BC_BACTEC_PE BC PE
type module
Ref ID in the knowledge base of the
BC_VERSATREK_NA BC NA
VERSATREK type module

MYLA® Test Code Result Bottle

Module Type
Identifier Type Type
Ref ID in the knowledge base of the
BC_VERSATREK_AN BC AN
VERSATREK type module
Ref ID in the knowledge base of the
BC_VERSATREK_AE BC AE
VERSATREK type module
Ref ID in the knowledge base of the
BC_VERSATREK_PE BC PE
VERSATREK type module
Ref ID in the knowledge base of the
BC_GENERIC_NA BC NA
GENERIC_BC type module
Ref ID in the knowledge base of the
BC_GENERIC_AN BC AN
GENERIC_BC type module
Ref ID in the knowledge base of the
BC_GENERIC_AE BC AE
GENERIC_BC type module
Ref ID in the knowledge base of the
BC_GENERIC_PE BC PE
GENERIC_BC type module

ID/AST Codes

Identification confidence code

The table below lists the available confidence codes used for the confidence code field.

All the codes can be sent by MYLA® for the results.

Five codes (ID_PRESUMPTIVE, ID_EXCELLENT, ID_VERY_GOOD, ID_GOOD,

ID_ACCEPTABLE) can be used when the LIS sends offline test to MYLA®.

161150-1283 -D 11-21 MYLA® V4.9

Typical Workflow Additional Information

For the ID_PRESUMPTIVE code, the organism code and name are free text (see Message
from LIS with a (presumptive) identification result only on page 12-10).

For all the other codes, the organism code must match an organism defined on MYLA® (see
Message from LIS with an identification result only on page 12-8).

Key Confidence Code Confidence Label

7 ID_PRESUMPTIVE Presumptive identification
8 ID_EXCELLENT Excellent identification
9 ID_VERY_GOOD Very good identification
10 ID_GOOD Good identification
11 ID_ACCEPTABLE Acceptable identification
12 ID_LOW_DISCRIM Low discrimination
Organism with low reactivity biopattern - please check
13 ID_LOW_REACTIVE_BIOPATTERN
viability
14 ID_INCONCLUSIVE Inconclusive Identification
15 ID_UNIDENTIFIED_ORG Unidentified organism
16 ID_CONFIDENCE_NONE _
Terminated disposable - no organism suspension
17 ID_TERMINATED_DISPOSABLE
detected
18 ID_DISPOSABLE_ERROR DISPOSABLE ERROR - Missing data
19 ID_CONTROL_FAIL Internal Control failed

Expert (antibiogram) confidence code

Key Confidence Code Confidence Label

1 EXPERT_CONSISTENT Consistent expertise
2 EXPERT_INCONSISTENT Inconsistent expertise
3 EXPERT_CORRECTED Consistent expertise with correction
4 EXPERT_UNEXPERTIZED Expert analysis not performed
5 EXPERT_UNKNOWN Unknown
6 EXPERT_PRELIMINARY Preliminary expert results

Offline test codes and values

The following list provides some offline tests that can be received by MYLA® with their default
code and their positive and negative result codes. This list is not exhaustive.

Code mapping can be defined on MYLA® if the LIS does not use the default code.

(Offline) test code (Offline) Test name Pos value Neg value
BLA Beta-Lactamase Pos Neg
ESB ESBL Pos Neg
HLG Gentamicin High Level (synergy) SYN-R SYN-S
HLK Kanamycin High Level (synergy) SYN-R SYN-S
HLS Streptomycin High Level (synergy) SYN-R SYN-S
ICR Inducible Clindamycin Resistance Pos Neg
OXS Oxacillin Screen R S
OXSF Cefoxitin Screen Pos Neg
VAS VRSA Screen Pos Neg

161150-1283 -D 11-22 MYLA® V4.9

MYLA® Messages Identification Additional Information

MYLA® Messages Identification

The aim of this section is to help the LIS identify the system that produces the result that
triggers the message sent by MYLA®.

Instrument System

Name Type Serial Number Test Group

(Field 171 & 189) (Field 172 & 190) (Field 191) Code
(BMX: id, tj) (BMX: ii, tj) (BMX: is) (Field 176)
(BMX: it)
Concatenation of 2 fields
Name of BACT (comport1.comport_
configured in BACT instrument1.id)
driver property file: bta configured in BACT
BACT/ALERT® 3dcomm.properties (all in lower case) driver property file:
BC
bta for consolidated 3dcomm.properties.
results bta for consolidated
results
BACT/ALERT® Name of the
SIMON VIRTUO Bank Identifier BC
VIRTUO™ VIRTUO™ unit
VITEK® 2 Com- Facility name managed Instrument serial number
pact / identifica- on VITEK® 2 System V2S managed on VITEK® 2 ID
tion PC System PC
Facility name managed Instrument serial number
VITEK® 2 Com- on VITEK® 2 System V2S managed on VITEK® 2 SU
pact / antibiogram PC System PC
Instrument name Instrument serial number
VITEK® MS (managed on MSID (managed on acquisition ID
acquisition station) station)
MYLA® code
Manual identifica- MANUAL MANUAL-ID ID
corresponding to
tion method used
MYLA® code
Manual antibio- MANUAL MANUAL-AST SU
corresponding to
gram method used

161150-1283 -D 11-23 MYLA® V4.9

12 MESSAGE SAMPLE

NOTE: In some examples below the Patient and Specimen information is not fully present to simplifiy
the document. In a real connection, the Patient and Specimen information should be
repeated in all messages sent to MYLA®. If information sent in a message is not present in a
second one, the data will be set to blank in MYLA®.

Basic Request with Test Group

A basic request with the test group to direct the MYLA® workflow is described below.

XML
File: request_basic_testGroup_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>G406270/A</patientIdentifier>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>id12345</specimenIdentifier>
</specimen>
<test>
<universalIdentifier>
<testGroupCode>SU</testGroupCode>
</universalIdentifier>
</test>
</testOrder>
</request>
</lisMessage>

BMX format
File: request_basic_testGroup_RS232.txt

Blocks: Header, Patient, Specimen, Footer.

mtmpr|itSU|piG406270/A|si|ciid12345|zz|

CLSI LIS2-A2 – Not Applicable

161150-1283 - D 12-1 MYLA® V4.9

Basic Request with Specimen Type Message Sample

HL7

File: request_basic_TestGroup.hl7

MSH|^~\&|LISName|LIS|myla|BMX|20191018170201||OML^O33^OML_O33|MSG-20191018-17020
1-0000|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|||PID130000
PV1||O
SPM|1|SPE130001||URC^Urine clean catch^99BMx|||||||P^^HL70369||||||20160804000100
SAC|||SPE130001
ORC|NW||||||||20191018153553
TQ1|||||||||R^^HL7048
OBR|1|AWOS130001||ID^ID^99BMx

Basic Request with Specimen Type

A basic request with the sample type to direct the MYLA® workflow is described below.

XML
File: request_basic_sampleType_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>G406270/A</patientIdentifier>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>id12345</specimenIdentifier>
<specimenType>Blood</specimenType>
</specimen>
</testOrder>
</request>
</lisMessage>

BMX Format
File: request_basic_sampleType_RS232.txt

Blocks: Header, Patient, Specimen, Footer.

mtmpr|piG406270/A|si|ciid12345|ctBlood|zz|

161150-1283 - D 12-2 MYLA® V4.9

Basic Request with Specimen Type Message Sample

CLSI LIS2-A2
File: request_basic_sampleType_astm.txt

H|\^&||||||||||||20191121085502
P|1|G406270/A
O|1|id12345|||||||||||||Blood
L|1|F

HL7
File: request_basic_sampleType.hl7

MSH|^~\&|LIS|LAB|MYLA|BMX|20190524170201||OML^O33^OML_O33|MSG-20190524-170201-
0000|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|||PID130000
PV1||O
SPM|1|SPE130001||URC^Urine clean catch^99BMx|||||||P^^HL70369||||||2016080400010
0
SAC|||SPE130001
ORC|NW||||||||20191018153553
TQ1|||||||||R^^HL7048
OBR|1|AWOS130001||ID^ID^99BMx

161150-1283 - D 12-3 MYLA® V4.9

Non Basic Request (patient and specimen info) Message Sample

Non Basic Request (patient and specimen info)

XML
File: request_patient_specimen_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>G406270/A</patientIdentifier>
<patientVisitNumber>G406270_123</patientVisitNumber>
<lastName>Robinson, Adele</lastName>
<physicianIdentifier>Dr. Robert</physicianIdentifier>
<location>9EAST</location>
<freeTextFields>
<item>
<code>w1</code>
<name>G406270 123</name>
</item>
</freeTextFields>
<comment>
<code>Age=7</code>
<text></text>
</comment>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>1</specimenIdentifier>
<collectedDateTime>20090302105501</collectedDateTime>
<specimenType>blood</specimenType>
<specimenSource>Left Arm</specimenSource>
<comment>
<code>S GN</code>
<text></text>
</comment>
</specimen>
</testOrder>
</request>
</lisMessage>

161150-1283 - D 12-4 MYLA® V4.9

Request Allowing Optimum Use of Statistical Reporting Module Message Sample

BMX Format
File: request_patient_specimen_RS232.txt

Blocks: Header, Patient, Specimen, Footer.

mtmpr|piG406270/A|pvG406270_123|pnRobinson, Adele|pl9EAST|ppDr. Robert|pcAge=7|pt|w1G406270

123|si|ssLeft Arm|s12009/03/02|s210:55:01|scS GN|sn|ci1|ctblood|zz|

CLSI LIS2-A2 – Not Applicable

HL7

File: request_patient_specimen.hl7

MSH|^~\&|LIS|LAB|MYLA|BMX|20190524170201||OML^O33^OML_O33|MSG-20190524-17
0201-0378|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|||PID131001||Marie^Martin^^^^^L|||F|||Duport^^Lyon^^69000^France|||||
M|
PV1||U|Oncto Service^ROOM13^^Institution code^^^^^Room 13^||||DOCT001^Dr
Att||||||||||||PIV130001
SPM|1|SPE131001||WB^Blood^99BMx|||CATH^Catheterized^99BMx|LAC^Left Ante-
rior Chest^99BMx|||P^Patient^HL70369||||||20191018090803|20191018090703
SAC|||SPE135001
ORC|NW||||||||20190614153553
TQ1|||||||||R^^HL7048
OBR|1|AWOS131001||BC^Blood Culture^99BMx||||||COID4589^BILL||||||OPID0001
^Dubol|0033689745612|

Request Allowing Optimum Use of Statistical Reporting Module

A full request with patient and specimen information allowing the creation of meaningful
statistical reports using the dedicated MYLA® module is described below.

161150-1283 - D 12-5 MYLA® V4.9

Request Allowing Optimum Use of Statistical Reporting Module Message Sample

XML
File: request_optimal_for_stat_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>833224778</patientIdentifier>
<lastName>Adam</lastName>
<firstName>David</firstName>
<birthdate>19201008</birthdate>
<sex>M</sex>
<hospitalService>surg</hospitalService>
<hospitalInstitution>HCL</hospitalInstitution>
<location>109</location>
<admissionDate>20130714</admissionDate>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>130718002</specimenIdentifier>
<specimenNature>catheter</specimenNature>
<specimenType>blood</specimenType>
<specimenSource>jugular</specimenSource>
<collectedDateTime>20130718083213</collectedDateTime>
<collector>js</collector>
<collectorName>John Smith</collectorName>
</specimen>
</testOrder>
</request>
</lisMessage>

BMX Format
File: request_optimal_for_stat_RS232.txt

Blocks: Header, Patient, Specimen, Footer.

mtmpr|pi833224778|pnAdam|qcDavid|pb1920/10/08|psM|pxsurg|qiHCL|pl109|pa
2013/07/14|si|ci130718002|stcatheter|ctblood|ssjugular|s12013/07/18|s208:
32:13|dhjs|dlJohn Smith|zz|

161150-1283 - D 12-6 MYLA® V4.9

Request Allowing Optimum Use of Statistical Reporting Module Message Sample

CLSI LIS2-A2
File: request_optimal_for_stat_astm.txt

H|\^&|||SENDERNAME|||||BACT/ALERT||P|1|20100128164942
P|1|833224778|||Adam^David||19201008|M|||||||||||||||20130714||109|||||su
rg|||HCL|
O|1|130718002||^^^BC^BSA^SA023023|||20130718083213|||js^john
Smith|||||blood^jugular|
L|1|F

HL7
File: request_optimal_for_stat.hl7

MSH|^~\&|LIS|LAB|MYLA|BMX|20190524170201||OML^O33^OML_O33|MSG-20190524-
170201-0377|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|||PID132001||Bill^Arbre^^^^^L||20190830|F|||Duport^^Lyon^^69000^Franc
e|||||M|
NTE|1|A|Comment about the patient|RE^^HL70364
PV1||U|Oncto Service^ROOM21^^Institution code^^^^^Room 21^||||DOCT001^Dr
Att||||||||||||PIV137001
SPM|1|SPE132001||WB^Blood^99BMx|||CATH^Catheterized^99BMx|LAC^Left Ante-
rior Chest^99BMx|||P^Patient^HL70369|||patient traveled on epidemic zone
||BIO^^99BMx|20191018090803|20191018090703
SAC|||SPE132001
ORC|NW||||||||20191018153553||||Collection Service^Room005^^Collection
Institution code^^^^^Collection Room 5|
TQ1|||||||||R^^HL7048
OBR|1|AWOS132001||SU^Susceptibility test^99BMx||||||COID4589^BILL||||||OP
ID0001^Dubol|0033689745612

161150-1283 - D 12-7 MYLA® V4.9

Message from LIS with an identification result only Message Sample

Message from LIS with an identification result only

XML

NOTE:This message only contains a result, not a request.

File: request_offline_id_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>GX-78584</patientIdentifier>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>id12345</specimenIdentifier>
</specimen>
<isolateNumber>2</isolateNumber>
<test>
<universalIdentifier>
<testGroupCode>ID</testGroupCode>
<testIdentifier>Identification</testIdentifier>
<testName>Identification</testName>
</universalIdentifier>
<result>
<value>
<identification>
<significantTaxon>
<code>staaur</code>
<name>Staphylococcus aureus</name>
</significantTaxon>
</identification>
</value>
</result>
</test>
</testOrder>
</request>
</lisMessage>

NOTE:Using the testGroupCode tag for the Identification is not mandatory but recommended.

BMX Format
File: request_offline_id_RS232.txt

161150-1283 - D 12-8 MYLA® V4.9

Message from LIS with an identification result only Message Sample

Blocks: Header, Patient, Specimen, Identification, Footer.

mtmpr|piGX-78584|si|ciid12345|t12|o1escool|o2Escherichia coli|o999|oiID_-
EXCELLENT|zz|

CLSI LIS2-A2 - Not Applicable

HL7
File: request - with ID Offline only.hl7

MSH|^~\&|LISNAME|LIS|myla|BMX|20191020170201||OML^O33^OML_O33|MSG-20191020-13200
1-0001|P|2.5.1||||||UNICODE UTF-8
PID|||PID132001||Bill^Arbre^^^^^L||20190830|F|||Duport^^Lyon^^69000^France||3358
975466|0014||M|
NTE|1|A|Comment about the patient|RE^^HL70364
PV1||U|Oncto Service^ROOM21^^Institution code^^^^^Room 21^||||DOCT001^Dr Att|||||
|||||||PIV132001
SPM|1|2|SPE132001|WB^Blood^99BMx|||CATH^Catheterized^99BMx|LAC^Left Anterior Che
st^99BMx|||P^Patient^HL70369|||||BIO^^99BMx|20191012090803|20191012090703
SAC|||2|SPE132001|
ORC|PR||||||||20191020170201
TQ1|||||||||R^^HL7048
OBR|1|PROR167001||ID^ID^99BMx|
OBX|1|CE|ID^ID^99BMx||strcc^Streptococcus^99BMx|||N^Normal^HL70078|||F||||||||08
041620112634||||||||||SCI

161150-1283 - D 12-9 MYLA® V4.9

Message from LIS with a (presumptive) identification result only Message Sample

Message from LIS with a (presumptive) identification result only

XML

NOTE:This message only contains a result, not a request.

File: request_offline_id_presumptive_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>GX-78584</patientIdentifier>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>id12345</specimenIdentifier>
</specimen>
<isolateNumber>2</isolateNumber>
<test>
<universalIdentifier>
<testGroupCode>ID</testGroupCode>
<testIdentifier>Identification</testIdentifier>
</universalIdentifier>
<result>
<value>
<identification>
<identificationConfidenceCode>ID_PRESUMPTIVE</identificationConfidenceCode>
<significantTaxon>
<code>Suspected pneumonia</code>
<name>Suspected pneumonia</name>
</significantTaxon>
</identification>
</value>
</result>
</test>
</testOrder>
</request>
</lisMessage>

161150-1283 - D 12-10 MYLA® V4.9

Message from LIS with an AST Result only Message Sample

BMX Format
File :request_offline_id_presumptive_RS232.txt

mtmpr|piPID3001002|si|ciSID3001002|t11|o1escool|o2Escherichi-
acoli|oiID_PRESUMPTIVE|zz|

CLSI LIS2-A2 - Not Applicable

HL7 - Not Supported

Message from LIS with an AST Result only

XML

NOTE:This message only contains a result, not a request.

File: result_ast_only_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20150316102700</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>V789AB</patientIdentifier>
<patientVisitNumber>V789AB</patientVisitNumber>
<lastName>MARTIN</lastName>
<firstName>Marie</firstName>
<birthdate>19800710</birthdate>
<sex>F</sex>
<address1>Paris</address1>
<telephone>0474951234</telephone>
<admissionDate>20150812</admissionDate>
<hospitalService>emerg</hospitalService>
<hospitalServiceText>Emergency</hospitalServiceText>
<hospitalInstitution>stcha</hospitalInstitution>
<hospitalInstitutionText>St. Charles</hospitalInstitutionText>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>007124</specimenIdentifier>
<collectedDateTime>20150707112700</collectedDateTime>

161150-1283 - D 12-11 MYLA® V4.9

Message from LIS with an AST Result only Message Sample

<specimenType>urine</specimenType>
</specimen>
<isolateNumber>5</isolateNumber>
<test>
<universalIdentifier>
<testGroupCode>ID</testGroupCode>
<testIdentifier>ID</testIdentifier>
</universalIdentifier>
<result>
<value>
<identification>
<identificationConfidenceCode>ID_EXCELLENT</identificationConfi-
denceCode>
<significantTaxon>
<code>ECO</code>
<name>Escherichia coli</name>
</significantTaxon>
</identification>
<ast>
<antibiotic>
<code>TIC</code>
<highMic/>
<category>R</category>
<nonExpertCategory>R</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>TCC</code>
<highMic/>
<category>R</category>
<nonExpertCategory>R</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>TZP</code>
<highMic/>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>MEM</code>
<highMic/>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>IPM</code>
<highMic/>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>CLO</code>
<highMic/>
<category>-S</category>
<nonExpertCategory>-S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>TM</code>
<highMic/>

161150-1283 - D 12-12 MYLA® V4.9

Message from LIS with an AST Result only Message Sample

<category>-S</category>
<nonExpertCategory>-S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>RA</code>
<highMic/>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>AN</code>
<highMic/>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>CIP</code>
<highMic>
<micSign>&lt;=</micSign>
<micValue>1</micValue>
</highMic>
<category/>
<nonExpertCategory/>
</antibiotic>
</ast>
</value>
</result>
</test>
</testOrder>
</request>
</lisMessage>

BMX Format
File: request_with_ast_offline_only_rs232.txt

mtmpr|piV789AB|pvV789AB|pnMARTIN|pb1980/07/10|psF|pxemerg|p3Emergency|pa
2015/08/12|qcMarie|qu0474951234|qeParis|qistcha|qjSt. Charles|si|s12015/
07/07|s211:27:00|ci007124|cturine|t15|o1ECO|o2Escherichia coli|oiID_EXCEL
LENT|ra|a1TIC|a4R|anR|ra|a1TCC|a4R|anR|ra|a1TZP|a4S|anS|ra|a1MEM|a4S|anS|
ra|a1IPM|a4S|anS|ra|a1CLO|a4-S|an-S|ra|a1TM|a4-S|an-S|ra|a1RA|a4S|anS|ra|
a1AN|a4S|anS|ra|a1CIP|a3<=1|a4|an|zz|

CLSI LIS2-A2 - Not Applicable

161150-1283 - D 12-13 MYLA® V4.9

Message from LIS with an AST Result only Message Sample

HL7

File: request - with AST Offline only.hl7

MSH|^~\&|LISNAME|LIS|myla|BMX|20191020170201||OML^O33^OML_O33|MSG-20191020-
132001-0001|P|2.5.1||||||UNICODE UTF-8
PID|||PID132001||Bill^Arbre^^^^^L||20190830|F|||Duport^^Lyon^^69000^France||3358
975466|0014||M|
NTE|1|A|Comment about the patient|RE^^HL70364
PV1||U|Oncto Service^ROOM21^^Institution code^^^^^Room 21^||||DOCT001^Dr
Att||||||||||||PIV132001
SPM|1|2|SPE132001|WB^Blood^99BMx|||CATH^Catheterized^99BMx|LAC^Left Anterior
Chest^99BMx|||P^Patient^HL70369|||||BIO^^99BMx|20191012090803|20191012090703
SAC|||2|SPE132001|
ORC|PR||||||||20191020170201
TQ1|||||||||R^^HL7048
OBR|1|PR0001256||SU^SU^99BMx|
OBX|1|CE|ID^ID^99BMx||esccol^Escherichia coli^99BMx|||N^Nor-
mal^HL70078|||F||||||||08041620112634||||||||||SCI
OBX|2|CE|TIC^iyuiracillin^99BMx|1||||R^Resis-
tant^HL70078|||F||||||||20190830231804||||||||||SCI
OBX|3|NM|IPM^initipmipllin^99BMx|1|5|mm^milliliter^UCUM||S^Suscepti-
ble^HL70078|||F||||||||20190830231804||||||||||SCI
OBX|4|SN|RA^Rifampicin^99BMx|1|<=^0.03|mg/mL^microgram per millili-
ter^UCUM||S^Susceptible|||F||||||||20190830231804||||||||||SCI

161150-1283 - D 12-14 MYLA® V4.9

Full request with offline identification Message Sample

Full request with offline identification

XML

Full request using specimen type dispatching with identification offline result.

File: request_offline_id_with_specimen_type_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>GX-78584</patientIdentifier>
<lastName>Bob Father</lastName>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>id12345</specimenIdentifier>
<specimenType>blood</specimenType>
</specimen>
<isolateNumber>2</isolateNumber>
<test>
<universalIdentifier>
<testGroupCode>ID</testGroupCode>
<testIdentifier>Identification</testIdentifier>
<testName>Identification</testName>
</universalIdentifier>
<result>
<value>
<identification>
<significantTaxon>
<code>staaur</code>
<name>Staphylococcus aureus</name>
</significantTaxon>
</identification>
</value>
</result>
</test>
</testOrder>
</request>
</lisMessage>

161150-1283 - D 12-15 MYLA® V4.9

Full request with offline identification Message Sample

Full request using test group code dispatching with identification offline test result.

File: request_offline_id_with_test_group_code_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>GX-78584</patientIdentifier>
<lastName>Bob Father</lastName>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>id12345</specimenIdentifier>
</specimen>
<isolateNumber>2</isolateNumber>
<test>
<universalIdentifier>
<testGroupCode>SU</testGroupCode>
</universalIdentifier>
</test>
<test>
<universalIdentifier>
<testGroupCode>ID</testGroupCode>
<testIdentifier>Identification</testIdentifier>
<testName>Identification</testName>
</universalIdentifier>
<result>
<value>
<identification>
<significantTaxon>
<code>staaur</code>
<name>Staphylococcus aureus</name>
</significantTaxon>
</identification>
</value>
</result>
</test>
</testOrder>
</request>
</lisMessage>

161150-1283 - D 12-16 MYLA® V4.9

Full request with offline identification Message Sample

BMX Format

Full request with an offline identification

BMX format does not allow messages with the test group code and an offline identification.
Indeed, the test group code will be associated to the offline identification and not as a request.

Two different messages must be sent:

· one with the patient information, sample/specimen and test group code information,
· one with the offline identification (with sample/specimen identification to be able to make
the link with the previous message).

NOTE:The order of messages is very important.

First message

Use specimen type dispatching.

File: request_offline_id_spe_first_RS232.txt

Blocks: Header, Test code, Patient, Specimen and isolate number, Footer

mtmpr|piG406270/A|pnFather|qcBob|si|ciid12345|ctblood|t12|zz|

Use test group dispatching.

File: request_offline_id_first_RS232.txt

Blocks: Header, Test code, Patient, Specimen and isolate number, Footer.

mtmpr|itSU|piGX-78584/A|pnFather|qcBob|si|ciid12345|ctblood|t12|zz|

Second Message

Same message for specimen or test group dispatching.

File: request_offline_id_second_RS232.txt

Blocks: Header, Patient, Specimen and isolate number, Identification, Footer.

mtmpr|piGX-78584|si|ciid12345|ctblood|t12|o1escool|o2Escherichia coli|
o999|oiID_EXCELLENT|zz|

CLSI LIS2-A2 – Not Applicable

161150-1283 - D 12-17 MYLA® V4.9

Request Containing Clinical information for MYLA® AST Filter feature Message Sample

HL7

File: request -SU with ID Offline only.hl7

MSH|^~\&|LISName|LIS|myla|BMX|20191018170201||OML^O33^OML_O33|MSG-20191018-
170201-0004|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|||PID167001||Bob^Bug^^^^^L||20110830|F|||Duport^^Lyon^^69000^France|||||S|
NTE|1|A|Comment about the patient|RE^^HL70364
PV1||U|Oncto Service^ROOM54^^Institution code^^^^^Room 54^||||DOCT001^Dr
Att||||||||||||PIV167001
SPM|1|2|SPE167001|WB^Blood^99BMx|||CATH^Catheterized^99BMx|LAC^Left Anterior
Chest^99BMx|||P^Patient^HL70369|||||BIO^^99BMx|20191018090803|20191018090703
SAC|||2|SPE167001
ORC|NW||||||||20191018153553
TQ1|||||||||R^^HL7048
OBR|1|AWOS167001||SU^SU^99BMx||||||BILL01^BILL^Gin||||||orderingPhysicians-
ID1^Dubol|0033689745612
ORC|PR||||||||20191020170201
OBR|2|PROR167001||ID^ID^99BMx|
OBX|1|CE|ID^ID^99BMx||esccol^Escherichia coli^99BMx|||N^Nor-
mal^HL70078|||F||||||||08041620112634||||||||||SCI

Request Containing Clinical information for MYLA® AST Filter feature

The functionality AST Filter allows to delete some drugs in an antibiogram, depending on
several criteria, one of them is the clinical context.

To use the clinical context in a rule definition the following fields have to be correctly filled in:

All "offline" test results information can be used as clinical information in AST Filter rules.

The clinical information must be sent as simple result (offline result). Examples are available in
section "Request Containing an Offline Result":

The clinical information must be sent as simple results. Examples are available in section
Request Containing an Offline Result on page 12-28. In this section, examples contain test
result “Pos” for test code “Bla”. For Myla AST Filter, you are able to send test code and test
result you want and use them in Myla AST Filter rules.

Example: to send pregnant information with code “Pre” and result values "YES" or "NO", so in
the messages examples replace “Bla” by “Pre” and "Pos" by “YES” or “NO”. Again, the test
codes and the test values are free text and will be usable as is in the rules of the Myla AST
Filter.

161150-1283 - D 12-18 MYLA® V4.9

Request Containing a Blood Culture Result Message Sample

Request Containing a Blood Culture Result

This message is one with a result coming from the LIS.

The result part of the message must contain at least:

• result value POS/NEG

• date of result field “dateResultDetermined”
• time to detection, field “timeToDetectionInHours”

NOTE: This message does not contain a request but only a result that will be associated with a
request that was previously sent.

In “Myla” dispatching mode, it is not possible to differentiate a message with a result only from
a message with a request and a result. In this case, MYLA® will consider the message as a
request and the number of BACT/ALERT® bottles to load will be incremented.

XML

NOTE: To send several bottle results, a different testIdentifier has to be sent for each bottle.

161150-1283 - D 12-19 MYLA® V4.9

Request Containing a Blood Culture Result Message Sample

File: request_offline_blood_culture_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>PTSC77002</patientIdentifier>
<lastName>LastName</lastName>
<firstName>FirstName</firstName>
<birthdate>20130606</birthdate>
<sex>M</sex>
<physicianIdentifier>ATD</physicianIdentifier>
<physicianName>ATTENDING DOCTOR</physicianName>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>STSC77002</specimenIdentifier>
<collectedDateTime>20090302105501</collectedDateTime>
<specimenType>blood</specimenType>
<specimenSource>Left Arm</specimenSource>
</specimen>
<test>
<universalIdentifier>
<testGroupCode>BC</testGroupCode>
<testIdentifier>BC_GENERIC_AE</testIdentifier>
</universalIdentifier>
<result>
<value>
<bloodCulture>
<dateResultDetermined>20160310121242</dateResultDeter-
mined>
<timeToDetectionInHours>120</timeToDetectionInHours>
<result>Neg</result>
</bloodCulture>
</value>
</result>
</test>
<test>
<universalIdentifier>
<testGroupCode>BC</testGroupCode>
<testIdentifier>BC_GENERIC_AN</testIdentifier>
</universalIdentifier>

161150-1283 - D 12-20 MYLA® V4.9

Request Containing a Blood Culture Result Message Sample

<result>
<value>
<bloodCulture>
<dateResultDetermined>20160306141242</dateResultDeter-
mined>
<timeToDetectionInHours>11</timeToDetectionInHours>
<result>Pos</result>
</bloodCulture>
</value>
</result>
</test>
</testOrder>
</request>
</lisMessage>

BMX Format
File: request_offline_blood_culture_RS232.txt

Blocks: Header, Patient, Specimen, Blood Culture, Footer.

mtmpr|piG406270/A|si|ciid12345|t12|rcPos|zz|

CLSI LIS2-A2 – Not Applicable

HL7
File: request_offline_blood_culture.hl7

MSH|^~\&|LIS|LAB|MYLA|BMX|20190524170201||OML^O33^OML_O33|MSG-20190524-170201-
0004|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|||PID133001||Karl^Bill^^^^^L||20110830|F|||Duport^^Lyon^^69000^France|||||S
NTE|1|A|Comment about the patient|RE^^HL70364
PV1||U|Oncto Service^ROOM54^^Institution code^^^^^Room 54^||||DOCT001^Dr
Att||||||||||||PIV133001
SPM|1|2|SPE133001|WB^Blood^99BMx|||CATH^Catheterized^99BMx|LAC^Left Anterior Ches
t^99BMx|||P^Patient^HL70369|||patient traveled on epidemic zone||BIO^^99BMx|2019
0612090703
SAC|||2|SPE133001
ORC|NW||||||||20190614153553
TQ1|||||||||R^^HL7048
OBR|1|AWOS133001||SU^Susceptibility test^99BMx||||||BILL01^BILL||||||orderingPhy-
siciansID1^Dubol|0033689745612
ORC|PR
OBR|1|""||BC^Blood Culture^99BMX|
OBX|1|CE|BC^Blood Culture^99BMX||Pos^Positive^99BMX||||||F|||20150825231804|

161150-1283 - D 12-21 MYLA® V4.9

Request Containing a Gram Staining Result Message Sample

Request Containing a Gram Staining Result

This message is one with a result coming from the LIS.

NOTE: This message does not contain a request but only a result that will be associated with a
request that was previously sent.

XML

NOTE: The GRAM format is not the same with BCI Link and BCI Connect. Both formats are decribed
below.

Format Only Supported by BCI Link

File: request_offline_gram_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>G406270/A</patientIdentifier>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>id12345</specimenIdentifier>
</specimen>
<isolateNumber>2</isolateNumber>
<test>
<universalIdentifier>
<testGroupCode>SC</testGroupCode>
<testIdentifier>gram</testIdentifier>
</universalIdentifier>
<result>
<value>
<gramStainingTest>
<shapeCode>cocci</shapeCode>
<gramColorCode>positive</gramColorCode>
</gramStainingTest>
</value>
</result>
</test>
</testOrder>
</request>
</lisMessage>

161150-1283 - D 12-22 MYLA® V4.9

Request Containing a Gram Staining Result Message Sample

New Format Only Supported by BCI Connect from MYLA® V4.7

Only available from Myla 4.7.1. It is not possible for the LIS to transmit GRAM result to MYLA
4.7.0 and BCI Connect.

File: request_offline_gram_astm_BCIC.xml
<?xml version="1.0" encoding="UTF-8"?>
<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>G406270/A</patientIdentifier>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>id12345</specimenIdentifier>
</specimen>
<isolateNumber>2</isolateNumber>
<test> <!-- Request for identification test -->
<universalIdentifier>
<testGroupCode>ID</testGroupCode>
</universalIdentifier>
</test>
<test> <!-- test result-->
<universalIdentifier>
<testGroupCode>SC</testGroupCode>
<testIdentifier>GRAM</testIdentifier>
</universalIdentifier>
<result>
<resultID>
<resultTestCode>MORPH</resultTestCode>
<resultTestName>Shape</resultTestName>
</resultID>
<value>
<testResult>
<valueType>CE</valueType>
<observationValue>COCCI</observationValue>
<observationName>Cocci</observationName>
</testResult>
</value>
</result>
<result>
<resultID>
<resultTestCode>COLOR</resultTestCode>
<resultTestName>color</resultTestName>
</resultID>
<value>
<testResult>
<valueType>CE</valueType>
<observationValue>VARIABLE</observationValue>
<observationName>Variable</observationName>
</testResult>
</value>
</result>
</test>
</testOrder>
</request>
</lisMessage>

161150-1283 - D 12-23 MYLA® V4.9

Request Containing a Gram Staining Result Message Sample

Codes Supported by MYLA for Gram Staining Results

<testGroupCode>, possible value:

- SC

<testIdentifier>, possible value:

- GRAM

<resultTestCode>, possible values:

- MORPH

- GRAM_COLOR

- ARRANGEMNT

- QUANTITY

<observationValue> and <observationName> are free.

BMX Format

Legacy Format Supported by BCI Link and BCI Connect

For BCI Connect, it is recommended to use the new format described in the following section.

File: request_offline_gram_BCI_Link_RS232.txt

Blocks: Header, Patient, Specimen, Gram Staining, Footer.

mtmpr|piG406270/A|si|ciid12345|t12|etcocci|eupositive|zz|

New Format Only Supported by BCI Connect from MYLA® V4.7

File: request_offline_gram_BCI_Connect_RS232.txt

Blocks: Header, Patient, Specimen, Gram Staining, Footer.

mtmpr|piG406270/A|si|ciid12345|t12|ta|itSC|rtGRAM|ga|gcMORPH|gsBMX99|vtCE
|ovCOCCI|oncocci|gcCOLOR|gsBMX99|vtCE|ovVARIABLE|onVariable|zz|

NOTE:Only available from MYLA 4.7.1. It is not possible for the LIS to transmit GRAM result to MYLA
4.7.0 and BCI Connect.

CLSI LIS2-A2 – Not Applicable

161150-1283 - D 12-24 MYLA® V4.9

Request with optional DisposableIdentifier and optional expected duration Message Sample

HL7
File: request -ID with GRAM offline.hl7

MSH|^~\&|LIS|LAB|MYLA|BMX|20190524170201||OML^O33^OML_O33|MSG-20190524-
170201-0008|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|||PID150001||Karl^Bill^^^^^L||20110830|F|||Duport^^Lyon^^69000^France
|||||S|
NTE|1|A|Comment about the patient|RE^^HL70364
PV1||U|Oncto Service^ROOM54^^Institution code^^^^^Room 54^||||DOCT001^Dr
Att||||||||||||PIV134001
SPM|1|2|SPE150001|UR^Urine^99BMx|||||||P^Patient^HL70369||||||20190612090
703
SAC|||2|SPE150001
ORC|NW||||||||20190614153553
TQ1|||||||||R^^HL7048
OBR|1|AWOS150001||ID^Identification
test^99BMx||||||BILL01^BILL^Gin||||||Dr0001^Dubol^Jean|0033689745612
ORC|PR
OBR|2|AWOSOFF0001||GRAM^Gram Staining^99BMx|
OBX|1|CE|MORPH^Gram Morph^99BMx||COCI^Coci shape^99BMx|||N^Nor-
mal^HL70078|||F||||||||||||||||||SCI

Request with optional DisposableIdentifier and optional expected duration

In this example, a request is sent with the Blood culture systems disposable identifier.
These examples contain optional fields "disposable identifier", "expected duration" ( (Eg.
Expected incubation time for the blood culture). When "expected duration" is sent without
disposable identifier (bottle ID), the value of the "expected duration" will be applied to all
bottles linked to the specimen identifier.

NOTE: "Expected Duration" will be sent to BACT/ALERT® Virtuo and NOT to BACT/ALERT® 3D.

161150-1283 - D 12-25 MYLA® V4.9

Request with optional DisposableIdentifier and optional expected duration Message Sample

XML
File: request_with_bacT_bottle_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>PTSC50001</patientIdentifier>
<lastName>LastName</lastName>
<firstName>FirstName</firstName>
<birthdate>20130606</birthdate>
<sex>M</sex>
<address1>Main Street</address1>
<physicianIdentifier>ATD</physicianIdentifier>
<physicianName>ATTENDING DOCTOR</ physicianName >
<location>ROOM70</location>
<hospitalService>WARD70</ hospitalService >
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>STSC50001</specimenIdentifier>
<collectedDateTime>20090302105501</collectedDateTime>
<specimenType>blood</specimenType>
<specimenSource>Left Arm</specimenSource>
</specimen>
<test>
<universalIdentifier>
<testGroupCode>BC</testGroupCode>
</universalIdentifier>
<disposableIdentifier>ARG50001</disposableIdentifier>
</test>
<test>
<universalIdentifier>
<testGroupCode>BC</testGroupCode>
</universalIdentifier>
<expectedDuration>10</expectedDuration>
<disposableIdentifier>NRG50001</disposableIdentifier>
</test>
</testOrder>
</request>
</lisMessage>

NOTE: As shown in this example, if you work with the specimenType dispatching mode (Dispatching
Rules on page 11-11), you must add a “universalIdentifier” tag to be compliant with the XML
schema.

161150-1283 - D 12-26 MYLA® V4.9

Request with optional DisposableIdentifier and optional expected duration Message Sample

BMX Format
File: request_with_bacT_bottle_RS232.txt

Blocks: Header, Patient, Specimen, Order/Result, Footer.

mtmpr|piG406270/A|pvG406270 123|pl9EAST|ppDr. Robert|si|ssLeft Arm|s12009

/03/02|s210:55:01|ci1|ctblood|tbSA023023|ol10|zz|

CLSI LIS2-A2
File: request_with_bacT_bottle_astm.txt

H|\^&|||SENDERNAME|||||BACT/ALERT||P|1|20100128164942
P|1|G406270/A||G406270_123|||||||||Dr. Robert||||||||||||9EAST
O|1|1||^^^BC^BSA^SA023023^10|||20090302105501||||||||blood^Left Arm
L|1|F

NOTE: To send several bottle IDs, you can:

• Send several messages, one per bottle ID. In the first message, you have to put all the
patient and specimen information, in the following messages you can just put the IDs (or
all the information).
• Use a repeat delimiter on the Universal Test ID of the Order (File:
request_with_bacT_bottle_repeat_on_845_astm.txt):
H|\^&|||SENDERNAME|||||BACT/ALERT||
P|1|20100128164942P|1|G406270/A||G406270_123|||||||||Dr. Rob-
ert||||||||||||9EAST
O|1|1||^^^BC^BSA^SA023023\^^^BC^BSN^SN021883|||20090302105501||||||||bloo
d^Left ArmL|1|F
• Use several Result records (File: request_with_bacT_bottle_r_records_astm.txt):
H|\^&|||SENDERNAME|||||BACT/ALERT||
P|1|20100128164942P|1|G406270/A||G406270_123|||||||||Dr. Rob-
ert||||||||||||9EAST
O|1|1|||||20090302105501||||||||blood^Left Arm
R|1|^^^BC^BSA^SA 023023
R|2|^^^BC^BSN^SN021883L|1|F

NOTE: On the Universal Test ID, the LIS can send more components than shown in these examples.
Extra components will be silently ignored by MYLA®.

HL7
Blood culture request can contain only one bottle ID. To send several Bottle ID it's required to
send several messages. Several Bottle ID can be attached to the same specimen ID.

161150-1283 - D 12-27 MYLA® V4.9

Request Containing an Offline Result Message Sample

File: request_with_bacT_bottle.hl7

MSH|^~\&|LIS|LAB|MYLA|BMX|20190524170201||OML^O33^OML_O33|MSG-20190524-
170201-0101|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|||PID135001||Jane^Care^^^^^L||19781212|F|||Duport^^Lyon^^69000^France
|||||S|
PV1||E|Oncto Service^ROOM300^^Institution code^^^^^Room
300^||||DOCT001^Dr Att||||||||||||PIV135001
SPM|1|SPE135001||WB^Blood^99BMx|||CATH^Catheterized^99BMx|LAC^Left Ante
rior Chest^99BMx|||P^Patient^HL70369|||||||20190929153553
SAC|||SNP458978^BOTTLE||||||
ORC|NW||||||||20190930153553
TQ1|1||C|||10^d&Expected duration in day&UCUM|||R^Routine^99LIS1
OBR|1|AWOS135001||BC^Blood culture^99BMx||||||BILL01^BILL||||||OPID3^Dubo
l|0033689745612^^PH|

Request Containing an Offline Result

NOTE: This message does not contain a request but only a result that will be associated with a
request that was previously sent.

NOTE: Beta-Lactamase results will only be sent to VITEK® 2 if the “isolateNumber” is present in the
message and if the MYLA® system never received a request for this sample without an isolate
number.

XML

Format Supported by BCI Link and BCI Connect

For BCI Connect, it is recommended to use new format described in the following section.

161150-1283 - D 12-28 MYLA® V4.9

Request Containing an Offline Result Message Sample

File: request_offline_offline_BCI_Link_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>G406270/A</patientIdentifier>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>id12345</specimenIdentifier>
</specimen>
<isolateNumber>2</isolateNumber>
<test>
<universalIdentifier>
<testIdentifier>Bla</testIdentifier>
<testName>Beta-Lactamase</testName>
</universalIdentifier>
<result>
<value>
<offlineTest>
<resultCode>Pos</resultCode>
</offlineTest>
</value>
</result>
</test>
</testOrder>
</request>
</lisMessage>

161150-1283 - D 12-29 MYLA® V4.9

Request Containing an Offline Result Message Sample

New Format Only Supported by BCI Connect from MYLA® V4.7

File: request_offline_offline_BCI_Connect_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>G406270/A</patientIdentifier>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>id12345</specimenIdentifier>
</specimen>
<isolateNumber>2</isolateNumber>
<test> <!-- Request for identification test -->
<universalIdentifier>
<testGroupCode>ID</testGroupCode>
</universalIdentifier>
</test>
<test> <!-- test result-->
<universalIdentifier>
<testGroupCode>SC</testGroupCode>
<testIdentifier>Bla</testIdentifier>
</universalIdentifier>
<result>
<resultID>
<resultTestCode>Bla</resultTestCode>
</resultID>
<value>
<testResult>
<valueType>CE</valueType>
<observationValue>POS</observationValue>
<observationName>Positive</observationName>
</testResult>
</value>
</result>
</test>
</testOrder>
</request>
</lisMessage>

NOTE: The <disposableIdentifier> field is now transmited by BCI Connect to MYLA®. This is
particularly useful for a blood culture with offline results.

161150-1283 - D 12-30 MYLA® V4.9

Request Containing an Offline Result Message Sample

BMX Format

Format Supported by BCI Link and BCI Connect

For BCI Connect, it is recommended to use the new format described in the following section.

File: request_offline_offline_BCI_Link_RS232.txt

Blocks: Header, Patient, Specimen, Offline test result, Footer.

mtmpr|piG406270/A|si|ciid12345|t12|ba|b1Bla|b2Beta Lactamase|b3Pos|zz|

New Format Only Supported by BCI Connect from MYLA® V4.7

File: request_offline_offline_BCI_Connect_RS232.txt

Blocks: Header, Patient, Specimen, Offline test result, Footer.

mtmpr|piG406270/A|si|ciid12345|t12|ta|itSC|rtBla|ga|gcBla|gsBMX99|vtCE|ov
POS|onPositive|zz|

CLSI LIS2-A2 – Not Applicable

HL7
In HL7 Offline test can be send in request message with or without order. An offline test is
composed of three segments:

ORC

OBR

{OBX} [1..*]

ORC-1 must be set to PR value ( Previous result).

The OBR-2 is mandatory but can be set to NULL ("").

The OBR can be follow by several OBX, one per result.

The static structure of request with one order an one offline test is:

ORC ( ORC-1 = NW )

OBR

ORC ( ORC-1 = PR )

OBR

{OBX} [1..*]

161150-1283 - D 12-31 MYLA® V4.9

Result for Blood Culture Message Sample

NOTE: The ORC/OBR for order (ORC-1=NW must be placed in first).

NOTE: If the message contains only offline test ORC-1=PR, the acknowledgment message will not
contain any ORC segment.

File: request -ID with BLA offline.hl7

MSH|^~\&|LIS|LAB|MYLA|BMX|20190524170201||OML^O33^OML_O33|MSG-20190524-
170201-0018|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|||PID134001||Karl^Bill^^^^^L||20110830|F|||Duport^^Lyon^^69000^France
|||||S|
NTE|1|A|Comment about the patient|RE^^HL70364
PV1||U|Oncto Service^ROOM54^^Institution code^^^^^Room 54^||||DOCT001^Dr
Att||||||||||||PIV134001
SPM|1|2|SPE134002|UR^Urine^99BMx|||||||P^Patient^HL70369|||||||2019061209
0703
SAC|||2|SPE134002
ORC|NW||||||||20190614153553
TQ1|||||||||R^^HL7048
OBR|1|AWOS134002||ID^Identification test^99BMx||||||BILL01^BILL||||||Dr00
01^Dubol^Jean|0033689745612
ORC|PR
OBR|2|""||BLA^Beta-Lactamase^99BMx|
OBX|1|CE|BLA^Beta-Lactamase^99BMx||POS^Positive^HL70078|||N^Normal^HL7007
8|||F|||||811|||08041620112634||||||||||SCI

Result for Blood Culture

From MYLA® V4.4, blood culture results can contain new optional information:

- Bottle volume

- Bottle traceability information

•Bottle lot number

•Bottle expiration date
•Bottle load date and time
•Bottle unload date and time

The availability of this information depends on 3 criteria:

- Type of instrument: only available on BACT/ALERT Virtuo.

- Type of bottle: required bottles 2D label.

- The value of BCI Software properties field.enabled.volume and

field.enabled.traceability (for BCI Link only).

161150-1283 - D 12-32 MYLA® V4.9

Result for Blood Culture Message Sample

BCI Software properties field.enabled.volume and field.enabled.traceability are set by

default to false. This means that these new fields are not sent to the LIS.

The properties can be modified in the file:

<BCILink>\lib_server\properties\bcinet.properties in the following lines:

### ========== Volume management for Blood Culture
field.enabled.volume=false
# Only AST protocol
field.enabled.traceability =false

- If field.enabled.volume is set to "true", Bottle volume will be sent to the LIS.

- If field.enabled.traceability is set to "true", Bottle lot number, Bottle expiration date, Bottle
start date, Bottle start time, Bottle end date, Bottle end time will be sent to the LIS.

In the CLSI LIS2-A2 result message uploaded to the LIS, the Patient segment only contains
“Patient Identifier” and the Order segment only contains specimen ID and completed date
time.

It is possible to activate the upload of all Patient and Order information. To do so, add the
following 2 properties in the <BCILink>\lib_server\properties\bcinet.properties file.
# To activate Patient full information upload set the following property to false:
bcinet.fmla.astm.translator.params.clsi-lis2.generation.skipDataFieldOnPatient = false

# To activate Order full information upload set the following property to false:
bcinet.fmla.astm.translator.params.clsi-lis2.generation.skipDataFieldOnOrder = false

NOTE:For BCI Connect all parameters are available from configuration screen.

One Bottle Result per Message

XML

File: result_blood_culture_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<aiMessage>
<header>
<senderName>FMLA</senderName>
<processingIdentifier>P</processingIdentifier>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
<instrumentName>BTA-1 Name</instrumentName>
<serialNumber>COM20_1</serialNumber>
</header>
<requestResult>
<patientInformation>
<patientIdentifier>9500000755</patientIdentifier>
<lastName>TDUPONT, TMARIE</lastName>
<sex>U</sex>

161150-1283 - D 12-33 MYLA® V4.9

Result for Blood Culture Message Sample

<admissionDate>20100626</admissionDate>
<dischargeDate>20100626</dischargeDate>
<location>100</location>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>95541204</specimenIdentifier>
<collectedDateTime>20100626095800</collectedDateTime>
<receivedDateTime>20100626100230</receivedDateTime>
<specimenType>Blood</specimenType>
<specimenSource>ABR</specimenSource>
<specimenSourceText>ABR</specimenSourceText>
</specimen>
<test>
<universalIdentifier>
<testGroupCode>BC</testGroupCode>
</universalIdentifier>
<instrumentSectionId>5A55</instrumentSectionId>
<instrumentName>BTA-1 Name</instrumentName>
<instrumentType>bta</instrumentType>
<instrumentSerialNumber>COM20_1</instrumentSerialNumber>
<result>
<value>
<bloodCulture>
<dateResultDetermined>20100705135406</dateResultDetermined>
<timeToDetectionInHours>168.1</timeToDetectionInHours>
<result>Neg</result>
</bloodCulture>
</value>
<abnormalFlags>6</abnormalFlags>
<resultStatus>F</resultStatus>
<startDateTime>20100628134841</startDateTime>
<bmxResultData>
<disposable>
<disposableIdentifier>SNJN2W28</disposableIdentifier>
<reference>BSN</reference>
<disposableType>BOTTLE</disposableType>
<lotNumber>90009</lotNumber>
<expirationDate>20160627</expirationDate>
<disposableStartDateTime>20100628134841</disposableStartDateTime>
</disposable>
<volume>1</volume>
<volumeUnit>mL</volumeUnit>
</bmxResultData>
</result>
</test>
</testOrder>
</requestResult>
</aiMessage>

161150-1283 - D 12-34 MYLA® V4.9

Result for Blood Culture Message Sample

Request Cancelation
Request cancelation messages are supported from MYLA® version 4.8.

The cancel is accepted by MYLA® only if the analysis has not yet started:

• Bottle not loaded yet in blood culture instrument,

• No isolate prepared on VITEK® MS slide or VITEK® 2 card,
• No results available.

To cancel a request, the request message can be resent by the LIS with “Action Code” set
with the value CA.

XML

File: Request-cancel.xml

<?xml version="1.0" encoding="UTF-8"?>

<lisMessage>
<header>
<version>1394-97</version>
<dateTime>20210105101200</dateTime>
</header>
<request>
<patientInformation>
<patientIdentifier>123456</patientIdentifier>
<lastName>Karotz</lastName>
<firstName>Joe</firstName>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>56897</specimenIdentifier>
<collectedDateTime>20210104101200</collectedDateTime>
<specimenType>blood</specimenType>
</specimen>
<isolateNumber>1</isolateNumber>
<test>
<actionCode>CA</actionCode>
<universalIdentifier>
<testGroupCode>SU</testGroupCode>
</universalIdentifier>
</test>
</testOrder>
</request>
</lisMessage>

161150-1283 - D 12-35 MYLA® V4.9

Result for Blood Culture Message Sample

BMX Format

File: Request-cancel-RS232.txt

mtmpr|itSU|pi134657|pnKarotz|qcJoe|si|s12019/06/
18|s210:00:00|ci123456|ctblood|t11|oeCA|zz|

CLSI LIS2-A2

File: request-cancel-ASTM.txt

H|\^&|||SENDERNAME|||||BACT/ALERT||P|1|20100128164942
P|1|G406270/A||G406270_123|||||||||Dr. Robert||||||||||||9EAST
O|1|1||^^^BC^BSA^SA023023^10|||20090302105501||||CA||||blood^Left Arm
L|1|F

HL7

File: Request-cancel.hl7

MSH|^~\&|LISName|LIS|myla|BMX|20191018170201||OML^O33^OML_O33|MSG-
20191018-170201-0004|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|||PID133001||Bob^Bug^^^^^L||20110830|F|||Duport^^Lyon^^69000^France||
|||S|
NTE|1|A|Comment about the patient|RE^^HL70364
PV1||U|Oncto Service^ROOM54^^Institution code^^^^^Room 54||||DOCT001^Dr
Att|DOCT002^Dr Ref|DOCT003^Dr Cons||||||||||PIV133001
SPM|1|2|SPE133001|WB^Blood^99BMx|||CATH^Catheterized^99BMx|LAC^Left Ante-
rior
Chest^99BMx|||P^Patient^HL70369|||||BIO^^99BMx|20191018090803|20191018090
703
SAC|||2|SPE133001
ORC|CA||||||||20191018153553|
TQ1|||||||||R^^HL7048
OBR|1|AWOS133001||SU^SU^99BMx||||||BILL01^BILL^Gin||||||orderingPhysi-
ciansID1^Dubol|0033689745612

BMX Format

File: result_blood_culture_RS232.txt

161150-1283 - D 12-36 MYLA® V4.9

Result for Blood Culture Message Sample

Blocks: Header, Patient, Specimen, Order/Result, Traceability, Blood culture result, Footer.

mtrsl|idBTA-1 Name|iibta|isCOM20_1|itBC|pi9500000755|pnTDUPONT, TMARIE|

psU|pl100|pa2010/06/26|qv2010/06/26|si|ssABR|s5ABR|s12010/06/26|s209:58
:00|s32010/06/26|s410:02:30|ci95541204|Blood|ta|tiBTA-1 Name|tjbta|t4F|
og5A55|ec6|r12010/06/28|r213:48:41|ts|dtBOTTLE|tuBSN|tpSNJN2W28|th2010/
06/28|tk13:48:41|tbSNJN2W28|rd2010/07/05|ru13:54:06|re168.1|rcNeg|zz|

NOTE: The bottle identifier is filled in two fields: tp and tb.

Same example with bottle volume

File: result_blood_culture_with_volume_RS232.txt

Blocks: Header, Patient, Specimen, Order/Result, Traceability, Blood culture result, Footer.

mtrsl|idBTA-1 Name|iibta|isCOM20_1|itBC|pi9500000755|pnTDUPONT,TMARIE|
psU|pl100|pa2010/06/26|qv2010/06/26|si|ssABR|s5ABR|s12010/06/26|s209:58
:00|s32010/06/26|s410:02:30|ci95541204|Blood|ta|tiBTA-1Name|tjbta|t4F|
og5A55|ec6|r12010/06/28|r213:48:41|ts|dtBOTTLE|tuBSN|tpSNJN2W28|th2010/
06/28|tk13:48:41|ro1|rimL|tbSNJN2W28|rd2010/07/05|ru13:54:06|re168.1|rc
Neg|zz|

NOTE: The volume value and unit are filled in two fields: ro and ri.

CLSI LIS2-A2

File: result_blood_culture_astm.txt

H|\^&|||BACT/ALERT^A.00|||||||P|1|20100128164942
P|1|9500000755|9500000755
O|1|95541204
R|1|^^^BC^BSN^SNJN2W28|Neg|||||F|||20100628134841|20100705135406|2C31
R|2|^^^TTD^BSN^SNJN2W28|168.1|||||F|||20100628134841|20100705135406|2C31
L|1|F

NOTE: - Even if possible, it is not recommended to use the MYLA® v1 mode with CLSI LIS2-A2
messages. The messages compatible with legacy are available in 7.9.2.3 CLSI LIS2-A2.
- Result reported date time and result flags can be removed by using “User defined mapping”.

File: result_blood_culture_without_date_time_astm.txt

H|\^&|||BACT/ALERT^A.00|||||||P|1|20100128164942P|1|9500000755
O|1|95541204||||||||||||||||||||20100705135406
R|1|^^^BC^BSN^SNJN2W28|Neg|||6||F|||20100628134841|20100705135406|5A55
R|2|^^^TTD^BSN^SNJN2W28|168.1|||6||F|||20100628134841|20100705135406|5A5
5L|1|F

161150-1283 - D 12-37 MYLA® V4.9

Result for Blood Culture Message Sample

Same example with volume value and traceability segment

File: result_blood_culture_with_tracability_astm.txt

H|\^&|||BACT/ALERT^A.00|||||||P|1|20100128164942
P|1|9500000755
O|1|95541204||||||||||||||||||||20100705135406
R|1|^^^BC^BSN^SNJN2W28|Neg|||6||F|||20100628134841|20100705135406|5A55
R|2|^^^TTD^BSN^SNJN2W28|168.1|||6||F|||20100628134841|20100705135406|5A5
5
R|3|^^^SVM^BFN+^SNJN2W28|1|mL||6||F|||20100628134841|20100705135406|5A55
M|1|SNJN2W28|^BOTTLE^BFN+^90009^20160627^20160618^102930L|1|F

Positive bottle unload with expired bottle flag

File: result_blood_culture_expired_astm.txt

H|\^&|||BACT/ALERT^A.00|||||||P|1|20161108155514
P|1|PATCONF4
O|1|SpeIDESC1020D||||||||||||||||||||20161102093642
R|1|^^^BC^BSA^SAN07VTR|Pos|||EXPIRED^SR||P|||20161020155508|20161020155728|K4
R|2|^^^TTD^BSA^SAN07VTR|0|||EXPIRED^SR||P|||20161020155508|20161020155728|K4
M|1|SAN07VTR|^BOTTLE^BSA^90009^20161019^20161021^154143^20161102^093908|K4L|1|F

HL7

The HL7 result message contains all traceability information including volume.

File: result-BC-bottle1.hl7

MSH|^~\^|myla|BMX|||20190930173833+0200||OUL^R22^OUL_R22|d139e1d8-657c-47
44-ad37-cf78f926db45|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|||PID135001||Jane^Care^^^^^L||19781212|F
PV1|1|U|||||||||||||||||PIV135001
SPM|1|SPE135001||WB^Blood^99BMx|||CATH^Catheterized^99BMx|LAC^Left Ante-
rior Chest^99BMx||
|P^Patient||||||20190929153553
SAC|1||""
OBR|1|AWOS135001||||||||BILL01^BILL||||||OPID3^Dubol|0033689745612
OBX|1|CNE|BC^Blood Culture^99BMx|1|Pos^Positive^99BMx|||N^Normal^99BMx|||
P|||||""||SIMON^biomerieux~1^biomerieux~Instrument 1^biomerieux~I8^bio-
merieux|||||||||||RSLT
INV|BPA^BACT/ALERT® BPA^99BMx|NA^Not Applicable^HL70383|BOTTLE^^99BMx|SN
P458978|||||5||mL^MilliLiter^UCUM|20220131||||21685790004
OBX|2|NM|TTD^Time To Detection^99BMx|1|20312|s^Second^UCUM||N^Normal^99BM
x|||P|||||""||SIMON^biomerieux~1^biomerieux~Instrument 1^biomerieux~I8^bi
omerieux|||||||||||SCI
INV|BPA^BACT/ALERT® BPA^99BMx|NA^Not Applicable^HL70383|BOTTLE^^99BMx|SN
P458978|||||5||mL^MilliLiter^UCUM|20220131||||21685790004

161150-1283 - D 12-38 MYLA® V4.9

Result for Blood Culture Message Sample

Several Bottle Results in the Same Message

XML

File: result_blood_culture_several_bottles_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<aiMessage>
<header>
<senderName>FMLA</senderName>
<processingIdentifier>P</processingIdentifier>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
<instrumentName>bta</instrumentName>
<serialNumber>bta</serialNumber>
</header>
<requestResult>
<patientInformation>
<patientIdentifier>9500000755</patientIdentifier>
<lastName>TDUPONT, TMARIE</lastName>
<sex>U</sex>
<admissionDate>20100626</admissionDate>
<dischargeDate>20100626</dischargeDate>
<location>100</location>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>95541204</specimenIdentifier>
<collectedDateTime>20100626095800</collectedDateTime>
<receivedDateTime>20100626100230</receivedDateTime>
<specimenType>Blood</specimenType>
<specimenSource>ABR</specimenSource>
<specimenSourceText>ABR</specimenSourceText>
</specimen>
<test>
<universalIdentifier>
<testGroupCode>BC</testGroupCode>
</universalIdentifier>
<instrumentName>bta</instrumentName>
<instrumentType>bta</instrumentType>
<instrumentSerialNumber>bta</instrumentSerialNumber>
<result>
<value>
<bloodCulture>
<dateResultDetermined>20100910110844</dateResultDetermined>
<result>Neg</result>
</bloodCulture>
</value>
<resultStatus>F</resultStatus>
<summaryResult>true</summaryResult>
</result>

161150-1283 - D 12-39 MYLA® V4.9

Result for Blood Culture Message Sample

</test>
<test>
<universalIdentifier>
<testGroupCode>BC</testGroupCode>
</universalIdentifier>
<instrumentSectionId>05A56</instrumentSectionId>
<instrumentName>BTA-1 Name</instrumentName>
<instrumentType>bta</instrumentType>
<result>
<value>
<bloodCulture>
<dateResultDetermined>20100910110844</dateResultDetermined>
<timeToDetectionInHours>4.1</timeToDetectionInHours>
<result>-</result>
</bloodCulture>
</value>
<abnormalFlags>6</abnormalFlags>
<resultStatus>F</resultStatus>
<startDateTime>20100910070101</startDateTime>
<bmxResultData>
<disposable>
<disposableIdentifier>SA023023</disposableIdentifier>
<reference>BSA</reference>
<disposableType>BOTTLE</disposableType>
<disposableStartDateTime>20100910110820</disposableStartDateTime>
<disposableFinalDateTime>20100910110844</disposableFinalDateTime>
</disposable>
</bmxResultData>
</result>
</test>
<test>
<universalIdentifier>
<testGroupCode>BC</testGroupCode>
</universalIdentifier>
<instrumentSectionId>05A55</instrumentSectionId>
<instrumentName>BTA-1 Name</instrumentName>
<instrumentType>bta</instrumentType>
<result>
<value>
<bloodCulture>
<dateResultDetermined>20100910110837</dateResultDetermined>
<timeToDetectionInHours>4.1</timeToDetectionInHours>
<result>-</result>
</bloodCulture>
</value>
<abnormalFlags>2</abnormalFlags>
<resultStatus>F</resultStatus>
<startDateTime>20100910070134</startDateTime>
<bmxResultData>
<disposable>
<disposableIdentifier>SN021883</disposableIdentifier>
<reference>BSN</reference>

161150-1283 - D 12-40 MYLA® V4.9

Result for Blood Culture Message Sample

<disposableType>BOTTLE</disposableType>
<disposableStartDateTime>20100910110819</disposableStartDateTime>
<disposableFinalDateTime>20100910110837</disposableFinalDateTime>
</disposable>
</bmxResultData>
</result>
</test>
</testOrder>
</requestResult>
</aiMessage>

NOTE: 3 results in this message:

- One “specimen level” result (the first one) which is flagged with a summaryResult = true.
This “result” is managed by following the rules defined in Typical Workflow on page 11-13.

- One result per bottle (two bottles in the example).

On the “specimen level” result:

- Only a few fields are filled. To have all the information, bottle results should be taken into
account.

- The instrumentName field is filled with a constant depending on the type of system that
performs the analysis.

- At the message level, instrumentName and serialNumber are filled with the same values
as “specimen level” result.

BMX Format

For BMX Format, several messages are available:

- One for the accession result.

- One for each bottle.

In the following example, there are 2 bottles.

NOTE: BCI Link/MYLA® do not ensure that the messages will be received in this order (even if they
are generated in this order). Indeed, if there is a transmission problem on a message, BCI Link
tries to process the other messages and retries the non-transmitted message(s) later.

Accession result message

File: result_blood_culture_several_bottles_0_RS232.txt

Blocks: Header, Patient, Specimen, Order/Result, Blood culture result, Footer.

mtrsl|idbta|iibta|isbta|itBC|pi9500000755|pnTDUPONT, TMARIE|psU|pl100|pa
2010/06/26|qv2010/06/26|si|ssABR|s5ABR|s12010/06/26|s209:58:00|s32010/06
/26|s410:02:30|ci95541204|ct.812|ta|t4F|ff|rd2010/09/10|ru11:08:44|rcNeg
|zz|

NOTE:The “ff” field (Summary result) informs the LIS that this message is a summary message and
contains the result for the specimen.

161150-1283 - D 12-41 MYLA® V4.9

Result for Blood Culture Message Sample


In this message, only a few fields are filled. To have all the information, the bottle message
should be taken into account.

The “id” (Instrument System Name) and “ti” ("Controler" System Name) fields, which contain
the same value, are filled with constant values.

First bottle result message

File: result_blood_culture_several_bottles_1_RS232.txt

Blocks: Header, Patient, Specimen, Order/Result, Traceability, Blood culture result, Footer.

mtrsl|idBTA-1 Name|iibta|isCOM20_1|itBC|pi9500000755|pnTDUPONT, TMARIE|psU|pl100|

pa2010/06/26|qv2010/06/26|si|ssABR|s5ABR|s12010/06/26|s209:58:00|s32010/06/26|
s410:02:30|ci95541204|ct.812|ta|tiBTA-1 Name|tjbta|t4F|og05A56|ec6|r12010/09/10|
r207:01:01|ts|dtBOTTLE|tuBSA|tpSA023023|th2010/09/10|tk11:08:20|td2010/09/10|tm11
:08:44|tbSA023023|rd2010/09/10|ru11:08:44|re4.1|rc-|zz|

NOTE: The bottle identifier is filled in two fields: tp and tb.

Second bottle result message

File: result_blood_culture_several_bottles_2_RS232.txt

Blocks: Header, Patient, Specimen, Order/Result, Traceability, Blood culture result, Footer.

mtrsl|idBTA-1 Name|iibta|isCOM20_1|itBC|pi9500000755|pnTDUPONT, TMARIE|psU|pl100|

pa2010/06/26|qv2010/06/26|si|ssABR|s5ABR|s12010/06/26|s209:58:00|s32010/06/26|
s410:02:30|ci95541204|ct.812|ta|tiBTA-1 Name|tjbta|t4F|og05A55|ec2|r12010/09/
10|r207:01:34|ts|dtBOTTLE|tuBSN|tpSN021883|th2010/09/10|tk11:08:19|td2010/09/10|
tm11:08:37|tbSN021883|rd2010/09/10|ru11:08:37|re4.1|rc-|zz|

NOTE: The bottle identifier is filled in two fields: tp and tb.

CLSI LIS2-A2

File: result_blood_culture_several_bottles_astm.txt

H|\^&|||BACT/ALERT^A.00|||||||P|1|20100128164942
P|1|9500000755
O|1|95541204||||||||||||||||||||20100910110844|||F
R|1|^^^BC^BSA^SA023023|-|||6||F|||20100910070101|20100910110844|05A56
R|2|^^^TTD^BSA^SA023023|4.1|||6||F|||20100910070101|20100910110844|05A56
R|3|^^^BC^BSN^SN021883|-|||2||F|||20100910070134|20100910110837|05A55
R|4|^^^TTD^BSN^SN021883|4.1|||2||F|||20100910070134|20100910110837|05A55
L|1|F

HL7

HL7 Blood culture consolidated result structure:

The SAC segment is present with SAC-3 set to NULL ( "" ).

161150-1283 - D 12-42 MYLA® V4.9

Result for Blood Culture Message Sample

The message contains 2 OBX segments per bottle, one for Blood culture result Pos/neg and
one for time to detection value.

The couple of OBX is following by INV segment with all traceability about the bottle. The bottle
ID is present in INV-4-1.

The consolidated result is sent in OBX segment with OBX-3 set to "FF" and the value of
consolidated result in OBX-5.

Structure:

SPM

SAC (SAC-3 = "")

OBR

OBX (BC result for the first bottle)

OBX (TTD result for the first bottle)

INV (first bottle information)

OBX (BC result for the second bottle)

OBX (TTD result for the second bottle)

INV (second bottle information)

OBX (OBX-3 = FF, consolidated result)

161150-1283 - D 12-43 MYLA® V4.9

Result for Blood Culture Message Sample

File: result-BC-consolidated.hl7

MSH|^~\&|myla|BMX|HL7LIS01|LIS|20191202175014+0100||OUL^R22^OUL_R22|4d358
df1-d483-41a0-8290-c128c4ea6496|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|1||PID145001||Graal^Laure||19781212|F
PV1|1|U|||||||||||||||||PIV145001
SPM|1|SPE145001||WB^Blood^99BMx|||CATH^Catheterized^99BMx|LAC^Left Ante-
rior Chest^99BMx||
|P^Patient||||||20190929143500|20190929153553
SAC|1||SPE145001
OBR|1|AWOS145011||BC^BC^99BMx||||||BILL01^BILL^Gin||||||OPID3^Dubol|00336
89745612
ORC|SC||||IP
OBX|1|CE|BC^Blood Culture^99BMx|1|Pos^Positive^99BMx|||N^Normal^99BMx|||P
|||||""||SIMON^biomerieux~1^biomerieux~Instrument 1^biomerieux~I8^biomeri
eux|20191120175501||||||||||RSLT
OBX|2|NM|TTD^Time To Detection^99BMx|1|8478|s^Second^UCUM||N^Normal^99BMx
|||P|||||""||SIMON^biomerieux~1^biomerieux~Instrument 1^biomerieux~I8^bio
merieux|20191120175501||||||||||SCI
INV|BPA^BACT/ALERT® BPA^99BMx|NA^Not Applicable^HL70383|BOTTLE^^99BMx|SNP
145011|||||12||mL^milliliter^UCUM|20220131||||21685790004
OBR|2|AWOS145022||BC^BC^99BMx||||||BILL01^BILL^Gin||||||OPID3^Dubol|00336
89745612
ORC|SC||||IP

161150-1283 - D 12-44 MYLA® V4.9

Result for Blood Culture Message Sample

OBX|1|CE|BC^Blood Culture^99BMx|1|Unk^Unknown^99BMx|||N^Normal^99BMx|||I|
||||""||SIMON^biomerieux~1^biomerieux~Instrument 1^biomerieux~I9^biomerie
ux|20191202175010||||||||||RSLT
OBX|2|NM|TTD^Time To Detection^99BMx|1|1036757|s^Second^UCUM||N^Normal^99
BMx|||I|||||""||SIMON^biomerieux~1^biomerieux~Instrument 1^biomerieux~I9^
biomerieux|20191202175010||||||||||SCI
INV|BPA^BACT/ALERT® BPA^99BMx|NA^Not Applicable^HL70383|BOTTLE^^99BMx|SNP
145022|||||10||mL^milliliter^UCUM|20220131||||21685790004
OBX|3|CE|BC^Blood Culture^99BMx|1|Unk^Unknown^99BMx|||N^Normal^99BMx|||I|
||||""||SIMON^biomerieux~1^biomerieux~Instrument 1^biomerieux~I9^biomerie
ux|20191202175010||||||||||RSLT
OBX|4|NM|TTD^Time To Detection^99BMx|1|1036510|s^Second^UCUM||N^Normal^99
BMx|||I|||||""||SIMON^biomerieux~1^biomerieux~Instrument 1^biomerieux~I9^
biomerieux|20191202175010||||||||||SCI
INV|BPA^BACT/ALERT® BPA^99BMx|NA^Not Applicable^HL70383|BOTTLE^^99BMx|SNP
145022|||||10||mL^milliliter^UCUM|20220131||||21685790004
OBR|3|AWOS145011||BC^BC^99BMx||||||BILL01^BILL^Gin||||||OPID3^Dubol|00336
89745612
ORC|SC||||IP
OBX|1|CE|FF^Blood Culture Consolidated^99BMx|1|Pos^Positive^99BMx|||N^Nor
mal^99BMx|||P|||||""||SIMON^biomerieux~SIMON^biomerieux~SIMON^biomerieux~
|20191120175501||||||||||RSLT
OBX|2|NM|TTD^Time To Detection^99BMx|1||s^Second^UCUM||N^Normal^99BMx|||P
|||||""||SIMON^biomerieux~SIMON^biomerieux~SIMON^biomerieux~|201911201755
01||||||||||SCI

161150-1283 - D 12-45 MYLA® V4.9

Result for Identification Message Sample

Result for Identification

Standard Identification Results

XML

File: result_id_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<aiMessage>
<header>
<senderName>FMLA</senderName>
<processingIdentifier>P</processingIdentifier>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
<instrumentName>Vitek 2 System</instrumentName>
<serialNumber>0000139C426D</serialNumber>
</header>
<requestResult>
<patientInformation>
<patientIdentifier>9500000797</patientIdentifier>
<lastName>OABBA, OALICE</lastName>
<sex>U</sex>
<admissionDate>20100629</admissionDate>
<dischargeDate>20100629</dischargeDate>
<location>119</location>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>95545401</specimenIdentifier>
<collectedDateTime>20100629075000</collectedDateTime>
<receivedDateTime>20100629075334</receivedDateTime>
<specimenType>UR</specimenType>
<specimenSource>TUR</specimenSource>
<specimenSourceText>TUR</specimenSourceText>
</specimen>
<isolateNumber>2</isolateNumber>
<test>
<universalIdentifier>
<testGroupCode>ID</testGroupCode>
<testIdentifier>GN</testIdentifier>
<testName>GN</testName>
</universalIdentifier>
<instrumentName>Vitek 2 System</instrumentName>
<instrumentType>V2S</instrumentType>
<instrumentSerialNumber>0000139C426D</instrumentSerialNumber>
<result>
<value>
<identification>
<identificationConfidenceCode>ID_EXCELLENT</identificationConfidenceCode>
<identificationConfidence>Excellent identification</identificationCon-
fidence>

161150-1283 - D 12-46 MYLA® V4.9

Result for Identification Message Sample

<bioNumber>0405610540566601</bioNumber>
<probability>99.0</probability>
<significantTaxon>
<code>ECO</code>
<name>Escherichia coli</name>
</significantTaxon>
</identification>
</value>
<resultStatus>F</resultStatus>
<startDateTime>20100705001449</startDateTime>
<resultDateTime>20100705041449</resultDateTime>
<bmxResultData>
<disposable>
<disposableIdentifier>2411590401199261</disposableIdentifier>
<reference>GN</reference>
<disposableType>VITEK2-ID-CARD</disposableType>
<lotNumber>241159040</lotNumber>
<expirationDate>20110422</expirationDate>
<disposableStartDateTime>20100705001449</disposableStartDateTime>
<disposableFinalDateTime>20100705041449</disposableFinalDateTime>
<disposableSetupTechnologist>LabAdm</disposableSetupTechnologist>
<disposableSetupTechnologistText>LabAdmin</disposableSetupTechnologistText>
</disposable>
</bmxResultData>
</result>
</test>
</testOrder>
</requestResult>
</aiMessage>

BMX Format

File: result_id_RS232.txt

Blocks: Header, Patient, Specimen, Order/Result, Traceability, Identification result, Footer.

mtrsl|idVitek 2 System|iiV2S|is0000139C426D|itID|pi9500000797|pnOABBA, OA
LICE|psU|pl119|pa2010/06/29|qv2010/06/29|si|ssTUR|s5TUR|s12010/06/29|s207
:50:00|s32010/06/29|s407:53:34|ci95545401|ctUR|c12010/07/05|c204:14:49
|ta|rtGN|rnGN|tiVitek 2 System|tjV2S|t4F|r12010/07/05|r200:14:49| r32010/
07/05|r404:14:49|ts|dtVITEK2-ID-CARD|tuGN|tp2411590401199261|tg241159040
|te2011/04/22|th2010/07/05|tk00:14:49|td2010/07/05|tm04:14:49|tqLabAdm|tr
LabAdmin|t12|o1ECO|o2Escherichia coli|o30405610540566601|o999.0|ocExcel-
lent identification|oiID_EXCELLENT|zz|

CLSI LIS2-A2 – Not Applicable

161150-1283 - D 12-47 MYLA® V4.9

Result for Identification Message Sample

HL7

File: result-ID.hl7

MSH|^~\&|myla|BMX|||20191001075757+0200||OUL^R22^OUL_R22|43931b2a-e2b7-
4752-9b5c-39d9506c1c7c|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|||PID134001||Karl^Bill^^^^^L||20110830|F
PV1|1|U|||||||||||||||||PIV134001
SPM|1|2|SPE134002|UR^Urine^99BMx|||||||P^Patient^HL70369||||||20191018090
803|20191018090703
SAC|1||1|SPE134002
OBR|1|AWOS134002||ID^ID^99BMx||||||BILL01&BILL||||||DR0001&Dubol&Jean|003
3689745612
ORC|SC||||CM
OBX|1|CE|ID^Bacteria identified in isolate^99BMx|1|esccol^Escherichia
coli^99BMx|||N^Normal^99BMx|98.0||F|||||""||Vitek2^biomerieux~12345678900
0^biomerieux~LabName^biomerieux~|20191001075253||||||||||RSLT
NTE|1|Z|0405611540565211|o3^Final Bionumber^99BMx
OBX|2|CE|o4^Colony
Count^99BMx|1|mod1^few^99BMx|||N^Normal^99BMx|||F|||||""||Vitek2^biomerie
ux~123456789000^biomerieux~LabName^bio-
merieux~|20191001075253||||||||||SCI
NTE|1|Z|Excellent identification|oc^ID Confidence^99BMx
INV|GN^^99BMx|NA^Not Applicable^HL70383|VITEK2-ID-
CARD^^99BMx|2413123401239641||||||||20150703||||241312340

Specificities of VITEK® MS Results Regarding “Standard” Identification Results

The examples provided in the “vitekms” subfolder are described below:

161150-1283 - D 12-48 MYLA® V4.9

Result for Identification Message Sample

XML

File: vitekms_1IsolatS8-1-Sent_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<aiMessage>
<header>
<senderName>FMLA</senderName>
<processingIdentifier>P</processingIdentifier>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
<instrumentName>Karry Instr</instrumentName>
<serialNumber>12313123321</serialNumber>
</header>
<requestResult>
<patientInformation>
<patientIdentifier>1PATIENTS8</patientIdentifier>
<lastName>Name_1S8</lastName>
<birthdate>19680530</birthdate>
<sex>M</sex>
<physicianIdentifier>Doctor S8</physicianIdentifier>
<admissionDate>20101027</admissionDate>
<dischargeDate>20101027</dischargeDate>
<location>RS8</location>
<hospitalService>Srv8</hospitalService>
<hospitalInstitution>HCL</hospitalInstitution>
<comment>
<text>The Patient comment</text>
</comment>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>1IsolatS8</specimenIdentifier>
<cultureNumber>1</cultureNumber>
<receivedDateTime>20101109161510</receivedDateTime>
<specimenType>blood</specimenType>
<specimenSource>LArm</specimenSource>
<specimenSourceText>Left Arm</specimenSourceText>
</specimen>
<isolateNumber>1</isolateNumber>
<test>
<universalIdentifier>
<testGroupCode>ID</testGroupCode>
<testIdentifier>MALDI-TOF</testIdentifier>
<testName>MALDI-TOF</testName>
</universalIdentifier>
<positionOnDisposable>A3</positionOnDisposable>
<instrumentName>Karry Instr</instrumentName>
<instrumentType>MSID</instrumentType>

161150-1283 - D 12-49 MYLA® V4.9

Result for Identification Message Sample

<instrumentSerialNumber>12313123321</instrumentSerialNumber>
<result>
<value>
<identification>
<identificationConfidenceCode>ID_GOOD</identificationConfidenceCode>
<identificationConfidence>Good identification</identificationCon-
fidence>
<probability>82.1</probability>
<significantTaxon>
<code>ECH</code>
<name>Escherichia hermannii</name>
</significantTaxon>
</identification>
</value>
<resultStatus>F</resultStatus>
<resultDateTime>20101109161719</resultDateTime>
<bmxResultData>
<disposable>
<disposableIdentifier>10008</disposableIdentifier>
<reference>DS110401129</reference>
<disposableType>AXIMA_SLIDE_REF</disposableType>
</disposable>
<extraResultData>1008</extraResultData>
</bmxResultData>
</result>
</test>
</testOrder>
</requestResult>
</aiMessage>

BMX Format

File: vitekms_1IsolatS8-1-Sent_RS232.txt

Blocks: Header, Patient, Specimen, Order/Result, Traceability, Identification result, Footer.

mtrsl|idKarry Instr|iiMSID|is12313123321|itID|pi1PATIENTS8|pnName_1S8|pb
1968/05/30|psM|plRS8|pxSrv8|ppDoctor S8|pa2010/10/27|ptThe Patient com-
ment|qiHCL|qv2010/10/27|si|ssLArm|s5Left Arm|s32010/11/09|s416:15:10|ci1
IsolatS8|c01|ctblood|c12010/11/09|c216:17:19|ta|rtMALDI-TOF|rnMALDI-TOF|
tiKarry Instr|tjMSID|t4F|ojA3|r32010/11/09|r416:17:19|ts|dtAXIMA_SLIDE
_REF|tuDS110401129|tp10008|t11|o1ECH|o2Escherichia hermannii|o982.1|oc
Good identification|oiID_GOOD|zz|

CLSI LIS2-A2 – Not Applicable

161150-1283 - D 12-50 MYLA® V4.9

Result for Identification Message Sample

HL7

File: result-ID.hl7

MSH|^~\&|myla|BMX|HL7LIS01|LIS|20191127123806+0100||OUL^R22^OUL_R22|2ec22c9a-
481b-47fd-bb05-f3dfbda492b4|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|1||PID138101||Marin^Osalle|||F
PV1|1|U|||||||||||||||||PIV138101
SPM|1|1|SPE138101|WB^Blood^99BMx|||CATH^Catheterized^99BMx|LAC^Left Anterior
Chest^99BMx|||P^Patient||||||20191127123350|20190612090703
SAC|1||1|SPE138101
OBR|1|AWOS138101||||||||COID4589^BILL||||||OPID0001^Dubol|0033689745612
ORC|SC||||CM
OBX|1|CE|ID^Bacteria identified in isolate^99BMx|1|PPM^Pseudomonas men-
docina^99BMx|||N^Normal^HL70078|75.0||F|||||Tech2||MSID^biomerieux~qsd-c877-
487b-90cf-9cac7e42cbf7^biomerieux~Vitek MS Server 2^biomerieux~is-serialNumber-
IS-itest-legacy^biomerieux|20191127123350||||||||||RSLT
INV||NA^Not Applicable^HL70383|MATRIX^^99BMx|2||A1||||||||||201912345
INV|1624_1178^^99BMx|NA^Not Applicable^HL70383|AXIMA_SLIDE^^99BMx|1||A1
NTE|1|Z|Good identification|oc^ID Confidence^99BMx

Manual Identification Specificities

For manual identification, the test code and name are user configured. The returned value will
depend on the configuration defined by the user.

XML

File: manual_manual_id_result_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<aiMessage>
<header>
<senderName>FMLA</senderName>
<processingIdentifier>P</processingIdentifier>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
<instrumentName>idMethod</instrumentName>
</header>
<requestResult>
<patientInformation>
<patientIdentifier>1PATIENTS8</patientIdentifier>
<lastName>Name_1S8</lastName>
<birthdate>19680530</birthdate>
<sex>M</sex>
<physicianIdentifier>Doctor S8</physicianIdentifier>
<admissionDate>20101027</admissionDate>
<dischargeDate>20101027</dischargeDate>
<location>RS8</location>
<hospitalService>Srv8</hospitalService>
<hospitalInstitution>HCLB</hospitalInstitution>

161150-1283 - D 12-51 MYLA® V4.9

Result for Identification Message Sample

<comment>
<text>The Patient comment</text>
</comment>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>s2</specimenIdentifier>
</specimen>
<isolateNumber>1</isolateNumber>
<test>
<universalIdentifier>
<testGroupCode>ID</testGroupCode>
</universalIdentifier>
<instrumentName>idMethod</instrumentName>
<instrumentType>MANUAL</instrumentType>
<result>
<value>
<identification>
<significantTaxon>
<code>ECO</code>
<name>Escherichia coli</name>
</significantTaxon>
</identification>
</value>
<resultStatus>F</resultStatus>
<startDateTime>20130729165600</startDateTime>
<resultDateTime>20130729165600</resultDateTime>
</result>
</test>
</testOrder>
</requestResult>
</aiMessage>

BMX Format

File: manual_manual_id_result_RS232.txt

Blocks: Header, Patient, Specimen, Order/Result, Identification result, Footer.

mtrsl|ididMethod|iiMANUAL|itID|pi!oRPHaN!|pv!oRPHaN!|psU|si|cis2|c12013/07/29|
c216:56:00|ta|tiidMethod|tjMANUAL|t4F|r12013/07/29|r216:56:00|r32013/07/29|r416:
56:00|t11|o1ECO|o2Escherichia coli|zz|

CLSI_LIS2_A2 - not applicable

161150-1283 - D 12-52 MYLA® V4.9

Result for Antibiogram Message Sample

HL7

File: result-ID Manual.hl7

MSH|^~\&|myla|BMX|||20191001122800+0200||OUL^R22^OUL_R22|7d7d3b01-ca9e-4c
8e-a3a1-d68445d79195|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|1||PID133001^Bill||Karl||20110830|F
PV1|1|U|||||||||||||||||PIV133001
SPM|1|2|SPE133001|WB^Blood|||CATH^Catheterized|LAC&Left Anterior Chest|||
P&Patient|||||BIO&BIO|20190612090703
SAC|1||""
OBR|1|""||||||||BILL01&BILL||||||ORDERINGPHYSICIANSID1&Dubol|003368974561
2
ORC|SC||||CM
OBX|1|CE|ID^Bacteria identified in isolate^99BMx|1|N024^Actinomyces radi-
cidentis^99BMx|||N^Normal^99BMx|||F|||||""||MANUAL^biomerieux~~FMLAIT^bio
merieux~|20191001122600||||||||||RSLT
NTE|1|Z|Manual ident from plate|nd^User Comment^99BMx

Result for Antibiogram

Standard Antibiogram Result

XML

File: result_ast_simple_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<aiMessage>
<header>
<senderName>FMLA</senderName>
<processingIdentifier>P</processingIdentifier>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
<instrumentName>Vitek 2 System</instrumentName>
<serialNumber>0000139C426D</serialNumber>
</header>
<requestResult>
<patientInformation>
<patientIdentifier>9500000797</patientIdentifier>
<lastName>OABBA, OALICE</lastName>
<sex>U</sex>
<admissionDate>20100629</admissionDate>
<dischargeDate>20100629</dischargeDate>
<location>119</location>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>95545401</specimenIdentifier>
<collectedDateTime>20100629075000</collectedDateTime>
<receivedDateTime>20100629075334</receivedDateTime>
<specimenType>UR</specimenType>

161150-1283 - D 12-53 MYLA® V4.9

Result for Antibiogram Message Sample

<specimenSource>TUR</specimenSource>
<specimenSourceText>TUR</specimenSourceText>
<comment>
<text/>
</comment>
</specimen>
<isolateNumber>2</isolateNumber>
<test>
<universalIdentifier>
<testGroupCode>SU</testGroupCode>
<testIdentifier>AST-GN31</testIdentifier>
<testName>AST-GN31</testName>
</universalIdentifier>
<instrumentName>Vitek 2 System</instrumentName>
<instrumentType>V2S</instrumentType>
<instrumentSerialNumber>0000139C426D</instrumentSerialNumber>
<result>
<value>
<identification>
<identificationConfidenceCode>ID_EXCELLENT</identificationConfi-
denceCode>
<identificationConfidence>Excellent identification</identifica-
tionConfidence>
<bioNumber>0405610540566601</bioNumber>
<probability>99.0</probability>
<significantTaxon>
<code>ECO</code>
<name>Escherichia coli</name>
</significantTaxon>
</identification>
<ast>
<antibiotic>
<code>TCC</code>
<name>Ticarcillin/Clavulanic Acid</name>
<highMic>
<micSign/>
</highMic>
</antibiotic>
<antibiotic>
<code>PIP</code>
<name>Piperacillin</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>4</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>TZP</code>
<name>Piperacillin/Tazobactam</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>4</micValue>

161150-1283 - D 12-54 MYLA® V4.9

Result for Antibiogram Message Sample

</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>CTX</code>
<name>Cefotaxime</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>1</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>CAZ</code>
<name>Ceftazidime</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>1</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>CRO</code>
<name>Ceftriaxone</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>1</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>FEP</code>
<name>Cefepime</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>1</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>ATM</code>
<name>Aztreonam</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>1</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>

161150-1283 - D 12-55 MYLA® V4.9

Result for Antibiogram Message Sample

<antibiotic>
<code>ETP</code>
<name>Ertapenem</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>0.5</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>IPM</code>
<name>Imipenem</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>1</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>MEM</code>
<name>Meropenem</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>0.25</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>AN</code>
<name>Amikacin</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>2</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>GM</code>
<name>Gentamicin</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>1</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>TM</code>
<name>Tobramycin</name>
<highMic>

161150-1283 - D 12-56 MYLA® V4.9

Result for Antibiogram Message Sample

<micSign>&lt;=</micSign>
<micValue>1</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>CIP</code>
<name>Ciprofloxacin</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>0.25</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>LEV</code>
<name>Levofloxacin</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>0.12</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>TGC</code>
<name>Tigecycline</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>0.5</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>SXT</code>
<name>Trimethoprim/Sulfamethoxazole</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>20</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
</ast>
<expertFinding>
<expertConfidence>Consistent expertise</expertConfidence>
<resistanceMechanism>
<drugFamily>QUINOLONES</drugFamily>
<phenotype>RESISTANT QUIN-1</phenotype>
<phenotype>PARTIALLY RESISTANT</phenotype>
<phenotype>WILD</phenotype>

161150-1283 - D 12-57 MYLA® V4.9

Result for Antibiogram Message Sample

</resistanceMechanism>
<resistanceMechanism>
<drugFamily>TETRACYCLINES</drugFamily>
<phenotype>RESISTANT</phenotype>
<phenotype>WILD</phenotype>
</resistanceMechanism>
<resistanceMechanism>
<drugFamily>BETA-LACTAMS</drugFamily>
<phenotype>WILD</phenotype>
<phenotype>INHIBITOR RESISTANT PASE (IRT OR OXA)</phenotype>
<phenotype>CEPHALOSPORINASE (AmpC)</phenotype>
</resistanceMechanism>
<resistanceMechanism>
<drugFamily>AMINOGLYCOSIDES</drugFamily>
<phenotype>WILD</phenotype>
</resistanceMechanism>
<resistanceMechanism>
<drugFamily>TRIMETHOPRIM/SULFONAMIDES</drugFamily>
<phenotype>WILD</phenotype>
<phenotype>TRIMETHOPRIM RESISTANT</phenotype>
</resistanceMechanism>
</expertFinding>
</value>
<resultStatus>F</resultStatus>
<startDateTime>20100705002209</startDateTime>
<resultDateTime>20100705090709</resultDateTime>
<bmxResultData>
<disposable>
<disposableIdentifier>4011640101018282</disposableIdentifier>
<reference>AST-GN31</reference>
<disposableType>VITEK2-AST-CARD</disposableType>
<lotNumber>401164010</lotNumber>
<expirationDate>20110611</expirationDate>
<disposableStartDateTime>20100705002209</disposableStartDate-
Time>
<disposableFinalDateTime>20100705090709</disposableFinalDate-
Time>
<disposableSetupTechnologist>LabAdm</disposableSetupTechnolo-
gist>
<disposableSetupTechnologistText>LabAdmin</disposableSetupTech-
nologistText>
</disposable>
</bmxResultData>
</result>
</test>
</testOrder>
</requestResult>
</aiMessage>

161150-1283 - D 12-58 MYLA® V4.9

Result for Antibiogram Message Sample

BMX Format

File: result_ast_simple_RS232.txt

Blocks: Header, Patient, Specimen, Order/Result, Traceability, Identification result, Ast result,
Footer.

mtrsl|idVitek 2 System|iiV2S|is0000139C426D|itSU|pi9500000797|pnOABBA,
OALICE|psU|pl119|pa2010/06/29|pt|qv2010/06/29|si|ssTUR|s5TUR|s12010/06/29
|s207:50:00|s32010/06/29|s407:53:34| ci95545401|ctUR|c12010/07/05|c209
:07:09| ta|rtAST-GN31|rnAST-GN31|tiVitek 2 System|tjV2S|t4F| r12010/07/05|
r200:22:09|r32010/07/05|r409:07:09|ts|dtVITEK2-AST-CARD|tuAST-GN31|tp401
1640101018282|tg401164010|te2011/06/11|th2010/07/05|tk00:22:09|td2010/07/
05|tm09:07:09|tqLabAdm|trLabAdmin|t12|o1ECO|o2Escherichia coli|o30405610
540566601|o999.0|ocExcellent identification|oiID_EXCELLENT| afQUINOLONES|
apRESISTANT QUIN-1|apPARTIALLY RESISTANT|apWILD|afTETRACYCLINES|apRESIS-
TANT|apWILD|afBETA-LACTAMS|apWILD|apINHIBITOR RESISTANT PASE (IRT OR
OXA)|apCEPHALOSPORINASE (AmpC)|afAMINOGLYCOSIDES|apWILD|afTRIMETHOPRIM/
SULFONAMIDES|apWILD|apTRIMETHOPRIM RESISTANT|ra|a1TCC|a2Ticarcillin/
Clavulanic Acid|a3|ra|a1PIP|a2Piperacillin|a3<=4|a4S|anS|ra|a1TZP|a2Pip-
eracillin/Tazobactam|a3<=4|a4S|anS|ra|a1CTX|a2Cefotaxime|a3<=1|a4S|anS|ra
|a1CAZ|a2Ceftazidime|a3<=1|a4S|anS|ra|a1CRO|a2Ceftriaxone|a3<=1|a4S|anS|r
a|a1FEP|a2Cefepime|a3<=1|a4S|anS|ra|a1ATM|a2Aztreonam|a3<=1|a4S|anS|ra|a1
ETP|a2Ertapenem|a3<=0.5|a4S|anS|ra|a1IPM|a2Imipenem|a3<=1|a4S|anS|ra|a1ME
M|a2Meropenem|a3<=0.25|a4S|anS|ra|a1AN|a2Amikacin|a3<=2|a4S|anS|ra|a1GM|a
2Gentamicin|a3<=1|a4S|anS|ra|a1TM|a2Tobramycin|a3<=1|a4S|anS|ra|a1CIP|a2C
iprofloxacin|a3<=0.25|a4S|anS|ra|a1LEV|a2Levofloxacin|a3<=0.12|a4S|anS|ra
|a1TGC|a2Tigecycline|a3<=0.5|a4S|anS|ra|a1SXT|a2Trimethoprim/Sulfamethox-
azole|a3<=20|a4S|anS|acConsistent expertise|zz|

CLSI LIS2-A2 – Not Applicable

HL7

Result Comments

Some observation results may have a corresponding human-readable comment associated

with it. This readable comment is sent using the NTE segment. The NTE comment is always
related to the previous OBX segment in the message. The comment is available in the field
NTE-3. The organism information is sent in the first OBX segment with OBX-29=SCI.

NOTE: Please refer to Section C.5 - NTE Segment in document #Doc2- PaLM TF-2b.

Phenotype Information

The phenotype information generated by AST system is available in a dedicated OBX

segment. This segment is always the last OBX segment of the OUL^R22 result message. It is
identifiable with the corresponding OBX-3 Observation Identifier field with
ap^Phenotype^99BMx. The value type (OBX-2) of this result is TX for Text. The result value

161150-1283 - D 12-59 MYLA® V4.9

Result for Antibiogram Message Sample

is readable. The result value is formatted by using the ~ separator (repeatable filed) in order to
differentiate each line of result.

161150-1283 - D 12-60 MYLA® V4.9

Result for Antibiogram Message Sample

File: result-SU-simple.hl7

MSH|^~\&|myla|BMX|HL7LIS01|LIS|20191121184442+0100||OUL^R22^OUL_R22|5e7b
7529-bc37-4d5c-99f9-21326c18a56a|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|1||PID1001000||Adam^David||19201008|M
PV1|1|U|||||||||||||||||PIV137001
SPM|1|1|SPE1001001|WB^Blood^99BMx|||CATH^Catheterized^99BMx|LAC^Left
Anterior
Chest^99BMx|||P^Patient|||||BIO^BIO|20191018090803|20191018090703
SAC|1||1|SPE1001001
OBR|1|AWOS137001||||||||COID4589^BILL||||||OPID0001^Dubol|0033689745612
ORC|SC||||CM
OBX|1|CE|ID^Bacteria identified in isolate^99BMx|1|ECO^Escherichia coli^
99BMx|||""|||""|||||""||""|""||||||||||SCI
OBX|2|CE|BLA^Beta-Lactamase^99BMx|1|""|||POS^Positive|||C|||||""||Vitek2
^biomerieux~123456788000^biomerieux~VTK02 Comp Lab02^biomerieux~|20191108
151205||||||||||RSLT
OBX|3|CE|OXSF^Cefoxitin Screen^99BMx|1|""|||NEG^Negative|||C|||||""||Vite
k2^biomerieux~123456788000^biomerieux~VTK02 Comp Lab02^biomerieux~|201911
08151205||||||||||RSLT
OBX|4|SN|P^Benzylpenicillin^99BMx|1|>=^0.5|mg/mL^microgram per milliliter
^UCUM||R^Resistant|||C|||||""||Vitek2^biomerieux~123456788000^biomerieux~
VTK02 Comp Lab02^biomerieux~|20191108151205||||||||||RSLT
OBX|5|SN|OX1^Oxacillin^99BMx|1|=^0.5|mg/mL^microgram per milliliter^UCUM|
|S^Susceptible|||C|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK
02 Comp Lab02^biomerieux~|20191108151205||||||||||RSLT
OBX|6|CE|GM^Gentamicin^99BMx|1|""|||S^Susceptible|||C|||||""||Vitek2^biom
erieux~123456788000^biomerieux~VTK02 Comp Lab02^biomerieux~|201911081512
05||||||||||RSLT
NTE|1|Z|SYN-S|bp^SYN drug^99BMx
OBX|7|SN|K^Kanamycin^99BMx|1|<=^4.0|mg/mL^microgram per milliliter^UCUM||
S^Susceptible|||C|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK02
Comp Lab02^biomerieux~|20191108151205||||||||||RSLT
OBX|8|SN|TM^Tobramycin^99BMx|1|<=^1.0|mg/mL^microgram per milliliter^UCUM
||S^Susceptible|||C|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK
02 Comp Lab02^biomerieux~|20191108151205||||||||||RSLT
OBX|9|SN|OFL^Ofloxacin^99BMx|1|<=^0.5|mg/mL^microgram per milliliter^UCUM
||S^Susceptible|||C|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK
02 Comp Lab02^biomerieux~|20191108151205||||||||||RSLT
OBX|10|CE|ICR^Inducible Clindamycin Resistance^99BMx|1|""|||NEG^Negative|
||C|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK02 Comp Lab02^
biomerieux~|20191108151205||||||||||RSLT
OBX|11|SN|LNZ^Linezolid^99BMx|1|=^2.0|mg/mL^microgram per milliliter^UCUM
||S^Susceptible|||C|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK
02 Comp Lab02^biomerieux~|20191108151205||||||||||RSLT

161150-1283 - D 12-61 MYLA® V4.9

Result for Antibiogram Message Sample

OBX|12|SN|TEC^Teicoplanin^99BMx|1|<=^0.5|mg/mL^microgram per milliliter^

UCUM||S^Susceptible|||C|||||""||Vitek2^biomerieux~123456788000^biomerieux
~VTK02 Comp Lab02^biomerieux~|20191108151205||||||||||RSLT
OBX|13|SN|VA^Vancomycin^99BMx|1|<=^0.5|mg/mL^microgram per milliliter^UCU
M||S^Susceptible|||C|||||""||Vitek2^biomerieux~123456788000^biomerieux~VT
K02 Comp Lab02^biomerieux~|20191108151205||||||||||RSLT
OBX|14|SN|TE^Tetracycline^99BMx|1|<=^1.0|mg/mL^microgram per milliliter^
UCUM||S^Susceptible|||C|||||""||Vitek2^biomerieux~123456788000^biomerieux
~VTK02 Comp Lab02^biomerieux~|20191108151205||||||||||RSLT
OBX|15|SN|FT^Nitrofurantoin^99BMx|1|<=^16.0|mg/mL^microgram per millilite
r^UCUM||S^Susceptible|||C|||||""||Vitek2^biomerieux~123456788000^biomerie
ux~VTK02 Comp Lab02^biomerieux~|20191108151205||||||||||RSLT
OBX|16|SN|RA^Rifampicin^99BMx|1|<=^0.03|mg/mL^microgram per milliliter^
UCUM||S^Susceptible|||C|||||""||Vitek2^biomerieux~123456788000^biomerieux
~VTK02 Comp Lab02^biomerieux~|20191108151205||||||||||RSLT
OBX|17|SN|SXT^Trimethoprim/Sulfamethoxazole^99BMx|1|<=^10.0|mg/mL^microgr
am per milliliter^UCUM||S^Susceptible|||C|||||""||Vitek2^biomerieux~12345
6788000^biomerieux~VTK02 Comp Lab02^biomerieux~|20191108151205||||||||||
RSLT
OBX|18|TX|ap^Phenotype^99BMx|1|WILD:AMINOGLYCOSIDES~WILD:QUINOLONES~WILD:
TETRACYCLINES~WILD:MACROLIDES/LINCOSAMIDES/STREPTOGRAMINS~MLSB CONSTITUTI
VE:MACROLIDES/LINCOSAMIDES/STREPTOGRAMINS~MLSB+SA CONSTITUTIVE:MACROLIDES
/LINCOSAMIDES/STREPTOGRAMINS~WILD:GLYCOPEPTIDES~WILD:FURANES~WILD:RIFAMYC
INS~WILD:TRIMETHOPRIM/SULFONAMIDES~RESISTANT TO LINCOSAMIDES:MACROLIDES/
LINCOSAMIDES/STREPTOGRAMINS~ACQUIRED PENICILLINASE:BETA-LACTAMS~TRIMETHOP
RIM RESISTANT:TRIMETHOPRIM/SULFONAMIDES~RESISTANT TO STREPTOGRAMINS (SGA-
SGB):MACROLIDES/LINCOSAMIDES/STREPTOGRAMINS~WILD:OXAZOLIDINONE~RESISTANT
(EFFLUX):MACROLIDES/LINCOSAMIDES/STREPTOGRAMINS||||||C|||||""||Vitek2^bio
merieux~123456788000^biomerieux~VTK02 Comp Lab02^biomerieux~|201911081512
05||||||||||RSLT
INV|AST-P631^^99BMx|NA^Not Applicable^HL70383|VITEK2-AST-CARD^^99BMx|2413
1234012134002||||||||20220327||||7310486103
NTE|1|Z|AMPICILLIN: Perform an alternative method of testing prior to re
porting of results.|nd^User Comment^99BMx
NTE|2|Z|Resent for report|nd^User Comment^99BMx

Antibiogram with an Offline Test

This antibiogram result file will contain:

- the identification result,

- the antibiogram result,

- the Beta-Lactamase result.

161150-1283 - D 12-62 MYLA® V4.9

Result for Antibiogram Message Sample

XML

File: result_ast_astm.xml

<?x161150-1283 - Dml version="1.0" encoding="UTF-8"?>

<aiMessage>
<header>
<senderName>MYLA-1.0.0.11</senderName>
<processingIdentifier>P</processingIdentifier>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
<instrumentName>V2S</instrumentName>
<serialNumber>123456789000</serialNumber>
</header>
<requestResult>
<patientInformation>
<patientIdentifier>G406270/A</patientIdentifier>
<patientVisitNumber>G406270-123</patientVisitNumber>
<lastName>Robinson, Adele</lastName>
<physicianIdentifier>Dr. Ro</physicianIdentifier>
<physicianName>Dr. Robert</physicianName>
<location>9EAST</location>
<locationText>9EAST</locationText>
<comment>
<source>P</source>
<code>Age=7</code>
<text>Age=7</text>
<type>G</type>
</comment>
</patientInformation>
<testOrder>
<specimen>
<specimenIdentifier>WD1245452</specimenIdentifier>
<collectedDateTime>20091204124514</collectedDateTime>
<specimenType>Wound</specimenType>
<specimenTypeText>Wound</specimenTypeText>
<specimenSource>Left A</specimenSource>
<specimenSourceText>Left Arm</specimenSourceText>
<comment>
<source>P</source>
<code>S-GN</code>
<text>S-GN</text>
<type>G</type>
</comment>
</specimen>
<isolateNumber>1</isolateNumber>
<isolateRelativeIdentifier>103574</isolateRelativeIdentifier>
<test>
<universalIdentifier>
<testGroupCode>SU</testGroupCode>

161150-1283 - D 12-63 MYLA® V4.9

Result for Antibiogram Message Sample

<testIdentifier>AST-N233</testIdentifier>
<testName>AST-N233</testName>
</universalIdentifier>
<instrumentName>La balme</instrumentName>
<instrumentType>V2S</instrumentType>
<instrumentSerialNumber>00000738268C</instrumentSerialNumber>
<result>
<value>
<identification>
<significantTaxon>
<code>ECO</code>
<name>Escherichia coli</name>
</significantTaxon>
</identification>
<ast>
<antibiotic>
<code>AM</code>
<name>Ampicillin</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>2.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>AMC</code>
<name>Amoxicillin/Clavulanic Acid</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>2.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>TIC</code>
<name>Ticarcillin</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>8.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>

161150-1283 - D 12-64 MYLA® V4.9

Result for Antibiogram Message Sample

<antibiotic>
<code>TZP</code>
<name>Piperacillin/Tazobactam</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>4.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>CF</code>
<name>Cefalotin</name>
<highMic>
<micValue>8.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>FOX</code>
<name>Cefoxitin</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>4.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>CTX</code>
<name>Cefotaxime</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>1.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>CAZ</code>
<name>Ceftazidime</name>
<highMic>

161150-1283 - D 12-65 MYLA® V4.9

Result for Antibiogram Message Sample

<micSign>&lt;=</micSign>
<micValue>1.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>ETP</code>
<name>Ertapenem</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>0.5</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>IPM</code>
<name>Imipenem</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>0.25</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>AN</code>
<name>Amikacin</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>2.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>GM</code>
<name>Gentamicin</name>
<highMic>
<micSign>&lt;=</micSign>

161150-1283 - D 12-66 MYLA® V4.9

Result for Antibiogram Message Sample

<micValue>1.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>TM</code>
<name>Tobramycin</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>1.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>NA</code>
<name>Nalidixic Acid</name>
<highMic>
<micValue>4.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>CIP</code>
<name>Ciprofloxacin</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>0.25</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>OFL</code>
<name>Ofloxacin</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>0.25</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>

161150-1283 - D 12-67 MYLA® V4.9

Result for Antibiogram Message Sample

<antibiotic>
<code>FT</code>
<name>Nitrofurantoin</name>
<highMic>
<micValue>32.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
<antibiotic>
<code>SXT</code>
<name>Trimethoprim/Sulfamethoxazole</name>
<highMic>
<micSign>&lt;=</micSign>
<micValue>20.0</micValue>
</highMic>
<category>S</category>
<nonExpertCategory>S</nonExpertCategory>
</antibiotic>
</ast>
<expertFinding>
<expertConfidence>Expert analysis not performed</expertConfidence>
</expertFinding>
</value>
<resultStatus>F</resultStatus>
<startDateTime>20150507152027</startDateTime>
<resultDateTime>20150507230527</resultDateTime>
<bmxResultData>
<disposable>
<disposableIdentifier>6333219101108035</disposableIdentifier>
<reference>AST-N233</reference>
<disposableType>VITEK2-AST-CARD</disposableType>
<lotNumber>633321910</lotNumber>
<expirationDate>20151007</expirationDate>
<disposableStartDateTime>20150507152027</disposableStartDateTime>
<disposableFinalDateTime>20150507230527</disposableFinalDateTime>
<disposableSetupTechnologist>LABTEC</disposableSetupTechnologist>
<disposableSetupTechnologistText>LabTech</disposableSetupTechnologistText>
</disposable>
</bmxResultData>
</result>
</test>
</testOrder>
</requestResult>
</aiMessage>

161150-1283 - D 12-68 MYLA® V4.9

Result for Antibiogram Message Sample

BMX Format

File: result_ast_RS232.txt

Blocks: Header, Patient, Specimen, Order/Result, Traceability, Identification, Expert finding,

Antibiogram result, Footer.

mtrsl|idV2S|iiV2S|is123456789000|itSU|piG406270/A|pvG406270-123|pnRobin-
son, Adele|pl9EAST|p29EAST|ppDr. Ro|p5Dr. Robert|pcAge=7|ptAge=7|si|ss
Left A|s5Left Arm|s12009/12/04|s212:45:14|scS-GN|snSGN|ci2|ctWound|cn
Wound|c12009/12/10|c223:52:30|ta|rtAST-GP55|rnAST-GP55| tiV2S|tjV2S|t4F|
r12009/12/10|r217:22:30|r32009/12/10|r423:52:30|ts|dtVITEK2-AST-CARD|
tuAST-GP55|tp1201850201206984|tg120185020|te2012/01/07|th2009/12/10|
tk17:22:30|td2009/12/10|tm23:52:30|tqLabTech|trLabTech|t11|o1pseaer|
o2Pseudomonas aeruginosa|o30003053003500000|o999.0|ocExcellent identifi-
cation|afGLYCOPEPTIDES|apRESISTANT (TEC)|apWILD|afRIFAMYCINES|apWILD|
afQUINOLONES|apWILD|afTETRACYCLINES|apWILD|afBETA-LACTAMS|apMODIFICATION
OF PBP (mecA)|apACQUIRED PENICILLINASE|afFURANES|apWILD|afAMINOGLYCO-
SIDES|apRESISTANT KAN TOB (ANT(4')(4"))|apWILD|apRESISTANT KAN (APH(3')-
III)|afPHENICOLS|apWILD|afMACROLIDES/LINCOSAMIDES/STREPTOGRAMINS|apWILD|
ra|ar|a1Bla|a2BetaLactamase|a3Pos|a4+|an+|ra|a1peng|a2Benzylpenicillin|
a3>=0.5|a4R|anR|ra|at|a1ams|a2Ampicillin/Sulbactam|a3|a4R|anS|ra|a1ox|
a2Oxacillin|a30.5|a4R|anR|ra|at|a1cz|a2Cefazolin|a3|a4R|anS|ra|a1gm|a2Ge
ntamicin|a3<=0.5|a4S|anS|ra|a1cip|a2Ciprofloxacin|a3<=0.5|a4S|anS|ra|a1l
ev|a2Levofloxacin|a30.25|a4S|anS|ra|a1nor|a2Norfloxacin|a31|a4S|anS|ra|a
1ofx|a2Ofloxacin|a3<=0.5|a4S|anS|ra|a1e|a2Erythromycin|a3<=0.25|a4S|anS|
ra|a1cc|a2Clindamycin|a3<=0.25|a4S|anS|ra|a1va|a2Vancomycin|a3<=1|a4S|an
S|ra|a1tet|a2Tetracycline|a3<=1|a4S|anS|ra|a1ftn|a2Nitrofurantoin|a332|a
4S|anS|ra|a1c|a2Chloramphenicol|a38|a4S|anS|ra|a1rif|a2Rifampicin|
a3<=0.5|a4S|anS|acConsistent|zz|

CLSI LIS2-A2 – Not Applicable

HL7

Result Comments

Some observation results may have a corresponding human-readable comment associated

with it. This readable comment is sent using the NTE segment. The NTE comment is always
related to the previous OBX segment in the message. The comment is available in the field
NTE-3.

NOTE: Please refer to Section C.5 - NTE Segment in document #Doc2- PaLM TF-2b.

Phenotype Information

The phenotype information generated by AST system is available in a dedicated OBX

segment. This segment is always the last OBX segment of the OUL^R22 result message. It is
identifiable with the corresponding OBX-3 Observation Identifier field with

161150-1283 - D 12-69 MYLA® V4.9

Result for Antibiogram Message Sample

ap^Phenotype^99BMx. The value type (OBX-2) of this result is TX for Text. The result value
is readable. The result value is formatted by using the ~ separator (repeatable filed) in order to
differentiate each line of result.

File: result-SU-with BLA.hl7

MSH|^~\&|myla|BMX|HL7IS01|LIS|20191122164224+0100||OUL^R22^OUL_R22|4ad47f
3a-be3e-43a3-b444-7cdfbe3157aa|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|1||PID137001||Bill^Arbre||20190830|F
PV1|1|U|||||||||||||||||PIV137001
SPM|1|1|SPE137001|WB^Blood|||CATH^Catheterized|LAC^Left Anterior Chest|||
P^Patient|||||BIO^BIO|20191018090803|20191018090703
SAC|1||1|SPE137001
OBR|1|AWOS137001||||||||COID4589^BILL||||||OPID0001^Dubol|0033689745612
ORC|SC||||CM
OBX|1|CE|ID^Bacteria identified in isolate^99BMx|1|ECO^Escherichia coli^99
BMx|||""|||""|||||""||""|""||||||||||SCI
OBX|2|CE|BLA^Beta-Lactamase^99BMx|1|""|||POS^Positive|||F|||||""||Vitek2^
biomerieux~123456788000^biomerieux~VTK02 Comp Lab02^biomerieux~|201911221
63749||||||||||RSLT
OBX|3|CE|OXSF^Cefoxitin Screen^99BMx|1|""|||NEG^Negative|||F|||||""||Vite
k2^biomerieux~123456788000^biomerieux~VTK02 Comp Lab02^biomerieux~|201911
22163749||||||||||RSLT
OBX|4|SN|P^Benzylpenicillin^99BMx|1|>=^0.5|mg/mL^microgram per milliliter
^UCUM||R^Resistant|||F|||||""||Vitek2^biomerieux~123456788000^biomerieux~
VTK02 Comp Lab02^biomerieux~|20191122163749||||||||||RSLT
OBX|5|SN|OX1^Oxacillin^99BMx|1|=^0.5|mg/mL^microgram per milliliter^UCUM|
|S^Susceptible|||F|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK0
2 Comp Lab02^biomerieux~|20191122163749||||||||||RSLT
OBX|6|SN|GM^Gentamicin^99BMx|1|<=^0.5|mg/mL^microgram per milliliter^UCUM
||S^Susceptible|||F|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK
02 Comp Lab02^biomerieux~|20191122163749||||||||||RSLT
OBX|7|SN|K^Kanamycin^99BMx|1|<=^4.0|mg/mL^microgram per milliliter^UCUM||
S^Susceptible|||F|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK02
Comp Lab02^biomerieux~|20191122163749||||||||||RSLT
OBX|8|SN|TM^Tobramycin^99BMx|1|<=^1.0|mg/mL^microgram per milliliter^UCUM
||S^Susceptible|||F|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK
02 Comp Lab02^biomerieux~|20191122163749||||||||||RSLT
OBX|9|SN|OFL^Ofloxacin^99BMx|1|<=^0.5|mg/mL^microgram per milliliter^UCUM
||S^Susceptible|||F|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK
02 Comp Lab02^biomerieux~|20191122163749||||||||||RSLT
OBX|10|CE|ICR^Inducible Clindamycin Resistance^99BMx|1|""|||NEG^Negative|
||F|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK02 Comp Lab02^bi
omerieux~|20191122163749||||||||||RSLT

161150-1283 - D 12-70 MYLA® V4.9

Result for Antibiogram Message Sample

OBX|11|SN|LNZ^Linezolid^99BMx|1|=^2.0|mg/mL^microgram per milliliter^UCUM

||S^Susceptible|||F|||||""||Vitek2^biomerieux~123456788000^biomerieux~VTK
02 Comp Lab02^biomerieux~|20191122163749||||||||||RSLT
OBX|12|SN|TEC^Teicoplanin^99BMx|1|<=^0.5|mg/mL^microgram per milliliter^
UCUM||S^Susceptible|||F|||||""||Vitek2^biomerieux~123456788000^biomerieux
~VTK02 Comp Lab02^biomerieux~|20191122163749||||||||||RSLT
OBX|13|SN|VA^Vancomycin^99BMx|1|<=^0.5|mg/mL^microgram per milliliter^
UCUM||S^Susceptible|||F|||||""||Vitek2^biomerieux~123456788000^biomerieux
~VTK02 Comp Lab02^biomerieux~|20191122163749||||||||||RSLT
OBX|14|SN|TE^Tetracycline^99BMx|1|<=^1.0|mg/mL^microgram per milliliter^
UCUM||S^Susceptible|||F|||||""||Vitek2^biomerieux~123456788000^biomerieux
~VTK02 Comp Lab02^biomerieux~|20191122163749||||||||||RSLT
OBX|15|SN|FT^Nitrofurantoin^99BMx|1|<=^16.0|mg/mL^microgram per millilite
r^UCUM||S^Susceptible|||F|||||""||Vitek2^biomerieux~123456788000^biomeri
eux~VTK02 Comp Lab02^biomerieux~|20191122163749||||||||||RSLT
OBX|16|SN|RA^Rifampicin^99BMx|1|<=^0.03|mg/mL^microgram per milliliter^
UCUM||S^Susceptible|||F|||||""||Vitek2^biomerieux~123456788000^biomerieux
~VTK02 Comp Lab02^biomerieux~|20191122163749||||||||||RSLT
OBX|17|SN|SXT^Trimethoprim/Sulfamethoxazole^99BMx|1|<=^10.0|mg/mL^microgr
am per milliliter^UCUM||S^Susceptible|||F|||||""||Vitek2^biomerieux~12345
6788000^biomerieux~VTK02 Comp Lab02^biomerieux~|20191122163749||||||||||
RSLT
OBX|18|TX|ap^Phenotype^99BMx|1|WILD:GLYCOPEPTIDES~WILD:RIFAMYCINS~WILD:QU
INOLONES~WILD:TETRACYCLINES~ACQUIRED PENICILLINASE:BETA-LACTAMS~WILD:FURA
NES~WILD:OXAZOLIDINONE~WILD:AMINOGLYCOSIDES~WILD:TRIMETHOPRIM/SULFONAMIDE
S~TRIMETHOPRIM RESISTANT:TRIMETHOPRIM/SULFONAMIDES~MLSB CONSTITUTIVE:MACR
OLIDES/LINCOSAMIDES/STREPTOGRAMINS~MLSB+SA CONSTITUTIVE:MACROLIDES/LINCOS
AMIDES/STREPTOGRAMINS~WILD:MACROLIDES/LINCOSAMIDES/STREPTOGRAMINS~RESISTA
NT (EFFLUX):MACROLIDES/LINCOSAMIDES/STREPTOGRAMINS~RESISTANT TO LINCOSAMI
DES:MACROLIDES/LINCOSAMIDES/STREPTOGRAMINS~RESISTANT TO STREPTOGRAMINS (S
GA-SGB):MACROLIDES/LINCOSAMIDES/STREPTOGRAMINS||||||F|||||""||Vitek2^biom
erieux~123456788000^biomerieux~VTK02 Comp Lab02^biomerieux~|201911221637
49||||||||||RSLT
INV|AST-P631^^99BMx|NA^Not Applicable^HL70383|VITEK2-AST-CARD^^99BMx|2413
1238888137055||||||||20220327||||7310486103
NTE|1|Z|AMPICILLIN: Perform an alternative method of testing prior to re
porting of results.|nd^User Comment^99BMx

Manual Antibiogram Specificities

For manual antibiograms, the test code and name are user configured. The returned value will
depend on the configuration defined by the user.

The identification associated with the antibiogram is always sent for manual antibiogramming.

161150-1283 - D 12-71 MYLA® V4.9

Result for Antibiogram Message Sample

If the antibiogram contains a panel and at least one individual drug, two messages will be sent
to the LIS. The first message will contain all drugs included in the panel and the second will
contain all the individuals drugs. It is important to note that for both messages the testIdentifier
will be the "panel code".

If the antibiogram only contains individual drugs, all the results will be sent to the LIS in the
same message without testIdentifier.

No expert finding is performed.

NOTE: The MIC values are strings and can have any value (it will depend on what the user has typed
on the screen).

XML

File: manual_manual_ast_result_astm.xml

<?xml version="1.0" encoding="UTF-8"?>

<aiMessage>
<header>
<senderName>FMLA</senderName>
<processingIdentifier>P</processingIdentifier>
<version>1394-97</version>
<dateTime>20100128164942</dateTime>
<instrumentName>KB</instrumentName>
</header>
<requestResult>
<patientInformation>
<patientIdentifier>9500000797</patientIdentifier>
<lastName>OABBA, OALICE</lastName>
<sex>U</sex>
<admissionDate>20100629</admissionDate>
<dischargeDate>20100629</dischargeDate>
<location>119</location>
<testOrder>
<specimen>
<specimenIdentifier>s7</specimenIdentifier>
</specimen>
<isolateNumber>1</isolateNumber>
<test>
<universalIdentifier>
<testGroupCode>SU</testGroupCode>
<testIdentifier>panelCode</testIdentifier>
<testName>panelName</testName>
</universalIdentifier>
<instrumentName>KB</instrumentName>
<instrumentType>MANUAL</instrumentType>
<result>

161150-1283 - D 12-72 MYLA® V4.9

Result for Antibiogram Message Sample

<value>
<ast>
<antibiotic>
<code>AN</code>
<name>Amikacin</name>
<suppressedDrug>false</suppressedDrug>
<deducedDrug>false</deducedDrug>
<highMic>
<suppressedMic>false</suppressedMic>
</highMic>
<category>S</category>
<diamter>1</diameter>
</antibiotic>
</ast>
</value>
<resultStatus>F</resultStatus>
<startDateTime>20130729173700</startDateTime>
<resultDateTime>20130729173700</resultDateTime>
</result>
</test>
</testOrder>
</requestResult>
</aiMessage>

BMX Format

File: manual_manual_ast_result_RS232.txt

Blocks: Header, Patient, Specimen, Order/Result, Antibiogram result, Footer.

mtrsl|ididMethod|iiMANUAL|itSU|pi!oRPHaN!|pv!oRPHaN!|psU|si|cis7|c12013/
0729|c217:37:00|ta|rtpanelCode|rnpanelName|tiidMethod|tjMAN-
UAL|t4F|r12013/07/29|r217:37:00|r32013/07/
29|r417:37:00|t11|ra|fi1|a1AN|a2Amikacin|a4S|zz|

CLSI LIS2-A2 – Not Applicable

161150-1283 - D 12-73 MYLA® V4.9

Result for Gram Staining Message Sample

HL7

File: result_manual_ast_result.hl7

MSH|^~\&|myla|BMX|||20191001123322+0200||OUL^R22^OUL_R22|88fd7e35-aba5-49
cb-8123-c7dba061ac7a|P|2.5.1|||NE|AL||UNICODE UTF-8
PID|1||PID133001^Bill||Karl||20110830|F
PV1|1|U|||||||||||||||||PIV133001
SPM|1|2|SPE133001|WB^Blood^99BMX|||CATH^Catheterized^99BMX|LAC&Left Ante-
rior Chest^99BMx|||
P&Patient|||||BIO&BIO|20190612090703
SAC|1||""
OBR|1|AWOS133001||||||||BILL01&BILL||||||ORDERINGPHYSICIANSID1&Dubol|0033
689745612
ORC|SC||||CM
OBX|1|CE|ID^Bacteria identified in isolate^99BMx|1|N024^Actinomyces radici
dentis^99BMx|||""|||""|||||""||""|""||||||||||SCI
OBX|2|CE|CAZ^Ceftazidime^99BMx|1||||R^Resistant|||F|||||""||MANUAL^biome
rieux~~Etest^biomerieux~|20191001123000||||||||||RSLT

Result for Gram Staining

Sending GRAM results to LIS is not supported by MYLA®.

161150-1283 - D 12-74 MYLA® V4.9

A Appendix - Message Mapping Table

This appendix refers to a message mapping table available in an Excel format file
attached to this PDF document.

To open this file:

1. Click on the left side of the screen.

2. Double-click on the file to open it or right-click and save it.

The fields contained in the table are described below:

Field type Meaning

Managed fields –symbolized by 
LIS to MYLA® (download): The field can be received.
® The field can be sent.
MYLA to LIS (upload):
For the AI (ex. MYLA® to VITEK® or The field is managed by the AI and MYLA® will send/receive the
VITEK® to MYLA®): data if available.

Fields not managed –symbolized by 

The field cannot be received (if the field is in the message, either
LIS to MYLA® (download): the field will be ignored or an error will be generated).
MYLA® to LIS (upload): The field will never be sent.
For the AI (ex. MYLA® to VITEK® or The field is not managed by the AI and MYLA® will not send/
VITEK® to MYLA®): receive the data if available.

Mandatory fields
We expect these fields to be present. (Mandatory fields in result
Download:
parts are mandatory only if you download results).
Upload: The fields will be present.

Important fields (information is considered like the data fields in MYLA®)

Non mandatory field, but really important for the MYLA®
Level - 1 processing.
– Critical information: In download, interesting information to have.
In upload, information to be taken into account.

Level 2 Important field for MYLA®.

- Very important information: In download, interesting information to have.
In upload, information to be taken into account.
Level 3 – Important information: Field that can be useful to MYLA®.
No level – Information fields N/A

Versioning
"Version added" column Allows identification of fields added after MYLA® V1.

161150-1283 - D A-1 MYLA® V4.9

B Appendix - Glossary

Abbreviations and Acronyms

AI Analysis Instrument or analysis system.

ASTM American Society for Testing and Materials.
AWOS Analytical Work Order Step(s)
BCI BioMérieux Communication Interfaces.
BMX Abbreviation for bioMérieux.
Clinical and Laboratory Standards Institute (formerly NCCLS) is an international,
interdisciplinary, nonprofit, standards-developing, and educational organization that
CLSI promotes the development and use of voluntary consensus standards and
guidelines within the health care community. Mostly followed in North America.
HIS Hospital Information System.
IT Information Technology.
LIMS Laboratory Information Management System – mainly used in industry scope.
Laboratory Information System.
LIS A LIS will send analysis requests to MYLA® and will expect to receive results from
MYLA®.
N/A Not Applicable.
TBD To Be Defined.
EXtensible Markup Language. XML is a markup specification language for
XML structuring documents.

Definitions

ASTM E1394 Standard specification for transferring information between clinical instruments and
computer systems, published in the early 90’s by the E31 committee and the
American Society for Testing and Materials
LIS-A2 In 2001, the ASTM Committee E31 decided to transfer responsibility for the E31.13
standards to NCCLS.
LIS-A Following this transfer, nine standards were redesigned as NCCLS standards. LIS1
is the revision of the former ASTM-1381 and LIS2 is the revision of the former ASTM
1394-97. The last version of CLSI LIS1 is LIS1-A, the last version of CLSI LIS2 is
LIS2-A2.
Specifications of messages relating to the transfer of data between the bioMérieux
ASTM-XML representa- analyzers and the LIS.
tion This specification, elaborated by bioMérieux, is based on the ASTM LIS2-A2
attributes with an XML message structure.
Communication connec- Represents a bi-directional interface between two applications on the same machine
tion or Socket or on two separate machines (inter-process communication).
A data management system is a software that will only receive information from
Data Management Sys- MYLA® in order to compute statistics and reports.
tem It must be able to receive results and can optionally receive requests (forwarded by
MYLA®).
Type of description used to structure messages for data transfer between analysis
Data representation instruments and the laboratory information systems.
The FTP service is based on a client/server architecture and is used to transfer files
FTP between heterogeneous machines. It is based on the TCP/IP network protocols. 
For further information, refer to the RFC 0959 standard - http://www.rfcs.org
Previous observation, which is embedded in the order or sent allow in request
Offline test message.
Unique identifier used for a biological analysis (also known as sample ID, accession
Specimen ID ID/number, laboratory ID/number).

161150-1283 - D B-1 MYLA® V4.9

Revision History

This section contains a summary of changes made to each released revision of this document starting with
part number 161150-1283 - A.

Change type categories:

N/A Not applicable (First publication)

Correction Correction of documentation anomalies
Technical change Addition, revision and/or removal of information related to the product
Administrative Implementation of non-technical changes noticeable to the user

Note: • Minor typographical, grammar, and formatting changes are not included in the revision
history.
• Not all versions may be available in all languages.

Release Date Part Number Change Type Change Summary

2021-02 161150-1283 - D Technical Update for MYLA 4.9:
change • Section: Difference MYLA® 4.8 vs MYLA® 4.9 added
• Example of Optional Expected Duration added to Request
with optional DisposableIdentier
• Admission date and discharge date request messages
fields supported in HL7 format
• Example of Request cancellation messages added
2020-04 161150-1283 - Administrative • Attached files added to main pdf file
C1 change

2020-02 161150-1283 - C Technical • Addition of HL7 protocol

change
2019-06 161150-1283 - B Technical • Update protocol names to be more consistent
change
- ASTM-XML renamed to XML

- RS232 Format renamed to BMX

Format

- ASTM protocol renamed to CLSI

• New section about differences between MYLA® V4.7 and

MYLA® V4.7.1
2018-12 161150-1283 - A N/A First publication
 bioMérieux SA
376 Chemin de l’Orme
69280 Marcy-l’Etoile, France
Tel. +33 (0)4 78 87 20 00 Fax +33 (0)4 78 87 20 90

www.biomerieux.com