PROJECT AND CLIENT BACKGROUND
Care Quality Dashboard is a legacy project which has been previously developped by fellow UCL students under the university's Industry Exchange Network (IXN) programme. Our team has been given the responsibility of further extending this project to allow for more functionalities, which can hugely benefit clinicians at the National Health Service (NHS) Wales. In essence, our project aims to provide an interactive platform to allow clinicians from the said organisation to evaluate themselves accross different dashboards, other than just care quality alone.This should continuously improve the overall standard, accross different medical practices, provided to patients. Additionally, our system provides an intuitive approach to enable Head-of-Departments monitor the progress of clinicians within their department. Our client is Dr Joseph Connor who is acting on behalf of NHS Wales, which is the public healthcare system responsible for providing accessible healthcare services to the 3 million residents of Wales and they have requested some additional features to be built upon the first edition of a long term project.
PROJECT GOALS
REQUIREMENTS
The requirements of our project as listed below are acquired from semi-structured interviews with pseudo-users to help us determine the direction of our project development. For the interview, we prepared a set of open-ended questions to be asked to our users as this type of questions can help us better understand the needs of their needs. All our interviews were conducted in-person or online and all answers were recorded. After gathering our requirements, we discussed our findings in a group meeting to evaluate the important features that our website should include, as needed by the users. This can ensure a user-centric final product is produced. The main requirements we gathered can be categorised as follows:
TIME MANAGEMENT

Saves a lot of clinicians' valuable time by having an easily-navigable interface for self-evaluation

SUPERVISION

Allows Head-of-Departments to supervise clinicians for continued improvement in care quality provided

USABILITY

Multiple dashboard feature which allows different medical practices to assess staff across different departments

PERSONAS AND SCENARIOS
Before beginning to design the dashboard, it is imperative to determine its main types of users or personas because this can ensure that our project design is in accordance to their needs. Based on our interviews with the pseudo-users, we conluded that the main users of this dashboard are regular clinicians and head-of-departments. Next, we proceeded with developping scenarios on how the personas will make use of our interface. The personas and scenarios for our project can be simplified as per the diagrams below:
USE CASES DIAGRAM AND LISTS
Below are the use case diagram and use case lists of our project that we produced in order to further understand the requirements of the project. It also helped us define permissions and use cases for each type of user who will be expected to use the system.
Use Case Diagram
MoSCoW LIST
The MoSCoW requirements list is a methodology that we followed during development in order to list out all the required features to be developed in order of their importance. This way, we can focus on finishing the more important criteria given by clients first before proceeding to other less prominent features. Our MoSCoW list can be seen below and our requirements are categorised into functional and non-functional requirements.
Functional Requirements
Number Requirement Priority
1 Multiple Dashboards Feature Must Have
2 Create Read Update and Delete Dashboards Feature Must Have
3 Improve User Interface to be useable for desktop and mobile devices(responsive) Must Have
4 Department Managers create new dashboards for all clinicians within a department Must Have
5 Clinicians and department managers are able to answer likert scale questions for their self-assessment Must Have
6 Clinicians and department managers can visualise their progress via a line chart Must Have
7 Clinician self-reporting results remain anonymous. Must Have
8 Platform Administrators should be able to add new hospitals and healthboards Must Have
9 Platform Administrators create new dashboards for all departments on the entire system Should Have
10 List of dashboards should be easily accessible by being searchable Should Have
11 Test front-end, backend and end-to-end(e2e) Should Have
12 Include non health and care standards Won't Have
13 Non Likert-Scale questions for the self-report Won't Have
Non-Functional Requirements
Number Requirement Priority
14 New Entity Relation Diagram Must Have
15 Include deployment Documentation Must Have
16 The System must have a user manual to help assist navigation of the website Must Have
17 Re-new prisma schema for more than one dashboard rather than just care quality alone Must Have
18 Include a simple User interface Should Have
19 Secure Platform to Avoid Data Breach Should Have
Copyright © 2021-2022 CareQualityDashboard, UCL IXN Team 13. All Rights Reserved.