Define the system
Module architecture, relationships between roles and continuity across preparation, consultation, treatment and follow-up.
All case studies
HealthTech Product · HealthTech · Product ecosystem
Designing an AI-assisted clinical experience without losing human judgment.
The HealthTech product connects patients, healthcare professionals and service organizations within a functional-medicine experience. My work translates that complexity into a clear, coherent MVP prepared for implementation.
- My role
- Senior UX/UI Designer · Functional Analyst · Product Design
- Status
- MVP definition, design and implementation support
- Scope
- Patient · Physician · Administration
- Principle
- AI suggests; people retain control
Open larger image ↗A concept artifact used to visualize breadth and dependencies before prioritizing and simplifying the MVP solution.
UX/Product direction · AI-assisted visualizationThe product problem
Clinical complexity should not become product complexity for the people using it.
The platform must record clinical information, support consultations, organize therapeutic strategies, generate documents and sustain follow-up. At the same time, it must avoid overloading physicians, confusing patients or presenting AI suggestions as automatic decisions.
Guiding questionHow can we preserve the depth required for care while creating an experience that is easy to learn, use and build?
From concept to implementable definition
My contribution connects strategy, experience and delivery.
Reduce friction
Shallow flows, consistent patterns, familiar forms and progressive decisions based on context.
Prepare delivery
MVP prioritization, functional definition, reusable components, microcopy and criteria for development support.
From producing screens to designing complete flows
I redefined the unit of work so UX could lead the experience, not only represent it.
The team worked around individual screens, with daily reviews and an expectation of roughly two screens per day. I proposed that UX interpret the functional diagrams and turn goals, rules and dependencies into experience flows before designing the interface.
Before
Screen production
- Unit of workIndividual screens
- ExpectationApproximately two screens per day
- DefinitionFlows co-constructed during meetings
- Follow-upDaily review of visual progress
- UX roleRepresent the screens being described
After
Experience-flow design
- Unit of workComplete, connected journeys
- ExpectationUnderstandable proposals before interface detail
- DefinitionUX prepares the flow from goals and rules
- Follow-upOne weekly progress and clarification session
- UX roleUnderstand, propose and design the experience
Observable outcome
One weekly conversation around flows, approved design and development.
On Mondays, proposed flows were presented in Figma, the development team showed the screens approved the previous week and questions were resolved. The change reduced the need for daily screen reviews and gave each discipline clearer ownership.
- 01Goals and rulesBusiness defines what is needed.
- 02UX understandingInterpret the functional flow.
- 03Proposed flowDesign the experience in Figma.
- 04Review and approvalResolve questions and refine together.
- 05DevelopmentImplement the approved flow.
Qualitative outcome documented from the working dynamic; no productivity or rework percentages are claimed because measurements are not available.
One project, six product problems
Each case explores a different decision within the ecosystem.
The purpose is not to show six groups of screens, but to demonstrate different capabilities: strategy, architecture, human-AI interaction, clinical operations and communication of complex information.
01Available in English
MVP Strategy and Architecture
Turning a broad clinical-platform vision into a first version that is understandable, valuable and technically feasible.
Read full case02Available in English
End-to-end Patient Experience
Supporting the patient from consultation preparation through treatment understanding and continuity.
Read full case03Available in English
Physician Workspace
Giving healthcare professionals information and control without turning the experience into an aircraft cockpit.
Read full case04Available in English
AI-assisted Consultation
Allowing AI to transcribe, organize and suggest information without replacing clinical judgment.
Read full case05Available in English
Therapeutic Strategy and Documents
Turning a complex prescription into a clear, reviewable and useful daily plan for the patient.
Read full case06Available in English
Clinical Follow-up and Continuity
Helping physicians identify what needs attention and quickly recover the context of each case.
Read full caseCriteria applied across the product
Designing for health requires clarity, boundaries and accountability.
Humans remain in control
AI organizes and suggests; clinical decisions require professional validation.
Transparency
The product distinguishes device data, patient-reported information and AI-assisted interpretation.
Intentional MVP
Every capability must justify its value before adding navigation depth or technical complexity.
Contextual privacy
Each role accesses only the information required to fulfill its responsibility.
Continue exploring
End-to-end Patient Experience
How preparation, consultation, treatment and follow-up can remain connected without overwhelming the patient.
Read case