Dental Coding for Veneers, Crowns, Inlays, Onlays and CAD/CAM Restorations

US scope: This operational guide does not reproduce CDT descriptors. Consult the current CDT publication and payer contract.

Report the restoration—not the machine

Code selection follows the completed restoration, tooth, coverage design and actual material. A scanner, mill or same-day CAD/CAM process does not alone create a different procedure category.

Classification checklist

Date of service

Apply current completion guidance and payer rules. The chart, laboratory or manufacturing record, claim and ledger must agree; do not assume the preparation date.

CAD/CAM documentation

Record scan, design/fabrication pathway, material traceability under policy, try-in, adjustments, definitive placement and final assessment. Technology language cannot replace clinical facts.

Build-ups and provisionals

A separately reported foundation must be actually performed and independently supported under the current definition. Routine provisional steps should not be unbundled. Document structural loss, material placed, purpose and outcome.

Replacement and repair

• Prior placement date if known and source
• Fracture, recurrent disease, margin, retention and symptoms
• Diagnostic images and examination findings
• Why repair, replacement or monitoring was selected
• Whether the final service was repair, recementation, remake or replacement

Original narrative

Tooth [number] had [diagnosis/findings] involving [surfaces/cusps/remaining structure]. The existing restoration was [condition/age]. Because [rationale], a [type/material] restoration was selected. Supporting records: [items]. Definitive placement occurred [date]; fit, contacts and occlusion were verified and [bonding/cementation] completed.

Claim workflow

1. Document the service before selecting a code.
2. Verify the current-year code source and notes.
3. Check patient eligibility, plan limits, network rules and authorization.
4. Reconcile the claim with the chart, images and ledger.
5. Retain the response and address denials by reason—not guesswork.

Coverage is separate from coding

The correct procedure may be excluded or limited. Never substitute a covered code for a different service. Predetermination is useful but does not guarantee payment.

Documentation template

Compliance safeguards

• Do not copy forward facts that were not reassessed.
• Do not alter diagnoses or dates to obtain payment.
• Use an amendment process that preserves the original record.
• Limit attachments to relevant, legible records.
• Audit payer edits separately from clinical code selection.

Operational review before submission

A reliable review separates four layers that are often mixed together: the clinical decision, the clinical record, code selection, and benefit adjudication. The clinician owns the accuracy of the diagnosis and service record. The coding team translates that record using the current authoritative code set. The benefits team verifies administrative requirements. A payer then applies the contract. Keeping these layers distinct prevents coverage rules from rewriting the chart.

Eight-point preflight

1. Identity: confirm patient, provider, location and date.
2. Diagnosis: confirm the assessment appears before or contemporaneously with treatment.
3. Specificity: identify tooth, site, arch, quadrant, material or time detail when relevant.
4. Completion: confirm the reported service reached the code’s reportable endpoint.
5. Consistency: compare note, claim, images, laboratory record and ledger.
6. Authority: check the current official code source rather than an old cheat sheet.
7. Benefits: verify administrative rules without allowing them to change the code.
8. Communication: present patient responsibility as an estimate, not a promise.

Decision matrix for documentation quality

How to write a useful narrative

A good narrative is brief enough to review and specific enough to connect evidence with the service. Start with the diagnosis and objective findings, identify anatomy, explain the decision, state what was completed and point to dated attachments. Avoid adjectives such as “severe” unless the clinical measurements support them.

Narrative formula

On [date], examination of [anatomy] identified [diagnosis] supported by [objective findings]. Because [patient-specific clinical rationale], [service] was performed/completed on [date] by [provider]. The record includes [relevant attachments]. Outcome and follow-up: [facts].

What weak narratives look like

• They repeat the procedure name without explaining need.
• They use payer language instead of clinical language.
• They contain copied measurements that do not match attached records.
• They add unrelated history and obscure the relevant facts.
• They state that authorization “guarantees” payment.

Attachment governance

Establish an office protocol for naming, dating, orienting and exporting attachments. Before transmission, verify that every image belongs to the correct patient and that no unrelated protected information is included. Maintain the original diagnostic-quality record even if the payer portal compresses the submitted copy.

Predetermination and patient estimates

Predetermination can reveal exclusions, frequency limits, alternate benefits and documentation requests, but it is not a contract for payment. Eligibility may change before treatment, and adjudication may depend on the final service. Written estimates should state assumptions, expected plan payment, possible patient balance and the fact that clinical recommendations do not depend on benefit design.

Denial response workflow

1. Read the explanation of benefits and exact adjustment reason.
2. Determine whether the issue is eligibility, coverage, coding, missing information, authorization, coordination or processing.
3. Compare the submitted claim with the original chart and current authoritative sources.
4. Correct a clerical error transparently or appeal a supportable decision with focused evidence.
5. Never modify the underlying clinical facts to fit a payer criterion.
6. Track the outcome so recurring workflow failures can be corrected.

Audit sampling plan

Each quarter, select a small sample across providers, locations and payers. Compare the service date, code, anatomy, narrative, attachments, ledger and remittance. Classify defects as clinical-record, coding, administrative or communication failures. Assign an owner and completion date; education without follow-through is not a control.

Team roles and handoffs

Frequently asked questions

Can a payer tell the practice which code to use?

A payer can explain how it adjudicates a submitted code, but the claim must accurately report the documented service. Ask for policy language when coverage is unclear.

Should every claim include a narrative?

No. Follow the payer’s requirements and use a narrative when it adds necessary context. Unrequested, repetitive text may slow review.

Can a note be completed after the visit?

Records should be contemporaneous. A legitimate late entry or amendment should be identified, dated, attributed and preserve the original according to office policy and applicable rules.

What if the patient asks the office to change a code?

Explain that codes report services actually provided. The team may correct an error, but cannot change accurate reporting to produce a preferred benefit.

How often should code references be updated?

At least for every annual code-set release, with targeted training and updates to templates, software favorites, fee schedules and payer rules.

Editorial and clinical-use disclaimer

This educational material supports workflow design. It does not replace the current codebook, a payer contract, professional clinical guidance, state law, legal advice or a patient-specific decision. Practices should obtain qualified guidance for ambiguous or high-risk cases.

References

1. ADA: CDT
2. ADA: Coding Education
3. ADA: Dental Benefits Q&A