HL7 Data Sharing Protocol

Catalog
1 Summarize
1.1 Purpose
1.2 Accommodation
1.3 Character set、Data coding
1.4 Standard content of HL7 involved in file
2 Communication process
2.1 Communication protocol
2.2 Message type and Interface of data transmission
2.3 NET process
3 Message type
3.1
3.2 MSH segment
3.3 Observe coding convention in report
4 Broadcast message
4.1 ASM broadcast message online
4.2 Broadcast message online of CMS and Gateway
5 Message about Bed list
5.1 Message content
5.2 Message type
5.3 Message segment
6 TCP connection to online message
7 Patient information altering message
7.1 Message content
7.2 Message form
7.3 Message segment
8 Query message
8.1 Message content
8.2 Message form
8.3 Message segment
8.4 Example of query message
9 Query message feed back
9.1 ORF query success
9.2 ACK query failure
10 Active observation of reported message
10.1 Observation report of parameter data
10.2 Observation report of parameter alarm setting
10.3 Observation report of parameter alarm message
10.4 Observation report of module loading and uninstalling
10.5 Observation report of module configuration
Appendix A Module/Parameter/Alarm ID referring to <Definition of Module ID of Patient
Monitor>
Appendix B Units list of Transmission Observation
1 Summarize
1.1 Purpose
Patient Monitor Data Sharing Agreement (hereafter referred to as MDS) describes in detail the
PROGETTI Monitor products and third-party information systems via TCP / IP protocol to
implementMonitor in the form of HL7 standard data sharing agreement, the contents of this
document to guide third-party information PROGETTI HL7 Protocol system to monitor
product data receiver development.

Communication model in MDS, PROGETTI Monitor products work on the server (server) mode,
third-party information systems work on the client (client) mode, server listen for requests from
the client, and request specific data content for monitoring data Send, server supports up to 5
client data requests.

1.2 Adaptation range

This agreement applies to the following Monitor products of PROGETTI company
● A series monitors (A series patient monitor) (hereinafter referred to as ASM)
● Central monitoring system (CMS)
● MDS Gateway (hereinafter referred to as Gateway)
MDS Gateway is a software system for medical institutions have PROGETTI M Series monitors,
but the central monitoring system is not configured, but also need to monitor data to HL7 format to
exportthe case, you need to install the MDS Gateway software.

1.3 Character set, data coding

1.3.1 HL7 standards in the MSH segment MSH-18 field indicates the message using the character
sets, UNICODE encoding used in this Agreement, in the transmission, patient name resolution,
monitors, etc. to note the name of its encoding.

1.3.2 The protocol used in the transmission data PROGETTI parameter module, alarm parameters
such asID defined in detail see <Patient Monitor module ID definition>

1.4 Documents related to the HL7 standard content

This Agreement is based on the HL7 protocol version V2.3.1, involved in the HL7 standard as
follows:
● Chapter 2 Control / Query
● Chapter 3 Patient Administration
● Chapter 7 Observation Reporting
2 Communication process
2.1 Communication protocol
Server, Client during the data transfer using TCP / IP protocol and HL7 standards recommended
LLP (Lower Layer Protocol) protocol.
2.11 LLP agreement
TCP is based on a continuous byte stream protocol, can not distinguish between the beginning and
end of HL7 messages. LLP to pass through the local area network using TCP the most common
mechanism of HL7 messages. LLP in the use of an HL7 message when a message must be used to
encapsulate the end of the first and the message in order to distinguish between a beginning and end
of HL7 messages. Usually the header / tail identifies the use of non-printable ASCII codes used in
this Agreement are as follows:
● header: one byte, the ASCII value of 0x0B;
● HL7 message: the standard HL7 messages, see the specific format of HL7 V2.3.1;
● messages tail: two bytes, the ASCII value 0x1C and 0x0D;

2.2 Message types and data transmission interface

2.2.1
TCP / IP link layer
Server and Client side in the communication process needs to use the communication port as
follows:
● Server side CMS mode UDP broadcast port: 52000;
● Server-side Broadcast ASM mode UDP port: 52002;
● Server-side Gateway mode, UDP broadcast port: 52001;
● Server-side TCP listening port: 51000 for and accept client connection requests, established TCP
connection, send monitoring data.
● Server-side Gateway, CMS mode UDP query port: 51001 for Gateway, CMS mode online
machines to receive the list of Client-side query

2.2.2
Message type
Communication process involves the following message types:

Data or messages Send or receive Interface Protocol Transmission

time direction
CMS Central Monitor Once per second 52000 UDP LAN
Station Broadcast
News Online
Gateway mode Once per second 52001 UDP LAN
Broadcast News
Online
Monitor(ASM) Once per second 52002 UDP LAN
Broadcast News
Online
TCP connection Once per second 51000 TCP Server-Client
maintenance message Client-Server
Bed When server 51001 UDP Server-Client
list(CMS/Gateway) receives a query
Patient Information 1. TCP client to 51000 TCP Server-Client
 establish and
receive query
messages (QRY) to
send;
2. were sent when
the information
changes;
Monitoring data query Client needs to 51000 TCP Client-Server
message (QRY) query any time
List of query messages Query client once 51001 UDP Client-Server
beds (QRY) every 5 seconds

Successful query Server receives a 51000 TCP Server-Client

response message client's QRY
ORF; messages 51001 UDP
Query failed response
message ACK;
Parameter data 1. continuous 51000 TCP Server-Client
measurement
parameters: once
per second;
2. intermittent
measurement
parameter: send the
completed
measurement;
Physiology Alarm Once per second 51000 TCP Server-Client
Technology Alarm Once per second 51000 TCP Server-Client
Parameter alarm limit 51000 TCP Server-Client
1. TCP connection
is established and
the client query
message received
by the passive
transmission;
2. parameter sent
when the alarm
limit changes;
Parameter alarm levels 1. TCP connection 51000 TCP Server-Client
is established, and
when queried by
clients to send a
message;
2. sent when the
alarm level change;
Module loading 1. TCP connection 51000 TCP Server-Client
messages establishment and
received a message
the client sends
QRY;
2. A module into
the active send or
open module;
Module unload Are sent when the 51000 TCP Server-Client
message module is pulled
off
Module configuration Sending module 51000 TCP Server-Client
 change message configuration is
changed, such asthe
ECG lead
switching module

2.3 The network processing

2.3.1 communication connection establishment process is as follows:
● Server to broadcast its own online news network
● Server for TCP listener
● Client Server online message receives a connection request to the Server
● Server Client connections accepted
● Client to Server initiated data request to start sending care Server Data
● Server package data in accordance with this agreement, the frequency of once per second to
send data to the Client
● the process of transferring data to the Server Client should periodically issue a query, a list of
machines to obtain the latest information (CMS, Gateway mode)
● the transmission process, TCP connection to both the frequency of once per second to send
heartbeat packets to each other, can not receive heartbeat packets consecutive 10s, as the other
dropped.

2.3.2 Online Radio News

Server starts online broadcast to the network host to send a message to notify their existence,
Server work patterns are different, the port is different broadcast messages, see table below:

Mode of the the port message content

CMS 52000 CMS name
MDS Gateway 52001 Gateway name
ASM 52002 basic information about the current care
patients

2.2.3 TCP connection establishment and maintenance of

● Server starts, start listening TCP port 51000, Client Server receives the online broadcast
message to the Server online after the test, should be Server initiated and established a TCP
connection.
● Client-side in establishing a connection to send data requests to the Server (TCP port), Server
receives the data request, the start frequency of 1 per second sent to the Client monitoring data
(physical parameters, alarm configuration information). A periodic data (such as NIBP, patient
information changes, configuration changes) in a measured value or change to send.
·After starting transmission of data, TCP connection need to rely on the maintenance of Server,
Client sends heartbeats per second wave to each other to represent the active connection, the
connection of any party does not receive heartbeat packets consecutive 10s, is that the other side is
not online, should take the initiative off Open connection, stop receiving and sending HL7 data.
● Server-side support up to five Client for data transmission, using the time to note this limitation.

2.3.4 query messages

According to the different operating modes or product, we will check the message is divided
into two, one bed list of query messages, the second is the monitoring data query message, as
follows:

Mode Query Port Supporting message

CMS TCP(51000) Monitoring data query message
UDP(51001) Bed List query message
MDS Gateway TCP(51000) Monitoring data query message
UDP(51001) Bed List query message
ASM TCP(51000) Previous Patient Basic information
·a list of query messages beds
The query message is only for two modes of CMS and Gateway, which aims to check the current
CMS or the Gateway monitor online, get the current line monitors the IP and other information. In
both modes, Client-side Server's UDP port 51001 to send a list of query messages beds, Server
receives inquiries sent to the Client-side beds in the current list of online information.
Because the connection with the CMS or the Gateway monitor the Client can not
directly access online information, it should receive the CMS Client or Gateway on-line
message to send queries to the Server beds list information, and periodically during the data
transfer (5s Or so) list of information to send queries timely access to beds beds online,
offline status.
Client A series of direct and monitor the communication, no need to send this message
·monitoring data query message
Monitoring data query message is defined in the list of query messages beds other than query
messages, such as parameter data inquiry message, the alarm limit / alarm level of query messages,
query messages and other patient information. Query messages according to the different
operating modes, the query slightly different.
A series of direct client care, and data transmission, the query conditions need to include the IP
address information Server, just the specific query can be specified;
When the client and the CMS, Gateway Communications, query in addition to containing specific
query, but also a list based on the service side of the bed, clear the query monitor the IP address in
order to inform the Server Monitor to send which data from Taiwan and Taiwan.

2.3.5 Monitoring data transmission

Client-Server with TCP Client connection is established and received only when the correct query
messages to send monitoring data to the Client, or will not send any monitoring data.
Server sends monitoring data through the TCP port (51000) for all the physiological parameters,
technical alarm, physiological alarms, patient information, configuration information to be sent
through this. Send data at 1 second intervals periodically to send the process, the communicating
parties have to each other under the heartbeat packets to determine whether there.

2.3.6 Disconnect
In the face of the following data is sent when the Server will stop, disconnect the current
connection, and make clear the current connection and termination of the operation.
● Server Client over 10s did not receive the heartbeat packet;
● In the CMS, Gateway mode, has been connected to the bedside monitor from Gateway
monitoring network in the CMS and dropped;

3 message types
3.1 Message Types

Each HL7 message type has a specific message, the message type that the message contains what
kind of health related information, but also determine what to include in the message section.
Consumers usually in the HL7 message type the first paragraph (MSH) in the ninth field (Fields)
MSH-9 is given by the message type code and event type code for common components. The
following table shows the document in guiding software development, HL7 message types used in
the main
Message Description Event
ADT Patient Administration A01 Patient Diagnosis
QRY Query R02 Monitor Result Query
ORF Response to a QRY message R04 Query Answer
ACK General acknowledgment message Blank
ORU Unsolicited transmission of an observation R01 Automatic Monitor
message Report

Message content and message control ID message type is uniquely determined. HL7 message
control ID did not make uniform regulations but reserved for developers to customize as needed.
Message Control ID in the MSH segment in the first 10 fields are given in MSH-10, the document
agreed upon by the message control ID of the appendix in the document has been given, the
subsequent chapters introduce the relevant HL7 message type to use these controls ID.

3.2 MSH segment

Each HL7 message must only contain a MSH segment, the segment is the first segment of HL7
messages, pointing out the need to parse HL7 message delimiter, message type, message control
ID and other necessary information, the next figure shows the MSH segment Composition:
S/N lengt Type optiona usable name Memo
h l
1 1 ST R Yes Field seperator ‘|’
2 4 ST R Yes Unicode ‘^~\&’
 9 7 CM R Yes Message Type
10 20 ST R Yes Message control
ID
11 3 PT R Yes processing ID ‘P’
12 60 VID R Yes Version ID ‘2.3.1’
18 16 ID O yes Unicode set ’UNICODE’
Given a large number of documents will appear on the HL7 segment presentation, we will refer to
HL7 standards to the table described in paragraph form, the next question referred to in paragraph
form about HL7 are used in the form of a document, and that we care about the characters on
Described in paragraph listing and description. The following table header of the following
documents to facilitate the preparation of instructions and reading:

Field number (SEQ): the serial number field in the segment, starting from 1;
Length (LEN): field length, in bytes;
Data Type (DT): field data type is defined by HL7 standard data types;
Whether to use (Used): whether to use the field, Yes-use, No-do not use;
Field Name (Field Name): Field Name;
Notes (Description): Notes on the field notes;
MSH | ^ ~ \ &||||||| ORU ^ R01 | MsgCtrlID | P | 2.3.1 |||||| ISO8859_1 | (map)

3.3 Observations in the coding conventions

Guardianship of the HL7-based data sharing is based on HL7 standard secondary development. In
the number of shared custody, the majority of monitoring data, such as parameters, alarm limits,
alarm information, alarm level, they have a message via HL7 OBX segment completed. In the OBX
segment, HL7 does not provide the relevant clinical data transmitted code (eg, observation ID,
observation sub-ID, parameter ID,) the provisions, but rather the determination of the code leftto
the application developers, this , many of the design parameters of the report because of the encoding
parameters of different developers are quite different. Therefore, characteristics of the document for
the product involved in the report parameters and patient Clinical Informatics specifically define
their own coding system, the client and server during the secondary development of HL7 must
follow the code conventions, or else both parties will not engage in normal communication
Interactive work.
Agreement related to the code later in the appendix are listed in tabular form for Client-side software
used to receive data.

4 Broadcast News

All server and client interactions are based on information and monitoring data in the form of HL7
messages for transmission, from the beginning of this chapter will document the different types of
messages contained in the content, message format, the section contains a detailed definition. The
two sides interact in the communication and data transfer command when the message must be in
accordance with the document describes the format, to ensure that communications both to work.
Here's broadcast messages. Broadcast news has sent the server to inform the client can send query
requests. The following described previously broadcast messages according to the type and
content of the different detailing the content of broadcast messages.

4.1.1 message content

ASM A series of online radio message from the monitor of the HL7 interface through port
52002 sent to the entire network, inform the passenger-side their own online information,
including the following:
● department name
● bed number (machine number)
● patient name and ID
● room number and bed number
● IP address and port number
● patients that
● machine name

4.1.2 Message Format

HL7 message format specified using the syntax notation for the segment: MSH EVN PID PV1
{OBX}, {OBX} indicates that the field can be repeated in the message, for example as follows:
MSH | ^ ~ \ &||||||| ADT ^ A01 | BM01 | P | 2.3.1 | EVN | | 00000000 | PID | | | 201011161506 | |
Patient Surname ^ Patient Name | PV1 | | I | ^ Room 1 ^ ICU & Bed 1 & 3293316523 & 51000 &
1 ||||||||||||||| A | OBX | | ST | 6304 ^ MonitorName | | A8 |||||| F |

News Section 4.1.3

MSH Message Header Section 4.1.3.1
MSH segment defines the message header the purpose, origin, destination addresses and details of
the message syntax, the fields in paragraph (Field) may refer to 3.2 of the meaning of fields in the
MSH table. This document on the message type and message control ID is defined as follows:
● type of message (MSH-9): ADT ^ A01
● Message Control ID (MSH-10): BM01
For example:
MSH | ^ ~ \ &||||||| ADT ^ A01 | BM01 | P | 2.3.1 | <CR>
HL7 V2.3.1 forth in the message must be used between segments separated by carriage return
symbols, and its ASCII code is 0x13. Content described in this document are used to represent the
carriage return symbols <CR> symbols.

4.1.3.2 Pieces of type information in EVN

EVN segment is used to accept the application of information to pass the necessary trigger event,
the composition used in the field, defined as follows:
 S/N lengt Type optional usable Name Memo
h
2 26 TS R Yes Record date If the accepting timeof
and Time patient is date, the
default field is “0”
For example:
EVN||20101227|<CR>

4.1.3.3 PID patient identifier information

PID segments are all applications of information transfer in patients with identifier information as
the primary means of transmission in this document mainly in patients with ID and patient name,
the composition used in the field, defined as follows:
S/N lengt Type optio usable Name Memo
h nal
3 20 CX R Yes Patient ID List Reserve Patient ID
5 48 XPN R Yes Patient Name Field Format is as
following：
<FirstName>^<LastNa
m>
PID|||201011161506||Zhang^San|<CR>

4.1.3.4 PV1 fragment in patients with treatment

PV1 segment is used to pass information about account information and treatment of patients with
information, the main use of PV1 pass the message ID and patient name patient, the use of the
composition of the field, defined as follows:
S/N lengt Type opti usable Name Memo
h ona
l
2 1 IS R Yes Patient Type ‘I’ （Present intensive patient）
This field has a number of components and
sub-containing components, see:
● PV1-3 patient location
HL7 allows applications to define their own
types of patients, see:
● PV1-3 in patients with type
3 80 PL O Yes Position
Patient

18 2 IS O Yes Patient Type

·PV1-3 patient location

This field contains the number of components from the (component), the document only the first
two components 2,3, so the first component is set to no value components, the components 2,3 is
omitted after the format:
| ^ <room> ^ <bed> |
<room> component used to store the number of patients in the ward, and <bed> be broken down
into the following components and sub-components, to hold more detailed location information
for patients:
^ <Office Name> & <bed id> & <TCP Addr> & <TCP Connect Port> & <Patient Admitted Flag>
^
<Patient Admitted Flag> that patients identify, document the value of the sub-components to do
the following provisions:
‘1’：means the patient is accepted
'0 ': means the patient is not Admitted.
● PV1-3 Patient’s type
Definition of patient’s type as follows:
'N': means the patient type for infants (Neonate)
'A': means the patient type for adults (Adult)
'P': means the patient type for children (Pediatric)
'U': means the patient type is unknown (Unknown)
PV1 example:
PV1||I|^Room 1^ICU&Bed 1&3293316523&51000&1|||||||||||||||A|<CR>
We know from the above description of the PV1 segment with following patient information:
The patient is adult ('A') hospitalized patient ('I'), the room number is Room 1, Bed No. is
Bed 1, belongs to ICU department. The monitor IP address of this patient is 3293316523, its TCP
port number is 51000.
4.1.3.5 OBX observation information
OBX Information segment is for the transmission of a single observation task or observation
report, is the smallest non-divisible indivisible segment, whose main purpose is to tranfer the
relevant information of the observation report. OBX field of the information, defined as follows:
Fiel Leng Data Opti Field Name Remarks
d th Type ons Valid
No.
2 2 ID R Yes Value type Data type: 'ST'
3 80 CE R Yes Observation ID Application definition
4 20 ST O No Observation sub-ID No value
5 65K R Yes Observations Application definition
(results)
6 60 CE O No unit Transfer with the default
unit when observations
already defined

7 60 ST O No Reference range
11 1 ID R Yes observation status Stay at 'F', means it is the
final result
13 20 ST O No User-defined path
 check
14 26 TS O No Observation Date / Format:
Time YYYYMMDDHHMMSS

● OBX-3 Observation ID
OBX-3 field contains a number of parts, this information is only the first two parts of OBX-3
field, as follows:
<ID>: means the specific observation ID, find their own ID of different task in the
appendix of this document, for this one the ID is 6304;
<text>: is the detail description of the specific observation ID, this message is 'MonitorName',
means this observation ID is observing the name of the monitor;
OBX example:

OBX||ST|6304^MonitorName||ICUA8||||||F|<CR>
Special note: Some segments (such as MSH, OBX) in different or the same message will appear
several times, each time when they appear, most of these segments’ composition and value is
relatively fixed (such as the OBX-11, MSH-11, MSH-12), only a portion of the value or composition
of the field will be slightly different due to the message or observation change. (such as the OBX-
3, MSH-9, MSH-10). In the follow-up content, this document will not repeat those relatively fixed
composition and value of the field or those which do not use, but only highlight those items different
segments when the message or observe task is change.

4.2 CMS and Gateway's online broadcast message

4.2.1 message content
CMS and Gateway's online broadcast message by the central monitoring system or Gateway
mode by specifying the port sent to the entire network, inform the passenger-side their own
online information, including CMS broadcast port 52000, Gateway mode radio port 52001.
Broadcast message contains the following:
CMS or the name of Gateway

4.2.2 Message Format

HL7 message format specified using the syntax notation for the segment: MSH OBX, examples
below.

MSH|^~\&|||||||ORU^R01|BC01|P|2.3.1|<CR>
OBX||ST|6523^||M6000C||||||F|<CR>
4.2.3 News Section
4.2.3.1 MSH
Section of the field (Field) may refer to 3.2 meaning of fields in the MSH table. This
document on the message type and message control ID is defined as follows:
● type of message (MSH-9): ORU ^ R01
● Message Control ID (MSH-10): BC01
4.2.3.2 OBX
Section of the field (Field) field value the meaning and can refer to 4.1.3.5 OBX field in the
 composition of the table, observed in this document to the message ID (OBX-3) and observations
(OBX-5) of the definition of As follows:
● Observation ID (OBX-3): 6523 ^
● observations (OBX-5): M6000C

5 bed list of messages

5.1 The content of the message
In the CMS or Gateway mode, the server query port 51001 in the bed on the list received a
list of the client's bed inquiry message (see 8 query message), the Council passed the 51,001 beds
in the port list to the client to send a message to inform the current monitoring network exists The
bedside monitor, the message reads as follows:
● the number of currently online bed machine
● broadcast messages online bed machine
● identify the beginning and end of the list of beds

5.2 Message Format

The list of messages to include line beds bedside monitors and the number of bedside monitors
each line of basic information. Monitor the number of line segments that can use the OBX, and
monitor use of the basic information documents directly online using the 4.1 monitor broadcast
news. The beginning and end of the list of bed and directly use the document to form a control
section OBX, to identify the beginning and end of the bed of the list. Bed list format of the message
is as follows:

MSH Header
OBX The number of online bed
machine
OBX Online bed began to identify a list
Monitor1 broadcast Msg Monitor online radio news
…………………………
Monitorn broadcast Msg

Message example:

MSH|^~\&|||||||ORU^R01|BL01|P|2.3.1|<CR>
OBX||NM|6520^||1||||||F|<CR>
OBX||CE|6521^||1^||||||F|<CR>
MSH|^~\&|||||||ADT^A01|BM01|P|2.3.1|<CR>
EVN||00000000|<CR>
PID|||201011161506||1111^2222|<CR>
PV1||I|^room1^ICU&Bed1&0&0&1|||||||||||||||A|<CR>
OBX||ST|6304^MonitorName||ICUA8||||||F|<CR>
OBX||CE|6521^||2^||||||F|<CR>
News Section 5.3
Section of the field (Field) may refer to 3.2 meaning of fields in the MSH table. This document on
the message type and message control ID is defined as follows:

● type of message (MSH-9): ORU ^ R01

● Message Control ID (MSH-10): BL01
5.3.2 OBX
5.3.2.1 number of beds online
The list of messages in the bed of the OBX segment field (Field) field value the meaning and
can refer to 4.1.3.5 OBX field in the composition of the table, observed in this document to the
message ID (OBX-3) and observed values (OBX-5) is defined as follows:

Field Lengt Dat Option Field Name Remarks

No. h a s Valid
Typ
e
2 2 ID R No Type Data type：‘NM’
3 80 CE R Yes Observe ID ‘6520’
5 65K R Yes result Quantity of connected bed

The following line shows the current number of beds online OBX segment bedside machine
number 1:

OBX||NM|6520^||1||||||F|<CR>
5.3.2.2 bed list start / end control section
The OBX segment is used to identify the beginning and end of the bed of the list, the field is
composed as follows:

Field Lengt Dat Option Field Name Remarks

No. h a s Valid
Typ
e
2 2 ID R No Type Data Type：‘CE’
3 80 CE R Yes Observe ID ‘6521’
5 65K R Yes Result Bed list start with‘1^’
Bed list start with ‘2^’

Example
OBX||CE|6521^||1^||||||F|<CR>
OBX||CE|6521^||2^||||||F|<CR>

6 TCP connect to the online news

 TCP connect to the online news that the aforementioned heartbeat packet data communications
for both sides to maintain TCP connection, that the communicating parties to establish TCP
connection should be periodically (1S) to send the message to the other, within a specified time
(10s) did not receive the message that the TCP connection interrupt or exception, should take the
initiative to break the TCP connection.
This message is only played the role of a radio line, can not share too much traffic, so the
message contains only a MSH segment, the message type and message control ID is defined as
follows:

● type of message (MSH-9): ORU ^ R01

● Message Control ID (MSH-10): EC01
For example:
MSH|^~\&|||||||ADT^A01|BM01|P|2.3.1|<CR>

7 Patient information to change the message

The message in the TCP connection is established or changed patient information is sent by
the active server, due to the transfer of patients using the OBX segment height, weight, blood type
and other clinical information, the type of the message instead of using the ORU ^ R01 ADT ^ A08.
7.1 The content of the message
● department name
● bed number (machine number)
● room number and bed number
● IP address and port number
● patient name and ID
● identify patients
● the patient's sex, date of birth
● patient height, weight, blood type
7.2 Message Format
HL7 message format specified using the syntax notation for the segment: MSH PID PV1
OBR {OBX}, examples below.
MSH|^~\&|||||||ORU^R01|PA01|P|2.3.1|<CR>
PID|||201011161506||1111^2222||20101215|F|<CR>
PV1||I|^room1^ICU&Bed1&0&0&1|||||||||||||||A|<CR>
OBR||||PROGETTI Monitor||||<CR>
OBX||NM|6051^||44.9||||||F|<CR>
OBX||NM|6052^||173.5||||||F|<CR>
OBX||CE|6302^Blood Type||1^B||||||F|<CR>
OBX||CE|6303^pacemaker||1^ON||||||F|<CR>
7.3 News Section
7.3.1 MSH
Section of the field (Field) may refer to 3.2 meaning of fields in the MSH table. This
document on the message type and message control ID is defined as follows:
● type of message (MSH-9): ORU ^ R01
 ● Message Control ID (MSH-10): PA01
7.3.2 PID
PID segment of the message field PID-3, PID-5 composition and definition with 4.1.3.3, that
the message is also used in other
PID-7, PID-8 two fields, the following composition:

Field Lengt Data Optio Field Name Remarks

No. h Type ns Valid
7 26 TS O Yes Birth Date Date format is as
following:
‘YYYYMMDD’
8 1 IS O Yes Patient Sex Details in ● PID-8
patient sex

● PID-8 with the gender

Document the patient's gender conventions are as follows:

'M': that male gender of patients
'F': that sex for women patients
'U': that the patient's sex is unknown
PID segment example:
PID|||201011161506||1111^2222||20101215|F|<CR>
7.3.3 PV1
PV1 segment of the message composition and definition consistent with the 4.1.3.4, refer to
the completion of the construction of the paragraph.
7.3.4 OBR Observation request segment
OBR clinical observation of all the first report of the data, the main prescription information
and the report itself contains information that correspond to different components of OBR or field,
the report describes the process of observing the different roles. The message uses only the OBR-4
OBR OBR-7 and two fields, which are defined as follows:

Field Length Data Optio Field Name Remarks

No. Type ns Valid
4 200 CE R Yes General service
 Field Length Data Optio Field Name Remarks
No. Type ns Valid
mark ‘Biligth Monitor’
means that service
provider
7 26 TS C Yes Observing is‘0’
date/time

7.3.5 OBX
7.3.5.1 Weight and height
Field Len Data Option Field Name Remarks
No. gth Type s Valid
2 2 ID R No Type Data Type：‘NM’
3 80 CE R Yes Observing ID Weight：‘6051’
Height：‘6052’
5 65K R Yes Result Height
Weight
6 60 CE O No unit With default unit

Disclaimer: To simplify the program logic, observation in the use of OBX sent when all units need
to explain observations in Appendix behind the project documents are used to pass the default units,
field OBX-6 will be omitted, the latter not repeat them.
The following example shows that patients with body weight of 44.9kg, elevated 173.5cm:

OBX||NM|6051^||44.9||||||F|<CR>
OBX||NM|6052^||173.5||||||F|<CR>
7.3.5.2 identify the blood type and pacing

Field Len Data Option Field Name Remarks

No. gth Type s Valid
2 2 ID R No Type Data Type：‘CE’
3 80 CE R Yes Observing ID Blood Type：‘6302’
Pulse：‘6303’
5 65K R Yes Result Details in observations code
conventions

● observations code conventions

Blood and pacing are used observations identified the following form: To observe the value
type the text that identifies the ^ observations.
Blood types of observations and the observations identify text that is defined as follows:
0 ^ A: that A, the blood type identification bit 0
1 ^ B: that B, the blood type identification bit 1
2 ^ AB: that AB, the blood type identification bit 2
 3 ^ O: that O, the blood type identification bit 3
4 ^ U: that the patient blood type is unknown, their blood type identification bit 4
Pacing identifies the type of observations and the observations identify text that is
defined as follows:
0 ^ Off: turn off that pacemaker, the identification bit 0
1 ^ On: said pacemaker to open its identity bit 1
2 ^ Unkown: that pacemaker status is unknown, the identification bit 2
The following paragraph 2 OBXA blood sample showed that the B-type patients,
patients wear a pacemaker and open:
OBX||CE|6302^Blood Type||1^B||||||F|<CR>
OBX||CE|6303^pacemaker||1^ON||||||F|<CR>

8 query messages
The role of query messages is as follows:
● HL7 interface to work in the ASM model and has established a TCP connection, the server
from port 51000 to receive query messages from the client and the client through the port to send
the initiative to observe the report message;
● work in the CMS server or Gateway mode, CMS or the Gateway port 51000 to receive from
a query message from the client, the client sends the query to monitor the message of active
observations;
● work in the CMS server or Gateway mode, the server can query window 51001 beds in the list
received from the client list of query messages beds, and through the port to the client to send the
current monitoring network in the beds in the list of all online information.

8.1 Message content

By querying the message, the client directly to the bedside monitor or through the CMS
(Gateway) check the following online bed the following information:
● parameter data (values)
● alarm limit
● alarm level
● Basic information of patients
● physiological alarm information
● alarm information technology
● CMS or the Gateway list information online beds
8.2 Message Format
Document uses the query message (QRY), or the content of the project due to differences in
query slightly different, mainly in the news these different sections of the differences and differences
in field values, the following content will QRY message about the general format And messages for
different examples.
Query message (QRY) format using the HL7 notation provides syntax for the segment: MSHQRD
{[QRF]}
For example:

MSH|^~\&|||||||ORU^R02|RP01|P|2.3.1|<CR>
 QRD|201011161731|R|I||||||RES|<CR>
QRF|THD||||3232235568&0^1^1^1^1|<CR>

8.3 News Section

8.3.1 MSH
Section of the field (Field) may refer to 3.2 meaning of fields in the MSH table. This
document on the message type and message control ID is defined as follows:
● type of message (MSH-9): QRY ^ R02
● Message Control ID (MSH-10): RP01
8.3.2 Topics described in QRD Query

Field Length Data Opti Field Name Remarks

No. Type ons Valid
1 26 TS R Yes Query date/time Format:
YYYYmmDDhh
MMss
2 1 ID R Yes Query format Always be‘R’
unicode
3 1 ID R Yes Query priority Always be‘I’
4 10 ST R Yes Searching ID Application
definition
9 3 PT R Yes Filter topics Always be‘RES’

● standard fields
HL7 standard field QRD-2, QRD-3, QRD-9 values have a unified definition (refer to relevant
chapters in the HL7 V2.3.1), the query document in accordance with the development needs of the
application during the HL7 Construction of the message listed in the table must be used when the
field value, otherwise the server will generate an error message (ACK), back to the client.
● QRD-4 query ID
● QRD-4 Query ID value of the field defined by the application itself, which uniquely
identifies a query, the query ID, the document provides as follows:
'QBM2010': query bedside machines that monitor data
'QCM2010': indicates that the query list of CSM or Gateway's bed care beds or query the
data online
8.3.3 QRF query filter segment
QRD and QRF is mainly used in conjunction with a precise definition of the initial model for
further inquiry under the conditions and contents. This field is mainly used for document check
online bed care data (including from the CMS / Gateway query), through the CMS / Gateway check
the list of messages to ignore the bed field. Of fields used in the document are defined as follows:

Field Length Data Option Field Name Remarks

 No. Type s Valid
1 20 ST R Yes Filter topics Application
place distribution
5 1000 ST O Yes Filter other QRY Application
topics distribution

● QRF-1
HL7 allows the application to assign the field value is used to identify query their
departments, systems and subsystems. Place the document on the screen as follows:
'BMS': that the client directly query the data from the bedside monitor
'CMS': that the client directly query the data from the CMS or Gateway
'THD': said server from the client to query data (not support, facilitate follow-up reserved for
extensions)
● QRF-5
This field contains the locally defined, between the two systems used in the filter, the program
used by some and inquiries about the code, components can be defined by the applicationitself. The
field is divided into several components of the document, its format and meaning are as follows:
|<SenAddr>^<SendType>^<SendFreq>^<SendAll>^<List>|
（1） SenAddr：Search for address（CE）
It includes 2 sub-components including: ^ <IP> & <IPSeq> ^, as follows:
IP (NM) or Gateway for the query from the CMS bed care line data, specify the IP address of
query-bed, the value of the relevant provisions see 4.1.3.4. When the client directly query the data
from the bedside monitor, because the client has already established direct bedside machine TCP
connection, without specifying IP, so the value of the sub-component is set to '0 '.
IPSeq (NM) follow-up to the company for wireless products (433M) set aside the interface,
sub-group scores to take '0 '.
(2) SendType: query type (ID)
Specified in the client's specific type of query data, documents the development of data
involved in the query as follows:
'0 ': invalid value
'1 ': parameter value data
'2 ': waveform data (follow-up reserved for use, not to support the development of this wave
of data transmission)
'3 ': physiological alarm
'4 ': Technical alarm
'5 ': Other configuration information
Since each QRF segment can only send a query type ID, so the client monitoring information
in query requires a different use of multiple QRF segments.
(3) SendFreq transmit frequency (NM)
The server component indicates the frequency of sending query data to s as a unit.
(4) SendAll all send (ID)
The component specified by callers was sent under the specified query all the parameter data
type (configuration), or just send the subsequent sub-component <List> parameter data listed. The
component values are as follows:
'1 ': ignore the rest of the list of components of the query <List>, sending all the parameters
of the specified type of data;
'0 ': According to the back of the check list of components <List>, send a list of parameters
specified in the parameter data;
To simplify the program logic, the document provides that the total component is set to '1 ', the
server will send all the parameters of the specified type of data, this time component <List> will be
ignored.
(5) <List> parameter list
The components used to enumerate the list of parameters to the query, when Send all component
value is '0 'when the components of effective, otherwise the component will be ignored.Follow-up
can be extended to specify the module parameters for the query, the document format of the List
component is defined as follows, and the data type of each sub-component are "NM":
^<ModuleID>&<ParamID>~<ModuleID>&<ParamID>~……^
ModuleID and ParamID local conditions by the application-defined code, representing the module
ID and module parameters belong ID (a module can have multiple parameters). See document ID
code behind the definition of the appendix. For programming convenience, the document provides
for up to repeated use of components containing List 6 sub-components, that is, a QRF segment can
search for up to 6 different or the same module parameters, when the query parameter is greater than
the time necessary to use more than 6 months A section of the QRF. For example, to query ECG
module (ModuleID as '1 ') of the HR parameters (ParamID '0') and NIBP Module (Module ID as '3
') of the DIA parameters (ParamID to '2 '), the List consists of the following components:

^1&0~3&2^
In view of the development of sending all the parameters, List component of the value is always '1
', under which no longer contains sub-components, the server process the query message can be
ignored.

8.4 Example query messages

8.4.1bed side machine direct access to monitoring information
MSH|^~\&|||||||ORU^R02|RP01|P|2.3.1|<CR>
QRD|201011161731|R|I| QBM2010|||||RES|<CR>
QRF|||||0&0^1^1^1^1|<CR>
The query message to the server information is:
8.4.1.1 Query Target
QRD-4 query ID is QBM2010, direct access to the bedside machines that monitor
information;
QRF-5 sub-components of IP value '0 '.
8.4.1.2 query condition
QRF-5 in the SendType = '1 ', indicates that the query parameter data;
QRF-5 in the SendFreq = '1 ', the sending server that requires a frequency of 1s;
QRF-5 in the SendAll = '1 ', that query the current parameters of all measurements;
8.4.2 from the CMS / Gateway queries bed care information online
To the query on the premise that the client has sent the online server list information query
message beds (see 8.4.3), and received information on the server to return a list of messages beds
(see the list of messages 5 beds), and get the current Online bed.
MSH|^~\&|||||||ORU^R02|RP01|P|2.3.1|<CR>
QRD|201011161731|R|I| QCM2010|||||RES|<CR>
QRF|||||3232235568&0^1^1^1^1|<CR>
QRF|||||3232235568&0^2^1^1^1|<CR>
8.4.2.1 Query Target
QRD-4 query ID QCM2010, expressed through the CMS / Gateway check online bed care
information;
QRF-5 in the IP sub-group was divided into 3,232,235,568, said the inquiry was
3,232,235,568 IP beds, that is 192.168.0.66;
8.4.2.2 query
QRF paragraph 1 of the query is the query passed all the parameter values required to send a
frequency of 1s;
QRF segment 2nd query is the query passed all the physical parameters of the alarm
message to send the frequency of 1s.
8.4.3 On-line bed check list
The message does not contain QRF segment, only the QRD-4 in the query that the purpose of
CMS / Gateway, the message example:
MSH|^~\&|||||||ORU^R02|RP01|P|2.3.1|<CR>
QRD|201011161731|R|I| QCM2010|||||RES|<CR>

9 query reply message

Query reply message is received by the server to the client's inquiry response message to
inform the client query is successful. Query is successful the server will send ORF message query
that returns data transfer immediately begin; query fails or the server when an error occurs will send
ACK message, and report the error contents.

9.1 ORF query success

9.1.1 message content
● identify the position to accept inquiries
● query returns
9.1.2 Message Format
：ORF segment syntax notation as: MSH MSA QRD {[QRF]}, example:
MSH|^~\&||||||| ORF^R04| QY11|P|2.3.1|<CR>
MSA|AA| RP01||<CR>
QRD|201011161731|R|I| QCM2010|||||RES|<CR>
QRF|||||3232235568&0^1^1^1^1|<CR>
QRF|||||3232235568&0^2^1^1^1|<CR>
9.1.3 MSH segment
Section of the field (Field) may refer to 3.2 meaning of fields in the MSH table. This
document on the message type and message control ID is defined as follows:
 ● type of message (MSH-9): ORF ^ R04
● Message Control ID (MSH-10): QY11
9.1.4 MSA News confirmed section
MSA section contains another message sending confirmation message, used to report to the client

inquires the message handling, documents use the composition of the MSA fields defined as

follows:

field length data Opti wheth field name remark

S/N types onal er use
1 2 ID R Yes Confirmation HL7 define

code

2 20 ST R Yes news control ID Be reply query

message control

ID

3 80 ST O Yes text information Describe error

messages

● MSA-1 Confirmation code（ID）

MSA - 1 field indicated the query of reception, an HL7 message this field value defined, the

concrete content see an HL7 the relevant sections, document to the field values only used as

follows

AA： To accept the query

AE： be show use for program error
In confirmation message ORF inquires the success of value for MSA - 1 "AA '

● MSA-2 news control ID (ST)

MSA - 2 value was reply query message control ID, it makes the message sending system inquires

the news and the corresponding reply message will corresponding up . Query of news control ID

see eight inquires the contents of the news

● MSA-3 text message（ST）

MSA - 3 fields are optional, in ORF in may be omitted; In an ACK message that inquires the news

failure is used to convey error messages

The following MSA segment to accept the news for RP01 query control ID news , MSA - 3

omitted

MSA|AA| RP01|<CR>
9.1.5 QRD section
See 8.3.2 QRD inquires the topic paragraphs

9.1.5 QRF section

See QRF inquires 8.3.3 theme describe section

9.2 ACK inquires the failure

9.2.1 the message content

●News error identification

●Error information
9.2.2 message format
An HL7 section grammar identifier: MSH MSA, That is the message contained only MSH and

MSA two fields.

For example

MSH|^~\&||||||| ORF^R04| QY11|P|2.3.1|<CR>

MSA|AE| RP01|QRF Segment is error|<CR>
9.2.3 information section
9.2.3.1 MSH section
The meaning of Section of each Field ) can reference the table which composed of the MSH

fields of 3.2. In this document for message types and news control ID defined as follows

：ORF^R04
● message types（MSH-9）
：QY10
● news control ID（MSH-10）
9.2.3.2 MSA section
Field definition component see 9.1.4 MSA news confirmed section, the news column used in

value as follows

● MSA-1：AE
● MSA-2： Be reply query message control ID

● MSA-3： Error information

。 The following MSA section said news RP01 query control ID for news errors occur, error

messages for "QRF Segment is error".

 MSA|AE| RP01|QRF Segment is error|<CR>

10 Active observations news

Active observations news refers to send bedside machine monitoring data and the working state of

news, such as parameters report news, physiological/technical alarm information news, the alarm

limit/alarm level info, module load/unload news, module parameters configuration changes news ,

these news news will be in the client successfully sent inquires the news or server-side working

condition change initiative to send, and so has become active observations. The server through

surveillance TCP connection 51000 and client TCP connection in the TCP connection, after take

care of data query news and send corresponding active observations news. According to the

monitoring below will transfer data types and monitoring terminal can work of the state, was

introduced. 4.1.3.5 OBX observations message segments

10.1 Parameter data observation

10.1.1 information content

● Parameters subordinate module ID

● Parameters ID
● Parameters name
● parameter values
10.1.2 information format
An HL7 section grammar identifier: MSH {OBX}. Each parameter values use one OBX transfer,

want to use a passing multiple parameters observation time need to repeat OBX paragraph. More

than

10.1.3 news section

10.1.3.1 MSH
The meaning of Section of each Field ) can reference the table which composed of the MSH
fields of 3.2. In this document for message types and news control ID defined as follows
：ORU^R01
● message types（MSH-9）
：RP01
● news control ID（MSH-10）
10.1.3.2 OBX
OBX segment of the composition and definition see 4.1.3.5 OBX observations information section,

the message to the application definition of field values provisions below

●OBX - 2 value types (ID)

OBX - 2 'book explain observation of type, "NM”said parameters observations results in digital

form relay.
●OBX - 3 observation ID (CE)

OBX - 3 contains observation project unique identifiers, to observe parameters in the module
ID, definition of module ID appendix
●OBX - 4 observation branch ID (ST)

OBX - 4 project results used to observe the classification, its composition is defined as
|ParamID^ParamName|
（1） For observes parameters of ID, the definition of parameters ID appendix

（2） Components ParamName (ST)

For the name of the observed parameters, the parameters of ID definition of appendix

●OBX - 5 observations (NM)

To observe the value of the parameter send moments.

OBX - 13 user defined pathways check (ST)

Document with this field parameters transfer value of transfer mode, namely is parameter cycle

relay, or according to the measured results update status transfer, its value stipulated below

The non-periodic passes parameters, the measured results of transmission, such as NIBP;

● The non-periodic passes parameters, namely receive inquires the command, periodic
send parameters, such as HR
For continuous measuring parameters such as HR, SpO2, this field may be omitted
namely default for PERIODIC ' '
● OBX-14 Observation time（TS）
Only in this field OBX - 13 to any value 'APERIODIC' effective, record the result update time,

when 4.1.3.5 function format as stated in, When on OBX - 13 value, ignoring the PERIODIC '

'fields.

For example, the server to the client sends the following parameters data from observations

news, reports of knowable draw transfer content for HR = 80 , SpO2=98，NIBP_SYS=90：

MSH|^~\&|||||||ORU^R01|RP01|P|2.3.1|<CR>
OBX||NM|1|0^HR|80||||||F|<CR>
OBX||NM|2|0^SpO2|98||||||F|<CR>
OBX||NM|3|0^NIBP_SYS|90||||||F|| APERIODIC |201012301422|<CR>

10.2 Parameters alarm configuration observations

10.2.1 The alarm limit parameters observations

10.2.1.1 information content
●The alarm limit logo

●module ID
●parameters ID
●alarm limit
10.2.1.2 information format
as 10.1.2
10.2.1.2 information section
10.2.1.2.1 MSH
The meaning of Section of each Field ) can reference the table which composed of the MSH
fields of 3.2. In this document for message types and news control ID defined as follows

● message types（MSH-9）：ORU^R01
：AI01
● news control ID（MSH-10）
10.2.1.2.2 OBX
OBX segment of the composition and definition see 4.1.3.5 OBX observations information
section, the message to the application of the field values provisions defined as follows
● OBX-2 Value types（ID）：‘TS’

● OBX-3 Observation ID（CE）

Its value is 6002, 'said transmission is parameters of the alarm limit

● OBX-4 observation branch ID（ST）

Contains two components, its composition for ParamID | | ModuleID: ^. ParamID | The meaning

of each component see introduction about OBX-3

● OBX-5 observation result（NM）

Includes 2 repetitive components, its composition for |UpLimit ~LowLimit |. Among them,

the components UpLimit said parameters of alarm limit, LowLimit for alarm limit, me

group components of data types are 'NM'

The following message transfer of ECG module (ModuleID = 1) on HR (ParamID = 0) alarm

up limit for 150, alarm down limit for 50:

MSH|^~\&|||||||ORU^R01|AI01|P|2.3.1|
OBX||NM|6002^|1^0|150~50||||||F|
10.2.2 Parameters alarm level observation

10.2.2.1 information content

● Alarm limit logo

● module ID
● parameters ID
● alarm level
10.2.1.2 information format
as 10.1.2
10.2.1.2 information section
10.2.1.2.1 MSH
The meaning of Section of each Field ) can reference the table which composed of the MSH
fields of 3.2. In this document for message types and news control ID defined as follows
：ORU^R01
● message types（MSH-9）
：AE01
● news control ID（MSH-10）
10.2.1.2.2 OBX
OBX segment of the composition and definition see 4.1.3.5 OBX observations information
section, the message to the application of the field values provisions defined as follows
：
● OBX-2 values types（ID）
● OBX-3 observation ID（CE）

Its value is transmitted 6003 ', said the alarm level is parameters

● OBX-4 observation branch ID（ST）

Contains two components, its composition for | | ModuleID: ^. ParamID | The meaning of each

component see introduction about OBX-3 among 10.1.3.2

● OBX-5 observation result（NM）

In view of some parameters of alarm level are points of upper, document dosage repetitive
components seperately upper/low quotation level, its composition for| : UpLevel ~ LowLevel |.
Among them, UpLevel said limit alarm level components, LowLevel for lower limit alarm level,
each composition data types are 'NM'. For alarm level don't distinguish between upper, components
UpLevel and LowLevel when the value of the same. About alarm level stated below
‘1’： low
‘2’： middle
‘3’： high
The following message transfer alarm level info for:the middle alarm level for HR
（UpLevel，LowLevel all are
2） ，the up limit alarm level of SpO2 for high level（UpLevel=3）, low limit alarm level for
middle level（LowLevel=2）
MSH|^~\&|||||||ORU^R01|AI01|P|2.3.1|<CR>
OBX||NM|6003^|1^0|2~2||||||F|<CR>
OBX||NM|6003^|2^0|3~2||||||F|<CR>
10.3 Parameters alarm information observations

10.3.1 Physiological alarm information

10.3.1.1 information content

● Alarm message type identifiers

● module ID
 ● parameters ID
● alarm code
10.3.1.2 information format
as 10.1.2
10.3.1.3 information section
10.3.1.3.1 MSH
The meaning of Section of each Field ) can reference the table which composed of the MSH
fields of 3.2. In this document for message types and news control ID defined as follows
：ORU^R01
● information types（MSH-9）
：AP01
● news control ID（MSH-10）
10.3.1.3.2 OBX
OBX segment of the composition and definition see 4.1.3.5 OBX observations information
section, the message to the application of the field values provisions defined as follows
● OBX-2 value types（ID）：‘ID’
● OBX-3 observation ID
Contains two components, its composition for | | ModuleID: ^. ParamID | The meaning of each

component see introduction about OBX-3 among 10.1.3.2

● OBX-4 observation branch ID

Used to convey information alarm parameters current alarm level, alarm level of definition see

10.2.1.2.2 OBX.

● OBX-5 observation result ID（ID）

As the parameters alarm information code that identifies a alarming message, the alarm
information code definition appendix
● OBX-14 observation time（TS）
Time format is the same as above, used to convey alarming time.

The following information for the message alarm :HR for overtop (1), alarm level for high level,

SpO2 low,(2), alarm level for middle

MSH|^~\&|||||||ORU^R01|AP01|P|2.3.1|<CR>
OBX||NM|1^0|3|1||||||F|||201011161548|<CR>
OBX||NM|2^0|2|2||||||F|||201011161548|<CR>
10.3.1 Technical alarm information

Technical alarm information and physiological alarm information of the message format basic

similar, only MSH segment of news control ID variations , the news control ID (MSH-10) for

“AT01”

Below disappear examples, explain SpO2 happened fall off alarm

MSH|^~\&|||||||ORU^R01|AT01|P|2.3.1|
OBX||NM|2^71|1|254||||||F|||201011161548|
In order to simplify the alarm information transmission, the document will be also as a module

technology alarm parameters, among them the 254 for the alarm code of sensor fall off

In addition to explanation, when be queried beds no alarm occurs, an alarm information news
will contain only a MSH section, no OBX section, at this time the client without any processing
10.4 Module loading/unloading observations

10.4.1 Module loading news

If the bedside machine there are physical module insert or software opened, the server will be sent

modules loaded active news through TCP connection, to the client-side report modules loaded

specific information

10.4.1.1 information content

● loading module ID
● loading module name
● module all parameters ID and name
10.4.1.2 information format
An HL7 section grammar identifier: OBX {MSH OBX}. Among them, the module load

information to have a OBX transfer, the parameters of load information need one or more OBX

section. News examples are as follows:

MSH|^~\&|||||||ORU^R01|ML01|P|2.3.1|
OBX||CE|6023^||1^ECG||||||F|
OBX||CE|6025^|1|0^HR||||||F|
OBX||CE|6025^|1|1^PVCs||||||F|
OBX||CE|6025^|1|2^ST-I||||||F|
OBX||CE|6025^|1|3^ST-II||||||F|
OBX||CE|6025^|1|4^ST-III||||||F|
OBX||CE|6025^|1|5^ST-AVR||||||F|
OBX||CE|6025^|1|6^ST-AVL||||||F|
OBX||CE|6025^|1|7^ST-AVF||||||F|
OBX||CE|6025^|1|8^ST-V1||||||F|
OBX||CE|6025^|1|9^ST-V2||||||F|
OBX||CE|6025^|1|10^ST-V3||||||F|
OBX||CE|6025^|1|11^ST-V4||||||F|
OBX||CE|6025^|1|12^ST-V5||||||F|
OBX||CE|6025^|1|13^ST-V6||||||F|
10.4.1.2 information section
10.4.1.2.1 MSH
The meaning of Section of each Field ) can reference the table which composed of the MSH
fields of 3.2. In this document for message types and news control ID defined as follows
：ORU^R01
● info types（MSH-9）
：ML01
● news control ID（MSH-10）
10.4.1.2.1 OBX
In the news in OBX section is used to convey two types of information: load module information

and load parameter information. Among them, the former using a OBX transmission, the latter to

one or more OBX transfer, namely each load parameters can use an OBX relay. The following is

the value:

● OBX-2 ‘CE’value types（ID）

● OBX-3 observation ID
Transfer load module information to any value when observation ID | 6023 ^ | :

Transfer load parameters information to any value when observation ID | 6025 ^ |

● OBX-4 observation branch ID
Transfer load module information when branch ID value for: observation: no value neglecting;

Transfer load parameters information when branch ID value for: loading module ID
● OBX-5 observation result
Transfer load module information to any value: |ModuleID^ModuleName|，Said load module ID

and their names

Transfer load parameters information to any value: |ParamID^ParamName|，Said load

parameters ID and their names
The above message an example shows that the bedside machine opened the ECG module, the

server sends messages to inform the client-side load module of relevant information.

10.4.2 module unloading info

If the bedside machine there are physical module uproot or through software open a module, the

server will be sent active modules unload info through via TCP connection, unloading news to the

client report module unloading specific information

Module uninstall news only contains is unloaded module ID would be ok, an HL7 section syntax

notation is: OBX MSH. The news OBX and MSH related fields in values are defined as follows:

● MSH-10 news control ID MU01；

● OBX-2 value types CE；
● OBX-3 observation ID：6024^
● OBX-4 observation branch ID: no value
● OBX-5 observation value: ModuleID ^，ModuleID define as above
News examples below, transfer information for the blood oxygen module (ModuleID = 2) be

plucked up or manual off

MSH|^~\&|||||||ORU^R01|MU01|P|2.3.1|
OBX||CE|6024^||2^||||||F|
10.5 Module configuration observations

Module configuration observations in bedside machine on the configuration of modules

changed (such as in ECG module by 12-lead couplet switch to 5 guide couplet), the server will pass
a TCP connection initiative is sent to the client, client needs according to the configuration ofthe
changing situation refresh corresponding modules and parameters of the relevant information
10.5.1 info content
● configuration change module ID
● unloading parameter ID
● loading parameter ID
10.5.2 information format
An HL7 section grammar identifier: MSH {OBX} {OBX}. Among them, the first to repeat the

OBX group used for storage module configuration changes need to uninstall parameters

(ParamID); The second repeated OBX group used for storage module configuration changes need

to load parameters (ParamID). Each of them OBX can only transmit a parameter of load or unload

news, message example is as follows:

MSH|^~\&|||||||ORU^R01|PM01|P|2.3.1|
OBX||CE|6502^|1|8||||||F|
OBX||CE|6502^|1|9||||||F|
OBX||CE|6502^|1|10||||||F|
OBX||CE|6502^|1|11||||||F|
OBX||CE|6502^|1|12||||||F|
OBX||CE|6502^|1|13||||||F|
OBX||CE|6025^|1|14^ST-V||||||F|
10.5.3 information section
10.5.3.1 MSH
The meaning of Section of each Field ) can reference the table which composed of the MSH
fields of 3.2. In this document for message types and news control ID defined as follows
：ORU^R01
● info types（MSH-9）
：PM01
● news control ID（MSH-10）
10.5.3.2 OBX
Below will load and unload parameters of OBX field composition and define unified introduction

● OBX-2 value type CE

● OBX-3 observation ID
Transfer load parameters when the value is observed ID 6025 ^; :

Transfer unload parameters when the value is observed ID 6025 ^; :

·OBX -4 observation branch ID: Module ID, configuration change ID, definition as above
● OBX-5 observation value:ParamID, load or unload parameter ID, definition as above
V1、V2、V3、V4、V5、V6。The above example 10.5.2 messages in ECG module expressed by

12lead switch to 5lead when the server sent to client news, switching process needed to uninstall
parameters for 8 ~ 13 ID ,expression of parameters in turn for V1, V2, V3 V4, V5, V6,.
Appendix A module/parameters/alarm ID refer to the monitor module definition of ID.doc
The appendix B observation transfer units list

observation type transfer units

HR/PR bpm
PVCs /min
ST section value mv
RR/awRR rpm
weight kg
height cm
SPO2 %
BP mmHg
temperature(contain temperature difference) ℃
N2O %
AG %
O2 mmHg
CO2 mmHg
C.I. L/min/m²
C.O. L/min
SV ml
SI ml/m²
SVR DS/cm5
SVRI DS∙m²/cm5
TFC /kΩ
TFI Ω
 Progetti Srl
Strada del Rondello 5
Trofarello, 10028
Italy
www.progettimedical.com
info@progettimedical.com