Feature Requests

One potential path is using the DIMSE code from version one, found and packaged nicely here: https://github.com/OHIF/dicom-dimse You could use it as part of a standalone Node app, then provide some simple Express routes for DICOMWeb-style calls. Creating a node proxy between DICOMweb to make DIMSE calls. Why? Not all PACS support DICOMWeb. Having a way to connect to and interact with them may be essential to some teams.

_Awaiting scope from a qualified individual_ [ ] Angle [ ] Arrow [ ] Bi-Dimensional [ ] Ellipse [ ] Freehand

Thank you for incorporating the 2D MPR functionality into the REACT version. Are there planned updates for this functionality? If so, what are the updates planned and what is the time frame? I'm currently building a cancer research tool for a medical school's bio-medical engineering department and the 2D MPR functionality is a requirement. I'm wondering if I should merge my software with the current OHIF version or wait until the next update. Thank you, Marc McLean

The available tools and "More Menu" differ a fair amount from Version 1. We should modify the toolbar to align with Version 1's tool naming and tool placement. [ ] Rename the current menu named "More" to "View" [ ] Add a "More" menu. Move Bidirectional, Ellipse, Circle, Rectangle, Freehand, and Brush into it (in that order) [ ] Add missing tools (dragProbe, Magnify, clear tools, flip H, flip V, Invert, ROI Window) which were present in v1 (see viewer.ohif.org for the order) [ ] Fix tool names. 'EllipticalRoi' should be Ellipse. 'CircleRoi' should be Circle, 'RectangleRoi' should be Rectangle. Why? There was intentional decisions made for the original placements and naming The new placement causes the icons to wrap at an earlier minimum screen width

Estimated how we could integrate the visualizer with our RIS / HIS ?, Is there any documentation of the methods?

Linked Issue: https://github.com/OHIF/Viewers/issues/521 One of our more popular use cases is dropping the viewer into an existing application, Google Colab, Python Notebook, or Codesandbox to provide a quick demonstration of _something else_, or a quick view of interesting imaging data. Existing documentation for this approach lives here: https://docs.ohif.org/deployment/recipes/embedded-viewer.html While it is currently easier than customizing and building the OHIF Viewer, it still has too many hurdles to provide the ease of use one would expect. These should be addressed so it truly feels "drop-in". We need to remember, and optimize for, the use cases and users that this approach makes sense for.

Support setting the initial study/series/image to load and view via querystring parameters (route). Why? A common integration point for our viewer is as follows: 3rd party application is not capable of displaying DICOM images, but has thumbnails of images the end user may find interesting. When a thumbnail is selected, the 3rd party application launches the OHIF Viewer. Ideally, with the initial study/series/image loaded/viewable as the tapped thumbnail.

Migrate extensions to scoped OHIF packages: @OHIF/extension-{extension-name}

https://imgur.com/a/debwpmJ Add support for the Download Screenshot menu that existed in version 1.