Revisit visualization of planar annotations from SR

[fedorov]

Describe the Bug

Need to update to 3.12 and then see what happens about these:

1. arrows pointing to points do not disappear when scrolling
2. bounding box shows text corresponding to code+code meaning for finding or finding site, instead should show the code meaning from under Finding concept (and no code)

Steps to Reproduce

n/a

The current behavior

n/a

The expected behavior

na/

OS

na

Node version

na

Browser

na

[fedorov]

I will get back about this after testing 3.12 in dev.

[fedorov]

@igoroctaviano can we address the below in our fork to move on with this, or we need to wait for an update in upstream?

Point annotations: work much better, since they don't stick as I scroll through the stack. But:

• the text showing next to the circle is not helpful - it appears to show intensity value and coordinates (which make sense for a probe, but not for the target visualization). Instead, the text should show the same that is shown in the right hand panel ("Lesion" in the example below)
• the circle is movable! It should be static and not movable! This feels like another of those issues that for some reason is coming back again and again. @sedghi @wayfarer3130 - is it really such a niche IDC request to make sure that annotations loaded from DICOM are not modified by accident? Seems like a no-brainer medical device safety issue to me! What am I missing?

Bounding box annotations:

• similar to points, I think it is important to show the same annotation as in the right panel
• I am not convinced area and intensity stats are usable in all cases, but it clutters the interface a lot - I would prefer to have that enabled as an option, not as default
• same as with points - the box is movable!

[wayfarer3130]

There is a lock attribute on annotations - I have created: OHIF#5857 Auto lock loaded annotations by default I will ask James if we can include it - it is quite a small change so I don't imagine it will be an issue. Thank you for the suggestion - I hadn't thought about that aspect of things and I think it will be useful for other people. For the text showing next, I agree, it should show Lesion. Probably we should create a default sub-type of Probe that has this configuration in OHIF. Should be easy to do. I will let Igor create such an issue. Bill.

…

On Thu, 26 Feb 2026 at 14:02, Andrey Fedorov ***@***.***> wrote: *fedorov* left a comment (ImagingDataCommons/ViewersV3#107) <#107 (comment)> @igoroctaviano <https://github.com/igoroctaviano> can we address the below in our fork to move on with this, or we need to wait for an update in upstream? Point annotations: work much better, since they don't stick as I scroll through the stack. But: - the text showing next to the circle is not helpful - it appears to show intensity value and coordinates (which make sense for a probe, but not for the target visualization). Instead, the text should show the same that is shown in the right hand panel ("Lesion" in the example below) - the circle is movable! It should be static and not movable! This feels like another of those issues that for some reason is coming back again and again. @seghdi @wayfarer3130 <https://github.com/wayfarer3130> - is it really such a niche IDC request to make sure that annotations loaded from DICOM are not modified by accident? Seems like a no-brainer medical device safety issue to me! What am I missing? image.png (view on web) <https://github.com/user-attachments/assets/4caf2961-7f72-43aa-a14c-3cd3cadc48ca> Bounding box annotations: - similar to points, I think it is important to show the same annotation as in the right panel - I am not convinced area and intensity stats are usable in all cases, but it clutters the interface a lot - I would prefer to have that enabled as an option, not as default - same as with points - the box is movable! image.png (view on web) <https://github.com/user-attachments/assets/69ed381a-d3ec-468d-8368-15986973934c> — Reply to this email directly, view it on GitHub <#107 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGT56XOTWG3KYUHYU2FTAND4N47MTAVCNFSM6AAAAACU53O5WOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSNRYGU4TQNJUGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[fedorov]

@wayfarer3130 @igoroctaviano since this is a catch-all issue for the feedback - would it be possible to modify the annotation used for the probe, or parameterize it? Circle annotation is highly problematic, since it is not what is in the SR (which contains point), and it is not what is used for probing (I am assuming it probes at the center of the circle, and does not average over the circle area?). How about we switch to using an asterisk, or a cross? This is what is used in Slicer, and I think it is much less ambiguous as to what is actually being measured.

[igoroctaviano]

@wayfarer3130 @igoroctaviano since this is a catch-all issue for the feedback - would it be possible to modify the annotation used for the probe, or parameterize it? Circle annotation is highly problematic, since it is not what is in the SR (which contains point), and it is not what is used for probing (I am assuming it probes at the center of the circle, and does not average over the circle area?). How about we switch to using an asterisk, or a cross? This is what is used in Slicer, and I think it is much less ambiguous as to what is actually being measured.

Now that I have added subtypes its up to us/you decide how they should look like. It doesn't need to be a probe anymore. @wayfarer3130 can confirm that.

[fedorov]

@igoroctaviano what version do I need to deploy to test this? The fork or the latest OHIF?

It is broken completely in the one I have currently deployed...

https://viewers-sandbox-gha-testing.web.app/segmentation?StudyInstanceUIDs=1.3.6.1.4.1.14519.5.2.1.7311.5101.247316591887822227457894627822

[igoroctaviano]

@fedorov the fork.

[fedorov]

Same - does not work at all, does't recognize SR.

https://viewers-sandbox-gha-testing.web.app/segmentation?StudyInstanceUIDs=1.3.6.1.4.1.14519.5.2.1.7311.5101.247316591887822227457894627822