Sprint 140 Progress Summary

September 08th - September 22nd

Executive Summary:

Overall Status

Sprint status is good. The Product Team has prioritized the following themes and tasks for Sprint 140 comprising 22 points. These themes included -

Partner and Community support
X12 (Continued Testing, Error Handling and Large Payload Support)
SSA & VA Implementation Support
Healtheway Product Certification Support (Research and Support for Vendor Reported Issues)
Direct (Event Logging and Message Monitoring Testing)
Admin GUI (Password and Multiple Call Bugs)

The team completed 20 points this sprint. The team supported VA with their 4.2.2.2 upgrade as well as SSA with 4.3.2 implementation/testing related questions. The team implemented error handling as well as research related to large payloads for X12 messaging. 2 tickets were pulled out of the sprint early related to Direct testing(CONN-1228 and CONN-1231) and 2 tickets related to Admin GUI (CONN-1131 and CONN-1228) were pulled in. 1 ticket was re-pointed from 3 to 1 because the related support work (CONN-1330) was less than anticipated.

Burndown:

Sprint Themes and related tickets for Sprint 140:

Partner and Community support

Forum discussions
VA 4.2.2.2 implementation (CONN-1331)
- 4.2.2.2 release information can be found here - 4.2.X Patches
- VA determined the remaining three partners receiving 'Auth Failed' errors were due to same vendor spec interpretation issue related to attribute statement nesting
  - Related forum post - http://exchange-specifications.wikispaces.com/share/view/69155678. Both flavors are in use in the eHealth Exchange, but Healtheway will do some additional research to check the numbers on production(how many use one flavor vs. the other). From a specification perspective, the underlying specification(OASIS/SAML) allows for both flavors and hence the recommendation is that a responding gateway should be accepting both flavors to be compliant.
SSA 4.3.2 implementation (CONN-1330)
- Researching X509 certificate issue related to "SAML Certification Verification : No providers found".
  - Issue was due to a library supporting Direct(BouncyCastle) that was not required for Exchange based services, but was being utilized.
  - SSA removed Bouncy Castle and the issue was solved for them.
  - CONNECT team was not able to replicate this issue in the test environment.
  - Next steps are to follow-up with SSA and get some additional information on the environment to identify the root case( like version of WAS and IBM JDS, testing with multiple vendors using X509 certs etc)
  - CONN-1341 has been created for further analysis.
Partner Questions
Community and OHT support

Next Release (4.4)

Support for NwHIN CAQH Core X12 Document submission service
- Team reviewed the progress made last sprint with CMS team
  - CONNECT team demonstrated end to end Generic Batch service for X12 Document submission.
- Completed research and implementation for Large payloads for Deferred X12 Document submission using streaming and pass by reference(CONN-1314, CONN-1329, CONN-1337)
  - /wiki/spaces/CONNECTWIKI/pages/24084496
- Researched and implemented error handling for cases described below -
  - Error Handling (CONN-1325, CONN-1333)
- Updated wiki links and documentation for -
  - Design Approach for CAQH Core X12 Document Submission Service enhancement
- Updated SOAP UI test cases -
  - To include RelatesTo and MessageId in the Generic Batch Submission Deferred Response (request)(CONN-1328)
  - To include sample X12_BatchReceiptConfirmation and updated timestamp in Deferred response(CONN-1327)
Admin GUI
- Updated password fields in Create User and Login screens. Password field is showing strength indicator and password is starred out when it is being entered by user(CONN-1181)
- Fixed issue related to Admin GUI initiating multiple calls to backing bean(CONN-1220)

JIRA Planning Board of Committed User Stories for Sprint 140:

Related Files:

Sprint 140 code tag

Binaries are here - ftp://ftp.connectopensource.org/connect_4.0/CONNECT_sprint_140/