Integrating Spirometry and CPET Results Into GP Practice Management Software: Closing the Loop Between Hospital Labs and Primary Care Providers

Feb 20, 2026

When a patient completes spirometry or a cardiopulmonary exercise test (CPET) in a hospital lab, the clinical value of that data depends entirely on what happens next. If the results sit in a siloed reporting system, never reaching the GP who manages the patient day-to-day, the test was only half useful. Closing the loop between specialist labs and primary care is one of the most practical, high-impact improvements available to respiratory medicine today.

TL;DR

  • Spirometry and CPET results generated in hospital labs frequently fail to reach GPs in a timely, structured format.

  • Poor data flow between labs and primary care contributes to under-diagnosis and guideline non-adherence for conditions like COPD.

  • Structured digital integration between lab reporting systems and GP practice software is the most reliable fix.

  • Pulmonary function test software that supports interoperability and EMR integration is central to solving this problem.

  • Rezibase is built specifically for respiratory labs and offers the integrations needed to bridge this gap.

Why Does the Gap Between Lab Results and GP Software Exist?

The gap is structural, not accidental. Hospital respiratory labs and GP practice management systems were built for different workflows, different users, and often different eras of health IT. Labs generate rich, multi-parameter reports, including flow-volume loops, predicted vs. actual values, and exercise tolerance metrics. GP systems are designed to receive simple coded results, not complex physiological datasets.

The result is a fragmented handoff: PDFs emailed or faxed, results manually re-entered, or structured data lost entirely in translation. Each of these failure points introduces clinical risk and delays care.

What Does the Research Say About This Problem in COPD Care?

The evidence is pointed. A 2025 study published in BJGP Open (Bottle et al.) examined variation in COPD management across GP practices and found that pre-diagnosis spirometry use, while improving slightly between cohorts, fell back during the COVID era to just 61.1%. The study highlighted meaningful between-practice variation, suggesting that system-level factors, not just clinician knowledge, are driving inconsistent care.

Separately, research published by Pulmonology Advisor in 2024 found that adherence to COPD guidelines improved when respiratory specialists were integrated directly into GP practices. The implication is clear: when specialist knowledge and data reach primary care, outcomes improve. Technology that enables this integration is not a convenience, it is a clinical necessity.

What Are Spirometry and CPET Results Actually Telling GPs?

Understanding what these tests produce helps explain why structured data transfer matters so much.

Spirometry measures:

  • FEV1 (forced expiratory volume in one second)

  • FVC (forced vital capacity)

  • FEV1/FVC ratio

  • Flow-volume loop morphology

These values classify obstruction, restriction, and mixed patterns. They are the diagnostic backbone for COPD, asthma, and interstitial lung disease.

CPET goes further, measuring integrated cardiopulmonary response to exercise. According to a 2024 review in the Revista Portuguesa de Cardiologia, CPET evaluates VO2 peak, ventilatory efficiency (VE/VCO2), and anaerobic threshold, providing insights that resting tests cannot. A 2024 study published in the European Journal of Cardiovascular Nursing (Kalliath et al.) compared CPET parameters between COPD smokers and healthy smokers, finding meaningful differences in VO2, VCO2, respiratory exchange ratio, and their associations with six-minute walk distance and spirometric values. These are nuanced, multi-variable outputs that a GP needs in context, not as a raw number dropped into a free-text field.

The takeaway: these tests generate layered clinical data. Without structured integration into GP software, that data is reduced to a summary paragraph, and the GP loses the ability to trend values, flag deterioration, or trigger guideline-based actions automatically.

What Does "Closing the Loop" Actually Require?

Closing the loop is not just about sending a PDF faster. It requires:

Requirement

Why It Matters

Structured data export (HL7, FHIR)

Allows GP systems to ingest discrete values, not just text

EMR and PAS integration

Results flow directly into the patient record

Consistent normal value references

GPs interpret results against the same benchmarks used by the lab

Timely automated delivery

Reduces reliance on manual follow-up

Audit trail and version control

Supports medico-legal accountability

Each of these requirements points to the same solution: pulmonary function test software that is designed for interoperability from the ground up, not bolted on as an afterthought.

How Does Specialist Lab Software Enable This Integration?

This is where the design philosophy of the lab's reporting system becomes critical. Legacy or manufacturer-specific systems often create vendor lock-in, limiting what data can be exported and in what format. A vendor-neutral, cloud-based platform changes the equation.

Rezibase is a cloud-based respiratory and sleep reporting system built by respiratory scientists, designed specifically for clinical physiology labs. Its integration architecture supports connections with Patient Administration Systems (PAS), Electronic Medical Record (EMR) systems, Electronic Orders Systems, and Hospital Finance Systems. This means results generated in the lab can flow directly into the systems GPs actually use, without manual re-entry, without data loss, and without the clinical risk that comes from transcription errors.

The platform's Magic Import function automatically extracts discrete data from device reports, including flow-volume loops, ensuring that structured values enter the system from the moment of capture. That structure is what makes downstream integration to GP software possible.

What Should Labs Look for in Pulmonary Function Test Software?

If your lab is evaluating pulmonary function test software with integration in mind, prioritise these capabilities:

  • Vendor neutrality: Import data from any device manufacturer without restriction.

  • Structured data outputs: HL7 or FHIR-compatible exports that GP systems can consume.

  • EMR connectivity: Direct integration with hospital and community EMR platforms.

  • Normal values library: Regularly updated, ATS-aligned reference ranges that travel with the result.

  • Cloud delivery: Accessible from any location, reducing IT overhead and enabling broader connectivity.

  • Audit and accreditation support: ISO 15189-aligned quality controls that satisfy TSANZ/NATA standards.

Frequently Asked Questions

Can spirometry results be sent directly to a GP's practice management software?
Yes, when the lab uses a system that supports HL7 or FHIR integration and the GP platform accepts structured data feeds. The key is ensuring both systems are configured to exchange discrete values, not just PDF attachments.

What is the clinical risk of not integrating lab results with GP systems?
Manual re-entry introduces transcription errors. Delayed results slow treatment decisions. Missing structured data prevents automated alerts. All three increase risk for patients with chronic conditions like COPD.

Does CPET data integrate differently from spirometry data?
CPET produces more parameters, which makes structured formatting even more important. Systems that support discrete data fields for VO2, VCO2, and ventilatory thresholds allow GPs to trend these values over time.

Is cloud-based lab software secure enough for hospital use?
Yes. Enterprise-grade cloud platforms, including those deployed on-premises for hospital environments, meet the same security standards as traditional server-based systems, often with stronger audit and access controls.

How long does it take to set up integrations between a lab system and a GP platform?
This varies, but modern platforms with pre-built connectors for common EMR and PAS systems can complete integrations significantly faster than custom-built solutions.

About Rezibase

Rezibase is Australia's most advanced cloud-based respiratory and sleep reporting solution, trusted by over 35 sites including NHS facilities in the UK and NSW Health in Australia. Built by respiratory scientists Peter Rochford and the late Jeff Pretto, and now part of the Cardiobase group, Rezibase is designed to reduce clinical risk, eliminate vendor lock-in, and connect lab data with the broader care team through deep EMR and PAS integrations.

Explore what Rezibase can do for your lab at rezibase.com.

References

Real-Time ADT Event Handling in Respiratory Reporting Platforms: Keeping Patient Demographics Synchronized Across Admission, Transfer, and Discharge Workflows ›

Real-Time ADT Event Handling in Respiratory Reporting Platforms: Keeping Patient Demographics Synchronized Across Admission, Transfer, and Discharge Workflows ›