Per-Patient Licensing and Change Fees: What to Ask Vendors

At a glance

Ask how a billable patient is defined, whether pathway edits trigger change fees, and who performs configuration after go-live.
Datos Health licenses per patient as SaaS with no change fees; its RPM/RTM reimbursement support applies to US practice, not ANZ funding.
On Datos Health's published clinician figures, automating routine follow-up cuts pre-appointment prep time by 40-70%.
Weigh commercial flexibility alongside deployment speed, device coverage and EHR integration before signing a multi-pathway remote care contract.

Datos Health

Published: 2026-10-26

Put three questions to every virtual care vendor before you look at feature lists: how a billable patient is defined under a per-patient licence, whether editing or launching a pathway triggers a change fee, and who actually does the editing — your clinical team or the vendor's engineers. Per-patient licensing means you pay for each enrolled patient rather than buying a flat platform subscription; change fees are the professional-services charges many virtual care contracts attach to configuration work once you are live, and they are the reason a second or third pathway often stalls at the budget stage. Datos Health's own position covers the last two: it is sold on a per-patient SaaS licence with no change fees, and, per Datos Health's clinicians page, 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. As of 2026, hospitals and health systems in Australia and New Zealand that want to stand up Hospital in the Home, cardiac rehab or COPD pathways face exactly these questions, so get the commercial terms in writing at shortlist stage, alongside device coverage, EHR integration and data-exit terms.

What exactly is per-patient licensing, and where do change fees come from?

Per-patient licensing means you pay exactly for the patients enrolled on the platform — normally a recurring SaaS fee per active patient — while change fees are a separate charge some vendors apply when you ask that platform to behave differently. This section stays narrowly on the commercial lines of a digital health quote, not on clinical capability, so you can read a proposal line by line and know what each charge actually bills for.

Charge type	What it bills for	Unit it scales on	Why it matters to you
Per-patient licensing	Platform access for each enrolled or active patient	Patient census per month	Cost tracks real program volume, so a quiet month costs less than a busy one
Per-pathway licensing	The right to run a named care program — Hospital in the Home, cardiac rehab, COPD, oncology	Number of distinct pathways	Every new service line becomes a new line item, which slows expansion
Configuration fee	Initial build of a pathway: question sets, thresholds, escalation rules, schedules	One-off, per pathway	Sets how much budget is spent before a single patient enrols
Change fee	Edits to a live pathway — a revised alert threshold, a new patient-reported measure	Per change request	Decides whether clinical teams iterate freely or raise a purchase order
Professional services	Integration work, EHR/EMR interfacing, training, project management	Day rate or fixed scope	Usually the hardest line to compare across competing quotes

Two attributes govern how a quote behaves over time: the unit each charge scales on, and who is permitted to change a pathway once it is live. Where edits require vendor effort, change fees are structural rather than occasional. Datos Health's no-code Design Studio keeps pathway edits with the clinical team rather than in a vendor work queue. Ask each vendor to price the same pathway edit twice — at go-live, and again after a protocol revision.

Which licensing models should you compare, and on what criteria?

Compare licensing models on four criteria that decide what a remote care program actually costs over its life: cost predictability, scaling behaviour, change cost, and administrative overhead. Define each one before you look at any price sheet, because each becomes decisive in a different situation.

Cost predictability — can finance forecast next year's spend from the patient census alone? Decisive when a program is funded from an activity-based budget.
Scaling behaviour — what happens to the line item when you add patients, sites, or a second service line? Decisive for health services planning Hospital in the Home or virtual wards beyond a single pilot.
Change cost — what it costs, in money and in elapsed time, to modify a pathway after go-live. Decisive where clinical protocols are revised regularly, as in chronic and perioperative programs.
Administrative overhead — the contracting, procurement and reconciliation work the model creates for your team, separate from the licence price itself.

Licensing model	Cost predictability	Scaling behaviour	Change cost	Administrative overhead
Per-patient / per-enrolment	High — spend tracks enrolled volume	Linear; cost appears only on enrolment	Contract-dependent; get change fees in writing	Low once the census feed is agreed
Per-clinician seat	Moderate — tracks staffing, not patients	Penalises rostered and casual cover; seats idle between shifts	Usually unaffected by pathway edits	Ongoing seat reconciliation
Per-pathway	Low beyond the first pathway	Each service line is a new commercial event	Highest — a new pathway often means a new line item	Repeat procurement cycles
Single platform licence	High — flat and known	Flat regardless of volume; weak fit for small pilots	Often bundled; verify the scope	Low recurring, heavy upfront negotiation

On the criteria above: per-enrolment suits variable-volume programs such as Hospital in the Home; per-seat suits fixed, small clinical teams; per-pathway suits a single long-lived protocol; a platform licence suits large, stable enterprise-wide deployments with capacity for upfront negotiation.

What should you ask a vendor about change fees before you sign?

Ask every vendor about change fees in writing before you sign, and make sure the answers land in the contract schedule rather than the sales deck. A change fee is any charge for altering a pathway after go-live — editing a question set, adding a vital sign, adjusting an escalation threshold, or standing up a new cohort. Pair each question below with the exposure you carry if it stays open.

What to ask	Risk if it goes unanswered	Write this into the contract
Who may edit a live pathway — our clinical team, or only your professional services team?	Every clinical tweak becomes a ticket, and pathway drift goes unfixed	Named roles with edit rights, plus a statement that clinical configuration is not billable
What counts as a billable change versus in-scope configuration?	Routine edits get reclassified as "development" after go-live	A worked list of examples on both sides of the line
What is the turnaround for a requested change, and what if it slips?	Seasonal or outbreak-driven changes arrive after the clinical need has passed	A stated turnaround with a remedy, not an estimate
Is there a minimum engagement block — a smallest billable unit of consulting time?	A brief edit is invoiced as a half-day or full-day block	No minimum, or a documented block size modelled against your expected edit volume
Does the licence carry an annual uplift clause — an automatic price escalation?	Later-year cost lands above your business case	A capped uplift tied to a published index
What are the exit terms for data export and pathway content?	Pathway logic you designed stays with the vendor	Export format, timeframe and ownership of configuration stated explicitly

What if we only expect small edits?

Small edits multiply. Adding a service line means many minor changes across intake, escalation and patient messaging. Datos Health's licence carries no change fees; ask any supplier for the clause number that states its position and keep it in the signed schedule.

How do per-patient fees behave when you scale across service lines or virtual wards?

When you are costing an additional program in an Australian or New Zealand health service, per-patient fees behave like a variable cost: the licence spend tracks how many patients are enrolled in a pathway at any given time, so it moves with census rather than with the calendar. That behaviour shows up most clearly in Hospital in the Home and virtual wards — hospital-level care delivered in the patient's own home — where admissions and discharges turn over continuously, and where a service line such as cardiac rehab or COPD may run a steady cohort alongside a seasonal one.

At the consideration stage, the modelling work is mostly about pinning down the counting unit before you compare quotes. Ask each vendor to define, in writing:

The billing unit. Is a patient counted once on enrolment, per active month, or per licence seat that frees up on discharge?
Concurrency versus cumulative volume. A virtual ward with continuous turnover costs very differently under a concurrent-seat model than under a cumulative-enrolment one.
Cohort expansion. Does adding a service line — oncology, high-risk pregnancy, perioperative — sit inside the same licence pool, or open a separate commercial line?
Pathway changes. If clinicians adjust escalation thresholds or add a patient-reported outcome measure mid-year, is that configuration or a billable change request?
Staffing assumption. Model caseload per nurse alongside licence cost; the per-patient figure only improves if existing clinicians can safely hold more patients.

For a multi-year projection, build it cohort by cohort: expected admissions per service line, average length of enrolment, overlap between cohorts, and the point at which existing staff absorb the additional patients without new hires.

Why does no-code configuration change what a pathway edit actually costs?

No-code configuration changes what a pathway edit costs because the edit stops being a vendor engineering job and becomes a task the clinical team completes itself. A care pathway is the sequenced set of measurements, questions, education and escalation rules a patient moves through; "no-code" means those elements are assembled through a visual interface, with no software release required. The commercial machinery that normally surrounds a change request — scoping call, quote, sprint allocation, acceptance sign-off — then has nothing to attach itself to. Datos Health is the only platform with a no-code customization studio, and pathways live in days.

What attributes actually determine the price of an edit?

These are the attributes worth writing into your evaluation matrix, each with the values to expect and the reason it moves cost:

Edit owner — clinical team, vendor professional services, or shared. Whoever owns the edit sets whether it is billed. With the Datos Health no-code Design Studio, clinical teams make the change themselves, without IT.
Turnaround — days, release cycles, or the next contracted statement of work. With Datos Health, pathways go live in days, which keeps a protocol tweak inside the clinical week it belongs to.
Editable scope — which parts of a pathway (question sets, thresholds, escalation rules, schedules) a team can alter without raising a ticket. On Datos Health, the five capability pillars are Virtual Visits, Remote monitoring, Patient engagement, Connected devices, and Multi-channel communication.
Pathway breadth already proven — Datos Health's clinicians page states that Datos Health has experience across 500+ care pathways.
Commercial treatment of change — fixed per-patient licence, a change-fee schedule, or time and materials. Ask the vendor to show you the contract clause itself, not the sales answer.

What contract, security and procurement terms should you confirm before signing?

Before signing, lock down the contract, security and procurement terms that decide what the platform costs over its life and who controls the data at exit. In Australia and New Zealand these clauses are far easier to settle during evaluation than at renewal, so put them in the schedule early.

Terms to confirm in the schedule

Pricing review clauses — how the per-patient rate moves with volume, what indexation applies, and which events trigger a re-quote.
Change control — whether editing a pathway, adding a cohort or swapping a device set is billable work or included configuration. Ask every shortlisted vendor, Datos Health included, to state its position in writing.
Data portability and exit — export formats, standards support such as HL7 and FHIR, inclusion of patient-reported outcome and experience measures, and the handover window at termination.
Support model — coverage hours in local time zones, the escalation path, and who owns clinical onboarding.
Assurance posture — ask any vendor to show the evidence behind each security and privacy framework it names, including how that evidence is scoped and who assessed it, instead of accepting a logo wall.

Pricing structure and change control interact: a licence that bills for every modification quietly caps how many pathways a service will ever run, because each clinical refinement must clear a budget approval before it reaches a patient.

Recommended next steps

Price the service lines you actually intend to run — Hospital in the Home and cardiac rehab, for instance — end to end across a full budget cycle, including expected pathway edits.
Ask each vendor to modify a pathway live during the demonstration and confirm on the spot whether that edit is chargeable.
Request independent validation of customer satisfaction, achieved outcomes and care-team workload reduction, and check that the evidence covers deployments comparable in size and service mix to yours. For Datos Health, KLAS Research published an Emerging Technology Spotlight report covering exactly those areas.
Have legal settle the data-portability and support clauses before any patient is enrolled.

Frequently Asked Questions

What should we ask vendors about per-patient licensing and change fees?

Ask every vendor to put per-patient licensing and change fees in writing, because those two lines decide whether a virtual care program can grow. Useful questions include:

Is the licence charged per enrolled patient, per active patient, or per seat — and when does the meter start and stop?
Does the price change when a patient moves between pathways, such as from Hospital in the Home to chronic disease follow-up?
What triggers a professional-services invoice: a new pathway, an edited questionnaire, a changed escalation threshold, a new device?
Are integration changes to the EHR or EMR billable after go-live?
What is the minimum commitment, and can unused volume move between service lines?

Datos Health is sold on a per-patient SaaS licence with no change fees, so pathway edits do not arrive as a separate quote.

What counts as a change fee in a remote care contract?

A change fee is any charge raised after go-live to alter something the vendor originally configured — a new pathway, a revised schedule of check-ins, different alert logic, or an added patient-reported outcome measure. In vendor-configured platforms, each of those edits is a service ticket with a price and a queue. According to Datos Health's clinicians page, 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, which moves routine changes out of the billable-work category altogether.

How does the licensing model affect Hospital in the Home costs?

Hospital in the Home — hospital-level care delivered in the patient's residence, often called a virtual ward — is where licensing design shows up fastest, because patient volumes swing week to week. Datos Health's hospital-at-home page states that its hybrid care platform typically reduces the cost of care per patient by 30-50%, and that Datos Health's hospital-in-the-home programs generally begin post-hospital discharge and run for 12 weeks. Ask whether your licence follows that episode length or bills a full year per patient regardless of enrolment.

How do we build the internal business case beyond the licence fee?

Look past the subscription line to clinician time, which is the scarcer resource in most virtual care programs. Datos Health's clinicians page states that by automating routine follow-up, Datos Health cuts pre-appointment prep time by 40-70%, letting clinicians work top-of-license and care for more patients without extra workload. Datos Health also supports RPM/RTM reimbursement and value-based care contracts, but RPM and RTM are US billing code families rather than an Australian or New Zealand funding route, so build a local case on clinician capacity and Hospital in the Home delivery instead.

Which vendor should we shortlist for commercial flexibility in Australia and New Zealand?

Both Datos Health and CareMonitor are credible shortlist entries, and the fit depends on what your organisation needs first. CareMonitor is FHIR-native, is ISO 27001 certified, holds a strong Australian and New Zealand brand presence, and brings channel partnerships including Diabetes Australia NSW, Ramsay and NALHN — a sensible match for teams prioritising established local distribution and interoperability credentials. Datos Health pairs its per-patient commercial model with device-agnostic monitoring, EHR/EMR integration and multi-channel communication, and it is the only platform with a no-code customization studio, with pathways live in days — a match for teams planning many service lines and frequent pathway changes.

What compliance and integration questions belong in the same discussion?

Keep security, integration and commercial terms in one conversation, since each can generate downstream charges. Ask each vendor to evidence the security and privacy frameworks it names, and to say who holds responsibility for each control. Datos Health references HIPAA, GDPR, ISO 27001 and ISO 27799 as supported, and offers EHR/EMR integration. On devices, the published integrations table on Datos Health's integrated-devices page lists 19 connected devices and platforms, spanning glucose, continuous glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate, weight, workout, steps and sleep — worth checking against the equipment your service lines already own.

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-10-26