From RFP to Go-Live: How Physiology Departments in Australia and the UK Successfully Navigate the Vendor Selection Process for Cloud-Based Lab Systems

Feb 20, 2026

Choosing a cloud-based lab system for a clinical physiology department is one of the most consequential decisions a department head can make. The RFP vendor selection process, when done well, protects your department from costly mistakes, vendor lock-in, and systems that don't fit clinical workflows. This guide walks through how physiology departments in Australia and the UK approach this process, what separates successful selections from regrettable ones, and what to look for at every stage from first draft to go-live.

TL;DR

  • A structured RFP process reduces risk and surfaces the vendors most aligned with your clinical and operational needs.

  • Healthcare RFPs require additional compliance layers, including integration requirements, accreditation standards, and data migration considerations.

  • The best vendor selections prioritise workflow fit, not just feature lists.

  • Cloud-based SaaS solutions reduce IT burden and support faster deployment.

  • Rezibase is a purpose-built respiratory and sleep platform trusted by NHS and NSW Health sites across the UK and Australia.

What Is an RFP in the Context of Healthcare Lab Systems?

An RFP (Request for Proposal) is a formal document issued by a healthcare organisation to invite vendors to propose solutions for a defined need. In the context of clinical physiology labs, it typically covers software capabilities, integration requirements, compliance, pricing, and implementation support.

According to Inventive AI's guide on RFI and RFP in healthcare procurement, healthcare RFPs go beyond standard enterprise procurement. They involve HIPAA-equivalent compliance considerations, specific EHR integration requirements, and a higher standard of documentation than most other sectors.

For physiology departments, this means your RFP must also address:

  • Compatibility with existing Patient Administration Systems (PAS) and EMR platforms

  • Accreditation standards such as TSANZ/NATA and ISO 15189

  • Data migration from legacy systems

  • Role-based access and audit trail requirements

Why Do So Many Lab System Selections Go Wrong?

Most failed vendor selections share a common pattern: the evaluation focused on surface-level features rather than clinical workflow fit. A system that looks impressive in a demo may create friction for scientists doing real work every day.

Common failure points include:

  • Vendor lock-in: Systems tied to specific device manufacturers, making it impossible to import data from other equipment.

  • Double data entry: Poorly integrated platforms that force staff to re-enter data already captured by devices.

  • Underestimating integration complexity: Failing to map out all required connections to hospital systems before signing a contract.

  • Ignoring accreditation requirements: Discovering post-go-live that the system doesn't support quality control or document management to the required standard.

As EHR in Practice notes in their complete EHR RFP guide, an effective RFP process ensures you receive the best candidates. This means the quality of your RFP directly determines the quality of your vendor shortlist.

What Should a Physiology Lab RFP Actually Include?

A strong RFP for a respiratory or sleep lab system should be built around your clinical reality, not a generic IT checklist. Arphie's guide to healthcare RFPs highlights that healthcare RFPs require significantly more compliance documentation than standard enterprise RFPs.

Core sections to include:

RFP Section

What to Cover

Clinical Workflow Requirements

Reporting workflows, normal values, device compatibility

Integration Requirements

PAS, EMR, DICOM, finance, electronic orders

Accreditation and Quality

ISO 15189, TSANZ/NATA, Westgard QC methods

Data Migration

Import of historical patient records and reports

Security and Hosting

Cloud vs on-premise, data sovereignty, access controls

Pricing and Contract Terms

Monthly vs annual, lock-in clauses, trial availability

Implementation and Support

Go-live timeline, training, ongoing support model

The more specific your requirements, the easier it is to disqualify vendors that cannot genuinely meet your needs.

How Should Physiology Departments Evaluate Vendors After Receiving Proposals?

Evaluation should be structured, not intuitive. Graphite Connect's RFP process best practices guide recommends a clear scoring framework applied consistently across all vendors, which removes bias and creates a defensible decision trail.

Recommended evaluation approach for physiology labs:

  1. Score against mandatory requirements first. Any vendor that cannot meet non-negotiable criteria (e.g., TSANZ/NATA accreditation support) is eliminated before detailed review.

  2. Request a live demonstration using your own workflows. Ask vendors to demonstrate a specific scenario, such as importing a flow-volume loop from your current devices.

  3. Speak with reference sites. Prioritise references from departments with similar size, case mix, and system environment.

  4. Assess the vendor's domain expertise. A system built by respiratory scientists will reflect different design decisions than one built by generalist software developers.

  5. Review the migration plan. Data migration should be a clearly defined, supported process, not an afterthought. A good vendor will make this transition feel manageable.

What Does a Successful Go-Live Look Like for a Cloud-Based System?

Go-live is not the finish line. It is the beginning of a working relationship with your vendor. Departments that navigate this well share a few characteristics:

  • They completed thorough data migration planning early. Moving historical records into a new system is straightforward when the vendor has a defined, tested process and experienced support staff.

  • They trained staff before go-live, not during. Cloud-based systems with intuitive interfaces reduce training time significantly, but structured onboarding still matters.

  • They validated integrations in a test environment. Connecting to PAS, EMR, and electronic orders systems should be tested end-to-end before any patient data flows through.

  • They established a feedback loop with the vendor. The best implementations involve a vendor who is genuinely responsive to post-go-live feedback.

This is where platforms built for clinical physiology have a clear advantage. Rezibase, for example, was founded by respiratory scientists Peter Rochford and the late Jeff Pretto, which means the system reflects the real workflows scientists use daily, not assumptions made by developers who have never worked in a lab.

Frequently Asked Questions

How long does a typical RFP vendor selection process take for a lab system?
Most healthcare lab system selections take between three and nine months from RFP issue to contract signing, depending on the complexity of requirements and the number of vendors evaluated.

Do we need an RFI before issuing an RFP?
An RFI (Request for Information) is useful when you are still defining requirements. If your department already has clear requirements, you can proceed directly to an RFP.

How do we handle data migration from our current system?
Most reputable vendors offer structured data migration support. The key is to clarify what data will be migrated, in what format, and who is responsible for validation. With the right vendor, this process is well-defined and straightforward.

What accreditation standards should a respiratory lab system support?
In Australia and New Zealand, TSANZ/NATA standards apply, including ISO 15189 requirements. In the UK, equivalent standards apply for NHS laboratories. Your RFP should require vendors to demonstrate how their system supports document management, training records, non-conformance, and quality control.

Can cloud-based systems be deployed in hospital environments with strict IT policies?
Yes. Enterprise-grade cloud solutions can be configured for on-premise deployment or hosted in compliant cloud environments that meet hospital IT requirements.

What is vendor lock-in and why does it matter?
Vendor lock-in occurs when a system is tied to specific device manufacturers, making it difficult or expensive to switch equipment. A manufacturer-agnostic platform allows you to import data from any device, protecting your department's flexibility.

Is a 30-day trial realistic for evaluating a complex lab system?
A trial is most useful for assessing usability and workflow fit. It should be combined with a thorough RFP process, reference checks, and a structured demonstration to make a fully informed decision.

About Rezibase

Rezibase is Australia's most advanced cloud-based respiratory and sleep reporting platform, trusted by over 35 sites including NHS hospitals in the UK and NSW Health in Australia. Built by respiratory scientists, it offers a manufacturer-agnostic, fully integrated solution covering reporting, accreditation, administration, and quality control. Rezibase is delivered as a SaaS platform with transparent monthly pricing, no lock-in contracts, and a 30-day free trial.

Explore Rezibase at rezibase.com or get in touch to discuss your department's requirements.

References

What Procurement Teams Should Ask When Evaluating Vendor-Neutral Pulmonary Function Platforms: A Due Diligence Checklist for Healthcare Buyers ›

What Procurement Teams Should Ask When Evaluating Vendor-Neutral Pulmonary Function Platforms: A Due Diligence Checklist for Healthcare Buyers ›