Static mockup for a patient dashboard
Overview
The goal of this project was to create a web portal for patients to access their complete patient file, documentation of treatments and the rights of patients. The portal should provide information in plain, easy to understand language that removes barriers in the doctor-patient relationship.
The full task took about 4h to be completed, including the requirements analysis, information architecture, quick ideation and design of two alternative keyscreens.
Background and strategic fit
The new regulations in Germany strengthen the role of the adult patient and put her on an equal level with the treating physician. By centralising all patient files and rights in one online repository, the system aims to empower the user to have easy access to the big picture and become more familiar with the rights and duties of all parties involved in connection with medical care.
Audience
All citizens over 18 years old with access to the German healthcare system.
All citizens over 18 years old with access to the German healthcare system.
Technical Requirements
The application must be:
- Available Online
- Complete Patient Medical Record
- Web-based Application
- Legally compliant
The application must be:
- Available Online
- Complete Patient Medical Record
- Web-based Application
- Legally compliant
Process
I allocated a limited amount of time to each phase and tackled the task in the following order:
- Reading through the provided legal documentation by the German government
- Assessing the target audience and technical requirements
- Listing the goals that the application must fulfill
- Noting hypotheses given the lack of user research, to help making design decisions
- Writing down all the assumptions I was making and the non-answered questions
- Mapping the assumptions and questions to the recommended research methodologies
- Setting the task scope (all the activitites I was not doing given the time constraint)
- Categorising the topics of the online medical file into three sections: providing an overview, tailored to patient and generic content.
- Ideating 8 different alternatives by using the Crazy 8s method (adjusted to 3min per idea)
- Prototyping 2 high fidelity keyscreens in Adobe Xd as the final deliverable to present to the client.
I allocated a limited amount of time to each phase and tackled the task in the following order:
- Reading through the provided legal documentation by the German government
- Assessing the target audience and technical requirements
- Listing the goals that the application must fulfill
- Noting hypotheses given the lack of user research, to help making design decisions
- Writing down all the assumptions I was making and the non-answered questions
- Mapping the assumptions and questions to the recommended research methodologies
- Setting the task scope (all the activitites I was not doing given the time constraint)
- Categorising the topics of the online medical file into three sections: providing an overview, tailored to patient and generic content.
- Ideating 8 different alternatives by using the Crazy 8s method (adjusted to 3min per idea)
- Prototyping 2 high fidelity keyscreens in Adobe Xd as the final deliverable to present to the client.
Outcome & results
The task was very condensed and intense, with a great deal of time spent on the first part, putting together all the legal requirements and translating the official documentation. The final deliverables were a good starting point for discussion, using stories and cases as a tool to determine which elements were valuable and which needed refinement.
The task was very condensed and intense, with a great deal of time spent on the first part, putting together all the legal requirements and translating the official documentation. The final deliverables were a good starting point for discussion, using stories and cases as a tool to determine which elements were valuable and which needed refinement.
Although there was no data on users, the drawn plan for research methodologies caused a good impression and helped emphasising the importance of those activites to make further decisions on the design of the application.
Recommended research methodologies to validate the assumptions and questions