HIMSS and RSNA
Integrating the Healthcare Enterprise
IHE/MESA Importer Tests
Electronic Radiology Laboratory
Mallinckrodt Institute of Radiology
510 South Kingshighway Blvd.
St. Louis, MO 63110
314.362.6965 (Voice)
314.362.6971 (Fax)
Revision 10.1.0
August 25, 2006
Importer Tests
Introduction
Message Attributes
Message Values
Configuration
Starting the MESA Servers
Loading Test Data
Submission of Results
Test Cases: Importer
This document lists a number of tests for Importer 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.
The Importer scripts use an ASCII configuration file to identify parameters such as host names and port numbers. The configuration file is named imp_test.cfg and is included in the directory $MESA_TARGET/mesa_tests/rad/actors/importer. Edit the file and change entries (host name, port number) which pertain to your system. Your system is identified by entries that begin with TEST.
For IHE Basic Security tests, all messages are exchanged using TLS. MESA servers are run on the same ports but with the TLS option. The configuration file that identifies your information is imp_secure.cfg. This separate file allows you to use different port numbers for secure and standard configurations. You may decide to use the same port numbers for both types of communication. The MESA software will only use all secure or all standard communication for a test; we do not mix communication protocols.
This version of the software assumes the AE title of your Importer is IMPORTER1. That will be the Scheduled AE title and the AE title we assume you use when you send images, mpps events and storage commitment requests. Please use this AE title for your Importer.
Importers will communicate with two MESA servers during these tests. Parameters for the tests are listed below. Worklist queries should be sent to the MESA MWL Server. All other messages (storage, storage commitment, MPPS) should be sent to the MESA Image Manager.
The file $MESA_TARGET/runtime/imgmgr/ds_dcm.cfg is used to configure the MESA Image Manager . The only parameter users should change is the LOG_LEVEL value. Log levels are defined in the "Starting MESA Servers" section below. DICOM configuration parameters are listed in the table below.
System |
Application Entity Title |
Port |
MESA Image Manager |
MESA_IMG_MGR |
2350 |
MESA MWL Server |
MESA_MWL |
2250 |
MESA Audit Record Repository |
|
4000 |
There is a one-time setup step to run before any tests are started. DICOM UIDs and other identifiers have seed values which are stored in the MESA databases. You should reset the UIDs one time before you start the tests. If you decide to rerun tests, you should not have to reset the UIDs. If you decide to reload the Modality Worklist, you will get different Study Instance UIDs (which is probably the behavior that you want).
To set the UIDs for the first time or reset them at a later time:
perl scripts/reset_uids.pl
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 the MESA Order Placer and MESA Order Filler servers. Make sure the appropriate database is running (PostgreSQL, SQL Server). To start the MESA servers:
scripts/start_mesa_servers.csh (Unix)scripts\start_mesa_servers.bat (Windows)
Log levels are set for the MESA Image Manager in the file: $MESA_TARGET/runtime/rpt_manager/ds_dcm.cfg. / Log levels are:
When you are finished running one or more tests, you can stop the servers:
scripts/stop_mesa_servers.csh (Unix)
scripts\stop_mesa_servers.bat (Windows)
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 MESA servers are stopped using these scripts: scripts/stop_mesa_secure.csh and scripts\stop_mesa_secure.bat.
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.
These test cases are associated with the Radiology Import Reconciliation Workflow (IRWF) profile
Test 283: DICOM Composite Object Evaluation – DVTNOTE: This test is not yet available in the importer directory; you must run this test from the MESA_TARGET/rad/actors/mod directory In this test, you evaluate samples of Composite Objects that you create using the Agfa/Philips DVT. The number of evaluations you run depends on the types of images that you import/produce. We will not list specific requirements, but ask you to apply good judgment. ReferencesInstructions
EvaluationSupplemental InformationTest 283 assumes you have installed the DVT on a Windows system. You may elect not to run this test, but you will be required to run test 284. If you choose not to run this test, create a file with a message that indicates you have chosen to run test 284 and submit that file as the results for test 283. |
NOTE: This test is not yet available in the importer directory; you must run this test from the MESA_TARGET/rad/actors/mod directory
In this test, you evaluate samples of Composite Objects that you create using the Dave Clunie DICOM3TOOLS. The number of evaluations you run depends on the types of images that you import/produce. We will not list specific requirements, but ask you to apply good judgment.
You need to evaluate and provide the output for at least one DICOM Composite Object. Evaluating other objects can only help your implementation.
perl 284/eval_284.pl <output level> <path to file>
Test 284 assumes you have installed the MESA tools on a Unix system. You may elect not to run this test, but you will be required to run test 283. If you choose not to run this test, create a file with a message that indicates you have chosen to run test 283 and submit that file as the results for test 284.
Test Case 3705: MWL Test for Scheduled Import OptionThis test case exercises the MWL SCU capabilities of the Importer actor for those Importer actors supporting the Scheduled Import Option in the IRWF profile. The Importer’s requirements for transaction RAD-5 are the same as those for an Acquisition Modality in Scheduled Workflow. ReferencesRAD TF-2: 4.5.4.1.2.2 Instructions<this test is intented to test the Importer’s ability to query the DSS/OF for MWL. It is not implemented yet.> EvaluationSupplemental Information
|
<This test is not yet implemented in the MESA tools.>
Test Case 3720 involves transactions for the patient GOLDENROD^G for the Unscheduled Import Option in the IRWF profile. If you import scanned film or documents, you should run test 3721 instead.
Importers will query the Patient Demographics Supplier, import a DICOM study from portable media, or via the network, coerce attributes as required, and store the resulting DICOM objects to the Image Manager, with associated PPS messages. Storage Commitment is covered in a different test.
In this test, the Patient ID (3720) and Date of Birth received in the query response differs from that in the DICOM objects imported from portable media.
RAD TF-1: 21.3.1.3 and RAD TF-2: Appendix A.2
To run this test, follow these steps:
perl scripts/imp_irw.pl 3720
To evaluate this test run:
perl 3720/eval_3720.pl <log> <IMP AE title>
Test Case 3721: Importer (digitizer) Coerces Attributes – Unscheduled Import Option<This test is not yet implemented in the MESA tools.> Test Case 3721 involves transactions for the patient YELLOW^Y for the Unscheduled Import Option in the IRWF profile. If you import from DICOM objects, eg from portable media such as CD or via the network, you should run test 3720 instead. ReferencesRAD TF-1: 21.3.1.3 and RAD TF-2: Appendix A.2 InstructionsTo run this test, follow these steps:
perl scripts/imp_irw.pl 3721 EvaluationTo evaluate this test run: perl 3721/eval_3721.pl <log> <IMP AE title> Supplemental Information |
Test Case 3725 involves transactions for the patient VIOLET^V for the Scheduled Import Option in the IRWF profile. If you import scanned film or documents, you should run test 3726 instead.
Importers will query for modality worklist, import a DICOM study from portable media or via the network, coerce attributes as required, and store the resulting DICOM objects to the Image Manager, with associated PPS messages. Storage Commitment is covered in a different test.
In this test, the Patient ID (3725) and Date of Birth received in the MWL differ from that in the DICOM objects imported from portable media. That is part of the test; use the data from the MWL entry to coerce the data from the CD.
The test steps below reference the ISO image of the IRWF-FUSION-2006 CD. This CD is located with the MESA software distribution. It contains more than one study (and is therefore a good test of your ability to import selected data from a CD).
RAD TF-1:21.3.1.2
RAD TF-1:Appendix A.2
Test description/steps for test 3725.
To run this test, follow these steps:
perl scripts/imp_irw.pl 3725 <log_level>
To evaluate this test run:
perl 3725/eval_3725.pl <log_level: 1-4> <AE title of your MPPS SCU>
If you are a digitizer, you will not run this test, but you will be required to run test 3726. If you do not run this test, create a file with a message that indicates you are a digitizer which will run test 3726 and submit that file as the results for test 3725.
Test Case 3726: Importer (digitizer) Coerces Attributes – Scheduled Import OptionTest Case 3726 involves transactions for the patient LAVENDER^L for the Scheduled Import Option in the IRWF profile. If you import DICOM objects, eg from portable media such as CD, or via the network you should run test 3725 instead. For this test, you should assume: Importers will query for modality worklist, scan a film or document, coerce the attributes as required, and store the resulting DICOM objects to the Image Manager, with associated PPS messages. Storage Commitment is covered in another test. ReferencesRAD TF-1: 21.3.1.2 and RAD TF-2: Appendix A.2 InstructionsTo run this test, follow these steps:
perl scripts/imp_irw.pl 3726 <log_level> EvaluationTo evaluate this test run: perl 3726/eval_3726.pl <log_level: 1-4> <AE title of your MPPS SCU> Supplemental InformationIf you are a an Importer which imports via the network or portable media, you will not run this test, but you will be required to run test 3725. If you do not run this test, create a file with a message that indicates you are not a digitize, so will run test 3725, and submit that file as the results for test 3726. |
<This test is not yet implemented in the MESA tools.>
This tests the behavior of the Importer when the operator abandons the import after storing one object to the Image Manager, and then discontinues the PPS. This test is for Importers which support the Unscheduled Import Option.
RAD TF-2: 21.3.2
RAD TF-3: 4.60.4.1.2.2
To run this test, follow these steps:
perl scripts/imp_irw.pl 3739 <log_level>
To evaluate this test run:
perl 3739/eval_3739.pl <log_level: 1-4> <AE title of your MPPS SCU>
Test Case 3740: PPS Exception Management – abandoned import - scheduledThis tests the behavior of the Importer when the operator abandons the import after storing one object to the Image Manager, and then discontinues the PPS. This test is for Importers which support the Scheduled Import Option. If you support the Unscheduled Import Option, you should run test 3739 instead. ReferencesRAD TF-2: 21.3.2 Test description/steps for test 3740. InstructionsTo run this test, follow these steps:
perl scripts/imp_irw.pl 3740 <log_level> EvaluationTo evaluate this test run: perl 3740/eval_3740.pl <log_level: 1-4> <AE title of your MPPS SCU> Supplemental Information |
<This test is not yet implemented in the MESA tools.>
This tests the behavior of the Importer when the operator realizes, after storing one object to the Image Manager, that the wrong patient was selected from the list received from the Patient Demographic Supplier. After the PPS is discontinued, the Importer selects the correct patient, reconciles the imported objects and stores them to the Image Manager. This test is for Importers which support the Unscheduled Import Option.
RAD TF-2: 21.3.2
RAD TF-3: 4.60.4.1.2.2
To run this test, follow these steps:
perl scripts/imp_irw.pl 3741 <log_level>
To evaluate this test run:
perl 3741/eval_3741.pl <log_level: 1-4> <AE title of your MPPS SCU>
Test Case 3742: PPS Exception Management – incorrect worklist item - scheduledThis tests the behavior of the Importer when the operator realizes, after storing one object to the Image Manager, that the wrong item was selected from the worklist received from the DSS/OF. After the PPS is discontinued, the Importer re-queries the DSS/OF, reconciles the imported objects and stores them to the Image Manager. This test is for Importers which support the Scheduled Import Option. ReferencesRAD TF-2: 21.3.2 Test description/steps for test 3742. InstructionsTo run this test, follow these steps:
perl scripts/imp_irw.pl 3742 <log_level> EvaluationTo evaluate this test run: perl 3742/eval_3742.pl <log_level: 1-4> <AE title of your MPPS SCU> Supplemental Information |
<This test is not yet implemented in the MESA tools.>
This tests the Importer behavior when the Image Manager fails to store the objects which were imported (ie receives a non-zero (not success) status in response to the C-STORE).
Test Case 3745: Billing and Material Management Option - unscheduled<This test is not yet implemented in the MESA tools.> This is derived from Test Case 218 for Acquisition Modalitites. Test 3745 exercises the Billing and Material Management Option for Importer actors. With this option, a importer actor must provide the Billing Supplies and Devices Sequence in the MPPS message, as specified in RAD TF-3: Table 4.60-2. This test is for Importers which support the Unscheduled Import Option. ReferencesRAD TF-3: 4.60.4.1.2.3 Instructions
0040 0324 Billing Supplies and Devices Sequence
EvaluationTo evaluate your MPPS messages: perl 3476/eval_3476.pl <log_level: 1-4> <AE title of your MPPS SCU> Supplemental Information |
<This test is not yet implemented in the MESA tools.>
This is derived from Test Case 218 for Acquisition Modalitites.
Test 3746 exercises the Billing and Material Management Option for Importer actors. With this option, a importer actor must provide the Billing Supplies and Devices Sequence in the MPPS message, as specified in RAD TF-3: Table 4.60-2. This test is for Importers which support the Scheduled Import Option.
RAD TF-3: 4.60.4.1.2.3
0040 0324 Billing Supplies and Devices Sequence
Attribute Name |
Tag |
Value |
Billing Procedure Step Seque |
(0040,0320) |
|
> Code Value |
(0008,0100) |
BP1001 |
> Coding Scheme Designator |
(0008,0102) |
IHEDEMO |
>Code Meaning |
(0008,0104) |
Billing Procedure 1001 |
Billing Supplies and Devices Sequence |
(0040,0324) |
|
> Billing Item Sequence |
(0040,0296) |
|
>> Code Value |
(0008,0100) |
These values are still TBD from DICOM |
>> Coding Scheme Designator |
(0008,0102) |
DCM |
>> Code Meaning |
(0008,0104) |
See valudes in RAD TF-3: Table 4.60-3. |
>Quantity Sequence |
(0040,0293) |
|
>>Quantity |
(0040,0294) |
1 |
To evaluate your MPPS messages:
perl 3476/eval_3476.pl <log level> <AE Title MPPS SCU>
Test Case 3750: Instance Availability Notification upon ImportReferencesInstructions<This test is not yet implemented in the MESA tools.> EvaluationSupplemental Information |