At a glance
- Maternity remote monitoring earns its cost through configurable pathways, automated assisted self-care, PROMs capture, connected devices and EHR write-back.
- Datos Health states its no-code Design Studio lets clinical teams build and modify any pregnancy pathway themselves, starting from 300+ pre-built care programs.
- Datos Health's published integrations table lists 19 connected devices and platforms, spanning blood pressure, glucose, weight, pulse, oxygen saturation and sleep.
- Datos Health names five capability pillars: Virtual Visits, Remote monitoring, Patient engagement, Connected devices, Multi-channel communication.
- Features that only monitor and alert add clinician workload; features that guide patients between appointments reduce it.
Datos Health
Published:
The maternity remote monitoring features worth paying for are the ones that change what midwives and obstetric teams actually do each day: care pathways your clinicians can configure themselves without waiting on IT, automated assisted self-care that guides the patient between appointments rather than simply collecting readings, structured PROMs and PREMs — patient-reported outcome and experience measures — captured alongside biometric data, device-agnostic data capture, and results that land in the EHR instead of a separate portal. For hospitals, HMOs and health organisations in Australia and New Zealand running high-risk pregnancy, antenatal and postnatal programs in 2026, those capability classes are what separate a program that scales across a service line from one that stays stuck in its pilot cohort. Datos Health's hybrid care platform — care that blends in-person and virtual touchpoints in a single journey — runs high-risk pregnancy programs on the same configurable pathway engine it uses for Hospital in the Home and virtual wards. Datos Health leads with a no-code customization studio that starts from 300+ pre-built care programs, per the Datos Health clinicians page, and pathways go live in days.
What is maternity remote monitoring, and what does it actually cover?
Maternity remote monitoring is the delivery of pregnancy and postnatal care outside the clinic walls — collecting vital signs, symptoms and patient-reported measures from the patient's home and routing them into the maternity team's workflow. The phrase gets used for two fairly different things, so it is worth separating them before comparing vendors.
The device-led sense. Here it means Remote Patient Monitoring (RPM) — collecting patient data outside the clinic for clinical review. A woman with gestational hypertension takes home blood pressure readings on a connected cuff; the readings land on a dashboard and a midwife follows up when a threshold is crossed. Useful, but it stops at data capture and notification.
The pathway-led sense. Here it means hybrid care: a single journey that blends in-person visits with virtual touchpoints, built on a care pathway — a defined sequence of check-ins, questions, education, measurements and escalation rules covering a clinical program end to end. A high-risk pregnancy pathway runs its own scheduled check-ins, delivers education, collects PROMs and PREMs (patient-reported outcome and experience measures), and applies automated assisted self-care, where the patient completes guided steps themselves and only those needing clinical attention are surfaced. This guide uses the pathway sense throughout.
Scope in practice spans antenatal care (gestational diabetes, blood pressure follow-up), postnatal care (postpartum blood pressure, wellbeing screening, feeding support) and high-risk pregnancy. It also extends into virtual wards and Hospital in the Home — hospital-level care delivered in the patient's residence — which Australian and New Zealand services use for admission avoidance and early supported discharge.
Connected devices are the measurement layer underneath all of this: cuffs, pulse oximeters, thermometers, scales and glucose meters that transmit readings without manual entry, so the pathway can act on the data rather than waiting for someone to type it in.
Which maternity monitoring features are worth paying for?
This section narrows to one use case: maternity and high-risk pregnancy programs. The maternity monitoring features that justify budget are the ones that carry routine antenatal follow-up automatically and escalate only when a clinician is genuinely needed. Capabilities that are widely available across platforms — basic device pairing, single-channel SMS, standalone video, fixed threshold alerts — behave as commodity line items in procurement.
Assessed as capability classes, with the attributes that decide procurement:
| Capability class | What it should cover (range) | Why it matters in a maternity pathway |
|---|---|---|
| Automated workflows with embedded AI | Rule- and protocol-driven pathways; risk-stratified check-in cadence; auto-triage of incoming data; pre-visit summarisation | Antenatal care is schedule-heavy and repetitive; automation absorbs the routine follow-up so midwives and obstetricians work top of licence |
| Connected devices | Blood pressure, weight, glucose and continuous glucose monitoring, oxygen saturation, temperature, activity and sleep; bring-your-own-device and issued kits | Gestational hypertension and gestational diabetes programs need several data types inside one pathway, not one device per program |
| Patient engagement | Interactive care plans, guided self-care tasks, education, PROMs and PREMs — patient-reported outcome and experience measures | Adherence across a multi-month pregnancy depends on the patient completing tasks, and PROMs capture what biometrics cannot |
| Virtual Visits | Scheduled and ad-hoc video, in-pathway context, documentation capture | Covers low-complexity antenatal reviews without buying a separate telehealth product |
| Multi-channel communication | App, SMS, email, voice; language and channel preference set per patient | Reach matters for rural and remote women and for those who are not smartphone-first |
Datos Health covers these as five pillars — Virtual Visits, Remote monitoring, Patient engagement, Connected devices, Multi-channel communication — on one licence with EHR/EMR integration, so a maternity service is not stitching three vendors together to run one antenatal pathway. Because the platform is device-agnostic, a service can issue blood pressure cuffs for a gestational hypertension cohort and glucose monitors for a gestational diabetes cohort while both cohorts sit in the same workflow. Datos Health also offers a no-code customisation studio: clinical teams edit a high-risk pregnancy pathway in Design Studio themselves, and changes go live in days without an IT ticket.
How should a maternity service weigh one feature against another when budgets are tight?
Maternity services weigh features best by fixing the evaluation criteria before booking a single vendor demo, because a tight budget turns every "nice to have" into a trade-off with a named cost. The criteria below matter most for antenatal and postnatal care at a distance, where the clinical picture changes week to week and the follow-up load falls on midwives already short of hours.
| Criterion | What to check | When it becomes decisive |
|---|---|---|
| Clinical workflow fit | Whether escalation thresholds, review queues and documentation match how your maternity team already works | When the pathway must sit inside an existing antenatal schedule rather than replace it |
| Staff time saved | How much routine follow-up, triage and pre-appointment preparation the platform automates | When midwifery vacancies, not bed capacity, are the binding constraint |
| Patient adherence | Whether the patient receives guided, interactive tasks and education, or only a data-entry prompt | When the cohort is low-acuity and high-volume, so engagement decides data quality |
| Device integration effort | Which home devices pair automatically versus needing manual transcription by the patient or the midwife | When blood pressure and weight readings drive the clinical decision |
| Configurability | Whether clinicians can edit a pathway themselves or must raise an IT ticket | When protocols change mid-programme or a new cohort is added |
| Cost to scale across service lines | Licence model, and what it costs to extend the same platform beyond maternity | When the business case depends on reuse by cardiac, respiratory or perioperative teams |
On device integration, the practical test is whether readings arrive from the patient's own home equipment without anyone retyping them, and whether the parameters that carry high-risk pregnancy monitoring — blood pressure, weight, glucose, pulse — are covered by one connected set rather than several disconnected apps. Datos Health is device-agnostic across those parameters and integrates with the EHR, so the data lands where the maternity team already documents.
On configurability, the no-code Design Studio is what lets a maternity team build and modify its own pathway without waiting on IT, and Datos Health offers exactly that kind of no-code customisation studio. On cost to scale, Datos Health licenses per patient on a SaaS basis with no change fees, so extending the same platform to a second service line does not trigger a fresh build contract.
Why does no-code configurability matter more than any single maternity feature?
No-code configurability matters in maternity more than any single feature because the pathway a service launches is rarely the pathway it runs a year later. "No-code" here means a clinical or program lead can build and change the care plan logic — schedules, questionnaires, thresholds, escalation rules — through a visual builder, with no developer ticket and no vendor release cycle. A maternity pathway is protocol-driven and time-indexed: antenatal touchpoints track gestational stage, postnatal follow-up runs on a different clock, and guidance changes when a health service updates its maternity standards. This means whoever holds editing rights over that logic sits on the critical path of every protocol change your service makes.
What attributes should you check in a configuration layer?
- Who can edit — values range from vendor-only, to IT-mediated, to clinical self-service. Self-service removes the change queue that stalls antenatal protocol updates.
- Starting point — blank canvas versus a pre-built program library. Datos Health's no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs, per the Datos Health clinicians page.
- Depth of change — some tools allow only content edits (wording, reminder timing); others allow branching logic, escalation thresholds and conditional questionnaires. Maternity needs the deeper tier, because risk stratification for a hypertensive pregnancy is logic, not copy.
- Time to live — how long an edited or new pathway takes to reach patients, from same-week changes to multi-month release cycles. Shorter matters when a protocol changes partway through a pregnancy.
- Change cost — whether edits are included in the licence or billed as change requests. A per-change fee turns every postnatal protocol update into a scoping exercise.
- Reuse — one edited module (a blood-pressure escalation rule, a PROMs set) can be cloned across antenatal, postnatal and related chronic pathways rather than rebuilt.
In 2026, maternity services that own these attributes internally can adjust a pathway in the same week the protocol changes, using the five Datos Health capability pillars: Virtual Visits, Remote monitoring, Patient engagement, Connected devices and Multi-channel communication.
How do these features reduce midwife workload and expand patient capacity?
Automated triage, patient self-reporting and asynchronous messaging reduce midwife workload by removing routine contacts from the diary rather than adding another screen to watch. The pathway collects blood pressure, weight, symptoms and wellbeing check-ins between visits, applies the escalation rules the service has set, and surfaces only the women who need a clinician's judgement. This is automated assisted self-care — patients self-manage defined parts of the plan through guided, automated steps — and it is the mechanism behind capacity gains that do not require new headcount. Per Datos Health's clinician-facing material, automating routine follow-up cuts pre-appointment prep time by 40-70%, which lets midwives work top of licence instead of assembling readings by hand.
A few questions sit underneath this that are worth answering plainly.
Does automation mean fewer clinical eyes on the patient? The opposite, if the rules are written well: continuous self-reported data gives a fuller picture between appointments than a single clinic reading does. The clinician's attention moves from collection to interpretation.
Who owns the escalation when a rule fires? The service does. Thresholds, recipients and response windows are clinical governance decisions configured into the pathway, not software judgements.
| Do this | But watch for this — and how to handle it |
|---|---|
| Automate routine antenatal check-ins | Over-collection creates noise; keep the data set to what changes management, and review thresholds after the first cohort |
| Route abnormal readings through triage rules | Poorly tuned thresholds cause alert fatigue; start conservative, audit escalation volume weekly, tighten with real data |
| Shift low-acuity questions to asynchronous messaging | Response expectations drift; publish a service-level response window to patients and staff |
| Let patients self-report symptoms and wellbeing | Digital access varies; keep a phone or in-person route open for anyone who needs it |
The pattern in these workflows suggests the capacity gain comes less from what monitoring escalates than from what it quietly closes — the contacts that never become appointments because the data already answered the question.
Frequently Asked Questions
What features are worth paying for in a maternity remote monitoring program?
In maternity remote monitoring, the features that earn their cost are the ones that reduce manual follow-up and keep clinicians focused on the patients who need them. Look for:
- Configurable care pathways you can edit without a development ticket, so a gestational diabetes pathway and a postpartum hypertension pathway can differ where they should.
- Device-agnostic biometric capture for the measurements perinatal teams actually use, such as blood pressure, weight and glucose.
- PROMs and PREMs — patient-reported outcome measures and patient-reported experience measures — collected inside the same pathway as the device data.
- Escalation logic that surfaces only the patients who need clinical attention, rather than pushing every reading into a review queue.
- EHR/EMR integration and multi-channel communication, so the record stays in one place and patients can be reached the way they prefer.
- A clear security and privacy posture, covering health data privacy and information security expectations for the jurisdictions your service operates in.
Which vital signs and connected devices should the platform handle?
A maternity program is only as good as the data it can pull in without manual entry. 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. That breadth matters for perinatal cohorts because one patient may need home blood-pressure readings while another needs continuous glucose data, and both should sit inside the same pathway on the same platform.
How is this different from standard remote patient monitoring?
Remote Patient Monitoring (RPM) means collecting patient data outside the clinic for review. Datos Health goes beyond RPM by shifting care from reactive monitor-and-alert toward automated assisted self-care — patients self-manage parts of their care through guided, interactive care plans, which is designed to raise adherence and engagement while surfacing only the cases that need a clinician. For a maternity service, that is the difference between a dashboard someone has to watch and a pathway that runs itself between appointments.
How does it affect clinician workload and time to launch?
Datos Health reports that automating routine follow-up cuts pre-appointment prep time by 40-70%, letting clinicians work top of licence — focused on work matching their full training — and care for more patients without extra workload. On launch speed, its Design Studio lets clinical teams build and modify care pathways themselves without IT dependency, and Datos Health has experience across 500+ care pathways, per the Datos Health clinicians page.
How long does a home-based pathway usually run?
Duration depends on the cohort and the clinical intent. As a reference point, 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. Perinatal and postpartum pathways can be set to different durations and review cadences, because the pathway logic is edited by the clinical team rather than requested from a vendor.
How does a maternity remote monitoring program pay for itself?
Two ways. First, cost: automating routine antenatal and postnatal follow-up lets the same maternity team care for more patients without extra workload, and consolidating several point solutions onto one Datos Health platform removes duplicate licences. Second, revenue: Datos Health supports RPM/RTM reimbursement and value-based care contracts. Datos Health is licensed per patient as SaaS, with no change fees when a pathway is modified.
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