Healthcare
Doctor
Companion
A mobile workspace concept for doctors, developed through competitive benchmarking, information architecture, sketching and interface design.
I started by studying products already solving parts of the patient and appointment journey.
The benchmark focused on PatchAi and MioDottore. PatchAi offered a useful reference for continuous patient support through health dashboards, symptom reporting, quality-of-life questionnaires, daily goals, treatment reminders, visit planning and educational content.
MioDottore covered a different part of the journey: finding doctors, nearby search, reviews, favorites, appointment booking and management, chat and video consultations.
Monitoring, symptom collection, reminders and educational content suggested how health information can stay available between visits.
Booking, appointment management, messaging and online consultations provided references for the service layer around the visit.
I translated the benchmark into a workspace built around the doctor rather than reproducing either product.
The concept brings the most relevant parts of the doctor workflow into one mobile structure: upcoming appointments, patient information, alerts, chat and scheduling.
The aim was to make routine information easy to scan while giving urgent events a clearly different priority.
The structure was kept deliberately shallow so the main areas remain directly reachable.
The information architecture organized the product around Home, Calendar, Chat, Alerts, Profile and Appointment. This gave each recurring task a clear destination while keeping the home screen focused on the doctor's next appointments.
Paper sketches were used to question structure and navigation before refining the interface digitally.
I used quick hand sketches to think through functions, basic page structure and navigation questions. I kept them rough because their purpose was to expose uncertainty early, not to become polished deliverables.
Daily overview
The home screen prioritizes the next appointments instead of trying to summarize everything at once.
Each appointment card combines the patient, age, reason for the visit, date, time and consultation mode. The bottom navigation keeps Calendar, Chat and Alerts one tap away.
An alert state can also surface directly in the navigation, giving urgent information a different visual weight without rebuilding the entire page.
Patient context
The patient screen groups the information needed around an appointment into one place.
Personal details, reason for the visit, date, time and consultation mode sit above medication information and health indicators such as blood pressure and blood oxygenation.
The hierarchy separates identity and appointment context from monitoring data, making the screen easier to scan before or during a consultation.
Alerts
Urgent events are visually distinct and carry the minimum context needed to react.
The alert view highlights the event type, patient, time, reason and location. In the concept, fall detection is treated as a high-priority event and separated from routine appointment information.
This was an early design direction rather than a validated clinical alert system. A production version would require careful testing of severity, escalation and notification fatigue.
Communication
Messaging keeps follow-up communication connected to the patient relationship.
The chat screen keeps the patient's identity and condition visible while supporting direct conversation, attachments and voice input.
This extends the workflow beyond the appointment and reflects the communication capabilities identified during benchmarking.
The original work established a coherent structure from benchmark to information architecture and interface design. The most important next step would be research with clinicians. I would validate what belongs on the home screen, which patient indicators are genuinely useful during a consultation, and how alerts should be prioritized without increasing cognitive load or notification fatigue.