HIMSS and RSNA
Integrating the Healthcare Enterprise
IHE/MESA Cross Reference Mgr 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.11.0
29-November-2006
Contents:
Cross Reference Manager Tests
Introduction
Patient Identification
Configuration
Starting the MESA Servers
Installation Test
Submission of Results
Test Cases: PIX
The MESA tests include a number of cases each of which rely on a sequence of messages between actors. These tests range across different integration profiles:
This document lists the transactions and messages for a number of cases. It may not describe the clinical scenario behind each case, but listing the transactions should clearly define what is expected of each actor. These are all of the transactions involving all of the actors. When you test with your particular actor, you may see only a subset of these messages.
The MESA scripts are run from the directory $MESA_TARGET/mesa_tests/iti/xref_mgr. The ASCII configuration file xref_mgr.cfg contains parameters that identify the Cross Reference Manager under test and the MESA Cross Reference Manager.
Edit the configuration file and modify the two entries that begin with TEST to identify your Cross Reference Manager. The value for TEST_XREF_HOST_HL7 can specify an IP address or a host name (assuming the host table or DNS is accurate).
The default port number for the MESA Cross Reference Manager is 3600. You should only change this port number if there is a conflict with another service on the MESA test computer. There will be no conflicts with other MESA servers; the only conflict would occur with something from the operating system or other software package.
MESA servers are started from a DOS/CMD window or a terminal emulator. Follow these steps for Unix systems
cd $MESA_TARGET/mesa_tests/iti/actors/xref_manager
scripts/start_mesa_servers.csh
To stop the servers:
scripts/stop_mesa_servers.csh
The start instructions for MESA tools on a Windows system are:
cd %MESA_TARGET%\mesa_tests\iti\actors\xref_manager
scripts\start_mesa_servers.bat
To stop the MESA servers:
scripts/stop_mesa_servers.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.
This section describes test cases that are generally associated with the PIX Integration Profile. There may be some overlap with other profiles.
Each test case involves a series of transactions involving one test patient. Some patients may require that a single actor participate in multiple transactions. The tables in this section give the order of messages for an integrated system with all actors. This is provided as a centralized reference. To test an individual IHE actor, refer to the appropriate test document.
Test Case 10501: PIX Query Case 1 and Case 2Test case 10501 covers the PIX Query Case 1 and 2. One patient (ALPHA) is registered in two different domains. A second patient (SIMPSON) is registered in a single domain. Three registration messages are sent to a Cross Reference Manager. ReferencesITI TF-2: 3.9.4.2.2 InstructionsTo run this test, follow these steps using a DOS window or terminal emulator:
perl scripts/xref_mgr_pix.pl 10501 <log level>where <log level> is a value between 1 and 4.
EvaluationTo evaluate your response to this test:
perl 10501/eval_10501.pl 4
Supplemental InformationThe evaluation script takes a single argument, <log level>. When debugging output, it is sometimes helpful to use a log level of 1 to see only differences. When submitting results, we prefer the output with the most verbose level, 4. |
Test case 10502 covers the PIX Query case 3. Two patients are registered in a single domain. A PIX consumer sends a query for a third patient who is not recognized as one of the two registered patients.
ITI TF-2: 3.9.4.2.2
To run this test, follow these steps using a DOS window or terminal emulator:
perl scripts/xref_mgr_pix.pl 10502 <log level>where <log level> is a value between 1 and 4.
To evaluate your response to this test:
perl 10502/eval_10502.pl 4
The evaluation script takes a single argument, <log level>. When debugging output, it is sometimes helpful to use a log level of 1 to see only differences. When submitting results, we prefer the output with the most verbose level, 4.
Test Case 10503: PIX Query Case 4Test case 10503 covers the PIX Query case 4. No new patients are registered. A PIX query is sent with a Patient ID that includes an unknown issuer (value is ‘XXXX’). The Cross Reference Manager responds appropriately. ReferencesITI TF-2: 3.9.4.2.2 InstructionsTo run this test, follow these steps using a DOS window or terminal emulator:
perl scripts/xref_mgr_pix.pl 10503 <log level>where <log level> is a value between 1 and 4.
EvaluationTo evaluate your response to this test:
perl 10503/eval_10503.pl 4
Supplemental InformationThe evaluation script takes a single argument, <log level>. When debugging output, it is sometimes helpful to use a log level of 1 to see only differences. When submitting results, we prefer the output with the most verbose level, 4. |
Test case 10506 covers PIX Patient Feed, the ADT^A08 message, and PIX queries. Patient TAU^TERI is registered in domain ADT1 with “correct” demographics. This patient is then registered in ADT2 with incorrect demographics. The demographics are sufficiently different that a Cross Reference Manager should not link these two records.
A patient update message is sent for the patient in domain ADT2 that should synchronize the demographics with those seen in ADT1. The Cross Reference Manager should now link the two records.
ITI TF-2: 3.9.4.2.2
To run this test, follow these steps using a DOS window or terminal emulator:
perl scripts/xref_mgr_pix.pl 10506 <log level>where <log level> is a value between 1 and 4.
To evaluate your response to this test:
perl 10506/eval_10506.pl 4
The evaluation script takes a single argument, <log level>. When debugging output, it is sometimes helpful to use a log level of 1 to see only differences. When submitting results, we prefer the output with the most verbose level, 4.
Test Case 10511: PIX Patient Feed: A01Test case 10511 covers PIX Patient Feed and the ADT^A01 message. ReferencesITI TF-2: 3.8.4 InstructionsEvaluationSupplemental Information |
Test case 10512 covers PIX Patient Feed and the ADT^A04 message. These behaviors are tested:
The nominal patient name is EPSILON^ELLIE.
ITI TF-2: 3.8.4
To run this test, follow these steps using a DOS window or terminal emulator:
perl scripts/xref_mgr_pix.pl 10512 <log level>where <log level> is a value between 1 and 4.
Test Case 10513: PIX Patient Feed: A05Test case 10513 covers PIX Patient Feed and the ADT^A05 message. ReferencesITI TF-2: 3.8.4 InstructionsEvaluationSupplemental Information |
Test case 10514 covers PIX Patient Feed and the ADT^A08 message.
ITI TF-2: 3.8.4
Test Case 10515: PIX Patient Feed: A40Test case 10515 covers PIX Patient Feed and the ADT^A40 message. ReferencesITI TF-2: 3.8.4 InstructionsEvaluationSupplemental Information
|
Test case 10531 covers a use case involving the PIX Update Notification transaction and behavior of the Cross-reference Manager.
ITI TF-2: 3.10
Test Case 10532: PIX Update Notification: MESA 2Test case 10532 covers a use case involving the PIX Update Notification transaction and behavior of the Cross-reference Manager. ReferencesITI TF-2: 3.10 InstructionsEvaluationSupplemental Information |
Test case 10533 covers a use case involving the PIX Update Notification transaction and behavior of the Cross-reference Manager.
ITI TF-2: 3.10
Test Case 10541: PIX Integrated Test 1Test case 10541 covers a use case with several PIX transactions integrated into a larger test. ReferencesITI TF-2: 3.10 InstructionsEvaluationSupplemental Information |
Test case 10542 covers a use case with several PIX transactions integrated into a larger test.
ITI TF-2: 3.10
Test Case 10543: PIX Integrated Test 3Test case 10543 covers a use case with several PIX transactions integrated into a larger test. ReferencesITI TF-2: 3.10 InstructionsEvaluationSupplemental Information |
This section describes test cases that are generally associated with the PSA Integration Profile. There may be some overlap with other profiles.
Each test case involves a series of transactions involving one test patient. Some patients may require that a single actor participate in multiple transactions. The tables in this section give the order of messages for an integrated system with all actors. This is provided as a centralized reference. To test an individual IHE actor, refer to the appropriate test document.
This section describes test cases that are generally associated with the CT component. There may be some overlap with other profiles.