DentalX
Live SiteComprehensive dental ERP solution
- Role
- Product Designer
- Category
- ERP, Healthcare
- Team Size
- 4 Engineers1 Product Designer (me)
- Skills
- UI/UX Design, Design System
JARVIS Technology provides comprehensive dental clinic management & operations software, fully compliant with Vietnamese regulations.
What I did as product designer in this team:
- Prototyped the service booking, calendar, diagnosis, treatment, interactive tooth chart,...etc in Figma
- Built the component library, almost dashboard pages / landing pages and handoff docs for engineering sprints
I. Problem
- Paper and scattered tools: Clinics run on spreadsheets, and disconnected apps. Staff re-enter patient data at every step.
- Slow check-in: Average check-in took alot of time across systems: find the patient, re-enter details, open the chart.
II. Goal
One patient record from booking to follow-up, with every role seeing only what it needs.
III. Design Process
1. Preparation
Briefing: Mapped end-to-end clinic workflows with the product manager.
2. Research & Analytics
Hypothesis: If every step shares one patient record — booking, treatment, payment, stock deduction, follow-up — clinics will stop re-entering data, recover no-show revenue, and see the business live instead of at month-end.
3. Prototyping
User flows first, testable screens later.
4. Visual Design
- Calendar UI: Week calendar with dentist columns, drag-to-reschedule, and reminder settings per clinic.
5. Testing & Finalization
One finding per decision, tested with the role that lives it.
6. Measure & Iterate
I measure results with the product teams.
7. Scale
I design for scale with a clear system: design systems and component-driven design for long-term impact.
IV. Outcome
1. Design Solution
Connected clinic system: role-based views, Vietnam-legal finance, and follow-up that brings patients back.
- Operations: calendar, handoff pipeline, daily performance overview, multi-branch switching
- Records: customer file, diagnosis, electronic medical records, images
- Legal finance: electronic invoices, national prescriptions, payments
2. Testing
Each flows tested before rollout.
V. What I Learned
At any workflow, I have to know how users are doing currently with/without the software. By acknowledge the job to be done, how user do the workflow and what the behavior, sequential tasks, and even how the empty and filled states of each flow looks like, then I can think outside the box and brave to modify the components/layouts in the unique way for serving user purpose the most.
