iMedOne®
Hospital Information System — Digitizing clinical workflows for healthcare professionals across Europe
Hospital Information System — Digitizing clinical workflows for healthcare professionals across Europe
Challenge
Users
My Role
Research
Problem
Architecture
Wireframes
Low-fidelity wireframes were designed to validate layout, information hierarchy, and user flows before moving into visual design. The focus was on ensuring that each screen supported core clinical workflows and that users could find information without cognitive strain.
Evolution
The design evolved through multiple iterations, with each stage focused on making the product clearer, faster, and easier to navigate for healthcare professionals.
01 — Initial Exploration
The first concepts explored how to accommodate large amounts of patient and operational data without overwhelming the user.
02 — Establishing Hierarchy
I introduced stronger visual hierarchy by separating critical information, supporting data, and secondary actions. This helped users quickly identify what required their attention.
03 — Simplifying Workflows
Complex journeys were broken into focused steps. Patient management, consultation, prescription, and scheduling were connected into predictable workflows rather than isolated screens.
04 — Refining the Visual System
The interface evolved toward a lighter healthcare visual language with soft blue surfaces, strong typography, clear cards, consistent spacing, and restrained use of color for status and actions.
05 — High-Fidelity Validation
The final iterations focused on usability details—component consistency, responsive layouts, interaction states, data visualization, and touch-friendly controls.
The evolution was not about making the interface look simpler—it was about making the complexity easier to understand.
The final design combines clinical depth with visual clarity, giving professionals the information they need while keeping everyday workflows focused and predictable.
Decisions
Every major design decision was driven by one question: "What does a healthcare professional need to see or do at this moment?"
01 — Dashboard-first information hierarchy
I prioritized patient activity, appointments, key metrics, and alerts so clinicians could understand their workload and act without navigating through multiple screens.
02 — Progressive disclosure
Instead of presenting every clinical detail at once, information was grouped into meaningful sections and tabs. Users can start with an overview and progressively access deeper patient information when needed.
03 — Workflow-based navigation
The information architecture follows core clinical tasks—Patients → Consultation → Diagnosis → Prescription → Follow-up—rather than organizing the product purely around backend modules.
04 — Consistent visual language
Reusable cards, tables, charts, navigation patterns, and interaction states create consistency across the product and reduce the learning curve.
05 — Data visualization for quick scanning
Charts and summary metrics were used where they provide immediate value, allowing clinicians to recognize patterns and trends without reading large amounts of raw data.
06 — Tablet-ready responsive design
The experience was designed to remain usable across desktop and tablet environments, with touch-friendly controls and layouts that preserve important information hierarchy.
Make complex clinical information feel simple, predictable, and actionable—without removing the depth professionals need.
Impact
iMedOne transformed a complex healthcare workflow into a structured, intuitive dashboard experience that helps clinicians find information faster and manage their daily tasks with greater confidence.
01 — Faster access to patient information
Centralized patient data, medical history, appointments, and clinical information reduced the need to navigate between disconnected screens.
02 — Reduced cognitive load
Clear hierarchy and progressive organization made large volumes of clinical information easier to scan and understand.
03 — More efficient workflows
Patient management, consultation, prescription, and follow-up workflows were structured into predictable, repeatable journeys.
04 — Better decision support
Dashboards and analytics gave healthcare professionals a quick overview of patient activity, trends, and operational information.
05 — Scalable design system
Reusable components and consistent interaction patterns created a foundation that could scale across additional clinical modules and workflows.
The final experience balanced clinical complexity with simplicity—helping healthcare professionals spend less time navigating the system and more time focusing on patient care.
Design impact:
Clarity · Efficiency · Confidence · Scalability
Reflection
iMedOne reinforced that healthcare UX is less about adding functionality and more about reducing cognitive load. Clinicians work with large amounts of information under time pressure, so every hierarchy, interaction, and piece of information needs a clear purpose.
01 — Prioritize information, not features
The challenge was not simply to organize more data, but to surface the right information at the right moment. This shaped the dashboard, patient profile, appointments, and clinical workflows.
02 — Workflows should follow real mental models
Mapping the end-to-end journey helped me design around how healthcare professionals actually work—from finding a patient to reviewing history, documenting a consultation, prescribing medication, and scheduling follow-ups.
03 — Consistency builds confidence
Reusable components, predictable navigation, consistent terminology, and clear visual patterns became especially important in a product where users repeatedly perform high-impact tasks.
04 — Visual simplicity requires structural thinking
The clean interface was not achieved by removing information. It came from creating hierarchy, grouping related information, and progressively revealing detail.
The biggest takeaway was that good healthcare UX should make complexity feel simple—not hide complexity, but help users navigate it with confidence.