An RPM reimbursement calculator projects remote patient monitoring revenue from CPT codes, enrolled patients, monitoring days, clinical management time and payer rates. It shows how setup, device supply and management codes combine into monthly and annual revenue, so practices can judge whether a program is sustainable before investing in devices, staff and software.
RPM programs fail financially for predictable reasons: patients who do not transmit enough data, management time that is never documented and codes billed incorrectly. Medicare’s 2026 Physician Fee Schedule changed the math with new codes for shorter monitoring and lighter management, so older projections are now out of date. Taction Software builds RPM platforms drawing on 200+ healthcare projects since 2013, and this calculator method builds on our RPM reimbursement guide to 2026 CPT codes.
What the RPM Reimbursement Calculator Estimates
The calculator estimates how much a remote patient monitoring program can bill each month and year, based on how many patients you enroll, how consistently they transmit data and how much clinical management time your team documents. It separates revenue by code type, so you see which part of the program drives income and where leakage is likely. It also highlights the operational metrics that matter most. The six estimates below form the full revenue picture of an RPM program, and each can be tracked monthly once your program is live and patients are enrolled.
Monthly Device Supply Revenue
Device supply codes pay for providing devices and receiving transmitted data each 30-day period. Revenue depends on how many patients transmit on enough days to qualify for each code, which makes patient engagement the single biggest driver of RPM device revenue.
Treatment Management Revenue
Management codes pay for clinical staff or provider time reviewing data and communicating with patients each calendar month. Revenue depends on documented minutes and required interactive communication, so time tracking built into your RPM platform directly protects this income stream every month.
One-Time Setup Revenue
The setup and patient education code pays once per episode of care when a patient starts monitoring. It contributes meaningfully when enrollment grows quickly, but it should not drive program economics, because recurring monthly codes generate far more revenue over time.
Revenue Leakage
The calculator estimates revenue lost when patients fall below day thresholds, management time is undocumented or interactive communication is missing. Leakage is often the difference between a profitable and unprofitable program, and measuring it shows exactly where operational fixes will pay back.
Program Costs
Costs include devices, connectivity, platform software, clinical staff time, billing and patient support. Comparing costs with projected revenue shows margin per patient and the enrollment level needed to break even, which is essential for planning staffing and growth sensibly. Hidden costs erode margin.
Break-Even Enrollment
The calculator identifies how many actively monitored patients the program needs to cover fixed costs, such as staff and software. Many programs underestimate this number, then struggle because enrollment grows slowly or engagement falls after the first few months of monitoring.
RPM CPT Codes Used in the Calculator
RPM billing combines a small set of CPT codes covering setup, device supply and treatment management. The 2026 Medicare Physician Fee Schedule added two new codes for shorter monitoring periods and lighter management time, giving programs more ways to bill for patients who do not meet older thresholds. Rates vary by locality and payer, so always use current fee schedule rates and your commercial contracts. The six codes below are the ones the calculator uses, and correct code selection each month is essential to both revenue and compliance with Medicare billing requirements.
CPT 99453: Setup and Education
CPT 99453 covers initial device setup and patient education on using the equipment. It is billed once per episode of care, subject to current Medicare requirements. Clear onboarding also improves engagement, which protects the recurring device and management revenue that follows.
CPT 99454: Device Supply, 16 or More Days
CPT 99454 covers device supply with daily recordings or programmed alerts when data is transmitted on 16 or more days in a 30-day period. It remains the primary device code for patients who monitor consistently throughout the month. Engagement drives it.
CPT 99445: Device Supply, 2 to 15 Days
New for 2026, CPT 99445 covers device supply when data is transmitted on 2 to 15 days in a 30-day period. It cannot be billed in the same period as 99454, and it captures revenue from patients with lower monitoring frequency.
CPT 99457: First 20 Minutes of Management
CPT 99457 covers the first 20 minutes of treatment management time by clinical staff or providers in a calendar month, including at least one real-time interactive communication with the patient or caregiver. Documented time and communication are essential to bill it.
CPT 99458: Each Additional 20 Minutes
CPT 99458 is an add-on code for each additional 20 minutes of treatment management in the same calendar month, billed alongside 99457. Patients with more complex needs or unstable readings often qualify, increasing revenue for higher-acuity monitoring programs. Documentation matters.
CPT 99470: First 10 Minutes of Management
New for 2026, CPT 99470 covers 10 to 19 minutes of treatment management in a calendar month with required interactive communication. It captures revenue for lighter-touch months that previously could not be billed because they fell short of 20 minutes.
Inputs You Need for the Calculation
Accurate RPM projections depend on realistic inputs, especially engagement and management time. Optimistic assumptions, such as every patient transmitting every day, create projections that real programs rarely achieve. Use data from existing programs, pilots or published experience in similar populations wherever possible. The six inputs below drive nearly all of the variation in RPM revenue, and collecting them before buying devices or software gives you a projection your finance team can trust. Our free healthcare AI ROI calculator uses similar input discipline for broader digital health programs. Assumptions should stay visible.
Eligible and Enrolled Patients
Estimate how many patients meet clinical criteria for monitoring, and how many will realistically enroll. Enrollment usually builds gradually, so model enrollment month by month rather than assuming the full eligible population joins at launch. Realistic ramps prevent disappointment. Plan monthly.
Monitoring Day Distribution
Estimate what share of patients will transmit on 16 or more days, 2 to 15 days or fewer than 2 days each month. This distribution determines which device code applies, and it is the most important input in the entire RPM revenue calculation.
Management Time Distribution
Estimate how many patients will receive 10 to 19 minutes, 20 to 39 minutes or 40 or more minutes of documented management each month. Time depends on patient acuity, staffing and workflow design, so base it on realistic care team capacity.
Payer Mix and Rates
Use current Medicare Physician Fee Schedule rates for your locality and the rates in your commercial and Medicare Advantage contracts. Payer coverage policies differ, so confirm which payers reimburse each code and under what conditions before including them in projections.
Program Cost Inputs
Include device costs, connectivity, platform fees, clinical staff time, billing support, patient onboarding and device logistics. Missing costs make RPM look more profitable than it is, especially when device replacement and patient support needs are underestimated at launch. Include everything.
Attrition
Patients stop monitoring for many reasons, including improvement, frustration and device problems. Model monthly attrition and re-enrollment, because a program that loses patients quickly needs constant enrollment just to maintain revenue and staff utilization at sustainable levels. Plan for it.
The RPM Revenue Formula Step by Step
The RPM revenue calculation multiplies patients in each monitoring and management category by the applicable code rates, then subtracts costs. Keeping each step separate makes projections transparent and easy to update as real program data arrives. Use your own current rates rather than published averages, because reimbursement varies by locality and payer. The six steps below walk through the calculation our team uses when modeling RPM programs, and the illustrative example in the final step uses assumed rates purely to show how the math works, not to predict your results.
Step 1: Count Patients by Device Code
Multiply enrolled patients by the share transmitting 16 or more days for 99454, and by the share transmitting 2 to 15 days for 99445. Patients below 2 days generate no device revenue that month, which highlights the cost of disengagement.
Step 2: Count Patients by Management Code
Multiply enrolled patients by the share receiving 10 to 19 minutes for 99470, 20 or more minutes for 99457, and each additional 20 minutes for 99458. Ensure interactive communication requirements are met for every patient counted in these categories. Time drives it.
Step 3: Apply Your Rates
Multiply each patient count by your blended rate for that code, combining Medicare and commercial rates according to your payer mix. Use current fee schedule and contract rates, and update them annually when CMS publishes the new Physician Fee Schedule.
Step 4: Add Setup Revenue
Add revenue from 99453 for newly enrolled patients each month, based on your enrollment forecast. Setup revenue is higher during rapid growth and lower once the program matures, so model it separately from recurring monthly revenue for accuracy. Growth shapes it.
Step 5: Subtract Program Costs
Subtract monthly costs for devices, connectivity, platform software, clinical staff, billing and patient support. The result is net monthly program margin, which shows whether the program is sustainable and how margin changes as enrollment grows over time. Margin decides viability.
Step 6: An Illustrative Example
Assume 200 enrolled patients averaging an illustrative $100 per patient per month across all codes, and costs of $60 per patient per month. Net margin would be about $8,000 monthly. Replace every assumption with your own rates and costs before using the result.
Compliance Requirements That Protect RPM Revenue
RPM revenue is only real if claims survive audits. Medicare and commercial payers expect specific conditions to be met and documented, and gaps can lead to denials, recoupments or worse. Building compliance into workflows and software is far more reliable than relying on staff memory. The six requirements below are the ones that most often affect RPM revenue, and an RPM platform designed around them protects income automatically. Always confirm current requirements with CMS guidance, payer policies and your compliance advisers, because rules evolve with each annual fee schedule update.
Patient Consent
Patients must consent to remote monitoring services, including understanding potential cost sharing. Consent should be documented before services begin. Platforms that capture and store consent during onboarding prevent a common audit finding that can invalidate months of otherwise correct billing.
Medical Necessity
Monitoring must be reasonable and necessary for the patient’s condition, ordered by a qualified practitioner and documented in the record. Clear enrollment criteria and documentation templates help demonstrate medical necessity consistently across every patient enrolled in the program. Templates help.
Qualifying Devices
Devices used for RPM must meet the FDA definition of a medical device and automatically transmit physiologic data. Patient-entered data alone generally does not qualify. Device selection therefore affects both clinical value and whether device supply codes can be billed at all.
Accurate Day Counting
Device code selection depends on the number of days with transmitted data in each 30-day period. Platforms must count days accurately and select the correct code automatically, because manual counting across hundreds of patients quickly produces errors and lost revenue.
Time and Interaction Documentation
Management codes require documented time and at least one real-time interactive communication each month. Time tracking and communication logs built into the RPM platform create reliable records, protecting management revenue during audits and payer reviews of your program. Audits depend on it.
Billing Rules and Overlaps
Rules limit billing RPM by more than one practitioner for the same patient in the same period, and RPM cannot be billed alongside remote therapeutic monitoring for the same patient. Automated checks prevent overlapping claims that payers routinely deny. Checks save money.
How to Increase RPM Revenue Without Adding Risk
Most RPM programs can grow revenue significantly without enrolling a single extra patient, simply by reducing leakage and matching codes to real care. Better engagement lifts more patients over day thresholds, smarter workflows document management time that is already happening, and the 2026 codes capture months that used to go unbilled. These improvements also improve care, because engaged patients and timely interactions lead to better outcomes. The six strategies below consistently increase RPM revenue for the programs we support, and each stays firmly within Medicare billing rules and payer requirements.
Use the 2026 Codes Correctly
Bill 99445 for patients transmitting 2 to 15 days and 99470 for 10 to 19 minutes of management. These codes capture revenue from lighter-touch months that previously generated nothing, provided documentation and interactive communication requirements are met consistently for every patient.
Improve Patient Engagement
Reminders, simple devices, clear onboarding and responsive support help patients transmit more consistently. Every patient moved from below 2 days into a billable category, or from 2 to 15 days into 16 or more, increases device revenue while improving clinical visibility.
Automate Time Tracking
Management time often goes undocumented because staff record it manually or forget. Platforms that capture review time, calls and messages automatically ensure work already performed is counted, protecting management revenue without adding extra workload for clinical staff. Accuracy improves too.
Prioritize Alerts Intelligently
Triaged alerts direct clinical attention to patients who need it most, making management time more valuable and easier to document. Prioritization also reduces burnout, helping programs scale enrollment without proportional increases in nursing or clinical staff headcount. Quality rises as well.
Flag At-Risk Patients Early
Dashboards that show which patients are approaching month end below day or time thresholds let staff intervene in time. A short outreach call can restore engagement and meet requirements, turning a missed month into a billable one through genuine patient care.
Reduce Attrition
Track why patients stop monitoring and address common causes, such as device problems or unclear value. Retaining patients longer improves outcomes and lifetime revenue per patient, and it reduces the constant enrollment effort that high-attrition programs require just to stay stable.
How We Help You Build a Profitable RPM Program
We build RPM platforms that capture revenue correctly, support clinical workflows and integrate with EHRs and billing systems. Our work is billed at a blended rate of $50 per hour, and the ranges below are planning figures, not quotes. Device, connectivity and third-party fees are separate. For Rhythm, we built a full-lifecycle RPM platform covering enrollment, insurance verification, device logistics, triaged alerts, billing guidance and bidirectional EHR integration, described in the Rhythm case study. The six options below describe how organizations engage us. Every estimate lists assumptions. Scope is agreed upfront.
RPM Revenue Model: $2,000 to $6,000
Building a documented RPM revenue and cost model typically takes 40 to 120 hours, covering inputs, code distributions, payer mix, costs, break-even and sensitivity analysis, so leadership can approve the program with realistic expectations. Assumptions stay visible throughout. Updates are simple.
RPM Platform MVP: $40,000 to $104,000
An RPM platform MVP with patient app, device integration, clinician dashboard, day counting, time tracking and billing support typically takes 800 to 2,080 hours. Our remote patient monitoring software development page explains the scope. Billing logic is included. New codes are supported.
Full RPM Platform: $104,000 to $208,000
A full platform with multiple programs, triaged alerts, care team workflows, EHR integration, analytics and automated billing typically takes 2,080 to 4,160 hours, suiting organizations running RPM across many service lines or offering RPM to other providers. Phased delivery helps.
Specialty RPM Programs
We build condition-specific programs, such as cardiac RPM platform development and diabetes RPM platform development, with devices, alerts and workflows tailored to each condition. Each program reuses the same core platform, billing logic and integrations, so additional conditions cost less to launch and clinical teams work in one familiar system.
AI for Alert Fatigue
Triaged alerts keep clinical teams focused on patients who need attention. Our guide to how AI reduces RPM alert fatigue explains how prioritization improves care team efficiency and supports management time documentation. Clinicians spend time where it matters most for patients.
Dedicated RPM Developers
Organizations with existing platforms can hire RPM developers at about $8,000 per engineer per month to add new codes, programs, devices and integrations as reimbursement rules and clinical needs evolve. They bring experience with device integration, billing logic and EHR connections.
Frequently Asked Questions
These are the questions practice leaders, CFOs, clinical directors and digital health founders ask most often when they project RPM reimbursement, whether they are launching a first program, adding the 2026 codes or fixing revenue leakage. The answers are short on purpose and are not billing or legal advice, so confirm requirements with CMS guidance, payers and compliance advisers. If your question depends on your patients or payers, a short call with our team will help. For broader program guidance, see our remote patient monitoring guide. Answers reflect current rules.
What Are the RPM CPT Codes for 2026?
The core codes are 99453 for setup, 99454 for 16 or more days of device data, 99457 and 99458 for 20-minute management increments, plus new 2026 codes 99445 for 2 to 15 days of data and 99470 for 10 to 19 minutes of management.
How Much Revenue Can an RPM Program Generate?
It depends on enrollment, monitoring days, documented management time, payer mix and rates. Model your own inputs with current fee schedule and contract rates, because published averages vary by locality and rarely match a specific program’s patient engagement and payer mix.
Can 99445 and 99454 Be Billed Together?
No. They cannot be billed for the same patient in the same 30-day period. Use 99454 when data is transmitted on 16 or more days and 99445 when data is transmitted on 2 to 15 days. Choose one each period.
Why Do RPM Programs Lose Revenue?
Common causes include patients transmitting too few days, undocumented management time, missing interactive communication, incorrect code selection and attrition. Platforms that track days, time and communication automatically, and flag at-risk patients early, reduce this leakage significantly. Fixes pay back quickly.
How Much Does an RPM Platform Cost to Build?
At our $50 blended hourly rate, an RPM platform MVP typically costs $40,000 to $104,000, and a full platform $104,000 to $208,000. Device, connectivity and third-party service fees are separate from development cost. Every estimate lists assumptions. Scope decides the range.
Can RPM Integrate With Our EHR?
Yes. We integrate RPM platforms with EHRs through FHIR APIs and HL7 interfaces, sending readings, alerts and documentation into the patient record and pulling demographics and orders, so clinicians work inside familiar workflows rather than separate systems. Adoption improves. Most do.
Tell Us About Your RPM Program
Share your patient population, current or planned enrollment, devices, payer mix and existing systems. In a 30-minute call we will outline your revenue model, flag likely leakage and estimate what the right platform would cost. Book a free consultation. No commitment.