The 2026 Medicare Fee Schedule Through an Operational Lens: What RPM and CCM Teams Should Review

Annual Medicare updates often draw attention to new codes and revised payment amounts. For organizations operating Medicare care management programs, however, the 2026 update has a broader operational impact. It affects how Remote Patient Monitoring (RPM) and Chronic Care Management (CCM) activity is identified, documented, reviewed, and prepared for billing.

The most visible change is the addition of two RPM codes for shorter periods of data transmission and treatment management. The more important question for care teams is whether their systems and workflows can distinguish these new pathways from existing services without creating gaps, overlaps, or unsupported billing decisions.

Meeting Medicare care management requirements in 2026 will depend on more than updating a code table. Organizations also need to review system logic, staff guidance, documentation practices, pre-billing controls, and financial forecasts.

What Changed for RPM in 2026

Under the CY 2026 Medicare Physician Fee Schedule Final Rule, CMS adopted two new RPM codes effective January 1, 2026. CPT 99445 covers device supply when physiologic data are transmitted on 2–15 days within a 30-day period. CPT 99470 covers the first 10 minutes of treatment management during a calendar month and requires at least one live, real-time, interactive communication with the patient or caregiver.

The longer-duration pathway remains available. CPT 99454 applies to 16–30 days of transmitted data, CPT 99457 covers the first 20 minutes of treatment management, and CPT 99458 covers each additional 20 minutes.

These new codes apply to RPM, not CCM. CCM remains operationally relevant because the two programs may share patients, staff, documentation, and monthly time-tracking processes.

The shorter and longer pathways are alternatives rather than cumulative services. CPT 99445 is not reported with CPT 99454 for the same 30-day period, and CPT 99470 is not added to CPT 99457 for the same calendar month. The selected code must reflect the service that was actually furnished.

This is the central operational change behind RPM reimbursement in 2026. Systems built around the previous 16-day and 20-minute thresholds must now distinguish different service levels without combining alternative pathways. Clinical need must continue to guide the service provided.

Reporting Periods Must Be Applied Correctly

Device supply and treatment management do not use the same time boundary. Device-supply codes are based on a 30-day period, while treatment-management time is measured by calendar month.

A system that treats those periods as identical may calculate the correct activity but assign it to the wrong reporting window. It must also distinguish the number of days on which qualifying data were transmitted from the total number of readings. Several readings received on one day do not represent several transmission days.

Organizations should test how their systems handle midmonth enrollment, partial months, periods that cross calendar months, and interruptions in transmission. If the device, monitoring platform, clinical record, and billing system define an “active day” or “completed time” differently, the discrepancy may not appear until pre-billing review.

Documentation Must Support the Service, Not Only the Threshold

Reaching a numerical threshold does not, by itself, establish that a reportable RPM service was completed. CMS guidance on Remote Patient Monitoring explains that RPM supports the management of acute and chronic conditions through connected medical devices that electronically transmit patient data. CMS has also clarified requirements related to the established patient relationship, patient consent, eligible devices, and automatic data transmission in its Physician Fee Schedule guidance on RPM services.

The new 10-minute pathway does not replace these requirements. Treatment management still requires at least one live, interactive communication with the patient or caregiver during the calendar month, as described in the CMS Telehealth and Remote Monitoring guidance.

Reviewing data, responding to an alert, preparing an internal note, or sending an asynchronous message may contribute to care, but those activities do not independently show that the required real-time communication occurred. The record should identify the contact type, participants, time, purpose, and connection to treatment management. Capturing this information as the work occurs gives the billing team clearer evidence for review.

Medicare RPM and CCM Need Shared Records With Clear Attribution

Remote Patient Monitoring and Chronic Care Management may support the same patient during the same month. That continuity can be clinically valuable, but the same time or effort should not be attributed to both reported services.

A patient conversation may address an RPM blood-pressure trend and a broader concern in the chronic care plan. Both may be appropriate, but the record must show which work supports RPM, which supports CCM, and how the time was assigned.

For teams reviewing CCM billing in 2026, a single monthly “care management” total does not provide enough detail. A shared clinical view with program-specific attribution preserves both care continuity and the distinctions needed for billing review. CMS outlines the broader service framework in its Chronic Care Management Services guidance.

Pre-Billing Review Should Focus on Exceptions

A pre-billing process that checks only whether a threshold was reached is no longer sufficient. Review should also confirm that the correct pathway and reporting period were used, the required communication is documented, and the activity was not assigned to another program.

This does not require every patient month to be reconstructed manually. A more sustainable approach is to direct human review toward exceptions: alternative codes proposed for the same period, overlapping RPM and CCM time, inconsistent transmission-day counts, missing communication details, or a proposed code without the supporting service elements.

The billing team should receive the proposed service together with enough context to evaluate it. Staff also need clear guidance on which activities belong to each program, what must be recorded, and when an incomplete record requires clarification. Final coding and billing decisions remain with the qualified professionals responsible for them.

Financial Forecasts Need Local, Code-Specific Data

According to the CMS CY 2026 Physician Fee Schedule Final Rule Fact Sheet, the 2026 conversion factor is $33.57 for qualifying Alternative Payment Model participants and $33.40 for practitioners who are not qualifying participants. Compared with the 2025 conversion factor of $32.35, these represent projected increases of 3.77% and 3.26%, respectively.

These percentages do not guarantee the same increase for every RPM or CCM service. Final payment also reflects the relative value assigned to each code, geographic adjustments, practitioner status, site of service, and other applicable rules.

Organizations should use the final CMS fee-schedule files, the correct payment locality and site of service, and applicable Medicare Administrative Contractor guidance. Shorter and longer RPM pathways should be modeled separately so that forecasts reflect realistic patterns of patient activity rather than one national estimate.

Preparing the Operating Model for 2026

A controlled transition begins with clear ownership of internal policy and continues through system configuration, staff education, scenario testing, and early post-implementation review.

Testing should cover different levels of transmission and treatment-management time, including a patient who also receives CCM. Each scenario should confirm that the workflow preserves the reporting period, the service performed, the required communication, and the program to which the time belongs.

After implementation, reviewing a sample of early patient months can reveal repeated issues, such as missing communication, differences between device and billing records, overlapping program time, or unusual use of a new code.

How Hoss Care Supports Medicare Care Management

The Hoss Care platform is designed as care execution infrastructure that connects program requirements with daily operational activity. For RPM and CCM teams, this can include patient eligibility, assigned work, patient contact, time capture, program attribution, and EHR-connected documentation.

Structured workflows can give teams a shared view of the patient while keeping RPM and CCM activity distinguishable. They can also improve traceability from the care activity to pre-billing review. Organizations assessing staffing capacity may consider HossClinical as an extension of the clinical team under the required direction and oversight of the responsible billing practitioner.

Technology does not replace clinical judgment, CPT guidance, CMS requirements, or the organization’s responsibility for coding and billing decisions. It can help teams apply approved policies more consistently and maintain documentation designed to support review.

The Operational Takeaway

The 2026 Medicare Fee Schedule does more than add two RPM codes. It introduces additional reporting pathways that depend on the service furnished, the applicable time period, the required communication, and the documentation supporting the work.

For Medicare care management organizations, the central question is not only what a new code may pay. It is whether the operating model can identify the correct service, document it when the work occurs, separate RPM from CCM activity, and move the record into pre-billing review without overlap or manual reconstruction.

Explore the Hoss Care blog for additional perspectives on Medicare care management, RPM, CCM, and connected care operations.

This article is for educational purposes and does not constitute legal, coding, or billing advice. Organizations should verify current CMS requirements, CPT guidance, and Medicare Administrative Contractor instructions applicable to their setting.

Sources

• CMS: Calendar Year 2026 Medicare Physician Fee Schedule Final Rule Fact Sheet

• CMS: CY 2026 Medicare Physician Fee Schedule Final Rule

• CMS: Remote Patient Monitoring

• CMS Medicare Learning Network: Telehealth & Remote Monitoring

• CMS Medicare Learning Network: Chronic Care Management Services