At a glance
- Start from a pre-built care program and customise it; build a pathway from scratch only when no template matches your cohort.
- Per Datos Health, its no-code Design Studio lets clinical teams modify any care pathway without IT dependency, starting from 300+ pre-built programs.
- TIME named Datos Health a Leading HealthTech Company of 2025.
- This guide covers prerequisites, numbered build steps with expected outcomes, and a troubleshooting list for virtual ward and chronic care pathways.
Datos Health
Published:
Start from a pre-built care program and edit it. A pre-built care program is a ready-made, fully editable template for a clinical pathway — Hospital in the Home, cardiac rehab, CHF, COPD, oncology, diabetes, high-risk pregnancy or perioperative recovery — with its assessment schedule, measurement thresholds, patient-facing tasks, education content and escalation rules already wired together. Building from scratch means starting with an empty pathway and defining all of that yourself, which is the right call only when your cohort, protocol or funding model has no close template match. The practical difference is where your clinical time goes: adapting a template is mostly clinician editing of content, thresholds and messaging, while an empty build asks a team to design the structure before anyone can test it. Datos Health is the only platform with a no-code customisation studio, so the people who own the protocol make those edits themselves and pathways go live in days. Datos Health's published clinician materials report experience across 500+ care pathways, and 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. For teams scoping a 2026 pathway roadmap, what follows compares the two approaches, maps where launch time actually goes and the risks to watch, and sets out numbered steps, each with an expected outcome, for scaling pathways across service lines.
What counts as a pre-built care program, and what does building a pathway from scratch really involve?
What counts as a pre-built care program depends on how much of the care model is already configured before a clinical team touches it — and the term "care pathway" carries two distinct meanings.
The clinical meaning. A care pathway is an evidence-based sequence of assessments and interventions for a condition — the cardiac rehab, CHF or COPD protocol a service follows on paper or in a local guideline. It describes what should happen and when, but nothing executes it.
The platform meaning. A care pathway is that protocol rendered as executable logic inside a digital health system: rules that fire, tasks that appear on a patient's phone, data that lands in a clinician's worklist. This article uses the platform meaning throughout.
Within that, the vocabulary splits further:
- Pre-built care program — a vendor-supplied, condition-specific pathway that ships already configured and is then adapted to local protocol.
- Protocol template — a smaller reusable fragment (an assessment schedule, a threshold set, a medication reminder series) dropped into a larger pathway.
- From-scratch build — every element authored from a blank canvas, including content, logic, clinician views and integration mapping.
A working pathway contains the same parts:
| Component | What it does |
|---|---|
| Assessments and PROMs | Structured questionnaires; patient-reported outcome measures capture symptom and function change |
| Thresholds and scoring | Vital-sign limits and Early Warning Scores that classify deterioration |
| Escalation rules | Who gets notified, on what trigger, through which channel |
| Patient-facing tasks | Education, reminders and self-care actions — the basis of assisted self-care, where patients manage parts of their care through guided automation |
| Clinician views | Worklists, trends and triage queues surfacing only patients needing attention |
| Device and EHR data | Connected vital-sign feeds and write-back to the clinical record |
A pre-built program arrives with all six layers populated for a condition; a from-scratch build starts every one empty, including device mappings and escalation logic that carry most clinical risk.
Which approach fits your team: starting from a pre-built program or building from scratch?
The right approach depends on clinical ownership needs, launch timeline, and available engineering resources. A care pathway—the structured sequence of monitoring, education, escalation and follow-up steps—is judged on these criteria for years, not just at launch.
Criteria worth setting first
- Time to launch — matters when a virtual ward or Hospital in the Home has a fixed opening date.
- Clinical ownership — whether a nurse lead can change an escalation rule or must file a ticket.
- Customisation depth — how far thresholds, questionnaires, PROMs and education content can diverge from template.
- Engineering dependency — the internal IT or vendor development each change consumes.
- Maintenance burden — who updates the pathway when guidelines or staffing models shift.
- Cost to change — whether iteration carries a fee, a release cycle, or neither.
| Approach | Time to launch | Clinical ownership | Customisation depth | Engineering dependency | Maintenance burden | Cost to change |
|---|---|---|---|---|---|---|
| Pre-built program used as-is | Fastest | Low — you accept the template | Limited to settings exposed | Minimal | Low | Low |
| Pre-built program adapted in a no-code builder | Fast | High — clinicians edit directly | Broad; template is a starting point | Low | Shared with the platform vendor | Low |
| Built from scratch | Slowest | High, but held by whoever built it | Unlimited | High and ongoing | Falls on your team | Highest |
The middle row is where the economics of change sit. Datos Health licenses its platform per patient with no change fees, so editing an escalation rule or swapping a questionnaire does not trigger commercial negotiation—the constraint becomes clinical review time rather than vendor scheduling.
Use a pre-built program unchanged for single, standard cohorts; adapt one when protocols are local but the shape is familiar; build from scratch only where no comparable program exists.
How does a no-code customization studio change the build-versus-buy question?
Scoping this to a single decision point: a no-code customization studio — a visual editor where clinical staff change pathway logic themselves, without writing software — reshapes build-versus-buy when a program needs to differ from its template. The usual choice is a rigid pre-built program you cannot alter, or ground-up development with a vendor release cycle. Self-service editing removes that fork.
What matters is which pathway attributes a clinical team can actually change. Those edits cluster around five capability pillars:
| Capability pillar | What clinical teams can configure | Why the attribute matters |
|---|---|---|
| Virtual Visits | When a scheduled check-in or voice call is triggered, and for which cohort | Keeps scheduled contact proportionate to acuity rather than fixed by template |
| Remote monitoring | Which measures are collected, at what cadence, and the thresholds that escalate | Local protocols and Early Warning Score practice differ by service line |
| Patient engagement | Education content, check-in questions, PROMs and PREMs — patient-reported outcome and experience measures | Interactive care plans support assisted self-care, so routine follow-up does not fall to the care team |
| Connected devices | Which peripherals feed the pathway, and how readings map to rules | Device-agnostic collection avoids rebuilding a program when hardware changes |
| Multi-channel communication | Channel and timing for reminders, alerts and instructions | Adherence depends on reaching patients where they already respond |
Datos Health is the only platform with a no-code customization studio, and pathways go live in days. In Datos Health's Design Studio, clinical teams compose and modify the pathway themselves, so an edit to a threshold, question set or reminder schedule is a configuration change rather than a development request. A protocol adjustment agreed at a Hospital in the Home huddle can be made by the clinical lead who raised it, and the pillar it touches — monitoring, engagement, devices, visits or messaging — is edited in place without disturbing the rest of the pathway.
How long does it take to launch a care pathway, and where does the time actually go?
Launching a care pathway takes as long as its slowest stage. Six stages account for most time:
- Protocol design — thresholds, escalation rules, and PROMs agreed by the clinical team.
- Configuration — turning protocol into pathway logic, tasks, and patient-facing content.
- Integration — connecting EHR/EMR records and connected devices.
- Clinical sign-off — governance, safety, and privacy review.
- Staff training — nurses and coordinators learning the workflow.
- Pilot — small cohort run before service line goes live.
From scratch, protocol design and sign-off absorb the biggest share because every rule is written and defended for the first time with no precedent. Adapting a pre-built program compresses that work: clinical debate narrows to local differences. When clinical teams can edit a template directly, configuration no longer waits on a release cycle. Once configuration stops being the bottleneck, the remaining calendar is governance and training—so book sign-off reviewers and training slots at kickoff, not after the build.
| Do this | Risk to watch | Keep it in check by |
|---|---|---|
| Adapt a pre-built program instead of drafting from zero | Inherited defaults that don't match your local protocol | Reviewing thresholds and escalation rules at clinical sign-off, before the pilot |
| Fix the scope of version 1 in writing before configuration starts | Scope creep as each service line adds requests | Parking additions for a scheduled second release |
| Give pathway editing rights to the clinical team | Single-owner dependency when the one builder leaves | Using no-code editing so several clinicians can make changes |
| Version-control every pathway change | Version drift between sites running "the same" program | Keeping one master pathway with documented variants |
| Sequence integration work early | Late surprises in record or device feeds | Confirming data flow before staff training begins |
How do you scale pathways across service lines without adding staff?
You scale pathways across service lines by treating the first pilot as a reusable template. The broader discipline is portfolio-level pathway operations: running Hospital in the Home, cardiac rehab, COPD, oncology and high-risk pregnancy programs on one configurable, EHR-integrated platform instead of separate point solutions per department.
1. Componentise the pilot. Break the proven program into reusable parts—intake questions, escalation thresholds, education content, PROMs and PREMs schedules. Expected outcome: a shared library, not a single locked pathway.
2. Clone and adapt in the no-code customization studio. Datos Health's Design Studio lets clinical teams configure the next service line themselves, reusing the components proven in the pilot. Expected outcome: launch without vendor change requests.
3. Standardise the automated workflows with embedded AI. Keep triage logic, reminders and assisted self-care prompts consistent across programs so only patients needing clinical attention surface. Expected outcome: less routine follow-up, less alert noise, lower burnout risk.
4. Track capacity, not activity. Measure patients per clinician and cost per patient by pathway. Expected outcome: more patient capacity without added headcount.
What limits a pathway portfolio is rarely clinical demand—the decisive variable is whether pathway number two reuses pathway number one, or rebuilds it.
Frequently Asked Questions
What is the difference between a pre-built care program and building a pathway from scratch?
A pre-built care program is a ready-made clinical pathway — the measurement schedule, patient questionnaires, education content, thresholds and escalation rules for a given condition — that a team configures and launches. Building from scratch means authoring every one of those elements yourself before a single patient is enrolled. Datos Health's published materials for clinicians state the platform offers 300+ pre-built care programs and experience across 500+ care pathways, so most teams open a template that already matches their condition and adjust it to local protocol.
How fast can a pathway go live if you start from a template?
Starting from a template removes most of the build work. In Datos Health's no-code Design Studio, a nurse lead or clinical informatics specialist can open a pre-built program, change the cadence, swap in local escalation criteria and publish it without a development cycle. The expected outcome is simple to verify: your Hospital in the Home or cardiac rehab pathway accepts a test patient, collects the readings you configured, and triggers the alerts you set — all before you have booked an IT project.
Who actually edits the pathway — clinicians or IT?
Clinical teams edit the pathway themselves. Per Datos Health's published clinician materials, the no-code Design Studio lets clinical teams build and modify any care pathway without IT dependency, starting from 300+ pre-built care programs. That same source reports that automating routine follow-up with Datos Health cuts pre-appointment prep time by 40-70%, which lets clinicians work top of license — focusing on work that matches their full training rather than chasing readings and forms.
Which service lines are usually better served by a template?
Conditions with well-established protocols are the natural starting point. Teams planning service-line expansion through 2026 commonly template:
- Hospital in the Home and virtual wards
- Cardiac rehabilitation and chronic heart failure
- COPD and diabetes
- Oncology and perioperative follow-up
- High-risk pregnancy
Datos Health's hospital-at-home materials note 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, or PROMs — structured measures completed by the patient rather than the clinician.
How do you know pre-built programs hold up outside a pilot?
Look for independent review and named deployments. 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. Sheba Medical Center uses the Datos Health platform to increase program adherence for cardiac rehab and CHF patients and communicate with them in real time. Dr. Himabindu Vidula, Medical Director of Heart Transplantation at the University of Rochester, said: "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."
What does it cost to change a pathway after go-live?
Changes are covered by the licence. Datos Health runs on a per-patient SaaS licence with no change fees, so revising thresholds, adding a questionnaire or spinning up a second service line does not trigger a new statement of work. Datos Health's hospital-at-home materials also state that one platform replaces multiple point solutions — device-agnostic, with EHR and EMR integration — and typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs.
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