Hi @Morasta -
Sounds like you are exploring all the good options, but probably there isn’t yet a really complete end-to-end implementation that’s in production.
I’m not personally too familiar with the paraview approaches. Maybe you could describe a bit about what you want to achieve and why your current approach isn’t working for you and why you want to change direction?
For myself, we’ve been working mostly lately with this formulation (all should be easy to find by searching but let me know if you want more info):
- DICOMweb serving all the data (can come from Google Healthcare or self-hosted open source server)
- OHIF client for dicom study browser, layout, app context
- vtk.js plugin for MPR rendering
For server-side rendering with Slicer, I’ve been playing for a while with embedding a web server in Slicer. This actually works quite nicely, but it means you have to maintain a server with the user’s data loaded or create one on the fly. That’s why the client-side rendering is preferred in general, although there will be limits on how much data can be downloaded efficiently and how much can be loaded into the browser.
Hope that helps - I’m curious to hear what works best for your use case.