ABOUT THIS PROJECT

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.

The 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 an pacient also gets credit because everyone can see who is in the team and their responsebility. That should give patients and their data a big value and pushed down problems while the treatment is running.

The process

The best process here was combination of the double diamond method and design thinking. Starting from scratch was important, gathering the nessecary imformatin from interviews and a competetive analysis to find quickly the pain points of this personal project. 

ROLE

UX/UI Designer

CLIENT

Personal Project

PLATTFORMS

Desktop, Tablet and Mobile

MEDI_LP_overview
01

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.

AMZ_LP3
02

Double diamond design thinking

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 have contact with the patients. First it was time to find the paint points of the patient as well as the worker in the hopital, for both was it important to find the specific 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
AMZ_LP4
03

Patient profile

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

Medi.net was concepted to be a tablet first intranet. People in hospitals should be able to get the information on the fly and tablets are the perfect medium that combines information dencity and mobility for the user. It also gives the possibility to add other hardware like little mobile headphones to have quick calls with colleaques.

AMZ_LP2
04

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. 

AMZ_LP2
05

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. 

TORU-LOGO-white

Tony Andreas Rudolph

UX & VFX Storyteller

zulusplitter@online.de
+49 16090197007

Legal notice      Privacy policy