How to Evaluate/Fix Common Expression Errors (Eval tokens)

This type of error occurs when system attempts to retrieve value of an empty field. This expression expects a value stored for the field and cannot accept null value. In the above example, system is attempting to retrieve the clinical status of the visit associated which is empty.

Solution:

If the token is for an optional field, always use null safe operators (?.).
E.g.: eval("TreatmentType",#specimen?.visit?.clinicalStatus?.value).

This type of token is used when specimen label needs to extract substring after a separator e.g., dot (.) from parent specimen label. If there is no separator or text after the separator, system cannot extract a second part.

Solution: Ensure the parent specimen label has text after the separator (.)

This type of token is used to extract the substring from the start of the label up to the second occurrence of the underscore. For example, if the parent specimen label is "Parent_LabelText_01", it will extract "Parent_LabelText".

If system doesn't find any of the 2 underscores in parent specimen label, it returns -1. This leads to an invalid range in the substring method giving the StringIndexOutOfBoundsException.

In the above error message, end -1 indicates that the second underscore was not present in the parent specimen label.

Solution: Ensure the parent specimen label contains at least two underscores.