ServiceManual SentrySuite

Service Manual
SentrySuite® Software
V-781239
Version 06.02
for SentrySuite® Software ≥ 2.21
Service Manual - SentrySuite Software
This manual has been composed with the assistance of Adobe® Creative Suite®
programs Adobe InDesign®, Adobe Photoshop®, Adobe Illustrator® and Adobe
Acrobat®. The complete pages have been produced with Adobe InDesign® CS4 for PC
and are also available as PDF files.
Adobe Acrobat Reader is required in order to open these PDF files.
Trademarks
Microsoft, Windows and Server are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
Dell, Optiplex and Latitude are either registered trademarks or trademarks of Dell
Computer Corporation in the United States and/or other countries.
Core is a trademark of Intel Corporation in the U.S. and/or other countries.
Adobe, Creative Suite, InDesign, Photoshop, Illustrator and Acrobat are registered
trademarks of Adobe Systems Incorporated in the USA and/or other countries.
Copyright
All rights, including those of translations, are reserved. Written permission of
CareFusion shall be obtained for the reproduction of this manual or any excerpt
thereof by any means which includes printing, photostatic duplication, microfilms or
any other processes.
Please contact:
CareFusion Germany 234 GmbH
Leibnizstrasse 7
97204 Hoechberg, Germany
Tel. +49 931 4972-0
Fax +49 931 4972-423
E-Mail: MarketingInfo.EU@carefusion.com
Note
This document contains copyright information. All rights are reserved. It is not allowed
to copy, duplicate or translate this manual in any other language without obtaining
written approval from CareFusion. CareFusion reserves the right to alter the infor-
mation included in this document without notice.
Names of persons mentioned in the context of this manual are fictitious - any resem-
blance to living or deceased persons is purely incidental and not intended.
Alterations and Revisions

In case of a new edition the manual is completely revised. Modification sheets, if
necessary, will be issued with additional information. The version number on the front
page will only change if a new edition is published. Minor corrections which do not
have any influence on the functionality of the product might be included in a reprint
without changing the version number.
For many product improvements it is not necessary to modify the manual. On the
other hand, corrections in the manual can be made without changing the product.
Therefore, the version number of the product often differs from the version number
of the manual.
Subject to technical modifications.

Copyright © 2017 by CareFusion Germany 234 GmbH, Hoechberg
Page 2/296 Version 06.02 • 2017-07-04

Table of Contents
Document Revision Table.......................................................................................... 8

General Information.................................................................................................. 8
General Safety Precautions........................................................................................ 9
Symbols for Notes on Safety in Instructions for Use and Service Manuals................... 10
Related Documents................................................................................................. 10
1. Installation.......................................................................................... 11
1.1 Installation Requirements.................................................................... 11
1.1.1 SeS Software Licensing....................................................................... 11
1.1.2 PC-Hardware and Operating System Requirements............................. 14
1.1.3 Directory Structure............................................................................. 15
1.1.4 Default User Names and Passwords.................................................... 16
1.1.5 Adobe® Acrobat® .............................................................................. 16
1.1.6 Office/Word....................................................................................... 16
1.1.7 Antivirus: Exclusion Files/Folders.......................................................... 16
1.1.8 Microsoft® Hotfixes............................................................................ 17
1.1.9 Firewall Settings for SeS version up to 2.11......................................... 19
1.1.10 Firewall Settings for SentrySuite 2.21.................................................. 20
1.1.11 Encryption.......................................................................................... 22
1.1.12 DNS Functions.................................................................................... 22
1.2 Installation Guides
22
1.2.1 Installation of EASI-PCIe Card and Driver............................................ 22
1.2.2 Preparing a SeS Network (Client and Server Preparation).................... 28
1.2.3 Installation Guide SentrySuite Software.............................................. 30
1.2.3.1 How to install the SentrySuite Software.............................................. 31
A) SentrySuite Standalone Installation................................................. 34
B) SentrySuite Client Installation......................................................... 38
C) SentrySuite Backend Installation..................................................... 43
1.2.3.2 Initial Configuration............................................................................ 47
1.2.3.3 Start SentrySuite................................................................................. 53
1.2.4 Installation Guides Sentry.NET............................................................ 55
1.2.4.1 Installation Guide Sentry.NET for Windows 7...................................... 55
1.2.4.2 Installation Guide Sentry.NET for Windows 2008................................ 60
1.2.4.3 Installation Guide Sentry.NET for Windows 2012................................ 66
1.2.4.4 Sentry.NET Quick Report Feature........................................................ 74
1.2.5 Installing Vmax - SentrySuite Hybrid System........................................ 76
1.2.6 Vmax Encore System to SentrySuite Connectivity ............................... 77
1.2.7 Interconnectivity with JLAB Systems.................................................... 90
1.2.8 Installation Guide SES Q Remote......................................................... 90
1.3 Restore- and Update Instructions........................................................ 90
1.3.1 How to create a SentrySuite Restore Point.......................................... 90
1.3.2 Creating a SentrySuite Restore Point for StandAlone SentrySuite System.
91
1.3.3 Creating a SentrySuite Restore Point for a SentrySuite Dedicated Server
System 92
Version 06.02 • 2017-07-04 Page 3/296

1.3.4 Creating a SentrySuite Restore Point for a Small System Server Installati-
on 92
1.3.5 Creating a SentrySuite Restore Point for a Client Installation............... 92
1.3.6 Restoring Data from a Restore Point................................................... 93
1.3.7 SentrySuite 2.19 update instructions................................................... 94
1.3.7.1 From SentrySuite 2.15........................................................................ 94
A) Standalone System 2.15................................................................. 94
B) Network 2.15................................................................................. 94
B) Network 2.13................................................................................. 96
B) Network 2.11................................................................................. 98
1.3.7.4 From SentrySuite ≤ 2.10..................................................................... 99
A) Special considerations.................................................................... 99
B) Update procedure for all systems ≤ 2.10......................................... 99
1.3.8 SentrySuite 2.21 Update Scenario's.................................................. 100
1.4 Database Imports to SentrySuite....................................................... 122
1.4.1 Vmax Onetime Batch Import to SentrySuite...................................... 122
1.4.2 Batch Import from JLAB to SentrySuite............................................. 124
1.4.3 Batch Import from Micro Medical to SentrySuite............................... 124
1.4.4 Batch Import from Nspire to SentrySuite........................................... 124
1.5 Repair, Reconfigure and Remove SentrySuite Software (RRR-mode).. 124
1.5.1 Repair SentrySuite Software.............................................................. 125
1.5.2 Reconfigure SentrySuite Software..................................................... 126
1.5.3 Remove SentrySuite Software........................................................... 127
1.6 Emergency Failover mode................................................................. 128
1.6.1 Set-up on a SentrySuite client........................................................... 128
1.6.2 Emergency Fail-Over mode in Action................................................ 133
1.6.2.1 Different Modes & Status screens..................................................... 133
1.6.2.2 Testing in Emergency Fail-Over mode............................................... 135
1.6.2.3 Use of Patient Data Management..................................................... 137
1.7 Support Tools ≥ V. 2.13.................................................................... 140
1.7.1 General notes on using this tool....................................................... 140
1.7.2 Functions.......................................................................................... 142
1.7.2.1 DB Tools........................................................................................... 142
1.7.2.2 Patient Data Management Tools....................................................... 143
2. Software.......................................................................................... 148
2.1 Software History............................................................................... 148
2.2 SentrySuite Desktop......................................................................... 148
2.2.1 SentrySuite Desktop Top Menu Items............................................... 148
2.2.1.1 Show System Information................................................................. 148
2.2.1.2 Show Service Information................................................................. 150
2.2.1.3 Service Settings................................................................................ 151
2.2.1.4 Language Import.............................................................................. 152
2.2.1.5 System Summary Import................................................................... 152
Page 4/296 Version 06.02 • 2017-07-04

2.2.1.6 Exit................................................................................................... 152

2.3 Patient Chart.................................................................................... 152
2.3.1 Patient.............................................................................................. 152
2.3.2 Demo Patient................................................................................... 152
2.3.3 Bio QC............................................................................................. 152
2.3.4 SentrySuite QM................................................................................ 152
2.4 User Administration.......................................................................... 152
2.4.1 Log File Viewer................................................................................. 152

2.4.2 User Administration.......................................................................... 152
2.5 Database Handling........................................................................... 153
2.5.1 Backup/Restore................................................................................. 153
2.5.2 Data Export/Import........................................................................... 160
2.5.3 Database Management.................................................................... 169
2.5.4 Patient Data Management................................................................ 169
2.5.5 Remove Server Configuration........................................................... 169
2.5.6 Server Configuration........................................................................ 169
2.5.7 Server Re-configuration.................................................................... 169
2.6 Configuration................................................................................... 169
2.6.1 GDT/HIS Settings.............................................................................. 169
2.6.2 GDTSelect Utility............................................................................... 172
2.6.3 Global Settings................................................................................. 174
2.6.4 System Configuration....................................................................... 174
2.6.4.1 Connectivity Settings........................................................................ 174
2.6.4.2 Global Settings................................................................................. 174
2.6.4.3 System Configuration....................................................................... 174
2.6.4.3.1Configuration of a Failover System................................................... 175
2.6.4.3.2Configuration of a Failover System................................................... 180
2.6.4.4 Turn On/Off Hardware Modules....................................................... 184
2.6.4.5 Change Serial Number of your Hardware Devices............................. 184
2.6.4.6 Change Port Number of Devices....................................................... 184
2.6.4.7 Test Hardware Devices...................................................................... 184
2.6.4.8 Peripheral Devices Information.......................................................... 184
2.6.4.8.1Overview of Available Drivers for Peripherals..................................... 185
2.6.4.8.2Ergometers....................................................................................... 188
A) ER 900, Viasprint 150 P, Viasprint 200 P...................................... 188
B) Demo Bike.................................................................................... 188
C) Technogym Excite Bike Med......................................................... 188
D) Lode Excalibur.............................................................................. 189
E) Lode xxx....................................................................................... 189
F) Cyclus 2........................................................................................ 189
G) Monark 939 E.............................................................................. 190
H) Monark 839 E.............................................................................. 191
2.6.4.8.3 Treadmills......................................................................................... 192
A) Demo treadmill............................................................................ 192
B) Technogym Excite Run Med.......................................................... 193
C) HP CosCom V2............................................................................ 194
Version 06.02 • 2017-07-04 Page 5/296

D) HP CosCom V3............................................................................ 194

E) Woodway..................................................................................... 196
2.6.4.8.4 Serial SpO2....................................................................................... 196
A) Nonin 7500.................................................................................. 196
B) Nonin 8600.................................................................................. 196
C) BCI 3304...................................................................................... 196
2.6.4.8.5 Blood Pressure.................................................................................. 197
A) Suntech Tango............................................................................. 197
B) Suntech Tango Plus...................................................................... 197
C) Suntech Tango M2....................................................................... 197
2.6.4.8.6 Blood Pressure.................................................................................. 199
A) Polar WearLink............................................................................. 199
2.6.4.8.7 How to setup the Bluetooth connections.......................................... 199
A) If the Bluetooth icon is not shown in the taskbar.......................... 199
B) Vyntus ECG.................................................................................. 200
C) Polar Wearlink.............................................................................. 203
2.7 Utilities............................................................................................. 207
2.7.1 Interconnectivity Manager................................................................ 207
2.7.2 Predicted Values............................................................................... 221
2.7.3 Questionnaire Designer.................................................................... 221
2.7.4 Report Designer................................................................................ 221
2.7.5 User Parameters............................................................................... 221
2.8 Calibration Tools.............................................................................. 222
2.8.1 CPET Service Calibration................................................................... 222
2.8.2 Gas Analyzer Calibration.................................................................. 222
2.8.3 Volume Calibration........................................................................... 222
2.9 Applications..................................................................................... 222
2.9.1 Spirometry........................................................................................ 222
2.9.1.1 Result Mode..................................................................................... 222
2.9.1.2 Measurement Mode......................................................................... 222
2.9.1.3 Edit Mode........................................................................................ 222
2.9.2 Bodyplethysmography...................................................................... 222
2.9.3 FRC Rebreathing............................................................................... 222
2.9.4 Diffusion SB CO/He.......................................................................... 222
2.9.5 Diffusion SB Intrabreath.................................................................... 222
2.9.6 Diffusion SB Realtime....................................................................... 222
2.9.7 Impulse Oscillometry......................................................................... 222
2.9.8 MIP / MEP......................................................................................... 222
2.9.9 P 0.1................................................................................................ 222
2.9.10 R Occlusion...................................................................................... 222
2.9.11 CPET................................................................................................ 223
2.9.11.1 Settings and 3rd party ECG configuration.......................................... 223
2.9.11.1.1 Layout.............................................................................................. 223
2.9.11.1.2 Ergometer........................................................................................ 224
2.9.11.1.3 ECG/Data Source Setup.................................................................... 225
A) General Notes.............................................................................. 225
B) General Overview and Information............................................... 226
Page 6/296 Version 06.02 • 2017-07-04

C) General Description of the Interface (same PC)............................. 227

D) General Description of the Interface (RS 232)............................... 230
E) General Description of the Interface (LAN).................................... 232
F) Vyntus ECG.................................................................................. 233
G) AmedTec ECGPro........................................................................ 234
H) GE-Cardiosoft (on the same PC)................................................... 241
I) GE-Cardiosoft (on a separate PC via RS 232).................................. 244
J) GE-Cardiosoft (on a separate PC via LAN)...................................... 247
K) Cardiolex...................................................................................... 249
L) Custo Diagnostic .......................................................................... 257
M) Norav ......................................................................................... 263
N) PBI .............................................................................................. 268
O) WelchAllyn - CardioPerfect.......................................................... 276
P) MedSet Padsy............................................................................... 280
Q) Mortara ...................................................................................... 285
R) 3rd Party ECG (General) ................................................................ 285
2.9.12 Bloodgas Data Transfer..................................................................... 286
2.9.13 Offline Data Input............................................................................. 286
2.9.14 Spirometer Data Transfer.................................................................. 286
2.9.15 Bronchial Challenge.......................................................................... 286
3. Troubleshooting............................................................................... 286
3.1 Error Diagnosis................................................................................. 286
3.1.1 SentrySuite Log Viewer..................................................................... 286
3.1.2 SentrySuite System Log Files............................................................. 288
3.1.3 Windows Event Viewer..................................................................... 288
3.2 Error Messages & Solutions............................................................... 289
3.3 Describe Functional Process Details................................................... 296
3.4 System Description .......................................................................... 296
3.5 Check Procedure for Modules (Service Tools & Utilities).................... 296
3.6 Disassembly of System and Replacement of Modules........................ 296
4. Contacts........................................................................................... 297
4.1 Important Email Addresses and Phone Numbers............................... 297
4.2 Product Improvements (Downloads of New Software /Firmware),
Web Links, Shops............................................................................. 298
4.3 PR Material (Poster, Flyer, CD’s), Training Material…......................... 298
Version 06.02 • 2017-07-04 Page 7/296

Document Revision Table
Date Revision Major Changes

February 2015 5.00 SentrySuite 2.13
June 2016 6.01 SentrySuite 2.19
June 2017 6.02 SentrySuite 2.21
NEW:
• 1.1.2 PC-hardware and
O.S. requirements
• 1.3.7 SentrySuite 2.19
Update instructions
• 1.3.8 SentrySuite 2.21
Update scenario’s.
General Information
This service manual is intended for CareFusion employees and for trained staff of
distributors only. Repairs and maintenance work must only be carried out by trained
and authorized technicians. In case of noncompliance, CareFusion does not assume
any liability for the device.
Before starting to work with the unit or carrying out any repairs, you should have read
the chapter "General Safety Precautions". In addition, refer to common safety
measures and local regulations prior to repairing and/or opening parts of this device.
Furthermore, you should be familiar with the Instructions for Use. This service manual
refers to the standard of the unit, as it was at the time this manual was compiled.
Subject to technical alterations.
FEDERAL U.S. LAW RESTRICTS THIS DEVICE TO SALE BY OR ON THE ORDER OF A

PHYSICIAN. (Rx only)
Page 8/296 Version 06.02 • 2017-07-04

General Safety Precautions
The service manual is regarded to be a part of the instrument, and should

always be kept on hand.
The service manual describes the present state of the device, including software and
accessories, with regard to the fundamental requirements of the MDD 2007/47/EC.
Exact adherence to the instructions issued is a prerequisite for perfect and intended
functioning of CareFusion instruments.
CareFusion only guarantees for the safety, reliability and function of the instrument if
- installation, extension, modifications, and repairs are exclusively carried out by
personnel authorized for these tasks by CareFusion.
- the room in which the equipment is operated complies with the installation
instruction.
- the unit can be plugged into a socket with protective conductor system.
- the ambient conditions at the installation location are suitable for the unit.
- the unit is used according to the training and instruction manual.
The instructions on hygiene are described in a separate manual (V-781332).
Version 06.02 • 2017-07-04 Page 9/296

Symbols for Notes on Safety in Instructions for Use and Service

Manuals
Following the ANSI recommendations (American National Standards Institute) for

safety notes, specific passages of the instruction manual are clearly marked as safety
notes.
Injury to Damage
Degree of Danger Use in case of:
Persons to Property
DANGER indicates an imminently hazardous situation

which, if not avoided, will result in death or serious injury.
X
This signal word is to be limited to the most extreme
situations.
WARNING indicates a potentially hazardous situation
X which, if not avoided, could result in death or serious injury.
CAUTION indicates a potentially hazardous situation

X (X) which, if not avoided, may result in minor or moderate
injury. It may also be used to alert against unsafe practices.
Additional icons shown in the instruction manual:
See instruction manual and documents delivered with the

X X
equipment.
Important and useful information. Information does not warn

of dangerous or harmful situations.
Hints for use.
Related Documents
This manual has references to other CareFusion documentation, including:
- 640412 07 00 SeS general system Product Requirement Specification.

- V-781300-029 Installation Instructions SentrySuite
Page 10/296 Version 06.02 • 2017-07-04

1. Installation
1.1 Installation Requirements
1.1.1 SeS Software Licensing
Hardware and software configuration
The Hardware and Software configuration provide a mechanism to set up the
workstation for using the right hardware and software options the user has
purchased. The complete configuration information is encrypted in a license code.
The string is translated into devices, hardware options and software options during
the setup and first time configuration process.
After the hardware is configured, the "System Configuration" program can handle
all hardware dependent processes like hardware checks. Also the configured software
options are validated by the "System Configuration" utility.
"System Configuration" utility

The "System Configuration" is the program to list and configure or check the
purchased hardware and initiate the One-Time-Validation process. It has a
configuration wizard implemented to help the user to step through the single steps of
setting up the device communication. Changes of the configuration can also be done,
for example entering a new configuration string.
License code
The license code has to be entered by the user during the first steps of the installation
process. It contains the following configuration information:
- device and hardware to be configured
- package information used by the installation process
- software options to be released for this system/serial number(s)
- a checksum code to ensure the correctness of the entered data.
The license code is encrypted and will be encoded. Following example of a valid
license code may illustrate the format: A01B -60182 -1000-C0G00-F0002-G08-1
Validation code
The validation code is a checksum calculated from the license code checksum and one
or more serial numbers as supplied by CareFusion devices. The following format is
used to encode the serial number:
SerialNumber-HardwareID-Checksum
The SerialNumber value is a valid serial number as supplied by CareFusion devices. The
HardwareID is the internal identification used to enumerate the hardware types and
the checksum is a check-code digit calculated from the preceding information. The
code is used to validate the system during the One-Time Software Validation process
(see below).
Example for a possible validation string:
Configuration string = 6SNMC-G600-XK70-E380Q-FW-G08-1
Hardware information with serial number = 764100-00001400-7
-> Validation string = 77B2FWQ935
Version 06.02 • 2017-07-04 Page 11/296

Windows required access-right:

Installation: local admin
Operation: std. windows-user
Example of a license & validation code sheet.
Page 12/296 Version 06.02 • 2017-07-04

Devices and hardware options

Each SentrySuite installation is attached to a device. A device can be a physical piece
of hardware which is used for measuring, but it can also be a simple workstation with
a hardlock (dongle).
Each device provides the system with a unique serial number.
Measurement devices with hardware options

During the configuration process the information about devices with hardware
options is retrieved from the configuration string and the information is entered in a
local configuration file which contains all information needed by the driver system to
communicate with the devices. The devices are stored in the database also and are
attached to the workstation. The list of hardware is shown in the
System Configuration utility.
Workstation with a hardlock (Dongle)

A simple workstation without measurement hardware is also shown as a device. These
workstations are configured to have a so called "Dongle" which is a hardlock device
which contains a serial number. This serial number is used in the same way as a serial
number from a measurement device.
Version 06.02 • 2017-07-04 Page 13/296

1.1.2 PC-Hardware and Operating System Requirements
SentrySuite® software V. 2.21 and higher

OS Windows® 10 Pro/Enterprise/Enterprise LTSB 64 bit
Windows® 7 Professional/Ultimate/Enterprise 64
bit SP1
Other patches None
Data platform Microsoft® SQL Server® 2014 Standard
For updates:
Microsoft® SQL Server® 2008 R2 Standard
For server/backend systems provided by customer:
Microsoft® SQL Server® 2016 Standard/Enterprise
Languages English, English (US), German, French, Italian,
Spanish, Portuguese, Danish, Swedish, Norwegian,
Finnish, Polish, Russian, Korean, Chinese
NET framework 3.5 for Microsoft® SQL Server® 4.5 for SentrySuite
and Sentry.NET
Instrument and workstation requirements
Computer Manufacturer Dell
Processor Minimum Dual CoreTM with 2.0 GHz or more
Recommended Quad CoreTM with 2.8 GHz and
more
RAM Minimum 4 GB Recommended 8GB or more
Hard drive Minimum 100 GB HDD, 20 GB free disc space
Recommended 320 GB or larger SSD
Other drive DVD-ROM, recommended DVD-RW
Network (if Minimum 100 Mbit/s TCP/IP
networking) Recommended 1000 Mbit/s
OS Windows® 10 Pro/Enterprise/Enterprise LTSB 64 bit
Windows® 7 Professional/Ultimate/Enterprise 64
bit SP1
Interfaces Vyntus® SPIRO/ 1 free USB
PNEUMO/ IOS/APS/
CPX/ECG
MasterScreen 1 free serial RS 232 or 1 free USB 2.0 1 free PS/2
Pneumo unheated or 1 free USB 2.0
MasterScreen 1 free serial RS 232 or 1 free USB 2.0
Pneumo heated
MasterScreen IOS 1 free serial RS 232 or 1 free USB 2.0
MasterScreen PFT/ 1 free PCIe interface
Body/ Diff
APS pro 1 free serial RS 232 or 1 free USB 2.0
Monitor Screen resolution Minimum 1280 x 900, wide or normal screen
Display 32 bit color
Power Computer/Monitor 100 to 240 V AC, 4.6 A
Page 14/296 Version 06.02 • 2017-07-04

Server/Sentry.NET Server/Backend System requirements

Computer Processor Minimum Dual CoreTM with 2.0 GHz or more
Recommended Quad CoreTM with 2.8 GHz and more
RAM < 100 000 patients: Minimum 8 GB
> 100 000 patients: Minimum 16 GB
Hard drive Performance based RAID level or SSD
< 100 000 patients: Minimum 360 GB free disc space
> 100 000 patients: Minimum native 100 GB free
disc space
+ 200 GB per 100 000 patients; incl. database
backups: minimum 360 GB free disc space + 600 GB
per 100 000 patients
Other drive DVD-ROM, recommended DVD-RW
Network Minimum 100 Mbit/s TCP/IP Recommended 1000
Mbit/s
OS Windows® Server 2016 SP1 or higher
and Windows® Server 2012 R2
and Windows® Server 2008 R2
Windows 10 Pro/Enterprise/Enterprise LTSB 64 bit
and Windows® 7 Professional/Ultimate/Enterprise 64
bit SP1
Power Server/Monitor 100 to 240 V AC, 4.6 A
Network hardware
Ethernet Speed Minimum 100 Mbit/s, recommended 1000 Mbit/s
Sentry.NET client systems
Browser Recommended: Internet Explorer 11 or higher
Minimum: Internet Explorer 8, 9, 10, Windows Edge
Technology Microsoft® SilverlightTM 5
1.1.3 Directory Structure

Registered exceptions for applications:
· SentrySuiteInstallFolder%\VASServiceData.exe
· SentrySuiteInstallFolder%\VASDesktop.exe
· Program Files\Microsoft® SQL Server®\MSSQL.[1-9]\ MSSQL\Binn\Sqlservr.exe
· C:\program files (x86)\CareFusion\SentrySuite
Version 06.02 • 2017-07-04 Page 15/296

1.1.4 Default User Names and Passwords
Application User Password

WinXP User 12345
SentrySuite PC's User 12345
Example for a Replication sentrysuite sentryuser
Agent user account
SeS Desktop, Service Service SESService
configuration
SeS Emergency Failover Technician emergency
SES user administration Administrator SESAdmin
The user names must not contain a space.
1.1.5 Adobe® Acrobat®

Disable auto-update function in Adobe Reader.
Windows 10:
CareFusion has changed it's policy in respect to Windows updates. This policy was
not ready at the moment of releasing this manual, please check with our international
hotlines and request for the latest update.
1.1.6 Office/Word
No information available.
1.1.7 Antivirus: Exclusion Files/Folders

Please exclude the following folders from real time scanning:
- SentrySuite installation folder
- Snapshot folder on server installs.
If possible, exclude SeS services from realtime scanning by A/V software.
Page 16/296 Version 06.02 • 2017-07-04

1.1.8 Microsoft® Hotfixes

CareFusion verifies and validates all software versions with Windows Updates by the
time of release of our software. Later issued Windows Updates are not verified and
validated.
Therefore, CareFusion recommends:
- Never dispatch Windows Updates automatically as it can interfere with current
conducted pulmonary function tests.
- Always test the Windows Update on one system first until you install it on all systems.
- Perform an image backup of the entire harddrive before rolling out the Windows
Update.
- Install the Windows Update on all other systems if the Windows Update works
without issue on one system.
Windows 10:
To delay update period for feature updates and to give enough time to validate
security updates it is important to set the following settings:
• Choose "Update settings" - "Advanced option"
- "Choose when updates are installed": Check “Current Branch for Business”
- "Feature update deferred by this many days”: 365
- “Quality update deferred for this many days”: 30
- Choose how updates are delivered:
- “Updates from more than one place" option should be switched off.
Version 06.02 • 2017-07-04 Page 17/296

• Choose "Update settings" - "Change active hours"
- Set your Start time and End time to maximum expected working time.
End time - Start time can currently be max. 18 hours.
- Proposal: Set Start time to 6:00am and End time to 21:00/9pm
- “Quality update deferred for this many days”: 30
- Windows can automatically be rebooted without notification if updates are
installed and the system is not within “Active hours” time period. This means
if your active hours timeframe is between 6:00(am) and 20:00/8:00pm than it
is possible that the system reboots at 20:01/8:01pm because of pending
updates - also during device operation.
Page 18/296 Version 06.02 • 2017-07-04

1.1.9 Firewall Settings for SeS version up to 2.11
Scenario Port
CIS DATA service 5310 (TCP)
SQL Server default instance running 1433 (TCP)
over TCP
SQL Server named instances in the Dynamically determined.
default configuration
SQL Server named instances when they The port number configured by the
are configured to use a fixed port administrator.
To configure a fixed port number for
SQL named instances see next pages.
Dedicated Admin Connection 1434 (TCP) for the default instance.
Other ports are used for named

instances. Check the error log for the
port number.
SQL Server Browser service 1434 (TCP)
Only when using Sentry.NET: SQL Server 80 (TCP), 443 (TCP)
instance running over an HTTP endpoint
SQL Server default instance running 443 (TCP)
over an HTTPS endpoint
Service Broker 4022 (TCP)
To verify the port, run that SQL-

Statement:
SELECT name, protocol_desc, port,

state_desc
FROM sys.tcp_endpoints
WHERE type_desc = 'SERVICE_BROKER'

Database Mirroring Administrator chosen port. To
determine the port, execute the
following query:
SELECT name, protocol_desc, port,

state_desc FROM sys.tcp_endpoints
WHERE type_desc = 'DATABASE_

MIRRORING'
Transact-SQL debugger 135 (TCP)
File and Print Sharing 137, 138, 139 (TCP), 445 (TCP) Win-
dows shares, SMB
Only for SentrySuite Version 2.5 Add an inbound firewall exception
for:"microsoft sql server \ms-
sql10_50.sentrysuite\msssql\binn\
SQLservr.exe"
Version 06.02 • 2017-07-04 Page 19/296

1.1.10 Firewall Settings for SentrySuite 2.21
List of assigned Ports for SentrySuite 2.21 Networks:
Port Protocol Program Name Purpose SeS SQL- SeS APP- SeS
Server Server Client
80 / TCP Sentry.Net / IIS CareFusion Web X
443 Application
1433 TCP Sqlservr.exe Default instance X
of SQL Server
1434 UDP Sqlbrowser.exe SQL Browser for X
named instances
5080 TCP MCservice.exe CareFusion X
Vmax
VmaxPremi-
umPackage
NetLinkListener
Webservice
5308 TCP CisDataService. SentrySuite X
WindowsSer- Failover Service
viceHost.exe
5309 TCP reserved for X
Sentry CIS
Data Service
via Reverse
Proxy
Page 20/296 Version 06.02 • 2017-07-04

5310 TCP CisDataService. CareFusion X

WIndowsSer- Data Service
viceHost.exe Interface for
SQL database
nssm.exe Unless Sentry
CIS Reverse
Proxy is
installed.
5311 TCP Vyntus Walk Mobile Data X
Vyntus Service
Questionnaire
5312 UDP Vyntus Walk Mobile Data X
USB tethering Service
broadcast
5320 TCP Sentry CIS Sentry CIS X
Business Business Object
Object Service Service
SentrySuite
Send Report
Webservice
5331 TCP SeSCalcula- CareFusion X
tionService. Sentry Suite
Server.Service. Calculation
exe Webservice
5332 TCP SeSReportSer- CareFusion X
vice.Server. Sentry Suite
Service.exe Report
Webservice
5333 TCP SeSAuthSer- CareFusion X
vice.Server. Sentry Suite
Service.exe Authentication
Webservice
5334 TCP SeSAuthSer- Administration- X
vice Admin Page for
Page AuthService
5335 TCP SentryCisData-
Distribution-
Service
Version 06.02 • 2017-07-04 Page 21/296

1.1.11 Encryption
CareFusion advises that if software-encryption is required, the negative performance

aspects of encryption are compensated by using more RAM and SSDs in 64bit
architecture PCs.
For more information on this topic, please contact CareFusion Technical Support (see
chapter 5 "Contacts").
1.1.12 DNS Functions
Make sure that name resolution (DNS) is running in the network.

- Verify if you can ping the SentrySuite server with his computer name from the
SentrySuite Client.
- Verify if you can ping the SentrySuite Client with his computer name from the
server.
1.2 Installation Guides
1.2.1 Installation of EASI-PCIe Card and Driver

MasterScreen PFT and MasterScreen Body/Diff requires an EASI interface card which
must be installed in the PC.
The delivered EASI-PCIe card is released for the personal computer DELLTM OptiplexTM
XE and 7010.
EASI-PCI Express Card

PN: V-708518
Page 22/296 Version 06.02 • 2017-07-04

1. Install EASI-PCIe Card (for example on the DELL™ Optiplex™ XE)
Switch off the PC and disconnect the power cable from the PC. Open the PC housing
and pull out the riser module.
Remove the slot covers on the insert and attach the EASI-PCIe card to the free PCIe
slot of the riser card.
Both cover slots are required for the EASI card.
After having the EASI-PCIe card inserted, please check its correct position in the
slot.
Version 06.02 • 2017-07-04 Page 23/296

Re-insert the riser module in the PC and close the PC.
2. Install EASI-PCIe Driver
Re-connect the PC power cable and switch on PC.
Installation KEASI
Insert the SentrySuite software DVD into the DVD drive.

Double-click the program Install.bat in the folder “KEASI“ to start the installation
procedure.
Procedure:
1. On the Windows® desktop, select the icon <Windows Explorer> and click on
“Computer“.
2. In the following window, select the DVD drive and open the folder “KEASI“.
Start the program “Install.bat“.
Follow the instructions as they appear on the screen. They will guide you through
the installation process.
Screen display:
Continue with <Run> .
Page 24/296 Version 06.02 • 2017-07-04

Screen display:
Continue with <Next>>.
Screen display:
Continue with <Install>.
Version 06.02 • 2017-07-04 Page 25/296

Screen display during the installation process:
Screen display when the installation process is complete:
Click on <Finish>.
Page 26/296 Version 06.02 • 2017-07-04

The following entry appears in the Device Manager after successful installation:
Version 06.02 • 2017-07-04 Page 27/296

1.2.2 Preparing a SeS Network (Client and Server Preparation)

Introduction
The following section contains the installation instructions for a SentrySuite network.
For instructions on installing a single, stand-alone SentrySuite device, please use the
Installation Instructions SentrySuite p/n V-781300-xxx.
Overview
Welcome to SentrySuite!
Installing a SentrySuite network requires a minimum of two computers – one machine
to act as a Server or be a Server computer and at least one machine to be a client
computer (measuring device). There is no limit on the number of client machines that
may be networked outside of licensing requirements. Please see the pre-installation
section for further definition.
Pre-installation
This document assumes knowledge of creating and/or adding computers to a
Workgroup or Domain network. The appropriate User rights and access to create and
modify files and folders are required.
Preparing the SentrySuite Computers

Location of the SentrySuite Server database can be located on a Server computer
(recommended) or a standard computer acting as a Server.
Check section 1.1 "Installation requirements" for the hardware specifications.
Either a Windows workgroup or domain network can be used. Most of the work
involved in setting up a machine for SentrySuite is done prior to installing the
SentrySuite software. The actual software installation is Wizard-based with relatively
simple and straight-forward instructions.
It is important to note that the SentrySuite Server system should be installed
first prior to installing the SentrySuite software on the Client computers.
The client systems (measuring device, workstations) need to be installed after the
SentrySuite Server database is in place.
Many of the pre-installation tasks are needed on both the Server computer and the
Client computers.
Page 28/296 Version 06.02 • 2017-07-04

Naming the computers and Workgroup

It is important that each computer on the network has a unique name. To change the
computer name, right-click the "My Computer" icon and select "Properties" from
the pop-up menu. In the system properties dialog box, select the "Computer Name"
tab. Then click on the "Change…" button.
Type a unique computer name and enter the existing network name. In the example
above, the computer name is "SeSClient" and the Workgroup network is "SES_
DEMO". All computers must have a unique name, but contain the same Workgroup
name.
Version 06.02 • 2017-07-04 Page 29/296

1.2.3 Installation Guide SentrySuite Software

Pre-installation warnings
Prior to installing the software, the measuring system has to be connected

to the PC or notebook. The measuring system must be switched on.
At a report or view station (without measuring system), the USB dongle
has to be connected to a free USB port.
Networking different versions of SentrySuite software is ONLY supported for

versions 2.19 and 2.21(and later).
NOTE: Sentrysuite 2.19 systems should have the latest HOTFIXES installed.
Please read the technote on the 2.21 DvD.
Certain prerequisites have to be fulfilled to ensure proper functioning of the

SentrySuite software. Accessory equipment connected to the analog and digital
interfaces must be certified according to the respective IEC standards (e.g. IEC
60950 for data processing equipment and IEC 60601-1 for medical electronic
equipment). Additional equipment connected to medical electrical equipment
must comply with the respective EN (IEC) or ISO standards (e.g. EN 60950 for
data processing equipment). Furthermore, all configurations shall comply with
the requirements for medical electrical systems ((section 16 of the 3rd ed. of
EN 60601-1). Anybody connecting additional equipment to medical electrical
equipment configures a medical system and is therefore responsible that the
system complies with the requirements for medical electrical systems. Attention
is drawn to the fact that local laws take priority over the above mentioned
requirements. If in doubt, consult your local representative or the CareFusion
Global Customer Support.
Please check the system requirements prior to installation.
To ensure software integrity, all automatic software updates (such as

Microsoft® Windows®) should be deactivated.
CareFusion has only validated the device with computers using certain features
and hence cannot guarantee that any computer with a Microsoft® Windows® 7
will work properly. For additional information please contact your local represent-
ative or the CareFusion Global Customer Support.
To install software, Windows® administrator rights are required.

The user name must not contain spaces. If the user name contains spaces,
do not change the user name but create a new user instead.
The sentrySuite installation folder need R/W access for all ses operators.
Page 30/296 Version 06.02 • 2017-07-04

1.2.3.1 How to install the SentrySuite Software
If an EASI-PCIe card is used which is integrated in the PC and required e.g. for
MasterScreen PFT, the card driver must be installed prior to the installation of the
SentrySuite software. See "Installation of EASI-PCIe Card" (chapter 1.2.1).
The SentrySuite installation process has 3 different types

• A Standalone system (no network)
• A SentrySuite client (that will need a connection to a SentrySuite Server)
• A Backend installation (which is usually the first step in a network
installation and installs the SentrySuite server)
The SentrySuite software is provided on a Installation DVD.

Insert the SentrySuite Software DVD into the DVD drive.
Start the installation process by double-clicking the Setup.exe program.
Procedure:
1. Select the “Windows Explorer“ icon on the Windows® desktop and click on
“Computer“.
2. Click the DVD drive in the respective window and start the“Setup.exe“ program.
To install the SentrySuite software, follow the instructions as they appear

on the screen. They will guide you through the installation process.
When updating from a previous version of SentrySuite:

please read paragraph 1.3.7.
Version 06.02 • 2017-07-04 Page 31/296

This generic section is the starting point for all installation types.
When this generic section has been completed, proceed with the appropriate section
A), B) or C) below to continue the installation.
If the USB-RS232 adapter is used (e.g. with the MasterScreen Pneumo, MasterScreen
IOS, APS SA), connect the adapter to a free USB port.
Windows® will automatically try to install the appropriate driver.
Insert the USB-RS232 adapter software CD and follow the on-screen instructions.
(The CD is included in the delivery package of the USB-RS232 adapter.)
If an EASI-PCIe card is used which is integrated in the PC and required e.g. for
MasterScreen PFT, the card driver must be installed prior to the installation of the
SentrySuite software. See Installation Instructions “MasterScreen“.
Page 32/296 Version 06.02 • 2017-07-04

The following screen will be displayed automatically:

In the following screen, the license code must be entered.
Please make the appropriate selection and proceed with the appropriate section A), B)
or C) below.
Version 06.02 • 2017-07-04 Page 33/296

A) SentrySuite Standalone Installation
Please complete section 1.2.3.1 "How to install SentrySuite software" first!
ONLY complete this section if you are installing a standalone system, i.e. you will
not network this system with any other SentrySuite system/server.
Sentry CIS Dataservice requires SQL integration services. This means that you may
see a SQL setup. This only installs the SQL integration services, the SQL server is
not installed!
When the SQL setup is finished, it will request a reboot of your PC. Please do
so, SentrySuite setup will automatically continue the installation. If the setup.exe
does not autostart, restart setup.exe manually from your installation media. The
software installation will continue where it left off.
A message appears indicating that the SentrySuite software will be installed in the
recommended destination folder
“C:\Program files (x86)\CareFusion\SentrySuite“.
For installation in a different folder, select <Browse...> and choose a different

destination.
Page 34/296 Version 06.02 • 2017-07-04

Click <Install> to install the previously selected settings.
Screen display during installation:
Version 06.02 • 2017-07-04 Page 35/296

Several windows will pop up during the installation process. It is not necessary for the
user to interact here.
Now, the computer needs to be restarted.

Please DO NOT CHANGE the settings.
Click <Finish> to shut down and restart the PC.
Page 36/296 Version 06.02 • 2017-07-04

After the restart, the Windows® desktop is shown.
Depending on the type of PC and the existing system configuration, it may

be necessary to restart the PC several times and, after that, to also restart the
SentrySuite installation procedure.
When the installation is complete, the following screen is displayed:
Click <Finish> to finish the installation process.
The initial configuration is automatically displayed.
Please continue with 1.2.3.2, "Initial Configuration".
Version 06.02 • 2017-07-04 Page 37/296

B) SentrySuite Client Installation
Please complete section 1.2.3.1 "How to install SentrySuite software" first!
ONLY complete this section if you have a SentrySuite network defined and you
want to add a new work- or measurement station to an existing SentrySuite
server in your network.
Sentry CIS Dataservice requires SQL integration services. This means that you may
see a SQL setup. This only installs the SQL integration services, SQL server is not
installed!
When SQL setup is finished it will request a reboot of your PC. Please do so,
SentrySuite setup should automatically continue with the installation. If the setup.
exe does not automatically restart, restart setup.exe manually from your installa-
tion media. The software installation will continue where it left off.
NOTE on re-installation:
When you're re-installing a SentrySuite client and you keep the same hostname,
SentrySuite will recover you original configuration!
Page 38/296 Version 06.02 • 2017-07-04

For Vmax-Hybrid systems ONLY:
Version 06.02 • 2017-07-04 Page 39/296

Settings for Calculation service:
Enter the host-address for the SentrySuite Server:

"http:/<Servername>;5310"
Please replace "Servername" with the hostname or IP-address of the SentrySuite

server in your network.
SentrySuite will now configure the Sentry CIS Data service in client-mode and connect
this to your SentrySuite server on port number 5310.
If no server host address is entered here, the software will error but continue with the
installation. Please run setup.exe again and select <repair>, then <reconfigure>, and
then enter a valid host address. For more information, see paragraph 1.2.3.
Please verify that any firewalls between this SentrySuite client and the SentrySuite
server are properly configured. For more information see paragraph 1.1.10 and
1.1.11, "Firewall Settings".
Page 40/296 Version 06.02 • 2017-07-04

If your SentrySuite server has enabled SentrySuite security, you may be asked to
enter login credentials as username and password to log in into your SentrySuite
server.
Click <Install>.
Version 06.02 • 2017-07-04 Page 41/296

Please continue with 1.2.3.2, "Initial Configuration".
Page 42/296 Version 06.02 • 2017-07-04

C) SentrySuite Backend Installation
Please complete the generic section 1.2.3.1 "How to install SentrySuite software"
first.
This is usually the first step in a network setup!
In case you need to install a SentrySuite server into a SQL cluster environment,
please contact CareFusion Technical Support for details and instructions.
Complete this section only if you plan to add a SentrySuite server, a Sentry.NET
server, the database or other single SentrySuite component to your network.
The SentrySuite backend installation includes the installation of Microsoft SQL

server 2008R2. When the SQL setup is finished, it will request a reboot of your PC.
Please do so, SentrySuite setup should automatically continue with the installation.
If the setup.exe does not restart automatically, restart setup.exe manually from
your installation media. The software installation will continue where it left off.
Click <Next>>.
Version 06.02 • 2017-07-04 Page 43/296

For a SentrySuite server, select:

• SQL server
• DataService Host
This option will only install
• MS SQL server 2008R2
• the SentrySuite instance and
• the Sentry CIS dataservice.
For a SentrySuite Small Server, a Multi-server or Sentry.NET server, select:

• SQL server
• DataService Host
• SentrySuite
Click <Next>>.
Page 44/296 Version 06.02 • 2017-07-04

Click <Next>>.
SentrySuite 2.13 server setup allows you to specify your 3 main storage locations on
your server.
CareFusion recommends to use separate disks for these 3 locations:
• Backup location
• SQL MDF file location (main DB)
• SQL transaction log file location
Version 06.02 • 2017-07-04 Page 45/296

For backup purposes, please inform your enduser's IT-department to move any
backup files that SentrySuite creates in the backup location to their own offline
storage media.
Verify server installation:

You can verify the successful installation of the SentrySuite server by checking the
services that should now be running in your SentrySuite server.
Please check if:
• Sentry CIS data service
• SQL server (SENTRYSUITE)
• SQL server agent (SENTRYSUITE)
have been installed and are running.
• If you planned to install a Dedicated SentrySuite server:

• This completes the SentrySuite Server installation.
• There’s no need to complete sections 1.2.3.2 "Initial Configuration" and
1.2.3.3 "Start SentrySuite".
• If you planned to install a SentrySuite Small server, a Sentry.NET server or a

SentrySuite Multi-server, please continue with 1.2.3.1, section B
"SentrySuite Client Installation".
Page 46/296 Version 06.02 • 2017-07-04

1.2.3.2 Initial Configuration
The initial configuration wizard will check the connected hardware modules.
If the initial configuration is omitted, the software validity will be limited to 90 days.
The following screen will be displayed:
Enter the required

validation code in the field
“Validation Code“ and
“Configuration String“.
The option "Force a system reconfiguration" should only be used if your initial in-
put of license- and validation string returns a validation error. If this happens, run the
configuration wizard again and activate this option.
Version 06.02 • 2017-07-04 Page 47/296

The “Configurations String” and “Validation Code“ is provided with your

system. Here, “License” equates “Configurations String” while “Validation”
equates “Validation Code”.
Please enter exactly as indicated.
Please note that the license code is case-sensitive.
Continue with <Next>.
Page 48/296 Version 06.02 • 2017-07-04

Now, the following features will be checked in a step-by-step process:

- Interfaces
- Serial numbers of the devices
- Corresponding hardware
Confirm every step by clicking <Next>.
In the following windows the system serial numbers are requested. There are at least
two different serial numbers which can be found in the delivered license/validation
code sheet.
- System serial number. In our example “90000056“
- Serial number of the device, e.g. MasterScreen Pneumo.
In our example “511123“.
A window appears for entering the system serial number:
Version 06.02 • 2017-07-04 Page 49/296

The system serial number can be found in the delivered documents.
Screen display after the serial number was entered:
Click <Next>.
Page 50/296 Version 06.02 • 2017-07-04

Once the window for entering the MasterScreen serial number appears, it should not
be necessary to enter this number. The software should read it automatically.
If the serial number is not displayed automatically, it has to be entered manually via
the keyboard.
Version 06.02 • 2017-07-04 Page 51/296

The following prompt is displayed:

“Device found and tested successfully!“
At the end of the initial configuration, a validation summary will be displayed.
Now, the initial configuration is complete and SentrySuite Desktop will be started
automatically if the system does not use a network database.
(See chapter 1.2.3.3 “Start SentrySuite“).
Page 52/296 Version 06.02 • 2017-07-04

1.2.3.3 Start SentrySuite
After the program has been started, a self-test is automatically performed

verifying that all hardware modules connected to the system are functioning
correctly.
The following appears on the screen:
The system now verifies that all hardware modules connected to the unit are
functioning correctly. For the MasterScreen Pneumo for example, the connection to
the digital handle (DH) is checked.
Time System MasterScreen System Vyntus

05 minutes MasterScreen Pneumo, Vyntus Spiro, Vyntus Pneumo,
MasterScreen IOS, APS Vyntus IOS, Vyntus APS
15 minutes MasterScreen Body, Vyntus CPX
MasterScreen Body/Diff,
MasterScope Body
45 minutes MasterScreen PFT,
MasterScreen Diffusion (RT),
MasterScreen Body/Diffusion (RT)
Version 06.02 • 2017-07-04 Page 53/296

The start screen/desktop will now be automatically displayed:
Page 54/296 Version 06.02 • 2017-07-04

1.2.4 Installation Guides Sentry.NET
Sentry.NET requires the Full SES server, unlimited seats.
1. The PC on which Sentry.NET will be installed cannot have underscores ( _ ) in

the hostname!!
2. Sentry.NET using SentryConnect Interface
If Sentry.NET is going to use SentryConnect Interface both services have to be
installed on the same computer system.
Please read the appropriate subparagraph!

1.2.6.1 Installation guide Sentry.NET for Windows 7
1.2.6.2 Installation guide Sentry.NET for Windows 2008
1.2.6.3 Installation guide Sentry.NET for Windows XP and 2003
1.2.6.4 Sentry.NET Quick Report Feature
1.2.4.1 Installation Guide Sentry.NET for Windows 7
Intended Use
The intended use of this section is to describe the installation of the Sentry.NET on
Windows 7. Sentry.NET is a web application that can be accessed from web browsers
over the network.
Network
Sentry.NET
server
Server side
On the server side the following installation steps are required:
1. Check that Internet Information Services (IIS) are installed.

Open "Programs and Features" by clicking the <Start> button,
clicking <Control Panel>, clicking <Programs>, and then clicking <Programs
and Features>.
Verify that Internet Information Services (IIS) is turned on (filled box). If IIS is not
installed, select it.
Version 06.02 • 2017-07-04 Page 55/296

Open "Internet Information Services" → "Web Management Tools" and check

the box "IIS Management Console".
Open "Internet Information Services" → "Word Wide Web Services" →

"Application Development Features" and check the box “ASP.NET”.
Page 56/296 Version 06.02 • 2017-07-04

Make sure "Internet Information Services" → "Common Http Features" →

"Static Content" is selected. Without this feature, the Sentry.NET Silverlight
application will not work.
Confirm with <OK>.

You will probably need your Windows 7 setup disk. Once IIS is installed, you can
browse to http://localhost to check that it is running.
2. Check that Microsoft.NET framework 3.5.1 is installed.

Open "Programs and Features" by clicking the <Start> button, clicking <Con-
trol Panel>, clicking <Programs>, and then clicking <Programs and Features>.
Verify that the item Microsoft.NET Framework 3.5.1 is turned on (filled box). If not,
select it and confirm with <OK>.
3. Check that ASP.NET is registered to IIS.

Open DOS command box as Administrator and type
• 32bit system:
"c:\Windows\Microsoft.Net\framework\v2.0.50727\aspnet_regiis.exe" –i
• 64bit system:
"c:\Windows\Microsoft.Net\framework64\v2.0.50727\aspnet_regiis.exe" –i
4. Check that the Windows Communication Foundation (WCF) service is registered

to IIS.
• 32bit system:
"c:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication
Foundation\servicemodelreg" -i
• 64bit system:
"c:\Windows\Microsoft.NET\Framework64\v3.0\Windows Communication
Version 06.02 • 2017-07-04 Page 57/296

5. If a firewall is turned on, check that incoming HTTP/HTTPS-traffic is enabled:

Go to <Control Panel> → <Windows Firewall> → <Advanced settings> →
<Inbound rules> → Enable "World Wide Web Services (HTTP Traffic-In)"
resp. "World Wide Web Services (HTTPS Traffic-In)"
6. Run SentrySuite installation.

Follow the instructions through the installation and configuration procedure.
7. Run Sentry.NET installation

Run the program "SentryNetInstall.exe". It can be found in the SentrySuite
program folder. You have to be logged on as Administrator.
Check the option “Install”.

Press button <Next>> to continue installation.
If installation is successful, all items contain a green icon. Press the button
<Next>>.
Page 58/296 Version 06.02 • 2017-07-04

Press the button <Finish>.
8. To activate all settings made previously, a restart may be required.
Client side
On the client side, the following installation steps are required:

1. Check that a state of the art web browser is installed.
2. Check that the Silverlight plugin is installed.
Open your web browser and open web page
http://www.microsoft.com/getsilverlight
3. Check that Adobe PDF Reader is installed and working.
Go to <Control Panel>, then <Add or Remove Program>. Check for entry
"Adobe Reader”. If entry does not exist, install Adobe Reader.
You can download it from the Adobe web site.
Please start Adobe Reader at least once and close it again.
Open Sentry.NET page
On the client side open your web browser and open page
http://<servername>/SentryNET/SentryNETPage.aspx
where <servername> is the computer name or IP address of your Sentry.NET server.
In the login form, enter your SentrySuite username and password:
Version 06.02 • 2017-07-04 Page 59/296

Intended Use
Windows Server 2008. Sentry.NET is a web application that can be accessed from web
browsers over the network.
Network
Sentry.NET
server
Server side
1. Run SentrySuite installation

2. Check that Internet Information Services (IIS) are installed.

Open "Server Manager" by clicking the <Start> button, clicking <Administra-
tive Tools>, and clicking <Server Manager>. Choose "Roles".
Verify that Internet Information Services (IIS) is in the list of installed roles.
Page 60/296 Version 06.02 • 2017-07-04

If "IIS" is not in the list of roles, use the "Add Roles Wizard" to install it by
clicking <Add Roles>, clicking <Server Roles> and checking the <Web Server
(IIS)> checkbox.
Select "Web Server (IIS)" → <Role Services> and check the "IIS Management
Console" checkbox in section "Management Tools".
Version 06.02 • 2017-07-04 Page 61/296

In section "Application Development", choose "ASP.NET".

A dialog appears, choose <Add Required Role Services>.
Make sure "ASP.NET", ".NET Extensibility", "ISAPI Extensions" and "ISAPI

Filters" are checked in section "Application Development".
Page 62/296 Version 06.02 • 2017-07-04

Make sure "Static Content" is selected in section "Common HTTP Features".

Without this feature, the Sentry.NET Silverlight application will not work.
Start the installation by clicking <Next>>, then clicking <Install>. You will
probably need your Windows Server 2008 setup disk. Once IIS is installed, you can
browse to "http://localhost" to check that it is running.
3. Check that Microsoft.NET framework 3.5.1 is installed.

Open "Server Manager" by clicking the <Start> button, clicking
<Administrative Tools>, clicking <Server Manager>. Choose Features.
Version 06.02 • 2017-07-04 Page 63/296

4. Check that ASP.NET is registered to IIS.

• 32bit system:
"c:\Windows\Microsoft.Net\framework\v2.0.50727\aspnet_regiis.exe" –i
• 64bit system:
"c:\Windows\Microsoft.Net\framework64\v2.0.50727\aspnet_regiis.exe" –i
5. Check that the Windows Communication Foundation (WCF) service is registered

to IIS.
• 32bit system:
"c:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication
• 64bit system:
"c:\Windows\Microsoft.NET\Framework64\v3.0\Windows Communication
6. If a firewall is activated, check that incoming HTTP/HTTPS-traffic is enabled:

Go to <Control Panel> → <Windows Firewall> → <Advanced settings> →
<Inbound rules> → Enable "World Wide Web Services (HTTP Traffic-In)"
resp. "World Wide Web Services (HTTPS Traffic-In)
7. Run Sentry.NET installation

program folder. You have to be logged on as Administrator.
Check the option “Install”.
Press button <Next>> to continue installation.
Page 64/296 Version 06.02 • 2017-07-04

If installation is successful, all items contain a green icon.

Press the button <Next>.
8. To activate all settings made previously, a restart may be required.
Client side

Open your web browser and open web page
Go to <Control Panel>, then <Add or Remove Program>. Check for the entry
"Adobe Reader”. If this entry does not exist, install Adobe Reader. You can
download it from the Adobe website.
Please start Adobe Reader at least once and close it again.
Version 06.02 • 2017-07-04 Page 65/296

On the client side, open your web browser and open the page
where <servername> is the computer name or IP address of your Sentry.NET server.
Intended Use
Windows Server 2012. Sentry.NET is a web application that can be accessed from web
browsers over the network.
Network
Sentry.NET
server
Page 66/296 Version 06.02 • 2017-07-04

Server side
1. Internet Information Services (IIS) are installed and configured correctly

Open "Server Manager", choose "Manage" -> "Add Roles and Features" in
the menu to start the "Add Roles and Features Wizard".
Choose "Installation Type" -> "Role-Based or feature-based installation"
Choose "Server Selection" and select the server to configure:
Version 06.02 • 2017-07-04 Page 67/296

Make sure IIS is in the list of installed roles.

If it isn't: Install it by clicking "Server Roles" and checking the "Web Server (IIS)"
checkbox.
Accept installation of the IIS Management Console by clicking <Add Features>.
Page 68/296 Version 06.02 • 2017-07-04

Choose "Web Server Role (IIS)" -> "Role Services":
Make sure "Management Tools" -> "IIS Management Console" is checked.
In section "Application Development", choose "ASP.NET 4.5".
Accept the recommendations with <Add Features>.
Version 06.02 • 2017-07-04 Page 69/296

Make sure that "ASP.NET 4.5", ".NET Extensibility 4.5", "ISAPI Extensions"
and "ISAPI Filters" are checked in section "Application development".
Make sure that "Static Content" is selected in the section "Common HTTP
Features".
Without this feature, the SentryNET Silverlight application will not work.
Page 70/296 Version 06.02 • 2017-07-04

2. Microsoft.NET framework 3.5 and 4.5 are installed and configured correctly:
Choose "Features"
- make sure that ".NET Framework 3.5 Features" -> ".NET Framework 3.5
(includes .NET 2.0 and 3.0)" is checked
- make sure that ".NET Framework 4.5 Features" -> ".NET Framework 4.5"
and "ASP.NET 4.5" are checked
Check ".NET Framework 4.5 Features" -> "WCF services" -> "HTTP
Activation".
Accept the recommendations with Add Features.
Version 06.02 • 2017-07-04 Page 71/296

3. Choose "Confirmation" and start the installation by clicking <Install>:

You will probably need your Windows Server 2012 setup disk.
Once IIS is installed, you can browse to http://localhost to check that it is running.
4. If a firewall is turned on, check that incoming HTTP/HTTPS-traffic is enabled: Go to

"Control Panel" -> "System and Security" -> "Windows Firewall" -> "Ad-
vanced settings" -> "Inbound rules" -> Enable "World Wide Web Services
(HTTP Traffic-In)" resp. "World Wide Web Services (HTTPS Traffic-In)"
5. Run SentrySuite installation.

6. Run Sentry.NET installation.

program folder.
You have to be logged on as Administrator.
Check the option "Install". Press button <Next>> to continue the installation.
Page 72/296 Version 06.02 • 2017-07-04

If the installation is successful, all items contain a green icon. Press the button
<Next>.
7. To activate all settings, a system reboot is recommended.

(At least a restart of IIS is required: open a command prompt as Administrator,
execute "iisreset").
Client Side

Open your web browser and open the web page

Go to the Control Panel, then add or remove the program. Check for the entry
"Adobe Reader". If the entry does not exist, install Adobe Reader. You can
download it from the Adobe web site. Please start Adobe Reader at least once and
close it again.
Version 06.02 • 2017-07-04 Page 73/296

On the client side, open your web browser and open the following web page:
<servername> is the computer name or IP address of your SentryNET server.
1.2.4.4 Sentry.NET Quick Report Feature
Overview
The Sentry.NET QuickReport feature allows creation and/or display of a report by
calling a single URL.
This can be used by external programs (e.g. hospital information systems) to provide
quick access to reports.
Using QuickReport
Calling Syntax
<protocol>://<hostname>/SentryNET/SentryNETService.svc/QuickReport?User=<
username>&Pwd=<password>&PatId=<externalPatientId>&Date=<visitDate>&Rep
ort=<reportTemplate>&Create=<creationFlag>&Show=<showFlag>
e.g.:
http://denb832/SentryNET/SentryNETService.svc/QuickReport?User=docto
r&Pwd=12345&PatId=CFNSPJO750209&Date=27042012&Report=SPIR_
FVC&Create=true&Show=true
Page 74/296 Version 06.02 • 2017-07-04

Parameters
Parameter Value Comment

<protocol> http or https Protocol used by Sentry.NET
<hostname> Hostname or IP-Address Server hosting Sentry.NET
<username> SeS username Login name of SeS user with
Sentry.NET access rights
<password> Password of SeS user Password of SeS user with
Sentry.NET access rights
<externalPatientId> External patient id
<visitDate> Date of visit Format: If there is more than one visit
ddMMyyyy e.g. for this patient and date, the
19022013 latest visit will be chosen
<reportTemplate> Report template e.g.
SPIR_FVC
<creationFlag> true or false true: create report (and
override existing report of
same type)
false: only retrieve existing
report
<showFlag> true or false true: redirect URL to report
view (or error) page
false: return JSON object: true
or false
QuickReport result
See <showFlag>
Security Considerations
1) A special user should be created to access QuickReport.
This user only should belong to its own user group with not more than the
following right:
Respiratory
Sentry.Net
Sentry NET Report Review
create data
This configuration makes sure the user isn’t able to access Sentry.NET’s web client
or other parts of SeS.
2) 3rd party and internal tools using QuickReport must not display generated URLs
(and SeS user credentials) to their users.
Version 06.02 • 2017-07-04 Page 75/296

1.2.5 Installing Vmax - SentrySuite Hybrid System
When installing a Vmax-SentrySuite hybrid system, please refer to manual

p/n 28450-001:
Installation and Setup Instructions
Vmax Vision software
Vmax/SeS software package.
Page 76/296 Version 06.02 • 2017-07-04

1.2.6 Vmax Encore System to SentrySuite Connectivity
When installing DBxConnect you need:

1 Vmax workstation adapter per Vmax Encore system. This adapts the Vmax user
interface to support the SeS connect features.
1 Vmax Database adapter per Vmax database! (example: if you have 3 Vmax
encore stations connected to 1 networked Vmax database, you will need to install
3 Workstation adapters, but on 1 station you will need to add the database
adapter.
In the entire network, you only need 1 DBxConnect service Host. This service acts
as a gateway-service from the Vmax environment to the SeS environment. All
Vmax systems will connect through the Host service to the SeS interconnectivity
manager.
Intended Use
The DBxConnect program is intended for converting Vmax® system data for use with
the SentrySuite system. The program also enables the transfer of patient demographic
data from the SentrySuite system to the Vmax system. In addition, nSpire, Medical
Graphics, and Micro Medical data can be imported into SentrySuite.
Product overview
The DBxConnect software is a series of applications that enable you to move Vmax
Encore data to the SentrySuite database and to move SentrySuite patient
demographic data to the Vmax Encore system while both systems are connected to a
common network.
Two installations are required; each from different CDs:

• Vmax Encore software version 21-2 or higher
• DBxConnect CD
HIPAA compliance
The DBxConnect program can access any Vmax Encore database, encrypted or
non-encrypted.
Using the Security Administration (VSA) program does not prevent this program from
operating.
Key points for HIPAA compliance:

• Access rights to the Vmax database, Vmax program, and DBxConnect program are
the responsibility of the customer.
• Access rights to the nSpire database, nSpire software, and DBxConnect software
are the responsibility of the customer.
• Access rights to the Medical Graphics database, Medical Graphics program, and
DBxConnect software are the responsibility of the customer.
• Access rights to the Micro Medical SPCS database, Micro Medical SPCS program,
and DBxConnect software are the responsibility of the customer.
Version 06.02 • 2017-07-04 Page 77/296

• Access rights to the SentrySuite database and the SentrySuite program are the
responsibility of the customer.
• At no point in the DBxConnect data integration program is patient measurement
data accessible or viewable.
• The mechanism (transfer file) used to export system data to SentrySuite
Connectivity is encrypted and deleted after the data transfer is completed.
Installing the DBxConnect database adapter and DBxConnect service host
All Vmax Encore databases require the DBxConnect Database Adapter. This adapter
prepares the Vmax data for transfer to Sentry Suite. Subsequently, nSpire, Medical
Graphics, and MicroMedical data transfer require use of the DBxConnect Database
Adapter. The DBxConnect Service Host gives SentrySuite a single communication
pathway to communicate with one or more DBxConnect Database Adapters.
For the data connectivity and transfer function to work, Vmax Encore systems
must be running Vmax Encore software version 21-2 or later. If this software is not
installed, follow the installation instructions provided on the Vmax Encore 21-2 CD.
You can install the DBxConnect Database Adapter and DBxConnect Service Host
on the same machine (any computer or server on the network). We recommend,
however, that you do not install the program on a Vmax measurement system.
The DBxConnect CD installs the components needed to perform Vmax Encore system
connectivity with SentrySuite. Each component can be selected for installation. This
CD contains four components:
• Vmax Workstation Adapter

• DBxConnect Database Adapter
• DBxConnect Service Host
• DBxConnect Data Import Scheduler
Insert the DBxConnect CD into the CD drive. If auto-run is enabled, the installation
wizard should start automatically. If auto-run is disabled, do the following:
1. Double-click the <My Computer> icon on the Windows® desktop.

The "My Computer" window opens.
2. Right-click the icon for the installation CD, and then click <Open>.
3. Double-click "Setup.exe".
The "DBxConnect Setup Wizard" window opens.
Page 78/296 Version 06.02 • 2017-07-04

4. Click <Next>> to continue.

The "Connectivity Installation Preferences" window opens.
5. Select the "DBxConnect Database Adapter" checkbox and the "DBxConnect

Service Host" checkbox, and then click <Next>>.
For connecting multiple Vmax databases, each Vmax database requires an
installation of the DBxConnect Database Adapter, each configured to the location
of its own Vmax database (see section “DBxConnect database adapter notes”).
There should be only one installation instance of the DBxConnect Service Host.
Version 06.02 • 2017-07-04 Page 79/296

6. DBxConnect always runs as a service. Usually, the services run as the LOCAL
SYSTEM account. If the services shall have access to the network (e.g. network
drive), checking "Create and configure a new service account" will run the
DBxConnect programs as user "DBxConnectUser". Please note that the user
"DBxConnectUser" must have appropriate Windows rights for accessing the
network resources.
7. Click <Next>> to confirm the installation.
Page 80/296 Version 06.02 • 2017-07-04

8. Click <Close> to finish the installation process.
DBxConnect Service Host notes
After completing the installation process, you can use the Service Monitor for
stopping and starting the DBx Service Host. There are three components that need to
know about the location of the DBx Service Host.
All Vmax systems

The Vmax.ini file found in the Windows® directory needs to be configured for the
location of the DBxConnect Service Host. This file needs to be set correctly if
SentrySuite patient demographics are to be recalled into the Vmax systems.
DBx database adapter

The DBx.DatabaseAdapter.exe file found in ProgramFiles/CareFusion/DBxConnect
folder needs to be configured (by using a text editor) for the location of the DBxCon-
nect Service Host.
SentrySuite Interconnectivity Manager (InterConMan)

On one SentrySuite system, the application SeSInterconMan must be configured
to the location of the DBxConnect Service Host. The application can be found and
started in the ProgramFiles/SentrySuite folder.
Note:
When you need to make changes to the Vmax connection ("Settings" tab) you need
to start the SeS interconnectivity manager as an administrator; right click it, select
"Run as an Administrator".
Version 06.02 • 2017-07-04 Page 81/296

Clicking the magnifier icon opens the Host Service log file.
DBxConnect database adapter notes
After completing the installation, you access the configuration for the DBxConnect
Database Adapter through the Service Monitor. Clicking the Database Adapter Con-
figuration icon opens the DBconfig file in Notepad. The location of the Vmax database
and the location of the Vmax application folder must be created. Stopping and start-
ing of the DBx Database Adapter should be performed when changes to the Database
Adapter configuration file are made.
Database adapter
start and stop
Database adapter
configuration
Page 82/296 Version 06.02 • 2017-07-04

Configuring DBCONFIG.XML
The standard file contains predefined headers for DatabaseConfiguration and

Databases. There is one DBCONFIG.XML for each Database Adapter application.
The Databases section lists all DataSources used by the database adapter.
<DatabaseConfiguration>
<Databases>
… *DataSources go here
</Databases>
</DatabaseConfiguration>
Vmax database
XML entry for a VMAX database:
<DataSource>
<Plugin>VmaxDbAdapter</Plugin>
<DatabasePath>C:\VIDATAS\</DatabasePath>
<ApplicationPath>C:\VISION\</ApplicationPath>
</DataSource>
Replace DatabasePath and ApplicationPath as appropriate for the location of your

database and Vmax application.
nSpire database
XML entry for an nSpire database:
<DataSource>
<Plugin>nSpireDbAdapter</Plugin>
<ConnectionString>Data Source=<COMPUTERNAME>;
Initial Catalog=PlusDB;Integrated Security=True</ConnectionString>
</DataSource>
Replace "<COMPUTERNAME>" in the ConnectionString with the location of the

nSpire database (SQL 2000 uses computer name as the data source). If the database
adapter is installed on the same machine as the SQL2000 server, or both components
are installed on computers on a domain, you can use Integrated Security.
SQL2000 server must be setup for remote connections.

See the section “Setting up the SQL2000 server”.
If the database adapter and the SQL2000 server are on separate computers and
both computers are not on a domain (they only share a workgroup), you cannot use
Integrated Security. In this case, the connection string must include a username and
password for the connection to the SQL server.
<ConnectionString>Data Source=<COMPUTERNAME>;
Initial Catalog=PlusDB;Integrated Security=False; User=”sa”;
Password=”PWD”</ConnectionString>
Version 06.02 • 2017-07-04 Page 83/296

Replace the username and password as appropriate for the SQL authenticaion of your
SQL2000 server.
Additional steps are required to configure the SQL2000 server for remote
connection and to allow Mixed Mode Authentication.
MGC database
XML entry for an MGC database:
<DataSource>
<Plugin>MgcDbAdapter</Plugin>
<ConnectionString>Data Source=<COMPUTERNAME>\<INSTANCENAME>; Initial
Catalog=MgcDBase;Integrated Security=True</ConnectionString>
</DataSource>
Example:
Replace <COMPUTERNAME> in the ConnectionString with the correct location of
<?xml version="1.0" encoding="utf-8" ?>
<DatabaseConfiguration>
<Databases>
<DataSource>
<Plugin>MgcDbAdapter</Plugin>
<ConnectionString>Data Source=DWDEU0712558PY\SENTRYSUITE;Initial
Catalog=MgcDBase;Integrated Security=True</ConnectionString>
</DataSource>
</Databases>
</DatabaseConfiguration>
the nSpire database (SQL 2000 uses computer name as the data source). If the data-
base adapter is installed on the same machine as the SQL2000 server, or both compo-
nents are installed on computers on a domain, you can use Integrated Security.
SQL2000 server must be setup for remote connections.

If the database adapter and the SQL2000 server are on separate computers, and
both computers are not on a domain (they only share a workgroup), you cannot use
Integrated Security. In this case, the connection string must include a username and
password for the connection to the SQL server.
<ConnectionString>Data Source=<COMPUTERNAME>\<INSTANCENAME>; Initial

Catalog= MgcDBase;Integrated Security=False; User=”sa”; Password=”PWD”</Connection
String>
Replace the username and password as appropriate for the SQL authentication of
your SQL2000 server.
Additional steps are required to configure the SQL2000 server for remote
connection and allow Mixed Mode Authentication.
Page 84/296 Version 06.02 • 2017-07-04

SPCS Database
XML entry for an SPCS database:
<DataSource>
<Plugin>SpcsDbAdapter</Plugin>
<DatabasePath>C:\SPCS\SpcsDatabase.rdb</DatabasePath>
</DataSource>
Replace DatabasePath with the location of your SPCS database file.
Setting up the SQL2000 server
The following steps are necessary for all connections.

To setup the SQL network connectivity for remote connection, use the SQL Server
2000 Server Network Utility to configure the instance of SQL Server 2000 to listen for
network connections.
To setup the SQL2000 server:
1. Run "Svrnetcn.exe" located in the SQL server Tools/Binn folder.
2. On the "General" tab, select the name of the instance of SQL Server in the
"Instance(s) on this computer" box. Click to select "servername" (computer
name) for the default instance, or select "servername/instancename" for any
named instance.
3. To allow the instance of SQL Server to permit remote connections, click <Named
Pipes> and click <Enable>. Click <TCP/IP> and click <Enable>. Both items
appear in the Enabled Protocols list.
4. Click <Apply> and <OK> to close the SQL Server Network Utility window.
The following steps are necessary only for SQL Authentication (not using Windows
authentication on a domain):
• To set the password for the username ‘sa’ to blank:

Open a command prompt and type in the following commands:
osql –E
sp_password @new = ‘’, @loginame = ‘sa’
go
exit
exit
• To allow mixed mode authentication:

Update the windows registry. Look for:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer
The LoginMode registry subkey must be set to 2. This setting allows you to do
Mixed Mode authentication – Windows® and SQL authentication.
Version 06.02 • 2017-07-04 Page 85/296

Installing the Vmax® Workstation Adapter
All Vmax Encore systems require a locally-installed Vmax Workstation Adapter. This
allows updating the User Interface for SentrySuite connectivity.
1. Select only the "Vmax Workstation Adapter" checkbox to install the adapter on
Vmax Encore systems.
2. Click <Next>>.
When the installation process is complete, the "Installation Complete" dialog
box opens.
3. Click <Close> to finish the procedure.
Page 86/296 Version 06.02 • 2017-07-04

4. Open the "Vmax.ini" file found in the Windows® folder.

This file must be configured with the address of the DBxConnect Service Host if the
host service is located on another machine. This setup is stored in the section:
[SESCONNECT]
SERVICEADDRESS=net.tcp://localhost:8000/DBxService
The INI file may also be setup with the computer name of the system running the
host rather than just the IP address. For example:
SERVICEADDRESS=net.tcp://REPORTCENTER1:8000/DBxService
Using the computer name is the preferred method of setting the service address in
an environment using DHCP (automatic assignment of IP addresses).
5. Replace localhost with the IP address of the system running the host. (You may
also need to change the port number if the port number was changed in the
"DBx.WindowsService.exe.Config.")
6. Select the Vmax "Ses Connect" software option.

Contact CareFusion Customer Care to enable this option.
Version 06.02 • 2017-07-04 Page 87/296

7. Start the Vmax application and select the Setup | Settings menu option.
The Vmax configuration window opens.
8. Select "Enable SesConnect" to enable SentrySuite connectivity.
9. Select "Retrieve Patient Demographics" to allow the Vmax software to retrieve

demographic data from SentrySuite.
10.Select "Export Test Results" to automatically export the current patient’s test
results to SentrySuite whenever a new patient is selected.
Configuring SentrySuite for the SeSConnect Host
The final step for installing the Vmax Encore system to SentrySuite Connectivity is
configuring the SentrySuite program.
From the SentrySuite system:
1. Use Windows® Explorer to locate the program "SesInterconMan.exe" and
double-click the icon.
The SentrySuite Connectivity Manager program resides in the installation directory
of the SentrySuite software. The default location is normally the directory
"C:\ProgramFiles\SentrySuite".
Note:
When you need to make changes to the "Settings" tab you need to start the
SeS interconnectivity manager as an administrator; right click the program file and
select "Run as Administrator".
Page 88/296 Version 06.02 • 2017-07-04

2. Click the "Settings" tab.
3. Select "Vmax" in the "Data Source" box.
4. Type the computer name of the SeSConnect Host in the "Database connectivity
host" box.
5. Select the "Enable mixed network" checkbox.
6. Click <Apply>.
The connectivity adapters (Vmax workstation adapter, Vmax database adapter,

and SeSConnect host) must all be installed and running before applying the
SentrySuite settings; otherwise, the connection will not be established. If
SentrySuite Connectivity Manager cannot make a connection, a timeout message
appears.
Version 06.02 • 2017-07-04 Page 89/296

1.2.7 Interconnectivity with JLAB Systems

Compatible with all JLAB 5.x DB’s; no need for JLAB, only the JLAB DB will suffice.
See also Online Manual "JLAB - SentrySuite Connectivity".
1.2.8 Installation Guide SES Q Remote
See also Online Manual "Desktop", paragraph "SeS Q Remote", "SeS Q Re-
mote Setup".
1.3 Restore- and Update Instructions
1.3.1 How to create a SentrySuite Restore Point
The general workflow is the following:

1) Save the necessary files from the old SentrySuite installation to a portable media
like an USB drive/stick.
2) Install the new SeS software and re-run the setup again. This will trigger the repair
mode (see paragraph 1.2.3).
3) Now, offer the files you created in step 1) above to the new installation of Sentry-
Suite. SentrySuite will then import all your settings & data into the new installation.
SeS 2.3
Update from 2.3
Installation 2.5
Windows 7 or higher with SeS 2.5
license code or higher
The following workflows provide information how this update can be done for the
different SentrySuite installations.
Page 90/296 Version 06.02 • 2017-07-04

1.3.2 Creating a SentrySuite Restore Point for StandAlone SentrySuite System
Please backup the following files from the system you want to make a Restore Point
for.
The service technician needs to backup the following files of the SentrySuite
installation version 2.3.
All backup files could be stored on an USB drive for instance.
Backup the SentrySuite 2.3 database and name it "DB_2_3.SeSBp". Store the file
also on a remote drive to bring everything to the new Windows 7 system.
File Source path (XP)

VasBase.ini SentrySuite
VasConnect.ini SentrySuite
Conf.cfg SentrySuite \DB
JGDT.ini SentrySuite
JHisConn.ini SentrySuite
VisitUploadConsumerService.dat SentrySuite
Database backup
DB_2_3.SeSBp Via backup procedure
JREPORT.JFI SentrySuite\DB
GDTselect.ini SentrySuite
Note: Is it essential to name the DB_2_x.SeSBp files, use the previous version here!
Example: if you are creating a restore point for a SentrySuite v.2.11, name this file
DB_2_11.SeSBp.
Using your SentrySuite Restore Point in a newer version of SentrySuite

Install the new version of SentrySuite.
Re-run "setup.exe" again to trigger the Repair-mode (see paragraph 1.2.4.1).
Version 06.02 • 2017-07-04 Page 91/296

1.3.3 Creating a SentrySuite Restore Point for a SentrySuite Dedicated Server System
Prerequisites
Backup of ini-files are not necessary for this update process. Only the database back-
up is necessary. Backup the SentrySuite 2.x server database and name it "DB_2_x.
SeSBp". Store the file on a remote drive to bring everything to the new operating
system.
All clients should be unsubscribed before the update process can be started
(see chapter "Client Installation").

Database backup
DB_2_x.SeSBp Via backup procedure
Server Setup SentrySuite 2.y

Call the SentrySuite setup of the version 2.y and select “User defined Setup”.
Select the feature “Update from 2.x” and specify the path where the backup
database can be found (remote drive, USB drive, etc.).
After installation, the clients can be installed and connected to the new server.
1.3.4 Creating a SentrySuite Restore Point for a Small System Server Installation
The workflow is the same as a standalone installation. The only difference is that all
clients should be unsubscribed from the existing small system server workstation
(see chapter "Client Installation").
1.3.5 Creating a SentrySuite Restore Point for a Client Installation
Prerequisites
The client should be unsubscribed from its server (DB server or small system server).
The service technician needs to backup the following files of the SentrySuite
installation version 2.x.
All backup files could be stored on an USB drive for instance. There are no special
actions necessary concerning backup of the database.

VasBase.ini SentrySuite
VasConnect.ini SentrySuite
Conf.cfg SentrySuite \DB
JGDT.ini SentrySuite
JHisConn.ini SentrySuite
Setup SentrySuite 2.x

Call the SentrySuite setup of the version 2.y and select “User defined Setup”.
Select the feature “Update from 2.x” and specify the path where the backup files
can be found (remote drive, USB drive, etc.).
Page 92/296 Version 06.02 • 2017-07-04

1.3.6 Restoring Data from a Restore Point
Procedure
- Do a clean-install of SentrySuite.
- Once SentrySuite is completely configured and has completed it's initial
configuration,
- run setup.exe again.
It is possible to call the setup even if the same version is already installed. The Setup
will find the exiting installation and offers 3 different modes:
- Program Change
- Program repair
- Program remove
Select the “repair” mode. Within repair mode, the user has the possibility to select
the “Update from earlier SentrySuite version” feature and select all backup files
and start the update process as described in paragraph 1.3, "Restore- and Update
Instructions".
Important: The repair mode with the feature “Update from earlier
SentrySuite version” will create a complete new 2.x database with the
information of the 2.3 database. All information which was in the 2.x database
before will be lost!
Version 06.02 • 2017-07-04 Page 93/296

1.3.7 SentrySuite 2.19 update instructions
1.3.7.1 From SentrySuite 2.15

A) Standalone System 2.15
• Backup SentrySuite
• Exit SentrySuite
• Insert SentrySuite 2.17 DVD
• Start setup.exe
• You are guided through the update/installation process
Depending on database size, update should last no longer than 10-45 minutes. If
database is large (lot of converted JLAB/VMAX data) and system is 32bit or has less
than 8GB of RAM, then a RAM upgrade is recommended.
B) Network 2.15
A SentrySuite network consists of

• Backend system (Server)
Most backend systems are standard backend systems which are directly installed
with the SentrySuite installation program with or without SentrySuite components.
Some larger, distributed networks are custom installed e.g. as a cluster system.
See update of a distributed backend system.
• Client systems (Workstations or measurement systems).
This includes Sentry.NET server if not directly installed on a backend system.
• Legacy (e.g. JLAB / VMAX ) systems connected to SentrySuite.
Update should be done in the following order:

1. Backup SentrySuite
2. Exit SentrySuite on backend system (if applicable) and on all client systems (i.e.
leave SentrySuite desktop or shut down the computer)
Do not perform any measurements on connected legacy systems!
3. Update of the backend system (Server)

a) Start the MS Management Studio and run the 2.11 & 2.13 to 2.15 clean up
scripts. See TB-20150903.
b) Update of standard server (non-clustered)
- Insert SentrySuite Setup DVD
- Start setup.exe
- You are guided through the update/installation process
(Please take care of backup message)
c) Update of a distributed backend system:
I) Update database server (SentrySuite instance on SQL cluster)
Get the most recent SQL-scripts from CareFusion Global Customer Support
department.
II) Update application server (SentryCIS client host)
• If System was installed with SentrySuite Installation WITHOUT manually
configured host service address:
- Start setup.exe.
Page 94/296 Version 06.02 • 2017-07-04

• If System was installed with SentrySuite WITH manually configured

host service address:
- Uninstall SentrySuite
- Install SentrySuite as backend (Option Host+SeS w/o db)
• If System has been installed manually:
- Select folder "CISDataService\Setup"
- Double-click on "CisDataService.Windowsinstaller.msi"
4. Update of each Client System

a) Insert SentrySuite Setup DVD
b) Start setup.exe
c) You are guided through the update/installation process.
Update should last no longer than 10 Minutes per Client.

• Perform a Backup of SentrySuite
• Start setup.exe
Version 06.02 • 2017-07-04 Page 95/296

B) Network 2.13

See update of a distributed Backend system.

3. Update of the Backend system (Server)

a) Update of standard Backend system (i.e. non-clustered)
- Insert SentrySuite 2.17 DVD
- Start setup.exe
(Please take care of backup message)
b) Update of a Distributed Backend system:
I) Update database server (SentrySuite instance on SQL cluster)
Get the most recent SQL-scripts from CareFusion Global Customer Support
department.
II) Update application server (SentryCIS client host)
• If System was installed with SentrySuite Installation WITHOUT manually
configured host service address:
- Start setup.exe.
• If System was installed with SentrySuite WITH manually configured
host service address:
- Uninstall SentrySuite
- Install SentrySuite as backend (Option Host+SeS w/o db)
• If System has been installed manually:
- Select folder "CISDataService\Setup"
- Double-click on "CisDataService.Windowsinstaller.msi"
a) Insert SentrySuite Setup DVD
b) Start setup.exe
c) You are guided through the update/installation process.
Update should last no longer than 10 Minutes per Client.
Page 96/296 Version 06.02 • 2017-07-04


• Perform a Backup of SentrySuite
• Start setup.exe
Only one manual process needs to be done:
After the start of the installation, the following user dialog appears:
The update should be based on the previous installation type. This can be a
standalone system, a client system or all other systems (like server or small system
server) etc. The default selection for this selection is done based on the previous
configuration.
Because SentrySuite 2.11 has no reliable marker for the installation type, this
default selection can be wrong. It is important that the selection is manually
changed to the desired configuration to a Standalone System.
To change the setup type afterwards is NOT possible in SentrySuite 2.15.
All other steps in the update process will be done automatically, including upgrade
of the database (from a SentrySuite based database to a Sentry-CIS based data-
base).
Version 06.02 • 2017-07-04 Page 97/296

B) Network 2.11

Updates to distributed backend systems are handled differently, please consult

with CareFusion Global Customer Service dept.


3. Unsubscribe all SentrySuite Clients from Server

a) This step may take quite some time. If this step is successful, continue with
step 3 or proceed to unsubscribe the next client until all clients have been
unsubscribed.
b) Perform this step ONLY if step 3a fails:
I) Note the client’s hostname.
II) On the SentrySuite server: manually remove local subscriptions for this
hostname on all 6 publications (see MS Management studio, replication,
local publications).
III) Try to unsubscribe again from the client (see step 3a).
This should now work immediately and be finished in few seconds.
4. Update of the backend system (Server, non clustered)
a) Insert SentrySuite 2.17 DVD
b) Start setup.exe
In best case, the Client systems are installed completely new, not updated.
This is possible because there is no important data stored locally at SentrySuite
Clients. First of all, the following 2 questions need to be negotiated to delete:
- Are there any special user data beside SentrySuite saved in the SentrySuite
database?
- Does the user access the local database and need it for any special purpose?
De-installation of SentrySuite:
Don’t delete your existing SentrySuite installation if
- there is any special user data beside SentrySuite saved in the local
SentrySuite database
- there is any special user data manually stored in the SentrySuite folders
To uninstall SentrySuite:
- Uninstall SentrySuite via Windows control panel -> "Programs and
Features"
Page 98/296 Version 06.02 • 2017-07-04

Delete existing SQL Server instance

Don’t delete the SQL Server if
- It is planned to create an Emergency failover system in SentrySuite
- The local SQL server is used for different, special purpose beside SentrySuite
- and the local SQL server caused no issues in the past
To delete the SQL server
- Uninstall SQL server via Windows control panel / Programs and Features
- Only remove “Microsoft SQL Server 2008 R2”.
Reinstall Sentry CIS Client
1.3.7.4 From SentrySuite ≤ 2.10
A) Special considerations
• SentrySuite 2.10 will store provocation observation modules/sequences in the

network environment so that these are available for all SentrySuite systems.
This means that any locally stored observation module/sequence you may have
created in SentrySuite 2.9 or earlier will be lost.
• An export of observation module/sequence from SentrySuite 2.9 or earlier and
an import into SentrySuite 2.10 will not work! Please print any observation
module/sequence you created in SentrySuite 2.9 or earlier and re-enter these
manually in SentrySuite 2.10 or higher.
• EASI board driver update:
If you are updating to SentrySuite 2.10 / 2.13 / 2.17 from any prior versions
(2.5 / 2.7 / 2.9):
First install the new EASI bd driver; see paragraph 1.2.1 on how to install the
EASI bd. and driver software. Make sure you use the SentrySuite DVD for the
driver installation.
B) Update procedure for all systems ≤ 2.10


3. If your SentrySuite version is 2.10 or earlier, run the pre-upgrade 211 utility
4. Now proceed with paragraph "Update from SentrySuite 2.11"
Version 06.02 • 2017-07-04 Page 99/296

1.3.8 SentrySuite 2.21 Update Scenario's
Table of Contents
Glossary.................................................................................................................. 101
Introduction............................................................................................................ 103
Scenarios................................................................................................................ 105
Mandatory checks:.................................................................................................. 105
Updates from previous SeS versions........................................................................ 106
Updates of Vmax-SeS Premium packages................................................................ 106
Legend of Scenario schematics............................................................................... 106
A - Standalone Systems........................................................................................... 108
A1 - Standalone Systems – New installation........................................................ 108
A2 - Standalone Systems – Update installation.................................................... 109
B - Networked Systems (SeS 2.21 only with no mixed network), SQL Server 2014
or core based licenses only.................................................................................. 110
B1 – Network 2.21 and SQL 2014 only - New installation.................................... 111
B2 – Network 2.21 and SQL 2014 only -
Updating complete system to SeS 2.21............................................................... 112
B3 – Network 2.21 and SQL 2014 only -
Adding additional devices with SeS 2.21............................................................. 115
B4 – Network 2.21 and SQL 2014 only –
Add Standalone system of 2.19 to existing network and update to SeS 2.21....... 116
B5 - Network 2.21 and SQL 2014 only –
Add Client system of version 2.19 to existing network and update to SeS 2.21... 116
C - Networked Systems (Mixed network 2.19), Mixed SQL Server versions............... 116
C1 - Add SeS 2.21 station to existing SeS 2.19 network without
SQL Server upgrade............................................................................................ 118
C2 - Add SeS 2-21 station to existing SeS 2.19 network with Server upgrade...... 120
Page 100/296 Version 06.02 • 2017-07-04

Glossary
Term Description
Base Version Last sold full feature version paid by the customer
Hotfix Package A Hotfix Package provides bug fixes and other updates for a
single SentrySuite version. Hotfix Packages are being applied to
an already installed SentrySuite version by a setup routine which
handles all tasks that are needed for the update.
Service Pack A Hotfix Package provides bug fixes and other updates for a
single SentrySuite version. Hotfix Packages are being applied to
an already installed SentrySuite version by a setup routine which
handles all tasks that are needed for the update.
Core based This is a short term for:
licenses / License Access from/to server is licensed by a core (or processor) based
is provided by SQL server license. This license is normally provided by the
customer customer but can also be provided by CareFusion (most times
part of clinical integration project). With this license type, no
separate client license are needed to access SQL server from
client stations. In most cases, backend systems with core based
licenses are installed and maintained by customer by using
component based and script based installation.
Instead of the term “Core base licenses” the term “License is
provided by customer” can be used.
Latest SeS version Latest released version of SeS. For this document this is SeS
2.21
Mixed Network It is possible to run a network of SeS with different versions
of SentrySuite on different stations. The minimum SeS version
supported is a SentrySuite 2.19 version. Older SeS versions
(2.17, 2.15, …) need to be updated to supported version to run
in a mixed network environment.
In a mixed network environment, the backend/server database
needs to be updated to the version of the newest system. In
addition the Sentry CIS Data Service Host needs to be updated
to the version of the newest system.
Running a mixed network can result in a restricted functionality
especially on older (e.g. 2.19) systems. Please check mixed
network documentation for a list of restrictions.
It is recommended to run a mixed network only for a
limited timeframe (e.g. during update process of complex
networks).
Newest system The system with the highest SeS version in the network. If there
are systems with SeS version 2.19 and 2.21 than the newest
system is any system with SeS version 2.21.
Sentry CIS Data SentrySuite has a client-server architecture including a middle
Service ware solution for data access. This middle ware is a web service
named the “Sentry CIS Data Service”. The Sentry CIS data
Service runs in a host mode on backend servers and in a client
mode on SentrySuite systems. Standalone systems run in a
combined client/host mode.
The Sentry CIS data service includes a build in compatibility
between different versions. The host service and the backend
database structure needs to be at the newest system version,
clients can have lower version of the Sentry CIS Data Service In
a mixed network environment.
SeS SentrySuite
Version 06.02 • 2017-07-04 Page 101/296

Term Description
SeS versions / Latest SeS version: SeS 2.21
Update versions Legacy versions:
summary
- Versions below latest SeS version
2.19, 2.17, 2.15, …, 2.5
SeS direct update versions
- Direct SeS Updates (via installation program) are possible
from version:
(2.21), 2.19, 2.17, 2.15, 2.13
DB update versions
- Database updates via backup / restore are possible from the
following versions
(2.21, )2.19, 2.17, 2.15, 2.13
Indirect update versions
- Versions 2.11 and older (2.11, 2.10, 2.9, 2.7, 2.5) can not
be updated directly. Instead of this, an update to version
2.19 needs to be done at first according to Service manuals.
The update from 2.19 to current version is afterwards done
as described below.
Mixed network versions
- The following versions can run in a mixed network
environment:
2.19, 2.21
SQL Server Standard SQL Server version:
version - SQL Server 2014 SP1 (or later Service Pack)
Legacy SQL Server version:
- SQL Server 2008R2 and all other versions earlier than
Standard SQL Server version
Supported SQL Server version:
- These versions are (at least in some scenarios) supported by
SentrySuite installation:
SQL Server 2008R2, SQL Server 2012 SP2, SQL Server 2014
SP1, SQL Server 2016
Page 102/296 Version 06.02 • 2017-07-04

Introduction
According to “Hardware and Software requirements” documentation provided by

Microsoft each SQL Server version is compatible with various Microsoft Windows ver-
sions as operating system as well for client systems and for server systems. In general,
only a limited number of SQL server versions can be installed on newest Windows ver-
sions and newest SQL server versions cannot be installed on legacy Windows versions.
According to the documentation provided, Microsoft SQL Server 2008 R2 (which is
delivered with SentrySuite 2.19 and lower) is no longer supported with Windows 10.
On the other hand, SQL Server 2016 (this is the newest Microsoft SQL server) does not
support Windows 7 any longer.
Because SeS 2.21 should be compatible to Windows 10 and to Server 2016 licensing
of SentrySuite together with Microsoft SQL server needs to be changed.
The following table shows the compatibility of different Windows versions and SQL
server versions.
SQL Server SQL Server SQL Server SQL Server

2008 R2 2012 SP2 2014 SP1 2016 (64bit
SP2 only)
Windows 7, 32 bit X X X --
Windows 7, 64 bit X X X --
Windows 8 X X X X
Windows 8.1 X X X X
Windows 10
Windows Server 2003 X -- -- --

Windows Server 2003 R2 X -- -- --
Windows Server 2008 X X X --
Windows Server 2008 R2 X X X --
Windows Server 2012 X X X X
Windows Server 2012 R2 X X X X
Windows Server 2016 -- X X X
The main restrictions are:
- SQL Server 2008 R2 is not compatible to Windows 10 and to Windows Server
2016
- SQL Server 2016 is not compatible to Windows 7
Additional information:
- Starting with Windows server 2008 R2 Server operating systems are 64 bit only.
- SQL Server 2016 is no longer available as 32 bit version
Therefore, SQL Server 2014 SP2 64 bit is defined as standard solution for SentrySuite
installation. Licenses will provided only to SQL Server 2014 SP2.
Version 06.02 • 2017-07-04 Page 103/296

To fulfill Microsoft’s Hardware and Software requirements and to limit number of

possible combinations in the field the following operating systems are supported with
SentrySuite 2.21.
For systems with SQL server based

on core license model provided by
customer
Windows Version For updated Default
systems license
only1 delivered
with
SentrySuite
SQL Server SQL Server SQL Server SQL Server
2008 R2 2012 SP2 2014 SP22 2016 SP1
SP21
Windows 7 64 bit X X X --
Professional / Enterprise /
Ultimate
Windows 10 64 bit -- X X X
Pro / Enterprise / Enterprise
LTSB
Windows Server 2008 R2 X X X --

Windows Server 2012 R2 X X X X
Windows Server 2016 -- X X X
1
licensing needs to be checked in mixed network environment. Mixed networks are recommended only for
a limited timeframe.
2
for new installation only
There is no upgrade path for Embedded SQL licenses provided by Microsoft (from SQL
Server 2008 R2 to SQL Server 2014/2016).
Page 104/296 Version 06.02 • 2017-07-04

Scenarios
The following chapters show some common scenarios for system installation. These
use cases describe what checks are done by the installation program and whether ad-
ditional actions like upgrades are needed. Even though this is a very detailed list, not
all possible scenarios can be listed in this document.
Each scenario includes one or more setup/use cases and a schematic showing the
principle system structure on a very rough level. Details, system structure and espe-
cially the number of attached systems can be different in “real life”.
Table of scenarios:
A) Standalone Systems
A1) New installation
A2) Update installation
B) Networked Systems (SeS 2.21 only with no mixed network), SQL Server 2014 or
core based licenses only
B1) New installation
B2) Updating complete system to SeS 2.21
B3) Adding additional devices with SeS 2.21
B4) Add Standalone system of 2.19 to existing network and update to SeS 2.21
B5) Add Client system of version 2.19 to existing network and update to SeS 2.21
C) Networked Systems (Mixed network 2.19), Mixed SQL Server versions
C1) Add SeS 2.21 station to existing SeS 2.19 network without SQL Server up-
grade
C2) Add SeS 2-21 station to existing SeS 2.19 network with Server upgrade
Mandatory Checks
For all scenarios, the following checks need to be done during order processing and
again when system installation is planned to be prepared and to decide what alterna-
tive works for you.
1) Check whether operating system for all systems are supported by new ver-
sion
Please notice especially that 32 bit operating systems are no longer supported
Please notice that SQL Server 2008 R2 is not compatible with Windows 10
Please check also backend/server systems
2) Minimum/Recommended hardware requirements are fulfilled, see Para-
graph 1.1.2 SentrySuite Hardware and O.S. requirements.
Updates from previous SeS versions

All update scenarios below are only related to “SeS direct update versions” (2.19, …,
2.13) as described in glossary. If you need to update versions described in “Indirect
update versions” (2.11 and lower) than a two-step update needs to be done. The
database needs to be updated at first to version 2.19 according to Service manuals.
The update from 2.19 to current version is afterwards done as described below. This
update in two steps is needed, because these versions are based on Microsoft SQL
Server replication mechanisms that are also used during conversion process. The last
SentrySuite version that supports this technology is SeS version 2.19.
Version 06.02 • 2017-07-04 Page 105/296

Updates of Vmax-SeS Premium packages

In general, the scenarios below are also valid for Premium packages, because changes
are related to SentrySuite and SQL Server only. Before installation please check that
operating system is released for Vmax and SeS e.g. Windows 10 installation is only
possible if supported by both systems.
- Open questions: Default configuration
- Do we need additional use cases?
Legend of Scenario schematics
Installed Microsoft SQL Server Instance
MS SQL Server 2014 Server instance
MS SQL Server 2008 R2 Server instance

MS SQL Server 2012 / 2014 / 2016 installation
provided by customer
License for SQL Server
SQL Server MS SQL Server 2014 embedded

license. Delivered with SentrySuite
2.21 or newer key or sold separately
2014
SQL Server
MS SQL Server 2008R2 embedded
license. Delivered with SentrySuite
2008 R2 2.19 or older
SQL Server
MS SQL Server 2012/2014/2016
license provided by customer
xxxx
SentrySuite installation
SentrySuite 2.21 and newer

station SentrySuite 2.21 and newer
measurement or review station incl.
Sentry.NET server
SentrySuite 2.19 and older

station SentrySuite 2.19 and older
measurement or review station incl.
Sentry.NET server
Page 106/296 Version 06.02 • 2017-07-04

Installed Windows version – Desktop Operating systems
64 32 Desktop OS
Windows 7 64 bit / Windows 7 32 bit
Windows 8 or 8.1 64 bit
Windows 10 64 bit Before After

update update
Installed Windows version – Server Operating systems
Windows Server 2003 or 2003 R2 - 32 bit or 64 bit
Windows Server 2008 or 2008 R2 - 64 bit
Windows Server 2012 or 2012 R2 – 64 bit

Server OS
Windows Server 2016 – 64 bit Before After
update update
Update
Before After
System structure before updating system System structure after updating system
Version 06.02 • 2017-07-04 Page 107/296

A) Standalone Systems
A1) Standalone Systems - New installation
1) Installation checks whether operating system is supported by new version:

If operating system is not supported, than installation will not be possible (Error
message is shown). Supported operating system needs to be installed by user first.
2) Installation checks that SeS is NOT installed
Scenario A2 is used if SeS is installed
3) Installation checks whether there is an existing “SentrySuite” SQL server
instance already installed on the system. If this is the case and the existing
instance is a legacy SQL Server version than installation will not be pos-
sible (Error message is shown).
This check is needed, because existing instance of “SentrySuite” can cause issues
in later setup of configuration steps. This existing SQL server instance can be a left-
over from previous SentrySuite uninstall processes or can be manually created by
script based installations. In case of an issue the existing SQL server instance need
to be manually removed by user before installation can proceed. Please note: An
existing SQL Server version WITHOUT SentrySuite instance causes no issue and no
error message is shown.
4) Installation proceeds with Installation of SQL Server 2014 (if not already
installed)
5) Installation proceeds with installation of SentrySuite
After

station
SQL Server
2014
Page 108/296 Version 06.02 • 2017-07-04

A2) Standalone Systems - Update installation
For all alternatives below the following steps are done at first
1) The user needs to backup existing SQL database attached to SQL Server
2008R2 to external disc or network drive
Depending on next steps, this database is needed in case of an installation issue or
is used to be restored in one of the later steps.
2) Installation checks whether operating system is supported by new version:
message is shown). Supported operating system needs to be installed by user first.
Please note that especially 32 bit systems are no longer supported.
A2 – Alternative 1 (Recommended): Update Operating system (if needed) and install

SQL server 2014
Recommended way:
3) User makes a complete new installation of the Windows system
4) SentrySuite is installed (see A1 – New installation). SQL Server 2014 is
installed
5) Restore SQL database to SQL Server 2014
Call SentrySuite from Windows Control panel. Start “Repair program/Restore
database backup. In next dialog, enable option to restore database and select the
previously backed up database. Proceed with repair process.
6) A new configuration key needs to be entered in System configuration
Before After
SentrySuite 2.19 and older SentrySuite 2.21 and newer SQL Server SQL Server
station 2008 R2
station
2008 R2 license is still
available, but
no longer in
use
SQL Server SQL Server
2008 R2 2014
A2 – Alternative 1 Prerequisite:
Only possible if no Windows upgrade is planned/needed
3) Uninstall SQL Server 2008 R2 by using the Windows control panel
All Microsoft SQL Server 2008 R2 related programs need to be removed. When
you get uninstall errors, than recommended way (see above) needs to be used. It
is not unlikely that you get errors from uninstall and it can be quite complicate to
solve these issues.
4) Continue with installation. SQL Server 2014 is installed. SentrySuite is
updated
Call SentrySuite from Windows Control panel. Start “Repair program/Restore
database backup. In next dialog, enable option to restore database and select the
previously backed up database. Proceed with repair process.
Version 06.02 • 2017-07-04 Page 109/296

A2 – Alternative 2 - Do not upgrade SQL server 2008 R2:

Prerequisite: Operating system is supported by new version
Please notice especially that 32 bit operating systems are no longer supported
Please notice that SQL Server 2008 R2 is not compatible with Windows 10
This is the fastest upgrade path, but it is not recommended to be long term
active. This should only be done on special customer demand.
3) During SentrySuite installation a message is shown that there is already

an existing SentrySuite instance of SQL server installed and whether the
user wants to run the system without upgrading the SQL server.
As mentioned before it is preferred to upgrade the SQL server. If you really want
to use Alternative A2 than you need to decide NOT to upgrade the SQL server
and move forward with installation.
4) SentrySuite is updated. SQL Server 2014 is NOT installed
Before After
SQL Server
2014 license is
SentrySuite 2.19 and older SentrySuite 2.21 and newer SQL Server
delivered, but
station station not used until
2014
update of
system
SQL Server SQL Server Old SQL

Server 2008
R2 license is
2008 R2 2008 R2
still in use
B) Networked Systems (SeS 2.21 only with no mixed network),

SQL Server 2014 or core based licenses only
This type of setup is recommended for networks because it provides the easiest
system structure and no restrictions related to workflows and available data on any
system. There is no mixed network functionality with SeS 2.19.
In general, backend installations (New or updated installations) are installed in two
steps. At first the Backend/Server is installed or updated. In a second step client
systems are installed and updated.
Like in versions before backend installation can in principle be installed/updated by
using SentrySuite backend installation or by installation of single components (mostly
combined with core based licensing). Please note that SentrySuite installation checks
several installation and potential licensing issues, but this is not done when single
components are used for installation. For a SentrySuite based backend installation
system checks are made which are similar to Standalone installations.
Not every installation step for both possibilities are listed in the following scenarios,
but keep in mind that both possibilities are available.
Page 110/296 Version 06.02 • 2017-07-04

B1) Network 2.21 and SQL 2014 only - New installation
1) Install backend system based on alternatives below

Can be installed by script based setup or based on SentrySuite installation
2) Install client systems based on alternatives below
After
Clients

station
SQL Server
2
2014

station
SQL Server
2014
Server / Backend
SQL Server
1a
2014
SQL Server
1b
xxxx
Version 06.02 • 2017-07-04 Page 111/296

SQL Server
Alternative 1: Backend installation with SentrySuite. SQL Server
1a 2014
2014 Licenses are provided by SentrySuite
SQL Server Alternative 2: Backend installation provided by customer. SQL

1b xxxx
licenses for Backend server + clients provided by customer
(commonly with SQL core license)
SQL Server
Alternative 1 (with 1a): Without Emergency Failover, SQL Server in
2 backend installed with SentrySuite: No local SQL Server on Client.
2014
Access to Backend SQL server by SentrySuite license.
SQL Server Alternative 2 (with 1a): With Emergency Failover, SQL Server in
backend installed with SentrySuite: Local SQL Server on client.
2014 Emergency failover mode + access to backend SQL server by
SentrySuite license.
SQL Server Alternative 3 (with 1b): Without Emergency Failover, SQL Server in
backend provided and licensed by customer: No local SQL Server
xxxx on Client. SentrySuite SQL license is not used.
SQL Server
Alternative 4 (with 1b): With Emergency Failover, SQL Server in
SQL Server backend provided and licensed by customer: Local SQL Server on
2014
client. Emergency failover mode licensed by SentrySuite license.
xxxx Access to backend SQL server licensed by customer.
B2) Network 2.21 and SQL 2014 only - Updating complete

system to SeS 2.21
1) Update backend system based on alternatives below

- Client access is not possible during backend update
Update can be installed by script based setup or based on SentrySuite
installation
In a script based environment potentially only database needs to be updated to
new system structure and Sentry CIS data host service needs to be updated.
- Client systems can access the server when backend update has finished
successfully, but access can be delayed because of update procedures.
2) Update client systems based on alternatives below

Recommended way:
2.1) Note current computer name and configurations serial numbers.
2.2) User makes a complete new installation of the Windows system.
2.3) SentrySuite is installed as client installation using previous client’s server data.
2.4) During System Configuration (first time configuration in SentrySuite) the
previous computer assignment can be selected by checking previous computer
name and serial numbers. The client takes over previous clients settings and
calibrations. No data is lost. A new configuration key needs to be entered in
System configuration
Alternative:
Prerequisites (if not fulfilled use recommended way), see Paragraph 1.1.2.
There is no windows upgrade planned or needed
As preparation it is recommended to uninstall SQL Server 2008 R2 by using the
Windows control panel.
All Microsoft SQL Server 2008 R2 related programs need to be removed. When you
get uninstall errors, than recommended way (see above) needs to be used. It is not
unlikely that you get errors from uninstall and it can be quite complicate to solve
these issues.
Local SQL Server installation is no longer needed on SentrySuite client. Only on an
Emergency Failover system a local SQL server is needed, but in that case it should be
based on SQL Server 2014 instead of 2008R2.
Page 112/296 Version 06.02 • 2017-07-04

2.1) Start SentrySuite update installation

2.2) Installation checks whether operating system is supported by new
version
message is shown). Supported operating system needs to be installed by user
first. Please note that especially 32 bit systems are no longer supported.
2.3) In case that you haven’t uninstalled the SQL Server 2008R2 another
check is done.
This check is needed, because existing instance of “SentrySuite” can cause
issues in later setup of configuration steps. We recommend in addition to
uninstall the existing SQL Server 2008R2, because it is no longer needed on
client machines without Emergency failover. Please note: An existing SQL Server
version WITHOUT SentrySuite instance causes no issue and no error message is
shown.
2.4) SentrySuite is updated.
SQL Server 2014 is only installed if system was originally configured as
Emergency failover system.
2.5) A new configuration key needs to be entered in System configuration
Before After
Clients Clients
SentrySuite 2.19 and older SentrySuite 2.21 and newer

station station
SQL Server
SQL Server
2008 R2
2
2014
SentrySuite 2.19 and older SentrySuite 2.21 and newer

station station
2008 R2 2014
Server / Backend Server / Backend
2008 R2 2014
1a
1b
xxxx xxxx
Version 06.02 • 2017-07-04 Page 113/296

SQL Server
Alternative 1: Update of backend installation with SentrySuite. SQL
1a 2014
Server 2014 Licenses are provided by SentrySuite. SQL Server 2008
R2 licenses are not used any longer.
SQL Server Alternative 2: Backend installation provided by customer. If
1b backend server fullfills requirements, than no update of SQL server
xxxx is needed, only db structure and Sentry CIS hosts need to be
updated.
SQL Server
2 backend installed with SentrySuite: No local SQL Server on Client is
2014
needed. Access to Backend SQL server by SentrySuite license. SQL Server
2008 R2 licenses are not used any longer. Update of client at best done
via new installation or otherwise SQL server needs to be uninstalled.
SQL Server Alternative 2 (with 1a): With Emergency Failover, SQL Server in backend
installed with SentrySuite: Local SQL Server on client. Emergency
2014 failover mode + access to backend SQL server by SentrySuite license.
Update of client at best done via new installation or otherwise SQL
server needs to be uninstalled.
SQL Server
Alternative 3 (with 1b): Without Emergency Failover, SQL Server in
xxxx
on Client. SentrySuite SQL license is not used. Update of client at
best done via new installation or otherwise SQL server needs to be
uninstalled.
SQL Server
2014
xxxx Access to backend SQL server licensed by customer. Update of
client at best done via new installation or otherwise SQL server
needs to be uninstalled.
Page 114/296 Version 06.02 • 2017-07-04

B3) Network 2.21 and SQL 2014 only - Adding additional

devices with SeS 2.21
1) Install client system based on alternatives below

3) Activate emergency failover on client machine (via System Configuration
in SentrySuite). This installs a new SQL server 2014 instance on the local
machine
Before After
Clients Clients
SentrySuite 2.21 and newer SentrySuite 2.21 and newer

station station
SQL Server
SQL Server
2014
2014

station
1
SQL Server
2014
2014 2014
or or
xxxx xxxx
SQL Server
2014
needed. Access to Backend SQL server by SentrySuite license. Install
new client and connect to network
installed with SentrySuite: Local SQL Server on client. Emergency
2014 failover mode + access to backend SQL server by SentrySuite license.
Install new client and connect to network
SQL Server
xxxx
on Client. SentrySuite SQL license is not used. Install new client
and connect to network.
SQL Server
2014
xxxx Access to backend SQL server licensed by customer. Install new
client and connect to network
Version 06.02 • 2017-07-04 Page 115/296

B4) Network 2.21 and SQL 2014 only – Add Standalone system
of 2.19 to existing network and update to SeS 2.21
1) Backup local database to USB or network drive

2) Update Standalone system to version 2.21 as described in Scenario B2
3a) In non-clustered environments (if server is installed with SentrySuite
installation)
Restore database to server by using “Support tools”. Depending on database
versions patient- and measurement data is converted automatically to server
database if needed.
3b) In clustered environments (script based installations)
All steps are done by IT system administrator:
- Restore database to server to special database (“SyncSource”).
- Afterwards merge SyncSource database into destination database by using
upgrade and merge scripts created by “support tools”.
B5) Network 2.21 and SQL 2014 only – Add Client system of
version 2.19 to existing network and update to SeS 2.21
See B2) Step 2.
C) Networked Systems (Mixed network 2.19), Mixed SQL

Server versions
This type of setup should only be used when update of complete system to one
version is not possible (at best for a limited timeframe). In a mixed network
environment, the backend/server database needs to be updated to the version of the
newest system. In addition, the Sentry CIS Data Service Host needs to be updated to
the version of the newest system.
Running a mixed network can result in a restricted functionality especially on
older (e.g. 2.19) systems. Please check mixed network documentation for a list of
restrictions. It is recommended to run mixed systems only for a limited time.
Running different SQL server versions in backend and on clients is possible, but
licensing can be quite complicate. We recommend update of all systems to the same
SQL Server version. Only if the backend server license is provided as a core based
license, than a mixed licensing between user provided version and licensing of failover
systems can make sense.
NOTE: For all mixed network installations: All systems which are not running updated
to the latest software version need at first updated to the latest available hotfix
package.
There are four general use cases to use mixed network functionalities. Use cases
number one and two are the main scenario why mixed networks are provided. It is
in each case preferred to upgrade the complete network as soon as possible to most
recent version.
Page 116/296 Version 06.02 • 2017-07-04

1. Upgrade of existing network to version 2.21 needs some days or even

weeks because of complex network structures or long validation times for
measurement systems.
This is the main scenario
For this use case existing systems with version 2.19 can run as long as they are
not upgraded. General data workflows need to be checked before, because data
measured on 2.21 systems can not be reloaded with 2.19 measurement programs.
2. Upgrade of existing networks to version 2.21 is currently not possible

because of financial delays, but is planned in a short period.
General data workflows need to be checked before, because data measured on 2.21
systems can not be reloaded with 2.19 measurement programs.
3. There are a limited number of stations which should stay on 2.19 because
of computer, operating systems or other restrictions.
General data workflows need to be checked before, because data measured on 2.21
systems can not be reloaded with 2.19 measurement programs.
4. The system should run for a more or less unlimited time in a mixed
network environment
It is recommended to limit access of 2.19 systems to special workflows which are not
contrary to the mixed network restrictions.
Version 06.02 • 2017-07-04 Page 117/296

C1) Add SeS 2.21 station to existing SeS 2.19 network without
SQL Server upgrade
1) Update 2.19 systems to latest available hotfix package for 2.19

2) Update backend system based on alternatives below
Update can be installed by script based setup or based on SentrySuite
installation
In a script based environment potentially only database needs to be updated
to new system structure and Sentry CIS data host service needs to be
updated.
successfully, but access can be delayed because of update procedures
Before After
Clients Clients
SentrySuite 2.19 station SentrySuite 2.19 station
2008 R2 2008 R2

station 2
SQL Server
2014
SQL Server
SQL Server
2008 R2
1a
2008 R2
1b
xxxx xxxx
Page 118/296 Version 06.02 • 2017-07-04

SQL Server
1a 2014 If backend server fullfills requirements, than no update of SQL

server is needed, only db structure and Sentry CIS hosts need to be
SQL Server updated.
1b
xxxx
SQL Server
2014
needed. Access to Backend SQL server by SentrySuite 2014 license. This
is possible because newer SQL licenses can be used to access SQL Server
2008 R2 in backend.
installed with SentrySuite: Local SQL Server on client. For 2.19 systems:
2014 Emergency failover mode + access to backend SQL server by SentrySuite
SQL 2008 R2 license. For 2.21ff systems: Emergency failover + access to
backend SQL server via SQL 2014 license. Access to backend SQL server
is possible because newer SQL licenses can be used to access SQL Server
2008 R2 in backend.
SQL Server
xxxx
on Client. SentrySuite SQL license is not used.
SQL Server
2014
client. Emergency failover mode licensed by SentrySuite license
xxxx (SQL Server 2008 R2 for 2.19 systems, SQL Server 2014 for 2.21
systems). Access to backend SQL server licensed by customer.
Existing (SeS 2.19 stations): Can still run with SQL server 2008 R2
SQL Server
license. Uninstalling SQL server 2008 R2 on local client machine is
NOT possible.
2008 R2
Version 06.02 • 2017-07-04 Page 119/296

C2) Add SeS 2-21 station to existing SeS 2.19 network with
Server upgrade
Precondition: This scenario is only possible if core based licenses are used. This
means that this scenario is NOT possible with client based licenses provided
by SentrySuite. In that case, you have to update complete network to SeS
2.21 by using scenarios B2 and B3.
The general steps are the same as in scenario

For all alternatives below the following steps are done at first
1) The user needs to backup existing SQL database attached to SQL Server
2008R2 to external disc or network drive
Depending on next steps, this database is needed in case of an installation issue or
is used to be restored in one of the later steps.
2) Update 2.19 systems to latest available hotfix package for 2.19
3) Update backend system Step 1: Install SQL Server 2014 based on
alternatives below
Alternative 1: If backend installation is virtualized:
Provide virtualized image for SQL Server 2014
Alternative 2: If not virtualized, make complete new installation of
Windows system:
Reinstall operating system, install SQL Server 2014
Alternative 3: If installation is not possible: Uninstall SQL Server 2008 R2 by
using the Windows control panel
All Microsoft SQL Server 2008 R2 related programs need to be removed. When
you get uninstall errors, than Alternative 2 (see above) needs to be used. It is not
unlikely that you get errors from uninstall and it can be quite complicate to solve
these issues.
4) Update backend system Step 2: Install Data Service and SentrySuite (if
needed)
Update can be installed by script based setup or based on SentrySuite installation
In a script based environment database needs to be updated to new system
structure and Sentry CIS data host service needs to be updated.
In a SentrySuite based installation SQL Server 2014 is installed by using SentrySuite
installation functionality.
successfully, but access can be delayed because of update procedures
Page 120/296 Version 06.02 • 2017-07-04

Before After
Clients Clients
SentrySuite 2.19 station SentrySuite 2.19 station
SQL Server
SQL Server
2008 R2
xxxx

station 2
SQL Server
xxxx
x x
SQL Server
2008 R2
1a
1b
xxxx xxxx
x
SQL Server
Alternative 1 (with 1a): Update is NOT possible
Access of SeS 2.19 clients with SQL Server 2008 R2 licenses to a SQL
1a 2014
Server 2014 would result is NOT possible.
SQL Server
If backend server fullfills requirements, than no update of SQL
1b server is needed, only db structure and Sentry CIS hosts need to be
xxxx
updated.
2 x SQL Server
2014
Alternative 1 and 2 (with 1a): Update is NOT possible
Access of SeS 2.19 clients with SQL Server 2008 R2 licenses to a SQL
Server 2014 would result is NOT possible.
SQL Server
xxxx
on Client. SentrySuite SQL license is not used.
SQL Server
SQL Server
2008 R2Server
SQL backend provided and licensed by customer: Local SQL Server on
2014
client. Emergency failover mode licensed by SentrySuite license
xxxx (SQL Server 2008 R2 for 2.19 systems, SQL Server 2014 for 2.21ff
systems). Access to backend SQL server licensed by customer.
Version 06.02 • 2017-07-04 Page 121/296

1.4 Database Imports to SentrySuite

1.4.1 Vmax Onetime Batch Import to SentrySuite
Introduction:
With the release of SentrySuite a need may arise to import Vmax data into
SentrySuite. The complete procedure to interface a Vmax Encore system to SentrySuite
is described in paragraph 1.2.6.
If you are replacing the Vmax system(s) and you need to do a onetime database
import from Vmax data into SentrySuite 2.10, please follow this procedure.
Notes:
• The customer needs to be informed that inconsistent patient demographic data
within the Vmax DB cannot be converted, these patient-records will be logged but
will not be transferred to SentrySuite!
• This procedure assumes the Vmax system is running version 21-2.
• Make sure your current Vmax DB resides on your local harddisk!
• Any archived patient data needs to be restored into the Vmax DB first!
Required parts:
• p/n V-570149 SeS data integration kit
This kit contains the DBxConnect CD and the latest revision of Vmax Encore
software.
• p/n V-781239 Service Manual SentrySuite Software
(Note: PDF file is free of charge, printed version has a cost!)
Procedure:
1. Vmax DB promotion to Version 21-2b:
If the current Vmax database is not yet at the latest version you will need to
promote the current Vmax DB to the latest Encore version.
(The latest Vmax Encore CD is part of the kit V-570149, see required parts above).
a) Run the setup.exe from the Encore CD 21-2b.
NOTE: In the installation screen, select the backup s/w option to folder
"c:\<your current Vmax version> (example: "c:\12-7", see fig.1.)
Fig.1: The Vmax installation screen
Page 122/296 Version 06.02 • 2017-07-04

b) Install the new Encore CD software, uncheck all options (see fig.1).
c) Start the new Vmax s/w. This will automatically promote the current Vmax DB
to the latest version. Depending on the size of your database, this may take
quite some time.
d) If required, you can restore the original Spectra software from the backup,
folder "c:\12-7 to the original c:\vision" (see step "1a").
2. Installation & configuration of DBxConnect:

We need a temporary installation of DBxConnect software on the Vmax station.
a) From the DbxConnect CD run the setup.exe

b) Install ONLY 2 components:
I) the DBXConnect Service host +
II) the DBxConnect Database adapter!
Fig.2: DBxConnect ONLY 2 components required!
c) See paragraph 1.2.5 for details.

d) Note that if you only need to do a one time import, you only need 2 of 4
DBxConnect components.
3. Configure SentrySuite Connectivity Manager:

You will need to configure the SeS interconnectivity manager for the Vmax Db
conversion. See paragraph 1.2.5.
4. Perform a Batch Import of Vmax data from SentrySuite interconnectivity manager.
See paragraph 1.2.6.
Version 06.02 • 2017-07-04 Page 123/296

1.4.2 Batch Import from JLAB to SentrySuite

See our Online Manual "JLAB - SentrySuite Connectivity", paragraph "Importing
Batch Data".
1.4.3 Batch Import from Micro Medical to SentrySuite
1.4.4 Batch Import from Nspire to SentrySuite
1.5 Repair, Reconfigure and Remove SentrySuite Software (RRR-mode)
RRR-mode can only be activated on a PC that already has SentrySuite installed.

When needed, there are two ways of starting this mode:
• Re-run SentrySuite setup.exe from a DVD or a local folder.
• Open Windows control panel and
- select "Programs & Features"
- right-click on "SentrySuite"
- select "Change".
Note that option 2 does not require SentrySuite installation media.
Page 124/296 Version 06.02 • 2017-07-04

1.5.1 Repair SentrySuite Software
This option will repair your SentrySuite installation and restore it to its original
situation right after the initial installation.
Note: The repair will not affect your patient data.
The repair mode will allow you to import a previous SentrySuite Restore Point.
For details on creating a SentrySuite restore point, see paragraph 1.4.
• Please backup FIRST (see online manual, home page, Database...., Backup/
Restore)
• Note that this restore will overwrite all data and settings in SentrySuite at
this moment!
Version 06.02 • 2017-07-04 Page 125/296

Once you selected the location of your SentrySuite restore point, the software will
ask you to reboot the PC. After the reboot it will automatically continue restoring
your data from the selected location.
1.5.2 Reconfigure SentrySuite Software
This option allows you to

• Take over a changed computer name.
In network installations, the computer hostname may sometimes need to
be changed.
As connections in a SentrySuite network depend on these
hostnames, it is necessary to make these changes in SentrySuite.
• Change of internal workstation-ID.
When you receive a new computer from CareFusion with SentrySuite preinstalled
and that needs to be implemented in a new/existing SentrySuite network, this op-
tion may be required to be run once at installation time. This option will create a
new unique workstation-ID in the existing SentrySuite server in your customer's
network. It will copy all the settings from the old to the new workstation-ID.
• Reconfigure the server connection
If you replaced an existing SentrySuite server, you may need to reconfigure the
SentrySuite clients to the new SentrySuite server host location URL (see paragraph
1.2.3.1, section B).
• Change other configurations depending on installation
n/a.
Page 126/296 Version 06.02 • 2017-07-04

1.5.3 Remove SentrySuite Software
This option allows you to uninstall SentrySuite.
Please create a SentrySuite restore point FIRST (see paragraph 1.4) before
uninstalling!
Version 06.02 • 2017-07-04 Page 127/296

1.6 Emergency Failover mode
1.6.1 Set-up on a SentrySuite client

• Open the SentrySuite Client station that requires Emergency Fail-Over activated
• Open “System Configuration” in SentrySuite Desktop
• Under "Configuration" click “Convert to CIS Client System with Failover"
• Click “Start Reconfiguration” to setup the SentrySuite Client with Emergency

Fail-Over.
• SentrySuite will close and the installation/reconfiguration of SentrySuite will begin.

Click <Next>.
Page 128/296 Version 06.02 • 2017-07-04

• Use the <Test> button to test the connection to the SentrySuite BackEnd server
and click <Next>.
• Do not check the “Change Workstation ID” box. Click <Reconfigure>.
Version 06.02 • 2017-07-04 Page 129/296

• SentrySuite Client station will now reload and setup with Emergency Fail-Over
mode enabled.
• A local Microsoft SQL server 2008R2 setup will commence.
• Proceed with a reboot if required.
Page 130/296 Version 06.02 • 2017-07-04

• SentrySuite will continue to setup once the Windows reboot is completed.

• A local SentrySuite DB is setup to be used for Emergency Fail-Over mode.
• When prompted, click <Finish> and start SentrySuite Client.
Version 06.02 • 2017-07-04 Page 131/296

• Click <Next> and enter the SentrySuite Client configuration license details.
• The local SentrySuite DB is then finished being set up.

• Basic demographics data and settings are downloaded from the main SentrySuite
server.
• The final system setup is then completed. Note that the client station now is listed
with “Failover".
• The SentrySuite Client station is now setup with Emergency Fail-Over mode
enabled.
Page 132/296 Version 06.02 • 2017-07-04

1.6.2 Emergency Fail-Over mode in Action
SentrySuite Emergency Fail-Over mode uses a special user for Emergency logins:
Application User Password

SeS Emergency Failover Technician Emergency
1.6.2.1 Different Modes & Status screens

The mode below indicates that the SentrySuite Client has Emergency Fail-Over Mode
enabled and is connected to the SentrySuite Server.
In the event that SentrySuite server becomes unavailable for more than about 5
seconds, then SentrySuite Client will state that it’s disconnected and present the
option to either close SentrySuite and wait for the SentrySuite Server to be available
again or to stop and restart up SentrySuite in Emergency Fail-Over mode.
If SentrySuite is restarted in Emergency Fail-Over mode, the following message

appears:
Click <OK> to start SentrySuite in Emergency Fail-Over mode.

When SentrySuite starts in Emergency Fail-Over mode, functionality is limited.
Emergency Fail-Over mode is confirmed by the Database indicating being “Not
Connected”.
Note also that many of the Desktop/Admin options are not enabled… only Calibration
and Measurement applications are available.
All test data performed in Emergency Fail-Over mode is stored to a local SentrySuite DB.
The SentrySuite server patient demographic is available to view and add tests to in
Emergency Fail-Over mode. However, no retrospective test data may be viewed.
Version 06.02 • 2017-07-04 Page 133/296

If the SentrySuite Server becomes available again whilst testing in Emergency Fail-
Over mode, the Database status turns to “Available”.
Note that the Red “disconnected” indicator is still showing. This indicates that
SentrySuite is still in Emergency Fail-Over mode. In order to connect back to the
server, SentrySuite software on the client must be restarted.
Once SentrySuite has restarted, it will sync any data obtained Emergency Fail-Over
mode. SentrySuite cannot be used whilst the data is syncing to the main DB on the
SentrySuite server.
Once done, SentrySuite will open in network mode with full functionality enabled
again.
The green "Connected" logo indicates that network mode is enabled.
Page 134/296 Version 06.02 • 2017-07-04

1.6.2.2 Testing in Emergency Fail-Over mode

In the event that the SentrySuite network is interrupted for more than 5 seconds
during testing a patient, SentrySuite will prompt the user to exit SentrySuite and
restart in Emergency Fail-Over mode.
SentrySuite is then restarted in Emergency Fail-Over mode.
Note that in Emergency Fail-Over mode there is no test data for current patient
although the demographic data has come across. A new test visit needs to be
initiated.
Any offline tests that are measured in Emergency Fail-Over mode will be
automatically transferred to SentrySuite server once SentrySuite has been rebooted
into its normal (networked) mode of operation.
Version 06.02 • 2017-07-04 Page 135/296

Testing is done under a new visit. If the SentrySuite network is made available again,
the Database status will turn to “Available”. It’s recommended to finish testing
in Emergency Fail-Over mode and then restart SentrySuite into its normal mode of
operation.
At that point, the data acquired in Emergency Fail-Over mode will be automatically
synced to the SentrySuite DB on the SentrySuite server as a new visit. If required, it
can be merged with the rest of the test results with Patient Data Management.
Upon restarting SentrySuite it can be seen that the test data collected in Emergency
Fail-Over mode is being transferred to the SentrySuite server. Once done, it will be
erased from the local SentrySuite DB used for Emergency Fail-Over mode.
Note: When the patient file in this example is brought up, there are two test
visits. The second visit with the pre and post field is the data synced from the local
SentrySuite DB when in Emergency Fail-Over mode. Given this is a continuation of
the initial test, the spirometry in Emergency Fail-Over mode was performed as Post
BD, i.e. the blank Pre 1 field needs to be combined with the initial visit that was
commenced in network mode.
Page 136/296 Version 06.02 • 2017-07-04

1.6.2.3 Use of Patient Data Management
Within "Patient Data Management", put the patient on both sides of the screen,
highlight the post 1 on the patient file on the Left hand side, highlight the Pre 1 of
the initial test when in network mode on the patient file on the right hand side. Note
that the <Level> button is enabled in the middle.
Click the <Level> button to transfer the Post BD level to the initial test visit which
just has the pre 1 level.
Click <Yes> when prompted to move the level.
Version 06.02 • 2017-07-04 Page 137/296

Now, the Post 1 level is combined with the Pre 1 level test done when in network
mode.
Now, delete the second visit with the empty Pre 1 level which was done in
Emergency Fail-Over mode. This is done by highlighting the test visit and clicking the
"Bin" icon at the bottom of the screen.
Page 138/296 Version 06.02 • 2017-07-04

Combined test is left for reporting on.
Version 06.02 • 2017-07-04 Page 139/296

1.7 Support Tools ≥ V. 2.13
1.7.1 General notes on using this tool

• SupportTools.exe is version-specific for different versions of SentrySuite!
• Please verify that you have the right version for the SentrySuite version you want
to use.
• Check the CareFusion FTP server for updates.
• This paragraph describes the SupportTools.exe for versions 2.13 and up.
• SupportTools.exe for SentrySuite 2.11 is slightly different, please contact
CareFusion GCS department for instructions.
• BEFORE using this program, make an extra backup of your SentrySuite system
and secure this backup in a safe environment.
When you run SupportTools.exe, you will be asked to supply credentials.

Please use: User = Service
Password = SESService
Next, the SupportTools Main Menu will appear:
Please select a function you wish to execute. See the next paragraphs for details.
Page 140/296 Version 06.02 • 2017-07-04

When can you use SupportTools:

• Standalone (all SeS versions)
• Backend Host System with SentrySuite (version 2.13 and onwards)
• Remote Client using CIS Data Service (version 2.13 and onwards)
Green: All of the tools will work! – Why?

• All tools work because the required SentrySuite client software is installed,
• the SQL Server SentrySuite Instance is installed locally,
• and replication is not used!
Amber: Patient Data Management tools will work! – Why?

• Patient Data Management Functions will work because the SentrySuite Client
software is installed locally.
• DB Diagnostics and Repair Functions do NOT work because SQL Server SentySuite
Instance is remote.
When NOT to use Support Tools:

• Backend Host System without SentrySuite.
Why?
• Ses client s/w not installed.
Version 06.02 • 2017-07-04 Page 141/296

1.7.2 Functions
1.7.2.1 DB Tools
a. Clean-Up scripts
When selected, the Check and Cleanup menu shows.
Simply select the Cleanup Script you wish to apply from the relevant drop down list
and click <Run>.
Once complete, the execution status (success or fail) should be shown in the Activity
Log below.
N.B.: The scripts will only update the database if a condition exists that must be
corrected.
b. DB Diagnostics & Fix

This tool will:
1. Rebuild a SQL Server Instance that will not start
2. Repair database corruption (master, msdb and SentrySuite)
3. Check configuration and reconfigure where necessary
(SQL Server Services, Backup Jobs)
This tool will not:

1. Resolve replication issues
2. Run on a system with replication.
Page 142/296 Version 06.02 • 2017-07-04

1.7.2.2 Patient Data Management Tools

a. Sync two SentrySuite databases into one database
• This function requires a full SentrySuite installation!
• This Tool will merge patient-data from another SentrySuite database into the
default SentrySuite database.
b. DataSource
• This functionrequires a SentrySuite Backup file (*.sesbp) of the same version as
the datasource. This Backup file needs to be accessible on the SentrySuite
server (see "Backup to Restore" in the screenshot below).
Version 06.02 • 2017-07-04 Page 143/296

c. Intermediate Database
• This Sync-tool will create a separate intermediate target DB in the SentrySuite
instance (see MS Management studio, SentrySuite instance, Databases, SES_Sync_
Source).
c. Target Database
• Once the synchronization function has restored the data from the backup file into
the intermediate database, it will search this intermediate database for patient
data that is non-existing data in the SentrySuite database. It will request to
"synchronize" this patient data into the standard SentrySuite database.
• This synchronization function may result in duplicate patients (same PID- & DoB-
fields, differences in other fields?) in the target database SentrySuite. If duplicate
patients are detected, a patient-merge will automatically be offered to resolve
these duplicate patients.
• Sync speed: using local DB's 1750 pat's, 2500 visits take 5 min.
Page 144/296 Version 06.02 • 2017-07-04

Version 06.02 • 2017-07-04 Page 145/296

• If duplicated patients are detected, merge is automatically offered. See next

paragraph.
• If no patient-merge is required, the following screen is shown:
Page 146/296 Version 06.02 • 2017-07-04

c. Merge duplicate patients into one patient
• Possible Merge Scenarios

You have just synchronized data from a different SentrySuite system and you
notice that you now have duplicated patients
• How to identify merge candidates

When using the Patient Search dialog in SentrySuite, you notice that the patient
data is duplicated:
• Rules for merge

Merge possible for patients that have the same identification and birthdate only.
Patient Last name, First name and Gender are ignored.
• There’s no possibility to select a target/master patient!

• The size of the Database will influence the run-time of this tool.
• Any indication on progress? No, just on-screen messages.
Version 06.02 • 2017-07-04 Page 147/296

2. Software
2.1 Software History

Not available at the moment.
2.2 SentrySuite Desktop
Advanced features in the SentrySuite Desktop are only available after logging in
with service credentials: In the SeS Desktop, select "Programs" and
<Service Settings>.
Login Authentication: user = "Service", password = "SESService"
2.2.1 SentrySuite Desktop Top Menu Items

2.2.1.1 Show System Information
Clicking “Show System Information“ in the “Program“ tab opens additional
information.
System Startup Provides information on the warmup of the devices of the connected systems.
System Desktop Shows the start screen from which all applications can be accessed.
System Messages Show in detail (date and time) when the warmup of every connected system has been
performed.
System Database Provides information on the local database such as:
• Date of the last backup

• Details on the network protocol
• Current statistics on the SentrySuite database such as:
- Number of included patients

- Number of examinations performed
- Number of connected stations
- Station name
Page 148/296 Version 06.02 • 2017-07-04

Manage DB tasks like Attach, Detach, Backup & Restore the database.
Manage DB jobs such as running backups, etc.
System Installation Provides information on system installation such as:
• Operating system, type of computer, CPU, memory

• Installed SentrySuite version
• Installed SentrySuite programs
• Installed hardware with serial number and firmware
Version 06.02 • 2017-07-04 Page 149/296

System Hardware Provides information on the connected hardware such as:

PFT with serial number, firmware, status ...
This paragraph details the how to use the Device Diagnostics Functions that are built
into SentrySuite.
1. If required, click the arrow on the left side of Device Diagnostics to display the
various diagnostic functions available.
NOTE: these functions may vary per your hardware configuration!
2. Selecting a Diagnostic Function will open a link in the System Information screen
on the right that will allow you to perform the diagnostic test.
2.2.1.2 Show Service Information
Advanced features in the SentrySuite Desktop are only available after logging in
with service credentials: In the SentrySuite Desktop, select "Programs" and
<Service Settings>.
Login Authentication: user = "Service", password = "SESService"
After logging in with the service credentials you can select the various Tabs to view
detailed information and see the advanced menu options at the bottom of the screen.
Page 150/296 Version 06.02 • 2017-07-04

2.2.1.3 Service Settings

Here you can set / clear your maintenance information:
Desktop Task Settings:
In this menu you can add tasks that are initiated at system startup.
Version 06.02 • 2017-07-04 Page 151/296

2.2.1.4 Language Import

This menu option allows you to import a SentrySuite Country CD into your system.
A SentrySuite Country CD contains a set of country specific settings for SentrySuite
which can be created with the Data export function in chapter 2.5.2.
2.2.1.5 System Summary Import

2.2.1.6 Exit
This command exits the 'service mode' of the SentrySuite Desktop app.
2.3 Patient Chart

2.3.1 Patient
2.3.2 Demo Patient
2.3.3 Bio QC
2.3.4 SentrySuite QM
2.4 User Administration

2.4.1 Log File Viewer

Please see paragraph 3.1 for more information.
2.4.2 User Administration

Page 152/296 Version 06.02 • 2017-07-04

2.5 Database Handling
Many features in this menu require you to log in to the SentrySuite Desktop with
service credentials, see paragraph 2.2 "SentrySuite Desktop".
2.5.1 Backup/Restore
For Backup purposes, please instruct the IT department of your enduser to copy
any backup files that SentrySuite creates in the backup location to other offline
storage media.
For SentrySuite servers:

The backup location for SentrySuite backup files is defined in your server setup
(see 1.2.3.1, section C).
For Standalone SentrySuite systems:

The default Backup location is "C:\program files (x86)\CareFusion\SentrySuite\
DB\Backup\".
View and Change Backup Jobs within SentrySuite

Enter "Service Settings..." in the SentrySuite application:
Login with service user:
Password: "SESService"
Select the "SystemDatabase" tab and click on <Gather Database Information>.
Version 06.02 • 2017-07-04 Page 153/296

Select the Maintenance Job/ Backup Job which needs to be displayed or changed.
Click <Manage Database Jobs> to start the Database Administration tool.
Select SQL server instance (SeS-server or local computer).
Page 154/296 Version 06.02 • 2017-07-04

Click the <Show available jobs> button.
Disable the check mark on "Use the actual windows user to connect" if no jobs
are displayed. The output test windows shows: "Failed to get the Jobs: Failed to
connect to server..."
Click <Show job details / Modify Schedule> to display the backup job details.
Version 06.02 • 2017-07-04 Page 155/296

To save the modified schedule job, click <Save modifications>.
Page 156/296 Version 06.02 • 2017-07-04

Review / Modify Backup Jobs
"C:\Program Files\SentrySuite\VasSMOAdminGui.exe" /jobs
This tool can be used to verify and modify the existing SeS databases backup jobs.
VasSMOAdminGui, Backup and Restore Tools, Backup SeS

Databases from SeS Database Administration Tool
"C:\Program Files\SentrySuite\VasSMOAdminGui.exe" /backup

"C:\Program Files\SentrySuite\VasSMOAdminGui.exe" /restore
This tool can be used to backup any existing SeS Database on the local system as well
as on any SeS server.
Note: The backup file extension must be ".SesBp".
Version 06.02 • 2017-07-04 Page 157/296

Page 158/296 Version 06.02 • 2017-07-04

SentrySuite comes with the following standard backup jobs scheduled to run in the
background.
Standard Backup jobs:
SeS-Workstation Monday Tuesday Wednes- Thurs- Friday Satur- Sunday Time Backup File Name
day day day
Full1BackupSentrySuite X X X X 14:00 SentrySuite1.SesBp
Full1BackupSentrySuitemaster X X X X 14:00 SentrySuitemaster1.bak
Full1BackupSentrySuitemsdb X X X X 14:00 SentrySuitemsdb1.bak
Full2BackupSentrySuite X X X 14:00 SentrySuite2.SesBp
Full2BackupSentrySuitemaster X X X 14:00 SentrySuitemaster2.bak
Full2BackupSentrySuitemsdb X X X 14:00 SentrySuitemsdb2.bak
TrLog1BackupSentrySuite X X X X X X X 9:00 SentrySuite1.trn
SeS Server Monday Tues- Wednes- Thurs- Friday Satur- Sunday Time Backup File Name
day day day day
Full1BackupSeSGlobal X X X X 0:00 SeSGlobal1.bak
Full1BackupSentrySuitemaster X X X X 0:00 SentrySuitemaster1.bak
Full1BackupSentrySuitemsdb X X X X 0:00 SentrySuitemsdb1.bak
Full2BackupSeSGlobal X X 0:00 SeSGlobal2.bak
Full2BackupSentrySuitemaster X X 0:00 SentrySuitemaster2.bak
Full2BackupSentrySuitemsdb X X 0:00 SentrySuitemsdb2.bak
TrLog1BackupSeSGlobal X X X X X X X 9:00 SeSGlobal1.trn
Version 06.02 • 2017-07-04 Page 159/296

2.5.2 Data Export/Import
Intended Use
The intended use of this section is to describe how the content of the Country CD is
prepared.
The Country CD is used to modify a new installed SentrySuite workstation with
predefined database items and settings.
This modification is also called "upgrade process" of SentrySuite. Each set of a
country specific upgrade must be on its own country specific CD.
Content of the Country CD

The CD contains files for starting the automated upgrade process and a directory
which contains the data files with the information which is transferred to the data-
base.
Root
The root directory contains all the necessary files to start and perform the country
specific upgrade process of the SentrySuite installation. The set of files and the
content of the scripts are created and modified by the development department only.
Note: Never change the content of these files!
autorun.inf Windows shell script to perform autostart of a CD

PRODUCT.TAG Information about the software platform and version
SesAuto.exe Auto start utility
SeSAuto.ini Script used to perform autostart
US.GRD Script for the upgrade of database items
Database xml exports

The country CD contains a predefined set of different exported database items. The
files reside in the directory DBImport.
Settings.xml Setting values

PLB.xml Measurement parameter list box settings
ParamLocal.xml Parameter localization of one language local
ReportExport.xml Report definitions
Medications.xml Medication names and administrations
User.xml SentrySuite user definitions
UserGroup.xml SentrySuite user group definitions
Authors.xml Predicted system authors definitions
Modules.xml Predicted system modules
Questionnaire.xml Questionnaire
Page 160/296 Version 06.02 • 2017-07-04

Each item can contain the exported data of the specific type. The exported data
resides in .xml-files with predefined names. The .xml-files are used within a predefined
automated procedure which can be started automatically. During this process the files
are opened and the content is merged into the database.
Create Content of the Country CD

This section describes how the content of each item of the setting CD can be created.
The most important issue is that each data type must be exported into a file with the
exact name which is used during the script, otherwise the upgrade procedure cannot
find the file and no data will be transferred. With the version SentrySuite 2.5, there is
a new and easy way to export the complete system into one directory which can be
specified by the user.
System Summary export

In the last tab of the export/import dialog is a possibility to specify a directory where
the complete system export should be copied to. Call the export dialog form the
Desktop program menu or button menu:
Specify the export directory and press export.

The predefined list of exported settings and data to be used in a country CD contains:
- All reports (ReportExport.xml)
- Parameter list settings of all programs (Settings.xml)
- All user predicted authors and modules (Authors.xml and Modules.xml)
- Parameter language properties (ParamLocal.xml)
- All questionnaires (Questionnaire.xml)
- General settings (example: print screen, monitor, default measurement program,
etc.) (Settings.xml), and Default user (User.xml)
- Measurement settings (Settings.xml)
- Measurement template sets (Settings.xml)
- Medication settings (Settings.xml)
- Medication and administrations (Medications.xml)
- Comment templates (Settings.xml)
- Patient settings (default patient settings and patient dialog settings) (Settings.xml)
Note: There are no user group exports in the system summary export.
Version 06.02 • 2017-07-04 Page 161/296

Single data value export

The other possibility is to export single data items by using all the other tabs of the
export/import dialog. The following chapters explain the possible items.
Note that the file names must be consistent with the specified names of the
country CD script.
a) Creating settings value export:

Call the export dialog from the Desktop program menu:
Select the tab "General Settings" and mark the item you want to be in the export
file from the left part only, which concerns the system settings (red rectangle).
Enter the path and file name of the export file.
The file name must be "Settings.xml".
You can add the general system settings, the measurement settings and medication
settings, but not the medication itself. These are exported in a separate file!
You can also select and add the measurement template settings from list below.
Copy the file into the DBImport directory of the country CD.
Page 162/296 Version 06.02 • 2017-07-04

b) Creating PLB export:

Select the tab "Parameter list" and mark the programs which parameter list you
want to export.
Enter the path and file name of the export file. The file name must be "PLB.xml".
All parameter list box settings of the marked programs will be exported.
The parameter list box settings can be adjusted in the measurement programs.
Version 06.02 • 2017-07-04 Page 163/296

c) Creating parameter localization export:

Select the tab "Unit/Parameter" and mark the local language you want to export.
Enter the path and file name of the export file.
The file name must be "ParamLocal.xml".
All parameter and unit localizations of the selected language local will be exported.
The parameter and unit can be adjusted in the "General configuration" dialog of
the desktop.
Page 164/296 Version 06.02 • 2017-07-04

d) Creating report definition export:

Select the tab "Export reports" and move the report to the export list you want
to export. Enter the path and file name of the export file. The file name must be
"ReportExport.xml".
Copy the file into the DBImport directory of the Country CD.
Version 06.02 • 2017-07-04 Page 165/296

e) Creating medication export:

Select the tab "General settings" and select the medications you want to export.
Enter the path and file name of the export file. The file name must be
"Medications.xml".
Page 166/296 Version 06.02 • 2017-07-04

f) Creating user export:

Call the User Administration program and select the user you want to export.
Select the menu "User"->"Export" and enter a export file name. The file name must
be "User.xml".
g) Creating user group export

Call the User Administration program and select the user you want to export.
Select the menu "User group"->"Export" and enter a export file name. The file
name must be "UserGroup.xml".
h) Creating Predicted authors and modules export

Select the tab "Predicted data" select the authors and modules you want to export.
Enter the path and file name for each authors and/or modules export file. The file
name must be "Authors.xml" for predicted authors and "Modules.xml" for
predicted modules.
Version 06.02 • 2017-07-04 Page 167/296

i) Creating Questionnaire export:

Select the tab "Questionnaire" and select the questionnaires you want to export.
Enter the path and file name of the export file. The file name must be "Question-
naire.xml".
Auto start
Enter the CD into the CD-ROM slot of your computer. The upgrade process will start
automatically. If the process does not start automatically you can also double click on
the executable <SesAuto.exe> to start the process manually.
Notes
Creation and deployment of the country CD is a regulatory process and is described in
the quality management documents of CareFusion.
Page 168/296 Version 06.02 • 2017-07-04

2.5.3 Database Management

2.5.4 Patient Data Management

The following paragraphs require service login credentials, see paragraph 2.2,
"SentrySuite Desktop".
2.5.5 Remove Server Configuration

2.5.6 Server Configuration
2.5.7 Server Re-configuration
2.6 Configuration
2.6.1 GDT/HIS Settings
To access the HIS Settings, click on "Configuration" in the SentrySuite Desktop and
choose <GDT/HIS Settings>.
The first tab is for the HIS Settings:

Import
ADT - Import of patient demographics stored on the SentryConnect Gateway
Query - Import of patient demographics on demand via SentryConnect Gateway
ORD - Import of specific appointments for patients stored on the SentryConnect
Gateway
Version 06.02 • 2017-07-04 Page 169/296

Export
File - PDF/RTF Report stored as a File with reference link in HL7 message
SQL - PDF/RTF Report stored as a BLOB element in a Microsoft SQL Database
Mime/HEX - PDF/RTF Report stored Base64 encoded within the HL7 message
FTP - PDF/RTF Report stored as a File on a FTP server with reference link in
HL7 message
Advanced Options
Patient Read Block – amount of results per page when searching on SentryConnect
(default 500)
Parameter Suffix – default CARD
Allow generation of new patient – if activated, the user can manually create patients,
even if the clinic connection is active (default yes)
Connection Settings…
Spy Port - TCP Port of the SentryConnects SOAP Server for reporting
(default 702)
Query Port - TCP Port of the SentryConnects SOAP Server for query
(default 703)
Host IP - textfield to enter either SentryConnects IP address or hostname
Client Timeout - timeout for query in seconds
ADT Mapping…
Overview of the fields in SentrySuite and the corresponding fields in the
SentryConnect intermediate database, table patients.
Order Table Mapping…

Overview of the fields in SentrySuite and the corresponding fields in the
SentryConnect intermediate database, table orders.
Report XML Mapping…

Overview of the fields in SentrySuite and the corresponding exported XML tags on
SentryConnect.
Importing from HIS
ADT
When ADT is active, open the Search dialogue and activate the checkmark above the
Search button, “HIS Import”. When active, every search fill look up in the
intermediate database of SentryConnect.
The result list shows each record found with the following information:
• Identification
• Last Name
• First Name
• Date of Birth
• HIS Visit ID
• Referring Physician
• Social Security Number
Page 170/296 Version 06.02 • 2017-07-04

Valid fields for searching are

• Identification
• Last Name
• First Name
• HIS Visit ID
The fields can be combined for searching to provide more accurate results.
Query
When Query is active, open the Search dialogue and activate the checkmark above
the Search button, “HIS Import”. SentrySuite will request a single record of patient
demographics according to a unique patient identification number or visit
identification number.
Only these two fields will be available for searching. The result must be unique!
ORD
When ADT is active, open the Search dialogue and activate the checkmark above the
Search button, “HIS Import”. When active, every search fill look up in the
intermediate database of SentryConnect.
The result list shows each record found with the following information:
• Identification
• Last Name
• First Name
• Date of Birth
• Tests ordered
• Date of Visit
• Provider
• Date of Order
• HIS Order ID
• HIS Visit ID
• Referring Physician
• Social Security Number
Valid fields for searching are

• Identification
• Last Name
• First Name
• HIS Visit ID
• HIS Order ID
The fields can be combined for searching to give back more accurate results.
Version 06.02 • 2017-07-04 Page 171/296

Reporting to HIS
To report to the HIS, a report must be saved to a Visit. To do so, open the SentrySuite
Review. You can either create a report by marking a visit and choosing
“New Report” or by double clicking a test of a visit and creating/saving directly the
report from the measurement program.
When a report is marked, it can be send by pressing “Send Report”. After
sending it, the report will be flagged with the term “HIS”. It isn’t possible to delete
the report from the SentrySuite Review anymore. It can be resent by doing some
modifications. If a report has changed but was already sent, it is marked with the term
“must be sent to HIS again”.
HIS Reports have three different states

• Preliminary
• Final
• Corrected
These states can be filtered more by the current send status of the report
• All
• Changed (Not sent + Modified)
• Modified
• Not sent
• Sent
These filters can be used to specify the user specific workflow.
2.6.2 GDTSelect Utility
GDTSelect executable
By using the external tool GDTSelect, special tasks can be performed by a call from a
practice system. SentrySuite and the practice system need a SentrySuite Installation on
the same computer. The output is done based on the last visit.
GDTSelect selects a current patient with a given ID, selects the last visit as current visit
and starts a report. A user definable program can be started as well.
The practice system needs to be able to deliver the PatientID as a command line
variable to GDTSelect. Command line parameters are context sensitive. The following
command line parameters are possible.
Page 172/296 Version 06.02 • 2017-07-04

GDTSelect command lines

/P<patientid>
Output of patient data, report selection box is provided from SentrySuite.
/A<patientid>
Output of patient data (leading zeros are cut off, this is for numeric patient ID’s only!),
report selection box is provided from SentrySuite.
/D<patientid>
Output of patient data (the first 2 characters of patient ID is cut off), report selection
box is provided from SentrySuite
/R<reportname>
The report <reportname> is created, without showing a report selection box
/G<gdt-filename>
Data is acquired by utilizing the file <gdt-filename>. Location and file name are
retrieved from GDT settings (for more information, see paragraph 2.6.1).
Processing and subsequent calls are driven by the GDT file content (GDT id’s), for
example:
0158402Lufu02 -> search in GDTSelect.ini for program in Section [GDTPrograms]
LUFU02=Spir
F<bdt-filename>
Data is read in by utilizing the file <bdt-filename> (full pathname). The file needs to
have BDT.
/L<startprogramname>
User defineable program
GDTSelect ini file

INI file name=GDTSelect.ini
Location is the SentrySuite directory (normally C:\Program files\SentrySuite\..)
[GDTSelect]
Section which specify the report program name, which is the default for all report
concerning calls.
The Entry SeSReport is the default name for the report program "repout32.exe".
This must not be changed.
The entry Startprogramparameter can be used as standard parameter (report name)
for all processings where no id for report name is used. Otherwise ignore it.
Example:
[GDTSelect]
Startprogramname=SeSReport
Startprogramparameter=<Report name>
Version 06.02 • 2017-07-04 Page 173/296

[GDTReports]
This is a section which can contain definitions for report names. Depending on GDT
file information the report generation is called with the specific report template.
Example:
[GDTReports]
LUFU01=SPIR_FCV_POST
LUFU02=ROCC
[GDTPrograms]
Section which can start programs, depends on GDT file information
[GDTPrograms]
LUFU01=Spir.exe
LUFU02=Rocc.exe
Notes:
The given patient ID via the command line or file will remain as selected patient
and visit in the system until another patient is selected manually or automatically.
2.6.3 Global Settings

2.6.4 System Configuration
This section allows configuration of:
• Connectivity settings
• Global settings
• System configuration
2.6.4.1 Connectivity Settings

In this section, all SentrySuite’s HIS-, GDT- or SeS connection interface-settings are
configured.
For more information please contact Support.Connect.EU@CareFusion.com.
2.6.4.2 Global Settings

These settings apply to all SentrySuite programs & apps, including Language settings,
General measurement settings, Medication lists, Parameter Language properties,
Report settings, SQL query settings, Vmax-settings.
2.6.4.3 System Configuration

These settings allow you to (re-)configure your hardware- and software settings.
The SentrySuite configuration wizard is an automated configuration wizard which
allows you to reconfigure your software options (by re-entering a new license- and
validation-string), or change the hardware serial numbers of your devices.
For more information, see paragraph 1.2.5.3, "Initial Configuration".
Page 174/296 Version 06.02 • 2017-07-04

2.6.4.3.1 Configuration of a Failover System
In today’s network environments, configuration of a Failover System should

not be needed. First and foremost, networks are today reliable - if not, they
should be made reliable first. It is important that this should be the priority for all
professional environments.
Short network interruptions (some seconds) are normally covered by

SentrySuite also without configuration of a Failover System.
(See "Client System without Failover").
If an end-user insists on an emergency solution in case of network failure, a Sentry-

Suite client measurement station can be installed as an Emergency Failover system.
Please only install the Emergency Failover option on 1 or 2 system(s) in your network.
CareFusion does not recommend to use this options on all your networked client
systems!
Only a SentrySuite Client Measurement Systems can be configured as an

Failover System.
It makes no sense to install a Review station, Report station or any server system as
Failover system.
NOTE: Setting up a failover system may need up to 2 hours and more.
Customer should be informed about the disadvantages of a Failover Systems:

• Each start of the Desktop is delayed by some seconds to check current failover
state.
• Storage of data at a local system is not accepted in some environments.
• The local SQL Server installation adds complexity to the environment, potentially
slows down the system and costs additional maintenance.
• A failover system has an local SQL server installed and should not be powered
down without shutting down Microsoft Windows first, otherwise the local data-
base can be corrupted.
Installation process
The Failover system needs the activation of a Failover mode option (505). This option
is needed for each Failover system.
To enable a system for emergency failover, SentrySuite needs to be reinstalled

from scratch – before installation, all SentrySuite MS SQL instances need to be
removed from the system.
HOTFIX must be installed BEFORE ‘Convert …’ is run.
The configuration is done by starting the System Configuration from Desktop.

The menu item is only enabled if the Failover option is released.
NOTE: If you enter a new configuration code with Failover mode enabled and the
code before had NO failover mode enabled, then you potentially need to restart the
system configuration to enable the menu item.
Version 06.02 • 2017-07-04 Page 175/296

Select the “Convert to CIS Client System with Failover” to reconfigure the system:
Selection of “Start Reconfiguration” starts the SentrySuite installation in a special

reconfiguration mode. Just click through the dialogs. You don’t need to make any
change.
Page 176/296 Version 06.02 • 2017-07-04

This is the last Dialog where the Reconfiguration process can be canceled.
If you press “Cancel”, the system stays in a Client System without Failover.
If you press “Reconfigure”, the system is reconfigured to a Client System with
Failover. The Reconfiguration installs a local SQL Server and all needed files.
Reconfiguration process may take some minutes.
Version 06.02 • 2017-07-04 Page 177/296

Launch SentrySuite starts the initial system configuration. You don’t need to change
any setting during the configuration process.
Page 178/296 Version 06.02 • 2017-07-04

After closing the configuration, the local database is prepared for the usage in Emer-
gency mode. Depending on the original database size, this can last up to 1 hour and
more.
Log files for the Emergency failover setup and operation can be found in the
CisEmergency Failover subfolder of SentrySuite:
C:\Program Files (x86)\CareFusion\SentrySuite\CisEmergencyFailover\Logs
The system is now ready to run in failover mode when needed.
You can see that the system is configured as Failover System in the program’s toolbar.
Version 06.02 • 2017-07-04 Page 179/296

If you want to synchronize any data again, you can start this in the system
configuration program:
2.6.4.3.2 Configuration of a Failover System
A) What data is available in Emergency mode?
Data Available Not available/ Synchronization

Restrictions
System data, • Only default text • When Desktop is
texts, reports, language – not all started every 24
predicted languages hours
modules • Current lists of • With initial
patient fields synchronization
like operators,
physicians,
referring
physicians,
wards, diagnosis,
properties etc.
• Only default
predicted modules
Patient data Primary patient Other fields, Existing • When Desktop is
data (ID, name, visits, Existing started: Every 1
first name, measurements minute
Birthdate, height, • With initial
weight) only synchronization
Ambient and From current Older calibrations • When Ambient
Calibration workstation, last or ambient values, measurement
ambient data and Calibrations and or Calibration is
last calibrations ambient values from stored at local
only other systems system
• With initial
synchronization
Released From current • Configuration
software workstation change in system
options and configuration
hardware program
configuration • With initial
synchronization
Because existing visits and measurements are not available when switching from
Normal mode to Emergency Failover mode, only new visits with new levels and mea-
surements can be done. It is not possible to continue a measurement or a bronchial
challenge sequence in Emergency Failover Mode when measured in Normal Mode.
Page 180/296 Version 06.02 • 2017-07-04

B) What programs/functionalities are available in Emergency mode?
Data Available Not available/

Restrictions
Measurement Measurement Settings can’t be changed
programs programs are available. within measurement
Measurements can be programs.
done. Report lists can’t be
adapted.
Medication lists and units
can’t be changed.
Calibrations Calibrations can be done, Calibrations
Ambient
Bronchial Challenge From current workstation, Only default protocols are
measurement last ambient data and last available?
calibrations only. Report lists can’t be
adapted.
Settings can’t be changed.
Offline Data Entry Available Parameter lists can not be
changed,
Report lists can not be
adapted.
Bloodgas and Setting changes are not
Spirometry Data synchronized.
Transfer
User administration Not available
& logfile viewer,
Database handling
tools, export, import,
patient merge
Utilities like Report Not available
Designer, Predicted
Value Editor, CPET
Profile Editor,
Bronchial Cahllenge
Generation,
Interconnectivity
manager etc.
Review Not available
Version 06.02 • 2017-07-04 Page 181/296

C) Status description
Scenario Toolbar status Description Remark /

shows Known
issues
Normal mode – A normal connection to the server is shown in the
Connection to toolbar status window on top of each program.
Server available
Emergency mode You can work in Emergency mode as long as you

– Connection is want, also if the connection is back again. The toolbar
available again status is changed to “Available”. The normal mode is
started if you close SentrySuite and start SentrySuite
(Desktop) again.
Restarting During restart of the System from Failover Mode to

SentrySuite in work in Normal Mode again, the Splasher is shown.
Normal mode
again, after
Emergency mode
• Temporary stored files are restored to global

database.
• New patients, visits and measurements created in
Emergency Failover Mode are transferred to the
global database and deleted from local database.
• All needed data is synchronized again.
Connection Loosing the connection during measurement will cause Changes in

lost during no interruption of your workflow. the toolbar
measurement The measurement can be finished. status can
(Online mode in last 5-10
If the connection is available again when your
measurement seconds after
measurement is finished (after pressing F3 in the
program) loosing the
measurement program) then you will find almost
connection.
no changes in workflow compared to the normal,
connected mode.
If the connection is not available when your
measurement is finished then data is saved to a
temporary file. This temporary file will be automatically
restored to the server after the connection has been
restored.
If the connection is not available after saving data to
the temporary file, then the workflow for “Connection
lost during normal operation” will be activated (see
below).
Page 182/296 Version 06.02 • 2017-07-04

Scenario Toolbar status Description Remark /

shows Known issues
Connection lost A message box appears (see Figure 1 below). There can be
during normal You don’t need to take any action. If the some seconds
operation connection is established again, the dialog is between
automatically closed and all temporary saved data activation of the
is restored at this point. toolbar status and
the appearance of
If you expect that the interruption needs more
the message box.
time, than you can decide to close SentrySuite and
start later on when the issue is solved. In this case
the temporary data is restored when the system is It is possible that
able to start with a normal connection. there are some
You can also decide to restart the system in information
Emergency mode. messages shown
in windows when
the connection is
lost.
These messages
are caused by
processes which
work in parallel
to the application
and can be
ignored.
Connection not If the server connection is not available when
available when the SentrySuite Desktop is started the following
Desktop is started message box appears:
After pressing <OK>, SentrySuite is started in

Emergency Mode.
Figure 1
Version 06.02 • 2017-07-04 Page 183/296

2.6.4.4 Turn On/Off Hardware Modules
2.6.4.5 Change Serial Number of your Hardware Devices

Serial number of hardware devices can only be changed after the system has had an
initial valid configuration!
2.6.4.6 Change Port Number of Devices
2.6.4.7 Test Hardware Devices
2.6.4.8 Peripheral Devices Information
General remarks:
For combining different medical devices, at least in Europe an "Article 12 declara-
tion" is needed. This exists for all devices which we are selling together or as an
option to Vyntus CPX, however, it does not (yet) exist for a lot of other peripheral
devices, even if we have the communication driver available in our software.
If you combine such systems without an Article 12 declaration, you become the
manufacturer and you take over full responsibility for the whole medical system!
General remark to this paragraph:

This paragraph describes the different drivers and adaptations for peripheral devices
together with SentrySuite.
As we do not have all devices available, not all systems can be tested completely, and
there may be other devices as well which are compatible with one of the existing
drivers.
Therefore, any additional information, comment or suggestion to this paragraph is
highly appreciated and welcome.
Please send your feedback to Support.RT.EU.JAE@CareFusion.com.
Thanks for your support!
Page 184/296 Version 06.02 • 2017-07-04

2.6.4.8.1 Overview of Available Drivers for Peripherals
SeS V 2.15 Article tested tested tested

Devices Driver Name Compatible with 12 ≤V2.13 V 2.15 V 2.17 Note 1 Note 2
Bikes
Demo Bike -- -- ok ok ok see Demo Bike
ER 800 ER 800 Yes ?? ?? ??
Technogym Excite Bike Med No ?? ?? ?? Emulate ER 800
Monark 939E No ?? ?? ?? Emulate ER 800
Monark 839E No ?? ?? ?? No Medical Emulate ER 800
Device!
ER 900 ER 900 Yes ok ok* ok ER 900
Viasprint 150P Yes ok ok* ok ER 900
Viasprint 200P Yes ok ok* ok ER 900
Ergotop 100 P / 200 P ?? ?? ?? ?? From MedSet Identical to
Ergoline
Lode Excalibur ?? ok ok* ok* Emulate ER 900
Lode xxx ?? ?? ?? ?? Emulate ER 900
Cyclus 2 ?? ?? ?? ?? Emulate ER 800
Not possible
Monark 894E -- -- -- -- -- No Medical No remote
Device! control!
Note: "ok*" means that we did not re-test the device as there was no change in the software in this respect.
Version 06.02 • 2017-07-04 Page 185/296


Treadmills
Demo -- -- ok ok ok see
Treadmill Demo Treadmill
TrackMaster T 425 No ok ok* ok*
T 428 No ok ok* ok*
Technogym Excite Run Med No ?? ?? ?? Emulate
TrackMaster
Lode Valiant TM No ?? ?? ?? Emulate
TrackMaster
Ergotop TM No ok ok* ok* From MedSet This is a Lode TM
Emulater
TrackMaster
H-P-COSMOS CFN LE 200 No ok ok* No Obsolete!! Not CosCom V2
CosCom V2 available anymore (don't use)
(obsolete) since SeS V2.17
H-P-Cosmos XXX No ?? ?? No Obsolete!! Not CosCom V2
available anymore (don't use)
since SeS V2.17
H-P-COSMOS CFN LE 200 Yes ok ok* ok CosCom V3
CosCom V3
H-P-Cosmos XXX Yes ?? ?? ?? CosCom V3
Woodway Woodway PPS-XXX No -- ok ok Woodway
Not possible
Woodway -- -- -- -- -- -- No Medical No "standard"
ProXL Device! driver!
Important Note:
To control any of the above mentioned treadmills, from SeS 2.17 onwards the
drivers for these treadmills are not delivered standardly with the system.
This is an option now and must be ordered explicitly, even this option will be free
of charge. The release is then done via the configuration string.

SpO2
Nonin 7500 Nonin 7500 No ok ok* ok see Nonin 7500
Nonin 8600 No ?? ok ok see Nonin 8600
BCI 3304 BCI 3304 No ok ok* ok* see BCI 3304
Not possible
Page 186/296 Version 06.02 • 2017-07-04


Blood pressure
Suntech Tango Tango No ok ok* ok* Suntech Tango
Tango Plus No ok ok* ok* Suntech Tango
Plus
Tango M2 No ok ok* ok Suntech Tango
M2
Not possible

HR monitor
Polar WearLink -- No ok ok* ok* WearLink
(V 2.0) installation
Not possible
Version 06.02 • 2017-07-04 Page 187/296

2.6.4.8.2 Ergometers
A) ER 900, Viasprint 150 P, Viasprint 200 P

Please note: For a correct initialization, these bikes need a "Start Blood pressure mea-
surement" command at the beginning.
This command was skipped in V 2.13, which has the consequence that
1. The ER 900 is not started at all.
2 The Viasprint is started, but the blood pressure measurement from a
previous measurement is not cleared.
This problem is solved in SeS V 2.15; for SeS 2.13 please create a BP-event at the be-
ginning of the Resting Phase or start the BP-measurement manually via SeS (F6).
B) Demo Bike
This driver should be selected if no direct communication with a bike is possible:
As SentrySuite always shows and records the actual load (and RPM) from the
ergometer, there will be no load in SeS. As a result, it will not be displayed in the
graphs, tables or reports. The demo-driver uses the selected profile, simulates an out-
put and reads the “output”.
This has the advantage that the “actual load” is available as well. That means, if you
want to run any profile on your bike, just generate the same in SeS via the profile
editor and use this together with the “Demo-driver”.
In this case, the system will always show you BxB the “actual” load during the
measurement. (Of course, you need to synchronize the bike and SeS during the
measurement).
C) Technogym Excite Bike Med

1. Cable: Supplied as standard with Excite Med products (0WCU012AA)
2. How to emulate the ER 800 driver:
In the machine config. Menu (pwd 2406) you can select communication protocols
for external medical devices. This function allows you to set the correct communica-
tion protocol to connect the machine to different medical devices as electrocardio-
graphs or metabographs, used for tests or medical exams. To change the selection,
when the LED matrix shows the current setting:
EXT.xxx
Press the <+/- GOAL> keys to select the desired option out of those listed in the table
below:
Communication Protocol
CSAFE <default>
MARQUETTE
TRACKMASTER
Press <ENTER> to confirm the selection, use the <+> or <-> speed keys to move to
the next or previous parameter.
Procedure to start Run Med by ECG, once the correct cable has been chosen:
a. Switch on the Run Med.
b. Set up and connect the ECG to the Run by proper cable.
c. Press 4 button on the treadmill.
d. Start ECG.
Page 188/296 Version 06.02 • 2017-07-04

D) Lode Excalibur
1. Cable: Standardly supplied with the bike (Lode no. 930911).
a. Connect the RS 232 cable and switch on the bike.
b. The Excalibur initial screen is displayed.
I. Press the Enter button to open the Main Menu.
II. Use the Down/Up arrow keys to change the selection to
“SYSTEM PARAMETER”, then press <Enter>.
III. Use the Down/Up arrow keys to change the selection to
“SETTINGS”, then press <ENTER>.
IV. Use the Down/Up arrow keys to change the selection to
“DEFAULT START MENU”, then press <Enter>.
V. Use the Down/Up arrow keys to change the selection to
“TERMINAL”, press the <Enter> button and select “Yes” at the
Save menu.
VI. Use the Down/Up arrow keys to change the selection to
“RS232 PROTOCOL”, then press <Enter>.
VII. Use the Down/Up arrow keys to change the selection to
“Ergoline P10”, then press Enter and select "YES" at the
Save menu.
VIII.To return to the Main Menu, press and hold the <Enter> button
until it appears.
Additional details can be found in the eService DVD.
E) Lode xxx
1. Cable: Standardly supplied with the bike (Lode no. 930911).
See description above (Lode Excalibur).
F) Cyclus 2
1. Cable: Standard cable (female - female - crossed) - delivered with the
bike.
2. Install and test the ER 800 driver.
3. Note: Before each CPET-measurement, you need to perform "connect" on the
bike:
Version 06.02 • 2017-07-04 Page 189/296

G) Monark 939 E
1. Cable: To connect a PC to the ergometer, use a 0-modem cable (RS232)

with a 9-pin D-sub female at each end. If no RS232 Serial port is
available on the computer.
Connection to an external unit e.g. ECG device:
First check the brake belt tension. If the belt is too tight, loosen it a little by moving
the force indicator to about 4 kp and hold it there for a few seconds. Then the
force-adjusting servo will loosen the belt tension. To be sure that indicator positions
are correct, do a calibration.
a. Press the switch <2> to turn off the power (see picture "Connections").
Disconnect the cable from any connected external device.
b. Adjust the scale mechanically so that 0-index on the scale and indicator are
in line.
c. Move the indicator to 6 kp and hold it there.
d. Turn on the power again. (The green LED on the lower left side of the bike is
lit up when there is power to the bike (see picture "LED").)
e. Hold the indicator at 6 kp until two beeps are heard.
f. Move the pendulum pointer to
0 = mode for use with PC or hand unit
1 = mode for Siemens Megacart ECG
2 = mode for other ECG devices, alt. 1
3 = mode for other ECG devices, alt. 2
g. Keep at the selected position until two signals can be heard. Then release the
pointer to 0. The system will now restart in the selected mode.
h. Reconnect the correct cable between the external device (ECG Siemens
Megacart requires a special cable) and the bike.
i. The bike is now controlled digitally from the external device.
These settings can also be applied using the PC or the terminal. Follow the instructions
described in the respective manuals.
Reset the Ergometer to use with terminal/PC. Follow the points 1-7.
At point 7, press <0> and then <ENTER>. The Ergometer can now be controlled
again from the terminal or an external PC.
Alt. 1: ECG, Ergoline compatible command set, requested load value

Alt. 2: ECG, Ergoline compatible command set, current load value
Page 190/296 Version 06.02 • 2017-07-04

H) Monark 839 E
This is not a medical device!
1. Cable: To connect a PC to the ergometer, use a null-modem RS232

cable with a 9-pin D-sub female at each end. If no RS232 Serial
port is available on the computer.
Connection to controller:
a. Setting command type (PC or ECG device)

First check the brake belt tension. If the belt is too tight, loosen it a little by
moving the force indicator to about 4 kp and hold it there for a few seconds.
Then the force-adjusting servo will loosen the belt tension. To be sure that
indicator positions are correct, perform a calibration.
I. Turn off the power by turning th power switch (2) (see picture
"Connection"). Disconnect the cable from any connected external device.
II. Adjust the scale mechanically so that 0-index on the scale and indicator are
in line.
III. Move the indicator to 6 kp and hold it there.
IV. Turn on the power again. The green LED (3) is lit when power is connected
to the bike.
V. Hold the indicator at 6kp until two beeps are heard.
VI. Move the pendulum pointer to
0 = mode for use with PC or handheld controller
1 = mode for Siemens Megacart ECG
2 = mode for ECG, Ergoline compatible command set, requested load
3 = mode for ECG, Ergoline compatible command set, current load value
VII. Keep at the selected position until two signals can be heard. Then release
the pointer to 0. The system will now restart in the selected mode.
b. What command type is set?

When power is turned on to the bike it will beep, and from the number of
beeps the command type can be determined.
• Command type 0: A long beep
• Command type 1: A long beep followed by a short beep
• Command type 2: A long beep followed by two short beeps
• Command type 3: A long beep followed by three short beeps
c. Procedure when connecting to the handheld controller:

When using a terminal (Art. No: 9339-51), proceed as follows:
I. Connect the handheld controller to the bike using the enclosed cable.
II. Connect power to the bike.
III. When the main menu is displayed on the LCD screen, press "99" and the
hidden service menu appears.
IV. Press 6, "settings".
Version 06.02 • 2017-07-04 Page 191/296

V. Press <ENTER> (normally 13 times) until the display "Command type"

appears:
• Press <1> and <ENTER> if the bike is connected to a Siemens

Megacart ECG device.
•. Press <2> and <ENTER> if the bike is connected to a Siemens
Megacart ECG device, alt. 1.
• Press <3> and <ENTER> if the bike is connected to a Siemens
Megacart ECG device, alt. 2.
• Press <0> if the bike is connected to a PC or a handheld controller
VI. After that, press <0> twice to return to the main menu.
2.6.4.8.3 Treadmills
A) Demo treadmill
This driver should be selected if no direct communication with a treadmill is possible.
As SentrySuite always records and shows the actual speed, elevation (and the
calculated load accordingly), there will be no speed, elevation or load in SeS. As a re-
sult, it will not be displayed in the graphs, tables or reports. The demo-driver uses the
selected profile, simulates an output and reads the “output”.
This has the advantage that the “actual speed, elevation and calculated load”
is available as well. That means, if you want to run any profile on your treadmill, just
generate the same in SeS via the profile editor and use this together with the
“Demo-driver”.
In this case, the system always will show you BxB the “actual” speed, elevation and
load during the measurement. (Of course, you need to synchronize the treadmill and
SeS during the measurement).
Page 192/296 Version 06.02 • 2017-07-04

B) Technogym Excite Run Med

1. Cable: Standardly supplied with Excite Med products (0WCU012AA).
2. How to emulate the Trackmaster driver:
In the machine config. Menu (pwd 2406) you can select communication protocols
for external medical devices. This function allows to set the proper communication
protocol to connect the machine to different medical devices as electrocardiographs
or metabographs, used for tests or medical exams. To change the selection, when the
LED matrix shows the current setting:
EXT.xxx
Press the <+/- GOAL> keys to select the desired option out of those listed in the table
below:
Communication Protocol
CSAFE <default>
MARQUETTE
TRACKMASTER
Press <ENTER> to confirm the selection, use the <+> or <-> speed keys to move to
the next or previous parameter.
Procedure to start Run Med by ECG, once the correct cable has been chosen:
a. Switch on the Run Med.
b. Set up and connect the ECG to the Run by proper cable.
c. Press 4 button on the treadmill.
d. Start ECG.
Version 06.02 • 2017-07-04 Page 193/296

C) HP CosCom V2
The HP CosCom V2 driver is obsolete and not allowed for medical devices
anymore!
If the treadmill does not support the CosCom V3 driver, please update your treadmill
firmware.
To configure the HP CosCom, see "D) HP CosCom V3":
D) HP CosCom V3
1. Cable: Standardly supplied with the treadmill (CFN no. 982019).

2. How to configure the treadmill:
To start the HP CosCom configuration:
Select user options

Initation: Running belt is not moving. One of the modes LED is flashing: (manual,
profile, cardio, test).
Page 194/296 Version 06.02 • 2017-07-04

Version 06.02 • 2017-07-04 Page 195/296

E) Woodway
Woodway has two different types of treadmills:

• The PPS-series: these are medical devices and can be controlled via "Track-
master emulation"
• The ProXL-series: These are non-medical devices and have a different (un-
known) communication. Therefore, they cannot be connected to SentrySuite /
Vyntus CPX.
1. Cable: Supplied as standard with the treadmill (no. ??? ???).

2. Note: Woodway can emulate the Trackmaster protocol, but this seems not to
work.
Important:
During the installation, the communication (reaction and timeout) is checked. This
timeout may vary from check to check due to the treadmill reaction. Therefore,
please check it several times and take the highest timeout time.
The last time will be stored and used for emergency check!
2.6.4.8.4 Serial SpO2
A) Nonin 7500
Important:
Nonin needs a special RS 232-cable.
There is a small converter in the cable!
The cable can be ordered via Nonin:
Interface cable Model 7500 SC; part no. 5994-001.
Nonin has to be set to “Memory Playback/Output mode” (=default setting for a
new device).
B) Nonin 8600
This system is not tested yet!
Important:
Nonin needs a special RS 232-cable.
There is a small converter in the cable!
The cable can be ordered via Nonin:
Interface cable Model 1000PFC for 8600; part no. 3258-000.
C) BCI 3304
No details yet.
Page 196/296 Version 06.02 • 2017-07-04

2.6.4.8.5 Blood Pressure
A) Suntech Tango
See paragraph C),"Suntech Tango M2".
B) Suntech Tango Plus

See paragraph C),"Suntech Tango M2".
C) Suntech Tango M2
1. PC-Connection cable:
a. Standard RS 232 cable: 9 pin female-female
(SunTech part no.: 91-0013-00 or CFN part no.: 918263).
CFN SunTech
b. Alternatively, you can use a USB-cable:

CFN part no.: XXXXXX.
2. ECG-cable:
The SunTech Tango M2 needs an ECG cable (3 leads) that will provide the ECG
signal from the patient to the Tango M2 (or any other ECG-trigger signal if avail-
able from an ECG).
a. ECG-cable: SunTech part no.: 91-0004-00 or CFN part no.: 982113.
Version 06.02 • 2017-07-04 Page 197/296

3. SunTech connections:

USB ECG
or patient
RS 232 cable
4. Setup:
1. Connect the Suntech Tango M2 to the PC (via USB or RS 232).
2. Connect the patient cable
• From: Tango M2 Internal ECG connection
• To: the patient.
5. Configure the Suntech Tango M2:

a. When the measurement view screen is displayed, press the <SELECT> button
once. This will bring up the "MAIN MENU" screen.
b. Using the "UP" or "DOWN" arrows, highlight "MONITOR SET UP"
and press the <SELECT> button.
c. Using the "UP" or "DOWN" arrows, highlight "STRESS SYSTEM"
and press the <SELECT> button.
d. Using the "UP" or "DOWN" arrows, scroll through the list until
"CUSTOM" is highlighted and press the <SELECT> button to confirm the
choice.
e. With Protocol highlighted, press the <SELECT> button.
f. Using the "UP" or "DOWN" arrows, scroll through the list until "SUNTECH"
is highlighted and press the <SELECT> button to confirm the choice.
g. Press the "DOWN" arrow to highlight "ECG Trigger", and press the
<SELECT> button.
h. Using the "UP" or "DOWN" arrows, scroll though the list until "INTERNAL" is
highlighted and press the <SELECT> button to confirm the choice.
i. Using the "UP" or "DOWN" arrows, select "EXIT" twice to return to the
operating screen.
Page 198/296 Version 06.02 • 2017-07-04

2.6.4.8.6 Blood Pressure
A) Polar WearLink
See C), "Polar WearLink".
2.6.4.8.7 How to setup the Bluetooth connections
Make sure that the Bluetooth receiver is activated (or insert the Bluetooth USB-stick)
and the Bluetooth icon is visible in the toolbar or at least in the hidden icon field.
Do not install the driver delivered with the Bluetooth receiver CD!
A) If the Bluetooth icon is not shown in the taskbar

1. Select "Start" and enter "Bluetooth" in the search field.
2. Select "Change Bluetooth settings".

3. Activate "Show Bluetooth icon...".
Version 06.02 • 2017-07-04 Page 199/296

B) Vyntus ECG
1. Insert the Bluetooth receiver into the PC.
Do not install the driver delivered with the Bluetooth

receiver CD!
2. Open the Bluetooth menu via the Bluetooth icon (or from taskbar).
(If no Bluetooth icon available, see previous chapter "A) If the Bluetooth icon is not
shown in the taskbar").
3. Push the ECG button at least 3 seconds until the blue LED is blinking "fast":
The ECG must be in the "fast blinking mode" during

the installation. There is a timeout after 1 min and the
ECG will switch off.
4. Select "Add a device".
Page 200/296 Version 06.02 • 2017-07-04

5. Select the Vyntus ECG and press <Next>.
6. Select "Enter...pairint code".

(Note: Bluetooth version ≥ V 2.1 does not need the pairing code anymore.)
7. Enter the pairing code "0000" and press <Next>.

(Note: Bluetooth version ≥ V 2.1 does not need the pairing code anymore.)
Version 06.02 • 2017-07-04 Page 201/296

8. Now, the system is installing the drivers. If successful, press <Close>.
9. Now wait until the clock disappears.
Installing: Finished:
10. Select the Vyntus ECG via right mouse click and select the Hardware tab.
Page 202/296 Version 06.02 • 2017-07-04

11. Note the COM selection (here: COM 9). You may need to select the COM during
the system configuration.
12. Done.
C) Polar Wearlink
1. Insert the Bluetooth receiver into the PC.
Do not install the driver delivered with the Bluetooth

receiver CD!
2. For the setup, you need to put the Polar Belt onto a subject.
3. Open the Bluetooth menu via the Bluetooth icon (or from taskbar).
(If no Bluetooth icon available, see chapter "A) If the Bluetooth icon is not shown
in the taskbar").
4. Select "Add a device".
Version 06.02 • 2017-07-04 Page 203/296

5. Select the Polar iWL and press <Next>.
6. Select "Enter...pairing code".
7. Enter the pairing code "0000" and press <Next>.
Page 204/296 Version 06.02 • 2017-07-04

8. Now the system is installing the drivers. If successful, press <Close>.
9. Wait until the clock disappears.
Installing: Finished:
Version 06.02 • 2017-07-04 Page 205/296

10. Select the Polar iWL properties via the right mouse button and select
the Hardware tab.
11. Note the COM selection (here: COM 7).

You may need to select the COM during the system configuration.
12. Done.
Page 206/296 Version 06.02 • 2017-07-04

2.7 Utilities
2.7.1 Interconnectivity Manager
Intended Use
The intended use of this section is to describe the usage of the SentrySuite
Interconnectivity Manager. The interconnectivity manager is a SentrySuite utility to
set the settings which are needed to enable the connection to a legacy software/
database of JLAB, Vmax, MGC and nSpire.
CareFusion highly recommends that only trained personnel use this section.
The following use cases are described in the following paragraphs.
- Bulk transfer of patients with measurements
- Enable mixed network functionality
Start the Connectivity Manager

The interconnectivity manager can be started from the SentrySuite desktop
application by selecting "utilities" and then "Interconnectivity Manager".
Bulk Transfer of Patients with Measurements

This process can be used to transport measured data from the legacy system to
SentrySuite or upgrade/replace a legacy system with SentrySuite. In the end all
scenarios use the same technical implementation to convert the legacy data into the
SentrySuite database.
1
SentrySuite
Connectivity
Manager
3 2
SentrySuite Legacy
Database Database
Version 06.02 • 2017-07-04 Page 207/296

General conversion settings

The patient and visit data can be converted in 2 different ways. First possibility is the
conversion of new patients and visits only. Second is that every conversion will
overwrite the complete patient and visit data. It is necessary to understand that when
calling the conversion of a patient twice this behavior has an important impact on the
data of the patient and visit. The setting can be adjusted only by editing the following
ini-file:
VasBase.ini
[Conversion]
Update=2
1=only new data, 2=overwrite data (=default)
This setting has no effect on measurement and level data. This kind of data will
always overwrite the existing data on the SentrySuite side when transferred.
Settings for connectivity with JLAB

For the simple upgrade of JLAB data the complete JLAB software is not required.
To establish the connection to the JLAB database the database files must be available
(for example via network). The libraries needed for connecting and reading data are
provided by the SentrySuite installation. The following steps must be taken to enable
the access to the JLAB database.
Select the data source in the "Settings" tab.
Enter a path to the database files of JLAB.
Click on <Apply> to store the changes. The check box "Enable mixed network" is
not needed for the bulk transfer, so do not check it.
Page 208/296 Version 06.02 • 2017-07-04

Special JLab – SentrySuite mapping of data fields

There are some fields in the JLab database which are used by customers for different
purposes. These fields can now be mapped to the Patient and Visit free property fields
1-15.
List of JLab attributes which can be mapped:
JLAB Field name (JLAB 5.71) User mapping name (VasBase.ini) Default mapping to SeS field
Patient Insurance JLab_Right_2 Insurance
Insurance No
Patient Street JLab_Left_1 Street
Patient City JLab_Left_2 City
Patient Phone JLab_Left_3 Phone
Patient Free JLab_Left_4 Property 1
Patient Profession JLab_Left_5 Profession
Patient import information (HIS/GDT) n.a. Property 4
Patient import information (HIS/GDT) n.a. Property 5
Patient Birth name BirthName
Patient SSN/BSN SSN
Test 0 -> Patient current settings, Test 1 - x -> Visit
Test Diagnosis JLab_Left_6 Diagnosis
Test Patient History JLab_Left_7 Patient History
Test Smoker JLab_Left_8 Patient History
Test Operator JLab_Right_4 Operator
Test Ward JLab_Right_5 Ward
Test Physician JLab_Right_6 Physician
Test Ref. Physician JLab_Right_7 Ref. Physician
MLDATA Occup. Exposure JLab_Left_9 Occupational Exposure
MLDATA Diagnosis 2 JLab_Left_10 Property 7
MLDATA Free Text JLab_Left_11 Property 8
MLDATA Medication1 JLab_Left_12 Medication
MLDATA Medication2 JLab_Right_8 Medication
MLDATA Visit ID not configurable HIS Visit ID
MLDATA Order ID not configurable HIS Order ID
Mapping table of JLab fields with mapping names corresponding the position within the patient mask (see below) and the default
SentrySuite field.
Version 06.02 • 2017-07-04 Page 209/296

Overview of the JLab patient mask with all attributes and description of the
mapping name:
JLab patient and test0 dialog. Magenta fields are copied to each new test.
Page 210/296 Version 06.02 • 2017-07-04

The setting for this mapping can be adjusted only by editing the following ini file.
As usual the attributes of a “patient” and/or “test0 record” are mapped to the
patient free fields 1-15. Attributes of the “JLab test 1-xx” are mapped to the
corresponding SentrySuite visit free fields 1-15.
There are some free fields which are already used in the default mapping. These free
fields must not be used for variable mapping of other fields and are not available in
the mapping section, see ini description below. Please pay attention to use the exact
wording, case sensitive!
The mapping must be enabled by setting the entry UseJLabSeSMapping=1.
VasBase.ini
[JLabConversion]
UseJLABSeSMapping=1 activate this to enable or disable the special JLab
;SeS_Free1=JLab_Left_4 do not use! -> is used by default mapping
SeS_Free2=
SeS_Free3=
;SeS_Free4= do not use! -> is used by default mapping
;SeS_Free5= do not use! -> is used by default mapping
SeS_Free6=
SeS_Free9=
SeS_Free10=JLab_Right_8 map Medication 2 to SeS free field property no 10
SeS_Free14=
SeS_Free15=
If a mapping is used twice, there will be no error or warning! The last mapping will
overwrite previous mapping. If a mapping is changed and patients are imported again
the original SentrySuite Free 1-10 fields will not be erased.
Conversion of JLab questionnaires

Normally the JLab questionnaires are flagged as deleted during the conversion of the
questionnaires. For testing purposes, a special flag exists in the VasBase.ini file which
triggers the questionnaires to be visible in the SentrySuite questionnaire designer.
[JLabConversion]
AllowQuestionnaireUsable=1
This setting must be set before transferring questionnaires to SentrySuite. Already

transferred questionnaires are not saved again unless there are changes within the
questionnaire.
Attention:
Changes in the questionnaire either on JLAB or on SentrySuite side may corrupt
the structure of the questionnaire which leads to wrong question – answer
connections and wrong results. Textual changes which do not change the
meaning are allowed. If you need to change a questionnaire take care that you
only add new questions at the end of the questionnaire.
Version 06.02 • 2017-07-04 Page 211/296

Settings for connectivity with Vmax

To transfer patients from a VMAX system, a connection must be established to a
remote computer within the network which contains the DBx connectivity solution.
See documentation of enabling the connectivity with SentrySuite within a VMAX
system in the VMAX technical documents.
The following steps must be taken to enable access to the DBx connectivity solution.
Select the data source in the "Settings" tab.
In the box “Connection Settings” press the button <Configure...>.
In the dialog “SeSConnect Connection Settings” enter name/IP address and the
port number of the computer which contains the DBx connectivity solution. If the DBx
connectivity solution is on the same computer as the SentrySuite, use ‘localhost’ as
computer name. The default port number is "8000".
Click <OK> to store the changes.

The check box <Enable mixed network> is not needed for the bulk transfer, so do
not check it.
Please note:
The same connection is used for connectivity with Vmax, MGC and nSpire.
Page 212/296 Version 06.02 • 2017-07-04

Special VMAX – SentrySuite mapping of data fields

There are some special fields in the VMAX database which can be used for different
purposes. The fields are normally for additional patient ID’s or information.
The VMAX fields are:
ID_1, ID_2, ID_3, ID_4, ID_5 ID_6.
The setting can be adjusted only by editing the following ini file. The mapping must
be enabled by setting the entry UseVmaxSeSMapping = 1.
VasBase.ini
[Conversion]
UseVmaxSeSMapping =1 enable/Disable the usage of the following mapping
SeS_Free1=ID_1 map ID_1 to SentrySuite Free 1 field
SeS_Free4=
SeS_Free5=
SeS_Free6=
SeS_Free7=
SeS_Free9=
SeS_Free10
SeS_Free11
SeS_Free12
SeS_Free13
SeS_Free14
SeS_Free15
SeS_HISVisitID=ID_4 map ID_4 to SentrySuite HIS visit ID
SeS_HISOrderID= map one of ID1-ID6 to SentrySuite order id if
UseOrderIDFromHL7 is not applicable.
UseOrderIDFromHL7=1 map the order id from HL7 information record to the
SentrySuite HIS Order ID field. By default this is not
mapped.
If a mapping is used twice, there will be no error or warning! The last mapping will
overwrite previous mappings. If a mapping is changed and patients are imported
again the original SentrySuite Free 1-10 fields will not be erased. If both SeS_HISOrde-
rID and UseOrderIDFromHL7 are set the SeS_HISOrderID will win.
New field “HIS visit information” – this field is only available via patient report
module! There is no editable field in the patient dialog up to now.
Settings for connectivity with MGC

To transfer patients from a MGC database, a connection must be established to a
See documentation of enabling the connectivity with SentrySuite within a
MGC database in the Dbx connectivity technical documents.
To enable the access to the DBx connectivity solution see paragraph “Settings for
connectivity with Vmax”.
Please note:
Version 06.02 • 2017-07-04 Page 213/296

Settings for connectivity with nSpire

To transfer patients from a nSpire database a connection must be established to a
See documentation of enabling the connectivity with SentrySuite within a nSpire
database in the Dbx connectivity technical documents.
To enable the access to the DBx connectivity solution see paragraph “Settings for
connectivity with Vmax”.
Please note:
Transfer of data
Switch to the "Data Transfer" tab. Select the data source you want to use.
Additionally you have the possibility to set a date range. Only patients which have
tests within this date range are searched.
Click on <Search> to start searching. It is strongly recommended to use a date range
for large databases. Otherwise, the list and the time to build it will get very long. After
the list of patients is shown, select the patients you want to transfer.
Click on <Check all> if you want to transfer all found patients.
Click on <Start data transfer> to start the bulk transfer. When the transfer is
finished, a result list is shown.
Page 214/296 Version 06.02 • 2017-07-04

Enable Mixed Network Functionality

Enable mixed network functionality for Vmax, MGC and nSpire
To enable the mixed network functionality, switch to the "Settings" tab and press
the button <Configure...> in the box “Connection Settings”.
In the dialog “SeSConnect Connection Settings” check the box <Enable mixed
network>.
The mixed network functionality uses the same connection settings as the bulk
transfer.
The port of the SentrySuite database adapter can be set additionally on the "Set-
tings" tab. The default setting is “Auto”.
After clicking on <Apply>, the Interconnectivity Manager starts the necessary
Windows service to communicate with the legacy data providers.
Please note:
The SeS Connectivity service is used for connectivity with Vmax, MGC and nSpire.
Version 06.02 • 2017-07-04 Page 215/296

Enable mixed network functionality for JLAB

To enable the mixed network functionality, switch to the "Settings" tab and check
the <Enable mixed network button>.
The mixed network functionality uses the same settings a the bulk transfer for
JLAB data.
If the database is located on a network drive then a drive letter cannot be used in the
database path on the "Settings" tab. Instead you have to use an UNC path,
i.e. "\\servername\path".
The port of the SentrySuite database adapter for JLAB can be set additionally on the
"Settings" tab. The default setting is “8090”.
After clicking on <Apply> the Interconnectivity Manager starts the necessary

Windows service to communicate with the legacy data providers.
If the database is located on a network drive the SeS JLab Connectivity service has to
be allowed to access the network drive. There are two possibilities:
- Log on as a Windows user at the computer on which the SeS JLab Connectivity
service is running
- Run the SeS JLab Connectivity service as a different Windows account
In both cases the used Windows account must have mapped the network drive in
Windows. If the Windows account is not an Administrator you additionally have
to grant permissions to this Windows account for the URL namespace of the SeS
JLab Connectivity service otherwise the service will not run. To do this a Windows
Administrator has to run the program “SesConServiceCfgAcl.exe” with the
command line parameter “jlab”. The program can be found in the SentrySuite
program folder. In the field “URL” the same port number has to be used which
is entered in the field “Database Adapter” on the JLAB Settings page of the
Connectivity Manager.
Page 216/296 Version 06.02 • 2017-07-04

Log on as a Windows user at the computer on which the SeS JLab

Connectivity service is running
- On the Windows logon screen enter the username and the password of a Windows
account that has access to the network drive on which the JLAB database is located.
- After logging on in Windows the Ses JLab Connectivity service will automatically use
the currently logged-on Windows user to access the network drive on which the
JLAB database is located.
Run the SeS JLab Connectivity service as a different Windows account

- Open <Control Panel>, <Administrative Tools>, <Services>.
- Select the service “SeS JLab Connectivity Service” and right-click on it. Select
“Properties” from the context menu.
- In the window “SeS JLab Connectivity Service Properties (Local Computer)”
select the tab “Log On”. Select the option “This account” and enter the username
and the password of a Windows account that has access to the network drive on
which the JLAB database is located.
Version 06.02 • 2017-07-04 Page 217/296

- Press button <Apply> to confirm changes.

Confirm the following message box with <OK>:
- In the window “SeS JLab Connectivity Service Properties (Local Computer)”,

select the tab “General” to restart the service. Press the button <Stop> to stop the
service. After the service has been stopped, press the button <Start> to start the
service with the new logon account.
Page 218/296 Version 06.02 • 2017-07-04

- Press the button <OK> to close the window “SeS JLab Connectivity Service
Properties (Local Computer)”.
CPET Settings for Data Transfer

For data transfer of CPET data, the following settings can be made on the
"Settings" tab:
Version 06.02 • 2017-07-04 Page 219/296

AT determined as
either first threshold (Wasserman AT): data è AE
or second threshold (Wasserman RCP): data è AT
If AT is determined as first threshold, then additionally for RCP:

RCP determined as
either second threshold (Wasserman RCP): data è AT
or third threshold (International RCP): data è RCP
If AT is determined as second threshold, then:

RCP determined as third threshold (International RCP): data è RCP
Logging
You can show special log files via the menu:
By default, only errors will be logged in the files.
To log additional information in the files the log level can be set to one of the
following values:
10 log only errors
20 log errors and warnings
30 log errors, warnings and informational messages
The setting for the log level can be adjusted only by editing the following ini file:
VasBase.ini
[Conversion]
LogLevel=10
Please note:
- Changing the log level takes effect after restarting the program.
- A higher log level decelerates the data import.
Data Conversion Notes

Patient data
Patient which shall be converted is searched in SentrySuite by the patient ID entered
when the patient was created. There are some special rules which are checked if a
patient can be transferred to SentrySuite or is blocked. If a patient can not be
transferred, there is an error entry in the log files which will provide more information
as to the cause of the error.
Page 220/296 Version 06.02 • 2017-07-04

Patient import rules:

1) New patient check: patient with its ID is not found in SentrySuite and should be
created
a. ID: must conform to the rules of valid characters of a SentrySuite patient ID.
The following regular expression is checked: "^[\\w \\-#@\\~!$&.=]+$"
b. The birth date must be valid and not before 01.01.1800.
2) Compare patient check: patient with the same ID is found in SentrySuite.
The following patient properties must be identical in both patients. The check is
not case sensitive.
- Birth date
Empty fields are not compared and do not lead to an error.
If one of the rules above fails, the patient is not transferred to SentrySuite.
LungSubs
LungSubs contains data from Lung Volumes, Enhanced Spirometry, and
Plethysmography all in one table. Vmax does not really care which test was used, but
for SentrySuite you may need to differentiate. The main difference is the presence/
absence of the graphs:
An LsGraph indicates LungVolume test.
An LsPlGraph indicates Enhanced Spirometry or Body Box test.
The Presence of Vtg would indicate Body Box, no Vtg would mean Enhanced
Spirometry.
According to this behavior a test that contains a Vtg parameter is stored as Body
measurement and the measured spirometry data is stored to this Body measurement.
2.7.2 Predicted Values

2.7.3 Questionnaire Designer
For installing the SentrySuite Q-remote option, please read paragraph 1.2.9.
2.7.4 Report Designer

2.7.5 User Parameters
User Parameters Editor needs to have Internet Explorer 9 or higher installed.

Otherwise, an error message is shown and program start is not possible.
Version 06.02 • 2017-07-04 Page 221/296

2.8 Calibration Tools

2.8.1 CPET Service Calibration
This requires service login credentials, see paragraph 2.2 "SentrySuite Desktop".
2.8.2 Gas Analyzer Calibration

2.8.3 Volume Calibration
2.9 Applications
2.9.1 Spirometry
2.9.1.1 Result Mode

2.9.1.2 Measurement Mode
2.9.1.3 Edit Mode
2.9.2 Bodyplethysmography
2.9.3 FRC Rebreathing

2.9.4 Diffusion SB CO/He

2.9.5 Diffusion SB Intrabreath

2.9.6 Diffusion SB Realtime

2.9.7 Impulse Oscillometry

2.9.8 MIP / MEP

2.9.9 P 0.1
2.9.10 R Occlusion
Page 222/296 Version 06.02 • 2017-07-04

2.9.11 CPET
2.9.11.1 Settings and 3rd party ECG configuration
Select <Settings> and <Local Configuration...>.
2.9.11.1.1 Layout
Version 06.02 • 2017-07-04 Page 223/296

2.9.11.1.2 Ergometer
Page 224/296 Version 06.02 • 2017-07-04

2.9.11.1.3 ECG/Data Source Setup
A) General Notes
Note 1
For combining a 3rd party ECG with SeS / Vyntus CPX, at least in Europe an “Article
12 declaration” is needed.
This exists for installing the CardioSoft / USB-CAM onto a SeS / Vyntus CPX system,
but not for combining e.g. SeS / Vyntus CPX with the CASE-system.
It also does not (yet) exist for any other 3rd party ECG.
In this case, the ECG-manufacturer has to install “his software” and “his ECG” onto
the system and will be responsible for the whole medical system.
If you combine such systems without the official statement from the ECG-manufac-
turer, you will get the manufacturer and you take over the full responsibility for the
whole medical system.
Note 2
Please check program paths thoroughly: this document describes a new

installation.
a. Depending on the Operation system, “Program Files (x86)” may be
“Program Files”
b. Depending if SeS is a new installation or an updated:
New: “ProgramFiles(x86)\Carefusion\SentrySuite\DB" may be Update:
”ProgramFiles (x86)\SentrySuite\DB"
Note 3
In case of connecting two systems (via RS 232 or LAN), please consider the
electrical safety (isolation, isolation transformer etc.).
Version 06.02 • 2017-07-04 Page 225/296

B) General Overview and Information
In SeS V 2.17, following 3rd party ECGs can be configured:
SeS V 2.15 tested tested tested Article

ECG name Manufacturer Software V2.13 V 2.15 V 2.17 Notes 12
Vyntus ECG CFN SeS V 2.17 ok ok ok Vyntus ECG yes
3rd party ECGs
General description of the 3rd party ECG interface Interface no
AMEDTEC ECGpro AMEDTEC V 4.08 ok ok* ok AMEDTEC no
CardioSoft GE Healthcare V 6.73 ok ok ok CardioSoft yes
CardioSoft - 232 GE Healthcare V 6.73 -- ok ok CardioSoft - 232 no
CardioSoft - LAN GE Healthcare V 6.73 -- ok ok* CardioSoft - LAN no
Cardiolex Cardiolex V 4.0.0.9 ok ok* ok* Cardiolex no
CustoDiagnostic Custo V 4.31 ok ok* ok* Custo no
V 5.361 ok ok* ok
Norav Norav V 5.513, V 5.514, no no no Norav no
V 5.515.0 or .1 or .2
V 5.515.3 ok ok* ok*
PBI Pulse Biomedical V 4.06 ok ok* ok PBI no
Welch Allyn Welch Allyn V 1.65 ok ok* ok* WelchAllyn no
Padsy MedSet V 7.3.0.0 -- ok ok MedSet no
Mortara Mortara ?? -- ?? ?? Mortara no
3rd party ECG ?? ?? ?? ?? ?? 34d Party no
For these combinations, the ECG program acts as the master, SentrySuite-CPET as a
slave.
The data exchange between SentrySuite and the ECG's is performed via GDT for the
patient data and via the ergpspir.dat - file for the measurement data.
During the measurement, the ECG controls the measurement phases and writes the
phase information together with the ECG data into the ergospir.dat - file. Some ECG’s
are writhing this file every seconds (recommended), some only every 2 to 5 seconds.
SeS reads this file and saves the data into the CPET-measurement.
As there may be different names for the different phases, Sentry Suite interprets the
following names as identifiers for the following phases:
Synonyms for Check phase: chck

Synonyms for Rest phase: base, supi, rest
Synonyms for Warmup phase: refe, warm
Synonyms for Test phase: work, stag, ramp, exec
Synonyms for Recovery phase: reco
Synonyms for Stop: stop
If someone wants to adapt another ECG to SentrySuite, please ask for a detailed de-
scription of the data exchange (Patient data, ECG data, format etc.).
Important: For the communication between SeS and 3rd party ECG’s (not the
Vyntus ECG) the ECG-Interface option no. V-577500 is required.
Page 226/296 Version 06.02 • 2017-07-04

C) General Description of the Interface (same PC)
Vyntus ECG), the ECG-Interface option no. V-577500 is required.
Please see also chapter "General notes", Note 1.
For the setup, the following steps have to be performed in general:

1. Install the ECG software and hardware (please refer to the ECG-manufacturer's
installation guide).
2. Start the SeS-CPET-Application.
3. Select "Settings", "Local Configuration".
a. Select the Tab “ECG/Data Source” and the proper ECG device,
e.g. CardioSoft:
Note: Depending on the used version, not all ECGs (or even more) may be
selectable.
Version 06.02 • 2017-07-04 Page 227/296

b. As soon as one of the available ECG’s is selected, the default settings

of the selected ECG will be installed:
That means, e.g. HR and Blood pressure are taken from the ECG, SpO2 is taken from
the Vyntus CPX. If other external
peripherals are available, these can be selected via the pull-down menus (please also
refer to the settings in the user manual).
c. If in the Global Settings “Show extended measurement settings” is

activated, further details can be selected via the “Advanced” mode:
Page 228/296 Version 06.02 • 2017-07-04

• Allows to stop CPET while still

recording ECG
• Stop CPET from the ECG;

close / restart ECG in the
evaluation mode
• Split screen (only available

if the monitor & graphic
resolution is sufficient
(1280+1280 = 2560))
d. Advanced mode:
• Allows to check if the ECG-

software path is correct
• ECG-path
• Command line 1 (GDT-info)
• Command line 2 (if needed)
• Path of the “ergosopir.dat” file
• ECG & SeS on the same PC
Version 06.02 • 2017-07-04 Page 229/296

D) General Description of the Interface (RS 232)
The principle is the same as above (see "General description of the interface (same
PC)"), only that the data coming via the RS 232 (e.g. COM1) are converted to the
ergospir.dat - file via the program VasCPETCase.exe.
For the setup, the following steps have to be performed in general:

1. Install the ECG software and hardware - please refer to the ECG-manufacturer's
installation guide).
2. Connect the PC’s with a null-modem cable.
3. Start the SeS-CPET-Application.
4. Select "Settings", "Local Configuration".
a. Select the Tab “ECG/Data Source” and “3rd Party ECG"-device:
Page 230/296 Version 06.02 • 2017-07-04

b. Configure the communication:
• Allows to check if the ECG-

software path is correct
• Conversion program path
• COM port
• Path of the “ergosopir.dat” file
• ECG & SeS on different PC’s
5. Click <OK> and close the Local configuration.

6. Define the settings in the corresponding ECG so that the ECG is able to transfer
the ergospir.dat data to the defined COM-port.
7. Additional note:
There is also a INI-file for the RS 232-communication:
"C:\Program Files (x86)\Carefusion\SentrySuite\VasCPETCase.ini"
This file contains the default COM-port settings as well as a reference table, if the
phase names, baud rate, handshake etc. are different.
• COM-port settings:
o COM1: COM1
o 1200: baud rate
o n: no parity
o 8: data bits
o 1: XONOFF
• DOSIM:
o 0: off
(Simulation mode for testing without ECG, like ER-Demo)
• Text reference table, e.g. ECG sends “opwa” – SeS interprets it as
“warm”.
Version 06.02 • 2017-07-04 Page 231/296
E) General Description of the Interface (LAN)
The principle is the same as above (see "General description of the interface (same
PC)"), only that the data the ergospir.dat - file is saved in a net-environment on a
server.
In this case, in the “Advanced settings” you define in SeS
1. The path of the shared file
2. ECG on a different PC
• No entry
• Path of the shared file

(ergospir.dat)
• ECG on a different PC
3. In the ECG you may need to define the folder where the ECG should write the
ergosopir.dat file (must be the same as defined in SeS).
Page 232/296 Version 06.02 • 2017-07-04

F) Vyntus ECG
For the Vyntus ECG, no special settings are required. If the software option is released
and the hardware is available, everything is automatically configured during the instal-
lation.
The installation and configuration of the Vyntus ECG can be found in the “System
Configuration” under "Peripheral devices info".
You only need to select the Vyntus ECG in the drop-down list and maybe adapt the
different sources for Heart rate, Blood pressure and O2-saturation.
Version 06.02 • 2017-07-04 Page 233/296

G) AmedTec ECGPro
Important: For the communication between SeS and the ECG, the option no.
V-577500 is required.
1. Please consider chapter "General Notes", Note 1 and Note 2!

2. Install the AmedTec software V 4.08.
3. Connect the ECG unit to a free USB port on the PC – now the software will
install the hardware driver.
4. Insert the software-Dongle as well.
5. Start the AmedTexc ECGpro software.
6. Configure the ECC-settings:
a. Start the settings:
b. Select "Ergospirometry" in the left column:
Page 234/296 Version 06.02 • 2017-07-04

c. Select in the “General”-Tab: “Enable plugin”, “Use this

Plugin for acquisition” and “Cortex MetaSoft (version 3.9.2)”:
Version 06.02 • 2017-07-04 Page 235/296

d. Select the "Import"-Tab and enter (or browse to)

I. Path: "C:\Program Files (x86)\CareFusion\SentrySuite\DB"
II. File name: "HELLCPET.GDT"
It could be that the character encoding needs to be set to "1250- Central European
(Windows)".
Note:
The path is normally "C:\Program Files (x86)\CareFusion\SentrySuite\DB".
However:
Please check the path (see Note 2): Depending on the installation, the path may also
be "C:\Program Files (x86)\SentrySuite\DB" or similar.
Page 236/296 Version 06.02 • 2017-07-04

e. Select in the “Export”-Tab and enter (or browse to)

I. Measurement data Path:
"C:\Program Files (x86)\CareFusion\SentrySuite\DB"
II. Measurement data File name: "Ergospir.dat"
III. Result Path: : "C:\Program Files (x86)\CareFusion\SentrySuite\DB"
IV. Result File name: "CPETHELL.GDT"
V. Define “Create a result file for …"
VI. Define “AMEDTEC ECGpro" after closing / saving.
Note:
However:
Please check the path (see Note 2): Depending on the installation, the path may also
be "C:\Program Files (x86)\SentrySuite\DB" or similar.
Version 06.02 • 2017-07-04 Page 237/296

VII. Select Bicycles and configure the bike according to your system
settings, e.g.:
VIII. For further ECG-settings, please refer to the AmedTec user manual.
IX. Start the SentrySuite program.
X. In case of a dual screen, set SeS to the monitor “2”:
Page 238/296 Version 06.02 • 2017-07-04

XI. Select "SeS" - "CPET" – "Settings Local configuration" – "ECG/

Data source", select "AmedTech Pro" and check the paths and
settings (see also item "e. IV." and "e.V."):
Done.
XII. Short guidance for the ECG-operation:

• Start the CPET-Application (ECG will start automatically
when starting the measurement).
• Wait until Zeroing-phase is finished in SeS and the program
jumps into the Check phase.
• <CONTINUE> on the ECG will start the ECG; CPET remains
in the Check phase.
• Check if all parameters are plausible.
• <Start Test> on the ECG will start the Resting phase.
• <Start Exercise> on the ECG will start the Test Phase Notes:
1. It seems that AmedTec does not have a Warmup phase.
2. It seems that AmedTec does not transfer the “act load”, but the
“predicted load”.
Version 06.02 • 2017-07-04 Page 239/296

• <Start Recovery> on the ECG will start the Recovery phase.

• <STOP> will stop the measurement.
• <Save> will save the measurement.
Note:
At the end, AmedTec seems not to write the META – data:
This has the consequence, that in the review mode SeS cannot open the
corresponding ECG-measurement automatically - you need to select it
manually.
XIII. For further ECG-settings and performance, please refer to the Cardiolex
user manual.
Page 240/296 Version 06.02 • 2017-07-04

H) GE-Cardiosoft (on the same PC)
1. Install the Cardiosoft software and CAM 15 USB: Insert the CD and follow the
instructions.
2. Enter the CardioSoft software codes.
3. Select "SeS" - "CPET" - "Local configuration" – "ECG/Data source". Select
"Cardiosoft (GE Healthcare)" and check the paths and the settings
(see also Note 2):
4. Check the CardioSoft LOC_WIN.ini file if it contains the following entries in the
[Cas_Record] section:
[Cas_Record]
SpiroOptionWriteToFile=1
SpiroDirectory=C:\Program Files (x86)\CareFusion\SentrySuite\DB
(SpiroOptionWriteToFile=1 means: write the ergospir.dat – file)
(SpiroDirectory=C:\Program Files (x86)\CareFusion\SentrySuite\DB
is the location of the ergospir.dat file)
5. For further ECG-settings; please refer to the CardioSoft user manual.
Version 06.02 • 2017-07-04 Page 241/296

6. Additional info to CardioSoft:

a. With a “Standard” Installation, CardioSoft releases only a few
ergometers:
b. To get “all” ergometers, you need to perform the following

procedure:
I. Exit Cardiosoft to edit the "ca_sys.ini" file.
II. Open the ca_sys.ini file as found in the "C:/CARDIO" directory.
Add the following line at the end of the "ca_sys.ini" file:
"CFG_RemoveErgoandTMDevices=0"
III. Now “all” ergometers should be available again:
c. Please create proper profiles in CardioSoft:

CardioSoft normally only has a PRETEST (=Rest), EXERCISE (=Test)
and RECOVERY (=Recovery) phase.
To get also a Warmup-phase, modify the profile so, that the
Rest-phase is divided into two stages and indicate the second stage
with “Warm”:
Page 242/296 Version 06.02 • 2017-07-04

If you now start a measurement in CardioSoft with this profile, with

clicking
- <F1> (Pretest) the measurement is started in the Resting phase
- <F1> again jumps to the Warmup phase
- <F2> to the Test phase
- and so on.
7. Short guidance for the ECG-operation:

a. SeS: Start the CPET-Application (F1)
b. SeS: Select an existing Event profile, <ok>, <Start measurement>
c. SeS: continues with the Zeroing phase
(ECG will be started automatically)
d. SeS: Wait until Zeroing-phase is finished in SeS and the program
e. ECG: Select a proper profile in the ECG.
f. SeS: Check if all parameters are plausible.
Note: Cardiosoft does not yet write the Ergospir.dat file, so no data
(e.g. no HR) transferred from the ECG
g. ECG: <F1> to start the Resting phase
h. ECG: <F1> again to start the Warmup phase (see f. III.)
i. ECG: <F2> on the ECG will start the Test Phase
j. ECG: <F3> to start the Recovery phase
k. ECG: <F4> will stop the measurement
l. ECG: Close the ECG closes the ECG recording window and transfers
the META-data
m. SeS: <OK> stops and starts the Evaluation mode
8. For further ECG-settings and performance, please refer to the CardioSoft user
manual.
Version 06.02 • 2017-07-04 Page 243/296

I) GE-Cardiosoft (on a separate PC via RS 232)
Important: For the communication between SeS and the ECG the option no.
V-577500 is required. Please see also chapter "General Notes", note 1 and the
electrical safety if you combine two medical systems!
1. Install the Cardiosoft software and CAM 15 USB: follow the instructions.
Enter the CardioSoft software codes and configure the Cardiosoft program.
2. In CardioSoft, enable the Metabolic Cart and define the COM-Port for the
connection:
Page 244/296 Version 06.02 • 2017-07-04

3. Select "SeS" - "CPET" - "Local configuration" – "ECG/Data source".

Select 3rd Party ECG and check the paths and the settings (see also Note 2):
• Path and program name for the

RS 232-interface:
"C:\Program Files (x86)
\CareFusion\SentrySuite
\VasCPETCase.exe"
• COM - port (e.g. COM1)
• Path of shared file:

"C:\Program Files (x86)
\CareFusion\SentrySuite\DB"
4. Check/modify the CardioSoft LOC_WIN.ini file with the following serial port section:
[Cas_Record]
SpiroParity=0
SpiroDataBits=1
SpiroStopBits=0
SpiroBaudrate=2
SpiroHandShake=0
The settings for the serial port can be changed with the following entries:
SpiroParity: 0 = no parity, 1 = even parity, 2 = odd parity
SpiroDataBits: 0 = 7 data bits, 1 = 8 data bits
SpiroStopBits: 0 = 1 stop bit, 1 = 2 stop bits
SpiroBaudRate: 0 = 300 baud, 1 = 600 baud, 2 = 1200 baud, 3 = 2400 baud,
4 = 4800 baud, 5 = 9600 baud, 6 = 19200 baud,
7 = 38400 baud, 8 = 56000 baud, 9 = 128000 baud
SpiroHandShake: 0 = no handshake, 1 = XonXoff,
2 = hardware handshake,
3 = hardware handshake and interpretation of CR and NULL
Version 06.02 • 2017-07-04 Page 245/296

Furthermore, set
SpiroOptionWriteToFile = 0 means: do not write the ergospir.dat – file
SpiroDirectory = C:\Program Files (x86)\CareFusion\SentrySuite\DB

does not matter as the file is not written the in this
case
5. For further ECG-settings please refer to the CardioSoft user manual.

6. For defining a warmup phase in CardioSoft, please see above (chapter H, section
6.c.).
7. Short guidance for the operation:
a. SeS: Select / enter the PD-data in SeS
b. ECG: Start the ECG application – select / enter the PD-data in the ECG again
c. ECG: Select a proper profile in the ECG.
d. ECG: Continue until the check phase
e. SeS: Start the CPET-Application (F1)
f. SeS: Select an existing Event profile, <ok>, <Start measurement>
g. SeS: continues with the Zeroing phase
h. SeS: Wait until Zeroing-phase is finished in SeS and the program jumps into
the Check phase.
i. SeS: Check if all parameters are plausible.
Note: Cardiosoft does not yet write the Ergospir.dat file, so no data (e.g. no
HR) transferred from the ECG
j. ECG: <F1> to start the Resting phase
k. ECG: <F1> again to start the Warmup phase (see chapter H, section 6.c.).
l. ECG: <F2> on the ECG will start the Test Phase
m. ECG: <F3> to start the Recovery phase
n. ECG: <F4> will stop both the ECG as well as the SeS-CPET-applications.
manual.
Page 246/296 Version 06.02 • 2017-07-04

J) GE-Cardiosoft (on a separate PC via LAN)
Important: For the communication between SeS and the ECG the option no.
V-577500 is required. Please see also chapter "General Notes", note 1 and the
electrical safety if you combine two medical systems!
The principle is the same as above (see chapter "General description of the interface
(same PC)"), only that the data the ergospir.dat - file is saved in a net-environment on
a server.
In this case, in the “Advanced settings” you define in SeS
1. The path of the shared file
2. ECG on a different PC
• No entry
• Path of the shared file

(ergospir.dat)
Version 06.02 • 2017-07-04 Page 247/296

3. [Cas_Record]
SpiroOptionWriteToFile=1
SpiroDirectory=H:\HE\HELP\ECG_LAN
(SpiroOptionWriteToFile=1 means: write the ergospir.dat – file)

(SpiroDirectory= H:\HE\HELP\ECG_LAN
is the location of the ergospir.dat file)
4. For defining a warmup phase in CardioSoft, please see chapter above (chapter H,
section 6.c).
5. Short guidance for the operation:
a. SeS: Select / enter the PD data
b. ECG: Start the ECG application – select / enter the PD data in the ECG again
c. ECG: Select a proper profile in the ECG.
d. ECG: Continue until the check phase
e. SeS: Start the CPET-Application (<F1>)
f. SeS: Select an existing Event profile, <ok>, <Start measurement>
g. SeS: continues with the Zeroing phase
h. SeS: Wait until Zeroing-phase is finished in SeS and the program jumps into
the Check phase.
i. SeS: Check if all parameters are plausible.
Note: Cardiosoft does not yet write the Ergospir.dat file, so no data (e.g. no
HR) transferred from the ECG
j. ECG: <F1> to start the Resting phase
k. ECG: <F1> again to start the Warmup phase (see chapter H, section 6.c.)
l. ECG: <F2> on the ECG will start the Test Phase
m. ECG: <F3> to start the Recovery phase
n. ECG: <F4> will stop both the ECG as well as the SeS-CPET-applications.
manual.
Page 248/296 Version 06.02 • 2017-07-04

K) Cardiolex

2. Install the Cardiolex EC-Sense software V 4.0.
3. Connect the ECG unit to a free USB port on the PC – now the software will
install the hardware driver – if not installed properly, update the driver
(browse to the Cardiolex folder, e.g. "C:\Program Files (x86)\Cardiolex").
4. Start the EC-Sense program.
5. Configure the ECC-settings:
a. Start the settings:
b. The following window will appear:
Version 06.02 • 2017-07-04 Page 249/296

c. Select the “Exercise ECG” – tab and configure the

Ergometer(s) to be used:
• Select “Exercise ECG” - Tab
• Select “Prot. and

equipment”
• Select “Connected
equipments”
• Open the list box
d. If needed, add one (or more) ergometers:
• Select <Add>
• Select the “empty field”
• Select “Equipment”
• Open the list box
Page 250/296 Version 06.02 • 2017-07-04

e. Select the ergometer, e.g. ErgoLine 900:
f. Select “ErgoLine900”, “Port” and select the correct COM-Port, e.g. COM1:
Version 06.02 • 2017-07-04 Page 251/296

g. Repeat step "d." and "e." and select “CareFusion JLAB” as “Equipment”:
Page 252/296 Version 06.02 • 2017-07-04

h. Select “port” and enter under “No port” the path for the
Ergospir.dat file:
• Click on “No port”
• Enter the path for the

ERGOSPIR.DAT file:
"C:\Program Files (x86)\
CareFusion\SentrySuite\DB"
Important:
Please check the path (see
Note 2): Depending on the
installation, this may be
also "C:\Program Files
(x86)\SentrySuite\DB" or
similar.
Version 06.02 • 2017-07-04 Page 253/296

i. You can define your “default ergometer” by selecting the

ergometer and moving it with the arrow keys up on top, e.g.:
6. For further ECG-settings, please refer to the Cardiolex user manual.

7. Start the SentrySuite program.
8. In case of a dual screen, set SeS to the monitor “2”:
Page 254/296 Version 06.02 • 2017-07-04

9. Select "SeS" - "CPET" – "Settings Local configuration" – "ECG/Data source",

select "Cardiolex" and check the paths and settings (see also item "h.")
Done.
Version 06.02 • 2017-07-04 Page 255/296

10.Short guidance for the ECG-operation:

a. SeS: Start the CPET-Application (<F1>).
b. SeS: Select an existing Event profile, <ok>, <Start measurement>.
c. SeS: continues with the Zeroing phase (ECG will be started
automatically).
e. CPET: Check if all parameters are plausible.
Note: No HR transferred yet to SeS, as Cardiolex does not write the
ERGOSPIR.DAT during the Check phase.
f. ECG: <START> will start the Resting Phase.
g. ECG: <F8> respectively will step through the Rest, Warmup-, Test-
and Recovery-phase and finally stop the measurement.
h. ECG: Close the ECG
i. CPET: activate “Save without the meta data”.
j. CPET: <OK> stops and starts the Evaluation mode.
Notes:
• Sometimes, with the first pressing of <F8>, the Cardiolex does not jump to
the warmup phase! In this case, you need to activate it twice.
• Cadiolex does not transfer the “actual” load, but the “predicted” load!
• At the end, Cardiolex does not write the META – data: You have to close the
SeS CPET program by activating “Save without the meta data”.
This has the consequence, that in the review mode SeS cannot open the
corresponding ECG-measurement automatically - you need to select it
manually.
11.For further ECG-settings and performance, please refer to the Cardiolex user
manual.
Page 256/296 Version 06.02 • 2017-07-04

L) Custo Diagnostic

2. Install the Custo Diagnostic software V 4.3.
3. Start the Custo Diagnostic software and configure the settings via
"Examinations" – "Settings":
Version 06.02 • 2017-07-04 Page 257/296

4. Select "System", "Export", "EHR" - Tab:
a. Activate “Data Import” and select “GDT 1.0 WIN”.

b. Activate “Data Export” and select “GDT 1.0 WIN”.
c. Activate “Enable manual patient admissions”.
d. Activate “Apply of changed patient data”.
e. Set the Import path, file name and extension:
• Path: “C:\Program Files (x86)\CareFusion\SentrySuite\DB”
• File Name: “HELLCPET”
• Extension: "solid" - “GDT”
f. Set the Export path, file name and extension:
• Path: “C:\Program Files (x86)\CareFusion\SentrySuite\DB”
• File Name: “CPETHELL”
• Extension: "solid" - “GDT”
g. Don’t forget to activate <Save>.
Note:
However: Please check the path (see chapter "General Notes", Note 2):
Depending on the installation, this may be also "C:\Program Files (x86)\
SentrySuite\DB" or similar.
Page 258/296 Version 06.02 • 2017-07-04

5. Select <System>, <System> and <Workstation> - Tab.
a. Activate the Interface “ViaSys”.

b. Don’t forget to activate <Save>
6. Configure the ergometer connected to the ECG, e.g. via <System>,

<Connection> <Device>.
a. Select the ergometer and the COM – Port.

b. Don’t forget to activate <Save>.
c. For further details please refer to the Custo Diagnostic user manual.
Version 06.02 • 2017-07-04 Page 259/296

7. Configure this Ergometer for Cardiopulmonary Exercise: <Cardiopulmonary

Exercise>, <Connection> <Device>.
a. Select the correct ergometer and the COM – Port.

b. Don’t forget to activate <Save>.
c. For further details please refer to the Custo Diagnostic user manual.
8. Modify the WIN.INI – file, normally found in “C:\Windows\”:

Change or add the following section:
[Cas_Record]
SpiroDirectory=C:\Program Files (x86)\CareFusion\SentrySuite\DB
Note:
However: Please check the path (see Note 2):
9. Additional note:
a. To suppress the start-up login dialog box:
Configure <System> <System> <User>.
(e.g. “Logon this computer”: Supervisor, PW: custo)
b. For further details please refer to the Custo Diagnostic user manual.
10.Start the SentrySuite program.
Page 260/296 Version 06.02 • 2017-07-04

11.In case of a dual screen, set SeS to the monitor “2”:
12.Select "SeS" - "CPET" – "Settings Local configuration" – "ECG/Data source",

select "Custo Diagnostic" and check the paths and settings (see also item "4."
and "8."):
Done.
Version 06.02 • 2017-07-04 Page 261/296


a. SeS: Start the CPET-Application (<F1>)
c. SeS: continues with the Zeroing phase (ECG will be started automatically)
d. SeS: Wait until Zeroing-phase is finished in SeS and the program jumps into
the Check phase.
e. ECG: Select the proper Protocol in the ECG
• We recommend to use the following settings:
- Resting: “End by user”
- Warmup: e.g. 3 min (end via <Next Stage>):
f. ECG: <Start> starts the Check phase in the ECG

(CPET remains in the Check phase)
g. Check in CPET if all values are plausible (including HR)
h. ECG: <Start> Starts the Resting phase
i. ECG: <Start Exercise> starts the Warmup phase
Note:
• Custo Diagnostic does not (yet) transfer the “Warmup” message to
CPET, therefore CPET will remain in the “Resting phase !!
j. ECG: <Next Stage> starts the Test phase
k. ECG: <Recovery Stage> starts the Recovery phase
l. ECG: <Stop> ends the ECG – but still running
m. ECG: <End> saves the ECG data and stops CPET
n. ECG: <End> closes the ECG recording window and transfers the META-data
o. SeS: <OK> stops and starts the Evaluation mode
p. For further ECG-settings and performance, please refer to the Custo
Diagnostic user manual.
Page 262/296 Version 06.02 • 2017-07-04

M) Norav

2. Install the Norav PC-ECG 1200 software version according to the Norav installation
manual. The description below was made with V 5.316, so the settings may be a
bit different with later versions, but in principle they are the same.
Note:
The version V 5.316 works fine.
V 5.513 and V 5.514 and V 5.515.0 may not work properly.
V 5.515.3 works fine, but only tested with Win 7 – 64 bit
3. Connect the ECG unit to a free USB port on the PC – now the software will install
the hardware driver - make sure that the green light on the ECG is on.
Note: Follow the default installation – if not, you may need to adapt the settings
described below.
4. Insert the software-Dongle as well; connect a patient cable and verify the
connections:
a. Open the PC-ECG 1200 - folder in the desktop
b. Start the “Resting ECG” application
c. Press <F1>, enter a Patient ID, <OK>; verify the ECG-traces on the screen
d. <F2> to stop the ECG and close the program.
5. Start the “Stress ECG” application, select "Setup".
6. Select the “Environment” tab, configure “your default” Exercise Device and click
<Apply>:
Version 06.02 • 2017-07-04 Page 263/296

7. For further ECG-settings please refer to the Norav user manual.

8. Select the “Advance” Sub-Tab, activate “Use real time …”, enter the correct
path for the ERGOSPIR.DAT file and click <Apply>:
• Select the "Advance" Sub-tab.

• Activate "Use real time ...".
• Enter the correct path name for
the ERGOSPIR.DAT-file (see also
item "k."):
CareFusion\SentrySuite\DB\
ERGOSPIR.DAT".
Important:
chapter "General notes",
Note 2): Depending on
the installation, this may
be also "C:\Program
Files (x86)\ SentrySuite\
DB\ERGOSPIR.DAT" or
similar.
Page 264/296 Version 06.02 • 2017-07-04

9. Select the "GDT/BDT Format" tab and activate / enter the GDT-info:
• Select the “GDT/BDT

Format”-Tab
• Select Auto: “Import from
GDT/BDT”
• Select File Format: "GDT"
• Browse to (or enter) the
correct File (see also item
"k.") for the GDT exchange:
CareFusion\SentrySuite\
DB"
• Enter the “Taken for PC
ECG”: "HELL"
Important:
(x86)\ SentrySuite\DB"
or similar.
10.Start the SentrySuite program.
Version 06.02 • 2017-07-04 Page 265/296

12. Select "SeS" - "CPET" – "Settings Local configuration" – "ECG/Data

source", select "Norav" and check the paths and settings (see also item "6." and
"7."):
Done.
Page 266/296 Version 06.02 • 2017-07-04


c. SeS: continues with the Zeroing phase
e. ECG: Press <F6> to start the Rest phase (may be enter BP values as well)
f. ECG: <F9> to allow entering a Warmup load at the button on the screen:
g. ECG: Enter a value (or use "< >" ) – with <SEND>, the Warmup phase is
started
h. ECG: <F3> to start the Test Phase
i. ECG: <F5> to start the Recovery phase
j. ECG: <F4> to stop the measurement
k. ECG: Close closes the ECG Stress program and transfers the META-data
l. SeS: <OK> stops and starts the Evaluation mode
14.For further ECG-settings and performance, please refer to the Norav user manual.
(Note: Norav does not transfer the “actual” load, but the “predicted” load!)
Version 06.02 • 2017-07-04 Page 267/296

N) PBI

2. The ECG-HW must have an USB – or Bluetooth connection.
3. Connect the PBI-ECG via USB-cable (or via Bluetooth) to the PC.
4. Install the PBI Software “QRS Card Cardiology Suite V 4.06”.
The software can be downloaded as .msi-file in different languages from
"http://qrscard.com/download_demofull.html"
or as .exe-file (only English/US) from "http://qrs-card-cardiology-suite.soft-
ware.informer.com/download/ ".
5. After the installation, start the QRS-Card Cardiology Suite via
6. The program may respond with a message “invalid product ID":
7. Continue with <Cancel> (and <OK> in the next window).
8. In the ECG-Screen, select “Help” and “About”:
Page 268/296 Version 06.02 • 2017-07-04

9. Select the <Service> button in the next picture; the “Unlock Transfer
Key” window will open. Here, enter "1234":
10.Selecting <OK> will show the “Transfer Security Key to Computer” window:
11.Send the yellow highlighted DEVID to the Tech Support Team from PBI to get the
software license code for this PC (note: this will not be free of charge!).
Version 06.02 • 2017-07-04 Page 269/296

12 After that, you will get the following data from PBI, e.g.
TK: 578C-1D80-9B21-33E4S
PID: C632-342C-8CC9-182BFG
13.Start the QRS-Card Cardiology Suite and open the “About...” box
(perform steps "5.","6.","7.","8.").
14.Select the “lock” icon, enter the PID and confirm with <OK>.
15.Select <Service>, enter "1234" and enter the TK (see step "7." and "8.") and
confirm the registration with <OK>:
Page 270/296 Version 06.02 • 2017-07-04

16.Close the QRS-Card Cardiology Suite.
Note: The registration is stored under “CURRENT_USER”.

You may need to re-enter this again if the user is changed.
17.Start the Registry (e.g. via <WINDOWS> and <R> and entering “regedit”).
Navigate to "HKEY_CURRENT_USER\Software\Pulse Biomedical\Cardiology
Suite 4\Options".
Right-click and enter a new “string value”.
Version 06.02 • 2017-07-04 Page 271/296

18.Re-name it to “CareFusion”:
19.Enter the following (opening CareFusion):

"C:\Program Files (x86)\CareFusion\SentrySuite\DB\ERGOSPIR.DAT"
Confirm with <OK>.
20.Start the QRS-Card Cardiology Suite and perform the configuration:
Page 272/296 Version 06.02 • 2017-07-04

21.Adjust the configuration and confirm with <OK>:
• Select the “EMR” – Tab

• Select File: “Custom”
• Enter the correct File (see also
item "19."):
DB\HELLCPET.GDT"
• Select Format “GDT”
• Select “GDT”
• Enter the correct File (see also
item "19."):
DB\CPETHELL.GDT"
Important:
(x86)\ SentrySuite\DB\
HELLCPET.GDT"
respectively
"C:\Program Files
(x86)\ SentrySuite\
DB\CPETHELL.GDT" or
similar.
22.Start the Stress Setup:
Version 06.02 • 2017-07-04 Page 273/296

23.Perform (check) the following configuration:
• Select a proper profile
• Select the ergometer

(Note: the system searches
automatically for the
connection (from COM1 –
COM 8)
• Check the QRS Card

connection (USB, RS 232,
Bluetooth)
Page 274/296 Version 06.02 • 2017-07-04

25.Select "SeS" - "CPET" -" Local configuration" – "ECG/Data source",

select "PBI (Pulse Biomedical)"and check the paths and settings
(see also item "21."):
Done.
26.Note: In case of a 32-Bit Win 7 and an “old ECG-Hardware”, the ECG-driver may
not be found. In this case, update the ECG-driver from the folder
“.../Pulse Biomedical\V400".
Note: For further ECG-settings, please refer to the PBI user manual.
Version 06.02 • 2017-07-04 Page 275/296

O) WelchAllyn - CardioPerfect

2. Install the CardioPerfect software V 1.6.5.
3. Install the “SetupCardioPerfectJLABInterface.exe” (you will receive this from
WelchAllyn).
Adapt the “JLABInterface.ini” file in “C:\Program Files (x86)\Welch Allyn\
JLAB Interface”:
[Options]
Filename = 'ergospir.dat'
GDTFilenameAndPath = 'C:\Program Files (x86)\CareFusion\SentrySuite\DB\
HELLCPET.GDT'
SignificantLead = 'I'
SpeedUnit = 'KMH'
LockPatient = True
SuspectString = 'SUSPECT'
PatientMatchCriteria = 'MATCH_DOB_GENDER_LAST_FIRST'
ST_LEVEL_USE_BLANK_VALUE = 0
ST_SLOPE_USE_BLANK_VALUE = 0
Directory = 'C:\Program Files (x86)\CareFusion\SentrySuite\DB'
Note: The path is normally "C:\Program Files (x86)\CareFusion\SentrySuite\

DB".
However: Please check the path (see chapter "General Notes", Note 2):
4. Start the CardioPerfect program.

5. Navigate to: "File"-> "settings" -> "Exercise ECG" Icon -> "Monitor" tab:
Page 276/296 Version 06.02 • 2017-07-04

Enable checkbox “Use event dispatcher for external applications".
6. Select "Devices" and configure your ergometer(s), e.g.:

8. In case of a dual screen, set SeS to the monitor “2”:
Version 06.02 • 2017-07-04 Page 277/296

9. Select "SeS" - "CPET" – "Settings" - "Local configuration" – "ECG/Data

source", select "Welch Allyn" and check the paths and settings
(see also item "3."):
Done.
Page 278/296 Version 06.02 • 2017-07-04


c. SeS: continues with the Zeroing phase (ECG will be started
automatically)
e. CPET: Check if all parameters are plausible (no HR transferred yet).
f. ECG: Start the Exercise ECG
g. CPET: Check if all parameters are plausible (no HR transferred yet)

Note:
• No HR transferred yet to SeS, as Welch Allyn does not yet write the
ERGOSPIR.DAT file at this stage.
h. ECG: Press <START> to start the measurement.
Note:
• If no Pre-test phase defined (see Tools – Protocol editor), both the ECG as well
as the CPET immediately will jump to the Test phase
• The CardioPerfect does not have a Warmup phase.
i. ECG: Continue with <Goto Exercise>, respectively <Goto Recovery>
j. ECG: <Stop Test> ends the measurement
k. CPET: activate “Save without the meta data”.
l. CPET: <OK> stops and starts the Evaluation mode
11.Further notes:
a. CardioPerfect does not transfer the “actual” load, but the “predicted” load!
b. CardioPerfect does not transfer the RPM form the ergometer!
c. At the end, CardioPerfect does not write the META – data:
You have to close the SeS CPET program by activating
“Save without the meta data”.
This has the consequence, that in the review mode SeS cannot open the corre-
sponding ECG-measurement automatically - you need to select it manually.
12.For further ECG-settings and performance, please refer to the CardioPerfect user
manual.
Version 06.02 • 2017-07-04 Page 279/296

P) MedSet Padsy

2. Install the MedSet Software V 7.3.0.0 and the corresponding hardware according
to the installation description from MedSet
(Dongle, Dongle SW from CD: \Windows\Dongle-SW\Runtime.exe)
(Padsy SW from CD: \Windows\Padsy\Standard.exe)
(FLASHLIGHT Sensor Hardware via USB V 3.0)
3. Start Padys Software, install the license and configure the settings:
a. Select GDT setup via the Navigation tree:
b. Define the GDT settings

Modify the following settings:
• HELL
• CPET
• Enter the correct path for the
shared file:
CareFusion\SentrySuite\DB"
• If necessary (e.g. for ö, ä, ...),
select the correct character
set
• Activate the 3 GDT settings
Page 280/296 Version 06.02 • 2017-07-04

c. Define your hardware and ergometers via selecting "Tools" - "Hardware"
• Define your ECG hardware
For details, see MedSet user manual
• Define your ergometer:
For details, see MedSet user manual
Version 06.02 • 2017-07-04 Page 281/296

d. Select the Stress program settings via the Navigation tree:
e. Define the Spirometry settings:
Modify the following settings:

Select
• Yes
• Spirometry-Interface
• Enter (or browse to) the

correct path for the shared
file:
DB"
f. For further details please refer to the Medset user manual.
Page 282/296 Version 06.02 • 2017-07-04


5. In case of a dual screen, set SeS to the monitor “"”:
6. Select SeS - CPET – Settings Local configuration – ECG/Data source, select "Padsy
(MedSet)" and check the paths and settings:
Version 06.02 • 2017-07-04 Page 283/296

7. Short guidance for the ECG-operation:

a. SeS: Start the CPET-Application (<F1>).
b. SeS: Select an existing Event profile, <ok>, <Start measurement>.
c. SeS: continues with the Zeroing phase (ECG will be started automatically).
d. SeS: Wait until Zeroing-phase is finished in SeS and the program jumps into
the Check phase.
e. Check in CPET if all values are plausible (including HR).
Note: ECG does not transfer ECG-data like HR during the check phase.
f. ECG: with
the Resting phase will be started – SeS jumps to the Resting

phase as well.
g. ECG: Before continuing with the Test phase, Padsy expects a BP-entry via:
h. ECG: with
the Test phase will be started – SeS jumps to the Test phase
as well.
Note: Padys does not have a Warmup phase and jumps
directly to the Test phase.
i. ECG: with
the Recovery phase will be started – SeS jumps to the

Recovery phase as well.
j. ECG: Select end test criteria and <END>:
Page 284/296 Version 06.02 • 2017-07-04

k. ECG
with both the ECG as well as SeS will stop and start in the
evaluation mode.
Note:
As the ECG does not send the complete Meta-data-set, you
need to select the corresponding ECG-measurement
manually for the evaluation.
l. CPET: <OK> stops and starts the Evaluation mode
8. For further ECG-settings and performance, please refer to the Padsy user manual.
Q) Mortara
Important: For the communication between SeS and any 3rd party ECG, the
option no. V-577500 is required.
To be described.
R) 3rd Party ECG (General)
This chapter describes the ECG-CPET-User interfaces in general, which will allow
any ECG-manufacturer to adapt his ECG so that it can run in combination with the
SentrySuite and Vyntus CPX.
To be described.
Please ask Global Customer Support (GCS) if the description is already available.
Version 06.02 • 2017-07-04 Page 285/296

2.9.12 Bloodgas Data Transfer

2.9.13 Offline Data Input
2.9.14 Spirometer Data Transfer
2.9.15 Bronchial Challenge
3. Troubleshooting
3.1 Error Diagnosis
SentrySuite comes with an extended error logging system. CareFusion recommends
that you use paragraph 3.1.1 - 3.1.3 to document any error you experience with
SentrySuite and report them to the CareFusion technical support for analysis.
There are three possible sources to diagnose SentrySuite errors:
1. SentrySuite log viewer
2. SentrySuite system logfiles
3. Windows eventlogs
3.1.1 SentrySuite Log Viewer
See <SentrySuite Desktop application>.

Select <User Administration>, <Log File Viewer>.
Unfiltered view ("No filter") shows all events.
Page 286/296 Version 06.02 • 2017-07-04

To filter events by errors, select the "Error" tab. Following screen will appear:
Double-click an error to see its details:
The log can be exported by selecting <File> and <Export>.

Following message appears:
Version 06.02 • 2017-07-04 Page 287/296

3.1.2 SentrySuite System Log Files
These files can be found in <SentrySuite-install-path> \DB\LOG.
In order to review these files, click on <SentrySuite Desktop application> and se-
lect <User Administration>, <Log File Viewer>, <File>, <System Logs>.
There are three groups of System Logs:
1. Setup Logs
2. Application Logs
3. Database Logs
3.1.3 Windows Event Viewer
Run "Eventvwr.msc" in the Windows Start Menu.
Select "Windows Logs", "Application Logs" and right-click in order to filter this
log for specific application entries like "SQL" or "Sentry*".
NOTE: Under "Application and Services Logs", there's a special DBxConnect log.
Double-clicking an event will open the details of the respective event. Click the
<Copy>-Button to copy the event with all details and paste it into a Notepad- or
Wordpad-file. Send this file to CareFusion for analysis.
For a tutorial on using Event Viewer, see:
http://www.sevenforums.com/tutorials/226084-event-viewer-open-use-windows-7-a.html
Page 288/296 Version 06.02 • 2017-07-04

3.2 Error Messages & Solutions

Setup Client
Wrong operating system
If the setup detects a Windows OS that is not supported by SentrySuite or an OS with
an incorrect ServicePack, the following warning will appear:
"The current installed version of operation system (<DETECTED OS NAME>) is
not supported by this setup.
SentrySuite supports following operating systems: Windows® 7 ServicePack 1
or higher.“
Nevertheless, the installation can be continued.
Wrong display resolution

If the setup detects a display resolution lower as specified, the following warning will
appear:
"Display resolution is too low. Expected resolution is at least 1280x900.“
Setup Server
Wrong operating system
If the setup detects a Windows OS that is not supported by SentrySuite or an OS with
an incorrect ServicePack, the following warning will appear:
"The current installed version of operation system (<DETECTED OS NAME>) is
not supported by this setup.
SentrySuite supports following operating systems: Windows Server 2008."
Desktop
Initial System Check
Upon startup, the Desktop performs several system checks in order to determine if the
SentrySuite system is functional. If one of these checks fails, the following information
window containing a Failure-Code (FC) and additional information concerning the
failure is displayed.
Version 06.02 • 2017-07-04 Page 289/296

Following failure codes are defined:
FAILURE_PREENV_ENVMGR 0x00000001 Desktop Internal error

FAILURE_PREENV_ENVDAT 0x00000002 Desktop Internal error
FAILURE_PREENV_ENVTXT 0x00000004 Desktop Internal error
FAILURE_PREENV_ENVSTR 0x00000008 Desktop Internal error
FAILURE_SYSTEMFILES 0x00000010 Some files are missing in the installation folder or are corrupt
FAILURE_SYSTEMSERVICE 0x00000020 The SentrySuite DataService is not running
FAILURE_SYSTEMCOMPONENTS 0x00000040 Some COM files are not registered correctly
FAILURE_SYSTEMDATABASE 0x00000080 Something is wrong with the database connection
FAILURE_SYSTEMSIGNATURES 0x00000100 A SentrySuite binary file seems to be corrupt
FAILURE_SYSTEMPLUGINS 0x00000200 A SentrySuite Desktop component is missing
FAILURE_MODULE_APPLICATION 0x10010000 Desktop Internal error

FAILURE_MODULE_ERRORLOG 0x10020000 The error logging seems corrupt
FAILURE_MODULE_ENVIRONMENT 0x10040000 The application environment seems to be corrupt
FAILURE_MODULE_SESSION 0x10080000 The SessionManager is not working
FAILURE_MODULE_SCRIPTING 0x10100000 Desktop Internal error
FAILURE_MODULE_SKINNING 0x10200000 Desktop Internal error
FAILURE_MODULE_SYSEVENTS 0x10400000 The Windows System Events are not working
FAILURE_MODULE_SYSINFO 0x10800000 The SentrySuite DataService is not running
FAILURE_MODULE_SYSRIGHTS 0x11000000
FAILURE_MODULE_SYSMESSAGES 0x12000000 The SentrySuite DataService is not running
FAILURE_MODULE_STATEMACHINE 0x14000000 The Statemachine information is corrupt
FAILURE__FATAL 0x40000000 The SentrySuite Desktop is unable to start and

will be terminated
In this case, the failure code is "0x40000040" and is composed of following values:
FAILURE_SYSTEMCOMPONENTS 0x00000040
FAILURE__FATAL 0x40000000
This means that the system is not functioning correctly and the SentrySuite Desktop is
terminated.
To fix the indicated failure, it needs to be described in more detail and be left open!
Page 290/296 Version 06.02 • 2017-07-04

Backup / Restore database messages

Issue:
When a database is to be restored and the version of the backup database is not the
same as the current SentrySuite version, the following task dialog is shown.
Solution: There is nothing to do. You can restore nevertheless but this is not
recommended because there may be structural changes which are not compatible
with the current version.
Export data in XML files

Issue: When exporting data from the SQL database into an external xml file, there
may be a problem with write-protected folders. When exporting the file to a folder,
the user does not have the necessary rights to write or create the file; the export will
show no error dialog, however. Instead, a message is shown indicating that the export
is completed successfully, which is not the case. The export file will not be available!
Solution: There is nothing to do but to change to a folder the user has the necessary
rights to create and write a file at.
System Configuration
Enter configuration and validation code
Issue: When entering a configuration or validation code, there can be multiple
possibilities of typos. As the code has to be entered exactly, a message may be shown
indicating that the code was not entered correctly:
Solution: Reenter the code.
Version 06.02 • 2017-07-04 Page 291/296

SentryConnect - Connectivity
ADT first patient search with COM-error
Issue:
When there is no patient in the temporary database, an error message is generated
which looks as follows:
Solution: This error message occurs only once, when no patient was transmitted
from HIS. After at least one patient was transferred from HIS, the message will never
occur again.
Send report error
Issue:
Sending a report in SentrySuite Review program returned this error message.
Solution:
Check the HIS Connection Settings in SentrySuite Desktop program (menu Desktop >
"Intercon configuration")
Page 292/296 Version 06.02 • 2017-07-04

Driver system
Device not found
If a device is not plugged in or plugged-in but not switched on, an error message box
is shown:
The user has now the opportunity to switch the device OFF and click on
<Repeat device search>.
Zero failure
If the zeroing of one or more channels fails, an error message box is shown:
The user can either repeat the zeroing by clicking the <Retry> button or skip it.
A click on <More Information> shows additionally the failed channels.
Version 06.02 • 2017-07-04 Page 293/296

Connection lost
The drivers of the MS-Pneumo, MS-APS and MS-IOS check the connection when the
measurement is started. (See 5.1). If the connection is lost during measurement
(e.g. the cable is unplugged), no additional error message will be shown.
Interconnectivity Manager
Patient list could not be loaded
Issue:
The list of patients could not be loaded in Interconnectivity Manager.
Solution:
1. Check settings in Interconnectivity Manager (Tab Settings)
2. Check whether the Connectivity Host is running on the remote computer.
Mixed network could not be enabled for Vmax or JLAB
Issue:
The service for mixed network could not be started.
Solution:
1. Check settings in Interconnectivity Manager (Tab Settings)
2. Check whether the Connectivity Host is running on the remote computer.
Setting for [...] could not be saved
Page 294/296 Version 06.02 • 2017-07-04

Other error messages

Settings for CPET conversion could not be saved.
Setting for database path could not be saved.
Setting for database adapter could not be saved.
Setting for database connectivity host could not be saved.
Issue:
The settings in Interconnectivity Manager could not be saved.
The Windows user who is running Interconnectivity Manager has not enough rights to
write the following configuration files in SentrySuite program folder:
SesInterconMan.exe.config
SesJLabConServiceHost.exe.config
SesVmaxConServiceHost.exe.config
Vasbase.ini
Solution:
1. Run Interconnectivity Manager using a different user who has write permissions
for the configuration files
2. Add write permissions to the configuration files for the Windows user
Sentry.NET
Login failed
Issue:
The SentrySuite user who logged in has not enough rights to start Sentry.NET
Solution:
Grant rights for Sentry.NET to the SentrySuite user using the SentrySuite User
Management program.
Version 06.02 • 2017-07-04 Page 295/296

Patient chart
Invalid data
Other error messages

Please check name
Please check first name
Please check date of birth
Please check gender
Please check current setting
Please check predicted module
Please check height
Please check weight
Please check type of patient
ID is already assigned to another patient.
A ... with the same name already exists.
Issue:
In Patient chart patient data was not entered completely or data was entered but is
out of range.
Solution:
Check the patient data in Patient chart.
3.3 Describe Functional Process Details

3.4 System Description
3.5 Check Procedure for Modules (Service Tools & Utilities)
See paragraph 2.2.1.2 System Hardware.
3.6 Disassembly of System and Replacement of Modules
Page 296/296 Version 06.02 • 2017-07-04

4. Contacts
4.1 Important Email Addresses and Phone Numbers
Europe - Hoechberg, Germany
Global Customer Support:

(Hotline Respiratory Diagnostics):
support.RT.EU.JAE@carefusion.com +49 931 4972-127
Administration:
support.admin.eu@carefusion.com +49 931 4972-867
Clinical Integration Services:

support.connect.EU@carefusion.com +49 931 4972-672
Accessories/Consumables: +49 931 4972-365

Leibnizstrasse 7
97204 Hoechberg
Germany
+49 931 4972-0 tel
+49 931 4972-423 fax
www.carefusion.com
North America - Yorba Linda, CA

Technical Support: 800 231 2466
support.jaeger.us@carefusion.com 714 283 2228
Customer Service (Order Management): 800 231 2466 ext.8500
Version 06.02 • 2017-07-04 Page 297/296

4.2 Product Improvements (Downloads of New Software /Firmware),

Web Links, Shops
Sentry.NET demo:
http://10.240.118.90/SentryNET/SentryNETPage.aspx
login-credentials:
user = Doctor
password = 12345
4.3 PR Material (Poster, Flyer, CD’s), Training Material…

V-791700 Brochure MS Pneumo SeS DE
V-791701 Brochure MS Pneumo SeS EN
V-791702 Spec Sheet MS Pneumo SeS DE
V-791703 Spec Sheet MS Pneumo SeS EN
V-791705 Brochure SentrySuite EN
V-791707 Spec Sheet SentrySuite EN
V-791722 Brochure MS IOS EN
V-791724 Brochure MS IOS DE
V-791725 Brochure MS IOS FR
V-791720 Brochure APS pro EN
V-791726 Brochure APS pro DE
V-791727 Brochure APS pro FR
V-791716 MicroGard Spec Sheet EN
V-791728 Brochure MS PFT EN
Page 298/296 Version 06.02 • 2017-07-04

Distribution & Service:
CareFusion Yorba Linda
22745 Savi Ranch Parkway
Yorba Linda, CA 92887
USA
+1 714 283 2228 tel
+1 714 283 8493 fax

Leibnizstrasse 7
97204 Hoechberg
Germany
+49 931 4972-0 tel
+49 931 4972-423 fax
© 2017 CareFusion or one of its affiliates.

All rights reserved.
SentrySuite and MicroGard are trademarks or registered
trademarks of CareFusion Corporation or one of its affiliates.
All trademarks are property of their respective owners.
carefusion.com

ServiceManual SentrySuite

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ServiceManual SentrySuite

Uploaded by

Copyright:

Available Formats

Service Manual

Alterations and Revisions

Subject to technical modifications.

Page 2/296 Version 06.02 • 2017-07-04

Document Revision Table.......................................................................................... 8

Version 06.02 • 2017-07-04 Page 3/296

Page 4/296 Version 06.02 • 2017-07-04

2.2.1.6 Exit................................................................................................... 152

2.4.1 Log File Viewer................................................................................. 152

Version 06.02 • 2017-07-04 Page 5/296

D) HP CosCom V3............................................................................ 194

Page 6/296 Version 06.02 • 2017-07-04

C) General Description of the Interface (same PC)............................. 227

Version 06.02 • 2017-07-04 Page 7/296

Document Revision Table

Date Revision Major Changes

FEDERAL U.S. LAW RESTRICTS THIS DEVICE TO SALE BY OR ON THE ORDER OF A

Page 8/296 Version 06.02 • 2017-07-04

General Safety Precautions

The service manual is regarded to be a part of the instrument, and should

The instructions on hygiene are described in a separate manual (V-781332).

Version 06.02 • 2017-07-04 Page 9/296

Symbols for Notes on Safety in Instructions for Use and Service

Following the ANSI recommendations (American National Standards Institute) for

DANGER indicates an imminently hazardous situation

CAUTION indicates a potentially hazardous situation

Additional icons shown in the instruction manual:

See instruction manual and documents delivered with the

Important and useful information. Information does not warn

Hints for use.

This manual has references to other CareFusion documentation, including:

- 640412 07 00 SeS general system Product Requirement Specification.

Page 10/296 Version 06.02 • 2017-07-04

"System Configuration" utility

Version 06.02 • 2017-07-04 Page 11/296

Windows required access-right:

Example of a license & validation code sheet.

Page 12/296 Version 06.02 • 2017-07-04

Devices and hardware options

Measurement devices with hardware options

Workstation with a hardlock (Dongle)

Version 06.02 • 2017-07-04 Page 13/296

1.1.2 PC-Hardware and Operating System Requirements

SentrySuite® software V. 2.21 and higher

Page 14/296 Version 06.02 • 2017-07-04

Server/Sentry.NET Server/Backend System requirements

1.1.3 Directory Structure

Version 06.02 • 2017-07-04 Page 15/296

1.1.4 Default User Names and Passwords

Application User Password

The user names must not contain a space.

1.1.5 Adobe® Acrobat®

1.1.7 Antivirus: Exclusion Files/Folders

Page 16/296 Version 06.02 • 2017-07-04

1.1.8 Microsoft® Hotfixes

Version 06.02 • 2017-07-04 Page 17/296

• Choose "Update settings" - "Change active hours"

Page 18/296 Version 06.02 • 2017-07-04

1.1.9 Firewall Settings for SeS version up to 2.11

Other ports are used for named

To verify the port, run that SQL-

SELECT name, protocol_desc, port,

WHERE type_desc = 'SERVICE_BROKER'