[script removed] This rule instructs the server to auto-route MR and CT studies to CLEARCANVAS
-->
<rule>
  <condition expressionLanguage="dicom">
    <and>
      <equal test="$Modality" refValue="CT" />
      <equal device="AN_SERVER" />
    and>
  condition>
  <action>
    <auto-route device="CT_SRV1" />
  action>
rule

 

 

Trying this rule to auto-route CT image when the images comes from particular device.  Rule is accepted but waiting if it will work. Can multiple device be use so condition can be placed for multiple device. When tried it get  syntax error that device is not defined.

 

 

ajg

 To route based on the source Application, you would do something like this:

 

 

<rule>
  <condition expressionLanguage="dicom">
    <or>
      <and>
        <equal test="$Modality" refValue="CT" />
        <equal test="$SourceApplicationEntityTitle" refValue="AN_SERVER" />
      </and>
      <and>
        <equal test="$Modality" refValue="MR" />
        <equal test="$SourceApplicationEntityTitle" refValue="MR_SERVER" />
      </and>
    </or>
  </condition>
  <action>
    <auto-route device="CT_SRV1" />
  </action>
</rule>

This rule will route MR studies from "MR_SERVER" or CT studies from "AN_SERVER". The key is that the "equal" must use a DICOM tag. We specifically fill in the tag Source Application Entity Title with the source AE Title for the purposes of auto-routing by device.

Steve

Auto routing is working as i planned

 

I also use the calling ae as a condition not to auto route to the original sending node. Useful when restoring from a backup server

Including the code in  the sample route would be great

 

 

thanks

ajg

 

 

 I entered a ticket for this here:

https://trac.clearcanvas.ca/source/ticket/5330

We'll include a new sample rule in the next release.

Steve

Hi,

  I have a rule that is for routing studies using the $"SourceApplicationEntityTitle" with a (not) operator and it isn't working as expected.  (sorry, my browser won't let me save any XML typed into this message window, it disappears when I save the post)   The study that gets sent to the imageserver is from the AE Tilte inside the operator and is routed every time.  The Source AE Title does have an '-' in it for example 'ae-TITLE' like so.  Hopefully this isn't causing any issues.

I had to attach my rule - can someone tell me how I can type or paste XML code into a post so that it shows up in a seperate window?  I have seen Steve do this many times and works great, I just can't get it to work for me as I see no way to do it with the tools provided on a reply/new post.

 Thanks for everyones help in these forums!

--Jamie

 Jamie,

As for adding XML into posts, its a little messy, but you have to go into the html editor (via the "add reply" button), and then edit the source html. From there you can add < pre > < code > < /code > < /pre > elements, and place the xml within the code element. If you switch back to the html view, the xml will not show up, but when you post it will be there.

As for your rule, you have some extra 'and' elements that aren't needed. The rules have an "implicit" and of their elements. , so the and elements you added are not needed. Could you try using a not-equal element and see if that makes a difference? In any case, your rule should route all CT images that are not from the AE title 'ae-TITLE'.  

In any case, I would suggest something like this:

 

 

<!-- 
This rule instructs the server to auto-route CT studies 
-->
<rule>
  <condition expressionLanguage="dicom">
      <equal test="$Modality" refValue="CT" />
      <not-equal test="$SourceApplicationEntityTitle" refValue="ae-TITLE" />
  </condition>
  <action>
    <auto-route device="CTROUTE" />
  </action>
</rule>

 

Steve

 

Steve- Thanks for helping me out with this rule. I tried the rule below and the rule still fails when studies arrive from the Source AE Title. I guess I'll try to change the source's AE title to see if that will make a difference. The source AE title has a different AE title for incoming and outgoing and I am positive I am using the correct one by verifying its settings and checking the CC logs.

 
 
<!-- 
This rule instructs the server to auto-route CT studies
-->
<rule>
   <condition expressionlanguage="dicom">     
     <equal test="$Modality" refvalue="CT">
     <not-equal test="$SourceApplicationEntityTitle" refvalue="ae-TITLE">
   </condition>
   <action>
     <auto-route device="CTROUTE">
   </action>
</rule>  
 
 

 

Jamie,

Could you take a look and do a listing of the actual DICOM files received for the study? Ie, find their location on disk (you can look at the study storage tab on the study details page), and then do a "dicom dump" in the viewer of the study, and find the value contained in the Source Application Entity Title tag? I'd just like to confirm that this is set to "ae-TITLE".

Steve

Steve-

     I just checked out a study that 'did not' get caught by my autoroute rule.  I viewed the study details of the study in the image server and then picked 'series details' tab and did a 'view details' of a series and brought up a 'series details' window that showed me the 'source AE:' which was 'ae-TITLE'.

Jamie,

Your rule is a "not-equal" rule, so this study would not auto-route, since your Source Application Entity title is equal to "ae-Title". Isn't this what you were expecting?

Steve

Well -

what I was hoping it would do is when study was written to the FS, it would look at the modality and say 'yes this is a CT' & then look at the Source AE and say 'no this is not from 'ae-TITLE' so then I need to autoroute this to 'CTROUTE'.  If the study was from any other Source AE other than 'ae-TITLE' then I would expect it to do the autoroute.

-thanks for your help on this steve!

 

Jamie

 Jamie,

Could you give a shot at using a rule with a regex to do this, instead of the equal?  I'm wondering if the issue is with the equal condition.  Here's an example:

<rule>
  <condition expressionLanguage="dicom">
    <regex test="$Modality" pattern="CT" />
    <not>
      <regex test="$SourceApplicationEntityTitle" pattern="ae-TITLE" />
    </not>
  </condition>
  <action>
    <auto-route device="CLEARCANVAS" />
  </action>
</rule>​

 

Thanks,

Steve

 Jamie,

I had one other suggestion, do you have the AE title (CTROUTE) as the destination of your rule defined as a Device on the device configuration page?  If the device is not defined, the rule will not attempt to move the study.  You should, however, get an error in the application log if this were the issue.

Steve

Hi All. New to CC and loving it. I'm considering implementing an autoroute based on date, PatientID and Type of study. So for example all CT's done on this date plus priors for each PatientID where the study is equal. i.e. PatientID=HI00012345 and study1 has today's date and it was a Chest 2V. PatientID also has priors with the same type-Chest 2V so it should include them in the autoroute. Is this possible? I would be willing to build my own script but I don't know what all the commands are, is there a reference manual?

Cheers,
Mark

Mark,

Unfortunately, the rules engine used by auto-routing only applies the rules on the study being processed. It does not have a way to determine priors and autoroute them. So, what you're thinking of doing really isn't possible.

Steve