Sprint 126 Progress Summary

Feb 24 - Mar 10, 2014

 

Executive Summary

Overall Status

Sprint status is excellent. The Product team prioritized the following themes and tasks for Sprint 126 comprising 41 points. These themes included - Bug fixes affecting release, Terremark migration, VA/community support, Release testing and documentation and certificate issue documentation.The team completed 35 points for this sprint.

During this sprint, the team prepared the draft test plan and also started on installation testing for the next Release 4.3. The team  supported VA with their 4.2.1 upgrade preparations and participated in the Interoperability showcase at HIMSS . The team completed most of the tickets that were planned for this sprint. The team pulled a couple of tickets into the sprint that were considered higher priority(CONN-903, CONN-891) and hence a few tickets were not completed and will slide over to the next sprint(CONN-789, CONN-815, CONN-892).

 

Burndown

Sprint Themes and related tickets for Sprint 126:

  • Community Implementation support
    • Worked with the VA team on their 4.2.1 deployment in their development environment 
      • Supported several meetings including an in-person  meeting and email exchanges
      • Conducted research on a deployment issue with WebLogic 12c and Windows. The team was able to successfully install on WebLogic 12c (12.1.1) but found an issue with deployment of Connect 4.2.1 on Weblogic 12c (12.1.2) that would need further research(CONN-877) 
    • Researched and tested a persistent eHealth Exchange certificate issue affecting multiple organizations  
      • Conducted industry and exchange related research to isolate the issue
      • Tested with the VA, Conemaugh and MiHIN
      • Discussed and presented findings to Healtheway/Spec Factory
      • Documented additional detail about PKI to help the community understand certificate setup and provided troubleshooting guidance.(CONN-884)
        • The certificate issue was discovered in the staging environment as a result of some adopters having connectivity issues with their trading partners on the Exchange. Analysis and research conducted by the CONNECT team led to the conclusion that there were two certificates with different roots in use on the Exchange on the staging environments causing trust issues between the partners.   
        • HealtheWay was able to clarify that the Root CA downloaded from Entrust (SKI: DED9) is being phased out and replaced with the other one (SKI: FF25); members of the eHealth Exchange will eventually have to replace any certificates that were signed before the new Root CA was introduced.
        • This issue was documented as a case study that can be used for reference - /wiki/spaces/CONNECTWIKI/pages/11174264
        • Troubleshooting information can be found here - eHealth Exchange Certificate chain overview and troubleshooting (CONN-885, CONN-886)
    • Support and testing efforts continued with NIST, discussed several topics and compared interpretations of specifications
      • Completed testing NIST test cases for SOAP transport/Document Submission (CONN-882)
    • Tested DIL test for RDR test case(CONN-876)
    • Document Database configuration (CONN-849/CONN-888)
  • Release preparation
    • Bug fixes affecting release
      • Fix xsi:type for PurposeOfUse and Role attribute values to be CE. See spec factory related discussion.(CONN-875)
      • Researched issue related Entity Document Query and Document Retrieve secured services throwing errors and created supporting tickets (CONN-662)
        • Updated Entity Document Retrieve secured interfaces to support multi-spec enhancements.(CONN-891) 
        • Entity Document Query secured services throwing errors (CONN-892) – Work started but not completed this sprint. Moved to next sprint.
      • Research issue when there was a replay attack fault returned when concurrent requests are sent from a 3.x gateway to a 4.x gateway(CONN-859)
        • Documented analysis and possible options 
        • Disabled CXF replay detection as the CXF algorithm is not mature enough (CONN-903) 
      • Remove all HIEM tables and related database scripts(CONN-887)
    • Began install testing on Release 4.3
      • Created 4.3 RC1 tag (CONN-883) 
      • Binary Install testing on GlassFish(Windows) (CONN-780)
      • Source Install testing on GlassFish(Windows) (CONN-781)
      • Binary Install testing on WebLogic12c(Linux) (CONN-785)
      • Binary Install testing on JBoss(Linux) (CONN-790)
      • Source Install testing on JBoss(Linux) (CONN-791)
      • Source Install testing on WebSphere 8.5(Liberty Profile)(Linux) (CONN-789) – Work started but not completed this sprint. Moved to next sprint.
    • Release Documentation
      • Review and update System Architecture Documentation (CONN-873)
      • Document Release test plan for 4.3 (CONN-815) – Draft ready for review but not completed this sprint. Move to next sprint.
  • Security scan analysis and resolution
    • Received feedback from the DoD security team on the Fortify scan and security report responses supplied by the CONNECT Product team. Will review the responses and address the comments in the next sprint.
  • HIMSS Demo and community outreach at Interoperability showcase(CONN-889)
    • Supported the community at the showcase answering questions related to CONNECT features and functionality
    • Demonstrated two gateways communicating and exchanging health data with each other using NwHIN specifications - One as a home for health data collection for high impact conditions where data captured from various EHRs/hospitals are transferred to this repository and the other as a requester of documents. 
  • Infrastructure improvements
    • Infrastructure migration for Terremark was complete (CONN-813)
      • Migration of the Direct RI and Mail servers to Amazon Cloud (CONN-879/CONN-878)
      • DIL and NIST testing internal environments moved to GFE
      • GFE configurations and servers clean-up.
      • Inventory management and documentation 
  • Ongoing Custodial Agent Duties
  • CONNECT 4 Blogs and Forum posts

JIRA Planning Board of Committed User Stories for Sprint 126

Completed Tickets


Tickets not completed in sprint


 

Related Files