Dental Clinic Management System
Unifying appointment scheduling, patient records, and transaction management into one system.
Problem
Dental clinics still relied on manual, fragmented processes for patient records, appointment bookings, and payment tracking — leading to missed visits, billing errors, and inconsistent data across staff.
Solution
We designed and built a centralized clinic management platform following a design thinking process — going from staff interviews to deployed system across five core modules.
Outcome
Built a centralized platform with 5 core modules covering patients, appointments, transactions, and automated SMS. Pivoted from Twilio to HttpSMS weeks before the deadline and shipped on time.
Client
Lim Dental Care Clinic
Role
Designer & Developer in a 5-person team
Timeline
Aug 2024 – Apr 2025
Problem
Many dental clinics still relied on manual, fragmented processes for patient records, appointment scheduling, and payment tracking — leading to missed bookings, billing errors, and data inconsistencies across staff.
Process
We followed a design thinking approach to make sure our solution addressed real-world needs — continuously aligning design and development decisions with actual user pain points.
Empathize
We conducted discovery interviews and informal observation sessions with clinic staff — receptionists and assistants. This surfaced day-to-day frustrations with manual record-keeping, fragmented appointment tools, and tracking payments on paper. We also considered the patient side: missed SMS reminders and long intake processes were a recurring pain point.
Define
From our research, we identified four core problem areas:
- Fragmented workflows — separate tools or paper for different tasks
- Appointment errors — double bookings and no-shows
- Inconsistent records — handwritten notes, lost patient history
- No real-time visibility — no centralized patient database
These became our design goals: build a centralized, intuitive system that reduces errors and saves time for clinic staff.
Ideate
Together with our advisor, we brainstormed feature sets and system structures — exploring modular dashboards, calendar views, form layouts, and automated SMS flows. We ranked ideas by impact vs. complexity, eventually scoping down to patients, appointments, transactions, and messaging.
Design
We started with low-fidelity wireframes in Figma to test layouts fast. After feedback sessions with the clinic, we iterated into high-fidelity interactive prototypes — prioritizing clarity and minimal cognitive load for non-technical users like receptionists.
Build
The frontend was built with React and Bootstrap for a responsive, clean interface. The backend used Django and MySQL for robust API structure and database management. SMS notifications were integrated via HttpSMS after pivoting from Twilio weeks before our deadline.
Takeaways
- Design with users in mind. Real interviews helped us turn pain points into practical features.
- Balance scope and feasibility. Not all ideas were buildable — prioritization was key.
- Embrace iteration. Frequent feedback helped us refine the system to meet real needs.
- Adapt under pressure. We pivoted from Twilio to HttpSMS weeks before the deadline.
- Communicate clearly. Working with non-technical stakeholders taught me to explain design choices simply.
Stack
React
Bootstrap
Django
Python
MySQL
Figma
Twilio
Calendly
cPanelParts of this work are under NDA.
Reach out — let's chat about the details.