Adobe, the Adobe logo, Acrobat and Adobe Connect are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. ----------------
Technical Requirements List FROM the eHealth domain, for SMP provision:
MANDATORY
R1. The TSL (Certificates, End Points), epSOS 3.3.6 ???;
R.2 The International Patient Search Mask (what the format intended);
OPTIONAL
R.3 Store OpenSwan Config in PRIVATE area;
R.3.1 PRIVATE area means of AuthN & AuthZ;
The SMP/SML integration on eHealth Cross Border Services (document)
The eHealth requirements, detailed and recovering the epSOS Central Configuration Services requirements;
An assessment (legal, organisational, technical) on why the current SMP/SML implementation cannot address the pointed requirements;
Propose on a possible evolution proposal of SMP/SML, to be considered by the service provider; Regarding "OpenNCP integration with SMP",
requirement gathering and impact assessment should be consolidated, communicating clearly constraints and possible solutions for the future;
development activities should be placed in stand-by mode until SMP/SML service provision is fully align with the eHealth requirements (e-SENS Pilot end - March, 2016);
(development activities should focus the integration of Electronic Patient Identification BB);
Alert EXPAND that Central Services (Configuration) are crucial for e-SENS pilots and CEF eHealth service deployment.
The current contract with the vendor providing the central services, will end September.
Technical Requirements List FOR OpenNCP adoption:
TSL files should be removed and replaced by SMP Signed Information files.
(Maybe not to delete the TSL EDITOR, explore TSL EDITOR to prepare the information to submit to the SMP )
INTEGRATE a REST client to CRUD the information...
TSL EDITOR should be enhanced for "Configuration Editor" and produce any type of config file "TSL" but we are pointing to the "SMP SignedInformation files"
OpenNCP Technical Specification (refactoring):
OpenNCP modules refactoring:
OpenNCP test plan recommendation:
OpenNCP QA (should be performed by PNs), since no central NCP is available, or maybe we can use the EC NCP for this QA stage before release for PNs.
OpenNCP Release (unleash the e-SENS Health Pilot 2º stage..... as well CEF compliance)
4. AOB
Massimiliano Masi: Did you think to use any tool like vagrant or puppet for the automatic deployment of the OpenNCP?
OpenNCP integration with SMP: proposed date - Thursday, Jul 9th 14:00 CEST