[Feature]: Save additional metrics to SR report for all annotations

[abhijith-trenser]

Context

• This PR implements the feature described in [Feature Request] Save additional metrics to SR report for all annotations #459 .
• It is part of the corresponding PR in cs3d: [Feature]: Save additional metrics to SR report for all annotations cornerstonejs/cornerstone3D#2430
• This PR has been incorporated by FlyWheel.io

Changes & Results

• Added Radius, Mean, Maximum, and Minimum metrics to TID300 for Circle, Ellipse, and Polyline tools.
• Introduced a helper function buildContentSequence to eliminate repetitive graphic data usage across tools.

What are the effects of this change?

The following tools in Cornerstone3D, Length, Bidirectional, Ellipse, Circle, Rectangle, and Freehand now include all annotation metrics without requiring rendering.

This feature applies only to newly created SRs. Existing SR files will not reflect these changes unless re-saved.

Testing

• Launch a Study using /local
• Draw annotations in different slices using different tools.
• Open right side panel
• Click 'Create SR' and save the SR with a file name.
• Launch the same study along with the downloaded SR
• Load the SR into viewport and confirm to track the study
• Observe the annotations and all annotaions display all metrics without rendering it.

Checklist

PR

• My Pull Request title is descriptive, accurate and follows the
  semantic-release format and guidelines.

Code

• My code has been well-documented (function documentation, inline comments,
  etc.)

Public Documentation Updates

• The documentation page has been updated as necessary for any public API
  additions or removals.

Tested Environment

• OS: Windows 11
• Node version: 22
• Browser: Chrome 141.0.7390.123

[netlify]

✅ Deploy Preview for dcmjs2 ready!

Name	Link
🔨 Latest commit	4e0f2e2
🔍 Latest deploy log	https://app.netlify.com/projects/dcmjs2/deploys/6929bb9206dbc100087bb6f5
😎 Deploy Preview	https://deploy-preview-460--dcmjs2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[sen-trenser]

@sedghi Could you please review this or suggest anyone that can help with approving the PR in dcmjs?
This is related to cornerstonejs/cornerstone3D#2392

[wayfarer3130]

@sen-trenser - could you:

1. Attach an example dcm file for a planar freeform with 2 different types of measurement values?
2. Run dciodvfy on the example dcm file
3. Annotate a dcmdump verison of the example with your changes?
   It would just help a lot to have it well documented as to what the changes look like in terms of generated output.

[nithin-trenser]

@wayfarer3130 We found some errors when run dciodvfy on the example dcm file. Currently resolving these errors.

[nithin-trenser]

@wayfarer3130
Please find the attachment below.

1. Attach an example dcm file for a planar freeform with 2 different types of measurement values?
   • Example dcm files are attached Example_files.zip
2. Annotate a dcmdump verison of the example with your changes?
   • Annotated dcmdump version of example file -> sr-all-annotations.txt
     cc: @sen-trenser

[sen-trenser]

@wayfarer3130 We had some modifications to fix errors reported by the dciodvfy tool. Could you please check the attached data @nithin-trenser provided above?

Please check the area marked with text #################### in the sr-all-annotations.txt to see the new content changes.

[wayfarer3130]

There is the concept of INFERRED FROM allowing references to a common layout to be used - that basically looks like below:
Note the ReferencedContentItemIdentifier
It is legal to put those under ONLY the second and subsequent measurement. That isn't the "preferred" DICOM way, but it is legal DICOM as far as I know, and I believe is compliant with our parsing. The problem with just repeating data is that there isn't a way to tell it is actually the same/consistent data, and there are circumstances when it actually uses different data.
Would it be possible for you to make that tweak as well to reference the first set of data?

(0040,a730) SQ (Sequence with undefined length #=3) # u/l, 1 ContentSequence
(fffe,e000) na (Item with undefined length #=7) # u/l, 1 Item 1: SCOORD ROI
(0040,a010) CS [CONTAINS] # 10, 1 RelationshipType
(0040,a040) CS [SCOORD] # 6, 1 ValueType
(0040,a043) SQ (Sequence with undefined length #=1) # u/l, 1 ConceptNameCodeSequence
(fffe,e000) na (Item with undefined length #=3) # u/l, 1 Item
(0008,0100) SH [121071] # 6, 1 CodeValue (example: “Region of Interest”)
(0008,0102) SH [DCM] # 4, 1 CodingSchemeDesignator
(0008,0104) LO [ROI] # 4, 1 CodeMeaning
(fffe,e00d) na (ItemDelimitationItem) # 0, 0
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0
(0040,a730) SQ (Sequence with undefined length #=1) # u/l, 1 ContentSequence (child: IMAGE)
(fffe,e000) na (Item with undefined length #=4) # u/l, 1 Item 1.1: IMAGE
(0040,a010) CS [SELECTED FROM] # 14, 1 RelationshipType
(0040,a040) CS [IMAGE] # 6, 1 ValueType
(0008,1199) SQ (Sequence with undefined length #=1) # u/l, 1 ReferencedSOPSequence
(fffe,e000) na (Item with undefined length #=2) # u/l, 1 Item
(0008,1150) UI =CTImageStorage # 26, 1 ReferencedSOPClassUID
(0008,1155) UI [1.2.3.4.5.6.7.8.9] # xx, 1 ReferencedSOPInstanceUID (PUT YOUR UID HERE)
(fffe,e00d) na (ItemDelimitationItem) # 0, 0
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0
(fffe,e00d) na (ItemDelimitationItem) # 0, 0
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0
(0070,0022) FL 202.8033\60.46706\202.8033\114.96518\193.98744\87.716118\211.61917 # 32, 8 GraphicData
(0070,0023) CS [ELLIPSE] # 8, 1 GraphicType
(fffe,e00d) na (ItemDelimitationItem) # 0, 0 ItemDelimitationItem

(fffe,e000) na (Item with undefined length #=6) # u/l, 1 Item 2: NUM Measurement #1
(0040,a010) CS [CONTAINS] # 10, 1 RelationshipType
(0040,a040) CS [NUM] # 4, 1 ValueType
(0040,a043) SQ (Sequence with undefined length #=1) # u/l, 1 ConceptNameCodeSequence
(fffe,e000) na (Item with undefined length #=3) # u/l, 1 Item
(0008,0100) SH [121206] # 6, 1 CodeValue (example: “Length”)
(0008,0102) SH [DCM] # 4, 1 CodingSchemeDesignator
(0008,0104) LO [Length] # 6, 1 CodeMeaning
(fffe,e00d) na (ItemDelimitationItem) # 0, 0
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0
(0040,a300) SQ (Sequence with undefined length #=1) # u/l, 1 MeasuredValueSequence
(fffe,e000) na (Item with undefined length #=4) # u/l, 1 Item
(0040,a30a) DS [12.3] # 4, 1 NumericValue (PUT YOUR VALUE)
(0040,08ea) SQ (Sequence with undefined length #=1) # u/l, 1 MeasurementUnitsCodeSequence
(fffe,e000) na (Item with undefined length #=3) # u/l, 1 Item
(0008,0100) SH [mm] # 2, 1 CodeValue
(0008,0102) SH [UCUM] # 4, 1 CodingSchemeDesignator
(0008,0104) LO [millimeter] # 10, 1 CodeMeaning
(fffe,e00d) na (ItemDelimitationItem) # 0, 0
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0
(fffe,e00d) na (ItemDelimitationItem) # 0, 0
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0
(0040,a730) SQ (Sequence with undefined length #=1) # u/l, 1 ContentSequence (evidence: by-reference)
(fffe,e000) na (Item with undefined length #=2) # u/l, 1 Item 2.1: by-reference to SCOORD
(0040,a010) CS [INFERRED FROM] # 14, 1 RelationshipType
(0040,db73) UL 1 # 4, 1 ReferencedContentItemIdentifier (REFERS TO ITEM 1)
(fffe,e00d) na (ItemDelimitationItem) # 0, 0
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0
(fffe,e00d) na (ItemDelimitationItem) # 0, 0 ItemDelimitationItem

(fffe,e000) na (Item with undefined length #=6) # u/l, 1 Item 3: NUM Measurement #2
(0040,a010) CS [CONTAINS] # 10, 1 RelationshipType
(0040,a040) CS [NUM] # 4, 1 ValueType
(0040,a043) SQ (Sequence with undefined length #=1) # u/l, 1 ConceptNameCodeSequence
(fffe,e000) na (Item with undefined length #=3) # u/l, 1 Item
(0008,0100) SH [121207] # 6, 1 CodeValue (example: “Area”)
(0008,0102) SH [DCM] # 4, 1 CodingSchemeDesignator
(0008,0104) LO [Area] # 4, 1 CodeMeaning
(fffe,e00d) na (ItemDelimitationItem) # 0, 0
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0
(0040,a300) SQ (Sequence with undefined length #=1) # u/l, 1 MeasuredValueSequence
(fffe,e000) na (Item with undefined length #=4) # u/l, 1 Item
(0040,a30a) DS [45.6] # 4, 1 NumericValue (PUT YOUR VALUE)
(0040,08ea) SQ (Sequence with undefined length #=1) # u/l, 1 MeasurementUnitsCodeSequence
(fffe,e000) na (Item with undefined length #=3) # u/l, 1 Item
(0008,0100) SH [mm2] # 3, 1 CodeValue
(0008,0102) SH [UCUM] # 4, 1 CodingSchemeDesignator
(0008,0104) LO [square millimeter] # 17, 1 CodeMeaning
(fffe,e00d) na (ItemDelimitationItem) # 0, 0
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0
(fffe,e00d) na (ItemDelimitationItem) # 0, 0
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0
(0040,a730) SQ (Sequence with undefined length #=1) # u/l, 1 ContentSequence (evidence: by-reference)
(fffe,e000) na (Item with undefined length #=2) # u/l, 1 Item 3.1: by-reference to SCOORD
(0040,a010) CS [INFERRED FROM] # 14, 1 RelationshipType
(0040,db73) UL 1 # 4, 1 ReferencedContentItemIdentifier (REFERS TO ITEM 1)
(fffe,e00d) na (ItemDelimitationItem) # 0, 0
(fffe,e0dd) na (SequenceDelimitationItem) # 0, 0
(fffe,e00d) na (ItemDelimitationItem) # 0, 0 ItemDelimitationItem

[wayfarer3130]

@pieper - for the saving of SR annotations, I'm proposing that second and subsequent measurements use references to the annotation definition in the first measurement value - that is, a structure like:

measurement value 1:
max value MAX
annotation graphic data ....
measurement value 2:
min value: MIN
annotation reference: 1/1 (refers to first sub-sequence of the shared measurement value, starting from the shared parent.)

The TID 1500 canonical way I believe is:
annotation graphic data: ...
measurement value 1:
max value MAX
annotation reference: 1
measurement value 2:
min value MIN
annotation reference: 2

As I read part 16, I THINK either way is acceptable, but I'm not 100% sure. The point in either one is to avoid duplicating the image/graphic data references so that there is no chance that they are different. That is only done when they actually ARE the same - things like bidirectional are not the same annotations first/second.

Might ask David what he thinks about this? I'd very much prefer not to go down something not standards compliant.