ICD code S65.192S – Left radial artery wrist injury sequela

Key takeaways

S65.192S codes a sequela of other specified left radial artery injury at wrist and hand level, distinct from initial (A) or subsequent (D) encounters.

The code is specific to the left arm, so a right-arm injury takes S65.191S and an unspecified arm takes S65.199S.

The sequela manifestation, such as chronic pain or a scar, is sequenced first, and S65.192S follows as the code for the causal injury.

A claim that reports S65.192S without the manifestation code breaks the sequencing rule and can trigger denials or payer queries.

Pabau, the practice and billing software we build, routes claims through Claim.MD edits that flag sequencing errors before submission.

ICD-10 code S65.192S: Quick reference

ICD-10 code S65.192S reports other specified injury of the radial artery at wrist and hand level of the left arm, at a sequela encounter. It applies when the patient is treated for a lasting effect of the old injury, and that effect is coded first.

S65.192S sits within category S65, which the CDC/NCHS ICD-10-CM tabular list defines as injuries of blood vessels at wrist and hand level. The table below captures the key attributes coders need before submitting a claim.

What S65.192S covers: Code definition and clinical scope

S65.192S applies when a patient presents with a lasting consequence of a left radial artery injury at the wrist or hand level. The injury itself is historical. What the coder documents is the sequela, a condition that exists because of the original trauma.

The “other specified” qualifier is the key distinction. It means the documented injury was neither a laceration (S65.112S) nor left unspecified (S65.102S). Common scenarios that land here include arterial thrombosis after blunt trauma, post-traumatic arterial scarring, and documented pseudoaneurysms.

• Chronic vascular insufficiency of the radial artery following a crush or blunt injury to the wrist
• Post-traumatic arterial fibrosis or scarring at the wrist or hand level, documented by the treating clinician
• Residual functional impairment of the hand attributed to prior radial artery damage (e.g. reduced grip strength, cold sensitivity)
• Documented pseudoaneurysm resulting from a prior radial artery injury at the wrist where no more specific code applies
• Ongoing pain directly attributed by the physician to radial artery damage, reported alongside a secondary pain code

The physician’s documentation must explicitly connect the current condition to the prior radial artery injury. A vague reference to “wrist pain” without a link to the original trauma does not support S65.192S.

Understanding the 7th character S: Sequela vs initial vs subsequent encounter

The ICD-10-CM Official Guidelines define three encounter types for injury codes through the 7th character. Picking the wrong one is a common coding error across the S65.192 family.

S65.192S vs S65.192A vs S65.192D: Choosing the right encounter code

The clinical phase decides the switch from D to S, whatever the calendar says. A patient still healing from a repair is coded S65.192D, even months later. A patient whose injury has stabilized but who now has chronic vascular symptoms is coded S65.192S.

A practical test: Ask whether the treating clinician would describe the injury as “healing” or as “healed but causing ongoing problems.” Healing means D. Healed with lasting consequences means S.

What S65.192S excludes: Codes not covered by this descriptor

S65.192S is tightly scoped. Several adjacent clinical scenarios require a different code entirely.

• Unspecified radial artery injury at wrist, sequela: Use S65.102S (left arm) when the injury type cannot be specified at all. A known injury type without its own code still belongs in S65.192S.
• Ulnar artery injury at wrist, sequela: The ulnar artery has its own S65.0- subcategory. Other specified injury of the left ulnar artery, for example, is S65.092S. It runs on the little-finger side of the wrist and never belongs in S65.1-.
• Radial artery injury at a different anatomical level: S65.192S is specific to wrist and hand level. Injuries of the radial artery in the forearm or elbow use codes from other categories.
• Laceration of the radial artery: When documentation specifies a laceration, use S65.112S for the left arm rather than defaulting to “other specified.”
• Right or unspecified arm: A right-arm injury takes S65.191S, and an injury with no side documented takes S65.199S.
• Fracture sequelae: If the wrist fracture sequela is primary and vascular damage is secondary, the fracture sequela code leads, not S65.192S.

Neighboring codes commonly confused with S65.192S

These are the codes coders reach for in error when S65.192S is the right answer, and vice versa. The difference is usually the vessel, the side, the injury type, or the anatomical level. Each character of the code carries one of those choices, as the breakdown below shows.

Documentation requirements for S65.192S

Sequela encounters carry a higher documentation bar than initial or subsequent encounters. The medical record must support both the sequela condition itself and its causal link to the prior radial artery injury.

• Identification of the sequela condition: The physician must name the specific lasting consequence, such as chronic pain, arterial fibrosis, functional impairment, or sensory deficit. “History of wrist injury” alone is not sufficient.
• Explicit causal link: The note must state that the current condition is a direct result of the prior radial artery injury. A coincidental finding or a new injury does not qualify.
• Anatomical specificity: Documentation should confirm the injury involved the left radial artery at wrist or hand level, not the forearm or elbow.
• “Other specified” justification: If queried by a payer, the coder should be able to show why neither the laceration code nor the unspecified code applies.
• Secondary manifestation code support: The record must also support the sequela manifestation code for pain, scarring or functional loss. That code sequences first on the claim.

Secondary codes required alongside S65.192S

ICD-10-CM sequela coding rules require the sequela manifestation to be coded first. S65.192S is the causal injury code and sequences second, per ICD-10-CM Official Guidelines Section I.C.19.a. Omitting the manifestation code can trigger denials or payer queries.

Common secondary manifestation codes that pair with S65.192S:

The specific manifestation code depends entirely on what the physician documents. Never assume a manifestation code without explicit clinical support in the record.

Payer guidelines and prior authorization

No CMS National Coverage Determination (NCD) is specific to S65.192S. Coverage for treating radial artery injury sequelae follows the procedure performed, not the diagnosis code. The local coverage determination (LCD) and medical necessity rules for that procedure apply.

Key payer considerations for this code:

• Medicare: Sequela codes are accepted when the medical record demonstrates the current treatment is for a consequence of a prior injury, not the injury itself. CMS auditors look for clear physician attribution in the note.
• Commercial payers: Most commercial plans follow CMS sequela coding conventions per ICD-10-CM guidelines. Some plans require the original injury date in supporting documentation for sequela claims, particularly for surgical procedures.
• Prior authorization: Authorization requirements attach to the procedure codes (CPT), not to S65.192S directly. However, the diagnosis must support medical necessity for the procedure being authorized. A sequela claim without a documented functional deficit may face necessity challenges.
• Workers’ compensation: Workers’ comp payers routinely scrutinize the injury-to-sequela chain. Documentation must clearly establish that the original injury was work-related and that S65.192S represents its lasting consequence.

Always verify current LCD policies with your Medicare administrative contractor (MAC), as coverage parameters change with each fiscal year update. Billing platforms such as Pabau connect to the Claim.MD clearinghouse to run eligibility checks before submission. That surfaces payer-specific documentation flags before a claim is built.

Common claim denial reasons and how to prevent them

Claims for S65.192S are denied for a predictable set of reasons, and most are preventable with documentation review before submission. Effective denial management starts with knowing which errors cause rejections for this code family. When a denial does arrive, our guide to denial codes explains how to read and answer the payer’s reason code.

How Pabau catches sequela coding errors before submission

Catching sequela errors on S65.192S usually comes down to two manual checks. Is the manifestation code listed first, and does the note state the causal link to the radial artery injury? On a busy billing day, either check can slip.

Pabau’s claims management software routes submissions through Claim.MD, which checks ICD-10-CM diagnosis combinations for pairing and sequencing issues. A missing manifestation code or a reversed sequence is flagged before the claim leaves the practice.

The platform also surfaces clean claim requirements by payer, and our clean claim guide covers them in depth. Your billing team fixes errors once, before submission, instead of working the same claim through a resubmission.

Reduce claim denials on sequela codes

Pabau’s claims management tools flag sequencing errors and missing manifestation codes before submission, so S65.192S claims reach payers correctly the first time.

Book a demo

Conclusion

S65.192S is easy to look up and easy to get wrong on the claim. The trouble rarely starts with the code itself. It starts when the manifestation code is missing, listed second, or unsupported by the note, and that can trigger denials or payer queries.

The fix sits upstream of billing. Ask the clinician to name the lasting condition and tie it to the prior left radial artery injury in one sentence. Once that sentence is in the note, the sequencing follows from it.

Pre-submission edits then catch what slips through. To see how Pabau’s medical billing workflow checks sequela codes before a claim leaves your practice, book a demo.

Continue your research

Need to understand denial codes on rejected sequela claims? Denial codes in medical billing explains the most common CARC denial reason codes and how to respond to each.

Want to verify eligibility before a sequela encounter visit? Insurance eligibility verification covers how real-time eligibility checks catch payer mismatches before the patient arrives.

Looking for how electronic remittances map to denial patterns? Electronic remittance advice (ERA) explains how 835 transactions surface denial reason codes at the claim line level.

Frequently asked questions