ICD code S92.599P – Unspecified lesser toe fracture with malunion

Key Takeaways

S92.599P applies to a lesser toe fracture that healed incorrectly (malunion). It does not cover a fracture still under active treatment or one that failed to heal (nonunion).

The 7th character P is only correct for subsequent encounters, the visits after active treatment is complete. Using A or B for a follow-up visit misstates the episode of care and can lead to denial.

Unspecified laterality (S92.599P) should only be used when the treating physician’s note cannot confirm left or right. S92.591P (right) or S92.592P (left) are always preferred.

Pabau’s claims management software lets practices submit claims, check eligibility and track statuses from one dashboard. The documentation behind each diagnosis code stays with the encounter.

ICD-10 Code S92.599P: Definition and billable status

ICD-10 Code S92.599P is a valid, billable ICD-10-CM diagnosis code for fiscal years 2025 and 2026.

Its official descriptor is: Other fracture of unspecified lesser toe(s), subsequent encounter for fracture with malunion.

Breaking that descriptor apart gives you three distinct claims. “Other fracture” means the injury is not a proximal, medial or distal phalanx fracture. Those fractures have their own subcategories (S92.51 to S92.53). “Unspecified lesser toe(s)” means the documentation does not confirm whether the affected toe is the left or right foot. “Subsequent encounter for fracture with malunion” means the patient is past active treatment and the provider documents that the fracture healed in an abnormal position. All three conditions must be met for S92.599P to be the correct code.

Confirm the code against the CDC/NCHS ICD-10-CM web tool each fiscal year, as the annual tabular release occasionally affects adjacent codes in the S92 family.

Code hierarchy: Where S92.599P sits in ICD-10-CM

S92.599P descends from a clear parent chain. Each level narrows scope from broad injury category to the specific fracture, toe, and episode of care. The CMS ICD-10 codes page publishes the full tabular list annually – the hierarchy below reflects the FY2026 release.

The S92.5 subcategory covers only the lesser toes – the second through fifth toes. Fractures of the great toe fall under S92.4 and require separate codes. Coders working in podiatry or orthopedics should confirm which toe is affected before navigating this hierarchy. Misassigning a great-toe fracture to S92.5 is a straightforward audit finding.

Anatomy of ICD-10 Code S92.599P: What each character means

S92.599P is a seven-character code. Each position carries specific clinical meaning. A coder who understands what each character signals can catch selection errors before the claim goes out.

The 6th character is the laterality position for lesser toe codes. Within S92.599, the final digit before the 7th character is 9, indicating unspecified laterality. S92.591x codes are for the right foot; S92.592x codes are for the left. Coders should always check the physician note for a laterality statement before defaulting to the “9” unspecified position. Payers increasingly audit unspecified codes and may request additional documentation.

What “subsequent encounter for fracture with malunion” means clinically

Malunion means the fractured bone completed the healing process but did so in an abnormal or misaligned position. The bone is no longer broken in the acute sense, because it has united. The union occurred at an incorrect angle, with overlap, or with rotational deformity. This is distinct from nonunion, where healing has failed entirely and no bony bridging has occurred across the fracture gap.

The “subsequent encounter” element refers to the episode of care, not the number of visits. According to the ICD-10-CM Official Guidelines for Coding and Reporting (Section I.C.19), subsequent encounters are visits after the patient has received active treatment. Active treatment includes surgical treatment, emergency department care, and evaluation and continuing treatment by the same or a different provider. Follow-up visits to assess healing, manage complications, or monitor recovery are subsequent encounters. That is where the 7th characters P, K, D and G apply.

• D – routine healing: subsequent encounter, fracture healing as expected
• G – delayed healing: subsequent encounter, healing progressing more slowly than typical but still progressing
• K – nonunion: subsequent encounter, fracture failed to heal (no bony bridging)
• P – malunion: subsequent encounter, fracture healed but in an abnormal position
• S – sequela: late effect of the fracture, such as chronic pain or deformity arising after healing is complete

Selecting P requires the provider to document malunion. Imaging that shows the abnormal position is the strongest support, and payers often ask for it. A note stating the patient “continues to have pain” without a finding of malunion does not support S92.599P. The provider’s documentation must describe abnormal healing, misalignment, angulation, or a similar finding.

Malunion vs nonunion: Choosing between S92.599P and S92.599K

S92.599P and S92.599K are the two most commonly confused codes in the S92.599 family. S92.599P designates a subsequent encounter where the fracture healed incorrectly; S92.599K designates a subsequent encounter where the fracture has not healed at all. The clinical distinction is straightforward, but coders frequently encounter documentation that is ambiguous about which condition the physician is describing.

When a physician’s note says “fracture not healing well” without specifying malunion or nonunion, the coder should query the physician before assigning either code. Querying is always preferable to defaulting to the unspecified healing-complication code, and it protects the practice from payer-initiated audits.

Adjacent and commonly confused codes

The S92.599 code family covers the same fracture type across multiple 7th character options and two laterality variants. Coders should also know the right- and left-specific malunion codes, S92.591P and S92.592P. Using the unspecified S92.599P when laterality is documented is a correctable audit finding. The AAPC ICD-10-CM lookup lists the full S92.59 family with their current FY descriptors.

Documentation requirements for S92.599P

Payers reviewing a claim billed with S92.599P look for three documentation elements. If one is missing, a medical reviewer may deny the claim or request additional records. Verifying each element before submission is faster than appealing a denial after the fact. Use the Check ICD-10 database to confirm the code’s current validity. Then check the chart against the three requirements below.

• Provider statement of malunion: The treating provider must document malunion, abnormal healing, or a fracture healed in an incorrect position. General pain complaints without a healing-status assessment are insufficient.
• Subsequent-encounter status: Documentation that active treatment is complete. The note should reflect a monitoring, management, or follow-up visit rather than active treatment (surgery, emergency care, or ongoing evaluation and treatment).
• Laterality: Either a left/right designation allowing upgrade to S92.591P or S92.592P, or a documented reason laterality cannot be determined. Examples include a bilateral injury or a patient unable to provide history.

Imaging is recommended supporting documentation, and payers often request it. Keep a recent X-ray or CT report that shows the malunion, not only the original injury film.

Practices using Pabau’s claims management software keep documents and photos on the patient record, and the invoice attaches to the claim. When a payer requests medical records, staff pull them from one place instead of rebuilding the file.

Payer and Medicare coverage considerations for S92.599P

S92.599P is a subsequent encounter code, which means it appears on claims for follow-up visits rather than the initial fracture encounter. Medicare and commercial payers apply different medical necessity standards to subsequent encounter visits than to initial treatment, and understanding those standards reduces denials before submission.

For Medicare, subsequent encounter visits billed with a malunion diagnosis code must document that the visit is medically necessary. The physician should be actively managing or evaluating the malunion complication, not simply confirming a healed fracture. A visit where the physician reviews imaging, discusses corrective osteotomy options, or evaluates the patient’s functional limitation from the malunion meets medical necessity. A visit where the physician only notes “malunion present, no change” without a clinical decision component may not.

Local Coverage Determinations (LCDs) issued by Medicare Administrative Contractors (MACs) govern podiatric services in each jurisdiction. LCDs applicable to foot care and fracture management specify covered diagnoses, visit frequencies, and documentation expectations. Practices should verify the applicable MAC LCD for their region, as coverage rules vary and update annually. The guidance here reflects general Medicare principles rather than any specific MAC policy – verify against your MAC’s current LCD before coding.

• Corrective osteotomy: When S92.599P is the primary diagnosis supporting a corrective osteotomy, many commercial payers require prior authorization, so check each payer’s policy. The request should include the imaging report showing the malunion and the physician’s rationale for surgical correction.
• Bundling: Some payers bundle evaluation and management (E/M) codes with minor fracture-related procedures when billed on the same day. Confirm whether the E/M service is separately billable using modifier 25 if a procedure is performed at the malunion follow-up visit.
• Frequency limits: Commercial payers may limit the number of covered subsequent encounter visits for a fracture complication. Documenting functional impairment or a change in the clinical plan at each visit strengthens medical necessity for repeated visits.

Submitting claims for S92.599P through a Claim.MD clearinghouse integration gives practices real-time eligibility checks before the visit and electronic remittance advice after submission. Coverage denials then surface quickly rather than aging in a queue.

Common claim denial reasons for S92.599P and how to avoid them

Denials on S92.599P claims cluster around a small number of correctable errors. Most come down to the wrong 7th character or missing documentation rather than the code itself being inappropriate. Denial management workflows that flag these patterns at the pre-submission stage prevent the majority of rejections.

Coding tips for podiatry and orthopedic practices

Podiatry and orthopedic practices manage lesser toe fractures from the initial encounter through malunion follow-up. A few workflow habits reduce coding errors across that episode of care.

Manage fracture follow-up documentation from one place

Pabau gives podiatry and orthopedic practices a single platform for clinical notes, imaging attachments and claims submission, so your billing team works from one record.

Book a demo

• Lock in laterality at the initial encounter. When the first visit note documents the affected foot as left or right, subsequent encounter codes default naturally to S92.591x or S92.592x. Practices that capture laterality consistently at intake avoid the unspecified trap altogether.
• Align the 7th character to the phase of care, not the calendar. A patient can be in the initial encounter phase for weeks if active treatment continues. The 7th character follows clinical status, not the visit number. An initial encounter code is correct for the third visit if the patient is still receiving active treatment.
• Verify healing status before every malunion or nonunion assignment. Pull the most recent imaging report before coding P or K for a visit. If no imaging has been done since the last visit, the physician may be relying on prior films. Confirm the physician is still describing the same healing status.
• Audit common CPT codes paired with S92.599P. Follow-up E/M codes (99211-99215) and X-ray interpretation codes are typical companions. Many commercial payers require prior authorization for surgical correction codes, so check each payer’s policy. Routine audits of CPT/ICD pairing patterns catch mismatches before they accumulate into a denial trend.

Clean claim submission workflows can help reduce missing or contradictory information on claims before they reach the payer. A medical billing compliance framework also creates an audit trail for responding to payer record requests on malunion claims.

Conclusion

The most common S92.599P errors are preventable: a wrong 7th character selection, a malunion the provider never documented, or a defaulted unspecified laterality code. Each one has a documentation fix that takes seconds at the point of care and saves hours in appeals downstream.

Pabau’s Claim.MD clearinghouse integration turns invoices into electronic CMS-1500 claims, checks eligibility in real time and brings electronic remittance advice back into Pabau. Denial patterns then surface quickly. To see how Pabau supports podiatry and orthopedic billing workflows end to end, book a demo.

Continue your research

Need a broader framework for managing claim rejections? Denial management in healthcare covers the full workflow for tracking, appealing, and preventing common claim denial patterns across specialties.

Submitting electronic claims for the first time? 837 file submission explains the EDI transaction format payers require for electronic claim submission and how clearinghouses process it.

Want to verify patient coverage before the visit? Insurance eligibility verification outlines the process for confirming active coverage and fracture follow-up benefits before the patient arrives.

Frequently Asked Questions