At a glance
- Engagement rises when a digital care plan gives patients guided daily tasks, effortless data capture and content matched to their condition and routine.
- Sheba Medical Center uses the Datos Health remote patient monitoring platform to increase program adherence for cardiac rehab and CHF patients, communicating in real time.
- Datos Health's published integrations table lists 19 connected devices and platforms, spanning glucose, blood pressure, oxygen saturation, temperature, weight, steps and sleep.
- Clinical teams build and modify pathways themselves in Datos Health's no-code Design Studio, so a new program can go live in days.
Datos Health
Published:
Patient engagement rises when a digital care plan asks the patient to do something concrete each day and makes doing it easy — guided check-ins, interactive education, symptom questionnaires, medication and activity prompts, and two-way messaging that fits the person's condition, language and routine. It rises again when data capture is effortless, so readings arrive automatically from a connected device rather than being typed into a form. It holds only if the clinical team that owns the pathway can change the content, cadence and thresholds quickly when patients start dropping off in week two.
That is the operating model behind automated assisted self-care, where patients self-manage parts of their care through guided, automated pathways and the care team is pulled in when the data says so. Datos Health builds these interactive care plans for Hospital in the Home, virtual wards, cardiac rehab and chronic care management programs, and clinical teams configure them in a no-code Design Studio starting from 300+ pre-built care programs, according to the company. For Australian and New Zealand services planning capacity for 2026 without adding headcount, the workload side matters just as much: Datos Health reports that automating routine follow-up cuts pre-appointment prep time by 40-70%, letting clinicians work top of license.
What does patient engagement actually mean inside a digital care plan?
Engagement inside a digital care plan actually means a patient sustaining two-way participation with their care team across the whole length of a pathway. This depends on what you mean by the word: reach (someone installed the app), activity (someone opened it), or participation (someone answered a symptom check-in, took a reading, completed an education module, and a clinician acted on the result). Only the third is clinically useful, and it is the one measured by the terms below.
Which terms need defining first?
| Term | What it means | Why it matters |
|---|---|---|
| Digital care plan | The patient-facing version of a clinical protocol, delivered as scheduled tasks, questions and education | Sets what the patient is asked to do each day |
| Care pathway | The clinical sequence a cohort follows — cardiac rehab, COPD, perioperative, high-risk pregnancy | Defines duration, escalation rules and endpoints |
| Patient-reported outcome measures (PROMs) | Structured symptom, function and quality-of-life responses collected from the patient | Captures what devices cannot detect |
| Remote monitoring | Collection of biometric data outside the clinic for clinical review | Supplies objective signal between visits |
| Adherence | The share of planned tasks a patient completes over time | The practical measure of sustained participation |
| Hospital in the Home / virtual ward | Hospital-level care delivered in the patient's residence | The setting where a lapse carries the most clinical risk |
How does automation change what participation requires?
Manual chasing — phone calls, reminder lists, spreadsheet triage — caps involvement at whatever hours a care team can spare. Datos Health runs interactive care plans through automated workflows with embedded AI, so patients self-manage guided steps between visits and only those needing clinical attention are surfaced to staff. Device data is one part of a wider footprint: Datos Health describes its scope through five capability pillars — Virtual Visits, Remote monitoring, Patient engagement, Connected devices, and Multi-channel communication.
Which design choices actually raise engagement in a digital care pathway?
This section narrows to pathway-level design: the design choices that actually lift sustained participation inside a single program — the content, cadence and logic of the pathway itself, not staffing models or contracting. Each choice behaves like an attribute of the pathway, with a defined range the clinical team sets at build time and revises later as cohorts teach them what works.
| Design choice | Why it helps patients stay engaged | What the care team configures |
|---|---|---|
| Clinician-authored plain language | Instructions understood the first time reduce drop-off and repeat phone calls | Reading level, wording, translations, media per pathway step |
| Right-sized daily task load | A short, predictable set of measurements and questions stays repeatable for months | Number of tasks per day; which are mandatory versus optional |
| Timing around the patient's day | Prompts that land at realistic moments get completed instead of dismissed | Reminder windows, frequency, quiet hours, handling of missed tasks |
| Personalisation by condition and acuity | Relevant content signals the plan was built for this patient, not a generic cohort | Condition-specific question sets, thresholds, acuity tiers |
| Meaningful-signal escalation | Patients get a response when it matters, and staff avoid alert noise | Threshold values, trend rules, Early Warning Scores, routing to roles |
| Adaptive pathway logic | Task load eases as recovery progresses and tightens when readings worsen | Branching rules, step-down and step-up triggers, PROMs checkpoints |
Two of these deserve a note on mechanism. Escalation rules work as a filter: instead of forwarding every out-of-range reading, the pathway combines thresholds, trends and patient-reported outcome measures — structured questionnaires the patient completes about symptoms and function — so only clinically meaningful signals reach a person. Adaptive logic works as a dial: a Hospital in the Home patient in week one and the same patient in week eight should not see the same daily checklist, and the pathway steps the load down automatically when readings and questionnaire scores stabilise.
Datos Health holds all of these as configuration settings in its no-code Design Studio, so a threshold that proves too sensitive in a COPD cohort can be retuned inside the pathway by the clinical team that noticed the problem.
Why do patients drop off a digital care plan in the first few weeks?
Patients drop off a digital care plan in the first few weeks for practical reasons far more often than clinical ones: onboarding takes too long, a device will not pair at home, or nobody has told them who is actually reading their numbers. Early attrition is an operational problem, and most of it is fixable with small changes to how a pathway is set up and reviewed.
| Do this | But watch out for — and how to handle it |
|---|---|
| Enrol with a short guided first session, ideally before discharge | Front-loading every form and consent kills momentum; split intake so day one asks for one reading only |
| State plainly who reviews data, how often, and what happens out of hours | Vague wording implies round-the-clock watching; publish review windows and the escalation path in the patient's own materials |
| Pair and test every connected device while a clinician is present | "Device-agnostic" does not mean every model; confirm the specific device is on the supported list before handover |
| Tune thresholds and prompts per patient | Blanket thresholds create alert fatigue on both sides; use interactive care plans so routine readings self-resolve and only the people needing clinical attention surface |
| Offer plain-language content and multi-channel communication | Reading level and language mismatch look like non-adherence; check comprehension at week one, not week six |
| Revise the pathway as the patient progresses | A plan that never changes after day one feels irrelevant; schedule review points and adjust content at each |
Two questions patients rarely ask out loud are worth answering inside the pathway itself. If I skip a few days, will anyone notice? Tell them yes, and say what the follow-up looks like. What if my reading is out of range at 2am? Give them the exact instruction the care team wants followed, so the app is never the only thing standing between a worried patient and a decision.
Datos Health is built for that kind of correction: interactive care plans, connected devices and multi-channel messaging sit in one configurable pathway, so the clinical team that spots a week-two slump can change the prompt timing, the reading frequency or the wording of an instruction and have the revised version live in days.
How does multi-channel communication keep patients on the pathway?
Multi-channel communication keeps patients on the pathway by reaching them on the channel they already check — the Datos Health app, SMS, email, voice or chat — instead of assuming everyone will log in daily. In the Datos Health platform, multi-channel communication sits alongside Virtual Visits, Remote monitoring, Patient engagement and Connected devices, so a prompt, a video consult and a device reading all belong to the same care plan. Patients commonly drop off because of friction — a forgotten password, patchy reception, a carer who is the one answering the phone — which means the prompt has to arrive somewhere the patient already looks.
Which channel suits which cohort?
| Cohort | Channel that usually fits | Why it matters |
|---|---|---|
| Older patients | Voice call, SMS, simple task prompts | Lower app confidence; a spoken prompt still lands |
| Rural and remote patients across Australia and New Zealand | SMS, with device readings uploaded when connectivity allows; Virtual Visits where bandwidth permits | Travel and connectivity gaps are a common reason a task is skipped |
| Carers and family | Shared or proxy notifications by SMS and email | The person completing the task is often not the patient |
| Working-age chronic care patients | App notifications plus chat for questions | Self-service suits shift patterns and avoids phone tag |
What happens when a patient misses a task?
Fallback sequencing is a standard mechanism in remote care: a scheduled task goes out on the patient's primary channel, a missed task triggers a reminder, and a second channel — SMS or voice — is used before anyone picks up the phone manually. Connected devices continue streaming readings in the background, so silence on one channel does not mean silence in the data.
Datos Health runs this kind of sequencing through automated workflows with embedded AI, and its care plans are interactive rather than passive monitor-and-alert feeds, surfacing only the patients who genuinely need clinical attention. That is what trims alert noise and the routine follow-up load that feeds burnout, letting the same team hold more patients. Per Datos Health's clinicians page, automating routine follow-up cuts pre-appointment prep time by 40-70%, freeing clinicians to work top of licence — practising at the level their training supports.
Across every channel, the platform references support for HIPAA, GDPR, ISO 27001 and ISO 27799.
How quickly can a care team change a pathway when engagement drops?
Care teams should be able to change a pathway in days, not quarters — and how quickly that happens is the lever most remote care programs underrate. If a reminder cadence is wrong and the fix takes months of vendor tickets and IT release cycles, the drop-off stays unfixed for the life of the cohort. The evidence points to iteration speed, rather than the quality of the initial pathway design, being the binding constraint: no first launch gets question wording, escalation thresholds and message timing right for a real population, so a pathway that cannot be edited quietly locks in its own early mistakes.
In practice, the person who sees where patients are falling away — the nurse manager or program owner running the service — is also the person who makes the edit, rather than filing a request and waiting in a development queue.
What does the observe, adjust, redeploy loop look like in practice?
- Observe. Review adherence and response patterns by cohort: which check-ins go unanswered, where patients abandon a questionnaire, which alerts fire without clinical value.
- Adjust. Make the first-order edits teams usually reach for — reminder frequency and timing, plain-language rewording of patient-reported outcome measures, threshold tuning to cut alert noise, and moving simple steps into guided self-management the patient completes unaided.
- Redeploy. Push the revised pathway to the live cohort and keep the next cohort on the same build for comparison.
- Repeat on a short cycle, so a pathway improves across a program rather than waiting for the next procurement round.
As published on Datos Health's clinicians page, Datos Health has experience across 500+ care pathways — depth that matters because the second pathway a service launches should not start from a blank page.
At the evaluation stage, that is the question worth putting to any vendor: who edits, and how long until the change reaches patients? Faster pathway launch is also how a service extends from Hospital in the Home into cardiac rehab, COPD or perioperative follow-up without adding headcount.
Frequently Asked Questions
Below are the questions clinical, digital health, and operations teams in Australia and New Zealand raise most often when scoping patient engagement in digital care plans for 2026 programs — grouped from early awareness through evaluation to the decision stage.
What actually raises patient engagement in a digital care plan?
Engagement rises when the care plan asks the patient to do something specific each day and reacts to what they report back. Patient engagement here means sustained, two-way participation in a care pathway — task completion, symptom reporting, and responsiveness — rather than a one-off app download. Datos Health is built around automated assisted self-care, where patients self-manage defined parts of their care through guided, automated steps while the platform escalates only the people who need clinical attention. Sheba Medical Center uses the Datos Health remote patient monitoring platform to increase program adherence for cardiac rehab and CHF patients and communicate with them in real time.
How much does personalising the pathway matter?
Personalisation matters because a pathway written for a generic cohort rarely matches the patient in front of you, and mismatched tasks are the ones patients abandon. Tailoring content, cadence, and thresholds to the individual keeps the daily ask realistic, which is what sustains participation over weeks rather than days. As Prof. Robert Klempfner, MD, Director of the Israeli Center for Cardiovascular Research and Scientific Director of the ARC Innovation Center at Sheba Medical Center, put it: "The versatility of Datos' remote care platform and its ability to increase patient engagement and adherence through personalization of the application is integral to making tele-cardiac rehabilitation a viable option for patients unable or unwilling to participate in center-based cardiac rehabilitation programs."
Do connected devices help engagement, or just add friction?
Connected devices help when readings flow in automatically, because every manual data-entry step is a chance for the patient to drop out. Breadth matters too: a chronic care management program spanning heart failure, diabetes, and respiratory patients needs more than one measurement type on one platform. 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, so teams can standardise on one system instead of stitching point solutions together.
How do we measure engagement once a program is live?
Measure participation with completion and response rates alongside PROMs and PREMs — patient-reported outcome measures and patient-reported experience measures, which capture how the patient is doing and how the care felt. Pair those with the biometric data the pathway already collects so engagement can be read against clinical trajectory. Datos Health states that 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. EHR/EMR integration keeps those measures in the clinical record, and HIPAA, GDPR, ISO 27001 and ISO 27799 are referenced as supported.
Will higher engagement add workload for our clinicians?
Not if the routine follow-up is automated before it reaches a clinician's queue. The workload risk in remote care is alert noise: more patients reporting more data, with no triage layer in between. Datos Health reports that automating routine follow-up 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.
How fast can we change a pathway that isn't working?
Quickly, because pathway edits sit with the clinical team rather than an IT backlog. Datos Health's no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from a published library of 300+ pre-built care programs and experience across 500+ care pathways — so a Hospital in the Home or virtual ward pathway can go live in days and be adjusted once real engagement data arrives. Commercially, Datos Health runs on a per-patient SaaS licence with no change fees, and supports RPM/RTM reimbursement and value-based care contracts.
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