Lighweight "zero footprint" 3D Slicer viewer wanted

For day clinical work it would be awesome (maybe wrong word - required) to have a lightweight, streamlined, fast, optimized, pretty, small preferable HTLM-5 or gradio based 3D SLicer viewed available, which does nothing but

  • display of slices ,
  • threedview and tables,
  • basic cropping,
  • windowing,
  • measurements,
  • labels
  • tables
  • GPU requirements should be minimal and be orientated at available PACS browsers

This reader should be FDA-approved.

It should be callable in a Chromium browser, HTML5 or gradio based, and should accept arguments such as passing data files or patient IDs, etc to enable the call from HIS systems. A threedview would be mandatory. MPR would be great. Cine would be mandatory. Saving videos ffmpeg videos or screenshots too. It must be highly configurable, should offer themes, in all aspects and keyboard shortcuts.
No Python or Python console.

It should be updated only once a year and the update should be fully automatic.

No extensions.

It should offer speech-to-text transcription with one of the more spread llm and the ability to build up a ChatGPT connection if API key is provided into a password or settings field.
Mainly a pure display tool for DCM, nrrd, mrb, glTF, obj, stl 3D data formats.
Segmentation list box with on off checkboxes.

Things to avoid: Docker, Jupyter etc. Too complicated to setup and maintain in a hospital.
It should support user authentication and user action logging.
It should be passable with data folders with just a few DLLs.


Looks like this is what ohif is meant to be.

I don’t know if there are means in slicer to satisfy the browser/html5 requirement

Hi @rbumm - yes, @pll_llq is correct, OHIF is an effort in that direction. Several of us in the Slicer community also work with OHIF and use it in various projects. For example the viewer integrated in the Imaging Data Commons is based on OHIF.

Regarding FDA approval, OHIF is a lot like Slicer in the sense that it’s an open source platform that can be used to make commercial products. There are several systems that make use of OHIF already, but one that may address your interests is FlexView.

Does OHIF have a 3D display that can be rotated in all axes? Did not see one, but there might be an extension …

OHIF version 3 (try the demo here) has been in development for a while now and has some very good 3D features. It is based on vtk.js, the javascript version of the C++ VTK that we use in Slicer, and OHIF v3 is extensible so new features can be exposed, like this MIP PET/CT example. Both Kitware’s Glance and VolView use vtk.js as well, so there’s a lot of synergy and features that are in any of the systems can in principle be migrated to any of the others with enough effort. They all have different goals so their user interfaces differ, and I think that of these FlexView is the one that is closest to what you are looking for (FDA cleared and supported for clinical use, but there may be others).

There’s more about OHIF in this paper: Open Health Imaging Foundation Viewer: An Extensible Open-Source Framework for Building Web-Based Imaging Applications to Support Cancer Research - PMC

One goal for me and others has been to use DICOM objects to enable standards-based interoperability between Slicer and OHIF.


You describe almost exactly what a radiology image viewer web application is. It is a very popular product category, which is slowly replacing desktop viewers, as web viewer capabilities expand, they are more mobile friendly, can leverage web technology stacks, and easier for IT departments to manage. There are hundreds of commercial systems offering such solutions (all PACS vendors and many other companies) and there are 5-10 open-source projects with similar goals. There may be just a very few specific requirements that are unlikely to be fulfilled (e.g., update limited to once a year, research/consumer file support in a clinical system, FDA approval for a community-supported project).

Slicer is in a different product category. It is an “advanced workstation”. It offers more features and has more resource needs and does not have be that mobile (no need for all the features in a phone).

I expect that the line between these two product categories will get more and more blurry in the coming years, because web applications will get more capabilities, desktop applications will become more web-friendly and web browser catches up to desktop operating systems. However, they fulfill quite different set of needs, so probably both will remain distinct categories for a good while.