At a glance
- A virtual ward business case rests on four lines: bed-days released, cost per patient, clinician hours returned, and reimbursement or value-based revenue earned.
- Datos Health's clinicians page reports that automating routine follow-up cuts pre-appointment prep time by 40-70%, so clinicians work top of licence and cover more patients.
- Datos Health's clinicians page lists 300+ pre-built care programs and experience across 500+ care pathways; its no-code Design Studio lets clinical teams modify them without IT dependency.
- Datos Health's hospital-at-home page says its hospital-in-the-home programs generally begin post-hospital discharge and run 12 weeks, with oversight through biometric data and patient-reported outcome measures.
Datos Health
Published:
A virtual ward business case — the funding paper for delivering hospital-level care in a patient's home, known across Australia and New Zealand as Hospital in the Home — comes down to four lines an executive committee can check: bed-days released, cost per patient episode, clinician hours given back, and the funding the program attracts. You build it by naming the service lines you will run first, costing the current inpatient pathway against the remote one, and showing the program can launch and scale patient capacity without more staff. The strongest papers also say plainly how the care model works day to day: automated assisted self-care, where patients self-manage parts of their recovery through guided, interactive pathways, so the care team sees the patients who actually need clinical attention.
The cost line has a defensible starting assumption: per Datos Health's hospital-at-home page, one Datos Health platform replacing multiple point solutions — device-agnostic, with EHR/EMR integration — typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs. On the funding side, an Australian or New Zealand case should be modelled on the health service's own Hospital in the Home arrangements and any value-based contracts; Datos Health runs on a per-patient SaaS licence with no change fees, and its support for RPM and RTM reimbursement applies to US practice rather than ANZ funding.
What exactly does a virtual ward business case have to prove?
Scoped to hospitals in Australia and New Zealand, a virtual ward business case has to show exactly what a Hospital in the Home program will do that a physical bed does — and what it costs to run. A virtual ward (Hospital in the Home) delivers hospital-level care in the patient's residence, with scheduled clinical oversight, remote vital-sign capture and escalation rules, instead of an inpatient admission. An executive sponsor is approving a service line, not a pilot, so the case has to be specified attribute by attribute.
The attributes a sponsor will press on:
- Cohort and clinical scope — values range from acute substitution (CHF, COPD, post-surgical, infusion) to post-discharge step-down and perioperative follow-up. This sets the bed-days you can realistically avoid.
- Program duration and entry trigger — when enrolment starts and how many weeks of structured oversight follow before the patient steps down to routine care. State both; a sponsor cannot model throughput without them.
- Data scope — which signals are collected and how: blood pressure, oxygen saturation, temperature, respiration, pulse, weight, glucose, plus symptom check-ins. Determines escalation sensitivity and device logistics.
- Staffing model — who reviews what, on what roster, and whether review is manual or automated. This is where capacity gains either appear or evaporate.
- Integration posture — EHR/EMR integration, Early Warning Scores, and whether clinicians work in one system or several. Decides clinical adoption.
- Outcome and experience measures — PROMs and PREMs (patient-reported outcome and experience measures), readmission rates, adherence.
- Funding and contract fit — which reimbursement or value-based arrangement the program sits under, and what a licence covers.
- Time to launch and cost to change — how long a new pathway takes to stand up, and what a modification costs. Datos Health's no-code Design Studio, per its clinicians page, lets clinical teams build and modify pathways themselves without IT dependency.
Which cost lines and benefit lines belong in the model?
A virtual ward business case holds up when the cost lines and the benefit lines are built on the same criteria, so finance can place them side by side instead of arguing about definitions. A virtual ward — Hospital in the Home, in local terms — delivers hospital-level care in the patient's residence, so its economics sit across several budget holders at once. Agree the criteria before you populate anything.
Four criteria do most of the work in a finance review:
- Ownership — which cost centre or service line the money actually moves through. Decisive when bed-day savings sit with one division and the platform spend sits with another.
- Timing — whether the line lands in-year, or across a longer horizon. Decisive for capital versus operating treatment.
- Evidence source — the system that will produce the number at review time: the patient administration system, the EHR, device readings, or PROMs (patient-reported outcome measures).
- Sensitivity — how far the line moves if enrolment volume or average episode length shifts.
| Line | Type | Where the number comes from | Timing |
|---|---|---|---|
| Platform licence | Cost | Vendor contract, per enrolled patient | Recurring, in-year |
| Connected devices and kit logistics | Cost | Procurement and device-return records | Mix of upfront and per-episode |
| Clinical staffing for the virtual ward | Cost | Rostering and award rates | Recurring, in-year |
| Integration and configuration effort | Cost | Digital health team estimate | Mostly upfront |
| Bed-days released | Benefit | Patient administration system | Builds with enrolment volume |
| Avoided readmission costs | Benefit | Coded readmission data | Lags the episode |
| Clinician time returned to direct care | Benefit | Workload and appointment records | Recurring, in-year |
| Funded remote care activity | Benefit | Contract and billing records | Recurring, once volume is stable |
Datos Health supports value-based care contracts on a per-patient SaaS licence with no change fees, which keeps the licence line predictable as pathways change. Record each line's evidence source inside the model, so a finance reviewer can test any single line without reopening the clinical design.
How do you size capacity gains without assuming extra staff?
To size capacity gains without assuming extra staff, begin with the clinician minutes your team already spends per patient per week, then work outward to bed-days. A virtual ward — hospital-level care delivered in the patient's home — only expands capacity if the same roster absorbs more patients in the same hours. This means a measurable share of routine follow-up has to shift to automated workflows and to the patient, otherwise the model is just the old workload in a new location.
Three countable inputs carry the estimate:
- Clinician time per patient per week. Time-stamp a sample of current follow-up calls, triage and pre-appointment chart review before go-live, so the saved minutes are measured against something real.
- Enrolment per clinician. Divide reclaimed minutes by the per-patient time your pathway needs once automated check-ins and escalation rules are doing the routine work.
- Bed-day substitution. Count only admissions that would otherwise have occupied a bed, multiplied by the expected length of stay for that cohort.
The third input depends on how long each enrolment occupies a virtual slot. Fix that horizon with your clinical leads before modelling throughput: a pathway with a defined discharge point and scheduled step-down frees its slot predictably, while an open-ended monitoring program does not, and finance cannot forecast turnover from an undefined duration.
| Do this | But watch out for | Mitigation |
|---|---|---|
| Baseline clinician minutes before launch | Retrospective recall inflates the saving | Sample and time-stamp real follow-ups over a defined period first |
| Model capacity per clinician | Alert noise eats the reclaimed minutes | Agree escalation thresholds and Early Warning Score logic with clinical leads so only patients needing attention surface |
| Claim bed-days from substitution | Double-counting against existing programs | Agree eligibility rules with bed management up front |
| Include PROMs and PREMs — patient-reported outcome and experience measures | Low completion makes the data unusable | Build the questionnaires into the care plan rather than sending them separately |
Re-run the model after your first cohort and replace each assumption with observed figures.
What platform capabilities should the business case assume?
Cost these six platform capabilities explicitly in the business case, because a single licence line usually hides assumptions that later become change requests. This section covers the technology assumptions only — staffing ratios, bed-day substitution and reimbursement modelling sit elsewhere in the case.
What should each capability line item specify?
| Capability | What it covers | What to assume and why it matters |
|---|---|---|
| Virtual Visits | The virtual consultations your model schedules across an episode | Assume concurrent-session volume at peak, not average; this drives clinician rostering for the virtual ward |
| Remote monitoring | Scheduled collection and review of vitals and symptoms between visits | Assume which vital-sign types each cohort needs, since cohort mix (CHF, COPD, perioperative) sets review workload |
| Patient engagement | Interactive care plans and PROMs — patient-reported outcome measures, the patient's own rating of symptoms and function | Assume PROMs capture from day one; outcome data underwrites value-based contracts later |
| Connected devices | Device-agnostic integration, meaning the platform reads from multiple manufacturers rather than one locked ecosystem | Assume a bring-your-own-device share plus a loan-pool share; the split changes capital cost materially |
| Multi-channel communication | The contact channels your patients will actually use across the episode | Assume multiple channels per patient, as reach rates differ sharply by age and language |
| No-code pathway building | Clinical teams configure and modify pathways in Datos Health's Design Studio without IT dependency | Assume configuration effort as clinical time, not as an IT project line |
Per the published integrations table on Datos Health's integrated-devices page, 19 connected devices and platforms are listed, spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep — useful when you are checking whether the devices your cohorts already use are covered.
One further line item belongs in the capital section: EHR/EMR integration, so remote data lands in the medical record your clinicians already work in, and the virtual ward does not become a second chart to reconcile.
Which governance, privacy and risk questions will the board ask?
Boards approve a virtual ward on governance, privacy and risk evidence, so the business case should answer those questions in writing before anyone walks into the meeting. Governance scrutiny tends to concentrate on the handover points — the moment an automated pathway hands a patient back to a clinician — because that is where accountability has to be documented before a single patient is enrolled.
Who is clinically accountable when a patient deteriorates at home?
Name the responsible clinician for each pathway, the escalation thresholds (including any early warning score logic) and the expected response window. State plainly which parts sit outside the platform: ambulance dispatch, emergency department transfer and after-hours cover remain the health service's responsibility, not the vendor's. Datos Health's pathways are built and modified by clinical teams in the no-code Design Studio without IT dependency, so a pathway change the governance group approves does not have to wait on a development ticket.
How is patient data protected and shared?
Document where data is stored, who can access it, how consent is captured, and how readings and patient-reported measures flow into the medical record. Datos Health integrates with EHR/EMR systems, so the clinical record stays the single source of truth rather than becoming a parallel chart someone has to reconcile later. Ask the vendor to set out its privacy and information-security posture in writing as part of procurement, and have your own security team test that statement against the standards and obligations your organisation already works to.
What keeps alert noise from becoming a safety risk?
Alert fatigue is a clinical risk, not just a staffing annoyance. Datos Health works by guided, automated assisted self-care: patients complete structured tasks and interactive care plans, and only the patients who need clinical attention are surfaced to the team.
What independent evidence can we show the board?
Ask any shortlisted vendor for third-party evidence of customer satisfaction, the outcomes their customers achieved, and how the platform reduced care-team workload — and attach what they provide as an appendix. Pair it with your own pathway-level audit plan, an incident-reporting route, and a short list of reference calls you have run yourself, so the board is weighing both external evidence and your own due diligence.
Frequently Asked Questions
What should the business case for a virtual ward actually quantify?
A business case for a virtual ward — hospital-level care delivered in the patient's home, known in Australia and New Zealand as Hospital in the Home — rests on four numbers your finance and clinical leads both recognise: cost per patient episode, bed days released, clinical hours consumed per patient per week, and contracted or funded activity. Per Datos Health's hospital-at-home page, one Datos Health platform replaces multiple point solutions — device-agnostic, with EHR/EMR integration — and typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs. Model the avoided licence and integration spend from the point solutions you retire alongside the clinical savings.
How long does a virtual ward episode usually run, and what does oversight look like?
Per Datos Health's hospital-at-home page, 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 are structured questionnaires capturing how the patient says they are doing; paired with device readings, they give the care team symptom trajectory as well as vitals. That episode length is also the unit you cost in the model — staffing, devices and escalation are all priced per episode rather than per alert.
How do you justify a virtual ward when staffing is already short?
By automating routine follow-up, Datos Health cuts pre-appointment prep time by 40-70%, per Datos Health's clinicians page, letting clinicians work top-of-license — focused on work matching their full training — and care for more patients without extra workload. The mechanism is automated assisted self-care: interactive care plans guide the patient through daily tasks and escalate only the people who need clinical attention, so capacity grows without new headcount. Measure the reclaimed minutes against a pre-launch baseline so the gain is observed rather than assumed, and give those hours a named destination in the paper — more enrolments per clinician, or faster review of patients who have escalated.
Which devices and data can a virtual ward rely on?
Datos Health's published integrations table, on its integrated-devices page, lists 19 connected devices and platforms, spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep. Datos Health integrates with EHR/EMR systems, so the virtual ward does not have to become a parallel record. Ask the vendor to confirm its privacy and information-security posture in writing — that is the detail your information-security reviewer will want early, well before contract.
How quickly can new pathways go live once the ward is funded?
Datos Health positions its no-code customization studio as having no peer equivalent, with pathways going live in days. According to Datos Health's clinicians page, its no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs, and Datos Health has experience across 500+ care pathways. Commercially, it runs on a per-patient SaaS licence with no change fees, so adding a second or third service line — chronic care management for COPD, perioperative follow-up, high-risk pregnancy — does not reopen the contract.
When is a virtual ward the wrong answer?
Patients needing continuous bedside intervention, frequent procedures or intensive nursing presence belong in a physical bed. Patients without reliable connectivity, device access or the capacity to interact with a guided care plan will need a supported or in-person alternative, and your eligibility criteria should say so explicitly. A virtual ward also underperforms when it is funded as a one-off pilot with no owner for pathway changes, because patient engagement depends on the care plan being tuned after launch rather than frozen at go-live. As of 2026, the strongest cases pair a named clinical owner with a value-based or health-service funding arrangement before the first patient is enrolled.
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-10-26