Per 21 CFR Part 50, informed consent is the legally effective agreement of a subject to participate in a clinical investigation, obtained under circumstances that minimize coercion and ensure understanding of risks, benefits, and alternatives. 21 CFR 50.25 lists the required elements, including the study purpose and procedures, foreseeable risks and benefits, alternatives, confidentiality, compensation for injury, contacts and the right to withdraw without penalty. Consent is usually documented with a signed written form and must be in language the subject understands. ISO 14155 and MDR Article 63 set similar requirements for EU device investigations.

Why it matters

Informed consent documents are reviewed by IRBs. Pediatric, vulnerable population, and digital trial contexts have additional considerations.

Common pitfalls

•Failing to clearly explain all reasonably foreseeable risks and discomforts to the participant is a common pitfall.
•Overlooking the need for re-consent when significant new information arises during a clinical investigation can lead to non-compliance.
•Using overly technical or complex language in informed consent forms can hinder a participant's understanding, invalidating the consent.
•Not ensuring that the informed consent process is free from coercion or undue influence, especially with vulnerable populations, is a serious violation.
•Failure to document the informed consent discussion and signed form appropriately can result in regulatory deficiencies.

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.