Integrating the Healthcare Enterprise
IHE/MESA Patient Encounter Source 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 9.10.1
13-March-2006
Patient Encounter Source
Introduction
Patient Identification
Configuration
Starting the MESA Servers
Installation Test
Test Software Environment
Submission of Results
Test Cases PAM
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 tests described in this document rely on patient demographics supplied as part of the test procedure. This document is intended for the Patient Encounter Source; therefore the tests assume the source is responsible for supplying an identifier for each test patient.
The MESA scripts are run from the directory $MESA_TARGET/mesa_tests/iti/actors/pat_encounter_src.
The ASCII configuration file pat_encounter_src.cfg contains parameters that describe your system and the test environment. If the Patient Encounter Source is not grouped with a Patient Demographics Source and needs to receive patient demographic information, the following parameters are used to tell the MESA software where to send those messages:
Variable Name |
Default Value |
TEST_PES_HOST_HL7 |
pat_encounter_src |
TEST_PES_PORT_HL7 |
3900 |
MESA servers are started from a DOS/CMD window or a terminal emulator. Follow these steps for Unix systems
To stop the servers:
scripts/stop_mesa_servers.cshThe start instructions for MESA tools on a Windows system are:
To stop the 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 PAM Integration Profile. There may be some overlap with other profiles.
Test 12120: PAM Admit/Discharge PatientIn test 12120, the Patient Encounter Source is required to send two messages to first admit and then discharge a patient. The test script allows the Patient Encounter Source to receive demographic information from the MESA system (that is, a standalone Encounter Source) or to use demographic information if grouped with a Patient Demographic Source. ReferenceITI TF InstructionsTo run this test, follow these steps using a DOS window or terminal emulator:
perl scripts/pat_encounter_src.pl 12120 <log level>
Evaluation
perl 12120/eval_12120.pl <log level> Patient Demographics for Test 12120
|
In test 12121, the Patient Encounter Source is required to send one messages to register a patient as an outpatient. The test script allows the Patient Encounter Source to receive demographic information from the MESA system (that is, a standalone Encounter Source) or to use demographic information if grouped with a Patient Demographic Source.
Segment / Field |
Element Name |
Value |
PID.3.4 |
(Patient ID) Assigning Authority |
&1.3.6.1.4.1.21367.2005.1.1&ISO |
PID.3.5 |
(Patient ID) Identifier Type Code |
PI |
PID.5 |
Patient Name |
SMITH^AMBER |
PID.7 |
Date/Time of Birth |
19791130 |
PID.8 |
Administrative Sex |
M |
PID.11 |
Patient Address |
17 OCEAN^^WEBSTER^MO^63119 |
PV1 |
Patient Class |
N |
ITI TF
To run this test, follow these steps using a DOS window or terminal emulator:
perl scripts/pat_encounter_src.pl 12121 <log level>
where <log level> is a value between 1 (low) and 4 (high).
perl 12121/eval_12121.pl <log level>