Sprint 139 Progress Summary

Owned by Greg Turner (Unlicensed)
Last updated: Sept 11, 2014 by Deepthi Rodrigues (Unlicensed)
4 min read

Aug 25th - Sep 08th

Executive Summary

Overall Status

The Product team prioritized the following themes and tasks for Sprint 139 comprising 24 points.  These themes included -   

  1. Partner and Community support

  2. X12 (Synchronous Testing, Generic Batch Dev, Update and Finalize Design Approach)

  3. SSA & VA Implementation Support

  4. Healtheway Product Certification Support (Research and Support for Vendor Reported Issues, Wiki Page Updates)

  5. Admin GUI (Password and Multiple Call Bugs)

Sprint status is excellent and the team completed 26 points this sprint, one ticket that was pulled in to fix an issue related to content type header missing semicolon, that was resulting in an interoperability issue with partner integration at VA.

Release 4.2.2.2 was made available to the community this sprint. The team completed the X12 Document Submission framework for the deferred/generic batch submission time transactions. 

Burndown

Sprint Themes and related tickets for Sprint 139:

Community Implementation support

  1. Forum discussions
  2. Community and OHT support
  3. SSA 4.3.2 implementation
  4. Continued 4.3.2 RC1 Testing/ Monitoring
  5. Support VA with 4.2.2.2 implementation
    1. 4.2.2.2 was released with bug fixes - /wiki/spaces/CONNECT4/pages/10584084
    2. Fixes include
      1. Missing semi-colon in content-type header (CONN-1321)

      2. Merlin Crypto package classes read their related properties files from the bundled Properties.jar library; not the "config/nhin" folder(CONN-1178)

      3. Modify logging/exception detail for troubleshooting endpoint exceptions(CONN-1184)

      4. NwHIN PD response can have invalid creation time(CONN-1114)

  6. Partner Questions
  7. Fixed ant install and broken ant deploy.connect scripts 
  8. Community support with certification testing

Support and research Healtheway product certification issues 

  • See /wiki/spaces/CONNECTWIKI/pages/21823498 for discussion on Known issues related to CONNECT and Product certification
  • Discussed attribute nesting question on the spec factory forums - http://exchange-specifications.wikispaces.com/share/view/69155678. This question was posted by the CONNECT team as it was raised by one of the trading partners during partner integration testing.

    • It was understood that 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. Healtheway indicated that after their research they would publish an FAQ entry with the recommendation. The flavor that CONNECT supports(separate attribute statement for each attribute) is acceptable per the specification. However it is important to note the differences in 4.x compared to earlier versions of CONNECT - In earlier versions (3.3 and earlier) CONNECT (utilizing Metro stack) provided an attribute statement with all attributes nested within it. In 4.0, CONNECT uses the CXF/Open SAML tech stack that generates the SAML headers and produces an attribute statement separately for each attribute. CONNECT on the responding side accepts both flavors.

  • Discussed semanticsText usage question on the spec factory forums and call - http://exchange-specifications.wikispaces.com/share/view/68996574
    • The team followed up with both the spec factory and IHE on the specification requirements for the semanticsText field used in the PD query parameters. 

    • It seems that a new CP(IHE ITI) is required to update the base XCPD spec diagrams to reflect the mandatory behavior of the SemanticsText field.  In its current form/version the spec indicates that null flavors are allowed for SemanticsText although it is not how IHE thinks its usage has evolved and IHE indicates that this should be mandatory and not just required in RIM terms. 

    • CONN-1310 has been created and fixed in the latest code base, and will be available in the next CONNECT release.

    • To summarize, the issue is related to the HL7 WSDL.  CONNECT uses a 2008 version of the HL7 WSDL which has been in place since the 2.X versions of CONNECT.  By updating the WSDL to alter the semantics text data type the issue of dropping these values would be resolved however this will significantly impact all current CONNECT adopters requiring a fresh install with a new binary with possible adapter updates.   

    • Currently it seems to be more of a compliance issue rather than interoperability issue. We are still not clear whether products will be tested for the default values of SemanticsText or not.  This will help us determine next steps for other supported releases based on impact to the community and federal partners.

       

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 Real time/synchronous service for X12 Document submission.
    • Completed Generic Batch Submission Request and Response framework (CONN-1300, CONN-1301, CONN-1302)
      • Created X12 Generic Batch Submission reference adapter
      • Created Generic Batch Document Submission request and response Transaction Test Case and added it to the ConnectValidation Test Suite.
    • Researched error handling scenarios at the gateway that may need to be handled(CONN-1303)
    • Design approach updated on the wiki to include Deferred/Generic batch transactions
  • Bug fixes
    • Fixed issue related to CONNECT removing SemanticsText's value from the edge/entity in PD request to NwHIN - Values if provided in the entity request will be sent over through the NwHIN interface(CONN-1310)
      • Changed the data types used from ST to ST_explicit in common types module that allowed to not drop the values.
      • Validated the fix in the interoperability test environment to ensure CONNECT is compatible with other supported CONNECT versions after the applied fix.(CONN-1315)
      • Validated the fix after successfully executing PD Tests in the DIL(CONN-1316)
    • Commented out Fanout-Test regression Suite test that was resulting in CONNECT NIGHTLY CI build failure. (CONN-1318)

JIRA Planning Board of Committed User Stories for Sprint 139:

Related Files

Sprint 139 code tag

Binaries are here - ftp://ftp.connectopensource.org/connect_4.0/CONNECT-4.4.0_sprint_139/