Open etpeterson opened 10 months ago
@etpeterson can you give more description on, I am hoping to work on it.
@Unique-Usman this is probably a multipart project and I wrote this up a while back so I wouldn't forget. Basically, what happens in hospitals is the images are created in DICOM format and pushed around using the c-store operation. It would be very convenient to be able to have a dicom listener running that accepts these pushes, then trigger the processing, then push the result somewhere else. It's much more complicated than that, but that's the basics.
I think it would make most sense as a docker image, but it could be a standalone program itself. Here's a list of projects that would have to be completed to make this work - roughly in order.
docker run <TF2.4image> <IVIM input images> <IVIM output images>
Almost surely I forgot something, but I think that largely outlines my thoughts. The goal is at the end to have a standalone container that can be integrated into processing pipelines with very little effort. I could create a new issue for some of the earlier ones with more detail if that still sounds interesting.
This sounds interesting. It also a big project. I think starting with the earlier ones seems interesting and I will like to work on it also. Thank you.
This sounds interesting. It also a big project. I think starting with the earlier ones seems interesting and I will like to work on it also. Thank you.
@Unique-Usman here's an issue I created for the first bullet if you want to tackle that one.
@etpeterson, thanks for the guidiance during the contribution. Can we move to the next line of action ?
@etpeterson, thanks for the guidiance during the contribution. Can we move to the next line of action ?
Sure! I created the next bullet point as a separate issue here.
This code will be used in pipeline processing. It is currently called on each dataset individually. However, medical imaging software is often configured so images can be pushed to it and it then pushes the results onward in the chain. It would be useful for this to be wrapped in a way that it can be triggered with DICOM pushes, and the processed images are subsequently pushed onward.
DICOM pushes should be supported, but also nifti files, for example bids format, should also be supported. This could take the form of websocket or HTTP methods.