Electronic signatures on NEMT trip logs: what Medicaid and brokers accept

What the law says about electronic signatures

Two laws make an electronic signature as valid as ink for most business records, NEMT trip logs included. The federal Electronic Signatures in Global and National Commerce Act (ESIGN) says a signature or record tied to interstate commerce may not be denied legal effect solely because it is electronic (15 U.S.C. 7001(a)). Its definition is broad: a sound, symbol, or process attached to or logically associated with a record and adopted by a person with the intent to sign (15 U.S.C. 7006(5)). A rider tracing a name on a driver’s phone fits it.

The Uniform Electronic Transactions Act (UETA) does the same job in state law. Section 7(d) of the model act says that if a law requires a signature, an electronic signature satisfies that law. Every state but New York has enacted UETA, as have the District of Columbia, Puerto Rico, and the U.S. Virgin Islands. New York uses its own Electronic Signatures and Records Act, Article 3 of the State Technology Law.

Neither law makes a payer accept your format. ESIGN leaves federal and state agencies free to require that records filed with them follow specified standards or formats (15 U.S.C. 7004(a)). The model UETA lets each state agency decide whether, and how, it will accept electronic signatures (section 18), and between private parties it applies only when both have agreed to deal electronically (section 5(b)). So a NEMT company works under three layers:

1. E-signature law makes the signature valid in principle.
2. The state Medicaid program sets what a trip record must contain and, in some states, the exact form.
3. The broker contract sets how signatures reach the broker and what makes a claim clean.

Read the broker’s provider manual first, because it sets the day-to-day rules your claims are checked against. For every other field on the trip record, see the documentation requirements guide.

What Medicaid programs and brokers accept

Programs differ on three points: whose signature is required, whether a typed or tapped entry counts, and where the record has to go. These current manuals spell it out.

Two differences matter most. New York built its rule around the driver’s attestation, while the others also want a signature from the rider’s side of the trip. And MTM’s standard provider agreement (the copy Pennsylvania publishes is dated January 1, 2023) says the connected device in every vehicle must transmit member signatures in real time, alongside the van’s location and trip events (section 4.B). Outside dispatch software qualifies only if MTM first reviews it and sets up a data connection, which MTM may decline.

Minnesota has a change coming. Laws 2026, chapter 121, signed May 27, 2026, lets records that comply with Minnesota’s EVV statute (section 256B.073) serve as NEMT trip records, provided every required element is in them. It takes effect on the later of January 1, 2027, and the date of federal approval. The EVV guide explains what those systems record.

Riders who cannot sign

A driver never signs the rider’s name. Arizona’s manual allows no exception, including drivers who are family members or caregivers of the rider, and Modivcare’s Mississippi manual bars anyone but the member from signing the member’s name. The programs agree on a set of fallbacks instead:

1. The rider signs with a finger or stylus. Arizona also accepts a fingerprint from a member who cannot write.
2. An authorized person signs their own name. Arizona allows a family member, parent, guardian, caretaker, or escort, who notes the relationship, as in “by J Smith, daughter”. Arizona members under 18 sign for themselves only if emancipated; otherwise a legal guardian signs.
3. Staff at the destination sign. Minnesota accepts the medical provider’s signature certifying the rider arrived. Arizona allows the provider at the appointment to sign when the member travels alone, and Modivcare’s Mississippi manual has drivers ask a facility representative where the ride begins or ends.
4. The driver documents the gap. Indiana’s run sheet carries the words “the patient was unable to sign” plus why. Minnesota wants a note “that signatures were requested and not provided.” Modivcare wants “unable to sign” on the member’s line with the driver’s initials, and the specific reason in the driver’s comments.

Build these as choices in the app rather than free text the driver has to remember. A good exception screen asks who signed and how they relate to the rider, or why nobody could, and saves the answer to that leg. Modivcare’s manual also asks providers to tell the broker about members who cannot sign, so keep a standing note on those riders’ profiles.

What an audit-ready signature record holds

An electronic signature proves little without the data saved alongside it. UETA section 9 says a signature is attributable to a person if it was that person’s act, which may be shown in any manner, including through the security procedure used. In an audit, that proof is the record around the mark. For each trip leg, keep:

• The leg: trip or authorization number, service date, rider name, and both addresses.
• The signer: a printed name captured separately from the drawn signature, and their role (rider, guardian, escort, facility staff).
• The mark: the drawn signature or fingerprint image, not a typed name.
• When and where: a time stamp the system generates, never one the driver types, and the phone’s coordinates at the moment of signing.
• Who collected it: the driver’s own login. Shared logins break the link between a signature and a person.
• The words signed: the attestation text shown on screen. Minnesota’s driver attestation, for example, includes an acknowledgment that misreporting can bring civil or criminal action.
• Exceptions: the reason a signature is missing, entered on the spot.
• History: corrections saved as new entries, with the original kept.

Retention is the other half. ESIGN treats an electronic record as meeting a retention rule only if it accurately reflects the information and stays accessible, in a form that can be reproduced later, for the whole required period (15 U.S.C. 7001(d)). New York’s period is six years, and broker contracts can run longer: MTM’s standard provider agreement asks for 10 years. Keep signed records for whichever required period is longest, and once a year pull a few old legs to confirm you can still export and print them. The broker audit guide shows how reviewers sample those records.

Rolling out electronic signatures in your vans

Moving off paper is mostly setup, followed by a month of close checking. A workable order:

1. Get each broker’s rule in writing. Ask whether they accept signatures from your app, need them through their own app or connection, or want a specific form. Modivcare’s Mississippi manual takes trip logs from the provider’s own software, with a master log in its provider portal for when that software misses required data, while Arizona accepts only its own form.
2. Decide when the signature is taken. Follow the payer. Modivcare’s Mississippi trip log list calls for a member signature at each drop-off. Where the rule is silent, drop-off is the natural point, because the ride has happened.
3. Keep other riders off the screen. The signing screen should show only that rider’s leg. The HIPAA guide covers the rest of phone privacy.
4. Plan for dead zones. The app should save the signature, time, and location on the phone and send them when signal returns, without stopping the driver from finishing the trip.
5. Train the exception flow. Riders who cannot sign come up far less often than routine signatures, so walk drivers through the fallbacks on day one and again after the first month.
6. Review every week at first. Pull legs with missing signatures, signatures captured far from the pickup or drop-off, and the same scribble repeated across many riders. Each one is a coaching conversation now instead of an audit finding later.

Keep a paper fallback anyway. A few copies of your trip log template in each van cover a dead phone, as long as those legs are entered the same day.

Signatures in the HealthRide driver app

In the HealthRide driver app, riders sign right on the phone, and the app keeps working even when there’s no signal. Signatures, GPS miles, on-time records and no-show wait times are saved on every ride, and the trip log prints ready for broker audits.