Our project builds upon the work of performed by Team 20 during the 2020/21 IXN
cycle.This work can be
found hosted at: https://clarionclinical.net/
1,2.
Our first step in our research involved analysing the existing system, taking the following steps:
This initial review identified 4 core strengths we could harness and 4 weaknesses which, if addressed, would result in a more usable, useful and efficient system.
Clinicians and managers appreciate the current statistics view, it provides a clear and immediate picture of the past and present, it also allows for easy filtering of results.
Like the statistics page the self reporting page is clear and effective. It is easy for clinicians to complete their assessment in minutes
The current system allows user to complete self assessment forms within the context of mentorship sessions
(where users are paired with their managers and can discuss each question).
This is reflected by a checkbox. Mentorship sessions are visualised in the statistics page using a separate
icon.
The current system possesses a powerful visual tool in the form of a wordcloud. When completing a self-assessment form, clinicians can enter “Enablers” and “Barriers”: words which represent current positive and negative feelings. These can be seen by managers to get a quick picture that reflects the clinicians’ current mood.
The biggest pain point in the existing system is the user onboarding. Each user account needs to be
created
individually by the system administrator, this involves assigning a temporary password which needs to be
handed over securely to the user. There is also no prompt upon login to change this password, as a result,
it is thought that many users will keep this password permanently.
Altogether, this results in a complex and time consuming process. Stakeholders suggested registration
could
be deferred to users and approved by the admin, resulting in a more efficient system.
Another issue is the current lack of an adequate role hierarchy to represent the real-world usage. The system currently has department and hospital managers but is missing team managers: a key role which is the primary supervisor and point of contact for clinicians.
The system has been well received by stakeholders, as a result, users would like to apply this for multiple different form types, in addition to the Care Quality Framework.
Maintaining the system and implementing new features requires a level of technical expertise which can represent a barrier for most users. When running the system we noticed many of the dependency packages used were outdated and presented severe vulnerabilities.
These 8 points represent key takeaways resulting from multiple conversations across the user spectrum. We will now look into applying these findings when designing our extension to the system.
The initial intention was to expend the existing system's functionality. However, after consulting with stakeholders, in particular system administrators, we realised the complexities of deploying the current system within the Welsh NHS environment. Additionally, users were vocal about the possibility of extending the system themselves, creating new pages and views in the future, without the need for much technical knowledge.
After considering this feedback our client proposed an alternative approach using low code tools. This
would allow users to easily maintain the system both at a technical and non-technical level. Providing a
number of advantages, including:
As a result, the first step in our research involved investigating the suitability of different low-code platforms5.
Retool6 is a platform which allows users to build custom internal tools and applications for
their
businesses.
It supports a wide range of data sources and integrations, including databases (such as MySQL, PostgreSQL,
and
MongoDB), APIs (such as Stripe, Twilio, and GitHub), and more. Custom workflows can easily be built by
connecting these data sources and services.
As a tool, it is more suited to create management dashboards and is intended for use within internal
applications. As a result, users must be signed-up by an administrator, this means it is not-ideal to
accomplish our self-registration goal.
Microsoft Power Apps7 is a low-code platform that allows users to easily create custom business
applications
without the need for extensive programming knowledge. It platform provides a range of pre-built templates
and
components, which can be extended through custom code blocks.
One of the main disadvantages of the suite is its licensing: a license is required for each user of the
system, this can be a financial and maintenance burden. It also increases vendor lock-in, which could
prove
to
be problematic should the pricing structure change or a better solution come along.
Softr8 is a low-code environment allowing
users with
no programming experience to use
it with ease, making it an ideal choice for the client. Softr is a powerful tool with a vast selection of
built-in “blocks” which are the key elements in building a platform/website.
We will try to replicate and extend the previous system using these blocks however Softr also gives
the option of a “Custom code block” which we will utilise when the builtin blocks are not functional for
the task, for example we will be using the code block for the charts as the graphing block in Softr is
quite limited.
Softr can also be integrated with OpenId which allows
for federated authentication,
allowing users to use third-party applications to authenticate themselves.
Airtable9 is the industry standard for
building
databases without any prior coding/programming experience. One
of the main advantages is its extensive community support and out of the box Softr integration.
Data from the database can be then visualised using powerful extensions in Airtable such as Vega lite.
Repetitive tasks can also be automated in Airtable using Airtable’s builtin automations which allows users
to
create rules that automatically trigger specific actions.
Overall Airtable provides users with the freedom to view and edit tables autonomously.
We investigated various charting libraries to display self-reporting statistics across a variety of user
groups. As part this research we tested and evaluated each library according to the following metrics:
Statistics in the original system were visualised using Chart.js, this free and open source library offers a variety of customisable visualisations, plenty of documentation and examples and a solid community support. As a result, we have decided to confirm this choice for the current system.