DICOM example
This process shows how Cloverleaf handles a DICOM request, routes, and sends back the reply.
This example has one CL_SCP, that can receive the message to RIS, MPPS, and PACS, and routes:
- RIS message to to_RIS
- MPPS message to to_MPPS
- PACS message to to_PACS
The Dvtk Modality Emulator is used as an outside SCU side. All port are 11112. This is the port that is defined in the CL_SCP thread.
The AE Title that is set in the Emulator must match the Remote AE Title definition in to_RIS, to_MPPS, and to_PACS.
If they do not match, then the reply message is automatically dropped by the engine.
The Dvtk RIS Emulator is used as RIS (port 107, defined as Remote Port in to_RIS). It is also used as MPPS (port 108, defined as Remote Port in to_MPPS) systems.
The ConQuest DICOM server is used as a PACS system. The port is 5678, defined
as Remote Port in to_PACS.
StorageCommitmentPushModelSOPClass
is not supported, so you must use
another server on which to test Store Commit.
The TRXID Determination is DICOM.
Using a wildcard, you can only use the AbstractSyntax as trxid
in the data
route definition, and static
as the reply route.
To test:
- Configure and start the Modality Emulator, RIS Emulator, and ConQuest DICOM Server.
- Start process "Vivian".
- Click in Modality Emulator. This returns the results.
- Select one of the records.
- Store Image in Modality Emulator. When it is sending, you can open the ConQuest log. ConQuest receives several stored messages.
- Send MPPS Completed.