|
Medical Imaging in IDL: Using IDL DICOM Network Services |
|
The Storage SCU functionality of the DICOM Network Services utility transmits DICOM files from the local DICOM Storage SCU (Service Class User) to a remote destination that is identified as a DICOM Storage SCP (Service Class Provider). This sends a copy of the images to the file storage machine, leaving the original image data intact.
The IDL Storage SCU functionality typically sends a DICOM file using the file's current transfer syntax. IDL detects, during the association negotiation, whether or not the remote Storage SCP server can accept the file's current transfer syntax. If the remote Storage SCP cannot accept the current transfer syntax the file's transfer syntax is changed to Implicit VR or Explicit VR and then sent to the remote node. The original file on disk remains unchanged. JPEG Lossy files are not converted to Implicit VR or Explicit VR files because the user at the remote end could be mislead into thinking that the file contains lossless data.
| Note The required Storage SCU tab is not available if you start the DICOM Network Services utility with the SYSTEM keyword. |
To send files to a remote machine, see the following topics:
You need to configure an Application Entity for the remote machine to which you will send DICOM files. (Once an Application Entity has been defined, you do not need to re-execute the following steps.) Record the Application Entity name, host name or IP address, and port number of the remote machine's Storage SCP service. You need this information to configure the network properties of the Application Entity as follows:
DICOMEX_NET
See Defining a New Application Entity for further instructions.
| Note You can verify a connection to the remote machine using the Echo SCU functionality. See Returning Connection Status with Echo. |
Once the Application Entity has been defined, you can send files to the remote node, described in the following section.
You can use the Storage SCU functionality of the DICOM Network Services utility to browse for and send DICOM files to a remote machine. To do so, complete the following steps:
DICOMEX_NET
| Note This tab is not available if the DICOM Network Services utility is started with the SYSTEM keyword. |
There are common configuration errors that can lead to problems when attempting to send files. If the following error appears in the Status window of the Storage SCU tab, consider the following possible resolutions:
|
Error
|
Resolution
|
|---|---|
|
Failed to open an association.
|
The remote machine you are attempting to send images to is not recognized. Try these steps:
1. Make sure that you can connect to the remote machine. See Returning Connection Status with Echo. If echo fails, see the following item.
2. Try sending files to yourself. Select the current Storage SCP entity (which appears in the grayed out Storage SCP Application Entity section of the Configuration tab) from the Destination Node droplist. (This was configured in Configuring Your System to Receive Files). Select and send yourself a file.
3. If you can send yourself a file, double-check the network settings of the Application Entity related to the machine you are attempting to send files to. The Application Entity Title, Host Name (or IP Address), and Port Number must all match the values of the remote machine. See Defining the Remote Storage SCP Node.
|
| Note If your files are not arriving at the destination and you are running Windows XP service pack 2, the firewall that is automatically started is likely blocking the transfer of DICOM packets. See Allowing File Transfer with a Windows XP Firewall for ways to modify your firewall settings. |
IDL Online Help (March 06, 2007)