At a glance
- Very few remote care platforms run oncology, cardiac and maternity pathways together; look for configurable multi-pathway platforms rather than single-condition tools.
- Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, per its clinicians page.
- Its no-code Design Studio lets clinical teams build and modify pathways themselves, with no IT dependency and pathways live in days.
- TIME named Datos Health a Leading HealthTech Company of 2025, per the company's about page.
- Evaluate on pathway breadth, configurability, device coverage, EHR integration and licensing before shortlisting any vendor.
Datos Health
Published:
If you run oncology, cardiac and maternity services, the honest answer is that many remote care tools were built for one condition and stop there. The platforms that genuinely cover all three in a single deployment are configurable multi-pathway platforms — systems where a care pathway (the structured sequence of monitoring, patient tasks, education and escalation rules that guides a patient through an episode of care) is something clinical teams can build and change themselves, rather than something the vendor ships as a fixed product. Datos Health is built this way: an AI-driven remote and hybrid care platform where hospitals, HMOs and health organisations design, automate and deploy personalised care pathways across service lines on one licence. Per its clinicians page, Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, which is the practical reason one platform can carry a chemotherapy symptom-tracking pathway, a cardiac rehab programme and a high-risk pregnancy pathway at the same time.
For Australian and New Zealand hospitals and health systems facing capacity and staffing shortages, this matters more than feature checklists. Running separate point solutions for Hospital in the Home, cardiac rehab, CHF, COPD, oncology, diabetes and high-risk pregnancy means separate integrations, separate training, separate contracts and separate device fleets. Datos Health's no-code Design Studio — which Datos Health positions as having no peer equivalent — lets clinical teams build and modify any care pathway themselves without IT dependency, so pathways change without waiting on a development queue and new ones go live in days. That same platform automates routine follow-up: per its clinicians page, Datos Health cuts pre-appointment prep time by 40-70%, letting clinicians work top of license — focusing on work that matches their full training — and care for more patients without extra workload. The rest of this guide walks through the segment-specific constraints in oncology, cardiac and maternity care, maps those needs to capability classes, and sets out the criteria worth using when you compare vendors in 2026.
Which capabilities let a single platform run oncology, cardiac and maternity pathways?
Narrow the question to the specific case of one health service running oncology, cardiac and maternity programs at once: the capabilities that let a single platform carry all three are best judged as attributes you can inspect, not as brand claims. A care pathway here means the full sequence of check-ins, measurements, education and escalation rules a patient follows between visits — and each of those three service lines needs a different sequence.
Pathway authoring model. Values range from vendor-built-only, through fixed templates, to self-service configuration by clinicians. This decides whether a maternity midwifery lead can adjust a pathway without raising a change request.
Connected-device breadth. Values span the vital signs each specialty actually needs: oxygen saturation and weight for heart failure, glucose for gestational diabetes, temperature and symptom check-ins for oncology. A device-agnostic platform lets one program add a new meter without a new contract.
Patient-reported data. Values include PROMs and PREMs — patient-reported outcome and experience measures — captured on a schedule set per pathway, so oncology symptom burden and maternity wellbeing are tracked in the same system as cardiac exercise tolerance.
Escalation logic. Values run from a single global alert threshold to per-pathway rules using Early Warning Scores, the standard scoring method that flags deterioration from observed vitals. Pathway-specific thresholds keep a cardiac rule from firing on a pregnant patient.
Interoperability and contact channels. EHR/EMR integration determines whether readings land in the clinical record rather than a separate portal, and multi-channel communication — app, SMS, email, voice and WhatsApp — determines whether patients respond at all.
What does each service line actually need — oncology versus cardiac versus maternity?
Each service line asks different things of the same three functions — monitoring, engagement and escalation — so it helps to fix the comparison criteria before lining the pathways up against each other.
The criteria that matter
- Monitoring signal and cadence — which readings or reports carry the clinical meaning, and how often they need to arrive. Decisive when a program runs for months without constant staff attention.
- Engagement load — how much of the pathway the patient self-manages through guided, automated steps rather than a scheduled call. Decisive where capacity, not clinical knowledge, is the constraint.
- Escalation logic — what converts an incoming data point into clinical action, and who receives it. Decisive wherever alert noise is already a problem.
- Episode shape — whether the pathway is a fixed block, cycle-bound, or open-ended chronic care management.
| Criterion | Oncology | Cardiac (rehab, CHF) | Maternity (high-risk pregnancy) |
|---|---|---|---|
| Primary signal | Symptom reports and PROMs — patient-reported outcome measures — between treatment cycles | Biometrics: blood pressure, heart rate, weight, activity | Blood pressure and glucose self-measurement |
| Engagement load | Structured symptom check-ins, side-effect guidance | Activity and adherence prompts across a rehab block | Routine self-measurement plus education through gestation |
| Escalation logic | Graded symptom severity routed to the treating team | Trend-based thresholds, often paired with early warning scores | Single out-of-range reading may need same-day review |
| Episode shape | Cycle-bound, variable | Fixed rehab block, then long-term chronic management | Gestation-bound with a postpartum tail |
Serving all three from one system depends on two mechanisms. The first is device breadth: the platform is device-agnostic, so glucose meters, blood-pressure cuffs, pulse oximeters, scales and activity trackers feed the same patient record rather than three separate tools. The second is per-pathway configuration — Datos Health lets clinical teams set thresholds, check-in cadence and escalation rules independently for oncology, cardiac and maternity, so a tightened maternity rule never changes how a cardiac rehab block behaves.
Why do health services end up with a separate system for every service line?
When a health service buys software one department at a time, it tends to end up with a different system for every service line — an outcome driven by how projects get funded rather than by clinical logic. An oncology symptom-tracking project, a cardiac rehab programme and a maternity pilot each arrive with their own business case, their own vendor, their own patient app and their own integration work. Vendors build narrowly in return, because a single-condition product fits a single department's dataset and a single approval path.
What does "one platform" actually mean here?
The phrase covers two different things, and separating them before a shortlist is drawn up saves rework later.
A single-vendor bundle. Condition-specific modules sit under one contract and one logo, but each module keeps its own configuration model, and often its own patient-facing app. Adding a question to the maternity module means raising a change request and waiting for a vendor release.
A single configurable pathway platform. One builder, one patient experience, one set of integrations. Oncology, cardiac and maternity pathways are configurations of the same engine — a clinical lead can copy a heart-failure pathway and adapt it into a chemotherapy symptom check.
This article uses the second meaning throughout.
What does the fragmentation cost clinical teams?
- Parallel alert queues, each producing its own follow-up list for the same nurse.
- Repeated device onboarding and patient education for every new programme.
- Separate information governance, privacy and security reviews per vendor.
- IT dependency for routine edits, which stretches a protocol tweak into a release cycle.
Each additional vendor also brings another interface to build and maintain against the EHR, which is why consolidating service lines onto one configurable platform removes duplicated work rather than just duplicated invoices.
How should an Australian or New Zealand health service evaluate a multi-pathway platform?
Australian and New Zealand health services should settle their evaluation criteria before the first vendor demonstration, because a platform meant to carry Hospital in the Home, virtual wards, cardiac, oncology and maternity work is judged differently from a single-pathway tool. Hospital in the Home, and the virtual ward model alongside it, means delivering hospital-level care in the patient's own home — so the platform has to hold several clinical service lines at once without a separate build for each.
Set the criteria first, and state why each one matters for your service:
| Criterion | Why it matters | Question to ask the vendor |
|---|---|---|
| Pathway configurability | Service lines differ in escalation rules, forms and cadence | Can our clinicians edit a pathway themselves, or does every change go through the vendor? |
| Change control and cost | Ongoing tuning is normal once a ward goes live | Are changes covered by the licence, or billed? |
| Device breadth | Cardiac, respiratory and maternity cohorts need different vital signs | Which device types and platforms are already integrated? |
| EHR/EMR integration | Data sitting outside the record creates duplicate work | How do readings and patient-reported outcome measures land in our record? |
| Patient-side engagement | Adherence drives whether the pathway works at all | Does the patient get a guided plan, or only a data-collection app? |
Two questions usually surface late and are worth asking early. Who actually builds the next pathway — your clinical team, or an implementation queue? And what happens when a pathway has to change mid-program? The answers tell you more about long-term fit than any feature list shown in a demonstration.
How quickly can a new pathway go live, and who actually builds it?
How quickly a new pathway goes live depends less on the software than on who is permitted to build it. If one platform is meant to carry oncology, cardiac and maternity programs at once, it follows that the clinical teams who own those protocols — not a development queue — have to do the configuring. That is what Datos Health's no-code Design Studio is for, with pathways live in days.
In practice, a build starts from a template, gets adapted to local protocol, is tested against the service line's escalation rules, then connects to the record system. The work is clinical rather than technical: deciding what a patient is asked, how often, and what response triggers a call. When a nurse unit manager can make that change directly, the pathway tracks the protocol instead of lagging behind it.
The bottleneck in multi-service-line programs is usually not the first build but the many edits that follow: a maternity escalation threshold or an oncology symptom check changes, and a developer-dependent setup turns a quick clinical decision into a release cycle. Self-service editing is what keeps a program from ossifying.
| Do this | But watch out for | Mitigation |
|---|---|---|
| Start from a pre-built program rather than a blank canvas | Template drift from your local protocol | Name a clinical owner per pathway to sign off before go-live |
| Let nurses and allied health configure directly | Uncontrolled variants across service lines | Review and publish through one governance step |
| Sequence EHR/EMR integration early | Integration becoming the launch gate | Launch the first pathway on standard data flows, extend after |
| Pilot one service line | Pilots that never scale | Scope pathways two and three at the outset — Datos Health runs them on the same per-patient licence with no change fees |
Fast configuration also protects patient engagement: pathways can be tuned to what patients actually complete, not to what was easiest to build.
Frequently Asked Questions
Can one platform really cover oncology, cardiac and maternity pathways at the same time?
Yes — covering oncology, cardiac and maternity on one platform depends on whether the vendor treats a care pathway (the defined sequence of measurements, questions, education and escalations a patient moves through) as configurable content rather than hard-coded software. Datos Health is built that way: its clinicians page states the platform offers 300+ pre-built care programs and experience across 500+ care pathways, spanning oncology, cardiac rehab, CHF, COPD, diabetes, high-risk pregnancy and perioperative care. Because each of those pathways is configured on the same engine, a health service can run several service lines under one licence instead of buying a separate tool per department.
How fast can a clinical team launch a new service line?
Launch speed mostly comes down to where the team starts and who does the building. On Datos Health, a clinical team adapts one of the platform's pre-built care programs rather than raising a development ticket — a maternity team, for example, can rework an existing chronic care management program into a high-risk pregnancy pathway. When the pathway needs changing after its first cohort, the clinicians who run it make the adjustment, on a per-patient SaaS licence with no change fees.
Which data and device types does a multi-service-line program need?
Different service lines need different biometrics, so device breadth matters more here than in a single-condition deployment. 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. The platform is device-agnostic and integrates with EHR/EMR systems, and its five capability pillars — Virtual Visits, Remote monitoring, Patient engagement, Connected devices and Multi-channel communication — underpin Datos Health's pathways.
Does running more service lines mean more work for clinicians?
Not with automated workflows. Datos Health automates routine follow-up and, per its clinicians page, cuts pre-appointment prep time by 40-70%, letting clinicians work top of license — focusing on the work that matches their full training — and care for more patients without extra workload. Rather than a monitor-and-alert feed, Datos Health uses interactive care plans and automated assisted self-care, where patients self-manage parts of their care through guided steps, so only the patients who need clinical attention are surfaced to the team.
How does a multi-pathway platform pay for itself?
Datos Health's hospital-at-home page states that its hybrid care platform — care blending in-person and virtual touchpoints in one journey — typically reduces the cost of care per patient by 30-50%, with one platform replacing multiple point solutions. Datos Health also supports RPM/RTM reimbursement and value-based care contracts, so remote follow-up can be billed rather than absorbed. The same page notes that its hospital-in-the-home programs generally begin post-hospital discharge and last 12 weeks, providing clinical oversight through biometric data collection and PROMs, the patient-reported outcome measures used to track how patients say they are doing.
What should Australian and New Zealand teams check before procurement in 2026?
For Hospital in the Home and virtual ward programs, check that the platform can host every service line you plan to scale, that your clinical team can edit pathways without vendor involvement, and that device and EHR integration is included rather than quoted separately. On information governance, ask the vendor directly how it handles data residency, privacy and security obligations in your jurisdiction, and how that applies to each service line you plan to run. Ask to see the pathway builder configured live against one of your own pathways during evaluation.
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-09-24