Use DICOM to store annotations

[ivmartel]

The current code saves presentation and drawing information in a json state file. This storage is not standard and cannot be shared easily. DICOM storage must be studied to replace the json file. For example:

• Grayscale Softcopy Presentation State: part03/sect_A.33
• Graphic Annotation Module: part03/sect_C.10.5
• Structured Report: part03/sect_A.35 (as suggested by David Clunie in DICOM SR for communicating planar annotations)

[wangwendong-code]

are you working with this?

[ivmartel]

Not right now, not sure when I will be able to... Any help is appreciated!

[ivmartel]

The plan for now is to first store annotations as DICOM SR and then store state as presentation state. This issue is for the first part, saving annotations. See progress on the related branch.

[ivmartel]

The possible shapes are limited by the possible values of the GraphicType type tag (00700023 on innolitics) ie POINT, MULTIPOINT, POLYLINE, CIRCLE and ELLIPSE (for 2D). That means that the freehand tool does not have a possible value, a possible replacement being a segmentation for this kind of complex shape.

So, unless somebody complains, this tool will not be reimplemented in the SR implementation.

[ivmartel]

Regarding the old state format, the plan is to support its loading but all code that allowed to save them will be removed. Remember that the old state was not as precise as the DICOM SR, its relation to the 'reference' data was very loose and there was no real guaranty for shapes drawn on oriented views.