At a glance
- Remote care pays through two channels: activity-based RPM/RTM billing codes and value-based contracts rewarding avoided admissions, adherence and patient-reported outcomes.
- Reimbursement follows documented enrolment, device-sourced readings, review time and structured outcome data — not clinical intent alone.
- Datos Health supports RPM/RTM reimbursement and value-based contracts on a per-patient SaaS licence with no change fees.
- Datos Health's published integrations table lists 19 connected devices and platforms, spanning glucose, blood pressure, oxygen saturation and more.
- Hospital in the Home carries the strongest economics: Datos Health's hybrid platform typically reduces cost of care per patient by 30-50%.
Datos Health
Published:
Remote care becomes financially sustainable through two distinct funding channels, and most programs need both. The first is activity-based reimbursement — Remote Patient Monitoring (RPM, the collection of patient data outside the clinic for clinical review) and Remote Therapeutic Monitoring (RTM, the equivalent for therapy adherence and musculoskeletal or respiratory data), billed against documented enrolment, device-sourced readings, and clinician review time. The second is value-based contracting, where a hospital, health plan or health service is paid for outcomes and risk transfer — avoided admissions, shortened bed-days, adherence, and patient-reported outcome measures (PROMs) — rather than for each recorded interaction. A program that only bills codes stays small and margin-thin; a program that only chases outcomes without billing infrastructure funds itself out of operating budget. In practice both channels are served by the same pathway, which produces the billing artefacts and the outcome evidence as part of ordinary clinical work.
That dual-channel logic is why the design of the pathway matters more than the choice of device. Billing rules reward documented, time-stamped data capture; at-risk contracts reward the sustained patient adherence that actually prevents readmission. The programs that clear both bars share the same characteristics — automated enrolment, structured data flowing into the EHR, patient-reported measures collected on a schedule, and exception-based escalation so clinicians spend their time on the patients who need it. This guide sets out what each funding model actually requires, where the two overlap, how the mechanism works end to end, and what Australian and New Zealand health services running Hospital in the Home and virtual wards should build first in 2026.
Which reimbursement pathways actually pay for remote care today?
Reimbursement pathways that actually pay for care delivered outside the clinic cluster into a handful of recognisable families, and each one has its own attributes — what it covers, what evidence it demands, and how it is claimed. Knowing those attributes before you design a pathway is what separates a funded programme from an unfunded pilot.
| Pathway | What it pays for | Core requirements | Why it matters |
|---|---|---|---|
| Remote Patient Monitoring (RPM) — collecting physiological data outside the clinic for clinician review | Device supply, data transmission, and clinician time spent reviewing readings | A connected device, a minimum volume of transmitted days, documented clinical review and patient consent | The most established billing family for physiological data; underpins CHF, COPD and hypertension programmes |
| Remote Therapeutic Monitoring (RTM) — monitoring non-physiological data such as adherence, pain or function | Therapy adherence and patient-reported data, plus management time | Patient-reported inputs, documented treatment management, allied-health eligibility in some schemes | Extends funding to rehab, musculoskeletal and oncology supportive care where vitals alone do not tell the story |
| Care-coordination and chronic care management items | Non-face-to-face care planning, coordination and review between visits | A documented care plan, defined review intervals, consent to enrol | Funds the follow-up labour that otherwise sits unbilled on nursing rosters |
| Telehealth and virtual visit items | Scheduled video or phone consultations | Eligible provider, modality and patient-relationship rules | The simplest to claim, but only covers the consultation — not the work between consultations |
| Hospital in the Home / virtual ward funding | Bed-substitutive acute care delivered at home, usually bundled or activity-based | Admission criteria, clinical governance, documented escalation | Pays at hospital rates, so it carries the strongest business case in Australia and New Zealand |
Most organisations end up combining several of these across service lines, which is why platform configurability matters. Datos Health's no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, so each service line can run the pathway it needs rather than waiting on an IT release cycle.
What is a value-based contract for remote care, and how does it differ from fee-for-service billing?
A value-based contract for remote care ties payment to measured outcomes and total cost of care, while fee-for-service reimbursement pays a fixed amount per billed code, encounter or monitoring period. The four terms that matter most are: shared savings (the provider keeps an agreed share of spend that comes in under a benchmark), capitation (a fixed per-member-per-month payment covering defined services), bundled payments (a single price for an episode, such as a joint replacement and its recovery window), and upside versus downside risk (whether you only share in savings, or also repay losses when spend exceeds the benchmark).
Which criteria should you weigh before comparing models?
- Revenue trigger — is income earned per activity or per outcome? This decides whether adding patients adds revenue or adds exposure.
- Risk exposure — upside-only arrangements protect the balance sheet; downside risk demands confidence in your clinical pathways before signing.
- Data and reporting burden — every model needs evidence, but at-risk contracts require outcome measures such as PROMs (patient-reported outcome measures), not just time logs.
- Scalability — per-code billing rewards volume of touchpoints; at-risk models reward automation that keeps well patients out of the queue.
| Model | How revenue is earned | Risk carried | Evidence required | Fit for virtual programs |
|---|---|---|---|---|
| Fee-for-service (RPM/RTM codes) | Per code, per patient, per period | None beyond unbilled time | Device days, clinician minutes | Predictable, but capped by staff hours |
| Shared savings | Share of spend below benchmark | Upside only | Utilisation, readmissions | Good entry point for virtual wards |
| Bundled payment | Fixed price per episode | Cost overruns within the episode | Episode outcomes, complications | Strong fit for perioperative and rehab |
| Capitation | Fixed per-member-per-month | Full upside and downside | Population outcomes, engagement | Highest reward where automation is mature |
Read across the table, fee-for-service revenue is what typically sustains a pilot, while at-risk contracts are what sustain a scaled service. Whether an at-risk arrangement is affordable comes down to how much clinician time each enrolled patient consumes — which is why Datos Health replaces reactive monitor-and-alert working with automated assisted self-care, surfacing only the patients who genuinely need clinical attention.
How do you build a unit economics model that proves a remote care program pays?
To build a unit economics model that stands up to finance review, start with the smallest repeatable object in the program: one enrolled patient, one month. If the program is to pay for itself, it follows that per-patient monthly contribution — billable or contracted revenue minus the clinical and platform cost of serving that patient — must be positive at a realistic census, not at a best-case one. Model the inputs individually before you model the total.
The variables worth defining explicitly
- Per-patient-per-month (PPPM) revenue — the reimbursement or contracted amount attached to one enrolled patient in one month, whether from a monitoring billing code, a bundled episode, or a capitated arrangement. It sets the ceiling on everything else.
- Enrolment rate — the share of eligible patients who actually activate, expressed as a percentage of the referred cohort. Low activation is the most common reason a sound business case underperforms, because fixed platform and setup costs spread across fewer patients.
- Adherence threshold — the minimum days of data or completed tasks required for a patient-month to count as billable or clinically useful. Define it per pathway; a cardiac rehab cohort and a COPD cohort will not behave alike.
- Staffing cost per patient-month — nurse and allied-health minutes consumed per patient, costed at loaded salary. This is the variable that scales, so it decides whether growth improves or erodes margin.
- Breakeven census — the enrolled-patient count at which contribution covers fixed platform, integration and programme-management cost.
Build these assumptions per pathway rather than per programme, because a cardiac cohort and a perioperative cohort behave differently on almost every line. Datos Health offers 300+ pre-built care programs, so a new service line can start from an existing pathway instead of a blank sheet, and the finance work narrows to the assumptions that genuinely differ.
Which documentation, consent, and compliance requirements determine whether a claim gets paid?
Whether a claim gets paid usually turns on three things: documentation that matches the service billed, consent captured before monitoring begins, and compliance evidence you can still produce a year later. This depends on what you mean by compliance, though — the word covers three separate regimes that fail in different ways.
- Billing compliance: payer rules for RPM (remote patient monitoring — collecting patient data outside the clinic for review) and RTM (remote therapeutic monitoring) generally require a minimum number of transmitted device-data days per billing period, logged clinical review time, an identified supervising clinician, and documented patient consent.
- Privacy and security compliance: how identifiable data is stored, transmitted and accessed, and which recognised privacy and information-security obligations the deployment must satisfy in its own jurisdiction.
- Clinical governance: scope of practice, escalation rules, and who is accountable when a reading breaches an Early Warning Score threshold.
| Do this | But watch out for |
|---|---|
| Record consent at enrolment, with date, scope and the right to withdraw | Verbal consent noted only in a nursing entry is hard to retrieve at audit |
| Log device-derived data days automatically from connected devices | Manually keyed vitals may not count as device-transmitted data |
| Timestamp clinical review and interactive communication | Retrospective time entry is the most common clawback trigger |
| Name the billing and supervising clinician on the pathway | Supervision rules differ by contract and by jurisdiction |
| Keep an immutable audit trail per patient episode | Data spread across point solutions cannot be reconstructed later |
Each of these requirements is easier to meet when the record is generated inside the clinical workflow rather than assembled afterwards as a separate administrative task. That is also where the economics land — Datos Health reports that its hybrid care platform typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs, because the same automated pathway that guides the patient produces the record that supports the claim.
How should an organization move from fee-for-service billing to at-risk remote care contracts?
An organization that wants to move beyond fee-for-service billing rarely does it in one jump — the practical route is a staged sequence where code-based revenue funds the evidence you will later need at the negotiating table. This is decision-stage work: you already accept that virtual programs belong in your service mix, and the question is contracting mechanics.
- Bill the codes you already qualify for. Stand up RPM (remote patient monitoring — collecting patient data outside the clinic for review) and RTM claims on one or two pathways so the program is cash-positive before any risk is taken on.
- Instrument outcomes from day one. Capture PROMs and PREMs — patient-reported outcome and experience measures — alongside biometric readings, because a shared-savings conversation is won or lost on baseline data quality.
- Pick one condition-defined cohort to put at risk. Post-discharge cohorts suit this best: Datos Health states that its Hospital in the Home programs generally begin post-hospital discharge and last 12 weeks, giving clinical oversight through biometric data collection and patient-reported outcome measures — a bounded window with a measurable endpoint.
- Model the counterfactual. Compare bed days, escalations and unplanned presentations against a matched historical period before proposing a savings split.
- Negotiate a shared-savings corridor, then step into capitation. Cap downside exposure in year one; widen it only when the cohort's variance is understood.
- Standardise the pathway, then replicate. Reuse the configuration for the next service line so contracting effort compounds instead of restarting.
The pattern worth noticing is that fee-for-service and at-risk models are not really rivals during transition. Code-based billing acts as the measurement scaffold: the documentation discipline it forces is precisely the dataset a payer will demand before signing capitation. Organizations that treat step one as disposable usually arrive at step five with no defensible baseline.
Frequently Asked Questions
What is the difference between RPM and RTM reimbursement?
Remote Patient Monitoring (RPM) — collecting physiological data such as blood pressure, weight or oxygen saturation outside the clinic for clinical review — is billed on device-derived readings and clinician review time. Remote Therapeutic Monitoring (RTM) covers non-physiological data: medication adherence, symptom scores, respiratory or musculoskeletal therapy response. The practical difference is the evidence trail each requires. Datos Health supports both RPM and RTM reimbursement, capturing device readings and patient-reported responses in the same care plan so the billing record is a by-product of the clinical workflow rather than a separate admin task.
Which measures matter most under value-based contracts?
Outcome and experience measures, not activity counts. Value-based agreements pay against results, so PROMs (patient-reported outcome measures) and PREMs (patient-reported experience measures) become contractual instruments rather than research artefacts. For health plans, including Medicare Advantage, Star Ratings and CAHPS performance sit on the same data foundation. Datos Health collects biometric readings and patient-reported outcome measures inside its interactive care plans, which is how the same pathway serves clinical oversight and contract reporting at once.
How long does a hospital-in-the-home episode usually run?
Datos Health states that its 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. That episode length matters commercially: it defines the billing window for virtual ward activity and the observation period a value-based contract will judge you on.
Why does consolidating point solutions protect the margin?
Every separate monitoring tool adds a licence, an integration, a training burden and a reconciliation step before anything can be billed. One Datos Health platform replaces multiple point solutions — device-agnostic across 8+ vital-sign types with EHR/EMR integration — and the company prices it as a per-patient SaaS licence with no change fees, so redesigning a pathway does not trigger a new invoice.
How fast can a new billable pathway go live?
Days, not quarters. Datos Health's no-code Design Studio lets clinical teams build or modify a pathway themselves without IT dependency, starting from 300+ pre-built care programs, so a new billable configuration does not wait on an IT release cycle.
What compliance considerations apply to these programs?
Remote care programs stand or fall on defensible, auditable data handling: identifiable data must be stored, transmitted and accessed under controls your governance team can evidence at audit. Procurement teams should confirm local data-residency and privacy obligations for Australian and New Zealand deployments, since contract reporting and claim integrity both depend on that foundation.
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