What Is a Respiratory Information System - and Why Does It Matter for Your Lab?
A respiratory information system (RIS) is a specialised software platform designed to manage the full workflow of a respiratory and sleep lab, from patient intake and test ordering through to data capture, clinical reporting, and quality compliance. Unlike generic hospital software, a RIS is built around the specific demands of pulmonary function testing and sleep diagnostics. For labs still relying on spreadsheets, paper records, or fragmented systems, a purpose-built RIS is not a luxury upgrade - it is a clinical necessity.
TL;DR
A respiratory information system centralises all lab workflows: patient management, device data, reporting, and accreditation.
Generic EMRs and hospital systems rarely accommodate the unique complexity of pulmonary function testing.
The right platform eliminates double data entry, reduces clinical risk, and supports compliance with ATS and TSANZ/NATA standards.
Cloud-based solutions remove the IT burden from clinical teams and enable access from anywhere.
Rezibase is a purpose-built, vendor-neutral RIS designed by and for respiratory scientists, trusted by over 35 sites across Australia, New Zealand, the UK, and Ireland.
About the Author: This article was written by the Rezibase team - respiratory scientists and healthcare technology specialists with 37 years of experience building and supporting clinical physiology lab software across Australia, the UK, and beyond.
What Does a Respiratory Information System Actually Do?
A respiratory information system is not simply a database for storing test results. It is an operational backbone for the entire patient journey through a respiratory or sleep lab.
A well-designed RIS manages:
Patient administration: Referrals, waitlists, bookings, rostering, and billing.
Device data capture: Direct import of results from testing equipment, regardless of manufacturer.
Clinical reporting: Structured doctor workflows, medical dictation, and guideline-compliant interpretation.
Quality and accreditation: Document control, audit trails, non-conformance tracking, and quality control.
System integrations: Connections to hospital PAS, EMR, DICOM, and electronic ordering systems.
The respiratory system itself is complex [4]. Its primary job is transporting oxygen to the body and removing carbon dioxide [1][2][3]. The clinical tools used to measure its performance - spirometry, diffusion testing, sleep studies - generate rich, structured data that generic systems simply are not equipped to handle.
Why Can't a Standard EMR Handle Pulmonary Function Test Software Needs?
Standard electronic medical records are designed for breadth, not depth. They cover the full spectrum of clinical encounters, which means they inevitably compromise on specialist workflows. Pulmonary function test software has requirements that fall well outside what most EMRs accommodate out of the box.
Consider what a typical respiratory lab needs that a standard EMR cannot reliably deliver:
Requirement | Standard EMR | Specialist RIS |
|---|---|---|
Device-agnostic data import | Rarely supported | Core feature |
Flow-volume loop extraction | Not standard | Automated |
ATS-aligned normal values library | Not included | Pre-configured and updated |
Accreditation and ISO 15189 compliance tools | Generic at best | Built-in modules |
Sleep study workflow support | Usually absent | Integrated |
Respiratory-specific booking and rostering | Not supported | Tailored modules |
When labs use generic systems for specialist work, the gap is filled by manual effort: double data entry, copied values, and workarounds that introduce clinical risk. This is not a technology limitation to work around - it is a structural mismatch between the tool and the task.
What Are the Real Risks of Using the Wrong System?
The consequences of an ill-fitting system are not abstract. In a respiratory lab, the downstream effects are clinical.
Double data entry introduces transcription errors into patient records.
Non-standardised reporting creates inconsistency in how results are interpreted and communicated.
Manual quality control processes are time-consuming and prone to gaps that can jeopardise accreditation.
Vendor lock-in ties a lab's data and workflows to a single equipment manufacturer, limiting clinical and procurement flexibility.
Unsupported normal values mean labs may be applying outdated reference ranges without realising it.
None of these are hypothetical edge cases. They are common frustrations reported by respiratory scientists, and they were the specific problems that motivated the founding of Rezibase.
What Should You Look for in a Respiratory Information System?
Choosing a RIS is a long-term infrastructure decision. The following criteria should guide the evaluation:
1. Purpose-built design
The platform should be built specifically for respiratory and sleep labs, not adapted from a general clinical system. Workflows, terminology, and data structures should reflect how respiratory scientists actually work.
2. Vendor neutrality
A manufacturer-agnostic system allows labs to import data from any device, protecting clinical independence and avoiding procurement pressure tied to software compatibility.
3. Integrated accreditation support
Compliance with TSANZ/NATA Standards and ISO 15189 requirements should be a built-in function, not an afterthought. This includes document management, training records, non-conformance tracking, and Westgard-based quality control.
4. Cloud delivery
A cloud-based SaaS model removes the need for local servers, simplifies IT management, and makes the platform accessible from any connected location. Enterprise on-premises deployment should also be available for hospital environments with specific requirements.
5. Meaningful integrations
The system should connect natively with PAS, EMR, DICOM Modality Worklists, hospital finance systems, and electronic ordering platforms.
6. Transparent pricing
All-inclusive monthly pricing with no lock-in contracts reduces financial risk and makes total cost of ownership predictable.
How Does Switching Systems Work in Practice?
Data migration is a concern that comes up in almost every conversation about switching systems. The good news is that moving to a modern RIS is more straightforward than it sounds.
With a platform like Rezibase, the transition is supported end to end. Historical data can be brought across, and the Magic Import function means that device reports from existing equipment can be pulled directly into the new system, with discrete data extracted automatically, including flow-volume loops. There is no requirement to re-enter historical results manually or replace existing devices.
The practical steps typically look like this:
Data mapping: Existing records are reviewed and mapped to the new system's structure.
Configuration: Normal values, report templates, and integration settings are configured to match the lab's clinical and organisational requirements.
Training: Clinical and administrative staff are onboarded to the new workflows.
Go-live: The system is activated with support available throughout the transition period.
The goal is minimal disruption to clinical operations and a clear improvement in day-to-day efficiency from day one.
Frequently Asked Questions
What is a respiratory information system?
A respiratory information system is a specialised software platform that manages the complete workflow of a respiratory and sleep lab, including patient administration, device data import, clinical reporting, and accreditation compliance.
Is respiratory information system software different from a general EMR?
Yes. General EMRs are not designed to handle the complexity of pulmonary function test software, including device-agnostic data import, ATS-aligned normal values, or respiratory-specific accreditation requirements.
Does a RIS replace existing testing equipment?
No. A manufacturer-agnostic RIS imports data from existing devices regardless of brand, so labs keep their current equipment.
How long does it take to switch to a new respiratory information system?
Timelines vary by site size and complexity, but the process is designed to be straightforward, with full support provided for data migration and staff training.
What standards should a RIS support?
Look for platforms that support ATS guidelines for reporting, TSANZ/NATA Standards, and ISO 15189 accreditation requirements.
Is a cloud-based RIS secure enough for clinical use?
Yes. Enterprise-grade cloud platforms are built to healthcare security standards and often offer greater reliability and data protection than local server infrastructure.
Does Rezibase cover sleep lab workflows as well as respiratory?
Yes. Rezibase is one of the few platforms that covers both respiratory and sleep in a single integrated solution.
About Rezibase
Rezibase is Australia's most advanced respiratory and sleep reporting solution, built by respiratory scientists Peter Rochford and the late Jeff Pretto, and now developed and supported by Cardiobase. Trusted by over 35 sites including the NHS in the UK and NSW Health in Australia, Rezibase delivers a cloud-based, vendor-neutral platform that covers the full patient lifecycle from referral to billing. With 37 years of experience in clinical physiology software and a commitment to improving patient care through technology, Rezibase offers a transparent, all-inclusive pricing model with no lock-in contracts and a 30-day free trial.
Ready to see what a purpose-built respiratory information system looks like in practice? Visit rezibase.com to explore the platform or start your free 30-day trial.