From IHE Wiki
Jump to: navigation, search
The test definitions on this page are RETIRED, but are kept here, for now, as an archive.


Export Selector Tests


Read the document IHE Tests: Transaction Sequences. This document lists all the transactions in a series of use cases which drive tests for individual actors. Export Selector will participate in a subset of the transactions. Reading that document will allow you to understand the full set of transactions for each test. These are the 1xx series tests. There are other tests that do not depend on message flow as defined in IHE Tests: Transaction Sequences. These other tests (the 4xx series tests) are used to evaluate more static features of the Export Selector, such as responses for specific keys as defined in the IHE Technical Framework. Each test is run using the same procedure. We assume you are using an interactive terminal or terminal emulator and are logged on to the MESA test system. Change directory to $MESA_TARGET/mesa_tests/rad/actors/expsel. Make sure the $MESA_TARGET and $MESA_STORAGE environment variables are set properly.

Integration Profiles and Test Procedures

This document lists a number of tests for Export Selector Systems. You may not be responsible for all of these tests. Please refer to the Connectathon web tool to list the required tests for your system. The web address of this tool depends on the year and project manager. Please contact the appropriate project manager to obtain this information.

Message Attributes

Message Values


Application AE Title Port Number

Read the Runtime Notes section of the Installation Guide to determine the proper settings for the MESA runtime environment.

Starting the MESA Servers

These instructions assume you are using a terminal emulator on Unix systems or an MS DOS command window under Windows NT. Each test uses a command line interface; there is no graphical user interface. Before you start the test procedure, you need to start several MESA servers. Make sure the appropriate database is running (PostgreSQL, SQL Server). To start the MESA servers:

1. Enter the Export Selector exam directory: mesa_tests/rad/actors/expsel

2. Execute the perl script to start the servers:

   perl  scripts/ [loglevel]

loglevel is an optional argument (0 is default). Log levels are:

0. no logging

1. errors

2. warnings

3. verbose

4. conversational (really verbose)

When you are finished running one or more tests, you can stop the servers:

   perl scripts/

Log files are stored in $MESA_TARGET/logs. For the security tests, the MESA servers are started with different scripts. These are scripts/start_mesa_secure.csh and scripts\start_mesa_secure.bat. The log levels are the same as for the standard tests. The syntax for starting the servers in secure mode is:

   scripts/start_mesa_secure.csh <log level> Unix
   set  LOGLEVEL=X (1, 2, 3, 4)  (Windows)

The MESA servers are stopped using these scripts: scripts/stop_mesa_secure.csh and scripts\stop_mesa_secure.bat.

Submission of Results

Test descriptions below inform the reader to “submit results to the Project Manager”. This is does not mean “email”. The current submission process should be documented by the Project Manager, but will not include emailing files directly to the Project Manager.

Unique Identifiers

Test Instructions

Please note the test instructions change starting with the 6.7.0 release. Each test is independent of the others. You must collect the results of one test before starting a new test.

1. Enter the Export Selector exam directory: mesa_tests/rad/actors/expsel.

2. Remember the MESA servers were started according to the directions in Starting the MESA Servers.

A test engine manages the test process. This test engine is driven by a text file that describes the events for the specific test. Each test below will indicate which script is appropriate. The arguments to the script are the test number and the log level for output:

1. errors only

2. warnings

3. verbose

4. reference information (pointers into IHE Technical Framework)

An example of the syntax used to invoke the script for the 3000 test is:

   perl  scripts/ 3000 1

The test script will announce what events are about to happen and will request that you send specific events according to the sequence defined in IHE Tests: Transaction Sequences. When you have completed the sequence of events, results can be evaluated by running the evaluation script:

   perl  <test>/eval_<test>.pl <log level> <MPPS Mgr AE Title>

For example:

   perl 131/ 3 AE_TITLE_FILLER

The log level for evaluation is defined as:

1. errors only

2. warnings

3. context information (verbose)

4. reference information (pointer into IHE Technical Framework)

Starting with version 6.7.0 of the MESA software, the user can change the patient name and patient ID of the test subject prior to running the test. This allows one to rerun a test without clearning the database of the prior subject. This is done from the directory $MESA_TARGET/mesa_tests/rads/msgs. A perl script is used to query the user for a new patient name and other demographics; the script automatically generates the new patient identifier. The perl script can also use an existing text file to specify the new demographics. The software is shipped with text files that are designed for IHE United States. It would be a simple task to make different text files for other countries. As listed in each sectio below, invoke the perl script with no arguments for interactive questions. If you specify an argument, it is the name of a text file with the demographic values.

Export Selector Tests

Each section below lists one Export Selector test. As mentioned above, the individual transactions involving the Export Selector under test are described in other documents.

Export Selector Test 3001: Simple Single Study Teaching File Export

Test case 3001 exercises the basic set of transactions needed to support the teaching file export workflow. The images sent by the Export Selection actor are deidentified by the Export Manager, who then transmits them to the Receiver.



This test was first written under the assumption that you would produce a Key Object note designed only for Teaching Files. As of version 11.8.0, you can run the same test for Clinical Trial Export. Run the test according to the script below, but use the proper document title for Clinical Trial Export. When you evaluate the output, use the proper code on the evaluation line.

To run this test:

   perl scripts/ 3001 <log>


To evaluate this test:

   perl 3001/ <log> <TF | CT>

Use TF if you are testing Teaching File Export; use CT if you are testing Clinical Trial export.

The output will be stored in 3001/mir_mesa_3001.xml. It should indicate pass/0 errors. When you have successfully completed that test, submit that XML file to the Project Manager (load into Kudu or Gazelle).

Supplemental Information

Export Selector Test 3003: Teaching File Export with Wait for More Data Sent via DICOM

Test case 3003 exercises the option of waiting for additional data. In this use case the data being waited for is transferred via DICOM, followed by a final manifest that includes the additional data.



To run this test:

   perl scripts/ 3003 <log>


To evaluate this test:

   perl 3003/ <log>

Supplemental Information