medical-image-computing

Is your feature request related to a problem? Please describe.

When a release is being created, the checklist associated with the issue documenting progress is manually crafted. For example, see Slicer/Slicer#5217 and Slicer/Slicer#5489.

While the steps are already documented on the wiki (see [here](https://www.slicer.org/wiki/Documentat

The current Transfer Options page leaves a bit to be desired. I propose that these aspects are improved:

• There isn't a way to enable a transfer syntax regardless of the SOP class (or at least for those already admitting at least one transfer syntax). This means that allowing a transfer syntax requires looking up every applicable SOP class.
• The "Select All" and "Deselect All" will check and

At the moment, standard codes used require manual typing of the code tuple, such as here. This is error-prone and long. Instead, we should use the #defined constants, as done in dcmsr: https://github.com/commontk/DCMTK/blob/patched-DCMTK-3.6.3_20180205/dcmsr/include/dcmtk/dcmsr/codes/dcm.h#L51.

It would be also i

cornerstone has native support for layers and transparency and it would be useful to output segmentations and heatmaps and show multi-modal images like PET-CT

relevant JS is https://github.com/cornerstonejs/cornerstone/blob/803dd7335e16de3cc398a3d42eda2552dd47cb1b/example/layers/index.html#L95-L152