ICD-10 Code S59.009D: Physeal fracture lower end of radius

Key Takeaways

S59.009D is a billable ICD-10-CM code for an unspecified physeal fracture of the lower end of the radius, unspecified arm, at a subsequent encounter where the fracture is healing routinely

The parent code S59.009 (without a 7th character) is NOT billable; a 7th character is required to make any S59.009 code valid for HIPAA-covered transactions

Using the 7th character D when delayed healing (G), nonunion (K), or malunion (P) is documented constitutes a coding error with compliance implications

Pabau’s claims management software helps orthopedic and physical therapy practices track encounter type, manage fracture follow-up coding, and reduce claim errors

ICD-10 Code S59.009D is a billable ICD-10-CM diagnosis code valid for fiscal year 2026 HIPAA-covered electronic transactions. The full official description is: Unspecified physeal fracture of lower end of radius, unspecified arm, subsequent encounter for fracture with routine healing.

Three elements define this code. First, “physeal” means the fracture involves the growth plate (physis), not the bone shaft. Second, “unspecified arm” signals that laterality is not documented. Third, “subsequent encounter for fracture with routine healing” is the meaning of the 7th character D, confirming the patient is in active treatment and healing is progressing normally.

S59.009D code details at a glance

Use this quick-reference table to confirm the code’s core attributes before submission.

Understanding the 7th character D in ICD-10 fracture codes

The CMS ICD-10-CM Official Guidelines for Coding and Reporting require a 7th character for all fracture codes in the S59 series. Without it, the code is not billable and HIPAA-covered transactions will reject. The 7th character describes encounter type and healing status, not the fracture itself.

The 7th character D specifically designates a subsequent encounter for fracture with routine healing. A subsequent encounter is any visit after the patient has received active treatment and the provider is managing recovery. Routine healing means the fracture is progressing normally with no complication documented.

All 7th character variants for S59.009

Each 7th character maps to a distinct clinical scenario. Selecting the wrong suffix is a coding error that can trigger audits or claim denials.

Clinical background: Physeal fractures of the distal radius

The physis, or growth plate, is a cartilaginous zone at the end of long bones in children and adolescents. Because cartilage is mechanically weaker than bone during growth periods, the physis is the most vulnerable point in a developing skeleton. A fall onto an outstretched hand (FOOSH mechanism) concentrates force at the distal radial physis, making it the most commonly fractured growth plate site in pediatric patients. Practices managing pediatric orthopedic or sports injury cases, including those using physical therapy practice management platforms, encounter these codes regularly during follow-up care.

Salter-Harris classification and ICD-10 coding

The Salter-Harris system classifies physeal fractures by the relationship of the fracture line to the physis, epiphysis, and metaphysis. This classification directly affects ICD-10 code selection. S59.009D applies only when the Salter-Harris type is not documented in the chart.

If a radiologist or orthopedic surgeon documents a specific Salter-Harris type in the record, coders must use the corresponding typed code. Using S59.009D (unspecified) when a specific type is documented is a coding error. Review pediatric ICD-10 code references for additional context on age-specific diagnostic coding nuances.

ICD-10-CM code hierarchy for S59.009D

Understanding where S59.009D sits in the ICD-10-CM hierarchy helps coders verify correct code selection and navigate parent codes during audits. The full hierarchy is:

For ICD-10 coding in elbow and forearm injuries, verify each code against the AAPC Codify ICD-10-CM lookup to confirm current validity before submission.

Coding guidelines and documentation requirements for S59.009D

Per ICD-10-CM official guidelines, accurate documentation must support every element of S59.009D before submission. Practices should review their claims management software to ensure encounter type is captured at the point of care, not reconstructed from memory at billing time. Good physiotherapy clinic compliance requirements frameworks apply equally here: documentation must be contemporaneous.

• Encounter type: The chart note must explicitly describe this as a follow-up or subsequent visit, not a new evaluation or the first time active treatment was administered.
• Healing status: The provider must document that healing is progressing normally. Radiology reports or clinical exam findings confirming callus formation or expected alignment are ideal.
• Laterality: S59.009D uses “unspecified arm.” If the medical record documents right or left arm, use a laterality-specific code instead (S59.001D for right arm, S59.002D for left arm). Unspecified laterality is only appropriate when the chart genuinely does not specify.
• Salter-Harris type: If the fracture type is classified anywhere in the record, the unspecified S59.009D series does not apply. A specific Salter-Harris type code is required.
• Transition from A to D: The switch from S59.009A (initial encounter) to S59.009D (subsequent encounter) occurs when the provider is no longer administering active treatment and the patient is in the monitoring phase. This is a clinical judgment, not a time-based rule.

Common coding errors with ICD-10 Code S59.009D

Most coding errors with this code family fall into three categories. Competitors listing S59.009 codes rarely address the compliance consequences of each mistake, so this section covers the practical risk attached to each one. Good patient compliance in fracture management depends on accurate coding to ensure appropriate follow-up care is reimbursed correctly.

• Submitting S59.009 without a 7th character. This is the most common mistake. S59.009 alone is not a billable code. Claims submitted with S59.009 will reject for HIPAA non-compliance. Always append the appropriate 7th character before submission.
• Using D when G, K, or P is documented. If the chart note or imaging report references delayed healing, nonunion, or malunion, S59.009D is the wrong code. Submitting D in these circumstances misrepresents the clinical status and constitutes a coding error with compliance implications. Use G (delayed healing), K (nonunion), or P (malunion) as appropriate.
• Using A on subsequent visits. Coders sometimes continue billing S59.009A through multiple follow-up visits because it was used on the first encounter. The 7th character A applies only while the patient is receiving active treatment. As soon as the provider shifts to monitoring, D (or G/K/P if complications develop) should replace A.
• Defaulting to “unspecified arm” when laterality is documented. If the chart says “right wrist fracture,” using S59.009D instead of S59.001D is a specificity error. Payers can flag or deny claims where documented information was available but not coded.
• Using S59.009D when a specific Salter-Harris type is documented. An orthopedic note stating “Salter-Harris Type II fracture” requires a specific code from the S59.02x series, not the unspecified S59.009 series. Unspecified physeal fracture codes are last-resort selections when classification is genuinely absent from the record.

Practices with high pediatric orthopedic or sports medicine volume benefit from a dedicated coding protocol for growth plate fractures. Using structured practice management software that flags encounter-type fields at billing time can reduce these errors before claims are submitted.

Related ICD-10 codes in the S59 category

S59.009D sits within a larger family of physeal fracture codes at the distal radius. Coders working in orthopedics or sports medicine software practices will encounter these sibling codes frequently alongside S59.009D.

Verify current code validity using the ICD List free ICD-10-CM lookup tool, which mirrors official CMS and NCHS data for the current fiscal year. Practices managing pediatric ICD-10 code references alongside conditions such as other pediatric ICD-10 code references should maintain separate coding protocols for each clinical area.

Reduce fracture coding errors with Pabau

Pabau's claims management tools help orthopedic and physical therapy practices capture encounter type at the point of care, flag incomplete documentation before billing, and track follow-up coding across the full S59.009 series. See how it fits your workflow.

Book a demo

Conclusion

Physeal fracture coding at the distal radius fails most often not because of diagnostic confusion, but because the 7th character is missing or misassigned. S59.009D is billable and HIPAA-valid for 2026, but only when the chart supports every element: a confirmed subsequent encounter, documented routine healing, genuinely unspecified laterality, and the absence of a documented Salter-Harris classification.

For practices managing pediatric fracture follow-up at volume, clinical documentation tools that structure encounter type and healing status capture at the point of care remove the guesswork from 7th character selection. Teams looking to tighten their ICD-10 coding accuracy alongside broader ICD-10 coding for related conditions can use Pabau’s claims management workflows to reduce denials across the board.

Continue your research

Need to understand how practice management tools support coding accuracy? Practice management software features covers what billing and documentation tools to look for when choosing a platform for orthopedic or physical therapy practices.

Managing compliance requirements for physical therapy or physiotherapy clinics? Physical therapy EMR software outlines how Pabau supports documentation workflows for PT practices dealing with follow-up fracture care.

Looking for a claims management overview specific to your specialty? Claims management software explains how Pabau handles billing workflows from encounter capture through submission.

Frequently Asked Questions