Anonymization not updating ReferencedSeriesSequence->Item X->SeriesInstanceUID correctly

Hi there, I guess this one is mainly for you Sebastien.

We’ve been working extensively with the anonymization feature in Orthanc and I believe I’ve come across another field not updating correctly during the process. We run into issues when carrying across PR annotation graphics which do not display correctly after the anonymization due to the below bug. Please see the metadata snippets below:

Before anonymization of a PR instance.

  • ReferencedSeriesSequence :

  • Item #0 xfffee000

  • ReferencedImageSequence :

  • Item #0 xfffee000

  • ReferencedSOPClassUID : “1.2.840.10008.5.1.4.1.1.2” [ CT Image Storage ]

  • ReferencedSOPInstanceUID : “1.2.276.0.7230010.3.1.4.665618.6496.1542297415.301794”- SeriesInstanceUID : “1.2.276.0.7230010.3.1.3.665618.6496.1542297412.301746”
    After anonymization of the same PR instance.

  • ReferencedSeriesSequence :

  • Item #0 xfffee000

  • ReferencedImageSequence :

  • Item #0 xfffee000

  • ReferencedSOPClassUID : “1.2.840.10008.5.1.4.1.1.2” [ CT Image Storage ]

  • ReferencedSOPInstanceUID : “1.2.276.0.7230010.3.1.4.2976155648.3920.1553190927.305”- SeriesInstanceUID : “1.2.276.0.7230010.3.1.3.665618.6496.1542297412.301746”

as you can see, the number range has changed correctly for the ReferencedSOPInstanceUID (we fixed this together in 1.3.2). however the SeriesInstanceUID is not updated and still points to the old number range.

I can send over the full pre and post data if that helps.
regards,
Pär
www.cmrad.com

Hello,

Yes, please provide a sample DICOM file and associated call to the REST API so that I can add an integration test.

Regards,
Sébastien-

Hey Sebastien, thanks for getting back.

here is the test data you can use:

Pre-anonymization study (1 PR instance pointing at 1 CR instance): https://drive.google.com/open?id=17gdZ3HQw7QXHiCt38YNn2J_3ayIywbGh
Post-anonymization study (1 PR instance with broken series pointer to 1 CR instance): https://drive.google.com/open?id=1RTL3NfNHUzZxSZW_bSAqoBa5neYROF-Z

This is the only series level pointer which is causing us issues, but I know there are other nested DICOM tags also containing series level pointers which may need the same fix to the anonymization.

thanks again for a great product!
Pär
www.cmrad.com

Hello,

This issue should be fixed by the following changeset:
https://bitbucket.org/sjodogne/orthanc/commits/90b4a5001c24e542ddf87c992685ca3e766fad13

Obviously, as you noticed, there might be other DICOM tags that should be updated. The related patches to Orthanc should all have the same look: Please send me sample DICOM files, and I’ll try and make the patches quickly.

HTH,
Sébastien-

Thank you Sebastien, Extremely helpful as always.

In which future release will this become part of mainline? In order to stop tracking the patch.

I will review if we have further examples of the same behaviour for other DICOM tags and send them across. This one is part of a bug we are dealing with which breaks PR annotation objects during the anonymization process.

Thanks again,
Pär

Hi, Glad to read that this patch solves your issue!

No official release of Orthanc is planned in the short-term. Indeed, because of our strict quality control that is mandatory for healthcare software, the release process takes about one day-man, which is something we can’t afford too often.

Feel free to get in touch with Osimis support if you want to sponsor an early 1.5.7 release:
http://www.osimis.io/en/support.html