Last updated: 2026-09-21

Dental coding in Open Dental is not medical coding with different numbers on the codes. A dental coder codes off the treatment plan and the clinical note, and the code set is CDT, the Current Dental Terminology the American Dental Association maintains and revises each year, rather than the CPT and ICD sets a medical coder works. So the job description comes first, then coding the treatment plan, because the plan is where the work a claim bills gets recorded. Choosing the right CDT code comes next. Writing the narrative that supports the claim sits beside it, since many dental claims need words or an image before a payer pays. The alternate benefit downgrade follows, then asking the dentist to clarify a chart entry, then what happens when a claim denies. Loading the yearly CDT update comes after that, because a retired code rejects the day it takes effect. Audit support sits next to it. Access is the question a practice asks hardest of a remote coder, and where a remote coder falls short closes the practical side. The sources behind these facts end the page.

What does a dental coder do in Open Dental?

A dental coder does the reading half of the dental revenue cycle in Open Dental, turning a signed treatment plan and clinical note into the CDT codes a claim can stand behind. Billers take those codes and work the claim to payment. Code the wrong procedure and the practice carries that error for as long as the record stays open, so a coder's responsibilities part company with a biller's on the first task.

Several pieces of work fill a dental coder's day inside a practice.

• Reading the full clinical note and the signed treatment plan against the CDT code that fits.
• Choosing the CDT code that matches the procedure the dentist documented and completed.
• Writing the narrative that tells a payer why the code the claim carries was necessary.
• Reading the explanation of benefits when a plan pays a downgrade instead of the treatment the code billed.
• Sending a query to the dentist when a chart entry won't support a clean code.
• Loading the yearly CDT update so a retired code stops and a new code works.

Open Dental runs in single-location offices, in dental groups, and in the billing companies that serve them, so a coder here may work several small clients in a week. Two offices on the same software hand a remote coder different fee schedules, buttons and document categories, because every build is local. Calling that person a general office assistant with a code book misses what the role owns.

How does a coder code a treatment plan in Open Dental?

A coder codes a treatment plan in Open Dental by reading each planned procedure against the clinical note, then assigning the CDT code the record supports and no more than that. The plan lists what the dentist proposes, while the claim bills what the dentist completed, so a coder codes from the finished work rather than the proposal. Dental treatment often runs in phases, and only the phase done at this visit becomes a claim.

Before a planned procedure turns into a coded claim, a coder checks four things.

• Whether the procedure was completed at this visit, or still sits in a future phase of the plan.
• Whether the tooth number, surface and quadrant that the CDT code needs are all written in the note.
• Whether the narrative or the attached image the procedure calls for is already on file.
• Whether the note and the plan name the same procedure, rather than two that nearly match.

Completed status is where a rushed claim goes wrong. One procedure marked planned but coded as done bills work the record can't yet support, and the reverse leaves finished treatment unbilled. Reading the plan and the note together, on the same date, keeps the claim honest.

How does a coder choose the right CDT code in Open Dental?

Choosing the right CDT code in Open Dental means the coder reads what the dentist performed and picks the single Current Dental Terminology entry that describes that procedure, no broader and no narrower. Codes get earned from the record, not from a coder's sense of what the dentist probably did. The American Dental Association publishes the CDT set and its yearly changes on its CDT codes page, so the descriptor behind a familiar number is worth rereading.

Three questions settle most CDT choices in a practice.

• Whether the code describes the exact procedure, such as the number of surfaces on a restoration or the crown material used.
• Whether a more specific code exists for the same work, since a general one invites a downgrade or a records request.
• Whether last year's update retired the code or moved its descriptor while the number stayed put.

Surface counts trip people up more than any other choice. Two-surface and three-surface restorations carry different codes and different fees, and the note has to name each surface for the higher one to hold. Guessing up is a refund waiting to happen. Guess down and the practice leaves money it earned on the table.

How does a coder write a narrative that supports a dental claim in Open Dental?

A coder writes a narrative in Open Dental by telling the payer, in a few plain sentences, why the procedure was necessary and what the clinical picture showed. Many dental claims pay on the codes alone. The ones that don't need a narrative, an x-ray, or a periodontal chart before an adjuster approves them, and a thin narrative is the most common reason a supportable procedure gets held.

Every narrative that survives review carries four things.

• The clinical finding that made the procedure necessary, such as a fracture, decay depth or bone-loss measurement.
• The date and the tooth or site of the procedure, matched to whatever the attached image shows.
• The alternative procedure that was considered and why it wasn't chosen, on a plan that tends to downgrade.
• Plain language, since the person reading the procedure narrative is often not a clinician.

Copy-and-paste narratives read as boilerplate to an adjuster, and they invite the records request they were meant to avoid. One narrative built from the actual note beats a template every time. For the wider shape of the role across care settings, our medical coder guide covers the reading work a coder owns.

How does a coder handle an alternate benefit downgrade in Open Dental?

Handling an alternate benefit downgrade in Open Dental means the coder reads the explanation of benefits line by line, because the downgrade shows up there and nowhere on the claim the practice sent. An alternate benefit clause lets the plan pay toward a lower-cost treatment, such as an amalgam filling in place of a composite, or a base-metal crown in place of a noble-metal one. The office still performed the procedure it billed, but the plan paid a smaller number against it.

Reading a downgrade, a coder works through a short list.

• Whether the explanation of benefits names an alternate benefit or a least-expensive-alternative clause.
• Whether the patient's plan contains that clause, or the payer applied it in error.
• Whether the clinical record supports the procedure performed over the cheaper alternative.
• Whether an appeal with the narrative and image attached has a basis, or the balance is the patient's under the plan.

Downgrades slip past a practice that reads only the paid amount and moves on. Catching one early lets the front desk explain the patient balance before it becomes a surprise, which is a different conversation than the one that starts sixty days later.

How does a coder ask a dentist to clarify a chart entry in Open Dental?

A coder asks a dentist to clarify a chart entry in Open Dental by writing a short question that quotes the note, names what's missing, and offers no answer of its own. Handing the dentist a code to agree to is worse than no query at all. It puts words in the record and leaves a trail that it happened.

Queries go out when a chart entry falls short in one of four ways.

• Conflicting, where the note and the treatment plan name different teeth or different procedures.
• Incomplete, where the note gives the diagnosis but leaves out the surface, quadrant or tooth number the code needs.
• Ambiguous, where the note would support either of two codes and nothing settles the choice.
• Unsupported, where a procedure sits in the plan and nothing in the note shows it was done.

Response times vary by dentist far more than by office, and a coder splitting time across several clients learns each rhythm the slow way. Agree a response window during onboarding and name who chases it, since an unanswered query holds a claim nobody is watching. For the rest of what the job owns day to day, our breakdown of medical coder duties and responsibilities covers the wider set.

What happens when a dental claim denies in Open Dental?

When a dental claim denies in Open Dental, the code decision comes back to the coder rather than the biller, and the fix starts with reading the denial reason against the note that produced the claim. Billers work the claim itself, the resubmission and the follow-up. Deciding whether the code was right, then defending it or correcting it, is the coder's call.

Four denial reasons land on a dental coder's desk.

• Missing narrative or attachment, where the procedure needed words or an image and the claim went out without them.
• Frequency limit, where the plan covers the procedure only so often and this claim's date falls inside the window.
• Downgrade or alternate benefit, where the plan paid toward a cheaper treatment and the claim's balance needs a decision.
• A code that doesn't match the tooth or surface documented, where the record and the claim disagree.

State Medicaid dental programs follow coding and billing rules the Centers for Medicare and Medicaid Services publishes, and commercial plans set their own, so a coder reads the specific plan's policy before resubmitting anything. Adding an attachment the record doesn't contain, just to clear a denial, turns a denied claim into a paid claim and an audit finding at the same time.

When does a coder load the yearly CDT update in Open Dental?

A coder loads the yearly CDT update in Open Dental ahead of January 1, when the American Dental Association's revisions take effect, so a code retired at year end stops billing and the codes replacing it are ready. Retired codes never announce themselves. They come back as rejections weeks later, on claims somebody already counted as clean.

Four checks belong in every yearly CDT update a coder runs.

• Every deleted code pulled out of the procedure list, favorites and fee schedule in the practice's build.
• Every new code the office uses added, with the dentist briefed on what the note now has to record.
• Every changed descriptor read in full, since a number that still works can now mean something different.
• Every recurring denial pattern rechecked against the revised codes.

Reference software carries part of this, and none of it carries the part where a dentist's writing habit has to change for a new code. Working several offices, a coder runs the update once per build, not once in total, because each fee schedule and favorites list is its own. The office that skips the update meets it in February as a stack of rejections.

How does a coder support a dental record audit in Open Dental?

Supporting a dental record audit in Open Dental means the coder pulls the full record behind every sampled claim and points to the note, the image and the narrative that stand behind each CDT code. An audit reads paper, not memory. The coder who left the reasoning in the record at the time walks a sample in an afternoon rather than a fortnight.

An audit response a coder assembles carries the same pieces every time.

• The claim as sent, with every CDT code, tooth number and surface the coder put on it.
• The signed clinical note behind the claim for that date of service, plus the treatment plan it came from.
• Any x-ray or periodontal chart the claim relied on, matched to the tooth and the date.
• The narrative sent with the claim, and any query to the dentist along with its answer.

Nobody rewrites a note to survive an audit. Late addenda are legitimate when dated and signed as one, and fraud when backdated to look as though they were there all along. For the abilities this reading work asks of a person, our rundown of medical coder skills lays them out.

What access does a remote coder need in Open Dental?

A remote coder needs read access to the full clinical record, the imaging and the signed treatment plan, and write access to nothing past the coding and claim fields. Reading the whole chart is the job, since nothing is coded from a summary screen. Handing over the entire login is the mistake practices make in the other direction.

Five access decisions a practice settles before a remote coder starts.

• A named account for the coder, so the audit log shows who opened which chart and when.
• Read access for the coder across the clinical notes, imaging and treatment plans for the dates being coded.
• Write access for the coder limited to the coding and claim fields, with no rights over the dentist's note.
• Multi-factor authentication on the coder's login, with a recovery path that doesn't rest on one phone.
• A revocation step run the day the coder's engagement ends, against every system the coder touched.

The boundary runs through the middle of the work. This coder reads everything the dentist wrote and decides nothing a dentist decides. Changing a note, adding a diagnosis the dentist never made, or telling a patient what an x-ray means all sit outside the role. Honest Taskers staff do administrative and clinically adjacent work and never give clinical advice or make clinical decisions. The talent pool includes licensed nurses and physicians, which describes how the company recruits rather than what a placement does.

Professionals are HIPAA-trained under a dedicated HIPAA compliance officer, with quarterly HIPAA and data privacy training, and a Business Associate Agreement is signed when a professional accesses protected health information. Its security environment is described as SOC 2 audit ready. The closest published occupational description belongs to medical records specialists, written up by the Bureau of Labor Statistics in its "Occupational Outlook Handbook" (Bureau of Labor Statistics, 2025), where the listed duties are records, codes and classification systems rather than clinical judgment. Practices new to remote support often start by asking can a virtual assistant work in your EHR, which walks through the access question in general.

Where does a remote coder fall short in Open Dental?

A remote coder comes with three limits worth naming before a job posting goes up, and not one of them argues against making the hire.

Platform time is not build time. Somebody who spent two years in Open Dental elsewhere still needs a week with your fee schedule, procedure buttons and document categories, because those are local choices rather than vendor defaults. Budget that week instead of finding it inside a backlog.

Payer knowledge doesn't map cleanly across plan types. One coder fluent in commercial dental claims isn't fluent by default in a state Medicaid dental program, and the two carry different narrative and frequency rules. Ask what the coder has coded, for which plans, and for how long.

Narrowing on one platform plus one specialty plus one schedule filters three ways at once, so the search runs long or a criterion gives way. Decide up front which of the three you would trade.

On terms, Honest Taskers recruits in the Philippines, Latin America, India and Pakistan, and its professionals work the client's US time zone and approved schedule. Rates run $10.00 to $12.65 an hour depending on the role, candidate background, schedule and location, so 20 hours a week runs roughly $800 to $1,012 a month and 40 hours roughly $1,600 to $2,024. New clients may receive a two-week working trial with their first selected professional, subject to current service terms, and replacement support is unlimited. Retention runs 99.6% average monthly by the company's own reporting, which matters for a coder because a year of coding decisions and the reasoning behind them lives with that one person.

Where do these Open Dental coder facts come from?

Honest Taskers rates, recruiting geography, trial terms, retention figure and compliance posture come from the company's published rate card and service terms. Open Dental appears here as dental practice-management software that dental offices run, and no module name, menu path, price or customer figure for it was read from the vendor. CDT and its yearly revisions come from the American Dental Association, and state Medicaid coding and billing rules from the Centers for Medicare and Medicaid Services, with the occupational description from the Bureau of Labor Statistics. Everything about coding a treatment plan, choosing a code, writing a narrative and answering an audit reflects general dental coding practice, not one office's protocol. No coding accuracy rate, claims-per-hour figure or turnaround time appears on this page.

Offices that have settled how the dental coding work runs and want to weigh providers next can start with our ranking of best virtual medical coder companies. It reads healthcare focus, compliance posture, recruiting reach and support model across the firms placing remote coders, which is the comparison an office makes once workflow and access are answered rather than before. A dental coder and a medical coder aren't the same hire, so read a coding company's dental experience closely before you shortlist it.

Request a remote dental coder with Open Dental and CDT experience for your practice.