Healthcare API - Optimizing Image Loading in OHIF Viewer

[marco11]

Hello everyone,

We are currently working on integrating the OHIF viewer with Google Cloud Platform's Healthcare API to access DICOM images stored in GCP. We've successfully established a connection, and images are being loaded in the OHIF viewer. However, we're encountering a significant issue. The images we are dealing with are each about 50 MB in size, which is contributing to the problem.

Problem: When accessing images (instances) for a single patient (study), OHIF loads all images simultaneously. This approach is causing extremely slow performance and prolonged data loading times.

Ideal Solution: Our optimal solution would be to have the OHIF viewer load only the first selected image in the viewport at full resolution. The remaining images could be loaded as thumbnails or utilize any form of lazy loading strategy. This would significantly enhance the performance and user experience.

Current Configuration: We have attempted the following settings in the OHIF configuration:

• thumbnailRendering: 'wadors'
• enableStudyLazyLoad: true

Despite these settings, we are not achieving the desired outcome.

Request for Assistance: Has anyone faced a similar challenge or implemented a solution that aligns with our needs? Any advice, tips, or guidance on how to effectively configure OHIF for optimal image loading with the GCP Healthcare API would be immensely appreciated.

Thank you in advance for your insights and assistance!

[nimrah-waqar]

1. Custom Image Loading Logic: Modify OHIF viewer to load only the first selected image at full resolution, while the rest are loaded as thumbnails or using lazy loading strategies.

2. Pre-fetching and Caching: Implement mechanisms to pre-fetch and cache images in the background to reduce loading times.

3. Server-Side Optimization: Optimize server-side configurations and caching mechanisms in the Healthcare API to improve response times.

4. OHIF Viewer Plugins: Develop or utilize plugins that support lazy loading or thumbnail rendering strategies for improved performance.

5. Community Engagement: Seek advice and guidance from the OHIF community for tailored solutions and best practices.

6. Professional Services: Consider consulting experts for specialized assistance in optimizing image loading performance.

[ketki]

Hello @marco11 ,

We are currently working on similar problem. It would be really helpful if you post the steps that you took to implement this logic. We are able to connect to gcp but not able to open images with specific studyId due Cross Origin error.

Thank you in advance.

[Davisgtaylor]

Hi Ketki - same problem for me. Did you get this resolved? 

[Davisgtaylor]

Hi Marco, 

I have been trying to get OHIF working using a DICOM data store on GCP. Did you have trouble with CORS when you first implemented it? When I run the viewer after following the set up instructions from OHIF, I get a CORS request error. It doesn't appear any steps were missed.