Integration of DICOM server with Horos/Osirix or other desktop viewing applications about dicom-server HOT 9 CLOSED

@JackPo, Qvera has pricing options that start well below $20k per year. To get a quote, please fill out a request at https://www.qvera.com/request-more-information/

from dicom-server.

Thanks for reaching out, we do not have this scheduled in our work, but we are happy to take contributions.

from dicom-server.

Hi @benjaminirving - as noted in the documentation, we do include the OHIF viewer as a default feature. There are many different viewers in the DICOM ecosystem, so our strategy is to implement the standard rather than test against each implementation. That said, I'd be happy to discuss your particular workflow and understand the value of the particular viewers you mentioned.

from dicom-server.

Thank you so much, @benjaminirving, for your comment. It really does make sense to have documentation on connecting to many different viewers and PACS system. We haven't done that, because of the standards-based nature of the product. But once you add in security, guides become very important. Given that Osirix is, according to their documentation, the most popular and widely used viewer on the planet, it makes sense to start there.

I can't promise anything in the short term, but this is an important piece of documentation. I want to make it as easy as possible for people to try out both this solution, and the hosted solution found in the Azure Healthcare APIs.

Thank you again, @benjaminirving. I appreciate your comment, and you trying the service!

from dicom-server.

Hi @stevenBorg/ @jovinson-ms By any chance documentation of integrating to Osirix came into your worklist? And if not, do you see this coming in near future? Thank you so much for your time in advance.

from dicom-server.

+1, would love instructions on this. About to move to GCP for this service because can't figure out how to get auth working from Osirix.

from dicom-server.

@JackPo @lijinjoseji @benjaminirving One option is to use an on-premise solution to convert between DIMSE to DICOMweb as described in the Azure Samples: https://github.com/Azure-Samples/azure-health-data-services-samples/blob/main/samples/dicom-demo-env/demo-instructions.md

from dicom-server.

Mike - thanks for linking the documentation.

I'll close this out given that we haven't seen much interaction lately, but if there's any additional feedback or questions, please let us know and we can reopen this issue.

from dicom-server.

Thanks so much for the pointer to the documentation, but I will point out that QVera and MedDream are both significant paid solutions, with QVera DICOM routing engine costing 20K+ just to route from DICOM QRS to DICOM WEB. It's a bit weird that Nuance PowerShare (now also owned by MSFT) can't even speak to DICOM Web, and the recommendation is to buy a subscription to a 20K+ product just to get messages from Nuance Powershare => Azure DICOMWeb.

from dicom-server.