PROJECT OVERVIEW
Dental consultations involve much more than identifying what is wrong with a tooth. Dentists need to document diagnoses, add clinical context, recommend treatment and leave behind a record that another dentist can easily understand later.
The challenge was to bring this process into a digital experience without forcing dentists into a rigid workflow that slowed them down.
I explored different ways dentists could document a patient's dentition during consultation, gradually refining the experience through feedback and review sessions with dentists.
What started as a highly customisable tagging system eventually became a more structured consultation experience built around a familiar dental chart, standardised diagnoses and treatment planning.
THE PROBLEM
A lot of dental consultation workflows are still heavily manual.
Dentists develop their own ways of recording what they see, abbreviating diagnoses and organising treatment notes. This works when one dentist is responsible for the patient, but it becomes harder when that information needs to move between people. A patient might visit another dentist because their usual dentist is unavailable. They might change clinics, move to another location or simply need another professional to review their history.
In those moments, the record has to speak for itself.
The challenge became:
"How can we give dentists the flexibility and speed they need during consultation while keeping patient records consistent and easy for any dentist to understand?"
UNDERSTANDING HOW DENTISTS WORK
One thing that became clear quite early was that there wasn't one perfect consultation workflow that every dentist followed.
Individual dentists had preferences around how they documented conditions, how much information they recorded and when they introduced treatment planning. That made customisation attractive.
But it also created tension. The more the product adapted to each dentist, the less predictable the experience became for the next person using the record.
I wasn't trying to teach dentists a new way to consult. I was trying to find the right amount of structure so the software could fit naturally into their workflow without turning every patient's record into a personal code only one dentist understood.
SOLUTION
Iteration 1: Starting with custom markers
My first approach borrowed from something familiar: attaching a label to an object to add information about it.
Dentists could place a marker on an individual tooth to represent a diagnosis. Each marker could be customised using predefined diagnoses from ICD-10, giving dentists the freedom to create a visual system that matched the way they preferred to work.
"ICD-10 is a standardised classification system for diseases and health conditions."
The thinking was simple. If dentists already had their own shorthand for consultations, the product should help them recreate that digitally instead of forcing them to learn an entirely new system.
Within the consultation experience, it gave dentists a recognised set of diagnostic terms to choose from instead of relying entirely on manually written descriptions.
WHERE THIS APPROACH FELL SHORT
The marker system worked well for the person who created it, and that was also its biggest problem.
FIRST ISSUE
During review sessions, I realised that personalisation was beginning to come at the expense of clarity. A new dentist reviewing the patient's record first had to understand what another dentist's markers meant before they could understand the patient's dental history. That became particularly problematic during patient transfers or when another dentist needed to take over a consultation.
SECOND ISSUE
The setup process was also becoming increasingly complicated. Different dentists wanted different markers, layouts and ways of documenting their consultations. Accommodating every preference meant the product itself was becoming harder to configure.
THIRD ISSUE
There was another dependency I hadn't fully accounted for: the reference image. If dentists could choose different dental charts, someone reviewing the record later might encounter a representation they weren't familiar with. Instead of reducing the learning curve, the customisation was introducing another one.
FOURTH ISSUE
More importantly, a diagnosis marker only captured part of the consultation. Dentists still needed to manually document clinical details and create treatment plans somewhere else. Reviewing the patient later meant looking at the tooth, interpreting the marker and then finding the corresponding notes for context.
The first iteration taught me something important
Giving users more control does not always make a professional tool easier to use. Sometimes consistency is what makes the experience faster.
Iteration 2: Creating a shared visual language
For the second iteration, I moved away from custom markers and introduced a consistent dental chart built around detailed illustrations of each tooth.
The position and structure of the chart followed the human mouth, making it immediately recognisable to dentists without requiring a custom setup. Instead of dragging a marker onto the chart, dentists could interact directly with a tooth.
Selecting a tooth opened its clinical information, where the dentist could choose an ICD-10 diagnosis and add supporting notes.
This significantly changed the experience because the tooth itself became the anchor for its clinical history.
A dentist reviewing the patient no longer needed to understand someone else's colour system or marker configuration. They could see exactly what had been documented.
It also meant every dentist worked from the same visual structure and, as a result, there were fewer items to configure, less to learn, and less room for the record to become dependent on one person's preferences.
This was better but not finished!! The second iteration solved the consistency problem, but conversations with dentists surfaced several details I had missed.
FIRST DISCOVERY
A tooth could have more than one diagnosis, so treating every diagnosis as a completely separate entry could quickly clutter the patient's record.
SECOND DISCOVERY
Diagnosis and treatment were also more closely connected than the interface suggested. Dentists often decide on a treatment plan while documenting the diagnosis, so separating the two created unnecessary back-and-forth.
THIRD DISCOVERY
Treatment could also involve more than one tooth. If several teeth required the same procedure, dentists shouldn't have to document that treatment repeatedly for every individual tooth. The interface needed a way to select multiple teeth and treat them as part of one plan.
FOURTH DISCOVERY
Mixed dentition introduced another layer of complexity. For patients with both milk and permanent teeth, dentists needed to quickly distinguish what had been diagnosed and treated without having to interpret an overcrowded chart.
At this point, the problem was no longer how dentists recorded a diagnosis.
It had become:
"How do we support the full thinking process that happens around a tooth during consultation?"
Iteration 3: Designing around the consultation
The third iteration brought diagnosis, clinical context and treatment planning closer together.
Instead of treating every diagnosis as an isolated record, multiple diagnoses could live under the same tooth. This gave dentists a clearer picture of everything associated with that tooth without creating repeated entries across the chart.
Treatment planning was added to the same workflow. After documenting what they found, dentists could move naturally to what needed to happen next without leaving the context of the selected tooth.
For procedures involving several teeth, I introduced multi-selection so dentists could apply a treatment plan across the relevant teeth rather than documenting the same information repeatedly.
The experience also accounted for different dentition types, allowing dentists to better navigate milk, permanent and mixed dentition while still keeping the patient's clinical history visible.
The goal wasn't to add more features.
It was to make the product follow the way the consultation was already unfolding in the dentist's head:
Select → diagnose → add context → plan treatment.
ADDITIONAL WORKFLOW INTERACTIONS
The core dental chart handles diagnosis and treatment, but a few supporting interactions were needed to make the workflow feel complete for different patient cases.
Add treatment without leaving the flow
The treatment modal lets dentists create a treatment plan directly from the selected tooth or teeth. This keeps diagnosis and treatment connected, so dentists do not have to switch between different parts of the product to finish documenting a consultation.
Switch between dentition types
Dentists can filter the chart between All, Adult Dentition and Child Dentition. This helps them focus on the teeth that are relevant to the patient, especially in mixed dentition cases where both primary and permanent teeth may be present.
Filtering also makes it easier to review the diagnosis and treatment attached to each dentition type without overcrowding the chart. Dentists can quickly narrow the record down to what they need at that moment.
THE FINAL EXPERIENCE
The final direction centred the consultation around a consistent interactive dental chart. Dentists could select a tooth, document one or multiple diagnoses using ICD-10, add clinical notes and create the corresponding treatment plan from the same context.
When a treatment involved several teeth, they could select them together rather than repeating the process individually. Most importantly, the record no longer depended on understanding how a particular dentist had configured their workspace.
The dentist could still work quickly, but the information left behind remained structured enough for someone else to pick up.
That balance became the core of the final experience:
Flexible enough for the dentist doing the work and consistent enough for the next dentist who needs to understand it.
WHAT CHANGED THROUGH ITERATIONS
The biggest shift in this project wasn't visual. It was how I thought about customisation. I started by assuming that giving dentists more freedom would naturally make the product faster for them.
What I learnt was that in a clinical environment, flexibility has a cost when it affects how easily information can be understood by someone else.
The first iteration optimised heavily for the individual dentist, the second created a common language then the third found a better balance between both.
SUMMARY
Designing this experience made me think differently about professional tools.
Efficiency isn't always about reducing the number of clicks. Sometimes it is about reducing the amount of interpretation required before someone can make the next decision.
For a dentist, saving a few seconds during documentation matters. But being able to open a patient's record months later, or hand that record to another dentist without an explanation, matters just as much.
The final design became less about digitising a manual dental chart and more about creating a clinical record that could remain useful beyond the person who created it.