Hi I really think Slicer is great and use it a ton, it continues to get better and better.
I work with clinicians (often remotely) and as I am not a clinician I would like to provide them a way to review a segmentation or model without editing stuff and have them login to a web portal remotely and view the information. From my experience with clinicians it needs to be very simple and not cluttered (distracting). Paraview has a nice client-server approach but it still requires downloading client, I guess there is paraviewWeb? which I haven’t tried.
The main thing would be able to have the traditional four up view with image data and the segmentation or model shown together on the image slices and in 3D view. Markups would be a nice to have to record comments but not required.
Does something like this exist? Does anyone have a suggestion about how this might be done.
There is now what we called
ParaviewGlance, you can give a try here: ParaView Glance
What is ParaviewGlance
In a nutshell, it is an example of client side web application built on top of vtk.js and itk.js allowing to load and visualize datasets. Both open-source under a permissive license.
Note that vtk.js has been built from the ground up to associated direction cosines with its image datastructure.
There is also a support for creating custom widget or annotation here is an example of box widget.
web portal integration
Building on these components and integrating them with a data management system providing authentication/user management as well as REST API allows to implement tailored workflow.
An example of such data-management system supporting this would be Girder, see Girder: a data management platform — Girder 3.1.7 documentation, but vtk.js and itk.js are agnostic to this particular system and could be integrated anywhere.
Out-of-box integration ?
All components enabling this exists. That said, some work is required to create a tailored application as well as its associated maintenance and deployment strategy.
Such solution could either be hosted within an institution, or deployed on cloud services ilke Amazon or Google depending on the requirement of each institution.
What about server side processing and Jupyter integration ?
If this is of interest, consider posting an other question on the forum.
However, for the use case that you describe, running Slicer in a docker container and allowing remote access through a web browser may be more suitable You can hide all user interface elements that you would not like the user to interact with. You can try an example here:
https://tinyurl.com/y82y5fk8 (link expired) – similar demo is available using Binder here
Multiple people can see and interact with the same Slicer instance and they all see the same view, which is great for collaboration/shared viewing (you can test it by opening the link in multiple browser windows). Also, viewing is immediate, no data need to be downloaded to the viewer’s computer.
Another obvious choice is to save image and segmentation data in DICOM format and push it to the clinical PACS system that clinicians can nowadays access remotely.