CMS ABN Form 2026: Avoid Costly Denials Before the May 12 Deadline

CMS released the updated Advance Beneficiary Notice of Noncoverage. Here's what's changing, what isn't, and how to protect your ambulance reimbursement.

CMS ABN form 2026 update for EMS ambulance Medicare billing compliance

Share

CMS ABN Form 2026: Critical Update EMS Agencies Must Make by May 12

The CMS ABN form 2026 update is here, and every ambulance service that bills Medicare needs to have the new version in rotation by May 12, 2026. Miss that deadline, and you’re putting reimbursement at risk on the exact runs where you can least afford to lose it.

The good news: this isn’t a major operational overhaul. The form looks cleaner, reads more easily, and the underlying rules haven’t changed. The bad news: if your crews are still handing out the old form on May 13, or worse, using ABNs incorrectly in the field, you could lose your ability to collect from the patient when Medicare denies the claim.

Here’s what’s changing, what isn’t, and what your agency should do this month to stay clean.

What is the ABN, and why does it matter for ambulance services?

The Advance Beneficiary Notice of Noncoverage is the form an ambulance provider gives a Medicare Fee-for-Service patient before a transport when there’s reasonable belief that Medicare will deny the claim. It’s not a billing form. It’s a notice form — and it’s the legal mechanism that lets you bill the patient directly when Medicare won’t pay.

Without a properly issued ABN, two things happen if Medicare denies the claim:

  1. You can’t shift financial liability to the patient.
  2. You eat the write-off.

For ambulance services specifically, CMS has carved out narrow but important rules. An ABN is mandatory in non-emergency ambulance transport situations when all three of these conditions are met:

  • The service is a Medicare-covered ambulance benefit under federal regulation
  • The provider has a reasonable basis to believe Medicare will deny the claim, in whole or in part, as “not reasonable and necessary”
  • The transport is non-emergency and the patient is not under duress

That third point is where ambulance services differ from most other Medicare providers. You cannot issue an ABN during an emergency or when a patient is under similar duress. CMS treats that as coercion, and a coerced ABN is an invalid ABN.

What’s new in the CMS ABN form 2026 update?

CMS issued the updated form on March 13, 2026. The Office of Management and Budget approved it for a standard three-year cycle, so this version is valid through March 31, 2029.

The form itself was cleaned up — CMS reduced visual clutter and revised wording in several sections for readability. The substantive requirements and provider responsibilities have not changed. Same fields. Same patient options. Same notifier obligations. Same GA modifier on the back end to signal to Medicare that a signed ABN is on file.

The previous version of the ABN technically expired January 31, 2026, but CMS is giving providers a transition window. You can continue using the old form through May 12, 2026. After that date, the updated form is required, and using an outdated version may invalidate the notice and the financial liability transfer that goes with it.

When EMS agencies should — and shouldn’t — issue an ABN

This is where we see the most confusion in the field, and frankly, where we see the most revenue leakage. Here’s the short version.

Issue an ABN when:

  • Non-emergency transports where medical necessity is questionable. The patient is stable, the transport is scheduled or routine, and you have a reasonable basis to think Medicare may deny.
  • Level-of-care downgrades. Example: an ALS-staffed unit responds, but the call clearly should have been billed at BLS. If you’re providing a higher level than the patient’s condition supports, an ABN protects you on the upgrade portion.
  • Air-to-ground situations. When an air transport is requested but a ground transport would have been clinically appropriate and safe.
  • Repetitive non-emergency transports. Dialysis runs, wound care transports, scheduled hospital-to-SNF moves — anywhere the medical necessity bar is high and your documentation may not clear it.

Do NOT issue an ABN when:

  • The patient is having a medical emergency or is under duress. This is the single biggest compliance mistake we see. An ABN handed to a patient on a 911 response is not just useless — it’s a compliance problem.
  • The service is statutorily excluded from Medicare entirely (for example, wheelchair van transport). These aren’t denials — they’re never-covered services. You don’t need an ABN; you can use a voluntary Notice of Exclusions from Medicare Benefits (NEMB) instead as a courtesy.
  • You’re issuing it as a blanket cover-your-bases form. CMS explicitly prohibits “blanket ABNs.” Each ABN must state the specific reason you believe coverage may be denied. “Just in case” is not a reason.

The prior authorization wrinkle EMS agencies in PA and NJ need to remember

If you’re operating in Pennsylvania, New Jersey, or any of the other states in the Repetitive Scheduled Non-Emergent Ambulance Transport (RSNAT) prior authorization program, the CMS ABN form 2026 works alongside — not instead of — the prior auth requirement.

For patients getting three or more round trips in a 10-day period, or at least one round trip per week for three weeks or more, your agency or the patient may submit a prior authorization request to Medicare before the fourth round trip in a 30-day window. If prior auth is denied and the patient still needs the trip, you’ll need a valid ABN on file to bill the patient.

Get the prior auth wrong and the ABN wrong, and you’ve stacked two unbillable problems on top of each other.

What your EMS agency should do before May 12, 2026

Three essential steps, in order:

1. Download the new form from CMS directly. The current version is posted on the CMS Beneficiary Notices Initiative (BNI) page in both English and Spanish. Don’t pull it from a third-party PDF you found on Google — vendors and clearinghouses sometimes lag behind CMS, and an out-of-date form is an invalid form.

2. Replace the old form everywhere it lives. Every rig. Every iPad. Every binder. Every billing office printer tray. Every ePCR template that auto-generates an ABN. Once you implement the new version, the old one should be pulled from circulation entirely. CMS will only accept the current approved version after May 12.

3. Re-train the people actually handing the form to patients. This is usually the gap. Crews on non-emergency transports, scheduled-transport coordinators, and dispatch supervisors all need a quick refresher on the three-criteria test and the no-duress rule. The form itself didn’t change much — but the May 12 deadline is a perfect excuse to re-anchor the policy.

Where ARS clients stand on the CMS ABN form 2026 transition

If you’re a current ARS client, your billing team is already tracking this. We’re updating ABN references in client onboarding materials, confirming current-version usage during routine documentation review, and flagging any incoming PCRs that reference the outdated form so it can be corrected before submission.

If you’re not yet working with ARS and you’re not sure whether your agency is positioned to make the May 12 deadline cleanly — or you’ve had ABN-related denials that you suspect were technically avoidable — that’s exactly the kind of detail an EMS-only billing partner should be catching for you.

ARS has been billing exclusively for ambulance services since 1989. We work with municipal and volunteer EMS agencies across Pennsylvania and New Jersey, and Medicare compliance work like this is the baseline of what we do, not an add-on. Learn more about our EMS billing services or contact our team to talk through where your agency stands.


This article is informational and does not constitute legal or compliance advice. For the official form, current instructions, and the Medicare Claims Processing Manual, Chapter 30, visit the CMS Beneficiary Notices Initiative page.