Proof of Capability Requirements
The Proof of Capability requirements for the DSIC Onboarding Toolset are captured here.
These requirements are not intended to be finalised and further refinement is needed, particularly for the Non-Functional Requirements which are currently in a non-measurable state of development.
The Proof of Capability requirements are intended to indicate, in brief, the expectations of any Onboarding Toolset. They will also provide a reduced set of requirements which can be used to inform the DSIC Programme whether a candidate solution will be able to meet the most fundamental functions.
A more complete set of MVP requirements will be delivered in due course to Providers whose products are selected for further consideration.
User Management
Requirement ID | Requirement Name | Requirement Description | Actors | Priority |
---|---|---|---|---|
Supplier records and Supplier Users Accounts | ||||
POC-UM001 | Create Supplier record | Create a Supplier record which includes Supplier information and metadata (e.g. Supplier name, address, primary contact). | NHS/Supplier | MUST |
POC-UM002 | View Supplier record | View the Supplier record. | NHS/Supplier | MUST |
POC-UM003 | Create Supplier User | Create a user account for a Supplier user.
| NHS | MUST |
NHS User Accounts | ||||
POC-UM004 | Create NHS User | Create a user account for an NHS user.
| NHS | MUST |
Framework and Requirements Management
Requirement ID | Requirement Name | Requirement Description | Actors | Priority |
---|---|---|---|---|
Manage Capabilities available to select | ||||
POC-FRM001 | Add new Capabilities | Create a new Capability and Epic(s).
| NHS | MUST |
POC-FRM002 | Update Capabilities | Epic can be added to/removed from Capabilities.
| NHS | MUST |
Manage Frameworks available to select | ||||
POC-FRM003 | Create Frameworks | Create new Framework which can be selected and applied to Solutions. Creating a Framework involves defining its content:
| NHS | MUST |
POC-FRM004 | Update Framework content | Update a Framework’s content:
| NHS | MUST |
POC-FRM005 | Enable/disable Frameworks | Enable/disable a Framework as a selection available to Solutions.
| NHS | MUST |
Solution Registration
Requirement ID | Requirement Name | Requirement Description | Actors | Priority |
---|---|---|---|---|
Add new Products (Solutions and Additional Services) | ||||
POC-SR001 | Add new Solutions | Add a new Solution to a Supplier record.
| NHS/Supplier | MUST |
POC-SR002 | Add Additional Services to a Solution | Add 0+ Additional Services to a Solution.
| NHS/Supplier | MUST |
POC-SR003 | View Solutions and Additional Services | View the Solutions and Additional Services registered with a Supplier. | NHS/Supplier | MUST |
POC-SR004 | Track Progress | View any tasks which are outstanding that are associated with the Supplier record or Solutions. | NHS/Supplier | MUST |
Select Frameworks for Solutions | ||||
POC-SR005 | Select Frameworks for a Solution | Select a Framework for a Solution. Frameworks determine the Capabilities and Standards that must be delivered by the Solution. | Supplier | MUST |
POC-SR006 | View Capabilities and Epics in Frameworks | View the Capabilities and Epics that are within the scope of the selected Framework. | Supplier | MUST |
Select Capabilities and Epics for Products (Solutions and Additional Services) | ||||
POC-SR007 | Select Capabilities and Epics for Solutions | Select the Capabilities and Epics that the Solution, and any Associated Services, will be assessed against.
Additional Services are expected to provide additional functionality over and above that provided by the Parent Solution. If the same Capability and/or Epic is selected for both the Solution and for an Additional Service, this will be reviewed internally and queried - the only circumstances this would be permitted is if the same functionality is delivered in different ways. | Supplier | MUST |
POC-SR008 | View Selected Capabilities & Epics | View the Capabilities and Epics that are selected for the Solution and any Additional Services. | NHS/Supplier | MUST |
Respond to Preliminary Assurance Requirements | ||||
POC-SR009 | Record responses to Preliminary Assurance requirements | Questions will be presented to the user that they can respond to. | Supplier | MUST |
POC-SR010 | Record additional responses based a preceding question | Additional questions may be displayed based on the response to a preceding question (e.g. dates, space-limited explanations). | Supplier | MUST |
Requirement Response Types | ||||
POC-SR011 | Restricted Selectable Options | Users can select from a limited number of options that encompass the possible responses to the requirement (e.g. does the Supplier have a Clinical Safety Officer, yes or no?). | Supplier | MUST |
POC-SR012 | Restricted Text Inputs | Users can input text in a short, controlled format (e.g. dates, document numbers, version numbers).
| Supplier | MUST |
POC-SR013 | File Upload | Users can upload files as evidence.
| Supplier | MUST |
Solution Registration submission and review | ||||
POC-SR014 | Submit Solution Registrations for review and approval | Submit the Solution Registration information for review and approval.
| Supplier | MUST |
POC-SR015 | View all Solution Registration review tasks | View all Solution Registration submissions that have not yet been approved or returned to the Supplier with feedback. | NHS | MUST |
POC-SR016 | View Solution Registration submission | View all Solution Registration submission information, including…
| NHS/Supplier |
|
POC-SR017 | Record notes on Solution Registration submissions | Record notes for the submitted Solution Registration submission, including…
Notes may be captured for individual parts of the submission or to the submission as a whole. | NHS | MUST |
POC-SR018 | Approve or reject Solution Registration submissions | Approve or reject a Solution Registration submission.
| NHS | MUST |
POC-SR019 | View reviewed Solution Registrations submissions | View the approval/rejection outcome and any notes for the submission. | NHS/Supplier | MUST |
POC-SR020 | Access uploaded files | Download uploaded files. | NHS/Supplier | MUST |
Solution Registration amendments | ||||
POC-SR021 | Amend rejected Solution Registrations | The Solution Registration can be amended if the submission is rejected.
| Supplier | MUST |
POC-SR022 | “Unlock” and “lock” approved Solution Registrations | Approved Solution Registrations can be unlocked to allow amendments, and locked to prevent further amendments.
| NHS | MUST |
Proof of Capability Non-Functional Requirements
Requirement ID | Requirement Name | Requirement Description | Actors | Priority |
Look and Feel | ||||
POC-NFR001 | Toolset interface clarity | The toolset will have a clean and professional appearance. | N/A | MUST |
POC-NFR002 | User IT proficiency | The toolset must be accessible to users with basic IT proficiency and who are not technically trained.
| N/A | MUST |
Usability and Human-Centred Design | ||||
POC-NFR003 | Prevent invalid data and file types | The toolset must prevent invalid data from being input and invalid file types from being uploaded.
| N/A | MUST |
POC-NFR004 | Accessibility | The toolset meets a range of accessibility needs.
| N/A | MUST |
Performance & Capacity | ||||
POC-NFR005 | Data backup and recovery | The toolset must back up all data to avoid data loss and include a recovery service to restore data from backups. | N/A | MUST |
POC-NFR006 | File storage | The toolset must EITHER provide file storage capabilities, OR facilitate reliable integrations with a file storage solution. | N/A | MUST |
Operational | ||||
POC-NFR007 | Web based | The toolset must be a web based solution. | N/A | MUST |
POC-NFR008 | Browser compatibility | The toolset must be usable on a range of web browsers (e.g. Internet Explorer, Chrome, Safari, Firefox). | N/A | MUST |
POC-NFR009 | Immediate publishing of submitted changes | The toolset must immediately publish any changes submitted by a user without delay, so that other authorised users can see the immediately see the changes. | N/A | MUST |
POC-NFR010 | Test Environment | The toolset must have a test environment in which changes to the content and order of activities can be tested before release. | N/A | MUST |
Maintainability and Support | ||||
POC-NFR011 | Regular Updates | The toolset will be capable of supporting regular changes to the content and order of onboarding activities, as required by a range of causes. | N/A | MUST |
Security | ||||
POC-NFR012 | User authentication | The toolset must require users to be authenticated against a unique user identity.
| N/A | MUST |
POC-NFR013 | Password authentication | If authenticating through the use of a password, the toolset must include…
| N/A | COULD |
POC-NFR014 | Role-based Access Control | The toolset must deliver role-based access control to be used to enable and disable a user’s access to features and data in the toolset.
Note that the Programme may wish to prevent Supplier users from adding their own products (Solutions and Additional Services) and have these actions performed by NHS staff on the Suppliers' behalf. | N/A | MUST |
POC-NFR015 | Cyber Security | The toolset must be capable of protecting itself against malevolent software, cyber attacks and other hostile actions. | N/A | MUST |
POC-NFR016 | Data Integrity | The toolset must maintain the integrity of the data that is stores to ensure that it is protected from corruption and misuse, i.e. data must be stored as it was originally received. | N/A | MUST |
POC-NFR017 | Audit Trails | The toolset must keep a clear and easily understandable audit trail to allow complete verification of its operations and data.
| N/A | MUST |
Legal | ||||
POC-NFR018 | Data Protection and Internet Security | The toolset, and process for using the toolset must:
| N/A | MUST |
Supporting Functions
The below functions are generic and might be considered “quality of life”. They are not required for “Proof of Capability” or the MVP, but would would be considered an advantage if a toolset can offer these functions, and they are likely to become important for long-term development goals.
User notification functionality (e.g. popups, emails) informing a user when a change is made to a Solution or when a task required attention.
Reporting and Dashboarding functionality which provides insights into the usage and workloads in the toolset, such as pipelines.
Workload Management functionality (e.g. assigning tasks to users, deadline warnings, prioritisation of tasks) which allows users to coordinate and allocate responsibilities and priorities.