Remote Patient Monitoring in Australia: What Medicare Covers and What Private Insurers Won’t

Remote patient monitoring (RPM) is a Medicare-approved service that uses digital devices to track patients’ vitals at home, and as of 2025 Medicare reimburses it under CPT codes 99453-99457. In plain English it lets doctors keep an eye on chronic conditions without the patient having to come into the clinic every week. The idea sounds simple, but the billing rules, insurer quirks and emerging tech make it anything but.

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 Remote Patient Monitoring (RPM)?

When I first covered telehealth back in 2019, the buzz was all about video calls. Today, RPM is the next frontier - it’s the collection of physiologic data (blood pressure, glucose, weight, oxygen saturation) via Bluetooth-enabled wearables or home-based sensors, which then flow straight into the electronic health record.

In my experience around the country, a typical RPM setup looks like this:

• Device prescription: A GP or specialist orders a sensor kit for a chronic condition such as heart failure or COPD.
• Patient onboarding: A nurse or allied health professional shows the patient how to wear the sensor and sync it to a smartphone app.
• Data transmission: The device sends readings to a secure cloud platform every few minutes or hours.
• Clinical review: The health team receives alerts when values fall outside preset thresholds.
• Intervention: The clinician may call, adjust medication, or schedule a face-to-face visit based on the data.

The Australian Digital Health Agency reports a steady rise in RPM pilots, especially in regional NSW and Queensland, where travel distances make home monitoring a lifesaver. Yet, the majority of primary care practices still haven’t nailed the billing side - a gap that costs them up to $647,000 a year in missed Medicare revenue, according to CMS data on advanced primary-care management programmes (2025).

Key Takeaways

• RPM lets clinicians monitor chronic patients from home.
• Medicare reimburses specific CPT codes for RPM.
• Many practices miss out on $647k annually in revenue.
• UnitedHealthcare is pulling back on RPM coverage.
• Understanding billing is crucial for sustainable RPM.

How Medicare Covers RPM - The Basics

When I sit down with a practice manager in Melbourne, the first question is always: “Will Medicare actually pay for this?” The short answer is yes, but only if you tick a handful of boxes.

1. Eligibility: The patient must have a chronic condition that requires ongoing monitoring, and they need to consent to the service.
2. Device qualification: The equipment must be FDA-cleared (or TGA-approved in Australia) and capable of transmitting data electronically.
3. Time threshold: Medicare only pays for at least 20 minutes of cumulative monitoring per month - that’s the “minimum clinical staff time” rule.
4. Documentation: You must log the set-up (code 99453), the device supply (code 99454), and each 20-minute monitoring session (code 99457). An add-on code 99458 is available for each additional 20-minute increment.
5. Billing frequency: RPM services are billed monthly, not per encounter, so the practice needs a reliable billing cycle.

Look, here’s the thing: the Medicare rebate for RPM is modest - around $42 for the set-up, $31 for device supply and $55 per 20-minute monitoring session (2025 rates). It doesn’t sound like much, but stack it across dozens of patients and it quickly adds up to a sustainable revenue stream.

In my experience, the biggest barrier isn’t the amount of money but the administrative overhead. Many GPs still use paper charts, and pulling a monthly report from a device platform can feel like hacking a server. That’s why a few forward-thinking clinics have hired a dedicated “RPM coordinator” to manage onboarding, data alerts, and billing submissions.

Why Private Insurers Are Pulling Back - UnitedHealthcare Case Study

On Dec 18 2025, STAT reported that UnitedHealthcare will hold off on its RPM coverage policy change. The insurer, which covers a sizable chunk of Medicare Advantage members, announced a delay to its rollout of broader remote-monitoring benefits, citing “regulatory uncertainty” and “inconsistent clinical outcomes” (STAT). A separate Fierce Healthcare story notes that UnitedHealthcare is also limiting coverage for most chronic conditions, effectively rolling back what it had promised in early-2024 (Fierce Healthcare).

What does that mean for Australian patients? Not a lot of us have UnitedHealthcare, but the move is a cautionary tale. Private health funds often mirror US insurers in their approach to emerging tech - they’ll fund what they see as proven, cost-effective care, and retreat when the evidence base is still thin.

Key takeaways from the UnitedHealthcare pull-back:

• Policy lag: Coverage decisions can shift quickly, leaving providers scrambling.
• Evidence demand: Insurers want robust data linking RPM to reduced hospitalisations.
• Condition scope: UnitedHealthcare now limits RPM to diabetes and hypertension, dropping heart failure and COPD.
• Prior authorisation: Even approved services now need a case-by-case approval, adding paperwork.

In my experience, the same pattern is emerging in Australia. Several health funds have introduced “RPM pilots” but are hesitant to commit to long-term contracts until they see clear cost-savings.

Practical Steps to Set Up a Sustainable RPM Service

Whether you’re a solo GP or a multi-site practice, the following checklist will help you avoid the pitfalls that have left many clinics under-billing.

1. Assess patient suitability: Use your EMR to flag chronic-disease patients with high readmission rates.
2. Choose the right tech stack: Look for platforms that integrate with Cerner or Medtech’s MyHealth Record, and have a clear audit trail.
3. Train staff: Run a half-day workshop on device set-up, data privacy, and billing codes.
4. Develop consent forms: Include clear language on data sharing, duration of monitoring, and patient responsibilities.
5. Set clinical thresholds: Work with specialists to define alert limits (e.g., SpO₂ < 92%).
6. Automate reporting: Use the platform’s monthly export function to generate billing spreadsheets.
7. Submit claims on time: Medicare accepts RPM claims within 12 months of service; private insurers may have tighter windows.
8. Track outcomes: Record hospital readmission rates, medication changes, and patient satisfaction scores.
9. Iterate the model: After six months, review which devices and conditions are most cost-effective.
10. Engage the payer: Share outcome data with health funds to lobby for continued coverage.

When I covered a pilot in regional WA, the practice that followed this checklist saw a 15% drop in heart-failure readmissions within the first year - enough to convince the local health fund to extend the pilot.

Comparison: Medicare vs. Private Insurer RPM Reimbursement (2025)

Notice the stark difference: Medicare offers a clean, standard set of codes, while private insurers sprinkle in caps, prior authorisations and selective condition coverage. If you’re thinking about offering RPM, the safest bet is to start with Medicare-only patients and use the data you collect to make a business case to private funds.

Common Pitfalls and How to Avoid Them

Here are the mistakes I see time and again, paired with quick fixes:

• Skipping consent: Leads to audit failures - always use a signed form.
• Using non-approved devices: May void Medicare claims - stick to TGA-listed equipment.
• Under-documenting staff time: The 20-minute rule is an audit trigger - keep precise logs.
• Neglecting alerts: If you ignore an out-of-range reading, you risk patient safety and legal exposure.
• Assuming private coverage: Verify each health fund’s policy before enrolling a patient.

One practice in Adelaide tried to bill RPM under a “general telehealth” code and got a denial. After they switched to the correct CPT codes and added a simple Excel tracker, the denial rate fell to zero.

Future Outlook: RPM in 2026 and Beyond

Good news and bad news for RPM in 2026 - a Healthcare IT News piece notes that while technology adoption is accelerating, insurer hesitancy remains (Healthcare IT News). The Australian government is funding a $30 million “Digital Chronic Care” trial that will test RPM in heart failure and diabetes across five states (Stat News). If the trial shows a ≥10% reduction in hospitalisations, we could see permanent Medicare expansions.

Meanwhile, AI-driven analytics are being baked into RPM platforms, promising predictive alerts that could pre-empt crises. However, as UnitedHealthcare’s pause demonstrates, without solid evidence of cost-saving, insurers will pull back.

So, what should you do right now?

1. Start small: Pick one chronic condition and a reliable device.
2. Focus on data quality: Clean, auditable data wins insurer confidence.
3. Collect outcomes: Track readmission rates, medication changes, and patient-reported outcomes.
4. Share success stories: Use case studies to lobby private funds for broader coverage.
5. Stay updated: Watch for Medicare policy tweaks each July budget cycle.

In my experience, the clinics that thrive are the ones that treat RPM as a clinical service first and a revenue stream second. The money follows when the data shows better health outcomes.

Frequently Asked Questions

Q: What exactly qualifies as RPM under Medicare?

A: Medicare covers RPM when a clinician monitors physiologic data (e.g., blood pressure, glucose) from a patient-owned device for at least 20 minutes per month, using approved CPT codes 99453-99457. The patient must have a chronic condition and give written consent.

Q: Can private health funds reimburse RPM?