Denial AppealsAugust 4, 2026

No Surprises Act independent dispute resolution: how emergency and air ambulance balance-billing appeals work

CMS says the No Surprises Act protects patients from many surprise bills for emergency services and certain out-of-network services at in-network facilities, limits patient cost-sharing in covered situations, and establishes a patient-provider dispute resolution process for certain self-pay or uninsured patients. That's the line everyone quotes. In revenue cycle, though, the breakdown usually happens earlier: teams treat the independent dispute resolution, or IDR, track like a routine underpayment appeal and forget that the patient billing protections drive the workflow. Per CMS, this is a billing restriction framework first, not just a payment fight.

The first mistake is using the patient as leverage

Look, if the claim falls into the No Surprises Act patient billing protections described by CMS, the standard out-of-network playbook has to stop. Emergency services are in scope. Certain out-of-network services at in-network facilities are in scope. And air ambulance services sit within the broader No Surprises Act framework CMS maintains on its patient billing protections page.

In practice, the point is simple, even when the payment dispute is not. Staff cannot let balance bills, collection language, or inflated patient statements become the pressure point while the payer and provider are still in dispute. The law is built around limiting the patient's cost-sharing in covered situations. If your system keeps dropping the full out-of-network balance to patient liability because the plan underpaid, you've created compliance exposure before IDR even enters the picture.

This is also where emergency claims break workflows. Emergency accounts move fast, registration data can be incomplete, and the claim can cross from facility billing to professional billing to vendor air transport billing. If those teams do not share the same coverage and No Surprises Act status flags, one side can hold the patient harmless while another sends a balance notice. Avoidable. And exactly the kind of mess that turns a payment dispute into a complaint.

Before anyone talks IDR, sort out what track the claim actually belongs on

Here's the thing. The No Surprises Act created a federal dispute pathway for certain out-of-network payment disputes. That pathway sits alongside, not inside, ordinary claim reconsideration logic. So the first operational question is not, "Did the payer underpay?" It is, "Is this one of the protected claim types where the patient billing limits apply and the provider-plan dispute belongs in the No Surprises Act structure?"

For emergency services, that usually turns on whether the service is part of the protected emergency encounter and whether the claim was processed as out-of-network. For air ambulance, the same discipline applies. Do not collapse those claims into standard underpayment buckets just because the remittance looks familiar.

If the account qualifies for the federal protections, the downstream path is different. CMS frames the No Surprises Act as a set of patient billing protections, not merely a claims payment edit. Your appeal inventory should separate at least three things internally: protected emergency claims, protected air ambulance claims, and everything else. Without that early split, staff default to the payer's ordinary reconsideration forms, ordinary collection timelines, and ordinary patient statement cadence. Backwards for these accounts.

And don't overcomplicate this with unsupported payer-specific folklore. The source packet does not give payer-by-payer IDR instructions for UnitedHealthcare, Aetna, Cigna, Anthem, or other commercial plans. So the safe operational point is straightforward: whatever payer name is on the card, the federal patient billing protections can change what your team is allowed to bill the patient and how the payment dispute should be handled.

For emergency and air ambulance files, documentation control decides everything

None of this works if the documentation package is sloppy. One of the few broad lessons that clearly carries across reimbursement fights is the one highlighted in MedLearn's reporting on CMS oversight: documentation, enrollment compliance, and clinical decision-making remain under increased scrutiny. That reporting was about home health oversight, not No Surprises Act IDR, so it should not be stretched beyond that. Still, the operational takeaway holds. When regulators and payers review payment, weak documentation gives them the opening.

For emergency and air ambulance disputes, the file has to support the status of the service, the coverage situation, the patient billing treatment, and the payment challenge path the team chose. If you cannot show why the claim belongs in the protected bucket, you invite rework. If you cannot show what the patient was or was not billed, you invite complaints. And if the clinical and billing records do not line up, the dispute gets harder for no good reason.

Build the file like someone outside the organization will read it cold. The claim record, remittance activity, patient liability treatment, and correspondence need to tell one coherent story. Not five versions scattered across the facility account, pro fee account, and air transport vendor notes.

Code selection matters too, but only in the way the source packet supports. Use the actual CPT, HCPCS, and ICD-10 identifiers on the claim consistently across all related records, and make sure any modifier use matches the claim submitted and the services documented. The packet does not provide a code list for emergency or air ambulance services, so staff should not invent internal shorthand or relabel claim categories after the fact. In an IDR-sensitive account, even basic coding inconsistency can make the dispute package look unreliable.

Monday morning, tighten the intake point first

Here's the practical move: create one No Surprises Act intake checkpoint before any out-of-network emergency or air ambulance account reaches patient statements or routine appeal staff. The checkpoint should answer only a few questions, in plain language, before the account goes anywhere else:

Is this an emergency service claim or an air ambulance claim that may fall under CMS patient billing protections?
Has patient cost-sharing been limited appropriately for a covered situation?
Has the account been pulled out of ordinary out-of-network balance-bill workflows?
Is the dispute file complete enough to support the provider-plan payment challenge?

Not glamorous. But it stops the most expensive operational mistake: treating a protected balance-billing dispute like a generic underpayment appeal.

One more thing. Keep policy references current. The Federal Register proposed rule for calendar year 2027 says CMS would revise the Medicare Hospital Outpatient Prospective Payment System and the Ambulatory Surgical Center payment system based on continuing experience with those systems, and it also proposes to implement certain provisions of the Consolidated Appropriations Act, 2026, for off-campus outpatient departments of a provider. That rule is not an IDR manual. But it does underline the point that payment operations, compliance obligations, and federal billing rules keep moving together. A No Surprises Act workflow cannot sit in a drawer while the rest of reimbursement policy changes around it.

If the team does one thing Monday morning, do this: pull every open out-of-network emergency and air ambulance account out of the standard self-pay and underpayment queues, add a No Surprises Act status review, and make one owner responsible for both patient billing compliance and dispute-readiness on each file. That's usually where the leaks are.