| "DICOM SEND" Needed ! :-) |
Oct 6, 2019 10:04 AM
by luke
by luke
The feature "DICOM SEND" is highly usefull and needed.
Please add this feature ASAP :-)
This will allow to send eg. quickly imported dicoms from ZIPs (great feature) to any destination in DICOM networkfrom RadiAnt's database.
Also "DICOM MOVE" allowing remote transfer between remote nodes usinf RadiAnt as a "remote control" would be very cool.
Great software BTW, congratulations ! I'm a pro (radiologist with deep technical background) and becoming a greatest fan of RadiAnt these days :-) All the best !
luke
Please add this feature ASAP :-)
This will allow to send eg. quickly imported dicoms from ZIPs (great feature) to any destination in DICOM networkfrom RadiAnt's database.
Also "DICOM MOVE" allowing remote transfer between remote nodes usinf RadiAnt as a "remote control" would be very cool.
Great software BTW, congratulations ! I'm a pro (radiologist with deep technical background) and becoming a greatest fan of RadiAnt these days :-) All the best !
luke
Oct 8, 2019 04:42 PM
by GT
by GT
Hellow my friend) Make yourself comfortable. We have been asking them for this for years...
Oct 13, 2019 08:44 AM
by luke
by luke
GT: But now there IS a database and there IS dicom network support. The only thing to add is she DICOM SEND command and it is simple now given the above facts.
At the moment adding it from DICOM OFFIS toolkit (dicom.offis.de/dcmtk) should be very easy.
Go RadiAnt ! :-)
At the moment adding it from DICOM OFFIS toolkit (dicom.offis.de/dcmtk) should be very easy.
Go RadiAnt ! :-)
Oct 15, 2019 07:36 PM
by
by
Luke, thank you for your kind words!
We only use our own proprietary code for DICOM files and network protocol.
The thing is that our focus was on the client features since the beginning of RadiAnt.
Which means reading DICOM files but not creating them.
For the DICOM send to work as expected, you have to often translate the original DICOM files into the transfer syntax supported by the server. We don't have the engine for such operations yet.
We only use our own proprietary code for DICOM files and network protocol.
The thing is that our focus was on the client features since the beginning of RadiAnt.
Which means reading DICOM files but not creating them.
For the DICOM send to work as expected, you have to often translate the original DICOM files into the transfer syntax supported by the server. We don't have the engine for such operations yet.
Oct 18, 2019 11:11 AM
by damian
by damian
Luke, as a workaround you may to try something like this: github.com/DraconPern/dovo