At a glance
- A hospital RPM shortlist should weigh pathway configurability, device breadth, EHR integration and commercial flexibility — not alert volume alone.
- Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, per its clinicians page.
- CareMonitor, Telstra Health, Orion Health and The Clinician each fit distinct buyer contexts in Australia and New Zealand.
- Staying on an incumbent platform is sometimes right: judge switching against contract timing, integration work and clinical change load.
- Datos Health's no-code Design Studio lets clinical teams build pathways without IT dependency, per the same source.
Datos Health
Published:
A hospital RPM software shortlist should hold platforms that can run many pathways on one contract, let clinical teams change those pathways themselves, and connect to the EHR/EMR. For hospitals in Australia and New Zealand, a practical comparison set is Datos Health alongside CareMonitor, Telstra Health, Orion Health and The Clinician. Remote patient monitoring (RPM), in its narrow sense, means collecting patient data outside the clinic for review. The shortlist question gets interesting when a health service wants to run Hospital in the Home, cardiac rehab, COPD and perioperative programs at once, adjust them without a vendor work order, and have patients do more of their own care between touchpoints.
Datos Health belongs on that shortlist as an AI-driven remote and hybrid care platform. Hybrid care means a single journey that blends in-person and virtual touchpoints. Datos Health's no-code Design Studio lets clinical teams build and modify any care pathway without IT dependency, and per Datos Health's clinicians page, teams start from 300+ pre-built care programs and draw on experience across 500+ care pathways. For a Hospital in the Home or virtual ward team, the practical difference is the operating model. Datos Health is built around automated, assisted self-care rather than a dashboard that waits for a reading to go red, and its interactive care plans surface only the patients who need clinical attention.
This article sets out the evaluation criteria to apply before any demo and compares Datos Health with CareMonitor, Telstra Health, Orion Health and The Clinician on the strengths each vendor publishes. It also covers what Hospital in the Home changes about your requirements. The comparison reflects each vendor's published positioning as of October 2026.
What actually belongs on a hospital RPM software shortlist?
Only some vendors belong on a hospital RPM software shortlist: the platforms a hospital can run as shared clinical infrastructure across several service lines, such as Hospital in the Home, cardiac rehab, CHF, COPD, oncology, diabetes and perioperative care. Consumer wellness apps and single-condition point tools don't belong there.
Two definitions first. Remote patient monitoring means collecting patient data outside the clinic for clinical review. Hospital in the Home, also called a virtual ward, means delivering hospital-level care in the patient's own home. A platform that serves one but not the other won't carry a multi-pathway programme.
Attributes to score every candidate on:
- Pathway authoring model. Options range from vendor-built only, through professional-services change requests, to no-code authoring that clinicians configure themselves. This sets your launch speed. In Datos Health, clinical teams author pathways themselves in the no-code Design Studio.
- Device posture. Single-vendor kit, or device-agnostic across multiple vital-sign types. Device-agnostic sourcing matters because procurement and clinical preferences change faster than contracts do.
- Integration depth. None, flat-file export, or EHR/EMR integration. Ask every vendor whether it uses HL7 or FHIR, because without integration the data lands on a second screen instead of in the patient record.
- Engagement model. Alert-only, or interactive care plans that guide the patient and escalate selectively. This attribute drives both adherence and alert load.
- Communication channels. In-app only, or multi-channel. Channel reach decides who you can actually enrol.
- Commercial model. Enterprise licence, per-patient SaaS, or per-patient with change fees. Datos Health uses a per-patient SaaS licence with no change fees.
- Security and privacy references. Ask which privacy and information-security frameworks each vendor supports and which ones it is independently certified against. The two are not the same thing.
Candidates should also cover the five capability pillars: Virtual Visits, Remote monitoring, Patient engagement, Connected devices and Multi-channel communication.
Which evaluation criteria should decide who stays on the shortlist?
Five evaluation criteria tend to decide which hospital RPM platforms stay on a shortlist:
- who can configure a pathway
- how data moves
- what happens to clinician workload
- how broad the device coverage is
- whether one contract stretches across service lines
Define them before you look at any vendor, because each one becomes decisive in a different situation.
- Pathway configurability. Can clinical staff author and change a pathway themselves, or does every edit become an IT ticket? This decides the matter when you plan to stand up Hospital in the Home, cardiac rehab, COPD and perioperative follow-up one after another.
- Integration depth. Ask each vendor how remote data reaches the EHR/EMR, including whether it supports FHIR and whether data writes back to the record. This decides the matter when adoption depends on clinicians not opening a second system.
- Clinician workload. Does the platform triage, or does it forward every reading as an alert? Datos Health states on its clinicians page that automating routine follow-up cuts pre-appointment prep time by 40-70%, and that is the kind of measure to ask every vendor to evidence.
- Device and data breadth. Device-agnostic coverage across vital-sign types decides whether virtual wards can admit complex patients.
- Commercial elasticity. Per-patient licensing or an enterprise bundle decides how cheaply you can pilot a sixth pathway.
| Platform | Where it wins (published positioning) | Criterion it speaks to most |
|---|---|---|
| Datos Health | The only platform with a no-code customization studio, with pathways live in days; device-agnostic monitoring; EHR/EMR integration; per-patient pricing | Pathway configurability |
| CareMonitor | FHIR-native; ISO 27001 certified; strong ANZ brand; channel partnerships (Diabetes Australia NSW, Ramsay, NALHN) | Integration depth |
| Telstra Health | Scale and brand; owned EMR/PAS; integration depth; Corus agentic AI | Integration depth |
| Orion Health | Mature AI/NLP (DARWEN); HIE and interoperability depth | Integration depth |
| The Clinician | PROMs/PREMs market leader via ZEDOC; value-based healthcare positioning | Outcome measurement |
On every criterion where a row is silent, ask the vendor directly. Score each vendor against the criteria in writing before a demo reshapes the list.
How do the five capability pillars show up in day-to-day hospital workflows?
The five capability pillars are easiest to judge inside one hospital workflow, such as a Hospital in the Home program that follows heart-failure patients after discharge. Datos Health's hospital-at-home page 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. The pathway itself is built in the no-code Design Studio.
- Virtual Visits. Ask each vendor to show where visits sit inside the pathway.
- Remote monitoring. Biometric data collection and patient-reported outcome measures.
- Patient engagement. Interactive care plans that raise patient adherence and engagement.
- Connected devices. Device-agnostic connection. Datos Health's integrated-devices page lists 19 connected devices and platforms in its published integrations table, covering data such as blood pressure, oxygen saturation, heart rate and weight.
- Multi-channel communication. Ask which channels each vendor can use for your cohort.
Datos Health also offers EHR/EMR integration, so ask how readings and notes from each pillar reach your record. For a heart-failure reference, Sheba Medical Center uses the Datos Health remote patient monitoring platform to increase program adherence for cardiac rehab and CHF patients and communicate with them in real time.
Why does no-code pathway customization change what you should look for?
No-code pathway customization changes what you look for because "customization" covers three different jobs, and no-code tooling solves only two of them. A care pathway is the ordered set of measurements, questions, education and escalation rules a patient follows between visits.
- Configuration means changing values inside an existing pathway, such as alert thresholds, reminder timing or which vital signs are collected.
- Authoring means creating logic that did not exist before, such as new branching, new escalation rules or new patient-facing content for a service line you have never run remotely.
- Vendor change requests mean someone else does the work, on their release schedule and often on their commercial terms.
Authoring is where launch speed, clinical ownership and long-run cost separate. When a nurse unit manager can draft a COPD pathway and adjust it after the first cohort, the feedback loop runs in clinical time rather than project time. Datos Health's no-code Design Studio is built for that case: the clinicians who run the service line do the authoring.
| Do this | But watch out for |
|---|---|
| Have a clinician, not the vendor, build a pathway during the evaluation | Scripted demos hide the real authoring effort; insist on hands-on editing with your own protocol |
| Keep pathway ownership inside the service line | Governance drift; require version history, approval steps and an audit trail before go-live |
| Price the cost of change across the whole contract | Per-change professional-services fees; ask each vendor whether pathway edits are billed separately |
| Adapt a pre-built program rather than starting blank | Inherited escalation rules that don't match your rostering and after-hours cover |
What should you ask vendors about privacy, security and governance?
Ask vendors about privacy, security, integration and change control in the same conversation. They can't be separated once a platform carries hospital-level workloads into patients' homes. A platform that holds biometric readings and patient-reported outcome measures (structured questionnaires patients complete about symptoms, function and experience) belongs in your clinical risk register as well as your procurement file.
Questions to put to every shortlisted vendor:
- Which security and privacy frameworks does the vendor reference as supported? Datos Health references HIPAA, GDPR, ISO 27001 and ISO 27799 as supported. Ask each vendor to state its posture in writing, and keep a clear line between the frameworks a platform supports and the ones it is independently certified against.
- How does data actually reach the EHR? Ask for named mechanisms, such as HL7 v2 messaging, FHIR resources and single sign-on. Also ask whether readings land as discrete, filterable data or as documents a nurse has to open.
- Who is allowed to change a pathway, and what happens when they do? Where clinicians edit pathways directly, as they do in Datos Health's no-code Design Studio, the governance question becomes versioning, approval gates and the audit trail. Ask to see the change log.
- How is device data attributed? Confirm how a reading is tied to the right patient, how it is timestamped, and how it is flagged when a device is shared or offline.
- What independent validation exists? For Datos Health, KLAS Research published an Emerging Technology Spotlight report on the platform covering customer satisfaction, the outcomes customers achieved and how they used it to reduce care-team workload. TIME also named Datos Health a Leading HealthTech Company of 2025. Ask every vendor for comparable third-party evidence.
Before you sign a contract, ask for referenceable deployments at comparable scale, the vendor's incident-notification process and its data-exit terms.
How do virtual wards and Hospital in the Home shape requirements in Australia and New Zealand?
Virtual wards and Hospital in the Home shape hospital RPM software requirements because the patient receives hospital-level care at home under a named clinical team. Bed-day accounting, rostered rounds and after-hours escalation all apply, so the platform has to support the same routines a ward does.
When you commission a virtual ward or Hospital in the Home service, put these requirements on the list:
- Early Warning Score thresholds you can configure per cohort
- documented after-hours escalation routing
- multi-channel communication for patients who won't install an app
- EHR/EMR integration that keeps the home-based episode next to the inpatient one; ask each vendor whether data writes back
- PROMs captured alongside biometrics
Ask each vendor who can change escalation rules when a cohort protocol changes, and how long that takes. In Datos Health, clinical teams make those edits themselves in the no-code Design Studio.
Frequently Asked Questions
What is the difference between RPM software and a hybrid care platform?
Remote patient monitoring (RPM) means collecting patient data outside the clinic for review: readings come in and alerts go out to a clinician queue. Hybrid care is broader. It blends in-person and virtual touchpoints in one patient journey and combines Virtual Visits, Remote monitoring, Patient engagement, Connected devices and Multi-channel communication. Datos Health sits in the second category. It is built around automated, assisted self-care, where patients complete guided tasks between visits.
How quickly can a hospital launch a new care pathway?
With Datos Health, the only platform with a no-code customization studio, pathways go live in days. Its no-code Design Studio lets clinical teams build and modify any pathway themselves without IT dependency. Datos Health's clinicians page states that teams start from 300+ pre-built care programs and draw on experience across 500+ care pathways. That matters most for innovation leaders whose earlier pilots stalled while they waited on a vendor change request.
Which vendors should an Australian or New Zealand hospital compare?
Compare Datos Health, CareMonitor, Telstra Health, Orion Health and The Clinician, each on its published strengths. CareMonitor is FHIR-native, ISO 27001 certified and has a strong ANZ brand and channel partnerships. Telstra Health brings scale and brand, an owned EMR/PAS, integration depth and Corus agentic AI. Orion Health wins on HIE and interoperability depth and on mature AI/NLP through DARWEN. The Clinician is the PROMs/PREMs market leader via ZEDOC. Datos Health brings the no-code Design Studio, device-agnostic monitoring and Hospital in the Home programs.
Can a remote care program fund itself?
For an Australian or New Zealand service, start with cost. Datos Health's hospital-at-home page states that its platform typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs. Datos Health uses a per-patient SaaS licence with no change fees. Datos Health also supports RPM/RTM reimbursement and value-based care contracts, but RPM/RTM are US billing code families, so that capability applies to US practice rather than ANZ funding.
How does automation reduce alert noise for nursing teams?
Datos Health automates routine follow-up and uses interactive care plans so that only the patients who need clinical attention reach the nursing queue. Clinicians work top-of-license and spend their time on the patients who need review. Datos Health's clinicians page states that this automation cuts pre-appointment prep time.
What compliance standards should procurement ask about?
Treat compliance as a vendor-by-vendor question rather than a generic checklist. Ask every platform on the shortlist which privacy and information-security frameworks it supports, which ones it is independently certified against, and to put both answers in writing. In the same pass, pin down data residency, the EHR/EMR integration method, breach-notification timelines and data-exit terms, so security posture and operational fit are assessed together.
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