Conquest and SwiftMRI

Hello Marcel and greetings from germany,

I have a working installation with two Conquest Servers. The first is receiving the images from MRI, it stores all images and sends it to a second Conquest Server which is used for K-PACS with CD-Rom export and for image viewing.

This works from 2007 until today and is very stable!!!

Now wie plan to use SwiftMRI. The DICOM Images have to be transfered from Conquest1 to the SWIFT-Server. the Swift-Server than remodels the image and send it back to PACS.

Our problem is that only Conquest1 is in the hospital network AND in our own network. Conquest2 that needs the swift Images is only in hospital network.
So the images have to go from conquest1 to swift and than back from Swift to conquest1 and from there the same way as the last years with ExportConverter to Conquest2.
I would use a filter like ExportCallingAE for both ExportConverters (wich recognizes MRI-Scanner or SWIFT-Server) and sends images to swift or to conquest2.

what do you think, could this work or would you suggest a better way?

(PS: the admisitration of the hospital network is not really good in support so we try to do everything that´s possible without them in our own network...

Thanks, Björn

Hello,

I`m on Conquest 1.4.19c and we have 5.5TB of Data so a rebuild might cost a lot of time

And i must apologize but I never used the importconverter so I have to read first how to use it, but it sounds like a good idea to destroy the duplicates automatically. Can you give a simple example of Importconverter and could it filter by sending aet? that would be the most simple idea for me...

Thanks, Björn

I apologize... I was very blind, I found the manual...

I tested the ExportConverter with AET filter and that works so we are save

next days I will have a look at the ImportConverters.

Björn