Tech transfer covers documented transfer of design outputs, process recipes, equipment qualifications, work instructions, and training to the receiving site, typically followed by re-qualification and process validation runs. Transfers happen when moving production to a new site, a contract manufacturer or a new line. The receiving site must show equivalence through comparison testing and validation, and change control assesses whether regulators or notified bodies need to be notified. Under the EU MDR, a new site or critical subcontractor may require notified body review.

Why it matters

Among the highest-risk activities in a device lifecycle - under-resourced tech transfers cause launch delays, scrap, and field issues.

Common pitfalls

•Failing to involve quality assurance and regulatory affairs early in the technology transfer process can lead to significant delays and non-conformities.
•Inadequate documentation of changes and controls during transfer can result in a loss of process understanding and control.
•Not performing sufficient re-qualification and re-validation activities at the receiving site often leads to manufacturing inconsistencies and product defects.
•Assuming that processes and equipment will perform identically in a new environment without empirical verification is a common and costly mistake.
•Underestimating the need for comprehensive training of personnel at the receiving site can compromise manufacturing quality.

Sources

ISO 13485:2016 §7.5 · ISO
ISO 13485 Standard Page · ISO
GHTF/IMDRF Process Validation Guidance · IMDRF/GHTF

Open full page

Select term B to compare.

Why compare MedTech terms side by side?

MedTech terminology is full of pairs that look interchangeable but carry very different regulatory, clinical, and commercial consequences. Picking the wrong framework, pathway, or standard early in a project can add months to a submission, invalidate clinical evidence, or trigger an audit finding. Side-by-side comparison is the fastest way to surface those differences before they become costly mistakes.

Each comparison on this page pulls from the same vendor-neutral, sourced definitions used throughout the MedTech Terms glossary. You see the one-line summary, the formal definition, why it matters in practice, common pitfalls, and the primary sources (FDA guidance, EU MDR/IVDR articles, ISO/IEC standards, MDCG documents, IMDRF principles) that back each entry. That makes the comparison defensible in regulatory strategy memos, design reviews, and submission narratives.

Common comparison patterns

Regulatory pathway choice - 510(k) vs PMA, 510(k) vs De Novo, Abbreviated vs Special 510(k).
Quality systems - QSR vs ISO 13485, QMSR vs QSR.
Software classification - SaMD vs SiMD, Locked vs adaptive AI.
EU frameworks - MDR vs IVDR, CE Mark vs UKCA.
Cybersecurity artifacts - SPDX vs CycloneDX SBOM, CVE vs CVSS.
Post-market actions - Recall vs field action, Removal vs correction.

How to use this tool

Pick term A and term B from the dropdowns, or click a preset above. The URL updates with both slugs so you can bookmark or share the exact comparison with a colleague, a notified body reviewer, or your regulatory consultant. Click Open full page on either side for the complete entry, including FAQs, related terms, and the full citation list. If you are not sure which term to start with, browse the Categories view or the A-Z index.

MedTech Terms is a vendor-neutral community resource sponsored by Blue Goat Cyber. Definitions are written for educational use and are not legal or regulatory advice.