NewMissing Records Detection: flags every visit, provider, and date missing from the file. See how →
  1. Solutions
  2. Case types
  3. Uber and Lyft accidents
Rideshare accident cases

In a rideshare crash, the minute decides the policy. The chart decides the rest.

Coverage turns on whether the app was off, on, or carrying a passenger. Medrecords AI lines up the trip record with the injury chronology, so the crash time, the coverage period and the treatment all sit on 1 timeline. Every entry links to its page.

  • HIPAA, under a BAA
  • SOC 2
  • 100 pages a minute
  • First case is free on us
1 crash, 2 recordstap a point
Trip record
Medical file
21 Mar 2025Insurer letterTrip record

Claim opened under the TNC policy. Coverage period stated as "app on, waiting".

p. 15conflicts with p. 4
Illustrative case. The people, trip, dates and pages are fictional.
$1Mcoverage

Minimum TNC liability coverage in California once a ride is accepted and during the trip.

Cal. Pub. Util. Code §5433(b)
$50Kper person

The California minimum when the app is on but no ride is accepted.

Cal. Pub. Util. Code §5433(c)
3app periods

Off, waiting, and matched or carrying a passenger. Each can land on a different policy.

Cal. Pub. Util. Code §5433
100pages a minute

How fast Medrecords AI reads the file.

Medrecords AI
Where rideshare cases turn

6 places the carrier looks first. The chronology gets you there before they do.

A rideshare case is a car case with a coverage fight stacked on top. These are the points where the trip record and the medical file meet, each flagged with the page behind it.

Trip record

The period at the crash time

Log-on, acceptance, pickup and drop-off times set beside the crash time from the police report, so the coverage period is a fact on the page.

Cal. Pub. Util. Code §5433
Trip record

The insurer's version

Every coverage position the carrier states in writing, set against the trip log. A mismatch is flagged with both pages.

flagged
Trip record

Who was in the car

Driver, passenger, or someone in the other vehicle. The injury chronology is built for the person you represent, with the role on every page.

cited
Medical file

The first medical note

How the ED described the mechanism, the seat position and the complaints, quoted with the time of the note.

cited
Medical file

The gap in treatment

Every interval over 30 days between visits, with both dates and the reason if the chart gives one.

flagged
Both

The records that never arrived

The trip receipt, the insurer's coverage letter, the imaging a referral ordered. Listed with the page that points to each one.

missing-records list
Sample output

What comes back: the trip record and the medical file, every line cited.

DateSourceFindingPageFlag
8 Mar 2025, 22:51Trip logDriver accepts a ride request. Period 2 begins.p. 4period 2
8 Mar 2025, 23:02Trip logPassenger picked up. Period 3 begins.p. 4period 3
8 Mar 2025, 23:09Police reportT-bone collision at an intersection. Rideshare vehicle struck on the passenger side.p. 9crash time
21 Mar 2025Insurer letterClaim opened under the TNC policy. Coverage period stated as "app on, waiting".p. 15conflicts with p. 4
Fictional case built for this page. Real output carries the same columns, with every page linked to the source PDF.
How it works

Send the crash file. Get 1 timeline back.

What you send

  • The police report and any trip logs or receipts you have
  • Insurer correspondence and coverage letters
  • ED, treating and therapy records
  • Billing ledgers and itemized statements
  • Any format: PDFs, scans, faxes, phone photos

What you get

  • A timeline of the trip record against the crash time
  • Coverage positions in writing, flagged where they conflict with the log
  • A page-cited injury chronology from the scene forward
  • Every treatment gap over 30 days, with both dates
  • A list of records the file refers to but does not contain

We lay out the record. Coverage and causation stay with you.

We place what the trip log, the police report and the treating records say on 1 timeline, with pages. We do not decide which policy applies, interpret state TNC law or say the crash caused the injury. Those belong to you and your experts.

HIPAA, under a signed BAAEvery file is handled under our Business Associate Agreement.
SOC 2Encryption in transit and at rest, and PHI access logging on every event.
Never trains a modelYour records never train any AI model, ours or anyone else’s.
Deleted after deliveryFiles are deleted 30 days after delivery, with an audit log of every access.
Questions

Uber and Lyft accident record review, answered.

Do you decide which insurance policy applies?

No. We put the trip times and the crash time on 1 timeline with pages, so the coverage period is easy to see and argue. Which policy applies under your state's law is your call.

Can you read Uber or Lyft trip data?

If you have it as a document, yes: trip receipts, driver logs and insurer letters are read like any other record. We do not pull data from Uber, Lyft or any insurer.

Does this work for passengers, drivers and people in the other car?

Yes. The chronology is built for the person you represent, and every entry is tied to that person, so records for another occupant never leak into the file.

Do you retrieve records from providers?

No. Medrecords AI does not retrieve records from providers or facilities. You bring the records you already have, and review starts in minutes from upload.

Related case types

Send us 1 rideshare file. The first case is free on us.

Book a short demo. After it we open trial access on one of your own cases, the first one free on us, with the timeline back page-cited.