RPM for Hypertension in 2026: Medicare Billing, Devices and Workflow Guide

Updated for 2026. Hypertension is one of the clearest clinical use cases for Remote Patient Monitoring (RPM). Instead of relying only on blood pressure measurements taken during occasional office visits, an appropriate RPM program can allow patients to use a connected blood pressure device at home and automatically transmit physiologic data to their healthcare team.

CMS specifically uses hypertension and a connected blood pressure cuff as an example of Remote Patient Monitoring. The practitioner determines that monitoring is medically necessary, the patient consents, the patient receives and learns to use the connected device, blood pressure information is automatically transmitted, and the clinical team uses the data to help manage treatment.

For practices, however, RPM is more than shipping a blood pressure cuff to a patient. Medicare billing depends on meeting the requirements for the individual services being reported, maintaining appropriate documentation, collecting qualifying device data, performing treatment-management work when applicable, communicating with the patient or caregiver when required, and avoiding duplicate services.

This guide explains how practices can build a structured hypertension RPM program in 2026.

What Is Remote Patient Monitoring for Hypertension?

Remote Patient Monitoring, also called Remote Physiologic Monitoring, allows physiologic information to be collected outside the traditional office setting using an appropriate connected medical device.

For hypertension, the monitored physiologic parameter is commonly blood pressure.

A typical workflow may look like this:

1. A practitioner identifies a patient whose hypertension would benefit from remote monitoring.
2. The practitioner determines RPM is medically reasonable and necessary.
3. The patient provides consent.
4. The patient receives an appropriate connected blood pressure device.
5. The patient receives setup and device education.
6. The patient takes blood pressure measurements at home.
7. The device electronically and automatically transmits the readings.
8. The healthcare team reviews the information.
9. The practitioner or care team uses the data as part of treatment management.
10. Clinically significant findings are escalated according to practice protocol.

Why Hypertension Is Well Suited to RPM

Blood pressure can vary significantly between office visits. A connected home-monitoring workflow can provide clinicians with additional longitudinal information rather than relying on a single measurement obtained during an appointment.

RPM may help an appropriate clinical team:

• Review blood pressure trends between visits
• Identify potential persistent elevation or other concerning patterns
• Assess response after treatment changes
• Support medication-adherence conversations
• Identify patients who may need earlier clinical review
• Improve patient engagement with home blood pressure monitoring
• Provide additional information for treatment decisions

RPM should supplement appropriate clinical care rather than replace medically necessary office, emergency, or other services.

Medicare RPM Eligibility for Hypertension

CMS states that Medicare broadly covers Remote Patient Monitoring for physiologic data when applicable requirements are met and that RPM can be used for both chronic and acute conditions.

For hypertension RPM, the practitioner should determine that remote physiologic monitoring is medically necessary for the individual patient.

Unlike Chronic Care Management, RPM does not require the patient to have two chronic conditions simply because RPM is being considered.

A patient with hypertension alone may potentially be appropriate for RPM when the clinical need and all applicable Medicare requirements are satisfied.

RPM Requires an Appropriate Connected Medical Device

One of the most important distinctions between formal Medicare RPM and general home blood pressure tracking is the device.

CMS has stated that an RPM device must:

• Meet the applicable FDA definition of a medical device
• Be capable of collecting the relevant physiologic information
• Digitally and automatically transmit the information

This means a patient simply writing blood pressure readings in a notebook and telling them to the care manager is not the same workflow as device-based Medicare RPM.

Example Hypertension RPM Workflow

Consider a Medicare patient with hypertension whose blood pressure remains difficult to evaluate based on office measurements alone.

The practitioner determines that connected home blood pressure monitoring is medically necessary.

The practice:

• Documents the reason for RPM
• Obtains patient consent
• Provides an appropriate connected blood pressure cuff
• Educates the patient on proper device use
• Receives automatically transmitted blood pressure information
• Reviews trends
• Performs applicable treatment-management activities
• Communicates with the patient as required
• Escalates clinical concerns when necessary

The documentation and billing pathway should reflect the specific RPM services actually furnished.

2026 RPM CPT Codes Practices Should Know

The code selected should be based on the actual service furnished and current CPT, CMS, Medicare Administrative Contractor and payer requirements.

CPT 99453: RPM Setup and Patient Education

CPT 99453 is associated with initial setup and patient education for remote physiologic monitoring equipment.

For a hypertension program, setup may include:

• Providing or activating the connected blood pressure device
• Explaining how to use the equipment
• Teaching the patient how measurements are transmitted
• Confirming the patient can operate the device
• Explaining whom to contact for technical problems

The practice should document that setup and education actually occurred.

CPT 99445: New Shorter Monitoring-Day RPM Pathway for 2026

Beginning in 2026, CPT 99445 provides an RPM device-supply pathway for patients with 2 through 15 days of qualifying physiologic monitoring during the applicable 30-day period.

This is particularly relevant for patients whose clinical monitoring plan does not require the longer device-data threshold associated with the traditional RPM device-supply pathway.

The existence of 99445 does not mean practices should intentionally reduce monitoring days simply to use a different code. Monitoring frequency should be clinically appropriate for the patient.

CPT 99454: Longer RPM Device-Supply Monitoring

CPT 99454 represents the traditional device-supply pathway for RPM when the applicable longer monitoring-day requirements are met.

CMS's Medicare RPM materials identify 99454 with monitoring over 16 or more days during a 30-day period.

For hypertension RPM, the system should be able to determine how many qualifying days of automatically transmitted data occurred during the applicable monitoring period.

Do Not Confuse Number of Readings With Number of Monitoring Days

Device usage rules should be evaluated according to the current requirements for the specific code being reported.

A patient may take several blood pressure measurements on one day, but multiple readings on the same day do not necessarily represent multiple monitoring days.

Your RPM platform should separately track:

• Total readings
• Unique monitoring days
• Transmission status
• Applicable 30-day monitoring period

CPT 99470: New 10-Minute RPM Treatment-Management Pathway

For 2026, CPT 99470 introduces a shorter RPM treatment-management pathway associated with the first 10 minutes under the applicable requirements.

This gives practices another potential treatment-management pathway for patients whose clinically necessary monthly management does not reach the traditional 20-minute pathway.

Practices should review the current CPT descriptor and CMS billing rules before reporting 99470 and should not manufacture or stretch time to qualify for any RPM treatment-management code.

CPT 99457: Traditional RPM Treatment Management

CPT 99457 represents RPM treatment-management services during a calendar month and includes an interactive communication requirement with the patient or caregiver.

CMS has historically described 99457 as the first 20 minutes of applicable RPM treatment-management time.

Qualifying work may involve:

• Reviewing transmitted blood pressure information
• Assessing trends
• Managing the patient's treatment plan
• Communicating with the patient or caregiver
• Escalating issues to the billing practitioner
• Documenting clinically relevant follow-up

CPT 99458: Additional RPM Treatment-Management Time

CPT 99458 is an add-on code associated with additional qualifying RPM treatment-management time beyond the applicable base treatment-management service.

It should not be treated as an independent RPM service without satisfying the applicable base-code requirements.

Practices should also verify current payer rules and applicable unit limitations before billing multiple additional units.

Interactive Communication Matters

CMS has clarified that the interactive communication requirement associated with RPM treatment-management codes involves real-time synchronous, two-way interaction that can be enhanced by video or other data transmission.

Simply reviewing a dashboard without the applicable patient or caregiver interaction does not by itself satisfy every requirement of the treatment-management code family.

A strong workflow should document:

• Date of communication
• Person contacted
• Method of communication
• Clinical issue discussed
• Treatment-management work performed
• Staff or practitioner involved
• Applicable duration

Patient Consent

CMS permits patient consent for RPM to be obtained when the services are furnished.

The practice should document consent clearly in the medical record or RPM system.

Example Documentation

Patient educated regarding Remote Patient Monitoring for hypertension, connected blood pressure device use, remote transmission of physiologic information, program communication expectations and potential Medicare cost sharing. Patient agreed to participate.

Your actual consent language should reflect current requirements and organizational policies.

Established Patient Relationship

Medicare RPM policy has generally required an established patient-practitioner relationship for RPM services outside temporary public-health-emergency exceptions.

Practices should verify that the relationship and any required initiating clinical evaluation are supported under current CMS and payer rules before beginning billing.

How Often Should a Patient Check Blood Pressure?

Medicare billing requirements should not be used to determine a patient's clinical blood pressure measurement schedule.

The monitoring plan should be determined by the treating practitioner based on the patient's clinical situation.

Factors may include:

• Severity of hypertension
• Recent medication changes
• Comorbid conditions
• Previous blood pressure variability
• Symptoms
• Patient ability to use the device

Practices should distinguish the clinical monitoring plan from the separate requirements of an RPM billing code.

Blood Pressure Device Training

Incorrect measurement technique can reduce the clinical usefulness of home blood pressure information.

Patient education should follow the device instructions and the practice's clinical protocol.

Training may address:

• How to apply the cuff correctly
• How to activate a measurement
• How data transmission occurs
• What to do if the device does not transmit
• When to contact the practice
• What to do if symptoms require urgent or emergency attention

The RPM program should not imply that dashboard monitoring replaces emergency care.

Clinical Escalation Workflow

Every hypertension RPM program should have a defined escalation process.

The software may identify readings requiring attention, but the clinical team should determine how alerts are handled.

The workflow should define:

• Who reviews incoming information
• Who evaluates concerning trends
• When the practitioner is notified
• How patient communication is documented
• What happens when the patient cannot be reached
• How urgent symptoms are directed to appropriate care

Alert thresholds and treatment decisions should be established by qualified healthcare professionals rather than generated solely for billing purposes.

Sample Hypertension RPM Workflow

Step 1: Patient Identification

The practitioner identifies a patient whose hypertension would benefit from remote physiologic monitoring.

Step 2: Clinical Review

The practitioner determines that RPM is medically necessary and appropriate.

Step 3: Consent

The patient is educated about RPM and provides consent.

Step 4: Device Setup

The patient receives an appropriate connected blood pressure cuff and education.

Step 5: Data Collection

The patient uses the device according to the clinical monitoring plan, and readings are automatically transmitted.

Step 6: Monitoring

The care team reviews incoming physiologic data according to practice protocols.

Step 7: Treatment Management

When applicable, qualifying staff or practitioners perform treatment-management activities and required interactive communication.

Step 8: Monthly Billing Review

The practice verifies device data, monitoring days, treatment-management time, communication, staff eligibility, documentation and concurrent services before submitting claims.

What Should an RPM Blood Pressure Record Contain?

A useful RPM record may include:

• Patient name and identifier
• Billing practitioner
• Condition being monitored
• Medical necessity documentation
• Consent
• Device information
• Setup and education date
• Automatically transmitted physiologic data
• Unique monitoring days
• Clinical review activities
• Treatment-management activities
• Interactive communications
• Staff identities
• Time entries
• Clinical escalations
• Monthly billing status

Sample RPM Documentation

Weak Documentation

Reviewed BP. Patient doing well. RPM 20 minutes.

Stronger Documentation

Reviewed automatically transmitted home blood pressure trends for the current monitoring period. Multiple readings remain above the patient's practitioner-defined treatment target. RN contacted patient in real time, reviewed medication adherence and device use, confirmed no newly reported urgent symptoms, and escalated the trend to the supervising practitioner for treatment-plan review. Follow-up task created after practitioner review.

The stronger entry identifies what information was reviewed, what action occurred, and how the activity affected treatment management.

Do Not Automatically Bill Every Patient Every Month

A patient being enrolled in an RPM program does not automatically mean every RPM code is billable each month.

Before billing, verify that the requirements for each proposed service were actually satisfied.

Possible reasons a patient-month may not support a particular RPM code include:

• Insufficient qualifying monitoring days
• Device not transmitting automatically
• Insufficient treatment-management time
• Missing required interactive communication
• Documentation is incomplete
• Patient stopped using the program
• Duplicate monitoring by another practitioner

99445 vs 99454 for Hypertension RPM

The clinical monitoring plan should determine device usage. Code selection should follow the services actually furnished rather than driving patient care.

99470 vs 99457

Practices should verify the latest CPT and Medicare instructions before configuring automated code-selection logic.

RPM vs Self-Measured Blood Pressure Monitoring

Hypertension practices should understand that Medicare RPM is not the only framework involving home blood pressure information.

CPT codes 99473 and 99474 describe separate self-measured blood pressure services under their own requirements.

The workflows should not be confused.

RPM

• Uses an appropriate connected medical device
• Physiologic data are automatically transmitted
• Includes separate device and treatment-management pathways

Self-Measured Blood Pressure Services

• Use their own specific measurement, training and reporting requirements
• Should be evaluated independently from the RPM code family

The practice should determine which service reflects what is actually being furnished.

RPM and CCM for Hypertension

A patient with hypertension plus another qualifying chronic condition may also meet Chronic Care Management requirements.

CMS permits qualifying remote monitoring and care-management services concurrently when each service independently satisfies its requirements.

The same time and effort should not be counted twice.

Example

An RN spends time performing RPM treatment management based on automatically transmitted blood pressure information.

Later, the RN performs distinct CCM work coordinating the patient's nephrology appointment and updating a comprehensive chronic-care plan.

The activities should be documented separately under the appropriate programs.

RPM and APCM

Some primary-care patients may also receive Advanced Primary Care Management services.

Practices should review current CMS bundling and concurrent-service rules before reporting additional services with APCM rather than assuming every RPM component is separately payable.

Only One Practitioner Should Bill the Remote Monitoring Service for the Same Period

Coordination is particularly important when primary care, cardiology, nephrology or another specialty may all want access to home blood pressure information.

Your enrollment workflow should identify:

• Responsible RPM practitioner
• Practice furnishing the RPM service
• Condition being monitored
• Device being used
• Monitoring start date

This helps reduce duplicate monitoring and billing risk.

Hypertension RPM Dashboard Features

A practical RPM platform should help staff see:

• Active patients
• Connected device status
• Latest transmitted reading
• Monitoring days
• Transmission gaps
• Practitioner-defined alert status
• Open patient communications
• Treatment-management time
• Clinical escalations
• Billing readiness

Do Not Treat Every Abnormal Reading the Same

RPM software can surface information, but clinical interpretation belongs to qualified healthcare professionals.

Practices should configure workflows consistent with clinical protocols rather than relying on generic alert thresholds supplied by software vendors.

Patient-specific treatment goals and escalation instructions may differ depending on the patient's health status and treatment plan.

Common Hypertension RPM Mistakes

1. Using a Non-Connected Device

Manually reported readings should not be represented as automatically transmitted RPM device data.

2. Billing Based on Enrollment

An active RPM status does not automatically satisfy every monthly code.

3. Ignoring Monitoring Days

Device-supply coding depends on applicable monitoring requirements.

4. Confusing Readings and Days

Multiple readings on one date do not automatically equal multiple monitoring days.

5. Missing Treatment-Management Communication

The applicable treatment-management pathways contain communication requirements that should be documented.

6. Automatically Adding Time

Treatment-management minutes should represent actual qualifying work.

7. Double Counting CCM Time

The same work should not simply be entered into both RPM and CCM.

8. No Clinical Escalation Process

A dashboard showing concerning readings is not enough. Practices need an operational response process.

9. Assuming RPM Replaces Office Care

RPM complements clinical care. It does not replace medically necessary evaluation or emergency care.

10. Choosing Codes Based on Payment Instead of Service

The service actually furnished should determine the code.

Hypertension RPM Pre-Billing Checklist

• Patient has a condition appropriate for RPM.
• Medical necessity is documented.
• Applicable patient-practitioner relationship requirements are satisfied.
• Patient consent is documented.
• Device meets applicable RPM requirements.
• Device data are digitally and automatically transmitted.
• Setup and education are documented when billed.
• Unique monitoring days are accurately calculated.
• Correct device-supply pathway is selected.
• Treatment-management activity is documented when billed.
• Applicable interactive communication occurred and is documented.
• Staff or practitioner identity is documented.
• Actual treatment-management time is supported.
• Add-on code requirements are satisfied.
• Concurrent CCM or other services have been reviewed.
• Duplicate time and effort have been removed.
• Another practitioner is not improperly billing duplicate monitoring.
• Current CMS, CPT, MAC and payer requirements have been checked.

30-Day Hypertension RPM Implementation Plan

Week 1: Build the Program

• Select eligible billing practitioners.
• Define patient-selection criteria.
• Select appropriate connected devices.
• Create consent workflow.
• Create setup and education workflow.
• Define clinical escalation protocols.

Week 2: Configure Technology

• Connect device platform.
• Configure patient assignments.
• Configure monitoring-day calculations.
• Configure treatment-management time tracking.
• Configure communication documentation.
• Configure billing-readiness checks.

Week 3: Start a Patient Pilot

• Select clinically appropriate patients.
• Obtain consent.
• Distribute devices.
• Complete education.
• Verify successful data transmission.

Week 4: Review the First Monitoring Cycle

• Review device adherence.
• Review transmission problems.
• Review clinical escalations.
• Review documented treatment management.
• Perform a pre-billing audit.

Metrics to Track in a Hypertension RPM Program

How ChronicSync Can Help

Hypertension RPM becomes difficult to manage when patient enrollment, connected-device data, monitoring days, treatment-management activities, clinical communication and billing review are spread across separate systems.

ChronicSync is designed to help practices organize longitudinal care and remote-monitoring workflows in a structured environment.

A well-designed workflow can help care teams track patient participation, document activities, maintain clear program boundaries, coordinate follow-up and identify missing information before monthly billing review.

For practices offering both CCM and RPM, maintaining separate activity and time records can also reduce the risk of duplicate documentation.

Start your ChronicSync Free Pilot and explore a structured approach to chronic care and remote patient monitoring.

Frequently Asked Questions

Does Medicare cover RPM for hypertension?

Medicare covers qualifying Remote Patient Monitoring services, and CMS specifically uses hypertension with a connected blood pressure cuff as an RPM example. The service must satisfy applicable medical-necessity, device, documentation and billing requirements.

Does a hypertension patient need two chronic conditions for RPM?

No. The two-chronic-condition requirement applies to CCM, not to RPM simply because remote monitoring is being furnished. CMS states RPM may be used for acute and chronic conditions when applicable requirements are met.

Can a normal home blood pressure cuff qualify for Medicare RPM?

The RPM device must satisfy applicable medical-device requirements and digitally transmit the physiologic information. A basic cuff requiring a patient to manually report readings is not equivalent to automatically transmitted RPM device data.

What is CPT 99445?

CPT 99445 is a new 2026 RPM code representing the shorter device-supply monitoring pathway for 2 through 15 days during the applicable 30-day period.

What is CPT 99454?

CPT 99454 is the established RPM device-supply pathway associated with the longer monitoring-day requirement. Current CMS material identifies it with 16 or more days during a 30-day period.

What is CPT 99470?

CPT 99470 is a new 2026 RPM treatment-management code for the shorter initial 10-minute pathway when applicable requirements are satisfied.

What is CPT 99457?

CPT 99457 is an established RPM treatment-management service associated with the first 20 minutes during a calendar month and includes an applicable interactive communication requirement.

Can RPM and CCM be billed for the same hypertension patient?

Potentially yes. CMS permits qualifying remote monitoring and care-management services concurrently when each independently satisfies its requirements and the same time and effort are not counted twice.

Can patients manually enter blood pressure readings for RPM?

Medicare RPM device services are based on physiologic information that is digitally and automatically collected and transmitted by an appropriate connected medical device. Manually reported data should not be represented as automatically transmitted RPM device data.

Does RPM replace regular hypertension appointments?

No. RPM supplements the patient's clinical care and should not replace medically necessary office visits, diagnostic evaluation, urgent care or emergency services.

Should every hypertension patient be enrolled in RPM?

No. The treating practitioner should determine whether remote physiologic monitoring is medically appropriate and necessary for the individual patient.

Sources

• CMS: Remote Patient Monitoring
• CMS Medicare Learning Network: Telehealth and Remote Patient Monitoring
• CMS: CY 2026 Medicare Physician Fee Schedule Final Rule

This article is provided for educational purposes only and does not constitute medical, legal, coding, reimbursement, compliance or billing advice. Blood pressure treatment decisions and monitoring protocols should be established by appropriately qualified healthcare professionals. CPT, CMS, Medicare Administrative Contractor, Medicare Advantage and commercial payer requirements may change. Verify the current CPT code set and applicable payer requirements before furnishing or billing services.