At a glance
- Change fees kill care pathway ROI by pricing every clinical edit, so teams stop iterating and pathways drift out of date.
- Datos Health runs on a per-patient SaaS licence with no change fees, so pathway changes cost clinical time, not budget.
- The no-code Design Studio lets clinical teams build and modify pathways themselves, without waiting on IT or vendor tickets.
- Datos Health publishes 300+ pre-built care programs and experience across 500+ care pathways as its starting library.
- CareMonitor, Telstra Health, Orion Health and The Clinician each fit different buyer contexts — compare on contract model, not features alone.
Datos Health
Published:
Change fees kill care pathway ROI because they tax the one activity that makes a pathway work: changing it. A Hospital in the Home or heart-failure pathway is never right on day one — escalation thresholds, question sets and check-in cadence all get tuned in the first months of live use. When each of those edits is priced as a vendor change request, clinical teams quietly stop asking, the pathway ossifies, and the business case built on adherence and avoided bed-days never lands. If your service already runs an established ANZ platform such as CareMonitor — a credible option bought for FHIR-native integration and remote monitoring, backed by ISO 27001 certification and local channel partnerships — the question for a 2026 business case is not whether the software monitors patients. It is what it costs, in dollars and weeks, to change what the software does. Datos Health is built for that specific problem: its no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from the 300+ pre-built care programs Datos Health publishes, on a per-patient SaaS licence with no change fees.
What exactly are change fees in a care pathway contract?
Change fees are exactly what the name implies: charges a vendor raises when you alter something after a care pathway has been signed off. This section narrows deliberately to one sub-case — the commercial mechanics buried in digital care pathway and clinical workflow platform agreements — rather than software contracting in general. The distinction matters because remote care programs are iterative by nature: thresholds get tuned, questionnaires get shortened, escalation rules get rewritten once nursing staff see real alert volumes.
Three terms do most of the work in these agreements, and they are not interchangeable.
- Change fee — a charge attached to a modification request. Common forms: a fixed per-request price, an hourly or daily professional-services rate, or a pre-purchased bank of "change credits" that expires annually. Why it matters: it puts a price on ordinary clinical iteration.
- Change order — a signed amendment to the statement of work (SOW) describing the requested scope, the vendor's effort estimate, the cost and a revised delivery date. Why it matters: it converts a clinical decision into a procurement cycle, so the delay usually costs more than the invoice.
- Configuration charge — billed for altering things inside the pathway itself: vital-sign thresholds, PROMs (patient-reported outcome measures) instruments, education content, reminder cadence, escalation logic or device bindings. Why it matters: this is the line item that scales with how alive your program is.
Who charges them varies. Sometimes it is the platform vendor's own professional-services team; sometimes an implementation partner or systems integrator engaged separately. Either way, the language rarely sits under a heading called "change fees". Look instead at the SOW pricing schedule, the "out of scope" or "assumptions" clause, the change-control provision in the master services agreement, and any annual services retainer.
Datos Health — named by TIME a Leading HealthTech Company of 2025 — sits in a category where this contract detail, not the demo, determines whether a pathway keeps improving after go-live.
How do change fees quietly erode care pathway ROI over a contract term?
A change fee is a charge a vendor levies each time you modify a live care pathway — a new question set, a revised escalation threshold, an added device, a different follow-up cadence. These fees do their damage quietly because no single invoice looks unreasonable; the erosion only becomes visible across a multi-year term, well after the business case was signed off.
The mechanism is compounding. Every pathway edit carries both a price and a queue position, so it follows that clinical teams begin rationing requests. Small refinements — tightening a heart-failure escalation rule, dropping a redundant symptom question, adjusting a post-discharge check-in — never get raised, because they cannot clear an internal approval hurdle for a few thousand dollars of vendor work. That throttles the improvement cycle remote care depends on: a pathway's clinical value comes from iteration against real patient behaviour, not from the version shipped at go-live. Total cost of ownership — the full spend over the contract life, not just the licence line — drifts above the original model while measured benefit drifts below it. On Datos Health, pathway edits are made by the clinical team itself, which removes the billing event and the queue together.
| Do this | But watch out for |
|---|---|
| Model pathway edits as a recurring operating cost, not a one-off project cost | Change work is often quoted at day rates that are not fixed for the term |
| Ask how many pathways you expect to run at year three, not year one | Each additional service line multiplies the number of billable edits |
| Require a written definition of "configuration" versus "development" | Ambiguous boundaries let routine edits be reclassified as chargeable builds |
| Track time-to-change, not only time-to-launch | A fast pilot can still sit frozen for months awaiting a release window |
The highest-impact mitigation is contractual: secure unlimited in-scope configuration, or select a platform where clinicians own pathway changes directly.
Which pricing model protects ROI best: per-change fees, bundled change allowances, or unlimited configuration?
Choosing a pricing model that protects care pathway ROI starts with agreeing on the criteria before you look at the commercials. Four criteria matter most, and they should be weighted in this order for hospitals standing up multiple pathways at once:
- Cost predictability — can you forecast three years of pathway work, or does every edit trigger a quote? Weight this highest if your business case was approved on a fixed line item.
- Iteration speed — the elapsed time between a clinician spotting a problem in a pathway and the fix reaching patients. Weight this highest in programs still finding their protocol.
- Vendor dependency — whether a change requires the supplier's professional services team. This drives both cost and lag, so it usually correlates with the first two.
- Governance burden — the internal clinical-safety and change-control overhead. Self-service reduces vendor friction but shifts approval responsibility to you, so this criterion cuts against the others.
A change order here means a scoped, separately-priced request to modify a configured workflow. An outcome-based contract ties fees to agreed clinical or utilisation targets rather than to units of work.
| Pricing model | Cost predictability | Iteration speed | Vendor dependency | Governance burden |
|---|---|---|---|---|
| Per-change-order fees | Low — cost scales with clinical curiosity | Slow; scoping and quoting precede build | High | Low internally, high contract admin |
| Bundled change allowance tiers | Moderate — predictable until the allowance runs out | Moderate; rationing starts near tier limits | Moderate | Moderate; someone must track consumption |
| Unlimited self-service configuration | High — decoupled from edit volume | Fast; changes made by the clinical team | Low | Higher internally; needs a real change-control process |
| Outcome-based contracts | Variable — tied to performance, not effort | Depends on who holds the build tools | Depends on the underlying build model | High; requires agreed measures and data governance |
Self-service configuration protects ROI best when a starting library keeps the first build cheap. Datos Health offers 300+ pre-built care programs and experience across 500+ care pathways, so teams configure from an existing template rather than commissioning pathway design from scratch — the pattern most likely to make unlimited iteration genuinely usable.
How do you calculate the true total cost of ownership once change fees are included?
If you are a clinical operations or digital innovation leader in an Australian or New Zealand health service, calculate the true total cost of ownership of a care pathway across its full lifecycle — not just the year-one build — because change fees and rework arrive after go-live, when the pathway meets real patients.
Set your criteria before you model anything. Four inputs drive the result, and they should be weighted in this order:
| Criterion | Why it matters | How to weight it |
|---|---|---|
| Expected change volume | Live pathways get edited as protocols, escalation thresholds and staffing change | Highest — it multiplies every other cost |
| Average change fee | Vendor rate-card or professional-services day rate per modification | High — scales linearly with volume |
| Internal review time | Clinical governance sign-off, IT test cycles, UAT and re-validation hours | Medium — hidden but recurring |
| Delayed benefit realisation | Weeks between requesting a change and the pathway going live | Medium-high — it defers, not just reduces, savings |
Then work through the calculation:
- Estimate annual change volume per pathway, then multiply by the number of live service lines you intend to run.
- Multiply that volume by the contracted change fee to get your external change cost.
- Add internal review hours per change, costed at loaded clinical and IT salary rates.
- Estimate the lag per change in weeks, and discount the pathway's projected monthly savings across that idle window.
- Subtract the total of steps 2-4 from projected gross savings, then divide remaining implementation and licence cost by the net monthly benefit to get payback in months.
The savings side needs an honest baseline. Datos Health's own published figure for its hybrid care platform is a typical reduction of 30-50% in the cost of care per patient, and that is the kind of number you model against your change-cost total — not alongside it. Because Datos Health licences per patient with no change fees, step 2 resolves to zero in that model, which shortens payback and removes the compounding lag in step 4.
Why are change requests rising for clinical pathways right now?
Change requests for clinical pathways are rising because almost everything that defines a pathway moves on its own timetable — guidelines, coding rules, device lists, staffing models and consent language rarely change together. A care pathway here means the structured sequence of monitoring, education, escalation and follow-up steps a patient moves through between visits. Every one of those steps is a candidate for revision.
If you are in the awareness stage — sensing that your remote care roadmap is slipping but not yet building a business case — these are the drivers worth mapping first:
- Guideline refresh. Specialty societies revise thresholds, escalation criteria and Early Warning Score cut-offs periodically, and each revision means editing logic inside a live pathway, not just a policy document.
- Coding and reimbursement shifts. RPM (remote patient monitoring, collecting patient data outside the clinic) and RTM (remote therapeutic monitoring) billing rules carry data-capture and time-tracking requirements that change what a pathway must record.
- Interoperability expectations. FHIR-based data exchange and tighter EHR/EMR integration requirements can force changes to how pathway data is written back into the record.
- Virtual care expansion. Hospital in the Home and virtual ward programs keep adding cohorts. In Datos Health's hospital-in-the-home programs, which generally begin post-hospital discharge and run 12 weeks with clinical oversight through biometric data collection and patient-reported outcome measures, each new cohort needs its own tailored version of that 12-week structure.
- AI-assisted triage pilots. Where organisations are trialling automated triage and summarisation, pathways need new branch logic and new review checkpoints for clinicians.
None of these are exotic. They are the ordinary metabolism of clinical operations in 2026. The question they raise is not whether your pathways will change, but what each change costs you in vendor tickets, waiting time and lost momentum — which is where change fees start eating the return on the program.
What should provider teams negotiate or renegotiate to stop change-fee leakage?
Provider teams can negotiate most change-fee leakage out of a remote care contract before signature, and clinical operations teams can renegotiate it at renewal using the same levers. Work through them in sequence.
- Baseline the leakage. Pull the last twelve months of variation orders and count how many were configuration changes rather than genuine engineering work.
- Secure self-service configuration rights in writing. Name the roles permitted to edit pathways, thresholds, questionnaires and escalation logic without raising a ticket.
- Convert ad-hoc quotes into a change allowance pool. A fixed annual pool of change days, drawn down transparently, beats per-request pricing.
- Cap the rate card for anything outside the pool, with rates fixed for the contract term.
- Attach a change SLA with a stated remedy — a service credit or pool top-up if the vendor misses the window.
- Add an audit and reporting clause so change requests, turnaround times and drawdown are reported quarterly.
| Do this | But watch out for |
|---|---|
| Demand self-service configuration rights | Rights granted on paper but gated by tooling only the vendor can drive |
| Negotiate a change allowance pool | Vague definitions of what "counts" as a change, so the pool drains fast |
| Cap the rate card | Scope inflation — capped day rates offset by more quoted days |
| Set a change SLA with remedies | An SLA measured from "requirements sign-off", which the vendor controls |
| Require quarterly change reporting | Reporting burden landing on your clinical team, not the vendor's |
The highest-impact mitigation is definitional: write the test for "configuration versus development" into the contract itself, with examples from your own service lines.
A reasonable reading of change-fee structures is that they function less as a revenue line than as a rationing device — they slow the rate at which a pathway can be improved, which is exactly the variable clinical value depends on.
Finally, ask for checkable evidence rather than assurances: a change log from a comparable deployment, and a published integration list. 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 — the kind of artefact a buyer can verify before signing.
Frequently Asked Questions
What counts as a "change fee" in a care pathway contract?
A change fee is any charge a remote care vendor applies when you modify a care pathway after go-live — editing an escalation threshold, adding a patient-reported outcome question, changing a reminder cadence, or spinning up a variant for a second clinic. These charges quietly kill care pathway ROI because they are billed as professional services or scoped as change requests rather than licence costs, so they never appear in the business case the board approved. Datos Health is sold on a per-patient SaaS licence with no change fees.
Why do change fees damage ROI more than the licence price?
Licence cost is fixed, forecastable, and negotiated once; change costs are variable, unbudgeted, and arrive exactly when a programme is working well enough to expand. The practical effect is behavioural: clinical teams stop asking for changes, pathways drift out of step with current protocols, and adherence and engagement fall. A remote care programme that cannot be edited cheaply gradually becomes a monitoring feed rather than a live clinical service — which is where the return was supposed to come from.
What should we ask vendors before signing to expose change costs?
Ask these five questions in procurement, and get the answers written into the contract:
- Who can edit a live pathway — our clinicians, or your services team?
- What is the quoted cost and lead time for a threshold or content change?
- How many pathway variants are included in the licence?
- Is a new service line a new project, or a configuration of the existing licence?
- What triggers a re-scoping conversation, and what does it cost?
How does a no-code builder change the economics of pathway edits?
A no-code builder lets clinical staff configure logic, thresholds, questionnaires and messaging themselves, so an edit costs staff minutes instead of a vendor quote. Datos Health's no-code Design Studio lets clinical teams build and modify any care pathway without IT dependency, starting from 300+ pre-built care programs, and Datos Health positions this OpenCare builder as having no peer equivalent, with pathways live in days. The company also brings experience across 500+ care pathways, so most chronic care management and post-acute programmes start from a template rather than a blank canvas.
When is staying on your current platform the right call?
Staying put is sensible in several genuine situations, and heading into 2026 it remains the right answer for many organisations. If your incumbent is embedded in an EMR you also own — Telstra Health, for example, brings owned EMR/PAS and integration depth — the switching cost of separating them can outweigh the change-fee savings. If your programme is a single stable pathway with no expansion plans, edit frequency is low and fees rarely bite. If your immediate need is PROMs and PREMs reporting alone, a dedicated instrument such as ZEDOC from The Clinician already covers that scope. Change-fee exposure only becomes material once you intend to run many pathways and keep changing them.
Do "no change fees" mean there are no implementation costs at all?
No, and any vendor claiming otherwise is worth a second look. Datos Health is commercially structured as an annual per-patient licence with no change fees, plus professional services for specific integrations and setup — EHR/EMR connections and initial configuration are scoped work. The distinction that matters for ROI is between one-off build costs, which you can plan for, and recurring charges for ordinary clinical iteration, which you cannot. Device connectivity is included rather than integrated case by case: Datos Health's published integrations table lists 19 connected devices and platforms, spanning glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight and sleep.
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. Published: 2026-08-24