My Health - the digital health record
Lean UX • UX Design
The Project
My Contribution
This project should be conceptually and prototypically implemented using methods such as Lean UX, a project as group work. The topic of our group was the digital patient record from the patient's point of view and the protection of patient data.
We were team of four design students. Everyone participated included everything from finding the problems, mapping the use journey, ideating a solution, formulating and designing the prototyping.
The Topic
Before the group work could begin, we had to agree on a topic. As a group, we chose the topic "patient record from the patient's point of view", a topic that has not been touched for many years in hospitals and clinics. Doctors still use age-old systems and patients do not even have the chance to see their data. A patient has no overview of the data collected about him. At this point, we wanted to build on and create something for the patient, which supports him in his visits to the doctor.
Method "How Might We" Questions
In the style of Lean UX, we first formed the "how might we" questions to better understand our problems and requirements.
Here are the questions we have formulated:
How might we...
- ... help the patient to easily give his data to all doctors?
- ... help patients structure and structure their data and their course of illness meaningfully and clearly?
- ... help the patient to have his data ready at all times?
- ... protect the patient's data?
- ... present health information on time and easily?
User Journey
To better understand the potential problems, pain points, and needs of a doctor's visit to a patient's perspective, we created a Persona and a User Journey. Persona: Matthias Schmidt, 31 Matthias has been back pain for a while and decided to visit a doctor. But he finds questionnaire at the doctor's visit annoying and can rarely answer all questions exactly because he does not have some information. He would like to have an overview of his doctor's appointments, the course of the illness, as well as medication compatibility in order to better organize and have his health information available. He is interested in knowing who has access to his information.
↑ in this user journey:
Yellow: course of first time back pain until treatment with the doctor Pink: Pain Points
Blue: Opportunity Points
It will be .... an app!
Since the constant availability of the data was very important to us, the choice of the target platform quickly fell on a smartphone app. You always have a smartphone with you. And thus also his patient file.
Feature List
Next we had to decide which features should be included in our app. We made a list of all the features we discussed and chose those that seemed relevant to our current state. In this step, we sorted out features like "Data Transfer via NFC" or "The Translator" to make our app leaner. Important features included "the digital questionnaire" or "the drug archive".
Low-Fidelity Prototype
In this step, each person in the group created a paper prototype. These should visualize our ideas of the final product. So that we can start directly with several ideas and designs, we decided that each person from the group first visualizes his ideas alone and presents them to the other group members at the next meeting. This had the advantage that we could work impartially and at the end of the many individual prototypes could create a common. This contained the advantages of its predecessors.
High-Fidelity Prototype
Paper prototypes are nice and good, but better are interactive prototypes. The tester gets the feeling in an interactive prototype that it uses the real app. This will also affect the feedback. So you can go into the feedback in detail and even criticize or praise details that are not visible in a paper prototype.
As a platform we chose Invision and our digital prototypes can be tested here.
To see the prototype of the App, please enter here !
Style Guide
