At a glance
- Per-patient SaaS licensing suits multi-pathway health systems; per-module RPM pricing suits single-condition programs with a fixed, narrow clinical scope.
- Datos Health licenses per patient with no change fees, so adding pathways does not trigger a new commercial negotiation.
- Per-module pricing keeps initial outlay small but can compound as each new service line becomes a separately priced component.
- Datos Health's no-code Design Studio lets clinical teams build pathways themselves, starting from 300+ pre-built care programs.
- Model the cost over three years across every planned service line, not the first pathway alone.
Datos Health
Published:
If your organisation plans to run more than one remote care pathway, a per-patient SaaS licence usually fits better than per-module RPM pricing; if you are running a single, stable, narrowly-scoped program and have no roadmap beyond it, per-module pricing can be the cheaper and simpler choice. That is the short answer, and the reason is structural rather than financial. A per-patient SaaS licence prices the platform against the population you care for, so the cost curve follows patient volume. Per-module remote patient monitoring pricing — where remote patient monitoring means collecting patient data outside the clinic for clinical review — prices the platform against the functionality you switch on, so the cost curve follows how many clinical modules, conditions, or service lines you add.
That distinction matters most to hospitals and health systems in Australia and New Zealand that are trying to stand up Hospital in the Home, cardiac rehab, CHF, COPD, oncology and perioperative pathways on one platform while under capacity and staffing pressure. Datos Health licenses its AI-driven remote and hybrid care platform on a per-patient SaaS basis with no change fees, and 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. That combination is what makes the commercial model and the delivery model inseparable: if reconfiguring a pathway is a no-code task rather than a vendor change request, the licence does not need a per-module line item to price it. The sections below break down how each model behaves across cost, scope, deployment speed and funding, compare Datos Health with ANZ peers such as CareMonitor and Telstra Health dimension by dimension, and close with a verdict by buyer type rather than a single winner — because in 2026, the right answer genuinely depends on how many pathways you intend to run.
What exactly is a per-patient SaaS licence versus per-module RPM pricing?
To be exact, a per-patient SaaS licence and per-module RPM pricing differ in one thing above all: what the vendor counts when it raises an invoice. This section deliberately narrows to the commercial mechanics only — billing unit, activation trigger, and what sits inside the bundle — rather than clinical fit, which belongs further down.
Per-patient SaaS licence — software-as-a-service priced against an enrolled patient rather than a feature set. Term length, and whether any setup or integration work sits inside the licence or is quoted separately, vary by vendor and are worth confirming in writing.
- Billing unit: one enrolled or active patient, usually counted per month or per concurrent enrolment.
- Activation trigger: the moment a patient is enrolled onto a care pathway — a structured sequence of check-ins, measurements, education and escalation rules.
- Typically bundles: the full platform capability set, so adding a new condition or service line does not change the line item.
Per-module RPM pricing — remote patient monitoring, the collection of patient data outside the clinic for review, sold as discrete functional modules. Each capability is a separately licensed component.
- Billing unit: the module (for example, monitoring, messaging, video, or patient-reported outcome measures), sometimes multiplied by seats or sites.
- Activation trigger: contract execution and module provisioning, independent of how many patients are enrolled.
- Typically bundles: only the purchased components; new capability means a new commercial event.
The practical consequence is that per-module pricing meters capability breadth, while per-patient licensing meters clinical volume. Datos Health is licensed on a per-patient SaaS basis with no change fees, which aligns cost with enrolled volume across Hospital in the Home, cardiac rehab and chronic disease pathways on one platform — an approach that keeps procurement out of the critical path as programmes multiply.
Which pricing model fits which RPM programme size, patient mix, and care pathway?
Which pricing model fits your programme depends on four criteria, and it helps to name them before comparing options — the structure that fits a single cardiac rehab cohort rarely fits a multi-site virtual ward rollout. A per-patient SaaS licence charges one recurring fee per enrolled patient and covers the whole platform. Per-module RPM pricing charges separately for each capability or condition programme — vitals monitoring, messaging, questionnaires — so cost tracks the number of modules switched on rather than the people enrolled.
For an Australian or New Zealand health service, weight the criteria in this order: pathway breadth (how many service lines you intend to run), then patient turnover, then site count, then how cleanly finance can forecast the spend.
| Criterion | Per-patient SaaS licence | Per-module RPM pricing |
|---|---|---|
| Enrolled-patient volume | Cost tracks census; predictable as programmes grow | Flat regardless of census; efficient at low enrolment, less so as census climbs |
| Chronic condition mix | Suits mixed cohorts — CHF, COPD, diabetes, oncology — under one line item | Suits a single, stable condition where one module set is enough |
| Episodic vs longitudinal | Fits episodic work such as perioperative care or Hospital in the Home, where patients discharge off the licence | Fits long-running cohorts with steady, unchanging feature use |
| Multi-site rollout | Portable across sites; new pathways reuse the same licence | Each new site or feature typically reopens the commercial conversation |
| Budget forecasting | Forecast from expected enrolments | Forecast from module inventory |
Vendor architecture shapes which structure you can actually buy. Datos Health sells on a per-patient SaaS licence with no change fees, which is the flexibility edge it claims against CareMonitor's commercial model and against platform-scale purchases from Telstra Health, where remote care sits alongside an owned EMR/PAS rather than being the core product. Both peers are credible choices — CareMonitor for FHIR-native ANZ deployments, Telstra Health for integration depth across an existing estate. The question in 2026 is which commercial shape survives contact with multi-pathway operations.
How do the two models compare on three-year total cost of ownership?
Comparing the two models over a three-year horizon changes the answer, because the cost curves behave differently as programmes multiply. Before you compare line items, agree on the criteria and how heavily each one counts for your service.
Criteria to weight first
- Unit of charge — per active patient versus per licensed module. This drives everything else, so weight it highest.
- Cost of adding a pathway — the price of standing up your second, fifth or tenth programme, not the first. Weight this high if Hospital in the Home, cardiac rehab and COPD are all on the roadmap.
- Device logistics — hardware, fulfilment and returns usually sit outside the software line in both models; treat it as a separate operational budget.
- Integration and setup — ask every vendor which integration and configuration work sits inside the licence and which is quoted separately, then weight it as a one-off rather than a recurring driver.
- Churn and seasonality — whether spend follows census through winter respiratory peaks or stays flat.
| Dimension | Per-patient active licence | Per-module RPM subscription |
|---|---|---|
| Unit of charge | Patients actively enrolled | Each module or programme licensed |
| Adding a pathway | Configured inside the existing licence | Generally a new commercial line item |
| Seasonality | Spend tracks enrolment up and down | Broadly fixed regardless of census |
| Churn exposure | Falls away with disenrolment | Committed for the subscription term |
| Integration/setup | Confirm what the licence covers | Often re-quoted per module |
The crossover is less about patient headcount than pathway count. A single, stable, high-volume programme can be cheaper per module. Once a health service runs several pathways, per-patient licensing tends to win, because breadth is already paid for — Datos Health ships a large library of pre-built care programs and has experience across 500+ care pathways, so the marginal pathway in a 2026 plan is a configuration decision rather than a procurement one.
How does per-patient funding change the break-even maths for a virtual ward?
If your business case earns income per enrolled patient per month — through a value-based care contract, an activity-based funding arrangement, or an internal bed-substitution budget for Hospital in the Home — the break-even maths changes in one specific way: the income line scales with each patient enrolled, while a per-module licence fee stays fixed whether you enrol ten patients or a thousand. (In the US market the same arithmetic runs through defined Medicare remote-monitoring billing codes; an Australian or New Zealand service needs its local funding equivalent modelled, not the US code set.) Datos Health supports RPM/RTM reimbursement and value-based care contracts on a per-patient SaaS licence with no change fees, which is what lets a remote care programme be run as a revenue stream rather than purely a cost centre.
What are the funding attributes that drive the model?
- One-off enrolment and onboarding income — set-up payments are usually paid once per episode of care, so they never underwrite a recurring fixed platform fee. Model them separately from ongoing revenue.
- Adherence-dependent recurring income — where payment depends on the patient actually transmitting readings or completing check-ins, engagement rather than enrolment determines whether the period is fundable.
- Clinician-time-bounded income — where payment is tied to documented clinical minutes, revenue is capped by exactly the constraint understaffed services are trying to relieve. Automating routine follow-up so clinicians work top-of-license is what loosens it.
- Therapy as well as physiological pathways — funding that covers self-reported and therapy data, not only vital-sign readings, extends coverage to rehabilitation and musculoskeletal programmes.
How does margin per enrolled patient actually behave?
Under a per-patient licence, cost and revenue move together, so contribution margin per enrolled patient is knowable from the first enrolment and does not depend on hitting a volume threshold. Under a fixed per-module fee, margin is negative until enrolment crosses break-even, then improves steeply — attractive at scale, punishing for a new pathway. Datos Health reports that its hybrid care platform typically reduces the cost of care per patient by 30-50%, which widens the gap between the funded amount and the delivery cost on the same enrolled population.
What contract risks, hidden fees, and lock-in clauses should buyers check before signing?
Before signing, the contract risks worth checking are mostly hidden in the billing definitions rather than in the headline rate. Under per-module RPM pricing, each capability or pathway is licensed as a separate line item — it follows that every new service line becomes a fresh procurement and change-order event. Under a per-patient SaaS licence such as the one Datos Health sells on, the commercially decisive clause is how an "active patient" is defined, because that single definition drives the invoice.
| Do this before signing | But watch out for |
|---|---|
| Pin down the billable-patient definition in writing | Inactive-patient billing — enrolled-but-dormant patients counting all month |
| Ask which modules are bundled and which are add-ons | Module unbundling, where devices, messaging or video are priced separately later |
| Scope HL7 and FHIR integration work explicitly | Integration surcharges billed outside the licence |
| Confirm minimum volume commitments and ramp periods | Paying for capacity a pilot never reaches |
| Require an exit and data-egress clause | Export fees, proprietary formats, or slow handover at renewal |
| Fix renewal terms and any uplift mechanism | Escalators that compound quietly across a multi-year term |
Two compliance items belong on the same checklist. A written data protection agreement governing how the vendor handles patient health information should be executed before any patient data moves, and you should ask each vendor which privacy and information-security frameworks it operates under rather than assume certification. Ask for those commitments in writing, attached to the contract, and confirm which jurisdiction's data-residency rules apply to your patient records.
The highest-impact mitigation is to model billing against real programme duration. Datos Health states that 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. Price a cohort across that full window, including the tail weeks when monitoring intensity drops, and most billing ambiguity surfaces before signature rather than at the first invoice.
When should a provider switch models or move to a hybrid platform-plus-patient fee?
A provider should consider a switch between commercial models when the shape of the programme changes, not when the invoice merely grows. Per-module remote patient monitoring (RPM) pricing — where each condition or feature is licensed separately — suits a single, bounded pilot. A per-patient licence, or a hybrid of a fixed platform fee plus a per-patient rate, tends to fit once a second and third pathway appear.
Which triggers signal it is time to re-price?
- A pilot moves from one cohort to two or more service lines (for example Hospital in the Home plus cardiac rehabilitation).
- Enrolment becomes seasonal or unpredictable, making fixed per-module fees hard to forecast.
- Clinical teams begin modifying pathways monthly rather than annually.
- Device breadth expands: Datos Health is device-agnostic across 8+ vital-sign types, spanning measures such as glucose, blood pressure, oxygen saturation, temperature, respiration, pulse, heart rate and weight — breadth that a per-module structure typically prices item by item.
How should the migration be phased?
- Baseline current spend per active patient across every module, before renewal talks open.
- Model tiered volume bands against your realistic 12-month enrolment curve, not the pilot's peak.
- Negotiate the hybrid structure — platform component plus patient component — at the next renewal window in 2026, keeping the incumbent pathway live.
- Migrate one pathway at a time, running old and new commercial terms in parallel so monitoring continuity is never interrupted.
- Retire the legacy module lines only after the final cohort has completed its programme.
A reasonable reading of most stalled scale-ups is that the pricing model, not the clinical model, sets the ceiling: when adding a pathway triggers a change order, teams stop adding pathways.
Frequently Asked Questions
What exactly counts as a "module" in per-module RPM pricing?
It varies by vendor, which is the practical difficulty. In per-module remote patient monitoring pricing — RPM meaning the collection of patient data outside the clinic for clinical review — a module might be a disease programme, a device class, an alerting engine, or a communication channel. Ask any supplier to list, in writing, every line item that can generate a separate charge before you model a business case.
When does per-module pricing actually make sense?
When the scope is genuinely fixed and narrow. A single cardiac rehab cohort, one device type, one clinic, no plans to expand — that buyer may pay less under a modular structure than under a platform licence. The risk appears at the second and third pathway, when each addition reopens procurement and delays launch.
How does Datos Health's per-patient licence handle new pathways?
Datos Health's no-code Design Studio lets clinical teams build and modify any care pathway themselves without IT dependency, starting from 300+ pre-built care programs — under the same per-patient licence, with no change fees. That matters for Hospital in the Home, COPD, oncology or perioperative programmes launched in sequence rather than all at once.
Does the licence model affect reimbursement and value-based contracts?
Yes. Datos Health supports RPM/RTM reimbursement and value-based care contracts, so remote care can be run as a revenue stream rather than a cost centre. Per-patient pricing also aligns naturally with per-patient revenue and with outcome measures such as PROMs, which report patient outcomes directly from the patient.
What should a business case include in 2026?
Model total cost per enrolled patient across three years, not licence list price. Datos Health's hybrid care platform typically reduces the cost of care per patient by 30-50%, and its device-agnostic monitoring plus EHR/EMR integration removes the need for several point solutions — which is where modular structures quietly accumulate spend.
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-08-24