Академический Документы
Профессиональный Документы
Культура Документы
1
System Administration Printable Help
Pub. #8J3225
29 June 2010
Table Of Contents
Preface ........................................................................................................14
Trademark and Copyright Information.......................................................................................................... 14
FCC Compliance ........................................................................................................................................ 14
Safety ..........................................................................................................28
Safety Guidelines ...................................................................................................................................... 28
Hazards.................................................................................................................................................... 29
IEC 60601-1 Classification .......................................................................................................................... 30
Owner Responsibilities ............................................................................................................................... 31
User Limitations ........................................................................................................................................ 32
Safety and Maintenance Rules..................................................................................................................... 33
ii
Table Of Contents
iii
CARESTREAM PACS, Version 11.1 System Administration Printable Help
Auditing .....................................................................................................122
Pre-Filtering the Audit Viewer Tool Window ................................................................................................. 123
Audit Viewer Tool Window ........................................................................................................................ 124
Archiving an Audit ................................................................................................................................... 125
Managing the Display (Audit Viewer Tool)................................................................................................... 125
Field Chooser .......................................................................................................................................... 125
Changing the Fields Appearing in the Audit Trail Viewer ............................................................................... 125
Available Fields for Display ....................................................................................................................... 125
Filtering the Display ................................................................................................................................. 126
Applying Multiple Filters to the Audit Viewer............................................................................................ 126
Applying an Individual Filter to the Audit Viewer...................................................................................... 126
Sorting the Display .................................................................................................................................. 126
Refreshing the Display ............................................................................................................................. 126
Viewing Event Details............................................................................................................................... 127
v
CARESTREAM PACS, Version 11.1 System Administration Printable Help
vi
Table Of Contents
Moving Studies to Another Patient (Storage Management Admin Tool) ........................................................... 159
Detaching Studies ............................................................................................................................... 161
Moving an Incorrectly Attached Study to a Newly Created Patient (Split) .................................................... 161
Split and Merge Series Pre-Fetched from External Archive(s) .................................................................... 162
Splitting a Series from One Study to Another .......................................................................................... 163
Merging a Series from One Study to Another .......................................................................................... 164
Relocating a Series from One Study to Another ....................................................................................... 165
Merging a Series from Multiple External Archives (E-SIRs)........................................................................ 166
Locating Studies (Storage Management Admin Tool)................................................................................ 167
Viewing Backup Media for Studies (Storage Management Admin Tool) ....................................................... 168
Exiting the Storage Management Admin Tool .......................................................................................... 168
Single Media Archive (SMA) .................................................................................................................. 168
Loading from Single Media Archive (SMA)............................................................................................... 169
viii
Table Of Contents
Email Suite.................................................................................................254
CARESTREAM PACS Email Suite Overview................................................................................................... 254
Email Suite Lifecycle ............................................................................................................................ 254
Email Suite System Components ........................................................................................................... 254
Features and Benefits .......................................................................................................................... 254
Email Suite Lifecycle ............................................................................................................................ 254
MHTML Report Generator ......................................................................................................................... 255
Mail Component ...................................................................................................................................... 255
CD Direct ...................................................................................................261
CARESTREAM PACS CD Direct Suite Overview ............................................................................................. 261
Components ....................................................................................................................................... 261
Features............................................................................................................................................. 261
Setting CD Direct Configuration Parameters ................................................................................................ 262
Production Parameters ......................................................................................................................... 262
Directories Parameters ......................................................................................................................... 262
Labels Parameters ............................................................................................................................... 262
Application Parameters......................................................................................................................... 262
ix
CARESTREAM PACS, Version 11.1 System Administration Printable Help
RIS-PACS Synchronization.........................................................................287
Events in the RIS .................................................................................................................................... 288
Using Manual RIS-Sync ............................................................................................................................ 289
Multiple Studies....................................................................................................................................... 289
RIS-PACS Log ......................................................................................................................................... 289
Pre-Fetch ............................................................................................................................................... 289
JPEG Compression ................................................................................................................................... 291
Study Grouping ....................................................................................................................................... 292
Reverse Study Grouping........................................................................................................................... 292
Icons ..................................................................................................................................................... 292
x
Table Of Contents
Running a System Check from the Online Storage Management Server ...................................................... 296
Performing Routine Maintenance ............................................................................................................... 297
Root Account E-mail (UNIX).................................................................................................................. 298
Backup Verification (UNIX) ................................................................................................................... 299
Verifying the Workflow Manager Daily Backup (UNIX) .................................................................................. 300
Central Configuration Backup (UNIX) ......................................................................................................... 300
Preparing Previously Used Tape............................................................................................................. 300
ORACLE Alert File (UNIX) ..................................................................................................................... 301
Database Fitness Verification (UNIX)...................................................................................................... 302
Online Storage Management Storage Volume Check (UNIX)...................................................................... 303
Checking the Online Storage Management Storage Volume....................................................................... 303
Online Storage Management General (UNIX) .......................................................................................... 304
Viewing System Processes (UNIX) ......................................................................................................... 305
Viewing Daemon Processes....................................................................................................................... 305
Viewing Push and Conference Processes ..................................................................................................... 305
Viewing Currently Running Workflow Manager and Oracle Database Processes ................................................ 305
PreStore Backup Verification (UNIX) ...................................................................................................... 306
Long-Term Storage Manager Storage Volume Check (UNIX) ..................................................................... 307
Long-Term Storage Manager General Fitness Check (UNIX) ...................................................................... 308
Library Hardware Fitness Check (UNIX) .................................................................................................. 309
Moving Audit Logs to Offline Storage (UNIX) ........................................................................................... 310
Exporting Audit Log Files .......................................................................................................................... 310
Clearing the Audit Log.............................................................................................................................. 310
Retrieving Audit Logs ............................................................................................................................... 310
System Monitoring on a Cluster System ..................................................................................................... 311
Using the VCS Cluster Manager to Monitor the Cluster (UNIX) ................................................................... 312
Logging on to the Cluster Manager ........................................................................................................ 312
Cluster Monitor Toolbar and Menus ........................................................................................................ 313
Cluster Monitor Panels ......................................................................................................................... 314
Accessing the Cluster Explorer Window (UNIX)........................................................................................ 315
Cluster Explorer Toolbar (UNIX) ............................................................................................................ 316
Cluster Monitoring Procedures................................................................................................................... 317
Monitoring the Cluster Status (UNIX) ..................................................................................................... 318
Monitoring the Cluster Properties (UNIX) ................................................................................................ 319
Monitoring the Cluster Service Groups (UNIX) ......................................................................................... 320
Monitoring the Cluster Resources (UNIX) ................................................................................................ 321
Monitoring the Cluster Heartbeat (UNIX) ................................................................................................ 322
Viewing Messages from the Log Desk (UNIX) .......................................................................................... 322
Creating Filters for the Log Desk (UNIX)................................................................................................. 322
Switching a Service Group (UNIX) ......................................................................................................... 322
Setting up VCS Event Notification (UNIX) ................................................................................................... 322
Monitoring the Cluster from the Command Line ........................................................................................... 323
Reviewing the VERITAS Cluster Server (VCS) Error Message Logs ............................................................. 323
Engine Log ......................................................................................................................................... 323
Agent Log........................................................................................................................................... 324
VCS Monitoring and Status Commands (UNIX) ........................................................................................ 325
VCS Environmental Variables (UNIX) ..................................................................................................... 326
Common VCS Commands (UNIX) .......................................................................................................... 327
Preserving Cartridges............................................................................................................................... 328
Bar Code Scanner.................................................................................................................................... 328
Programming the Bar Code Scanner ...................................................................................................... 328
Scanning Bar Codes ............................................................................................................................. 329
xi
CARESTREAM PACS, Version 11.1 System Administration Printable Help
xii
Table Of Contents
Index .........................................................................................................361
xiii
Preface
System Administration for
CARESTREAM PACS, Version 11.1
Trademark and Copyright Information
CARESTREAM is a trademark of Carestream Health, Inc.
This document is copyrighted with all rights reserved.
Under the copyright laws, this document may not be copied, in whole or in part, without the written consent of
Carestream Health, Inc. Under the law, copying includes translating into another language or format.
All names or identities used in this document are fictitious.
CAUTION: Federal law restricts this device to sale to, by, or on order of a physician.
The information contained herein is based on the experience and knowledge relating to the subject matter gained by
Carestream Health, Inc. prior to publication. No patent license is granted by this information.
Carestream Health, Inc. reserves the right to change this information without notice and makes no warranty, express
or implied, with respect to this information.
Carestream Health, Inc. shall not be liable for any loss or damage, including consequential or special damages,
resulting from the use of this information, even if loss or damage is caused by Carestream Health’s negligence or
other fault.
FCC Compliance
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15
of the FCC Rules.
These limits are designed to provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and,
if not installed and used in accordance with the instruction manual, may cause harmful interference to radio
communications.
Operation of this equipment in a residential area is likely to cause harmful interference in which case users will be
required to correct the interference at their own expense.
P/N 8J3225 29 June 2010
Carestream Health, Inc.
150 Verona St.
Rochester, NY 14608
USA
14
CARESTREAM PACS, Version 11.1
System Components
CARESTREAM PACS Client Overview
CARESTREAM PACS Workflow Manager Overview
CARESTREAM PACS CD Direct Suite Overview
Info Router Overview
CARESTREAM PACS IS Link Software Overview
15
CARESTREAM PACS Client Overview
The CARESTREAM PACS Client offers radiologists a one-stop system for all their reading and reporting work. It
integrates image review and analysis with third-party dictation and reporting tools to create a friendly, unified
environment for the radiologist. It seamlessly integrates with other CARESTREAM PACS System components to
provide an efficient, automated radiology workflow.
Automatic worklists and hanging protocols streamline the reading tasks and facilitate sharing the workload.
Easy integration with Radiology Information Systems (RIS) enables the distribution of reports into and out of the
radiology department.
3-D image processing applications provide advanced visualization and diagnostic tools.
The CARESTREAM PACS Client offers the following features:
One to four high-resolution, high-brightness, or color monitors
Extensive image review, analysis, and manipulation tools
Personalized display protocols to streamline the workflow
Easy comparison of old and new studies
SUPERPACS Architecture
Global Worklist in Archive Explorer
From the Archive Explorer, you can create a global worklist folder which:
Shows studies from all your sites.
Supports seamless work planning.
Eliminates the need to log in to different servers.
Saves you valuable time.
All studies are synchronized with the original server and are sent to your computer as quickly as possible.
Push to Client
You can read studies faster with Push. The Push capability allows you to transfer studies to your home PC or another
remote location. Another person can push studies for you as needed, increasing the potential for collaboration
between physicians within the enterprise.
You can transfer, monitor, receive, and clear studies from the Archive Explorer.
You can receive studies from the PowerViewer.
Volume Matching
With this new application, you can accurately compare different volumetric studies from any modality.
The Volume Matching application provides:
A set of predefined Display Options.
Image synchronization and manipulation capabilities.
Image fusion.
You can use Volume Matching to:
Swap between primary and secondary images.
Adjust opacity.
Apply a color map to show potential pathology.
PET/CT
The PET/CT application is an image viewer, a registration tool, and an analysis workstation.
The application supports all features required for PET/CT reading, including the ability to:
Fuse together PET and CT images.
View combined current and prior images to see the progress of an area of pathology.
You can use PET/CT to:
Select a pre-defined Display Option to present PET, CT, and Fusion images.
Apply a color map to show potential pathology.
Apply measurements in Standard Uptake Values (SUV).
Apply layouts to synchronize PET and CT data sets.
Register and compare studies.
Enhanced 3D
The enhanced 3-D functions include:
17
Volume Rendering Quality applies a special algorithm for high resolution 3-D images.
Object and Anatomy Removal
Automatic Bone Removal creates a boneless VolR (below the shoulders). A menu provides new correction
tools which you can use to automatically remove additional bone fragments or restore vessel segments.
Automatic Scanner Bed Removal removes the scanner bed from 3-D images (VolR or MIP).
MPR Double Oblique allows you to freely swivel the reference images in the MPR and Cardiac applications,
and view the same anatomical region from three perpendicular orientations.
Aneurysm Measurement enables stent planning, such as a stent for an aortic aneurysm.
DICOM Tunneling
Ability to query the global worklist through a regular DICOM query. The query is tunneled to the SuperPACS Data
Center. This allows 3rd party PACS easy and standard access to the Global Worklist.
See DICOM Tunneling for more information.
Global Priors
This feature enhances local queries for a study with an additional background query to the Data Center for all patient
priors.
This allows you to view the complete patient profile without changing anything in the regular working flow.
See also:
Enhanced Transfer Syntax Configuration
Multiple Patient ID Support (PIX) in Database Administrator Tool
DICOM Tunneling
18
CARESTREAM PACS, Version 11.1
20
CARESTREAM PACS, Version 11.1
Components
The CD Direct Suite comprises the software and hardware, including the CD Manager Server and a CD burner,
necessary to produce CDs that contain image data.
CD Manager Server–the CD Manager Server includes a DICOM server that allows the CD Direct Suite to receive
images through a DICOM copy or move command issued from an external DICOM device. The CD Manager Suite
prepares the content for each media disc (CD or DVD), including reports, DICOM DIR, DICOM Viewer, JPEG Lossy
presentation of the images, and HTML page for quick viewing of the Lossy images.
CD Burner–the CD Direct Suite uses a CD burner (a RIMAGE CD publishing system or another CD burner set up with
your system). If you use a RIMAGE CD publishing system, you can print patient information on the face of the CDs
(see the RIMAGE CD publishing system user guide for information about printing).
Features
Cost-effective
Eliminates the need for handling patient films.
Creates CDs without the fear of ruining image data.
Provides hospitals with the option to give CDs to referring physicians.
Provides referring physicians with the option to give patients CDs or the option to keep CDs for their own
records.
Ability to burn reports to a CD.
Burns CDs in DICOM part 10 format (removable media).
NOTE: The CD Direct Viewer is not intended for primary diagnostic viewing. See the user documentation for the
CARESTREAM PACS CD Direct Suite for more information.
For information about defining the CD Direct Suite configuration parameters, see this topic:
Setting CD Direct Configuration Parameters
21
The Info Router is a CARESTREAM PACS System application that facilitates the flow of data in medical image
management systems. The Info Router enables the remote control of medical data routing through a standard Web
browser. The routing is based on a set of configurable rules defined by the system administrator.
Info Router
The Info Router CARESTREAM PACS Workflow Manager is a configurable, rules-based automatic router, controlling
image flow in a PACS/DICOM environment.
The Info Router performs all the system’s Pre-Fetch requests from the near-line to the online storage, based on
triggers from the CARESTREAM PACS IS Link Software (for example, scheduling data for “r;true” Pre-Fetch) or the
Workflow Manager (for example, a new image received for “r;late” Pre-Fetch or Post-Fetch). Pre-loading allows data
to be pushed from the online storage to the local cache of specific reading stations.
The Info Router rules are configurable based on image headers and can also be set according to a calendar schedule.
Intended Users
The Info Router is intended for use by system administrators as an interface for defining rules that determine when
images are redirected and the destinations to which the images are sent. The system administrator needs only a
network connection to control or configure the Info Router. The images and tools provided by the Info Router are
intended as aids for the competent user only.
22
CARESTREAM PACS, Version 11.1
Concept Description
IS Link Software The IS Link Software is comprised of the Listener process and the Converter
process.
IS Link Database The IS Link Software receives and translates HL-7 data from the RIS or HIS.
The translated data is then stored within the IS Link database.
Listener Process The Listener process waits for HL-7 messages from the RIS and places them
in the message queue without interpretation. This lets the system keep
messages intact for later processing if the Converter process is down for any
reason.
Converter Process The Converter process takes messages from the queue and parses them to
the database tables. When message processing is complete, the Converter
sends the event notifications to the relevant enabled notification queues.
Pre-Fetch Process The CARESTREAM PACS System uses the IS Link Software as a trigger for the
daily Pre-Fetch processes.
NOTE: See Pre-Fetch for a detailed description of the Pre-Fetch process.
RIS-PACS Synchronization The CARESTREAM PACS System uses the IS Link Software as a trigger for the
Process RIS-PACS synchronization process.
NOTE: For more information, see RIS-PACS Synchronization.
Report Presentation The IS Link Software lets the end user, such as a radiologist, view clinical
reports using the PACS Client. The report information is stored in the IS Link
database, and can be retrieved as required.
NOTE: See the user documentation for the CARESTREAM PACS Client for
more information.
23
General System Requirements for Admin Tools
Browser Requirements
NETSCAPE Navigator version 7.0, or 7.1 or later, with JAVA 1.4.2_05 or JAVA 1.6_17
MICROSOFT INTERNET EXPLORER version 6.0, 7.0, 8.0
GOOGLE Chrome 3.0 or 4.0
APPLE SAFARI 1.0 Beta V51 JRE Build 1.4.1-24, or Beta V60 JRE Build 1.4.1-24
To run the Admin Tools on the APPLE MACINTOSH computer, you must obtain the correct version of the JAVA
Runtime Environment (JRE) listed above from Apple.
24
CARESTREAM PACS, Version 11.1
JAVA Plug-In
The current JAVA Runtime Environment (JRE), provided by SUN MICROSYSTEMS INC., supports the JAVA plug-in
required by the client. If the JAVA plug-in is not installed, it may be downloaded from the server. MICROSOFT
INTERNET EXPLORER and NETSCAPE Navigator have different methods to download the JAVA plug-in, as described in
the following sections.
25
Support
For initial support, contact your local system administrator.
Otherwise:
Go to www.carestreamhealth.com.
In the U.S., call 1-800-328-2910.
In countries outside of the U.S., contact your local representative or your usual product supplier.
26
CARESTREAM PACS, Version 11.1
27
Safety
Safety Guidelines
This product was designed and manufactured to ensure maximum safety of operation. It must be operated and
maintained in strict compliance with the safety precautions and operating instructions described.
This product must be installed, maintained and serviced according to Carestream Health, Inc.'s maintenance
procedures by Carestream Health, Inc. personnel, or other qualified maintenance personnel approved in writing
by Carestream Health, Inc..
The system, in whole or in any part, may not be modified in any way without prior written approval from
Carestream Health, Inc.
Unauthorized personnel must be prevented from accessing the system.
If the system does not operate properly, or if it fails to respond to the controls described in this manual, contact
the nearest Carestream Health, Inc. field service office to report the incident and await further instructions.
The images and tools provided by this system are intended as tools for the competent user only. They are
explicitly not to be regarded as a sole incontrovertible basis for clinical diagnoses. Operators are encouraged to
study the literature and reach their own professional conclusions regarding the utility of the system.
The operator must be aware of the product specifications and of the system accuracy and limitations. These
limitations must be considered before making a decision based on quantitative values. When in doubt, consult
the nearest Carestream Health, Inc. field service office.
28
Safety
Hazards
CAUTION: To prevent serious personal injury and damage to the system, strictly follow the instructions
provided in these hazard warnings. Always remain alert when operating this equipment. If a malfunction
occurs, do not use the equipment until qualified personnel correct the problem.
EXPLOSION HAZARD
Do not operate the equipment in the presence of flammable or explosive liquids, vapors or gases. Do not plug in or
turn on the system if hazardous substances are detected in the environment.
If flammable substances are detected after the system has been turned on, do not attempt to turn off the system or
unplug it. Evacuate and ventilate the area before turning off the system.
IMPLOSION HAZARD
Do not subject the system to serious mechanical shocks, as the cathode ray tube (CRT) can explode if struck or
jarred. An explosion may result in flying pieces of glass and coating that can cause serious injury.
OVERHEATING
Do not block the ventilation ports of the electronic equipment. Always maintain at least 6 inches (15 cm) clearance
around the ventilation ports to prevent overheating and damage to the electronic hardware.
EMERGENCIES
Do not use the system if unsafe conditions are known to exist. In the event of hardware failure that could cause
hazardous conditions (smoke, fire, and so on), turn the power OFF and unplug the power cords for both the monitor
and the desktop unit.
ELECTRICAL FIRES
Conductive fluids that seep into the active circuit components of the system may cause short circuits that can result
in an electrical fire. Therefore, do not place fluids or food on any part of the system.
To avoid electrical shocks and burns caused by the use of the wrong type of fire extinguisher, ensure that the fire
extinguisher at the site has been approved for use on electrical fires.
29
IEC 60601-1 Classification
The equipment has the following IEC 60601-1 classifications:
Type of protection against electric shock: Class I equipment.
Degree of protection against electric shock: Type B equipment.
Degree of protection against harmful ingress of water: Ordinary equipment.
30
Safety
Owner Responsibilities
It is the owner's responsibility to maintain a list of personnel authorized to operate this equipment. Before authorizing
any person to operate the system, verify that the person has read and understood the operation manual. The owner
should ensure that only properly trained and fully qualified personnel are authorized to operate this equipment.
Carestream Health, Inc. makes no representation to operate, test, or calibrate the system.
31
User Limitations
The software and documentation described in this manual are furnished under license and nondisclosure agreements.
The software and documentation may be used or copied only in accordance with the terms of these agreements.
No modifications, additions or deletions are allowed on the equipment. No operations can be performed other than
those available through the applications that are described in this online Help. Carestream Health, Inc. shall be
neither liable nor obligated in respect to bodily injury and property damage arising from the use of this software, if
such use is not in strict compliance with the instructions contained in this manual and in all other relevant literature
supplied by Carestream Health, Inc. This is in accordance with the terms of warranty and sale of this product.
32
Safety
33
User Management Admin Tool (Group)
Data Import Tool
The application installs automatically. When installation is complete, the Browse for Folder window appears.
The main window displays the contents of the DICOMDIR grouped by patients.
2. Select a patient (all studies for the patient are selected by default) or select specific studies (for the same patient),
3. Click Import .
34
User Management Admin Tool (Group)
35
Changing Data Import Tool Settings
36
User Management Admin Tool (Group)
NOTE: While performing Patient Matching, use the issuer tag as defined in the study.
De-Identify: De-Identify settings.
General
37
2. Specify the desired settings in each tab.
3. Click .
38
User Management Admin Tool (Group)
Importing Studies
The Data Import Tool has two import options:
Import Studies
De-Identify and Import
To import studies:
4. Click to review the patient and study details before starting the import operation.
1. From the Data Import Tool toolbar, click De-Identify and Import .
The Hide Details window appears showing default values.
39
2. Specify new details.
New IUIDs will be generated for all images (study, series, and image). Other identifiers (referring physician,
operator, institution, station name, etc.) are removed from the images.
3. Click to review the patient and study details before starting the import operation.
40
User Management Admin Tool (Group)
LDAP
LDAP (Lightweight Directory Access Protocol) is an open standard protocol used to access directory servers.
Some sites use a centralized directory service to administer user accounts, groups, and devices. At such sites, the
CARESTREAM PACS System can be configured to rely on the directory service for user identification and authorization.
Although this prevents duplication of effort, the directory service must be highly available; otherwise, users might not
be able to log in.
When a site uses LDAP, the user information stored within LDAP cannot be viewed using the User Management Admin
Tool. In this configuration, the UM controls only parts of the group and system settings.
Allowed applications are also determined only at the group level. In this case, the User Management Admin Tool
functions and the graphical user interface (GUI) appear differently than in systems that are not using LDAP.
For example, in the main User Management Admin window, only groups can be viewed; therefore, only the Groups
tab is displayed.
In systems using LDAP, when adding and editing groups and system settings, the displayed windows are also
condensed versions of the standard windows. The windows are condensed because the user information is defined at
the site within the directory server and only have read access to their information, and can perform any
administrative functions on it. The site controls all the users, and you control only the groups that you define.
NOTE: Contact Customer Service for more information about setting up this optional feature.
Configuring Authentication
When a user logs in to any CARESTREAM PACS product, the login mechanism uses a central user database to perform
authentication of the user.
This authentication is performed using the login name and password assigned to each user by the system
administrator. Users can use this assigned information to log in, change their password, or log in without a password
by answering a question correctly if the password was forgotten. The question and its correct answer must be set up
in advance by an administrator. The user cannot change the question or answer.
The system automatically informs users when their password has expired and prompts them to change it. The length
of time that each password is valid can be configured by the administrator. In addition, the allowed system operations
for each user depend on the configured access rights.
See Access Control Management Tool for more information.
41
Logging in to the CARESTREAM PACS Admin Home Page
Logging in requires both the assigned login name and password in order for the Workflow Manager to identify and
authenticate the user.
NOTE: You must have permission to access User Management in order to log in.
2. Click Administration.
The CARESTREAM PACS Admin home page appears.
42
User Management Admin Tool (Group)
NOTE: When you log in for the first time, you are prompted to change your password.
4. In the Login field, enter your assigned login name.
5. In the Password field, enter your password.
6. Click OK to log in to the selected product.
From a WINDOWS OS
1. Select Start --> All Programs --> Carestream Solutions --> Admin.
The Login window appears.
NOTE: When you log in for the first time, you are prompted to change your password.
2. In the Login field, enter your assigned login name.
3. In the Password field, enter your password.
4. Click OK to log in to the selected product.
NOTE: If a license violation error occurs, the error will be displayed on the admin entry screen. See WFM Licensing
Status Monitoring for more information.
43
Performing User Management Configuration
User Management Admin Overview
The User Management Admin Tool centralizes all the user management functions by providing a central location
where all authorized users of the system are defined. The User Management Admin Tool lets you define permissions
and settings.
The User Management Admin Tool is also integrated with the Access Control Management Tool, which lets you define
each user’s access rights to specific Workflow Manager data at the same time that you initially define them in the
system.
44
Performing User Management Configuration
Users Tab
The Users tab contains list of predefined users. You can add users to the list, edit a user’s settings, or delete a user,
as well as filter and sort the list of users. The Users tab contains the following information for each user:
Column Description
Login Name The user’s assigned login name.
First Name The user’s first name.
Last Name The user’s last name.
Group Name The group to which the user is assigned by the administrator.
E-mail The user’s e-mail address.
Last Login Date The date that the user last logged in to the system. This is useful for determining if
the user is actively using the system or not.
To insert the current date, click Current Date for the relevant field.
Between/and: a date option that filters users by the Last Login Date. In the
Between/and field, enter the to and from dates in DD/MM/YYYY format.
Previous: Enter or select the number of previous days (for example, enter 7 for the
previous week). All users who have logged in during the previous [x] days appear.
Password Age The age of the user’s password (in days). This lets you know when it is time for users
to change their passwords (and remind them if necessary). It is also useful for
determining if a user’s password is too old and should be changed for security
purposes.
From/To: This numeric option filters the users by the password age. Enter the
required range of days (for example, from 20 to 50).
Status The user’s current status, as follows:
Active: The user is currently active and has access to the system.
Suspend: The user has attempted to log in several times using incorrect login
information and is currently blocked from accessing the system. The user remains
locked until the administrator unlocks the user account.
Timeout: The user has attempted to log in several times using incorrect login
information and is currently blocked from accessing the system for the preconfigured
timeout period. The user can either wait for the timeout period to pass or request to
be unlocked by the administrator.
Expired: The user can no longer access the system. This often indicates that the user
was assigned a temporary role, which allowed access to the system for only a limited
time. It is recommended to delete any expired user accounts from the system.
NOTE: The Audit Trail uses the user's login ID when recording actions performed by
this user. When a user account is removed from the system, the system administrator
should keep a record (for at least six years) of the personal identity of the user, so
that historical data in the Audit Trail can be related to that individual.
NOTE: A user can also be manually locked out of the system, if required. For more information, see the User Status
option in Adding New Users.
1. Select the Users tab and click Filter from the User Management toolbar.
45
The Set filters window appears.
NOTE: To clear the filter criteria, click Clear.
2. Enter the desired filter criteria.
3. Click OK.
The list of users is updated automatically and displays only the users that match the filter criteria that you
specified. In addition, the criteria that the list is currently filtered by appear in gray fields above the relevant
column names.
46
Performing User Management Configuration
47
Adding New Users
Adding new users to the system consists of defining the following information for each user:
General details (for example, the name of the group the user is assigned to).
Login details (for example, the user’s login name and password).
Advanced settings (for example, minimum and maximum password length, password expiration criteria, allowed
applications, access control settings).
Profile details are assigned automatically when selecting a group since group selection determines the profile.
External applications, if applicable (for example, access to the voice dictation system and the RIS system).
Edit user permissions (for example, access permissions).
The general and login details are defined for each individual user. The advanced settings are inherited from the group
level unless you modify them on the user level. Any settings modified on the user level override the settings inherited
from the group level.
After a new user has been defined in the system, the user is required to change the temporary password (assigned
initially) at the first login to the system.
1. In the User Management Admin window, select the Users tab.
2. Do one of the following:
48
Performing User Management Configuration
o Group operator: This user has permission only to lock/unlock the users in the group to which the operator
belongs and then to change their passwords. This user can view system, group, and user settings, but
cannot modify them.
NOTE: The Group operator role should not be assigned to users because this role can modify the settings of
the system administrator and group administrator within any group.
o Standard: This user only has permission to use the system to log in to products, and therefore has no
management permissions or administrative role (for example, a radiologist).
o Temporary account: This user only has temporary access to the system and is usually used for an
emergency operator. The allowed time period is configured by the administrator and begins the first time
the temporary user logs in to the system. When the temporary time period passes, the user is assigned an
Expired status.
NOTE: The administrator can modify the validity date of the temporary user’s account.
4. Enter the user’s login details, as follows:
Login Name: The name the user uses to log in to the system.
Password: A temporary password that is valid until the user changes it at the first login.
Confirm Password: Re-enter the user’s temporary password to confirm it.
Recovery Question: (Optional) A question that is asked if the user has forgotten the assigned password. This
information must be obtained from the user.
NOTE: If the user forgets the assigned password and this option has not been defined, the user must request a
new password from the administrator.
Recovery Answer: (Optional) The answer to the recovery question. This information must be obtained from
the user.
User must change password with next login: This option must be selected the first time you enter a user’s
details. This lets you assign a temporary password to the user, and the user must change the password at
the first login.
This option is selected (checked) by default.
5. In the User Status area, select the required status, as follows:
User Active: The user is active (unlocked) and has permission to access and use the system.
User Locked: The user is not active (locked) and does not have permission to access and use the system.
NOTE: This is the manual method for locking or unlocking a user. A locked user is only allowed back into the
system after intervention by a system/group administrator or group operator.
To define advanced options and external applications for this user, see Defining Advanced Settings for Users and
Defining External Applications for Users.
6. Click Add.
The new user is added to the list of users displayed in the User Management Admin Window Users tab.
49
Defining Advanced Settings for Users
You can define advanced settings when you initially add a user to the system or later by editing the user's settings.
User options are the same as for the group level, and values are inherited automatically from the group level. If you
modify a value at the user level, the value overrides the value inherited from the group level. This lets you customize
specific settings for individual users in a group.
1. In the Add User window or the Edit User Settings window, click Advanced Options.
The User Advanced Settings window appears.
2. Change the settings, as required.
The setting definition is determined by its color:
Blue indicates the setting is inherited from the assigned group level settings.
When you modify a value for the user, the field changes to white, which indicates it is now defined at the
user level.
You can also deny an application for a user that is allowed by the user's group. Click to change the field to white
with a checkmark, which indicates the application is allowed both by the group and by the user. Click again to
remove the checkmark. The blank white field indicates that the application is allowed by the group but is denied
for this user.
See Adding New Users for a description of each option.
3. Click OK.
50
Performing User Management Configuration
51
Viewing/Editing User Settings
You can edit user settings to change or update specific settings when specific settings, such as access control
settings, were not defined initially when the user was added to the system.
You can modify the settings for individual users. This can include a user’s general details, login details, and/or
advanced settings that might or might not have been defined previously.
For example, a user might have been added to the system initially without any access control settings being defined.
Editing user settings lets you modify a setting such as this that was not defined previously or to modify a setting that
needs to be changed or updated.
1. In the User Management Admin window, select the Users tab.
2. Do one of the following:
Select the required user in the list and click from the User Management toolbar.
Double-click a user in the list.
From the Tools menu, select Edit Selected.
Right-click a user, then select User Properties.
The Edit User window appears with the same options as the Add User window.
Blue fields indicate that the displayed setting is inherited from the group level settings. When you modify a value
for the specific user, the field changes to white, indicating that it is now defined on the user level for that specific
user.
3. View/edit the user settings, as required.
See Adding New Users for a description of each option.
NOTE: Selecting the applications settings options lets you configure the relevant settings for those applications on the
user level.
4. Click OK.
52
Performing User Management Configuration
Deleting a User
You can delete users from the system only if your assigned role gives you permission to do so. Deleting users
depends on your requirements. For example, it is recommended to delete users who were assigned a temporary role
and now have an Expired status and no longer need to be in the system.
NOTE: The Audit Trail uses the user's login ID when recording actions performed by this user. When a user account is
removed from the system, the SA should keep a record (for at least 6 years) of the personal identity of the user, so
that historical data in the Audit Trail can be related to that individual.
1. In the User Management Admin window, select the Users tab.
2. Do one of the following:
Select a user name from the relevant list and click from the User Management toolbar.
From the Tools menu, select Delete Selected.
Right-click the required user and select Delete Selected Users.
The Delete Selected User window appears.
3. Click OK.
The user is removed from the system and is no longer displayed.
53
User Management Admin Tool (Contacts)
The Contacts tab contains a list of contact details stored in the User Management Repository.
Contacts are different from the standard system users since the system does not manage their credentials and
permissions (i.e., they cannot log-in to the system). The Contacts tab is also enabled in the LDAP repository.
The following information is kept for each contact:
54
Performing User Management Configuration
Script Location
UNIX: /usr/algotec/um/scripts/importFromCsv.scr
WINDOWS: D:\Program Files\Carestream Solutions\System5\scripts\importFromCsv.bat
Usage
Use a single script named importFromCsv with the following flags:
importFromCsv <-addcontacts | -addusers> <-user> <-pass> <-inputfile > [-outputdir] [-header]
addcontacts: The CSV file contains contacts.
addusers: The CSV file contains users.
user: User name to log into the system.
pass: Password to log into the system.
inputfile: CSV file that contains the data.
outputdir: where to place logs of operation. Optional when not used. No logs will be written to the local log.
header: Used when using –addcontacts flag. Indicates that the first line contains a header.
55
Access Control
56
Performing User Management Configuration
7. In the Value field, enter the predefined value for the selected tag.
NOTE: You can add more than one restriction by inserting a backslash (\) between each specific value. For example,
1\2 allows the user to access studies from site 1 or 2 only.
8. Click OK.
The new access control settings appear in the Tag/Value pane.
9. If required, repeat steps 5 to 8 to add additional restrictions to the same user.
57
See these topics:
Updating a Restriction
Removing a Restriction
Access Control Management Tool
58
Performing User Management Configuration
Updating a Restriction
You can update existing restrictions. For example, you can change the type of data that is limited or you can add
additional values to an existing restriction tag.
1. Open the Access Control window by selecting the required group to which you want to add a restriction.
The selected group or node is displayed in the Access Control pane.
2. Do one of the following:
59
Removing a Restriction
You can remove a restriction from a group to enable previously limited CARESTREAM PACS Workflow Manager data to
be accessed.
1. Open the Access Control window by selecting the required group.
The selected group is displayed in the Access Control pane.
2. Do one of the following:
60
Security Manager
The Security Manager is a system-wide application that controls the various permissions, access restrictions, and
other permission-based features of all products in the CARESTREAM PACS System, including configuration and
administration tools. The system is built using the principles described below.
Group A group is an entity containing users and is attached to a specific profile. A group contains a
set of parameters such as Display Protocols in CARESTREAM PACS Client or specific security
settings, etc.
Profile A profile describes the functions a user has after logging in to the CARESTREAM PACS Client.
A profile contains a list of features (similar to licensing). Sites cannot edit the contents of a
profile. One group can only belong to one profile. However, several different groups can
belong to the same profile.
For example: Group A belongs to one specific profile (Profile A). Group B also belongs to one
specific profile (Profile A). Users of both groups have the same set of basic features (and user
interface) when they log on to the system. However, each group has its own set of
permissions.
A feature is a licensed permission, is not configurable, and represents a function in the
system.
Permissions The permissions to perform certain operations or view certain data are controlled by the
Security Manager and managed by the UM. Permissions are attached by default to a specific
group. Permissions can also be configured on a user level. Each group has a specific set of
permissions with a 1:1 ratio (one set of permissions is available for one group and vice
versa).
The same theory applies to users. For example, a user belonging to a group automatically
inherits the group’s permissions. If a specific permission is added or removed from the user,
the user has a specific set of permissions.
You can configure permissions on a system, group, or user level. Each level overrides the
preceding level.
Certain permissions are dependent upon features. If a user does not have the feature in the
profile to which the user is attached, the permission is not available to the user.
The permissions mechanism must read the profile content and allow configuring permissions
for the relevant features in the profile and changing the permissions. Features that are not in
a specific profile do not appear in the User Management at all.
Permissions Certain features of the system are included as part of the profile definition and require
and Profiles permission controls. The permissions mechanism allows configuring or changing permissions
for the relevant features in the profile. Features that are not in a specific profile do not
appear in the Security Manager. Most sites have more than one profile, so the permissions
mechanism must be able to read the profile that is relevant for a specific user or group.
61
Applicable Permissions
The following permissions are controlled through the Security Manager.
Setting Description
Update Data Permission to edit patient and study details. Should apply to any update of
patient and study details, both in the Archive Explorer (editable fields) and in
the Administrator tool (update, merge/split, RIS Sync, etc.).
Lets the user delete images and reports. Should apply to deletion being
performed from the CARESTREAM PACS Client or from the Administrator tool.
Access to Foreign Permission to access, save, copy, and/or delete images from any of the remote
Archives servers that are configured.
(View/Write/Delete)
Print Images Permission to print images to a network printer or a DICOM printer.
URL and Action Button Permission to change a study after the URL activation was invoked (launch
Permissions Archive Explorer and select a different study).
NOTE: The permission to allow URL activation is included under the Application
Access Permissions.
Permission to activate a specific Action button that is configured on site (for
example, the ORTHOVIEW action button triggering the integration with the
ORTHOVIEW application).
View Reports Permission to view reports. If this permission is not given, the R or O icons in
the Patient Mini-Archive are disabled and the Reports button in the Archive
Explorer or the Viewer is disabled.
By default, this permission is applied to any user defined in the Radiologists
group.
Reading Permissions This permission allows a user/group reading permissions (the ability to move
studies from one status to another within the system when clicking on Done),
together with the ability to lock a study.
If permission is not granted, the user returns to the Archive Explorer when
clicking Done and does not receive the Done dialog box.
By default, this permission is applied to any user defined in the Radiologists
group. If this permission is given, the relevant workflow is configured for the
particular group/user.
Mark Key Images Permission to mark images as key images. Only users with reading permissions
can be assigned with the Mark Key Images permission.
By default, this permission is applied to any user defined in the Radiologists
group.
NOTE: The permission to mark key images does not necessarily mean that the
user has Save As permissions. Users who do not have permission to Save
62
Security Manager
Dictate Report Permission to dictate a report. Only users with reading permissions can be
assigned the Dictate Report Permission.
By default, this permission is applied to any user that is defined in the
Radiologists group.
Save Reports Permission to save reports that have been automatically generated in
CARESTREAM PACS applications such as Calcium Scoring and Vessel Analysis.
Only users with reading permissions can be assigned the Save Reports
permission.
By default, this permission is applied to any user defined in the Radiologists
group.
Create Sticky Notes Levels of permission for Sticky Notes:
Only view Sticky Notes
View and add Sticky Notes (no editing)
Edit and delete user's own Sticky Notes
Edit and delete other users’ Sticky Notes
Teaching Files Levels of permission for Teaching Files:
View a Teaching File
View and insert a study into the Teaching File
Change the content of a Teaching File (view/add/edit)
View/add/edit/delete a teaching file
Edit the Teaching File form
Access Control Rules Similar to the Access Control rules currently in existence in the CARESTREAM
PACS.
Query Permissions controls whether a user or group can query certain locations.
This capability is in the general Security Manager application and can be applied
at group level (the permission to add/edit/delete users in your group or at
system level).
Resetting Users' Permission to reset user passwords. This capability is inherent today based on
Permissions the role of the user such as System Operator or Group Operator.
This capability is in the general Security Manager application and can be applied
at group level (the permission to reset users’ passwords in your group or at
system level).
Editing Users' Permission to edit permissions. This capability is inherent based on the role of
Permissions the user (System Operator or Group Operator).
This capability is in the general Security Manager application can be applied at
group level (the permission to grant users’ permission in your group or at
system level).
63
Security Manager Permissions Settings
The system is installed with several default permission settings.
Setting Description
System These settings are automatically applied to any user defined in the Administrators
Administrator group.
Radiologist These settings are automatically applied to any user defined in the Radiologists group.
Web These settings are automatically applied to any user defined in the MS_Users group.
Mammography If you are defined as a Group Administrator, the user receives the relevant settings for
the group the user belongs to and also receives an additional permission to add, edit,
and delete users from that group.
If a new group is defined in the system, it inherits the System Level Permission
Settings. Alternatively, if a new group is created by copying an existing group, it
inherits the permission settings of the original group.
If a new user is defined in the system, you inherit the permission settings of the group
to which the new user belongs.
Temporary User These settings are automatically applied to any user defined as a temporary user in
the system.
If you are defined as a Group Administrator, the user receives the relevant settings for
the group the user belongs to and also receives an additional permission to add, edit,
and delete users from that group.
If you are defined as a Group Operator, you receive the relevant settings for the group
that the user belongs to and also receive an additional permission to reset the
password of a user.
If you are defined as a Service User, you receive the permission settings of the
administrators group.
If a new group is defined in the system, it inherits the System Level Permission
Settings. Alternatively, if a new group is created by copying an existing group, it
inherits the permission settings of the original group.
If a new user is defined in the system, you inherit the permission settings of the group
to which the new user belongs.
64
Security Manager
65
Performing Group Management Configuration
Group Management Overview
The User Management Admin Tool centralizes all the user management functions by providing a central location
where all authorized users of the system are defined. The User Management Admin Tool lets you define permissions
and settings on the user, group, and system levels.
You can define logical groups for the users and define basic group and user details, including their central login
criteria and what products they can access. You can also edit the system default settings (if you have permission to
do so) to change the settings for all groups and users.
The User Management Admin Tool is also integrated with the Access Control Management Tool, which enable you to
define each user’s access rights to specific Workflow Manager data at the same time that you initially define them in
the system.
For information about individual user configuration, view the topics listed under User Administration and Access
Control.
66
Performing Group Management Configuration
Users Tab
The Users Tab contains a list of users defined in the system. You can add users to the list, edit user details or delete a
user, as well as filter and sort the list of users.
Groups Tab
The Groups tab contains a list of predefined groups. You can add groups to the list, edit a group’s settings, or delete a
group, as well as filter and sort the list of groups.
Profiles Tab
The Profiles Tabs contains a list of profiles configured in the system. By clicking on each profile, the contents of each
profile and the features allowed by that profile are displayed.
67
Viewing/Editing System Settings (Group)
The default system settings that were defined during system installation can be modified, depending on your
requirements. The system settings apply initially to all groups and users in the system.
For example, whether you leave the system defaults or modify the settings, the system settings are automatically
inherited from the system level by the groups and users that you add to the system. When adding groups and users,
you have the option of modifying the inherited system level settings at the group level or the user level, which
overrides the inherited system level settings.
NOTE: The Edit System Settings window appears differently depending on whether your system is using LDAP or not.
The options in the Edit System Settings window (with LDAP) are the same as those in the Add Group window except
for the Allowed Applications options, which are not relevant at the system level.
68
Performing Group Management Configuration
69
Central Configuration Editor
The Central Configuration Editor is a simple repository enabling the user to save permanent application information in
the CARESTREAM product environment. The Central Configuration Editor is structured as a hierarchical tree, with
multiple levels of branches and keys (folders).
The left pane of the screen displays the configuration tree. The tree can be expanded to show all branches, folders,
and subfolders. This pane is used to navigate to the required key.
Keys are managed in this pane using the configuration editor tree. Right-click on the left pane to open a menu with
these options:
Option Description
Add Key Adds a new key to the tree.
Remove Key Removes an existing key.
Cut Cuts a key to somewhere else.
Copy Copies the key to somewhere else.
Paste Pastes the key to somewhere else.
Rename Renames an existing key.
Search Searches for a string under a particular node.
Search Next Searches for the next node.
Import Imports a key from another place.
Export Exports a key to another place.
Dump to XML File Dumps a string in an XML file.
Copy Path to Clipboard Copies a path to the clipboard to paste somewhere else.
The right pane displays the parameters and values for the selected folder in the configuration editor tree. Use this
pane to view specific parameters and values, as well as to modify configurations.
In this pane, parameters can be managed and values assigned to a selected folder. Right-click in this pane to access
these options:
Option Description
Add Value Adds a new value.
Remove Deletes an existing value.
Copy Copies a value to somewhere else.
Cut Cuts the value to somewhere else.
Paste Pastes the key to somewhere else.
Edit Value Lets you edit the value.
Select All Selects all values.
Copy Path to Clipboard Copies a value to the clipboard to paste somewhere else.
IMPORTANT: Select File --> Save to save your changes. Otherwise, changes will be lost.
CAUTION: Exercise caution when changing the Central Configuration. Changing the wrong entries or
making an incorrect entry for a setting can introduce an error that prevents the entire system from
starting or working properly. Contact Systems personnel for assistance before making any changes.
70
Performing Group Management Configuration
71
Selecting LDAP as the UM Repository
When LDAP is configured as the UM repository, all user information is stored in the Directory Server. The User
Management application supports two types of commercial LDAP servers: MICROSOFT Active Directory and SUN One
Directory Server 5.2 (iPlanet). These products have different schema and usually support different sets of controls
and attributes.
1. Open the User Management Administration tool and click LDAP settings.
The LDAP Settings window appears.
2. Add the server name to the User Directory Hosts list. You can add several hosts to the list and change the order of
the host names. In case of failure to connect to the first host (On Top), a second attempt is made to the following
hosts in order.
3. Set the Port in the User Directory Port field.
There usually are different ports for secured and non-secured connections.
4. If the LDAP connection is to be secured (SSL), check the Secured LDAP Connection box.
5. Enter the Base DN of the LDAP Server users account.
6. Enter the URLs for changing user password in the Change/Forgot password URL fields.
If the password is forgotten, the User Management application opens these URLs when you click the Login dialog
box button.
7. Click on the Credentials tab.
8. Set the Bind user name and password to be used for the LDAP pre-authentication stage (bind).
This user setting is used for initial authentication to transform the User Login Name into an LDAP Distinguished
Name (DN).
9. If an Anonymous bind is to be performed, check the Anonymous Bind Checkbox
10. Click the Prefixes tab.
11. Attach a Group prefix to the Group name in the Group Prefixes list.
Any group with a group prefix found in the LDAP server should appear without a prefix in the User Management
group list. It should also exist in the User Management application.
12. Attach a Role prefix in the Role Prefixes list.
13. Click the Advanced Settings tab.
14. Set the search method to Whole subtree starting with Base DN.
15. Set the objectclass filter to objectclass=*
16. Set the unique user identifier attribute name, for Active Directory set sAMAccountName.
17. Check the Build user DN dynamically box.
18. Click the Authentication Result tab.
19. Set the page size limit for the LDAP Query.
The paged query divides the result into pages in the specified size.
20. Select Paging Control (LDAP Query-type field).
For Active Directory, select Paged Query or No Paging.
21. Select the Error handling method
For Active Directory, select Active Directory Error Codes only.
72
Performing Group Management Configuration
73
Configuring the Change/Set Forgotten Password URL
There are two configurable elements:
the protocol
the IP
You can set the protocol to either http or https. If the value in the URL is http, the protocol depends on that of the
user. If the user enters using https, it remains secured.
You can configure the IP element to a specific IP value, for example, 199.203.80.132 or $IP$. If the IP is static, the
server name used is irrelevant because the change password URL opens with the predefined IP address. If the value is
$IP$, the IP value is taken from the URL entered by the user.
1. In the Central Configuration, select imaginet --> system --> applications --> securitymanager --> change
password.
2. For value set:, enter http://$IP$/um/ChangePassword.jsp
3. For Protocol (http/https):, enter // [<199.203.80.123> | $IP$] /um/changePassword.jsp
74
Performing Group Management Configuration
75
Adding New Groups
Adding new groups consists of defining the following information for each group:
The group name
The group profile
Password settings (e.g., minimum and maximum password length)
General settings (e.g., password expiration and temporary account criteria)
Security settings (e.g., allowed number of password failures and whether to lock or suspend users when the
allowed number is exceeded)
Application settings (the access control settings on the group level for users in the specific group)
Group permissions
All group details are automatically inherited from the system settings unless you modify them on the group level
during definition. In this case, any settings modified on the group level override the settings inherited from the
system level.
NOTE: The Add Group window appears differently depending on whether or not your system is using LDAP.
NOTE: Selecting these options lets you configure the relevant settings for those applications on the group level.
9. Edit group permissions.
10. Click Add.
The new group is added to the list of groups displayed in the User Management Admin window Groups tab.
77
Viewing/Editing Group Settings
Edit group settings when specific settings need to be changed or updated, or when specific settings were not defined
initially when the group was added to the system, such as access control settings.
NOTE: You must have the appropriate permission in order for you to perform editing.
You can modify the settings (permissions) for an entire group of users. Groups automatically inherit the system
default settings when they are defined initially unless you modify them. This let you modify only the settings that you
want to change on the group level and leave the ones inherited from the system level as they are defined.
The Edit Group Settings window also contains links to the Web Client and access control settings. You can select these
options to configure the relevant settings on the group level for all users belonging to the current group. See Access
Control Management Tool for more information.
The Edit Group Settings window appears differently depending on whether or not your system is using LDAP.
78
Performing Group Management Configuration
Select the required group in the list and click Edit Selected from the User Management toolbar.
Double-click the required group in the list.
From the Tools menu, select Edit Selected.
Right-click, then select Group Properties.
The Edit Group Settings window appears.
NOTE: Yellow fields indicate that the displayed setting is inherited from the system level settings. When you modify a
value for the specific group, the field changes to white, indicating that it is now defined on the group level for that
specific group.
To cancel any changes made to the group level settings, click Restore System Defaults. The system settings are
restored, and all the fields are displayed in blue again.
3. View/edit the group settings, as required.
See Defining New Groups for a description of each option.
4. Click OK.
79
Viewing/Editing Group Settings (with LDAP)
1. In the User Management Admin window, select the Groups tab.
2. Do one of the following:
Select the required group in the list and click Edit Selected from the User Management toolbar.
Double-click the required group in the list.
From the Tools menu, select Edit Selected.
Right-click, then select Group Properties.
A condensed version of the Edit Group Settings window appears.
3. View/edit the group settings, as required.
See Defining New Groups for a description of each option.
4. Click OK.
80
Performing Group Management Configuration
Deleting a Group
You can delete groups only if you have permission to do so. Each user is assigned a role in the system: System
Administrator, Group administrator, and Group operator. The System Administrator role has permission for adding,
editing, and deleting groups and users.
1. In the User Management Admin window, select the Groups tab.
2. Do one of the following:
Select a group name from the relevant list and click Delete Selected from the User Management
toolbar.
From the Tools menu, select Delete Selected.
Right-click the required group/user and select Delete Selected Groups.
The Delete Selected Group window appears.
3. Click OK.
The group is removed from the system.
81
Access Control Management Tool
The Access Control Management Tool lets you set restrictions to control the type of Workflow Manager data that users
can access. When a user logs in and requests data, the system automatically checks for restrictions.
User—according to the user’s personal access level. See Adding Restrictions to Users and Groups.
Group—according to the group to which the user belongs. See Adding Restrictions to Users and Groups.
You configure access control by opening the Access Control Management tool and adding, updating, and removing
restrictions, as required. This lets you determine the exact data that each user can access by setting restrictions that
place limitations on the data that the specific user, group, or node is authorized to access.
Examples
No assigned access level means that the user has full access to all Workflow Manager data. All users must be
assigned to a group, so if neither the individual user nor the group has been assigned an access level, all users
in the group have full access.
A group restriction specifying a MODALITY DICOM tag and an MR value means that users in this group can only
view MR images.
82
Performing Group Management Configuration
83
Opening the Access Control Management Tool Users Tab
1. In the User Management Admin window, select the Users tab.
2. Do one of the following:
Select the required user in the list and click Edit Selected .
Double-click the required user in the list.
From the Tools menu, select Edit Selected.
Right-click and select User Properties.
The Edit User Settings window appears.
3. Click Advanced Options.
4. Click Access Control.
The Access Control window appears. The Access Control pane on the left displays a view-only hierarchical tree that
shows the currently selected user, group, or node.
The Tag/Value pane on the right lets you add, update, or remove a restriction for the selected user, group or
node. If the selected user, group, or node has existing restrictions, they are displayed in this pane.
NOTE: When accessing the Access Control window from the User Management Admin Tool, the information displayed
in the Access Control pane on the left depends on the access level from which it was opened (user or group).
5. Add, update, or remove restrictions for the selected user.
84
Performing Group Management Configuration
Select the required user in the list and click Edit Selected .
Double-click the required user in the list.
From the Tools menu, select Edit Selected.
Right-click and select Group Properties.
The Edit Group Settings window appears.
3. Click Access Control.
The Access Control window appears. The Access Control pane on the left displays a view-only hierarchical tree that
shows the currently selected user, group, or node.
The Tag/Value pane on the right lets you add, update, or remove a restriction for the selected user, group or
node. If the selected user, group, or node has existing restrictions, they are displayed in this pane.
NOTE: When accessing the Access Control window from the User Management Admin Tool, the information displayed
in the Access Control pane on the left depends on the access level from which it was opened (user or group).
4. Add, update, or remove restrictions for the selected group.
NOTE: All users must be assigned to a group. Users with no configured restrictions on the user or group levels are
allowed full access to all Workflow Manager data.
85
Adding Restrictions to Users and Groups
Restrictions at the user level are configured by selecting one user at a time and adding one or multiple restrictions, as
required.
Each user must be assigned to a group. Restrictions at the group level are configured for one group at a time. The
restrictions you configure for a group are applicable to all users in the group.
For example, you can define a CT group and an MRI group and use the procedure below to configure a restriction for
each group. This limits the groups to view only CT images or only MRI images. You can then assign a specific user to
the required group without having to configure specific restrictions for each individual user.
1. Click Access Control on the Edit System Settings window.
7. In the Value field, enter the predefined value for the selected tag.
NOTE: You can add more than one restriction by inserting a backslash (\) between each specific value. For example,
1\2 allows the user to access studies from site 1 or 2 only.
8. Click OK.
The new access control settings appear in the Tag/Value pane.
9. If required, repeat steps 5 to 8 to add additional restrictions to the same user.
86
Performing Group Management Configuration
Updating a Restriction
You can update existing restrictions. For example, you can change the type of data that is limited or you can add
additional values to an existing restriction tag.
1. Open the Access Control window by selecting the required group to which you want to add a restriction.
The selected group or node is displayed in the Access Control pane.
2. Do one of the following:
87
Removing a Restriction
You can remove a restriction from a group to enable previously limited CARESTREAM PACS Workflow Manager data to
be accessed.
1. Open the Access Control window by selecting the required group.
The selected group is displayed in the Access Control pane.
2. Do one of the following:
88
CARESTREAM PACS Info Router
The Info Router is a CARESTREAM PACS System application that facilitates the flow of data in medical image
management systems. The Info Router enables the remote control of medical data routing through a standard Web
browser. The routing is based on a set of configurable rules defined by the system administrator.
Info Router
The Info Router CARESTREAM PACS Workflow Manager is a configurable, rules-based automatic router, controlling
image flow in a PACS/DICOM environment.
The Info Router performs all the system’s Pre-Fetch requests from the near-line to the online storage, based on
triggers from the CARESTREAM PACS IS Link Software (for example, scheduling data for “r;true” Pre-Fetch) or the
Workflow Manager (for example, a new image received for “r;late” Pre-Fetch or Post-Fetch). Pre-loading allows data
to be pushed from the online storage to the local cache of specific reading stations.
The Info Router rules are configurable based on image headers and can also be set according to a calendar schedule.
Intended Users
The Info Router is intended for use by system administrators as an interface for defining rules that determine when
images are redirected and the destinations to which the images are sent. The system administrator needs only a
network connection to control or configure the Info Router. The images and tools provided by the Info Router are
intended as aids for the competent user only.
89
Using the Info Router
The Info Router configuration is the interface through which rules are controlled. The Info Router client is the
interface through which commands are monitored and controlled. Rules determine how images and other data are
routed within the CARESTREAM PACS System and under what conditions the images are sent.
The Info Router client automatically synchronizes with the server, enabling you to create and update rules, as well as
view existing rules and their related data. You can also create aliases for items and/or groups of items and apply
conditions to them.
Opening the Info Router
Info Router Client Window
Info Router Toolbar
Info Router Menu Bar
Rules Configuration Window
90
CARESTREAM PACS Info Router
2. Click Administration.
The CARESTREAM PACS Admin home page appears.
From a WINDOWS OS
91
1. Select Start --> All Programs --> Carestream Solutions --> Admin --> System Monitoring.
The Login window appears.
NOTE: When you log in for the first time, you are prompted to change your password.
2. In the Login field, enter your assigned login name.
3. In the Password field, enter your assigned password.
4. Click OK to log in to the selected product.
92
CARESTREAM PACS Info Router
See these topics for information about the Info Router Client window elements:
Info Router Toolbar
Info Router Menu Bar
Rules Configuration Screen
Available Rules
Custom Function
General Parameters
93
CARESTREAM PACS Info Router Configuration Toolbar
The CARESTREAM PACS Info Router toolbar enables you to perform various common operations such as defining rules
and aliases, filtering commands, and so on.
Refresh Lets you manually refresh the data that appears in the Info Router Client
window tabs.
When you use this option, the currently displayed tab data is refreshed.
When you select another tab, the Info Router also automatically refreshes
the data in that tab.
Save Lets you save changes.
Alias
Insert Aliasing Lets you define an alternate name for an item or a group of items.
94
CARESTREAM PACS Info Router
Refresh Lets you manually refresh the data that appears in the Info
Router Client window tabs.
Commands Filter Lets you filter the commands that appear in the Monitor tab,
as described in Filtering Commands.
You should filter periodically to avoid displaying an excessive
number of commands.
Select All Selects all items in the current tab.
95
CARESTREAM PACS Info Router Client Menu Bar
Menu Option Description
File Exit Exits the Info Router client application.
Edit Retry Retries the execution of the command.
Hold Holds the execution of the command.
Release Releases the Hold option and executes the command.
Priority Changes the priority of the command.
Delete Deletes the selected item(s).
Select All Selects all items in the current tab.
Select None Deselects all currently selected items.
View Refresh Lets you manually refresh the data that appears in the Info Router Client
window tabs.
Auto Refresh Refreshes the displayed data automatically according to the values set in
the AutoRefresh Time Interval Setter window.
A checkmark next to the Auto Refresh option indicates that the option is
enabled.
Filter See Filtering Commands.
Commands Lets you filter or display commands as follows:
Filter: Lets you filter the commands that appear in the Monitor tab,
as described in Filtering Commands. It is recommended that you
filter periodically to avoid displaying an excessive number of
commands.
Last Hour: Shows all commands initiated in the last hour.
Last Day: Shows all commands initiated in the last day.
Last 2 Days: Shows all commands initiated in the last two days.
Last Week: Shows all commands initiated in the last week.
In Progress: Shows all commands that have a Running or Waiting
status.
Failed: Shows all commands that failed.
Succeeded: Shows all commands that succeeded.
Rules Displays the list of rules as they appear in the System Configuration.
Tools Auto Refresh Intervals Auto Refresh Intervals lets you configure the automatic refresh intervals
for the data that appear in each Info Router Client window tab (in
seconds, minutes, or hours).
Help Help Accesses the Info Router online help.
About Info Router Shows information about the current Info Router software version
number.
96
CARESTREAM PACS Info Router
Monitoring Tab
The Monitoring tab is comprised of the Command List area and the Command Log Information area. In addition, two
panes at the top of the screen display the Commands Execution Status both with and without filters.
These panes display the status as shortcuts. To view information about each status, click the command status
shortcut. The information corresponding to the shortcut appears.
Screen splitter arrows between the areas enable you to resize the Command Log Information area, or to click and
drag it to a new position.
The number of commands displayed in the Monitoring tab can be controlled by applying filters, as described in
Filtering Commands.
Option Description
ID The unique identification number for each command, according to the order in
which the commands were created.
When a command is deleted, the remaining commands retain their original
identification numbers.
Type The type of the command.
Patient Name The name of the patient to whom the image or study relates.
Source The name of the source device from which the image or study is being copied.
Destination The name of the destination device to which the image or study is being copied.
Date Completed The date and time when the command succeeded or failed.
Percent Completed The percentage of completion of the command currently running.
The display resets to 0% each time there is a retry.
97
Filtering Commands
You can filter the commands that are displayed in the Command List area of the Monitor tab. You can also view the
number of commands that appear in the Command List area when the filters are applied.
You should apply the appropriate command filters to reduce the number of commands that appear in the Command
List area of the Monitor tab. When fewer commands appear, the retrieval time is reduced.
1. Do one of the following:
Option Description
command ID between The ID of the command from which to start the display. If you leave this field
blank, all commands created up to the selected command in the To ID field are
displayed.
Command Type The type of command (for example, Send to mail or Copy).
Originator Rule ID The rule that generated the command.
Patient Name The name of the patient you want to display. Enter a partial name to display all
the patient names that begin with that string of letters.
Source The source of the event (for example, Copy from the Online Storage
Management).
Destination The destination of the event (for example, Copy to Diagnostic Workstation).
Number of commands The number of commands that are displayed, if the filters are applied. This field
is read-only.
NOTE: Any change to parameters does NOT automatically update the counter.
Click the Refresh Count button to update the number of commands. The button
is disabled if there are no changes.
3. Click OK to apply the selected filters.
4. Close the Commands Filter window.
The information in the Commands List area is updated and displayed according to the criteria that you defined.
98
CARESTREAM PACS Info Router
UNIX System
1. In your browser, enter the address (URL) of the server and press Enter.
You are connected to the local server. The home page appears.
2. Click Administration.
The PACS Admin home page appears.
3. Select System Monitor --> Processes.
The Enter Network Password window appears.
4. Enter your network User Name and Password, then click OK.
The System Monitoring window appears.
5. Click Info Router Processes.
The Info Router Processes window appears.
6. Click Start or Stop, as required.
WINDOWS OS System
1. Select Start --> Programs --> Carestream Solutions--> Admin --> System Monitor --> Processes.
The LOGIN window appears.
NOTE: When you log in for the first time, you are prompted to change your password.
2. Enter your login name and password, then click OK.
99
CARESTREAM PACS IS Link Software
IMS Document Agent (XDS/XDS-I Document Source)
IMS Document Agent is a document publisher and store agent. It is responsible for sending documents to a Document
Repository/PACS.
The Document Agent can be used in two environments:
PACS: Stores documents in the PACS. Each document is stored as a new study for a patient (for example, two
documents are stored as two studies).
XDS: (See IHE XDS Profile for more details) Supplies metadata to the Document Repository for subsequent
registration of the documents within the Document Registry.
By default, the IMS Document Agent sends the documents to the IMS Document Repository which stores them in the
IMS Archive. Documents can be retrieved in two ways: through the PACS Client or through XDS Document Retrieve
(XDS Consumer).
100
CARESTREAM PACS IS Link Software
101
Configuring the IMS Document Agent
The IMS Document Agent configuration is found in the central configuration under the subtree
imaginet\system\applications\medilink\xds\source
Option Description
xds_repository_uri The URI(URL) of the Document Repository, documents is stored to this repository
(Using XDS Provide and Register transaction). To use SSL communication, configure
https protocol, appropriate certificates must be configured to establish HTTPS
communication.
xds_disable_pix_query If false, the document agent performs pix query against the pix manager to obtain
affinity domain patient identifier (Enterprise PID) which is used to publish a
document.
xds_pix_manager_ip The PIX Manager IP address.
xds_pix_manager_port The PIX Manager port number.
Submission Details
Name: A descriptive name of the submission, when document is stored it will be used as content for DICOM
STUDY_DESCRIPTION.
Reference: By default, the value of this field is mapped to TAMAR_MISC_STRING_2.
Date Time: By default, the value is taken from the document creation date time. You can change it by setting a
new date time.
Documents Location: Click Add Document to add documents to be stored.
102
CARESTREAM PACS IS Link Software
Properties
disable_register_document
This field specifies if to Register the incoming documents in the Document Registry.
------------------------START VALUE-----------------------
PATH: imaginet\system\applications\medilink\xds\repository\settings\disable_register_document
VALUE: false
------------------------END VALUE-----------------------
\xds_registry_uri
The URL of the Document Registry
------------------------START VALUE-----------------------
PATH: imaginet\system\applications\medilink\xds\repository\settings\xds_registry_uri
VALUE: http://129.6.24.109:9080/axis2/services/xdsregistrya
------------------------END VALUE-----------------------
repository_dump_files_location_or_disabled
If set with directory location the repository will dump temporary metadata files for diagnostic purpose.
------------------------START VALUE-----------------------
PATH: imaginet\system\applications\medilink\xds\repository\settings\repository_dump_files_location_or_disabled
VALUE: /usr/algotec/medilink/resources/xds/doc_repository/output/
------------------------END VALUE-----------------------
xds_repository_base_document_uri
This base uri is used to update the Document Registry about each document retrieve URL.
------------------------START VALUE-----------------------
PATH: imaginet\system\applications\medilink\xds\repository\settings\xds_repository_base_document_uri
VALUE: http://10.2.0.166/um/webapp_services/xds-rep-load?objectUID=%
------------------------END VALUE-----------------------
103
CARESTREAM PACS IS Link Software Overview
CARESTREAM PACS IS Link Software is a configurable HL-7 interface engine that provides seamless integration of
PACS with a Hospital Information System (HIS) and/or a Radiology Information System (RIS).
The IS Link Software functions as an “intelligence agent” for the PACS, collecting relevant information from the
HIS/RIS and passing it on to the PACS. It offers these features:
Tight data synchronization between the HIS/RIS and the PACS.
Full support for IHE Scheduled Workflow and Patient Information Reconciliation integration profiles, including
patient and study-data synchronization with the RIS database.
The IS Link Software provides important features and benefits, including:
Comprehensive integration and connectivity to HIS/RIS.
Notification to CARESTREAM PACS products about events happening on the RIS.
A computerized data repository for textual clinical results, patients, visits, and order information.
Concept Description
IS Link Software The IS Link Software is comprised of the Listener process and the Converter
process.
IS Link Database The IS Link Software receives and translates HL-7 data from the RIS or HIS.
The translated data is then stored within the IS Link database.
Listener Process The Listener process waits for HL-7 messages from the RIS and places them
in the message queue without interpretation. This lets the system keep
messages intact for later processing if the Converter process is down for any
reason.
Converter Process The Converter process takes messages from the queue and parses them to
the database tables. When message processing is complete, the Converter
sends the event notifications to the relevant enabled notification queues.
Pre-Fetch Process The CARESTREAM PACS System uses the IS Link Software as a trigger for the
daily Pre-Fetch processes.
NOTE: See Pre-Fetch for a detailed description of the Pre-Fetch process.
RIS-PACS Synchronization The CARESTREAM PACS System uses the IS Link Software as a trigger for the
Process RIS-PACS synchronization process.
NOTE: For more information, see RIS-PACS Synchronization.
Report Presentation The IS Link Software lets the end user, such as a radiologist, view clinical
reports using the PACS Client. The report information is stored in the IS Link
database, and can be retrieved as required.
NOTE: See the user documentation for the CARESTREAM PACS Client for
more information.
104
CARESTREAM PACS IS Link Software
105
Verifying the CARESTREAM PACS IS Link Software Startup
The following procedure verifies that the Listener and Converter processes are running.
1. Log in to the operating system as root.
2. Type cd /usr/algotec/medilink/bin and press Enter.
3. Type ./medilink listener ping and press Enter.
The message "medilink Listener is alive" appears.
4. Type ./medilink converter ping and press Enter.
The message "medilink Converter is alive" appears.
NOTE: If any other messages appear, the Listener and/or Converter startup failed. When a problem occurs, check
that the processes are running by entering the following command: ps –ef | grep medilink
Look for the processes medilink_listener and medilink_converter, and check the TAMAR_LOG file to view the log
messages from the IS Link Software processes to ensure that the CARESTREAM PACS IS Link Software is running
properly (not terminated).
106
CARESTREAM PACS IS Link Software
107
Using the CARESTREAM PACS IS Link Admin Tool
108
CARESTREAM PACS IS Link Software
.
The View Patient Data window appears.
The View Patient Data window shows all data relating to the selected patient. The Additional Information section
allows you to choose any information that is not displayed in the fields.
NOTE: Click the appropriate button if you want to view the specific Visits, Orders, or Reports of the selected patient.
109
CARESTREAM PACS IS Link Admin Tool Visits Tab
The Visits tab displays the visits that are stored in the database.
To view Visit information:
1. Click the Visits tab.
2. Double-click on a visit you want to view, or select Patient Visits from the View Patient Data window in the Patients
tab.
The View Visit Data window appears.
110
CARESTREAM PACS IS Link Software
IS Link Queues
Delete Report You can change the configuration to delete reports. The
default is set to enabled. See System Configuration. To
change this configuration go to the Central Configuration and
change the following path:
PATH:
imaginet\system\applications\medilink\config\admintool\
islink_configurationVALUE: true
IS Link Central
Configuration
Filter
Refresh
111
CARESTREAM PACS IS Link Configuration
IS Link Software is the gateway that links the CARESTREAM PACS System products with hospital/radiology
information systems (HIS/RIS) through an HL-7 interface. Specifically, IS Link Software provides the system with
patient demographic, visit, and order information. It also allows the system to retrieve clinical reports. IS Link
Software runs as a software module within the system.
112
CARESTREAM PACS IS Link Software
Mapping Mechanism
In the IS Link Software, the mapping mechanism allows a change of the default HL-7 mapping to a different field. For
example, where the RIS sends the value of the Exam Start Date field, which it expects to receive from the HL-7 field
OBR-27.4.1, but in fact it sends an OBR-36, the mapping mechanism allows you to change the field mapping of the
Exam Start Date field to OBR-27.4.1 to OBR-36.
Furthermore, the mapping mechanism allows you to perform mappings in the same segment as well as mappings in
different segments. Where mapping has occurred in repeatable fields, the lowest number of repetitions are used.
113
Complex Mapping Table – Dictionary
Lets you define a dynamic table in which the number of fields is dynamic. Columns can be added and removed by the
click of a button. The sorting of the table is performed by order of the fields in the user interface.
114
CARESTREAM PACS IS Link Software
See also:
Handling Multiple Patient IDs in Database Administrator Tool
If there are several patient IDs in the CARESTREAM PACS IS Link Software, you can choose which ID is used in the
system. The HL-7 field for the Patient ID is generally composed of the Patient ID plus information such as Assign
Authority and Facility, or the location of the ID in the HL-7 message sent by the RIS or broker.
The CARESTREAM PACS IS Link Software configures the converter so only one Patient ID is used during the Patient
Matching process. This ID is stored in the CARESTREAM PACS IS Link Software database while the remaining
information is ignored. The repetitions flag determines how many repetitions can be used separately. The
configuration can be found at:
imaginet\system\applications\medilink\config\patient_id\repetitions
The CARESTREAM PACS IS Link Software has a feature for handling multiple Patient IDs. This is required when
integrating with a RIS that sends multiple patient IDs such as in a Multi-site environment, the CARESTREAM PACS IS
Link Software can either select one ID and map it as the primary ID to the WFM or use several IDs for the purpose of
displaying it in the Archive Explorer of the Viewer.
When this feature is disabled, by default, the CARESTREAM PACS IS Link Software chooses the first ID in the
sequence as the primary ID for the patient. When this feature is enabled, the CARESTREAM PACS IS Link Software
stores all the IDs for the same patient.
In the CARESTREAM PACS IS Link Software there is no special importance for any particular IDs, as opposed to WFM
where there is only one identifier for the patient and all the other IDs are for display purposes only. In order to make
the IDs stored in CARESTREAM PACS IS Link Software available for display, it is necessary to map them from IS Link
to WFM. Only mapped IDs are available to be displayed in the Archive Explorer Viewer.
Multiple Patient IDs are sent in PID3.1 as in this example:
PID|||GLOBALPID10099^^^ADT1~LOCALPID3008^^^ADT2
where GLOBALPID10099 is the global Patient ID and LOCALPID3008 is the local Patient ID.
115
Mapping IDs from the CARESTREAM PACS IS Link Software to WFM can be performed in two different ways:
1. According to assigning authority. For example, a map ID with the assigning authority "ADT1" to WFM Patient ID
field and the ID with the assigning authority "ADT2" to the WFM Patient Custom field.
2. According to the order of the Patient ID. For example, map only the first ID in the sequence to WFM Patient ID
field and the second ID in sequence to the WFM Patient Custom field.
The preferred and correct method to map IDs from the CARESTREAM PACS IS Link Software to WFM is according to
Assigning Authorities.
To enable this feature, you must follow these rules:
1. Ensure that each ID you want to display by either assigning authority or by sequence is mapped to a field in WFM.
IMPORTANT: At least one of the IDs must be mapped to the WFM Patient ID field.
2. Ensure that the mapped WFM field used for the mapping is re-syncable.
NOTE: To make a field re-syncable, see Mapping Mechanism.
3. Enable the Patient ID feature.
To add patient ID mappings:
1. Go to:
imaginet\system\applications\medilink\config\api\multiple_pid\
2. Add patient_id_X entry with
select c.val_id from the MDB_Rep_CX_Field c
where c.current_dbid = (select max(c.current_dbid) from MDB_Rep_CX_Field c
where c.column_dbid = 101 and c.dbid = %u and
c.val_assign_auth_name = 'Assigning_Authority')"
where the ''Assigning_Authority' is changed according to the identifier assigning authority.
and
Add patient_id_X_mst_map entry with the WFM field name to map as a value
NOTE: X is a sequential number and can be used for each required ID (1, 2, 3 etc…).
Example:
The following example shows how to map the Global ID shown above to the Patient ID field in WFM and the Local ID
to the WFM Patient Custom field No. 1.
------------------------START VALUE-----------------------
PATH: imaginet\system\applications\medilink\config\api\multiple_pid\patient_id_1
VALUE: select c.val_id from MDB_Rep_CX_Field c where c.current_dbid = (select max(c.current_dbid) from
MDB_Rep_CX_Field c where c.column_dbid = 101 and c.dbid = %u and c.val_assign_auth_name = 'ADT1')
------------------------END VALUE-----------------------
------------------------START VALUE-----------------------
PATH: imaginet\system\applications\medilink\config\api\multiple_pid\patient_id_1_mst_map
VALUE: patient_id
------------------------END VALUE-----------------------
------------------------START VALUE-----------------------
PATH: imaginet\system\applications\medilink\config\api\multiple_pid\patient_id_2
VALUE: select c.val_id from MDB_Rep_CX_Field c where c.current_dbid = (select max(c.current_dbid) from
MDB_Rep_CX_Field c where c.column_dbid = 101 and c.dbid = %u and c.val_assign_auth_name = 'ADT2')
------------------------END VALUE-----------------------
------------------------START VALUE-----------------------
PATH: imaginet\system\applications\medilink\config\api\multiple_pid\patient_id_2_mst_map
VALUE: patient_custom_field_1
------------------------END VALUE-----------------------
116
CARESTREAM PACS IS Link Software
New Site ID
The CARESTREAM PACS IS Link Software includes a new site ID option when there are sub-sites within a main site.
This ensures that the report headers and footers are identical, irrespective from where they are sent. The
configuration can be found at:
system/applications/medilink/cgi/report header
To operate the Site ID function, add the site ID under the report header sub-tree. The CARESTREAM PACS IS Link
Software searches for a Site ID. If it does not find one, it uses the default. Additional Site IDs should be added to the
report_footer node and the order_template node.
117
3. Click Choose HL7 Field.
A window containing a table of all the HL-7 fields appears.
4. Select the required HL-7 field and click OK.
You are returned to the first window.
5. To return to the default settings, click the Restore Default button.
6. To replace the HL-7 value using the dictionary table, check the box to enable the Edit Table button.
7. Click the Edit Table button.
The Old Patient ID Table window appears.
8. Click the Add Data button to add new data.
9. Enter the field Value and add the Converted Value.
10. Edit or Delete any existing value, as required.
11. Click OK to return to the Field Configuration Window.
12. If the Enable RIS-Sync box is checked, you can update the field according to the rule appearing in the drop-down
list. If the box is not checked, the options are grayed out.
13. If you want to Normalize the RIS Value, check the box.
It appears under the Normalized column of the System Configuration table.
14. Click OK.
118
CARESTREAM PACS IS Link Software
Dictionary Mechanism
The dictionary consists of:
Simple Dictionary (Mapping Table): The Simple Mapping Table lets you define simple translation tables of the
various codes you are using. You enter a value and receive the converted value.
Complex Dictionary (Mapping Table): The Complex Mapping Table is a dynamic table in which the number of
fields is dynamic. You can add or remove columns with the click of a button. The sorting of the table is
determined by the order of the fields in the user interface.
To: Do this:
Add data 1. Click the Add Data button.
2. Add the new value and converted value.
3. Click Save and Clear to continue adding new values,
4. Click OK when you are done.
Delete a value 1. Select the value and click the Delete Data button.
You are asked to confirm the deletion.
2. Select Yes.
Edit a value 1. Select the value and click the Edit Data button.
The Update Table Data dialog box appears.
2. Change the value.
3. Click OK.
4. Click Exit to return to the main window.
Add a new Mapping Table 1. Click the Add button on the right side.
The Add Simple Mapping Table dialog box appears.
2. Enter the name of the New Table.
3. Click OK.
The new table is added to the list.
Delete a Simple Mapping 1. Select the table you want to delete and click the Delete button.
Table You are asked to confirm the deletion.
2. Click Yes.
119
The window specifying the complex mapping tables appears.
2. Select a table.
3. Click View.
120
CARESTREAM PACS IS Link Software
IS Link Maintenance
Pushing Scripts
For a RIS system that does not open a connection to the CARESTREAM PACS IS Link Software and sends the HL-7
messages through the connection, it is possible to save the messages in a file. The RIS puts these files in a specific
directory and the CARESTREAM PACS IS Link Software knows where to fetch and read these files, to then insert them
into the database.
The script has two parameters:
The files are saved from the RIS.
The CARESTREAM PACS IS Link Software saves the directory after handling the data from within it.
For WINDOWS OS
C:\Program Files\Carestream Solutions\System5\medilink\admin\
send_file_loop.pl
121
Auditing
The CARESTREAM PACS System includes a comprehensive auditing function that tracks all PHI-related activities,
warnings, and failures that occur in the system.
Using the Audit Viewer Tool, Security Administrators can exclude events from auditing and define filters to manage
information collected by the system. This information can be used to trace the source of selected changes to
information in the system, as well as to detect unusual system activity.
122
Auditing
Warning—events that could affect the system, such as major configuration changes or start/stop operations
(for example, stopping the Info Router). Any changes made to the list of events that are not audited, as
described in Defining Audit Event Settings, are also considered warning events.
Error—events that indicate any type of failure that affects the availability of the system.
Success Audit—events such as successful logins to the system and other security-related matters.
Failure Audit—events that indicate a security violation, such as an authentication failure (bad login) or an
access control restriction violation attempt.
Field Filter area—filters events according to information contained in selected fields, as follows:
o User Name—the name of the user who performed the action recorded by the event.
o Source—the source of the event, such as the Central Configuration.
o Location—the server on which the event occurred.
o Category—the event type, such as System Access or Account Management.
o Sub Category—the event subtype, such as User Authentication or Security Alert.
o Last Name—the patient’s last name.
o First Name—the patient’s first name.
NOTE: Partial entries and wildcards can be used in these fields.
3. Click OK.
The selected filter criteria are applied and the Audit Viewer Tool window appears. See Audit Viewer Tool Window.
NOTE: To erase all currently defined filter criteria, click Clear.
123
Audit Viewer Tool Window
The Audit Viewer Tool window displays those events that meet the defined filter criteria. The Events List area includes
those fields that were selected for display.
The Audit Viewer Tool window lets you perform the following actions:
Managing the Display
Viewing Event Details
Defining General Auditing Settings
Defining Audit Event Settings
Updating Screen Settings
Viewing History
124
Auditing
Archiving an Audit
The Audit Trail allows the user to periodically export and archive data after a specific time (months).
IMPORTANT: It is the responsibility of the site to back up exported data.
For example, if the script runs once a month, the data from the previous month is exported and archived.
An additional script allows the user to import the archived data back to the database so the user can view its
contents.
Field Chooser
By default, a set of fields in the study, series, and image level are displayed. Users can change the set of displayed
fields, the order in which they are displayed, and the width of each column.
Field Chooser options are available by right clicking the column headings and selecting the required option. These
options are described below:
To: Do this:
Move a column Click the column header and drag the column to the right or left.
Delete a column Right-click the column you want to delete and select Remove Column.
Change the column Click the edge between two adjacent column headings and drag to the position
width you want.
Add a column Right-click the column header, select Field Chooser, and click Add.
Remove a column Select a field in the right pane, select Field Chooser, and click Remove.
Save changes Right-click the column header and select Save Settings.
NOTE: If you do not save the settings, changes apply only to the current session
and are not saved for new sessions.
Reset the filters Right-click any column in the right pane and select Clear All Filters.
Reset the default Right-click anywhere in the column header and select Set Default Settings.
settings
To add a field:
1. Right-click the column header and select Field Chooser.
The Field Chooser window appears. The left pane lists all available fields in alphabetical order.
2. Select the desired field.
3. Click Add.
The selected field is added to the list in the right pane.
To remove a field:
• Select the field in the right pane and click Remove.
125
SOURCE The name of the application that generated the event
STUDY INSTANCE UID The unique ID number for the study instance
ADDITIONAL (For future use)
DEST AE The node (including AE title, if any) to which the accessed data was sent
LAST NAME The patient’s last name
LOG DBID N/A
PATIENT ID The patient ID number
SRC AE The node (including AE title, if any) from which the accessed data was taken
SUB CATEGORY The event subtype
CATEGORY The event type, such as PHI Access or System Access
EVENT DATE The event date
LOCATION The server that was the source of the event
LOG NAME (For future use)
SEVERITY The severity of the event
STUDY ACCESSION NO The Study Accession number used by the RIS
USER NAME The name of the user who initiated the event
126
Auditing
127
The selected field name appears in the Field Name list.
6. Select the field name, right-click, then select Add Value from the pop-up menu.
7. In the pop-up window, enter the field value to exclude from auditing.
8. Click OK.
The value appears in the Field Values list.
9. (Optional) Repeat steps 5 and 6 to define additional values for the selected field name.
10. Repeat steps 3 through 8 to define additional discard rules.
11. Click OK to save the settings.
NOTE: To delete a field value, select it from the Field Values list, right-click, and select Remove Value.
To delete a field name, select it from the Field Name list and click .
Viewing History
The History Viewing function allows you to view audits either online or offline. Audits that are kept offline prevent the
list of the Audit Trail Viewer from become overloaded. The time parameters for when events are taken offline is
configurable.
1. From the View option of the menu bar, choose Select Audit Repository.
2. Choose Audit Offline.
The offline Audit View trail appears.
1. Click Export .
2. In the Export Audit to File window, select the location to save the file.
3. Click OK.
128
Workflow Management
Highly modular system design ensures scalability and easy expansion to accommodate growing and evolving
needs.
Open standards-based system guarantees easy integration and connectivity with other imaging and health care
information systems.
Unique hybrid distributed/centralized system architecture assures fault tolerance.
Storage solutions range from magnetic disk/RAID-based short-term buffers to multi-layered DLT libraries, or any
other library compatible with and supported by NetBackup, offering terabytes of capacity.
Multiple backup features provide high redundancy and fault tolerance.
Intelligent management and image compression software minimizes costs.
All functions are Web enabled and Web controlled.
RIS-PACS synchronization ensures that all data and images stored are always up-to-date and are the same as
the hospital records.
The Workflow Manager is a “r;privacy-enabled” system that provides tools that facilitate compliance with HIPAA
regulations.
Workflow Grid
The Workflow Grid system allows for multi-site configurations to include the following capabilities:
1. Sharing studies throughout an organization.
2. Creation of a Data Center.
3. Cross-reading between hospitals.
4. The ability to perform multiple functions using one system.
These capabilities provide a true "virtualization" of the reading process across various sites, regardless of the physical
architecture and supporting various configurations and relationships between sites. The Workflow Grid technology
supports the following key features:
Global Worklist—users can access a single Worklist representing their "to do" list – studies that need to be read,
even if studies included in the list are stored in different physical locations.
Unified Workflow—users can use the same workflow whey reading studies stored in different locations, including
having all relevant study information together with updated statuses.
Study Tunneling—the system is able to select the fastest and most efficient route in certain scenarios where the
user retrieves studies located on a remote server. This involves the use of streaming technology on a per-study
basis.
Data Integrity—a synchronization process between sites with a mechanism to ensure that all relevant data is
synchronized correctly and to be able to recover from scenarios where the synchronization was interrupted.
Since the system is flexible it supports the configuring of different levels of synchronization to balance properly
between the need of updated data and database and network overloads.
Supporting Unlimited Architecture—The "building blocks" composing the technical solution of Super PACS are
designed so that they support a wide variety of configurations and can be tailored for specific use cases when
required.
129
SUPERPACS Building Blocks
The Super PACS architecture is based on two key elements:
1. Server Metadata Synchronization
2. Protocol Tunneling
Each server in a multi-site environment has its own database and is able to work independently of other servers
belonging to this environment. At the same time, each server is defined as a Server (Target Server) synchronized
against another server (Original Server).
Example:
All metadata tags related to Study Status (such as "Locked By") these are maintained as one group and are
synchronized between sites every five seconds. Whereas all metadata tags related to Teaching File information (such
as ACR Codes or Pathology) are maintained as one group and synchronized between sites every 60 seconds.
Since the study level details are of most interest, only these details are synchronized between sites. If other Series
Level or Image Level information is required this is performed on an "as required" basis.
130
Workflow Management
131
Tunneling Protocol
Tunneling is a new mechanism that enables efficient and intelligent routing of study data between any multiple
servers.
The main benefits of the Tunneling Protocol are:
Allows a CONN-based connection between clients and remote servers, i.e. servers at other sites.
Integrated support over GRID: Secured (SSL) / Non Secured and FAST/Streaming loading.
Performance optimization—The new mechanism knows the most optimized way to perform each operation.
It supports the following capabilities:
Querying an operation to a remote server including DICOM tags and proprietary information such as Order and
Report information, Sticky Notes and Teaching Files information.
Images are automatically retrieved from their fastest location. Seamlessly switching between lossless and
streaming technology.
Abstracting the sites infrastructure—the user can easily get data from a distant and unknown PACS, without
having any connection or knowledge of that site.
Enhanced speed—data is streamed through the tunneling mechanism, so there is no need to wait, a complete
study “travels” across all nodes until it is displayed to the user.
132
Workflow Management
Fast, Best Quality For studies available either on local, Online or Online2 tiers and arriving in best
quality mode.
Slow, Best Quality For studies available nearline arriving in best quality mode (the user is physically
connected on a slow network to the server on which the study is stored).
Fast, Progressive Quality For studies available either on Online or Online2 tiers and arriving in progressive
quality.
Slow, Progressive Quality For studies available on nearline arriving in progressive quality.
Unavailable For offline studies.
NOTE: The Fast and Slow values indicated in the Expected Rate column refer to the expected rate derived by storage
tier—online / nearline / offline—and not to the traditional internal referral of a fast network versus a slow network.
Priors Policy
The important parameter of the streaming policy is the location of the studies and not the login mode.
The DP Streaming flag should be used as follows:
The flag must always be used and not limited to specific login modes
The flag determines whether to bring priors or not based on the location of the priors
The behavior supported by using this flag is as follows:
When set to True, the DP always retrieves priors as define in the DP rules, regardless of their location.
When set to False the process is to first identify the prior studies that should be loaded based on the DP rules
and then, from those studies only automatically load priors available on a fast network.
Export Operations
Export operations, such as Key Images or Saving DICOM images, are performed against the original server from
which the study was retrieved. When the user is working against a Global Worklist and is loading studies from
133
different locations, then for each study the exported data is saved automat9cally to the server from which the study
was retrieved from.
134
Workflow Management
135
Database Encryption
The CARESTREAM PACS system can use the ORACLE 10 Transparent Data Encryption mechanism to encrypt sensitive
database columns. The encryption is almost transparent to PACS applications.
During installation, specific database columns are marked as encrypted.
After providing the access-password, encryption and decryption of sensitive database columns is enabled for all
applications, until the database instance is shut down or the system administrator provides a lock-password:
o On store—each time patient data is saved to the database, ORACLE encrypts the data before writing it to an
encrypted column.
o On query/load—each time a PACS application queries the sensitive data, Oracle decrypts the sensitive
columns before sending data to the application.
136
Workflow Management
137
Storage Management Admin Tool Window Toolbar
The Storage Management Admin Tool window toolbar lets you perform various common operations, such as updating
patient and study details, moving studies, and viewing study location. The Storage Management Admin Tool window
toolbar contains the following options:
Merge Patient Lets you move one or more studies attached to an incorrect patient to
the correct patient.
Split Patient Lets you move one or more studies attached to an incorrect patient to a
newly created patient.
Refresh Online Lets you manually refresh the data that appears in the Studies List area.
Studies
Display Settings Lets you configure the automatic refresh settings and the maximum
rows of data that display in the Studies List area.
View Filter Window Lets you filter the data that appears in the Studies List area using single
or multiple filter criteria.
Study Location Lets you search for and view the location of one or more studies in the
system.
Study Media Lets you search for and view the location of the backup media for one or
more studies in the system.
Manual RIS-Sync Lets you perform a manual synchronization between the RIS and the
Online Storage Manager.
Exit Lets you exit from the Storage Management Admin Tool and return to
the CARESTREAM PACS Admin Home Page.
Explore Study Lets you explore the series in more detail.
138
Workflow Management
139
Storage Management Admin Tool Right-Click Menu
The Storage Management Admin Tool right-click menu appears when you right-click on a study in the Studies List
area. This lets you perform frequently used functions.
140
Workflow Management
To: Do this:
Move a column Left-click the column header and drag the column to the right or
left.
Delete a column Right-click the column you want to delete and select Remove
Column.
Change the column width Left-click the edge between two adjacent column headings and drag
to the position you want.
Add a column Right-click anywhere on the column header, select Field Chooser,
and click Add.
Remove a column Select a field in the right pane, select Field Chooser, and click
Remove.
Save changes Right-click anywhere in the column header and select Save Settings.
NOTE: If you do not save the settings, changes apply only to the
current session and are not saved for new sessions.
Reset the filters Right-click any column in the right pane and select Clear All Filters.
Reset the default settings Right-click anywhere in the column header and select Set Default
Settings.
The Field Chooser window appears. The left pane lists all available fields in alphabetical order.
141
2. Click the desired field.
3. Click Add.
The chosen field is added to the list on the right pane, which lists the fields to be displayed.
4. To remove a displayed field, highlight a field in the right pane.
5. Click Remove.
6. Use the Move Up and Move Down buttons to change the order in which the displayed fields appear.
7. Click OK when complete.
142
Workflow Management
143
3. Complete the details in the fields.
4. Click Search Series.
A list of series appears.
5. Select the series.
6. Click OK.
The details are entered automatically into the Select Target Series for Merge window.
7. Click OK.
A prompt appears.
8. Click OK.
Splitting a Series
1. From the Image Details window of the Database Admin Tool, select an image.
2. Click Split from Series.
The Select Target Study window appears.
144
Workflow Management
145
Protecting and Unprotecting Studies
The Database Admin Tool allows you to mark a study as Protected or to revert a protected study to Unprotected.
Studies that are protected are not influenced by the auto-delete process or from any manual deletion operation.
To protect a study:
1. From the Database Admin Tool, select a study.
2. Click Protect Study.
3. Click Refresh.
The protection status of the study is displayed in the Study Locked column.
NOTE: For details of how to view the Study Locked column, refer to the description for using the Field Chooser.
To unprotect a study:
1. From the Database Admin Tool, select a study.
2. Click Unprotect Study.
3. Click Refresh.
The protection status of the study is displayed in the Study Locked column.
146
Workflow Management
Once the feature has been activated, a new Manage Patient ID option is added to the right-click menu when you click
on study.
The Manage Patient ID option is not shown by default, you can add it through the system configuration tool:
imaginet\system\applications\medistore\admintool\use_pid_manager = TRUE (default)
Note: The update patient dialog will not allow changing patient ID/issuer anymore
It is now possible to view, add or update a PID.
147
To delete an existing PID:
All operations are synced except Delete. The Delete button is disabled by default.
To change the default setting, go to:
set imaginet\system\applications\medistore\admintool\allow_pid_delete = TRUE
Once enabled, a Delete key appears:
148
Workflow Management
149
Online Storage Management Auto Delete
The Online Storage Management system serves as the main image repository in the Web Distribution System. Images
from current studies based on queries received from operators are loaded, stored on, and retrieved from the Online
Storage Management system, as required.
Since there is a finite amount of disk space on the Online Storage Management system, space must be cleared
periodically by removing those studies that are least likely to be required. Removing studies is managed by the Auto
Delete process, which is governed by a set of configurable rules or priorities, customized to meet each site's specific
needs. Once the rules are configured, this process operates automatically, without the need for user intervention.
The Online Storage Management Auto Delete process is triggered by a configurable timing schedule whenever the
available free online disk space falls below a user-defined threshold (low watermark). When this threshold is reached,
the Auto Delete process is invoked each night at a preconfigured time and deletes studies until the free space rises
above a (second) user-defined threshold (high watermark). The default time set during the installation of Online
Storage Management is 3:00 a.m.
The Online Storage Management Auto Delete process also writes a report into the standard log file (usually
/usr/tmp/TAMAR_LOG), logging all of the delete actions.
NOTE: Online Storage Management Auto Delete rules and Auto Delete threshold parameters can be configured. For
more information, contact Customer Service.
The Online Storage Management Auto Delete process consists of two phases:
Studies Removal
Database Analysis
150
Workflow Management
151
Image Resend
The Image Resend process prevents images from being archived multiple times. It protects the database from storing
duplicate images and assures that the stored image represents the latest version received by the database.
Images are usually added to the database as part of a study. Individual images can later be retrieved from online
storage, manipulated, and returned to storage. When the image is returned to storage, it overrides the older image.
Before an individual image is added to the database, a cross-reference check is performed to determine whether an
image with the same SOP instance UID already resides in the Workflow Manager database. If such an image is found,
the Workflow Manager verifies that the incoming image and the stored image have the same series instance UID and
study instance UID. Only after this verification does the incoming image override the older image. If a difference is
found in one of the SOP instances, the image is rejected.
152
Workflow Management
153
Studies Removal
The studies to be removed are selected as follows:
To avoid any possibility of losing image data, only images that are already backed up in the long-term storage
are deleted.
If the system has long-term storage, the studies are removed from the disk, but the database entries remain
untouched. If a removed study is requested in the future, it is retrieved from long-term storage. If the system
does not have long-term storage, the studies are removed from the disk and from the database.
Studies are removed according to their priority group categories, starting from the least important group and
ascending hierarchically until the process is completed. Within each group, studies are sorted according to the
least recently accessed rule, meaning that the least recently accessed studies are deleted first.
154
Workflow Management
You can manage the studies displayed in the Studies List area by performing these standard functions:
Filtering the Studies List
Sorting the Studies List
Configuring Display Settings for the Storage Management Admin Tool
Refreshing the Studies List
155
Filtering the Studies List (Storage Management Admin Tool)
The studies list can be filtered according to the information contained in one or more columns. Different types of
filters are used for different columns.
The studies list can be filtered using multiple filter criteria at one time or by using only one type of filter, as required.
If filters have been applied, the filter criteria are displayed in the relevant filter fields (the white fields above the
column names).
NOTE: The Enter Filter Values window also appears automatically when you open the Storage Management Admin
Tool window. This lets you filter the studies included in the studies list before the list is loaded, reducing the download
time required to display the list.
Filter Types
The following types of filters can be applied to the studies list in the Storage Management Admin Tool window.
String Filter A string filter is applicable to columns that display data in string format and can
accept any kind of string. Each string in the column that begins with the entered filter
string passes through the filter and appears in the Studies List.
Date Filter A date filter is applicable to columns that display data in date format.
There are two ways to enter this type of filter:
Between: Filters the studies list by the defined date range. Enter the to and from
dates in DD/MM/YYYY format, or to insert the current date, click Current Date for
the relevant field.
Previous: Select/enter the number of previous days (for example, 7 for the
previous week). All studies added to the archive during the previous [x] days
appear.
Numeric Filter A numeric filter is applicable to columns that display numbers. This type of filter
enables the entering of a single number or a numeric range.
156
Workflow Management
Symbol Description
First Sort Ascending
From the Storage Management Admin Tool toolbar, click Display Settings .
From the Edit menu, select Display Settings.
The Display Settings window appears.
2. Select the Automatic Refresh check box to activate the automatic refresh feature.
3. In the Refresh Interval field, select/enter the refresh interval in seconds.
4. In the Limit Fetched Rows to field, enter the required maximum number of rows to appear.
NOTE: You can enter a value of 0 to display all studies, but the list may be so large that it is unworkable.
5. Click OK.
157
Updating Patient Details (Storage Management Admin Tool)
You can update patient details, such as the patient’s name, sex or birth date for an individual patient or for multiple
patients at the same time.
1. Select the required study or studies in the Studies List area.
2. Do one of the following:
From the Storage Management Admin Tool toolbar, click Update Patient .
From the Edit menu, select Update Patient.
Right-click the required study in the Studies List area and select Update Patient.
158
Workflow Management
From the Storage Management Admin Tool toolbar, click Update Study .
From the Edit menu, select Update Study.
Right-click the required study in the Studies List area and select Update Study from the Storage Management
Admin Tool right-click menu.
The Update Study Data window appears.
NOTE: When updating study details, the Accession Number field and the Study ID field are disabled, as this unique
data for each study cannot be updated.
The study modality is calculated by adding the modality of the series.
3. To edit the modality of the study, click Edit Modality.
The Update Series Modality window appears:
4. Click on the drop-down menu button to choose the modality or enter a different modality if it does not exist in the
list.
If you have chosen a modality that does not appear in the list, a confirmation message appears. Edit as required,
and click OK.
5. Update the study data, as required.
6. Click OK.
The Confirm Update message appears, prompting you to confirm the update operation.
7. Click Yes.
The relevant study data is updated in the archive.
From the Storage Management Admin Tool toolbar, click Merge Patient .
From the Tools menu, select Merge Patient.
Right-click the incorrectly attached study in the Studies List area and select Merge from the Storage
Management Admin Tool right-click menu.
The Select Target Patient For Merge window appears.
159
3. Enter one or more patient criteria in the fields, as required.
You can also enter a partial string in any of the fields. Start with the initial characters. The subsequent characters
may be omitted.
4. Click Search Patient.
The Select A Patient window appears with a list of patients matching the criteria that you defined in the previous
step.
5. Select the required patient and click OK.
Any missing patient details appear in the Select Target Patient For Merge window.
6. Click OK.
The Merge Patient Confirmation message appears, prompting you to confirm the Merge operation.
7. Click OK.
The Merge Patients Successful message appears.
8. Click OK.
The incorrectly attached study merges with the selected patient information in the archive.
NOTE: The Merge operation may take longer if you are merging multiple studies. In this case, an additional
confirmation message appears, informing you that it will take some time and asking if you want to continue with the
Merge operation.
CAUTION: If the error message “Error Connecting to Admin Server” is received when performing either
the Merge or the Split operations, you must ensure that the Admin Server process is running.
160
Workflow Management
Detaching Studies
Detaching of a study from a patient is done when a study is inserted and attached to the incorrect patient. Sometimes
when you search for a patient to whom you would like to attach a study, you find that the required patient has not
yet been created. The Split operation lets you create a new patient and move an individual incorrectly attached study
or multiple studies to that new patient.
161
Split and Merge Series Pre-Fetched from External Archive(s)
NOTE: After the last study is received, you must wait five minutes before performing a Split or Merge function.
162
Workflow Management
163
Merging a Series from One Study to Another
1. Using the Admin Tool, locate the series to merge.
2. Note the following:
Patient ID
Patient Name
Study ID
Series Number
External Archive (E-SIR) where the study is located
3. Click the Storage Management Admin Tool toolbar.
4. Select the patient/study to which series have to be merged.
5. Note the following:
Patient ID
Patient Name
Accession Number
Study ID
6. Note the External Archive (E-SIR) location where the study to merge is located.
NOTE: In the case of multiple External Archives (E-SIRs), note the External Archive (E-SIR) node.
164
Workflow Management
165
Merging a Series from Multiple External Archives (E-SIRs)
Use this procedure to merge a series from one study to another and when the “from” and “to” studies are located on
different External Archives (E-SIRs).
1. Using the Admin Tool, locate the series to merge.
2. Note the following:
Patient ID
Patient Name
Study ID
External Archive (E-SIR) where the study is located
3. Click Merge Patient from the Storage Management Admin Tool toolbar.
4. Select the patient/study to which series have to be merged.
5. Note the following:
Patient ID
Patient Name
Accession Number
Study ID
6. Note the External Archive (E-SIR) location where the merge to study is located.
7. On the Merge tab, click OK to save your changes.
8. Go to the WebView Contents menu on the system console of the External Archive, and select the DB Update Tool.
9. When the Database Query page appears, enter the information from step 2.
10. After a patient level, study level, or query is performed, the delete function appears on the resulting Patient List
page, letting you delete the series.
11. Click the appropriate check box(es) to select the item(s) to be deleted.
NOTE: Up to five items can be deleted at one time.
12. Click Delete to delete the entire series from the database.
13. Repeat steps 8 to 12, except that when the Database Query page appears, enter the information from step 5.
166
Workflow Management
Click Study Location from the Storage Management Admin Tool toolbar.
From the View menu, select Study Location.
Right-click the required study and select Location.
The Studies Images Locations window appears, listing the exact location of all copies of the study or studies in the
system, as shown in this example:
/fir_fs: The study is online.
/sir_fs: The study is in the Long-Term Storage Manager or the Long-Term Storage Manager cache.
Backed up in Jukebox: The study is offline (in the Jukebox).
Backed up in External Archive: The study is nearline on an E-SIR.
167
Viewing Backup Media for Studies (Storage Management Admin Tool)
You can view the exact backup media location for near-line studies (in the Long-Term Storage Manager cache) and
offline studies (outside the library).
The Media operation can be performed for an individual study or for multiple studies at the same time. This lets you
quickly locate the relevant tape or tapes and determine if they need to be inserted into the Jukebox before you send
the Fetch command to the system.
1. In the Studies List area, select the required study or studies.
2. Do one of the following:
From the Storage Management Admin Tool toolbar, click Study Media .
From the View menu, select Study Media.
Right-click the required study and select Study Media.
The Media ID List window appears.
NOTE: If a study has not yet been backed up on tape, a message appears informing you that the study does not
reside on any media.
168
Workflow Management
To update a Media:
1. From the Media tab, mark a study you want to update.
169
2. Click the Update Media button.
The Update Media XXX dialog box appears.
3. In the Media Status field, you can change the status from the dropdown list of options.
4. Use the arrows to change how many copies are available.
5. Click OK.
NOTE: The Auto-Refresh option automatically refreshes the data in the tabs, but you can also click on the icon to
refresh the list data.
When there are multiple CD Direct servers installed in a system, only one CD Direct workstation can be used as the
SMA. The CD Direct station used as the SMA is set during CD Direct installation, but can be changed to a different
station at any time later using the SMA Settings dialog boxes.
Using WADO
The WADO Retrieve transaction enables an Imaging Client to access DICOM SOP Instances with a web-based service
through an HTTP/HTTPS protocol.
The Imaging Client issues an HTTP "Get To" request to request a specific DICOM instance from the CARESTREAM
PACS Client. The CARESTREAM PACS Client receives the request and generates the response with the appropriate
content and sends an HTTP response to the Imaging Client.
The message semantics are defined by the DICOM Web Access to DICOM Persistent Objects (WADO), PS 3.18.
The WADO Retrieve transaction is performed by the Imaging Client to send an HTTP Request-URI to the Workflow
Manager. The Imaging Client generates the HTTP Request-URI to retrieve a DICOM instance. The DICOM instance is
specified with its Study Instance UID, Series Instance UID and SOP Instance UID in the HTTP Request-URI. The
Imaging Client must obtain the host information (e.g., web server location and script language) of the web server to
perform this.
The Imaging Client can map the Retrieve AE Title of the SOP Instance to the web server host information based on its
local configuration.
The IMS WADO URL: http://www.carestreamserver/um/webapp_services/wado
The IMS WADO service supports the following fields in the HTTP request:
170
System Configuration
The System Configuration tool is divided into two sections: Application Configuration and Workflow Configuration.
Workflow Configuration
The Workflow Configuration provides a flow to define configuration parameters by providing a structured step-by-step
wizard to guide the user in the process of configuring a specific flow. The Workflow Configuration tool is the flow to
configure Image Storage rules.
Application Configuration
The Application Configuration section includes the various configuration parameters that are defined per
Application/Component.
171
Restarting Services and Processes
Once changes have been made and saved, the Save Operation window appears. This windows shows the changes
made and restart options. Both services and processes can be restarted.
DICOM Configuration
The DICOM configuration allows you to configure servers and printers using the System Configuration.
172
System Configuration
Standard Fields
JPEG Lossless JPEG Lossless 1st Order predictions, JPEG Lossless PR14
JPEG Lossy/
Lossless 2000
RLE Lossless RLE Lossless, compressed or uncompressed
Custom Can define additional custom TX. See also Enhanced TX support.
Supports Study Root Does this node support the DICOM Study Root query/retrieve model?
Supports Image Query Does this node support queries at the image level? If disabled, the
CARESTREAM PACS Client does not allow exploration to image level in the
Archive Explorer.
Invoke Filter In CARESTREAM PACS Client the filter is invoked automatically. This
option is used to avoid excessively long queries to this node.
Create Folders in DX Should this server appear in the CARESTREAM PACS Client Archive
Explorer?
Search What is the display name of the Search Folder in CARESTREAM PACS
Client Archive Explorer? This allows non-English users to change the
display name of the folder.
All Studies What is the display name of the All Studies Folder in CARESTREAM PACS
Client Archive Explorer? This allows non-English users to change the
display name of the folder.
All Patients What is the display name of the All Patients Folder in CARESTREAM PACS
Client Archive Explorer? This allows non-English users to change the
display name of the folder.
Presentation State C-Move Determines what to do with Presentation States when they are copied to
Policy this server. See Presentation_State_C_Move_Policy table.
Move with Referenced Images Presentation States are moved together with all referenced images, even if
they were not requested.
Apply Presentation State Presentation State is applied to the referenced images and this unified
result is stored to the server.
Ignore Presentation State Presentation States are not moved to this server regardless of any prior
command.
New Association Storage Commitment response to this server is provided using a new
association.
Not Allowed Storage Commitment is neither offered nor accepted in DICOM Association
to this server.
174
System Configuration
175
Workflow Manager Configuration (DICOM)
The window contains the following tabs:
Server Options
Node Options
Communication Configuration
Loader Configuration
176
System Configuration
The Transfer Syntaxes are used for all non-customized SOP classes, both as client or server:
When acting as a client, it requests all configured Transfer Syntaxes from the specific Node
When acting as a server, it supports all configured Transfer Syntaxes for the specific Node
177
The more you exclude, the more you can multiply.
DICOM Tunneling
Use Cases
1. Transferring messages compressed in private formats (RICE) and from 3rd party archives to 3rd party clients, via
the C-Move protocol, use the SVDDS service as a mediator for format conversion purposes.
Note: The DICOM C-Move command has three roles participating: Move Caller, Move Provider, and Move Destination.
Move Caller - the entity invoking the move command
Move Provider - the entity presumed to have the data
Move Destination - the entity to which the data is sent
The Move Caller and the Move Destination can be different entities.
2. Forwarding stored responses between a client not directly connected to a provider, but via one or more Carestream
servers.
3. Updating the DICOM messages retrieved from long term storage, with newer information stored on the servers
before transferring them to the move destination.
178
System Configuration
3. There is a new device type called DDS, which is the DICOM tunneling entry point.
4. The DDSs AE title of the local server is determined upon installation or upgrade. It can be found in the Work Flow
Manager section of the System Configuration. The port is the same as the port of the FIR.
179
5. Add the DDS-type AE title of all other Carestream servers in the archive section, and all 3rd party archives as well.
The new AE has the same port as the FIR AE title.
NOTE: This AE title cannot be queried.
180
System Configuration
181
HL-7 to PACS Field Mapping Set
The user interface permits each field to define a number of different points, such as:
HL-7 Mapping
Whether the value of the field received the HL-7 message and if it is passed as is or is converted through the
simple mapping table (Dictionary Mechanism) when one of the other applications is the IS Link API.
The fields that are part of the synchronization process between the CARESTREAM PACS IS Link Software and the
Storage Management Software (RIS Sync) process — the reason that caused it to be part of the RIS Sync
process — is either Not Null in IS Link or Null in Storage Management Software.
Whether or not the value passed through normalization during the RIS Sync process.
There are three exceptions:
Body Part
Modality
Service Area
By default, these are taken from the Complex Procedures Table and the user can select whether they are taken from
the Complex Table or the HL-7 Mapping (the message). If it is taken from RIS, the rules above apply.
182
System Configuration
Dictionary Mechanism
The dictionary consists of:
Simple Dictionary (Mapping Table): The Simple Mapping Table lets you define simple translation tables of the
various codes you are using. You enter a value and receive the converted value.
Complex Dictionary (Mapping Table): The Complex Mapping Table is a dynamic table in which the number of
fields is dynamic. You can add or remove columns with the click of a button. The sorting of the table is
determined by the order of the fields in the user interface.
To: Do this:
Add data 1. Click the Add Data button.
2. Add the new value and converted value.
3. Click Save and Clear to continue adding new values,
4. Click OK when you are done.
Delete a value 1. Select the value and click the Delete Data button.
You are asked to confirm the deletion.
2. Select Yes.
Edit a value 1. Select the value and click the Edit Data button.
The Update Table Data dialog box appears.
2. Change the value.
3. Click OK.
4. Click Exit to return to the main window.
Add a new Mapping Table 1. Click the Add button on the right side.
The Add Simple Mapping Table dialog box appears.
2. Enter the name of the New Table.
3. Click OK.
The new table is added to the list.
183
3. Click OK.
Delete a Simple Mapping 1. Select the table you want to delete and click the Delete button.
Table You are asked to confirm the deletion.
2. Click Yes.
184
System Configuration
In the case of an empty field, the DICOM Parsing feature enables the CARESTREAM PACS Workflow Manager to
recognize that the data in one field relates to another field, by transforming the field tag without affecting the input
screen. In case of a partially unused field, multiple data is entered in a single field, divided by separators, and then
broken into smaller chunks of information, each forming a distinct DICOM tag. In both cases, once the images are
imported into the CARESTREAM PACS Workflow Manager, they can be indexed and stored accurately and efficiently.
Using the rules in a Tag Morphing scenario can provide any user the ability to replace their existing PACS system, for
example, while maintaining data integrity.
The parsing mechanism supports two main scenarios:
Exporting data from the WFM - Query or Move
Inserting data to the WFM - Store or Update tags
The Rule Filter window allows you to apply the rule on export:
185
Choose Query to set the value query in DSER_PARSE_RULE_FILTER.FILTER_SCENARIOS.
Choose Move and Query to set the values query and move in this column.
Concatenation Rule
186
System Configuration
If it is necessary to concatenate the parsing results to an additional tag, this can be performed in the DICOM Parsing
Rule Editing Panel.
1. Choose the Parsing method.
2. Add basic Parsing tag.
3. Add any prefix or suffix values.
4. Parsing result concatenation.
a. No Concatenation
b. Add before existing value in the To Tag
c. Add after the existing value in the To Tag
d. Add any separation string, if required
NOTE: Tag Morphing/DICOM Parsing is based on a number of predefined, configurable rules. These rules can be
configured using the Admin Tool. Contact Customer Service for more information.
187
Configuring Database Objects Auto-Delete
Images saved as Icons or Streaming Tags can be deleted after a configurable amount of time or based on storage
availability. It is more likely that storage space is more important than time.
The DB Objects Auto-Delete option under Life Cycle Management of the System Configuration provides two options
for deleting database objects, Icons or Streaming Tags:
Set Icons Storage Limit
No Icons Storage Limit
If the No Icons Storage Limit is selected, the storage information is displayed in linear format of both the Icons
Tablespace Size and the Current Storage used.
If the Set Icons Storage Limit is selected, the screen expands to display Icons Auto-Delete Settings. You can specify
to manually set the storage limit or allow the system to calculate the storage limit by icons sized based on the
number of months entered into the field.
The storage limits are displayed in cylindrical form based on either the automatic calculation or the specified
parameters. The delete mechanism always deletes the oldest information first.
188
System Configuration
189
Configuring Study Grouping
Study grouping is a method for ensuring that study details are always attached to the correct group, based on their
unique ID. Study grouping can be performed using the data in the CARESTREAM PACS Workflow Manager or using
data stored in the hospital RIS server.
To remove a rule:
1. Select the rule and then click Remove.
You are asked to confirm the removal.
2. Click OK.
190
System Configuration
Configuring Pre-Fetch
Pre-Fetch is based on a number of predefined, configurable conditions and rules. These can be configured using the
CARESTREAM PACS Admin Tool.
1. Click Workflow Manager Configuration in the left pane and then click Pre-Fetch.
The Pre-fetch Patterns Set in Workflow Manager window appears in the right pane.
To remove a rule:
1. Select the rule and click Remove.
You are asked to confirm the removal of the rule.
2. Click OK.
191
The New Rule Name dialog box appears.
2. Enter the new name and click OK.
The new name appears in the list.
3. To prioritize the rules use the arrows on the left side of the window.
192
System Configuration
To remove a strategy:
1. Select the strategy, then click Remove.
You are asked to confirm the deletion.
2. Click OK.
193
Configuring Compression Settings
Compression of images is the function of the Online Storage Manager. The manner in which images are effectively
stored reduces the use of storage space as well as reducing the traffic on the network.
The compression of the images to be stored can be performed in three ways:
Compressed: Using JPEG / JPEG2000 compression, the user can decide how much loss to introduce and make a
trade-off between file size and image quality.
NOTE: This is only available for use in a state and country that allow picture processing using this method. If you
select this method, a warning appears that asks you to confirm that you understand the implications of using
compressed images.
Lossless Compression: With Lossless Compression it is possible to use JPEG / JPEG2000 / RICE compression. All
image information originally in the file remains after the file is uncompressed.
Lossy Compression Factor: Lossy Compression reduces a file by permanently eliminating certain information,
especially redundant information. When the file is uncompressed, only part of the original information is still
there (although the user may not notice it).
Each Online Storage Manager can be separately defined to store images in a different compression mode. In addition,
it is possible to define more detailed policies to choose a particular compression method according to the source AE or
even modality. The compression is determined at the time that the image is stored.
NOTE: The Lossy Compression Factor controls the amount of compression. When the value is high, the file is more
compressed. When the value is low, the file is less compressed.
194
System Configuration
195
JAVA Configuration
The JAVA Configuration GUI must be standalone (installed locally on the service PC) and not only web-based to
reduce the time during a remote connection.
For example: If version 11 already exists, it automatically runs System Configuration. If version 11 does not exist,
the system searches on the server for the JAR files and downloads the files for System Configuration.
1. Go to Carestream --> syscfgplugin.
196
System Configuration
IS Link Configuration
IS Link Software is the gateway that links the CARESTREAM PACS System products with hospital/radiology
information systems (HIS/RIS) through an HL-7 interface. Specifically, IS Link Software provides the system with
patient demographic, visit, and order information. It also allows the system to retrieve clinical reports. IS Link
Software runs as a software module within the system.
197
Configuring a Converter and Listeners
Converter
The converter process takes messages from the queue and parses them to the database tables. When message
processing is complete, the converter sends the event notifications to the relevant enabled notification queues.
Listeners
The listener process waits for HL-7 messages from the RIS and places them in the message queue without
interpretation. This process enables the system to keep messages intact for later processing if the converter process
is down for any reason.
To edit a listener:
1. Click Edit Listener.
The Edit Listener window appears.
2. Edit the fields as required.
3. Click OK.
To delete a listener:
1. Click Delete Listener.
You are prompted to confirm the deletion.
2. Click Yes.
198
System Configuration
199
Configuring Reports and Orders Values
CARESTREAM PACS IS Link Software enables the end user, such as a radiologist, to view clinical reports using the
CARESTREAM PACS Client. The report information is stored in the IS Link database, and can be retrieved as required.
1. Click IS Link Configuration in the left pane, then select Reports & Orders.
A window appears in the right pane of the window.
200
System Configuration
To add a Parser:
1. Click Add Parser.
The Add Parser window appears.
2. Complete the fields as appropriate:
Search Text
Replace Text
Prefix Text
Suffix Text
Case Sensitive
Use Original Text
Enable
3. Click OK.
201
Configuring Queues and Notifications
When message processing is complete, the converter sends the event notifications to the relevant enabled notification
queues.
1. Click IS Link Configuration in the left pane, then select Queues and Notifications.
A window appears in the right pane of the window.
2. To add notification, select a parameter in the Queue Name list.
The list of Notification Types appears under the Notification Name list. The checkbox shows whether or not the
notification name is enabled.
3. Click the Add Notification button.
The Add Notification window appears.
4. Enter the Name of the notification.
5. Enter the Notification Condition.
6. Check the Enable box.
7. Click OK.
To delete a notification:
1. Select the Queue Name to display the list of notifications, then select the notification you want to delete.
2. Click the Delete Notification button.
You are asked to confirm the deletion.
3. Click Yes.
202
System Configuration
203
Configuring General Email Values
1. Click E-Mail Suite Configuration in the left pane and then select General.
A window appears in the right pane.
2. Complete the fields, as appropriate:
Administrator E-mail
Mail Server IP
Default Web Server Software Device (name from archive list)
204
System Configuration
Click Save .
205
Info Router Configuration
The System Configuration tool includes the configuration parameters of the Info Router component. The configuration
parameters include the definition of Rules and Aliases, as well as the ability to define general configuration
parameters and rule-specific configuration parameters.
Screen splitter arrows between the areas enable you to either resize the Rule Information area, or click and drag it to
a new position. The Rule tab right-click menu also provides access to frequently used functions.
Option Description
Status The operational status of the rule.
Rule ID The unique identification number for each rule that is assigned in the order in which the
rules are created.
If a rule is deleted, the remaining rules retain their original identification numbers.
Event The name of the event for which the rule is defined.
206
System Configuration
207
Configuring Info Router Aliases
An alias is a defined alternate name for an item or a group of items that might include users or devices. An alias can
have conditions applied to it, for example, a range of dates within which the alias applies, or a group of different
locations to which information is to be sent.
The Alias tab displays a list of aliases, together with information about each alias.
Option Description
Alias Name The name of the alias.
Defining/Modifying Aliases
An alias is a name defined for an item or a group of items, including devices, users, and/or other aliases. An alias can
have conditions applied to it, for example, a range of dates within which the alias applies or a group of different
locations to which information is to be sent. These defined conditions are required to activate the alias.
For example, you can create an alias called On-Call that consists of the user, Dr. Jones. The conditions for this alias
may be a range of dates: January 1, 2003 16:00 to January 2, 2003 23:00. The system recognizes Dr. Jones as the
on-call physician and routes information and/or images to Dr. Jones during the specified time frame (as defined by
the rules).
All defined aliases, together with information about each alias, appear in a list in the Alias tab of the Info Router
Client window.
NOTE: See Alias Tab (Info Router) for a detailed description of the Alias tab and the information it displays for each
alias.
1. Do one of the following:
208
System Configuration
209
Available Rules
Automatic Printing Sends each new image to be printed by the CARESTREAM PACS Client.
Backup Studies Backs up images according to the defined parameters and filters.
Compress Incoming Each new study that arrives is sent by Info Router to the compression server.
Study
Copy Incoming Images New images that meet the defined parameters and filters have arrived at the
To selected source device. Each image is copied one by one.
In addition, each line in the Monitor tab data list represents an individual image;
only complete studies are pushed to copy.
Copy Incoming Studies New studies that meet the defined parameters and filters have arrived at the
To selected source device. When a study storing process is completed is defined in
System Configuration --> Info Router --> General Parameters --> Timeout.
Create Structured New reports from the CARESTREAM PACS Client that meet the defined
Report parameters and filters have arrived at the selected source device. Multiple
structure reports are consolidated into one. An SR that includes the information
from the RIS and CARESTREAM PACS Client is created. The consolidated SR is
stored in the CARESTREAM PACS Workflow Manager. If a consolidated SR is
created, the unused SR from the CARESTREAM PACS Client is deleted.
Create Structured New reports that meet the defined parameters and filters have arrived at the
Report When RIS Msg selected source device. A Structured Report (SR) is generated immediately after
Arrives the radiology report is completed. It contains the radiology report, as well key
images and 3D processed images. The SR is stored in the Workflow Manager. If
no study yet exists, an SR is not created.
Create Structured The study has arrived to a report which already exists in the CARESTREAM PACS
Report When Study IS Link Software. An SR is created from both the study and the report.
Arrives
Custom Function The user can define both the Event Type and the Command Type that specifies
the action that is to take place when the event occurs.
When you select Custom Function, the Additional Events available are:
First/Additional Image Arrived and Generic Probe.
The First/Additional Image Arrived event enables you to execute the command as
soon as the first image arrives.
The Generic Probe Event applies only to advanced and internal use only.
E-Mail Report Sends an SR by email to the referring physician.
Enable Copy Copies images manually, according to the defined parameters and filters, and
copies accordingly.
Enable Push Pushes images from CARESTREAM PACS Client to the client local disk, according
to the defined parameters and filters, and copies accordingly.
Enable Storage A new study has arrived and the Study Status is set to Storing. When the storing
Completion Notification is complete, the Study Status changes to Unread.
Migrate Copies the studies to a different tier according to rules defined in the Life Cycle
Management. If the tier is local, the study is copied locally. If not, it is copied
using DICOM.
Migrate to CD If the CD Direct Suite is used as the secondary backup device, CARESTREAM
PACS Info Router uses this rule to migrate all studies to CD.
Pre-fetch from Near- Retrieves patient studies from offline storage, according to the defined
line Archive parameters and filters. Click Advanced to open the Advanced Options window.
Pre-load History Retrieves patient studies from offline storage, according to the defined
parameters and filters, and forwards them to the CARESTREAM PACS PACS
Client. Click Advanced to open the Advanced Options window.
SMA (Single Media If SMA is used as the primary backup, Info Router burns all the studies to SMA.
Archive)
Synchronize Study Tags Synchronizes the studies between the two computers.
Update DICOM tag New images that meet the defined parameters and filters have arrived at the
upon Image Arrival selected source device. The Info Router modifies the DICOM tags in the images
according to the configured request.
Update DICOM tag A new study that meets the defined parameters and filters has arrived at the
selected source device. The Info Router modifies the DICOM tags in the study
210
System Configuration
1. Click Add .
or
Right-click on the list of rules and select Insert Rule.
The New Rule Creation window appears.
2. In the Description field, enter a descriptive name to provide a clear description of the rule.
The filter applied to the rule appears in the Filter field at the bottom of the window.
3. Click Edit to create or modify the rule filter.
The Edit Filter window appears.
211
You can compose different filtering by matching particular criteria with an applicable condition and criteria details.
4. Click Edit.
The Filter Fields Editor appears.
5. Use the Add and Remove buttons to change the filters from the general list of available tags.
6. Click OK.
The Edit Filter window appears.
The Scheduling field displays the scheduling defined to the particular rule, including default scheduling parameters
defined during installation. Different functions have different scheduling parameters.
7. Click Edit to adjust the scheduling.
The Rule Scheduling Dialog window appears.
212
System Configuration
213
Custom Function
The Custom function enables the user either to compose a new combination of Event and Acton not available under
the predefined list of functions or to create a group command to allow the execution of sequential commands.
214
System Configuration
General Parameters
Parameters that are general for all rules appear under General Parameters. Parameters that are specific to certain
rules appear as a separate sub-entrance. General parameters include:
For each action type, it is possible to configure the maximum number of actions of this type that can run
simultaneously. In addition, there are a total (configurable) number of actions. This number sets the upper limit for
the number of actions that can run simultaneously regardless of the specific action type. For each action type, it is
possible to set its priority compared with other action types. The lower the number, the higher the priority.
For example, if Dynamic Copy has a priority of 30 and Manual Push has a priority of 60, then Dynamic Copy has a
higher priority than Manual Push and is executed first.
Actions not defined with an explicit priority have the priority that is defined in the configurable parameter of the
Default Command Priority. Priority between actions of the same name, such as several Dynamic Copy requests, is
assigned according to a first-in-first-executed order. It is possible to configure whether a specific action type should
be included in the Rules Configuration windows or not. The default should be set to false (the action is included).
Rules-Specific Windows
In addition to the General Parameters window, there are additional rules-specific windows.
Backup Parameters: lets you modify the default backup configuration parameters.
Pre-fetch Parameters: lets you modify the default pre-fetch configuration parameters.
Push to Users Parameters: lets you modify the default push to user configuration parameters.
Timeout Parameters: lets you modify the default timeout parameters.
215
Defining New Info Router Rules
1. From the System Configuration --> Info Router toolbar, click Add .
or
From the right-click drop-down menu, choose Add.
The New Rule Creation window appears.
216
System Configuration
217
Defining the Rule Filters
You can filter the instances of events that trigger a rule. For example, you can specify that only new images arriving
from a particular modality trigger that rule, or that only copy requests from a defined CARESTREAM PACS Client
trigger the rule.
1. Perform steps 1 through 3 of the procedure for defining the rule event.
2. From the list in the Criteria area, select the criterion by which you want to filter the event.
The possible values for the selected criterion appear in the Criterion Details area.
3. Select the filter condition from the Condition drop-down list (for example, is or is not).
4. From the list in the Criterion Details area, select the filter condition.
For example, if you select Head for the Body Part criterion, then only events involving head studies trigger the
rule.
5. Click Apply.
The filter criterion is applied and displayed in the Filter Expression area.
NOTE: The Apply button is only displayed in the Event tab. You must click Apply before you click OK to ensure that
the data entered in the Event tab is saved.
6. (Optional) Click And to define another criterion that must be met in order for the rule to be triggered,
or
Click Or to define an alternative criterion that must be met in order for the rule to be triggered.
The order of the calculation of the filter is always carried out from left to right.
7. If required, repeat steps 2 through 6 to define additional filter criteria.
8. If you wish to edit the list of Criteria in the middle pane of the screen, click Edit.
The Filter Fields Editor window appears. The list on the left side represents the full list of DICOM tags and/or HL-7
fields that can be added as criteria to filter the rule.
218
System Configuration
NOTE: The scheduling options are identical for all types of events.
2. From the On failure, retry every drop-down lists, define when the command is rerun in the event of a failure (any
combination of the options).
3. From the Continue retry within drop-down lists, define the period within which the command is retried in the event
of failure (any combination of the options).
4. The Delay option postpones the execution of a command. Click Delay and a further field opens to enter the time of
the delay.
5. Click OK.
The new rule is displayed in the Rule tab of the Info Router Client window and immediately begins operation.
219
Dynamic Filters
All the events in the CARESTREAM PACS Info Router may be filtered to satisfy special conditions. Each rule has its
own fixed list of filters, from which the user can choose.
There is a utility to use more filters, to actually filter by any DICOM tag existing in the study. To add a filter to the
CARESTREAM PACS Info Router, the user must add it directly to the Central Configuration to enable the CARESTREAM
PACS Info Router to obtain the required DICOM tag information. The filter is then added to the rule via the User
Interface. The probes that support the tag filters are:
New Study
New Image
Pre-fetch
RIS
The Info Router supports both standard and private tags.
Adding Filters to CARESTREAM PACS Info Router Rules
In the New Image or New Study Rule Creation window, click Edit in the Filter panel to display the list of DICOM
fields.
Rules with events related to RIS can also be dynamically filtered, similar to filtering the DICOM tags.
220
System Configuration
221
Life Cycle Management Configuration
Life Cycle Management allows the configuration for the automatic transfer of images from one storage tier to another
according to certain rules, including the time they are transferred and whether they are deleted.
222
System Configuration
Archive Configuration
The Archive Configuration window displays the storage available together with other statistics for each server. The
information is displayed in cylindrical format and shows both the High Water mark and Low Water mark levels of
storage space. You can configure the availability of servers and the percentages of storage space available for each
server. Clicking each server name displays details and statistics for that server.
223
Configuring Auto Delete
Since there is a finite amount of disk space on the servers, space must be cleared periodically by removing those
studies that are least likely to be required. The Auto Delete operates when the high watermark is reached. Images
are deleted until the percentage in the low watermark field is reached.
The watermark percentages are configurable and can be changed by clicking on the amount in the field and entering
a new number. If the watermarks are not defined in the Archive Configuration window, the default watermark
amounts are taken from the figures configured in the Auto Delete window.
Removing studies is managed by the Auto Delete process, which is governed by a set of configurable rules or
priorities, customized to meet each site's specific needs.
Using the arrows on the left side of the window allow you to set the priority of each object according to its order and
appearance on the list. Objects can be added, edited, or removed by clicking on the buttons on the right side of the
window.
224
System Configuration
Multi-tier Archiving
Multi-tier archiving has a user interface to allow easier configuration of life-cycle management rules. The user
interface lets you define which objects should be included in archiving rules, such as the entire study or specific
elements such as Key Images or SR, and the archiving policy for each object. This can also include how long the
object is stored in each tier, and to which tier it should be moved.
225
Long-Term Storage Manager (LTSM)
LTSM Overview
The Long-Term Storage Manager is the DICOM server that automatically and transparently manages the repository of
near-line and offline images, providing cost-effective storage management and archival and retrieval services. It
copies images from online disks (Online Storage Management storage) to automated storage media, and restores the
images back online as needed.
The Long-Term Storage Manager:
extends data protection by writing multiple copies to multiple removable media.
supports DICOM-3, supplying storage and retrieval services.
backs up and restores a nearly unlimited amount of data, with a lossless compression ratio of approximately 2:1.
can archive images from several Online Storage Management devices simultaneously and can manage several
storage devices (tape libraries).
uses a small online disk cache for holding studies that are to be stored on libraries compatible with and
supported by NetBackup software, as well as recently fetched studies.
manages the library cartridges in the system by automatically exporting cartridges to the mail slot (for example,
when the library is full).
imports requested cartridges from the mail slot.
The Long-Term Storage Manager can be installed either in a local configuration (on the same server on which the
Online Storage Management is running) or in a remote configuration (on a separate server).
NOTE: For a WINDOWS OS, the Long-Term Storage Manager can only be installed on a separate server.
226
Long-Term Storage Manager (LTSM)
Info Router Backup Rule
The diagram below illustrates the location of the CARESTREAM PACS Info Router backup rule in the flow of
information through the Workflow Manager:
The Info Router backup rule controls the migration of images from the online repositories to the RIS. When there are
images that must be backed up, the Info Router backup rule initiates a request to move DICOM data (image/study)
from the Online Storage Manager (WFM) location to the compatible RIS location.
When a new study is stored in one of the WFMs, the Info Router backup rule initiates a checking process to detect if
the study should be moved to the RIS. If the study is new, then the complete study is moved into the RIS that was
preconfigured to back up that specific WFM.
NOTE: The CARESTREAM PACS System can contain multiple RIS and WFM.
The migration process is triggered by a prescheduled, configurable timing schedule. The Info Router backup rule can
handle image migration from multiple WFM to multiple LTSMs.
NOTE: The Info Router backup rule process runs at prescheduled, configurable times.
227
Backup to Long-Term Storage (PreStore)
Backup to long-term storage is called the PreStore process. The PreStore process initiates prescheduled study
backups to DLT removable media (or any other media supported by NetBackup). The Long-Term Storage Manager
saves new images in a temporary online buffer (LTSMs cache) until the PreStore process copies the images to
permanent media. For every study, there are at least two copies in existence at all times.
Before the storage process begins, the system determines which of the studies need to be backed up, according to
the following criteria:
The arrival time of a study at the LTSMs. This parameter is used to prevent incomplete studies from being
stored.
Whether all of the study images reside in the LTSMs cache. If all of the images reside in the cache, the study is
listed for immediate backup. A second list is then created that includes all of the incomplete studies that must be
bound with new images before they can be stored. To minimize backup time, both lists are executed
simultaneously, so that every fetched study is immediately stored on removable media.
The PreStore operation automatically copies the images ready for long-term storage to a media volume from the
unused media pool in the library archive. If there is no new media available, the PreStore process halts and requests
a new media volume through the LTSMs Web interface.
After the PreStore process is completed, and if the system is configured to work without the mirroring feature, the
LTSMs cache is cleaned automatically.
228
Long-Term Storage Manager (LTSM)
Clone
After the PreStore process is completed, and if the system is configured to work with the mirroring feature, the Clone
process creates a second copy of the stored images on a different media volume.
NOTE: The Clone process is automatically generated after the PreStore process has been terminated.
When the Clone process takes place, both drives are used for duplicating the images. When only two drives exist in
the library, Fetch requests generated during the Clone process remain pending until the mirror process is complete.
For this reason, it is recommended to have more than two drives, to enable other operations to be executed in
parallel to the Clone process.
The Clone process can be performed either automatically by the system or manually by the system administrator. The
manual Clone option should be used when a Clone has not been created automatically. Refer to the NetBackup
Administrator Guide for information about performing a manual Clone.
NOTE: When the cartridge is full, it is recommended to switch it to the write protected state.
Shelf Management
The CARESTREAM PACS Workflow Manager assigns a Study Availability status to each study in the CARESTREAM
PACS System. This status is saved in the Workflow Manager database. This enables users to know at all times where
a particular study is located.
Online indicates that the study is located on the CARESTREAM PACS Workflow Manager where it can be accessed
quickly when needed. If the status is near-line or offline, the user knows the study must first be retrieved from
the tape library managed by the RIS.
Near-line indicates that the tape for the requested study is currently in the tape library.
Offline indicates that the tape is not in the library and manual intervention is required.
If studies are located offline, the user can cancel the request to retrieve the study if no one is available to load the
required tape in the library.
The Study Availability status of each study can be viewed in the Admin Tool as well as in the CARESTREAM PACS
Client.
The RIS Synchronizer is the automated process responsible for tracking the status of each study in the system. For
example, when a tape is taken from the library, the statuses of all the studies contained on the tape are changed to
online. If an offline tape is placed in the library, all the studies contained on the tape have their availability status
changed to near-line and so on. The RIS Synchronizer runs once a day, at 3:00 am.
VIParchive
The Versatile Intelligent Patient Archive (VIParchive) can be used as a Long-Term Storage Manager. When using the
VIParchive as the Long-Term Storage Manager, the Fetch from Offline and the Backup Rule work in the same way.
However, the implementation of the VIParchive is different since it is an external archive. Therefore, the procedures
detailed above regarding Pre-Store and Cloning are irrelevant when using the VIParchive.
When dealing with Shelf Management in the VIParchive, the status of a study is always displayed as near line.
229
Long-Term Failover Agent
The Failover Agent detects the failure or abnormal termination of the previously active Data Center and enables an
automatic switch over to a second Data Center. The Failover Agent is also be used where one Data Center may have
been taken down manually due to maintenance or service.
NOTE: At initial operation it is recommended to consult with a Carestream Health Service Representative.
UNIX
Action UNIX Command and Result
Identify if the Failover Agent has # /usr/tamar.root/scripts/failover_role – list
been installed on the system. Yes:
Role expected by 127.0.0.1:104 for node <role name>: <server
name>_active
No:
Roles provided by 127.0.0.1:104:
None
Identify if the Failover Agent is # /usr/tamar.root/scripts/failover – status
running on a satellite.
Yes:
failover service running: pid 5141
No:
failover service not running
Start the Failover. /usr/tamar.root/scripts/failover
Stop the Failover. /usr/tamar.root/scripts/failover – stop
View the Failover Log. /usr/tmp/failover.pl.log
MICROSOFT WINDOWS
Action MICROSOFT WINDOWS Command and Result
Identify if the Failover Agent has perl D:\Program Files\Kodak\System5\scripts\failover_role.pl -list
been installed on the system.
Identify if the Failover Agent is perl D:\Program Files\Kodak\System5\scripts\failover – status
running on a satellite.
Start the Failover. Start a WINDOWS service named "Imaginet Failover Service"
Stop the Failover. Stop the WINDOWS service "Imaginet Failover Service"
View the Failover Log. D:\Program Files\Kodak\System5\log\failover.pl.log
230
Long-Term Storage Manager Admin Tool
The Long-Term Storage Manager Admin Tool lets you monitor the Long-Term Storage Manager processes and
manage the Jukeboxes. The Long-Term Storage Manager Admin Tool also identifies and reports any malfunction in
the Long-Term Storage Manager processes and provides a variety of recovery tools.
231
Opening the Long-Term Storage Manager Admin Tool
The Long-Term Storage Manager Admin Tool can be accessed through the CARESTREAM PACS Admin Home Page
using a Web browser. This is similar to all other CARESTREAM PACS products, which are accessed through this central
location.
From a WINDOWS OS
1. Select Start --> Programs --> Carestream Solutions --> Admin --> Workflow Manager --> Jukebox Admin.
The LOGIN window appears.
NOTE: When you log in for the first time, you are prompted to change your password.
2. In the Login field, enter your assigned login name.
3. In the Password field, enter your assigned password.
4. Click OK to log in to the selected product.
232
Long-Term Storage Manager Admin Tool
Exit Lets you exit from the Long-Term Storage Manager Admin Tool and
return to the CARESTREAM PACS System Administration Home page.
233
Long-Term Storage Manager Admin Tool Menu Bar
Menu Option Description
File Refresh Lets you manually refresh the data that appears in the Recovered
Studies List area.
This option does not affect the Pending Requests area and the Event Log
area.
Exit Lets you exit from the Long-Term Storage Manager Admin Tool and
return to the CARESTREAM PACS Admin Home page.
Edit Settings Lets you configure the automatic refresh settings for the data that
appears in the Recovered Studies List area.
This option does not affect the Pending Requests area and the Event Log
area.
Tool Media Management Lets you access the Media Management window, where you can perform
functions such as generating reports, importing and exporting media to
and from the Jukebox, and so on.
Long-Term Storage Lets you run the Long-Term Storage Manager Backup process. A
Manager Backup confirmation message appears when the backup process is complete.
See Backup to Long-Term Storage.
Long-Term Storage Lets you run the Long-Term Storage Manager Auto Delete process. A
Manager Auto Delete confirmation message appears when the Long-Term Storage Manager
Auto Delete process is complete.
234
Long-Term Storage Manager Admin Tool
235
Recovered Studies List Area (LTSM)
The Recovered Studies List area displays the following data about each recently performed Fetch request.
Column/Field Description
Last Name The last name of the patient for whom the Fetch request was made.
First Name The first name of the patient for whom the Fetch request was made.
Fetch Status The status of the Fetch request, as follows:
IN_PROGRESS: The Fetch request was executed but not yet completed.
DONE: The Fetch request was completed successfully.
FAILED: The Fetch request failed.
Fetch Source The name of the computer from which the Fetch request was initiated.
Fetch Time The Fetch time, according to the Fetch status, as follows:
If the Fetch status is IN_PROGRESS, Fetch time displays the time when the
Fetch request was executed.
If the Fetch status is DONE or FAILED, Fetch time displays the time when the
execution of the Fetch request was completed.
NOTE: The data in the Pending Requests area can be filtered, sorted, and refreshed, as described in Managing the
Display (LTSM Admin Tool).
236
Long-Term Storage Manager Admin Tool
Column/Field Description
ReqID The NetBackup ID number for the request.
Barcode The bar code of the required media.
Operation The operation that is to be performed on the media. In most cases, the operation is
Read.
Time The time that the initial Fetch request was received.
Density The type of the media.
VolGroup The volume to which the media belongs, if applicable.
NOTE: The data in the Pending Requests area can be filtered, sorted, and refreshed, as described in Managing the
Display (LTSM Admin Tool).
237
Resubmitting Pending Requests
1. Import the appropriate media into the Jukebox, as described in Importing Media into the Jukebox.
2. In the Pending Requests area, select the request that you want to resubmit, right-click, and select Resubmit
Request.
If the correct media is found, the request is removed from the Pending Requests area, and the study status in the
Recovered Studies List area is changed to DONE.
If the correct media is not found, the request remains in the Pending Requests area and the study status remains
as IN_PROGRESS.
238
Long-Term Storage Manager Admin Tool
239
Event Log Area (LTSM)
The Event Log area displays progress and error messages for Long-Term Storage Manager processes, including
PreStore, Clone, and Auto Delete. The following information appears for each message
Column Description
Event The type of message (General or Error).
Message The content of the message (for example, Long-Term Storage Manager Clone on
Server PHIONA Started).
Date The date and time of the message.
The Long-Term Storage Manager Admin Tool window must be open while performing operations; otherwise, the event
log cannot receive the messages. Messages appear in the event log for a limited time. When the event log is full and
new messages must be displayed, old messages are deleted automatically. The data in the Event Log area can be
sorted, as described in Managing the Display (LTSM Admin Tool).
240
Long-Term Storage Manager Admin Tool
Option Description
Inventory Lets you generate an Inventory report.
Media List Lets you generate a Media List report.
Drive State Lets you generate a Drive State report.
Import Lets you import a cartridge into the Jukebox.
Export Lets you export a cartridge from the Jukebox.
Switch Lets you switch between the primary and secondary copy of a cartridge.
Clone This option is not functional in this version.
Clear Log Lets you clear the Results area of the Media Management window.
Close Lets you close the Media Management window and return to the Long-Term Storage
Manager Admin Tool window.
241
Using the Long-Term Storage Manager Admin Tool
This section contains detailed procedures for the available Long-Term Storage Manager Admin Tool operations, which
include:
Managing the Display
Running NetBackup Synchronizer
Generating an Inventory Report
Generating a Media List Report
Generating a Drive State Report
Importing Media into the Jukebox
Exporting Media from the Jukebox
Switching Media Cartridges
Clearing the Results Area of the Media Management Window
Exiting the Media Management Window
Clearing the Long-Term Storage Manager Admin Tool Event Log
Long-Term Storage Manager Admin Tool Toolbar
Long-Term Storage Manager Admin Tool Menu Bar
242
Long-Term Storage Manager Admin Tool
Symbol Description
First Sort Ascending
From the Long-Term Storage Manager Admin Tool toolbar, click Display Settings .
From the Edit menu, select Settings.
The Update Settings window appears.
2. Select the Automatic Refresh check box to activate the automatic refresh feature.
3. In the Refresh Interval field, select/enter the refresh interval in seconds.
243
4. Click OK to apply the settings.
From the Long-Term Storage Manager Admin Tool toolbar, click Refresh .
or
From the File menu, select Refresh.
The currently displayed data in the Recovered Studies List area is updated and displayed according to the latest
information in the archive.
244
Long-Term Storage Manager Admin Tool
245
Generating an Inventory Report (LTSM Admin Tool)
An Inventory report lets you view the current contents of the Jukebox, and indicates if there is a lack of
synchronization between the physical contents of the Jukebox and the recorded contents of the Jukebox.
For example, if there is a problem with a cartridge not being read by the Jukebox, you can re-run the Inventory
report so that the cartridge can be recognized by the Jukebox.
If a lack of synchronization is detected, import the appropriate cartridge into the Jukebox, as described in Importing
Media into the Jukebox, then regenerate the Inventory report to ensure that the mismatch has been corrected.
1. Do one of the following:
From the Long-Term Storage Manager Admin Tool toolbar, click Media Management .
From the Tool menu, select Media Management.
The Media Management window appears.
2. In the Reports pane, click Inventory.
The Inventory report appears in the Results area. The Inventory report includes the following information for each
slot in the Jukebox.
Column Description
Slot The number of the slot in the Jukebox.
Robot Tape Indicates whether a cartridge is physically in the slot in the Jukebox or if it was removed.
Contents The bar code of the cartridge in the slot, if any.
Barcode
Volume Media ID The NetBackup ID for the cartridge in the slot, if any.
Configuration A configurable bar code for the cartridge found in the slot, if any. This bar code can
Barcode include additional prefixes or suffixes that are not included in the actual bar code on the
cartridge.
Mismatch Indicates if a synchronization problem was detected for the slot.
Detected
246
Long-Term Storage Manager Admin Tool
From the Long-Term Storage Manager Admin Tool toolbar, click Media Management .
From the Tool menu, select Media Management.
The Media Management window appears.
2. In the Reports pane, click Media List.
The Media List report appears in the Results area. The Media List report includes the following information for each
media volume.
Column Description
Media Pool The name of the media pool to which the volume belongs.
This information appears in the body of the report rather than as a separate column.
Each volume is then listed under the appropriate Media Pool name.
Media ID The media identification number that was assigned to the volume when it was added to
the system.
Media Type The type of the media volume.
Robot # The identification number of the Jukebox in which the volume is stored.
Robot Slot The slot in the Jukebox in which the volume is stored.
Side/Face The side of the media on which the volume is stored (for example 1/2).
Ret Level The retention for the backups on this volume.
The retention level is an integer between 0 (one week) and 9 (infinity).
Size KBytes The total number of kilobytes stored on this volume.
Status The volume status:
Active: The volume is currently in use.
Available: The volume is available for use.
Suspended: The volume is not used for backups until the retention periods for all
backups on it have expired.
Frozen: The volume is no longer in use for backups.
Full: The volume is full and cannot store additional backups.
Expired: All backups on the volume are expired.
Imported: The backups on the volume were imported.
247
Generating a Drive State Report (LTSM Admin Tool)
A Drive State report lets you view all pending requests, as well as monitor the status of each of the drives. Additional
drive information, such as the type of the drive and the drive name, also appears.
1. Do one of the following:
From the Long-Term Storage Manager Admin Tool toolbar, click Media Management .
From the Tool menu, select Media Management.
The Media Management window appears.
2. In the Reports pane, click Drive State.
The Drive State report appears in the Results area. The Drive Status portion of the Drive State report includes the
following information:
Column Description
Drv The drive number
Type The drive type
Control The type of control used for the drive
User The user running the drive report
Label The current machine label
RVSN Not relevant
EVSN Not relevant
Ready The current drive status (ready or is busy)
Wr. Enbl. Indicates whether the drive is write-enabled or not
ReqID The NetBackup ID number
248
Long-Term Storage Manager Admin Tool
From the Long-Term Storage Manager Admin Tool toolbar, click Media Management .
From the Tool menu, select Media Management.
The Media Management window appears.
3. In the Operations pane, click Import.
The Import Media window appears.
4. Click OK.
The cartridge is taken into the Jukebox and stored in a system-assigned slot.
NOTE: To ensure that the cartridge was successfully imported into the Jukebox, generate an inventory report.
249
Exporting Media from the Jukebox (LTSM Admin Tool)
You can remove a cartridge from the Jukebox when the Jukebox is full.
1. Do one of the following:
From the Long-Term Storage Manager Admin Tool toolbar, click Media Management .
From the Tool menu, select Media Management.
The Media Management window appears.
2. In the Operations pane, click Export.
The Export Message window appears.
3. Enter the identification number of the cartridge you want to remove from the Jukebox.
4. Click OK.
The cartridge is placed in the mail slot and can be removed. If the requested cartridge cannot be found, an error
message appears.
250
Long-Term Storage Manager Admin Tool
From the Long-Term Storage Manager Admin Tool toolbar, click Media Management .
From the Tool menu, select Media Management.
The Media Management window appears.
2. In the Operations pane, click Switch.
The Switch Message window appears.
3. Enter the identification number of the corrupted cartridge and click OK.
The system retrieves the secondary copy of the cartridge and uses it to replace the corrupted primary copy.
251
Clearing the Results Area of the Media Management Window (LTSM)
You can manually clear the data displayed in the Results area of the Media Management window.
In the Operations pane of the Media Management window, click Clear Log.
The Results area of the Media Management window appears blank.
252
Long-Term Storage Manager Admin Tool
From the Long-Term Storage Manager Admin Tool toolbar, click Clear Admin Reports .
The data in the Event Log area of the Long-Term Storage Manager Admin Tool window is cleared. See Event Log
Area for more information.
253
Email Suite
CARESTREAM PACS Email Suite Overview
The CARESTREAM PACS Email Suite offers automatic e-mail distribution to referring physicians. These e-mail
messages are generated immediately after the radiology report is completed, and contain the radiology report, as
well key images and 3D processed images.
All confidential information is encrypted and can only be accessed by the referring physician by providing a password.
When opened, the e-mail attachment appears.
The Email Suite offers automatic e-mail distribution by combining the power of IS Link and Info Router to create an e-
mail message that contains key images marked on the PACS Client and the report received from the RIS. The Email
Suite sends encrypted e-mails to selected referring physicians, with a link back to the complete study, if required.
NOTE: The images and tools provided by the Email Suite are intended as aids for the competent user only.
254
Email Suite
Mail Component
The mail component takes from the SR the MHTML page containing the report and sends the email to the relevant
referring physician. The email address of the referring physician is retrieved from the Central Configuration.
The mail encryption (DES-128 standard) and signing are performed using ALIROO PRIVAWALL, a third-party software
application.
255
Opening the Email Suite Configuration Tool
1. In your browser, type the address (URL) of the server and press Enter.
You are connected to the local server.
2. Click Administration.
The CARESTREAM PACS Admin home page appears.
3. Click Email Suite.
The Enter Network Password window appears.
4. In the Login field, enter your login name.
5. In the Password field, enter your password.
6. Click OK.
The Email Suite Configuration Tool window appears.
7. Configure the Email Suite parameters in each tab.
8. After configuring the Email Suite parameters, click OK to save the configuration and exit from the Email Suite
Configuration Tool window.
256
Email Suite
257
Email Suite Configuration Message Body Tab
The Message Body tab lets you set the text that is included in the body of the email along with the radiologist’s
report.
1. In the Email Suite Configuration Tool window, select the Message Body tab.
2. In the Message Body Text area, type the text you want to appear in the body of the emails.
NOTE: The text can include a field, indicated by a hash mark (#) before and after the field name. When generating an
email, the Email Suite automatically retrieves the relevant value from the report.
258
Email Suite
259
Restarting the Server
Once the Email Suite parameters are all configured, the server must be stopped and restarted. This is performed
remotely.
260
CD Direct
CARESTREAM PACS CD Direct Suite Overview
The CARESTREAM PACS CD Direct Suite allows you to create media discs (CDs or DVDs) containing image data.
If the CARESTREAM PACS IS Link Software is installed on your system, you can also burn (copy) radiology reports to
the CD. The CD contains the original uncompressed DICOM image data along with a viewer, which allows anyone with
a PC to view the images.
All CD Direct Suite operations, including configuration of the system and monitoring burn requests, are performed
from the CD Direct Suite Queue Manager window.
Components
The CD Direct Suite comprises the software and hardware, including the CD Manager Server and a CD burner,
necessary to produce CDs that contain image data.
CD Manager Server–the CD Manager Server includes a DICOM server that allows the CD Direct Suite to receive
images through a DICOM copy or move command issued from an external DICOM device. The CD Manager Suite
prepares the content for each media disc (CD or DVD), including reports, DICOM DIR, DICOM Viewer, JPEG Lossy
presentation of the images, and HTML page for quick viewing of the Lossy images.
CD Burner–the CD Direct Suite uses a CD burner (a RIMAGE CD publishing system or another CD burner set up with
your system). If you use a RIMAGE CD publishing system, you can print patient information on the face of the CDs
(see the RIMAGE CD publishing system user guide for information about printing).
Features
Cost-effective
Eliminates the need for handling patient films.
Creates CDs without the fear of ruining image data.
Provides hospitals with the option to give CDs to referring physicians.
Provides referring physicians with the option to give patients CDs or the option to keep CDs for their own
records.
Ability to burn reports to a CD.
Burns CDs in DICOM part 10 format (removable media).
NOTE: The CD Direct Viewer is not intended for primary diagnostic viewing. See the user documentation for the
CARESTREAM PACS CD Direct Suite for more information.
For information about defining the CD Direct Suite configuration parameters, see this topic:
Setting CD Direct Configuration Parameters
261
Setting CD Direct Configuration Parameters
To access the CD Direct Suite configuration options:
Click the Options icon of the CD Direct Queue Manager toolbar or select the Tools --> Options and select the desired
tab.
Production Parameters
Parameter Description
Summary CD When there are multiple CDs in a single task, check this box to create a JPEG
representation of the contents of the CDs as a complementary summary CD.
Auto Burn Check to burn a disc automatically after all images are received.
Burn Viewer Check to burn a DICOM Viewer Application with the DICOM images. Uncheck to
burn only the DICOM images.
Local Burner Check to burn to a local CD burner instead of the RIMAGE CD burner.
Media Selects CD-R or DVD-R media.
Printing Prints the labels on the disc in relation to the angle of the marker. Aligned
printing is available only with the RIMAGE printer.
Smart Burning Mode Check Smart Burning Mode to force the system to wait for the entire study before
beginning the burn process. Selecting this option avoids splitting studies and
series over multiple CDs.
Directories Parameters
These parameters specify the destination directories for the stages of the burning process.
Labels Parameters
These parameters define the data that appears on the CD label if you are using a RIMAGE CD burner and printer. The
order of the fields in the dialog box determines the order in which the labels are printed on the disc. Number of
Studies, Study Date, and Study Modality are printed by default for each study.
Application Parameters
Parameter Description
Institution Name Specifies the name of the institution.
Timeout Specifies the time that the CD Direct Suite waits from receipt of the last image by
the server until the server recognizes that the copying process is complete.
Wait for Report(s) If Wait For Report is checked, a burn task without a report is not started until CD
Direct receives the report is received or until the report timeout elapses. CD
Direct checks for reports at the Report Refresh Interval.
Burn With History Check Burn With History to burn the patient’s history. Specify the number of
studies to retrieve from the Patient History.
System Parameters
Parameter Description
Auto Delete Specifies if burned studies are automatically deleted from the hard disk.
Media Specifies the size of the media on which information is burned.
Priorities Parameters
You can set different priorities for tasks from specific users or referring physicians. Use Add, Edit, Delete, or change
the position of an entry.
262
CD Direct
Supported Configurations
1. CD Direct remote mode: Install CD Direct on a dedicated workstation in a WFM environment.
2. Windows WFM with CD Direct:
CD Direct installation is part of the windows WDM installation procedures. The product is always installed, A
service is added and is running (Imaginet CDDirect service).
When a license is not present for CD Direct, the CD Direct Windows service is still started but non-functional. CD
Direct logs indicate that there is no license to run CD Direct.
263
CD-Direct Auto-Delete
A scheduled task, cd_direct_auto_delete, runs nightly on the CD Direct workstation to clear CD Direct temporary
folders.
CD Direct Auto-Delete deletes all data of completed or cancelled tasks that passed the delete criteria:
264
CD Direct
265
with a link to the external report on the CD's main
HTML page.
Options -->System Tab Auto Delete: Lets you specify when burned studies
are automatically deleted from the hard disk.
CD/DVD/BD-R Capacity: The size of the media upon
which information is burned.
Media ID Prefix (optional): Enter any alphanumeric
character.
Number of Copies: Lets you specify the number of
copies of each media to burn.
Options -->Priority Tab Lets you set higher priorities for tasks received by
specific users or referring physicians. You can add,
edit, delete or change the position of each entry.
Options -->Archive Tab Lets you configure the options for Archive Mode.
266
Privacy and Security Management
HIPAA Security Regulations
CARESTREAM PACS provides health care organizations with the infrastructure and tools necessary to facilitate full
compliance with the Health Insurance Portability and Accountability Act (HIPAA) of 1996. Towards that end, the
system provides these organizations with a suite of security mechanisms to ensure the highest standards of patient
confidentiality, in accordance with HIPAA regulations. These mechanisms work together to make the system a
“privacy-enabled” system. A subset of HIPAA security regulations defines five areas where measures must be taken to
ensure patient confidentiality, as follows:
Authentication
HIPAA requires health care organizations to have strict controls on which users can access confidential patient
information. CARESTREAM PACS features the User Management Admin Tool, which manages the login mechanism
that serves as the entry point to all system applications and tools. It centralizes all user management functions,
enabling you to define permissions and settings at the user, group, and system levels.
Authorization
Maintaining strict control over the type of access these authenticated users have is just as important as regulating
who has access to confidential PHI (protected health information).
CARESTREAM PACS features the Access Control Management Tool, which ensures that users can view only the
Workflow Manager data that they are authorized to view. Access control is performed by setting restrictions at the
user, group, or node level, providing both role-based and context-based protection. Restrictions can be configured for
different data types, according to any DICOM criteria.
The Access Control Management Tool works in conjunction with the User Management Admin Tool to provide
comprehensive protection of patient confidentiality.
Auditing
HIPAA regulations require an auditing system against unauthorized users that penetrate the first two levels of access
control: authentication and authorization.
The auditing function in the Workflow Manager logs every PHI task or operation stored in the system, such as
accessing information, editing, and deleting. Each logged event can include: the operation performed, the user who
performed it, the location from which it occurred, and the information affected.
The auditing function permits security administrators to monitor system activity for suspicious behavior including
authorized users accessing patient data for which they have no need to know and to trace the origins of any action
that occurred in the system.
NOTE: For more information, see Auditing.
Data Protection
HIPAA regulations apply to data that is transmitted within health care organizations within a secure domain (using
firewalls), as well as over the Internet.
The system supports encryption of all data passing through the system using a variety of common protocols (for
example, SSL) and includes an integrity mechanism to ensure that data was not tampered with during transit.
Different encryption mechanisms can be configured for different clients to allow maximum flexibility.
In addition, the CARESTREAM PACS System uses the ALIROO PRIVAWALL Server, a secure email server that
automatically applies end-to-end, rule-based encryption to any email and attached files routed through the email.
Several different protection schemes, such as certificate-based S/MIME encryption/decryption and self-decrypting
symmetric messages, are supported.
Disaster Recovery
HIPAA regulations require that health care organizations have the ability to recover confidential patient data from any
situation caused by hardware or software failures.
The Workflow Manager implements a multi-layered solution that includes full and incremental data backups to offline
storage as well as hot/cold server backups in cases of hardware failures. All image data is automatically cloned to
secondary media, which can be removed from the system library and stored in a secure location.
NOTE: Contact Customer Service for more information about the Workflow Manager’s backup features.
267
Security Policy
Carestream Health, Inc. has established and complies with an internal security policy that applies to its Health Group
products, imaging services, and repair services that are privacy-enabled. “Privacy-enabled” is Carestream Health
Inc.'s term to identify products and services that enforce its security policy via design features or specific procedures
to be followed during development, operation, or maintenance of Carestream Health products.
Under this policy, Carestream Health, Inc. has undertaken to do the following:
Provide privacy-enabled products with the following privacy and security features:
o User identification and authentication of the claimed identity
o Controlled access to product functions, including those that allow access to patient-identifiable information
o Security audit logging to enforce individual accountability of access to sensitive data and system resources
o System integrity mechanisms to guard against unauthorized changes to data or software applications
o Identify a set of Customer Security Obligations that describe the duties and responsibilities of users in order to
gain maximum benefit from the privacy-enabled features built-into Carestream Health products.
These Customer Security Obligations are listed in Customer Security Obligations. Carestream Health, Inc. will
verify and document the understanding and acceptance of these obligations via a contractual agreement.
Ensure that Carestream Health, Inc. service personnel understand and commit to their security-related
responsibilities when providing service for privacy-enabled Carestream Health, Inc. products. This is
accomplished via service training, and a signed acknowledgment by service personnel.
Provide service user identification and authentication prior to allowing access to privacy-enabled Carestream
Health, Inc. products.
Provide proper and secure product installation. This is accomplished by the service technician following standard
Carestream Health, Inc. approved procedures for installation.
268
Privacy and Security Management
Hazard Caution
Operational Privacy-enabled Carestream Health, Inc. products must be operated and maintained
Environment within a controlled customer environment.
Software Changes Because customers are not authorized to add to or modify software supplied by
Carestream Health, Inc. without written permission of Carestream Health, Inc.
Carestream Health, Inc. is not responsible for security lapses or violations due to the
introduction of unauthorized software.
Privacy and Security The enterprise in which privacy-enabled Carestream Health, Inc. products are
Policy of the User's installed has developed approved policies and procedures for protecting the privacy of
Enterprise any Protected Health Information (PHI) it may collect or generate, for obtaining
proper authorization and consent for its collection and use, and for patient access to
its PHI for appropriate review and revision.
The enterprise is responsible for overall conformance to its privacy and security
policies and procedures.
Clearance Individuals, including members of the Carestream Health, Inc. workforce such as
maintainers, to whom the Security Administrator (SA) grants unescorted or electronic
access to privacy-enabled Carestream Health, Inc. products that may contain PHI,
have completed any required training on the privacy and security policies and
procedures of the enterprise in which the products are installed.
Use Training Individuals granted unescorted access to privacy-enabled Carestream Health, Inc.
Agreement products that may contain PHI have acknowledged their responsibilities for protecting
the privacy of any PHI to which they may gain access in accordance with the privacy
and security policies and procedures of the institution in which the products are
installed.
Permission to User accounts for privacy-enabled Carestream Health, Inc. products are only granted
Operate Products by the SA to individuals who are cleared and who have completed their user training
agreement.
Operation of Privacy-enabled Carestream Health, Inc. products must be operated in accordance
Products with operating instructions and user manuals provided by Carestream Health.
Need-to-Know The identity of individuals with clearance to PHI, but who do not have need-to-know
for all PHI a privacy-enabled Carestream Health, Inc. product may contain, is known
by the SA so that the SA can properly set access authorizations.
Protection of PHI The customer must protect PHI released in hardcopy form, which includes hardcopy
Released as images, and human-readable reports from privacy-enabled Carestream Health, Inc.
Hardcopy products from compromise of its confidentiality in accordance with the approved
privacy protection policies and procedures of the enterprise in which the hardcopy is
produced.
Security of Networks provided by a customer to interconnect its privacy-enabled Carestream
Customer Networks Health, Inc. products contain the necessary features to protect any PHI carried
therein in accordance with the privacy protection policies and procedures of the
enterprise.
SA Reaction to The SA has the responsibility to be aware of the security status of its network and of
Security-Relevant the devices the network interconnects, and if the SA becomes aware of a problem,
Events has an obligation to react. Failure to react may result in improper behavior of
Carestream Health equipment.
Input from Other Data transmitted on an approved data interface that is not authorized to contain PHI,
Systems from any source to a privacy-enabled Carestream Health, Inc. product, must never
contain PHI.
NOTE: The Carestream Health, Inc. product does not treat data received on these
interfaces as if the data contained PHI.
269
Configuration Customers must maintain control over the topology of the privacy-enabled
Control During Carestream Health, Inc. products installed within their enterprise, including data
Operation and interfaces and software versions. Customers must use the interfaces and our
Maintenance products for the purpose for which they were designed and in a configuration that has
been approved by Carestream Health, Inc.
270
Privacy and Security Management
271
Security Manager
The Security Manager is a system-wide application that controls the various permissions, access restrictions, and
other permission-based features of all products in the CARESTREAM PACS System, including configuration and
administration tools. The system is built using the principles described below.
Group A group is an entity containing users and is attached to a specific profile. A group contains a
set of parameters such as Display Protocols in CARESTREAM PACS Client or specific security
settings, etc.
Profile A profile describes the functions a user has after logging in to the CARESTREAM PACS Client.
A profile contains a list of features (similar to licensing). Sites cannot edit the contents of a
profile. One group can only belong to one profile. However, several different groups can
belong to the same profile.
For example: Group A belongs to one specific profile (Profile A). Group B also belongs to one
specific profile (Profile A). Users of both groups have the same set of basic features (and user
interface) when they log on to the system. However, each group has its own set of
permissions.
A feature is a licensed permission, is not configurable, and represents a function in the
system.
Permissions The permissions to perform certain operations or view certain data are controlled by the
Security Manager and managed by the UM. Permissions are attached by default to a specific
group. Permissions can also be configured on a user level. Each group has a specific set of
permissions with a 1:1 ratio (one set of permissions is available for one group and vice
versa).
The same theory applies to users. For example, a user belonging to a group automatically
inherits the group’s permissions. If a specific permission is added or removed from the user,
the user has a specific set of permissions.
You can configure permissions on a system, group, or user level. Each level overrides the
preceding level.
Certain permissions are dependent upon features. If a user does not have the feature in the
profile to which the user is attached, the permission is not available to the user.
The permissions mechanism must read the profile content and allow configuring permissions
for the relevant features in the profile and changing the permissions. Features that are not in
a specific profile do not appear in the User Management at all.
Permissions Certain features of the system are included as part of the profile definition and require
and Profiles permission controls. The permissions mechanism allows configuring or changing permissions
for the relevant features in the profile. Features that are not in a specific profile do not
appear in the Security Manager. Most sites have more than one profile, so the permissions
mechanism must be able to read the profile that is relevant for a specific user or group.
272
Privacy and Security Management
273
Security Manager Permissions Settings
The system is installed with several default permission settings.
Setting Description
System These settings are automatically applied to any user defined in the Administrators
Administrator group.
Radiologist These settings are automatically applied to any user defined in the Radiologists group.
Web These settings are automatically applied to any user defined in the MS_Users group.
Mammography If you are defined as a Group Administrator, the user receives the relevant settings for
the group the user belongs to and also receives an additional permission to add, edit,
and delete users from that group.
If a new group is defined in the system, it inherits the System Level Permission
Settings. Alternatively, if a new group is created by copying an existing group, it
inherits the permission settings of the original group.
If a new user is defined in the system, you inherit the permission settings of the group
to which the new user belongs.
Temporary User These settings are automatically applied to any user defined as a temporary user in
the system.
If you are defined as a Group Administrator, the user receives the relevant settings for
the group the user belongs to and also receives an additional permission to add, edit,
and delete users from that group.
If you are defined as a Group Operator, you receive the relevant settings for the group
that the user belongs to and also receive an additional permission to reset the
password of a user.
If you are defined as a Service User, you receive the permission settings of the
administrators group.
If a new group is defined in the system, it inherits the System Level Permission
Settings. Alternatively, if a new group is created by copying an existing group, it
inherits the permission settings of the original group.
If a new user is defined in the system, you inherit the permission settings of the group
to which the new user belongs.
274
Privacy and Security Management
Encryption
NOTE: This section is not used for the CARESTREAM PACS Standalone Workstation.
Encryption is the process of transforming information so it is unintelligible to anyone but the intended recipient. This
is done by using encryption mechanisms, editing configuration files, and good security practices.
The CARESTREAM PACS Workflow Manager can be configured to use encryption and to support the Secure Sockets
Layer (SSL) protocol for encrypted communication. Using SSL, the CARESTREAM PACS Workflow Manager uses the
following ports for communication. These ports must be open at the firewall to let CARESTREAM PACS Workflow
Manager clients use the application.
24466: CARESTREAM PACS Workflow Manager client-server connection
24444: Push client-server connection
25511: Push Sender Server (Workflow Manager client connection)
24477: Conference Server (Workflow Manager client connection)
443: Web server port for https
NOTE: Port 80 is still used when the applet is downloaded via SSL (port 443). It must also be open on the firewall,
even when using SSL.
All connections via ports in the 2xxxx range are over SSL and are encrypted. Demographic and image data is always
transferred using port 24466 while administrative information is transferred using the other ports.
NOTE: View the topics listed under User Management Admin Tool (Group) and under User Management Admin Tool
(User) for information about configuring the use of SSL.
The CARESTREAM PACS Workflow Manager installation includes the APACHE Web server (version 1.3.22/6) with SSL
support using the modSSL package. To activate https, a valid certificate should be purchased from a Certified
Authority (CA) company such as VeriSign or Thawte.
275
NOTE: By default, all networks are considered external, so SSL is enabled for every user, which affects performance.
It is recommended that internal networks that are sufficiently secure be configured not to use SSL. The “xx.xx.xx”
and “yy.yy” entries are examples of subnet address formats. They are ignored by the system and may be removed.
Encryption
NOTE: This section is not used for the CARESTREAM PACS Standalone Workstation.
Encryption is the process of transforming information so it is unintelligible to anyone but the intended recipient. This
is done by using encryption mechanisms, editing configuration files, and good security practices.
The CARESTREAM PACS Workflow Manager can be configured to use encryption and to support the Secure Sockets
Layer (SSL) protocol for encrypted communication. Using SSL, the Workflow Manager uses the following ports for
communication. These ports need to be open at the firewall to let Workflow Manager clients use the application.
24466: CARESTREAM PACS Workflow Manager client-server connection
24444: Push client-server connection
25511: Push Sender Server (Workflow Manager client connection)
24477: Conference Server (Workflow Manager client connection)
443: Web server port for https
NOTE: Port 80 is still used when the applet is downloaded via SSL (port 443). It must also be open on the firewall,
even when using SSL.
All connections via ports in the 2xxxx range are over SSL and are encrypted. Demographic and image data is always
transferred using port 24466 while administrative information is transferred using the other ports.
NOTE: View the topics listed under User Management Admin Tool (Group) and under User Management Admin Tool
(User) for information about configuring the use of SSL.
The Workflow Manager installation includes the APACHE Web server (version 1.3.22/6) with SSL support using the
modSSL package. To activate https, a valid certificate should be purchased from a Certified Authority (CA) company
such as VeriSign or Thawte.
276
Privacy and Security Management
NOTE: By default, all networks are considered external, so SSL is enabled for every user, which affects performance.
It is recommended that internal networks that are sufficiently secure be configured not to use SSL. The “xx.xx.xx”
and “yy.yy” entries are examples of subnet address formats. They are ignored by the system and may be removed.
Field Description
Country Name Enter a two-letter code.
Example: US
State or Province Name Enter the full name of the state or province.
Example: California
Locality Name Enter the name of your locale, such as a city.
Example: Los Angeles
Organization Name Enter the name of your company.
Example: Carestream Health, Inc.
Organizational Unit Name Enter the name of a specific group.
Example: Information Technology
Common Name Enter the domain name of your server.
When running the create_key_csr_for_apache.scr script, use the fully qualified
host name (i.e., hostname.domainname. This entry must be identical to the
name used in the URL.
For example, if the host name is medi172 and the domain is
us.carestreamhealth.com, then the Common Name should be
medi172.us.carestreamhealth.com and the URL to the Web Client is
https://medi172.us.carestreamhealth.com/.
CAUTION: If the Common Name in the certificate differs from the fully
qualified server name in the URL, the browser displays a warning.
Moreover, service user access (which is exclusively via SSL) may be
impossible.
If the domain name is not entered here, an error message appears
saying that the name on the security certificate does not match the
name of the site.
277
/usr/tamar.root/server_root/conf/ssl.key/server.key
/usr/tamar.root/server_root/conf/ssl.csr/server.csr
/usr/tamar.root/server_root/conf/ssl.crt/server.crt
The new key and temporary certificate are used as soon as the server is restarted. The temporary certificate is self-
signed and valid for 10 years. As soon as the real certificate from the CA is received, copy this certificate to overwrite
the temporary certificate /usr/tamar.root/server_root/conf/ssl.crt/server.crt.
The private key should be placed in crt/usr/tamar.root/server_root/conf/ssl.key/server.key.
To restart the server, make sure that no users, including diagnostic users, are using the system (their sessions will be
aborted without warning). Also, modalities should not send images to the system during a restart (any DICOM
associations will fail).
Restart the server by rebooting the entire server (cannot be done using the administration tool). Login as root and
type the following:
/etc/rc2.d /S99MediSurf stop
/etc/rc2.d /S99MediSurf start
NOTE: The new key and certificate should be tested to ensure that the parameters, such as Common Name, are
correct before submitting the Certificate Signing Request to the CA.
CAUTION: The Security Administrator should make a secure off-line backup copy of the private key file
and keep this copy in a physically safe place. A service user should never be allowed to make copies of
this key, since this key is private to the customer and any unauthorized copying would compromise the
key (and require revocation of the certificate and going through the process of generating a new key and
buying a new certificate).
278
Privacy and Security Management
279
General Security Practices
Some good practices include:
Limiting physical access to the Workflow Manager application server.
Setting up firewalls.
Limiting access to administration capabilities.
Managing passwords.
Limiting the presence of other applications on the server.
Configuring for protected and unprotected servers.
Only specifically identified and controlled administrative and service users should be given a login account email
that allows direct UNIX access to the server and then only with the minimum privileges necessary to perform the
required tasks.
280
Privacy and Security Management
281
Changing Default ORACLE Passwords (WINDOWS OS)
The system contains two database instances: mst1 for all clinical data and rc01 for backup and recovery. Each
database has built-in accounts, sys and system. You can change the passwords for these accounts.
1. Type:
C:\Program Files\Carestream Solutions\System5\scripts\
DB_change_system_ts.pl
2. Enter Y to verify that you want to change the administration password.
3. Enter the old password.
4. Enter the new password.
5. Enter the new password again.
6. Click session_timeouts in the Central Configuration Editor left pane.
NOTE: You can override this parameter for each application by moving the session_timeouts sub-tree under each
application separately.
7. Configure the following parameters.
minutes_to_lock_application: Sets time in minutes to blank screen.
minutes_to_logout_application: Sets time in minutes to log out of the Workflow Manager.
session_timeout_enabled: Set to True to enable session timeout parameters.
NOTE: Be sure to set the minutes_to_lock_application threshold time to a shorter value than the
minutes_to_logout_application threshold time, so that the application screen blanks before logging out the user.
Carestream Health, Inc. recommends setting the log out time to 30 minutes or less.
282
Privacy and Security Management
Privacy Notice
Users can click the Privacy Notice link on the Login window to view a privacy notice. The notice can be edited to
conform to the privacy policy for your specific organization by editing the privacy_notice parameter via the Central
Configuration utility.
Right-click the privacy text in the Central Configuration Editor right pane to display the text for editing.
Configuring Permissions
The permissions settings are accessed from the System/Group/User window in the User Management application.
1. From the User Admin Management window, choose the User or Group tab.
2. From the displayed list, double-click the name of the User or Group to be edited or configured.
Depending on the group chosen, the group name appears at the top of the screen.
3. Click Group Permissions.
The Group --> Group Name --> Permissions Settings window appears. The categories are listed in the left pane.
Export Data Permissions
Update Data Permissions
Reading Flow Permissions
Folder Creation / Deletion Permissions
DP Creation Permissions
URL & Action Buttons
Access Permissions to Foreign Archives
Application Access Permissions
Application Settings Permissions
CD Monitoring Permissions
User Management Permissions
NOTE: The CARESTREAM PACS CD Direct Suite permissions allow you to access the CD-Direct Web Monitoring
interface, view users’ burn requests in queue, and update the user’s burn requests.
System Configuration includes the System Configuration entry on the admin page and all the tools that are available
through it.
System Administration includes all the tools under the System Administration entry on the admin page, excluding
Central Configuration.
System Monitoring includes all the tools under the System Monitoring entry on the admin page.
4. Click OK when all configurations are done.
5. If you want to restore defaults, click Restore to Defaults.
283
Applicable Permissions
The following permissions are controlled through the Security Manager.
Setting Description
Update Data Permission to edit patient and study details. Should apply to any update of
patient and study details, both in the Archive Explorer (editable fields) and in
the Administrator tool (update, merge/split, RIS Sync, etc.).
Lets the user delete images and reports. Should apply to deletion being
performed from the CARESTREAM PACS Client or from the Administrator tool.
Access to Foreign Permission to access, save, copy, and/or delete images from any of the remote
Archives servers that are configured.
(View/Write/Delete)
Print Images Permission to print images to a network printer or a DICOM printer.
URL and Action Button Permission to change a study after the URL activation was invoked (launch
Permissions Archive Explorer and select a different study).
NOTE: The permission to allow URL activation is included under the Application
Access Permissions.
Permission to activate a specific Action button that is configured on site (for
example, the ORTHOVIEW action button triggering the integration with the
ORTHOVIEW application).
View Reports Permission to view reports. If this permission is not given, the R or O icons in
the Patient Mini-Archive are disabled and the Reports button in the Archive
Explorer or the Viewer is disabled.
By default, this permission is applied to any user defined in the Radiologists
group.
Reading Permissions This permission allows a user/group reading permissions (the ability to move
studies from one status to another within the system when clicking on Done),
together with the ability to lock a study.
If permission is not granted, the user returns to the Archive Explorer when
clicking Done and does not receive the Done dialog box.
By default, this permission is applied to any user defined in the Radiologists
group. If this permission is given, the relevant workflow is configured for the
particular group/user.
Mark Key Images Permission to mark images as key images. Only users with reading permissions
can be assigned with the Mark Key Images permission.
By default, this permission is applied to any user defined in the Radiologists
group.
NOTE: The permission to mark key images does not necessarily mean that the
284
Privacy and Security Management
user has Save As permissions. Users who do not have permission to Save
Images to Server can still mark key images.
Dictate Report Permission to dictate a report. Only users with reading permissions can be
assigned the Dictate Report Permission.
By default, this permission is applied to any user that is defined in the
Radiologists group.
Save Reports Permission to save reports that have been automatically generated in
CARESTREAM PACS applications such as Calcium Scoring and Vessel Analysis.
Only users with reading permissions can be assigned the Save Reports
permission.
By default, this permission is applied to any user defined in the Radiologists
group.
Create Sticky Notes Levels of permission for Sticky Notes:
Only view Sticky Notes
View and add Sticky Notes (no editing)
Edit and delete user's own Sticky Notes
Edit and delete other users’ Sticky Notes
Teaching Files Levels of permission for Teaching Files:
View a Teaching File
View and insert a study into the Teaching File
Change the content of a Teaching File (view/add/edit)
View/add/edit/delete a teaching file
Edit the Teaching File form
Access Control Rules Similar to the Access Control rules currently in existence in the CARESTREAM
PACS.
Query Permissions controls whether a user or group can query certain locations.
This capability is in the general Security Manager application and can be applied
at group level (the permission to add/edit/delete users in your group or at
system level).
Resetting Users' Permission to reset user passwords. This capability is inherent today based on
Permissions the role of the user such as System Operator or Group Operator.
This capability is in the general Security Manager application and can be applied
at group level (the permission to reset users’ passwords in your group or at
system level).
Editing Users' Permission to edit permissions. This capability is inherent based on the role of
Permissions the user (System Operator or Group Operator).
This capability is in the general Security Manager application can be applied at
group level (the permission to grant users’ permission in your group or at
system level).
285
Security Manager Service Configuration
Session Timeout
If the server receives no communication from the client within a configurable amount of time, the session is closed
and all resources, such as licenses, are released.
To configure the Session Timeout:
1. In the Central Configuration select imagint --> system --> applications --> securitymanager --> preferences>
login_idle_time.
2. Change the value to the desired time in minutes (default 60).
286
RIS-PACS Synchronization
The RIS-PACS synchronization process ensures that the patient details and ordering information in the PACS are up to
date and synchronized with that in the RIS.
When a patient registers at the RIS or HIS, the patient’s details are entered into the database and an order is issued
with the relevant procedure to perform. These details are then sent to the PACS via an HL-7 interface and stored in
the CARESTREAM PACS IS Link Software.
After the scan is performed at the modality, the technician reenters the patient details and the body part(s)
examined. As these details are manually entered, there is the risk that a typographical error or a missing field may
cause this data to be different from that sent by the RIS. These details are saved in the imaging study created by the
modality and stored in the CARESTREAM PACS Workflow Manager.
The RIS-PACS synchronization process ensures that the details are the same in the RIS and in the PACS, and that the
patient attributes stored in the Workflow Manager contain the most up-to-date details from the hospital records. If
there are differences, the information in the RIS is used to update the information stored in the PACS, such as in the
Workflow Manager.
RIS-PACS synchronization occurs whenever a study is stored in the Workflow Manager or an event takes place in the
RIS.
287
Events in the RIS
The RIS notifies the CARESTREAM PACS System about relevant events via an HL-7 interface with the CARESTREAM
PACS IS Link Software, which forwards the notification to the Workflow Manager.
NOTE: The RIS-PACS synchronization triggered by RIS events can be enabled or disabled according to the
configuration. For more information, contact Customer Service.
The CARESTREAM PACS Workflow Manager is notified whenever:
Patient details are updated
Whenever a patient is added to the RIS or the patient’s details are updated, the CARESTREAM PACS Workflow
Manager is notified. The CARESTREAM PACS Workflow Manager searches its database for details on that patient
according to the Patient ID. If the patient is found, the attributes are overridden by the updated attributes in the
RIS.
The attributes that can be overridden are:
o Patient Name
o Birth Date
o Sex
Patient details are merged
Whenever two sets of details for one patient are merged in the RIS, the CARESTREAM PACS Workflow Manager is
notified. The patient details are then merged in the CARESTREAM PACS Workflow Manager as well.
NOTE: For more information about merging patient data, see Patient Matching.
A new report is created
Whenever a report is created in the RIS, the CARESTREAM PACS Workflow Manager is notified. The Has report
column is updated to Yes.
If the CARESTREAM PACS Workflow Manager has a related study, it updates the study status to READ. This
removes studies from the UNREAD worklist that were not read using CARESTREAM PACS Client.
Order details are changed
Whenever the details of an order, such as the date of a scan, are changed, the CARESTREAM PACS Workflow
Manager is notified.
A patient is admitted to the hospital
Whenever a patient registers at the hospital, the Workflow Manager is notified.
288
RIS-PACS Synchronization
Multiple Studies
You can perform a manual RIS-Sync for multiple studies.
1. Choose the studies on which you will perform the manual RIS-Sync.
RIS-PACS Log
Whenever there is a change in one or more attributes due to the RIS-PACS synchronization process, the old values
and the updated values are logged in the Audit Trail log. The log can be viewed using the Audit Trail Viewer, as
described in Defining Audit Event Settings.
Pre-Fetch
The Pre-Fetch process ensures smart retrieval of studies from the Long-Term Storage Manager server to the Online
Storage Management server.
The Pre-Fetch uses preconfigured rules to automatically decide which studies must be brought online and when,
based on data received from the HIS. The list of studies is then sent to the Info Router, which issues the request to
move the studies from the Long-Term Storage Manager server to the Online Storage Management server, thereby
enabling fast image retrieval. For example, the RIS notifies the Workflow Manager when a patient enters the system.
Pre-Fetch can then retrieve any images related to the patient that are stored on tape and bring them back online for
easy access. Pre-Fetch works in two stages:
Decides when the data should be brought online
Decides which data should be brought online
Both stages are controlled by a configurable list of patterns and rules.
Pre-Fetch streamlines the lengthy process of study retrieval from the Long-Term Storage Manager server by
retrieving the studies in advance, when possible, at times when there is less demand on server resources.
The diagram below illustrates the stages of the Pre-Fetch process
289
Three different types of Pre-Fetch can be performed:
Daily Pre-Fetch: In this instance, the CARESTREAM PACS IS Link Software informs the Workflow Manager when
there is an order for a scan to be performed or when a patient is admitted to the facility.
The details of the scan (for example, the body part to be scanned) are supplied to the Workflow Manager, if
available. Based on this information, the appropriate studies are brought online before the new scan is performed.
In order for Daily Pre-Fetch to work effectively:
o The CARESTREAM PACS IS Link Software must be installed at the facility.
o The CARESTREAM PACS IS Link Software must be able to communicate with the facility’s RIS server.
o The Info Router must be installed at the facility.
o A computerized, online scan scheduling system must be used diligently.
o Late Pre-Fetch: In this instance, the Workflow Manager receives images from an AE and queries the server for
the patient’s history.
This type of Pre-Fetch process is useful when there is no internal information system at the facility, or in case of
an emergency when there is no opportunity to retrieve the patient’s history in advance.
Night Pre-Fetch: In this instance, the CARESTREAM PACS IS Link Software informs the Workflow Manager that a
patient is scheduled to come in for a specific scan.
The details of the scan (for example, the body part to be scanned) are supplied to the CARESTREAM PACS
Workflow Manager, if available. Based on this information, the appropriate studies are brought online the night
before the patient arrives at the facility.
In order for Night Pre-Fetch to work effectively:
o The CARESTREAM PACS IS Link Software must be installed at the facility.
o The CARESTREAM PACS IS Link Software must be able to communicate with the facility’s RIS and HIS
servers.
o The Info Router must be installed at the facility.
o A computerized, online scan scheduling system must be used diligently.
290
RIS-PACS Synchronization
JPEG Compression
Compression of the images is the function of the Online Storage Manager. The manner in which images are effectively
stored reduces storage space and traffic on the network.
The compression of the images to be stored can be performed in three different ways.
Compressed: Using JPEG / JPEG2000 compression, the user can decide how much loss to introduce and balance
file size and image quality.
NOTE: This is only available for use in states that allow picture processing using this method.
Lossless Compression: With Lossless Compression it is possible to use JPEG / JPEG2000 / RICE compression.
Every piece of data that was originally in the file remains after the file is uncompressed. All of the information is
completely restored.
Lossy Compression Factor: Lossy Compression reduces a file by permanently eliminating certain information,
especially redundant information. When the file is uncompressed, only part of the original information is still
there (although the user may not notice it).
Each Online Storage Manager can be separately defined to store images in a different compression mode. In addition,
it is possible to define more detailed policies to choose a particular compression method according to the source AE or
even modality. The compression is determined at the time that the image is stored.
NOTE: The Lossy Compression Factor controls the amount of compression. When the value is high, the file is more
compressed. When the value is low, the file is less compressed.
291
Study Grouping
Study grouping is a method for ensuring that study details are always attached to the correct group, based on their
unique ID. Study grouping can be performed using the data in the Workflow Manager or using data stored in the
hospital RIS server.
Icons
Each image received by the CARESTREAM PACS Workflow Manager is saved together with an icon of the image saved.
This allows the user to view several images on screen without having to see the full detailed image. This is also
relevant particularly for the Patient Mini-Archive.
292
Maintenance (UNIX)
293
WFM Licensing Status Monitoring for Both Operating Systems
The new monitoring tools track the license status in terms of volumes and counters of total exams in the systems.
The tool adds a simple notification to help you ensure that the license terms are adhered to. The data collection is
carried out in a non-disruptive manner to the system stability and performance.
You are notified when a license violation has occurred.
A warning notification appears on the Admin Tool home page, in either the logs or in the Dashboard.
Important: The warning does not interfere with system operation. You must contact a Carestream Health
representative to check or renew the license.
The red warning message is a link. Click on the link to display the Licenses Log which details the license errors:
Each line states whether that type of license has a violation (or an error in the check). The percentage values
quantify the amount of violation from the licensed amount.
The most common license type for Archive (IMS) or a PACS is the EXAMS_YR counter, which measures the amount of
studies that enter the system annually.
294
Maintenance (UNIX)
Database Analysis
This phase rearranges the database statistics after the Online Storage Management Auto Delete process has deleted a
large amount of data from the database to optimize performance.
1. Log in as root.
2. Ensure that the Editor environment variable is set appropriately (for example: vi).
3. Type:
crontab –e
4. Press Enter.
The crontab schedule file appears in the default editor.
5. Locate the line that contains db_worker.pl.
This is the script that runs DB Worker, which resides under /usr/tamar.root/scripts.
The first two numbers on the line indicate the time in minutes and hours (24-hour clock), respectively, when the
daily Online Storage Management Auto Delete process is performed.
For example: 0 4 * * * perl /usr/tamar.root/scripts/mst_db_worker.pl
The above line represents an Online Storage Management Auto Delete process scheduled for 4:00 am every day.
6. Edit the timing parameters according to the required scheduling.
7. Save the file.
NOTE: Refer to crontab documentation for information about crontab scheduling options. Crontab documentation can
be found online using the man crontab command.
295
Running a System Check (UNIX)
You can run a script on the Online Storage Management server that causes the system to perform a complete system
check. This system check performs all the routine maintenance checks to ensure that there are no problems with any
of the Workflow Manager components. The script should be run every day and must be run from the root user. If
there are any problems, a report is generated listing the problems.
The system check indicates errors, but does not fix them. In case a problem is found during the system check, you
must perform the relevant manual procedure to correct it. See Performing Routine Maintenance for more information.
System Uptime The system has been up for less than three days. This
check is performed in order to check for unexpected
system reboots.
Database Utilization A tablespace is more than 85% full.
Database Extents A table or index contains more than 450 extents.
Database Connections There are more than 200 open connections to the
database.
Database Analyze More than 48 hours have elapsed since the last
database analysis.
Database Log Errors in the ORACLE ALERT log.
Number of Running DICOM There are more than 25 DICOM servers running at a
Servers time.
Jukebox Backups There are studies older than 48 hours that have not yet
been backed up.
Long-Term Storage Manager The Long-Term Storage Manager cache exceeds a
Cache Utilization certain limit.
Pre-Fetch Contact Customer Service for further instructions.
Application Check There is an application problem with the Info Router
Software, CARESTREAM PACS IS Link Software, or RIS
Reports.
Application Log There are SQL and image storing errors in the
application log.
All the fields are configurable, and can be changed by editing using the following command:
/usr/tamar.root/scripts/system_check_params
296
Maintenance (UNIX)
297
Root Account E-mail (UNIX)
Each time a scheduled job is executed, a message is delivered to the inbox of the root mail account. These messages
provide a summary of what the process did, and the status (successfully completed or failed).
These messages should be checked on a daily basis.
1. Log in as root.
2. Type:
mailx
3. Press Enter.
NOTE: For more information about the mailx program, type man mailx.
298
Maintenance (UNIX)
299
Verifying the Workflow Manager Daily Backup (UNIX)
1. Type: ls -ltr ~oracle/admin/mst1/cdump/
2. Press Enter.
3. Type: ls -ltr ~oracle/admin/rc01/cdump/
4. Press Enter.
You should locate the log files created during the previous backup and verify that the procedure was successful.
If OK appears in the backup filename, the backup was successful.
If ERR appears in the backup filename, an error occurred. Contact Customer Service.
300
Maintenance (UNIX)
Next time you inspect the alert log, type tail +<n> <filename>. This shows all lines starting with line number n.
When everything is OK, count and record the number of lines again.
3. Locate the past week’s dates and review the messages.
Only informative messages are acceptable. For example: startup, shutdown, and changing log files.
(Thread 1 advanced to log sequence)
If an error exists, contact Customer Service.
301
Database Fitness Verification (UNIX)
The CARESTREAM PACS Workflow Manager has a built-in log file that lists messages concerning database fitness. A
checkup process scans the databases and verifies that each metadata set (header) in the mst1 database corresponds
to an existing image in the Image File System. The checkup process results are written into the Workflow Manager
TAMAR_LOG file.
When the process is done, review the log file in order to identify potential problems.
You should invoke periodic database fitness verification processes at least once a week.
1. Log in as ms user.
2. Type:
source ~oracle/.oracleenv /export/home/tamar.root/db_admin
3. Press Enter.
4. Type:
/usr/tamar.root/bin/db_sync [ delete or log_only]
5. Press Enter.
In case any image files are missing from the Image File System, the db_sync program updates the database to
reflect that those images are no longer present.
If there are no other copies of those images (such as in Long-Term Storage Manager), the database no longer has
any knowledge of them. If still possible, the images must be re-sent by the original source.
NOTE: Under normal circumstances, this situation should never arise (the Auto Delete process updates the database
in a consistent way). If any database updates are reported in the TAMAR_LOG file, save a copy of the TAMAR_LOG file
and contact Customer Service.
The process may take several minutes, depending on the size of the database. When the process is complete,
review the Workflow Manager’s general log. For example: type vi /usr/tmp/TAMAR_LOG.
6. Locate the relevant date.
A problem is indicated in a format similar to the following example.
May 6 18:15:24 phiona FIR [21260]: 4 FIR_DbSync.C (967):
FIR_DbSync: Image /fir_fs_01/000/000/000/002/2/2/17.img does not reside on fir1 and should be deleted.
302
Maintenance (UNIX)
303
Online Storage Management General (UNIX)
When the system is restarted, following either a failure or an invoked operation, such as installation, upgrade, or
restructuring, you must ensure that all of its components are functioning properly. The Online Storage Management
general fitness check should be performed manually after every boot.
When the system is up, the following processes should be running:
CARESTREAM PACS Workflow Manager database processes (mst1)
CARESTREAM PACS Workflow Manager backup management database processes (rc01)
ORACLE Listener process (tnslsnr)
On an idle system, there are a small number of oraclemst1 (LOCAL=NO) processes even if no users are logged
in. For users of diagnostic clients, there may be up to 12 of these processes running.
304
Maintenance (UNIX)
305
PreStore Backup Verification (UNIX)
The Workflow Manager PreStore process is scheduled to back up the daily new studies to Long-Term Storage
Manager. This procedure is performed automatically according to a preconfigured schedule, usually at 12:00 am.
You should verify that the PreStore backup operation was successfully completed.
The Workflow Manager PreStore process should be performed manually when there is a related problem reported by
the system check.
1. Type:
cat /usr/tmp/TAMAR_LOG | grep -i prestore
2. Press Enter.
3. Locate the log messages created by the PreStore process during the previous backup and verify a successful
procedure.
4. Check the following NetBackup log files for errors.
/var/tmp/mst_sir_NB_catalog_backup_run.log
/export/home/tamar.root/bin
/mst_sir_prestore_run.log/export/home
/tamar.root/bin/mst_sir_clone_run.log/export
/home/tamar.root/bin
/mst_sir_auto_delete_run.log
/export/home/tamar.root/bin
/mst_sir_sync_run.log/var/tmp
/mst_sir_NB_catalog_backup_run.log/var
/tmp/TAMAR_LOG/tmp/sir_study_list/tmp
/algotec_class_restore_log/tmp
/algotec_class_backup_log/tmp
/algotec_class_clone.log
5. Check these files using NetBackup's Administrator tool. To start the tool, type:
# cd /disk02/openv/netbackup/bin ./jnbSA
6. When the VERITAS NetBackup login window appears, type the root password.
7. From the VERITAS NetBackup DataCenter, select Activity Monitor.
For more information about using NetBackup, see the VERITAS NetBackup documentation.
If an error exists, contact Customer Service.
306
Maintenance (UNIX)
307
Long-Term Storage Manager General Fitness Check (UNIX)
When the Long-Term Storage Manager server is restarted, following either a failure or an invoked operation such as
installation, upgrade, or restructuring, you must ensure that all its components are functioning properly.
The Long-Term Storage Manager general fitness check should be performed manually after every Long-Term Storage
Manager server boot.
NOTE: Whenever there is a reboot of the Online Storage Management, also perform a reboot for the Long-Term
Storage Manager.
When the Long-Term Storage Manager server is up, these processes should be running:
MVSMain process
SVSIR processes
Router process
Monitor router (connecting the Jukebox monitor router to the database)
308
Maintenance (UNIX)
309
Moving Audit Logs to Offline Storage (UNIX)
NOTE: The user names and passwords referred to in this topic are ORACLE Database user names and passwords.
Before performing this procedure, contact Customer Service to obtain this information.
310
Maintenance (UNIX)
311
Using the VCS Cluster Manager to Monitor the Cluster (UNIX)
From the Cluster Manager windows, you can determine the status and health of the cluster, bring clusters online and
offline, perform failovers, and add or delete cluster resources.
The first window that appears after you log on to Cluster Manager is the Cluster Monitor window. Use Cluster Monitor
to log on and off the cluster, view summary information about the cluster, and exit Cluster Manager.
312
Maintenance (UNIX)
Delete Cluster File --> Delete Cluster Removes a cluster panel from the
Cluster Monitor.
313
Cluster Monitor Panels
The Cluster Monitor contains two panels, each of which provides information about one of the clusters.
The left pane of each panel contains three buttons representing the status of:
Service Groups
Systems
Heartbeats
The right pane of the cluster panel provides summary status information about the cluster.
314
Maintenance (UNIX)
Service Groups: Shows the service groups in the cluster. When expanded, the service groups show the
group’s resource types and resources.
The following colors and symbols indicate the status of the cluster:
A red slash in the panel indicates at least one object is faulted and no objects are online.
A yellow slash indicates at least one object is faulted and one object is online.
A gray object is offline.
A locked icon indicates the object is frozen.
315
Cluster Explorer Toolbar (UNIX)
The Cluster Explorer toolbar provides access to cluster operations, which are described in the following table.
NOTE: Depending upon your logon privileges, some of the buttons may be grayed out and, therefore, inaccessible.
Manage Systems for a Service Group Displays the System Manager dialog box.
Online Service Group Displays the Online Service Group dialog box.
Offline Service Group Displays the Offline Service Group dialog box.
316
Maintenance (UNIX)
317
Monitoring the Cluster Status (UNIX)
1. From the Cluster Explorer, click a cluster in the configuration tree.
2. In the View Panel, select the Status tab to open the Cluster Explorer - Status view.
3. Use the Status View to monitor the status of a cluster, system, service group, resource type, and resource.
318
Maintenance (UNIX)
319
Monitoring the Cluster Service Groups (UNIX)
1. From the Cluster Explorer, click a cluster in the configuration tree.
2. In the View panel, select the Service Groups tab to open the Cluster Explorer - Service Groups view.
3. Use the graph in this view to monitor the dependencies between service groups.
The line between grp_ora and grp_imaginet represents a dependency. Because it is a red line, it is a firm
dependency. This means that grp_ora must be online before grp_imaginet is brought online and that grp_imaginet
is automatically taken offline if grp_ora faults.
320
Maintenance (UNIX)
321
Monitoring the Cluster Heartbeat (UNIX)
1. From Cluster Explorer, click a cluster in the configuration tree.
2. In the View panel, select the Heartbeat tab to open the Cluster Explorer - Heartbeat view.
3. Use the Heartbeat view to monitor the system links and disk group heartbeats.
4. Move the cursor over the system icons to display pop-up windows with information about the links and disk group
heartbeats.
The priority number indicates the failover sequence, with 1 denoting the first system to start after a failover.
4. Click Next.
5. On the Notifier Options dialog box:
a. Specify the path for the Notifier resource. Click ... to view the default pathname and to edit the attribute at a
local or global system level.
b. Choose the mode of notification that must be configured. Click the check boxes to configure SNMP and/or
SMTP (if applicable).
6. On the SNMP Configuration dialog box (if applicable):
a. Click + to create the appropriate number of fields for the SNMP consoles and severity levels. Click - to
remove a field.
b. Enter the console and click the severity level in the drop-down list box. For example, “snmpserv” and
Information.
c. Enter the SNMP trap port. 162 is the default value.
7. Click Next.
8. On the SMTP Configuration dialog box (if applicable):
a. Enter the name of the SMTP server.
b. Click + to create the appropriate number of fields for recipients of the notification and severity levels. Click -
to remove a field.
c. Enter the recipient and click the severity level in the drop-down list box.
9. Click Next.
10. On the NIC Resource Configuration dialog box:
a. Click Do not configure NIC Resource (if applicable), click Next, and proceed to the next step.
or
If you configure the NIC resource (as recommended by VCS), proceed to substep b.
b. Enter the name of the resource.
c. Click the ... in the Discover column of the table to find the MAC Address for each system.
d. Click OK in the Discover dialog box.
11. Click Next.
12. Click Bring the Notifier Resource Online if desired.
13. Click Next.
14. Click Finish.
Engine Log
The engine log is located at /var/VRTSvcs/log/engine_A.log.
The format of an engine log messages is:
TAG | Date (yy/mm/dd) | Time | Product | Message ID | Message
The following is a typical engine log entry:
TAG_C 2001/12/03 18:54:58 VCS:10075:building from remote system.
323
Agent Log
The agent log is located at $VCS_HOME/log/agent_A.log. The format of agent log messages is:
TAG | Date (yy/mm/dd) | Time | Product | Message ID | Agent Type |Resource Name | Entry Point | Message
The following is a typical agent log entry:
TAG_C 2001/12/03 19:40:01 VCS:254001:Oracle:oracle1:online:One or more attributes contain invalid values.
All tag entries are written to the engine and agent logs. Tag A and B entries are also written to the system log, which
can be viewed at _____________.
324
Maintenance (UNIX)
325
VCS Environmental Variables (UNIX)
The following variables are used to configure common VCS processes.
326
Maintenance (UNIX)
Task Command
Start VCS cold (on each node). /opt/VRTSvcs/bin/hastart
Start VCS cold and accept system as valid (on /opt/VRTSvcs/bin/hastart -force
each node).
Stop VCS gracefully (on each node). /opt/VRTSvcs/bin/hastop -local
Stop VCS and leave resources online. /opt/VRTSvcs/hastop -local -force
Stop VCS on all systems and leave groups online. /opt/VRTSvcs/hastop -all -force
Watch VCS logs. tail -f /var/VRTSvcs/log/engine.log_A
Force a halt/reboot to perform a failover. /sbin/gabsync;sync;halt
or
/sbin/gabsync;sync;reboot
Locate Configuration File. /etc/VRTSvcs/conf/config
Locate Main config. /etc/VRTSvcs/conf/config/main.cf
Included files. types.cf
Modify resource while VCS is running (CLI). Open configuration:
/opt/VRTSvcs/bin/haconf -makerw
Modify Resource:
/opt/VRTSvcs/bin/hares -modify <resource> <attribute>
<value>
Close Configuration:
/opt/VRTSvcs/bin/haconf -dump -makero
Modify resource while VCS is running (GUI). In the Cluster Explorer, select Open Config from the Cluster
menu.
Select the resource to modify and look at the attributes view.
Push the little e button in the upper right corner of the
attributes view.
Select the attribute to change.
Enter the new value in the small box.
From the edit menu, select Set. The change should be
reflected in the attribute view.
In the Cluster Explorer, select Close Config from the Cluster
menu.
Directing SNMP Traps. Open configuration:
/opt/VRTSvcs/bin/haconf -makerw
Change the SNMP IP to <IP Address>
/opt/VRTSvcs/bin/hasnmp -modify IPAddr <IP Address>
Dump the configuration and make read only:
/opt/VRTSvcs/bin/haconf -dump -makero
Clearing resource failure. /opt/VRTSvcs/bin/hares -clear <resource> -sys <system>
NOTE: You should clear faults because when a resource faults, it stops the onlining of all dependencies (e.g., Oracle
does not online if a diskgroup faults). To attempt a new onlining, you must clear the faults on the resource first.
Online a group. /opt/VRTSvcs/bin/hagrp -online <group> -sys <sys>
View summary status. /opt/VRTSvcs/bin/hastatus -summary
View tailing status. /opt/VRTSvcs/bin/hastatus
View system’s node name. uname -n
Confirm that the configuration is closed. # /opt/VRTSvcs/bin/haconf -dump -makero
Look for the FAULTED status of a service group. # /opt/VRTSvcs/bin/hasys -display
Look for the FAULTED status of a system. # /opt/VRTSvcs/bin/hasys -display
Review logs. /var/adm/messages
/var/VRTSvcs/log/*
327
Preserving Cartridges
To ensure a longer life for full or new cartridges, store cartridges in a clean environment and follow these
recommendations:
Do not drop or bang the cartridge. This can displace the tape leader, making the cartridge unusable and possibly
damaging the drive.
Store the data cartridge in the plastic shipping enclosure.
Do not expose tape cartridges to direct sunlight and other heat sources.
If the cartridge has been exposed to extreme heat or cold, stabilize the cartridge at room temperature for the
same amount of time it was exposed (up to 24 hours).
Place the identification label in the slide-in slot on the front of the cartridge only.
Do not attach labels anywhere on the cartridge except in the slide-in slot.
328
Maintenance (UNIX)
329
Maintenance (WINDOWS OS)
330
Maintenance (WINDOWS OS)
Important: The warning does not interfere with system operation. You must contact a Carestream Health
representative to check or renew the license.
The red warning message is a link. Click on the link to display the Licenses Log which details the license errors:
Each line states whether that type of license has a violation (or an error in the check). The percentage values
quantify the amount of violation from the licensed amount.
The most common license type for Archive (IMS) or a PACS is the EXAMS_YR counter, which measures the amount of
studies that enter the system annually.
331
Running a System Check (WINDOWS OS)
You can run a script on the Online Storage Management server that causes the system to perform a complete system
check. This system check performs all the routine maintenance checks to ensure that there are no problems with any
of the Workflow Manager components. The script should be run every day and must be run from the root user. When
there are any problems, a report is generated listing the problems.
The system check script runs as a scheduled task every day at 0600. It creates the following log:
IMAGINET_ROOT\log\system_checks\system_check_<current date>.log
The system check indicates errors, but does not fix them. In case a problem is found during the system check, you
must perform the appropriate manual procedure to correct it. See Performing Routine Maintenance for more
information.
System Uptime The system has been up for less than three days. This
check is performed in order to check for unexpected
system reboots.
Database Utilization A tablespace is more than 85% full.
Database Extents A table or index contains more than 450 extents.
Database Connections There are more than 200 open connections to the
database.
Database Analyze More than 48 hours have elapsed since the last
database analysis.
Number of Running DICOM There are more than 25 DICOM servers running at a
Servers time.
Jukebox Backups There are studies older than 48 hours that have not yet
been backed up.
Long-Term Storage Manager The Long-Term Storage Manager cache exceeds a
Cache Utilization certain limit.
Pre-Fetch Contact Customer Service for further instructions.
All the fields are configurable, and can be accessed for editing using the following command:
C:\Program Files\Carestream Solutions\System5\scripts\system_check_params
332
Maintenance (WINDOWS OS)
Supported Options
Option Use to:
log_file specify a log filename (instead of the default)
db_name specify another database name (instead of the default mstore)
min_percent specify the minimum free space to cause enlargement (instead of the default
of 15)
add_percent specify the enlargement percentage (instead of the default of 20)
tablespace_name specify one or more tablespaces separated by a comma (the default is all
tablespaces)
enlarge_to_min_free_mb allow enlargement to a minimum of free MB in the tablespace(s)
enlarge_to_min_free_percent allow enlargement to a minimum of free MB in the tablespace(s)
333
Performing Routine Maintenance
The following table describes a list of checks that are additional to the system check or must be performed manually
in cases where there is an error reported by the system check
334
Maintenance (WINDOWS OS)
Hot Backup
During a hot backup, the database is not down and users can continue to work without interruption. The hot backup
procedure creates log files under the log directory: IMAGINET_ROOT\log.
The backup log files are named backup_<type>.<dbname>.log where
type = inc for the full backup and al for an archive log
dbname = the name of the database instance: mst1 or rc01
The actual backup files and the last backup log files are stored under the IMAGINET_BACKUP_ROOT directory. Only
the last successful backup is kept.
Cold Backup
During a cold backup, the database is shut down and users are unable to work until the backup is complete. The
default method is a full backup, which runs every night in two phases:
Full backup: the scheduled task db_backup_inc runs at 2 am.
Archive log backup: the scheduled task db_backup_al runs each night at 5 am.
A log file is created under the ImagiNet log directory IMAGINET_ROOT\log\backup.log. The actual backup files are
stored in the IMAGINET_BACKUP_ROOT directory. Depending on the amount of available disk space, either the last
one or two successful backups are saved.
NOTE: You should copy the database backups to separate media, so they can be recovered in case of a disk failure.
Full or partial restoration of a database from backup can only be done by Customer Service. Any attempt by
unqualified personnel may result in permanent loss of patient data and/or general system malfunction.
335
Verifying the Workflow Manager Daily Backup (WINDOWS OS)
The system check script runs as a scheduled task everyday at 6 am.
1. Select Start --> Settings --> Control Panel --> Scheduled Tasks.
2. Right-click Open.
3. For the desired scheduled task db_backup, db_backup_inc, or db_backup_al, check that the time in the Last Run
Time column is compatible with today’s date.
4. Use Notepad or WordPad to open the log file in IMAGINET_ROOT\log.
If an error exists, contact Customer Service.
336
Maintenance (WINDOWS OS)
Only informative messages are acceptable. For example: startup, shutdown, and changing log files.
(Thread 1 advanced to log sequence)
If an error exists, contact Customer Service.
337
Moving Audit Logs to Offline Storage (WINDOWS OS)
NOTE: The user names and passwords referred to in this topic are ORACLE Database user names and passwords.
Before performing this procedure, contact Customer Service to obtain this information.
338
Maintenance (WINDOWS OS)
Pass/Fail Criteria From the Scheduled Tasks window, verify the following:
Last Results (for all tasks) must be 0X0.
Any other result is an error.
Last Run Time to verify the last time that the check was run.
Verify that there are no errors in the log files.
The log files are in C:\Program File\Carestream Solutions\System
5\TEMP.
339
Daily Task: ORACLE Alert Files (WINDOWS OS)
Check Description Checking the ORACLE Software Alert File.
1. Using Notepad or WordPad, open the ORACLE Software Alert File
iC:\Program File\Carestream Solutions\System
5\admin\mst1\bdump\alert_mst.log.
2. Scroll down to the last section of the file.
3. Locate the past week’s dates and review the messages.
Only informative messages are acceptable, for example, startup,
shutdown, and changing log files.
(Thread 1 advanced to log sequence)
340
Maintenance (WINDOWS OS)
341
Weekly Task: Event Viewer (WINDOWS OS)
Check Description Check the WINDOWS System Event Viewer for any RAID messages.
Pass/Fail Criteria Make sure that no errors exist in the System Event Viewer regarding the RAID.
Error Handling Contact vendor support.
Contact Customer Service.
Pass/Fail Criteria From the Scheduled Tasks window, verify the following:
Last Results for EMBackup DB Normal to TAPE must be 0X0. Any
other result is an error.
Verify that the backup completed without any errors.
Error Handling Contact Customer Service.
342
Maintenance (WINDOWS OS)
Pass/Fail Criteria From the Scheduled Tasks window, verify the following:
Last Results for EMBackup Images INC to TAPE must be 0X0. Any
other result is an error.
Verify that the backup completed without any errors.
Error Handling Contact Customer Service.
343
Programming the Bar Code Scanner
NOTE: You must use the correct symbol (s) to program the scanner.
1. Select FCN 3 in the Control column of the B-Coder Professional Screen.
The system generates the correct code to program the scanner. For example, 128.
2. You can enter information in the comment field that can be used for future reference.
3. Enter 1.0 in. in the Bar Height field.
4. Enter 13.0 mils in the Narrow Bar Width field.
5. In the Preferences menu, disable the Include Text option.
6. Press F2 to create the Bar Code.
NOTE: A message instructs you how to use the new Bar Code.
7. Copy the Bar Code.
8. Use the Paste Special option to paste the Bar Code to a new page.
NOTE: Do not use the Enhanced Metafile option because it distorts the Bar Code and the scanner might not be able to
read it.
344
Maintenance (WINDOWS OS)
345
Troubleshooting (UNIX)
Online Storage Management Software for the CARESTREAM PACS System is equipped with automatic backup and
cleanup procedures. However, you might encounter problems due to very high load levels, configurations that were
not adapted to changing needs, negligence in performing maintenance procedures, or hardware and software
malfunctions.
Below are some known problems. Click the link for information about possible causes and recommended solutions.
Copying Log Files
Online Storage Management Storage Failure
Database Access Failure
Low Rate of Performance
Performance Related to Memory Leak/System Stress
Recovery Procedure Related to PHI
Long-Term Storage Manager General Recovery Problem
Long-Term Storage Manager General Backup Failure
Suspected Damaged Drive
Exported Cartridge is Lost or Damaged
ORACLE Error Messages
Cannot Access MICROSOFT INTERNET EXPLORER Applications
Archive Explorer and Viewer Icons Appear as Blue Squares
JAVA Security Error
Checking the Logs
E-Mail Message Details
NOTE: If these procedures are not sufficient, contact Customer Service.
The logs are compressed by the gzip command. To uncompress the files for viewing, type gunzip -c [Logname] more.
This is a plain text file that can be viewed, moved, printed, etc. If you move the files onto a system with a WINDOWS
OS, you can use WinZip to uncompress the files.
346
Troubleshooting (UNIX)
347
Performance Related to Memory Leak/System Stress (UNIX)
If users remain logged into the system for an extended period of time, a memory leak can occur. The memory leak
might decrease system performance (such as increased time to load studies, or the inability to load studies). Users
should manually log out after they complete their work, or when they do not need to use the application, rather than
waiting for the system’s automatic log out. This practice conserves system resources, and frees up user licenses. If
necessary, enforce the policy by reducing the automatic logout time. You should also regularly monitor the system
resources.
Cause 1 The Long-Term Storage Manager cache is full. No free space is available.
348
Troubleshooting (UNIX)
349
Long-Term Storage Manager General Backup Failure (UNIX)
Problem Studies with an insert time of greater than one day were not backed up.
Cause 1 Hardware failure; for example, one of the drives failed during the backup procedure.
Solution 1 1. Click Device Monitor in the NetBackup Administration window.
The Device Monitor window appears.
2. In the Device Monitor window, check the drive status:
If the drive status is DOWN, manually change the state to UP and restart the
backup process.
If NetBackup changes the drive status to DOWN again, consult contact Customer
Service or the storage vendor support.
Cause 2 There are no SCRATCH POOL media available for backup.
Solution 2 1. In the Long-Term Storage Manager Media Management window, click Media List. A list
of all the available media appears.
2. Verify that there are volumes available for use in the SCRATCH POOL.
3. If the SCRATCH POOL is empty, insert new media into the library, as described in Using
the Long-Term Storage Manager Admin Tool.
Cause 3 Database error. For example, a database connection error due to the Online Storage
Management being rebooted.
Solution 3 1. On the Long-Term Storage Manager server, look for sir_prestore log error messages,
such as database connection failure.
2. If entries are found, run the PreStore process again.
3. If no such entries are found, contact Customer Service.
350
Troubleshooting (UNIX)
Cause 2 The Mirror cartridge has been lost or physically damaged, outside of the library.
Solution 2 Insert the Master Cartridge into the library and perform a manual Mirror Operation on the
Master copy through the Jukebox Monitor.
NOTE: Operations in the Jukebox Monitor are always on the Master copy.
351
Cannot Access MICROSOFT INTERNET EXPLORER Applications (UNIX)
Problem Users are not able to access other MICROSOFT INTERNET EXPLORER applications that use
JAVA applets.
Cause The JRE (JAVA Runtime Engine) 1.4.2_05 that is installed on the client computer adversely
affects other applications that utilize JAVA applets.
Solution 1. Open MICROSOFT INTERNET EXPLORER.
2. Go to Tools --> Internet Options --> Advanced.
3. Scroll down to the JAVA (Sun) option.
4. Uncheck Use JAVA 2 v1.4.2_05 for <applet> (requires restart).
5. Click OK.
6. Restart MICROSOFT INTERNET EXPLORER.
352
Troubleshooting (UNIX)
JAVA Security Error in Online and Long-Term Storage Configuration or Clustering Set Up
(UNIX)
Problem The JAVA applet does not load, the Administration window does not open, and “r;Applet
Loading…notinitiated” appears.
In the JAVA console, the following error message appears:
java.security.AccessControlException: access denied (java.net.SocketPermission
198.180.70.201 connect,resolve)
Cause A JAVA security error occurred. A JAVA security error can occur when you are using Long-Term
Storage Manager from a Web Server client and then attempt to access the Online Storage
Management server, for example, to do system administration tasks. This JAVA security error
occurs because Online Storage Management and Long-Term Storage Manager have different IP
addresses.
The JAVA security error can also occur if clustering is used. In the JAVA .policy file, use the
ORACLE IP address instead of the Online Storage Management IP address.
Solution 1. Go to the directory, C:\program files\java\ j2re1.x.x\lib\security.
2. Open the Java.policy file and add this line:
permission java.net.SocketPermission “r;ip-address:1521-”, “r;resolve,connect”;
where ip-address is the Online Storage Management IP address. A sample modified file
excerpt is shown below where 198.180.70.201 is the Online Storage Management IP
address.
grant {
.....
permission java.util.PropertyPermission “r;java.vm.vendor”, “r;read”;
permission java.util.PropertyPermission “r;java.vm.name”, “r;read”;
permission java.net.SocketPermission “r;198.180.70.201:1521-”, “r;resolve,connect”;
353
Troubleshooting (WINDOWS OS)
Online Storage Management Software for the CARESTREAM PACS is equipped with automatic backup and cleanup
procedures. However, you might encounter problems due to very high load levels, configurations that were not
adapted to changing needs, negligence in performing maintenance procedures, or hardware and software
malfunctions.
Below are some known problems. Click the link for information about possible causes and recommended solutions.
Copying Log Files
Monitoring the PACS WINDOWS Operating System Services
Configuring the Log Mechanism
Viewing Log Messages
Online Storage Management Storage Failure
Database Access Failure
Low Rate of Performance
ORACLE Database Listener Check
Troubleshooting the Info Router
Troubleshooting the IS Link Software
ORACLE Error Messages
NOTE: If these procedures are not sufficient, contact Customer Service.
354
Troubleshooting (WINDOWS OS)
Starting/Stopping All PACS Services
To shut down all PACS System Processes including the database, run the script
IMAGINET_ROOT\mst\admin\shutdown.bat.
To start all PACS System Processes including the database, run the script
IMAGINET_ROOT\mst\admin\startup.bat
To shut down or restart all PACS processes not including the database, stop or restart the Imaginet
Startup/Shutdown WINDOWS Service.
NOTE: You cannot use the Imaginet Startup/Shutdown WINDOWS Service to start all CARESTREAM PACS processes
after they were stopped. Use the startup.bat script for that purpose.
355
Online Storage Management Storage Failure (WINDOWS OS)
Problem A storage attempt to the Workflow Manager failed. The log file displays the message
Store Failed – All file systems are full.
Cause Online Storage is full. There are no free volumes.
Solution Manually run the Auto Delete process: C:\Program Files\Carestream
Solutions\System5\mst\admin\fir_AutoDelete.exe
1. From the Scheduled Tasks window, right-click FIR_AutoDelete.
2. Click Run.
To prevent a recurrence of the problem, increase the free space limitation in the Auto
Delete configuration.
For more information, contact Customer Service.
Cause 2 A storage attempt to the Workflow Manager has failed or the system check reports
tablespace free space is below limit.
Solution 2 Run the script IMAGINET_ROOT\scripts\db_ts_fix.pl to enlarge the tablespace.
Cause 3 The existing FIR mounts are full.
Solution 3 Run the script: IMAGINET_ROOT\mst\admin\
AddFirMount.exe to add a new FIR mount.
356
Troubleshooting (WINDOWS OS)
Database Access Failure (WINDOWS OS)
Problem Problems occur when connecting to the DICOM server (Dser process). The log file displays the
message DB_Connection: Failed to connect to database.
Cause The database is not running.
Solution NOTE: Contact Customer Service before applying the solution.
1. Verify that the database is running, as described in Running a System Check.
2. If the database is not running, use the database system script to reactivate the database
(C:\Program Files\Carestream Solutions\System5\scripts\DB_startup.scr).
3. Check the ORACLE Database Listener alert log
imaginet_db\admin\mst1\bdump\alert_mst1.log.
4. Look for the database startup message and watch for errors (ORA-xxx messages).
Refer to ORACLE Error Messages.
5. If errors are found, contact Customer Service. If no errors are found, try to restart the
server.
If the problem continues, contact Customer Service.
357
ORACLE Database Listener Check (WINDOWS OS)
1. To open a command window, select Start --> Run --> cmd.
2. To check the ORACLE Database Listener, type:
>tnsping mstore
For example:
Used TNSNAMES adapter to resolve the alias.
Attempting to contact (description= (address= (protocol=ipc) (key=mst1))
(connect_data=(sid=mst1)(srvr=dedicated)))
OK (10 msec)
3. If OK does not appear, try to restart the Listener. Type:
>lsnrctl stop
>lsnrctl start
4. Repeat the test.
If the test still fails, contact Customer Service.
Application Problems
Problem The connection to the Info Router Server failed.
Cause The Info Router Server is down.
Check When starting the Info Router Admin Tool, check the message that appears.
Solution Restart the Info Router WINDOWS OS service.
Server Problems
Problem No routing of images occurs.
Cause Copy command Server crashed Probe failed Images do not
failed satisfy filter criteria
Check Check the Info Check the status of the Check the Info Check the relevant
Router monitor. Info Router WINDOWS Router logs for rules filters.
OS service. errors.
Solution Depends on the Restart the Info Router Restart the Info Fix rule as necessary.
problem found. WINDOWS OS service. Router WINDOWS
OS service.
Problem As soon as the Info Router starts, there are many commands in the queue.
Cause The Info Router Server was down for a long time and many commands are waiting to be executed.
Check Check the queue’s size and the waiting commands’ sizes.
Invoke sqlplus and run the following command:
sqlplus> select count(*) from autorouter. ar_image_queue_ table;
358
Troubleshooting (WINDOWS OS)
Solution To clean the AR commands, run the following script:
IMAGINET_ROOT\algotec\autorouter\admin\ar_delete_all_commands.bat
To clean the AR queue, invoke sqlplus and run the following command:
sqlplus> truncate table
autorouter. ar_image_queue_ table;
Restart the Info Router WINDOWS OS service.
Problem An error message appears in either the Installing IS Link Database window or the Upgrading IS
Link Database window, and the installation aborts.
An example of an error message is: number of errors is 4>0m
Cause One of the IS Link Software services is running and blocking the database.
The database is down.
Solution Solve the problem that is causing the installation to abort, according to the error message.
Stop the IS Link Software services.
Listener/Converter Failure
A failure can occur during the Listener/Converter services startup procedure or while the Listener/Converter is
running.
Problem The IS Link Software log displays the description of an occurred exception
(java.sql.SQLException…).
Cause The incorrect configuration parameters were entered during the IS Link Software
installation process.
The database is down.
Solution Restart the IS Link Software installation process from the beginning, enter the correct
parameters, and verify that the installation completes successfully.
Contact Customer Service to report the database failure.
359
Email Suite Troubleshooting Procedures (WINDOWS OS)
Although the Email Suite is configured to operate automatically, problems can occur if one of the servers fails, if an e-
mail must be sent to a referring physician not registered in the system, or if an e-mail cannot be delivered. In these
cases, user intervention might be required.
360
Index
A C
Access Control Management tool .......................... 70 Cancelled orders, filtering.................................. 103
Groups tab, opening ........................................ 73
Cannot access MICROSOFT INTERNET EXPLORER
opening.......................................................... 71 applications (UNIX) ...................................... 340
Users tab, opening .......................................... 72 CARESTREAM PACS overview.................................3
Accessing, Cluster Explorer screen ..................... 303 Cartridges, preserving ...................................... 316
Accession number CD Direct Suite
automatic update .......................................... 105 overview .................................................. 9, 249
bar code, scanning .................................317, 332 Setting Configuration Parameters .................... 250
Activating Central configuration
IMS Document Agent ....................................... 89 backup
Adding UNIX........................................................ 288
groups ........................................................... 64 WINDOWS OS........................................... 324
prefix Patient ID ............................................ 103 selecting as UM repository ................................ 59
referring physician......................................... 247 Central configuration editor ................................. 58
restrictions ..................................................... 44 Certificate, installing for APACHE web server ....... 265
to users and groups ............................... 45, 74 Change/set forgotten password URL, configuring.... 62
suffix Patient ID ............................................ 103 Changed ......................................................... 227
users ............................................................. 36 FAILED......................................................... 227
Adding contacts ................................................. 42 Changing
Admin Tools, system requirements for .................. 12 Data Import tool settings ................................. 24
Advanced settings for users, defining.................... 38 default ORACLE passwords
Aliases, configuring Info Router ......................... 196 UNIX........................................................ 269
APACHE web server, installing certificate for ........ 265 WINDOWS OS........................................... 270
Applicable permissions .................................50, 272 scheduled time for performing backup (WINDOWS
Application security OS) ......................................................... 324
UNIX............................................................ 263 User Management repository (group) ................. 57
WINDOWS OS............................................... 264 Checking
Archive configuration ........................................ 211 Online Storage Management storage volume
Assigning permissions....................................... 271 UNIX........................................................ 291
Audit archiving................................................. 113 WINDOWS OS........................................... 325
Audit event settings, defining ............................ 115 Clearing
Audit logs, moving to offline storage bar code programming ............................317, 333
UNIX............................................................ 298 Long-Term Storage Manager Admin Tool event log
WINDOWS OS............................................... 326 ............................................................... 241
Audit Trail ......................................................... 41 Results Area of Media Management Window (LTSM)
............................................................... 240
Audit Viewer Tool window.................................. 112
filtering ........................................................ 111 Client window, Info Router .................................. 81
Clone.............................................................. 217
Auditing .......................................................... 110
Cluster
Auto Delete ...................................... 138, 212, 217
Auto-Delete, configuring database objects........... 176 heartbeat, monitoring .................................... 310
monitoring from command line, UNIX .............. 311
B monitoring procedures ................................... 305
Backup properties, monitoring.................................... 307
external media, WINDOWS OS ........................ 324 resources, monitoring .................................... 309
media for studies, viewing .............................. 156 service groups, monitoring ............................. 308
rule, Info Router............................................ 215 status, monitoring ......................................... 306
to long-term storage (PreStore) ...................... 216 system, system monitoring on ........................ 299
verification Cluster Explorer
UNIX........................................................ 287 screen, accessing .......................................... 303
WINDOWS OS....................................323, 327 toolbar ......................................................... 304
Backup flow, single media archive (SMA) ............ 156 Cluster Manager
Bar code Log Desk ...................................................... 310
accession numbers, scanning ...................317, 332 logging on to ................................................ 300
programming, clearing ............................317, 333 Cluster Monitor
scanner .................................................316, 331 menus ......................................................... 301
programming .....................................316, 332 panels.......................................................... 302
scanning ...............................................317, 332
361
toolbar ......................................................... 301 Custom function............................................... 202
Common VCS commands (UNIX)........................ 315 Customer obligations, security ........................... 257
Complex mapping table, configuring ............107, 171
D
Compression settings, configuring Online Storage
Manager ..................................................... 182 Daemon processes, viewing............................... 293
Compression, JPEG........................................... 279 Daily maintenance checks WINDOWS OS) ........... 327
Conference processes, viewing........................... 293 Daily tasks, WINDOWS OS
Configuration................................................... 159 backup verification ........................................ 327
Field chooser ................................................ 129 disk space .................................................... 329
user............................................................. 129 ORACLE Alert files ......................................... 328
Configuration Window ....................................... 159 scheduled tasks............................................. 327
Configuring services up and running ................................. 328
change/set forgotten password URL ................... 62 verify system check log .................................. 327
complex mapping table ...........................107, 171 Damaged drive
database objects auto-delete .......................... 176 suspected, UNIX............................................ 339
display settings for Storage Management Admin Damaged exported cartridge ............................. 339
tool ......................................................... 145 Dashboard ...............................................282, 319
email Data Import tool
error message options ............................... 192 installing ........................................................ 22
message body options................................ 192 settings, changing ........................................... 24
properties................................................. 192 using ............................................................. 23
report properties ....................................... 193 Data observation, saving................................... 105
Email Suite ............................................191, 246 Database
parameters, restarting server ..................... 248 access failure
properties................................................. 243 UNIX........................................................ 335
general email values ...................................... 192 WINDOWS OS........................................... 345
HL-7 to PACS field mapping set ................105, 170 Admin tool.................................................... 125
IMS Document Agent ....................................... 90 analysis........................................................ 283
Info Router ................................................... 194 backup to external media verification (WINDOWS
aliases ..................................................... 196 OS) ......................................................... 330
rules ........................................................ 194 encryption .................................................... 124
IS Link ..................................................100, 185 fitness verification (UNIX)............................... 290
converter and listeners............................... 186 objects auto-delete, configuring ...................... 176
database values ........................................ 187 synchronizer (WINDOWS OS) ..................325, 330
queues and nofications............................... 190 tablespace free space..................................... 321
log mechanism,WINDOWS OS......................... 343 values, configuring IS Link.............................. 187
Online Storage Manager compression settings... 182 Default ORACLE passwords, changing
patient matching, DICOM parameters .............. 177 UNIX............................................................ 269
permissions .................................................. 271 WINDOWS OS............................................... 270
Pre-fetch ...................................................... 179 Defining
referring physicians email list.......................... 193 advanced settings for users .............................. 38
report parser values ...................................... 189 aliases, Info Router ....................................... 196
reports and order values ................................ 188 audit event settings ....................................... 115
RIS-PACS synchronization .............................. 191 external applications for users........................... 39
simple mapping table..............................107, 171 general auditing settings ................................ 115
Single Media Archive (SMA) ............................ 157 Info Router rule, new ..................................... 199
SIR restore settings ....................................... 213 new groups..................................................... 63
Workflow Manager ......................................... 172 new Info Router rule ...................................... 199
DICOM ..................................................... 164 new Info Router rules .................................... 204
init values ................................................ 183 new users....................................................... 35
Contact information ............................................ 14 rule filters, Info Router................................... 206
Contacts, adding ................................................ 42 rule function, Info Router ............................... 204
Converter and listeners, configuring IS Link......... 186 rule parameters, Info Router........................... 205
Copying log files rule schedule, Info Router .............................. 207
UNIX............................................................ 334 Delete Selected.................................................. 41
WINDOWS OS............................................... 342 Delete Selected User window ............................... 41
Creating Delete Selected Users ......................................... 41
filters for log desk ......................................... 310 Deleting
recurring aliases, Info Router .......................... 197 group............................................................. 69
362
Index
363
I Admin Tool Patients tab ................................... 97
Icons .............................................................. 181 Admin tool Reports tab..................................... 98
Icons, Workflow Manager .................................. 280 Admin tool Visits tab ........................................ 98
ID 41 Admin tool window toolbar ............................... 99
IEC-601 classification ......................................... 18 configuration .........................................100, 185
Image backup to external media verification configuring converter and listeners .................. 186
(WINDOWS OS)........................................... 330 configuring database values............................ 187
Image encryption, DICOM ................................. 123 configuring queues and notifications ................ 190
Image level configuring report parser values ...................... 189
merging at ................................................... 131 configuring reports and orders values .............. 188
splitting at .................................................... 131 converter failure............................................ 347
Image resend .................................................. 140 database installation failure ............................ 347
Importing DICOM data ........................................ 23 message processing failure ............................. 347
Importing media into Jukebox............................ 237 overview .................................................. 11, 92
Importing studies ............................................... 27 processes, shutting down ................................. 95
IMS Document Agent shutdown, verifying ......................................... 95
activating ....................................................... 89 startup, verifying............................................. 94
configuring ..................................................... 90 troubleshooting in ......................................... 347
IMS Document Agent (XDS/XDS-I Document Source) using ............................................................. 93
................................................................... 88 using Admin tool ............................................. 96
IMS Document Repository (XDS Document
Repository) ................................................... 91 J
Info Router........................................................ 84 JAVA
application problems ...................................... 346 configuration ................................................ 184
backup rule .................................................. 215 plug-in, downloading ....................................... 13
Client window ................................................. 81 security error, UNIX
configuration ................................................ 194 clustering set up........................................ 341
configuration toolbar........................................ 82 online and long-term storage configuration... 341
configuring aliases ......................................... 196 JPEG compression ............................................ 279
configuring rules ........................................... 194 Jukebox .......................................................... 227
creating recurring aliases ............................... 197 exporting media from..................................... 238
defining/modifying aliases .............................. 196 importing media ............................................ 237
filtering commands .......................................... 86
K
menu bar ....................................................... 84
Kill command, using ........................................... 95
Monitoring tab................................................. 85
opening.......................................................... 79 L
overview .................................................. 10, 77 LDAP ................................................................ 68
rule filters, defining ....................................... 206 configuration, testing ....................................... 61
rule function, defining .................................... 204 selecting as UM repository ................................ 60
rule parameters, defining ............................... 205 Library hardware fitness check........................... 297
rule schedule, defining ................................... 207 Licenses Log .............................................282, 319
rules Life Cycle
defining new ............................................. 204 configuration ................................................ 210
updating................................................... 209 management ................................................ 210
server problems ............................................ 346 Limitations, user ................................................ 20
starting and stopping ....................................... 87 Listeners and converter, configuring IS Link ........ 186
toolbar ........................................................... 83 Loading from Single Media Archive (SMA) ........... 157
troubleshooting ............................................. 346 Locating studies ............................................... 155
using ............................................................. 78 Log..........................................................282, 319
Info Router rule desk
editing ......................................................... 199 Cluster Manager ........................................ 310
new, defining ................................................ 199 creating filters for...................................... 310
Init values, configuring Workflow Manager .......... 183 exporting to MICROSOFT EXCEL ...................... 116
Installing files, copying
certificate for APACHE web server.................... 265 UNIX........................................................ 334
Data Import tool ............................................. 22 WINDOWS OS........................................... 342
Inventory report, generating ............................. 234 mechanism, configuring
IS Link WINDOWS OS........................................... 343
Admin tool Orders tab ...................................... 98 messages, viewing ........................................ 310
364
Index
366
Index
368
Index
369
CARESTREAM is a trademark of Carestream Health, Inc.
The Kodak trademark and trade dress are used under license from Kodak.
370