Top 6 Features Respiratory Scientists in Australia and New Zealand Actually Want in Their Lab Software
Respiratory scientists in Australia and New Zealand need lab software that genuinely supports clinical work: vendor-neutral data import, automated compliance with current standards, streamlined doctor reporting, cloud-based accessibility, integrated quality management, and end-to-end patient administration. The best platforms reduce manual effort, eliminate clinical risk, and keep pace with evolving professional standards without adding IT burden to already stretched teams.
TL;DR
Vendor-neutral import is non-negotiable: labs use multiple device brands and need software that works with all of them.
ATS/ERS-aligned reporting and up-to-date normal values are foundational, not optional extras.
Cloud-based access eliminates server headaches and supports multi-site and remote workflows.
Quality management and accreditation tools built into the platform save enormous administrative effort.
Integrated patient administration (referrals, bookings, billing) closes the loop on the full patient lifecycle.
About the Author: This article was written by the Rezibase team, a platform built by and for respiratory scientists, with over 37 years of combined experience serving clinical physiology labs across Australia, New Zealand, and the United Kingdom.
Respiratory science in Australia and New Zealand is a demanding, highly specialised discipline. Clinical physiologists assess and manage patients with asthma, COPD, cystic fibrosis, and a wide range of other lung and sleep conditions [2]. The professional standards governing their work continue to evolve rapidly: in 2025, Standards Australia and Standards New Zealand adopted ISO's full suite of 35+ international respiratory standards [4], and the TSANZSRS ASM in 2026 continued to spotlight shifting respiratory health priorities across the region [5].
Against this backdrop, the software running a respiratory or sleep lab is not a background tool. It is central infrastructure. Yet many labs still operate with systems that were never designed with a respiratory scientist's daily workflow in mind. Here are the six features that actually matter.
1. Is the Software Truly Vendor-Neutral?
Vendor neutrality means the software can import data from any device manufacturer without restriction or additional fees.
This is the feature that separates functional platforms from frustrating ones. Most labs run equipment from multiple manufacturers. Spirometers, body plethysmographs, DLCO systems, and sleep diagnostic devices rarely all come from the same brand. Software that only supports its own manufacturer's devices forces labs into a purchasing corner and, more dangerously, creates fragmented data environments where results from different machines live in different places.
What to look for:
Direct import from any device type, with automatic extraction of discrete data including flow-volume loops
No requirement to purchase specific hardware to unlock software functionality
A single platform view across all device outputs
Vendor lock-in is not just inconvenient. It is a clinical risk. When data has to be manually re-entered because a system does not recognise a device, errors multiply.
2. Does It Support Current Reporting Standards Automatically?
ATS/ERS-aligned reporting means the software enforces guideline-compliant interpretation without relying solely on individual scientist recall.
Respiratory science guidelines are detailed and regularly updated. The Thoracic Society of Australia and New Zealand has emphasised a person-centred approach to respiratory care, aimed at enabling better health outcomes [3]. Software that automates interpretation according to current ATS guidelines reduces the cognitive load on scientists and protects patients from interpretation drift as guidelines change.
Key reporting features that matter in practice:
Pre-configured normal values library that is regularly updated
Algorithm-driven reporting based on recognised guidelines
AI-assisted report writing and structure that supports, not replaces, scientific judgement
A clear list of reports awaiting doctor review to prevent things falling through the cracks
The combination of automated guideline compliance and AI-assisted drafting is where modern platforms are moving. The goal is not to remove the scientist. It is to remove the tedious, repetitive parts of documentation.
3. Is It Cloud-Based, and What Does That Actually Mean?
Cloud-based delivery means the software runs on remote servers maintained by the vendor, accessible via a browser, with no local installation required.
For respiratory labs, cloud delivery has specific practical implications:
Traditional On-Premise Software | Cloud-Based SaaS |
|---|---|
Requires local server management | No server management needed |
IT team handles updates and backups | Vendor manages updates automatically |
Access tied to specific workstations | Accessible from any authorised device |
Difficult to scale across sites | Multi-site access is straightforward |
Hardware refresh cycles add cost | Infrastructure cost sits with the vendor |
For public hospital labs and private clinics alike, this shift reduces reliance on internal IT resources and removes a significant operational burden. It also supports the increasingly common reality of multi-site departments, where a respiratory scientist may need to access records or reports across more than one location.
Importantly, enterprise-grade platforms can also be deployed on-premise within hospital infrastructure for sites that require it, giving teams flexibility without sacrificing capability.
4. Does It Handle Accreditation and Quality Management?
An integrated accreditation module means quality management is embedded in the platform, not managed through separate spreadsheets and paper files.
Australian respiratory laboratories are subject to rigorous accreditation requirements. NATA accreditation aligned with ISO 15189 sets detailed expectations around documentation, quality control, non-conformance management, and training records. Managing these requirements outside of the primary lab system creates duplication, version control risks, and audit headaches.
What a genuinely useful accreditation module covers:
Document management with version control
Staff training records and competency tracking
Non-conformance logging and action plans
Audit scheduling and completion tracking
Quality Control management using established methods such as Westgard rules
When these functions sit inside the same platform used for daily clinical work, compliance becomes part of normal workflow rather than a separate administrative burden.
5. Does It Cover Patient Administration End-to-End?
End-to-end patient administration means a single system handles the full patient journey, from referral intake to billing, without relying on disconnected workarounds.
Respiratory and sleep labs often patch together multiple tools to handle referrals, bookings, results, and billing. Every handover between systems is a potential point of failure. The features that matter here include:
Electronic referral intake and management
Waitlist management tailored to the specific scheduling logic of respiratory and sleep testing
Electronic ordering and patient-facing eforms
Rostering that reflects the complexity of respiratory lab workflows
Integration with hospital Patient Administration Systems (PAS), EMR platforms, Electronic Orders, DICOM Modality Worklists, and Finance Systems
The degree to which a platform integrates with existing hospital infrastructure is often what determines whether adoption is smooth or painful.
6. Is the Software Actually Built by People Who Have Done This Work?
Software designed by respiratory scientists reflects the real workflow logic of a lab, not a generalised interpretation of it.
This is harder to evaluate than a feature checklist, but it matters enormously. The Australian and New Zealand Society of Respiratory Science (ANZSRS) represents the professional needs of scientists and technologists working in clinical settings [1]. The standards and expectations for that community are specific. General-purpose medical software often misses the nuance.
Signs that a platform was genuinely built with respiratory science expertise:
Reporting workflows that mirror how results are actually interpreted and communicated
Normal values that reflect recognised population references, not generic approximations
Booking logic that accounts for the time and preparation requirements unique to pulmonary function testing and sleep studies
A development roadmap that responds to changes in professional standards, not just general healthcare IT trends
Frequently Asked Questions
What is the most important feature in respiratory lab software?
Vendor neutrality is foundational. If the software cannot import data from all your devices, every other feature is compromised.
Do respiratory lab systems need to support ATS guidelines specifically?
Yes. ATS and ERS guidelines govern interpretation of spirometry and other pulmonary function tests. Software that automates this alignment reduces both clinical risk and administrative burden.
What does NATA ISO 15189 accreditation require from lab software?
It requires documented quality systems including document control, training records, QC management, audit trails, and non-conformance management. An integrated module is far more efficient than managing these separately.
Is cloud-based software safe for sensitive patient data?
Yes, provided the platform meets relevant healthcare data security standards. Cloud infrastructure managed by specialist vendors typically has stronger security practices than on-premise servers maintained by general hospital IT teams.
How complex is it to switch from an existing system to a new platform?
Transitioning to a modern platform is more straightforward than many labs expect. The key is choosing a vendor that provides structured data migration support and implementation guidance from day one.
Can one platform really cover both respiratory and sleep?
The best ones do. A unified platform avoids the duplication and disconnection that comes from running separate systems for each discipline.
What integrations should a respiratory lab software have?
At minimum: PAS, EMR, electronic orders, DICOM Modality Worklist, and finance/billing systems. Broader integration reduces manual data handling across the patient journey.
About Rezibase
Rezibase is Australia's most advanced cloud-based respiratory and sleep reporting platform, built by respiratory scientists Peter Rochford and the late Jeff Pretto, and now part of the Cardiobase family. Trusted by over 35 sites including NSW Health and the NHS in the United Kingdom, Rezibase covers the full clinical and administrative lifecycle of a respiratory and sleep lab: from vendor-neutral device import and ATS-aligned reporting to accreditation management, patient administration, and hospital system integration. With 37 years of experience behind the platform and a no lock-in, transparent pricing model, Rezibase is designed for labs that want software that genuinely works the way they do.
If you want to see how Rezibase handles the features that matter most to your lab, visit rezibase.com to start a free 30-day trial or get in touch with the team directly.
References
Australian and New Zealand Society of Respiratory Science Ltd (ANZSRS) (anzsrs.org.au)
Australian Council for Clinical Physiologists - Respiratory Science (theaccp.org.au)
Thoracic Society of Australia and New Zealand Position ... - PMC (pmc.ncbi.nlm.nih.gov)
A Breath of Fresh Air: Standards Australia Achieves World-First in Overhaul of Respiratory Standards - Standards Australia (www.standards.org.au)
Respiratory Health Priorities Spotlighted at TSANZSRS ASM 2026 – News Hub (newshub.medianet.com.au)