Skip to content
Evaluation and management

Modifier XE

Separate encounter — a service that is distinct because it occurred during a separate encounter

Modifier XE states that two services were distinct because they took place at separate encounters on the same day. It is the cleanest of the X modifiers to support, because the separation is a matter of documented time rather than clinical judgement.

Use it when

  • A patient returns later the same day for a genuinely separate encounter
  • A morning procedure and an unrelated afternoon procedure
  • Services separated by the patient leaving and returning

Do not use it when

  • Services performed in one continuous session, however long
  • A break within a single encounter — a pause is not a separate encounter
  • The distinction is anatomic rather than temporal — use XS

A worked example

A patient has a procedure performed in the morning, leaves the facility, and returns in the afternoon after a change in condition for a second, related procedure. An edit bundles the two.

The services occurred at genuinely separate encounters, so the second carries modifier XE. Documented times for each encounter are what support it — arrival, procedure and departure for both.

A single visit during which the patient waited two hours between two procedures is one encounter, not two, however long the gap felt.

What decides it

XE is the easiest X modifier to defend because the evidence is objective. Times are recorded contemporaneously and do not depend on anyone's interpretation of what counts as separate.

It is also the least used, because genuinely separate same-day encounters are uncommon outside emergency and urgent care settings. A practice reporting XE frequently in a scheduled outpatient setting is describing something unusual, and the pattern is visible.

The documentation requirement is simply that both encounters are separately recorded with their own times. Where a practice's system records one visit per day per patient, that is a configuration problem to solve before the modifier can be supported.

Denial codes this affects

Modifiers often confused with this one

Terms used here — NCCI Edits · Modifier · Claim Scrubbing

How we handle it — Medical Coding · Claims Management · Denial Management

Primary sources

What the payers and code-set maintainers actually publish about modifier XE.

Questions about modifier XE

When two services were distinct because they occurred at separate encounters on the same day — the patient left and returned. It is the cleanest X modifier to support, because the separation rests on documented times rather than clinical judgement.

No. A pause within a single continuous visit is one encounter regardless of duration. The patient leaving and returning is what creates a separate encounter.

Because genuinely separate same-day encounters are uncommon outside emergency and urgent care. A scheduled outpatient practice reporting XE frequently is describing something unusual, and that pattern is visible in claims data.

Both encounters recorded separately with their own times — arrival, service and departure. Where a system records only one visit per patient per day, that configuration has to be fixed before the modifier can be supported.

Find out what your denials are costing you

A free billing audit reviews your denial rate, AR aging and clean claim rate against industry benchmarks. Takes about two minutes to request. No sales pitch.

No setup fees · You pay when we collect · Pricing from 3% of net collections