OrthanC and OHIF Viewer

Google Groups archive
1

Hi all, I’m doing some tests with eh OHIF viewer and OrthanC, versión 1.0.0 from 11/Dic/2015 with DicomWeb Pluging 0.2

I’m able to get the studies list from the OrthanC server, but with no Modality or # of images available.

Also If I click on any studie I get errors about "loading image: dicomweb:http://localhost:8042/wado?requestType=WADO&studyUID=……

OrthanC and the meteor server for OHIF are running on the same server, so ‘localhost’ it’s ok

Have anyone test them together? … do we need something more than the DicomWeb Pluging loaded?

The extrange thing is that I don’t see any log on the OrthanC trace about queries over the wado URL … just the dicom-web when queries the estudies.

2

Ummm … found this on the Chrome develop console:

XMLHttpRequest cannot load http://192.168.1.4:8042/wado?requestType=WADO&studyUID=1.2.392.200036.9125.…036.9125.4.0.370135861.1321736448.10040342&contentType=application%2Fdicom. No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘http://192.168.1.4:3000’ is therefore not allowed access.

I updated the URL on the OHIF setup file and now trying to get the images from other computer.

Also on the OrthanC trace file:

T0129 10:25:03.651295 OrthancPlugins.cpp:1685] Calling service 3001 from plugin /usr/local/share/orthanc/plugins/libOrthancDicomWeb.so
I0129 10:25:03.651326 OrthancPlugins.cpp:941] Plugin making REST GET call on URI /instances/07dcf9ef-0ccd54a6-91af5f58-a9bdfa20-51ed6aa9/file (built-in API)
T0129 10:25:03.651362 Statement.cpp:144] SQLite::Statement::Step SELECT internalId, resourceType FROM Resources WHERE publicId=?
T0129 10:25:03.651400 Statement.cpp:144] SQLite::Statement::Step SELECT internalId, resourceType FROM Resources WHERE publicId=?
T0129 10:25:03.651434 Statement.cpp:144] SQLite::Statement::Step SELECT uuid, uncompressedSize, compressionType, compressedSize, uncompressedMD5, compressedMD5 FROM AttachedFiles WHERE id=? AND fileType=?
T0129 10:25:03.717606 OrthancPlugins.cpp:1685] Calling service 2000 from plugin /usr/local/share/orthanc/plugins/libOrthancDicomWeb.so
T0129 10:25:11.409190 HttpOutput.cpp:370] Compressing a HTTP answer using gzip
E0129 10:25:11.432493 PluginsManager.cpp:194] Exception while invoking plugin service 2000: Error in the network protocol
E0129 10:25:11.435641 HttpOutput.cpp:71] This HTTP answer has not sent the proper number of bytes in its body

So something missing here … Who should send the headers for the CORS to works? … DicomWeb Pluging or OHIF client ?

3

Hi,

Orthanc does not natively support CORS.

For such deployments, please consider using nginx with CORS enabled:
https://orthanc.chu.ulg.ac.be/book/faq/nginx.html#enabling-cors

Please let me know if this helps.

Sébastien-

4

You have to enable CORS in orthanc
The easist way to do this is through a simple node.js reverse proxy server that included in ohif viewer at folder etc

5

You have to enable CORS in orthanc
The easist way to do this is through a simple node.js reverse proxy server that included in ohif viewer at folder etc

6

Hello,

Were you able to integrate OHIF Viewer and Orthanc?

I am trying to do something similar but in vain. I only see the Orthanc Explorer to upload images and send to DICOM modality but not able to integrate OHIF viewer

Thanks
Selva