Installation Guide Rev G - IBE Rel B.08.PDF Nodeid 15604638&vernum - 2

Healthcare, Interoperability & Standards
Installation Guide
IntelliBridge Enterprise (IBE) B.08
PHILIPS
453564589121
PRINTED IN THE U.S.A
OCTOBER 2017
REVISION G
IBE B.08 Installation Guide

WARNING: THIS PAGE CONTAINS COPYRIGHTED MATERIALS THAT ARE CONFIDENTIAL AND/OR PROPRIETARY. ANY RELEASE OR DISTRIBUTION OF THIS MATERIAL,
WITHOUT PERMISSION, IS A VIOLATION OF LAW.
Copyright © 2017 Koninklijke Philips N.V. All rights reserved
TABLE OF CONTENTS
1 INTRODUCTION AND TECHNICAL INFORMATION................................................................................. 6

1.1 Document History ......................................................................................................................................... 6
1.2 Product Overview ......................................................................................................................................... 7
1.3 Product Release Cycle ................................................................................................................................. 9
1.4 What is included in the Installation Guide? .................................................................................................. 9
1.5 Communication with Philips Healthcare ..................................................................................................... 10
1.5.1 Support Handling and Escalation Procedure ..................................................................................... 10
1.5.2 Problem Reporting ............................................................................................................................. 10
1.6 Manual Conventions .................................................................................................................................. 11
1.6.1 Symbols and Characters .................................................................................................................... 11
1.6.2 Glossary: General Terminology and Abbreviations ........................................................................... 11
2 PRE-INSTALLATION REQUIREMENTS................................................................................................... 12
2.1 Passwords procurement before installation ............................................................................................... 13
3 PROCURE ORION RHAPSODY LICENSE ................................................................................................ 14
3.1 IBE Version - Orion Rhapsody Version - HIF Version ............................................................................... 17
4 OPERATING SYSTEM............................................................................................................................ 18
5 CONFIGURE THE WINDOWS LOCATION AND WINDOWS KEYBOARD SETTING.................................. 19
6 SOFTWARE INSTALLATION .................................................................................................................. 20
6.1 Install .NET Framework .............................................................................................................................. 22
6.1.1 Prerequisite ........................................................................................................................................ 22
6.1.2 .NET 3.5 SP1 Framework .................................................................................................................. 25
6.1.3 .NET 4.5.2 Framework ....................................................................................................................... 26
6.2 Install Microsoft SQL Server ...................................................................................................................... 28
6.2.1 Install MS SQL Server 2014 ............................................................................................................... 28
6.2.2 Check SQL Server Service Pack Installation ..................................................................................... 32
6.2.3 Configuration steps ............................................................................................................................ 34
6.3 Install and Configure Acrobat Reader ........................................................................................................ 36
6.4 Install Orion Rhapsody ............................................................................................................................... 38
6.4.1 Port availability check ......................................................................................................................... 38
6.4.2 Install Rhapsody Integration Engine .................................................................................................. 40
6.4.3 Install Rhapsody IDE Application ....................................................................................................... 47
6.4.4 Apply Rhapsody License .................................................................................................................... 49
6.4.5 Add users for Rhapsody ..................................................................................................................... 56
6.4.6 Lockers and Groups ........................................................................................................................... 59
6.4.7 Password Policy Management ........................................................................................................... 67
6.4.8 Exponential Back--off on Authentication Failures .............................................................................. 68
Rev G IBE B.08 Installation Guide 2 of 223
6.4.9 Disable SSLv2, SSlv3, TLS1.0 on Web Server ........................................................................................ 70
6.5 Install and Configure IIS ............................................................................................................................. 71
6.5.1 Register ASP.NET to Web Server (IIS).............................................................................................. 73
7 Install and Configure IBE Server .......................................................................................................... 74
7.1 IBE Release Zip Overview ......................................................................................................................... 74
7.1.1 IBE SIS Installer ................................................................................................................................. 76
7.1.2 Rhapsody Files................................................................................................................................... 78
7.1.3 PSA .................................................................................................................................................... 79
7.2 Installation .................................................................................................................................................. 80
7.2.1 Pre-install check ................................................................................................................................. 80
7.2.2 Installing IBE ...................................................................................................................................... 83
7.2.3 Installing HIF ...................................................................................................................................... 86
7.2.4 Post-install check ............................................................................................................................... 95
7.2.5 Configuring HIF .................................................................................................................................. 97
7.2.6 Configuring IBE .................................................................................................................................. 99
7.2.7 Add/Remove features ...................................................................................................................... 117
7.2.8 Configuration information ................................................................................................................. 120
7.3 Uninstallation ............................................................................................................................................ 121
7.3.1 Uninstalling IBE ................................................................................................................................ 121
7.3.2 Uninstalling HIF ................................................................................................................................ 121
8 System Check and Backup................................................................................................................. 122
8.1 Post Installation Verification ..................................................................................................................... 122
8.1.1 Operating System............................................................................................................................. 122
8.1.2 IBE Support User ............................................................................................................................. 122
8.1.3 Dot Net 3.5 SP1 and 4.5.2 frameworks ........................................................................................... 122
8.1.4 IIS 8 .................................................................................................................................................. 122
8.1.5 MS SQL Server ................................................................................................................................ 122
8.1.6 Orion Rhapsody ............................................................................................................................... 122
8.1.7 HIF .................................................................................................................................................... 122
8.1.8 CartGateway .................................................................................................................................... 123
8.1.9 PSA .................................................................................................................................................. 124
8.1.10 ADT Reporter ................................................................................................................................... 124
8.1.11 Order Reporter ................................................................................................................................. 124
8.1.12 IECG (required Registry settings) .................................................................................................... 125
8.2 System Checks ........................................................................................................................................ 127
8.3 System Backup and Final Settings .......................................................................................................... 127
8.4 Rhapsody Integration Engine Startup/Shutdown ..................................................................................... 128
8.5 IBE Clean Shutdown on Windows Restart ............................................................................................... 132
8.5.1 Introduction ....................................................................................................................................... 132
8.5.2 Solution ............................................................................................................................................ 133
9 Upgrade Model ................................................................................................................................. 135
9.1 Upgrade Paths ......................................................................................................................................... 138
10 Migration Instructions ...................................................................................................................... 139
10.1 Migration from earlier versions of IBE to B.08 ......................................................................................... 139
10.1.1 Pre migration site preparation .......................................................................................................... 139
10.1.2 Pre migration check on IBE Box ...................................................................................................... 139
10.1.3 Database Migration .......................................................................................................................... 140
10.1.4 Rhapsody RLC Migration ................................................................................................................. 149
10.1.5 Post Migration check ........................................................................................................................ 161
10.2 Upgrade from Rhapsody 4.1.x/6.2.1 to 6.2.2 ........................................................................................... 162
11 PSA .................................................................................................................................................... 165
11.1 Philips Service Agent (PSA)..................................................................................................................... 165
11.1.1 PSA Solution Installation – Start ...................................................................................................... 165
11.1.2 Log File ............................................................................................................................................. 170
11.1.3 Check in PRS Portal ........................................................................................................................ 170
11.2 Remote Monitoring ................................................................................................................................... 172
11.2.1 Pattern Configuring in PSA .............................................................................................................. 172
11.2.2 Alarm and Rule Configuration in PRS Device Type Management .................................................. 176
11.2.3 Configuring alerts action (Email Configuration) ............................................................................... 178
11.3 Configuring PCCI PSA Solution Installer with the “IPSEC VPN” Connection Type ................................. 179
11.3.1 PSA Solution Installer with the “IPSEC VPN” Connection Type for QA Environment ..................... 179
11.3.2 PSA Solution Installer with the “IPSEC VPN” Connection Type for Production Environment ......... 186
11.4 Remote Monitoring – Configuring Notification to write logs ..................................................................... 191
12 Appendices ........................................................................................................................................ 196
12.1 Troubleshooting FAQs ............................................................................................................................. 196
12.1.1 MS SQL Server ................................................................................................................................ 196
12.1.2 Performance issue and Memory Leak – SQL Server 2008 R2 ........................................................ 198
12.1.3 Rhapsody Server and MCAFEE ...................................................................................................... 199
12.1.4 IBE .................................................................................................................................................... 199
12.1.5 HIF .................................................................................................................................................... 200
12.1.6 Rhapsody ......................................................................................................................................... 203
12.1.7 Enabling CartGateway with .Net 4.5.2 ............................................................................................. 204
12.1.8 Font installation for Barcode in Xcelera/ISCV PDF report ............................................................... 205
12.1.9 Port conflict between JVM port and Xcelera ADT/ORU port ........................................................... 206
12.1.10 Data migration from B.02 to B.07 and above ............................................................................... 208
12.1.11 Rhapsody Management Console browser ................................................................................... 209
12.2 DICOM Manager Service Manual Installation .......................................................................................... 210
12.2.1 Objective .......................................................................................................................................... 210
12.2.2 Steps to Uninstall and Install DICOM Manager Service from Command Prompt ............................ 210
12.3 Microsoft Security Patch Deployment Steps ............................................................................................ 213
12.3.1 Objective .......................................................................................................................................... 213
12.3.2 Steps to deploy MS Security Patch on IBE Server .......................................................................... 213
12.4 PSA .......................................................................................................................................................... 217
12.4.1 Background ...................................................................................................................................... 217
12.4.2 Resolution ........................................................................................................................................ 218
12.4.3 Attended Installation Mode ............................................................................................................... 219
12.4.4 Unattended Installation Mode .......................................................................................................... 222
12.4.5 Post Installation Checks and Troubleshooting ................................................................................. 223

1 INTRODUCTION AND TECHNICAL INFORMATION
1.1 Document History

Revision Revision Date Reason of changes
A 2015-07-31 First issue for IntelliBridge Enterprise B.04
B 2016-03-29 First issue for IntelliBridge Enterprise B.05
C 2016-09-30 First issue for IntelliBridge Enterprise B.06
D 2017-03-31 First issue for IntelliBridge Enterprise B.07
E 2017-05-25 Second issue for IntelliBridge Enterprise B.07
F 2017-06-25 First issue for IntelliBridge Enterprise B.07.01
G 2017-10-31 First issue for IntelliBridge Enterprise B.08

1.2 Product Overview
Philips IntelliBridge Enterprise (IBE) is the “One Pipe” PCMS interoperability solution that enables interoperability
between Philips solutions in our customers’ environment with a hospital’s information systems (i.e. HIS, EMR, LIS).
IBE provides a single, standards-based point of interoperability between Philips clinical systems and enterprise
information systems while reducing complexity and cost in the healthcare environment. IntelliBridge Enterprise can
also be used to connect with other information systems such as those associated with comparative effectiveness
research. The below Figure 1.2.1 describes basic overview of IBE server.
Figure-1.2.1: Philips IntelliBridge Enterprise Overview
The Figure 1.2.1 shows Philips products interoperating with Hospital external systems through IBE. Each component
shown in Figure 1.2.1 is described below:
 Philips Products: This can be one or more Philips products/product portfolios that are supported on the
IBE.
 Hospital External Systems: All external systems that Philips products/product portfolios interoperate with.
Examples: HIS, EMR, CPOE, LIS etc.
 Philips Shared Staging Service: This is a software component that is shared between Philips client
applications/systems to provide a single service for processing patient demographics, order information and
lab information when interfacing to Hospital Information Systems (HIS). Example: HIF (Healthcare
Integration Foundation) / PI (Patient Index) is a shared staging service across all client application/systems
requiring Patient Demographics from EMR system.
 Microsoft SQL Server: This is used to host the databases and its components required for IBE and
subsidiary components such as HIF

 IIS: IIS is required to host web based applications and modules within IBE. Example: Alert Viewer
application.
 Orion Rhapsody Interface Integration Engine: This is the Interface Engine used to build the interfaces
between each Philips product and corresponding Hospital External System.
 Philips Single Pipe and Product Profiles: Every product has its product specific profile using standard
messaging protocols and application specific messaging formats. These profiles are built on top of Orion
Rhapsody Interface Integration Engine.
 Philips Product Extensions: These are the existing interfaces and interface features that are consumed in
IBE when the products/product portfolios are adopted. Example: Agilink, Surelink etc.
 Services: There are several system level services required for IBE to function. These services run under
the administrator account on the operating system. Example: HIF service, PSA service, PIC iX ICIP service
etc.
 Configuration/Tools: IBE consists of configuration tools and other tools that help in IBE deployment,
maintenance and monitoring. Below are the most commonly used tools:
o IBE Configuration Wizard: This is a UI based windows application that helps in installing and
configuring IBE database and service components.
o Audit Trail: This is a UI based application that allows viewing the user/product based Audit
information of the interface engine. This provides information on user logins and modifications to the
interface integration engine components.
o PSA: PSA allows network connectivity to Client systems from Philips network for Support and
Administration.
o Alert Viewer: This is a web based application that allows viewing any exceptions in the message
transfer related to particular features like Device Data in IBS, IIC, IICiX, IP5 and SSPM products.
o Rhapsody Lookup table and variables migration tool: Support for migration of values in Rhapsody
Lookup table and variables

1.3 Product Release Cycle
Installation:
Details of the installation procedures are found in the Installation Guide ~ this manual.
On-site Configuration:
Site/environment preparedness is to be completed by Field Service Engineer along with Hospital IT staff to check
the system, configure and customize it for local conditions, perform a set of test runs in the presence of the customer,
and create a final Drive Image backup. Details of the procedures used are found in the Implementation Guide.
Interface Solution information:

The Solution Guide helps in understanding the details of the solutions offered in IBE to various stakeholders of the
software. The guide could aid in the pre-sales, post-sales discussions and during the development of solution
proposals for the customer.
1.4 What is included in the Installation Guide?

This manual includes the following:
 The installation process of an entire system including all specific hardware and software such that a basic
working system is available to commence local configuration and verification based on Windows Server 2012
R2 x64 server.
The Operating System (OS) installation is carried out by either Hospital IT or local vendors.
 Standard default settings and values as tested for performance and robustness
 Installation of recommended Software Packages (e.g. IIS, SQL Server, Acrobat Reader, Remote Services)
This manual does NOT describe the following:

 Installation of locally purchased recommended and/or approved 3 Party software (e.g. MS Office, McAfee Virus
rd
Scan) – refer to the Knowledge Base (KBS or Knova)

 Configuration relevant to actual interface settings – refer to the Implementation Guide(s)
 Connection with licensed modalities – refer to the Implementation Guide
 Solution specific configuration information – refer to the Implementation Guide
 Interface Solution information – refer to Solution Guide

1.5 Communication with Philips Healthcare
1.5.1 Support Handling and Escalation Procedure
Please refer to IBE CSPP (Customer Services Product Plan) document for details.
1.5.2 Problem Reporting

In cases where IBE support team needs to be approached for events with the system attributing to an error, this
problem should be reported to IBE Support via E-mail ibesupport@philips.com with clear problem description,
relevant configuration information, software release identification etc.
To facilitate rapid processing of the Field Problem Report, the following should be sent with the Field Problem Report:
A copy of the IBE error-log-files, screenshots, if available and System configuration. Use the Rhapsody Console or
Utility folders to collect these files.
Any feedback on documentation can be sent to ibesupport@philips.com
Please note that IBE Support team mail id is for internal use only and should not be shared with customer.
CAUTION
Any information containing ePHI must be de-identified before sending it to support.

1.6 Manual Conventions
1.6.1 Symbols and Characters
The following Symbols and Characters will apply throughout this manual:
Example(s) Explanation
Esc Keys on the keyboard – press indicated key to perform
action
Proceed with installation… General informative or instructional message
cardio, D:\MSSQL, John Smith Information which appears on the screen
C:\WINNT\System32… Information you enter (type) using the keyboard
Menu or pull-down list items in sequence to be
Start > Programs > …
followed
Application buttons on the screen – use mouse to
Cancel activate
 Insert CD
 Wait for the period shown in the instructions
Explanation of information with a direct bearing on
NOTE
current procedures
Explanation of potential system-wide or process
CAUTION specific problems or difficulties which may result if
certain steps are not followed
Explanation of potential system-wide or process
WARNING specific hazards, or safety risk problems which may
result if certain steps are not followed
1.6.2 Glossary: General Terminology and Abbreviations

Term/Abbreviation Explanation Purpose
Archive Offline data security storage Secure data copy independent of system functionality (e.g.
tape, DVD, MO, etc.)
Autorun Automated Executable process Starts program from specific location without user input (e.g.
from a CD)
Backup Local/Remote copy of data Partial/full data copy maintained locally (e.g. tape, CD, hard
disk, etc.)
CD (-R/-RW) Compact Disk (wRite/ReWrite) Media used for System Installation and Study storage
DNS Domain Name System An Internet service that translates domain names into IP
addresses
DOS Microsoft® Disk Operating System Operating System (16 bit)
DVD-R Digital Versatile Disk -wRite Media used as Archive option
IIS Internet Information Server Microsoft Web Server software
NTFS New Technology File System Disk partition format type used by Windows 2000 OS
OS Operating System Front-end user application for simplifying computer tasks
Partition Hard Disk Partition NTFS Formatted hard disk area assigned a drive letter
SQL Structured Query Language Fourth Generation database programming Language (4GL)
SQL Server SQL Administration Application MS application installed on Intellispace CardioVascular Server;
includes database management functionality
Win 2008 Microsoft® Windows 2008 R2 Server Operating System type (64 bit)
TTS Transition To Support TTS is used by Remote Support Engineers for Production
Support

2 PRE-INSTALLATION REQUIREMENTS
IBE can be installed on a Physical server or on a VMware ESXi 5.0 (or later) virtual machine. The hardware and
software requirements are detailed in the IBE IT Specification. We recommend having 2 servers setup – one for
Production and the other for Test. This section details out the IBE installation.
Checkpoints
 Both hardware and software requirements (as specified in IBE IT Specification) should be met.
 The hardware should be up and running. Basic system configurations should be completed.
 IBE server should be an independent box and should not be shared with other products.
This part is performed by customer IT personnel or by Philips as a service by the service team on behalf of the
customer, only if contracted to do so.
 Install and configure the Operating System per requirements stated in the IBE IT Specification guide
 Create Administrator level user with all necessary read/write/execute permissions on the local server for
installation
 Download MS SQL software as per requirements stated in IBE IT specification guide
 Install supporting applications IIS, .NET 3.5 SP1 and .NET 4.5.2
NOTE
The operating system, SQL Server and virtual machine are not part of IBE software package
but purchased by customer. The installation/configuration/maintenance details of the same are
out of scope of this guide except SQL Server.
This part is performed by Philips IT personnel.
 Procure Orion Rhapsody license

 Orion Rhapsody Installation
 Downloading the IBE Release zip with the latest release of IBE software
 IBE Installation and configuration
Installation Responsibilities
IBE installation is performed by a combination of customer IT Personnel and Philips Technical Personnel.
Customer IT Responsibilities Philips Responsibilities

System hardware, virtual machine, memory and MS SQL installation and configuration. Can be
related installation. Customer IT task, sometime Philips performs this
task
Operating system installation and configuration. Orion Rhapsody installation including engine, IDE
and license.
Windows user creation with admin permissions IBE installation & configuration including
and necessary access privileges. interfaces and PSA.
Supporting application installation, including IIS Migration/Upgrade of IBE, if needed.
and .NET 3.5 SP1 and .NET 4.5.2 runtime
environments.

2.1 Passwords procurement before installation
Please procure below passwords from IBE Support via E-mail ibesupport@philips.com
1. Rhapsody default
2. IBE default
3. HIF SupportUser

3 PROCURE ORION RHAPSODY LICENSE
This process refers to ordering licenses for the IntelliBridge Enterprise solution.
Before going to the Orion License site:
1. Field places Customer Order in Field Client MP1 or a similar system, with the option and quantity.
2. The Sales Order is transferred into factory MCP.
3. The factory turns the Sales Order into a Production Order, and releases to Production.
4. This Production Order triggers lower level BOM item (the License), and causes the buyer to place PO with
Orion, referencing the SSD number.
5. Production makes the Orion Label, processes and ships the production order.
6. Production sends an email to the predefined field addresses. All certificates go to all pre-defined mailboxes:
CIS-I@philips.com (GSSI),
CMSITPS@philips.com (NA),
NCCsupport@philips.com (Sure Signs),
GICC@philips.com (EMEA and APAC/Xcelera/ISCV) and
dl_DECG_IBE_Activate@philips.com (NA DECG)
7. The service organization checks their mailbox for the “license to use” certificate and when received can go
to the Orion webpage to make the request for the license
Ordering the Production/Test license:
For COE PCMS International, please send your Orion Rhapsody License requests to: CIS-I@philips.com
For EMEA and APAC Xcelera\ISCV, please send your Orion Rhapsody License requests to: GICC@philips.com
For all others (Americas), please use the Orion IBE Licensing web site to place your request using the web
forms. The URL is: https://orionhealth.com/philips-license-request The current username and password can be
obtained by sending a request to ibesupport@philips.com If for any reason you cannot access the web site due to
network issues or system down, please send your Orion Rhapsody License requests to:
ibesupport@philips.com with the information listed in the table below
Ordering the Non-Production (Demo) license:
All requests for Non-Production licenses should be directly sent to ibesupport@philips.com with the information
listed in the table below.

If you have any questions, please send a message to: ibesupport@philips.com
License file will be emailed to the Email address entered in the form.

Figure: Orion License information displayed
CAUTION
Orion Rhapsody PROD license should be installed within 90 days of procurement.
If not installed, the PROD license shall expire post 90 days.
Orion Rhapsody NON-PROD license should be installed within 30 days of procurement.
If not installed, the NON-PROD license shall expire post 30 days.

3.1 IBE Version - Orion Rhapsody Version - HIF Version
IBE Version Orion Rhapsody Version HIF Version CCP Version
A.00 4.0 Not Applicable Not Applicable
A.01 4.1 Not Applicable Not Applicable
A.02 4.1 A.00 Not Applicable
A.03 4.1 A.00 Not Applicable
A.04 4.1 B.00.00.12 Not Applicable
A.04.01 4.1 B.00.00.13 Not Applicable
B.00 4.1 B.00.01.3 Not Applicable
B.01 4.1.1 (with MSMQ HotFix) B.00.01.3 Not Applicable
B.01.02 4.1.1 (with MSMQ HotFix) B.00.01.3 Not Applicable
B.02 4.1.1 (with MSMQ HotFix) B.00.01.3 Not Applicable
B.03.01 4.1.4 B.02 Not Applicable
B.02.01 4.1.4 B.02 Not Applicable
B.04 4.1.4 Not Applicable A.0
B.05 4.1.4 C.0 Not Applicable
B.07.01 6.2.2 C.0 Not Applicable

4 OPERATING SYSTEM
The Operating System (OS) installation is carried out by either Hospital IT or local vendors. Please choose default
settings while installing the OS.
IBE IT Specification Guide provides more information on the software versions.

5 CONFIGURE THE WINDOWS LOCATION AND WINDOWS KEYBOARD
SETTING
By default, there will be an English (US) keyboard installed. However, some customer will prefer a different keyboard.
For those customers it is possible to change the keyboard setting or add a keyboard so it will be possible to switch
between keyboards.
1.  Select Start > Control Panel, Clock, Language, and Region

2.  Select Region > Change Location
3. On the Location tab under Home location: select the Current location: (default is United States)
4. Press  Apply and / or  OK to close window
5.  Select Language > Add a language
6. English (United States) is the default selection.  Click Options > Click  Add an input method
7.  Select the desired keyboard input method option and  click Add…
8.  Click Save to save the changes

6 SOFTWARE INSTALLATION
The Software Installation section includes the installation of all 3rd Party software required by the system. After
installation, proceed to IBE Implementation Guide for product interface configuration in Rhapsody.
WARNING
Software Packages that are not specifically required and/or approved
should NOT be installed on the IntelliBridge Enterprise system
Failure to comply with this requirement may lead to performance degradation or even data loss
Use Figure 6.1: IBE System Setup Installation Flowchart for IBE System Setup

Figure 6.1: IBE System Setup Installation Flowchart

6.1 Install .NET Framework
.NET 3.5 SP1 and .NET 4.5.2 are required for IBE installation. Other .NET versions may not be compatible.
NOTE
Internet Connectivity and Windows updates should be enabled for .NET Framework
installation
6.1.1 Prerequisite
Open the Local Group Policy Editor
You can open the Local Group Policy Editor by using the command line or by using the Microsoft Management
Console (MMC).
To open the Local Group Policy, at a command prompt or in Search, type gpedit.msc, and then click OK or press
ENTER.
To open the Local Group Policy Editor as an MMC snap-in
1. Search for MMC, and then press ENTER.
2. On the File menu, click Add/Remove Snap-in.
3. In the Add or Remove Snap-ins dialog box, click Local Group Policy Editor, and then click Add.
4. In the Select Group Policy Object dialog box, click Browse.
5. Click This computer to edit the Local Group Policy object, or click Users to edit Administrator, Non-
Administrator, or per-user Local Group Policy objects.
6. Click Finish, click Close, and then click OK. The Local Group Policy Editor opens the Group Policy object
(GPO) for you to edit.
Windows has to download the 3.5 installation files, but the server is configured not to use Windows Update
(common for managed servers), but WSUS.
1. Start the Local Group Policy Editor or Group Policy Management Console.
2. Expand Computer Configuration, expand Administrative Templates, and then select System.

3. Open the Specify settings for optional component installation and component repair Group Policy
setting, and then select Enabled.
4. Select the Contact Windows Update directly to download repair content instead of Windows Server
Update Services (WSUS) check box
5. Click Apply and OK to save.

In Internet Explorer, go to:
Tools (gear wheel) > Internet Options > Security > Internet > Custom Level > Downloads | File Download = Enable
Run PowerShell as an Administrator and Enter this, to download and install .net 3.5:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All
Goto
Control Panel > System and Security > Windows Update
Server should be able to download the updates for .Net 3.5 installation files and installed updates should be seen
in Update History. Below is a sample screen shot:

6.1.2 .NET 3.5 SP1 Framework
1. Launch Registry Editor by entering regedit.exe command in windows.
2. Check the registry - 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework
Setup\NDP\v3.5\1033'
3. There should be an SP=1 DWORD key there if you have SP1 installed.
4. Alternatively, from command prompt run 'reg query':

C:\>reg query "HKLM\Software\Microsoft\NET Framework Setup\NDP\v3.5\1033"
SP=1 and Version = 3.5.30729.4926 confirm .NET 3.5 SP1 is installed on the server.

6.1.3 .NET 4.5.2 Framework
NOTE
.Net 4.5.2 not required to be installed if .Net Framework higher than version 4.5.2 already
installed on the server
1.  Select  to exit any open applications or screens
2. Launch Microsoft .NET Framework 4.5.2 (Offline Installer)
3.  Click Download
4. Below screen should appear which should start downloading the installer. If download does not start
automatically,  click on Click here as marked in red below.
5.  Click Save to download.
6.  Click Open Folder to show installer download location.

7.  Right Click on NDP452-KB2901907-x86-x64-AllOS-ENU.exe and select  Run as administrator to
launch the installation of .NET Framework 4.5.2.
8. Use the checkbox  I have read and accept the license terms.
9. Press  Install to accept the installation.
10. Launch
https://www.microsoft.com/en-us/download/details.aspx?id=44211
11.  Click Download.
12.  Select the download as per the bitness of the IBE Server and  click Next.
13.  Click Save to download.

14.  Click Open Folder to show installer download location.
15. Open the download location and  Right Click on Windows8-RT-KB2977766-x64.exe and select  Run as
administrator.
16. Software Update Installation Wizard shows up. Press  Next.
17. Use the checkbox  I have read and accept the license terms. Press  Next to complete installation.

6.2 Install Microsoft SQL Server
MS SQL Server is a prerequisite for IBE server. This document captures the steps to install and Configure MS SQL
Server on a fresh IBE system.
Pre-requisite
 Correct version of MS SQL Server and/or Service Pack is downloaded as per IBE IT Specification Guide
 Administrative rights to the Operating System of the IBE server to install MS SQL Server
6.2.1 Install MS SQL Server 2014

The Microsoft SQL Server 2014 SP2 application needs to be installed on IBE Server.
1 Be sure you are logged in as (Domain) Administrator
2 Make sure the Windows Location is configured correctly (e.g. Japan, see section 5)
3  Right Click on SQL Server installer and select  Run as administrator to launch the installation wizard
4 Press  OK to install the prerequisites and continue
5  Wait a few minutes

6 The SQL Server Installation Center screen appears
7 Select Installation
8 Select New SQL Server stand-alone installation or add features to an existing installation
9 The Product Key screen appears
10 Enter the 25-character Product key
11 Press  Next to proceed
12 The License Terms screen appears
13  Select  I accept the license terms
14 If the License Terms are not acceptable, press  Cancel to stop the install process
15 Press  Next to accept the License Terms and proceed
16 Global Rules screen appears in a flash and if all prerequisites are met, Microsoft Update screen appears. 
Click Next.
17 Install Setup Files screen appears in a flash and if all successful Install Rules screen appears
18 Check that no errors appear, ignore the warnings on Computer domain controller (not on member servers),
Microsoft .NET Application Security and Windows Firewall.
19 Press  Next to continue
20 The Setup Role screen appears
21  Select  SQL Server Feature Installation

22 Press  Next to continue
23 The Feature Selection screen appears
Figure 6.2.1.1 Example SQL Server 2008 Setup Feature Selection screen
24 Make sure the following options are selected:
 Database Engine Services

 SQL Server Replication
 Full Text and Semantic Extractions for Search
 Data Quality Services
 Reporting Services – Native
 Client Tools Connectivity
 Integration Services
 Client Tools Backwards Compatibility
 Management Tools – Basic
 Management Tools – Complete
25 Change installation destination drive in Instance root directory to D and press  Next to continue.
26 The Feature Rules screen appears in a flash and if successful, the Instance Configuration screen appears
27  Select  Default instance (default MSSQLSERVER)

NOTE
If required named instance can be configured instead of Default instance
28 The Server Configuration screen appears
29 Change the Startup Type for all the SQL Services to Automatic
30 Select the Collation tab
31 Check that the Database Engine: field is configured to SQL_Latin1_General_CP1_CI_AS, if not press 
Customize… to configure it
33 The Database Engine Configuration screen appears
34 On the Server Configuration tab select  Mixed mode (SQL Server authentication and Windows
authentication)
35 Type in the SQL Server system administrator password in Enter password: and Confirm Password: fields
36 Press  Add Current User to add the SQL Server administrator
37 Select the Data Directories tab
38 Choose the directory as desired (E.g. Data root directory: E:\IBEDB). For recommendations on the drive
layout, refer to IT Specification Guide
40 The Reporting Services Configuration screen appears
41  Select  Install only.
43 Feature Configuration Rules screen appears in a flash and if successful, Ready to Install screen appears
44 Press  Install to continue
45 The Installation Progress screen appears

46  wait up to 10 minutes as components are installed
47 The Complete screen appears and Succeeded status appears for all features
48 Press  Close to proceed
49 Select  to close the SQL Server Installation Center
CAUTION
IBE recommends not using any default accounts for SQL access due to security threats but
disable/rename default accounts and creating new users as per hospital requirement.
Eg : sa account

6.2.2 Check SQL Server Service Pack Installation
1 Select Start > All Programs > Microsoft SQL Server 2014 > SQL Server Management Studio
2 Press  Connect to connect to the IBE Server
3 One of the following versions can appear (Press F7 to view the Object Explorer Details):
4 12.0.2000 ~ this indicates that no Service Pack is installed
5 12.0.4100 or 12.1.4100 ~ this indicates that Service Pack 1 is installed
6 12.0.5000 or 12.2.5000 ~ this indicates that Service Pack 2 is installed
7 If Service Pack 2 is not installed install it as described below
8 If Service Pack 2 is installed, you can skip this service pack installation part.
9  Select  to exit the SQL Server Management Studio
NOTE
If Service Pack 1 is not installed, then directly proceed with Service Pack 2. SP2 covers SP1.
You need to download the applicable Service Pack for installation.
Installation of Service Pack 2 for SQL2014:
1 Login as Administrator
2 Copy the downloaded SQL Server 2014 Service Pack 2 installer SQLServer2014SP2-KB3171021-x64-
ENU.exe file on IBE installation server.
3  Right Click on SQLServer2014SP2-KB3171021-x64-ENU.exe installer and select  Run as

administrator to launch the installation wizard.
4  Wait while SQL Server 2014 processes the current operation

5 SQL Server 2014 update screen appears in a flash and if all prerequisites are met, the License Terms
screen appears
6 Select  I accept the license terms
7 Press  Next> to continue or press  Cancel if you don’t agree
8 The Select Features screen appears where all features should be selected
9 Press  Next> to continue
10 The Check Files In Use screen appears
11 Some processes needs to be stopped for updating but you can ignore this as a reboot is done when setup
is finished
12 Press  Next> to continue

NOTE
During the installation process some files are locked and can’t be replaced
You can continue with the installation but you NEED to REBOOT when Setup is finished
13 The Ready to Update screen appears
14 Press  Update to begin the installation
15 The Update Progress screen appears
16  Wait while setup installs the files
17 When finished check that the status is success on the Complete screen
18 Press  Close to close the installation process
19 Reboot the computer

6.2.3 Configuration steps
The below steps are MS SQL configuration related (any version of SQL).
NOTE
If required named instance can be configured instead of Default instance. If named instance is
configured by default then follow below steps for assigning static port
1. Open the SQL Server Configuration Manager.
Figure 6.2.3.1: SQL Configuration Manager
2. Enable TCP/IP, Shared Memory and Named Pipes.
Figure 6.2.3.2: Network configuration
Static port assignment for named instance which by default has dynamic port:
a.  Right click and select TCP/IP Properties

b. Go to IP Addresses tab
c. Assign 1433 under IPAll > TCP Port

Figure 6.2.3.3: SQL service port check
If the SQL Server Configuration Manager is not accessible, please follow the steps to enable or disable Server Network Protocol
3. Restart the MS SQL service as shown below
Figure
6.2.3.4: SQL
service re-
start

6.3 Install and Configure Acrobat Reader
The Acrobat Reader application is used to be able to open reports that are generated as PDF files. This application
should be installed on all systems.
Installation:
1. Login as Administrator
2. Launch Download Adobe Acrobat Reader and  click Adobe Reader 11.0 - Multilingual (MUI) installer
> Download Now link
3.  Click Save to save the installer
4. Extract the contents of AdbeRdr11000_mui_Std.zip.

5. Open the extracted folder,  Right Click on Setup.exe and select  Run as administrator to launch the
installation of Adobe Acrobat Reader 11.0.
6. Follow the screens step by step to install Adobe Reader 11.0 on IBE Server.

Configuration:
1. Login as Administrator
2.  Double click Acrobat Reader icon on the desktop or select Start > All Programs > Acrobat Reader
3. If Adobe Reader Protected Mode screen appears
select  Always open with Protected Mode disabled and  click OK
4. The License Agreement screen appears

5. Read the Software License agreement
6. Press  Accept to continue or  Decline to quit
7. Press  Continue on Welcome screen.
8. Select Edit, Preferences
9. In the Categories: table select Internet
− Under Web Browser Options unselect  Display in Read Mode by default
− Under Web Browser Options unselect  Allow fast web view
− Under Web Browser Options unselect  Allow speculative downloading in the background
10. Press OK to accept the settings
11. Select  to exit the Adobe Reader application (right upper corner)

6.4 Install Orion Rhapsody
Orion Rhapsody is the heart of IBE server. The software and patches needs to be downloaded from the below FTP
site. 32 bit or 64 bit needs to be downloaded based on the operating system.
Rhapsody 6.2.2
1. Create a new folder on the IBE server named Orion Rhapsody 6.2.2 and open it
2. Create 2 subfolders named: Engine and IDE
3. Go to the Orion site for Rhapsody 6.2.2:
https://orionhealth.app.box.com/v/rhapsody622
a. Download the Engine/rhapsody-6_2_2-windows-x64.exe file into the Engine subfolder.
b. Download the IDE/RhapsodyIDE.exe file into the IDE subfolder
6.4.1 Port availability check

Check availability of port 8444
 Prior to installing Rhapsody, we need to verify that port 8444 is not in use by any (web) application on your
IBE Server.
 Open Internet Explorer and type in: https://localhost:8444
or use netstat –an | find “:8444” to find out if the port is in use
Figure 6.4.1.1: Port availability checking
 If port 8444 is not in use, Internet Explorer cannot display the webpage, and we are allowed to use port
8444 for Rhapsody. So accept the default port of 8444 for Rhapsody Management Console during the
Rhapsody installation.

6.4.1.1 Port change after Rhapsody installation
 The parameter: WebMonitoringService.http.port in the <Install Path>\Orion

Health\Rhapsody\rhapsody\rhapsody.properties file has to be modified.
 The batch file monitor-start.bat in <Install Path>\Orion Health\Rhapsody\bin has to be modified.
Example
@echo start /D"C:\Program Files\Orion Health\Rhapsody\bin" RhapsodyMonitor -S "Rhapsody_6.2.2" -B

4031 -M https://localhost:<PORT>
. To make the change active restart the Rhapsody engine.

6.4.2 Install Rhapsody Integration Engine
1 Navigate to Orion Rhapsody 6.2.2\Engine,  Right Click on rhapsody-6_2_2-windows-x64.exe and select

 Run as administrator to launch the installation of Rhapsody Integration Engine
Figure 6.4.2.1: Select appropriate executable for Rhapsody installation for the system
2 Click  Yes on the User Account Control security screen (if displayed).
3 Click  Next on Welcome to the Rhapsody Installation Wizard screen
Figure 6.4.2.2: Click Next in Rhapsody 6.2.2 Installation Wizard
4 Accept the default destination folder on the Select Destination Directory screen.
Click  Next

Figure 6.4.2.3: Path to install Rhapsody
NOTE
On production systems Drive D is recommended to be used as the Rhapsody Engine
Destination Directory for installation (as specified in the IBE IT Specification Guide)
5 Accept the default data folder on Data Directory Location screen. Click  Next
Figure 6.4.2.4: Path for the Rhapsody Data File
NOTE
On production systems Drive E is recommended to be used as the Rhapsody Data
Directory (as specified in the IBE IT Specification Guide)
Suggested location E:\Rhapsody\data
6 On the Rhapsody Engine Memory Settings screen:

JVM Max Memory (MB) : select the Max memory as 4096 (MB)

Figure 6.4.2.5: JVM memory settings for Rhapsody
Click  Next
7 On the Rhapsody Port Settings screen:

Secure Web Management Console Port
Accept the default 8444 port if no web page was found during the pre-check in Section 6.4.1.
Alternatively, if a web page was found during the section, use a different free port
Figure 6.4.2.6: Port settings for Rhapsody
8 Accept the default start menu folder on Select Start Menu Folder screen. Click  Next

Figure 6.4.2.7: Rhapsody shortcut name
9 Accept the default names on the Rhapsody Service screen. Make sure that the Service Start Type is set to
Auto Start. Click  Next
Figure 6.4.2.8: Rhapsody service identification
10 Provide Service User Account and Service User Password on Rhapsody User Account screen, if there is a
network share to be accessed by Rhapsody engine

Click  Next
Figure 6.4.2.9: User for Rhapsody Service
11 Click  Next in Rhapsody Service Overview screen.
Figure 6.4.2.10: Overview of service name and user account
12 Make sure to select both check boxes on Post Installation Options screen.
Run Rhapsody Service Monitor
Run Rhapsody 6.2.2
Click  Next.

Figure 6.4.2.11: Post Installation Options
13 Here the installation of Rhapsody Integration Engine ends. Click  Exit
Figure 6.4.2.12: Rhapsody installation complete
14 Post installation check  Verify Rhapsody Integration Engine started.

At this moment your Rhapsody Integration Engine will be started automatically. Using the taskbar you can
verify that Rhapsody is starting/started.
Red circling Rhapsody icon  Starting

Figure 6.4.2.13: Rhapsody icon on the task bar
Big Red Rhapsody icon  Started
Figure 6.4.2.14: Rhapsody engine after starting the service

6.4.3 Install Rhapsody IDE Application
1  Right Click on RhapsodyIDE.exe and select  Run as administrator to launch the installation of
Rhapsody IDE
Figure 6.4.3.1:Rhapsody IDE setup
2 Click  Yes on the User Account Control security screen (if displayed).
3 Click  Next on the IDE Welcome Wizard
Figure 6.4.3.2: Rhapsody IDE setup wizard
4 Accept the default installation folder on Choose Install Location screen. Click  Next
Figure 6.4.3.3: Path for Rhapsody IDE installation

NOTE
On production systems Drive D is recommended to be used as the Rhapsody IDE
Destination Directory for installation (as specified in the IBE IT Specification Guide)
5 Accept the default start menu folder on Choose Start Menu Folder screen. Click  Install
6.4.3.4: Rhapsody IDE shortcut
The IDE Application will be installed
6 Click  Finish
Figure 6.4.3.5: Completes Rhapsody IDE installation
At this moment your Rhapsody IDE application is installed

6.4.4 Apply Rhapsody License
The Rhapsody Integration Engine license (Rhapsody Integration Engine.ohl) needs to be applied via the IDE
user interface.
CAUTION
Rhapsody Engine/Service should be running with user having appropriate permissions
1 Select Start > All Programs > Rhapsody 6 > Rhapsody IDE
Figure 6.4.4.1: Rhapsody IDE
2 The IDE Interface is launched with Username: Administrator pre-populated on the Rhapsody Login screen

Figure 6.4.4.2: Rhapsody IDE login screen
To logon type in, the default first time Password: <Rhapsody default>. At a later step this password must
be changed to a new password as per the Hospital’s IT Policy.
3 In Certificate Warning select below checkbox and click  Yes

 Permanently trust this certificate
Figure 6.4.4.3: Certification Authentication

If you see an error screen during Certificate authentication, close the error screen.
Click  More Options on the Rhapsody Login screen and  click Rhapsody IDE Trust Manager.
On Rhapsody IDE Trust Manager screen select the certificate,  click Remove and  close.
Retry login from Step 2.
Figure 6.4.4.4: Rhapsody IDE Trust Manager
4 The IDE Interface will be opened and first time login Rhapsody Configuration Wizard will popup. This wizard
will guide you through several configuration steps. Click  Next
Figure 6.4.4.5: Rhapsody license and registration
5 Fill in the site information for the Hospital and click  Next

Figure 6.4.4.6: Organization information for Rhapsody registration
6 In Engine Licensing screen fill in the following information:

 Suggested Engine name: IBE_<SW Version>_<Name of Healthcare Facility>
 Select the Rhapsody License: Browse to the location where the Rhapsody license is located.
 Change the Administrator password: Fill in the New and Confirm password for the Rhapsody
Administrator.
NOTE
Remember the changed Rhapsody Logon Administrator password and communicate to the
Implementation and Support team
Figure 6.4.4.7: Rhapsody licensing
Click  Next
7 Click  Next on the Complete Configuration screen

Figure 6.4.4.8: Information sharing with Orion
8 The application will now try to send the configuration information to Orion Health
Figure 6.4.4.9: Contacting Orion Server to share information
9 It is expected that the transmission of this data will fail. Select  Send Via E-mail
Figure 6.4.4.10: Alternative Information sharing of Rhapsody via email
10 In case the IBE Server has no Email application installed the following screen will appear.
Click  OK.
Figure 6.4.4.11: Pop-up when no email client configured in the machine
11 Click  Save File on the Completing Configuration screen
Figure 6.4.4.12: Save the Rhapsody information in a text file to send in future
12 Save the file to desktop to send this file to Orion Health (rhapsody.report@orionhealth.com) for registration
purposes. Click  Close.
Figure 6.4.4.13: Configuration completed
13 Click  Finish to complete your installation

Figure 6.4.4.14: Finish Rhapsody installation
Rhapsody Integration Engine, IDE and License have been

successfully installed

6.4.5 Add users for Rhapsody
1. Login to Rhapsody IDE using Administrator credentials
2. Navigate to View > User Manager
3.  Click Add
Figure 6.4.5.1: User creation
4. On Add New User screen, enter the Account Details:

Username – The user's login name. This name is not case-sensitive.
NOTE
This name must be unique; when you click the OK button to save the user, Rhapsody will
check that the entered name is unique and will display a warning if it is not.
It is advised to create personal logons for all people that are logging onto IBE\Rhapsody for
reliable audit logging.
Full Name – The user's actual name.

Password – The user's password. This is case-sensitive
Confirm Password – Re-enter the password entered in the Password field.
Access Group – The access group with which the new user is to be associated. Refer to Group Management
for details on group management. Default Access Groups are:
 Administrator
 Dashboard
 Developer
 Monitoring
 Password Never Expires – Select this field if the user's password never expires
 Disabled – Select this field to create an inactive user
CAUTION
When a user logs on for the first time, they must change their password. The new password will
then never expire. If a Password Policy has been defined, all password policy rules will be
displayed on the Change Password screen.
If a password policy is defined, and has set the password policy rule to Never Expire this will
override all the individual settings. Otherwise, the individual setting will be applied.

Figure 6.4.5.2: Add New User
5.  Click OK to create the new user.
6.4.5.1 Group Management

The Access Groups screen enables you to view and maintain the Rhapsody access groups that have been
defined.  Click View > User Manager... , then  click the Groups button to view this screen.
Figure 6.4.5.1.1: Access Groups
The Groups tab displays the following information:
Column Description
Group The name of the group.
The lockers associated with the group that have custom
Lockers with Custom Rights
access rights
Number of Users The number of users in the group
Status Whether or not the group is disabled.

6.4.5.2 Adding an Access Group
To add an access group to the Rhapsody engine:
1.  Click View > User Manager... , then  click the Groups button.
2.  Click the Add button.
3. Enter the following details for the new access group:
Figure 6.4.5.2.1: Editing Setting for Aadministrator group
Field Description
 Enter a Group Name for the group.
 Select the Disabled checkbox to disable the group. All users associated with the
Group Details group will then have a status of Disabled and cannot access Rhapsody.
 Select the Password Never Expires checkbox if you want all users in the group
to have passwords that do not expire
Lockers Select a locker associated with the group, whose permissions you want to set.
For each locker associated with the group, select the access rights that apply to that
locker by checking the appropriate checkboxes. You can use the search box to filter the
Access Rights
list of access rights displayed. Refer to Access Rights for a description of all available
access rights.
Selecting a preset checkbox selects all access rights associated with that preset as
Presets
indicated by the preset icon adjacent to every access right checkbox.
CAUTION
The user permission overrides the group permission. That is, if this field is not selected for the
group, but is selected for an individual, the user's password will not expire

6.4.6 Lockers and Groups
User Access to Lockers
• Rhapsody Users (and their settings) are NOT saved in RLC’s.
Refers to:
* User Account and passwords, and settings
* Groups (access)
* Lockers (rights)
Groups
• PatientMonitoringGroup: HIF, PICiX, IICiX, OBTV, ICIP, IP5, Guardian, SSPM, Orders, PatientData
Query
• CardiologyGroup: ISCV\Xcelera, Orders, Patient Index, DICOM, Unified Communication, Medstreaming,

Xper, (cardWorks).
• ISPGroup: ISP, Orders, Patient Index, Unified Communication
• ECGGroup: DECG, Orders, Patient Index, DICOM, Unified Communication.
• HDSPGroup: CDR Interface, EMR Interface
• eICUGroup: eCareManager

• PatientMonitoringGroup:
General Group User (default): e.g. PMUser

Team User: e.g. COEUser, COENAUser, MRCSupportUser
Single Team Member User: e.g. doeid (for John Doe)
• CardiologyGroup:
General Group User (default): e.g. CardioUser
Team User: e.g. CISupportUser, CIGICCUser…..
Single Team Member User: e.g. jansent
• HSDPGroup:
General Group User (default): e.g. HSDPUser
Team User:……….
Single Team Member User: …..
• ISPGroup:
General Group User (default): e.g. ISPUser
Team User:……….
Single Team Member User: …..

Admin\Developer user
> All unlocked > no is shown
unlocked
User that has access to

All Lockers
User Access to Lockers > Example PM User
• Patient Monitoring Engineer: PMUser
– All foundation routes locked, still visible
– Common Production routes unlocked
– “Product” Production routes unlocked
– Routes of other products locked, but still visible (ISP,HSDP,DECG)

Locked
because
unlocked
Locked
because
Foundation
unlocked
User that has access to Locked

ICIP, PICIX, PIIC, OBTV, SSPM, Guardian, HIF becaus
and common Lockers
unlocked
User Access to Lockers > Example ISP User
• Rhapsody Users (and their settings) are NOT saved in RLC’s.
– Refers to:
* User Account and passwords, and settings.

* Groups (access).
* Lockers (rights).

locked
locked
unlocked
user
locked
locked
ISP Lockers
User Access to Lockers > Example Card.Inf. User
• Cardiology Engineer
– Routes of other products not visible (ISP)

Locked because
Foundation
user

ISCV Lockers
unlocked
User Access to Lockers > Example ISP User
• Intellispace Portal Engineer
– Routes of other products not visible (ISCV)

Locked because
user Foundation

ISP Lockers
unlocked
User > No access to Lockers > Example
• User has no access to certain locker.
– During performing change “permission privilege warning” will be shown

Locked icon
First customer live with Lockers
• Landesklinikum Krems An Der Donau - Austria.

– Single Modality: Cardiology Only
– Only Foundation parts are locked
Locked because Foundation
unlocked

6.4.7 Password Policy Management
The Password Policy tab enables an administrator to define a password policy for an engine:
The Policy Password tab enables you to apply the following rules according to your organization requirements.
Option Description
Minimum Passwords must consist of at least a specified number of characters. With this
Length setting, users cannot use blank passwords, and they have to create passwords
that are a certain number of characters long.
Minimum Passwords must consist of at least a specified number of numerals;; for example,
Number 0 -- 9.
Minimum Passwords must consist of at least a specified number of symbols;; for example,
Symbols #,@,%, and so on.
Minimum Passwords must consist of at least a specified number of uppercase characters.
Uppercase
Minimum Passwords must consist of at least a specified number of lowercase characters.
Lowercase
Password • Never Expire -- prevents a user password from expiring.
Expiry Expire After -- define the Maximum password age setting so that passwords expire as often as
necessary for your environment, typically,
every 30 to 90 days.
• Reuse After -- users cannot reuse the same password when their
password expires and must wait <n> days before they can reuse a
password.
User Lockout • Never -- user account is never locked out if the password is entered
incorrectly.

• After <n> failures -- user account is locked out if the password is entered
incorrectly more than <n> times.
• Temporary lockout -- user account is temporarily locked out if the
password is entered incorrectly more than <n> times. Refer to
Exponential Back--off on Authentication Failures for details.
6.4.8 Exponential Back--off on Authentication Failures

Password policies include an option to lock out user accounts after a number of failed login
attempts, however, this is not always appropriate as it allows a malicious user to, instead,
effectively perform a denial of service attack. As an alternative to account lockouts, an
exponential back--off strategy provides a mechanism to prevent malicious users from attempting
to obtain a user's password via brute force.
Using exponential back--off, you can temporarily lock out an account with a number of
consecutive failed login attempts, preventing further login attempts until the lockout expires. The
lockout time increases exponentially, but a successful login attempt resets the failed attempt
count, so that subsequent attempts are no longer delayed.
The delay period is calculated as follows:
Min(MaximumDelay, InitialPenalty + (2^(Number of failures above

threshold)) *
IncrementalPenalty)
Login failures and temporary lockouts do not accumulate across Rhapsody restarts.
Enabling Exponential Back--off
To enable exponential back--off:
1. Click View>User Manager..., then click the Password Policy button. The Password Policy
dialog is displayed:

2. Under User Lockout:
a. Select the Temporary lockout checkbox.
b. In the After <n> failures field, set the threshold (<n>) or the number of login failures
after which the temporary lockout applies.
3. Click the OK button. This temporarily locks out the user accounts in Rhapsody, if the password is
entered incorrectly more than <n> times.
The other parameters are configured via the rhapsody.properties file.
All these properties are configurable in seconds.

Property Name Range Default
Value
UserManagementService.maximumExponentialBackoffDelay 1 second -- 24 20 minutes
hours
UserManagementService.initialExponentialBackoffPenalty 0 -- 5 minutes 30 seconds
UserManagementService.incrementalPenalty 0 -- 1 hour 4 seconds
The result of these default settings, with a threshold set at 3 attempts, is as follows:
After Delay
Failures 0--2 No delay
Failure 3 34 seconds
Failure 12 1200 seconds (maximum delay of 20 minutes)
The password policy should be synchronized with the site password policy. IBE recommends below policy:
Minimum length should be 8

Minimum Numbers should be 1
Minimum Symbols should be 1
Minimum Uppercase should be 1
Minimum Lowercase should be 1
The password expiry and user lockout policy should only be implemented if FSE has better mechanism to track the
passwords. If the FSEs are using standard passwords as they are now, we should not recommend anything until
we provide a means for them to store the client passwords securely.
Password expiry should be 60 days

User Lockout should be after 3 tries

6.4.9 Disable SSLv2, SSlv3, TLS1.0 on Web Server
SSLv2, SSlv3, TLS1.0 should be disabled on web server.
Please find the link below for steps to disable SSLv2, SSlv3, TLS1.0 on web server.
Reference link: (https://support.microsoft.com/en-in/help/187498/how-to-disable-pct-1-0--ssl-2-0--ssl-3-0--or-tls-1-

0-in-internet-infor)

6.5 Install and Configure IIS
Exponential Back--off on Authentication Failures
IIS 8 is required for Cart Gateway and Alert Viewer features of IBE
The steps to install the same are mentioned below:
1. On desktop  click Server Manager to launch Server Manager.
2. Dashboard should be displayed by default.  Click Add roles and features
3. On Select installation type screen select  Role-based or feature-based installation and  click Next >.
4. On Select destination server screen select  Select a server from the server pool. Local server should be
displayed and selected in the Server Pool frame. If not selected, Filter and select the local server and  click
Next >.
5. On Select server roles screen select  Web Server (IIS). Next a window pops-up.  Click Add features to
continue.  Click Next > to continue.
Figure 6.5.1: Add roles

6. On Select features screen don’t select anything.  Click Next > to continue.
7. On Web Server Role (IIS) screen, click Next >.
8. On Select role services screen, select the options as displayed below.
Figure 6.5.2: Role Services
 Click Next >.

9. The wizard provides a summary of what will be installed.  Click Next > to start Feature Installation.
10.  Click Close.
This completes the IIS installation.

6.5.1 Register ASP.NET to Web Server (IIS)
To register/install or uninstall ASP.NET 4.5 on Windows Server 2012, use one of the following options:
 aspnet_regiis.exe command does not work in Windows Server 2012.

Run the following command from an administrative command prompt: dism /online /enable-feature
/featurename:IIS-ASPNET45
 For Windows Server 2012 computers, enable "IIS-ASPNET45" using Server Manager, under "Web Server
(IIS) -> Web Server ->Application Development -> ASP.NET 4.5"

7 INSTALL AND CONFIGURE IBE SERVER
This section details the site preparation aspects and installation steps for IBE.
Checkpoints
 Both hardware and software requirements (as specified in IBE IT Spec) should be met
 Basic system configurations should be completed
 IBE server should be an independent box and should not be shared with other product-lines
 Orion Rhapsody should be up and running
7.1 IBE Release Zip Overview

To install and setup IBE, you would first need to download latest 866183 “B” release from the InCenter via below
URL.
http://incenter.medical.philips.com/Default.aspx?tabid=249&itemId=8310&LLClassId=9082509
Or
http://incenter.medical.philips.com/Default.aspx?tabid=839&itemId=9742&LLClassId=10393182
The URL opens up after providing the credentials, the below download window appears, Product documentation
can also be found in Installation and Reference tab
Figure 7.1: IBE download via InCenter
On choosing Release B, the latest software package gets downloaded. Within the zip file, the below is seen.

Figure 7.2: IBE release zip
NOTE
1. Always download IBE latest 866183 “B” release via InCenter.
2. Remember to keep a backup of this software on the IBE Server.
3. Note IBE.B.xx.YY.zzz indicates IBE “B” Release with “xx” version “YY” indicates Patch
release and ”zzz” is the Build Number

7.1.1 IBE SIS Installer
IBE SIS Installer is an installshield based exe file. It is used to install:
1. HIF Component (not installed for Xcelera/DECG/iECG/ISP solutions)

2. Alert Viewer application
3. Audit Trail application – this icon gets created on the desktop.
4. DICOM Manager Windows Service
5. IBE Configuration Wizard – this icon gets created on the desktop.
Below is the flowchart for IBE Installation:

Start of IBE Installation
Launch IBE
Installer
Specify IBE
Install location
IBE installation
complete
Launch IBE
Configuration
Wizard
Choose Connection Remote Enter system details for

Type: Local/Remote Remote IBE DB installation
Local
No
Required interface is
DECG/iECG/Xcelera/ISP?
Yes
Install HIF
Yes
HIF DB Remote Enter Remote
Installation? DB details
No
HIF installation
starts
HIF installation
complete
Select and install DB

components
Launch Rhapsody and

import relevant rlcs
Configure the interface solution

variables/lookup tables and start all
routes and communication points
End of IBE Installation

On extracting the zip file, IBE installer file is shown below.
Figure 7.1.1.1: IBE installer
7.1.2 Rhapsody Files

 Click on the Rhapsody Files folder within the zip file. All IBE product-line specific starter kits are packaged in this
folder. You will see the following:
Figure 7.1.2.1: Rhapsody Files
The starter-kits in the Common folder are used across multiple Philips product-lines.

7.1.3 PSA
 Click on the PSA folder within the zip file. Philips Service Agent (PSA) is used for remote monitoring. Within the
zip file, the below is seen.
Figure 7.1.3.1: PSA

7.2 Installation
The general guidelines and hardware/software recommendations specified in IBE IT Specification should be carefully
followed. IBE installation steps are mentioned below.
7.2.1 Pre-install check
Login to IBE server with the credentials of Admin privileges and check for the following essentials
1. Operating system is Windows Server 2012 R2

2. Refer Section-6.1 (Dot Net Framework) for further instructions on installing .Net 3.5 SP1/4.5.2
3. Refer Section-6.2 for installing MS SQL Server 2014 SP2
4. Refer Section-6.3 for installing and configuring Acrobat Reader.
5. Refer Section-6.4 for Orion Rhapsody 6.2.2 installation
6. Refer Section-6.5 for IIS installation/configuration
NOTE
Page Writer/Stress/Holter interfaces and Alert Viewer application use IIS service
The user that installs IBE needs the dbcreator role. After the database is installed, the
dbcreator role can be removed from the user
7. Latest release of IBE is downloaded from InCenter on to the IBE server. Refer to Section-7.1 (IBE Release
Zip Overview) for further instructions on downloading the latest release of IBE
8. Prerequisites for HIF installation:
a. Installation drive should have minimum 25 GB free disk space on local server where HIF
application/service shall be installed
b. Recommended RAM memory is 8 GB
c. SQL Server 2008 R2 SP3 or above should be Installed on local/remote server where HIF DB shall
be installed
d. SQL Server Reporting Services should be installed and service should be running on local/remote
server where HIF DB shall be installed

7.2.1.1 Setup prerequisites for Offloading SQL on Remote SQL Server
Offloading SQL allows for the SQL databases of dedicated server-class hosts (excluding Enterprise Link) to be stored
on a remote host. The SQL version requirements for the remote SQL Server host are specified in the IBE IT
Specification. Depending on the type of authentication being used, there are different setup prerequisites.
For offloading SQL using Windows Authentication:

1. Create a new standalone SQL instance, or identify an existing, currently unused SQL instance, that meets
the versioning requirements and is on hardware that meets the minimum requirements specified in the IT
Specification. Ensure that the SQL instance is set up for either Windows authentication or mixed
authentication. (The device hosting this SQL server instance will be referred to hereafter as the remote
SQL Server host.)
2. Ensure you have the credentials for a user account in the domain’s active directory that has local
administrative privileges. If you do not have such an account, it may be cloned from an existing account.
Either ask a team member who already has an account configured, or ask the Lab Support team, for
assistance with this. This account will be used to allow access to the domain at various points in the
configuration process as well as to complete System Setup.
3. Add the remote SQL Server host and the IBE server offloading SQL to the desired domain (if they are not
added already). This can be done using the procedure outlined in the section “Adding a Host to a Domain.”
4. Open SQL Server Management Studio on the remote SQL Server host. Connect to the SQL instance
identified in the Step (1) using Windows authentication.
5. In the folder tree for the target SQL server instance, locate the Logins folder under Security. Right-click
the Logins folder and select New Login….
6. Select the Search… button next to the Login name field. In the resulting pop-up window, press the
Locations… button and expand the search to the Entire Directory. In the object name field, enter the user
name of the previously identified active directory user account and press the Check Names button. The
user account should be recognized.
Note: This step can also be completed by entering the domain\username of the account.
7. Ensure the option to use Windows authentication is selected.
8. Move to the Server Roles page using the menu in the top left of the window. Check the box next to the
sysadmin role. Press OK at the bottom of the window.
9. Repeat steps 4-7 for each Active Directory login that needs access to the SQL instance.
10. Right-click the Logins folder and select New Login….
11. In the Login name field, enter domainName\serverName$, where serverName is the host name of the
IBE server offloading SQL. (For example, if SYS5-A-DB1 is offloading SQL, the entry would be:
RNDNEST\SYS5-A-DB1$.) Ensure the authentication type is set to Windows Authentication.
13. On the IBE server that will be offloading SQL, start System Setup using one of the active directory logins
configured with a login for the target SQL instance. Navigate to the SQL Server Connection page. If the
server is a part of an existing installation, create an archive prior to starting System Setup.
14. From the top dropdown menu, select to offload All Databases.
15. In the available fields, enter the remote SQL Server host server name (fully-qualified domain name) and
the name of the target instance.
16. Change the authentication type Windows Authentication.
17. Test the connection using the Test Connection button. The connection should be successful.
18. Complete System Setup and ensure Patient Monitoring Services start successfully.
NOTE
Installing HIF on remote database with named instance requires SQL authentication mode.

For offloading SQL using SQL Authentication
1. Create a new standalone SQL instance, or identify an existing, currently unused SQL instance, that meets
the versioning requirements, and is on hardware that meets the minimum requirements, specified in the IT
Specification. Ensure that the SQL instance is set up for mixed authentication. (The device hosting this
SQL server instance will be referred to hereafter as the remote SQL Server host.)
2. Open SQL Server Management Studio on the remote SQL Server host. Connect to the SQL instance
identified in the Step (1) using Windows authentication.
3. In the folder tree for the target SQL server instance, locate the Logins folder under Security. Right-click the
Logins folder and select New Login….
4. Enter the desired login name in the Login name field. Change the authentication method to SQL Server
authentication.
5. Enter the desired password for account in the Password and Confirm password fields. Change the
password policy settings as desired.
7. On the IBE server that will be offloading SQL, start System Setup and navigate to the SQL Server
Connection page. If the server is a part of an existing installation, create an archive prior to starting
System Setup.
8. From the top dropdown menu, select to offload All Databases.
9. In the available fields, enter the remote SQL Server host server name (fully-qualified domain name, if
applicable) and the name of the target instance.
10. Change the authentication type to SQL Authentication. Enter the user name and password for the
previously created login.
11. Test the connection using the Test Connection button. The connection should be successful.
12. Complete System Setup and ensure Patient Monitoring Services start successfully.
Adding a Host to a Domain
Currently, IBE supports having server-class hardware and VMs as members of a domain. Note that this
configuration change may impact the process by which servers may be accessed.
1. Open Control Panel > System and Security > System, and select the Change settings link under
Computer name, domain, and workgroup settings. A new window will open.
2. Under the Computer Name tab, select the Change… button. A new window will open.
3. In the Member of group box, select the Domain option and enter the domain name. Press the OK button at
the bottom of the window.
4. A credential window will open. Provide credentials for an Active Directory user in the domain used in the
previous step that has permission to add new computers to the domain.
5. Once adequate credentials have been applied, the computer is added to the domain, and will need to be
restarted for the changes to take effect. Following the reboot, note any domain prefixes added to logins,
particularly if attempting to log in using a local user account.
After the host has been added to a domain, active directory users can be added to the host.
1. Log in to the host using a local user account with Administrator privileges.
2. Go to Control Panel > User Accounts > User Accounts > Manage User Accounts. A new window will
open.
3. Press the Add… button beneath the list of available user accounts. A new window will appear to Add a
domain account.
4. Enter the information for the desired user account, or browse for it using the supplied tool. Repeat this
process until all desired user accounts are added.
5. Return to the User Accounts window. If any of the added users require administrative privileges, select
the user account from the user list and press the Properties button. The user type can be changed and
saved.

7.2.2 Installing IBE
1.  Right click on IBEInstaller.exe and select  Run as administrator.
Figure 7.2.2.1 : Run IBE installer
2. IBE Installer Welcome screen appears.  Click Next.
Figure 7.2.2.2 : IBE Installation Welcome window

3.  Click Next on next screen. If you wish, change the destination folder as appropriate in the Destination
Folder screen.
Figure 7.2.2.3: IBE Destination location
4.  Click Install to start IBE installation
Figure 7.2.2.4 : Ready to start IBE installation

5.  Click Finish. This completes first part of IBE installation
Figure 7.2.2.5: First part of IBE installation completed
NOTE
Skip steps 7.2.3 and 7.2.5 if installing IBE for Xcelera/ISCV/DECG/iECG/ISP solutions.
These solutions do not use HIF.
CAUTION
Even if IBE is installed on any drive other than C, below components shall always be installed
in C drive: C:\philips\IBE\Xcelera, DicomService, HL7TestTool and Utilities folder
(C:\philips\IBE\Utilities)

7.2.3 Installing HIF
NOTE
Unattended Installation is not available for HIF but only for IBE product features
1. Launch IBE Configuration Wizard from desktop.

2. Enter Reason to Access and  click OK.
3. IBE Installation Type screen will display. Select the Install Mode as Traditional.
4. Configurations for IBE-Database screen should be displayed.
5. As per the location of IBESIS DB to be installed, choose  Connection Type: Local or Remote and 
click Next to save the changes.  Click OK.
6. Pre-requisites to precede IBE Installation screen is displayed.
 Click Install if you wish to install HIF.
7. If SMO CLR installation status pending screen appears, Click Install to install these components.

8. After completion of SMO CLR component installation, HIF starts preparation for installation
9. Healthcare Integration Foundation Installer Welcome screen appears.  Click Next.

If you wish, change the destination folder as appropriate in the Destination Folder screen.
Then  click Next.  Click Cancel if you wish to exit Setup
Install location

10. Select  Complete and  click Next.
11. Ready to Install the Program screen appears.  Click Install.

12. HIF Installation will be done and at Installation Wizard Completed screen  click Finish.
13. If you wish to install HIF DB on local server with default instance
Choose None to Specify Database(s) to offload and  Click Next

If you wish to install HIF DB on
 Local server with multiple SQL Instances
 Remote server
Refer Setup prerequisites for Offloading SQL on Remote SQL Server
NOTE
This step configures the connection for HIF DB to be installed to SQL Server with or without
Named instance. If instance name is not provided it will consider the instance from the IP, Port
number provided (Default Port number:1433 if not mentioned)
Choose All Databases to Specify Database to offload. Click Next
a. Enter the SQL server Installed local/remote machine’s IP address in below format
If multiple instances, SQL ServerName: <IP Address>,<Port#>[\<SQL Instance Name>] where [ ]
denotes optional value.
If default instance, SQL ServerName: <IP Address>
b. You can also enter the instance name in SQL InstanceName, if not mentioned in SQL ServerName
field. If the installed SQL is default instance leave the field blank
c. Select the Authentication mode.
d. Enter SQL Username which has permissions to create DB
e. Enter the corresponding SQL Password for above username
f.  Click Test Connection to see Successful connection message.  Click OK, then Next.

CAUTION
Please take backup of existing HIF DB for migration before clicking Install in the next step.
14.  Click Install on Database Installation screen to install the HIF database

15. After successful Database Installation  click Next to continue.
16.  Click Next on Restore Archive screen.
17. Qualification and Validation screen will appear with rules. Warnings and errors may be displayed.

The Support Account is named SupportUser.
18.  Click Verify to test all check marked rules.

19.  Click Correct to fix and test all check marked rules.
20.  Click Next once all errors are corrected and green check marks are seen for all the rules.

21. Select  Launch Configuration on Setup Complete screen and  click Finish.
22. Philips HIF screen appears. Press  to close the window

7.2.4 Post-install check
1. If you see below two icons on IBE Server desktop, it means HIF installation was successful.
2. If you see below two icons on IBE Server desktop, it means IBE installation was successful
3. Select Start > Run. Type services.msc and press Enter
Search Philips Healthcare Integration Foundation service as shown below which marks successful
installation of HIF service.
CAUTION
Ensure the HIF Service is started with SupportUser account

7.2.4.1 Check IBE Version
1. Navigate to IBE Install location <Install Drive>:\Philips\IBE\IBEInstaller
2.  Right click on Philips.IBE.ConfigWizard > Properties and goto Details tab
3. Check the Product Version property which should be B.08.00.xxx where xxx is the Build number

7.2.5 Configuring HIF
1. Launch Healthcare Integration Foundation Configuration from desktop.

2. Communication Point:
 Click Configure > Patient Identification > Communication > Port
Figure 7.2.5.1 : Patient Identification Feature in HIF
NOTE
If user wishes to change the port 9000 to site specific, then remember to modify the HIF Patient
Demographics interface as well on
TCP Communication point: HIF PatientDemographics Consumer V2 Client HIFServerName
Route: HIF PatientDemographics Consumer V2 HL7ToXMLMappping in
Philips.IBE.B.xx\Rhapsody Files\HIF\Philips.IBE.B.08.HIF.PatientDemographics.rlc
3. Matching Criteria:
 Click Configure > Patient Identification > Matching Criteria > Edit existing Rule set (Ruleset #1) >
Select required identifiers as per the implementation site. Below is an example:

Figure 7.2.5.2: Example to Configure Patient Matching Criteria in HIF
NOTE
HIF Patient Match Criteria supports Multifacility using Patient External Identifier along with
Medical Record Number as shown in above example
4. Purge interval:
 Click Configure > Patient Identification > Communication > Port
can be configured to maximum 180 days from Purge tab, by factory default it’s 10 days.
Then press  Start Services to apply the changes. Press  to close the window.
Figure 7.2.5.3: Configuring HIF purge.

7.2.6 Configuring IBE
The IBE Configuration Wizard is mainly used for following purposes.
I. Pre-requisites check
II. Interface specific database schema configuration (under Installation).
III. Database password reset (under Additional Settings)
IV. Clinical Data Access configuration (under Additional Settings) is used for Alert Viewer
application.
CAUTION
If IBE is installed at a user defined custom location on IBE server, follow Local Server section
in Step 2 to change install path location in a sql script called during IBE DB configuration
If IBE database needs to be installed on a remote server, follow Remote Server section in
Step 2 to change install path location in a sql script called during IBE DB configuration
Rhapsody variables in Variable Manager should be updated with the new custom location
1. Local Server
Steps to change install path in install SQL script and manually copy configuration file:
I. Navigate to IBE install path <<IBE Install Path>>\IBEInstaller\SQLScripts\
II. Open the script Xcelera_Install_PatientQuery_V1.sql in Notepad and edit: C:\Program Files
(x86)\Philips\IBE\IBEInstaller\Utilities\Philips.IBE.PatientQuery.dll to
<<IBE installed directory>>\IBEInstaller\Utilities\Philips.IBE.PatientQuery.dll.
For example, if IBE install path is D:\Philips\IBE\ then modify to D:\Philips\IBE\
Utilities\Philips.IBE.PatientQuery.dll. Save the changes.
III. Copy <<IBE Install Path>>\IBEInstaller\Utilities\patientquery.app.config file to
C:\philips\IBE\PatientQuery folder
Remote Server
Steps to change install path in install SQL script and manually copy configuration file:
I. Navigate to IBE install path on local IBE server <<IBE Install Path>>\IBEInstaller\SQLScripts\
II. Open the script Xcelera_Install_PatientQuery_V1.sql in Notepad and edit: C:\Program Files
(x86)\Philips\IBE\IBEInstaller\Utilities\Philips.IBE.PatientQuery.dll to
<<Shared Path>>\Philips\IBE\PatientQuery\Philips.IBE.PatientQuery.dll.
For example, if <<Shared Path>> is \\IBESQLDBServer\ then modify to
\\IBESQLDBServer\Philips\IBE\PatientQuery\Philips.IBE.PatientQuery.dll.
Save the changes.
III. Copy Philips.IBE.PatientQuery.dll file from <<IBE Install Path>>\IBEInstaller\Utilities on local
IBE Server to <<Shared Path>>\Philips\IBE\PatientQuery folder and
Copy patientquery.app.config file from <<IBE Install Path>>\IBEInstaller\Utilities on local IBE
Server to <<Shared Path>>\Philips\IBE\PatientQuery folder

2. Configuring IBE with features:
2.1 On the desktop  Right click on Philips.IBE.ConfigWizard and select  Run as administrator.
Figure 7.2.7.1. : Run IBE configuration wizard
2.2 Enter Reason to Access and  click OK
2.3 IBE Installation Type screen will display.
2.3.1 Select the Install Mode as Traditional and follow steps from 2.4
2.3.2 Select the Install Mode as Unattended (Beta Version) and follow steps from 2.11
2.4 Configurations for IBE-Database screen should be displayed.

2.5 If IBESIS DB is to be installed on Local server choose  Connection Type: Local and goto Step 2.6
2.5.1 Choose Authentication Type as SQL Authentication or Windows Authentication
2.5.2 If SQL Authentication is selected provide the local SQL server login credentials (Username
and Password for DB).
Figure 7.2.7.2: Local Connection Type
2.6 If IBESIS DB is to be installed on Remote Server choose  Connection Type: Remote
2.6.1 Provide the remote SQL server IP Address in Hostname: in one of the below formats
<IP>
<IP>,<PORT>\<INSTANCE NAME>
<IP>\<INSTANCE NAME>
(E.g.: 127.0.0.1,15000\NMDINST1)
2.6.2 Choose Authentication Type as SQL Authentication or Windows Authentication (if IBE
server is member server to Hospital Domain in which Remote server also resides and we are
logged in as Domain user to install IBE)
2.6.3 If SQL Authentication is selected provide the remote SQL server login credentials (Username
and Password for DB).

Figure 7.2.7.3: Remote Connection Type
2.7.  Click Next to save the changes.
Figure 7.2.7.4. : IBE Configuration

2.8.  Click OK
2.9.  Click Next
Figure 7.2.7.5. : Pre-requisites for IBE installation
2.10 On Installation tab select features and  click Add to move features from left list to right list. Select
features in the right list and choose  Install, Un-install or  Upgrade and
 click Configure.
Figure 7.2.7.6: IBE Installation

2.11 IBE Silent Installer
IBE Silent Installer helps to load RLCs (install Rhapsody in case of fresh install) and database of
selected product line(s) without user intervention once configurations are taken from UI. Silent
Installer is merged with existing IBE Configuration Wizard.
2.11.1 Philips.IBE.ConfigWizard can be found on desktop. Right Click and Run as Administrator to
open the below screen.
Figure 7.2.7.7: Run IBE configuration wizard
WARNING
Prerequisite check – If OS Version (Windows 2012 R2 or 2008 R2) or Powershell version (4.0)
is not as per specification, error will be displayed and installation shall not proceed
2.11.2 Provide ‘Enter Reason to Access’ and click OK Button.
Figure 7.2.2.2: Reason to Access

2.11.3. Select Unattended (Beta Version) for silent Installation of IBE.
2.11.4. Provide path for Rhapsody Installation Root Folder containing “Rhapsody 6.2.2” Folder (Installation of
IDE, Engine and Dashboard) and “Rhapsody Files” (for RLCs loading) and click Next.
Navigate to <IBE Install drive>\Program Files (x86)\Philips\IBE\IBEInstaller\PowerShellScripts\

and update below files as highlighted:
rhapsody-6_2_2-windows-x64.varfile – To update Rhapsody Engine install path & Rhapsody Data folder path
Rhapsody_Dashboard-2_0_0-windows-x64.varfile – To update Dashboard install path

config.xml – To update engine registration license details (organization, addressline1, addressline2, city,
postcode, state, country), Engine Name (By default IBE will be named)
Copy the license file to <root folder>Rhapsody 6.2.2 folder and update License file name Rhapsody Integration
Engine.ohl in LicensePath accordingly
Rhapsody IDE shall be installed at <root folder>Program Files (x86)\Orion Health\Rhapsody IDE 6
In below case Root Folder will be D:\Orion Rhapsody\
Figure 7.2.2.3: Root Folder
2.11.5. If Rhapsody IDE and Engine already exists, provide Existing Rhapsody Password and Rhapsody
Files Root Folder (for loading RLCs) and Click Next.

Figure 7.2.2.4: Unattended Install Mode
2.11.6. If Selected Root Folder is not correct or Rhapsody install folder and Rhapsody Files folder is named
incorrectly, below error will be displayed.
Figure 7.2.2.5: Root Directory Missing
2.11.7. Provide database connections details for silent product Database installation
Connection Type: Local or Remote

If Local is selected, by default hostname will be present in UI.
Authentication Type:
Windows Authentication: Enter hostname
SQL Authentication: Enter hostname, username and password.

And Click Next.
Figure 7.2.2.6: Windows Authentication for Local Connection Type
Figure 7.2.2.6: SQL Authentication for Local Connection Type

2.11.8 If IBESIS DB is to be installed on Remote Server choose  Connection Type: Remote
2.11.8.1 Provide the remote SQL server IP Address in Hostname: in one of the below formats
<IP>
<IP>,<PORT>\<INSTANCE NAME>
<IP>\<INSTANCE NAME>
(E.g.: 127.0.0.1,15000\NMDINST1)
2.11.8.2 Choose Authentication Type as SQL Authentication or Windows Authentication (if IBE
server is member server to Hospital Domain in which Remote server also resides and we are
logged in as Domain user to install IBE)
2.11.8.3 If SQL Authentication is selected provide the remote SQL server login credentials
(Username and Password for DB).
Figure 7.2.7.3: Remote Connection Type
2.11.8.4  Click Next.
2.12 If system is according to specifications, all pre-requisites will be in green. Click Next.

Figure 7.2.7.5: Pre-requisites for IBE Installation
NOTE
If specified IIS version is not installed, warning sign will be displayed but installation shall
proceed
2.13 Select Product in available product list and respective RLC to load in rhapsody and click (>>) button.
Selected product will be added to selected product list. If selected product has database, database will be
installed in background.
Example: Select Common (Unified, CommonLookupTables, PI and Orders) and Dynalync.

Figure 7.2.7.6: Product and RLC selection
On selection of product in ‘selected list’ selected RLCs will be displayed
Figure 7.2.7.7: Selected list of Product and RLC

Figure 7.2.7.8: Product and RLC Selection
Click Submit.
2.14 By Clicking Submit, all configurations will be saved and UI will be closed opening below
progress bar window.

2.15 If Rhapsody is not present in system , Rhapsody Installation will happen.
2.16 And all selected RLCs (Unified,PI,Orders and Dynalync) in Step 2.13 will be loaded into
Rhapsody.
2.17 All selected Product tables (PI, Study and Dynalync) are installed in database.

2.18 Once all RLCs are loaded and database is installed, MessageBox will be displayed as
shown below.
2.19 Logs can be found in following folder

<<IBE Installed Location>>: \Philips\IBE\IBEInstaller\PowerShell Scripts\logs

2.20 After Silent installation, System report will be generated in the following location
<<IBE Installed Location>>: \Philips\IBE\IBEInstaller\PowerShell Scripts\Report
2.21 If any Error occurs during Silent Installation, below message will be displayed and Logs
can be found in folder mentioned in Step 2.19.
Configuration of below Features install corresponding Services:
Feature Service Installed

IICiX Device Data for ICIP Philips IBE ICIPiXProxy
SSPM Enterprise Device Integration Philips.IBE.SSPMUserAuth
Xcelera/DECG/IECG/ISP Philips.IBE.DICOMManagerService

NOTE
Based on the site need choose appropriate features.
Since, HIF is not used by Xcelera/DECG/iECG/ISP solutions, and IIS is used only by
CartGateway and AlertViewer, its OK to get Warning messages for HIF and IIS components
not being installed on the system
4. Reset the factory default password from Additional Settings tab and ensure to configure in Rhapsody
variable manager.  Click Apply. (local windows password policy will be enabled by default)
Figure 7.2.6.7: Password reset
NOTE
Default SQL authentication credentials for IBE user
Username: IBESISUser Password: <IBE default>
The IBE application has been successfully installed

Please refer to IBE Implementation Guide to configure Product specific interfaces solution

7.2.7 Add/Remove features
1. On the desktop  Right click on Philips.IBE.ConfigWizard and select  Run as administrator.
Figure 7.2.8.1 : Run IBE configuration wizard
2. Enter Reason to Access and  click OK

3. Configurations for IBE-Database screen should be displayed
4.  Connection Type: Local or Remote should be preselected as entered during IBE Configuration (Section
7.2.6) and entered connection details should be disabled as entered in Section 7.2.6 > Section 2.5.  Click
Next and then  OK.
Figure 7.2.8.2 : Remote Connection Type

5. On Prerequisites screen,  click Next.
6. On Installation tab in the below picture, select features and  click Add to move features from left list to
right list and  click Remove to move features from right list to left list. Select features in the right list and
choose  Install, Un-install or  Upgrade and  click Configure.
 ISCV/Xcelera: feature is for setting up the schema for Xcelera/ISCV systems and for setting
up the database view
 PIIC: feature is for setting up the database view for PIIC patient lookup in IBE database
 Device: feature is for setting up advanced Observations Out schema for PIIC, PIIC iX,
IntelliVue Guardian Systems, IntelliBridge Systems, Invivo IP5 and Sure Signs product-lines
 SSPM: feature is for setting up the schema for Sure Signs VS4 and non-Cerner EMR
integrations
 DECG: feature is for setting up the schema for Page Writer TC, Stress, Holter, iECG systems
and for setting up the database view
 ISP: setting up the database view for IntelliSpace Portal (ICAP) for information filling in IBE
database
 Xper: feature is for setting up the schema for Xper systems and for setting up the database
view
 DynaLync: feature is for setting up schema for DynaLync
 DoseWise: feature is for setting up schema for DoseWise
 HSDP: feature is for setting up schema for HSDP Cloud Toolkit
Figure 7.2.8.3 : IBE product selection

Configuration of below Features install corresponding Services:
Feature Service Installed

IICiX Device Data for ICIP Philips IBE ICIPiXProxy
SSPM Enterprise Device Integration Philips.IBE.SSPMUserAuth
Xcelera/DECG/IECG/ISP Philips.IBE.DICOMManagerService
NOTE
Based on the site need choose appropriate features.
Since, HIF is not used by Xcelera/DECG/iECG/ISP solutions, and IIS is used only by
CartGateway and AlertViewer, its OK to get Warning messages for HIF and IIS components
not being installed on the system

7.2.8 Configuration information
After adding features on the Installation tab in IBE Config Wizard, user can goto Configurations tab for more IBE
Server related information:
1. Software Information
a. Windows Server available
b. SQL Server installed
c. IBE version installed
2. Services – IBE Services installed
3. IBE Configurations – system CPU utilization
4. Status – Logs for recent transactions in IBE Config Wizard
Alternatively, user can directly press Status button on Installation tab to move to Configurations tab.

7.3 Uninstallation
7.3.1 Uninstalling IBE
1. Navigate to Start > Control Panel > Programs and Features
2.  Select Philips IBE Installer and  click Uninstall
3.  Click Yes to confirm IBE uninstallation
4. If screen shows list of IBE services running, select  Automatically close applications and attempt to
restart them after setup is complete and  click OK.
7.3.2 Uninstalling HIF

1. Navigate to Start > Control Panel > Programs and Features
2.  Select Healthcare Integration Foundation and  click Uninstall
3.  Click Yes to confirm HIF uninstallation
NOTE
HIF DB does not get removed on Uninstallation of Philips Healthcare Integration Foundation
from Control Panel. Delete the HIF DB manually from SQL Server Management Studio
Removing HIF DB
1. Login to SQL Server Management Studio and  Select Philips.HIF.Primary

2.  Right click and  select Delete.
3.  Select check box:  Close existing connections and  click OK
4. Perform steps 1-3 for below databases also:
a. Philips.HIF.Configuration
b. Philips.HIF.Diagnostics

8 SYSTEM CHECK AND BACKUP
8.1 Post Installation Verification

This section details out the post installation/configuration verification steps for IBE components and its interfaces.
8.1.1 Operating System

Navigate to Control Panel\System and Security\System. The system details should match to what is mentioned
in IBE IT spec.
8.1.2 IBE Support User

Log-in to the IBE box as IBESupportUser and check the roles. This user should have admin permissions and
necessary network share access privileges.
8.1.3 Dot Net 3.5 SP1 and 4.5.2 frameworks

Navigate to Server Manager  Features and verify whether .Net 3.5 and 4.5.2 frameworks are installed.
8.1.4 IIS 8
Navigate to Server Manager  Roles  Web Server (IIS) and verify whether IIS is up and running.
Under Services  World Wide Web Publishing Service and verify this service is up and running.
8.1.5 MS SQL Server
 Open the MS SQL management studio and login as IBESISUser under SQL Server Authentication. On
providing correct password you will be logged-in.
 Verify whether <<MS SQL installed path>>\Data is properly configured and periodic back-up is also setup
8.1.6 Orion Rhapsody
 Start the Orion Rhapsody service (if not yet running) and login to Rhapsody IDE.
 Verify whether <<Rhapsody installed path>>\data is properly configured.
 Login to Rhapsody management console and ensure archive clean-up and periodic back-up is setup
 In Windows services check if Rhapsody service is running under the correct user account
8.1.7 HIF
 Verify whether HIF service Philips Healthcare Integration Foundation is up and running.
 Navigate to <<HIF installed path>>Program Files (x86)\Philips\Healthcare Integration
Foundation\C.00\Product and open the Philips.HIF.ConfigurationHost tool. Verify whether the patient
matching criterion and purge is properly set as per site need
 Open the Philips.HIF.Test.Manual tool and choose PPIS. Click on Publish tab and key in patient
demographics details manually. This inserts patient directly to IBE database (HIF).

Figure-8.1.7.1 HIF Test tool
 Login to the MS SQL management studio as IBESISUser and view the below
Figure-8.1.7.2 Verifying patient in database
8.1.8 CartGateway
Open IIS 8 and click Browse button. This opens up a blank Internet Explorer window

Figure-8.1.8.1CartGateway
8.1.9 PSA
Please refer the IBE Training Course CMS9064 for further details.
8.1.10 ADT Reporter

 To check ADT is created. Navigate to HIF installation folder <<Installed-Drive>>:\Program Files
(x86)\Philips\Healthcare Integration Foundation\C.00\Product and open the Philips.HIF.Test.Manual tool.
Click on PPIS and next on the Refresh Census View tab as shown below, the table should be blank.
 Send an ADT message to the ADT reporter either directly or via unified communication point. Then refresh the
census view, the ADT record should appear in the table. This ensures the ADR reporter interface has been
configured properly
Figure-8.1.10.1 HIF Test tool
8.1.11 Order Reporter

Open the MS SQL Management Studio and browse the below vPatientStudy. After sending an order message
the order record will get displayed on selecting this view. For more specific details check against the columns
StudyInstanceUID and Status in the vPatientStudy. If the order has been placed the StudyInstanceUID and Status
will have the data.

Figure-8.1.11.1 Databases views
8.1.12 IECG (required Registry settings)

iECG has to be configured to interact with IBE expect some configuration in iECG itself. The configuration includes
modifying the values in registry.
1. IOAPIMessagesURL: should match the iECG Results Reporter V1 HTTPReceiver communication point.
2. OrdersURL: should match the DECG WorkListQuery Reporter V1 Communicator Receiver communication
point.
3. OrdersADTOptions: Code to be entered to support (ADT_ORDERS/ORDERS/ADT) options.
4. OrdersPassword: Should be the same Password in the lookup table
DECG_WorkListQuery_Common_V1_CartConfiguration
5. OrdersUsername: Should be the same as the CartID in the lookup table
DECG_WorkListQuery_Common_V1_CartConfiguration

Figure-9.1.12.1 IECG configuration
WORKLIST WORKFLOW:
The worklist can be verified by login to the iECG application, the order inbox will get updated in the “Outbox” tab of
Order search window of iECG. This ensures we have already established the connection with IBE. If we then search
for the worklist the worklist should appear for the patient which we have already admitted for checking Order reporter
interface verification.
RESULTS WORKFLOW :
After receiving the results from the modalities iECG sends the preliminary results will be pushed to the iECG
Results Reporter V1 Preliminary Export communication point, which receives the result files (PDF,XML etc.,). And
configuring the iECG Results Consumer V1 HIS Outbound communication point to receive the result (ORU)
message from IBE. This ensures that IBE is receiving the message from iECG and sending the Result message to
the external application

8.2 System Checks
Please refer IBE IT Specification Guide for System checks.
8.3 System Backup and Final Settings

Please refer IBE IT Specification Guide for Rhapsody and SQL Server backup procedure.

8.4 Rhapsody Integration Engine Startup/Shutdown
Rhapsody Integration Engine – Startup
• Engine executes in a Java Virtual Machine (JVM)
– System RAM is allocated for JVM Maximum
 4 GB is recommended for IBE B.08
– Many background functions are started before the engine is ready
 Monitor their progress by opening Management Console during startup
 If previous shutdown was not clean, Data Integrity Check will be executed
– Interface components (Routes & Communication Points) will start:
 In 1 of 5 phases as configured (Startup First – Startup Last)
 Automatically, if Safe-Mode is not enabled
JVM Maximum Memory Allocation

• Management Console  System Statistics
• The Red line shows the Maximum memory allocated
• The Blue line shows memory usage (currently assigned to support processes)
• The Green line shows the actual memory being used (currently active with data)
• Change the “Maximum Java heap size” in the file:
D:\Program Files\Orion Health\Rhapsody\bin\wrapper.conf and restart the Rhapsody service

Monitoring Rhapsody Engine Startup
• Open Management
Console immediately after
starting the Rhapsody
service to display the
Status of the Rhapsody
services as they start:
(The web page will
automatically refresh
every
1-2 seconds, providing
updated display)
• Access the directory:

D:\Program Files\Orion
Health\Rhapsody\logs
for recorded log
information.
• If the Rhapsody Engine

did not previously
complete a clean
shutdown, Rhapsody will
Invoke its Data Integrity
Check on next startup.
Interface Components Startup

• Interface components (Routes & Communication Points) will start automatically after the engine starts
successfully.
• Components will be started in one of 5 phases (Startup First, Startup Second,.. Startup Last) as configured
for each component:

Interface Components Startup Order
• Each component should be configured to startup during one of the 5 phases.
• Determine which phase to start in by its relative position within the interface:
• Typically, you should start the components in the reverse order of the data flow:
– Output communication points should start 1st
– Intermediate routes should start 2nd
– Input communication points should start Last (3rd)
Rhapsody Startup in “Safe-Mode”
• Safe-Mode is a startup state that will start the engine as usual but will not automatically start the interface
components.
• This is useful when troubleshooting a potential run-away component issue or just to make sure that a
reboot of the system will not start anything until you are ready, i.e.: in preparation for go-live.
• You can configure Rhapsody to startup in “Safe-Mode” by changing the setting in the “D:\Program
Files\Orion Health\Rhapsody\rhapsody\rhapsody.properties” file:
Normal Operation Safe-Mode Start-up

… …
#QueueService.directory=queue #QueueService.directory=queue
#QueueService.forceWrites=true #QueueService.forceWrites=true
# This setting is used as a "safe-mode“ # This setting is used as a "safe-mode"
# If set to true, no components will start at startup # If set to true, no components will start at Startup
#StartupService.safeMode=false Service.safeMode=true
#StatisticsService.directory=statistics #StatisticsService.directory=statistics
… …

Rhapsody integration Engine – Shutdown
• Rhapsody engine shuts down all routes then communication points (not in the reverse order of the start up
sequence).
• After all interface components are stopped, the engine will shut down.
• The last shutdown action by Rhapsody is to delete the file: E:\rhapsody\data\engine.running
• When the OS is shutdown, it will issue a shutdown request to the Rhapsody service and wait 12-30 sec
before throwing an exception and killing the Rhapsody service.
• The Rhapsody service apparently does not RequestAdditionalTime() during the OnStop event, therefore, it
is to our benefit to do one of the following:
– Manually stop the Rhapsody service before shutting down the OS.
– Add a Wait4Service command to the Windows Shutdown process to prevent the Rhapsody service
from being killed by the OS before the shutdown completes.
Wait4Service.cmd
• The command file can be added to the Scripts(Shutdown) properties of the Windows Settings in the Local
Group Policy Editor (gpedit.msc)
• When Windows begins its shutdown procedure, it will execute the shutdown script and wait for its
completion before continuing.
• The shutdown script must stop the service and must have a mechanism to identify that the target service
has completed its shutdown before returning control back to the Windows shutdown process.
• Wait4Service.cmd flow diagram:
• See the section: IBE Clean Shutdown on Windows Restart for installation instructions.

8.5 IBE Clean Shutdown on Windows Restart
Configuring Windows Server 2012 to wait for the Rhapsody Integration Engine to complete its shutdown before
terminating the service.
8.5.1 Introduction
The Philips IBE product is built on the Orion Health™ Rhapsody Integration Engine, which is a Java-based solution
that is configured as a service when installed on a Microsoft Windows platform. In addition to the 20 +/- daemon
processes that make up the Rhapsody engine, stopping the Rhapsody service begins with stopping all interface
components. For an IBE solution, even the simplest product interface is made up of many components (routes &
communication points). Stopping all of these components takes time and as such, the Rhapsody engine often does
not complete its shutdown sequence in the time allocated, when requested to stop during an Operating System
(O.S.) shutdown/restart event. When this occurs, the Rhapsody service is killed, which introduces the risk of
corrupting managed data and always prevents it from registering a clean shutdown. As a result, upon the next
startup, the Rhapsody engine will invoke its Data Integrity Check process to validate that no data has been corrupted.
Although the Rhapsody engine is designed to perform the most crucial aspects of the check first then start the
interfaces and continue with the rest of the checks in the background, there is always a delay in startup of the
interfaces and depending on the volume of data, the background processing can take a while to complete. Startup
delays have taken as long as 10 minutes and background integrity checks have lasted as long as 90 minutes, during
which, a slightly reduced performance is apparent.
To ensure that the Rhapsody engine service completes a clean shutdown, the recommended procedure is to stop
the Rhapsody service before initiating an O.S. shutdown/restart event. Manually stopping the service is appropriate
for interactive shutdown events; however, that is not a practical solution for an automated restart of Windows after,
for instance, a centrally pushed Policies update. The following solution will provide a practical mechanism to ensure
a clean shutdown of the Rhapsody service for all O.S. Shutdown events.

8.5.2 Solution
The Windows Server 2012 R2 Operating System includes a feature which allows multiple scripts to be executed
during startup and/or shutdown of the Windows O.S. This solution will utilize a Windows command file named
Wait4Service.cmd to delay Windows shutdown until after the Rhapsody service has completely stopped.
Implementing this solution can be completed by completing the following steps:
1.  Right click and Copy the Wait4Service.cmd file (contact IBE Support at ibesupport@philips.com for
the cmd file) to a folder on the drive that contains the IBE & Rhapsody binaries, for a standard installation
this should be the D: drive. For this example, the file is copied into a new folder named D:\Program
Files\IBE_Shutdown.
2. In preparation for configuring the Wait4Service command for execution, the following information is
required:
A. The complete path to the Wait4Service command file: for this example, it is D:\Program
Files\IBE_Shutdown\Wait4Service.cmd
B. The Rhapsody service name: depending on the version of Rhapsody installed, this might be
Rhapsody_6.2.2, etc.
C. The complete path to the file that will be deleted when the service shutdown has completed: for
Rhapsody, this is E:\rhapsody\data\engine.running
D. The complete path to a log file that will be created/overwritten each time the Wait4Service command
is executed; this can be anywhere on the server but for this example will be located in the same folder
as the Wait4Service.cmd file: D:\Program Files\IBE_Shutdown\RhapsodyShutdown.log
3. With the Wait4Service.cmd file copied into the designated folder and 3 additional information values
required, add the Wait4Service.cmd script to the Windows shutdown process as follows:
A. Open the Local Group Policy Editor by executing gpedit.msc at a command prompt or from the 
Start  Run command.
i. In the Local Group Policy Editor window,  expand the left panel tree to display:
Local Computer Policy
[-] Computer Configuration
[-] Windows Settings
[-] Scripts (Startup/Shutdown)
ii. In the right panel,  double-click Shutdown

to open the Shutdown Properties dialog and do the following:
a.  Click Add button to open the Add a Script dialog

b. In the Script Name: field,  Browse for or enter the full path and file name of the
Wait4Service.cmd file recorded in step 2A above.
c. In the Script Parameters field, enter each of the 3 values recorded in step 2B, 2C & 2D above
separated by a space.
NOTE
If the parameter itself contains a space, be sure to enclose the entire parameter in quotation
marks
d.  Click the OK button to close the Add a Script dialog.

iii.  Click the OK button to close the Shutdown Properties dialog.
B.  Click the main menu File  Exit to close the Local Group Policy Editor.
4. Test the new configuration by executing a Windows Restart.
5. When the Windows Restart completes, logon as usual and open the log file: D:\Program
Files\IBE_Shutdown\RhapsodyShutdown.log to verify that the Wait4Service command executed
properly.

9 UPGRADE MODEL
This section details IBE upgrade principles, process and scenarios for field personnel. These guidelines should be
followed during any IBE upgrades.
The guiding principle for IBE upgrade is – as long as a version of interface is supported in a release of IBE,
irrespective of which previous release it was born, that interface will be able to function without change in
production.
The upgrade process at a high level involves following activities:
Activity Description
System backup IBE system files such as RLC, Rhapsody engine configurations, database should be
backed up.
Reference documents TTS document and Acceptance test case document should be referenced.
Test server setup A test IBE server should be set-up to test all the upgradation/migration before
deploying on production.
Project planning A robust IBE upgrade project plan considering the below aspects should be created.
Impact analysis, technical/commercial risks, work-break down structure and risk
mitigation actions.
The upgrade scenarios common to field are described below.
Scenario Customer is adding a new interface for existing product-line from the same release of IBE.
Example
Customer is currently using Unsolicited (basic) interface from IBE B.08 for PIIC product-line. Now
they are adding one more interface “Waveform export” from the same release of IBE.
Impact Analysis
Customer is still on the same IBE release and hence there is no impact on the existing interface
solution.
Upgrade steps
1) Backup the existing IBE production server and re-store the same on IBE test server.
1 Download the “Waveform export” interface (RLC file) from IBE B.08 release on test server.
(Refer IBE Implementation Guide for RLC download and import details).
2) Load the above RLC into Rhapsody IDE on the test server.
3) Perform all the necessary configurations/customizations of the interface on test server.
4) Run the acceptance test cases jointly identified by both customer and Philips IT personnel
on test server.
After successful completion of verification on the test server, the solution can then be deployed
on to production.
Scenario Customer is adding a new interface for an existing product-line from the latest IBE release.
Example
Customer is currently using PIIC Unsolicited (basic) interface from an older release of IBE (A.04).
Now they are adding a new interface “Waveform export” for the same product-line from the latest
2 release of IBE (B.08).
Impact Analysis
The Unsolicited (basic) interface from IBE A.04 for PIIC is still supported in the latest release (and
subsequent releases) of IBE. Therefore the existing interface should work without interruption after
the upgrade. However Orion Rhapsody upgrade to 6.2.2 should be carried out.
Upgrade steps : Refer upgrade/migration section

Scenario Customer is adding a new interface for different product-line. This interface is available in the
same release of IBE.
Example
Customer is currently using iECG interfaces from IBE B.08 release. Now they are adding one new
interface “Cerner Enterprise device integration” from SureSigns product-line from the same release.
Impact Analysis
Customer is still on the same IBE release and hence there is no impact on the existing interface
solution.
Upgrade steps
3 1) Backup the existing IBE production server and re-store the same on IBE test server.
Download the SureSigns “Cerner Enterprise device integration” interface (RLC files) from
IBE B.08 release on test server. (Refer IBE Implementation Guide for RLC download
and import details).
2) Load the above RLC files into Rhapsody IDE on the test server.
3) Perform all the necessary configurations/customizations on the test server.
4) Run the acceptance test cases jointly identified by both customer and Philips IT personnel
on test server.
After successful completion of verification on the test server, both iECG and SureSigns interface
solutions can then be deployed on to production.
Scenario Customer is adding a new interface for different product-line. This interface is available in
new release of IBE.
Example
Customer is currently using OBTV interfaces from IBE B.00 release. Now they are adding Xcelera
interfaces from IBE B.08 release.
4
Impact Analysis
The OBTV interface from IBE B.00 release is compatible with B.08 release of IBE; hence the OBTV
interface will seamlessly function in the new release. However Orion Rhapsody upgrade to 6.2.2
should be carried out.
Upgrade steps: Refer upgrade/migration section
Scenario Customer is upgrading to newer release of IBE for one of the following reason
1) Orion Rhapsody Heartbleed fix

2) Performance improvement in Inbound ADT/Order Processing (Through PI in IBE B.08)
3) Need defect fixes/Enhancements for Existing interfaces of the Products (Xcelera, ECG
product line Defect Fixes/Enhancements i.e. CR’s) which are not available in IBE B.02.01
but available in IBE B.08
4) Need to move current IBE database to SQL 2012 infrastructure in remote SQL farm
Example
Customer is currently using IBE A.04 release. Now they want to upgrade to B.08
5
Impact Analysis
The list of existing interfaces from IBE A.04 release must be reviewed jointly with IBE Support.
Upgrade steps: Upgrade/Migration will be done only on need basis as per the steps under
upgrade/migration section.
Scenario Customer is upgrading to newer release of IBE (for whatever reason) but an existing interface is
discontinued in newer IBE release.
Example
Customer is currently using IBE B.01 for iECG A.01 Order worklist interface and now adding Xcelera
product-line. The newer release of IBE B.08 supports Xcelera but not the version of B.01 iECG A.01
6
Order worklist interface version.
Impact Analysis
The Order worklist from B.08 must be used instead of existing IBE B.01 “iECG A.01” Order worklist
interface.

Scenario Customer is upgrading from old IBE release to IBE B.08 release
Example
Current System:
OS: Windows Server 2008 R2 SP1 (64bit)
IBE: B.02.01.007
HIF: B.00
Rhapsody: v4.1.1
New System:
OS: Windows Server 2012 R2 (64 bit)
IBE: B.08.00.020
HIF: C.0
Rhapsody: v6.2.2
Installed IBE Features:

HIF (Patient Lookup for PICiX)
7
Impact Analysis
The new system shall be installed on a new hardware, so we are not doing an in-place migration.
IBE:
We install the standard IBE B.08 with HIF on the new hardware.
IBESIS:
Backup the existing IBESIS database only after ensuring that the purge works as expected and
restore the database on SQL server in B.08 environment
HIF:
Upgrade from older HIF version to newer is not possible.
Rhapsody:
New rlcs from IBE B.08 package should be imported on B.08 server and custom configurations
should be done as recorded in the TTS document.

9.1 Upgrade Paths
The upgrade paths from older releases of IBE to current B.08 version is detailed out in the below matrix
IBE Version Upgrade Path

B.00
B.01
B.01.02
B.02 (with or
without any
hotfix)
B.02.01 (with or
without any
hotfix)
Refer the Migration Instructions section and upgrade/migrate to B.08
B.03
B.03.01
B.04
B.05
B.06
B.07
B.08

10 MIGRATION INSTRUCTIONS
10.1 Migration from earlier versions of IBE to B.08

WARNING
For sites upgrading from older version of HIF to newer version (HIF C.02) there is no direct
path for database migration. Sites will be required to wait approx. one day in order for EMR
ADT, Lab and Orders messages to accumulate a patient census within the HIF.
10.1.1 Pre migration site preparation

1 Verify the Purge functionality (Patient Purge and Order Purge). Please reach out to IBE Support via E-mail
ibesupport@philips.com, if you need any assistance in confirming the same.
2 Backup the existing IBESIS database only after ensuring that the purge works as expected.
3 If migration is from B.05 or lower versions, restore the database (backed up in step 2) on SQL server in B.08
environment.
4 RLC migration needs to be done outside the customer environment.

Please reach out to IBE Support to review the TTS and provide necessary steps for RLC migration.
10.1.2 Pre migration check on IBE Box

1.  Right click on Rhapsody Service Monitor in system notification area and  select Open Management
Console.
2. Login to Rhapsody Management Console and  stop all the inbound TCP communication points
3.  Wait until all the messages in the queues are processed (queues can be seen in Rhapsody Management
Console > Communication Points and Routes sections)
4. If the IBE version is B.02 or B.02.01
a. Login to MS SQL Management Studio and ensure both temp order and MPPS queues (these are the 2
tables in IBE SIS database) are cleared.
5. If migration is from B.02 to B.07 and above for ISP product interface, Install Xcelera from B.02 Config Wizard
before taking backup. Refer Section 12.1.10.
Take database backup. If migration is from B.05 or lower versions, ensure that the backed up database is
restored on SQL Server in B.08 environment.
6. Back up the RLC file and Orion Production license file; Export all the lookup table into a temporary folder;
Make a note of all Rhapsody variable settings and Notification schema configuration (we need these while
configuring B.08 or alternatively these can be always referred from TTS doc).
7. Check the Rhapsody version installed:
If Rhapsody version is not 6.2.2, it requires an upgrade – Refer Section 10.2 for Rhapsody upgrade.
If it is 6.2.2 then cleanup should be performed:
  Stop Rhapsody service and navigate to the Rhapsody Data folder location
(Ex. <Install Drive>\Orion Health\Rhapsody\rhapsody\data).
 Delete the data folder
 Start Rhapsody 6.2.2 service. Use <Rhapsody default> password to login to Rhapsody IDE.
 Load the RLC files as per the required product interfaces from B.08 (Refer IBE Implementation Guide) and
configure the same. Do not start any routes or communication points.

10.1.3 Database Migration
1.  Select Start > Control Panel > All Control Panel Items > Programs and Features >  Right click and
Uninstall Philips IBE Installer without dropping the database components, (As shown in below figure) 
Select No on Philips IBE Configuration – uninstallation screen
Search Philips Healthcare Integration Foundation service,  right click and Stop the service
3.  Select Start > Control Panel > All Control Panel Items > Programs and Features >  Right click and
Uninstall Healthcare Integration Foundation, for sites not using Xcelera/ISCV
4. Launch IBE Installer (Refer Section 7.2) and install IBE and HIF till Section 7.2.3 Step 13.
 Click Cancel on Database Installation screen to cancel HIF database installation.
5. Refer Section 7.2.6 to configure database connection till Step 2.9
CAUTION
Do not install any database components from Installation tab at this stage
6. Launch IBE Configuration wizard. Enter Reason to Access and  click OK.

7. Choose  Install Mode as Traditional and  click Next.
8. Choose  Connection Type and  click Next.

9. Select the Authentication Type and  click Next.
10.  Click OK

11.  Click Next.
12. By default, Installation tab is displayed. Click on Migration tab.

13. Migration tab is displayed
NOTE
For IBE versions B.00, B.01, B.01.01, B.01.02, B.02, B.02.01 follow the below steps from Step
14 – Step 28.
For IBE versions B.03, B.03.01, B.04, B.05, B.06, B.07 and B.07.01 follow the below steps from
Step 14 – Step 15 and then from Step 18 – Step 28.
14.  Select Current IBE Version as per the IBE version from the drop down fields.
15.  Migrate To will be defaulted to B.08.
16.  Select Choose the option for the Field name set as EpisodeNumber as per the site configuration from
the drop down fields.
17.  Select Choose the option for Migration drop down fields.

Migration tab for IBE versions B.00, B.01, B.01.01, B.01.02, B.02 and B.02.01
Migration tab for IBE versions B.03, B.03.01, B.04, B.05, B.06, B.07 and B.07.01

18.  Click Archive.
19. Once Archive is selected Archive Information screen appears with data count.  Click OK.
20.  Click OK on Archive Completed screen.
21. After Archiving is complete the IBE Configuration Wizard redirects to Installation tab to install the required
features
CAUTION
Only preinstalled product features’ data shall be migrated. If all preinstalled product features
are not reinstalled during migration, data will be lost for products not selected.
Eg. During database migration if three product features were initially installed but after
archiving if only two product features are selected, other not installed product data will be lost.
Refer Section 12.1.10. If migration is for non-Xcelera implementation from B.02 to B.07 and
above for:
DECG/iECG interface: Install Xcelera and DECG/iECG features from Config Wizard
ISP interface: Install Xcelera and ISP features from Config Wizard
22. Refer Section 7.2.6 and install the required features.

a. Step 3 to configure database components from Installation tab
b. Step 4 to reset password, if required from Additional Settings tab

23.  Goto Migration tab and  click OK on the Migration information screen. See example below:
24.  Click Restore
25. Once Restore is selected, below warning message will be shown which shows the name of product lines,
separated by comma for which the data will be migrated. See example below:

26.  Click OK. Restore Information screen appears with data count.  Click OK.

27.  Click OK on Restore Completed Screen
28. On Migration tab and check the information displayed for successful Migration. See example below:
NOTE
Refer Section 12.1.10. If migration is for non-Xcelera implementation from B.02 to B.07 and
above for:
DECG/iECG/ISP interface: Uninstall Xcelera from Config Wizard

10.1.4 Rhapsody RLC Migration
New RLCs from IBE B.08 package should be imported on B.08 server and custom configurations should be done
as recorded in the TTS document.
10.1.4.1 Lookup Table Migration Tool

Lookup Table Migration Tool helps in migration of Lookup Table Configurations from Lower versions of IBE to IBE
B06 / B07/ B07.01/ B.08 with Rhapsody 6 and above.
1. Lookup Table Migration Tool can be found in the <<IBE Installed Drive>>:\philips\IBE\Utilities folder for IBE
B.08. For IBE B.08, Import the Lookup Table Migration Tool on the server.
Right Click and Run as Administrator to open the below screen.
2. Click on Browse to select the path to define the location where the Lookup Table configurations of B.08
version will be archived in csv format.
3. The Hostname and the Port number are selected by default. Rhapsody Port number can be modified if
required.
4. Provide the Rhapsody credentials as Username / Password here. Click on Next
5. All the Lookup Table configurations of the B.08 will be displayed in the Selection screen

6. Click on Archive. The below popup will be displayed and click on OK.
The Lookup Table configurations will be saved at the specified path in csv format.
7. Proceed further to Archive the Rhapsody Variables or else Close the Lookup Table Migration Tool.

8. All the Rhapsody Variables configurations of the B08 will be displayed in the Selection screen.
9. Click on Archive. The below popup will be displayed and click on OK. Rhaposdy Variables will be archived at
the same location with the file name VariableConfig.xml
10. Uninstall IBE B.07.01 and Install IBE B.08. Load the B08 RLCs as required.
11. Right Click on the Lookup Table Migration Tool and Run as Administrator.
12. The below screen will be displayed with the details auto saved. Type in the Rhapsody password and click on
Next.

R
13. Now only the common Lookup Table configurations between the B06 and B07 versions will be displayed. If
there are any site specific Lookup Tables implemented in B.06, they will have to be configured manually in
B.08 as they won’t be available for Migration via the tool.
14. Select Migrate and Click on the Migrate tab.
15. The below screen displays the B06 configurations, B07 configurations and the Merged configurations. Make
the modifications as required in the Merged configurations.
If any changes are required in any of the other Lookup Table configurations, click on Table Selection to go
back and select the appropriate Lookup Table.
Merged Configurations takes the data Values from the Old configuration. However, the additional Rows
and Columns from the New configurations will also be populated (See below screenshot for reference).
16. Click on Next to make the modifications in the next Lookup Table. If no changes are required in other Lookup
Tables, we can directly navigate to Save to Rhapsody.
The modifications that are made in the Merged configurations will be always saved at below location:
C:\Users\Administrator\AppData\Philips\LookupTableMigration\CSVFiles\Response.
17. This screen displays the List of Lookup Tables that have been selected to Save to Rhapsody.

18. Click on Save to save the changes to Rhapsody.
19. The next screen shows the Logs with complete details of Lookup Tables that were migrated successfully as
well as the failures.
20. Click on Variables -> Selection to proceed further for Rhapsody Variables Migration else Click on Finish to
close the tool.
21. Now only the common Rhapsody Variables between the B06 and B07 versions will be displayed.
22. Select Migrate and Click on the Migrate tab

23. The below screen displays the B06 configurations, B07 configurations and the Merged configurations. Make
the modifications as required in the merged configurations.
Note: The Rhapsody variables with Encrypted value can’t be migrated via the tool and will have to be
configured manually in B.08.

24. Click on Save to save the Rhapsody Variables configurations.
25. The pop-up shows the logs with details of the Rhapsody Variables which were not able to migrate successfully.
26. Click on OK. Click on Finish to close the Tool.
Note: Lookup Table migration tool is generally used for migration from B06 to B08.
However it can be used for migration from any Lower version using Rhapsody 4.x to either B06 / B07 which use
Rhapsody 6 (and above) by following the below steps:-
1) If IBE needs to be upgraded in the same Instance :-

i) Export the RLC configuration of the old IBE version to a drive.
ii) Uninstall the lower IBE version and Rhapsody.
OR If IBE needs to be upgraded in a new instance :-
i) Export the RLC configuration of the old IBE and Import it to the new instance.
2) Install IBE B.06 / IBE B.07/ B.08 on the specified instance.
3) Install Rhapsody 6.x
4) Import the old RLC to the Rhapsody 6.x
5) Follow the Same Procedure from Step 1 at the top as mentioned above in the document.
Note: In Step 10, you just need to remove the old RLC and import the RLC of new IBE version
The Lookup Table Migration Tool also handles the difference in change in names of Lookup Tables / Rhapsody
variables in the Old and New IBE version. Follow the below steps if there is a change in the names of any Lookup
Table / Rhapsody variable:-
i) Open the NameChange_config file which is found in the same location as the Lookup Table
Migration Tool.
ii) Add the names of Lookup Tables in below XML format for the Tool to address the name change
while Migration.
<LookupTables>
<lookuptable>

<old_name>Xcelera_Worklist_Common_V3_DICOMConfiguration</old_name>
<new_name>IBE_DICOM_Worklist_Common_V3_DICOMConfiguration</new_name>
</lookuptable>
<lookuptable>
<old_name>DICOM_V3_General_Settings</old_name>
<new_name>IBE_DICOM_Worklist_V3_General_Settings</new_name>
</lookuptable>
</LookupTables>
<Variables>
<variable>
<old_name></old_name>
<new_name></new_name>
</variable>
</Variables>
</Name_Changes>
iii) Save the NameChange_config file

10.1.4.2 Migration tool usage for IBE B.05 or lesser versions (Rhapsody 4) to B.06 or
above versions (Rhapsody 6)
Procedure 1: Manual process
For Lookup Tables:

1. Export each lookuptable as csv file manually from rhapsody 4 to certain folder.
2. Install IBE B.06 or higher version and load rlc into rhapsody.
3. Open migration tool, provide folder location in the path section in configurations page
4. In next page, you can directly migrate the lookuptables (No need to archive lookuptables since it is done
manually)
5. Continue the Migration as mentioned in Section 10.1.4.1.

For Variables:
1. Create an xml file with name VariableConfig.xml in below format.

2. From rhapsody 4 read all variable names, values and encrypted and update the xml.
3. Save xml file in same folder where lookuptables are manually saved as csv files
4. Open the tool, and select migrate option in variable selection page and continue migration as mentioned in
other document.

Procedure 2: Loading Rhasody4 rlc into Rhapsody6
1. From IBE B.05 or lower versions (Rhapsody 4), save the rlc.
2. Load saved rlc into rhapsody 6.
3. Open the tool, archive lookuptables and variables (don’t migrate).
4. Clean the rhapsody and load B.06 rlc.
5. Continue migration as mentioned in other document.

10.1.5 Post Migration check
Search,  right click and Start below services

 Philips Healthcare Integration Foundation Service (if required)
 Rhapsody 6.2.2
2. Login to Rhapsody IDE and start required routes and communication points

10.2 Upgrade from Rhapsody 4.1.x/6.2.1 to 6.2.2
On the 4.x.x or 6.2.1 system, perform the following steps:
1. Create a new folder on the IBE server named Orion Rhapsody 6.2.2 and open it
2. Create 3 subfolders named: Engine, IDE and Documentation
3. Go to the Orion site for Rhapsody 6.2.2: https://orionhealth.app.box.com/s/t5mvjq9jgt6xjy3efndp6obv1bursi62
a. Download the Engine/rhapsody-6_2_2-windows-x64.exe file into the Engine subfolder.
b. Download the IDE/RhapsodyIDE.exe file into the IDE subfolder
c. Download Documentation/Rhapsody 6.2.2 Installation and Upgrade Manual.pdf and other files into
the Documentation subfolder
4. Make note of the Rhapsody <InstallationFolder> typically = D:\Program Files\Orion Health\Rhapsody

5. Open the <InstallationFolder>\rhapsody\rhapsody.properties and note down below settings:
a. AdministrationManager.AdminPort = 3041
b. AdministrationManager.BroadcastPort = 4031
c. InitialisationService.dataDirectory = D:/Rhapsody/Data/
d. WebMonitoringService.http.enabled = true
e. WebMonitoringService.http.port = 8081
f. WebMonitoringService.https.enabled = true
g. WebMonitoringService.https.port = 8444
h. WebServiceApi.httpsPort = 8449
i. And any other entry in the file that is not commented out with a # character
6. Open the <InstallationFolder>\rhapsody\bin\monitor-start.bat and record the value that is described at the end
of the config line > http://localhost:8081
7. Open the <InstallationFolder>\bin\wrapper.conf file and note:
wrapper.java.maxmemory=1024 (should be changed to 4096)
8. Note the Rhapsody Administrator password
9. Note the Domain, User & Password that the Rhapsody service runs under Eg. PHC, Philips/Service;
The above-mentioned value is the default, at customer sites this might be a different value.
10. Open the Rhapsody Management Console and perform the following:
a.  Click the Communication Points icon in the left side menu
i. Scroll to the bottom of the screen
ii.  Click Stop for all Input communication points
iii. Ensure that all messages on the route have completed processing
iv.  Click Stop for all output communication points
b.  Click the Routes icon in the left side menu

i. Scroll to the bottom of the screen
ii.  Click Stop All
iii.  Click OK button to confirm stopping all routes
c. Navigate to the Server Settings > Backup screen and check the Current Backup Schedules section.
d. Backup your existing:
i. Configuration, including any custom communication points and filters. Refer to Configuration
Migration for details.
ii. Rhapsody installation directory.
iii. Rhapsody data directory.
e. If Type: Full backup is already defined where Area = All,  click Action: Backup Now
f. If Type: Full backup is not defined, create a definition under the Create New Backup Schedule section
as follows:
i. Select Type:  Full
ii.  Select Area : All
iii. Select any Frequency and Time settings since these values are not used for this step.
iv. Enter a Directory path where the backup should be stored. Recommended drive is F.
v.  Click Add
vi.  Click Action: Backup Now and wait for the Status to change from Running to Completed
<date & time>
g. Note down the location of the Rhapsody Integration Engine installation directory. This is required to
update the existing installation.
h. Uninstall the existing Rhapsody IDE.
WARNING
Do NOT specify a location that falls under either of the directory paths recorded in steps 5 or 6
above.
11.  Stop the following services on the IBE server:

a. DICOM Service (if present)
b. Philips Healthcare Integration Foundation Service, if running
c. Philips.IBE.DICOMManagerService, if running
d. Rhapsody_4.1.x/6.2.1 service
e. SQL Server (MSSQLSERVER) and other SQL Server services that are running.
Upgrade Migration Steps
Before you begin the upgrade process, ensure you manually migrate the following data which is not
automatically transferred during the upgrade process:
 Mapper's Handling of Missing Fields
 Change to Property Extraction in Database Lookup Filter
 Saved Searches
 Notification Schemes
 HL7 Acknowledgement Generation Filter
 Migrating Waiting and Idle Count Notifier Communication Point
 log4j.properties File
 Wrapper Files
 UTF-8 Encoded Message Properties
 IDEA-CBC/IDEA Cipher Not Supported
 User-defined Certificates
 Non-unique Folder Names
12. Open the new Orion Rhapsody 6.2.2\Engine folder and  double-click the rhapsody-6_2_2-windows-
x64.exe file to begin the installation and  click the Next button on the Welcome to the Rhapsody
Installation Wizard screen.
13. Open the Rhapsody 6.2.2 Installation and Upgrade Manual v1.0.pdf and

a. Follow the instructions to upgrade Rhapsody to 6.2.2 beginning with page 153 and enter the values
recorded in the previous steps above when/where they are requested.
b. Uninstall the existing Rhapsody IDE 4.1.x application.
c.  Double-click the ~\Orion Rhapsody 6.2.2\IDE\RhapsodyIDE.exe file to begin the installation of the
IDE application.
d. Follow the instruction in the Rhapsody 6.2.2 Installation and Upgrade Manual v1.0.pdf file beginning
with page 64.
e. New Orion Rhapsody 6.2.2 license should be procured for this upgrade.
14. Start the Rhapsody 6.2.2 service and wait for the red circling icon to become a red stationary icon in the
system tray.
15. Launch the Rhapsody IDE application from the IBE server desktop and do the following:
a. Logon to Rhapsody as Administrator using the same password recorded in step 8 above.
b. If the Untrusted Self Signed Certificate dialog is presented, place a check in the Permanently trust
this certificate check box and  click Yes
c.  Click the Next button to display the originally entered registration information
d.  Click the Next button to display the originally entered Engine name & purpose info
e.  Click the Next button to display the registration summary page (XML)
f.  Click the Next button to complete the registration process - if network transmission fails, select
 Retry Transmission or  Send Via E-mail button as appropriate
g.  Click the Finish button.
16. Start the following services:

a. All SQL Server services configured to start automatically
b. Philips.IBE.DICOMManagerService
c. Philips Healthcare Integration Foundation Service, if required
d. DICOM Service (if present)

11 PSA
11.1 Philips Service Agent (PSA)

Definitions
Term Definition
The Remote Service Network is the standard supported network for Philips Medical Systems.
RSN
It is a Virtual Private Network between Philips Medical Systems and hospitals.
M2M is commonly translated as Machine-to-Machine or Man-to-Machine.
M2M is a term used to designate the concept of communications between a device
M2M containing some amount of data and another device that requires the use of that data.
Within the context of Remote Services M2M describes the communication between the PSA
and the Enterprise Server
Questra Enterprise Server: Centralized, internet-accessible application installed in a data
M2M Enterprise center.
M2M Enterprise (Production) and M2M Enterprise (QA) is available
Philips Service Agent is a device service running on the medical device to monitor, alert and
PSA enable SW distribution to the device.
The PSA is a common interface to the Questra Enterprise Server.
System Identification and Data Standard
SIDS
Electronically readable information on the Medical Device.
User A person that supports devices remotely
IDM Intelligent Device Management – M2M Web Interface
(internet Secure Socket Layer) SSL-based connectivity for devices with PSA installed for
iSSL
delivering remote services as an alternative to establishing an IPSEC tunnel (i.e. VPN).
PRS Philips Remote Service – marketing name to describe the suite of tooling for remote service.
11.1.1 PSA Solution Installation – Start

The PRS_IBE_Solution can be installed to point to either one of the following M2M Servers:
 The M2M Enterprise Production Server – for Live Production “Field” use.
 The M2M QA Enterprise Server – For Business unit testing of the solution prior to release.
By default, the installer package assumes that user wants to install a configuration that uses the M2M Enterprise
Production Server Address (This is not configurable).
 To install the PSA with a configuration that uses the M2M Enterprise Production Server address:
o Click and invoke the installation process, which by default will extract the installation package files to:
“C:\Downloaded Philips\ PRS_IBE_Solution_A.00.01_Build”
 To install the PSA with a configuration that uses the M2M Enterprise QA Server address:
o Exit out of the Installer Interface (Figure 2), and Open command prompt as Administrator, go to the
location where the package was downloaded and Run the following command:
“PRS_IBE_Solution_Installation_A.00.01.exe /QA”
Figure 1
1. The
installation
wizard
window
will open
(Figure 2).
The
Destination folder location is configurable, but points by default to:
2. Click Install to continue the installation.
Figure 2
3. The PSA Solution installation program provides two Connection Types that are specific to the installation
environment Internet (iSSL) or IPSEC VPN.
 Figure 3 shows the PCCI PSA Solution Installer with the Internet (iSSL) Connection Type selected

M2M Enterprise Production Server Address M2M QA Enterprise Server Address
Figure 3
 Select Proxy Settings checkbox to enable insertion of site specific proxy information.
Note: Any Proxy information is ignored as soon as Proxy Settings checkbox is unchecked.
 Find and Insert the Entitlement Information of the product that will be managed by the PSA. Use the
service number and serial number during the installation. Send email to PSA team at
iscs.developer.support@philips.com to get the above details.
 Enable the Start PSA checkbox to enable/disable PSA service directly after installation.
4. Press Install button after inserting all required information as shown in the Figure 4.
Figure 4
5. PSA Solution Installation – Finish
After pressing the Install button, the installation continues displaying some installation windows and a command line
configuration window (all without user interaction). The “status bar” at the bottom of the installation interface shows
the current installation step progress.
At the end of the installation, the application window will display the message “Installation completed successfully.
Please close the application.” in the status bar.
When closing the “PSA Solution Installation” window, the user will be prompted with a Close Window dialog. The
user can choose to save the entered settings (except for password) into an xml file for future reference. The name
of the file the data is saved to is configuration.xml.
*** For security purposes, the proxy password is not saved in the XML file.
Figure 5

6. Once installation is completed, open a command prompt as Administrator, and run the command
“SetEnvironment PL”
Figure 6
7. Windows Service
In order to be compatible with the PSA update process and the common agent features, the PSA is installed as a
Windows Service. Now Start the PSA service as shown in the below figure.
Figure 7
The PSA (Philips Service Agent) service can be started and stopped using either the Computer Management
Console (Services snap-in) or command line using the sc start/stop PSA command.

11.1.2 Log File
The log file of the PSA is stored in the subfolder “logs” of the PSA program folder:
 C:\Program Files\Philips\psa\<Revision.Update>”
 C:\Program Files (x86)\Philips\psa\<Revision.Update>”
11.1.3 Check in PRS Portal

Once the service as started, service agent will appear in PRS Portal as shown in the below diagram.
Figure 8
Steps to verify Service & Serial Number

The Field Service Engineer who is doing the installation could test the entitlement information associated with the
device being installed before they go onsite to make sure it will allow the PSA to successfully register back to the
M2M Enterprise
 GCS provides a web based utility. Login into the Philips Remote Services Data Administration
website(https://pww.rsn.cle.ms.philips.com/RsnDataAdmin/), and select “M2MàM2M Registration
Tools”,
 The M2M Registration of Service Number and Serial Number can be tested. This information is
entered in the PSA installation interface for IBE.
 In the screenshot below, the FSE would enter the serial number and Material Number (this is
equivalent to the Service Number), and then click “Test M2M Registration”. The results will then
display if there is a matching installed base record in M2M.
Link : https://pww.portal.rs.healthcare.philips.com/RsnDataAdmin/M2MUtilities/M2MLookup.aspx

11.2 Remote Monitoring
11.2.1 Pattern Configuring in PSA
Once the PSA is up running. Update “qsaconfig.xml” & “regexFWconfig.xml” available in below folder location:
“C:\Program Files (x86)\Philips\psa\4.2\etc\templates\CMS_IBE_Solution”
1. Open “qsaconfig.xml” file and add the below VirtualDirectory tag containing the path of the log file being
scanned, and also the FileWatcherTask as shown below.
<VirtualDirectory>
<Alias>RhapsodyFolder</Alias>
<Directory>C:\Program Files\Orion Health\Rhapsody 6\log </Directory>
</VirtualDirectory>
<FileWatcherTask>
<Path>/RhapsodyFolder</Path>
<Filter>log.*</Filter>
<FileWatcherSource ref="regexFW"/>
</FileWatcherTask>
Figure 1

2. open “regexFWConfig.xml” file and add the pattern to be matched in the log file along with the
ErrorCode as shown in the below figure (where E:\Remote Monitoring\log\log.txt is the location of the
log file being monitored ). Note you can remove the unwanted default specificRegex.
<File>
<FileName>E:\Remote Monitoring\log\log.txt</FileName>
<StateFileName>__INSTALL_DIR__\etc\state\CMS_IBE_Solution\log.state</StateFileNam
e>
<SpecificRegex>
<Pattern>.*Login failed for user.*</Pattern>
<Abstract>Login failed for user</Abstract>
<ErrorCode>LOGIN_FAILED</ErrorCode>
<Description>See detail for user name, and refer to troubleshooting
guide.</Description>
</SpecificRegex>
<SpecificRegex>
<Pattern>.+Communication point.*stopped</Pattern>
<Abstract>Failed communication point</Abstract>
<ErrorCode>COMMUNICATION_POINT_STOPPED</ErrorCode>
<Description>Fix failed comm point.</Description>
</SpecificRegex>
<SpecificRegex>
<Pattern>.*There are too many messages on the error queue.*</Pattern>
<Abstract>Error Queue Size Exceeded</Abstract>
<ErrorCode>LARGE_ERROR_QUEUE</ErrorCode>
<Description>Check the cause of error.</Description>
</SpecificRegex>
<SpecificRegex>
<Pattern>.+Communication Point Connection *Failed</Pattern>
<Abstract>Failed communication connection point</Abstract>
<ErrorCode>COMMUNICATION_POINT_CONNECTION_FAILED</ErrorCode>
<Description>Fix failed comm connection point.</Description>
</SpecificRegex>
</File>

3. Once all the editing is completed. Open the Cmd prompt as Administrator, go to the location
“C:\Program Files (x86)\Philips\psa\4.2\bin” and execute the below two commands:
gencfg.cmd -template ..\etc\templates\CMS_IBE_Solution -cfgdir ..\etc

 qsamain.exe -menu -config ..\etc\qsaconfig.xml

11.2.2 Alarm and Rule Configuration in PRS Device Type Management
Following Alarm and Rules are already configured and available in PRS Device Type Management:
i. login failure
ii. Communication point stopped.
iii. Communication point connection failed
iv. Large queue size
Device Type Name details:
Steps
to add
new
Alarm
and
rules
to the
existing device data:
 Click on Edit.
 Go to Alarm tab and Create a new alarm by entering the alarm name and alarm severity as shown below:
 Go to Rules tab, fill in the required details like rule name, rule type, error code, procedure and alarm
associated to the rule as shown in the below figure.
11.2.3 Configuring alerts action (Email Configuration)
Action for the alarm can be configured in Alarm Disposition
As shown in the below diagram insert the required field and add the list of email id in the email rule one by one.
 Click on the respective IBE_Solution alarm.

 Untick “Take no action”.
 Go to Email Rules tab.
 Click on “Add a new location”.
 Select the SSR and provide the device name which is configured to monitor the alarms.
 Add Email ID’s one by one to the list.
 Click on Insert/Update to save.

11.3 Configuring PCCI PSA Solution Installer with the “IPSEC VPN”
Connection Type
11.3.1 PSA Solution Installer with the “IPSEC VPN” Connection Type for QA Environment
NOTE
In order to work with IPSEC VPN, system should be in PRS network lab.
 To install the PSA with a configuration that uses the M2M Enterprise QA Server address:
“PRS_IBE_Solution_Installation_A.00.01.exe /QA”
 The
installation
wizard
window
will open
(figure
below).
The Destination folder location is configurable, but points by default to:
 Click Install to continue the installation.

 The PSA Solution installation
program provides two Connection Types that are specific to the installation environment IPSEC VPN.
 Below figure shows the PCCI PSA Solution Installer with the IPSEC VPN Connection Type selected
Below is the following sample entitlement information given by PRS team.

Service Number Serial Number
DEVIBE 503456789101
 Once after installation. Below are manual changes need to done in both QSA config file and Site.xml file.
 In QSA config file:
Go to the following folder path and modify the QSAconfig.xml file

“C:\Program Files (x86)\Philips\psa\4.2\etc\qsaconfig.xml”
<OCM name="httpsOCM">
<ServerAddress>https://192.68.49.50:443</ServerAddress>
To be replaced with
<OCM name="httpsOCM">
<ServerAddress>https://192.68.49.48:443</ServerAddress>
 In Site.xml config file:

Go to the following folder path and modify the sitemap.xml file
“C:\Program Files (x86)\Philips\psa\4.2\etc\sitemap.xml”
1: Assets type and changed serial number and product ID.
<replace>

<text symbol="__ASSET_NAME__">IM_SPF_Not Applicable</text>
<text symbol="__ASSET_MANUFACTURER__">Philips Medical Systems</text>
<text symbol="__ASSET_PRODUCT__">IM</text>
<text symbol="__ASSET_MODEL__">SPF</text>
<text symbol="__ASSET_VERSION__">Not Applicable</text>
<text symbol="__ASSET_INITIALPOLLINTERVAL__">30</text>
</replace>
<replace>

<text symbol="__SERIAL_NUMBER__">123456789</text>
<text symbol="__PRODUCT_ID__">PSA_ENG_SYS</text>
<text symbol="__SYSTEM_IDENTIFIER__">00001111</text>

<text symbol="__ASSET_MEMBERNAME__">Generated Member name</text>
<text symbol="__ASSET_FRIENDLYNAME__">WIN-MLD9VDCTJC4_Administrator_12-20-
2016_03:32:06</text>
<text symbol="__ASSET_DESCRIPTION__">WIN-MLD9VDCTJC4</text>
</replace>
Above lines should be replaced with below.
<replace>


<text symbol="__ASSET_NAME__">CMS_IBE_Solution</text>
<text symbol="__ASSET_PRODUCT__">CMS</text>
<text symbol="__ASSET_MODEL__">IBE_Solution</text>
</replace>
<replace>
<text symbol="__SERIAL_NUMBER__">Entered while installing PSA</text>
<text symbol="__PRODUCT_ID__"> Entered while installing PSA </text>
<text symbol="__ASSET_MEMBERNAME__"> Generated Member name </text>
<text symbol="__ASSET_FRIENDLYNAME__">CMS_IBE_Solution_DEVICE</text>
<text symbol="__ASSET_DESCRIPTION__">IntelliBridge Enterprise Solution</text>
</replace>
2: Update OCM address
<text symbol="__OCM_ADDRESS__">192.68.49.50</text>
<text symbol="__OCM_ADDRESS__">192.68.49.50</text> should be replaced with <text

symbol="__OCM_ADDRESS__">192.68.49.48</text>
3: Update TA address
<text symbol="__TA_ADDRESS__">192.68.49.49</text>
<text symbol="__OCM_ADDRESS__">192.68.49.49</text> should be replaced with <text

symbol="__OCM_ADDRESS__">192.68.49.58</text>
 Run the following command “qsaMain.exe -menu -config ..\etc\qsaconfig.xml “ in command prompt shown
in below figure.
 Checking the member name in PRS portal
Philips » INDIA » KARNATAKA » Bangalore »Pic-Bangalore Test Environment >>

CMS_DEVIBE_001_503456789101_DEVIBE
From: https://pww.portal.qa2.rs.healthcare.philips.com/PrsPortal/default.aspx
Below are the sample entitlement information which was given at the time of installation.
 DEVIBE-Service Number
 503456789101-Serial number

NOTE
In above figure M2M member name is test_IBE [Name defined by PRS team]
represents generated member name which exist in site.xml.

11.3.2 PSA Solution Installer with the “IPSEC VPN” Connection Type for Production
Environment
NOTE
In order to work with IPSEC VPN, system should be in PRS network lab.
“PRS_IBE_Solution_Installation_A.00.01.exe /PROD”
Figure 1
 The installation wizard window will open (Figure 2). The Destination folder location is configurable, but points
by default to:
 Click Install to continue the installation.

Figure 2
 The PSA Solution installation program provides two Connection Types that are specific to the installation
environment IPSEC VPN.
 Below figure shows the PCCI PSA Solution Installer with the IPSEC VPN Connection Type selected
Below is the following sample entitlement information given by PRS team.

Service Number Serial Number
DEVIBE 503456789101
 Once after installation. Below are manual changes need to done in Site.xml file.
 In Site.xml config file:
Go to the following folder path and modify the sitemap.xml file

“C:\Program Files (x86)\Philips\psa\4.2\etc\sitemap.xml”
1: Assets type and changed serial number and product ID.
<replace>

<text symbol="__ASSET_NAME__">IM_SPF_Not Applicable</text>

<text symbol="__ASSET_PRODUCT__">IM</text>
<text symbol="__ASSET_MODEL__">SPF</text>
</replace>
<replace>
<text symbol="__SERIAL_NUMBER__">123456789</text>
<text symbol="__PRODUCT_ID__">PSA_ENG_SYS</text>
<text symbol="__ASSET_MEMBERNAME__">Generated Member name</text>
<text symbol="__ASSET_FRIENDLYNAME__">WIN-MLD9VDCTJC4_Administrator_12-20-
2016_03:32:06</text>
<text symbol="__ASSET_DESCRIPTION__">WIN-MLD9VDCTJC4</text>
</replace>
Above lines should be replaced with below.
<replace>

<text symbol="__ASSET_NAME__">CMS_IBE_Solution</text>
<text symbol="__ASSET_PRODUCT__">CMS</text>
<text symbol="__ASSET_MODEL__">IBE_Solution</text>
</replace>
<replace>
<text symbol="__SERIAL_NUMBER__">Entered while installing PSA</text>

<text symbol="__PRODUCT_ID__"> Entered while installing PSA </text>
<text symbol="__ASSET_MEMBERNAME__"> Generated Member name </text>
<text symbol="__ASSET_FRIENDLYNAME__">CMS_IBE_Solution_DEVICE</text>
<text symbol="__ASSET_DESCRIPTION__">IntelliBridge Enterprise Solution</text>
</replace>
 Run the following command “qsaMain.exe -menu -config ..\etc\qsaconfig.xml “in command prompt shown
below
 Checking the member name in PRS portal
Philips » INDIA » KARNATAKA » Bangalore » Pic-Bangalore Test Environment >>

CMS_DEVIBE_001_503456789101_DEVIBE
From: https://pww.portal.rs.healthcare.philips.com/PrsPortal/default.aspx
Below are the sample entitlement information which was given at the time of installation.
 DEVIBE-Service Number
 503456789101-Serial number
NOTE
Search M2M member name [Name defined by PRS team] in PRS portal. M2M member
name represents generated member name which exist in site.xml.

11.4 Remote Monitoring – Configuring Notification to write logs
Following are steps to configure mail notification in rhapsody 6.2.x by creating a watchlist.
 Login to Rhapsody Management Console.

 Creating Watchlist:
1) Click on the WatchList Link in the left pane.
2) Enter name for the WatchList and click on the (+) icon.

3) Click on the WatchList name after adding it then the watchlist page will provide an option to add
the components.
4) Select the communication points and routes needed to be monitored from the list provided.

5) The selected communication points and routes will be displayed and the users to whom the
notification should be sent can be added.
6) To check whether the WatchList is configured properly go to Rhapsody development console and
click on View->Object Browser.
7) It will display all the routes and the watchlist column should be containing the created watchlist
element against the specific route.
Setting Notification:
1) Go to My Notification in console manager.

2) Then clicking on the selected user (administrator) will allow us to configure its email id.

Configure Delivery methods:
Then go to Delivery methods where server host and port settings to configure the email notification have to be
provided by selecting Enable notifications to be sent via email.

Default Notification Settings
1) Go to default setting, add a mail ID in default notification for unmonitored components and click (+)
symbol.
2) Apply the changes.
3) In default threshold setting change the “Raise Issue” to yes for the issue for which monitoring is
required as shown in the below figure.
4) Apply the changes.

12 APPENDICES
12.1 Troubleshooting FAQs

Common issues and troubleshooting tips/tricks are mentioned below.
12.1.1 MS SQL Server
How to check dual instance of MS SQL on IBE server?

Check the registry for MS SQL installed instance. There should be ONLY one instance MSSQLSERVER. Delete
rest of them.
Figure-12.1.1.1 MS SQL dual instance check
More information on this topic can be found on MS website:

http://technet.microsoft.com/en-us/library/cc708610(v=ws.10).aspx
Figure-12.1.1.2 Appendix A

Apparently, SQL Server 2008 R2 does not allow .mdf and .ldf files to be created to the root of any drive.
 SQL Server was configured as follows for the MDF and LDF locations:
Figure-12.1.1.3: Server properties
Changing the Data location to E:\MDF and the Log location to F:\LDF (and creating those directories on the file
system), we were able to install the HIF database without failure.

12.1.2 Performance issue and Memory Leak – SQL Server 2008 R2
Symptoms:
• Available memory is almost exhausted.
• The system file cache consumes most of the physical RAM.
• The system has relatively high disk I/O
• There is a continuous and high volume of cached read requests to the hard disk.
• Obvious application performance issues due to increase in paging caused by lack of RAM
Solution:
• Set a Fixed Amount of Memory (SQL Server Management Studio)
• RAMMap to clear the cache/memory maps used by the system
12.1.2.1 Set a Fixed Amount of Memory (SQL Server Management Studio)

Use the two server memory options, min server memory and max server memory, to reconfigure the amount of
memory (in megabytes) in the buffer pool used by an instance of SQL Server. By default, SQL Server can change
its memory requirements dynamically based on available system resources. When configured with a min server
memory setting, the buffer pool does not immediately acquire the amount of memory specified for the min server
memory. For more information about how SQL Server acquires memory, see Effects of min and max server memory.
To set a fixed amount of memory
1. In Object Explorer, right-click a server and select Properties.

2. Click the Memory node.
3. Under Server Memory Options, enter the amount that you want for Minimum server
memory and Maximum server memory.
Use the default settings to allow SQL Server to change its memory requirements dynamically based on
available system resources. The default setting for min server memory is 0, and the default setting
for max server memory is 2147483647 megabytes (MB). The minimum amount of memory you can
specify for max server memory is 16 MB
Recommendation:
1. Set the Max Server Memory of SQL Server to 5012 MB for an 8 GB RAM IBE Server. This setting is to
ensure the SQL Server doesn’t overuse the memory allocated for the server.
2. Place the MDF and LDF on different drives for better IO operation.
3. Create temp db files on different folder. Create multiple data files for temp db (if 8 core RAM then create 8
data files).
This helps in reducing the temp db contention.

12.1.2.2 RAMMap v1.5
RAMMap is an advanced physical memory usage analysis utility for Windows Vista and higher. It presents usage
information in different ways on its several different tabs:
• Use Counts: usage summary by type and paging list

• Processes: process working set sizes
• Priority Summary: prioritized standby list sizes
• Physical Pages: per-page use for all physical memory
• Physical Ranges: physical memory addresses
• File Summary: file data in RAM by file
• File Details: individual physical pages by file
Download the tool called RAMMap (free and safe). This will provide you a real view of the memory working set
including metafile and memory mapped files. It is not advised to clear the mapped files/cache too frequently, as the
system would need to use some of those to perform. So when it tries to rebuild the needed ones, it utilizes more
memory than reading the available cache. There are recommendations, however, to set the maximum memory that
can be used by metafile and mapped file by the system.
Temporarily, you can use the RAM Map Tool: Go to Empty and  click on System Working set. It will not release
your application/3rd party processes/memory but clear the cache/memory maps used by the system. This is safe
tool written by sysinternals (Microsoft) to troubleshoot memory related issues.
12.1.3 Rhapsody Server and MCAFEE

In case Rhapsody Server refuses to start up after install this might be due to a port 8081 conflict with MCAFEE.
In some occasions MCAFEE’s ePO service claims port 8081. To verify (upfront) if port 8081 is claimed, type in the
web browser application http://localhost:8081. No webpage should be displayed.
Port 8081 is claimed
This means that the management webservice of rhapsody can’t be launched. As a result Rhapsody server cannot
start. To change the port setting for Rhapsody, change the value in the rhapsody.properties file (install location of
rhapsody).
12.1.4 IBE
 Can a new IBE release be installed on existing IBE?
Yes, new release of IBE will first check for the existing IBE instance. User will be prompted to either retain or delete
existing configuration & database. If user chooses not to delete then the newer release will retain database and
adds only the new features/functionalities/database schemas without removing any of the existing configurations.

12.1.5 HIF
 How to remove HIF service?
Open the command prompt and use the following command to delete the Philips Connected Care Services service.
>>sc delete Philips Connected Care Services
 How to remove HIF database?
Navigate to <<MS SQL Install Path>>\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA

and delete the HIF schema in MS-SQL data folder manually.
 Installing the Philips HealthCare Integration Foundation Service
Run system setup host. When the qualifiers page is reached, select Verify.
One or both of the ServiceHost Installation or ServiceHost Settings qualifiers will fail. This depends on whether
HIF service host has been previously installed.

Select the Correct button.
The Service Host qualifiers will be corrected. Select Next.

Select Start Services. This requires a machine reboot.
The machine may be rebooted.
Philips Healthcare Integration Foundation Services will be displayed in the Services as Running and with a
Startup Type of Automatic.

12.1.6 Rhapsody
 Orion Rhapsody engine is running but IDE is not logging-in. What could be the problem?
Some Customers enable FIPS. The engine will run with FIPS enabled. The IDE will not. Run regedit.exe and find
the key below
HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled
 0 = off and 1 = on
 Turn off the FIPS.
FAQs
 Could you tell me how long we can use an IBE license? For how many years will we be able to request the
same license using the same sales order number?
IBE licenses are perpetual unless specified otherwise. This means, there is no time limit until when you
can use them. They do have installation window though in which they should be installed. There is no limit
on replacement licenses as well.
 Is there any driver to get sites updated from Rhapsody 4 to Rhapsody 6, is Version 4 going out of support
any time soon?
Yes, version 4 would be out of support soon. We are still to identify the exact dates, but no new orders are
expected to be on version 4.

12.1.7 Enabling CartGateway with .Net 4.5.2
Enable “Automatically detect settings” in LAN setting in Internet Explorer

12.1.8 Font installation for Barcode in Xcelera/ISCV PDF report
Xcelera/ISCV: Embedding Font should support while creating a PDF by IBE
Steps followed:
1) Install the Barcode font on IBE and ISCV servers. Restart the servers.
2) Update the Template with below code.
<td><nobr><font face="Bar-Code 39" size="8">

<a href="//hpdb:study/PatientMRN"
format="AlwaysLabel"><b><SCRIPT>writeLabel("PATIENTID")</SCRIPT>: </b></a></font></nobr></td>
3) Configure Study type with template to display barcode font in US reporting tool.
4) Open the Study using US reporting tool, finalize the report in ISCV.
5) Check the PDF which is converted by PDF converter
6) It should retain the Barcode font in PDF.
CAUTION
Limitation: If the PDF generated by IBE is copied to a machine which doesn’t have barcode
font, it shall not display the Barcode font on the report

12.1.9 Port conflict between JVM port and Xcelera ADT/ORU port
Symptom: "Xcelera HL7Inbound Reporter V3 HIS HL7 Receiver (TCP Server)" communication point is in Retry
state.
With the new rhapsody 6.x implementation we could have a port conflict.
The JVM normally starts on a port in the range of 31000-31999.
"wrapper.jvm.port.min" and "wrapper.jvm.port.max":
In some cases, it is necessary to control the range of ports that the Wrapper will use when choosing a port. The
defaults were chosen to make it very unlikely that they would conflict with any well-known ports numbers (from 0 to
1023 generally assigned on most systems). If the default 31000-31999 range is causing problems, it can be changed
using the wrapper.jvm.port.min and wrapper.jvm.port.max properties. If these are used, be sure to provide a large
enough range to make it unlikely that all of the ports will be in use when the Wrapper attempts to start.
The "Xcelera_Common_Reporter_V3_HL7TCPReceiverPort" also uses 31000.
So if you see this issue, which you can see when IE using TCPView:
To resolve it set the below in the "wrapper-local.conf" file in "<Rhapsody Installed drive>:\Program Files\Orion
Health\Rhapsody\bin":
wrapper.jvm.port=31149

12.1.10 Data migration from B.02 to B.07 and above
Problem: Migration from IBE B.02 to B.07 is failing to populate data in DECG data contract table.
Impact: All site using iECG/DECG and planning to move to B.07 or above.
Observation & Resolution: Data will not populate in DECG data contracts until we install Xcelera/ISCV feature,
even though site is not using Xcelera/ISCV. There is a dependency with Xcelera/ISCV in our migration script code
to get data populated in DECG data contacts
For data migration from B.02 to B.07 and above, the following scenarios exist for different product lines:
1. To migrate data for DECG/iECG product line, Xcelera should be installed in the migrated version.
(Steps to be followed are mentioned in the table below)
2. To migrate data for ISP product line, Xcelera should be installed in both B.02 and the migrated version.
(Steps to be followed are mentioned in the table below)
Product lines Product lines to be Data Custom Solution

installed in B.02 installed in B.07 and above Migration
Xcelera Xcelera Success Not Applicable
DECG/iECG DECG/iECG Fail Follow the below steps:
1. Archive the data from Config Wizard

2. Install Xcelera and DECG/iECG from
Config Wizard
3. Retrieve the data from Config
Wizard
4. Uninstall Xcelera from Config Wizard
Note: To populate DECG/iECG data

contracts, Xcelera should be installed in
the migrated version
ISP ISP Fail Follow the below steps:
1. Install Xcelera from B.02 Config

Wizard before taking backup
2. Archive the data from Config Wizard
3. Install Xcelera and ISP from Config
Wizard
4. Retrieve the data from Config
Wizard
5. Uninstall Xcelera from Config Wizard
Note: To populate ISP data contracts,
Xcelera should be installed in both B.02
and the migrated version

12.1.11 Rhapsody Management Console browser
Often it is best to use Chrome when doing troubleshooting via the Management Console.
Information is provided like in Rhapsody 4.x
When using IE, not all information might be visible. In screenshot below > no information is given in flat wire
section
Same section as
previous slide. You can
view it by using the
“download button”.

12.2 DICOM Manager Service Manual Installation
12.2.1 Objective
This guide was created primarily to aide IT specialists to manually Uninstall and Install DICOM Manager Service
from Command Prompt on IBE server
12.2.2 Steps to Uninstall and Install DICOM Manager Service from Command Prompt
1. Check if Dot Net Framework 2.0 or 4.0 is installed in your machine. If yes, go to the location as in below
screenshot to verify if you have InstallUtil.exe available with the .Net installed version. If not install .Net
Framework 4
2. In
preparation
for
configuring
the
InstallUtil.exe command for execution, the following information is required
a. Location for Dot Net Framework where InstallUtil.exe is available: for this example, it is
C:\Windows\Microsoft.NET\Framework\v4.0.30319
b. Current install location of DICOM Manager Service from where Service needs to be uninstalled: for this
example, it is C:\Program Files (x86)\Philips\IBE\IBEInstaller\
DICOMServiceManager\Philips.IBE.DICOMManagerService.exe
c. Location of the new installer of DICOM Manager Service: for this example, it is
C:\Users\Administrator\Desktop\Xcelera_07022013\DICOMServiceManager\Philips.IBE.DICOMMan
agerService.exe
3. Launch command prompt and execute commands as below:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>cd \
C:\>cd C:\Windows\Microsoft.NET\Framework\v4.0.30319 <<value from 2a>>
C:\Windows\Microsoft.NET\Framework\v4.0.30319>InstallUtil.exe /u "C:\Program Fil

es (x86)\Philips\IBE\IBEInstaller\DICOMServiceManager\Philips.IBE.DICOMManagerSe
rvice.exe" <<value from 2b>>
Microsoft (R) .NET Framework Installation utility Version 4.0.30319.1
Copyright (c) Microsoft Corporation. All rights reserved.
The uninstall is beginning.

See the contents of the log file for the C:\Program Files (x86)\Philips\IBE\IBEI
nstaller\DICOMServiceManager\Philips.IBE.DICOMManagerService.exe assembly's prog
ress.
The file is located at C:\Program Files (x86)\Philips\IBE\IBEInstaller\DICOMServ
iceManager\Philips.IBE.DICOMManagerService.InstallLog.
Uninstalling assembly 'C:\Program Files (x86)\Philips\IBE\IBEInstaller\DICOMServ
iceManager\Philips.IBE.DICOMManagerService.exe'.
Affected parameters are:
logtoconsole =
logfile = C:\Program Files (x86)\Philips\IBE\IBEInstaller\DICOMServiceManager
\Philips.IBE.DICOMManagerService.InstallLog
assemblypath = C:\Program Files (x86)\Philips\IBE\IBEInstaller\DICOMServiceMa
nager\Philips.IBE.DICOMManagerService.exe
Removing EventLog source Philips.IBE.DICOMManagerService.
Service Philips.IBE.DICOMManagerService is being removed from the system...
Service Philips.IBE.DICOMManagerService was successfully removed from the system
.
Attempt to stop service Philips.IBE.DICOMManagerService.
The uninstall has completed.
C:\Windows\Microsoft.NET\Framework\v4.0.30319>InstallUtil.exe C:\Users\Administr
ator\Desktop\Xcelera_07022013\DICOMServiceManager\Philips.IBE.DICOMManagerServic
e.exe <<value from 2c>>
Microsoft (R) .NET Framework Installation utility Version 4.0.30319.1
Copyright (c) Microsoft Corporation. All rights reserved.
Running a transacted installation.
Beginning the Install phase of the installation.

See the contents of the log file for the C:\Users\Administrator\Desktop\Xcelera_
07022013\DICOMServiceManager\Philips.IBE.DICOMManagerService.exe assembly's prog
ress.
The file is located at C:\Users\Administrator\Desktop\Xcelera_07022013\DICOMServ
Installing assembly 'C:\Users\Administrator\Desktop\Xcelera_07022013\DICOMServic
eManager\Philips.IBE.DICOMManagerService.exe'.
logtoconsole =
logfile = C:\Users\Administrator\Desktop\Xcelera_07022013\DICOMServiceManager
assemblypath = C:\Users\Administrator\Desktop\Xcelera_07022013\DICOMServiceMa
Installing service Philips.IBE.DICOMManagerService...
Service Philips.IBE.DICOMManagerService has been successfully installed.
Creating EventLog source Philips.IBE.DICOMManagerService in log Application...
The Install phase completed successfully, and the Commit phase is beginning.
See the contents of the log file for the C:\Users\Administrator\Desktop\Xcelera_
07022013\DICOMServiceManager\Philips.IBE.DICOMManagerService.exe assembly's prog
ress.
The file is located at C:\Users\Administrator\Desktop\Xcelera_07022013\DICOMServ
Committing assembly 'C:\Users\Administrator\Desktop\Xcelera_07022013\DICOMServic
eManager\Philips.IBE.DICOMManagerService.exe'.
logtoconsole =
logfile = C:\Users\Administrator\Desktop\Xcelera_07022013\DICOMServiceManager
assemblypath = C:\Users\Administrator\Desktop\Xcelera_07022013\DICOMServiceMa
The Commit phase completed successfully.
The transacted install has completed.
C:\Windows\Microsoft.NET\Framework\v4.0.30319>
DICOM Manager Service has been successfully installed

12.3 Microsoft Security Patch Deployment Steps
12.3.1 Objective
This guide was created primarily to aide IT specialists in deploying MS Security Patches on IBE server
Only Security Only patches should be installed on the IBE Server. All security patches released prior to the IBE
release should be installed first on IBE server and then approved patches only should be applied post IBE release
month.
For example: Windows Server 2012 R2 was introduced with IBE B.06 released in Oct 2016. ALL MS patches
published before IBE B.06 release should be applied on the IBE B.06 Server upto Oct 2016 – from Nov 2016
Philips has been releasing the approved Security patches. Hence, the security patches released by MS prior to IBE
release are not included in the list.
12.3.2 Steps to deploy MS Security Patch on IBE Server

1. Below is the sample list of MS Security patches identified for deployment on IBE server.
 Select first item in Vulnerability / Patch ID column from the list of security patch items to be applied –
click on the sample link
Applicable patches as of
IntelliBridge Enterprise 2017-10-16
Windows Server 2012 (R2
Version B.07.01 (inclusive of versions starting B.06)
standard(64 bit))
Vulnerability Last update Recommended
Activity Status Notes / Instructions
/ Patch ID by Philips Customer Action
No product Install recommended
4034672 2017-08-21 MS KB Article ID: 4034672
changes planned solution
4034733 2017-08-21 MS KB Article ID: 4034733
4025333 2017-07-14 MS KB Article ID: 4025333
4025252 2017-07-14 MS KB Article ID: 4025252
4022717 2017-07-14 MS KB Article ID: 4022717
2.  Click Download for the item which is applicable to the environment where MS Security Patch is to be
deployed.
For example, if IBE Server is running on Windows Server 2012 R2 – we need to  click the highlighted
item.

3. In some cases, clicking on the Vulnerability / Patch ID link, it can redirect to the below screen:

4.  Select the highlighted Microsoft Update Catalog in above screen. It will redirect you to the download
screen
5.  Click on Download. Below popup window will appear:
6.  Click on the above highlighted item. Downloading will start.

7. Go to the download location and  double click on the downloaded security update installer to apply
the Microsoft Security Update on IBE server

12.4 PSA
Please refer the IBE Training Course CMS9064 for further details.
PSA was released to enable FSE’s to access IBE servers via PRS portal. Here are the instructions for applying the
PCCI PSA PRS Portal Patch.
12.4.1 Background
Symptom:
For some PCCI PSA-enabled solutions, the new PRS Portal does not list the associated M2M applications (e.g.
RDP, UltraVNC) under ApplicationsDevice.
Pictured below is the expected behavior (see Figure 12.4.1) and an example where the M2M application(s) are
missing (See Figure 12.4.2).
Figure 12.4.1– Example of M2M Application(s) listed in PRS Portal “Applications” window
Figure 12.4.2 – Example of missing M2M application(s) in PRS Portal “Applications” window
Cause:
A configuration component is not included in the currently deployed Philips Service Agent. This component is
required for M2M applications to be displayed in PRS Portal.

12.4.2 Resolution
Apply the PCCI Patch PRS Portal Application Visibility to impacted systems to populate the missing XML
configuration.
Patch Utility Prerequisites:
 The PCCI PSA must be installed on the device.

 Administrator/equivalent privileges are required:
o You must be logged onto Windows as an Administrator/equivalent.
o To execute the patch utility via the graphical user interface (GUI) on Win 7/Win 2008 platforms,
you must  right click on the .exe and  select Run as Administrator.
o To run the patch utility from the command line (e.g. Unattended Install), the command window
must be launched with Run as Administrator privileges.
Patch utility deployment Recommendations and Important Notes:
 The patch utility is designed so that it can be applied to systems where the PSA is not communicating with
the Philips Remote Service (PRS)/M2M backend (for example, network connectivity is not available, or the
PSA service was manually stopped). However, it is recommended that issues impacting communication of
the PSA with the M2M/PRS backend are resolved prior to deploying the patch. This will minimize or
eliminate post patch deployment troubleshooting scenarios.
 The Patch utility can be executed remotely via M2M/PRS, but it should be noted that the PSA service
needs to be restarted for the patch to be activated. Upon restart of the PSA, the remote connection will be
lost, and the remote user will have to wait for the PSA service to re-establish communication with
PRS/M2M. At that point the user can remotely reconnect to complete/validate the installation

12.4.3 Attended Installation Mode
 Log onto the PSA enabled system as an Administrator or equivalent
 To Run the Patch Utility:
o For Win 7 or Win 2008 systems,  right click on the Patch utility, and click Run As Administrator
(Figure 8.3.1).
o For XP systems, double click on the .exe to launch the application.
Figure-12.4.3.1 launch the application
 The patch utility will launch, and Figure 8.3.2 is displayed.  Click Install Patch to apply the fix.
Figure-12.4.3.2 PCCI patch PRS portal application visibilty

 During the update, the GUI will briefly display the text shown in Figure 8.3.3:
Figure-12.4.3.3 cancellation
The Windows shown in Figure-8.3.4 are displayed indicating that the updated XML configuration has been applied
(new Solution Version shown as A.01.00 in Figure-8.3.4-top image). To start/restart the Philips Service Agent
Service and activate the updated PSA configuration,  click OK in the Popup Window (Figure-8.3.4-bottom
image).
WARNING
If you are performing the upgrade via a M2M/PRS remote connection, restarting the PSA will
disconnect you from the device. You will need to wait for the PSA service to restart and re-
establish its communication with the M2M/PRS environment. Once the device is shown as
“Online” in M2M/PRS, you can remotely re-connect to the device to complete the installation. If
for some reason the PSA service does not start/restart (e.g. timeout), it may be necessary to
request that a Health Care Facility IT/Biomed restart the PSA service for you
Figure-12.4.3.4 PCCI Patch PRS Portal Application Visibility

 During the PSA service restart process, the text in Figure 8.3.5 is displayed:
Figure 12.4.3.5 PSA Service Restart
 Once the Service Restart has been completed, the text in Figure 8.3.6 is shown, indicating that the Patch utility
can be closed. Proceed to Section 12.4.5 for Post installation checks.
Figure 12.4.3.6 PSA Service Restart Complete

12.4.4 Unattended Installation Mode
The patch utility can also be run silently in Unattended mode from a Command window for those BIU’s that wish
to call the patch utility from their application/installer. The options are shown in Figure 8.4.1:
Figure-12.4.4.1 PCCI Patch PRS Portal Application Visibility
The /U switch allows the patch utility to be run as a silent unattended installation. The /S switch starts or restarts
the Philips Service Agent Service (depending on its state) after the PSA xml configuration has been updated.
NOTE
Remember that the patch utility and command window must be run with Administrator or
equivalent privileges.
For remote installations via M2M Enterprise, using the /S switch will disconnect the remote
session. Refer to Section 12.4.3 Attended Installation Mode for further details

12.4.5 Post Installation Checks and Troubleshooting
Post PRS Portal Patch installation checks:
The following verification steps assume that the PSA was working properly and communicating with M2M prior to
applying the patch utility:
 Verify the PSA Service is running after applying the patch (Assumption is that the user chose to Re-/Start
the PSA after the patch was deployed to activate the new configuration.
 Verify the PRS Portal shows the device as being Online, and M2M Application(s) are now displayed for the
device (e.g. RDP and/or UltraVNC) in PRS Portal as shown in Figure 8.5.1.
Figure-12.4.5.1 reachabilty
Troubleshooting:
 Confirm the PSA service was restarted after the patch was deployed.
 Review entries in the Patch utility log file for errors (PCCI_PSA_Patch_PortalAppVis_A.00.00.log), which
can be found at:
o 32 Bit Operating Systems: C:\Program Files\Philips\psa\4.2\logs
o 64 Bit Operating Systems: C:\Program Files (x86)\Philips\psa\4.2\logs
If it appears that the patch was deployed, but is not communicating properly with the M2M/PRS Portal backend,
refer to your relevant service documentation for troubleshooting PSA connectivity or entitlement issues.

Installation Guide Rev G - IBE Rel B.08.PDF Nodeid 15604638&vernum - 2

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

Installation Guide Rev G - IBE Rel B.08.PDF Nodeid 15604638&vernum - 2

Uploaded by

Copyright:

Available Formats

Healthcare, Interoperability & Standards

IntelliBridge Enterprise (IBE) B.08

IBE B.08 Installation Guide

1 INTRODUCTION AND TECHNICAL INFORMATION................................................................................. 6

Rev G IBE B.08 Installation Guide 5 of 223

1.1 Document History

Rev G IBE B.08 Installation Guide 6 of 223

Figure-1.2.1: Philips IntelliBridge Enterprise Overview

Rev G IBE B.08 Installation Guide 7 of 223

Rev G IBE B.08 Installation Guide 8 of 223

Interface Solution information:

1.4 What is included in the Installation Guide?

This manual does NOT describe the following:

Scan) – refer to the Knowledge Base (KBS or Knova)

Rev G IBE B.08 Installation Guide 9 of 223

1.5.2 Problem Reporting

Any feedback on documentation can be sent to ibesupport@philips.com

Any information containing ePHI must be de-identified before sending it to support.

Rev G IBE B.08 Installation Guide 10 of 223

1.6.2 Glossary: General Terminology and Abbreviations

Rev G IBE B.08 Installation Guide 11 of 223

This part is performed by Philips IT personnel.

 Procure Orion Rhapsody license

Customer IT Responsibilities Philips Responsibilities

Rev G IBE B.08 Installation Guide 12 of 223

Rev G IBE B.08 Installation Guide 13 of 223

Before going to the Orion License site:

Ordering the Production/Test license:

Ordering the Non-Production (Demo) license:

Rev G IBE B.08 Installation Guide 14 of 223

Rev G IBE B.08 Installation Guide 15 of 223

Rev G IBE B.08 Installation Guide 16 of 223

A.00 4.0 Not Applicable Not Applicable

A.01 4.1 Not Applicable Not Applicable

A.02 4.1 A.00 Not Applicable

A.03 4.1 A.00 Not Applicable

A.04 4.1 B.00.00.12 Not Applicable

A.04.01 4.1 B.00.00.13 Not Applicable

B.00 4.1 B.00.01.3 Not Applicable

B.01 4.1.1 (with MSMQ HotFix) B.00.01.3 Not Applicable

B.01.02 4.1.1 (with MSMQ HotFix) B.00.01.3 Not Applicable

B.02 4.1.1 (with MSMQ HotFix) B.00.01.3 Not Applicable

B.03.01 4.1.4 B.02 Not Applicable

B.02.01 4.1.4 B.02 Not Applicable

B.04 4.1.4 Not Applicable A.0

B.05 4.1.4 C.0 Not Applicable

B.06 6.2.1 C.0 Not Applicable

B.07 6.2.2 C.0 Not Applicable

B.07.01 6.2.2 C.0 Not Applicable

B.08 6.2.2 C.02 Not Applicable

Rev G IBE B.08 Installation Guide 17 of 223

IBE IT Specification Guide provides more information on the software versions.

Rev G IBE B.08 Installation Guide 18 of 223

1.  Select Start > Control Panel, Clock, Language, and Region

Rev G IBE B.08 Installation Guide 19 of 223

Rev G IBE B.08 Installation Guide 20 of 223

Rev G IBE B.08 Installation Guide 21 of 223

Open the Local Group Policy Editor

To open the Local Group Policy Editor as an MMC snap-in

1. Search for MMC, and then press ENTER.

2. On the File menu, click Add/Remove Snap-in.

4. In the Select Group Policy Object dialog box, click Browse.

Rev G IBE B.08 Installation Guide 22 of 223