IQ verifies that equipment is installed per specification; OQ verifies that it operates within defined limits; PQ verifies that the integrated process consistently produces conforming output. Together they support process validation. OQ typically challenges process parameters at the edges of their operating windows to show the process still produces acceptable results, while PQ runs at nominal conditions over multiple runs or lots to show reproducibility. The GHTF process validation guidance (SG3/N99-10) is still widely used as a reference for this approach. Protocols must define acceptance criteria in advance, and deviations must be documented and assessed.

Why it matters

A well-known shorthand, but the structure varies - software validation and aseptic process validation each have their own variants.

Common pitfalls

•Confusing IQ/OQ/PQ as a one-time event rather than a lifecycle approach that includes re-qualification or continuous monitoring.
•Failing to establish clear acceptance criteria for each qualification stage, leading to ambiguous results or unvalidated processes.
•Not adequately documenting all qualification activities, including deviations and resolutions, which can lead to regulatory non-compliance during audits.
•Applying a generic IQ/OQ/PQ approach without tailoring it to the specific risks and complexities of the process or equipment being validated.
•Underestimating the resources, time, and expertise required to perform thorough and effective IQ/OQ/PQ activities.

Sources

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.