ICD-10 Code S92.526D: Nondisplaced fracture, unspecified toe

Key takeaways

ICD-10 Code S92.526D reports a nondisplaced fracture of the middle phalanx of an unspecified lesser toe, subsequent encounter with routine healing.

The 6th character 6 means laterality was not documented. Right is S92.524D and left is S92.525D.

The 7th character D signals a follow-up visit where healing is on track. Use A for the initial encounter and S for sequela.

S92.526D is billable and has been in ICD-10-CM since the code set took effect on October 1, 2015. It is not a new code.

Practice management software like Pabau keeps laterality and encounter type in the record, so coders rarely need an unspecified code.

ICD-10 Code S92.526D reports a nondisplaced fracture of the middle phalanx of an unspecified lesser toe. The 7th character D marks a follow-up visit where healing is progressing normally.

The word carrying the most weight in that description is unspecified. S92.526D is the code you fall back on when the record never names the injured foot. It is billable, but it also tells the payer the documentation stopped short.

This reference covers the code structure, the 7th character options, the right and left alternatives, documentation requirements, and the errors that send these claims back.

ICD-10 Code S92.526D: Definition and billable status

S92.526D is a billable ICD-10-CM code, valid on any claim type that accepts ICD-10-CM diagnosis codes. The table below gathers the administrative details coders check before submission.

S92.526D sits in ICD-10-CM chapter S00-T88, injury, poisoning and certain other consequences of external causes. Confirm the description each October against the CDC/NCHS ICD-10-CM web tool, which gives year-specific tabular lookups from the official source.

What S92.526D means, character by character

Every character in S92.526D encodes one clinical attribute. A coder who knows the positions can build the code from the note instead of memorizing the family.

The 6th character is the one that trips people up, because it carries two facts at once. In the S92.52 group, 1, 2 and 3 are displaced fractures of the right, left and unspecified toe. Then 4, 5 and 6 repeat that order for nondisplaced fractures. The grid below lays out all six.

There is no 9 in the 6th position of this group, so a code such as S92.529D does not exist. The parent code S92.526 is a header, and it is not billable without a 7th character.

Clinical meaning of each part of the description

Each phrase in the official description maps to something a clinician has to write down. Misreading one phrase selects the wrong code family entirely.

One distinction is worth stating plainly. Nondisplaced does not mean minor, it means the alignment is preserved. The note has to say the fracture is nondisplaced, because an imaging line that reads “fracture seen” leaves displacement status unknown.

The 7th character D: Subsequent encounter with routine healing

Under the ICD-10-CM Official Guidelines for Coding and Reporting, section I.C.19, the 7th character encodes the phase of care. It does not describe severity or site. Every valid option for this code appears below.

D covers most follow-up visits for toe fractures. A patient who returns four weeks after buddy taping for a check and an x-ray showing normal callus formation is a D encounter. Moving to G, K or P happens only on documented evidence, never as a precaution.

Coders sometimes read “subsequent encounter” as “second visit”. The character reflects the phase of care instead of a visit count. A patient can have several initial encounters at different facilities before definitive treatment is settled, and every routine follow-up after that takes D.

S92.526D code hierarchy and parent codes

S92.526D sits at the most granular level of the ICD-10-CM tree for toe fractures. Each level above it adds one piece of clinical specificity.

Parent codes above S92.526D are header codes used for classification and grouping, so they are not billable on their own. Only the full seven-character code carries the specificity that CMS ICD-10-CM requirements expect for reimbursement.

S92.526D encounter variants: A, D, G, K, P and S compared

The base code S92.526 takes six 7th characters for closed fractures. Each one maps to a distinct point in the episode of care.

A patient can move from active fracture management to treatment of a residual condition. At that point the 7th character changes from D to S. The sequela character never applies while the fracture is still healing.

Related ICD-10-CM codes for lesser toe fractures

Most claims that end up on S92.526D belong on a neighboring code instead. The table below shows the full middle phalanx set at routine healing, plus the adjacent phalanx levels.

Cross-reference any of these against the AAPC ICD-10-CM code reference before submission. Reading the right and left codes next to each other is the fastest way to see what a note is missing. Our ICD-10-CM code library covers the neighboring foot and ankle codes in the same detail.

When to use S92.526D instead of a more specific code

Three attributes decide whether S92.526D is right, or whether a sibling code fits better. Each one comes straight from the documentation.

Laterality: Right, left, or unspecified

S92.526D is the unspecified option, so it applies only when the record does not name the side. Within the nondisplaced set, 4 is right, 5 is left, and 6 is unspecified. That gives S92.524D, S92.525D and S92.526D.

Unspecified codes are acceptable when the side is genuinely unknown at the time of coding. They are not a shortcut around a thin note. Payers watch unspecified laterality closely, and some request records before they pay.

Displaced vs nondisplaced: S92.523 vs S92.526

Displacement shares the 6th character with laterality. S92.523 is the displaced fracture of the middle phalanx of an unspecified lesser toe, and S92.526 is the nondisplaced version of the same injury.

Radiology wording decides this. Reports that describe fragment displacement or an angulated fracture map to the displaced code. Reports that say nondisplaced, or fracture without displacement, map to S92.526 plus the correct 7th character.

Phalanx level: Proximal, middle, or distal

S92.526D is specific to the middle phalanx. Proximal phalanx fractures of the lesser toes use the S92.51 group, and distal phalanx fractures use S92.53.

Imaging usually settles the level. When the radiology report does not name the phalanx, the treating clinician’s assessment has to clarify it before the claim goes out.

Coding guidelines and documentation requirements

S92.526D is valid for Medicare, Medicaid and most commercial payers. Before it goes on a claim, the note has to establish the fracture, the encounter type, and the healing status.

The 7th character reports the phase of care rather than the complexity of the visit. A long follow-up with new imaging and a change in the plan still takes D, as long as healing is normal.

Documentation checklist

• Fracture type: Nondisplaced, stated in the note rather than assumed from an imaging line
• Bone specificity: Middle phalanx of a lesser toe, ideally with the toe number
• Laterality: Right or left foot. S92.526D applies only when neither is documented
• Encounter type: Subsequent, meaning active treatment has already been provided
• Healing status: Routine, supported by clinical or radiographic evidence at this visit
• External cause: Code separately from V00-Y99 where the payer or facility requires it

A referral letter is not enough on its own. The treating clinician’s documentation at this encounter has to support every element above. A missing healing status is a provider query rather than a guess.

Present on admission (POA) reporting

S92.526D is exempt from present on admission reporting. Subsequent encounter codes carry a built-in time element, since the fracture by definition happened before this encounter.

CMS therefore leaves them off the POA requirement for inpatient claims. Facility policies can still add their own rules, so check the current CDC exempt list before you drop the indicator.

MS-DRG and outpatient grouping

A single code never determines an MS-DRG. Assignment depends on the principal diagnosis, secondary diagnoses, procedures, and patient demographics taken together.

Where S92.526D is a principal diagnosis on an inpatient claim, it groups within major diagnostic category 8 for musculoskeletal conditions. Weights change with each fiscal year, so work from the active CMS MS-DRG definitions manual.

In practice this code appears mostly on outpatient claims, where MS-DRG does not apply. Those claims group under the ambulatory payment classification system instead.

Commonly used CPT codes with S92.526D

A follow-up visit for a healing toe fracture usually pairs an evaluation and management service with imaging or immobilization. The codes below are the ones that show up most often alongside S92.526D.

Watch the global period when fracture care was billed under 28510. Routine follow-up inside that window is already paid, and an unrelated visit needs modifier 24. Check the pairing against the payer’s local coverage determination first, because rules vary.

Approximate synonyms and index references

The ICD-10-CM alphabetical index maps several clinical phrasings to S92.526D. Coders who search by description rather than code number meet these equivalents.

• Nondisplaced fracture of middle phalanx of lesser toe, subsequent encounter, side not documented
• Non-displaced middle phalanx fracture, lesser toe, follow-up visit
• Closed fracture of middle phalanx of toe, subsequent encounter, routine healing
• Lesser toe middle phalanx fracture, healing normally, laterality unknown
• Fracture of toe (lesser), middle phalanx, nondisplaced, subsequent

These phrasings help with documentation review and audit prep. Where a note uses different wording, map the documented description through the alphabetical index rather than by memory.

Code history and effective dates

S92.526D is not a new code. It arrived with ICD-10-CM when the code set replaced ICD-9-CM in the United States on October 1, 2015. The description has stayed the same through every annual update since.

Code lookup sites often show a heading like “2026 ICD-10-CM diagnosis code”, which refers to the current edition rather than the year the code appeared. Its FY 2026 validity period runs from October 1, 2025 through September 30, 2026.

Common coding errors and how to avoid them

Lesser toe fractures look simple, which is exactly why they generate rework. These are the errors that show up most often on subsequent encounter claims.

• Reading S92.526D as a left-side code. The 6th character 6 means unspecified. Left is S92.525D and right is S92.524D
• Reaching for a code that does not exist. There is no S92.529D and no S92.520D. The 6th character in this group runs 1 to 6 only
• Defaulting to unspecified when the chart has the answer. Check the initial encounter note and the imaging order before you settle for S92.526D
• Carrying the A character into follow-up. Billing S92.526A at a six-week check reads as active treatment, and the payer denies the line
• Switching to G without evidence. Delayed healing needs a documented delay, not a clinician’s caution about a slow recovery
• Using S too early. Sequela applies after the fracture has healed and a residual condition remains, never during the healing phase

The first three errors share a root cause. Laterality gets recorded once at the initial visit, then never repeats in the follow-up notes the coder works from.

How Pabau keeps laterality on the claim

In a split system, laterality lives in the first clinician’s narrative and nowhere else. By the third follow-up the note often says “toe fracture, healing well”, and the coder either queries the provider or codes unspecified.

Practice management software like Pabau keeps the appointment, the treatment note and the claim in one patient record. Pabau’s claims management software carries the diagnosis code from the note onto the claim. The side documented at the initial visit stays visible at every follow-up.

For US practices, Pabau connects to the Claim.MD clearinghouse for electronic submission, eligibility checks and remittance processing. Codes get validated before they reach the payer, which catches format and specificity problems while they are still cheap to fix.

The outcome is fewer follow-up claims going out with unspecified laterality on them. Billing staff spend less time chasing notes, and denial management stops absorbing time that belongs to patients.

Keep fracture claims specific from first visit to final payment

Pabau connects clinical notes, ICD-10-CM coding and claim submission in one platform, with Claim.MD for US electronic claims. See how it fits the way your practice already works.

Book a demo

Conclusion

S92.526D is a correct code and a documentation signal at the same time. It says the fracture was nondisplaced, in the middle phalanx of a lesser toe, at a follow-up visit where healing was on track. It also says nobody wrote down which foot.

So the work sits upstream of the claim. Record laterality at every encounter, state displacement status in words, and name the healing status at each follow-up. The coder then reaches S92.524D or S92.525D, and the unspecified code stays where it belongs, as a last resort.

Book a demo to see how Pabau keeps laterality, encounter type and healing status in the record your coders bill from.

Continue your research

Managing denial patterns on fracture claims? Denial codes in medical billing explains the most common CARC reason codes and how to address them before resubmission.

Want to understand the clearinghouse process end-to-end? 837 file format guide covers how ICD-10-CM diagnosis codes are structured in electronic claim submissions.

New to insurance credentialing? How to get credentialed with insurance companies walks through the payer enrollment process required before submitting claims.

Frequently asked questions