CONNECT Testing Tools

There are many reasons why an organization would need to test. Are you developing tools that marry with the CONNECT Solution? Are you installing a gateway and want to ensure it is functioning correctly? Are you developing an adapter to support your HIE? The CONNECT Team is in the process of evolving tools and creating new ones that will address these questions.

If you are in the process of standing up a CONNECT Solution, to help you be successful the CONNECT Team recommends you exercise these tools in the order listed.

1. Gateway Installation Self-Tests

CONNECT self-test scripts have been developed to ensure that the installation completed successfully and to validate that the local gateway is functioning. These tests are a self test of the gateway and do not confirm connectivity and related functionality. The scripts utilize SOAPUI, an open-source, freeware utility that sends and receives SOAP messages. Tests for each version of the gateway are available with each release.

2. Developer Gateway Testing

If you are developing tools that need to work with the CONNECT Solution or have a Gateway that needs a quick test, there are several CONNECT External Test (CET) Gateway servers available. These CET Gateways will be able to respond to Subject Discovery (SD) / Patient Discovery (PD), Document Query and Document Retrieve messages. Use the server that corresponds to the version of CONNECT that you are using. We have also added a unidirectional HIEM test. This will allow you to test in one direction that you can receive File Transfers and that your connectivity is sound.

We wanted to ensure it was clear what configuration you are testing against. We have provided the following table and will updated it as we upgrade the CONNECT versions or modify any of the Reference Tools that we point to.

Subject Discovery Endpoint GUI
For CONNECT R2.2 only, in order for CET to properly respond to a SD message each organization will need to pre-populate the Home Community ID and SD endpoint of their gateway using the following GUI http://exttestgw.fedsconnect.org:8080/UDDIModifierGUI. If you have tested with CET before and your Home Community ID or SD endpoint has already been loaded, you do not need to load them again. Actually, the CET SD endpoint GUI will not allow re-additions of the same Home Community ID or SD endpoints. If you run into any issues please post a message on the forums.

HIEM Unidirectional Test
These steps will allow you to setup a profile to receive a file from the exttestgw3 or exttestgw4. These files are generated and sent every 15 minutes. Please ensure to unsubscribe once the test is complete, otherwise you will continue to receive the files to your servers.

Pre-conditions:

• Configure HIEM Test for CONNECT 2.4: http://developer.connectopensource.org/display/NHINR24/HIEM+File+Transfer
• Configure HIEM Test for CONNECT 3.0: http://developer.connectopensource.org/display/NHINR30/Mirth+Connect+HIEM+File+Transfer+Adapter
• Install Mirth File Chunker:
  http://developer.connectopensource.org/display/CONNECTWIKI/Mirth+CONNECT+HIEM+FTA

After configuration, make sure that the Inbound and Outbound channel settings in the FTAConfiguration.xml matches exactly the path of the Inbound and Outbound directories in the mirth_fta.properties file from the Mirth File Chunker.

Instructions:

• Send a Subscription to the External Test Gateway for the Topic "nhin:NotifyTest" in order to Subscribe and receive messages.
• The External Test Gateway sends a file via FTA and the Mirth File Chunker every 15 minutes. The file name format is: "NotifyTest-yyy-mm-ddThh-mm-ss.txt"
• The contents of the file will be “yyyy-mm-ddThh-mm-ss: This file was sent to you because you have a subscription to the NotifyTest topic.”
• The assembled file will be found in the FTA_ASSEMBLER_OUTPUT_DIR folder. This property is defined in the mirth_fta.properties.

Post-condition:

• Unsubscribe from the Subscription in order to stop the messages from coming.

Review the Logs
For the testing you perform, you will be able to obtain copies of the logs by access the following URLs in the table below. These will assist you with any troubleshooting you may require. You can copy and paste the logs from this location to an editor that will allow you to search the logs.

Test Patients Prepositioned
A number of patients have been prepositioned in each CET Gateway to assist with your testing. The table below provides the details of this data for exttestgw and exttestgw2:

The table below provides the details of this data for exttestgw3 and exttestgw4: