MNT-10910-01-F MIURA Connessione LIS - ENG

I.S.E.
– Sistemi Intelligenti Elettronici
Miura Instrumentation Series

Random Access Autoanalyzers
L.I.S. Connection – Technical Manual
I.S.E. S.r.l. – Italy Rome MNT-10910-01-F Rev.E ENG

MIURA Instrumentation Series
i.1 Identification Data

This document applies to the Miura Series of Clinical Chemistry Analyzers.
Refer to the Instrument User Manual for information on the correct operation and
use of the Instrument.
i.1.1 Document
 Document code: MNT-10910-01-F
 Revision: F
 Revision date: 18 July 2012
i.1.2 Revision history

 Revision C  Modified structure of messages
o PatientInformation
o TestOrder
o Terminator
 Comment message added
 Revision D  revision history added
 STX definition (par. 3.2.3) -> da 12H a 02H
 Header message example (par. 3.3.1)
 PatientInformation message example (par.3.3.2)
 TestOrder message example (par. 3.3.3)
 Terminator message example (par. 3.3.7)
 Request message example (par. 3.3.8)
 Revision E  Modified example par. 3.4.1

 Date time in Result message optional (par. 3.3.4)
 Added field number column to message
descriptions for readability purpose
 Added length for required field
 Added maximum length for not fixed field
 Revision F  Refactoring of the whole manual
 New chapters added
 Changed TestOrder message definitions
i.1.3 Instrument
 MIURA: p/n 10001-xx-A (xx=version)
 MIURA 200: p/n 10674-xx-A (xx=version)
 MIURA 100: p/n 10750-xx-A (xx=version)
I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 2/28

MNT-10910-01-E Rev.F ENG
i.1.4 Producer
 I.S.E. S.r.l.
Via delle Driadi, 45
00133 Roma – Italy
Phone: +39 06 20610289
Fax: +39 06 2018131
E-mail: info@logotech-ise.com
WEB: www.logotech-ise.com
i.2 Copyright
The content of this document, the pictures, the tables and the graphics included, is
intellectual property of I.S.E. S.r.l.
Unauthorized copies, total or partial, could cause legal actions in order to preserve
owner’s interests.
i.3 Purpose of This Document

This document defines the communication protocol that is used for connecting a
Miura Chemistry System to a Laboratory Information System (L.I.S.). This document
contains complex technical information. Therefore, it is intended for use by
technical staff that have experience of interfacing Laboratory Instruments and/or
Medical Computer Systems.
i.4 Definitions, Acronyms ed Abbreviations

AD Applicable Document
FW Firmware
HW Hardware
L.I.S. Laboratory Information System
SW Software
TBD To Be Defined
TBC To Be Confirmed
TBV To Be Verified
i.5 Documentation
i.5.1 Applicable Documents

The Latest version of the Miura Instrument User Manual.

i.5.2 Reference Documents

NCCLS, code LIS02-A2, Vol.24 Nr.33
“Specification for Transferring Information Between Clinical Laboratory Instruments
and Information Systems; Approved Standard—Second Edition”.
ASTM, code E1381-02

“Standard Specification for Low-Level Protocol to Transfer Messages Between
Clinical Laboratory Instruments and Computer Systems”.
IEEE, 802.3
“Carrier sense multiple access with collision detection (CSMA/CD) access method
and physical layer specifications”.
ANSI, X3.15-1976
“Bit sequencing of the code for information interchange in serial by bit data
transmission (with ANSI X3.15-1976)”
ANSI, X3.16-1976
“Character structure & character parity sense for serial by bit data communication
in the code for information interchange (with ANSI X3.16-1976/R1983)”.

i.6 List of Contents

i.1 Identification Data .....................................................................................................2
i.1.1 Document ................................................................................................................2
i.1.2 Revision history .........................................................................................................2
i.1.3 Instrument.................................................................................................................2
i.1.4 Producer ...................................................................................................................3
i.2 Copyright .....................................................................................................................3
i.3 Purpose of This Document .........................................................................................3
i.4 Definitions, Acronyms ed Abbreviations .................................................................3
i.5 Documentation...........................................................................................................3
i.5.1 Applicable Documents..........................................................................................3
i.5.2 Reference Documents ...........................................................................................4
i.6 List of Contents ............................................................................................................5
1. General ........................................................................................................................6
2. System Configuration .................................................................................................6
3. Miura LIS Component ................................................................................................7
3.1. Settings menu ..........................................................................................................8
3.2. Log view ...................................................................................................................8
3.3. General commands ...............................................................................................8
4. Working scenarios .......................................................................................................8
4.1.1. Slave server mode ...........................................................................................8
4.1.2. Host/Query mode ............................................................................................9
5. LIS protocol and Miura specialization .....................................................................9
5.1. Communication Physical Layer ............................................................................9
5.1.1. Connection Establishing Phase ...................................................................10
5.1.2. Conflict Resolution Phase .............................................................................10
5.1.3. Data Transfer Phase ......................................................................................11
5.2. Application Level ..................................................................................................11
5.2.1. Universal Test Id field .....................................................................................12
5.2.2. Sample and patient types ...........................................................................14
5.3. Header message ..................................................................................................14
5.4. PatientInformation message ...............................................................................16
5.5. TestOrder message ...............................................................................................19
5.6. Result message......................................................................................................22
5.6.1. Comment message ......................................................................................23
5.7. Terminator message .............................................................................................25
5.8. RequestInformation Message .............................................................................25
5.9. Keep Alive message .............................................................................................26
5.10. Examples ............................................................................................................27
5.10.1. Analysis Request ............................................................................................27
5.10.2. Sending results to host...................................................................................27

1. General
This document describes the electronic transmission of digital information between
the Miura Series of Clinical Chemistry Analyzers and a Medical computer system.
Specifically, the scope of this document is the communication protocol and
connection method between the Miura and a Host Computer (referred to as the
Host in the following sections of this document).
The protocols used allow bi-directional communication which improves Laboratory

automation with real time data exchange. This includes work-lists, patient data,
and patient final results.
2. System Configuration
The communication between the Miura System and the external Host is compliant
to the IEEE 802.3 standard, that regulates the most common local area network
(LAN) technology based on Ethernet standard. The Miura System Personal
Computer is then provided with an internal network interface (Ethernet interface);
it is linked to the laboratory information local area network through a Hub or
through a Switch Hub the connects several other stations for communication
purposes. The Host Computer is obviously part of the same network and it is
connected in the same manner.
The following diagram shows the functional components of a typical Miura/HOST
Installation.
MIURA FAMILY RS-232C

INSTRUMENT
MIURA PC HUB HOST PC

MIURA SYSTEM AUTOANALYZER
The transmission protocol is TCP/IP. The bit sequence, the transmitted character
structure and the parity check are compliant to the ANSI X3.15-1976 and X3.16-
1976 standards. The transmission speed (in accordance with IEEE 802.3) is at least
10MB/sec.

Refer to the Windows system documentation in order to set up the Host pc in a

laboratory lan.
3. Miura LIS Component
The Miura LIS server is an application called BCLisServer. This manages the data
exchange between the Miura instrument and the Host PC, referred to as HOST.
See the Miura user manual for information on how to use and configure
BCLisServer from the user interface point of view.
When active, Miura LIS is run when Miura software is started. Its icon is located in
the Windows Systray which is normally hidden from the user. Figure 1 shows the
BCLisServer icon located near the system clock in the Systray.
Figure 1: BCLisServer icon in the systray
BCLisServer can be brought to the screen by clicking on the button “Show L.I.S.
interface” located at System Config menu of the Miura software interface.
An interface as shown in figure 2 will be displayed.
Figure 2: Miura LIS server interface

3.1. Settings menu

This menu allows BCLisServer to be configured, Settings are:
Local port (slave mode): The default it is 4000. This is the port used by the server to
waiting for a remote connection.
Keep Alive timing (slave mode): Expressed in seconds, the default is 0. This is the
time interval used to send a packet called (KeepAlive) that is needed to keep the
connection open. Available in slave mode only.
Host/Query mode: This enables/disables host/query mode
Remote port (H/Q only): The default it is 0. This is the port used to communicate
with a remote host when Host/query mode is active.
Remote host (H/Q only): This is the IP address, or the hostname, of the remote host
LIMS system.
Save params: Stores configuration changes.
Test con: Tests the connection with a remote host. It sends an acknowledge, a
sequence of message composed by ENQ, Header and Teminator. (refer to the
following chapters of this document for the specifications of these massages).
3.2. Log view

Logs used for debugging/troubleshooting purposes, this menu shows raw data
exchanged between BCLisServer and the remote host.
3.3. General commands

Lis connection status: This shows the status of the connection. Light green indicates
an active connection, dark green indicates an inactive connection.
Minimize: Minimizes the application to the systray
Close app: Closes the application and disconnects the remote host.
4. Working scenarios
The BCLisServer has 2 modes of operation, these are Host/Query mode or slave
server mode.
4.1.1. Slave server mode

In this configuration, BCLisServer listens and waits for an external connection. This
means that the HOST, is responsible for connection management, one of its tasks is
to check that the connection is kept open.

To avoid disconnection due to a lack of activity caused, as an example, by a

central proxy server, BCLiServer can be configured to send data to keep the
connection active. This is described elsewhere in this manual.
By default, BCLisServer listens on remote port 4000.
In this mode, the instrument waits for data from the Host. Using an active
connection can be used:
 To transmit a worklist
 To ask for results (all or filtering by a specific sample)
Manually sending results to the host is possible, providing an active connection or

having the Host/Query mode option enabled.
In case you use H/Q mode with slave mode, pay attention to not have more than
one connection active at the same time. In this case, only the last connection will
be used to transmit the results.
4.1.2. Host/Query mode

BCLisServer manages the connection to a remote host. It tries to establish a
connection when required. In this configuration it is mandatory to specify the
remote address/name of the host and the host’s remote port.
Host Query Mode can be used to:
 Ask for a specific test for an already programmed sample
 Ask for a whole Worklist
 Send the results after patient validation.
5. LIS protocol and Miura specialization
This Section describes:
1. Communications – The Physical Layer

2. Communications - Level 1
3. The Application Level
4. Typical Communication Scenarios.
5.1. Communication Physical Layer

Based on ASTM E1381, this level defines the connectivity procedures used such as
sequence control, error detection and recovery. This level makes use of a protocol
based on ASCII codes.

The information, in any instant, transfers in one direction only (one communication
element becomes the “sender” the other is a “receiver”).Correct Message
reception (or not) is confirmed by the receiver. The transfer of information is split
into 3 distinct phases, these are:
1.Establish a connection phase;

2.The Conflict resolution phase;
3.The Data transfer phase.
The TCP/IP port used for the connection can be configured by the user.
The Host Computer:
 Must have a valid connection to the Miura Computer,

 Must run a “connect TCP/IP”, to the IP address assigned from the network
administrator to the Miura System, on the port being used.
 If the LIS is enabled in the Miura application, the BCLisServer is listening and
ready to communicate.
5.1.1. Connection Establishing Phase

The “sender” notifies the “receiver” the need to transmit data by sending an
<ENQ> to the receiver. The receiver answers with <ACK> in order to confirm the
availability to receive data . In this case the Data transfer phase can start.
If the receiver answers with a <NACK>, the sender must wait at least 10 seconds
before trying again.
NOTE: during this phase the receiver can only receive <ENQ>, <ACK> & <NACK>.
Other messages are ignored.
5.1.2. Conflict Resolution Phase

If the receiver gets <ENQ> as the answer to its previous <ENQ> request, the Miura
Computer has the priority to transmit data. This means that the Host cannot send
other messages and must wait for the next <ENQ> coming from the Miura
Computer. In this scenario, it must respond with an <ACK> and it becomes a
receiver. The Miura computer must wait a minimum of 1 second prior to
transmitting the second <ENQ>.

5.1.3. Data Transfer Phase

Messages are transmitted in “blocks” called frames. Each block can contain a
maximum of 2048 characters. This includes flow control and error checking data.
The structure of each block is described in the following table:
Chracters Description Value

<STX> Start of text 02H
FN Frame number ‘0’-‘7’
text Message content
<ETX> End of text 03H
C1 Checksum Most Significant character ‘0’-‘9’ o ‘A’-‘F’
C2 Checksum Last Significant character ‘0’-‘9’ o ‘A’-‘F’
<CR> Carriage return 0DH
<LF> Line Feed 0AH
The frame number allows the receiver to recognize the block(s) that have been re-
transmitted. This number is sent as an ASCII character and it is increased for each
message up to 7, (the number “7” is followed by “0”). The first frame in the transfer
phase is numbered 1.
The checksum allows the receiver to recognize a message that has not been
correctly received. This is calculated as the arithmetic sum of all received bytes
without the carry-over (the calculation doesn’t use: <STX>, the checksum
characters and the final <CR> and <LF> ).
The data transfer phase is terminated with the message <EOT> (End of Text) - 04
hexadecimal (HEX).
Other special characters:
Chracters Description Value
<ENQ> Enquire 05H
<EOT> End of transmission (to terminate data transfer) 04H
<ACK> Message Ackowledgement 06H
<NACK> Message discarded 15H
<KeepAlive> Keep alive packet 16H
5.2. Application Level

Based on the LIS2-A2, the list of frames used by Miura instruments is shown in the
following table. This includes the definition of custom fields.
Message Description Code

Header Defines fields delimiter ’H’

Message Description Code

PatientInformation Information about the patient ‘P’
TestOrder Request of analysis ‘O’
Result Results ‘R’
Comment Result comments ‘C’
Terminator End of data transmission ‘L’
RequestInformation Request of results/tests ‘Q’
The field construction of each type of frame is described in the following sections
of this document. The defined sequences must always be present in order to allow
the correct interpretation of messages.
Empty fields that have no meaning for the Miura System can be “null value”, this
means that no characters are sent between the headers or field delimiters.
Note – In the following Message Description Tables, the column MS (Miura

Sensitive) can get the following values:
 “N” - Required field - the field itself must have a value different from null
 “O” - Optional field – the field itself can have any value (including null)
because it is not used.
 “OU “ – optional field used by the software if the value is not null
Note: In the following Message Description Tables, the column “L” defines the
message length for the fixed length fields. Length for the fields that they have not
fixed length is expressed as number in brackets. (i.e. (20))
5.2.1. Universal Test Id field

This field is common to several different kinds of frame. It is composed of 4
elements and is used to define a test.
The four parts which are defined below are the universal test identifier, the test
name, the test identifier type, and the manufacturer-defined test code. All test ID
parts must be separated by a component delimiter and are position dependent.
Element Name Description L Values Opt

number
1 Universal Test ID 1 null O
(Part 1)
(Part 2)
(Part 3)

Element Name Description L Values Opt

number
4 Manufacturer’s or Identifies a test 2 Test barcode N
Local Code (part 4) using Miura
barcode
identifier (see
below)
In the case of a Q frame, the universal test id field may be composed by a single
string having the value of “ALL”. This indicates a request for data for all methods.
In all other cases the standard format ”^^^bc” is required
5.2.1.1. Manufacturer’s or Local Code

This element is only part of the field used by Miura systems It consists of the
barcode associated to the method assigned by I.S.E. srl for its reagents or by the
final user when using open systems that are running a different set of reagents.
The Miura system automatically generates a file listing all of the methods stored.
This is saved any time that the operator saves or deletes a method. The file over-
writes any previous version.
This file is exported into a special folder for user handling; it can be copied on to
removable media or accessed by the Host computer when the MIURA managing
PC is incorporated into a LAN. In this case, the “MethodList” folder must be
“shared” in network in order to allow a host computer to download and process
the file.
The exported file is named method.csv (with the delimiter “;”).

IT IS VERY IMPORTANT TO ACCESS THIS FILE ANY TIME A NEW METHOD IS ADDED IN
ORDER TO UPDATE THE METHOD LIST.
This file also indicates the association between methods and their Id Code. The file
is created every time a method is saved and over-writes the last one.
Location:
%ProgramRoot% \ MethodList
File name:
methods.csv
File Structure Format:
Record delimiter character: ascii code 10 (Line Feed)
Record Field delimiter: ascii code 59 (‘;’)
Record fields:
Method Name Method Method Method
Acronym Barcode Internal Index
Fields meaning:
 Method Name: name given to the analysis method
 Method Acronym: acronym given to the analysis method.

 Method Barcode: identification barcode of the analysis method

(placed on the reagent bottle). Associate this value
to the second element of UniversalTestID.
 Method Internal Index: identification code of the analysis method.
5.2.2. Sample and patient types

Miura instruments allow a user to use a custom set of sample/patient types in order
to suit different requirements, such as adding different categories of patients to
diversify the normal value based on age.
For each of these custom types, a single character has been defined that is used
in LIS communications.
To view a complete list of available sample/patient types, refer to the Miura user
manual. The information is in the “”Extra procedures” menu Section.
5.3. Header message

Element Field Description L Values Opt
number
1 RecordTypeID Message 1 ‘H’ N
Identifier
2 DelimiterDefinition Delimiter 4 Field delimiter I N
definitions
Repet delimiter \
Component delimiter ^
Escape delimiter &
3 MessageControlID O
4 AccessPassword O
5 SenderID Instrument (20) “Miura” O
name
6 SenderStreetAddress O
7 ReservedField O
8 SenderTelephoneNumbe O
r
9 CharacteristicsOfSender O
10 ReceiverID O
11 Comment O
12 ProcessingID Message 1 ‘P’ O
interpretation
mode (P-
production)


number
13 VersionNumber 7 “LIS2-A2” O
14 DateAndTimeOfMessage 14 Format: O
YYYYMMDDHHMMSS
Where:
Field delimiter = vertical bar (|) Latin-1(124)
Repeat delimiter = backslash (\) Latin-1(96)
Component delimiter = caret (^) Latin-1(94)
Escape delimiter = ampersand (&) Latin-1(38).
Example:
<STX>0H|\^&|||Miura|||||||P|LIS2-A2|20110112100000<ETX>1F<CR><LF>

5.4. PatientInformation message

Elemen Field Description L Values Opt
t
number
1 RecordTypeID Message Identifier 1 ‘P’ N
2 SequenceNumber Message sequence N
number
3 PracticeAssignedPatientID O
4 LaboratoryAssignedPatientID O
5 PatientIDNumber3 O
6 PatientName Patient Name (100) Surname^Name O
7 MotherMaidenName
8 Birthdate 8 Fomat: YYYYMMDD O
9 PatientSex 1 M, F, or U O
10 PatientRaceOrEthnicOrigin W - white O
B - black
O - Asian/Pacific
Islander
NA - Native
American/Alaskan
Native
H - Hispanic
11 PatientAddress O
12 ReservedField O
13 PatientTelephoneNumber O
14 AttendingPhysicianID O
15 SpecialField1 O
16 SpecialField2 O
17 PatientHeight O
18 PatientWeight O
19 PatientKnownOrSuspectedDiag O
nosis
20 PatientActiveMedications O
21 PatientDiet O
22 PracticeFieldNumber1 O
23 PracticeFieldNumber2 O
24 AdmissionAndDischargeDates O
25 AdmissionStatus OP - outpatient O
PA - preadmit
IP - inpatient
ER - emergency
room
26 Location O
27 NatureOfAlternativeDiagnostic O
CodeAndClassifiers

Elemen Field Description L Values Opt

t
number
28 AlternativeDiagnosticCodeAnd O
Classification
29 PatientReligion P - Protestant O
C - Catholic
M - Church of the
Latter Day Saints
(Mormon)
J - Jewish
L - Lutheran
H - Hindu
30 MaritalStatus M - married O
S - single
D - divorced
W - widowed
A - separated
31 IsolationStatus ARP - antibiotic O
resistance
precautions
BP - blood and
needle precautions
ENP - enteric
precautions
NP - precautions for
neutropenic patient
PWP - precautions
for pregnant women
RI - respiratory
isolation
SE -
secretion/excretion
precautions
SI - strict isolation
WSP - wound and
skin precautions
32 Language O
33 HospitalService O
34 HospitalInstitution O
35 DosageCategory 2 A - ADULT, O
P1 - PEDIATRIC (one
to six months),
P2 - PEDIATRIC (six
months to three
years)

Example:
<STX>
2P|1||0016-
20101012||SURNAME^NAME||19800907|M|W|||||||||||||||||||U|S|||||A
<ETX>72<CR><LF>
With this revision of the protocol, the Miura ignores patient private data, so a P
frame may be truncated using the frame number, message identifier and
sequence number.

5.5. TestOrder message

Element Field Description L Values MS
number
1 RecordTypeID Message Identifier 1 ‘O’ N
2 SequenceNumber Message N
sequence number
3 SpecimenID Patient Barcode N
4 InstrumentSpecimenID O
5 UniversalTestID Identification of (20) ^^^barcode_test N
the test method to
run
6 Priority Request priority 1 S stat N
R routine
7 RequestedDateAndTime Format: O
YYYYMMDDHHMMSS
8 SpecimenCollectionDateAndTi O
me
9 CollectionEndTime O
10 CollectionVolume O
11 CollectorID O
12 ActionCode 1 C cancel request O
for the battery or
tests named
A add the
requested tests or
batteries to the
existing specimen
with the patient
and specimen
N new requests
accompanying a
new specimen
P pending
specimen
X specimen or test
already in process
Q treat specimen as
a Q/C test
specimen
13 DangerCode O
14 RelevantClinicalInformation O

Element Field Description L Values MS

number
15 DateTimeSpecimenReceived O
16 SpecimenDescriptor Type of sample 1 S N
(serum, urine etc.)
Refer to sample
type table listed on
the instrument
17 OrderingPhysician O
18 PhysicianTelephoneNumber O
19 UserFieldNumber1 Type of the patient 1 M N
(male, female, new
born etc.) Refer to
patient type table
listed on the
instrument
20 UserFieldNumber2 O
21 LaboratoryFieldNumber1 O
22 LaboratoryFieldNumber2 O
23 DateTimeResultsReportedOrLa O
stModified
24 InstrumentChargeToInformatio O
nSystem
25 InstrumentSectionID O
26 ReportTypes 1 O order record; user N
asking that analysis
be performed
F Final result
Z no record of this
patient (in response
to query)
Q response to query
27 ReservedField O
28 LocationOfSpecimenCollectio O
n
29 NosocomialInfectionFlag O
30 SpecimenService O
31 SpecimenInstitution O
The UserFieldNumber2 is used to send a custom information from the host to the
instrument. This information is shown in Miura software interface close to the Sample
barcode field. A possible use of this field is to memorized a surname of the sample,
without compiling the whole Patient message.
Example:
<STX> 3O|1|6549909368||^^^f7|R|20110922105919|||||N||||S|||M|||||||O|||||

<ETX>69<CR><LF>

5.6. Result message

number
1 RecordTypeID Message Identifier 1 ‘R’ N
2 SequenceNum Message sequence number N
ber
3 UniversalTestID (20) ^^^barcode_t N
est
4 DataOrMeasur Result value, in float format (i.e.:
(20) N
ementValue 23.354)
5 Units Measurement Unit (text containing (20) N
the used measurement unit)
6 ReferenceRan Reference values, in format: min- (50) min-max N
ges max (i.e.: 0.2-3.45)
7 ResultAbnormal 2 L below low N
Flags normal
H above high
normal
LL below panic
normal
HH above
panic high
N normal
A abnormal
8 NatureOfAbnor O
malityTesting
9 ResultStatus 1 F final results N
10 DateOfChang Standard, execution date 14 Format: O
eInInstrumentN YYYYMMDDHH
ormativeValues MMSS
OrUnits
11 OperatorIdentif Name of the operator N
ication
12 DateTimeTestSt O
arted
13 DateTimeTestC 14 Format: O
ompleted YYYYMMDDHH
MMSS


number
14 InstrumentIdent “Miura” (20) N
ification
Example:
<STX>5R|1|^^^b9|79.146248|mg/H|10.000000:55.000000|H||F||admin|||Miura<ETX>8D<CR
><LF>
5.6.1. Comment message

A Comment frame may be included after a Result frame, if a result comment must
be notified. For each Comment message sent, only one comment per result is
included.

number
1 RecordTypeID Message 1 ‘C’ N
Identifier
2 SequenceNumber Message N
sequence
number
3 Comment source This field 1 ‘I’ clinical instrument N
specifies the system
comment
origination
point:
4 Comment text Result comment (4) INS_CMT (see table 1 N

for possible values)
5 Comment type Comment ‘I’ instrument flag(s) N
qualifier comment
Table 1: instrument comment values
Value Description
BOR Blank of range
SBD Substrate deplation
OBF Out of best fit
OST Out of standard
ONO Out of normal
OLM Detection limit reached
OLN Out of linearity
IAH ISE Air in hardware

Value Description
ICD ISE Cal A drift
IMN ISE Mv noise
IN2 ISE Mv noise 2
IMO ISE Mv out
IO2 ISE Mv out 2
IOS ISE out of slope
UMD User modified
Example:
<STX>6C|1|I|OBF||<ETX>06<CR><LF>

5.7. Terminator message

number
1 RecordTypeID Message 1 ‘L’ N
Identifier
2 SequenceNumb 1 N
er
3 TerminationCode 1 N normal termination N
T sender aborted
R receiver requested abort
E unknown system error
Q error in last request for information
I no information available from last

query
F last request for information

processed
Example:
<STX>4L|1|N<ETX>FA<CR><LF>
5.8. RequestInformation Message

number
1 RecordTypeID Message 1 ‘Q’ N
Identifier
2 SequenceNumber 1 N
3 Sample Sample (200) Barcode sample N
Identifier or “ALL” string
4 EndingRangeIDNumber O
5 UniversalTestID barcode (20) ^^^barcode_tes N
t or “ALL” string
6 NatureOfRequestTimeLimits O
7 BeginningRequestResultsDateAndTime O
8 EndingRequestResultsDateAndTime O
9 RequestingPhysicianName O


number
10 RequestingPhysicianTelephoneNumbe O
r
13 RequestInformationStatusCodes 1 F final results N
(host request)
O requesting test
orders
(instrument
request)
Example (request all results):

<STX>2Q|1|||||||||||F<ETX>1F<CR><LF>
5.9. Keep Alive message

The KeepAlive message is a custom message implemented in order to prevent
disconnections.
This packet is sent cyclically from BCLisServer to the remote , its sole purpose is to
keep the connection open.
This message is useful when a large LAN or a WAN is controlled by a central proxy
server. In this scenario the proxy could disconnect the remote connection if it has
been inactive for a long period of time. To avoid disconnection, BCLisServer can
be configured to send this KeepAlive message to the host every x seconds.
An acknowledgement from the host is not required, but replying with the same
message is strongly suggested.

5.10. Examples
In the following sub-paragraphs, some of the communication scenarios.
5.10.1. Analysis Request

REMOTE HOST H <ENQ>
MIURA M <ACK>
H: <STX>1H|\\^&|||HOST-1|||||||P||<ETX>F0<CR><LF>
M: <ACK>
H: <STX>2P|1|<ETX>AE<CR><LF>
M: <ACK>
H: <STX>
3O|1|6549909368||^^^f7|R|20110922105919|||||N||||S|||M|||||||O||||
|<ETX>69<CR><LF>
M: <ACK>
H: <STX>
4O|2|6549909368||^^^f1|R|20110922105919|||||N||||S|||M|||||||O||||
|<ETX>65<CR><LF>
M: <ACK>
H: <STX>5L|1|N<ETX>F1<CR><LF>
<EOT>
5.10.2. Sending results to host

MIURA M <ENQ>
REMOTE HOST H <ACK>
M: <STX>1H|\\^&|||MIURA|||||||P||<ETX>D2<CR><LF>
H: <ACK>
M: <STX>2P|1|<ETX>AE<CR><LF>
H: <ACK>
M: <STX>
3O|1|6549909368|6549909368|^^^f7|R|20110922105919|||||N||||S|||M||
|||||F|||||<ETX>7B<CR><LF>
H: <ACK>
M: <STX>
3R|1|^^^f7|2.247595|mg/l|1.2000:5.3000|N||F||admin|||Miura<ETX>E7<CR><LF
>
H: <ACK>
M: <STX>4C|1|I|BOR||<ETX>43<CR><LF>
H: <ACK>
M: <STX>
5O|2|6549909368|6549909368|^^^f1|R|20110922105919|||||N||||S|||M||
|||||F|||||<ETX>78<CR><LF>
H: <ACK>

M: <STX>
6R|2|^^^f1|1.1|mg/l|1.2000:3.1000|L||F||admin|||Miura<ETX>CF<CR><LF>
H: <ACK>
M: <STX>7L|1|N<ETX>FD<CR><LF>
H: <ACK>
<EOT>


MNT-10910-01-F MIURA Connessione LIS - ENG

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MNT-10910-01-F MIURA Connessione LIS - ENG

Uploaded by

Copyright:

Available Formats

I.S.E.

– Sistemi Intelligenti Elettronici

Miura Instrumentation Series

L.I.S. Connection – Technical Manual

I.S.E. S.r.l. – Italy Rome MNT-10910-01-F Rev.E ENG

i.1 Identification Data

i.1.2 Revision history

 Revision E  Modified example par. 3.4.1

I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 2/28

i.3 Purpose of This Document

i.4 Definitions, Acronyms ed Abbreviations

i.5.1 Applicable Documents

I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 3/28

i.5.2 Reference Documents

ASTM, code E1381-02

I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 4/28

i.6 List of Contents

I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 5/28

The protocols used allow bi-directional communication which improves Laboratory

MIURA FAMILY RS-232C

MIURA PC HUB HOST PC

I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 6/28

Refer to the Windows system documentation in order to set up the Host pc in a

3. Miura LIS Component

Figure 1: BCLisServer icon in the systray

Figure 2: Miura LIS server interface

I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 7/28

3.1. Settings menu

3.2. Log view

3.3. General commands

4.1.1. Slave server mode

I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 8/28

To avoid disconnection due to a lack of activity caused, as an example, by a

Manually sending results to the host is possible, providing an active connection or

4.1.2. Host/Query mode

5. LIS protocol and Miura specialization

This Section describes:

1. Communications – The Physical Layer

5.1. Communication Physical Layer

I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 9/28

1.Establish a connection phase;

The Host Computer:

 Must have a valid connection to the Miura Computer,

5.1.1. Connection Establishing Phase

5.1.2. Conflict Resolution Phase

I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 10/28

5.1.3. Data Transfer Phase

Chracters Description Value

5.2. Application Level

Message Description Code

I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 11/28

Message Description Code

Note – In the following Message Description Tables, the column MS (Miura

5.2.1. Universal Test Id field

Element Name Description L Values Opt

I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 12/28

Element Name Description L Values Opt

5.2.1.1. Manufacturer’s or Local Code

The exported file is named method.csv (with the delimiter “;”).

I.S.E. S.r.l. – Sistemi Intelligenti Elettronici 13/28

 Method Barcode: identification barcode of the analysis method

5.2.2. Sample and patient types

5.3. Header message