Remote Patient Monitoring Without Alert Fatigue: Alert Design and the Billing Rules Behind It

Alert fatigue sets in when an RPM program sends care teams more alerts than they can act on. How to tier and route alerts, how the Medicare RPM codes and rules should shape the design, and which metrics show fatigue early.

In short

  • Remote patient monitoring alert fatigue happens when care teams get more alerts than they can act on, so they start to miss the ones that matter.
  • AHRQ's patient safety guidance points to the main fixes: tier alerts by severity, make only severe alerts interruptive, remove alerts with no clinical consequence, and tailor alerts to the patient.
  • Medicare pays for RPM through codes for setup, device supply and treatment time, with rules on days of data, real-time communication and who can bill, so build those rules into routing and worklists from day one.

Remote patient monitoring (RPM) alert fatigue happens when a program sends care teams more alerts than they can act on, so people start to tune all of them out. The fix is design: tier alerts by severity, interrupt people only for the severe ones, set thresholds per patient, and send non-clinical problems, such as a missed reading or a dead battery, to the patient or support team instead of the nurse. The Medicare billing rules for RPM, which pay for setup, device supply and staff time, should shape that design from the start, because they decide what your team must track every month.

What is alert fatigue, and why does RPM make it worse?

AHRQ's patient safety network describes alert fatigue as busy clinicians becoming desensitized to safety alerts and, as a result, ignoring or failing to respond to warnings. The numbers it cites show the scale. In one 2014 study, physiologic monitors in 66 adult ICU beds at an academic hospital produced more than 2 million alerts in one month, about 187 per patient per day. A Veterans Affairs study found primary care clinicians receiving more than 100 alerts per day.

RPM adds its own pressures. Readings come from homes, taken without supervision, on consumer-style devices. A cuff placed wrong or a scale on a soft rug produces an out-of-range number that looks clinical but is not. Data arrives at all hours. And enrollment can grow faster than the team reviewing it. A design that alerts on every out-of-range value works for ten patients and fails at five hundred.

How does Medicare pay for remote patient monitoring?

CMS describes remote monitoring as three components, each building on the one before: patient education and device setup, device supply, and treatment management, meaning review of the data to improve outcomes. The CPT codes follow that structure:

  • 99453: initial setup and patient education on the device.
  • 99454: device supply with data transmission. CMS's 2021 rule requires 16 days of data in each 30 days to bill 99453 and 99454.
  • 99457: the first 20 minutes of treatment management in a calendar month, which requires interactive communication with the patient or caregiver.
  • 99458: each additional 20 minutes of treatment management.
  • 99091: the fifth RPM code CMS clarified in its 2021 rule. Check its current descriptor before you combine it with the others in one month.

For 2026, the CPT code set added codes for shorter monitoring periods. CMS's December 2025 booklet says data must be collected for 2 to 15 or 16 or more days out of 30, depending on the code descriptor, and that this day count does not apply to the treatment management codes. Check the current CPT descriptors and your Medicare Administrative Contractor for the exact codes and their rules before you build billing logic around them.

Which rules does an RPM program have to follow?

CMS's December 2025 Telehealth & Remote Monitoring booklet lists the main requirements:

  • RPM requires an established patient relationship.
  • Only physicians and non-physician practitioners eligible to provide evaluation and management services can bill remote monitoring.
  • The patient must have an acute or chronic condition, and monitoring must be medically reasonable and necessary.
  • Only 1 practitioner can bill remote monitoring for a patient in a 30-day period.
  • You cannot bill remote physiologic monitoring and remote therapeutic monitoring together.
  • Patient consent is required at the time RPM services are provided.
  • Data must be collected electronically and uploaded automatically to a secure location, from a device that meets the FDA definition of a medical device.
  • Auxiliary personnel can provide the services under the general supervision of the billing practitioner.
  • Treatment management needs at least 1 real-time interactive communication with the patient or caregiver in the calendar month.

The CY 2021 rule defines that interactive communication as a conversation that occurs in real time, and says the 20 minutes for 99457 and 99458 can include time spent on care management as well as the conversation itself.

What changes in 2027?

The CY 2027 Physician Fee Schedule final rule, displayed on November 4, 2026, finalized three remote monitoring changes as proposed. RTM is limited to established patients. Practitioners reporting RPM or RTM must furnish a separately reportable initiating visit in association with the start of services. And CMS updated how these services are valued. A proposal to pay only when the work is done by clinical staff employed by the practice was delayed to January 1, 2029. A proposal to bundle the RPM and RTM codes into four new G-codes was not finalized.

Payment amounts change every year and vary by locality, so do not hard-code them. Look up each code in the CMS Physician Fee Schedule Look-Up Tool for your MAC locality, and store rates as data your billing team can update.

How should the billing rules shape alert design?

Each rule above turns into a design decision. Getting these right removes a whole class of alerts from clinicians' screens.

  • Treat missing data as a patient task. Count data days per patient per 30-day period. After a gap, remind the patient first. Escalate to staff only when the gap puts the month's day count at risk or the patient does not respond.
  • Device problems go to support. A device that stops syncing, a low battery or a failed pairing should open a support ticket and stay off the nurse's screen.
  • Time has to be captured as it happens. Log review and call time per patient from the actions staff take in the system, and show progress toward each time threshold, so nobody reconstructs minutes at month end.
  • Interactive communication needs a worklist. Show which patients have had no real-time conversation this month, well before the month ends.
  • One billing practitioner per patient per 30 days means ownership must be explicit. Every enrolled patient needs one named responsible practitioner in the data model.

Ownership also cuts noise. In the systems we build, each clinician sees only their own patients. A worklist limited to your own panel is shorter, and every item on it is something you are responsible for.

What does a good alert tier look like?

AHRQ's suggestions are to tier alerts by severity, make only the most severe ones interruptive, remove alerts with no clinical consequence, tailor alerts to patient characteristics and clusters of physiologic signs, and apply human factors design to format, content, legibility and color. For RPM, that becomes four tiers:

  • Critical: a confirmed value outside the patient's critical range set by their clinician. Interruptive, sent to a named person, with a time limit to acknowledge and automatic escalation if nobody does.
  • Review: a trend that crosses a threshold over several readings, such as weight rising over a few days. Goes to the worklist for same-day review, never interruptive.
  • Informational: a single out-of-range reading that recovers on the next measurement. Shown in the patient summary without a notification.
  • Technical: no data, device offline, low battery. Goes to the patient and the support queue, and clinicians never see it.

How do you set thresholds per patient?

  • Let the responsible clinician set ranges for each patient, starting from a protocol default, and record who changed a threshold and when.
  • Ask for a repeat measurement before raising an alert on a single high or low value, with instructions on how to measure correctly.
  • Suppress duplicates. One open alert per patient per issue, updated as new readings arrive, instead of a new alert for each reading.
  • Combine signals where the protocol allows, for example weight together with symptoms reported in a short questionnaire.
  • Review thresholds on a schedule. A range set at enrollment may not fit the patient three months later.

Which metrics show alert fatigue early?

Measure alert load the way you measure clinical outcomes, every week, by team:

alerts_per_patient_day = alerts raised / (enrolled patients x days)
actionable_share       = alerts that led to a documented action / alerts raised
time_to_acknowledge    = median minutes from critical alert to acknowledgment
unacknowledged         = critical alerts past their time limit / critical alerts
dismiss_share          = alerts dismissed without action / alerts raised
data_day_compliance    = patients meeting the month's day count / enrolled patients

A falling actionable share with a rising dismiss share is the early sign. It means the team is learning that most alerts do not matter. Fix it by removing or retiering alerts; asking people to try harder leaves the noise in place.

What should you test before launch?

  • Replay realistic data, including bad readings and missed days, through the rules for a full 30-day cycle and count the alerts each role would get.
  • Sit with the nurses and clinicians who will use the worklist and watch them work through a simulated day.
  • Check that every billable minute and data day is captured without manual entry.
  • Confirm the escalation path works at night and on weekends.

Security comes before patient data flows. We sign a BAA before we touch PHI and run penetration tests before launch.

Planning or fixing an RPM program?

Talk to an engineer at Onix Health about your alert rules, your worklists and your billing logic. We offer a 5-day free technical audit that ends with a written report, so you can see where the noise comes from before you change anything.