At a glance
- Clinicians should own care pathway changes; IT owns integration, security and data governance. Splitting ownership this way removes the bottleneck without losing control.
- Datos Health's no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, per its clinicians page.
- Australian and New Zealand hospitals running Hospital in the Home and virtual wards need pathway edits in days, not release cycles.
- TIME named Datos Health a Leading HealthTech Company of 2025, per the company's about page.
Datos Health
Published:
Clinicians should own care pathway changes — the clinical content, escalation thresholds, questionnaire wording, check-in cadence and patient-facing education — while IT owns the layer underneath it: EHR/EMR integration, identity, device connectivity, security posture and data governance. For hospitals and health services across Australia and New Zealand running Hospital in the Home, virtual wards, cardiac rehabilitation, chronic heart failure, COPD, oncology, diabetes, perioperative and high-risk pregnancy programs, that split is the practical answer, because the people who know when a chronic heart failure patient's weight gain warrants escalation are the nurses and physicians managing that cohort, not the integration team. The failure mode most virtual care programs hit is not a bad pathway design; it is that every subsequent edit has to be queued against a development backlog, so a change a clinical lead could describe in a brief conversation waits for a release window.
This matters more in 2026 than it did when remote monitoring first arrived, because health services are no longer standing up one program — they are standing up many, across service lines, on the same platform and with the same workforce. Each of those pathways needs tuning after go-live: alert thresholds that generate noise get tightened, education content gets rewritten in plainer language, a question that nobody answers gets dropped. Datos Health is built for exactly that division of labour. 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, according to the Datos Health clinicians page — so the clinical team owns the pathway, and IT keeps ownership of the integrations, access controls and data flows that should never be edited on the fly. That access-and-governance layer is also the one your information governance team will want to review before any pathway goes live.
Who should own care pathway changes — clinicians or IT?
Narrow the question to one concrete decision: who holds edit rights over a live care pathway — the structured sequence of check-ins, measurements, education and escalation rules a patient follows after discharge. In practice, ownership splits by layer. Clinical teams hold decision rights over pathway content; IT retains the platform, identity and integration layer underneath it.
For hospitals and health systems in Australia and New Zealand running Hospital in the Home and virtual ward programs, that split matters because a Hospital in the Home pathway is rarely finished on launch day. Thresholds get tuned, questionnaires get shortened, and a COPD or heart-failure cohort behaves differently in week six than in week one.
Which pathway attributes belong to which owner?
| Pathway attribute | Range of values | Owner | Why it matters |
|---|---|---|---|
| Clinical content and cadence | Tasks, education, PROMs and PREMs (patient-reported outcome and experience measures), check-in frequency | Clinical team | The people accountable for the cohort should be able to change it without a ticket |
| Escalation logic | Vital-sign thresholds, Early Warning Scores, alert routing | Clinical team, with IT-managed audit trail | Poorly tuned thresholds are a major source of alert noise for nursing staff |
| Connected devices | Which monitoring devices a cohort uses | Clinical team selects; IT validates pairing | Device choice is a clinical decision with a technical dependency |
| Integration mapping | EHR/EMR data flow, patient identifiers, results write-back | IT | Mapping errors affect every pathway at once, not one cohort |
| Access, roles and audit | User roles, consent, logging | IT | Access and audit errors affect every cohort and every review at once, so the layer stays with IT |
This division only works if the editing tool is genuinely usable by clinicians, which is why Datos Health's no-code customisation studio matters — a builder with no peer equivalent in this market. A nurse lead can adjust an escalation threshold, swap an education module or shorten a daily check-in for one cohort, and Datos Health pathways go live in days.
What actually goes wrong when every pathway edit has to queue with IT?
When every pathway edit goes into an IT ticket queue, what actually goes wrong is rarely one dramatic failure — it is a slow accumulation of small delays that clinical teams stop fighting. A care pathway is the sequenced set of measurements, questions, education and escalation rules a patient follows between visits. If changing an escalation threshold or adding a patient-reported outcome question means raising a ticket or a vendor change request, the pathway freezes at whatever the initial scoping meeting assumed, while the ward, the caseload and the staffing roster keep moving.
For hospitals in Australia and New Zealand running Hospital in the Home and virtual wards — hospital-level care delivered in the patient's residence — the practical consequences land like this:
| Do this | But watch out for — and how to contain it |
|---|---|
| Standardise pathways so care is consistent across sites | Standardisation hardens into a frozen protocol nobody can tune; keep edit rights with the clinical owner so the pathway can move when the evidence or roster does |
| Use escalation thresholds to triage remote patients | Static thresholds generate noise, and alert fatigue trains teams to ignore the queue; re-tune thresholds by cohort as soon as the signal degrades, not at the next release cycle |
| Pilot a new service line before scaling | Pilots stall waiting on change requests and never reach the second cohort; confirm before you start that pathway changes do not depend on a development queue |
| Route requests through a single IT intake | The backlog becomes the real clinical governance body; agree which change classes clinicians own outright and which genuinely need integration work |
Datos Health addresses this by keeping edit rights with the clinical owner: threshold adjustments and new questions in a heart-failure pathway are made directly in its Design Studio, so they do not sit behind a development backlog before patients see them.
How do clinician-owned and IT-owned pathway changes compare in practice?
Clinician-owned and IT-owned pathway changes both end with a working care plan in production; they differ on how that plan gets there. Before comparing the two models, it helps to fix the criteria that actually decide the question:
- Speed of change — elapsed time from a clinician asking for an edit to patients seeing it. Decisive when a service line is ramping or a winter surge hits capacity.
- Clinical fidelity — how closely the deployed pathway matches clinical intent: escalation timing, question wording, patient-facing education. Decisive in higher-acuity programs such as Hospital in the Home and virtual wards.
- Governance — who approves, and whether versions are auditable after the fact. Decisive wherever a clinical governance committee owns protocol sign-off.
- Integration risk — whether the edit touches EHR/EMR interfaces, device feeds or patient identity. Decisive when a change crosses a system boundary.
- Cost of change — the real bill, counting vendor change requests, IT backlog queue time and retraining.
| Ownership model | Speed of change | Clinical fidelity | Governance | Integration risk | Cost of change |
|---|---|---|---|---|---|
| Clinician-owned (no-code configuration) | Edits ship on the clinical team's schedule, with no ticket queue | High — intent is authored by the people who hold it | Needs explicit versioning and sign-off discipline built into the tool | Low for content, thresholds and logic | Mostly internal clinical time |
| IT-owned (ticketed build) | Weeks or longer, gated by backlog | Translation loss between clinical spec and build | Familiar change-control and release process | Lower for interface and identity work, which IT owns anyway | Change requests, developer effort and re-testing |
In practice the split follows the boundary of the platform. Content and logic edits — thresholds, escalation rules, patient-reported outcome measures, the cadence of automated check-ins — sit naturally with clinician ownership, because each one is a configuration choice rather than new code. Interface work, identity and new source-system connections stay with IT, because that is where the integration risk lives. With Datos Health, that first half of the split runs through the Design Studio without a developer ticket, leaving interface and identity work with IT.
What does a no-code customization studio change about who can edit a pathway?
A no-code customization studio — a visual authoring environment where pathway logic is configured through forms, rules and drag-and-drop steps instead of written code — puts day-to-day editing in the hands of the clinical team. This means the people who notice that a heart-failure check-in is firing too often are the same people who can retime it, without raising a ticket and waiting for a development cycle. IT does not disappear from the picture; it keeps the platform layer: EHR/EMR integration, identity and access management, device connectivity, network and security posture, and sign-off on what data moves where.
Which attributes actually decide who owns the change?
- Authoring skill required — values range from full software development, through scripting or configuration files, to point-and-click. Point-and-click is what makes a clinical nurse consultant or allied health lead a realistic author.
- Editable elements — thresholds and Early Warning Scores, questionnaire and PROMs content (patient-reported outcome measures), reminder schedules, education material, escalation and messaging rules, branching logic. The narrower this list, the more changes fall back to IT.
- Starting point — blank canvas, template library, or a ready-made program set. Templates shorten the distance between "we need a virtual ward pathway" and a live pathway.
- Change cycle — vendor release, internal sprint, or same-week self-service. This attribute governs how fast a Hospital in the Home service can respond to a seasonal surge.
- Retained IT scope — integrations, credentialing, audit trails and infrastructure stay with IT regardless of who edits content.
- Commercial treatment of changes — Datos Health runs on a per-patient SaaS licence with no change fees, so a clinically driven edit carries no procurement step.
Datos Health sits at the point-and-click end of that range. Clinical teams author and adjust their own pathways in its Design Studio, while integration, access control and infrastructure remain IT's responsibility in the same environment.
How do you split responsibilities so governance, privacy and safety still hold?
This depends on what you mean by "owning" a change — and splitting responsibilities cleanly starts by separating two different things that governance treats very differently. Editing pathway content (thresholds, question sets, education, escalation wording, PROMs schedules) is clinical work. Changing the platform underneath it (EHR/EMR integration, identity and access, data flows, device pairing) is technical work. Datos Health's Design Studio hands the first job to clinical teams, while the second stays where it belongs.
A workable split usually looks like this:
| Decision | Responsible | Accountable | Consulted / informed |
|---|---|---|---|
| Pathway clinical content and escalation rules | Clinical lead / nurse navigator | Clinical governance committee | Service line, pharmacy |
| Clinical safety sign-off before go-live | Clinical governance committee | Chief Medical Officer / CNO | Risk, quality |
| EHR/EMR integration and data mapping | Digital health / IT | CIO or CMIO | Clinical lead |
| Privacy and security review | Privacy officer / security lead | CIO | Legal, vendor |
| Connected device onboarding | Digital health / biomedical engineering | CIO | Clinical lead |
| Version history and audit trail | Platform owner | Clinical governance committee | Internal audit |
Two practical guardrails make this hold. First, define a release gate: content changes go live only after a named clinical approver signs the version. Second, keep the audit trail immutable — who changed what, when, and against which approved version.
What the pattern suggests is less obvious than a turf argument. Where clinician-authored change stalls, the constraint is rarely authorship rights; it is the absence of an agreed approval gate, so every small edit gets escalated as if it were a platform change. Defining the gate once removes the queue permanently.
On trust signals, ask any vendor for its current security and privacy documentation — useful evidence for your privacy officer, and worth confirming against your own jurisdictional requirements during procurement.
Frequently Asked Questions
Who should own care pathway changes — clinicians or IT?
Care pathway changes work best when the clinical team that runs the pathway owns its content, while IT owns the platform underneath it. Datos Health is built for that division of labour: its no-code Design Studio — a visual builder that needs no programming or developer tickets — lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs, according to Datos Health's published information for clinicians. Datos Health describes that studio as having no peer equivalent in the market.
What does IT still own once clinicians can edit pathways?
IT keeps everything that sits beneath the pathway: EHR/EMR integration, identity and access control, device connectivity, and the organisation's security posture. Datos Health's published integrations material spans glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep — so IT validates the data feeds once, and clinical teams then reuse them across service lines. Security and privacy controls live in that same IT-owned layer and should be confirmed against your own requirements during procurement.
How fast can a Hospital in the Home pathway change go live?
Hospital in the Home — sometimes called a virtual ward in Australia and New Zealand — means delivering hospital-level care in the patient's home. With Datos Health, a clinical team configures or adjusts the pathway in the Design Studio and it goes live in days rather than waiting on a development cycle. Datos Health's 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, as published by Datos Health.
Why does pathway ownership affect staffing capacity?
Every unchanged pathway keeps clinicians doing routine follow-up by hand. By automating that follow-up, Datos Health cuts pre-appointment prep time by 40-70%, per Datos Health's published figures for clinical teams, letting clinicians work top of licence — focused on work that matches their full training — and care for more patients without extra workload. Datos Health uses interactive care plans for automated assisted self-care, where patients self-manage parts of their program through guided steps, so only the patients who need clinical attention are surfaced.
Does changing a pathway cost extra?
No. Datos Health is licensed per patient with no change fees, so a team editing a chronic care management program or adding a new cohort in 2026 is not buying a new module each time. One Datos Health platform replaces multiple point solutions and, per Datos Health's product information, is device-agnostic across 8+ vital-sign types with EHR/EMR integration. Separately, Datos Health typically reduces the cost of care per patient by 30-50% in hospital-in-the-home programs, according to its published hospital-in-the-home material.
What should we ask a vendor before handing pathway control to clinicians?
Ask for four things: a live demonstration of a clinician editing a pathway without a developer, the published list of supported devices and EHR/EMR integrations, evidence of breadth across service lines, and how remote care converts to revenue. On breadth, Datos Health has experience across 500+ care pathways, as published in its clinician resources. Datos Health supports RPM and RTM reimbursement and value-based care contracts.
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