Matlock & Partners← Back to AskMatlock
The Shoulder
sharp-swift-234

Rideshare passenger injury — gap between what insurance "covers" and what I actually owe is massive

Posting anonymously because I'd rather keep my financial stress off my main profile.

Back in the fall I was riding in a rideshare — wasn't driving, just a passenger — when the driver blew through a yellow and got T-boned by an SUV. I walked away thinking I was fine, but about two days later my shoulder and upper back were screaming. Went to urgent care, they referred me to a chiropractor and then a physical therapist.

The rideshare company has passenger injury coverage, so I figured I was in decent shape. Filed the claim, got approved, started treatment. Eight or nine weeks of PT later, I'm doing a lot better physically. Then the bills start arriving and my stomach dropped.

Here's where it gets confusing: there's apparently a third-party medical financing company involved that I did not fully understand when I signed intake paperwork at the PT clinic. Like, I thought I was signing standard patient forms. Now this company is telling me there's a lien on my claim and I owe the difference between what they billed and what the rideshare insurer actually paid — which is a significant gap.

The rideshare insurer keeps saying my treatment was "reasonable" up to a certain point and then just... stopped authorizing sessions mid-treatment. Nobody told me that was happening in real time.

I'm a grad student. I do not have a cushion for a surprise bill this size. A few questions for anyone who's been through something similar:

  • Is this lien situation normal? Did I accidentally sign away my rights somewhere?
  • Can the insurer retroactively decide treatment wasn't necessary after already approving it?
  • Is there any way to negotiate this down or push back on the financing company?

Any help is really appreciated. I feel like I got hurt through no fault of my own and I'm somehow the one getting squeezed.

9replies

9 replies

Most helpful first

0 / 4000 · posted under a randomly assigned handle