Testing XLT configurations

hcixlttest tests a translation specification without starting the engine. This tool requires only the name of the translation. This defines a translation specification that converts translation data into another format.

  • If an input file is not supplied, then the tool checks only the translation specification for validity.
  • If an input file is supplied, then the tool processes the messages in the input file.

You can configure a translation file to modify a DICOM data element value. DICOM can be used as input or output for a translation.

  1. For Translation File, click the folder button to open a file browser from which to select the file to test.
  2. Specify the testing data file in Choose Data File. You can also click the folder button to open a file browser to select the data file. By default, the file browser locates on the $HCISITEDIR/formats/ folder.
  3. Select how to process records.
    process all records reads the selected data file and processes all the records in it.
    process one record reads the selected data file and processes only the first record in the file.
  4. Select This defines a translation specification that converts translation data intoShow Field Names to show field names.
  5. Select Leak Detection to check for memory leaks.
  6. Select Print unreadable chars without changing to hex to print the output in pretty print.
  7. Open the Detail level menu to select from a list of detail levels for the test output that is reported in the Result pane. Detail levels go from 0 (raw, unparsed data) to 4 (most detail).
  8. Select the line termination format in which to save the test messages. Click the arrow to open a list of formats.
    Newline Terminated reads the data in the file until it finds a newline character, making all that data one message, and sends that to the parser. It then reads until it finds the next newline character, makes a second message, and sends that to the parser.
    Length Encoded reads the first 10 characters to determine the first message length. Then it reads that many characters into a message, and sends it to the parser.
    EOF Terminated reads the file until it gets to the end-of-file character, takes that as a message, and sends it to the parser.
  9. Specify the encoding in the Encoding field. You can also click the arrow to open a list of different encodings that identify the encoding of messages in the selected data file. The command converts the messages from the identified encoding to UTF-8 to perform the test. When you select an encoding from the list, an -e encoding option is added to the corresponding command line.
  10. For Pre Xlate TPS, click Edit to open the TPS Editor dialog box. Use this dialog box to select the TPS procedures to run before message translation. Click Add to select the procedures or Java class. Then, specify any arguments.
  11. For Post Xlate TPS, click Edit to open the TPS Editor dialog box. Use this dialog box to select the TPS procedures to run after message translation. Click Add to select the procedures or Java class. Then, specify any arguments.
  12. Specify a file name in which to store the result in the Save To field, or click the folder button to open a file browser.
  13. Select the line termination format in which to save the test messages. Click the arrow to open a list of formats.
    Newline Terminated reads the data in the file until it finds a newline character, making all that data one message, and sends that to the parser. It then reads until it finds the next newline character, makes a second message, and sends that to the parser.
    Length Encoded reads the first 10 characters to determine the first message length. Then it reads that many characters into a message, and sends it to the parser.
    EOF Terminated reads the file until it gets to the end-of-file character, takes that as a message, and sends it to the parser.
  14. In Inbound Separator Options and Outbound Separator Options, specify the separator characters for parsing messages.
  15. If required, then select Grep to filter the output.
  16. Click Run Command to run the command shown in Preview Command to Issue.
    As the test is being configured, a command-line command and the requisite parameters are generated in Preview Command to Issue. This is for display only. A command cannot be manually entered.