Orthanc 1.12.9 and other updated plugins

Dear community,

Sébastien and myself are pleased to announce that Orthanc 1.12.9 is now available !

This new version includes many changes that aren’t directly visible to end users but that will enable new use cases in plugins. In particular, the plugin SDK now allows plugins or lua script to change the “Stable” status of a resource without waiting for the StableAge. Plugins are also now able to emit Audit Logs or listen to them to e.g. store them in the Orthanc database (currently implemented only in PostgreSQL).

Check the full Orhanc release notes.


The Orthanc Explorer 2 plugin has been updated to version 1.9.0 adding a new “inbox” page where users can fill a form and upload DICOM resources that are then processed by a custom python plugin. This new version can also display Audit Logs generated by the Authorization plugin.


PostgreSQL 9.0 is out with a few small optimizations and fixes + support for Audit Logs.

This version comes with an updated DB schema (rev 6) so check the Orthanc book if you have a large system with multiple Orthanc instances connected to the same DB.


The Authorization plugin has been updated to version 0.10.1 to better support anonymous users and audit-logs.


The OHIF plugin has been updated to version 1.7 featuring OHIF v3.11.0.


The Python plugin has been updated to version 6.0 to support new features like SetStableStatus, the Audit Logs, Key-Value Stores and Queues.


All these releases are available

Enjoy !

Alain

5 Likes

Oops, I forgot to release the DICOMWeb plugin …

So the DICOMWeb plugin has been updated to version 1.21 with a few small improvements.

It is now available

Enjoy !

Alain

1 Like

Hello Alain,

the new python plugin creates a /usr/orthanc.pyi .

First, under /usr this is an unusual place (maybe putting it to the *.so files?), second, I’m not sure its needed after generation of the rpm package.

Can you advise?

Thanks

Axel

Dear Axel,

Thanks for letting me know. The orthanc.pyi stub file is now excluded from the “install” step during the build. Python package developers should include this stub only when necessary.

The stub file could have been installed as /usr/include/orthanc/orthanc.pyi, but this would also have been an unnatural location regarding GNU/Linux packaging conventions.

Indeed, the file is not “needed” for the plugin to properly run. It is only useful to developers who would like to create Python plugins for Orthanc.

Regards,
Sébastien-