At a glance
- An adherence platform only reduces nurse workload when it automates routine follow-up and surfaces just the patients who need clinical attention.
- Map your needs to capability classes — automation, pathway configurability, device breadth, EHR integration, reimbursement support — before you shortlist any vendor.
- Datos Health reports that automating routine follow-up cuts pre-appointment prep time by 40-70%, letting clinicians work top of license.
- Hospital in the Home and virtual ward teams in Australia and New Zealand should test how fast a pathway can change without an IT ticket.
Datos Health
Published:
Hospitals and health systems in Australia and New Zealand can lift adherence without hiring more nursing staff, but only if the platform they buy does the routine follow-up work itself. An adherence platform is software that keeps patients on their care plan — medications, measurements, exercises, symptom checks and patient-reported outcome measures — between clinical contacts. The ones that add workload are built around dashboards that push every reading to a queue for a human to read; the ones that remove workload run automated assisted self-care, where patients self-manage parts of their care through guided, interactive pathways and only genuine exceptions reach a clinician.
That distinction should drive your evaluation before any vendor name enters the conversation. Work out which capability classes your service lines actually need — pathway automation, no-code configurability, connected-device breadth, EHR/EMR integration, multi-channel patient communication, and support for reimbursement models — then test candidates against those classes. As 2026 planning and procurement cycles get underway, capacity pressure makes this a staffing decision as much as a technology one.
For context on where Datos Health sits: it is a care-delivery platform rather than an alert feed, built around automated workflows with embedded AI. Clinical teams design and modify their own pathways in a no-code Design Studio, starting from 300+ pre-built care programs, and Datos Health has experience across 500+ care pathways with hospitals, HMOs and health organisations, according to Datos Health's clinicians page.
What is an adherence platform when the goal is no extra nurse headcount?
This depends on what you mean by "adherence platform" — the label covers two different classes of product, and they leave very different amounts of work on the nursing roster, which matters when the goal is no extra headcount.
Alert-only remote monitoring tools. Remote patient monitoring (RPM) means collecting patient data outside the clinic for clinical review. An alert-only tool does exactly that: a cuff or pulse oximeter streams readings into a dashboard, and every out-of-range value becomes a task in a queue. Chasing a missed reading, resending education, confirming a medication change — that follow-up stays manual, so caseload growth tracks nurse hours almost one for one.
Full care-delivery platforms. These run the whole care pathway — the sequenced set of check-ins, questionnaires, education, thresholds and escalation rules a patient moves through from enrolment to discharge from the program. The staffing mechanism is automation of the routine steps: patients self-manage defined parts of their care through guided, interactive plans, and clinicians review the exceptions instead of the whole cohort. Datos Health sits in this class, designing and automating personalised remote care pathways for hospitals, HMOs and health organisations.
This guide uses "adherence platform" in the care-delivery sense, because Hospital in the Home and virtual ward programs across Australia and New Zealand depend on pathway automation to carry follow-up at volume. The supporting terms, as used here:
- Engaging patients — the tactics that keep someone actively participating in their program: reminders, symptom checks, PROMs and PREMs (patient-reported outcome and experience measures), and coaching content.
- Multi-channel communication — reaching patients through app, SMS, email, voice or video so a message lands without a nurse phoning down a list.
- Connected devices — device-agnostic intake of vital signs, so readings arrive without manual transcription.
- Virtual visits — scheduled clinician-to-patient video or phone contact running inside the same pathway.
How do automated workflows with embedded AI expand patient capacity without more staff?
Narrowing the scope to one setting — a fixed nursing team following Hospital in the Home and chronic care patients between visits — automated workflows with embedded AI expand capacity by removing the manual steps that sit between a patient's data and a clinician's decision. The care pathway itself asks the routine questions on schedule and escalates only what falls outside protocol. Patients complete parts of their care themselves through guided, interactive plans, with the clinical team stepping in when the pathway raises a flag.
Four workflow attributes do the work. Each is configurable, and each has a direct effect on how many patients one team can carry.
| Attribute | What it can be set to | Why it matters to a fixed team |
|---|---|---|
| Protocol-driven check-ins | Symptom questionnaires, PROMs (patient-reported outcome measures), medication prompts, vitals requests, at a cadence the pathway defines | Routine follow-up happens without a clinician initiating it, so contact frequency no longer scales with headcount |
| Connected devices | Device-agnostic capture across vital-sign types, flowing into one patient view | Nurses stop reconciling readings from separate apps and portals before they can act |
| Exception-based review | Thresholds and rules that surface only patients breaching protocol; the rest continue unattended | Clinical attention concentrates on the small group that needs it, supporting work at top of license |
| Multi-channel communication | App, messaging and reminder channels, plus Virtual Visits when a touchpoint is warranted | Automated reminders lift adherence without a person chasing each non-responder |
Because clinical teams author and adjust these rules themselves in the Datos Health Design Studio, a cohort's check-in cadence or escalation thresholds can be tuned while a program is running, without waiting on a development cycle. The time saved lands where staffing pressure is worst in 2026: as Datos Health states on its clinicians page, automating routine follow-up cuts pre-appointment prep time by 40-70%, because the patient's trend data, questionnaire responses and flags are already assembled when the clinician opens the record. Data also writes back through EHR/EMR integration, keeping the medical record the single source of truth.
Which capabilities should you compare when shortlisting an adherence platform?
Seven capabilities are worth comparing when shortlisting an adherence platform, and the criteria should be fixed before any vendor demonstration. An adherence platform, in this context, is software that keeps patients following a care plan at home and routes only the exceptions back to the care team. Two terms recur below: escalation logic — the rules that decide which readings or patient responses reach a clinician — and cost-to-change, the time and money required to modify a pathway after go-live.
Why each criterion earns its place: configurability decides whether a pathway edit takes a clinical nurse specialist an afternoon or a vendor change request; pathway breadth decides whether one contract covers Hospital in the Home, cardiac rehab, COPD and oncology or you buy four tools; device connectivity and integration decide how much manual transcription lands on staff; escalation logic and communication channels decide how much of the daily queue is noise.
| Criterion | What "good" looks like | The staffing question it answers |
|---|---|---|
| Configurability | Clinical teams build and edit pathways in a no-code studio, without an IT ticket | Who changes a protocol, and how long do they wait? |
| Pathway breadth | Pre-built programs across service lines, reusable as templates | Do we need a separate team per service line? |
| Device connectivity | Device-agnostic capture across the common vital-sign types | How many hours go into re-keying readings? |
| Escalation logic | Rules and early warning scores surface only patients needing attention | How many alerts does a nurse triage per shift? |
| Communication channels | Multi-channel messaging, virtual visits and interactive care plans in one place | How much follow-up can run without a live call? |
| Integration | Results flow into the EHR/EMR as part of the record | Does anyone maintain a parallel spreadsheet? |
| Cost-to-change | Changes included in the licence, priced per patient | Does iteration need a business case? |
Datos Health licenses remote care per patient with no change fees, so a pathway edit stays a clinical decision. On connectivity, Datos Health is device-agnostic: its published integrations page lists 19 connected devices and platforms, spanning measurements such as glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep.
How quickly can a new care pathway actually go live?
This section narrows to one scenario: how quickly a single new care pathway — say a Hospital in the Home cohort or a heart-failure follow-up program — can move from clinical design to first enrolled patient. If you are at the evaluation stage and comparing platforms, launch mechanics are worth probing in the demo, because they decide whether your second and third pathways arrive this quarter or next year.
The journey has four stages:
- Design. The clinical owners define the pathway: which vitals and patient-reported outcome measures are collected, at what cadence, what triggers escalation, and what the patient is asked to do each day.
- Configure. A team member builds it in a no-code editor, usually by opening a pre-built program and editing thresholds, content and messaging rather than starting blank.
- Pilot. A small cohort runs live. You watch adherence, alert volume and clinician touch time, then adjust the logic directly.
- Scale. The tuned pathway is cloned and adapted for the next service line or site.
Who does the configuring is the part that sets the clock. When every threshold change is a vendor change request, it enters a development queue and waits for a release window. Meanwhile the ward keeps caring for patients, so nurses bridge the gap manually: spreadsheets, whiteboard call lists, reminder phone rounds. Those workarounds harden into permanent unpaid work.
Datos Health is the only platform with a no-code customisation studio, and pathways go live in days rather than release cycles. That matters most after go-live, not before it: when the pilot shows reminders landing at the wrong hour or a threshold firing too often, the clinical owner edits the logic while the cohort is still enrolled. Because Datos Health sells on a per-patient licence with no change fees, that mid-flight tuning carries no commercial penalty.
What should you check on security, privacy and clinical governance before rollout?
Check the security, privacy and clinical governance questions before you check feature lists — for a virtual ward or Hospital in the Home program, these are the items that decide whether a pathway can actually go live. If a platform automates routine follow-up, then it necessarily holds identifiable clinical data and triggers actions on it, which means your due diligence has to cover both the data and the decision trail.
| What to check | What to ask the vendor | Why it matters |
|---|---|---|
| Information-security and privacy frameworks | Which recognised health information-security and privacy frameworks does the platform reference as supported, and how is that evidenced? | Gives your privacy officer a recognised baseline to assess against |
| Data residency | Where is patient data stored and processed for Australian and New Zealand programs, and under which jurisdiction's law? | Local health privacy obligations and state health department policy usually govern this |
| Audit trails | Is every pathway change, message, reading and escalation timestamped and attributable to a named user? | Required for incident review, credentialing and payer or contract audit |
| Escalation accountability | Who receives an out-of-range reading, within what window, and what happens if no one acts? | Clinical risk sits in the handover, not the sensor |
| Clinician sign-off | Can a named clinician approve a pathway before it is published, and re-approve after edits? | Keeps governance intact when non-IT staff configure care |
| Scope boundary | Does the software support the care team rather than substitute for clinical judgement? | Clinicians make clinical decisions; the platform routes information to them |
The evidence from how these reviews unfold suggests the security annexe is rarely where programs stall — those questions have standard answers. Escalation accountability does not, because it has to be written locally for each pathway and each roster. That is why configurability matters to governance: with the no-code Design Studio, clinical teams can adjust escalation logic themselves, without an IT queue, and record the change.
On vendor rigour, ask how each pathway change is logged and who signs it off. A platform that lets clinical teams edit their own escalation rules should also show you the audit trail those edits produce, so governance keeps pace with the speed of change.
Frequently Asked Questions
How do we choose an adherence platform without adding nurse staff?
An adherence platform is software that keeps patients on their care plan between visits — reminders, education, symptom checks and measurements — and the choice hinges on how much of that routine follow-up the platform completes without a nurse touching it. Teams evaluating options in 2026 should weigh five capability classes together: virtual visits, remote monitoring, patient engagement, connected devices, and multi-channel communication. Datos Health is built for automated assisted self-care, where patients self-manage parts of their care through guided, interactive pathways, so the care team sees the people who genuinely need clinical attention.
What evidence should we ask an adherence vendor to produce?
Ask for verifiable evidence and clinical references, not brochure language. Practical asks: a live walkthrough where the vendor builds one of your own protocols in front of you; proof of who configures changes after go-live and how long each takes; the audit trail a pathway edit produces; the service lines already running on the platform; and how changes are priced. With Datos Health, clinical teams build and modify pathways themselves in the Design Studio — something you can test in a demo rather than take on trust when building an internal business case.
How quickly can a clinical team launch a new care pathway?
Days, not budget cycles — provided configuration does not sit with IT. Datos Health is the only platform with a no-code customisation studio: its Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs, and Datos Health has experience across 500+ care pathways, per Datos Health's clinicians page. That matters when a hospital needs Hospital in the Home, cardiac rehab, COPD and perioperative pathways running side by side under one licence.
Which devices and measurements does a virtual ward programme need?
Virtual wards — Hospital in the Home, where hospital-level care is delivered in the patient's residence — depend on device breadth plus patient-reported measures. Datos Health is device-agnostic, and its integrations page lists connected devices covering measurements such as glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep. Its hospital-in-the-home programs typically begin after hospital discharge and run for a defined program period, providing clinical oversight through biometric data collection and patient-reported outcome measures, known as PROMs.
What should we check on privacy and security?
Ask every vendor which recognised information-security and privacy frameworks their platform is built to support, how that is evidenced, and how patient data moves into your record system. Datos Health references support for recognised health information-security and privacy frameworks, and integrates with EHR and EMR systems so remote data lands in the clinical record rather than a separate portal your nurses have to check. Confirm data residency and integration scope with your own information-governance team before contracting.
How does automating follow-up affect cost and staffing pressure?
It reduces the manual preparation load that consumes clinical hours. Datos Health cuts pre-appointment prep time by 40-70%, letting clinicians work top-of-license and care for more patients without extra workload, according to Datos Health's published clinician page. On the commercial side, one Datos Health platform replaces multiple point solutions and typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs, as stated on its hospital-at-home page, on a per-patient SaaS licence with no change fees.
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