The bottom lineNonoperative fracture care is a 90 day package worth several visits. Code it once, correctly, with the modifier 57 logic.

Even the experts are guessing

Fracture care coding is genuinely hard, and I have watched excellent orthopaedic surgeons get it wrong, not from carelessness, but because the rules are unintuitive. The hardest question is deceptively simple: for this fracture, does the fracture care code or a straightforward E/M visit pay more? Even experienced surgeons often cannot tell at a glance. That uncertainty is exactly why I built the fracture coding calculator, and why this is the one tool I would bookmark.

The 15-second version

Managing a fracture nonoperatively is skilled longitudinal care, the reduction, the follow-up, the serial imaging, the judgment calls about healing. The coding should reflect all of it. Yet nonoperative fracture care is one of the areas of orthopaedic coding where the rules are most commonly misunderstood, and where both undercoding and inadvertent unbundling errors are most common. The key concept is the fracture care package.

What the Fracture Care Package Includes

When you code a fracture care CPT code (for example, 25600 for a distal radius fracture treated without manipulation, or 25605 for one treated with manipulation), that code covers a global package that includes:

This is why coding a separate E/M on the same day as a fracture care code is typically not appropriate, the fracture care code already includes the evaluation component. The evaluation of the fracture and the decision to treat nonoperatively are built into the fracture care package.

The Exception: Separately Identifiable Service on the Day of Fracture Care

If you address a problem that is unrelated to the fracture on the same day, Modifier 25 can be applied to the E/M. For example, a patient presents with a wrist fracture and also has new chest pain you evaluate and address. The chest pain evaluation is unrelated to the fracture and can be coded separately. The documentation must clearly support the distinct service.

Treatment vs. No Treatment: A Key Distinction

There is an important coding distinction between:

This distinction matters in settings like emergency consultations, urgent care follow-ups, or cases where you evaluate a fracture and direct the patient to a specialist for ongoing care.

Common Fracture Care Codes and Their wRVU Values

CPTDescriptionwRVUs
25600Distal radius/ulna fracture, no manipulation2.71
25605Distal radius/ulna fracture, with manipulation6.09
27750Tibia fracture, no manipulation3.29
27752Tibia fracture, with manipulation6.11
28470Metatarsal fracture, no manipulation1.98
27786Fibula fracture, no manipulation2.94
The interactive fracture coding tool
PhysicianCodingGuide.com includes a Nonoperative Fracture Coding Calculator covering 52 fracture codes with a 4-step workflow. Use it to find the right code for any nonoperative fracture and see the current wRVU value.

Casting and Strapping: Separate vs. Bundled

Initial cast application is included in fracture care codes that involve manipulation. For fractures treated without manipulation (where you apply a splint or cast at the initial visit), there is a nuance: if no fracture care code is being coded, cast and strapping codes (29000-29590 series) can be coded separately. If a fracture care code is coded, the initial cast application is generally considered bundled.

Subsequent cast changes during the global period are bundled into the fracture care package. If a cast change requires significant additional clinical evaluation, Modifier 25 rules apply (see the Modifier 25 guide ).

Can You Code an E/M Visit With Fracture Care? Yes, With the Right Modifier

A common and costly misconception is that fracture care never carries a separate E/M. It can. The American Academy of Orthopaedic Surgeons has made this explicit: you may code a separate E/M visit on the same day as a fracture-care procedure when that visit is the encounter where the decision for definitive treatment was made, and the documentation shows it. The mechanism is the same global-period logic that governs all surgery.

Here is the part that surprises people. Most fracture-care codes, with or without manipulation, carry a 90-day global period, which classifies them as major procedures. That means the correct modifier on the decision visit is usually Modifier 57 (decision for surgery), not Modifier 25. Modifier 25 is for the minor procedures with 0 or 10-day globals. So when you evaluate a new fracture, decide on and render definitive treatment that day, you can code the E/M with Modifier 57 and the fracture-care code together. Without the modifier, the E/M is denied as part of the global package.

Treating to Completion: The Package Versus Per-Visit Choice

You also have a genuine choice in how to code fracture care, and it is a decision you make and document, not an automatic rule. One option is the definitive fracture-care code, which behaves like a surgical package: one code covers the restorative treatment and the routine follow-up across the 90-day global. The other option is to code an E/M at each visit plus the cast or splint application, rather than the global package. Both are legitimate; what matters is that your documentation matches the choice.

The deciding distinction is definitive, restorative management versus interim stabilization. If you have taken responsibility for treating the fracture to completion and are managing it as a package, payers expect the single definitive code, not a series of separately coded visits within the same period. If instead you are providing temporary stabilization and referring on, or the clinical picture genuinely calls for ongoing evaluation rather than packaged care, the E/M-plus-application approach fits. The one thing you cannot do is double-dip: code the global package and then also itemize separate E/M visits for routine fracture follow-up within that global period. Note also that an unrelated problem during the global period is separately codable with Modifier 24, and that X-rays are separately reportable and not part of the fracture package.

Sources and Further Reading for This Chapter

Put it to workOpen the Fracture Coding Calculator
PreviousOrthopaedic Surgery Coding