Modifier XE: A Distinct Service Because It Happened at a Separate Encounter
Modifier XE reports a service that is distinct because it occurred during a separate encounter on the same day — a morning procedure and an unplanned evening return. It is one of four X modifiers CMS created in 2015 as more specific replacements for modifier 59.
- Applies to
- NCCI-bundled code pairs performed at genuinely separate sessions same day
- Payment impact
- Bypasses the PTP edit so both services pay
- Audit risk
- Moderate — times in the record must prove two encounters
- Common denial
- CO-97 / CO-236 when missing or when records show one continuous session
What does modifier XE do?
It unbundles an NCCI code pair by asserting the two services happened at separate encounters on the same date — the narrowest and most audit-durable of the distinctness arguments. CMS created the four X modifiers (XE, XS, XP, XU) in 2015 because modifier 59 had become a catch-all that hid why services were distinct. XE names the reason: time.
When do you use it?
When the same-day repeat pairing was driven by a new clinical event at a different session. Realistic example: a pulmonologist performs a diagnostic bronchoscopy at 9 a.m. The patient is recovered and discharged to the floor; at 6 p.m. acute mucus plugging causes lobar collapse, and the patient returns to the suite for a therapeutic aspiration that NCCI bundles with the earlier code. Bill the second procedure with XE — two encounters, two notes, two sets of times. The edit lifts and both pay.
- Confirm the pair hits a PTP edit with modifier indicator 1.
- Confirm two truly separate sessions with documented start/stop times.
- Append XE to the column-2 code only.
When is it wrong or a denial trigger?
- One continuous session. Different steps of one procedure are not separate encounters — that is classic unbundling.
- Distinct site, same session. That fact pattern is XS, not XE. Using the wrong X modifier is survivable but weakens the claim on review.
- Indicator-0 edits. No modifier unbundles those pairs; XE just flags the claim.
- Scheduled "second sessions" engineered for billing. Splitting one planned service into two sittings to defeat an edit is the abuse pattern integrity units screen for.
What are the documentation and payment impacts?
Correct XE use pays the column-2 code at its normal allowable, subject to multiple-procedure rules. Documentation must show two encounters: separate notes, separate times, and ideally the discharge-and-return sequence in nursing records. Payers increasingly run X-modifier claims through pattern analytics — a practice whose XE rate spikes without matching encounter data gets prepay review, so keep usage tied to real events and let the low-frequency honesty be your protection.
Frequently asked questions
A distinct patient session with its own start and stop — the patient left the room, the case ended, and a new clinical event brought them back. Two procedures in one continuous session, even hours apart in the OR, are not separate encounters.
If the distinctness is genuinely "different session, same day," XE is the precise choice and the one CMS prefers. Reserve 59 for scenarios no X modifier describes. Medicare accepts either, but specific modifiers survive review better because they assert a checkable fact.
No. CMS instructs that X modifiers are used instead of 59, never alongside it. Stacking both is a data error that some contractors reject outright.
It clears the bundling edit, but the payer can still review necessity. If the second encounter's documentation lacks its own time, indication, and note, expect a records request and possible denial on review.
Sources & further reading
Reviewed by the ImmediCare Solutions RCM team
Certified billers and coders handling claims across 50+ specialties nationwide. This entry is reviewed against current payer policy and CMS rules. Last review: Jul 5, 2026.
Stop losing revenue to problems like this.
A free billing audit shows exactly where your practice is leaking money — no cost, no commitment.
