Ambulance Origin-and-Destination Modifiers

CMS's instruction is short and its shape is the whole point. Origin-and-destination modifiers are created by combining two alpha characters; each character, with one exception, represents either an origin or a destination; the pair of characters creates one modifier; the first position is the origin and the second is the destination. There are eleven characters, and the exception is that one of them can only ever appear in the second position.

Because the code cannot hold it. CMS describes the ambulance fee schedule's coding logic in six lines, and two of them explain the whole design: there are seven categories of ground service and two of air, and payment is based on the condition of the beneficiary, not on the type of vehicle used. The code therefore answers what level of service the beneficiary's condition required. It is silent about the journey.

And the journey is what the rest of the program cares about. Two things turn on the endpoints, and they turn on different ends of the trip.

The destination governs coverage

Medicare's ambulance benefit has an origin-and-destination requirement, and the modifier is where the claim states whether it is met. CMS's manual records a concrete instance of that requirement being settled by rule: from 24 February 1999, transports to or from a non-hospital-based dialysis facility — the modifier character for a freestanding end-stage renal disease facility — satisfy the program's origin-and-destination requirements for coverage. That is a coverage determination expressed as a character in a modifier.

The origin governs payment

Payment is determined by the point of pickup, as reported by its five-digit ZIP code. 42 CFR 414.610(e) (opens in a new tab) puts it as a requirement: the ZIP code of the point of pick-up must be reported on each claim for ambulance services so that the correct geographic adjustment factor and rural adjustment factor may be applied. The manual defines the point of pickup as the location of the beneficiary at the moment of being placed on board — not where the vehicle was dispatched from, and not where the call came from.

This is the part that surprises people who have worked the field for years, and it is worth being exact about because the wording is CMS's own. Since the early implementation of the 5010 professional format in January 2011, electronic billers have been required to report the loaded trip's destination information — the ZIP code of the point of drop-off — in addition to its origin information. And then: only the ZIP code of the point of pickup will be used to adjudicate and price the ambulance claim, not the point of drop-off. The drop-off ZIP is an additional reporting requirement rather than an input to the payment.

Count what the claim now says about where the trip ended: the second character of the modifier, and a ZIP code. Two statements, neither of which sets the amount. The amount comes from the other end.

1. 01

   On the paper professional claim, the pickup ZIP is item 23

   The same field that carries a laboratory's certification number on a laboratory claim — a reminder that item 23 is a multi-purpose field whose meaning depends on what is being billed, which the corpus also covers under billing CLIA-waived tests.
2. 02

   One pickup ZIP per claim

   Because the ZIP prices the claim, more than one ambulance service may share a paper claim for a beneficiary only where every point of pickup has the same ZIP code. Where the points of pickup sit in different ZIP codes, a separate claim is required for each trip.
3. 03

   No ZIP, or more than one, returns the claim

   A claim with no ZIP code in that item, or with multiple ZIP codes in it, must be returned as unprocessable. As with the laboratory case, that is a rejection rather than a denial — no determination to appeal, a corrected submission as the remedy, and a filing period that has been running throughout.

An ambulance line often carries two modifiers doing unrelated jobs, and the second one is about who furnished the service rather than about where it went. Institution-based providers must report, with every ambulance code, whether the service was furnished directly by the provider of services or provided under arrangement by it — QN for the first and QM for the second. CMS's editing on institutional ambulance claims looks for both an origin-and-destination modifier and one of that pair on every ambulance line item.

The distinction is not cosmetic. It decides which contractor adjudicates the claim and which entity submits it: ambulance services furnished under arrangement with a provider are typically billed by the provider to its Part A contractor rather than by the supplier to its Part B contractor. The manual also draws a narrow, chapter-specific line between the words provider — an institution-based ambulance operation owned or operated by a hospital, critical access hospital, skilled nursing facility, rehabilitation facility, home health agency or hospice — and supplier, meaning any ambulance service that is not institutionally based. Reading either word in its ordinary Medicare sense will produce the wrong answer in this chapter.

An ambulance trip has as many candidate dates as a laboratory test has, and CMS answers it for this benefit specifically rather than generally. The date of service of an ambulance service is the date the loaded vehicle departs the point of pickup. Not the date of the call, not the date of dispatch, and not the date of arrival at the destination.

There are two named variations, both for the case where the beneficiary is pronounced dead before being loaded. For a ground transport the date of service is the date the vehicle was dispatched; for an air transport it is the date of takeoff. Both exist because the general rule refers to a loaded departure that never happened.

1. 01

   Build the modifier from the trip, in order

   Origin first, destination second, from the record of where the beneficiary actually was when loaded and where the vehicle actually delivered them. Building it from the dispatch record or from the caller's location produces a plausible modifier describing a different trip.
2. 02

   Take the pricing ZIP from the point of pickup, separately

   It is a different fact from the modifier and it comes from a different question — where the beneficiary was standing, sitting or lying when placed on board. A crew base ZIP, a facility ZIP or the destination ZIP will all price the claim, and all three will price it wrongly.
3. 03

   Split the claim by pickup ZIP, not by convenience

   Trips sharing one claim must share one pickup ZIP. A day's transports batched onto one claim will be returned the moment two of them started in different ZIP codes, and the rejection will not look like a geography problem.
4. 04

   Never reason about this modifier from the rest of the modifier system

   The character combinations overlap with other HCPCS modifiers and mean only origin and destination on an ambulance transportation code. This is the one place in the modifier system where a familiar two-character string should be read as a fresh fact rather than recognized.
5. 05

   Decide the furnished-directly-or-under-arrangement question before coding

   It sets the second modifier, and it also decides which entity bills and which contractor adjudicates. Getting it wrong is not a modifier error that can be corrected on the same claim; it is the wrong claim, from the wrong party.
6. 06

   Sort the unprocessable returns out of the denial queue

   A missing or duplicated pickup ZIP returns the claim rather than denying it, so it carries no appeal right and stops no clock. Worked as a denial it will sit in a queue waiting for a determination that was never made.