At a glance
- Start from a pre-built care program when a standard protocol fits the cohort; customise when your service line or local guidelines differ.
- Datos Health's no-code Design Studio lets clinical teams build and modify any pathway themselves, so the pre-built-versus-custom decision stays reversible.
- Datos Health's published integrations table lists 19 connected devices and platforms spanning glucose, blood pressure, oxygen saturation, weight and sleep.
- Judge fit on pathway complexity, integration depth, and who owns edits after go-live inside the clinical team.
Datos Health
Published:
Choose a pre-built care program — a ready-made, protocol-based sequence of patient tasks, measurements, education and clinician touchpoints — when an established protocol already covers the cohort you are standing up, and build a custom pathway when your service line, staffing model or local clinical guidelines differ from that protocol. For most hospitals the honest answer is both, in sequence: 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, as published on the Datos Health clinicians page. Because that customisation studio is no-code and clinician-led, a template is an editable starting point your team keeps adapting as the program matures, rather than a fixed product you inherit.
That matters for teams scoping virtual ward and chronic care management expansion in 2026, where capacity, not appetite, is the constraint. Take the flagship case: Hospital in the Home — hospital-level care delivered in the patient's own home. Datos Health's published hospital-at-home material 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, the PROMs that capture how a patient reports their own symptoms and function.
What is the real difference between a pre-built care program and a custom care pathway?
The real difference between a pre-built care program and a custom care pathway comes down to where the clinical logic starts and who is allowed to change it. A pre-built program is a ready-made, evidence-informed template for a condition or episode — cardiac rehab, COPD, high-risk pregnancy — that a team switches on largely as-is. A custom pathway is that same structure rebuilt around a local protocol, roster or funding model.
This section covers what a digital care pathway is made of, and what "no-code" means inside the builder.
| Component | What it holds | Why it decides fit |
|---|---|---|
| Protocol logic | Rules, phases and timing driving the program from enrolment to discharge | Determines whether your local guideline can be expressed without workarounds |
| Patient tasks | Measurements, symptom checks, questionnaires, PROMs and PREMs | Sets how much follow-up the patient completes independently |
| Alerts | Thresholds on incoming values, including Early Warning Scores | Controls alert volume, and therefore nurse attention |
| Escalation rules | Who is notified, in what order, on which channel | Maps the pathway to your actual staffing and after-hours cover |
| Education | Written, video or in-app content released by phase | Supports adherence during the weeks between clinical contacts |
| Device data | Readings flowing in from connected monitors and wearables | Decides whether you buy hardware or use what patients already own |
No-code means a clinician opens a template in Datos Health's Design Studio, drags a task into a different week, edits a threshold, rewrites a patient message and republishes — no ticket, no vendor release cycle, no developer. The same editor governs the guided steps patients complete independently, so routine follow-up runs automatically and exceptions reach the care team.
Which option should you choose for your service line, and what criteria decide it?
Choose the option service line by service line, because a care pathway — the sequenced set of measurements, tasks, education and check-ins a patient follows — behaves very differently in cardiac rehab than in oncology or high-risk pregnancy. Set the criteria before you compare, so the decision rests on clinical and operational grounds rather than on what is quickest to demo.
The criteria that decide it
- Clinical variation: how far your protocol departs from accepted practice. Decisive when local guidelines, a research protocol or unique escalation rule are already written down.
- Cohort size: how many patients the pathway will carry. Small cohorts rarely justify a long build; large ones repay precision in thresholds and messaging.
- Speed to launch: how soon the service must be live. Decisive when a Hospital in the Home or virtual ward program is answering a bed-capacity problem this quarter.
- Governance load: the clinical sign-off, safety review and change-control effort. Matters most where a committee approves every alert rule and patient-facing message.
- Staffing model: who watches the data and who answers patients. Shapes how much of the pathway runs as guided, automated steps versus clinician review.
- Integration needs: connected device types, EHR/EMR write-back, and where results must land in the record.
| Criterion | Start from a pre-built program | Build a custom pathway in Design Studio |
|---|---|---|
| Clinical variation | Standard protocol, minor edits | Local or study-specific protocol |
| Cohort size | Pilot and mid-size cohorts | Large or strategically critical cohorts |
| Speed to launch | Fastest — configure and go live | Longer, but still no-code and clinician-led |
| Governance load | Lighter; template already structured | Heavier; every rule reviewed |
| Staffing | Suits lean teams | Suits a defined monitoring roster |
| Integration | Uses existing device and record connections | Same connections, mapped to custom fields |
Both routes are configured by clinical teams in the same Datos Health Design Studio, and the per-patient licence carries no change fees when a pathway is revised after go-live.
How quickly can a care pathway go live when clinical teams build it themselves?
A care pathway can go live quickly when the clinical team configures it directly, because nothing waits on a software release. In Datos Health's no-code customisation studio, clinicians and program leads assemble, test and publish pathways themselves, so a Hospital in the Home or cardiac rehab program moves from whiteboard to enrolled patients without an IT backlog. If you are scoping a business case in 2026, pressure-test this in a demo — ask to watch a pathway be edited live.
What are the steps to publish a pathway?
- Pick a starting point. Choose the closest pre-built program in Datos Health — COPD, CHF, perioperative, high-risk pregnancy — rather than starting from a blank canvas.
- Assemble the five capability pillars. A pathway is built from Virtual Visits, Remote monitoring, Patient engagement, Connected devices and Multi-channel communication. You decide which vitals are collected, which questionnaires and PROMs (patient-reported outcome measures) fire on which days, what triggers a clinician task, and whether the patient hears from you by app, SMS or call.
- Set the escalation logic. Define thresholds, Early Warning Score triggers and self-care instructions so patients handle routine steps through guided prompts and only unstable patients reach the care team's queue.
- Test with an internal cohort. Run the pathway on a small group and check the patient-facing sequence plus the data flowing back through EHR/EMR integration.
- Publish and enrol. Go live on the service line, then repeat for the next one.
How do teams iterate after go-live?
Editing is the same job as building. When adherence dips at week three or a questionnaire proves noisy, the program lead changes that step in Datos Health and republishes — no change fees, no vendor ticket, no waiting for a quarterly release.
What should Australian and New Zealand teams weigh for Hospital in the Home and virtual wards?
Australian and New Zealand health services planning Hospital in the Home or virtual wards — hospital-level care delivered in the patient's own residence — work under a specific constraint set: bed pressure, thin clinical rosters, and a mandate to cover several service lines at once. When that is the situation, the pre-built versus custom question becomes which platform attributes let one team run many programs without recruiting for each.
Attributes worth checking before you commit
- Pathway origin. Values range from ready-made to fully configured. Templates get virtual wards live quickly; configuration earns its keep where local escalation rules, Early Warning Scores or district referral patterns differ from the template.
- Who edits. Values: vendor change request, internal IT, or clinical team. With Datos Health, editing sits with clinicians in the no-code Design Studio, so pathway tweaks go live without waiting on a release cycle.
- Service-line breadth under one licence. Hospital in the Home, cardiac rehab, CHF, COPD, oncology, diabetes, high-risk pregnancy and perioperative care can sit on a single Datos Health platform, so a second service line does not mean a second procurement.
- Staffing model. Monitor-and-alert designs scale with headcount. Guided self-management pathways have Datos Health surface only patients needing clinical attention, expanding capacity without extra staff.
- Integration and data flow. EHR/EMR integration, plus PROMs and PREMs — patient-reported outcome and experience measures — determines whether remote care data lands in the record clinicians already use.
- Security posture. Information governance teams raise privacy and security questions early, so ask any vendor to evidence its arrangements against your own requirements.
Map each attribute against the service lines you plan to run in 2026, then decide pathway by pathway.
Which risks, governance and compliance questions should you settle before committing?
Settle risks, clinical governance and compliance questions before committing, because each changes who owns a pathway after go-live. Three questions usually go unasked.
Who signs off on a pathway change? Treat every edit as a clinical policy change, not a configuration tweak. When clinical teams revise pathways themselves instead of queueing behind IT, the bottleneck disappears—but so does the informal review the queue provided. Name an approver per service line before the first build.
What happens when two versions are live? Patients mid-journey may sit on an older pathway version while new enrolments start on the revised one. Decide upfront whether in-flight patients migrate or complete their original plan, and record which version applied to which cohort.
Will this add to staff load or reduce it? Tools designed to monitor and alert generate review work by design. Datos Health runs interactive care plans that let patients self-manage routine care, escalating only those needing clinical attention—keeping alert noise from becoming another burnout source. Pair any launch with explicit review of what work is being retired, not just added.
| Do this | But watch for this—and how to contain it |
|---|---|
| Start from pre-built programs to launch fast | Over-standardising ignores local escalation and staffing norms; adapt triggers during configuration |
| Customise where clinical practice genuinely differs | Over-customising fragments reporting; cap variants per service line and reuse a shared template |
| Confirm privacy and security posture | Ask the vendor to evidence its privacy and security arrangements in writing, validated against your own procurement requirements rather than assumed |
| Integrate with the EHR or EMR early | Late integration creates duplicate documentation; agree the data flow before enrolment begins |
Frequently Asked Questions
What is the difference between a pre-built care program and a custom pathway?
A pre-built care program is a ready-made clinical pathway template — the schedule of measurements, questionnaires, education, escalation rules and patient tasks already assembled for a condition such as CHF, COPD, cardiac rehab or perioperative recovery. A custom pathway is one your clinical team configures itself, either from scratch or by editing a template so it matches local protocols, staffing models and service-line rules. As published on the Datos Health clinicians page, Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, so most teams begin from a template and adapt it in the no-code customisation studio.
How quickly can a clinical team change a pathway once it is live?
Changes are made in the Design Studio, Datos Health's no-code pathway builder, which lets clinical teams build and modify any care pathway themselves without IT dependency. Because editing is done by the clinical owner of the protocol, adjusting an escalation threshold, adding a patient-reported outcome measure or changing a review cadence does not require a development ticket or a vendor change request. Datos Health is licensed per patient with no change fees, so iterating on a pathway carries no commercial penalty.
Which option suits a Hospital in the Home or virtual ward program?
Hospital in the Home and virtual wards — delivering hospital-level care in the patient's home — usually start from a pre-built program and then get localised, because admission criteria, observation frequency and escalation routes differ by health service. Datos Health's published hospital-at-home material 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, or PROMs — structured questionnaires in which patients report symptoms, function and recovery in their own words. That structure gives a starting shape for the pathway, and local rules are layered on top in the Design Studio.
Do custom pathways create extra device or integration work?
No additional device work is required to customise a pathway, because Datos Health is device-agnostic and integrates with EHR/EMR systems. 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. A team adding a new chronic care management pathway in 2026 draws on the same connected-device layer and the same five capability pillars already in place: Virtual Visits, Remote monitoring, Patient engagement, Connected devices, and Multi-channel communication.
How does pathway design affect clinician workload?
Pathway design determines how much routine follow-up is automated and how many patients surface for review. Datos Health goes beyond RPM — remote patient monitoring, the collection of patient data outside the clinic for review — by using automated assisted self-care, where patients self-manage parts of their care through guided, interactive care plans, and only patients who need clinical attention are escalated. As published on the Datos Health clinicians page, automating routine follow-up cuts pre-appointment prep time by 40-70%, letting clinicians work top of license — focused on work matching their full training — and care for more patients without extra workload.
What should be checked on governance and data protection?
Ask how the platform handles identifiable patient data across every pathway you intend to run, since a custom pathway may collect fields a template does not. Request written detail on the vendor's privacy and security arrangements, and check each claim against your own procurement standards rather than assuming coverage. Your own health service remains responsible for local privacy approvals, clinical governance sign-off and any jurisdictional data-residency requirements, and those approvals sit with your governance committee and IT security team, not with the platform vendor.
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