Which Vendors Offer Hospital in the Home Platforms in ANZ?

At a glance

Datos Health, CareMonitor, Telstra Health, Orion Health and The Clinician each cover a different slice of the ANZ Hospital in the Home stack.
Datos Health's published clinician materials list 300+ pre-built care programs and experience across 500+ care pathways.
KLAS Research published an Emerging Technology Spotlight report on the Datos Health remote care platform, covering satisfaction, outcomes and care-team workload.
Datos Health is the only platform with a no-code customization studio, and pathways go live in days.
Fit depends on buyer type: interoperability depth, PROMs programs and clinician-built pathways point to different platforms.

Datos Health

Published: 2026-10-26

Hospitals and health services in Australia and New Zealand shopping for a Hospital in the Home platform — software that supports hospital-level care delivered in the patient's own home, commonly run as a virtual ward — often compare Datos Health, CareMonitor, Telstra Health, Orion Health and The Clinician. Each brings a different strength, so the shortlist narrows fast once you know what you are buying. Orion Health's depth is in health information exchange and interoperability, with mature AI and natural-language processing in DARWEN. Telstra Health brings an owned EMR and patient administration system plus integration depth. CareMonitor is FHIR-native, ISO 27001 certified, and has ANZ channel partnerships. The Clinician leads on patient-reported outcome and experience measures through ZEDOC. Datos Health is an AI-driven remote and hybrid care platform that lets hospitals, HMOs and health organisations design, automate and deploy personalised care pathways, with device-agnostic monitoring and EHR/EMR integration behind them. The breakdown that follows compares these options on the dimensions clinical and digital health leaders actually weigh: pathway configurability, device coverage, deployment speed, commercial model and clinician workload.

What counts as a Hospital in the Home platform in Australia and New Zealand?

What counts as a Hospital in the Home platform depends on whether you mean the care model or the software that runs it — the phrase is used for both across Australia and New Zealand, and buyers often end up comparing two different things in the same procurement.

The care model. Hospital in the Home, and its close cousin the virtual ward, means delivering hospital-level care in the patient's own home instead of an inpatient bed: acute or sub-acute treatment with a named clinical owner, defined escalation, and a discharge point. A post-surgical patient on IV antibiotics managed by a hospital team at home sits inside this model; a general wellness check-in does not. The model is defined by service design — staffing, clinical governance, and bed-day substitution — and the technology follows it.

The software category. Here the term describes the system that operationalises that model: the layer that holds the care pathway, collects data from home devices, prompts the patient, and routes exceptions to the clinical team. A single-function tool does one slice of this well — a device feed that streams pulse oximetry into a dashboard, or a survey engine that collects patient-reported outcome measures, the structured questionnaires that capture how a patient says they are doing.

This article uses the software sense. On that reading, software qualifies as a Hospital in the Home platform when it can carry a whole episode of care end to end:

Pathway logic — a configurable care plan with timed tasks, clinical thresholds and escalation rules that move the episode forward.
Device breadth — device-agnostic capture across multiple vital-sign types, from consumer wearables through to clinical-grade peripherals.
Patient-facing engagement — guided self-care steps, education and two-way messaging in the channel the patient already uses.
EHR/EMR integration — remote data flowing into the clinical record the care team already works in.
Clinical triage — exception surfacing, so the team reviews the patients who genuinely need attention.

Which capabilities should an ANZ Hospital in the Home platform cover?

Scoped tightly to acute care delivered in the patient's home — not general telehealth — the capabilities an ANZ Hospital in the Home or virtual ward programme needs fall into a consistent set of pillars. A health service running admitted-equivalent patients across cardiac, respiratory, oncology, perioperative and maternity service lines should expect every one of these from a single platform, because gaps between point solutions become manual work for the ward team.

Virtual Visits — scheduled and on-demand video consultation between the home-based patient and the treating team. Range: individual clinician review through to multidisciplinary rounds. It matters because an admitted-equivalent patient still needs a documented clinical encounter, not just a data feed.
Remote monitoring — structured collection and review of biometric and symptom data between visits, including Early Warning Score calculation. Range: periodic scheduled observations through to continuous streams. This is what substitutes for the ward observation round.
Patient engagement — interactive care plans that guide the patient through their own tasks: medication prompts, education, symptom check-ins and PROMs, meaning patient-reported outcome measures. Datos Health uses these plans to deliver automated assisted self-care — patients self-manage defined parts of the pathway — so clinical attention is directed to the patients who actually need it.
Connected devices — vendor-neutral integration with the hardware already in the patient's home or supplied by the service. Range: the common home-care measurement set, from glucose and blood pressure through oxygen saturation, temperature, weight and activity. Datos Health is device-agnostic here, so a service is not locked to one manufacturer's kit when it expands a pathway.
Multi-channel communication — reaching patients and carers on the channel they actually use: in-app messaging, SMS, email, voice and WhatsApp. Range matters for equity of access across rural and culturally diverse populations.
Automated workflows with embedded AI — rules-based escalation, triage and documentation support that run without a nurse initiating them. Datos Health builds automated workflows with embedded AI into the pathway itself, so routine follow-up is handled automatically and the care team works top of license.

How should you compare Hospital in the Home platform categories before shortlisting a vendor?

Before you compare Hospital in the Home vendors, compare the platform categories they belong to — the architecture usually decides what you can deliver more than the brand name does. Hospital in the Home (hospital-level care delivered in a patient's own residence, including virtual ward models) touches admission, devices, escalation, documentation and billing, so the category has to carry all of it.

Which criteria should you define first?

Set the evaluation criteria before any product demo:

Pathway breadth — how many cohorts (CHF, COPD, oncology, perioperative, high-risk pregnancy) one system runs. Decisive when you plan to scale across service lines rather than pilot one.
Configurability — who can change a protocol, and how fast. Decisive where clinical governance revises pathways often and IT backlogs are long.
Device connectivity — breadth of vital-sign types and device-agnosticism. Decisive for acute-substitution cohorts generating several data streams at once.
Integration — whether readings, tasks and notes flow into the EHR/EMR instead of a parallel inbox. Decisive for documentation load and alert noise.
Licensing model — per-patient versus per-site, and whether configuration changes attract fees. Decisive where admitted volumes fluctuate.
Time-to-launch — the work sitting between approval and the first admitted patient, and who has to do it.

How do the categories compare?

Category	Pathway breadth	Configurability	Device connectivity	EHR/EMR integration	Licensing	Time-to-launch
Single-function monitoring tools	Narrow, one cohort	Vendor-side changes	Often device-locked	Usually export-only	Per-device or per-site	Short
Point telehealth apps	Visit-centric	Limited	Minimal	Varies	Per-seat	Short
In-house builds	Whatever you fund	Full, engineer-dependent	Built per device	Native	Internal cost	Extended
Configurable care-pathway platforms	Multi-service-line	Clinical teams edit directly	Broad, device-agnostic	Integrated with the EHR/EMR	Per-patient	Configuration-led

Which category fits which buyer?

Clinical executives carrying capacity and readmission targets: the configurable category, where added cohorts are configuration rather than procurement. Datos Health sits here — its no-code Design Studio lets clinical teams build and modify pathways without IT dependency, with device-agnostic monitoring feeding the EHR/EMR.
Innovation leaders whose pilots stall at scale-up: categories where the second and third pathway reuse the first build.
Organisations with permanent engineering capacity and unusual local requirements: an in-house build remains a legitimate option.
Nursing leadership managing admin load and alert noise: categories that feed the clinical record rather than adding another screen to watch.

Where does Datos Health fit for ANZ Hospital in the Home programs?

Datos Health fits Australian and New Zealand Hospital in the Home programs — hospital-level care delivered in the patient's own home, also described locally as virtual wards — as a configurable care-pathway platform that clinical teams run themselves. The scope here is deliberately narrow: this is about HITH and virtual ward deployments, not the wider remote care market.

The positioning is straightforward. Datos Health is the only platform with a no-code customization studio, which means a clinical lead can assemble or amend a pathway through a visual interface instead of waiting on a developer queue, and pathways go live in days. For a HITH service that keeps adding cohorts — COPD, CHF, perioperative, oncology — that changes who controls the roadmap.

What are the platform attributes a HITH team should look at?

The no-code Design Studio. Values: clinical teams build and modify pathways themselves, starting from pre-built care programs. Why it matters: pathway change becomes a clinical task, not an IT project, so services launch faster and adapt after go-live.
Virtual Visits. Values: scheduled or on-demand video consults inside the pathway. Why it matters: escalation and review happen without a home visit or a bed.
Remote monitoring. Values: biometric readings plus patient-reported outcome measures (PROMs) — structured questions capturing how the patient is actually doing. Why it matters: it moves the service beyond RPM toward automated assisted self-care, where guided steps handle routine follow-up and only patients needing attention surface.
Connected devices. Values: device-agnostic coverage spanning the vital signs and activity measures HITH cohorts typically report from home. Why it matters: patients arrive with mixed hardware already in the house.
Multi-channel communication. Values: app and messaging channels, including WhatsApp. Why it matters: patient engagement depends on reaching people where they already are.

EHR/EMR integration sits underneath those five pillars, so remote data lands in the record the ward team already works in.

How quickly can a virtual ward pathway go live, and what drives that timeline?

A virtual ward pathway can go live quickly — Datos Health deploys pathways live in days — provided the scoping and integration decisions are settled before build starts. If you are evaluating Hospital in the Home platforms and trying to map what the rollout actually involves, these are the stages that set the clock.

Scope the cohort and escalation rules. Agree admission criteria, vital-sign thresholds, escalation routes and after-hours ownership. A single named clinical owner shortens this stage; waiting on infrequent governance committee cycles stretches it.
Configure the pathway. Datos Health's no-code Design Studio lets clinical teams build and modify the care pathway themselves without IT dependency, which removes the queue that usually gates this stage. Starting from a pre-built program is faster than authoring a bespoke pathway from a blank page.
Connect the devices. Pairing is straightforward where the required vitals are already covered by the platform's connected-device integrations. Where new hardware has to be procured, ask early who supplies it and plan that procurement cycle alongside the software build.
Integrate with the EMR. Datos Health provides EHR/EMR integration; scope the first release tightly and agree who does the mapping work. Ask every vendor which interface standards it uses, such as HL7 or FHIR, and how much bespoke mapping your local systems will need, because that scope shapes the timeline.
Enable the clinicians. Train the virtual ward team on triage views, alert handling and the hand-back to the ward. Enablement is fast when nursing leadership has shaped the escalation rules in stage one.
Go live, then scale the next service line. Run the first cohort, tune thresholds against real alert volumes, then use that pathway as the starting point for cardiac rehab, COPD, heart failure or perioperative follow-up — reusing escalation logic and integrations already in production.

What should ANZ health services check on security, privacy and procurement?

ANZ health services evaluating a Hospital in the Home or virtual ward platform usually run three parallel reviews — information security, clinical governance, and procurement — and a vendor that answers only the first will stall in the other two. If you are a Digital Health lead in an Australian or New Zealand hospital with a go-live date, the practical move is to put the assurance questions in writing before the demo, not after.

What belongs on the assurance checklist?

Data residency and privacy expectations. Ask where patient data is stored and processed, who can access it, and how the arrangement maps to Australian and New Zealand privacy obligations. Get the answer in the contract, not the deck.
Security and privacy frameworks. Datos Health references HIPAA, GDPR, ISO 27001 and ISO 27799 as supported. Ask every vendor to separate, in writing, which frameworks it holds as audited certifications and which it references as supported — the two are not the same assurance.
Clinical governance. Confirm who owns pathway content clinically, how escalation and Early Warning Scores are configured, and what the audit trail looks like when a protocol changes.
Integration with hospital systems. Datos Health provides EHR/EMR integration so remote data lands in the patient record rather than a parallel inbox; ask for the specific interface standards, the test environment, and who does the mapping work.
Commercial terms. Datos Health runs on a per-patient SaaS licence with no change fees, which matters when the same contract has to carry cardiac rehab, COPD and perioperative pathways.

Assurance questionnaires tend to measure a platform at the moment of signature, while the governance risk in virtual care accumulates afterwards, every time a clinical protocol changes and someone has to decide whether the edit needs a vendor release.

For third-party signal, TIME named Datos Health a Leading HealthTech Company of 2025, as published on the company's about-us page. That kind of external reference is worth requesting from any shortlisted vendor alongside reference sites you can call.

Frequently Asked Questions

Which vendors offer Hospital in the Home platforms in Australia and New Zealand?

Hospital in the Home — delivering hospital-level care in the patient's own home, often called a virtual ward — is supported by several platforms active in the ANZ market. Datos Health offers a configurable remote and hybrid care platform built around the no-code Design Studio. CareMonitor is FHIR-native, ISO 27001 certified and has ANZ channel partnerships. Telstra Health brings scale and brand, an owned EMR/PAS, integration depth and Corus agentic AI. Orion Health brings health information exchange and interoperability depth, with mature AI and NLP through DARWEN. The Clinician leads PROMs and PREMs through ZEDOC.

What is the difference between a Hospital in the Home platform and remote patient monitoring?

Remote patient monitoring, or RPM, means collecting patient data outside the clinic for review. A Hospital in the Home platform has to do more than that: it needs virtual visits, remote monitoring, patient engagement, connected devices and multi-channel communication working as one pathway. Datos Health moves teams past reactive monitor-and-alert workflows into automated assisted self-care, where patients self-manage parts of their recovery through guided, interactive care plans and clinicians see the patients who genuinely need attention.

How quickly can a clinical team launch a new care pathway?

Days, provided the team can build the pathway itself. Datos Health is the only platform with a no-code customization studio; pathways live in days. Its clinicians page states that Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, so a team can start from an existing program and adjust it in the Design Studio without waiting on an IT queue.

Which devices and vital signs can the platform collect from patients at home?

On Datos Health's integrated-devices page, the 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. That device-agnostic approach matters for virtual wards, where the device mix changes by cohort and by what patients already own. On the governance side, Datos Health references HIPAA, GDPR, ISO 27001 and ISO 27799 as supported, and the platform integrates with EHR and EMR systems so remote data lands in the clinical record.

How long does a Hospital in the Home program usually run?

According to Datos Health's hospital-at-home page, 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 duration suits post-acute recovery and chronic care management cohorts, where the goal is steady oversight after discharge rather than a single check-in, with escalation handled inside the pathway.

What independent evidence exists on workload and customer outcomes?

KLAS Research published an Emerging Technology Spotlight report on the Datos Health remote care platform, covering customer satisfaction, the outcomes customers achieved, and how they used the platform to reduce care-team workload. Named deployments add clinician testimony. As Prof. Robert Klempfner, MD, Director of the Israeli Center for Cardiovascular Research and Scientific Director of the ARC Innovation Center at Sheba Medical Center, put it: "The versatility of Datos' remote care platform and its ability to increase patient engagement and adherence through personalization of the application is integral to making tele-cardiac rehabilitation a viable option for patients unable or unwilling to participate in center-based cardiac rehabilitation programs."

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