Datos Health's Design Studio is a no-code workflow builder that lets nurses and clinical teams design, modify, and deploy remote care pathways themselves — no custom code, no IT tickets, no vendor change requests. Nurses work in a visual editor to configure patient questionnaires, vital-sign thresholds, education content, reminders, and escalation rules, then publish the pathway live to patients. Instead of writing a spec and waiting months for a developer build, the clinician who owns the protocol is the same person who ships it, often in days.
That shift matters because remote care programs stall when workflow changes depend on a queue outside the clinical team. In 2026, health services across Australia and New Zealand are standing up Hospital in the Home, virtual wards, chronic care management, and perioperative pathways in parallel — and each one needs its own logic. The sections below unpack what that looks like in practice: what Design Studio actually is, how a nurse builds a workflow step by step, which guardrails keep clinical governance intact, and how it compares to code-first or IT-dependent alternatives.
What is Design Studio and how does it enable nurses to build workflows without code?
Design Studio is Datos Health's no-code builder that enables nurses and other clinical staff to design, modify, and deploy remote care workflows themselves — without writing custom code or waiting on IT. Think of it as a drag-and-configure canvas where a nurse maps out what a patient journey should look like (which vitals to collect, which questions to ask, which thresholds trigger a call), and the platform turns that map into a live pathway.
What does "no-code clinical workflow builder" actually mean here?
The phrase can be read two different ways, so it's worth separating them:
- No-code for citizen developers — generic drag-and-drop tools (form builders, low-code app platforms) that anyone can use but which know nothing about clinical care.
- No-code for clinicians — a purpose-built environment where the building blocks are already clinical: symptom check-ins, PROMs (patient-reported outcome measures), device readings, escalation rules, education content.
Design Studio is the second kind. Nurses aren't wiring up databases; they're arranging clinical logic they already understand.
Which attributes matter when a nurse sits down to build?
| Attribute | What it means | Why it matters to a nurse |
|---|---|---|
| Starting library | 300+ pre-built care programs shipped with the platform | You rarely start from a blank page — clone a CHF or post-op template and adapt it |
| Building blocks | Vitals, PROMs/PREMs, education, tasks, messages, escalations | Matches how clinicians already think about a care plan |
| Device inputs | Datos Health's published integrations table lists 19 connected devices and platforms across vitals like glucose, blood pressure, SpO2, weight and more | Choose the device once; the pathway handles the data |
| Escalation logic | Rule-based thresholds and Early Warning Scores | Only patients who need attention surface to the clinician |
| Edit cycle | Modify a live pathway and re-deploy without a release ticket | Cardiac rehab tweak on Tuesday goes live the same week |
| Integration | EHR/EMR connectivity | Data flows back into the record clinicians already use |
The net effect: the person closest to the patient owns the workflow.
How do nurses actually build a workflow in Design Studio step by step?
Nurses can actually build a live workflow in Design Studio without writing code, using drag-and-drop blocks to assemble a personalized care pathway in days. The no-code Design Studio was designed for clinical teams — not developers — so a charge nurse or care coordinator can go from blank canvas to piloted pathway themselves, without waiting on an IT ticket queue.
This walkthrough targets the decision-to-launch stage: you have chosen a use case (say, a Hospital in the Home discharge pathway for CHF) and you are ready to configure it.
What are the drag-and-drop steps?
- Start from a template, not a blank page. Open the Design Studio library and pick one of the 300+ pre-built care programs — CHF, COPD, perioperative, cardiac rehab, oncology, high-risk pregnancy. This becomes your baseline.
- Set the enrolment rules. Drag in the eligibility block and configure who lands on this pathway (diagnosis, discharge disposition, risk score) and for how long — for example, the 12-week post-discharge window typical of Hospital in the Home programs.
- Assemble the daily patient journey. Drop in the CareApp blocks patients will see: symptom check-ins, medication reminders, education modules, PROMs (patient-reported outcome measures) and PREMs (experience measures), and video Virtual Visits.
- Bind the devices. Pick from the connected devices catalogue — blood pressure, SpO2, weight, glucose, continuous glucose, temperature, and the other vital-sign types Datos Health supports — and map each reading to the pathway.
- Configure thresholds and Early Warning Scores. Set the parameters that trigger a nurse review versus automated patient guidance, so alerts flag only patients who genuinely need clinical attention.
- Route the escalations. Draw the notification paths: who gets pinged, on which channel, and what the fallback is if no one acknowledges.
- Review, then publish. Check the configuration, tweak, and go live. Iteration keeps working the same way — no change fees, no re-implementation project.
The whole flow is visual, editable, and owned by the clinical team.
Which nursing workflows can be automated with Design Studio?
Which routine tasks translate cleanly into no-code pathways?
- Virtual rounding and check-ins. Scheduled prompts collect vitals from connected devices and symptom scores via PROMs (patient-reported outcome measures — short questionnaires patients complete themselves), so nurses see a triaged list instead of paging through every stable patient.
- Shift handoffs. Rules can roll up overnight readings, missed responses, and Early Warning Score changes into a structured summary for the incoming shift.
- Discharge follow-up. Post-discharge pathways — common in Hospital in the Home programs — sequence education, medication reminders, and biometric check-ins across the recovery window.
- Escalations. Threshold logic surfaces only the patients who need clinical attention, routing alerts to the right role instead of broadcasting to a shared inbox.
- Pre-appointment preparation. Intake questionnaires and device readings populate the chart before the visit, cutting the manual prep burden that would otherwise fall on nursing staff.
Nursing teams can turn many recurring workflows into automated pathways inside Design Studio, the no-code builder that lets clinical staff assemble care logic without writing code. Because the studio ships with 300+ pre-built care programs and experience across 500+ care pathways, nurses usually start from a template and adapt it — rather than building from a blank canvas — for the specific cohort or ward.
What attributes define a nurse-built workflow?
| Attribute | Typical values | Why it matters |
|---|---|---|
| Trigger | Enrolment, discharge, threshold breach, time-of-day | Determines when the pathway fires |
| Data inputs | Vitals from connected devices, PROMs, PREMs, manual entry | Shapes what nurses see and act on |
| Escalation path | Nurse, care coordinator, MD, on-call | Prevents alert noise reaching the wrong role |
| Duration | Days to weeks, aligned to the clinical program window | Aligns pathway to clinical program length |
| Channel | SMS, app, voice, email | Matches patient preference and access |
Related topics worth exploring
Nurse-built workflows connect naturally to chronic care management programs, virtual ward staffing models, and value-based care contracting — each leans on the same automated assisted self-care foundation, where patients self-manage guided steps and clinicians intervene by exception.
How does Design Studio compare to custom-coded workflow development?
To compare Design Studio against custom-coded workflow development, it helps to line up the two approaches against the criteria that actually matter to clinical and IT leaders: speed to launch, total cost, governance, and long-term maintenance. Design Studio is Datos Health's no-code environment where clinical teams configure care pathways directly, whereas custom code means engineers hand-building each workflow in a bespoke stack.
Which criteria should you weigh?
Before comparing tools, agree on what "better" means. We suggest four criteria, weighted for a scaling remote care program:
- Speed to launch — days versus quarters matters when service lines are waiting.
- Total cost of ownership — includes build, change requests, and integration upkeep.
- Clinical governance — who owns the pathway, and how changes are reviewed.
- Maintenance burden — device drivers, EHR/EMR integrations, and regulatory updates over time.
How do the two approaches stack up?
| Criterion | Design Studio (no-code) | Custom-coded development |
|---|---|---|
| Speed to launch | Pathways live in days, starting from 300+ pre-built care programs | Weeks to quarters per pathway |
| Who builds | Clinical teams, without IT dependency | Software engineers, with clinical BA translation |
| Change requests | Configured in-app; no change fees on the per-patient SaaS licence | New sprint, new spec, new QA cycle |
| Integrations | Device-agnostic across 8+ vital-sign types with EHR/EMR integration included | Each device and EHR interface built and maintained in-house |
| Governance | Care pathways owned and edited by clinicians | Code repos owned by IT, further from bedside |
| Maintenance | Vendor-maintained platform, with a compliance posture referencing HIPAA, GDPR, ISO 27001 and ISO 27799 | Ongoing engineering to keep drivers, APIs and security current |
What's the verdict?
For hospitals standing up multiple pathways — Hospital in the Home, cardiac rehab, CHF, COPD, oncology — the no-code route wins on every criterion that scales.
What are the risks and safeguards when nurses build clinical workflows themselves?
When nurses build clinical workflows themselves, the real risks are not that safeguards disappear — it's that governance has to move from gatekeeping every change to reviewing configurations at the speed clinicians make them. If a pathway can go live in days, then review, validation, and sign-off have to run at that same tempo, or safety debt accumulates quietly.
It follows that the guardrails work best when they live in the clinical process, not as an afterthought. In practice that means a clear review-before-publish step so a pathway is checked before it reaches patients, and EHR/EMR integration so patient data stays inside the system of record rather than living in a side spreadsheet.
What to do — and what to watch for
| Do this | But watch out for |
|---|---|
| Let nurse leads own pathway logic in Design Studio | Pathway drift — the same condition modelled three different ways across units |
| Start from the 300+ pre-built care programs | Copy-paste errors when a template is edited without documenting why |
| Add a review-before-publish step and agree who can publish | Approval bottlenecks that push clinicians back to workarounds |
| Document why each change was made | Alarm and escalation thresholds edited without clinical governance sign-off |
| Validate changes against test patients before going live | Skipping validation for "small" tweaks that touch escalation rules |
The highest-impact mitigation
The single biggest risk is inconsistent escalation logic — two nurses building COPD pathways with different Early Warning Score thresholds. Mitigate it by treating escalation rules, PROMs scoring, and alert thresholds as a shared clinical governance artefact: a small multidisciplinary committee (nursing lead, CMO delegate, digital health) signs off changes to those specific elements, while nurses retain full autonomy over content, cadence, and patient-facing education. That preserves the speed advantage of no-code authoring in 2026 without letting patient-safety logic fragment across service lines.
Frequently Asked Questions
Do nurses really build pathways without writing code?
Yes. The Design Studio is a no-code environment, meaning clinical teams configure workflows through a visual builder rather than programming. Nurses and clinical leads assemble triggers, questions, thresholds, and patient-facing content directly. Datos Health positions this as a no-code OpenCare builder with no peer equivalent.
How long does it take to launch a new care pathway?
Pathways can go live in days rather than the multi-month cycles typical of IT-led builds. Because nurses start from Datos Health's library of 300+ pre-built care programs — covering Hospital in the Home, cardiac rehab, CHF, COPD, oncology, diabetes, high-risk pregnancy and perioperative care — most work is tailoring rather than building from scratch.
What clinical training or technical background is required?
Design Studio is built for clinicians, not developers. A nurse who understands the care pathway — the assessments, escalation rules, and patient education involved — has the domain knowledge needed. Familiarity with common clinical instruments like Early Warning Scores (EWS), PROMs and PREMs helps, but no scripting or database skills are required.
Can nurses modify a live pathway without breaking anything?
Yes. Pathways are configurable, so clinical teams can adjust thresholds, questions, or reminder cadences as evidence and local protocols evolve — for example, updating a CHF weight-gain alert or adding a new PROM. This is core to the assisted self-care model, where pathways adapt to patient response rather than staying static.
How does Design Studio work with our EHR and devices?
Pathways built in Design Studio plug into Datos Health's EHR/EMR integration and connected-device layer. The 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 a nurse-built workflow can pull biometrics and push documentation without a separate integration project.
What about compliance and data governance when nurses configure workflows?
Datos Health references support for HIPAA, GDPR, ISO 27001 and ISO 27799, and clinical governance stays with the health service. Design Studio gives nurses the build surface, while a review-and-sign-off step lets clinical leadership approve changes before a pathway reaches patients — the same governance you would apply to any protocol update in 2026.