The CTP DICOM Filter
The CTP DicomFilter is a pipeline stage that provides preprocessing of DicomObjects, quarantining those which do not meet the conditions of a script program. This article describes the script language. The intended audience for this article is CTP administrators setting up a processing pipeline.
The Script Language
The script language interrogates a DICOM object and computes a boolean result that, if true, results in the object being accepted for further processing in the pipeline, and if false, results in the object being quarantined, aborting further processing.
An expression in the language consists of terms separated by operators and/or parentheses. There are three operators, listed in order of increasing precedence:
- + is logical or
- * is logical and
- ! is unary logical negation
- term + term * term
- term * (term + term) + term * !term
Terms in the language are either reserved words (true. or false.) (note the periods after the words) or expressions in the form:
An identifier is either a DICOM element name as defined in the CTP DICOM Anonymizer (e.g. SOPInstanceUID) or a DICOM tag, specified in square brackets (e.g. [0008,0018]). No spaces are permitted in identifiers, and tags are required to contain all eight hexadecimal digits identifying the group and element.
An element in the first item dataset of a sequence element may be referenced by connecting identifiers with pairs of colons, e.g. SeqOfUltrasoundRegions::RegionLocationMinY0 or [0018,6011]::[0018,601A]. There is no limit to the length of the chain of identifiers. All identifiers in the chain except the last must be sequence elements, and the last must not be a sequence element.
The language supports these methods:
- equals returns true if the value of the identifier exactly equals the string argument; otherwise, it returns false.
- equalsIgnoreCase is the case-insensitive version of equals.
- matches returns true if the value of the identifier matches the regular expression specified in the string argument; otherwise, it returns false.
- contains returns true if the value of the identifier contains the the string argument anywhere within it; otherwise, it returns false.
- containsIgnoreCase is the case-insensitive version of contains.
- startsWith returns true if the value of the identifier starts with the string argument; otherwise, it returns false.
- startsWithIgnoreCase is the case-insensitive version of startsWith.
- endsWith returns true if the value of the identifier ends with the string argument; otherwise, it returns false.
- endsWithIgnoreCase is the case-insensitive version of endsWith.
The value of an identifier is the string value stored in the DICOM object in the element associated with the identifier. If an identifier is missing from the received DICOM object, an empty string is provided.
All text starting with two '/' characters and proceeding to the end of the line is treated as a comment.
Suppose that images are to be rejected if they are of type "SECONDARY". Such images could be filtered out of the pipeline with a script like:
Note the unary negation operator, which is necessary to generate true for images which do not contain the string SECONDARY.
Suppose that images are to be rejected if they are of type "SECONDARY" or of type "DERIVED". Such images could be filtered out of the pipeline with a script like:
- !(ImageType.contains("SECONDARY") + ImageType.contains("DERIVED"))
Note again the unary negation operator, and also note the parentheses and the logical or operator, all of which combine to generate true only if the type is neither SECONDARY nor DERIVED.
The same effect could be achieved with a script like:
- !ImageType.contains("SECONDARY") * !ImageType.contains("DERIVED")
Note the use of the logical and operator and the way that each term is individually negated.
Finally, suppose that images containing any non-empty value in the ImageType element are to be rejected. Such images could be filtered out with a script like:
Note that in this case the unary negation operator is not used because if the element is missing or empty, the equals method will generate true, which is the value necessary to pass the object down the pipeline. This script could also be coded using the DICOM group and element numbers like this:
Here is an example with comments:
//This is a comment !PatientName.equals("xyz") //accept anybody but xyz + !PatientID.contains("1") //or anybody without a 1 in the PatientID //+ InstitutionName.containsIgnoreCase("JACKSONVILLE") //note: this line is ignored because it starts with // //This is another comment