Sprint 102 Progress Summary

February 25 - March 10, 2013

Executive Summary

Overall Status

Burndown

Cumulative Flow

Sprint Themes

The Product team pointed and prioritized the following themes and tasks for Sprint 102 comprising 20 points.  The reduced predicted velocity is due to team member attendance at HIMSS.
The team pulled in an extra 3 points during the sprint and completed 21.5 of the 23 total points for this sprint.

• HIMSS ’13 Preparation & Attendance
  • CONN-53 - As an Exchange interoperability showcase participant. I go to a CONNECT web app, enter in my endpoints, synch up my cert, and enter in the basic demographic data about MY patients, so I can demonstrate my use of Exchange technology.
  • CONN-52 - As a Direct interoperability showcase participant, I want to use a CONNECT web app, to enter my direct address, and synch up my cert, so that I can demonstrate Direct.
  • CONN-231 - As a HIMSS participant, I want the CONNECT-Hub user interface to be polished and handle my errors.
  • CONN-54 - I'm an Exchange interoperability showcase participant, I want to go to a CONNECT web app, enter in my endpoints, synch up my cert, and look up the basic demographic data from other participants, so I can exchange with them.
  • CONN-136 - As an Exchange interoperability showcase participant. I need an UDDI to store Exchange addresses.
  • CONN-227 - As the FHA director, I want the CONNECT Product team to participate and demonstrate CONNECT in the HIMSS interoperability showcase, so that adopters are aware of the capabilities of CONNECT supporting Exchange/Direct
  • CONN-140 - As the FHA director, I want CONNECT installed on a server for us use in the interoperability showcase.
  • CONN-232 - As a CONNECT developer, I want to do some HIMSS13 demo dry runs, so I can be sure our demo goes smoothly.
  • URLs:
    • Harness to add connection information to allow testing between CONNECT and Direct implementers - http://interop.5amsolutions.com - uid: himss; pwd: exchange
    • Updated Universal Client: http://connect.5amsolutions.com:8080/CONNECTUniversalClientGUI - test patient Cindy Winters

• CONNECT 4.1
  • CONN-186 - Confirm that event logging hibernate file does not work with WAS in 4.0
  • CONN-229 - Wrap to external testing for Direct on WL and WS --CONN-84 - Remove deprecated Database code
  • CONN-138 - As a CONNECT adopter, I want the CONNECT validation suite to be able to run against a remote server so that CONNECT is thoroughly tested against self and other machines.
  • CONN-286 - regressionimprovementsfromregressionsuite automation
  • CONN-281 - Createpatientdbregression suite
  • CONN-230 - Install and Reconfigure CONNECTInteropTest Harness atTerremark
  • CONN-188 - As a CONNECT adopter/developer, I want to IncreaseCoberturacoverage for Policy Engine, Aggregator, and Transform packages by at least 20% in line, method, and branch statistics so that code quality is improved
  • CONN-74 - As a CONNECT adopter/developer I a clean property file (gateway.properties) so that there is no confusion with regards to the unused properties or default values.
  • CONN-233 - As a CONNECT adopter/developer, I would like CONNECT to useliquibasefor easier database management.

• CONNECT 4.0 Community Support (Forums, etc.)
  • Forums + Community Support
    • http://www.connectopensource.org/developer-resources/forums
    • CONN-166 - Adopter reporting build problems - failing tests
  • Webinars
    • NeHC Webinar (http://www.nationalehealth.org/CONNECT)

• Multi-Spec DQ Investigation & Analysis (CONN-46, CONN-15, CONN-215)
  • CONN-46 - As a CONNECT implementer supporting both versions of theeHealthExchange specifications, I need to know what version of the spec a message is implementing, so that I can validate the incoming message.
  • CONN-15 – As a CONNECT implementer, I want to instruct the gateway which spec version/endpoint to target for a service so that I have greater flexibility when exchanging with my trading partners.
  • CONN-215 - As a CONNECT adopter, I need to understand how fanning out requests to multiple communities is handled with the multi-specification implementation in CONNECT
  • CONN-293 - As a CONNECT developer, I want to research design options related to determining what version of the spec an incoming message is implementing to support partnerusecase(CONN-46)
  • CONN-296 - As a CONNECT developer, I want to research design options related to instructing the gateway which spec version/endpoint to target for a serviceinorderto support partner use case (CONN-15)

Prioritized JIRA Planning Board of Committed User Stories for Sprint 102

(https://issues.connectopensource.org/secure/VersionBoard.jspa?selectedProjectId=10140)

Related Files

• Sprint 102 review notes - Notes about the work completed in s102. (Also includes work planned for s103)
• Sprint 102 planning notes - Notes about the work planned in s102. (Also includes work completed for s101)
• Sprint 102 code tag
• JIRA. See Sprint 102