How Rezibase Connects With Your Hospital's EMR: A Plain-English Guide for Respiratory Lab Managers
Rezibase integrates with your hospital's Electronic Medical Record (EMR) system by acting as a purpose-built respiratory and sleep data layer that sits alongside your existing hospital infrastructure. Rather than replacing your EMR, Rezibase connects to it, pulling patient demographics in and pushing completed reports out, so your team works in one focused environment built for respiratory science instead of toggling between systems.
TL;DR
Rezibase integrates with EMRs, Patient Administration Systems (PAS), electronic ordering platforms, and hospital finance systems.
Integration eliminates double data entry, reducing clinical risk and saving measurable admin time.
The platform is vendor-neutral and manufacturer-agnostic, meaning it works with your existing devices and hospital systems.
Setup is handled by Rezibase, not your IT department alone, keeping the process straightforward.
Rezibase is a cloud-based SaaS solution, so there is no local server infrastructure required on your end.
About the Author: This guide was written by the Rezibase team, respiratory-science specialists with 37 years of experience building and supporting clinical physiology lab software across Australian and UK hospital networks, including NSW Health and the NHS.
Why Does EMR Integration Matter for Respiratory Labs Specifically?
EMR integration is the process of creating a live, structured data connection between a specialist clinical system and the hospital's central patient record. For respiratory labs, this matters more than it might for other departments because the workflow spans multiple touchpoints: a referral arrives from a doctor, a booking is made, tests are performed using equipment from various manufacturers, results are reported by a respiratory scientist, and a final report lands back with the referring clinician.
Without integration, each of those handoffs is a manual step. A patient's name, date of birth, and MRN get typed in twice. A completed report gets scanned and uploaded rather than filed automatically. An order gets phoned through instead of arriving electronically. Every manual step is a chance for error and a drain on scientist time.
The practical consequences include:
Transcription errors on patient demographics that invalidate test results.
Delayed reports sitting in queues waiting to be manually attached to the EMR.
Duplicate bookings caused by referral information living in two systems.
Audit trails that are incomplete because data exists in silos.
Integration solves all of these by making information flow automatically between systems.
What Systems Does Rezibase Actually Connect To?
Rezibase is designed as an integration-first platform. The connections it supports cover the full administrative and clinical chain of a respiratory lab [cardiobase.com]:
System Type | What It Does in Context |
|---|---|
Patient Administration System (PAS) | Pulls verified patient demographics into Rezibase automatically |
Electronic Medical Record (EMR) | Sends completed respiratory and sleep reports back to the patient record |
Electronic Orders System | Receives test orders directly, eliminating phone and fax referrals |
DICOM Modality Worklist | Synchronises patient lists with testing equipment |
Hospital Finance System | Passes billing data through without re-entry |
Each of these integrations addresses a specific friction point. The DICOM Modality Worklist connection, for example, is particularly relevant for labs running spirometry or body plethysmography equipment that supports DICOM. Instead of manually entering the patient on the device, the worklist populates it automatically.
How Does the Data Actually Move Between Rezibase and the EMR?
The data exchange follows standard healthcare interoperability protocols, primarily HL7 messaging. HL7 (Health Level Seven) is the globally recognised messaging standard that most hospital systems, including major EMR platforms, already use to pass structured data between applications.
Here is how a typical patient journey looks once integration is live:
A referring doctor submits an electronic order through the hospital's ordering system.
The order arrives in Rezibase, pre-populated with patient demographics pulled from the PAS.
The patient is added to the Rezibase waitlist and booked, with equipment worklists updated automatically via DICOM.
The respiratory scientist performs testing. Device data is imported directly into Rezibase using the Magic Import function, which extracts discrete data values, including flow-volume loops, without manual entry.
The scientist and reviewing doctor complete the report inside Rezibase.
The finalised report is automatically sent back to the EMR and becomes part of the patient's central record.
At no point does a scientist need to retype patient information or manually attach a PDF to the EMR. The loop closes itself.
Is Switching From an Existing System to Rezibase Complicated?
Migrating from an existing system, including Respiro, is straightforward. The Rezibase team manages the data migration process with you, and the goal is always to preserve your historical records and get your team operational quickly with minimal disruption to the lab.
A few things that make the transition easier in practice:
Existing patient data can be migrated across so your history is not lost.
Training is built into onboarding, not bolted on as an optional extra.
The cloud-based platform means there is no hardware to procure or install before go-live.
Integration configuration is handled collaboratively, so your IT team is not left to figure out HL7 mappings alone.
The honest reality is that any system change requires effort. What Rezibase is designed to avoid is the kind of prolonged disruption that comes from inadequate onboarding support or a one-size-fits-all implementation approach.
What About Hospitals With Complex IT Environments?
Rezibase is enterprise-grade and can be deployed on-premises where hospital policy requires it, in addition to its standard cloud delivery model. This matters for large teaching hospitals or health networks where data sovereignty rules or network security requirements make pure cloud deployment difficult.
For NHS sites and large Australian health networks, this flexibility has been a practical requirement, not just a marketing checkbox.
The platform is also manufacturer-agnostic, meaning it does not favour any particular diagnostic equipment vendor. Whether your lab runs Jaeger, CareFusion, ndd, or another spirometry system, the Magic Import function is designed to bring that device's output into Rezibase without proprietary lock-in.
Frequently Asked Questions
Does Rezibase replace our EMR?
No. Rezibase is a specialist respiratory and sleep reporting system that connects to your EMR. It handles what the EMR cannot do well: device data import, respiratory-specific reporting, normal values, and accreditation. The EMR remains the central patient record.
What EMR systems does Rezibase integrate with?
Rezibase uses standard HL7 messaging, which is compatible with the major hospital EMR platforms used across Australia, New Zealand, the UK, and Ireland. Specific compatibility is confirmed during the scoping process.
How long does integration take to set up?
Integration timelines depend on the complexity of your hospital's IT environment and the number of systems being connected. The Rezibase team manages this process collaboratively rather than handing you a technical specification and stepping back.
Will our historical patient data be migrated?
Yes. Data migration from existing systems, including Respiro, is part of the onboarding process. Your historical records can be brought across so continuity of care is maintained.
Is the integration maintained after go-live?
Yes. As a SaaS platform, Rezibase manages updates and integration maintenance on an ongoing basis. You are not responsible for keeping the connection alive when either system updates.
Do we need dedicated IT resources to manage the integration?
No dedicated IT resource is required on your side for day-to-day operation. Initial setup involves your IT team for network and security approvals, but ongoing management sits with Rezibase.
What if our lab uses multiple device brands?
Rezibase is manufacturer-agnostic. The Magic Import function is built to handle device outputs from multiple vendors, so mixed-equipment labs are well supported.
About Rezibase
Rezibase is Australia's most advanced cloud-based respiratory and sleep reporting platform, purpose-built by respiratory scientists for clinical physiology labs [cardiobase.com]. Trusted by over 35 sites including NHS hospitals in the UK and NSW Health in Australia, Rezibase covers the full patient lifecycle from referral and booking through to reporting, accreditation, and billing. The platform is backed by 37 years of experience in clinical physiology software and is delivered with transparent, all-inclusive monthly pricing and no lock-in contracts.
Ready to see how Rezibase connects with your hospital's existing systems? Visit rezibase.com to book a demonstration or start your 30-day free trial.