ICD-10 code S02.651K: Fracture of angle of right mandible, nonunion

Key takeaways

ICD-10 code S02.651K reports a fracture of the angle of the right mandible at a subsequent encounter, with nonunion.

The 7th character K means the provider documented failed healing, which separates it from routine healing (D) and delayed healing (G).

Six 7th characters exist for S02.651: A and B for initial encounters, D, G and K for subsequent ones, and S for sequela.

The note has to state laterality, encounter type and nonunion in the provider’s own words before a coder assigns K.

Practice management software like Pabau holds the clinical note and the claim in one place, so the coder reads the provider’s own wording.

ICD-10 code S02.651K reports a fracture of the angle of the right mandible at a subsequent encounter, where the bone has failed to heal. The 7th character K carries all of that weight. It tells the payer the fracture never united.

Most mandibular angle fractures heal on schedule. The ones that fail arrive on a coder’s desk as a judgment call. K is the character people reach for too early.

Nonunion is a clinical finding that a provider has to state, so the character you assign has to trace back to something the surgeon wrote. Start with what the code says on the claim.

What S02.651K covers, and when it is billable

S02.651K is a billable, valid ICD-10-CM diagnosis code. Its official description reads: Fracture of angle of right mandible, subsequent encounter for fracture with nonunion.

The 2026 edition took effect on October 1, 2025. It is valid in every HIPAA-covered electronic transaction, per CMS ICD-10 guidance. The code sits in the S00-T88 injury block, inside the S00-S09 chapter for injuries to the head.

S02.651K belongs to ICD-10-CM, the American version of the classification. That makes it different from the WHO’s international ICD-10, so US claims always use the ICD-10-CM string above. Everything else on the claim follows the usual rules for HIPAA-compliant medical billing.

What the 7th character K signals on a claim

The 7th character K tells the payer that a fracture already treated has stopped healing. It is not optional on S02.651. Leave it off and the code is incomplete, so the claim rejects on submission.

S02.651 takes six 7th characters, and each one describes a different encounter. The treating provider’s documentation decides which one applies. Coders never infer healing status on their own.

Section I.C.19.a of the ICD-10-CM Official Guidelines sets these rules, and CMS publishes them jointly with the National Center for Health Statistics. They govern every trauma fracture code, not just this family. Consistent clinical documentation practices at the point of care are what make the character defensible six months later.

Nonunion has to be a documented finding

Nonunion means the fracture has not healed and is not expected to heal without further intervention. It is a complication in its own right, and it changes how the case is managed.

That matters here because K needs more than elapsed time. The provider has to write that healing failed. Thresholds shift by payer and by clinical context, so counting weeks and drawing the conclusion yourself is never enough.

How to choose between D, G and K

The character reflects healing status, never how long the patient has been coming back. Hold onto that one distinction and most errors in this family disappear.

• Use D when the provider records normal progression, callus formation, or healing as expected.
• Use G when healing is happening but running slow, with no finding of failed union.
• Use K when the provider states nonunion, failed union, or a finding such as persistent mobility at the fracture site.
• Use S when the fracture has resolved and the patient returns with a late effect of the original injury.

So a note reading “patient returns for follow-up, fracture healing well” cannot support K, however many months have passed. Clinical records that hold the surgeon’s exact healing language are what protect the practice when an auditor asks.

Why the mandibular angle gives way

The angle of the mandible is the curved corner where the vertical ramus meets the horizontal body of the jaw. It fails often for two reasons. The bone changes direction at that corner, and third molars frequently sit in the same spot and thin the wall.

Angle fractures account for roughly 20% to 36% of all mandibular fractures, according to published oral surgery literature. Blunt force is the usual cause, most often a motor vehicle collision, a fall, or an assault. Side matters clinically as well as for coding, because nerve proximity, surgical approach and occlusal effects all differ.

• Laterality: the right side has to be confirmed on exam and imaging. S02.651 is right-specific, S02.652 is left, and S02.650 is unspecified.
• Fracture type: angle fractures may be displaced or not. The code does not capture displacement, but the note still should.
• Associated injuries: angle fractures often pair with subcondylar or parasymphyseal fractures, and each site needs its own code.
• Nonunion risk: infection, poor bone contact, weak fixation and smoking all raise the odds of failed union.

Oral and maxillofacial, ENT and trauma teams see these patients across many follow-up visits, so consistency is the real work.

A surgical EMR that carries laterality, mechanism and healing status forward keeps every encounter aligned. Practices that repair nonunion with grafts or biologics need the same continuity in their regenerative medicine records.

The full S02.65 family, side by side

S02.651K sits inside a tightly structured family. Reading the whole set at once is the fastest way to catch a laterality slip or the wrong encounter character.

For right-side fractures, S02.651 is always the parent. Reach for S02.650 only where laterality genuinely cannot be documented, not where it simply was not. Payers query unspecified codes when a specific one exists.

One subcategory over, S02.600D covers the body of the mandible with routine healing. That is a common miscode when an operative note says “jaw” and nothing more precise.

Three tests to clear before you code K

All three of these have to be true at the same time. If one fails, K is the wrong character.

1. The fracture is at the angle of the right mandible. Not the body, condyle, symphysis or ramus. Confirm the site from imaging and the operative note.
2. The encounter is subsequent. Active treatment has finished, and the patient is under ongoing management or secondary repair.
3. The provider has documented nonunion. Delayed healing and prolonged recovery are different findings, and they carry different characters.

Meet all three and S02.651K is correct. Where only the first two hold and healing status is blank, the next step is a provider query rather than a guess.

What a chart note must show

A note that supports S02.651K covers six elements. Digital intake forms let you build all six into the follow-up template, so nothing depends on the surgeon remembering.

• Laterality confirmed: “right mandible” or “right side” stated in the exam or the imaging findings.
• Encounter type established: the note shows a return visit for a fracture that was already treated.
• Nonunion documented: the provider writes “nonunion”, “failed union”, “absence of bridging callus”, or equivalent.
• Imaging referenced: a panoramic radiograph, CT or CBCT finding backs up the conclusion.
• Mechanism noted: the original injury appears in the record, even if it was first captured at initial treatment.
• Plan documented: revision surgery, bone grafting, extra fixation, or watchful waiting.

Once the note is complete, the claim itself has its own set of requirements. Claims management software checks that every field an insurer needs is present and holds the claim back from submission until it is.

A status dashboard then shows where each claim sits after it goes out. Format and completeness problems surface early, though the healing-status decision still belongs to the provider and the coder.

How the claim moves, and where it stalls

S02.651K rarely travels alone. It usually rides with a procedure code for the repair, and that pairing is where claims get held up.

Nonunion is what triggers a second intervention. Bone grafting for a major defect is reported with CPT code 20902, and non-invasive bone stimulation with CPT code 20979.

Line up the diagnosis and the procedure on the same date of service. Otherwise the payer asks why a nonunion diagnosis appears on a visit where nothing was done about it.

Before you submit: a quick check

These six questions take about thirty seconds, and they catch most problems before the claim goes out.

• Does the note name the right side in the provider’s words, rather than the coder’s?
• Does it say nonunion, or only that healing is slow?
• Is there an imaging finding sitting behind the nonunion statement?
• Is this visit clearly a follow-up rather than active treatment?
• Does an external cause code from the original injury still belong on the claim?
• Do the procedure codes on the claim match the plan written in the note?

Mistakes that turn into denials

Four errors account for most of the S02.651K claims that come back.

• Coding K by the calendar. Six months of follow-up visits is not a nonunion finding.
• Carrying the initial character forward. A follow-up visit never keeps A or B, whatever the original injury looked like.
• Dropping to S02.650 when the note says “right”. Unspecified laterality invites a query you did not need.
• Reporting K and S together. A fracture cannot be both unhealed and resolved with a late effect.

Where S02.651K sits in the ICD-10-CM hierarchy

Each level of the hierarchy narrows the injury until one billable code is left. Reading it top to bottom is a quick way to check you have not stopped a character short.

The CDC ICD-10-CM tool carries the official tabular navigation for S02, including the index entries that lead to angle-of-mandible fractures. Underneath the whole structure, the rule stays simple.

Code to the highest level of specificity the documentation supports, and no further. The same discipline runs across the chapter, so S42.90XG records delayed healing at the shoulder girdle in exactly the same way.

How Pabau keeps trauma notes and claims in step

Most practices code S02.651K from a note written somewhere else. The surgeon dictates into one system, the coder reads a summary in another, and the healing language gets shortened on the way across.

Practice management software like Pabau keeps the note and the claim in one record, so the coder reads what the provider actually wrote.

For codes that turn on a single character, that wording is everything. Pabau Scribe, our AI scribe, drafts the encounter note from the consultation itself. Structured templates then hold fields for laterality, encounter type and healing status, so an oral surgery team gets the same prompts at every fracture follow-up.

Claims then leave with the insurer’s required fields already filled in, and submission is held until they are.

Practices can also see how EHR integration ties clinical records to billing, so a follow-up note and its claim never drift apart. Fewer queries go back to the surgeon, and subsequent-encounter codes keep an audit trail worth defending.

Keep trauma notes and claims in one record

Pabau links the clinical note to the claim, so laterality, encounter type and healing status reach billing exactly as the provider wrote them. That means fewer queries back to the surgeon and cleaner submissions.

Book a demo

Conclusion

S02.651K is a narrow code doing one specific job. It says a right mandibular angle fracture was treated, came back, and never united.

Nearly every error in this family starts the same way, with a coder settling a healing status the provider never stated. So read the healing language before you read the calendar. Where the wording is vague, query it, and pick the character afterwards.

Get that habit right and the whole episode holds together. A clean run of subsequent-encounter characters shows a payer that the fracture was tracked rather than guessed at. Book a demo to see how Pabau keeps the operative note and the claim reading the same way.

Continue your research

Coding the same jaw at a different site? S02.600D walks through the body of the mandible at a subsequent encounter with routine healing.

Need the character for healing that is slow but still moving? S42.90XG shows how delayed healing is reported elsewhere in the chapter.

Billing non-invasive treatment for a failed union? CPT code 20979 covers low intensity ultrasound stimulation of bone, including coverage limits.

Grafting the defect instead? CPT code 20902 sets out the documentation a major bone graft claim needs.

Facial trauma rarely arrives on its own. S06.307A explains how a co-occurring focal brain injury is coded at the initial encounter.

Frequently asked questions