Switching from ndd EasyOne Connect or Morgan Scientific: What Respiratory Scientists Wish They Knew Before Migrating to a Vendor-Neutral Platform

Feb 20, 2026

Moving from a device-tied reporting system like ndd EasyOne Connect or Morgan Scientific to a vendor-neutral platform is one of the most impactful operational decisions a respiratory lab can make. The good news: it is far less disruptive than most scientists expect. The core shift is conceptual, not technical. You are moving from a system built around a device manufacturer's interests to one built around your clinical workflow. That change alone resolves most of the frustrations that prompted the switch in the first place.

TL;DR

  • Vendor lock-in limits your ability to upgrade equipment, adopt new standards, or scale your lab independently.

  • Data migration from systems like ndd EasyOne Connect or Morgan Scientific is manageable and far simpler than most labs anticipate.

  • The biggest post-migration gains are in workflow efficiency, reduced double data entry, and improved compliance readiness.

  • A platform built by respiratory scientists addresses clinical needs that generic or manufacturer-owned software simply was not designed to solve.

  • Asking the right questions before you migrate saves months of frustration after go-live.

What Is Vendor Lock-In and Why Does It Matter in Respiratory Labs?

Vendor lock-in occurs when a software system is so tightly coupled to a specific manufacturer's hardware that switching equipment means losing access to your data, your workflows, or both. In respiratory science, this is a structural problem. Labs evolve. Equipment gets upgraded. Standards change. A system that cannot move with you becomes a liability.

Device-bundled software like ndd EasyOne Connect is purpose-built to work with ndd spirometers. That integration is seamless within its ecosystem, which is genuinely useful. According to ndd Medical, PFT testing via spirometry and portable DLCO can be completed conveniently across cardiology and respiratory settings. However, the moment a lab wants to add a different device brand or consolidate reporting across multiple device types, that tight coupling becomes a constraint.

Morgan Scientific occupies a similar space. Its products are well-regarded in cardiorespiratory diagnostics, and a 2015 review of spirometry and diagnostics products highlighted the breadth of devices available from leading manufacturers across the sector. But breadth of hardware does not equal flexibility of software. Many labs using these platforms find themselves locked into equipment refresh cycles they did not choose, simply because changing the device means rebuilding their reporting setup.

What Do Respiratory Scientists Actually Lose by Staying with Device-Bundled Software?

The hidden costs of staying are rarely listed on a spec sheet. Here is what experienced respiratory scientists report after making the switch:

  • Duplicated data entry: Device software captures raw data, but reporting often requires re-entering values into a separate EMR or hospital system.

  • No unified patient record: When a patient has tests across multiple devices or modalities, data lives in silos.

  • Standards lag: Manufacturer software updates to reflect new ATS/ERS guidelines on the manufacturer's timeline, not yours.

  • Limited accreditation support: ISO 15189 and TSANZ/NATA requirements involve document control, non-conformance tracking, and audit trails that device software was never designed to manage.

  • No sleep integration: Respiratory and sleep are clinically linked, but most device-bundled platforms treat them as entirely separate.

How Complicated Is the Data Migration, Really?

This is the question that causes the most unnecessary anxiety. The honest answer: for most labs, migration is straightforward.

Modern vendor-neutral platforms are designed with import flexibility as a core feature, not an afterthought. Rezibase, for example, includes a Magic Import function that directly ingests device reports, automatically extracting discrete data including flow-volume loops, without requiring manual re-entry. You bring your historical reports across. Your patient records follow. The process is structured and supported.

A few practical realities worth knowing before you start:

Concern

Reality

"We will lose historical data"

Export formats from ndd and Morgan systems are well-documented and importable

"Staff will need months of retraining"

Most scientists are proficient within days on a well-designed platform

"IT will block the migration"

Cloud-based platforms reduce IT burden; no local server setup required

"Our integrations will break"

Vendor-neutral platforms are built for EMR, PAS, and DICOM integration

The migration conversation should start with your data inventory, not your fear of change.

What Should You Ask a Vendor-Neutral Platform Before You Commit?

Not all vendor-neutral platforms are equal. Here are the questions that separate genuinely agnostic systems from those that are simply less locked-in:

  1. Can you import from any device, including our legacy equipment? If the answer involves exceptions or additional fees, probe further.

  2. How are normal values managed? A pre-configured, regularly updated normal values library is a significant time-saver and a compliance safeguard.

  3. Does the platform support ATS-compliant reporting natively? Algorithms that structure reports to ATS guidelines reduce clinical risk and physician review time.

  4. Is accreditation management built in? Document control, QC via Westgard methods, non-conformance tracking, and audit readiness should be part of the core platform.

  5. Does it cover both respiratory and sleep? Labs that manage both modalities benefit enormously from a unified system.

  6. What does pricing actually include? Hidden implementation costs and per-module fees erode the value proposition quickly.

What Does a Well-Designed Vendor-Neutral Platform Look Like in Practice?

A genuinely scientist-first platform looks different from the inside than any device-bundled system. The workflow is oriented around the patient and the report, not the device output.

Rezibase was founded by respiratory scientists Peter Rochford and the late Jeff Pretto specifically to address the frustrations described above. Now part of Cardiobase, it operates as a cloud-based SaaS platform used across more than 35 sites including NHS facilities in the UK and NSW Health in Australia. The platform covers the full patient lifecycle: referrals, electronic ordering, waitlist management, bookings, rostering, billing, and reporting, all in one place.

For labs preparing for TSANZ/NATA accreditation or ISO 15189 compliance, having document management, training records, action plans, and quality control integrated into the same system as clinical reporting is a material advantage.

Frequently Asked Questions

Will we lose access to our existing test data when we migrate?
No. Data from ndd EasyOne Connect and Morgan Scientific systems can be exported and imported into a vendor-neutral platform. The process is structured and supported by the receiving platform's implementation team.

How long does a typical migration take?
Timelines vary by lab size and data volume, but most migrations are completed within a few weeks, not months. Cloud-based platforms eliminate the server setup phase that traditionally extended timelines.

Do vendor-neutral platforms support all spirometer brands?
A genuinely agnostic platform will support import from any device manufacturer. Confirm this explicitly, including for your specific device models, before committing.

What happens to our normal values configuration?
Platforms like Rezibase include a pre-configured normal values library aligned with current standards. Your existing configuration can typically be replicated or improved upon during onboarding.

Is cloud-based software safe for patient data?
Yes, when the platform is built to healthcare data standards. Enterprise-grade cloud platforms can also be deployed on-premises for hospitals with specific data sovereignty requirements.

Can one platform really handle both respiratory and sleep reporting?
Yes. Rezibase is one of the few platforms that integrates both modalities, which reflects how clinical physiology labs actually operate.

What if we need to switch equipment again in the future?
That is precisely the point of a vendor-neutral platform. Future equipment changes do not require a software migration.

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 facilities, it offers a manufacturer-agnostic, fully integrated solution covering clinical reporting, accreditation management, and the complete patient administration lifecycle. Rezibase is backed by Cardiobase and offers transparent monthly pricing with no lock-in contracts and a 30-day free trial.

Explore what a scientist-first platform looks like at rezibase.com.

References