Glossary · Coding

Modifiers XE / XP / XS / XU

XE, XP, XS, and XU are four HCPCS modifiers—collectively called -X{EPSU}—that CMS created as more precise alternatives to modifier 59 to identify distinct, separately reimbursable services that would otherwise be bundled under NCCI Procedure-to-Procedure edits. Each modifier names a specific reason a service is distinct: a separate encounter (XE), a separate practitioner (XP), a separate anatomical structure (XS), or an unusual non-overlapping service (XU).

Verified May 8, 2026 · 8 sources ↓

Drawn from CMSNovitasAAPCHorizonblueModahealth

Definition

Source · Editorial summary grounded in 8 cited references ↓

The Centers for Medicare & Medicaid Services (CMS) introduced the -X{EPSU} modifier set to address chronic overuse and imprecise application of modifier 59. Modifier 59 had become a catch-all for bypassing NCCI Procedure-to-Procedure (PTP) bundling edits, but it carries no built-in specificity about why two services are distinct. The four X-modifiers each correspond to a clinically meaningful rationale. XE indicates the service occurred during a completely separate patient encounter on the same date of service—for example, a post-operative check in the morning and an unrelated injection in the afternoon. XP signals that a different practitioner performed the second service. XS identifies that the service was performed on a different organ or anatomical structure. XU covers services that genuinely do not overlap with the standard components of the primary procedure, even when performed by the same provider at the same encounter on the same structure.

In orthopedic practice, XS is the modifier that appears most frequently. When a surgeon performs procedures on two structurally distinct joints or anatomical sites during the same operative session—such as addressing both the shoulder and the elbow, or treating separate lesions on different tendons—XS signals that the NCCI bundling edit should not apply because the anatomy is genuinely separate. XE is relevant when a patient is seen twice on the same calendar day for unrelated reasons, and XU surfaces in scenarios where an add-on or ancillary service does not share components with the base procedure despite appearing linked by code pairing.

Payer adoption of -X{EPSU} varies. Medicare processes all four modifiers and, since CMS Transmittal 2259 (effective July 1, 2019), will honor them whether appended to the Column 1 or Column 2 code in a bundled pair. However, many commercial payers and Medicaid programs still rely primarily on modifier 59 and may not recognize the X-modifiers at all. Coders must verify payer-specific modifier acceptance before substituting an X-modifier for 59 on non-Medicare claims.

Why it matters

Appending the wrong modifier—or using modifier 59 when an X-modifier more precisely describes the situation—creates audit exposure. Medicare's NCCI Policy Manual and CMS guidance explicitly state that modifier 59 should be used only when none of the -X{EPSU} modifiers accurately fit. RAC and MAC auditors reviewing claims with modifier 59 will look for documentation that the service was truly distinct; if the record would clearly support XS or XE instead, using 59 can be flagged as imprecise or improper. Conversely, omitting any modifier when one is required causes automatic denial of the Column 2 code. In high-volume orthopedic practices—where bilateral procedures, multi-level spine work, and same-day injection plus surgery combinations are routine—a systematic misapplication of these modifiers can result in tens of thousands of dollars in recoupment demands and False Claims Act risk.

Common mistakes

Where people most often go wrong with this concept.

Source · Editorial brief grounded in cited references ↓

  • Using modifier 59 as a default when XS clearly applies—e.g., billing arthroscopy of the knee and arthroscopy of the hip on the same day without switching to XS on the second procedure.
  • Appending XP to two providers of the same specialty group assuming that alone justifies separate payment; payer policy frequently restricts XP to providers of genuinely different specialties or separate practice entities.
  • Using XE to describe two procedures done in the same operative session rather than reserving it for a truly separate patient encounter on the same calendar date.
  • Stacking modifier 59 and an X-modifier on the same claim line; CMS and most payers reject this as redundant and contradictory.
  • Failing to verify whether a commercial or Medicaid payer even recognizes -X{EPSU} modifiers before substituting them for modifier 59 on non-Medicare claims.
  • Appending XS to procedures on contiguous structures within the same organ system—such as adjacent tendons in the same compartment—when those structures do not meet the payer's threshold for 'separate organ/structure.'
  • Appending any of these modifiers to E&M codes; modifier 25 or 24 governs those scenarios, not -X{EPSU}.
  • Placing the modifier only on the Column 1 code and omitting it from Column 2 (or vice versa) without confirming that pre-July 2019 payer logic is still in effect for that carrier.

Related codes

Codes commonly involved when this concept appears in practice.

Frequently asked questions

Source · Generated from the editorial pipeline, verified against 8 cited references ↓

01Can I still use modifier 59 for Medicare claims, or must I switch to XE/XP/XS/XU?
Medicare accepts modifier 59, but CMS expects coders to use the most specific -X{EPSU} modifier when one accurately describes the situation. Using 59 when XS or XE clearly applies is considered imprecise and increases audit risk. Reserve modifier 59 for circumstances that genuinely do not fit any of the four X-modifier definitions.
02Do commercial payers accept XE, XP, XS, and XU?
Not universally. Many commercial payers and Medicaid programs have not adopted -X{EPSU} and still require modifier 59. Survey each payer before using X-modifiers on non-Medicare claims; submitting an unrecognized modifier can result in denial or processing as if no modifier were present.
03Which X-modifier applies when a surgeon operates on the left knee and the right knee in the same session?
Bilateral procedures on paired limbs are typically handled with modifiers LT and RT, or modifier 50, rather than -X{EPSU}. The X-modifiers address distinct service rationale under NCCI PTP edits and are not a substitute for anatomical-side modifiers.
04What documentation must support use of modifier XS in an orthopedic case?
The operative report must clearly identify each procedure and the specific anatomical structure on which it was performed, confirming that the structures are not contiguous parts of the same organ system. The record must also show that the second procedure was not a standard component of the first.
05What happens if I append an X-modifier to an E&M code?
It is inappropriate to use -X{EPSU} modifiers on evaluation and management codes. Use modifier 25 when a significant, separately identifiable E&M service accompanies a procedure on the same date, or modifier 24 for an E&M during a postoperative global period.
06Since CMS Transmittal 2259, does it matter which column code I put the modifier on?
For Medicare, no—since July 1, 2019, the modifier bypasses the NCCI PTP edit whether it appears on the Column 1 or Column 2 code. However, legacy claims processing logic may still apply at some non-Medicare payers, so confirm with each carrier.

Mira AI Scribe

When Mira detects that the operative note or encounter documentation describes services on anatomically distinct structures, separate patient encounters on the same date, or services performed by a different provider, it will flag the appropriate -X{EPSU} modifier for coder review before claim submission. • If the note references two distinct joints or anatomical structures treated in the same session (e.g., shoulder + elbow, or medial compartment + lateral compartment as separate procedures), Mira will suggest modifier XS on the second procedure code. • If the note reflects two separate patient visits on the same calendar date for unrelated reasons, Mira will suggest modifier XE. • If a supervising or co-surgeon of a different specialty performed a distinct component of the encounter, Mira will flag modifier XP for coder verification. • If a service is documented as genuinely non-overlapping with the components of the primary procedure, Mira will suggest modifier XU. Mira does NOT auto-append these modifiers to the claim. It surfaces the suggestion with the supporting documentation snippet so the credentialed coder can confirm clinical and payer-policy criteria are met. For non-Medicare payers, Mira will alert the coder to verify modifier recognition before substituting any X-modifier for modifier 59. Mira will also flag and warn against dual use of modifier 59 and an X-modifier on the same claim line.

See Mira's approach

Related terms

Ready?

Ready to transform your orthopedic practice?

See how orthopedic practices are running documentation, billing, and operations on a single voice-first platform.

Get started for free