Running a respiratory lab with more than one spirometer brand is the norm, not the exception. Yet most pulmonary function test software was built as if every lab uses a single device from a single manufacturer. The result is fragmented data, duplicated effort, and reporting workflows that create more work than they save. This guide explains why multi-device data consolidation matters, what the practical barriers are, and how modern lab systems are solving it.

TL;DR

• Most respiratory labs operate multiple spirometer brands, but legacy software treats each device as a silo.

• Fragmented data creates double entry, inconsistent reporting, and increased clinical risk.

• Vendor-neutral import tools can pull discrete data, including flow-volume loops, from any device into a single system.

• Consolidation does not require replacing your devices, only upgrading the software layer above them.

• Platforms like Rezibase are purpose-built to solve this exact problem, without locking you into any manufacturer.

Why Do Labs End Up With Multiple Spirometer Brands in the First Place?

Multi-device environments are a natural consequence of how labs grow. Equipment is replaced on different budget cycles, departments merge, clinics expand, or a preferred device is simply discontinued. Over time, a lab can end up with devices from two or three different manufacturers, each generating data in its own proprietary format.

This is not a niche problem. According to recommendations published in Archivos de Bronconeumología in 2026, spirometry remains the primary diagnostic procedure for most respiratory diseases, which means the volume and clinical weight of this data is significant. When that data lives in disconnected silos, the downstream consequences are real.

What Goes Wrong When Spirometer Data Is Not Consolidated?

The problems are operational, clinical, and administrative:

• Double data entry: Technicians manually re-enter values from one system into another, introducing transcription errors.

• Inconsistent normal values: Different devices may apply different reference equations, making longitudinal comparisons unreliable.

• Fragmented patient records: A patient tested on two different devices over time may have no single, unified record.

• Reporting delays: Doctors reviewing results have to chase data across systems rather than working from one queue.

• Audit and accreditation risk: Incomplete records make it harder to demonstrate compliance with standards like ISO 15189.

The guidance on best practices for spirometry testing in occupational health settings, documented via Scribd, reinforces that personnel requirements and data integrity are central to a defensible testing program. Fragmentation undermines both.

What Does "Vendor-Neutral" Actually Mean for Pulmonary Function Test Software?

Vendor-neutral means the software layer is completely independent of the device manufacturer. It can accept, interpret, and store data from any spirometer brand without requiring a proprietary connection or a commercial agreement with that manufacturer.

In practice, this means:

The distinction matters enormously when a lab upgrades equipment. With vendor-locked software, a hardware change can trigger a software change, a migration, and a retraining cycle. With a vendor-neutral platform, the software simply absorbs the new device.

How Does Data Actually Get From Multiple Devices Into One System?

This is where the practical mechanics matter. There are three common approaches:

1. Manual export and upload
The technician exports a report from the device, then uploads it to the lab system. Simple, but still manual and prone to inconsistency.

2. Direct integration via HL7 or DICOM
The device communicates directly with the lab system using a standard protocol. Reliable, but requires both the device and the software to support the same standard, and often requires IT involvement.

3. Intelligent document import
The software automatically extracts discrete data from device-generated reports, including structured values and graphical outputs like flow-volume loops. This approach does not require the device to "speak" a particular protocol. It reads the output the device already produces.

Rezibase uses this third approach through its Magic Import feature, which pulls discrete data directly from device reports regardless of the originating manufacturer. For labs with legacy equipment that does not support modern integration protocols, this is often the most practical path forward.

Is Switching from One Lab System to Another Complicated?

The short answer is: less complicated than most labs expect. The concern around data migration is understandable, but modern platforms are designed to make the transition straightforward.

A few practical realities:

• Historical data can travel with you. Most modern systems support structured data import from predecessor platforms. If you are moving from a system like Respiro to Rezibase, the process is managed and guided, not a cliff edge.

• You do not need to migrate everything on day one. A phased approach, where new data flows into the new system while historical records remain accessible, is a common and workable strategy.

• Cloud-based platforms remove the infrastructure burden. There is no server to configure, no local installation to manage, and no IT project to run before you can start.

The goal of any migration should be a cleaner, more connected workflow on the other side. The transition is a means to that end, not a barrier to it.

What Should Labs Look For in a Consolidation-Ready Lab System?

Not all pulmonary function test software is built for multi-device environments. When evaluating options, prioritise these capabilities:

• Device-agnostic import: Can the system ingest data from your specific device brands without custom development?

• Discrete data extraction: Does it capture individual numeric values and graphical data, or just a PDF image?

• Unified normal values library: Is there a single, configurable reference equation library applied consistently across all imported data?

• ATS-aligned reporting: Does the reporting workflow follow current ATS guidelines regardless of which device generated the raw data?

• Integration with hospital systems: Can it connect to your PAS, EMR, and electronic orders systems to avoid creating yet another silo?

• Accreditation support: Does it support ISO 15189 requirements, quality control, and audit trails in one place?

Rezibase was built by respiratory scientists specifically to address these requirements. It is manufacturer-agnostic by design, not as an afterthought.

Frequently Asked Questions

Can we keep our existing spirometers and just change the software?
Yes. A vendor-neutral platform sits above your devices. You do not need to replace hardware to consolidate data.

What happens to our historical patient data if we switch systems?
Historical data can be migrated. The process is guided and does not require you to start from scratch.

Does each device brand need a separate licence or integration agreement?
With a vendor-neutral system like Rezibase, no. The platform is designed to handle multiple device types under a single subscription.

How are normal values handled when data comes from different devices?
A centralised normal values library applies consistent reference equations across all imported data, regardless of source device.

Is a cloud-based system secure enough for clinical data?
Enterprise-grade cloud platforms are built to meet healthcare data security requirements and can also be deployed on-premises for hospitals that require it.

How long does it take to get a new system running?
Timelines vary, but cloud-based platforms significantly reduce setup time by eliminating server installation and local IT configuration.

What if our lab needs accreditation support as well?
Look for a platform that includes quality control, document management, and audit tools aligned to TSANZ/NATA and ISO 15189 standards.

About Rezibase

Rezibase is Australia's most advanced cloud-based respiratory and sleep reporting platform, built by respiratory scientists for respiratory labs. It is manufacturer-agnostic, integrates with major hospital systems, and is trusted by over 35 sites including NHS and NSW Health facilities. Learn more at rezibase.com.

References

• Archivos de Bronconeumología. Recommendations for Performing Spirometry. https://www.archbronconeumol.org/es-recommendations-for-performing-spirometry-articulo-S0300289626000128

• Scribd. Best Practices for Spirometry Testing. https://www.scribd.com/document/478666771/book-pdf