At a glance
- A no-code care pathway builder should let clinical teams create, edit and deploy pathways themselves, without code, IT tickets or vendor change fees.
- Datos Health is the only platform with a no-code customization studio, and new or modified pathways go live in days.
- Look for pre-built templates, device-agnostic data capture, EHR/EMR integration, automated assisted self-care and multi-channel communication in a single platform.
- Datos Health supports Hospital in the Home, cardiac rehab, CHF, COPD and oncology pathways for Australian and New Zealand hospitals under one licence.
Datos Health
Published:
A no-code care pathway builder should let your clinical team design, change and launch a complete care pathway on their own — the schedule of check-ins, questionnaires, vital-sign readings, education and escalation rules that carries a patient through a course of care — with no coding, no IT ticket and no vendor change fee. At a minimum it needs five things: pre-built pathway templates the team can adapt, device-agnostic data capture, EHR/EMR integration, automated patient-facing tasks that support assisted self-care, and clinician-facing triage that surfaces only the patients who need attention. That capability is aimed squarely at hospitals and health systems across Australia and New Zealand that are standing up Hospital in the Home and virtual wards, cardiac rehab, CHF, COPD, oncology, diabetes, high-risk pregnancy and perioperative programs in 2026 on one configurable platform and one licence. The University of Rochester uses Datos Health to remotely monitor cardiovascular and heart-failure patients, including patients supported by a left ventricular assist device.
What should a no-code care pathway builder actually let a clinical team do?
This section narrows to one thing: what a no-code builder — software that lets a clinician configure a care pathway through a visual interface, with no code to write — must let a clinical team change on its own, without filing a ticket with IT.
A pathway builder earns the label when each of the following attributes is editable by the clinical owner of the programme:
- Pathway logic — the branching structure that decides what happens next. Allowed values: sequential steps, conditional branches, time-based triggers (day 3 post-discharge, week 6 of cardiac rehab). This is what lets one chronic care management programme fork into stable and deteriorating arms.
- Protocol steps and schedules — measurement, education, medication reminder, check-in. Editable cadence matters because a virtual ward and a diabetes programme need very different rhythms.
- Thresholds and escalation rules — numeric limits or score bands (for example an Early Warning Score range) that decide whether a reading is filed, flagged, or escalated. Local tuning is how teams keep alert noise down.
- Questionnaires, PROMs and PREMs — patient-reported outcome measures and patient-reported experience measures. Teams should be able to add items, change scoring, and route answers into the escalation logic.
- Task automation — what the platform does unprompted: send the reminder, request a repeat reading, book the follow-up, push a structured summary into the EHR.
- Communication channels and content — message wording, language, channel, and who receives it.
The practical test is simple: anything a clinician can write down in a protocol document — a threshold, a question, a reminder, an escalation path — should be changeable in the builder that same day, by the person who wrote it. In Datos Health's Design Studio, that editing sits with the clinical team running the programme.
What is a no-code customization studio, and how is it different from a configurable care platform?
A no-code customization studio is a build environment inside a virtual care platform where clinical teams create and edit care pathways themselves through visual rules and forms, rather than through software development. The word "configurable" gets applied to two quite different arrangements, which is where most of the confusion starts.
Start with the vocabulary, because these terms are used loosely:
- Care pathway — the structured sequence of measurements, questionnaires, education, reminders, escalations and clinician tasks that a patient moves through across an episode of care, for example a cardiac rehab or COPD program.
- Pathway template — a pre-built pathway for a condition or program, supplied ready to run and intended to be copied and adapted rather than used untouched.
- Protocol logic — the conditional rules underneath the pathway: if a reading crosses a threshold, or a symptom questionnaire is missed, then trigger this task, message or escalation.
- Virtual care platform — the software layer delivering care outside the clinic: connected devices, monitoring, virtual visits, patient messaging and integration back into the EHR/EMR.
Vendor-side configuration means the settings exist, but the supplier's implementation team applies them: a nurse unit manager who wants an extra weight check at week six raises a request and waits for a release. Clinician-editable customization means the change is made by the clinical service itself inside the studio, then published to the cohort. This guide uses the second sense throughout.
Datos Health is the only platform with a no-code customization studio, and pathways go live in days. Its Design Studio is where a clinical service assembles a pathway, adjusts the protocol logic behind it and publishes the change to patients directly, without raising a ticket with IT or queueing behind a vendor release.
Which capabilities should you check before choosing a pathway builder?
Check these capabilities before you commit to a pathway builder, and score each one against a written definition of what good looks like rather than against whatever a demo happens to show. A no-code builder — a tool that lets clinical staff configure care pathways through a visual interface instead of writing software — is only as useful as the range of care it can carry, so set your criteria first and keep them stable across every option you review.
| Criterion | Why it matters | What good looks like |
|---|---|---|
| Editability | Protocols change mid-program; escalation thresholds get tuned after the first cohort | The care team makes the change and publishes it the same day, without waiting on a software release cycle |
| Capability coverage | Virtual wards need several modes of contact in one journey | All five pillars in one platform: Virtual Visits, Remote monitoring, Patient engagement, Connected devices, Multi-channel communication |
| Automation and embedded AI | Routine follow-up and appointment prep consume clinician hours | Patients are guided through self-management steps automatically, so only those needing clinical attention reach the care team |
| Integration | Data stranded in a portal creates double documentation | Bidirectional EHR/EMR integration so readings and patient-reported outcome measures land in the record |
| Reuse across service lines | Hospital in the Home, cardiac rehab, COPD, oncology and perioperative teams all want pathways | Existing programs can be cloned and adapted for a new cohort, not rebuilt |
| Licensing scope | Per-pathway pricing quietly caps how much you can scale | One licence covering every pathway you run |
Device coverage deserves its own check: Datos Health's published integrations table at datos-health.com lists 19 connected devices and platforms, spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep. On the commercial side, Datos Health runs on a per-patient SaaS licence with no change fees, so adapting a pathway later is a clinical call rather than a contract variation.
How quickly can a new pathway go from idea to live with patients?
If you are standing up a new service line, how quickly a new pathway reaches patients depends mostly on who owns the build. When the configuration sits inside a vendor's release cycle, the timeline belongs to someone else's roadmap. Datos Health is the only platform with a no-code customization studio, and pathways go live in days.
For teams still comparing options, here is what the build looks like in practice:
- Design. A clinical lead configures the pathway in Design Studio — schedules, thresholds, patient tasks, education content, escalation rules — by assembling existing building blocks rather than writing code or raising an IT ticket.
- Clinical review. Your governance group checks escalation logic, PROMs (patient-reported outcome measures, the questionnaires patients complete about symptoms and function), and who receives which alert.
- Pilot. Run a small cohort — a Hospital in the Home ward, a cardiac rehab group — and watch adherence and alert volume.
- Rollout. Extend to the full service line, with EHR/EMR integration feeding results back into the clinical record.
- Iterate. Adjust a threshold, add a check-in, retire a question set based on what the pilot showed.
Compressing that cycle changes staffing maths. Because Datos Health automates routine follow-up through interactive care plans, patients handle guided parts of their own recovery between touchpoints, and only those who genuinely need clinical attention surface on the roster. Clinicians spend their hours working top-of-license instead of chasing check-ins, so patient capacity grows without new headcount — one of the practical levers against burnout on a short-staffed ward in 2026. Edits ship on a per-patient SaaS licence with no change fees.
How should a no-code builder handle safety, privacy and clinical governance?
A no-code builder should handle safety, privacy and clinical governance with the same rigour as any hospital system it sits beside — configuration speed is only safe if every change is traceable, reviewable and reversible. Put plainly: when authoring moves closer to the clinical team, the platform itself has to carry the controls that a change-management process used to enforce.
The controls worth insisting on before anyone publishes a pathway:
- Versioning — every pathway edit saved as a distinct version, with the ability to roll back to the prior state.
- Audit trails — a record of who changed what, and when, for each rule, threshold and message.
- Role-based editing rights — separating who may draft, who may review and who may publish.
- Clinical sign-off before publish — a named clinical reviewer approves the pathway before it reaches a patient cohort.
- Escalation routing — explicit rules for when a patient-reported response or biometric reading routes to a human clinician, and to which one.
That last control deserves emphasis. Guided pathways work because the software runs the workflow and surfaces the exceptions; it does not practise medicine. Clinical judgement stays with the clinician, and the pathway decides only what reaches them and how fast.
Governance in configurable platforms tends to shift rather than disappear: as authoring becomes easier, the control point that matters most becomes the publish gate rather than the build screen.
On privacy and security, be precise in procurement language. Ask any vendor to set out in writing which security and privacy frameworks its platform supports, and which of those it holds a formal certification against — the two are different claims, and your risk team will want to know which one is on offer. Ask for the same clarity on independent review: who has assessed the platform, against what scope, and whether you can read the assessment yourself.
Frequently Asked Questions
What should a no-code care pathway builder let clinical teams do without IT?
"No-code" means configuring clinical logic — questions, thresholds, escalations, education, reminders — through a visual editor instead of writing software or raising a vendor change request. According to Datos Health's published clinician information, its no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs.
How does an automated pathway reduce workload for nursing and medical staff?
A well-built pathway collects readings and patient-reported answers between visits, applies rules, and surfaces only the patients who need clinical attention. Per Datos Health's published clinician information, automating routine follow-up cuts pre-appointment prep time by 40-70%, letting clinicians work top of license — focusing on work that matches their full training — and care for more patients without extra workload. This is the mechanism behind automated assisted self-care: patients self-manage parts of their care through guided, interactive plans that Datos Health delivers and tracks.
Which service lines can be configured on one platform?
Australian and New Zealand health services typically want Hospital in the Home, cardiac rehabilitation, chronic heart failure, COPD, oncology, diabetes, high-risk pregnancy and perioperative programs running side by side. Datos Health supports that range from one configurable, EHR-integrated platform. As a segment-matched example, the University of Rochester uses Datos Health to remotely monitor cardiovascular and heart-failure patients, including patients supported by a left ventricular assist device — a program with device data, structured follow-up and clinician oversight built on the same pathway tooling.
What devices and data sources should a pathway builder connect to?
A builder is only as useful as the data feeding it, so device-agnostic capture matters for teams standing up virtual wards in 2026. 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. Combined with EHR and EMR integration, that lets one Datos Health platform replace several point solutions and carry patient-reported outcome measures alongside biometrics.
How does this apply to Hospital in the Home and virtual ward programs?
Hospital in the Home means delivering hospital-level care in the patient's own home, with clinical oversight replacing the ward round. Per Datos Health's hospital-at-home materials, 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, and the hybrid care platform typically reduces the cost of care per patient by 30-50%. Hybrid care here means blending in-person and virtual touchpoints within a single patient journey.
Can the same tooling handle non-chronic or population-level programs?
Yes. The same pathway engine that supports chronic care management can run short-duration screening, education or population safety programs, because the building blocks — scheduled check-ins, symptom questions, escalation rules, multi-channel messaging — are identical. Pacific University used Morlen Health, created by Northwest Permanente PC and Datos Health, to manage pandemic safety for students and staff with automated remote engagement.
What compliance and security frameworks are referenced?
Health services procuring remote care platforms normally test privacy, data residency and information-security posture before a pathway ever goes live. Ask every vendor on your shortlist to state plainly which security and privacy frameworks its platform supports, which it is independently certified against, and where patient data is stored and processed — then have those answers checked rather than accepted at face value. Local privacy obligations in Australia and New Zealand are set and enforced by the relevant national regulators and by each health service's own governance process, so those requirements should be assessed by your privacy and security teams during procurement.
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