Arrow left
Back to blog
Vector illustration of a dental implant screw anchored in jawbone supporting a tooth crown next to a clipboard with dental records an insurance shield an invoice document with a dollar symbol and a gear icon on a light blue background
June 3, 2025

Understanding Dental Code D6092 – Re-cement or re-bond implant/abutment supported crown

Learn when and how to accurately use D6092 dental code for re-cementing or re-bonding implant-supported crowns, with practical billing tips and documentation best practices.

Understanding Dental Code D6092

When to Use D6092 dental code

The D6092 dental code is designated for the re-cementation or re-bonding of an implant or abutment-supported crown. This CDT code should be used when a previously placed implant or abutment-supported crown becomes loose or dislodged and requires reattachment, but the restoration itself is not being replaced. It is important to distinguish this from codes used for natural tooth crowns or for the replacement of the crown itself. Proper use of D6092 ensures accurate billing and minimizes claim denials.

Documentation and Clinical Scenarios

Accurate documentation is essential when billing for D6092. Your clinical notes should clearly state the reason for the visit, the condition of the implant and crown, and the steps taken to re-cement or re-bond the restoration. Include details such as:

  • Date of original crown placement
  • Type of implant or abutment system
  • Assessment of the crown and abutment (e.g., no damage, intact margins)
  • Materials used for re-cementation or re-bonding
  • Patient’s response and post-procedure instructions

Common clinical scenarios include crowns that have loosened due to occlusal forces, minor trauma, or cement failure. If the crown or abutment is damaged and requires replacement, refer to the appropriate code, such as D6096 for removal and replacement of implant crowns.

Insurance Billing Tips

To maximize reimbursement and reduce accounts receivable (AR) delays, follow these best practices when billing D6092:

  • Verify coverage: Not all dental plans cover implant-related procedures. Confirm patient benefits and limitations before treatment.
  • Submit clear documentation: Attach clinical notes, pre- and post-op radiographs or photos, and a narrative explaining why re-cementation was necessary.
  • Use the correct code: Do not use D6092 for natural tooth crowns or for new crown fabrication. If the abutment or implant is also being repaired, additional codes may apply.
  • Appeal denied claims: If a claim is denied, review the Explanation of Benefits (EOB), address the payer’s reasons, and submit a detailed appeal with supporting documentation.

Staying up to date with payer policies and CDT code updates is crucial for successful dental billing and revenue cycle management.

Example Case for D6092

Case: A patient presents with a loose implant-supported crown on tooth #30. The crown was placed two years ago and is otherwise undamaged. After clinical evaluation, the dentist determines the crown and abutment are intact, and the crown is re-cemented using appropriate implant cement. The procedure is documented, and D6092 is billed to the patient’s insurance with supporting notes and intraoral photos. The claim is processed and paid according to the plan’s implant coverage policy.

This example highlights the importance of thorough documentation and correct code selection to ensure timely reimbursement and compliance with dental insurance standards.

DayDream helps dentists put their billing on autopilot. Interested in learning more? Book a demo today.

Star
Schedule a call
Schedule a call

FAQs

Is there a frequency limitation on how often D6092 can be billed for the same patient?
Can D6092 be used for re-cementing or re-bonding crowns on natural teeth or bridges?
What should be done if the insurance denies a claim submitted with D6092?

Have more questions about billing? Send us an email and one of our experts will get back to you in 1-2 days!

Submission confirmed. We'll be in touch.
Oops! Something went wrong while submitting the form.