Remote Patient Monitoring Billing: Make the New RPM Codes Work

A patient transmits blood-pressure readings for nine days, then stops. Your clinical team reviews the readings, reaches the patient, and spends 14 documented minutes managing treatment during the month. Under an outdated remote patient monitoring charge workflow, that episode might disappear into a “threshold not met” work queue. Under Medicare’s 2026 framework, it deserves a closer look—not an automatic charge, but a review against the newer billing pathways.

The 2026 Medicare Physician Fee Schedule added options for shorter monitoring periods and shorter treatment-management intervals. By October, practices should be testing whether those changes actually reached their billing systems, vendor agreements, and clinical workflows. A code added to a fee schedule does not automatically become a correctly documented, covered, payable service.

The opportunity is specific: capture medically necessary remote patient monitoring, or RPM, that satisfies the new requirements without turning every incomplete monitoring month into a billable event. With practices reviewing year-end performance and setting next year’s budgets, the useful question is no longer whether RPM has new codes. It is whether the program can distinguish earned revenue from attractive-looking charges that will not survive review.

1. Know Exactly What the New RPM Codes Changed

Effective January 1, 2026, Medicare’s RPM framework includes CPT 99445 for device supply and data transmission involving two to 15 days of readings within a 30-day period. The existing device-supply code, 99454, remains the pathway for a qualifying period with at least 16 days of readings. The lower-day code is an alternative for the applicable period, not an additional payment layered onto the longer-day code.

The other important addition is CPT 99470, covering the first 10 minutes of qualifying RPM treatment-management services during a calendar month, with the required interactive communication. Operationally, it provides a pathway for qualifying management totaling 10 to 19 minutes. CPT 99457 remains the initial code for 20 minutes, with 99458 addressing additional qualifying 20-minute increments.

That creates two separate choices: a device-supply pathway based on data days and a treatment-management pathway based on eligible time and communication. Neither choice establishes eligibility for the other. A practice may have sufficient device data without billable treatment management, or qualifying management without meeting the device-supply threshold.

CMS’s Calendar Year 2026 Medicare Physician Fee Schedule final rule and the current CPT descriptors are the starting references. Configure from those requirements and applicable Medicare guidance—not from a vendor slide that reduces the change to “RPM now pays after two days.” That shorthand leaves out almost everything a reviewer needs.

2. Keep Medical Necessity Ahead of the Charge Opportunity

A shorter threshold does not make a device shipment medically necessary. The record still needs to explain why monitoring physiologic information supports management of the patient’s condition. A diagnosis copied into a template is weaker than a concise plan identifying the parameter being monitored, the clinical concern, and how the team will respond to meaningful changes.

For Medicare RPM, the equipment must meet the applicable definition of a medical device and digitally transmit physiologic data. A patient manually typing home readings into a portal is not interchangeable with the connected-device data required for these device-supply services. Do not confuse meeting the medical-device definition with a blanket requirement that every product be described as “FDA approved.”

Medicare also generally requires an established patient relationship for RPM. Obtain and document patient consent, including the financial discussion appropriate to the patient’s coverage. Medicare Part B cost sharing generally applies; a monitoring program should not be presented as automatically free.

The new low-day pathway is particularly vulnerable to weak enrollment practices. If nearly every patient produces only a few readings, investigate before celebrating the charge volume. Some patients may appropriately need shorter monitoring. Others may not understand the equipment, lack connectivity, or have been enrolled without a workable clinical plan. Those are different situations and should not share one default explanation.

3. Build Around Two Clocks, Not One Monthly Report

RPM has a deceptively simple timing problem: device-supply services operate on a 30-day period, while treatment-management services operate on a calendar month. Those periods can overlap without matching. A report labeled “October RPM” may therefore be insufficient to support either charge unless the underlying dates remain visible.

Suppose a patient’s device period begins October 8 and ends November 6. The qualifying data-day count belongs to that 30-day interval. Treatment-management minutes performed in October belong to October’s management calculation; November minutes belong to November’s. Do not move work between months to clear a threshold, or restart the device period on November 1 merely because the billing department closes its monthly batch.

The billing system should retain distinct fields for the device-period start and end, qualifying data days, calendar-month management minutes, and interactive communication. It should also identify previously billed intervals so that corrections do not produce overlapping device claims.

Before releasing charges, test boundary cases: enrollment near month-end, a replacement device, a temporary transmission outage, and a patient who resumes monitoring after a gap. Ask staff to explain which dates support each proposed code. If the answer requires reconstructing the episode from three spreadsheets, the workflow needs repair before volume grows.

4. Count Data Days Without Inflating Them

The device-supply threshold concerns days with qualifying readings, not the number of readings. Twenty blood-pressure measurements taken on one day do not become 20 monitoring days. Nor should two connected devices automatically create two separately payable device-supply episodes for the same patient and period.

A reliable data feed needs more than a dashboard total. It should preserve enough information to connect the reading to the patient, device, and relevant date. Duplicate transmissions, test readings, and records assigned to the wrong patient should not silently enter the billing count.

Technical exceptions deserve a written policy. For example, distinguish the measurement timestamp from the transmission timestamp when a device stores readings during a connectivity interruption. Do not let billing staff improvise a counting convention each time a batch arrives late. Validate the approach against the code requirements, Medicare guidance, and the system’s actual data behavior.

Use automated edits to route exceptions rather than automatically converting every low-use episode into 99445. A nine-day episode should trigger verification of the full service requirements. A one-day episode should not be rounded up. A period with enough qualifying days for 99454 should not generate both device-supply codes.

• Flag duplicate or overlapping device-supply periods before claim creation.
• Separate qualifying data days from total readings and device-connection days.
• Retain the underlying transmission evidence, not just the final count.
• Review unusually consistent minimum-threshold patterns for clinical and operational causes.

5. Make the Ten-Minute Pathway Clinically Defensible

CPT 99470 does not turn a brief administrative call into treatment management. Qualifying time must involve the work described by the service and be attributable to eligible personnel. Shipment tracking, insurance verification, and appointment scheduling should not enter the treatment-management total merely because they support the RPM program.

Interactive communication remains essential. Medicare describes this as real-time, synchronous, two-way audio communication that can be enhanced with video or other data transmission. A portal message alone, an unanswered call, or a voicemail should not be treated as satisfying that requirement.

The time record should show who performed the work, what was done, when it occurred, and how much eligible time was spent. A useful note connects the monitored information to an assessment or management action: review of concerning trends, discussion of symptoms, reinforcement of a treatment plan, or escalation to the treating practitioner. Not every contact requires a medication change, but the record should show actual clinical management.

Set mutually exclusive initial-code logic. A qualifying month with 14 minutes points toward the shorter pathway; a qualifying month with 24 minutes points toward 99457 rather than stacking 99470 onto it. Apply the additional-time requirements for 99458 separately. Never count the same minutes twice across RPM and another time-based service.

Clinical staff may furnish qualifying Medicare RPM management under the applicable general-supervision rules. That does not eliminate the billing practitioner’s responsibility for the service, supervision arrangement, or documentation. An outside monitoring team needs clear escalation procedures and accessible records—not merely a monthly invoice listing minutes.

6. Follow One Patient Through the Entire Charge Decision

Consider a hypothetical established Medicare patient monitored for hypertension. During a defined 30-day device period, the connected cuff supplies qualifying readings on nine distinct days. During October, eligible staff document 14 minutes of treatment-management work, including a live conversation about the readings and the care plan. The record supports medical necessity, consent, and the remaining service requirements.

That fact pattern may support 99445 for the device period and 99470 for October’s management. The important word is “may”: billing still depends on coverage, the complete documentation, correct claim construction, and the absence of conflicting or duplicate services. The data-day count alone cannot establish that everything is payable.

Change one fact and the charge decision changes. If the management total is nine minutes, the practice should not round it to 10. If no qualifying interactive communication occurred, accumulating enough review time does not cure the missing communication. If 18 qualifying data days occurred, the device-supply pathway changes, but the management code still depends on its separate monthly requirements.

Finally, check whether another practice or monitoring company is already furnishing overlapping RPM services. A patient can accept a second device without understanding that the programs may conflict. Intake should ask about existing monitoring, and staff should resolve ownership before the practice invests clinical work in an episode it cannot appropriately bill.

7. Verify Payer Adoption and the Billing Entity

Medicare recognition of the new codes does not establish identical payment across Medicare Advantage, commercial insurance, and Medicaid. Coverage obligations, processing instructions, contract terms, and payment methodologies are related but distinct. A payer may need a coding-system update even when the underlying benefit question is settled.

Build a payer matrix specifically for the new RPM codes. Record the relevant product, effective date, coverage policy, authorization requirements if applicable, billing instructions, and reimbursement method. Preserve the written source or a documented payer response. “The representative said RPM is covered” is not a sufficient answer to whether a particular code will process correctly.

Also verify the practitioner and entity actually submitting the claim. A vendor’s use of the practice name does not establish that its proposed billing arrangement is valid. Confirm enrollment, reassignment where applicable, network participation, supervision, and access to the supporting records.

Whether this work is handled internally or through provider credentialing services, connect enrollment findings to the charge workflow. A provider who is clinically authorized to manage the patient may still have an unresolved payer-enrollment issue. Do not let a clean RPM dashboard conceal a billing-identity problem.

Use early remittances to validate the matrix. If a new code rejects as unrecognized or noncovered, investigate the specific payer and product before changing the claim. Never substitute the older, higher-threshold code merely because the payer’s system accepts it.

8. Reprice Vendor Economics Around Collectible Revenue

The lower thresholds can improve revenue capture, but they can also make an expensive monitoring arrangement look healthier on paper than it is in cash. A vendor may charge per enrolled patient, per shipped device, per active patient, or per completed management episode. Those units do not necessarily correspond to payable services.

Review the contract using actual collections by code and payer—not a single advertised monthly RPM reimbursement figure. Medicare amounts vary with the applicable payment inputs, and contracted payer reimbursement may differ. Device logistics, clinical labor, replacement equipment, connectivity support, and patient collection effort all belong in the margin calculation.

Separate patients who never start transmitting from those who complete a qualifying lower-day period. Separate clinically appropriate shorter management from undocumented work that cannot be billed. Otherwise, management may wrongly conclude that a staffing problem has been solved by adding a new charge code.

An internal billing team or outside medical billing services should be able to reconcile each released charge to its evidence and each payment to the contract assumptions. That reconciliation also needs to account for patient responsibility, refunds, reversals, and vendor fees incurred on nonbillable episodes.

• Define when vendor fees begin and end, including inactive-patient treatment.
• Require exportable data-day, communication, and time records.
• Assign responsibility for payer rejections, corrected claims, and audit support.
• Compare net collections with total program costs by payer and service pathway.

9. Run a Targeted Fourth-Quarter RPM Audit

October is a useful point to test whether the 2026 changes were implemented correctly. Sample across pathways rather than reviewing only the largest payments: shorter and longer device periods, shorter and longer management months, nonbillable episodes, rejected claims, and patients whose vendor charges continued after monitoring stopped.

For each episode, reconstruct the service from source records to remittance. Confirm the clinical rationale, consent, device qualification, data-day count, relevant period, eligible management time, interactive communication, billing practitioner, and payment. Also look for services that were supported but suppressed by obsolete system rules.

A focused lookback may reveal missed revenue, but rebilling is not simply a code-replacement exercise. Check timely-filing limits, payer implementation dates, documentation available from the original service, and corrected-claim procedures. Do not create retrospective time records or add clinical assertions solely to make an old episode billable.

Assign findings to their actual owners. Missing transmission evidence belongs with technology and operations. Unsupported time belongs with clinical workflow and supervision. An unrecognized code may belong with payer configuration. Enrollment defects belong with the credentialing and enrollment function. Sending every failure to the biller guarantees that the same failures return.

The practical standard for next year’s budget is straightforward: count revenue only when the practice can explain the service, prove the threshold, identify the responsible practitioner, and support the payer’s payment. The new RPM codes reward qualifying work that older thresholds left unpaid. They do not replace the need to show what happened.