SureSigns VM Series

Patient Monitors

HL7 Guide

Release A

English
Proprietary Notice

This document and the information contained in it is proprietary and confidential information
of Philips Medical Systems (“Philips”) and may not be reproduced, copied in whole or in part,
adapted, modified, disclosed to others, or disseminated without the prior written permission of
the Philips Legal Department. Use of this document and the information contained in it is
strictly reserved for current Philips personnel and Philips customers who have a current and
valid license from Philips for use by the customer's designated in-house service employee on
equipment located at the customer's designated site. Use of this document by unauthorized
persons is strictly prohibited. Report violation of these requirements to the Philips Legal
Department. This document must be returned to Philips when the user is no longer licensed
and in any event upon Philips' first written request.

Philips Medical Systems

3000 Minuteman Road
Andover, MA 01810-1085
(978) 687-1501
Printed in the USA

Document Number
4535 640 41111

Copyright © 2006 Koninklijke Philips Electronics N.V. All Rights Reserved

Warranty Disclaimer

Philips provides this document without warranty of any kind, either implied or expressed,
including, but not limited to, the implied warranties of merchantability and fitness for a
particular purpose.

Limits of Liability

Philips has taken care to ensure the accuracy of this document. However, Philips assumes no
liability for errors or omissions and reserves the right to make changes without further notice
to any products herein to improve reliability, function, or design. Philips may make
improvements or changes in the product(s) or program(s) described in this document at any
time.

ii
Printing History

New editions of this document incorporate all material updated since the previous edition.
Update packages may be issued between editions and contain replacement and additional
pages to be merged by a revision date at the bottom of the page. Pages that are rearranged due
to changes on a previous page are not considered revised.

The documentation printing date and part number indicate its current edition. The printing
date changes when a new edition is printed. (Minor corrections and updates that are
incorporated at reprint do not cause the date to change.) The document part number changes
when extensive technical changes are incorporated.

First Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . July 2006

iii
Text Conventions
The manual uses the following conventions for Notes, Cautions, and Warnings.

Note A Note calls attention to an important point in the text.

Caution A Caution calls attention to a condition or possible situation that could damage or
destroy the product or the user’s work.

Warning A Warning calls attention to a condition or possible situation that could cause injury to
the user and/or patient.

iv
 Contents

1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
What is Exported? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Establishing a Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

2. HL7 Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Notation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
ORU/ACK Flow of Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
ORU Message Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Message Header (MSH) Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Patient Identification (PID) Segment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Common Order (ORC) Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Patient Visit (PV1) Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Observation Request (OBR) Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Observation/Result (OBX) Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
ACK Message Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Message Header (MSH) Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Message Acknowledgment (MSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
MDIL Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

3. Enabling Data Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Configuring Data Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Enabling Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Establishing a Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Contents-1
Contents-2
 1
Overview
The SureSigns VM Series patient monitors can export patient monitoring data in HL7 format
over a local area network (LAN) using the TCP/IP transport protocol. The data can be sent to
a server and then forwarded to an Electronic Medical Records (EMR) system or sent directly
to the EMR system.

This manual is for HL7 programmers who want to develop an application that will receive the
HL7 data exported from the SureSigns VM monitors. This manual provides the following
information:

• The type of data that is exported from the SureSigns VM monitors and the intervals at
which the data is exported
• The syntax of the exported HL7 messages
• The MDIL numeric codes used in the exported HL7 messages
• The procedure for enabling data export on the SureSigns VM Series monitors
This manual assumes that the user is familiar with HL7 programming.

What is Exported?
Note—Only data with an assigned Patient ID is exported. If an entry does not have an
associated patient ID (“ID Unknown” appears in the patient information pane), the data is
not exported.

When the Data Export function is enabled, the SureSigns VM monitor exports data
periodically and aperiodically.

The periodic data is sent at regular time intervals, which can be configured in the Network
Configuration menu. Available intervals are: 5 min., 10 min., 15 min., 30 min., 1 hour,
2 hours, 4 hours, and 8 hours. Periodic data includes:

• The most recent record in the trending database

• All new SpotCheck records that have occurred since the data was last exported
• All new alarms that have occurred since the data was last exported
Aperiodic data includes NBP measurements and predictive temperature measurements.
(Predictive temperature is available on the SureSigns VM4 only.) These measurements are
sent at the time that they occur, regardless of the specified data export interval.

The exported data can also be encrypted.

For information on setting the export intervals, enabling the Data Export function, and
encrypting the data, see Chapter 3, Enabling Data Export.

Overview 1-1
Establishing a Connection

Establishing a Connection
To establish a network connection, you must:

• Connect the monitor to your Local Area Network

Connection icon
• Configure a TCP/IP address for the monitor and the designated server
• Specify a Data Export interval
When a connection is established, a connection icon appears in the upper left corner of the
monitor’s screen. The connection remains in effect indefinitely. If the network goes down or
the monitor is shut down, the connection is broken. Once the network comes back up or the
monitor is powered up, the monitor will attempt to re-establish the connection when the next
export interval is due to occur.

See Chapter 3, Enabling Data Export, for more information.

System Requirements
The server and network must meet the following minimum requirements:

• HL7 standard version 2.4

• Local Area Network using Ethernet TCP/IP IEEE 802.3

1-2 Overview
 2
HL7 Messages

Introduction
This chapter describes the two types of HL7 messages used with the SureSigns VM patient
monitor:

Message Description
ORU Unsolicited Observation Reporting. This message contains patient data
and vital signs parameters.

ACK Acknowledgement. This message is sent by the receiving system back to

the SureSigns VM patient monitor. It acknowledges that the message was
received.

Note For a complete description of HL7 message syntax, see the HL7 Interface Standards Version
2.4.

Notation Conventions
The HL7 messages use the following notation conventions:

• Single ASCII characters are enclosed in single quotes.

• Special characters or non-printing ASCII characters are enclosed in angle brackets
< ... >.
• Special characters are the LLP start block and end block characters.
• Non-printing ASCII characters can be written as abbreviations; for example, ESC for
the Escape character. They also may be written as hex values in the form 0xXX, where
X is a hexadecimal digit. For example, in Standard ASCII, <ESC> is <0x1B >.
• Block Format: HL7 messages are enclosed by special characters to form a block.
The message format is:

<SB>ddddd<EB><CR> <SB>
where:

<SB> = Start Block character (1 byte) ASCII <VT>, for example, <0x0B>. Do not confuse
this with the ASCII characters SOH or STX.

dddd = Data (variable number of bytes). This is the HL7 data content of the block. The data
can contain any ASCII characters and the carriage return character, <CR>, as delimiter of
individual segments.

<EB> = End Block character (1 byte) ASCII <FS>, for example, <0x1C>. Do not confuse this
with the ASCII characters ETX or EOT.

<CR> = Carriage Return (1 byte). The ASCII carriage return character, for example, <0x0D>.

HL7 Messages 2-1

ORU/ACK Flow of Events

The HL7 standard recommends using the following special characters:

Special Character Meaning

| Field separator

^ Component separator

& Subcomponent separator

~ Repetition separator

\ Escape character

Abbreviations
The following abbreviations are used in the message syntax descriptions.

Abbreviations Description
Seq Sequence number

DT Data type

Len Length (for primitive types only)

Usage Element usage. Usage abbreviations are:

• R = Required element
• RE = Required, but can be empty
• C = Conditional – based on predicate evaluation
• CE = Conditional, but can be empty

Min Minimum number of occurrences

Max Maximum number of occurrences

Table HL7 table

ORU/ACK Flow of Events

The following is an overview of what happens when the monitor sends a message to the
server.

1. The monitor sends a message containing vital signs results.

2. The server receives the message and attempts to commit the message to persistent
storage.
3. If the server is unable to persist the message, it returns an ACK Rejection message (AR
code).
4. If the receiver successfully persists the message, it returns an ACK Accept message
(AA code).

2-2 HL7 Messages

 ORU Message Syntax

5. The receiver of the ACK message (the monitor) starts to send the next message in case
of success (AA code).
6. The receiver of the ACK message (the monitor) resends the message if the message was
rejected (AR code). After 3 retries, the monitor stops trying and waits until the next
interval.
7. If the server does not respond within 60 seconds, the monitor times out and retries the
transmission. After 3 retries, the monitor stops trying and waits until the next interval.
The following figure shows what happens when the monitor (Sender) sends a message to a
server (Receiving Application).

ORU

ACK (AA)

ORU

ACK (AR)

Retry ORU

ACK (AR)

ORU

ACK (AA)

ORU Message Syntax

The unsolicited observation reporting (ORU) message contains patient data, including:

• Patient information
• Bed data (device ID)
• All vital signs parameters currently available

HL7 Messages 2-3

ORU Message Syntax

Each ORU message consists of a variable number of segments that are delimited by the <CR>
character.

The following table describes the segments within the ORU message:

Segment Description Usage Min Max

MSH Message header R 1 1

PID Patient identification R 1 1

ORC Common Order R 1 1

PV1 Patient visit R 1 1

OBR Observation request R 1 1

OBX Observation/result R 1 7

Example:

MSH|^~\&|^SureSignsVM||||20060510124500||ORU^R01^ORU_R01|USP1000302200
60510124500|P|2.4|||||||||2.16.840.1.113883.9.2.1<CR>
PID|||412345134||<CR>
ORC|NW|||||||||||||||||USP1000302
PV1||||||||||||||||||A<CR>
OBR||||MONITOR|||20060328134602<CR>
OBX||NM|0002-4bb8^SpO2^MDIL|0|95|0004-0220^%^MDIL|||||F<CR>
OBX||NM|0002-4182^HR^MDIL|0|60|0004-0aa0^bpm^MDIL|||||F<CR>
OBX||NM|0002-4a05^NBPs^MDIL|0|120|0004-0f20^mmHg^MDIL|||||F<CR>
OBX||NM|0002-4a06^NBPd^MDIL|0|70|0004-0f20^mmHg^MDIL|||||F<CR>
OBX||NM|0002-4a07^NBPm^MDIL|0|91|0004-0f20^mmHg^MDIL|||||F<CR>
OBX||NM|0401-0b54^pTemp^MDIL|0|37.1|0004-17a0^C^MDIL|||||F<CR>

2-4 HL7 Messages

 ORU Message Syntax

Message Header (MSH) Segment

Every ORU message begins with the message header (MSH) segment. This segment contains
message envelope information, not clinical information.

Example:

MSH|^~\&|^SureSignsVM||||20060510124500||ORU^R01^ORU_R01|USP1000302200
60510124500|P|2.4|||||||||2.16.840.1.113883.9.2.1<CR>

The following table describes each field in the MSH segment.

Sample
Seq. Field Description DT Len Usage Min Max Table
Value

1 Field ST 1 R 1 1 |
Separator

2 Encoding Every message begins with the ST 4 R 1 1 ^~\&

Characters MSH segment. This segment
contains message envelope
information, not clinical
information.

3 Sending Generic identifier for HD 180 RE 0 1 0361 ^SureSigns

Application SureSigns VM Series patient VM
monitors

3.2 universal The identifier for all devices of ST 5 RE 0 1

ID this type.

7 Date/Time TS 20 R 1 1
of Message

7.1 Date/Time Date and time: NM 20 R 1 1 200605101

YYYYMMDDHHMMSS 24500

9 Message CM_ 15 R 1 1 0076

Type MSG

9.1 message Message type is a fixed value ID 3 R 1 1 0076 ORU

type for all message instances.
Unsolicited transmission of an
observation message

9.2 trigger Message type is a fixed value ID 3 R 1 1 0034 R01

event for all message instances.
Unsolicited transmission of
results.

9.3 message ID 7 R 1 1 0354 ORU_R01

structure

HL7 Messages 2-5

ORU Message Syntax

Sample
Seq. Field Description DT Len Usage Min Max Table
Value

10 Message This is the unique identifier for ST 30 R 1 1 USP10003

Control ID this message instance. To 022006051
ensure uniqueness, this is a 0124500
combination of the device
serial number and the current
timestamp.

11 Processing PT 3 R 1 1
ID

11.1 processing All results are production ID 3 R 1 1 0103 P

ID messages from the monitors

12 Version ID VID 60 R 1 1 0104

12.1 version ID Version 2.4 is currently ID 3 R 1 1 0104 2.4

supported. HL7 is backwards
compatible. Any previous
version is compatible with this
specification.

21 Conformance This string references the HL7 ID 30 R 1 1 0449 2.16.840.1.

Statement registry OID corresponding to 113883.9.2
ID this profile. .1

Patient Identification (PID) Segment

The PID segment in an ORU message identifies the subject of the observation.

Example: PID|||412345134||<CR>

The following table describes the fields in the PID segment.

Note — The Patient Name, family name, surname, and given name fields are not supported in
the current release of the SureSigns VM monitors.

Sample
Seq. Field Description DT Len Usage Min Max Table
Value

3 Patient Contains the patient ID as CX 250 R 1 1

Identifier entered in the device. It may
List contain any numeric
characters.

3.1 ID Patient identifier. It may be the ST 10 R 1 1 412345134

medical record number or
another unique identifier used
across the enterprise.

5 Patient The patient name is included if XPN 30 RE 0 1

Name the device is integrated with
the central station application.

2-6 HL7 Messages

 ORU Message Syntax

Sample
Seq. Field Description DT Len Usage Min Max Table
Value

5.1 family FN 20 RE 0 1
name

5.1.1 surname Patient's last name. Only the ST 20 RE 0 1 Penrose

first 10 characters are
displayed by the monitor.

5.2 given name Patient's first name. Only the ST 10 RE 0 1 Roberta

first 10 characters are
displayed by the monitor.

Common Order (ORC) Segment

The ORC segment provides the serial number of the sending device.

Example: ORC|NW|||||||||||||||||USP1000302

The following table describes each field in the ORC segment.

Sample
Seq. Field Description DT Len Usage Min Max Table
Value

1 Order ID 2 R 1 1 0119 NW
Control

18 Entering Specifies the device used for CE 250 RE 0 1

Device the measurements.

18.1 identifier Device Serial Number ST 11 RE 0 1 USP10003

02

Patient Visit (PV1) Segment

The PV1 segment is sent in ORU messages to identify the patient type.

Example: PV1||||||||||||||||||A<CR>

The following table describes each field in the PV1 segment.

Sample
Seq. Field Description DT Len Usage Min Max Table
Value

18 Patient Adult ( “A”) , Pediatric (“P”) IS 2 R 1 1 0018 A

Type or Neonatal (“N”).

HL7 Messages 2-7

ORU Message Syntax

Observation Request (OBR) Segment

The OBR segment identifies the type of data being exported — monitor (trend data),
spotcheck, or alarm — and the date and time that the measurement occurred.

Examples:

OBR||||MONITOR|||20060328134602<CR>

OBR||||SPOTCHECK|||20060328134602<CR>

OBR||||ALARM|||20060328134602<CR>

The following table describes each field in the OBR segment.

Sample
Seq. Field Description DT Len Usage Min Max Table
Value

4 Universal CE 250 R 1 1
Service
Identifier

4.1 identifier Identifies the type of result as ST 20 RE 0 1 SPOTCHE

monitor, spotcheck, or alarm. CK

7 Observation Date and time of the TS 14 R 1 1

Date/Time # measurement of the parameter
in ISO format
(YYYYMMDDHHMMSS).

7.1 Date/Time YYYYMMDDHHMMSS NM 14 R 1 1 200603281

34602

Observation/Result (OBX) Segment

The OBX segment reports results and alerts. There is one OBX segment for each result or
alarm value. OBX segments for periodic data are sent at a fixed interval. OBXs for aperiodic
data (NBP measurements and predictive temperature measurements) are sent when they
occur.

Examples:

OBX||TX|1^Red Alarm^MDIL-ALERT|0|ASYSTOLE||||||F<CR>

OBX||TX|2^Yellow Alarm^MDIL-ALERT|0|HR LOW, HR=55||||||F<CR>

OBX||TX|6^Soft Inop^MDIL-ALERT|0|TEMP LOW, TEMP=35.0||||||F<CR>

OBX||NM|0002-4bb8^SpO2^MDIL|0|95|0004-0220^%^MDIL|||||F<CR>

OBX||NM|0002-4182^HR^MDIL|0|60|0004-0aa0^bpm^MDIL|||||F<CR>

OBX||NM|0002-4a05^NBPs^MDIL|0|120|0004-0f20^mmHg^MDIL|||||F<CR>

OBX||NM|0002-4a06^NBPd^MDIL|0|70|0004-0f20^mmHg^MDIL|||||F<CR>

2-8 HL7 Messages

 ORU Message Syntax

OBX||NM|0002-4a07^NBPm^MDIL|0|91|0004-0f20^mmHg^MDIL|||||F<CR>

OBX||NM|0401-0b54^pTemp^MDIL|0|37.1|0004-17a0^C^MDIL|||||F<CR>

OBX||NM|0002-4a15^IBPs^MDIL|0|120|0004-0f20^mmHg^MDIL|||||F<CR>

OBX||NM|0002-4a16^IBPd^MDIL|0|70|0004-0f20^mmHg^MDIL|||||F<CR>

OBX||NM|0002-4a17^IBPm^MDIL|0|91|0004-0f20^mmHg^MDIL|||||F<CR>

OBX||NM|0002-50b0^etCO2^MDIL|4|38|0004-0220^%^MDIL|||||F<CR>

OBX||NM|0002-5000^Resp^MDIL|4|23|0004-0ae0^rpm^MDIL|||||F<CR>

OBX||NM|0401-0068^YSI^MDIL|0|37.1|0004-17a0^C^MDIL|||||F<CR>

OBX||NM|0002-5012^awRR^MDIL|4|30|0004-0ae0^rpm^MDIL|||||F<CR>

The following table describes each field in the OBX segment.

Sample
Seq. Field Description DT Len Usage Min Max Table
Value

1 Set ID - Sequence number in the SI 4 RE 0 1

OBX segment group.

2 Value Type • NM = Numeric ID 2 R 1 1 0125 NM

(SpotCheck, monitor),
• TX = Text (alarms)

3 Observation This field contains a unique CE 250 R 1 1

Identifier identifier for the observation.
The format is:
<identifier> ^ <text> ^ <name
of coding system>
Two types of observations are
supported: vital signs
observations (monitor and
spot-check) and alarm
observations. The Coding
system is “MDIL” or
“MDIL-ALERT”.
Example:
0002-4182^HR^MDIL

3.1 identifier This field contains a unique ST 20 R 1 1 0002-4182

identifier for the observation -
encoded using MDIL.

3.2 text Text value for the coded ST 10 R 1 1 HR

identifier.

3.3 name of Always “MDIL” or IS 4 RE 0 1 0396 MDIL

coding “MDIL-ALERT”.
system

HL7 Messages 2-9

ACK Message Syntax

Sample
Seq. Field Description DT Len Usage Min Max Table
Value

5 Observation Contains the result value or NM 5 R 1 1 23

Value string. In case of an alert
observation, this field contains
the alert message.

6 Units Contains unit information. CE 250 R 1 1

Example:
0004-0aa0^bpm^MDIL

6.1 identifier Code corresponding to the unit ST 20 R 1 1 0004-0aa0

of measure.

6.2 text Description text for the units of ST 10 R 1 1 bpm

measure.

6.3 name of Always “MDIL”. IS 4 RE 0 1 0396 MDIL

coding (fixed)
system

11 Observation Always set to "F" for Final. ID 1 R 1 1 0085 F

Result Status The monitor sends only final (fixed)
results.

ACK Message Syntax

The ACK message is sent by the receiving system back to the SureSigns VM patient monitor.
It acknowledges that the message was received.

The following table describes the segments within the ACK message.

Segment Description Usage Min Max

MSH Message header R 1 1

MSA Message acknowledgement R 1 1

The following syntax message information represents the profile for the Receiver. Any
message segment not supported is ignored. RE elements (required, but can be empty) will be
used, if valid, but ignored otherwise.

Each ACK message consists of these variable segments.

Message Header (MSH) Segment

The MSH segment is used primarily as a message envelope.

Example:

2-10 HL7 Messages

 ACK Message Syntax

MSH|^~\&|||||2006022012342200|ACK^^ACK_ALL|398098728972|P|2.4|
NE|NE|||415235.353.654

The following table describes each field in the MSH segment.

Sample
Seq. Field Description DT Len Usage Min Max Table
Value

1 Field ST 1 R 1 1 |
Separator

2 Encoding ST 4 R 1 1 ^~\&
Characters

7 Date/Time Of TS 26 R 1 1
Message

7.1 Date/Time Date and time of the NM 20 R 1 1 200602201

message transmission. 2342200

8 Message CM_ 15 R 1 1 0076

Type MSG

8.1 message type ID 3 R 1 1 0076 ACK

8.3 message ID 7 R 1 1 0354 ACK_ALL

structure

9 Message ST 20 R 1 1 398098728
Control ID 972

10 Processing ID PT 3 R 1 1

10.1 processing ID P - production is the only ID 3 R 1 1 0103 P

supported value

11 Version ID VID 60 R 1 1 0104

11.1 version ID ID 8 R 1 1 0104 2.4

12 Accept ID 2 R 1 1 0155 NE
Acknowledg
ment Type

13 Application ID 2 R 1 1 0155 NE
Acknowledg
ment Type

16 Conformance ID 10 RE 0 1 0449 415235.35

Statement ID 3.654

Message Acknowledgment (MSA)

The MSA message indicates the response code and the initiating message identifier.

Example: MSA|AA|USP100030220060510124500

HL7 Messages 2-11

MDIL Codes

The following table describes each field in the MSA segment.

Sample
Seq. Field Description DT Len Usage Min Max Table
Value

1 Acknowled The following codes are ID 2 R 1 1 0008 AA

gment Code supported:
• Accept: AA
• Reject: AR

2 Message Message control ID of the ST 20 R 1 1 USP10003

Control ID initiating message 022006051
(ORU^R01). 0124500

MDIL Codes
The SureSigns VM monitors use numeric codes from the Medical Device Interface Language
(MDIL) standard to uniquely identify parameter, alarm, and unit sources. The identifiers use
the following format:

<Partition>-<TermCode>

The values for the Partition and TermCode are hexadecimal values between 0x0000 and
0xffff, which are separated in the output with a “-” character.

Note The label strings in this chapter are valid only for installations with English language software.
When used in other countries, the label strings vary according to how they are translated into
the respective language. Philips recommends that for parameter identification, you use the
numeric parameter identifiers instead of parameter labels.

2-12 HL7 Messages

 MDIL Codes

The following table shows the coding systems used by the SureSigns VM monitors.

Coding System Format of Identifier Format of Text

MDIL Contains a unique parameter/unit identifier that Contains the parameter label string
has the following format: or the unit string

<Partition>-<TermCode>

The values for Partition and TermCode are

hexidecimal values between 0x0000 and 0xffff
and follow the MDIL standard nomenclature.
Partition may be one of the following values:
0x0002 - SCADA partition
0x0401 - EMFC partition
0x0004 - Dimension partition (for units)

MDIL-ALERT Contains a unique ID for the severity of the alarm: Contains the alarm message

• 6 - Soft Inop. Corresponds to a low priority

(technical) alarm on the SureSigns VM
monitor.
• 2 - Yellow Alarm. Corresponds to a
medium priority alarm on the SureSigns
VM monitor
• 1 - Red Alarm. Corresponds to a high
priority alarm on the SureSigns VM
monitor.

The following table lists the MDIL codes for all SureSigns VM parameters. Only those
parameters that are available on your SureSigns VM monitor are exported.

Parameter
MDIL Code Description
Label
0002-4bb8 SpO2 Oxygen saturation of arterial blood

0002-4a05 NBP (s) Non-invasive blood pressure (systolic)

0002-4a06 NBP (d) Non-invasive blood pressure (diastolic)

0002-4a07 NBP (m) Non-invasive blood pressure (mean)

0002-4182 HR Heart rate

0002-4a15 IBP (s) Invasive blood pressure (systolic)

0002-4a16 IBP (d) Invasive blood pressure (diastolic)

0002-4a17 IBP (m) Invasive blood pressure (mean)

0002-50b0 etCO2 End-tidal CO2 concentation

0002-5012 awRR Airway respiration rate

0002-5000 Resp ECG respiration

HL7 Messages 2-13

MDIL Codes

Parameter
MDIL Code Description
Label
0401-0b54 pTemp Predictive temperature

0401-0068 YSI Continuous temperature

The following table lists the MDIL codes for the units of measurement.

MDIL Code Unit Label

0004-0220 % (percent)

0004-0f20 mmHg

0004-0aa0 bpm

0004-0ae0 rpm

0004-17a0 C (Celsius)

Note—Temperature measurements are exported in Celsius only; pressure measurements are

exported in mmHg only.

2-14 HL7 Messages

 3
Enabling Data Export
This chapter describes how to configure the SureSigns VM monitor to export patient data. It
also describes how to enable data encryption.

Configuring Data Export

To enable data export and configure the data export settings on the SureSigns VM monitor:

1. Rotate the navigation wheel until the System icon is highlighted, then press the wheel.
System
Icon The System Menu appears.
2. Turn the navigation wheel until the System Admin button is highlighted, then press the
wheel.
A Password window appears.
3. Enter the Administrator password (2-1-5) by turning the navigation wheel until the first
box is highlighted, then pressing the wheel. Turn the wheel to select the first digit, then
press the wheel to save the digit. Repeat this for the next two digits of the password.
4. Rotate the navigation wheel until the OK button is highlighted, then press the wheel.
The System Admin Menu appears.
5. Rotate the navigation wheel until the Networking button is highlighted, then press the
wheel.
The Network Configuration menu appears.
6. Specify an IP address for the monitor:
To obtain an IP address from a DHCP server, select the Obtain an IP address
automatically (DHCP) checkbox.
To assign a specific IP address, select the Use the following IP address checkbox, and
then use the navigation wheel to manually enter an IP Address, Subnet Mask, and
Default Gateway.
7. Rotate the navigation wheel until the Data Export Interval field is highlighted. Select
the desired export interval. The available options are: Disable, 5 min., 10 min., 15
min., 30 min., 1 hour, 2 hours, 4 hours, and 8 hours.
After you select an interval, the Server IP Address field becomes available.

8. Use the navigation wheel to enter the Server IP Address.

9. Rotate the navigation wheel to highlight the Server Port field. Enter the port number
for the server. The default value is 4000.
10. Optionally, enable the Encryption option. See the next section, Enabling Encryption,
for more information.
11. Rotate the wheel to highlight the Apply button, then press the wheel.
If you made changes to the IP address, a Reboot window appears. Select OK to reboot
the system.

Enabling Data Export 3-1

Enabling Encryption

If you did not make changes to the IP address, the System Admin Menu reappears.
Rotate the wheel to highlight the Return button. The System Menu reaappears. Press
the Main Screen button on the front panel to return to the main screen.

Enabling Encryption
The SureSigns VM monitor supports the RC4 stream algorithm for encryption. RC4 is a data
encryption algorithm based on the RC4 symmetric stream cipher. The shared encryption key
must reside on the SureSigns VM Monitor and the server.

To enable encryption, on the SureSigns VM monitor:

1. Open the Network Configuration menu, as described above.

2. Rotate the navigation wheel to highlight the Encryption checkbox and press the wheel
to check the box.
3. Enter the encryption key in the Encryption Key field.

Establishing a Connection
To establish a network connection, plug one end of an RJ-45 Ethernet cable into the Ethernet
port on the back of the monitor and the other end into a LAN port.

Connection icon After you configure the TCP/IP address of the designated server and enable the Data Export
function (as described in the previous section), the monitor attempts to establish a connection
to the server.

When a connection is established, a connection icon appears in the upper left corner of the
monitor’s screen. The connection remains in effect indefinitely. If the network goes down or
the monitor is shut down, the monitor will attempt to re-establish the connection when the
next export interval is due to occur.

Note Each SureSigns VM monitor can export data to one server. The monitor cannot be configured
to export data to multiple destinations.

3-2 Enabling Data Export

 Index

A ORU Message Header (MSH) segment, 2–5

ACK Message Header (MSH) segment, 2–10 ORU messages
ACK messages Common Order (ORC) segment, 2–7
flow of events, 2–2 example, 2–4
Message Acknowledgment (MSA), 2–11 flow of events, 2–2
Message Header (MSH) segment, 2–10 list of segments, 2–4
overiew, 2–10 Message Header (MSH) segment, 2–5
syntax, 2–10 Observation Request (OBR) segment, 2–8
Observation/Result (OBX) segment, 2–8
Aperiodic data, 1–1
overview, 2–3
C Patient Identification (PID) segment, 2–6
Patient Visit (PV1) segment, 2–7
Common Order (ORC) segment, 2–7
syntax, 2–3
Connection icon, 1–2
P
D
Patient Identification (PID) segment, 2–6
Data export
enabling, 3–1 Patient Visit (PV1) segment, 2–7
Periodic data, 1–1
E
S
Enabling data export
procedure, 3–1 Special characters, 2–2
Enabling encryption, 3–2 System requirements, 1–2
Encryption, 3–2
Establishing a connection, 1–2, 3–2
F
Flow of events, 2–2
H
HL7
notation conventions, 2–1
overview, 1–1
special characters, 2–2
HL7 messages
types of, 2–1
M
MDIL codes, 2–12
Message Acknowledgment (MSA) segment, 2–11
Message Header (MSH) segment
ACK, 2–10
ORU, 2–5
N
Notation conventions, 2–1
O
Observation Request (OBR) segment, 2–8
Observation/Result (OBX) segment, 2–8

Index-1
Index-2