S9110 and Texas Medicaid RPM Billing, Explained

Remote patient monitoring (RPM) has become a practical way for home care agencies to follow Medicaid patients between visits — and in Texas, the billing for it works differently than the Medicare codes most platforms are designed around. This post walks through the basics of how Texas Medicaid handles RPM so your team has a shared understanding of the pieces involved.

This article is educational, not billing or legal advice. Coverage, rates, and requirements change. Always verify current rules with TMHP and your own compliance team before billing.

What S9110 is

For Texas Medicaid remote patient monitoring, S9110 is the procedure code that represents the monthly RPM service. Rather than spreading the work across several separate Medicare-style codes, Texas Medicaid uses S9110 together with modifiers to describe what actually happened that month — whether a device was just set up, whether monitoring took place, and how much review went into it.

The role of U1–U9 modifiers

Modifiers are the part that makes S9110 specific. They tell the payer which kind of RPM activity a claim represents. In broad terms, the U1–U9 modifiers distinguish things like:

• Setup — the one-time work of onboarding a patient and getting their device running.
• Monthly monitoring — the routine work of collecting and reviewing readings over the month.
• Extended monitoring — months with a higher volume of readings or monitoring activity.
• Review — the clinical time spent reviewing data and managing the patient’s care.

The exact definition tied to each modifier, and the rate associated with it, is determined by TMHP and its fee schedule — not by any single platform. The point for an agency is that the modifier you submit has to match what your documentation actually supports.

Why reading-day and time tracking matter

This is where many RPM programs run into trouble. The modifier you bill is only defensible if you can show the underlying activity. That usually comes down to two kinds of evidence:

• Reading days — how many distinct days the patient submitted device readings during the period.
• Time — how much clinical review and care-management time the team logged.

If those numbers aren’t captured at the source, reconstructing them later is slow, error-prone, and hard to defend in an audit. Capturing them automatically — as readings arrive and as staff work the patient — means the data behind each claim already exists when it’s time to bill.

How a TMHP-focused platform reduces denials

A platform built around Texas Medicaid, rather than retrofitted from Medicare workflows, can line the day-to-day work up with the way S9110 claims are actually structured. In practice that means:

• Generating and routing authorization paperwork in the format TMHP expects, with audit-ready records.
• Tracking reading days and time automatically, so the right modifier is supported by real data.
• Rolling that documentation into bundle exports that pair each claim with the evidence behind it.

None of this replaces a knowledgeable billing team or removes the need to verify current rules. But when the authorization, the monitoring data, and the billing export all come from one connected workflow, there’s far less manual reconciliation — and fewer of the documentation gaps that lead to denials.

If you’re evaluating how to run Texas Medicaid RPM cleanly, the question worth asking any tool is simple: does it capture the reading-day and time evidence your S9110 claims depend on, by default?