Billing and claims
What Is Encounter Data in Medicaid? How Each NEMT Ride Gets Reported to the State
Encounter data is the record a Medicaid managed care plan or NEMT broker sends the state for each service a member receives, including every ride. Federal rules make plans collect and check it, and states validate it, send it to CMS, and set plan rates with it. Your trip records feed it, and brokers check them before they pay you.
- An encounter reports a service the plan or broker already paid for. It is not a second bill to the state.
- Federal money for a state's managed care contracts depends on validated encounter data, so brokers push hard for complete trip records.
- North Carolina reports each trip leg as its own encounter, with 24 items including times, miles, and both addresses.
- Texas holds its health plans to matching at least 85 percent of NEMT encounters to a medical visit or other health care event.
- Oregon and Ohio reject encounters for services by providers the state has not enrolled, so your Medicaid enrollment has to be in place.
What encounter data is
In a managed care program, the state does not pay for each ride. It pays a managed care organization or a transportation broker a set amount per member, and that plan pays you. The state still needs to know what care its members got. Encounter data is how it finds out: one record for each service, sent by the plan.
Federal rule 42 CFR 438.242 makes states require each managed care organization, prepaid inpatient health plan, and prepaid ambulatory health plan to collect data “on all services furnished to enrollees through an encounter data system or other methods as may be specified by the State.” A broker that covers only rides under a state contract, paid by capitation or rates other than the state’s own, is a NEMT PAHP. 42 CFR 438.9 applies the encounter data rules in 438.242 and 438.818 to it.
An encounter looks much like a claim, but it does not ask the state for money. CMS guidance for the national Medicaid data system, T-MSIS (updated December 20, 2024), has states report NEMT PAHP encounters as managed care encounter records, which it also calls dummy records. It adds that fee-for-service ride arrangements, including brokers that pay at state rates without taking risk, are not reported as managed care.
How one ride becomes an encounter
| Step | Who | What happens |
|---|---|---|
| 1 | You | Run the leg and record times, miles, and addresses. Send your invoice or claim. |
| 2 | Your broker | Checks the trip, pays you, and builds the encounter record |
| 3 | The health plan, if the broker works for one | Adds the ride to its encounter files for the state |
| 4 | The state | Reviews and validates the data for completeness and accuracy |
| 5 | CMS | Receives it in T-MSIS. Federal funding for the plan contract depends on it. |
Under 438.242(c), the plan’s contract with the state must provide for:
- Enough data to identify the provider who delivered each service
- Submission at the frequency and detail CMS and the state set
- All encounter data, including the allowed and paid amounts, so the state sees what you were paid
- Standard formats: the X12 837, with the 835 as appropriate. See the 837P.
The plan must also verify the accuracy and timeliness of what providers report, and screen it for completeness, logic, and consistency. Your trip log is the provider data it is checking.
What a NEMT encounter holds
North Carolina spells it out. Its Medicaid managed care NEMT policy (amended January 1, 2025) has plans report each leg of a trip as a separate encounter with 24 items:
| Group | What goes in |
|---|---|
| Who | Billing provider (the broker or subcontractor) and rendering provider (the company that drove) |
| The trip | A 9-character trip number unique to the encounter, trip type (initial, return, or transfer), leg number from 1 to 9, transportation type (such as WV for a wheelchair van), and the date the trip was requested |
| The rider | Special needs indicator, type of attendant, number of people riding along, and whether the member was picked up |
| Billing | The HCPCS code, a unit code (MJ for waiting time under T2007, UN for everything else), actual miles or minutes waited, and a place of service |
| Times | Appointment time, scheduled pickup, arrival at the pickup, departure, and drop-off |
| Places | Pickup and drop-off location types (such as DI for dialysis or HM for home) and both full addresses |
The same policy reports canceled trips as denied encounters. It checks for duplicates by claim number, or by the same billing and rendering provider, member, date, codes and modifier, and leg. Every NEMT encounter needs an ICD-10-CM diagnosis code, and the policy recommends Z76.89.
Nevada shows the file side. Its companion guide for ride encounters (August 4, 2026) requires origin and destination modifiers on each procedure code (pharmacy trips take initial and return trip modifiers instead), place of service 99, and the appointment, scheduled pickup, actual pickup, and actual drop-off times on lines billed with A0120, A0130, T2005, or A0080. Encounter files must go at least monthly, each encounter within 90 calendar days, and a disputed file must be corrected and resent within 60 days. One compliance error rejects the whole transaction set it sits in.
Each of those items comes from your trip leg record.
Why brokers push for complete trip data
Encounter data drives money at every level, so gaps in your records turn into questions for you.
Federal funding. Under 42 CFR 438.818, federal matching funds for a managed care contract are available only if the state sends CMS validated encounter data. If a state cannot fix a noncompliant submission, CMS may defer or disallow funding for all or part of the contract.
Future rates. States must give their actuary validated encounter data from at least the three most recent complete years when setting plan rates (42 CFR 438.5). Rides missing from the data can look like rides that never happened. Plans must keep that data for at least 10 years (42 CFR 438.3(u)). For health plans, a chief executive or chief financial officer, or someone reporting to one, certifies the data as accurate, complete, and truthful (42 CFR 438.606).
Matching rides to care. Texas checks each ride against the care it was for:
| Texas rule | What it requires |
|---|---|
| Uniform Managed Care Manual 16.4.1 (version 2.1, April 1, 2024) | Health plans must match at least 85 percent of NEMT encounters to a health care claim, encounter, pharmacy sale, or other insurance record |
| Same chapter | TMHP publishes a monthly matching extract and a quarterly compliance report. The April and October rates count for compliance. |
| Same chapter | A plan under 85 percent sends a root cause analysis within 15 business days of the state’s notice, and can face corrective action plans or liquidated damages |
| Uniform Managed Care Manual 16.4 (version 2.0.1, effective August 1, 2021), section 3250 | Plans confirm each paid ride matches a health care service. If no claim or encounter exists, they should get evidence from the provider that the member kept the appointment. |
Brokers pass that pressure to you. WellTrans’s Indiana provider agreement (revised October 16, 2025) says it pays only when riders actually attend a Medicaid or Medicare covered service, and that you must cooperate with audits confirming attendance. In Kentucky’s regional broker program, 603 KAR 7:080 has the broker report every broker and subcontractor trip with the dollar amount paid for each one-way trip, and makes a broker’s failure to record and report trips on time grounds to end its contract.
Your enrollment has to match the encounter
An encounter names the provider who gave the ride, so the state checks that provider against its enrollment files.
- Oregon. OAR 410-141-3565(3), effective January 1, 2025, requires providers to be enrolled with the Oregon Health Authority, as a fee-for-service provider or an encounter-only provider, before encounter claims are submitted, so the encounter is accepted.
- Ohio. A memo to managed care plans dated March 31, 2026 says unenrolled providers will not be paid and plan encounters will not be accepted. Encounters also reject when the link between the billing and rendering provider was never on file.
- North Carolina. Health plans must make sure their NEMT providers and brokers enroll through NCTracks. A transportation provider can enroll with an NPI or as an atypical provider without one.
See your Medicaid provider number and how to become a Medicaid transportation provider.
How to keep your trips ready for encounter reporting
- Record each leg on its own. North Carolina counts every pickup and drop-off as a separate encounter.
- Log the times the state asks for. Arrival at the pickup, departure, drop-off, and the appointment time. Nevada and North Carolina both use them.
- Use actual miles and full addresses. Street, city, state, and ZIP code for each end of the leg.
- Put the broker’s trip number on every invoice line. It is how the broker ties your ride to its encounter.
- Report cancellations and no-shows the way the broker asks. North Carolina reports canceled trips as denied encounters, so they still leave a record.
- Keep your IDs matched to your enrollment. The NPI or Medicaid ID, taxonomy, and billing and rendering setup on your invoice should match what the state has on file.
- Answer data questions fast. Brokers have their own state deadlines, such as Nevada’s 60 days to correct a disputed file.
- Keep the records. Kentucky’s broker rule requires five years. Your contract or state may require longer. See NEMT trip documentation and the trip log template.
Frequently asked questions
What is the difference between a claim and an encounter?
A claim asks for payment. An encounter reports a service that was already paid for under a managed care contract. You send your claim or invoice to the broker or health plan, it pays you, and it sends the state an encounter for the ride. CMS guidance (updated December 20, 2024) has states report NEMT PAHP encounters in T-MSIS as managed care encounter records, which it also calls dummy records.
Do I submit encounter data myself?
Usually not. Your broker or health plan does. What you send it, the invoice, trip log, times, miles, and addresses, becomes its encounter. Some states still put a duty on you. Kentucky's rule for its regional broker program, 603 KAR 7:080, has each subcontractor, a company that drives trips for the broker, collect and keep encounter data on every trip and keep program records for five years.
Why does my broker ask for exact pickup and drop-off times?
Because the encounter needs them. North Carolina's managed care NEMT policy (amended January 1, 2025) lists the arrival, departure, and drop-off times, the appointment time, and both addresses for every leg. Nevada's broker encounter guide (August 4, 2026) requires the appointment, scheduled pickup, actual pickup, and actual drop-off times for codes A0120, A0130, T2005, and A0080.
What happens if a ride cannot be matched to a doctor visit?
The plan looks for proof. Texas's managed care NEMT handbook has plans confirm that each paid ride matches a health care service, and when no claim or encounter exists, says plans should get evidence from the provider that the member kept the appointment. WellTrans's Indiana provider agreement (revised October 16, 2025) pays only when the rider actually attended a Medicaid or Medicare covered service.
Does encounter data apply in fee-for-service states?
Not in the same way. Encounters come from managed care: health plans, and brokers that a state pays by capitation or by rates other than its own fee schedule to cover only rides. Federal rules call those brokers NEMT PAHPs. CMS says fee-for-service ride arrangements, and brokers that pay at the state's own rates without taking risk, are not reported as managed care in T-MSIS, the national Medicaid data system.