ICD-10 code S02.600D: Mandible body fracture, routine healing

Key takeaways

ICD-10 code S02.600D covers a fracture of the body of the mandible, unspecified side, at a subsequent encounter with routine healing.

If the record names no mandible site at all, the correct code is S02.609D rather than S02.600D.

The 7th character D marks the phase of care, not the visit number, so it starts once active treatment ends.

There is no S02.60XD code, and S02.61XD and S02.62XD were deleted in 2016, so laterality digits apply instead.

Practice management software like Pabau keeps the fracture record and the claim in one place, so missing detail surfaces before you submit.

ICD-10 code S02.600D covers a fracture of the body of the mandible, unspecified side, at a follow-up visit where healing is on track. Code lookups often shorten that to “fracture of mandible, unspecified.” The short version belongs to a different code, and that mix-up sits behind a lot of denied post-op claims.

The full descriptor is narrower than the nickname suggests. It ties the fracture to the body of the mandible, the horizontal part of the lower jaw. Only the side stays undocumented. A chart that says nothing more than “mandible fracture” will not support this code.

Oral and maxillofacial surgeons, emergency physicians, and their billing teams meet S02.600D at every healing check. Two details in the chart settle it. One is the fracture site, and the other is the phase of care at the visit. Practices with steady facial trauma volume lean on EMR software to cut the manual lookups behind these errors.

S02.600D narrows the fracture to the body of the mandible

S02.600D is valid, billable, and written for the follow-up visit rather than the repair. Its full descriptor is fracture of unspecified part of body of mandible, unspecified side, subsequent encounter for fracture with routine healing. You can confirm it in the CDC/NCHS ICD-10-CM web tool.

Two phrases in that descriptor carry the weight. “Body of mandible” fixes the anatomy and rules out the condyle, the ramus, and the angle. “Unspecified side” says the chart never recorded left or right. The site group is settled, so only laterality stays open.

Splitting the code into its characters makes selection faster, and it cuts transcription slips at a busy billing desk.

That last row is worth a second look. When ICD-10-CM launched, S02.600 read “fracture of unspecified part of body of mandible” with no side attached. CMS added “unspecified side” effective October 1, 2016, once laterality digits arrived.

The anatomy never moved. S02.600 has meant the body of the mandible in every fiscal year since 2015. So if the record names a different mandible site, a different code applies. If it names no site at all, the code is S02.609D. That single distinction is where most S02.600D errors begin.

S02.6 splits the mandible into nine coded sites

S02 covers every fracture of the skull and facial bones under CMS coding guidelines. It sits in Chapter 19, which governs injury and poisoning codes.

Inside S02, the .6 subcategory belongs to the mandible. It splits into nine site groups, and each one takes its own 5th character. Facial trauma practices, including teams running maxillofacial surgery software, work through them constantly.

• S02.60 Fracture of mandible, unspecified
• S02.61 Condylar process
• S02.62 Subcondylar process
• S02.63 Coronoid process
• S02.64 Ramus
• S02.65 Angle of mandible
• S02.66 Symphysis
• S02.67 Alveolus
• S02.69 Other specified site

S02.60 is where the confusion starts. Its heading reads “fracture of mandible, unspecified,” which makes every code below it look generic on a quick scan. Only one of them is. S02.609 carries the generic meaning, while S02.600, S02.601, and S02.602 all sit in the body of the mandible.

The other eight groups behave the same way. Add a side digit and a 7th character and you have a full code, as S02.642A does for the angle of the mandible.

Facial trauma also rarely arrives alone. A tackle or a fall that breaks a jaw often injures a shoulder too, so a claim can carry S43.303A beside the jaw diagnosis. Practices that treat contact-sport injuries all week run sports medicine software to keep both problems on one chart.

The 7th character tracks the phase of care, not the visit count

The 7th character records where the patient sits in the course of treatment. Per ICD-10-CM Official Guidelines Section I.C.19, it reflects the phase of care rather than the number of visits. S02.600 offers six.

Notice what is absent. Skull and facial fracture codes carry no malunion character, unlike many long bone fractures. Radius codes such as S52.131Q add characters for malunion and for open fracture type. For S02.600, the list runs A, B, D, G, K, S and stops there.

A worked example makes the switch to D concrete. A patient has open reduction and internal fixation of a mandible body fracture on March 3. Code that operative encounter S02.600A, because active treatment is under way.

The March 17 wire check is still active management, so it stays on the A character. On April 14 the surgeon documents union progressing normally, with no further intervention planned. That April visit is the first one that takes S02.600D.

“Subsequent” therefore has nothing to do with second. A third post-op visit can still be A. A first post-discharge visit can already be D. Treatment phase decides, every time.

S02.600S works differently again. It covers a new condition caused by the old fracture, such as temporomandibular joint arthritis found long after healing. Reach for it when you are treating the consequence rather than the fracture.

Every current sibling code ends in a laterality digit

The 6th character in S02.60, S02.61, and S02.62 is always a digit. A 0 means unspecified side, 1 means right, and 2 means left. S02.60 adds a 9, which drops the site reference altogether.

That gives a tidy set of subsequent-encounter codes across the three most-used mandible sites. Every descriptor below ends with “subsequent encounter for fracture with routine healing.”

The remaining mandible sites follow the same pattern. S02.63 to S02.65 and S02.67 all use 0, 1, and 2 for unspecified side, right, and left.

When later imaging pins down the site or the side, move to the more specific code. Carrying S02.600D forward after the chart improves leaves specificity on the table, and specificity is what defends a claim under review.

The X placeholder belongs to S02.66 and S02.69 only

Some S02.6 codes really do use an X in the 6th position, and that is where a lot of bad guidance comes from. Only two subcategories qualify. Neither of them is S02.60, S02.61, or S02.62.

• S02.66X, symphysis of the mandible. The symphysis is a midline structure, so left and right cannot apply. S02.66XD is a valid code.
• S02.69X, mandible of other specified site. The site is named but falls outside the listed groups, so no laterality digit applies. S02.69XD is valid, and so is S02.69XK for a nonunion.

Everything else in S02.6 takes a laterality digit. Three code strings that still turn up in old cheat sheets and stale crosswalk tables are therefore dead ends.

• S02.60XD has never been a valid ICD-10-CM code, in any fiscal year.
• S02.61XD and S02.62XD were valid in FY2015 and FY2016 only. The laterality expansion effective October 1, 2016 deleted both, roughly ten years ago.

A claim built on any of those three rejects as an invalid code. If your billing software still offers them, its code set needs updating.

What the record must show to support S02.600D

Auditors read the note, not the code. For S02.600D, five things need to be visible at the follow-up encounter.

• Fracture confirmed and located. Prior records or the current note must establish a fracture in the body of the mandible. The clinician does not have to re-diagnose it, but continuity of care has to be traceable.
• Active treatment finished. Wording such as “post-operative follow-up,” “routine healing check,” or “monitoring fracture consolidation” supports D. Anything implying ongoing intervention points back at A.
• Routine healing. Record the findings that show healing on track, such as an occlusion check, imaging review, or wound assessment. No timeline figure is required.
• Why the side is unspecified. S02.600D states that left and right were never documented. If the chart names a side, use S02.601D or S02.602D instead.
• External cause. ICD-10-CM guidelines call for the cause of injury as a secondary code from Chapter 20. Workers’ compensation and liability claims lean on it especially hard.

Practices using digital clinical forms can build these five checkpoints into the follow-up template. The clinician then captures them while the patient is still in the room, which beats chart review the day before submission. It also leaves the audit trail that HIPAA compliance expects across the full episode.

Several providers often document the same episode. Patient record management tools that hold one continuous clinical timeline let coders confirm the treatment phase without hunting through separate notes.

Pair the diagnosis with the right CPT code

The diagnosis code explains why the visit happened, and the CPT code explains what was done. Reimbursement follows the second one, so S02.600D on its own moves nothing.

Here is how a healing check usually reaches the payer. At the visit, the clinician documents the healing findings. The coder then picks an office or outpatient evaluation and management code from the 992xx series and links S02.600D to it. Billing scrubs the claim and sends it electronically.

The AAPC ICD-10-CM code lookup is a quick way to confirm the diagnosis code before it goes out. A few other things trip these claims up, so run through them before you submit.

• Global surgical period. A surgically treated fracture carries a global period. A follow-up inside it may not be separately billable unless modifier 24 or 25 applies.
• Repair codes. Intermediate repair codes such as 12032 belong to the initial encounter, and the face has its own range. A routine healing check bills an evaluation and management service instead.
• Symptom codes. The fracture already explains the pain, so a code such as R52 adds nothing beside S02.600D.
• Payer edits. Some payers run medical necessity edits that want the healing phase documented alongside a D-character code. Check the policy first.
• Multiple fractures. Mandible fractures travel with other facial fractures. Code each site that carries its own clinical finding, then sequence by the standard multiple injury rules.
• Electronic submission. S02.600D is accepted on HIPAA-standard electronic claims. Claims management software keeps the fracture record and the claim in one system, so missing detail shows up before the claim leaves the practice.

That same split holds in every specialty. A diagnosis justifies medical necessity, and the procedure describes the service.

Six mistakes that turn an S02.600D claim into a denial

Denials and audit flags on this code cluster around a short list. Working through it once usually clears most of the rework.

• Using S02.600D when no site is documented. If the chart says “mandible fracture” and nothing more, the code is S02.609D. S02.600D asserts a body-of-mandible fracture the record does not support.
• Coding a deleted or invented X code. S02.60XD does not exist, and S02.61XD and S02.62XD were deleted on October 1, 2016. Use the laterality digits instead.
• Keeping A after active treatment ends. This is the most frequent one. Once the surgeon signs off on active management, the follow-up takes D.
• Treating D as visit number two. Submitting A for three post-op visits and D for the fourth applies the character by appointment count. Clinical status drives it, not sequence.
• Reaching for S at the first sign of slow healing. Sequela codes cover late effects. Delayed healing takes G, and nonunion takes K.
• Skipping the external cause code. Chapter 20 codes matter for liability and workers’ compensation, and many payers expect them beside a fracture diagnosis.

Sorting denials by diagnosis code shows whether S02.600D rejects more often than its neighbors. That pattern usually points at one of the six. The chart drives the code, and the code has to match the phase of care the chart describes.

How Pabau keeps mandible fracture records and claims in step

Most of the errors above start in the record rather than the claim. The fracture site sits in an imaging report nobody reopened. Meanwhile, the healing note lives in one system while the claim gets built in another.

Practice management software like Pabau puts the whole episode in one place. The operative note, the imaging, the follow-up forms, and the invoice all hang off the same patient record. A coder checking whether active treatment ended reads it straight off the timeline.

Custom clinical forms let you build a fracture follow-up template that asks for the site, the side, and the healing status every time. Pabau also checks the required fields before a claim can go out, and a status dashboard shows where each one stands.

None of that picks your 7th character. It does mean the note behind the code is one click away when a payer asks.

Keep fracture follow-up notes and claims together

Pabau brings the operative note, imaging, follow-up forms, and the claim onto one patient record. Coders can confirm the site, the side, and the phase of care without leaving the chart.

Book a demo

Conclusion

S02.600D is a precise code wearing a vague label. Treat it as the body-of-mandible code it has always been and most of its denial risk goes away. Read the site out of the chart, then the phase of care, and pick the character last.

The trade-off worth remembering is specificity. An unspecified-side code is valid and it will pay, but it tells a payer the chart came up short. Whenever the record names a side, the more specific sibling makes the stronger claim.

If your team reconciles fracture notes in one system and builds claims in another, that split is where character errors breed. Book a demo to see how Pabau keeps the clinical record and the claim on one page for facial trauma follow-ups.

Continue your research

Need the delayed-healing version of this pattern? S42.90XG walks through the G character when a fracture stops progressing on schedule.

Want to see how open fracture characters work? S52.001E shows the extra open fracture detail that long bone codes carry and the mandible list leaves out.

Need the same logic for a dislocation? S43.139D applies the subsequent-encounter character to a joint injury rather than a fracture.

Rebuilding your follow-up note? The SOAP progress notes template gives you a structure that captures the healing findings a D character needs.

Found debris at a healing check? M79.5 covers a residual foreign body in soft tissue, which can surface long after the original injury.

Frequently asked questions