dicomedit for validation?

[Miklos Espak]

Hi,

is there a way to use an anonymisation script to refuse uploading DICOM images without certain tags?

It happened at our site that some images did not have series description tag that we need for our protocol. I'm wondering what would be the simplest way of enforcing this requirement.

Cheers,
Miklos

[Daniel Marcus]

Miklos,

Enforcement is always best done by flying to the site and giving the staff a good old fashioned beat down.

Within the XNAT realm, we've taken the approach of never rejecting data, b/c it's usually important to still archive data even if it's non-compliant.  However, you can set up a DICOM validation pipeline that will throw off a bunch of notifications if the data are non-compliant. With a little work, you might even be able to get it to auto-reserve your plane ticket to the site...

Documentation here: http://xnat15.wikispaces.com/Protocol+Check+Module

-Dan

--
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 post to this group, send email to xnat_di...@googlegroups.com.
Visit this group at http://groups.google.com/group/xnat_discussion?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Archie, Kevin]

On Feb 18, 2013, at 5:19 PM, Daniel Marcus wrote:

Enforcement is always best done by flying to the site and giving the staff a good old fashioned beat down.

Yikes. All work and no play makes Dan something something.

Within the XNAT realm, we've taken the approach of never rejecting data, b/c it's usually important to still archive data even if it's non-compliant.  However, you can set up a DICOM validation pipeline that will throw off a bunch of notifications if the data are non-compliant. With a little work, you might even be able to get it to auto-reserve your plane ticket to the site...

Documentation here: http://xnat15.wikispaces.com/Protocol+Check+Module

...which is absolutely the right way to do this.

I'll toss in a wrong approach that has some advantages: You could create a private project to hold bad sessions, then build a custom project identifier (https://wiki.xnat.org/display/XNAT16/DICOM+identifier+configuration+and+customization) that reads the DICOM metadata fields in question and shunts bad sessions to the trash project. This would be a little complicated to implement and configure, and isn't as elegant as the protocol check approach, but it keeps the bad sessions well out of the way.

  - Kevin

-Dan

On Mon, Feb 18, 2013 at 4:21 PM, Miklos Espak <m.e...@ucl.ac.uk> wrote:

Hi,

is there a way to use an anonymisation script to refuse uploading DICOM images without certain tags?

It happened at our site that some images did not have series description tag that we need for our protocol. I'm wondering what would be the simplest way of enforcing this requirement.

Cheers,
Miklos

--
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 post to this group, send email to xnat_di...@googlegroups.com.
Visit this group at http://groups.google.com/group/xnat_discussion?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
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 post to this group, send email to xnat_di...@googlegroups.com.
Visit this group at http://groups.google.com/group/xnat_discussion?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

---

The material in this message is private and may contain Protected Healthcare Information (PHI). 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.

[David Gutman]

Is a beat-down option part of the project plan for the next major XNAT release?

I'd love to beta-test it at my University.

David A Gutman, M.D. Ph.D.
Assistant Professor of Biomedical Informatics
Senior Research Scientist, Center for Comprehensive Informatics
Emory University School of Medicine

[Miklos Espak]

Hi guys,

thanks for the hints. We will kindly remind the sites of the protocol. :)

As I see, with the protocol check pipeline the missing DICOM tag would be discovered only after we archived the image. Or is there a way to auto-run a pipeline after an image arrives to the pre-archive? This would be useful also for other tasks, e.g. notifying people that data is waiting for archiving.

Do I understand correctly that with the custom project identifier approach the data would be in a trash project in the prearchive? Or does that code run at archiving only?

Cheers,
Miklos

[Archie, Kevin]

On Feb 19, 2013, at 6:41 AM, Miklos Espak wrote:

Do I understand correctly that with the custom project identifier approach the data would be in a trash project in the prearchive? Or does that code run at archiving only?

The project identifier is the piece that the DICOM receiver uses to figure out in which project each received file belongs. So you could turn off autoarchiving for the trash project, and those files would stay in the prearchive.

You would have to write your own Java code for the project identifier, as opposed to the protocol check where you'd just put together a config file. On the other hand, you'd get to write your own Java code for the project identifier, so you'd have full access to the DICOM metadata in each received object.

I don't know enough about the protocol check module to comment sensibly, so I won't try.

  - Kevin

--
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 post to this group, send email to xnat_di...@googlegroups.com.
Visit this group at http://groups.google.com/group/xnat_discussion?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Miklos Espak]

Great, I will try this approach.

Cheers,
Miklos

[Herrick, Rick]

It’s worth noting that bodily harm is one of the only management protocols enshrined in Dan’s office, but I do think he has it copyrighted, so you’ll have to check on fair-use agreements, etc., before copying. Or, well, you can guess what the penalty for THAT is.

[Torsten Rohlfing]

In case anyone is interested -

We have started putting together Python scripts to enforce imaging protocols for our consortium. Those scripts, which we run nightly on our server, are evolving here:

http://www.nitrc.org/plugins/scmsvn/viewcvs.php/scripts/pyxnat/?root=ncanda-datacore

Our main instrument for convincing people to comply is that the users who added offending datasets receive a daily (!) reminder email that lists all their failures until they fix them.

For added convenience, these mails include direct links to the non-compliant subject or session entries, so one can simply click through the list and fix these one by one.

Best,
  Torsten

[Daniel Marcus]

Hey Torsten,

Email harassment may be almost as effective as the more thuggish approach I advocated to Miklos with many fewer legal ramifications.  Great work!

-Dan

--