3.1.0

DQR 3.1.0 rebuilds Send to PACS functionality on the modern dcm4che API and adds failure reporting for C-MOVE requests that return success but deliver nothing. It is compiled on JDK21 for XNAT 1.10.1+.

Send to PACS Reimplemented

• PLUGINS-354: Send to PACS fails immediately with "IllegalStateException: Connection ... not owned by DicomSender3Device". BasicCStoreSCU is replaced with Dcm4che3CStoreSCU, which changes send behavior in three ways:
  • Every object in a send request goes over a single association, whose presentation contexts are negotiated from the SOP classes and transfer syntaxes of the files themselves.
  • Each object is streamed to the PACS in the transfer syntax in which it is stored in the archive, preserving its original encoding rather than transcoding it. Objects archived gzip-compressed are decompressed en route.
  • The DIMSE status returned for each object is inspected. A warning status (Bxxx — the object was stored, but with data elements coerced or discarded) is logged and the send continues; any other non-success status fails the send, reporting the status code and the PACS error comment.

Bug Fixes

• PLUGINS-323: Mark PACS request FAILED when C-MOVE returns success but zero files. Previously PacsDequeueThread only logged a warning and left the request in the ISSUED state, so the study stalled with no failure signal. The request is now marked FAILED with the message Received zero files for study <uid> in project <project>, so downstream orchestration can detect and surface it.
• PLUGINS-353: Misspelling in PACS/VNA table of plugin settings. Corrects AETITILE in the AE summary on the PACS administration page.

Also New to the 3.x Line

These two changes shipped in DQR 2.4.0 on the 1.9.3.x line and reach the 3.x line for the first time in 3.1.0.

• PLUGINS-295: Add subject and experiment label fields to PacsRequest/QueuedPacsRequest routing, enabling incoming DICOM studies to be routed to a specific subject and experiment within a project at queue pickup time.
• PLUGINS-296: Split the single DICOMweb HTTP read timeout into two configurable preferences, so binary retrieval (WADO-RS) is no longer constrained by the shorter metadata-query timeout.
  • dicomWebMetadataReadTimeoutSeconds (default 20) — socket read timeout for DICOMweb metadata requests: QIDO-RS searches, instance metadata fetches, and PACS ping checks.
  • dicomWebRetrieveReadTimeoutSeconds (default 20) — socket read timeout for DICOMweb binary retrieval (WADO-RS multipart responses). Raise this on PACS implementations whose server-side response-assembly delay before the first byte exceeds the default.

2.4.1

DQR Plugin Version: 2.4.1

Bug Fixes

• PLUGINS-323 Fail a PACS request when a C-MOVE reports success but delivers zero files to the prearchive. Previously PacsDequeueThread only logged a warning and left the executed request in the ISSUED state, so the study stalled with no failure signal. The request is now marked FAILED with the message Received zero files for study <uid> in project <project> so downstream orchestration can detect and surface the failure.

2.4.0

Updating to version 2.4.0

3.0.0

Update to version 3.0.0 and parent version 1.10.0

2.3.2

Update to version 2.3.2

2.3.1

Update to version 2.3.1

2.3.0

Update to version 2.3.0

2.2.2

Update to version 2.2.2

2.2.1

Update to version 2.2.1

2.2.0

Update to version 2.2.0 and parent version 1.9.1