At a glance
- Judge a diabetes remote monitoring platform on pathway configurability, device breadth, EHR integration, automated self-care logic, and reimbursement support — not alert volume.
- Datos Health's no-code Design Studio lets clinical teams build and change pathways themselves, starting from 300+ pre-built care programs.
- By automating routine follow-up, Datos Health cuts pre-appointment prep time by 40-70%, so clinicians work top-of-license.
- Device-agnostic capture across 8+ vital-sign types plus EHR/EMR integration replaces multiple point solutions with one licensed platform.
- Ask vendors for named customer evidence and clear ANZ fit before signing anything in 2026.
Datos Health
Published:
If you are choosing a platform to manage diabetes outside the clinic, the decision comes down to five things: how easily your clinical team can build and change a care pathway without waiting on IT, how many device and vital-sign types the platform ingests, whether it writes back into your EHR/EMR (the electronic record your clinicians already work in), whether it automates patient self-management rather than simply firing alerts at nurses, and whether it supports reimbursement models such as RPM and RTM. Remote Patient Monitoring — collecting patient data outside the clinic for review — is the baseline, not the goal. Diabetes is a long-horizon condition with glucose, weight, blood pressure and patient-reported data all in play, so a monitor-and-alert tool tends to add triage work instead of removing it. What you want is automated assisted self-care: guided, interactive care plans that let patients self-manage the routine parts of their programme and surface only the people who genuinely need clinical attention. Datos Health is built around that model, and by its own account offers 300+ pre-built care programs plus experience across 500+ care pathways for teams that need diabetes running alongside CHF, COPD, perioperative and Hospital in the Home programmes on one licence. The sections below set out the evaluation criteria, the trade-offs, and where this class of platform is not the right fit — useful whether you are shortlisting vendors in 2026 or auditing a programme you already run.
What makes a diabetes remote monitoring platform different from generic RPM software?
This section narrows the scope to one use case: what makes a diabetes remote monitoring platform distinct from general-purpose remote patient monitoring (RPM) software — that is, tools that simply collect patient data outside the clinic for later review. Glycaemic management is continuous, self-managed and behaviour-driven, so a diabetes-specific platform has to do more than stream numbers into a dashboard.
The attributes worth checking during evaluation:
- Data types accepted. Range: fingerstick glucose, continuous glucose monitoring (CGM) traces, weight, blood pressure, activity and sleep. Why it matters: diabetes rarely travels alone, and a single-signal tool forces a second contract for the comorbidities.
- Pathway logic. Range: static reminder schedules through to conditional, branching care plans that change with the reading. Why it matters: without branching, every out-of-range value lands on a clinician instead of triggering patient-facing guidance first.
- Patient-reported inputs. Range: none, simple surveys, or validated PROMs and PREMs — patient-reported outcome and experience measures. Why it matters: adherence and symptom burden are invisible in device data alone.
- Escalation model. Range: alert-everything versus rules that surface only patients needing clinical attention. Why it matters: alert noise is the fastest route to clinician disengagement.
- EHR/EMR integration. Range: PDF summaries through to structured write-back. Why it matters: unintegrated data creates a parallel chart.
Datos Health is built for this hybrid model, blending in-person and virtual touchpoints in one journey rather than monitoring alone.
Which CGM, BGM, insulin pump, and pen integrations should the platform support?
Continuous glucose monitoring (CGM) — sensor-based glucose readings captured automatically through the day — and blood glucose meters (BGM), the fingerstick devices patients use at home, are the baseline feeds. Insulin delivery data from connected pens and pumps is a separate question to put to any vendor, and one worth asking explicitly rather than assuming. Ask each vendor to specify the following attributes, device by device, before you sign.
- Device classes covered. Allowed values: CGM sensors, BGM meters, connected insulin pens and pumps, Bluetooth blood-pressure cuffs, and weight scales. Why it matters: comorbid hypertension and weight sit in the same review, so a glucose-only feed forces a second tool.
- Transport method. Allowed values: direct Bluetooth Low Energy pairing to the patient app, or cloud-to-cloud API pull from the device manufacturer's data platform. Why it matters: it sets the ceiling on how fresh your data can be.
- Latency. Allowed values: near-continuous streaming through to periodic batch sync. Why it matters: titration decisions need current readings; trend review does not.
- Calibration model. Allowed values: factory-calibrated sensors versus meters requiring fingerstick confirmation. Standards such as the ISO accuracy criteria for glucose meters, and MARD as the accepted CGM accuracy metric, give you a common yardstick.
- Units and mapping. Confirm mmol/L handling for Australian and New Zealand services, plus how readings map to discrete EHR observations rather than PDF summaries.
On the glucose and comorbidity side of that checklist, Datos Health is device-agnostic across 8+ vital-sign types with EHR/EMR integration, so glucose, continuous glucose, blood pressure, weight and activity data land in one clinical view instead of several vendor portals.
How should glycemic analytics and alerting reduce clinician alarm fatigue?
Glycemic analytics only cut alarm fatigue when the calculation layer and the alerting layer are designed together, not bolted on separately. Ask a vendor to show exactly how each metric is derived and what it is allowed to trigger.
- Time in range (TIR) — the share of readings inside the clinician-set target band over a defined window. It is a trend metric, so it follows that TIR should populate a review queue, never a real-time page.
- GMI (glucose management indicator) — an estimated HbA1c derived from mean sensor glucose. Useful for pathway review; meaningless as an instant alarm.
- Coefficient of variation (CV) — standard deviation divided by mean glucose, the standard measure of glycaemic variability. Rising CV is an early signal that a regimen needs revisiting.
- Hypoglycaemia risk — should be weighted by depth, duration and nocturnal timing, not by a single crossed threshold.
| Do this | But watch out for |
|---|---|
| Set patient-specific thresholds, not one cohort default | Over-personalisation drifts if nobody reviews it |
| Require persistence (sustained excursion) before escalating | Genuine rapid falls can be delayed — exempt hypoglycaemia from persistence rules |
| Route by acuity: educator, nurse, then physician | Silent hand-offs when a role is unstaffed; define fallback owners |
| Let guided self-care resolve routine excursions | Patients disengage if prompts are too frequent |
The highest-impact mitigation is separating trend analytics from event alerting at design time. Datos Health supports this with its library of pre-built care programs, so escalation logic starts from a tested diabetes template rather than a blank rule set.
How does the platform fit into EHR workflows and interoperability standards?
When you are evaluating whether a diabetes remote monitoring platform will fit your existing EHR workflows, the integration questions matter more than the dashboard. If a nurse has to leave the electronic health record to see a glucose trend, the pathway adds clicks instead of removing them. Datos Health supports EHR/EMR integration so that data collected at home lands where the care team already works.
Use these attributes as your checklist when scoping an integration with a hospital or health service IT team:
| Attribute | What to specify | Why it matters |
|---|---|---|
| Interface standard | HL7 v2 messaging (ADT for admissions, ORU for results) and HL7 FHIR resources such as Observation and Patient | Determines whether your integration engine can broker the feed without custom middleware |
| Launch model | SMART on FHIR embedded launch versus a separate clinician portal | An embedded launch keeps review inside the clinician's existing chart context |
| Terminology binding | LOINC codes for glucose, HbA1c and vital signs; SNOMED CT for problems | Uncoded results arrive as free text and cannot be trended or reported on |
| Direction of flow | Inbound device and questionnaire data, plus write-back of notes, tasks or orders | One-way feeds create duplicate documentation for the care team |
| Security posture | Ask for the vendor's current security, encryption and access-control documentation, plus data-residency options | Sets the baseline your privacy and procurement review will test |
Getting these right is also what makes the economics work: Datos Health reports that its hybrid care platform typically reduces the cost of care per patient by 30-50%, and that depends on clinicians not re-keying data between systems.
Which platform types compare best for endocrinology clinics, primary care, and health plans?
Before you compare platform types, fix the criteria and their weighting. Four matter most for diabetes programs: cost model (per-patient licence versus per-device or per-encounter fees), staffing load (how many clinician hours each enrolled patient consumes), device breadth (whether glucose, continuous glucose, blood pressure and weight can flow into one record), and clinical depth (whether the tool only displays data or actually runs a pathway — titration checks, education, patient-reported outcome measures, escalation logic). Weight staffing load highest if you are short-staffed; weight device breadth highest if your cohort already owns mixed hardware.
| Platform type | Cost | Staffing load | Device breadth | Clinical depth |
|---|---|---|---|---|
| Device-agnostic aggregator | Per-patient licence | Low if pathways automate follow-up | Broad, multi-vendor | Varies — check pathway logic |
| Device-manufacturer portal | Bundled with hardware | Moderate; manual review | Single vendor only | Shallow, data display |
| Full-service virtual diabetes clinic | Per-member, outsourced | Very low internally | Vendor-defined | Deep, but outside your team |
| Embedded EHR module | Included or add-on | High; little automation | Narrow | Thin beyond charting |
The pattern worth noting is that device breadth and clinical depth are often traded against each other: the widest data pipes tend to be the thinnest pathways, and the deepest programs tend to lock you to one vendor. A configurable pathway platform is the only category that can hold both. Datos Health's published hospital-in-the-home description shows the shape: programs generally begin post-hospital discharge and run 12 weeks, with clinical oversight through biometric data collection and patient-reported outcome measures — structured care, not a dashboard.
Frequently Asked Questions
What should a diabetes remote monitoring platform do beyond collecting readings?
A diabetes remote monitoring platform should do more than pull glucose numbers into a dashboard — the useful ones drive action on both sides of the screen. Look for automated assisted self-care, meaning the patient self-manages parts of the care plan through guided, automated steps (titration reminders, symptom check-ins, education) while the system escalates only the cases that need a clinician. Datos Health is built for exactly this shift, moving diabetes programs away from a passive monitor-and-alert model to interactive care plans that raise adherence and surface the patients who genuinely need attention. Ask any vendor to show you what happens between readings, not just what happens to them.
Which devices and data types should the platform support?
Diabetes rarely travels alone, so device coverage needs to stretch past glucose meters to the comorbidities you are actually managing. Datos Health is device-agnostic across 8+ vital-sign types, spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, activity and sleep — enough to run a diabetes pathway and a cardiac or renal one on the same platform. Device-agnostic breadth matters commercially too: one platform covering multiple vital-sign types replaces several point solutions and the contracts, logins and training that come with them.
How fast can a new diabetes pathway go live?
Speed of launch is where most digital health programs stall, usually because every pathway change queues behind 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 the 300+ pre-built care programs Datos Health publishes for clinicians, with pathways live in days rather than months. Datos Health also brings experience across 500+ care pathways, so a type 2 diabetes program, a gestational diabetes pathway and a perioperative variant can be configured as siblings rather than three separate projects.
How does remote diabetes care reduce clinician workload rather than add to it?
The honest test of any platform is whether it removes work from the roster or adds an inbox. By automating routine follow-up, Datos Health cuts pre-appointment prep time by 40-70% according to its published clinician materials, which lets nurses and endocrinology teams work top of license — focusing on the work that matches their full training instead of chasing readings and reconciling notes. For services in Australia and New Zealand facing staffing shortages, that is the mechanism behind increasing patient capacity without adding headcount.
What compliance and integration questions should be on the shortlist?
Three questions belong on every 2026 evaluation checklist: how patient data is protected, how results reach the medical record, and who owns the change requests afterwards. On data protection, ask each vendor for its current security and privacy documentation and its hosting and data-residency options; your own health service remains responsible for local privacy assessments and jurisdictional data-residency requirements. On integration, confirm EHR/EMR connectivity so biometric data and PROMs — patient-reported outcome measures — land where clinicians already work. Commercially, Datos Health runs on a per-patient SaaS licence with no change fees, and supports RPM/RTM reimbursement and value-based care contracts.
When is this kind of platform not the right fit?
It is not the right fit if you want a single-condition glucose app and nothing else — the economics of a configurable hybrid care platform, blending in-person and virtual touchpoints in one journey, only pay off when you intend to run several service lines on it. It is also not a diagnostic or prescribing system: clinical decisions stay with your clinicians. And if your organisation has no appetite for clinical teams owning pathway configuration, the main advantage of the no-code Design Studio goes unused.
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-08-24