Modifier XE- Separate encounter

Identifies a service that is distinct because it was performed during a separate encounter on the same date and may qualify for separate reporting under Medicare NCCI rules.

Home > All Modifier Categories > HCPCS Modifiers > Modifier XE

What Is Modifier XE?

Modifier XE is a HCPCS Level II modifier defined by CMS as “Separate Encounter.” It identifies a service that is distinct because it occurred during a separate encounter.

XE is one of the four X{EPSU} modifiers used to provide greater specificity in circumstances where Modifier 59 has traditionally been reported:

XE: Separate encounter.

XP: Separate practitioner.

XS: Separate organ or structure.

XU: Unusual non-overlapping service.

CMS continues to recognize these modifiers in its April 2026 guidance. When one of the X{EPSU} modifiers accurately explains why services are distinct, it provides more specific information than Modifier 59.

When to Use Modifier XE

Separate Encounter: Two services occur during genuinely separate encounters on the same date of service.

Different Sessions: The patient returns for another medically necessary procedure or service later in the day, and the encounters are clinically distinct.

NCCI Edit Allows a Modifier: The applicable NCCI PTP edit has a Correct Coding Modifier Indicator that permits an NCCI-associated modifier under qualifying circumstances.

XE Best Describes the Distinction: The reason the services qualify for separate reporting is the separate encounter rather than a different practitioner, organ, structure, or unusual non-overlapping service.

Documentation Supports Both Encounters: The medical record clearly establishes the separate timing and circumstances of each encounter.

CMS identifies separate patient encounters as one of the circumstances in which NCCI PTP-associated modifier reporting may be appropriate.

When NOT to Use Modifier XE

Same Encounter: Do not use XE merely because two procedures were performed at different times during the same encounter.

Separate Practitioner: Modifier XP is more specific when the distinction is based on a different practitioner.

Separate Structure: Modifier XS is more specific when the services occurred on separate organs or structures.

Unusual Non-Overlapping Service: Modifier XU is more appropriate when the service is distinct because it does not overlap the usual components of the primary service.

Different Diagnosis Alone: Different diagnoses do not independently establish that two services occurred during separate encounters.

CCMI of 0: An NCCI PTP edit with a Correct Coding Modifier Indicator of 0 cannot be bypassed using XE or another NCCI PTP-associated modifier.

To Obtain Separate Payment: Do not append XE solely because Medicare bundled or denied a service. The documentation must support a legitimate separate encounter.

Billing Example

A patient receives a medically necessary procedure during a morning encounter.

Later that day, the patient's clinical circumstances require the patient to return for a separate encounter during which another medically necessary procedure is performed.

An NCCI PTP edit normally prevents the two procedure codes from being reported together.

If the applicable edit permits modifier use and the documentation demonstrates that the second service occurred during a genuinely separate encounter, the appropriate procedure may be reported with Modifier XE.

The separate encounter—not merely a different diagnosis or the passage of time—is what supports XE.

Documentation Requirements

Separate Encounters: Clearly document that the services occurred during distinct encounters.

Timing: Record the time or sequence of the encounters when relevant to demonstrating separation.

Reason for Each Encounter: Explain why each encounter occurred and the clinical circumstances requiring the services.

Procedures Performed: Identify the procedure or service furnished during each encounter.

Medical Necessity: Support the medical necessity of each separately reported service.

Distinct Documentation: The record should provide enough information for a reviewer to understand why the encounters were separate rather than components of one continuous episode of care.

CMS requires documentation to support the use of NCCI PTP-associated modifiers.

Billing and Claim Considerations

Modifier XE is particularly important when services are subject to Medicare NCCI Procedure-to-Procedure edits.

NCCI PTP edits identify code combinations that generally should not be reported together because the services overlap or one service is considered integral to another.

CMS assigns a Correct Coding Modifier Indicator to applicable edits.

A CCMI of 0 means the edit cannot be bypassed using an NCCI PTP-associated modifier.

A CCMI of 1 means the code combination may qualify for separate reporting under limited circumstances when an appropriate modifier is supported.

A CCMI of 1 does not automatically justify XE. The separate encounter must actually have occurred and be supported by the medical record.

Modifier XE and NCCI Edits

CMS continues to recognize XE as an NCCI PTP-associated modifier in 2026.

The modifier provides Medicare with a specific reason why services normally subject to an edit may be distinct: they occurred during separate patient encounters.

However, providers should not automatically append XE whenever procedures occur on the same date.

CMS notes that NCCI-associated modifiers should only be used when the circumstances satisfy the modifier requirements. The presence of an edit does not itself establish that separate reporting is appropriate.

The documentation should clearly demonstrate where one encounter ended and the separate encounter began.

Modifier XE vs. Modifier 59

Modifier XE: Identifies services that are distinct because they occurred during separate encounters.

Modifier 59: Identifies a distinct procedural service when another more specific modifier does not adequately describe the circumstances.

When a separate encounter is specifically what makes the service distinct, XE provides more precise information.

CMS's current guidance emphasizes proper use of the more specific X{EPSU} modifiers when they accurately describe the circumstances.

Modifier XE vs. Modifier XP

Modifier XE: The service is distinct because it occurred during a separate encounter.

Modifier XP: The service is distinct because it was performed by a different practitioner.

XE focuses on when the service occurred.

XP focuses on who performed the service.

A different practitioner does not automatically mean there was a separate encounter, so the modifier should reflect the actual reason the services qualify as distinct.

Modifier XE vs. Modifier XS

Modifier XE: Identifies a service performed during a separate encounter.

Modifier XS: Identifies a service performed on a separate organ or structure.

XE is based on separate encounters, while XS is based on separate anatomy.

If two procedures are performed during the same encounter but on qualifying separate organs or structures, XS may be more appropriate than XE.

Modifier XE vs. Modifier XU

Modifier XE: Identifies a service that is distinct because it occurred during a separate encounter.

Modifier XU: Identifies an unusual service that is distinct because it does not overlap the usual components of the primary service.

XE focuses on separation between encounters.

XU focuses on the non-overlapping nature of the services themselves.

The modifier should describe the specific circumstance that supports separate reporting.

Modifier 59 and X{EPSU} Billing Guide

Modifier XE is part of the X{EPSU} modifier family used to explain more precisely why procedural services qualify as distinct.

Choosing between Modifier 59, XE, XP, XS, and XU depends on whether the distinction involves a separate encounter, practitioner, structure, or unusual non-overlapping service. CMS's April 2026 guidance addresses proper use of all five modifiers.

For a complete comparison, see our Modifier 59 vs. XE, XP, XS, and XU Guide.

Common Billing Mistakes

Using XE for the Same Encounter: Multiple services performed during one continuous encounter do not become separate merely because they occurred at different times.

Using XE Automatically With NCCI Edits: The existence of a PTP edit does not independently justify the modifier.

Confusing XE With XP: A different practitioner is represented by XP when that is the reason the service is distinct.

Confusing XE With XS: Separate anatomical structures are represented by XS when that is the basis for separate reporting.

Using Different Diagnoses as Justification: Different diagnoses alone do not establish separate encounters.

Insufficient Documentation: The medical record does not clearly establish that the patient had distinct encounters.

Common Denial Reasons

Separate Encounter Not Supported: Documentation suggests the services were performed during the same encounter.

NCCI Edit Cannot Be Bypassed: The applicable code pair has a CCMI of 0.

Incorrect X{EPSU} Modifier: Another modifier more accurately describes why the services are distinct.

Service Considered Integral: Medicare determines that the second service remains part of the primary procedure.

Insufficient Documentation: Records do not adequately establish the timing, circumstances, or medical necessity of the separate encounter.

Medical Necessity Not Supported: The separately reported procedure lacks sufficient clinical support.

Frequently Asked Questions

Does a different time on the same day automatically support Modifier XE?
No. XE requires a genuinely separate encounter. A time difference alone does not necessarily establish that one encounter ended and another distinct encounter occurred.

Can Modifier XE bypass any NCCI edit?
No. XE may only be used when the applicable edit permits an NCCI-associated modifier and the documentation supports a qualifying separate encounter. Edits with a CCMI of 0 cannot be bypassed with XE.