• Support Board: https://openncp.atlassian.net/secure/RapidBoard.jspa?rapidView=2
• Meeting Words: http://meetingwords.com/zb1ANd6ZNm
  

• Sprint Review / Retrospective

  • A validation tool was developed and incorporated into Util project (The global module structure is "DataModel", "Services" (validation wrappers) and "Reporting" - UML Diagram: https://openncp.atlassian.net/wiki/download/attachments/14778416/REMOTE_VALIDATION_LIB_UML.png?api=v2);
  • Remote validation results are represented in the form of structured XML reports, written to "validation" dir, inside EPSOS_PROPS_PATH;
  • They are divided between NCP-A and NCP-B;
  • The adopted naming convention is the following: [date]_[used validator]_[validation result].xml (Because of the NCP stateless requirement each message is validated in an independent way - theres is no grouping by workflow, for instance);
  • They contain the validated object and the validation output- sample Reports:
  • • XCA Retrieve Anwser: https://openncp.atlassian.net/wiki/download/attachments/14778416/20131118161744626_EPSOS-2_FETCHDOCUMENTSERVICE_RETRIEVE_-_RESPONSE_PASSED.xml?api=v2);
  • • Audit Messages: https://openncp.atlassian.net/wiki/download/attachments/14778416/20131118165551938_EPSOS-2_-_FETCH_DOCUMENT_SERVICE_%28SERVICE_PROVIDER%29_FAILED.xml?api=v2
  • It was considered to represent the reports in a more friendly way (e.g. using IHE EVSClient XSLTs), but due to the resources and time constrain in order to obtain a fine-tuned version it was decided to stick with XML format, at least for now; 
  • • The message will most probably be managed by a server, not by users, so the user friendly is not a CRITICAL, mas should be marked as an possible IMPROVEMENT.
  • • ERIC: has been really helpfull on providing feedback and inputs for improving the strategy. CREDITS and special thanks should be sent.
  • The validation is turned on or off by the usage of a database property called "automated.validation";
  • Remote validation services for XD*, HL7v3 and Audit Messages are already implemented for Client and Server Side;
  • CDA validation is also implemented but there seems to be an issue with the Validation Web Service - An e-mail has been sent to Eric Poiseau and Abderrazek;
  • Steps for sucessfully complete sprint (to be putted in place today):
  • • Clarify CDA validator Issue with Eric and Abderrazek;
  • • Clarify if SAML remote validator is available or not (Eric stated that it exists here: https://openncp.atlassian.net/wiki/x/MIDh, but it is not listed here: http://gazelle.ihe.net/node/443);
  • FUTURE IMPROVEMENTS
  • • Implement a tool, for instance a web portal, where we can see all the validated messages, maybe grouping them by workflows if possible (maybe with filters like we have at IHE EVSClient).
  
  

   

• QA Internal STAGE  Planning;

  • MRO Service + CI Enhancements
  • INTERNAL QA > 19 to 22 Nov > OpenNCP V2.1.0;
  PN’s QA > 25Nov to 6 Dec
  • (Fine tune first approach with provided information and incorporate final tasks)
  
  

   

• GOLD (FINAL) Release - OpenNCP V2.1.1

  • Release Process:  9 to 13Dec

  • Support Countries Updating: 16 to 20Dec;

Articulate with IHE improvements - Gazelle Web Services to perform validation on audits:

- The current Gazelle validation web-services do not return any EVS Permanent link, as they only validate the messages and return validation result and details (errors and warnings);

• it would be useful to have a "permanent link" functionality (in Gazelle Remote validation services) in order to keep validation reports simpler and traceable, by linking them to validation pages in EVS Client;
• We should enforce the responsible usage of remote validation services by PN's as some limitations are imposed by IHE;
• The current imposed numbers ( No more than 30 requests per IP address per minute, No more than 3000 requests per period of 24 hours per IP address) should be enough for the CI environment and even PN's - but we should keep this topic under control;
• A meeting between Gareth Woodham, Marcelo Fonseca and Eric will take place tomorrow to discuss this topic;

b) Documentation preparing

b) Documentation preparing

• c) Knowledge sharing

Knowledge sharing & Collaborative Design

https://openncp.atlassian.net/wiki/display/ncp/Road+to+Sustainability

• Webinars (online) – When?
  • a. Tools and Method
  • b. Architecture and Technologies
  • c. Testing and Deploying
    
    
• Workshop (f-2-f) – Where? When?
  • a. Real Life Operation - Struggles
  • b. Security Hackathon
  • c. Performance Hackathon
  • d. 3rd Party Projects Collaboration
  • e. Designing the Future - evolutions roadmap

How can we add more value to actions?
Questions and next steps?

• Status
  colour Blue title To Do

  [ Licinio Kustra Mano ] Schedule "Sprint Review/

• Retrospective" TConf > Tuesday, 25th November 2013 09h30 CET

• ;

• Status
  colour Green title Done

  [ Ivo Pinheiro ] Prepare and make available OpenNCP 2.0.3 Release Notes - Technical Details 

• Status
  colour Green title Done

  [ Licinio Kustra Mano ] Announce OpenNCP 2.0.3 Release

• Status
  colour Green title DONE

  [ Marcelo Fonseca ] CI Environment > Clarify with Eric Poiseau the OpenNCP CI Requirements and Strategy > having in mind the sustainability plan for this service;

• Status
  colour

• Green title

• DONE

  [ Marcelo Fonseca and Gareth Woodham ] Focus TConf on "CI Automated Testing Suite Enhancements" design refinement and development work organization + effort estimation + Implement Enhancements;

• Status
  colour

• Green title

• DONE

   [ Marcelo Fonseca and Gareth Woodham ] Implement the "CI Automated Testing Suite Enhancements"

• Status
  colour Red title ON HOLD

  [ Ivo Pinheiro ]  Research for alternatives approaches to a single country hosting the CI - e.g. cloud based services with Open Source Projects special service plans.

• Status
  colour Yellow title IN PROGRESS

  [ Licinio Kustra Mano ] Request Kostas Karkaletsis to report (OpenNCP Support Board) issue found related with MRO new service ( PDF retrieval)

• Status
  colour Green title DONE

  [ Licinio Kustra Mano ] Create Draft: OpenNCP Installation Manual Overview;

• Status
  colour

• Green title

• DONE

   [ Licinio Kustra Mano ] Create Draft: OpenNCP General Presentation;

• Status
  colour

• Yellow title

• IN PROGRESS

   [ Licinio Kustra Mano ] Create Draft: OpenNCP Technical Sheet  / Review of epSOS Technical Aspects
  

• Status
  colour Yellow title IN PROGRESS

  [ Licinio Kustra Mano ] Evaluate with Marcello Melgara the value added and effort needed for updating the epSOS D 3.B.2 document
  

• Status
  colour

• Green title

• DONE

   [ Licinio Kustra Mano ] Circulate for review in OpNCP-Comm (Stéphane Spahni and Ivo Pinheiro and Konstantin Hyppönen) for Review: OpenNCP Installation Manual Overview;

• Status
  colour

• Yellow title

• IN PROGRESS

   [ Licinio Kustra Mano ] Circulate for review in OpNCP-Comm (Stéphane Spahni and Konstantin Hyppönen) for Review: OpenNCP General Presentation;

• Status
  colour

• Yellow title

• IN PROGRESS

   [ Licinio Kustra Mano ] Circulate for review in OpNCP-Comm (Stéphane Spahni + Konstantin Hyppönen + Ivo Pinheiro) for Review: OpenNCP Technical Sheet

• Status
  colour

• Green title

• DONE

   [ Licinio Kustra Mano ] OpenNCP Webinars > Present a value proposition (to OpenNCP-Comm and to Juergen);

• Status
  colour

• Green title

• DONE

   [ Licinio Kustra Mano ] OpenNCP Workshop > Present a value proposition (to OpenNCP-Comm and to Juergen) for further discussion on When and How make this happen.

• Status
  colour Yellow title IN PROGRESS

  [OpenNCP-Comm] OpenNCP Webinars & Workshop > Consolidation and Review

• Status
  colour Blue title To Do

  [ Licinio Kustra Mano ] VPN Problem > Provide a short summary of what has happened and solutions adopted