[Bug] Unable to open multiframe segmentation in OHIF 3.9

[RTAN0411]

Describe the Bug

Unable to open multi-frame segmentation in OHIF 3.9, but possible for older versions of OHIF (e.g. 3.8.2)

Steps to Reproduce

1. Link Orthanc to OHIF by replacing the links in local_orthanc.js
2. Build and run the app
3. Upload dicom files and multi-frame dicom seg files
4. Open OHIF Viewer for the file
5. Drag segmentation files to Viewport

The current behavior

When I load a multi-frame segmentation onto OHIF along with the dicom image, I get a warning error: 'Image not present in stack, can
t import frame: xx' (where xx is the number starting from 0) that comes from Segmentation_4X.js, and the segmentation is not visible

Upon tracing the error, I realised the imageIds created in displaySet do not include WADORs links for frames 2 and beyond. It only contains the link for frame 1, but I am not too sure if this is the cause

This issue does not occur in older versions (I tried testing with 3.8.2)

The expected behavior

Upon double-clicking/dragging the segmentation to the Viewport, I would expect the segmentation to be shown on the screen

OS

macOS 15.1.1

Node version

22.7.0

Browser

Chrome 131.0.6778.205

[sedghi]

Could you kindly provide the data if it has been anonymized and you can confirm that there is no patient health information present in any of the headers or embedded within the pixel data?

[RTAN0411]

Could you kindly provide the data if it has been anonymized and you can confirm that there is no patient health information present in any of the headers or embedded within the pixel data?

Hi! I have uploaded the data in the drive folder: https://drive.google.com/drive/folders/1qYbLmY-Fck1MDkPB5FCr1MJhWMOGMFVa?usp=sharing

Please let me know if you face any issues

[RTAN0411]

Also, upon tracing the issue, I realised that the displaySet for the DICOM itself has an 'images' key-value pair and imageIds key-value pair, making it able to accommodate multi-frame DICOM. However, for DICOM SEG, the displaySet does not contain the key-value pair because it is not an instance of ImageSet as shown in the screenshots below.

If this is the case, how can we make changes to allow for handling the multi-frame DICOM SEG?

getSopClassHandlerModule.js -- DICOM image
Image

getSopClassHandlerModule.ts -- DICOM SEG