OpenNCP Community: Weekly meeting

TCon technologies
- GoToMeeting..... using it in a trial mode > Go to License version (36€ per month).
  - If it works OK, let's see who can provide a 1 organizer license, for 25 attendees > Request to Matic the license he offered.
  - Audio is not working on Linux
  - An alternative can be TeamViewer: pay attention to the number of users.

a) Manifesto and Governance (feedback from EXPAND WP5 Kick Off)

MANIFESTO: https://openncp.atlassian.net/wiki/x/AwBvAg
GOVERNANCE: https://openncp.atlassian.net/wiki/x/DYANAg
EXPAND Presentation: OpenNCP-Community_EXPAND-WP5_RATIONALE-and-Challenges-20140710_Reviewed.pptx
EXPAND Factories vision (early draft):

Image Modified

ACTIONS
- Update the Manifesto page with feedback after EXPAND WP5 KickOff;
- Wait for EXPAND WP5 Proposals towards Governance and Manifesto;

b) Developments progress monitoring

...

Specification and Design:
- STORK in OpenNCP: eIdentification and Mapping Procedures
- FutureID: AW_ epSOS usecases in FutureID _ eSens.pdf
Stork 2.0
- Overall Presentation of Stork 2.0. link to PPT presentations
- eID scenarios is all about joint efforts from eSENS and Stork 2.0.
  - Olaf: UC 3: difficulties to understand:
    - Gottfired: Swedish Doctor working Italy, that wants to authenticate as doctor.
    - HEIKO: Doctors in country B, accessing to patient info in Country A.
      - Gottfried: similar to epSOS,
  - Patient Consent
    - Document oriented?
    - Gottfried: no document, online consent generation;
  - Olaf: is just get evidence that something works or make it work completely (identity federation)
    - Common problems that from eSENS
    - Gottfried: avoid patient registration...
  - Gottfired:
    - Wants to harmonize with e-SENS...joint efforts are needed
ROADMAP:
- Reach Production somewhere September 2014.
  - 2 countries running UC 1, 2 and 3.
    - DONE: UC1: Patient Access with STORK eID Infrastructure for exchange of Medical Information (only Patient Summary) on Test Environment
    - UC2: Login with delegated person – otherwise like UC1
    - UC3: Login of HCP with STORK 2.0 Infrastructure and additional the foreign county receives the attributes that the citizen is indeed a doctor.
    - UC1: Additional Patient Consent
- As Patient Access: search mask is filled up when the patient authenticates himself, you get all attributes needed for XCPD request;
  - In STORK you request some attributes after authenticating the person.
  - Fill the Stork attributes with the epSOS Patient Identification: attributes > mapping file between
  - Marcelo Fonseca: will share a clarifying page on the mapping between Stork eID attributes and epSOS Patient Identification.
- Start piloting: 2015, Abril;
- - Complementary to STORK (Stork used in a more centralized services architecture, while FuruteID is more local seamless services).
Next events:
- e-SENS
  - Work meeting: 10 to 12 of September... discuss and validate the eSENS eID component;
  - September 2014: Countries need to commit specifically to what countries want to Pilot.
  - Wave 1 for eHealth Pilots: Start piloting: 2015, April;
- STORK
  - Developments Effort Estimation (for UC1, UC2, UC3) DONE (end of July, by iUZ and Gnomon);
    - Educated guess: end of developments DEC 2014;
  - Engagement of countries for Piloting actions (end of August);
    - Candidate countries to be contacted: AT, CH, SP, IT?, PT, GR, MT??, LU;
- Trillium Bridge
  - Working meeting 17th of July;
  - September (end) project review towards EC;
  - October 2014 US (Boston) Demonstration;

c) Support actions

Keep the distribution list from epSOS.
- Add new distribution lists from e-SENS (maybe a subset of WP5.2) and EXPAND (maybe WP5)
Certificates - NCP Installation
- Are there any news on AT issue:
  Jira Legacy
  server JIRA (openncp.atlassian.net)
  serverId 5eab37ce-f509-3cbb-9925-c13d0f8d6d44
  key OPENNCP-62

...

Licinio Kustra Mano Schedule next meeting: 21st of July (Monday) from, 14:30 to 16:00 CET (90min)
Licinio Kustra Mano: Update the Manifesto page with feedback after EXPAND WP5 KickOff;
Licinio Kustra Mano: Obtain EXPAND WP5 Proposals towards Governance and Manifesto;

...

previously identified actions - keep track

Schedule next meeting: 23th of June (Monday) from, 10:00 to 11:00 CET (60min)
Schedule next meeting: 16th of June (Monday) from, 10:00 to 11:00 CET (60min)
Licinio Kustra Mano: Schedule next meeting: 9th of June (Monday) from, 10:00 to 11:00 CET (60min)
Licinio Kustra Mano: prepare and circulate (for community review) the document "OpenNCP Community Manifesto" ,

Licinio Kustra Mano: Schedule next meeting: 3rd of June (Tuesday) from, 12:00 to 13:00 CET (60min)
Licinio Kustra Mano: Distribute editable roadmap materials, as well as ballpark estimate baseline numbers
Industry Team: Alexander Berler (Unlicensed) and Isabel Cruz: provide accurate estimates on time and costs (until 30th of May)
Licinio Kustra Mano: Compile and re-assemble presentations, making them available in PDF format.
Licinio Kustra Mano: Update the Athens event page with all the highlighs, so that the page can be distributed (with the PDF) for dissemination purposes.
Licinio Kustra Mano: CI proposal from eGOBLab: update Fredrik and request for advise on how to proceed;
Licinio Kustra Mano: CI recommend Portugal, to materialize the proposed and accepted by the PSB alternative, for holding the CI on their own;
Jürgen Wehnert: Disseminate epSOS information on certificates renewing possibility for the next 3 years
Licinio Kustra Mano: Make available the list of 15 Countries that shown interest in keeping the services running (included in the minutes)
Licinio Kustra Mano: Understand the AT team issues, and why they are struggling with certificates

...

Versions Compared

Old Version 3

New Version 4

Key

OpenNCP Community: Weekly meeting

a) Manifesto and Governance (feedback from EXPAND WP5 Kick Off)

b) Developments progress monitoring

c) Support actions

Page Comparison

Versions Compared

Old Version 3

New Version 4

Key

a) Manifesto and Governance (feedback from EXPAND WP5 Kick Off)

b) Developments progress monitoring

c) Support actions