RPM Manual
The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.
Read the RPM Guide →Anthem updated CG-MED-91 to explicitly incorporate the 2026 “short-cycle” RPM/RTM coding structure, adding new 2–15 day device supply codes and new 10-minute treatment management codes.
Organizations that still run “16 days or nothing” device logic and “20 minutes or nothing” management logic will misbill unless they restructure eligibility, time capture, and documentation around the new descriptors.
How to use this page: This is an operational compliance guide based on publicly available payer and CMS sources. It is not legal advice. Use it to update workflows, billing logic, documentation standards, and payer-specific configurations.
Anthem’s CG-MED-91 (published December 18, 2025) explicitly adds 2026 RPM/RTM codes that split device supply into 2–15 days vs 16–30 days and add 10-minute treatment management options, so billing workflows must select codes based on the actual day-count tier and interactive-communication requirement rather than forcing episodes into legacy 16-day/20-minute assumptions.
CG-MED-91 lists a publish date of 12/18/2025. In the History section, Anthem states it “Updated Coding section with 01/01/2026 CPT changes,” adding 98979, 98984, 98985, 98986, 99445, and 99470.
Anthem’s update explicitly aligns its code list with 2026 CPT changes, supporting shorter monitoring episodes and a new 10-minute treatment-management increment. That changes how eligibility logic, time capture, and documentation must be structured.
Anthem requires documentation that RTM/RPM is clinically appropriate (not for convenience), the patient is at risk of clinically significant change, the patient cannot access regular outpatient care or needs between-visit monitoring, and monitoring is reasonably likely to prevent deterioration or adverse events. For RPM, Anthem specifies an FDA-recognized medical device that directly measures physiologic data.
The Definitions section states RPM is “longer than 16 days,” but the Coding section lists 99445 for 2–15 days. Operationally, treat the code descriptor as the controlling unit definition and treat the older sentence as stale text, while documenting medical necessity and the selected descriptor.
Legacy RPM programs often treated device supply as binary. Under Anthem’s 2026 list, that logic is wrong because 99445 exists for 2–15 days.
If workflows only bill after 20 minutes, they miss legitimate 10-minute cases. Anthem lists 99470 and 98979 for first 10 minutes with an interaction requirement.
Delaying billing until a patient “stabilizes” risks constructing claims that no longer match the defined 30-day period and invites inconsistencies if reviewed.
Anthem expects data assessment to detect acute change and prompt intervention. Device-only programs without documented assessment and response are misaligned to the criteria.
Anthem’s update treats RTM with the same structural rigor as RPM. Expect denials and audits to mature similarly.
If the descriptor defines a 2–15 day or 16–30 day unit in a 30-day period, then stretching or borrowing days across boundaries changes the unit you are claiming. Anthem’s list makes the unit boundaries explicit.
Both 99470 and 98979 require at least one real-time interactive communication within the calendar month. Billing without a defensible interaction record is a direct descriptor mismatch.
Even when the code is selected correctly by days and time, Anthem’s “ALL of the following” medical-necessity criteria can still trigger denial if the documentation does not show active assessment, patient risk/instability, and a likelihood of preventing deterioration or adverse events.
If medically necessary and documented, Anthem’s list includes 99445 and 98984–98986 for 2–15 days. The documentation still must meet the medical-necessity criteria.
Supply codes use a 30-day period, while management codes use calendar month time and require interactive communication within that month. Your system must track both units separately.
Anthem states RTM/RPM is not medically necessary when similar services are provided concurrently (for example, home health). Documentation should show why the monitoring is not duplicative.
The 2–15 day tier reduces pressure to “make up” missing days. Use the day-count tier achieved, or do not bill supply.
CMS MLN Matters MM14250 identifies 98984 and 98985 as new RTM device supply codes for 2–15 days and 98979 as a new RTM management code for the first 10 minutes, effective January 1, 2026, and discusses their “sometimes therapy” designation.
The CY 2026 PFS final rule fact sheet notes CMS will use OPPS hospital data to inform costs for some remote monitoring services. AMA commentary also highlights the shift toward OPPS-driven practice expense valuation for the RPM family, signaling more scrutiny of unit integrity.
Payer-by-payer support and adoption timelines. CG-MED-91 shows Anthem’s coding alignment, but benefit plans and claims edits can vary by line of business, and Anthem notes that plan language governs coverage.
The 2026 changes reflect a broader trajectory: CMS and payers are shifting remote monitoring from rigid, month-sized constructs to unit definitions that support short, clinically meaningful episodes (2–15 day supply; 10-minute management). Anthem adopting these descriptors in CG-MED-91 signals commercial utilization management is tracking the same shape.
At the same time, CMS is moving toward more auditable, data-driven valuation and rate-setting for remote monitoring services, including OPPS data use. Episode flexibility is increasing, but expectations for unit integrity and documentation consistency are also increasing.
FairPath’s billing engine automatically generates RPM/RTM billing codes, including the new 2026 codes and correct tier selection logic (2–15 vs 16–30 day device supply and 10-minute management options), so teams are not manually counting days or reconstructing time logs.
FairPath’s compliance engine can be configured payer-by-payer to deny or flag codes not supported by a specific line of business and to require prerequisite compliance artifacts (such as interactive communication) before a claim is marked billable.
FairPath is built on operational work, not theory. We publish the playbooks and checklists we use to keep programs compliant and profitable. Use them whether you run FairPath or not.
Browse the Expert Library →The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.
Read the RPM Guide →How to run Remote Therapeutic Monitoring for MSK, respiratory, and CBT workflows with the correct 9897x and 9898x rules.
Read the RTM Guide →Calendar-month operations for CCM: consent, initiating visit, care plan requirements, time counting, and concurrency rules.
Read the CCM Guide →The operator blueprint for Advanced Primary Care Management: eligibility, G0556–G0558 tiers, and monthly execution.
Read the APCM Playbook →