Image data arrives where it belongs – even when modalities, PACS and practice systems do not speak the same dialect. Behind it sits a modular DICOM router.
IMConnect accepts DICOM associations, applies configurable filter rules and forwards them: one central entry point, routing by calling and called AE title to several PACS or archives. Unknown senders are rejected cleanly – with A-ASSOCIATE-RJ and the correct reject codes rather than a silent timeout.
What saves the most in practice: IMConnect rewrites AE titles, worklist responses and C-MOVE destinations on the fly. Sender and receiver stay as they are – you do not need an appointment with the modality vendor to carry out a change.
For operations: an audit trail of every DIMSE operation in PostgreSQL, binary PDU captures for troubleshooting, and several instances behind HAProxy that can be drained and reloaded one at a time through the management CLI – updates with no break in the image flow.
Your benefit
AE titles, worklist responses and C-MOVE destinations are rewritten in transit. Sender and receiver need not change anything.
An audit trail of every DIMSE operation in PostgreSQL, plus PDU captures – when something goes wrong you can show what passed through and what was rejected.
Several instances behind HAProxy, drain and reload through the management CLI: rolling updates instead of a maintenance window.
FAQ
A modular DICOM router. It accepts DICOM associations, applies configurable filter rules and processing steps and forwards them to the right destination – from simple forwarding through to rewrite plugins, audit trail and capture.
Through a central DICOM entry point: one listener, routing by calling and called AE title to several PACS or archives. Unknown senders are rejected cleanly – with A-ASSOCIATE-RJ and the correct DICOM reject codes rather than a silent timeout.
Usually not. IMConnect rewrites AE titles, worklist responses and C-MOVE destinations in transit, so sender and receiver can stay unchanged. That is exactly what saves you the appointment with the modality vendor.
Yes. Every DIMSE operation lands in an audit trail in PostgreSQL; for troubleshooting the binary PDU captures can be examined as well.
Several instances run behind HAProxy with an agent check. Through the management CLI an instance is drained and reloaded – updates roll through without a break in the image flow.
We look at your image flow and show where IMConnect simplifies it.