Login, Gateway Status, Account Management and Exchange Management
Version# | Date | Modified By | Description of Modification |
---|---|---|---|
0.1 | 10/01/2014 | Sovann Huynh | Initial version |
0.2 | 01/23/2015 | Christopher May | Added Ping Utility tests |
0.3 | 06/11/2015 | Sailaja Adusumilli | Adding Test Tool tests |
0.4 | 11/02/2018 | Tabassum Jafri | Updated Cross-Gateway Query Client and User Accounts section |
Overview
Important note regarding UDDIConnectionInfo.xml and internalConnectionInfo.xml
As of CONNECT 5.1, both files have been replaced with the more versatile exchangeInfo.xml and internalExchangeInfo.xml files. For users of CONNECT 5.0 and earlier versions, substitute references to these new files with the original uddiConnectionInfo.xml and internalConnectionInfo.xml files
The following test steps are for the CONNECT AdminGUI interface functionality, not including the Direct-related components. It is divided into three sections – Login, Gateway Status and Account Management:
- Login - Verification of login procedure from the main page.
- Gateway Status - Verification of the metrics pertaining to gateway health. Includes three tabs:
- Dashboard - displays system data pertinent to the CONNECT instance.
- Performance Statistics - displays the total number of inbound, outbound and error messages currently associated with the CONNECT instance.
- Remote Gateway List - lists all the gateways that the CONNECT instance has been communicating with and displays the total inter-gateway transaction count by service.
- Account Management - Verification of user account management functionality. including the functionality to add/edit user accounts and set user roles:
- User Accounts - allows for creation and management of user accounts
- Manage Roles - allows for modification of access rights for each of the three supported user roles: administrator, user, super user
- Services Test Tool
Test preparation
- Deploy CONNECT with Direct ear and AdminGUI war. Note: Direct needs to be included in the ear in order to use these test cases.
- Successfully execute ConnectValidation SoapUI Test suites before running AdminGUI test cases.
- Browse to http://localhost:8080/CONNECTAdminGUI (depending on your application server and deployment settings, you may need to append the version to the link, e.g., -4.4.0-SNAPSHOT)
Test flow
These tests are intended to be run sequentially, as successful completion of some test steps will require the successful completion of previous test steps
Login
Test scenario | Test steps | Expected results |
---|---|---|
User attempts to log in with no password | Log in with username CONNECT and leave password field blank | User is not logged in and "Password is required" message appears |
User attempts to log in with invalid username | Log in with username CONNECT and password password | User is not logged in and "The user name or password entered is incorrect" message appears |
User attempts to log in with invalid password | Log in with username CONNECTAdmin and password changeme | User is not logged in and "The user name or password entered is incorrect" message appears |
User logs in with valid username and password | Log in with username CONNECTAdmin and password password | User is logged into CONNECT AdminGUI and Gateway Status Dashboard appears |
User logs out | Hover cursor over the "Logged in as ..." box near the upper left corner and select Log out | User is logged out and returned the the "Please sign in" page |
Log back in to continue testing
All test steps below require tester to be logged in to the CONNECT AdminGUI interface
Gateway Status
Gateway Monitor (Dashboard)
Expand the Gateway Status menu in the left navigation panel, select Dashboard and execute the following tests:
Test scenario | Test steps | Expected results |
---|---|---|
Verify that the page is populated with real gateway metrics | Visually inspect the gateway metrics | - OS data is displayed - JAVA version data is displayed - Memory data is displayed - Total inbound data is displayed - Total outbound data is displayed - App Server data is displayed |
Verify that all available services have been listed | Visually inspect the left-hand column under Services | All services available to the gateway are listed (including versions) |
Verify that the charts are accurate |
| Each time a test is executed, the chart is updated accordingly |
Account Management
User Accounts
Expand the Account Management menu in the left navigation panel, select User Accounts and execute the following tests:
Test scenario | Test steps | Expected results |
---|---|---|
Verify password strength indicator |
| After the completion of each step, you should see the strength indicator go up |
Create a User account |
| In the userlogin table in the adminguidb database, there is an entry for user connect2 with a userRole value of 3. Log off and log in with the connect2. Go to Cross-Gateway Query client and do a Patient search. Go to server logs and verify that EntityPatientDiscovery request has the following assertions: <ns3:userInfo> |
Create a Super User account |
| In the userlogin table in the adminguidb database, there is an entry for user connect3 with a userRole value of 2 |
Test Validation |
| An error message should appear alerting the user that required fields were not entered. |
Manage Roles
Select Manage Roles in the left navigation panel and execute the following tests:
Test scenario | Test steps | Expected results |
---|---|---|
Edit Direct Config access for all users |
|
|
Verify Administrator privileges |
| Domains page should not render |
Verify User privileges |
| Domains page should not render |
Verify Super User privileges |
| Domains page should not render |
View Users and Delete User
Test scenario | Test steps | Expected results |
---|---|---|
Verify that users are displayed. |
| Values should match in GUI table and in database. |
Verify delete. |
| After creating user, should appear in database and on GUI. After delete the user should not be in table and can not log in with deleted user. |
Verify can't delete CONNECTAdmin |
| Should see warning message that CONNECTAdmin can not be deleted. |
Verify can't delete current user. |
| Should see warning on delete that you can't delete current user. |
Exchange Management
Expand the Exchange Management menu in the left navigation panel and execute the following tests:
Test scenario | Test steps | Expected results |
---|---|---|
Change the refresh interval and maximum number of backups |
| In exchangeInfo.xml: <refreshInterval>1441</refreshInterval> |
Refresh exchanges (manual exchange insertion) | In exchangeInfo.xml, add the following exchange: <exchange type="fhir"> In SoapUI,start the xmlExchange mock FHIR directory In the Exchange Manager, click "Refresh Exchanges" | exchangeInfo.xml has been udpated with Exchange 2 data |
Change default exchange |
| In exchangeInfo.xml: <defaultExchange>Exchange 2</defaultExchange> |
Delete an exchange |
| Exchange 2 has been deleted from exchangeInfo.xml |
Refresh exchanges (using Exchange Manager to add an exchange) |
| exchangeInfo.xml has been udpated with Exchange 2 data |
Disable refresh for Exchange 2 | Click the "Enabled" button for Exchange 2 | In exchangeInfo.xml, for Exchange 2: <disabled>true</disabled> |
Enable refresh for Exchange 2 | Click the "Disabled" button for Exchange 2 | In exchangeInfo.xml, for Exchange 2: <disabled>false</disabled> |
View and ping external endpoints | In the Organizations accordion:
| Ping status is PASS for all services |
Cross-Gateway Query Client
Overview
The Service Test Tool in the System Administrative GUI application provides the ability to patient search, query for documents within a given date range based on document type, and to view documents for selected patients interactively using a web browser. This currently only works in a passthrough gateway setting.
Test Preparation
- The Service Test Tool tests are designed to run using two separate gateways but additional configurations allow for loopback processing. The assumption is that the initiating and responding gateway will have HCID 1.1 and 2.2, respectively. Based on that, set the following prerequisites:
- Setup for Initiating and Responding Gateway:
- For CONNECT 5.2
- Setup for Initiating and Responding Gateway:
Prerequisite
Create User: In the System Administrative GUI, navigate to Account Management > User Accounts and create a new user. Note: Before doing a Patient search, you need to be logged in with the newly created user.
Note: Cross-Gateway Query Client now works in both standard and passthrough mode and creates SAML assertion based on logged in user's credentials. No special configuration is required, to run Cross-Gateway Query Client, except the normal gateway to gateway setup which is described below:
- Initiating Gateway Setup
- exchangeInfo.xml
- Add an entry for HCID 2.2, updating endpoints to use the hostname or IP address of the responding gateway
- exchangeInfo.xml
- Responding Gateway Setup
- gateway.properties
- In the System Administrative GUI, navigate to Properties > Gateway and update the entry for the HCID to 2.2
- internalExchangeInfo.xml
- Add or update the entry for the HCID 2.2
- adapter.properties
- In the System Administrative GUI, navigate to Properties > Adapter and update the entry for the HCID to 2.2
- exchangeInfo.xml
- Update the endpoints for HCID 1.1 to use the hostname or IP address of the initiating gateway. NOTE: This is actually not necessary as there will be no tests from 2.2 to 1.1.
- gateway.properties
- Initiating Gateway Setup
- For Prior Versions
- Initiating Gateway Setup
- gateway.properties
- Set all services to passthrough mode
- exchangeInfo.xml or uddiConnectionInfo (depending on CONNECT 5.1.2 or prior version)
- Add an entry for HCID 2.2, updating endpoints to use the hostname or IP address of the responding gateway
- gateway.properties
- Responding Gateway Setup
- gateway.properties
- In the System Administrative GUI, navigate to Properties > Gateway and update the entry for the HCID to 2.2
- Patient Discovery must be set to standard mode, Document Query and Document Retrieve must be set to passthrough mode
- internalExchangeInfo.xml or internalConnectionInfo (depending on CONNECT 5.1.2 or prior version)
- Add or update the entry for the HCID 2.2
- adapter.properties
- In the System Administrative GUI, navigate to Properties > Adapter and update the entry for the HCID to 2.2
- exchangeInfo.xml or uddiConnectionInfo (depending on CONNECT 5.1.2 or prior version)
- Update the endpoints for HCID 1.1 to use the hostname or IP address of the initiating gateway. NOTE: This is actually not necessary as there will be no tests from 2.2 to 1.1.
- Set <alias alias="adapterpolicyengineorchestrator" name="adapterpolicyengineorchestratorjava" />
- Make sure to use orchestartorjava instad of samlJava in PolicyEngineProxyConfig.xml. (when samljava impl is used it makes check on assertion objects most and java impl makes check on few)
- gateway.properties
- Initiating Gateway Setup
- Certificates must be exchanged and trusted between the two gateways per the instructions found here: https://connectopensource.atlassian.net/wiki/x/8wCD
- In order to test Patient Discovery, Document Query, and Document Retrieve from a single gateway, make sure that the patient test data exists in the mpi.xml file.
- At least one document must exist in the database table docrepository.document for the test patient. This record should already be present if you ran the populateTestData.sql script from the Product\DBScripts\nhincdb directory.
- Deploy the CONNECT ear and AdminGUI war.
- Successfully execute the ConnectValidation SoapUI test suites before running AdminGUI test cases.
- Browse to http://localhost:8080/CONNECTAdminGUI (depending on your application server and deployment settings, you may need to append the version to the link, e.g., -4.5.0-SNAPSHOT)
Loopback Mode
With CONNECT 5.2
- adapter.properties
- In the System Administrative GUI, navigate to Properties > Gateway and update the entry for the HCID to 2.2. Note: you need to restart the server after this change.
Prior to CONNECT 5.2
- Set Patient Discovery to standard mode
- Set Document Query and Document Retrieve to passthrough mode
- PolicyEngineProxyConfig.xml changes:
- Set <alias alias="adapterpolicyengineorchestrator" name="adapterpolicyengineorchestratorjava" />
- AdapterMpiConfig.xml changes:
- Set <alias alias="mpichecker" name="mpidbjava" /> if attempting to match patients in the patients database
- Set <alias alias="mpichecker" name="mpixmljava" /> if attempting to match patients in the mpi.xml file
- PatientCorrelationConfig.xml changes:
- Set <alias alias="patientcorrelation" name="patientcorrelationjava" />
Test flow
These tests are intended to be run sequentially, as successful completion of some test steps will require the successful completion of previous test steps.
Note
Changes had been made for the Patient Search and will required a user with roleCode to build the assertion for the request message; CONNECTAdmin does not have a roleCode for the search to function.
Patient Search
Expand the Universal Client menu in the left navigation panel, select Patient Search and execute the following tests:
Test Scenario | Test Steps | Expected Results |
---|---|---|
Universal Client left navigation menu availability |
| Only "Patient Search" menu item should appear under "Universal Client". |
Patient Search Tab, Document Search Tab availability |
| On the right side of page, under Universal Client, the user will see two tabs: 1. Patient Search 2. Document Search Only the "Patient Search" tab should be enabled; the "Document Search" tab should be disabled. Under "Search Wizard", the "Start Over" and "Enter Patient Search Criteria" options are enabled while the "Enter Document Search Criteria" option is disabled. |
Search for a patient without providing all required values in "Search Wizard" under the Patient Search Tab. |
| A "Required Field" alert will be displayed for fields which are left blank. If all fields are left blank, user will see an error message as below: Organization required. Purpose of Patient/Document Request required. FirstName required. LastName required. DateOfBirth required. Gender required. |
Search for a patient by providing all required values in "Search Wizard" under Patient Search Tab. |
| If a patient is found, below are the expected results:
If a patient is not found, under the "Patient Search" tab, the user will see a "Patient Not Found" message. If the user clicks on the "Clear" button, the "Enter Patient Search Criteria" will be refreshed and the form will be displayed to search for a patient. |
View Patient Search Details |
| User will navigate to the "Document Search" tab. Under "Enter Document Search Criteria", the following details are displayed:
User will be able to navigate between the "Patient Search" and "Document Search" tabs. Under "Search Wizard", "Enter Patient Search Criteria" will be disabled and "Start Over" will be enabled. If the user wants to search for a new patient, a new search can be initiated using "Start Over" from the "Enter Document Search Criteria" option. |
Search for Documents |
| If documents are found, the following will be displayed:
The user will be able to navigate between the "Patient Search" and "Document Search" tabs, and both tabs will retain data which was already entered by the user in the previous test case. |
Search for Document by Document Type |
| If documents are found based on selected document type, a list of documents will be displayed under the "Document Found" table with DocumentID, Document Type, Content Type, Title, Creation Time, Size.
|
Search for Document by Document Creation Date Range |
| If documents are found between selected date range, list of documents will be displayed under "Document Found" table with below information: (DocumentID, Document Type, Content Type, Title, Creation Time, Size)
|
View Document Metadata |
|
|
View Document Details as per document content type display |
|
|