837P for NEMT: how electronic transportation claims are built and sent
The 837P is the HIPAA electronic claim for professional services, and Medicaid programs and plans use it for NEMT. Payers use version 5010, implementation guide 005010X222A1. It carries the same data as a CMS-1500, arranged in loops for the billing provider, member, claim, and service lines. Many NEMT programs also require pickup and drop-off addresses and trip times.
On this page
What the 837P is
The 837P is the electronic version of the CMS-1500. It is the HIPAA standard transaction for professional claims, and NEMT programs use it because transportation is billed as a professional service. The standard is published by ASC X12, and HHS adopted it as the HIPAA standard for professional claims in 45 CFR 162.1102.
The version in use is 5010. The regulation names the implementation guide 005010X222, and Medicare’s EDI manual lists 005010X222A1 as the current version, which includes the A1 errata. When a companion guide or clearinghouse says “5010A1,” it means the same thing.
Medicaid NEMT programs use it every day:
- Colorado says the 837P “should be utilized for electronic billing” of NEMT and treats portal claims as professional claims.
- North Dakota accepts the CMS-1500 or an 837P for NEMT.
- Texas takes Medical Transportation Program claims through TexMedConnect or through the TMHP EDI gateway, which runs on version 5010.
Everything that goes on the paper form has a place in the file. If you know the CMS-1500, you already know most of the data.
How an 837P file is organized
An 837P file is plain text made of segments. Each segment starts with a short ID and ends with a terminator character, usually a tilde. Segments group into loops, and loops nest in a hierarchy. The table covers the parts a NEMT biller runs into.
| Part | What it holds | CMS-1500 equivalent |
|---|---|---|
| ISA, GS, ST | The envelope: sender, receiver, version, control numbers | None |
| Loop 1000A | Submitter name and contact | None |
| Loop 1000B | Receiver, the payer you are sending to | None |
| Loop 2000A and 2010AA | Billing provider: taxonomy, name, NPI, address, tax ID | Items 33 and 33a |
| Loop 2000B and 2010BA | Subscriber: the member’s name and Medicaid ID | Items 1a and 2 |
| Loop 2300, CLM segment | Claim ID, total charge, place of service, frequency code | Items 24B, 22, and 28 |
| Loop 2300, HI segment | Diagnosis codes | Item 21 |
| Loops 2310E and 2310F | Ambulance pick-up and drop-off locations | No direct box |
| Loop 2400, SV1 segment | Procedure code, modifiers, charge, unit type, units | Items 24D, 24F, and 24G |
| Loop 2400, DTP segment | Date of service | Item 24A |
| Loop 2400, NTE segment | Line notes, used by some programs for trip times | No standard box |
The CLM segment’s fifth element carries the place of service and the claim frequency code: 1 for an original claim, 7 for a replacement, and 8 for a void. Corrections also carry the payer’s original claim number in a REF segment with qualifier F8.
A NEMT service line, read piece by piece
Nevada’s NEMT encounter companion guide includes a sample line for an ambulatory trip. Here is the service line portion:
SV1*HC:A0120*139.8*UN*1***1:2**Y~
DTP*472*D8*20180111~
NTE*ADD*AT1400,PT1230,PA0000,AD1330~Read left to right:
- SV1*HC:A0120 is a HCPCS code (qualifier HC), A0120, for a mini-bus or ambulatory vehicle trip. Modifiers follow the code, separated by colons, when the payer requires them.
- 139.8 is the line charge, UN is the unit of measure, and 1 is one trip.
- The elements after the units point to the claim’s diagnosis codes and carry other line details.
- DTP*472 is the date of service, January 11, 2018 in this sample.
- NTE carries four trip times Nevada requires on certain codes: appointment time (AT), scheduled pickup (PT), actual pickup (PA), and actual drop-off (AD), each in 24-hour HHMM format.
A mileage line follows the same pattern, with the mileage code and the miles as units. See NEMT billing codes for which codes your state wants.
What NEMT programs add to the standard claim
The national standard allows a lot of optional data. NEMT companion guides decide which of it becomes required. Three examples:
- Pickup and drop-off addresses. Arizona’s Medicaid program requires them in loops 2310E and 2310F on NEMT encounters. Records missing them pend on edits H140 (pick up information missing) and H141 (drop off information missing), a hard edit in effect since October 1, 2022. They cannot be overridden and must be corrected with a replacement record.
- Trip times. Nevada’s NEMT encounter guide requires appointment, scheduled pickup, actual pickup, and actual drop-off times in the NTE segment when the code is A0120, A0130, T2005, or A0080.
- Origin and destination modifiers. The same guide requires a two-letter origin and destination modifier on each NEMT procedure code and lists the valid pairs for every code. Pharmacy trips use U1 for the trip out and U2 for the return instead.
Nevada’s guide also shows how strict these rules are. It excludes the CN1 segment from NEMT encounters and says transaction sets that include it will reject.
Acknowledgments: how you know the claim arrived
After you send a file, the payer sends back acknowledgments. Each one answers a different question.
| Response | What it tells you |
|---|---|
| TA1 | Whether the outer envelope (ISA and IEA) was readable. An R means the whole interchange was rejected. |
| 999 | Whether the file passed the standard’s syntax checks. AK9*A is accepted, R rejected, P partially accepted, E accepted with errors noted. |
| 277CA | Whether each claim was accepted into the payer’s system, or rejected with a reason. |
| 835 | The payment or denial, sent after the claim is processed. |
Nevada says a 999 normally arrives within one hour and can take up to 24 hours. It also says a 999 “does not guarantee processing.” A clean 999 only means the file was readable. Check the 277CA for each claim, and use the remittance advice to see what was paid.
Three ways to send an 837P
You do not need special software to bill electronically. There are three common routes:
- The payer’s web portal. Many Medicaid programs let you key professional claims directly. Colorado’s provider web portal and North Dakota’s web portal both take NEMT claims.
- Your own trading partner connection. You enroll with the payer as a trading partner, test, and send files yourself. Nevada enrolls trading partners through its provider portal. Texas takes files from third-party software and vendors through the TMHP EDI gateway.
- A clearinghouse. A clearinghouse is a company that receives your claims, checks them against each payer’s rules, converts them to the payer’s format, and forwards them. It returns the acknowledgments to you. It is most useful when you bill several payers.
Brokers set their own rules for how trips are billed, so check each contract. Our guide on how to bill Medicaid for NEMT covers the broker side.
Keeping the trip record complete
The NEMT-specific data payers ask for comes from the trip itself: addresses, times, service level, and miles. In HealthRide, each trip leg records pickup and drop-off addresses, scheduled and actual times, the driver, the vehicle, signatures, and GPS-recorded miles. The trip log exports all of it as a spreadsheet or PDF when a payer asks for proof of a trip.
Frequently asked questions
- Which version of the 837P do NEMT providers use?
- Version 5010. The HIPAA rule at 45 CFR 162.1102 names the ASC X12 837 Professional, 005010X222, and Medicare's EDI manual lists 005010X222A1 as the current version. State companion guides, such as Nevada's for NEMT, are written against 005010X222A1 and its errata.
- Do I need a clearinghouse to send 837P claims?
- No. Many Medicaid programs let you key claims into a web portal, such as Colorado's Provider Web Portal or Texas's TexMedConnect, or enroll as a trading partner and send files yourself. A clearinghouse is a service that checks and routes claims for you, which helps when you bill several payers.
- How does a 999 differ from a 277CA?
- A 999 is an implementation acknowledgment. It tells you whether the file or transaction passed the standard's syntax checks. A 277CA is a claim acknowledgment, which reports whether each claim was accepted into the payer's system. Neither one means the claim will pay. Payment and denials come later on the 835 remittance advice.
- Where do pickup and drop-off addresses go on an 837P?
- In the ambulance pick-up and drop-off location loops, 2310E and 2310F, when your payer requires them. Arizona's Medicaid program made missing pickup or drop-off data a hard edit for NEMT encounters: records without them pend for edits H140 and H141 and must be fixed with a replacement record.
- How do I correct an 837P claim that already paid?
- Send a replacement or void. The claim frequency code in CLM05-3 is 7 for a replacement or 8 for a void, and the payer's original claim number goes in a REF segment with qualifier F8. Nevada's NEMT encounter guide says to use the most recently paid Nevada Medicaid claim number when adjusting or voiding.
- What is a companion guide?
- A payer's own instructions for using the national 837P implementation guide. It cannot change the standard, but it narrows it: which codes the payer accepts, which optional fields it requires, and how to enroll and test. For NEMT, companion guides are where programs spell out modifiers, trip times, and address rules.
