CAPA is a quality system process for identifying, investigating, and addressing the root causes of nonconformities, complaints, and other quality events, and for preventing their recurrence. A typical CAPA flow is: identify and document the issue, assess risk, investigate root cause (with tools such as 5 Whys, fishbone diagrams or fault trees), define actions, implement them, and verify effectiveness. Corrective actions address an existing problem; preventive actions address a potential one. Inputs include complaints, nonconformances, audits, service records and trend data. CAPA is one of the most frequently cited areas in FDA Form 483 observations.

Why it matters

CAPA is one of the most frequently cited subsystems in FDA inspections and forms one of the four Quality System subsystems FDA reviews under QSIT. Regulators expect a documented procedure covering identification of quality data sources, investigation, root cause analysis, action planning, implementation, verification of effectiveness, and communication of information to management review.

Common pitfalls

•Treating CAPA as a paperwork exercise without verification of effectiveness (VoE). VoE is what regulators look for first when reviewing closed CAPAs.
•Jumping to a corrective action without a documented root cause analysis (5 Whys, fishbone, fault tree).
•Opening a CAPA for every nonconformance. CAPA should be reserved for systemic issues; individual NCRs are handled through the nonconformance process.
•Not feeding CAPA outputs into management review, risk management, and design controls.

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.