Loading...

Heat-Season Remote Patient Monitoring in Arizona: Putting the New Short-Burst RPM Codes to Work

Healthcare IoT

Published by IOT Arizona Research & Editorial Team

Heat-Season Remote Patient Monitoring in Arizona: Putting the New Short-Burst RPM Codes to Work

By September 8, 2026, Maricopa County public health officials had confirmed 150 heat-related deaths for the year, up 97 percent from 76 at the same point in 2025, with hundreds more deaths still under investigation. Yuma County had recorded 26. Emergency physicians in the Valley have warned that the toll may not have peaked, particularly among people with existing health vulnerabilities.

Many of those deaths share a pattern that clinicians recognize: an older adult, often living alone, managing a chronic condition with medications that interfere with the body's ability to handle heat, in a home where the air conditioning has failed or is not being used. The warning signs often build over several days. And until this year, most remote patient monitoring programs were poorly suited to catching them.

This article explains why the 2026 Medicare changes to remote patient monitoring open a practical path for heat-season monitoring in Arizona, how a short-burst protocol could work, and why the most important reading in a heat emergency may not be a vital sign at all.

Why Traditional RPM Programs Missed the Heat Window

Before 2026, the Medicare device supply code for remote physiologic monitoring, CPT 99454, required at least 16 days of data transmission in a 30-day period. That structure favored long-term chronic disease monitoring. A clinician who wanted to watch a heart failure patient closely for a nine-day extreme heat stretch had no clean way to bill for it.

The 2026 Physician Fee Schedule changed that. CMS finalized CPT 99445 for device supply when a patient transmits between 2 and 15 days of data in a 30-day period, paid at the same rate as 99454. It also added CPT 99470 for the first 10 minutes of treatment management time in a calendar month. Industry commentators and billing specialists have noted that these codes were designed with episodic, transitional and short-term monitoring in mind. A heat wave is exactly that kind of episode.

A Quick Reference to the Codes

CodeWhat It CoversKey Rule to Know
99453Initial setup and patient educationNow requires at least 2 days of monitoring to qualify
99445Device supply with data transmission, 2 to 15 days in 30Cannot be billed with 99454 in the same 30-day period
99454Device supply with data transmission, 16 or more days in 30Unchanged; remains the code for longer monitoring
99470First 10 minutes of treatment management in a calendar monthRequires real-time interactive communication; cannot be billed with 99457 in the same month
99457 and 9945820 minutes of treatment management, plus additional 20-minute incrementsUnchanged; use when management time reaches 20 minutes

Coding rules, payer policies and Medicare Advantage or AHCCCS plan requirements vary, so confirm details with your compliance and billing teams before launching a program. This overview is not billing or legal advice.

Who Belongs in a Heat-Season Cohort?

Arizona providers do not need to monitor everyone during a heat warning. The goal is a targeted list of patients at highest risk. Clinical teams typically consider:

  • Adults over 65, especially those living alone or with limited mobility.
  • Patients with heart failure, chronic kidney disease, COPD, diabetes or dementia.
  • Patients taking medications that affect fluid balance or thermoregulation, including diuretics, some blood pressure medications, anticholinergics, and certain psychiatric medications.
  • Patients recently discharged from the hospital during the heat season.
  • Residents of mobile homes or older housing, where cooling failures are more common and indoor temperatures rise quickly.
  • Patients with substance use involvement. Maricopa County has reported that nearly half of this year's heat deaths involved drugs or alcohol, and stimulants in particular raise heart rate and body temperature while dulling awareness of danger.

Designing a Heat-Burst Monitoring Protocol

A heat-season program works best when it is planned before May rather than improvised during the first extreme heat warning. A practical sequence:

  1. Pre-enroll in spring. Identify the cohort, obtain consent, and ship or deliver devices in March or April. Train patients and caregivers while conditions are still mild.
  2. Define the trigger. Activate daily monitoring when the National Weather Service issues an Extreme Heat Warning for the patient's area, or when the local HeatRisk forecast reaches a level your clinical team agrees on.
  3. Choose meaningful measurements. Daily weight is one of the most useful signals, because a rapid drop can indicate dehydration, especially in patients on diuretics. Blood pressure, heart rate and pulse oximetry add context. Thresholds should be set by the treating clinician for each patient.
  4. Review daily and call early. A nurse or care manager reviews readings each morning and contacts any patient with concerning trends. That real-time conversation is clinically important and also required for the treatment management codes.
  5. Escalate with a clear path. Define in advance when a patient is advised to go to a cooling center, when a home visit or welfare check is arranged, and when emergency services are called.
  6. Stand down and document. When the heat warning ends, return patients to their normal care plan and record outcomes for later review.

The Missing Vital Sign: Indoor Temperature

Maricopa County's 2021 heat death report found that one in four heat-associated deaths happened indoors. Of those who died indoors, 86 percent had an air conditioner present, and in three out of four of those cases the unit was not working. That pattern has shaped county heat prevention efforts ever since.

A connected indoor temperature sensor is inexpensive, runs for months on batteries, and can alert a care team when a home crosses a dangerous threshold, often hours before any physiological reading changes. For many high-risk patients it may be the single most valuable device in the home.

There is an important catch. Room temperature is an environmental reading, not a physiologic parameter, so it does not by itself support Medicare RPM billing. Programs usually fund ambient sensors through other channels: health plan care management budgets, social determinants of health initiatives, grants, hospital community benefit programs or partnerships with cooling assistance and AC repair programs. Pairing a billable physiologic program with a separately funded home sensor is a workable model.

Arizona-Specific Hurdles to Plan For

  • Connectivity. Many older patients lack home broadband, and coverage is thin in parts of rural Arizona and on tribal lands. Devices with built-in cellular connections avoid dependence on home Wi-Fi.
  • Power outages. Heat-driven outages and planned public safety power shutoffs in wildfire-prone northern Arizona can disable both cooling and monitoring. Choose devices with battery backup and treat a sudden loss of signal from a high-risk patient as a reason to call.
  • Device delivery in summer. Electronics left in a mailbox or car at 115 degrees can fail. Deliver devices before the heat season or arrange hand delivery.
  • Language and literacy. Bilingual English and Spanish materials and simple, single-button devices improve adherence across many Arizona communities.
  • Privacy and trust. Explain clearly who sees the data, especially for home temperature readings, which can feel intrusive. Consent should be specific and easy to withdraw.

Staffing the Program Without Burning Out Nurses

The hardest part of heat-season monitoring is not the devices. It is the surge in clinical workload that arrives precisely when emergency departments are busiest. A cohort of 300 patients generating daily readings during a ten-day heat warning can overwhelm a care management team that was not planned for it.

Programs that hold up under pressure usually share a few design choices. They set a small number of clear alert rules per patient rather than flagging every out-of-range reading. They use tiered review, with medical assistants or community health workers handling routine check-in calls and escalating to nurses only when criteria are met. They schedule extra coverage in advance for the historically hottest weeks, typically from late June through August in the Phoenix area. And they give patients and caregivers a simple script for what to do on their own, such as moving to the coolest room, drinking water if their clinician has approved it, and calling the care line if they feel dizzy or confused.

It also helps to coordinate with community partners. Cooling centers, area agencies on aging, home health agencies and utility assistance programs already work with many of the same patients. A shared escalation list prevents duplicate calls and makes sure someone actually shows up when a patient cannot be reached.

How to Tell Whether It Worked

Health systems and health plans in Phoenix, Tucson and Mesa considering this model should decide on outcome measures before launch. Useful metrics include heat-related emergency department visits and admissions within the cohort, 30-day readmissions for patients discharged during the heat season, the number of cooling failures detected and resolved, and patient adherence during heat warnings. Comparing enrolled patients with a similar group from the prior season gives a reasonable, if imperfect, picture of impact.

What Comes Next

Several developments could make heat-season monitoring more effective. Integration of weather forecast data directly into RPM platforms would allow automatic activation for patients in affected ZIP codes. Smart thermostats already installed in many homes could, with consent, share indoor temperature data without new hardware. And analytics that combine medication lists, housing data and forecast heat could help care teams prioritize calls on the worst days.

Technology will not solve the structural drivers of heat deaths, including housing instability and aging homes with failing cooling. But for patients already connected to the healthcare system, a short, well-timed burst of monitoring during the most dangerous days of the year is now clinically practical and financially supported. Organizations looking for local technology partners can explore the IoT Arizona company directory.

Related articles

Top