Updated for 2026. Remote Patient Monitoring (RPM), also called Remote Physiologic Monitoring, can help practices manage patients between office visits using connected devices that automatically transmit physiologic data.
RPM billing, however, requires more than shipping a blood-pressure cuff or recording monthly minutes. Medicare expects the service to be medically necessary, supported by an established patient relationship, use an appropriate connected medical device, include required monitoring activity, and have documentation supporting the specific CPT code billed.
This practical 2026 RPM documentation checklist can help practices review their workflow before claim submission.
RPM Documentation Checklist at a Glance
- Confirm an established patient relationship.
- Document the acute or chronic condition being monitored.
- Document why RPM is medically reasonable and necessary.
- Obtain and document patient consent.
- Use a device that meets applicable medical-device requirements.
- Confirm physiologic data is electronically and automatically transmitted.
- Document patient device setup and education when billing the setup service.
- Document the number of qualifying monitoring days for device-supply codes.
- Select the appropriate 2-15 day or longer monitoring code.
- Document treatment-management time separately.
- Document required interactive communication for applicable treatment-management codes.
- Identify the practitioner and clinical staff performing each activity.
- Confirm only one practitioner is billing remote monitoring during the applicable 30-day period.
- Do not bill RPM and RTM concurrently for the same patient.
- Avoid duplicate time with CCM, PCM, TCM, BHI, or other time-based services.
1. Confirm an Established Patient Relationship
CMS states that Remote Physiologic Monitoring requires an established patient relationship.
Your record should support that the patient has an established relationship with the practitioner responsible for the RPM service.
This is an important compliance point because HHS OIG has specifically identified RPM billing involving patients with no prior history with the billing medical practice as an area warranting additional scrutiny.
2. Identify the Condition Being Monitored
CMS allows RPM for both acute and chronic conditions.
The medical record should clearly identify the condition or clinical issue that makes remote physiologic monitoring appropriate.
Examples may include:
- Hypertension
- Heart failure
- Diabetes
- COPD
- Post-treatment physiologic monitoring
- Other acute or chronic conditions when RPM is medically necessary
A diagnosis alone does not establish that RPM is appropriate. Documentation should connect the monitored physiologic parameter to the patient's treatment or management needs.
3. Document Medical Necessity
CMS requires remote monitoring to be medically reasonable and necessary.
Consider documenting:
- Why remote monitoring is needed
- Which physiologic parameter will be monitored
- How the transmitted data will affect treatment or management
- The expected monitoring period
- Clinical goals for monitoring
Example
RPM initiated for management of hypertension because home blood-pressure trends are needed to evaluate treatment response between office visits and guide medication-management decisions.
4. Obtain and Document Patient Consent
CMS requires patient consent for remote monitoring and permits consent to be obtained when RPM services are furnished.
The medical record should indicate that the patient agreed to participate in the RPM service.
Your organization may also document:
- The purpose of RPM
- How the device will be used
- How data will be transmitted
- Patient responsibilities
- Potential Medicare cost sharing
5. Verify the Device Meets Medicare RPM Requirements
CMS requires RPM to use an internet-connected medical device that automatically transmits physiologic data.
The device should meet the applicable FDA definition of a medical device.
Examples may include connected:
- Blood-pressure cuffs
- Weight scales
- Pulse oximeters
- Glucose-monitoring devices when applicable
- Other qualifying physiologic monitoring devices
6. Confirm Data Is Automatically Transmitted
RPM is different from simply asking a patient to write measurements in a notebook or manually send readings.
CMS states that the physiologic data used for RPM must be electronically collected and automatically transmitted to a secure location where the healthcare team can access it for analysis and treatment management.
Potential Documentation
Patient supplied connected blood-pressure monitor configured to automatically transmit readings to secure RPM platform.
7. Document Device Setup and Patient Education
CPT 99453 represents the initial RPM device setup and patient education component.
When reporting the setup service, documentation should support that the patient received appropriate instruction.
This may include:
- Device activation
- Correct device placement or use
- How and when measurements should be taken
- Confirmation that data transmission is working
- Troubleshooting instructions
- When the patient should contact the care team
HHS OIG has highlighted concerns that some Medicare RPM patients did not receive all major components of RPM, including device education and setup.
8. Track Monitoring Days Accurately
For 2026, CMS recognizes different RPM device-supply pathways based on the number of qualifying monitoring days within a 30-day period.
CodeGeneral Monitoring Period99445Device supply for 2-15 days of qualifying monitoring within 30 days99454Device supply for the longer monitoring period described by the current code, generally 16-30 days within 30 days
The billing system should use actual device data to determine the number of qualifying monitoring days rather than assuming every enrolled patient automatically qualifies for a device-supply code.
9. Document the Actual Number of Monitoring Days
Your RPM platform should make it possible to determine:
- First qualifying transmission date
- Last qualifying transmission date
- Number of qualifying days with transmitted physiologic data
- Whether the code-specific monitoring threshold was met
Example
Connected blood-pressure monitor transmitted qualifying physiologic readings on 12 separate days during the 30-day monitoring period.
The billing team can then evaluate the applicable 2026 device-supply code based on the documented monitoring period.
10. Do Not Confuse Readings With Monitoring Days
CMS's current patient-facing RPM guidance notes that connected devices must collect and transmit sufficient readings, while the billing code descriptors distinguish monitoring periods based on qualifying days.
Your software should therefore retain both the transmitted data and the dates on which qualifying monitoring occurred.
A large number of readings on a single day should not automatically be interpreted as multiple monitoring days.
11. CPT 99470: First 10 Minutes of RPM Treatment Management
For 2026, CPT 99470 provides a treatment-management pathway beginning with the first 10 minutes of qualifying RPM management activity during the calendar month.
Documentation should identify:
- Who performed the treatment-management service
- How much qualifying time was spent
- What RPM data was reviewed
- How the data affected patient management
- Required communication with the patient or caregiver
Do not select a treatment-management code solely from the time total. Verify all applicable CPT and Medicare requirements.
12. CPT 99457: RPM Treatment Management
CPT 99457 represents the traditional first 20 minutes of qualifying RPM treatment-management services during a calendar month.
The service involves treatment-management activity based on the patient's remotely collected physiologic data and includes required interactive communication with the patient or caregiver.
13. CPT 99458: Additional RPM Treatment Management
CPT 99458 is an add-on code for additional qualifying RPM treatment-management time after the applicable base treatment-management requirements are met.
Practices should document actual additional qualifying time and follow current CPT, CMS, Medicare Administrative Contractor, and payer instructions before reporting add-on units.
14. Document Interactive Communication
Applicable RPM treatment-management codes include an interactive communication component with the patient or caregiver.
Documentation should identify:
- Date of communication
- Who participated
- Mode of permitted communication
- Clinical issue discussed
- RPM data reviewed
- Treatment or management action resulting from the communication
Example
Reviewed transmitted blood-pressure trend with patient. Discussed persistent elevated morning readings and medication adherence. Practitioner notified for treatment review; patient advised to continue monitoring according to established plan.
15. Document What Was Done With the RPM Data
Collecting data alone does not demonstrate the treatment-management component of RPM.
Your documentation should show how the healthcare team used the information.
Examples include:
- Reviewing blood-pressure trends
- Evaluating weight changes
- Reviewing oxygen-saturation trends
- Identifying potentially significant physiologic changes
- Communicating findings to the practitioner
- Adjusting or reinforcing the treatment plan when clinically appropriate
16. Identify Who Performed Each RPM Activity
A strong RPM record should identify the practitioner or staff member responsible for each service.
Consider recording:
- Name
- Role
- Date
- Activity type
- Duration when applicable
- Clinical outcome
This is especially important for treatment-management codes and incident-to workflows involving clinical staff.
17. Only One Practitioner Can Bill Remote Monitoring During the Applicable 30-Day Period
CMS states that only one practitioner may bill remote monitoring services for a patient during a 30-day period.
Before enrolling a patient, consider checking whether another provider is already furnishing RPM.
This can be particularly important when a patient is being managed simultaneously by primary care and multiple specialists.
18. Do Not Bill RPM and RTM Together
CMS states that Remote Physiologic Monitoring and Remote Therapeutic Monitoring cannot both be billed concurrently for the same patient.
Your patient-enrollment workflow should therefore identify whether the patient is already receiving RPM or RTM before activating another monitoring program.
19. RPM May Be Billed With CCM — But Do Not Double Count Time
CMS permits RPM to be furnished concurrently with Chronic Care Management when the requirements of both services are independently satisfied.
The same time and effort cannot be counted twice.
Incorrect
A care manager spends 12 minutes reviewing transmitted blood-pressure data and communicating with the patient, then records the same 12 minutes toward both RPM and CCM.
Better Documentation
- RPM: 12 minutes reviewing transmitted blood-pressure data and conducting qualifying treatment-management communication.
- CCM: Separate activity coordinating nephrology follow-up and updating the comprehensive chronic-care plan.
20. Review Other Concurrent Care-Management Services
CMS allows RPM or RTM — but not both together — to be furnished concurrently with several care-management services when their separate requirements are met and time and effort are not counted twice.
Examples include:
- Chronic Care Management
- Principal Care Management
- Transitional Care Management
- Behavioral Health Integration
- Chronic Pain Management
Maintain program-specific activity records when multiple services are active.
21. Maintain Device Inventory and Assignment Records
HHS OIG has identified billing for multiple monitoring devices for the same Medicare enrollee as a useful indicator for potential scrutiny.
Your organization should consider maintaining:
- Device identifier
- Device type
- Patient assignment
- Activation date
- Replacement date
- Return date when applicable
- Reason for replacement
This can help prevent accidental duplicate device billing and strengthen audit readiness.
22. Review Enrollment Source
RPM should be based on a legitimate patient-practitioner relationship and medical necessity rather than indiscriminate device enrollment.
HHS OIG has warned Medicare beneficiaries about RPM fraud schemes involving unsolicited devices and enrollment unrelated to appropriate clinical care.
Practices should maintain clear documentation showing how and why the patient entered the RPM program.
23. Document Discontinuation
Your RPM workflow should also record when monitoring stops.
Document:
- Date RPM ended
- Reason for discontinuation
- Device return or reassignment when applicable
- Final clinical follow-up
- Whether another monitoring service replaced RPM
This helps prevent claims from continuing after the patient is no longer actively receiving the service.
Sample RPM Documentation Entry
Example: Established patient with hypertension enrolled in RPM after practitioner determined remote blood-pressure monitoring was medically necessary to evaluate treatment response. Patient consent documented. Connected blood-pressure cuff supplied and device-use education completed. Device automatically transmitting readings to secure RPM platform. During current period, qualifying readings received on 14 days. RPM team reviewed transmitted trends and documented separate treatment-management communication with patient regarding elevated morning readings and medication adherence.
Sample RPM Treatment-Management Note
Example: Reviewed automatically transmitted blood-pressure readings showing persistent elevation over previous week. Discussed readings and medication adherence with patient through qualifying interactive communication. Patient denied new symptoms. Information escalated to supervising practitioner for treatment review. RPM treatment-management time documented separately from CCM activity.
RPM Internal Audit Checklist
Review ItemStatusEstablished patient relationship supportedPass / ReviewCondition documentedPass / ReviewMedical necessity supportedPass / ReviewConsent documentedPass / ReviewConnected medical device verifiedPass / ReviewAutomatic data transmission verifiedPass / ReviewSetup and education documentedPass / ReviewMonitoring days supportedPass / ReviewCorrect device-supply code selectedPass / ReviewTreatment-management time supportedPass / ReviewInteractive communication documentedPass / ReviewDuplicate time reviewedPass / ReviewNo concurrent RPM and RTMPass / ReviewSingle RPM billing practitioner confirmedPass / Review
Common RPM Documentation Mistakes
1. No Clear Medical Necessity
The record should explain why remote physiologic data is needed to manage the patient's condition.
2. Using Manually Reported Data as if It Were Automatically Transmitted RPM Data
CMS requires RPM physiologic data to be electronically and automatically collected and transmitted using an appropriate connected medical device.
3. Not Tracking Monitoring Days
Device-supply billing depends on the applicable code's monitoring-day requirements.
4. Billing Treatment Management Without Supporting Communication
Applicable treatment-management codes require the communication and management elements described by current CPT and Medicare rules.
5. Counting the Same Minutes Under CCM and RPM
CMS permits concurrent services but prohibits counting the same time and effort twice.
6. Billing RPM and RTM Together
CMS states that the two remote-monitoring families cannot be billed concurrently for the same patient.
7. Multiple Practitioners Billing RPM
CMS permits only one practitioner to bill remote monitoring for a patient during the applicable 30-day period.
8. Continuing Billing After Monitoring Ends
Maintain clear discharge and device-status records so billing stops when the service is no longer being furnished.
2026 RPM Pre-Billing Checklist
- Established patient relationship confirmed
- Acute or chronic condition documented
- Medical necessity documented
- Patient consent documented
- Appropriate connected medical device supplied
- Automatic electronic transmission verified
- Device setup documented when applicable
- Patient education documented when applicable
- Qualifying monitoring days calculated
- 99445 vs 99454 device-supply pathway reviewed
- Treatment-management time documented separately
- 99470 vs 99457 treatment-management pathway reviewed
- 99458 additional time reviewed when applicable
- Interactive communication documented when required
- Staff and practitioner identities recorded
- Only one RPM billing practitioner confirmed
- No concurrent RPM and RTM billing
- Duplicate CCM, PCM, TCM, BHI, or chronic-pain-management time reviewed
- Device assignment records reviewed
- Current CMS, CPT, MAC, and payer rules verified
Why RPM Audit Readiness Matters
HHS OIG currently lists an active audit of Medicare Part B RPM services to determine whether providers furnished and billed RPM in accordance with Medicare requirements.
OIG has also reported that Medicare RPM payments exceeded $500 million in 2024 and has developed billing measures to identify practices that may warrant additional scrutiny.
These findings make accurate patient selection, device documentation, monitoring records, and program-specific billing controls increasingly important.
How ChronicSync Can Help
RPM documentation becomes difficult when connected-device data, patient communications, monitoring days, treatment-management activity, and care-management programs are spread across disconnected systems.
ChronicSync helps care teams organize remote-monitoring workflows, maintain structured patient documentation, track ongoing activity, and improve visibility across RPM and chronic-care programs.
A structured workflow can help clinical and billing teams review documentation before claims are submitted and identify duplicate or incomplete activity earlier.
Start your ChronicSync Free Pilot and explore a more organized approach to Remote Patient Monitoring and Chronic Care Management.
Frequently Asked Questions
What documentation is required for Medicare RPM?
The record should support an established patient relationship, the monitored condition, medical necessity, consent, use of an appropriate connected device, automatic data transmission, applicable monitoring days, treatment-management activity, and other requirements for the specific RPM code billed.
Does RPM require an established patient relationship?
Yes. CMS's current remote-monitoring guidance states that Remote Physiologic Monitoring requires an established patient relationship.
Can RPM be used for acute conditions?
Yes. Medicare broadly covers RPM for medically necessary monitoring of acute or chronic conditions.
Does RPM data have to transmit automatically?
Yes. CMS requires RPM physiologic data to be electronically collected and automatically transmitted through an appropriate connected medical device.
What is CPT 99445?
CPT 99445 is a 2026 RPM device-supply code for qualifying monitoring over 2-15 days within a 30-day period.
What is CPT 99470?
CPT 99470 is a 2026 RPM treatment-management code representing the first 10 minutes under its applicable code requirements.
Can CCM and RPM be billed together?
Yes. CMS permits concurrent RPM and CCM when each service independently meets its requirements and the same time and effort are not counted twice.
Can RPM and RTM be billed together?
No. CMS states that RPM and RTM cannot be billed concurrently for the same patient.
Is Medicare auditing RPM?
HHS OIG currently lists an active audit of Medicare Part B RPM services focused on whether providers furnished and billed the services in accordance with Medicare requirements.
Sources
- CMS: Remote Patient Monitoring
- CMS Medicare Learning Network: Telehealth & Remote Monitoring
- HHS OIG: Billing for Remote Patient Monitoring in Medicare
- HHS OIG: Audit of Medicare Part B Remote Patient Monitoring Services
This checklist is provided for educational purposes only and does not constitute medical, legal, coding, reimbursement, compliance, or billing advice. CPT, CMS, Medicare Administrative Contractor, and payer requirements can change. Verify the current code set and payer requirements before submitting claims.