Electronic Data Capture (EDC) systems are validated software platforms used to design electronic Case Report Forms (eCRFs), collect clinical data from investigator sites, run edit checks, manage queries, and produce locked datasets for analysis. Common platforms include Medidata Rave, Veeva Vault EDC, Oracle InForm, and Castor. EDC systems generate audit trails, enforce role-based access, and integrate with related systems, Clinical Trial Management Systems (CTMS), eConsent, ePRO, randomization (IRT/IWRS), safety databases, and electronic Trial Master Files (eTMF).

Why it matters

EDC is foundational to modern clinical trial conduct. Sponsors must validate EDC systems per 21 CFR Part 11 (electronic records and signatures), maintain audit trails, and demonstrate data integrity meets ALCOA+ principles. For IDE device trials, EDC validation, user training records, and source data verification approach are routinely inspected by FDA bioresearch monitoring inspectors. The shift toward Risk-Based Monitoring (RBM) and Decentralized Clinical Trials (DCT) is built on EDC capabilities including remote source data review and real-time anomaly detection.

Common pitfalls

•Treating EDC validation as a vendor responsibility, sponsors are accountable for the validation evidence in their environment, with their configuration.
•Skipping or shortcutting 21 CFR Part 11 audit-trail review during inspection readiness.
•Underestimating data migration risk when switching EDC platforms mid-study, FDA expects defensible mapping and re-validation.

Sources

21 CFR Part 11 · eCFR
21 CFR Part 312.62, Investigator recordkeeping · eCFR
ClinicalTrials.gov · NIH

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.