Insurance Coding for Full-Arch Restorations: A Practical Guide for Restorative Practices

Full-arch restorations are the highest-revenue procedure most general practices will ever bill, and they are also the most likely to get pended, downgraded, or denied. The clinical work is hard. The coding is harder, because the CDT framework was not built around a workflow that includes guided surgery, immediate-load provisionals, and a final monolithic zirconia prosthesis screwed into four or six implants. The codes exist. They just have to be sequenced correctly.

This is a coding primer, not a billing-company pitch. The goal is to help the restorative team get cleaner submissions on the first pass so the case does not stall between surgery day and final delivery.

Start With the Treatment Phase, Not the Code Book

Every full-arch case has at least three billable phases: diagnostic and surgical planning, surgical placement with provisional, and the definitive prosthesis. Most denials happen because someone tried to code the whole case as a single event, or split the phases across calendar years without a documented treatment plan tying them together.

Before the first code goes on the claim, the chart should show:

• A diagnostic record set (CBCT, intraoral scan or impression, photographs)
• A written treatment plan with the phased sequence
• The prosthetic design decision (fixed hybrid vs. removable overdenture vs. fixed zirconia bridge)
• The implant count and intended attachment type

That last point matters more than most practices realize. The difference between a D6114 (implant/abutment supported removable denture for edentulous arch) and a D6118 (implant/abutment supported interim fixed denture for edentulous arch) is not interchangeable language. The plan dictates the code, and the code dictates the narrative the carrier will accept.

The Codes That Matter Most

The CDT codes that show up on nearly every full-arch claim cluster into four groups. Knowing which ones to lead with, and which ones to bundle, is half the battle.

Diagnostic and surgical guide

• D0364 to D0367: cone beam imaging, billed once per arch, with a narrative explaining the diagnostic necessity for implant planning.
• D6190: radiographic/surgical implant index. This is the surgical guide code. It is frequently denied as inclusive, so the narrative needs to explain that the guide was fabricated from CBCT-merged data and is not the same as a stent.

If the lab fabricated the guide from a digital plan, that detail belongs in the narrative. A CBCT-derived, tooth-supported or bone-supported guide is a different deliverable than a vacuum-formed stent, and carriers that understand the distinction will pay D6190 more consistently when the documentation reflects it.

Surgical placement

• D6010: surgical placement of implant body, billed per implant.
• D7953: bone replacement graft for ridge preservation, when indicated and documented preoperatively.
• D6104: bone graft at time of implant placement.

For an All-on-4 case, that is four units of D6010. For All-on-6, six units. Bundle these on the surgical date of service with the surgeon's operative note attached. If the restorative dentist and the surgeon are different providers, this claim belongs on the surgeon's side, not the restorative side.

Provisional prosthesis

• D6118orD6119: interim fixed denture for edentulous (D6118) or partially edentulous (D6119) arch.

This is where immediate-load cases get coded. The interim is a billable deliverable. It is not included in the final prosthesis code, and it should not be written off as a freebie. The narrative should reference the same-day load protocol and the planned conversion timeline.

Definitive prosthesis

• D6114 / D6115: implant/abutment supported removable denture for edentulous (D6114) or partially edentulous (D6115) arch.
• D6116 / D6117: implant/abutment supported fixed denture for edentulous (D6116) or partially edentulous (D6117) arch.
• D6078 / D6079: implant/abutment supported fixed denture for completely or partially edentulous arch, by some carrier interpretations. Use the version your carrier guidance documents accept.

The choice between the D6114 series and the D6116 series is the single most consequential coding decision in the case. Removable overdenture cases code differently than fixed hybrids, and the narrative has to match the prosthetic design the lab delivered.

Where Cases Get Denied

In our experience reviewing claim feedback with referring practices, denials on full-arch cases cluster around four recurring issues.

Missing pre-authorization on the definitive prosthesis.Most carriers require pre-auth for any prosthesis code in the D6100 series. Submitting without it almost guarantees a 30 to 60 day pend while the carrier requests documentation that should have been in the original packet.

Inconsistent provider taxonomy across phases.When the surgeon bills D6010 and the restorative dentist bills D6116, the carrier wants to see both providers documented on the treatment plan. A claim that arrives without a clear handoff narrative gets flagged for coordination of benefits review.

Bundled abutment codes.D6056 (prefabricated abutment) and D6057 (custom abutment) are separately billable in most plans, but only when the abutment is documented as a distinct deliverable. Custom milled titanium or zirconia abutments fabricated by the lab need to show up as D6057 with the lab invoice attached. Bundling them into the prosthesis code leaves money on the table on every case.

Calendar-year annual maximum confusion.A $28,000 full-arch case will always exceed the annual maximum. The question is whether the case is structured to maximize benefit across two plan years or to use a third-party financing flow for the balance. That decision belongs in the treatment plan conversation, not at the final delivery appointment.

What the Lab Should Be Sending With Every Case

A full-arch case packet from the lab should include the documentation that makes the coding defensible: the digital design files, the CAD/CAM design summary, the material specification for the final prosthesis, and the abutment specifications with manufacturer references. When the carrier asks for documentation on D6057 or D6190, the practice should be able to pull it from the case file without calling the lab back.

This is the operational difference between a lab partnership and a lab transaction. The practices that get cases paid on the first submission have a workflow where the lab anticipates the documentation request. The practices that fight denials are usually the ones piecing the packet together after the fact.

A Note on DSO Coding Workflows

For multi-location practices, the coding workflow needs to be standardized across offices or the case mix will produce inconsistent submission quality. A documented coding playbook (which codes get used for which prosthetic designs, which narratives get attached, which carriers require pre-auth) protects the revenue cycle from drift as the group adds locations. The lab partner should be a participant in that playbook, not a downstream vendor.

Full-arch restorations are not getting simpler. The clinical workflows are evolving toward immediate-load, digital-design, monolithic-material cases that the CDT code book is still catching up to. The practices that win on these cases are the ones that treat coding as part of the clinical plan, not as an afterthought on delivery day.