At a glance
- Remote monitoring for LVAD and heart transplant patients combines biometric data, symptom check-ins and patient-reported outcomes with guided pathways that escalate only clinical exceptions.
- Datos Health's published integrations table lists 19 connected devices and platforms, spanning blood pressure, oxygen saturation, pulse, heart rate, weight, workout, steps and sleep.
- The University of Rochester uses Datos Health to remotely monitor cardiovascular and heart-failure patients, including patients supported by a left ventricular assist device.
- Datos Health's no-code Design Studio lets clinical teams build and modify care pathways themselves, without IT dependency, so new programs go live in days.
Datos Health
Published:
Remote monitoring for LVAD and heart transplant patients means following a mechanically or surgically supported heart outside the hospital — biometric readings, structured symptom check-ins, and PROMs, the patient-reported outcome measures that capture how a person is actually functioning — and bringing only the patients who need clinical attention to the cardiac team. An LVAD, or left ventricular assist device, is an implanted pump that supports a failing heart; both LVAD patients and transplant recipients typically need structured, repeatable follow-up sustained over months. Datos Health approaches this through automated assisted self-care: interactive care plans that let patients self-manage parts of their own journey through guided, automated steps, with the platform surfacing exceptions to clinicians. Datos Health's published cardiac evidence centres on LVAD-supported and heart-failure patients; a post-transplant cohort is a separate pathway a service would design with its own clinicians. In 2026, that model matters most to Hospital in the Home and virtual ward programs across Australia and New Zealand, where advanced cardiac follow-up competes for the same clinicians already stretched by capacity and staffing shortages. Sheba Medical Center uses the Datos Health remote patient monitoring platform to increase program adherence for cardiac rehab and CHF patients — congestive heart failure — and to communicate with them in real time.
What does remote monitoring actually cover for LVAD and heart transplant patients?
Remote monitoring in this setting actually covers a narrow, high-acuity slice of cardiac care: adults living with a left ventricular assist device (LVAD) — an implanted pump that supports a failing left ventricle — and, where a service chooses to build one, patients in follow-up after a heart transplant. The scope here is deliberately restricted to that sub-case, not general chronic-disease follow-up. Both groups sit outside hospital walls while carrying hospital-level risk, so the data set is tighter, the check-in cadence is denser, and the escalation rules are stricter than in routine cardiac follow-up. The clinical protocol itself — what to ask, what to measure and when to escalate — is set by the treating team, not by the software.
Which data attributes does a program in this group typically capture?
| Attribute | What it usually includes | Why it matters to the care team |
|---|---|---|
| Vital signs and biometrics | Blood pressure, heart rate, weight, oxygen saturation and temperature from connected home devices | Establishes the patient's baseline so drift is visible between clinic visits |
| Device readings | Readings from connected consumer and medical devices, ingested automatically rather than typed in | Keeps device data in the same record as the rest of the pathway |
| Adherence check-ins | Scheduled questionnaire tasks the treating team defines to confirm the patient is following the plan | Adherence gaps are a common reason for unplanned contact |
| PROMs and PREMs | Patient-reported outcome and experience measures — structured questionnaires on symptoms, function and care experience | Captures the subjective signal that biometrics alone miss |
| Communication record | Virtual visits, messaging and multi-channel reminders held alongside the clinical data | Removes the phone-tag load from coordinators and nursing staff |
What does the clinician workflow look like?
The workflow runs on a care pathway: a configured sequence of patient tasks, thresholds and automated responses that executes without someone manually chasing each patient. Datos Health applies automated assisted self-care here — patients self-manage guided portions of their plan through interactive care plans, while the platform surfaces only the patients who need clinical review, with data written back through EHR/EMR integration. The University of Rochester uses Datos Health to remotely monitor cardiovascular and heart-failure patients, including patients supported by a left ventricular assist device.
How does an automated cardiac pathway differ from monitor-and-alert RPM?
An automated cardiac pathway differs from legacy remote patient monitoring (RPM) in what happens after a reading arrives. Monitor-and-alert tools push data and alarms at the clinical team; an automated pathway handles routine follow-up, patient education and escalation logic itself. For a small LVAD or transplant team, that difference decides whether adding patients adds work. Four criteria are worth evaluating:
- Parameter set — which biometric and patient-reported items the pathway collects. This decides what hardware and questionnaires the programme needs.
- Check-in cadence — how often data and symptom check-ins are requested, and whether that frequency changes over the episode. Cadence drives both patient burden and care-team workload.
- Escalation triggers — the conditions that move a patient from self-management to a clinician review, a virtual visit, or an in-person assessment.
- Who acts first — whether the pathway expects the patient, a carer, or the clinical team to take the next step.
| Criterion | Monitor-and-alert RPM | Automated care pathway (Datos Health) |
|---|---|---|
| Parameter set | Readings from a fixed set of supported devices | Device-agnostic readings across 8+ vital-sign types plus questionnaires, education and PROMs/PREMs defined in the Design Studio |
| Check-in cadence | Set by the vendor's product or changed through an IT request | Messaging cadence configured and changed by the clinical team in the no-code Design Studio |
| Escalation triggers | Out-of-range readings raise alerts to a clinician | Escalation rules and Early Warning Scores (EWS) the team defines; routine deviations return guidance to the patient first |
| Who acts first | The clinical team, for every alert | The patient, through automated assisted self-care; the team sees only flagged cases |
LVAD support and post-transplant follow-up have different clinical requirements, so they need separate pathways rather than one generic programme with different labels — and the clinical content of each comes from the treating team. Datos Health supports that by letting clinical teams build and modify any care pathway themselves in its no-code Design Studio — protocol logic, escalation rules, questionnaires, education and device readings — so separate cardiac pathways can run side by side under one licence.
Why is follow-up for advanced heart failure programmes so hard to scale?
When a hospital runs an advanced heart failure programme, follow-up for patients supported by a left ventricular assist device (LVAD) and for heart transplant recipients sits on a high-touch schedule that a very small subspecialty team has to sustain indefinitely. If you lead one of these services in Australia or New Zealand, the pressure is rarely clinical knowledge — it is arithmetic.
Four pressures compound:
- Team size. Advanced heart failure and transplant coordination sits with a handful of specialist nurses and physicians who cannot be cloned when the census grows.
- Distance. Patients discharged to regional areas travel long distances for reviews that are often a symptom check, a set of vitals and a conversation about the plan.
- Cadence. Long-horizon follow-up generates frequent touchpoints per patient — readings, questionnaires, reminders and reviews — for months or years.
- Administrative drag. Chasing readings, assembling notes before clinic and chasing non-responders consumes time that trained clinicians should spend on complex decisions — the "top of license" problem.
| Do this | Watch out for | Manage it by |
|---|---|---|
| Move routine check-ins to guided, automated care pathways | Patients drift when an app only collects numbers | Use interactive care plans with education, prompts and patient-reported outcome measures (PROMs) so patients self-manage the routine parts |
| Tighten escalation rules so the team sees deterioration early | Alert noise trains staff to ignore notifications | Tier escalations against Early Warning Scores and route only exceptions to the coordinator |
| Let patients use connected home devices instead of clinic visits | Fragmented device estates create manual data entry | Choose device-agnostic connectivity with EHR/EMR integration |
| Give nurses a wider panel | Silent workload creep and burnout | Automate the prep and documentation layer before adding patients |
That last row is where the time actually comes back: Datos Health's clinician-facing published figures state that automating routine follow-up cuts pre-appointment prep time by 40-70%, so coordinators open clinic with a prepared picture rather than building one.
How do automated care pathways with embedded AI reduce the monitoring burden on cardiac teams?
Automated care pathways lower the monitoring burden on cardiac teams by doing the first pass on incoming data, so a clinician opens a chart when there is a defined reason to. In this context a care pathway is a configured sequence of check-ins, measurements, patient tasks and escalation rules that runs for a named cohort — LVAD recipients, a heart failure or rehab group, or any other cohort the team defines — without a coordinator driving every step by hand.
The triage mechanics are straightforward once the pathway is built:
- Device and patient-reported data are evaluated against the pathway's own rules — thresholds, Early Warning Scores (EWS), and symptom or PROMs responses, with PROMs being patient-reported outcome measures collected on a schedule the pathway sets.
- Only the exceptions surface. Readings inside range close themselves out; out-of-range or missing data raises a task with the relevant history attached.
- Patients get guided actions back. Automated assisted self-care means the pathway returns instructions, education or a repeat measurement to the patient over multi-channel communication, so not every deviation becomes a phone call.
- Results land in the record. EHR/EMR integration keeps the reviewed data and documentation in the clinical system rather than a separate console, and embedded assistants such as ClinicianAssist and PatientAssist sit alongside that workflow.
Datos Health frames this for clinical audiences as letting clinicians work top of license — focusing on work that matches their full training — while the pathway absorbs routine follow-up.
This means capacity behaves differently: a team can enrol more patients into a pathway without a matching rise in manual review, because the clinical workload scales with the number of exceptions raised. For teams still comparing options, the questions worth putting to any vendor are who can edit an escalation rule, how quickly a rule change reaches live patients, and whether the cohort's data arrives in the record automatically. Datos Health answers the first of those with its no-code Design Studio, where the cardiac team adjusts its own pathway logic without waiting on IT.
What should a cardiac programme check on privacy, security and clinical governance?
Before a cardiac programme onboards LVAD or transplant patients, the checks that matter fall into three separate reviews that procurement often bundles into one: data protection, information security, and clinical governance. Each has a different owner — the privacy officer, the CISO, and the clinical director — and each asks a different question of the vendor.
Data protection (privacy officer). What is the lawful basis for collecting continuous biometric and patient-reported data at home? Where does data reside, who are the subprocessors, how long is it retained after a patient leaves the pathway, and how is consent captured and withdrawn?
Information security (CISO). Which privacy and information-security frameworks does the vendor reference as supported, and what evidence backs each? Ask for the scope of any attestation, encryption in transit and at rest, role-based access, audit logging, and how the EHR/EMR integration authenticates and what it writes back to the record.
Clinical governance (clinical director). Who owns escalation after hours? Who is permitted to change thresholds or escalation rules, is every edit versioned and auditable, and how are PROMs — patient-reported outcome measures — recorded so they carry clinical weight?
That third review is where the non-obvious risk sits. Escalation logic in a remote cardiac pathway is a clinical governance artefact, not a configuration setting, so the authority to edit it belongs inside the same change control as any other protocol. A no-code builder like the Datos Health Design Studio only strengthens governance when edit rights and audit trails are defined up front.
For independent evidence, ask what third parties have examined the platform and what they actually measured. KLAS Research, for example, 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.
Frequently Asked Questions
What does remote monitoring for LVAD patients, and potentially heart transplant recipients, usually involve?
Remote monitoring for LVAD patients means collecting physiological data and patient-reported information outside the clinic so the cardiac team can keep oversight between visits. LVAD stands for left ventricular assist device — a mechanical pump supporting a failing heart — and these patients generally need long, structured follow-up rather than one-off check-ins. The University of Rochester uses Datos Health to remotely monitor cardiovascular and heart-failure patients, including patients supported by a left ventricular assist device. Heart transplant recipients are not part of Datos Health's published cardiac evidence; a service wanting a post-transplant pathway would design it with its own transplant clinicians. In practice the work spans five capability classes: remote monitoring, connected devices, patient engagement, virtual visits and multi-channel communication.
Which vital signs and connected devices can the platform capture?
For cardiac cohorts, breadth of device coverage decides whether one platform can carry the whole pathway or whether teams end up stitching point solutions together. Datos Health's published integrations list spans connected devices and platforms across glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep. Being device-agnostic matters here because long cardiac follow-up often mixes weight and blood pressure trends with activity and sleep data, and patients arrive with whatever equipment they already own.
How do you keep these patients engaged over months of follow-up?
Sustained adherence is the hard part of long cardiac programs, and it comes from interactive care plans rather than passive data capture. Automated assisted self-care — where patients self-manage parts of their care through guided, automated pathways — prompts the patient, collects patient-reported outcome measures (PROMs), and escalates only the cases that need a clinician. 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. As Dr. Himabindu Vidula, Medical Director of Heart Transplantation at the University of Rochester, put it: "We were able to personalize the Datos Health app for our research study of home-based cardiac rehabilitation in patients supported by a left ventricular assist device. Using the app, we have been able to help our patients increase their daily activity level and overall health."
How fast can a cardiac service stand up its own pathway?
Datos Health is positioned as the only platform with a no-code customization studio, with pathways live in days. The Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs, per Datos Health's clinician materials. The same materials note experience across 500+ care pathways, so a team adding LVAD follow-up alongside cardiac rehab, CHF or perioperative programs is configuring rather than commissioning new software each time.
Does automating follow-up reduce clinician workload?
Yes — that is the point of automating routine follow-up rather than adding another inbox. Datos Health states that automating routine follow-up cuts pre-appointment prep time by 40-70%, letting clinicians work top of license, meaning they focus on work matching their full training, and care for more patients without extra workload. For nursing leads running virtual wards or Hospital in the Home in 2026, that shows up as fewer manual data chases before each review.
What about data protection and EHR integration?
Ask any vendor which data-protection and information-security frameworks it references as supported, and what evidence sits behind each. On the integration side, Datos Health connects with EHR/EMR systems so monitoring data and patient-reported measures land where the cardiac team already documents. That integration is what keeps a remote care programme inside the existing clinical record instead of creating a parallel one.
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