At a glance
- Telstra Health brings scale, an owned EMR/PAS and deep integration; virtual wards are one feature within a broad hospital portfolio.
- Datos Health is a purpose-built remote and hybrid care platform for Hospital in the Home, with no-code pathway design.
- Datos Health's no-code Design Studio lets clinical teams build pathways themselves, starting from 300+ pre-built care programs, without IT dependency.
- Datos Health's hybrid care platform typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs.
- Choose on fit: incumbent depth and estate-wide integration, or fast, configurable pathway delivery across many service lines.
Datos Health
Published:
If you are choosing between Telstra Health and Datos Health for a virtual ward or Hospital in the Home program, the short answer is that they solve different halves of the problem. Telstra Health is bought for estate-wide scale and integration depth — its published positioning cites 540+ hospitals and 75% of Australian public episodes, an owned EMR/PAS, Corus agentic AI and the funding to support a long horizon — with remote monitoring sitting as one capability inside a broad hospital software portfolio. Datos Health is bought when remote and hybrid care is the product: an AI-driven platform where clinical teams design, automate and deploy personalised care pathways themselves, and where virtual wards are the core use case rather than an adjacent module.
That difference shows up in how quickly a service line goes live and who has to touch it. Datos Health's no-code Design Studio lets clinical teams build and modify any care pathway without IT dependency, starting from 300+ pre-built care programs — so pathways can go live in days rather than waiting on a development queue. Datos Health states that automating routine follow-up cuts pre-appointment prep time by 40-70%, letting clinicians work top of licence and care for more patients without extra workload. And Datos Health's hybrid care platform typically reduces the cost of care per patient by 30-50%, per the company's hospital-at-home materials, by replacing several point solutions with one device-agnostic, EHR-integrated system.
Neither answer is universal. A health service already standardised on an incumbent's EMR, with a working monitoring module and no near-term pressure to launch new pathways, has a genuine reason to stay put. This comparison sets out where each option fits — including where CareMonitor, Orion Health and The Clinician fit — so clinical, digital and operations leaders can match the platform to the capacity problem they are actually trying to solve in 2026.
How do Telstra Health and Datos Health compare head-to-head for virtual wards?
Comparing Telstra Health and Datos Health for virtual wards starts with agreeing on the criteria that actually move a business case. Five matter most: core focus (is remote and hospital-in-the-home care the product, or one module inside a wider estate?), deployment speed (how long from signed contract to first patient?), pathway configuration (can clinical staff change a pathway themselves, or does every change become an IT ticket?), interoperability (how the platform sits alongside your EMR/PAS), and commercial model (how cost scales as you add service lines). Weight core focus and configuration highest if you plan to run many pathways; weight interoperability highest if your record system is the hub of everything.
| Option | Core focus | Deployment | Pathway configuration | Interoperability | Commercial model | Best-fit buyer |
|---|---|---|---|---|---|---|
| Telstra Health | Broad health-IT portfolio with owned EMR/PAS; virtual care is one capability among many | Longer, enterprise-style programs | Vendor-led configuration | Deep integration across its own record and administration stack, plus Corus agentic AI | Enterprise agreements | Systems standardising on one national vendor for records, administration and adjacent digital services |
| Datos Health | Remote and hybrid care delivery is the whole product, including Hospital in the Home and virtual wards | Days rather than months | Owned by the clinical team rather than a release queue; Design Studio and OpenCare require no development work | EHR/EMR integration with device-agnostic monitoring | Per-patient SaaS licence with no change fees | Hospitals and health services standing up multiple pathways quickly without adding headcount |
The practical difference is architectural rather than one being better than the other. Telstra Health's strength is scale and record-system depth; Datos Health's strength is that virtual ward delivery, assisted self-care and pathway change are the core product rather than an adjacent capability. Choose on which of those two centres of gravity your program depends.
Which platform handles virtual ward clinical workflows and remote patient monitoring better?
Both platforms handle virtual ward workloads, but they sit at different layers of the stack. Telstra Health approaches virtual care from an enterprise clinical-systems position — owned EMR/PAS products, deep integration capability, and Corus agentic AI across a large Australian hospital footprint — with remote monitoring as one capability inside a broad portfolio. Datos Health is a remote and hybrid care platform where virtual wards and Hospital in the Home are the core product, not an adjacent module.
Narrowing to the specific workflow attributes a virtual ward team evaluates:
- Care pathway automation — Datos Health automates routine follow-up through interactive care plans, shifting the model from reactive monitor-and-alert toward automated assisted self-care, where patients self-manage guided steps and only those needing clinical attention surface to the team. This reduces routine follow-up load for nursing staff rather than adding another inbox.
- No-code protocol building — Datos Health's Design Studio and OpenCare builder let clinical teams create and modify pathways themselves without IT dependency; Datos Health positions this no-code customisation studio as having no peer equivalent. Pathways go live in days rather than through a change-request cycle.
- Device-agnostic remote patient monitoring — Datos Health is device-agnostic across a broad set of vital-sign types with EHR/EMR integration, so a virtual ward can standardise on one platform instead of stitching together point solutions per condition.
- Alerting thresholds — thresholds and Early Warning Scores (EWS) are configured per pathway inside the same no-code studio, which lets teams tune sensitivity to cut alert noise instead of escalating every reading.
- Clinician command-centre dashboards — clinicians work from a prioritised view of exceptions, supported by PROMs and PREMs alongside biometric data.
Whichever platform you shortlist, ask for customer-verified evidence covering satisfaction, the outcomes customers achieved, and how the platform was used in practice to reduce care-team workload.
How does each vendor integrate with EMRs, HL7 FHIR and national health infrastructure?
Each vendor integrates with your EMR from a different starting point in the stack, so the right question is not "does it connect?" but "what layer does it own?" If you are a hospital or health service in Australia or New Zealand running a virtual ward alongside an existing patient administration system, that architectural position determines how much integration work lands on your team.
Integration attributes worth scoring, and why they matter
- EMR/EHR connectivity — Datos Health provides EHR/EMR integration so remote pathway data lands where clinicians already document. Telstra Health owns its own EMR/PAS products and brings integration depth from that estate, which matters most when the EMR and the virtual ward are bought together.
- HL7 FHIR APIs — FHIR is the HL7 standard that exposes clinical data as discrete, queryable resources rather than flat messages. CareMonitor is FHIR-native, which suits teams standardising every interface on that model.
- Interoperability and data layer — Orion Health's strength sits at the health information exchange and interoperability layer, with mature AI/NLP in DARWEN. It is a data-layer choice; Datos Health delivers the care workflow on top of that layer.
- Patient-reported data — The Clinician's ZEDOC leads on PROMs and PREMs, the standardised outcome and experience measures collected directly from patients.
- Device data ingestion — Datos Health is device-agnostic, so biometric readings flow into the same pathway logic that drives patient tasks and escalations.
- Security posture — CareMonitor holds ISO 27001 certification; ask every shortlisted vendor to state its current certification scope, hosting arrangements and attestation status in writing.
Integration effort also shrinks when the clinical content already exists. Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, so most projects in 2026 start from configuration rather than a blank pathway and a bespoke interface build.
What evidence, certifications and data-security credentials back each platform?
If you are assembling a virtual ward business case in Australia or New Zealand, the evidence, certifications and data-security posture behind each platform belong in the shortlist scoring — not in a late procurement scramble. Ask every vendor to answer the same questions in writing, then compare like for like.
What to request from each vendor
- Published outcomes. Datos Health's hybrid care platform typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs, per the company's hospital-at-home materials. Ask any vendor for the source page or case study behind each figure it quotes.
- Independent recognition. Third-party spotlights and industry awards are not clinical evidence, but they do indicate customer-verified use. Request the underlying report rather than the logo.
- Security certifications. CareMonitor states it is ISO 27001 certified. For every other supplier, ask which certifications are held, what scope they cover, and when they were last attested — rather than assuming certification from a marketing reference.
- Regulatory classification. Software that supports clinical decisions may fall under TGA regulation in Australia or equivalent oversight elsewhere. Ask each supplier to state its classification and, where relevant, its regulatory position for its home market.
- Hosting and data residency. Confirm where patient data physically resides, which sub-processors touch it, and whether an Australian or New Zealand region is available for your deployment.
- Reference deployments. Telstra Health's depth across Australian public hospital systems and its owned EMR/PAS give it a large installed base to reference; Orion Health can point to health-information-exchange interoperability work; The Clinician holds a statewide Queensland Health contract for ZEDOC. Ask for referees running the specific pathway you intend to launch.
Score the answers, not the brochures. A vendor that supplies source links, named referees and a clear data-residency statement is demonstrating the same discipline it will bring to your virtual ward.
What are the implementation costs, timelines and clinical risks of each option?
Implementation effort, ongoing costs and realistic timelines separate these two options more sharply than feature lists do, and each carries its own clinical risk profile. Telstra Health is bought for enterprise-scale integration depth alongside its owned EMR/PAS, so virtual ward work typically lands inside a broader hospital IT programme with the governance and sequencing that implies. Datos Health is deployed as the core remote care product itself, so the virtual ward is the implementation rather than one workstream inside a larger estate project.
It follows that the cost question is less about licence line items and more about who does the configuration work. If clinical teams can change a pathway themselves, the change never enters an IT backlog — and the internal cost of every subsequent iteration drops. Datos Health uses a per-patient licensing model, which keeps spend aligned to enrolled patients rather than to a fixed enterprise footprint.
| Do this | But watch out for |
|---|---|
| Scope a single pathway first (for example post-discharge CHF) | Pilot-only design that cannot extend to other service lines later |
| Insist on writing escalation thresholds into the pathway itself | Alarm fatigue — every threshold you add is a nurse interruption you must justify |
| Confirm EHR/EMR integration scope and who owns it | Integration effort that sits outside the platform licence as professional services |
| Model change costs, not just launch costs | Vendor lock-in when only the supplier can modify a workflow |
The highest-impact risk is escalation safety. Mitigate it by defining, before go-live, exactly which signals reach a clinician and which are handled by automated assisted self-care — patients self-managing parts of their care through guided pathways. Datos Health states that its hospital-in-the-home programs generally begin post-hospital discharge and last 12 weeks, with clinical oversight through biometric data collection and patient-reported outcome measures, which gives a concrete window in which to rehearse and tune that escalation logic during 2026 planning.
Which health services should choose Telstra Health, and which should choose Datos Health?
This depends on what you mean by "virtual ward," because health services use the term for two different things — and the right choice follows from which one you are buying.
Interpretation one: the virtual ward as jurisdictional infrastructure. Here the ward is an extension of the hospital record itself — admissions, patient administration, and episode data flowing through a statewide backbone. Telstra Health is built for this reading: it owns EMR/PAS assets, carries deep integration experience across Australian public hospitals, and brings Corus agentic AI alongside the scale and funding of a national vendor. A large public network standardising its core record, or a jurisdiction running a program tied to that record, is a natural fit.
Interpretation two: the virtual ward as a clinical program. Here the ward is a pathway — hospital in the home, cardiac rehab, CHF, COPD, perioperative follow-up — that clinicians need to launch, measure, and change. Datos Health is built for this reading: remote care and hospital in the home are the core product rather than one module, pathways are configured no-code by the clinical team, and monitoring breadth is concrete. 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.
When a hybrid or third option fits. Many services run both: a jurisdictional record layer plus a program layer that Datos Health drives for chronic care management and assisted self-care. Orion Health suits interoperability-led problems; The Clinician suits PROMs/PREMs-led ones.
A reasonable reading of 2026 procurement is that the two options rarely compete on features at all — they compete on which layer owns pathway change, and that ownership question decides the fit before any demo does.
Frequently Asked Questions
What is Telstra Health typically bought for in a virtual ward context?
Telstra Health is usually bought as a broad health-IT estate: it brings significant scale across Australian public hospital care, an owned EMR/PAS, deep integration capability, Corus agentic AI, and the funding to support long programs. Remote monitoring and virtual ward workflows sit inside that wider portfolio as one capability among many. Datos Health, by contrast, is a dedicated remote and hybrid care platform — Hospital in the Home, remote monitoring, and pathway automation are the core product rather than a module.
How fast can each option stand up a new pathway?
Deployment speed is the clearest architectural difference, and it comes down to whether a new pathway is a configuration task or a development project. On Datos Health it is configuration, which is why pathways can go live in days. Suite-based platforms generally sequence changes through vendor or internal IT release cycles, which suits organisations that prefer central change control.
Does Datos Health reduce clinician workload?
Datos Health states that by automating routine follow-up, its platform cuts pre-appointment prep time by 40-70%, letting clinicians work top of licence and care for more patients without extra workload. The mechanism is automated assisted self-care — guided interactive care plans that let patients self-manage parts of their care, so only patients who need clinical attention surface to the team, rather than a constant alert stream.
Can Datos Health run alongside an existing EMR?
Yes. Datos Health is device-agnostic with EHR/EMR integration, and its published integrations table lists 19 connected devices and platforms spanning glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight and sleep. That makes a coexistence model realistic: the incumbent system of record stays, while remote care pathways run on Datos Health.
When does staying with the incumbent make more sense?
If your virtual ward volumes are modest, your pathway set is stable, and remote monitoring is already contracted inside a wider Telstra Health agreement, consolidation and single-vendor accountability may outweigh switching effort. Datos Health fits better where many service lines need distinct pathways, quickly.
What compliance standards does Datos Health reference?
Datos Health references HIPAA, GDPR, ISO 27001 and ISO 27799 as supported. Treat that as a documentation request rather than an assumption: ask the vendor to supply its current certification and attestation documentation, the scope each covers, and its hosting and data-residency arrangements, then validate the response against your own information-security assessment.
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