Respiratory labs use equipment from a wide range of manufacturers, and each device speaks its own data language. The core challenge is that most pulmonary function test software is built to work with one vendor's ecosystem, forcing labs into a cycle of manual re-entry, siloed data, and costly hardware dependencies. Rezibase solves this directly: its Magic Import function reads vendor-specific file formats from virtually any respiratory or sleep device and automatically extracts discrete, structured data, including flow-volume loops, into a single unified reporting environment.

TL;DR

• Respiratory devices from different manufacturers produce incompatible file formats, creating data fragmentation in clinical labs.

• Most pulmonary function test software is vendor-specific, contributing to manual re-entry errors and workflow inefficiency.

• Rezibase's Magic Import feature ingests device reports directly, extracting discrete data automatically regardless of the source device.

• Being manufacturer-agnostic means labs are free to use the best equipment for their patients, not just what their software supports.

• Rezibase is a cloud-based SaaS platform built by respiratory scientists, trusted by over 35 sites across Australia and the UK.

About the Author: This article is written by the Rezibase team, a group of respiratory scientists and healthcare technology specialists with 37 years of combined experience building and supporting respiratory and sleep reporting systems across Australian and UK clinical physiology labs.

Why Do Different Respiratory Devices Produce Incompatible File Formats?

Respiratory devices are manufactured by a range of companies, each of which develops its own proprietary data structures, file types, and output conventions. There is no single universal export standard enforced across the industry for spirometry, body plethysmography, CPAP, or polysomnography devices. As a result, a file exported from one manufacturer's spirometer looks nothing like the output from a competitor's system.

This fragmentation is not an oversight. It is often an intentional design choice. When your reporting software only reads your own device's output, customers are far less likely to switch hardware. This is vendor lock-in by design, and it comes at a real cost to labs.

The practical consequences for a clinical physiology lab include:

• Manual transcription of values from printed or PDF device reports into a separate reporting system.

• Increased risk of transcription errors, which carries direct clinical risk for patients.

• Time lost per test that adds up to hours across a busy lab week.

• Inability to compare or aggregate data across different device types used within the same department.

What Is Vendor Lock-In and Why Does It Matter for Respiratory Labs?

Vendor lock-in occurs when a lab becomes operationally dependent on a single manufacturer's ecosystem because switching would require replacing software, reformatting data, or retraining staff. In respiratory medicine, this is particularly common because:

• Device manufacturers often bundle their own basic reporting software with hardware purchases.

• That bundled software typically only reads that manufacturer's native output.

• Labs that want to upgrade their equipment face the added burden of replacing their reporting workflow too.

The result is that clinical decisions about what equipment to buy get distorted by IT constraints rather than driven purely by clinical quality, patient outcomes, or cost-effectiveness.

Rezibase was specifically built to break this dependency. As a manufacturer-agnostic platform, it is designed to accept data from any device, not just a preferred partner's hardware.

How Does Magic Import Actually Work?

Magic Import is the mechanism Rezibase uses to ingest device-generated reports and extract structured, discrete data from them automatically. Rather than requiring manual data entry or custom integrations for every device type, the import process is designed to be straightforward.

Here is what happens in practice:

1. Device generates output: The respiratory device produces its standard report or data file, in whatever format that manufacturer uses.

2. File is uploaded to Rezibase: The file is submitted through the Magic Import interface in the cloud platform.

3. Automatic extraction occurs: Rezibase reads the file, identifies the relevant data fields, and extracts discrete values including flow-volume loops, numerical results, and measurement parameters.

4. Data populates the patient record: Extracted data flows directly into the patient's report within Rezibase, ready for review, interpretation, and sign-off.

The critical word here is "discrete." Rather than embedding a static image of a report into a record (which still requires manual reading and re-entry), Magic Import pulls out the underlying data points. This means the data is usable, searchable, and structured within the system.

What Are the Clinical Risks of Manual Data Entry in Pulmonary Function Testing?

Manual transcription between a device output and a reporting system introduces a category of error that is entirely preventable. In pulmonary function testing, where results directly inform diagnoses such as COPD, asthma severity, and interstitial lung disease, a transcription error can have downstream consequences for patient management.

Common risk points in manual workflows include:

• Misreading printed values, particularly decimals and units.

• Entering values into the wrong field (for example, FEV1 vs FVC).

• Omitting data points that are present in the device output but not included in the manual transfer.

• Version mismatches, where an updated device result is not reflected in the final report.

Eliminating double data entry is one of the most direct ways to reduce clinical risk in a respiratory lab. It is also one of the clearest arguments for adopting pulmonary function test software that integrates natively with device output rather than sitting parallel to it.

Does Being Manufacturer-Agnostic Affect Reporting Quality or Compliance?

A common concern when moving away from a vendor-specific system is whether reporting quality or compliance with clinical guidelines will be maintained. The short answer is no, it does not reduce quality, and it can improve it.

Rezibase is built around ATS (American Thoracic Society) guidelines and includes a pre-configured, regularly updated Normal Values Library. Reporting templates are aligned with current standards regardless of which device generated the underlying data.

Additional compliance and quality features include:

• An accreditation module covering TSANZ/NATA standards and ISO 15189 requirements.

• Quality control tools based on Westgard methods.

• Management of documents, training records, non-conformances, action plans, and audits.

The source device does not determine the reporting standard. Rezibase enforces the standard at the reporting layer, independent of where the raw data came from.

Frequently Asked Questions

Can Rezibase import data from any respiratory device brand?
Rezibase is designed to be manufacturer-agnostic. Magic Import supports file formats from a wide range of device types. If you are evaluating Rezibase for your lab, the team can advise on compatibility with your specific devices.

Will switching from our current system mean losing historical patient data?
Data migration is part of the onboarding process and is handled with support from the Rezibase team. The process is designed to be straightforward, and your historical records can be transitioned into the new platform.

Is Rezibase only for spirometry, or does it cover sleep studies too?
Rezibase covers both respiratory and sleep, which is a meaningful differentiator. Most platforms specialise in one or the other. Rezibase manages both within a single unified system.

Does Rezibase require on-site servers or local IT infrastructure?
No. Rezibase is fully cloud-based and delivered as a SaaS solution. It can also be deployed on-premises for enterprise hospital environments that require it.

How long has Rezibase been operating?
The platform's founders have 37 years of experience in respiratory science and reporting systems. Rezibase is not a new entrant to the space and has an established track record across Australian and UK clinical sites.

Is there a contract lock-in period?
Rezibase operates on a transparent, all-inclusive monthly pricing model with no lock-in contracts and a 30-day free trial.

About Rezibase

Rezibase is Australia's most advanced respiratory and sleep reporting platform, built by respiratory scientists for clinical physiology labs. As a cloud-based, manufacturer-agnostic SaaS solution, it eliminates vendor lock-in, reduces clinical risk through automation, and supports compliance with ATS guidelines, TSANZ/NATA standards, and ISO 15189 requirements. Trusted by over 35 sites including NHS hospitals in the UK and NSW Health facilities in Australia, Rezibase is backed by 37 years of respiratory science expertise and is supported by Cardiobase, a dedicated healthcare technology company.

If your lab is managing data from multiple device types and spending time on manual re-entry, Rezibase may be the most practical step forward. Visit rezibase.com to start a free 30-day trial or speak with the team about your specific device environment.