...
It is vital for the virtual development team to have the best possible tools available to them. During the epSOS project this requirement has been turned into reality. As per today the OpenNCP team commands a highly integrated and comfortable set of support systems including meeting support.
Code repositories and work support tools have been chosen and fed with information. The repositories are provided by the EU free of charge, the work support tool from Atlassian (https://openncp.atlassian.net/) also has no price tag attached to it as long as the development is limited to open source systems.
The Continuous Integration tool will be hosted held by the EXPAND project (until delivery to CEF or other bets suited organization)on an EU service ([http://www.egovlab.eu/) and/ or a PN's system, again no costs are expected. IHE is also preparing an offera proposal which will include the semantic servicesenvision to provide a neutral and impartial hosting place for various assets of epSOS in order to allow PNs to continue their cross border healthcare efforts. The offer is expected June 2014.
Costs have to be anticipated for Projectathon and Connectathon type events. A central support system (ticketing system) is in use within epSOS. It has shown that for the developers it is not of great importance, while for user support it may be necessary. It is expected that the free tool support system can be hosted by one of the PNs. Alternatively the feature can be integrated in the development support system on Atlassian, given it will be comfortable enough for end users (preferred route if sufficiently user-friendly).
Licinio Kustra Mano: proposed to remove next topic;
Development Scheme
Illustration 2 below provides the roadmap which has been discussed in the OpenNCP community. Release 3.0.0 is not to be seen as the last and final one, this is just how far the planning has progressed. 3.0.0 is considered to cause significant effort and its implementation depends on a decision to move to a decentralized solution for semantic terminology.
Illustration 2: Release roadmap OpenNCP (status May 2014)
Licinio Kustra Mano: proposed to remove next topic;
Effort Estimation
The effort estimation figures presented in the next tables should be used as baselines that can and MUST be revised as long as concrete actions start to be planned. While the presented estimates rely specifically on development activities, there are other organizational activities that, depending on the OpenNCP Community strategy, should be considered for determining overarching financing needs, namely: testing, IHE CAT participation, dissemination, marketing, project management.
Profiles | Person Number | Effort Allocation | TOTAL man/month |
Orchertrator | 1 | 40% | 0.4 |
Architects | 3 | 40% | 1.2 |
Developers (full time) | 2 | 100% | 2 |
Developers (part time) | 2 | 40% | 0.8 |
|
|
| 4.4 |
Time window | in months |
| TOTAL man/month |
July 2014 -April 2015 | 10 |
| 44 |
Financing | Number of Entities |
| Per entity (annual) |
Participation Nation or Projects | 10 |
| 50.000,00 € |
Rel. | EPIC | Details | days |
2.1.1 | XDM (IHE) - Cross-enterprise Document Media Interchange (Trillium Bridge scope) |
| 15 |
| CDA Display Tool Improvements |
|
|
|
|
|
|
2.2.0 | Error handling and messaging display in Portal |
| 25 |
| Testing Mechanism Improvements |
|
|
|
|
|
|
2.3.0 | eADC - Services for Visualizing and Export data |
| 10 |
| General Performance Improvements |
|
|
| Implement compliance with epSOS 2 Specs for XCPD, XCA, XDR transactions |
|
|
|
|
|
|
2.4.0 | Settings Manager (convention over configuration, overwriting only if needed) |
| 20 |
| Virtual Machine Image (prepare and make it available for download) |
|
|
| Services/Component Monitor |
|
|
|
|
|
|
2.5.0 | CTS2 Terminology Services |
| 100 |
|
|
|
|
2.6.0 | Extended Security Safeguards |
| 20 |
| e-Identification for Patients (e-SENS) |
|
|
|
|
|
|
2.7.0 | XCF (IHE) - Cross-Community Fetch | a) In the Patient Summary service XCF makes sense, so we should consider its implementation. b) Please note that XCF should not fully replace XCA, because XCF is not really a viable option in the ePrescription service | 30 |
|
|
|
|
2.8.0 | Enable the exchange of LABORATORY requests and results |
| 80 |
| Enable the exchange of IMAGIOLOGY related information (images and reports) |
|
|
|
|
|
|
2.9.0 | --empty so far |
| ? |
|
|
|
|
3.0.0 | Decentralized Terminology Services |
| 40 |
| Decentralized Connection Settings Services |
|
|
|
|
|
|
3.1.0 | Adapt OpenNCP gateway for usage beyond epSOS |
| 30 |
Quality Management
The management and assurance of the quality of new versions and releases of the OpenNCP itself but also that of the national integration has been queried by the reviewers of the fifth Annual Technical Review.
Quality management regards several aspects. epSOS developed rigid and comprehensive schemes and applied them rigorously. What worked in the beginning proved to be complicated and very time consuming towards the end of the project. This is because the number of piloting nations increased and e.g. the number of end-to-tests grew substantially.
Also it proved that a lot of the necessary know-how was either not present anymore (although available on ProjectPlace or in mails) or it could not be easily accessed because of new and thus inexperienced PNs; last but not least a number of the original "wisdom bearers" had left the project.
It is thus for more than one reason necessary to address various issues to ensure quality in a changing environment. None-exhaustive listing:
...