Spacelabs XPrezzNet

XprezzNet™
96190
074-0211-01 Rev. A | www.spacelabshealthcare.com January 2016
S Y S T E M A D M I N I S T R A T I O N
M A N U A L
9 6190 XPREZZNET SYSTEM ADMINISTRATION MANUAL
©2016 Spacelabs Healthcare
All rights reserved. Contents of this publication may not be reproduced in any form without
the written permission of Spacelabs Healthcare. Products of Spacelabs Healthcare are
covered by U.S. and foreign patents and/or pending patents. Printed in U.S.A. Specifications
and price change privileges are reserved.
Spacelabs Healthcare considers itself responsible for the effects on safety, reliability and
performance of the equipment only if:
• assembly operations, re-adjustments, modifications or repairs are carried out by persons

authorized by Spacelabs Healthcare, and
• the electrical installation of the relevant room complies with the requirements of the
standard in force, and
• the equipment is used in accordance with the operations manual.
Spacelabs Healthcare will make available, on request, such circuit diagrams, component part
lists, descriptions, calibration instructions or other information which will assist appropriately
qualified technical personnel to repair those parts of the equipment which are classified by
Spacelabs Healthcare as field repairable.
Spacelabs Healthcare is committed to providing comprehensive customer support beginning
with your initial inquiry through purchase, training, and service for the life of your Spacelabs
Healthcare equipment.
CORPORATE OFFICES
Corporate Headquarters
Spacelabs Healthcare, Inc.

35301 SE Center Street
Snoqualmie, WA 98065
U.S.A.
Telephone: (1) 800-287-7108
Telephone: (1) 425-396-3300
Authorized EC Representative
Spacelabs Healthcare, Ltd.

43 Moray Place
Edinburgh, EH3 6BT
Scotland
Telephone: 44 (0) 131 240 6481
Fax: 44 (0) 131 240 6459
Please refer to http://www.spacelabshealthcare.com/en/company/trademarks for a full listing of

Spacelabs Healthcare trademarks. Other brands and product names used herein are trademarks of their
respective owners.
• Rx Only U.S. Federal law restricts the devices documented herein to sale by or on
the order of a physician.
• Before use, carefully read the instructions, including all warnings and cautions.
www.spacelabshealthcare.com
Table of Contents
1 Introduction
About this manual............................................................................................................ 1-1
Conventions used in this manual ............................................................................... 1-1
XprezzNet overview....................................................................................................... 1-3
XprezzNet compatibility............................................................................................... 1-4
XprezzNet intended use ............................................................................................... 1-5
Potential users .................................................................................................................. 1-5
2 Installation
Overview............................................................................................................................. 2-1
System requirements.................................................................................................... 2-2
Prerequisites..................................................................................................................... 2-2
List of prerequisites ............................................................................................ 2-3
Deployment ...................................................................................................................... 2-3
To deploy XprezzNet ........................................................................................... 2-4
To verify the deployment of XprezzNet ....................................................... 2-5
3 Licensing
Licenses............................................................................................................................... 3-1
Product Activation......................................................................................................... 3-2
To activate XprezzNet ......................................................................................... 3-2
4 Administrative Interface
XprezzNet Administration ........................................................................................... 4-1
Main Menu .............................................................................................................. 4-1
XprezzNet Administration (home page) .................................................... 4-2
To open the XprezzNet home page ............................................................... 4-2
Status ............................................................................................................................. 4-3
To confirm that the list of devices is shown................................................ 4-3
Devices .......................................................................................................................... 4-5
To see the properties of a device....................................................................4-6
Connected Clients .....................................................................................................4-8
Configuration ....................................................................................................... 4-8
Available configuration settings .................................................................... 4-9
General Configuration Settings ...........................................................................4-9
Settings for Monitoring XTR Devices ...............................................................4-12
UVSL Networks Configuration ............................................................................4-12
Settings to Control Health Status Monitoring .............................................. 4-14
Logging Configuration Settings ........................................................................ 4-15
Metrics ................................................................................................................... 4-16
Counters ..................................................................................................................... 4-16
Timers ...........................................................................................................................4-17
Gauges ..........................................................................................................................4-17
Meters .......................................................................................................................... 4-18
Logs ........................................................................................................................ 4-18
To download logs ................................................................................................ 4-18
Support ................................................................................................................ 4-20
Upgrade instructions ...................................................................................................4-21
To uninstall XprezzNet 1.1 ..................................................................................4-21
To upgrade XprezzNet from an earlier software version ....................4-22
To uninstall XprezzNet 1.2 ................................................................................4-22
5 Security
Overview of Security ..................................................................................................... 5-1
Windows Firewall Configuration.............................................................................. 5-2
To configure the Windows firewall and inbound ports .......................... 5-2
To set up the outbound port............................................................................. 5-2
www.spacelabshealthcare.com I
XPREZZN ET (91690)
SYSTEM ADMINISTRATION MANUAL
6 Troubleshooting
Problems and Solutions ............................................................................................... 6-2
To uninstall XprezzNet 1.2 ..................................................................................6-9
A Appendix A — Symbols
II www.spacelabshealthcare.com
XPREZZNET (916 90)
Introduction
XprezzNet™ (96190) is a network interface that exports Spacelabs Healthcare patient

monitoring information to external systems, such as Electronic Medical Records (EMR).
The information sent to the EMR includes alert notification systems, remote viewing
applications, and more. To enhance workflow, XprezzNet also enables patient-to-device
association from external systems.
About this manual

This manual provides instructions to install, license, configure, secure, and troubleshoot
Spacelabs Healthcare XprezzNet (96190).
• Installation—Installation on page 2-1
• Licensing the product—Licensing on page 3-1
• Settings and configuration—Administrative Interface on page 4-1
• Firewall and Security—Security on page 5-1
• Troubleshooting with logs, event logs, and messages—Troubleshooting on page 6-1
Conventions used in this manual

Some of the formatting conventions used in this manual are as follows:
For manuals viewed in PDF format, reference links are blue. Blue typeface is a potential link
to additional information in the manual. Hover the mouse over the blue text and click to go
to the linked topic. Reference links are located throughout the manual, which includes the
Table of Contents.
• Non-blue italicized typeface is used for references to information outside this manual.
This style of typeface can indicate references to other manuals or information which is
available in another form, as identified by a title and a part number.
• Blue typeface is also used to identify URLs or browser addresses.
www.spacelabshealthcare.com 1-1
XPREZZNET (91690) I NTRODUCTION
• Bold typeface indicates text labels, phrases, or titles that show on an LCD or display
which are part of a Spacelabs Healthcare software application. Bold typeface can also
indicate the formal name of a graphical user interface, such as an icon or control, but
which does not include a text label or title.
• A term that is ALL CAPITALIZED can represent a user interface such as a key label or
menu, a status, or error message on a host monitor.
• Numbered steps are presented to accomplish a task. Some steps conclude in a step
result—unnumbered, indented text.
• Warnings, cautions, and notes are listed in the priority of the information. Warnings are
of the highest priority. Notes, while important, are not as serious as the warnings and
cautions. Examples of warnings, cautions, and notes follow.
Warnings indicate potentially harmful conditions that

could lead to injury or death.
Cautions indicate conditions that could lead to damage to or

malfunction of the device.
Note:
Notes alert the user to relevant facts and conditions.
1-2 www.spacelabshealthcare.com
XPREZZNET (916 90) INTRODUCTION
XprezzNet overview
• Customers who use XprezzNet are responsible for their own network
security settings. Such settings include firewalls, anti-virus
applications, and other related security, such as the encryption of
electronic Protected Health Information (ePHI).
• The security of XprezzNet depends on the security of the network.
Spacelabs Healthcare is not responsible for any breaches of security
related to hospital system network configurations.
XprezzNet provides an Administrative Interface web application to set up and configure

medical device networks to work with Spacelabs Healthcare monitoring devices. For more
information on the Administrative Interface, refer to Administrative Interface on page 4-1.
As a web services application, XprezzNet does not expose a graphical user interface. The
XprezzNet Application Programming Interface (API) provides a way for developers to
create applications which capture patient monitoring data and make it available to a
third-party client application.
XprezzNet is a Windows Communication Foundation (WCF) service hosted under Internet
Information Service (IIS) 7.5 or later. XprezzNet provides a Representative State Transfer
(REST) interface.
The network interface server connects with RESTful APIs that provide the means to receive
clinical data, such as vitals data, alarms, change limits notification, and waveform data.
Spacelabs Healthcare Ultraview™ SL, XPREZZON™, qube™, or Xhibit™ Telemetry System
monitoring devices provide the data to the third-party product. The third-party interface is
responsible for any translation of the data. For an example of the XprezzNet workflow,
refer to Figure 1-1 on page 1-3.
Figure 1-1 XprezzNet exchange of data flow chart
For more information on the use of XprezzNet APIs, refer to XprezzNet Developer’s Guide
(P/N 074-0227-xx).
The XprezzNet data sheet (P/N 061-2657-xx [English] and P/N 061-2673-xx [French
Canadian]) contains more detailed information on the product, including features, product
specifications, and licenses.
XprezzNet compatibility
XprezzNet is compatible with Ultraview SL™, XPREZZON™, and qube™ bedside monitors,
the Xhibit™ Telemetry System, and selected parameter modules and Flexports. For more
information, refer to Table 1-1 on page 1-4.
Do not install XprezzNet and Intesys® Clinical Suite (ICS) G2 on the

same CPU.
Notes:
• Check that monitors and modules for use with XprezzNet are compatible versions.
• Use TCP/IP monitoring networks only.
• XprezzNet can coexist with ICS G2 Monitor Loader on the same network and
communicate with the same monitors. XprezzNet and Monitor Loader must be on
separate servers.
• XprezzNet APIs are authorized for use only with applications approved by
Spacelabs Healthcare.
Table 1-1 XprezzNet Compatibility
Product Software version
Monitors
Ultraview™ SL (2200/2400/2600) 2.03.11, 2.03.13
Ultraview SL (2700/2800/2900) 2.03.11, 2.03.13
XPREZZON™/qube™ (91393/91390) 3.03.00, 3.04.xx, 3.05.xx
Modules
Command Module (90496) 1.02.28
Command Module (91496) 2.02.04, 2.03.05, 2.03.06, 2.04.xx, 2.05.xx
Capnography Module (91517) 1.00.11, 1.00.12
SvO2/ScvO2 (91424) 1.00.03, 1.00.05
Capno Pod (92516) 1.00.01
Capno Module (92517) 1.00.00
XPREZZNET (916 90) INTRODUCTION
Table 1-1 XprezzNet Compatibility (Continued)
Product Software version
Multigas Module (91518) 1.00.16, 1.00.17
Multigas (92518) 1.00.01
BISx Module (91482) All
External Devices
Xhibit™ Telemetry Receiver (96280) All
Flexport® System Interfaces
90422A-03 Sentec 2.00.02
90436A-15 Puritan Bennett 840 1.00.05, 1.00.06
91436B-A Maquet SERVO-i 1.00.01, 1.00.05
90442A-03 Edwards Vigilance II 2.00.02
90442A-03 Masimo Radical 2.00.02
91439B-A Edwards Vigileo 1.00.00
91443A-A ARKON All (numeric data only)
91443C-A Dräger Apollo/Primus/Primus IE/Perseus 1.00.01 (numeric data only)
XprezzNet intended use

XprezzNet is a software application intended for use in the transportation, aggregation and
derivation of data between medical devices.
XprezzNet is not intended to directly monitor, diagnose or treat patients or to be used in
the prevention of a disease or condition, nor does XprezzNet come into direct contact with
patients.
Potential users
The potential users of XprezzNet are classified into various categories as follows.
• Software Developers—The developer works for the hospital or a third-party contracting
organization. They program XprezzNet API services to function as planned between
Spacelabs Healthcare monitors and the third-party devices or systems. For more
information on the API services, refer to the XprezzNet™ 96190 Developer’s Guide
(P/N 074-0227-xx).
• Biomedical Engineers—A biomed installs, supports, and repairs monitoring systems and
sometimes network interfaces. Biomeds can work directly for the hospital, for a
third-party contract organization, or work as a Spacelabs Healthcare Field Service
Engineer (FSE). If nurses or technicians have problems with the system, the inhouse
Biomed is typically the first person called. Biomeds can configure the network interface
server connection to the monitoring network.
• Enterprise Integration Managers (EIMs)—Spacelabs Healthcare EIMs install and confirm
XprezzNet functionality, update software and licensing, and access audit and error logs
for troubleshooting the system.
• Global Technical Support (GTS)—Spacelabs Healthcare GTS personnel troubleshoot
customer issues.
• IT Staff—IT staff install, support, and repair network interfaces, computer systems,
servers, and applications.
• Clinicians—Clinicians such as physicians, nurses, and other healthcare professionals use
the monitor devices that generate the data. They are also consumers of the data in the
vendor applications.
XPREZZNET (916 90)
Installation
Overview
The XprezzNet™ is a REST web service that runs under IIS 7.5 or later. XprezzNet runs
on either Windows Server 2008 R2 with Service Pack 1 or Windows Server 2012 R2.
XprezzNet uses an application-friendly way to communicate with Spacelabs Healthcare
medical devices.
Notes:
• IIS 7.5 applies to Windows 7, Windows Server 2008, Windows Server 2008 R2,
and Windows Vista.
• IIS 8 applies to Windows Server 2012 R2.
When an earlier version of XprezzNet is already installed, do changes in

this order.
• First, set up a new server to install the newest version of XprezzNet.
• Second, decommission the server with the older version of
XprezzNet.
To verify deployment, enter license information, or configure the application to use the
XprezzNet Administrative Interface. For more information, refer to To verify the
deployment of XprezzNet on page 2-5, Licenses on page 3-1, and XprezzNet
Administration on page 4-1.
Your user account must be added to the local Administrator group to access the
Administrative Interface.
Notes:
• The XprezzNet Administrative Interface is only available if you are given local
administrative access to the host server that XprezzNet runs on. This access
limitation allows the local system administrator to control access to electronic
Protected Health Information (ePHI) available through the Administrative Interface.
XPREZZNET (91690) I NSTALLATION
• Always access the Administrative Interface remotely and NOT from the XprezzNet
server. Versions of Windows Server on which XprezzNet runs include a loop-back
security check feature. This security feature prevents access to the interface from the
local console or a local instance of Internet Explorer.
System requirements
These requirements apply any server that runs XprezzNet.
• Windows Server 2008 R2 SP1, Windows Server 2012 R2
• CPU—Intel Xeon E5-1410 2.80 GHz, 10 M Cache, Turbo, 4 Core
• Minimum memory (RAM), 8 GB
• 300 GB of free disk space
• Dual network connection at 1 GBE
Prerequisites
Before you install XprezzNet, make sure you have the system requirements listed in System
requirements on page 2-2 and the prerequisites listed in this section.
Note:
During the XprezzNet installation process, the XprezzNet application automatically
installs Microsoft Visual C++ 2010 Redistributable Package and .NET 4.5.1.
• As installation progresses, XprezzNet checks for the required

components. If not found, the installation process stops.
• Do NOT install XprezzNet on the same computer with another
high-performance application that uses an HDD read/write
operation of 2 Gbs or faster, has 20% or more CPU consumption,
or uses 10% or more network bandwidth.
• Do NOT install XprezzNet on the same computer with
Intesys® Clinical Suite (ICS) G2.
XPREZZNET (916 90) I NSTALLATION
List of prerequisites
Note:
XprezzNet operates in English only, regardless of the system locale.
• IIS 7.5 or later
• Some of the XprezzNet APIs are accessible from a default website that runs under
IIS on port 80 or SSL port 443.
Note:
When there is an SSL connection with port 443, everything that goes through the
connection is encrypted.
• The installation server is on the same local network as all Spacelabs Healthcare
monitors and devices.
• Set up the server to run on the same local network as the Spacelabs Healthcare devices
to which XprezzNet needs access.
Note:
You can install and use Spacelink Axeda separately, but it is not required to run
XprezzNet. Spacelink Axeda is not a part of the installation package.
Deployment
Do NOT modify any XprezzNet deployment components. Spacelabs

Healthcare does not support modifications to the application.
Install the complete package with default options for each software application. Use the
web addresses provided to download the software. The web addresses are provided in the
procedures that follow.
XprezzNet customer documents are available on the software installation CD-ROM in
portable document format (PDF).
• XprezzNet™ 96190 System Administration Manual (P/N 074-0211-xx)
• XprezzNet™ 96190 Data Sheets (P/N 061-2657-xx, English) and
(P/N 061-2673-xx, French Canadian)
The XprezzNet™ Developer’s Guide (P/N 074-0277-xx) is available through Global
Technical Support as part of a developer’s contract issued by Spacelabs Healthcare.
To deploy XprezzNet
1 Log in to the XprezzNet server as an administrator.
Note:
To log in, an administrator must add your user account to the Administrators group on
the correct server.
2 Open the XprezzNet software distribution CD-ROM.
3 From the CD-ROM, run the installer XprezzNetInstaller.exe.
XprezzNetInstaller Setup window opens.
Figure 2-1 XprezzNetInstaller Setup window
4 Select Install.
The Setup Successful window shows.
Figure 2-2 Setup Successful
XPREZZNET (916 90) I NSTALLATION
5 Select Close.
The installation is complete.
To verify deployment, use the XprezzNet Administrative Interface to enter license
information and configure XprezzNet for your network and medical monitoring devices.
For more information, refer to Licensing on page 3-1 and Administrative Interface on
page 4-1.
To verify the deployment of XprezzNet

Always access the Administrative Interface from a remote computer and not from the
XprezzNet server. Advanced Windows security features could interfere with access to the
interface when you try to log on locally to use the Administrative Interface.
Note:
Always check the event log for errors from XprezzNet to check that it restarted.
1 On a remote computer, navigate to http://[server]/XprezzNetAdmin/.
Note:
In this manual, [server] represents the fully qualified server name for your XprezzNet
installation.
2 At the Windows Security window, enter your user name and password to log in.
Note:
Your user account must be added to the local Administrator group to access the
Figure 2-3 Windows Security—log in to XprezzNet Administrative Interface
3 Select OK.
When verified, the XprezzNet Administration home page shows (refer to Figure 2-4).
If a different screen shows, contact Spacelabs Healthcare for assistance.
Figure 2-4 Verification of XprezzNet deployment
Note:
If there is a problem with the installation, refer to To uninstall XprezzNet 1.2 on page 6-9.
XPREZZNET (916 90)
Licensing
Licenses
To license the XprezzNet application for your device network, use the XprezzNet
Administrative Interface. For more information on the Administrative Interface, refer to
Administrative Interface on page 4-1.
Before you can configure XprezzNet, activate the license first.
If you have to install XprezzNet for development or test purposes, contact a Spacelabs
Healthcare representative for a developer license code.
There is a predefined limit of licensed devices based on the category of licenses purchased.
Know the limits of the host server that XprezzNet is set to run on. Change the default limits
of licensed devices to within the server limitations.
Your license is preserved in the Nalpeiron license manager as long as your upgrade is on
the same server with your computer’s GUID.
On same server, you can uninstall XprezzNet 1.1 and install XprezzNet 1.2. The license still
shows as activated.
If you move to a different server, contact GTS to deactivate your current license code on
the older server.
A failure to match the settings to within the actual network limitations

can result in a critical overload that could affect or stop the XprezzNet
service.
XPREZZNET (91690) L ICENSING
The XprezzNet limits for devices are as follows:

• 64 licensed devices with waveforms.
• 128 licensed devices without waveforms.
The default XprezzNet out-of-box settings are as follows:
• 90 licensed devices with waveforms
• 100 licensed devices without waveforms
Product Activation
The XprezzNet Administrative Interface is only available if you have local administrative
access to the host server that XprezzNet runs on. This access limitation allows the local
system administrator to control access to electronic Protected Health Information (ePHI)
available through the Administrative Interface.
To activate XprezzNet
Before you can configure XprezzNet, you must first activate the license.
Notes:
• A valid 18-character license code is required to complete the activation.
• A valid license for multiple devices is usable on multiple servers, but you can use it
only once on each server.
• To reuse a license on the same server, please contact GTS to deactivate the license
on that server.
1 Enter http://[server]/XprezzNetAdmin/Licensing/Index in your browser.
Before activation, the home page looks empty, as in Figure 3-1.
Figure 3-1 Before activation
2 Enter the valid 18-digit license code shipped with your product.
As you enter the license code, the Activate XprezzNet button shows but is not enabled
until you enter 18 characters.
XPREZZNET (916 90) LICENSING
Figure 3-2 Partially activated XprezzNet
3 Select Activate XprezzNet.

Activation succeeded shows next to the Activate XprezzNet button.
Note:
If you incorrectly enter any license code, Invalid License Number shows next to the
Activate XprezzNet button.
Figure 3-3 Activation succeeded
4 Press F5 to refresh the browser and to open the Product Activation Status page.
• If you correctly entered a valid 18-digit code that is not already in use, the Product
Activation Status window shows with Activated in the lower right, as in Figure 3-4.
• For added security, an alias number replaces the actual license code and shows in
the InstallationID field.
• A new Product Activation entry field is automatically added to allow any license
updates to the existing license on the same server. Use this field to replace the
existing license with a new license on the same server.
License Code number changes to

an alias InstallationID number
Product Activation field for

future license updates
Figure 3-4 Already activated after refresh
XPREZZNET (91690) L ICENSING
Note:
If a delay of more than a few minutes occurs, select Restart Service from the XprezzNet
Administration, Status window. Restart Service refreshes the process. If there is still an
extended delay, contact your Spacelabs Healthcare Global Technical Support.
5 Take notes on the Maximum Devices(CDF) value from the Product Activation Status
page.
The CDF value represents the maximum number of devices that the installed XprezzNet
instance supports. It corresponds to the number of Devices in the home page Status
section (refer to Figure 3-5).
Spacelabs Healthcare recommends that your CPU usage does not exceed more
than 50%. The device limits are controlled in the Configuration settings. For more
information, refer to Administrative Interface on page 4-1 and to Troubleshooting on
page 6-1.
Figure 3-5 Home page—number of devices active on the network
Notes:
If you enter either the original active license code or the update license code again, That
License Number has already been used shows next to the Activate XprezzNet button
on the Product Activation Status (refer to Figure 3-6). If you get this message and need
to reuse that licenses code on that server, contact Spacelabs Healthcare GTS to reset
your existing license association.
Figure 3-6 License is already used
XPREZZNET (916 90)
Administrative Interface
XprezzNet Administration
The XprezzNet Administrative Interface is a tool that allows you to configure the
XprezzNet application for your device network.
To configure the product, do the steps in Licensing on page 3-1 before you use the
Note:
After changes are made to any configuration setting, manually refresh the browser
window to confirm the results of the changes.
Main Menu
The main menu of the Administrative Interface includes the list that follows:
• Licensing on page 3-1
• XprezzNet Administration on page 4-1
• Configuration on page 4-8
• Metrics on page 4-16
• Logs on page 4-18
• Support on page 4-20
Figure 4-1 XprezzNet Administration (home page) and the main menu
XPREZZNET (91690) ADMINISTRATIVE INTERFACE
XprezzNet Administration (home page)

The XprezzNet Administration menu link takes you to the home page for the
The XprezzNet Administration home page consists of three sections:
• Status
• Devices
• Connected Clients
To open the XprezzNet home page

1 From your browser, enter http://[server]/XprezzNetAdmin/.
-OR-
From the XprezzNet Administration main menu, select Configuration.
Figure 4-2 XprezzNet Administrative Interface home page
XPREZZNET (916 90) ADMINISTRATIVE INTERFACE
Status
The Status section describes the health of the network, the number of devices, and
streaming and waveform connections on the network. The Health of the network is
described here as Good, Server Overloaded, Server Critically Overloaded, or Server
Down. For status definitions, refer to Table 4-1 on page 4-4.
Spacelabs Healthcare recommends that your CPU usage does not exceed 50%. The device
limits are controlled in the Configuration settings. For more information, refer to
Administrative Interface on page 4-1 and to Troubleshooting on page 6-1.
The Restart Service button is located here. Restart Service restarts the application pool in
the Internet Information Services (IIS) web server, which restarts all web applications on
the server. When you use Restart Service, expect momentary downtime and disconnected
network devices until the service comes back up.
Notes:
• After changes are made to any configuration setting, manually refresh the browser
window or press F5 in order to see the results of the changes.
• To confirm your changes, navigate to the Administrative Interface home page.
Figure 4-3 Status section on the Home Page
To confirm that the list of devices is shown

1 From the main menu select XprezzNet Administration to view the home page or visit
http://[server]/XprezzNetAdmin.
2 After 20 seconds if no devices or an incomplete list of devices is shown, repeat the
attempt to allow the service to initialize fully. From the XprezzNet Administration page,
you can also select Restart Service. For assistance, contact Spacelabs Healthcare Global
Technical Support.
Note:
Restart Service restarts the application pool in the Internet Information Services (IIS)
web server, which restarts all web applications on the server.
If you are a developer, use the XprezzNet API help page at
http://[server]/XprezzNet/help/.
For more information on all the supported data types and their structure as well as
information on the XprezzNet API, refer to XprezzNet Developer’s Guide
(P/N 074-0227-xx).
Table 4-1 Status definitions on the Home Page
Status Definition
Time The current date and time associated with the network server.
Health What shows here indicates the status of the network connections.
This description depends on the settings entered under Settings
to Control Health Status Monitoring on page 4-14.
• Good (green background) indicates that no limits exceed any
settings entered under Settings to Control Health Status.
• Server Overloaded (yellow background) indicates that the
network connections and devices are close to exceeding the
limits entered under Settings to Control Health Status for
streamed data connections and the number of devices
monitored.
Message shown: Device Yellow Limit Exceeded
• Server Critically Overloaded (red-orange background)
indicates that the network connections and device limits
exceed the limits entered under Settings to Control Health
Status for streamed data connections and the number of
devices monitored.
Message shown: Device Red Limit Exceeded
• Server Down (red background) indicates that the XprezzNet
server is down.
Message shown: No response
Devices The number of available network devices.
Streaming Connections The combined number of alert streams and waveforms derived
from the API.
Connected Waveform Feeds The number of connected waveform feeds from available devices
on the network.
Restart Service Restart Service restarts the application pool in the Internet
Information Services (IIS) web server, which restarts all web
applications on the server.
When you use Restart Service, expect momentary downtime and
disconnected network devices until the service comes back up.
Devices
When a device is marked offline, it is removed from the active device list during the next
cleanup cycle. SalishCDI.DevicesAutoCleanup static property controls device cleanup. For
more information on status definitions, refer to Table 4-2.
For telemetry devices, channel numbers identify telemetry devices instead of Node IDs and
the farm names show instead of network numbers (refer to Figure 4-4 on page 4-5). Refer
to Table 4-2 for status descriptions for devices.
To sort a column, select a blue link in the heading.
Node ID (corresponds to a unique bed name)

Network number
Device type
Figure 4-4 Devices
Table 4-2 Device Status Definitions
Status Definition
Offline Device did transmit, but is no longer reachable.
Available Device is known to exist on the network.
Connected A connection to the network is active and ongoing.
TopicLimitExceeded An active connection was made to the device and is ongoing. However,
too many other devices are connected and no slots for topics are
available on the subject device.
Standby An active connection was made to the device and is ongoing, but the
device is in Standby Mode.
Subscribed The device is fully connected and all CDI topics are connected.
ConnectRefused The device is online, but has actively rejected connections.
ConnectTimeout The device is online, but the device does not respond to connection
attempts.
ConnectError Device is online, but the device does not respond to connection
attempts.
To see the properties of a device

1 From the XprezzNet Administration home page under Devices, select the blue link in
the Id column.
A page opens with a list of topics and feeds set up for that device through the API.
2 Select General.
Links to Properties and Patient show.
3 To see the properties associated with the device, select Properties or Patient. For an
example of properties and patient data, refer to Figure 4-5.
Notes:
• ECG and SpO2 are the only topics available to view for telemetry devices. SpO2 does
not have waveform data.
• Data is organized around the ECG leads received from a telemetry transmitter.
Figure 4-5 General Properties of a bedside monitor and the patient
4 Select a topic from the list of available topics. Topics shown here depend on the API
requests set up on the development side. For more information on the API, refer to
XprezzNet Developer’s Guide (P/N 074-0227-xx).
Figure 4-6 Example of properties for TOPIC-ECG
Notes:
• The Waveforms category includes an interface that depicts a waveform from a
device. To begin the waveform replica, select the play button for Waveform1 or
Waveform2. Telemetry devices include a waveform for each ECG lead connected to
a patient.
• The sample waveforms shown here are not intended as accurate depictions of actual
waveforms on a monitor. They only confirm that waveform data is moving through
the XprezzNet system from a monitoring device.
Connected Clients
The settings under Connected Clients cannot be changed in this view. These fields
populate automatically depending on the network and API configurations.
Figure 4-7 Connected Clients
Table 4-3 Connected Clients Definitions
Status Definition
Client IP IP address of clients connected to the XprezzNet network.
Connection Type The underlying network or connection type of the devices that
the web application accesses.
Connection Request Uri String used to connect to the resource, which enables
interactions with representations of the resource over a network
or web.
Configuration
All the configuration values discussed here are required, unless stated otherwise. Configure
XprezzNet AFTER deployment and licensing, but BEFORE the first use of XprezzNet.
XprezzNet exposes the application setting to the user.
Non-editable fields that show in Configuration pages contain data from the different
sources related to the XprezzNet setup. These fields are shown in the Logging
Configuration Settings (refer to Logging Configuration Settings on page 4-15) and Metrics
(refer to Metrics on page 4-16).
• After you have entered all your changes, navigate to the end of the
configuration groups near the bottom of the web page.
• Select the Update Configuration button.
• No configuration settings are saved unless you select Update
Configuration.
Notes:
• Make all configuration changes and then select the Update Configuration button
near the bottom of the Configuration window.
• After changes are made to any configuration setting, manually refresh the browser
window or press F5 in order to see the results of the changes.
• If a delay of more than three minutes occurs during configuration, go to the

XprezzNet Administration home page and select Restart Service to refresh the
process. If there is more delay, contact your Spacelabs Healthcare representative.
• To confirm your changes, navigate to the XprezzNet Administration home page.
Available configuration settings

The available XprezzNet Administrative Interface configuration categories are listed
as follows.
• General Configuration Settings
• Settings for Monitoring XTR Devices
• UVSL Networks Configuration
• Settings to Control Health Status Monitoring
• Logging Configuration Settings
General Configuration Settings

Definitions for the General Configuration Settings are shown in Figure 4-8.
Figure 4-8 General Configuration Settings
Table 4-4 Available Fields Under General Configuration Settings
Label Definition
Log purging will maintain Min Per Cent To prevent the drive designated for log files from
Free Disk Space filling up completely, enter between 20% and 50%.
Failure to maintain enough free space on the drive
can result in an interruption to the XprezzNet
service.
Note:
This control sets the minimum free storage space
on the drive designated for log files. Once the
limit is reached on that drive, the system deletes
excess XprezzNet log files to maintain the
configured free space. However, the purger
cannot delete an active log file.
Process Waveforms Select or deselect this control to include or exclude

waveform data from the overall data stream that
XprezzNet provides to the client system.
How long (seconds) before a device times out Sets a countdown timer that determines when to
remove a device from the device list provided to the
client. The countdown timer starts when there is no
response from a device for the designated amount of
time entered.
Note:
This control can affect the device list and the
count on the Administrative Interface home page.
When the configured time expires, the device is
removed from all device lists.
Categories included in AlertStreams
The label Categories included in AlertStreams includes a number of continuous data streams. Default
selections are indicated in the scroll list by white text on blue background (refer to Figure 4-9). You can
select which of these alert streams are reported through the AlertNotificationStream and
AlertNotificationSSE queries. By default, four general streams are reported.
Default alert streams
GeneralAlert These alarms include general technical alarms data

from the monitored devices.
LimitAlert These alarms indicate the value range that defines

the limits set on the monitor from one of the
monitored devices.
Status Reports status updates on a monitored device. For

example, a change of ECG leads.
Table 4-4 Available Fields Under General Configuration Settings (Continued)
Label Definition
ExtendedStatus This alert stream provides further detail on the

reported status from devices. For example, a change
in a patient age group.
LimitChange This alert stream reports changes to alarm limits.
SystemNotifications This is a system-level alert, such as a notification

that a device dropped off the system and was
re-established.
You can select more streams specific to monitor models or modules. For example, the
VitalsData stream continuously reports numeric data from devices as it becomes available.
The streams and their contents are described in detail in the extended topics and feeds
help page, available at http://[server]/XprezzNet/SpacelabsDataTypes.htm.
Note:
Too many LimitAlert streams added through API requests can affect the overall
performance of XprezzNet, which depends on server capacity and network
infrastructure.
Figure 4-9 Example of default alert streams (white text on blue ground)
Feeds of the same name can contain different information, which depends on the device
which reports the data. To minimize network and server load, Spacelabs Healthcare
recommends that you subscribe to a minimum set of feeds.
• Select one or more categories from the available list.
• To select more than one category from the scroll list, press and hold the Ctrl key as you
select new categories.
• If you do not use the Ctrl key to select more categories, existing selections drop off
the list.
Settings for Monitoring XTR Devices

A separate network is required for devices associated with the Xhibit Telemetry Receiver.
Figure 4-10 Settings for Monitoring XTR Devices
Table 4-5 Available Fields Under Settings for Monitoring XTR Devices
Label Definition
XTR Farm Name Enter the name of the telemetry farm.
Transmitters to Monitor Enter the telemetry channels that you want to include in
the XprezzNet setup. Use any character to separate the
values, such as comma or colon. For a range of values,
use the hyphen to separate.
Ignore these Transmitters Enter the channel numbers of available transmitters on

the network that you want to ignore.
Use common delimiters as separators with no extra
space before or after the separator. For example,
1111,1222,1333,1444.
UVSL Networks Configuration

Use UVSL Networks Configuration to add or delete networks to and from the XprezzNet
system.
At first use, there are no network fields. Select Add new UVSL Network and complete the
required information for a network to show here. To save your changes, always select
Update Configuration near the bottom of the page.
For more information and definitions of fields, refer to Table 4-6 on page 4-13.
Figure 4-11 UVSL Networks Configuration
Table 4-6 Available Fields Under UVSL Networks Configuration
Label Definition
Add New UVSL Network To configure a UVSL network to work with XprezzNet, select
this button.
Notes:
• There are no network fields until you select Add new
UVSL Network.
• You can add multiple networks.
• To delete a network, select the Delete check box.
Network is enabled To enable or disable the specified network, select or deselect

the check box.
UVSL Network Number Enter the number of the UVSL network.
UVSL NodeID on this network Enter the UVSL Node ID. One Node ID for each network.
MAC Address of Network Adapter Use the Physical Address of the network interface card that
communicates with Spacelabs Healthcare monitors.
Figure 4-12 For the MAC address, enter the Physical Address
Time Master on this UVSL Network To make XprezzNet the Time Master on the UVSL network,
select this check box.
Monitor Devices with these NodeIDs These devices are included in the monitored group.
Note:
An asterisk (*) in the field represents all devices in the
category.
Table 4-6 Available Fields Under UVSL Networks Configuration (Continued)
Label Definition
Ignore Devices with these NodeIDs These devices are ignored from the monitored group.
Note:
An asterisk (*) in the field represents all devices in the
category.
Delete Select the check box next to a network to remove it and

its settings.
Settings to Control Health Status Monitoring

The limits entered in Settings to Control Health Status Monitoring depend on your
server setup. Violations of these limits are shown in the Health field under Status on
page 4-3 on the Administrative Interface home page. If necessary, adjust default
out-of-box settings based on your server.
Figure 4-13 Control the status of network health
Table 4-7 Available Fields Under Settings to Control Health Status Monitoring
Label Definition
Red Limit on Streamed Data Connections Stops streaming beyond the limit value entered.
Yellow Limit on Streamed Data Prevents streaming beyond the limit value entered.
Connections
Red Limit on Number of Devices Sets the limit on the number of monitored devices. Above
Monitored this limit, the system only responds to status requests.
Yellow Limit on Number of Devices Sets the limit on the number of monitored devices. Above
Monitored this limit, the system no longer accepts new device
connections.
Logging Configuration Settings

These settings control the internal logging records within XprezzNet.
Notes:
• Do not modify these fields!
• Only Spacelabs Healthcare Global Technical Support is authorized to modify or
request others to make modifications to the Logging Configuration Settings.
Figure 4-14 Example of Logging Configuration Settings
Note:
To save your configuration changes, make sure that you select Update Configuration
(refer to Figure 4-15).
Figure 4-15 Update Configuration button
Metrics
Developers are the main users of the Metrics information. Global Technical Support also
uses the Metrics service-level data to help with troubleshooting issues that occur in the
XprezzNet system.
It is not possible to edit Metrics settings from the XprezzNet Administrative Interface. The
fields on the Metrics page populate automatically. The information is polled from the
XprezzNet setup and is dependent on the API and client network infrastructure.
Press F5 to refresh the page. You can select Reset Counters to set the metrics back to
zero (0). Each metric category returns a metrics summary for that metric category.
The Metrics categories consist of the list that follows.
• Counters
• Timers
• Gauges
• Meters
Note:
TimeStamp refers to the ISO 8061 time format when the data was read from the
monitor. Used as the timestamp for non-episodic data.
Counters
The Counters section maintains a running count of API requests, performance counters,
and events, such as responses or errors.
Figure 4-16 Counters
Timers
Timers measure the duration of various internal operations within XprezzNet.
Figure 4-17 Timers
Gauges
Gauges go up and down over time. The unit column describes the subject of the
measurement. Many of these metrics are related to Windows operating systems and are
also available through the Windows Performance Monitor application.
The important values for users to check are CdiDevices-Cdi-Devices, which correspond to
devices on the network and CdiDevices-XNet-Devices, which correspond to values
on the home page (refer to Status on page 4-3).
Figure 4-18 Gauges, CdiDevices indicated
Meters
Meters are used only for error counts within the metric package that is used.
Figure 4-19 Metrics page, Meters
Logs
XprezzNet redacts electronic Protected Health Information (ePHI) in generated logs,
including any .ePHI log files. The logged data is also a way to trace connections and
disconnections in the XprezzNet setup. Spacelabs Healthcare Global Technical Support
accesses, reads, and interprets logged information. When requested, fetched logs merge
XprezzNet-related data into one single log output.
Note:
What you enter in the field Log purging will maintain Min Per Cent Free Disk Space
sets the minimum free storage space on the drive designated for log files. Spacelabs
recommends values between 20% and 50%. Once the limit is reached on that drive,
the system deletes excess XprezzNet log files to maintain the configured free space.
However, the purger cannot delete an active log file.
To download logs
1 From the Logs page, select a StartTime.
The Select a Date and Time popup shows.
Figure 4-20 Select a Date and Time popup
2 Select the button choices under Year, Month, Day of Month, Hour, Minute, and Second
to enter your StartTime and EndTime for the logs you want to fetch.
3 Select Fetch Logs.
Figure 4-21 Example of Logs window
The Archive Status window shows.
Figure 4-22 Logs, Archive Status
Log Bytes Remaining to Archive:1xxxxxxxx shows on the Logs page. A numeric

counter tallies and archives all logs within the specified start and end times.
4 When the Archive Ready page shows, select Begin Download.
Figure 4-23 Logs, Archive Ready, Begin Download
5 Select Begin Download.
6 Select Save to download the .zip file.

The .zip file contains .log files. Open the standard .log file with a standard text editor.
Open other logs, such as .troublelog and .codelog, with a Windows log file monitoring
tool. XprezzNet redacts electronic Protected Health Information (ePHI) in generated
logs, including any .ePHI log files.
Figure 4-24 Examples of downloaded logs files
Support
Version Info includes the product ID number and product version.
Contact Information includes Spacelabs Healthcare address and phone and email contact
information.
Figure 4-25 XprezzNet support information
Upgrade instructions
• Always establish a new server first before you install a

new XprezzNet upgrade.
• Spacelabs Healthcare recommends that you upgrade on a
server where XprezzNet is not already installed.
• Once the upgrade is complete on the new server,
decommission the older server.
If you need to uninstall an existing XprezzNet instance, do the steps that follow.
To uninstall XprezzNet 1.1

For XprezzNet 1.1, there are no entries under Add/Remove programs. It is a manual process
to uninstall XprezzNet 1.1.
1 To remove content from IIS, go to IIS Manager.
2 Start IIS Manager from the Run dialog box.
a From the Start menu, select All Programs > Accessories > Run.
b In the Open box, enter inetmgr, and select OK.
3 Stop IIS.
a From within IIS Manager, right-click the server name on the navigation tree and
select Stop.
4 Remove the SLNI website.
a On the navigation tree within IIS Manager, expand Sites.
b Expand Default Web Site.
c Right-click SLNIservice and select Remove.
5 Remove SLNI Application Pool.
a On the navigation tree within IIS Manager, select Application Pool.
b Right-click SLNIAppPool and select Remove.
6 Remove services.
a From the Start menu, select All Programs > Accessories > Run.
b In the Open box, type cmd and select OK.
c Once the command prompt window is open, enter the list of commands that follow:
sc stop SpacelabsAxeda [press return]
sc delete SpacelabsAxeda [press return]
sc stop SpaceLabsSLNILicensing [press return]
sc delete SpaceLabsSLNILicensing [press return]
7 Remove directories.
a Delete the directories that follow.
C:\SLNI
C:\SLNIservice
C:\SLNIAxeda
To upgrade XprezzNet from an earlier software version

Note:
Before you install XprezzNet, make sure to uninstall all instances of Microsoft Visual C++
Redistributable files—or C++Runtime—from the server.
1 Back up or copy the Web.config file to C:\SLNIService\Web.config.
2 Uninstall the previous version (refer to To uninstall XprezzNet 1.1 on page 4-21).
3 To deploy a new upgrade of XprezzNet, repeat the steps in Deployment on page 2-3.
4 To configure XprezzNet, use the backup Web.config file (refer to Step 1 on page 4-22
under To uninstall XprezzNet 1.1).

1 From the Windows Control Panel, open Programs and Features.
2 Select Uninstall a Program from the network and remove the applications that follow.
a XprezzNetInstaller
b Spacelabs XprezzNet Service
c XprezzNetAdminMsi
XPREZZNET (916 90)
Security
Overview of Security
XprezzNet runs under a single application domain as a .NET 4.5 application hosted
by IIS 7.5 or later, and all the platform security mechanisms apply. However, it is
recommended to have a running firewall with only the required ports open, according
to the application configuration.
• Customers who use XprezzNet are responsible for their own network
security settings. Such settings include firewalls, anti-virus
applications, and other related security, such as the encryption of
electronic Protected Health Information (PHI).
• The security of XprezzNet depends on the security of the network.
Spacelabs Healthcare is not responsible for any breaches of security
related to hospital system network configurations.
XPREZZNET (91690) SECURITY
Windows Firewall Configuration
• Make sure that the Windows firewall allows access to port 80 with
the TCP protocol.
• Make sure that the Windows firewall allows access to port 443 with
the SSL protocol.
To configure the Windows firewall and inbound ports

1 Select Start > Control Panel > System and Security.
2 Select Windows Firewall.
3 Select Advanced Settings on the left side of the window.
4 Select Inbound Rules.
5 Select New Rule in the Actions section.
6 Select the Port button and then select Next.
7 Select the TCP button.
8 Select the Specific local ports button.
9 In the field, enter 80 and then select Next.
Note:
For SSL installations, enter port 443.
10 Select the Allow the connection button and then select Next.
11 Select all check boxes (Domain, Private, Public) and then select Next.
12 In the Name field, enter Inbound TCP port 80.
13 Select Finish.
14 Repeat these steps to create a rule to allow connection on inbound UDP ports or for port
443 if SSL is used.
Note:
Open inbound ports to receive monitor network packets. The range of ports is specific
to the monitor network(s) that XprezzNet is set up to listen to.
To set up the outbound port

1 Select Outbound Rules.
2 Select New Rule in the Actions section.
3 Select the Port button and then select Next.
4 Select the TCP button.
5 Select the Specific local ports button.
6 In the field, enter 80 and then select Next.
7 Select the Allow the connection button and then select Next.
XPREZZNET (916 90) SECURITY
8 Select all check boxes (Domain, Private, Public) and then select Next.
9 In the Name field, enter Outbound TCP port 80
Note:
For SSL installations, enter port 443.
10 Select Finish.
Note:
Inbound ports should be open to receive monitor network packets. The range of ports is
specific to the monitor network(s) XprezzNet is set up to listen to.
The range of inbound port numbers for a given MonitorNetwork is calculated by using a
base constant of (51374…51376) + 256 * Network ID, where the Network ID is each of the
comma-separated values set in the XprezzNet settings called NetworkIDs.
Figure 5-1 Edit Application Setting
If the monitor network is 0, open inbound port range:

51374-51376.
If the monitor network is 1, the range of ports to open is:

(51374...51376) + 256 = 51630-51632.
Note:
If there are multiple monitor networks, then open an equivalent number of port ranges.
XPREZZNET (91690) SECURITY
96190 XPREZZNET SYSTEM ADMINISTRATION MANUAL
Troubleshooting
Check the Application Event logs first. These logs record problem
events and when and where they took place.
For example, the event log in Figure 6-1 shows that
EnabledDeviceNodeID.0 is missing.
I
Figure 6-1 Event Log
The solution is to change EnabledDeviceNodeIDs from 1 to 0 and

the value to * for this particular setup.
GTS can change these values through the Administrative Interface in
the Logging Configuration Settings section under the
Configurations tab. For more information, refer to Logging
Configuration Settings on page 4-15.
Spacelabs Healthcare recommends that only Spacelabs

Global Technical Support (GTS) edit settings under Logging
Configuration Settings.
96190 X PRE ZZNE T S YSTEM ADMINISTRATION MANUAL TROUBLESHOOTING
Problems and Solutions
Table 6-1 Problems and Solutions
Problem Solution
When XprezzNet is configured for 128 Check the default out-of-box settings for the device limit
devices, Server Critically Overload and update them to the correct number of devices for the
message shows in the XprezzNet network.
Administration window.
A delay in the refresh of the page after • Wait two to three minutes to allow the service time to
you select the Update or buttons. You process the request.
could see an error message popup or a • Select XprezzNet Administration and then select
configuration error in the logs. Restart Service.
Only the NodeID shows in the Devices list You can locate the bed name through the Devices section
on the home page for identification of the on the XprezzNet Adminstration home page. Select the
bedside monitor. How do you locate the blue link under Id and open the properties for the device.
bed name associated with the Node ID? However, the NodeID that corresponds to a bed name is
For an example, refer to Figure 6-2. not easy to find because it is not listed in the Name
column.
Contact your hospital biomed engineer or IT group. It is
possible that they maintain a record of Node IDs and their
corresponding bed names for your organization. They can
also check the target monitoring device directly to find the
Node ID of the device and then check the log record for
that device.
For more information, refer to Devices on page 4-5.
Node ID (corresponds to a unique bed name)

Network number
Device type
Figure 6-2 Devices
96190 X PREZZNE T SYSTEM ADMINISTRATION MANUAL TROUBLESHOOTING
Table 6-1 Problems and Solutions (Continued)
Problem Solution
Xhibit Telemetry Receiver devices • Keep a record of how many telemetry devices by serial
inadvertently drop off the DHCP server number are available or active on the network.
without any indication or alert that they
• Include an API request to poll the serial numbers of all
have done so. This drop-off is not
telemetry devices on the network.
distinguishable from a patient discharge
from the device. • Check the list of connected devices in the
Administrative Interface and compare those device
values against the records of telemetry devices on the
network.
• Periodically use the Restart Service button on the
home page.
After you add a new Ultraview SL monitor Reboot or restart the server. The Status > Health field of
and select Update Configuration, you get the network turns green and the new monitor shows in the
an error message and the Status, Health Administrative Interface.
field on the home page turns red. You get
a second error message when you select
Restart Service on the home page.
All or some monitors are not available • Check the application event log for event log errors on
from XprezzNet. How do I check if a the computer where XprezzNet is installed. The event
configuration issue exists? log lists specific issues with the configuration.
• If there are no errors in the event log, make sure that
the product configuration includes the expected
monitor network number.
• Make sure each network has a correct include list
(filter).
The number of configured monitors Reconfigure XprezzNet to include the desired monitors by
exceeds the number for which the monitor IDs within the license limitation. Go to the
XprezzNet instance is licensed. This makes application event log and check for errors from
XprezzNet include devices that first SLNIService that indicates the licensing issue.
respond on the network and ignore the
late-responders. This situation creates an
unpredictable monitor include list.
The monitor is not accessible from the Run Spacelabs Monitor Tester on the computer with the
computer where XprezzNet is installed. XprezzNet installation and make sure that you can
connect to the monitors and view data.
Note:
Spacelabs Monitor Tester is available as part of the
executable installation files.
Problem Solution
Some or all monitor data is not coming • XprezzNet is not compatible with all monitors. For
from Xprezznet, even though XprezzNet more information, refer to XprezzNet compatibility on
lists the device as active. page 1-4.
• To confirm that your monitors are supported, go to the
folder at %PROGRAMDATA%\Spacelabs\SLNI\Logs
and open the newest SLNIService-****.codelog file in
any text viewer or editor. Search for the keyword
NODE_REPORT-# to find all the supported and
unsupported monitors. Examine the results. For
example, NODE_REPORT-#01#0240 represents the
device on monitor network 1 and monitor ID 240.
• Check the list of monitors and software versions that
XprezzNet supports in the release documentation. If
the software version running on the monitor does not
exactly match the supported versions, then there is a
compatibility issue.
XprezzNet provides outdated • This outdated data is a potential performance issue.
numeric data. Check the CPU. In general, the load should not exceed
50%. If it is close to 100%, check whether the problem
is the IIS process. If the IIS process is taking most of the
CPU, it is likely that one or more of the items that
follow are to blame:
• XprezzNet gets more web calls than it can handle.
Limit the number of calls made to XprezzNet.
• Hardware where XprezzNet is running does not meet
the product requirements.
After the XprezzNet installation, Permissions are not always set to show performance
performance metrics do not show in the metrics. Set the permissions to show performance metrics
Administrative Interface Metrics page. with the command that follows.
net localgroup "Performance Monitor Users"
"IIS AppPool\XprezzNetAppPool" /ADD
The GaugeMetrics_AfterEnablePermissions.png file

shows after Performance Metrics is added to the server.
Large latency on the waveform data or • This could be a performance issue. Check the CPU. The
many missed waveform packets. load in general should not exceed 50%. If the load is
close to 100%, check whether it is the IIS process.
• Also, the application event log potentially contains
warning entries about the missed waveform packets.
Problem Solution
You get a list of devices, but not • Check that the include list matches the number of
consistently. licensed devices.
• Most likely this happens because XprezzNet is going to
sleep. That is the setting in IIS manager that you can
change from the default value of 20 minutes of
inactivity. Under the advanced settings of the
application pool XprezzNetAppPool, set the value for
Idle Time-out to 0. This stops XprezzNet from going to
sleep.
• Business logic in the application drives the application
settings. While the idle settings are part of the IIS
management, system administration manages the IIS
settings for the installed applications based on the
hardware utilization. That functionality is a feature of
IIS, not XprezzNet.
To change the settings:
• Go to IIS->ApplicationPool.
• Select XprezzNetAppPool.
• Select the Advanced Settings link on the right-hand
panel.
Setting the browser format preference Use the correct JSON plug-ins for browsers. For instance,
to JSON. POSTMAN for Chrome where the GET/POST request with
parameters and the format in the header string. However,
the browser and the plug-ins are outside of the scope of
XprezzNet support, as these are third-party applications.
How do I update XprezzNet from 1.1 to 1.2? For more information, refer to To upgrade XprezzNet from
an earlier software version on page 4-22.
If debugging is available, can it be Yes, but only by GTS personnel. This feature is available in
turned off? the Logging Configuration Settings. For more
information, refer to Logging Configuration Settings on
page 4-15.
Is it necessary to license XprezzNet again It is not necessary to license the system again as long as
when you upgrade? the XprezzNet installation has been updated through the
install wizard, and as long as the previous version was not
uninstalled and the new version installed.
Problem Solution
How do I uninstall and reinstall XprezzNet Your license is preserved by the Nalpeiron license
so that I can reuse the XprezzNet license? manager as long as your upgrade is on the same server
with your computer’s GUID.
On same server, you can uninstall 1.1 and install 1.2. The
license still shows as activated.
If you move to a different server, contact support so they
can deactivate on the older server and reactivate your
current license code on a new server.
Is there data storage or is it all pass There is no actual data storage. However, there are
through? temporary settings, and other information that gets stored
in the OS program data folder.
Note:
It is not recommended that this data be moved as it
requires OS system changes.
How much clinical/waveform data is XprezzNet is a real-time transport protocol, and therefore
stored on the XprezzNet server? does not store any significant amount of waveform data. It
caches a small amount of the waveform cached within the
transport pipes. Use ICS as the to store waveform and
numeric data for a prolonged period of time.
In troubleshooting data issues, how do I Check the event logs.

verify that an episodic or continuous value
was sent from XprezzNet from time X to All the values captured by XprezzNet are logged in the
as much as 30 to 60 minutes later? .codelog files. The log files are kept for the past five days.
The data can be searched in the file using a regular
expression (for example: #01#0123.*_Numer, where the
01 is the number of the UVSL network, and 0123 is the
monitor node ID). That query finds all the data captured
from the specified monitor.
How do I know if my EMR calls to the Modify the Web.Config file at

XprezzNet interface are received by C:\inetpub\wwwroot\XprezzNet\Web.config to enable
XprezzNet? tracing on the XprezzNet server.
For information on setting that up, visit
http://msdn.microsoft.com/en-us/library/ms733025
(v=vs.110).aspx. View this log file with the Microsoft utility
found at http://msdn.microsoft.com/en-us/library/
ms732023.aspx.
What are the limitations of XprezzNet in • No limitations with Daylight Saving Time.
terms of Daylight Saving, antivirus
XprezzNet timestamps are in Universal Time
software, maximum number of supported
Coordinated (UTC).
beds, memory, CPU, and disk
requirements? • Antivirus can potentially blocks ports.
• Maximum beds with waveforms: 64
• Maximum beds without waveforms: 128
Problem Solution
What Windows processes have to run to IIS needs and the Default Website need to be running, and
confirm that XprezzNet works, other than the XprezzNetAppPool needs to be active. The IIS process
pulling a list from the Devices file? For name is w3p.exe.
instance, if you want to stop something in
Task Manager related to XprezzNet, what
would it be?
How do I verify the locale in Microsoft The XprezzNet product has been tested with all software
Server 2008 R2? installed in English-only. The XprezzNet product does not
affect the local language used on the monitor, or the
receiving third-party product. XprezzNet passes all
monitor information from the monitor to the third-party
data system. However, XprezzNet is only configurable in
English. To install all Microsoft components (.NET 4.5,
Visual C++ 2010 Runtime) in English, do the steps that
follow.
1 At the Server, select the Start button.
2 Select Control Panel.
3 Select Clock > Language > Region.
4 Select Region and Language.
5 Select the Administrative tab.
6 Select the Change system locale button.
7 Select English (United States) from the
drop-down menu.
8 Select OK.
Do Virtual Machines actually need 300 GB Yes. XprezzNet stores log files for five days with all the
of free space for XprezzNet? traffic. With 128 beds, it can take 300 GB.
What happens if XprezzNet is installed on Normally, the time is synchronized within a domain.
a server with a Disjointed Domain? By disjoining the domain, XprezzNet is at risk of running
with a different clock than the clients connected to it.
How do I verify data integrity against the Use the Administrative Interface and cross-reference your
Electronic Medical Records (EMR) system. EMR system.
How do I verify connected devices? Check the number of devices shown in the Administrative
Interface.
Problem Solution
An error message shows An application An IT administrator can manage the application pool
pool exceeded time limits within the settings for XprezzNet. However, only a person who
Event Viewer. What is the process to understands the meaning for each setting should use
resolve this? these settings.
1 Select Start > Administrative Tools > Internet
Information Services (IIS) Manager.
2 In the Connections section, select the Application
Pools.
3 Select XprezzNetAppPool, and right-click to open a
context menu.
4 Select Advanced Settings in the context menu.
Listed here are some of the application pool settings that
could need attention.
• .NET Framework Version: v4.5—This setting cannot be
changed.
• Enable 32-bit Applications: True—This setting cannot
be changed.
• Identity: ApplicationPoolIdentity—This setting cannot
be changed.
• Idle Time-out (minutes): 20—You can change this
setting to stop XprezzNet from going to sleep, or to
change the number of minutes when the application
can go into sleep mode.
• Disable Overlapped Recycle: True—Spacelabs
Healthcare recommends that this is set to True.
• Regular Time Interval (minutes): You can change this
setting to stop XprezzNet from recycling, or to recycle
at a different interval.
Problem Solution
What if there is a problem with XprezzNet If problems continue with the XprezzNet installation,
installation? remove all XprezzNet components to uninstall XprezzNet
completely.
These instructions remove the XprezzNet software,
XprezzNet licensing service, and the IIS installation. These
instructions do not remove the items that follow.
• Microsoft Visual C++ 2010 Runtime
• Microsoft Web Deploy
• Microsoft .NET 4.5
• Spacelink Agent
Note:
For information to remove XprezzNet 1.1, refer to To
uninstall XprezzNet 1.1 on page 4-21.

1 From the Windows Control Panel, open Programs and
Features.
2 Select Uninstall a Program from the network and
remove the applications that follow.
a XprezzNetInstaller
b Spacelabs XprezzNet Service
c XprezzNetAdminMsi
XPREZZNET (916 90)
Appendix A — Symbols
The following list of international and safety symbols describes all

symbols used on Spacelabs Healthcare products. No one product
contains every symbol.
Note:
Graphic elements of certain keys and symbols may vary between
product lines.
HELP Key
?
HELP (Explain Prior Screen) Key
MONITOR SETUP Key
REMOTE Key
www.spacelabshealthcare.com A-1
XPREZZNET (91690) APPENDIX A — SYMBOLS
SYSTEM ADMINISTRATION
TRENDS Key
RECORD Key
Dynamic Network Access (DNA) Key
SPECIAL FUNCTIONS Key
NORMAL SCREEN Key
SAVE Key
No Network Connection
Network Connection
Do Not Connect to Network
No Connection to Intesys® Clinical Suite (ICS)
Compression
Magnifying Glass
File Cabinet
A-2 www.spacelabshealthcare.com
XPREZZNET (916 90) A PPENDIX A — SYMBOLS
List of Rooms
Printer
Service Message
PREVIOUS MENU Key
HOME Key
Arrows
On Direction
ON — Power Connection to Mains
ON — Part of the Instrument Only
ON Position for Push Button Power Switch
OFF — Power Disconnection from Mains
OFF Position for Push Button Power Switch
OFF — Part of the Instrument Only
Partial ON/OFF
ON/OFF
Standby
STANDBY Key
Power ON/OFF Key
Keyboard Connection
Mouse Connection
PAUSE or INTERRUPT
START/STOP Key
START/STOP
STOP or CANCEL Key
CONTINUE Key
ENTER Key
Delete
x
Nurse Alert Interface
ALARM SUSPEND/TONE RESET Key
ALARMS Key
Alarm, General
Alarm Reset
Alarm Audio ON
Alarm Audio OFF
Alarm Audio Paused
Low Priority Alarm
Medium Priority Alarm
High Priority Alarm
Alarms Paused
Alarm OFF or Equipment has no Alarm System
Parameter below measurement range

---
Parameter above measurement range
+++
Parameter measurement indeterminate
???
Indicator — Remote Control
PRINT REPORT Key
Normal Screen
Clock/Time Setting Key
Slow Run
Activate Recorder for Graphics
Reset
START (NIBP) Key
Power Indicator LED
Activate Telemetry Recorder
Output (Non-terminated)
Data Input/Output
Input
No Output (Terminated)
Indicator — Local Control
Indicator — Out of Paper
Recorder Paper
Menu Keys
Waveform/Parameter Keys
1
Return to Prior Menu
2
3 1
2
3
Monitor Setup
1
2
Select Program Options
3
Set Initial Conditions Menu

1
2 A
3
Access Special Function Menu

1
2 B
3
Return Unit to Monitor Mode

1
2
3
Keypad
Serial Port 1
1
Serial Port 2
2
Serial Port
Auto Mode (NIBP)
External Marker Push Button Connection
Arterial Pulse
Gas Exhaust
Video Output
Television; Video Display
Video Output, Primary
1
Video Output, Secondary
2
Enlarge, Zoom
Input/Output
PCMCIA Card
Touchscreen, External
Universal Serial Bus
SDLC Port
SDLC
Hard Drive
Antenna
Electrocardiograph or Defibrillator Synchronization
Microphone
Foot Switch
Audio Output, Speaker
Event
Gas Sampling Port
Gas Return Port
Battery
Replace only with the appropriate battery.
Battery Status
Battery
Low Battery

(+ / - signs may be reversed)
Battery off. Shipping and service mode.
Battery on. Regular operating mode.
Check battery switch on bottom of unit.
All batteries should be disposed of properly to protect the environment.

Lithium batteries should be fully discharged before disposal. Batteries such as
lead-acid (Pb) and nickel-cadmium (Ni-Cd) must be recycled. Please follow
your internal procedures and or local (provincial) laws regarding disposal or
recycling.
This symbol indicates that the waste of electrical and electronic equipment
must not be disposed as unsorted municipal waste and must be collected
separately. Please contact an authorized representative of the manufacturer
for information concerning the decommissioning of your equipment.
Caution - hazardous voltages. To reduce risk of electric shock, do not remove

the cover or back. Refer servicing to a qualified field service engineer (U.S.A.).
DANGER - High Voltage (International)
Protective Earth Ground
Replace Fuse Only as Marked
Power supply jack polarity.

(+ / - signs may be reversed)
Alternating Current
Both Direct and Alternating Current
Functional Earth Ground
Fuse
Equipotentiality Terminal
Direct Current
Input Power. Use only Spacelabs Power Supply (P/N 119-0527-xx).
AC/DC Input
Loop Filter
Audio Output, Speaker
IEC 60601-1 Type B equipment. The unit displaying this symbol contains an
adequate degree of protection against electric shock.
IEC 60601-1 Type BF equipment which is defibrillator-proof. The unit

displaying this symbol is an F-type isolated (floating) patient-applied part
which contains an adequate degree of protection against electric shock, and
is defibrillator-proof.
IEC 60601-1 Type BF equipment. The unit displaying this symbol is an F-type
isolated (floating) patient-applied part providing an adequate degree of
protection against electric shock.
IEC 60601-1 Type CF equipment. The unit displaying this symbol is an F-type
isolated (floating) patient-applied part providing a high degree of protection
against electric shock, and is defibrillator-proof.
IEC 60601-1 Type CF equipment. The unit displaying this symbol is an F-type
isolated (floating) patient-applied part providing a high degree of protection
against electric shock.
IEC 60601-1 Class II equipment, double-isolated. The unit displaying this

symbol does not require a grounded outlet.
Warning: Do not modify this equipment without authorization of the

manufacturer.
Operates on Non-Harmonized Radio Frequencies in Europe
!
Adult Noninvasive Blood Pressure (NIBP)
Fetal Monitor Connection (Analog)
Fetal Monitor Connection RS-232 (Digital)
Physiological Monitor Connection RS-232 (Digital)
Noninvasive Blood Pressure (NIBP), Neonate
Symbol Set, Adult/Pediatric Cuff Sizes
Symbol Set, Neonatal Cuff Sizes
NIBP Cuff, Neonatal 1
NIBP Cuff, Single Hose
NIBP Cuff, Dual Hose
NIBP Cuff, Surface Applied to Patient

THIS SIDE TO PATIENT
NIBP Cuff, Child Size (12 to 19 cm)

CHILD
NIBP Cuff, Child Size, Long (12 to 19 cm)

CHILD, LONG
NIBP Cuff, Small Adult Size, Long (17 to 25 cm)

SMALL ADULT, LONG
NIBP Cuff, Small Adult Size (17 to 25 cm)

SMALL ADULT
NIBP Cuff, Adult Size, Long (23 to 33 cm)

ADULT, LONG
NIBP Cuff, Large Adult Size, Long (31 to 40 cm)

LARGE ADULT, LONG
NIBP Cuff, Large Adult Size (31 to 40 cm)

LARGE ADULT
NIBP Cuff, Adult Size (23 to 33 cm)

ADULT
NIBP Cuff, Infant Size (8 to 13 cm)

INFANT
NIBP Cuff, Neonatal 1 Size (3 to 6 cm)

NEONATAL 1

NEONATAL 2

NEONATAL 3

NEONATAL 4

NEONATAL 5
NIBP Cuff, Thigh Size (38-50 cm)

THIGH
NIBP Cuff, Nylon Material

NYLON
NIBP Cuff, Soft Material

SOFT
NIBP Cuff, Vinyl Material

VINYL
Quantity
QTY
Place Artery Symbol and Arrow over Brachial or Femoral Artery

ARTERY
eIFU = electronic Instructions for Use (CD-ROM or website) is available
Consult Instructions For Use
Follow Instructions For Use
Warning About Potential Danger to Human Beings (Consult Accompanying

Documents)
Caution About Potential Danger to a Device (Consult Accompanying

Documents)
Note Note
Keep Dry
Indoor Use Only
Environmental Shipping/Storage Altitude Limitations

12,200 m
Environmental Shipping/Storage Temperature Limitations
Fragile
Handle with Care
This Way Up
Up Arrow
Down Arrow
Environmental Shipping/Storage Humidity Limitations
Humidity limitation
Atmospheric pressure limitation
Open Padlock
Closed Padlock
Happy Face
Sad Face
PVC-Free (Polyvinyl Chloride)
PVC
Do Not Reuse; Single Use Only

2
Reusable
Drip-Proof
IPX1
Unit can withstand accidental immersion in one meter of water for up to
IPX7 30 minutes
Reference Number or Order Number

REF
Use by date [YYYY-MM-DD]
Recycle
Non Sterile
NON
STERILE
Latex-Free
LATEX
LATEX
Date of Manufacture
Manufacturer
Radio transmitting device; elevated levels of non-ionizing radiation
A CE mark certifies that a product has met EU health, safety, and

environmental requirements, which ensure consumer safety.
XXXX is the European Notified Body number. 0123 is the number for TÜV SÜD
XXXX Product Service GmbH, München, Germany.
Canadian Standards Association Approved
Does not contain hazardous substances — Europe
Does not contain hazardous substances — China
Batch Code
LOT
Nellcor Oxisensor II Compatible

NE
2
Novametrix Compatible
NV
X
Spacelabs TruLink Compatible
Nellcor OxiMax Compatible
Spacelabs Compatible
UL recognized component in Canada and United States
Nellcor OxiMax Compatible
Masimo SET Compatible
ABBREVIATIONS USED AS SYMBOLS ARE SHOWN BELOW.
1 - 32 Access Codes 1 Through 32
AIR Air
A Amperes
ANT 1 Diversity Antenna System 1

ANT 2 Diversity Antenna System 2
Arr1 Arrhythmia Net 1

ArrNet2 Arrhythmia Net 2
avDO2 Arterial/Venous Oxygen Difference
CaO2 Arterial Oxygen
CH EEG, EMG, or ECG Channel

ch EEG Channels - CH1, CH2, CH3, CH4
EMG Channel - CH5
cmH2O Centimeters of Water
C.O. Cardiac Output

CO
CvO2 Venous Oxygen
CO2 Carbon Dioxide

CO2
DIA Diastolic
dia
ECG Electrocardiogram
ecg
EEG Electroencephalogram
eeg
EMG Electromyogram
emg
ESIS Electrosurgical Interference Suppression
EXT External
FECG Fetal Electrocardiogram
FHR1 Fetal Heart Rate, Channel 1

FHR2 Fetal Heart Rate, Channel 2
GND Ground
gnd
Hz Hertz
Hgb Hemoglobin
HLO High-Level Output

hlo
Multiview Multi-Lead Electrocardiogram
N2 O Nitrous Oxide
NIBP Noninvasive Blood Pressure

nibp
O2AV Oxygen Availability
O2 Oxygen
PaO2 Partial Pressure of Arterial Oxygen
PRESS Pressure
press
PRS
PvO2 Partial Pressure of Mixed Venous Oxygen
Ref. Oxygen reference gas port
RESP Respiration
resp
SDLC Synchronous Data Link Control
Serial number
SN
Model number
MDL
Option
OPT
SPO2 Arterial Oxygen Saturation as Measured by Pulse Oximetry
SpO2
SpO2
SaO2
SVO2 Mixed Venous Oxygen Saturation

SvO2
SvO2
SYS Systolic
sys
T1 Temperature 1
T2 Temperature 2
T3 Temperature 3
T4 Temperature 4
TEMP Temperature
temp
UA Uterine Activity or Umbilical Artery
UV Umbilical Venous
VAC Vacuum Connection
VO2 Oxygen Consumption
V Volts
W Watts

Spacelabs XPrezzNet

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Spacelabs XPrezzNet

Загружено:

Авторское право:

Доступные форматы

XprezzNet™

074-0211-01 Rev. A | www.spacelabshealthcare.com January 2016

©2016 Spacelabs Healthcare

• assembly operations, re-adjustments, modifications or repairs are carried out by persons

Spacelabs Healthcare, Inc.

Spacelabs Healthcare, Ltd.

Please refer to http://www.spacelabshealthcare.com/en/company/trademarks for a full listing of

XprezzNet™ (96190) is a network interface that exports Spacelabs Healthcare patient

About this manual

Conventions used in this manual

Warnings indicate potentially harmful conditions that

Cautions indicate conditions that could lead to damage to or

XprezzNet provides an Administrative Interface web application to set up and configure

Figure 1-1 XprezzNet exchange of data flow chart

Do not install XprezzNet and Intesys® Clinical Suite (ICS) G2 on the

Table 1-1 XprezzNet Compatibility

Product Software version

Ultraview™ SL (2200/2400/2600) 2.03.11, 2.03.13

Ultraview SL (2700/2800/2900) 2.03.11, 2.03.13

XPREZZON™/qube™ (91393/91390) 3.03.00, 3.04.xx, 3.05.xx

Command Module (90496) 1.02.28

Command Module (91496) 2.02.04, 2.03.05, 2.03.06, 2.04.xx, 2.05.xx

Capnography Module (91517) 1.00.11, 1.00.12

SvO2/ScvO2 (91424) 1.00.03, 1.00.05

Capno Pod (92516) 1.00.01

Capno Module (92517) 1.00.00

Table 1-1 XprezzNet Compatibility (Continued)

Product Software version

Multigas Module (91518) 1.00.16, 1.00.17

Multigas (92518) 1.00.01

BISx Module (91482) All

Xhibit™ Telemetry Receiver (96280) All

Flexport® System Interfaces

90422A-03 Sentec 2.00.02

90436A-15 Puritan Bennett 840 1.00.05, 1.00.06

91436B-A Maquet SERVO-i 1.00.01, 1.00.05

90442A-03 Edwards Vigilance II 2.00.02

90442A-03 Masimo Radical 2.00.02

91439B-A Edwards Vigileo 1.00.00

91443A-A ARKON All (numeric data only)

91443C-A Dräger Apollo/Primus/Primus IE/Perseus 1.00.01 (numeric data only)

XprezzNet intended use

When an earlier version of XprezzNet is already installed, do changes in

• As installation progresses, XprezzNet checks for the required

Do NOT modify any XprezzNet deployment components. Spacelabs

Figure 2-1 XprezzNetInstaller Setup window

Figure 2-2 Setup Successful

To verify the deployment of XprezzNet

Figure 2-3 Windows Security—log in to XprezzNet Administrative Interface

Figure 2-4 Verification of XprezzNet deployment

A failure to match the settings to within the actual network limitations

The XprezzNet limits for devices are as follows:

Figure 3-1 Before activation

Figure 3-2 Partially activated XprezzNet

3 Select Activate XprezzNet.

Figure 3-3 Activation succeeded

License Code number changes to

Product Activation field for

Figure 3-4 Already activated after refresh

Figure 3-5 Home page—number of devices active on the network

Figure 3-6 License is already used

XprezzNet Administration (home page)

To open the XprezzNet home page

Figure 4-2 XprezzNet Administrative Interface home page