Machine specific tools, software tools and auxiliary equipment
1 System Configuration
There are three possibilities to configure ADCQS.2.1. All three possibilities
have their justification if they are applied for the purpose they are designed for:
• Configuration ViewerÆ Standard configuration tool for the ADCQS for
onsite configuration, configuration changes and enhancements
• CPF-file created by CCM ToolÆ Can be used after initial setup to save
configuration work; should not be used later on anymore for configuration
changes or enhancements
• Cloning Æ Allows to duplicate stations; this helps especially to reduce the
GUI configuration work if more than one Viewer has to be set up similarly.
1.1 Configuration via Configuration Viewer
The Configuration Viewer is the ideal tool on ADC QS to change or modify the
configuration of the system.
It is explained in detail in the Configuration Viewer Software - User Manual,
separately added in this chapter 3.2 .
Here we mainly focus on the Device configuration.
1.1.1 Configure Digitizer
(1) To Configure Digitizer select at Configuration Viewer
Machine specific tools, software tools and auxiliary equipment
DD+DIS135.02E
(4) Enter network information at tab Network and AE Title at tab DICOM
at tab Image the image type can be looked up.
(5) Click <Finish> to save configured digitizer
To transfer the configuration information from the ADC QS to the digitizer
at the end of the configuration session a Digitizer CPF-file (partial CPF-file)
must be created and installed on the digitizer (see further explanation
below, at 1.2.2 of this chapter).
1.1.2 Configure Gateway
(1) To Configure Gateway select at Configuration Viewer
<Setup><Devices> <ADCQS>
<Server Hostname>
(2) Double click on host name of the Server e.g. <QS_SERVER_10>
(3) Check host name and IP-Address at tab Network. Network settings are
taken over from “Windows NT Network Settings”. To test TCP/IP
connection you can press <Test Connection…> button.
Machine specific tools, software tools and auxiliary equipment
Select only one ID-Station in a cluster for DirectID. To communicate the IDViewer to run DirectID on ADC SOLO digitizer, a Digitizer CPF-File (partial
CPF-file) has to be created and imported on the digitizer. In addition
DirectID has also to be activated in the ADC SOLO digitizer to make it
working.
1.1.4 Configure Medical Printers
(1) To Configure Medical Printers select at Configuration Viewer
<Setup><Devices> <Medical Printers>
(2) Double click on <Add new medical printer>
(3) Select printer model, click <Next>
Repair and Service
(4) Enter IP_address and name of printer, click <Next>
Machine specific tools, software tools and auxiliary equipment
Softcopy:
Enter display settings
DD+DIS135.02E
1.2 Configuration via CPF-File
In conjunction with ADC QS we distinguish between two different CPF-files:
• The CPF-file created by means of CCM-Tool.
• The Digitizer CPF-File or also called partial CPF-File.
1.2.1 CPF-File created by CCM
This is the file which is used to configure VIPS, PRID and the CR-Digitizers.
This file can be used as a good basis to get started after initial setup of an
ADC QS Cluster. To configure ADC QS with the CCM created CPF-file
proceed as follows:
(1) Carry out Configuration work with CCM tool.
Please note that the hostname for an ADC QS Server has to be entered in
capital letters (the simplest is here to use the same term for hostname,
station name and DICOM_AE title).
(2) Save CPF-file on floppy
(3) Startup Configuration Viewer on ADC QS Server
(4) Enter floppy and Select “File-Æ Import CPF”
(5) At the end of the import you maybe asked to synchronize printers. Just
select a printer and press “Install”. Repeat this until all printers are
installed.
Machine specific tools, software tools and auxiliary equipment
ADC QS supports IP_address resolution via DNS (or Netbui). However
most of the other AGFA devices (digitizers, printers, etc.) do not support
this resolution method.
During importing a CPF-file the ADC QS reads the IP_addresses of that
different device in the CPF-file and tries to resolve the corresponding
hostname via DNS (or Netbui). If it is successful finding a corresponding
hostname, it will fill it in into the “Hostname” field.
If it is not successful, it will fill in the IP_address into the “Hostname” field.
The next time you export Digitizer CPF-file (partial CPF-file) you will have
the IP_address filled in for hostname and IP_address.
Therefore it is advised after importing a CPF-file created by CCM to select
Setup Æ Devices Æ Input Devices Æ Digitizer. There you select the
Network tab and change the hostname field (containing the IP_address)
into the actual hostname of the digitizer.
Please note that importing a CPF-file on the ADC QS Server deletes all
configuration information setup before. That is:
• The whole device configuration
• The whole examination configuration
• The whole image processing configuration
• The whole dose monitoring statistics
Therefore we recommend to use the CPF-file import only for the initial
startup.
1.2.2 Digitizer CPF-File (also called partial CPF-File)
The need for a Digitizer CPF-file came up together with ADC QS.2.1. The
reason why we need that file is because in a pure ADC QS environment the
Configuration Viewer is used to configure ADC QS. However the CR-Digitizers
still need a CPF-file to be configured.
ADC QS produces that file itself. It must only be used for Digitizers, as it
contains only part of the information a CCM created CPF-file contains.
To create a Digitizer CPF-File you have to perform the following steps:
(1) Carry out Configuration work with Configuration Viewer
(2) Put floppy to floppy drive of ADC QS station
(3) Select at Configuration Viewer
<File>
<Export AGFA DICOM Digitizer CPF>
(4) Click <Export CPF> to browse folder A:\ to save CPF-file on floppy
(5) Install the CPF-file from floppy in the digitizer
Machine specific tools, software tools and auxiliary equipment
1.3 Configuration of mixed environments
ADC QS.2.1 can also be installed in mixed environments with PRID and VIPS.
For the initial setup the same CPF-file, created by the CCM-Tool can be used.
If this file is imported into ADC QS you will find in the Configuration Viewer
under Setup Æ Devices Æ Destination also the VIPS stations as possible
destinations. This destinations must be deleted as they are not able to receive
data from an ADC QS.
For later configuration changes it is advised to use Configuration Viewer for
ADC QS and CCM-Tool for VIPS and PRID related changes. This may require
also manual adaptation between the different configuration methods.
1.4 Configuration Cloning
Depending what is to be done two procedure to clone ADC QS devices maybe
applied. They also can be used in combination.
DD+DIS135.02E
1.4.1 Cloning an ADC-QS Server
This is normally done when configuration from one Server should be
transferred to another Server, i. e. into another cluster. Here only the
configuration data kept in the database is transferred. The procedure is as
follows:
(1) Start Configuration Viewer on Source Server*
(2) Select
<File>
<Export Configuration to xml-file>
This may take some minutes depending on the size of the configuration.
(3) Stop ADC QS application on Target Server
(4) Start Configuration Viewer on Target Server
(5) Select
<File>
<Import Configuration from xml-file>
This may take some minutes depending on the size of the configuration;
app. 5 min per 0.5Mb size of xml-file.
(6) Check Gateway configuration in Configuration Viewer and adapt if
necessary to the requirements on the Target Server
(Setup Æ Devices Æ ADCQS Æ <Server name>). Parameters to be
adapted maybe hostname, IP_address and DICOM AE_title
(7) Select
<Setup>
<Devices>
<Destinations>
and delete the Target Server from the list of possible destinations (to
avoid sending to itself)
Machine specific tools, software tools and auxiliary equipment
(8) Select
<Setup>
<Devices>
<Destinations>
and add the Source Server to the destination list, if it is requested to send
studies to the source ADC QS
*In the above text the Source Server is always the Server which provides the
configuration to be duplicated, while the Target Server is the one to receive
this configuration.
1.4.2 Cloning User Settings of Viewers (for ADC QS Server and Client)
The cloning of Viewers retrieves configuration information from the system
which comprises of user settings, registry entries for GUI configuration,
textbox definitions, etc. This allows to transfer GUI configuration from one
Viewer to others (either in the same or in another cluster). Thus a lot of time
can be saved as work does not have to be done double.
There is one restriction of this procedure for the time being, that only the
configuration for the “empty” user can be transferred (i.e. no login name and
password are used to login on application level).
The procedure is as follows:
(1) Each Viewer which is activated on a Source System should be at least
started once before you start the cloning, as some files and registry
settings are only created after the first start-up of a Viewer.
(2) Stop ADC QS
(3) Insert an empty floppy into the floppy drive of the Source System with the
Viewer to be cloned.
(4) Select at NT-Start Menu
<AGFA>
<ADC-QS>
<Tools>
<ExportUserSettings>
This program copies all the above mentioned information to a floppy.
(5) If you have other application users set up as the “empty” user you have to
copy the files <username>.cpx from the C:\temp\cpf directory manually to
the floppy.
(6) Insert the floppy into the floppy drive of the Target System where the
Viewer should be imported to.
(7) Select at NT-Start Menu
<AGFA>
<ADC-QS>
<Tools>
<ImportUserSettings>
The old GUI configuration information will be overwritten.
Machine specific tools, software tools and auxiliary equipment
(8) If you have other application users set up as the “empty” user you have to
copy the files <username>.cpx from the floppy to the directory C:\temp\cpf
of the Target System where the Viewer is imported.
(9) After resetting the system the Viewer of the Target System has the same
GUI settings as the Viewer of the Source System.
This procedure can be used both on ADC-QS Server and Client for cloning
Viewer settings.
2 License Management
For ADCQS from a commercial point of view it is distinguished between
software options which require Server or Client license:
Software - Options
License for each
Server PC
DD+DIS135.02E
License for
each Client PC
ADC Online-Processing Software (Win)
ADC IPD-Viewer Software (Win)
ADC Black Border Software (Win)
ADC Smart Print Software (Win)
ADC Autorouting Software (Win)
ADC Pediatric Software (Win)
ADC Uro/Tomo Software (Win)
ADC Dental Software (Win)
ADC DICOM-Store (Win)
ADC Multi Format Import/Export (Win)
ADC Annotation Software (Win)
ADC QC-Viewer Software (Win)
ADC ID Software (for Win appl.)
ADC Full leg/spine Software (Win)
ADC Rislink Toolkit Software (for Win appl.)
ADC Dose-Monitoring Software (Win)
ADC Auto QC Software (Win)
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
A Server License has to be acquired once for an ADC QS cluster, while a
Client License has to acquired for each PC it should run on. Therefore the
following has to be regarded when adding a new license:
• A Server License has to be activated on each PC in the cluster. The same
license_ID can be used throughout the cluster.
• A Client License must only be activated on the PC(s) the SW-Option is
bought for. For each PC a different license_ID must be used.
Machine specific tools, software tools and auxiliary equipment
3 Creation of an ADC QS Restore CD
3.1 General
The creation of a bootable Restore CD-ROM onsite makes it possible to
restore the server system at a later date back to the same identical state as it
was by creation time of the CD. Please pay attention to the following points:
• The CD must only be used on the PC where it was created!
• During the process the CD tray can open and close automatically; this
is then part of the procedure.
Together with ADC QS 2.1.xx the Restore Toolkit version 2.5 is introduced. It
provides the following new features compared with version 2.4:
• Client Restore CDs can be created as well (if CD-Writer available)
• Norton Ghost 7.5 makes it possible to directly write to the CD Writer.
This saves some time. However only high quality CD-R should be
used. Cheap ones are very error prone (esp. on Clients).
• Restore Toolkit fits on a floppy now.
• Restore CDs are date and time stamped, labeled with system type
information and which disk image is included.
• The system event logs are also included in the system disk image.
• Disk spanning is possible now (i.e. if the disk image does not fit on one
CD, it can be continued on a second one).
DD+DIS135.02E
3.2 Requirements
• ADC-QS Restore Toolkit version 2.5 or higher
• Blank or re-writeable CD (use high quality CD-Rs only)
• ADC-QS System (Server or Client) with built in CD Re-Writer
3.3 Procedure
(1) Insert the ADC QS Restore Toolkit floppy in the floppy drive.
(2) Stop ADC QS and empty the desktop Recycle bin.
Machine specific tools, software tools and auxiliary equipment
(3)
Re-start the system, which will boot now from floppy drive. The
following menu is shown:
Make selection according to system type:
For ADC-QS Server normally only Disk 1 needs to be restored.
For ADC-QS Client only Disk 1 exists.
(4) CD tray opens. Insert blank CD or clean re-writeable CD
(5) The following menu is shown
Enter <Y>
(6) If CD tray is not already closed, it will be closed automatically now.
(7)
Norton Ghost Software starts automatically. It reads first boot data from
floppy and starts afterwards to burn the Restore CD of the selected
Disk. No action required – takes about 12 minutes.
(8) CD tray opens automatically, when process is finished.
If the system image does not fit on a single CD, message “Insert next media and press enter to continue…” appears. Insert
a new blank CD or clean re-writeable CD and press enter.
(9) The following window is shown:
Follow the instructions to eject the new created Restore CD and the
floppy and restart the system by pressing Ctrl+Alt+Del
Machine specific tools, software tools and auxiliary equipment
3.4 Restore Toolkit Version 2.5 – Potential Errors and Solutions
Most errors take place during the writing of the Ghost image, in this case an
error code is given together with a short explanation. In all cases, if an error
occurs, additional information is found in the file c:\temp\ghosterr.txt.
a) ABORT: 440, Ghost cannot run on Windows NT based systems
(NT/2K/XP).
You are attempting to use the Restore Toolkit floppy or created Restore CD
from within a Windows session.
Restart the system with the Toolkit floppy or Restore CD inserted.
b) ABORT: 52102, CD-R disc is not writeable. Insert blank media.
Ghost can only write to clean media (no multi-session possible)
Insert a new blank CD-R or an erased CD Rewritable.
c) Critical Error 0x0C Sharing Violation, Abort or Retry ?
This is a non-standard error that will normally only be seen when you are
doing some custom steps with the Ghost program. The following are known
situations:
i) The ghost image was made with a later version of Ghost (eg.
7.5) and you are trying to read it with an older version (eg.
6.01). Note: the other way around is OK (older .GHO files are
read OK by 7.5)
Use Ghost v7.5 or later.
ii) The source and destination disk are the same.
Write directly to the CD Writer.
d) ABORT:10027, Unknown image format: code 51: later Ghost version
required.
Same as c) i) above.
e) ABORT: 18190, No such file or directory (ENOENT) when opening
A:\SKIPLIST.TXT
Can not find a file referenced during the Ghost image creation process.
Leave the Restore Toolkit floppy in the drive, until everything is
complete.
f) Write protect error writing drive A (Abort, Retry, Fail?)
The write protect tab prevents the toolkit from writing some temporary files
on the floppy.
Flip the protection tab back to the write enabled position.
Machine specific tools, software tools and auxiliary equipment
DD+DIS135.02E
4 Agfa DICOM bridge
See appended document AGFA DICOM Bridge Version 2.0 (User Guide)
5 ID-Viewer GUI and DICOM Modality Worklist GUI
The configuration of the ID-Viewer GUI and DICOM Modality Worklist GUI is
mainly described in the ID-Viewer User Manual.
The GUI of the ID-Viewer and the DICOM Modality Worklist can be configured
in the field only by predefined GUI templates. Screenshots of these GUI
templates can be found in chapter 11, Installation Planning. Other changes
are not foreseen in the field. If the currently provided templates should not be
accepted by the customer, inform your Global Support Center. There, a
headquarter decision will be initiated if and when a change will be provided.
6 RIS Link
The configuration of the RIS Link is described in the RIS Link Toolkit User
Manual (enclosed in the ADC QS RIS-Link Toolkit option). It gives the
information how the data provided by the RIS should look like in respect to
format, structure and DICOM mapping. The data the hospital RIS system
delivers, have to match to these definitions. Changes on ADC QS side are not
foreseen. To avoid delays during set-up it is absolutely necessary that the
customer is aware well in advance what his HIS/RIS system has to deliver.
If the customer's HIS/RIS system is not able to fulfill these requests, GSC has
to be involved right from the beginning. The goal is to have for these sites
before the actual set-up of the ADC QS starts a response from AGFA whether
these adaptation requests can be fulfilled or not.
Please note that the ADC QS RIS-Link Toolkit does not support anymore data
retrieval from RIS/HIS systems by means of a DOS executable file. Only a
Windows executable can be used. For supported connection modes refer to
ADC QS RIS-Link Toolkit user manual.
Machine specific tools, software tools and auxiliary equipment
8 Setup of a Secure User
(optional – only on Customer Request)
The “Secure User Script” allows to create a user which has very limited
access to NT-Operating System. Almost all icons are removed from the
desktop and additionally the NT-Start Menu is reduced to the absolute
minimum.
Desktop includes only the following icons:
NT-Start Menu of the Secure User is reduced to
Agfa Æ ADC QS Æ ID Viewer, Reset ADC QS, Start ADC QS, Stop ADC QS
In addition the right mouse button is deactivated on the NT-Desktop and it
prevents the user, logged in with “Secure User” account, to access the
Configuration Viewer.
However the ”Secure User” does not have any restrictions on application level.
The “Secure User” is able to delete images from the application or reject
studies. The security is only provided on NT-Operating System and
Configuration level.
The sequence of installation of the Secure User in relation to the printers is
important.
• First configure all printers on Server (with “compas” account)
• Add Secure User account on Server
• Add same Secure User account on Client. During creation of the
account the printer connections will be automatically setup as network
printers.
If you want to add a printer later on you have to perform the following steps:
• Configure printer to be added on the Server (with “compas” account)
• Remove Secure User on the Client only
• Re-install Secure User on Client again. In this way the new printer is
added to the Secure User account.
Repair and Service
8.1 Add Secure User
Only one account for a Secure User has to be created. It has to be the same
account on ADC QS Server and Client.
Machine specific tools, software tools and auxiliary equipment
DD+DIS135.02E
(2) Define Secure User with a corresponding password. Confirm the
password by clicking <OK>
(3) System restarts two times. During this do not start any other application.
(4) Auto logon is switched off now. NT login window appears after every
restart.
8.2 Remove Secure User
If you want to change the complete Secure User account it is best first to
remove current Secure User and then add a new one. This has to be done
both on Server and Client.
This procedure must also be applied on the Client only, if a printer should be
added to the Secure User account (see above)
(1) Check that you are logged in as “compas"
(2) Select
Start
AGFA
ADC-QS
Tools
Remove Secure User
(3) Select Secure User, you would like to delete, from pull down menu and fill
in corresponding password. Confirm the password by clicking <OK>
(4) System restarts two times. Always login as “compas" account. If the last
Secure User has been deleted from the system, Auto Logon is activated
again.
Machine specific tools, software tools and auxiliary equipment
9 Installing ADC-QS into an Existing NT Domain
By default the systems delivered by AGFA are set up to operate in an
unmanaged ‘peer to peer’ network pool called ‘WORKGROUP’. This name
‘WORKGROUP’ is the same for all language versions of ADC-QS.
Further to this the ADC-QS Server and Client machines are set up with 2 local
machine accounts:
Account
Password
administrator (empty)
compas compas98
Both these accounts are members of ‘Administrator’ group on the local
machine. By default ADC-QS runs under the ‘compas’ account. The
advantage of running ADC-QS as part of ‘WORKGROUP’ is that the
administration tasks are much reduced – the downside to this is that there is
almost no security in place.
In many hospital environments ADC-QS will be used as part of a secure NT
domain. To add new ADC-QS systems to the domain will require assistance
from the local NT Domain Administrator (who has the passwords and authority
required). Follow the sequence below to add an ADC-QS Server or Client into
a domain:
9.1.1 ADC-QS System Name
Change the system name to the new name assigned by the domain
administrator – Start Menu::Settings::Control Panel::Network::Identification,
click on button ‘Change’, enter the new name, click <OK> . Click <OK> on
confirmation dialog, click <Close> on the network control panel, dialog ‘… You
must shut down and restart your computer… Restart now’, click <Yes>. The
system restarts.
9.1.2 Add ADC-QS System to Domain
Log back in as local system Administrator (blank password ). Hold down the
shift key to defeat any auto-login. Once logged in, stop any ADC-QS autostart (Server only). From Start Menu::Settings::Control
Panel::Network::Identification, click on button ‘Change’, click on radio button
‘Domain’, enter the domain name. Select checkbox ‘Create Computer
Account in the Domain’, enter the Domain Administrator name and
password. Click <OK>.
Machine specific tools, software tools and auxiliary equipment
DD+DIS135.02E
Upon success the message ‘Welcome to <Domain Name>’ will popup. Click
<OK>, then <Close>, dialog ‘… You must shut down and restart your
computer… Restart now’, click <Yes>. The system restarts.
9.1.3 Adding Domain User to Local System
Log back in as local system Administrator (not
the ‘User Manager for Domains’, double click on ‘Groups->Administrators’ in
the list at the bottom half of the screen.
Machine specific tools, software tools and auxiliary equipment
Click then on <OK> to close this dialog. Close the User Manager (Alt-F4, or
menu User::Exit).
DD+DIS135.02E
9.1.4 Logging onto the Domain
Log-off from the local system (‘Start Menu::Shut down::Close all programs
and log-on as different user’) ,then re-logon using the domain account as
shown below:
Once logged in, ADC-QS is now available for use.
9.1.5 Notes:
a) The auto-login and auto-shutdown feature of ADC-QS Server is still
working under domain log-in. To bypass the auto-login, hold down the
Shift key during the login phase.
b) The domain administrator will normally carry out sections Create Compas
account and Adding Domain User to Local System
you do not have to make a request for the domain administrator account
and passwords.
c) Procedures for setting up printers and other devices from the ADC-QS