The question is what distinguishes data that’s intended for the project(s) where you want to use this naming logic from data that’s intended for other projects? Without knowing that it’s hard to say if this is doable with the custom routing features.
The biggest issue is that, as best I can tell (it’s been QUITE a while since I’ve messed with this functionality, so I may be wrong on this), you can’t use the value of one tag when evaluating/expanding another. Say you want a rule something like:
“If the project found in StudyDescription is A, then if PatientID matches ^Session: (.*)$ use capture group 1 as the session label.”
That doesn’t work because the custom rule implementation only looks at a single tag at a time.
DicomEdit can do this sort of thing, though, something like:
(0008,1030) == "A" ? session := format["{0} {1}", StudyDate, StudyTime]
Outside of that, my first impulse would be to write a custom DICOM object identifier implementation that does exactly what you want (including handling the conditionals) then assign that to the DICOM receiver where this data will be sent. But I spend all day every day writing Java code in XNAT, so it’s probably not too surprising that that’s my first impulse 😊
--
Rick Herrick
XNAT Architect/Developer
Computational Imaging Laboratory
Washington University School of Medicine
From:
xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of John McLean <johnmc...@gmail.com>
Date: Tuesday, November 16, 2021 at 9:40 AM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] 'Contactless' custom dicom routing rules e.g. for QA scans
* 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/6aa37fb0-cb53-4586-84ec-f0a65d77651an%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.