OpenNCP Weekly Sprint Meeting

23rd Jul 10:00 to 11:00  CET

Work RoadMap - epSOS 2 Services

1º Sprint: 28Jan > 8 Fev (2 weeks) > Completed
2º Sprint: 11Fev > 22Fev (2 weeks) > Completed
3º Sprint: 25Fev > 8Mar (2 weeks) > Completed
4º Sprint: 11Mar > 22Mar (2 weeks) (<- both weeks, or perhaps just the last week could be the code freeze?) Completed

...

• Goal 1: PAC + HCER > Audit Trail Messages (Compliance)
  
• Goal 2: HCER > Document Automated Tests (Quality)
• //Goal 3: PS + PAC > Document & Transactions Automated Tests (Quality)
• //Goal 4: eP/eD > Document & Transactions Automated Tests (Quality)
  
  
• Release OpenNCP 2.0.1 > 31 July, 2013 (Wednesday)
  

Agenda

1. OpenNCP Support

2. OpenNCP 2.0.1 Progress

2.1 PAC & HCER Audit Trail

Location

Skype (sirLicman + Jira Board)

Participants:

...

...

...

MEETING NOTES

1. OpenNCP Support

• Emergency WorkFlow - 
  • GNOMON: Portal > How can handle this situation? PT Adaptation
    • https://support.epsos.cz/issues/315
    • POSTed in the issue the proposal for solution in this case;
      • Emergency Workflow in OpenNCP

2. OpenNCP 2.0.1 Progress

• Goal 1: PAC + HCER > Audit Trail Messages (Compliance)
  
  LKM: Check the SPECS and make them available for the dev team.
  • Requested Soren Bittins > sent email epSOS: Audit Trail Specifications > 15 July, 2013 10:30:33 AM GMT+01:00
    
  • Kostas: modify the audit library
    • It is possible to prepare some development, while waiting for the SPECS;
      
  • MF + IVO: Could change the component in order to invoke the library;
    • Where to invoke the Audit Trail Messages:
      
  • Reference Documentation
     D 3.4.2 Common Components Specifications - Version 1 (for XCA or 2.2 for XCF)
    • https://service.projectplace.com/pp/pp.cgi/0/852608418?op=get_framed_props&id=841951755_852608418 IMPEDED - Waiting for Soren situation point on this
  • PAC: currently using identification service and the patient service audit schemas; should be updated when SPECS are in place;
  • HCER: currently using eD service and consent service audit schemas; should be updated when SPECS are in place;
• Some changes may be needed in order to guaranty compliance with the new SPECS.
  • Reinforce the NEED for the SPECS;
• Is the compliance with epSOS 1 assurance guaranteed in OpenNCP 2.0.1?
  • Countries moving from OpenNCP 1.1.3 to 2.0.1 should go under a PPT slot before going Operation;
  • 4th PPT: 2º Quarter of September; >
  • 5th PPT: When??
• Reinforce SPECS need before releasing;
  • Even without the SPECS the release MUST came out;
    
    
• Goal 2: epSOS 1 & 2 > Document

  Jira Legacy
  server JIRA (openncp.atlassian.net) key PT-295

  • The great news for today meeting is that all epSOS services 1 and 2, all covered and checked by currently implemented tests;
    
    • http://dev.iuz.pt/openncp-jenkins/job/DEVELOP-epSOS.PT.ClientSide/lastSuccessfulBuild/console
  • Future work: 
    • Extend tests for Transactions / Audit / Assertions;
    • Extend tests for dynamic created documents (by injecting live data directly on the Portal);
      

NEXT Steps