What is encounter data, and why do brokers ask for so much trip detail?
Encounter data is the service-by-service record that a Medicaid managed care plan or capitated broker sends the state for everything it covers, including each NEMT trip. Federal rules require it to identify the provider who gave the service, use standard 837 formats, and pass state checks before the state reports it to CMS. That is why brokers insist on complete trip details.
On this page
Where encounter data comes from
When a plan is paid a set amount per member, the state still needs to know what care members actually got. Encounter data fills that gap. Under 42 CFR 438.242, every plan contract must require:
- Data on all services furnished to members, detailed enough to identify the provider who delivered each one.
- Submission to the state at the frequency and detail the state and CMS set.
- Standard formats: the ASC X12N 837 and NCPDP formats, plus the 835 where appropriate.
The state then checks the data and forwards it to CMS. States send their Medicaid files to CMS each month through T-MSIS, the national system that grew out of the older Medicaid Statistical Information System. Under 42 CFR 438.818, federal matching money for plan contracts depends on the state getting that data right.
For a ride, the path runs like this: you complete the trip and send the record to the broker, the broker screens and pays it, then reports it as an encounter to the plan or state.
What North Carolina collects on each trip leg
North Carolina’s managed care NEMT policy is a good look at the detail involved. It treats each leg of a trip as its own encounter and lists the information that must come with it.
| Filled from what happened on the trip | Set when the trip is booked or billed |
|---|---|
| The company that ran the trip, as rendering provider | Trip number, nine characters and unique per encounter |
| Whether the member was picked up | Date the trip was requested |
| Actual miles, or minutes of wait time | Appointment time and scheduled pickup time |
| Arrival and departure times at the pickup | Special needs indicator from the assessment |
| Drop-off time | Trip type (initial, return, or transfer) and leg number |
| Pickup and drop-off street addresses | Pickup and drop-off location types, such as home or dialysis |
| Vehicle type, attendant type, and number of companions | Procedure code, unit type, and place of service |
The policy adds three rules providers feel directly. Canceled trips are reported as denied encounters. Encounters are checked for duplicates by claim number, or by matching billing and rendering provider, member, date, codes, and trip leg. Every NEMT encounter needs an ICD-10-CM diagnosis code, and the state suggests Z76.89. The NEMT diagnosis codes page covers that code.
Why incomplete trips get rejected
Federal rules make the plan responsible for the quality of what providers send it. It must check provider data for accuracy and timeliness and screen it for completeness, logic, and consistency. For example, a leg with no drop-off time, or two legs that look identical, can fail that screen before it ever reaches the state.
Broker contracts build the data collection into daily operations. MTM’s standard agreement, as Pennsylvania posts it, requires vehicles to send location, trip events, and member signatures in real time from an internet-connected device. Trips billed later than 90 days after they were run are not paid, unless MTM’s client sets a different window.
Recording it at the moment it happens
The fields brokers check are easiest to get right when they are captured during the ride. HealthRide’s driver app stamps each step of a trip with the time and GPS miles, takes the rider’s signature on screen, and still works in areas with no cell service. See the driver app.
Frequently asked questions
- How is an encounter different from a claim?
- A claim asks to be paid. An encounter reports a service that a plan already covers under its capitation payment. CMS's national data system files them as managed care encounter records, sometimes called dummy records. Your invoice to the broker is a claim, and the broker turns it into an encounter for the state.
- What happens when encounter data is incomplete?
- The state has to validate encounter data for completeness and accuracy before sending it to CMS. If a state cannot fix data that CMS finds noncompliant, CMS can defer or disallow federal funding on all or part of the plan contract. So plans and brokers screen your trip records for completeness, logic, and consistency before they pay.
- Do NEMT-only brokers have to report encounters?
- Yes, when the state pays them as NEMT prepaid plans. 42 CFR 438.9 applies the health information system and encounter data rules in 42 CFR 438.242 to those brokers, and the state's duty to report encounters to CMS. Brokers hired by health plans feed their data to the plan, which reports it.
- Why does the broker need my NPI or provider ID on each trip?
- Because the encounter has to identify who actually provided the service. In North Carolina, the broker or plan subcontractor is the billing provider on each NEMT encounter, and the transportation company that ran the trip is the rendering provider. A trip record without that ID is incomplete.
