ICD-10 code S53.116D: Anterior ulnohumeral dislocation

Key takeaways

S53.116D is a billable ICD-10-CM code for anterior dislocation of the unspecified ulnohumeral joint at a follow-up visit.

The code is valid for FY2026, which runs from October 1, 2025 through September 30, 2026.

The 7th character D covers the whole healing phase, so S53.116A belongs only on the first treatment encounter.

Most S53 denials trace back to a note that never states whether the visit is initial or follow-up care.

Practice management software like Pabau prompts for encounter type while the note is written, not after the claim is built.

S53.116D is a valid, billable ICD-10-CM code for anterior dislocation of the unspecified ulnohumeral joint at a subsequent encounter. The Centers for Medicare and Medicaid Services (CMS) lists it as valid for FY2026. That fiscal year runs from October 1, 2025 through September 30, 2026.

The parent code S53.116 is not billable on its own. Coders have to append the right 7th character, A, D or S, before the code is valid for HIPAA-covered transactions.

What is anterior dislocation of the ulnohumeral joint?

Anterior dislocation of the ulnohumeral joint means the ulna has been forced forward, off the end of the humerus. The ulnohumeral joint, also called the humeroulnar joint, is where the trochlea of the humerus meets the trochlear notch of the ulna.

That joint is the elbow’s main hinge, and it drives flexion and extension. Forward displacement is far less common than the posterior dislocation most elbow injuries produce, which is why the anterior codes sit in their own subcategory.

The word unspecified in S53.116D refers to laterality. The record does not say whether the left or the right elbow was involved. Where the note does identify a side, the laterality-specific sibling code applies instead.

The code turns up most often on physical therapy follow-ups, orthopedic outpatient check-ins, and post-reduction monitoring. In each case the patient has already had initial care for the dislocation and is back for the rest of it.

Where S53.116D sits in the code hierarchy

The table below traces the full path, from the injury section down to the billable code. Running that check takes seconds, and it catches parent or child code mismatches before a claim goes out.

What the 7th character D means

The 7th character on an injury code records the type of encounter. That rule sits in Section I.C.19.a of the ICD-10-CM Official Guidelines for Coding and Reporting. Getting it wrong is one of the most common causes of claim rejection across musculoskeletal categories.

Key distinction: S53.116D covers the whole healing and recovery phase, not just the first post-acute visit. A physical therapist treating the fourth week of rehab after an elbow reduction still codes S53.116D. The 7th character reflects the phase of care, not the visit number.

Once healing is finished and the practice is treating a lasting effect, the 7th character becomes S instead. Other joints follow the same logic, as S63.004S does for the wrist. Fracture codes add characters the dislocation codes never use, which is why S62.163P exists for a malunion.

When to use S53.116D and what to document

Supporting S53.116D on a claim means the record has to establish a few facts. The medical forms behind the visit should show that it follows prior initial treatment for the same dislocation episode.

Required documentation elements to support ICD-10 Code S53.116D:

• Confirmation that initial treatment for the anterior ulnohumeral dislocation was already given at an earlier encounter
• Clear notation that this visit is for follow-up, rehabilitation, or monitoring during healing
• The joint involved, which is the ulnohumeral joint, even where laterality is unspecified
• The direction of the dislocation, documented as anterior in the clinical note
• The encounter type in the provider’s own words, such as follow-up for elbow dislocation or PT for post-reduction rehab

One check is worth adding to every S53 claim review. S53.116D is an unspecified-laterality code, yet almost every elbow chart names a side somewhere. Read the imaging report and the therapy note before settling for the unspecified version.

If either document says left or right, the claim should carry S53.115D or S53.114D. Unspecified codes are the ones payers pull for documentation review, so the specific code is the safer submission whenever the record supports it.

Common documentation mistakes: flag any note that describes an elbow injury without saying whether it was a dislocation or a sprain. Flag any note that leaves out whether the visit is initial or follow-up. Either omission blocks correct 7th character assignment and usually triggers a denial.

Keeping HIPAA-compliant documentation workflows in place means records stay complete and accurate, ready to support the coding decision at the point of care.

Sibling codes and laterality choices

The S53.11 subcategory covers anterior subluxation and dislocation of the ulnohumeral joint with full laterality detail. Where documentation identifies the affected side, the laterality-specific code replaces S53.116D. Practices handling sports medicine cases tend to see all three variants.

Subluxation means partial displacement and covers S53.111 to S53.113. Dislocation means complete displacement and covers S53.114 to S53.116.

The two are not interchangeable, so the note has to say whether the joint was partially or fully displaced. Coding a subluxation when the record says dislocation can trigger a payer audit.

MS-DRG grouping and reimbursement context

For inpatient admissions, S53.116D groups into two MS-DRGs under version 43.0 of the MS-DRG classifications. Which one applies depends on whether a major complication or comorbidity (MCC) is documented.

• MS-DRG 562: Fracture, sprain, strain and dislocation except femur, hip, pelvis and thigh with MCC
• MS-DRG 563: Fracture, sprain, strain and dislocation except femur, hip, pelvis and thigh without MCC

MS-DRG groupings are updated annually, and the v43.0 assignments above apply to FY2026. Practices handling inpatient billing should re-check the current grouping at the start of each fiscal year.

ICD-9-CM crosswalk

Practices reconciling historical records or legacy billing data may need to map S53.116D back to its ICD-9-CM predecessor. The General Equivalence Mappings (GEMs) give an approximate crosswalk, though ICD-9 never carried the same anatomical or encounter-type detail.

GEMs conversions are rarely one to one. When you convert a historical record, document the rationale behind the mapping. Note as well that the ICD-9 code never carried the anatomical or encounter detail the ICD-10-CM version does.

How Pabau keeps 7th character coding accurate

The 7th character is decided when the note is written, not when the claim is built. Practices working from free-text notes lose the details that settle the code. Laterality, encounter type, and dislocation versus subluxation end up buried in narrative or missing altogether.

Practice management software like Pabau puts those fields in front of the provider instead. Digital intake forms capture injury type, laterality and prior treatment history as structured data. Claims management then carries that data through to the claim, so nobody has to chase the treating provider for it.

EHR integration keeps documentation and billing data connected across the whole patient journey. Fewer incomplete records at the front end means far less rework at the back end.

Pabau’s patient care management tools cover multi-specialty practices seeing both acute and follow-up musculoskeletal cases. The result is a tighter loop from documentation to reimbursement, and fewer denials on encounter-type codes like S53.116D.

Reduce ICD-10 coding errors at point of care

Pabau's claims management helps orthopedic and physical therapy practices catch ICD-10-CM errors before claims go out. That means fewer denials and less rework across the S53 category.

Book a demo

Conclusion

The hard part of S53.116D is not finding the code. It is proving the encounter type in the note. Get that one line into the chart and the rest of the claim follows on its own.

So put the check where the documentation happens, not in the billing queue. A coder who has to reconstruct the phase of care from a narrative note ends up guessing. A guess on the 7th character is exactly what payers send back.

Pabau’s practice management software gives orthopedic and rehabilitation teams the structured fields that make that check automatic. Book a demo to see how it keeps S53-category claims clean.

Continue your research

Checking nerve recovery after an elbow injury? Two-point discrimination test sets out normal values and the technique for sensory testing at follow-up.

Need a range of motion record for rehab notes? Hip range of motion test gives you a measurement template you can adapt for other joints.

Coding a late effect rather than a follow-up? S56.114S shows how the sequela character changes what the claim describes.

Rolling out structured notes to a new team? EHR training is a practical guide for practice managers running the switch.

Losing time between the visit and the claim? Patient flow explains where the delays build up and how to clear them.

Frequently asked questions