Ot-Dice v3 Usermanual
Ot-Dice v3 Usermanual
OTDICE V 3.0
(Version 3.0)
User Manual
OTech Inc,
2001, East Oakshores Drive,
Crossroads, TX 76227, USA,
Telephone: 9404409530
Fax: 9404409566
For sales and licenses send email to [email protected]
For technical support send email to Paul Gihring at [email protected]
www.otechimg.com
OTech Inc, OTDICE User Manual, Print Date: 05/08/06, 8:16 AM Page 2 of 49
Table Of Contents
REVISION HISTORY...................................................................................... 4
1. Overview .................................................................................................................... 5
1.1 General..................................................................................................... 5
1.2 Definitions / Abbreviations......................................................................... 6
1.3 References ............................................................................................... 7
1.4 How this manual is organized.................................................................... 7
3. Operations ............................................................................................................... 11
3.1 Configuration .......................................................................................... 11
3.1.1 General Configuration...................................................................... 11
3.1.2 DICOM Nodes Configuration ........................................................... 11
3.1.3 Configuration Information – Registry................................................ 13
3.1.4 Configuration Information – Files ..................................................... 13
3.2 Echo SCU............................................................................................... 14
3.3 Storage SCU........................................................................................... 14
3.4 Send List................................................................................................. 15
3.4.1 Compression ................................................................................... 16
3.4.2 Update Files .................................................................................... 16
3.5 Storage SCP / Echo SCP........................................................................ 18
3.5.1 Storage SCP Node Details Configuration......................................... 18
3.6 Query SCU ............................................................................................. 20
3.6.1 Setup Query Attributes .................................................................... 21
3.7 Move SCU .............................................................................................. 22
3.8 Image Mode............................................................................................ 23
3.8.1 View the image................................................................................ 23
3.8.2 Window Level the image.................................................................. 24
3.8.3 Edit/Save the image ........................................................................ 24
3.8.4 Save dumps of the image ................................................................ 25
3.9 Results.................................................................................................... 26
3.10 Sessions ............................................................................................... 26
4. Sample Sessions..................................................................................................... 28
4.1 Sample Session 1 ................................................................................... 28
4.2 Sample Session 2 ................................................................................... 32
4.3 Sample Session 3 ................................................................................... 36
4.4 Sample Session 4 ................................................................................... 38
4.5 Sample Session 5 ................................................................................... 39
4.6 Sample Session 6 ................................................................................... 40
4.7 Sample Session 7 ................................................................................... 43
6. Installation / Uninstallation.................................................................................... 48
6.1 Installation .............................................................................................. 48
6.2 Uninstallation ......................................................................................... 48
REVISION HISTORY
1. Overview
1.1 General
OTDICE – OTech DICOM Interoperability Checking Entity is a software utility that performs DICOM Messaging
services CSTORE, CECHO, CFIND and CMOVE. It acts both as a service class user and provider for CSTORE
and CECHO services. It acts as a service class user for CFIND and CMOVE services.
OTDICE will also assist in testing DICOM conformance. It displays the DICOM message transferred between peer
Application Entities.
The intention of DICOM is to define the communication capabilities of each product type to a degree that allows
products, supplied by different vendors, to be connected together to form an open, integrated diagnostic / treatment
capability.
It is assumed that the user has a basic understanding of the DICOM standard. For further clear information, please
refer the ACR/NEMA Standards Publications, No PS3 2001 DICOM Standards documents.
Notes:
Print SCP, Print SCU and SR Report are features of Version 3.0 and hence these buttons and menu items are
disabled.
Transfer Syntax A set of encoding rules that allow Application Entities to unambiguously
negotiate the encoding techniques (e.g., Data Element structure, byte
ordering, compression) they are able to support, thereby allowing these
Application Entities to communicate.
SCU Service Class User: The role played by a DICOM Application Entity
(DIMSEServiceUser), which invokes operations and performs notifications
on a specific Association.
SCP Service Class Provider: The role played by a DICOM Application Entity
(DIMSEServiceUser), which performs operations and invokes notifications
on a specific Association.
Storage SCU The DICOM Application Entity, which performs the role of the service class
user, for the DICOM CSTORE service.
Storage SCP The DICOM Application Entity, which performs the role of the service class
provider, for the DICOM CSTORE service.
Echo SCU The DICOM Application Entity, which performs the role of the service class
user, for the DICOM CECHO service.
Move SCU The DICOM Application Entity, which performs the role of the service class
user, for the DICOM CMOVE service.
Query SCU The DICOM Application Entity, which performs the role of the service class
user, for the DICOM CFIND service.
PDU Protocol Data Unit The fragment of Messages exchanged between peer
DICOM Application Entities.
AE Title Application Entity Title – The representation used to identify the DICOM
nodes communicating between each other.
Calling AE Title It is the Application Entity (AE) which initiates the DICOM messaging service
request. It is based on the Source DICOM Application Name.
Called AE Title It is the Application Entity (AE) which is the intended acceptor of the service
request. It is based on the Destination DICOM Application Name.
Node Term used to represent a combination of AE Title, its port number, IP address
and maximum PDU size. A node is identified by a unique node name.
1.3 References
ACR/NEMA Standards Publications, No PS3 2001 DICOM Standards
Part 1 – Introduction,
Part 2 – Conformance,
Part 3 – Information Object Definitions,
Part 4 – Service Class Specifications,
Part 5 – Data Structures and Encoding,
Part 6 – Data Dictionary,
Part 7 – Message Exchange,
Part 8 – Network Communication Support,
Part 9 – Point to Point Communication Support for Message Exchange Retired,
Part 10 – Media Storage and File Format for Media Interchange,
Part 11 – Media Storage Application Profiles,
Part 12 – Media Formats and Physical Media for Media Interchange,
Part 13 – Print Management PointtoPoint Communication Support – Retired,
Part 14 – Grayscale Standard Display Function
Part 15 – Security Profiles
Part 16 – Content Mapping Resource
This section gives a brief of the application in general. It also describes the commonly used definitions for certain
terms. It also lists the reference documents where further information could be got about the DICOM standard.
The general user interface of the application is described and the actions of each menu items in the menu are
described. Shortcut key combinations, which can be used, are also listed.
Section 3 – Operations
This section describes the various functions that can be performed using the application. Steps to do the required
configuration and all other finer details of the implementation are described.
A few sample sessions have been described. These sample sessions demonstrate most of the functionalities of the
application.
The license agreement, information about the license files and steps on how to register the software are described.
Section 6 – Installation/Uninstallation
Details about the steps for installation and uninstallation of the software are described. The important points to be
considered during installation/uninstallation are also described.
2. User Interface
2.1 Main Window
The main window consists of
· A menu item area, using which all the application functions can be performed.
· A mode window, which contains nine buttons, used to switch between the various modes.
· An area below the mode window, which will have
ـthe AE Title and Configure nodes button displayed when the application is in Storage SCP mode
ـCalling AE Title, Called AE Title, the node name and Configure nodes button displayed for Storage
SCU, Query SCU and Echo SCU modes
ـCalling AE Title, Called AE Title, the node name and Configure nodes and Configure Destination AE
Titles buttons for Move SCU mode.
· A threeview display window having a tab control for displaying the Local result and Remote result for the
corresponding mode the application is in and the Log view.
· An area above the tab control where the buttons dynamically change for the corresponding mode and using
which the operations are performed for the particular mode.
· On the top right corner are two buttons CLEAR and CLEAR ALL, which are used to clear the contents from
the display area. These two buttons will be present for all modes except Image mode.
2.2 Menu
Creates a new session and allows to perform the DICOM operations. By default when the application is launched a
new session is created.
Open Session
Allows opening a saved session. All the saved information will be displayed in the display areas. More operations
may be performed in the opened session.
Save Session
Saves the currently open session. If a session with a same name exists, you will be prompted on whether to overwrite
the existing session or a new session will be created.
Save Session As
License
Displays the license dialog where the product could be registered by entering the license key.
Exit
Exits the application. When the application is receiving or sending data over the network, the Exit menu item and the
close button will be disabled, and you will not be able to exit the application. Cancel the current transmission and/or
stop the storage SCP service before you exit the application
Clear All
Clears the information from all the display areas in the application.
The focus is set to the local tab its contents are displayed.
Remote Report
The focus is set to the remote tab its contents are displayed.
Log
The focus is set to the log tab its contents are displayed.
Refer to the section 3.9 View the Results for more details about the display views
Storage SCU
Query SCU
Move SCU
Echo SCU
Image
Displays the general configuration dialog, where the following parameters can be set. Calling AE Title, Startup Mode,
Log File Name and Number of Days in Log.
Nodes
Brings up the storage SCP node details property sheet when the application is in storage SCP mode or if it is any one
of the other modes, it brings up the DICOM node details dialog.
Displays the help information for the OTDICE software in a separate window. This will be implemented in the forth
coming Version. For this Version this document serves as the Help.
About OTDICE
3. Operations
The application uses a modebased operation. The available modes are Storage SCU, Storage SCP, Query SCU
Move SCU, Echo SCU and Image. The Storage SCP mode also handles echo requests by functioning as an Echo
SCP. Only one mode will have the prominence at any point of time. For example, when Storage SCP mode is in use,
only functions that are available for Storage SCP mode can be used and it’s settings alone can be configured. The
local and remote tabs will also display the information for that mode alone. If the displayed information has to be seen
for some other mode, the respective mode has to be selected.
3.1 Configuration
3.1.1 General Configuration
The general configuration required are specifying the log file name, the number of days entries should be in the log,
the startup mode, and the calling AE Title. These parameters can be set using the General Configuration dialog,
which can be displayed by selecting the General menu item from the Configuration menu.
This has a list control, which displays all the nodes created using the DICOM node details dialog. It has buttons ADD,
EDIT, DELETE and OK which are used to do the following
ADD – brings up the DICOM Node Details Dialog into which all the node details are entered and
the node created.
EDIT – brings up the DICOM Node Details Dialog, which displays all the information for the
selected node and using which the details can be edited.
DELETE clears the node from the list
OK makes the selected node as the current one.
This has a twopage property sheet, which can be used to set the general node information and the transfer syntax
supported by the node.
Node Name The node name, which is used to represent the current setting
IP Address The IP Address of the node
AE Title The Application Entity Title name
Port Number The port number through which the SCU will initiate any connections
PDU Size The maximum PDU size for this node in bytes
Response Timeout The amount of time the SCU will wait for a response from the SCP in seconds
The IP Address should not exceed 64 characters, the AE Title should not exceed 16 characters and the PDU Size
should be a value in the range between 8192 and 65536 bytes. For more details about the valid characters and the
valid length that can be used, please refer to ACR/NEMA Standards Publications, No PS3, 2001 DICOM Standards
Part5 – Data Structures and Encoding.
The transfer syntaxes page has a list of transfer syntaxes. A check box is displayed in each one of the listed transfer
syntax, which can be checked to indicate that the node supports the checked transfer syntaxes. The Check All check
box is used to check all the transfer syntaxes displayed in the list.
A word of caution here – Please do not edit the registry settings unless you are 100% sure of what you are doing.
The specifics provided here are only for informational purpose. Improper use of registry settings in extreme cases
may even lead to an unmountable system.
Two support files imgtypes.dat and qrykeys.dat are used by the application.
Imgtypes.dat contains the abstract syntax of the image types supported by the application. These entries will be
displayed in the Image types tab of the Storage SCP node details configuration property sheet. When a new image
type is added from the application, this file will be updated with that entry.
Qrykeys.dat contains details of the entire key attributes used for query and move. The application uses the
information available in this file to populate the Setup Query and Setup Move dialog.
License Files
A file with a name OTDICE.Lic will be created in the folder path where the application was installed. This file will be
used by the application for authentication purpose by the application. Please do not edit these file for any reason.
Doing so will corrupt the license and the application may not run properly. Uninstalling the software will not remove
this file. Please do not delete this file if the software has to be reinstalled. If it is removed, the license will become
void and the software will not run upon reinstallation.
The send list consists of a file name list, which is a repository of the files to be sent. Files could be added to the list or
removed from it. When a file in the list is selected by clicking on it, on the top left side of the dialog a thumbnail view
of the image will be displayed and on the top right side of the dialog a brief information about the file will be displayed.
The information includes the Patient Name, Patient ID, SOP class name and Transfer Syntax of the image. It also
informs whether the selected file is a Part10 format DICOM file or not.
ADD button – The file dialog will be displayed when this button is clicked. Choose the files
needed and hit OK, they will be added to the list.
REMOVE button – Selecting a file and clicking on this button will remove it from the list. Also, after
the file is sent to any remote node successfully, it will be removed from this list.
UPDATE FILES check box – Checking this will edit all the attributes setup in the Update Attributes dialog on
the images in the list. Unchecking will not apply the edit the attributes in the list.
The files will be updated when the Send List dialog is closed using the CLOSE
button.
UPDATE ATTRIBUTES button – Brings up the Update Attributes dialog where the attributes to be updated in the
files can be setup.
COMPRESS button – Compresses the selected file according to the compression type selected in the
Compression Type combo box.
COMPRESS TYPE combo box – The type of compression to be used can be specified using this combo box.
Further explained in the following section.
3.4.1 Compression
1. Any uncompressed part10 format image having bits stored value of 8 or 12 or 16 can be compressed. (ie)
images which have the transfer syntax of LittleEndianExplicitVR or LittleEndianImplicitVR or
BigEndianExplicitVR.
2. As soon as an image is selected in the send list, the possible types of compression that can be performed
on that image will be displayed in the compression types combo box.
3. If compression cannot be performed on the image, the compression types combo box will remain disabled.
4. The following are the types of compression that can be performed
5. After choosing the compression type click on the compress button. A message box will be displayed whether
the image was successfully compressed or not.
6. If the file was successfully compressed, the file will be overwritten with the new compressed pixels as a part
10format file. The new meta header will have the new compression transfer syntax UID given below, OTech
implementation version name, OTech implementation class UID.
For e.g. – Some 5 images are available in the list. The Study date attribute has to be set to the current date in all the
files.
Click on Update Attributes button and bring up the Update Attributes dialog. Add the study date attribute’s group and
element number and choose CURRENT_DATE value in the value field. Click on Update button to add the study date
item to the list. Close the dialog. Now check the Update Files check box. When closing the send list dialog, the study
date attribute will be edited with the current date value in all the 5 images in the list.
After the files are updated with the attributes setup, the file will be rewritten to the disk with the edited attributes. If it
fails, a message box will be displayed that an error has occurred and whether to proceed further or not.
1. Click on the UPDATE ATTRIBUTES button to bring up the Update Attributes dialog.
2. To enter an attribute, enter the group number, element number and the value in the appropriate combo
boxes and click on the UPDATE button. The attribute will be added to the attributes list.
3. To edit an attribute in the attribute list, click on the attribute to be edited. The values will be displayed in the
group number, element number and value combo boxes. Edit the value and click on UPDATE button. The
changes will be reflected on to the attributes list.
4. To delete an attribute, select it and hit the DELETE button to remove it.
5. Three preset values are available in the combo box. They can be selected by using the dropdown combo
box labeled ‘Value’.
CURRENT DATE
This will apply the current date to the attribute on the images in the list.
CURRENT TIME
This will apply the current time to the attribute on the images in the list.
6. If the default UID Root has to be overridden, enter the new UID Root to be used in the Use UID Root edit
box.
7. These values will be preserved in the registry and will show up each time the dialog is displated. Use the
Update File check box in the Send List dialog to decide whether to apply these attributes to the images in
the list or not.
8. Any valid DICOM attribute or private attribute can be entered in this dialog.
This has a threepage property sheet, which is used to set the general node information, the transfer syntaxes
supported by the node and the image types supported by the node.
The AE Title should not exceed 16 characters and the PDU Size should be in the range between 8192 and 65536
bytes. For a more details about the valid characters and the valid length that can be used, please refer to ACR/
NEMA Standards Publications, No PS3, 2001 DICOM Standards Part5 Data Structures and Encoding.
The image types page has a list where all the image types and their respective SOP class UIDs can be added, edited
and deleted using the ADD, EDIT and DELETE buttons. A check box is displayed in each image types, which can be
checked to indicate that the node supports the checked image types. The Check All check box can be used to select
all the image types.
Further, clicking on ADD will bring up the Image Type details dialog. The Image Type details dialog has two edit
boxes, one for entering the image type and another for entering the SOP Class UID. Enter values for them and hit OK
button. The Name field is just a reference to represent the SOP Class UID and so any name could be given. Also any
SOP Class UID could be entered as it will not be validated. Entering a wrong SOP Class UID could make the SCP
not to accept that particular image type. So, please refer to the standard and enter the correct value for the SOP
Class UID and a reasonable name to represent it. The newly entered image type will be added to the list in the Image
The transfer syntax page has a list of transfer syntaxes. A check box is displayed for each one of the transfer syntax
listed, which can be checked to indicate that the node supports the checked transfer syntaxes. The Check All check
box can be used to select all the transfer syntaxes.
The Setup Query dialog – From the General Page, the following parameters can be setup.
Information Model – The type of information model used to perform the query. The supported information
models are Patient Root, Study Root, Patient /Study Only Root and Modality Worklist
Information models.
Query Level – The query level to be used to perform the query. The supported query levels are Patient,
Study, Series and Image levels.
CLEAR ATTRIBUTES – Clears the current query key set.
The list control below displays all the General query keys available for the type of the information model and the
query level selected. To enter a value for a query key, select the attribute and double click on the value column.
This will bring up an edit control on the item with the existing value displayed on the control. Edit the value and to
save it hit the ENTER key or to revert back to the old value hit the ESCAPE key.
Checking the check box in the attributes, which has to go into the query, will add that attribute to the query key. To
clear the currently selected query keys, click on Clear Attributes button. Clicking on Clear Attributes will also clear all
the query keys and values set in the Additional attributes list.
The Setup Query Dialog – From the Additional Attributes page all the additional keys can be set which has to go into
the query. In general, most of the type 3 attributes are listed in the Additional Attributes list.
1. Only items which have the checkbox checked would be included in the query
2. A blank entry would be considered as a universal match query. This is similar to including ‘*’ character alone in a
query. E.g. just include Patient Name in the query. Leave the Value field for it blank. This would mean something like
(select all patient names from FOR_EG_ARCHIVE).
3. An ‘*’ character could be included in the value field. Entering a ‘*’ character alone conveys the same meaning as a
blank entry. It could be used in conjunction with any other characters. E.g. To query all patient names starting with
the character ‘P’ a value like ‘P*’ could be entered.
4. The ‘?’ character could be used for performing a single character match query. E.g. To query all patients with 3
character names and have the first letter J, the query value could be ‘J??’.
5. The ‘?’ and ‘*’ could also be used in combination on a same value field. E.g. ‘*Ja??c*’
6. Date and Time values matching and UID list matching can also be queried.
Please refer to the DICOM Standard PS3.4 for further information on the types of matching and the characters
allowed in a query key for each type of matching and the VR.
Information Model – The type of information model used to perform the query. The supported
information models are Patient Root, Study Root and Patient /Study Only Root
Information models.
Retrieve Level – The query level to be used to perform the query. The supported query levels are
Patient, Study, Series and Image levels.
UID – Enter the identifier in this edit box. The label for this edit box will change
depending on the Retrieve level selected. For ex. If Patient Level is selected it
will display “Enter Patient ID” and so on. For study, series and image levels,
enter the appropriate UIDs. Wild card characters can be entered as explained in
the subsection “Ways to represent the query” in section 3.6.1. Multiple UIDs can
also be queried for by entering all the UIDs delimited by the ‘\’ character like
“1.2.3.333.333\1.2.4.444.444\1.2.2.222.222”.
6. Set the Destination AE Title on the main window. This will display all the available AE Titles in the
application. Additionaly you may overtype on the combo box to enter a different destination AE Title. The
newly entered AE Title will also be saved until another new AE Title is entered.
7. The Storage SCP available in OTDICE also can run and its AE Title could be the Destination AE Title. Any
other AE Title could also be specified.
8. Click on the Move button to perform move.
9. While the move is in progress, it can be canceled by clicking on the CANCEL button.
10. Interpret the dumped information.
Displays the images in each frame one after another in a loop thereby creating a cine run.
As we move through the frames, the frame number will be displayed on the status bar.
value displayed on the control as shown in the figure below. Edit the value and to save it hit the ENTER key
or to revert back to the old value hit the ESCAPE key.
4. To delete an attribute, select the attribute and click on the Delete button. Clicking on any item in a sequence
will delete the entire sequence attribute.
5. To add a sequence to the Image Data set, click on the Add Sequence button. This will bring up the
sequence dialog shown in the figure below.
a. Click on the Add button of Sequence Element dialog to add the sequence attribute.
b. Click on the Item Begin button to start the sequence.
c. Add the Sequence attributes by clicking on the Add button.
d. Click on the Item End button to end the item.
e. Continue to add the other items after this item.
f. To end the sequence, click on the Item End button and then on Sequence End button.
g. To edit an attribute in the sequence, click on the Edit button on Sequence Element dialog.
h. To delete an attribute in the sequence, click on the Delete button on the Sequence Element dialog.
i. Finally click Ok button to add the sequence to the chosen image.
6. To edit a sequence to the Image Data set, select any item of the sequence attribute to be edited and click on
the button. The sequence dialog will be displayed with all the attributes. Edit the needed attributes in the
manner specified above.
7. Click on the Close button to close the Edit mode. When it is closed and if the contents have been edited, a
message will be prompted that the contents of the file have been modified and whether the changes have to
be saved. Clicking YES will bring up the Save File dialog. Enter a file name to save the changes made. By
default, the same file name will appear. A message will be prompted if the file has to be overwritten.
Clicking YES will overwrite the changes to the file.
3.9 Results
OTDICE displays all the DICOM messages transferred in the local, remote and log tabs. The tab control can be
clicked to navigate between the three views. Alternately, they can be viewed by selecting the appropriate menu item
from the View menu.
Local Result
The local result window will display the information it transmitted to the remote node. For example, in Storage SCU
mode it will display the association request it makes to the SCP, and the dataset that was transmitted if the request
was successful. In Storage SCP mode, it will display the response for the association request that it received.
Remote Result
The remote result window will display the information that is received from the remote node. For example, the remote
result window of storage SCU will display the information sent by the remote node. The remote result window of the
storage SCP will display the information sent by the requesting node.
Log
The log window will display brief information regarding message transfer states, error/warning conditions and final
statuses, etc.
3.10 Sessions
The messages displayed by the DICOM operations performed using OTDICE can be saved and retrieved later. By
default when the application is launched a new session is created.
Create Session
Select New Session from the File menu item. A new session will be created.
Open Session
Select Open Session from the File menu item. Previously saved sessions will be opened and the information will be
displayed in the respective display area. More operations can be performed in the opened session.
Save Session
Select Save Session from the File menu item to save the currently open session. If a session with a same name
exists, you will be prompted on whether to overwrite the existing session or a new session will be created. Save
Session As menu item can also be used to save an open session with a different session name.
Session Files
When any session is saved, a session file with the session name “SAMP_SESS.ses” will be created. A folder with the
same name will also be created. Inside the folder nine *.txt files with the following file names will be created.
EchoSCULocal.txt
EchoSCURemote.txt
MoveSCULocal.txt
MoveSCURemote.txt
QuerySCULocal.txt
QuerySCURemote.txt
StoreSCPLocal.txt
StoreSCPRemote.txt
StoreSCULocal.txt
StoreSCURemote.txt
OTDiceLog.txt
If the session file and the corresponding folder are deleted, the application will not be able to open the saved session,
as it will not be able to find them.
4. Sample Sessions
Seven sample sessions are provided below with each describing the test scenario, the steps taken to perform the test
and the expected results.
Test Scenario
Send an image using DICOM CSTORE service demonstrating the usage of Storage SCU and storage SCP services.
Here we try to send the images to the same machine. A single instance of OTDICE application is launched and the
storage SCP service is started. Switching to storage SCU mode, we select the files and the storage SCU initiates a
request and gets a response from the SCP and then sends the images.
Steps
From the File menu select New Session, a new session Untitled.ses will be created. In this session we will first
demonstrate the usage of Storage SCP and Storage SCU services.
1. Switch to Storage SCP mode by either clicking on the STORAGE SCP button in the main display or by
selecting Storage SCP menu item from the Modes menu
2. Click on CONFIGURE NODES button or select Nodes menu item from the Configure menu and bring up the
Storage SCP Node Details Dialog.
3. For our sample session enter the following values,
Results
The local result window of the storage SCU will display information sent by the storage SCU. It will display the
request made to the remote node, and the dataset that was transmitted if the request was successful.
The remote result window of storage SCU will display the information sent by the remote node.
The local result window of the storage SCP will display the information sent to the requesting node.
The remote result window of the storage SCP will display the information sent by the requesting node.
The log window will display brief information regarding message transfer states, error/warning conditions and final
statuses.
The log
Test Scenario
Send and store two 8bit compressed images. Demonstrates using compression and updating certain attributes of the
images to be sent on the fly.
Steps
From the File menu select New Session, a new session Untitled.ses will be created.
1. Switch to Storage SCP mode by either clicking on the STORAGE SCP button in the main display or by
selecting Storage SCP menu item from the Modes menu
2. Click on CONFIGURE NODES button or select Nodes menu item from the Configure menu and bring up the
Storage SCP Node Details Dialog.
3. For our sample session enter the following values,
10.1 Click on the ADD button of Send List Details dialog to add 2 uncompressed images whose Bits
Stored value is 8.
10.2 Select the first image in the list, choose 8 BIT LOSSY from the compression type combo box and
click on Compress button. The image will be compressed and the new header information will
display the compression transfer syntax. Likewise, compress the second image also.
10.3 Click on the Update Attributes button and bring up the Update Attributes dialog.
10.4 Enter the Group Number, Element Number and Value for the attribute to be added and Click on
Update button. Click on Ok button and return to Send List Details dialog.
For this sample session, add the attribute Treatment Date. Enter the Group number 3008 and
Element number 0250 and value as 01252002. After the files are sent, these values could be seen
from the dump of the files.
10.5 Now check the Update Files check box in the Send List Details dialog and close the dialog. The
attribute will be updated in both the image files.
11. Finally click on the SEND button, which will transfer the images to the images received folder specified in the
storage SCP node details configuration dialog.
Results
The local result window of the storage SCU will display information sent by the storage SCU. It will display the
request made to the remote node, and the dataset that was transmitted if the request was successful.
The remote result window of storage SCU will display the information sent by the remote node.
The local result window of the storage SCP will display the information sent to the requesting node.
The remote result window of the storage SCP will display the information sent by the requesting node.
The log window will display brief information regarding message transfer states, error/warning conditions and final
statuses.
The log
Checks the Echo SCU and Echo SCP services. In this case the Storage SCP service takes the role of the Echo SCP
service
Steps
1. Keep the configuration details created for the sample session 1 for both the storage SCP node and the
DICOM node (test_node).
2. Start storage SCP mode if it is not already started.
3. Switch to Echo SCU mode by either clicking on the ECHO SCU button in the main display or by selecting
Echo SCU menu item from the Modes menu
4. Now you can see storescp value come up in the Called AE Title in the main window.
5. Select storescp value in the Called AE Title combo box in the main window.
6. Finally click on the SEND button to initiate an Echo request.
Results
The echo succeeds and the log window displays the status of the operations.
The log
Steps
Result
The storage of the image file fails, as the storage SCP is unable to recognize the called AE Title. The error message
is displayed in the log window.
Log Window
Make an Echo request from SCU when the SCP is not ready
Steps
Result
The Echo request will fail since there is no echo SCP running to respond to the request.
Log Window
Steps
1. First create a new session by selecting the New Session menu item of File Menu.
2. Switch to Query SCU mode by either clicking on the Query SCU button in the main display or by selecting
Query SCU menu item from the Modes menu
3. Ensure that the remote query SCP against which the query has to be made is running. (Query SCP is not
available in OTDICE)
4. Click on Configure Nodes button and click on the ADD button and bring up the DICOM Node details dialog
to create a node.
Enter the values of the remote query SCP service (the values given here are sample values),
For e.g. In the General page (assuming these could be query SCP’s values),
Node Name test_node2
AE Title queryscp
Port Number 104
Maximum PDU Size 65536 bytes
IP Address Give the SCP’s IP address
Response Timeout 10 seconds
In the Transfer Syntax page,
For this sample session click on the Check All check box. Checking Check All ensures that the Query SCU
will propose all the syntaxes specified in the list. Select the created node and click on OK button.
5. Now you can see queryscp value come up in the Called AE Title in the main window.
6. Bring up the General Configuration dialog box by choosing General menu item from the configure menu.
Enter queryscu in the calling AE Title.
7. Now you can see queryscu value come up in the Calling AE Title in the main window.
8. Click on the Setup Query button to form the query to be executed. Once the Setup Query button is clicked
Setup Query dialog pops up.
8.1 Clear any existing query key values by clicking on the Clear Attributes button in the General page of
Setup Query dialog.
8.2 In the General page of Setup Query dialog choose the Information Model, Query Level and Attributes to
form the query. Values can be specified to attributes by double clicking the corresponding Value
column.
For this Sample Session, choose Patient Root as Information Model and PATIENT as the query level
and check both the attributes in the list. Ensure that the Query SCP supports Patient Root Query
Information model.
8.3 Additional attributes can also be included in the query by selecting the attributes in Additional Attributes
page of Setup Query dialog.
For this Sample Session, check Patient’s Birth Date and Patient’s Sex attributes.
Results
The querying process succeeds if the Query SCU and Query SCP nodes are configured properly. The remote result
of query SCU will display what went on in the local side of the query SCP and vice versa.
Steps
1. First create a new session by selecting the New Session menu item of File Menu.
2. Switch to Move SCU mode by either clicking on the Move SCU button in the main display or by selecting
Move SCU menu item from the Modes menu
3. Ensure that the remote move SCP against which the move has to be requested is running. (Move SCP is
not available in OTDICE)
4. Click on Configure Nodes button and click on the ADD button and bring up the DICOM Node details dialog
to create a node.
5. Configure a destination node. For this session use the storage SCP availlable in OTDICE itself as the
destination. Configure the sotrage SCP and start it to accept associations and store images as explaied in
Section 3.5.
6. Enter the values of the remote move SCP service (the values given here are sample values)
For e.g. In the General page (assuming these could be move SCP’s values),
Node Name test_node2
AE Title movescp
Port Number 104
Maximum PDU Size 65536 bytes
IP Address Give the SCP’s IP address
Response Timeout 10 seconds
In the Transfer Syntax page,
For this sample session click on the Check All check box. Checking Check All ensures that the Move SCU
will propose all the syntaxes specified in the list. Select the created node and click on OK button.
7. Now you can see movescp value come up in the Called AE Title in the main window.
8. Bring up the General Configuration dialog box by choosing General menu item from the configure menu.
Enter movescu in the calling AE Title.
9. Now you can see movescu value come up in the Calling AE Title in the main window.
10. Select a Destination AE Title. If the Destination AE Title is not available in the list, enter the AET Title in the
combo box.
11. Click on the Settings button to form the query to be executed. Once the Settings button is clicked Setup
Move dialog pops up. Choose the Information Model, Retrieve Level and enter the identifier asked for.
12. For this Sample Session, choose Patient Root as Information Model and PATIENT as the Retrieve level.
Yoe will be asked to enter the Patient ID. Enter the Patient’s ID whose images have to be moved. You can
use wild card characters also. Please refer to Section 3.6.1 for details on how to use wild card characters.
Ensure that the Move SCP supports Patient Root Query Retrieve Information model.
13. Click on the Move button to perform the move.
Results
The Move process succeeds if the Move SCU and Move SCP nodes are configured properly. The remote result of
move SCU will display what went on in the local side of the move SCP and vice versa. The local and remote storage
SCP results window will display the command set and the datasets of the images moved and also the negotiation
contents.
To activate the product, Click Activate on the right hand side. If you would like to continue to evaluate the product,
click Evaluate. The software will transmit the serial number to the OTech server and obtain the permanent license
key. This may take up to a minute to complete. After the activation process is over, a message box will be displayed
informing you that the software has been successfully activated.
If you are activating the product with a serial number issued for evaluation and you have not paid for a license, you
will receive the following message.
If you would like to pay for a license and activate the installed software, click Validate. It will launch a web browser
and take you to a checkout screen on the OTech website to purchase a license. If you would like to continue to
evaluate the product, click Evaluate.
To activate the product, bring up the Validate License dialog by choosing the License menu item found under the
Application’s File menu. This menu item will be enabled even after the 15day evaluation period and the product
could be registered anytime.
In the Validate License dialog the serial number you entered during installation will be displayed. If you have received
a new serial number, enter it now. Enter your email address and click OK.
The software will transmit the serial number to the OTech server and obtain the permanent license key.
This may take up to a minute to complete. After the activation process is over, a message box will be displayed
informing you that the software has been successfully activated.
To complete activation, email OTech at support @otechimg.com or call (940) 4409791. Provide them with the Hard
Drive Serial Number and OTDICE Serial Number which are displayed in the dialog box. The OTech representative
will give you a Phone Activation code.
Enter the Phone Activation Code in the third box in the dialog titled ‘Phone Activation Code’. A message box will be
displayed informing you that the software has been successfully activated.
PLEASE READ THIS LICENSE CAREFULLY BEFORE INSTALLING THE SOFTWARE. BY INSTALLING AND / OR
USING THE SOFTWARE, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THE LICENSE. IF YOU DO
NOT AGREE TO THE TERMS OF THIS LICENSE, YOU ARE NOT AUTHORIZED TO INSTALL AND / OR USE THE
SOFTWARE.
The OTDICE software consists of executable software, library files, support files, test files and documentation, which
will be collectively referred to as OTDICE.
Restrictions
You are not allowed to decompile, reverse engineer, disassemble or otherwise reduce OTDICE to a human
perceivable form. You may not modify, network, rent, lease, distribute or derivative works based upon OTDICE in
whole or in part. You may not electronically transmit OTDICE over a network.
You expressly acknowledge and agree that use of OTDICE is at your sole risk. OTDICE is provided AS IS and
without warranty of any kind. OTech shall EXPRESSLY DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. OTech DOES NOT WARRANT THAT THE SOFTWARE WILL BE UNINTERRUPTED OR
ERROR FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED.
Limitation of Liability
OTech SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE OR ANY THIRD PARTY AS A
RESULT OF USING OTDICE. IN NO EVENT WILL OTech BE LIABLE FOR ANY LOST REVENUE, PROFIT OR
DATA, OR FOR DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,
HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR
INABILITY TO USE SOFTWARE, EVEN IF OTech HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
Severability
If any of the above provisions are held to be in violation of applicable law, void, or unenforceable in any jurisdiction,
then such provisions are herewith waived to the extent necessary for the License to be otherwise enforceable in such
jurisdiction. However, if in the opinion of OTech deletion of any provisions of the License by operation of this
paragraph unreasonably compromises the rights or increase the liabilities of OTech, OTech reserves the right to
terminate the License.
6. Installation / Uninstallation
6.1 Installation
The OTDICE software comes in a selfextracting installation package.
To install the software double click on the OTDICE_V3.exe application. When prompted, specify the target folder
where you wish the application to be installed.
During installation, you will be asked registration information. Enter your name, company name and the software’s
serial number. You should have received a serial number when you purchased the software or downloaded the trial.
If you do not have a serial number, please email OTech at [email protected] or call (940) 4409791.
Once the software is successfully installed, an icon labeled “OTDICE_V3” will be created on the destktop and an
entry “OTDICE_V3” will be added to the Programs sub menu under the Start menu.
The application can be launched from the desktop by double clicking the icon or by selecting the entry in the Start
>Programs menu. The software has a free evaluation period of 15 days. After the 15day evaluation is over, the
software will not function and a permanent license must be purchased from OTech, Inc. At any time during the 15day
evaluation period or after that you may obtain a permanent license and enter the license in the registration dialog.
Please refer Section 2 on how to activate the product.
After the installation process is over, a message box will be displayed informing that the software has been installed
successfully.
6.2 Uninstallation
Go to the control panel and click on the Add / Remove programs icon. Select OTDICE_V3 from the list available and
click on Add/ Remove. The software will be uninstalled.
Alternatively, running the setup exe again when the software is installed will also uninstall the software.
After the uninstallation process is over, a message box will be displayed informing that the software has been un
installed successfully.