Disclaimer
All capabilities designed, developed, and tested during the CONNECT 5.2 project time frame are described below. Known defects in the product are listed below as well as in the CONNECT Issue Tracker tool. Defects which may occur within the product may not be limited to these issues. This product and the accompanying written materials are provided "as is" without warranty or guarantee of any kind. Furthermore, no representations made regarding the use, or the results of use, of the product in terms of correctness, accuracy, reliability, currency, or otherwise is warranted or guaranteed. The Federal Health Architecture (FHA) shall not be held liable for any direct, indirect, consequential, or incidental damages arising out of the use of or the inability to use this product.
Version History
Version# | Date | Modified By | Description of Modification |
|---|---|---|---|
| 0.1 | 10/23/2018 | Sovann Huynh | Initial Draft |
CONNECT 5.2.0.1
IMPORTANT NOTE: CONNECT 5.2 is not supported and is replaced by CONNECT 5.1.2 All information on this page regarding CONNECT 5.2 applies to CONNECT 5.2.0.1
Summary
Release 5.2 continues to build on the functionality and architecture introduced in Release 4.0 through additional features, selected improvements, and bug fixes. We encourage the CONNECT community to upgrade to Release 5.2 to take advantage of these updates. Details can be found in the following subsections:
Enhancements and Announcements
Java 7 no longer supported
As of CONNECT 5.2, only Java 8 is supported.
Certificate Manager updates
Certificate expiration alerts have been added to the CONNECT Admin GUI dashboard. A certificate chain of trust view has been added to provide a clear hierarchical representation of certificates in the trust store.
Exchange Manager updates
Organizational view and search function have been enhanced to provide a more user friendly experience.
Internal Endpoints Manager
An internal endpoint editor has been added to more easily manage internal adapter, policy engine and other endpoints necessary for transaction processing.
Document Data Submission
A web service to support a proposed Register Document workflow has been created, as well as a reference adapter for testing and demonstrating the new service.
Patient Location Query
A web service to support a proposed Record Locator Service workflow has been created, as well as a reference adapter for testing and demonstrating the new service.
Failure Logging
This addition to CONNECT's existing Event Logging feature allows users to quickly locate exceptions and transaction failures.
Additional Admin GUI updates
Admin GUI web services have been decoupled from the CONNECT core to provide a more lightweight gateway to CONNECT users not utilizing the interface. An alerts and notifications section has been added to the dashboard to make users aware of important system notifications. The Cross Query Gateway Client now includes SAML assertions with real time user data and can be used for fully-compliant Exchange messaging.
Test Data Loader updates
Test document creation has been refined to better reflect existing Document Query and Document Submission requirements.
Security Scans findings and security update
The CONNECT team as part of the release readiness process in 5.2, identified and addressed findings based on security scans performed on the CONNECT gateway code base. Several tools were used including Fortify, SonarQube, OWASP Dependency Checks and FindBugs as part of the scans executed on the 5.2 code. All Critical, High, Medium, and Cat 1 Low findings were addressed and the team will continue to work with the federal partners to ensure the code quality meets their implementation requirements. Addressing these security findings will ensure adopters deploy a more secure implementation and will assist in meeting their organization's internal security reviews, as they deploy CONNECT in their preferred environments.
Release testing
CONNECT 5.2 was install-tested in multiple environments and with multiple operating systems to support the federal partner environments and application servers/configurations used by the community. As with each release, CONNECT was regression tested as well as integration tested against prior supported versions of CONNECT. See below the testing matrix with the application servers/OS that were utilized for release testing.
Testing summary by Operating system and application server for 5.2
App Server | WebSphere (Version 8.5.5.3) | WebLogic12c (Version 12.1.1) | WildFly (Version 8.2.1) | JBoss (Version EAP 7) | |
|---|---|---|---|---|---|
OS | |||||
Windows 64 | B, S, A, IO, R | ||||
Linux 64 | B, A, IO | B, A, IO | B, A, IO | B, A, IO |
Legend:
- S – Source Code Installation and Validation
- B – Binary Installation and Validation
- R – Regression
- IO – Interoperability
- A – Admin GUI (IE v11, Chrome)
Product Development Notes
Open source application server – WildFly
From a product development perspective, the team uses WildFly as the team-supported open source application server. We are aware of community members using CONNECT on JBoss EAP, the enterprise version of WildFly. We have published instructions for FIPS configurations on JBoss EAP 7, WebSphere and WildFly.
Development, installation and new feature testing will be done on WebLogic, WebSphere, JBoss EAP 7 and WildFly only.
Known Issues
| Issue |
|---|
CONNECTDirectConfig - postmasterAddressId Not Populating when adding a Domain |
Direct Interop: Multi-Recipient Messages(Inbound) issue when recipient is one of many recipients in the message |
| Garbage Collection (GC) exceptions may occur if CONNECT is undeployed and re-deployed without a server restart in between |