OHIF as a standalone viewer in the browser without PACS server?

[Dalai Lama]

Hi,

is it possible to use the OHIF framework as a standalone viewer in the browser without a connection to a PACS backend?

Lets say our server delivers a DICOM binary to the front-end, can we feed the OHIF viewer somehow with this DICOM binary?

Cheers

[Antonio Diaz Tula]

Hello Dalai

We looked at the OHIF code a few weeks ago to try to do the same thing, but we did not find an easy way to do that. It seems to be designed to offer the web viewer along with the other services (PACS etc.) OHIF version 1 was easier to integrate with our custom backend.

Cheers

[Zaid Safadi]

Hey Dalai, you sure can use OHIF without a PACS in the back-end. All the viewer needs is an endpoint to return the DICOM file and some metadata that describes the display and structure (Studies, Series, Instances).

This is achieved by providing a JSON file with metadata and URL to the images you want to display. Here is an example:

JSON file: https://s3.eu-central-1.amazonaws.com/ohif-viewer/JSON/PTCTStudy.json

Viewer + JSON: http://viewer.ohif.org/viewer?url=https://s3.eu-central-1.amazonaws.com/ohif-viewer/JSON/PTCTStudy.json

-Zaid

[Dalai Lama]

Hi Zaid,

Thanks for your helpful response. I think you lead us into the right direction.

One more question:

What javascript library (e.g. parser) we have to use on the front-end (browser) in order to produce the DICOM Metadata JSON file 

https://s3.eu-central-1.amazonaws.com/ohif-viewer/JSON/PTCTStudy.json

you linked in your reply?

We have tried the cornsterstonejs/dicomParser but we cannot produce the JSON structure from DICOM files we drag and drop into their live examples.

Or did we miss something?

https://github.com/cornerstonejs/dicomParser

Thanks in advance!

-Dalai

[Dalai Lama]

[Willis Yonker]

Hi Zaid,

I'm trying to view files that are stored on the same machine that the OHIF viewer is on.  I have generated the .json file but it doesn't seem to work if I pass it.  The .json file and the DICOM files are served by an existing Apache setup.  Is that something that should work?  My URL looks like this:

http://10.1.1.100:3000/viewer?url=http://10.1.1.100/json/1_20200325_160958920.json

If I browse to http://10.1.1.100/json/1_20200325_160958920.json, the file is accessable.  The .json that I have generated has the following url line:

"url": "http://10.1.1.100/sent/1_20200325_160958920/SC.1.3.6.1.4.1.23849.1588592538.11.1637206557272669288.2.2.1.dcm"

would that work or does the URL need to be different?  If there is documentation on this that I should have read first, please let me know.  I did try to find something that would point me in the right direction but didn't get what I needed.

[Maciel Soncini Bueno]

Hello,

OHIF is not viewing exams where there are series with SOP UID 1.2.840.10008.5.1.4.1.1.7 in my environment.

Some way to solve it?  

Remetente notificado por Mailtrack 25/03/20 14:57:51

[nenad femic]

Hi Willis, did you solve this

 

[Willis Yonker]

On Thursday, March 26, 2020 at 7:53:23 AM UTC-4, nenad femic wrote:

Hi Willis, did you solve this

Unfortunately not.  I moved everything to the web server that yarn started.  That seemed to help with the json file but not the actual DICOM.  Originally I was serving them from my standard Apache that is also on the same box.

I guess my problem is I am new to yarn in general so even finding the logs is a challenge.  :)  

Still poking around though.

[Zaid Safadi]

Hi Willis, it seems to me your viewer to be running on port 3000 while your JSON is served on port 80.

Can you check your browser developer console if you have any CORS or other errors?

-Zaid

[nenad femic]

Hi Zaid,

i try to replace remote dicom files with my own, or at least to run over json  file over browser url as you set as example on this page.

my local server run and successfully  open remote dicom file over link

http://localhost:3000/viewer/2.25.63009447009646876712620988718732709379

but how to replace with my own files on local server or at least how to run over Amazon s3 storage. I was try to use

your json file in my local server but not work.

http://localhost:3000/viewer?url=https://s3.eu-central-1.amazonaws.com/ohif-viewer/JSON/PTCTStudy.json

Can y help

[Zaid Safadi]

How do you debug? What are the errors in your browser console?

[nenad femic]

Hi Zaid, when try to run http://localhost:3000/viewer?url=https://s3.eu-central-1.amazonaws.com/ohif-viewer/JSON/PTCTStudy.json

I get this info below in console:

On Sunday, March 29, 2020 at 12:53:04 PM UTC+2, Zaid Safadi wrote:

How do you debug? What are the errors in your browser console?

 

[Maciel Soncini Bueno]

Is Eclipse on OHIF and ROI the same tool?

If they are different, how do I enable ROI on OHIF?

Thanks.

[Maciel Soncini Bueno]

I have exams (x-rays and tomography for example) that on some computers you can see quickly (3 or 4 seconds).

The same exam on other computers can take up to 5 minutes to visualize.

What justifies such a big difference from one environment to another?

Thanks

[Jan Witowski]

You would have to provide some more information about the setup, are the "slower computers" trying to access a network where OHIF is deployed, where is the data stored etc.

[Maciel Soncini Bueno]

The viewer part is an amazon instance, running the viewer structure in docker (LDAP, Postgree, DCM4chee and OHIF).

--
You received this message because you are subscribed to the Google Groups "cornerstone platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cornerstone-plat...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cornerstone-platform/174336ea-4b9a-4851-8929-479ef14d175c%40googlegroups.com.

[Scott Kendall]

Hi Zaid,

 I'm also trying to use the viewer with your json and running into issues with StandaloneRouting.js (/platform/viewer/src/routes/)

I had to change some variables to get them to work on StandaloneRouting.js with your json
study.StudyInstanceUID -> study.studyInstanceUid
series.SeriesInstanceUID - > series.seriesInstanceUid
study.series -> study.seriesList

Getting past those errors, i go to this:

Tthere is nothing called metaData in instance, so I'm not sure what to do there. It's failing on line 98:

const { url: imageId, metadata: naturalizedDicom } = instance;

So then the rest of the function won't work

                // Add instance to metadata provider.
                metadataProvider.addInstance(naturalizedDicom);
                // Add imageId specific mapping to this data as the URL isn't necessarliy WADO-URI.
                metadataProvider.addImageIdToUIDs(imageId, {
                  StudyInstanceUID,
                  SeriesInstanceUID,
                  SOPInstanceUID: naturalizedDicom.SOPInstanceUID,
                });

Thanks for any help you can provide.

[Zaid Safadi]

I strongly recommend you open an issue on the OHIF GitHub repo to track this and get proper support.

https://github.com/OHIF/Viewers

[Scott Kendall]

Thanks, I will do that.   I wasn't sure if there is some guide on the JSON required for this to work anywhere, or if I should just assume yours is correct and the code is non-conforming now.

[Zaid Safadi]

@scott thanks for bringing this up. I think there has been a recent change in OHIF metadata that makes this JSON file not valid anymore. Please look at this issue here:

https://github.com/OHIF/Viewers/issues/1500

[Scott Kendall]

Yes, thank you, dannyrb pointed this out and after making updates to the json, I now have it working.