DICOM Conformance and Generating graphs: Difference between pages

From MIPAV
(Difference between pages)
Jump to navigation Jump to search
m (1 revision imported)
 
MIPAV>Angelfish100
 
Line 1: Line 1:
=DICOM Conformance Statement=
MIPAV allows you to generate intensity profiles, or contour VOI graphs, for VOI contours. For delineated VOIs, you can generate 2D, 3D, or 4D intensity graphs. You can also generate a 3D intensity graph at a specific point across all slices in a dataset. For information on how to contour a VOI, refer to Chapter 1, "Segmenting Images Using Contours and Masks,"<br />
<div style="font-style: normal; margin-bottom: 6pt; margin-left: 6pt; margin-right: 6pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#0023a9"> In this appendix . . .<br /></font>'''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 1pt; margin-left: 18pt; margin-right: 6pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: -12pt; text-transform: none; vertical-align: baseline"><font color="#0023a9"> "MIPAV" <br />
"MIPAV DICOM communications interface" <br />
"Implementation model" <br />


The purpose of this conformance statement is to facilitate communications and interoperations with the National Institutes of Health (NIH) Medical Image Processing, Analysis, and Visualization program (MIPAV).<br />
=== Generating contour VOI graphs ===
Contour VOI graphs display the intensity values of the selected contour's boundary in the Contour VOI Graph window (Figure 10). You can generate either 2D or 3D contour VOI graphs. <br />


This introduction describes the MIPAV application and briefly summarizes the Digital Imaging and Communications in Medicine (DICOM) standard services employed by MIPAV.
'''To generate 2D contour VOI graphs'''<br />
1 Open an image.<br />
2 Delineate a 2D VOI on the image using one of the 2D icons in the MIPAV window.<br />


== MIPAV ==
MIPAV is an <span style="font-weight: normal; text-decoration: none; text-transform: none; vertical-align: baseline">''<font color="#000000">n</font>''</span>-dimensional, general purpose image-processing program designed to assist the NIH research and clinical communities in extracting quantitative information from various medical imaging modalities to better understand, diagnose, monitor, and treat medical disorders.<br />
MIPAV, which is written in Java, takes advantage of the programming language's intrinsic object-oriented capabilities to improve code reuse, functionality, and portability. MIPAV is available on any Java-capable operating system, such as Windows, Macintosh, Irix, and Solaris.
Although this is a general purpose image-processing platform, Dr. McAuliffe presently uses this platform to develop specific and unique image processing techniques to meet the requirements of his collaborators.
== MIPAV DICOM communications interface ==
The MIPAV DICOM communications interface automates the process of querying and retrieving DICOM standard formatted files. The transfer of images can be clumsy and time consuming when studies are manually transferred to removable media or even to File Transfer Protocol (FTP) access, which does not ensure file format compatibility. MIPAV allows you to transfer DICOM standard formatted images over the network using the DICOM communications protocol that runs over the Transmission Control Protocol/Internet Protocol (TCP/IP) stack.<br />
The MIPAVapplication starts a DICOM image receiver that runs in the background and listens on a given port for incoming DICOM-store requests. When a store request is received by the DICOM receiver, the DICOM-formatted images are saved to the local system disk in the user-designated images directory. Once stored, you can use MIPAV to access, visualize, and analyze images.
MIPAV can also send selected images that are on the local disk to a remote destination by implementing the composite storage (C-STORE) service class as a service class user (SCU).
Finally, and most important, MIPAV has a query and retrieve capability that allows you to query a remote DICOM query server for patient, study, series, and image information. You can select from the responses to the query the set of images to be retrieved (moved) to the local disk for visualization and analysis.
== Implementation model ==
This section describes the application entities (AEs) in the MIPAV DICOM communications interface and how they relate to both local and remote real-world activities. The implementation model consists of an application data flow diagram and functional definitions of all DICOM processes handled by the MIPAV AE.<br />
The MIPAV DICOM receiver conforms to the DICOM standard as a service class provider (SCP) of most C-STORE service object pair (SOP) classes. The MIPAV query/retrieve process conforms to the DICOM standard as a SCU for DICOM C-FIND and C-MOVE services. In addition, the MIPAV DICOM sender conforms to the DICOM standard as a SCU for most DICOM C-STORE SOP classes.
=== Application data flow diagram ===
Figure 1 shows the relationship between the MIPAV AE and its DICOM processes and the remote AE and its DICOM processes. The remote AE could be any DICOM-compliant system that acts as a query/retrieve server and a DICOM image file receiver and sender, such as a DICOM image archive.<br />


{| border="1" cellpadding="5"
{| border="1" cellpadding="5"
|+ <div style="font-style: normal; margin-bottom: 3pt; margin-left: 0pt; margin-right: 0pt; margin-top: 9pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Figure 1. MIPAV dataflow diagram<br /></font>'''</div>
|+ '''Figure 10. Contour VOI Graph window '''
|-
|-
|
| rowspan="1" colspan="3" |
[[Image:MIPAVdataflowdiagram.jpg]]
[[Image:windowContourVOIGraph.jpg]]
|}
 
<br />
 
=== Functional definitions of AEs ===
 
This section describes the image verification, query, and transfer functions to be performed by the MIPAV AE and the DICOM services used to accomplish these functions.
 
=== Verification ===
The MIPAV DICOM communications interface verifies application-level communication with a remote DICOM AE with the C-ECHO (Verification) SOP class in the SCP role. A remote DICOM AE supporting the Verification SOP class SCU role shall send a C-ECHO request to the MIPAV application. The MIPAV AE then sends a response of SUCCESS to confirm DICOM communications between the two AEs.<br />
 
==== DICOM receiver (C-STORE SCP) ====
The DICOM image receiver is initialized as a standalone resident program when the MIPAV application is started. The DICOM receiver waits for a remote AE to request a connection at the presentation address configured for its AE Title. The presentation address of the DICOM receiver consists of the system IP address, AE Title, and communications port. The AE Title and communications port for the DICOM receiver are user configurable in the preferences file mipav.preferences.
 
The DICOM receiver accepts associations with Presentation Contexts for the SOP Classes of the Storage Service Class. Thus, the DICOM receiver accepts storage requests for Computed Tomography (CT), Magnetic Resonance (MR), Ultrasound (US), Nuclear Medicine (NM), Computed Radiography (CR), and most other modalities. It receives the images and writes them to files in the format specified in <span style="font-weight: normal; text-decoration: none; text-transform: none; vertical-align: baseline">''<font color="#000000">Digital Imaging and Communications In Medicine (DICOM) Part 10: Media Storage and File Format for Media Interchange</font>''</span> (see Appendix E for a full citation.)
 
==== DICOM query (C-FIND SCU) ====
 
The MIPAV application supports the DICOM C-FIND query class as a SCU by allowing you to query a remote DICOM query server (C-FIND SCP) for patient, study, series, and image information. MIPAV employs the Study Root Query/Retrieve Information Model based on the three-level hierarchy:
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 5pt; text-align: left; text-decoration: none; text-indent: -24pt; text-transform: none; vertical-align: baseline"><font color="#000000">  <span style="font-weight: normal; text-decoration: none; text-transform: none; vertical-align: baseline">''<font color="#000000">Study</font>''</span>-Study is the top level. It contains attributes associated with the study and patient information entity's (IE). <br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 5pt; text-align: left; text-decoration: none; text-indent: -24pt; text-transform: none; vertical-align: baseline"><font color="#000000">  <span style="font-weight: normal; text-decoration: none; text-transform: none; vertical-align: baseline">''<font color="#000000">Series</font>''</span>-The series level, which is below the study level, contains attributes associated with the series, frame of reference, and equipment IEs.<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 5pt; text-align: left; text-decoration: none; text-indent: -24pt; text-transform: none; vertical-align: baseline"><font color="#000000">  <span style="font-weight: normal; text-decoration: none; text-transform: none; vertical-align: baseline">''<font color="#000000">Image-</font>''</span>Image is the lowest level. It contains attributes associated with the Image IE.<br /></font></div>
 
You can use a Study Root Study Level C-FIND request message, with search key attributes of patient name or patient ID and study date range, to query the SCP for a patient list or for demographic information about a given patient. A Study Root Study Level query, with a known search key attribute of patient ID, can be sent to the Query SCP for the study list corresponding to the given patient ID. Once the desired study is queried, then MIPAV can send a Study Root Series Level query with the known Unique Key Attributes of Patient ID and Study Instance UID to the query server for the list of series corresponding to the given study. Finally, once the desired series is located, you can query at the Study Root Image Level with known Key Attributes of Patient ID, Study Instance UID, and Series Instance UID to get the list of images corresponding to the selected series.
 
The MIPAV query routine interprets all PENDING status responses from the C-FIND SCP as matches to the key attributes in the query request. A status equal to SUCCESS, FAILED or REFUSED conveys the end of query request.
 
To cancel the C-FIND service, the MIPAV AE issues a C-FIND-CANCEL request at any time during the processing of the C-FIND query. The MIPAV query routine that issued the C-FIND request recognizes a status of CANCELED to indicate that the C-FIND-CANCEL was successful.
 
==== DICOM retrieve (C-MOVE SCU) ====
MIPAV supports the DICOM C-MOVE SOP class as a SCU. You can request the transfer of images from a remote AE to the local system or to a desired remote destination with a DICOM C-MOVE service request. The destination for the move, whether it is the local disk or a remote system, may be configured and selected from a host table from within the MIPAV DICOM Communication Panel window. The Move Destination is specified by the parameters of AE Title, IP Address, and Communications Port number in the Hosts table. To review or modify the configuration of the Hosts table, the user selects the Hosts tab from the DICOM Communication Panel window.<br />
 
The DICOM C-MOVE class employs, like the DICOM Query, the Study Root Query/Retrieve Information Model based on the three-level hierarchy:
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 5pt; text-align: left; text-decoration: none; text-indent: -24pt; text-transform: none; vertical-align: baseline"><font color="#000000">  <span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Study</font>'''</span>-A C-MOVE request at the study level transfers all images related to a study to the designated move destination. <br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 5pt; text-align: left; text-decoration: none; text-indent: -24pt; text-transform: none; vertical-align: baseline"><font color="#000000">  <span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Series</font>'''</span>-A C-MOVE request at the series level transfers all images related to a series.<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 5pt; text-align: left; text-decoration: none; text-indent: -24pt; text-transform: none; vertical-align: baseline"><font color="#000000">  <span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Image</font>'''</span>-A C-MOVE request at the image level transfers all selected individual images.<br /></font></div>
 
The MIPAV retrieve routine supplies unique key values to identify an entity at the level of retrieval to the C-MOVE SCP. The SCP executes C-STORE suboperations for the corresponding storage SOP instances identified by the unique key values in the C-MOVE request. The MIPAV retrieve routine interprets all PENDING status responses from the C-MOVE SCP as matches to the key attributes in the retrieve request. A status equal to SUCCESS, FAILED, or REFUSED conveys the end of the retrieve request.
 
The MIPAV AE may cancel the C-MOVE service request by issuing a C-MOVE-CANCEL request at any time during the processing of the C-MOVE request. The MIPAV retrieve routine that issued the C-MOVE request recognizes a status of CANCELED to indicate that the C-MOVE-CANCEL was successful.
 
==== DICOM sender (C-STORE SCU) ====
MIPAV provides the DICOM C-STORE SOP class as a SCU. <br />To access the DICOM send option<br /></font>'''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 18pt; margin-right: 0pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: -18pt; text-transform: none; vertical-align: baseline"><font color="#000000">  1 Select File &gt; DICOM Database Access in the MIPAV window. The DICOM Communication Panel window opens.<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 18pt; margin-right: 0pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: -18pt; text-transform: none; vertical-align: baseline"><font color="#000000">  2 Select Send to view the Send page.<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 18pt; margin-right: 0pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: -18pt; text-transform: none; vertical-align: baseline"><font color="#000000">  3 Select a patient, study, series, or image to send to a designated destination. The store destination is specified by the parameters of AE Title, IP Address, and Communications Port number in the hosts table. <br /></font></div><div style="font-style: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 14pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> To review or modify the configuration of the hosts table<br /></font>'''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 18pt; margin-right: 0pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: -18pt; text-transform: none; vertical-align: baseline"><font color="#000000">  1 Select Hosts in the DICOM Communication Panel window. The Hosts page opens.<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 18pt; margin-right: 0pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: -18pt; text-transform: none; vertical-align: baseline"><font color="#000000">  2 Select the desired image data and the storage destination. <br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 18pt; margin-right: 0pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: -18pt; text-transform: none; vertical-align: baseline"><font color="#000000">  3 Click OK. The MIPAV sender routine establishes an association with the selected destination and transfers the image data.<br /></font></div>
 
==== Sequencing of real-world activities ====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> Not applicable.<br /></font></div>
 
=== AE specifications ===
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> This section provides detailed specifications of the MIPAV DICOM communications interface. It lists the SOP classes supported and outlines the policies with which MIPAV initiates or accepts associations. A description of proposed (for association initiation) and acceptable (for association acceptance) Presentation contexts is also provided.<br /></font></div>
 
Note that a Presentation Context consists of an Abstract Syntax and a list of acceptable Transfer Syntaxes. The Abstract Syntax identifies one SOP Class or Meta SOP Class. By listing the AEs with their proposed and accepted Presentation Contexts, this Conformance Statement identifies the set of Information Objects and Service classes recognized by MIPAV.
 
For each SOP Class related to an Abstract Syntax, a list is given of any supported SOP options.
 
==== MIPAV AE specification ====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> This section summarizes the SOP classes that are supported by the MIPAV DICOM Communications interface. The supported SOP classes are listed in two categories: <br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 5pt; text-align: left; text-decoration: none; text-indent: -24pt; text-transform: none; vertical-align: baseline"><font color="#000000">  SOP classes supported by MIPAV as a SCU<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 5pt; text-align: left; text-decoration: none; text-indent: -24pt; text-transform: none; vertical-align: baseline"><font color="#000000">  SOP classes supported by MIPAV as a SCP<br /></font></div>
 
MIPAV provides Standard Conformance to the DICOM V3.0 SOP Classes shown in Table 1 as a SCU.
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> <br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
 
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 1.  DICOM query, retrieve, and sender classes supported by MIPAV</div>
|- bgcolor="#CCCCCC"
!
<div class="CellHeading">SOP class name</div>
!
<div class="CellHeading">SOP class UID</div>
|-
|-
| rowspan="4" colspan="1" |
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">File</font>'''</span></div>
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 6pt; margin-left: 6pt; margin-right: 6pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> <span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">DICOM query</font>'''</span><br /></font>'''</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Open Graph</font>'''</span>-Opens a PLT file that contains graph data. When you select this command or press Ctrl O on the keyboard, the Open Graph Data dialog box appears. </div>
|-
|-
|
| rowspan="1" colspan="2" |
<div class="CellBody">Study Root Query/Retrieve Information Model, C-FIND</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Save Graph</font>'''</span>-Saves the graph data in a PLT file. When you select this command or when you press Ctrl S on the keyboard, the Save dialog box opens.</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.2.2.1</div>
|-
|-
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 6pt; margin-left: 6pt; margin-right: 6pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> DICOM retrieve<br /></font>'''</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Print Graph</font>'''</span>-Allows you to print the graph. When you select this command or press <br />Ctrl P, the Print dialog box opens.</div>
|-
|-
|
| rowspan="1" colspan="2" |
<div class="CellBody">Study Root Query/Retrieve Information Model, C-MOVE</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Close Graph</font>'''</span>-Closes the Intensity Graph window. To close the window, you can also press Ctrl X on the keyboard.</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.2.2.2</div>
|-
|-
| rowspan="3" colspan="1" |
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Edit</font>'''</span></div>
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 6pt; margin-left: 6pt; margin-right: 6pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> DICOM sender<br /></font>'''</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Delete Function</font>'''</span>-Allows you to delete a specific function. However, you cannot delete a function if it is the only function displayed in the window.</div>
|-
|-
|
| rowspan="1" colspan="2" |
<div class="CellBody">CR Image Storage</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Copy Function</font>'''</span>-Copies a function that is currently displayed in the window.</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.1</div>
|-
|-
|
| rowspan="1" colspan="2" |
<div class="CellBody">CR Image Storage</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Paste Function</font>'''</span>-Pastes a previously copied function into the window. The pasted function has a different color than the first function displayed in the window.</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.2</div>
|-
|-
|
| rowspan="3" colspan="1" |
<div class="CellBody">MR Image Storage</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Views</font>'''</span></div>
|
| rowspan="1" colspan="2" |
<div class="CellBody">1.2.840.10008.5.1.4.1.1.4</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Modify Graph Features</font>'''</span>-Allows you to customize the appearance of the graph.</div>
|-
|
<div class="CellBody">NM Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.20</div>
|-
|
<div class="CellBody">US Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.6</div>
|-
|
<div class="CellBody">Secondary Capture Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.7</div>
|}
 
MIPAV provides Standard Conformance to the DICOM version 3.0 SOP Classes shown in Table 2 as a SCP.
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
 
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 2.  Verification and DICOM receiver classes supported by MIPAV</div>
|- bgcolor="#CCCCCC"
!
<div class="CellHeading">SOP class name</div>
!
<div class="CellHeading">SOP class UID</div>
|- bgcolor="#CCCCCC"
!
<div style="font-style: normal; margin-bottom: 6pt; margin-left: 6pt; margin-right: 6pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Verification<br /></font>'''</div>
!
<div class="CellBody">Â </div>
|-
|
<div class="CellBody">Verification SOP Class</div>
|
<div class="CellBody">1.2.840.10008.1.1</div>
|-
|-
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 6pt; margin-left: 6pt; margin-right: 6pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> DICOM receiver<br /></font>'''</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Reset Range to Default</font>'''</span>-<span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">[TBD]</font>'''</span></div>
|-
|
<div class="CellBody">CR Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.1</div>
|-
|
<div class="CellBody">CT Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.2</div>
|-
|-
|
<div class="CellBody">MR Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.4</div>
|-
|
<div class="CellBody">NM Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.20</div>
|-
|
<div class="CellBody">US Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.6</div>
|}
<br /></font></div>
==== DICOM query (C-FIND SCU) AE specification ====
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> MIPAV provides standard conformance to the DICOM 3.0 Query/Retrieve SOP class listed in Table 3.<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 3.  Supported C-FIND SOP class</div>
|- bgcolor="#CCCCCC"
!
<div class="CellHeading">SOP class name</div>
!
<div class="CellHeading">SOP class UID</div>
|-
|
<div class="CellBody">Study Root Query/Retrieve Information Model</div> <div class="CellBody">C-FIND</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.2.2.1</div>
|}
<br /></font></div> <div class="CellBody"><br /></div>
===== Association establishment policies =====
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> General<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The MIPAV query routine initiates an association with a remote DICOM query server. Extended negotiation is not provided.<br /></font></div>
The maximum Protocol Data Unit (PDU) size in an association request defaults to 16 kilobytes.
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Number of associations<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> Each query request within MIPAV initiates an association with a remote DICOM query server. Thus, multiple associations can be opened and processed by MIPAV in one working session.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Asynchronous nature<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The DICOM Query routine only allows a single outstanding operation on an Association. Thus, there is no asynchronous activity in this implementation.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Implementation identifying information<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> (TBD. Need information on the Implementation Class Unique Identifier (UID) for the MIPAV query routine.<span style="font-style: normal; font-weight: normal; text-decoration: none; text-transform: none; vertical-align: baseline"><font color="#ff0000"> </font></span>Note that this may be the same for all applications, one implementation UID for a DICOM application. For information, contact Richard Eaton at NEMA at 703/841-3248 or e-mail at ric_eaton@nema.org).<br /></font></div>
===== Association initiation by real-world activity =====
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> To initiate an association from MIPAV to a remote query server (C-FIND SCU), select the Send Query button in the DICOM Communication Panel window.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Query request<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> After you insert the search keys and set the study date range in the DICOM Communication Panel window, you can then select the Send Query button to transfer the C-FIND request to the remote DICOM query server. Each query opens an association with the query server. Select Cancel at the bottom of the DICOM Communication Panel window to cancel the C-FIND request. The C-FIND-CANCEL request is sent over the same association as the originating C-FIND request.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Associated real-world activity<br /></font>''</div>
The initiation of a C-FIND request is the associated real-world activity.
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Proposed Presentation Contexts <br /></font>''</div>
When MIPAV initiates a C-FIND request, a presentation context is proposed for the Study Root Query/Retrieve C-FIND supported SOP Class. No extended negotiation is supported.
<div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 4.  Presentation context proposed by MIPAV as a result of real-world activity query request to an external query server</div>
|- bgcolor="#CCCCCC"
! rowspan="1" colspan="6" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Presentation context table<br /></font>'''</div>
|-
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Abstract syntax<br /></font>'''</div>
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Transfer syntax<br /></font>'''</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Reset Graph to Original</font>'''</span>-<span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">[TBD]</font>'''</span>. </div>
| rowspan="2" colspan="1" |
<div class="CellHeading">Role</div>
| rowspan="2" colspan="1" |
<div class="CellHeading">Extended negotiation</div>
|-
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Name <br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> UID<br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Name list<br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> UID list<br /></font>'''</div>
|-
|
<div class="CellBody">Study Root Q/R C-FIND</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.2.2.1</div>
|
<div class="CellBody">Implicit VR Little Endian</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|
<div class="CellBody">SCU</div>
|
<div class="CellBody">None</div>
|}
 
<br /></font></div>
 
===== SOP specific conformance statement for SOP class study root query/retrieve information model C-FIND =====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The attributes listed in Table 5 comprise the Study Root Query/Retrieve C-FIND identifier that is sent in the DICOM query message. The level column indicates the query level at which the attributes can be included.<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
 
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 5.  DICOM data elements supported for SOP class study root query/retrieve information model C-FIND SCU"</div>
|- bgcolor="#CCCCCC"
!
<div class="CellHeading">Level</div>
!
<div class="CellHeading">Description</div>
!
<div class="CellHeading">Tag</div>
!
<div class="CellHeading">Type</div>
|-
| rowspan="1" colspan="4" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Study<br /></font>'''</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Study Date</div>
|
<div class="CellBody">(0008,0020)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Study Time</div>
|
<div class="CellBody">(0008,0030)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Study ID</div>
|
<div class="CellBody">(0020,0010)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Patient's Name</div>
|
<div class="CellBody">(0010,0010)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Patient ID</div>
|
<div class="CellBody">(0010,0020)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Study Instance UID</div>
|
<div class="CellBody">(0020,000D)</div>
|
<div class="CellBody">U</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Referring Physician's Name</div>
|
<div class="CellBody">(0008,0090)</div>
|
<div class="CellBody">O</div>
|-
| rowspan="1" colspan="4" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Series<br /></font>'''</div>
|-
|
<div class="CellBody">Series</div>
|
<div class="CellBody">Modality</div>
|
<div class="CellBody">(0008,0060)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Series</div>
|
<div class="CellBody">Series Number</div>
|
<div class="CellBody">(0020,0011)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Series</div>
|
<div class="CellBody">Series Instance UID</div>
|
<div class="CellBody">(0020,000E)</div>
|
<div class="CellBody">U</div>
|-
|
<div class="CellBody">Series</div>
|
<div class="CellBody">Series Date</div>
|
<div class="CellBody">(0008,0021)</div>
|
<div class="CellBody">O</div>
|-
|
<div class="CellBody">Series</div>
|
<div class="CellBody">Series Description</div>
|
<div class="CellBody">(0008,103E)</div>
|
<div class="CellBody">O</div>
|-
|
<div class="CellBody">Series</div>
|
<div class="CellBody">Body Part Examined</div>
|
<div class="CellBody">(0018,0015)</div>
|
<div class="CellBody">O</div>
|-
| rowspan="1" colspan="4" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Image<br /></font>'''</div>
|-
|
<div class="CellBody">Image</div>
|
<div class="CellBody">Image Number</div>
|
<div class="CellBody">(0020,0013)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Image</div>
|
<div class="CellBody">SOP Instance UID</div>
|
<div class="CellBody">(0008,0018)</div>
|
<div class="CellBody">U</div>
|-
|
<div class="CellBody">Image</div>
|
<div class="CellBody">Image Date</div>
|
<div class="CellBody">(0008,0023)</div>
|
<div class="CellBody">O</div>
|-
|
<div class="CellBody">Image</div>
|
<div class="CellBody">Image Time</div>
|
<div class="CellBody">(0008,0033)</div>
|
<div class="CellBody">O</div>
|}
 
<br /></font></div>
 
===== Association acceptance policy =====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> Not applicable.<br /></font></div>
 
==== DICOM retrieve (C-MOVE SCU) AE specification ====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> MIPAV provides standard conformance to the DICOM 3.0 Query/Retrieve SOP class.<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
 
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 6. Supported image storage service</div>
|- bgcolor="#CCCCCC"
!
<div class="CellHeading">SOP class name</div>
!
<div class="CellHeading">SOP class UID</div>
|-
|-
|
|
<div class="CellBody">Study Root Query/Retrieve Information Model</div> <div class="CellBody">C-MOVE</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Help</font>'''</span></div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.2.2.2</div>
|}
 
<br /></font></div>
 
===== Association establishment policies =====
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> General<br /></font>''</div>
 
The MIPAV retrieve routine initiates an association with a remote DICOM query/retrieve server. Extended negotiation is not provided.
 
The maximum PDU size in an association request defaults to 16 kilobytes.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Number of associations<br /></font>''</div>
 
Each retrieve (C-MOVE) request within the MIPAV application initiates an association with a remote DICOM query/retrieve server. Thus, multiple associations for the C-MOVE SOP class can be opened and processed by MIPAV in one working session.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Asynchronous nature<br /></font>''</div>
 
The DICOM Receiver only allows a single outstanding operation on an association. Thus, there is no asynchronous activity in this implementation.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Implementation identifying information<br /></font>''</div>
 
(TBD. Need the Implementation Class Unique Identifier (UID) for the MIPAV move request routine. Note that this may be the same for all applications-one implementation UID for a DICOM application. For information, contact Richard Eaton at NEMA at 703/841-3248 or e-mail at ric_eaton@nema.org.
 
===== Association initiation by real-world activity =====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> To initiate an association from MIPAV to a remote query/retrieve server (C-MOVE SCP), select Q/R Client in the DICOM Communication Panel window. Then complete the appropriate parameters in the Q/R Client page. Initially run a query from the Q/R Client page. You can then select an entry from the query responses that indicates the desired patient, study, series, or image to be moved to the set destination. The destination to be moved to with the C-MOVE request is user configurable in the Hosts page, which is in the DICOM Query Panel window.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Retrieve request<br /></font>''</div>
 
After you successfully query the remote query/retrieve server and locate the set of images to move to the local system, you can then send a C-MOVE request to move the desired images to the local system. To initiate the C-MOVE request, click Move Image in the DICOM Communication Panel window, which then opens an association to the remote query/retrieve server. The remote server then responds to the C-MOVE request by initiating a C-STORE request on a new association to the C-STORE SCU process in the MIPAV application.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Associated real-world activity<br /></font>''</div>
 
The initiation of a C-MOVE request is the associated real-world activity.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Proposed presentation contexts<br /></font>''</div>
 
When MIPAV initiates a C-MOVE request, a presentation context is proposed for the Study Root Query/Retrieve C-MOVE supported SOP Class. No extended negotiation is supported.
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
 
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 7.  Presentation context proposed by MIPAV as a result of <br />real-world activity "MOVE Request to an External Query Server"</div>
|- bgcolor="#CCCCCC"
! rowspan="1" colspan="6" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Presentation context table<br /></font>'''</div>
|-
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Abstract syntax<br /></font>'''</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Help Topics</font>'''</span>-Displays online help topics.</div>
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Transfer syntax<br /></font>'''</div>
| rowspan="2" colspan="1" |
<div class="CellHeading">Role</div>
| rowspan="2" colspan="1" |
<div class="CellHeading">Extended negotiation</div>
|-
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Name <br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> UID<br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Name list<br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> UID list<br /></font>'''</div>
|-
|
<div class="CellBody">Study Root Q/R C-MOVE</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.2.2.2</div>
|
<div class="CellBody">Implicit VR Little Endian</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|
<div class="CellBody">SCU</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|}
|}


<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> SOP specific conformance statement for SOP Class Study Root Query/Retrieve Information Model C-MOVE<br /></font>''</div>
<br />
3 Select the VOI. <br />
As an option, copy the VOI to other slices in the dataset by selecting VOI &gt; Propagate and one of the following commands:<br />
*To Next Slice<br />
*To Previous Slice<br />
*To All Slices<br />
4 Do one of the following:<br />
*Select VOI &gt; Graph &gt; Boundary Intensity in the MIPAV window. <br />
*Right click on the VOI and then select Graph &gt; Boundary Intensity.<br />
*The Contour VOI Graph window (Figure 10) opens.<br />


The attributes listed in Table 8 comprise the Study Root Query/Retrieve C-MOVE identifier that is sent in the DICOM retrieve message. The level column indicates the query level at which the attributes can be included. Note that the table of attributes below is identical to those for the Study Root Query/Retrieve C-FIND identifier in Table 8]
'''To generate 3D contour VOI graphs'''<br />
1 Open an image.<br />
2 Delineate a VOI on the image using the 3D rectangular VOI icon, in the MIPAV window. <br />
3 Select the VOI. <br />
As an option, copy the VOI to other slices in the dataset by selecting VOI &gt; Propagate and one of the following commands:<br />
*To Next Slice<br />
*To Previous Slice<br />
*To All Slices<br />
4 Do one of the following:<br />
*Select VOI &gt; Graph &gt; Boundary Intensity in the MIPAV window.<br />
*Right-click on the VOI and then select Graph &gt; Boundary Intensity. <br />
The Contour VOI Graph window (Figure 10) opens. This window displays a graph of the intensity values of the selected contour's boundary. <br />


<div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
=== Generating intensity graphs ===
Intensity profiles, or graphs, present information on the intensity values of the VOI region in an image. The intensity graph appears in the Intensity Graph window (Figure 11).<br />


{| border="1" cellpadding="5"
'''To generate 2D intensity graphs'''<br />
|+  <div class="TableTitle">Table 8.  DICOM data elements supported for SOP Class Study Root Query/Retrieve Information Model C-MOVE SCU</div>
1 Open an image.<br />
|- bgcolor="#CCCCCC"
2 Delineate a 2D VOI on the image using one of the 2D icons in the MIPAV window.<br /><
!
3 Select the VOI. <br />
<div class="CellHeading">Level</div>
As an option, copy the VOI to other slices in the dataset by selecting VOI &gt; Propagate and one of the following commands:<br />
!
*To Next Slice<br />
<div class="CellHeading">Description</div>
*To Previous Slice<br />
!
*To All Slices<br />
<div class="CellHeading">Tag</div>
4 Do one of the following:<br />
!
Select VOI &gt; Graph in the MIPAV window and either of the following:<br />
<div class="CellHeading">Type</div>
* ''2.5D Total Intensity'' -To generate a graph of the sum of the intensity values of the VOI region. <br />
|-
* ''2.5D Average Intensity'' -To generate a graph of the average of the intensity values of the VOI region.<br />
| rowspan="1" colspan="4" |
Right-click on the VOI and then select Graph and one of the following commands:<br />
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Study<br /></font>'''</div>
* ''2.5D Total Intensity'' -To generate a graph of the sum of the intensity values of the area delineated by the VOI per slice.<br />
|-
* ''2.5D Average Intensity'' -To generate a graph of the average of the intensity values of the VOI region.<br />
|
* ''2.5D Total Intensity with Threshold'' -TBD. <br />
<div class="CellBody">Study</div>
* ''2.5D Average Intensity with Threshold'' -TBD.<br />
|
The Intensity Graph window (Figure 11) opens.
<div class="CellBody">Study Date</div>
|
<div class="CellBody">(0008,0020)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Study Time</div>
|
<div class="CellBody">(0008,0030)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Study ID</div>
|
<div class="CellBody">(0020,0010)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Patient's Name</div>
|
<div class="CellBody">(0010,0010)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Patient ID</div>
|
<div class="CellBody">(0010,0020)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Study Instance UID</div>
|
<div class="CellBody">(0020,000D)</div>
|
<div class="CellBody">U</div>
|-
|
<div class="CellBody">Study</div>
|
<div class="CellBody">Referring Physician's Name</div>
|
<div class="CellBody">(0008,0090)</div>
|
<div class="CellBody">O</div>
|-
| rowspan="1" colspan="4" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Series<br /></font>'''</div>
|-
|
<div class="CellBody">Series</div>
|
<div class="CellBody">Modality</div>
|
<div class="CellBody">(0008,0060)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Series</div>
|
<div class="CellBody">Series Number</div>
|
<div class="CellBody">(0020,0011)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Series</div>
|
<div class="CellBody">Series Instance UID</div>
|
<div class="CellBody">(0020,000E)</div>
|
<div class="CellBody">U</div>
|-
|
<div class="CellBody">Series</div>
|
<div class="CellBody">Series Date</div>
|
<div class="CellBody">(0008,0021)</div>
|
<div class="CellBody">O</div>
|-
|
<div class="CellBody">Series</div>
|
<div class="CellBody">Series Description</div>
|
<div class="CellBody">(0008,103E)</div>
|
<div class="CellBody">O</div>
|-
|
<div class="CellBody">Series</div>
|
<div class="CellBody">Body Part Examined</div>
|
<div class="CellBody">(0018,0015)</div>
|
<div class="CellBody">O</div>
|-
| rowspan="1" colspan="4" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Image<br /></font>'''</div>
|-
|
<div class="CellBody">Image</div>
|
<div class="CellBody">Image Number</div>
|
<div class="CellBody">(0020,0013)</div>
|
<div class="CellBody">R</div>
|-
|
<div class="CellBody">Image</div>
|
<div class="CellBody">SOP Instance UID</div>
|
<div class="CellBody">(0008,0018)</div>
|
<div class="CellBody">U</div>
|-
|
<div class="CellBody">Image</div>
|
<div class="CellBody">Image Date</div>
|
<div class="CellBody">(0008,0023)</div>
|
<div class="CellBody">O</div>
|-
|
<div class="CellBody">Image</div>
|
<div class="CellBody">Image Time</div>
|
<div class="CellBody">(0008,0033)</div>
|
<div class="CellBody">O</div>
|}
 
<br /></font></div>
 
===== Association acceptance policy =====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> Not applicable.<br /></font></div>
 
==== DICOM sender (storage SCU) AE specification ====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> MIPAV provides standard conformance to the DICOM 3.0 Storage SOP classes listed in Table 9<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">


{| border="1" cellpadding="5"
{| border="1" cellpadding="5"
|+ <div class="TableTitle">Table 9. Supported C-STORE SOP classes</div>
|+ '''Figure 11. Intensity Graph window '''
|- bgcolor="#CCCCCC"
!
<div class="CellHeading">SOP class name</div>
!
<div class="CellHeading">SOP class UID</div>
|-
|
<div class="CellBody">Computed Radiography Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.1</div>
|-
|
<div class="CellBody">CT Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.2</div>
|-
|
<div class="CellBody">MR Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.4</div>
|-
|
<div class="CellBody">Nuclear Medicine Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.20</div>
|-
|-
|
|
<div class="CellBody">Ultrasound Image Storage</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">File</font>'''</span></div>
|
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.6</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Open Graph</font>'''</span>-Opens a PLT file that contains graph data.</div> <div class="CellBody">When you select this command or press Ctrl O on the keyboard, the Open Graph Data dialog box appears. </div>
|-
|
<div class="CellBody">Secondary Capture Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.7</div>
|}
 
<br /></font></div>
 
===== Association establishment policies =====
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> General<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The MIPAV DICOM image sender initiates an association with a remote DICOM image receiver. Extended negotiation is not supported.<br /></font></div>
 
The maximum PDU size in an association request defaults to 16 kilobytes.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Number of associations<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> Each send (C-STORE) request within the MIPAV application initiates an association with a remote DICOM image receiver. Thus, multiple associations for the C-STORE SOP class can be opened and processed by MIPAV in one working session.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Asynchronous nature<br /></font>''</div>
 
The DICOM Sender only allows a single outstanding operation on an Association. Thus, there is no asynchronous activity in this implementation.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Implementation identifying information<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> (TBD. Need the Implementation Class Unique Identifier (UID) for the MIPAV DICOM Sender. Note that this may be the same for all applications- one implementation UID for a DICOM application. For information, contact Richard Eaton at NEMA at 703/841-3248 or through e-mail at ric_eaton@nema.org.<br /></font></div>
 
===== Association initiation by real-world activity =====
 
To initiate an association from MIPAV to a remote image receiver (C-STORE SCP), select Send in the DICOM Query Panel window. When you select File &gt; DICOM Database Access in the MIPAV window, the DICOM Communication Panel window opens.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> DICOM send request<br /></font>''</div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Associated real-world activity<br /></font>''</div>
 
The initiation of a Send image request is the associated real-world activity.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Proposed presentation contexts<br /></font>''</div>
 
When MIPAV initiates a C-STORE request, a different presentation context is proposed for each of the different supported C-STORE SOP Classes. No extended negotiation is supported.
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
 
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 10.  Presentation contexts proposed by MIPAV as a result of real-world activity "store request to an external query server</div>
|- bgcolor="#CCCCCC"
! rowspan="1" colspan="6" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Presentation context table<br /></font>'''</div>
|-
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Abstract syntax<br /></font>'''</div>
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Transfer syntax<br /></font>'''</div>
| rowspan="2" colspan="1" |
| rowspan="2" colspan="1" |
<div class="CellHeading">Role</div>
[[Image:VOIGRaphMOdifyPointsVis.jpg]]
| rowspan="2" colspan="1" |
<div class="CellHeading">Extended negotiation</div>
|-
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Name <br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> UID<br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Name list<br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> UID list<br /></font>'''</div>
|-
|
<div class="CellBody">CR Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.1</div>
|
<div class="CellBody">Implicit VR Little Endian</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|
<div class="CellBody">SCU</div>
|
<div class="CellBody">None</div>
|-
|
<div class="CellBody">CT Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.2</div>
|
<div class="CellBody">Implicit VR Little Endian</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|
<div class="CellBody">SCU</div>
|
<div class="CellBody">None</div>
|-
|-
|
|
<div class="CellBody">MR Image Storage</div>
<div class="CellBody"> </div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.4</div>
|
<div class="CellBody">Implicit VR Little Endian</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|
<div class="CellBody">SCU</div>
|
<div class="CellBody">None</div>
|-
|
<div class="CellBody">US Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.6</div>
|
<div class="CellBody">Implicit VR Little Endian</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|
<div class="CellBody">SCU</div>
|
|
<div class="CellBody">None</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Save Graph</font>'''</span>-Saves the graph data in a PLT file. </div> <div class="CellBody">When you select this command or when you press Ctrl S on the keyboard, the Save dialog box opens.</div>
|-
|-
|
|
<div class="CellBody">Secondary Capture Image Storage</div>
<div class="CellBody"> </div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.7</div>
|
<div class="CellBody">Implicit VR Little Endian</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|
<div class="CellBody">SCU</div>
|
<div class="CellBody">None</div>
|}
 
<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> SOP specific conformance statement for supported storage SOP classes<br /></font>''</div>
 
The following overview summarizes the behavior of the MIPAV DICOM Sender routine depending on the responses to the C-STORE request:
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 5pt; text-align: left; text-decoration: none; text-indent: -24pt; text-transform: none; vertical-align: baseline"><font color="#000000">  <span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Successful C-STORE response: </font>'''</span>In the case of a response of SUCCESS for the C-STORE request, the MIPAV Send status panel in the Send page in the DICOM Communication Panel window displays a status of SUCCESS. This indicates that the images were properly received by the image receiver (C-STORE SCU).<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 5pt; text-align: left; text-decoration: none; text-indent: -24pt; text-transform: none; vertical-align: baseline"><font color="#000000">  <span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Unsuccessful C-STORE response: </font>'''</span>In the case of a response of REFUSED, CANCEL, or FAILED, for the C-STORE request, the DICOM sender routine aborts the association. The MIPAV Send status panel in the Send page in the DICOM Communication Panel window displays a status of FAILED. The software makes no further attempts to retry the transfer of the aborted images.<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 5pt; text-align: left; text-decoration: none; text-indent: -24pt; text-transform: none; vertical-align: baseline"><font color="#000000">  <span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Warning status in C-STORE response:</font>'''</span> In the case of a response of Warning for the C-STORE request, the MIPAV DICOM sender routine behaves the same as if a response of SUCCESS was received.<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The DICOM Sender does not attempt any extended negotiation.<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The DICOM Sender supports all type 1, type 2, and type 3 attributes defined in the Information Object Definition (IOD) associated with the SOP class. No attributes are discarded or coerced by the DICOM Sender. The originally saved DICOM file is read from disk and forwarded to the desired remote system. Note that the DICOM Sender does not validate that the attributes of the SOP instance for the outgoing C-STORE message request meet the requirements of the IOD. It is assumed that the saved DICOM image file is stored in a valid DICOM file format.<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 24pt; margin-right: 0pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The SOP Instance UID (group 0x0008, element 0x0018), Study Instance UID (group 0x0020, element 0x000D), and Series Instance UID (group 0x0020, element 0x000E) consist of a root and suffix. The root consists of the date and time of transaction. The suffix is conforms to the DICOM standard.<br /></font></div>
 
===== Association acceptance policy =====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> Not applicable.<br /></font></div>
 
==== Verification (C-Echo SCP) AE specification ====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> MIPAV provides standard conformance to the DICOM 3.0 Verification SOP class listed in Table 11].<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
 
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 11.  Supported verification SOP class</div>
|- bgcolor="#CCCCCC"
!
<div class="CellHeading">SOP class name</div>
!
<div class="CellHeading">SOP class UID</div>
|-
|
<div class="CellBody">Verification SOP Class</div>
|
<div class="CellBody">1.2.840.10008.1.1</div>
|}
 
<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> <br /></font></div>
 
===== Association establishment policies =====
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> General<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The MIPAV DICOM Verification routine responds to a verification of communication request from a remote DICOM AE by sending a C-Echo response of a status of SUCCESS.<br /></font></div>
 
The maximum PDU size in an association request defaults to 16 kilobytes.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Number of associations<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> Each verification (C-Echo) request sent to the MIPAV application is responded to on an association opened by the remote AE. Multiple associations for the C-ECHO SOP class can be accepted and processed by MIPAV in one working session.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Asynchronous nature<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The DICOM verification routine only allows a single outstanding operation on an Association. Thus, there is no asynchronous activity in this implementation.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Implementation Identifying Information<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> (TBD. Need the Implementation Class Unique Identifier (UID) for the MIPAV DICOM verification routine. Note that this may be the same for all applications- one implementation UID for a DICOM application. For information contact Richard Eaton at NEMA- (703) 841-3248, email- ric_eaton@nema.org)<br /></font></div>
 
===== Association initiation by real-world activity =====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> Not applicable.<br /></font></div>
 
===== Association Acceptance Policy =====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> MIPAV accepts all associations for C-ECHO requests initiated by remote systems.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> DICOM Verification Request<br /></font>''</div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Associated Real-World Activity<br /></font>''</div>
 
The arrival of a verification, or C-Echo, request is the associated real-world activity.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Proposed Presentation Contexts<br /></font>''</div>
 
When the MIPAV Message Receiver gets a verification request, the presentation context accepted for the C-ECHO SOP class is listed in Table 12. No extended negotiation is supported.
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
 
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 12.  Presentation contexts accepted by MIPAV as a result of real-world activity "verification" request</div>
|- bgcolor="#CCCCCC"
! rowspan="1" colspan="6" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Presentation context table<br /></font>'''</div>
|-
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Abstract syntax<br /></font>'''</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Print Graph</font>'''</span>-Allows you to print the graph. When you select this command or press <br />Ctrl P, the Print dialog box opens.</div>
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Transfer syntax<br /></font>'''</div>
| rowspan="2" colspan="1" |
<div class="CellHeading">Role</div>
| rowspan="2" colspan="1" |
<div class="CellHeading">Extended negotiation</div>
|-
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Name <br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> UID<br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Name list<br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> UID list<br /></font>'''</div>
|-
|-
|
|
<div class="CellBody">Verification</div>
<div class="CellBody"> </div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.1</div>
|
<div class="CellBody">Implicit VR Little Endian</div>
|
<div class="CellBody">1.2.840.10008.1.1</div>
|
<div class="CellBody">SCP</div>
|
<div class="CellBody">None</div>
|}
 
<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> SOP Specific Conformance Statement for Verification SOP Class<br /></font>''</div>
 
The Verification AE follows the DICOM 3.0 standard for handling of C-ECHO requests. A status of SUCCESS is returned to a valid C-ECHO verification request.
 
==== DICOM image receiver (storage SCP) AE specification ====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> MIPAV provides standard conformance to the DICOM 3.0 Storage SOP classes listed in Table 13<br /></font></div><div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
 
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 13.  Supported C-STORE SOP classes</div>
|- bgcolor="#CCCCCC"
!
<div class="CellHeading">SOP class name</div>
!
<div class="CellHeading">SOP class UID</div>
|-
|
<div class="CellBody">CR Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.1</div>
|-
|
<div class="CellBody">CT Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.2</div>
|-
|
<div class="CellBody">MR Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.4</div>
|-
|
<div class="CellBody">NM Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.20</div>
|-
|
<div class="CellBody">US Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.6</div>
|-
|
<div class="CellBody">Secondary Capture Image Storage</div>
|
<div class="CellBody">1.2.840.10008.5.1.4.1.1.7</div>
|}
 
<br /></font></div>
 
===== Association Establishment Policies =====
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> General<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The MIPAV DICOM image receiver opens a node at the port specified in the mipav.preferences file and waits for an association from a DICOM application at the specified port. MIPAV accepts an association from a remote DICOM image sender. Extended negotiation is not supported.<br /></font></div>
 
The maximum PDU size in an association request defaults to 16 kilobytes.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Number of Associations<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The DICOM Image Receiver initiates a new process for each connection request it receives. Thus, the image receiver can have multiple simultaneous connections and there are no inherent limitations on the total number of simultaneous associations that the image receiver can maintain.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Asynchronous Nature<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The DICOM Image Receiver only allows a single outstanding operation on an Association. Thus, there is no asynchronous activity in this implementation.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Implementation Identifying Information<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> (TBD. Need the Implementation Class Unique Identifier (UID) for the MIPAV DICOM Receiver. Note that this may be the same for all applications- one implementation UID for a DICOM application. For information contact Richard Eaton at NEMA- (703) 841-3248, email- ric_eaton@nema.org)<br /></font></div>
 
===== Association Initiation by Real-World Activity =====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> Not applicable. The DICOM Image Receiver never initiates an association.<br /></font></div>
 
===== Association Acceptance Policy =====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> When the MIPAV Image Receiver accepts an association, it receives any images transferred on that association and stores the images on the local disk in the native machine file system, in the format specified in <span style="font-weight: normal; text-decoration: none; text-transform: none; vertical-align: baseline">''<font color="#000000">Digital Imaging and Communications In Medicine (DICOM) Part 10: Media Storage and File Format for Media Interchange</font>''</span> (see Appendix E for a full citation.) The Image Receiver places no limitation on who may connect to it, or the number of simultaneous connections it can support.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> DICOM image receiver <br /></font>''</div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Associated real-world activity<br /></font>''</div>
 
The storage of an image on the disk of the local system is the associated real-world activity for the Image Receiver.
 
<div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Proposed presentation contexts<br /></font>''</div>
 
The presentation contexts accepted by the MIPAV Image Receiver are listed in Table 14. No extended negotiation is supported.
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">
 
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 14.  Presentation contexts proposed by MIPAV as a result of real-world activity "receive and store images"</div>
|- bgcolor="#CCCCCC"
! rowspan="1" colspan="6" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Presentation context table<br /></font>'''</div>
|-
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Abstract syntax<br /></font>'''</div>
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Transfer syntax<br /></font>'''</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Close Graph</font>'''</span>-Closes the Intensity Graph window. To close the window, you can also press Ctrl X on the keyboard.</div>
| rowspan="2" colspan="1" |
<div class="CellHeading">Role</div>
| rowspan="2" colspan="1" |
<div class="CellHeading">Extended negotiation</div>
|-
|-
|
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Name <br /></font>'''</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Edit</font>'''</span></div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> UID<br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Name list<br /></font>'''</div>
|
<div style="font-style: normal; margin-bottom: 2pt; margin-left: 3pt; margin-right: 3pt; margin-top: 2pt; text-align: center; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> UID list<br /></font>'''</div>
|-
|
<div class="CellBody">CR Image Storage</div>
| rowspan="1" colspan="2" |
<div class="CellBody">1.2.840.10008.5.1.4.1.1.1</div>
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div class="CellBody">Implicit VR Little Endian</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Delete Function</font>'''</span>-Allows you to delete the function that you select. However, you cannot delete a function if it is the only function displayed in the window.</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|-
|-
|
|
<div class="CellBody">CT Image Storage</div>
<div class="CellBody"> </div>
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div class="CellBody">1.2.840.10008.5.1.4.1.1.2</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Paste Function</font>'''</span>-Pastes a previously copied function into the window. The pasted function has a different color than the first function displayed in the window.</div>
| rowspan="1" colspan="2" |
<div class="CellBody">Implicit VR Little Endian</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|-
|-
|
|
<div class="CellBody">MR Image Storage</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Views</font>'''</span></div>
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div class="CellBody">1.2.840.10008.5.1.4.1.1.4</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Modify Graph Features</font>'''</span>-Allows you to customize the appearance of the graph.</div>
| rowspan="1" colspan="2" |
<div class="CellBody">Implicit VR Little Endian</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|-
|-
|
|
<div class="CellBody">NM Image Storage</div>
<div class="CellBody"> </div>
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div class="CellBody">1.2.840.10008.5.1.4.1.1.20</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Reset Range to Default</font>'''</span>-TBD.</div>
| rowspan="1" colspan="2" |
<div class="CellBody">Implicit VR Little Endian</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|-
|-
|
|
<div class="CellBody">US Image Storage</div>
<div class="CellBody"> </div>
| rowspan="1" colspan="2" |
<div class="CellBody">1.2.840.10008.5.1.4.1.1.6</div>
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div class="CellBody">Implicit VR Little Endian</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Reset Graph to Original</font>'''</span>-TBD.</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|-
|-
|
|
<div class="CellBody">Secondary Capture Image Storage</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Help</font>'''</span></div>
| rowspan="1" colspan="2" |
<div class="CellBody">1.2.840.10008.5.1.4.1.1.7</div>
| rowspan="1" colspan="2" |
| rowspan="1" colspan="2" |
<div class="CellBody">Implicit VR Little Endian</div>
<div class="CellBody"><span style="font-style: normal; text-decoration: none; text-transform: none; vertical-align: baseline">'''<font color="#000000">Help Topics</font>'''</span>-Displays online help topics.</div>
|
<div class="CellBody">1.2.840.10008.1.2</div>
|}
|}


<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> SOP Specific Conformance Statement for Supported Storage SOP Classes<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The MIPAV Image Receiver conforms to the Storage SOP Classes as a SCP at Level 2 (Full). No elements are discarded or coerced by the MIPAV Image Receiver. In the event of a successful C-STORE operation, the DICOM image file is successfully written to the local disk with a standard path and file name format. The default path for the image data is /images. The default path can be customized in the mipav.preferences file. The image receiver does not support any extended negotiation.<br /></font></div>
'''To generate 3D intensity graphs of all slices in a dataset at a specific point'''<br />
1 Open an image.<br />
2 Draw a point VOI on the image (Figure 12).<br />
3 Select the VOI.<br />
4 Do one of the following:<br />
*Select the Propagate VOI to all slices icon.<br />
*Select VOI &gt; Propagate &gt; To All Slices. <br />
*Right-click on the VOI, then select Propagate &gt; To All Slices (Figure 12).<br />
5 Right-click on the VOI and select Show VOI Graph (Figure 12).<br />


=== Communications profiles ===
{| border="1" cellpadding="5"
|+ '''Figure 12. Point VOI'''
|-
|
<div style="font-style: normal; font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000">  <br /></font></div>


==== Overview ====
<br clear="all" />


<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> This section lists all communication protocols supported by MIPAV.<br /></font></div>
{|
 
|
==== Supported communications stacks ====
[[Image:PointVOIPropagate.jpg]]
 
|}
===== TCP/IP =====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The MIPAV DICOM routines run over the TCP/IP stack.<br /></font></div><div style="font-weight: normal; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt; margin-top: 12pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">''<font color="#000000"> Application Programmer's Interface (API)<br /></font>''</div><div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The MIPAV DICOM routines are implemented using the Berkeley Sockets interface to TCP/IP services.<br /></font></div>
 
===== Physical Media Supported =====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The MIPAV DICOM routines run on any physical media supported by the TCP/IP stack that is run on the host machine.<br /></font></div>
 
=== Extensions, Specializations, and Privatizations ===
 
==== Overview ====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> This section lists all DICOM Standard extended, specialized, or private SOP Class implementations.<br /></font></div>
 
==== MIPAV AE DICOM Services ====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> No extended, specialized, or private SOPs are specified.<br /></font></div>
 
=== DICOM Configuration Details ===
 
==== Overview ====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> This section addresses the method of setting configurable parameters for the DICOM routines.<br /></font></div>
 
For the MIPAV DICOM Receiver, the port number and AE Title are configurable in the mipav.preferences file.
 
The MIPAV Query/Retrieve process also uses the AE Title, IP Address, and port number settings for the host machine and the remote query server. You can change the values for these settings on the Hosts page in the DICOM Communication Panel window. The settings can also be configured in the mipav.preferences file.
 
==== AE Title/Presentation Mapping ====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> The MIPAV DICOM routines map the AE title to a presentation address (IP address and port number) by accessing information on the Hosts page in the DICOM Communication Panel window. This is then written and saved in the mipav.preferences file.<br /></font></div>


=== Support of Extended Character Sets ===
'''To generate 3D intensity graphs of specific areas'''<br />
1 Open an image.<br />
2 Delineate a VOI on the image using the 3D rectangular VOI icon.<br />
3 Select the VOI. Then, do one of the following:<br />
*a Select VOI &gt; Graph and either of the following in the MIPAV window:<br />
** ''2.5D Total Intensity'' -To generate a graph of the sum of the intensity values of the area delineated by the VOI per slice.<br />
** ''2.5D Average Intensity'' -To generate a graph of the average of the intensity values of the VOI region.<br />
*b Right-click the VOI, and then select Graph and one of the following commands in the MIPAV window:<br />
** ''2.5D Total Intensity'' -To generate a graph of the sum of the intensity values of the area delineated by the VOI per slice.<br />
** ''2.5D Average Intensity'' -To generate a graph of the average of the intensity values of the VOI region.<br />
** ''2.5D Total Intensity with Threshold'' -TBD.<br />
** ''2.5D Average Intensity with Threshold'' -TBD.<br />
The Intensity Graph window (Figure 11) opens.<br />


==== Overview ====


<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> Any support for extended character sets, such as multibyte characters, are described in this section.<br /></font></div>
[[Customizing the appearance of graphs - Modify graph dialog box]]
 
==== MIPAV ICOM AE ====
 
<div style="font-style: normal; font-weight: normal; margin-bottom: 6pt; margin-left: 0pt; margin-right: 0pt; margin-top: 0pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline"><font color="#000000"> MIPAV does not support extended character sets.<br />
 
{| border="1" cellpadding="5"
|+  <div class="TableTitle">Table 15.  DICOM tags </div>
|- bgcolor="#CCCCCC"
!
<div class="CellHeading">Field</div>
!
<div class="CellHeading">Description</div>
|-
|
<div class="CellBody">Study Instance UID (0020,000D)</div>
|
<div class="CellBody">Unique identifier for the study. Only numeric characters with optional periods are allowed.</div>
|-
|
<div class="CellBody">Modality (0008,0060)</div>
|
<div class="CellBody">Type of equipment that was used to acquire the data used to create the images in the dataset. Options are: Biomagnetic Imaging, Color Flow Doppler, Computed Tomography, Duplex Doppler, Computed Radiography, Diaphanography, Digital Radiography, Endoscopy, General Microscopy, Hard Copy, Intraoral Radiography, Laser Surface Scan, MR Angiography, Mammography, Magnetic Resonance, MR Spectroscopy, Nuclear Medicine, Other, PET, Panoramic XRay, Radio Fluoroscopy, Radiographic Imaging, Radiotherapy Dose, Radiotherapy Image, Radiotherapy Record, Radiotherapy Structure, Slide Microscopy, SPECT, Thermography, Ultrasound, XRay Angiography, and External Photography.</div>
|-
|
<div class="CellBody">Series Instance UID (0020,000E)</div>
|
<div class="CellBody">Unique identifier for the study. Only numeric characters (with optional periods) are allowed.</div>
|-
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 6pt; margin-left: 6pt; margin-right: 6pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Patient<br /></font>'''</div>
|-
|
<div class="CellBody">Patient's Name (0010,0010)</div>
|
<div class="CellBody">Patient's full name.</div>
|-
|
<div class="CellBody">Patient's Birth Date (0010,0030)</div>
|
<div class="CellBody">Date of patient's birth.</div>
|-
|
<div class="CellBody">Patient's Birth Time (0010,0032)</div>
|
<div class="CellBody">Time of patient's birth.</div>
|-
|
<div class="CellBody">Other Patient Names (0010,1001)</div>
|
<div class="CellBody">Other names used to identify the patient.</div>
|-
|
<div class="CellBody">Patient Comments (0010,4000)</div>
|
<div class="CellBody">User-defined comments about the patient.</div>
|-
|
<div class="CellBody">Patient ID (0010,0020)</div>
|
<div class="CellBody">Primary hospital identification number or code used to identify the patient.</div>
|-
|
<div class="CellBody">Patient's Sex (0010,0040)</div>
|
<div class="CellBody">Gender of the patient. Options are: Unknown, Male, Female, and Other.</div>
|-
|
<div class="CellBody">Other Patient IDs (0010,1000)</div>
|
<div class="CellBody">Other IDs used to identify the patient.</div>
|-
|
<div class="CellBody">Ethnic Group (0010,2160)</div>
|
<div class="CellBody">Ethnic group or race of the patient.</div>
|-
|
<div class="CellBody">Patient Orientation (0020,0020)</div>
|
<div class="CellBody">Patient direction of the rows and columns of the image. </div>
|-
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 6pt; margin-left: 6pt; margin-right: 6pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Study<br /></font>'''</div>
|-
|
<div class="CellBody">Study ID (0020,0010)</div>
|
<div class="CellBody">User- or equipment-generated study identifier. </div>
|-
|
<div class="CellBody">Study Time (0008,0030)</div>
|
<div class="CellBody">Time the study started.</div>
|-
|
<div class="CellBody">Study Description (0008,1030)</div>
|
<div class="CellBody">Institute-generated description or classification of the study (component) performed.</div>
|-
|
<div class="CellBody">Physician(s) of Record (0008,1048)</div>
|
<div class="CellBody">Physician responsible for the overall patient care at the time of the study.</div>
|-
|
<div class="CellBody">Admitting Diagnoses Description (0008,1080)</div>
|
<div class="CellBody">Description of the admitting diagnoses.</div>
|-
|
<div class="CellBody">Patient's Size (0010,1020)</div>
|
<div class="CellBody">Length or size of the patient in meters.</div>
|-
|
<div class="CellBody">Occupation (0010,2180)</div>
|
<div class="CellBody">Occupation of the patient.</div>
|-
|
<div class="CellBody">Study Date (0008,0020)</div>
|
<div class="CellBody">Date the study started.</div>
|-
|
<div class="CellBody">Accession Number (0008,0050)</div>
|
<div class="CellBody">An RIS-generated number which identifies the order for the study.</div>
|-
|
<div class="CellBody">Referring Physician's Name (0008,0090)</div>
|
<div class="CellBody">Patient's referring physician.</div>
|-
|
<div class="CellBody">Physician(s) Reading Study (0008,1060)</div>
|
<div class="CellBody">Physician(s) reading the study.</div>
|-
|
<div class="CellBody">Patient's Age (0010,1010)</div>
|
<div class="CellBody">Age of the patient.</div>
|-
|
<div class="CellBody">Patient's Weight (0010,1030)</div>
|
<div class="CellBody">Weight of the patient, in kilograms.</div>
|-
|
<div class="CellBody">Additional Patient's History (0010,21B0)</div>
|
<div class="CellBody">Additional information about the patient's history.</div>
|-
| rowspan="1" colspan="2" |
<div style="font-style: normal; margin-bottom: 6pt; margin-left: 6pt; margin-right: 6pt; margin-top: 6pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> Series<br /></font>'''</div>
|-
|
<div class="CellBody">Series Number (0020,0011)</div>
|
<div class="CellBody">A number that identifies this series.</div>
|-
|
<div class="CellBody">Performing Physicians' Name (0008,1050)</div>
|
<div class="CellBody">Name(s) of the physician(s) administering the series.</div>
|-
|
<div class="CellBody">Series Description (0008,103E)</div>
|
<div class="CellBody">User-provided description for the series.</div>
|-
|
<div class="CellBody">Body Part Examined (00018,0015)</div>
|
<div class="CellBody">A text description of the body part that was examined. Options are: Unknown, Skull, CSpine, TSpine, LSpine, SSpine, Coccyx, Chest, Clavicle, Breast, Abdomen, Pelvis, Hip, Shoulder, Elbow, Knee, Ankle, Hand, Foot, Extremity, Head, Heart, Neck, Leg, Arm, and Jaw.</div>
|-
|
<div class="CellBody">Smallest Pixel Value (0028,0108)</div>
|
<div class="CellBody">Minimum value of all images in this series.</div>
|-
|
<div class="CellBody">Procedure Step ID (0040,0253)</div>
|
<div class="CellBody">Identification of that part of a procedures that was performed during this step.</div>
|-
|
<div class="CellBody">Procedure Step Start Time (0040,0245)</div>
|
<div class="CellBody">Time when the procedure step started.</div>
|-
|
<div class="CellBody">Laterality (0020,0080)</div>
|
<div class="CellBody">Options are: Unknown, Left, and Right.</div>
|-
|
<div class="CellBody">Series Time (0008,0031)</div>
|
<div class="CellBody">Time series started.</div>
|-
|
<div class="CellBody">Protocol Name (0018,1030)</div>
|
<div class="CellBody">User-defined description of the conditions under which the series was performed.</div>
|-
|
<div class="CellBody">Operator's Name (0008,1070)</div>
|
<div class="CellBody">Name(s) of the technologist(s) supporting the series.</div>
|-
|
<div class="CellBody">Patient Position (0018,5100)</div>
|
<div class="CellBody">Patient position relative to the imaging-equipment space. Options are: Unknown, Head-First Prone, Head-First Supine, Feet First-Prone, Feet First-Supine, HF-Decubitus Right, HF-Decubitus Left, FF-Decubitus Right, FF-Decubitus Left.</div>
|-
|
<div class="CellBody">Largest Pixel Value (0028,0109)</div>
|
<div class="CellBody">Maximum value of all images in this series.</div>
|-
|
<div class="CellBody">Procedure Step Start Date (0040,0244)</div>
|
<div class="CellBody">Date when the procedure step started.</div>
|-
|
<div class="CellBody">Procedure Step Description (0040,0254)</div>
|
<div class="CellBody">Institute-generated description or classification of the procedure step that was performed.</div>
|}

Revision as of 20:22, 21 February 2012

MIPAV allows you to generate intensity profiles, or contour VOI graphs, for VOI contours. For delineated VOIs, you can generate 2D, 3D, or 4D intensity graphs. You can also generate a 3D intensity graph at a specific point across all slices in a dataset. For information on how to contour a VOI, refer to Chapter 1, "Segmenting Images Using Contours and Masks,"

Generating contour VOI graphs

Contour VOI graphs display the intensity values of the selected contour's boundary in the Contour VOI Graph window (Figure 10). You can generate either 2D or 3D contour VOI graphs.

To generate 2D contour VOI graphs
1 Open an image.
2 Delineate a 2D VOI on the image using one of the 2D icons in the MIPAV window.


Figure 10. Contour VOI Graph window

WindowContourVOIGraph.jpg

File
Open Graph-Opens a PLT file that contains graph data. When you select this command or press Ctrl O on the keyboard, the Open Graph Data dialog box appears.
Save Graph-Saves the graph data in a PLT file. When you select this command or when you press Ctrl S on the keyboard, the Save dialog box opens.
Print Graph-Allows you to print the graph. When you select this command or press
Ctrl P, the Print dialog box opens.
Close Graph-Closes the Intensity Graph window. To close the window, you can also press Ctrl X on the keyboard.
Edit
Delete Function-Allows you to delete a specific function. However, you cannot delete a function if it is the only function displayed in the window.
Copy Function-Copies a function that is currently displayed in the window.
Paste Function-Pastes a previously copied function into the window. The pasted function has a different color than the first function displayed in the window.
Views
Modify Graph Features-Allows you to customize the appearance of the graph.
Reset Range to Default-[TBD]
Reset Graph to Original-[TBD].
Help
Help Topics-Displays online help topics.


3 Select the VOI.
As an option, copy the VOI to other slices in the dataset by selecting VOI > Propagate and one of the following commands:

  • To Next Slice
  • To Previous Slice
  • To All Slices

4 Do one of the following:

  • Select VOI > Graph > Boundary Intensity in the MIPAV window.
  • Right click on the VOI and then select Graph > Boundary Intensity.
  • The Contour VOI Graph window (Figure 10) opens.

To generate 3D contour VOI graphs
1 Open an image.
2 Delineate a VOI on the image using the 3D rectangular VOI icon, in the MIPAV window.
3 Select the VOI.
As an option, copy the VOI to other slices in the dataset by selecting VOI > Propagate and one of the following commands:

  • To Next Slice
  • To Previous Slice
  • To All Slices

4 Do one of the following:

  • Select VOI > Graph > Boundary Intensity in the MIPAV window.
  • Right-click on the VOI and then select Graph > Boundary Intensity.

The Contour VOI Graph window (Figure 10) opens. This window displays a graph of the intensity values of the selected contour's boundary.

Generating intensity graphs

Intensity profiles, or graphs, present information on the intensity values of the VOI region in an image. The intensity graph appears in the Intensity Graph window (Figure 11).

To generate 2D intensity graphs
1 Open an image.
2 Delineate a 2D VOI on the image using one of the 2D icons in the MIPAV window.
< 3 Select the VOI.
As an option, copy the VOI to other slices in the dataset by selecting VOI > Propagate and one of the following commands:

  • To Next Slice
  • To Previous Slice
  • To All Slices

4 Do one of the following:
Select VOI > Graph in the MIPAV window and either of the following:

  • 2.5D Total Intensity -To generate a graph of the sum of the intensity values of the VOI region.
  • 2.5D Average Intensity -To generate a graph of the average of the intensity values of the VOI region.

Right-click on the VOI and then select Graph and one of the following commands:

  • 2.5D Total Intensity -To generate a graph of the sum of the intensity values of the area delineated by the VOI per slice.
  • 2.5D Average Intensity -To generate a graph of the average of the intensity values of the VOI region.
  • 2.5D Total Intensity with Threshold -TBD.
  • 2.5D Average Intensity with Threshold -TBD.

The Intensity Graph window (Figure 11) opens.

Figure 11. Intensity Graph window
File
Open Graph-Opens a PLT file that contains graph data.
When you select this command or press Ctrl O on the keyboard, the Open Graph Data dialog box appears.

VOIGRaphMOdifyPointsVis.jpg

Save Graph-Saves the graph data in a PLT file.
When you select this command or when you press Ctrl S on the keyboard, the Save dialog box opens.
Print Graph-Allows you to print the graph. When you select this command or press
Ctrl P, the Print dialog box opens.
Close Graph-Closes the Intensity Graph window. To close the window, you can also press Ctrl X on the keyboard.
Edit
Delete Function-Allows you to delete the function that you select. However, you cannot delete a function if it is the only function displayed in the window.
Paste Function-Pastes a previously copied function into the window. The pasted function has a different color than the first function displayed in the window.
Views
Modify Graph Features-Allows you to customize the appearance of the graph.
Reset Range to Default-TBD.
Reset Graph to Original-TBD.
Help
Help Topics-Displays online help topics.

To generate 3D intensity graphs of all slices in a dataset at a specific point
1 Open an image.
2 Draw a point VOI on the image (Figure 12).
3 Select the VOI.
4 Do one of the following:

  • Select the Propagate VOI to all slices icon.
  • Select VOI > Propagate > To All Slices.
  • Right-click on the VOI, then select Propagate > To All Slices (Figure 12).

5 Right-click on the VOI and select Show VOI Graph (Figure 12).

Figure 12. Point VOI


PointVOIPropagate.jpg

To generate 3D intensity graphs of specific areas
1 Open an image.
2 Delineate a VOI on the image using the 3D rectangular VOI icon.
3 Select the VOI. Then, do one of the following:

  • a Select VOI > Graph and either of the following in the MIPAV window:
    • 2.5D Total Intensity -To generate a graph of the sum of the intensity values of the area delineated by the VOI per slice.
    • 2.5D Average Intensity -To generate a graph of the average of the intensity values of the VOI region.
  • b Right-click the VOI, and then select Graph and one of the following commands in the MIPAV window:
    • 2.5D Total Intensity -To generate a graph of the sum of the intensity values of the area delineated by the VOI per slice.
    • 2.5D Average Intensity -To generate a graph of the average of the intensity values of the VOI region.
    • 2.5D Total Intensity with Threshold -TBD.
    • 2.5D Average Intensity with Threshold -TBD.

The Intensity Graph window (Figure 11) opens.


Customizing the appearance of graphs - Modify graph dialog box

Retrieved from "https://mipav.cit.nih.gov/pubwiki/index.php?title=DICOM_Conformance&oldid=229"