TestSCU is a dedicated software utility developed by CharruaSoft used for testing, diagnosing, and troubleshooting DICOM (Digital Imaging and Communications in Medicine) network communications.
Operating as a Service Class User (SCU), it acts as a DICOM client to simulate workflow requests, validating that PACS servers, modalities, and other Service Class Providers (SCPs) are reachable and responding correctly. Key Features of TestSCU
The software bundles essential DICOM networking services into a single diagnostic interface:
Echo-Verification (C-ECHO): Sends a ping-like verification request to a remote server to confirm basic network connectivity and valid DICOM handshake capability.
Store (C-STORE): Simulates a medical modality (like an MRI or CT scanner) by sending test DICOM image files to a destination PACS or routing server.
Query-Find (C-FIND): Allows users to search a remote DICOM database using specific attributes like patient name, ID, or study date.
Query-Worklist (MWL): Simulates a modality querying a Modality Worklist provider, checking if patient scheduling data transfers seamlessly from the Hospital Information System (HIS/RIS).
Print Service: Tests connection and layout commands to a DICOM Laser film Printer before wasting actual physical film. Configuration Guide
To successfully run tests with TestSCU, you must align both local and remote AE (Application Entity) parameters. 1. Local SCU Parameter Setup
Define how TestSCU identifies itself on the local computer or network:
Local AE Title: Specify the Application Entity Title assigned to TestSCU (e.g., TEST_SCU). This is case-sensitive.
Local Port: While clients typically use ephemeral ports, some environments require defining a strict listening port if you expect synchronous responses (e.g., 104 or 11112). 2. Remote SCP (Target) Parameters
Input the networking details of the destination system (e.g., a PACS server like CharruaPACS):
Remote AE Title: Enter the exact AE Title of the target server.
IP Address / Hostname: The network address where the target server resides.
Port Number: The TCP port the remote server listens on (standard DICOM ports are usually 104, 4006, or 11112). 3. Execution & Workflow Troubleshooting
Once parameters are keyed in, tests should be executed in this logical order:
Run a C-ECHO (Echo) first. If this fails, check for firewall blocks, incorrect IP routing, or misaligned AE Titles on the server’s acceptance list.
Perform a C-FIND (Query) or Worklist search using a broad wildcard filter (e.g., Patient Name = *) to verify database access.
Attempt a C-STORE (Store) transmission with a sample .dcm image file to confirm directory write permissions on the target device. If you are setting this up right now, let me know:
What target system are you connecting to? (e.g., Orthanc, dcm4chee, a local PACS?)
Are you getting a specific error code? (e.g., Association Rejected, Timeout?)
I can walk you through adjusting your settings or diagnosing network blocks! CharruaPACS User Manual – CharruaSoft
Leave a Reply