Part of The Revenue Model Sets the Strategy
CPT Code / RPM Reimbursement
Revenue flows through CPT billing codes tied to remote patient monitoring.
01
How it works
Revenue is generated through CPT billing codes tied to remote patient monitoring services. Healthcare organizations enroll eligible patients, provide connected devices that transmit physiologic data, and bill payers for qualifying services.
While RPM was originally designed around ongoing chronic disease management (diabetes, heart failure, COPD, hypertension), the current code structure also supports short-duration acute and transitional monitoring, including post-discharge monitoring to prevent hospital readmissions.
The current code structure provides two tiers of device supply and data transmission billing. The new codes were created by the AMA in the CPT 2026 code set, with CMS finalizing payment for them in the CY 2026 Physician Fee Schedule final rule. CPT code 99445 covers 2 to 15 days of device data transmission in a 30-day period, while CPT code 99454 covers 16 to 30 days. The two codes are mutually exclusive within a 30-day period, and both are currently reimbursed at the same rate. For clinical staff management, CPT code 99470 covers 10 to 19 minutes of qualifying interaction per month, while CPT codes 99457 and 99458 cover 20-minute increments; here too, 99470 and 99457 cannot both be billed in the same calendar month. Initial device setup and patient education are billed under 99453 as a one-time charge, which now requires at least 2 days of monitoring to qualify for reimbursement. Note that the device codes run on a rolling 30-day period while the management codes run on the calendar month, so the two families don't share a billing window. In 2026, CMS valued the supply codes against outpatient hospital cost data rather than practice-submitted invoices, on the reasoning that the cost of supplying a device doesn't change with the number of days it transmits. The CY 2027 rule revalues them against the self-measured blood pressure codes (see what the CY 2027 rule changes, below).
The 2026 changes are worth noting because many practitioners learned RPM billing under the prior structure, where each code family had its own all-or-nothing threshold: 16 days of device usage gated the device supply code, and 20 minutes of clinical interaction gated the management code, each billed independently. A practice could bill for device supply without any management minutes, and vice versa, but anything below either threshold generated nothing for that code family. The current structure eliminates those cliffs, allowing organizations to bill for shorter monitoring periods and briefer clinical interactions.
The digital health company's revenue may come from a platform license or per-patient fee charged to the healthcare organization, or through a revenue share on the CPT reimbursements the organization collects. In a revenue share model, the digital health company's revenue is directly tied to billing volume, making CS responsible not just for platform adoption but for maximizing patient enrollment, usage threshold compliance, and billing capture.
02
Why the Engagement Gate matters here
The Engagement Gate is the threshold a program has to cross before it produces value for anyone: enough of the intended users doing enough of the intended behavior, for long enough to count. What varies by model is how fast a closed gate shows up in the numbers, and who has to change behavior to open it. The full treatment sits on the Engagement Gate page.
This is the model where end-user engagement has the most direct, immediate impact on revenue. Unlike the other models in this framework, the revenue impact is instantaneous rather than a lagging indicator reviewed at a renewal that is a year or more away. Every month, every patient either generates a billable event or doesn't, and the revenue either flows or it doesn't.
Because the 2026 code structure reimburses equally for 2 to 15 days and 16 to 30 days of device usage, the financial threshold for billing has dropped. A patient who uses their device 5 days in a month now generates the same reimbursement as a patient who uses it 25 days. This means the short-term revenue signal and the clinical value signal have decoupled. Revenue can look healthy even when engagement is minimal.
It's worth being precise about where that parity sits, because it doesn't run across the whole code set. It sits on the device side only. Above the two-day floor, more device days don't produce more device supply revenue. The management codes work differently: 99470 was finalized at roughly half the value of 99457, so shorter clinical interactions pay proportionally less. Effort and reimbursement are still aligned there. The decoupling problem is specific to device supply and transmission, which happens to be exactly where patient engagement lives.
Same payment
This creates a trap worth recognizing. In RPM under the current structure, low-threshold billing can mask clinically insufficient engagement. The billing looks fine at 5 days of usage. But the clinical data generated from 5 days is far less actionable than 25 days. The clinical outcomes that justify program renewal, expansion, and advocacy require sustained, meaningful engagement, not just enough device usage to trigger a billing code.
The revenue pressure on CS therefore shifts from maximizing device days to protect billing to maximizing device days to protect clinical outcomes that justify renewal. If clinical staff don't document qualifying interactions, they cannot bill 99457, 99458, or the shorter-duration 99470. CS isn't just supporting revenue in this model. CS is the revenue engine. But the engine now runs on two fuels: billing compliance (which has gotten easier) and clinical outcome delivery (which hasn't).
03
The objection: whose problem is shallow use?
A practice manager running on thin administrative margin can look at the decoupling described above and see something other than a trap. Full device supply reimbursement from a patient who transmits twice a month is the best margin in the program. On that reading, a CS team arriving to push the panel toward 25 device days is asking clinical staff for materially more work at identical device supply revenue, and introducing friction into an account that was financially satisfied.
That objection deserves a real answer, partly because it uses this framework's own logic. If value is defined by each stakeholder on their own terms, and the administrator's terms are margin, then shallow use is a win by the framework's own standard.
Three things hold anyway, and none of them require an appeal to clinical idealism.
Durability. A patient panel billing the short-duration code at near-universal rates is a visible utilization pattern, and it sits on a code barely a year old. New codes build a utilization record before anyone revisits whether the original valuation was right, and the 2026 device supply rates were set against outside hospital cost data that gets refreshed rather than fixed once. That is an observation rather than a prediction about what CMS will do: a margin resting on a new threshold used at its floor is less durable than one resting on a settled code. That's a financial argument, and it belongs in front of the administrator rather than the clinician.
Defensibility. RPM claims rest on medical necessity and on a provider actually using the transmitted data. Two readings a month cannot support a clinical decision. When the ordering provider has nothing actionable to act on, the documentation supporting the claim thins, and that exposure sits with the practice rather than with the vendor.
Referral volume. The administrator is satisfied. The provider receiving unusable data stops enrolling new patients. The patient seeing no benefit stops transmitting. The program doesn't fail on margin, it fails on referral volume, and it fails quietly enough that the financial dashboard shows nothing until enrollment has already stalled. Across this framework, the contract unravels at the weakest link, and the stakeholder who's satisfied here isn't the one generating the patients.
There's also a structural point that gets missed. The parity that creates this situation exists only on device supply. On the management side, deeper engagement produces more documented interaction time and more billable management minutes at proportionally higher value. The incentive to drive depth has moved to a different code family rather than disappearing.
And the objection carries different weight depending on the payment environment. In a capitated or ACO practice, device supply revenue isn't the point at all, and a panel transmitting twice a month produces no cost avoidance to speak of. The argument for depth there is straightforward, because the buyer's economics already require it.
What's fair to concede is this: in a pure fee-for-service setting, with an administrator clearing good margin on a low-touch program, a CS team pressing hard for engagement depth without connecting it to durability, defensibility, or referral volume is optimizing vendor metrics against a content customer. The case for depth is real, but it is conditional, and it has to be made in the buyer's currency rather than asserted as a general principle.
04
Stakeholder value drivers and KPIs
| Stakeholder | What they care about | Value drivers | KPIs |
|---|---|---|---|
| Clinic administrators / practice managers | Revenue impact and financial return on program investment | CPT reimbursement flowing; claims processed and paid; revenue generated vs. collected; minimal claim denials | Revenue per enrolled patient; CPT claims submitted vs. paid; denial rate and denial aging; eligible patients enrolled (%) |
| Providers (MDs, PAs, NPs, nurses) | Patient adherence, clinical outcomes, minimal workflow disruption | Improved patient outcomes; low workflow friction; visibility into patient adherence | Avg. time to clinical target; patient adherence rate (days active/30); provider login frequency; prescription/enrollment rate per provider |
| Billing / RCM staff | Billing accuracy, clean claims, documentation compliance | Pre-built charge capture workflows; denial rate minimization; accurate documentation trail; correct code selection between short-duration and standard codes | First-pass claims acceptance rate; charge lag time (days between service and claim submission); days in A/R for RPM claims; code selection accuracy (99445 vs. 99454) |
| Patients / members | Feeling better, simplified condition management, easy experience | Tangible health improvement; simple daily routine; responsive support | Device usage rate (days/month); patient-reported outcomes; 30/60/90-day retention rate; support ticket volume |
| CS team (internal) | Portfolio health, revenue protection, scalable operations | Proactive account visibility; early warning on at-risk accounts; engagement depth beyond billing thresholds | Customer health score; net revenue retention; time-to-value (onboarding to first claim); billing eligibility rate (patients meeting the billing threshold / patients enrolled); avg. device days per patient |
A note on KPIs in digital health. In many cases, CS teams can't access the direct outcome data that proves value to stakeholders. Claims data lives with the payer. Clinical outcome trends live in the EHR. Cost savings calculations require actuarial analysis the vendor doesn't control. This means CS must build signal systems using proxy KPIs: metrics that are accessible to the CS team and correlate with the outcomes stakeholders care about. A drop in device usage days this month predicts lost billing revenue next month. A decline in provider login frequency predicts a drop in documented interactions, which predicts unbillable patients. The KPIs in the table above include both direct outcome metrics and the proxy signals CS teams can actually track day to day. The distinction matters because in digital health, the metrics a CS team can see are often two steps removed from the result the stakeholder cares about.
What CS can see
App usage, device days, provider logins
Where the evidence lives
Payer claims, EHR, actuarial analysis
What the stakeholder cares about
Clinical outcomes, savings
Dotted connections mark the gaps in direct access. A drop in device days this month predicts lost billing revenue next month.
A note on engagement depth vs. billing eligibility. Under the current code structure, it is tempting for CS teams to track "percentage of patients who met billing threshold" as a primary KPI. Because the threshold is now as low as 2 days, this metric will trend toward 100% without reflecting whether patients are actually engaging enough to produce meaningful clinical data. CS teams should track average device days per patient as the primary engagement metric, with billing eligibility rate as a secondary financial metric. That metric only reads as engagement once device logistics are ruled out, since a device that shipped late, never paired, or sits in a coverage dead zone produces the same zero as a patient who stopped using it. The gap between the two shows how much of the patient panel is generating revenue without generating clinical value. What that predicts depends on the buyer's payment environment. Under capitation or an ACO arrangement it's an immediate threat to the value story, since device supply revenue was never the point. Under fee-for-service it doesn't touch this period's revenue, which is why it goes unnoticed until it surfaces as stalled enrollment and thinner claim defensibility.
05
How the buyer's payment environment shifts the value story
At its core, the RPM model sits on the "generating revenue" side for most buyers: provider organizations are creating new reimbursement revenue they wouldn't have without the program. The stakeholder table above assumes that context, provider organizations billing Medicare. But the orientation flips entirely when the buyer operates under capitation.
One remote patient monitoring program
The buyer's payment environment changes the value story. An ACO shared savings arrangement sits on the cost side with the plan.
Fee-for-service Medicare
The 2026 code changes make the financial case for RPM programs stronger and easier to demonstrate. The lower threshold means fewer patients fall into the "no revenue generated" category, which improves the program's overall financial return during ramp-up periods when engagement is still building. That makes it tempting to present billing volume as proof of program success, and that temptation is worth resisting. The QBR conversation should still center on clinical outcomes and engagement depth, with billing metrics as supporting evidence of financial sustainability.
Medicare Advantage (capitated)
RPM shifts from a revenue generator to a cost-avoidance tool. The MA plan receives fixed payments from CMS and is at risk for total cost of care. The QBR conversation moves from "how much revenue did we generate from CPT codes" to "how many ER visits and hospital readmissions did we prevent, and how is our quality performance affecting Star Ratings." Star Ratings matter because they directly affect CMS bonus payments, which means even under capitation, RPM has a revenue-generating component through quality measure improvement.
Hospital readmission reduction is one of the most financially compelling RPM use cases under capitation, and the 2026 code changes make it more practical. CMS penalizes hospitals for excessive 30-day readmissions across conditions including heart failure, pneumonia, COPD, and hip/knee replacement through the Hospital Readmissions Reduction Program. A patient discharged after a heart failure episode who is monitored via RPM for 7 to 10 days post-discharge can generate the same billing as a chronic patient monitored for 25 days, while also helping the plan avoid a readmission. The hospital has its own reason to care. Beginning with the FY 2027 program year, CMS added Medicare Advantage beneficiaries to the six Hospital Readmissions Reduction Program measures, so MA readmissions now count toward the readmission rate a hospital is penalized on. That gives an MA plan and its network hospitals a shared interest in the same post-discharge window, which is a different conversation than a plan asking a hospital for a favor. For CS teams, this means the value story for MA buyers should explicitly include readmission prevention as a quantifiable outcome, with tracked metrics like 30-day readmission rates for monitored versus unmonitored patients.
The 2026 code changes have a further strategic implication for MA buyers beyond readmission reduction. The lower monitoring threshold makes it financially viable to extend RPM into other acute and transitional care episodes: medication titration, temporary condition flare-ups, post-surgical recovery for procedures beyond the readmission penalty list. This expands the eligible patient population considerably. CS teams can now help MA buyers build a broader enrollment case: "which patients across chronic, acute, and transitional care would benefit from monitoring?" rather than limiting enrollment conversations to patients with ongoing chronic conditions. A broader monitored population strengthens the cost-avoidance case at renewal because more clinical interventions can be documented and attributed to the program.
ACO shared savings arrangements
The primary success metric becomes total cost of care reduction for attributed patients. The ability to do targeted, short-duration monitoring around high-risk episodes (hospital discharge, medication changes) without committing to 30-day chronic monitoring creates a new lever for reducing total cost of care. Post-discharge readmission prevention matters most here: readmissions are one of the largest drivers of total cost of care for attributed patients, and short-duration RPM monitoring during the critical 7 to 14 day post-discharge window directly targets the highest-cost events. CS can build a case for episodic RPM layered on top of chronic RPM, which wasn't financially viable under the prior threshold structure. CS must understand attribution rules and help target enrollment toward high-risk patients who represent the greatest cost-savings potential. QBRs require longer lookback periods (12 to 18 months) to demonstrate savings.
06
Real-world example
At one digital therapeutics company operating entirely on a revenue share model, a large account had enrolled 200+ patients and showed strong early adoption. But revenue was running 40% below projections. The investigation revealed that patients were using the app consistently and the device data transmission codes were being billed successfully. The gap was in the provider interaction codes: clinicians were reviewing patient data and making clinical decisions, but they weren't documenting the qualifying interactions required to bill for management services. The billing department didn't realize those codes were available to them. After creating documentation templates, training providers on the revenue impact of their time, and working with the EHR administrator to add workflow shortcuts, revenue increased 65% within two months with the same patient panel. The clinic administrator became an active advocate, and the account expanded to additional locations.
Under the current code structure, this type of revenue leakage becomes both easier to prevent (because shorter interactions are now billable through 99470) and harder to detect (because the lower device threshold means billing looks healthier even when provider interaction codes are being missed). CS teams should monitor both device transmission billing and clinical management billing separately rather than treating "total RPM revenue" as a single metric.
CS in RPM models isn't about software adoption metrics. It's about understanding billing requirements, identifying where revenue is being left on the table, and removing friction in the workflows that enable compliant billing. Under the 2026 code structure, it's also about recognizing that billing success alone no longer signals clinical success. The most dangerous accounts are the ones where billing looks healthy, engagement is shallow, and the clinical outcomes that justify renewal aren't materializing. When revenue metrics decouple from engagement and outcomes, the renewal is at risk long before anyone sees it coming.
07
What the CY 2027 rule changes
CMS finalized the CY 2027 Physician Fee Schedule on November 4, 2026. Three of its decisions land on this model, and they take effect January 1, 2027.
An initiating visit before billing begins. Billing for RPM can't start until the practitioner has furnished a separately reportable visit, in person or by telehealth, where remote monitoring was discussed. There is no deadline between that visit and the start of monitoring, and no exemption, including for ACO patients. Patients already being monitored before January 1, 2027 are grandfathered. For the Engagement Gate, this puts a clinical encounter in front of activation. A patient the program has reached can't be activated into billable monitoring until a provider has seen them. The funnel gains a step the partner doesn't control, and the enrollment number that matters becomes initiating visits completed, not devices shipped.
Device values come down, as the durability argument above expected. CMS revalued setup (99453) and both device supply codes (99445, 99454) against the self-measured blood pressure codes, on the view that the devices were overvalued and the cost data behind them was thin. The cuts phase in over 2027 and 2028, because a single year's reduction is capped at 19 percent. All 19 remote monitoring codes go back to the AMA's valuation committee in January 2027, so the device side may move again. The management codes kept their clinical staff costs, so the incentive to drive depth stays where the 2026 structure put it. Device revenue at the two-day floor was the least settled number in the program, and it moved first.
Employed staff from 2029. Starting January 1, 2029, RPM can be billed only when the clinical staff doing the work are direct employees of the practitioner or the practice. Contracting out ends then. Through 2028 nothing changes beyond the existing supervision rules. For partners whose own clinicians deliver the management minutes, this is the clause to read first, and any contract running past 2028 should settle now who employs the staff who bill 99457, 99458, and 99470.
08
Looking ahead: the CMS ACCESS model
What it is. CMS's ACCESS model (Advancing Chronic Care with Effective, Scalable Solutions), which launched July 5, 2026 as a 10-year voluntary model, signals where payment for chronic care is heading. ACCESS introduces recurring outcome-aligned payments for technology-supported chronic care, essentially combining RPM-style infrastructure with VBC-style payment logic. The mechanics matter here: ACCESS is a parallel participation track, not a payment structure a provider flips existing RPM patients into. Participating organizations enroll beneficiaries into one or more of four condition tracks: early cardio-kidney-metabolic, cardio-kidney-metabolic, musculoskeletal pain, and behavioral health. The first two split the metabolic population by stage, and a beneficiary can't sit in both at once.
How it pays. Payment isn't a simple monthly fee. Participants receive roughly half the annual outcome-aligned payment in quarterly installments, with the rest withheld and reconciled after twelve months against two tests: whether enrolled patients hit their clinical targets, and whether they avoided duplicative services for the same condition elsewhere in Medicare. That second test reduces payment rather than barring participants from billing other services. The cash flow shape should look familiar from the Value-Based / Outcomes-Based model. Meanwhile the patient's regular physicians continue billing traditionally, and can collect a new co-management payment of roughly $30 per service for reviewing an ACCESS care update and documenting a coordination action, without needing to join the model themselves.
Who's in it. Organizations already running RPM programs bring relevant infrastructure and clinical workflows, but the launch cohort includes more than 150 accepted organizations, many of them digital-native companies that have never served Medicare beneficiaries, so incumbency is not a moat.
For CS leaders, ACCESS reinforces the framework's core argument: the same product and the same patient population can sit under fundamentally different payment structures, and the CS motion must adapt accordingly. An organization managing hypertensive patients through RPM under fee-for-service billing today may find itself competing with, partnering with, or becoming an ACCESS participant serving that same population under outcome-aligned payments. The patients don't change. The engagement requirements don't change. But the value story, the measurement burden, and the financial risk profile shift dramatically.
ACCESS launched with its first cohort in July 2026, so there are no operational track records yet. It is an early read on how CMS intends to connect technology-enabled care delivery to outcomes-based payment at scale.
09
Where to go next
The Engagement Gate page carries the full treatment of the threshold this page keeps returning to, including the lag comparison across all five models and the rules for reporting an engagement rate honestly. The other four model pages follow the same shape as this one: how the model works, how the buyer's payment environment shifts the value story, the stakeholder value drivers, and an example drawn from practice. The hybrid page maps contract structures instead, since a hybrid inherits its stakeholders from the models it combines.
The three buyer lens pages come at it from the other direction, covering how pharma, health plans, and employers each define value and what each one accepts as proof.
Take the working structures with you
The Field Kit pulls the framework's durable layer out into structures built for use rather than reading: the identify-your-model diagnostic, blank stakeholder and KPI worksheets, the tiered QBR builder, the hybrid trade-off script, the believable-proof checklist, and the seven-step guide to putting the framework to work on a live account. Version-stamped, designed to print, and free to subscribers, who get it first when it ships. Billing-code specifics stay on this site by design, so the kit stays accurate as the rules change.
Your email delivers the kit when it ships, plus occasional new insights from Digital Health Success. No spam. Unsubscribe anytime.