09.00 - 09.30 | Welcome coffee and registration |
09.30 - 09.40 | Welcome and introduction | Dietmar Gattwinkel (CEF eDelivery Business Owner, DG CNECT H4) | | - Dietmar welcomed the participants and introduced the agenda for the day, asking participants whether any additions should be considered.
|
09.40 - 10.40 | Round table: sharing of eDelivery status at national level The Workshop participants are invited to present the status on eDelivery implementation at national level. | Participants to the Workshop | Denmark (DK) - Denmark is using eDelivery in the context of PEPPOL for eInvoicing and eProcurement. Authorities are connected for receiving invoices using the European Standard. Denmark has been preparing a national eDelivery implementation and have also made a decision to do a pilot implementation of a central SMP service and a trust-list schema for using the national eID certificates with eDelivery.
- There are as well some sectorial eDelivery implementations supporting cross border.
- The national eID scheme (under eIDAS) has not been notified but it is rightly used. It is secure and wide spread despite not being notified. It is mandatory for self-service using government services both for citizens and businesses. There is also preparation ongoing for the next generation and some activities will be conducted in the next few years.
- There is a plan to implement eDelivery in healthcare services in Denmark for the exchange between hospitals and municipalities. There is also a foreseen potential for exchanging information across domains. The question is not whether to use eDelivery but rather how to use it.
Germany (DE) - Uptake of PEPPOL in Bremen and the Federal government for eInvoicing. Bremen and the Federal government decided to make eInvoices mandatory starting from 1k EUR.
- eDelivery AS4 is currently being evaluated as the exchange system of choice for interoperable digital public service in Germany.
Croatia (HR) - Increased focus on the CEF programme as Croatia is taking over the Council presidency.
Lithuania (LT) - No major changes since last meeting. Lithuania has now a fully operational eInvoicing system that relies on eDelivery. Working to encourage public institutions to make the use of AS4 mandatory for suppliers in order to further automate invoice processing.
- National eInvoicing system is now under the governance of a newly created organisation that provides centralised and more streamlined accountancy service to other institutions.
- Plans to translate the eInvoicing standard to Lithuanian standard. No more than 100 eInvoices were shared using eDelivery infrastructure but some growth is expected.
- Lithuania is participanting in the Nordic-Baltic procurement network - this will most likely encourage recognition of benefits by the national government.
Luxembourg (LU) - No major changes since last meeting. Luxembourg is still using PEPPOL in the context of eInvoicing and also some other eDelivery Access Points in the context of European Projects (e.g. BRIS). Currently analysing how they could extend the use of PEPPOL in procurement, for, e.g. post award phase.
Austria (AT) - Austria is launching an eDelivery system by end of November 2019 relying on a 3-corner model with a central system where messages are fetched from providers. However, the system does not yet support AS4 as it starts with a protocol that was already used in Austria for backward compatibility. There will be a potential support for AS4 in the future. Austria is considering the interconnection of the system in the context of eIDAS and is interested in funding to do so.
Norway (NO) - eDelivery is the backbone of secure mail in Norway.
- Norway just started the production of eDelivery usage for inter-bank communication and payment instructions from public entities to banks and for tax authorities for accessing and controlling accounts in the banks.
- There are a few interested parties in Norway that would like to work on blockchain.
NIIS - NIIS has been working on a X-Road eDelivery gateway solution. However, there are still questions to be solved, especially related to non-repudiation within the message chain.
Netherlands (NL) (by RINIS Foundation) - eDelivery is currently in place for some services, such as eJustice, eCodex, BRIS.
- RINIS is currently building a SMP service on top of the eDelivery national gateway for the use within the Netherlands.
- Currently implementing eProcurement at national level by using the eDelivery building block.
- The Netherlands is preparing with Belgium an eConfirmation pilot (i.e. for access to medical care when abroad by using the eHealth insurance card, with eConfirmation providing a real-time verification of the citizen's status as a patient).
- Testing eTranslation eDelivery access point with DG CONNECT.
Belgium (BE) - Belgium is ramping up on eDelivery installations. Connecting eInvocing with the citizen eBox (citizen documentation exchange platform). eDelivery will allow for citizen documentation to be directly delivered to the citizen eBox. Belgium will be launching a SMP/SML service for companies. Need to also ensure compliance with eIDAS.
Finland (FI) - Finland is using X-Road at national level for information exchange. Interested to get eDelivery and X-Road working together.
- Finland is also using PEPPOL.
Sweden (SE) - Sweden is planning to have a central SMP, which is going into production next year.
- Sweden is highly involved in PEPPOL.
- There is interest from different national authorities who want to use eDelivery to exchange messages among themselves. It is foreseen that eDelivery will have an increasingly bigger role in the future.
- High interest in APIs.
- Have prepared a report on the implementation on eDelivery (available in Swedish).
UK - Use of PEPPOL in the healthcare sector and the UK national grid uses AS4.
- However, UK is interested in secure message exchange and in learning experiences and best practices from other countries.
|
10.40 - 11.00 | Updates on CEF eDelivery | Ines Costa, Maarten Daniels, Pim van der Eijk (CEF eDelivery team) | - Cf. presentation attached.
|
11.00 - 11.15 | Coffee break |
11.15 - 12.00 | 'Secure Digital Communication' project - eDelivery for user to organisation exchanges | Martin Volcker (Swedish eDelivery coordinator, DIGG - Agency for Digital Government) | | - Cf. presentation attached.
- Key conclusion is that the main challenges are not related to technology itself but rather to organisational aspects, such as existence of organisational guidelines and rules, business models, legal agreements.
- The project will be piloted during 2020 with some organisations. The specifications will evolve during this period. By end 2020 these will be more mature and can then be shared.
Notes from discussion: CZ: Is it just for delivery or does the system allow for archiving of messages? A: The idea is to see this as a post office/message transportation service. It is the sender and received who handles/are in charge of the archiving aspect. DK: To add, DK is also preparing for new generation of such networks. Previous week they had a workshop on the possibilities of creating connected digital post solutions. There was a consensus that this is not so hard to do on a technical basis with eDelivery as a preferred infrastructure. Something that could be extended across all EU Member States. Standardisation is crucial, especially as an enabler for the Single Digital Gateway. LT: Lithuanian representative asked what would be the benefits of using this infrastructure against simple emails or other similar already existing solutions. A: This goes beyond two persons, there is a central address box, connecting thousands of organisations, which is secure. The idea was to look like email for the purpose of user centricity, but it is of course more secure and it is a flexible, well integrated solution. EC: Does this support also citizens contacting specific offices? This is still an ongoing discussion, even though this is technically feasible (as some agencies want citizens interacting through eServices). EC: What is the reusability of this? Pilot in 2020, which will allow to learn further and refine specifications. This perhaps would be a better stage for sharing. EC: In the eIDAS Regulation there is currently no obligation for ERDS systems to be interoperable. This is something that might be reviewed under the upcoming evaluation.
|
12.00 - 13.00 | Lunch |
13.00 - 14.40 | - Working group 1: Possible use of APIs in/or without eDelivery
- Working group 2: How to leverage Blockchain technology within eDelivery
| RINIS Foundation Sven Rasmussen (Danish Ministy of Finace, Agency for Digitisation) Dietmar Gattwinkel (CEF eDelivery Business Owner, DG CNECT H4) Joao Rodrigues Frade (Head of CEF building blocks sector, DIGIT D3) | | Working group on APIs (notes on discussion) EC: Cooperation with Member States is at the core of the ISA² proposal. However, agreement on specifications is the first step. This was the case with eDelivery where Member States drove the choice for the AS4 protocol. A similar approach should be taken with APIs, including: analysis of landscape on what exists, (building on the API4DGOV study) discuss and agree on what is relevant to be able to building a comprehensive list of current initiatives with the support of Member States. Synergies with ISA² initiatives such as the Core Public Service Vocabulary (CPSV-AP) for a practical implementation and the use Common assessment method for standards and specifications (CAMSS) must be taken into account to support cross-border interoperability. - CZ: Layout out of the business process should come before specifications.
- DK: JRC study is a good starting point and it contains many use cases demonstrating implementation of APIs. Before specifications, one should also consider the architecture. eDelivery, for example, is much more than AS4, it is a package of components with a number of needs-based reusable elements. For the project to have value, the group should start by recognizing that REST is mature.
- AT: We are always considering abstract use cases that can then be implemented across sectors. With regard to architecture, APIs would be added as an additional eDelivery component.
- LU: Welcomes the initiative.
- FI: Perhaps first there is a need for generic specifications and user needs' mapping.
Working group on Blockchain (notes on discussion) - EC: We can see blockchain as a possible log of transactions taking place across the eDelivery network.
- AT: Implemented a blockchain solution with eDelivery to track the transactions in a eDelivery network. Details to be shared with the group.
- DK: eDelivery should be deployable without APIs and vice versa so that the possibility to use different configurations remains.
|
| 14.40 - 15.10 | Coffee break |
15.10 - 16.40 | Working groups: next steps | Workshop conveners and participants | n/a | Main takeaways: - There was an agreement that the starting point should be to have a common working group while the scope is still being defined as it will allow everyone to contribute to both subjects.
- Interested group members: DK, NL, EE (X-Road team would like to be aligned and compatible), NO, SE (currently working on the national strategy on APIs), CZ, LU, FI, DE.
- eDelivery is not only the AS4 specifications but it is also an architecture framework and a collection of components (e.g. AP, SMP, SML, certificate service, etc.). The approach to the APIs work should follow the same approach and be included as part of the eDelivery components.
Next steps: - Build comprehensive list of info sources on standards and technical specifications that CEF can consolidate in a page in the user community, pointing out the specific use cases for each of the specifications. This should be complemented with a view on the needs that are not yet covered by eDelivery and how APIs and Blockchain could cover those needs.
- SE would like to set up an informal group on Digital Post, which could communicate through Joinup (AT, NL, DE, DK, FI showed interest).
- Follow up meeting to be planned in January/February 2020 (incl. half day of presentations by EC projects using eDelivery).
|
16.40 - 17.00 | Wrap-up & closing | Joao Rodrigues Frade (Head of CEF building blocks sector, DIGIT D3) | - There is an interest in having more informal meetings that participants can join via videoconference as well. The topics for these meetings could be proposed and decided upon by the network itself.
- Joao thanked the participants for their enthusiasm and interest in following up the work on APIs and Blockchain and highlighted the 'next steps' defined.
|
2 Comments
Peter Danko
Will be this Event streamed online?
Thanks,
Peter Danko
Ines COSTA
Hello Peter Danko,
No, this event will not be web streamed.
Best regards,
Ines