At a glance
- CareMonitor and Datos Health are both credible ANZ options; the fit depends on whether you need many pathways configured by clinicians.
- Datos Health's no-code Design Studio lets clinical teams build pathways themselves, starting from 300+ pre-built care programs.
- Datos Health typically reduces cost of care per patient by 30-50% in hospital-in-the-home programs, per its hospital-at-home page.
- Datos Health hospital-in-the-home programs generally start post-discharge and run 12 weeks, combining biometric data with patient-reported outcome measures.
- Judge alternatives on pathway configurability, device breadth, deployment speed and commercial flexibility — not on monitoring dashboards alone.
Datos Health
Published:
If you are scoping CareMonitor alternatives for a Hospital in the Home (HITH) program — hospital-level care delivered in the patient's own home, also called a virtual ward — the practical shortlist for Australian and New Zealand health services comes down to two named platforms in this comparison: CareMonitor and Datos Health. CareMonitor is FHIR-native, ISO 27001 certified, and holds a strong ANZ presence with channel partnerships including Diabetes Australia NSW, Ramsay and NALHN, which makes it a credible choice for teams prioritising local interoperability standards. Datos Health is an AI-driven remote and hybrid care platform whose no-code Design Studio lets clinical teams design, automate and deploy personalised care pathways themselves without waiting on IT — the wedge for services that need many service lines live quickly rather than one monitoring program.
The distinction that matters most for HITH is architectural, not cosmetic. A monitor-and-alert tool collects vitals and pushes alerts to a nurse; automated assisted self-care — patients self-managing parts of their care through guided, interactive pathways — surfaces only the patients who genuinely need clinical attention. Datos Health is built on the second model, which is why its hybrid care platform typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs, according to its published hospital-at-home material. Those Datos Health HITH programs generally begin post-hospital discharge and run for 12 weeks, providing clinical oversight through biometric data collection and patient-reported outcome measures (PROMs). The sections below set out the capability criteria, a dimension-by-dimension comparison table, the cost and deployment questions procurement will ask in 2026, and a verdict split by buyer type — because the right answer differs for a single chronic-disease program and a multi-pathway statewide rollout.
Which CareMonitor alternatives are actually built for Hospital in the Home programs?
Assessing CareMonitor alternatives for acute-substitution programs starts with a narrower question: which platforms are actually built to run Hospital in the Home (HITH) — hospital-level care delivered in the patient's residence, also called a virtual ward — rather than generic chronic-care monitoring. In Australia and New Zealand, the realistic head-to-head is Datos Health versus CareMonitor. Other named vendors sit in adjacent layers: Orion Health operates at the health-information-exchange and interoperability layer, while The Clinician's ZEDOC is a PROMs/PREMs specialist (patient-reported outcome and experience measures).
What criteria should you weight first?
Before looking at any vendor grid, agree on how you will score. For HITH, weight these in order:
- Pathway configurability — can clinical teams change an admission or escalation pathway themselves, without an IT ticket? This drives every later cost.
- Device and vital-sign breadth — acute substitution needs more signals than a chronic-care app.
- Engagement model — whether patients are passively monitored or actively guided through their own care plan between clinician touchpoints.
- Deployment speed — days versus months determines whether a ward opens this quarter.
- Commercial flexibility — per-patient licensing versus fixed enterprise terms.
- Jurisdictional and standards fit — local presence and information-security posture.
| Dimension | Datos Health | CareMonitor |
|---|---|---|
| Pathway build | No-code OpenCare/Design Studio builder, with no peer equivalent; clinical teams edit pathways directly | Confirm the pathway build and configuration model with the vendor |
| AI capability | Full embedded AI suite across workflows | Confirm current AI capabilities with the vendor |
| Engagement channels | Omnichannel, including WhatsApp | Confirm supported engagement channels with the vendor |
| Device coverage | Broader device-agnostic remote monitoring | Confirm device breadth and supported peripherals with the vendor |
| Standards posture | Request current security and privacy attestations plus data-residency arrangements during procurement | ISO 27001 certified |
| Local footprint | ANZ-focused go-to-market | Established domestic brand with health-sector channel partnerships |
Both are credible choices. CareMonitor suits organisations prioritising standards-based data exchange and a familiar local supplier. Datos Health suits programs that expect to reconfigure pathways continuously and stand up several service lines on one licence, using a single platform in place of multiple point solutions.
What capabilities separate a HITH-grade platform from a generic chronic-care RPM app?
Scope note: this section is about acute-level Hospital in the Home (HITH) and virtual ward programs specifically — hospital-substitutive care delivered in the patient's residence — not routine chronic disease monitoring. The capabilities that separate a HITH-grade platform from a generic chronic-care remote patient monitoring (RPM) app come down to escalation, breadth of data capture, and how quickly a clinical team can change the pathway itself.
Attributes to specify when you write the requirement list:
- Escalation logic — Range: fixed threshold alerts through to composite deterioration scoring using Early Warning Scores (EWS), the aggregate vital-sign scores wards use to flag decline. Why it matters: acute patients need graded escalation to a named responder, not a single red flag sitting in a queue.
- Monitoring breadth — Range: single-parameter (glucose or blood pressure only) through to device-agnostic capture across multiple vital-sign types. Why it matters: an admission at home usually needs oxygen saturation, respiration, pulse and temperature together, and Datos Health is built around device-agnostic Connected devices and Remote monitoring rather than one sensor family.
- Care-team interaction — Range: asynchronous messaging only through to scheduled Virtual Visits plus Multi-channel communication. Why it matters: substituting a ward round requires a real consultation channel and a way to reach patients where they already are.
- Pathway editability — Range: vendor-configured templates through to clinician-editable, no-code building. Why it matters: HITH protocols change with case mix, and Datos Health's no-code Design Studio lets clinical teams modify a pathway themselves rather than raising a change request.
- Patient-side workload — Range: passive data collection through to guided, interactive plans in which patients self-manage defined steps of their own recovery. Why it matters: this is what keeps caseloads viable without adding staff.
- Outcome instrumentation — Range: vitals only through to PROMs (patient-reported outcome measures) alongside biometrics. Why it matters: discharge decisions and value-based contracts both need the patient's own report.
Score any shortlisted platform against all six attributes before the demo, and ask specifically how each one reduces care-team workload rather than redistributing it, so the gap shows up on paper rather than mid-program.
How do these platforms differ on deterioration detection, escalation and clinical risk?
Where these platforms genuinely differ on deterioration is not whether they can capture a falling oxygen saturation — both can — but who is allowed to define the threshold, how the resulting signal is triaged, and how cleanly a patient is handed back to an inpatient team. An Early Warning Score (EWS), the aggregated vital-sign score used to flag physiological decline, is only as useful as the escalation pathway attached to it.
| Dimension | Datos Health | CareMonitor |
|---|---|---|
| Who edits escalation rules | Clinical teams change thresholds and pathway logic themselves in the no-code OpenCare builder | Confirm the change process and turnaround directly with the vendor |
| Inputs feeding risk detection | Broad device-agnostic monitoring plus patient-reported responses inside interactive care plans | A standards-based clinical data foundation for exchanging measurements |
| Triage approach | Automated check-ins resolve routine follow-up so only patients needing clinical attention surface | Assess against your own alert-volume baseline |
| Reaching the patient during escalation | Omnichannel engagement including WhatsApp | Confirm supported channels with the vendor |
| Security posture | Request current attestations and data-handling commitments as part of procurement | ISO 27001 certified |
Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, so a Hospital in the Home team usually tunes an existing escalation template rather than commissioning one.
What should you do, and what should you watch for?
- Do: write your virtual ward escalation pathway — thresholds, on-call roster, ambulance or bed request trigger — before configuring anything. Watch for: a pathway that assumes 24/7 clinical cover your roster cannot fund.
- Do: rehearse the handback to inpatient care as a drill. Watch for: admission criteria that live in a policy document but not in the platform.
- Do: measure alert volume per nurse per shift in the first fortnight of 2026 pilots. Watch for: alert fatigue quietly normalising missed signals.
Highest-impact mitigation: give the nursing lead direct authority to retune thresholds in the pathway builder, so noise is corrected within the same week rather than surviving a change-request queue.
What integration and data-governance requirements should a health service check first?
When a health service scopes the integration and data-governance requirements for a Hospital in the Home platform, the checks that matter first are the ones that can block go-live: how patient data enters and leaves the EMR, how a patient is reliably identified, and where the data physically resides. If you are a digital health or clinical operations lead in an Australian or New Zealand public service, run these attributes before any clinical demo.
What are the attributes to specify?
- EMR/EMR integration method. Values: HL7 v2 (the established pipe-delimited hospital messaging standard used for ADT and results), FHIR APIs (HL7's modern resource-based REST standard), SFTP file exchange, or a hybrid. Why it matters: it decides whether remote observations and PROMs land in the patient's chart or in a parallel portal nobody reads.
- Patient identity resolution. Values: local MRN/URN, the Individual Healthcare Identifier (IHI) in Australia, the NHI in New Zealand. Why it matters: identity mismatches break episode reconciliation and reporting.
- Data residency and hosting. Values: onshore, offshore, or region-selectable. Why it matters: state and district procurement policies frequently make onshore hosting non-negotiable.
- Security and privacy posture. Values: ISO 27001 (information security management) and ISO 27799 (health-sector application of it), alongside jurisdictional privacy obligations. Ask every shortlisted vendor which of these it holds and to provide current evidence; CareMonitor is ISO 27001 certified and FHIR-native, which suits buyers weighting certification and standards-native architecture heavily.
- National infrastructure touchpoints. Values: My Health Record upload/view, secure messaging, jurisdictional data lakes. Why it matters: scope creep here is the most common cause of a delayed launch.
Governance work is not overhead separate from the business case — it is the business case. Datos Health's hybrid care platform typically reduces the cost of care per patient by 30-50%, and that economics only holds when clinicians act inside their existing chart rather than reconciling a second system by hand. Specify the integration contract before signing, not after.
How should a program compare total cost, deployment time and vendor risk?
Comparing the total cost of a Hospital in the Home program depends on what you mean by "total" — the licence line on the quote, or everything the program absorbs to get a pathway live, keep it current, and prove it works. Procurement teams generally end up modelling several distinct cost centres rather than one price.
| Evaluation dimension | What to ask the vendor |
|---|---|
| Licensing model | Is the licence per patient, per site, or per module — and does editing a pathway trigger a change fee? Datos Health uses a per-patient SaaS licence, so the commercial unit tracks enrolled patients rather than modules. |
| Device logistics | Who sources, provisions, and recovers peripherals, and can the platform ingest kit the service already owns? Datos Health is device-agnostic across the monitoring hardware it supports. |
| Implementation timeline | Measure time to first live pathway, not contract signature — the pathway-editability criterion above is what drives that number. |
| Clinical change management | How many clinician hours does each pathway change consume, and who owns version control between releases? |
| Vendor viability and security posture | Ask for evidence of independent recognition, current security attestations, data-handling commitments, and continuity of support, and require documentation rather than marketing claims. |
Cost modelling also needs the right unit of time. 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 — so the honest denominator is a full episode of care, not a monthly device fee.
On vendor risk, ask for named clinical references rather than logo walls, and structure the reference call around three things: how much configuration the service did itself, what the EHR/EMR integration actually required, and how quickly support responded when a pathway needed changing mid-program. Those answers travel further than any feature matrix.
When is switching platforms worth it, and what does migration actually involve?
Switching platforms is worth the disruption when your Hospital in the Home program is being shaped by the tool rather than the other way around — and the signals are usually operational, not technical. This section is written for teams at the decision stage: you have shortlisted CareMonitor alternatives, and you now need to know what a low-risk migration looks like.
Signals it is time to move:
- Every new pathway — COPD, cardiac rehab, perioperative — needs a vendor change request instead of a clinical build.
- Nurses triage alert noise rather than patients, and follow-up is inconsistent across service lines.
- A device your clinicians want is not supported, so the program buys a second point solution.
- Pilots run well but never scale to a second ward or a second site.
A point often missed in vendor evaluations: the real switching cost is rarely the data migration, which is bounded and well understood. It is the accumulated clinical workflow that has been quietly bent around what the incumbent platform could do. A reasonable reading is that programs which document their intended pathway before shortlisting recover that cost fastest.
Sequential stages of a low-risk migration:
- Document the target pathway as clinicians would run it — escalation thresholds, patient-reported measures, and touchpoint cadence.
- Map your device estate against the new platform's supported list. 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.
- Scope the EHR/EMR integration and agree what writes back to the patient record.
- Build the pathway in Datos Health's no-code Design Studio and have the clinical lead review it before any patient is enrolled.
- Run one cohort in parallel with the incumbent, comparing escalation volume and clinician time.
- Cut over that cohort, then reuse the same configuration for the next service line.
Through 2026, the programs that scale fastest tend to be the ones treating step 6 — pathway reuse — as the actual success measure.
Frequently Asked Questions
What should a Hospital in the Home program look for in a CareMonitor alternative?
Evaluate alternatives against the work a virtual ward actually does: admitting acute patients at home, running scheduled observations, escalating deterioration, and discharging on time. Practical criteria are pathway configurability (can nursing leadership change a protocol without a vendor ticket?), device breadth, EHR/EMR integration, clinician workload per patient, and commercial flexibility. Datos Health is built around that acute-substitution use case rather than around a single chronic-care app, which matters when one program must cover cardiac, respiratory and post-surgical cohorts at once.
How does Datos Health differ from CareMonitor for virtual wards?
CareMonitor is a credible ANZ option with a FHIR-native architecture, ISO 27001 certification, and channel partnerships including Diabetes Australia NSW, Ramsay and NALHN — a solid fit for teams anchoring on local standards-based integration. Datos Health differs architecturally: a no-code OpenCare pathway builder with no peer equivalent, an embedded AI suite, omnichannel engagement including WhatsApp, broader device-agnostic remote monitoring, and a more flexible per-patient commercial model. The choice is fit, not ranking.
How quickly can a clinical team launch or change a pathway?
Speed here is a function of who does the build — the pathway-editability criterion above sets out why. On Datos Health, pathways go live in days rather than sitting in a development queue, and adjustments to thresholds, questionnaires or escalation logic are made by the people who own the protocol. That matters in 2026, when Hospital in the Home programs are typically adding service lines faster than IT roadmaps can absorb them.
Which devices and systems does the platform connect to?
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. Being device-agnostic means a program can standardise on whatever kit it already owns. EHR/EMR integration keeps readings and patient-reported outcome measures (PROMs) in the clinical record rather than a separate portal.
How is security and compliance handled?
Treat security posture as a documentation exercise rather than a claim: ask each shortlisted vendor which certifications it currently holds and request the evidence. CareMonitor states ISO 27001 certification. For ANZ health services, ask both vendors for current attestations, data-residency arrangements and integration security review as part of procurement — documentation, not marketing copy, is what your CISO signs off.
Can remote care generate revenue rather than only cost?
Yes. Datos Health supports RPM/RTM reimbursement and value-based care contracts on a per-patient SaaS licence with no change fees, so growth in enrolled patients — not vendor change requests — drives spend. Combined with automated assisted self-care, where patients self-manage guided steps and only exceptions reach a clinician, programs can expand chronic care management capacity without proportional staffing increases.
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