Isp Isg 453564935121

In stal la tion a nd S erv ice Gu id e
IntelliSpace Perinatal
Rev. K.00
Pa tie n t Monit o ring
4535 649 35121

Software revision K.00.20
Published in Germany 02.2021
Internal Code: 20210209
Notice
Philips makes no warranty of any kind with regard to this material, including, but not limited to, the
implied warranties of merchantability and fitness for a particular purpose. Philips shall not be liable for
errors contained herein or for incidental or consequential damages in connection with the furnishing,
performance or use of this material.
This document contains proprietary information that is protected by copyright. All rights are reserved.
No part of this document may be photocopied, reproduced or translated to another language without
prior written consent of Philips.
For warnings and cautions concerning the application software please refer to the Instructions for Use.
The information contained in this document is subject to change without notice.
Philips assumes no responsibility for the use or reliability of its software on equipment that is not
furnished by Philips.
Federal Law (US) restricts this device to sale by or on the order of a physician.
Philips developed this system in cooperation with Massachusetts General Hospital, an affiliate of the
Harvard Medical School.
WARNING Failure on the part of the responsible individual hospital or institution employing the use of this
equipment to implement a satisfactory maintenance schedule may cause undue equipment failure and
possible health hazards.
Trademarks
Microsoft® is a U.S. registered trademark of Microsoft Corp.
Windows®, Windows Server 2019®, Windows Server 2012 R2® and Windows 10® are U.S.
registered trademarks of Microsoft Corp.
Sybase and Sybase Central are U.S registered trademarks of Sybase, Inc.
Legato™ is a U.S. registered trademark of Legato Systems, Inc.
VMware® is a registered trademark of VMware, Inc. in the United States and/or other jurisdictions.
All other product and company names mentioned may be the trademarks of their respective owners.
Acknowledgements
Automated Windows installation developed using AutoIt.
https://www.autoitscript.com/site/autoit/
IntelliSpace Perinatal uses ZedGraph.

Printing History
Edition..................Part Number...............Release ......................................... Print Date
First Edition..........M1381-9000J .............A.02.00......................................August 1999
Second Edition......M1381-9000K............B.00.00...................................... March 2000
Third Edition........M1381-9000L ............B.01.00................................ September 2000
Fourth Edition ......M1381-9000M...........B.01.00...................................... March 2001
Fifth Edition .........M1381-9000N ...........C.00.00 ......................................... July 2001
Sixth Edition.........M1381-9000P ............C.01.00 ............................... November 2001
Seventh Edition.....M1381-9000Q ...........C.01.01 ..................................... March 2002
Eighth Edition ......M1381-9000R............C.01.01 (new PC hardware) ....October 2002
Ninth Edition .......M1381-9000S ............D.00.00 ........................................April 2003
10th Edition .........M1381-9000T............D.00.01 .....................................August 2003
11th Edition .........M1381-9000U ...........D.00.02 ....................................January 2004
12th Edition .........M1381-9000V............D.01.00 ......................................... July 2004
13th Edition .........M1381-9000W ..........D.01.10 .....................................August 2004
14th Edition .........M1381-9000X............D.01.11 ..................................February 2005
15th Edition .........M1381-9000Y ............D.01.13 ............................... September 2005
16th Edition .........M1381-9000Z............E.00.00.....................................January 2006
17th Edition .........M1381-900AA ...........E.00.10...................................... March 2006
18th Edition .........M1381-900AB ...........E.00.20......................................... June 2006
19th Edition .........M1381-900AC ...........E.00.21................................ December 2006
20th Edition .........M1381-900AD...........E.00.22......................................... May 2007
21st Edition ..........M1381-900AE ...........E.00.23 ............................... November 2007
22nd Edition.........453564115251. ..........F.00.10 ......................................August 2008
23rd Edition .........453564122361 ...........F.00.11 .....................................January 2009
24th Edition .........453564159421 ...........F.00.12 ......................................... May 2009
25th Edition .........453564159421 ...........F.00.13 ................................ December 2009
26th Edition .........453564159821 ...........G.00.00 ......................................... July 2010
27th Edition..........453564245931............G.00.10................................November 2010
28th Edition..........453564271661............G.00.20..........................................July 2011
29th Edition..........453564298831............G.00.20SP1....................................July 2011
30th Edition..........453564290221............H.00.00................................December 2012
31st Edition...........453564423841............H.00.10........................................April 2013
32nd Edition.........453564440151.............H.00.15........................................June 2013
33rd Edition..........453564 62121..............H.00.20..................................October 2013
34th Edition..........453564531191.............J.00.00................................ December 2014
35th Edition..........453564561931.............J.00.10.......................................March 2015
36th Edition..........453564576651.............J.00.20...........................................July 2015
37th Edition..........453564617711.............J.00.20 (new hardware)..........February 2016
38th Edition..........453564626051.............J.00.21..........................................May 2016
39th Edition..........453564718891.............K.00.10.........................................July 2017
40th Edition..........453564791161.............K.00.11.......................................April 2018
41st Edition..........453564845701.............K.00.12.......................................March 2019
42nd Edition.........453564935121.............K.00.20...................................February 2021
Contents
1Table Of Contents
1 Overview 1
What is IntelliSpace Perinatal? 1

Who Should Read This Guide 1
About This Guide 1
Special Tools 2
Service Packs 2
Conventions in This Document 2
Sterilization and Cleaning 2
2 Testing and Maintenance 3
Introduction 3
Terminology and Definitions 4
Recommended Frequency 4
Symbol Identification 4
System Overview 5
Centralized System 5
Decentralized System 6
Uninterruptible Power Supply (UPS) 7
Computer Power Consumption 7
Testing Sequence 8
Visual Inspection 9
Safety Tests 9
Warnings, Cautions, and Safety Precautions 9
Safety Test Procedures 10
System Test 12
What is a Medical Electrical System? 12
General Requirements for a System 12
System Example 13
System Installation Requirements 13
Required Protective Measures at System Installation 15
Case 1: Medical Device Combined with Medical Device 15
Case 2: Medical Device Combined with a Non-Medical Device 16
Case 3: Medical Device Combined with a Medical or 
Non-Medical Device with one Device in a Non-Medically-Used Room 19
System Test Procedure 21
Test and Inspection Matrix 22
Safety Test Procedures 27
Reference: Allowable Values for Safety Tests based on IEC/EN 60601-1 34
When to Perform Tests 34
Reporting of Test Results 35
Carrying Out and Reporting Tests 36
Test and Inspection Responsibility 38
4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - i

After Installation Testing or Repair 39
Safety and Site Preparation 39
Safety Notes for Cabling and Installation 39
Network Verification 40
Electrostatic Handling Precautions 40
Emissions and Immunity 40
Guidance and Manufacturer’s Declaration 41
Recommended Separation Distances 44
3 System Description 47
Overview 47
4 New System Setup 49
Introduction 49
Computer Roles 49
Order in which to Perform Tasks 49
Installation Checklists 50
Tasks 67
Remote Desktop Clients 78
5 Setup Details 79
Introduction 79
Installing a Client on a Cart (Mobile Client) 79
Client UPS 79
Configuration 79
Moving the Cart 80
Connecting Fetal Monitors 81
M1350, M1351/53 and Avalon FM20/30/40/50 Monitors 81
Other Fetal Monitors 81
Connecting Four Fetal Monitors 82
Connecting More than Four Fetal Monitors 82
Protocol Conversion 82
Hewlett-Packard / Agilent / Philips Fetal Monitors 82
Connecting to the Network 86
Network Connections 86
Switches 86
Network Specifications 86
Cable Specifications 87
Cabling a LAN 88
Installing and Configuring Remote LAN Clients 89
Limitations and Prerequisites 89
Installation and Configuration 89
Installing and Setting up a Serial Port Server 92
Introduction 92
Host Computer Network Settings 93
Connect Port Server 94
ii - IntelliSpace Perinatal Installation and Service Guide - 4535 649 35121

Port Server Network Settings 95
Configure Serial Port Server 96
Install Software for Firmware Check 5610-8/16 99
Install NPort Server 5610 and 6610 series common driver software 100
Configure IntelliSpace Perinatal 103
Connect Fetal Monitors 103
Check Fetal Monitor to Bed Connection 103
Using the Serial Port Server at a Different Computer 103
Replacing a Serial Port Server 105
Installing Word and Excel Templates 110
Overview 110
IntelliSpace Perinatal Key for Reports and Statistics 113
New Installation 113
6 Network Based Storage 115
Introduction 115
Prerequisites 115
Local Storage Directory 115
Location of the Archive Computer Function 115
Changing the Archive Computer Function to a Different Machine 116
Moving the NBS Location to Another Location 116
Changing NBS User Credentials with IntelliSpace Perinatal Running 116
NBS Folder Structure and Archive Index 116
Service Storage Tool 117
Additional References for Network Based Storage 118
Integration Testing 118
7 Troubleshooting 119
Networking and System Setup Problems 119

Network Storage Access 123
Checking Network Connectivity 123
Checking File Access 123
Closing the Network Connection 123
Hardware Problems 123
Fetal Monitor Connection / Data Acquisition Problems 124
Application Problems 126
8 IntelliSpace Perinatal Services 129
Services Overview 129

General Service behavior 129
New System startup and shutdown functionality 130
Overall System state 130
Single service or application state 131
Detailed Technical Information on Services 133
IntelliSpace Perinatal Service and Application Monitoring and Recovery 134
4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - iii
9 Maintenance 139
Introduction 139
Recommended Maintenance 139
IntelliSpace Perinatal Backup 140
Rebooting the Remote Desktop Session Host Server 140
Virus Protection 140
External Database Performance 140
Manual Purge 141
Automatic Purge 141
10 System Support 143
Log Files 143

HP Service Pack for ProLiant 145
HP Insight Diagnostics Online Edition for Windows 145
11 Configuration Verification Procedure 147
Customer Verification 147

Configuration Verification 147
12 Component Installation (Upgrade/Repair) 149
Introduction 149
Software Distribution 149
Computer System Board Replacement 150
Additional Memory 150
Network Interface (LAN) Card 150
DVD-ROM Drive 150
Primary Hard Disk Drive 151
BIOS / Firmware Update Verification 151
13 Renaming a Computer 153
Changing a Server Name 153

Changing a Client Name 153
Replacement Client 153
14 Repairing/Replacing Hardware and Media 155
Repair Strategy 155

Hardware Defects 155
Substituting a Computer 159
Software Media Defects 159
Parts Stocking 160
Fetal Monitor Connections 160
Power Supply 160
Cabling 160
Serial Port Servers 161
HP rp5810 (453564552581) 162
iv - IntelliSpace Perinatal Installation and Service Guide - 4535 649 35121

HP Proliant DL180 G9 (453564552601) 163
HP Proliant DL180 G9 (453564672431) 164
HP Proliant DL360 G10 (453564764651) 165
HP Proliant DL360 G10 V2 (453564913991, 453564914891) 166
PC Common Parts 167
Software Media and Documentation 168
15 Tools 169
Overview 169
Standard Windows Tools 169
Database Tools 170
IntelliSpace Perinatal Tools 170
Windows Tools 173
Disk Defragmenter 173
IntelliSpace Perinatal Tools 173
External Database Administration Tool (External DB) 173
Patient Data Administration Tool (Internal DB) 174
Database Anonymize Tool 175
Update Archive Tool 175
Database Rebuild Tool 176
Backup Tool 178
NBS Check Tool 185
LogFile Viewer for Error Logs 188
Installation Record 193
Fetal Monitor Spy (FMSpy) 193
GetLog 196
NetTest 197
Active Directory Test Tool 198
16 Document Export (DOX) 199
Overview 199
Document Export Computer 199
Using MS Office for Document Export 199
Installing MS Office for Document Export 200
Word Options 200
Troubleshooting 200
Printer Drivers for Document Export 200
Overview 201
Advanced Printer Properties and Printing Defaults 201
Printing Preferences 201
IntelliSpace Perinatal Document Export Map Settings 201
Adobe PDF 201
17 IntelliSpace Perinatal Repair and Recovery 203
What To Do If... 203

Which Tool? 205
4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - v

Recovery Process After Hardware or System Software Failure 206
Recovery Process: Internal Server with RAID Disk Array
(including High-End Small Architecture Systems) 206
Recovery Process: Internal Server with Archiving 
(no RAID / including Standard Small Architecture Systems) 
and all Internal Servers with a Backup Drive D: and/or E: and/or F: 208
Recovery Process: High End Data Acquisition Server 214
Recovery Process: Internal Server without Archiving 214
Recovery Process: External Database Server 215
Recovery Process: Remote Desktop Session Host Server 216
Recovery Process: Client 216
All Scenarios: System Startup after Recovery Warning 217
Local Data Recovery Tool 218
Using the Local Data Recovery Tool 218
Data Recovery Process 218
Automatic Recovery on Internal Server/Archive Server 220
Manually Running the Local Recovery Tool 220
Link Recovery Tool 221
When to Use the Link Recovery Tool 221
Prerequisites 221
Using the Link Recovery Tool 221
Configuration Backup (Internal Server Only) 222
Preconditions 222
Retrieve from Archive (RFA Wizard) 223
Checks Before Running the RFA Tool 224
Special Considerations When Using RFA on Linked Systems 224
Using the RFA Tool 224
Importing Patient Data Created by OB TraceVue A.02.00 or Higher 226
Importing Patient Data Created by OB TraceVue A.01.64 227
Finalizing Imported Patient Data 227
Merging Patient Data From Another Archive 227
Merge Patient Data From Another Archive (Archive View-Only Mode) 227
Restoring the External Database 227
After Running the RFA Tool 229
Log File 229
Report Files 229
Error Messages 230
HP Array Configuration Utility 231
Locating the Array Configuration Tool 231
Configuring a Replacement Disk 231
18 System Check 233
19 IntelliSpace Perinatal Installation 235
Introduction 235
When to Reinstall IntelliSpace Perinatal 235
vi - IntelliSpace Perinatal Installation and Service Guide - 4535 649 35121

IntelliSpace Perinatal Setup 236
Installing IntelliSpace Perinatal 236
Changing IntelliSpace Perinatal System Options 237
Running Setup 237
Install the IntelliSpace Perinatal Software 238
System Settings 239
Configure Settings 242
Finishing Setup 251
Restoring the IntelliSpace Perinatal Philips Password 251
Installing / Upgrading Word and Excel Templates 252
Uninstalling IntelliSpace Perinatal 252
Internal Server 252
Clients 252
Uninstalling IntelliSpace Perinatal Link 253
20 Windows Installation 255
Operating System Installation and Configuration 255

For All Software-only Versions of IntelliSpace Perinatal 255
For All Versions of IntelliSpace Perinatal including Hardware 256
Additional Information 258
System Check Tool 258
DHCP Server 258
UPS 258
21 Upgrades 259
Introduction 259
User Accounts 259
Moving Functionality During the Upgrade 259
Upgrading from Rev G.00, H.00, J.00 260
Upgrade with new or continuing Hardware 260
Upgrading IntelliSpace Perinatal computers other than External and Internal Server 265
Upgrading from Rev. K.00 267
Preparation 268
Upgrading the Internal Server 269
Upgrading the External Server 270
Upgrading the Remote Desktop Session Host Server Software 271
Upgrading the Client Software 272
Upgrading an RD Client with Online Monitoring and Alarming 272
Upgrading Templates 272
Final Steps after Upgrade 273
Cleanup Old Hardware 273
Upgrading Word and Excel Templates 274
Prerequisites 274
Factory Templates and Files 274
Customized Templates and Files 274
Template Upgrade Procedure 275
4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - vii
Upgrading Customized Templates and Files 276
22 System Upgrades 277
Introduction 277
Adding IntelliSpace Perinatal RD Client Licenses 277
Adding Remote Desktop Session Host Server 277
Adding External Database Server Machine 278
Merging or Linking Systems 278
Introduction 278
Prerequisites (for Merging and for Linking) 280
Merging Systems 283
Linking Systems 287
Cleanup after Go-Live 288
Merging External Databases 289
Upgrading Small Architecture System to Internal Server 290
Upgrade Re-using the Existing Computer Hardware 290
Upgrade with New Hardware or Virtual Machine 292
Final Steps for All Upgrade Scenarios 294
Upgrading Small Architecture with External DB to Large Architecture 295
23 XDS Installation 297
Overview 297
Initial Configuration 297
24 HP ProLiant DL180 G9 (453564552601) 303
Specifications 303
Removing the Computer Cover 303
Slot Assignments for HP ProLiant DL180 G9 303
Configuration and Setup Tables 304
BIOS Version for HP ProLiant DL180 G9 304
BIOS Settings for HP ProLiant DL180 G9 304
RAID Configuration for the HP ProLiant DL180 G9 305
Interrupt Adjustments for HP ProLiant DL180 G9 306
RAID BIOS Settings for HP Proliant DL180 G9 306
25 HP ProLiant DL180 G9 (453564672431) 307
Specifications 307
Slot Assignments for HP ProLiant DL180 G9 307
BIOS Version for HP ProLiant DL180 G9 308
BIOS Settings for HP ProLiant DL180 G9 308
RAID Configuration for the HP ProLiant DL180 G9 309
Interrupt Adjustments for HP ProLiant DL180 G9 310
RAID BIOS Settings for HP Proliant DL180 G9 310
viii - IntelliSpace Perinatal Installation and Service Guide - 4535 649 35121
26 HPE ProLiant DL360 G10 (453564764651, 453564913991,
453564914891)311
Specifications 311
Slot Assignments for HPE ProLiant DL360 G10 311
BIOS Version for HPE ProLiant DL360 G10 313
BIOS Settings for HPE ProLiant DL360 G10 313
RAID Configuration for the HPE ProLiant DL360 G10 315
Interrupt Adjustments for HPE ProLiant DL360 G10 315
RAID BIOS Settings for HPE Proliant DL360 G10 316
27 HP rp5810 317
Specifications 317
Slot Assignments for HP rp5810 317
BIOS Version for HP rp5810 318
BIOS Settings for HP rp5810 318
28 Fetal Monitor Connections 321
Overview 321
Available Serial Cables 322
Cable Pin Layout 323
Fetal Monitor Cable for M1350A/B/C, 
and Avalon FM 20/30/40/50 M1380-61612 323
Fetal Monitor Cable for M1351/53 M1380-61613 323
Neoventa STAN S31 connector 324
4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - ix

x - IntelliSpace Perinatal Installation and Service Guide - 4535 649 35121
4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - xi
xii - IntelliSpace Perinatal Installation and Service Guide - 4535 649 35121
What is IntelliSpace Perinatal? 1 Overview
1Overview
1.1 What is IntelliSpace Perinatal?

The Philips IntelliSpace Perinatal system (formerly called OBTraceVue) offers high quality data
management capabilities for obstetrical care. It combines surveillance and alarming with
comprehensive patient documentation and data storage into one convenient system, giving you the
information you need to document and manage patient care in an OB department, from the first
antepartum visit up to delivery, postpartum, and discharge, across several pregnancies.
IntelliSpace Perinatal can be installed as a standalone system or on a network of a server and clients that
allows simultaneous monitoring of many patients.
Key options include patient data storage; an External Server is used, for example, to facilitate forms
based patient records and statistical reporting; and an optional HL7 link for ADT and ORU messages.
The users of IntelliSpace Perinatal are obstetrics specialists such as physicians, midwives, and nurses.
IntelliSpace Perinatal is in conformity with the requirements of the European Medical Devices
Directive 93/ 42/EEC. It is classified into Class IIa according to Annex IX rule 10 and carries the CE
marking accordingly.
1.2 Who Should Read This Guide

This book is intended for qualified personnel authorized to install, service or repair an IntelliSpace
Perinatal system. This guide is for personnel, who:
• Installs IntelliSpace Perinatal hardware and software.
• Configures an installation.
• Upgrades an installation.
• Needs to resolve IntelliSpace Perinatal problems.
A good understanding of the English language is a requirement. You must be familiar with the
Windows operating system and be able to use its standard tools.
1.3 About This Guide

An IntelliSpace Perinatal system is made up from specified standard hardware components and
operates in a standard Microsoft Windows networking environment. Much detailed installation and
configuration information already exists in manuals written especially for these standard products.
Each component of an IntelliSpace Perinatal system is shipped with support documentation that you
must use. Any settings given in this guide override factory defaults and must be implemented.
The electrical, physical, environmental, and performance specifications for IntelliSpace Perinatal are
given in its Technical Data Sheet.
4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - 1

1 Overview Special Tools
1.4 Special Tools

You do not need any special tools for hardware installation.
Under some circumstances it may be necessary to perform a Safety test using an appropriate Safety
Tester. Refer to Testing and Maintenance on page 3.
For details about wall cabling, wallplates, and connectors, refer to the IntelliSpace Perinatal Site
Preparation and IT Specification Guide.
1.5 Service Packs

Before setting up a new system or reinstalling IntelliSpace Perinatal software you should always check
Philips InCenter for the latest IntelliSpace Perinatal service pack(s) and ensure that this is installed too.
After applying an IntelliSpace Perinatal service pack, you must back up the configuration.
1.6 Conventions in This Document

The following conventions for notes, cautions, and warnings are used in this guide:
Note:
A note calls attention to an important point in the text.
Caution:
A caution alerts you where special care is necessary for the safe and effective use of the product. Failure
to observe a caution may result in minor or moderate personal injury or damage to the product or
other property, and possibly in a remote risk of more serious injury.
Warning:
A warning alerts you to a potential serious outcome, adverse event or safety hazard. Failure to observe a
warning may result in death or serious injury to the user or patient.
All software texts in this guide are quoted in English. Depending on configuration, your system may
show software texts in another language.
1.7 Sterilization and Cleaning

The components of an IntelliSpace Perinatal system do not require sterilization before use. Care and
Cleaning instructions are provided in the IntelliSpace Perinatal Instructions for Use.
2 - IntelliSpace Perinatal Installation and Service Guide - 4535 649 35121

2
2Testing and Maintenance
2.1 Introduction
This chapter provides a checklist of the testing and maintenance procedures to ensure the performance
and safety of the system.
These tests must be performed only by qualified personnel certified by the responsible organization.
Qualifications required are: training on the subject, knowledge, experience and acquaintance with the
relevant technologies, standards and local regulations. The personnel assessing safety must be able to
recognize possible consequences and risks arising from non-conforming equipment.
All recurring safety and performance assurance tests must be performed under equal environmental
conditions to be comparable.
Preventive Maintenance refers specifically to the series of tests required to make sure the measurement
results are accurate. The accuracy and performance procedures are designed to be completed as
specified in the following sections or when readings are in question.
This chapter highlights issues that may affect the safety of the patient, hospital staff, and the
maintainer. It also shows the relationship of medical to non-medical devices.
For detailed instructions on cleaning of IntelliSpace Perinatal and its accessories, see the IntelliSpace
Perinatal Instructions for Use.
WARNING IT hardware used with IntelliSpace Perinatal is classified as IT equipment (IEC/EN 60950) and is not
intended for placement in the patient vicinity.
The patient vicinity is defined as anywhere within 1.5 meters (5 feet) of the perimeter of the patient's
bed and 2.5 meters (8.2 feet) from the floor.
A Safety Isolation Transformer must be used for IT products that are placed in the patient vicinity.
CAUTION Servers must be protected from unauthorized user access. Install servers in a room that can only
accessed by authorized personnel.
NOTE It is the customer's responsibility to grant necessary access to the service provider person as this is
needed for support or maintenance activities.

2 Testing and Maintenance Terminology and Definitions
2.2 Terminology and Definitions

The following terms and definitions are used throughout this chapter and taken from the international
standards IEC/EN 60601-1 and IEC/EN 62353.
Medical System: a medical electrical system is a combination of at least one medical electrical device
and other electrical equipment, interconnected by functional connection or use of a multiple portable
socket-outlet.
Patient Vicinity: any area in which intentional or unintentional contact can occur between the patient
and parts of the medical system or between the patient and other persons who have had contact with
parts of the medical system. The patient vicinity is defined anywhere within 1.5m (5 feet) of the
perimeter of the patient's bed and 2.5m (8.2 feet) from the floor.
Separation Device/Transformer: a component or arrangement of components with input parts and
output parts that, for safety reasons, prevent a transfer of unwanted voltage or current between parts of
a medical system.
Multiple Portable Socket-Outlet: a combination of two or more socket-outlets intended to be
connected to or integrated with flexible cables or cords, which can easily be moved from one place to
another while connected to the power mains.
Functional Connection: an electrical connection for transfer of signals and/or power.
Tests: Safety or Performance Assurance test procedures which may consist of several steps.
2.3 Recommended Frequency

See Recommended Maintenance on page 139. The procedures listed in this chapter as suggested for
periodic care, maintenance and backup of mass-storage devices.
These suggestions do not supersede local requirements.
2.4 Symbol Identification

Equipotential Terminal 
This symbol is used to identify terminals which are connected together, bringing various equipment or
parts of a system to the same potential. This is not necessarily earth potential. (The value of potentials
of earth may be indicated adjacent to the symbol.)
International Caution Symbol 
This symbol indicates that the operator should refer to the product instruction manual before
beginning a procedure.
Earth Terminal 
This symbol identifies the terminal for connection to an external protective earth.
Resistance Measuring Device
Follow the Instructions for Use

System Overview 2 Testing and Maintenance
2.5 System Overview

2.5.1 Centralized System
This configuration shows a typical IntelliSpace Perinatal system, in which the computer is situated at a
central station and the fetal monitor is at the patient's bedside.
Figure 1 System Overview, Office (without isolation transformer)

2 Testing and Maintenance System Overview
2.5.2 Decentralized System

This configuration shows a typical IntelliSpace Perinatal system, in which both the fetal monitor and
computer are situated at the patient's bedside.
Figure 2 System Overview, Bedside (with isolation transformer)
WARNING Do not connect the fetal monitor or an adult monitor to this isolation transformer.

System Overview 2 Testing and Maintenance
2.5.3 Uninterruptible Power Supply (UPS)

An uninterruptible power supply (UPS) will, in the event of a mains power failure, supply power for a
short period of time.
The configuration in Figure 3 shows a typical IntelliSpace Perinatal system comprising of an isolation
transformer, UPS, computer with display and fetal monitor:
~ UPS
Medical
Isolation
Transformer
RS232
~ Fetal Monitor
Figure 3 UPS in Patient Vicinity
2.5.4 Computer Power Consumption

The current rating information on the computer label is not relevant to IntelliSpace Perinatal, because
it refers to the maximum possible load conditions.
Maximum load conditions would include things such as a high-performance graphics card, CD-writer,
maximum number of processors, maximum system RAM, maximum number of hard disks, maximum
number of cards, and other accessories. This “worst-case” scenario is not implemented with the
IntelliSpace Perinatal system.
The IntelliSpace Perinatal maximum power consumption is 300VA at 100-127V as printed on the
isolation transformer (M1389-60001). This transformer controls the total power which is supplied to
the IntelliSpace Perinatal unit (UPS + computer + display). The maximum current for this unit is
limited to 3.2A by two fuses in the isolation transformer.

2 Testing and Maintenance Testing Sequence
2.6 Testing Sequence

Summary of the recommended sequence of testing:
Start
Select the test See Reference: Allowable Values for Safety Tests
based on IEC/EN 60601-1 on page 34.
Visual Inspection See Visual Inspection on page 9.
Safety Tests See Safety Tests on page 9.
Performance Tests See Test and Inspection Matrix on page 22.
Reporting of Results See Reporting of Test Results on page 35.
Evaluation of Results See Test and Inspection Responsibility on

page 38
Check and prepare for normal
If any single test fails, testing must be discontinued immediately and the device under test must be
repaired or labeled as defective.

Safety Tests 2 Testing and Maintenance
2.6.1 Visual Inspection
2.6.1.1 Before Each Use

Check all exterior housings for cracks and damage. Check the condition of all external cables, especially
for splits or cracks and signs of twisting. If serious damage is evident, the cable should be replaced
immediately. Check that all mountings are correctly installed and secure. Refer to the instructions that
accompany the relevant mounting solution.
2.6.1.2 After Each Service, Maintenance or Repair Event

Ensure all fuses accessible from the outside comply with the manufacturer’s specification.
Check:
• the integrity of mechanical parts, internally and externally.
• any damage or contamination, internally and externally.
• that no loose parts or foreign bodies remain in the device after servicing or repair.
• the integrity of all relevant accessories.
2.6.1.3 Power On Test

See the "Power On" test procedure in Test and Inspection Matrix on page 22.
2.7 Safety Tests

Safety tests are comprised of the following tests performed on the monitoring system:
• detachable power cord protective earth resistance
• equipment leakage current
• system test (if required)
Safety test requirements are set according to international standards, their national deviations and
specific local requirements. The safety tests detailed in this Service Guide are derived from
international standards but may not be sufficient to meet local requirements. We recommend that you
file the results of safety tests. This may help to identify a problem early particularly if the test results
deteriorate over a period of time.
Each individual piece of equipment of the monitoring system which has its own connection to mains
or which can be connected or disconnected from mains without the use of a tool must be tested
individually. The monitoring system as a whole must be tested according to the System Test
procedure.
Accessories of the monitoring system which can affect the safety of the equipment under test or the
results of the safety test must be included in the tests and documented.
2.7.1 Warnings, Cautions, and Safety Precautions

• These tests are well established procedures of detecting abnormalities that, if undetected, could
result in danger to either the patient or the operator.
• Disconnect the device under test from the patient before performing safety tests.

2 Testing and Maintenance Safety Tests
• Disconnect the device under test from mains before performing safety tests. If this is not possible,
ensure that the performance of these tests does not result in danger to the safety analyzer operator,
patients or other individuals.
• Test equipment (for example, a Safety Analyzer) is required to perform the safety tests. Please refer to
Annex C of IEC/EN 62353 for exact requirements for the measurement equipment and for
measurement circuits for protective earth resistance and leakage currents. Refer to the
documentation that accompanies the test equipment. Only skilled technicians should perform safety
testing.
• The consistent use of a Safety Analyzer as a routine step in closing a repair or upgrade is emphasized
as a mandatory step to maintain approval agency status. You can also use the Safety Analyzer as a
troubleshooting tool to detect abnormalities of line voltage and grounding plus total current loads.
• During safety testing, mains voltage and electrical currents are applied to the device under test.
Ensure that there are no open electrical conductive parts during the performance of these tests.
Avoid that users, patients or other individuals come into contact with touch voltage.
• For Europe and Asia/Pacific, the Philips fetal monitor complies with: 
IEC 60601-1:2005 + A1:2012 / EN60601-1:2006 +AC:2013
For USA, the Philips fetal monitor complies with:
ANSI/AAMI ES60601-1:2005 + A1:2012 + C1:2009/2012 + A2:2010/2012
For Canada, CAN/CSA C22.2#60601-1-14
• Local regulations supersede the testing requirements listed in this chapter.
• If a device is connected to the medical electrical device during an installation, the resulting medical
electrical system must comply with IEC/EN 60601-1.
• Perform safety tests as described on the following pages.
2.7.2 Safety Test Procedures

Use the test procedures outlined here only for verifying safe installation or service of the product. The
setups used for these tests and the acceptable ranges of values are derived from local and international
standards but may not be equivalent. These tests are not a substitute for local safety testing where it is
required for an installation or a service event. If using an approved safety tester, perform the tests in
accordance with the information provided by the manufacturer of the tester and in accordance with
your local regulations, for example IEC/EN 60601-1 and IEC/EN 62353. The safety tester should
print results as detailed in this chapter, together with other data.
Refer to Annex C of IEC/EN 62353 for requirements for the measurement equipment and for
measurement circuits for protective earth resistance and leakage currents.
CAUTION Ensure all fuses accessible from the outside comply with the manufacturer’s specification.
Check:

Safety Tests 2 Testing and Maintenance
2.7.2.1 Hints for Correct Performance of Safety Tests

• Perform a visual inspection of all detachable power cords used with the system and include these in
all safety test procedures.
• Connection lines such as data lines or functional earth conductors may appear to act like protective
earth connections. These may lead to incorrect measurements and need to be considered during
testing. If necessary, unplug these connections.
• During measurements the equipment under test shall be isolated from earth, except the protective
earth conductor in the power supply cord.
• Position all cables and cords in such a manner that they do not influence the safety tests.
• Measurement of insulation resistance is not required.
2.7.2.2 Guideline for the Performance of Safety Tests

Connect the detachable power cord of the device under test to the safety analyzer's test mains port.
Connect the enclosure test lead of the safety analyzer to the enclosure of the device under test, for
example to the equipotential connector. For testing the applied part leakage current, connect all
applied parts to the safety analyzer using the appropriate patient lead or adapter cable. If necessary,
repeat the safety test procedure until all available applied parts have been tested. Refer to the
documentation that accompanies the safety analyzer for further details on how to set up the test. Power
on the device under test for all tests.
Figure 4 Protective Earth Resistance Test - Setup Example

2 Testing and Maintenance System Test
Figure 5 Equipment Leakage Current Test - Setup Example
NOTE The above graphics resemble the Metron QA-90 setup and are protected by copyright. Copyright
owned by Fluke (Metron).
2.8 System Test

After mounting and setting up a system, perform system safety tests according to IEC/EN 60601-1.
2.8.1 What is a Medical Electrical System?

A medical electrical system is a combination of at least one medical electrical device and other electrical
equipment, interconnected by functional connection or use of a multiple portable socket-outlet.
• Devices forming a medical electrical system must comply with IEC/EN 60601-1 edition 3 
clause 16.
• Any electrical device, such as IT equipment, that is connected to the medical electrical equipment
must comply with IEC/EN 60601-1 edition 3 clause 16 and be tested accordingly.
2.8.2 General Requirements for a System

After installation or subsequent modification, a system must comply with the requirements of the
system standard IEC/EN 60601-1 edition 3 clause 16. Compliance is checked by inspection, testing or
analysis, as specified in the IEC/EN 60601-1 edition 3 clause 16 or in this book.
Medical electrical equipment must comply with the requirements of the general standard IEC/EN
60601-1, its relevant particular standards and specific national deviations. Non-medical electrical
equipment shall comply with IEC and ISO safety standards that are relevant to that equipment.
Relevant standards for some non-medical electrical equipment may have limits for equipment leakage
currents higher than required by the standard IEC/EN 60601-1 edition 3 clause 16. These higher
limits are acceptable only outside the patient environment. It is essential to reduce equipment leakage
currents when non-medical electrical equipment is to be used within the patient environment.

System Test 2 Testing and Maintenance
2.8.3 System Example
This illustration shows a system where both the medical electrical equipment and the non-medical
electrical equipment are situated at the patient’s bedside.
Non-Medical Devices Medical Devices

Personal
Computer
Distance to patient
must be >= 1.5m
Isolation
Transformer
Key:
Power cables:
Data cables: Fetal Monitor
WARNING • Do not use additional AC mains extension cords or multiple portable socket-outlets. If a multiple
portable socket-outlet is used, the resulting system must be compliant with IEC/EN 60601-1
edition 3 clause 16. Do not place multiple socket-outlets on the floor. Do not exceed the maximum
permitted load for multiple socket-outlets used with the system. Do not plug additional multiple
socket-outlets or extension cords into multiple socket-outlets or extension cords used within the
medical system
• Do not connect any devices that are not supported as part of a system.
• Do not use a device in the patient vicinity if it does not comply with IEC/EN 60601-1. The whole
installation, including devices outside of the patient vicinity, must comply with IEC/EN 60601-1
edition 3 clause 16. Any non-medical device, including a computer running an IntelliSpace
Perinatal system, placed and operated in the patient’s vicinity must be powered via a separating
transformer (compliant with IEC/EN 60601-1 edition 3 clause 16) that ensures mechanical fixing
of the power cords and covering of any unused power outlets.
2.8.4 System Installation Requirements

• Ensure that the medical electrical system is installed in a way that the user achieves optimal use.
• Make sure the user is informed about the required cleaning, adjustment, sterilization and
disinfection procedures listed in the Instructions for Use.
• The medical electrical system must be installed in such a way that the user is able to carry out the
necessary cleaning, adjustment, sterilization and disinfection procedures listed in the Instructions for
Use.

• Ensure that the medical electrical system is installed in a way that an interruption and restoration of
power to any part of the medical electrical system does not result in a safety hazard.
• We recommend using fixed mains socket outlets to power the medical system or parts thereof. Avoid
using multiple portable socket-outlets.
• Any multiple portable socket outlets used must be compliant with IEC 60884-1 and IEC/EN
60601-1 edition 3 clause 16.
• Ensure that any part of the system connected to multiple portable socket-outlets is only removable
with a tool, that is, the multiple portable socket-outlet provides a locking mechanism to prevent
power cords from being plugged or unplugged unintentionally. Otherwise, the multiple portable
socket-outlet must be connected to a separation device. Multiple socket outlets used within the
medical electrical system must only be used for powering medical electrical equipment which is part
of the system.
• Ensure that any functional connections between parts of the medical electrical system are isolated by
a separation device according to IEC/EN 60601-1 edition 3 clause 16 to limit increased equipment
leakage currents caused by current flow through the signal connections where necessary (e.g. leakage
current coming from non-medical electrical equipment into medical electrical equipment or
building ground voltage differences providing leakage current through grounded data cables). This
only works if the equipment leakage current of the respective medical electrical system parts is not
exceeded under normal conditions. This isolation is especially important where the non-medical
electrical equipment leakage currents can pass to the medical electrical equipment in the system or
building ground voltage differences can pass to the medical electrical equipment via ground in a data
cable connection in the system.
• Avoid increase of equipment leakage currents when non-medical electrical equipment within the
medical electrical system is used. This only works if the equipment leakage current of the respective
medical electrical system parts is not exceeded under normal conditions. Use additional protective
earth connection, separation device or additional non-conductive enclosures.
• Within the patient environment it is important to limit electrical potential differences between
different parts of a system. If necessary, use potential equalization equipment (equipotential cable) or
additional protective earth connections.
• Medical electrical equipment used in medical rooms must be connected to potential equalization
equipment (equipotential cable) to avoid electrical potential differences. Check your local
requirements for details.

2.8.5 Required Protective Measures at System Installation

For any IT equipment (IEC/EN 60950-1) operated in patient vicinity ensure that the equipment
leakage current does not exceed the limits described in IEC/EN 60601-1. Use a separation device to
ensure compliance. After installation of IT equipment in patient vicinity, an enclosure leakage current
test is required.
2.8.6 Case 1: Medical Device Combined with Medical Device

If you combine a medical device with another medical device (including Philips specified displays) to
form a medical electrical system according to IEC/EN 60601-1 edition 3 clause 16, no additional
protective measures are required. The medical electrical devices may be located in or outside the patient
vicinity in a medically used room. This is valid as long as the medical devices are connected to separate
mains outlets. No system test is required.
If the combined medical devices are connected to the same multiple portable socket outlet an enclosure
leakage current test of the entire device combination on the multiple portable socket outlet is required
to ensure that the resulting protective earth leakage current and equipment leakage current does not
exceed the limits of IEC/EN 60601-1 edition 3 clause 16. Avoid using multiple portable socket outlets.
The medical electrical devices may be located in or outside the patient vicinity in a medically used
room. If the limits are exceeded, additional protective measures are required, e.g. a separation device or
the connection of each device to separate mains.

2.8.7 Case 2: Medical Device Combined with a Non-Medical Device

If you combine a medical device with a non-medical device to form a medical electrical system
according to IEC/EN 60601-1 edition 3 clause 16, additional protective measures are required, e.g.
usage of a separation device. The medical electrical devices or the IT equipment may be located in or
outside the patient vicinity in a medically used room. After system installation including protective
measures, a system test is required to ensure that the resulting equipment leakage current and applied
part leakage current does not exceed the limits of IEC/EN 60601-1 edition 3 clause 16.
For any IT equipment (IEC/EN 60950-1) operated in patient vicinity ensure that the equipment
test is required.

If the combined devices forming the medical electrical system are connected to the same multiple
portable socket outlet, ensure that the resulting protective earth leakage current and equipment leakage
current do not exceed the limits of IEC/EN 60601-1 edition 3 clause 16. The medical electrical devices
or IT equipment may be located in or outside the patient vicinity in a medically used room. Avoid
using multiple portable socket outlets. If the limits of IEC/EN 60601-1 edition 3 clause 16 are
exceeded, additional protective measures are required, e.g. a separation device or the connection of each
device to separate mains.

For any IT equipment (IEC/EN 60950) operated in patient vicinity, ensure that the equipment
test is required.

2.8.8 Case 3: Medical Device Combined with a Medical or 

Non-Medical Device with one Device in a Non-Medically-Used Room
If you combine a medical device with a medical or non-medical device to form a medical electrical
system according to IEC/EN 60601-1 edition 3 clause 16 using a common protective earth connection
and one of the devices is located in a non-medically used room, additional protective measures are
required, for example usage of a separation device or additional protective earth connection. The
medical electrical devices or IT equipment may be located in or outside the patient vicinity. After
system installation including protective measures, a system test is required to ensure that the resulting
equipment leakage current does not exceed the limits of IEC/EN 60601-1 edition 3 clause 16.

If you combine a medical device with a medical or non-medical device to form a medical electrical
system according to IEC/EN 60601-1 edition 3 clause 16 using two separate protective earth
connections and one of the devices is located in a non-medically used room creating a potential voltage
difference, additional protective measures are required, e.g. usage of a separation device or additional
protective earth connection. The medical electrical devices or IT equipment may be located in or
outside the patient vicinity. After system installation including protective measures, a system test is
required to ensure that the resulting equipment leakage current does not exceed the limits of IEC/EN
60601-1 edition 3 clause 16.

2.8.9 System Test Procedure

If the medical electrical device has already been tested as a standalone device e.g. during factory safety
testing, an equipment leakage current test must only be performed once the device is connected to
another electrical device / system. If the medical electrical system has not been tested as a standalone
device, the device has to be tested as a standalone device (without connection to the system) and as part
of the system (with connection to the system).
Connect the detachable power cord of the device under test to the safety analyzer's test mains port.
Connect the enclosure test lead of the safety analyzer to the enclosure of the device under test, for
example to the equipotential connector. Refer to the documentation that accompanies the safety
analyzer for further details on how to set up the test.
Test Expected Test Results
Equipment Leakage Current Sys 1 <= 100A

Test (Normal Condition)
Equipment Leakage Current Sys 2 <= 300A
Test (Single Fault Condition)
After the testing of the device as a standalone device and as part of the system, check that the resulting
values (without connection and with connection to the system) do not differ by more than +/- 10%
from each other.
2.8.9.1 Sys 3 - Protective Earth Leakage Current of Multiple Socket Outlets

If the devices in the medical electrical system are connected to a multiple portable socket outlet the
resulting protective earth leakage current needs to be determined. All system components must be
connected to the multiple portable socket outlet and be switched on during this measurement.
Protective Earth Leakage Sys 3 <= 300A

Current of Multiple Socket
Outlets
Refer to the documentation that accompanies the safety analyzer for further details on how to set up
the test.
2.8.9.2 Equipment Leakage Current Test - Setup Example

When running safety tests on the peripheral components of the system, refer to the documentation
included with those products.
Ground leakage current limits apply to the power cables between:
Mains supply isolation transformer (required if computer & Display in patient vicinity)  UPS
Computer and Display Monitor
Whenever you connect a patient monitor to the IntelliSpace Perinatal system perform the Test,
Inspection and Safety tests defined for that monitor. Refer to the documentation included with the
patient monitor. If significant parts of the monitor have been exchanged, repaired, upgraded or worked
on in any way you may be required to perform additional tests.

22Test and Inspection Matrix
Testing and Maintenance

2.9 Test and Inspection Matrix
Test Procedure Test or “Inspection” to Perform Expected Test Results What to Record on
Name Service Record
Visual Inspect all system components for obvious damage. Expected answers are “yes”. V:P or V:F
Are they free of damage? If so, Visual test is passed. where P=Pass and F=Fail
Power On Power on the computer(s) and/or peripheral(s). Expected answers are “yes”. PO:P or PO:F
Does the self-test complete successfully? If so, Power On test is passed. where P=Pass and F=Fail
Are user interface controls operational (for example, keyboard, mouse, display, sound) and is the
picture quality of the trace display appropriate?
Start IntelliSpace Perinatal:
- Does the train engine icon animate without flashing?
- Is the IntelliSpace Perinatal icon bar active and accessible?
Performance Perform all individual Performance Tests detailed below. Expected answer is “yes”. P:P or P:F
Do all the individual Performance Tests pass? If so, Performance Test is passed. where P=Pass and F=Fail
Audible Alarms If audible alarms are to be used on this computer, check the Alarm Sound. Expected answer is “yes”. A:P or A:F
Click on the alarming symbol (while no alarm is active) and test all alarm levels. If so, Performance Test is passed. where P=Pass and F=Fail
Is the sound volume adequate in the respective environment?
WARNING: Do not use keyboards or other peripheral devices that bear the risk of
unintentionally muting the sound.
312966

Name Service Record
Performance Expected answers are “yes”. PSW:P or PSW:F
Step Action
SoftWare If so, Software test is passed. where P=Pass and F=Fail
1. Start IntelliSpace Perinatal.
• Does the train icon animate without flashing?

• Is the correct system date/time displayed? (Year must be 4 digits).
• Is the IntelliSpace Perinatal icon bar active and accessible?
• Does the Philips Configuration screen display the correct software
revision?
2. Only if storage option exists:
On the Archive machine, start the System Console. 
Click Processes -> Storage.
• Do all applicable folders have the status Available = yes?
• Is the Current Archive Directory correct?
312966

Name Service Record
Performance
SoftWare Step Action
(continued) 3. Check Remote Desktop Session Host server.

At a computer connected to the hospital network:
Start Windows Internet Explorer, connect to the Remote Desktop Session Host
server.
Enter http://<ip address> (IP address of the Remote Desktop Session Host server
external NIC) 
or http://<server name> (Remote Desktop Session Host server must be registered in the
hostname locating service (e.g. DNS) of hospital network.
• Does the IntelliSpace Perinatal web page open?
• Does the Remote Desktop client start?
If the optional online monitoring and alarming capability is installed at the

Remote Desktop Client perform the test
Audible Alarms.
312966

Name Service Record
Performance For each fetal monitor connected to a computer: Expected answers are “yes”. PRS:P or PRS:F
RS-232 At the fetal monitor generate a fetal trace (only one trace at a time). If so, RS-232 test is passed. where P=Pass and F=Fail
At the IntelliSpace Perinatal computer:
• Does the trace appear in the single trace display?
• Does the data appear in the expected bed?
Performance Serial For each fetal monitor connected to a serial port server: Expected answers are “yes”. PSPS:P or PSPS:F
Port Server At the fetal monitor generate a fetal trace (only one trace in the IntelliSpace Perinatal system at If so, serial port server test is where P=Pass and F=Fail
a time). passed.
At the IntelliSpace Perinatal host computer of the serial port server:
• Does the trace appear in the expected bed?
Performance LAN For each fetal monitor connected via LAN: Expected answers are “yes”. PLANFM:P or
Fetal Monitor At the fetal monitor generate a fetal trace (only one trace in the IntelliSpace Perinatal system at If so, the LAN FM test is passed. PLANFM: F
a time). where P=Pass and F=Fail
• Does the trace appear in the expected bed?
Verify IntelliSpace Perinatal log file of the hosting client.

• Is it free of error messages regarding the fetal monitor connection?
Safety Computer In Patient Vicinity  S:P
The computer/display (and client UPS) in the patient vicinity must be connected to a Medical  where P=Pass
Isolation Transformer. The system must be connected as follows: 

Mains supply isolation transformer (required if Computer & Display in patient vicinity)  
UPS Computer & Display Monitor
Do the isolation transformer and fetal monitor have additional protective earth connections? If the answer is “yes”, Safety test
Refer to System Overview on page 5. is passed.
If the answer is “no”, perform
the safety tests mentioned below.
312966

Name Service Record
Safety (continued) Computer Not In Patient Vicinity 
Does the computer have fetal monitor connections? If the answer is “no”, Safety test
is passed.
If the answer is “yes”, go to next
Step.
Does each fetal monitor have an additional protective earth connection? If the answer is “yes”, Safety test
Refer to System Overview on page 5. is passed.
If the answer is “no”, perform
the system tests 1-2.
Safety (S1) Protective Earth Continuity Test. With mains cable max. S(1):P/X1 or F/X1 
See S 1 - Protective Earth Resistance on page 28 impedance = X1 (<=300mOhm)
where P=Pass and F=Fail
System (Sys 1-3) System Safety Test Enclosure Leakage Current / Normal Condition. Normal condition maximum Sys 1:P/X1 or F/X1 
See Sys 1 - System Equipment Leakage Current - NC (normal condition) on page 29. leakage current = X1 (<= 100uA) Sys 2:P/X2 or F/X2
Sys 3:P/X3 or F/X3
System Safety Test Enclosure Leakage Current / Single Fault Condition. Single fault maximum leakage where P=Pass and F=Fail
See Sys 2 - System Equipment Leakage Current - SFC (single fault condition) on page 30. current = X2 (<= 300A)
If the devices in the medical electrical system are connected to a multiple portable socket outlet, Protective earth leakage 
the resulting protective earth leakage current needs to be determined. All system components current of multiple socket 
must be connected to the multiple portable socket outlet and be switched on during this outlets = X3 (<= 300A)
measurement.
See Sys 3 - Protective Earth Leakage Current of Multiple Socket Outlets on page 21.
Installation Service Check the installation records at all Internal Server machines where the SP has been installed. Expected answer is "yes". ISP:P or ISP:F 
Pack Does it state:  where P=Pass and F=Fail
Installed <revision code> SP Level <n> at: <date> <time>
where n = SP level?
312966
Test and Inspection Matrix 2 Testing and Maintenance
2.9.1 Safety Test Procedures

Use the test procedures outlined here only for verifying the safe installation or service of the product.
The setups used for these tests and the acceptable ranges of values are derived from local and
international standards but may not be equivalent. These tests are not a substitute for local safety
testing where it is required for an installation or a service event. If using an approved safety tester,
perform the tests in accordance with the information provided by the manufacturer of the tester and in
accordance with your local regulations, for example IEC/EN 60601-1 and IEC/EN 62353. The safety
tester should print results as detailed in this chapter together with other data.
Refer to Annex C of IEC/EN 62353 for requirements for the measurement equipment and for
measurement circuits for protective earth resistance and leakage currents.
Supply mains Protective earth
L, N Supply mains terminals PE Protective earth terminal

Mains part Applied part
F-type applied part Measuring device
Resistance measuring device Connection to accessible con-

ductive parts
......... Optional connection
CAUTION After each service, maintenance or repair event:

Ensure that all fuses accessible from the outside comply with the manufacturer’s specification.
Check:

2 Testing and Maintenance Test and Inspection Matrix
2.9.1.1 S 1 - Protective Earth Resistance

Test to perform:
Measuring circuit for the measurement of Protective Earth Resistance in medical electrical equipment
that is disconnected from the supply mains.
This measures the impedance of the Protective Earth (PE) terminal to all exposed metal parts of the
Device under Test (DUT), which are for safety reasons connected to the Protective Earth (PE).
Measurements shall be performed using a measuring device capable of delivering a current of at least
200 mA into 500 mOhms with maximum 24V.
This safety test is based on IEC/EN 62353.
Flex the power cord during the protective earth resistance test to evaluate its integrity. If it does not
pass the test, exchange the power cord. Then repeat the test. Report the highest value (X1).
If the protective earth resistance test fails, testing must be discontinued immediately and the device
under test must be repaired or labeled as defective. All values for current and voltage are the root mean
square (r.m.s.) values, unless otherwise stated.

2.9.1.2 Sys 1 - System Equipment Leakage Current - NC (normal condition)

Test to perform:
Measuring circuit for the measurement of Equipment Leakage Current - Direct method, according to
IEC/EN 62353.
If the medical electrical device has already been tested as a standalone device, for example during
factory safety testing, an equipment leakage current test must be performed once the device is
connected to the system network. If the medical electrical device has not been tested as a standalone
device (without connection to the system), the device must be tested as a standalone device (without
connection to the system) and as part of the system (with connection to the system). Connect the
detachable power cord of the device under test to the safety analyzer's test mains port. Connect the
enclosure test lead of the safety analyzer to the enclosure of the device under test, for example to the
equipotential connector. Refer to the documentation that accompanies the safety analyzer for further
details on how to set up the test.
Testing must be performed with all components connected (computer display - transformer system
must be tested, the RS-232 and LAN connection must be made).
Apply test to point of patient contact: fetal monitor (and report the highest value (Sys1). The system
test detects leakage problems caused by any component.
Run the test on each fetal monitor. If more than one fetal monitor is connected to the same computer
or serial port server, disconnect the power cables of the fetal monitors not being tested.
In the case of an IT-power system, the safety test measurements require special measuring of the
circuit, for example, with its own integrated TN-system or use of an external isolation transformer
attached to the safety test device.
In the patient vicinity: Run the test on each computer system (includes computer, display, UPS,
transformer). The whole system is tested together.
Outside patient vicinity: Depends on installation. See System Test Procedure on page 21. Report the
highest value (Sys1).
This safety test is based on IEC/EN 62353. All values for current and voltage are the root mean square
(r.m.s.) values, unless otherwise stated.

2.9.1.3 Sys 2 - System Equipment Leakage Current - SFC (single fault condition)
Test to perform:
Measuring circuit for the measurement of Equipment Leakage Current - Direct method, according to
IEC/EN 62353.
If the medical electrical device has already been tested as a standalone device, for example during
factory safety testing, an equipment leakage current test must be performed once the device is
connected to the system network. If the medical electrical device has not been tested as a standalone
device (without connection to the system), the device must be tested as a standalone device (without
connection to the system) and as part of the system (with connection to the system). Connect the
detachable power cord of the device under test to the safety analyzer's test mains port. Connect the
enclosure test lead of the safety analyzer to the enclosure of the device under test, for example to the
equipotential connector. Refer to the documentation that accompanies the safety analyzer for further
details on how to set up the test.
Testing must be performed with all components connected (computer display - transformer system
must be tested, the RS-232 and LAN connection must be made).
Apply test to point of patient contact: fetal monitor (and report the highest value (Sys2). The system
test detects leakage problems caused by any component.
Run the test on each fetal monitor. If more than one fetal monitor is connected to the same computer
or serial port server, disconnect the power cables of the fetal monitors not being tested.
In the case of an IT-power system, this safety test measurements require special measuring circuit, for
example with its own integrated TN-system or use of an external isolation transformer attached to the
safety test device.
In the patient vicinity: Run the test on each computer system (includes computer, display, UPS,
transformer). The whole system is tested together.
Outside patient vicinity: Depends on installation. See System Test Procedure on page 21. Report the
highest value (Sys2).
This safety test is based on IEC/EN 62353. All values for current and voltage are the root mean square
(r.m.s.) values, unless otherwise stated.

2.9.1.4 SPS 1 - Protective Earth Resistance (Serial Port Server)

Test to perform:
Measuring circuit for the measurement of Protective Earth Resistance in Information Technology
electrical equipment that is disconnected from the supply mains.
This measures the impedance of the Protective Earth (PE) (with mains cable) to all exposed metal parts
of the Device under Test (DUT), which are for safety reasons connected to the Protective Earth (PE).
You can find metal parts of the device at the mounting screw holes.
Measurements shall be performed using a measuring device capable to deliver a current of at least 200
mA into 500 mOhms with maximum open circuit voltage of 24V.
This safety test is based on IEC/EN 60950-1.
Report the highest value (X1).
Protective Earth Resistance X1 <= 300 mOhms

Test (with mains cable)
NOTE • If the protective earth resistance test fails, testing must be discontinued immediately and the device
under test must be repaired or labeled as defective.
• All values for current and voltage are the root mean square (r.m.s.) values, unless otherwise stated.
• Flex the power cord during the protective earth resistance test to evaluate its integrity. If it does not
pass the test, exchange the power cord. Then repeat the test. If it still does not pass, follow the
instructions in the first bullet point of this note above.

2.9.1.5 SPS 2 Touch Current - NC (normal condition, Serial Port Server)

Test to perform:
Measuring circuit for the measurement of Touch Current - Direct method based on IEC/EN 60950-1.
This test measures touch current of accessible earthed conductive and non-earthed conductive metal
parts of the device. It tests normal and reversed polarity. Perform the test with S1 closed (Normal
Condition).
There are no parts of the equipment that are not protectively earthed. Disconnect any data cables and
any connections that may provide an extraneous earth path. Test the device under test (DUT) on an
insulated surface. Do not touch the DUT during testing.
Touch Current Test  X1 <= 3.5 mA

(Normal Condition - 
with mains cable)
NOTE • All values for current and voltage are the root mean square (r.m.s.) values, unless otherwise stated.
• In case of an IT power system, this safety test measurement requires a special measuring circuit, for
example with its own integrated TN system or use of an external isolation transformer attached to
the safety test device.

2.9.1.6 SPS 3 Touch Current - SFC (single fault condition, Serial Port Server)
Test to perform:
Measuring circuit for the measurement of Touch Current - Direct method based on IEC/EN 60950-1.
This test measures leakage current of accessible earthed conductive and non-earthed conductive metal
parts of the device. It tests normal and reversed polarity. Perform the test with S1 open (Single Fault
Condition).
There are no parts of the equipment that are not protectively earthed. Disconnect any data cables and
any connections that may provide an extraneous earth path. Test the device under test (DUT) on an
insulated surface. Do not touch the DUT during testing.
Touch Current Test (Single X2 <= 3.5 mA

Fault Condition - with mains
cable)
NOTE • All values for current and voltage are the root mean square (r.m.s.) values, unless otherwise stated.
• In case of an IT power system, this safety test measurement requires a special measuring circuit, for
example with its own integrated TN system or use of an external isolation transformer attached to
the safety test device.

2 Testing and Maintenance Reference: Allowable Values for Safety Tests based on IEC/EN 60601-1
2.10 Reference: Allowable Values for Safety Tests

based on IEC/EN 60601-1
Protective Earth resistance (between the PROTECTIVE EARTH TERMINAL and any
ACCESSIBLE METAL PART which is PROTECTIVELY EARTHED, without power cord): 100
mOhm
Protective Earth resistance of power cord: 100 mOhm
Enclosure leakage current (IEC/EN 60601-1): 100 A (N.C.)
Enclosure leakage current (IEC/EN 60601-1): 500 A (S.F.C)
All values for current and voltage are the root mean square (r.m.s.) values, unless otherwise stated
2.11 When to Perform Tests

The following table tells you when to carry out specific tests. All the tests must be performed on the
Service Event Test procedure(s) Required

Installation Visual, Power On, Performance, Audible Alarms, Safety and
system test procedures.
Preventive Maintenance Customer responsibility.
Installation of a S/W service pack Installation Service Pack
Repair - computer (display, internal computer components) Power On, Performance Software, Audible Alarms, Safety Test
procedures.
Repair - RS232 Power On, Performance RS-232, Safety test procedures.
Repair - software reload (Operating system, IntelliSpace Power On, Performance, Audible Alarms.
Perinatal)
Repair - RS232 (cables, converters) Performance RS232.
Repair - Serial Port Server Power On
Safety test procedures: 
- SPS 1: Protective Earth Resistance (Serial Port Server)
- SPS 2: Touch current Normal Condition (Serial Port Server)
- SPS 3: Touch current Single Fault Condition (Serial Port
Server)
Performance Serial Port Server.
Repair - switch/LAN Power On.
Repair - isolation transformer Visual, Safety test procedures.
Upgrade - add memory, 2nd network card Power On, Performance, Safety test procedures.
Upgrade - add RS232 card Power On, Performance RS232, Safety test procedures
Upgrade - add serial port server Power On, Performance Serial Port Server
All other Service Events Visual, Power On, Performance, Audible Alarms.

Reporting of Test Results 2 Testing and Maintenance
Service Event Test procedure(s) Required

Combining or exchanging system components (non- Perform the System Test for the respective system components
medical electrical equipment connected to a Fetal Monitor
or medical electrical equipment operated on one multiple
socket outlet)
2.12 Reporting of Test Results

Philips recommends all test results are documented in accordance with local laws. Authorized Philips
personnel report test result back to Philips.
While hospital personnel (biomedical engineers or technicians) do not need to report results to Philips,
Philips recommends that they record and store the test results in accordance with local laws.
The following table lists what to record after completing the tests in this chapter. Record the results in
the empty column in the following table.
The following is a guide as to what your documentation should include:
• Identification of the testing body (for example, which company or department carried out the tests).
• Name of the person(s) who performed the tests and the concluding evaluation.
• Identification of the device(s) and accessories being tested (serial number, etc.).
• The actual tests (including visual inspections, performance tests, safety and system tests) and
measurements required
• Date of testing and of the concluding evaluation.
• A record of the actual values of the test results, and whether these values passed or failed the tests.
• Date and confirmation of the person who performed the tests and evaluation.
The device under test should be marked according to the test result: passed or failed.

2 Testing and Maintenance Reporting of Test Results
2.12.1 Carrying Out and Reporting Tests
2.12.1.1 Test Report
Testing Organization: Test before putting into service (reference value)  O

Name of testing person: Recurrent Test O
Test after Repair O
Date: (check one of these options)
Responsible Organization:
Device Under Test: ID Number:
Product Number Serial No.:
Accessories:
Measurement Equipment
(Manufacturer, Type, Serial No.):
Safety Test Method used:
Functional Test (parameters tested):
Mains voltage and frequency 

used during safety testing:
Test and Inspection Matrix

Test Block Test or Inspection Expected Test Results Record the Results (mandatory for
to be Performed Philips Personnel only)
What to Record Actual Results
Visual Inspection Perform Visual Pass or Fail V:P or V:F *
Inspection (see Visual
Inspection on page
9).
Power On Power on the unit. If Yes, Power On test is passed. PO:P or PO:F *
Does the self-test
complete successfully?
Safety 1 Perform Safety Test 1: With mains cable: S1:P/X1 or *
Protective Earth Maximum impedance (X1)  S1:F/X1
Resistance. m Ohm
System Perform the system test Equipment Leakage Current: Sys 1:P/X1 or F/X1 *
Sys 1-2 according to IEC/EN Sys 1 <= 100A (Normal Condition) Sys 2:P/X2 or F/X2
60601-1 edition 3
clause 16, if applicable, Sys 2 <= 300A (Single Fault
after forming a system. Condition)
System Perform the system test Protective Earth Leakage Current if Sys 3:P/X3 or F/X3 *
Sys 3 according to IEC/EN medical electrical system components
60601-1 edition 3 are connected to the same Multiple
clause 16, if applicable, Portable Socket-Outlet:
after forming a system. Sys 3 <= 300A

Reporting of Test Results 2 Testing and Maintenance
Test Block Test or Inspection Expected Test Results Record the Results (mandatory for
to be Performed Philips Personnel only)
What to Record Actual Results
SPS 1 (Serial Port Perform Protective Protective Earth Resistance X1 (with SPS 1:P/X1 or *
Server) Earth Resistance test mains cable) SPS 1:F/X1
according to IEC/EN X1 <= 300mOhms
60950-1
SPS 2 (Serial Port Perform Touch Current Touch Current X1 normal condition SPS 2:P/X1 or *
Server) test based on IEC/EN X1 <= 3.5mA SPS 2:F/X1
60950-1 in normal
condition
SPS 3 (Serial Port Perform Touch Current Touch Current X2 single fault SPS 3:P/X1 or *
Server) test based on IEC/EN condition SPS 3:F/X1
60950-1 in single fault X2 <= 3.5mA
condition
Key: P = Pass, F = Fail, X or Sys = test value to be recorded, 
* = Record the worst-case results and the associated switch positions (e.g. normal/reverse polarity).
All values for current and voltage are the root mean square (r.m.s.) values, unless otherwise stated.
2.12.1.2 Evaluation of Test Results

The evaluation of the test results must be performed by appropriately trained personnel with sufficient
product, safety testing and application knowledge.
If any test results are between 90% and 100% of the respective expected result, the previously
measured reference values must be taken into consideration for the assessment of the electrical safety of
the device under test. If no reference values are available, you should consider shorter intervals between
upcoming recurrent tests.
If any single test fails, testing must be discontinued immediately and the device under test must be
repaired or labeled as defective. Be sure to inform the user about the test failure in writing.
2.12.1.3 Evaluation
Yes No
Safety and Functional Test passed
Repair required at a later date, safety and functional test passed
Device must be taken out of operation until repair and passed tests
Device failed and must be taken out of operation
Notes:
Next Recurrent Test:
Name:
Date/Signature:

2 Testing and Maintenance Test and Inspection Responsibility
2.13 Test and Inspection Responsibility

An IntelliSpace Perinatal system comprises (but is not limited to) multiple components such as
computer hardware, software, and fetal monitors. Such components may be altered independently
from each other and by various parties such as Philips, the end customer and authorized service
providers.
The following table describes which party is responsible for testing and documenting changes
(including test record retention) after any alteration (e.g. installing, adding, changing, modifying) of
any of the involved components.
Scenario Who is responsible?

Electrical/ Customer or Customer authorized Customer is responsible for
Functional service performing and documenting
Connections provider installs/adds/changes/ tests as described in the product
modifies medical HW or non-medical service documentation.
HW directly connected to medical
HW as described and specified by
Philips
Philips or Philips authorized service Philips or Philips authorized
provider installs/adds/changes/ service provider is responsible
modifies medical HW or non-medical for performing and
HW directly connected to medical documenting tests as described
HW as described and specified by in the product service
Philips documentation.
Mounting Customer or Customer authorized Customer is responsible for
solutions service provider installs/adds/changes/ performing and documenting
modifies mounting hardware as tests as described in the product
described and specified by Philips service documentation.
provider installs/adds/changes/ service provider is responsible
modifies mounting hardware as for performing and
described and specified by Philips. documenting tests as described
in the product service
documentation.
Software Customer or Customer authorized Customer is responsible for
service provider generates/adds/ performing and documenting
changes/modifies a medical SW tests as described in the product
installation as described and specified service documentation.
by Philips
provider generates/adds/changes/ service provider is responsible
modifies a medical SW installation as for performing and
described and specified by Philips documenting tests as described
in the product service
documentation.

After Installation Testing or Repair 2 Testing and Maintenance
• Non-medical equipment in patient vicinity always requires electrical safety testing and may require
protective measures (e.g. usage of separation device or other protective measure)
• This guide provides information about when and how to perform required tests. See Test and
Inspection Matrix on page 22 and When to Perform Tests on page 34 for further information.
• Generally, unless otherwise indicated in product installation or service guides, Philips does not allow
third party software or hardware to be used as medical devices in conjunction with or on the same
platform as the Philips product. 
In all instances, it is the customer's responsibility to ensure that integration or use of this hard-/
software does not affect the Philips device, system or installation specifications as described in the
installation and service documentation. These additional components and their functionality are
not subject to the Philips support and warranty and are the responsibility of the customer for
servicing and replacement. 
For IntelliSpace Perinatal, additional functional tests for third party hardware and software are
documented in the IntelliSpace Perinatal Integration Guide, chapter Integration Tests.
2.14 After Installation Testing or Repair

Before handing the IntelliSpace Perinatal system over to the customer, ensure that it is appropriately
configured.
Ensure that the customer receives the current revision of the IntelliSpace Perinatal documentation.
2.15 Safety and Site Preparation

After running the tests, return the system to its pre-test condition to restore safe operating conditions.
WARNING 1 Site Preparation may involve the application of Mains/Line voltage to the test lead.
USE EXTREME CAUTION TO AVOID SEVERE PERSONAL INJURY OR DEATH.
2 To ensure test accuracy, equipment must be isolated electrically from ground.
2.16 Safety Notes for Cabling and Installation

Fetal Monitor
• The thick yellow-black ground cable is NOT required. It cannot be used as a required safety
connection, as it can be removed without tools. It is, however, an additional safety feature.
• All metal parts in the patient room must be grounded to protective earth.
Computer in Patient Vicinity
To meet the requirements of IEC/EN 60601-1 edition 3 clause 16 when a computer is located in the
patient vicinity:
• Use an isolation transformer to supply both the display and the system unit of the computer. The
devices must be connected in the following order:
Mains supply isolation transformer  UPS Computer & Display Monitor

2 Testing and Maintenance Network Verification
• DO NOT connect the computer to any other device, such as a printer, or a modem, unless the
device has an isolation transformer or a floating power supply.
See the IntelliSpace Perinatal Site Preparation and IT Specification Guide for full cabling details.
2.17 Network Verification

Network verification is required. This is part of the wall cabling installation, and is NOT bundled with
IntelliSpace Perinatal. It is the customer’s responsibility to obtain network certification.
2.18 Electrostatic Handling Precautions

Static electricity can damage electronic components. To prevent damage, observe the following
handling precautions:
• Use a grounding wrist strap, if available, connected to the metal frame of the computer. To dissipate
static electricity, the power cord must be connected between the computer and the wall outlet (by
way of the isolation transformer) with the system switched off. If there is no isolation transformer,
you require a grounded work place.
• Always touch the metal part of the computer frame just before handling a circuit board or disk drive.
• Avoid directly touching components or edge connectors on the board. Handle circuit boards and
disk drives by their metal brackets or frames.
2.19 Emissions and Immunity

The product is designed and evaluated to comply with the emissions and immunity requirements of
international and national EMC standards. See the following tables for detailed information regarding
declaration and guidance.
The EMC standards state that manufacturers of patient-coupled equipment must specify immunity
levels for their systems. See Table Electromagnetic Immunity - General on page 42 and Table
Electromagnetic Immunity on page 43 for this detailed immunity information. See Table
Recommended Separation Distances on page 44 for recommended minimum separation distances
between portable and mobile communications equipment and the product.
Immunity is defined in the standard as the ability of a system to perform without degradation in the
presence of an electromagnetic disturbance. Degradation in system performance is a qualitative
assessment which can be subjective.
Caution should, therefore, be taken in comparing immunity levels of different devices. The criteria
used for degradation is not specified by the standard and can vary with the manufacturer.

Emissions and Immunity 2 Testing and Maintenance
2.19.1 Guidance and Manufacturer’s Declaration

The product is intended for use in the electromagnetic environment specified in the following tables.
The customer or the user of the product should assure that it is used in such an environment.
Electromagnetic Emissions
Emissions Test Compliance Electromagnetic Environment Guidance

Radio Frequency (RF) The product uses RF energy only for its internal function.
emissions Therefore, its RF emissions are very low and not likely to
CISPR 11 cause interference in nearby electronic equipment.
Group 1
or
CISPR 22
RF emissions Class A
CISPR 11
or CISPR 22
Harmonic emissions Class A The product is suitable for use in all establishments, other
IEC/EN 61000-3-2 than domestic and those directly connected to the public
low-voltage power supply network that supplies buildings
used for domestic purposes.
Voltage fluctuations/ Complies
flicker emissions
IEC/EN 61000-3-3

2 Testing and Maintenance Emissions and Immunity
Electromagnetic Immunity - General
Immunity Test IEC/EN 60601  Compliance Electromagnetic Environment - Guidance

Test Level Level
Electrostatic discharge + 6 kV contact + 6 kV contact Floors should be wood, concrete, or ceramic tile. If floors are
(ESD) + 8 kV air + 8 kV air covered with synthetic material, the relative humidity should
IEC/EN 61000-4-2 be at least 30%.
Electrical fast transient/ + 2 kV for power + 2 kV for power Mains power quality should be that of a typical commercial or
burst supply lines supply lines hospital environment.
IEC/EN 61000-4-4 +1 kV for input/ +1 kV for input/
output lines output lines
Surge + 1 kV differential + 1 kV differential Mains power quality should be that of a typical commercial or
IEC/EN 61000-4-5 mode mode hospital environment.
+ 2 kV common mode + 2 kV common mode
Voltage dips, short < 5% UT a < 5% UT a Mains power quality should be that of a typical commercial or
interruptions, and (> 95% dip in UT) for (> 95% dip in UT) for hospital environment. If the user of the product requires
voltage variations on 0,5 cycle 0,5 cycle continued operation during power mains interruptions, it is
power supply input 40% UT  40% UT  recommended that the product be powered from an
lines (60% dip in U ) (60% dip in U ) uninterruptible power supply or a battery.
T  T 
IEC/EN 61000-4-11 for 5 cycles for 5 cycles
70% UT  70% UT 
(30% dip in UT)  (30% dip in UT) 
for 25 cycles for 25 cycles
< 5% UT  < 5% UT 
(> 95% dip in UT) for (> 95% dip in UT) for
5 sec 5 sec
Power frequency 3 A/m 3 A/m Power frequency magnetic fields should be at levels
(50/60 Hz) characteristic of a typical location in a typical commercial or
magnetic field hospital environment.
IEC/EN 61000-4-8
aU
T is the AC mains voltage prior to application of the test level.

Electromagnetic Immunity
Immunity Test IEC/EN 60601 Compliance Electromagnetic Environment - Guidance

Test Level Level
Portable and mobile RF communications equipment should be
used no closer to any part of the product, including cables, than
the recommended separation distance calculated from the equation
applicable to the frequency of the transmitter.
Recommended Separation Distance
Conducted RF 3 Vrms 3 Vrms
IEC/EN 61000-4-6 150 kHz to 80 MHz
d  1 .2 P
Radiated RF 3 V/m 3 V/m
IEC/EN 61000-4-3 80 MHz to 800 MHz
d  1 .2 P
80 MHz to 2.5 GHz

d  2.3 P
where P is the maximum output power rating of the transmitter in
watts (W) according to the transmitter’s specified output power
and d is the recommended separation distance in meters (m).
Field strengths from fixed RF transmitters, as determined by an
electromagnetic site survey,a should be less than the compliance
level in each frequency range.b
Interference may occur in the vicinity of equipment marked with
the following symbol:
At 80 MHz and 800 MHz, the higher frequency range applies.

These guidelines might not apply in all situations. Electromagnetic propagation is affected by absorption and reflection from structures,
objects and people.
a
Field strengths from fixed transmitters, such as base stations for radio (cellular/cordless) telephones and land mobile radios, amateur
radio, AM and FM radio broadcast and TV broadcast cannot be predicted theoretically with accuracy. To assess the electromagnetic
environment due to fixed RF transmitters, an electromagnetic site survey should be considered. If the measured field strength in the
location in which the product is used exceeds the applicable RF compliance level above, the product should be observed to verify
normal operation. If abnormal performance is observed, additional measures are necessary, such as re-orienting or relocating the
product.
b
Over the frequency range 150 kHz to 80 MHz, field strengths should be less than 3 V/m.

2.19.2 Recommended Separation Distances

The product is intended for use in an electromagnetic environment in which radiated RF
disturbances are controlled. The customer or the user of the product can help prevent
electromagnetic interference by maintaining a minimum distance between portable and
mobile RF communications equipment (transmitters) and the product as recommended
below, according to the maximum output power of the communications equipment.
Separation Distance According to Frequency of Transmitter (m)

Rated Maximum Output 150 kHZ to 800 MHz 800 MHz to 2.5 GHz
Power of Transmitter (W)
d  1 .2 P d  2.3 P
0.01 0.1 m 0.2 m
0.1 0.4 m 0.7 m
1 1.2 m 2.3 m
10 4m 7m
100 12 m 23 m
For transmitters rated at a maximum output power not listed above, the recommended separation distance d in meters (m) can be determined
using the equation applicable to the frequency of the transmitter, where P is the maximum output power rating of the transmitter in watts
(W) according to the transmitter’s manufacturer.
At 80 MHz and 800 MHz, the higher frequency range applies.
These guidelines might not apply in all situations. Electromagnetic propagation is affected by absorption and reflection from structures,
objects and people.



3
3System Description
3.1 Overview
IntelliSpace Perinatal is Software that is installed on a computer-based network system for obstetrical
surveillance, alarming, and patient data management. For system specifications of the required
hardware, please refer to the IntelliSpace Perinatal Site Preparation and IT Specification Guide.
Key options include patient data storage to a network location; an External Server used, for example, to
facilitate forms-based patient records and statistical reporting; an optional HL7 link for Admission
Discharge Transfer (ADT) messages and ORU (IntelliSpace Perinatal notes) messages; and an optional
access via RDS.

3 System Description Overview

Introduction 4 New System Setup
4New System Setup
4.1 Introduction
This chapter tells you how to get a new system up and running.
You should also check Philips InCenter for the latest IntelliSpace Perinatal service pack and ensure
that it is installed.
4.1.1 Computer Roles

There are different roles for IntelliSpace Perinatal computers:
• Internal Server
• External Server
• Remote Desktop Session Host server
• High-end Data Acquisition Server
• Clients used for data acquisition from fetal monitors (Client Data Acq.)
• Clients not used for data acquisition (Other Client)
• Small Architecture System server
• Data Warehouse Server
This chapter consists of a sequence of tasks you must do to install all types of computer roles. Each task
starts with a small table indicating for which computer role the task is relevant. To install an
IntelliSpace Perinatal computer, start with task number 1 and go through the tasks that are marked for
your computer role.
X Internal Server
External Server
Remote Desktop Session Host server
Client Data Acq.
Other Client
X High-end Data Acquisition Server
Data Warehouse Server
For a description of how to start Remote Desktop clients and install Remote Desktop clients with
alarming please refer to Remote Desktop Clients on page 78.
4.1.2 Order in which to Perform Tasks

The order in which you perform the tasks is important. When installing a system (server and at least
one client), please observe the following workflow:
1 Install the Internal Server.
2 Install each client.

4 New System Setup Installation Checklists
4.2 Installation Checklists

The following pages are installation checklists, one for each computer role. To use the installation
checklists:
For each computer in your installation:
1 Determine the role of the computer (server, standalone, External Server, Remote Desktop Session
Host server, client with data acquisition, or other client). Make a copy of the appropriate
installation checklist.
2 Verify that the computer meets the specifications of IntelliSpace Perinatal.
3 Install the computer by performing the tasks in the checklist. If a check box is enclosed in
parentheses, the task is optional or conditional.
4 For each task, the task number refers to the tasks as described in this chapter. The page number(s)
refer(s) to the page(s) where information on how to perform the task can be found. Page numbers
in bold type refer to the pages with the greatest level of detail.
5 After completing a task, check the check box in the checklist.
CAUTION When you have finished installing all computers, staple all the installation checklists together and store
them.
WARNING Installation of IntelliSpace Perinatal in the healthcare facility network/on customer provided hardware,
and installation of third party hardware and/or software can severely compromise the system
performance and the alarm-handling of the IntelliSpace Perinatal system.
For third party hardware and/or software components that are not Philips factory validated there is a
risk that alarming could be delayed, or the IntelliSpace Perinatal system performance could be
compromised, even if an integration test was successful. Installing third party applications on to clients
with data acquisition or servers increases these risks. If integration proves incompatible with the
IntelliSpace Perinatal system, the integration must be removed.
You must perform the required integration tests to ensure that IntelliSpace Perinatal performance is
not adversely affected by the integration. These tests show a ‘snapshot’ of the system functionality at
the time of testing. They do not guarantee that this functionality will be maintained. The tests indicate
that there is no evidence of incompatibility at the time of testing.
For integration details, follow the instructions described in the IntelliSpace Perinatal Integration Guide.
Internal Server
Installation Checklist
Date: ___________________
Computer Name: ___________________ Room: ___________________

Installation Checklists 4 New System Setup
Tasks Page Done
1: Check Shipment 67 
2: Put Equipment in Place 67 
3: Set Voltage Selection Switch 67 
4: Connect Isolation Transformer 68 
5: Connect Fetal Monitors 69 
6: Connect to Network 69 
8: N/A
8: Connect Serial Port Server 70 
9: Install Operating System and Run System Check Tool 70 
10: Set up Soundcard 71 
11: Set Date and Time 71 
12: IntelliSpace Perinatal Setup 71 
14: N/A
15: N/A
16: N/A
16: Install Word/Excel Templates 72 
17: Start IntelliSpace Perinatal 73 
18: Configure IntelliSpace Perinatal at Internal Server machine 73 
20: N/A
21: N/A
21: Set up Document Export 74 
22: Functionality Test 74 
23: Safety Test 75 
24: Print and Back-up Configuration Record 75 
25: Print out Computer Installation Record 76 
26: Set up the Backup Tool Script 76 
28: N/A
28: Change Passwords 77 
29: Store Documentation and Backups 77 


External Database Server

Date: __________________
Computer Name: __________________ Room: ___________________
Tasks Page Done
6: N/A
8: N/A
9: N/A
13: Set up the HL7 Interface 72 
15: N/A
15: Install Microsoft Office 72 
17: N/A
19: N/A
19: Configure IntelliSpace Perinatal at client machines 73 
21: N/A
25: N/A
Tasks Page Done
28: N/A 75 

Remote Desktop Session Host server

Date: ___________________
Tasks Page Done
5: N/A
6: N/A
7: Connect Second Network Card 70 
9: N/A
11: N/A
14: N/A
14: Configure Remote Desktop Session Host Server 72
Settings 
17: N/A
18: N/A
19: N/A
20: Installation of VNC Server 74 
22: N/A
25: N/A

Tasks Page Done
27: N/A
27: Install and Activate RDS Client Access Licenses 76 

Client with Data Acquisition

Date: ___________________
Tasks Page Done
8: N/A
14: N/A
15: N/A
17: N/A
19: N/A
21: N/A
22: N/A
25: N/A
27: N/A

Tasks Page Done
28: N/A

High-end Data Acquisition Server

Date: ___________________
Tasks Page Done
5: N/A 
8: N/A
11: N/A
14: N/A
15: N/A
16: N/A
17: N/A
19: N/A
21: N/A
22: N/A
25: N/A

Tasks Page Done
27: N/A
28: N/A

Other Client (including Remote Client)

Date: ___________________
Tasks Page Done
6: N/A
7: Connect Second Network Card 70 
9: N/A
15: N/A
17: N/A
19: N/A
21: N/A
25: N/A
27: N/A

Tasks Page Done
28: N/A

Small Architecture System

Date: ___________________
Tasks Page Done
8: N/A
10: N/A
14: Configure Remote Desktop Session Host Server Settings 72 
16: N/A
17: N/A
18: Configure IntelliSpace Perinatal at Internal Server machine 73 
20: N/A
20: Installation of VNC Server 74 
24: Print and Back-up Configuration Record 75 
27: N/A

Tasks Page Done
27: Install and Activate RDS Client Access Licenses 76 



Date: ___________________
Tasks Page Done
5: N/A
6: N/A
8: N/A
9: N/A
11: N/A
14: N/A
15: N/A
16: Install Word/Excel Templates 72 
18: N/A
19: N/A
20: N/A
21: N/A
22: N/A
23: N/A
25: N/A

Tasks Page Done
28: N/A

Tasks 4 New System Setup
4.3 Tasks
1: Check Shipment
X Internal Server
X External Server
X RD Session Host Server
X Client with Data Acq.
X Other Client
X High-End Data Acq. Server
X Small Architecture System
X Data Warehouse Server
Unpack the shipment and cross-check against the customer's order that all hardware and software is
present.
2: Put Equipment in Place
X Internal Server
X External Server
X Other Client
NOTE The location of the Internal Server deserves special consideration. An Internal Server malfunction
(crash) will bring down the complete IntelliSpace Perinatal network. To minimize this risk it is highly
recommended that the Internal Server is put in a secure place (such as a closet) and is not used for day-
to-day operations except for configuration work, archive administration and retrieve. If the Internal
Server is installed in the central station or nursing lounge, it should always be locked to overview
display and not used for patient data acquisition, charting or administration.
Choose the location and orientation of each display to fulfill ergonomic requirements such as avoiding
direct sunlight, and reflections from lamps. This both improves user comfort and allows you to reduce
the display’s brightness and contrast settings, which significantly increases the display’s lifetime.
3: Set Voltage Selection Switch
X Internal Server
X External Server
X Other Client
Some computers have a 115V/240V voltage selector switch (refer to the computer’s user manual). If
this switch is present, set it to suit the local power supply. If this switch is not present, the computer’s
power supply is auto-ranging.

4 New System Setup Tasks
4: Connect Isolation Transformer

X Internal Server
X External Server
RD Session Host Server
X Other Client
High-End Data Acq. Server
CAUTION Mandatory for all computers in patient vicinity.
Computers and displays located in patient vicinity must be powered via an approved isolation
transformer that ensures mechanical fixing of the powercords and covering of unused power outlets.
Use the device power cables supplied with the transformer.
Connecting the Isolation Transformer to the Mains Power Supply and UPS:
CAUTION You must connect the devices in the order described below. If you connect the devices in the
wrong order, leakage currents exceeding the regulatory limits can occur.
Connect the devices in the following order:

1 Connect the isolation transformer to the main power supply.
2 Connect the isolation transformer to a UPS, if applicable.
3 Connect the UPS to the computer.
Connecting the Cables:

To connect the cables, open the metal clips at the transformer outlets, insert the cables then close the
clips to secure the cables. The configuration in Figure . 8: Connect Serial Port Server shows a typical
IntelliSpace Perinatal system comprising of an isolation transformer, UPS, computer with display and
fetal monitor:
~ UPS
Medical
Isolation
Transformer
RS232
~ Fetal Monitor

5: Connect Fetal Monitors

X Internal Server
External Server
Other Client
Fetal Monitors are connected to the IntelliSpace Perinatal system
• directly via computer COM Ports or
• through a serial port server
• via Ethernet (for Avalon FM20/30/40/50)
For Ethernet connections, Avalon FM20/30/40/50 monitors require a valid and unique IP address.
Network parameters can be configured manually, but the preferred method is to obtain them from a
BOOTP server automatically. IntelliSpace Perinatal server machines can be used to serve both DHCP
and BOOTP requests. For domain-integrated systems, the domain DHCP servers can also provide
BOOTP addresses. For further details please refer to the IntelliSpace Perinatal Integration Guide.
For details about cables and protocol converters, refer to Installing a Client on a Cart (Mobile Client)
on page 79.
The fetal monitor protocols do not support transmission of strings which require multibyte character
sets (for languages such as Japanese and Chinese). Notes containing such characters are not sent
correctly from/to the fetal monitor.
CAUTION Do not connect a fetal monitor directly to the server except in a small system, that is a system with no
more than 20 clients.
6: Connect to Network
X Internal Server
X External Server
X Other Client
1 If there are two network interface cards installed locate the first network card.
2 Plug the network cable into the socket on the back of the computer. See section Connecting to the
Network on page 86 for details.

7: Connect Second Network Card

Internal Server
External Server
Client with Data Acq.
X Other Client
Small Architecture System
1 Locate the second network card.
2 Connect to the card.
3 Enable the second network card (default = disabled).

8: Connect Serial Port Server
X Internal Server
External Server
Other Client
Refer to Installing and Setting up a Serial Port Server on page 92.
9: Install Operating System and Run System Check Tool

X Internal Server
X External Server
X Other Client
Make sure that appropriate drivers are installed. Drivers for Philips-supported hardware are included
on the IntelliSpace Perinatal distribution medium. Please refer to Windows Installation on page 255.
For the Small Architecture System, this must only be performed for a re-install. New systems come pre-
installed from the factory. Make sure that the Windows operating system package is stored in a safe
place for re-installation scenarios.
For details on the System Check Tool, please refer to the System Check Chapter in the IntelliSpace
Perinatal Site Preparation and IT Specification Guide.

10: Set up Soundcard

X Internal Server
X External Server
X Other Client
The soundcard is pre-installed and ready to use.
CAUTION The soundcard is used for audible alarming and has no other purpose.
Users must not play audio CDs since this may adversely affect audible alarming.
Do not install additional hardware for playback via the soundcard or install any additional external or
internal speaker(s), or install software to control audio CD playback.
High-end computers do not have soundcards.
11: Set Date and Time

X Internal Server
X External Server
X Other Client
Set the local date and time in the Control Panel.
12: IntelliSpace Perinatal Setup

X Internal Server
X External Server
X Other Client
You must run the IntelliSpace Perinatal Setup to install the software.
The Small Architecture System comes pre-installed, but Setup needs to run in order to change
IntelliSpace Perinatal System Options.
NOTE Do not configure clients and other servers until you have completed configuring the Internal Server.

13: Set up the HL7 Interface

Internal Server
X External Server
X Other Client
During new system setup, the machine running the HL7 interface/link must be set up. 
14: Configure Remote Desktop Session Host Server Settings

Internal Server
External Server
Other Client
Remote Desktop Session Host Configuration:
Check the IntelliSpace Site Preparation and IT Specification Guide for more details.
15: Install Microsoft Office

Internal Server
X External Server
X Other Client
Please refer to the IntelliSpace Perinatal Site Preparation and IT Specification Guide for more details.
16: Install Word/Excel Templates

X Internal Server
External Server
Other Client
For details, see Installing Word and Excel Templates on page 110.

17: Start IntelliSpace Perinatal

X Internal Server
X External Server
X Other Client
In the Start menu click the IntelliSpace Perinatal icon.
NOTE Do not start IntelliSpace Perinatal at the Remote Desktop Session Host server. 
The Remote Desktop Session Host server is dedicated to run only the Remote Desktop sessions
initiated by Remote Desktop clients.
18: Configure IntelliSpace Perinatal at Internal Server machine

X Internal Server
External Server
Other Client
• Finish configuring the Internal Server before configuring the clients.
• Each configuration screen builds on the information provided on the previous screen. Work through
the configuration icons from left to right.
• Create at least one new superuser as the user Philips is only to give you initial access to the system
and to the Philips-only configuration screen.
For details see the IntelliSpace Perinatal Instructions for Use.
NOTE Do not use user Philips for regular operation.

Never create/edit/delete patient related data when you are logged in as Philips user.
19: Configure IntelliSpace Perinatal at client machines

Internal Server
X External Server
X Other Client
• Do not configure a client until you have completed configuring the Internal Server.
• Leave IntelliSpace Perinatal running at the Internal Server while you complete each client’s PC
Configuration and Fetal Monitor Setup screens.

20: Installation of VNC Server

Internal Server
External Server
X WRD Session Host Server
Other Client
Remote Support using RDP can be cumbersome because IntelliSpace Perinatal is started if the server is
used as an RD Session Host server for IntelliSpace Perinatal RDS Access. If you need to access the
server remotely for support it is recommended to set up an alternative remote access like Real VNC.
This is described in the IntelliSpace Perinatal Site Preparation and IT Specifications Guide.
21: Set up Document Export

X Internal Server
X External Server
X Other Client
The Document Export feature is intended to support integration with Document Management
Systems or a clinical data repository (CDR). It offers the automated generation of electronic
documents using printer drivers being capable of file generation in various formats (e.g. .pdf, .xps).
Any type of document that can be printed manually using the IntelliSpace Perinatal printing module
can also be configured for automated generation. The Document Export covers two main activities:
1 IntelliSpace Perinatal automatically generates electronic documents and stores the results in a
configurable target folder.
2 If configured, IntelliSpace Perinatal sends HL7 MDM-T01 messages to inform a remote system of
the document creation.
For more information, please refer to Document Export (DOX) on page 199.
22: Functionality Test

X Internal Server
X External Server
X Other Client
Perform the Functionality Test as described in Test and Inspection Matrix on page 22.

23: Safety Test

X Internal Server
X External Server
X Other Client
CAUTION Mandatory for all computers in patient vicinity.
• If the computer is in patient vicinity, perform the Safety Test as described in Test and Inspection
Matrix on page 22.
24: Print and Back-up Configuration Record

X Internal Server
External Server
Other Client
Backing-up the Configuration Record
When you have finished configuring the IntelliSpace Perinatal system create a configuration backup
record at the server or standalone:
• From IntelliSpace Perinatal by clicking
Configuration Backup can be made to hard disk or to the NBS archive.
• From Windows: Start the Configuration Backup Tool.
Configuration Backup can be made to hard disk.
Store a backup of the final configuration record in the system binder.
For more information refer to Configuration Backup (Internal Server Only) on page 222.
Reviewing and Printing the Configuration Record

Although you cannot use the configuration text file to amend or set any installation or configuration
parameters, you should print the file and review its content:
1 Start IntelliSpace Perinatal.
2 Go to System Manager’s Configuration General.
3 Click Export Configuration, in the ACSII Format section click Export (you may change the default
name of the configuration text file before clicking Export).
4 Start NotePad, open the configuration text file.
5 Print the file.

6 Close NotePad.
7 Review the printed file with the System Manager. Store a print of the final configuration record
with the configuration.
25: Print out Computer Installation Record

X Internal Server
X External Server
X Other Client
Each IntelliSpace Perinatal computer automatically maintains its own installation record. This record
contains information such as the setup type (for example, network server), the installation path and
system options. To review the installation record:
Go to IntelliSpace Perinatal Support  Installation Record.
By default, the installation record opens as a .txt file in NotePad. You may print the installation record
from NotePad.
26: Set up the Backup Tool Script
X Internal Server
X External Server
Other Client
Define a task in the Windows Task Scheduler to call c:\tv2\prog\backup.cmd with appropriate
parameters at desired intervals. Make sure that the Windows user running the backup task has access
rights to the destination location. For more information refer to Backup Tool on page 178.
27: Install and Activate RDS Client Access Licenses
Internal Server
External Server
Other Client
Access of computers to IntelliSpace Perinatal via RDS requires separate purchase and activation of
Remote Desktop Services Client Access Licenses (RDS CALs). The licenses must be ordered through
a Microsoft sales channel. It is the sole responsibility of the customer to order and activate these
licenses. Refer to Microsoft documentation for details of the licensing model and how to install and
activate them.
NOTE • Clients can access IntelliSpace Perinatal via RDS without RDS CAL for a grace period of 120 days.
After that period a valid RDS CAL has to be installed for these clients.

• After activating new RDS CALs in the license server clients should immediately connect to
IntelliSpace Perinatal via RDS twice to initiate automatic transfer of the license. This prevents
unintended usage of the licenses by other clients.
28: Change Passwords

X Internal Server
X External Server
X Other Client
For security purposes, it is recommended to change the following passwords:
• Windows Users (at all machines)
• IntelliSpace Perinatal User: Philips
CAUTION Note the passwords and store in a safe place.

If all administrator passwords are lost you need to reinstall Windows.
If the Philips password is lost see Restoring the IntelliSpace Perinatal Philips Password on page 251.
29: Store Documentation and Backups

X Internal Server
X External Server
X Other Client
Store all license sheets, password sheets, configuration printouts, the installation record, and emergency
repair disks in a safe location.

4 New System Setup Remote Desktop Clients
4.4 Remote Desktop Clients

For details about setting up access via RDS, refer to the IntelliSpace Perinatal Site Preparation and IT
Specification Guide, Chapter IntelliSpace Perinatal Remote Desktop Session Access. 

5
5Setup Details
5.1 Introduction
This chapter gives details on the following setup tasks:
• Installing a Client on a Cart (Mobile Client)
• Connecting Fetal Monitors
• Connecting to the Network
• Installing and Configuring Remote LAN Clients
• Installing and Setting up a Serial Port Server
• Installing Word and Excel Templates
• Using MS Office for Document Export
The detailed descriptions in this chapter are referred to from Chapter New System Setup on page 49.
5.2 Installing a Client on a Cart (Mobile Client)

A client can be cart mounted with a Fetal/Maternal monitor.
Do NOT connect a printer to a cart mounted client.
5.2.1 Client UPS

You must power the computer and display via a UPS and an isolation transformer. Make the power
connections as follows:
Mains  Isolation Transformer  UPS Computer/Display
Do not power the fetal monitor via a UPS.
Do not attempt to leave IntelliSpace Perinatal running at a client (supported by the UPS) while the cart
is disconnected from the LAN and moved to a new location.
If you move a mobile client into a storage room, reconnect the UPS to the power supply to recharge
the UPS batteries. Never leave the UPS disconnected, because the batteries will drain down.
5.2.2 Configuration
After starting IntelliSpace Perinatal this client needs to be configured as Mobile. Refer to the
IntelliSpace Perinatal Instructions for Use for configuration instructions.

5 Setup Details Installing a Client on a Cart (Mobile Client)
5.2.3 Moving the Cart

Whenever the mobile client is moved to a different location you need to assign the new bed to the
client.
To shut down a mobile client:

1 Exit IntelliSpace Perinatal.
You must exit IntelliSpace Perinatal before moving the cart, disconnecting from the LAN, or
turning off the client.
2 Go to Start -> Shutdown, select Shut down.
3 Disconnect the power and LAN cables.
To start a mobile client:

1 Connect the power and LAN cables.
2 Turn on the computer.
3 Log on to Windows.
4 Log on to IntelliSpace Perinatal.
5 At the Fetal Monitor Setup screen verify the Fetal Monitor connections and select the correct bed
labels. Assign the new bed to the new location.
6 A cart mounted computer is configured as a mobile client. The IntelliSpace Perinatal startup screen
for a mobile client is the Fetal Monitor Setup screen.

Connecting Fetal Monitors 5 Setup Details
5.3 Connecting Fetal Monitors

This section tells you how to connect fetal monitors to IntelliSpace Perinatal.
Fetal monitors are connected to
• the COM ports of the client machines
• the COM ports of the server machine (small systems only)
• the COM ports of a standalone computer
• the COM ports of a serial port server.
5.3.1 M1350, M1351/53 and Avalon FM20/30/40/50 Monitors

M13501, M1351/53, and Avalon FM20/30/40/50 fetal monitors are connected directly, using the RS-
232 FM-cable.
FM20/30/40/50 fetal monitors can also be connected using the LAN interface. For details, please refer
to the IntelliSpace Perinatal Integration Guide.
5.3.2 Other Fetal Monitors

All other fetal monitor cables come as a cable unit consisting of:
• Small cable from Fetal Monitor to converter
• Converter box
• RS-232 cable to COM port or Wallplate SUB-D
1.Requires RS-232 Digital Systems Interface.

5 Setup Details Connecting Fetal Monitors
5.3.3 Connecting Four Fetal Monitors

The computer must be fitted with an additional RS-232 serial interface card to support four fetal
monitors.
The PCI RS-232 serial interface card provides two additional COM ports, both 9 pin.
5.3.4 Connecting More than Four Fetal Monitors

More than 4 fetal monitors can be connected using one or more serial port servers. For details see
Installing and Setting up a Serial Port Server on page 92.
5.3.5 Protocol Conversion

IntelliSpace Perinatal accepts the digital signal protocol used by Series 50 and Avalon FM20/FM30/
40/50 fetal monitors. Other fetal monitor types, including others manufactured by HP/Agilent/
Philips, use different cable connectors and signal protocols. To connect these to IntelliSpace Perinatal
you must use the appropriate adapter cables and protocol converters. A separate converter is required
for each fetal monitor. Refer to Appendix A for details of how to use the protocol conversion kits, and
data tables for supported fetal monitors and mounting instructions.
Mounting the Converter Box:

Mount the converter box onto the fetal monitor housing using the velcro patch provided.
5.3.6 Hewlett-Packard / Agilent / Philips Fetal Monitors

The following information will help you to connect standard HP/Agilent/Philips monitors. See the Site
Preparation and IT Specification Guide for full details, including ordering information, for the system
interface requirements and cable drawings.
5.3.6.1 M1351/53 Fetal Monitor

Use the IntelliSpace Perinatal connection cable M1380-61613, (Cabling option K13), which has a
24pin connector to the monitor. Do not use the 9pin connector.
The RS-232 interface requires at least software version A.02.02 and M1353-69531(E).

IntelliSpace Perinatal connection on M1351/53:
IntelliSpace
Perinatal
connection

5 Setup Details Connecting Fetal Monitors
5.3.6.2 M1350A/B/C
Use the IntelliSpace Perinatal connection cable M1380-61612, (Cabling option K12) which has a 9pin
connector. If an RS422 interface is also plugged in, you need to set the push button configuration
setting C13 to 1. See the Service Guide for this monitor for details about how to change the
configuration settings.
The RS-232 interface requires at least software revision A.04.01.
M1350A/B/C RS-232 Digital System Interface connection to an IntelliSpace Perinatal system:

5.3.6.3 Avalon FM20, FM30, FM40 and FM50

Use the IntelliSpace Perinatal connection cable M1380-61612 (Cabling option K12) to connect via
the RS-232 port. The interface connections are underneath the monitor. For connection to
IntelliSpace Perinatal, the Avalon FM requires:
• Avalon FM software revision C.00 or greater for RS232 connection.
• Avalon FM software revision D.00 or greater for LAN connection.
RS-232 interface connection LAN connection

5 Setup Details Connecting to the Network
5.4 Connecting to the Network

The installation and maintenance of network cabling to a professional standard is the customer’s
responsibility. This section describes how computers in an IntelliSpace Perinatal installation are
connected to form a Local Area Network (LAN).
NOTE See also the Site Preparation and IT Specification Guide, Network Guide chapter.
5.4.1 Network Connections

The IntelliSpace Perinatal computers are connected to switches to form a LAN with star topology.
IntelliSpace Perinatal computers may be connected to the hospital network. Routing ports to the
hospital backbone are preferred. Alternatively VLAN can be used.
In a decentralized installation, clients are located close to the bedside, so the wall cabling is the LAN
connection. In centralized installations, much of the wall cabling is from fetal monitors to clients
located, for example, at the Central Station.
When the FSE installs IntelliSpace Perinatal all wall cabling must be in place. If additional clients are
purchased, extensions to the LAN and any other fixed cabling must be in place before the FSE re-
installs IntelliSpace Perinatal.
5.4.2 Switches
The following switches are supported:
• HP ProCurve Switch 2312 (12 port unmanaged 10/100 Base-TX autosensing switch)
• HP ProCurve Switch 2324 (24 port unmanaged 10/100 Base-TX autosensing switch)
Detailed information on how to install these products is provided in the appropriate installation guide
delivered with the switch.
5.4.3 Network Specifications
5.4.3.1 Networks with Switch

• The IntelliSpace Perinatal Internal Server machine must be connected directly to the switch (100
Mbps). It is recommended to connect the External Server machine to the same switch.
• It is possible to connect Avalon fetal monitors directly to the IntelliSpace Perinatal switch.
• Network devices can be connected directly to a switch port.
• Switches can be cascaded.
• Cascading switches can be used to extend the distance between IntelliSpace Perinatal server and
clients.
5.4.3.2 Serial Port Servers

The network between the serial port server and the host machine must not be routed (same network
segment).
See also Connect the Serial Port Server on page 94.

Connecting to the Network 5 Setup Details
5.4.4 Cable Specifications

All the cable used in the LAN must be twisted pair with at least 2 twists per foot or 6 twists per meter.
This cable is also known as “EtherTwist”.
The customer must ensure cables are within the maximum length permitted for LAN cabling,
including the lengths of cable between faceplates and hardware.
Cable Type and Length:
Connection Cable must Cable Type Length Limits

Type conform to
specifications
defined in:
100Base-TX IEEE 802.3u Type Category 5 or 6 100 100m switch  switch

100Base-TX Unshielded Twisted Pair.
standard RJ-45 modular plugs.
100Base-FX ITU-T G.651 and 62.5/125m or 50/125m 2km1 for full duplex
Switch only: ISO/IEC 793-2 (core/cladding) diameter, connections (the 100Base-
Type A1b or A1a graded - index, multimode FX transceiver only
for transceiver respectively. fiber-optic cables. operates in full duplex
connection mode).
(optional) Fitted with SC connectors.
RS-232 9-pin/25-pin SUB-D 100m

connector.
8/16-port serial Port Server:
RJ45-8 / 9-pin SUB-D
connectors.
1. 1.68 miles
Do not use a flat cable in the LAN, even if the cable length is very short.
5.4.4.1 100 Base-T Cable Testing

Use a Wire Test Instrument to determine whether a cable is suitable for a Type 100Base-T network by
testing attenuation, crosstalk, continuity and burst noise. Refer to the CAT-5 Specification
Attenuation 11.5dB attenuation between 5MHz and 10MHz

(10dB in cable, 1.5dB in connectors)
Pair to Pair 30.5dB at 5MHz
Crosstalk 26dB at 10MHz

5 Setup Details Connecting to the Network
5.4.5 Cabling a LAN
To connect a computer to the LAN cable:

When connecting a computer to a LAN cable, ensure that the latch on the RJ-45 connector is clicked in
place correctly.
CAUTION When failing to secure the LAN cable properly the client may shut down or crash, and loss of data may
occur.
1 Plug one end of the EtherTwist cable into the RJ-45 socket on the network card in the computer.
Push the connector in as far as possible.
2 Gently pull the cable to test whether the catch is properly clicked in. If the connector cannot be
pulled out, it is firm; continue with step 4. If it can be released by pulling, continue with step 3.
3 Take a closer look at the RJ-45 socket on the computer. If the hole is too close to the edge of the
computer housing the latch on the connector cannot click in. To alleviate the problem:
a. Turn off the power.
b. Remove the computer housing.
c. Loosen the screw holding down the network adapter.
d. Move the network adapter until as much of the RJ-45 socket is uncovered to let the connector
click in properly. If necessary, use a moderate amount of force.
e. Tighten the screw holding down the network adapter.
f. Replace the computer cover.
4 If the client is in a cart you must provide some form of strain relief for the LAN cable on the
computer side, for example, a tie-wrap.
To connect a Computer to a Switch:

Ensure that mains power to all equipment is switched off before you start. See the Site Preparation and
IT Specification Guide for wall cable drawings.
1 Connect the LAN cable to the computer.
2 Plug the other end of the EtherTwist cable into an RJ-45 port on the LAN faceplate. For a
centralized installation, plug it into the switch RJ-45 port directly.
3 Connect the switch to the faceplates.
4 Repeat the previous steps to connect the server, clients, printer (with JetDirect card).

Installing and Configuring Remote LAN Clients 5 Setup Details
5.5 Installing and Configuring Remote LAN Clients

A Remote LAN Client is an IntelliSpace Perinatal computer that is connected to an IntelliSpace
Perinatal server that does not reside in the same physical network.
The Remote LAN Client can be an IntelliSpace Perinatal client, External Server, or Remote Desktop
Session Host server machine.
Remote LAN Clients operates in the same way as a “normal” IntelliSpace Perinatal client.
5.5.1 Limitations and Prerequisites

Described in the Site Preparation and IT Specification Guide, chapter Network Guide.
All requirements and pre-requisites must be fulfilled.
5.5.2 Installation and Configuration

NOTE It is not permitted to install and configure a 2nd NIC in the IntelliSpace Perinatal Internal Server and
External Server.
5.5.2.1 Prepare Network

• Hospital IT department should set access control lists in a way that allows only the Remote LAN
Clients to access the Internal and External IntelliSpace Perinatal servers. Router ports must be
configured as IntelliSpace Perinatal gateway.
• Connect the IntelliSpace Perinatal switch to the gateway (router port).
5.5.2.2 Prepare Internal Server Machine

1 Assign the default gateway (IP address of router port).
Control Panel Network Protocols and Dial up Connections Local Area Connections 
Properties TCP/IP Protocol
2 Start IntelliSpace Perinatal Setup.
• Select Only change database settings or system settings
• Select Do not change system settings.
• Configure IP Addresses of Servers for Remote Clients: Enter the IP addresses of the NICs that
are connected to the hospital network.
If name resolution is available for all connecting PCs, the names of the servers can be entered
instead of the IP address.
3 Restart IntelliSpace Perinatal.

5 Setup Details Installing and Configuring Remote LAN Clients
5.5.2.3 Prepare Remote LAN Machine

1 If required, install the operating system1. See Windows Installation. Do not install the IntelliSpace
Perinatal software automatically.
2 Assign IP address, subnet mask, and default gateway (IP address of the connected router port). Do
not use DHCP.
Control Panel Network Protocols and Dial up Connections Local Area Connections 
Properties TCP/IP Protocol
3 Name resolution:
Open %windir%\system32\drivers\etc\hosts and add the following line:
<IP Address of Internal Server Computer> <Internal Server Computer Name>
Example: 172.16.1.2 FR71900243
It is also possible to use name resolution provided by hospital servers (e.g. WINS).
4 Connect the NIC to the hospital network.
5.5.2.4 Test the Connection

1 At the Server DOS prompt enter
• ping <Client IP address>
In case of problems try ping <OBTV default gateway> and ping <HIS default gateway>
• tracert <Client IP address>
A route to the client must be found.
2 At the Client DOS prompt enter
• ping <Server IP address>
In case of problems try ping <HIS default gateway> and ping <OBTV default gateway>
• tracert <Server IP address>
A route to the server must be found.
• ping <Server name>
The Server machine should reply properly. This verifies correct name resolution.
1. If the computer does not have a CD-ROM drive temporarily connect the computer to the same network
segment as the IntelliSpace Perinatal server.

Installing and Configuring Remote LAN Clients 5 Setup Details
5.5.2.5 Install IntelliSpace Perinatal at the Remote LAN Computer

Ensure that there is an established network connection from the remote LAN client machine to the
Internal Server before starting IntelliSpace Perinatal setup. This can be done by opening a network
drive to the Internal Server (do not select reconnect at startup).
1 Install IntelliSpace Perinatal from the local DVD-ROM or at the Internal Server. The “setup”
directory is on the server share. \\<servername>\OBTraceVue\setup
2 Perform a complete new IntelliSpace Perinatal setup.
Note: You need to enter the server name manually; you cannot browse.
NOTE If the external IP addresses of the Internal Server or External Server machine changed after Remote
LAN Client installation you must reinstall IntelliSpace Perinatal at the remote LAN client.
If setup finishes but reports an error when it tries to connect to the IntelliSpace Perinatal server database
try to ping the database:
dbping -c "CommLinks=tcpip{HOST=<Server IP Address>};ENG=<Internal Server Computer Name>I"
(The last argument of this command is the DB service name, which is the Internal Server computer
name appended with the uppercase letter I)
A connection to the database server should be established without error messages.

5 Setup Details Installing and Setting up a Serial Port Server
5.6 Installing and Setting up a Serial Port Server

5.6.1 Introduction
A serial port server (SPS) supplies multiple asynchronous RS-232 serial ports through a TCP/IP
network.
At the port server host computer a driver is installed that manages the conversion of the data back to
RS-232 format and maps the port server port to a COM port of the host computer. A port server may
be hosted at any IntelliSpace Perinatal computer that allows the direct connection of fetal monitors:
Small and Large Architecture Internal Servers, Clients and Data Acquisition Servers.
For system limitations regarding serial port servers refer to Connect the Serial Port Server on page 94.
CAUTION Serial port servers must not be installed in the patient vicinity.
5.6.1.1 Example Serial Port Server Installation

Installing and Setting up a Serial Port Server 5 Setup Details
5.6.1.2 Installation Tasks

To install serial port servers you must perform the following steps:
NOTE You must log onto Windows as Windows administrator.

Do not host different series of NPort servers (6610 series and 5610 series) at one computer.
1 Configure Host Computer Network Settings.

2 Physically Connect Port Server to the network.
3 Configure Port Server Network Settings.
4 Install Software for Firmware Check 5610-8/16.
5 A Windows device driver must be installed at each host computer for serial port server hosting.
Check Serial Port Server Firmware Revisions for 6610-8/16.
6 Configure Serial Port Server (access control / access IP list)
7 Repeat step 2, 3, 5 and 6 for each additional serial port server connected to the host computer.
8 Configure IntelliSpace Perinatal (serial ports, beds) at the host computer.
9 Repeat step 1 through 6 for each additional host computer.
10 Connect Fetal Monitors to the serial port servers and Check Fetal Monitor to Bed Connection.
11 For security reasons, protect every serial port server with a password.
5.6.1.3 Documentation
It is strongly recommended to use the tables at the end of this section for documentation. Store the
configuration sheets with all your other system documentation.
5.6.2 Host Computer Network Settings

Serial port server host computers must not operate as DHCP clients. They must have a fixed IP
address.
Start Network and Sharing Center  Change Adapter Settings Properties  TCP/IP Properties
Host Computer Network Settings:
IP Address Recommended range:

172.16.201.1 .. 172.16.201.254
Netmask 255.255.0.0
Default gateway none
DNS none
WINS none

5.6.2.1 IP Address when Installing Multiple Serial Port Server

When installing multiple serial port server it is strongly recommended to assign IP address ranges that
reflect the connection between host computer and port server:
172.16.201.10 first host computer

172.16.200.10 .. 172.16.200.19 serial port servers hosted by first host computer
172.16.201.20 second host computer

172.16.200.20 .. 172.16.200.29 serial port servers hosted by second host computer
172.16.201.30 third host computer

172.16.200.30 .. 172.16.200.39 serial port servers hosted by third host computer
... ...
5.6.3 Connect Port Server
5.6.3.1 Connect the Serial Port Server

The serial port server can be connected
• To the network via a network switch.
It is possible to connect the serial port server to the hospital network. 5610 family serial port servers
and the serial port server host computer must be connected to the same network segment (not
routed).
• Directly to the network interface card of an IntelliSpace Perinatal host computer using a cross-wired
Ethernet cable (only one serial port server).
The NPort Server 6610 supports IPv4 and IPv6.
CAUTION The network between Serial Port Server, Host computer, and Internal Server must be at least
100Mbps.
NOTE You must use a fail-safe power supply for the serial port server and for the network switches.
If the network connection between IntelliSpace Perinatal computer and the serial port server has been
interrupted you should reboot the IntelliSpace Perinatal computer to reconnect.
5.6.3.2 Maximum Cable Length

To minimize side effects on the serial connection, the serial cable should be as short as possible, but the
serial port server must not be installed in patient vicinity. The length is 100m per network node, plus
100m for RS232 connection to the fetal monitor.
See also Cable Specifications on page 87.

5.6.4 Port Server Network Settings
5.6.4.1 Network Settings

Serial port servers must have a fixed IP address. The following network settings must be used:
Serial Port Server Network Settings:
IP Address Recommended range:

172.16.200.1 .. 172.16.200.254
Netmask 255.255.0.0
DHCP disable
5.6.4.2 Configuring Serial Port Server Network Settings

Use the push buttons of the device to enter at least one IP address that is in the same network as the
IntelliSpace Perinatal Serial Port Server host machine.
Once entered, the web console of the SPS may be used for further settings:
• Open a web browser on the SPS host machine and enter the new IP address of the SPS.

5.6.5 Configure Serial Port Server
5.6.5.1 Configure NPort Server 5610-8/16
Basic Settings:
• Start Web Console and log in.
• Select Basic Settings and enter a descriptive name for the serial port server (no blanks)

Network Settings:
• Enter an IP Address and Netmask (see Port Server Network Settings)
• Disable SNMP if not needed
Check Port Settings:

The port configuration determines which ports of the serial port server(s) are mapped to which COM
ports on the host computer.
1 Check COM ports:
To ensure that there is no conflict between COM ports, check whether serial port server ports
[Moxa Communication Port x (COM y)] conflict with built-in COM ports [Communications
Port (COM z)] or other port server ports.
2 Check COM port mapping and configure port server ports:
In case of duplicate COM ports or if you want to change COM port assignment for other reasons:
a. Start Web Console and log in.
b. Select Operating Settings  Port 1 (for example)  Operation Mode
c. Mode RealCOM must be selected for each port.
d. Ensure that the port servers do not conflict with built-in COM ports.
e. Document port settings using the table Serial Port Server Host Computer Installation
Documentation: on page 108.
Operation Mode:
For each port, select Real COM Mode, keep the default settings of Real COM attributes.

5.6.5.2 Configure NPort Server 6610-8/16

Basic Settings:
• Select System Configuration  Basic Settings and enter a descriptive name for the serial port
server (no blanks)
• Network Settings:
• Enter an IP Address and Netmask (see Port Server Network Settings)
• Disable SNMP if not needed
Check Port Settings:

The port configuration determines which ports of the serial port server(s) are mapped to which COM
ports on the host computer.
1 Check COM ports:
To ensure that there is no conflict between COM ports, check whether serial port server ports
[Moxa Communication Port x (COM y)] conflict with built-in COM ports [Communications
Port (COM z)] or other port server ports.
2 Check COM port mapping and configure port server ports:
In case of duplicate COM ports or if you want to change COM port assignment for other reasons:
a. Start Web Console and log in.
b. Open Serial Port Configuration  Port 1 (for example)  Operation Modes
c. Mode RealCOM must be selected for each port.
d. Ensure that the port servers do not conflict with built-in COM ports.
e. Document port settings using the table Serial Port Server Host Computer Installation
Documentation: on page 108.
Operation Modes:
For each port, select Real COM Mode, keep the default settings of Real COM attributes.

5.6.6 Install Software for Firmware Check 5610-8/16

When using Moxa 5610 series NPort servers, first install the old 5610 driver as described in the
following two sections Checking NPort Server Firmware for 5610-8/16 (only for firmware upgrade)
and Upgrading NPort Server Firmware for 5610-8/16. These steps are required to make the 5610
servers ready for the firmware update.
The required firmware revisions for serial port servers are:
SPS Firmware Revision:
NPort Server Firmware Revision
5610-8/16 3.9
5.6.6.1 Checking NPort Server Firmware for 5610-8/16 (only for firmware upgrade)
Run from the distribution medium: \Drivers and Firmware\Moxa Serial Port Server\NPort 5600
Series\Npadm_Setup_*.exe. Click through the wizard and keep all default settings. 
This installs the NPort Administration Suite and necessary drivers.
1 Start NPort Administration Suite  NPort Administrator.
2 Right click on Configuration in the left function window.
3 Select Broadcast Search.
4 Double click the appropriate serial port server to open the Configuration window, where the
firmware version is visible.

5.6.6.2 Upgrading NPort Server Firmware for 5610-8/16

If you need to update the firmware:
1 Start NPORT Administration Suite  NPort Administrator.
2 Press the Search button.
3 Select NPort Server.
4 Right click on Configuration in the left function window.
5 Select Upgrade Firmware.
6 On the distribution medium, browse to the folder: \Drivers and Firmware\Moxa Serial Port
Server\NPort 5600 Series\ and select the appropriate firmware for your NPort server.
7 Start the upgrade. In case of a ‘Time out’ error, repeat the steps above.
5.6.7 Install NPort Server 5610 and 6610 series common driver
software
Run from the distribution medium: \Drivers and Firmware\Moxa Serial Port Server\NPort 6600
Series\moxa-windows-driver-manager_*.exe. Click through the wizard and keep all default settings. 
This installs the NPort Windows Driver Manager and necessary drivers.
• Start NPort Windows Driver Manager
• Press the button + Add
• Click Search
• Select the appropriate NPort Server and click OK
• Click Yes to activate the COM ports

• Verify the network connection using ping.
5.6.7.1 Configure Accessible IP List (5610)

The serial port server maintains a list of known host computers (accessible IP list) that are allowed to
connect to the device.
To avoid simultaneous access of two computers to one serial port server, ensure that only the
IntelliSpace Perinatal host computer of the serial port server is registered in the accessible IP list.
• Select Accessible IP Settings:
• Enter IP address and Netmask
• Save configuration
For advanced settings see the MOXA manual.
5.6.7.2 Configure Accessible IP List (6610)

The serial port server maintains a list of known host computers (accessible IP list) that are allowed to
connect to the device.
To avoid simultaneous access of two computers to one serial port server, ensure that only the
IntelliSpace Perinatal host computer of the serial port server is registered in the accessible IP list.
• Select System Configuration Accessible IP List:
• Enter IP address and Netmask
• Save configuration
For advanced settings see the MOXA manual.
5.6.7.3 Serial Port Server Firmware Revisions for 6610-8/16

The required firmware revisions for serial port servers are:
SPS Firmware Revision:
NPort Server Firmware Revision
6610-8/16 1.17
5.6.7.4 Checking NPort Server Firmware for 6610-8/16

1 Start Web Console (open Web browser and enter IP address) and log in.
2 Check the firmware revision on the welcome screen.
5.6.7.5 Upgrading NPort Server Firmware for 6610-8/16

If you need to update the firmware:
1 Start Web Console and log in.
2 Select System Configuration Firmware Upgrade.
3 On the distribution medium, browse to the folder: \Drivers and Firmware\Moxa Serial Port
Server\NPort 6600 Series\ and select the appropriate firmware for your NPort server.
4 Start the upgrade.
5.6.8 Configure IntelliSpace Perinatal

1 Verify Basic Serial Connection
Start the FMSpy (see Fetal Monitor Spy (FMSpy) on page 193) and select a mapped COM port.
Start data transmission for this connection and check that data can be received.
2 Setup Serial Ports
Run the IntelliSpace Perinatal setup on the host computer for the serial port server. In the setup
program the COM ports can be selected as usual.
Run the IntelliSpace Perinatal Setup:
• Only change database settings or system settings
• Do not change system settings (no password required).
• Check Define port settings.
If not all COM ports are available verify the driver settings and check the access control lists.
Restart the computer and run setup again.
3 Assign Beds:
a. Start IntelliSpace Perinatal.
b. In Fetal Monitor Setup assign the available ports to IntelliSpace Perinatal beds. 
COM 1 .. COM4 are listed as FM 1 (A) .. FM 4 (D), all other ports as FM x.
5.6.9 Connect Fetal Monitors

See the Site Preparation and IT Specification Guide for pin assignments and cable layout.
Serial Port Server RS-232 Connectors:
Port Number RS-232 Remarks

Server of Ports Connector
5610-8 8 RJ45-8
5610-16 16 RJ45-8
6610-8 8 RJ45-8
6610-16 16 RJ45-8
Use adapter M1380-60610 for every fetal monitor connected to a 6610/5610 SPS. Please refer to the
Site Preparation and IT Specification Guide for the complete wiring scheme.
5.6.10 Check Fetal Monitor to Bed Connection

Perform the test described in the chapter Performance Serial Port Server on page 25.
5.6.11 Using the Serial Port Server at a Different Computer
1 On the old host computer

a. For 5610-8/16 (if NPort Administration Suite is still used): Open Start  NPort Administration
Suite  NPort Administrator.
Select COM Mapping, select the serial port server and Remove Target.
For 6610-8/16 and 5610-8/16: Open Start  NPort Windows Driver Manager.
Select COM Ports and Remove appropriate COM ports.
b. Run IntelliSpace Perinatal setup to remove the serial port server ports.
See also Configure IntelliSpace Perinatal on page 103, step 2.
c. Start IntelliSpace Perinatal and check port to bed assignment. 
See also Configure IntelliSpace Perinatal on page 103, step 3.
2 On the new host computer
a. Install the software (see Install Software for Firmware Check 5610-8/16 on page 99).
b. Configure the serial port server (see Configure Serial Port Server on page 96 or Configure
IntelliSpace Perinatal on page 103) and check the port mapping.
c. Configure IntelliSpace Perinatal. See Configure IntelliSpace Perinatal on page 103.
d. Check Fetal Monitor  bed connection. Perform the test described in the chapter Performance
Serial Port Server on page 25.
5.6.12 Replacing a Serial Port Server
To replace a serial port server you must perform the following steps:
1 Physically connect the new port server device to the network. See Connect Port Server on page 94
2 For 5610-8/16(if NPort Administration Suite is still used): Open Start  NPort Administration
Suite  NPort Administrator.
• Select COM Mapping, select the old serial port server and Remove Target.
• Select Configuration  Specify by IP Address. Enter the IP Address of the new serial port
server device.
For 6610-8/16 and 5610-8/16: Open Start  Windows Driver Manager.
• Select COM Ports, select the serial port server and Remove.
• Select Add and enter the IP Address of the new serial port server device.
3 Configure the serial port server (access control / access IP list). See Configure Accessible IP List
(5610) on page 101.
The new port server must be hosted at the same host computer as the defect port server. See Serial
Port Server Host Computer Installation Documentation: on page 108.
4 Connect the fetal monitors to the serial port servers and check the connections.
Serial Port Server

Installation Documentation
List all serial port servers and their IntelliSpace Perinatal host computer.
Date: ____________________
Serial Port Server Installation Documentation:
Port Server IntelliSpace Perinatal Location/Remarks

Host Computer
Name IP Address Name IP Address

___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
___.___.___.___ ___.___.___.___
This page intentionally left blank.
Serial Port Server Host Computer

Installation Documentation
Use one page for each serial port server host computer.
List all serial port servers hosted at the computer and all port server ports mapped to local COM ports.
Date: ____________________
Computer Name: ____________________ Location: ____________________
IP Address: ____________________
Serial Port Server Host Computer Installation Documentation:
Port Server Mapped Remarks

to
Name Port
COM
This page intentionally left blank.
5 Setup Details Installing Word and Excel Templates
5.7 Installing Word and Excel Templates

5.7.1 Overview
5.7.1.1 Prerequisites
• IntelliSpace Perinatal must be installed with the External Database option.
• Windows administrator rights.
• You must be able to access the templates share (<server>\OBTVTemplates). The templates share is
C:\Tv2_Templates at the Internal Server machine.
• Microsoft Office
• IntelliSpace Perinatal Key for Reports and Statistics
5.7.1.2 Directory Structure

The initial installation of IntelliSpace Perinatal installs templates
and other files required for Word documents and Excel statistics in
the C:\Tv2_Templates directory on the Internal Server machine. This
directory is shared as OBTVTemplates.
...\code:
templates, macros and binary files for template support
do not modify the contents of this directory
...\factory:
directory for factory-provided templates
contents may be overwritten or modified by future IntelliSpace
Perinatal releases
do not modify the contents or store customized templates in this
directory
...\customer:
directory for templates accessible by the printing module
directory for customized templates
contents will not be overwritten or modified by future IntelliSpace
Perinatal releases
...\maternal: directory for templates used in maternal mode
...\newborn: directory for templates used in newborn mode
...\...\excel: Excel templates (*.xltx)
...\...\word: Word templates (*.dotx)
...\...\...\auto: files in print in the background
...\...\...\manual: files open Excel or Word
Installing Word and Excel Templates 5 Setup Details
Copy new factory-provided templates from C:\Tv2_Templates\factory to C:\Tv2_Templates\customer

to make them accessible for printing mode. This may be required for system upgrades with Setup
option Keep current: Document Templates. Setup copies all templates into the customer folder in all
other scenarios.
5.7.1.3 Microsoft Office

Microsoft Office must be installed.
See the IntelliSpace Perinatal Site Preparation and IT Specification Guide for information on how to
access Word and Excel templates.
5.7.1.4 Template Revisions
Template Latest layout change released with Rev. ...

Reports
Admission Summary.dotx K.00.12
Admission.dotx K.00.20
Anesthesia Summary.dotx H.00.00
Antepartum.dotx K.00.12
Care Unit Rounding List.dotx G.00.20
Complete Episode Record - Delivered.dotx K.00.20
Complete Episode Record - Undelivered.dotx K.00.20
Complete Prenatal Visit Record.dotx K.00.12
Discharge Summary_All_Patients.dotx J.00.00
Discharge Summary_Delivered.dotx J.00.00
Discharge.dotx G.00.20
DischargeRecord.dotx K.00.10
DischargeSummary.dotx K.00.20
Face Sheet.dotx G.00.20
FCAssessByTime.dotx G.00.20
FCAssessByType.dotx G.00.20
GYN All.dotx K.00.10
GYN Visit.dotx K.00.10
Inpatient Postpartum.dotx G.00.20
Labor and AlternateDelivery.dotx G.00.20
Labor and Delivery Summary.dotx K.00.10
Labor and Delivery.dotx G.00.20
Labor&Delivery.dotx G.00.20
Med Reconciliation Report.dotx G.00.20
NST Overview.dotx G.00.20
NST.dotx J.00.21
NST DawesRedman.dotx J.00.21
Newborn Admission Summary.dotx G.00.20
Newborn Discharge Summary.dotx J.00.00
Newborn Episode Record.dotx K.00.10
Newborn Face Sheet.dotx G.00.20
Newborn Summary of Stay.dotx J.00.10
NurseryAdmission.dotx K.00.10
NurseryDischarge.dotx K.00.10
NurseryFCAssessByTime.dot G.00.20
NurseryFCAssessByType.dotx G.00.20
ObstetricAdmit.dotx K.00.12
PatientsPregnancyEpisodes.dotx G.00.20
Postpartum Follow Up Visit.dotx K.00.10
PostpartumVisit.dotx K.00.10
PostpartumVisits.dotx K.00.10
Prenatal Visit List.dotx G.00.20
Prenatal Visit Summary.dotx K.00.10
Progress Notes.dotx G.00.20
ProgressNotes.dotx G.00.20
SBAR Report.dotx G.00.20
Summary of Stay.dotx K.00.10
Teaching Summary.dotx G.00.20
Teaching.dotx G.00.20
Triage Visit.dotx H.00.00
Empty Reports
TVReportM.dotx D.01.00
TVReportN.dotx D.01.00
Statistics
Benchmark_DeliveryByType.xltx G.00.20
Benchmark_GA.xltx G.00.20
Delivery Stats-Core.xltx G.00.20
Obstetric Statistics.xltx G.00.20
Regular Admin Statistics.xltx G.00.20
Yearly Admin Statistics.xltx K.00.12
Yearly Administrative Statistics.xltx K.00.12
Logs
Admission Log.xltx G.00.20
Augmentation Log with Statistic.xltx H.00.00
Baby Friendly Log with Statistic.xltx H.00.00
Bloodstream Infection Log - Core.xltx H.00.00
Breastfeeding Log - Core.xltx H.00.00
C-SectionLog.xltx H.00.00
CCHD Newborn Screening Log.xltx J.00.20
Cesarean log - Core.xltx H.00.00
ChalkboardM Log.xltx G.00.20
ChalkboardN Log.xltx G.00.20
Delivery Attendant Log.xltx G.00.20
Delivery Log.xltx G.00.20
Discharge Log.xltx G.00.20
Elective Delivery Log - Core.xltx H.00.00
Elective Induction Log - Core.xltx H.00.00
EMTALA log.xltx K.00.12
Fetal Alarm Log.xltx K.00.10
Fetal Death Log.xltx G.00.20
Labor&Delivery Log.xltx G.00.20
Labor&Delivery Detailed Log.xltx K.00.10
Live Birth Log.xltx G.00.20
Maternal Alarm Log.xltx K.00.10
MeaningfulUse Stage II.xltx H.00.20
Neonatal Abstinence Log.xltx J.00.00
Installing Word and Excel Templates 5 Setup Details
NurseryAdmission Log.xltx G.00.20

NurseryDischargeLog.xltx G.00.20
Nursery Feeding Count Log.xltx K.00.10
Open Cases 12 Month.xltx G.00.20
Open Pregnancies.xltx G.00.20
OR Procedure Log.xltx H.00.00
Pre Oxytocin Checklist Log.xltx J.00.00
Preeclampsia Evaluation Log.xltx K.00.10
Patient Creation Log.xltx G.00.20
Perinatal Death Log.xltx G.00.20
Perinatal Initiative Log.xltx H.00.00
Providers Log.xltx G.00.20
Scheduled Log.xltx G.00.20
Smoking Status Log.xltx J.00.00
Steroid use log - Core.xltx H.00.00
Stillborn Log.xltx G.00.20
SystemAuditTrail Log.xltx G.00.20
Transfer Log.xltx G.00.20
Undelivered Log.xltx G.00.20
Vacuum Bundle Log with Statistic.xltx H.00.00
Zip Log.xltx G.00.20
5.7.2 IntelliSpace Perinatal Key for Reports and Statistics

The IntelliSpace Perinatal Key for reports and statistics has to be defined for access to the external
database by Microsoft Office.
Start the IntelliSpace Perinatal System Console (to be found in the Windows start menu under
IntelliSpace Perinatal Support). In the left pane, select the node Console Root\IntelliSpace Perinatal
System Console\Patient Processes\Exporter. Then select Provide Key for Reports and Statistics on
Actions pane on the right.
5.7.3 New Installation

Only templates stored in the auto and manual subdirectories of C:\Tv2_Templates\customer can be
selected in the IntelliSpace Perinatal printing module. During setup, all factory-provided templates are
copied from C:\Tv2_Templates\factory to C:\Tv2_Templates\customer.
6
6Network Based Storage
6.1 Introduction
Please refer to the IntelliSpace Perinatal Site Preparation and IT Specification Guide for details and
instructions how to protect the NBS path against malware spreading or data modification by malware.
6.2 Prerequisites
NBS requires sufficient free space for IntelliSpace Perinatal to write the necessary data, which must be
available for subsequent retrieval. If there is insufficient space, archiving of data is postponed until
enough space is available. This may lead to filling up the hard disk of Internal Server.
Please refer to the IntelliSpace Perinatal Site Preparation and IT Specification Guide for more details.
6.3 Local Storage Directory

When a local directory is used as the archive location, do not enter user credentials in storage
configuration page when running IntelliSpace Perinatal setup (if they are provided they are ignored). A
local directory, all files and all sub directories must have full access permission by the local Windows
user group OBTV Internal Group.
CAUTION It is not supported to permanently archive to local hard drives of non-virtualized IntelliSpace Perinatal
computers. In virtualized environments, the NBS location must not reside on the same LUN as any of
the virtualized IntelliSpace Perinatal machines. This may only be done temporarily for
troubleshooting, if required.
6.4 Location of the Archive Computer Function

The storage functionality can reside on any computer in an IntelliSpace Perinatal network except on
the Remote Desktop Session Host Server.
6 Network Based Storage Changing the Archive Computer Function to a Different Machine
6.5 Changing the Archive Computer Function to a

Different Machine
To move the archive function to another computer (for example, the Internal/External Server, or a
client) after successful conversion:
1 Shut down the IntelliSpace Perinatal system.
2 Run IntelliSpace Perinatal on current Archive computer and select box to change Storage settings.
3 Do not disable System-wide storage option if setup is run at the Internal Server.
4 Disable setting (uncheck box) Archive and retrieve is running on this PC and complete setup.
5 Run IntelliSpace Perinatal setup on new Archive computer and, using the check box, enable the
setting Archive and retrieve is running on this PC and complete setup.
6 Start IntelliSpace Perinatal at the Archive computer and check NBS storage icon and archive/
retrieve operation.
6.6 Moving the NBS Location to Another Location

See the IntelliSpace Perinatal System Administration and Configuration Guide.
6.7 Changing NBS User Credentials with

IntelliSpace Perinatal Running
See the IntelliSpace Perinatal System Administration and Configuration Guide.
6.8 NBS Folder Structure and Archive Index
The above picture shows the NBS folder structure and archive index folder of a brand new IntelliSpace
Perinatal installation configured for NBS. The current archive folder is the folder with the long name
(also visible in the IntelliSpace Perinatal Storage Service Tool, shown below).
Service Storage Tool 6 Network Based Storage
6.9 Service Storage Tool

You access the Service Storage tool from the system console. To see the current
storage location and a list of storage directories, click this icon.
It is available on the computer hosting the archive functionality.
The following screen displays a list of all storage locations used by this IntelliSpace
Perinatal system. If No is shown in the Available column, this means that the location is stored in the
database but physical access to this location is not yet available. The location must show Available Yes
to allow retrieval.
The little triangle at the left hand side indicates the current archive folder.
6 Network Based Storage Additional References for Network Based Storage
6.10 Additional References for Network Based

Storage
See also the IntelliSpace Perinatal System Administration and Configuration Guide.
6.11 Integration Testing

See the IntelliSpace Perinatal Integration Guide for details of integration tests required after NBS
implementation.
7
7 Troubleshooting
7.1 Networking and System Setup Problems

Check for all applicable Field Change Orders when troubleshooting problems.
Setup and Startup Problems:
Problem Explanation Problem Verification Remedy
After new installation of the DHCP scope not created. Check if the server’s NIC is Manually configure DHCP.
operating system at the server If the server is not connected connected to the network. See DHCP Server on page
Setup fails at the clients. 258.
to the network during
installation the DHCP scope
is not created.
IntelliSpace Perinatal does not Setup program has been Rerun Setup from the Support
start, system gives message: started then cancelled. menu group (no DVD-ROM
setup not complete required). Step through all
menus, enter the appropriate
parameters.
IntelliSpace Perinatal does not Storage is defined in setup, Check the installation record Run setup again, deselect the
start at the server (no storage). but this is a non storage for storage definition. storage option.
The progress bar goes to 75% system.
and then moves backwards
again.
IntelliSpace Perinatal Client IntelliSpace Perinatal not Check server. Start IntelliSpace Perinatal at
won't start - goes into running at server. server.
shutdown immediately then
hangs with message: 
Wait until system writes
unsaved data
Client does not connect to Physical connection Check Switch. Adjust workgroup name.
server. interrupted. Check Server. Start server before clients.
Server not working Check computer names - use  Adjust computer names.
Wrong client computer name. Control Panel / Network. Establish server share.
Share on Server not Check share with 
established. Windows Explorer.
7 Troubleshooting Networking and System Setup Problems
Setup and Startup Problems:
IntelliSpace Perinatal does not You didn't run IntelliSpace Check the installation record  Power off, restart the
start after changing a Perinatal setup after changing (IntelliSpace Perinatal computer, 
computer name. the computer name. The new IntelliSpace Perinatal group re-run IntelliSpace Perinatal
computer name must be icon). This shows the Setup. Do not accept defaults,
entered into the database. computer name used by enter the correct parameters.
IntelliSpace Perinatal.
Windows runs CHKDSK File corruption detected and Wait until CHKDSK has
(CheckDisk) automatically. will be corrected finished. Replace hard drive,
automatically by CHKDSK. as necessary.
SHUTDOWN One of the clients is waiting Check clients. Acknowledge dialog-box at all
 for input (such as clients.
(Server hangs) acknowledgment of error-
message).
DIALOG-box does not You have multiple Move current message box
accept input. overlapping message boxes, aside. Repeat this until you
and the active one is behind reach the active one that
the one currently displayed. require input.
SYSTEM MESSAGE occurs Serious internal error. Press Restart to restart the
during normal operation: computer. If this message
serious error, restart PC  keeps coming back then
No network messages shutdown complete system (at
displayed server) and restart.
Make sure you restart the
requested computer, and not
the computer where you read
the message!
External database cannot be External Server is already Check all installed clients De-install external database
installed on External Server installed on the other installation record. from other client. Install
computer. computer. external database on desired
computer.
IntelliSpace Perinatal setup on After a OS re-installation e.g. Check content of D:\ drive If you really want to restore
the Internal Server offers a in case of an upgrade there from an IntelliSpace Perinatal
"recover" option instead of a might be left over files on the backup, erase the left over files
"restore a previously saved D:\ drive. from the D:\ drive.
installation" option.
Networking and System Setup Problems 7 Troubleshooting
Network Errors:
Network error messages Network has become Check switch and all Do not click OK or Hide; click
during normal operation: disconnected connections error-messages on on Restart. Make sure all
Network error has occurred; Message number 3 keeps server and other clients. network connections are
alarm affected; repeating after re-connection correct. Acknowledge all
if there was no attempt to error-messages at server.
Serious error, restart PC
access to the disconnected
Cannot read/write patient- client.
data
Message number 2 displays
Client does not seem to after re-connecting to
accept input network.
if system tried to access to the
disconnected client
Network error messages after At systems with two network Check NIC assignment. Connect external NIC to
reinstallation of Windows interface cards: hospital network, connect
Reinstallation of Windows internal NIC to IntelliSpace
may change NIC assignment. Perinatal network.
Serial Port Server Setup
A data acquisition machine IntelliSpace Perinatal is not The IntelliSpace Perinatal Troubleshoot the MOXA port
configured to run with a able to open mapped COM logfile shows unsuccessful server setup according to the
Moxa port server does not ports successfully. attempts to open COM ports description below.
display traces. mapped to a MOXA port
server.
Troubleshoot the MOXA port server setup:
Problem Solution
Improper IP configuration Make sure that your Host is able to PING the NPort.
Improper OP_mode Your operation mode must be [Host Based / Driver Mode] or [Real COM
Mode].
DHCP issue If your Host and NPort are in DHCP environment:

a. You have to assign a fixed IP address to NPort and your host.
b. Under a DHCP environment, you can reserve a specific IP address for
your NPort's and your host's MAC address.
Access authorization Use NPort Configurator or Administrator to check the NPort's access control
list; your Host IP must exist in the NPort access control list.
COM port number conflicts Check if there is any other installation using the same COM port number, e.g.,
with other devices internal modem on COM3.
Your firewall filter rule discards Check the filter rules to open TCP port # 950(to 965) & # 966(to 981).
the specific TCP packet
7 Troubleshooting Networking and System Setup Problems
Problem Solution
Port is occupied Telnet NPort's IP address, and check the ''Conn. Status'' message under
[Monitor]. It must be set to ''listen'' before you open the port.
Forgotten to click Apply and Click Apply after setting the COM Mapping with NPort5000/NE series. Click
Save button Save after installing the Driver with the NPort Server Family.
Network Storage Access 7 Troubleshooting
7.2 Network Storage Access

If there are access errors to the network storage location, perform these tests on the Archive computer:
7.2.1 Checking Network Connectivity

Open a command prompt and type net use <network storage path> /user:<network storage user>
If network access is possible, then this connection can be made.
7.2.2 Checking File Access

CAUTION Do not overwrite any existing file. After test is finished, do not remove any files created by the
Start notepad.exe and try to write a txt file to the network storage location. This can be done in the
base directory and in any subdirectory of the network storage location. Remove any files you create
after the check.
7.2.3 Closing the Network Connection

Open a command prompt and type net use /del <network storage path>
7.3 Hardware Problems
Hardware Problems:
Sound not working. Cable connection, Verify wire connection to speaker and system Replace speaker and
alarm-configuration. board. check connections.
Check Control Panel for volume setting and
system sounds enabled. Verify sounds.
7 Troubleshooting Fetal Monitor Connection / Data Acquisition Problems
7.4 Fetal Monitor Connection / Data Acquisition

Problems
Fetal Monitor / Data Acquisition Problems:
No traces from M1350A after RS422-I/F in fetal monitor is Check I/F-cards. Remove RS422-card; so only
installing RS-232 System plugged in (and takes Check connector: RS-232-IF is plugged in or
Interface. precedence). adjust system setting to RS-
Bar-code (wrong) is on 232-IF according to FM
Wrong connector used processor board.
(Barcode 9pin D-sub on manual.
processor-board). System (correct) is on system Use correct connector and
board M1350-66536. cable.
Wrong cable.
Cable: M1380-61612. Use correct connector and
cable.
No traces from M1351/53A Wrong I/F board, wrong Check I-F board and Use correct HW as described;
after installing RS-232Sys-IF. firmware revision, wrong firmware rev. (print error-log no mode setting required.
cable. on fetal monitor).
Cable: M1380-61613.
Connector: HPIB-type 25pin.
Verify I/F: M1353-66531(E).
Verify firmware: A.02.02.
No traces from non-HP/ Mode not adjusted at fetal Shutdown IntelliSpace Adjust mode at fetal monitor.
Agilent/Philips fetal monitor monitor; see FM manual. Perinatal at this client.
or from analog FMs. Wrong cable / converter. Start program FM-Spy from
OBTV support group.
if monitor-ID is displayed
correctly then cable/converter
are ok.
if no monitor-ID is displayed
then cable problem or wrong
converter.
No traces from any type of Setup was run but port NA Re-run setup / select correct
Fetal Monitor. settings were not selected. port settings.
Fetal Monitor Connection / Data Acquisition Problems 7 Troubleshooting
Fetal Monitor / Data Acquisition Problems:
When starting data This is due to Windows access Ensure Windows users group Two variations are allowed:
acquisition, a system alarm rights issues of the user membership, both on the data The user account is only a
"cannot read patient data" running IntelliSpace Perinatal acquisition host and on the member of the local group
may occur. on the data acquisition host. Internal Server. OBTV Users on the data
acquisition host.
It is not a member of any of
the Administrators group on
the Data Acquisition Host
and the Internal Server.
If the user account is a
member of the local group
Administrators, it also must be
a member of the Internal
Servers local Administrators
group.
Unreliable connection or "lost With Avalon software Check that the Avalon Fetal Check availability of software
messages" with LAN revisions higher than L.33.61, Monitors have a software upgrades for Avalon Fetal
connection to Avalon FM20/ the more reliable Ethernet revision higher than L.33.61. Monitors.
30/40/50. OBMS Encapsulation Check that XDS is installed Install XDS as described in
Tunnel Protocol is available, on the data acquisition host “XDS Installation” on
which can improve FM PC. page 297.
connections under adverse or
complex network conditions. Check that the Windows If Avalon software upgrades or
Service IPM RDist Service is XDS installation is not
This new protocol requires running. feasible, the data acquisition
XDS installed on the data host should be located
acquisition host PCs. physically closer to the fetal
monitors.
7 Troubleshooting Application Problems
7.5 Application Problems
Application Problems:
Patient list does not display all You are logged-in as user Verify user identity. Log-in as regular user with
beds. Philips. permission to see all beds.
Note: Never create/edit/delete
patient related data when you
are logged on as an Philips
user.
A message is displayed saying External Server computer Does the External Server run? Start up External Server.
that the External Server installed and configured but
computer is not running. not started.
Cannot log in as Philips user Users can change the Reinstall IntelliSpace Perinatal
password at the sever. See Restoring the
IntelliSpace Perinatal Philips
Password on page 251.
Decreased performance when Users face significant delays To troubleshoot the printing - Run test prints and review
printing documents. when printing documents. performance of individual the timings in the logs.
computers, advanced logging - Let customers print their
can be switched on and off. normal printing for a few days
For this purpose, two files are and review the logs for
provided in the installation significant delays.
medium in the folder OB
TraceVue\Tools\Advanced
Print Logging
- To switch advanced logging
on double-click
AdvancedLogging_On.reg
- To switch advanced logging
off double-click
AdvancedLogging_Off.reg
The detailed logging is
written to this computer’s log
file in the \tv2\logdata folder
of the Internal Server.
It is recommended to switch
off advanced logging after
troubleshooting to prevent
filling up the log file with
printing activity.
Switching on advanced
logging for many clients can
have a small impact on the
network performance due to
increased network activity.
Application Problems 7 Troubleshooting
Application Problems:

When connecting with an RD On the RD session host in the Check if the switch is missing. Append IntelliSpacePerinatal.exe
client you don’t see the startup of "Remote Desktop Session Host by the switch /remote
IntelliSpace Perinatal with the Configuration”, Environment tab, C:\TV2\prog\IntelliSpacePerinatal
progress bar. Instead you IntelliSpace Perinatal .exe /remote
immediately see another running (IntelliSpacePerinatal.exe) has to
IntelliSpace Perinatal session. be started with the switch /remote.
Documents or Statistics not No External Server machine Check if the External Server Start External Server
enabled in the printing dialog machine is configured and running
No template files available Check if the templates are Copy templates. See 5.7 Installing
available. In the Printing dialog, Word and Excel Templates on
open Properties, click Documents page 110.
or Statistics tab.
Office not installed Check if Excel or Word is Install Office. See the IntelliSpace
installed, and can be started Perinatal Site Preparation and IT
Specification Guide.
Office .NET programmability Check if .NET Programmability Install .NET Programmability

support not installed Support is installed. Support. See the IntelliSpace
Perinatal Site Preparation and IT
7 Troubleshooting Application Problems
8
8IntelliSpace Perinatal Services
8.1 Services Overview

Starting with Rev. H, the background functionality of IntelliSpace Perinatal is moved into Windows
Services. Services are programs that run in the background without a user interface, even when no user
is logged into the OS. All functionality providing user interaction is still in the IntelliSpace Perinatal
application. The application does not contain functionality which is needed permanently as a
background process. Therefore it does not matter whether the application is running on any machine,
the IntelliSpace Perinatal system is running in the background.
The following functionalities are hosted by services:
• Server functionality
• Internal network communication
• Data export to External DB
• HL7 interface
• Link interface
• Storage functionality
• Document Export Management (not the document generation)
• FM data acquisition (serial and network)
• Database Server
For details about these services see below.
8.1.1 General Service behavior

An IntelliSpace Perinatal service has two separate states:
• Started/Stopped
This is the status visible in Windows (services.msc)
The System Console allows to select individual services and start or stop them.
8 IntelliSpace Perinatal Services Services Overview
• Active/Inactive
An IntelliSpace Perinatal service can be in state Started, but still be Inactive. A stopped service is
always inactive. This Active/Inactive state is only controlled by the System Console. The Active
column in System Console PCs and Services shows Yes only if the service is started and active.
Otherwise it shows No. 
Stopping and starting the service from Windows or individually from the System Console does not
change the Active/Inactive state.
After starting Windows, all IntelliSpace Perinatal services are running, and the functionality of the
services is active. All service processes are set up as automatic startup and are always running. In
Windows Task manager, the services are listed as running.
8.1.2 New System startup and shutdown functionality

When Windows is running, all IntelliSpace Perinatal services are active, i.e. whole system is online.
Therefore it is necessary to have the option to control the active state of the system and sometimes the
active state of a single service.
To control the active state of the system and/or services, use the IntelliSpace Perinatal System Console,
to be found in the Windows start menu under IntelliSpace Perinatal Support). This console contains
nodes to monitor the active state of computers and services and to control the active state of the whole
system. In addition, after running the Internal Server setup, the operator has the possibility to start up
(activate) or to keep down the whole system.
The PCs and Services node of the system console shows the active state of the application and all
services installed on the different machines. The sub-nodes of this node provide special filters to view a
subset of the installed machines and their services.
The System node of the system console shows the overall system state and allows to control the whole
system.
8.1.3 Overall System state

In some cases it may be necessary to shut down or keep down (after setup) the whole IntelliSpace
Perinatal system, e.g. for upgrade or recovery scenarios.To review and control the overall system state,
use the System node of the IntelliSpace Perinatal System Console on the Internal Server. In addition,
the Internal Server setup allows for keeping the system down after running setup. In the System node
the current state of the system is shown:
• Number of active client applications
• Number of active RD client applications
• Number of active services
• Overall system state:
– System is up and running (green indicator): Applications can be started on server and clients.
Services are active (if not stopped manually).
– System is shutting down or starting up (yellow indicator): Some services or applications are still
active, some are not.
– System is shut down (red indicator): No applications or services are active, the system is
completely offline. (Services are still running, but inactive)
Services Overview 8 IntelliSpace Perinatal Services
8.1.3.1 Shutdown
The System node provides two possibilities to shut down the system:
• Shut down whole system, restart applications in wait mode: 
This deactivates all services and restarts all currently active applications into wait mode. Applications
wait for server clearance until the system is restarted. If users start applications in this system state,
the applications will wait for server clearance until the system is restarted. On later system startup,
all services and waiting applications will become active automatically.
• Shut down whole system: 
This deactivates all services and shuts down all active applications. If users start applications in this
system state, the applications will wait for server clearance until the system is restarted. On later
system startup, all services will become active automatically, the applications have to be started
manually, unless they were in wait mode.
After the system was shut down from the System Console or the Internal Server setup, even a reboot of
the computer will not activate the services. Windows Services start up automatically, but they only
become active when the system is started from the System Console or Internal Server setup.
Applications are not started automatically unless the computer is configured for auto login and the
application is in the startup folder of the logged in user.
8.1.3.2 Startup
The System node provides two possibilities to start up the system:
• Start whole system: 
Allows to start the application on all servers and clients and activates all services. Services that were
stopped manually do not become active. Data Acquisition starts automatically on all configured
beds. Applications in Wait mode will start automatically.
• Start internal server only: 
Allows to start the application and activates services on the Internal Server only. Services and
applications on other clients are not active.
8.1.4 Single service or application state

The PCs and Services node allows to view the state of single applications and services in the system.
8.1.4.1 Viewing
The node shows the following columns:
• Name: Name of the service or application session. For applications this name can be configured
using the PCs configuration in the application. The names of services are fix and cannot be
configured.
• Active: Shows the active state of a service or an application. For details, see below.
• Internal name:
– Services: This is the network name of the computer, combined with the service name of the
service.
– Remote desktop applications: This is the session name of the RD session.
– Thick client application: This is the network name of the computer.
• Current User: Shows the name of the currently logged-in user of an application. For inactive
applications this is the name of the select computer default set. 
Services do not have a current user (always empty).
• N of DACs: Shows the configured number of data acquisition instances configured for a computer.
This column is only valid for client applications. This number is the sum of configured classic and
network data acquisition instances.
• Ping result: Shows the result of the last network ping request. Because of their temporary nature, the
results are cleared after two minutes.
The column Active shows whether a service or an application is active and running with its full
functionality within the system.
• Active = Yes: Service or application is active, that is, it provides its full functionality.
• Active = No:
– Services: An inactive service is in 'standby' mode and does not provide any functionality, or it is
not running. To verify whether a service is running, use the Services page of the Windows Task
Manager or the Services snap-in of the MMC (Microsoft Management Console). In these tools,
the column Status shows whether a service is running/started or not. A service in 'standby' mode
is running and waits for clearance by the OBTV NetMsgService to become active.
– Applications: An inactive application is not running or waits in startup for the clearance to start
up completely.
8.1.4.2 Actions
The PCs and Services node of the system console allows performing the following actions:
• Restart Windows: Available when a computer is selected, allows restarting Windows on that
computer.
• Ping: Available when a computer is selected, allows to send an ICMP request to servers and clients.
• Ping all: Always available, sends ICMP requests to all servers and clients.
• Start Service/Stop Service: Allows starting and stopping services. 
This requires that the Windows user running the System Console has administrative rights on the
host where the service shall be stopped or started. 
Be aware of the fact that a manually stopped service will stay stopped until it is manually started
again. It will not provide any functionality to the system while it is stopped. Because the active/
inactive state of a service does not reflect whether the service is running or not, an error may occur
when trying to start an inactive service, because the service is already running but not active. To
analyze why the service is not active, see the log file of the service.
• Start/Stop Application: Allows starting the application on the selected machine. This requires that
the Windows user running the System Console has administrative rights on the host where the
application shall be started and that any user is logged into the remote machine. The application will
be started in this session.
To stop the application remotely you need to log on using RDP or VNC and stop the application
manually.
8.1.4.3 Notice
Stopping an application on a client or server (even on the Internal Server) will not influence the active
state of the system. All services keep on running, even when no user is logged into a client or server.
Single services can be stopped or started with the System Console or the Windows Task Manager. The
order in which the services are stopped or started doesn't matter. It is not recommended to stop
individual services while the system is started up, unless there are strong maintenance reasons. When
individual services are stopped while the system is started up, not all functionality is available, and
errors or warnings might be reported by the system.
8.1.5 Detailed Technical Information on Services

Each service is set up in the IntelliSpace Perinatal system as an own session. Such a session can be a
service or an application (client or RD session).
Each service and each application session has its own activation state, which can be viewed in the
system console.
8.1.5.1 Logging
Each service and each application writes a log file with the internal name of the service or application
into the logdata directory of the installation. There are two log files for each service and application:
• Local log file: This log file is written until the network connection to the server is established. It
contains the first entries of the startup and the entries while the service or application process is
running, but not active. This log file resides in the logdata directory on the machine where the
application or service is hosted on. When a service does not get active, this local log file is a good
starting point to search for the reason why.
• Server log file: This log file is written when the network connection to the Internal Server is
established. Normally all log entries that occur while the service or the application is active are
written into the log file on the Internal Server.
For services and the application hosted on the Internal Server, the local and the server log file are
identical.
8.1.5.2 List of Services

The following table lists all services installed and used by IntelliSpace Perinatal:
Service name Occurrences Hosted on Listed in Description
PCs and
Services
of System
Console
OBTV NetMsgService 1 per system Internal Server No Internal network
communication
OBTV Server Service 1 per system Internal Server Yes Server functionality
OBTV Exporter Service 1 per system External Server Yes Exporter to maintain the
data in the external DB
OBTV HL7 Service 1 per system Link/HL7 Yes HL7 interface
computer
OBTV Link Service 1 per system Link/HL7 Yes Link interface
computer
OBTV Storage Service 1 per system Archive Yes Storage interface
computer
OBTV DOX Manager Service 1 per system Document  Yes Document export manager;
Export document creation is not
computer hosted in a service
OBTV DAC Service_XXX 1 per DAC Each computer Yes FM data acquisition and
instance hosting data trace alarming
acquisition functionality.
OBTV Network FM Service 1 per DAC Each computer Yes Dispatcher for network FM
Server hosting hosting data connections to network
network data acquisition data acquisition instances
acquisition
OBTV Service 1 per Each computer Yes Time synchronization

computer functionality.
Controls automatic local
recovery on internal and
archive server.
OBTV Application Starter 1 per Each computer No Allows starting the

Service computer application, used by setup
and future service pack
installer.
SQLANYs_OBTV_DB_ 1 per system Internal Server No SQL Anywhere database

SERVER server, internal database
SQLANYs_OBTV_EXTDB_ 1 per system External Server No SQL Anywhere database
SERVER server, external database
8.1.5.3 Services and Local Data Recovery Tool

For information about interaction of Services and the Local Data Recovery Tool, see the chapter Local
Data Recovery Tool.
8.1.5.4 Document export functionality

All background functionality of the IntelliSpace Perinatal system is moved into services, but there is
one exception: The document generation module of the document export functionality.
The document generation is based on printer drivers (e.g. Adobe PDF) that rely on user settings of a
logged-in user. This printer driver cannot be used by a service. Therefore it is necessary to run the
application on the computer where the document export is hosted. The document export manager
service will check for the running application on the Document Export computer. When the
application is not running, a system message is generated.
8.1.6 IntelliSpace Perinatal Service and Application Monitoring and

Recovery
In order to keep an IntelliSpace Perinatal system up and running with its full functionality, the states of
all services and running applications are continuously monitored and automatically recovered if
necessary.
In general, the system detects crashes (unexpected terminations) and hang situations of IntelliSpace
Perinatal applications and services as well as intentionally or accidentally stopped services. After
timeouts, system messages are issued and automatic restarts take place if required. The detailed
behavior is described below.
8.1.6.1 IntelliSpace Perinatal Applications

An IntelliSpace Perinatal application crash is typically detected immediately by the AppWatch process.
A hang situation is detected after a timeout of 2 minutes. During a hang situation the System Indicator
(steam engine) stops moving.
After detection of such situations, the IntelliSpace Perinatal application is restarted automatically by
the AppWatch process.
If a running IntelliSpace Perinatal application is shut down, it needs to be started manually. This can
be done locally using the Windows user interface or remotely using the IntelliSpace Perinatal System
Console.
8.1.6.2 IntelliSpace Perinatal Services

All IntelliSpace Perinatal services are configured for automatic start upon Windows startup. (Except
the OBTV SQL Anywhere service on the Internal Server, see below.)
General behavior:
A crash of an active IntelliSpace Perinatal service is typically detected immediately by the Windows
operating system.
A hang situation is detected after a timeout of 5 minutes. After detection of such a situation, the service
is restarted automatically by the Windows operating system.
If an IntelliSpace Perinatal service cannot be restarted after a crash or is stopped intentionally or
accidentally by an operator or by another software, this is detected by the system within 5 to 7 minutes.
The System Indicator starts flashing on all running IntelliSpace Perinatal applications and System
Consoles to inform the user that an IntelliSpace Perinatal service is unexpectedly not active. An
operator has to restart that IntelliSpace Perinatal service manually. This can be done locally or remotely
using Windows service management tools or the IntelliSpace Perinatal System Console.
If all IntelliSpace Perinatal services are active again, the System Message is revoked after 2 minutes, and
the System Indicator stops flashing. If the System Message is acknowledged by a user, it is not issued
again.
IntelliSpace Perinatal services on a switched-off machine:
An installed IntelliSpace Perinatal machine is considered as switched on if at least the OBTV Service
(which is installed on every IntelliSpace Perinatal machine) is active. If an IntelliSpace Perinatal
application is running or starting on an IntelliSpace Perinatal machine, this machine is also considered
as switched on and will be monitored.
Generally, the system issues an error if an installed IntelliSpace Perinatal service is not active on a
machine that is recognized as switched on. On IntelliSpace Perinatal machines that are recognized as
switched off, the installed IntelliSpace Perinatal services are considered as not required. Therefore, no
error about missing IntelliSpace Perinatal services is issued.
If, for some maintenance reasons, IntelliSpace Perinatal services need to be stopped, it is strongly
recommended to keep the OBTV Service running, and therefore this machine is being considered as
switched on. There is no need to run the IntelliSpace Perinatal application for that.
The IntelliSpace Perinatal System Console gives an overview of the Service Status, Application Status
and Upgrade Status of all running IntelliSpace Perinatal machines. For more information about the
System Console, please refer to the embedded help.
8.1.6.3 Interfacing Services

The following services are monitored in addition to the mechanism described above. Independently of
whether their hosting machine is recognized as switched on or switched off, a system message is issued
if one or more of the following services are installed but not active.
OBTV Exporter Service
OBTV HL7 Service
OBTV Link Service
OBTV Storage Service
OBTV DOX Manager Service
8.1.6.4 Special IntelliSpace Perinatal services

The behavior of those services differs from the general behavior as described.
OBTV Server Service

If the OBTV Server Service crashes or hangs, the general behavior applies.
If the OBTV Server Service cannot be successfully restarted after a crash or is stopped, the entire system
shuts down after a waiting period of 10 minutes. As a result, all IntelliSpace Perinatal applications shut
down and all active IntelliSpace Perinatal services become inactive and wait for re-activation. In this
case an operator has to restart the OBTV Server Service manually. During the waiting period, starting
IntelliSpace Perinatal applications or IntelliSpace Perinatal services wait until the OBTV Server Service
has been started again.
If the OBTV Server Service is started again within the waiting period, no system message is issued. If it
is restarted after the system was shut down automatically, all inactive IntelliSpace Perinatal services will
get active again, and waiting IntelliSpace Perinatal applications will startup. Already shut down
IntelliSpace Perinatal applications have to be started manually.
OBTV NetMsgService
This service is not visible in the System Console.
If the OBTV NetMsgService crashes, is stopped or a hang situation is detected after a timeout of 2
minutes, the entire system restarts. All IntelliSpace Perinatal applications are restarted into wait mode,
all active IntelliSpace Perinatal services become inactive and wait for activation.
In case of a crash or hang, the service is restarted automatically by the Windows operating system. In
case it is stopped manually, it needs to be restarted manually.
If the OBTV NetMsgService is restarted, all inactive IntelliSpace Perinatal services will become active
again, and all waiting IntelliSpace Perinatal applications will startup automatically.
In case of restarting after a crash or hang situation, the Local Data Recovery Tool including Archive
Recovery runs automatically and needs to finish successfully before all IntelliSpace Perinatal services
and IntelliSpace Perinatal applications can become active again.
If one of the recoveries fails, the system does not start automatically. In this case the log file of the Local
Data Recovery Tool has to be consulted and the issue has to be solved. It might be necessary that an
operator manually forces a system startup using the IntelliSpace Perinatal System Console after
troubleshooting and repair.

OBTV SQL Anywhere Service

This service is not visible in the System Console.
The OBTV SQL Anywhere Service on the Internal Server is configured to be started manually. It is
started, monitored and recovered by the OBTV NetMsgService.
If the OBTV SQL Anywhere Service crashes, is stopped or hangs, all IntelliSpace Perinatal applications
and IntelliSpace Perinatal services get blocked or are trying to re-connect. This may lead to detection of
a hang situation (behavior as described above). In all cases, the OBTV SQL Anywhere Service is
restarted by the OBTV NetMsgService automatically. Then, all the already inactive IntelliSpace
Perinatal services will become active again, and all waiting IntelliSpace Perinatal applications will start
up automatically.
9
9Maintenance
9.1 Introduction
Physical care and cleaning requirements are described in the IntelliSpace Perinatal Instructions for Use.
This chapter describes the periodic care, maintenance and backup of mass-storage devices.
9.2 Recommended Maintenance

Some of the following tasks can be performed by the customer. Encourage them to do so.
Recommended Maintenance Schedule:
Task Shutdown Frequency Time (minutes)

System Reboot System Each month
Check RAID disks - Each week
Defect disk blinks; there is no acoustic alarm
on failure.
Check the internal database System Every 3 months Depends on the
Run the Local Data Recovery Tool. size of the database
and the number of
open episodes.
Check Error Log files - Each month 10
Check battery condition for RAID Battery- - Every 3 months
Backed Write Cache (BBWC), if present
Check according to manufacturer's
recommendations or if performance is
degraded.
Rebuild external database DB Rebuild Every 6 months or Depends on the

Run the DB Rebuild Tool Tool stops when report printing size of the external
and re-starts performance is poor database
local services
automatically
9 Maintenance IntelliSpace Perinatal Backup
9.3 IntelliSpace Perinatal Backup

Please refer to the IntelliSpace Perinatal Site Preparation and IT Specification Guide for the process
requirements.
Please refer to Backup Tool on page 178 for details about the IntelliSpace Perinatal Backup Tool.
9.4 Rebooting the Remote Desktop Session Host

Server
To reboot the Remote Desktop Session Host server without rebooting the whole IntelliSpace Perinatal
system follow the steps below:
1 At the Remote Desktop Session Host server, start the Task Manager.
2 Select all running sessions in the Users tab.
3 Right-click the selected sessions and select Send Message to send a free text notification to all
selected sessions.
4 Right-click the selected sessions and selectDisconnect.
5 Reboot the Remote Desktop Session Host server.
9.5 Virus Protection

See the IntelliSpace Perinatal Site Preparation and IT Specification Guide for virus protection
information.
9.6 External Database Performance

NOTE This applies only to systems with an external database
To maintain or optimize the performance of the external database server the size of the external
database must be kept under control. If the database becomes too large and the database server
therefore becomes too slow, episodes must be removed.
External Database Performance 9 Maintenance
9.6.1 Manual Purge

Use the External Database Administration Tool to purge patient data.
9.6.2 Automatic Purge

OB TraceVue D.01.00 and later supports automatic purge of closed episodes from the external
database.
You may specify a time after which closed episodes are automatically removed from the external
database in the System Manager’s Configuration screen, External DB tab at the Internal Server machine.
The default purge time is 2 years.
See also the External Database Guide.
CAUTION When upgrading from OB TraceVue D.00.02 or earlier: After you have upgraded the Internal Server
machine make sure to set the purge time to the required value before starting the external database
server.
Once you have upgraded and started IntelliSpace Perinatal at the external database server, closed
episodes will be removed from the external database if they are older than the specified “purge time”.
9 Maintenance External Database Performance
10
10System Support
10.1 Log Files

The following table lists all IntelliSpace Perinatal log files.
You can use GetLog to archive all log files in a single file. See GetLog on page 196.
IntelliSpace Perinatal Log Files:
Log Location Size Comment

Computer On Internal Server computer:  6MB Successes, warnings and
Log Applications: C:\tv2\logdata\<hostname>.log per file errors during execution of
Services:
C:\tv2\logdata\<hostname>_<servicename>.log
Startup Log On local computer:  6MB Check if IntelliSpace
Applications:  Typical: Perinatal does not start.
C:\tv2\logdata\<hostname>.log < 100kB
C:\tv2\logdata\AppWatch.log
Services:
On Remote Desktop Session Host server:  6MB
C:\tv2\logdata\<hostname>.log per file
C:\tv2\logdata\<hostname>_AppWatch.log Typical:
(for each RD client) < 100kB
Services:
HL7 Log Internal Server:  6MB Successes, warnings and
C:\tv2\logdata\<hl7server>.hl7 errors of the HL7 module.
Setup Error All computers: Typical: Errors that occurred in

Log C:\traceset.txt < 100kB execution of IntelliSpace
Perinatal Setup.
Only available if Setup failed.
Moved to
C:\tv2\logdata\traceset_<Date
Time>.txt after successful
Setup.
Overwritten at each start of
IntelliSpace Perinatal Setup.
10 System Support Log Files
IntelliSpace Perinatal Log Files:

Configuration Internal Server:  6MB Successes, warnings and
Backup Log C:\tv2\logdata\CfgBkup.log errors of the offline
Configuration Backup tool.
Local Internal Server:  6MB Activity log of the recovery
Recovery Log C:\tv2\logdata\RecoveryTool.log tool.
Retrieve from Internal Server: Typical: Activity log of the Retrieve

Archive Log C:\tv2\logdata\RFAWiz.txt < 5kB from Archive Tool.
added per
execution.
Link Recovery On computer running Link Recovery: Typical: All logs are overwritten at
Log  < 1MB each execution of Link
Recovery.
• ...\LinkRecover\ • Master activity log,
LinkRecover_Master.txt showing overall progress

of the recovery steps.
• ...\LinkRecover\PatStates.txt • A preview of all actions

 that will be executed on
the different systems.
• ...\LinkRecover\ • Agent activity log of steps
Agent_<systemname>.txt performed on each system.
• ...\LinkRecover\ • The list of SQL

Repair_<systemname>.sql commands executed on
each system.
• ...\LinkRecover\ • The list of results of the
RepairResult_<systemname>.txt SQL commands executed
on each system.
System Logs On Internal Server computer:  6MB
• C:\tv2\logdata\DocumentExport.log per file • Log of the Document
 Export (DOX) Manager
service.
• C:\tv2\logdata\NetMsgService.log • History of starting/
 stopping of all
 Applications and Services
(NetMsgService service)
• C:\tv2\logdata\SystemMessages.log • History of all System
 Messages sent (Blinking
steam engine).
• C:\tv2\logdata\TimeChange.log • History of all time
changes on the system.
• C:\tv2\logdata\DBWatch.log • History of database
starting/stopping.
Rebuild Log On local computer:  6MB Log of the DB Rebuild Tool.
C:\tv2\logdata\dbrebuild.log per file
TV Backup On local computer:  6MB Log of the TVBackup Tool.

Log C:\tv2\logdata\tvbackup.log per file
Office Office client(s): Typical: Word and Excel Templates

Templates C:\TV2\logdata\doctemplates.log  6MB
HP Service Pack for ProLiant 10 System Support
10.2 HP Service Pack for ProLiant

The ISP Small Architecture Server Drivers and Firmware medium includes the HP Service Pack for
ProLiant, drivers and firmware for Small Architecture rp5810 and DL360 G10 v1 for Server2012R2.
It can be ordered with part number 453564865991.
Installing the software from the ISP Small Architecture Server Drivers and Firmware medium onto the
specified server does not require an integration test. This software installation is required because it
includes the necessary operating system drivers.
Installation:
• On the ISP Small Architecture Server Drivers and Firmware medium, use HP Smart Update
Manager by starting \HP ProLiant\launch_hpsum.bat to upgrade BIOS / Firmware / Drivers of HP
ProLiant hardware.
10.2.1 HP Insight Diagnostics Online Edition for Windows

This tool is installed as part of the ProLiant Support Pack.
10.2.1.1 Configuration
To generate automatic reports, follow the instructions below:
1 Launch HP Insight Diagnostics Online Edition for Windows:
Start All Programs HP System Tools HP Insight Diagnostics Online Edition for
Windows.
2 Click Continue to this Website if a security certificate error has been displayed.
3 Login using any local Windows administrator account.
4 In the Survey tab, click on Schedule Survey Capture.
5 Set it to the desired interval, e.g. weekly, check all days and set the time to 23:55.
From now on, a report is generated automatically at the specified times. The output file is stored in
C:\hp\hpdiags and has the following format:
survey<YYYY>-<MM>-<DD>-<HH>-<mm>-<ss>.xml
You can view this file using any XML viewer. You can also load the file from the Management
Homepage in order to compare different logfiles to check for configuration changes.
Alternatively, the survey file can also be viewed in MS-Word. This requires that the XSL stylesheet be
loaded as well. The file Survey.xsl is located in the same directory as the survey file, itself.
10 System Support HP Service Pack for ProLiant
11
11Configuration Verification
Procedure
11.1 Customer Verification
The customer must verify that the system configuration is correct. To do this, you should make sure
that the customer signs a printout of the CONFIG.TXT file.
11.2 Configuration Verification

2 Go to System Manager’s Configuration.
3 In the Text Format box, enter C:\CONFIG.TXT as File Name.
4 Click Copy to copy the data to file.
5 Click Yes to confirm.
6 Print out the CONFIG.TXT file. The beginning of the file should look like in first the figure below.
7 The customer must sign the bottom of the file printout.
Config.txt File First Lines
Config.txt File Last Lines
11 Configuration Verification Procedure Configuration Verification
12
12Component Installation
(Upgrade/Repair)
12.1 Introduction
This chapter provides brief installation instructions for hardware components. These components are
supplied to upgrade or repair existing systems.
Any hardware settings or software procedures given are generic. Refer to the chapter in this guide that
describes the particular computer you are working on.
For details about installing components such as a hard drive or DVD-ROM drive, consult the User's
Guide that comes with the computer you are working on. This tells you how to safely remove and
replace items such as the computer’s cover, or power supply. Instructions given here are IntelliSpace
Perinatal specific requirements and are additional to instructions given in the computer’s User’s Guide.
Static electricity can damage electronic components. To prevent damage, observe standard handling
precautions. Refer to Electrostatic Handling Precautions on page 40.
When you have installed the hardware component you may have to install the driver software required
to allow the computer to communicate with that component.
12.2 Software Distribution

Driver software for IntelliSpace Perinatal components is distributed on the IntelliSpace Perinatal
distribution medium. For new components, driver software may be temporarily distributed via Philips
InCenter until the IntelliSpace Perinatal distribution medium is updated.
NOTE Do not install driver software from another source (such as a printer CD-ROM or the web) unless
specifically instructed to do so by, for example, a Field Change Order.
12 Component Installation (Upgrade/Repair) Computer System Board Replacement
12.3 Computer System Board Replacement

If you exchange the computer’s system board, you must flash the BIOS, if:
• The BIOS revision is less than the revision originally shipped with the IntelliSpace Perinatal
computer or
• If the original BIOS version shipped cannot be determined, and the current BIOS version on the
computer is less than the revision on the IntelliSpace Perinatal distribution medium for the specific
computer model.
NOTE After you have flashed the BIOS, follow the instructions in the IntelliSpace Perinatal Test and
Inspection Matrix.
Only use BIOS revisions on the IntelliSpace Perinatal Application distribution medium (do not
download BIOS revisions from the HP website).
Check that the BIOS settings are correct: Refer to the appropriate chapter in this guide for the
computer you are using.
12.4 Additional Memory

For instructions on the installation of additional memory refer to the User’s Guide for the computer on
which you are working.
12.5 Network Interface (LAN) Card

Fit the network interface card into the appropriate PC slot. The slot numbers are listed in the chapter
for the appropriate computer type. When replacing a LAN card, you do not have to re-install its driver.
Refer to 9: Install Operating System and Run System Check Tool on page 70.
12.6 DVD-ROM Drive

CAUTION When installing or replacing the DVD-ROM drive check drive letter assignment after you have
installed the new drive. Refer to 12: IntelliSpace Perinatal Setup on page 71.
The DVD-ROM drive fits on a mass-storage device shelf.

For general instructions on the installation of mass-storage devices refer to the User’s Guide for the
computer on which you are working. More detailed information is available in the computer’s Service
Manual.
Make sure that:
• The DVD-ROM drive is connected to the special DVD-ROM SATA cable.
• The jumper at the back of the DVD-ROM drive is set to Cable Select
Primary Hard Disk Drive 12 Component Installation (Upgrade/Repair)
12.7 Primary Hard Disk Drive

CAUTION When installing or replacing a hard disk check drive letter assignment after you have installed the new
disk. Refer to 12: IntelliSpace Perinatal Setup on page 71.
The primary hard disk drive fits on a mass-storage device shelf.

For general instructions on the installation of mass-storage devices refer to the User’s Guide for the
computer on which you are working. More detailed information is available in the computer’s Service
Manual.
When you have installed the hardware, start a new installation or recovery, as appropriate.
CAUTION All data on the hard disk will be lost.
12.8 BIOS / Firmware Update Verification

For this test, please refer to the IntelliSpace Perinatal Integration Guide.
12 Component Installation (Upgrade/Repair) BIOS / Firmware Update Verification
13
13Renaming a Computer
13.1 Changing a Server Name

1 Shutdown IntelliSpace Perinatal.
2 In the Windows operating system, change the name of the computer.
You can enter the computer’s complete serial number (FRXXXXXXXX) as the computer name.
3 Reboot the computer.
4 On the Server machine, run IntelliSpace Perinatal setup (see IntelliSpace Perinatal Setup on page
236) and accept using the new computer name.
5 Run IntelliSpace Perinatal setup on all client machines
a. Select Only change database settings or system settings.
b. Settings for this PC: Uncheck all check boxes in order to not change any settings.
c. Specify the new Server PC Name.
13.2 Changing a Client Name

NOTE If you have changed the server name you must complete all steps given above (including 5. Run
IntelliSpace Perinatal setup on all client machines) before you rename a client.
1 Shutdown the IntelliSpace Perinatal client.

2 In the Windows operating system, change the name of the computer.
You can enter the computer’s complete serial number (FRXXXXXXXX) as the computer name.
4 Run IntelliSpace Perinatal setup on the client and accept using the new computer name.
13.3 Replacement Client

Client machines may be interchanged to substitute temporarily for a defective computer. If you rename
a spare client machine, in order to use it as a substitute computer on the network, please see
Substituting a Computer on page 159.
13 Renaming a Computer Replacement Client
14
14Repairing/Replacing
Hardware and Media
14.1 Repair Strategy
This section describes the full unit exchange or board-assembly exchange strategy applied to
NOTE Support parts listed in this guide may only be purchased for Philips-supplied hardware. This hardware
must have been sold on a sales order fulfilled by the Philips factory/division.
14.1.1 Hardware Defects

Hardware defects can be dealt with in the following ways:
Repair methods and when to use them:
Repair Method When to use it
Component Exchange or For parts that are identified by exchange/replacement numbers

Replacement (such as power-supply, fan, connectors, cables).
Full Unit Exchange Exchange an entire unit if you cannot identify an exchange or
replacement part as the cause of the problem, and for compact
devices that should not be opened (such as isolation
transformer).
Other Loose connections, wiring problems, mechanical mounts,

installation problems.
Client computers can be interchanged to temporarily
substitute a defective computer.
A client machine can be upgraded to a server machine. This
requires installation of special server equipment (e.g.
additional memory). If patient data storage is required the
computer also requires an additional HDD.
14 Repairing/Replacing Hardware and Media Repair Strategy
Repair Method:
Equipment Repair Method
Peripheral Devices Component exchange/replacement as described in full unit ex-

change. Use part numbers printed on the component to help
identify parts listed in this guide. Note that the isolation trans-
former is only available as full unit exchange. You must not re-
place components or perform onsite repair.
PC Boards and In- Component exchange/replacement as described in Component
ternal Components Exchange or Replacement. Use part numbers printed on compo-
(soundcard, RS-232 nent.
card)
OEM Parts Replacement parts are available for individual components.
Fuses Provide replacement fuses locally. The isolation transformer is supplied

with extra fuses.
Batteries Replace these according to the part number printed on the batteries.
Cable and Connectors Replace these according to the part number printed on the cable or
connector.
14.1.1.1 Replaceable Parts of Server and Client Machines

• Power supply
• Motherboard and processor
You must exchange the complete board if any of the integrated connectors break.
• Memory
• Floppy disk drive
• Processor cooler
• HDD (Hard Disk Drive)
• Front panel
• Ribbon cable to floppy disk drive
• Ribbon cable to CD-ROM drive
• Power cables
• Battery
14.1.1.2 Additional Parts of Server Machines

• CD-ROM drive
• IDE/SATA drive (type depends on computer model).
Repair Strategy 14 Repairing/Replacing Hardware and Media
14.1.1.3 Optional Parts for Client and Server Machines

• RS-232 board (PCI)
• Speaker
• NIC
14.1.1.4 Replacing the Serial Port Server Power Supply

This procedure describes how to exchange the power supply of a MOXA serial port server.

Before you start:
• Turn off the power.
• Disconnect the power cable from the unit.
• Make sure the fuse is OK.
• Do not touch the components on the main board to avoid electrostatic discharge.
• Wear anti-static clothing and an electrostatic discharge wrist strap.

Replacing the power supply:
1 Remove the top cover.
• For unit without rack bracket: 
Remove 6 screws: 2 on the left side, 2 on the right side, and 2 on the back side.
• For unit with rack bracket:
Remove 14 screws: 2 on the left side, 2 on the right side, 2 on the back side, 
and 4 on both rack brackets.
14 Repairing/Replacing Hardware and Media Repair Strategy
2 Use a screwdriver to remove the screws in each corner of the power supply:
3 Pull out the AC input cable:
4 Pull out the DC output cable:
5 Take out the old power supply.

6 Align the new power supply and use a screwdriver to tighten the screws in the four corners of the
power supply.
Repair Strategy 14 Repairing/Replacing Hardware and Media
7 Connect the AC input cable.

8 Connect the DC output cable.
9 Close the top cover and tighten all screws (see point 1).
The power supply spare part is high-potential pre-tested under the following conditions: DC4242
Vrms, 10mA, for 1 minute.
For information about safety tests to perform after repair, see When to Perform Tests on page 34.
14.1.2 Substituting a Computer

When using a spare client (e.g. computer name SPARE) as a substitute for a defective client (e.g.
computer name ORIGINAL) you must ensure that the spare client has the same settings and alert
distribution as the original client. Simply renaming SPARE to ORIGINAL is not permitted.
1 Uninstall IntelliSpace Perinatal on the SPARE client.
2 Rename the spare computer to ORIGINAL and reboot.
3 Reinstall IntelliSpace Perinatal on the client. This ensures that the substitute client has the same
settings as the original client.
See Changing a Client Name on page 153 for details.
14.1.3 Software Media Defects

If an IntelliSpace Perinatal software media breaks, or cannot be read you must order a replacement
IntelliSpace Perinatal media kit. Also if the label gets lost or illegible an new medium has to be ordered.
14 Repairing/Replacing Hardware and Media Parts Stocking
14.2 Parts Stocking

• 12-digit part numbers (12NC) are Philips part numbers. Depending on the repair strategy they may
not be orderable (e.g. the 12NCs for complete computers/servers are typically not set up as orderable
parts).
• Mxxxx-xxxxx are old Philips part numbers (can be translated to 12-digit part numbers).
Internal Philips numbering (non-orderable; for reference only):
– HP = HP Spare Part number.
– EX = Exchange if appended as a suffix to HP Spare Part number.
14.2.1 Fetal Monitor Connections

Parts Stocking - Fetal Monitor Connections:
Description Part Number Remarks
Exchange New
Fetal Monitor Connection
See Available Serial Cables
14.2.2 Power Supply

Parts Stocking - Power Supply:
Exchange New
Power Supply
Isolation Transformer 110V n/a 453563279351 M1389-60001

Isolation Transformer 220V n/a 453563279361 M1389-60002
Power cable adapter n/a 453563199391 to connect power-plug to isolation transformer outlet
(PWR-CD-ADPTR 18-AWG 3-COND) 8120-5440
14.2.3 Cabling
Parts Stocking - Cabling:
Exchange New
Cabling (LAN, RS232)
UTP Patch Cable 3.6m (12ft) n/a 453563337411 M3199-60105, terminated

Cable RS232 3M 9F/9M n/a 453563278151 straight through - RS232 cable wall plate to
computer [9p male -9p female]
M1380-61616
Cable, USB 5m n/a 453564008021 USB cable for HP LaserJet P4015n
Parts Stocking 14 Repairing/Replacing Hardware and Media
14.2.4 Serial Port Servers

Parts Stocking - Serial Port Servers:
Exchange New
Serial Port Servers
Serial Port Server (Moxa) 6610 - 8 Port n/a 453564358121 Nport-6610-8 - 8-port Port Server
Serial Port Server (Moxa) 6610 - 16 Port n/a 453564358131 Nport-6610-16 - 16-port Port Server
Serial Port Server (Moxa) 5610 - 8 Port n/a 453564008531 Nport-5610-8 - 8-port Nport Server Pro
M1380-60112
Serial Port Server (Moxa) 5610 - 16 Port n/a 453564008541 Nport-5610-16 - 16-port Nport Server Pro
M1380-60113
ASSY-PWR Moxa 5610/6610 24W Power n/a 453564392391 Switch mode power supply for NPort 5610 and
Supply 6610 family
Adapter RJ45 male to RJ45 female (Cable) n/a 451261010041 M1380-60610
To be used with every fetal monitor connected to a
5610 family SPS. See below for corresponding FM
adapters.
Adapter DSub9Male/RJ45 Female n/a 451261010061 DB9 to RJ-45 adapter for M1350 and FM 20/30/
40/50
M1380-60612
Adapter Centronics 24P/RJ45 Female n/a 451261010071 Centronics to RJ-45 adapter for M1351/53A
M1380-60613
Adapter DSub9F/RJ45 Female n/a 451261010081 DB9 to RJ-45 adapter for FM-2
M1380-60624
14.2.5 HP rp5810 (453564552581)

Parts Stocking - HP rp5810 (453564552581):
Exchange New
HP rp5810 HP p/n: M7T47UC#ABA; Philips p/n: 453564552581
PCACY - ER:2917 PC Mouse USB n/a 453564581111 674316-001

OPTICAL
PCACY - ER:2917 PC Sys Board rp5810 n/a 453564581121 824651-001
PC- ER:2917 rp5810 4GB PC3-12800 n/a 453564581131 671613-001
PCACY - ER:2917 PC Internal Speaker n/a 453564581151 636925-001
PCACY - ER:2917 Intel i5 2.9G CPU n/a 453564581171 732505-001
PC CBL 19 SATA Cable 2 Straight Ends n/a 453564581181 638813-001
PC CBL 25 SATA Cable 1 Angled End n/a 453564581191 638814-001
PCCRD - ER:2917 PC Exp Card Riser n/a 453564581201 749249-001
24V
PCACY - ER:2917 Chassis Fan rp5810 n/a 453564581241 653024-001
PC CBL PWR Switch assy and Front I/O n/a 453564581251 766699-001
Cbl
PCACY - ER:2917 Power Supply rp5810 n/a 453564581261 659246-001
DRIVE HDD 500G 7.2K SATA-3 6Gb n/a 453564305331 636929-001
PCCRD - ER:2917 2nd DisplayPort  n/a 453564599221 749251-001
add-in
BAT 3V Lithium CR2032 n/a 453563464231 153099-001
14.2.6 HP Proliant DL180 G9 (453564552601)
Parts Stocking - HP ProLiant DL180 G9 (453564552601)
Exchange New
HP ProLiant DL180-G9 HP p/n: M5U84A; Philips p/n: 453564552601
SVR Pwr Supply Redundant HP n/a 453564566251 754376-001

SVR 4 GB UDIMMS n/a 453564566281 804842-001
SVR - ER:2990 HP 300GB SAS Drive n/a 453564574781 785410-001
12GB/s
SVR - ER:2990 HP 8GB PC4-2133 Mem n/a 453564574791 804843-001
PCACY DL180e Gen9 Spare Mbd n/a 453564578711 779094-001
PCACY - ER:2917 DL180Gen9 8SFF n/a 453564581061 782461-001
Hot Plug
PCACY - ER:2917 Hot Swap fan n/a 453564581071 779093-001
PCACY - ER:2917 DL180 Gen9 Intel n/a 453564581091 780762-001
Xeon
PCACY - ER:2917 DL180 Gen9 n/a 453564581101 779083-001
3PCIEX8
SVR - ER:2917 DL180 Gen9 Power n/a 453564586531 784636-001
Backplane
SVR - ER:2917 HP Smart Array P440/4G n/a 453564591381 749797-001
BAT 3V Lithium CR2032 n/a 453563464231 153099-001
ER:2917 HP Smart Storage Battery for n/a 453564620141 815983-001
SUPPORT
SVR ER:2917 SMART ARRAY CABLE n/a 453564620151 -
KIT for SUPPORT
14.2.7 HP Proliant DL180 G9 (453564672431)
Description Part Number
Exchange New
HP ProLiant DL180-G9 Philips p/n: 453564672431
PCACY DL180e Gen9 Spare Mbd n/a 453564647561

HP 900W 240DC Power Supply n/a 453564647571
8 SFF Hot Plug Cable Kit n/a 453564581061
Hot Swap Fan n/a 453564581071
Intel Xeon E5-2630v4 10 Core CPU Kit n/a 453564674541
300 GB 12G SAS 10K rpm SFF (2.5-inch) HDD n/a 453564574781
PCI-E X8 Riser Kit n/a 453564581101
8 GB (1 x 8 GB) Single Rank x4 DDR4-2133 Memory Kit n/a 453564574791
Power Backplane n/a 453564674551
H240 Smart Host Bus Adapter n/a 453564586541
System Battery (CR2032 Lithium Cell) n/a 453563464231
HP Smart Array P440/2G Controller n/a 453564647591
96W Smart Storage Battery n/a 453564720471
14.2.8 HP Proliant DL360 G10 (453564764651)
Exchange New
HPE ProLiant DL360 Gen10 HPE p/n: Q9F11A Philips p/n: 453564764651
BAT 3V Lithium CR2032 n/a 453563464231

SVR - Heatsink 1U Standard n/a 453564772431
BAT - BATT PACK MC 96W V3 n/a 453564772451
SVR - PCA Riser x16 x8 GPU PRi 1U n/a 453564772511
SVR - PCA SYS I/O W/SUBPAN n/a 453564772521
SVR - PCA TPM Gen10 TAA n/a 453564772541
SVR - PCA, AROC P408i-a SR Gen10 Cntrlr n/a 453564772551
SVR - CBL 2SFF/8SFF cables kit n/a 453564772561
SVR - PS, 1U 12V 500W HTPLG HE-P n/a 453564772571
SVR - CPU SKL Xeon-S 4114 2.2G 10c 85W n/a 453564772591
SVR - DIMM 16GB PC4-2666V-R 2Gx4 n/a 453564772601
SVR - DRV SSD 480GB - Micron n/a 453564772611
SVR - DRV SSD 480GB - Intel n/a 453564772621
SVR - FAN Mod STD n/a 453564772651
DL360 Gen10 PCA SYS I/O W/SUBPAN Custom n/a 453564786831
14.2.9 HP Proliant DL360 G10 V2 (453564913991, 453564914891)
Parts Stocking - HP ProLiant DL360 G10 V2 (453564913991, 453564914891)
Exchange New
HPE ProLiant DL360 Gen10 V2 HPE p/n: R4X05A (with TPM module), R5X54A (without TPM module)
Philips p/n: 453564913991 (with TPM module), 453564914891 (without TPM module)
BAT 3V Lithium CR2032 n/a 453563464231

SVR - PCA Riser x16 x8 GPU PRi 1U n/a 453564772511
SVR - PCA TPM Gen10 TAA n/a 453564772541
SVR - PCA, AROC P408i-a SR Gen10 Cntrlr n/a 453564772551
SVR - CBL 2SFF/8SFF cables kit n/a 453564772561
SVR - PS, 1U 12V 500W HTPLG HE-P n/a 453564772571
SVR - FAN Mod STD n/a 453564772651
SVR - 480GB SATA Solid State Drive n/a 453564948241
SVR - Gen10 v2 System Board n/a 453564933371
Gen10 v2 Custom System Board w/ TPM n/a 453564933381
SVR - Intel Xeon-Silver 4210R v4 CPU n/a 453564945731
SVR - DIMM 16GB Memory Kit (DDR4-2933) n/a 453564945741
14.2.10 PC Common Parts

Parts Stocking - PC Common Parts:
Exchange New
PC Common Parts
KBD TRADITIONAL CHINESE n/a 453564874171

KBD PORTUGUESE n/a 453564874291
KBD US ENGLISH n/a 453564874301
KBD FRENCH CANADA n/a 453564874311
KBD GERMAN n/a 453564874321
KBD SPANISH n/a 453564874331
KBD FRENCH n/a 453564874341
KBD DUTCH n/a 453564874351
KBD JAPANESE n/a 453564874361
USB keyboards
KBD SPANISH LATIN AMERICA n/a 453564874371
KBD NORWEGIAN n/a 453564874161
KBD SWISS GERMAN n/a 453564874181
KBD SWEDISH n/a 453564874191
KBD UK ENGLISH n/a 453564874201
KBD DUTCH/FLEMISH n/a 453564874211
KBD DANISH n/a 453564874221
KBD ITALIAN n/a 453564874231
KBD SIMPLIFIED CHINESE n/a 453564874241
KBD KOREAN n/a 453564874261
KBD HUNGARIAN n/a 453564874271
14.2.11 Software Media and Documentation

Parts Stocking - Software Media and Documentation:
Exchange New
IntelliSpace Perinatal Software Media and Documentation 

(no licenses - for replacement of lost, damaged or defective media only)
Aftermarket documentation is available through Globalware Solutions.
ISP Rev. K.00.20 Installation SW Kit USB n/a 453564954911 Includes IntelliSpace Perinatal Rev. K.00.20 software
and multi language documentation
ISP Rev. K.00.20 Demo SW Kit USB n/a 453564954921 Includes IntelliSpace Perinatal Rev. K.00.20 
Demo software
ISP Rev. K.00.20 High End OS  n/a 453564954931 Recovery media for DL360 G10 v2 only 
Restore Kit (Windows Server 2019, drivers and firmware
included)
ISP Rev. K.00.12 Small Architecture n/a 453564865991 Includes IntelliSpace Perinatal Rev. K.00.12 Drivers
Drivers and Firmware and Firmware for Small Architecture rp5810 and
DL360 G10 v1 for Server 2012R2. 
Compatible with K.00.20
ISP Rev. K.00.10 Small Architecture n/a 453564676611 Recovery media for Small Architecture Standard
Standard OS Restore Kit (rp5810, Windows Server 2012 R2) 
ISP Rev. K.00.11 Small Architecture  n/a 453564793721 Recovery media for Small Architecture High-End
High End OS Restore Kit (Windows Server 2012 R2, DL360 G10 v1 and v2)
15
15Tools
15.1 Overview
NOTE Do NOT use the diagnostic tools when IntelliSpace Perinatal is running, unless it is explicitly stated
that you do so.
15.1.1 Standard Windows Tools

NOTE Most Windows tools require Windows administrator rights. Use the Windows Search function to
access the tools.
Standard Windows Tools:
Tool When to Use

Computer Management
Control Panel
Administrative Tools
System Properties To change environment settings.
Network  Configure network settings, add or remove
Connections protocols.
Virtual Memory
Add Printer To add, remove, or modify printers.
Event Viewer Use to troubleshoot a problem for example, if you
have device problems.
Device Manager To view information about the current status of

Windows hardware devices and drivers.
Disk Management Use this when you have trouble accessing the hard
disk or to check if the hard disk volume has errors.
Services
Performance  To view application status, process resources and
Monitor system performance
Disk Defragmenter To increase hard disk performance.
Backup To create an emergency repair disk.
Command Prompt
Microsoft .NET Framework Configuration To view a list of assemblies in the assembly cache,
and to configure the .NET framework.
15 Tools Overview
15.1.2 Database Tools

NOTE To start Sybase Central you must log on as Windows administrator.
Database Tools:
Tool How to Start
Sybase Central OB TraceVue E.00.00 or later:

OB TraceVue Support or IntelliSpace Perinatal Support Sybase
Central (External Server machine only)
15.1.3 IntelliSpace Perinatal Tools

NOTE Some tools require Windows administrator rights. In addition some of the tools require an
IntelliSpace Perinatal user account with special access rights.
15.1.3.1 Program Group

Most tools are available in the IntelliSpace Perinatal support program group:
Start  Programs  IntelliSpace Perinatal Support
IntelliSpace Perinatal Tools:
Tool How to Start / Refer to When to Use

Administration IntelliSpace Perinatal Support   • After a training session, to delete
Tool Administration Tool “practice patients”.
(Patient Data Patient Data Administration Tool (Inter- • To delete data for patients which
Administration nal DB) on page 174. you do not expect to have any
Tool) Note: Data administration functionality more episodes at the hospital. For
has been moved to other parts of Intel- example: patient has moved away,
liSpace Perinatal. See Other Patient Data patient has died.
Administration Functionality on page
174
Configuration IntelliSpace Perinatal Support • Backup: After finishing a user
Backup Tool Configuration Backup configuration, so that you can
Configuration Backup (Internal Server recover in case the configuration
Only) on page 222 gets lost. Always do a backup after
a software upgrade or after
applying a service pack.
• Reload: Directly after IntelliSpace
Perinatal software is reinstalled.
Database Rebuild IntelliSpace Perinatal Support   To optimize the database data organiza-
Tool Database Rebuild Tool tion.
Database Rebuild Tool on page 176
External IntelliSpace Perinatal Support  Export To purge patient data from the external
Database Database Administration Tool database in order to reduce its size.
Administration See the External Database Guide.
Tool
Overview 15 Tools

Fetal Monitor IntelliSpace Perinatal Support  Spy When you first set up a system to check
Spy (FMSpy) Fetal Monitor Spy (FMSpy) on page 193 that you have the correct cabling and
connections to all fetal monitors.
This works for fetal monitors connect-
ed via RS232 (“Classic”) only, not for
LAN-based (“Network”) monitors.
GetLog IntelliSpace Perinatal Support  Get Log When the response center has requested
GetLog on page 196 all the system information available on
an IntelliSpace Perinatal system.
NetTest NetTest on page 197 Network analysis
Logfile Viewer for IntelliSpace Perinatal Support Logfile • When the system or computer
IntelliSpace Peri- Viewer hangs
natal Error Logs LogFile Viewer for Error Logs on page • After re-start for problem diagnosis
188 • If you have problems starting the
computer
• Whenever the system messages
indicate any error situation
• If the archive is not working
properly
Backup Tool IntelliSpace Perinatal Support  Backup • Regular backup
Tool
• Backup before repair
Backup Tool on page 178 • Backup before upgrade
Online, and offline, backup • Backup if exchanging hardware
• Backup TV2_Templates directory
• Restore
• Validation
Update Docu- On any computer with MS Office in- • To update document templates
ment Templates stalled, stop the local IntelliSpace Perina-
tal application and run
c:\tv2\prog\TemplUpdate.exe
SQL Editor for \\<Server>\OBTVTemplates\code\SQLed- • To edit Report fields and statistic
Office Templates it.xlsx queries
(on any computer with MS Office in-
stalled)
Link Recovery IntelliSpace Perinatal Support  Link Re- • To identify and repair inconsistent
Tool covery Tool patient records on linked
Link Recovery Tool on page 221 IntelliSpace Perinatal systems
Update Archive Run c:\tv2\prog\UpdateArchive.exe • As a preparation step when

Tool Database Anonymize Tool on page 175 planning a System Merge
• Before moving an archive as part of
a System Merge
15 Tools Overview

Active Directory Active Directory Test Tool on page 198 • To test an existing domain user
Test Tool integration
• To check if an upcoming
integration will work
NBS Check Tool Run c:\tv2\prog\NBSCheckTool.exe • When episodes have failed on
NBS Check Tool on page 185 retrieval.
Windows Tools 15 Tools
15.2 Windows Tools

15.2.1 Disk Defragmenter
Defragmentation increases hard disk performance and therefore reduces overall IntelliSpace Perinatal
response times.
Defragmentation can be performed after upgrade, re-installation or on a regular basis for system
maintenance.
NOTE Only defragment hard disks of IntelliSpace Perinatal Internal Server and External Server machines.
15.2.1.1 Process
1 Stop IntelliSpace Perinatal.
2 Log in as a Windows user having administrator rights.
3 Depending on which server you are defragmenting:
• On the External Server, stop the IntelliSpace Perinatal database server service using Sybase
Central on page 170.
• On the Internal Server, stop NetMsg Service (which stops the database service). IntelliSpace
Perinatal:
Select MyComputer  Manage  Services and Applications  Services  NetMsgService 
Stop.
4 Start the Disk Defragmenter on page 173.
5 Select the disk to be defragmented.
6 Click the Defragment button.
7 Defragmentation may take from minutes to hours depending on the amount of data, free space
and fragmentation rate of the hard disk.
8 After successful defragmentation reboot the computer.
15.3 IntelliSpace Perinatal Tools

This section details the diagnostic tools developed specially for use with IntelliSpace Perinatal.
15.3.1 External Database Administration Tool (External DB)

For details on how to use the External Database Administration Tool, refer to the IntelliSpace Perinatal
System Administration and Configuration Guide.
15 Tools IntelliSpace Perinatal Tools
15.3.2 Patient Data Administration Tool (Internal DB)
• If episodes have been closed or deleted prior to starting the tool, make sure that
– the archiving process has finished (archiving systems only)
– IntelliSpace Perinatal has cleaned up the patient record (may take up to 10 minutes)
• If you want to remove patient data: shutdown IntelliSpace Perinatal
15.3.2.2 Functionality
• Search for patient records:
The search criteria can be
• on one or more items of the patient identification or
• the state of the patient record (enabled / disabled)
• a time range of the last episode close
• Remove patient data:
When removing patient data from the internal database the data is no longer available via
IntelliSpace Perinatal, except via Retrieve from Archive (RFA Wizard). The following data items can
be removed:
• One or more patient pregnancy / newborn cases, including all the episode and child cases
belonging to that pregnancy.
• One or more patient cases, including all the pregnancy / newborn, episode and child cases
belonging to that patient(s).
15.3.2.3 Other Patient Data Administration Functionality
• Patient Administration
Patient data administration functionality that was available in the Patient Data Administration Tool
prior to version E.00.20 has been integrated into IntelliSpace Perinatal.
Use the Patient Administration feature to:
• Change the patient identifier
• Change HIS ownership
• Enable / disable records
a. Enter the Administrative operating mode of IntelliSpace Perinatal:
• Log on as a user who has the Administer patients right
• Click on the user profile
• Select Enter Administrative Mode
The administrative operating mode of IntelliSpace Perinatal is visualized by an icon.
b. Start the Patient Administration dialog:
• Go to Identify / Search Patient
• Select a patient (highlight the patient and click the Select Patient button)
IntelliSpace Perinatal Tools 15 Tools
• The administration dialog allows changes if the patient record token is on the local system.
• Lock/Unlock Patient Records

To lock and unlock patient records you can use:
• The Link Recovery Tool.
• The Token Overview dialog in the Identify/Search patient screen (Rolodex). This is described
in the System Administration and Configuration Guide.
15.3.3 Database Anonymize Tool

The Database Anonymize Tool allows to de-identify sensitive health-related data stored in the internal,
external, and data warehouse database.
After starting the tool, the user can select which database to de-identify (internal or external). After the
processing is done, the user can select a location where to store the de-identified database.
The tool overrides all personal data in the database with artificial values. Free text fields and other fields
which allow for free text entry are not de-identified.
It is recommended to have three times the size of the current database available as free disk space when
using the database anonymize tool.
15.3.4 Update Archive Tool
15.3.4.1 How the Tool Works

The tool automatically creates, and closes, episodes which IntelliSpace Perinatal requires for internal
administration purposes and then reports the system’s progress in archiving. The system must be
running when you use this tool. The system can be used while this tool is running. Performance of
some portions of IntelliSpace Perinatal may decrease, such as retrieval and reports printing.
15.3.4.2 Using Update Archive Tool

1 Start the IntelliSpace Perinatal system.
2 Run c:\tv2\prog\UpdateArchive.exe on any IntelliSpace Perinatal computer.
3 Update Archive must run at least until it has created all necessary episodes (if any). Archiving of the
created episodes is done by IntelliSpace Perinatal in the background. The Update Archive Tool
reports the progress in its status window:
Waiting for X closed episode(s) to be archived, (Y open), press 'Stop' to cancel wait.
Where:
X is the number of episodes that have been closed but not yet written to the archive. In a correctly
working system, this number will decrease to zero (0). In a live system it may increase temporarily
if users are closing episodes or when patient records are selected in the Review Episodes screen.
Y is the number of episodes that are opened at that time.
Update Archive Tool automatically terminates if both numbers are 0.
The Update Archive Tool has two modes:
1 Create administrative episodes to patients for the two purposes described below. To use this mode,
press Yes when the tool asks: Do you want to update the archive now? ... Use this mode in the cases
described below.
2 Only show the number of currently closed (not archived and currently open) episodes. Use this
mode if mode 1 was stopped after the creation of all episodes before these episodes were archived
successfully.
15.3.4.3 When to Use the Tool

The tool may be executed for two purposes only:
a. As a preparation step when planning to merge systems to eliminate potential differences
between the database and the archive. This is described in Update Archive on page 282. 
It is not necessary to close open episodes. If there are open episodes when you use the tool, the
tool will not terminate; it will report the number of open episodes. This is normal behavior. You
can safely stop the tool as soon as it enters the "Waiting for X closed episodes…." status. The
created admin episodes disable re-opening of closed pregnancies and closed newborn
documentations.
b. As the last step before terminating a system as part of a system merge to make sure all data from
the database is written to the archive. All data of a discontinued system must be archived first.
This includes potential differences between database and the archive and all episode data.
Therefore all open episodes must be closed. See Merging Systems on page 283.
NOTE When executed on a production system, the created admin episodes disable re-opening of closed
pregnancies and closed newborn documentations.
15.3.5 Database Rebuild Tool

The database rebuild tool is used to optimize the data organization of the internal and external database
and therefore increase database performance. It can also repair database discrepancies that are detected
by the Local Data Recovery Tool’s database validation.
After rebuilding the database, when the External Server restarts all open episodes are resynchronized to
the external database. This might delay document printing. The performance decrease may last for up
to several hours.
Before starting the tool:
• Backup the internal database (if running the tool on the Internal Server).
• Backup the external database (if running the tool on the External Server).
• Shutdown IntelliSpace Perinatal.
NOTE The amount of free space available on the hard disk must be at least the size of the internal / external
database.
The Database Rebuild Tool re-organizes the internal or external database by
• Creating a new empty database (tvtemp.db)
• Unloading the data from existing database
• Reloading the data into the new database
• Replacing the old database by the new database
15.3.5.3 Using the Tool

• To rebuild the internal database, start the Database Rebuild Tool at the Internal Server machine.
• To rebuild the external database, start the Database Rebuild Tool at the External Server machine.
NOTE A database rebuild can take up to hours depending on the amount of data to copy.
15.3.5.4 Final Steps

After the rebuild has finished:
• Start IntelliSpace Perinatal
• If no errors occur delete the old database files (tvold.db, tvold.log). The location of the files is given in
the log (dbrebuild.log).
15.3.6 Backup Tool

The Backup Tool comprises:
• an Online Backup tool
• an Offline Backup tool
The tool backs up a complete IntelliSpace Perinatal installation (including database, patient data files
and configuration data), or the contents of the TV2_Templates directory. It does not backup the
operating system, Microsoft Office or any other third party software. In order to backup all current
available system and patient data, it must be run on the Internal Server machine. To backup patient
data in the external database, it must be run on the External Server machine.
It is available on all IntelliSpace Perinatal computers (Internal Server, External Server, RDSH server
and all clients).
This tool can be used as an offline backup, in which case IntelliSpace Perinatal must be shutdown, or it
can be used online in parallel to IntelliSpace Perinatal. In this case, it creates an online snapshot backup
of the IntelliSpace Perinatal application directory at the computer on which it is running.
You can use the tool for:
• Regular online backup of IntelliSpace Perinatal system and all its data.
• Offline Backup in case of defect before any repair actions take place.
• Offline Backup before upgrading to newer software or if exchanging hardware.
• Offline Backup before 3rd party software integration.
• Backup of TV2_Templates folder before modifying MS Office templates.
• Restoration of a previously backed up TV2_Templates directory.
• Validation of the database of a previously generated backup.
15.3.6.1 General Information

The backup is stored in a single zip file or in a directory, the location of which you can specify. An
existing backup at this location is overwritten, after confirmation. Information about the backup
process is logged into a log window, which you may print out and/or store to a file.
The following data is stored:
• Internal Server
– Patient data files (notes, FM traces, audit trail, scanned (attached) documents)
– IntelliSpace Perinatal registry information
– IntelliSpace Perinatal internal database (including patient and configuration data)
– IntelliSpace Perinatal log files

• External Server
– External database
– IntelliSpace Perinatal log files
• All other computers
– IntelliSpace Perinatal log files
Store the backup file securely (for example, on a network drive or on a backup tape).
Please note that the Backup Tool will additionally copy its own log file to the backup location, and the
existing log file will be overwritten by the new one.
15.3.6.2 Offline Backup

The offline backup stops the database service, including the database file. It copies patient data files to
the backup location and writes any additional information that is required, such as registry data, to the
backup location.
No changes occur while the backup takes place; therefore the backup contains a real snapshot of the
IntelliSpace Perinatal installation.
Prerequisites for Offline Backup:
– IntelliSpace Perinatal must be shutdown
– You must log on to Windows as Windows administrator
Starting an Offline Backup:
The offline backup can be started at any computer.
– If the tool is not pre-installed on your system, you can run or copy it from the latest IntelliSpace
Perinatal distribution medium \IntelliSpace Perinatal\Tools\tvbackup.exe.
After a backup, you can restart IntelliSpace Perinatal without rebooting.
15.3.6.3 Online Backup

The online backup copies patient data files to the backup location, writes any additional information
that is required, such as registry data, to the backup location, and creates a backup of the database.
Optionally, it executes a full validation of the backed up database. Finally, it copies the database
backup to the online backup location and additionally copies any files newly generated since the first
copy of the files was made.
When running in online mode, you must ensure that only one instance of the backup tool is running.
To maintain the performance and responsiveness of the IntelliSpace Perinatal system you must omit
the database validation when creating an IntelliSpace Perinatal Backup.
Run the validation afterwards on a separate IntelliSpace Perinatal computer using the Backup Tool. To
do this, you must back up IntelliSpace Perinatal into a folder. It is not possible to validate a database
inside the zip backup. Full database validation is used.
Prerequisites for Online Backup:

– The backup location uses a directory path which is accessible using a drive letter or Universal
Naming Convention (UNC) path.
– The backup location must have enough free space so that the backup tool can write the necessary
data.
– One backup location folder per system is needed. It is not possible to share one location
(directory) among multiple (linked) IntelliSpace Perinatal systems.
– The local system needs enough free disk space (TEMP directory) to hold a database copy; this
copy is used to validate the database before storing to the backup location.
– The storage location needs to be secure from unauthorized access to ensure patient data
confidentiality.
– Make sure the backup time does not coincide with the generation of the system audit trail, which
is created every night around midnight and may take several minutes to complete.
– Internal server only: It is recommended to schedule the online backup so it does also not coincide
with the automatic DB backup, which occurs every 24 hours. It can be determined from the log
file of the Internal Server, when it occurs. Use the LogFile Viewer for Error Logs and search for:
"Database Backup was successful" and look for the most recent time stamp. The time when the
internal DB is backed up automatically can easily be set to a new time by manually triggering the
DB backup on the Internal Server from within IntelliSpace Perinatal (click the DB icon in the
System Configuration screen and select "Backup of Database"). This new time is stored in the DB
and thus preserved while IntelliSpace Perinatal is not running. If an automatic backup by
IntelliSpace Perinatal cannot be performed at the scheduled time due to IntelliSpace Perinatal
being down, then it occurs after the restart of the application.
15.3.6.4 Command Line Interface

Synopsis:
tvbackup /tv [ /validatedb ] /offline | /templ | /validatedb directory
Options:
/tv
Creates a backup of the IntelliSpace Perinatal installation, directory specifies the location where to
create the tvbackup directory. When the parameter /validatedb is additionally specified, the database of
the installation will be validated before it is stored in the backup location. It is recommended to
validate the database later using the /validatedb option when the validation was omitted at backup
time.
/offline
when running the backup tool with the command line, normally an online backup is created (this is to
avoid stopping database). Use this switch to enforce an offline backup. When this switch is omitted, an
online backup is performed.
/templ
Creates a backup of the \tv2_templates directory, directory specifies the location where to create the
templatebackup.zip file.
/validatedb
validates the database in the given backup directory, this can be an online or offline generated backup
directory.
Return Value:
The tools return 0 in case of successful backup/validate and 1 in case of failure, for more information
see log file tvbackup.log.
15.3.6.5 Integrating Online Backup into Task Scheduler

The backup script c:\tv2\prog\backup.cmd allows backing up the system into a well-defined folder
hierarchy while keeping a number of previous backups.
Define a task in the Windows Task Scheduler to call c:\tv2\prog\backup.cmd with the desired
parameters at desired intervals. Make sure that the Windows user running the backup task has access
rights to the destination location.
Do not modify c:\tv2\prog\backup.cmd. The changes would be overwritten during setup.
If customizations are required, copy the script to folder c:\tv2\customer and edit it there.
Never use this folder or any other folder in c:\tv2 as destination folder for backups.
Any files and folders in c:\tv2 can be deleted or overwritten by setup at any time, except files and
folders in c:\tv2\customer.
Using backup.cmd:
• backup backupfolder [KEEP_DAYS]
Backs up the system into the following folders:
– Internal\tvbkp_yyyy-mm-dd\HHMM
when executed on Internal Server.
– Templates\tvbkp_yyyy-mm-dd\HHMM 
when executed on Internal Server with existing document templates folder.
– External\tvbkp_yyyy-mm-dd\HHMM
when executed on External Server.
– Datawarehouse\tvbkp_yyyy-mm-dd\HHMM
when executed on Data Warehouse Server.
– Client-<hostname>\tvbkp_yyyy-mm-dd\HHMM
when executed on a client. <hostname> is the value of the COMPUTERNAME environment
variable.
tvbkp_yyyy-mm-dd is a folder named according to the day of backup execution.
HHMM is a subfolder of tvbkp_yyyy-mm-dd named according to the time of backup execution.
Multiple backups per day are stored in the same day-of-backup folder.
– Backupfolder
Destination base folder name for the backups. 
IMPORTANT: Each system must have its own base folder!
Avoid spaces in the file name or surround the path with "". The folder must be accessible by the
user running backup.cmd
– KEEP_DAYS
Number of days backups will be kept. If omitted, the default is 7 days.
After a successful backup, only this number of most recent tvbkp_* folders are retained, the older
ones are deleted.
• Status files
Status files are created both in the main folder (Internal, ...) and as a copy in the backup destination
folder. The files in the main folder show the most recent status.
– backup.running: backup has started but has not yet terminated regularly.
– backup.success: backup has finished successfully.
– backup.failed: backup has finished with error.
• Exit codes (ERRORLEVEL)

– 0: success.
If Templates and Internal were backed up: Both backups succeeded.
– 1: tvbackup failed. 
If Templates and Internal were backed up: At least one tvbackup failed.
– 2: script failed.
An error occurred. For example: invalid parameters, not existing folders, access denied.
• Examples
– backup.cmd \\backupserver\ISP\System1\backup 5
When executed on the Internal Server at 3-Feb-2015 4:10 pm, the internal database backup is
stored in \\backupserver\ISP\System1\backup\Internal\tvbkp_2015-02-03\1610
If backup succeeds, all folders tvbkp_* - except the most recent five are deleted.
Additionally, if a document template folder exists, the template backup is stored to
\\backupserver\ISP\System1\backup\Templates\tvbkp_2015-02-03\1610
If backup succeeds, all folders tvbkp_* - except the most recent five are deleted.
– backup \\backupserver\ISP\System1\backup 1
When executed on a client named OBTVDAC01 at 25-Aug-2014 4:10 pm, this backs up client
setup options that can be used to restore the client during re-installation.
The backup folder is:
\\backupserver\ISP\System1\backup\Client-OBTVDAC01\tvbkp_2014-08-25\1610
If backup succeeds, all backup folders except tvbkp_2014-08-25 are deleted.
15.3.6.6 Restore an IntelliSpace Perinatal/OB TraceVue Installation
CAUTION
Do not restore a backup of an older IntelliSpace Perinatal/OB TraceVue software revision if
any episodes were archived after the backup with a newer IntelliSpace Perinatal/OB
TraceVue software.
Example: An F.00.13 system was backed up. The system was upgraded to G.00.10 and some new
episodes were archived under G.00.10. The system is - for whatever reason - then downgraded
back to F.00.13 by recovering the old backup in a F.00.13 setup. The F.00.13 Local Data Recovery
Tool will however detect the G.00.10 episodes but cannot handle them.
CAUTION If a restore of an IntelliSpace Perinatal backup is performed to create a copy of an original

IntelliSpace Perinatal system, then it is vital to specify a new NBS location for the copied system.
Failure to do so will result in unrecoverable archive data alteration/loss on the NBS location.
Considerations:
Consider clearing the following setup/configuration data when creating a system copy in the same
network:
Consideration Resolution
(if consideration conflicts with production system)
The system copy may connect the fetal  Remove the LAN based fetal monitor connec-
monitors from the production system. tions from fetal monitor network configuration.
IntelliSpace Perinatal Link is set up and  Clear the IntelliSpace Perinatal Link configura-
configured. tion to other production systems.
Other Systems may receive unintended link  Change the system name of the copy.
patients from the system copy.
HIS systems potentially receive a mix of outgo- To avoid unwanted patients in the HIS buffer of
ing messages from production system and  the system copy, remove the HL7 routes from the
system copy. HL7 Links configuration to the production 
system.
DOX destination is configured; system sends Remove DOX Routes from system copy or
documents from system copy into receiving  change output folder on the system copy to a
system. non-production setup.
Make sure different names are used for clones. Change computer names.
If services for HL7, Link, Exporter and Storage Delete computers from IntelliSpace PC Configu-
are distributed among different computers, the ration that had the special roles (for instance In-
Internal Server copy alone may not be sufficient telliSpace Perinatal Link) and reinstall a
to reproduce the production system. computer with this role. Alternatively the system
options on the copy may be changed to remove
roles.
1 If you want to restore on a computer that contains an IntelliSpace Perinatal/OB TraceVue

installation you must uninstall that installation first. Run the IntelliSpace Perinatal Setup to
uninstall IntelliSpace Perinatal.
2 Run IntelliSpace Perinatal Setup using the following selections:
a. Restore a previously saved IntelliSpace Perinatal installation (from the Backup Tool on page
178.)
b. Specify the backup to restore IntelliSpace Perinatal from (path.)
c. Install IntelliSpace Perinatal software, select Install the IntelliSpace Perinatal Software, Keep
existing database and data files. Do not change any settings.
3 Apply existing IntelliSpace Perinatal/OB TraceVue Service Packs if available (and backup the
configuration afterwards).
4 Start IntelliSpace Perinatal:
a. First start the IntelliSpace Perinatal application on the Internal Server. During startup the Local
Data Recovery Tool runs automatically to finalize the restore or recovery.
• If the system is configured for archiving on the Internal Server, the Local Data Recovery Tool
also completes the internal database from the archive.
• If the system is configured for archiving on the archiving server, it is important to NOT start
patient documentation or start any further IntelliSpace Perinatal application of the system
before starting the IntelliSpace Perinatal application on the archiving server. During its
startup the Local Data Recovery Tool runs automatically again and completes the internal
database from the archive.
• Do not skip the Archive Recovery. The system downtime is kept at a minimum by restoring
the missing episodes only.
b. Then proceed to start the IntelliSpace Perinatal application on all other servers and clients of the
system and start patient documentation.
15.3.6.7 Restore a TV2_Templates Directory

You can restore a templates directory independently of whether c:\TV2_Templates exists. The restore
process asks you to confirm whether to overwrite the old templates.
The backup is stored in a zip file, the location of which you can specify. You may also select the drive to
which the restoration is made.
Run IntelliSpace Perinatal Setup, keeping the existing database and data files. Do no change any
settings.
15.3.7 NBS Check Tool

The Network Based Storage Check Tool allows for various checks on the storage location. The tool is
available on the computer where the storage functionality in an IntelliSpace Perinatal network is
installed (Archive Server).
The tool is run from C:\TV2\prog\NBSCheckTool.exe
In order to perform the checks, the tool/archive computer requires network access to the network
storage location. The Network Based Storage Check Tool can run in parallel to IntelliSpace Perinatal.
15.3.7.1 Limitations
• The tool checks the network storage location which is configured in the Internal database. As a
result, it is not possible to check different Network Storage locations from one Archive computer.
• If there is already a network connection to the storage location using other user credentials than
configured in IntelliSpace Perinatal, the tool cannot access the storage location because of a
limitation of Windows, which does not allow more than one network connection using different
user credentials.
15.3.7.2 Access Security

The tool requires IntelliSpace Perinatal System Manger permissions including the permission to read
patient data.
The tool shows a list of all directories which need to exist on the network storage location, and the
directories that reside in the storage location. This list is generated from the Archive Index stored in the
system’s internal database. This list contains the Label, the Directory name and whether the directory
exists or not (Available). Furthermore, it indicates if the directory is referenced in the database (Found
in DB) and the IntelliSpace Perinatal revision which generated the directory.
The current archive directory is marked. In this list it is possible to see whether a directory is missing
and must be restored from backup.
If the directory is a migrated disk, which is a backup from an original archive disk, then the entry is
marked as <Backup> (not shown in picture). A migrated backup disk can be incomplete depending on
the time when the backup was generated from the archive disk.
• Full Directory Check:

The directory check will be executed for the selected directories in the list and executes the following
tasks:
a. List all available files
b. Unpack all available package file to check whether the files are OK. The result of this check are
lists with good and bad files and lists with patient data of good and bad files.
c. Compare list of package files on network storage location against the list in the internal
database. This will result lists with missing files and their patient data and a list with files which
are not referenced in the database.
The list files will be stored in a sub directory so that they are available for later use.
• Fast Directory Check:
The fast directory check will only execute the check a.) and c.) of the full directory check.
• Check results:
The directory check generates all result in .TXT and .CSV files. These files have the same content.
The .TXT files also include a user legible header. The following result lists are generated by the
checks:
a. goodfile, goodpat: List of good files and list of patient names and ID fields in good files. Only
available after full directory check.
b. badfile, badpat: List of bad files and list of patient names and ID fields in bad files. Only
available after full directory check.
c. missingfile, missingpat: List of missing files and patient names and ID fields in missing files.
Restore the files from backup. Verify success by re-executing the NBS Check Tool.
d. filelist: List of all files
e. unreffile: List of files in archive directory which is not referenced by the database.
If this file contains entries of potentially real patients (i.e. not test patient records), contact your
nearest Philips Customer Care Solutions Center or Response Center.
f. patlist: Patient names and ID fields of all found files
All these list files are stored in the directory filelist that resides in each archive directory after a file
check.
• Show Check results:
This starts the internal Windows editor and brings up the lists generated by the directory check for
the directories selected in the list. The editor can be used to store the data in a defined location.
• Show all Check results:
This will combine all result files of the same type to one result file. In addition to the files, a file
summary.txt is generated with the list of directories including the time of the last directory check.
These result files will be stored in a user provided directory. Then the Windows editor will be started
to show these list files.
After a check of all directories in a storage location, the files contain the information about all
directories. It is the customer’s responsibility to prevent unauthorized access to these files and to
remove them from the computer once they are no longer used.
15.3.8 LogFile Viewer for Error Logs

The LogFile Viewer is an on-line support tool. Each IntelliSpace Perinatal computer automatically
produces a unique log file containing diagnostic error messages. The LogFile Viewer allows you to
review these log files. You can view log files for all computers from the server. You do not have to go to
a local client machine. Log file entries may be filtered. Files can be merged. A condensed log file set can
be generated with many log files in binary format.
The user interface is intuitive, and only Logfile-specific buttons and selections are described.
15.3.8.1 Files Read and Written by the LogFile Viewer

• IntelliSpace Perinatal log file (read only): The log file viewer reads the log files generated by
IntelliSpace Perinatal and shows the data in an easily readable format.
• HL7 (read only): Log files generated by the HL7 engine can be viewed.
• Evl - Event Files (read only): Evl - event log files generated by older versions of the IntelliSpace
Perinatal GetLog utility.
• Lfs - Log file set is a set of log files generated by or for the log file viewer. Each Lfs can contain one or
more log files. It can contain both IntelliSpace Perinatal log files, and Event log files generated in
binary format.
15.3.8.2 When to Use LogFile Viewer

See IntelliSpace Perinatal Tools on page 173.
15.3.8.3 Starting LogFile Viewer

Go to IntelliSpace Perinatal Support  Logfile Viewer
15.3.8.4 Tool bar Buttons
Generate a new Log File Set file.
Open a Log File Set file.
Save the currently opened files as a Log File Set file format.
In the main Logfile Viewer tool bar, use the filter dialog to filter entries from the
log file, and also to merge log files in a new window.
Find a word in all currently opened files.
Unload the current log file from the loaded file set.
Refresh the content from the source. This is effective for IntelliSpace Perinatal
logs, HL7 logs that were read directly from a file (not from an lfs file), and
Windows Event Logs.
Include/exclude Windows Event Log. The base name of the file is used as host
name. This merges Windows Event Logs (application and system). Typically used
when opening log files in c:\tv2\logdata
Shows all files loaded in the current compressed file.
15.3.8.5 Using the Filters

Filters allow you to search the log files. You can create a query, for example, to find all events that
occurred at a particular time within specified modules, grouped by the error level “Warning”.
When you have defined a filter, you can save it for future reuse.
Selections here determine what to include in the filter Choose which files to merge
Selections here determine what to exclude from the filter
Load a previously saved filter
Save the current filter settings as <filename>.lff
Controls Values
Include/Exclude Lines Tab Page
Error Levels Check the error level by which you want to group results
Modules Check the modules to include in the search
Details Value - Contents of string on which to filter
Error Code String value - error code in the entry
Date Time picker Specify the date and time range of the entries
Comment Enter a text comment to describe the filter, if required.
15.3.8.6 Understanding the LogFile Viewer Display
Time and date message was written to log file Event description
Error level of entry

Module to which message refers
15.3.8.7 Looking at Details

To view details for an individual entry of the log file, right-click the entry and select Details.
15.3.8.8 Exporting Currently Loaded Log Files

You can export currently loaded logfiles:
Select File  Save to export the currently loaded logfiles in a compressed binary format (.lfs)
15.3.8.9 Log File Path

The log files for all computers are stored at the server machine: C:\TV2\LOGDATA.
15.3.8.10 Available Log Files

You can view log files for each computer. Client log files are named according to the client names. All
log files are stored on the server.
15.3.9 Installation Record

Go to IntelliSpace Perinatal Support Installation Record
The installation log file is opened in Notepad as a .TXT file.
15.3.10 Fetal Monitor Spy (FMSpy)

FMSpy is a software diagnostic tool for fetal monitors, connected in the “Classic” (RS232) method,
that allows you to check:
• The physical connection between a fetal monitor and the computer to which it is connected.
• Data transfer between a fetal monitor and the computer to which it is connected.
You cannot use FMSpy to test data transfer over the IntelliSpace Perinatal network.
15.3.10.1 When to Use FMSpy

See Standard Windows Tools on page 169.
15.3.10.2 Starting FMSpy

There is no need to stop IntelliSpace Perinatal on the local computer, at the Internal Server or at any
other client. 
FMSpy running at the server cannot test data transfer from a fetal monitor connected to a client.
1 In the IntelliSpace Perinatal application (classic fetal monitor configuration) delete the bed - COM
port connection of the fetal monitor connection to test. If the bed port connection is not deleted,
the FMSpy tool will not be able to access the serial port.
2 At the computer where you wish to run FMSpy start IntelliSpace Perinatal Support Spy
15.3.10.3 Quitting FMSpy

To end the FMSpy tool, click the END SPY button. You can also exit by pressing Alt+E on the
keyboard. 
In the IntelliSpace Perinatal application (classic fetal monitor configuration) re-assign the bed to the
COM port.
15.3.10.4 Selecting the Port

Select the Port field. The system displays a list showing the available digital channels.
Select the port Digital COM 1 through Digital COM 20 directly using the Port dropdown box. If you need
to select a higher COM port then type #<number>#, for example #45# for COM 45.
15.3.10.5 Initializing the Port

When you select a port, FMSpy initializes that port and the monitor connected to that port. If the data
that FMSpy displays does not appear to be current it is probably showing old data contained in a
buffer. Reselect the port.
The field next to the Port field is color coded to show you at a glance the current status of the port.
Black Port does not physically exist. Perhaps there is no card for this port in the
computer, or it has been disabled during computer setup.
Red Port is in use, but not by this FMSpy.
Yellow FMSpy is trying to detect a fetal monitor at this port.
Green FMSpy has successfully established a connection to the fetal monitor.
15.3.10.6 Interpreting Data

FMSpy can obtain more data from a digital connection than it can from an analog connection. The
following describes all the information it is possible to obtain digitally.
15.3.10.7 Monitor Info Fields

After detecting a monitor, FMSpy displays information about the monitor itself in the Monitor Info
fields:
Field Monitor Data

Monitor ID Monitor type
Serial Number Monitor's serial number
Software Rev Revision number of the monitor software, if available
15.3.10.8 Received Data Heart Rate Fields

FMSpy reports the same type of information for HR1 (heart rate1), HR2 (heart rate 2, used for twins
monitoring) and MHR (maternal heart rate). This information is displayed in the Received Data
section beneath the headings HR1, HR2, and MHR.
1 Number of beats per minute.
NO_TRAN no transducer present

ext external monitoring
IUP internal monitoring
unknown method of monitoring is unknown
2 Signal quality. This can be:
Red Signal not valid

Yellow Signal quality good
Green Signal quality very good
3 Mode. This is the mode in which the transducer is being used. The possible values are:

US ultrasound
DECG direct ECG
MEGC maternal ECG
ext MECG external maternal ECG
Toco Maternal Pulse derived from Toco MP
Transducer
Unknown transducer mode unknown
Toco:
This indicates the way in which Toco is being monitored. The possible values for Toco are:

ext external monitoring
IUP internal monitoring
unknown method of monitoring is unknown
SpO2:
The data is valid only when the monitor is equipped to measure the oxygen saturation of the blood and
the check box below this field is green. A gray checkbox indicates that current data is not available (any
data is from an old measurement).
STAN®:
The T/QRS identification label validity of the STAN® T/QRS value (range = -0.30.. 090) is checked.
The BP identification label validity of the STAN® Biphasic Value (range = 0... 3) is checked.
Fetal Mov.:
If this Check Box is green, it indicates that fetal movement is detected.
15.3.10.9 Message Box

FMSpy displays all the messages received from the monitor, together with the time and date so that
you can verify the monitor’s operation. FMSpy appends messages to a file named SPY.LOG in the
current directory only if the Save active button is checked.
15.3.10.10 Recorder Status

Displays status information from the recorder.
15.3.10.11 Monitor Status

The status boxes display the monitor’s known condition. If the box contains a cross, the value is true.
For example, if the HR 1 Twin offset box contains a cross this indicates that the Twin Offset is
enabled.
15.3.10.12 Request and Send Buttons

Some monitors can receive messages sent by FMSpy and send back answers. A request message tries to
obtain a specified message from the monitor. A send message tries to send a message to the monitor.
The messages received from the monitor are displayed in the Message Box.
15.3.10.13 Request Buttons

Use these buttons to make the monitor display information in the Message Box. You can use this
information to diagnose problems.
Request Meaning
Timer Stat Not Used.
Record Stat Not Used.
Serial Stat Displays statistical data of bytes both transferred to, and received from, the
monitor.
Date-Time Displays the monitor’s internal date and time.
Monitor ID Refreshes the Monitor ID field, where possible. Not all monitors can send
this information to FMSpy.
15.3.10.14 Test Note Send Button

Use Send Note to print a user defined test message on the monitor’s own paper.
15.3.11 GetLog
GetLog must be started as administrative Windows user. Either log on as administrator or use
Windows command Run as...
GetLog compresses all available IntelliSpace Perinatal log files plus some additional system information
including event log data. The compressed data is stored in a single archive file. If running GetLog
directly, use \tv2\prog\GetLogUI.exe. The command line version \tv2\prog\GetLogCmd.exe is used
internally only.
15.3.11.1 When to use GetLog

See IntelliSpace Perinatal Tools on page 173.
15.3.11.2 Creating and Copying an Archive Log File

Run IntelliSpace Perinatal Support  Get Log.
GetLog compresses the log files into a single archive file named c:\temp\transfer\<hostname>_log.zip.
15.3.11.3 Decompressing an Archive Log File

Any standard ZIP utility can be used to extract files from <hostname>_log.zip.
15.3.12 NetTest
NetTest validates the network connection between the current computer and a computer provided as
command line parameter. NetTest may be executed on all IntelliSpace Perinatal computers, including
servers and clients. Normally, the computer passed as a parameter is the Internal Server machine,
because this is the most important connection. For clients doing Word printing, the test can also be
executed with the name of the External Server as parameter. NetTest and path ping are based on
ICMP. This protocol must be enabled in firewall and router settings.
NetTest consists of two parts:
• Connectivity test
The test creates a defined load between the two computers and reports the load that could actually
be transmitted, together with the minimum, average and maximum round trip time (RTT) and
packet losses.
This test does not cover the required bandwidth for IntelliSpace Perinatal computers. Standard
network analysis tools can be used to prove that the required bandwidth is available.
• Pathping test
The pathping test focusses on the physical network layout, reflecting network topology by listing all
network hops between the two computers plus RTT and packet loss. Packet loss is shown separately
for both directions.
As a network troubleshooting utility, pathping can, for example, show bottlenecks for bad round
trip times and can help identify the source of packet losses. It shows separate packet loss for the
routers at the hops and for the links between these hops.
See Windows Help for detailed information. Besides ICMP, there might be additional firewall
settings that prevent pathping from working. Check with local IT if pathping reports errors
15.3.12.1 Using NetTest

Use the command: nettest <hostname>
To generate a table formatted output, add 2>nul to the end of the command. For example, NetTest
HPSERV 2>nul.
15.3.12.2 Interpreting the Results

• Connectivity:
If the host was given as hostname, name resolution is included in the test. If the IP address was
given, only the network connectivity is tested.
• Bandwidth Test:
The first line shows the performance for less frequent and small packages. The last line shows the
performance for frequent and large packages.
Good networks don't show a significant increase of RTT for these bandwidths. See the network
specifications in the IntelliSpace Perinatal Site Preparation and IT Specification Guide for an
explanation of why there are no sharp limits.
The test is passed if:
• measured bandwidths do not differ significantly from the requested bandwidth. (first - last
line)
• round trip times match the specifications of the IntelliSpace Perinatal Site Preparation and IT
In general, good network application performance can be achieved if RTT is:
• < 2 msec for small packets (first line) (1 kBit/s)
and there is no packet loss for bandwidths <100 kBit/s.
15.3.13 Active Directory Test Tool

You can use this tool to:
• To test an existing domain user integration.
• To check if an upcoming integration will work.
Run it on a computer that is integrated into the hospital domain active directory. You can check
various user attributes to test the ability to query the active directory. The tool runs standalone; it does
not require an existing IntelliSpace Perinatal installation.
The Active Directory Test Tool requires the same .NET Framework version that IntelliSpace Perinatal
uses. For further information about .NET Framework usage refer to the IntelliSpace Perinatal Site
To run the tool: on the IntelliSpace Perinatal installation medium, click \IntelliSpace
Perinatal\Tools\ADTest.exe
16
16 Document Export (DOX)
16.1 Overview
The Document Export feature is intended to support integration with Document Management
Systems or a clinical data repository (CDR). It offers the automated generation of electronic
documents in various formats (e.g. .pdf, .xps).
Any type of document that can be printed manually using the IntelliSpace Perinatal printing module
can also be configured for automated generation.
The Document Export covers two main activities:
1 IntelliSpace Perinatal automatically generates electronic documents and stores the results in a
configurable target folder.
2 If configured, IntelliSpace Perinatal sends HL7 MDM-T01 messages to inform a remote system of
the document creation. For more detailed information about this feature please refer to the
IntelliSpace Perinatal System Administration Guide.
16.2 Document Export Computer

The interface must not be installed on computers performing data acquisition (except on High-End
Small Architecture Systems).
The interface can be installed on Internal Server machines without data acquisition and on Small
Architecture Systems, but then MS Office-based documents are not available.
Recommendations:
• Install the document export interface on a dedicated IntelliSpace Perinatal client machine that is not
used for daily operation.
• Do not install the feature on the External Server machine if MS Office-based document export is
required. For details see also .
16.3 Using MS Office for Document Export

Automatic generation of electronic documents may also include documents based on IntelliSpace
Perinatal office templates ("Documents", "Statistics"). For details see .
By using the Save as function, it is possible to save data to the file formats .pdf, .xps, .doc, .docx, .rtf,
.odt, .xls, .xlsx, .csv or .ods instead of sending them to a printer.
16 Document Export (DOX) Printer Drivers for Document Export
If necessary, the template backward compatibility to previous Office formats (like *.xls) can be checked
with the Microsoft Word/Excel Compatibility Checker: 
File -> Info -> Check for Issues -> Check Compatibility
16.3.1 Installing MS Office for Document Export

For the export of documents based on Microsoft Office templates you must install Microsoft Office on
the Document Export computer (including service packs and hotfixes). See the IntelliSpace Perinatal
Site Preparation and IT Specification Guide.
Document export uses the template files from the C:\Tv2_Templates\ ... \auto folder - see also Installing
Word and Excel Templates.
NOTE It is not recommended to install the document export feature on the External Server machine if office-
based document export is required.
If this can not be avoided make sure that the Windows server roles
– Remote Desktop Services
– Web Server (IIS)
are not installed on the External Server machine.
16.3.2 Word Options

The Background Printing Option in Word must be disabled.
Click the Office button, click the Word Options button, in the right pane select Advanced, uncheck
Print in background in the Print section.
16.3.3 Troubleshooting
If MS Office base document export does not work see the IntelliSpace Perinatal Site Preparation and IT
16.4 Printer Drivers for Document Export

NOTE Using printer drivers for document export is not recommended, unless other formats as the built-in
"Save as” types are required.
When using a driver for document export, make sure that:
• The driver supports printing to a file
• Any option that allows the display of generated documents automatically is disabled
• Any option that requires manual intervention is disabled
• The spooler settings are correct.
• The output is specified in the Document Export Map (see IntelliSpace Perinatal Document Export
Maps Settings)
Note that setting up printer drivers for Document Export is mandatory for all printer drivers used for
Document Export.
Printer Drivers for Document Export 16 Document Export (DOX)
16.4.1 Overview
Each printer driver user for document export must be configured properly. Failure to do so may result
in documents not being exported or slow down of the Document Export computer under high load
conditions.
1 Log on as Windows administrator
2 Configure Advanced Printer Properties and Printing Defaults and printing defaults
3 Log on as the dedicated Windows DOX user
4 Configure printing preferences
5 Make sure that a printer driver used for document export is not set as default printer.
16.4.2 Advanced Printer Properties and Printing Defaults

1 On the DOX computer, log on as Windows administrator
2 Select the printer device used for DOX
3 Change Printer Properties (do not use Printing Preferences)
4 Go to the Advanced tab
• Select Spool print documents so program finishes printing faster
• Select Start printing immediately
• Uncheck Hold mismatched documents
• Check Print spooled documents first
• Uncheck Keep printed documents
• Uncheck Enable advanced printing features
5 Click Printing Defaults... to configure printing defaults
16.4.3 Printing Preferences

The preferences must be specified for all Windows users running ISP on the DOX computer. 
The printing preferences must be identical to the printing defaults.
16.4.4 IntelliSpace Perinatal Document Export Map Settings

When using printer drivers, Document Export maps must contain a file name extension in the
"Output" section which is adequate for the selected driver.
• The extension must be in the format *.<ext>
• It must not contain a path
• When using Adobe PDF, select <Adobe PDF>
• If the extension is empty the documents are printed
16.4.5 Adobe PDF

Using Adobe PDF for document export is not recommended for new installations. It is also not
recommended for existing installations, unless there is no other option.
When using Adobe PDF, a dedicated Windows user is required for the DOX machine.
16 Document Export (DOX) Printer Drivers for Document Export
Manual printing using Adobe PDF is not possible on the DOX machine when using Adobe PDF for
DOX.
16.4.5.1 Adobe PDF Settings

• Adobe PDF Output Folder: 
Temp directory of the dedicated Windows user ..\IntelliSpace Prinatal\DOX. 
Example: C:\Users\DOX Admin\AppData\Local\Temp\IntelliSpace Perinatal\DOX
• Adobe PDF Page Size: A4 or Letter
• Uncheck View Adobe PDF results
• Check Rely on system fonts only; do not use document fonts
• Check Delete log files for successful jobs
Uncheck Ask to replace existing PDF file
17
17IntelliSpace Perinatal Repair

and Recovery
17.1 What To Do If...
CAUTION It is essential that the IntelliSpace Perinatal system time is always up to date. Specifically, great care
must be taken before (if possible) or during any type of recovery (e.g. RFA).
The following procedures are also applicable to virtual machines, which may be installed in a variety of
implementations, for example with the presence of a backup drive D:\.
However, installation of the operating system and handling of virtual hardware might differ from the
described procedures, which are written for physical hardware. In such cases, apply the procedures with
additional care.
This table tells you which procedures you may need to refer to if the IntelliSpace Perinatal system fails.
What to do if ...
Situation Refer to
hardware failed or Windows does not start at ...
• Server machine with RAID Recovery Process: Internal Server with RAID
Disk Array (including High-End Small
Architecture Systems) on page 206
• Server machine with archiving Recovery Process: Internal Server with Archiving
(no RAID / including Standard Small
Architecture Systems) and all Internal Servers
with a Backup Drive D: and/or E: and/or F: on
page 208
• Server machine without archiving Recovery Process: Internal Server without

Archiving on page 214
• External Database Server machine Recovery Process: External Database Server on

page 215
• Remote Desktop Session Host server Recovery Process: Remote Desktop Session Host
Server on page 216
17 IntelliSpace Perinatal Repair and Recovery What To Do If...
What to do if ...
Situation Refer to
• High End Data Acquisition Server Recovery Process: High End Data Acquisition
Server on page 214
• Client machine Recovery Process: Client on page 216
IntelliSpace Perinatal ...
• has had an uncontrolled shutdown Local Data Recovery Tool on page 218
• reports errors about incorrect patient data

• cannot be started
• cannot be started because of corrupt or IntelliSpace Perinatal Setup on page 236
missing installation files
the IntelliSpace Perinatal database ...
• is corrupt or not accessible Local Data Recovery Tool on page 218
systems with IntelliSpace Perinatal Link ...
• have been reinstalled from archive disks Link Recovery Tool on page 221
using RFA.
• have been merged using the RFA merge
feature
• report errors when patient records are to be
transferred between systems
information about archived patients is no longer available
• after new system installation (no database Retrieve from Archive (RFA Wizard) on page
backup available) 223
• after patient data was deleted using the

Administration Tool
the configuration of IntelliSpace Perinatal ...
• must be reloaded (for example, after Configuration Backup (Internal Server Only) on
software reinstallation with a new page 222
database)
• must be backed-up (for example, after
changing the configuration or after new
system setup, or after applying a service
pack).
Which Tool? 17 IntelliSpace Perinatal Repair and Recovery
17.2 Which Tool?

When to Use Which Tool:
Tool Page When to Use

Recovery Process After Hard- 206 • When a hard disk has crashed.
ware or System Software Failure
• When Windows does not start.
Local Data Recovery Tool 218 • If the database is corrupt, not accessible or errors about
incorrect patient data occur.
• If you replace the hard drive C or D, reinstall IntelliSpace
Perinatal system software, and want to recover the original
database.
• If the system has had an uncontrolled shutdown.
• If you have problems trying to start IntelliSpace Perinatal.
• After running CHKDSK.
• As part of regular system maintenance.
Link Recovery Tool 221 • To clean up inconsistencies (read/write permissions) of
patient records among systems connected with IntelliSpace
Perinatal Link:
• After complete reinstallation from archive disks (using
RFA) of a system with IntelliSpace Perinatal Link.
• After linked systems have been merged using the RFA
merge feature.
Configuration Backup (Internal 222 • Backup: After finishing a user configuration, so that you
Server Only) can recover in case the configuration gets lost. Always do a
backup after a software upgrade or after applying a service
pack.
• Reload: Directly after IntelliSpace Perinatal software is
reinstalled.
Retrieve from Archive (RFA 223 • When information about the archived patient is no longer
Wizard) available in IntelliSpace Perinatal. This could be after a
new system installation or hardware defect if no backup of
the database is available.
• When patient data was deleted using the IntelliSpace
Perinatal Administration Tool
• To merge data of different systems into one single
database.
HP Array Configuration Utility 231 • To review the state and configuration of RAID disks.
• When a failed RAID disk has to be replaced.
IntelliSpace Perinatal Setup 236 • When IntelliSpace Perinatal does not start up because of
corrupt/missing installation files.
17 IntelliSpace Perinatal Repair and Recovery Recovery Process After Hardware or System Software Failure
17.3 Recovery Process After Hardware or System

Software Failure
This section describes the process used to recover an IntelliSpace Perinatal system after a hardware
failure or corruption of the Windows operating system.
NOTE Using the CHKDSK utility to repair files after a system server crash could result in archiving of corrupt
files. Always run the Local Data Recovery Tool after running CHKDSK.
17.3.1 Recovery Process: Internal Server with RAID Disk Array

(including High-End Small Architecture Systems)
The IntelliSpace Perinatal server with RAID disk array has three hard disks per logical drive. Every
logical drive has a spare disk and the array is configured to RAID level 1.
CAUTION Before any operating system reinstallation is performed on an Internal Server with RAID, the customer
must be warned that data loss will occur. A decision must be made about the most appropriate way to
proceed.
If system uptime is the most important consideration, and a set of replacement RAID drives is not
immediately available, accept any open episode data loss. Service personnel can then attempt
reinstallation of the operating system on existing RAID drives to see if the server can be made
operational.
If potential data loss from open episodes is more critical than having a running system, service
personnel should remove existing RAID drives for data recovery (for example, performed by a third
party company). The server is left non-operational. Replacement RAID drives should be obtained as
soon as possible to get the system running again.
If a third party data recovery company is consulted by the customer, it is important that the operating
system is not reinstalled and the system used again with the existing RAID drives before this can occur.
This would have a significant negative impact on the chance of successfully recovering data. And, even
if data could be recovered from the former RAID drives, it might not be possible to reintegrate into the
system for later retrieval. Evaluation must be made on a case-by-case basis after factory analysis of
recovered data. Philips cannot guarantee that lost data is recoverable. The Response Centre can consult
with the factory regarding what data is most important for any data recovery attempt.
Recovery Process After Hardware or System Software Failure 17 IntelliSpace Perinatal Repair and Recovery
17.3.1.1 Single Hard Disk Failure

In case of a single hard disk failure, just replace the failed disk (indicated by a flashing red light). It is
not necessary to shutdown IntelliSpace Perinatal or to reboot the server.
CAUTION The configuration for the replacement disk is applied automatically for all HP Proliant servers.
CAUTION There is no default system alarm if disks fail. You need to check on a regular basis as preventive
maintenance or use HP / Compaq Insight Manager for alarm distribution. 
Refer to HP Service Pack for ProLiant on page 145.
17.3.1.2 Multiple Hard Disk Failure

In the improbable case that two or more hard disks failed at the same time and therefore the server
machine does not start any more, replace the defective hardware and refer to the procedure Two-Disk
System: Complete Server Reinstallation (Both Hard Disks Failed). If a multiple hard disk failure occurs
and a backup drive D: and/or F: is still available, refer to Recovery Process: Internal Server with
Archiving (no RAID / including Standard Small Architecture Systems) and all Internal Servers with a
Backup Drive D: and/or E: and/or F:
17.3.1.3 Other Hardware Failure (Spare Server Available)

If you have an identically configured spare server, you can use the spare hardware to restart the system
within several minutes:
1 Turn off the failed server and disconnect peripheral devices.
2 Connect the peripheral devices, network and power cables to the spare server.
3 Remove the hot swap disk drives from the failed server and install them carefully in the slots of the
spare server.
CAUTION Keep the drives in the same order. Do not mix the drives. Do not add any other disks.
1 Turn on the spare server and the external devices.

2 Run the Local Data Recovery Tool.
3 Check the system time of the computer.
4 Start IntelliSpace Perinatal on the new server and on the clients.
5 Make sure that the revision of the computer and the RAID BIOS are up to date. Update them if
necessary. 
17.3.1.4 Windows Does Not Start

To repair a corrupted Windows installation, try to use the "safe mode" for booting up the operating
system.
CAUTION In case of a corrupted Windows installation, you must NOT perform a new installation on drive C,
because this will erase all your data. Servers with RAID array do not have a backup disk D.
For the repair process you need a Windows installation medium.

To do the repair, follow these steps:
1 Press F8 while starting the computer, to enter the boot menu.
2 Select "Safe Mode with Networking" boot option.
3 Run the Backup Tool to save the existing IntelliSpace Perinatal installation and data files and
templates to a secure place, such as a network location.
4 Perform a new installation (as described in Windows Installation on page 255).
5 Re-install IntelliSpace Perinatal (as described in IntelliSpace Perinatal Setup on page 236).
6 Recover the templates using the Backup Tool.
7 Recover the backup using IntelliSpace Perinatal Setup.
17.3.2 Recovery Process: Internal Server with Archiving 

(no RAID / including Standard Small Architecture Systems) 
and all Internal Servers with a Backup Drive D: and/or E: and/or F:
17.3.2.1 Overview
The IntelliSpace Perinatal Server with archiving has between two and four hard disks:
• The C: drive represents the server’s first hard disk.
• The D: drive represents the server’s backup hard disk.
• The E: drive represents the server’s transaction log
• The F: drive represents the server’s database file.
The following description at first refers to two-disk systems. All kinds of possible hardware failures with
a Three-Disk System or a Four-Disk System can be recovered by falling back on the procedures
described here.
In case of a hard disk crash, check for each defective hard disk whether a backup disk is available. If yes,
apply the backup. If no, install a new disk, format and partition it.
After having installed each backup disk, look for the recovery scenario in the following descriptions.
Go through all steps as described.
17.3.2.2 Two-Disk System: Primary Hard Disk Failure
It is possible to recover the system from the backup disk.

1 Replace defective hardware
2 Remove the backup hard disk to prevent erasure of backup data.
It is essential to remove the backup drive (that is, to unplug the power and the data cable),
otherwise the recovery process will not succeed.
3 Install Windows as described in Windows Installation.
• Locate the file or printout of the installation record. This should have been saved after the
initial installation of the server. See Reviewing and Printing the Configuration Record. This
file specifies the computer name which is required when you reinstall the operating system.
4 Re-install all backup hard disks.
5 Install IntelliSpace Perinatal
In the following description, <D/E/F> stands for drive letter D, E, or F, whichever is the name of
the backup drive you want to recover.
a. Start Windows Explorer and check drive letters. See installation task 12: IntelliSpace Perinatal
Setup.
b. Rename the directory <D/E/F>:\TV2 to <D/E/F>:\<D/E/F>_TV2OLD (for example: D:\TV2 to
D:\D_TV2OLD). This is now your recovery source. If it is not possible to rename the directory,
reboot the computer.
c. Copy <D/E/F>:\<D/E/F>_TV2OLD to C:\<D/E/F>_TV2OLD. This is now your backup.
d. Install IntelliSpace Perinatal. Configure the system with the options and setting specified in the
installation record file or printout.
e. Reboot the computer, but do not activate the IntelliSpace Perinatal services.
f. Stop the NetMsgService: Computer  Manage  Configuration  Services  select OB
TraceVue NetMsgService  Stop.
g. Delete the directory <D/E/F>:\TV2. 
If it is not possible to delete the directory, reboot the computer and try again.
h. Rename the directory <D/E/F>:\<D/E/F>_TV2OLD to <D/E/F>:\TV2.
i. If no 4-disk-system: Delete the file C:\TV2\DB\TRACEVUE.DB (This is an empty database.)
j. Start the NetMsgService: Computer  Manage  Configuration  Services  select OB
TraceVue NetMsgService  Start.
k. Run the Local Data Recovery Tool.
l. Start the IntelliSpace Perinatal application and activate the services via the IntelliSpace Perinatal
System Console. The systems should now be working correctly, with all data visible.
m.Delete all directories named C:\<D/E/F>_TV2OLD.
17.3.2.3 Two-Disk System: Secondary Hard Disk Failure
1 Install, partition and format the new secondary hard disk.

2 Run the Local Data Recovery Tool.
3 Reboot the Server machine.
17.3.2.4 Two-Disk System: Complete Server Reinstallation (Both Hard Disks Failed)
In summary, to reinstall IntelliSpace Perinatal for the purpose of system recovery the following tasks
must be completed:
• Install the new hard disks.
• Install Windows.
• If an OBTV backup is available, restore IntelliSpace Perinatal from the OBTV backup, otherwise:
– reinstall IntelliSpace Perinatal with a new database
– reload the configuration backup
– reload the archived data.
1 Locate the file or printout of the installation record, which should have been saved after the initial
installation of the server (see Reviewing and Printing the Configuration Record on page 75). The
file specifies the computer name which is needed when you reinstall the operating system.
2 Install Windows as described in Windows Installation on page 255 using the computer name
specified in the installation record.
3 Deal appropriately with the backup situation.
• If an OBTV Backup of the Internal Server is available:
(This procedure recovers all data that is archived, even after OBTV backup, and all open
episode data at the time of the OBTV backup. All other data is lost.)
Use IntelliSpace Perinatal Setup to restore an IntelliSpace Perinatal installation from an OBTV
Backup, including the internal database and all files and settings. See Restore an IntelliSpace
Perinatal/OB TraceVue Installation on page 183. This process automatically completes the
internal database from the archive.
• If no backup is available:
This procedure recovers all data that is archived. All other data is lost when you follow this
procedure.
CAUTION You must follow the steps exactly in the order they are set out in these procedures. If you fail to do so,
archived data may be lost, and recovery may not be possible.
• At the Internal Server:

a. Install IntelliSpace Perinatal with a new database. Use the old installation record printout to
select exactly the same configuration as before. After Setup, verify the configuration by
comparing the new and the old installation record printout.
CAUTION Starting IntelliSpace Perinatal and assigning the NBS location at this stage will inhibit RFA and delete
the archive index on the NBS location.
b. Reboot, but do not activate the IntelliSpace Perinatal services.

c. Run the Configuration Backup tool to reload the most recent configuration back up. See
also Configuration Backup (Internal Server Only) on page 222.
• At the Archiving computer:
d. For security reasons, the password for connecting a network based storage share is not
backed up. If such a password is required, it must be re-entered manually after
configuration reload. Run setup on the Archiving computer. Provide the exact NBS
location and access credentials used before recovery.
e. Use RFA tool to recover patient data from archive by importing it. For details on how use
the RFA tool, please refer to Retrieve from Archive (RFA Wizard) on page 223.
4 Activate the IntelliSpace Perinatal services on the Internal Server and the Archiving computer.
In the Storage Service Tool (available on the Archiving computer only) click Assign Storage
Location to this system and confirm the action on the next screen.
Background Information:
The file ID.XML in the network storage location identifies the system that is allowed to write
archive data to the storage location. The internal ID of the system changes after the installation of
a new database. Consequently, the new system will not accept the network storage location of the
previous system for archiving. This is why the NBS location must be assigned explicitly. The
current index and ID.XML file are kept in a history folder and new ID.XML and index are
generated.
5 Start IntelliSpace Perinatal at each client. The client setup program runs automatically and reboots
the computer when finished.
17.3.2.5 Three-Disk System

The following table shows all possible combinations of possible hard disk failures in three-disk systems
and the way they can be handled by falling back on the recovery procedures of two-disk systems
described above.
Example:
In case 4, only the E: drive has failed. In this case, the E: drive is to be handled similarly to a D: drive
failing in a two-disk system. For recovery, follow the procedure described in Two-Disk System:
Secondary Hard Disk Failure on page 210.
17.3.2.6 Four-Disk System

The following table shows all possible combinations of possible hard disk failures in four-disk systems
and the way they can be handled by falling back on the recovery procedures of two-disk systems
described above.
Example:
In case 9, the C: and the F: drive have failed. This is to be handled in a similar way to a C: drive failing
in a two-disk system. For recovery, follow the procedure described in Two-Disk System: Primary Hard
Disk Failure on page 209.

Install Windows and IntelliSpace Perinatal according to the process described in Two-Disk System:
Primary Hard Disk Failure on page 209. Start with step 3 Install Windows as described in Windows
Installation.
17.3.3 Recovery Process: High End Data Acquisition Server
17.3.3.1 Complete High End Data Acquisition Server Reinstallation

file specifies the computer name which is needed when you reinstall Windows.
3 If applicable, install the serial port server device driver as described in Installing and Setting up a
Serial Port Server on page 92.
4 Install the IntelliSpace Perinatal software. Use the old installation record printout to select exactly
the same configuration as before. After Setup, verify the configuration by comparing the new and
the old installation record printout.
17.3.3.2 Windows does not Start

Repair of a corrupt Windows installation is not supported on the high end data acquisition server.
Reinstall the server, refer to Complete High End Data Acquisition Server Reinstallation.
17.3.4 Recovery Process: Internal Server without Archiving

CAUTION All data is erased when you use this procedure.
If a backup drive D: or F: is available, refer to Recovery Process: Internal Server with Archiving (no
RAID / including Standard Small Architecture Systems) and all Internal Servers with a Backup Drive
D: and/or E: and/or F:
If the server does not have a backup disk, you must replace the hard disk and then reinstall Windows
and IntelliSpace Perinatal.
17.3.4.1 Complete Server Reinstallation

3 Install IntelliSpace Perinatal. Use the old installation record printout to select exactly the same
configuration as before. After Setup, verify the configuration by comparing the new and the old
installation record printout.
4 Reboot, but do not activate the IntelliSpace Perinatal services.
5 Run the Configuration Backup tool to reload the most recent configuration back up. See also
Configuration Backup (Internal Server Only) on page 222.
6 Start the IntelliSpace Perinatal Server application and activate the services via the IntelliSpace
Perinatal System Console.
7 Start IntelliSpace Perinatal at each client. The client setup program runs automatically and reboots
the computer when finished.

Repair of a corrupt Windows installation is not supported on systems without archiving. Reinstall the
server, refer to Complete Server Reinstallation on page 214.
17.3.5 Recovery Process: External Database Server

CAUTION All data on the external database server is erased when you use this procedure. The database can be
restored from a customer’s backup and the IntelliSpace Perinatal archive.
17.3.5.1 Complete External Database Server Reinstallation

3 Deal appropriately with backups:
• If an external database backup (tape or equivalent file) is available:
a. Install the IntelliSpace Perinatal software on the external database server. Use the old
installation record printout to select exactly the same configuration as before. After Setup,
verify the configuration by comparing the new and the old installation record printout.
b. Restore the external database (see the External Database Guide).
• If an IntelliSpace Perinatal backup of the External Server is available, restore the IntelliSpace
Perinatal installation from an OBTV backup, including the external database and all settings.
See Restore an IntelliSpace Perinatal/OB TraceVue Installation on page 183.
• If no backup is available, install the IntelliSpace Perinatal software on the external database
server. Use the old installation record printout to select exactly the same configuration as
before. After Setup, verify the configuration by comparing the new and the old installation
record printout.
4 Use the RFA wizard to complete the content of the restored external database. This restores
episodes that were archived after the backup time of the restored external database (all episodes if
no backup is available at all). See Restoring the External Database on page 227.
During the first startup after recovery on the External Server, IntelliSpace Perinatal automatically
performs a resynchronization of all currently open episodes to the external database. See the
External Database Guide, Automatic Database Resynchronization.

Repair of a corrupt Windows installation is not supported on the external database server. Reinstall the
server, refer to Complete External Database Server Reinstallation on page 215.
17.3.6 Recovery Process: Remote Desktop Session Host Server
17.3.6.1 Complete Remote Desktop Session Host Server Reinstallation

3 Install the IntelliSpace Perinatal client software. Use the old installation record printout to select
exactly the same configuration as before. After Setup, verify the configuration by comparing the
new and the old installation record printout.

Repair of a corrupt Windows installation is not supported on the Remote Desktop Session Host server.
Reinstall the server, refer to Complete Remote Desktop Session Host Server Reinstallation on page
216.
17.3.7 Recovery Process: Client
17.3.7.1 Complete Client Reinstallation

installation of the system (see Reviewing and Printing the Configuration Record on page 75).
2 Install Windows as described in Windows Installation on page 255. When you are prompted for
the computer name, use the name given to the client during initial installation (see printout of
installation record).
3 Install the IntelliSpace Perinatal client software. Use the old installation record printout to select
exactly the same configuration as before. After Setup, verify the configuration by comparing the
new and the old installation record printout.

Repair of a corrupt Windows installation is not supported on a client machine. Reinstall the server,
refer to Complete Client Reinstallation on page 216.
17.3.8 All Scenarios: System Startup after Recovery Warning

If the system detects a potential data fallback caused by a system recovery (even unattended), a system
message is issued on all Apps and System Consoles (see the steam engine icon). This message appears
once after system startup if one of the following conditions applies:
• The system was restored from any external backup by using Setup.
• The system was recovered from the latest internal backup by using the Local Recovery Tool. This
might happen unattendedly if data corruption has been detected after a crash scenario.
• The last active time of the database was more than 5 hours ago. This might be caused by a downtime
of the system for maintenance or by other reasons like OS image restores, etc.
This message is intended to notify clinical users about the potential consequences of this situation.
The system message notifies the user about when the database was last active, and it prompts the user
to check if traces are assigned to the right patients and if configuration and patient data are correct.
17 IntelliSpace Perinatal Repair and Recovery Local Data Recovery Tool
17.4 Local Data Recovery Tool

This tool is available on the Internal Server machine and on computers that host the archive service.
The Local Data Recovery tool repairs and validates as much of the IntelliSpace Perinatal database as
possible from uncorrupted backup database and backup patient files.
The tool is launched automatically if the most recent system shutdown was not performed correctly -
for example, if the server crashed.
NOTE The length of time needed for data recovery depends on the size of the database and the number of
open episodes. It can take from minutes to hours.
17.4.1 Using the Local Data Recovery Tool
17.4.1.1 Running the Local Data Recovery Tool

Do not stop this tool while it is working. Some operations may take several minutes to several hours,
depending on the amount of data in the database.
1 Shutdown IntelliSpace Perinatal at the server
2 Go to Start  Programs IntelliSpace Perinatal Support, choose Local Recovery Tool.
3 In the TraceVue Local Data Recovery Tool window choose Start.
To minimize the risks of data loss, the tool is able to perform a full database validation if started from
the user interface. It asks whether to perform a full database validation, which is the default, or to
perform a quick database validation.
To minimize downtime on recovery or in a failover situation, where the tool is started automatically in
an unattended mode, it performs a quick database validation.
Follow the instructions on screen. You can click Show Log to see a more detailed progress status.
If your system is configured for network based storage, the tool finds the archive index without user
interaction. It is not necessary to insert the most recent archiving disk.
17.4.1.2 Logfile
The Local Data Recovery Tool creates a recovery log file (C:\TV2\logdata\RecoveryTool.log) that you
can open with the IntelliSpace Perinatal Log File browser.
17.4.2 Data Recovery Process

The Local Data Recovery tool first checks if the database file, the database backup file, the database
transaction log file and the database transaction log backup file are available.
If, for whatever reason, a file is not available, the tool repairs as much as possible from the remaining
files.
The tool then attempts to:
1 Recover the best possible database files.
2 Validate the database.
3 Validate patient files.
4 Recover additional files from the archive location.
Local Data Recovery Tool 17 IntelliSpace Perinatal Repair and Recovery
17.4.2.1 Database Recovery

• The tool tests whether the existing database and transaction log files can be used. If they can, the
files are assumed uncorrupted.
• If the transaction log is available, the tool reconstructs the database from the transaction log.
Although there is no loss of data, this “database rollforward” could take up to two hours.
• If the transaction log is not available, the tool tries to recover from the database. Approximately the
last five minutes of collected data may be lost.
• If only the database backup file is available, up to 24 hours data may be lost.
• If the database is accessible, and the database validation detects a discrepancy within the database,
the Database Rebuild tool might repair this discrepancy (on both standard and high-end servers).
After the Local Data Recovery Tool reports a database validation error, perform the following steps:
a. Reboot the system.
b. Run the Database Rebuild Tool on page 176.
c. Run the Local Data Recovery Tool again.
If the Local Recovery tool still reports an error, you must reinstall the system and use RFA to recover
the database.
Data Loss after Recovery:
Available Files
Transactio Database Backup Data Loss
n Log Database
   none
  none
 -  none
 - - open episodes
-   max. 5 minutes
-  max. 5 minutes
- -  max. 24 hours
- - - open episodes
17.4.2.2 Database Validation

The validation process tests the integrity of the database. Indexes, foreign key constraints and primary
keys are examined. The tool reports any errors found and is able to correct some errors automatically.
17.4.2.3 Patient File Recovery

This validation process examines each patient trace file held on the server. Any trace file found to be
corrupted is replaced by a copy of its (uncorrupted) backup.
When a trace file is replaced by its backup all associated files (for example the notes file) are also
replaced.
When a patient is discharged, associated files are deleted from the server. The patient file validation
process completes any failed patient file deletions so freeing-up wasted space on the hard disk(s).
17 IntelliSpace Perinatal Repair and Recovery Local Data Recovery Tool
17.4.2.4 Archive Recovery

This process recovers data from episodes that were closed after the last database backup, but are
available because they are stored in the archive. The tool finds the archive index without user
interaction, and recovers the patient data automatically from the archive location.
17.4.3 Automatic Recovery on Internal Server/Archive Server

When the system detects that the Local Recovery Tool has to run, e.g. in case of an incorrect Windows
shutdown, then the Local Recovery Tool will be started automatically by the OBTV Service on the
Internal Server and on the archive server when required.
If the system was not shut down in the System node of the System Console, the automatic start of the
Local Recovery Tool is performed on Windows startup of the Internal Server/Archive Server when
required.
If the system was shut down in the System node of the System Console, the automatic start of the
Local Recovery Tool is performed not before the system is started in the System node of the System
Console on the Internal Server. When the system is kept shut down, then no automatic recovery takes
place. In this case, the Local Recovery Tool can be started manually from the Windows start menu.
Services will stay inactive and starting applications will stay in wait mode until the recovery has been
finished by the Local Recovery Tool. The System Console shows this in the System page.
If the Local Recovery Tool is started automatically, it is not visible, because it runs in the 'Service'
session 0 of Windows. To see the progress of the recovery, check the RecoveryTool.log on the Internal
Server or on the Archive Server.
If the Local Recovery Tool has finished successfully for internal and archive recovery, the system can be
started (See Startup above).
If the Local Recovery Tool has failed on internal or archive recovery, the System Console gives further
instructions on how to proceed. Check the RecoveryTool.log on the Internal Server or Archive Server
for more details of the failure.
17.4.3.1 Failed Archive Recovery

In case of a failed archive recovery, the System node of the system console on the Internal Server shows
a dialog where it is possible to force the system startup even on a failed archive recovery. Please strictly
follow the instructions in this dialog before forcing a system startup.
17.4.4 Manually Running the Local Recovery Tool

The Local Recovery Tool on the Internal Server will stop the NetMsgService, which will lead to a full
shutdown of the whole system. All currently running applications and all services will start up again
after the database recovery part of the recovery process is ready.
When an additional archive recovery is necessary (on the Internal Server or on the Archive computer),
or when the user has decided to run it, it is necessary to manually shut down the whole system before
archive recovery can take place. The Local Recovery Tool will check the state of the whole system and
will not execute the archive recovery as long as there are any active applications or services.
After archive recovery it is necessary to manually start up the system using the System Console.
Link Recovery Tool 17 IntelliSpace Perinatal Repair and Recovery
17.5 Link Recovery Tool

The Link Recovery Tool helps to identify and repair inconsistent patient records on linked IntelliSpace
Perinatal systems.
It was originally developed for use exclusively with linked systems. The Link Recovery Tool is also used
when merging systems or creating new links between systems. The purpose of the tool in this case is to
generate the reports, which help to create a successful system “merge” or “link”.
It can run on any IntelliSpace Perinatal computer that has a network connection to each group of
linked systems to be merged. The other systems do not have to have the OBTV-link option installed. It
can also run on a standalone system.
17.5.1 When to Use the Link Recovery Tool

• Use this tool when IntelliSpace Perinatal Link patient record transfer fails due to invalid or
inconsistent patient record state among connected systems.
• The Link Recovery Tool must be used after complete reinstallation from archive (using RFA) of a
system that is connected to other IntelliSpace Perinatal systems with IntelliSpace Perinatal Link and
participated in patient record transfer.
• The Link Recovery Tool must be used before and after performing a merge of two systems with RFA
Index Merge Tool. See also System Upgrades, Merging or Linking Systems on page 278.
• Run this tool to identify inconsistencies of unique patient identifier usage across linked systems.
These inconsistencies can prevent IntelliSpace Perinatal Link from working properly. Inconsistencies
with unique patient identifiers must be cleaned up manually.
• The reporting capability of the Link Recovery Tool can also be used on IntelliSpace Perinatal
systems without the Link functionality in order to assist with other patient record issues. Please refer
to Generated Reports and Log Files on page 222 for more information about the reports.
17.5.2 Prerequisites
Before starting the Link Recovery tool, make sure that:
• a network connects the Internal Servers of the involved systems.
• the close process is finished for all episodes that have been transferred to other systems. Wait for 15
minutes until the data has been written to the archive location.
Execute the update archive tool (see Using Update Archive Tool on page 175) choosing the option
"no" to monitor the archiving progress. 
In the IntelliSpace Perinatal System Console, stop the OBTV Link Service.
This prevents further IntelliSpace Perinatal link transfers during the time of link status assessment
and recovery. Do not restart this IntelliSpace Perinatal service again until the link recovery is
finished.
17.5.3 Using the Link Recovery Tool
17.5.3.1 Where to Run the Link Recovery Tool

Link Recovery needs to run on a computer that has a direct network connection to all Internal Servers
of the linked systems.
17 IntelliSpace Perinatal Repair and Recovery Configuration Backup (Internal Server Only)
17.5.3.2 Running the Link Recovery Tool

1 Shutdown IntelliSpace Perinatal at all computers where the Link engine is installed. This is
normally the External Server of an IntelliSpace Perinatal system.
2 Start the Link Recovery Tool.
3 Follow the instructions on screen. Configure all involved systems. You can always cancel or restart
the recovery process using the Cancel or Back buttons.
4 Complete the link recovery. Follow the instructions on screen.
5 Restart IntelliSpace Perinatal on all computers where it has been previously shut down.
CAUTION Ensure that all linked Internal Servers are configured. Failure to do so will result in incorrect patient
states. Double charting could result.
Never select "Reporting Only" or "Skip automatic clean up / repair" if it is offered in repair cases such
as after RFA.
17.5.3.3 Generated Reports and Log Files

The tool generates reports during the link recovery process. These reports can be found in a sub-folder
LinkRecover under the path that the user defines when running the tool. The same path also contains
the file LinkRecoverReports.xlsm (MS Excel) which can be used to review the reports, and which also
contains a description of the reports. To allow automatic data refresh the generated
LinkRecoverReports.xlsm can be added as "trusted document" in MS Excel.
17.6 Configuration Backup (Internal Server Only)

This tool is used to save or reload an IntelliSpace Perinatal database configuration. Details are
described in the IntelliSpace Perinatal System Administration and Configuration Guide.
17.6.1 Preconditions
• Configuration Backup runs on an IntelliSpace Perinatal Internal Server only.
• You can reload a configuration immediately after reinstalling IntelliSpace Perinatal with the option
New Database. Select Do not start system when finishing setup. You cannot reload a configuration
if IntelliSpace Perinatal has been started previously.
Retrieve from Archive (RFA Wizard) 17 IntelliSpace Perinatal Repair and Recovery
17.7 Retrieve from Archive (RFA Wizard)

The RFA tool is able to restore patient data, stored on an NBS location, to the IntelliSpace Perinatal
internal and external database. This means that you are able to retrieve the archived patient episodes
when you run IntelliSpace Perinatal or run statistics using the external database.
You can restore single or multiple patients (or a whole set of available archived patients) from an NBS
location.
It is also possible to merge archived data from different IntelliSpace Perinatal systems into a single
database. This can be necessary when multiple IntelliSpace Perinatal systems should be merged to one
system.
Restoring patient data is done in two steps:
1 Restore or merge the archive index into the database.
2 Import patient data from the archive index to make it fully available to the application.
In Archive view-only mode this step is not necessary, as episodes can be retrieved directly from the
archive index.
The medical record number, social security number and patient identification must be unique. If
imported patients have the same patient identification on another system, the older patient record is
marked with a red cross in the Identify/Search Patient (Rolodex) screen and new episodes cannot be
added for this patient record. Merging different systems may result in “disabled patient-records” if
there are patient records with conflicting identifiers.
The external database does not require unique patient identifiers. Therefore, patient records which
have duplicate identifiers are not marked as a disabled record (with a red cross). In reports and
statistics, these count as separate patients.
CAUTION In case of hardware failures or system corruptions check Recovery Process After Hardware or System
Software Failure on page 206 before reinstalling IntelliSpace Perinatal.
RFA should only be used as the last resort if recovery of the IntelliSpace Perinatal database is not
possible from a backup database.
Requirements:
• Storage enabled in IntelliSpace Perinatal software.

• IntelliSpace Perinatal database engine is running.
Rules and Restrictions:

• If the system option Archive view-only is switched off, the whole system must be shut down to
recover and import patient data.
• If the system option Archive view-only is switched on, the system can be in clinical use while
merging an archive index.
• While recovering the External Database, the system can be in clinical use, but document printing is
not possible. OBTV Export Service must be stopped using the system console.
• In all cases, the RFA tool must be started on the IntelliSpace Perinatal machine where Archiving is
installed. The IntelliSpace Perinatal application and other support tools must be closed on this
machine.
17 IntelliSpace Perinatal Repair and Recovery Retrieve from Archive (RFA Wizard)
CAUTION When merging a system with Newborn option into a system without Newborn option, Newborn
patients are ignored and cannot be retrieved after the merge.
17.7.1 Checks Before Running the RFA Tool

The RFA tool reads all patient data from the network storage location.
Before you run the RFA tool you must do the following at the IntelliSpace Perinatal server:
1 For linked systems only: Run the Link Recovery Tool to check the uniqueness of patient
identification fields among the linked systems before carrying out the RFA merge.
2 Run the Local Data Recovery Tool to verify that the current database has no errors (see page 218).
3 Backup IntelliSpace Perinatal to a secure location.
4 For more information refer to the System Administration and Configuration Guide.
5 Make a backup of the external database (see the External Database Guide).
6 Shut down the IntelliSpace Perinatal system using the System Console.
17.7.2 Special Considerations When Using RFA on Linked Systems

If you use RFA to restore an internal database of a system that is part of a group of linked systems, the
tokens belonging to patient records received from other systems may get lost.
If this occurs, it means that no system has the patient record token, and therefore it is not possible to
create new episodes for the patient. The patient documentation cannot be continued until the token is
repaired.
The following methods are available to repair the token:
1 Full Token Repair
This repairs the tokens of all affected patient records. The tokens are restored to the system where
the latest episode of this patient was closed. If a patient was transferred to the RFA recovered
system in that latest episode, the token is recovered back to the source system.
Users can open a new episode using "Pull from Link" if the token resides on a linked system.
To recover the tokens, run the Link Recovery Tool.
2 Quick Token Repair
This repairs the tokens of all affected patient records. Usually, the tokens are restored to the system
where the last episode of the affected records was closed. You may need to transfer patient records
to the repaired system using "Pull from Link" at the Identify/Search Patient screen (Rolodex).
Use the Link Recovery Tool.
3 Individual Token Repair
This repairs the tokens of selected patient records. You may need to transfer the patient records to
the repaired system using the Pull from Link feature.
Use the Token Overview and Repair dialog in the Identify/Search Patient screen (Rolodex).
17.7.3 Using the RFA Tool

The tool is password-protected. Only IntelliSpace Perinatal users with System Manager permission and
the permission to change patient data can login.
At the IntelliSpace Perinatal server:

1 Start the RFA tool (In Windows, go to Start  Programs  IntelliSpace Perinatal Support 
Retrieve from Archive).
2 The archive index in the database might need to be restored as a first step. What exactly needs to be
done depends on the availability of archive index data in the NBS folder and the Archive view-only
system option. Follow the on-screen instructions shown by the RFA tool.
3 Click Next > to step through the wizard. Follow the on-screen instructions.
17.7.4 Importing Patient Data Created by OB TraceVue A.02.00 or

Higher
Select the corresponding option in the Wizard to be able to import patient data created by OB
TraceVue A.02.00 or higher. Optionally, you can select Directly start importing all missing episodes.
Otherwise, the patient selection dialog appears, showing all known patients (OB TraceVue A.01.x
patients are not included).
To filter patient records which require importing, select checkbox Show unimported patients only. 
To show System Audit Trail Record, select checkbox Show Audit Trail Record only.
Archive view-only systems: Patient records merged by RFA cannot be imported and are not shown in
this list. Patient records that were created in the application or by HL7 and are now missing after
recovery from a tvbackup can be imported.
Enter any required data to identify a single or several patients. It is possible to enter a time range in
which the last episode of a patient was closed.
• Select the patients you want to make retrievable with OB TraceVue by clicking on them, or use the
buttons on the right to select and deselect them.
• Press Start Import Data.
17.7.5 Importing Patient Data Created by OB TraceVue A.01.64
When retrieving data from A.01.xx into OB TraceVue, you must run Retrieve from Archive (RFA
Wizard):
1 Select retrieve from A.01.xx disks (all NBS sub-folders related to A.01.xx disks are listed).
2 Select a folder related to an A.01.xx disk to be imported.
3 Restore the data.
4 Repeat steps 2 and 3 for all disk folders to be imported.
17.7.6 Finalizing Imported Patient Data

After importing data to the internal database on linked systems, an additional step is required to restore
the patient state across linked systems. See Merge Patient Data From Another Archive (Archive View-
Only Mode) on page 227.
17.7.7 Merging Patient Data From Another Archive
This option is only available on systems having Archive view-only switched off. 
Copy all patient data folders from the source network location to the destination network location
using c:\tv2\prog\MergeArchiveFolders.cmd. Execute MergeArchiveFolders without parameters in a
command prompt to view usage instructions.
The tool does not copy folders starting with "index" (such as "index" or "index.bak").
The tool does not copy the file ID.XML.
The above mentioned items should not be copied manually either. Before starting the actual merge, the
RFA tool asks for confirmation if this manual step has been executed.
Use the RFA tool to read the archive index from the source network storage location (select network
path).
17.7.8 Merge Patient Data From Another Archive (Archive View-

Only Mode)
This option is only available on systems having Archive view-only switched on. It allows to merge the
archive index from another archive while the system is in use. The duration of the merge is about 30
minutes, but depends on the amount of data. The merge process is the same as described in Merging
Patient Data From Another Archive on page 227. The process can be stopped and resumed later at any
time. Patient records merged in this mode do not require the time-consuming Importing Patient Data
step. They can only be retrieved in the system, but cannot have new episodes.
17.7.9 Restoring the External Database

This feature allows the user to complete the contents of the external database by importing archived
episodes (created with OB TraceVue Rev. A.02.00 or higher) from the NBS location.
Due to the complex process of restoring the data, it may take several hours to restore the complete set
of data. The dialog shows a rough time estimation based on the data already processed.
If a customer does not need statistical reports from notes data, it is possible to exclude notes data from
the restore process. This will considerably reduce the time required.
There are options to import or repair, which differ in how patient records for restoration are selected:
17.7.9.1 Import Missing Patient Records

The intended use is to restore single or multiple patients that are missing from the external database,
for example, in case of a temporary downtime of the external database server or if systems were merged.
Patients merged in Archive View-only mode are ignored and cannot be imported into the external
database.
If you choose the first option, Import selected missing patient records..., you can manually select the
patient records to import. It is recommended to specify a time range using Search for patients with last
episode closed.... The time range should not start earlier than displayed in RFA. Episodes that were
closed earlier are purged automatically.
If all missing patient records shall be imported, select Import all missing patient records… to skip time-
consuming patient selection
17.7.9.2 Repair Incomplete Patient Records

The intended use is to repair existing patient records with missing pregnancy or newborn data on the
external database, which may result in incomplete statistical data.
The tool automatically identifies these incomplete patient records and displays their count when you
select this option. It is not possible to select or deselect patient records, the repair process runs
automatically when the Next button is clicked. Review the report file for a list of affected patient
records after processing.
17.7.10 After Running the RFA Tool

• In linked systems, after restoring the database on an Internal Server, you must run the Link Recovery
tool to set the correct patient states. In this case do not check the box "Reporting only" and do not
check the box "Skip automatic clean up / repair" if it is offered.
• Check the log file and the report files for errors.
17.7.11 Log File

The RFA tool automatically generates a log file: C:\TV2\LOGDATA\RFAWiz.txt. This file records
information about:
• Each action performed by the user.
• Each action performed by the RFA tool.
• Errors during operation.
17.7.12 Report Files

The RFA tool automatically generates the following report files:
• C:\TV2\LOGDATA\RFAIntDBReport.txt
• C:\TV2\LOGDATA\RFAExtDBReport.txt
These log files are overwritten with each start of recovery. Rename these files if you wish to keep them.
The report files contain records about:
• Successfully imported patient records
• Patient records which could not be imported
• Patient records which were disabled because of patient identifiers not being unique 
(MRN, SSN, ID).
17.7.13 Error Messages
17.7.13.1 At Start-up
Error Message Reason/Solution
The executable file is not valid. Please The executable file was modified after compilation. A
install correct version. possible reason is an error during a copy.
Invalid password Re-enter using correct password.
Another part of IntelliSpace Perinatal is Only one support tool or IntelliSpace Perinatal can be
already running. Press OK to exit running at any one time.
Unable to connect to IntelliSpace Perinatal IntelliSpace Perinatal database is not running. Reboot
database Server machine and try again. Verify whether the
IntelliSpace Perinatal software was installed correctly if
the problem persists.
17.7.13.2 In the Main Window
Errors occurred during operation! See An error occurred when the patient data was being
logfile C:\TV2\LOGDATA\RFAWiz.txt imported into the IntelliSpace Perinatal database.
for details Affected patients are listed in the log file.
17.7.13.3 In the Log File
ERROR: Importing Patient The selected patient data could not be imported into the
<patient_name> into TraceVue TraceVue database. Possible reasons:
database failed • An incomplete backup disk has been migrated to NBS.
• Missing or corrupted files.
This applies only to data archived Patient demographics are lost because of corrupted data
with revisions A.01.xx. records. The patient records affected are marked with XXX
WARNING: Duplicate records were
detected in datafiles! Some patient
demographics may be lost!
HP Array Configuration Utility 17 IntelliSpace Perinatal Repair and Recovery
17.8 HP Array Configuration Utility

From the Internal Server or a remote computer, this utility let you review and change settings for the
disk array.
17.8.1 Locating the Array Configuration Tool

1 Start Programs  HP System Tools
2 Choose HP Array Configuration Utility
For further information, see the HP Array Configuration Utility User Guide.
17.8.2 Configuring a Replacement Disk

No manual configuration is necessary:
• If a disk in the array fails, the dedicated spare disk is included into the active array automatically.
• If installing a replacement disk, the disk is included into the active array automatically. The former
spare disk is excluded and its status is re-set to spare.
17 IntelliSpace Perinatal Repair and Recovery HP Array Configuration Utility
18
18System Check
Please refer to the IntelliSpace Perinatal Site Preparation and IT Specification Guide.
18 System Check
19
19IntelliSpace Perinatal
Installation
19.1 Introduction
This chapter tells you how to install the IntelliSpace Perinatal software.
Before installing, make sure that all prerequisites, such as the requirements described in the Site
Preparation and IT Specification Guide, are fulfilled.
IntelliSpace Perinatal setup guides you through the Setup process. Instructions at each screen tell you
exactly what you need to do at that point. This chapter gives a brief outline of all possible Setup
screens. The configuration you choose, however, determines exactly which screens you see.
19.2 When to Reinstall IntelliSpace Perinatal

You will need to reinstall IntelliSpace Perinatal under the circumstances described in:
• Troubleshooting on page 119
• Repairing/Replacing Hardware and Media on page 155
• If you have installed the Windows operating system after installing a new hard disk, or because the
operating system was corrupt.
• IntelliSpace Perinatal Repair and Recovery on page 203
• Upgrades on page 259
• System Upgrades on page 277
• After an upgrade that involves installing or reinstalling the operating system.
• Restoring the IntelliSpace Perinatal Philips Password on page 251
If the password of the Philips user must be reset to its defaults value.
NOTE When you reinstall IntelliSpace Perinatal and the previously installed system was enabled for Newborn,
it is not possible to unselect Newborn and Forms based patient record. To remove the Newborn system
setting you must completely uninstall and then reinstall IntelliSpace Perinatal.
19 IntelliSpace Perinatal Installation IntelliSpace Perinatal Setup
19.3 IntelliSpace Perinatal Setup

IntelliSpace Perinatal setup allows you to install the software and to change system options.
19.3.1 Installing IntelliSpace Perinatal
Before you can install IntelliSpace Perinatal, the Windows operating system must be correctly installed.
19.3.1.2 Starting Setup

You must run Setup on the Internal Server machine before you setup any clients.
Setup allows for the selection of the IntelliSpace Perinatal languages. When upgrading, the language
and the code page that were used for patient data prior to rev. K must be specified.
NOTE On the Internal Server you must run Setup from the Installation medium. On all other computers you
can run Setup from the Internal Server share or from the Installation medium.
1 Logon to Windows as Windows administrator.

2 Run IntelliSpace Perinatal Setup
a. Internal Server
Run \IntelliSpace Perinatal\Setup\Setup.exe from the IntelliSpace Perinatal installation medium.
b. Client / External Server
Run \\<server name>\OBTraceVue\setup\setup.exe
c. Remote Desktop Session Host Server or Small Architecture System
• Go to Control Panel and select the Category view.
• Click on Programs.
• Click Install Application on Remote Desktop...
• Click Next.
• In the field File name type \\<server name>\OBTraceVue\setup\setup.exe.
• Select Install the IntelliSpace Perinatal software
Running Setup 19 IntelliSpace Perinatal Installation
19.3.2 Changing IntelliSpace Perinatal System Options
IntelliSpace Perinatal must be correctly installed.
19.3.2.2 Starting Setup

You can start the IntelliSpace Perinatal Setup at any computer.
Go to Start Programs IntelliSpace Perinatal Support IntelliSpace Perinatal Setup
It is possible to change System Settings only on the Internal Server.
Local settings such as Ports, Server Drives, and External Interface settings must be changed at each
computer individually.
19.4 Running Setup

Restore from Backup:
When running setup on a system where IntelliSpace Perinatal is not installed, it is possible to select
either to install a new system or to restore from a previously-saved backup.
If the restore option is chosen, setup restores the IntelliSpace Perinatal installation from the given
source and then setup integrates this IntelliSpace Perinatal backup into the machine while running
setup.
The restore process offers the following two choices:
1 Recovery Restore
This option restores the system from backup including all settings assuming that the original
system will not start again.
2 Copy Restore
The restore process allows the creation of a copy of an IntelliSpace Perinatal system. This will result
in new internal system identification. This identification will prevent erroneous access of the
copied system to the NBS location of the original system. When installing a copy system, the
storage configuration of this computer is reset and has to be entered manually again.
Restore IntelliSpace Perinatal backup previous revision restrictions:
IntelliSpace Perinatal Rev. K setup can restore backups created with Rev. K, Rev. J, Rev. H, and 
Rev. G.00.xx directly.
Screens:
The following describes all the screens you may see during setup.
1 In the first screen, enter the setup password. Click Next.
2 The second setup screen is the Welcome screen. It shows the copyright notice. You do not need to
make any input at this screen. Click Next to confirm that you want to continue with the setup.
3 In the next screen, a box shows which version of IntelliSpace Perinatal you are about to install.
Click Next to confirm that you want to continue with the setup.
19 IntelliSpace Perinatal Installation Running Setup
4 In the next screen, you decide what kind of setup operation you want. Select one of the following:
Install the IntelliSpace  The new system software is installed (refer to the section 
Perinatal software Install the IntelliSpace Perinatal Software on page 238).
Restore a previously saved  For details on how to restore a backup, see 
IntelliSpace Perinatal installa- Restore an IntelliSpace Perinatal/OB TraceVue Installation on
tion (from backup tool) page 183.
Only change database  This option is only visible if an IntelliSpace Perinatal installa-
settings or system settings tion of the same version already exists on this machine.
Change only port settings and/or system options, no files are
overwritten (Refer to the section System Settings on page 239).
Note: If you select this option, the correct port settings must be
selected. If not, the port settings will reset to the default settings
(that is disabled).
Uninstall IntelliSpace  This option is only visible if an IntelliSpace Perinatal installa-
Perinatal tion of the same version already exists on this machine.
Deletes existing software from computer. Use this only if you
want to remove IntelliSpace Perinatal from the computer and
do not wanting to reinstall it on this computer (Refer to the sec-
tion Uninstalling IntelliSpace Perinatal on page 252).
Select an option and click Next to continue.
19.4.1 Install the IntelliSpace Perinatal Software

If you select to install the IntelliSpace Perinatal software you must do the following:
1 Specify whether the system role you are installing is:
• Large Architecture System
- with Flowchart
- with Flowchart & Advanced Forms
- with EMR based charting
• Network Client PC (includes External Server and RDSH Server/High-End Data Acquisition
Server).
• Data Warehouse Server
• Small Architecture System
- with Flowchart
- with Flowchart & Basic Forms
2 Click Next to continue.
If you select a type that is different to the currently installed system type, you must confirm the
change. If you install a server version where there was previously a client, you will not be able to use
this computer to access the data that was previously on this computer.
CAUTION If you install a client where there was previously a server, all patient data from the old server/standalone
will be lost.
3 Server only
If you install IntelliSpace Perinatal over an existing version, you have to decide whether to keep the
existing database and data files and reuse them.
Option Patient Data Client

Machines
Keep existing database Patient and No client setup
and data files configuration data required.
remain.
Delete existing Patient data, and Run setup on all
database and data files configuration data, are clients.
DELETED!
Normally you select Keep existing database and data files if you decide to upgrade an existing
installation. Delete an existing database only if you want to reinstall IntelliSpace Perinatal with
completely new settings and patient data.
CAUTION If you select Delete existing database and data files all patient data will be lost.
Click Next to continue.
19.4.2 System Settings

The System Settings password screen is displayed if you have selected to change the system settings, or
if you have completed the steps in Install the IntelliSpace Perinatal Software on page 238.
NOTE It is possible to change system settings only during a server setup because these settings can be changed/
defined only at a server.
1 You must enter the Philips password before you may change any system settings. If setup is running
on a system where IntelliSpace Perinatal is already installed, you can select Do not change system
settings, then the password is not required and you skip the option change screen that follows.
If there is no previous installation on this computer, you must enter the password and complete the
options change screen that follows.
Click Next to continue.
2 The System Settings Screen is displayed. This box lets you change the system settings. Choose the
options that are appropriate for your customer.
Basic alarming Choose this setting if the customer does not require ad-
vanced alarming.
Advanced alarming Choose this to enable system-wide access to the advanced
alarming rule sets as well as the basic alarming rule sets.
Forms based patient record This setting is enabled when Large Architecture System
with Flowchart & Advanced Forms is selected, otherwise
it is deselected.
Newborn charting Select to enable newborn functionality. Can only be se-
lected if Large Architecture System with Flowchart & Ad-
vanced Forms is enabled.
Gynecological charting Select to enable gynecological charting functionality. Can
only be selected if Large Architecture System with Flow-
chart & Advanced Forms is enabled.
HL7 interface Select if you require HL7 Interface.
Storage Choose this to activate system-wide archiving.
IntelliSpace Perinatal Link Select to link together individual IntelliSpace Perinatal
(requires storage) systems.
Note: For the Link to work, IntelliSpace Perinatal Link
must have been selected during Internal Server setup.
Document export interface Select this setting to enable Document Export.
Trace only This setting is selected if Large Architecture System with
EMR based charting is enabled. This disables the preg-
nancy documentation for the system. When Trace only is
selected, new maternal episodes do not start a pregnancy,
and the Flowchart tab and forms are not available for
pregnancy documentation. The only tabs available in
Trace only mode are Single Trace, Notes Browser, Face
Sheet, and Audit Trail.
Archive view-only Select this setting to enable Archive view-only mode. The
Archive view-only mode allows system merge without
downtime, but with some restrictions (see Archive View-
Only on page 250).
Automation interface Select this setting to enable the Automation interface 
(only with special authentication).
Patient record attachment Select this setting to enable patient record attachment
management management.
Meaningful Use certification Select this setting to enable the functionality for Mean-
ingful Use certification.
Audit trail Select to enable the Audit Trail.
3 Click Next to continue.
4 On the second System Settings screen, enter the following information:

Number of Clients Enter the number of clients (including RD client licenses)
plus External Server (if any)1.
Number of Fetal Monitors Enter the maximum number of concurrently running
data acquisition (DAC) sessions per system.
The following is counted as concurrent DAC session:
• Every LAN-based FM connected to the system.
• Every COM port that is configured in IntelliSpace
Perinatal setup on any computer in the system
performing data acquisition.
It is possible that the sum total of all LAN based fetal
monitors configured at each data acquisition computer
(e.g. clients) exceeds this number of concurrently running
data acquisition session per system. This is because you
configure typically more LAN based fetal monitors per
computer than physically connected to allow the fail save
operation of the LAN based fetal monitors (that is when a
DAC computer goes down and another DAC computer
takes over the LAN DAC sessions). The following equa-
tion expresses the maximum number of LAN DAC ses-
sions per system:
Maximum Number of running LAN DAC Sessions =
(maximum number of concurrently running DAC ses-
sions per system) – (sum total of configured COM ports
on all data acquisition computers).
1. The limits discussed in the Site Preparation and IT Specification Guide must not be exceeded.
19.4.3 Configure Settings

This box allows you to define which settings you want to configure during setup. You can select to
define the following:
Define for this PC: Port settings

Configure server drives
Storage settings
External interface settings (Link, HL7 interface, exter-
nal database, document export)
Language of online help
Define for the System: UI settings (available Forms, language and alarm stan-
dard, CTG trace analysis)
Patient identification field and HL7 message types
IP addresses of remote client servers
Configure IntelliSpace Perinatal System Key
Configure type of context synchronization
You are able to configure only the items that you select here. If you do not select an item here, you will
not see the configuration screen for this item. The following section describes each screen.
19.4.3.1 Assign Disk Drives (Backup Drive)

Data can be spread onto different disk drives to improve performance of the internal database backup.
Setup supports up to four disk drives for the Internal Server. When using more than two drives, the file
system structure of a two-disk-system will be simulated by links (junctions).
Specify the drive(s) for the Server machine. In the following description, the drive letters C:, D:, E: and
F: are used, you may need to use other letters:
Depending on the number of drives used, the data will be distributed to the drives in the following
way:
Number of Drive Function

drives
1 C: Program, database, database transaction log, patient data

and database backup
2 C: Program, database, and patient data
D: Database transaction log, database backup and patient data
backup files
3 C: Program, database, and patient data
D: Database backup and patient data backup
E: Database transaction log
4 C: Program and patient data
D: Database backup and patient data backup
E: Database transaction log
F: Database
We recommend to use the drives exclusively for IntelliSpace Perinatal for best performance, and to
keep the virus scanner updated according to the drives used.
Make sure to perform a backup before any change in the multi-disk configuration.
CAUTION Do not change your existing RAID configuration when adding new drives. Otherwise data loss may
occur.
19.4.3.2 Select Forms to Use

Select the Forms for system-wide use. The availability of forms depends on the selected system type:
19.4.3.3 Appearance of the IntelliSpace Perinatal System

On this screen you define the language, alarm symbols and alarm sounds used system-wide:
• System Language:
Select a language for the whole IntelliSpace Perinatal system.
• Alarm Symbols:
Select the alarm symbols used by the whole IntelliSpace Perinatal system, corresponding either to
Alarm Standard IEC/EN 60601-1-8 or IntelliSpace Perinatal classic symbols.
• Alarm Sounds:
Select the alarm sounds used by the whole IntelliSpace Perinatal system, corresponding either to
Alarm Standard IEC/EN 60601-1-8 or IntelliSpace Perinatal classic sounds.
• Repetition of Low Priority Alarms:
Select Suppress flashing alarm icon and alarm sound repetition for low alarms if the customer
requests no visual or acoustical repetition of low priority alarms. If this option is selected, the icon
statically indicates the low priority alarm condition but does not flash, and the alarm sound is
generated only once.
• Select system language and code page used for processing patient data of IntelliSpace Perinatal
prior to Rev.K:
Select the Language to be used for the patient data. For upgrades, IntelliSpace Perinatal Setup
requires the configuration of the ‘Language for non-Unicode programs’. This defines how data
entered prior to IntelliSpace Perinatal Rev. K are read, converted and interpreted in the Rev. K
system. Otherwise patient data may become unreadable. The default is the current Windows
configuration language.
19.4.3.4 Language of the IntelliSpace Perinatal Online Help on this PC

Select the language for the IntelliSpace Perinatal online help. You can either select one of the languages
from the list, or the IntelliSpace Perinatal System Language.
19.4.3.5 CTG Trace Analysis

Select one of the following CTG trace analysis settings:
• NICHD 1997
• NICHD 2008
• Dawes/Redman 2002 (Not for U.S.A. and other FDA regulated territories)
19.4.3.6 Specify Patient Identification

• Default Patient Identification Field:
Define the ID used for patient identification in your system:
– Medical Record Number
– Patient ID
– Social Security Number
• Check the box Enforce uniqueness of Social Security Number to ensure that the system does not
allow the same SSN for more than one patient. There may be situations, e.g. when the SSN of a new
patient is unknown at the moment of admission, when you might want to be able to use a kind of
preliminary identification. If this is the case for your institution, uncheck this box.
• Patient ID field:
Used to define the appearance of the patient ID field in the system. Leave empty if you want to use
the default patient ID field.
– Label: Label of the patient ID field (max. 30 characters)
– Abbreviation: Abbreviation (short name) of the patient ID field (max. 8 characters)
– HL7 Identifier Type Code: Assign an HL7 type identifier from a list of available HL7 type
identifiers, or type free text.
19.4.3.7 HL7 Message Type

Select the HL7 message types that your system supports:
• Incoming and outgoing ADT
• Outgoing Observations (charting)
• Incoming ORU (LAB, charting)
• Outgoing MDM (documents)
Each routing type requires an appropriate HL7 license.
19.4.3.8 IntelliSpace Perinatal System Key

Click Configure IntelliSpace Perinatal System Key... to enter the System Key. This key is used as a
password for the Windows users created by Setup and to configure the database users of the internal
and external database of this system. The System Key must be provided by the customer be stored in a
safe location. Philips employees and personnel of service providers must not document the System Key
anywhere.
The Setup prompts for a new System Key:
• during new installations and
• upgrades from Rev. < K.0020
and also for the already used System Key:
• during installations/upgrades of all machines belonging to this system, all linked systems and
data warehouse server loading data from this system
• during restoring a backup on existing or new hardware
• potentially during other recovery scenarios
System Key criteria:
The System Key must match the Windows password criteria configured for the operating system. 
In addition, it must not:
• begin with white space, single quotes, or double quotes
• contain semicolons
• be longer than 100 characters
19.4.3.9 Context Synchronization

Select the type of context synchronization you want to use in your system:
EPIC or vendor neutral.
19.4.3.10 Regional Settings

This is only visible on the Internal Server when the regional settings have changed since the last run of
the setup. Click Accept using these regional settings for all IntelliSpace Perinatal Windows services in
a system. If the displayed regional settings are not OK, change them in your operating system.
19.4.3.11 Fetal Monitor Connections (Ports)

This screen lets you define for which type of data acquisition the existing ports will be used. It is
available on network clients and Internal Servers (up to 50 clients).
Serial Port: Fetal Monitor connected directly to the computer (RS-232) or via serial port server.
Ethernet: Fetal Monitors connected directly via Ethernet.
For further information refer to the Site Preparation and IT Specification Guide.
NOTE If serial ports are used for other purposes, then the ports do not appear in the list. The maximum
number of Fetal Monitor connections may be decreased.
19.4.3.12 Archive/Retrieve Module

If you run the archive and retrieve module on this PC, select Archive and Retrieve is running on this
PC. In this case, define the storage location. You can optionally specify a user account to access the
location, and you can run a network access test.
19.4.3.13 External Interface Settings

You must make sure that the corresponding options are enabled during server setup. Select from the
following options:
Install HL7 Interface/Link on Only possible to select when optional HL7 interface or
this PC. link is enabled.
Only one computer can have HL7 Interface.
HL7 and IntelliSpace Perinatal Link always reside on
one computer.
Install Document export Inter-
face on this PC
Install External Database on Only available on client computer if no data acquisition
this PC is configured.
Install a new External Data- All data is deleted in current external database.
base
Keep the External Database
Assigning Multiple Disk Drives during External Database Setup:


Data can be spread onto different disk drives to improve performance of the external database. Setup
supports up to three disk drives for the external database. When using more than one drive, the file
system structure of a one-disk-system will be simulated by links (junctions).
Specify the drive(s) for the Server machine. Depending on the number of drives used, the data will be
distributed to the drives in the following way:

drives
1 C: IntelliSpace Perinatal Installation

External Database (.db)
External database transaction log (.log)
External Database (.db)
D: External database transaction log (.log)

drives

D: External database transaction log (.log)
E: External Database (.db)
We recommend to use the drives exclusively for IntelliSpace Perinatal for best performance, and to
keep the virus scanner updated according to the drives used.
Make sure to perform a backup before any change in the multi-disk configuration.
CAUTION Do not change your existing RAID configuration when adding new drives. Otherwise data loss may
occur.
19.4.3.14 Word and Excel Templates

If you reinstall IntelliSpace Perinatal and the setup procedure finds already installed Word or Excel
templates, it asks whether to keep these existing templates, or install new ones:
• Keep Current: The C:\tv2_templates\customer directory is kept, but all other files and directory in
C:\tv2_templates are replaced by the content of the current revision.
• Install New: Setup moves the old C:\tv2_templates directory to a backup location and installs the
new templates to the C:\tv2_templates directory. The C:\tv2_templates\customer directory is filled
with the new factory default files.
See also Upgrading Word and Excel Templates on page 274.
19.4.3.15 Configure IP Addresses of Servers for Remote Clients

Specify the addresses of the Internal and External Server to be accessed by remote clients. For more
information refer to Installing and Configuring Remote LAN Clients on page 89.
19.4.3.16 Server Name (client only)

IntelliSpace Perinatal clients need to know their Server machine. Enter the computer name of the
Internal Server into the edit field.
19.4.3.17 Archive View-Only

The Archive view-only option avoids system downtime during system merge with the consequence of
permanent restrictions as described below.
Once the Archive view-only option has been chosen in the setup and the system is started, it is not
possible to remove this option anymore.
The Archive view-only option changes the behavior of the RFA Tool for merging patient records and
patient administration in the IntelliSpace Perinatal application. If the Archive view-only option is
chosen, the RFA Tool will merge patient records from an archive without importing them. This merge
is possible while the system is running in clinical use, and it is much faster than the merge without this
option.
Archive view-only patient records can be retrieved without any restrictions. However, they are
completely separated from those patient records which are created manually or by automatic ADT.
New episodes as well as re-opened episodes, corrections, patient merges and disabling of patient records
are not possible for Archive view-only patient records. These records are also not updated by incoming
HL7 messages, and they are not included in uniqueness checks. They are not visible in the Patient Data
Administration Tool (Internal DB) and in reports of the Link Recovery Tool.
To continue the documentation of an Archive view-only patient, a new patient record has to be
created. This record will appear as an additional row in the search result of the Patient Search. Archive
view-only patients can be found via the Patient Search in the IntelliSpace Perinatal application. You
can search for the following fields: First name, Last name, Maiden name, Middle initial, Date of Birth,
MRN, SSN, Identification.
Administrative actions from previous systems like disabling, merging or deleting via Patient
Administration Tool are undone by merging the archive in Archive view-only mode.
Recovery of Archive view-only systems:
The Archive view-only option does not influence the usual backup and recovery procedures. 
If no tvbackup is available and such a system needs to be fully recovered from its archive: all patient
records, including those created since initial installation, will be merged as Archive view-only patient
records with the restrictions described above.
Finishing Setup 19 IntelliSpace Perinatal Installation
19.5 Finishing Setup

Setup copies the files and configures the installed system and database.
If you select database settings which do not match, a screen is displayed informing you that you must
redefine them. To do this click Next.
If setup cannot find the files to copy, a screen is displayed. You must browse and select the directory in
which the files are stored. Setup does not continue until you have selected the correct directory.
After setup has copied the files and configured the system and database, a screen is displayed telling you
that setup is successful. You must reboot the computer to run IntelliSpace Perinatal. To do this click
Finish.
If setup fails a message is displayed. Click OK to return to the Windows main screen. Contact your
local support.
Apply available IntelliSpace Perinatal service packs for this revision.
19.6 Restoring the IntelliSpace Perinatal Philips

Password
Users can change the password of the Philips user.
To restore the password of the Philips user you must reinstall the IntelliSpace Perinatal software:
1 Run the IntelliSpace Perinatal Setup from the current medium at the Internal Server:
• Install the IntelliSpace Perinatal Software
• Keep settings Network Server or Standalone PC as is.
• Keep existing Database and Data Files.
• Uncheck all check boxes in order to not change any settings.
• Select Leave the current installed document template directory as it is.
2 Press Finish to reboot the computer.
3 Apply available IntelliSpace Perinatal service packs for this revision (and backup the configuration).
19 IntelliSpace Perinatal Installation Installing / Upgrading Word and Excel Templates
19.7 Installing / Upgrading Word and Excel

Templates
• When you select Install the IntelliSpace Perinatal Software for reinstallation you can choose to
Leave the current installed document template directory as it is. No further action is required in such a
case.
• If you installed new templates see Installing Word and Excel Templates on page 110.
• If you need to upgrade customized templates see Upgrading Word and Excel Templates on page
274.
19.8 Uninstalling IntelliSpace Perinatal

To uninstall IntelliSpace Perinatal, run IntelliSpace Perinatal Setup. Select Uninstall the existing
IntelliSpace Perinatal Software.
The uninstall routine deletes all program files.
It does not remove the ODBC components because these may be used by other applications.
19.8.1 Internal Server

Be careful when you uninstall the Internal Server. The uninstall routine deletes all program files, all
data files and the entire database.
All data will be lost.
19.8.2 Clients
To uninstall IntelliSpace Perinatal, run IntelliSpace Perinatal Setup. Select Uninstall the existing
IntelliSpace Perinatal Software. This will remove the software but keeps the entry of the client in the PC
configuration. To also remove the client settings, remove it from the IntelliSpace Perinatal PC
Configuration.
Uninstalling IntelliSpace Perinatal Link 19 IntelliSpace Perinatal Installation
19.9 Uninstalling IntelliSpace Perinatal Link

1 Delete all other systems in the IntelliSpace Perinatal Link configuration. If there are transfers
pending for any of these systems, the other system cannot be deleted. In this case, uncheck the
permissions to receive maternal and newborn patients (at the IntelliSpace Perinatal Link screen in
the General Configuration setting), wait for a few minutes and retry to delete the other system. If it
still cannot be deleted, the pending transfer cannot be executed because the other system might be
disconnected already. You must wait until that pending transfer is abandoned, e.g. 48 hours after it
was started. You can use the IntelliSpace Perinatal system during this interval.
2 Once all other systems are successfully deleted from the configuration, shutdown the system.
a. Run IntelliSpace Perinatal Setup at the Internal Server.
b. Select Change System Options.
c. Uncheck IntelliSpace Perinatal link, but leave all other check boxes unchanged.
d. Restart the system.
19 IntelliSpace Perinatal Installation Uninstalling IntelliSpace Perinatal Link
20
20Windows Installation
20.1 Operating System Installation and

Configuration
IntelliSpace Perinatal is supported by the following operating systems:
• Servers:
– Microsoft Windows Server 2012 R2 64-bit Standard or Datacenter Edition
or
– Microsoft Windows Server 2019 64-bit Standard or Datacenter Edition
• Clients:
– Microsoft Windows 10 64-bit LTSB 2016
or
– Microsoft Windows 10 64-bit LTSC 2019
CAUTION If you are installing the operating system to perform an IntelliSpace Perinatal Repair and Recovery,
make sure you follow the procedures in the corresponding chapter precisely. If you fail to do so,
unwanted data loss may occur.
20.1.1 For All Software-only Versions of IntelliSpace Perinatal

1 Install Windows. The operating system may be provided by your IT Department. Note that the
Operating System depends on your chosen IntelliSpace Perinatal computer role.
For all Windows versions, the operating system in the local language of choice is permitted.
2 Install the appropriate drivers. Drivers for supported servers and clients originally shipped by
Philips are available on the IntelliSpace Perinatal installation medium.
The files and folder structure of the drivers folder is self-explanatory.
3 Windows 10 / Windows Server 2012 R2 / Windows Server 2019: Install language support via
Control Panel - Languages.
4 Install appropriate Microsoft Updates and Security Hotfixes.
20 Windows Installation Operating System Installation and Configuration
20.1.2 For All Versions of IntelliSpace Perinatal including Hardware
20.1.2.1 Windows Server 2012 R2, shipped prior to K.00.20

1 Ensure the BIOS is set to boot from USB.
2 Plug in the Server OS restore medium and boot the computer.
3 Follow the on-screen instructions.
4 After the image has been deployed to the HDD, close the last remaining command prompt
window to reboot the machine. At the beginning of the reboot, unplug the USB medium in order
to boot from HDD.
5 Wait until the OS installation has finished.
6 After Windows has been installed successfully, install the appropriate drivers, which are available
on the ISP Small Architecture Server Drivers and Firmware medium. 
The files and folder structure of the drivers folder is self-explanatory.
7 Contact Microsoft to activate the operating system. Provide details from the COA label on the unit
as requested.
8 Install the required and other appropriate Microsoft Updates and Security Hotfixes.
The minimum required Microsoft Updates are described in the IntelliSpace Perinatal Site
9 Use the System Check Tool to prepare and validate the operating system settings for IntelliSpace
Perinatal use.
20.1.2.2 Windows Server 2019, shipped since K.00.20

The IntelliSpace Perinatal OS Installation media kit includes Microsoft Windows Server 2019.
IntelliSpace Perinatal Systems Rev. K.00.20 or later installed on Philips-supplied hardware are shipped
with activated Microsoft Windows operating systems.
An Internet connection is not required for activation, also in case of operating system re-installation.
1 Before you start the installation, put the media that contains the Philips software into the
appropriate USB port. Then restart the server. 
Important: Be sure that you have no other USB flash drives in other ports and that no error
appears during installation. You must remove the additional device(s) and click OK in the error
dialog to restart the machine.
2 During the boot sequence, press F11 to open the One-Time Boot Menu.
3 Use the keyboard up/down arrow keys to boot from USB device on which the Philips software is
plugged in. Then press Enter. After a short time a command box opens. Then the Philips Real
Time Analystics Installer dialog opens. 
NOTE: Installer illustrations are representative of the actual screens shown during product
installation; actual screens and text that appears on screens may be slightly different.
4 The Philips Real Time Analystics Installer dialog describes the actions that will occur if you click
OK. Click OK to begin Installation or Cancel to quit.
Operating System Installation and Configuration 20 Windows Installation
Once the destination Disk is discovered, the installer reports the approximate installation time. 
A dialog opens that informs which operating system will be installed.
20 Windows Installation Additional Information
5 To continue the installation click OK, or click Cancel to quit.
If you selected OK the Installer formats the drive and shows the image application progress
percentage.
When installation completes the status appears on the screen. Notification indicates that you can
remove the USB media and an alert that the system will reboot in 15 seconds appears.
6 Click OK in the dialog. 
Important: If you do not have the correct setting for Secure Boot a warning message will appear.
You must have Secure Boot enabled on your compatible hardware for successful installation. It is
equally important that you have the UEFI Optimized Boot setting enabled.
7 Remove the USB flash drive containing the Philips software. 
After reboot, the system may take some minutes to remove components that are not needed.
Important: The SupportUser is automatically logged in. The user can log in two more times
without entering a password. After the 3rd reboot user credentials are required. Change the
password as soon as possible.
20.2 Additional Information

20.2.1 System Check Tool
The IntelliSpace Perinatal System Check Tool provides pre-and post-installation assessment of software
and hardware. For further information about the System Check Tool, refer to the IntelliSpace Perinatal
Site Preparation and IT Specification Guide.
20.2.2 DHCP Server

It is recommended to work with a DHCP server. As a prerequisite for this, Active Directory must be
available. For further information, refer to the Microsoft documentation.
20.2.3 UPS
It is highly recommended to use a UPS as a power backup for the system.
21
21Upgrades
21.1 Introduction
This chapter describes how to upgrade your system from OB TraceVue / IntelliSpace Perinatal system
Rev. G or higher to the latest revision.
High Availability systems will be only a single server after the upgrade and will need additional steps.
21.1.1 User Accounts

Beginning with Rev. J IntelliSpace Perinatal no longer creates the user accounts OBTV Administrator,
Administrator and User when an upgrade is made. If those user accounts already exist, they are ignored
by an upgrade. The customer has to maintain these user accounts, because they are no longer used by
IntelliSpace Perinatal. The user account OBTV Internal 2, created as a successor to OBTV Internal, is
no longer a member of the Administrator’s group.
21.1.2 Moving Functionality During the Upgrade

Upgrade procedures generally require that upgraded computers have the same functionality after the
upgrade.
For example, an HL7 Interface computer remains an HL7 Interface computer or an archiving machine
remains an archiving machine.
Moving functionality from one computer to another has to be performed after the upgrade.
The typical way is to first run setup on the computer that previously had the functionality and switch
the functionality off. In cases where the functionality was on a computer that is not being upgraded,
you can also delete that computer from the list in the PC Configuration screen. Please note that this
also clears all the settings of this computer, including alarm distribution. Then, run setup on the
computer that will have the functionality and switch it on.
21.1.2.1 Backups
When creating backups using the tvbackup.exe tool, do not store them in any Network-Based Storage
(NBS) location folder structure. Store the backups in some other separate, safe storage location.
CAUTION Be sure that at least one episode is archived on the NBS location before upgrading the system to 
the current revision.
21 Upgrades Upgrading from Rev G.00, H.00, J.00
21.2 Upgrading from Rev G.00, H.00, J.00

21.2.1 Upgrade with new or continuing Hardware
This procedure allows for the adding of new hardware to the existing system.
21.2.1.1 Restrictions
• You cannot merge two systems during this upgrade
• Perform steps sequentially unless otherwise stated
Upgrade Overview
From IntelliSpace Perinatal Rev.G+DQG-
Customer provided
storage locations
Backup Int-Srv Ext-Srv All other
Shutdown
System
Backup
Backup Backup
$OOGDWDLQ%DFNXSRQO\
OS
,QVWDOO
Install OS Install OS Install OS
System Check System Check System Check
Upgrade
Setup/Restore
Start and activate
Setup/Restore Setup
Legend:
Data Startup
Flow
Start Start Start
Process Application Application Application
Flow
Upgrading from Rev G.00, H.00, J.00 21 Upgrades
21.2.1.2 Preparation of New Hardware (if applicable)

This step prepares the new hardware for the upgrade. Existing hardware that is currently not in use in
the old system must be prepared as well. During this step the existing system can still be running with
its full functionality.
Installing Windows Server 2012 R2 / Windows Server 2019 (all new servers):
1 Physically prepare the new hardware for installation. Add additional components, etc.
2 Install new operating system, according to the IntelliSpace Perinatal Rev. K installation process.
During this preparation, the new hardware requires a hostname / IP address different from the old
hardware if running on the same network.
See Windows Installation on page 255.
This step includes running the System Check Tool and correcting all identified problems.
Installing Windows 10 (all new clients):

1 Install new operating system according to the IntelliSpace Perinatal Rev. K installation process.
During this preparation, the new hardware requires a hostname / IP address different from the old
hardware if running on the same network.
See Windows Installation on page 255.
21.2.1.3 Prepare Old Hardware

1 If the system has an HL7/ ADT interface, use the Copy of Configuration button in the System
Managers Configuration screen to create a configuration text file and store it in a safe storage
location. For more information, refer to the Configuration text file.
You can use the contents of this file to configure the HL7 routes in the IntelliSpace Perinatal
application after the upgrade.
2 Shutdown IntelliSpace Perinatal / OB TraceVue on currently running system.
3 Run the Local Recovery Tool on the Internal Server to ensure that the database is not corrupted.
4 Continue with step 5) if the system is not a High-Availability system:
a. Check the mirror status in the management console. The Drive_D must be green and the detail
information about the mirror must indicate that the remote and local member disk states are
Healthy. Follow the detailed procedure below:
• In the EMC console, expand Data Sources
• Highlight Drive_D
• If the Results pane is not empty, click Clear Results
CAUTION Make sure you do not click any other icon than mentioned in the next bullet!
• In the tab Status click the second icon from the right Get Information from the current Data
Source.
• In the Results pane scroll down and check if the State is healthy
Member Server Disk Sig Offset Length State
1 <host name 1> xxx yyy zzz healthy
2 <host name 2> xxx yyy zzz healthy
If the state is cracked, then the disk is in automatic synchronization mode and you are at risk
for data loss when performing an upgrade now. Please wait until the state transitions back to
healthy (you need to retrieve the detail information again, as this detail information is only
displayed upon request. Click Clear Results and Get Information from the current Data Source
again). If the disk does not transition back to healthy but enters the mode Broken, please
perform the appropriate recovery steps in Legato Server Recovery / EMC Autostart Server
Recovery in the corresponding version of the Installation and Service Manual.
b. It is recommended to use the backup (to be created in step 6) from the last active server in order
to continue the upgrade. Determine and write down which server was the last active node.
Highlight the OBTV Application Resource Group (RG) and check the tool tip (hover the
mouse cursor over the RG).

Group: OBTV Application; State: Offline; Last Run On: <server node name>

It is not necessary for the IntelliSpace Perinatal / OB TraceVue application to be running. The
tool tip holds this information even after an operating system reboot. Remove all customizations
from the external database or prepare the database for automatic removal of customizations by
IntelliSpace Perinatal setup. Refer to the External Database Guide about modifications to the
external database.
5 Use the Offline Backup Tool / Backup Tool that is pre-installed on the existing system to backup
IntelliSpace Perinatal / OB TraceVue on the Internal and External Server and store it in a safe
storage location. Note: These backups can be taken simultaneously on both servers (i.e. internal
and external).
6 Backup the Word and Excel templates (only if available on the Internal Server) using the Backup
Tool and store them in a safe storage location.
7 While the old operating system is still installed, check the revisions of the PC BIOS, Raid BIOS
Firmware (if available), and NIC firmware (if applicable) and update them if required. Please refer
to the README.txt located on the IntelliSpace Perinatal distribution medium in the Firmware
folder. The latest updates are marked with an “*”. The minimum required revisions are also
documented in the PC-specific chapters.
8 Check the BIOS settings (in the PC-specific sections of this document) and adjust them if
required. Upgrade iLO firmware on all high-end servers (this must be done even if iLO will not be
used).
9 Print out the installation records of all system computers. Write down TCP/IP settings of the
Internal and External Servers and DHCP if used.
10 Ensure that the customer has backup copies of documentation and files created by third-party
applications, since all software is removed when you install the new operating system.
11 Shut down computers.
12 Only if using the old Internal Server or old External Server for the new system (and if available on
Internal Server or External Server):
• Remove the second network interface card (if installed) from the Internal Server and from the
External Server, and plug the empty slot with a blank.
Install Windows 10 / Windows Server 2012 R2 / Windows Server 2019 (if continuing old server
and client hardware):
1 Make sure you have backed up the installations of the Internal and External Server as described in
Prepare Old Hardware on page 261.
2 Install new operating system according to Windows Installation on page 255.
• Hostnames and IP Addresses

– Internal and External Servers:
• Keep the name (see printed installation record) and the TCP/IP settings of the old computers.
– Other IntelliSpace Perinatal computers (RD Session Hosts Servers, Data Acquisition Server,
Clients, etc):
• Using the name and IP address of the old computer for the newly installed computer is the
easiest way to upgrade.
• If new host names and/or IP addresses shall be used, refer to chapter [Host Names and IP
Addresses] how to preserve all IntelliSpace Perinatal / OB TraceVue computer settings and
configuration of the old computer for the new computer.
21.2.1.4 Preparing Internal and External Server (new or old hardware installed with
Windows Server 2012 R2)
1 Make sure that the newly-installed Internal Server and External Server have the original name,
TCP/IP settings and DHCP Server Configuration (if used).
See printed installation record.
2 Copy the IntelliSpace Perinatal / OB TraceVue backup files from the safe location to the newly-
installed Internal and External Servers. (Only Internal Server: if available, copy also the Word/
Excel template backup files from the safe location to the newly-installed Internal Server).
Upgrading Internal Server to the latest revision of IntelliSpace Perinatal:

On the Internal Server, restore the backup of Word/Excel templates files. Start the Backup Tool and
restore the TV2_Templates directory.
1 Start from the new IntelliSpace Perinatal software medium: 

:\IntelliSpace Perinatal\Setup\setup.exe
Use the following selections:
• Restore from previously saved backup.
• Keep network server selection as it currently is.
• Keep the existing database and data files.
• Keep current document templates.
• Do NOT delete the existing database and files.
• Enter Accept and confirm internal database upgrade.

• Do not activate the IntelliSpace Perinatal services!
• Click Finish to reboot the computer, or reboot manually.
2 Apply available IntelliSpace Perinatal service packs for this software revision.
Upgrading External Server to the latest revision of IntelliSpace Perinatal:

1 Make sure that Windows is up and running on the Internal Server.
2 Start the IntelliSpace Perinatal setup from the Internal Server share:
a. Go to Start → Run
b. Type \\<server name>\OBTraceVue\setup\setup.exe
c. Select Install the IntelliSpace Perinatal software.
• Restore from previously saved backup.
• Keep network client computer selection as it currently is.
• Enter Accept and confirm external database upgrade.
• If prompted: Keep existing external database.
• Click Finish to reboot the computer, or reboot manually.
3 For optional Office printing, install Microsoft Office, including required Service Packs and
Hotfixes. See the IntelliSpace Perinatal Site Preparation and IT Specification Guide.
Do not activate the IntelliSpace Perinatal services.
Only if Archiving is running on a Client:

If neither Internal Server nor External Server are configured for Archiving, install the Client machine
that will be configured for Archiving. See Upgrading Clients on page 266.
Start IntelliSpace Perinatal:

Select Start whole system in the IntelliSpace Perinatal System Console on the Internal Server and
then additionally on the Archive computer (if applicable). In some installations the Archive computer
is a separate computer, but typically the Archive computer is the Internal Server. For further
information about the IntelliSpace Perinatal System Console see the IntelliSpace Perinatal System
Administration and Configuration Guide.
21.2.2 Upgrading IntelliSpace Perinatal computers other than

External and Internal Server
Host Names and IP Addresses:
1 Host Names:
IntelliSpace Perinatal identifies a client by its hostname. Therefore, when replacing an old client
with a new one during upgrade, the easiest and most robust way is to use the same old name for the
new computer according to Replacement Client on page 153.
The host name must be set to the old name before IntelliSpace Perinatal setup is executed to add
the new client to the system.
Alternative way when it is required to use new host names for clients that replace old clients:
• Run c:\tv2\prog\tvbackup on the old client.
• Install the operating system on the new client with a new name.
• OB TraceVue / IntelliSpace Perinatal must not be installed. If it is, uninstall it first.
• When running setup to install the upgraded IntelliSpace Perinatal, recover from the
TVBackup of the old client.
This binds the new computer to the settings of the old computer and updates the hostname in the
computer list.
2 IP Addresses:
When using new IP addresses make sure all interface configurations are updated appropriately (e.g.
configuration for HL7 and IntelliSpace Perinatal Link computers, customers’ shortcuts to RD
Session Host Servers, etc).
21.2.2.1 Upgrading the Remote Desktop Session Host server

1 Make sure that Windows is up and running on the Internal Server.
IntelliSpace Perinatal may, but does not need to run.
2 Preparation of the computer
If the new computer shall have the same name as the old computer (see printed installation
record), then rename the newly installed computer now and reboot it. Otherwise, make sure that
the TVBackup of the old computer is available.
a. Go to Control Panel and select the Category view.
b. Click on Programs.
c. Click Install Application on Remote Desktop...
Note that you will not see this selection unless Server 2012 R2 has the Remote Desktop Session
Host role.
d. Click Next.
e. In the field File name type \\<server name>\OBTraceVue\setup\setup.exe
f. If the new computer will keep the old name, select Install the IntelliSpace Perinatal software. If
the new computer will have a new name, select Restore a previously saved IntelliSpace
Perinatal installation (from Backup Tool). Note that the latter choice is not available if
IntelliSpace Perinatal has previously been installed.
Install IntelliSpace Perinatal as described in IntelliSpace Perinatal Setup on page 236 and enter the
settings from the previously printed installation record.
4 Apply the available IntelliSpace Perinatal service packs for this software revision.
Hotfixes. See the IntelliSpace Perinatal Site Preparation and IT Specification Guide. Be sure to use
the method using Control Panel (as described above) for installing IntelliSpace Perinatal (i.e. Install
Application on Remote Desktop...).
6 Select Start whole system in the IntelliSpace Perinatal System Console to start the IntelliSpace
Perinatal application and services. Check that the system starts successfully and then shut it down.
21.2.2.2 Upgrading Clients

1 If this is the installation of the Archive computer, do not activate the IntelliSpace Perinatal services
on the Internal Server. Just make sure that Windows is up and running on the Internal Server.
2 Preparation of the computer
If the new computer will have the same name as the old computer (see printed installation record),
then rename the newly installed computer now and reboot it. Otherwise make sure that the
TVBackup of the old computer is available.
a. Go to Start → Run
b. Type \\<server name>\OBTraceVue\setup\setup.exe
c. If the new computer will keep the old name, select Install the IntelliSpace Perinatal software. If
the new computer will have a new name, select Restore a previously saved IntelliSpace
Perinatal installation (from Backup Tool). Note that the latter choice is not available if
IntelliSpace Perinatal has previously been installed.
Install IntelliSpace Perinatal as described in IntelliSpace Perinatal Setup on page 236 and enter the
settings from the previously printed installation record.
Hotfixes (see the IntelliSpace Perinatal Site Preparation and IT Specification Guide)
Perinatal application and services.
21.2.2.3 Upgrading RD Client

Upgrade every RD client that is configured for Online Monitoring and Alarming following the
procedure described in the IntelliSpace Perinatal Site Preparation and IT Specification Guide.
21.2.2.4 Upgrading Templates

Upgrade customized Word and Excel templates (or install new ones) according to Installing /
Upgrading Word and Excel Templates on page 252.
Continue with Final Steps after Upgrade on page 273.
Upgrading from Rev. K.00 21 Upgrades
21.3 Upgrading from Rev. K.00

The complete installation and setup process for IntelliSpace Perinatal is described in IntelliSpace
Perinatal Setup on page 236.
8SJUDGH2YHUYLHZ
)URP,QWHOOL6SDFH3HULQDWDO5HY.
Customer provided
storage locations
Backup Int-Srv Ext-Srv All other
Shutdown
System
Backup
Backup Backup
3UHSDUH
OS
8SGDWH26 8SGDWH26 8SGDWH26
6\VWHP&KHFN 6\VWHP&KHFN 6\VWHP&KHFN
Upgrade
Setup
Start and activate
Auto Setup Auto Setup
Legend:
Data Startup
Flow
Start Start Start
Process Application Application Application
Flow
21 Upgrades Upgrading from Rev. K.00
21.3.1 Preparation
21.3.1.1 Preparing all computers

Check the revisions of the PC BIOS, RAID BIOS Firmware (if available), and NIC firmware (if
applicable), and update them if required. Please refer to the Readme_BIOS.txt and Readme_Drivers.txt
files located on the ISP Small Architecture Server Drivers and Firmware medium in the appropriate PC
folder. The latest updates are marked with an “*”. The minimum required revisions are also
documented in the PC-specific chapters of this document.
Check the BIOS settings (in PC-specific sections) and adjust them if required. Upgrade iLO firmware
on all high-end servers (this must be done even if iLO will not be used).
21.3.1.2 Preparing IntelliSpace Perinatal

Serial port servers should be switched on and connected to the network while upgrading.
1 Shutdown IntelliSpace Perinatal and run the Local Data Recovery Tool on page 218 to ensure that
the database has no corruption.
2 Use the Backup Tool that is pre-installed on the existing system to backup IntelliSpace Perinatal on
the Internal and External Server and store it in a safe storage location. Note: These backups can be
taken simultaneously on both servers (i.e. internal and external)
3 Use the Backup Tool that is pre-installed on the existing system to backup the Word and Excel
templates (only if available on the Internal Server) and store them in a safe storage location
4 If a new version of the System Check Tool is available, uninstall the existing version.
5 Install the new System Check Tool.
6 Check and prepare the system using the System Check Tool.
Please refer to the chapter System Check in the IntelliSpace Perinatal Site Preparation and IT
Specification Guide for further details.
21.3.2 Upgrading the Internal Server
21.3.2.1 Install IntelliSpace Perinatal

1 As an OS administrator, run IntelliSpace Perinatal setup from the current IntelliSpace Perinatal
software medium :\IntelliSpace Perinatal\setup\setup.exe using the following selections:
• Install IntelliSpace Perinatal software.
• Keep network server selection as it currently is.
• Keep existing database and data files.
• Do NOT delete the existing database and files.
CAUTION If you delete the existing database, all patient data and configuration is lost.

• If you want to change the system language, choose Define System Language.
• Uncheck all check boxes, so that you do not change any settings.
2 Click Finish to reboot the computer, or reboot manually.
21.3.2.2 Final Steps

1 Apply available IntelliSpace Perinatal service packs for this revision.
Perinatal application and services, and backup the internal database.
3 Backup the configuration.
21.3.3 Upgrading the External Server

To start the upgrade process automatically, start the IntelliSpace Perinatal application as an OS
administrator. This automatically starts IntelliSpace Perinatal setup. To apply service packs
automatically (if necessary), start IntelliSpace Perinatal a second time as an OS administrator.
If the Setup does not start automatically, manually upgrade the machine as follows:
• Start the IntelliSpace Perinatal Setup from the Internal Server share:
– Go to Start  Run
– Type \\<server name>\OB TraceVue\setup\setup.exe
– Select Install the IntelliSpace Perinatal software
• Select Network Client
• Do not change any settings.
• Enter the IntelliSpace Perinatal System Key if required.
• Start IntelliSpace Perinatal to apply service pack(s), if necessary.
For further information see “IntelliSpace Perinatal Setup” on page 236.
For upgrade from revision K.00.12 and higher:

When the currently logged-on user is not an OS administrator, the application asks for credentials of
an OS administrator to execute automatic setup or service pack installation.
If the setup failed after the upgrade of the external database:
2 Restore the external database from the backup.
a. Go to Start  Run.
b. Type \\<server name>\OB TraceVue\setup\setup.exe
c. Select Install the IntelliSpace Perinatal software.
4 Select Network Client
5 Do not change any settings.
6 If prompted: Keep the existing external database.
7 Start IntelliSpace Perinatal to apply service pack(s), if necessary.
21.3.4 Upgrading the Remote Desktop Session Host Server Software

To start the upgrade process automatically, start the IntelliSpace Perinatal application on the console of
the Remote Desktop Session Host server as an OS administrator. This automatically starts IntelliSpace
Perinatal setup. To apply service packs automatically (if necessary), start IntelliSpace Perinatal on the
console of the Remote Desktop Session Host server as an OS administrator a second time. Then stop
IntelliSpace Perinatal on the console of the Remote Desktop Session Host server.

Automatic setup or service pack installation can also be started in a remote desktop session. When the
currently logged-on user is not an OS administrator or the application is started in a remote desktop
session, the application asks for credentials of an OS administrator to execute automatic setup or
service pack installation.
21.3.5 Upgrading the Client Software

To start the upgrade process automatically, start the IntelliSpace Perinatal application as an OS
administrator. This automatically starts IntelliSpace Perinatal setup. To apply service packs
automatically (if necessary), start the IntelliSpace Perinatal application a second time as an OS
administrator on the client machine.

When the currently logged-on user is not an OS administrator, the application asks for credentials of
an OS administrator to execute automatic setup or service pack installation.
21.3.6 Upgrading an RD Client with Online Monitoring and Alarming

Upgrade every RD client that is configured for Online Monitoring and Alarming following the
procedure described in the IntelliSpace Perinatal Site Preparation and IT Specification Guide.
21.3.7 Upgrading Templates

Upgrade customized Word and Excel templates (or install new ones) according to Installing /
Upgrading Word and Excel Templates on page 252.
Continue with Final Steps after Upgrade on page 273.
Final Steps after Upgrade 21 Upgrades
21.4 Final Steps after Upgrade

If Moxa Serial Port servers are part of the system, check the firmware and upgrade if necessary and
install drivers (see Installing and Setting up a Serial Port Server on page 92).
Create regular Backups according to a defined backup and recovery strategy (see Backup Tool on page
171).
On all Internal Servers of a linked system, specify the server name and IP addresses of the other
Internal Servers of the link in the System Manager’s Configuration screen, IntelliSpace Perinatal Link
page.
After all IntelliSpace Perinatal / OB TraceVue machines are upgraded, the user account 'OBTV
Internal' on the Internal Server is not used anymore. For security reasons, it is strongly recommended
to manually remove this user account from the Internal Server after the whole system has been
upgraded.
If the system is part of a Link Cluster, run the Link Recovery Tool (see page 171) in repair mode after
all systems have been upgraded.
Make sure together with the customer that the Forms configuration is correct after the upgrade because
in rare cases, parts of the forms configuration might be reset to factory defaults.
Print and backup the configuration record. For more information, refer to Configuration Backup
(Internal Server Only) on page 222.
When upgrading a system with existing Newborn Admission or Discharge Records using BMI
calculation, refer to the IntelliSpace Perinatal System Administration and Configuration Guide, chapter
Configuring Newborn BMI.
HP ProLiant Server only:

If required, install the HP Service Pack for ProLiant (see page 145).
HP Desktop Computers only:

If required, update all drivers that are available in the corresponding folder (rp5800/rp5810) of the ISP
Small Architecture Server Drivers and Firmware medium.
21.4.1 Cleanup Old Hardware

If you have upgraded to new hardware, you must make sure that you delete the contents of the old
hard disk when you have finished upgrading. This is required, as you no longer have software licenses
for the old computer. Rename the computer and change TCP/IP settings.
21 Upgrades Upgrading Word and Excel Templates
21.5 Upgrading Word and Excel Templates

21.5.1 Prerequisites
• IntelliSpace Perinatal must be installed with the External Database option.
• Windows administrator rights
• You must be able to access the templates share (\\<InternalServer>\OBTVTemplates).
• Microsoft Office must be installed and configured on an IntelliSpace Perinatal computer (refer to
the IntelliSpace Perinatal Site Preparation and IT Specification Guide).
21.5.2 Factory Templates and Files

A) ISP setup (standard):
The factory templates and factory files are updated by the IntelliSpace Perinatal system setup. The
handling of the customer templates depends on the setup option:
• Keep current
Leaves template documents in customer directory as is (the customer may need to upgrade
customized templates according to Customized Templates and Files on page 274).
Factory-installed templates can be copied manually from the factory directory at a later time.
To use new factory-provided templates, see Installing Word and Excel Templates on page 110.
• Install new, copy factory templates
Moves all existing template documents to a backup location. Copies new factory templates into the
customer directory.
B) Manual upgrade:
The template revision (including package revision) is not necessarily dependent on the IntelliSpace
Perinatal software revisions. If new templates become available (for example, for download via
InCenter or on distribution media) you can install them without having to re-install IntelliSpace
Perinatal. Follow the Template Upgrade Procedure on page 275.
21.5.3 Customized Templates and Files

If the hospital already has customized Word or Excel templates, only the customized templates may be
upgraded to the current revision. You can also upgrade templates which were customized on another
OB TraceVue / IntelliSpace Perinatal system.
When you upgrade templates, any customization the customer may have made to the template styles
(such as paragraph style, character style, paragraph formatting and so forth) will need to be reapplied.
This is the customer's responsibility.
Customized SQL statements must be manually updated after an upgrade. This is the customer's
responsibility. Refer to the IntelliSpace Perinatal System Administration and Configuration Guide for
further details.
The templates are installed in C:\Tv2_Templates on the Internal Server. This directory is shared as
OBTVTemplates and is accessible from the computer with MS Office installed via
\\<server>\OBTVTemplates. Template backup directories are accessible from a computer with MS
Office \\<server>\C$ installed.
To upgrade customized templates, follow the Template Upgrade Procedure on page 275.
Upgrading Word and Excel Templates 21 Upgrades
21.5.4 Template Upgrade Procedure
21 Upgrades Upgrading Word and Excel Templates
21.5.5 Upgrading Customized Templates and Files

The following single procedure automatically upgrades both Word and Excel templates and the format
of cFormFields.ini and cStatQuery.ini (files storing customized Report Fields and Statistical Queries)
for software revisions prior to the current one.
1 Use the flow chart shown in Template Upgrade Procedure on page 275 to
determine which upgrade procedure to follow. This procedure is the yellow
colored box.
2 On any computer with MS Office installed (see the IntelliSpace Perinatal Site Preparation and IT
Specification Guide), shut down the local IntelliSpace Perinatal application.
3 Log in as Windows administrator.
4 Start Update Document Templates. Execute C:\TV2\prog\TemplUpdate.exe
22
22System Upgrades
22.1 Introduction
This chapter describes how to upgrade an entire IntelliSpace Perinatal system:
• Adding IntelliSpace Perinatal RD Client Licenses
• Adding Remote Desktop Session Host Server
• Adding External Database Server Machine
• Merging or Linking Systems
• Upgrading Small Architecture System to Internal Server
• Upgrading Small Architecture with External DB to Large Architecture
Remember, when you add (or delete) computers you must make a new configuration backup record
and installation record printout.
22.2 Adding IntelliSpace Perinatal RD Client

Licenses
For the maximum number of RD clients supported on a single Remote Desktop Session Host server,
please refer to the IntelliSpace Perinatal Site Preparation and IT Specification Guide. If more clients are
required, additional Remote Desktop Session Host servers must be installed. Additionally, the total
number of clients (Remote Desktop clients and network clients) must not exceed the limits for the
currently used Internal Server hardware.
Customers are responsible for having enough RDS CALS.
22.3 Adding Remote Desktop Session Host Server

For adding a Remote Desktop Session Host server, follow the New System Setup on page 49
instructions for the specific computer type.
If you have more than one Remote Desktop Session Host server, you can use Load Balancing
(described in the IntelliSpace Perinatal Integration Guide) to distribute RD sessions among several
servers.
22 System Upgrades Adding External Database Server Machine
22.4 Adding External Database Server Machine

After the installation of an External Database Server on an existing system you have to restart
IntelliSpace Perinatal on the Internal Server.
22.5 Merging or Linking Systems

22.5.1 Introduction
The following diagram gives an overview of the process for merging or linking systems.
p
(Tasks shown in red imply significant system downtime)
Merging or Linking
Systems
Introduction
Prerequisites
 Upgrade Systems
 Link Recovery Repair
 Update Archive
 Unique System Names
 Single HIS-ID Domain
Merging Linking
Systems Systems
A) Link Directly B) Merge and Link
Cleanup after Go Live
Statistic Reports no
required ?
yes
Merging External
Databases
Done
Merging or Linking Systems 22 System Upgrades
22.5.1.1 Patient Identification

IntelliSpace Perinatal uses different kinds of patient identifiers:
• Internal patient identifier
A new unique internal identifier is created for each patient record. It is not visible in the IntelliSpace
Perinatal user interface.
• HIS-ID
Medical Record Number, Social Security Number or Patient Identification are referred to as HIS ID.
HIS-IDs are used by HL7/HIS systems to identify patients. Only one can be designated as the HIS
ID for the ADT interface.
• Patient Demographics
When searching for a patient record in the Identify/Search Patient screen, demographic data can also
be used to identify a patient.
22.5.1.2 Multiple Admissions

A patient should have exactly one HIS-ID and should be admitted to IntelliSpace Perinatal exactly
once.
However, it is possible to create multiple patient records for the same physical patient
• on a single system (if the HIS-ID is misspelled)
• on linked systems, even if an identical HIS-ID is entered.
• on separate systems.
NOTE A single IntelliSpace Perinatal patient record can be distributed over multiple IntelliSpace Perinatal
systems by transferring the record via IntelliSpace Perinatal Link. It may have different documentations
and episodes on different systems, but is still a single record. The so called Link token ensures that the
record can only be continued on one system. A new episode can only be created on that system, that
currently owns the token.
22.5.1.3 Merging/Linking Systems

When linking or merging previously unrelated systems, multiple patient records with identical HIS-ID
are handled as follows:
• the records are considered to belong to the same physical patient
• the record with the latest episode is enabled
• all other records are disabled
This is required to guarantee uniqueness of HIS-IDs within one single system.
22 System Upgrades Merging or Linking Systems
22.5.1.4 Link Recovery Reports

To identify problems in patient identifiers when linking or merging systems the Link Recovery Tool
creates a list of reports:
Suspicious HIS-IDs
Same HIS-IDs for (Matching demographics but
different records different HIS-IDs)
Patient Record Demographics

(Internal identifier. HIS-ID
“Create Patient” button in (MRN,SSN,PID)
(Last Name, First Name,
Identify/Search screen) MI, DOB)
Suspicious demographics
(Identical HIS-IDs, but different
demographics)
See ...\LinkRecover\LinkRecoverReports.xlsm
22.5.2 Prerequisites (for Merging and for Linking)
22.5.2.1 Upgrade Systems

Upgrade each system to the latest software version separately. Do not create new IntelliSpace Perinatal
links.
See Chapter Upgrades on page 259.
NOTE It is sufficient to upgrade the Internal Server and Archiving Server. Client machines can be upgraded
and used in parallel independent of the merge/link process.
22.5.2.2 Run Link Recovery

Run the Link Recovery Tool separately on each cluster of linked systems.
See Link Recovery Tool for full details of the computers on which the tool should be run.
When you run the Link Recovery Tool:
• Do not select Reporting Only
• Do not skip Repair
Cluster A
System 1 System 2
Cli Cli Cli

Cli
Cli
Cli
SRV2
Cli SRV1
Link
PC Link
PC Cli
Archive
System 3
Example of a new OB TraceVue Link

L System 4 and System 5 are linked to
Example of a merge
System 1 and 2 to combine
System 3 is discontinued S3
cluster A and B to a single cluster
Its data is merged into System 1
Archive
Cluster B
System 4
System 5
S4
S5
L
L
22.5.2.3 Update Archive

On all systems:
• Start IntelliSpace Perinatal at the Internal Server machine, the External Server machine, the HL7
Client machine and at the Document Export computer, if applicable.
• Run c:\tv2\prog\UpdateArchive.exe. When prompted, select Yes to create the required admin
episodes.
This automatically creates, and closes, episodes which IntelliSpace Perinatal requires for internal
administration purposes. It could be rather time consuming. The system can be used while this is
taking place. Performance of some portions of IntelliSpace Perinatal may decrease, such as retrieving,
and reports printing.
Update Archive tool can be stopped safely as soon as it enters the "Waiting for X closed episodes...."
status. In the background, the system automatically archives the closed episodes.
Link and Merge can be done later during a separate downtime of the affected system(s). This allows an
uptime period where necessary manual patient identification cleanup tasks can be made (e.g. systematic
changes of HIS-IDs, correcting misspelled HIS-IDs, …)
22.5.2.4 Unique System Names

Configure unique system names for all affected systems in the System Managers Configuration, page
IntelliSpace Perinatal Link.
Note the previous system names and store in a safe place. They might be requested by the Retrieve
from Archive (RFA Wizard) in the future.
The system name is used in the Link Recovery Tool to configure and identify the systems. It is also
shown in the reports to indicate which system currently has the responsibility for a patient record.
22.5.2.5 Single HIS-ID Domain

HIS-IDs (MRN, SSN or PID) are usually created by a HIS System. The "pool" of the HIS-IDs is called
HIS-ID domain. HIS-IDs created within one HIS-ID domain are unique. Other HIS-ID domains (e.g.
of a different hospital) may use the same HIS-ID for a different patient.
When merging or linking previously unrelated systems it is required that the systems have a single
HIS-ID domain.
A HIS-ID must be unique and refer to exactly one physical patient.
If this is not the case because either of the unrelated systems was using a different HIS-ID domain
containing HIS ID's overlapping with the other system, the HIS-IDs on one of the systems must be
changed:
• Manually using the Patient Administration dialog for closed episodes
• Manually using the demographics form for open episodes
• Automated using HL7 A47 messages.
• Before using A47, Run the Link Recovery Tool and create the report Records without HIS ownership.
This report lists all records, that would not be affected by a A47 message. Verify that the record has
the correct HIS-ID and establish the HIS ownership. HIS ownership can be established using the
Patient Administration dialog (only for closed episodes).
There is no need to handle multiple admissions of the same physical patient with identical HIS-ID at
this point in time. This will be handled automatically by IntelliSpace Perinatal.
Sending an A01 message with IDENTICAL patient demographics will reassign HIS ownership for
open and closed episodes.
22.5.3 Merging Systems

This section describes how to merge two system with Network Based Storage.
Basic approach:
• While the system to be discontinued is still in use, create a snapshot of its archive.
• Merge this snapshot into the newly-upgraded parallel server if the continuing system goes live.
Finally, shut down the discontinued system and merge only the incremental changes. Ask for help
from the factory about details on how to minimize downtime.
22.5.3.1 Preparing All Systems for Merging

1 Run the Link Recovery Tool on a computer that has connections to all Internal Server machines of
all IntelliSpace Perinatal link clusters that will participate in the merge. Include all Internal Server
machines of all the IntelliSpace Perinatal link clusters that will participate in the merge.
• For previously unlinked systems, select Reporting Only.
• For previously linked systems, do not select Reporting Only.
2 Create the report Same HIS-IDs for different records (in LinkRecoverReports.xlsm: Multi_MRN,
Multi_SSN, Multi_PID).
Let a clinical person review the results and correct wrong HIS-IDs in all cases where the same HIS-
ID refers to physically different patients (e.g. misspelled HIS-IDs). To easily change HIS-IDs for
closed episodes, use the IntelliSpace Perinatal Patient Administration Dialog.
For open episodes, this must be done at the demographic forms page.
3 Clinical Preparation for Configuration Merge
Before merging configuration of two systems consider the following: These are tasks for clinical
persons. They can be done in the production system, or, alternatively, in a copy installation or in
already pre-upgraded systems:
• Clarify what care units the final combined system will have.
Merging systems that had no care units yet will now probably require at least one care unit per
system. Important: Make care unit names unique across the systems. Locations can have
identical names as long as they are located in different care units. Assign locations and users to
their care units prior to configuration merge.
• Important: Across the systems, use consistent names for all other configuration items that are
not bound to a care unit. If the settings differ, the name must differ as well. If settings are
identical, the name should also be identical. When in doubt, make the names different. This
way, it is easier to make corrections later because you can still distinguish the configurations.
Examples:
Both systems might have an overview "Nurse Room", but the names must differ because the
configured locations are different. 
Both systems might have a user role "Regular Nurse". If the settings of these two rules are
identical, the names also must be identical. 

This applies to:

- User roles
- General overviews
- PC Default Sets
- Alarm Default Sets 
- Charting Maps
- Charting Elements
- Chalkboard Configuration 
- Print Maps
- App Link Configuration
- Access Point Configuration
• Clarify which system should define the configuration items that exist only once:
Merging a backup from B into the system A sets these configurations to the B values.
If you want to keep the values of A, first create a configuration backup of A.
After merging from backup of B, merge from backup of A again to reset these values.
This applies to:
- System Manager's Configuration (General, Trace Display, Flow Chart, Forms)
- Charting Configuration
- Forms Page Configuration
- Context Synchronization Configuration
• Note that integrated users from a common Active Directory might exist on both systems. If
they are active on both systems, they get their configuration from the backup file merged
latest. If they are inactive on one system only, it is recommended to delete the inactive user on
the other system. Otherwise users might get deactivated and receive their configuration from
the system where they were inactive. Compare Excel-readable user configuration exports to
identify such users.
NOTE There is no need to handle multiple admissions of the same physical patient at this time. During
import, RFA resolves conflicts of all HIS-IDs. If the same MRN or SSN or Patient Identification is
found for another record, the record that has the newest episode will remain unmodified. The other
record gets disabled1 and is later shown with a red cross in the Identify/Search screen.
22.5.3.2 Preparing the Discontinued System

1 On the source system (i.e. the system that will be merged and then discontinued):
a. The list of "Patients received from HIS" will not be merged to the continued system. Review the
list and create or merge Patients as appropriate.
b. Close all open episodes in Maternal, Newborn, and GYN mode (if applicable).
Use Identify/Search screen filter Open Episodes and Open Corrections to find all of them.
c. Run c:\tv2\prog\UpdateArchive.exe. When prompted, select Yes to create the required admin
episodes.
Wait until the tool enters a waiting loop. Make sure it displays 0 open episodes. If not, then
repeat step 1a.
1.Disabled record means that the record cannot have new episodes, but all data is available.
Press Stop and Close to close the tool. Open the IntelliSpace Perinatal System Console and
select Services – Episode Close Process. Make sure all listed computers are running. Refresh the
page until all modules except Deleter display 0 pending episodes.
In rare cases, the numbers might not decrease to 0. This could be due to past recovery
situations. In such cases, keep the offline backup in a safe place and contact your local Philips
support engineer. Shut down the Internal Server machine of the discontinued system. Do not
start it again.
This computer may not be used as Internal Server of the discontinued system any more after that
step.
2 The clients of the discontinued system can be connected to the continued system using
IntelliSpace Perinatal Setup in parallel.
3 If the discontinued system was previously linked to the continued system, remove the discontinued
system from the list of systems in the IntelliSpace Perinatal Link configuration.
22.5.3.3 Merging into the Continued System

1 Shut down IntelliSpace Perinatal at the Internal Server of the continued system.
2 If no links remain, also remove the Link Option as described in Uninstalling IntelliSpace Perinatal
Link on page 253.
3 Preparing the NBS folder of the continued system:
• Prerequisite:
Make sure there is an up-to-date backup of the current NBS
• The NBS folder of both systems may only contain one file:
ID.XML and the following folders:
index\
index.bak\
aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa\
bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb\
cccccccc-cccc-cccc-cccc-cccccccccccc\
(where each a,b,c is a digit or a letter a-f)
• Copy all aaaa, bbbb, cccc, ... folders from the NBS location of the discontinued system to the
NBS location of the continued system.
NOTE Never copy the folders index\ or index.bak\!
It is recommended to perform a full compare of the folders, since episodes with unsuccessfully or
partially copied files cannot be retrieved later.
• Keep the folder index\ on the NBS of the discontinued system. It is used when merging the
archive with the RFA Wizard in the next step.
4 Start Retrieve from Archive (RFA Wizard).
• Select Merge patient data...
• Choose Archive Index located on network path
• Enter the archive location of the discontinued system
• Import all patients

Also refer to Using the RFA Tool on page 224. If you still have linked systems after the merge also
read chapter Merge Patient Data From Another Archive (Archive View-Only Mode) on page 227.
• Check the RFA Report (see below)
5 The Link Recovery Tool must be executed once after the merge.
• Do not select Reporting Only.
• Do not skip Repair.
6 Review c:\tv2\logdata\RFAIntDBReport.txt. See Check the RFA Report. This must be done by a
clinical person
7 The system can go live.
8 Check Merging External Databases on page 289.
NOTE It is now possible to continue documentation for all patients. In case of double admissions, you can
continue with the record that has the newest episode. It is possible to manually re-enable any disabled
records and resolve conflicts later using the Patient Administration dialog.
It is recommended to let a clinical person Check the RFA Report and correct the status of patient
records within several days after the merge where necessary.
22.5.3.4 Check the RFA Report

RFA reports all activities in the log file c:\tv2\logdata\RFAIntDBReport.txt.
• Copy the file contents into an Excel sheet.
• Sort the data by the action performed to see all automatically DISABLED records done by RFA.
• Check if the correct record has been disabled; if not use the Patient Administration dialog to
correct it.
• It is recommended to save the excel file for documentation.
22.5.4 Linking Systems

A network connection between systems to be linked is a prerequisite.
22.5.4.1 Link Methods

There are two ways to establish a link between previously unlinked systems. Deciding which is easier to
implement during upgrade depends on the use model of the previously unlinked systems. To decide,
execute the following:
1 Run the Link Recovery Tool on a computer that has connections to all affected Internal Servers.
• Select Reporting Only.
• Configure all Internal Servers to be linked.
• Create the report Same HIS-IDs for different records.
2 Correct the HIS-ID in all cases where the same HIS-ID refers to physically different patients. Use
the Patient Administration dialog to change HIS-IDs for closed episodes. Use the Demographics
form for open episodes.
Ignore multiple admissions.
3 Run the Link Recovery Tool again.
• Create the report Same HIS-IDs for different records.
It should only show multiple admissions of same physical patients now.
• Is it possible to clean up the multiple admissions manually?
- Yes, cleanups can be done manually
This is the quickest way to establish the new IntelliSpace Perinatal link.
Continue with A) Link Directly:
- No, there are too many multiple admissions
Cleaning up the multiple admissions manually will take longer than the system merge.
Continue with B) Merge and Link:
A) Link Directly:
1 Configure the IntelliSpace Perinatal link between the systems.
2 Run the Link Recovery Tool.
• Do not select Reporting Only.
• Do not skip Repair.
• Configure all Internal Servers.
• Create all reports
3 Cleanup the patient records listed in report Same HIS-IDs for different records.
For each group of identical HIS-IDs the topmost record is the one with the newest episode.
Determine the record, that should be continued and disable all other records using the Patient
Administration dialog on the system that is indicated in the first column (e.g. via IntelliSpace
Perinatal TS client).
4 The system can go live, once you cleaned up all current patient records.
To avoid potential admission conflicts in the future, you should execute the Cleanup after Go-Live
within several days after the new link.
B) Merge and Link:

This alternative merges one of the systems to the other according to the previous chapter.
The linked system is re-installed with an empty internal database. All old patient records reside in one
system after the link. Please note that with Revision E or higher you can easily pull records from one
system to the other for continuation. Therefore, it is not important any more on which of the systems
the record currently resides.
1 Execute the merge process described in Merging Systems on page 283.
2 Install the second system with a new (empty) database and configure IntelliSpace Perinatal Link.
3 The system can go live immediately after the merge process.
22.5.5 Cleanup after Go-Live

To go live it is only necessary to cleanup current patient records. To avoid conflicts in the future it is
recommended to cleanup all patient records within a short period of time after the link.
22.5.5.1 Recommendations
• Use one single MRN for all previous records of a physical patient.
The older records are disabled to protect them from unintended continuation. It is possible to
retrieve, review and print episodes of disabled records.
Change records with HIS-IDs such as DO NOT USE xxx to a disabled record with the correct HIS-ID
and demographic data.
• Use consistent demographics for all records of a physical patient.
This helps when searching for old records of the patient.
To create reports run the Link Recovery Tool on a computer that has connections to all affected
Internal Servers. Configure all affected Internal Servers.
Generate all reports, especially the report Suspicious demographics or HIS-IDs.
The reports cannot detect multiple records that differ in both HIS-ID and demographics. They are
treated as separate patients.
Use Identify/Search screen search capabilities of IntelliSpace Perinatal Administration Tool and the
report AllRecords.txt generated by the Link Recovery Tool to identify these records.
The goal is that all reports finally are empty (except AllRecords of course).
The report Same HIS-IDs for different records is strongly recommended to be empty to avoid
unexpected conflicts in the running IntelliSpace Perinatal system e.g. at night or if the person trying to
admit a patient does not have the skills to resolve the conflict.
The customer might want to have a remaining reviewed list of records (e.g. of test patients) in the
report “Patient records that are disabled on all systems”.
22.5.6 Merging External Databases

N O T Es • Retrieved episodes can be printed normally without merging the external databases.
• A merge of external databases solely makes sense for statistical reports.
• Records of the same patient that were created independently on different systems are interpreted as
two patients by statistics. For example, if a pregnancy was documented in parallel in two records, it
counts twice. However, a pregnancy started on one system, sent over to the other system and
completed there, counts once.
If many patients were documented in parallel on the previously unrelated systems, re-starting with a
new external database instead of a merged database could produce better results.
It is also possible to continue with the external database of the first system without restoring the
external database of the merged system.
To merge external databases, refer to Restoring the External Database on page 227.
Merging external databases can be very time-consuming. It can be postponed to a later downtime of
the system. The statistics will analyze all data of the other system that was restored by RFA “Restore
External Database”.
22 System Upgrades Upgrading Small Architecture System to Internal Server
22.6 Upgrading Small Architecture System to

Internal Server
The following procedures describe how to convert a Small Architecture System to an Internal Server of
a Large Architecture System. Basically, there are two types of upgrades available:
1 Upgrade re-using the existing computer hardware
2 Upgrade to new hardware or virtual machine
In scenario 1, the existing hardware must comply with the new requirements (after the upgrade) of the
Internal Server of the Large Architecture System. For details see the Site Preparation and IT
Specification Guide, Chapter Hardware, IntelliSpace Perinatal Roles and Feature Mapping Tables.
22.6.1 Upgrade Re-using the Existing Computer Hardware
22.6.1.1 Preparation of the Current System

1 If the current system has an HL7/ ADT interface, use the Export Configuration button in the
System Manager's Configuration screen to create a configuration text file and store it in a safe
storage location. You can use the contents of this file to re-configure the HL7 routes in the
IntelliSpace Perinatal application after the upgrade.
2 On the current system, shut down the application (Rev. G) or shut down the system in the System
Console (Rev. H or later).
3 Run the Local Recovery Tool to ensure that the database is intact.
4 Use the Backup Tool to back up the current installation and store it in a safe location.
5 Copy the installation record and store it in a safe location or print it out.
6 If required for the new system, write down the current TCP/IP settings of the NIC and the DHCP
configuration if a local scope exists.
22.6.1.2 Preparation of the New System

Make sure you have backed up the installation and associated files as described above.
The operating system has to be re-installed because it is currently not supported to change the
IntelliSpace Perinatal role using the System Check Tool.
Installing Windows Operating System:

Install a supported operating system according to the IntelliSpace Perinatal Rev. K installation process
(see Windows Installation on page 255). This step includes running the System Check Tool and
correcting all required settings.
The operating system may be provided by the customer. Alternatively, the operating system may be
restored using the OS Restore medium originally provided with the Small Architecture System.
In all cases, it is the customer's responsibility that the new installation of the operating system complies
with Microsoft licensing requirements.
After Windows has been installed successfully, install the appropriate drivers, which are available on the
ISP Small Architecture Server Drivers and Firmware medium.
Upgrading Small Architecture System to Internal Server 22 System Upgrades
HP ProLiant Server only:

Install the HP Service Pack for ProLiant (see HP Service Pack for ProLiant on page 145).

HP Desktop Computers only:
Update all drivers that are available in the corresponding folder (rp5800/rp5810) of the ISP Small
Architecture Server Drivers and Firmware medium.
Check the Computer BIOS rev., RAID controller BIOS rev. and firmware rev. of the NICs and
upgrade them as required. Refer to the Readme_BIOS.txt and Readme_Drivers.txt files located on the
ISP Small Architecture Server Drivers and Firmware medium in the appropriate PC folder. The latest
updates are marked with an "*". The minimum required revisions are also documented in the PC-
specific chapters of this document.
22.6.1.3 Upgrading the Small Architecture System

Installing IntelliSpace Perinatal:
1 Copy the backup files from the safe location to the newly-installed Internal Server.
2 Run IntelliSpace Perinatal setup from the current IntelliSpace Perinatal software medium:
:\IntelliSpace Perinatal\setup\setup.exe, using the following selections:
• Select Restore a previously saved IntelliSpace Perinatal installation (from Backup tool)
• Browse to the backup file or directory
• Select Install IntelliSpace Perinatal Software
• Change the selection from Small Architecture System to Large Architecture System
• Select Recovery restore
• Keep existing database and data files. Do NOT delete the existing database and files.
• Enter the password to get to the System Settings screen

• Do not change the System Settings. If new/additional features are required, run setup again
after the upgrade is completed
• If applicable, adapt the maximum number of Clients and Fetal Monitors
• Define for this PC (enter check mark into check box):
- Port settings
- External interface settings
- IP addresses of remote client servers
• Click Next and adapt the number of fetal monitors and connection types for the Internal
Server of the Large Architecture System. For information on limits, refer to the Site Preparation
and IT Specification Guide, Chapter Hardware, IntelliSpace Perinatal Roles and Feature Mapping
Tables.
• Click Next and assign the available disk drives
• Click Next and configure the password for the OBTV Internal 2 and OBTV Connect users
• Click Next and configure the IP addresses of the Internal Server and the External Server, if
applicable
• Click Next and remove the check mark for HL7 interface / link. In a Large Architecture System,
the HL7 interface cannot reside on the Internal Server.
If applicable, also consider removing the check mark for the Document Export Interface.
While it is basically possible to enable the interface on the Internal Server of a Large Architecture
System, it is recommended to install this role on a client machine that does not host fetal monitors.
The HL7 Interface has to be enabled on another machine in the setup later.
For details about the location of both interfaces, please refer to the Site Preparation and IT
• Click Next to perform the upgrade
• Select Keep the IntelliSpace Perinatal system down and Restart Windows. Click Finish.
3 Install all other machines as required and licensed, and re-enable the HL7 and Document Export
Interface on machines as described above.
Final Steps:
1 Apply the available IntelliSpace Perinatal service packs for this revision.
22.6.2 Upgrade with New Hardware or Virtual Machine
22.6.2.1 Preparation of the New System

This step prepares the new machines for the upgrade. During this step, the existing system can still be
running with its full functionality.
Installing Windows:
On all new machines, install a supported operating system according to the IntelliSpace Perinatal 
Rev. K installation process (see Windows Installation on page 255). This step includes running the
System Check Tool and correcting all required settings.
The operating system and appropriate licensing have to be provided by the customer.
22.6.2.2 Preparation of the Current System

1 If the current system has an HL7/ ADT interface, use the Export Configuration button in the
System Manager's Configuration screen to create a configuration text file and store it in a safe
storage location. You can use the contents of this file to re-configure the HL7 routes in the
IntelliSpace Perinatal application after the upgrade.
2 On the current system, shut down the application (Rev. G) or shut down the system in the System
Console (Rev. H or later).
3 Run the Local Recovery Tool to ensure that the database is intact.
4 Use the Backup Tool to backup to back up the current installation and store it in a safe location.
5 Copy the installation record and store it in a safe location or print it out.
6 If required for the new system, write down the current TCP/IP settings of the NIC and the DHCP
configuration if a local scope exists.
Upgrading Small Architecture System to Internal Server 22 System Upgrades
22.6.2.3 Upgrading the Small Architecture System

Installing IntelliSpace Perinatal:
1 Copy the backup files from the safe location to the newly-installed Internal Server.
2 Run IntelliSpace Perinatal setup from the current IntelliSpace Perinatal software medium:
:\IntelliSpace Perinatal\setup\setup.exe, using the following selections:
• Select Restore a previously saved IntelliSpace Perinatal installation (from Backup tool)
• Browse to the backup file or directory
• Select Install IntelliSpace Perinatal Software
• Change the selection from Small Architecture System to Large Architecture System
• Select Recovery restore
• Keep existing database and data files. Do NOT delete the existing database and files.
• Enter the password to get to the System Settings screen

• Do not change the System Settings. If new/additional features are required, run setup again
after the upgrade is completed
• If applicable, adapt the maximum number of Clients and Fetal Monitors
• Define for this PC (enter check mark into check box):
- Port settings
- External interface settings
- IP addresses of remote client servers
• Click Next and adapt the number of fetal monitors and connection types for the Internal
Server of the Large Architecture System. For information on limits, refer to the Site Preparation
and IT Specification Guide, Chapter Hardware, IntelliSpace Perinatal Roles and Feature Mapping
Tables.
• Click Next and assign the available disk drives
• Click Next and configure the password for the OBTV Internal 2 and OBTV Connect users
• Click Next and configure the IP addresses of the Internal Server and the External Server, if
applicable
• Click Next and remove the check mark for HL7 interface / link. In a Large Architecture System,
the HL7 interface cannot reside on the Internal Server.
If applicable, also consider removing the check mark for the Document Export Interface.
While it is basically possible to enable the interface on the Internal Server of a Large Architecture
System, it is recommended to install this role on a client machine that does not host fetal monitors.
The HL7 Interface has to be enabled on another machine in the setup later.
For details about the location of both interfaces, please refer to the Site Preparation and IT
• Click Next to perform the upgrade
• Select Keep the IntelliSpace Perinatal system down and Restart Windows. Click Finish.
3 Install all other machines as required and licensed, and re-enable the HL7 and Document Export
Interface on machines as described above.
Final Steps:
1 Apply the available IntelliSpace Perinatal service packs for this revision.
22.6.2.4 Cleanup Old Hardware

If you have upgraded to a new Internal Server machine, you must uninstall the Small Architecture
system software after the upgrade. This is required because the old IntelliSpace Perinatal system is no
longer adequately licensed.
If the operating system is re-used, change the host name and the TCP/IP settings.
22.6.3 Final Steps for All Upgrade Scenarios

If Moxa Serial Port servers are part of the system, check the firmware and upgrade if necessary and
install drivers (see Installing and Setting up a Serial Port Server on page 92).
Create regular Backups according to a defined backup and recovery strategy (see Backup Tool on page
171).
Use the Export Configuration button in the System Manager's Configuration screen to create a
configuration text file and store it in a safe location. Copy the Installation Record and store it in the
same place.
Backup the configuration. For more information, refer to Configuration Backup (Internal Server
Only) on page 222.
Upgrading Small Architecture with External DB to Large Architecture 22 System Upgrades
22.7 Upgrading Small Architecture with External

DB to Large Architecture
The upgrade procedure from a Small Architecture with External DB on the same machine to a Large
Architecture with External DB on a separate machine is available for IntelliSpace Perinatal Rev. K.00.10 or
higher. On a Small Architecture system with forms, the external database may reside on the same
machine as the internal database. To upgrade this machine to a Large Architecture system, proceed as
follows:
1 Select Shut down whole system in the IntelliSpace Perinatal System Console on the Small
Architecture machine.
2 Start the Backup Tool on the Small Architecture machine to create an Offline Backup of the
external DB (.zip file). Store the backup in a safe location.
22 System Upgrades Upgrading Small Architecture with External DB to Large Architecture
3 Upgrade the Small Architecture machine to a Large Architecture Internal Server. To do this, start
Setup from the IntelliSpace Perinatal software medium:
:\IntelliSpace Perinatal\Setup\setup.exe and follow the steps to install a Large Architecture Internal
Server (see “Install the IntelliSpace Perinatal Software” on page 238). Accept deletion of external
database.
Keep the system down after Setup!
4 Set up the Large Architecture External Server on a new machine. To do this, start the Setup from
the IntelliSpace Perinatal software medium on the new machine, or on the Internal Server:
:\IntelliSpace Perinatal\Setup\setup.exe
• Do not select Restore..., but New Install...:
• Select Type of IntelliSpace Perinatal System: Network Client PC

• Restore the external database from the previously generated backup (.zip file)
On the Internal Server, select Start whole system in the IntelliSpace Perinatal System Console to start and
activate the system. The system is now ready to run.
23
23XDS Installation
23.1 Overview
This chapters contains a short description how to install and set up the Philips IntelliVue XDS
software for use with IntelliSpace Perinatal. Philips IntelliVue XDS software is used to enable near-
realtime view of Avalon Fetal Monitors in IntelliSpace Perinatal. For more detailed information refer
to the Philips IntelliVue XDS Installation and Configuration Guide.
NOTE If the machine where XDS is installed and the Avalon Fetal Monitors that should be reachable are in
different network segments, a default gateway and appropriate subnet mask have to be entered in the
network settings of the XDS machine and the monitors.
23.2 Initial Configuration

To install XDS, run the Philips IntelliVue XDS Application (BuildXXXX).exe file obtained from the
website http://intellivue.medical.philips.com/xds. Follow the instructions on the screen. At the end of
the installation process, the Initial Configuration Wizard is displayed:
Click Next.
23 XDS Installation Initial Configuration
Select the Profile IntelliSpace Perinatal and click Next.
Make sure that No is selected here and click Next.
Initial Configuration 23 XDS Installation
Make sure that No is selected here and click Next.
From the drop-down list, select the network card that is connected to the subnet containing the fetal
monitors, then click Next.
Click Finish to save the configuration settings and close the Initial Configuration Wizard.
Some more settings are required to complete the configuration. For access to these settings, launch the
XDS Configuration tool (e.g. by clicking on the desktop icon of the IntelliVue XDS Application, then
clicking Advanced -> Configuration, or via Windows Start menu -> All Programs -> Philips ->
IntelliVue XDS Application -> XDS Configuration):
Initial Configuration 23 XDS Installation
On the Remote Display - Window 2 screen:

• Mark the checkbox Enable Window 2.
• Define a Connection Password. The password must be identical to the remote display password
entered at the Avalon fetal monitor.
CAUTION For security purposes the XDS Remote Display factory default password must be changed at
installation.
• Mark the checkbox Show “No Audible Alarms” indicator (see warning below).
WARNING The IntelliVue XDS remote display application is not a primary alarming device. There may be delays
in the data from the monitor. There are no audible alarm indications and no visual alarm indications
apart from those on the screen. If the display on which the remote display is viewed is located outside
of the patient vicinity, it is required that an appropriate mechanism is put into place to provide the
clinical user with audible alarming, for example a remote alarm device or central monitoring system.
If the display on which the remote display is viewed is located outside of the patient vicinity, the user
screen notification "No Audible Alarms" (indicating that there are no audible alarms and that waves
may be delayed) must be configured to "on".
Click Save and close the Configuration Tool.
24
24HP ProLiant DL180 G9

(453564552601)
24.1 Specifications
This chapter refers to the HP ProLiant DL180 G9:
All Configurations:
All HP ProLiant DL180 G9 machines supplied for IntelliSpace Perinatal include:
• Two processors
• Two 10/100/1000 Network adapters onboard
• A RAID Controller, three hot-swap hard disks
• Second hot plug power supply
• One additional P440/4GB RAID Controller with Smart Storage Battery
24.1.1 Removing the Computer Cover

Before working inside the computer, refer to the detailed instructions for removing and replacing the
computer's cover and other items (such as the computer's power supply) given on the:
HP ProLiant DL180 G9 Documentation CD.
24.1.2 Slot Assignments for HP ProLiant DL180 G9
Slots for HP ProLiant DL180 G9:
Accessory Card and Type Slot

Two Network Interfaces Onboard
Display adapter Onboard
RAID Controller Onboard (disabled)
Additional P440 RAID Controller Slot 21
1. Slot 2 is in the middle position (rear view).
24 HP ProLiant DL180 G9 (453564552601) Configuration and Setup Tables
24.2 Configuration and Setup Tables

This section provides configuration and setup tables for HP ProLiant DL180 G9 machines.
To run IntelliSpace Perinatal, your machine must have the correct BIOS version. On the ISP Small
Architecture Server Drivers and Firmware media, use HP Smart Update Manager by starting 
\HP ProLiant\launch_hpsum.bat to upgrade BIOS/firmware/drivers of HP ProLiant hardware.
24.2.1 BIOS Version for HP ProLiant DL180 G9

The required PC BIOS version is U20 v2.30 (09/12/2016) or later.
The required P440 RAID BIOS version is v4.52 or later.
Check the time and date after upgrading the BIOS and adjust if necessary.
When you install a later BIOS/Firmware than specified above, the BIOS / Firmware Update
Verification on page 151 must be executed.
24.2.2 BIOS Settings for HP ProLiant DL180 G9


To view or change a computer's BIOS settings:
1 Power down the computer using its on/off switch.
3 After the self-test, press F9.
4 Select System Configuration and press Enter.
5 Select BIOS/Platform Configuration (RBSU) and press Enter.
6 Follow the on-screen instructions to view and change different screens and settings.
To reset the BIOS settings to the Default Settings:

1 Follow steps 1 through 6 described above (To view or change a computer’s BIOS settings).
2 Select System Default Options and press Enter.
3 Select Restore Default System Settings and press Enter twice, then select Yes, restore the default
settings.
4 Restart the computer.
Only the differences from the default BIOS settings are listed.
Non-Default BIOS Settings for DL180 G9
PCI Device Enable/Disable
Embedded SATA Controller # 1: Dynamic Smart Array Disabled

Slot 2: Smart Array P440 Controller Enabled
Boot Options
Boot Mode Legacy BIOS Mode
Configuration and Setup Tables 24 HP ProLiant DL180 G9 (453564552601)
Network Options
Network Boot Options / Embedded LOM 1 Disabled

System Options
Serial Port Options / Virtual Serial Port Disabled

SATA Controller Options / Embedded SATA Configuration Enable SATA AHCI Support
Virtualization Options / Virtualization Technology Disabled
Server Availability
ASR Timeout 5 Minutes

Wake-On LAN Disabled
Automatic Power-On Always Power On
Date and Time
Date Current Date

Time Current Local Time
Time Zone Unspecified Time Zone
Daylight Savings Time Disabled
Time Format Local Time
24.2.3 RAID Configuration for the HP ProLiant DL180 G9

The following procedure describes the RAID1 configuration before the Windows Server installation.
The RAID configuration procedure is not necessary if you perform a reinstallation on hardware that
already has RAID1 configuration.
24.2.3.1 High-end Systems (Single Server)

Prerequisites
The computer must have at least three hard disks installed (one logical drive). Disk bays 1, 2, and 3
must be used.
Disk bays 4, 5, 6, 7, and 8 are equipped with hard drive blanks.
CAUTION During RAID configuration, all data on the hard disks is erased.
1 During Boot Screen, press F10 Intelligent Provisioning.
2 Select HP Smart Storage Administrator and press Enter.
3 Select (left side) Smart Array P440 (no other controller should be listed).
4 Select Configure and, under Actions, select Create Array.
5 Select SAS HDD Port1l: Box 3: Bay 1 and SAS HDD Port1l: Box 3: Bay 2, then press Create Array.
6 Under Create Logical Drive, select RAID 1, then press Create Logical Drive.
7 Under Create Logical Drive, select Manage Spare Drives, then select SAS HDD Port1l: Box 3: 
Bay 3 and press Save.
8 In the Manage Spare Drives window, press Finish.
9 Exit and Reboot.
10 Continue with Windows Installation on page 255.
RAID Configuration:
Disk Port Port 1I Port 2I

Disk Bay Bay 1 Bay 2 Bay 3 Bay 4 Bay 5 Bay 6 Bay 7 Bay 8
Logical Drive 1 Disk1 Disk2 Disk3 Drive Drive Drive  Drive Drive
Spare blank blank blank blank blank
24.2.4 Interrupt Adjustments for HP ProLiant DL180 G9

All IRQs are auto-assigned. No manual configuration is necessary.
24.2.5 RAID BIOS Settings for HP Proliant DL180 G9

Do NOT change any RAID BIOS settings.
CAUTION If you change the RAID configuration settings, data on the DL180 G9 will be lost.
25
25HP ProLiant DL180 G9

(453564672431)
25.1 Specifications
This chapter refers to the HP ProLiant DL180 G9:
All Configurations:
All HP ProLiant DL180 G9 machines supplied for IntelliSpace Perinatal include:
• One processor
• Two 10/100/1000 Network adapters onboard
• A RAID Controller, three hot-swap hard disks
• One additional P440/2GB RAID Controller with Smart Storage Battery

HP ProLiant DL180 G9 Documentation CD.
25.1.2 Slot Assignments for HP ProLiant DL180 G9
Slots for HP ProLiant DL180 G9:

Two Network Interfaces Onboard
RAID Controller Onboard (disabled)
Additional P440 RAID Controller Slot 21
1. Slot 2 is the slot in the middle position (rear view).

This section provides configuration and setup tables for HP ProLiant DL180 G9 machines.
To run IntelliSpace Perinatal, your machine must have the correct BIOS version. On the ISP Small
Architecture Server Drivers and Firmware media, use HP Smart Update Manager by starting 
\HP ProLiant\launch_hpsum.bat to upgrade BIOS/firmware/drivers of HP ProLiant hardware.
25.2.1 BIOS Version for HP ProLiant DL180 G9

The required P440 RAID BIOS version is v4.52 or later.
25.2.2 BIOS Settings for HP ProLiant DL180 G9



settings.
PCI Device Enable/Disable

Slot 2: Smart Array P440 Controller Enabled
Boot Options
Boot Mode Legacy BIOS Mode
Configuration and Setup Tables 25 HP ProLiant DL180 G9 (453564672431)
Network Options

System Options
Serial Port Options / Virtual Serial Port Disabled

SATA Controller Options / Embedded SATA Configuration Enable SATA AHCI Support
Virtualization Options / Virtualization Technology Disabled
Server Availability

Date and Time
Date Current Date

25.2.3 RAID Configuration for the HP ProLiant DL180 G9


Prerequisites
must be used.
2 Select HP Smart Storage Administrator and press Enter.
3 Select (left side) Smart Array P440 (no other controller should be listed).
5 Select SAS HDD Port1l: Box 3: Bay 1 and SAS HDD Port1l: Box 3: Bay 2, then press Create Array.
7 Under Create Logical Drive, select Manage Spare Drives, then select SAS HDD Port1l: Box 3: 
9 Exit and Reboot.
RAID Configuration:

25.2.4 Interrupt Adjustments for HP ProLiant DL180 G9

25.2.5 RAID BIOS Settings for HP Proliant DL180 G9

26
HPE ProLiant DL360 G10

26
(453564764651,
453564913991, 453564914891)
(453564764651) V1
(453564913991) V2 w/TPM,
(453564914891) V2 w/o TPM for Russia, China etc.
26.1 Specifications
This chapter refers to the HPE ProLiant DL360 G10:
All Configurations:
All HPE ProLiant DL360 G10 machines supplied for IntelliSpace Perinatal include:
• One processor
• Four 10/100/1000 Network adapters onboard
• A RAID Controller HPE SmartArray P408i-aSR, three hot-swap hard disks, and Smart Storage
Battery

HPE ProLiant DL360 G10 Documentation
26.1.2 Slot Assignments for HPE ProLiant DL360 G10
Slots for HPE ProLiant DL360 G10:

Four Network Interfaces Onboard
26 HPE ProLiant DL360 G10 (453564764651, 453564913991, 453564914891) Specifications
Slots for HPE ProLiant DL360 G10:

RAID Controller Onboard
Configuration and Setup Tables 26 HPE ProLiant DL360 G10 (453564764651, 453564913991,
453564914891)

The factory-provided upgrade for BIOS, firmware and drivers depends on the media you have:
a. Small Architecture Drivers and Firmware:
Media was shipped prior to K.00.20. Use HPE Smart Update Manager by starting
\HPE_ProLiant_DL360G10\launch_sum.bat to upgrade BIOS/firmware/drivers of HPE
ProLiant hardware. Additional RAID BIOS for DL360 G10 must be updated manually. To do
this, start \HPE_ProLiant_DL360G10\BIOS\HP SA P408i-a\2.65\cp043370.exe
b. OS Installation for Windows Server 2019:
The media is shipped since Rev. K.00.20. The BIOS, firmware and drivers are updated
automatically after OS installation.
26.2.1 BIOS Version for HPE ProLiant DL360 G10

The required P408i-a RAID BIOS version is v2.65 or later.
26.2.2 BIOS Settings for HPE ProLiant DL360 G10



settings.
26 HPE ProLiant DL360 G10 (453564764651, 453564913991, 453564914891) Configuration and Setup
Tables
System Options
Serial Port Options
Embedded Serial Port Disabled

Virtual Serial Port Disabled
Server Availability

Virtualization Options
Intel (R) Virtualization Technology (Intel VT) Disabled
Boot Options
Boot Mode Legacy BIOS Mode

Recommendation: 
UEFI mode for server
running Windows Server
2019
UEFI Optimized Boot Enabled (for UEFI mode
only)
Server Security
Secure Boot Settings
Attempt Secure Boot Enabled (for UEFI mode

only)
Must be disabled for legacy
BIOS mode
Network Options
Network Boot Options
Embedded LOM 1 Port 1: HPE Ethernet 1GB 4-port......NIC Disabled

Date and Time
Date Current Date

For a new installation, check the Standard Boot Order (IPL).
Configuration and Setup Tables 26 HPE ProLiant DL360 G10 (453564764651, 453564913991,
453564914891)
26.2.3 RAID Configuration for the HPE ProLiant DL360 G10


Prerequisites
must be used.
2 Select Smart Storage Administrator and press Enter.
3 Select (left side) HPE Smart Array P408i-aSR.
5 Select SAS SSD Port1l: Box 1: Bay 1 and SAS SSD Port1l: Box 1: Bay 2, then press Create Array.
7 Under Create Logical Drive, select Manage Spare Drives, then select SAS SSD Port1l: Box 3: 
9 Exit and Reboot.
RAID Configuration:

26.2.4 Interrupt Adjustments for HPE ProLiant DL360 G10

26 HPE ProLiant DL360 G10 (453564764651, 453564913991, 453564914891) Configuration and Setup
Tables
26.2.5 RAID BIOS Settings for HPE Proliant DL360 G10

27
27HP rp5810
27.1 Specifications
This chapter refers to the HP rp5810.
All Configurations:
All HP rp5810 machines supplied for IntelliSpace Perinatal include:
• A sound card onboard.
• A 10/100/1000 BaseT LAN adapter onboard.
Internal Server with Archiving only:

• A second SATA hard disk.

computer's cover and other items (such as the computer's power supply) given in the HP rp5810
Hardware Reference Guide or Maintenance & Service Guide
27.1.2 Slot Assignments for HP rp5810
Slots for HP rp5810:
Accessory Card and Type Slot Number

Network Interface Onboard
Sound Card Onboard
27 HP rp5810 Configuration and Setup Tables

This section provides configuration and setup tables for HP rp5810 machines.
To run IntelliSpace Perinatal, your machine must have the correct BIOS version. You can find the
BIOS and drivers that are needed for re-installation or after upgrades on the ISP Small Architecture
Server Drivers and Firmware medium.
27.2.1 BIOS Version for HP rp5810

The required BIOS version is vA.02.35 or later world-wide except for China and Russia, or vB.02.35
or later for China and Russia.
If you need to update the BIOS:
1 Plug in the Small Architecture Drivers and Firmware USB stick into front USB port.
3 Press ESC while the Press the ESC key for Startup Menu message is displayed at the bottom of the
screen.
4 Press F10 to enter Computer Setup.
5 Under File, select Flash System ROM and press Enter.
6 Select USB and press Enter.
7 Select the appropriate firmware version and press Enter:
L20_A235.bin (world-wide except China and Russia, does allow TPM (Trusted Platform Module),
Embedded Security Device visible in BIOS).
L20_B235.bin (only for Russia and China, Embedded Security Device not visible in BIOS).
8 Press OK to start the BIOS upgrade and follow the instructions.
27.2.2 BIOS Settings for HP rp5810


3 Press ESC while the Press the ESC key for Startup Menu message is displayed at the bottom of the
screen.
4 Press F10 to enter Computer Setup.
To reset the BIOS settings to the default settings:

1 Follow steps 1 through 4 described above (to view or change a computer’s BIOS settings).
2 Select Apply Defaults and Exit. Press Enter and follow the instructions.
Configuration and Setup Tables 27 HP rp5810
27.2.2.1 BIOS Settings


BIOS Settings for HP rp5810:
Storage
Storage Options
Removable Media Boot Disabled
Boot Order
UEFI Boot Sources
USB Floppy/CD Disabled

USB Hard Drive Disabled
Legacy Boot Sources
USB Floppy/CD Disabled

Hard Drive
USB Hard Drive Disabled
Network Controller (IBA GE .....) Disabled
Security
USB Security
Front USB Ports Disabled
Network Boot
Network Boot Disabled
Advanced
Device Options
Num Lock State at power on On
27 HP rp5810 Configuration and Setup Tables
27.2.2.2 SATA Configuration for HP rp5810

The SATA devices are configured as follows:

SATA Device Configuration HP rp5810:
SATA Bus SATA Device

connector
SATA 0 first internal hard disk.
SATA 1 Second internal hard disk (server with archiving only)
28
Fetal Monitor Connections

28
28.1 Overview
IntelliSpace Perinatal accepts the digital signal protocol used by HP/Agilent/Philips Series 50 and
Avalon FM20/FM30/FM40/FM50 Fetal Monitors. Connecting these monitors to IntelliSpace
Perinatal is detailed in New System Setup on page 49. For more information about the digital signal
protocol used, see the Series 50 Fetal Monitors - Digital Interface Specifications Protocol Specifications
Programmer’s Guide (M1350-9074S).
You can connect fetal monitors of other brands to IntelliSpace Perinatal but then they need to comply
with the Philips digital signal protocol.
Responsibility for this compliance lies with that manufacturer. Connection of any third party fetal
monitor is subject to “limited support” and requires integration testing. See the IntelliSpace Perinatal
Integration Guide for further details.
IntelliSpace Perinatal supports only those features that are part of the Series 50/Avalon Fetal Monitor.
If your customer has a monitor that measures parameters other than those measured by Series 50/
Avalon monitors, IntelliSpace Perinatal cannot display them.
28 Fetal Monitor Connections Overview
28.1.1 Available Serial Cables

The following cables are available. Note that cable part numbers are printed on the cables.
Serial Cables:
Monitor Type Option Cabling Replacement Kit Contents

No part number
Series 50 IX/XM/XMO #K12 M1380-61612 453563278111 RS-232 bedside cable

(M1350A/B/C) (with
RS232 interface only) M1380-60612 451261010061 Adapter: Dsub 9 male to RJ45 female
Avalon FM20 / FM30 /

FM40 / FM50
Neoventa STAN S31
Series 50 A/IP  #K13 M1380-61613 453563278121 RS-232 bedside cable

(M1351A/53A)
M1380-60613 451261010071 Adapter: Centronics to RJ45 female
Sonicaid fetal  #K22 M1380-61612 453563278111 RS-232 cable

monitors that only require
an adapter cable. M1380-60612 451261010061 Adapter: Dsub 9 male to RJ45 female
Sonicaid 8001
0510-1334 453563023441 (Velcro) Fastener
1. Typically the Sonicaid 800 does allow a direct connection using the “TraceVue” interface setting
Cable Pin Layout 28 Fetal Monitor Connections
28.2 Cable Pin Layout

28.2.1 Fetal Monitor Cable for M1350A/B/C, 
and Avalon FM 20/30/40/50 M1380-61612
Connection between fetal monitor and computer/wall plate or between converter box and computer/
wall plate.
M1380-61612 Cable for M1350A/B/C and Avalon Fetal Monitors (front view):
9 Pin Female 9 Pin Male
2 3
3 2
5 5
28.2.2 Fetal Monitor Cable for M1351/53 M1380-61613

Connection between fetal monitor M1351/53 and computer/wall plate.
M1380-61613 Cable for M1351/53 Fetal Monitor (front view):
9 Pin Female 24 Pin HPIB
2 9
3 8
5 24
28 Fetal Monitor Connections Cable Pin Layout
28.2.3 Neoventa STAN S31 connector

Connection between Neoventa StAN S31 isolation kit (from Neoventa company) and computer/wall
plate: Use the M1380-61612 and a gender changer (female to female)
Gender changer for STAN S31 Isolation Kit and M1380-61612 Cable (front view):
9 Pin Female 1 9 Pin Female 2
2 3
3 2
5 5
1Index
A M1380-61612 fetal monitor cable for HP rp5810 318
Avalon FM20/30 323 Configuration backup 222
Additional memory 150 M1380-61612 fetal monitor cable for offline backup 223
Admin tool for internal database 174 M1350A/B/C 323
Configuration record
Administrative episodes, update archive PC 39
CONFIG.TXT 147
tool 175 pin assignment fetal monitor cable for
M1350A/B/C 323 printing 75
ADT interface storing 77
pin assignment fetal monitor cable for
setup 240 M1351/53 323 Connect 69
Agilent Series 50 monitors safety 39 Connecting Avalon FMs to IntelliSpace
See Series 50 monitors testing network cables 87 Perinatal 85
Avalon fetal monitor, protocol Cart mount Control Panel 169
conversion 82 moving 80 Conventions
Avalon FM connection 85 power supplies 79 caution 2
Avalon FM20/30 fetal monitors Cat 5 Cable Specification 87 note 2
connecting 81 Centralized implementation 6 warning 2
Changing PC name Customer acceptance procedures 21
B
client 153 Customer verification 147
Backup server 153
configuration 222 D
Checklist
integrating online into task internal server installation 50 Data access
scheduler 181 standalone PC installation 53 software engineering for 3rd party
offline 178, 179 external server installation 53 access 73
online 178 Web/Terminal server installation 55 Data acquisition
Battery client installation (data acquisition) 57, problems 124
replacement in server UPS 139 59
client installation (no data Database
BIOS
acquisition) 61 admin tool for external database 173
Settings
admin tool for internal database 174
HP ProLiant DL180 G9 304, 308, Client
administration tools 173
313 configuring 74
importing data from multiple A.01.xx
HP rp5810 318 defining number of clients during
disks 224
Version setup 241
regular maintenance 139
HP ProLiant DL180 G9 304, 308, installation checklist (data
313 acquisition) 57, 59 Database rebuild tool 176
when to flash 150 installation checklist (no data Database repair
acquisition) 61 archive recovery 220
C UPS 79 patient file validation 219
Cluster, of linked systems 280 validation 219
C drive, see primary hard disk drive 151
Compaq Array Configuration Utility Decentralized implementation 5
Cables
software 231 Defects
length limits 87
100Base-FX 87 Compaq Insight management software 145 hardware 155
100Base-TX 87 Component Installation software media 159
RS-232 87 UPS software 258 DHCP
serial port server 87 Computer Management 169 server configuration 258
Cabling CONFIG.TXT file 147 Display
Specifications 87 Configuration connecting 68
Fetal monitor 39 Hardware 258 Double charting 222
LAN 88 PCs DVD ROM drive
M1380-16613 fetal monitor cable for HP ProLiant DL180 G9 304, 308, installation 150
M1351/53 323 313
4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - i

E HIS-ID domain 282 client (no data acquisition) 61
HL7 Installation record
Earth Terminal symbol 4 setting up 73 install.txt 193
Electrostatic handling precautions 40 Hospital Information System, see HIS IntelliSpace Perinatal
Equipotential Terminal symbol 4 HP Array Configuration Utility configuring at client PCs 76, 77
Error messages software 231 definition 1
RFA 230 HP Insight management software 145 installing the software 238
Event viewer 169 reinstalling 235
HP ProCurve Switch 2312 86
External database starting 76
HP ProCurve Switch 2324 86 tools 173
defining at setup 242
HP ProLiant DL180 G9 PC uninstalling 252
External database admin tool 170 BIOS settings 304, 308, 313 IntelliSpace Perinatal link 240
External database server BIOS version 304, 308, 313 uninstalling 253
installation checklist 53 configuration 304, 308, 313
IntelliSpace Perinatal Setup 236
interrupts 306, 310, 315
F RAID settings 305, 309, 315 IntelliSpace Perinatal, connecting to 13
removing the PC cover 303, 307, 311 Internal database admin tool 174
fetal monitor
slot assignments 303, 307, 311 functionality 174, 176
cabling 39
specifications 303, 307, 311 when to use 170
Fetal monitors
HP rp5810 PC Internal server
cable for M1350A/B/C 323
BIOS settings 318 C drive 151
cable for M1351/53 323
configuration 318 configuring 73
connecting 70, 81
removing the PC cover 317 DVD-ROM drive 150
connecting four monitors 82
specifications 317 how to change PC name 153
connection 297, 321
HP Series 50 monitors installation checklist 50
connection problems 124
M1350A 84 See Series 50 monitors International Caution symbol 4
M1350B 84 Interrupts
I HP ProLiant DL180 G9 306, 310, 315
M1351/53 82
protocol converter kits 322 inspection matrix, see Test and Inspection IP Address
signal protocols 297, 321 matrix serial port server 95
types supported 322 install.txt, see also Installation Record 193 serial port server host PC 93
File Installation Isolation transformer
CONFIG.TXT 147 check shipment 67 connecting 70
RFAWIZ.TXT 229 connect 2nd network card 70 connecting to UPS 68
Flashing connect modem 71 safety when connecting a PC 39
BIOS 150 display 68, 69 with UPS in patient vicinity 7
Floppy disk drive fetal monitors 70
L
unlocking/locking 149 IntelliSpace Perinatal software 238
FMSpy 193 isolation transformer 70 LAN
closing 193 put equipment in place 67 see network
digital interpretation 194 remote client 89 LAN card, see Network I/F card 150
monitor data 194 set timezone and local time 72
Language
port initialization 193 set up IntelliSpace Perinatal to work
with CCOW applications 73 define system language (IntelliSpace
starting 193 Perinatal setup) 246
using 193 set up soundcard 72
software engineering for 3rd party data Limitations
G access 73 RFA tool 223
touchscreen driver 72 Link
GetLog 196 UPS 69 see IntelliSpace Perinatal link
virus protection software 140 Link recovery tool 221
H
voltage selection switch 67 log files 222
Hardware Installation checklist using 221
defects 155 internal server 50 Linking systems 278, 287
installing 79 standalone PC 53 direct link 287
problems 123 external server 53 merge and link 288
replacement parts 155 Web/Terminal server 55 Local Data Recovery tool 218
HIS 47 client (data acquisition) 57 recovery process 218
high-end (data acquisition) 59
4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - ii

using 218 upgrading templates 274 how to rename a server PC 153
Log files Word PC serial number 153
available logs 192 template installation 110 PC system board
GetLog 196 upgrading templates 274 replacement 150
link recovery tool 222 Mobile client Performance monitor 169
local data recovery tool 218 shutting down 80
Performance tests
path 192 Modem LAN FM 25
RFA 229 connecting 71 RS-232 25
tool to collect all available log files multi-disk system 243
(GetLog) 196 RS232 25
software 23
LogFile Viewer 188 N
starting 188 Philips Series 50 monitors
using 188 Network See Series 50 monitors
specifications 86 Port server
M cable specifications 87 see Serial port server
cable testing 87 Port settings
M1350A 84 cabling a LAN 88 defining at setup 242
cable pin assignment 323 connecting 86
Power consumption 7
M1350B 84 connecting 2nd network card 70
cable pin assignment 323 connecting a PC to a switch 88 Primary hard disk drive
connecting the PC to the LAN cable 88 installation 151
M1350C
cable pin assignment 323 errors 121 Printing
examples with 2 switches 88 configuration record 75
M1351
cable pin assignment 323 problems 121 Protocol conversion
serial port server settings 95 overview 82
M1351/53 fetal monitor 82
supported switches 86 Protocol converter
M1353 wall cable types 87 kits available 322
cable pin assignment 323 with switch 86 mounting 82
M1380-16612 Network based storage,
fetal monitor cable for M1350A/B/C troubleshooting 123 R
pin assignment 323
Network I/F card RAID
M1380-16613 installing 150
fetal monitor cable for M1351/53 pin configuration
assignment 323 Network verification 40 HP ProLiant DL180 G9 305, 309,
non-medical devices 315
Maintenance
in patient vicinity 13 HP / Compaq Array Configuration
checking the internal database 139
Utility 231
recommended 139 O Rebuild tool
Management Software
external database 176
HP / Compaq Insight Manager 145 Offline backup tool 171
internal database 176
Manual
P Recommended maintenance, see
organization 1 maintenance
readership 1 Parts 160 Recovery 208, 214, 215, 216
Memory hardware 156 client 216
additional 150 how to obtain replacement parts 160 database recovery 218
Merging systems 278, 283 software media 159 external database server 215
multiple admissions 279 Password internal server with archiving 208
RFA report 286 for change system options during linked systems 221
Merging/linking systems setup 239 local data recovery tool 218
archive update 282 Patient safety 3 server with archiving 208
configuring unique system names 282 PC server with RAID array 206
HIS-ID domain 282 cabling 39 server without archiving 214
link recovery reports 280 HP ProLiant DL180 G9 303, 307, 311 Web terminal server 216
link recovery tool 280 HP rp5810 317 Recovery process 206
patient identification 279 power consumption 7 recovering client’s hard disk 216
prerequisites 280 PC Management Software recovering external server’s hard
Microsoft HP / Compaq Insight 145 disk 215
Excel PC Name 153 recovering server’s backup (secondary)
template installation 110 hard disk 210
how to rename a client PC 153
4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - iii
reinstalling the server 214, 216 site preparation 39 welcome screen 237
Reinstalling visual inspection 22 Setup failure during upgrade 270
IntelliSpace Perinatal 235 when to perform 34 Shell
server (recovery process) 214, 216 safety tests 9 installing IntelliSpace Perinatal
Remote Client power on test 36 shell 251
configure IP address of server 249 visual safety check 36 Single HIS-ID domain 282
installing and configuring 89 SATA configuration Slot assignment
Remote LAN Client HP rp5810 320 HP ProLiant DL180 G9 303, 307, 311
limitations 89 Secondary hard disk Software
prerequisites for installing and recovery after failure 210 media defects 159
configuring 89 Send Note 196 reinstalling IntelliSpace Perinatal 235
Renaming Serial port server 92 Software upgrades
client PC 153 connecting 94 templates 274
server PC 153 device driver 99 Soundcard
Repair 155 example installation 92 setting up 72
Replaceable parts, see Parts 156 host PC 93
Spare PC
RFA tool 223 installation 93
server with RAID 207
checks before running 224 installation documentation
host PC 108 Special tools 2
error messages 230
port server 106 Specification
importing A.01.64 data 227
IntelliSpace Perinatal configuration 103 Network switch 86
limitations 223
log file 229 network settings 95 Specifications 317
merging archive index 227 replacing 105 Cables
re-importing A.02.10 or higher Series 50 monitors 81 100Base-FX 87
data 226 Server CAT-5 87
requirements 223 See internal server 50 RS-232 87
using 224 PCs
Service pack
RS-232 HP ProLiant DL180 G9 303, 307,
IntelliSpace Perinatal 2 311
cable specifications 87 services 129 HP rp5810 317
serial port server connectors 87, 103
Setup Serial port server connectors 103
S advanced alarming 239 SPS
advanced alerting 239 see Serial port server
Safety basic alarming 239 Standalone PC
cabling 39 basic alerting 239 installation checklist 53
electrostatic handling precautions 40 change options screen 239
installation 39 Stocking
change PC options 239
symbols 4 parts 160
configure IP addresses of servers for
safety Remote Clients 249 Storage
tests 9, 36 define alarm sounds 245 setup 240
procedures 10 define alarm symbols 246 Switch
system 12 define system language 246 12 port 86
Safety tests 21 drive settings 242 24 port 86
Audible Alarms 22 external database 242 connecting a PC to a 88
enclosure leakage current/normal external interface settings (for HL7) 245 supported with IntelliSpace Perinatal 86
condition 26 finish 251 Sybase Central 170
enclosure leakage current/single fault found system screen 238 Symbols
condition 26 HL7 detailed configuration 245 earth terminal 4
PC in patient vicinity 25 HL7 interface 240 equipotential terminal 4
PC not in patient vicinity 26 IntelliSpace Perinatal software 236, 237 international caution symbol 4
performance RS-232 25 number of clients 241 safety 4
performance RS232 25 password for change options 239
system
performance serial port server 25 port screen 243
example 13
performance software 23 port settings 242
medical electrical 12
performance tests 22 screens 237
test 12, 36
power on test 22 starting IntelliSpace Perinatal software
setup 236, 237 System description 1, 47, 199
procedures 27
protective earth 34 storage options 240 System linkage 278
4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - iv

System merge 278 system setup 119
System overview 5
U
centralized system 6
decentralized system 5 Uninstall
system test 12, 36 IntelliSpace Perinatal 252
System upgrade 277 IntelliSpace Perinatal link 253
Upgrade
T System
Task scheduler, integrating online adding Web client licenses 277
backup 181 adding Web/Terminal server PC 277
Templates UPS
directory structure 110 client 79
new installation 113 connected to isolation transformer 7
prerequisites 274 in patient vicinity 7
revisions 111 software
installing 258
terminal services and web access, setting
up 78 V
Test and inspection matrix 22
tests Verification
reporting 35 CONFIG.TXT file 147
safety 9, 36 customer 147
system 36 Virus protection 140
visual 9 visual test 9
Toco Voltage selection switch 67
FMSpy 195
token repair methods, repairing patient W
tokens 224
Wall cabling 87
Tools
web access and terminal services, setting
Computer Management 169 up 78
database rebuild tool 176
Web/Terminal Server
Device manager 169
adding 277
FMSpy 193
adding client licenses 277
GetLog 196
installation checklist 55
installation record (install.txt) 193
rebooting 140
IntelliSpace Perinatal tools 173
recovery 216
internal database admin tool 174
LogFile Viewer 188 Windows
offline backup 171 configuration
RFA, restoring the external database 227 DHCP server 258
Windows Control Panel 169 Device Manager 169
Windows disk management 169 Device manager 169
Windows event viewer 169 Disk Management 169
Windows performance monitor 169 Event viewer 169
Windows Services 169 performance monitor 169
Windows standard tools 169 Services 169
Touchscreen
driver 72
Trace Only 240
Troubleshooting 119
application 126
data acquisition 124
fetal monitor connections 124
hardware 123
network 119
network based storage 123
storage 126
4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - v

4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - vi

Isp Isg 453564935121

Uploaded by

Copyright:

Available Formats

Isp Isg 453564935121

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

Isp Isg 453564935121

Uploaded by

Copyright:

Available Formats

In stal la tion a nd S erv ice Gu id e

4535 649 35121

IntelliSpace Perinatal uses ZedGraph.

What is IntelliSpace Perinatal? 1

2 Testing and Maintenance 3

4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - i

4 New System Setup 49

ii - IntelliSpace Perinatal Installation and Service Guide - 4535 649 35121

6 Network Based Storage 115

Networking and System Setup Problems 119

8 IntelliSpace Perinatal Services 129

Services Overview 129

10 System Support 143

Log Files 143

11 Configuration Verification Procedure 147

Customer Verification 147

12 Component Installation (Upgrade/Repair) 149

13 Renaming a Computer 153

Changing a Server Name 153

14 Repairing/Replacing Hardware and Media 155

Repair Strategy 155

iv - IntelliSpace Perinatal Installation and Service Guide - 4535 649 35121

16 Document Export (DOX) 199

17 IntelliSpace Perinatal Repair and Recovery 203

What To Do If... 203

4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - v

18 System Check 233

19 IntelliSpace Perinatal Installation 235

vi - IntelliSpace Perinatal Installation and Service Guide - 4535 649 35121

20 Windows Installation 255

Operating System Installation and Configuration 255

22 System Upgrades 277

23 XDS Installation 297

24 HP ProLiant DL180 G9 (453564552601) 303

25 HP ProLiant DL180 G9 (453564672431) 307

28 Fetal Monitor Connections 321

4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - ix

1.1 What is IntelliSpace Perinatal?

1.2 Who Should Read This Guide

1.3 About This Guide

4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - 1

1.4 Special Tools

1.5 Service Packs

1.6 Conventions in This Document

1.7 Sterilization and Cleaning

2 - IntelliSpace Perinatal Installation and Service Guide - 4535 649 35121

2Testing and Maintenance

4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - 3

2.2 Terminology and Definitions

2.3 Recommended Frequency

2.4 Symbol Identification

Resistance Measuring Device

Follow the Instructions for Use

4 - IntelliSpace Perinatal Installation and Service Guide - 4535 649 35121

2.5 System Overview

Figure 1 System Overview, Office (without isolation transformer)

4535 649 35121 - IntelliSpace Perinatal Installation and Service Guide - 5

2.5.2 Decentralized System

Figure 2 System Overview, Bedside (with isolation transformer)