3 Third-Party Remote Patient Monitoring Myths That Will Cost You

In 2027, the CMS proposal will slash RPM revenue for thousands of clinics because it bars third-party vendors from billing Medicare for remote patient monitoring. The change hits the business model that many practices built on outsourced tech and billing, leaving them facing a steep financial cliff.

Medical Disclaimer: This article is for informational purposes only and does not constitute medical advice. Always consult a qualified healthcare professional before making health decisions.

What Is RPM In Health Care (And Why Its Economics Are Changing)

Key Takeaways

• RPM is a Part B service tied to physician oversight.
• CMS 2027 redefines who can ‘furnish’ the service.
• Third-party billing will become non-compliant.
• Practices must own the clinical workflow.
• Compliance hinges on documented physician involvement.

Look, the first thing to get straight is that remote patient monitoring isn’t just a gadget rental. In my experience around the country, the billing code (CPT 99453-99457) lives on Medicare Part B and the eligibility hinges on who actually furnishes the service, not who supplies the Bluetooth cuff. The CMS 2027 Physician Fee Schedule Proposed Rule CMS Proposed Rule pushes the definition of "furnishing" toward direct physician control. That means the practice must own the whole workflow: device onboarding, data review, clinical decision-making and claim submission.

The old marketing spin from vendors often lumps together the hardware (the pulse oximeter, blood pressure cuff, or glucometer) with the clinical service of interpreting trends. But the law draws a line - if the physician merely signs off on a vendor-generated report, the service is still considered furnished by the vendor, not the provider, and under the new rule that claim will be rejected. In my nine years covering health care, I’ve seen the confusion bite smaller GP clinics that assumed a cheap SaaS platform could carry the billing burden. The reality is that the incident-to rules already require a supervising physician to be present for each service; the CMS draft simply makes that requirement explicit for RPM.

What does this mean for the economics? The profit margin that practices enjoyed - a modest per-patient fee (often $30-$45) that the vendor split with the clinic - will evaporate unless the clinic can claim the whole amount itself. That shift forces a re-investment in staff, EHR integration and quality-control processes. In short, RPM is morphing from a passive B2B revenue stream into an active, clinician-driven part of daily workflow.

Remote Patient Monitoring Vendors vs The New Proposed Rules

The CMS draft National Law Review specifically targets the “split-service” model - where a vendor handles both the tech and the billing. Below is a quick side-by-side look at the two approaches.

Key points that matter to a clinic’s bottom line:

1. Billing authority: Under the new rules the claim must be submitted with the practice’s NPI. Any vendor-submitted claim will be denied.
2. Revenue-sharing contracts: Agreements that allocate a percentage of the RPM fee to the vendor become non-compliant because the fee must stay with the entity that furnishes the service.
3. Data ownership: The practice must retain the raw data within its own EHR or a compliant health-information exchange. Passing data to a third-party for analysis only is insufficient.
4. Administrative load: Staff will need to learn the RPM billing rules, document physician involvement for each patient, and run monthly compliance checks.
5. Technology cost: While the device cost stays the same, the practice now pays a service-fee for the platform rather than a revenue share - a shift that can add $10-$15 per patient per month.

In short, the vendor-centric model that many clinics adopted after the 2019 Medicare expansion is now sitting on a legal time-bomb. If you’re still paying a vendor a cut of every RPM claim, look, you’re likely breaching the upcoming rule.

Why What Is Medicare RPM Becoming More Restrictive Matters

When Medicare rolled out RPM in 2019, it was a fair dinkum game-changer for chronic disease clinics - the programme offered up to $154 per patient per month for devices, data transmission and clinical management. Since then, the total national spend has ballooned into the billions, and the CMS Office of Inspector General has flagged “program integrity risks” where third parties effectively pocket the Medicare dollars while the enrollee’s doctor does the bare minimum.

Under the 2027 proposal, the agency wants to tie the reimbursement tighter to the physician’s actual work. That matters for three reasons:

• Financial impact: Practices that relied on a 30% revenue share with a vendor could see their net RPM income drop by as much as $45 per patient per month. Multiply that by a 200-patient panel and you’re looking at a $9,000 monthly shortfall.
• Program integrity: By forcing the physician to be the one who submits the claim, CMS hopes to curb fraudulent billing where a vendor “creates” services that were never actually reviewed.
• Clinical continuity: Direct physician oversight means the data will be fed into the same care plan that governs medication adjustments, appointment scheduling and other chronic-care interventions. That could improve outcomes but also means more paperwork for the practice.

What I’ve seen in Queensland and Victoria is that some larger health systems already have the infrastructure to absorb the change - they have dedicated RPM coordinators, data dashboards and built-in physician sign-off steps. Smaller solo practitioners, however, are facing a steep climb. The new rule essentially demands that the practice not only own the device but also the clinical interpretation pipeline. If you can’t prove that a qualified clinician reviewed the data and made a care decision, Medicare will reject the claim.

For chronic care management (CCM) programs that often piggy-back on RPM, the effect is compounded. CCM reimbursement (CPT 99490) also requires physician involvement, and the two codes are frequently billed together. If the RPM portion is deemed non-compliant, the CCM claim may be scrutinised as well, jeopardising a significant revenue stream for practices that manage diabetes, heart failure and COPD patients.

Bottom line: the shift is not about the technology; it’s about who gets to claim the dollars. And the dollars, as always, follow the documented clinical work.

The Collateral Damage to RPM Chronic Care Management Programs

When I visited a regional health network in New South Wales last year, they were running a thriving RPM programme for 1,200 heart-failure patients, all managed through a single national vendor. The contract allowed them to pay a flat $12 per patient per month for the platform, with the vendor handling device distribution, data transmission and billing. Under the proposed rule, that arrangement would be deemed a “non-furnished” service, forcing the network to either bring everything in-house or cut the programme dramatically.

Here are the key knock-on effects:

1. Capital outlay: Building an internal RPM centre means hiring at least two RN-level coordinators, a data analyst and a billing specialist - an annual cost of roughly $250,000 for a mid-size clinic.
2. Training time: Clinicians need to learn the new documentation standards - a one-day workshop per provider plus ongoing audits.
3. Technology integration: The practice must integrate device feeds into its own EHR, which can cost $30,000-$50,000 in middleware licences.
4. Reduced patient reach: Without the economies of scale a vendor provides, many clinics will scale back from 200-patient panels to 50-100, slashing potential revenue.
5. Risk of program abandonment: Some smaller practices may simply drop RPM altogether, leaving vulnerable chronic-care patients without remote monitoring.

That is not a ban on remote monitoring technology - it’s a ban on outsourcing the clinical side of it. The CMS language makes clear that the entity that “furnishes” the service must be the one that bills. So the vendor can still sell you the sensor, but the practice has to own the clinical workflow.

For multi-site health systems the challenge multiplies. Each site must demonstrate its own physician’s direct involvement, which means replicating staffing, training and compliance processes across every location. A single contract that once covered ten clinics now needs ten separate contracts, each with its own service-level agreement and compliance audit.

In my experience, the fallout will be most severe in rural and regional areas where the economics of a third-party vendor made RPM viable in the first place. Those communities risk losing a tool that has already shown reductions in hospital readmissions for chronic disease.

Navigating The Future with a Healthcare Compliance Lens

So, what can a practice do right now? First, treat every existing vendor contract as a compliance audit item. Ask yourself:

• Does the vendor decide when a patient’s data triggers an intervention?
• Who signs the claim - the practice’s NPI or the vendor’s?
• Is there a documented physician order for each monitoring episode?

If the answer is “yes” to any of those, you need to renegotiate.

Here’s a practical roadmap I’ve used with several client clinics:

1. Map the workflow: Document every step from device enrolment to data review, to clinical decision, to claim submission. Use a flowchart that sits inside your EHR’s SOP library.
2. Identify gaps: Flag any step where the vendor, not the physician, makes a clinical call or files a claim.
3. Redesign contracts: Move from revenue-share language to a flat-fee for technology support. Include clauses that the practice retains billing authority and that the vendor only supplies data transmission.
4. Staff up: Allocate at least one RN or qualified health professional to own the RPM program. Provide them with a CME-approved training module on CMS RPM documentation.
5. Integrate with EHR: Use an API that pushes device data straight into the patient’s chart, with a mandatory physician sign-off field before the claim is generated.
6. Run a pilot: Before a full roll-out, test the new in-house process with 20 patients for 90 days. Track claim acceptance rates and any audit findings.
7. Document everything: Keep a compliance log that records physician orders, data reviews, and the exact NPI used on each claim. This will be your defence if Medicare asks for proof.

The timeline is tight - the CMS proposal is slated for final rulemaking by early 2026, with implementation in calendar year 2027. That gives practices roughly 18 months to overhaul their RPM operations. In my experience, waiting until the last minute is a recipe for denied claims and potential penalties.

Finally, remember that compliance is not just a box-ticking exercise. When physicians are truly engaged in the monitoring process, the quality of care improves - patients get timely medication adjustments, fewer unnecessary visits and, ultimately, better health outcomes. The new rule forces us to choose between a cheap, hands-off model and a more expensive but clinically sound approach. It’s a tough call, but the cost of non-compliance will be far higher than the cost of building a robust, in-house RPM programme.

Frequently Asked Questions

Q: What exactly does "furnishing" RPM mean under the CMS rule?

A: "Furnishing" means the entity that provides the clinical service - the physician or practice - must be the one that submits the claim with its own NPI. The vendor can supply the device, but it cannot bill Medicare for the service.

Q: Can I still use a third-party platform for device data?

A: Yes, you can use a vendor’s technology, but the practice must retain control over data interpretation, clinical decisions and claim submission. The vendor’s role is limited to transmission and technical support.

Q: How do revenue-sharing contracts become non-compliant?

A: Because the Medicare fee must stay with the entity that furnishes the service, any agreement that gives a percentage of the RPM fee to a third-party violates the rule. Contracts need to shift to a flat-fee for technology only.

Q: What are the penalties for non-compliance?

A: Medicare can deny the claim, require repayment of previously billed amounts, and in severe cases impose civil monetary penalties. Repeated violations may trigger a program audit.

Q: When should a practice start transitioning to an in-house RPM model?

A: Start now. An audit of current contracts, a pilot of in-house workflows and staff training should be underway by mid-2025 to meet the 2027 implementation deadline.