MESA/Patient Cross Reference Manager

MESA/Patient Cross Reference Manager

Cross Reference Manager Tests

Introduction

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:

• Retrieve Information for Display
• Enterprise User Authentication
• Patient Identity Cross Reference for MPI
• Patient Synchronized Application
• Consistent Time

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.

Configuration

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.

Starting the MESA Servers

MESA servers are started from a DOS/CMD window or a terminal emulator. Follow these steps for Unix systems

   1. cd $MESA_TARGET/mesa_tests/iti/actors/xref_mgr

   2. scripts/start_mesa_servers.csh

To stop the servers:

    1. scripts/stop_mesa_servers.csh

The start instructions for MESA tools on a Windows system are:

   1. cd  %MESA_TARGET%\mesa_tests\iti\actors\xref_manager

   2. scripts\start_mesa_servers.bat

To stop the MESA servers:

    scripts/stop_mesa_servers.bat

Submission of Results

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.

2 Test Cases: PIX

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 2

Test 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.

References

ITI TF-2: 3.9.4.2.2

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/iti/actors/xref_mgr.

2. Edit the file xref_mgr.cfg. This file describes your server that receives HL7 messages. Modify the values that begin with “TEST” to accurately describe your server.

3. Make sure the MESA servers have been started. See section 1.4 for details.

4. Run the test script as follows:

   perl  scripts/xref_mgr_pix.pl 10501 <log level>
                                                                                                     <log level> is a value between 1 and 4.

5. The test script will send three A04 registration messages to your system. After the three A04 messages, the test script sends two PIX queries. Your system will respond with appropriate PIX responses.

Evaluation

To evaluate your response to this test:

1. Run the evaluation script

    perl  10501/eval_10501.pl 4

2. The output file is 10501/mir_mesa_10501.xml. This test is successfully completed when the XML file indicates 0 errors/success. You can also examine 10501/grade_10501.txt and see if the last line indicates 0 errors.

3. Submit the grade file to the Project Manager

Supplemental Information

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 10502: PIX Query Case 3

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. The expected return is a response with the proper ERR segment.

References

ITI TF-2: 3.9.4.2.2

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/iti/actors/xref_mgr.

2. Edit the file xref_mgr.cfg. This file describes your server that receives HL7 messages. Modify the values that begin with “TEST” to accurately describe your server.

3. Make sure the MESA servers have been started. See section 1.4 for details.

4. Run the test script as follows:

   perl  scripts/xref_mgr_pix.pl 10502 <loglevel> 

where <log level> is a value between 1 and 4.

5. The test script will send three A04 registration messages to your system. After the three A04 messages, the test script sends two PIX queries. Your system will respond with appropriate PIX responses.

Evaluation

To evaluate your response to this test:

1. Run the evaluation script

    perl  10502/eval_10502.pl 4

2. The output file is 10502/mir_mesa_10502.xml. This test is successfully completed when the XML file indicates pass/0 errors. You can also check the end of 10502/grade_10502.txt.

3. Submit the grade file to the Project Manager (upload the XML file into Kudu or Gazelle).

Supplemental Information

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 4

Test 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 with the proper ERR segment.

References

ITI TF-2: 3.9.4.2.2

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/iti/actors/xref_mgr.

2. Edit the file xref_mgr.cfg. This file describes your server that receives HL7 messages. Modify the values that begin with “TEST” to accurately describe your server.

3. Make sure the MESA servers have been started. See section XXX for details.

4. Run the test script as follows:

    perl  scripts/xref_mgr_pix.pl 10503 <log level>

where <log level> is a value between 1 and 4.

5. The test script will send one PIX query with a PID that includes the issuer XXXX. This issuer is unknown to the Cross Reference Manager. The Cross Reference Manager should respond as defined in Case 4.

Evaluation

To evaluate your response to this test:

1. Run the evaluation script

    perl  10503/eval_10503.pl 4

2. The output file is 10503/mir_mesa_10503.xml. This test is successfully completed when the XML file indicates pass/0 errors. You can also check the end of 10503/grade_10503.txt.

3. Submit the grade file to the Project Manager (upload the XML file into Kudu or Gazelle).

Supplemental Information

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 10506: PIX Query, Patient Update

Test case 10506 covers PIX Patient Feed, the ADT^A08 message, and PIX queries.

• Patient TAU^TERI is registered in domain HIMS2005 with “correct” demographics.
• This patient is then registered in XREF2005 with incorrect demographics. The demographics are sufficiently different that a Cross Reference Manager should not link these two records.
• A PIX query is sent, and the expected response is NF.
• A patient update message is sent for the patient in domain XREF2005 that should synchronize the demographics with those seen in HIMS2005. The Cross Reference Manager should now link the two records.
• A second PIX query is sent. The response should show that the records are linked.

References

ITI TF-2: 3.9.4.2.2

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/iti/actors/xref_mgr.

2. Edit the file xref_mgr.cfg. This file describes your server that receives HL7 messages. Modify the values that begin with “TEST” to accurately describe your server.

3. Make sure the MESA servers have been started. See section XXX for details.

4. Run the test script as follows:

    perl  scripts/xref_mgr_pix.pl 10506 <log level>

where <log level> is a value between 1 and 4.

5. The test script will send one PIX query with a PID that includes the issuer XXXX. This issuer is unknown to the Cross Reference Manager. The Cross Reference Manager should respond as defined in Case 4.

Evaluation

To evaluate your response to this test:

1. Run the evaluation script

    perl  10506/eval_10506.pl 4

2. The output file is 10506/mir_mesa_10506.xml. This test is successfully completed when the XML file indicates pass/0 errors. You can also check the end of 10506/grade_10506.txt.

3. Submit the grade file to the Project Manager (upload the XML file into Kudu or Gazelle).

Supplemental Information

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: A01

Test 10511 is a repeat of 10501 but using A01 messages rather than A04 messages. We use the same patient names but different identifiers. You will likely have to clear your PIX Manager for the 10501 data before you run this test. Otherwise, you will end up correlating more patients than are expected by this test.

Test case 10511 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.

References

ITI TF-2: 3.9.4.2.2

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/iti/actors/xref_mgr.

2. Edit the file xref_mgr.cfg. This file describes your server that receives HL7 messages. Modify the values that begin with “TEST” to accurately describe your server.

3. Make sure the MESA servers have been started. See section 1.4 for details.

4. Run the test script as follows:

   perl  scripts/xref_mgr_pix.pl 10511 <log level>

<log level> is a value between 1 and 4.

5. The test script will send three A01 registration messages to your system. After the three A01 messages, the test script sends two PIX queries. Your system will respond with appropriate PIX responses.

Evaluation

To evaluate your response to this test:

1. Run the evaluation script

    perl  10511/eval_10511.pl 4

2. The output file is 10511/mir_mesa_10511.xml. This test is successfully completed when the XML file indicates 0 errors/success. You can also examine 10511/grade_10511.txt and see if the last line indicates 0 errors.

3. Submit the grade file (mir_mesa_10511.xml) to the Project Manager (upload into Kudu/Gazelle tool).

Supplemental Information

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 10512: PIX Patient Feed: A04

Test case 10512 covers PIX Patient Feed and the ADT^A04 message. These behaviors are tested:

• Patient Identity Source formulates an A04 message with the proper content
• Patient Identity Cross-reference Manager can receive and process a properly constructed ADT^A04 message.
• PIX Manager can receive/manage PID-3 values in at least three different formats.

The nominal patient name is EPSILON^ELLIE.

The PIX Manager needs to cross reference identifiers from different domains. The format of the Patient ID in PID-3 will vary depending on the ability of ADT systems. In this test, we send the same patient ID three times, but each time with a slightly different format of Assigning Authority. The goal is for the PIX Manager to accept all three versions and process them properly. There is no follow up query, so the test is more of a self-test that relies on the PIX Manager to be configured to fill in any needed but missing information.

References

ITI TF-2: 3.8.4

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/iti/actors/xref_mgr.

2. Edit the file xref_mgr.cfg. This file describes your server that receives HL7 messages. Modify the values that begin with “TEST” to accurately describe your server.

3. Make sure the MESA servers have been started. See section XXX for details.

4. In the step below, run the a script first. Then capture evidence that shows you have received the ADT message. Repeat for the b and c script. These all have the same demographics/patient ID, so you may need to alter values by hand in your database.

4.1 Run the test script as follows:

    perl  scripts/xref_mgr_pix.pl 10512a <log level>
    perl  scripts/xref_mgr_pix.pl 10512b <log level>
    perl  scripts/xref_mgr_pix.pl 10512c <log level>

where <log level> is a value between 1 and 4.

5. The test script will send an A04 registration message to your system.

Evaluation

1. Create evidence that this patient has been captured by your system:

a. Obtain a screen capture (software, digital camera) a UI screen

b. Extract a section of a log file

2. Name the output file xref_10512a.xxx, xref_10512b.xxx and xref_10512c.xxx where xxx is the appropriate extension such as jpg or bmp.

3. Zip/tar the screen capture file with other results and Submit to the Project Manager.

Supplemental Information

Test Case 10513: PIX Patient Feed: A05

Test case 10513 covers PIX Patient Feed and the ADT^A05 message.

References

ITI TF-2: 3.8.4

Instructions

Evaluation

Supplemental Information

Test Case 10514: PIX Patient Feed: A08

This test is covered by 10506. Do not run this test

Test case 10514 covers PIX Patient Feed and the ADT^A08 message.

References

ITI TF-2: 3.8.4

Instructions

Evaluation

Supplemental Information

Test Case 10515: PIX Patient Feed: A40

Test case 10515 covers PIX Patient Feed and the ADT^A40 message.

This test is not fully completed/tested. It is missing an evaluation script. You should read the instructions, run the test as described and look at your query response. We will work on getting an evaluation script written.

This test uses two different assigning authority domains and two patients. WASHINGTON^MARY and LINCOLN^MARY are the same person registered at different times. WASHINGTON is a maiden name. When she marries, she takes on the LINCOLN name and a new address. This history triggers the following sequence:

1. WASHINGTON registers in domain 1
2. WASHINGTON registers in domain 2
3. WASHINGTON marries, takes on the name LINCOLN and changes address at the same time. New A04 registration message is sent in domain 1 (because she forgot to tell the administrator of her name change).
   1. That means the A04 message above is for LINCOLN with a new address but same DOB
4. Someone recognizes the mistake and merges the records in domain 1. LINCOLN is the surviving record
5. Domain 2 has no direct knowledge of the merge. A query from domain 2 is made with the ID for WASHINGTON
6. The PIX manager should return the surviving ID for LINCOLN in domain 1.

References

ITI TF-2: 3.8

ITI TF-2: 3.9.4.2.2

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/iti/actors/xref_mgr.

2. Edit the file xref_mgr.cfg. This file describes your server that receives HL7 messages. Modify the values that begin with “TEST” to accurately describe your server.

3. Make sure the MESA servers have been started. See section 1.4 for details.

4. Run the test script as follows:

   perl  scripts/xref_mgr_pix.pl 10515 <log level>

<log level> is a value between 1 and 4.

5. The test script will send three A04 registration messages to your system and one A04 merge message. After the four ADT messages, the test script sends one PIX query. The query supplies the patient ID for WASHINGTON in domain 2 and wants the ID in domain 1. We expect the answer is the ID that was originally associated with LINCOLN in domain 1.

Evaluation

To evaluate your response to this test:

The evaluation script is not complete. Examine the HL7 message response in 10515/120/test/1000.hl7. That is the response message captured from your system. It should contain the identifier for LINCOLN in domain 1. You can see the MESA response in 10515/120/mesa/1000.hl7.

Enter a note in the Kudu tool indicating you have successfully run the test. If you do not agree with the test, results or interpretation, send a note to Steve Moore to help him understand the issue.

Test Case 10531: PIX Update Notification: MESA 1

Test case 10531 covers a use case involving the PIX Update Notification transaction and behavior of the Cross-reference Manager.

References

ITI TF-2: 3.10

Instructions

Evaluation

Supplemental Information

Test Case 10532: PIX Update Notification: MESA 2

Test case 10532 covers a use case involving the PIX Update Notification transaction and behavior of the Cross-reference Manager.

References

ITI TF-2: 3.10

Instructions

Evaluation

Supplemental Information

Test Case 10533: PIX Update Notification: MESA 3

Test case 10533 covers a use case involving the PIX Update Notification transaction and behavior of the Cross-reference Manager.

References

ITI TF-2: 3.10

Instructions

Evaluation

Supplemental Information

Test Case 10541: PIX Integrated Test 1

Test case 10541 covers a use case with several PIX transactions integrated into a larger test.

References

ITI TF-2: 3.10

Instructions

Evaluation

Supplemental Information

Test Case 10542: PIX Integrated Test 2

Test case 10542 covers a use case with several PIX transactions integrated into a larger test.

References

ITI TF-2: 3.10

Instructions

Evaluation

Supplemental Information

Test Case 10543: PIX Integrated Test 3

Test case 10543 covers a use case with several PIX transactions integrated into a larger test.

References

ITI TF-2: 3.10

Instructions

Evaluation

Supplemental Information

3 Test Cases: PSA

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.

4 Test Cases: CT

This section describes test cases that are generally associated with the CT component. There may be some overlap with other profiles.