At a glance
- A diabetes remote care platform must cover connected devices, remote monitoring, patient engagement, virtual visits and multi-channel communication in one configurable system.
- Datos Health's published integrations table lists 19 connected devices and platforms, spanning glucose, continuous glucose, blood pressure, weight, steps and sleep.
- Hospital diabetes teams need pathway logic clinicians can edit themselves, rather than waiting on an IT development queue.
- Datos Health is the only platform with a no-code customization studio; pathways live in days.
- Automated assisted self-care keeps routine follow-up moving and surfaces the patients who genuinely need clinical attention.
Datos Health
Published:
A diabetes remote care pathway — the structured sequence of readings, education, check-ins and clinical escalation that carries a patient between appointments — needs a platform that covers five capability pillars: Connected devices, Remote monitoring, Patient engagement, Virtual Visits and Multi-channel communication, all tied back into the medical record. For hospital and health system diabetes services in Australia and New Zealand evaluating platforms in 2026, the practical test is whether a diabetes nurse educator or endocrinology team can change the pathway logic themselves when a protocol shifts, and whether glucose and continuous glucose data arrive alongside weight, blood pressure and patient-reported measures in one place. Datos Health's published integrations table, on its integrated-devices page, lists 19 connected devices and platforms, spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep. Datos Health is the only platform with a no-code customization studio; pathways live in days. Its approach is automated assisted self-care, where patients self-manage parts of their care through guided, automated steps.
What must a diabetes remote care pathway cover from enrolment to discharge?
Narrowing the scope to diabetes specifically rather than chronic disease generally: a diabetes pathway delivered remotely must define a named owner and a required action at every stage, from the moment a patient is enrolled to the moment they are discharged or stepped down. For clinical and digital teams at the evaluation stage, the practical test of any platform is whether it can carry a patient through all of the following without a manual handover falling through the cracks.
- Enrolment and consent. Identify the patient (newly diagnosed, poorly controlled, post-admission, or gestational), capture consent, and set the program duration and review cadence up front.
- Baseline and stratification. Record starting glycaemic control, comorbidities, medications and social factors, then assign the patient to a pathway intensity that matches their risk.
- Device pairing and data capture. Connect glucose meters or continuous glucose monitoring — sensors that stream interstitial glucose readings rather than relying on finger-pricks — plus weight and blood pressure where the pathway calls for it.
- Guided self-care. Deliver education, medication reminders, diet and activity prompts, and symptom check-ins so patients actively self-manage between contacts instead of waiting for a clinician call.
- Clinical review and escalation. Route only out-of-range patterns and unanswered check-ins to a clinician, with clear thresholds for a virtual visit, a medication review by the treating team, or referral.
- Outcome measurement. Collect patient-reported outcome and experience measures, known as PROMs and PREMs, alongside biometric trends so the program can evidence its effect.
- Discharge or step-down. Close the loop with a documented handover to the general practitioner or outpatient clinic, plus a lighter maintenance plan for long-term follow-up.
Device breadth matters most at the capture stage: the pathway should accept readings from the meters and sensors patients already use, rather than forcing one vendor's hardware on the cohort. Alongside that, every stage needs to be documented in the patient record so continuity of care holds, which makes EHR/EMR integration a core evaluation question. One Datos Health platform replaces multiple point solutions, so enrolment, monitoring and discharge can sit in one configured pathway rather than in separate tools.
Which platform capabilities does a diabetes pathway actually depend on?
Scoped narrowly to diabetes, the platform capabilities a pathway depends on are more specific than generic monitoring tooling suggests — glucose data behaves differently from a weekly weight or a one-off symptom check. A diabetes programme runs on dense, device-sourced readings, patient self-management between visits, and escalation that only fires when a clinician is genuinely needed.
The capability classes below map to that workload. Each lists what it must cover and why it matters.
- Connected devices. Range: glucose meters, continuous glucose monitors (CGM — wearable sensors that stream interstitial glucose readings), blood pressure cuffs, scales, and activity and sleep trackers. Why it matters: device-agnostic ingestion across a broad set of vital-sign types means the pathway is not rebuilt when a health service changes supplier.
- Remote monitoring logic. Range: per-patient thresholds, trend rules, and Early Warning Scores rather than a single global alert rule. Why it matters: hypoglycaemia and hyperglycaemia limits differ by patient, and fixed thresholds generate alert noise nurses learn to ignore.
- Patient engagement. Range: interactive care plan tasks, medication and testing reminders, education, and PROMs — patient-reported outcome measures, the structured questionnaires that capture symptoms and function. Why it matters: this is where patients manage parts of their own routine through guided, automated steps, so only the people who need clinical attention reach the queue.
- Multi-channel communication. Range: more than one messaging channel, so reminders and check-ins reach patients where they already are. Why it matters: adherence drops when the only channel is an app the patient never opens.
- Virtual Visits. Range: scheduled reviews and escalation-triggered consults. Why it matters: a reading out of range needs a clinical conversation, not another notification.
- Pathway configurability and integration. Range: no-code editing in Datos Health's no-code Design Studio, so clinical teams adjust the diabetes pathway themselves without an IT queue, plus EHR/EMR integration.
How do connected glucose and vitals devices fit into the clinical workflow?
When a patient is enrolled on a diabetes pathway, connected glucose meters, continuous glucose monitors and other vitals devices should feed the care plan automatically rather than arriving as a separate data chore. In practice, the device pairs once with the patient's app, readings stream in the background, and the pathway logic decides what — if anything — the care team ever sees. Device-agnostic capture matters here because a diabetes cohort rarely produces glucose readings alone: cuffs, scales and activity wearables carry the cardiometabolic and lifestyle signals that sit alongside them in the same plan.
The attributes worth specifying before you configure anything:
| Attribute | Typical values or range | Why it matters |
|---|---|---|
| Data source | Bluetooth meter, continuous glucose monitor, cuff, scale, wearable, or manual entry | Determines whether a reading needs patient action, which drives adherence |
| Capture frequency | Continuous, scheduled, or event-triggered (pre-meal, post-meal, symptom-based) | Sets how much data arrives and how often the pathway evaluates it |
| Thresholds | Patient-specific limits, trend rules, missed-reading rules | Converts raw numbers into a triage decision instead of a running feed |
| Patient-reported inputs | PROMs and PREMs — patient-reported outcome and experience measures — plus symptom and medication check-ins | Supplies context a device cannot, such as hypoglycaemia symptoms or dose changes |
| Escalation route | Automated patient guidance, task to a nurse queue, or clinician review | Decides who acts, and keeps low-acuity events away from clinicians |
| Record destination | EHR/EMR integration | Keeps the clinical record authoritative and avoids a parallel data silo |
Triage is applied by the pathway itself before anything reaches a clinical inbox. Rules evaluated against those thresholds can trigger guided steps the patient completes independently — a repeat reading, a carbohydrate or hydration prompt, an education module — while deterioration patterns and recognised scoring logic such as Early Warning Scores route the patient to a clinician with the supporting readings attached.
How does a remote-enabled diabetes pathway differ from standard clinic follow-up?
A remote-enabled diabetes pathway and standard clinic follow-up serve the same cohort, but they differ on when data arrives, who handles routine work, and what triggers clinician time. Clinic follow-up is organised around booked appointments, so glucose patterns, medication adherence and symptom changes are reviewed retrospectively at a fixed interval. The remote-enabled model runs in the gaps between those visits, using an interactive care plan — structured tasks, measurements and education delivered to the patient — so routine checks happen continuously and only exceptions reach a clinician.
Before comparing the two models, it helps to fix the criteria that actually change a decision:
- Data cadence and recency — titration and lifestyle coaching depend on how fresh the glucose and weight data are when someone looks at it.
- Who does the routine follow-up — chasing readings, sending reminders and collecting questionnaires either consumes clinician hours or is automated.
- Escalation trigger — review happens because a date arrived, or because a threshold or trend rule fired.
- Patient role — passive reporting at a visit, versus guided self-management, where the patient completes defined parts of the plan through prompted, automated steps.
- Service model fit — whether the activity sits inside Hospital in the Home, a virtual ward, a value-based care contract, or episodic outpatient follow-up.
| Model | Data cadence | Routine follow-up work | Escalation trigger | Patient role |
|---|---|---|---|---|
| In-clinic follow-up | Snapshot at each visit | Manual, clinician-led | Scheduled date | Reports at appointment |
| Remote-enabled diabetes pathway | Continuous between visits | Automated workflows with embedded AI | Threshold or trend rule | Guided self-management |
On a Datos Health pathway, those routine steps run as automated workflows with embedded AI, so clinician review is reserved for the patients whose readings or questionnaire answers fall outside the plan.
In-clinic review remains the right setting for examination-dependent work such as foot and eye checks, or complex insulin starts that need hands-on teaching. The remote-enabled model suits stable-but-rising HbA1c, newly titrating patients, and long-term condition follow-up where frequent contact is the point of the programme.
How quickly can a diabetes pathway be built, changed and scaled across service lines?
A diabetes pathway can be built and changed quickly when the clinical team owns the configuration and is not queued behind a development backlog. The practical sequence looks like this:
- Start from a pre-built program, then subtract. Begin with the pre-built care program closest to your cohort and remove what your patients do not need, rather than specifying a new build from scratch.
- Map the data inputs to connected devices. Decide which readings the pathway acts on — glucose, continuous glucose, blood pressure, weight — and confirm each is covered by the platform's device integrations before writing any logic.
- Write the self-management logic, not only the alert logic. Guided automation means the patient handles parts of the plan themselves, so define the education, titration prompts and patient-reported outcome measures alongside escalation thresholds.
- Pilot on one clinic and iterate on a weekly cycle. Change thresholds and message timing in the Design Studio between cycles, so each revision costs a configuration session rather than a release.
- Clone into the adjacent service line. A stable diabetes pathway is the base for perioperative, long-term cardiometabolic and Hospital in the Home variants of the same cohort.
| Do this | But watch out for |
|---|---|
| Configure in-house without IT tickets | Governance gaps — agree who signs off clinical content changes before go-live |
| Automate routine follow-up | Over-automating edge cases; keep a manual review route for unstable patients |
| Reuse one pathway across service lines | Silent drift between copies; version them and review changes on a set cadence |
| Add device types as the cohort grows | Data you collect but nobody acts on; retire unused inputs at each review |
Datos Health's clinicians page says its no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs. Once configuration moves in-house, the binding constraint on scale migrates from engineering capacity to clinical governance capacity, since every cloned program still needs someone accountable for its content. Name that sign-off owner before the second service line launches.
Frequently Asked Questions
What should a diabetes remote care pathway cover end to end?
A diabetes remote care pathway should cover four things end to end: structured data capture, patient-facing tasks and education, escalation logic, and clinician review. Data capture for diabetes usually means glucose readings alongside weight, blood pressure and activity, plus PROMs and PREMs — patient-reported outcome and experience measures, the short questionnaires that tell you how someone is actually coping between visits. Datos Health's integrated-devices page shows a published integrations table of 19 connected devices and platforms, including glucose and continuous glucose sources. Escalation logic matters just as much: without rules that decide which readings warrant a clinician's time, a diabetes program simply converts one type of workload into another.
How fast can a clinical team change a diabetes pathway once it is live?
Pathway changes can stall when a titration rule or education sequence needs a vendor ticket. In Datos Health's no-code Design Studio, clinical teams build and modify care pathways themselves without IT dependency, so a diabetes nurse educator can adjust a check-in cadence directly rather than queuing behind an IT backlog.
Does automating diabetes follow-up really reduce clinician workload?
Yes, and the mechanism is specific: automating routine follow-up removes the manual chart-trawling that happens before every appointment. Datos Health's clinicians page states that, by automating routine follow-up, Datos Health cuts pre-appointment prep time by 40-70%, letting clinicians work top-of-license and care for more patients without extra workload. Patients handle guided self-management steps through interactive care plans, and only those who need clinical attention are surfaced to the team — which is also how you keep alert volume from overwhelming a small diabetes service.
Who uses Datos Health and what has been published about it?
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. KLAS Research published an Emerging Technology Spotlight report on the Datos Health remote care platform, covering customer satisfaction, the outcomes customers achieved, and how they used the platform to reduce care-team workload. TIME also named Datos Health a Leading HealthTech Company of 2025.
How do diabetes remote care programs get funded?
For hospital and health system diabetes services in Australia and New Zealand, funding usually follows the service model the pathway sits in, such as Hospital in the Home, a virtual ward, or a value-based care contract. Datos Health supports value-based care contracts and is sold on a per-patient SaaS licence with no change fees. For Hospital in the Home programs generally (not diabetes-specific), Datos Health's hospital-at-home page states that its hybrid care platform typically reduces the cost of care per patient by 30-50%. The platform also supports RPM and RTM reimbursement, which are US billing code families used in US practice rather than an ANZ funding route.
Which integration and compliance questions should we ask a vendor?
Ask about EHR and EMR integration first, because a diabetes pathway that writes readings into a separate portal creates a second chart nobody reads. Datos Health offers EHR/EMR integration and is device-agnostic. Put the same standards questions to every vendor, such as which HL7 or FHIR interfaces they support with your systems. On security and privacy, Datos Health references HIPAA, GDPR, ISO 27001 and ISO 27799 as supported.
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-10-26