Goal
- E.g. Simplify the user experience, reduce friction etc...
Background and strategic fit
Why are you doing this? How does this relate to your overall product strategy?
Assumptions
- List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this feature from a tablet).
Functional Requirements
| # | 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) | Observations |
|---|---|---|---|---|---|---|---|---|---|
| 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 | 2015 | Needed a CLEAR PICTURE on what to implement. | |||||
| 2 | eID Patient Identification - integration with OpenNCP (from e-SENS) Level 1 (LARMS) and Level 2 (LAM). | In Progress | 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 | - | To be better described | |||||
| 6 | Centralised GUI - configuration properties change (GUI for epsodb) | In RoadMap | - | 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 | - | 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 | 2016 | ||||||
| 9 | TSAM Synchronization refactoring (it needs a number of hours for a synchronisation) | In RoadMap | 2015 |
*Type: New feature; Improvement; Bug Fix;
- Beyond Patient Summary and ePrescription use cases
| # | Requirements | Short description | Type* | Business Value (0-lower 5-higher) | Effort needed (in hours) | Timeline (2015 or 2016) |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
| 3 | ||||||
*Type: New feature; Improvement; Bug Fix;
Non-Functional Requirements
| # | Requirements | Short description | Type* | Business Value (0-lower 5-higher) | Effort needed (in hours) | Timeline (2015 or 2016) |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | ||||||
*Type: New feature; Improvement; Bug Fix;