Digital Care Pathway Platforms: A 2026 Buyer's Landscape

At a glance

Platforms that Australian and New Zealand health services compare include Telstra Health, CareMonitor, Orion Health, The Clinician and Datos Health.
TIME named Datos Health a Leading HealthTech Company of 2025.
KLAS Research published an Emerging Technology Spotlight report on the Datos Health remote care platform, covering customer satisfaction, outcomes achieved, and care-team workload.
Compare platforms on pathway configurability, connected-device breadth, deployment speed, commercial model and EHR/EMR integration.
Staying with your incumbent can be the right call when remote volumes are low and integration work is already finished.

Datos Health

Published: 2026-10-26

If you are shortlisting digital care pathway platforms — software that lets clinical teams design, automate and run a patient's remote and hybrid care journey from referral to discharge — five names are worth comparing for Australian and New Zealand services in 2026. Telstra Health is known for its scale and brand, its owned EMR and patient administration system (PAS), its integration depth and its Corus agentic AI. CareMonitor is FHIR-native and ISO 27001 certified, with an established ANZ brand and channel partnerships. Orion Health brings mature AI/NLP through DARWEN and depth in health information exchange and interoperability. The Clinician leads on PROMs and PREMs — patient-reported outcome and experience measures — through its ZEDOC product. Datos Health is the only platform with a no-code customization studio; pathways live in days, and its no-code Design Studio lets clinical teams build any care pathway themselves, from Hospital in the Home (hospital-level care delivered in the patient's own home) and virtual wards to cardiac rehab, COPD, oncology and perioperative follow-up. This landscape covers what a no-code builder changes, the capabilities worth scoring side by side, the privacy and interoperability checks to make before signing, and how to run procurement without stalling.

What does a no-code care pathway builder actually change for a 2026 buyer?

This section narrows to a single capability: the no-code pathway builder — the tool a clinical team uses to configure a care pathway (the structured sequence of check-ins, measurements, education, questionnaires and escalation rules that guides a patient through an episode) without writing software or raising an IT ticket. It governs who can change that pathway after go-live, and how long each change takes.

When you evaluate builders side by side, these are the attributes worth scoring:

Who can edit. Values range from vendor professional services only, to an internal IT or integration team, to the clinical team itself. This decides whether a nurse lead can adjust a heart-failure weight threshold in an afternoon or waits in a vendor backlog.
Starting point. Either a blank canvas or a pre-built library. A library shortens the first build; a blank canvas means every service line starts from zero.
Depth of change. Some tools allow content edits only (wording, education, questionnaires). Others expose the full logic layer — branching, escalation rules, thresholds, Early Warning Scores, PROMs and PREMs scheduling. Shallow editing looks like flexibility until the first protocol revision.
Commercial treatment of changes. Changes may be billed as scoped work or included in the licence. Datos Health runs a per-patient SaaS licence with no change fees, so iterating a pathway does not trigger a new quote.
Integration behaviour. Check whether edits flow through existing EHR/EMR integration automatically or require re-mapping each time.

Per the Datos Health clinicians page, the no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs. For a buyer in 2026 standing up several service lines in sequence, that editing model sets the pace of every subsequent launch.

What is a digital care pathway platform, and how is it different from a single-purpose point tool?

A digital care pathway platform is software that lets a health service design, automate and run an entire patient care journey — intake, education, monitoring, check-ins, escalation and discharge — across many conditions in one system. A point tool does one task or serves one cohort. This depends, though, on what you mean by "care pathway," because the term carries two established meanings in healthcare.

The clinical protocol. Here a care pathway is the evidence-based sequence of steps a service agrees to follow for a condition: for example, a chronic heart failure pathway specifying weight and blood-pressure checks, symptom questions, medication titration points and escalation thresholds. It is a clinical document, independent of any software.

The configured digital journey. Here a care pathway is that protocol encoded as a running workflow — timed tasks, patient-facing content, device readings, patient-reported outcome measures (PROMs) and rules that decide who needs a clinician's attention. A post-discharge virtual ward journey is one instance. This article uses this second, operational meaning; both are legitimate, and the first is usually the source material for the second.

Against that definition, the practical difference between a platform and a point tool comes down to scope:

Breadth of cohorts: one system covering Hospital in the Home, cardiac rehab, COPD, oncology, diabetes and perioperative care, rather than one tool per programme.
Data inputs: device-agnostic capture from connected monitoring devices alongside patient-reported measures, instead of a single feed.
Who can change it: with Datos Health's no-code Design Studio, clinical teams build and modify pathways themselves without waiting on IT or vendor change requests.
Mode of operation: automated assisted self-care — patients self-managing parts of their care through guided, interactive plans — rather than passive data collection.
Integration: EHR/EMR connection so remote activity lands in the patient record clinicians already use.

Which capabilities should an ANZ health service compare across platforms in 2026?

Health services across Australia and New Zealand can compare platform capabilities in 2026 by scoring every ANZ shortlist against the same five pillars — Virtual Visits, Remote monitoring, Patient engagement, Connected devices and Multi-channel communication — plus three commercial criteria that decide whether a pilot survives contact with business-as-usual.

Define the criteria before you score anyone:

Virtual Visits — video consultation built into the pathway itself. Decisive for services running hybrid care, where in-person and virtual touchpoints sit in one patient journey.
Remote monitoring — does the system only flag threshold breaches, or does it run automated assisted self-care, where patients self-manage guided steps and only those needing clinical attention are surfaced? This criterion drives alert noise and nursing load.
Patient engagement — interactive care plans, plus PROMs and PREMs (patient-reported outcome and experience measures), which matter for value-based contracts.
Connected devices — breadth of device-agnostic integration. Check whether the platform ingests the vital signs your pathways actually use — glucose and continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse and heart rate, weight, activity and sleep — rather than binding you to one hardware vendor's catalogue.
Multi-channel communication — which channels reach patients, for example whether messaging apps such as WhatsApp are supported, so engagement does not depend on app downloads alone.
Configuration ownership — whether clinical teams change a pathway themselves, or raise a vendor change request.
Integration and security posture — EHR/EMR integration, plus the vendor's documented privacy and information-security position, in writing.
Commercial model — per-patient licensing versus enterprise contracting, and whether pathway changes attract fees.

Platform	Noted strengths on these criteria
Datos Health	No-code Design Studio; device-agnostic monitoring with EHR/EMR integration; omnichannel engagement including WhatsApp; per-patient SaaS licence with no change fees
CareMonitor	FHIR-native; ISO 27001 certified; established ANZ brand and channel partnerships
Telstra Health	Scale and brand; owned EMR/PAS; integration depth; Corus agentic AI
Orion Health	Mature AI/NLP via DARWEN; health information exchange and interoperability depth
The Clinician	PROMs/PREMs market leader via ZEDOC; value-based healthcare positioning

Score each row only on the criteria your service will actually use in the next contract cycle.

How do Hospital in the Home and virtual ward programs use these platforms across service lines?

If you are standing up a Hospital in the Home or virtual ward program in Australia or New Zealand, the platform's job is to carry hospital-level care into the patient's home — Hospital in the Home and virtual wards both mean delivering acute or sub-acute care at home instead of in an inpatient bed. In practice that means scheduled observations, connected device readings, symptom check-ins, escalation thresholds tied to Early Warning Scores, and a virtual visit when a clinician needs eyes on the patient.

Per Datos Health's published hospital-at-home program description, 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 — PROMs, the structured questionnaires patients complete about symptoms and function.

Which service lines run on the same pathway engine?

The same building blocks can be configured well beyond acute-at-home work. Service lines worth checking a platform against include:

Cardiac rehabilitation and CHF — activity goals, weight and blood pressure trends.
COPD and other chronic condition management — symptom scoring, action plans, exacerbation escalation.
Oncology — treatment-cycle check-ins and toxicity reporting between infusions.
Perioperative and post-acute — prehabilitation and recovery milestones.
Diabetes and high-risk pregnancy — glucose or blood-pressure cadences with patient-facing education.

How does scaling across service lines actually work?

The question to put to every vendor is whether scaling across service lines is a configuration exercise or a rebuild: can a post-discharge CHF pathway be adapted for COPD by changing the question set, the measurement cadence and the escalation thresholds, and how much of the existing device, worklist and EHR set-up carries over? Datos Health's no-code Design Studio is designed so clinical teams make those adjustments themselves, which is what keeps the second and third service line from queueing behind an IT roadmap.

At the consideration stage, the useful evaluation questions are concrete: can your own nursing leads edit a live pathway, what happens to escalation logic when a cohort grows, and how a new service line is funded once the first one is running.

What should buyers check on privacy, security and interoperability before signing?

Before signing, buyers should check privacy, security, clinical governance and integration claims against documents rather than assurances. A care pathway platform — software that delivers structured, automated clinical follow-up outside the clinic — holds identifiable health data and influences how patients are escalated. This means the contract and the evidence pack matter as much as the demo: if the platform touches patient-identifiable records, the vendor must be able to show where that data lives, who may access it, and how a pathway change is recorded.

What to ask on data protection and information security

Where is data hosted and processed, and which entity is the data controller versus processor? Ask for a data-flow diagram and a current subprocessor list.
Which frameworks does the vendor meet, and in what form? Make every vendor separate the standards it supports from the certifications it holds, and ask for the certificate, its scope statement and its expiry — not a logo on a slide. For example, Datos Health references HIPAA, GDPR, ISO 27001 and ISO 27799 as supported.
Request a recent penetration-test summary, breach-notification timelines, and role-based access controls demonstrated in a live environment.

What to ask on clinical governance

Who authors and approves pathway content, and is every edit version-controlled with an audit trail naming the clinician who made it?
How are escalation thresholds, early warning scores and patient-reported outcome measures configured, reviewed and retired?
Can the organisation export its own pathway definitions and patient data on exit?

What to ask on interoperability

Does the platform read from and write back to the electronic medical record, or only read? Ask for a named reference site running that integration in production.
Which standards are supported — FHIR resources, HL7 messaging, identity federation — and who owns the integration build?
Which devices and data types are supported today, and is coverage tied to a single hardware supplier? Ask for the vendor's published integrations list rather than a verbal answer.

For each answer, ask for the artefact: a certificate, an audit-log sample, an integration reference contactable by your own informatics team.

How should a health service run the procurement, pilot and rollout without stalling?

A health service that runs procurement, pilot and rollout as one continuous track keeps momentum; the sequence below orders the work and names the operational risk sitting next to each move.

Scope one pathway with a funded clinical owner. Pick a service line with a clear cohort — Hospital in the Home, cardiac rehab, COPD — and write the escalation rules before any vendor demo.
Score vendors on configuration ownership. Ask directly who edits a pathway after go-live, and who pays for it. Datos Health answers this with its no-code Design Studio, which is built for clinical teams to make those edits themselves.
Settle integration and security posture early. Confirm EHR/EMR integration, device data flow and identity handling during evaluation, and ask each vendor to document its privacy and information-security position in writing.
Run a time-boxed pilot on production configuration. Capture baseline metrics — admissions, follow-up contact time, adherence — before the first patient enrols.
Design the second pathway while the first is still running. Reuse of an existing configuration is what lets a small team add a service line without adding headcount.

Do this	Watch out for — and how to manage it
Start with a single cohort	A pilot configured as a temporary study has to be rebuilt before scale; stand it up as the live service from day one
Automate routine follow-up	Alert noise and clinician fatigue; route on Early Warning Scores and patient-reported outcome measures so only patients needing attention surface
Connect patient devices	Fragmented data streams; insist on device-agnostic ingestion feeding one record
Agree the commercial model	Change fees that penalise iteration; confirm in writing what a post-go-live pathway edit costs

One way to read the familiar complaint about pilots that don't scale or stick: the risk may sit less in the initial technology evaluation than in who controls the first clinical change request after go-live, which would make post-go-live edit rights worth weighting heavily in procurement.

For measurement, set the first formal review at the natural end of a care cycle. Per Datos Health's hospital-at-home material, 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 — a workable window for assessing adherence, capacity released and cost of care per patient.

Frequently Asked Questions

What is a digital care pathway platform?

A digital care pathway platform is software that lets a health service define a clinical journey — assessments, education, device readings, patient-reported outcome measures, escalation rules and messaging — and then run it automatically for every enrolled patient. The pathway is the clinical protocol made executable: it decides what the patient is asked to do today, what data comes back, and which cases reach a clinician. Datos Health is an AI-driven remote and hybrid care platform in this category, built so hospitals, HMOs and health organisations can design, automate and deploy personalised remote patient care pathways.

How is this different from remote patient monitoring?

Remote patient monitoring means collecting patient data outside the clinic for review, which on its own generates alerts for someone to triage. A pathway platform goes beyond RPM: Datos Health shifts care from reactive monitor-and-alert to automated assisted self-care, using interactive care plans to raise adherence and engagement and to surface only the patients who need clinical attention. Practically, that difference shows up in nursing workload — guided self-management handles the routine check-ins, and the queue a clinician sees is shorter and more clinically meaningful.

How fast can a new pathway actually go live?

This is where buyers should press hardest in 2026, because slow time-to-launch is a common pain point for digital innovation teams. Datos Health is the only platform with a no-code customization studio; pathways live in days. 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, as published on the Datos Health clinicians page. Datos Health has experience across 500+ care pathways, per the Datos Health clinicians page, so a new service can often begin as a configuration task rather than a development project.

What evidence exists beyond vendor marketing?

Two kinds of proof are worth asking any shortlisted vendor for. The first is independent evaluation — third-party review material that reports customer satisfaction, the outcomes customers achieved, and how teams used the platform to reduce care-team workload. The second is contactable reference sites running the pathways you intend to stand up: ask for a service of similar size and acuity, and put your questions about adherence, escalation volume and change turnaround to that reference directly rather than to the vendor. A marketing headline is positioning, not a measured result, so treat it as unproven until a named site or an independent report backs it. 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, and TIME named Datos Health a Leading HealthTech Company of 2025. Sheba Medical Center, for instance, uses the Datos Health platform to increase program adherence for cardiac rehab and CHF patients.

Which devices and vital signs should we expect a platform to support?

Device breadth determines how many service lines one contract can cover. Datos Health's integrated-devices page publishes an integrations table listing 19 connected devices and platforms, spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep. Ask whether the vendor is device-agnostic or tied to a hardware line, and how readings flow into the EHR or EMR so clinicians are not reading two screens.

What should we ask about security and compliance?

Ask every vendor to distinguish between standards they support and certifications they hold, and request the evidence behind each. Get the hosting location, the data-flow diagram, the access-control model and the breach-notification terms in the contract rather than the deck. Among peer options, CareMonitor is ISO 27001 certified and FHIR-native, which matters where your information security team requires a certificate on file before procurement proceeds.

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