...
| # | Requirements | Status | Short description | Type* | Business Value (0-lower 5-higher) | Effort needed (in hours) | Proposed Timeline (2015 or 2016) | Timeline Expectation (2016 or 2016) | Obs. |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Non-Repudation token creation, integrate with a repository to keep these records and build also a UI for viewing and exporting them. | In Progress | The non-repudiation token are being created during all IHE requests (XCPD, XCA) and portal (NCP-B) requests and for now being stored in filesystem. They should stored in database and give an easy way to administrator to browse and search or export them. | New Feature | 2015 | Needed a CLEAR PICTURE on what to implement. | |||
| 2 | eID Patient Identification (from e-SENS) | In Progress | Integration with OpenNCP Level 1 (LARMS) and Level 2 (LAM). | 2015 | |||||
| 3 | SMP Integration with OpenNCP (from e-SENS). | In Specification | 2016 | ||||||
| 4 | CTS2 compliance in:
| In RoadMap | 2016 | ||||||
| 5 | Centralised GUI - for invoking epsos services like:
| In RoadMap | The TSAM Sync and TSAM export are epsos utilities that only can be run from command line. It would be easier to create a contol center from which all these activities could be executed and logged. We could keep some execution details such as execution date, user has started the execution, result of execution. We could also add notification services for the status of the execution in order the administrator to be notified | - | To be better described | ||||
| 6 | Centralised GUI - configuration properties change (GUI for epsodb) | In RoadMap | In the current situation the configuration parameters (epsosdb) is being changed by getting access to mysql. We should create a small application/portlet for CRUD operations in epsosdb database and also keep log of changes being made in this database | New Feature | - | To be better described | |||
| 7 | Centralised log for all the epsos activities (possible extension of audit logs), and UI for browsing this log | In RoadMap | It is in relation with previous (point 6) of roadmap. If we manage to handle all epsos activities from a gui, then it would be useful to have a centralized log to see the status of all executed services and the heartbeat of the services. | New Feature | - | To be better described | |||
| 8 | eADC (Automatic Data Collecter) improvements to keep useful information. It needs to be revised what is kept now and maybe be extended
| In RoadMap | eADC, is a component made for keeping statistics about transactions made from/to countries. It has to be rescheduled in order to keep valuable data like: Home Country, Remote Country, Type of Query/Action, role of the user made the action, duration of the query. We have to think if we want to keep data of the queries made (such as patient data and documents data). This is much related the purpose of the statistics. | Improvement | 2016 | ||||
| 9 | TSAM Synchronization Refactoring (it needs a number of hours for a synchronisation) | In RoadMap | 2015 |
...