MESA/Image Manager

The test definitions on this page are RETIRED, but are kept here, for now, as an archive.

Image Manager/Archive Tests

Introduction

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. Image Manager/Archives (heareafter referred to as Image Managers) 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 Image Manager, 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/imgmgr or $MESA_TARGET/mesa_tests/card/actors/imgmgr . 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 Image Archive/Image Manager 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

Image Managers are required to forward MPPS messages to the MESA Order Filler, accept images for storage, respond to Storage Commitment reqeusts, respond to DICOM C-Find commands and respond to DICOM C-Move requests. The tables below list the attributes evaluated by the MESA software for various tests.

Attributes Evaluated for MPPS Messages Forwarded by Image Manager

Attribute Name	Tag
Performed Procedure Step Relationship
Scheduled Step Attribute Sequence	0040 0270
>Study Instance UID	0020 000D
>Referenced Study Sequence	0008 1110
>> Referenced SOP Class UID	0008 1150
0008 1150	0008 1155
>Accession Number	0008 0050
>Requested Procedure ID	0040 1001
>Requested Procedure Description	0032 1060
>Scheduled Procedure Step ID	0040 0009
>Scheduled Procedure Step Description	0040 0007
> Scheduled Action Item Code Sequence	0040 0008
>>Code Value	0008 0100
>>Coding Scheme Designator	0008 0102
>>Code Meaning	0008 0104
Patient’s Name	0010 0010
Patient ID	0010 0020
Patient’s Birth Date	0010 0030
Patient’s Sex	0010 0040
Performed Procedure Step Information
Performed Procedure Step ID	0040 0253
Performed Station AE Title	0040 0241
Performed Station Name	0040 0242
Performed Location	0040 0243
Performed Procedure Step Start Date	0040 0244
Performed Procedure Step Status	0040 0252
Performed Porcedure Step Description	0040 0254
Performed Procedure Type Description	0040 0255
Procedure Code Sequence	0008 1032
>Code Value	0008 0100
>Coding Scheme Designator	0008 0102
>Code Meaning	0008 0104
Performed Procedure Step End Date	0040 0250
Performed Procedure Step End Time	0040 0251
Image Acquissition Results
Modality	0008 0060
Study Id	0020 0010
Performed Action Item Code Sequence	0040 0260
>Code Value	0008 0100
>Coding Scheme Designator	0008 0102
>Code Meaning	0008 0104
Performed Series Sequence	0040 0340
>Performing Physician’s Name	0008 1050
>Protocol Name	0018 1030
>Operator’s Name	0008 1070
>Series Instance UID	0020 000E
>Series Description	0008 103E
>Retrieve AE Title	0008 0054
>Referenced Image Sequence	0008 1140
>>Referenced SOP Class UID	0008 1150
>>Referenced SOP Instance UID	0008 1155
>Referenced Standalone SOP Instance Sequence	0040 0220
>>Referenced SOP Class UID	0008 1150
>>Referenced SOP Instance UID	0008 1150

Attributes Evaluated in C-Find Responses

Attribute Name	Tag
Study Level
Study Date	0008 0020
Study Time	0008 0030
Accession Number	0008 0050
Patient Name	0010 0010
Patient ID	0010 0020
Study ID	0020 0010
Study Instance UID	0020 000D
Modalities in Study	0008 0061
Referring Physician’s Name	0008 0090
Patient’s Birth Date	0010 0030
Patient’s Sex	0010 0040
Number of Study Related Series	0020 1206
Number of Study Related Instances	0020 1208
Series Level
Modality	0008 0060
Series Number	0020 0011
Series Instance UID	0020 000E
Number of Series Related Instances	0020 1209
Request Attribute Sequence	0040 0275
>Requested Procedure ID	0040 1001
>Scheduled Procedure Step ID	0040 0009
Performed Procedure Step Start Date	0040 0244
Performed Procedure Step Start Time	0040 0245
Composite Object Instance Level
Image Number	0020 0013
SOP Instance UID	0008 0018
SOP Class UID	0008 0016
Image Specific Attributes
Rows	0028 0010
Columns	0028 0011
Bits Allocated	0028 0100
Number of Frames	0028 0008
Presentation State Specific Attributes
Presentation Label	0070 0080
Presentation Description	0070 0081
Presentation Creation Date	0070 0082
Presentation Creation Time	0070 0083
Presentation Creator’s Name	0070 0084
Referenced Series Sequence	0008 1115
>Series Instance UID	0020 000E
>Referenced Image Sequence	0008 1140
>>Referenced SOP Class UID	0008 1150
>>Referenced SOP Instance UID	0008 1155

Attributes Evaluated in SOP Instances Retrieved via C-Move

Attribute Name	Tag
Study Level
Study Date	0008 0020
Study Time	0008 0030

Message Values

These tests expect the Image Manager to reproduce values that were sent to the Image Manager via DICOM or HL7 messages. There is no documentation which lists all expected values; there would be too many values to document. The evaluation software will print the expected values and the values supplied by the Image Manager in the event of mismatches (or always if you use the verbose mode).

Configuration

The Image Manager scripts described below use an ASCII configuration file to identify parameters such as host names and port numbers. The configuration file is named imgmgr_test.cfg and is included in the directory $MESA_TARGET/mesa_tests/rad/actors/imgmgr. Edit the file and change entries (host name, port number) that 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 imgmgr_secure.cfg. This separate file allows you to use different port numbers for your 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. The table below gives parameters for MESA servers that will receive messages from your system. Other MESA servers are started and exchange messages, but do not receive messages from the Image Manager.

Attribute	AE Title	Port Number
MESA MPPS Manager and MWL Server	MESA_FILLER	2250
MESA Modality (for Storage Commitment)	MESA_MOD	2400
MESA Workstation (to receive SOP instances as the result of C-Move requests)	MESA_WKSTATION	3001
MESA Audit Record Repository	<none>	4000

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 Image Manager exam directory: $MESA_TARGET/mesa_tests/rad/actors/imgmgr or $MESA_TARGET/mesa_tests/card/actors/imgmgr

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

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/stop_mesa_servers.pl

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.

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 Image Manager exam directory: $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

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

Workflow tests (1xx series) use a test engine that manages the test process. This test engine is used for all 1xx series tests and is driven by a text file that describes the events for a specific test. Each test below will indicate which script is appropriate (usually the swf script for Scheduled Workflow). 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 131 test is:

    perl  scripts/imgmgr_swf.pl 131 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/eval_131.pl 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.

Image Manager 1xx Tests

Each section below lists one Image Manager test. As mentioned above, the individual transactions involving the Image Manager under test are described in other documents. In some cases, the MESA software will send a message to your Image Manager and will have no way to evaluate the response of your system. These messages must be accepted by your system, but are not listed in the sections below as being evaluated by the MESA software.

Image Manager Test 103: PIR Case 1: Unidentified Patient Registered at ADT and Ordered at the Order Placer

Test Case 103 involves transactions for the patient Jay Silverheels and tests the Unidentified Case 1: Unidentified Patient Registered at ADT and Ordered at the Order Placer.

References

RAD TF-1:4.4.

Instructions

The nominal patient name is SILVERHEELS^JAY. To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Run the test script as follows:

   perl  scripts/imgmgr_swf.pl 103 <log>

4. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl  103/eval_103.pl <log> <MPPS AE Title> <SC AE Title>

2. The evaluation output is found in 103/mir_mesa_103.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

Image Managers are expected to send Storage Commitment N-Event reports to the MESA modality using a different Association than that initiated by the MESA modality (for the N-Action). Please refer to the configuration tables above for the DICOM configuration for the MESA modality.

To change patient name, patient ID prior to the test:

   cd  $MESA_TARGET/mesa_tests/rad/msgs
   perl  mesa_reset/103.pl ihe-us/103.var 

(or)

   perl  mesa_reset/103.pl

Image Manager Test 105: PIR Case #3: Unidentified Patient Registered at ADT but Completed at Modality Prior to Order

Test Case 105 involves transactions for the patient Stephen Mustard and tests the Unidentified Case 3: Unidentified Patient Registered at ADT but Completed at Modality Prior to Order. Note that the Study Instance UID is generated by the Modality.

References

RAD TF-1:4.4.3

Instructions

The nominal patient name is MUSTARD^STEPHEN. To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr'.

2. Make sure the MESA servers have been started as described in [Starting the MESA Servers] above.

3. Run the test script as follows:

   perl scripts/imgmgr_swf.pl 105 <log>

4. Run the evaluation script below.

Evaluation

1. Run the evaluation script

    perl  105/eval_105.pl <log> <MPPS AE Title> <SC AE Title>

2. The evaluation output is found in 105/mir_mesa_105.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

To change patient name, patient ID prior to the test:

   cd  $MESA_TARGET/mesa_tests/rad/msgs
   perl  mesa_reset/105.pl ihe-us/105.var  (or)
   >perl  mesa_reset/105.pl

Image Manager Test 106: Green

This test is different from the other 1xx series tests. This is a test of the Presentation of Grouped Procedures Integration Profile. Your system will accept HL7 scheduling messages for two Requested Procedures, one series of images (IHE Group Case) and two separate GSPS objects. After you have received these messages, you perform these steps:

References

Instructions

1. Display the images for the separate procedures using the appropriate GSPS objects.

2. Perform a screen capture (electronic, camera) of your display system that indicates you can display information to indicate that these are grouped procedures but that you can split them according to the GSPS objects.

3. Send the screen capture (electronic, paper) to the Technical Project Manager.

Step 2 is intentionally vague. We do not want to evaluate the quality of your user interface or display. We do want to see if you support the splitting of these groups according to this Integration Profile. It is difficult for us to give guidelines for how to prove this. “We will know it when we see it.”

To run this test, follow these steps:

   perl  106/106_imgmgr.pl

After the message exchange is complete, perform appropriate screen captures and send results to the Project Manager.

Evaluation

Supplemental Information

Image Manager Test 108: PGP Test Data

In this test, Image Manager/Image Displays will examine the sample PGP data provided by other participants. The goal of the test is to make sure the Image Manager actors are not surprised by content when they arrive at a Connectathon.

References

Instructions

1. Find sample images uploaded by other vendors for test 108 in gazelle under Connectathon -> List of samples.... This page will evolve as vendors add samples, so be patient.
2. Retrieve the files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. Create a txt file that indicates which samples you tested with and whether or not you were successful. Upload that file as the results for this test
4. If you find issues with the samples, send an email to the Connectathon Manager now to wake him or her up. You can also contact the image provider directly to resolve issues.
5. The goal is no surprises.

Evaluation

The evaluation of this test is performed by examining the spreadsheet you provided to make sure you made a good faith effort to review the sample images.

Supplemental Information

Image Manager Test 109: Exception Management

The Exception Management test uses a typical sequence of messages for the Scheduled Workflow profile. The final MPPS N-Set message sets the procedure step status to DISCONTINUED and includes the reason code:

         110514, Incorrect worklist entry selected

According to the IHE Technical Framework, RAD-TF-2: 4.7.4.1.3.1, the Image Manager shall

• not return SOP Instances UIDs for the images in query responses

In this test, the Image Manager should receive and recognize the reason code. The MESA tools send a C-Find request at the IMAGE level for the discontinued procedure step. The Image Manager under test should return 0 responses. It is considered a failure if the Image Manager returns responses to this C-Find request.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Run the test script as follows:

   perl scripts/imgmgr_swf.pl 109 <log> <MPPS AE Title> <SC AE  Title>

4. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl 109/eval_109.pl <log>

2. The evaluation output is found in 109/mir_mesa_109.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

To change patient name, patient ID prior to the test:

   cd  $MESA_TARGET/mesa_tests/rad/msgs
   perl  mesa_reset/109.pl ihe-us/109.var (or)
   perl  mesa_reset/109.pl

Image Manager Test 111: Performed Work Status Update

Test 111 covers the Performed Work Status Update under the assumption that the Image Manager wants to receive this status from the Order Filler. Read the list of transactions that are listed in IHE Tests: Transaction Sequences.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Run the test script as follows:

   perl  scripts/imgmgr_swf.pl 111 <log>

4. Run the evaluation script below.

Evaluation

You will receive these status messages and do not need to produce them. There is no formal evaluation. Submit a file to the Project Manager indicating that you have received the messages properly.

Supplemental Information

To change patient name, patient ID prior to the test:

   cd  $MESA_TARGET/mesa_tests/rad/msgs
   perl  mesa_reset/111.pl ihe-us/111.var (or)
   perl mesa_reset/111.pl

Image Manager Test 131: Administrative and Procedure Performance Process Flow

Test 131 covers Administrative and Procedure Performance Process Flow in the Scheduled Workflow profile.

References

RAD TF-1:3.3.3

Instructions

The nominal patient name is BLACK^CHARLES. To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Run the test script as follows:

   perl  scripts/imgmgr_swf.pl 131 <log>

4. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl 131/eval_131.pl <log> <MPPS AE  Title> <SC AE Title> 

2. The evaluation output is found in 131/mir_mesa_131.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

To change patient name, patient ID prior to the test:

   cd  $MESA_TARGET/mesa_tests/rad/msgs
   perl  mesa_reset/131.pl ihe-us/131.var (or)
   perl  mesa_reset/131.pl

Image Manager Test 132: Order Change Flow Initiated by Order Filler

Test 132 covers order change flow initiated by the Order Filler in the Scheduled Workflow profile.

References

RAD TF-1:3.2.4).

Instructions

The nominal patient name is WISTERIA^MATTHEW. To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Run the test script as follows:

   perl scripts/imgmgr_swf.pl 132<log>

4. Run the evaluation script below.

Evaluation

There is no evaluation script for Image Manager Test 132. If you are preparing for a Connectathon, make sure your system can complete the transactions in this text. Then, submit a text file that indicates you have completed Image Manager Test 132. This is a one line statement. Nothing more elaborate is required.

Supplemental Information

To change patient name, patient ID prior to the test:

   cd  $MESA_TARGET/mesa_tests/rad/msgs
   perl  mesa_reset/132.pl ihe-us/132.var (or)
   perl  mesa_reset/132.pl

Image Manager Test 133: PIR Case 2: Unidentified Patient Registered at ADT and Ordered at Department System Scheduler/Order Filler

Test Case 133 involves transactions for the patient Ivan Indigo and tests the Unidentified Case 2: Unidentified Patient Registered at ADT and Ordered at the DSS/Order Filler.

References

RAD TF-1:4.4.2

Instructions

The nominal patient name is INDGO^IVAN. To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Run the test script as follows:

   perl  scripts/imgmgr_swf.pl 133 <log> 

4. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl  133/eval_133.pl <log> <MPPS AE Title> <SC AE Title>

2. The evaluation output is found in 133/mir_mesa_133.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

To change patient name, patient ID prior to the test:

   cd  $MESA_TARGET/mesa_tests/rad/msgs
   perl  mesa_reset/133.pl ihe-us/133.var (or)
   perl  mesa_reset/133.pl

Image Manager Test 134: Instance Availability Notification

Test 134 covers Image Manager/Image Archive notifies interested workflow actors about the availability status of instances at specified storage locations.

References Instructions

The nominal patient name is BLACK^CHARLES. To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr. 2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Run the test script as follows:

   perl  scripts/imgmgr_swf.pl 134 <log>

4. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl 134/eval_134.pl <log> <IM/IA AE  Title>

2. The evaluation output is found in 134/mir_mesa_134.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

To change patient name, patient ID prior to the test:

   cd  $MESA_TARGET/mesa_tests/rad/msgs
   perl  mesa_reset/134.pl ihe-us/134.var (or)
   perl  mesa_reset/134.pl

Other Tests

The tests described in this section test other features of Image Managers that are important for System Integration but are not covered in the Workflow Tests in the previous section. Each test will have separate and specific instructions.

All tests use a set of queries that must be constructed in a one-time step. Run the script scripts/construct_queries.pl (perl scripts/construct_queries.pl). This will construct C-Find queries to be used in later steps.

Test 281: Example Images and other DICOM objects

July-2016 - This test description has been replace by https://gazelle.ihe.net/content/evsdicomobjectevaluation

In this test, Image Managers will examine the DICOM samples provided by other participants. The goal of the test is to make sure the Image Manager actors are not surprised by content when they arrive at a Connectathon.

References

Instructions

1. Find sample images uploaded by other vendors for test 281 in gazelle under Connectathon -> List of samples.... On the "Samples available for rendering tab" you will find DICOM_OBJECTS submitted by other vendors. This page will evolve as vendors add samples, so be patient.
2. Retrieve the files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
3. Create a text file that lists the samples you tested with and any problems you encountered. Upload that as the results for this test.
4. If you find issues with the images, send an email to the Connectathon Technical Manager.
5. The goal is no surprises.

Evaluation

The evaluation of this test is performed by examining the text file you provided to make sure you made a good faith effort to review the sample images. If you find a problem with some samples, we will share your feedback with your Modality test partners.

Image Manager Test 401: Modalities in Study

The DICOM attribute 0008 0061 is named “Modalities in Study”. Image Managers are required to support this as both a query and return key at the Study Level. In this test, we will send studies with one modality and two modalities to your Image Manager and then query the Image Manager for results.

References

Instructions

1.Start the MESA servers as instructed in [Starting the MESA Servers].

2. Clear your Image Manager of all images.

3. Run the script scripts/clearMESA.pl

   (perl  scripts/clearMESA.pl)

to clear the MESA image manager of all images.

4. Run the script 40x/load_img_mgr.pl

    (perl 40x/load_img_mgr.pl)

This will send 6 studies to your Image Manager with the following values for Modality (MR, MR & CT, CT, CR, OT, OT). If your Image Manager does not support GSPS objects, use the script 40x/load_img_mgr_images_only.pl.

5. Run the script 401/401_imgmgr.pl :

   (perl  401/401_imgmgr.pl)

This runs 6 different queries against your Image Manager. Query A requests the 0008 0061 attribute for all studies in your Image Manager. You should see the 6 studies mentioned above and the values mentioned above. Your system might transpose the MR\CT value to CT\MR. Query B queries for all studies with MR images. This should generate two responses. Query C queries for all studies with CT images. This should generate two responses. Query D queries for all studies with CR images. This should generate one response. Query E queries for all studies with US images. This should generate no responses.

6. Query F queries for modalities: MR\CT. This is an illegal query just for your own testing. Clients should not send you this query. The evaluation scripts do not test your response to this query, so you are free to ignore this query. We may be incorrect in stating this is an illegal query. It requires some research. The evaluation scripts do not examine this response as of the 6.11.0 release.

Evaluation

Run the script 401/eval_401.pl. This will evaluate the performance of the above queries and will indicate pass/fail.

Supplemental Information

Image Manager Test 402: Related Series/SOP Instances

These tests query Image Managers for DICOM attributes such as Number of Study Related Series, Number of Study Related SOP Instances. This test uses the same sites as test 401 but with different queries.

References

Instructions

1. Clear your Image Manager of all images.

2. Run the script 40x/load_img_mgr.pl. This will send 6 studies to your Image Manager.

3. Run the script 402/402_imgmgr.pl. This sends two queries to your Image Manager. The first queries for Number of Study Related Series and Number of Study Related Instances. The second queries one study for Number of Series Related Instances.

4. For extra credit, run the 40x/load_img_mgr.pl script again. This will send the images to you a second time. Run the query scripts again. The counts should remain the same.

Evaluation

Run the script 402/eval_402.pl. This will evaluate the performance of the 402 queries and indicate pass/fail.

Supplemental Information

Image Manager Test 403: Other Image Manager Attribute

This test is not yet defined.

Image Manager Test 404: Image Specific Queries

The Image Specific Queries tests transmit DICOM C-Find commands to Image Managers with return keys that are specific to Image SOP Instances. The test reuses the images loaded into your system for the other 40x tests. The table below lists the attributes requested in the queries.

0008 0016	SOP Class UID
0028 0010	Rows
0028 0011	Columns
0028 0100	Bits Allocated
0028 0008	Number of Frames

References

Instructions

1. Clear your Image Manager of all images.

2. Run the script 40x/load_img_mgr.pl. This will send 6 studies to your Image Manager.

3. Run the script 404/404_imgmgr.pl. Two queries are sent, one each for a series in two different studies.

Evaluation

Run the script 404/eval_404.pl. This will evaluate the performance of the 404 queries and indicate pass/fail.

Supplemental Information

Image Manager Test 405: Storage Commitment

The Storage Commitment tests use different images from the 40x series tests. Images are sent to your Image Manager and storage commitment requests are made. You are expected to send the Storage Commitment N-Event reports to the MESA modality at port 2400.

References

Instructions

1. Run the script 405/produce_images.pl. This produces test images.

2. Run the script scripts/clearMESA.pl. This clears the MESA system of test data and responses from your Image Manager.

3. Start the MESA servers as instructed in Starting the MESA Servers.

4. Clear your image manager.

5. Run the script 405/405_imgmgr.pl. This will run the 405 test and indicate pass/fail. This script runs an application that acts as an SCU of the Storage Commitment Push Model SOP Class and requests associations with different association negotiation parameters. It makes one proper request that your application should accept and one improper request that your application should reject. The script will indicate pass/fail. An optional –v argument will enable verbose mode:

   perl  405/405_imgmgr.pl [-v]

6. Run the script 405/load_img_mgr.pl. This will send test images for four studies to your Image Manager.

7. Run the script 405/c405a.pl. This sends storage commitment requests to your Image Manager for two studies.

If you need to repeat this test, stop the MESA servers then restart at step 2.

Evaluation

Run the script 405/e405a.pl. This evaluates the Storage Commitment N-Event reports that you sent to the MESA modality (on a separate association). One required argument is the AE title of your Storage Commitment SCP when it initiates DICOM associations to send the N-Event reports. An optional –v argument will enable verbose mode:

   perl 405/e405a.pl <AE Title> [-v]

Supplemental Information

Image Manager Test 411: Presentation State Query

Images and related Presentation State objects are sent to the Image Manager under test. We query the Image Manager for attributes specific to Presentation State objects and test other query/retrieve features. These images are different from those used in the 40x series of tests.

References

Instructions

1. Run the script 40x/load_img_mgr.pl. This will send studies to your Image Manager that include Presentation State objects. (Yes, use the 40x/load_img_mgr.pl script).

2. Run the script 411/411_imgmgr.pl. This will query for presentation state specific attributes from the studies sent to your Image Manager.

Evaluation

Run the script 411/eval_411.pl. This will evaluate the responses and indicate pass/fail.

Supplemental Information

Image Manager Test 412: Presentation State Retrieve

The Image Manager is sent C-Move requests to retrieve studies that contain Presentation State objects. The Image Manager should correctly send both images and Presentation State objects to the server. In the 412 tests, the Image Manager will be sent C-Move requests with a destination AE title of WORKSTATION1. The MESA tools use these settings for that application:

AE Title	Workstation 1
Port	3001
Host	The MESA test system

References

Instructions

1. Start the MESA servers as indicated in Starting the MESA Servers.

2. Run the script 40x/load_img_mgr.pl. This will send studies to your Image Manager that include Presentation State objects.

3. Run the script 412/412_imgmgr.pl. This will clear the MESA workstation and send C-Move requests to move images and presentation state objects to the MESA workstation server.

Evaluation

Run the script 412/eval_412.pl. This will evaluate the objects retrieved from your Image Manager and indicate pass/fail.

Supplemental Information

Image Manager Test 413: Key Object Note Query

The Key Object Note Query test transmits one DICOM C-Find command to Image Managers with return keys that are specific to Key Image Note SOP Instances. The test uses the Key Object Notes loaded into your system for the other 41x tests. The table below lists the attributes requested in the queries.

0008 0023	Content Date
0008 0033	Content Time
0040 A032	Observation DateTime
0040 A043	Concept Name Code Sequence

References

Instructions

1. Start the MESA servers as described in Starting the MESA Servers above.

2. Clear your Image Manager of all images.

3. Run the script 41x/load_img_mgr.pl. This will send studies to your Image Manager containing Key Object Notes.

4. Run the script 413/413_imgmgr.pl. One query is sent for a Key Object Note.

Evaluation

Run the script 413/eval_413.pl. This will evaluate the performance of the 413 query.

Supplemental Information

Image Manager Test 414: Key Object Note Retrieve

The Image Manager is sent C-Move requests to retrieve studies that contain Key Object Notes. In the 414 tests, the Image Manager will be sent C-Move requests with a destination AE title of WORKSTATION1. The MESA tools use these settings for that application:

AE Title	Workstation 1
Port	3001
Host	The MESA test system

References

Instructions

1. Start the MESA servers as described in Starting the MESA Servers above.

2. Run the script 41x/load_img_mgr.pl. This will send studies to your Image Manager containing Key Object Notes.

   perl 41x/load_img_mgr.pl

3. Run the script to send C-Move requests to your system:

   perl  414/414_imgmgr.pl

Evaluation

Run the script 414/evaluate_414.pl. This will evaluate the Key Object Note retrieved in the last step:

   perl  414/eval_414.pl

Supplemental Information

Post Processing Tests

Image Manager Test 1402: Store Evidence Documents

The Store Evidence Document test uses C-Store to transmit Evidence Documents to Image Managers. Subsequent 140x tests will use these Evidence Document SOP Instances.

References

Instructions

1. Start the MESA servers as described in Starting the MESA Servers above.

2. Clear your Image Manager of all images.

3. Run the script 1402/load_img_mgr.pl. This will send documents to your Image Manager.

Evaluation

There is no evaluation script for this test. Successful completion of this test is prerequisite for completion of the remaining 140x tests.

Supplemental Information

Image Manager Test 1403: Query Evidence Documents

The Evidence Document Query test transmits one DICOM C-Find command to Image Managers with return keys that are specific to Evidence Document SOP Instances. The test uses the Evidence Documents loaded into your system in the 1402 test. The table below lists the attributes requested in the IMAGE level query.

0008 0023	Content Date
0008 0033	Content Time
0040 A370	Reference Request Sequence
0020 000D	>Study Instance UID
0008 0050	>Accession Number
0040 1000	>Requested Procedure ID
0032 1064	>Requested Procedure Code Sequence
0008 0100	>>Code Value
0008 0102	>>Coding Scheme Designator
0008 0103	>>Coding Scheme Version
0008 0104	>>Code Meaning
0040 A504	Content Template Sequence
0040 DB00	>Template Identifier
0040 A043	Concept Name Code Sequence
0008 0100	>Code Value
0008 0102	>Coding Scheme Designator
0008 0103	>Coding Scheme Version
0008 0104	>Code Meaning

References

Instructions

1. The MESA servers should be running from test 1402.

2. Your Image Manager should contain the documents sent to it in test 1402.

3. Run the script 1403/1403_imgmgr.pl. One query is sent for Evidence Documents.

Evaluation

Run the script 1403/eval_1403.pl. This will evaluate the performance of the 1403 query.

Supplemental Information

Image Manager Test 1404: Retrieve Evidence Documents

The Image Manager is sent C-Move requests to retrieve studies that contain Evidence Documents. In the 414 tests, the Image Manager will be sent C-Move requests with a destination AE title of WORKSTATION1. The MESA tools use these settings for that application:

AE Title	Workstation 1
Port	3001
Host	The MESA test system

References

Instructions

1. The MESA servers should be running from test 1402.

2. Your Image Manager should contain Evidence Documents sent in test 1402.

3. Run the script to send C-Move requests to your system:

   perl  1404/1404_imgmgr.pl

Evaluation

Run the script 1404/evaluate_1404.pl. This will evaluate the Evidence Document retrieved in the last step:

   perl 1404/evaluate_1404

Supplemental Information

Image Manager Test 1412: PWF CT

Test 1412 is a test of the steps for Post Processing Workflow in a CT 3D reconstruction scenario. The Image Manager will participate in Scheduled Workflow steps for the scheduling of one procedure step for a CT case and for the creation of the appropriate images and MPPS objects. Once the images and MPPS objects for that procedure step are completed, you will be asked to schedule a post processing step and to participate in the post processing workflow.

References

Instructions

1. Run the test script:

   perl 1412/1412_imgmgr_active.pl

Evaluation

Run the evaluation script:

   perl 1412/eval_1412.pl

The evaluation script should yield 0 errors.

Supplemental Information

Image Manager Test 1421: PWF Double Claim

This sequence of messages tests the response of the Post Processing Manager to consecutive claims of a single workitem. This is to simulate a situation where two Image Creators are querying for the same set of workitems. This test first uses the 142x script to do the scheduled workflow to schedule a CT 3D reconstruction post processing workitem. The 1421 script will then attempt to claim this workitem twice. Your system should accept the first claim and reject the second claim.

References

Instructions

1. Run the active manager test script:

   perl  142x/142x_imgmgr.pl

2. Follow the test instructions

3. Run the active manager test script:

   perl 1421/1421_imgmgr_active.pl

Evaluation

Run the evaluation script:

   perl 1421/eval_1421.pl

The evaluation script should yield 0 errors.

Supplemental Information

Image Manager Test 1422: PWF Release Claim

This sequence of messages tests the response of the Post Processing Manager to a request to release a claim. That is, a MESA Image Creator will claim a workitem from the PPM worklist, then release the workitem without completing it, and then query a second time to determine if the workitem is again available. This test relies on the use of Test 1421 to set up a workitem in progress. Please run Test 1421 immediately prior to running this test.

References

Instructions

1. Run the test script:

   perl 1422/1422_imgmgr_active.pl

Evaluation

Run the evaluation script:

   perl 1422/eval_1422.p

The evaluation script should yield 0 errors.

Supplemental Information

Basic Security Tests

This section describes tests that are specific to the IHE Basic Security integration profile. If you have the MESA servers running for the “standard” tests, you should stop those servers now. You will need to start the MESA secure servers with a different script.

Image Manager Test 1502: Pre-reg/Order Cancel/Reorder

This test is obsolete; do not perform this test.

Image Manager Test 1502 uses the same sequence of events as test 102 with some added DICOM C-Find requests. The Image Manager is expected to communicate with other systems using TLS negotiation and to send appropriate audit messages to the MESA syslog server. The MESA software sends one DICOM C-Find query to the Image Manager. This should trigger at least one message to the Audit Record Repository. You might trigger other messages to the Audit Record Repository based on your interaction with your Image Manager.

References

Instructions

1. Start the secure MESA servers as instructed in [Starting the MESA Servers].

2. Clear your Image Manager of all images.

3. Run the test script:

   perl 1502/1502_imgmgr.pl

This script will send messages to your system and prompt you along the way. You are expected to send audit messages in response to certain events (such as DICOM C-Find requests).

Evaluation

1. Run the evaluation script:

   perl 1502/eval_1502.pl <AE Title MPPS Mgr>

2. The evaluation output is found in 1502/mir_mesa_1502.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

3. Grab all of the files (tar/zip) in $MESA_TARGET/logs/syslog and send these to the Project Manager.

Supplemental Information

Image Manager Test 1503: Unidentified Patient Case #1

This test is obsolete; do not perform this test.

Image Manager Test 1503 uses the same sequence of events as test 103 The Image Manager is expected to communicate with other systems using TLS negotiation and to send appropriate audit messages to the MESA syslog server. The MESA software sends one DICOM C-Find query to the Image Manager. This should trigger at least one message to the Audit Record Repository. You might trigger other messages to the Audit Record Repository based on your interaction with your Image Manager.

References

Instructions

1. Start the secure MESA servers as instructed in Starting the MESA Servers.

2. Clear your Image Manager of all images.

3. Run the test script:

   perl 1503/1503_imgmgr.pl

This script will send messages to your system and prompt you along the way. You are expected to send audit messages in response to certain events (such as DICOM C-Find requests).

Evaluation

1. Run the evaluation script:

   perl 1503/eval_1503.pl <AE Title MPPS Mgr>

2. The evaluation output is found in 1503/mir_mesa_1503.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

3. Grab all of the files (tar/zip) in $MESA_TARGET/logs/syslog and send these to the Project Manager.

Supplemental Information

Image Manager Test 1531: Basic Security, Administrative and Procedure Performance Process Flow

Test case 1531 uses the same transactions as defined for test 131: Administrative and Procedure Performance Process Flow. The nominal patient name is BLACK^CHARLES. Notes: Before starting this test, make sure you have stopped the MESA servers for the standard mode tests and started the MESA servers for the secure mode tests.

References

Instructions

1. To run this test (the reference to 131 below is intentional):

   perl scripts/imgmgr_secure.pl 131 <log>

Evaluation

1. To evaluate this test (1531, not 131):

   perl 1531/eval_1531.pl <log>  <MPPS Mgr AE title> <SC AE title>

Supplemental Information

To change patient name, patient ID prior to the test (131 is intentional):

   cd $MESA_TARGET/mesa_tests/rad/msgs
   perl mesa_reset/131.pl ihe-us/131.var  (or)
   perl mesa_reset/131.pl

Evidence Document Tests

This section describes tests that are specific to the IHE Evidence Document integration profile.

Image Manager Test 1701: Evidence Document Management in Scheduled Workflow

Test 1701 covers evidence document management in scheduled workflow, part of the Evidence Document profile. The test itself is an implementation of the scheme shown in Figure 14.2-1 (see ).

References

RAD TF-1:14

Instructions

1. To run this test:

   perl  scripts/imgmgr_swf.pl 1701 <log>

2. Evaluation

To evaluate this test:

   perl  1701/eval_1701.pl <log>

Supplemental Information

Nuclear Medicine Profile Tests

This section describes tests that are specific to the IHE Nuclear Medicine integration profile.

Image Manager Test 2601: NM Storage SOP Classes

This test is not yet implemented in the MESA tools.

References

Rad TF-2:4.8.4.1.3.1.

Instructions

Test 2601 is used to determine if an Image Manager supports storage of required NM image types.

Evaluation

Supplemental Information

Image Manager Test 2602: NM Query Keys

This test is not yet implemented in the MESA tools.

References

Rad TF-2:4.14.4.1.2

Instructions

Test 2602 is used to determine if an Image Manager supports query keys required by the NM Integration Profile.

Evaluation

Supplemental Information

Image Fusion (FUS) Profile Tests

Tests in this section apply to Image Manager actors in the Image Fusion Profile.

Image Manager Test 3512: Spatial Registration Storage and Storage Commitment

This test is not yet implemented in the MESA tools.

This tests the ability of the Image Manager to store Spatial Registration objects and respond to a Storage Commitment request from the MESA Evidence Creator. Successful completion of this test is prerequisite for completion of the remaining 35xx tests.

References:

RAD TF-3: 4.56 DICOM PS3.3 – 2004 A.30

Test description/steps for test 3512.

Instructions

1. Make sure the MESA servers have been started as described in [Starting the MESA Servers] above.

2. Run the test script as follows:

   perl  scripts/imgmgr_fusion.pl 3512 <log>

3. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl 3512/eval_3512.pl <log level> <AE Title Storage Commit SCP> 

2. The evaluation output is found in 3512/mir_mesa_3512.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

Image Manager Test 3540: BSPS Storage and Storage Commitment

This test is not yet implemented in the MESA tools.

This tests the ability of the Image Manager to store Blended Softcopy Spatial Registration (BSPS) objects and respond to a Storage Commitment request from the MESA Evidence Creator.

References:

RAD TF-3: 4.57 DICOM PS3.3 – 2004 A.30

Test description/steps for test 3540.

Instructions

1. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

2. Run the test script as follows:

   perl  scripts/imgmgr_fusion.pl 3540 <log>

3. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl 3540/eval_3540.pl <log level> <AE Title Storage Commit SCP> 

2. The evaluation output is found in 3540/mir_mesa_3540.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

Image Manager Test 3556: BSPS and Spatial Registration Retrieve

This test is not yet implemented in the MESA tools.

The Image Manager is sent C-MOVE requests to retrieve BSPS, Spatial Registration and image objects. This will include series-level moves. The Image Manager should correctly send all requested objects to the server.

References:

RAD TF-2: 4.17 & 4.18

RAD TF-3: 4.57 & 4.58

Instructions

1. Start the MESA servers as indicated in [Starting the MESA Servers].

2. Run the script 3556/load_img_mgr.pl. This will send studies to your Image Manager that include BSPS, Spatial Registration objects, and referenced series of images.

3. Run the script 3556/3556_imgmgr.pl. This will clear the MESA workstation and send C-MOVE requests to move images, Spatial Registration and BSPS objects to the MESA workstation server.

Evaluation

1. Run the script 3556/eval_3556.pl. This will evaluate the objects retrieved from your Image Manager and indicate pass/fail.

Supplemental Information

Mammography Image Integration Profile Tests

This section describes tests that are specific to the IHE Image Fusion (FUS) profile.

Image Manager Test 3620: Image Fusion – Vendor Interoperability

Instructions

Test 3620 tests the storage of BSPS, Spatial Registration and image objects for Fusion created by other vendors. BSPS and Spatial Registration objects may be new to some Image Manager systems. Every Modality and Evidence Creator vendor’s objects submitted to the MESA test tool for this profile in test 3620 must be tested prior to the connectathon. No MESA software required.

1. DICOM data sets (BSPS, Spatial Registration, image series) created by Acquisition Modality and Evidence Creator actors in the Fusion Profile for MESA testing will be made available to Image Display and Image Manager actors. You will find these samples in gazelle under Connectathon -> List of samples.... We ask vendors to submit these samples at least 3 weeks prior to the MESA test deadline.

2. The Image Manager should store these DICOM objects so that you are confident your software understands the content.

3. After you have tested with all of the samples, create a text file indicating which vendors' objects you have tested with. Upload this file into gazelle as the results for test 3620.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in storing the fusion studies, you should notify the Project Manager. You will be asked to work with those vendors (and the Project Manager) to resolve those issues.

Supplemental Information

Mammography Image Integration Profile Tests

This section describes tests that are specific to the IHE Mammography Image Integration (MAMMO) profile.

Image Manager Test 3920: Mammo Storage SOP Classes

Image Manager / Image Archive actors in the MAMMO profile are required to support storage of:

• 1.2.840.1008.5.1.4.1.1.2 Digital Mammography Image Storage - For Presentation
• 1.2.840.1008.5.1.4.1.1.2.1 Digital Mammography Image Storage - For Processing
• 1.2.840.1008.5.1.4.1.88.50 Mammography CAD SR

This test C-STOREs one object of each type to your Image Manager.

Reference

Rad TF-2:4.8.4.1.3.1

Rad TF-3:4.43.4.2.1

Instructions

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

2. Make sure the MESA servers have been started as described in [Starting the MESA Servers] above.

3. There is no workflow associated with this test; run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl  3920/eval_3920.pl <log_level>

2. The evaluation output is found in 3920/mir_mesa_3920.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

Mammography Acquisition Workflow Integration Profile Tests

This section describes tests that are specific to the IHE Mammography Acquisition Workflow Integration(MAWF) profile.

Image Manager Test 4102: MAWF Vendor Interoperability - View Correction

Image Managers in the MAWF profile are required to support storage of DICOM KOS objects as well as mammography images.

This test gives you access to sample images and KOS objects created by MAWF Acquisition Modalities and Evidence Creators prior to the Connectathon. They are asked to submit samples into gazelle 3 weeks prior to the MESA test deadline or earlier. The goal is to avoid surprises on the Connectathon floor.

References

RAD TF-2:4.66.4.2.3

Instructions

You will find these samples in gazelle under Connectathon -> List of samples....

Your task is to test with these samples prior to the Connectathon. See expected behavior in the TF reference above. Do not complete this test before those samples are available.

Create a short txt file indicating you have accessed these samples. List those that you have successfully tested with your Image Manager. If you find a problem, contact the Project Manager who will facilitate working with the modality or EC vendor.

Upload that txt file into the gazelle system under the MESA test log results for this test.

Radiation Exposure Monitoring - REM and REM-NM - Profile Tests

This section describes tests that are specific to the IHE Radiation Exposure Monitoring profiles: REM and REM-NM.

Image Manager Test 4400: REM Vendor Interoperability

Image Managers in the REM profile are required to support storage of DICOM Dose SR objects.

This test gives you access to sample DICOM SRs created by REM Acquisition Modalities prior to the Connectathon. Modalities are asked to submit samples into gazelle 3 weeks prior to the MESA test deadline or earlier. The goal is to avoid surprises on the Connectathon floor.

You will find these samples in gazelle under Connectathon -> List of samples....

Your task is to test with these samples prior to the Connectathon. Do not complete this test before those samples are available.

Create a short txt file indicating you have accessed these samples. List those that you have successfully tested with your Image Manager. If you find a problem, contact the Project Manager who will facilitate working with the modality vendor.

Upload that txt file into the gazelle system under the MESA test log results for this test.

Image Manager Test 4404: Store Dose SR

Test Case 4404 stores one Dose SR object to the Image Manager and then performs a C-Find to determine if the object was actually stored.

References

RAD TF

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr'.

2. Make sure the MESA servers have been started as described in [Starting the MESA Servers] above.

3. Run the test script as follows:

   perl scripts/imgmgr_rem.pl 4404 <log>

4. Run the evaluation script below.

Evaluation

1. Run the evaluation script

    perl  4404/eval_4404.pl <log> 

2. The evaluation output is found in 4404/mir_mesa_4404.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

The sample that we use has the proper SOP class for the Dose SR object, but the object is not complete. If your Image Manager has validation software, it will likely reject this object.

Available Since

Version 12.2.0

Image Manager Test 4410: REM-NM Vendor Interoperability

Image Managers in the REM-NM profile are required to support storage of DICOM Radiopharmaceutical Radiation Dose Structured Report (RRDSR) objects.

This test gives you access to sample DICOM RRDSRs created by REM-NM Radiopharmaceutical Activity Supplier (RAS) systems prior to the current Connectathon. RASs are asked to submit samples into gazelle 2-3 weeks prior to the Connectathon test deadline (or earlier). The goal is to avoid surprises on the Connectathon floor.

Instructions

• You will find these samples in gazelle under Connectathon -> List of Samples. Select your system name and look for the REM-NM entry under Samples available for rendering to find sample REM-NM RRDSRs.

• Your task is to test with these samples prior to the Connectathon.

Evaluation

• Create a short txt file indicating you have accessed these samples. List those that you have successfully tested with your Image Manager. If you encounter problems, contact the Project Manager who will help resolve them with Modality vendors. Upload that txt file into gazelle as the results for this test.

PERF - CT/MR Perfusion Imaging with Contrast Tests

This section describes tests that are specific to the Radiology CT/MR Imaging with Contrast Integration Profile.

Test Case 4550: PERF Vendor Interoperability - Exchange Enhanced CT and MR Image Samples

Test 4550 tests the storage of DICOM objects created by Acquisition Modality actors in the PERF profile. Every vendors' objects submitted must be tested and successfully stored.

Instructions

1. Download the participant-supplied datasets for this test. These are found in gazelle under Connectathon-->List of samples Select your system name and look under Objects to render to find sample images for test 4550.

2. C-STORE these images into your system

3. Create a text file which lists the available samples and a note for each indicating whether you were able to successfully store them. If not, detail the problem. Upload that file as the result log for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in storing the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.

The goal of this test is to make sure your system can store the datasets produced by other systems. This also serves as a test of those objects.

DIFF - MR Diffusion Imaging Tests

This section describes tests that are specific to the Radiology MR Diffusion Imaging Integration Profile.

Test Case 4650: DIFF Vendor Interoperability - Exchange Enhanced MR Image Samples

Test 4650 tests the storage of DICOM objects created by Acquisition Modality actors in the DIFF profile. Every vendors' objects submitted must be tested and successfully stored.

Instructions

1. Download the participant-supplied datasets for this test. These are found in gazelle under Connectathon-->List of samples'. Select your system name and look under Objects to render to find sample images for test 4650.

2. C-STORE these images into your system

3. Create a text file which lists the available samples and a note for each indicating whether you were able to successfully store them. If not, detail the problem. Upload that file as the result log for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in storing the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.

The goal of this test is to make sure your system can store the datasets produced by other systems. This also serves as a test of those objects.

SMI - Stereotactic Mammography Imaging Tests

This section describes tests that are specific to the Radiology Stereotactic Mammography Imaging Profile.

Test Case 4950: SMI Vendor Interoperability - Exchange Stereotactic Mammography Image Samples

Test 4950 tests the storage of DICOM objects created by Acquisition Modality actors in the SMI profile. Every vendors' objects submitted must be tested and successfully stored.

Instructions

1. Download the participant-supplied datasets for this test. Due to the size of the samples, these are not uploaded into gazelle. Instead, we ask Modality vendors to upload samples 2-3 weeks prior to the pre-Connectathon test deadline onto the IHE ftp site: [1]. Look for the sub-directory for your connectathon.

2. C-STORE these images into your system

3. Create a text file which lists the available samples and a note for each indicating whether you were able to successfully store them. If not, detail the problem. Upload that file as the result log for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in storing the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.

The goal of this test is to make sure your system can store the datasets produced by other systems. This also serves as a test of those objects.

DBT - Digital Breast Tomosynthesis Tests

This section describes tests that are specific to the Radiology Stereotactic Mammography Imaging Profile.

Test Case 5250: DBT Vendor Interoperability - Exchange Stereotactic Mammography Image Samples

Test 5250 tests the storage of DICOM objects created by Acquisition Modality actors in the DBT profile. Every vendors' objects submitted must be tested and successfully stored.

Instructions

1. Download the participant-supplied datasets for this test. Due to the size of the samples, these are not uploaded into gazelle. Instead, we ask Modality vendors to upload samples 2-3 weeks prior to the pre-Connectathon test deadline onto the IHE ftp site: ftp://ftp.ihe.net/Connectathon/samples/RAD-profiles/DBT_samples/. Look for the sub-directory for your connectathon.

2. C-STORE these images into your system

3. Create a text file which lists the available samples and a note for each indicating whether you were able to successfully store them. If not, detail the problem. Upload that file as the result log for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in storing the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.

The goal of this test is to make sure your system can store the datasets produced by other systems. This also serves as a test of those objects.

Tests for Cardiology

Image Manager Test 20106: C5: Patient NOT Registered (no Order)

This test is not yet implemented in the MESA tools.

Test 20106 covers C5: Patient Not Registered.

References

CARD TF-1:3.4.5

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/card/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Run the test script as follows:

   perl  scripts/imgmgr_cath.pl 20106 <log_level>

4. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl  20106/eval_20106.pl <log> <AE     Title MPPS Mgr>

The evaluation output is found in 20106/mir_mesa_20106.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

Test Case 20602: ED: Describe Image Manager/Image Archive Methods

References

Instructions

Test 20602: Do not divulge any proprietary information. Create a Word document with the following naming convention: CompanyName_Product_20602_IM_2008.doc and send it to the appropriate Domain (cardiology, radiology, ITI) Technical Project Manager. In 500 words or less for each, describe the following:

1. Which SOP Classes does your product support? (e.g, Comprehensive, Basic Text, etc.)

2. Confirm that your IM product can support any Template within a SOP Class.

Evaluation

Supplemental Information

Image Manager Test 20106: C5: Patient NOT Registered (no Order)

Test 20106 covers C5: Patient Not Registered.

References

CARD TF-1:3.4.5

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/card/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Run the test script as follows:

   perl  scripts/imgmgr_cath.pl 20106 <log_level>

4. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl  20106/eval_20106.pl <log> <AE Title MPPS Mgr>

2. The evaluation output is found in 20106/mir_mesa_20106.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

Image Manager Test 20725: STRESS Storage SOP Classes

Image Manager / Image Archive actors in the Stress Testing Workflow Integration profile are required to support storage of:

• 1.2.840.1008.5.1.4.1.1.9.1.1 12-Lead ECG Waveform Storage
• 1.2.840.1008.5.1.4.1.1.9.1.2 General ECG Waveform Storage
• 1.2.840.1008.5.1.4.1.1.88.22 Enhanced SR
• 1.2.840.1008.5.1.4.1.1.88.33 Comprehensive SR
• 1.2.840.1008.5.1.4.1.1.88.40 Procedure Log
• 1.2.840.1008.5.1.4.1.1.104.1 Encapsulated PDF

This test C-STOREs one object of each SOP Class to your Image Manager.

Reference

CARD TF-2:4.2.6

Instructions

1. Set the current directory to $MESA_TARGET/mesa_tests/card/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. There is no workflow associated with this test; run the evaluation script below.

Evaluation

1. Run the evaluation script

    perl  20725/eval_20725.pl <log_level>

2. The evaluation output is found in 20725/mir_mesa_20725.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

Eye Care Profile Tests

The tests in this section apply to Image Manager actors in the Eye Care Profile.

Test 281: Example Images and other DICOM objects

In this test, Image Managers will store/examine the DICOM samples provided by other participants. The goal of the test is to make sure the Image Manager actors are not surprised by content when they arrive at a Connectathon.

Instructions

1. Find sample images submitted onto ftp.aao.org; contact the project manager for login/password). This content will evolve as vendors add samples, so be patient.
2. Retrieve the DICOM or zip files created by the other vendors. Examine/store them so that you are confident your software understands the content.
3. When you are finished, create a .txt or other file that lists the samples you tested with, and a brief comment on your result (eg "ok", or "could not store" or "error in attribute xxx"). Upload that txt file into gazelle as the result file for this test.
4. If you find issues with the images, send an email to the Connectathon Project Manager.
5. The goal is no surprises.

Evaluation

The evaluation of this test is performed by examining the text you provided to make sure you made a good faith effort to review the sample images. If you find problems with some samples, we will give your feedback to the Modality test partner.

50000: Eye Care Workflow: Test 1

Test 50000 covers a simple Eye Care Workflow scenario.

• A known patient is registered
• An order is placed for a procedure
• that order is scheduled
• images are acquired and stored to the Image Manager.

The patient, registered at the ADT, is BALTIMORE^CHARLES with a patient ID of 50000.

References:

Test description/steps for test 50000.

Instructions

1. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

2. Run the test script as follows:

   perl  scripts/imgmgr_swf.pl 50000 <log>

3. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl 50000/eval_50000.pl <log level> <AE Title MPPS SCP> <AE Title Storage Commit SCP> 

2. The evaluation output is found in 50000/mir_mesa_50000.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

50002: Eye Care Workflow: Patient Renamed

Test 50002 covers Eye Care workflow for the case of the patient changing name after original registration, order and image generation

• A known patient is registered
• An order is placed for a procedure
• That order is scheduled
• Images are acquired and stored to the Image Manager.
• The patient changes name after the acquisition.

The patient, registered at the ADT, is BRANSON^JANE with a patient ID of 50002.

References:

Test description/steps for test 50002.

Instructions

1. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

2. Run the test script as follows:

   perl  scripts/imgmgr_swf.pl 50002 <log>

3. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl 50002/eval_50002.pl <log level> <AE Title MPPS SCP> <AE Title Storage Commit SCP> 

2. The evaluation output is found in 50002/mir_mesa_50002.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

50003: Eye Care Workflow: Patient Merge

Unimplemented

References:

Test description/steps for test 50003.

Instructions

1. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

2. Run the test script as follows:

   perl  scripts/imgmgr_swf.pl 50003 <log>

3. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl 50003/eval_50003.pl <log level> <AE Title MPPS SCP> <AE Title Storage Commit SCP> 

2. The evaluation output is found in 50003/mir_mesa_50003.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

50004: Eye Care Workflow: Modality Performs Different Procedure

Test 50004 covers Eye Care workflow for the case of the modality performing a different procedure than that found on the MWL.

• A known patient is registered
• An order is placed for a procedure
• That order is scheduled
• Images are acquired and stored to the Image Manager.

The patient, registered at the ADT, is YORK^JUDITH with a patient ID of 50004.

References

Test description/steps for test 50004.

Instructions

1. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

2. Run the test script as follows:

   perl  scripts/imgmgr_swf.pl 50004 <log>

3. Run the evaluation script below.

Evaluation

1. Run the evaluation script

   perl 50004/eval_50004.pl <log level> <AE Title MPPS SCP>

2. The evaluation output is found in 50004/mir_mesa_50004.xml. The final result should indicate 0 errors. Submit the result run at log level 4 to the Project Manager. For pre-Connectathon tests, this normally means uploading the XML file into the Kudu or Gazelle tool.

Supplemental Information

50401: Eye Care Modalities in Study

In test 50401, the MESA tools transmit 3 DICOM objects from 3 different modality types (SOP classes differ and 0008 0060 differ) to an Image Manager. These objects are in a single study. The MESA tools then send a C-Find request for that one study and requests the attribute for 0008 0061 Modalities in Study. The Image Manager must return the proper value in that return key. The return key should have three values; order is not important.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Load one PDF file into the Image Manager:

       perl 50401/load_50401.pl

4. Send one query to the Image Manager:

       perl 50401/query_50401.pl

5. The query will create two result files in the 50401 folder. The file in 50401/test is the response returned by the Image Manager under test. The file in 50401/mesa is the value returned by the MESA tools.

Evaluation

1. Run the test/evaluation script as follows:

   perl 50401/eval_50401.pl log_level (use 4 for log_level)

2. The output result is stored in 50401/mir_mesa_50401.xml. Submit that xml file (and not grade_50401.txt) to the Project Manager for evaluation.

Supplemental Information

50402: Eye Care Related Series/SOP Instances

This test is not ready. Submit a text file indicating the test is deferred.

References

Instructions

Evaluation

Supplemental Information

50404: Eye Care Image Specific Queries

Test 50404 is a test of the Eye Care extensions that are defined in Eye Care 2: 4.5. The one specific extension is that the Image Manager shall be able to return 0010 0021 Issuer of Patient ID as a Query Return Key.

In test 50411, the MESA tools store one document to an Image Manager and send a C-Find request with 0010 0021 Issuer of Patient ID as a return key. The Image Manager must return the proper value for the Document Title to complete this test.

I think there is an error in the TF and DICOM standard that specifies this is at the Study Level. I believe this belongs at the Patient Level (or Study level in the combined model). Because Eye Care has chosen to specify the Study Root model, the issue can be ignored. I will run this past the DICOM WG 6 to ask about the Patient Root model. (Moore)

References

Eye Care TF 2: 4.5.5

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Load one PDF file into the Image Manager (yes, the step uses 50411)

       perl 50411/load_50411.pl

4. Send one query to the Image Manager:

       perl 50404/query_50404.pl

5. The query will create two result files in the 50404 folder. The file in 50404/test is the response returned by the Image Manager under test. The file in 50404/mesa is the value returned by the MESA tools.

Evaluation

1. Run the test/evaluation script as follows:

   perl 50404/eval_50404.pl log_level (use 4 for log_level)

2. The output result is stored in 50404/mir_mesa_50404.xml. Submit that xml file (and not grade_50404.txt) to the Project Manager for evaluation.

Supplemental Information

50405: Eye Care Img Mgr SOP Classes / Xfer Syntaxes

Test 50405 is a test of the requirements for storage of SOP classes as defined in Eye Care TF 2: 4.2.

In this test, the MESA tools propose SOP classes with transfer syntaxes to determine if the Image Manager supports the required Storage SOP Classes

References

Eye Care TF 2: 4.5

Instructions

This test is different from normal tests. For this test, you run the evaluation steps directly without starting a test.

Evaluation

To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Run the test/evaluation script as follows:

   perl 50405/eval_50405.pl log_level (use 4 for log_level)

4. The output result is stored in 50405/mir_mesa_50405.xml. Submit that xml file (and not grade_50411.txt) to the Project Manager for evaluation.

Supplemental Information

50411: Eye Care Document Title Return Key

In test 50411, the MESA tools store one document to an Image Manager and send a C-Find request with 0042 0010 Document Title as a return key. The Image Manager must return the proper value for the Document Title to complete this test.

References

Eye Care TF 2: 4.4.5

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Load one PDF file into the Image Manager:

       perl 50411/load_50411.pl

4. Send one query to the Image Manager:

       perl 50411/query_50411.pl

5. The query will create two result files in the 50411 folder. The file in 50411/test is the response returned by the Image Manager under test. The file in 50411/mesa is the value returned by the MESA tools.

Evaluation

1. Run the test/evaluation script as follows:

   perl 50411/eval_50411.pl log_level (use 4 for log_level)

2. The output result is stored in 50411/mir_mesa_50411.xml. Submit that xml file (and not grade_50411.txt) to the Project Manager for evaluation.

Supplemental Information

Test Cases for Eye Care Evidence Documents

Test 313: C-Store Encapsulated PDF

In this test, the MESA tools will store one Encapsulated PDF file to the Image Manager. The goal of the test is to provide Image Managers with an example of one storage request with a PDF file. In this version, there is no follow-up query to determine if the storage was successful. That will occur in a later version.

References

Instructions

To run this test, follow these steps using a DOS window or terminal emulator:

1. Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgmgr.

2. Make sure the MESA servers have been started as described in Starting the MESA Servers above.

3. Run the test script as follows:

   perl scripts/imgmgr_swf.pl 313 log_level

Evaluation

There is no formal evaluation. After you have determined that you have successfully stored the Encapsulated PDF, enter a note in gazelle under this test indicating that you have completed the test.

Supplemental Information

Test 50216: ECED Example Evidence Document

In this test, Image Managers will examine the sample evidence documents provided by other participants. The goal of the test is to make sure the Image Manager actors are not surprised by content when they arrive at a Connectathon.

References

Instructions

1. On this wiki, find the page that lists Test Software/Data for your Connectathon. Do not use data from a different connectathon unless you are explicitly given that instruction from the Connectathon Manager.
2. On the Test Software/Data page, you should see a link to Shared Data and test 50216. That will give you access to a page that lists sample documents uploaded by other vendors.
3. Retrieve the zip files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
4. You will find a table called Results Table on the samples for test 50216. Extract this table and place it in a spreadsheet that can be read by Excel. Fill in the columns labelled Reviewed and Comments. The Comments field is mainly an indicator of issues with the images. If there are no issues, you can leave that blank.
5. When you are finished, upload the spreadsheet into the Kudu / Gazelle tool.
6. If you find issues with the images, send an email to the Connectathon Manager now to wake him or her up. You can also contact the image provider directly to resolve issues.
7. The goal is no surprises.

Evaluation

The evaluation of this test is performed by examining the spreadsheet you provided to make sure you made a good faith effort to review the sample reports.

Supplemental Information