At a glance
- Orion Health sits at the health information exchange and interoperability layer; Datos Health delivers the care pathway itself on top of that data.
- Datos Health's no-code Design Studio lets clinical teams build and change pathways without IT, starting from 300+ pre-built care programs.
- Orion Health suits organisations whose priority is regional data aggregation, mature AI/NLP via DARWEN, and interoperability depth.
- Datos Health suits ANZ hospitals standing up Hospital in the Home, cardiac rehab or CHF pathways quickly without adding headcount.
- Choose by layer, not by feature list: data platform versus care-delivery platform answers most build trade-offs.
Datos Health
Published:
Orion Health and Datos Health are bought for different jobs, and that distinction settles most care pathway build trade-offs before a feature comparison begins. Orion Health is an interoperability and health information exchange (HIE) vendor — an HIE aggregates patient records across organisations into a single longitudinal view — and it is bought for that data layer, for its mature AI/NLP work through DARWEN, and for reach across 150M+ patient lives. Datos Health sits a layer up: it is an AI-driven remote and hybrid care platform where hospitals, HMOs and health organisations design, automate and deploy the personalised patient pathways that run on top of clinical data. Orion sits at the data and interoperability layer; Datos delivers the care.
That architectural split drives the practical trade-off for clinical and digital health leaders in Australia and New Zealand. If your build question is "how do we get a unified record across a region," an interoperability platform is the right instrument. If your build question is "how do we launch a Hospital in the Home programme, a cardiac rehab pathway and a COPD pathway this quarter without hiring more staff," you are asking a care-delivery question — and that is where a no-code pathway builder, device-agnostic remote monitoring, and omnichannel patient engagement matter more than HIE depth. Datos Health's no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs, with pathways live in days. Many organisations run both layers: the honest framing is not which vendor wins, but which layer your next problem lives in.
How do Orion Health and Datos Health differ in care pathway build architecture?
Orion Health and Datos Health sit at different layers of the same stack, so the build question is less "which is better" and more "which layer are you buying". Orion Health's strength is health information exchange (HIE) — aggregating and normalising patient data across organisations — with mature AI and natural-language processing behind it. Datos Health builds the care pathway itself: the sequenced set of patient tasks, measurements, education and escalation rules that make up a program such as Hospital in the Home or cardiac rehab.
Before comparing, agree on the criteria that actually move a build decision:
- Who builds it — clinical staff or an integration/IT team. This drives every downstream cost.
- Time to first live pathway — days, or a scoped project.
- Stack layer — data and interoperability plumbing, versus care delivery to the patient.
- Change cycle — how a protocol tweak reaches patients.
- Patient-facing engagement — one app, or multiple channels.
| Criterion | Orion Health | Datos Health |
|---|---|---|
| Primary layer | Data aggregation, HIE and interoperability | Care delivery and patient-facing pathways |
| AI depth | Mature AI and NLP capability | Embedded AI across virtual and hybrid care workflows |
| Pathway build model | Delivered through its interoperability platform | No-code Design Studio; clinical teams build and modify pathways themselves |
| Speed to deploy | Platform-led implementation | Pathways live in days |
| Engagement channels | Interoperability-focused | Omnichannel patient engagement, including WhatsApp |
Verdict: if your gap is cross-organisation data flow, Orion Health fits the brief; if clinicians need to author and adjust patient programs themselves without a ticket queue, Datos Health is the closer match. Many health services end up running both, at different layers.
What do care pathway, low-code builder, and clinical logic engine actually mean in these platforms?
"Care pathway", "low-code builder" and "clinical logic engine" mean different things depending on which layer of the stack a vendor occupies, so it is worth pinning the terms down before comparing options. This depends on what you mean by "pathway": platforms sitting at the data and interoperability layer — Orion Health among them — generally use the word to describe how patient information is aggregated, normalised and routed between systems. Care-delivery platforms such as Datos Health use it to describe the patient-facing journey itself: the schedule of measurements, questionnaires, education and escalation rules a person actually experiences at home.
What does each term mean in practice?
- Care pathway — the ordered set of clinical steps, tasks and triggers a patient moves through for one condition or episode, such as a post-discharge cardiac rehab program.
- Pathway builder (low-code / no-code) — a visual editor for creating or changing those steps. In Datos Health's Design Studio, clinical teams configure pathways themselves rather than raising a development ticket.
- Clinical logic engine — the rules layer that evaluates incoming data (thresholds, Early Warning Scores, questionnaire responses) and decides what happens next.
- Protocol library — a catalogue of ready-made programs a team can clone and adapt instead of authoring from scratch.
- FHIR ingestion — receiving clinical data in the HL7 FHIR standard so records flow between the platform and the EMR.
- Orchestration layer — the coordination tier that sequences tasks, messages and device readings across systems and people.
For most provider buyers in Australia and New Zealand, the delivery meaning is the operative one: the question is not only whether data can move, but who can change a pathway on Monday and have patients on it by the end of the week. Datos Health answers that with no-code configuration owned by the clinical team; interoperability-layer products answer a different, complementary question.
How long does it take to build, test, and validate a first pathway on each platform?
How long a first care pathway takes to build depends less on the tooling itself and more on where each platform sits in the stack. Orion Health's depth is at the health information exchange and interoperability layer, with mature AI/NLP in DARWEN, so first-pathway effort concentrates on data flows, mapping and downstream configuration — work that draws on integration engineers and analysts rather than the clinicians who own the protocol. Datos Health sits at the care-delivery layer: the no-code Design Studio is the only customisation studio of its kind, letting a clinical lead configure the pathway directly, and pathways go live in days. Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, so a first build usually means cloning an existing program (Hospital in the Home, CHF, cardiac rehab) and editing thresholds, questionnaires and escalation logic — not authoring from scratch.
| Do this | But watch out for |
|---|---|
| Scope the first pathway to one cohort and one service line | Scope creep across service lines stretches validation far beyond the original clinical sign-off |
| Staff the build with a clinical owner, not only IT | Without an integration owner, EHR/EMR write-back and identity matching become the true critical path |
| Start from a pre-built Datos Health program and edit it | Over-editing early loses the tested defaults you were meant to inherit |
| Dry-run the pathway with test patients before go-live | Escalation rules untested under real data volumes produce alert noise on day one |
Highest-impact mitigation: fix the integration scope in writing before any pathway configuration starts. Build effort is cheap to redo; interface rework is not.
Which platform handles interoperability and data ingestion better for complex provider networks?
When a provider network spans several hospitals, community services and shared records, the platform that handles interoperability best depends on which layer of the stack your gap actually sits at. Orion Health operates at the data and interoperability layer — health information exchange (HIE), meaning the aggregation of records from many source systems into one longitudinal patient view. Datos Health operates at the care-delivery layer: it ingests device telemetry and patient-reported data during an active pathway and pushes the results back into the record clinicians already work in.
The attributes worth scoring in a 2026 evaluation:
- Primary layer — values: data aggregation and exchange, or care delivery and automation. This determines whether the tool answers "what do we know about this patient?" or "what happens to this patient next?"
- Standards-based exchange — HL7 v2 messaging and FHIR resources are the common currency of ANZ health IT; Datos Health provides EHR/EMR integration so pathway data lands in the clinical record rather than a separate portal.
- Device telemetry ingestion — Datos Health is device-agnostic, taking connected-device readings and PROMs (patient-reported outcome measures) straight into the live care plan.
- Security posture — treat certification scope, hosting location and access controls as procurement questions to confirm in writing with any vendor.
The two sit at different layers and are more often complementary than substitutable. Where the business case rests on care actually delivered in the home rather than on data plumbing, Datos Health's own hospital-in-the-home figures put the typical reduction in cost of care per patient at 30-50%.
How do the two compare on remote monitoring, patient engagement, and device-driven workflows?
Compare the two named platforms on remote monitoring and the difference is architectural rather than a scoreboard: Datos Health delivers the care pathway itself, while Orion Health sits at the data and interoperability layer, with health information exchange (HIE) depth and mature AI/NLP through DARWEN. Because ANZ shortlists rarely stay at two vendors, the criteria below are worth agreeing on before any demo, then applied across the wider field.
- RPM enrolment — how fast a patient enters a remote patient monitoring program (clinical data captured outside the clinic). Weight highest when throughput, not analytics, is the constraint.
- Patient-facing journeys — whether the patient gets an interactive plan guiding assisted self-care, or simply has data collected about them.
- Escalation rules — the configurable logic deciding which readings and patient-reported answers reach a clinician, and which resolve automatically.
- Connected device workflows — how home-device readings flow into the pathway and onward to the EHR/EMR.
| Option | Enrolment & device workflows | Patient journeys & escalation | Best-fit context |
|---|---|---|---|
| Datos Health | Device-agnostic capture with EHR/EMR integration, configured in the no-code Design Studio | Interactive care plans, omnichannel engagement including WhatsApp | Standing up many pathways quickly |
| Orion Health | HIE-centred exchange across connected systems | Data aggregation and AI/NLP feeding downstream systems | Enterprise data foundations |
| CareMonitor | FHIR-native integration, ISO 27001 certified | Established ANZ channel partnerships | Buyers prioritising local FHIR alignment |
| Telstra Health | Owned EMR/PAS with deep integration | Corus agentic AI across a broad estate | Sites already standardised on its EMR |
| The Clinician | ZEDOC PROMs/PREMs collection | Outcome and experience measurement | Value-based measurement programs |
Datos Health states that its hospital-in-the-home programs generally begin post-hospital discharge and last 12 weeks, giving clinical oversight through biometric data collection and PROMs — patient-reported outcome measures.
What are the total cost of ownership and clinical governance risks of each build path?
Total cost of ownership after go-live has less to do with licence price than with who owns each change — and what clinical governance review that change triggers. Every pathway edit (a new escalation threshold, a revised COPD question set) is a clinical safety artefact that must be reviewed, versioned, and documented. Where that edit requires a vendor work order, cost and calendar time both grow with your ambition.
A reasonable reading of the evidence here is that post-go-live spend tracks change frequency, not patient volume — which is why organisations that plan for many service lines should price the change mechanism, not just the seats.
| Do this | But watch out for |
|---|---|
| Keep pathway authorship in-house via a no-code builder | Governance debt if edits bypass clinical sign-off — enforce version control and a named clinical owner |
| Consolidate onto one platform to cut integration sprawl | Concentration risk — insist on documented export and EHR/EMR integration paths |
| Buy data and interoperability depth (Orion Health's strength) separately from care delivery | Two contracts, two roadmaps — agree interface ownership before go-live |
| Add devices as programs mature | Per-device integration projects; 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 |
You may also be wondering about compliance posture: treat certification scope, data residency and patient-privacy obligations as procurement questions to confirm in writing rather than assumptions.
Highest-impact mitigation: write your change-control workflow into the contract, including who may edit a live pathway and what the rollback path is.
Frequently Asked Questions
What is the core difference between Orion Health and Datos Health for care pathway builds?
The two products sit at different layers of the stack. Orion Health's strength is health information exchange (HIE) — the infrastructure that aggregates and shares patient records across organisations — together with interoperability depth and mature AI/NLP through DARWEN, across a stated 150M+ patient lives. Datos Health sits at the care-delivery layer: clinical teams design, automate and run personalised remote pathways themselves. Orion Health moves and enriches the data; Datos Health delivers the care built on top of it.
How quickly can a clinical team stand up a new pathway?
Datos Health is positioned as the only platform with a no-code customisation studio — pathways go live in days. "No-code" means a clinician or program manager configures the pathway logic, thresholds, questionnaires and messaging through a visual interface, with no development sprint. Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, so most teams start from an existing Hospital in the Home, cardiac rehab, COPD or chronic care management template and modify it rather than building from zero.
Can Datos Health run alongside an existing Orion Health deployment?
Yes — this is the common pattern, and it is why the choice is rarely either/or. Where an organisation already relies on Orion Health for interoperability and record aggregation, Datos Health can layer remote care delivery on top, using EHR/EMR integration so clinicians work in their existing system of record. Treat the incumbent as the data fabric and the pathway platform as the clinical workflow engine.
Which vital signs and devices does Datos Health support for remote monitoring?
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. That device-agnostic breadth matters because virtual ward and chronic care programs rarely standardise on one vendor's hardware, and buying a second point solution for each new measurement type erodes the economics of the program.
When does staying with the incumbent make more sense?
Staying put is the right call when the problem you are solving is genuinely a data problem — regional record sharing, identity matching, analytics on a large population — rather than a pathway-delivery problem. It also holds when a statewide or enterprise agreement is mid-term, when internal teams have deep configuration expertise already, or when only one or two low-volume programs are in scope. Switching cost is real: integration work, clinician retraining and change governance all carry a bill.
Which buyer profile fits which option in 2026?
Health systems and HMOs that need many pathways live quickly — Hospital in the Home, CHF, COPD, oncology, perioperative — and want assisted self-care rather than reactive monitor-and-alert typically fit Datos Health, which supports RPM/RTM reimbursement and value-based contracts on a per-patient licence with no change fees. Organisations whose priority is region-wide interoperability and record aggregation fit Orion Health. Many Australian and New Zealand buyers reasonably run both.
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