ROLE

UX/UI Designer

CLIENT

Personal projects

PLATTFORMS

Desktop, Tablet and Mobile

Medi.Net

The idea of Medi.net was born from the problem of missing digital and modern possibilites in hospitals that give more value to a patient, pushes down missleading treatments and helping teams working closely together. Hopitals having the problem of using different softwares for different medical products. But they also missing a base on where they are able to storage the important data of patients. Here is where Medi.net comes in.

GOAL

Bringing people in hospitals together by enhancing the teamwork was the ultimate goal. In hospitality is it hard to combine different software ecosystems together to push team spirit and collaboration. Everyone who is working on the patient should also gets credit because everyone can see who is in the team and their responsebility. 

PROCESS

Starting from scratch was important, but also gathering the nessecary information from interviews and a competetive analysis to find quickly the pain points of this personal project.

  1. Competitive analysis
  2. Understanding the problem by interviewing employees working in hospitals and creating personas based on these interviews
  3. Patient data privacy protection
  4. Creation of the final design for the product
MEDI_LP_overview

COMPETITIVE ANALYSIS

Does it fits hopital and patient needs?

The first phase was spend with a potential competetive analysis. Results:

  • There are rarely intranets on the market, but still exclusively connected to specific IT infractrutes like Siemens Healtheer and other developers
  • It seems that there is no software able that gathers data from other third party softwares needed to work efficient with patients
  • There is no software available that combines intranet features with possible solutions to bring patient data into one place inside a hospital

The second phase was the user research, Tony found out that users or people working in hopitals looking for a way to share, collarborate and enter patient and insurence data about their patients they need for their daily business. Currently the data is stored and shared decentralized via paperwork and inside the third party software. That means users in hopitals have trouble to combine data from different sharepoints.

UNDERSTANDING THE PROBLEM

Understanding the problem to find a best design solution

From the beginning, patient data protection was an important part of the process. Every position in a hospital has different rules on patient data, that also influences the userflow. Even when the overall userflow is similar to each user, is the difference in the detail when users/employees have contact with the patients and how they might use the software. First it was time to find the paint points of the patient as well as the employees in the hopital, for both was it important to find the specific solution that solves these problems..

  • Patient data protection and data collection from third party software was important for the software and collaboration inside the hopital. To understand the problem, interviews with workers of hopitals where gathered. 
  • Patients are very important that their data is perfect collected, they only want that specialists get insights in their information, not everyone
  • Employees have fear how the software reacts with low to no acess to the internal wifi that blocks the real time refreshing of the patients data
  • The software might get to complicated to handle because of all the features needed to make the intranet valuable
d-User-analysis

PATIENT DATA PROTECTION

Patient data is important and there is different on how looks into a patient profile

Patient data was a big problem to solve doing this excursion. I had to be done severeal interations and rethinking on how patient data should be treated. 

The results were the following:

  1. Patient data is visible depending on not only hospital department, but also the people who are involved in the treatment
  2. Department- and teamleaders are needed to control the visibility of the patient data, only employees direct involed with the patient can see the nessesary information
  3. Patient data should be shared across the hospitals controlled by the insurence company (via the regular insurence card)
Data-access

TABLET FIRST

The focus of Medi.net is tablet use

Also the result of the market research was that intranets are available on the market, but still exclusively connected to specific IT infractrutes and ego system like Siemens Healtheer and other developers. No software is able to gather data from a third party software and store it in one software or place. Another important part was to decide that the app mainly runs on tablet first and second was a desktop version. Because many people in hopitals especially doctors, nurses and physicians tending to leave the desk on a very regular basis, which means they need a app that is flexibel enough to give enough value to be a teamwork and intranet software. 

LEARNINGS

The complexity of medical software

Within the process of creating this personal project. A big learning was the combination of third party software as well as the complexity of the information architecture within medical softwares. Medi.net grow up as a complex software concept that gathers big amount of complex data about the patients. Combining those with useful information architecture was the hardest part. Because it has to give value to every level within a hospital. But it also gives a lot of potential in the treatments of patients and the collaboration in hospitals because everyone can share their thougths across the team and this with a mobile device on the fly.

TORU-LOGO-white

Tony Andreas Rudolph

UX & VFX Storyteller

zulusplitter@online.de
+49 16090197007

Legal notice      Privacy policy