Sie sind auf Seite 1von 231

GE Healthcare

Centricity™ Imaging Analytics Real-time Dashboard

Installation and Administration


Manual
Version 1.4

Do not duplicate
Copyright © 2014-2017 General Electric Co.
Copyright Information
All Licensed Software is protected by the copyright laws of the United States and by
applicable international treaties. No rights under copyrights are transferred to Customer,
except as specifically provided in the License Grant.

Trademark Information
GE, the GE Monogram, and Centricity are trademarks or registered trademarks of
the General Electric Company. All other product names and logos are trademarks or
registered trademarks of their respective owners.

Confidentiality and Proprietary Rights


This document is the confidential property of GE and/or its affiliated entities. It is furnished
to, and may only be used by, customers and their employees under a written agreement
with GE and may only be used in accordance with the terms of that agreement. The
access and use of this document is restricted to customers and their employees. The user
of this document agrees to protect the confidentiality of the information contained herein
and GE’s proprietary rights as expressed herein and not permit access to this document
by any person for any purpose other than as an aid in the use of the GE software. In no
case may this document or any portion hereof be accessed, made available, examined, or
copied for the purpose of developing, marketing, or supporting any system or computer
program similar to the GE software. No part of this document may be copied without the
prior written permission of GE. The information in this document is subject to change by
GE without notice.
Inquiries regarding permission for use of material contained in this document should be
addressed to:
GE Healthcare ATTN: General Counsel, 540 W. Northwest Highway, Barrington, IL 60010

Publication Date and Document Numbers


April 13, 2017
DOC1974243
2103201-001

Service Pack
SP2

2103201-001 2
General Definitions of Symbols
The following table defines symbols used throughout this document and the product
software:

Symbol Definition
This symbol indicates the MANUFACTURER of the product.

This symbol indicates the DATE OF MANUFACTURE of the product.

This symbol indicates that the operator should CONSULT


INSTRUCTIONS FOR USE for further information.

2103201-001 3
About This Manual
This manual is for GE service representatives and customer system administrators. It describes
how to install, configure, and verify Centricity™ Imaging Analytics Real-time Dashboard.

Contacting GE Support
Contacting the ROC
Use the following information to contact the ROC (Remote Online Center).

Table 1 Online Center contact information

OLC/USA OLC/Europe OLC/ANZ


1–855-762-6650 +33 (0) 1 30 831300 61-2-316-3700
(US/Canada)
Latin America: contact your Contact your field service Contact your field service
field service representative representative. representative.

Applications Support Using iCenter, Applications Answerline, and


Customer Center
To request applications support, English-speaking customers may open a support request in
GE Healthcare iCenter. Other customers should contact their GE Field Engineers or support
personnel.
With GE Healthcare iCenter™ you can:
● Initiate requests for service and applications support from the web.
● Get rapid, online access to the Remote Operation Center (ROC) where expert Field
Engineers review and respond to service requests quickly.
● View status of open service requests.
● View service history and reports about your systems, including uptime, remote fix and
service call trends, and other service delivery metrics.
If you do not have access to iCenter, contact your Director of Service or Field Engineer to open
an iCenter account. English-speaking customers can also use the following resources:
● GE Analytics Applications Answerline, 1 (800) 682–5327, option 8 (available for US and
Canadian customers).

Related Documentation
For information about using Analytics, refer to the Centricity Imaging Analytics Real-time
Dashboard User Manual

Documentation Conventions

2103201-001 4
Text
The following table lists text conventions in this manual.

Table 2 Text Convention Descriptions

Description Example
This typeface represents all On the File menu, click New.
buttons, entry fields, menus, and
other user interface controls.
This typeface represents window This opens the Preferences dialog.
and dialog box names.
This typeface represents text you Enter localhost in the proper field.
enter in a user interface control.
This typeface represents user Default user name: sysadmin
names and passwords and
commands you type in response
to a command prompt.
This typeface represents file path Open lib\readme.txt.
names.
This typeface represents See Documentation Conventions (page 4).
cross-references and other
hypertext links.

Screen Captures
The example screens in this manual may not represent what you see on your monitor; use
them only as guidelines.

Safety
Service manuals contain information for safe use of the device and will therefore follow
regulatory requirements set forth for directions for use.
Refer to the Centricity Imaging Analytics Operator Manual for safety and certification
information.

Warning — Service Manual Translations


Table 3 Service Manual Translations

Warning Explanation
Warning: ● This Service Manual is available in English only.
● If a customer’s service provider requires a language other than
English, it is the customer’s responsibility to provide translation
services.
● Do not attempt to service the equipment unless this service
manual has been consulted and is understood.

2103201-001 5
Warning Explanation
● Failure to heed this warning may result in injury to the service
provider, operator or patient from electric shock, mechanical or
other hazards.
Advarsel: ● Denne servicemanual er kun tilgængelig på engelsk.
● Hvis en kundes serviceudbyder kræver et andet sprog end
engelsk, er det undens ansvar at tilbyde oversættelse.
● Forsøg ikke at udøve service på udstyret, medmindre denne
servicemanual er læst og forstået.
● Hvis denne advarsel ikke iagttages, kan serviceudbyderen,
operatøren eller patienten pådrage sig skader som følge af
elektrisk stød, mekaniske fejl eller andre farer.
Warnhinweis: ● Dieses Kundendienst-Handbuch ist nur in englischer Sprache
erhältlich.
● Wenn der Kundendienst des Kunden eine andere Sprache
benötigt, liegt es in der Verantwortung des Kunden, eine
Übersetzung anfertigen zu lassen.
● Versuchen Sie nicht, das Gerät zu reparieren, bevor dieses
Kundendienst- Handbuch nicht zu Rate gezogen und verstanden
wurde.
● Wird diese Warnung nicht beachtet, so kann es zu Verletzungen
des Kundendiensttechnikers, des Bedieners oder des Patienten
durch elektrische Schläge, mechanische oder sonstige Gefahren
kommen.
Προειδο- ● Αυτό το Εγχειρίδιο σέρβις είναι διαθέσιμο μόνο στα αγγλικά.
ποίηση: ● Εάν ο παροχέας υπηρεσιών σέρβις του πελάτη απαιτήσει κάποια
άλλη γλώσσα εκτός από τα αγγλικά, είναι στην ευθύνη του πελάτη
να παρέχει υπηρεσίες μετάφρασης.
● Μην επιχειρήσετε να εκτελέσετε σέρβις του εξοπλισμού, πριν
συμβουλευτείτε και κατανοήσετε αυτό το εγχειρίδιο σέρβις.
● Μη συμμόρφωση με την οδηγία αυτή μπορεί να προκαλέσει
τραυματισμούς στον παροχέα σέρβις, χειριστή ή ασθενή από
ηλεκτροπληξία, μηχανικά αίτια ή άλλες πηγές κινδύνου.
Advertencia: ● Este manual de servicio sólo existe en inglés.
● Si el proveedor de servicios del cliente solicita un idioma que no
sea el inglés, es responsabilidad del cliente ofrecer un servicio
de traducción.
● No se deberá realizar el mantenimiento del equipo sin haber
consultado y comprendido este manual de servicio.
● La no observancia del presente aviso puede dar lugar a que
el proveedor de servicios, el operador o el paciente sufran
lesiones provocadas por causas eléctricas, mecánicas o de otra
naturaleza.
Figyelmezte- ● A szervizkönyv csak angol nyelven érhető el.
tés: ● Ha a vásárló szervizképviselete fordítást igényel a
szervizkönyvhöz, a vásárló felelősségi körébe tartozik fordítások
biztosítása.
● Ne kísérelje meg a berendezés szervizelését a szervizkönyv
elolvasása és a benne foglaltak megértése nélkül.
● Ennek a figyelmeztetésnek a figyelmen kívül hagyása a
szervizszakember, a kezelő vagy a páciens áramütés általi,
mechanikus vagy egyéb veszélyekből fakadó sérülését okozhatja.

2103201-001 6
Warning Explanation
Vakava ● Tämä huolto-opas on saatavissa vain englanninkielisenä.
varoitus: ● Jos asiakkaan palveluntarjoaja vaatii muunkielisen oppaan,
kääntäminen on asiakkaan vastuulla.
● Laitteistoa ei saa yrittää huoltaa, ellei tähän huolto-oppaaseen
ole perehdytty ja ellei sen sisältöä ole ymmärretty.
● Tämän varoituksen huomioimatta jättäminen voi johtaa
palveluntarjoajan, käyttäjän tai potilaan loukkaantumiseen
sähköiskun, mekaanisen vaaran tai muun vaaratekijän vuoksi.
Avertissement: ● Ce manuel de maintenance n'est disponible qu'en anglais.
● Si un technicien du client a besoin de ce manuel dans une autre
langue que l'anglais, il incombe au client de le faire traduire.
● Ne pas tenter d'intervention sur les équipements avant d'avoir lu
et assimilé les instructions de ce manuel d'entretien.
● Le non-respect de cet avertissement peut entraîner chez le
technicien, l'opérateur ou le patient des blessures dues à des
dangers électriques, mécaniques ou autres.
Avviso: ● Questo manuale di manutenzione è disponibile solo in inglese.
● Se un fornitore di servizi del cliente richiede una lingua diversa
dall'inglese, spetta al cliente provvedere ai servizi di traduzione.
● Non tentare di eseguire la manutenzione dell'apparecchiatura
prima di aver consultato e compreso questo manuale di
manutenzione.
● La mancata osservanza ti tale avvertenza può causare lesioni al
fornitore di servizi, all'operatore o al paziente, derivanti da scosse
elettriche, rischi meccanici o di altro tipo.
警告:

경고:

Waarschuwing: ● Deze servicehandleiding is alleen beschikbaar in het Engels.


● Als de persoon die voor de klant het onderhoud uitvoert een
handleiding in een andere taal nodig heeft, moet de klant zelf
voor deze vertaling zorgen.
● Lees deze servicehandleiding door en let op dat u de inhoud
begrijpt voordat u probeert het apparaat te onderhouden.
● Als dit niet gebeurt, kunnen de persoon die het onderhoud
uitvoert, de operator of de patiënt verwondingen oplopen door
elektrische schokken of mechanische of andere defecten.

2103201-001 7
Warning Explanation
Advarsel: ● Denne servicehåndboken er bare tilgjengelig på engelsk.
● Hvis kundens tjenesteleverandør krever et annet språk enn
engelsk, er det kundens ansvar å tilby oversettelsestjenester.
● Det må ikke utføres service på utstyret med mindre denne
servicehåndboken er lest og forstått.
● Hvis denne advarselen ikke tas hensyn til, kan det føre til skader
på tjenesteleverandøren, brukeren eller pasienten som følge av
elektrisk støt, mekaniske farer eller andre farer.
Ostrzeżenie: ● Niniejszy podręcznik serwisowy (Service Manual) został
opublikowany wyłącznie w języku angielskim.
● Jeśli dział serwisowy klienta chce korzystać z innej wersji
językowej podręcznika niż angielska, wówczas dostarczenie
pracownikom wersji przetłumaczonej leży w gestii klienta.
● Nie wolno wykonywać żadnych czynności serwisowych w
odniesieniu do sprzętu bez zapoznania się z treścią niniejszego
podręcznika serwisowego i zrozumienia jej.
● Niezastosowanie się do tego zalecenia może skutkować
obrażeniami ciała pracownika serwisu, operatora lub pacjenta
spowodowanymi porażeniem prądem czy zagrożeniami
mechanicznymi i innego typu.
Aviso: ● Este Manual de Assistência Técnica só se encontra disponível
em Inglês.
● Se qualquer outro serviço de assistência técnica, que
não a GEHC, solicitar estes manuais noutro idioma, é da
responsabilidade do cliente fornecer os serviços de tradução.
● Não tente reparar o equipamento sem ter consultado e
compreendido este Manual de Assistência Técnica.
● O não cumprimento deste aviso pode pôr em perigo a segurança
do técnico, operador ou provocar choques eléctricos, falhas
mecânicas ou outros perigos.
Advertência: ● Este Manual de Serviços está disponível somente em inglês.
● Se um prestador de serviços do cliente precisar de um idioma
diferente do inglês, será responsabilidade do cliente fornecer
serviços de tradução.
● Não tente fazer a manutenção do equipamento a menos que
este manual de serviço tenha sido consultado e compreendido.
● Se este aviso não for seguido, poderá ocorrer dano ao prestador
de serviços, operador ou paciente em razão de choque elétrico,
problemas mecânicos ou outros perigos.
Предупрежде- ● Это руководство по обслуживанию доступно только на
ние: английском языке.
● Если поставщик услуг клиента требует предоставить
руководство на другом языке, выполнение перевода
возлагается на клиента.
● Не выполняйте сервисное обслуживание оборудования до
тех пор, пока это руководство по обслуживанию не будет
прочитано и принято к сведению.
● Игнорирование этого предупреждения может привести к
поражению электрическим током, механическим и другим
травмам поставщика услуг, оператора или пациента.

2103201-001 8
Warning Explanation
Varning: ● Den här servicehandboken är endast tillgänglig på engelska.
● Om en kunds serviceleverantör behöver en handbok på ett
annat språk är det kundens ansvar att stå för eventuella
översättningstjänster.
● Försök inte utföra service på utrustningen om du inte har läst
och förstått servicehandboken.
● Om denna varning inte beaktas kan elchock, mekaniska problem
eller andra faror innebära att serviceleverantören, operatören
eller patienten skadas.
Uyarı: ● Bu Servis Kılavuzu yalnızca İngilizce olarak mevcuttur.
● Bir müşterinin servis sağlayıcısının İngilizce dışında bir dile
ihtiyacı olması durumunda çeviri hizmetlerini sağlamak müşterinin
sorumluluğundadır.
● Bu servis kılavuzuna başvurmadan ve kılavuz anlaşımadan
ekipmana servis işlemi uygulama girişiminde bulunmayın.
● Bu uyarıya dikkat edilmemesi servis sağlayıcının, operatörün
ya da hastanın elektrik çarpması, mekanik tehlikeler ve diğer
tehlikeler nedeniyle yaralanmasına neden olabilir.
警告:

警告:

Terms, Acronyms, and Abbreviations


For a listing of commonly used terms, acronyms, and abbreviations, see Glossary (page 230).

2103201-001 9
Contents
About This Manual .............................................................................................. 4
Contacting GE Support ......................................................................................... 4
Contacting the ROC ....................................................................................... 4
Applications Support Using iCenter, Applications Answerline, and Customer
Center ..................................................................................................... 4
Related Documentation......................................................................................... 4
Documentation Conventions ................................................................................. 4
Text .............................................................................................................. 5
Screen Captures ........................................................................................... 5
Safety .................................................................................................................. 5
Warning — Service Manual Translations .......................................................... 5
Terms, Acronyms, and Abbreviations ..................................................................... 9

1 Pre-installation ................................................................................................ 14
1.1 Minimum System Requirements..................................................................... 14
1.1.1 Minimum Server Hardware Requirements.............................................. 14
1.1.2 Software Requirements for the Server ................................................... 15
1.1.3 Third-Party Software Requirements for the Client ................................... 16
1.1.4 Minimum Hardware Requirements For VM............................................. 17
1.2 SQL Server Data Worksheet.......................................................................... 17
1.3 Submit the ROC VPN Form ........................................................................... 18
1.4 Install or Upgrade CCG ................................................................................. 18
1.5 VPN Concentrator......................................................................................... 19
1.6 Workflow Understanding and HL7 Site Survey ................................................ 19
1.7 Authentication............................................................................................... 19
1.8 Microsoft Active Directory Domain Integration ................................................. 20
1.8.1 User Management................................................................................ 20
1.8.2 Systems Management.......................................................................... 20
1.8.3 Configuration Management................................................................... 20
1.8.4 Central Software Deployment ............................................................... 21
1.9 Modality Interfacing to CCG ........................................................................... 21
1.10 HL7 and ENM Mapping ............................................................................... 21

2 Install SQL Server 2008 .................................................................................. 22


2.1 Install SQL Server 2008 R2 ........................................................................... 22

3 Install or Upgrade SQL Server 2014 .............................................................. 32


3.1 Prerequisites for Installing SQL Server 2014................................................... 32
3.2 Upgrade SQL Server 2014 ............................................................................ 36

2103201-001 10
3.3 Fresh Installation .......................................................................................... 42

4 Business Analytics Software Installation / Upgrade ................................... 52


4.1 Configure the RAID ....................................................................................... 53
4.2 Install the Server OS ..................................................................................... 55
4.3 Install IIS Web Services................................................................................. 56
4.4 Make the Server IP Address Static ................................................................. 58
4.5 Add .NET Framework Features...................................................................... 60
4.6 Enable Static Content on the Web Server ....................................................... 61
4.7 Configure Automatic Updating ....................................................................... 61
4.8 Check to Make Sure the Software Installed at this Point Is Correct ................... 61
4.9 Install Analytics............................................................................................. 63
4.10 Set the Maximum SQL Server Memory Usage .............................................. 68
4.11 Change/Verify the Default Passwords ........................................................... 69
4.12 Upgrade Analytics ....................................................................................... 71
4.13 Configure SSL with Analytics (Optional)........................................................ 79
4.14 Post-Installation Verification Checklist........................................................... 79
4.15 Location of Analytics_Prod .......................................................................... 84
4.16 Install on VMware ....................................................................................... 84

5 CCG Baseline Installation .............................................................................. 85


5.1 CCG 8.0.2 .................................................................................................... 85
5.1.1 Running the CCG 8.0 Installer Wizard ................................................... 85
5.1.2 Verify the Installation ............................................................................ 87
5.1.3 Configure the Backup ........................................................................... 88
5.1.4 Post Installation Procedures ................................................................. 88
5.2 CCG 9.3.2 .................................................................................................... 91
5.2.1 Centricity Clinical Gateway Interface Engine Installation ......................... 91
5.2.2 Active Perl Installation .......................................................................... 95
5.2.3 CCG Components Installation ............................................................... 99
5.2.4 Set User and for Scheduled Tasks........................................................105
5.2.5 Post Installation Checks ......................................................................107
5.3 CCG v9.3.7 .................................................................................................108

6 CCG Upgrade ................................................................................................ 109


6.1 CCG 8.0.2 ..................................................................................................109
6.1.1 Prepare the Upgrade for CCG..............................................................109
6.1.2 Upgrade CCG ..................................................................................... 113
6.1.3 Running the CCG 8.0 Installer Wizard .................................................. 114
6.1.4 Verify the Upgrade .............................................................................. 117
6.1.5 Manually Restore the Backup Location and Schedule............................ 117

2103201-001 11
6.1.6 Autostart of Interfaces ......................................................................... 118
6.1.7 Restart the System or Hand Off to ITPS for Integration .......................... 118
6.2 CCG 9.3.2 .................................................................................................. 118
6.2.1 CCG Upgrade Worksheet .................................................................... 118
6.2.2 Pre-Upgrade Checks ...........................................................................120
6.2.3 Pre-Upgrade Procedures .....................................................................120
6.2.4 CCG System State Back Procedures....................................................120
6.2.5 Centricity Clinical Gateway (CCG) Interface Engine Upgrade .................123
6.2.6 ActivePerl Installation ..........................................................................126
6.2.7 Centricity Clinical Gateway (CCG) Components Upgrade ......................126
6.2.8 Restoring Interfaces ............................................................................128
6.2.9 CCG Configuration..............................................................................144
6.3 CCG v9.3.7 Upgrade....................................................................................152

7 How to Connect Analytics to CCG Using Tcl ODBC.................................. 153


7.1 Obtain the Tcl ODBC Zip File ........................................................................153
7.2 Install Tcl ODBC...........................................................................................153
7.3 Configure the Windows ODBC Connection ....................................................154
7.4 Testing the Tcl ODBC Connection .................................................................157
7.5 Configure the Tcl Procedures to Communicate with Analytics .........................159
7.6 Validate the Configuration.............................................................................161

8 Site Configuration ......................................................................................... 163


8.1 Edit the Client Configuration Files .................................................................163
8.1.1 GridColumns.config.............................................................................164
8.2 How to Change the Backup Configuration .....................................................164
8.2.1 Differential Backups ............................................................................167
8.2.2 How to Restore the Database Backup ..................................................167
8.2.3 Other Database Maintenance ..............................................................168
8.3 Load Master File Data ..................................................................................168
8.3.1 Update Relative Value Units (RVU) using Master File Data ....................169
8.4 CCG Interface Management .........................................................................170
8.5 Map HL7 to Analytics Parameters .................................................................171
8.6 How to Give Users Access to Analytics .........................................................171
8.7 Summary Table Jobs....................................................................................171
8.8 Enable/Disable EVENTS view Indexes Job....................................................174
8.9 Fragmentation/Defragmentation Jobs............................................................176
8.10 Adding Email Notification for SQL Server Jobs.............................................181

9 Analytics Administration and Customization............................................. 195


9.1 How to Log In to the Settings Screen ............................................................195

2103201-001 12
9.2 How to Add, Edit, or Delete a Setting ............................................................196
9.2.1 Using Exam Modifiers..........................................................................197
9.2.2 Create/Update Reason For Delay.........................................................198
9.2.3 Setting Ignore Demotion for an Exam Status.........................................199
9.2.4 Configure Ignore Timestamp when Promoting Events............................200
9.2.5 Create/Update a Staff..........................................................................201
9.2.6 Configuring Remote Alerts ...................................................................202
9.2.7 Settings Filters ....................................................................................202
9.3 Using User Statistics from Service Console ...................................................203
9.4 Assigning Users to Groups ...........................................................................204
9.5 Viewing Analytics Events in the Event Log.....................................................205
9.6 Customizing an Operational Metric (KPI) .......................................................206
9.7 Mapping Exam Events to RVU Components ..................................................207
9.8 Optimizing the Database ..............................................................................207

A Troubleshooting ........................................................................................... 210


A.1 Troubleshooting Table..................................................................................210
A.2 Create a User in SQL Server........................................................................210
A.3 Usage of Database Flags.............................................................................215

B PACS Events ................................................................................................. 219

C Cloverleaf License Request Process ......................................................... 221


C.1 Definitions...................................................................................................221
C.2 Identify Customer Configuration ...................................................................221
C.2.1 Host ID of the System .........................................................................222
C.3 License Key Request and Installation ...........................................................223
C.4 Sample Product Deployment Configurations .................................................227

2103201-001 13
1
Pre-installation
Important: Procedures in this manual require using GE-supplied
default passwords. Contact the GE Helpdesk to obtain the default
passwords.

The primary purpose of the pre-installation process is to work with the customer to
ensure that the customer site is properly set up to support installation of the Centricity
Imaging Analytics components they ordered. The pre-installation process involves several
functional groups, including:
● The customer
● GE Healthcare Service Group
● GE Healthcare Project Managers (PMs)
● GE Healthcare Field Engineers (FEs)
● GE Healthcare Zone Support Engineers (ZSEs)
● GE System Integration Specialist (SIS)
● GE Healthcare Clinical Configuration Specialists (CCSs)

1.1 Minimum System Requirements


The following minimum system requirements must be met. Install or upgrade your
software and/or hardware to meet these requirements.

1.1.1 Minimum Server Hardware Requirements


Customers who purchase GE supplied Analytics hardware and software receive
recommended hardware with the purchased software pre-installed.
Customer supplied server hardware should meet the specifications below.

2103201-001 14
Chapter 1: Pre-installation

Table 4 Recommended servers

Server Part Link to Technical Specifications Page


Number
Dell R710 Dell — For power and environmental specifications, see Tech Specs on Dell’s web
Server 2670748 page at: http://www.dell.com/us/business/p/poweredge-r710/pd?refid=server-
poweredge-
r710&=baynote_bnrank=1&baynote_irrank=0&~ck=baynoteSearch
HP DL380 Hewlett For power and environmental specifications, see Specifications on HP’s web page
Server Packard — at: http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/15351-15351-3328412-
BT291A 241644-241475-4091412.html

Note Customer supplied hardware must meet the following standards: IEC 60950-1
(or equivalent), IEC CISPR-22 (or equivalent), IEC-CISPR-24 (or equivalent).
● Intel 64 bit capable of 2.00GHz, or more (Intel 64/EM64T, AMD64/x86-64).
Note: Analytics is not compatible with the IA-64 architecture from Intel.

● 2 or more sockets
● Dual core or higher, per socket
● Minimum of 4 cores, per server
● 24GB RAM, or higher
● Storage attached to Ultra SCSI 320, SAS, Fibre channel, or equivalent SAN controller
with 256MB or higher of write back battery backed cache.
● DVD drive
● 120GB of disk storage for database
● 20GB of disk storage for operating system and application software
● 6 or more physical hard drives:
RAID Configuration:
● Last hard drive reserved as a hard spare.
● The 2 hard drives before that as RAID 1.
● Remaining hard drives as RAID 5.
● Ultra SCSI 320 or Fibre channel (or equivalent) disks of 10,000 RPM, or higher

1.1.2 Software Requirements for the Server


Note Analytics uses an x86 platform for its server hardware. It is not compatible
with Intel's IA-64 architecture.
● If the customer purchases the server hardware and software from GE, the purchased
software listed in Table 5 is pre-installed on the server.
● If the customer purchases the software from GE (but purchases the hardware from
another source), the customer provide the OS installed on the server, then the GE
Service Representative installs the other software listed in Table 5.

2103201-001 15
Chapter 1: Pre-installation

Table 5 Software requirements

Centricity Imaging Analytics Installer included on the Analytics media.


Data Aggregation Engine
Centricity Imaging Analytics License purchased separately. Installer included on the
Real-time Dashboard Analytics media.
(optional)
Centricity Imaging Analytics License purchased separately. Installer included on the
Operational Metrics Engine Analytics media. This option is required by the Real-time
(optional) Dashboard.
Microsoft SQL Server 2008 License purchased separately. SQL Server is not part
R2 (v10.50.1600.2) or SQL of Analytics media. It is separate media that customer
Server 2014 Enterprise / need to buy from catalog.
Standard Edition
Dundas Dashboard License purchase is included with the Real-time
Dashboard. Included on the Analytics media. License
key is built into the Analytics installer. No “client access
license” is required.
Microsoft Windows Server License included with hardware purchased from GE.
Standard 2008 R2 64–bit / Customers who do not purchase the hardware from GE
Microsoft Windows Server are responsible for installing the OS.
2012 Note Analytics also requires installation of Internet
Information Server (IIS) (which is built into Windows
Server).
OS recovery media is shipped with the hardware.
Centricity Clinical Gateway License purchased separately. You may install CCG
8.0.1 (optional) on the Analytics server or use an existing CCG 8.0.1
or greater system on another server. CCG ships on
separate media from Analytics. This option is required
by the Operational Metrics Engine and Real-time
Dashboard.

Note If the customer does not purchase the hardware from GE, the hardware
provider should be able to pre-configure it with the OS and the RAID.

1.1.3 Third-Party Software Requirements for the Client


The Analytics client application is able to detect whether the recommended version of
Microsoft Silverlight and Microsoft .NET is installed. If it is not, Analytics opens a message
dialog listing the missing software and giving instructions for obtaining the software.
Note Certain IT departments lock down installs on client PCs. If so, Silverlight
and .NET will not automatically install on clients. In this situation, the
site IT department is responsible for installing the proper versions of
Silverlight and .NET on all client PCs. The .NET installer is located at:
<Analytics Media>\Prerequisite\dotNetFx40_Full_x86_x64.exe. The
Silverlight installer is located at: <Analytics Media>\Prerequisite\Silverlight
Plugin\Silverlight.exe.
Analytics runs on OS versions and web browser versions supported by Silverlight 4.0.
● Microsoft Silverlight 4.0 (version 4.0.50826.0) plug in, or later
● Microsoft .NET 4.0 (version 4.0.30319.1) run time, or later
● Refer to Microsoft’s web site for information about system requirements for Microsoft
Silverlight.

2103201-001 16
Chapter 1: Pre-installation

1.1.4 Minimum Hardware Requirements For VM


Below are the minimum hardware specifications needed for VMware.
● 8v Cores or higher (recommended 16 v Cores)
● 24 GB vRAM or higher (recommended 64)
● DVD drive
● Storage supporting 1800 IOPS
● 150GB of disk storage for database on RAID 5
● 30GB of disk storage for operating system and application software on RAID 1
● Storage partitions:
● 300 GB – OS, Application Software (RAID 1+0)
● 120 GB Data (RAID-5)
● 30 GB Indexes (RAID-5)
● 5 GB Transaction Log (RAID 1+0))
● 5 GB Temp DB (RAID 1+0)
● 120 GB Backups (RAID-5) – optional network backup recommended
● DVD drive to install software

1.2 SQL Server Data Worksheet


If the site is using an existing SQL Server database, use a printout of the following
worksheet to record data about the database. Keep the filled out form as you perform
the installation.
Important If a database already exists on the SQL Server, a trained and
knowledgeable customer representative should add the Analytics
database to the SQL Server.
Component Required Data Entry
Network IP Address
Information
Hostname

Note Valid characters include A-Z, 0-9, the


underscore and hyphen. Maximum length
is 8 characters.
Subnet Mask
Gateway
ILO (HP) or
DRAC (Dell) IP
Address

2103201-001 17
Chapter 1: Pre-installation

Component Required Data Entry


Password Default User
Password
There are no requirements as to the length,
special characters, etc., for the password.
Default
Administrator
Password
There are no requirements as to the length,
special characters, etc., for the password.
Database backup
schedule
Full Backup (day of week and time).

1.3 Submit the ROC VPN Form


Be sure that the customer and the ROC are aware that the following ports must be open
on the site firewall and the ROC firewall:
● SNMP – 161
● SQL Server – 1433
● SSH – 22
● Web Server – 80, 443
● Windows RDP – TCP 3389
Note The FE should add a note on the VPN form that details which ports need
to be open.

1.4 Install or Upgrade CCG


Analytics requires CCG version 8.0.1 or higher. The site can either use a pre-existing
CCG installation or can install CCG on the Analytics server.
● To upgrade a pre-existing CCG system to 8.0.1 or higher, check for CCG compatibility
with the existing PACS system using the PACS compatibility matrix. Refer to the
appropriate version of the CCG for PACS Installation and Upgrade Manual for CCG
upgrade instructions.
● To install a new CCG system, see CCG Baseline Installation.
Wait until after you have installed Analytics before installing a new CCG system. The
new CCG system then uses the same SQL Server as Analytics.

2103201-001 18
Chapter 1: Pre-installation

1.5 VPN Concentrator


● The customer supplies the VPN concentrator.
● The Project Manager supplies the IP addresses to the Field Engineer.
● The Field Engineer submits the ROC VPN form, which includes a request to open
the required nonstandard ports.
● The ROC team works with the customer to configure the VPN and adds it to the
GE ROC internal VPN.

1.6 Workflow Understanding and HL7 Site


Survey
The HL7 integration team works with the customer to complete this document.

1.7 Authentication
If the site uses Windows Active Directory authentication (and would like to continue using
their domain login to access Analytics), add the Analytics server to the domain. You can
add a new Active Directory domain and add Analytics to that new domain. Any valid user
account in the domain to which the Analytics server is assigned can be used to log in to
the Analytics application. See your Active Directory manual or online help for information
about adding a domain and user.
Note When creating a new user in the Active Directory Users for Authentication,
make sure that the User must change password at next logon option is
NOT selected.
If the site does not want to use Active Directory domain logins, create Windows user
accounts on the Analytics server using operating system provided tools. Any valid
Windows user account on the Analytics server can be used to log in to the Analytics
application.

2103201-001 19
Chapter 1: Pre-installation

1.8 Microsoft Active Directory Domain


Integration
Analytics may be placed in a Microsoft Active Directory (AD) domain, but the following
topics should be carefully considered and prepared together with the customer beforehand.

1.8.1 User Management


A key benefit of joining an AD domain is that it can give domain users the access to
Analytics. It can also give domain groups the access to the Analytics. Another key
benefit is the easier setup of authentication for accessing network shares for network
backup purposes.

1.8.2 Systems Management


By default, joining an AD domain will make Domain Administrators members of the local
group "Administrators" and therefore give them full control over the Analytics server. For
example, Administrators:
● Can access and change stored data
● Can access and change system and application configuration
● Can alter access control lists
● Are entitled for remote access by default
The activities of Windows users within Analytics are logged using a Windows event
logging mechanism, but no explicit work has been done on the server to shield IT
administrators from accessing patient health information. This is a security, data-integrity,
and patient-data-privacy concern of which the customer should be fully aware.
It is the customer’s responsibility to carefully manage this concern with proper
employee policies and controls before placing the system in an AD domain!

1.8.3 Configuration Management


Joining an AD domain makes the Analytics server allow for its configuration via Group
Policy (GPO). However, GPOs have been a major cause of problems as a direct result of
placing systems in an AD domain.
Once downloaded to a local system, GPO can be hard to detect as the cause of problems
and hard to reset locally. Great care should therefore be taken to exclude the Analytics
server from any general-purpose GPO rollout.
Examples of commonly used GPOs that cause issues are password age rules and
password complexity rules. Analytics does not provide the ability to change domain
passwords. This may lead to user inconvenience at those sites where the end users do
not typically log in to the domain from workstations where they run this application or
from outside the facility, such as from home.
Additionally, firewall rules typically meant for workstations inhibit access on Port 80 and
443 which, if applied to this server, will stop it from serving up web pages.
Customers are strongly advised to ensure the GPOs applied to the Analytics server
do not inhibit its ability to perform as a web server!

2103201-001 20
Chapter 1: Pre-installation

1.8.4 Central Software Deployment


Joining an AD domain opens up the possibility for central software deployment.
Customers can install patches and software that are compatible with SQL Server 2008 R2
and IIS 7. Patches and software that require reboot should not be installed automatically;
they should be scheduled with GE support prior to patch installation. Also, deploying
unnecessary software and patches can potentially affect the performance of the system.

1.9 Modality Interfacing to CCG


DMWL MPPS Service should be selected during CCG installation in order to interface
with modalities. (See Running the CCG 8.0 Installer Wizard.)
See the MPPS Configuration chapter in the Centricity Clinical Gateway Service Manual for
information about configuring CCG for MPPS.

1.10 HL7 and ENM Mapping


GE Support Representatives should have a spreadsheet specifying HL7 and ENM
mapping information.

2103201-001 21
2
Install SQL Server 2008
2.1 Install SQL Server 2008 R2
To install SQL Server 2008 R2:
1. Right-click <SQL Server 2008 Install Location>\Setup.exe and select Run as
Administrator from the context menu.
Figure 1 Run SQL Server 2008 R2 Setup

2. When the SQL Server Installation Center window opens, select Installation. Choose
the option New installation or add features to an existing installation.

2103201-001 22
Chapter 2: Install SQL Server 2008

Figure 2 Choose New Installation

3. On the Setup Support Rules window, click OK.


Figure 3 Setup Support Rules

4. Provide the product key and click Next.

2103201-001 23
Chapter 2: Install SQL Server 2008

Figure 4 Provide Product Key for SQL Server 2008 R2

5. Read and accept the Microsoft Software License Terms and click Next.
Figure 5 Accept License Terms

6. Click Install to install setup support files. It should be completed without failures.
Click Next.

2103201-001 24
Chapter 2: Install SQL Server 2008

Figure 6 Install Setup Support Files

Figure 7 Installation of Setup Support Files in Progress

7. Provide the product key in the Product Key window and click Next.
8. Read and accept the Microsoft Software License Terms and click Next.
9. In Setup Role window, select SQL Server Feature Installation and click Next.

2103201-001 25
Chapter 2: Install SQL Server 2008

Figure 8 Select Setup Role as SQL Server Feature Installation

10. Select all the features to be installed and click Next.


Figure 9 Select SQL Server Features to install

11. Choose the default instance and specify instance ID of the SQL Server as
MSSQLSERVER and click Next.

2103201-001 26
Chapter 2: Install SQL Server 2008

Figure 10 SQL Server Name and Instance ID

12. Review Disk Space Requirements and click Next.


Figure 11 Disk Space Requirements

13. Specify the server configuration details and click Next.

2103201-001 27
Chapter 2: Install SQL Server 2008

Figure 12 Server Configuration

14. In Database Engine Configuration, specify the authentication mode as Mixed Mode
and provide the password. Specify SQL Server system administrators or click Add
Current User. Click Next.
Figure 13 Database Engine Configuration

2103201-001 28
Chapter 2: Install SQL Server 2008

15. In Analysis Services Configuration, add administrative user. Click Add Current
User. Click Next.
Figure 14 Analysis Services Configuration

16. In Reporting Services Configuration, specify the reporting services native mode as
Install the native mode default configuration . Click Next.
Figure 15 Reporting Services Configuration

2103201-001 29
Chapter 2: Install SQL Server 2008

17. Choose Error Reporting if required. Click Next.


Figure 16 Error Reporting

18. Ensure Installation Configuration Rules have passed and click Next.
Figure 17 Installation Configuration Rules

2103201-001 30
Chapter 2: Install SQL Server 2008

19. Verify the SQL Server 2008 R2 features to be installed and click Install. Wait for
the install to complete.
Figure 18 Start SQL Server 2008 R2 Installation

20. When the installation of SQL Server 2008 R2 is completed, click Close.
Figure 19 SQL Server 2008 R2 Installation Completed

2103201-001 31
3
Install or Upgrade SQL Server 2014
Prerequisites for Installing SQL Server 2014
Upgrade SQL Server 2014
Fresh Installation

3.1 Prerequisites for Installing SQL Server


2014
.NET Framework 3.5 must be installed.
Before installation, user should know the alternate path for the server source files on the
installation media.
To install .NET Framework 3.5:
1. Launch Server Manager by pressing Windows key + R to get the Run command
window and type ServerManager. In Server Manager, click Manage and then select
Add Roles and Features to start the Add Roles and Features Wizard.

2103201-001 32
Chapter 3: Install or Upgrade SQL Server 2014

Figure 20 Select Add Roles and Features

2. On the Before you begin screen, click Next .


3. On the Select installation type screen, select Role-based or feature-based
installation and click Next.
4. Select the target server and click Next.
5. On the Server Roles screen, select Web Server(IIS) and click Next.
6. On the Features screen, select .NET Framework 3.5 Features . On the Add Features
Wizard window, click Add Features. Click Next.
Figure 21 Add .NET Framework 3.5 Features

2103201-001 33
Chapter 3: Install or Upgrade SQL Server 2014

Figure 22 Feature Wizard

7. Specify an alternate source path link to specify the path to the \sources\sxs folder on
the installation media and then click OK.
Figure 23 Select Alternate Path for Source Files

2103201-001 34
Chapter 3: Install or Upgrade SQL Server 2014

Figure 24 Alternate Path for Source Files

8. On the Confirm Installation Selections window, click Install.


Figure 25 Install Features

Expected Result: Installation begins and an Installation Progress is displayed.


9. When the Installation Succeeded message displays on the Installation Results
window, click Close.
Expected Result:.NET Framework 3.5 Features are now installed.

2103201-001 35
Chapter 3: Install or Upgrade SQL Server 2014

3.2 Upgrade SQL Server 2014


To upgrade to SQL Server 2014 from SQL Server 2008/2012:
Note If upgrading from SQL Server 2008 R2, then you should at least have SP2
installed.
1. Right-click <SQL Server 2014 Install Location>\Setup.exe and select Run as
Administrator from the context menu.
Figure 26 Run SQL Server 2014 Setup

2. When the SQL Server Installation Center window opens, select Installation. Choose
the option Upgrade from SQL Server 2005, SQL Server 2008, SQL Server 2008
R2 or SQL Server 2012.

2103201-001 36
Chapter 3: Install or Upgrade SQL Server 2014

Figure 27 Choose Upgrade SQL Server

3. Provide the product key and click Next.


Figure 28 Provide Product Key for SQL Server 2014

4. Read and accept the Microsoft Software License Terms and click Next.

2103201-001 37
Chapter 3: Install or Upgrade SQL Server 2014

Figure 29 Accept License Terms

5. Specify the instance of SQL Server to modify and click Next.


Figure 30 Select SQL Server Instance to upgrade

6. Select all the features to be upgraded and click Next.

2103201-001 38
Chapter 3: Install or Upgrade SQL Server 2014

Figure 31 Select SQL Server Feature to upgrade

7. Specify the name and instance ID of the SQL Server as MSSQLSERVER and click
Next.
Figure 32 SQL Server Name and Instance ID

8. Specify the service account details and click Next.

2103201-001 39
Chapter 3: Install or Upgrade SQL Server 2014

Figure 33 Specify Server Configuration

9. Choose full-text upgrade option as Import and click Next.


Figure 34 Full-text Upgrade Option

10. Verify the SQL Server 2014 features to be upgraded and click Upgrade. Wait for
the upgrade to complete.

2103201-001 40
Chapter 3: Install or Upgrade SQL Server 2014

Figure 35 Start SQL Server 2014 Upgrade

11. When the upgrade of SQL Server 2014 is completed, you will be prompted to restart
your machine. Click OK and then Close.
Figure 36 SQL Server 2014 Upgrade Complete

Expected Result: The upgrade is complete. To verify, go to Start > All Programs >
Microsoft SQL Server 2014 and check whether all features are installed.

2103201-001 41
Chapter 3: Install or Upgrade SQL Server 2014

Figure 37 SQL Server 2014 Installed

3.3 Fresh Installation


To install SQL Server 2014:
1. Right-click <SQL Server 2014 Install Location>\Setup.exe and select Run as
Administrator from the context menu.

2103201-001 42
Chapter 3: Install or Upgrade SQL Server 2014

Figure 38 Run SQL Server 2014 Setup

2. When the SQL Server Installation Center window opens, select Installation. Choose
the option New SQL Server stand-alone installation or add features to an existing
installation.
Figure 39 Choose New SQL Server Installation

3. Provide the product key and click Next.

2103201-001 43
Chapter 3: Install or Upgrade SQL Server 2014

Figure 40 Provide Product Key for SQL Server 2014

4. Read and accept the Microsoft Software License Terms and click Next.
Figure 41 Accept License Terms

5. Choose Microsoft update if required and click Next.

2103201-001 44
Chapter 3: Install or Upgrade SQL Server 2014

Figure 42 Microsoft Update

6. In Install Rules window, click Next.


Figure 43 Install Rules

7. In Setup Role window, select SQL Server Feature Installation and click Next.

2103201-001 45
Chapter 3: Install or Upgrade SQL Server 2014

Figure 44 SQL Server Feature Installation selected

8. Click on Select All button under the features to be installed and click Next. Make
sure the software listed as Prerequisites for selected features are already installed
in the system.
Figure 45 Select SQL Server Feature to install

2103201-001 46
Chapter 3: Install or Upgrade SQL Server 2014

9. Choose the default instance and specify instance ID of the SQL Server as
MSSQLSERVER and click Next.
Figure 46 SQL Server Name and Instance ID

10. In the Server Configuration , change the Start Up type of each service as displayed in
the below screen and click Next.

2103201-001 47
Chapter 3: Install or Upgrade SQL Server 2014

Figure 47 Server Configuration

11. In Database Engine Configuration, specify the authentication mode as Mixed Mode
and provide the password. Specify SQL Server system administrators or click Add
Current User. Click Next.
Figure 48 Database Engine Configuration

2103201-001 48
Chapter 3: Install or Upgrade SQL Server 2014

12. In Analysis Services Configuration, specify the server mode as Multidimensional and
Data Mining Mode and add administrative user. Click Add Current User. Click Next.
Figure 49 Analysis Services Configuration

13. In Reporting Services Configuration, specify the reporting services native mode as
Install and configure. Click Next.
Figure 50 Reporting Services Configuration

2103201-001 49
Chapter 3: Install or Upgrade SQL Server 2014

14. Click on Add Current User in Distributed Replay Controller. Click Next.
Figure 51 Distributed Replay Controller

15. In Distributed Replay Client, provide the controller name as Voyager and click Next.
Figure 52 Distributed Replay Client

2103201-001 50
Chapter 3: Install or Upgrade SQL Server 2014

16. Verify the SQL Server 2014 features to be installed and click Install. Wait for the
install to complete.
Figure 53 Start SQL Server 2014 Installation

17. When the installation of SQL Server 2014 is completed, click Close.

2103201-001 51
4
Business Analytics Software
Installation / Upgrade
Fresh Installation
Upgrade Analytics

If the customer purchased the software and the server hardware from GE, the Analytics
and CCG software will already be installed. Skip to Site Configuration on page 163. This
chapter shows how to intall Analytics when the customer has purchased a software-only
system.

Note For a fresh installation to 1.4, both the Centricity Analytics v1.4 SP1 media
and the Centricity Analytics v1.4 SP2 patch are required.

Note Before installing Analytics, refer to the customer purchase order to verify the
options that were purchased.
Note For all of the installation procedures, log in to an account with system
administrator privileges.
● If you are starting with a new server with nothing installed, configure the RAID and
install the operating system. Refer to the instructions for configuring the RAID
distributed with the server. In most cases, the hardware vendor or GE Healthcare
Manufacturing will configure the RAID and install the operating system.
RAID Configuration:
● Last hard drive reserved as a hard spare.
● The 2 hard drives before that as RAID 1.
● Remaining hard drives as RAID 5.
These instructions include OS installation instructions for your convenience, in case
you have to re-baseline the system (Install the Server OS (page 55)).
● Once you have a system with a configured RAID and a supported Windows Server
installed, install the supported SQL Server and the Analytics software.
If it is purchased from GE catalog, it needs to be installed first. SQL authentication
should be enabled. Also, remember the password for the sa user.
1. Install IIS Web Services (page 56)
2. Make the Server IP Address Static (page 58)
3. Add .NET Framework Features (page 60)
4. Enable Static Content on the Web Server (page 61)

2103201-001 52
Chapter 4: Business Analytics Software Installation / Upgrade

5. Configure Automatic Updating (page 61)


6. Check to Make Sure the Software Installed at this Point Is Correct (page 61)
7. Install Analytics (page 63)
8. Set the Maximum SQL Server Memory Usage (page 68)
9. Post-Installation Verification Checklist (page 79)

4.1 Configure the RAID


Prerequisites:
● The Microsoft Windows Server DVD
● At least 6 hard drives

Configure the RAID if it is not already set up.


RAID Configuration:
● Last hard drive reserved as a hard spare.
● The 2 hard drives before that as RAID 1.
● Remaining hard drives as RAID 5.
1. Insert the Server OS DVD into the DVD drive. Then, restart the machine.
You are going to set up a RAID, then install the OS.
Note: HP servers come with a Smartstart DVD which has a configuration GUI
which you can use to set up the RAID. Though the interface is different
than the one shown here, the settings are the same. Other hardware
may come with a similar GUI.
2. During server boot up, press F8 to access the configuration screen.
Note: It is sometimes tricky to get the timing right on pressing F8. If the system
opens something other than the configuration screen, reboot and try
again. Also, some computers use a different function key to open the
configuration screen. When booting, the computer might briefly flash a
message telling you what key to press.
3. On the main menu screen, select the option to configure the RAID or create a logical
drive.
Note: In the configuration screens, you navigate using the keyboard. Navigation
instructions should be shown on screen.Use the UP and DOWN arrow keys
to scroll. Click TAB to navigate between sections. Use the SPACE BAR
to check or uncheck a selection.
4. Create a partition for the first drive. Under Available Physical Drives, select all but the
last three HDD drives.
5. Under RAID Configurations, select RAID 5.
6. Under Spare, select Use one drive as spare.
7. Under Maximum Boot Partition, select Enable. Press ENTER.

2103201-001 53
Chapter 4: Business Analytics Software Installation / Upgrade

Note: This screenshot is a sample. The actual HDD specification may differ.
8. Press F8 to save the configuration.
9. On the main menu, select the option to configure the RAID or create a logical drive.
10. Create a partition for the next drive. Under Available Physical Drives, select the
remaining drives.
11. Under RAID Configurations, select RAID 0.
12. Under Maximum Boot Partition, select Disable.
13. Under Spare, deselect Use one drive as spare. Press ENTER.

Note: This screenshot is a sample. The actual HDD specification may differ.
14. Press F8 to save the configuration.
15. Press ESCAPE to exit.
Expected Result:The RAID is now configured. The system reboots.
Next: After the system reboots, install the server OS.

2103201-001 54
Chapter 4: Business Analytics Software Installation / Upgrade

4.2 Install the Server OS


Prerequisite:
● The RAID must be properly configured. (See Configure the RAID (page 53)).

If you are installing the OS (rather than installing Analytics on a machine with a
pre-installed OS), you may have also configured the RAID on the system. After you
configure the RAID, the system reboots. During the system reboot, you will see an
installation window for Windows Server.
1. Click Install Now.
2. On the Select the operating system you want to install window, select Windows
Server 2008 R2 Standard (Full Installation) / Windows Server 2012 R2 Standard
(Server with a GUI). Click Next.
3. On the license terms window, select I accept the license terms. Click Next.
4. On the Which type of installation do you want? window, select Custom (Advanced).
Click Next.
5. Click Next.
6. Choose the boot disk.
If a Where do you want to install Windows? window opens, select Disk 0 for OS
installation and click Next. Disk 0 becomes the C: drive.
Expected Result: The installation begins. Upon completion, the system automatically
restarts.
7. Before logging in for the first time, specify a new password and confirm.
Expected Result: A popup tells you that the password has been successfully changed.
8. Minimize the Initial Configuration Tasks window.
9. After logging in, go to Start > All Programs > Administrative Tools > Computer
Management > Storage > Disk Management.
On Windows Server 2012, press Windows key + R to get the Run command window
and type diskmgmt.msc.
10. If you did not initialize the disk in step 6, do so now.
a. Right-click on the disk and choose Initialize Disk.
b. If given the choice, choose the MBR (Master Boot Record) partition style and
click OK.
11. On the Disk Management window, right-click CD-ROM 0.
Expected Result: Your DVD exists here.
12. Select Change Drive Letter and Paths..., and change the drive from D: to the
E: drive. Click OK.
Expected Result: You may get the following alert: Some programs that rely on drive
letters might not run correctly. Do you want to continue? This is OK. Click Yes.
13. Right-click in the box representing Disk 1 and select New Simple Volume.
Expected Result: The Create New Volume wizard opens.
14. Click Next, maintaining the default settings, until the Assign Drive Letter or Path
window displays. Select D: and click Next.
15. Click Next until the wizard completes and displays a summary of your choices.
Click Finish.
16. Maximize the Initial Configuration Tasks window. Click Enable Remote Desktop.

2103201-001 55
Chapter 4: Business Analytics Software Installation / Upgrade

17. On the Remote tab, select Allow connections from computers running any
version of Remote Desktop (less secure). Click OK for the firewall popup.
18. Click OK.
19. To turn off the firewall, go to Start > Administrative Tools > Server Manager >
Configuration > Windows Firewall with Advanced Security.
On Windows Server 2012, press Windows key + R to get the Run command window
and type ServerManager.
20. On the Windows Firewall with Advanced Security window, click Windows Firewall
Properties. On the Domain Profile, Private Profile, and Public Profile tabs, locate
Firewall State: and select Off. Click OK. and close Server Manager.
21. If you are required to change the server home:
a. Right-click Computer on the Desktop and select Properties from the context
menu.
b. Click the Computer Name tab.
c. Click Change.
d. Enter the new Computer name and click OK.
Expected Result:The server operating system is now installed.
Next: Install IIS Web Services (page 56)

4.3 Install IIS Web Services


Once the OS is installed you will need to install the web server.
1. Go to Start > Administrative Tools > Server Manager. Click Roles, then click
Add Roles.
On Windows Server 2012, press Windows key + R to get the Run command window
and type ServerManager.
2. On the Before You Begin window, click Next.
3. On the Select Server Roles window, select Web Server (IIS). Click Next.
4. On the Web Server (IIS) window, click Next.
5. On the Select Role Services window in section Select the role services to install
for Web Server (IIS):, keep the default selections and add all the Application
Development Roles. Click Next.
Note: If you are installing on Windows Server 2012, below features also have
to be selected:
Expand File and Storage Services and expand File and iSCSI Services and select
File Server.

2103201-001 56
Chapter 4: Business Analytics Software Installation / Upgrade

Figure 54 File Server in File and iSCSI Services

Expand .NET Framework 4.5 Features and expand WCF Services and select
HTTP Activation.
Figure 55 HTTP Activation

Click Next for the confirmation screen.

2103201-001 57
Chapter 4: Business Analytics Software Installation / Upgrade

Figure 56 Confirm Selection

6. On the Confirm Installation Selections window, click Install.


Expected Result: The installation begins and an Installation Progress message
displays.
7. When the Installation Succeeded message displays, close the window.
Expected Result:The web server is now installed.
Next: Make the Server IP Address Static (page 58)

4.4 Make the Server IP Address Static


The IP address of the Analytics server must be static.
To make the IP address static:
1. If you are not already logged in to the server as an administrator, log in.
2. Click the Network icon in the lower right corner of the Windows screen, then select
Open Network and Sharing Center from the resulting menu.

2103201-001 58
Chapter 4: Business Analytics Software Installation / Upgrade

Expected Result: The Network and Sharing Center window displays.


3. Click Local Area Connection.

Expected Result: The Local Area Connection Status dialog displays.


4. Click Properties.
Expected Result: The Local Area Connection Properties dialog opens.
5. Select Internet Protocol Version 4 (TCP/IPv4), then click Properties.

2103201-001 59
Chapter 4: Business Analytics Software Installation / Upgrade

Expected Result: The Internet Protocol Version 4 (TCP/IPv4) Properties dialog


displays.
6. Choose Use the following IP address, then enter the IP address, Subnet mask,
and Default gateway.
7. Enter the DNS server IP address. This should enable the DNS option.
8. Click OK, then click OK on the Local Area Connection Properties dialog, then click
Close on the Local Area Connection Status dialog.
Next: Add .NET Framework Features (page 60)

4.5 Add .NET Framework Features


1. Go to Start > Administrative Tools > Server Manager. Click Features and click
Add Features.
On Windows Server 2012, press Windows key + R to get the Run command window
and type ServerManager.
2. Select .Net framework 3.5 Features. On the Add Features Wizard window, click
Add Required Features. Click Next.
3. On the Confirm Installation Selections window, click Install.
Expected Result: Installation begins and an Installation Progress message displays.
4. When the Installation Succeeded message displays on the Installation Results
window, click Close.
Expected Result:.NET Framework Features are now installed.

2103201-001 60
Chapter 4: Business Analytics Software Installation / Upgrade

Next: Enable Static Content on the Web Server (page 61)

4.6 Enable Static Content on the Web Server


If static content is not enabled on the web server, do the following:
1. In Windows Server, go to Start > Administrative Tools > Server Manager > Roles >
Web Server (IIS).
On Windows Server 2012, press Windows key + R to get the Run command window
and type ServerManager.
2. On the Web Server (IIS) window, scroll down to Role Services.
3. Make sure the following features are shown as Installed in the Status column:
Common HTTP Features and StaticContent. If these features are not installed, click
Add Role Services on the right side of the Web Server (IIS) window and select the
Common HTTP Features and Static Content check boxes. Then, click Next.
Next: Configure Automatic Updating (page 61)

4.7 Configure Automatic Updating


1. Go to Start > Control Panel > System and Security.
On Windows Server 2012, press Windows key + R to get the Run command window
and type Control Panel. Go to System and Security.
2. Under Windows Update, click Change Settings link.
3. Under Important Updates, choose the option Never Check for Updates.
4. Click OK.
Next: Check to Make Sure the Software Installed at this Point Is Correct (page 61)

4.8 Check to Make Sure the Software


Installed at this Point Is Correct
1. Check to see if the web server is installed.
a. Select Start > Administrative Tools > Server Manager
On Windows Server 2012, press Windows key + R to get the Run command
window and type ServerManager.
b. Click Roles.
If Web Server (IIS) is listed under Roles Summary, then it is installed.
2. Select Control Panel from the Windows Start menu.
3. Under Programs, click Uninstall a program.
4. Check to see if SQL Server is installed.

2103201-001 61
Chapter 4: Business Analytics Software Installation / Upgrade

Note: Also set SQL Server and SQL Server agent services to run under
Local System account and restart services.
Press Windows key + R to get the Run command window and type
services.msc. Check SQL Server and SQL Server Agent services.
Figure 57 SQL Server and SQL Server Agent Services

To restart the particular service, right click the service and select Stop.
After it has been stopped, right-click again and select Properties. In
the Log On tab, select Local System Account. Click OK. Right-click the
service again and select Start.
Figure 58 Stop Service

2103201-001 62
Chapter 4: Business Analytics Software Installation / Upgrade

Figure 59 Service to run in Local System

Figure 60 Start Service

Next: Install Analytics (page 63).

4.9 Install Analytics


Prerequisite:
This procedure is for the initial installation of the Real-time Dashboard.
● Make sure the customer has purchased the Real-time Dashboard option.

1. Right-click <Analytics Media>\Setup.exe and select Run as Administrator from


the context menu.
2. Click Install.

2103201-001 63
Chapter 4: Business Analytics Software Installation / Upgrade

3. During installation, if the following window for installing Microsoft SQL Server 2008
R2 Native Client Setup is displayed, continue by clicking Next button. Else, go
to step 8
Figure 61 Microsoft SQL Server 2008 R2 Native Client Setup

4. Accept the terms and conditions by selecting the first item and Click Next.

2103201-001 64
Chapter 4: Business Analytics Software Installation / Upgrade

Figure 62 License Agreement

5. Enter the name and name of your organization as shown below and Click Next.
Figure 63 Registration Information

6. Select the feature SQL Server Native Client SDK and Click Next.

2103201-001 65
Chapter 4: Business Analytics Software Installation / Upgrade

Figure 64 Feature Selection

7. Click on Install
Figure 65 Ready To Install the Program

8. When the Centricity Imaging Analytics Setup Wizard window is displayed, click Next.
9. On the Custom Setup installer page, allow the default setup location and click Next.

2103201-001 66
Chapter 4: Business Analytics Software Installation / Upgrade

Note: The pre-selected location is C:\Program Files (x86)\GE


Healthcare\Centricity Analytics
10. On the Select SQL server instance installer page, choose a SQL server and specify
the User Name and Password, then click Next.
If you choose localhost, the installer will install the proper version of SQL Server on
the Analytics server. To use a pre-existing SQL Server, specify the IP address of that
server. Analytics requires Microsoft SQL Server 10.50.1600.1 2008 R2 or higher.
If you specify localhost, the default User Name should be sa. Provide a password
for the sa user.
Warning: You must change the GE-supplied default passwords before taking
the system live. Until you change the default passwords, you must
take measures to prevent unauthorized access to the server.
If you specify another server, specify the User Name and Password for a pre-existing
administrator account.
11. On the IIS Configuration page, choose the web site.
You should accept the default (Install under Default Web Site) by clicking Next.
If you need to create a new web site:
a. Choose Create a new Web Site.
b. Enter the appropriate Web Site Name and Web Site Port.
c. Click Next.
12. Click Install.
The next Wizard page displays the progress of the installation.
Note: A warning message will be displayed as shown below. Click Ignore to
continue with the installation

2103201-001 67
Chapter 4: Business Analytics Software Installation / Upgrade

13. On the Completed the Centricity Real-time Analytics Dashboard Setup Wizard page,
click Finish.
Expected Result: The Centricity Imaging Analytics Data Aggregation Engine is now
installed.
14. Do one of the following:
● If you chose not to install the Dashboard, then the installation is finished. Skip to
the next topic: Set the Maximum SQL Server Memory Usage (page 68).
Note: Check to see whether the site has purchased the Real-time
Dashboard option. This should be indicated with the GON (General
Order Number).
● If you opted to install the Dashboard, run DundasDashboard.exe from C:\Program
Files (x86)\GE Healthcare\Centricity Analytics\Dundas. Do not close this
window. (You can minimize or move it, just do not close it.) Then on the
Dashboard window, the installation progress displays. This should take about
5–10 minutes. After installation, close the command window.
Next: Set the Maximum SQL Server Memory Usage (page 68)

4.10 Set the Maximum SQL Server Memory


Usage
If 25% of the total memory on the server is greater than 2 GB (2048 MB), set the maximum
amount of memory that SQL Server uses to 75% of the total memory available. If 25% of
the total memory is less than 2048 MB, set the maximum memory to the total memory
minus 2048 MB.
1. From an administrator account on the computer hosting SQL Sever, open SQL Server
Management Studio and log into the server as sa. The server should be local, the
server type should be Database Engine, and the authentication should be SQL
server authentication.
To open Management Studio, select Start > All Programs > Microsoft SQL Server
2008 R2 > SQL Server Management Studio from the Windows toolbar.
On Windows Server 2012, press Windows key + R to get the Run command window
and type ssms . Click OK.
2. Right-click on the server in the Object Explorer (the server is the top item).
3. Select Properties from the context menu.
4. Select the Memory page in the Server Properties dialog.
5. Calculate the maximum memory to specify in MB (either 75% of the total or the total
memory minus 2 GB) and specify that amount under Maximum server memory.

2103201-001 68
Chapter 4: Business Analytics Software Installation / Upgrade

6. Click OK and exit the SQL Server Management Studio.

4.11 Change/Verify the Default Passwords


GE provides default passwords to install and upgrade the Centricity Imaging Analytics
Real-time Dashboard. You can change the default passwords before installing CCG. (The
CCG installation process asks you for the user name and password for the ccg account.
Specify the new password you set in the SQL Server database.)
Note Password management is the responsibility of the customer.
Below are the three default password you must change.
User Name Default Description
Password*
sa <sa_password> SQL Server system administrator.
analyst <analyst_pass- Account that Analytics and Dundas use to
word> connect to the database.
ccg <ccg_pass- Account that CCG uses to connect to the
word> Analytics database.

1. Change the passwords on SQL Server.


a. From the machine hosting SQL Server, log in to the Analytics database as sa.
b. Right-click on localhost > Security > Logins > sa.
c. From the context menu, select Properties.
d. Change the password on the resulting Properties dialog.
e. Repeat steps b through d for the analyst and ccg users.
2. Change the analyst password in Web.config.
a. Open Web.config with a text editor on the Analytics server.
The path should be:

2103201-001 69
Chapter 4: Business Analytics Software Installation / Upgrade

C:\Program Files (x86)\GE Healthcare\Centricity Analytics\Centricity Realtime


Dashboard Web Application\Web.config
b. Search for analyst.
The user ID should be in the phrase: User ID=analyst; followed by the phrase:
Password=<analyst_password>;
c. Change the password, then search for analyst again.
d. Change the password for that second instance of analyst.
e. Search for analyst again.
Expected Result: You should not find any more instances. If you do, change the
password for that instance and continue searching.
f. Once you have changed the password for all instances of analyst, save your
changes and close the file.
Example:
Web.config
<connectionStrings>
<!-- WIN-TC9GLUG7P8D.clients.am.health.ge.com -->
<!-- ILOUSE903K15L.clients.am.health.ge.com -->
<add name="dashboardURI" connectionString=
"http://3.28.73.65:85/DundasDashboardv5.0/" />
<add name="voyager" connectionString=
"Initial Catalog=voyager;Data Source=localhost;
User ID=analyst;Password=<analyst_password>;Persist Security Info=True;"
providerName="System.Data.SqlClient" />
<add name="VoyagerEntities" connectionString=
"metadata=res://*/Data.VoyagerEntityDataModel.csdl|
res://*/Data.VoyagerEntityDataModel.ssdl|
res://*/Data.VoyagerEntityDataModel.msl;
provider=System.Data.SqlClient;provider connection string=
&quot;Data Source=localhost;Initial Catalog=voyager;
User ID=analyst;Password=<analyst_password>;MultipleActiveResultSets=True&qu
providerName="System.Data.EntityClient" />
</connectionStrings>
3. Change the analyst password in Dundas.Dashboard.config.
a. Open Dundas.Dashboard.config.
The path should be:
C:\Program Files\Dundas Data Visualization Inc\Dundas Dashboard\5.0\www\
Dundas.Dashboard.config
b. Repeat steps 2 b through 2 f to change the password for analyst in the Dundas
configuration file.
c. Search for DundasDashboardUrl in Dundas.Dashboard.config and ensure it is
http://localhost:85/
Example:
Dundas.Dashboard.config
<!-- ==== DundasDashboardUrl ====
The URL of the Dundas Dashboard application. -->
<key name="DundasDashboardUrl" value="http://localhost:85/" />

4. Log in to Dundas as admin and change the analyst password in the Dundas interface.
Dundas should be located at:

2103201-001 70
Chapter 4: Business Analytics Software Installation / Upgrade

http://localhost:85/.
a. Log in as admin.
b. In the Design Explorer column, navigate to Data Connectors > CIA.
c. Right-click on CIA and select Edit from the context menu.
Expected Result: This opens the Editing Data Connector screen.
d. Under Use SQL Server security enter the User name (analyst) and Password.
The password for user analyst will be the same as given in Web.config file.

e. Click Test Connection.


f. If the test works, click Save. A dialog will be displayed, click Yes.

Next: Go through the Post-Installation Verification Checklist (page 79) to make


sure everything was correctly installed.

4.12 Upgrade Analytics


Prerequisites:
● Notify the ROC and HL7 integrator that you are about to upgrade Analytics.
● Before the upgrade, disconnect CCG and the Real-time Dashboard interface.
Messages will queue on the CCG side and will be processed when the Real-time
Dashboard interface is reconnected.
Upgrading from 1.2 to 1.4 requires both the Centricity Analytics v1.4 SP1 media and
the Centricity Analytics v1.4 SP2 patch on electronic media.
2103201-001 71
Chapter 4: Business Analytics Software Installation / Upgrade

● If the upgrade is done from 1.2 to a higher version, follow the below steps.
Go to Control Panel - Uninstall Program - Add and Remove -Centricity Analytics
In Control Panel , Choose Uninstall a program.
Figure 66 Uninstall Program

Select Centricity Analytics and click Uninstall.


Figure 67 Uninstall Centricity Analytics

On the confirmation dialog, click Yes.

2103201-001 72
Chapter 4: Business Analytics Software Installation / Upgrade

Figure 68 Uninstall Centricity Analytics Confirmation

Wait for the uninstallation to get complete.


● Follow this procedure only if version 1.2 is already installed. To verify, go to the
Real-time Dashboard About dialog box.
Verify whether or not the customer has purchased the Real-time Dashboard option. If
they have purchased Real time Dashboard,
Go to Control Panel - Uninstall Program - Add and Remove - Uninstall Dundas
Dashboard 2.5.5
In Control Panel , Choose Uninstall a program.
Figure 69 Uninstall Program

Select Dundas Dashboard 2.5.5 and click Uninstall .

2103201-001 73
Chapter 4: Business Analytics Software Installation / Upgrade

Figure 70 Uninstall Dundas Dashboard 2.5.5

On the confirmation dialog, click Yes.


Figure 71 Uninstall Dundas Dashboard 2.5.5 Confirmation

Wait for the uninstall to complete.

2103201-001 74
Chapter 4: Business Analytics Software Installation / Upgrade

Figure 72 Uninstall Dundas Dashboard 2.5.5 in Progress

● Set SQL Server and SQL Server agent services to run under Local System account
and restart services.

1. Right-click <Analytics Media>\Setup.exe and select Run as Administrator from


the context menu.
2. While upgrading from versions higher than 1.2, a pop up will get displayed with the
message, “The previous version of Centricity Analytics is already installed. Click OK
to Upgrade!”. Click OK, then click Install.
3. When the Centricity Imaging Analytics Setup Wizard window opens, click Next.
4. On the Custom Setup installer page, allow the default setup location and click Next.
5. On the Select SQL server instance installer page, choose a SQL server and specify
the User Name and Password, then click Next.
If you choose localhost, the installer will install the proper version of SQL Server on
the Analytics server. If you want to use a pre-existing SQL Server, specify the IP
address of that server. Analytics requires Microsoft SQL Server 10.50.1600.1 2008
R2 or higher.
If you specify localhost, enter the default User Name (sa) and your Password for sa.
If you specify another server, specify the User Name and Password for a pre-existing
administrator account.
6. On the IIS Configuration page, choose the web site.
Typically you should accept the default (Install under Default Web Site) by clicking
Next.
7. Click Install.
Expected Result: The next Wizard page displays the progress of the installation.
8. On the Completed the Centricity Real-time Analytics Dashboard Setup Wizard page,
click Finish.
Expected Result: The Centricity Imaging Analytics Data Aggregation Engine is now
installed. If you chose not to install the Dashboard, the installation is finished.
Note: Check to see whether the site has purchased the Real-time Dashboard
option. This should be indicated with the GON (General Order Number).

2103201-001 75
Chapter 4: Business Analytics Software Installation / Upgrade

If you opted to install the Dashboard, run DundasDashboard.exe available at


C:\Program Files (x86)\GE Healthcare\Centricity Analytics\Dundas , a new command
window opens. Do not close this window. (You may minimize or move it, just do
not close it.) The On the Dashboard window, the installation progress displays. This
should take about 5–10 minutes. After installation, close the command window.
The upgrade is complete. To verify functionality, refer to Post-Installation Verification
Checklist (page 79)
9. Verify the passwords.
When upgrading from Analytics 1.2 to 1.3, in Web.config (C:\Program Files
(x86)\GE Healthcare\Centricity Analytics\Centricity Realtime Dashboard Web
Application\Web.config) and Dundas.Dashboard.config (C:\Program Files\Dundas
Data Visualization Inc\Dundas Dashboard\5.0\www\Dundas.Dashboard.config), the
passwords will be updated to 8 characters by appending # to the existing passwords
for analyst. If the customer has already changed the password for analyst, update the
current analyst password in the below sections.
Web.config
<connectionStrings>
<!-- WIN-TC9GLUG7P8D.clients.am.health.ge.com -->
<!-- ILOUSE903K15L.clients.am.health.ge.com -->
<add name="dashboardURI" connectionString=
"http://localhost/DundasDashboardv2.0.0/" />
<add name="voyager" connectionString=
"Initial Catalog=voyager;Data Source=localhost; User ID=analyst;Password=<analys
providerName="System.Data.SqlClient" />
<add name="VoyagerEntities" connectionString=
"metadata=res://*/Data.VoyagerEntityDataModel.csdl|
res://*/Data.VoyagerEntityDataModel.ssdl|
res://*/Data.VoyagerEntityDataModel.msl;
provider=System.Data.SqlClient;provider connection string=
&quot;Data Source=localhost;Initial Catalog=voyager;
User ID=analyst;Password=<analyst_password>;MultipleActiveResultSets=True&quot;
providerName="System.Data.EntityClient" />
</connectionStrings>
Dundas.Dashboard.config
<!-- ==== AppDatabaseConnectionString ====
The connection string to the application database. -->
<key name="AppDatabaseConnectionString" value="Data Source=D0251-
W2008; Initial Catalog=Dundas_Dashboard_DataStore; User Id=sa;
Password=<sa_password>;" />
<!-- ==== SyncDatabaseConnectionString ====
The connection string to the synchronization database. -->
<key name="SyncDatabaseConnectionString" value="Data Source=
D0251-W2008; Initial Catalog=Dundas_Dashboard_Sync; User Id=sa;
Password=<sa_password>;" />

10. Change the analyst password in Web.config.


a. Open Web.config with a text editor on the Analytics server.
The path should be:
C:\Program Files (x86)\GE Healthcare\Centricity Analytics\Centricity Realtime
Dashboard Web Application\Web.config
b. Search for analyst.
The user id should be in the phrase: User ID=analyst; followed by the phrase:
Password=<analyst_password>;

2103201-001 76
Chapter 4: Business Analytics Software Installation / Upgrade

c. Change the password, then search for analyst again.


d. Change the password for that second instance of analyst.
e. Search for analyst again.
Expected Result: You should not find any more instances. If you do, change the
password for that instance and continue searching.
f. Once you have changed the password for all instances of analyst, save your
changes and close the file.
Example:
Web.config
<connectionStrings>
<!-- WIN-TC9GLUG7P8D.clients.am.health.ge.com -->
<!-- ILOUSE903K15L.clients.am.health.ge.com -->
<add name="dashboardURI" connectionString=
"http://3.28.73.65:85/DundasDashboardv5.0/" />
<add name="voyager" connectionString=
"Initial Catalog=voyager;Data Source=localhost;
User ID=analyst;Password=<analyst_password>;Persist Security Info=True;"
providerName="System.Data.SqlClient" />
<add name="VoyagerEntities" connectionString=
"metadata=res://*/Data.VoyagerEntityDataModel.csdl|
res://*/Data.VoyagerEntityDataModel.ssdl|
res://*/Data.VoyagerEntityDataModel.msl;
provider=System.Data.SqlClient;provider connection string=
&quot;Data Source=localhost;Initial Catalog=voyager;
User ID=analyst;Password=<analyst_password>;MultipleActiveResultSets=True&qu
providerName="System.Data.EntityClient" />
</connectionStrings>
11. Change the analyst password in Dundas.Dashboard.config.
a. Open Dundas.Dashboard.config.
The path should be:
C:\Program Files\Dundas Data Visualization Inc\Dundas Dashboard\5.0\www\
Dundas.Dashboard.config
b. Repeat steps 2 b through 2 f to change the password for analyst in the Dundas
configuration file.
c. Search for DundasDashboardUrl in Dundas.Dashboard.config and ensure it is
http://localhost:85/
Example:
Dundas.Dashboard.config
<!-- ==== DundasDashboardUrl ====
The URL of the Dundas Dashboard application. -->
<key name="DundasDashboardUrl" value="http://localhost:85/" />

12. Log in to Dundas as admin and change the analyst password in the Dundas interface.
Dundas should be located at:
http://localhost:85/.
a. In the Design Explorer column, navigate to Data Connectors > CIA.
b. Right-click on CIA and select Edit from the context menu.
Expected Result: This opens the Editing Data Connector screen.

2103201-001 77
Chapter 4: Business Analytics Software Installation / Upgrade

c. Under Use SQL Server security enter the User name (analyst) and the new
Password.

d. Click Test Connection.


e. If the test works, click Save. A dialog will be displayed, click Yes.

13. Assign analyst user with sysadmin server role.


a. Launch SQL Server Management Studio (Start > All Programs > Microsoft SQL
Server > SQL Server Management Studio) and log in to the Analytics database.
On Windows Server 2012, press Windows key + R to get the Run command
window and type ssms.
b. Expand Security folder and expand Logins.
c. Select the user analyst. Right-click and launch Properties.
d. On the properties window, click on Server Roles under Select a page.
e. Select the role sysadmin and click OK.

2103201-001 78
Chapter 4: Business Analytics Software Installation / Upgrade

Next: Set the Maximum SQL Server Memory Usage (page 68)

4.13 Configure SSL with Analytics (Optional)


1. Import certificate in IIS.
2. Enable SSL bindings on Analytics website with port 443.
3. Navigate to C:\Program Files (x86)\GE Healthcare\Centricity Analytics\Centricity
Realtime Dashboard Web Application\. Rename the web.config file to
web.config.nonssl and rename the web_SSL.config file to web.config.
4. Open the Dundas.Dashboard.config file (C:\Program Files\Dundas Data
Visualization Inc\Dundas Dashboard\5.0\www\Dundas.Dashboard.config). Search
the Dundas.Dashboard.config file for DundasDashboardUrl and ensure it is
https://localhost:85/.

4.14 Post-Installation Verification Checklist


Warning: You must change the GE-supplied default passwords before taking the
system live. Until you change the default passwords, you must take
measures to prevent unauthorized access to the server.

2103201-001 79
Chapter 4: Business Analytics Software Installation / Upgrade

Note User account management is the customer’s responsibility. See


Authentication (page 19)
● Make sure you have Set the Maximum SQL Server Memory Usage (page 68).
● Before configuring the system, make sure the IIS web server is running.
1. Select Start > Administrative Tools > Internet Information Services (IIS)
Manager
On Windows Server 2012, press Windows key + R to get the Run command
window and type inetmgr and Click OK.
2. Select the server which was created in the Analytics installation process.

3. In the Actions column on the right, make sure Start is greyed out and that Stop
is not.
● Make sure SQL Server Services are running (Started).
1. Select Start > Administrative Tools > Services.
On Windows Server 2012, press Windows key + R to get the Run command
window and type services.msc. Click OK .
2. Make sure SQL services are started.

● In a web browser, make sure you are able to log in to Analytics, located at:
http://localhost/Analytics
User name: viewer.
Default password for new install: <install_password>
Default password for upgrade: <upgrade_password>
Important You must change the GE-provided default passwords before taking
the system live.

2103201-001 80
Chapter 4: Business Analytics Software Installation / Upgrade

Note: If the browser does not have Microsoft Silverlight plug-in installed, a
message will be displayed to install Silverlight plug-in. Click on the
Silverlight Plugin link to install.
● While logging on to Analytics for the first time , a dialog will be displayed asking you to
enable additional storage. Click OK. Click Yes in the next dialog.

● For upgrade scenario, if live feeds are available, we can check dashboard and confirm
that the data is being displayed. In Scorecard and Report, there wont be any data
available as summary table jobs are not run. Jobs are scheduled to run at 12.00 am,
by default. To manually run these jobs, follow the below steps:
1. Select and Open a Scorecard or Report
2. Click on Filter button on the right side of the opened Scorecard or Report.
Figure 73 Selecting the filter

3. Move the mouse to ‘X’ on the opened filter window and Click Ctrl key followed
by a left mouse button click.
4. Check for kpi_id parameter name and note it down.

2103201-001 81
Chapter 4: Business Analytics Software Installation / Upgrade

Figure 74 Find the kpi_id

5. The summary table job for the kpi_id will be named as Synchro-
nize_kpi_<kpi_id>_summary. (eg. Synchronize_kpi_40_summary for KPI
ID = 40).
6. Launch SQL Server Management Studio (Start > All Programs > Microsoft SQL
Server > SQL Server Management Studio) and log in to the Analytics database.
On Windows Server 2012, press Windows key + R to get the Run command
window and type ssms . Click OK and log in to the Analytics database.
7. Check for SQL Server Agent on the left panel . Identify the corresponding job for
particular kpi_id under SQL Server Agent > Jobs

2103201-001 82
Chapter 4: Business Analytics Software Installation / Upgrade

Figure 75 Job corresponding to the kpi_id

8. Run the corresponding job to populate summary table. Right click the job and
Start Job at Step.
Figure 76 Run job to populate Summary table

● If you installed the Real-time Dashboard, make sure you are able to log in to it. Use a
web browser to go to: http://localhost:85/

2103201-001 83
Chapter 4: Business Analytics Software Installation / Upgrade

User name: admin.


Default password: <admin_password>
Next: CCG Baseline Installation (page 85)

4.15 Location of Analytics_Prod


The analytics_prod.zip file and the conf folder are located at: <AnalyticsMedia>\CCG.

4.16 Install on VMware


If installing Analytics on VMware, the customer is responsible for:
● Having an operating system on a virtual environment that meets or exceeds the
hardware specification.
● Providing remote access from this virtual environment via RDP.
● Being able to access the media from the OS virtual machine to setup by customer.
● Setting up VM farm and ensuring they provide a production VMware ESXi with
Windows 2008 OS installed.

2103201-001 84
5
CCG Baseline Installation
CCG 8.0.2
CCG 9.3.2

5.1 CCG 8.0.2


Note If CCG is already installed at your site, refer to the Upgrading CCG chapter of
the Centricity Clinical Gateway for PACS Integration Installation and Upgrade
Manual.

5.1.1 Running the CCG 8.0 Installer Wizard


Prerequisite: Close all applications and disable any antivirus programs before beginning
the installation procedure. Be sure to re-enable your antivirus programs after you
complete the install.

Warning: To prevent malicious corruption or transmission of sensitive medical data, you


must install and start a virus scanner that runs in real time.
1. Insert CCG media into the drive.
2. Copy the installation zip file to the Analytics server.
3. Extract the installation files from the zip file on the server to a folder on the desktop.
4. Open the extracted installation folder.
5. Right-click the Install CCG.bat file and select Run as Administrator.
Expected Result: Several command windows open, then close. The InstallAnywhere
dialog then shows a progress bar as the program prepares the installation. This
may take a few minutes.
When this finishes, the Centricity Clinical Gateway 8.0 Installer wizard Introduction
screen opens.
6. Click Next.
7. In the Choose Product Features window, select the options:
● CCG Core Components
● DMWL
● DMWL MPPS Service

2103201-001 85
Chapter 5: CCG Baseline Installation

8. Click Next.
This opens the Databse Local/Remote screen.
9. For an Analytics installation, there is typically no DMWL database. Choose Remote to
tell the installer that there is no local database.

10. The Remote DataBase Type screen displays . Select SQL Server, Select the type of
database you are using for DMWL at the site, then click Next.
Note: A CCG for Analytics installation may skip this screen.
11. In the Choose Install Folder window, specify the location in C:\ for Centricity Clinical
Gateway software installation.
Default: c:\gehc-it.

12. Click Next.

2103201-001 86
Chapter 5: CCG Baseline Installation

13. In the Pre-Installation Summary window, verify the summary information, and then
click Install. You can click Previous to change the selected install options.
Note: The feature list and total size of the installation may differ from the
illustration based on the components selected for installation.

14. Monitor the progress of the installation on the Installing Centricity Clinical Gateway
8.0 page.

15. On the Install Complete page, make sure the installation succeeded, then click Done.
Expected Result: The system reboots.
16. Log on as administrator once your system reboots.

5.1.2 Verify the Installation


5.1.2.1 Verify Programs are Installed
1. In the Windows Control Panel, open Programs > Uninstall a program
2. Confirm that the following items are installed:
● Centricity Clinical Gateway 8.0

2103201-001 87
Chapter 5: CCG Baseline Installation

● CLOVERLEAF(R) Integration Services 57MB


● CCG Cloverleaf Package
If any of these items are missing, the install failed. Contact the ROC.
3. Close all open windows.

5.1.2.2 Verify Services are Available


1. On the Windows Start menu, select Administrative Tools > Services.
2. In the Services window, confirm that the following services are available:
● Centricity Clinical Gateway Cache (if cache is installed)
● Centricity Clinical Gateway Service Tools
● Centricity Clinical Gateway Webmin Service
● CLOVERLEAF(R) Integration Services 5.7MB
● DMWL Prod Server
If any of these services are missing, the install failed. Contact the ROC.
3. Close all open windows.

5.1.2.3 Confirm Web Login Page


1. On the Windows Desktop, double click CCG Service Tools
2. Verify that the CCG service tools login page appears.
Note: If the login pages does not display, contact the ROC.
3. Close the login page.

5.1.3 Configure the Backup


For information about configuring backups for CCG, see the Upgrading CCG chapter in
the Centricity Clinical Gateway for PACS Configuration and Integration Manual.

5.1.4 Post Installation Procedures


5.1.4.1 Monitoring the Health of CCG

Note Monitoring is accomplished through SiteScope software. The site must have
this software and a SiteScope server installed. If they do not, contact the Call
Center for additional information. (See Contacting GE Support (page 4)
When the VPN was established to this site, SPS monitoring was also established. When
the system is in ‘Go Live’ state, the SPS monitoring is initiated. There are no further
requirements for monitoring the CCG.
Note Remote monitoring is unavailable if the site does not have an SPS server.

2103201-001 88
Chapter 5: CCG Baseline Installation

5.1.4.2 Log in to Webmin


To begin using the Webmin interface to access the service tools, open the Internet
browser on the server that is running or double-click the CCG Service Tools icon on the
desktop and go to step 3.
1. Start Internet Explorer or double click the CCG Service Tools icon and go to 3.
2. In the Address bar, if you are working on the server where CCG is installed, type:
http://localhost:10000
If you are working remotely, type:
http://<ipaddress>:10000/
where <ipaddress> is the IP address of the CCG server.
The port number (10000) on which Webmin is running is configurable as shown in
the CCG instruction manuals.
3. When the Login to Webmin dialog opens in the browser:
a. Enter geservice as the username.
b. Enter the <webmin_password>.
c. Click Login.

4. The Service Tools window opens to the Service tab.


Next: Items for each of the Centricity Clinical Gateway service tool modules display
in the menu list on the left.

5.1.4.3 Create a Local Sysadmin Account (Optional)


If you have a local sysadmin who is able to monitor the status of the system, you can create
a limited-privileges account for the user. The following procedure creates a local sysadmin
account with privileges to view the database and check the Cloverleaf thread status.
Note PACS Webmin comes pre-loaded with a geservice accounts. The default
installation login for geservice is: geservice/<webmin_password>.
All other privileges are reserved for GE personnel only, as untrained use of the other
Webmin tools could compromise the customer system and result in system downtime.
1. If you are not logged into Webmin, log in. See Log in to Webmin (page 89).
2. Click the Webmin tab to switch to the Webmin index page.

2103201-001 89
Chapter 5: CCG Baseline Installation

3. Click the Webmin Users menu item to open the page with the Webmin Users and
Webmin Groups controls.

4. Click the Create a new Webmin User link.


Expected Result: The Webmin user access rights dialog opens.

5. Enter the data in Table 6 to configure a standard customer site administrator account.
Note: Click the option titles to expand the list as in the Available Webmin
modules above.

Table 6 User Access Rights

Field Value Comments


Username localsa Suggested username for local sysadmin.

Password <localsa_password>

SSL certificate name None N/A


Language Default N/A
Categories modules Default N/A

2103201-001 90
Chapter 5: CCG Baseline Installation

Field Value Comments


Personal theme From Webmin Configuration N/A
IP access control Allow from all addresses Check with the local sysadmin to see if
stricter IP access controls are required.
Modules Check ONLY the following: Enabling any additional modules leaves the
Database Viewer Interface Monitor system open to accidental corruption.

Note: You may also want to create a Windows account for the local system
administrator.

5.1.4.4 Hand Off to ITPS for Integration


Inform your Project Manager that the CCG is successfully installed and it is ready to
be configured.
The ITPS Integration team handles the Cloverleaf (Quovadx) license key.

5.1.4.5 Install and License Cloverleaf


For installation instructions, refer to the Cloverleaf manual. The ITPS Integration team
handles the Cloverleaf licensing (see Cloverleaf License Request Process for details).

5.1.4.6 Engage the HL7 Integration Team


For implementation please contact the GE Project Manager so they can engage the HL7
Integration Team. For a reload of the CCG application, please contact the ROC.
How to Connect Analytics to CCG Using Tcl ODBC

5.2 CCG 9.3.2


Installation of the CCG Software has been broken down into three separate components
for this release. They must be installed in the following order:
1) CCG Interface Engine (Cloverleaf Integration Services/Cloverleaf-6.1-Windows) (See
Centricity Clinical Gateway Interface Engine Installation)
2) ActivePerl (See ActivePerl Installation)
3) CCG Components (See Centricity Clinical Gateway Components Installation)

5.2.1 Centricity Clinical Gateway Interface Engine Installation


1. Close all applications before beginning the installation procedure.
2. The Cloverleaf installation files are distributed either as a downloaded zip archive
or on removable media such as a DVD.
● If you received a zip file (Cloverleaf-6.1-Windows.zip), unzip the file before
proceeding. The folder extracted from the zip archive will contain the same
installation files and directory structure as you would have if you received the files
on a removable disk. Navigate to the folder where you extracted the files

2103201-001 91
Chapter 5: CCG Baseline Installation

● If you received the installation files on a removable disk, insert the disk and
navigate to the top level folder on the disk.
3. Right-click the Install.bat file and select Run as Administrator.
InstallAnywhere prepares the install wizard, which will guide you through the install
process. This may take up to several minutes.
4. When the install wizard has finished loading, the Introduction page of the wizard
appears. Click Next.

5. The Choose Features page appears. Click Next

2103201-001 92
Chapter 5: CCG Baseline Installation

6. The Choose Install Folder page appears.


● If you want an install folder other than the default folder, click Choose and
select the desired installation folder, or type the folder structure in the text box.
● Then click Next.

2103201-001 93
Chapter 5: CCG Baseline Installation

7. The Pre-Installation Summary page appears. Click Install.

8. The wizard beings installing the Cloverleaf interface engine. A progress bar appears
at the bottom.

9. When the installation is finished, the Install Complete page appears

2103201-001 94
Chapter 5: CCG Baseline Installation

● If you want to restart the system before installing additional CCG software
components, select Yes, restart my system.
● Click Done to exit the wizard

5.2.2 Active Perl Installation


1. Obtain the Active Perl installer.
2. If the system is used for development or testing, GE personnel can obtain
the Active Perl installer from the GE libraries: http://libraries.ge.com
/foldersIndex.do?entity_id=36913140101=1&sid=101&SF=1
Note: If you do not have access to libraries location, you can request access
by contacting the CCG team. If it is for a customer site, contact the CCG
team to obtain the login credentials for the business edition of the Active
Perl installer.
3. In Windows Explorer, navigate to the folder in which the ActivePerl installer is located.
Double-click the ActivePerl installer icon.

2103201-001 95
Chapter 5: CCG Baseline Installation

4. The ActivePerl Installation wizard starts. Click Next.

5. The wizard displays a license agreement.


● Select I accept the terms of the License Agreement.
● Click Next.

2103201-001 96
Chapter 5: CCG Baseline Installation

6. A component selection page appears.


● Deselect the Example group.
● If you want to save space, you can also deselect the Documentation group.
Note: The Perl and PPM groups are required for CCG operation.
● Click Next.

7. A page with additional installation options appears. Click Next to accept the defaults.

2103201-001 97
Chapter 5: CCG Baseline Installation

8. Click on the Next button.

9. Click Install again to start the installation.

2103201-001 98
Chapter 5: CCG Baseline Installation

10. When the installation dialog indicates that installation is complete, click Finish to exit.

5.2.3 CCG Components Installation


The following instructions describe how to install the Centricity Clinical Gateway
Components (CCG-9.3.2-Windows) software on Microsoft Windows 2008 Server and
Windows 2012 Server.
Note CCG Interface Engine (Cloverleaf Integration Services) and ActivePerl 5.8.9
must be installed prior to running the CCG Components installer.
1. Close all applications before beginning the installation procedure.
2. The CCG installation files are distributed either as a downloaded zip archive or on
removable media such as a DVD.
● If you received a zip file (CCG-9.3.2-Windows.zip), unzip the file before
proceeding. The folder extracted from the zip archive contains the same
installation files and directory structure as you would have if you received the files
on a removable disk. Navigate to the folder where you extracted the files.
● If you received the installation files on a removable disk, insert the disk and
navigate to the top level folder on the disk.
Note: The remainder of this procedure describes how to run the installation
wizard. If you want to install silently, proceed to “Silent Mode
Installation”.
3. Right-click the Install.bat file and select Run as Administrator. InstallAnywhere
prepares the install wizard, which will guide you through the install process. This
may take several minutes.

2103201-001 99
Chapter 5: CCG Baseline Installation

4. If Active Perl is not installed on the target system, the installer displays a Missing
Dependency (Active Perl) pop up window and exits.

5. When the installation wizard has finished initializing, the Introduction page appears.
Click Next to continue.

2103201-001 100
Chapter 5: CCG Baseline Installation

6. The Choose Product Features window appears.

7. Click Next to continue.


8. If you select features that require database support, the Choose Database window
appears.

2103201-001 101
Chapter 5: CCG Baseline Installation

9. If this page appears:


a. Specify the database to be used by filling out the following fields:
● DB IP Address: IP address of the system on which the selected database is
to be stored. If the database is to be stored on the local host (the same system
on which CCG is installed), you can enter either localhost or 127.0.0.1.
● Port Number:TCP port number on which the database service is listening.
Note: The default for MS SQL Server is 1433. However, it is possible to
reassign the port number for most applications. Check with the
database administrator to be sure
● Admin User:Username of the database administrator.
● Admin : of the database administrator.
b. Click Next.
10. The Choose Install Folder page appears.
● Specify the location for CCG 9.3.2 software installation.
Note: Click Choose to change folder and select your desired installation
folder, or type the folder structure in the text box.
● Click Next to continue.

2103201-001 102
Chapter 5: CCG Baseline Installation

11. The Pre-Installation Summary page appears.


a. Verify that the summary information displayed accurately reflects the type of
installation you want. If you want to make changes, click Previous to change the
selected install options.
Note: The screen capture above is for illustration purpose only. The feature
list and total size of the installation will vary based on the components
selected for installation.
b. Once review the installation options displayed in the summary, click Install.

2103201-001 103
Chapter 5: CCG Baseline Installation

The wizard will display a progress bar so that you can monitor the progress of
the installation.

12. When the Install Complete page appears.


a. Verify that the message displayed indicates that installation was successful.

2103201-001 104
Chapter 5: CCG Baseline Installation

b. Click Done to continue. The system will reboot.

13. Log on as Administrator once the system has finished rebooting.

5.2.4 Set User and for Scheduled Tasks

5.2.4.1 Windows 2008 and 2012 Specific Steps


To configure s for automatic tasks:
1. In the Windows Control Panel, open Administrative Tools > Task Scheduler.
2. The Task Scheduler window appears. In the left column, select Task Scheduler
Library.

2103201-001 105
Chapter 5: CCG Baseline Installation

3. Right-click the autostart entry, then select Properties from the menu that appears.
4. In the General tab, click the Change User or Group button.

5. The Select User or Group window appears.

2103201-001 106
Chapter 5: CCG Baseline Installation

6. Specify the name of a user who has Administrator privileges. There are two ways
to do this:
● Type the name of an appropriate user in the Enter the object name to select
box. Then, click the Check Names button. If the name you entered has been
defined on this system, the full user name should now appear in the box. OR
● Click the Advanced button and then click Find Now. A list of users defined on
the system should now appear. Select the desired user and click OK. The full
user name of the selected user should now appear in the Enter the object name
to select box.
7. Click OK to close the Select User or Group window.
8. Click OK to close the autostart Properties window.
9. Repeat the above procedure for the Smatcycle, Purge, System_State_Recur-
ring_Backup and CloverleafCleanup tasks.

5.2.5 Post Installation Checks


To check whether the CCG v9.3.2 installation is complete, follow these subsections.

5.2.5.1 Verify installation via Programs and Features


1. In the Control Panel, double-click Programs and Features, or click on Uninstall a
Program.
2. Confirm that the following items are installed:
● Centricity Clinical Gateway (CCG) Components
● Centricity Clinical Gateway (CCG) Interface Engine
3. Close all open windows.

2103201-001 107
Chapter 5: CCG Baseline Installation

5.2.5.2 Verify Services are Available and Started/Running


1. On the Windows Start menu, select Control Panel, then Administrative Tools >
Services.
2. In the Services window, confirm that the following services are available.
● Centricity Clinical Gateway (CCG) Webmin
● Infor CLOVERLEAF(R) Integration Services 61
● Centricity Clinical Gateway (CCG) Components
● Centricity Clinical Gateway (CCG) Service Tools
3. Close all open windows.

5.2.5.3 Confirm Web Login Page


1. On the Windows Desktop, double clickCCG Service Tools .
2. Verify that the CCG service tools login page appears.
3. Enter the following credentials:
● Username: geservice
● : <webmin_>
4. Click OK.
5. Verify that login is successful.
6. Close the page.
Next: How to Connect Analytics to CCG Using Tcl ODBC

5.3 CCG v9.3.7


For information about installing CCG v9.3.7, see the Centricity Clinical Gateway 9.3.7 for
PACS Installation and Upgrade Manual (DOC1976159).

2103201-001 108
6
CCG Upgrade
CCG 8.0.2
CCG 9.3.2
CCG v9.3.7

6.1 CCG 8.0.2


CCG (Centricity Clinical Gateway) v8.0.2.1 supports an automated upgrade from CCG
v5.1, v6.1, v6.2, and v8.0.1. (There should not be any CCG v7.x installations for PACS.
The standalone CCG upgrade from 7.x is supported, however, the PACS-specific upgrade
path has not been thoroughly tested.)
Important You must notify Integration Services at least one month in advance of
an upgrade so ITPS can schedule time to prepare for the upgrade.
You must engage an integrator prior to an upgrade. The upgrade
overwrites some data that the system must retain. The integrator must
save this data before the upgrade, then restore it after the upgrade.

6.1.1 Prepare the Upgrade for CCG


Pre upgrade Checklist:
1. Record the backup location and schedule for use later in the upgrade.
1) Login into CCG Webmin Service Tools. Backup location
The login is located at http:\\localhost:10000.
User: geservice
Password: <webmin_password>
Backup schedule
2) Click on the Service tab.
3) Click on System State.
4) Click on Configuration.
5) Record the indicated backup storage location.
6) Click on Backup.
7) Record the backup schedule.

2103201-001 109
Chapter 6: CCG Upgrade

Once you finish the upgrade, you manually restore these


settings.

2. Schedule a one time backup to start while you are preparing for the upgrade.
Note: Since the database is not dropped, there will be no data loss during the
upgrade process. However, we recommend doing a database backup
before the upgrade begins. Later, when the upgrade dialogs ask whether
you want to do a backup, answer No. If you let the upgrade process do
the backup, it significantly increase the downtime.
This backs up the database and other CCG system state information. The CCG
database stores transaction data from the last 30 days. For information on restoring a
backup, see the Scheduling and Restoring Backup chapter in the Centricity Clinical
Gateway v8.0.2 Service Manual for Windows.
To copy the backup to a NAS or another machine, make the backup locally, then copy
the entire backup directory to the other machine.
3. Collect information about the database for the old CCG installation.
If GE supplied the database for 8.0.1, it should be SQL Server 2008. GE supplied
databases for prior CCG for PACS releases should be Oracle 10g. GE supplied
databases obtained with other (non-PACS) CCG products may be Oracle 11g. The
parameters for a GE supplied database depend upon how the customer obtained the
database. If the customer supplied the database, you need to get the information
from the database administrator.

Table 7 Information for GE or customer supplied database

GE-supplied GE-supplied
CCG 8.0.1 CCG 8.0.1 GE-supplied GE-supplied
(installed with (installed with CCG 5.x or 6.x Oracle 11g Customer
PACS) Analytics)1 for PACS database2 supplied
Type: SQL Server SQL Server Oracle 10g Oracle 11g
Instance MSSQLSERVER MSSQLSERVER OraHomeMERCURY OraDb11g_home1
name:
Port 1433 1433 1515 1521
number:
Admin sa ccg sys sys
user
name:
Admin Contact the GE Helpdesk to obtain the default passwords.
password:
1) The administrator password for an Analytics CCG installation may have been changed. Check with the
database administrator.
2) Oracle 11g might have been installed with some CCG 5.x or 6.x versions for non-PACS products.

Warning: You must change the GE-supplied default passwords before taking
the system live. Until you change the default passwords, you must take measures
to prevent unauthorized access to the server.
4. Stop inbound threads for all Cloverleaf sites.
a. Open Cloverleaf.
Cloverleaf may not be on the desktop, but should be in the Start menu. It may be
listed as Cloverleaf IDE or IDE.
b. Change the server to his_prod by selecting Server > Change on the menus.

2103201-001 110
Chapter 6: CCG Upgrade

c. On the Server Change dialog, click Yes to continue.


d. When you change servers, a dialog saying that there is a lock on the site that may
open. Click Yes to continue.
e. Select the file path containing his_prod and click Apply.

f. Click Runtime, on the left side of the window, then click (Network
Monitor).
g. Right-click on each thread with an arrow pointing toward the HIS_OB_CCG thread
and select Stop from the context menu.
Cloverleaf represents each thread with a box in the Network Monitor view. The
name of the thread appears at the bottom of the box.
Note: Sometimes the pane containing the threads gets too narrow. If you
do not see any threads, drag the pane dividers so that the panes
are wider (there might be a pane divider against the right edge of
the window).

2103201-001 111
Chapter 6: CCG Upgrade

Figure 77 Narrow panes

h. Change the server to ccg_prod.


i. Stop the ENM_Inbound thread.
j. Open any remaining sites and stop all inbound threads.
Expected Result: Each inbound thread turns red when it stops.
5. Wait until CCG finishes processing all messages in all threads for all Cloverleaf sites.
Threads with no pending messages turn yellow.
You can also check how many pending messages are left as follows:
a. From the Network Monitor page, right click on an outbound thread (any thread
that you did not stop in the previous step) and select Status.
b. The Status report dialog shows the number of pending messages.

6. Open a site and select Monitor Daemon > Stop (in the upper right corner of the
CCG window).
Important You must stop inbound threads before stopping the Monitor
Daemon. If you do not, you lose any data currently pending in CCG.
This stops the remaining threads on the site.
7. Stop the remaining threads on all the remaining sites.
8. Take note of any Webmin custom configurations or new users.
That is, take note of any customizations to any of the information on the Webmin
page in Webmin. The easiest way to do this is go through all the screens on the
Webmin page and take a screen capture of each one. A CCG installation may have
no Webmin customizations.

2103201-001 112
Chapter 6: CCG Upgrade

Note: Webmin passwords are reset to the default during an upgrade. The
upgrade process removes any Webmin custom configurations or
additional Webmin users beyond the default.
9. Close all applications.
Open Task Manager to see if there are any open applications. Close any open
applications. Disable any antivirus software while you upgrade the software. After you
upgrade, be sure to re-enable your antivirus software.
Warning: To prevent malicious corruption or transmission of sensitive medical
data, you must install and start a virus scanner that runs in real time.
10. Stop the Cloverleaf service. Open Control Panel, click Administrative Tools, click
services, Stop the service “Cloverleaf Integration Servicesâ€
a. Select StartAdministrative ToolsServices
b. Select CLOVERLEAF(R) Integration Services.
Note: In older versions of CCG, this service may be called QDX (TM)
Integration Services.
c. Click Stop.
11. Make sure that there are no other remote desktop sessions active on the CCG server.
a. Open the Windows Task Manager.
b. Click the Users tab.
c. You are the user with the icon in the User column. Tell any other users to log off.

6.1.2 Upgrade CCG

To upgrade CCG (Centricity Clinical Gateway) from previous versions:


1. Insert the new CCG media into the drive.
2. Open the contents of the media.
3. Right-click the Install CCG.bat file and select Run as Administrator.
Expected Result: Several command windows open, then close. The InstallAnywhere
dialog then shows a progress bar as the program prepares the installation. This
may take a few minutes.
4. When the uninstaller asks you to Please confirm CCG upgrade, click Yes.
5. If you get a Please Uninstall Cloverleaf error dialog, click OK. When the CCG installer
exits, use Add/Remove Programs in the Control Panel to remove Cloverleaf.
6. If you get a Pending Messages error dialog, click No to stop the installation process.
When the CCG installer exits, use Add/Remove Programs in the Control Panel to
remove Cloverleaf.
The error occurs when a previous version of Cloverleaf is installed, but CCG is not
installed.
Expected Result: Once you confirm the upgrade, the uninstaller checks for pending
messages in the Cloverleaf sites.
Before installing, you should have stopped all threads in all sites, so there should
not be any pending messages. If the uninstaller finds pending messages, it opens
the Pending Messages dialog.
If the uninstaller finds any pending messages, it opens the Pending Messages dialog.

2103201-001 113
Chapter 6: CCG Upgrade

This dialog indicates the number of pending messages in each site.


7. If the uninstaller indicates that there are pending messages, click No to exit the
uninstaller, and then stop the threads on all sites, starting with incoming threads.
8. When the uninstaller asks you to Please Confirm Database Backup, click No.
The database is retained during the upgrade.
Note: You should back up the database before the upgrade. Backing up the
database during the upgrade increases the length of time the system is
down for the upgrade. Some systems may not have a database installed
with the older CCG. If that is the case, the uninstaller skips the DataBase
Backup dialog.
Expected Result: The uninstaller proceeds to uninstall CCG.
9. Once the un-installation completes, the uninstaller may ask to confirm an automatic
reboot. If it asks, select Yes .If it does not ask, it will reboot.
Expected Result:After the system reboots, the Centricity Clinical Gateway 8.0 Installer
opens.

6.1.3 Running the CCG 8.0 Installer Wizard


Prerequisite: Close all applications and disable any antivirus programs before beginning
the installation procedure. Be sure to re-enable your antivirus programs after you
complete the install.

Warning: To prevent malicious corruption or transmission of sensitive medical data, you


must install and start a virus scanner that runs in real time.
1. Insert CCG media into the drive.
2. Copy the installation zip file to the Analytics server.
3. Extract the installation files from the zip file on the server to a folder on the desktop.
4. Open the extracted installation folder.
5. Right-click the Install CCG.bat file and select Run as Administrator.
Expected Result: Several command windows open, then close. The InstallAnywhere
dialog then shows a progress bar as the program prepares the installation. This
may take a few minutes.
When this finishes, the Centricity Clinical Gateway 8.0 Installer wizard Introduction
screen opens.
6. Click Next.
7. In the Choose Product Features window, select the options:

2103201-001 114
Chapter 6: CCG Upgrade

● CCG Core Components


● DMWL
● DMWL MPPS Service

8. Click Next.
This opens the Databse Local/Remote screen.
9. For an Analytics installation, there is typically no DMWL database. Choose Remote to
tell the installer that there is no local database.

10. The Remote DataBase Type screen displays . Select SQL Server, Select the type of
database you are using for DMWL at the site, then click Next.
Note: A CCG for Analytics installation may skip this screen.
11. In the Choose Install Folder window, specify the location in C:\ for Centricity Clinical
Gateway software installation.
Default: c:\gehc-it.

2103201-001 115
Chapter 6: CCG Upgrade

12. Click Next.


13. In the Pre-Installation Summary window, verify the summary information, and then
click Install. You can click Previous to change the selected install options.
Note: The feature list and total size of the installation may differ from the
illustration based on the components selected for installation.

14. Monitor the progress of the installation on the Installing Centricity Clinical Gateway
8.0 page.

15. On the Install Complete page, make sure the installation succeeded, then click Done.
Expected Result: The system reboots.
16. Log on as administrator once your system reboots.

2103201-001 116
Chapter 6: CCG Upgrade

6.1.4 Verify the Upgrade


6.1.4.1 Verify Programs are Installed
1. In the Windows Control Panel, open Programs > Uninstall a program
2. Confirm that the following items are installed:
● Centricity Clinical Gateway 8.0
● CLOVERLEAF(R) Integration Services 57MB
● CCG Cloverleaf Package
If any of these items are missing, the install failed. Contact the ROC.
3. Close all open windows.

6.1.4.2 Verify Services are Available


1. On the Windows Start menu, select Administrative Tools > Services.
2. In the Services window, confirm that the following services are available:
● Centricity Clinical Gateway Cache (if cache is installed)
● Centricity Clinical Gateway Service Tools
● Centricity Clinical Gateway Webmin Service
● CLOVERLEAF(R) Integration Services 5.7MB
● DMWL Prod Server
If any of these services are missing, the install failed. Contact the ROC.
3. Close all open windows.

6.1.4.3 Confirm Web Login Page


1. On the Windows Desktop, double click CCG Service Tools
2. Verify that the CCG service tools login page appears.
Note: If the login pages does not display, contact the ROC.
3. Close the login page.

6.1.5 Manually Restore the Backup Location and Schedule


After the CCG upgrade, use the CCG Webmin Service Tools to reset the backup location
and schedule according to site specific needs or from notes made prior to the upgrade.
For information on restoring a backup, see the Scheduling and Restoring Backup chapter
in the Centricity Clinical Gateway v8.0.2 Service Manual for Windows.
1. Login to CCG Webmin Service Tools, using the shortcut on the desktop.
Username: geservice
: <webmin_>
2. For the backup location, click the Service tab.
3. Click System State.
4. Click Configuration

2103201-001 117
Chapter 6: CCG Upgrade

5. Enter the Backup Storage Directory. (You noted the directory while preparing for the
upgrade. See Prepare the Upgrade for CCG (page 109).)
6. Click Update to confirm your backup location.
7. For schedule, click Backup.
8. Enter the schedule that was previously noted down prior to the upgrade.
9. Click on the Save button to confirm your schedule.

6.1.6 Autostart of Interfaces


If CCG was configured to automatically start the Cloverleaf interfaces on reboot, it will
attempt to start them following the completion of the upgrade. However, until the new
license is in place, this script will fail. The script will resume normal operation on the first
reboot after the license file has been copied into place.

6.1.7 Restart the System or Hand Off to ITPS for Integration


If you upgraded from CCG 5.x or 6.x, the system needs a new Cloverleaf (Quovadx)
license. Typically the ITPS integration team handles the Cloverleaf licensing. Inform your
Project Manager that the CCG is successfully installed and it is ready for the Cloverleaf
license.
If you upgraded from CCG 8.0.1, the system should now be up and
How to Connect Analytics to CCG Using Tcl ODBC

6.2 CCG 9.3.2


CCG v 9.3.2 supports automatic upgrade from following versions of CCG:
● CCG v 8.0.2.1
To upgrade from a version of CCG not listed above, first upgrade to the version listed
above, then follow the upgrade procedure in this chapter.
Note: Upgrade is not supported on Windows 2012 Server 64 bit.

6.2.1 CCG Upgrade Worksheet


This work sheet is provided so you can record the necessary information about the
current CCG system configuration and settings. You will need to verify these settings and
configuration when you have completed the upgrade.
Important Print the CCG Upgrade Worksheet (below) so you can record the current
information when noted in the procedure.
Note This data is to be collected during the pre-upgrade procedure to ensure that
no data is missed during the restoration process.
Note Webmin passwords will be reset to their defaults after the upgrade. (To
obtain the default passwords, contact the GE Helpdesk.) Any additional users
created and custom configurations will be lost.
CCG Upgrade Worksheet

2103201-001 118
Chapter 6: CCG Upgrade

1. Computer Information:
● Computer Host Name
● IP Address
● Subnet Address
● Gateway Address
● DNS IP(s)
2. Windows Administrator Password
3. CCG Service Tools (webmin): http://local-
host:10000
● Username (default: geservice)
● Password (default: <webmin_password>)
4. CCG Install Directory: (Default C:\gehc-it)
Suggestion is: <CCG_INST_DIR>
5. CCG Backup Directory:(Default C:\gehc-
it\ccg\backup)
Suggestion is: <CCG_BACKUP_DIR>
6. CCG Pre-Backup Directory
This is where all files are copied to before the
upgrade is started. The CCG backup directory will be
deleted. Suggestion is: C:\CCG_BACKUP_PRE_UP-
GRADE\<CCG_PRE_UPGRADE_BACKUP>
7. Database Type: (Oracle or MS SQL)
8 .Default Schedule Tasks:
● Purge
● Auto Start
● Smatcycle
● CloverleafCleanup
● System_State_Recurring_Backup
9. CCG Purge Rules:
● Purge In-patient records older than
● Purge Out-patient records older than
● Purge emergency patient records older than
● Purge Discharged patient records older than
● Purge Completed/Cancelled orders older than
● Purge orders with Preliminary report older than
● Purge orders with Final report older than
● Purge Open orders that are older than
10. DMWL Server Info:
● DICOM Worklist SCP port
● DICOM Worklist SCP AE Title
● Expiration delay for scheduled exams (in days)
● Expiration delay for unscheduled exams (in days)

2103201-001 119
Chapter 6: CCG Upgrade

● Watchdog runs every day at


● DICOM events capture

6.2.2 Pre-Upgrade Checks

6.2.2.1 Verify Available Space


CCG 9.3.2 software does not require additional space. However, during the upgrade
procedure you are required to back up all the CCG files.
Verify that you have sufficient space (approximately 6 GB free) required for performing the
backups, especially if you have a 33 GB C: drive. If not, call the ROC.

6.2.2.2 Passwords
If you have any special user setups for Webmin other than the standard default account,
you will need to recreate those accounts after the upgrade. Record them on the CCG
Upgrade Worksheet.

6.2.3 Pre-Upgrade Procedures


Important
Stop sending messages to the CCG before proceeding. Also, stop any Real Time
Virus Scanner services running on the system before proceeding. You can start these
services again after CCG software has finished upgraded, but you need to exclude certain
files/folders from real time scanning.

6.2.4 CCG System State Back Procedures


Note Before performing the upgrade, perform a full system backup either through
the UI or Command line.

6.2.4.1 Folder Configuration


To configure a folder for backup:
1. Login to CCG Service tools(webmin).
2. Select the Service tab.
3. Select System state > Configuration in the navigation pane on the left.

2103201-001 120
Chapter 6: CCG Upgrade

4. If desired, change the Backup Storage Directory to any custom backup location, or
keep the existing backup location of C:\gehc-it\ccg\backup\data.
5. Click Update.

6.2.4.2 CCG System State - Scheduling Backup


Note Depending on the system configuration, this step could take approximately
5-30 minutes to complete.
To launch the backup page in CCG Service tools (webmin):
1. Log on to the CCG Service tools (webmin)
2. Select the Service tab.
3. Select System state > Backup in the navigation pane on the left. The list of backup
enabled components will now be displayed.
4. In the Backup Configuration page, select Once.
5. In the Backup Scheduling > Time field, type the time in the HH:MM:SS format. It
should be in the range of 00:00:00 to 23:59:59. The system will now display the
current time by default.
6. In the Backup Scheduling > Date field, type the date in the MM/DD/YYYY format.
7. The system will now display the current date by default.
8. Click Reschedule. A One Time Backup will be created with the selected configuration.
9. You can also perform a backup from the Command line. At the Command line, go to:
CCG_INSTALL_DIR/backup/bin.
10. Run the command: system_state.pl /backup. Wait for the CCG backup to be
completed.
Expected Result:
Note You are allowed to schedule a backup for a future date/time only.

6.2.4.3 CCG System State - Status Viewer


To check the status of the CCG System State scheduled backups:
1. Log on to the CCG Service tools (webmin).
2. Select the Service tab.
3. Select System state > Status in the navigation pane on the left. The Status page
displays the Last Run time, the Result and the Status of each Backup and Restore
scheduled
The possible values in the Result column are:
● OK
● Failed
● Failed<text>
The possible values in the Status column are:
● Waiting (if scheduled)
● OK
● Failed

2103201-001 121
Chapter 6: CCG Upgrade

● Running
4. The status window also displays the list of Backup-Enabled components.
Note: The timing of the backup can be anywhere from 5 minutes to upward of
1/2 hour, depending on the size of the database.

6.2.4.4 Interface Backup


The Interface Backup tool can be used to create zip files that contain one or more sites.
Such archives are useful for redistributing sites and/or deploying them on multiple systems.
The tool allows user to archive the current interface configuration, as well as the selected
interface engine (Cloverleaf) sites. This includes all associated configuration files,
translation files, input and output record formats.
You should do an interface backup each time you make a change to the interface
configuration.

Backing Up an Interface
To back up an interface:
1. Log on to the CCG Service Tools.
2. Select the Service tab. CCG Service Tools appears in the navigation pane on the left.
3. Select Interface Backup in the navigation pane. The CCG Interface Backup page
appears.

4. In the list of Installed sites, select the site to be backed up. To select multiple sites to
back up, hold down the Ctrl key while making selections.
5. Click Backup selected sites. The Interface Backup tool then backs up the site(s)
selected. The selected interfaces are archived as a “zip” file, with a date and time
stamp. The zip file is then stored in the <CCG install location>\ccg\backup directory
on the local disk.

2103201-001 122
Chapter 6: CCG Upgrade

6. Copy the zip file to an archive directory, such as a different disk on the network, or to
a backup medium.
Note: You should keep a copy of the backup file on a system or disk that will not
be affected if the CCG server suffers a catastrophic failure.

Restoring an interface
To restore an interface, see Restoring Interfaces

6.2.5 Centricity Clinical Gateway (CCG) Interface Engine


Upgrade
Note CCG Interface Engine and CCG Components installer does not support
upgrade to a different drive. Do not upgrade from the existing installation
under C:\ to F:\.
1. Stop the processes and threads for all Cloverleaf sites.
2. Stop the Cloverleaf Windows Service.

3. Check the task manager and ensure that there are no processes running for hciuser.
(These should have been stopped when the cloverleaf windows service was stopped).
4. Unzip the installation media or zip (Cloverleaf-6.1-Windows.zip) file.
5. Right-click on the Install.bat file and select Run as Administrator. InstallAnywhere
prepares the install wizard, which will guide you through the install process. This
may take up to several minutes.
6. Click YES to continue with the upgrade

2103201-001 123
Chapter 6: CCG Upgrade

The progress bar runs at the bottom.

7. Click Restart Windows.

2103201-001 124
Chapter 6: CCG Upgrade

Once the system has finished rebooting, the Centricity Clinical Gateway (CCG)
Interface Engine installer will automatically start.

8. Follow the normal installation steps of CCG Interface Engine (See Centricity Clinical
Gateway Interface Engine Installation, and continue from Step 4.)
The existing sites will be restored under <CCG_INSTALL_DIR>/quovadx/cis6.1/in-
tegrator
CCG v9.3.2 includes an updated version of Cloverleaf (i.e., 6.1). An upgrade from
previous versions will require the request of a new license from Infor. Go to Cloverleaf
License Request Process
Important After the upgrade, you must pull the hostid on the system and
contact the ROC to obtain a new license.

2103201-001 125
Chapter 6: CCG Upgrade

6.2.6 ActivePerl Installation


Follow the Active Perl Installation procedure in Section Active Perl Installation

6.2.7 Centricity Clinical Gateway (CCG) Components Upgrade


Note Patient Data Cache (PDC), DICOM Modality Worklist (DMWL), Centricity
PACS (CPACS) and IHE Interface components only are upgradable from a
previous CCG version.
Note Image Router and MPPS components are not upgrade supported.
1. Unzip the CCG-9.3.2-Windows.zip file and right-click on the Install.bat file.
2. Select Run as Administrator. InstallAnywhere prepares the install wizard, which will
guide you through the install process. This may take up to several minutes
3. Click on YES to continue with the upgrade. The installer will backup and delete the
previous version of CCG.

4. Click on YES to continue with the upgrade. The installer will backup and delete the
previous version of CCG.

2103201-001 126
Chapter 6: CCG Upgrade

A progress bar runs at the bottom.

Once the system has finished rebooting, the Centricity Clinical Gateway (CCG)
Components installer will automatically start.

2103201-001 127
Chapter 6: CCG Upgrade

5. Follow the normal installation steps of CCG Components (See Centricity Clinical
Gateway Components Installation, continue from Step 4.
The configurations from the previous CCG version will be backed up under
C:\backupbeforeUpgrade and restored accordingly.

6.2.8 Restoring Interfaces


The CCG Interface Management page of the CCG Service Tools allows you to restore
interfaces that have been backed up or archived, or backed up using any version of CCG.
Note Restoring interface engine sites overwrite existing site configurations.
To restore an interface
1. Stop the Cloverleaf service by following these steps:
a. Stop the entire threads/processes/Monitor Daemon for the given site via
Cloverleaf IDE if it is already deployed in Cloverleaf.
b. If the Cloverleaf IDE is open, close it now.
c. Open the Services window by selecting Start > Administrative Tools > Services.
d. Select Infor CLOVERLEAF(R) Integration Services 61.
e. Click Stop.
2. Open the CCG Service Tools.
3. Click the Service tab. The CCG Service Tools pane appears in the navigation area
to the left.
4. Select Interface Management. The CCG Interface Management page appears

2103201-001 128
Chapter 6: CCG Upgrade

Note: At this point, you may get a warning message from Internet Explorer
Enhanced Security Configuration. If such a message appears, you will
need to add the website to the Trusted site zone.
5. On the CCG Interface Management page, click Browse...
The following window appears.

6. Navigate to and select the desired interface file.


7. Click Open. The path of the desired file should now be displayed in the CCG Interface
Management page.
8. On the CCG Interface Management page, click Show Valid interface(s).

A list of valid interfaces is displayed.

2103201-001 129
Chapter 6: CCG Upgrade

9. Select the interface that you want to activate.


Note: The Available Interface(s) list allows multiple interfaces to be selected
simultaneously. To select multiple interfaces, hold down the Ctrl key while
making selections.
10. Click on Activate Interface(s) to deploy and activate the selected interface(s).
Note: When an interface is deployed over an existing interface, a backup
of the old interface will be created and can be found in <CCG install
location>\ccg\backup. So, if you had installed CCG in “C:\gehc-it”, you
must look in the “C:\gehc-it\ccg\backup” folder for the backup (.zip) files.
The Deployment Status box will provide the status of deployment and activation of
interface(s) process.

11. Restart the Cloverleaf service by doing the following


a. Select Start > Administrative Tools > Services.
b. Select CLOVERLEAF(R) Integration Services 61 in the list of services
c. Click Start to restart the service.
Note: The ability to restore a zip file that was not archived or created using CCG
v9.3 must be verified with Service team.
Note: Restoring interfaces backed up using older CCG version would require
going through the Cloverleaf Site Promotion procedure prior to site
restoration. For the Cloverleaf Site Promotion procedure, refer to
Cloverleaf Site Promotion guide installed on the CCG server. Search
for Windows Site Promotion in the Help section of Cloverleaf
documentation.

6.2.8.1 Pre-defined Interfaces


The pre-defined interfaces described below are included with CCG:

2103201-001 130
Chapter 6: CCG Upgrade

HIS_PROD
HIS_PROD is a predefined interface that is used to receive inbound HL7 messages from
external, non-GE systems. It then translates these messages into HL7 messages of a
type that can be recognized by CCG and other GE applications. It then routes those
messages to the various outbound threads based on the type of message.
There are four outbound threads:
● HIS_OB_order Raw: Un-translated ORDER messages to be sent to the current
CARESCAPE Gateway
● HIS_OB_adt Raw: Un-translated ADT messages to be sent to the CARESCAPE
Gateway
● HIS_OB_MUSE Raw: Un-translated messages to be sent to Muse
● HIS_OB_CCG: Translated messages to be sent to the CCG_PROD interface
The current default configuration expects to receive all supported types of messages
(HL7 ADT, ORDER, and RESULTS) from the external DIS/RIS/HIS on port 6002 for the
HIS_Inbound thread.
The latest version of HIS_PROD also provides another inbound thread called
NBSS_Inbound on port 6003 for supporting Mammography workflow. This inbound thread
sends translated messages to the CCG_PROD interface.

CCG_PROD
This interface supports ADT, ORDER , and RESULTS message flow to the CCG Local
Patient Cache (if the local cache option was selected during installation). The CCG
pre-defined interface includes three default translation files, one for each destination
listed above.
These files can be modified to add more destination-specific mapping and translation rules
as needed. This interface also takes care of forwarding messages to DMWL and PACS
interfaces if these features are installed and configured.

IHE_PROD
This is the CCG interface that supports MDM message conversion.

IHE_PROD_ORU
This is the CCG interface that supports ORU message conversion.
To make required post-activation changes
The IHE_PROD_ORU interface requires changes to the translate location after it has
been activated. Follow these steps:
1. Launch the Cloverleaf IDE and change the active site to IHE_PROD_ORU.
a. From the main Cloverleaf menu, select Server > Change. You will be prompted
to confirm that you want to continue.

2103201-001 131
Chapter 6: CCG Upgrade

b. Click Yes to confirm. The Select a CLOVERLEAF(R) Integration Services Server


and Environment dialog appears.
c. Select the IHE_PROD_ORU interface.
d. Click Apply.
2. When the site opens (and is listed in the first line of the Site Manager pane), click the
Configuration button in the Launch Bar
3. Click the Network Configurator button.

The NetConfig interface appears on the right.


4. Right-click on CDA_Outbound and select Thread Properties from the context menu.
5. Select the Outbound tab.

6. Click on the Edit button next the TPS Outbound Data field. The Outbound TPS Editor
window appears.
7. Click the Edit button in the new window. The TPS Properties window appears.

8. Replace the contents of the Args field with the path of the .xsl style sheet you want to
use.
9. Click OK to exit out of each of the three windows that you just opened.
10. Restart the processes/threads in ihe_prod_oru site to reset the settings.

2103201-001 132
Chapter 6: CCG Upgrade

XDR_SENDER_PROD
The sender site accepts a soap request with SAML header and CCDA document
as an XOP attachment if the SAML tag value is equal to NHIN_SAML in the hie-
configuration.xml file under CCG_INSTALL_DIR\conf.
The site validates the SAML header and extracts the attachment. The TCL script on the
route creates a new soap request and sends it out to the CCG IHE Adapter Service
listening on port 9000 if the request is valid. The CCG IHE adapter propagates the same
SAML header to the DRR.
The XDR sender site sends the NACK back to the sending system if the SAML header is
not valid, the SAML header is not present, or the SOAP body is not valid.
If the SAML tag is not equal to NHIN_SAML, the site it ignores the SOAP header in the
request.
Network Monitor

The wsserver and wsclient_outbound threads are Java Driver threads that take as input
ITI41_Server.xml and ITI41_Client.xml configuration files respectively.
The ITI41_Server.xml file can be modified to change the endpoint address of
http://localhost:9002/ccg/ihe/ccdaIti41 on which the wsserver listens for any
incoming soap requests. Thread wsclient_outbound sends the newly generated
soap request by TCL script to the endpoint address of the CCG IHE Adapter at
http://localhost:9000/ccg/ihe/CcdaIti41Service.
The WSDL and the configuration files for the XDR sender site are located in the
<CCG_INSTALL_DIR>\quovadx\cis6.1\integrator\xdr_sender_prod\javadriver folder.
To change the endpoint address of the WSDLl for the XDR Sender Web Service
If sending from an external location to CCG other than localhost, modify the address
property in the ITI41_Server.xml file with the IPV4 address of the machine on which
CCG is installed.
Example
If 3.20.156.56 is the CCG IPV4 address, update the address property as follows and
restart the threads and processes in the site: http://3.20.156.56:9002/ccg/ihe/ccdaIti41
To change the Cloverleaf timeout period on the wsclient_outbound thread
The wsclient_outbound thread has a default value of 30000ms. To change this value, edit
the property http:client ReceiveTimeout=”300000” within the ITI41_Client.xml file under
<CCG_INSTALL_DIR>\quovadx\cis6.1\integrator\xdr_sender_prod\javadriver\xdr-
client and restart the threads and processes in the site.
To change the Cloverleaf timeout period on the wsserver thread
The wsserver thread has a default value of 30000ms. To change this value, edit the
property <entrykey="cloverleaf-timeout"value="300000"/> within the ITI41_Server.xml
file under<CCG_INSTALL_DIR>\quovadx\cis6.1\integrator\xdr_sender_prod\javadriv-
er\xdrserver and restart the threads and processes in the site.

2103201-001 133
Chapter 6: CCG Upgrade

To change the Number and Retries and Interval between each Retry on the
wsclient_outbound thread
By default the Outbound tab of the thread is configured for 0 Retries. Edit the Retries and
Interval text boxes to change it to a different value. Restart the thread after the change.

Network Configurator

The Inbound tab of wsserver has the “validateSOAP.tcl” procedure to extract the
attachment and create a new soap request from the template file “soapRequest”. This tcl
procedure will additionally also validate the SAML block and error out if validation fails.
This validation happens only if the flag is set to NHIN_SAML in CCG configuration.
The Inbound tab of wsserver has the validateSOAP.tcl procedure to extract the
attachment and create a new soap request from the template file soapRequest. This TCL
procedure will also validate the SAML block and error out if validation fails. This validation
happens only if the flag is set to NHIN_SAML in the CCG configuration

TCL Procedures
sendResponse.tcl
This script sends ACK/NACK to the sending system based on the status received from
the DRR

2103201-001 134
Chapter 6: CCG Upgrade

The script looks at the statusCode value CCG IHE Adapter sends back to the site. If the
statusCode is 0, it is a failure. If it is 1, it is a success.

validateSOAP.tcl
If the SAML flag is enabled to NHIN_SAML, validateSOAP.tcl does two things primarily:
● Validates the existence of all mandatory elements and attributes
● Validates all mandatory element values and attribute values to ensure that they are
not null
End users have the option to customize the script to validate the SAML block based on
site requirements.

If SAML is not enabled, create the soap request by doing a search and replace in the
soapRequest template file.

2103201-001 135
Chapter 6: CCG Upgrade

If SAML is enabled, create the soap request along with the header with SAML block by
doing a search and replace in the soapRequestwithHeader template file.

Soap Request Template used when SAML is disabled


The template file is placed under the site at <CCG_INSTALL_DIR>\quovadx\cis6.1\inte-
grator\xdr_sender_prod.

Soap Request Template used when SAML is enabled


The template file is placed under the site at <L_INSTALL_DIR>\xdr_sender_prod.

2103201-001 136
Chapter 6: CCG Upgrade

To re-compile TCL procedures for a soap request without optional fields


In cases when the optional parameters such as <xdrFromEmail>, <xdrToEmail>,
<providerName> are not needed in the soap request going out to the CCG IHE Adapter,
follow these steps to re-compile the soap template and TCL procedures.
1) Stop all threads/processes within the site
2) If, for example, <providerName> is not required, open the file extractMetadata.tcl
found in the tclprocs folder within the site and comment out or remove the line set
soaprequest [regsub {\*\*PROVIDERNAME\*\*} $soaprequest $providerName]
3) Open the soapRequest template file within the site and comment the line
<providerName> **PROVIDERNAME**</providerName>
4) Click on the shell window on the Cloverleaf GUI for the site and issue the command
cd tclprocs, then press Enter.
5) Issue the command mktclindex and press Enter
6) Restart the threads and processes within the site.
.
To recompile TCL procedures for a soap header after removing validation checks
Note This is just an example. The changes will differ on the production system
based on the requirements related to validation
Note The following section is for knowledge purposes only. Do not make any
changes to existing software before consulting an HL7 Integration Engineer.
1) Stop all threads/processes within the site.
2) wsu:Timestamp is a required field in the saml assertion block that is validated by the
script for non-null value. To disable this chec,k open the file validateSOAP.tcl in the
tclprocs folder within the site and comment these lines:
#Validate wsu:Timestamp for parent wsse:Security if {$val eq "wsu:Timestamp" &&
$etype eq "START" && $iswsseSecurity eq "1"} { set iswsutimestamp 1}
if {$val eq "wsu:Timestamp" && $etype eq "EMPTY"} { set iswsutimestamp 0 set
isValidSAML "NO" set isValueError "YES" set errorDescription "ERROR validating
SAML. wsu:Timestamp is empty, has no value" break }
3) Click on the Shell Window on the Cloverleaf GUI for the site and issue the command
cd tclprocs and press Enter
4) Issue another command mktclindex and press Enter.
5) Restart the threads and processes within the site. This will make sure that the tcl does
not validate the saml2:AttributeStatement element’s value.

2103201-001 137
Chapter 6: CCG Upgrade

6) Users can now send an empty wsu:Timestamp


Example
<wsu:Timestamp wsu:Id="_1" xmlns:ns17="http://docs.oasis-open.org/ws-sx/ws-
secureconversation/200512" xmlns:ns16="http://schemas.xmlsoap.org/soap/enve-
lope/"></wsu:Timestamp>
To disable Validation checks of mandatory element attribute values [not
recommended]
Note The following procedure is just an example. The changes will differ on the
production system based on the requirements related to validation.
1) Stop all threads/processes within the site.
2) <saml2:Assertion ID="_9ace9cb4-7dc7-4c16-940a-449162cfa843"/> has the
mandatory ID attribute. To disable the check, open the file validateSOAP.tcl in the
tclprocs folder within the site and comment these lines:

3) Click on the shell window on the Cloverleaf GUI for the site and issue the command
cd tclprocs and press Enter.
4) Issue the command mktclindex and press Enter.
5) Restart the threads and processes within the site. This will make sure that the tcl does
not validate the <saml2:Assertion ID="_9ace9cb4-7dc7-4c16-940a-449162cfa843"/>
attributes value.
6) You can now send <saml2:Assertion ID=""/>
To disable Validation checks if the mandatory element itself is present or not [not
recommended
Note This is just an example. The changes will differ on the production system
based on the requirements related to validation.
1) Stop all threads/processes within the site.
2) The <wsu:Created></wsu:Created> element is mandatory in the SAML header. To
disable the check, open the file validateSOAP.tcl found in the tclprocs folder within the
site and comment these lines:

3) Click on the shell window on the Cloverleaf GUI for the site and issue the command
cd tclprocs and press Enter.
4) Issue the command mktclindex and press Enter.

2103201-001 138
Chapter 6: CCG Upgrade

5) Restart the threads and processes within the site.


This will ensure that the tcl does not validate the element name
<wsu:Created></wsu:Created>.
6) You can now send the SAML assertion block without the <wsu:Created></wsu:Cre-
ated>.
ERROR returned if SAML validation fails (SAMPLE ERROR MESSAGE)

XDR_RECEIVER_PROD
The receiver site accepts a soap request with the CCDA document as an XOP attachment
from PIL and extracts the attachment. The TCL script on the route creates a new soap
request and sends it out to any external client configured on the WSClient_inbound thread.

2103201-001 139
Chapter 6: CCG Upgrade

The wsserver and wsclient_inbound threads are Java Driver threads which take as input
ITI41_Server.xml and ITI41_Client.xml configuration files respectively. PIL sends out the
soap request to endpoint address of http://localhost:9003/pil/ccdaXdrService on which
the wsserver listens for any incoming soap requests.
Thread wsclient_inbound sends the newly generated soap request by
the TCL script to endpoint address of the external Service endpoint at
http://localhost:9006/mockCcdaXdrServiceSoapBinding
The endpoint address can be modified to any external service endpoint.
Note The endpoint address in this document is just an example; it will differ based
on the implementation of the external service.
The wsdl and the configuration files for the xdr receiver site are located under the
<CCG_INSTALL_DIR>\quovadx\cis6.1\integrator\xdr_receiver_prod\javadriver folder.
To change the endpoint address of the WSDL for the XDR Receiver Web Service
If sending to an external location from CCG other than localhost, modify the address
property in ITI41_Client.xml file with the IP address of the machine on which the external
service WSDL is running.
Example
If 3.20.156.57 is the external VM IP, update the address property as follows:
http://3.20.156.57:9006/mockCcdaXdrServiceSoapBinding and restart the threads
and processes in the site.
To change the Cloverleaf timeout period on the wsclient_inbound thread
The wsclient_outbound thread has a default value of 30000ms. To change
this value, edit the property http:client ReceiveTimeout=”300000” within the
ITI41_Client.xml found under <CCG_INSTALL_DIR>\\quovadx\cis6.1\integrator\xdr_re-
ceiver_prod\javadriver\xdrclient and restart the threads and processes in the site.
To change the Cloverleaf timeout period on the wsserver thread
The wsserver thread has a default value of 30000ms. To change this value edit
the property <entry key="cloverleaf-timeout" value="300000"/> within the
ITI41_Server.xml found under <CCG_INSTALL_DIR>\quovadx\cis6.1\integrator\xdr_re-
ceiver_prod\javadriver\xdrserver and restart the threads and processes in the site.
To change the Number and Retries and Interval between each Retry on the
wsclient_inbound thread

2103201-001 140
Chapter 6: CCG Upgrade

By default the Outbound tab of the thread is configured for 0 Retries. Edit the Retries and
Interval text boxes to change it to a different value. Restart the thread after the change.

Network Configurator

The Route Messages link from wsserver to wsclient_inbound uses the extractMetadata.tcl
procedure to extract the attachment and create a new soap request from the template
file soapRequest

2103201-001 141
Chapter 6: CCG Upgrade

TCL Procedures
extractMetdata.tcl
This script extracts the attachment in the following manner.

Create the soap request by doing a search and replace in the saopRequest template file.

sendResponse.tcl

2103201-001 142
Chapter 6: CCG Upgrade

This script is placed in Outbound Replies on the Inbound tab of the wsserver to send back
replies with a success or failure response to the PIL that originally sent the soap request
with the XOP attachment.

The script looks at the statusCode value CCG IHE Adapter sends back to the site. If the
statusCode is 0, it is a failure. If it is 1, it is a success.

Soap Request Template


The template file is placed under the site at <CCG_INSTALL_DIR>\quovadx\cis6.1\inte-
grator\xdr_receiver_prod

To re-compile TCL procedures for a soap request without optional fields


In cases when the optional parameters such as <xdrFromEmail>, <xdrToEmail> are not
needed in the soap request going out to external service/endpoint follow these steps to
re-compile the soap template and TCL procedures.

2103201-001 143
Chapter 6: CCG Upgrade

1) Stop all threads/processes within the site


Example
If <xdrFromEmail> and <xdrToEmail> are not required, open the file extractMetadata.tcl
found in the tclprocs folder within the site and comment out or remove the lines:
set soaprequest [regsub {\*\*FROMEMAIL\*\*} $soaprequest $xdrFromEmail] set
soaprequest [regsub {\*\*TOEMAIL\*\*} $soaprequest $xdrToEmail]
2) Open the soapRequest template file within the site and comment out or remove
the lines:
<xdrFromEmail>**FROMEMAIL**</xdrFromEmail>
<xdrToEmail>**TOEMAIL**</xdrToEmail>
3) Click on the shell window in the Cloverleaf GUI for the site and issue the command
cd tclprocs and press Enter.
4) Issue the command mktclindex and press Enter.
5) Restart the threads and processes within the site.

6.2.9 CCG Configuration


6.2.9.1 Modify Scheduled Tasks
Modify scheduled task per the CCG Upgrade Worksheet for each scheduled task.

6.2.9.2 Restore the Backup Database


The example below is for SQL server 2008 for 8.0.2.1. There is no schema change for
CCG 8.0.2.1 to CCG 9.3.2 for SQL Server. If you are performing the upgrade on some
other CCG 8.x version and Database, contact CCG Support for instructions.
Below are the steps for 8.0.2.1, SQL Server. You need to perform this operation for both
CGO and DMWL
1. Open SQL Server Management studio and select the database you need to restore
(CGO/DMWL).

2103201-001 144
Chapter 6: CCG Upgrade

2. Right-click and select Tasks > Restore > Database.

3. Select the file from where the backup is to be restored.


Example
C:\CCG_BACKUP_PRE_UPGRADE\CCG_PRE_UP-
GRADE_BACKUP\ccg_pdc_cache\ data\CGO.bak would be the backup for Patient
Cache. Similarly choose DMWL.bak if you want to restore the DMWL database.

2103201-001 145
Chapter 6: CCG Upgrade

4. Click OK.

5. Select Options.
6. Select Overwrite the existing database (WITH REPLACE).

7. When the restore is complete, the following screen appears.

6.2.9.3 License Cloverleaf


Transfer the license user has obtained from the ROC to the ccg server and place in the
following directory:
CCG_INSTALL_DIR\quovadx\cis6.1\integrator\vers

2103201-001 146
Chapter 6: CCG Upgrade

6.2.9.4 Post Upgrade Changes Required to ccg_prod


Note This step is only applicable if ccg_prod interface existed on older version of
CCG prior to the upgrade and was restored by the components installer.
Cloverleaf IDE should be licensed prior to beginning this activity.
The ccg_prod interface requires changes to the ports after it has been restored.
1. Launch the Cloverleaf IDE and change the active site to ccg_prod.
2. From the main Cloverleaf menu, select Server > Change. You will be prompted to
confirm that you wish to continue.
3. Click Yes to confirm, then select Infor Cloverleaf(R) Integration Services.
4. Server and Environment dialog appears.
5. Select the ccg_prod interface.
6. Click Apply.
7. When the site opens (and is listed in the first line of the Site Manager pane), click the
Configuration button in the Launch Bar.
8. Click the Network Configurator button.

The NetConfig interface appears on the right


9. Click on CCG_OB_PACS and select Properties from the context menu.
10. Click the Properties button.

11. Change the Port to 9092, then click OK to close the Properties window.

2103201-001 147
Chapter 6: CCG Upgrade

12. Click Yes in the Apply Changes window.


13. Click on CCG_OB_DWML and select Properties from the context menu.
14. Click the Properties button.

2103201-001 148
Chapter 6: CCG Upgrade

15. Change the port to 9091 if not already changed, then click OK to close the Properties
window.

16. Click Yes in the Apply Changes window.


17. Click on CCG_OB_CACHE and select Properties from the context menu.
18. Click the Properties button.

2103201-001 149
Chapter 6: CCG Upgrade

19. Change the port to 9095, the click OK to close the Properties window.

20. Click Yes in the Apply Changes window.

2103201-001 150
Chapter 6: CCG Upgrade

21. Click on ENM_OB_CCG and select Properties from the context menu.
22. Click the Properties button.

23. Change the port to 9093, then click OK to close the Properties window.

24. Click Yes in the Apply Changes window.


25. Right-click on ENM_OB_DMWL, then click Delete.
26. Click Yes in the Delete Confirmation window.

2103201-001 151
Chapter 6: CCG Upgrade

27. Right-click on ENM_OB_RIS, then click Delete.


28. Click Yes in the Delete Confirmation window.
29. Save NetConfig
30. Restart the processes/threads in ccg_prod to reset the settings.
Next: How to Connect Analytics to CCG Using Tcl ODBC

6.3 CCG v9.3.7 Upgrade


For information about upgrading from CCG v9.3.2 or later to CCG v9.3.7, see the Centricity
Clinical Gateway 9.3.7 for PACS Installation and Upgrade Manual (DOC1976159).
Note Direct upgrade from CCG versions prior to CCG v9.3.2 is not supported. For
steps to upgrade from an unsupported CCG version, see the Centricity Clinical
Gateway 9.3.7 Installation Manual for Microsoft Windows (DOC1952155).

2103201-001 152
7
How to Connect Analytics to CCG
Using Tcl ODBC
To install, configure, and enable Tcl ODBC:
1) Obtain the Tcl ODBC Zip File (page 153)
2) Install Tcl ODBC (page 153)
3) Configure the Windows ODBC Connection (page 154)
4) Testing the Tcl ODBC Connection (page 157)
5) Configure the Tcl Procedures to Communicate with Analytics (page 159)
6) Validate the Configuration (page 161)
Note This section is applicable to CCG 8.0.1 only. If you’re using CCG 8.0.2, follow
the instructions in .

7.1 Obtain the Tcl ODBC Zip File


● Download the Tcl ODBC zip file for Windows (all versions) from Sourceforge at the
following URL:
http://sourceforge.net/projects/tclodbc/files/tclodbc-win/2.3.1/

7.2 Install Tcl ODBC


1. Unzip the tclodbc.zip file downloaded from Sourceforge to a local folder on the
computer running Cloverleaf version 5.3 or higher.
Note: You will at least need to have a default Cloverleaf site in order to set the
shell environment to support installation of the tclodbc.
2. Select Start > Run and type cmd to open a Command window.
3. Type the following commands:
a. cd desktop
b. cd tclodbc
c. setroot

2103201-001 153
Chapter 7: How to Connect Analytics to CCG Using Tcl ODBC

d. setsite <cloverleaf_site>
The cloverleaf_site in the example below is ccg_prod.
e. hcitcl SETUP.TCL
f. hcitcl
This command give you a hcitcl prompt.
g. At the hcitcl prompt type: package require tclodbc.
The return value from this command should be 2.3, the same as the version
number of the installed tclodbc package.
h. Type exit twice (once to exit hcitcl and once to exit the Command window).
Example:

7.3 Configure the Windows ODBC Connection


Prerequisite: These instructions assume you are installing on a Windows Server 2008
R2 / Windows Server 2012 R2 system with SQL Server.

1. Launch the ODBC Administrator in 32 bit mode.


a. Select Start > Run
b. Enter C:\Windows\SysWOW64\odbcad32.exe.
c. Click OK.

2. Select the System DSN tab.

2103201-001 154
Chapter 7: How to Connect Analytics to CCG Using Tcl ODBC

3. Click Add.
4. Scroll down the driver list and select SQL Server Native Client 10.0.

5. Click Finish.
6. Fill in a name, description, and SQL server instance IP address in the first section of
the Create a New Data Source to SQL Server wizard.

2103201-001 155
Chapter 7: How to Connect Analytics to CCG Using Tcl ODBC

7. Click Next to continue.


8. Select With Sql Server authentication using a login ID and password entered
by the user.
9. Enter the appropriate user name in Login ID.
10. Enter the appropriate Password.

11. Select the Change the default database to: checkbox


12. From the dropdown menu, select the appropriate database instance for your
application (typically, Analytics).
13. Click Next to continue.

2103201-001 156
Chapter 7: How to Connect Analytics to CCG Using Tcl ODBC

14. Click Finish when presented with more options related to performance and tuning.
15. Select Test Data Source and review the output. The last line should read TESTS
COMPLETED SUCCESSFULLY!

7.4 Testing the Tcl ODBC Connection


1. This test is best accomplished by launching the cmd shell window from the Cloverleaf
IDE to ensure that the environment variables are set correctly.

2103201-001 157
Chapter 7: How to Connect Analytics to CCG Using Tcl ODBC

2. In the cmd window, type the following commands:


a. hcitcl
This launches the Tcl interpreter.
b. package require tclodbc
This loads the tclodbc package.
c. database connect <identifier> <odbc db name> <username> <password>
<identifier> names the connection within this Tcl session. This can be any legal
identifier.
<odbc db name> is the windows odbc administrator name created during the
odbc setup. Typically, this is analytics.
<username> is the database username.
<password> is the database password for the specified username.
Expected Result: When the command is successful, the return value is the same as
the user specified identifier for the hcitcl connection.
An error is returned when the login fails, the error is dependent on the reason for
the connection failure (i.e. Data source not found indicates that the database name
specified in the command was not the same as a 32 bit datasource name in the
windows odbc administrator.
3. A sample sql command can be given to test the connection by using the identifier
followed by a sql statement in quotation marks.
Example:

2103201-001 158
Chapter 7: How to Connect Analytics to CCG Using Tcl ODBC

7.5 Configure the Tcl Procedures to


Communicate with Analytics
To configure the Cloverleaf Analytics standard site Tcl Procedures to communicate with
the Analytics standard site:
1. After deploying the Standard Voyager Cloverleaf Site, open the Network Configurator.

2. Open the thread properties for the voyager thread and click on the inbound tab.

2103201-001 159
Chapter 7: How to Connect Analytics to CCG Using Tcl ODBC

3. In the TPS Outbound Data configuration pane, click the Edit command button to open
the TPS properties window TPS Editor.

4. Highlight the tps_validate TCL procedure and click the edit command button to bring
up the user arguments window.
5. Input the user and user password arguments in the form of {USER <username>}
{PASS <user pass>}

2103201-001 160
Chapter 7: How to Connect Analytics to CCG Using Tcl ODBC

6. Click the OK command button in the TPS Properties Window, then the OK command
button in the thread properties window to return to the Network Configurator window,
click the save icon (floppy disk) in the shortcut command button to save the Network
Configuration, then launch the Network Monitor Tool.
7. In the process monitor pane, right click the voyager process to bring up the process
command popup and select Control > Stop.
8. Allow the process to stop at which point the color of the process should change from
Green to Red.

Running process is green

Stopped process is red


9. After the process has stopped right click the voyager process icon in the process
monitor to bring up the process command popup and select Control > Start.

7.6 Validate the Configuration


1. Make sure that the client is sending transactions through the cloverleaf receiving
thread, after a transaction has been sent from the client hospital system modality, right
click the voyager thread to bring up the thread command popup and select Control >
Full to bring up the full control dialogue window.
2. From within the full control dialogue window select and execute the watch output
command button.
3. Review the output and ensure that the output shows an instance of the string “return
from sql comd is 0”

2103201-001 161
Chapter 7: How to Connect Analytics to CCG Using Tcl ODBC

2103201-001 162
8
Site Configuration
To configure a site, you:
1) Edit the Client Configuration Files (page 163)
2) If necessary, How to Change the Backup Configuration (page 164)
3) Load Master File Data (page 168)
4) Map HL7 to Analytics Parameters (page 171)

8.1 Edit the Client Configuration Files


You need to configure basic parameters (App.config) which apply to all Analytics clients.
Depending upon the site, you may also need to configure columns on the grid in the
Analytics Real-time Dashboard clients (GridColumns.Config).
To edit a configuration file:
1. Log in as Administrator on the server and select Start > Administrative Tools >
Internet Information Services (IIS) Manager
On Windows Server 2012, press Windows key + R to get the Run command window
and type inetmgr.
Expected Result: This opens the Internet Information Services (IIS) Manager window.
2. In the Connections column, select [server where IIS is running] > Sites > Default
Web Site > Analytics
3. Right-click on Analytics and select Explore.
Expected Result: This should open to the Analytics Web Application home directory.
4. Make a backup copy of a config file by selecting it, then pressing Ctrl-c, then pressing
Ctrl-v.
5. Right-click the config file and select Open to open it in the default text editor (probably,
Notepad).
Refer to the following for the proper configuration settings:
● GridColumns.config (page 164)

2103201-001 163
Chapter 8: Site Configuration

8.1.1 GridColumns.config
The entries in GridColumns.config specify which columns in the Real-time Dashboard grid
are visible, how the columns are labeled, and which columns the user can edit. The config
file specifies column parameters in xml format. Each add element in the file corresponds
to a column on the data grid. The attributes of each add element control a column display.
Example:
<?xml version="1.0"?>
<GridColumnsConfiguration>
<gridColumns>
...

<add name="dept_code" header="Department" readOnly="true" />


...
</gridColumns>
</GridColumnsConfiguration>

In this example, the dept_code column is given the heading, Department. The column is
read-only.

Attribute Description
name The name of the database column.
Note Timer does not exist as a column
in the database. It is created on the fly.
header The header displayed in the grid column.
If the site-specific terminology is different
than the GE-standard terminology, change
the headers to reflect the site-specific
terminology.
readonly To prevent users from editing data in the
column, set readonly to "true". To allow
the user to edit data in the column, set
readonly to "false". Typically, you keep
most columns read only.
Note You must set Timer to
readonly="true".
group Setting the group value of multiple grid
columns to the same string will group the
columns together when selecting new
columns to display.

8.2 How to Change the Backup Configuration


When you install Analytics, the installer schedules a script to back the database up every
day at 11:00 pm, and to keep the last 3 backups. It will create seprate directory for each
full backup in the default SQL Server backup directory.The script stores backups in the
default SQL Server backup directory (on the same RAID as the database itself).
Note The automated backups are full backups of the database. There should be
no need to do incremental backups.

2103201-001 164
Chapter 8: Site Configuration

Typically, when the SQL Server is installed on the Analytics server, the default database
backup location is: D:\Analytics\Backup. All the data files are under D:\Analytics\Data.
Dundas files are located in C:\Program Files (x86)\GE Healthcare\Centricity
Analytics\Dundas.
SQL Server stores the default backup location in the Windows registry. To find this
item in the registry, see the instructions for changing the default backup location in the
last bullet item in the list below.
Note There is a Backup directory in the Analytics application directory. This
directory is used to back up some intermediate data used in an upgrade, not
the SQL Server data.
Note The following procedure documents how to do a Voyager backup.
● If you want to back up the Dundas Dashboard database,
selectDundas_Dashboard_Datastore instead ofVoyager in step 3.
● If you want to back up the ASP.net database, select aspnetdb instead
of Voyager in step 3.
● If you want to back up to and restore from a different server, you have to manually
initiate the backup.
To configure a backup so you can copy it to a different server:
1. Log into the Analytics server as Administrator.
2. Launch SQL Server Management Studio (Start > All Programs > Microsoft
SQL Server 2008 R2 > SQL Server Management Studio) and log in to the
Analytics database.
On Windows Server 2012, press Windows key + R to get the Run command
window and type ssms.
3. In the Object Explorer, navigate to localhost > Databases > voyager.
4. Right-click on voyager and select Tasks > Back Up from the context menu.
5. Select the Options page.
6. Select Back up to a new media set, and erase all existing backup sets.
7. When you initiate the backup it will then create a single backup set which you
can copy to a different server.
● You enable, disable, or change the timing of the backup from SQL Server
Management Studio.
1. Log into the Analytics server as Administrator.
2. Launch SQL Server Management Studio (Start > All Programs > Microsoft
SQL Server 2008 R2 > SQL Server Management Studio) and log in to the
Analytics database.
On Windows Server 2012, press Windows key + R to get the Run command
window and type ssms.
3. In the Object Explorer, navigate to localhost > SQL Server Agent > Jobs >
Backup Voyager Database and double-click Backup Voyager Database.
● To enable or disable the backup:
1) Select the General page.
2) Select or deselect Enable.
3) Click OK.
Example This opens the Job Properties — Backup Voyager Database
window.
● To change the backup schedule:

2103201-001 165
Chapter 8: Site Configuration

1) Select the Schedules page.


2) Double-click the Voyager Backup Job Schedule.
This opens the Job Schedule Properties — Voyager Backup Job Schedule
window.

3) Change the frequency or time of the backup then click OK.


● If you need to change the number of backups the system keeps:
1. Open the Analytics application and log in to the Settings screen (see How to Log
In to the Settings Screen (page 195)).
2. Select Configuration Data in the Settings column and Configuration in the
Data Tables column.
3. Select the row with NUMBER OF ONLINE BACKUPS. in the config_name
column.

4. Click the edit icon ( ).


5. Click Save.
For more information about the Settings screens, see Analytics Administration
and Customization (page 195).
6. Change the config_value to the number of backups you want to keep.
● If you want to change the default location of SQL Server backups (and, thus change
the location of Analytics backups):
1. On Windows server on which SQL Server is running, select Start > Run.
2. Type regedit and click OK.
Expected Result: This opens the registry editor.
3. Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Microsoft
SQL Server > <Server instance> > MSSQLServer.
<Server instance> is the name of the SQL Server installation (which should be
similar to: MSSQLSERVER).
4. Right-click on BackupDirecotry and select Modify.
5. Change the Value data to the new SQL Server default backup directory and
click OK.
Expected Result: This saves the new default backup directory.

2103201-001 166
Chapter 8: Site Configuration

6. Exit Regedit.

8.2.1 Differential Backups


When you install Analytics, the installer schedules a script to back the database up
differentially every day at 1:00 am.By default it will take the differential backup every
2 hours.The script stores backups in directory which was created by previous day's
full backup under the default SQL Server backup directory (on the same RAID as the
database itself).
Note The Job for differential backup is Voyager Differential Backup Job.To change
the backup schedule please follow the instruction given in previous section.

8.2.2 How to Restore the Database Backup


If you have scheduled a job to back databse up differentialy then as per the configuration
, it will have set of differential backups.You will need to restore those set of backups in
order the way it got backed up,befor you restore the full backup. First differential backup
should be restored first and the order follows.
Note By default full backup is previous day's backup and differential backups will
be for today.
1. Log into the Analytics server as an administrator.
2. Launch the SQL Server Management Studio (Start > All Programs > Microsoft SQL
Server 2008 R2 > SQL Server Management Studio) and log in to the Analytics
database.
On Windows Server 2012, press Windows key + R to get the Run command window
and type ssms.
3. In the Object Explorer, navigate to localhost > Databases > voyager.
4. Right-click on voyager and select Tasks > Restore > Database.
5. From the Restore Database — voyager dialog, select the backup set you want
to restore and click OK.

6. Log into Analytics and see if you can access the KPIs.

2103201-001 167
Chapter 8: Site Configuration

If there are none available:


a. Log out of Analytics.
b. Log into the database as sa.
c. Enter the following two commands:
sp_change_users_login 'auto_fix', 'analyst'
sp_change_users_login 'auto_fix', 'ccg'
d. Log back into Analytics to make sure you can now access the KPIs.

8.2.3 Other Database Maintenance


You should not have to manually rebuild table indexes or do any database maintenance
other than configure the backups. Analytics automatically rebuilds the table indexes
when necessary.

8.3 Load Master File Data


Master File Data (MFD) tells Analytics how various systems (PACS, HIS, RIS, and other
systems) at the site are configured. When you install Analytics or reconfigure the systems
at a site, you need to be able to load a large quantity of master file data into Analytics.
Use a Master File Data bulk loader Excel Workbook to load this data.
If you just want to edit or add a few Master File Data records, you can use the Settings
screen in Analytics.
To load large quantities of Master File Data:
1. Copy an empty MFD Loader Workbook from the Analytics media.
This file is located at: <Analytics media>\Installer Setup\MasterFileDataLoader\
Analytics-MasterFileDataLoader.xls. The file is a Microsoft Excel spreadsheet
containing macros which call SQL stored procedures in Analytics.
2. Go to the DB Configuration sheet and enter the IP address, username, and
password of the SQL Server, and the name of the Analytics database.
Default username: sa
Default password: <sa_password>
Important You must change the GE-provided default passwords before taking
the system live. Until you change the default passwords, you must
take measures to prevent unauthorized access to the server.
3. Review the MFD Workbook to familiarize yourself with the data required. See the first
page of the MFD Workbook for a summary of each sheet. Comments at the top of
each column in the Workbook summarize the purpose of each column. (Hover over
the red triangle in the top-right corner of a column header to view its comment.)
4. Collect, review, and import your Master File Data into the MFD Workbook. If possible,
you should gather and import the data incrementally. That is, once you have some
data you should go through the following steps to import it into the MFD Workbook
and validate it.
a. Work with the appropriate people at the facility to begin gathering the required
data.
b. Export the data from the systems where it is currently stored into flat Excel or text
files (or any other format which you can import into Excel).

2103201-001 168
Chapter 8: Site Configuration

Note: If you are collecting data from paper-only records, you can enter the
data directly into the MFD Workbook. Skip to step e.
c. If not in Excel, import the data into Excel and organize the data into sheets and
columns to match the sheets and columns in the empty MFD Workbook.
d. Import your data from the spreadsheet you just created into the MFD Workbook.
e. Review and Validate the data.
You should manually review the data with the customer. You should also click
Validate periodically as you import more data into the Workbook.
Expected Result: Validate performs rudimentary error checking on the data in the
current sheet. You can click Validate as many times as you like. After validation,
invalid rows are indicated by a message in the last column.
f. After making any changes to the MFD data, save the file with a new version
number (for example: General_Hospital_v04.xls).
g. Periodically, send the latest version of the Workbook to the GE integrator who will
review the file to make sure the data is what is required.
5. Send the final version of the MFD Workbook to the GE integrator for review.
6. Once you have determined that the data is correct, click Save.
You can Save the data from any workstation that has network access to the Analytics
server.
Expected Result:This loads the data from the current sheet into the Analytics database. If
there is an error, Save skips that row and notes the error in the last column. If the Save
cannot insert a value into a table because of a mismatch or incorrect value, it will stop
executing. The Logs sheet lists the following:
● The name of the procedure called by the Save button.
● The parameters passed to the procedure.
● The return value of the procedure.

8.3.1 Update Relative Value Units (RVU) using Master File Data
The RVU values of a procedure code is set through Master File Data.
1. Click on procedure_RVU_set link which will be directed to procedure_RVU_set
sheet.
2. Click Query All Data button, which displays all procedure codes and RVU values
corresponding to each procedure with effective To and From dates
Note: If no values are set for procedure, only procedure codes will be displayed.
If multiple RVU values are set for procedure codes for different periods,
those records will also get displayed. .
Figure 78 Query All in procedure_RVU_set

3. Enter the Professional RVU, Professional CF, Technical RVU, Technical CF,
Global RVU, Global CF values along with Effective To and Effective Fromdates
against each Procedure Code.
Note: The Procedure Code and Effective Date From dates are mandatory
fields. Procedure Description and CPT Code are read only fields.

2103201-001 169
Chapter 8: Site Configuration

4. Click on Validate Data button to validate the data we want to save. Validation will
check if all mandatory columns are entered. It will show information in “Error” column,
if any mandatory field is missing.
5. Click Save to save all the RVU values for each procedure code.
Note: Each procedure code can have multiple RVU values with different
Effective From and To Dates.
Figure 79 Save RVU values for Procedure Codes

6. Click on Query Latest Data to view the ‘latest active procedure codes’ with RVU
values if set for any procedure code.
7. Click on Query All Active Data to view only procedure codes of active procedures
with the RVU values we set. If no RVU values are set, it will return only the procedure
codes of those procedures, that are active.

8.4 CCG Interface Management


CCG interfaces provide mapping, translation, and routing for HL7 messages. The
Analytics media includes a prod file for the Analytics-specific interface.
To deploy and activate interfaces in CCG:
Note While deploying the interface, ensure that the Cloverleaf IDE service is
stopped.
1. Log in to Webmin and click the Service tab.
Note: When you log in, you may get a warning message from Internet Explorer
Enhanced Security Configuration. If you do, you need to add the
website to the Trusted site zone.

2. Click Interface Management on the CCG Service Tools list.


3. On the CCG Interface Management page, click Browse, and navigate to the interface
zip file (<Analytics media>\ccg\Analytics_prod.zip).

2103201-001 170
Chapter 8: Site Configuration

4. Click OK, then click Show Valid interface.


Expected Result: A list of valid interfaces is displayed in the Available Interface(s) list.
Note: The Available Interface(s) list allows multiple interface selection. To
select multiple interfaces, hold down the Ctrl key while making selections.

5. In the CCG Interface Management window, select interface(s) from the Available
Interface(s) list, and click on Activate Interface(s) to deploy and activate the
selected interface(s).
Note: When an interface is deployed over an existing interface, a backup
of the old interface will be created and can be found in <CCG install
location>\ccg\backup. So, if you had installed CCG in C:\gehc-it, you
must look in the C:\gehc-it\ccg\backup folder for the backup files. The
Deployment Status box will provide the status of deployment and
activation of interface(s) process.

8.5 Map HL7 to Analytics Parameters


Analytics collects information from CCG by reading HL7 (and, possibly, also reading
MPPS).
Since different sites will use HL7 differently, the GE Integration team must use the
Cloverleaf Integration Suite to map HL7 to Analytics parameters.
To map HL7 to Analytics parameters:
1. The GE Support Representative uses a spreadsheet showing HL7 to Analytics
mappings as a guide when talking to the customer.
Note: For a list of PACS events which can be passed to CCG for mapping to
Analytics parameters, see PACS Events (page 219).
2. With Cloverleaf, map the appropriate HL7 codes to the appropriate Analytics stored
procedure parameters.

8.6 How to Give Users Access to Analytics


Users must be assigned to groups that give them access to some or all of the dashboards,
reports, and scorecards they will need to use. See Assigning Users to Groups (page
204) for instructions.

8.7 Summary Table Jobs


There will be summary table for each KPI of type Report and Scorecard. This table
will be created when a new KPI is created.
The summary tables will be named as kpi_<kpi_id>_summary (eg. kpi_40_summary
for KPI ID = 40).

2103201-001 171
Chapter 8: Site Configuration

Along with the summary table, a SQL job will also be created and scheduled to run in a
specific interval (6 hours by default. The database administrator will be able to update this
time interval). The summary table will get updated each time the job runs. The job will
retrieve changes from the last run and will update the summary table.
The jobs will be named as Synchronize_kpi_<kpi_id>_summary. (eg.
Synchronize_kpi_40_summary for KPI ID = 40).
Note Until the job is executed, there would not be any data in the corresponding
summary table and hence there would not be any records displayed in the
Dashboard (Report/Scorecard) for the newly created KPI.
Whenever an existing KPI is deleted (deactivated), the corresponding job will
be disabled. When a deactivated KPI is activated, the corresponding job
will be enabled.
When the key KPI parameters are edited, the data in the corresponding
summary tables will be truncated.
To manually run the job (to populate data in the corresponding summary table):
1. Identify the job for the KPI summary table.
a. Launch SQL Server Management Studio (Start > All Programs > Microsoft SQL
Server > SQL Server Management Studio) and log in to the Analytics database.
On Windows Server 2012, press Windows key + R to get the Run command
window and type ssms.
b. In a New Query window, execute the sql to get the KPI id from KPI description.
use voyager;
select * from kpi;
Figure 80 KPI id and description from KPI table

c. Identify the corresponding job for particular kpi_id under SQL Server Agent
→Jobs

2103201-001 172
Chapter 8: Site Configuration

Figure 81 Job corresponding to the kpi_id

2. Run the corresponding job to populate summary table. Right click the job and Start
Job at Step
Figure 82 Run job to populate Summary table

2103201-001 173
Chapter 8: Site Configuration

Figure 83 Job in Progress

8.8 Enable/Disable EVENTS view Indexes Job


It was identified that the Indexed view EVENTS is the main cause for slowing up the data
insertion and updates when there is a large queue of events waiting to be inserted to the
Analytics database. In order to enhance the performance, two jobs are created.
One job is to disable all the indexes on the EVENTS view which will boost the data
insertion and update performance. Another job is to enable and rebuild the indexes on
the EVENTS view to boost the data retrieval performance.
Figure 84 Jobs to Enable and Disable Index on EVENTS view

Note When the job is created, it will be disabled by default. The service engineer
will have to enable it first and then execute it.
To Disable and Enable Indexes on EVENTS View:

2103201-001 174
Chapter 8: Site Configuration

1. Launch SQL Server Management Studio (Start > All Programs > Microsoft SQL
Server > SQL Server Management Studio) and log in to the Analytics database.
On Windows Server 2012, press Windows key + R to get the Run command window
and type ssms.
2. Right click and enable the corresponding job under SQL Server Agent →Jobs
3. Execute the job.
Figure 85 Execute Job to Disable Indexes on EVENTS View Before Bulk Data Insert

Figure 86 Disable Index Job in Progress

2103201-001 175
Chapter 8: Site Configuration

Figure 87 Execute Job to Enable Indexes on EVENTS View After Data Insert

Figure 88 Enable Index Job in Progress

4. Change the jobs to disabled state after its execution.

8.9 Fragmentation/Defragmentation Jobs


There is possibility for fragmentation of database tables in long run. In order to find the
fragmented tables, a new job is created. This job will generate a fragmentation report and
store the fragmented table details to a permanent table.
In order to defragment these tables and indexes, another job is created. This job will
update the fragmentation report table with details like 'percentage of fragmentation after
defragmentation process', ' timestamp of last update' and 'defragmented flag' .

2103201-001 176
Chapter 8: Site Configuration

Figure 89 Job to Generate Fragmentation Report

2103201-001 177
Chapter 8: Site Configuration

Figure 90 Job to Defragment Tables and Indexes

Note By default, the fragmentation job is scheduled to run at 10 PM every Saturday


and defragmentation job is scheduled to run at 2 AM every Sunday.
To edit the default schedule or properties of the fragmentation/defragmentation jobs:
1. Launch SQL Server Management Studio (Start > All Programs > Microsoft SQL
Server > SQL Server Management Studio) and log in to the Analytics database.
On Windows Server 2012, press Windows key + R to get the Run command window
and type ssms.
2. Right click the corresponding job under SQL Server Agent →Jobs and launch the
Properties of the job.
3. Edit the Schedule to modify the default schedule of the job. Edit the Steps to modify
properties of the job.

2103201-001 178
Chapter 8: Site Configuration

Figure 91 Modify the Schedule of Generate Fragmentation Report Job

Figure 92 Modify the Properties of Generate Fragmentation Report Job

2103201-001 179
Chapter 8: Site Configuration

Figure 93 Modify the Schedule of Defragmentation Job

Figure 94 Modify the Properties of Defragmentation Job

2103201-001 180
Chapter 8: Site Configuration

8.10 Adding Email Notification for SQL Server


Jobs
Following describes steps to set up Database Mail to send an e-mail notification if a
SQL Server job fails:
1. Configure the Database Mail.
a. Open SQL Server Management Studio , connect to the Database Engine,
expand Management, right-click on Database Mail and then click Configure
Database Mail.
Figure 95 Configure Database Mail

b. Click Next in the following screen.

2103201-001 181
Chapter 8: Site Configuration

Figure 96 Database Mail Configuration Wizard

c. Select default option to Set up Database Mail by performing the following


tasks and click Next.

2103201-001 182
Chapter 8: Site Configuration

Figure 97 Database Mail Configuration Task

d. If mail has not been configured yet, a pop-up will appear; select Yes and then
click Next.

2103201-001 183
Chapter 8: Site Configuration

Figure 98 Database Mail Configuration Confirmation

e. Give the New Profile a name and click Add.

2103201-001 184
Chapter 8: Site Configuration

Figure 99 Database Mail New Profile Creation

f. Fill in the necessary information like E-mail address (sender e-mail address),
Display name, Reply e-mail, Server name and SMTP Authentication and click
OK. Click Next.

2103201-001 185
Chapter 8: Site Configuration

Figure 100 Database Mail Account Settings

2103201-001 186
Chapter 8: Site Configuration

Figure 101 Database Mail Profile Details

g. Check the option to make the new profile Public. If the profile is not set to Public,
permissions have to be assigned properly.

2103201-001 187
Chapter 8: Site Configuration

Figure 102 Database Mail Profile Security Settings

h. Review the System Parameters and adjust if needed.

2103201-001 188
Chapter 8: Site Configuration

Figure 103 Database Mail System Parameters

i. Click Finish.
j. Each Action should be completed with status Success. Click Close.

2103201-001 189
Chapter 8: Site Configuration

Figure 104 Database Mail Configuration Status

2. Adjust the properties within SQL Server Agent.


a. Right-click SQL Server Agent and select Properties.

2103201-001 190
Chapter 8: Site Configuration

Figure 105 SQL Server Agent Properties

b. Click on Alert System under Select a page.


c. Under Mail session , select the option to Enable mail profile. Ensure the correct
mail profile is selected.

2103201-001 191
Chapter 8: Site Configuration

Figure 106 Enable Mail Profile in SQL Server Agent Properties

d. Under Token replacement, enable Replace tokens for all job responses to
alerts.
e. Click OK. Restart the SQL Server Agent service.
3. Create an Operator.
a. Under the SQL Server Agent, right-click Operators and select New Operator.
Figure 107 SQL Server Agent New Operator

2103201-001 192
Chapter 8: Site Configuration

b. Type in the recipient email address in the E-mail name and click OK.
Figure 108 Operator Email Details

4. Configure e-mail notification for the required SQL Server job.


a. Expand SQL Server Agent and click on Jobs. Right click the required job for
which e-mail notification has to be added and select Properties.

2103201-001 193
Chapter 8: Site Configuration

Figure 109 SQL Server Job Properties

b. Under Select a page, select Notifications.


c. Enable the first option, E-mail. Then select When the job fails . Click OK.
Figure 110 Setting Notification as Email When Job Fails

2103201-001 194
9
Analytics Administration and
Customization
The Settings screen allows you to edit various administration and customization settings.
Settings are grouped into several categories.

⧫ CATEGORY DESCRIPTION
● Op-Metrics Definition Allow you to customize existing KPIs (Dashboards, Reports,
or Scorecards) or create new KPIs.
● Master File Data Allow you to add or update site-specific information like locations,
modality codes, or procedure codes. To add a large number of MFD settings, use the
Master File Data Loader spreadsheet. See Load Master File Data (page 168).
● Configuration Data Allow you to specify global information like defaults and labeling
on KPI displays.
Note: This is also where you specify the number of database backups to keep.
● Workflow Data Allow you to specify lists of statuses, types, or states used by
Analytics to monitor site workflow.

9.1 How to Log In to the Settings Screen


1. Log in to Analytics, then click Settings.

Expected Result: This opens a login dialog.


2. Enter the user name and password for a SQL Server administrator account:

2103201-001 195
Chapter 9: Analytics Administration and Customization

Default user: sa
Default password: <sa_password>
Important You must change the GE-provided default passwords before taking
the system live. (Log directly into the SQL Server database and
change the SQL Server password for the system administrator.)

9.2 How to Add, Edit, or Delete a Setting


1. If necessary, log into the Settings screen.
2. In the Settings column on the left, select the type of setting you want to add, delete,
or edit.
The options are:
● Op-Metrics Definition
● Master File Data
● Configuration Data
● Workflow Data
See the beginning of Analytics Administration and Customization (page 195) for
descriptions of these options.
3. In the Data Tables column, select the setting list you want to add to or edit.
Figure 111 Settings screen with the Location in the Master File Data selected

4. Add a new setting record or delete or edit an existing setting record.


● To add a setting, click the add icon (+) located in the area of the screen (the detail
area) underneath the listing of existing settings.
This adds an empty record to the list and opens the corresponding fields in the
detail area.
● To edit a setting:
1) Select the row you want to edit.

Note: You may use the page controls ( )


to scroll through the list, or click on a column heading to sort by
that column, or type in a column heading to filter the list.

2103201-001 196
Chapter 9: Analytics Administration and Customization

The check boxes ( ) at the top of the


setting list allow you to show all settings or just those that are
active. See Settings Filters (page 202). Deleting a setting makes
it inactive.
The Refresh button re-reads the data from the database.

2) Click the edit icon ( ) at the top of the detail area (beneath the list of
settings).
● To delete the selected record, click the delete icon (-).
Note: Deleting a setting makes it inactive. The database still retains the
setting and any data collected with that setting. Inactive settings no
longer accept new data.
5. If you are adding or editing a record, enter the new information in the detail area.
When creating any new Settings record, you must enter information in all fields with
bold headings.
Note: Some data can be UNSPECIFIED. UNSPECIFIED and UNKNOWN are
used interchangeably throughout the Analytics user interface.
Expected Result: As you enter data in the detail area, the new information also
appears in the record in the list above.
6. Click Save.
Note: You must either click Save or Cancel before the Settings screen will allow
you to select anything else.
Expected Result:Analytics is updated with your edits. To see your edits in the Dashboard,
Report, or Scorecard pages, log out and log back into Analytics.

9.2.1 Using Exam Modifiers


Exam modifiers let you further define site-specific information presented in dashboards,
reports, and scorecards. For example, exam modifiers can be configured to alert
radiologists that an exam needs to be read. Or, they can be used to exclude research
exams from being read.
Exam modifiers are stored at the exam level and require code book entries.
kpi_countable must be checked to be included in the count.

9.2.1.1 Enabling, Disabling, and Changing the Display Name


1. In the Settings column on the left, select Configuration Data.
2. In the Data Tables column, select Configuration.
3. Select the appropriate exam modifier.

4. To configure the value, click the edit icon at the top of the detail area (beneath
the list of settings).
5. The text entered in the config_value column determines the radio button name that
will display underFilter By.

9.2.1.2 Set the Value of the Modifier


1. In the Settings column on the left, select Master File Data.
2. In the Data Tables column, select Code Book.

2103201-001 197
Chapter 9: Analytics Administration and Customization

3. Select the row where you want to add a value for the exam modifier.

4. Click the edit icon at the top of the detail area (beneath the list of settings).
5. Enter text in the internal_code column. The text entered determines the values
that will display under Group By.

9.2.2 Create/Update Reason For Delay


1. In the Settings column on the left, select Master File Data.
2. In the Data Tables column, select Reason For Delay.
3. Create or update a reason for delay with empty reason for delay type.
Figure 112 Settings screen with the Reason For Delay in the Master File Data selected

4. Click the Save button.


A new/updated delay reason will be created/updated with reason for delay type as
‘UNSPECIFIED.’

2103201-001 198
Chapter 9: Analytics Administration and Customization

Figure 113 Settings screen with the Reason For DelayType as ‘UNSPECIFIED’

9.2.3 Setting Ignore Demotion for an Exam Status


1. In the Settings column on the left, select Workflow Data.
2. In the Data Tables column, select Exam Status.
3. Edit the ignore_demotion check box for any exam status.
The ignore_demotion check box controls whether an exam status should be
demoted based on the order in which the exam status events are received. The
ignore_demotion check box is in checked state by default when the service engineer
adds a new exam status.

2103201-001 199
Chapter 9: Analytics Administration and Customization

Figure 114 Setting ignore_demotion for an exam status.

4. Click the Save button.

9.2.4 Configure Ignore Timestamp when Promoting Events


1. In the Settings column on the left, select Configuration Data.
2. In the Data Tables column, select Configuration.
3. Edit the configuration IGNORE HIGHEST TIME STAMP RULE under group EXAM
WORK FLOW MANAGEMENT.
IGNORE HIGHEST TIME STAMP RULE is set to Y by default.

2103201-001 200
Chapter 9: Analytics Administration and Customization

Figure 115 Settings screen with the Ignore Highest Timestamp Rule in the Configuration
selected

4. Click the Save button.

9.2.5 Create/Update a Staff


● A new staff can be added, updated or deleted as any other Data Tables.
Figure 116 Create / Update a Staff

Note: We need to have a Specialty and Staff Group to create a new staff.
● Use the Specialty under Staff Data Table to create and manage a Specialty.

2103201-001 201
Chapter 9: Analytics Administration and Customization

Figure 117 Create / Update a Specialty

● The Staff Group Data table should be used for creating and managing Staff Group.
Figure 118 Create / Update a Staff Group

9.2.6 Configuring Remote Alerts


To enable or disable and set the time interval for alert notifications:
Note Users can further define their alerts when they set a bookmark by clicking
Add Notification.
1. On the Settings screen, go to Configuration Data > Data Tables > Configuration,
2. To enable or disable notifications, scroll to Boolean Flag To Turn On/Off
Notifications. To enable, set config_value to 1. To disable, set config_value to 0.
3. To specify the alert notification interval, scroll to Notification Check Interval in
Minutes (Minimum 3). To change the interval, set config_value to the desired
minutes.

9.2.7 Settings Filters

The check boxes ( ), at the top of the setting list, allow you to
show all settings (active and inactive), or only show active settings.

2103201-001 202
Chapter 9: Analytics Administration and Customization

To make a setting inactive, select it and click delete (-).

Check box Purpose


Active Excludes inactive settings from the list.
Some Master File Data settings and KPI calculation
settings are for testing, training, or administrative workflow,
but are not intended for general use on a production
system. These settings are marked as inactive. Inactive
settings do not display on Dashboards, Reports, or
Scorecards. Inactive settings also do not accept new data.
All Shows all settings in the list regardless of whether they
are active or inactive.

9.3 Using User Statistics from Service


Console
1. On the Settings page, on the left bottom , Click on Service Console.
2. Service Console window will be opened.
3. Click on User Statistics tab. The first grid displays the details of KPI’s accessed by
All users from different machines in different time periods. The second grid displays
the KPI information that user accessed and number of times each KPI is accessed.
Figure 119 User Statistics View

4. Click on the spinner control, next to Day(s) back to view the statistics details of
previous days.
5. Click the drop down next to Users , to change the user and view the statistics details
of selected user.

2103201-001 203
Chapter 9: Analytics Administration and Customization

Figure 120 Statistical Details of selected user

9.4 Assigning Users to Groups


The Installer will create five default Windows groups to which appropriate users can
be assigned. They are:
● CentricityAnalyticsDashboard – adding a user or group of users allows dashboards
to be viewed.
● CentricityAnalyticsReport – adding a user or group of users allows reports to be
viewed.
● CentricityAnalyticsScorecard – adding a user or group of users allows scorecards
to be viewed.
● CentricityAnalyticsSearch – adding a user or group of users allows access to all of
the events recorded in the system for an exam, patient, or staff.
● CentricityAnalyticsSettings – adding a user or group of users allows access to master
file, configuration, and workflow data.
"Administrators" and the “geservices” account will have access to all features. To access
the Groups file where you will assign users to groups, go to Local Users and Groups.

2103201-001 204
Chapter 9: Analytics Administration and Customization

For additional details about adding users, or users to groups, refer to the Microsoft
Windows online help.

9.5 Viewing Analytics Events in the Event Log


Analytics logs events and errors to the standard Windows Event Log.
To view Analytics events:
1. From Windows, select Start > Administrative Tools > Event Viewer.
On Windows Server 2012, press Windows key + R to get the Run command window
and type eventvwr.
Expected Result: This opens the Event Viewer window.
2. Select Event ViewerWindows LogsApplication in the column on the left.
Expected Result: This shows all logged events from all applications. Analytics events
list Application as the Source.
Note: Other applications on the system may list Application as the Source
for their events.
3. Click the Source column header to sort the events by Source.
Most items should be Information events.

A few items may be Error events.


4. Select an Application event.
Expected Result: This shows a description of the event and other general information.
From the description, you should be able to tell whether Analytics or another
application generated the event.
5. Click the Details tab to see the even details.

2103201-001 205
Chapter 9: Analytics Administration and Customization

9.6 Customizing an Operational Metric (KPI)


Typically, when you want a custom KPI you want one that is similar to an existing KPI.
Note There are two links at the lower-left corner of the Settings screen (Dundas
Dashboards and KPI Parameter Mgmt). These two links take you to tools
that are beyond the scope of this document. There are many undocumented
interactions between the settings you can modify with those tools. Modifying
parameters with these tools can have unintended consequences that are
difficult to troubleshoot. If you do not know the internal details of the Analytics,
do not use these tools.
1. If necessary, log in to the Settings screen.
2. Select Op-Metrics Definition under the Settings column on the left.
3. From the list of Data Tables, choose a Dashboard, Report, or Scorecard KPI.
4. Select the KPI that measures the metric most similar to what you want.
5. Click Clone.
Expected Result: This creates a KPI identical to the one you had selected, except “*
” is added as a prefix to the kpi_code.

6. Select the new clone KPI and click the edit icon ( ).
Note: To create a KPI from scratch, click add (+) rather than edit.
7. Change the kpi_code to better reflect the new metric. You may also add a description
(kpi_desc).
Note: If you do not change the name of a KPI clone, the next time you clone
the same KPI, you will have two KPIs with the same kpi_code. This will
cause confusion and may cause unpredictable behavior.
8. Click Set Parameters.
The parameters define what a KPI measures. The parameters are divided into
general categories.
Note: Do not alter Advanced Parameters unless you are thoroughly familiar
with the internal settings of the Real-time Dashboards. Altering any
advanced parameter could have unintended consequences that may
be difficult to debug.
Hover your cursor over a parameter to see its definition and valid values in a tool tip.
9. Select a parameter you want to modify.

10. Click edit ( ).


11. Edit the kpi_parameter_value.
kpi_parameter_name and kpi_parameter_type are read only.
12. Click Save.
The Parameter Editor will not let you select a different parameter until you click Save
or Cancel.
13. Once you have edited all the parameters you want to change, click the close icon ( )
in the upper-right corner of the Parameter Editor window.
Note: Do not overlap time limit categories when creating KPIs. KPIs with
overlapping categories will give incorrect results. For example, if one
category is 0–30 minutes and another is 15–45 minutes, the same exams
will be eligible for display in both categories. This will give incorrect totals.

2103201-001 206
Chapter 9: Analytics Administration and Customization

14. Log out of Analytics and log back in, then look at your newly created Dashboard,
Report, or Scorecard. If the data shown is not what you expect, then log back into the
Settings window and see if you missed a setting or specified a setting incorrectly.

9.7 Mapping Exam Events to RVU


Components
This configuration decides when to record RVU values for each RVU component
(PROFESSIONAL RVU, TECHNICAL RVU, and GLOBAL RVU) when exam events are
received.
To map exam events to RVU components:
1. Click Settings from the menu bar.
2. Select the Configuration Data setting and the Configuration data table.
3. From the Configuration list, select an RVU component (for example,
PROFESSIONAL RVU).

4. Click the Edit icon .


5. Edit the exam events in the config_value field. Use a comma to separate multiple
exam events.
6. Click Save.
7. Log out and then log in again to apply the changes.

9.8 Optimizing the Database


To optimize the database, you can place indexing on dedicated storage/disk (file group).
Consider moving indexes for the largest database tables to dedicated storage/disk:
● events
● exam_history
● visit
● exam
● person
● patient
● patient_identifier
● series
● exam_pps
● pps
Important: The operations described below are very resource intensive and might
dramatically impact database server performance and table availability.

Create a Dedicated File Group and Database File


1. Log into the Analytics server as an administrator.
2. Launch the SQL Server Management Studio and log in to the Analytics database.

2103201-001 207
Chapter 9: Analytics Administration and Customization

3. In the Object Explorer, right-click the voyager database and select Properties.
a. Click Filegroups.
b. Enter a filegroup name (e.g., FGINDEX) and click Add.
4. In the Object Explorer, right-click the voyager database and select Properties.
a. Click Files.
b. Create a database file and associate it with the new file group.

Attribute Example value


Logical name Voyager_NDX
File Type Rows Data
File Group FGINDEX
Initial Size (MB) 4096 MB (allocate several gigabytes based on need)
Auto Growth 4096 MB (4GB based on space available on dedicated
disk)
Path "F:\MSSQL\Index" (physical file location)
Physical file name "voyager.mdf"

c. Click Add.

Move Nonclustered Index to Dedicated File Group


1. In the Object Explorer, expand the voyager database, then Tables.
2. Select a table (e.g., dbo.exam), then expand Indexes
3. Right-click a non-clustered index, then click Script Index as > DROP and CREATE
to > New Query Editor Window.

A generated script is displayed in the query editor window.


4. Edit generated script to replace PRIMARY (default file group) with FGINDEX
(dedicated file group) as shown below.

2103201-001 208
Chapter 9: Analytics Administration and Customization

Note: If a site agrees on production downtime, you can set the ONLINE option
to OFF.

5. Execute the script.


6. Repeat steps 3–5 for each nonclustered index to move to the dedicated file group.

2103201-001 209
A
Troubleshooting

A.1 Troubleshooting Table


Problem Solution
The screen goes blank. The local storage (Silverlight cache) needs
to be cleared out.
You receive an error when you log in (after
you’ve logged out with a user preference 1) Right click on the application. Then,
dashboard, report, or scorecard open). click the Silverlight button.
Data hasn’t updated on the dashboard, 2) On the Microsoft Silverlight
report, or scorecard. Configuration window, select the
Application Storage tab and highlight
the web site that you want to clear.
Note If you’re not sure which web site
to select and clear, contact your site
administrator.
3) Click Delete.
4) A dialog box prompts you to confirm
that you want to delete application
storage from the web site. Click Yes.
When the application is launched, you ● If it has taken longer than usual for
see a revolving circle. After approximately the application to launch, click Cancel
30 seconds a “continue or cancel” popup to return to the log in screen and try
displays. again.
● If the situation warrants waiting a little
longer for the application to launch,
click OK.

A.2 Create a User in SQL Server


Following describes creation of a new user in SQL Server, if the user does not remember
the sa password
1. Launch SQL Server Management Studio (Start > All Programs > Microsoft SQL
Server > SQL Server Management Studio) and log in to the Analytics database.

2103201-001 210
Appendix A: Troubleshooting

On Windows Server 2012, press Windows key + R to get the Run command window
and type ssms.
2. Expand Securityfolder and right-click Logins.
3. Select New Login

Figure A–1 Create a new login

4. Enter the new user name and password. Uncheck the option User must
change password on next login.

2103201-001 211
Appendix A: Troubleshooting

Figure A–2 Entering new user name and password

5. Click on Server Roles. Server role public will be selected by default.

2103201-001 212
Appendix A: Troubleshooting

Figure A–3 Select Server Roles

6. Click User Mapping and select the msdb database.

2103201-001 213
Appendix A: Troubleshooting

Figure A–4 User Mapping Settings

7. Select Database role membership for msdb as shown in above figure.


8. Select Status and ensure that it matches the figure below.

Figure A–5 Status Settings

2103201-001 214
Appendix A: Troubleshooting

9. Click OK.
The user will be created with the given user name and password.

A.3 Usage of Database Flags


Following describes the various flags and its usage in Analytics database:

Table Flag Name Data Flag Value and Usage


Name Type
id_do- id_domain- int ID Domain Type Flags Bit Map can be used for
main_type _type_flag different purposes. Bit (1) indicates 'Active' Type.
id_domain id_do- int ID Domain Flags Bit Map can be used for different
main_flag purposes. Bit (1) indicates 'Active' Domain.
facility facility_flag int Facility Flags Bit Map can be used for different
purposes. Bit (1) indicates 'Active' Facility. Bit (2)
indicates KPI countable facility.
department dept_flag int Department Flags Bit Map can be used for different
purposes. Bit (1) indicates 'Active' Department.
service ser- int Referring Service Flags Bit Map can be used
vice_flag for different purposes. Bit (1) indicates 'Active'
Referring Service.

2103201-001 215
Appendix A: Troubleshooting

Table Flag Name Data Flag Value and Usage


Name Type
staff_group group_flag int Staff Group Flags Bit Map can be used for different
purposes. Bit (1) indicates 'Active' Group.
specialty spe- int Physician Specialty Flags Bit Map can be used
cialty_flag for different purposes. Bit (1) indicates 'Active'
Specialty.
staff staff_flag int Staff Flags Bit Map can be used for different
purposes. Bit (1) indicates 'Active' Staff.
physician physi- int Referring Physician Flags Bit Map can be used
cian_flag for different purposes. Bit (1) indicates 'Active'
Physician.
location loca- int Location Flags Bit Map can be used for different
tion_flag purposes. Bit (1) indicates 'Active' Location.
equipment equip- int Equipment Flags Bit Map can be used for different
ment_flag purposes. Bit (1) indicates 'Active' equipment. Bit
(2) indicates KPI countable equipment.
procedure proce- int Procedure Flags Bit Map can be used for different
dure_flag purposes. Bit (1) indicates 'Active' procedure. Bit
(2) indicates KPI countable procedure. Bit (4)
indicates procedure with contrast. Bit (8) indicates
'critical test'.
modal- modal- int Modality Code Flags Bit Map can be used for
ity_proce- ity_flag different purposes. Bit (1) indicates 'Active' modality
dure code. Bit (2) indicates KPI countable modality. Bit
(4) indicates linkable modality.
procedure_ procedure_ int Procedure Group Bit Map Flags can be used for
group group_flag different purposes. Bit (1) indicates 'Active' entry.
Bit (2) indicates 'KPI Countable' Procedure Group.
code_book code_flag int Lookup Code Bit Map Flags can be used for
different purposes. Bit (1) indicates 'Active' lookup
code. Bit (2) indicates 'KPI Countable' entry.
reason_fo- reason- int Reason For Delay Category Bit Map Flags can be
r_delay _for_de- used for different purposes. Bit (1) indicates 'Active'
lay_flag reason. Bit(2) indicates 'KPI Countable' reason for
delay
visit_status visit_sta- bigint Visit Work Flow State Bit Map Flag that is set to the
tus_flag Visit Instance when it reached the corresponding
state.
exam_sta- exam_sta- bigint Exam Work Flow State Bit Map Flag that is set to the
tus tus_flag Exam Instance when it reached the corresponding
state.
exam_sta- other_pro- bigint Other Exam State Properties presented as a Bit
tus perties Map. Bit (1) indicates 'ignore exam demotion' flag.
Bit (2) indicates 'Editable State' - to allow Voyager
proprietary exam states be unchecked
procedure- ps_sta- bigint Procedure Step Work Flow State Bit Map Flag
_step_sta- tus_flag that is set to the Procedure Step Instance when it
tus reached the corresponding state.

2103201-001 216
Appendix A: Troubleshooting

Table Flag Name Data Flag Value and Usage


Name Type
event_type event_typ- int Event Type Flags Bit Map can be used for different
e_flag purposes. Bit (1) indicates 'Active' event type. Bit
(2) indicates to 'Ignore Event On Input'. When
turned On, this type of work flow events will not be
logged in Voyager. Bit (4) indicates to 'Ignore Event
On Output'. When turned On, this type of work flow
events will be ignored in output data flow.
configura- config_flag int Configuration Flags Bit Map can be used for
tion different purposes. Bit (1) indicates 'Active'
configuration
person per- int Person Flags Bit Map can be used for different
son_flag purposes. 1 - Person is a Patient. 2 - Person is a
Referring Physician. 4 - Person is a Staff Member.
8 - Person is a Voyager application User. 16 - VIP
Flag. 32 - Person Death Flag.
per- identi- int Person Identifier Flags Bit Map can be used
son_iden- fier_flag for different purposes. Bit (1) indicates 'Active'
tifier identifier.
patient pa- int Patient Flags Bit Map can be used for different
tient_flag purposes 1 - Active Patient record. 2 - Confidential
Patient.
pa- identi- int Patient Identifier Flags Bit Map can be used
tient_iden- fier_flag for different purposes. Bit (1) indicates 'Active'
tifier identifier.
visit visit_flag bigint A Bit Map of all States that a Visit is reached in the
current live cycle. Status Bit (1) indicates an active
Visit.
exam exam_flag bigint A Bit Map of all States that an Exam is reached in
the current live cycle. Status Bit (1) indicates an
active Exam.
proce- ps_flag bigint A Bit Map of all States that a Performed Procedure
dure_step Step is reached in the current live cycle. Status Bit
(1) indicates an active Procedure Step.
series series_flag bigint Series Flags Bit Map can be used for different
purposes. Bit (1) indicates 'Active' series.
kpi_type kpi_type_fl int KPI Type Flags Bit Map can be used for different
ag purposes. Bit (1) indicates 'Active' KPI Type
kpi kpi_flag int KPI Flags Bit Map can be used for different
purposes. Bit (1) indicates 'Active' KPI.
kpi_proce- kpi_proce- int KPI Interface Stored Procedure Flags Bit Map can
dure dure_flag be used for different purposes. Bit (1) indicates
'Active' procedure.
kpi_param- kpi_param- int KPI Interface Stored Procedure Parameter Flags
eter eter_flag Bit Map can be used for different purposes. Bit (1)
indicates 'Active' KPI Parameter Value.

2103201-001 217
Appendix A: Troubleshooting

Table Flag Name Data Flag Value and Usage


Name Type
kpi_at- kpi_at- int KPI Attribute Flags Bit Map can be used for different
tribute tribute_flag purposes. Bit (1) indicates 'Active' KPI Attribute
Value.
ver- compo- int Software Component Bit Map Flags (can be used
sion_con- nent_flag for different purposes). Bit 1 means Active Software
trol Component

2103201-001 218
B
PACS Events
The PACS ENM events to which CCG should subscribe depend upon the needs and
workflow of the site. The table below shows events which Analytics can accept. If you
want an Analytics KPI to use any of these events, CCG must subscribe to the events. You
then map the corresponding HL7 to the proper parameters.

Table B–1 ENM events to which CCG can subscribe

Analytics Stored
Event ID Procedure Description and PACS Trigger
ExamStatusChange 1 EXAM_SET Exam status has changed. This event
encompasses: exam scheduled, exam
canceled, patient arrived, exam verified,
dictated, report transcribed, and exam
completed. The value it has changed to is found
in the state value attribute.
AcquisitionChange 2 SERIES_SET Acquisition state has changed. This event
encompasses Acquisition begun and Acquisition
Complete. The value it has changed to is found
in the state value attribute.
ExamLTAChange 3 EXAM_SET Lta_stat changed such as exam added to
long-term storage or images abandoned from
long-term storage.
OrderUpdated 4 SERIES_SET Any update to the exam other than exam_stat,
acq_stat, fce, report_text, or study_instance_uid,
img_cnt, total frame cnt, rejected frame cnt, last
viewed dttm, rejected img cnt
ExamMerged 5 EXAM_SET Exam merged or Study_instance_uid changed
PatientMerged 6 PATIENT_SET_BY_ID Patient records merged
StudyAddedSTS 7 SERIES_SET
StudyRemovedSTS 8 SERIES_SET
PatientUpdated 9 PATIENT_SET_BY_ID Patient demographic updated. Caused by any
update to patient record other than patient
merge.
ExamViewed 14 EXAM_SET Exam displayed on a workstation.
ExamPrinted 15 EXAM_SET Exam submitted to the print queue.

2103201-001 219
Appendix B: PACS Events

Analytics Stored
Event ID Procedure Description and PACS Trigger
ExamNotesDeleted 16 EXAM_SET This event is generated when an exam note is
deleted for an exam using RA1000. Information
related to the user, exam, and similar parameters
are logged.
For the event to execute, it has to be in the
subscriber event_subscription table (use
get_subscriber_info). That subscriber must also
be active (to verify, check the active flag of the
subscriber table).
PatConfidentialChg 18 PATIENT_SET_BY_ID Confidential patient setting changed.
ExamSent 19 SERIES_SET
RetrieveExam 21 SERIES_SET
StudyLTAChange 22 SERIES_SET
StudyAcqChange 23 SERIES_SET
ImageUpdated 27 EXAM_SET
ImageExported 28 EXAM_SET
WorkitemClaimed 29 EXAM_SET
WorkitemStatusChanged 30 EXAM_SET
ReportViewed 37 EXAM_SET
ExamAddedSTS 38 EXAM_SET Exam added to short-term storage (from either
archive, acquisition or C2C transfer).
Triggered when fetched from archive, acquired
from a modality, or transferred from another site
(C2C transfer).
ExamRemovedSTS 39 EXAM_SET Exam removed from short-term storage (CAM).
This removal occurs when exam is purged from
(any) cache.
ExamSaved 48 EXAM_SET
ReportSaved 49 EXAM_SET
ExamNotesCreated 50 EXAM_SET
SeriesInfo 54 SERIES_SET

2103201-001 220
C
Cloverleaf License
Request Process

C.1 Definitions
● Thread (External or Vendor) CCG communicates with each connected system
through a separate thread. You configure threads in the Cloverleaf Integration
Services NetConfig tool. When you create a thread, you must designate it as either
External or Vendor.
▪ Use an External Thread to communicate with a third-party system.
▪ Use a Vendor Thread to communicate with a PACS or other GE Healthcare
system.
● Connection The protocol through which CCG exchanges data with another system.
For example, you might configure a connection with TCP/IP with an IP address of
111.222.333.444 on port 1234.
Note: Each thread (external or vendor) is associated with a connection.

C.2 Identify Customer Configuration


Based on customer site surveys, identify the following:
● Total number of external production threads required.
● Product deployment configuration.
● Total number of additional production sites needed. By default, the following
production sites are required to be used by predefined adapters. These are used only
if interfaces are activated (based on integration needs).
● his_prod, ccg_prod ,ihe_prod, ihe_prod_oru
● Total number of test sites needed.
● Total number of external test threads required.
● Host ID of the system.

2103201-001 221
Appendix C: Cloverleaf License Request Process

C.2.1 Host ID of the System


1. To obtain the host ID, open Cloverleaf.
Expected Result: The first time you run Cloverleaf, the Please select a Configuration
Server and Environment (Root/Site) dialog opens.
2. Select Use the Local Config Server.
3. Select the default.site path shown under Select a CLOVERLEAF(R) Integration
Services Environment in which to work .

4. Click Apply.
Expected Result: The Cloverleaf Integrator window opens.
5. Click the Runtime tab, then click the Shell Window icon.

Note: Cloverleaf does not support systems with more than one Network
Interface Card (NIC). The system may not have a single host id if it has
more than one NIC.
If you do not get a Command Prompt when you click Shell Window, open a Command
Prompt from the Windows Start menu.

2103201-001 222
Appendix C: Cloverleaf License Request Process

6. In the shell window, change directories using the following commands:


c:
cd \gehc-it\ccg\quovadx\qdx5.7MB\integrator\bin
Where 5.7 is the Cloverleaf version number.
7. In the shell window, enter the following command:
hcihostid
Expected Result:The system responds with the host id of the current Network Interface
Card.
Record this id, so you can enter it in the License Key Request.
Example:

C.3 License Key Request and Installation


To download license data for Cloverleaf, complete the following steps:
1. Any person performing License key requests needs access to the OAC Web site
access, click the Request OAC Access link on the Support Central site link below:
http://supportcentral.ge.com/products/sup_products.asp?prod_id=21919
This is required to get access to the license request site.

2. Log on to the OAC Application web page:


http://oac.health.ge.com/oac/
Option Activation page opens.

2103201-001 223
Appendix C: Cloverleaf License Request Process

3. Click the Healthvison Cloverleaf link.


This takes you to a list containing a single link.
4. Click the link.
5. Enter the customer information.

a. Type the customer number in Customer Number text box, then click Fetch.
b. Click Select in the pop-up window that is displayed.

2103201-001 224
Appendix C: Cloverleaf License Request Process

The Customer Name and Customer Address text boxes are populated with
the selected data.

c. Select the Cloverleaf Version in the Version list.


d. Type the order number in the Order Number text box.
e. Type the non standard site IDs in the Additional Site IDs text box.
f. Click Submit.
6. On the Cloverleaf Option Activation Code Generator page, enter the Host ID you
obtained in Host ID of the System (page 222).

To select the options the customer ordered, type the correct item number in the Item
Number text box.
Click Generate Activator Codes.
7. Click Save License Data for Cloverleaf.

2103201-001 225
Appendix C: Cloverleaf License Request Process

The File download window displays.

8. Click Save to save the license data to the license.dat file in <CCG install
location>\ccg\quovadx\qdx5.7MB\integrator\vers.
To install the license file on another CCG system, save the license.dat file to the hard
drive or to a memory stick, and then transfer to the system being licensed.

2103201-001 226
Appendix C: Cloverleaf License Request Process

C.4 Sample Product Deployment


Configurations
The following product deployment configurations are possible.

2103201-001 227
Appendix C: Cloverleaf License Request Process

2103201-001 228
Appendix C: Cloverleaf License Request Process

2103201-001 229
Glossary
ADT Admit Discharge Transfer
Analyt- Centricity Imaging Analytics Real-time Dashboard
ics
CCG Centricity Clinical Gateway
CCS Clinical Configuration Specialist
For Analytics, the CCS works with the customer to create custom KPIs (Dashboards, Reports, or
Scorecards).
Dash- A graphically presented summary KPI (metric). Dashboards are shown as traffic lights, simple bar
board charts, stacked bar charts, or gauges. You can also view Dashboard KPIs in a tabular format called the
Data Grid.
HIS Hospital Information System
HL7 Health Level 7
Used by CCG to communicate with Analytics and other systems.
KPI Key Performance Indicator
The metric (statistic or measurement) shown in a Report, Dashboard, or Scorecard.
MPPS Modality Perform Procedure Step
This format contains data about what really has been performed by modality equipment during
acquisition. You can configure CCG to accept this data and send it to Analytics.
ORM Order Message
ORU Observation Result
PACS Picture Archive Communication System
PGP Presentation of Grouped Procedures
PM Project Manager
RDP Remote Display Protocol
Report A chart which allows the site to perform an operational analysis that identifies areas which require
improvement. Reports display as a simple bar chart, a stacked bar chart, or a stock chart.
RIS Radiology Information System
Score- A table which shows how well each department did with respect to a particular metric.
card
SIS System Integration Specialist
For Analytics, the SIS performs the HL7 to Analytics mapping and is involved in loading Master File
Data into the product database.
ZSE Zone Support Engineer

230
GE Healthcare
gehealthcare.com

Corporate Headquarters
GE Healthcare
540 W Northwest Highway
Barrington, IL 60010-3076
USA
Tel: +1 847 277-5000 or
1 800-437-1171 or
1 800-682-5327
Fax: +1 847 277-5240

231

Das könnte Ihnen auch gefallen