PACS-IW Site Config Tool

Centricity
PACS-IW

Site Configuration Tool

GE Healthcare IT
Dynamic Imaging Solutions

History
Date Description Revision Initials
08-‐JUN-‐2009 First Draft 1.0 CZ
Oct-‐13-‐2009 Update for 3.7.3 1.1 JA

© 2008 General Electric Company. All rights reserved. Page i

GE Healthcare IT
This page is intentionally blank.
© 2008 General Electric Company. All rights reserved. Page ii

GE Healthcare IT
Table of Contents
1. GETTING STARTED WITH SITE CONFIGURATION TOOL .................................... 1
1.1 ACCESS SITE CONFIGURATION TOOL .............................................................................. 1
2. BASIC CONCEPTS............................................................................................................... 3
2.1 STORAGE AREA AND ROUTE ............................................................................................ 3
2.2 DATA VOLUME ................................................................................................................. 5
2.2.1 Volumes in Different Storage Areas ........................................................................ 5
2.2.2 Multiple Volumes and Volume Watermarks ............................................................ 5
2.2.3 Auto Cleaning ........................................................................................................ 10
2.2.4 Cleaning dependency ............................................................................................. 12
2.3 ROUTES .......................................................................................................................... 12
3. LARGE INSTALLATIONS ............................................................................................... 16
3.1 STORE/FORWARD ........................................................................................................... 16
3.2 DATA MIGRATION .......................................................................................................... 17
4. KNOWN LIMITATIONS IN SITE CONFIGURATION TOOL ................................... 20
5. CONFIGURATIONS IN INFO TAB................................................................................. 25

5.1 SITE LEVEL CONFIGURATIONS....................................................................................... 25
5.1.1 System Security ...................................................................................................... 25
5.1.2 Storage Service ...................................................................................................... 26
5.1.3 System Configuration............................................................................................. 27
5.1.4 First Storage .......................................................................................................... 27
5.1.5 Remote Server ........................................................................................................ 28
5.1.6 Storage Controller Encoding ................................................................................. 28
5.1.7 Support for Enterprise MRN (EMPI)..................................................................... 29
5.2 SERVER LEVEL CONFIGURATIONS ................................................................................. 30
5.2.1 System Service........................................................................................................ 30
5.2.2 Query Retrieve Configuration................................................................................ 30
5.2.3 Guardian Module Configuration ........................................................................... 31
5.2.4 Login Configuration............................................................................................... 32
5.2.5 Audit Service .......................................................................................................... 32
5.2.6 Resource Service .................................................................................................... 33
5.2.7 Storage Service ...................................................................................................... 34
5.2.8 License Service....................................................................................................... 37
5.2.9 System Configuration............................................................................................. 38
5.2.10 Session Service....................................................................................................... 39
5.2.11 First Storage and Host Volume Service................................................................. 40
5.2.12 Anonimization Configuration................................................................................. 41
5.2.13 CD Film Configuration.......................................................................................... 42
5.2.14 DICOM Server Configuration ............................................................................... 42
5.2.15 Job Queue Configuration....................................................................................... 43
© 2008 General Electric Company. All rights reserved. Page iii

GE Healthcare IT
5.2.16 Centera Configuration ........................................................................................... 44
5.2.17 System Security Configuration............................................................................... 45

© 2008 General Electric Company. All rights reserved. Page iv

GE Healthcare IT
1. Getting Started with Site Configuration Tool

Site Configuration Tool is one of the most important tools in PACS IW. It provides a GUI
interface for storage configurations like disk volume management, image routing, auto
cleaning, etc. It also has the interface for switching on and off many system-‐wide
configurations like anatomically-‐related priors, storage commit, query retrieve and others.

Note that Site Configuration Tool does NOT open during installation or upgrade. It must
be manually opened to check the configuration before putting the system to production.

Note that in some large scale and complex configurations, this tool may not open
correctly or allow the user to efficiently configure the system. Consult Engineering when
direct database configuration is necessary.

1.1 Access Site Configuration Tool

1. To activate Site Configuration Tool, the Tomcat and Integrad System Management
services must be running. Verify this in the Integrad Control Panel.

Note that both services are needed. If Site Configuration Tool doesn't open
correctly, restart both services. The Tomcat service should be started first, then the
Integrad System Mamagement service.

2. To access the tool, go to Start → Integrad → Site Configuration. The Site
Configuration Tool displays, as shown in the figure below.

© 2008 General Electric Company. All rights reserved. Page 1

GE Healthcare IT

The title bar shows that the tool is connected to port 80 on the server. Tomcat
needs to be running.

The outer green square represents the server. A large installation will display more
servers (see the sections below).

The blue squares represent storage areas. The arrow pointing from one area to
another is called the Image Migration Route.


GE Healthcare IT

2. Basic Concepts

2.1 Storage Area and Route

A storage area is a container for the storage volumes (partitions or drive letters) that store
the images with a certain format. Different areas store the images in different formats. For
example, the Income area stores the images with at least four and up to five separate files
(.ini, .rst, .dcm, .flg, and possibly .ovl), and the Online area stores the images with .jp2, .jpg.

The arrow pointing from one area to another represents the Image Migration Route, which
defines how the image should be processed, and in what sequence. Different route types
perform different operations on the image or data object until it reaches the final Storage
Area. For example, the Map Route moves files from Incoming to Map area, adds the
study/series/image info to correct the database tables, and gets the image ready to be
compressed. The Compress Route picks images from the Map area, compresses the images
to JPEG 2000 format, updates the image condition in the database and saves the images to
the Online area (which usually is the final archive).

This figure below shows IW-‐supported storage areas.


GE Healthcare IT

1. To view the storage areas, highlight the server box and click the Properties
button. (Highlight only the large server box, not the storage area boxes.) The
Properties dialog displays (as shown in the figure above.)

2. Use the following definitions to understand the storage areas:

Online -‐ Stores the images in JPEG 2000 lossless format. The Viewer can load
images from this area.

Income – This incoming directory stores the images parsed by the DICOM
server. It is a temporary area. As soon as the images move to the next area, they
are removed from this area.

Map -‐ This area stores the images waiting to be compressed. It is also a
temporary area. As soon as the images are compressed, they are removed from
this area.

Note that after the images are moved out of Map area, the empty ncdstudy
folder will remain on this area permanently. Sometimes it could be helpful to
identify the studies that were sent to this server.

Aged -‐ This optional area can be enabled to store images in JPEG Lossy format.
The Viewer can load images from this area.

Archive -‐ This optional area can be enabled to store images to EMC Centera.
The Viewer cannot directly load images from this area. The images must “bring
online” first before viewer can load them.

BringOnline -‐ This area is used in tandem with the Archive area. When an
archived study is requested, it must be brought online from Centera archive.
The Viewer can load images from this area.

Backup and AgedBackup – These areas are optional. The system can be
configured to make an extra copy of Online or Aged data to Backup areas (Online
to Backup, Aged to AgedBackup) as a redundant copy. The Viewer cannot load
images from Backup and AgedBackup.

Forwarding – This area is only used in Store/Forward configuration. When
forwarding images from node to controller, the images are NOT directly copied
from Online (node) to Online (controller). Instead, they go to the Forwarding
area on Controller first, then from the Forwarding area (controller) to the Online
area (controller). The node may not know how many datavolumes the
controller has and the free space on those volumes; therefore it can't determine
which volume the images should be sent to without this extra step. With
Forwarding area, the images get to the controller first, and then the processes
on the controller can determine what the final location should be.


GE Healthcare IT
Note that the Forwarding area is hidden in Site Configuration Tool. It is
implied when forwarding is configured.

Note also that some areas (Recent, ExternalDevice, ExternalDeviceAged) are
not configured using this tool.

2.2 Data Volume

2.2.1 Volumes in Different Storage Areas

The following areas could have more than one data volume (partition):

Online (very common) -‐ IW has a partition size limit of 2 TB. It only supports MBR
NTFS, and 2 TB is the limit for this type of file system. It is very common to
configure a system with more than one online volume, to accommodate more than 2
TB storage. These drives are usually configured in a RAID 5.

Aged (very common) -‐ Same as Online. If the site uses the Aged area as a long-‐term
archive, then the Aged area could have more than one volume. The 2TB MBR NTFS
limit applies the same way.

Backup and AgedBackup (not common) -‐ If necessary, these backup areas can
have multiple volumes also.

BringOnline (not common) -‐ This area can have multiple volumes if necessary.

Note that the Income, Map, Archive area should NOT have more than one
volume.

2.2.2 Multiple Volumes and Volume Watermarks

When multiple datavolumes are defined for a certain storage area, every datavolume must
have a volume watermark so that the system knows when the datavolume is filled and can
start storing images using the next volume.

Every volume must have some free space. The system will have unpredictable problems if
any volume is completely full (0 bytes free). Every volume should have at least 20-‐30 GB
free at all times. The volume watermark is used to define how much free space should be
left on the volume.

There are two volume watermarks -‐ Complete Study and Volume Full. Complete Study
should be slightly higher than Volume Full. For example, Complete Study is set at 30 GB,
and Volume Full is at 29GB. The volume is considered full when the Disk Free Space falls
below the Complete Study watermark. The only exception is if a study is being processed
when the Free Disk Space falls below the Complete Study watermark. At that point, the

GE Healthcare IT
images will continue to be stored on this datavolume until either:
 The study is received completely.
 The Free Disk Space falls below the Volume Full watermark. At this point, the
image will start to be stored on the next volume whether the study has been
completed or not.

By default, the installation will automatically create one volume on the Income, Map, and
Online area.

1. To add more volumes, go to the Network tab and double-‐click the server box.

The following screen displays.

GE Healthcare IT

2. To check the properties of the existing volume, highlight the green box
representing the volume in each area (which is represented by an orange box),
and click the Properties button on the tool bar. The Volume Property dialog
displays.

Note that when there are too many storage volumes in one area, they may
not fit into the area box. Highlight both the area and storage volume boxes to
help to determine which area the volume belongs to.

The Volume Property dialog shows the name of the volume (any string is
acceptable, but the same value as the number field is suggested), its path, and
the Thresholds (volume watermark). The value in Thresholds is in GB.

3. To add another volume, highlight the orange Online area box (not the volume
box inside), and click the Add Storage button.


GE Healthcare IT

The example above shows that the second volume (name=2) is added, and the volume
watermark is set to 30-‐29GB.

Note that the volume path must contain a backslash (\) at the end, i.e.
E:\Integrad\3.7.1\Data\Dstorage\

Note the following issues when using NAS shares:
 IW supports both local volumes (e.g. E:\Integrad\.......) and NAS shares via UNC path
(e.g. \\NASserver\sharename\Integrad\.........).
 When a NAS share is used, configure it via UNC path, not a mapped drive letter.
 When a NAS share is used, IW services (Tomcat, Storage Controller, etc) must run
under the domain account that have read/write privileges to the share so that they
can save to/load from the share.
 With some NAS devices, the folder structure needs to be manually created on the
share before it can be used. You may need to manually create the empty folder tree
\\NASServer\sharename\Integrad\3.x\data\dstorage\
 Temporary areas like Income, Map, Forwarding should NOT be configured on NAS.


GE Healthcare IT

Note that there is no "Save" button in Site Configuration Tool. Any picture
drawn on the screen is saved in database.

To go back to site level (as shown in the figure above), click the black arrow button on the
toolbar.

Note that an area with only one volume has, by default, no watermark defined for that
volume. Immediately after introducing a second volume, however, you must define a
watermark for both the new volume and the first volume. The Migration tab displays in red,
as a warning, if a watermark is not defined for the first volume. (Close and reopen Site
Configuration Tool to see the error.)


GE Healthcare IT

2.2.3 Auto Cleaning

Areas may need to be auto-‐cleaned (purged) for the following reasons:
 In Store/Forward large installations, the node cleans from local storage after the
study is forwarded to the controller.
 When Aged area, or Centera Archive is used, the Online area is usually sized to hold
lossless compressed data for a period of time, and the long-‐term storage of image
data is kept in one of these other areas. The Online area is cleaned because it
doesn't need to hold data permanently. The data will ultimately be stored on Aged
or Archive.
 In Image distribution (Teleradiology) systems, the images are not saved
permanently on IW, so the Online area is cleaned to reuse the space.

GE Healthcare IT

The following figure shows how to configure auto-‐cleaning. In this case, the Aged area is
used to permanently store data, and the Online area is configured to clean.

1. To configure auto-‐cleaning, highlight the Online area.
2. Click the Properties button.
3. Check the "Enable clean area" checkbox.
4. Define the cleaning watermark via the first two fields. (These are required; the
other fields are explained in step 5.)
 The Start Cleaning watermark defines how much free space left on the area
(free space combined from all volumes in the area) triggers the cleaning to
start.
 The Stop Cleaning watermark defines how much free space is available
before the cleaning process should stop. As shown in the example, the Stop
Cleaning watermark should always be higher than start cleaning watermark.

Note that when calculating the free space of a storage area, all NON-‐FULL
datavolumes' free space are combined. If the volume is full (i.e., the free space
on the volume is below the volume watermark), then the free space from this
volume is NOT counted in the total free space of the area.

Note that the volume watermark and cleaning watermark should not be
confused. They are two completely different concepts. Cleaning is a process
that permanently deletes image data. Volume watermarks are needed to move
to a new datavolume in order to keep all data safe.

GE Healthcare IT
5. Enter additional values if necessary.
 Start clean area period: Instead of using free disk space, the cleaning can also
control how many days the study is stored on the area. This parameter is not
often used because, as long as there is sufficient disk space, the study can be
kept as long as possible.
 # of studies to clean (one batch): Cleaning is not performed continuously. The
system first deletes the number of studies defined in this parameter and then
hibernates. (The hibernation period is defined in the next parameter.) After
this period, auto-‐cleaning first checks whether the free space on the area has
surpassed the “stop cleaning watermark.” If the free space is below that
watermark, the cleaning process will delete another batch of studies and
hibernate again. This cycle continues until the free space meets the “stop”
watermark.
 Clean Every (min): This value defines the auto-‐cleaning hibernation period, in
minutes.

2.2.4 Cleaning dependency

Some images might not successfully move to the next area. Some images may note age
successfully, for example, and do not move to the Aged area. For this reason, a cleaning
dependency is defined to prevent the cleaning (loss) of a study from Online when it has not
been saved on Aged.

1. To configure a cleaning dependency, click the Backup button. The BackupView
displays.
2. Double-‐click the area that the cleaning area depends on. An arrow displays to
indicate the dependency.
3. There is no save button in this window. Close the window to auto-‐save the
configuration.

Note that a trashcan icon appears on areas that have been configured to clean. If the
area boxes are stacked on each other, drag the boxes to clear the view.

2.3 Routes
Routes, also known as Migration Routes define how the images should be moved between
areas and how the images should be processed during the move.

1. By default, Map and Compress routes are always defined by installation. To add
more routes, click the Add Migration Route button from the main toolbar
2. Click and drag the Source area box to the Destination box.
3. Release the mouse to display the Route Properties dialog, as shown below.
4. Select the Route Type from the drop-‐down list. IW has five types of routes:
 Map route: This route picks up files from incoming, saves the
study/series/image info to the database, and moves the files to the Map area.
 Compress route: This route picks up files from the Map area, compresses the
images to JPEG 2000 lossless format, and saves the files to the Online area.
 Aged route: This route picks up the files from the Online area, compresses the
images to JPEG 2000 lossy format (with user-‐defined compression ratio), and

GE Healthcare IT
saves the files to the Aged area.
 Backup route: This route picks up the files from source area and copies them to
a destination area. The common backup routes configuration includes:
Online (node) → Online (controller)
Aged (node) → Aged(controller)
Online → Backup
Aged → AgedBackup
Note that a study does not have to forward through the backup route in
order for it to be available to a user. As soon as the study reaches the Online
Area on the node, it can be opened.
 Centera route: This route picks up the files from Online area, calls the Centera
API, and delivers data packets to Centera. It saves the CenteraID to the database.

5. Click a tab in the lower pane to define that aspect of the route. Each tab is described
below.
 Schedule: Some routes may not need to run in real time. For example, when
forwarding from Node to controller via a WAN connection, it is common to
schedule the forwarding jobs in off hours so the image transmission doesn't
overwhelm the WAN. Up to four different schedules in a 24-‐hour period can be
configured. Check the checkbox and put in the time range.


GE Healthcare IT
Note that the schedule cannot pass through midnight. For example, to
configure the route run from 6 PM to 6 AM, you must configure two schedules: 6
PM -‐ 11:59 PM and 12:00 AM -‐ 6 AM.
Note also that only forwarding via the WAN (Backup Route) normally needs
to be scheduled. Other routes like income, map, compress, aged and archive
routes usually do not need to be scheduled.
 Aged Ratio: This tab, shown in the figure below, is activated only when an Aged
Route is defined.

IW supports modality-‐based
lossy compression ratios.
Different modality types could
have different lossy
compression ratios, e.g. MG 1,
CT 6, CR 20, etc. If the
compression ratio is not
specifically configured, the
default ratio is 6:1. This default
ratio works well for most
modalities, except MG.

MG images cannot be lossy
compressed. Therefore,
whenever an Aged route is
configured, MG must be
manually configured to 1:1
Aging (no further compression
from lossless).

 Parameters: In the parameters tab, there are two configurations.
Concurrency -‐ This defines how many concurrent threads can run on the route.
For example, if the concurrency is 3 on the compression route, that means 3
images can be compressed in parallel.
Note that this parameter is usually not changed. Many routes may have
problems if the concurrency is higher than 1. Before making any change to
concurrency, consult Engineering.
Migration Type -‐ By default the route processes new images. But sometimes it is
necessary to process existing images again. For example, the system is only
configured with Online area at the beginning, and then later the customer wants
to add Aged area so that the images can be compressed further and save disk

GE Healthcare IT
space. In order to do that, two Aged routes need to be configured: one for new
images in the future, and one for existing images that are already saved in the
Online area, as shown in the figure below.

Note that when migrating existing image routes, the performance could be significantly
impacted and only those studies that do not have any images are migrated. If the study is
partially migrated, then the images not migrated before will not be migrated by this route.


GE Healthcare IT

3. Large Installations

All of the examples above are collected from a single server setup. In a large installation
environment, the same concepts apply, but the actual configuration could be more
complicated. A large installation configuration consists of one large installation (LI)
controller and one or more large installation (LI) nodes. The controller is the master node
and controls the activity on all other nodes. PACS-‐IW has a single point of failure; the failure
of the controller means the system is completely down. It is usually clustered for high
availability. A server is defined as an LI controller or an LI node during the server software
installation. The following figure shows the page from the Server Software Setup (not part
of Site Configuration Tool) that defines the type of server.

Two common large installation configurations are discussed in this section.

3.1 Store/Forward
In this example, the site has Centera archive, with migrate new and old image route to
Centera. Several nodes are forwarding images (Backup Route) to the Controller, some of
the routes are scheduled (dotted line), and some are forwarding in real time (solid line).

GE Healthcare IT

Note that in the entire system, there is only one Centera Archive area, usually configured
on the Controller. If a node needs to send images directly to Centera (usually during data
migration from the legacy PACS), it should use the Archive area on the controller.

3.2 Data Migration

The Data Migration workflow is a special type of store/forward workflow. The difference
between a regular S/F node and the migration node is that the migration node doesn’t save
the image files on the local storage after they are forwarded.

An important feature of a Migration Node is that it allows for images coming from a
migration process (usually prior images coming a legacy PACS) to be handled separately
from new images coming into PACS-‐IW directly from the imaging modalities. This prevents
delays in receiving the new image data while the migration continues.


GE Healthcare IT

In the above example, 10.110.26.32 is the migration server. It has both an Online area and
an Aged area configured as “Temp” areas, so when the images are processed and
compressed on this server, they do not stay on this server. They pass through the storage
on the migration server, and eventually are archived in the Aged area on the Controller
(10.110.28.11).

As soon as the image moved to Aged on the migration server, it is deleted from Online on
the migration server. As soon as the image moved to Aged on the Controller, it is deleted
from Aged on the migration server. All of these file changes/movements normally happen
in a few seconds.

By definition, Income, Map, and Forwarding (hidden) areas are temporary areas. They
should not have files stored permanently. But in Site Configuration Tool, Income and Map
does NOT need to be marked as a Temp area. Forwarding does not display at all.


GE Healthcare IT
1. To configure a Temp area,
double-‐click the Temp area box to
display the Properties dialog.
2. Click the Temporary Area
checkbox in the Area properties
window.

Note that in both examples above, the
S/F nodes clean the online area after the
images are forwarded to controller.
However, on the Controller, the images
are processed further and Aged or
Archived. When defining cleaning
dependency on the nodes, the cleaning
should depend on the final area that
permanently saves the data, i.e. Aged or
Archive on the controller, not Online on
the controller. The figure below
illustrates the principle.


GE Healthcare IT

4. Known Limitations in Site Configuration Tool

This section lists some of the known limitations in Site Configuration Tool. Consider these
issues during configuration.

 In the Network tab, the server boxes may stack together. Click and drag the top
boxes to view the boxes below.


GE Healthcare IT

 In the Migration tab, use the horizontal scroll bar to move to the right if all
servers cannot fit into the initial window. Initially, the scroll bar has limited
length and may not move to the rightmost end. Click in the middle of the
window to expand the scale of the scroll bar.


GE Healthcare IT

If the server does note show in the initial window and must be viewed by scrolling, then you
may not be able to highlight it and the area boxes separately. Instead, drag the entire server
box (with areas inside) to the leftmost position in order to highlight the correct box.


GE Healthcare IT

Note If the number of servers makes moving every server to the left impractical, consult
Engineering to perform direct database access.


GE Healthcare IT


GE Healthcare IT

5. Configurations in Info tab

Besides storage management and image routing configurations, Site Configuration Tool has
another important section, which contains many system-‐wide workflow configurations.
These are accessed through the Info tab. The most common configurations are introduced
in this section.

The configurations can be site level or server level. Site level means the setting applies to
the entire PACS system. Server level means the setting only applies to the selected server.
If other servers need the same configuration, they must be configured individually.

Note that this section of Site Configuration Tool does NOT automatically save the
changes to the database as previous sections do. After a change, the Apply button is
activated. Click this button, enter a description of the change and click OK to save.

5.1 Site Level Configurations

5.1.1 System Security

No changes should be made on this screen.


GE Healthcare IT

5.1.2 Storage Service

Centera IP addresses are defined on Site level, not on the individual server level. IW only
supports one Centera in the entire setup.

To use EMC Centera for long-‐term archive, the Archive area must be added to the Image
Migration route. In addition, the Centera access node IP addresses must be specified from
Site Configuration Tool (as shown in the figure below).
1. From Info tab, click the Storage Service tab.
2. Enable Centera pool and configure access node IP addresses.


GE Healthcare IT
5.1.3 System Configuration

5.1.4 First Storage


GE Healthcare IT
5.1.5 Remote Server

5.1.6 Storage Controller Encoding


GE Healthcare IT

5.1.7 Support for Enterprise MRN (EMPI)

With Centricity PACS-‐IW 3.7.1, you can set the Enterprise MRN for several accounts with a
different local MRN. You can also build a list of candidates to assign a specific study to a
specific EMRN. This functionality provides two levels of integration: study and order.

To activate EMRN:
1. From the server side, start Site Configuration.
2. Select the Info tab.
3. Select Site.
4. From the right pane, select Support for Enterprise MRN (EMPI).

5. Use the following descriptions to set the values:
 EMPI Support — Select EMPI Support and/or EMPI Order Support.
 Default search criteria — Select how to search/build a list of candidates for
matching by enabling Sex as a criteria, choosing a pattern for the patient
name and choosing a pattern for the DoB (i.e., find only those that match the
full date, or those that match the year and month.)
6. Click the Apply button.
7. Restart the StorageController, HL7Server and TomCat services.
8. In Centricity Admin, make sure that the user has the Study-‐Update privilege.
9. Check the Study List under a privileged login. The following items should display in
the right-‐click menu.
 Link Studies

GE Healthcare IT
 Unlink Study
 Build Link Candidates List

5.2 Server Level Configurations

5.2.1 System Service

No changes should be made to this screen.

5.2.2 Query Retrieve Configuration
To make IW a QR SCP, Query Retrieve must be turned on. This is a server level
configuration. In a large installation environment, it can be selectively enabled on some
nodes. Normally, no other parameters in this section need to be changed.


GE Healthcare IT

The QR server port is 2104. After the QR server receives the request, it communicates to
storage controller on port 122 to send the request to the database. Therefore, these two
ports cannot be used for any other purpose.

By default, the QR server uses AE Title "DYNIM_QR". To send the studies back to the SCU,
the IP, port, and AET of the SCU need to be added to IW. This is configured in the
IntegradAdmin Client tool, not with the Site Configuration Tool.

5.2.3 Guardian Module Configuration

Please refer to Guardian Documentation for setup and configuration.


GE Healthcare IT

5.2.4 Login Configuration


5.2.5 Audit Service

GE Healthcare IT

5.2.6 Resource Service



GE Healthcare IT

5.2.7 Storage Service

1. Use the following definitions to set the relevant checkboxes on the Main tab:

 Allow patient Info update While Manual Matching:
By default, patient demographics are updated only when an order and report
are automatically matched to a study (by accession number and MRN). If this
setting is turned on, then patient demographics are updated when the manual
matching of an order or report to a study occurs. The update to the study is
based on the information from the order or report.

 Mark study As Dictated when Report is received in HL7: This checkbox is
checked by default.
 Visibility Rules: This feature limits users’ visibility to the database. It applies a
rule that displays only selected studies to particular users’ study lists.

2. Click the Auto-‐Fetch tab and set parameters according to the following explanations:


GE Healthcare IT

 Auto Fetch: This feature enables Auto-‐Fetch, which automatically loads relevant
studies. When the first study is closed, the second study in the tab opens
automatically. See the Centricity PACS-‐IW User Guide for more details.
 Auto Refresh: Enable this feature for the use of Auto Refresh. User must enable
Auto Refresh in the preferences of the study list for proper operation.
3. No changes should be made to parameters in the Centera tab.
4. Click the HIPAA tab and use the following information to set parameters.
 Timeout Fields: The first three fields control when the Viewer closes down after
inactivity. The three timeouts (medium, long, no timeout) can be assigned to
different ADM groups (in Centricity Admin), so that the users in those groups
can have different inactivity intervals. Enter a value for each field in minutes.


GE Healthcare IT

 Lock View Timeout (in min): The Viewer automatically sends an “alive” signal to
the server every 30 seconds. If the Viewer does not get a response from the
server after this value is met (one minute = two signals sent to the server), the
Viewer displays a pop up warning on the screen. This message indicates that
the connection to the server might be lost and changes may not be saved to the
server.

This setting also prevents double dictation. Through this parameter, the server
monitors whether a radiologist has a particular study open. If the server does
not receive the Viewer's signal within one minute, it will assume the Viewer has
been closed, and it will release the lock so that another radiologist can open the
study to dictate. Refer to related documents for more details.


GE Healthcare IT

5.2.8 License Service

This section shows the path to IW license file. It also provides the interface to change the
license file when necessary.


GE Healthcare IT

5.2.9 System Configuration


 Storage Commitment: Click the checkbox to enable IW to respond to a storage
commit request from the modality. Then use the IntegradAdmin Client tool to
configure the IP, port and AET of the modality where IW should send the
Acknowledgement.
Note that storage commit could add significant load to the IW database. Use
it for Mammography. Normally Mammography is not read on IW (unless the
site has Cedara integration) and only uses IW for archive.

 Use Anatomic Region For Priors: By default IW always displays the newest prior
study for comparison. To ensure that this prior is a related prior (i.e., the same
anatomical region), click this checkbox. When checked, the system checks the
anatomical region settings in every study for the patient and finds the newest
prior study with the same anatomical region as the current. Refer to related
documentation for more details.

 Use Network Address Translation Access: Click this checkbox if the server will
be accessed by Internet users who connect via a NATed IP address. Otherwise
the Internet users will see black boxes in the Viewer and no images.
2. All tabs relating to RIS (RIS. RIS IDX, IDX Connection and DI RIS) depend on the type
of integration. Configure as necessary.


GE Healthcare IT
5.2.10 Session Service

 Allow local Controller: By default IW only has one session controller, which
resides on the controller server. Click this checkbox on the node server only if it
is necessary for the node to manage the session by its own.

Note that if the node has session controller turned on, then the same user
could login to the node and the controller at the same time.

2. Click the Parameters tab and use the following definitions to set the relevant
checkboxes.

 Session Timeouts: There are two session timeouts -‐ suspend and destroy.
After the Session Suspend timeout has elapsed, the user's license will be sent
back to the pool, but the user's session is not permanently killed. If the user
returns, and during the inactivity, no other user had used this user’s license
from the pool, then the license will be reassigned to the user and that user can
resume working without noticing that the session had been suspended.
However, if there is no license available when the user returns, then the user's
session will be changed from "suspended" to "destroyed".


GE Healthcare IT

If the user leaves for a period that surpasses the Destroy value (in minutes), then the
session will be permanently killed even if there is a license available in the pool.

Session timeout and HIPAA timeout are two different concepts. HIPAA applies to an
individual Viewer opened on the workstation. Session timeouts apply to the session
the user is logged into. If the user's session is destroyed, that user cannot open any
study without logging in again. But if a Viewer is terminated by a HIPAA timeout,
the user can still open the same or a different study within the same session.

Session and HIPAA timeouts are also related. In a way, the HIPAA timeout affects
the Session timeout: as long as a Viewer is open in a user's session, the Viewer
automatically sends signals to the session controller to refresh the user's session.
So before the viewer is terminated by a HIPAA timeout, the user's session will not
timeout.
5.2.11 First Storage and Host Volume Service



GE Healthcare IT

5.2.12 Anonimization Configuration



GE Healthcare IT
5.2.13 CD Film Configuration

5.2.14 DICOM Server Configuration

The information entered here will be used for the PACS-‐IW DICOM server. The Host Name,
Port, Application Title, and Called AE Title can be configured here.


GE Healthcare IT
5.2.15 Job Queue Configuration

No changes should be made on this screen (under either tab, Main or Advanced).


GE Healthcare IT

5.2.16 Centera Configuration


GE Healthcare IT

5.2.17 System Security Configuration

The Active Directory server is configured here. Release 3.7.1 of Centricity PACS-‐IW includes
the Active Directory. In order for Active Directory to work, each user ID in the DB must be
entered as
<domain name>\<user name>

Note that all servers must be in the AD Domain.

To configure Active Directory with Centricity PACS-‐IW:
1. From the server side, start Site Configuration.
2. Select the Info tab.
3. Select the appropriate server.
4. From the right pane, select the System Security tab.
5. Check the “Use Active Directory” checkbox.
6. Enter the Server domain.
7. Enter the Port Number.
8. Enter the User Group.
9. Click the Apply button.
10. Restart Integrad Services.


GE Healthcare IT


PACS-IW Site Config Tool

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

PACS-IW Site Config Tool

Încărcat de

Drepturi de autor:

Formate disponibile

Site Configuration Tool

© 2008 General Electric Company. All rights reserved. Page i

This page is intentionally blank.

© 2008 General Electric Company. All rights reserved. Page ii

5. CONFIGURATIONS IN INFO TAB................................................................................. 25

© 2008 General Electric Company. All rights reserved. Page iii

© 2008 General Electric Company. All rights reserved. Page iv

1. Getting Started with Site Configuration Tool

1.1 Access Site Configuration Tool

© 2008 General Electric Company. All rights reserved. Page 1

© 2008 General Electric Company. All rights reserved. Page 2

2.1 Storage Area and Route

© 2008 General Electric Company. All rights reserved. Page 3

© 2008 General Electric Company. All rights reserved. Page 4

2.2 Data Volume

2.2.1 Volumes in Different Storage Areas

2.2.2 Multiple Volumes and Volume Watermarks

© 2008 General Electric Company. All rights reserved. Page 5

© 2008 General Electric Company. All rights reserved. Page 6

© 2008 General Electric Company. All rights reserved. Page 7

© 2008 General Electric Company. All rights reserved. Page 8

© 2008 General Electric Company. All rights reserved. Page 9

2.2.3 Auto Cleaning

© 2008 General Electric Company. All rights reserved. Page 10

© 2008 General Electric Company. All rights reserved. Page 11

2.2.4 Cleaning dependency

© 2008 General Electric Company. All rights reserved. Page 12

© 2008 General Electric Company. All rights reserved. Page 13

© 2008 General Electric Company. All rights reserved. Page 14

© 2008 General Electric Company. All rights reserved. Page 15

© 2008 General Electric Company. All rights reserved. Page 16

3.2 Data Migration

© 2008 General Electric Company. All rights reserved. Page 17

© 2008 General Electric Company. All rights reserved. Page 18

© 2008 General Electric Company. All rights reserved. Page 19

4. Known Limitations in Site Configuration Tool

© 2008 General Electric Company. All rights reserved. Page 20

© 2008 General Electric Company. All rights reserved. Page 21

© 2008 General Electric Company. All rights reserved. Page 22

© 2008 General Electric Company. All rights reserved. Page 23

© 2008 General Electric Company. All rights reserved. Page 24

5. Configurations in Info tab

5.1 Site Level Configurations

5.1.1 System Security

© 2008 General Electric Company. All rights reserved. Page 25

5.1.2 Storage Service

© 2008 General Electric Company. All rights reserved. Page 26

© 2008 General Electric Company. All rights reserved. Page 27

© 2008 General Electric Company. All rights reserved. Page 28

5.1.7 Support for Enterprise MRN (EMPI)

© 2008 General Electric Company. All rights reserved. Page 29

5.2 Server Level Configurations

5.2.1 System Service

© 2008 General Electric Company. All rights reserved. Page 30

5.2.3 Guardian Module Configuration

© 2008 General Electric Company. All rights reserved. Page 31

5.2.4 Login Configuration

© 2008 General Electric Company. All rights reserved. Page 32

5.2.6 Resource Service

© 2008 General Electric Company. All rights reserved. Page 33

5.2.7 Storage Service

© 2008 General Electric Company. All rights reserved. Page 34

© 2008 General Electric Company. All rights reserved. Page 35

© 2008 General Electric Company. All rights reserved. Page 36