Estimated release for "ROOT ID" support ?

Google Groups archive
1

I know that is on the TO DO list:

======= General =======

  • Configure an user-defined site UID root if generating DICOM UIDs (“FromDcmtkBridge::GenerateUuid()”)

Just wondering if there is an estimated release for that or if it is just a wish list item.

Unrelated, but is there a way from within a Python Plug-in to call the DCMTK commands ? I actually have dcmtk installed via apt in some of my containers for some utility things, but wondering if DCMTK is baked into and callable via Orthanc. Thanks.

/sds

2

Hi,

This root id stuff is just a wishlist item which is not scheduled in the near future.

wrt DCMTK: no problem to call any tool that has been installed in the container.

Best regards,

Alain.

3

I noticed that Orthanc does have the ability to generate UID’s on demand via the API using some built-in algorithm:

e.g. https://demo.orthanc-server.com/tools/generate-uid?level=study

I looked at that on the demo server vs. various instances that I have running:

1.2.276.0.7230010.3.1.2.296486144.1.1639796803.395895 (demo server)

1.2.276.0.7230010.3.1.2.313263872.1.1639796838.238273 (my localhost)

1.2.276.0.7230010.3.1.2.313264896.1.1639797104.272622 (dev server)

That looks like the default DCMTK Root ID. Not sure what algorithm is being used to generate the suffix.

If I have my own ROOT ID, how reliable would it be to just substitute the one that I have for the '1.2.276.0.7230010.3.1.2’ generated there.

The application would be for creating the StudyInstanceUID’s for MWL files. I currently generate the files from JSON that is passed into a Python script, and it converts those to .wl / .dcm MWL files on the file system or fetches them out of a database. It would be pretty convenient to create the StudyInstanceUID’s when the MWL files are created by just substituting a configured ROOT ID in the Python script for the default one used by DCMTK and Orthanc. That would be quite easy to do in the Python Plug-in. I take it I would have to use the RESTAPI from the Plug-in vs. some more direct method to get a uid from the Plug-in ?

4

Correction about the DCMTK ROOT: 1.2.276.0.7230010.3

See:

https://forum.dcmtk.org/viewtopic.php?t=910
and:

https://forum.dcmtk.org/viewtopic.php?t=34

5

That looks like the default DCMTK Root ID. Not sure what algorithm is being used to generate the suffix.

This is generated by function “dcmGenerateUniqueIdentifier()” of DCMTK, as can be seen verbatim in the source code:
https://hg.orthanc-server.com/orthanc/file/Orthanc-1.9.7/OrthancFramework/Sources/DicomParsing/FromDcmtkBridge.cpp#l1412

Macro “SITE_STUDY_UID_ROOT” is defined by DCMTK;

I take it I would have to use the RESTAPI from the Plug-in vs. some more direct method to get a uid from the Plug-in ?

No, using “OrthancPluginRestApiGet()” on URI “/tools/generate-uid?level=study” is the way to go.