ICD code S54.22XD – Radial nerve injury at forearm level, left arm

Key takeaways

S54.22XD is a valid, billable ICD-10-CM code for FY2025 and FY2026 under category S54, injury of nerves at forearm level.

The 7th character D marks a subsequent encounter, meaning routine care while the injury heals after active treatment has ended.

The clinical note must name the left arm, or the claim no longer supports S54.22XD over the unspecified code S54.20XD.

Payers often question S54.22XD when the claim history holds no record of the original injury and its active treatment.

Practice management software like Pabau pre-fills claims from the patient record, then submits and tracks them through the Claim.MD clearinghouse.

ICD-10 code S54.22XD: quick-reference summary

ICD-10 code S54.22XD is the billable ICD-10-CM code for injury of radial nerve at forearm level, left arm, subsequent encounter. Use it once active treatment has ended and the patient is receiving routine care while the nerve recovers.

The table below lists the core attributes to confirm before you submit the claim. Every field reflects the CMS ICD-10-CM Tabular List for FY2025 and FY2026.

Code definition and clinical scope of S54.22XD

S54.22XD covers traumatic injury to the radial nerve at the forearm level, left arm, during the subsequent (healing or recovery) phase of care. At this level the radial nerve runs along the lateral forearm. It supplies the wrist and finger extensors and carries sensation from the back of the hand and the thumb web space. Lacerations, fractures, compression and traction at this level can disrupt both motor and sensory function.

Three boundaries define what this code does and does not cover:

• Traumatic injury only. S54.22XD applies to nerve damage caused by an external event. Non-traumatic radial neuropathy (such as compression from a space-occupying lesion or systemic peripheral neuropathy) is coded elsewhere.
• Forearm level. The injury must be at the forearm segment. Radial nerve injuries at the wrist and hand level fall under category S64, not S54.
• Left arm, subsequent encounter. Both the laterality (left) and the encounter type (subsequent) are built into the 7th character extension. Missing either element in documentation creates a mismatch between the code and the clinical note.

Understanding the 7th character D: subsequent encounter rules

The 7th character D means the patient is receiving routine care during healing or recovery. The visit count plays no part, so a patient still in active treatment stays on XA at the third or fourth visit.

According to the CMS ICD-10-CM Official Guidelines, the three 7th-character options for traumatic injury codes carry these definitions:

• A: Initial encounter (XA). The patient is receiving active treatment for the condition. This includes the emergency department visit, the orthopedic or neurology consultation, and any surgical intervention. A provider other than the one who originally treated the injury can still use XA if they are providing active treatment.
• D: Subsequent encounter (XD). Active treatment is complete. The patient is in the healing or recovery phase. Routine care here includes physical therapy, occupational therapy, cast checks, or medication management for the injury.
• S: Sequela (XS). The acute injury phase has resolved but a late effect persists, such as chronic wrist extensor weakness or permanent sensory loss. The sequela code is reported as a secondary code alongside the code for the late-effect condition.

Take a physical therapist seeing a patient three weeks after a forearm laceration. Active treatment ended when the wound was closed and the nerve injury diagnosed, so the therapist reports S54.22XD, even at only the second clinical encounter. The 7th character follows the phase of care.

S54.22XA vs S54.22XD vs S54.22XS: choosing the correct 7th character

All three variants describe the same nerve injury at the same anatomical level. The 7th character alone signals the phase of care, and payers use it to validate clinical necessity for each encounter type. The diagram below walks through both choices, laterality first and then the phase of care.

Code hierarchy: parent codes and neighboring codes

S54.22XD sits within a precise code tree. Confirming its placement prevents laterality and level errors before submission.

S54.20XD (unspecified arm) should not be used when the provider’s note identifies the injured limb as left. Laterality specificity is a payer requirement and a clinical accuracy standard. Use S54.22XD whenever the note confirms left-arm involvement. For neighboring nerve and forearm injury codes, browse our ICD-10-CM reference for coders.

Excludes notes and coding limitations

S54.22XD carries inherited excludes notes from its parent category S54. These define what cannot be coded alongside it and which conditions belong elsewhere. Coders should review these before pairing S54.22XD with other nerve-related codes.

• Excludes2 – injury of nerves at wrist and hand level (S64). An injury to the radial nerve at the wrist or hand is coded to category S64, not S54. If the patient has separate nerve injuries at two anatomical levels, both codes may be reported. This is an Excludes2 note, meaning dual coding is permitted when clinically appropriate.
• Non-traumatic radial neuropathy. Radial neuropathy arising from systemic disease, compression neuropathy, or entrapment without trauma does not map to S54.22XD. Code a non-traumatic radial nerve lesion to G56.3-, lesion of radial nerve, or to the relevant peripheral neuropathy code. G56.32 covers the left upper limb.
• Wrist drop as the primary diagnosis. Wrist drop is a clinical sign. It may be documented alongside S54.22XD as a supporting finding, but it never replaces the nerve injury code.

For the full Chapter 19 tabular notes, check the CDC/NCHS ICD-10-CM web tool.

Clinical presentation associated with S54.22XD

Wrist drop is the hallmark of radial nerve injury at or proximal to the forearm-level extensor compartment. Coders validating documentation against S54.22XD should look for these clinical findings, which confirm the nerve injury is at the correct anatomical level.

• Wrist drop. Inability to extend the wrist against gravity. It results from lost innervation to the wrist extensors (extensor carpi radialis longus and brevis, extensor carpi ulnaris).
• Finger and thumb extension weakness. Weakness of the finger extensors and abductor pollicis longus, producing finger drop at the MCP joints.
• Sensory loss over the dorsal hand. Diminished or absent sensation over the dorsal thumb, index finger, and radial half of the back of the hand. This is the territory of the superficial radial nerve.
• Preserved grip strength. Grip remains relatively intact because the finger flexors and intrinsic hand muscles are supplied by the median and ulnar nerves. This finding helps separate radial nerve injury from other nerve lesions.

A nerve conduction study (NCS) or EMG/NCS confirms radial nerve involvement at the forearm level. It also distinguishes it from a higher lesion, such as a spiral groove injury at the humerus.

ICD-10-CM expects the documentation to support the specific code reported. An NCS report showing a forearm-level conduction abnormality strengthens the case for S54.22XD over adjacent codes. It is also the strongest laterality anchor when the clinical note uses vague phrasing such as “affected arm.”

Documentation requirements for payer acceptance of S54.22XD

Payer requirements for subsequent encounter codes vary by plan, but five documentation elements consistently support S54.22XD across commercial and Medicare claims. Missing any one of them is a common denial trigger.

1. Prior traumatic event with initial encounter on record. The patient’s claim history must include at least one S54.22XA (or equivalent initial encounter code) from a prior visit. If the original injury was treated elsewhere, a referral note or operative/ED report documenting the traumatic event and its treatment serves as the supporting record.
2. Provider note confirming the healing or recovery phase. Phrases such as “patient is undergoing rehabilitation following left radial nerve laceration” or “follow-up for radial nerve injury” do this job. They tell the payer that active treatment is complete.
3. Explicit laterality: left arm. The word “left” must appear in the provider’s note in direct association with the nerve injury. A note that documents “radial nerve injury” without specifying the side does not support S54.22XD.
4. No contradictory acute-injury language. If the note uses phrases such as “new injury,” “acute presentation,” or “first evaluation,” the coder should reassess whether XA applies. Contradictory language is a red flag in payer audits.
5. NCS/EMG results, when available. Electrodiagnostic results identifying radial nerve involvement at the forearm level are not universally required. They do reduce denial risk with high-scrutiny payers. Document the NCS laterality as “left” in the referencing note.

The same five elements carry you through a payer audit. Reviewing the electronic remittance advice from each payer shows how your S54.22XD claims are adjudicated, so a denial pattern surfaces while it is still small.

Commonly paired CPT codes with S54.22XD

The CPT codes submitted alongside S54.22XD reflect the care phase and the treating discipline. Physical and occupational therapy codes dominate subsequent-encounter claims. Electrodiagnostic codes appear when NCS/EMG is performed at the same visit. The table below covers the most common pairings, and AAPC Codify offers crosswalk lookups for medical necessity checks.

Common claim denial reasons for S54.22XD and how to avoid them

Denials for ICD-10 code S54.22XD cluster around a small number of predictable errors. Most stem from 7th-character misapplication or thin supporting documentation. Several of them trip automated claim edits before a human reviewer ever sees the case.

How claims management software keeps S54.22XD claims on track

Many therapy and neurology practices still copy the diagnosis, the side and the visit details from the note into a separate billing tool. Each copied field is one more place for a left-arm claim to go out coded as unspecified, or to stall without anyone noticing.

Pabau’s claims management for practices pre-fills each claim from the data already in the patient record. It then submits the claim and tracks its status through the Claim.MD clearinghouse.

The software doesn’t pick the 7th character or check laterality for you, so the five-point review above still sits with your coder. What changes is the rework. The claim carries what the note says, and you see which S54.22XD claims are paid, pending or denied in one place.

Submit and track S54.22XD claims in one place

Pabau pre-fills each claim from the patient record, then submits and tracks it through the Claim.MD clearinghouse. See how that fits your therapy or specialist practice.

Book a demo

Conclusion

S54.22XD holds up when the note names the left arm, links the visit to a documented injury, and places the patient in recovery. When one of those is missing, fix the note before you touch the code.

The trade-off is speed. An addendum request holds up one claim, while a swapped-in unspecified code or a wrong 7th character invites a denial and an appeal.

Book a demo to see how Pabau pre-fills, submits and tracks radial nerve injury claims for physical therapy and specialist practices.

Continue your research

Need to understand how claims move from code to payment? Revenue cycle management overview walks through the full claim lifecycle from coding to remittance.

Getting denials you can’t explain? Denial codes in medical billing maps the most common CARC codes to their corrective actions.

Submitting NCS or EMG claims alongside this code? Superbill documentation guide covers how to structure multi-procedure encounters for clean first-pass submission.

Want fewer claims bouncing back? What makes a clean claim lists the fields payers check before they accept a submission.

Building a denial follow-up routine? Denial management in healthcare covers how to track, appeal and prevent repeat denials.

Frequently asked questions