How OpenDentist Handles Ambiguous Tooth References

Dentists do not speak in clean notation. You say "the upper left six", "that one", "the tooth we talked about", and "next to the crown". A generalist transcription tool hears words. A dental tool has to understand teeth. Bridging that gap is one of the things that separates a tool built for dentistry from one adapted to it.

The problem with raw transcription

If a scribe just writes down what it hears, "upper left six" might land as plain text rather than a properly charted tooth, and a vague reference like "that one" is meaningless without clinical context. The result is a note that needs heavy correction, which defeats the purpose. Worse, a tool that guesses wrong could chart the wrong tooth, which is a clinical error, not just an inconvenience.

Resolving references in context

A dental-specific system interprets natural speech against the clinical context of the appointment. It tracks which teeth have been discussed, what was being examined, and how dentists actually refer to teeth, then maps spoken references to the correct notation rather than leaving raw phrases or guesses in the record. "The upper left six" becomes the correct tooth in the chart; "that one", where the context makes it clear, resolves to the tooth under discussion.

This is fundamentally a dental knowledge problem. Understanding that "upper left six" refers to a specific tooth, and that "the distal of that" refers to a surface of it, requires knowing how teeth are numbered and named and how clinicians speak about them. A generalist tool has no model of any of this.

When it cannot be sure

Where a reference is genuinely ambiguous, the safe behaviour is to flag it for the clinician rather than guess and risk charting the wrong tooth. A confident wrong answer is worse than a clear prompt to confirm, because a wrong answer can slip through review while a flag draws the eye. This is the same principle that governs the rest of a well-designed scribe: where the system does not know, it says so rather than inventing.

Why dental-specific matters here

This is exactly the kind of problem a generalist medical scribe is not built for. Understanding tooth references is core dental knowledge, and handling it well is part of what decides whether a note needs a quick glance or a full rewrite. The difference shows up not in a demo but in the daily editing burden, which is where any documentation tool is really judged.

A worked example

A clinician examines a patient and says, working round the mouth, "upper right seven looks fine, the six next to it has a distal cavity, and that one we discussed last time, the upper left five, I want to review." A raw transcript captures the words. A dental-specific tool charts the upper right seven as sound, records a distal lesion on the upper right six, and resolves "that one we discussed last time, the upper left five" to the correct tooth, flagging it for review. The clinician reads a note that already speaks dentistry, rather than a block of text to be untangled.

Frequently asked questions

Why can't a general transcription tool handle tooth references?

Because it has no model of dental notation or how clinicians speak about teeth, so it records words rather than charted teeth.

What happens with a vague reference like "that one"?

Where context makes it clear, a dental tool resolves it to the tooth under discussion. Where it is genuinely ambiguous, it flags it for the clinician.

Could the tool chart the wrong tooth?

A well-designed one avoids guessing when unsure, flagging ambiguity instead, because a confident wrong answer is more dangerous than a prompt to confirm.

Why does this matter day to day?

It determines how much you have to correct. Good reference handling means a quick review; poor handling means rewriting.