HIMSS and RSNA
Integrating the Healthcare Enterprise
IHE/MESA Cross Reference Consumer Tests
Electronic Radiology Laboratory
Mallinckrodt Institute of Radiology
510 South Kingshighway Blvd.
St. Louis, MO 63110
314.362.6965 (Voice)
314.362.6971 (Fax)
Version 10.11.0
29-November-2006
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 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_consumer. The ASCII configuration file xref_consumer.cfg contains parameters that configure the MESA Cross Reference Manager. The default port number 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.
You should configure your Cross Reference Consumer to send HL7 query messages to the MESA Cross Reference Manager listening on port 3600. HL7 communication uses TCP sockets and the minimal lower level protocol.
MESA servers are started from a DOS/CMD window or a terminal emulator. Follow these steps for Unix systems:
To stop the servers:
The start instructions for MESA tools on a Windows system are:
To stop the MESA servers:
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.
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. A PIX Query is sent to resolve a reference to ALPHA. A second PIX Query is sent to resolve a reference to SIMPSON. Because SIMPSON is not registered in the second domain, the response to that PIX Query will indicate no data. ReferencesITI TF-2: 3.9.4.2.2 InstructionsTo run this test, follow these steps using a DOS window or terminal emulator:
EvaluationTo evaluate your response to this test:
Supplemental InformationIf you want to see a query generated by a MESA Cross Reference Consumer, run test 10501 in self test mode. Then run the evaluation as above and examine the grade file. To run in self test mode: perl scripts/xref_cons_pix.pl 10501 4 self |
10502: PIX Query Case 3Test 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. ReferencesITI TF-2: 3.9.4.2.2 InstructionsTo run this test, follow these steps using a DOS window or terminal emulator:
EvaluationTo evaluate your response to this test:
|
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:
EvaluationTo evaluate your response to this test:
Supplemental Information |
10531: PIX Update Notification: MESA 1Test case 10531 covers a use case involving the PIX Update Notification transaction and behavior of the Cross-reference Manager. ReferencesITI TF-2: 3.10 |
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 |
10533: PIX Update Notification: MESA 3Test case 10533 covers a use case involving the PIX Update Notification transaction and behavior of the Cross-reference Manager. ReferencesITI TF-2: 3.10 |
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 |
10542: PIX Integrated Test 2Test case 10542 covers a use case with several PIX transactions integrated into a larger test. ReferencesITI TF-2: 3.10 |
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 |