Point of care Application
Restructuring daily care plans for improved relations between care givers & clients.
About this project
we designed an application together with healthcare providers in Söderhamn municipality, Sweden. During our course in participatory design we took the opportunity to break down and analyze the application Lifecare. This application is commonly used by several municipalities in Sweden to give healthcare providers an overview of their daily work tasks.
Our goal was to improve the interface in order to decrease the risks of human error and make the healthcare providers feel more safe while working with their care recipients.
In recent years several reports have been published regarding the stressful working conditions among healthcare providers around Sweden. The increased stress has led to decreased care for the care recipients and an increased insecurity among the healthcare providers. We realized that this was a complex problem and that it was a necessity to design the application together with the end users in order to optimize its usability. The end users in our case were health care providers in Söderhamn municipality, Sweden.
How can we reduce the number of mistakes made by the care givers, and make the care givers feel more secure with their tasks?
An application that allows the healthcare providers get a better overview of their daily tasks and potentially reduce stress.
In this project I was responsible for UX research, UX design and UI design, I planned for a Future Workshop and analysed the results as well as developing the design through wireframes, mockups and an interactive prototype. In addition I also prepared the material for user testing.
This project was conducted for educational purposes during my academic studies at Linnaeus University.
We initiated the design process by involving our users through a future workshop. The purpose of the workshop was to analyze the Lifecare application, fantasize about which functionalities the users would like to implement if they had no limits and create an action plan for what we could implement.
Our objective was to understand what issues the users were facing with the current application and what was needed in order to create a reliable work tool that would make their work easier.
What are the users saying?
After the workshop we analyzed the collected data in order to find themes that we could use as a starting point for the application requirements. We felt that the users had a lot of tacit knowledge in the area and it was essential for us to ensure that we developed an application that met their expectations.
THEMES & HIGHLIGHTS
The users wanted to be able to share information within the team, where they were located and how they were scheduled for the day.
An improved overview for their scheduled visits with a clear list of their tasks and potential updates in the care recipients routine.
A feature where the users could see a summary for any updates or changes that would affect their working day.
Analysing current tools
The healthcare providers in Söderhamn municipality use three different applications to complete their healthcare services. To get familiar with using point of care applications we analyzed their interfaces and functionalities. Additionally we researched the applications information architecture in order to get an insight of their terminology, labeling and used language. From the analysis we also found four key functions that we wanted to bring into our new application. In this step we also took into consideration what our users had told us at the workshop. These functions were:
See the daily schedule
Search for care recipients
Locking the screen
End the work shift/clock out
After the future workshop and the analysis of the current tools we continued making a requirement specification list for our application. This list made it clear what functions the application needed and helped us to start ideating on how the application could look like.
To start off the sketching process each team member sketched their own versions of how the application could look like. These sketches were then compared and our ideas were combined to one final sketch.
The combined sketches were then digitized into wireframes created on Figma. The wireframes helped us to create a clear structure and information architecture. The wireframes were then tested with the users. This was done before the UI design to assure that the structure was good and understandable for the users.
When the users had given their feedback on the wireframes we started to look at the visuals of the application. Each member of the team created their version of a mockup which were then discussed and combined into one single idea.
Testing the wireframe
In our first user test we wanted to evaluate the wireframes before we developed an interactive high fidelity prototype. The purpose of this method was to collect information on how the user interacted with the interface. This allowed us to identify problems early on in the design process. We conducted the user tests with three different users. During the test they followed a use case to perform certain tasks followed by a short interview with a few questions about their experience and opinions. This allowed the user to participate in the development of the application.
From the user tests we got some feedback about the color coding in the daily schedule. The colors that were used to differentiate between an ongoing and completed visit were unclear to the users.
The users pointed out that in order to start a visit with a care recipient they needed a function to “check in” at the care recipients home. This is a key function that needed to be implemented in our interface.
In order to create a digital representation of our interface we created a high fidelity interactive prototype in Figma. We took the results from all of the previous methods including the user feedback from the wireframe testing. To make sure we had resolved the pain points discovered by our users we conducted another user test with the prototype. This time the users followed the same use cases and then answered a System Usability Scale (SUS). The SUS gave us a quantitative measure of the users experiences.
What I've learned from this project
This was a very fun project and I gained experience from working with real users who were interested in improving their working tools. I believe the users participation was key to create a successful product since they have so much knowledge that we as designers don't have. Personally I also got to develop my skills in prototyping and visual design.