Disclaimer
All capabilities designed, developed, and tested during the CONNECT 5.1 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.
...
Several updates were made to enforce the conformant use of SAML assertions as required by the NwHIN messaging and authorization framework. The HOKSAMLAssertionBuilder, in particular, was updated to allow for more configurability while simultaneously increasing the amount of data validations.
Data-less deployment
CONNECT 5.1 can be deployed without creating all the data sources previously required. See /wiki/spaces/CONNECTWIKI/pages/259162119 for more details.
...
Development, installation and new feature testing will be done on WebLogic, WebSphere, JBoss EAP 7 and WildFly only.
...
.
...
The following tables display issues resolved or tasks addressed during the release of CONNECT 5.1. The details of these issues can be found in the CONNECT Issue Tracker, linked to in the tables below.
Features and improvements
(User stories, Improvements)
...
SAML assertions
...
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Data-less deployment
...
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
...
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Issue |
|---|
Direct Interop: Multi-Recipient Messages(Inbound) issue when recipient is one of many recipients in the message OPEN |
...
Details of the functional requirements can be found in the following JIRA user stories. The 'Traceability' column provides useful wiki links, associated ticket information and test case traceability for these requirements.
Feature/Requirement | Traceability | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| /wiki/spaces/CONNECTWIKI/pages/108691468, /wiki/spaces/CONNECTWIKI/pages/278528020 | ||||||||||
| Reported in ticketing system | ||||||||||
| Identified as a priority in CONNECT 5.1 CCB | ||||||||||
| Identified as a priority in CONNECT 5.1 CCB | ||||||||||
| Identified as a priority in CONNECT 5.1 CCB | ||||||||||
| identified as an eventual eHealth Exchange specifications update |