Core MB

Home  /  Specialties  /  Ambulance & EMS

Ambulance and EMS billing services

Ambulance billing is built on the run report. Level of service, loaded mileage, origin and destination, and the reason the patient could not travel by any other means all have to be supported by what the crew documented. Whether a claim pays depends on that narrative, the correct HCPCS pairing, and a signed physician certification when the transport was non-emergent.

What makes ambulance billing different

Ambulance claims follow rules that no office-based specialty uses, and most denials trace back to one of these.

See the full medical billing service →

  • Base rate codes A0428 and A0429 for BLS, A0426 and A0427 for ALS1, A0433 for ALS2 and A0434 for specialty care transport are chosen from the services documented, not from the crew that was dispatched.
  • Mileage bills on A0425 for loaded miles only, reported to the tenth of a mile for Medicare trips under one hundred miles, and air mileage uses A0435 or A0436 paired with the A0430 or A0431 base rate.
  • Every transport line carries a two-character origin and destination modifier such as RH, HH, HN or NH, and the pickup ZIP code drives the fee schedule locality, so an incorrect ZIP or modifier pair reprices or rejects the claim.
  • Non-emergency transports need a Physician Certification Statement, and repetitive scheduled non-emergent transports require Medicare prior authorization under the national RSNAT program before the fourth round trip.

Denials we see most in ambulance

Every denial gets a root cause, a fix and a feedback loop, so the same denial stops coming back.

Medical necessity not supported

The run report never states why the patient could not sit in a wheelchair or car. Core MB requests crew addenda when appropriate and appeals with the PCS, orders and condition documentation.

Level of service downcoded

ALS1 billed with no ALS assessment or intervention documented, so the payer pays BLS. Core MB codes from the narrative and vitals and shows the ALS assessment wording crews need to record.

Origin and destination mismatch

The modifier pair conflicts with the addresses or the facility type on the claim. Core MB validates modifiers against the dispatch addresses before release and corrects the facility classification on the appeal.

How Core MB bills for ambulance

Core MB bills ambulance transports from the electronic patient care report, matching level of service, mileage and modifiers to the crew narrative, and chasing PCS forms and prior authorizations before claims go out. Enrollment for new ambulance suppliers runs in the same client portal. Credentialing for new providers runs in the same system, tracked live in your client portal.

  • Every run report is reviewed for the ALS assessment, loaded mileage and condition narrative before a level of service is assigned.
  • PCS forms for non-emergent transports are tracked by patient and expiration date so repetitive transports never bill against an expired statement.
  • Facility-paid transports under consolidated billing are flagged so SNF and hospital-responsible trips are invoiced to the facility rather than Medicare.

Everything in the service

From eligibility on the pickup date through the last appeal, Core MB covers the full billing cycle for ambulance services and keeps your crews focused on patients, not paperwork.

  • Insurance verification and eligibility checks
  • Charge entry and specialty-specific coding review
  • Claim scrubbing and electronic submission
  • Payer follow-up on every open claim
  • Denial management and appeals
  • Payment posting and reconciliation
  • Accounts receivable recovery
  • Patient statements and balance support
  • Monthly reporting you can read in five minutes
  • Provider credentialing and payer enrollment

Ambulance billing questions

Which modifier goes on an ambulance claim when the patient is transported from a nursing home to a hospital?

The origin and destination pair is NH, nursing home as the first character and hospital as the second. Core MB confirms the facility type from the address because a skilled nursing facility stay under Medicare Part A may make the transport the facility's responsibility rather than a Part B claim.

Why does Medicare deny our dialysis transports even though the patient is bedbound?

Repetitive scheduled non-emergent transports require a prior authorization request built on a PCS and supporting records showing the patient cannot safely travel any other way. Core MB submits the request before the fourth transport, tracks the decision and resubmits with additional documentation when the MAC asks for more.

What happens when a crew is dispatched but the patient dies before transport?

If the patient is pronounced dead after the ambulance is called but before transport begins, Medicare pays the BLS base rate with modifier QL and no mileage. Core MB codes these runs from the time of pronouncement in the report so the claim is paid rather than denied as a no-transport.

How do we get started with Core MB for ambulance billing?

Submit the quote form with your service area, transport mix and current software. Core MB maps the ePCR export, builds the modifier and PCS workflow and runs the transition alongside your current billing so no runs are missed. Enrollment or revalidation for new ambulance suppliers can start at the same time.

Every transport documented, coded and paid the way it was run

Core MB turns run reports into clean ambulance claims, handles PCS and prior authorization tracking, and works every denial until the transport is resolved.