Handle Patient Name and Date-of-Birth Matching in a Dental Voice Workflow

Dental patient matching by voice should end with one clearly identified existing record or an explicit unresolved result. It should not end with the assistant choosing a person because their name sounds close enough.

Burki's supported Open Dental workflow uses confirmed first name, last name and date of birth to match an existing patient. Those details help locate a record. They are not a general substitute for a practice's identity-verification policy or permission to disclose clinical information.

Collect the fields separately

Ask for the patient's first and last name, then clarify any uncertain spelling. Collect the date of birth in an unambiguous format. Numeric dates can mean different things to different callers, so read the month in words when confirming.

Avoid asking a long compound question that makes it difficult to tell which answer belongs to which field. A caller may give their own name while booking for someone else. Establish whose record should be matched before proceeding.

The Open Dental integration overview explains the existing-patient scope. Keep the assistant's questions within that purpose rather than collecting extra information just because it might be useful later.

A hypothetical date correction

Imagine a caller saying “the fourth of May,” then correcting it to “the fifth of April.” The assistant should replace the earlier date and confirm the complete corrected version. It should not preserve the first month and combine it with the second day.

A useful readback is: “For the patient record, I have April fifth, followed by the year you provided. Is that correct?” In a real conversation, the full intended date must be clear; this example avoids using a real person's details.

If the caller interrupts the readback, obtain a clear confirmation of the final values. A partial acknowledgement does not resolve which version they intended.

Preserve the difference between no match and uncertainty

No exact match may mean the caller supplied different information from the stored record. An unresolved result may mean the available response cannot establish one unique patient. Neither outcome permits the assistant to invent a new patient or select a similar one.

Give staff a concise handoff: the caller requested an existing-patient appointment, the match could not be resolved, and no booking was confirmed. Follow the practice's policy for how identifying details are handled in that review.

Do not read out several patients' names or birth dates to help the caller choose. The conversation should collect the caller's information, not expose possible records.

Keep matching separate from appointment suitability

Even a correct patient match does not establish that every appointment type is appropriate. The current integration's general-appointment scope and configured dentist, operatory and duration still apply.

A caller asking for a clinical recommendation or a specialized procedure needs the practice's established process. The assistant should not infer the required treatment from a successful administrative lookup.

Open Dental's appointment API documentation shows the provider's scheduling concepts. That broader API does not expand the narrower set of actions available through Burki's current integration.

Review with the people who maintain patient records

Practice staff know common sources of mismatch: compound surnames, previous names, spelling differences and callers speaking for relatives. Use that knowledge to prepare representative, synthetic practice examples and clear handoff rules.

Browser practice is simulated and does not establish real patient lookup. Actual provider acceptance requires an authorized test practice and inspection of the resulting record association. Do not treat a fluent readback as evidence that the right patient was selected.

The Open Dental setup guide describes the connection and testing boundaries. Have the practice approve the exact matching questions, date format and unresolved-result wording before enabling scheduling actions.

Your next step is to review one difficult but fictional name-and-date example with the front-desk team. If they would need to intervene, make that intervention explicit in the workflow instead of expecting the assistant to guess.