ICD code S92.422D – Displaced fracture, distal phalanx, left great toe
Billable Code Specific Code
S92.422D is the billable ICD-10-CM code for displaced fracture of distal phalanx of left great toe, subsequent encounter for fracture with routine healing. Use it at follow-up visits once active treatment has ended and the bone is healing as expected.
A common error is applying A instead of D at follow-up visits, after the patient's active treatment is over. That one-letter slip is a common cause of denials. The note should confirm the left side, displacement, the distal phalanx and normal healing. The checks below walk through each point, plus the CPT codes that travel with this diagnosis.
- Chapter
- S00-T88 Injury, poisoning and certain other consequences of external causes
- Category
- S92 Fracture of foot and toe, except ankle
- Group
- S92.422 Displaced fracture of distal phalanx of left great toe
- Billable
- Yes
- Code also known as
- broken great toe, left hallux fracture, left big toe fracture
Let Pabau's smart automation suggest the right codes, reduce claim denials, and keep your practice compliant—effortlessly.
- AI-powered code suggestions
- Real-time compliance checks
- Faster claims, fewer denials
Automate repetitive tasks and focus on what matters most—your patients.
Reduce coding errors and ensure compliance with the latest regulations.
Clean claims, fewer denials, and faster reimbursements.
Powerful insights and reporting to help your practice thrive.
HIPAA compliant SOC 2 certified GDPR-compliant Trusted by 4,000+ clinics worldwide
Key takeaways
S92.422D covers follow-up visits for a displaced fracture of the left great toe’s distal phalanx that is healing as expected.
The seventh character D means active treatment has ended, so the visit count never decides it.
A doctor who takes over active treatment still reports A, even at their first visit.
Using A instead of D at a follow-up visit is a common cause of denials.
Pabau’s claims management software scrubs every claim for missing or invalid details before submission.
What ICD-10 code S92.422D covers
ICD-10 code S92.422D is a billable, fully specified ICD-10-CM code. It reports a follow-up visit for a displaced fracture at the tip of the left big toe.
Its official descriptor reads: Displaced fracture of distal phalanx of left great toe, subsequent encounter for fracture with routine healing.
The parent code S92.422 can’t go on a claim by itself. Every fracture code in category S92 needs a seventh character to be billable. Check the CDC/NCHS ICD-10-CM web tool to confirm the code is active for the fiscal year of the date of service.
The distal phalanx is the tip of the toe
The distal phalanx is the end bone of the great toe, or hallux. It sits at the very tip, under the nail bed. Behind it, the longer proximal phalanx joins the toe to the metatarsal head.
- Great toe (hallux): The first toe has two bones, the proximal and distal phalanx, and no middle phalanx
- Distal phalanx: The small end bone at the tip, often broken by a crush injury, a stub or a direct blow
- Proximal phalanx: A fracture here falls under a different S92.4 subcategory, not S92.422
- Left vs. right: The sixth character holds laterality, with 2 for left and 1 for right
The exact site matters at audit. A note that says “great toe fracture” without naming the phalanx is ambiguous, so payers often ask for more records.
Seventh character D follows treatment, not visit count
The seventh character D marks a subsequent encounter for a fracture that is healing as expected. There is no delayed healing, non-union or malunion. Under Section I.C.19.a of the ICD-10-CM Official Guidelines, treatment status at the visit picks the character. Where the visit falls in the sequence does not.
That rule catches plenty of coders out. A third visit can still take A if the provider is managing the fracture, for example with a manipulation or a new cast. The switch to D comes when active treatment ends and the visits turn to monitoring.
All seven characters S92.422 can take
When S92.422D fits the visit
S92.422D fits any visit where the provider monitors this fracture after active treatment is over. Routine healing means the bone is knitting normally, with none of the problems that G, K or P describe.
Visits that usually support D include:
- Cast or splint removal
- A wound or nail-bed check after a crush injury
- Progress X-rays that confirm callus formation
- A final review before discharge to physical therapy
A new manipulation, a corrective splint or a change of plan may move the visit back to A, but only if active treatment has restarted.
A or D? Four questions for the note
Under the guidelines, active treatment means care aimed at the fracture itself. A subsequent encounter starts once that care is complete. Work through the note in this order:
- Confirm the treatment phase: Did today’s visit treat the fracture, through reduction, casting or fixation, or only monitor it?
- Read the visit purpose: “Follow-up for healing fracture” supports D, while “applied short leg cast” supports A
- Check the imaging read: “Healing as expected” fits D, but “fracture gap widening” may point to G
- Look at what the provider did: With no active intervention, the encounter is almost always subsequent
Visit number never sets the seventh character on its own. The ICD-10-CM Official Guidelines base it on active treatment, even when a new or different provider sees the patient. So a specialist who takes over active management after ER care still reports A.
D applies only once the visits are monitoring only, such as cast removal, a healing X-ray or aftercare. The diagram below maps both decisions, treatment status first and healing second.

A worked example, from ER to healing review
Here’s how one fracture moves through the codes. A patient drops a weight on her left big toe. The ER X-ray shows a displaced distal phalanx fracture, and the ER reports S92.422A.
- Day 3, a podiatrist takes over: She reduces and splints the fracture. That is active treatment, so the code stays S92.422A.
- Week 3, splint check: The X-ray shows callus forming, and no new treatment is given. This visit takes S92.422D.
- Week 6, healing review: The X-ray shows little progress since week 3. The podiatrist documents delayed healing, so the code becomes S92.422G.
Each visit is coded on what happened that day. As a result, the same fracture carries three different codes in six weeks.
Codes that get mistaken for S92.422D
Several neighboring codes get confused with S92.422D. The table shows each one and what sets it apart.
One rule works in the coder’s favor here. Under Section I.C.19.c of the guidelines, a fracture not described as displaced or nondisplaced is coded as displaced.
What the note must show to support D
Each part of the code needs a matching line in the note. If a claim can’t be traced back to the note for each element below, expect a denial.
- Laterality (left): The note must say “left great toe” or similar. “Great toe” alone doesn’t support this code
- Displacement: The record must not call the fracture nondisplaced, which would make it S92.425D. If it’s silent, the guidelines default to displaced
- Anatomical site (distal phalanx): “Toe fracture” or “phalanx fracture” isn’t enough, so the note must name the distal phalanx
- Encounter type (subsequent): The note should show monitoring, not treatment. Phrases like “healing well” or “cast removed” support D
- Healing status (routine): The note must not mention delayed healing, non-union or malunion, since each one changes the seventh character
Pro Tip
Before you close a follow-up note for a displaced great toe fracture, run a four-point check. Confirm the left side, displacement wording that matches the code, the distal phalanx and normal healing. Missing any one turns a billable S92.422D claim into an audit finding.
CPT codes that travel with S92.422D
A follow-up fracture visit carries a diagnosis code and a procedure code. The CPT codes below often appear alongside S92.422D.
Check NCCI bundling edits before you pair any procedure with an E/M code at the same visit.
How a follow-up claim moves to payment
Most S92.422D problems start well before the payer sees the claim. Here’s the usual path for a follow-up visit, with the trip point at each step.
- The provider signs the note: It needs the side, the bone, the displacement and the healing status. A vague note stalls each step after it.
- The coder assigns the codes: S92.422D goes on with the E/M or procedure code. This is where A and D get mixed up.
- The billing system scrubs the claim: Edits catch missing fields and incomplete codes like a bare S92.422. Fixes here are quick and free.
- The clearinghouse checks the format: It rejects claims with invalid codes or missing data before they reach the payer.
- The payer adjudicates: It applies coverage rules, bundling edits and any open global period.
- Payment or a denial comes back: The remittance shows what was paid. A denial carries a reason code that tells you what to fix.
Five mistakes that get S92.422D denied
Seventh-character slips and thin notes are a common cause of denials on S92.422 fracture claims. The table pairs each mistake with its fix.
A denial management workflow that tracks rejections by seventh character shows where errors start. You’ll see whether the note or the code choice is at fault, which tells you who needs training.
Before you submit: A six-point checklist
Run this check on every S92.422D claim before it leaves the practice.
- The seventh character matches what happened today: A for treatment, D for monitoring
- The code has all seven characters, so S92.422D rather than S92.422
- The note names the left great toe and the distal phalanx
- The record doesn’t call the fracture nondisplaced
- Healing is documented as routine, with no delay, non-union or malunion
- You’ve checked whether the visit falls inside a 28490 or 28495 global period
Medicare wants a reason for every visit
Medicare covers follow-up fracture care when each visit is medically necessary. No national coverage determination caps the number of follow-up visits for toe fractures.
Instead, coverage depends on the Local Coverage Determination (LCD) for your MAC jurisdiction and on the specialty. Podiatry LCDs usually expect the note to give a clinical reason for each visit.
A visit coded S92.422D with only “routine check” as its rationale may be denied under LCD review. So capture the decision made at each visit, such as cast removal, an imaging read, a gait check or discharge planning.
- Medicare Part B: Covers office follow-up for displaced toe fractures when the note supports medical necessity
- MAC jurisdiction: LCDs vary by region, so check the one for podiatric care in your MAC
- Modifiers: Modifier 25 may apply when a significant, separately identifiable E&M service is billed with a procedure
- Global surgical period: CPT 28490 and 28495 carry a 90-day global period. Related E&M visits in that window are bundled unless a modifier applies
Getting each claim right the first time is the heart of a clean claim, and it shortens payment delays. Before each fiscal year, check the AAPC ICD-10-CM code reference for changes to the S92.422 family.
Recheck S92.422D every October 1
ICD-10 code S92.422D has stayed valid and billable across recent fiscal years, with no descriptor changes.
Check its status each year in the Check ICD-10 database, which mirrors the CMS and NCHS release files. Our ICD-10-CM code library lists the neighboring S92 codes too.
Cross-check against the official CMS annual update files as well. Payers tie fee schedules to one fiscal year’s code list. A claim built from last year’s file can be rejected once the date of service falls in the new year.
Our guide to medical billing basics shows where that yearly update fits in the claim cycle.
Pro Tip
Set a reminder for October 1, when each new ICD-10-CM fiscal year takes effect. Pull the updated tabular list from the CDC tool and search for S92.422D. Confirm it’s still active and unchanged before you process October claims.
How Pabau keeps fracture follow-up claims clean
Many podiatry and orthopedic practices still check fracture claims by hand. A biller reads the note, keys in the codes and hopes the claim is complete before the clearinghouse sees it.
Pabau, the practice management platform we build, opens each claim pre-filled from the invoice. Its error-catching claims management then scrubs every claim for missing or invalid details before it leaves Pabau.
US practices submit CMS-1500 claims through Claim.MD, which also runs insurance eligibility checks before the visit. A rejected claim is flagged “Needs action” with its reason, so your team can correct it and resubmit. The seventh-character call stays with your coder, while the scrub checks the rest of the claim.

Send fracture follow-up claims out clean
Pabau’s claims management scrubs every claim for missing or invalid details before submission. US practices submit CMS-1500 claims and check eligibility through Claim.MD.

Conclusion
S92.422D comes down to one question about each visit: was the fracture treated or watched? Once active treatment ends and the toe is healing on schedule, D is the right call.
The effort sits in the note. A few words on side, displacement and healing take seconds to write. A denied claim, by contrast, costs a resubmission and weeks of waiting. Build those prompts into your follow-up template, and run the checklist before each claim goes out.
Book a demo to see how Pabau scrubs fracture follow-up claims before they reach the payer.
Continue your research
Need to understand how claims move through the clearinghouse? Medical claims clearinghouse overview explains how claims travel from your billing system to payers and where rejections occur.
Dealing with repeated fracture code denials? Denial codes in medical billing breaks down the most common CARC codes and how to respond to each.
Want to verify eligibility before the follow-up visit? Insurance eligibility verification covers real-time 270/271 checks and how to integrate them into your workflow.
Billing Medicare for follow-up fracture care? Medicare billing walks through how Part B claims are prepared and paid.
Frequently asked questions
What is ICD-10 code S92.422D?
It’s the billable ICD-10-CM code for a follow-up visit on a displaced distal phalanx fracture of the left great toe with routine healing.
Do you need an external cause code with S92.422D?
Report one when your payer or state requires external cause data. It takes the same seventh character as the injury code, so D at a follow-up visit. Activity (Y93) codes are reported only once, at the initial encounter, and place (Y92) codes usually are too.
What if the note doesn’t say displaced or open?
Code it as displaced and closed, the two defaults in guideline Section I.C.19.c. An undescribed fracture of this bone still lands on S92.422, with treatment status picking the seventh character.
Should you use an aftercare Z code instead of S92.422D?
No. The guidelines bar aftercare Z codes for traumatic fractures. Report S92.422D itself, since the D already tells the payer this is follow-up care.
How is S92.422S sequenced?
List the residual condition first, such as chronic pain or stiffness, then S92.422S. The S goes only on the injury code and names the fracture that caused the problem.
Is S92.422D valid for FY2026 and FY2027?
S92.422D is valid and billable for FY2025 and FY2026, with no descriptor changes. Confirm FY2027 in the official tabular list, which took effect October 1, 2026, before you bill visits on or after that date.



