Denticode templates help turn what a clinician says during a visit into a clean, structured clinical note.

A good template saves time, keeps documentation consistent, and helps your team create notes that are easier to review, bill, and support with attachments. Once a template is built correctly, your team can use it again and again for the same type of visit.

For example, your office may have separate templates for:

The goal is simple: create one clear template for each visit type so your team does not have to rebuild the note every time.

A Denticode template is the structure Denticode uses to create the final clinical note.

It tells Denticode:

Think of the template as the outline for the final chart note.

Every Denticode template has a few key parts.

This is the name your team sees when choosing a template.

Use clear names that describe the visit type.

Good examples:

Avoid vague names like:

A clear name helps the team choose the right template quickly.

The template code is an internal shortcut or tag for the template.

Examples:

This is optional, but it becomes helpful as your office adds more templates over time.

The body is the actual note layout.

This is where you write the sections you want to appear in the final note, such as:

Inside the body, Denticode uses special placeholders called tokens.

Field links tell Denticode which pieces of information should fill each token.

For example, the patient name token should connect to the patient name field. The treatment date token should connect to the date field. The CDT code token should connect to the CDT code field.

This helps Denticode know exactly where each piece of information belongs.

A token is a placeholder that Denticode fills in later.

Tokens use this format:

#!Patient_Name!#

For example, a simple template may look like this:

Patient: #!Patient_Name!#
Date: #!Treatment_Date!#
Provider: #!Provider_Name!#

CHIEF COMPLAINT:
#!Chief_Complaint!#

HPI:
#!HPI!#

PROCEDURE SUMMARY:
#!Procedure_Summary!#

CDT CODES:
#!CDT_Codes!#

When the visit is recorded and finalized, Denticode replaces each token with the correct information.

For example:

Denticode fills template fields in a few different ways.

Some information can be pulled automatically from the visit details or transcript.

This may include:

These fields are usually the most straightforward because they follow predictable patterns.

Some fields require more context.

Examples include:

Denticode uses the visit transcript to suggest these fields. Your team can then confirm, edit, or replace the suggestion before finalizing the note.

Some information may need to be typed or selected manually.

This is useful when something was not said out loud during the visit or when the provider wants to add extra detail.

Each field in a template should have the correct field type. Choosing the right type helps keep the note clean and easier to review.

Use this for open-ended note sections.

Best for:

Use this for dates.

Best for:

Denticode can understand common date phrases like “today,” “yesterday,” or a specific date.

Use this when the field should only contain a number.

Best for:

Use this when the user should select one option from a fixed list.

Best for:

Use this when more than one option can apply.

Best for:

Use this for tooth-specific fields.

Denticode can recognize both written and spoken tooth numbers, such as:

Use this for dental procedure codes.

Denticode can recognize CDT-style codes and connect them to the code library.

Examples:

Use this for simple true-or-false fields.

Best for:

Denticode includes an AI template builder to help you create a template faster.

Go to:

Settings → Templates → New Template

Then describe the type of template you want.

Example:

Post-op note for a tooth #19 root canal, two visits, single root.

Denticode will generate a starter template with suggested sections and tokens. You can then review it, edit the wording, and decide which fields should be added to your template library.

This is the fastest way to create a first draft of a template.

Create templates based on the visit type, not the individual provider.

For example, use:

Crown Prep Visit

Instead of:

The template should reflect the practice’s documentation standard. Provider-specific style can be handled in the wording of the note, not by creating duplicate templates.

Try to keep the number of tokens manageable.

A template with too many fields can slow down the team because they have to review and confirm too much information.

As a general rule, only create tokens for information that truly needs to be captured, reviewed, or reused.

If a field has a limited set of possible answers, use a single-choice or multi-select field instead of free text.

For example:

Smoking Status:

This keeps notes cleaner and makes reporting easier later.

Required fields should be used carefully.

Good required fields may include:

Avoid making too many fields required. If the provider cannot complete a required field easily, the team may create workarounds that reduce note quality.

If your office uses the same language across multiple templates, save common sections to the template library.

Good examples include:

This keeps templates consistent across the practice.

Avoid names like Template 1 or General Note.

Use names that clearly tell the team when to use the template.

Do not create two fields that mean the same thing.

For example, avoid using both:

#!Chief_Complaint!#
#!Patient_Concern!#

Pick one field and use it consistently.

Too many required fields can slow down the visit and frustrate the provider.

Only mark a field as required when the note should not be finalized without it.

Tokens work best when they are placed under clear section labels.

Better:

HPI:
#!HPI!#

Less reliable:

The patient presents today with #!HPI!#.

Clear labels help Denticode understand where each piece of information should go.

Be careful with words that can mean more than one thing.

For example, “crown” could refer to a crown prep, crown seat, existing crown, temporary crown, or crown-related complaint.

Use specific wording whenever possible.

A good Denticode template should be easy for the whole team to use.

Build it once, keep it clear, avoid unnecessary fields, and structure it around the way your practice documents real visits. A well-built template can support hundreds of visits without creating extra correction work.