📋 Quick Summary
How FDA's Real World Evidence program applies to device 510(k), De Novo, and PMA submissions. Data governance requirements and building RWE capability early.
📬 Get daily updates like this in your inbox. Subscribe to RegWatch Daily →
What FDA's RWE Program Covers
FDA's Real World Evidence program for medical devices has been active since 2017 under MDUFA IV and V commitments. Most small and mid-size manufacturers have not engaged with it seriously. The program enables using data from electronic health records, device registries, insurance claims, or connected device data streams as a supplement to or replacement for traditional clinical trial evidence in premarket submissions.
FDA has accepted RWE to support 510(k) clearances, De Novo authorizations, and PMA supplementals. The evidentiary standard varies by submission type and device risk class. For a 510(k), RWE typically supplements rather than replaces bench or clinical performance data.
What Most Connected Devices Are Missing
Most connected devices are generating data that could support a future regulatory submission, but the data is not structured for regulatory use. The gap is usually in three areas: predefined clinical endpoints that map to regulatory performance claims, data governance documentation that establishes data integrity and chain of custody, and IRB or ethics committee coverage for prospective data collection intended for regulatory use.
Logging device outputs and outcomes data without predefined endpoints produces information, not evidence. FDA requires that RWE-generating studies have pre-specified endpoints before data collection begins, documented in a study protocol that is established before enrollment.
Data Architecture Decisions That Must Happen Early
RWE capability is a product design decision, not a submission-cycle activity. If your device will generate outcomes data that you intend to use in a future regulatory submission, your data architecture needs to support that use from launch. This means defining data elements and their collection methodology before commercial launch, establishing data validation and quality control procedures, and ensuring your data collection is compliant with applicable privacy regulations in each market.
The manufacturers who use RWE effectively built their data infrastructure before they needed it. The ones who wish they could use it typically discover the gap at submission preparation, when the data exists but is not structured for regulatory use.
Get this intelligence in your inbox every morning.
Daily regulatory briefings for QA managers, SaMD teams, and startup RA leads — personalized, actionable, free.
Subscribe Free →Free forever. Unsubscribe anytime.
How to Start Building RWE Capability
The practical starting point is a gap assessment against FDA's framework for RWE studies in device submissions. FDA published a framework document in 2017 and has updated its thinking through subsequent guidance and public workshops. The key questions: does your device collect data elements that map to clinical performance claims, do you have a data governance SOP that establishes data integrity, and do you have a study protocol with predefined endpoints for any prospective data collection?
For manufacturers with connected devices already on the market: audit your current data collection against these criteria. Identify what you are collecting, whether endpoints are predefined, and whether your governance documentation would satisfy FDA's data reliability standards. Most manufacturers find gaps in endpoint prespecification and governance documentation rather than in data volume.
📚 Sources & References
Get this intelligence in your inbox every morning.
Daily regulatory briefings for QA managers, SaMD teams, and startup RA leads — personalized, actionable, free.
Subscribe Free →Free forever. Unsubscribe anytime.
Get the Post-Market Surveillance Toolkit — 6 documents for PMS planning, PMCF, and real-world data governance under FDA QMSR and EU MDR.
Get the FDA Inspection Ready Bundle — $347