Interoperability Maturity Models for Clinical Physiology Departments: Assessing Where Your Respiratory Lab Falls on the Integration Spectrum in 2026

Feb 20, 2026

Interoperability maturity in clinical physiology is not a binary state. It exists on a spectrum, from manual, siloed data entry at one end to fully automated, bidirectional data exchange at the other. For respiratory labs in 2026, understanding where your department sits on this spectrum is the first step toward reducing clinical risk, meeting regulatory expectations, and delivering better patient outcomes. This article breaks down the key maturity levels, what they mean in practice for respiratory and sleep labs, and how to move forward.

TL;DR

  • Interoperability maturity is a measurable progression, not an on/off switch, and respiratory labs can be assessed against defined levels.

  • Most clinical physiology departments operate below their potential maturity level due to legacy software, double data entry, and poor system integration.

  • Regulatory frameworks in 2026 are actively pushing healthcare providers toward higher interoperability standards.

  • Vendor-neutral, cloud-based platforms are a practical path to advancing maturity without costly infrastructure overhauls.

  • Knowing your current maturity level helps you set realistic, prioritized integration goals.

What Is an Interoperability Maturity Model and Why Does It Matter for Respiratory Labs?

An interoperability maturity model is a structured framework that helps healthcare organizations assess their current level of data integration and chart a path toward more connected, efficient systems. According to the Oxford Research Encyclopedia of Public Health, the Digital Health Profile and Maturity Assessment Toolkit uses a sociotechnical capability maturity approach to evaluate how well digital health systems function across an organization. This kind of structured assessment is directly applicable to clinical physiology departments.

For respiratory labs specifically, the stakes are high. Data flows between spirometry devices, patient administration systems (PAS), electronic medical records (EMR), and reporting platforms. When these systems do not communicate well, the result is manual transcription, duplicated effort, and increased clinical risk.

What Are the Core Levels of Interoperability Maturity?

The National Academies of Sciences, Engineering, and Medicine outline interoperability as existing across distinct layers. Their framework, referenced in Procuring Interoperability, identifies the following progression:

Maturity Level

Description

Typical Respiratory Lab Scenario

Level 1: Foundational

Basic data exchange capability, no shared meaning

Paper reports, manual fax, no digital transfer

Level 2: Syntactic

Standardized formats used (e.g., HL7 v2)

PAS sends ADT messages; lab receives patient demographics

Level 3: Semantic

Shared data definitions and coding standards

SNOMED, LOINC codes applied to lung function results

Level 4: Organizational

Governance, policy, and workflow integration

Cross-department data sharing with agreed protocols

Level 5: Optimized

Continuous improvement, AI-assisted, fully automated

Automated result interpretation, real-time EMR updates

Most respiratory labs in 2026 sit somewhere between Level 2 and Level 3. They have some HL7 messaging in place but lack consistent semantic standards or organizational governance around data sharing.

What Does FHIR Mean for Respiratory Lab Integration in 2026?

FHIR (Fast Healthcare Interoperability Resources) is the current gold standard for health data exchange. A 2024 study published in the Journal of Medical Internet Research (Tabari et al., cited 55 times) provided a comprehensive overview of the state-of-the-art in FHIR-based data models and structures. The research highlighted FHIR's growing role in enabling structured, real-time data exchange across clinical systems.

For respiratory labs, FHIR matters because:

  • It enables standardized exchange of lung function test results between devices, reporting systems, and EMRs.

  • It supports patient-facing data access, which aligns with broader digital health mandates.

  • It is increasingly required by hospital procurement teams when evaluating new clinical software.

The U.S. Federal Register's January 2026 update to the Health Data, Technology, and Interoperability certification program confirmed that SMART v2 (built on FHIR) is now the only version available for use in certified health IT programs. While this is a U.S.-specific regulation, it signals a global direction of travel that Australian, UK, and New Zealand labs should be aware of.

How Do Regulatory Requirements Shape Interoperability Expectations in 2026?

Regulatory pressure is a significant driver of interoperability investment. In the U.S., the CMS Promoting Interoperability program directly ties reimbursement to interoperability performance across five objectives: electronic prescribing, health information exchange, provider-to-patient exchange, public health reporting, and care coordination.

According to Medisolv's 2025 analysis of Promoting Interoperability requirements, the measures have continued to evolve, with updated reporting periods and mandatory measures that raise the baseline expectation for connected care.

While Australian and UK labs operate under different regulatory frameworks (TSANZ/NATA standards and NHS digital mandates respectively), the underlying principle is the same: regulators expect systems to talk to each other, and departments that cannot demonstrate integration capability face increasing scrutiny.

What Does Low Interoperability Actually Cost a Respiratory Lab?

The cost of poor interoperability is rarely calculated but consistently felt. Common consequences include:

  • Double data entry: Technicians re-entering results from device reports into EMRs manually.

  • Transcription errors: A direct patient safety risk when values like FEV1/FVC ratios are entered incorrectly.

  • Delayed reporting: Bottlenecks caused by disconnected systems slow turnaround times.

  • Audit failures: Incomplete or inconsistent data trails create compliance gaps during NATA or NHS accreditation reviews.

  • Staff burnout: Administrative burden on respiratory scientists reduces time available for clinical work.

KLAS Research's 2025 interoperability overview identified health information exchange, care coordination, and patient engagement as the three most pressing interoperability use cases for healthcare organizations. All three apply directly to respiratory lab operations.

How Can a Respiratory Lab Move Up the Maturity Spectrum?

Moving from Level 2 to Level 3 or beyond does not require a complete system replacement. Practical steps include:

  1. Audit your current integrations. Map every data flow in and out of your lab, including device outputs, PAS connections, and EMR feeds.

  2. Identify manual touchpoints. Every manual data entry step is a maturity gap and a risk point.

  3. Prioritize semantic standardization. Ensure your reporting system uses recognized coding standards for lung function results.

  4. Evaluate your software's vendor neutrality. Systems that lock you to a single device manufacturer limit your integration options.

  5. Plan for cloud migration. On-premise systems are increasingly difficult to integrate with modern hospital infrastructure.

Platforms like Rezibase are designed with this progression in mind. Built by respiratory scientists, Rezibase integrates with PAS, EMR, DICOM Modality Worklists, and electronic ordering systems, and its Magic Import feature automatically extracts discrete data from device reports, eliminating manual transcription entirely. Switching from a legacy system like Respiro is straightforward, with data migration handled as part of the onboarding process.

Frequently Asked Questions

What is the most common interoperability gap in respiratory labs?
Manual data entry between device outputs and reporting or EMR systems. This is both the most common and the most addressable gap.

Do Australian respiratory labs need to comply with FHIR standards?
Not mandated at the lab level yet, but hospital procurement increasingly expects FHIR-capable systems. Aligning now reduces future disruption.

What is the difference between syntactic and semantic interoperability?
Syntactic interoperability means data is formatted consistently (e.g., HL7 v2). Semantic interoperability means the data is also understood consistently, using shared definitions and coding standards like LOINC or SNOMED.

How long does it take to improve interoperability maturity?
Moving one maturity level typically takes 6 to 18 months depending on system complexity, vendor support, and organizational readiness.

Is cloud-based software more interoperable than on-premise?
Generally yes. Cloud platforms are easier to connect via APIs and are updated more frequently to meet evolving standards.

What accreditation standards are relevant to respiratory lab interoperability in Australia?
TSANZ/NATA standards and ISO 15189 are the primary frameworks. Both require documented data management and quality control processes.

Can a small private respiratory clinic benefit from interoperability improvements?
Absolutely. Even basic integrations, like automated patient demographic imports from a PAS, reduce errors and save significant staff time.

About Rezibase

Rezibase is Australia's most advanced cloud-based respiratory and sleep reporting platform, built by respiratory scientists for respiratory scientists. Trusted by over 35 sites including NHS and NSW Health, Rezibase offers vendor-neutral integrations, automated data import, and a full accreditation module aligned to TSANZ/NATA and ISO 15189 standards. Learn more at rezibase.com.

Ready to assess where your lab sits on the interoperability spectrum? Visit rezibase.com to explore how Rezibase can help your department move forward.

References

Solving the Multi-Spirometer Problem: A Practical Guide to Consolidating Data From Different Lung Function Device Brands in One Lab System ›

Solving the Multi-Spirometer Problem: A Practical Guide to Consolidating Data From Different Lung Function Device Brands in One Lab System ›