How RPM Reimbursement Codes Apply to Telehealth Vitals Capture

Telehealth platforms have spent years trying to figure out how to bill for the clinical value they deliver beyond the video visit itself. The answer, increasingly, is remote patient monitoring. CMS has been expanding RPM reimbursement codes since 2019, and the 2026 updates added new codes that give providers more flexibility in how they bill. But there's a real gap between knowing the codes exist and actually qualifying for them. That gap gets wider when the vitals data comes from a patient's phone camera rather than a Bluetooth blood pressure cuff.

What follows is a breakdown of the current RPM reimbursement landscape, what changed in 2026, and where camera-based vitals capture fits into the billing framework.

"CMS categorizes RPM as care management services rather than traditional telehealth. This means RPM is not subject to the same originating site or geographic restrictions that apply to other telehealth services." -- Health Recovery Solutions, 2026 RPM Billing Analysis

RPM reimbursement in 2026: what the codes actually pay

CMS restructured RPM billing for 2026 by adding two new CPT codes (99445 and 99470) to the existing framework. The biggest change is that providers can now bill for shorter monitoring periods and less clinical time. For telehealth platforms, this lowers the bar for patient qualification in ways that actually matter.

Here's the full code set as of January 2026:

| CPT code | What it covers | 2026 Medicare national average | Frequency | |----------|---------------|-------------------------------|-----------| | 99453 | Initial RPM setup and patient education | $21.71 | One-time per patient | | 99454 | Device supply and daily data transmission (16+ days/month) | $52.11 | Monthly | | 99445 | Device supply and data transmission (2-15 days/month) | $52.11 | Monthly | | 99457 | First 20+ minutes of treatment management per month | $51.77 | Monthly | | 99458 | Each additional 20-minute management increment | $40.28 | Monthly (add-on) | | 99470 | 10+ minutes of non-face-to-face RPM services by clinical staff | $26.05 | Monthly |

The 99445 code is the one worth paying attention to. Before 2026, providers could only bill 99454 if data was transmitted for at least 16 days in a 30-day period. That's a high bar. Patients forget. Devices die. Apps crash. Prevounce's 2025 billing compliance report found the 16-day requirement was the single biggest reason RPM claims got denied.

With 99445, patients who transmit data for just 2 to 15 days per month are now covered. The reimbursement is identical ($52.11), but the compliance threshold is much lower. A patient who scans their vitals twice a week on a telehealth platform with camera-based capture still generates billable data.

How camera-based vitals qualify as RPM data

The question telehealth CTOs keep asking: does a phone camera count as an RPM "device"?

It depends on how you read the rules. The 2024 Medicare Physician Fee Schedule final rule defined RPM devices as "FDA-cleared medical devices that electronically collect and transmit patient physiologic data." But CMS has also said RPM isn't limited to traditional hardware, and the 2026 proposed rule broadened language around software-based monitoring tools.

The regulatory text is one thing. Operational reality is another. Here's how different vitals capture methods map to RPM billing:

| Vitals capture method | Typical device | RPM code eligibility | Key consideration | |----------------------|---------------|---------------------|-------------------| | Bluetooth blood pressure cuff | Omron, Withings | Clear eligibility under 99454/99445 | Hardware logistics, patient compliance | | Connected pulse oximeter | Masimo, Nonin | Clear eligibility under 99454/99445 | Device cost, shipping delays | | Smartphone rPPG (camera-based) | Patient's own phone | Eligible when integrated with cleared platform | No hardware needed, higher engagement | | Wearable continuous monitor | Apple Watch, Fitbit | Partial eligibility, varies by data type | Consumer device limitations | | Smart scale | Withings Body+ | Clear eligibility under 99454/99445 | Single vital sign only |

Camera-based rPPG captures heart rate, respiratory rate, blood oxygen estimates, and blood pressure trends from a standard smartphone camera. When this data flows through a platform that meets CMS documentation and transmission requirements, it can support RPM billing. The operational upside is hard to ignore: no devices to ship, no returns to process, no "my Bluetooth won't pair" support tickets eating up your helpdesk queue.

Dr. Joseph Kvedar at Harvard Medical School, a former president of the American Telemedicine Association, made this point in a 2024 NEJM Catalyst piece: "The future of remote monitoring depends on reducing friction for patients, and smartphone-native measurement is the logical next step."

The 16-day rule and why 99445 changes the math

The old 16-day transmission requirement under 99454 was a headache for telehealth platforms in a very specific way. If a patient in your chronic care management program misses a few days of readings, you lose the entire month's billing. That's not just lost revenue. It's unpredictable revenue, and unpredictable revenue makes it nearly impossible to build reliable financial projections for RPM programs.

A 2025 American Medical Association analysis found that roughly 30 percent of RPM claims were denied due to insufficient transmission days. Health systems running legitimate monitoring programs were losing reimbursement simply because patients couldn't hit the threshold consistently.

The 99445 code changes this math. A telehealth platform can now design a monitoring protocol where patients scan their vitals two or three times per week and still generate monthly reimbursement. For camera-based vitals, that's close to ideal. Patient opens the app, holds the phone to their face for 30 seconds, data transmits automatically.

Here's what per-patient revenue looks like under different monitoring frequencies:

| Monitoring frequency | Applicable code | Monthly reimbursement | Annual per patient | |---------------------|----------------|----------------------|-------------------| | Daily (16+ days) | 99454 + 99457 | $103.88 | $1,246.56 | | 3x per week (12 days) | 99445 + 99457 | $103.88 | $1,246.56 | | 2x per week (8 days) | 99445 + 99470 | $78.16 | $937.92 | | Weekly (4 days) | 99445 + 99470 | $78.16 | $937.92 |

The reimbursement gap between daily and twice-weekly monitoring is smaller than you'd think. Meanwhile, patient compliance at twice-weekly is dramatically higher. Dr. Sherry Pagoto at the University of Connecticut published a 2025 study in the Journal of Medical Internet Research showing that patient engagement with RPM programs dropped 47 percent when monitoring was required daily versus three times per week. So you're giving up maybe $25/month in potential revenue per patient but keeping far more patients actually enrolled.

Documentation requirements that trip up telehealth platforms

Getting the CPT code right is only part of it. CMS requires specific documentation for each RPM claim, and this is where telehealth companies consistently run into trouble.

For 99453 (initial setup), you need documented evidence that a clinician configured the monitoring tool and educated the patient on its use. For camera-based vitals, that means someone walked the patient through the app, explained what the readings mean, and confirmed the patient can use it on their own. A two-minute tutorial video doesn't count. CMS wants documentation of a live, interactive session.

For the monthly codes (99454, 99445, 99457), you need:

• A qualifying chronic condition documented in the patient's medical record
• Timestamped vitals data for the required number of transmission days
• Clinical staff notes documenting their review and any interventions
• A treatment plan that specifies RPM as part of the care pathway

The time-based codes (99457, 99458, 99470) require clinical staff to log their monitoring time. That doesn't mean a nurse staring at a dashboard for 20 straight minutes. It includes reviewing data, calling patients about abnormal readings, adjusting care plans, coordinating with physicians. But the time must be documented as it happens. Retroactive estimates are a compliance risk.

Healthicity's 2026 telehealth compliance guide flagged RPM documentation as "the most common audit trigger for telehealth programs." Their advice: build documentation requirements into the platform workflow so clinical staff can't skip steps.

How Medicaid and commercial payers handle RPM

Medicare gets all the attention, but Medicaid and commercial payer RPM reimbursement is growing fast. Prevounce's 2026 analysis found more than 40 state Medicaid programs now cover some form of RPM, though coverage requirements vary by state.

Commercial payers have moved slower on standardized RPM reimbursement, but the direction is obvious. UnitedHealthcare, Aetna, and Cigna all expanded RPM coverage in 2025. Blue Cross Blue Shield plans in 12 states added RPM billing codes that mirror the CMS framework.

Multi-payer RPM billing is where the real scale is. A platform that only bills Medicare is missing the commercial and Medicaid populations that often make up the larger share of a health system's patient base.

The catch: each payer has slightly different requirements. Some commercial plans still require FDA-cleared devices specifically. Others accept software-based monitoring but want clinical validation data on top. If you're building RPM into your telehealth platform, you need a payer-by-payer compliance matrix, not a one-size-fits-all approach.

Building the technical infrastructure for RPM billing

Qualifying for RPM reimbursement requires data flows that many telehealth platforms weren't originally designed to support.

The vitals data pipeline needs to:

• Capture timestamped readings with device/method metadata
• Transmit data to a clinician-accessible dashboard within 24 hours
• Count unique transmission days per patient per billing period
• Generate billing-ready reports that map to specific CPT codes
• Maintain audit trails for every data point and clinical interaction

For camera-based vitals through rPPG, the data pipeline is simpler than hardware-based RPM. No Bluetooth pairing to troubleshoot, no device firmware to update, no separate data transmission step. Patient completes a scan and the data flows straight to the platform. Transmission day counter ticks automatically.

Billing integration is where it gets harder. Most telehealth platforms connect to practice management systems or clearinghouses for claims submission. RPM codes need to be generated monthly based on automated eligibility checks: did this patient transmit enough days? Did clinical staff log enough time? Is the qualifying condition documented?

ThoroughCare and Rimidi have both built RPM billing engines that sit between the clinical platform and the claims system. If you don't want to build this in-house, these integration partners handle the billing logic while your platform handles the clinical workflow.

Where camera-based RPM goes from here

CMS keeps loosening RPM requirements. Payers keep expanding coverage. The technology for capturing vitals without hardware keeps getting better. The 2026 code changes weren't an endpoint. They were CMS acknowledging that RPM programs work better when compliance barriers are lower.

The strategic move for telehealth platforms is integrating vitals capture directly into the video visit. A patient joins an appointment, the platform captures their vitals via camera during the first 30 seconds, and that data feeds into both the visit note and the RPM monitoring program. One interaction, two billing pathways.

Companies like Circadify are building the rPPG infrastructure that makes this possible, offering SDK-based vitals capture that telehealth platforms can embed directly into their existing workflows. You can explore integration options at circadify.com/custom-builds.

Frequently asked questions

Can camera-based vitals qualify for RPM reimbursement?

Yes, when the data is captured and transmitted through a platform that meets CMS documentation and reporting requirements. CMS defines RPM eligibility based on the data being physiologic, electronically collected, and transmitted to a clinical team, not on the specific hardware used. Camera-based rPPG that captures heart rate, respiratory rate, and other vital signs through a smartphone camera can meet these criteria.

What changed with RPM billing codes in 2026?

CMS added two new codes: 99445 for data transmission on 2 to 15 days per month (replacing the strict 16-day requirement of 99454), and 99470 for at least 10 minutes of non-face-to-face clinical staff monitoring per month. These changes make RPM billing accessible for patients who don't monitor daily and for programs with lighter clinical touch.

Do commercial insurance plans reimburse for RPM?

Over 40 state Medicaid programs and major commercial payers including UnitedHealthcare, Aetna, and Cigna now cover RPM services. Coverage specifics vary by payer and state. Some plans mirror CMS CPT codes exactly while others have additional requirements around device clearance or clinical protocols.

What documentation is needed for RPM billing?

Each RPM claim requires a documented qualifying chronic condition, timestamped vitals data for the required transmission days, clinical staff notes showing review and intervention, and contemporaneous time logs for the time-based codes (99457, 99458, 99470). The initial setup code (99453) requires documentation of a live interactive patient education session.