Respiratory labs across Australia and New Zealand are increasingly walking away from long-term software contracts, and it is reshaping how vendors compete. The shift is straightforward: when a lab can leave at any time, software providers must continuously earn their place. No lock-in contracts remove the safety net that allowed mediocre platforms to persist for years, forcing a new standard of accountability, flexibility, and genuine value. For labs already under pressure from funding shortfalls, evolving accreditation standards, and growing patient demand, this is not just a commercial preference. It is a clinical one.

TL;DR

• Lock-in contracts have historically trapped respiratory labs in outdated systems, even when better options existed.

• A no lock-in model shifts power back to the lab, demanding ongoing performance from software vendors.

• Respiratory labs in Australia and New Zealand face compounding pressures from underfunding and tightening standards.

• Cloud-based, month-to-month platforms are increasingly the preferred choice for labs prioritising flexibility and clinical quality.

• Rezibase offers a 30-day free trial and no lock-in contracts, reflecting confidence in the product's ongoing value.

About the Author: This article was written by the Rezibase team, respiratory software specialists with 37 years of experience building and supporting clinical physiology labs across Australia, New Zealand, the United Kingdom, and Ireland.

Why Do Lock-In Contracts Persist in Healthcare Software?

Lock-in contracts are multi-year agreements that bind a customer to a vendor regardless of whether the product continues to meet their needs. In healthcare software, they have persisted for a simple reason: implementation is painful. Data migrations, staff retraining, system integrations, and downtime risk create a switching cost that vendors have historically relied upon to retain clients who might otherwise leave.

This dynamic has been particularly pronounced in niche clinical areas like respiratory and sleep medicine. The user base is small, the workflows are highly specialised, and for a long time, the number of credible alternatives was limited. If a lab wanted a system built for pulmonary function testing rather than a generic EMR, the options were few and the leverage was low.

The result was predictable. Labs tolerated software that was clunky, non-compliant with current guidelines, or simply not designed with scientists in mind, because the cost of changing felt greater than the cost of staying.

What Is Actually Driving Labs to Demand More Flexibility?

Several converging pressures are forcing respiratory labs to reconsider long-term vendor commitments.

Funding pressure is real and documented. The Lung Health Alliance has warned that Australia is failing to fully fund respiratory research, with lives being compromised as a result [Lives compromised, cut short as Australia fails to fully fund respiratory research - National Asthma Council Australia]. Labs operating in resource-constrained environments cannot afford to be locked into software costs that do not flex with their circumstances.

Standards are evolving faster than ever. New respiratory protection and testing standards, including updates to AS/NZS ISO 16975.3:2023, recommend annual fit testing and introduce tighter procedural expectations [Preparing for Australia’s New Respiratory Protection Standards - FAQ - Standards Australia]. Software that cannot keep pace with these changes becomes a compliance liability, not an asset.

Sustainability and practice variation are under scrutiny. Research into MDI use in Australian lung function labs has highlighted how practices can vary significantly between sites, and how small operational decisions carry broader consequences [Use of metered dose inhalers for bronchodilator responsiveness testing: laboratory practices in Australia and opportunities for carbon footprint reduction - PMC]. Labs are thinking more carefully about every system and process they operate.

Against this backdrop, a three or five-year software commitment feels increasingly out of step with how clinical environments actually evolve.

How Does a No Lock-In Model Change the Vendor-Lab Relationship?

A no lock-in contract fundamentally rebalances the relationship between a software vendor and a lab. It removes the structural safety net that locks in revenue regardless of performance and replaces it with a simple principle: if the software stops being useful, the lab stops paying.

This has several practical effects:

• Vendors must invest continuously. Feature development, compliance updates, and customer support cannot be front-loaded before signing and then deprioritised. The product must earn renewal every month.

• Labs gain negotiating power. Even if a lab has no intention of leaving, the option to leave changes how conversations with vendors happen.

• Risk is redistributed fairly. If a platform fails to update for new ATS guidelines or cannot support a new device, the lab is not contractually trapped while it waits for a fix.

• Onboarding pressure shifts to the vendor. Because switching costs are a deterrent, vendors with no lock-in have an incentive to make transitions as smooth as possible. This is the opposite of the old model, where difficult migrations kept clients captive.

Is Switching Respiratory Software Actually as Hard as It Sounds?

Switching software is a common fear, and in legacy environments, it has sometimes been justified. But the assumption that migration is always painful is increasingly outdated, particularly with cloud-based systems designed for interoperability.

Modern respiratory platforms handle data migration far more smoothly than systems from even five years ago. When a platform is built on open standards and designed by people who understand clinical physiology workflows, the transition from a previous system tends to be structured and manageable. It is a process, not a crisis.

Rezibase, for example, was built by respiratory scientists Peter Rochford and the late Jeff Pretto specifically to address the frustrations of real lab environments, including the difficulty of moving between systems. The platform supports broad integration with Patient Administration Systems, EMR systems, DICOM Modality Worklists, and Electronic Orders Systems, which means it connects to existing hospital infrastructure rather than requiring labs to rebuild around it.

The "Magic Import" function further simplifies the transition by allowing direct import of device reports from any equipment manufacturer, automatically extracting discrete data. For labs moving away from a previous system, this kind of tool reduces one of the most time-consuming aspects of switching: getting historical and ongoing device data into the new platform cleanly.

What Should Respiratory Labs Actually Look for in a Flexible Software Model?

Flexibility is not just about contract length. A genuinely flexible respiratory software solution should offer the following:

Rezibase meets each of these criteria. It is manufacturer-agnostic, meaning labs can use any device from any brand without the software dictating equipment choices. The accreditation module covers the full TSANZ/NATA and ISO 15189 requirements, including document management, training records, non-conformance tracking, and quality control using Westgard methods.

Frequently Asked Questions

What is vendor lock-in in healthcare software?
Vendor lock-in occurs when a healthcare organisation becomes dependent on a particular software provider due to contracts, data formats, or integrations that make switching costly or disruptive.

Are no lock-in contracts common in Australian respiratory software?
They are becoming more common, but they are not yet the norm. Rezibase is one of the few respiratory-specific platforms offering a transparent, month-to-month model with no long-term commitment required.

How difficult is it to migrate data from a legacy respiratory system?
With a well-designed platform and proper support, migration is manageable. Modern tools, including Rezibase's Magic Import, are built specifically to reduce the friction of transitioning between systems.

Does a no lock-in contract mean less support or commitment from the vendor?
The opposite is true. Vendors operating without lock-in contracts are incentivised to provide consistent support and development, because retention depends on ongoing performance rather than contractual obligation.

Is Rezibase suitable for both respiratory and sleep labs?
Yes. Rezibase covers both respiratory and sleep reporting within a single platform, which is a meaningful differentiator for labs that manage both service lines.

Can Rezibase integrate with existing hospital systems?
Yes. Rezibase integrates with PAS, EMR, DICOM, hospital finance systems, and electronic ordering systems, making it compatible with existing hospital infrastructure.

Is there a way to trial Rezibase before committing?
Rezibase offers a 30-day free trial, allowing labs to evaluate the platform in a real-world context before making any commitment.

About Rezibase

Rezibase is Australia's most advanced cloud-based respiratory and sleep reporting solution, purpose-built by respiratory scientists for clinical physiology labs. Trusted by over 35 sites including NHS facilities in the UK and NSW Health in Australia, Rezibase covers the full lab lifecycle from patient administration and bookings through to reporting, accreditation, and billing. Backed by 37 years of experience and developed in partnership with Cardiobase, Rezibase is built on the principle that software should work for scientists, not the other way around.

Ready to see what respiratory software looks like when it has to earn your business every month? Start your 30-day free trial or learn more at rezibase.com.