Can you help figuring out how to get field "Hash Code Value" in DICOM SEG in Siemens?

[PaulJehanno]

It looks like the private tag (0x0029, 0x0069) in DICOM SEG is a "Hash Code Value" from syngo.via's conformance statement
it has a form like b"irx7etoed3dSUPCpTgkkTguJx33D6n3qzumjKdc0N1Rtb3aLhxNU/xfh0U2y0XWISEmkCM3nt0CMcOWwQ/C5bw==" that is a base64-encoding of a 512-bits signature, possibly a SHA512 result.

As a matter of fact, it looks like it only depends on SOPInstanceUID of the volume on which the DICOM SEG was made. in particular, the previously displayed signature was made on a series of only 2 SOPInstances of respective UID of "1" and "2", but no matter what binary i feed to sha512, I don't get the corresponding signature. (I tried the concatenation of both, encoding in utf-8, or inserting some separator, but nothing seems to work)

Do you know about these Siemens' "signature" and how to generate them?

[mrbean-bremen]

I have no idea how the hash is calculated - just to clarify:

Why do you want to generate private tags of another vendor (as opposed to read them, which is what the conformance statement is for)?
If you are generating your own segementation or secondary capture, you should use defined tags, or at the very least, your own private tags.

[PaulJehanno]

You're right, but I need to propagate the exact same Segmentation to another series, and the only way to do this is by providing this "signature" of the targeted series. I do add other private tag to mark it as a synthetic dicom though.

[mrbean-bremen]

I don't know your use case, and I guess that there is a valid reason to do it that way (to be recognized by syngo maybe?), but the better solution would really be to create some standard DICOM (like a secondary capture, for example). I realize that this may not be possible, but I'm afraid that the generated hash may depend on some internals of syngo that are not directly accessible (like the SOPInstanceUID of the internally created virtual "volume"). Sorry for not being more helpful here :/