At a glance
- Virtual wards are funded by combining RPM/RTM reimbursement, value-based care contracts, and avoided bed-day costs into one defensible business case.
- Datos Health supports RPM/RTM reimbursement and value-based contracts on a per-patient SaaS licence with no change fees.
- Per Datos Health's hospital-at-home page, its hybrid care platform typically reduces cost of care per patient by 30-50%.
- Incumbent EMR-anchored suites like Telstra Health are bought for integration depth, not for standing up fundable pathways quickly.
- Funding follows evidence: capture biometrics and PROMs in the pathway, or the reimbursement case stays unproven.
Datos Health
Published:
Funding virtual wards in 2026 comes down to three revenue mechanics working together: RPM/RTM reimbursement (payment for remote patient monitoring and remote therapeutic monitoring, where the data is collected outside the clinic and reviewed by a care team), value-based care contracts that pay for outcomes rather than episodes, and the avoided cost of the hospital bed the patient is no longer occupying. Where a health service already runs parts of this on an incumbent enterprise suite, that incumbent has real strengths: Telstra Health, for example, wins on scale, an owned EMR/PAS and integration depth. Datos Health's edge against that kind of estate is speed to deploy — days rather than months — with RPM and Hospital in the Home as its core product rather than one feature of an EMR/PAS estate.
On the commercial side, Datos Health supports RPM/RTM reimbursement and value-based care contracts on a per-patient SaaS licence with no change fees, so the model scales with enrolled patients rather than with project variations. According to Datos Health's hospital-at-home page, its hybrid care platform typically reduces the cost of care per patient by 30-50%. This article walks through how each funding stream works, where the evidence for it is generated, how the main ANZ alternatives compare, and when staying put is the right call.
What exactly is a virtual ward, and which funding mechanisms apply to it?
Exactly what counts as a virtual ward depends on which of two models you mean, because the term carries a specific clinical definition and a looser marketing one. In Australia and New Zealand, the canonical form is Hospital in the Home (HITH) — hospital-level, substitutive acute care delivered in a patient's residence, where the person is formally admitted, occupies a virtual bed, and is discharged like any inpatient. That is the definition state health departments and hospital funding models work from, and it is the phrasing to use in a business case.
The second reading is broader: any remote patient monitoring (RPM) program — collecting vital signs and symptoms outside the clinic for clinician review — described loosely as a "virtual ward". Longitudinal management of CHF, COPD or diabetes usually sits here. Both are legitimate, but they are funded differently, so conflating them is where business cases fall apart.
The funding mechanisms that realistically apply:
| Mechanism | What it pays for | Typical fit |
|---|---|---|
| Activity-based / admitted funding | Substitutive acute care at home, counted as an admitted episode | HITH, virtual wards |
| RPM and RTM reimbursement | Device-collected physiological data (RPM) and patient-reported therapeutic data (RTM) | Post-acute and long-term condition programs |
| Value-based and outcomes contracts | Avoided readmissions, PROMs/PREMs performance, shared savings | Health plans, population health |
| Bundled or episode payments | A defined care episode across settings | Perioperative, cardiac rehab |
Datos Health is built to run acute-substitutive and longer-term pathways on one platform, so the funding model, not the tooling, decides how a program is designed.
How do RPM and RTM funding streams differ for an ANZ virtual ward?
RPM and RTM differ by the evidence of care they pay for, and in Australia and New Zealand that distinction matters more than any code list. Remote Patient Monitoring (RPM) — collecting patient data outside the clinic for review — is built around physiologic readings captured automatically by a connected device. Remote Therapeutic Monitoring (RTM) covers non-physiologic therapeutic data, such as medication adherence, therapy response, and patient-reported symptoms, which the patient may self-report.
ANZ funding rarely arrives as a single dedicated remote-monitoring line item. Instead, the same monitored activity is paid for through whichever local arrangement owns the patient, and each one asks for different evidence:
| Local funding route | What it pays for | Evidence the funder expects | Typical virtual ward use |
|---|---|---|---|
| State and territory activity-based funding for admitted HITH | Hospital-level care delivered at home, counted as an admitted episode | Admission and discharge records, observation, escalation and clinical governance logs | Acute substitutive virtual wards |
| Medicare-funded chronic condition management and telehealth services | Clinician planning, review and remote consultation time for eligible patients | Care plan documentation, review intervals, recorded consultations | CHF, COPD and diabetes cohorts followed longitudinally |
| Private health insurer hospital-substitute programs | Insurer-funded care at home in place of an admission | Insurer eligibility criteria, episode reporting, discharge outcomes | Post-acute, rehabilitation and perioperative pathways |
| Health New Zealand and district commissioning of virtual care | Contracted service volumes under a commissioning agreement | Activity reporting, quality and outcome measures against the contract | Regional virtual wards and long-term condition programs |
Which criteria decide where a pathway gets funded from?
Set the evaluation criteria before you map any pathway to a funding route:
- Care type — substitutive acute care that replaces a bed, versus longitudinal management of a long-term condition. This is the single decisive test.
- Data type — physiologic measurements versus therapy-response and adherence data. It determines whether a connected device is mandatory.
- Who holds the money — the health service, the national schedule, a private insurer, or a commissioning agency. Each has its own eligibility gate.
- Evidence retrievability — can enrolment, consent, transmitted readings and clinical review time be exported as one defensible record?
- Pathway fit — weight this highest: a long-term condition cohort funded through the wrong route creates rework at audit.
Every route above asks for the same operational discipline: documented enrolment and consent, a consistent monitoring cadence, and recorded clinical review — all retrievable months later.
Datos Health supports RPM and RTM reimbursement alongside value-based care contracts, so a single pathway can carry the documentation several funding routes need without running two systems in parallel. The RPM and RTM vocabulary itself comes from US reimbursement practice; for ANZ teams it is useful as a documentation model rather than a funding route, and the captured evidence still has to map to local Hospital in the Home and virtual ward arrangements.
Which value-based care contracts can pay for virtual wards beyond fee-for-service?
Beyond fee-for-service, virtual wards can be funded through value-based care contracts — agreements that pay for a population, an episode, or a measured outcome rather than for each billed activity. This section narrows to those risk-bearing vehicles specifically; per-encounter remote monitoring reimbursement is a separate funding track. For a Hospital in the Home or virtual ward business case, the practical question is which contract attributes your program can actually satisfy with evidence.
| Contract vehicle | Payment unit | Evidence the funder expects | Fit for virtual wards |
|---|---|---|---|
| Shared savings (ACO-style) | Retrospective share of spend below a benchmark | Attributed cohort, total cost of care, avoided admissions | Strong where readmission reduction is the savings driver |
| Bundled / episode payments | Fixed price per episode across a defined window | Episode boundaries, complication and readmission rates | Strong for perioperative, cardiac rehab and post-discharge pathways |
| Capitation / per-member-per-month | Prospective fixed sum per enrolled member | Enrolment lists, utilisation, quality and experience measures | Suits health plans managing chronic cohorts at scale |
| Outcomes- or quality-linked payments | Bonus or withhold tied to measured performance | PROMs and PREMs — patient-reported outcome and experience measures — plus adherence data | Suits programs already capturing structured patient-reported data |
| Substitutive admitted-care funding | Activity counted as admitted care delivered at home | Clinical governance records, observation and escalation logs | Applies where a jurisdiction recognises home delivery as admitted activity |
Each vehicle rewards the same underlying capability: consistent pathway execution that produces auditable data. Datos Health supports value-based arrangements by standardising how a cohort is enrolled, monitored and escalated, drawing on 300+ pre-built care programs, so a diabetes cohort under capitation and a surgical cohort under a bundle can run on one configuration layer. Model each contract against the data your program can defend before you commit to downside risk.
RPM/RTM fee-for-service or value-based contracts: which funding model produces more durable virtual ward revenue?
Durability is the real question once both options are on the table: fee-for-service payment for remote patient monitoring and remote therapeutic monitoring, or a value-based contract that pays for outcomes and total cost of care across an attributed population.
Before comparing them, agree on the criteria that actually decide durability:
- Revenue predictability — does income arrive per enrolled patient per month, or as a retrospective settlement?
- Enrolment dependency — how much clinical admin is needed to keep a patient claimable?
- Documentation burden — what evidence must be captured, and can the platform capture it automatically?
- Exposure to cost of care — does lowering utilisation increase or decrease your revenue?
- Scalability across service lines — can one funding model cover Hospital in the Home, cardiac rehab, COPD and perioperative cohorts?
Weight predictability highest in year one, and exposure to cost of care highest from year two onward — that is where the two models diverge.
| Criterion | Fee-for-service RPM/RTM | Value-based contract |
|---|---|---|
| Revenue predictability | Per-patient, per-month; visible early | Retrospective; depends on measured performance |
| Enrolment dependency | High — payment follows active enrolment | Lower — attribution is population-based |
| Documentation burden | Heavy; time and data thresholds must be evidenced | Moderate; outcome and PROMs evidence dominates |
| Exposure to cost of care | Reducing utilisation can reduce claimable volume | Reducing utilisation directly increases margin |
| Scale across service lines | Constrained to eligible cohorts | Applies across the attributed population |
The verdict: fee-for-service reimbursement funds the launch, while value-based contracts fund the decade — so build a virtual ward that can run both from one pathway. Datos Health is designed for exactly that dual mechanic: the same automated follow-up that evidences monitored clinical time also produces the PROMs (patient-reported outcome measures) and adherence data a value-based settlement is judged on, so finance teams are not maintaining two parallel evidence trails for one cohort.
What eligibility, consent, and documentation risks can void virtual ward funding?
Funding for a virtual ward is most often lost on paperwork, not on clinical performance: eligibility that was never evidenced, consent that was taken verbally but never recorded, and documentation that cannot be reconstructed at audit. If a payer or health service is paying for hospital-level care delivered at home under RPM/RTM reimbursement — remote physiologic or therapeutic monitoring funded per patient per period — it follows that every claim must be traceable to a dated record showing who qualified, what they agreed to, and what data actually arrived.
That traceability requirement has practical consequences. Most funding rules attach conditions to the episode: a documented eligible condition, recorded patient consent before enrolment, a minimum number of days on which device or patient-reported data was transmitted within the period, and evidence of clinical review time. Miss any one and the episode is unclaimable — even if the care was excellent.
| Do this | But watch out for |
|---|---|
| Capture consent digitally at enrolment, timestamped in the pathway | Verbal consent noted in free-text nursing notes is hard to retrieve at audit |
| Encode eligibility criteria into the enrolment step so ineligible patients cannot start | Criteria drift as a program expands; unversioned rules break the audit trail |
| Track transmission days and review time automatically per patient | Manual tallies in spreadsheets diverge from the source data |
| Keep enrolment, monitoring and discharge in one record | Point solutions split the episode across systems, so no single export proves it |
Per Datos Health's published hospital-at-home program description, its hospital-in-the-home programs generally begin post-hospital discharge and run 12 weeks, with clinical oversight through biometric data collection and patient-reported outcome measures — a defined episode structure that makes each funding period easier to evidence.
Highest-impact mitigation: version your pathway. If consent wording and eligibility logic are versioned inside the care plan, every claim can be tied back to the exact rules in force that week.
How can a blended funding stack de-risk the virtual ward business case?
A blended funding stack — layering activity-based remote monitoring payments, chronic-condition management funding and value-based or outcome-linked contracts over one virtual ward platform — de-risks the business case because no single revenue line has to carry the whole program. If one stream is delayed, re-priced or capped, the others keep the ward solvent while you prove clinical value.
For teams at the decision stage, a staged rollout keeps the funding model honest:
- Pick one cohort with money already attached — typically a Hospital in the Home or heart failure group where bed-day substitution is already funded.
- Bank the existing line first. Remote patient monitoring (RPM) reimbursement, where data is collected outside the clinic and reviewed by the care team, is usually the fastest line to activate.
- Add remote therapeutic monitoring (RTM) — tracking therapy adherence, symptoms and response rather than vital signs alone — so rehabilitation, respiratory and post-operative pathways carry their own funding.
- Layer the outcome contract only once the pathway is stable, using patient-reported outcome and experience measures (PROMs and PREMs) as the agreed evidence base.
- Re-forecast after each stage before extending to the next service line, so scale decisions rest on observed cost and utilisation, not the pilot narrative.
A reasonable reading of failed virtual ward business cases is that the funding gap is a measurement gap first: contracts are lost at the evidence stage, not the negotiation stage. Breadth of capture matters accordingly — Datos Health is device-agnostic across 8+ vital-sign types, spanning measures such as glucose, blood pressure, oxygen saturation, temperature and weight, which is what lets one pathway substantiate several funding lines at once.
Ask any shortlisted vendor to map each pathway to its funding line before contracting.
Frequently Asked Questions
What funding sources actually pay for a virtual ward?
Virtual ward funding usually draws on three streams: remote monitoring reimbursement (RPM and RTM — Remote Patient Monitoring for physiological data, Remote Therapeutic Monitoring for adherence and therapy response), value-based or bundled contracts that pay for outcomes rather than occasions of service, and internal capacity savings from avoided bed-days. Datos Health supports RPM/RTM reimbursement and value-based care contracts on a per-patient SaaS licence with no change fees, so a Hospital in the Home program can be funded from more than one stream without re-contracting each time a pathway changes.
How does a platform help you evidence a value-based contract?
Outcome-based agreements need defensible data, not anecdotes. Datos Health collects biometric readings alongside PROMs and PREMs — patient-reported outcome and experience measures — and pushes them into the record through EHR/EMR integration, giving finance and clinical governance the same source of truth. Being device-agnostic across 8+ vital-sign types, covering measures such as glucose, blood pressure, oxygen saturation, temperature, heart rate and weight, is what makes device-level evidence capture practical across mixed cohorts.
What cost effect should a business case assume?
Per Datos Health's hospital-at-home materials, its hybrid care platform typically reduces the cost of care per patient by 30-50%, because one platform replaces several point solutions rather than adding another subscription. The mechanism matters as much as the figure: automated assisted self-care — where patients self-manage parts of their plan through guided, interactive pathways — surfaces only the patients who need clinical attention, so staffing does not scale linearly with census.
How long does a hospital-in-the-home episode typically 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 is useful for modelling, since remote monitoring claiming cycles and value-based milestones both need a defined enrolment period, and a 12-week arc gives finance a repeatable unit of funding to forecast against.
How does Datos Health compare with other ANZ platforms on funding flexibility?
Each option fits a different buyer context. CareMonitor is FHIR-native, ISO 27001 certified, and holds strong ANZ channel partnerships. Telstra Health brings scale, an owned EMR/PAS and integration depth. Orion Health sits at the health-information-exchange and interoperability layer. The Clinician leads PROMs/PREMs through ZEDOC. Datos Health differs architecturally: a no-code OpenCare pathway builder with no peer equivalent, so clinical teams reconfigure programs themselves without IT tickets, plus a per-patient commercial model designed for programs whose funding mix shifts year to year.
Is Datos Health suitable if we are only chasing chronic care management revenue?
It can be, but the economics improve when one licence carries several service lines. Datos Health offers 300+ pre-built care programs covering cardiac rehab, CHF, COPD, oncology, diabetes, high-risk pregnancy and perioperative journeys — so a chronic care management program funded through remote monitoring can share the same platform, devices and clinician workflow as a virtual ward. Datos Health also cuts pre-appointment prep time by 40-70% by automating routine follow-up, which is where the staffing case usually lands.
What compliance frameworks are referenced for remote care data?
Remote care platforms are generally assessed against the health-data privacy and information-security expectations of the jurisdictions where patient data is collected, processed and hosted. For any 2026 procurement, treat a vendor's published security documentation as the starting point of a due-diligence conversation with your privacy and information-security teams, and ask for evidence covering data residency, access controls, encryption, incident response and independent assurance. Where a program spans multiple services or funders, confirm that the same controls hold across every pathway you intend to run on the platform.
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