Learn what RPM services include, key CPT codes, and the steps to launch a compliant, reimbursable remote patient monitoring program.
Remote Patient Monitoring (RPM) has shifted from an emerging care delivery model to a proven, reimbursable healthcare service - and adoption is accelerating. For cardiology practices, primary care providers, Chronic Care Management (CCM) programs, and health systems managing complex chronic populations, RPM services create a direct pathway to proactive care, reduced hospitalizations, and sustainable program revenue. Understanding what RPM services include and how to launch them correctly is the foundation for any successful implementation.
What Are RPM Services in Healthcare?
RPM services encompass the full ecosystem of technology, clinical workflows, and reimbursable activities that allow providers to collect and act on patient physiologic data outside of a traditional clinical setting. Under CMS guidelines, Medicare broadly covers RPM for the collection of physiologic data across a wide range of devices, for both chronic and acute conditions.
Three core service components define an RPM program:
- Device setup and patient education: Onboarding the patient with an FDA-cleared monitoring device and educating them on how to use it correctly and consistently.
- Device supply and data transmission: Ongoing provision of a connected device that automatically and digitally transmits health data - such as blood pressure, blood oxygen, weight, or glucose - without manual patient input.
- Clinical management and monitoring: Qualified clinical staff or providers reviewing transmitted data, managing thresholds and alerts, and engaging with patients when readings fall outside established parameters.
To be eligible, a patient must have a chronic or acute condition that requires monitoring, and the device used must meet the FDA's definition of a medical device, digitally uploading data and collecting transmissions at least every 2 days, every 30 days. For a full breakdown of how these components interact in real clinical settings, Circle Health Care's RPM pros, cons, and benefits guide covers the clinical evidence, use cases, and practical tradeoffs in detail.
What Do RPM Services Include?
RPM services span clinical, operational, and technology components across the patient journey:
Devices and data collection
- Blood pressure monitors (hypertension, heart failure)
- Pulse oximeters (COPD, asthma, post-COVID)
- Weight scales (heart failure decompensation monitoring)
- Glucometers (diabetes and blood sugar tracking)
- Wearables tracking heart rate and activity (cardiology, post-surgical)
Clinical monitoring activities
- Threshold-based alert management by clinical staff
- Trending and baseline deviation review
- Real-time or asynchronous provider-patient interaction
- Care plan adjustment based on transmitted data
Billing and documentation
- CPT code submission aligned to the calendar month
- Patient consent documentation (written or verbal)
- Physician or qualified provider ordering and oversight
- Coordination with CCM, transitional care, and other chronic care programs
RPM Billing Codes: 2025–2026 Overview
Medicare pays for each of the three main RPM components separately and at the same rate, regardless of the type of device the patient uses or the health data they collect. The core CPT codes as of 2026 are:
The 2026 Medicare Physician Fee Schedule introduced two significant additions:
- CPT 99445 - Device supply and transmission covering 2–15 days in 30 days, enabling billing for shorter monitoring programs previously unreimbursable under the 16-day threshold.
- CPT 99470 - A 10-minute RPM management tier for acute oversight; cannot be billed in the same month as CPT 99457.
Circle Health Care's guide to 2026 RPM CPT codes explains how to structure billing across both legacy and new codes without overlap or audit exposure.
For a dedicated breakdown of when and how to use CPT 99445 specifically, the complete guide to the 2–15 day RPM code covers eligibility, clinical use cases, and payer coverage confirmation. As of May 2026, RPM is also covered by 42 state Medicaid programs, according to the Center for Connected Health Policy.
How to Get Started with RPM Services
Launching an RPM program requires deliberate planning across clinical, operational, and technology dimensions. The following steps apply whether you are a solo primary care practice or a large health system standing up a new program.
Step 1 - Define your clinical goals and patient population.
Start with patients who have chronic conditions requiring consistent monitoring: hypertension, diabetes, COPD, or heart failure. These populations carry the highest eligibility under Medicare RPM coverage rules and deliver the greatest clinical ROI through early intervention. Circle Health Care's article on how RPM reduces hospital readmissions and elevates quality star ratings provides the clinical outcome benchmarks to use when setting program targets.
Step 2 - Select FDA-cleared, patient-appropriate devices.
Device choice has a direct impact on patient adherence and data quality. Prioritize cellular-enabled devices that transmit automatically without Wi-Fi, app pairing, or technical setup on the patient's end. Devices that ship pre-configured and ready to use eliminate the most common point of failure in RPM programs: patient onboarding friction.
Step 3 - Establish clinical workflows and alert protocols.
Define who reviews alerts, within what timeframe, and what the escalation path is when readings fall outside safe thresholds. Clinical staff can perform the majority of monitoring under the general supervision of a provider with a valid NPI. Document tier-based alert thresholds for each device type and condition, and standardize your response workflow before enrolling patients.
Step 4 - Obtain patient consent and physician orders.
Patients must consent - in writing or verbally - to receiving RPM services, and the RPM service must be ordered by a physician or other qualified healthcare professional such as a nurse practitioner, certified nurse specialist, or physician assistant. Build consent forms and physician order templates into your intake workflow from day one.
Step 5 - Pilot with a small cohort before scaling.
Start with 10–20 patients to validate device logistics, alert workflows, documentation practices, and billing submission. Identify gaps in staff training or patient education before scaling. Programs that attempt to enrol large volumes too early consistently encounter workflow problems that compound at scale.
Step 6 - Integrate RPM with CCM if applicable.
Under current CMS regulations and guidance, providers can bill RPM codes alongside Chronic Care Management (CCM) codes in the same month for the same patient, provided the services are documented as distinct. For CCM programs already managing COPD, heart failure, or diabetes patients, adding RPM devices deepens clinical insight and increases per-patient revenue without proportional staffing increases.
Frequently Asked Questions
What conditions qualify for RPM services under Medicare?
Medicare covers RPM for patients with chronic or acute conditions that require monitoring, including hypertension, heart failure, COPD, diabetes, and asthma. The monitoring must be medically necessary and ordered by a provider.
Who can order and manage RPM services?
RPM can be ordered by physicians, nurse practitioners, physician assistants, and other qualified healthcare professionals. Clinical staff may provide monitoring and patient support under general supervision.
How many days of data are required to bill CPT 99454?
CPT 99454 requires at least 16 days of transmitted readings in 30 days. CPT 99445, introduced in 2026, covers 2–15 days of data transmission.
Can RPM be combined with a Chronic Care Management (CCM) program?
Yes. RPM and CCM can be billed in the same month if the services and time spent are documented separately.
What is the difference between RPM and telehealth?
Telehealth involves live video or phone visits, while RPM continuously collects and transmits patient health data between visits using connected devices.
How long does it take to launch an RPM program?
Most RPM pilots can launch within 4–8 weeks, while full implementation and scaling typically take 3–6 months.