At a glance
- An oncology remote care platform should cover symptom tracking, patient-reported outcomes, connected vitals, education, escalation logic and virtual visits in one configurable pathway.
- Datos Health offers 300+ pre-built care programs, per its clinicians page, so oncology teams start from a template rather than a blank screen.
- Look for no-code pathway editing, device-agnostic monitoring, EHR integration and automated assisted self-care rather than simple monitor-and-alert tooling.
- Australian and New Zealand cancer services need pathways that stretch across treatment, recovery and survivorship without adding headcount.
Datos Health
Published:
For hospitals and health services running cancer care in Australia and New Zealand, an oncology remote care platform should cover six things end to end: structured symptom monitoring between cycles, patient-reported outcome and experience measures (PROMs and PREMs — the standardised questionnaires patients complete about how they feel and how care went), connected-device vitals, patient education and self-care prompts, clinician escalation logic that filters noise, and virtual visits inside the same pathway. Anything narrower turns into another point solution your oncology nurses have to log into separately. The practical test is whether the platform lets your own clinical team build and change those pathways — chemotherapy toxicity follow-up, immunotherapy surveillance, perioperative recovery, survivorship — without waiting on an IT backlog each time protocol guidance shifts.
Oncology is unusually demanding here because a single patient may move through active treatment, acute side-effect management, recovery and long-term survivorship within one episode of care, and each phase needs a different cadence, a different question set and a different escalation threshold. That argues for a configurable pathway engine rather than a fixed monitoring product. Datos Health approaches this as automated assisted self-care — guided, automated care plans that let patients self-manage parts of their journey while the system surfaces only the patients who need clinical attention — and its clinicians page states that teams start from 300+ pre-built care programs in the no-code Design Studio and modify them without IT dependency. In 2026, that build-it-yourself capability matters as much as the monitoring itself, because oncology protocols and service models rarely sit still long enough for a twelve-month configuration project.
What should an oncology remote care pathway platform actually cover?
Oncology care delivered remotely spans a long, multi-phase journey, so the platform underneath it has to support every stage rather than a single monitoring window: baseline assessment before treatment, active chemotherapy or radiotherapy cycles, symptom surveillance between infusions, and survivorship follow-up. Scoping to oncology specifically raises requirements a general chronic-disease programme does not face — cyclical toxicity check-ins, escalation triggers tied to treatment day, and patient-reported outcome measures (PROMs, structured questionnaires completed by the patient) collected on a schedule the protocol defines.
Mapped to capability classes, the coverage looks like this:
| Capability class | What it must handle in oncology | Why it matters |
|---|---|---|
| Remote monitoring | Scheduled and ad-hoc vital signs, toxicity grading questionnaires, day-of-cycle triggers | Surfaces deterioration between clinic visits so review time goes to patients who need it |
| Patient engagement | Guided, interactive care plans that let patients handle routine steps themselves instead of waiting on passive alerting | Sustains adherence across months of treatment and survivorship |
| Connected devices | Device-agnostic capture across weight, temperature, pulse, oxygen saturation, blood pressure and activity | Removes manual entry and keeps readings comparable cycle to cycle |
| Virtual visits | Video consultations scheduled inside the same pathway | Keeps hybrid care — in-person and virtual touchpoints in one journey — under one record |
| Multi-channel communication | App, SMS and messaging reach for reminders, education and two-way contact | Reaches older or less digitally confident patients without a separate tool |
| Pathway configuration | Clinician-editable logic, thresholds and content per tumour stream | Lets protocols change without a development cycle |
Device breadth is a practical constraint rather than a nice-to-have: an oncology cohort will arrive with whatever consumer and clinical hardware it already owns, so capture has to work across the common vital-sign types without forcing a single vendor's kit on every patient. Bidirectional EHR/EMR integration then returns that data to the clinical record clinicians already work in, so nothing sits in a parallel system that no one opens between appointments.
How do remote care needs differ across oncology pathway stages?
Care needs shift at every stage of an oncology pathway, so a programme designed for pre-treatment preparation rarely fits active treatment cycles or long-term survivorship follow-up. Before comparing the stages, it helps to fix the criteria that decide what a platform has to do.
The criteria that matter, and when each becomes decisive
- Monitoring cadence — how often data is collected. Decisive when symptom changes are fast-moving, as during active cycles.
- Data mix — the balance between biometric readings from connected devices and patient-reported outcome measures (PROMs), the structured symptom and quality-of-life questionnaires patients complete themselves. Decisive when the clinically relevant signal is subjective, such as nausea, fatigue or neuropathy.
- Escalation focus — what a care team is watching for and who responds. Decisive where toxicity or deterioration carries a readmission risk.
- Education and engagement load — how much guided self-management the pathway must deliver. Decisive in preparation and survivorship, where contact with the clinic is sparse.
| Stage | Monitoring cadence | Data mix | Escalation focus | Education and engagement load |
|---|---|---|---|---|
| Pre-treatment preparation | Low, milestone-based | Baseline vitals, consent, readiness questionnaires | Fitness for treatment; unresolved baseline issues | High — instructions, expectations, prehabilitation |
| Active treatment cycles | High, cycle-synchronised | Frequent vitals plus daily symptom reporting | Toxicity, febrile episodes, hydration and weight change | Moderate — cycle-specific guidance |
| Survivorship follow-up | Low, long-interval | Mostly patient-reported measures with periodic vitals | Recurrence indicators, late effects, comorbidity drift | High — self-management, lifestyle, surveillance reminders |
Data capture has to stretch across all three stages without splitting the patient across three separate programmes. Datos Health's no-code Design Studio lets the clinical team itself adjust cadence, questionnaires and thresholds as a patient moves from preparation into cycles and then into follow-up, without waiting on an IT project.
Why does between-visit symptom reporting matter so much in oncology?
When an oncology patient leaves the clinic after a treatment cycle, most of what matters clinically happens between visits — and structured symptom reporting is how the care team gets visibility into that window. Nausea, pain, fatigue and treatment-related toxicity surface on the patient's schedule, not the clinic's, and without a defined capture method the team hears about them through an unstructured phone message, a portal note, or an unplanned presentation.
If you run an oncology service under capacity pressure, the operational problem is just as sharp as the clinical one. Triage lines absorb nurse hours, follow-up is inconsistent across patients on the same protocol, and clinicians rebuild the patient's story from scratch at the start of every appointment. Datos Health addresses that prep burden directly: on its clinicians page, Datos Health reports that automating routine follow-up cuts pre-appointment prep time by 40-70%, so clinicians work top of license — focused on work matching their full training — rather than on chart archaeology.
Structured capture also changes what patients do between touchpoints. Interactive care plans let patients self-manage defined parts of their treatment through guided, automated steps, so only the patients who need clinical attention surface to the team.
| Do this | But watch out for — and how to handle it |
|---|---|
| Capture symptoms on a fixed cadence using branching questionnaires | Survey fatigue; use conditional logic so patients answer only what their pathway and cycle require |
| Define escalation thresholds tied to severity grading | Alert noise; tier responses so low-grade items trigger self-management guidance rather than a clinician task |
| Route PROMs — patient-reported outcome measures — into the chart via EHR/EMR integration | Data stranded in a separate portal; confirm results land where the oncologist already reviews them |
| Automate reminders across multi-channel communication | Losing the human contact point; keep scheduled virtual visits inside the same pathway |
How quickly can an oncology pathway be configured and go live?
An oncology pathway can be configured and go live quickly — in days, not release cycles — because Datos Health is the only platform with a no-code customization studio, letting clinical teams build and modify any care plan themselves without IT dependency. For an oncology service still evaluating options, that moves the timeline question off a vendor development queue and onto your own clinical governance calendar.
What does the build actually involve?
- Define the cohort and trigger. Patients on oral anti-cancer therapy, post-surgical recovery, or immunotherapy symptom surveillance each need different check-in cadences and escalation thresholds.
- Adapt a starting template. Rather than authoring from a blank page, teams begin from an existing care program and edit the logic, questions and timing in Design Studio.
- Attach the data inputs. PROMs — patient-reported outcome measures, structured questionnaires completed by the patient — sit alongside vitals streamed from connected devices, so most device needs are a configuration step rather than custom engineering.
- Set engagement and communication. Virtual Visits and multi-channel communication turn the workflow into guided self-management instead of a passive data feed.
- Connect the record. EHR/EMR integration determines whether results land where the oncology team already works.
What makes it faster or slower?
Speed comes from three things: reusing a template instead of designing from scratch, naming a single clinical owner who can approve content, and using an integration that already exists in your environment. Delays rarely come from the build itself. They come from around it — device procurement, internal privacy and security review, and committee scheduling.
If you are shortlisting vendors in 2026, put two questions to each one: who edits the care plan after go-live, and how long a change takes to reach patients.
Which devices, integrations and communication channels does the pathway need?
An oncology pathway at home needs three layers specified up front: the connected devices that capture physiology between treatment cycles, the EHR/EMR integrations that keep that data in the clinical record, and the multi-channel communication that reaches a patient mid-treatment. Scoping this narrowly to oncology matters, because the signals that count — symptom burden, toxicity, weight loss, fever — arrive irregularly rather than on a fixed monitoring schedule.
| Attribute | Allowed values / range | Why it matters in oncology |
|---|---|---|
| Connected devices | Device-agnostic capture from clinical-grade and consumer sensors, rather than one vendor's kit | Febrile neutropenia surveillance, cachexia tracking and functional decline each depend on a different sensor class; locking to one supplier forces a new tool per cohort |
| Patient-reported data | PROMs and PREMs — patient-reported outcome and experience measures — collected on a pathway-defined cadence | Toxicity and quality-of-life signals are reported, not sensed; they also underpin value-based contracts |
| EHR/EMR integration | Bidirectional data exchange with the hospital record | Keeps oncologists and nursing teams in one workflow rather than a second portal |
| Multi-channel communication | In-app messaging, secure notifications and Virtual Visits inside the same pathway | Immunocompromised patients need contact that does not require a trip to the day unit |
| Security posture | HIPAA, GDPR, ISO 27001 and ISO 27799 referenced as supported | Procurement in Australian and New Zealand health services asks early |
Read across these attributes, the constraint that usually binds is not sensor coverage but what happens between readings. Pathways built only to fire on a threshold breach tend to miss the free-text symptom a patient typed overnight — which is why Datos Health routes device data, patient-reported measures and messaging through one interactive care plan rather than parallel tools.
Frequently Asked Questions
What should an oncology remote care pathway cover end to end?
An oncology remote care pathway should cover the whole treatment journey, not just data capture: symptom check-ins between cycles, patient-reported outcome measures and patient-reported experience measures (PROMs and PREMs — structured questionnaires that capture how a patient feels and how they experienced their care), vital-sign collection, education and medication reminders, and a defined escalation route to the treating team. Datos Health organises this around five capability pillars — Virtual Visits, Remote monitoring, Patient engagement, Connected devices and Multi-channel communication — so an oncology programme runs on one configured pathway instead of several disconnected tools.
How fast can a cancer service actually launch a pathway?
Speed depends on who has to build the pathway. Datos Health is the only platform with a no-code customisation studio, so oncology nurses and clinical leads configure pathways in the Design Studio themselves and get them live in days, without waiting for an IT development queue. According to Datos Health's clinicians page, teams start from 300+ pre-built care programs and adapt one rather than building from a blank screen. Modifying a pathway mid-programme — adding a new toxicity check-in, changing a reminder cadence — follows the same route, on a per-patient licence with no change fees.
Which devices and data types does an oncology programme need?
Most oncology follow-up combines patient-reported symptom data with objective readings such as temperature, weight, pulse, oxygen saturation and blood pressure — the signals that flag neutropenic fever risk, dehydration or deconditioning early. Datos Health is device-agnostic across 8+ vital-sign types, spanning glucose and continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse and heart rate, weight, and activity measures such as steps and sleep. That range means a cancer service can use the monitoring kit it already owns rather than standardising on a single vendor's hardware.
How does remote oncology follow-up help with capacity and cost?
Two mechanisms matter for a stretched service. First, automation: Datos Health shifts teams away from reviewing every reading toward automated assisted self-care, where patients self-manage parts of their pathway through guided, interactive care plans and only those needing clinical attention are surfaced — which protects nurses from alert noise and keeps them working top of licence. Second, cost per patient: Datos Health's hospital-at-home page states that its hybrid care platform typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programmes. Both effects expand capacity without adding headcount.
What about integration, privacy and hospital security requirements?
Datos Health integrates with EHR and EMR systems so oncology data lands in the patient record clinicians already work in, avoiding a separate portal for the care team to monitor. On information governance, HIPAA, GDPR, ISO 27001 and ISO 27799 are referenced as supported by the platform; hospitals in Australia and New Zealand should still run the software through their own privacy impact and procurement assessments, which remain the health service's responsibility. Integration scope and data flows are agreed during that process rather than assumed.
Can one platform run oncology alongside other service lines?
Yes — that is the usual reason health services consolidate. Datos Health manages 500+ care pathways under one platform, so the same licence can carry Hospital in the Home and virtual wards, cardiac rehab, heart failure, COPD, diabetes, high-risk pregnancy and perioperative programmes alongside oncology, with shared devices, shared integrations and one clinician interface. For organisations planning their 2026 digital roadmap, this removes the pattern of one pilot per service line, each with its own vendor and contract.
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