The DICOM configuration allows the user to add/edit DICOM repositories. These repositories can be local folders containing DICOM files or DICOM network servers located on the local or a remote computer. The DICOM Dictionary is used by the DICOM Dump to identify information in the DICOM header. A How-To on configuring the NanoSPECT's DICOM Servers in the VQ is provided.
There are three methods available to access the DICOM Repositry. First, the repository index is accessible via the Repository panel in the DICOM Browser.
The second method is to select the Configuration option in the Tools menu and to then click on the DICOM panel.
The DICOM panel in the Configuration Tool provides the most in-depth DICOM information available in VQ. The DICOM panel consists of three sections: DICOM Settings, DICOM Cache, and Capture.
|DB path||Location of local DICOM database. Allows optimized internal access to the Mediso DICOM database. See Optimized local access for details.|
|Repositories||List of available repositories. The bank of buttons immediately beneath the pulldown menu operate on the selected repository in this field|
|: Check connection to DICOM repository.
Local folders are verified to exist and a C-ECHO is sent to
: Add a new repository
: Remove repository from list
: Open the DICOM Editor
|Dictionary||Shows list of additional dictionaries used by the DICOM library.
Please set environment variable
|Rcv Port||Port over which the DICOM peer sends data.|
|load palette %||When this box is checked, the palette window will be loaded in accordance with the image data. When this box is not checked, the palette window will be set to whatever the window was set to last.|
|DICOMDIR||Checking this box enables support for DICOMDIR files.|
|Folder Filter||Allows users to dictate the type of dicom files loaded into VQ. Users can configure loading extensionless dicom data by
adding a space and * to the end of the default settings:
The DICOM cache allows the storage of frequently used data sets locally, thus improving load time into VQ. Every time the VQ is started, it checks the current size of the cache against the maximum cache size. If the currect cache size exceeds the maximum cache size, then older files (those opened least recently in the VQ) are removed.
|Current Size||Size in Mb of the data currently stored in the DICOM Cache. The percentage to the right of the field indicates how close the cache is to capacity.|
|Max size||Maximum amount of memory that can be made available for the DICOM Cache (default = 1000.0 MB).|
|Life Time||Length of time over which data will be stored in the DICOM Cache (default = 14 days).|
|Clear||Empties the DICOM Cache|
Not yet implemented -- please check back soon!
The DICOM Repository panel in the DICOM Browser is the most convenient location for adding and editing repositories, including DICOM Servers, local folders, and PACS Servers.
|Repositories||List of available repositories. The bank of buttons immediately beneath the pulldown menu operate on the selected repository in this field. Please click here to learn more about the DICOM repository section of the DICOM browser.|
|Check connection to DICOM repository. Local folders are verified to exist and a C-ECHO is sent to DICOM servers.|
|Add a new repository.|
|edit: Open the DICOM Editor.|
|Opens a Windows Browser that can be used to select a local folder as a repository.|
|Fetch all DICOM meta data.|
|Remove repository from list.|
The DICOM Editor is used to add repositories, including DICOM Servers, PACS Servers, or local folders.
|Displayed Name||Name as shown in the repository selection box. Can contain any alphanumeric character.|
|Repository Type||Local folders are simple directories available on the local
computer (also via a shared network). Such directories with
many files take rather long to scan. in this case the
performance of a DICOM server is superior.
Such DICOM servers are network services on the local or a remote computer. They provide a database to efficiently browser study data. An iPACS server is an online PACS server, a regularly used picture archiving and retrieval system for medical images.
|Local DICOM folder||Select a local directory. All sub-folders will be displayed as projects in the second repository drop-down window.|
|DICOM server||AET is an Application Entity title.
Calling AET: Has to be a valid AET configured on the server
Called AET: Name of DICOM servers application entity.
|iPACS server||Username and password are specific to the user for their
site's iPACS system.
Hostname will be the site of the server for the iPACS and Port is the communication channel through which the iPACS server communicates.
A DICOM server is specified by a calling AET (application entity title), a called AET as well as a TCP address (consisting of a host name and a port, the default settings are localhost:104). The AETs have to be configured on the DICOM server, too. For VivoQuant use port 23104 on the remote server.
An iPACS server is specified by setting the appropriate Hostname and Port and by entering user-specific Username and Password. A DEMO iPACS server may be registered by using Hostname: demo.ipacs.invicro.com, Port 80 and leaving Username and Password blank. iPACS servers also enable the use of Projects, a useful tool for organizing DICOM data.
To use the optimized local DICOM access (much faster) use 'localhost' (all lower case, otherwise a normal DICOM connection is used) as the host name. Additionally, you have to define the 'DB path' (see above).
The iPACS repositories permit the use of projects. Projects represent a directory structure for DICOM repositories. Data may be stored and accessed via different projects, aiding organization of DICOM data. In this example, an iPACS repository for "bioscan/demo" is being configured. The "bioscan/demo" repository contains three projects.
If any projects are present within a configured iPACS repository, a second pulldown menu will appear in the Repository panel of the DICOM browser. All projects within that repository are available via the second pulldown menu. The three projects associated with the "bioscan/demo" repository are shown in the screenshot below.
Select any project to view only data associated with that project.
By default, data will only be displayed when the project to which it belongs is selected from the second pulldown menu. For example, in this screenshot, no data appears in the "bioscan/demo" repository because all data within the larger repository belongs to individual projects.
To simultaneously view all data belonging to a repository AND its projects, place a * at the end of the hostname during respository configuration. The * will cause all data within the repository and its projects to be displayed recursively. This behvavior applies across all repository and project levels.
First, open the DICOM Browser. Find the Repository panel and either select the pre-existing repository from the pulldown menu or select "new" to create a new repository.
For the standard access on the NS Workstation (WS), use:
|Displayed Name||NSxxWS_DCMSRV (or customer's preference)|
where xx is replaced with the NanoSPECT number, typically no leading 0 for numbers < 10.
The local access VQ is able to access the DICOM Server directly, so there is no need to add the VQ as a client on the DICOM Server. However, it does not hurt and is necessary when configuring an VQ for which access is not locally on the workstation. See Adding VQ as a DICOM Client for more information.
The above table described configuring VQ to access the Workstation DICOM Server. VQ may also be configured to access the Acquisition computer's DICOM Server. The procedure is similar, but there is no WS in the naming convention.
|Displayed Name||ACQ_NSxx_DCMSRV (or customer's preference)|
where xx is replaced with the NanoSPECT number, typically no leading 0 for numbers < 10.
In place of hostname (i.e., nanospectxx), it is also possible to use IP addresses (i.e., 192.168.1.1 for local WS-ACQ computer connections). Please verify that the hostname resolves by using 'ping hostname' in a Command window. Also, in order to access the ACQ computer from the WS computer, you must configure the DICOM Server on the ACQ computer.
Start C:\Program Files\Mediso\DICOM Server\DICOMServerMgr.exe
On the main panel, you see the name of the database (NSxx(WS)_DCMSRV where xx is the NS number and WS is present on the workstation) which should be used as the Called AET.
Click on the "Clients" button. On the WS, you should already see listed there the HiSPECT and InterviewXP entries. To add the VivoQuant, add the line at the bottom of the following list.
|Application Entity Title (AET)||Host||Port|
In place of HOSTNAME in the VQ entry, use LOCALHOST on the WS Computer and NANOSPECTxxWS or the workstation IP address on the ACQ computer.
|Example Number||Computer||Calling AET||Hostname||Port|
|Example #1||NS5 ACQ Computer||INVIVOSCOPE||NANOSPECT5WS||23104|
|Example #2||NS13 WS Computer||INVIVOSCOPE||LOCALHOST||23104|
|Example #3||NS13 2nd WS Computer||VQ-WS2||IP Address or 2nd WS Computer Name||23104|
What is of importance in this configuration is not the specific name "INVIVOSCOPE" but the fact that the same name "INVIVOSCOPE" was used in the DICOM Client Configuration and at the "Calling AET" in the VQ Repository Configuration. To illustrate this point, note the client in the image above with the name "VQ_anyname".
Also, separate names must be used for each configuration. In other words, to configure the VQ on a 2nd workstation, would require changing "INVIVOSCOPE" to something different, like "VQ-WS2". For example, let's say a 2nd workstation was being set up for the NS13. In the Client Panel of the DICOM Server Manager, a client would be added as in Example #3 in the above table.
In the VQ on the 2nd workstation, a new repository would be created with the following settings.
|Displayed Name||NS13WS_DCMSRV (or customer's preference)|
|Hostname||nanospect13ws (or IP)|