300+ Pre-Built Care Programs: A Shortcut to RPM Deployment
Datos Health's catalogue of 300+ pre-built care programs is the fastest route to a working remote patient monitoring (RPM) deployment because the clinical logic, patient-facing content, escalation rules, and device workflows are already assembled — your team configures rather than builds from scratch. Instead of scoping a bespoke pathway with IT for months, a clinical lead opens the no-code Design Studio, picks a program that matches the cohort (say, CHF post-discharge or perioperative recovery), and adapts thresholds, questions, and cadence to local protocols. Datos Health has experience across 500+ care pathways, and in 2026 that library is what turns "we want to launch a virtual ward" into a project measured in days rather than quarters. The result is a shortcut that skips the two things that usually stall RPM programs: waiting for engineering capacity, and starting the clinical design conversation from a blank page.
How do 300+ pre-built care programs accelerate RPM deployment?
Pre-built care programs shorten RPM deployment because the clinical logic, patient-facing content, escalation rules, and device bindings are already assembled — teams configure rather than build from scratch. Datos Health ships a library of 300+ pre-built care programs and experience across 500+ care pathways, so a hospital standing up Hospital in the Home, cardiac rehab, CHF, COPD, oncology, diabetes, high-risk pregnancy, or perioperative follow-up starts from a working template instead of a blank canvas.
What attributes make a pre-built program deployment-ready?
Each template in the library carries a defined set of attributes that a clinical lead can inspect and adjust in the no-code Design Studio before go-live:
- Cohort and enrolment rules — which patients the pathway targets and how they enter (post-discharge, referral, risk score).
- Assessment schedule — cadence of PROMs (patient-reported outcome measures) and PREMs (patient-reported experience measures), symptom check-ins, and vitals capture.
- Connected device bindings — the pathway is pre-mapped to Datos Health's integrations across glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep, so device onboarding is a selection, not an integration project.
- Escalation logic — thresholds, Early Warning Scores, and routing rules that decide when a patient becomes a task for a clinician versus continuing in automated assisted self-care.
- Patient-facing content — education, reminders, and interactive care plan steps in the CareApp.
- EHR/EMR write-back — where readings, alerts, and PROMs land in the record.
Why does this collapse the launch timeline?
Because these attributes ship as sensible defaults, the deployment conversation shifts from "how do we build a CHF pathway?" to "which parts of this CHF pathway do we adapt for our service?" Clinical teams edit thresholds, swap devices, or rewrite patient messages themselves in the Design Studio, without waiting on an IT backlog. In 2026 that difference — configuration in days rather than a multi-quarter build — is often what decides whether a virtual ward program actually goes live or stalls in scoping.
What conditions and care pathways do pre-built RPM programs cover?
Pre-built RPM programs cover the conditions and care pathways that account for most of a health system's high-volume, high-risk patient cohorts — from chronic disease management to acute post-discharge recovery. Datos Health ships a library that clinical teams can adopt as-is or reshape in the no-code Design Studio, so a hospital does not start every pathway from a blank page.
Which chronic conditions are covered?
The chronic side of the library spans the conditions that dominate readmission and outpatient follow-up workloads: congestive heart failure (CHF), COPD, diabetes (type 1 and type 2), and oncology surveillance. Cardiac rehabilitation pathways are well-established here — Sheba Medical Center, for example, uses the platform to lift adherence for cardiac rehab and CHF cohorts and to communicate with patients in real time. The University of Rochester runs cardiovascular and heart-failure monitoring on the same platform, including patients supported by a left ventricular assist device.
Which acute and episodic pathways are covered?
Acute coverage includes Hospital in the Home and virtual ward programs, perioperative prehab and recovery, post-discharge transitions of care, and high-risk pregnancy. Datos Health's hospital-in-the-home programs generally begin post-hospital discharge and run about twelve weeks, providing clinical oversight through biometric data collection and patient-reported outcome measures (PROMs).
What attributes define each pre-built pathway?
Every program in the library exposes a consistent set of attributes clinical teams can inspect and adjust:
| Attribute | Typical values | Why it matters |
|---|---|---|
| Clinical focus | CHF, COPD, diabetes, oncology, HITH, perioperative, maternity | Matches the pathway to a service line |
| Duration | Episodic (days) through chronic (ongoing) | Sets enrolment and discharge logic |
| Data inputs | Vitals, PROMs, PREMs, symptom check-ins | Determines device and survey configuration |
| Escalation logic | Threshold alerts, Early Warning Scores, clinician review | Controls who gets notified and when |
| Patient touchpoints | Education, reminders, virtual visits, messaging | Drives adherence and self-care |
Datos Health has experience across 500+ care pathways, so most conditions a hospital or HMO needs to stand up already have a starting template in the catalogue.
Why is building RPM protocols from scratch a costly bottleneck?
When building RPM protocols from scratch, hospitals routinely underestimate how long a home-grown pathway takes to reach patients — and how much clinical risk accumulates in the gap. Every locally authored protocol is a small software project: scoping the cohort, defining thresholds, wiring devices, writing patient-facing content, mapping to the EHR, validating alerts, and running a safety review before a single patient is enrolled. Multiply that by every service line — Hospital in the Home, CHF, COPD, oncology, perioperative — and the backlog quickly outruns the innovation team's capacity.
What are the hidden costs of in-house builds?
The direct costs are visible: clinical informaticists, integration engineers, and vendor fees for point solutions. The hidden costs are worse. Pathways built once are rarely maintained, so thresholds drift from current guidelines. Alert logic authored by one clinician isn't peer-reviewed by the next, which feeds alert fatigue and inconsistent follow-up. And because each new pathway usually needs IT tickets to modify, frontline clinicians stop asking — so the programme calcifies.
How should teams weigh action against risk?
| Do this | But watch out for |
|---|---|
| Build a pathway in-house to fit local workflow | Multi-quarter timelines that miss the reimbursement window |
| Standardise thresholds across service lines | Drift from updated clinical guidelines without a maintenance owner |
| Layer point solutions per condition | Fragmented data, duplicate device contracts, and no single patient view |
| Route every abnormal reading to a clinician | Alert noise that accelerates burnout and buries the patients who truly need attention |
Highest-impact mitigation: start from a validated pathway library rather than a blank canvas, and keep authorship in clinicians' hands so updates don't queue behind IT. Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, and its no-code Design Studio lets clinical teams modify any pathway themselves without IT dependency — turning a multi-month build into a configuration exercise clinicians can own in 2026 and beyond.
How do pre-built programs compare to custom-built RPM workflows?
Let me compare pre-built care programs against custom-built RPM workflows, so clinical and digital health leaders can weigh the tradeoffs before committing.
What criteria should you use to compare the two approaches?
Before looking at options, agree on the criteria that matter. In our view, five weigh heaviest for hospitals standing up virtual wards or Hospital in the Home:
- Time-to-launch — how quickly a pathway goes from decision to live patients.
- Clinical fit — how closely the workflow reflects your protocols, escalation rules, and PROMs/PREMs (patient-reported outcome and experience measures).
- IT dependency — whether clinical teams can iterate, or every change routes through a developer queue.
- Scalability across service lines — can the same platform host cardiac rehab, CHF, COPD, oncology, high-risk pregnancy, and perioperative pathways without a rebuild each time?
- Total cost of ownership — build costs, ongoing change fees, and the cost of care per patient once live.
How do pre-built and custom-built approaches stack up on each criterion?
| Criterion | Pre-built care programs (e.g. Datos Health library) | Custom-built RPM workflow |
|---|---|---|
| Time-to-launch | Pathways live in days using a no-code Design Studio | Months of scoping, build, and validation |
| Clinical fit | Starting point from 300+ pre-built programs, then tailored by clinicians themselves | Bespoke from day one, but rebuilt whenever protocols change |
| IT dependency | Minimal — clinical teams edit pathways directly | High — every change is a ticket |
| Scalability | One platform, many service lines under one licence | Each new pathway is a new project |
| Cost profile | Datos Health's hybrid care platform typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs | Higher build and change costs; harder to forecast |
What's the verdict?
For most Australian and New Zealand health services facing capacity pressure, a pre-built-then-configured approach wins on every criterion that matters at scale — you get clinical specificity without a multi-quarter build, and you preserve the ability to keep changing pathways as evidence and reimbursement rules evolve through 2026.
What steps should a clinical team follow to deploy a pre-built RPM program?
A clinical team can move from decision to live pathway in a handful of concrete steps, and the sequence matters more than the tooling. Below is a practical deployment workflow for launching a pre-built remote patient monitoring (RPM) program on Datos Health, written for teams at the decision and early-implementation stage of their digital-care journey.
- Pick a starting template. Choose one of the 300+ pre-built care programs in Datos Health that most closely matches your cohort — CHF, COPD, cardiac rehab, post-surgical, hospital-in-the-home, high-risk pregnancy, and similar pathways ship ready to configure.
- Assemble a small clinical working group. A physician lead, a nurse champion, and a digital-health coordinator are usually enough. IT is a reviewer, not a builder — the no-code Design Studio keeps configuration in clinical hands.
- Tailor the pathway in Design Studio. Adjust vitals thresholds, questionnaires, PROMs/PREMs, patient education, escalation rules, and communication cadence. This is where local protocols and Hospital in the Home policies get encoded into the pathway.
- Map devices and integrations. Select from the connected devices and platforms Datos Health publishes across vitals such as blood pressure, oxygen saturation, glucose, weight, and heart rate, and confirm EHR/EMR data flow with your integration team.
- Define the escalation and triage model. Decide which alerts route to nursing, which trigger a virtual visit, and which the interactive care plan handles through automated assisted self-care — so clinicians only see patients who actually need attention.
- Pilot with a small cohort. Run a limited group for a short cycle, review adherence, alert volume, and clinician workload, then refine the pathway directly in Design Studio without a change-request queue.
- Scale and add pathways. Once the first program is stable, layer additional service lines onto the same platform and licence.
Frequently Asked Questions
What is a pre-built care program?
A pre-built care program is a ready-made clinical pathway — protocols, patient tasks, escalation rules, and monitoring cadence — that a team can deploy as-is or adapt. Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, covering Hospital in the Home, cardiac rehab, CHF, COPD, oncology, diabetes, high-risk pregnancy, and perioperative journeys.
How fast can we go live with a Datos Health pathway?
Because pathways start from a library rather than a blank page, clinical teams configure them in the no-code Design Studio and go live in days rather than months. There is no IT ticket queue between an idea and a running program — the same tool that clones a template also edits questions, thresholds, and reminders.
Can we modify a template, or are we locked into it?
You can modify anything. The Design Studio is a no-code builder with no peer equivalent, so nurses, care managers, and program leads change task logic, PROMs, escalation thresholds, and patient-facing content directly. Templates are a starting point, not a ceiling.
How does this go beyond traditional Remote Patient Monitoring?
Traditional RPM (Remote Patient Monitoring — collecting patient data outside the clinic for review) generates alerts and leaves the workload on clinicians. Datos Health pathways drive automated assisted self-care: patients receive guided tasks, education, and check-ins, and only exceptions surface for review. It is the difference between monitor-and-alert and a full hybrid care pathway.
Which devices and vital signs are supported out of the box?
The platform is device-agnostic. 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 most Hospital in the Home and chronic care management deployments work with kit teams already own.
Do the templates support reimbursement and value-based contracts?
Yes. Pre-built programs are structured to capture the data required for RPM and RTM billing and for value-based care measures, including PROMs and PREMs. In 2026 that matters more than ever as Australian and New Zealand health systems tie funding to outcomes and virtual ward capacity.