Auto Route Rule with Multiple Entries

[cdeem]

I am writing an Auto Route rule that is based on the DICOM Tag of 0008,1030. My rule contain many entries, but I am limited as to the amount of characters that the rule can support. If I would create another rule that would simply continue on in the same manner, it would basically negate my first rule. Is there a way to link the rules together?

Or perhaps there is a way to extend the allowable number of characters that any given column in MySQL can support?

Any help would be appreciated.

Please see my actual rules below...

RULE 1
!((%00081030=ARTERIAL DOP, LOWER SEGMENTAL%) OR (%00081030=US ARTERY GRAFT, UNILAT%) OR (%00081030=CAROTID DOPPLER%) OR (%00081030=RENAL ARTERIAL FLOW%) OR ((%00081030=ULTRASOUND (USE TEXT)%)) OR (%00081030=BILAT LOW EXTREM VEN DOP%))

**Then route to AE1

RULE 2
!((%00081030=BILAT UP EXTREM VEN DOP%) OR (%00081030=LLE VENOUS DOPPLER%) OR (%00081030=RLE VENOUS DOPPLER%) OR (%00081030=LUE VENOUS DOPPLER%) OR (%00081030=RUE VENOUS DOPPLER%) OR (%00081030=RETROPER LTD AORTA OR KIDNEY%))

**Then route to AE1

I don't want any of the above studies to route to the destination, but the way it's laid out, study A may match RULE 1, but not RULE 2, thus resulting in the study still getting sent to the destination.

[pacsone]

The current routing rule pattern can hold up to 255 characters, so it should be more than enough to accommodate the examples you listed above (Rule 1 or Rule 2). So what seems to be the problem?

[cdeem]

In the example I gave, for the rule to apply correctly, it would require all the expressions to be contained in one rule. This would require much more than 255 characters. Can the 255 character limit be increased?

[pacsone]

Yes, you can certainly increase the field length for the pattern column of the AUTOROUTE table to any length you'd like, by running the following SQL query from the MySQL shell prompt after logging into the PacsOne Server database from a local command shell:

Code: Select all

mysql>alter table autoroute modify pattern VARCHAR(1024);

But it seems not efficient at all to enumerate all those string values in the same routing rule pattern, because it's very hard to keep track or trouble-shoot when there are that many string values applied with the logical OR operator. It makes more sense to classify the string values instead, e.g., all studies from the Ultrasound devices contain the string value that starts with "US*", and studies from the CT devices starts with "CT*", etc. Then you can create much simpler and manageable routing rules with those wild-card matching patterns.