Sprint 159 Progress Summary

June 1st - June 15th 

Sprint 159 Themes

  •  X12 Auditing Development, Integration and Testing
    •     Final cleanup tasks and Batch and Real-time testing
    •     Schedule demonstration to CMS & Complete Documentation
  •   Release 4.5 Preparation Tasks
    •    EHEX/NIST certification tests
    •   Continue to addressing Fortify scan findings
  •  Technical Stories
    •    Complete timeout by transaction testing
  •       Support Tasks
    •    DoD JBoss FIPS installation (PKCS11)
    •    WebLogic 12.1.3 VA Adapter upgrade

The team completed 30 points this sprint, and created the Release Candidate RC1 for the release.  The team will start release testing next sprint. 

Burndown:

Sprint Themes and related tickets for Sprint 159:

Partner and Community Support:

  • VA -  Installed CONNECT successfully on WelbLogic 12.1.3
  • eHealth Exchange - Reviewed Patient ID matching document from spec factory. Some comments that the Product Team had  - 
    • The document talks about optional and required traits. With multiple versions of underlying specifications being available(XCPD) and the NwHIN PD spec specifying constraints above the IHE specs, it would be best to qualify and call out each of the search parameters and traits. (maybe in an appendix to this document). Particularly with the CONNECT gateway product that supports reference adapters which are reference implementations, we would like to understand the specific traits so that these can be demonstrated to the community in our reference implementations.Also it would help us in understanding what will be enforced via test cases in the future and plan development accordingly.
    • There is a new requirement discussed'9.If applicable, Responding Gateways MAY return multiple (ambiguous) matches per Assigning Authority. '. This requires a specification change and will change the way patient correlation adapters work as they currently assume only one match per AA. Hence this will have impacts to the initiating gateway.
    • For patient identifier being decommissioned, need to understand whether this will be a new spec change or new error code.
  • DOD - DOD reported problems in configuring FIPS (with store type PKCS11) with CONNECT 4.3.1 on JBOSS EAP 6.3.(CONN-1616)
    • The Product Team fixed the issue - If the KeyStore type is "PKCS11" then a check is added not to load the file from store location provided in Signature.properties and "TrustStore.properties" 
    • The fix was tested using the validation suite but will need to be further tested by the DoD team in their environment.
    • Link to the wiki page - https://connectopensource.atlassian.net/wiki/x/9IA6Ag

Release 4.5

  • Manual Test cases(draft) were updated
  • Configured FHIR AdminGUI page to not appear when FHIR not in use.

  • Release Preparation
    • Created the test plan for Release 4.5
    • Addressed the Fortify and OWASP dependency check issues on the codebase.
    • Cut Release 4.5 RC1 tag
    • Generated and released Common Types and CONNECT WebServices libraries for release.

JIRA Planning Board of Committed User Stories for Sprint 159:

Related Files for Sprint 159:

4.5 RC1 code tag

Common-Types source

CONNECT-Webservices source