...
- Team planned and prepared for the CONNECT Change Control Board where features in the backlog were discussed to understand partners interest and priority
- Hosted Change Control Board on January 22nd
- Presented current Product Backlog features and new requirements gathered
- There was good discussion during the meeting, some additional requirements were identified
- The 2015 Roadmap document has been updated to reflect feedback and discussions (updates in blue font)- The Roadmap can be found on the CONNECT wiki: https://connectopensource.atlassian.net/wiki/display/CONNECTWIKI/CONNECT+Roadmaps - There wasn't a quorum for voting
- The updated Roadmap/notes are being rerouted for additional comment prior to voting and approval
- Team participated in Direct connect-a-thon to validate CONNECT's Direst Direct service implementation
Below are some interesting Direct 4.0 features identified from Direct Connect-A-Thon which can be added to our Direct priority list:
- Encrypting private keys stored in the Direct environment.
- New RESTful based Config Service implementation in Direct. Direct is planning to deprecate the SOAP based implementation. More analysis needs to be done
- Responded to several community questions via the forums
...
CONNECT 4.4.1 patch was released to the community with the following improvements
eHealth Exchange Certification Updates for 4.4.1
- Set "mustUnderstand" attribute on the WS-Addressing Action element in the SOAP response message
- Fixed issue - CONNECT is removing SemanticsText value for MatchCriterionList elements - MatchAlgorithm and MinimumDegreeMatch
Fixed to make the scoping of the hl7 attributes configurable for the Role and PurposeOfUse SAML assertion elements.
hl7 attribute scoping for Code, CodeSystemName and DisplayName used in the PurposeOfUse and Role elements in the SAML assertion are now configurable via gateway.properties parameter hl7PrefixForAttributes.
System Administration Module - Connection Utility
The System Administration Module as has been configured with a new utility that will allow an organization to ping a potential trading partner to verify connectivity.
More information can be found in the System Administration Module
- Design updates can be found here- https://connectopensource.atlassian.net/wiki/x/igDs
- Test scripts are updated here- https://connectopensource.atlassian.net/wiki/x/UAB3AQ
- Fortify scans were executed to ensure that there are no Critical, Highs, Medium Fortify tickets or no CAT1 tickets.
- Fortify findings/reports can be made available upon request.
- Testing
- Install tests were executed successfully on JBoss, WebSphere and GlassFish. There is a known issue of the ping utility on WebLogic application server.
- eHealth Exchange participant certification test cases were internally executed to ensure no new issues were created.
- NIST Document Submission test case was also executed to ensure that the PurposeOfUse/Role scoping issue was resolved.
- Patch was tested with prior versions of CONNECT to ensure interoperability
- See patch page for release notes and software artifacts - /wiki/spaces/CONNECT4/pages/30015631
...