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
| Question | Record |
|---|---|
| Veneer/full/partial coverage? | Preparation and surfaces/cusps covered |
| Inlay or onlay? | Surfaces and cusp coverage |
| Material? | Actual definitive material |
| Initial or replacement? | Existing restoration and failure |
| Completion? | Delivery, fit, contacts, occlusion and bonding/cementation |
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
- Document the service before selecting a code.
- Verify the current-year code source and notes.
- Check patient eligibility, plan limits, network rules and authorization.
- Reconcile the claim with the chart, images and ledger.
- 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
| Field | Entry |
|---|---|
| Diagnosis/findings | Patient-specific, objective facts |
| Service | What, where, when and by whom |
| Rationale | Clinical link between findings and care |
| Supporting records | Dated charts, images or correspondence |
| Outcome | Completion, response and follow-up |
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
- Identity: confirm patient, provider, location and date.
- Diagnosis: confirm the assessment appears before or contemporaneously with treatment.
- Specificity: identify tooth, site, arch, quadrant, material or time detail when relevant.
- Completion: confirm the reported service reached the code’s reportable endpoint.
- Consistency: compare note, claim, images, laboratory record and ledger.
- Authority: check the current official code source rather than an old cheat sheet.
- Benefits: verify administrative rules without allowing them to change the code.
- Communication: present patient responsibility as an estimate, not a promise.
Decision matrix for documentation quality
| Finding | Action before claim | Do not do |
|---|---|---|
| Service is clear; coverage uncertain | Report accurately and verify benefits | Replace it with a “covered” code |
| Record lacks a required clinical fact | Ask the treating clinician for a compliant clarification | Infer or invent the fact |
| Attachment and note conflict | Resolve the discrepancy and preserve amendments | Submit whichever version looks favorable |
| Current code changed | Apply the code set effective for the service date | Use a familiar obsolete entry |
| Payer requests more information | Answer the precise request with relevant records | Send an uncontrolled chart dump |
| Denial cites frequency or exclusion | Review eligibility, history and contract language | Assume the procedure was miscoded |
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.
Free for members
Keep reading — it's free
The rest of this article is open to DentalReach members. Create a free account, or sign in, and every article on the site opens in full.