Failed to get frame details from dicomweb-server to render in OHIF viewer

[Karthik-Devaraj]

I am trying to use this dicomweb-server (https://github.com/dcmjs-org/dicomweb-server) to render in OHIF viewer.

I tried this setup in Window 10.

I have used the below configuration dicomWeb: [{ name: 'dicomweb_server', wadoUriRoot: 'http://localhost:8084', qidoRoot: 'http://localhost:8084', wadoRoot: 'http://localhost:8084', qidoSupportsIncludeField: true, imageRendering: 'wadors', thumbnailRendering: 'wadors', enableStudyLazyLoad: true, supportsFuzzyMatching: true, requestOptions: { "requestFromBrowser": true } }, ],

I am facing issue to fetch wadors frame API /studies/1.3.6.1.4.1.5962.99.1.3975984249.1189277055.1386955486329.3.0/series/1.3.6.1.4.1.5962.99.1.3975984249.1189277055.1386955486329.4.0/instances/1.3.6.1.4.1.5962.99.1.3975984249.1189277055.1386955486329.2.0/frames/1 Error message: {"statusCode":404,"error":"Not Found","message":"Frame 1 was not found. Error: Empty buffer"}

Other API's like fetch studies, series, instance are working fine.

I can able to download the instance stream as dcm file from the below URL /studies/1.3.6.1.4.1.5962.99.1.3975984249.1189277055.1386955486329.3.0/series/1.3.6.1.4.1.5962.99.1.3975984249.1189277055.1386955486329.4.0/instances/1.3.6.1.4.1.5962.99.1.3975984249.1189277055.1386955486329.2.0

Please let me know, if I am missing anything in the configuration.

Thanks in advance.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[richsmith123]

Hello Karthik,

Did you find any solution to this issue? I am facing similar issue on my side. If you did find any solution then kindly share your findings.

Thanks, Rick

[Oumaima26]

Hello Karthik,

Did you find any solution to this issue? I am facing similar issue on my side. If you did find any solution then kindly share your findings.

Thanks, Omaima

[taivnn9]

Here is answer from chat gpt, maybe that can help.

If you're having trouble retrieving frame details using the dicomweb-server and OHIF viewer, there could be a few different issues at play. Here are a few things you can check:

Verify that your DICOM images and related metadata are being served correctly by the dicomweb-server. You can do this by testing the server's endpoints directly using a tool like Postman or cURL. Make sure that you are able to retrieve the DICOM images and metadata using the correct DICOMweb API endpoints.

Check that the DICOMweb API endpoints you are using are supported by the version of OHIF viewer you are using. Different versions of OHIF viewer may support different versions of the DICOMweb standard, so it's important to ensure that the endpoints you are using are compatible with your version of OHIF viewer.

Make sure that you are sending the correct request headers and parameters when requesting frame details. Double-check that the multipart/related media type is being used in the request header, and that the start parameter is set to the correct value for the DICOM image and related metadata you are requesting.

Check the logs of the dicomweb-server to see if there are any error messages or warnings that could give you a clue as to what might be going wrong.

If none of these steps help you resolve the issue, you may need to provide more details about your setup and the specific error messages you are seeing in order to get more specific guidance on how to fix the problem.

[sedghi]

Thank you for your past contributions and for raising this issue related to legacy versions of our OHIF Viewer. Your time and effort have been invaluable in helping us improve the product.

We wanted to update you that our development focus has shifted to OHIF Viewer v3, which is now available for testing on viewer-dev.ohif.org. This site is deployed from our master branch and incorporates new features, optimizations, and bug fixes. If you're still using viewer.ohif.org, it's worth noting that this is deployed from our release branch and may not have the latest updates. You can read more about our branching strategies here.

Given the move to Version 3, we are closing older issues that pertain to Versions 1 and 2, as we are no longer providing support for those versions. If you find that the issue you've raised is still relevant in Version 3, we encourage you to reopen this issue or create a new one for proper triage.

Thank you for your understanding and continued support.