How do you decide between ALS and BLS level codes?

What is the difference between ALS and BLS on an ambulance claim?

On the clinical side, BLS is care an EMT can give: oxygen, bleeding control, splinting, CPR, an AED. ALS is care that state and local law reserves for a paramedic or EMT-Intermediate: IV or intraosseous access, drug administration, advanced airways, cardiac monitoring and manual defibrillation. On the claim, none of that is what you are coding. Medicare pays for the level of medically necessary service actually furnished, not for the truck that showed up or the patch on the crew member’s sleeve. A fully equipped ALS unit that gave only basic care bills BLS. That single rule settles most of the arguments that reach a biller’s desk.

The distinction is worth real money, which is why payers audit it. The base rate for every ground level is a fixed relative value unit under 42 CFR 414.610, multiplied by a national conversion factor and a geographic adjustment. BLS is the baseline at 1.00. An ALS1 emergency is 1.90, which is 90 percent more for the same trip. Agencies that run mostly paramedic units and bill mostly BLS are leaving that gap on the table, and agencies that bill ALS because a paramedic was aboard are collecting money they will hand back. For the wider picture of how the ambulance revenue cycle is built around these codes, see our ambulance revenue cycle management breakdown.

How do you decide the level, step by step?

Work the claim in this order. Skipping to the code is how agencies end up defending a level they cannot support.

1. Confirm the transport itself is medically necessary. Other means of transportation must be contraindicated by the patient’s condition. If that test fails, the level does not matter because nothing is payable.
2. Decide emergency or non-emergency. An emergency response means responding immediately at the BLS or ALS1 level to a 911 call or its local equivalent. This flag changes the code, not the level.
3. Read the run report for ALS interventions actually performed. One qualifying intervention puts the claim at ALS1 on its own.
4. If there were no interventions, test the ALS assessment pathway. It is available only on emergency responses and only when the dispatch protocol sent an ALS crew based on the patient’s reported condition at the time of dispatch.
5. Count medication administrations and listed procedures to see whether ALS2 applies.
6. Pick the code, attach the origin and destination modifier, and add the loaded mileage.

Steps three through five are coding judgment made against documentation, which is why they belong with certified coders rather than with dispatchers. Our medical coding team works these decisions claim by claim against the run report.

What makes a call ALS1 emergency rather than BLS emergency?

Two separate doors lead to ALS1, and most published guidance only describes one of them. Under 42 CFR 414.605, ALS1 is ground transport plus medically necessary supplies and services and either an ALS assessment by ALS personnel or the provision of at least one ALS intervention. Either door is enough. Neither door requires the other.

The ALS intervention pathway

An ALS intervention is a procedure that state and local law requires ALS personnel to furnish. Starting an IV, pushing a drug, placing an advanced airway, running a 12-lead, manual defibrillation. One of them, documented with a time and a performing clinician, carries the claim to ALS1. This is the pathway everybody knows, and it is the reason so many agencies believe that a quiet transport can never be ALS.

The ALS assessment pathway

The second door is the one that gets missed. An ALS assessment is an assessment performed by an ALS crew as part of an emergency response that was necessary because the patient’s reported condition at the time of dispatch was such that only an ALS crew was qualified to perform it. The regulation then says something people skip over: an ALS assessment does not necessarily result in a determination that the patient requires an ALS level of service. The Benefit Policy Manual closes the loop by stating the service is covered at the ALS emergency level regardless of whether the patient required ALS intervention services.

So a chest pain call that turns out to be reflux, dispatched as ALS under a recognized protocol, assessed by a paramedic, transported with nothing more than oxygen, is an ALS1 emergency claim. Three conditions have to hold together: an emergency response, a dispatch center using a recognized dispatch protocol, and that protocol designating the call ALS based on the reported condition. Miss any one and you are back to BLS.

Which ambulance HCPCS codes and modifiers match each level?

Once the level is settled, the ambulance billing codes are mechanical. Emergency and non-emergency are separate codes at the BLS and ALS1 levels, and a single code covers ALS2 either way. Every claim also needs a two-letter origin and destination modifier and a mileage line.

The payment spread is the reason the level is worth arguing about. Measured against the BLS base rate, BLS emergency pays 160 percent, ALS1 pays 120 percent, ALS1 emergency pays 190 percent, ALS2 pays 275 percent and specialty care transport pays 325 percent.

Modifiers are their own failure point. The first letter is the origin, the second is the destination: R for residence, H for hospital, N for skilled nursing facility, S for scene of an accident or acute event, E for a residential or custodial facility, G and J for the two kinds of dialysis facility, P for a physician’s office, D for a diagnostic or therapeutic site, I for a site of transfer. For the full mechanics of assembling a Medicare ambulance claim around these codes, read our guide to how ambulance services bill Medicare.

What has to be in the run report to support the level you billed?

A level is only as good as the record behind it. When a payer or auditor asks why a claim was ALS1 rather than BLS, these are the fields they read, and these are the fields that are missing when the claim comes back downcoded.

• The dispatch center name and the response priority, so the emergency response is on the face of the record.
• The dispatch protocol or determinant code that sent an ALS crew, with the reported patient condition that triggered it.
• The level of the unit that arrived and the certification level of each crew member aboard.
• Assessment findings in narrative form, not a checkbox, showing what the paramedic evaluated and ruled out.
• Every intervention with a clock time and the clinician who performed it.
• On assessment-only calls, the paramedic’s stated reason for not intervening.
• Loaded miles from origin to destination, and the reason the destination was the nearest appropriate facility.

In our claim audit, missing or unsigned Physician Certification Statements appeared on 18% of non-emergency transports, and origin and destination modifier errors appeared on 6% of ambulance claims. Those are documentation failures, not coding failures, and they are the cheapest ones to fix. Our full-service billing team reads the run report before the claim goes out rather than after it comes back.

What happens when the level changes mid-call or another agency intercepts?

Code the transport that happened, as a whole. A BLS unit that arrives, starts transport, and meets a paramedic who boards and starts an IV has furnished an ALS1 service, and the transporting entity bills it. The reverse also holds: an ALS unit dispatched under an ALS protocol that finds a stable patient still reaches ALS1 through the assessment pathway on an emergency response, but the same unit on a scheduled non-emergency run with no interventions bills BLS non-emergency. Dispatch level alone never carries a non-emergency claim.

Paramedic ALS intercept is the narrow exception, and it is narrower than most agencies assume. Under 42 CFR 410.40(d), the intercept code is payable only where the paramedic service operates in an area designated rural by state law or regulation, under contract with volunteer ambulance services that furnish only BLS care and are prohibited by state law from billing for any service. In practice that combination exists in very few states. Everywhere else, the transporting agency bills the level of service furnished and the two entities settle between themselves under a written agreement. Repetitive scheduled non-emergency transports add a prior authorization layer on top, which our prior authorization team handles before the first trip rather than after the tenth denial.

What does getting the level wrong actually cost?

Take an agency running 3,000 emergency transports a year. Assume a $450 BLS base rate after the geographic adjustment, which puts BLS emergency at $720 and ALS1 emergency at $855, a gap of $135 per transport. If 9% of those emergency transports met the ALS assessment standard but were coded BLS, that is 270 trips and $36,450 of base payment a year, before mileage and before the same pattern repeats in the next year’s claims. Run the error the other way and the arithmetic is worse. If 1,800 of those trips go out as ALS1 emergency and 11% of them carry no documented assessment and no documented intervention, that is 198 claims at $135 of exposure each, $26,730 refundable on audit, with extrapolation and interest available to the auditor on top.

Level discipline travels with the rest of the claim. Across our client practices, first-pass denial rate fell from 14.2% to 6.1% within 90 days of onboarding, clean claim rate rose from 89.6% to 97.3% in the first 90 days, and net collection rate rose from 91.4% to 97.8% over the first six months.

For one ambulance client, the same work moved days in AR from 71 to 38. Where the level was billed correctly and the payer still downcoded, the fix is an appeal with the assessment narrative attached, which is the core of our denials and AR recovery work.

What are the most common ALS and BLS coding mistakes?

Six patterns account for most of the level errors we see. An ALS assessment that happened but was never written down accounts for 31% of them, a dispatch level that never reached the ePCR another 24%, missing intervention times 18%, a short ALS2 count 14%, a miscoded intercept 8% and a wrong emergency flag 5%.

The others follow from the same root. Crews log interventions without times, so a real ALS1 cannot be proved. Dispatch priority never makes it into the ePCR, so the assessment pathway is unavailable even when it applied. ALS2 gets billed on two medication administrations instead of three, or on a procedure that is not one of the eight listed. Intercept gets coded where the rural and volunteer conditions do not hold. And the emergency flag gets set from the lights and siren rather than from the dispatch record.

Two pieces of advice in circulation are worth correcting directly. A physician order does not set the level: it speaks to medical necessity, and 42 CFR 410.40 requires the patient’s condition to justify both the transport and the level of service provided. And defaulting to ALS when the record is unclear is not a conservative choice, it is an audit finding waiting to be written. If level-of-service coding is one of several places your revenue cycle is leaking, a billing review will show you where the rest are.

BLS, ALS1 or ALS2: which level does the record support?

Read across from what the documentation proves, not from the unit that responded. Base payment is shown as a share of the BLS base rate, set by the relative value units in 42 CFR 414.610.

Ambulance and EMS agencies

This is where the decision lives. The fight is almost never about whether a paramedic was aboard, it is about whether the assessment was documented well enough to survive a read. Agencies with strong ePCR narrative discipline bill ALS1 emergency on assessment-only calls and keep the money. Agencies without it bill BLS defensively and lose 90 percent of the base rate on every one of those trips. Build the dispatch protocol field into the ePCR template and the argument mostly ends.

Hospital-based ambulance services

Hospital-operated transport programs run the professional claim through a different system than the facility side, and the level often gets set by whoever is closest to the chart rather than by the run report. Watch the origin and destination modifier in particular: an H to H interfacility run and an S to H 911 response are coded from the same fleet and frequently get the same modifier by habit. Specialty care transport at A0434 applies only when the care exceeds paramedic scope.

Skilled nursing facilities

SNF transports are mostly non-emergency, which removes the ALS assessment pathway entirely. Without it, the level turns purely on interventions performed, and most SNF runs are BLS non-emergency at A0428 with an N origin modifier. Part A consolidated billing rules can also make the transport the facility’s responsibility rather than a Part B claim, which is a separate test run before the level question. See our skilled nursing facility billing page for that boundary.

Emergency departments as the destination

The receiving ED does not set the ambulance level, but its documentation often decides an appeal. When a payer downcodes an ALS1 emergency, the ED triage note describing the presenting complaint corroborates the dispatch protocol and the paramedic assessment. Agencies that can pull that note into an appeal packet overturn more downcodes than agencies that appeal on the run report alone. Our emergency room billing page covers the facility side of the same encounter.

Dialysis and repetitive transports

Scheduled dialysis runs are the most-audited category in the ambulance benefit and almost always BLS. The level question is nearly settled before it is asked, and the real work moves to the Physician Certification Statement dated no earlier than 60 days before the service, the bed-confinement test, and prior authorization for repetitive non-emergency transport. Billing ALS on a stable dialysis run because a paramedic drove is the single fastest way to attract a review.