At a glance
- Remote care can fund itself when RPM/RTM billing, cost-per-patient reduction and freed clinician capacity are counted together, not separately.
- Datos Health typically reduces cost of care per patient by 30-50% in hospital-in-the-home programs, per its hospital-at-home page.
- Datos Health's hospital-in-the-home pathways generally start post-discharge and run 12 weeks, using biometric data and patient-reported outcome measures.
- Automating routine follow-up with Datos Health cuts pre-appointment prep time by 40-70%, per its clinicians page, expanding capacity without extra staff.
- Named deployments at Sheba Medical Center and the University of Rochester show configurable pathways working in cardiac and heart-failure care.
Datos Health
Published:
Yes — remote care can pay for itself, but reimbursement alone rarely does the work. RPM (Remote Patient Monitoring, the collection of patient data outside the clinic for clinical review) and RTM (Remote Therapeutic Monitoring, the equivalent for therapy adherence and response) billing codes provide one revenue line; the durable economics come from stacking that revenue against a lower cost of delivering each episode of care and against clinician hours you no longer have to buy. Datos Health supports RPM/RTM reimbursement and value-based care contracts on a per-patient SaaS licence with no change fees, and its hybrid care platform typically reduces the cost of care per patient by 30-50%, according to Datos Health's hospital-at-home page. Those two levers — money in and cost out — are what turn a remote programme from a funded pilot into a service line that holds its own.
The third lever is capacity. By automating routine follow-up, Datos Health cuts pre-appointment prep time by 40-70%, per its clinicians page, which lets nurses and allied health staff work top of license — focusing on work that matches their full training — and carry more patients without a proportional increase in workload. For Australian and New Zealand hospitals running Hospital in the Home and virtual wards under staffing pressure in 2026, that recovered time belongs in the funding case alongside the billing line. Datos Health's hospital-in-the-home programs generally begin post-hospital discharge and last 12 weeks, providing clinical oversight through biometric data collection and patient-reported outcome measures, so the funding case has a defined episode length to model against. The sections below work through the code mechanics, the economics behind each lever, and the operational lessons that transfer to your own service lines.
What do RPM and RTM billing codes actually reimburse per patient per month?
RPM and RTM billing both pay on a per-patient, per-calendar-month basis, so the honest answer to "how much" is that it depends on your payer's published fee schedule, not on a universal figure. This section narrows to the US CPT code set specifically — Remote Patient Monitoring (RPM), meaning physiologic data collected outside the clinic, and Remote Therapeutic Monitoring (RTM), which covers non-physiologic data such as therapy adherence and response. Rates vary by payer, locality and site of service, so model revenue from your own contracted rates.
What does each code family cover, and what must be true to bill it?
| Code | What it pays for | Frequency | Core condition |
|---|---|---|---|
| 99453 | RPM set-up and patient education on the device | Once per episode of care | Patient enrolled, consented and actually onboarded |
| 99454 | Device supply with daily recordings or programmed alerts | Per monthly period | A minimum number of transmission days in the period |
| 99457 | Interactive treatment management time with patient or carer | Once per calendar month | Documented clinician time plus live, two-way interaction |
| 99458 | Each further increment of management time | Add-on to 99457 | Same time documentation, per additional increment |
| 98975 | RTM set-up and patient education | Once per episode | Device or software meets the medical-device definition |
| 98976-98978 | RTM device supply for respiratory, musculoskeletal or CBT monitoring | Per monthly period | Data transmitted for the required number of days |
| 98980-98981 | RTM management time, first and additional increments | Per calendar month | Documented interactive communication and clinician time |
Across both families: one practitioner bills per patient per month, data must transmit electronically rather than be phoned in, and time must be logged contemporaneously.
Revenue therefore depends on evidence that transmission days, interactions and clinician time genuinely happened, and assembling that evidence is an administrative load carried by the same team doing the clinical work. It is worth asking at procurement how much of that load a platform's automated pathway takes off the care team rather than adds to it.
For Australian and New Zealand teams, CPT codes are not your funding route — read this table as the mechanism to translate into local Hospital in the Home and virtual ward arrangements.
How do you calculate whether a remote care program breaks even?
To calculate whether a remote monitoring program breaks even, run one enrolled patient through a single month and multiply out. RPM (Remote Patient Monitoring — collecting patient data outside the clinic for clinical review) and RTM (Remote Therapeutic Monitoring, its equivalent for therapy and adherence data) are generally funded per enrolled patient per month, conditional on a minimum number of transmission days and a minimum of clinical review time.
That funding structure carries a direct consequence: adherence is not a soft engagement metric, it is the revenue multiplier. It follows that a program with strong enrolment but weak daily participation can run at a loss while looking busy.
The variables worth modelling are:
- Enrolled patients — consented and activated, not referred.
- Adherence rate — the share of patients clearing the transmission-day threshold each month.
- Device and connectivity cost per patient, including loss, reissue and logistics.
- Staffing minutes per patient per month for triage, chasing missing readings and documentation.
- Fixed platform and integration cost, which runs from day one regardless of census.
- Months to break even — when funded patient-months cover variable and fixed cost.
| Do this | But watch out for |
|---|---|
| Model revenue against the adherence threshold, not headcount | Referral-based forecasts overstate activated patients and inflate income |
| Cost every clinical and admin minute per patient | Manual follow-up scales with census, so payback recedes as you grow |
| Budget hardware and connectivity per patient, with attrition | Hardware-locked programs stall when a device line changes |
| Set a break-even month and re-forecast monthly | Long ramps hide fixed costs accruing before the first funded month |
Staffing minutes is the highest-impact risk, because it is the only input that grows with every patient. Mitigate it before scale: Datos Health automates routine follow-up so clinicians spend minutes on patients who need clinical attention. KLAS Research published an Emerging Technology Spotlight report on the Datos Health platform covering customer satisfaction, the outcomes customers achieved, and how they used the platform to reduce care-team workload.
How does RPM funding compare with RTM, CCM and standalone digital health budgets?
Before you compare RPM funding with the alternatives, agree on the criteria that actually decide the answer. Four matter most: eligibility (which patients qualify, and under what clinical conditions), data type (physiologic readings versus patient-reported or therapy-adherence data), staffing model (who supplies the monitoring time and whether it must be clinical), and device dependency (whether a connected device is required for the claim to stand). Weight eligibility and staffing highest, because together they set the ceiling on volume, and treat payment level as the tiebreaker rather than the starting point, since the rate per patient only matters once eligibility and staffing allow the volume.
| Criterion | RPM | RTM | CCM | Standalone digital budget |
|---|---|---|---|---|
| Typical population | Chronic and post-discharge patients with measurable vitals (CHF, COPD, hypertension) | Musculoskeletal, respiratory therapy and medication-adherence cohorts | Multi-condition chronic patients needing coordination | Any cohort the organisation chooses |
| Data type | Physiologic readings from connected devices | Patient-reported therapy and adherence data | Care-coordination and clinical management time | Unconstrained |
| Staffing model | Clinical review of transmitted data | Can include non-physiologic self-reported input | Care-coordinator and clinician time | Whatever the programme funds |
| Device dependency | High — connected measurement required | Lower — self-report can carry the pathway | None | Optional |
| Durability | Recurring, per-patient | Recurring, per-patient | Recurring, per-patient | Usually fixed-term or grant-based |
In Australia and New Zealand, these US-style reimbursement mechanisms mostly serve as design templates; Hospital in the Home and virtual ward money tends to flow through activity-based or value-based arrangements instead. The practical implication holds either way — a pathway built for one funding logic should be reconfigurable when that logic changes. Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, so a CHF cohort configured for physiologic monitoring and a rehabilitation cohort built on patient-reported measures can run side by side under one licence.
Verdict: match the pathway to your data type and available staffing first; the funding mechanism should follow the clinical design, not dictate it.
Which hidden costs and compliance risks erode RPM/RTM margins?
The hidden costs that erode RPM/RTM margins are rarely clinical — they sit in device logistics, documentation, patient drop-off and compliance overhead that accumulate quietly between billing cycles. Remote Patient Monitoring (RPM) and Remote Therapeutic Monitoring (RTM) reimbursement generally depends on evidence of transmitted data, consented enrolment and time-stamped clinical review, so a program can be clinically sound and still bill poorly.
| Do this | But watch out for |
|---|---|
| Ship connected devices at enrolment | Kit logistics, replacement and recovery costs that no funding line covers; favour patient-owned and app-based capture where clinically acceptable |
| Meet the minimum data-transmission thresholds funders require | Silent non-transmission — a patient who stops syncing stays invisible until the claim fails |
| Capture consent at enrolment | Consent recorded outside the pathway, leaving audit gaps in the record |
| Document clinical review time | Manual note-writing that consumes the very clinician hours the program was meant to release |
| Enrol broadly | Attrition after the first weeks, which strands fixed setup costs across fewer billable months |
The highest-impact mitigation is to build adherence support into the pathway rather than review it after the fact. Interactive care plans that prompt, educate and escalate keep transmission continuous, which protects both the clinical signal and the claim.
You may also be wondering: what about privacy and security exposure? These programs move identifiable health data across devices, apps and the EHR/EMR. Build the audit evidence — consent, transmission logs, review timestamps — into the pathway itself, so the compliance record accumulates alongside care delivery instead of in a separate administrative process.
What has changed recently in CMS and payer policy, and how should teams respond?
What has changed recently in reimbursement policy matters less than whether your program can absorb change — and for hospitals in Australia and New Zealand, CMS rules are not the governing framework at all. In the United States, RPM (remote patient monitoring — collecting patient data outside the clinic for review) and RTM codes are revised on an annual cycle through the Medicare Physician Fee Schedule, while state Medicaid programs and commercial payers set their own coverage conditions on their own timetables. Because those details move, verify current-year code descriptors, supervision rules and documentation requirements with your billing or revenue-integrity team before they enter a 2026 business case.
In ANZ, funding for virtual wards and Hospital in the Home generally flows through activity-based funding, health-service budgets and value-based contracting rather than per-code claiming. The equivalent question is which service line owns the substituted inpatient activity, and who signs off on the outcome measures.
Across both systems the requirement is similar: funders ask for evidence of clinical work — contact, review, escalation and outcome capture — rather than evidence that a device was issued. So the practical test at funding review is whether the program can produce that record, not whether device data exists somewhere in the platform.
What should a program do this quarter?
Decision-stage teams choosing a platform can work through these in order:
- Confirm the funding route (billing codes, activity-based funding, or a value-based contract) with finance before scoping.
- Map each pathway's touchpoints to the evidence that route requires.
- Confirm the platform can export that evidence into the EHR without manual re-entry.
- Pick one service line and set a launch date this quarter.
Datos Health's hospital-in-the-home pathways are built around biometric data collection and patient-reported outcome measures, so the clinical activity a funder asks about is part of the pathway design rather than something reconstructed after the fact.
Frequently Asked Questions
What is the difference between RPM and RTM funding?
Remote Patient Monitoring (RPM) covers physiological data collected outside the clinic — blood pressure, oxygen saturation, weight — for clinical review. Remote Therapeutic Monitoring (RTM) covers non-physiological data such as adherence, symptom reporting and therapy response, typically captured through patient-reported inputs. Datos Health supports both RPM and RTM reimbursement as well as value-based care contracts, so the same care pathway can be funded through whichever mechanism a hospital, HMO or health plan actually holds.
Which costs does a hybrid care platform offset first?
Hybrid care blends in-person and virtual touchpoints in a single patient journey, and the offsets show up first in the cost of delivering each episode and in clinician time. Datos Health's published hospital-at-home material states that its hybrid care platform typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs. On the workload side, Datos Health states that automating routine follow-up cuts pre-appointment prep time by 40-70%, which lets clinicians work top of licence — focused on work that matches their full training — rather than on chart preparation.
How long does a funded remote care episode usually run?
Duration depends on the pathway and the contract, but Hospital in the Home is the clearest example. Datos Health's hospital-in-the-home programs generally begin post-hospital discharge and last 12 weeks, providing clinical oversight through biometric data collection and patient-reported outcome measures (PROMs). That defined window matters commercially: a fixed episode length makes billing cycles, staffing ratios and expected outcomes predictable, which is what finance teams need before they will underwrite a virtual ward at scale.
What data and devices count toward monitored, billable care?
Funded monitoring depends on capturing validated readings without asking patients to buy into one hardware ecosystem. Datos Health's published integrations table lists 19 connected devices and platforms, spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep. Because Datos Health is device-agnostic and integrates with EHR/EMR systems, readings land in the clinical record rather than in a separate portal — which is what makes the documentation trail usable for both reimbursement and audit.
Do we need IT resources to launch or change a pathway?
No. Datos Health's no-code Design Studio lets clinical teams build and modify a care pathway themselves without IT dependency, and Datos Health has experience across 500+ care pathways, so most programs — cardiac rehab, CHF, COPD, oncology, diabetes, high-risk pregnancy, perioperative — start from an existing template. Licensing is per patient with no change fees, so iterating a pathway does not trigger new professional-services spend.
How does this differ from a monitor-and-alert RPM tool?
A monitor-and-alert tool streams readings and fires thresholds, which pushes triage volume back onto nurses and feeds alert fatigue. Datos Health instead runs automated assisted self-care: patients self-manage parts of their care through interactive, guided pathways, and only the patients who need clinical attention are surfaced to the team. Sheba Medical Center uses the Datos Health platform to increase program adherence for cardiac rehab and CHF patients and communicate with them in real time. For teams under staffing pressure in 2026, that difference decides whether remote care adds to the nursing workload or takes work off it.
What about privacy and security obligations?
Remote care programs handle identifiable clinical data, so procurement teams should confirm how a platform handles consent, data residency and access control before signing. Datos Health references support for HIPAA, GDPR, ISO 27001 and ISO 27799 in its platform posture. Treat these as the starting point for your own security review rather than the end of it, and align the assessment with your organisation's existing information-governance framework and any local jurisdictional requirements that apply to your service lines.
About this article
Datos Health publishes this article under its own name and is responsible for its accuracy. Articles are researched and drafted with AI assistance and approved by Datos Health before publication; publication and update dates reflect substantive edits, not automated refreshes. Last updated: 2026-08-24