OpenNCP Weekly Sprint Meeting

3rd 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

• Release date: 25March (Monday) > OpenNCP 2.0.0 >  Postpone

5º Sprint: 25Mar > 8Apr (2 weeks) Completed 

• Release date: 10Apr (Thursday) > OpenNCP 1.1.2 > Completed (Release Notes)
• Release date: 11Apr (Thursday) > OpenNCP 2.0.0 >  Postpone
  

6º Sprint: 22Apr> 3May (2 weeks) > Completed 

• Release date: 8May (Wednesday) > OpenNCP 1.1.3  > Completed (Release Notes)
  

 7º Sprint: 6May> 17May (2 weeks)  > Completed

• Release date: 22 May (Thursday) > OpenNCP 2.0.0 (Postpone)

 8º Sprint: 20May> 31May (2 weeks)  > Completed

• Goal: PAC + HCER QA

 9º Sprint: 3June> 14June (2 weeks)  > Completed

• Support OpenNCP 1.1.3 (used in 4th PPT-slot as May 27th - June 7th) 
• Release OpenNCP 2.0.0 > 19 June (Thursday)
  

10º Sprint: 24June > 5July (2 weeks)  > in Progress

• 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)
  

Current SPRINT -

FI: ??? Goal 1;

PT: Goal 2;

SW: NO availability;

CH: ??

Agenda

1. OpenNCP Support

2. OpenNCP 2.0.1 Progress

3. PAC & HCER Audit Trail

4. MRO Service Specification discussion

5. TSAM-sync adaptation for CTS2 compliance

Location

Skype ()

Participants:

MEETING NOTES

1. OpenNCP Support

• PT: working hard to go live
  • Current constraint: central services are not available for new content, since the migration started;
  • MF: Date planned for availability: End of June! - but Milan has left the project. Who is the new contact point for this?
  • KT: were working with the new Central Services in order to configure VPN;
    • MOST IMPORTANT: VPN may be not so important (this is not relaxation, before this mechanism was not in place). Certificates submission & sync mechanism;
  • LKM: Will inform Marcello and Juergen the situation point.
• Italian NCP takes between 10 to 15 seconds responding;
  • Mate: Says it ok.
  • Norbert: Says it was ok in April, but currently is unknown;
  • Marcello Melgare: Assertions in future cannot be sent (this may result in service failure); It needs clock sync from every countrys;
  • KT: Every NCP must support IHE CT profile  - must be synchronize;
  • MM: PPT env delay is a known feature; for Operation environment may be better;
• LKM: Referred that "PS breaking the glass" caused some doubts about belonging
  • MM: confirm that at this point the emergency scenario is scope;
    
    • Confirm that Audit Messages for emergency scenarios area being specialized;
• LKM: Patient Identifier may cause some because numbers
  
  • MM: there is hope for the future regarding eSense and Stork;
  • Increase the size of the input field and helping image;
• LKM: Physician evaluation questionnaire requires password protected:
  • +++++++
    

    An e-mail i got from the administrator or Questionnaire Portal:

    Hello Marcelo

    Unfortunately URL log-ins are disabled for security reasons. It just creates too many security loopholes in my opinion. If you feel that the Portal-B interface is secure enough, I suggest you display the credentials before the link

    Best Regards,

    Ion

  • +++++++
  • MM: this is country decision, so Portugal must decides what is the country strategy and then ask for epSOS support;
• MM: Spain is blocked for going to operation because:
  • incident 310 accur in TianiNCP
  • KTT: confirms it does not happen in OpenNCP;

2. OpenNCP 2.0.1 Progress

• Goal 1: PAC + HCER > Audit Trail Messages (Compliance)
  • Mika return at end of July; Konstantin come back middle August;
  • No job has been done;
• Goal 2: HCER > Document Automated Tests (Quality)
  • No job has been done;
• SW: in realistic perspective, unfortunately
  
• Slovenian: How is your availability?
  
  
  
• MM:
  
  • LKM: formalize the effort we need for OpenNCP support and sustainability;

3. MRO Service Specification discussion

• LKM: Ask for the specification team to clarify and meet with the development team;

4. epSOS2: TSAM-sync adaptation for CTS2 compliance

• Norbert: please stand by pushing this feature to development. Wait for decision on priorities and importance about this feature;

• Norbert: Austria development will be ready for November it is fully compliant with CTS2 requirements;
  • MM: There is a request of experts about the CTS2 specification approval;
  • MM to Norbert: there is the opportunity to check if the Austria implementation is compliant to epSOS CTS2 specifications are being.

XDM: export media the Patient Summary CDA

• Basic way to give the patient the ability to have in his hand the his PS.

NEXT Steps