Closed terraboss closed 2 weeks ago
is this AI generated text? What is the feature request really here?
It's my feature request.
And as you can easily read from my post, it's about the OHIF installation using Docker.
Unfortunately, the official documentation is not very helpful. It should explain how to integrate data sources like Orthanc into OHIF so that users can not only view/test the official sample data on their own server, but are also capable add their own DICOM data.
Perhaps the easiest way would be GUI-based. Grafana, for example, has made it really easy to add data sources within their preferences. No need to study deeply the docs and (hidden and unofficial) sample code on GitHub. At the moment it's quite difficult to configure OHIF and its settings, add sources and customize it.
There does not seem to be much help from the OHIF community. That's sad.
For others who are interested in using OHIF with Orthanc, I can recommend this recipe: https://github.com/orthanc-server/orthanc-setup-samples/tree/master/docker/ohif
Unfortunately, OHIF seems to be unresponsive/slowly and buggy. For example, when I do a port mapping for the OHIF container (3000) to use it with my Nginx proxy manager, I get a blank page. Not so when opening with the recommended link path. Opening DICOM files can take a while if my server does not run out of memory.
And it seems that the latest versions of OHIF don't support uploads anymore, or have I missed some configuration option?
There are other recipes here as well https://github.com/OHIF/Viewers/tree/master/platform/app/.recipes
And it seems that the latest versions of OHIF don't support uploads anymore, or have I missed some configuration option?
You can do some googling
And click on the first link
and you see the upload was added
I understand your comments may have a negative sentiment, but I have received a lot of positive feedback from the community. Therefore, I will disregard this particular comment. Have a nice day.
I have googled a lot. And I also know the link with the hidden (!) templates on Github. However, it didn't help me much.
Overall, I think the OHIF project is great and a real benefit for the medical imaging world. Especially as I have cancer myself, with lots of DICOM data and want to be able to show my doctors at different clinics, very good friends and family members what medical imaging has been done at any time. Of course, not for the purpose of diagnosis, as the findings are already done, but for research purposes and direct communication, without explaining others 3D slicer and so on.
In the meantime, I have already had several Docker installations. But none of them were so complicated, nerve-wracking, poorly documented and unsupported as OHIF. This may be due to the still small (inactive ?) community or the fact that medical technicians and medical IT specialists want to get paid for it. All good, but as an open source project, I think it's a shame that it's so difficult to install and get started. It took me a few days to find a working recipe with the latest versions.
I would like to see more tutorials (e.g. on YouTube) showing how to install and use it with various other tools / interfaces.
Thank you for your understanding. And time.
Also, we have this too: https://docs.ohif.org/deployment/ Sorry to hear about your situation, I hope you overcome cancer and regain your health soon.
What feature or change would you like to see made?
I would like to propose enhanced Docker support for OHIF to improve the update process, system isolation, and configuration management. Specifically, the features should include:
Why should we prioritize this feature?
Prioritizing enhanced Docker support for OHIF will significantly improve system stability and security by ensuring isolated environments and streamlined updates. Additionally, it will enhance flexibility and extensibility, making configuration easier and enabling seamless integration of extensions and DICOM data management tools.