|The test definitions on this page are RETIRED, but are kept here, for now, as an archive.|
- 1 Export Receiver Tests
- 1.1 Introduction
- 1.2 Message Attributes
- 1.3 Message Values
- 1.4 Configuration
- 1.5 Starting the MESA Servers
- 1.6 Unique Identifiers
- 1.7 Test Instructions
- 1.8 Export Receiver Test 3001: Simple Single Study Teaching File Export
- 1.9 Export Receiver Test 3003: Teaching File Export with Wait for More Data Sent via DICOM
Export Receiver 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 Receiver 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 Receiver, 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/expmgr. 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 Receiver 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.
|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 Receiver exam directory: mesa_tests/rad/actors/expmgr
2. Execute the perl script to start the servers:
perl scripts/start_mesa_servers.pl [loglevel]
loglevel is an optional argument (0 is default). Log levels are:
0. no logging
4. conversational (really verbose)
When you are finished running one or more tests, you can stop the servers:
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) scripts\start_mesa_secure.bat
The MESA servers are stopped using these scripts: scripts/stop_mesa_secure.csh and scripts\stop_mesa_secure.bat.
NB: The method for starting the MESA servers in “standard” mode changes with the 6.6.0 release. This better allows the MESA servers to listen for connections on ports other than our assumed defaults. This helps with some Solaris installations where there is conflict with the ports we chose as default values.
'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 Receiver exam directory: mesa_tests/rad/actors/exprcr.
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
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/exprcr_tce.pl 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>
perl 131/eval_131.pl 3 AE_TITLE_FILLER
The log level for evaluation is defined as:
1. errors only
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 Receiver Tests
Each section below lists one Export Receiver test. As mentioned above, the individual transactions involving the Export Receiver under test are described in other documents.
Export Receiver 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.
To run this test:
perl scripts/exprcr_tce.pl 3001 <log>
To evaluate this test:
perl 3001/eval_3001.pl <log>
Export Receiver 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/exprcr_tce.pl 3003 <log>
To evaluate this test:
perl 3003/eval_3003.pl <log>