Pre-connectathon testing for systems implementing the PAM (Patient Administration Management) integration profile are perfomed against the Patient Manager simulator available at http://gazelle.ihe.net/PatientManager
Before starting your tests, please set up properly your system and/or give the correct information to the simulator in order to enable it to access your system under test. We also strongly recommend to read the documentation located at http://gazelle.ihe.net/content/patient-manager-user-manual
Read the configuration parameters of the Patient Demographic Consumer part of the simulator and configure your system to send messages to this part of the simulator. You will find this information following the menu: Patient Identification Management/Patient Demographic Consumer/Configuration and messages. Be careful to select the right character encoding before checking the receiving port.
The messages you will send to the simulator will also be available on that page.
The pre-connectathon test dedicated to your system is located here.
Register your system under test into the Gazelle simulator following the menu SUT Configurations, then click on "Create a configuration". Select the SUT actor as "PDC" and select the encoding character set expected by your SUT otherwise your system will not be able to decode the messages. Make sure your system is available from the Internet and no firewall prevents Gazelle to access your tool.
The pre-connectathon test dedicated to your system is located here.
Read the configuration parameters of the Patient Encounter Consumer part of the simulator and configure your system to send messages to this part of the simulator. You will find this information by following the menu: Patient Encounter Management/Patient Encounter Consumer/Configuration and messages. Be carreful to select the right character encoding before checking the receiving port.
The messages you will send to the simulator will also be available on that page.
The pre-connectathon test dedicated to your system is located here.
Register your system under test into the Gazelle simulator following the menu SUT Configurations, then click on "Create a configuration". Select the SUT actor as "PEC" and select the right encoding character set otherwise you may receive messages your system will not be able to decode. Make sure your system is available from the Internet and no firewall prevents Gazelle to access your tool.
The pre-connectathon test dedicated to your system is located here.
This test will be performed against the PAMSimulator tool. The goal of this test is to check the capability of your system to send/receive the messages defined within the ITI-31 (Patient Encounter Management) transaction. This test is only dealing with the basic set of trigger events defined for ITI-31, that means Patient admisssion, registration, discharge and the relative cancellation.
You will retrieve the patients the simulator has sent or received under the "All patients" menu; for each patient, the list of relative encounters is available under the tab entitled "Patient's encounters". You may want to use the filter to facilitate your search. If you are using the simulator as a PES, you can log onto the application using the CAS mechanism (use your Gazelle credentials) and easily retrieve the patients you have created within the application by checking the "see only patients created by me" checkbox. If you use the simulator as a PEC, the creator of the patients/encounters received by the simulator is the sending facility_sending application of your system under test. Once you have found the right patient, click on the magnifying glass you will get the permanent link to this patient; copy and paste it into the comment box of your pre-connectathon test instance.
Before starting your test, please read the instructions at http://gazelle.ihe.net/content/pre-connectathon-tests/pam
This test requires three patients we will name Patient1, Patient2 and Patient3. According the PAM profile, there is no need for the consumer to be aware of these patients before receiving encounter notifications for them.
This test is divided into two parts:
You will use the PAM Simulator as a Patient Encounter Consumer. Go to the Patient Encounter/Management/Patient Encounter Consumer page in order to retrieve the configuration (IP address, port, receiving facility/application) of the simulator.
1. Admit patient
2. Register patient
3. Cancel admission
4. Discharge patient
5. Cancel discharge
In order to help the connectathon manager with checking this test, go to "All patients" page and retrieve Patient1, Patient2, Patient3. For each of those patients, copy the permanent link and paste it in Gazelle Test Management.
You will use the PAM Simulator as a Patient Encounter Supplier. You may want to log onto the application to easily retrieve the patients/encounter you will create. Go to the Patient Encounter Management/Patient Encounter Supplier page.
1. Admit patient
In this step, you are going to create Patient1 and Patient2 and to admit them as inpatients.
2. Register patient
In this step, you are expected to create Patient3 and to register them as outpatient.
3. Cancel admission
In this step, you are expected to cancel the admission of Patient1.
4. Discharge patient
In this step, you are expected to discharge Patient2.
5. Cancel discharge
In this step, your are expected to cancel the discharge of Patient2
In order to help the connectathon manager with checking this test, go to "All patients" page and retrieve Patient1, Patient2, Patient3. For each of those patients, copy the permanent link and paste it in Gazelle Test Management.
The aim of this pre-connectathon test is to check your system under test is able to receive/send the messages exchanged within the ITI-30 (Patient Identification Management) transaction. Here, we are testing your capability to create a new patient, update his/her demographics and identifiers and, depending of the set of options you support, to merge and/or link patient demographic information.
Both actors (Patient Demographic Consumer and Patient Demographic Supplier) will be asked to test against the PAM Simulator. For each step of this test, you are expected to provide the permanent link to the patient sent or received by the simulator and the permanent link to the test report.
You will retrieve the patients the simulator has sent or received under the "All patients" menu. You may want to use the filter to facilitate your search. If you are using the simulator as a PDS or PES, you can log onto the application using the CAS mechanism (use your Gazelle credentials) and easily retrieve the patients you have created within the application by checking the "see only patients created by me" checkbox. If you use the simulator as a PDC or PEC, the creator of the patients received by the simulator is the sending facility_sending application of your system under test. Once you have found the right patient, click on the magnifying glass you will get the permanent link to this patient; copy and paste it into the comment box of your pre-connectathon test instance.
The test report is also available through a permanent link. Go to the "HL7 Messages" page and select the message related to the current step, you will be the link to the test report.
Before starting your test, please read the instructions at http://gazelle.ihe.net/content/pre-connectathon-tests/pam
Test definition for Patient Demographic Consumer actor
Test definition for Patient Demographic Supplier actor
You will use the PAM Simulator as a Patient Demographic Supplier. You may want to log onto the application to easily retrieve the patients you will create. You will have to switch among the pages available under the Patient Identification Management/Patient Demographic Supplier menus.
1. Patient creation
In this step, you are expected to send to your simulator two new patients (ADT^A28^ADT_A05 messages). Go to Patient Identification Management/Patient Demographic Supplier/Create new Patient.
2. Update patient information
In this step, you are expected to update the first name of Patient1 and send the notification to your system under test. Go to Patient Identification Management/Patient Demographic Supplier/ Update patient information.
3. Change patient's identifier list
In this step, you are expected to change one of the identifiers of Patient1. Go to Patient Identification Management/Patient Demographic Suppliser/Change patient identifier list.
4. Merge patients (if option supported by your SUT)
In this step, you will reuse Patient1 and Patient2 and merge them. Go to Patient Identification Management/Patient Demographic Supplier/Merge patients.
5. Link patients (if option supported by your SUT)
In this step, you will reuse Patient1 and Patient2 and merge them. If your SUT supports both merge and link options and if you have already performed step4; please create a third patient to replace Patient2 in this test. Go to Patient Identification Management/Patient Demographic Supplier/Link Unlink patients.
You will use the PAM Simulator as a Patient Demographic Consumer. The creator of the patients you will send to the simulator will be set up from the sending facility and application values contained in the received HL7 messages. The configuration of this part of the simulator is available under Patient Identification Management/Patient Demographic Consumer/Configuration and messages.
1. Patient creation
2. Update patient information
3. Change patient's identifier list
4. Merge patients (if option supported by your SUT)
5. Link patients (if option supported by your SUT)
This test deals with the subset of trigger events defined for the Inpatient/Outpatient Encounter Management option of ITI-31 transaction. As a reminder, here is the list of events your system must support to fulfill the requirements of this option:
This test is written for both Patient Encounter Supplier and Patient Encounter Consumer, refer to the right section according the actors your system under test supports.
In this test, we check the capability of your system under test to send messages for notifying the PEC actor of new events. You are asked to test against the PAMSimulator. Your first task is to configured your system under test to tell it to send the messages to the PAMSimulator. To do so, retrieve the configuration of the PEC part of the simulator under Patient Encounter Management/Patient Encounter Consumer/Configuration. Do not forgot to select the right character encoding before specifying the port to your system.
In this first step, you will feed the PAMSimulator with a new patient and encounter.
Once the patient is admitted, we will transfer him/her to a new bed.
In this step, we will change the patient class to outpatient.
In this step, we will change back the patient class to inpatient
This last step is used to check the ability of your system to send a pre-admission notification and its cancellation
In this step, we check the capability of your system under test to act as a Patient Encounter Consumer for the PAM profile, and for the Inpatient/Outpatient Encounter Management option in particular. We want you to demonstrate that your system is able to integrate the notifications received from the PAM Simulator and to correctly acknowledge them.
In this step, we will transfer the patient to a new bed.
This step is used to change the patient class to outpatient (code = O)
This step is used to change the patient class to inpatient (code = I)
In this step, we test the capability of your system to pre-admit a patient and to cancel this pre-admission.
This tests the ability of your application to receive an ITI-10 PIX update notification message. This applies only to PIX Consumers that support the PIX Update Notification option.
This test is performed with the Patient Manager simulator http://gazelle.ihe.net/PatientManager sending ITI-10 messages to your system under test.
Tool documentation is located at http://gazelle.ihe.net/content/patient-manager-user-manual
In these steps, you will use the Patietn Manager tool to send a PIX update notification to your application.
The screen shots demonstrate that you have successfully processed the received message(s).
This test applies to Patient Demographic Consumers in the PDQ or PDQv3 Profiles.
This test is performed with the Patient Manager simulator http://gazelle.ihe.net/PatientManager acting as a Patient Demographic Supplier responding to these queries. Note that the test steps are the same no matter the transaction...you will choose the transaction(s) supported by your Consumer.
Tool documentation is located at http://gazelle.ihe.net/content/patient-manager-user-manual
In these steps, you will use the Patient Manager as a Patient Demographics Supplier (PDS) Simulator to respond to your PDQ Query.
The permanent link captures the message exchange. The screen shot demonstrates that you have successfully processed the received query response(s).
This test applies to Patient Demographics Suppliers in the PDQ or PDQv3 Profiles.
This test is performed with the Patient Manager simulator http://gazelle.ihe.net/PatientManager acting as a Patient Demographic Consumer to initiate these queries. Note that the test steps are the same no matter the transaction...you will choose the transaction(s) supported by your Supplier.
Tool documentation is located at http://gazelle.ihe.net/content/patient-manager-user-manual
In these steps, you will use the Patient Manager as a Patient Demographic Consumer (PDC) Simulator to initiate a PDQ Query to your Supplier.
The permanent link captures the message exchange. The screen shots demonstrate that you have successfully processed the received message(s).
This test applies to initiators of the [ITI-78] Patient Demographics Query for Mobile transaction: Patient Demographics Consumers in the PDQm or PMIR Profiles.
This test is performed with the Patient Manager simulator https://gazelle.ihe.net/PatientManager acting as a Patient Demographic Supplier to response to PDQm queries.
The list of patients available on the supplier side are available under the Patients menu. Select "simulated actor" = "PDS" to see which one can be returned in a PDQm query response.
The endpoint to contact is available under menu PDQ* > Patient Demographics Supplier> FHIR configuration.
Verify the conformance of each query issued by your system (blue play icon in the "query" column) and copy the permanent link to the message in your pre-connectathon test in Gazelle Test Management (available from the magnifying glass icon).
The messages received by the simulator are available under HL7 Messages. To restrict the search, either access the page using the "history" icon on the FHIR Configuration page, either sent the following filters in the search criteria panel:
Not all the following test cases might be of relevance for your system under test. The purpose of this test is to make sure you correctly implement the portions of the specifications which are of interest for your system (based on the use cases it supports).
For this first step, we assume that the operator wants to retrieve a list of patients based on some demographics traits. You might want to repeat this step with various combinations of parameters among the following ones to see how the supplier understand your query:
For each query, your system should at least display the number of retrieved entries and some of the demographic traits for each entry in the list.
Note that queries with no search parameter will return no entry at all.
If your system supports both JSON and XML encoding, repeat at least once of the previous query with the second encoding so that you can verify that your system correctly set the requested encoded. You might use the HTTP header or the _format query parameter.
In addition to the query feature, your system shall support the retrieve patient feature. Choose one patient out of the list and directly retrieve the associated resource by performing the retrieve operation.
Example: https://gazelle.ihe.net/PatientManager/fhir/Patient/UUID.
Send a new query to your system under test, make sure the query parameters do not match any patient in the tool. Your system is expected to inform the final user that no match has been found.
You must execute the steps below if your system is able to constrain the domains from which patient identifiers are returned from the Patient Demographics Supplier.
If you can turn off the domain restriction in your system. First, choose a combination of parameters that will return at least one patient with identifiers in several domains. Under the Connectathon > Patient Demographics menu, you will find the patients that will be pre-loaded by suppliers during the Connectathon; they are also known by the Patient Demographics Supplier implemented in the tool. Each patient has an identifier in at least four domains.
Your system shall receive the patient(s) with identifiers in the IHEBLUE, IHEFACILITY, IHEREF and IHEGREEN domains at least.
Reuse the same query parameters as for the previous test but restrict the domain to the IHEBLUE (urn:oid:1.3.6.1.4.1.21367.13.20.3000) domain.
If your query is correctly formatted, the returned patient(s) should only have identifiers with system = urn:oid:1.3.6.1.4.1.21367.13.20.3000.
If your system supports more than one domain, repeat the operation above: constraint the identification domain to IHEBLUE and IHERED (urn:oid:urn:oid:1.3.6.1.4.1.21367.13.20.1000).
Once again, if your query is correctly formatted, the returned patient(s) should only have identifiers with system urn:oid:1.3.6.1.4.1.21367.13.20.3000 and urn:oid:1.3.6.1.4.1.21367.13.20.1000.
Reuse the same query parameters once again and restrict the domain to urn:oid:1.3.6.1.4.1.21367.13.20.9999999. This domain is unknown from the Patient Demographics Supplier.
If your query is correctly formatted, you should receive HTTP 404 error code with an OperationOutcome resource in which the unknown domain is precised. You might or might not give feedback on such error to the final user. No entry shall be displayed to the user (none will be returned by the Patient Demographics Supplier).
Execute this step if your system supports the paging mechanism, meaning that it can add the _count parameter to the query. In this step we assume that the user is able to set the number of records to fetch at one time. If your system does not provide this ability (default quantity, or quantity to choose from a list), simply adapt the test data below.
Set search parameters in a way that they will select at least 3 entries (usually given=rob is a good candidate) and ask for only two records at a time. If your query is correctly formatted, the received Bundle should contain only 2 entries and
Ask for the next batch of results. You should be able to see at least one more patient.
This test applies to responders to the [ITI-78] Patient Demographics Query for Moblie transaction: Patient Demographics Suppliers in the PDQm Profile or Patient Identity Registry in the PMIR Profiles
This test is performed with the Patient Manager simulator https://gazelle.ihe.net/PatientManager acting as a Patient Demographic Consumer to initiate these queries.
There is no prerequisite in terms of data to be load into your system. As such, choose relevant values for the various parameters based on the patient demographics known by your system under test so that matches are returned.
First of all, register your system under test within the tool as a FHIR Responder under SUT Configurations > FHIR Responders. Make sure to select IHE => ITI-78 (PDQm Consumer) in the list of usages.
Access the Patient Demographics Consumer for PDQm in Patient Manager from menu PDQ* > Patient Demographics Consumer > [ITI-78] Patient Demographics Query FHIR.
Verify the conformance of each response issued by your system (blue play icon in the "response" column) and copy the permanent link to the message in your pre-connectathon test in Gazelle Test Management (available from the magnifying glass icon). Also verify that the response format expected in the query matches the response format (XML vs JSON) returned by your system.
Upload the capability statement of your system (showing at least the PDQm Supplier features) in the pre-connectathon test in Gazelle Test Management.
For this first step, we assume that the consumer actor wants to retrieve a list of patients based on some demographics traits. You might want to repeat this step with various combinations of parameters among the following ones to test the behavior of your system:
Note that for parameters of type string, "exact" modifier will be added to the query if the wildcard is not used in the field (when valued). If you want to search of patients with a given starting with Ro, enter Ro* in the form.
If your system supports the Pediatric Demographics Option, you might also want to make sure that your system supports the mothersMaidenName search extension.
For this step, you are asked not to modify the default parameters in the "Additional information" section of the page.
Once you have flll out the form, push the "Send message" button. If matches are returned by your system, they will be displayed at the bottom of the page.
After you have retrieved a first batch of patients. You should also be able to use the resource ID search parameter (_id). You can find the value to use in the response returned by your system in Bundle.entry.resource.Patient.id.value.
Your system under test shall be able to support at least both JSON and XML encodings. Previous step has been executed using "XML" as format to be returned. Return the step above at least one but select Response format = json before sending the message to your system.
Access the detail of the response content and for one of the entries, access the URL displayed in field entry.fullUrl.value. You should retrieve the content of the Patient resource.
Send a new query to your system under test, make sure the query parameters do not match any patient in your database. Your system is expected to send back a Bundle resource with Bundle.total.value = 0.
In this step, we focus on the domain restriction feature. We assume that your system manages at least one domain for patient identification.
First, choose a combination of parameters that will return at least one patient. If your system supports multiple identifier domains, make sure the returned patients will show at least identifiers from two different domains. DO NOT restrict the search to a particular domain. We are interested in knowing what are the identifiers known for this patient.
Repeat the search below but in the "Additional information" section, add the identifier of one of the domains for which the returned patient has a PID assigned. Click on "Add domain to list" for the tool to take the value into account.
Your system is expected to return the patients that are a PID assigned to this domain, only one PID shall appear for each of them.
If your system supports more than one domain, repeat the operation above to add a second domain in the list of domains that are returned.
Once again, your system is expected to return the patients with PID in the mentioned domains. No other PID shall be returned.
Repeat the test but first clean up the list of domains to return and add "1.3.6.1.4.1.21367.13.20.9999" instead (this domain might not be known by your system, otherwise choose another value).
No entry shall be returned. Refer to section 3.78.4.1.3 / Case 4 for details on the expected response (Code HTTP 404 with OperationOutcome or HTTP 200 with no content).
The Patient Demographics Supplier shall represent the incremental responses as specified in FHIR Paging.
Empty the query form and enter parameters that will allow your system to match more than two patients.
In the "Additional information" section, check the box for option "Limit number of responses" and set the limit value to "1".
Click on "Send message", the tool shall display the single entry that is returned by your system and the following message "More results are available on supplier side". As for the other steps, copy the link to this message in Gazelle Test Management.
Click on "Get next results".
In the "Returned patients" section, the number of pages increases. A single patient is displayed.
This test applies to Patient Identity Consumers who initiate queries in the PIX, PIXv3, PIXm, or PMIR Profiles.
This test is performed with the Patient Manager simulator http://gazelle.ihe.net/PatientManager acting as a Patient Identity Cross-Reference Manager (PIX Manager) responding to these queries. Note that the test steps are the same no matter the transaction...you will choose the transaction(s) supported by your Consumer.
Tool documentation is located at http://gazelle.ihe.net/content/patient-manager-user-manual
In these steps, you will use the Patient Manager as a PIX Manager Simulator to respond to your PIX Query.
The permanent link captures the message exchange. The screen shot demonstrates that you have successfully processed the received query response(s).
This test applies to Patient Identifier Cross-Reference Managers (PIX Managers) in the PIX, PIXv3, PIXm, or PMIR Profiles.
This test is performed with the Patient Manager simulator http://gazelle.ihe.net/PatientManager acting as a PIX Consumer to initiate these queries. Note that the test steps are the same no matter the transaction...you will choose the transaction(s) supported by your Supplier.
Tool documentation is located at http://gazelle.ihe.net/content/patient-manager-user-manual
In these steps, you will use the Patient Manager as a PIX Consumer Simulator to initiate a PIX Query to your PIX Manager
The permanent link captures the message exchange.
This tests the ability of your application to receive RAD-1 and RAD-12 patient registration and update messages.
This test is performed with the Patient Manager simulator http://gazelle.ihe.net/PatientManager sending messages to your system under test.
Tools documentation is located at http://gazelle.ihe.net/content/patient-manager-user-manual
Before starting your tests, please configure the tool to send to your appliction using the SUT Configurations menu in the tool.
1. Patient creation
In this step, you are expected to send a new patient to your application .
2. Update patient information
In this step, you are expected to update the first name of the new and send the notification to your system under test.
The screen shots demonstrate that you have successfully handled the received ADT messages.
This test applies to the XCPD Initiating Gateway actot that supports the Deferred Response Opiton. See ITI TF-1: 27.2.2 and ITI TF-2b: 3.55.6.2.
This test is performed with the Gazelle Patient Manager simulator: https://gazelle.ihe.net/PatientManager
See also the User Manual for testing XCPD with the Patient Manager here.
The instructions for this test are detailed in the User Manual for the Patient Manager tool, so they are not repeated here. See: https://gazelle.ihe.net/gazelle-documentation/Patient-Manager/user.html#deferred-response-on-initiating-gateway
After you perform the test, the Patient Manager tool will produce a Test Report. Copy the Permanent Link to to Test Report, then paste that link into Gazelle Test Management as the results for this test.
The basline requirements of the XCPD profile do not require the actors to also implement XUA; however, this test enables you to test your XCPD Initiating Gateway actor that also support XUA X-Service User
This test is performed with the Gazelle Patient Manager simulator: https://gazelle.ihe.net/PatientManager
See also the User Manual for testing XCPD with the Patient Manager here.
The instructions for this test are detailed in the User Manual for the Patient Manager tool, so they are not repeated here. See the instructions for XUA over XCPD for the X-Service User here: https://gazelle.ihe.net/gazelle-documentation/Patient-Manager/user.html#xua-over-xcpd
After you perform the test, find your result in the Patient Manager tool under menu XUA > X-Service User logs. Copy. the URL for your result and paste it into Gazelle Test Management as the result for this test.
This test applies to the XCPD Responding Gateway actot that supports the Deferred Response Opiton. See ITI TF-1: 27.2.2 and ITI TF-2b: 3.55.6.2.
This test is performed with the Gazelle Patient Manager simulator: https://gazelle.ihe.net/PatientManager
See also the User Manual for testing XCPD with the Patient Manager here.
The instructions for this test are detailed in the User Manual for the Patient Manager tool, so they are not repeated here. See: https://gazelle.ihe.net/gazelle-documentation/Patient-Manager/user.html#deferred-response-on-responding-gateway
After you perform the test, the Patient Manager tool will produce a Test Report. Copy the Permanent Link to to Test Report, then paste that link into Gazelle Test Management as the results for this test.
The baseline requirements of the XCPD profile do not require the actors to also implement XUA; however, this test enables you to test your XCPD Responding Gateway actor that also support XUA X-Service Provider
This test is performed with the Gazelle Patient Manager simulator: https://gazelle.ihe.net/PatientManager
See also the User Manual for testing XCPD with the Patient Manager here.
The instructions for this test are detailed in the User Manual for the Patient Manager tool, so they are not repeated here. See the instructions for XUA over XCPD for the X-Service Provider here: https://gazelle.ihe.net/gazelle-documentation/Patient-Manager/user.html#xua-over-xcpd
After you perform the test, find your result in the Patient Manager tool under menu XUA > X-Service Provider logs. Copy. the URL for your result and paste it into Gazelle Test Management as the result for this test.