DFMEA feeds design controls and the risk management file. PFMEA feeds process validation, control plans, and supplier controls. Both should be living documents updated as the design and process mature. A DFMEA asks how the design itself could fail to meet requirements, assuming it is made correctly; a PFMEA asks how manufacturing or assembly steps could produce a nonconforming product, assuming the design is correct. Severity for the same effect should be consistent across both and with the ISO 14971 risk management file. AIAG and VDA's FMEA handbook is a common reference, adapted for medical device risk practices.

Why it matters

Confusing the two - or treating PFMEA as a one-time deliverable - is a recurring quality finding during PAI and Notified Body audits.

Common pitfalls

•Confusing the scope of DFMEA with PFMEA can lead to critical risks being overlooked in either product design or manufacturing processes.
•Treating PFMEA as a static document, rather than a living one, results in an inability to adapt to manufacturing changes and continuous improvement efforts.
•Failing to link DFMEA outputs to design controls means that product risks identified are not adequately mitigated through design.
•Neglecting to integrate PFMEA outputs into process validation and control plans can lead to manufacturing inconsistencies and product defects.
•Ignoring supplier process risks in the PFMEA can introduce vulnerabilities into the supply chain that impact product quality and safety.

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.