Remote Patient Monitoring Billing Guide: CPT Codes, Requirements, and Common Mistakes

Common RPM data may include:

• Blood pressure
• Weight
• Pulse oximetry
• Blood glucose
• Heart rate
• Other physiologic readings captured by a connected medical device

RPM can be useful for patients with chronic or acute conditions that need ongoing monitoring. For medical practices, however, RPM billing can become difficult if the workflow is not controlled. Use this guide as an operational billing reference, not legal, clinical, or coding advice. Always confirm current payer policy, contract requirements, and CPT/HCPCS updates before submitting claims.

What Is Remote Patient Monitoring?

Remote Patient Monitoring is a non-face-to-face service where a patient uses a connected medical device to collect physiologic data outside the office. The device electronically transmits that data to the provider or care team, who can use it to help manage the patient's condition.

RPM is commonly used for conditions such as:

• Hypertension
• Diabetes
• Congestive heart failure
• COPD
• Post-discharge monitoring
• Other acute or chronic conditions where remote physiologic data supports care management

RPM is not simply giving a patient a device. The billing record should show why the monitoring is medically reasonable and necessary.

RPM vs RTM: What Is the Difference?

Remote Patient Monitoring and Remote Therapeutic Monitoring are related, but they are not the same.

RPM, or Remote Patient Monitoring, is used for physiologic data. Examples include blood pressure, oxygen saturation, blood glucose, weight, and heart rate.

RTM, or Remote Therapeutic Monitoring, is generally used for non-physiologic therapeutic data. Examples may include musculoskeletal status, respiratory therapy information, medication adherence, therapy adherence, or treatment response.

A simple way to remember the difference:

RPM monitors physiologic data. RTM monitors therapeutic or non-physiologic data.

For billing purposes, this distinction matters. RPM and RTM should not be billed together for the same patient during the same billing period.

Remote Patient Monitoring CPT Codes

Below are the main CPT codes commonly associated with RPM billing.

Payer rules may vary. Medicare, Medicare Advantage, Medicaid, and commercial plans may not all process RPM the same way. Billing teams should verify the payer's current policy before submitting claims.

2026 RPM Billing Update: 99445 and 99470

For 2026, two RPM code updates are especially important:

CPT 99445

CPT 99445 is used for RPM device supply and data transmission when there are 2–15 days of physiologic monitoring data in a 30-day period.

This matters because traditional RPM billing often focused on the 16-day threshold tied to 99454. The addition of 99445 gives billing teams a code pathway for shorter monitoring periods, when supported by payer policy and documentation.

Do not bill 99445 and 99454 together for the same monitoring period. Select the code that matches the number of valid data transmission days.

CPT 99470

CPT 99470 is used for RPM treatment management when the care team documents the first 10 minutes of RPM management time in a calendar month.

This helps address months where RPM management occurred, but the time did not reach the 20-minute threshold traditionally associated with 99457.

Billing teams should still validate payer-specific acceptance of newer codes before use.

Basic RPM Billing Requirements

Before billing RPM, the practice should confirm the following:

1. The Patient Has an Acute or Chronic Condition

RPM should be tied to a real clinical need. The record should show the condition being monitored and why remote monitoring is appropriate.

Example:

Patient has uncontrolled hypertension. Home blood pressure monitoring is medically necessary to evaluate treatment response and support medication adjustment.

The diagnosis alone is usually not enough. The documentation should connect the condition to the need for remote monitoring.

2. The Patient Relationship Is Established

RPM generally requires an established patient relationship. The patient should already be under the care of the billing practitioner or practice.

3. The Device Qualifies

The device should be a connected medical device that electronically collects and automatically transmits physiologic data.

Manual logs alone are weak support for RPM billing. The billing team should be able to rely on device or platform logs showing actual data transmission.

4. Patient Consent Is Documented

Patient consent should be documented at the time RPM services are furnished.

Good consent documentation should show that the patient understands:

• The RPM service being provided
• The device or monitoring process
• Their responsibility to use the device
• Potential cost-sharing
• How the care team may use the transmitted data

5. Data Transmission Days Are Tracked

For device-related RPM codes, the number of valid data transmission days matters.

A clean RPM workflow should track:

• Start date of the monitoring period
• End date of the monitoring period
• Number of valid data transmission days
• Device type
• Whether the data was automatically uploaded
• Whether the data was available to the billing practitioner or care team

6. Treatment Management Time Is Tracked Separately

Treatment management codes are time-based. The care team must document time spent on RPM-related management activities.

Examples may include:

• Reviewing transmitted data
• Assessing abnormal readings
• Communicating with the patient or caregiver
• Updating the care plan
• Escalating issues to the provider
• Coordinating medication or treatment changes when appropriate

The documentation should clearly support the time billed.

7. The Same Time Is Not Double-Counted

RPM may overlap operationally with services such as CCM, TCM, BHI, PCM, or chronic pain management. However, the same staff time and effort should not be counted twice.

If the practice bills RPM and another care management service in the same month, the documentation should clearly separate the work.

How RPM Billing Works in Practice

A clean RPM billing process usually follows these steps.

Step 1: Confirm Eligibility and Medical Necessity

Before enrollment, confirm that RPM is appropriate for the patient.

The provider should document:

• The condition being monitored
• Why RPM is needed
• What type of data will be monitored
• How the data may affect the care plan

Poor documentation:

Patient enrolled in RPM.

Better documentation:

Patient has uncontrolled hypertension with recent medication adjustment. RPM blood pressure monitoring is medically necessary to evaluate response to treatment and identify readings requiring follow-up.

Step 2: Obtain and Document Consent

Consent should be documented before or at the time RPM begins.

A sample consent note may look like this:

Patient consented to Remote Patient Monitoring services. Patient was informed of the purpose of RPM, device use expectations, potential cost-sharing, and that transmitted data may be reviewed by the care team for treatment management.

The consent does not need to be complicated, but it should be clear.

Step 3: Set Up the Device and Educate the Patient

The setup note should document:

• Device type
• Setup date
• Patient education provided
• Confirmation that the patient understands how to use the device
• Any caregiver involvement, if applicable

This supports billing for initial setup and patient education when payer requirements are met.

Step 4: Track Data Transmission Days

The billing team should not guess the number of data days.

Use the RPM platform or device report to confirm whether the patient had:

• 2–15 days of transmitted data
• 16+ days of transmitted data
• Insufficient data to bill the device code

Example:

The final code should match the documentation and payer policy.

Step 5: Track Treatment Management Time

Treatment management time should be documented throughout the calendar month.

Example time log:

Total RPM management time: 26 minutes.

This may support treatment management billing when all other requirements are met.

Step 6: Submit the Claim Only After Documentation Review

Before claim submission, the billing team should confirm:

• The correct RPM code was selected
• The monitoring period is clear
• Data transmission days support the device code
• Time supports the management code
• Patient consent is documented
• The device qualifies
• RPM is not duplicated with RTM
• Time is not double-counted with another care management service
• The billing provider is appropriate
• Payer-specific rules were checked

RPM billing should not be treated as an automatic monthly charge. Each billing period should be supported by documentation.

Example RPM Billing Scenarios

Scenario 1: Hypertension Patient With 18 Data Days

A patient with uncontrolled hypertension receives a connected blood pressure cuff. The device transmits blood pressure readings on 18 days during the 30-day monitoring period. The care team spends 24 minutes reviewing readings, calling the patient, and updating the care plan.

Possible coding:

• 99453, if this is the initial setup and patient education period
• 99454, because the patient had 16+ data transmission days
• 99457, because treatment management time reached 20 minutes

The claim should be supported by device logs, consent, setup documentation, and treatment management time records.

Scenario 2: Short-Term Post-Discharge Monitoring

A patient is monitored after discharge using a connected physiologic device. The device transmits data on 10 days during the 30-day period. The care team spends 14 minutes reviewing the data and communicating with the patient.

Possible coding:

• 99445, because the patient had 2–15 data transmission days
• 99470, because RPM treatment management time reached 10 minutes but did not reach 20 minutes

The billing team should confirm payer acceptance of the newer codes before submission.

Scenario 3: RPM and CCM in the Same Month

A patient receives RPM for blood pressure monitoring and Chronic Care Management for multiple chronic conditions.

The practice may be able to bill both services if:

• RPM documentation is separate from CCM documentation
• The same time is not counted twice
• Each service independently meets its own requirements
• The payer allows both services in the same period

This is a common audit risk area. The billing team should be careful.

Common RPM Billing Mistakes

Mistake 1: Billing RPM Without Medical Necessity

RPM should not be treated like a subscription service. The record should clearly support why the patient needs remote monitoring.

Mistake 2: Billing Device Codes Without Valid Transmission Data

The billing team should verify device logs before billing 99445 or 99454.

Mistake 3: Billing 99445 and 99454 Together

Do not bill both for the same patient and monitoring period. Select the code that matches the actual number of valid data transmission days.

Mistake 4: Double-Counting Time With CCM or Other Care Management Services

The same staff time should not support two different billed services.

Mistake 5: Missing Consent

Consent is a basic RPM requirement. Missing consent can create billing and compliance issues.

Mistake 6: Weak Device Documentation

The chart should show what device was used and whether the data was electronically collected and transmitted.

Mistake 7: No Interactive Communication Documentation

Treatment management should not look like passive data review only. When communication is required, the record should show the patient or caregiver interaction.

Mistake 8: Not Checking Payer Rules

Commercial plans, Medicaid programs, and Medicare Advantage plans may apply different RPM requirements. Billing teams should check the payer before assuming Medicare rules apply.

RPM Billing Documentation Checklist

Before billing RPM, confirm the chart includes:

• Patient diagnosis or condition being monitored
• Medical necessity for RPM
• Patient consent
• Device type
• Device setup date
• Patient education documentation
• Monitoring period
• Number of valid data transmission days
• Treatment management time, if billing time-based codes
• Patient or caregiver communication, when applicable
• Provider review or escalation, when clinically appropriate
• Confirmation that RPM and RTM were not both billed for the same period
• Confirmation that time was not double-counted with CCM, TCM, BHI, PCM, or other care management services
• Payer-specific policy review, when needed

Simple RPM Billing Workflow for Practices

A practical RPM billing workflow may look like this:

1. Provider identifies patient who may benefit from RPM.
2. Provider documents medical necessity.
3. Patient gives consent.
4. Patient receives device setup and education.
5. Device begins transmitting physiologic data.
6. Billing or RPM coordinator reviews data transmission days.
7. Clinical staff and provider document treatment management time.
8. Billing team validates code selection.
9. Claim is submitted.
10. Denials or requests for records are tracked and reviewed.

The key is to build documentation into the workflow before the claim is submitted.

Why RPM Billing Fails Without a Strong Back Office

Many practices launch RPM because the clinical idea makes sense. But the billing process breaks down when no one owns the operational details.

Someone must track:

• Patient enrollment
• Consent
• Device setup
• Device activity
• Data transmission days
• Treatment management time
• Monthly billing eligibility
• Payer-specific rules
• Claim submission
• Denials
• Patient balances

Without that structure, RPM can create more AR noise than revenue. A medical virtual assistant can own the enrollment, consent, and data-day tracking so nothing is billed without support.

How RCM Staff Can Help

RCM Staff helps medical practices and billing companies support revenue cycle workflows with trained medical billing staff from the Philippines.

For RPM programs, RCM Staff can help with:

• RPM documentation review
• Patient enrollment tracking
• Device data reconciliation
• CPT code validation
• Charge entry support
• Claim submission support
• Denial follow-up
• AR follow-up
• Monthly billing audits
• Patient balance support
• Reporting and workflow cleanup

Remote Patient Monitoring can be valuable for both patient care and practice revenue. But it only works when the billing process is controlled.

If your RPM program is growing, your billing workflow needs to grow with it.

Disclaimer: This article is for general educational purposes only and does not provide legal, medical, coding, or billing advice. CPT codes, payer policies, and reimbursement rules may change. Practices should verify current Medicare, Medicaid, Medicare Advantage, and commercial payer requirements before billing RPM services. RCM Staff is an independent service provider and is not affiliated with, endorsed by, or certified by the AMA, CMS, or any payer mentioned.