Anonymization order after upgrade to 1.8.10

[Tim Rosenow]

Hi there

Prior to version 1.8.10, I had updated my site anonymization location, using the "archive-processor-instance-api" on swagger, to "After Project Set", according to advice from Charlie Moore (https://groups.google.com/g/xnat_discussion/c/sGICBsJB3Vs/m/z_s1zXLvAwAJ), so that the anonymization process runs *before* setting the sessionID and hence I can create a custom sessionID from a composition of existing DICOM tags.

This is to create a session ID such as PatientID_StudyDescription.

Since upgrading to 1.8.10, this is no longer functioning as intended: the session names are being created and allocated before this script has run. There is nothing specific in the logs regarding this, and the anonymization script does run as intended.

Has the order of operations changed in 1.8.10 or some other way this is handled such that this is no longer functional?

[Tim Rosenow]

Just an update, I created a new image import processor and moved the logic there, this seems to have fixed the problem. Not sure if there was some changed behaviour regarding the site-wide anonymization process, but this is a working solution (for me at least)

[Timothy Olsen]

Are you setting the concatenated value in the DICOM object (like in the Patient ID)?  I've been playing with this a bit.  I was hoping I could set the name in the SessionData object in the processer, but I couldn't get that to work.  Updating the value in PatientID works, but then you are modifying the actual DICOM, which I was hoping to avoid.

Tim Olsen

[Moore, Charlie]

For some additional information, the reason this workflow broke is that it's an unfortunate side effect of the change in 1.8.9.2: https://wiki.xnat.org/documentation/xnat-1-8-9-2-release-notes .

Thanks,

Charlie

---

From: xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of Timothy Olsen <t...@xnatworks.io>
Sent: Thursday, September 19, 2024 4:58 PM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] Re: Anonymization order after upgrade to 1.8.10

 

t...@xnatworks.io appears similar to someone who previously sent you email, but may not be that person. Learn why this could be a risk

* External Email - Caution *

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/9a3a8830-876b-443a-8f63-2af4a56f80ban%40googlegroups.com.

 

---

The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.

[Tim Rosenow]

Oh, yes, I am modifying the actual DICOM. Basically I commandeered a DICOM tag I know is never used on our equipment (Clinical Trial Time Point Description), set this to my desired session name ("PatientID_StudyDescription" in my case), then configured xnat routing to use this tag to assign sessions. If that makes sense? 

I am happy to send you the plugin I wrote if you like, it's extremely basic and everything is hard coded because I'm lazy, but shouldn't be too hard to modify for your needs if you want. 

--
You received this message because you are subscribed to a topic in the Google Groups "xnat_discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/xnat_discussion/LmFig9CNUgY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to xnat_discussi...@googlegroups.com.