Using Real‑World Evidence to Strengthen Diagnostic Submissions

What Real‑World Evidence Means for Diagnostics (and How Regulators Use It)

Real‑world evidence (RWE) refers to clinical insights generated from data collected outside tightly controlled trials—such as electronic health records (EHRs), laboratory information systems (LIS), claims, registries, biobanks, and pragmatic or decentralized studies. For companion diagnostics (CDx) and other IVDs, RWE can confirm performance in diverse practice settings, characterize rare variants or phenotypes, and demonstrate that an assay’s real‑world use supports the same medical decisions described in its labeling. Regulators increasingly accept well‑designed RWE to complement clinical performance studies, justify label expansions (e.g., new tumor types or specimen matrices), or support bridging when a trial‑stage assay differs from the marketed configuration. Crucially, RWE is not a shortcut; agencies expect traceable provenance, pre‑specified analysis plans, and bias‑mitigation strategies that elevate observational data to decision‑grade evidence.

Two misconceptions commonly slow teams down. First, “RWE equals post‑market only.” In fact, prospective observational cohorts and pragmatic studies can run in parallel with pivotal trials to anticipate post‑market questions and accelerate submissions. Second, “Any big dataset is good enough.” Regulators weigh fitness for purpose—does the dataset reliably capture the analyte, the testing process, and the clinical outcomes tied to test‑guided therapy? For CDx, this means the record should include specimen type (e.g., FFPE vs plasma), platform/version, run controls, and the treatment actually administered based on the result.

Designing Decision‑Grade RWE: Cohorts, Comparators, and Confounding Control

Strong RWE starts with a protocolized plan and a clear question. Are you showing consistent clinical validity (e.g., biomarker‑positive patients benefit more than biomarker‑negative) or confirming analytical performance in routine practice (e.g., lot‑to‑lot precision, invalid rates, limit of detection behavior at the medical cut‑off)? Define your target trial emulation: eligibility, index date (specimen collection), exposure (test result and therapy), and outcomes (ORR, PFS, OS, or response categories relevant to the label). Choose a comparator strategy—concurrent biomarker‑negative patients, a historical external control aligned on line of therapy, or instrument‑to‑instrument comparisons at decentralized sites. Then pre‑specify confounding control: propensity scores, inverse probability weighting, stratification by line of therapy, and sensitivity analyses (e.g., E‑value for unmeasured confounding).

For qualitative CDx (positive/negative), include reclassification at the decision threshold and agreement with an orthogonal method captured in routine care. For quantitative markers (e.g., TMB), define allowable total error at the clinical cut‑off and evaluate bias across sites with mixed models. A practical acceptance framework might set PPA ≥95% and NPA ≥97% with lower 95% CI bounds ≥90%/94% respectively, weighted kappa ≥0.80 for categorical assays, and mean bias ≤10% at the threshold for quantitative results. While these are illustrative, keep criteria anchored to clinical risk—missing a true positive that withholds life‑saving therapy carries more weight than a small numeric bias far from the decision boundary. For process quality, track invalid rate (<3%), turnaround time (median ≤72 h), and repeat‑test frequency (<5%).

Data Architecture and Provenance: From EHR/LIS to Submission‑Ready Tables

Regulatory‑grade RWE depends on traceable data lineage. Start with a data dictionary covering analyte codes, platform versions, lot numbers, and key pre‑analytical fields (fixative, tumor content, time‑to‑freeze). Build an extract‑transform‑load (ETL) pipeline that preserves audit trails, and implement data quality rules (range checks for Ct or read depth, duplicate suppression, specimen‑ID concordance). Where multiple labs contribute data, harmonize units and reference ranges, and map local terminology to controlled vocabularies. For outcomes, link to pharmacy/claims and mortality sources using privacy‑preserving record linkage. Pre‑specify missing‑data strategies (multiple imputation vs complete‑case) and document them in the Statistical Analysis Plan.

Dummy RWE Data Quality Table:

When using decentralized testing, add inter‑site reproducibility (random‑effects models) and cross‑platform concordance. If the marketed assay differs from the trial assay, collect a bridging subset inside the RWE cohort (paired retesting on the new kit) to anchor comparability. For templates and SOP checklists that operationalize these controls, see PharmaValidation.in. For broad principles on quality and submissions, consult FDA’s device resources at fda.gov.

Building the RWE Package for Regulators: Analyses, Sensitivity Checks, and Narratives

Regulators review RWE with two questions in mind: “Are the results unbiased and robust?” and “Are they clinically meaningful for the labeled decision?” Present a hierarchy of analyses: primary (pre‑specified cohort, main endpoint, principal confounding adjustment), key sensitivity (alternative propensity models, negative control outcomes, site‑exclusion stress tests), and supportive (subgroups, time‑varying exposure). For agreement endpoints, include PPA/NPA/OPA with exact CIs and category agreement (kappa). For quantitative assays, add Deming regression, Bland–Altman bias/limits, and reclassification tables at the clinical cut‑off with two‑sided 95% CIs. Provide graphical diagnostics—love plots for covariate balance, funnel plots for site effects, and density overlays around the threshold.

Case Study (Illustrative): A PD‑L1 IHC CDx sought a tissue‑type expansion using a registry linking LIS results and EHR therapies across 42 centers. After pre‑specified propensity weighting, first‑line immunotherapy in PD‑L1‑high patients showed improved real‑world PFS (HR 0.68; 95% CI 0.61–0.76) versus chemo. Inter‑reader category agreement from routine practice yielded weighted kappa 0.83 (95% CI 0.80–0.86), with reclassification at TPS 50% of 3.5% (95% CI 2.7–4.4). Invalid rates and TAT met process targets. The dossier paired these RWE results with a small bridging concordance study on the marketed autostainer, enabling approval of the tissue‑type expansion without a new randomized trial.

Using RWE Under EU IVDR and Beyond: Performance Evaluation and PMS Synergy

Under the EU IVDR, RWE fits naturally into the Performance Evaluation Report (PER) across scientific validity, analytical performance, and clinical performance. Pre‑market observational evidence can prime the PER, while post‑market RWE feeds Post‑Market Surveillance (PMS) and Post‑Market Performance Follow‑up (PMPF). To streamline reviews, structure your PER with pre‑specified questions, robust methods, and traceable data sources; link each claim in the IFU to specific analyses and confidence intervals. Where a Notified Body and EMA must both opine (for CDx per Article 48(3)), highlight the drug‑diagnostic interface—how real‑world testing patterns map to labeled use, and how misclassification risk is monitored and minimized in practice. Practical IVDR insights and consultation mechanisms are available via EMA.

For global alignment, keep a cross‑walk that maps FDA RWE elements to IVDR PMS/PMPF and to Japan PMDA’s expectations for local applicability. When expanding into new regions, an RWE bridging cohort with local samples can reduce the need for large prospective trials if concordance and clinical outcomes mirror the reference population. Always pre‑agree success criteria with agencies and keep statistical code and curation logs audit‑ready.

Operational Playbook: Governance, Ethics, and Data Privacy

Ethical and privacy frameworks are central to RWE. Establish governance that covers data rights, site agreements, de‑identification or pseudonymization, and the legal basis for linkage. Ensure IRB/ethics approvals for observational use, especially where outcomes are abstracted from charts. Build a data monitoring process that tracks QC drift (e.g., weekly invalid rate >5% triggers corrective action), lot changes, and site outliers. For patient safety, define and trend real‑world failure modes (e.g., false negatives at low analyte levels). Provide a CAPA loop so issues detected in PMS translate into updated training, cut‑off clarifications, or software fixes. This continuous loop is what ultimately convinces reviewers that your assay is reliable in messy, real‑life settings—not just at a single center of excellence.

Sample RWE Governance Table:

Numbers That Matter: Sample RWE Performance Snapshot

To make RWE concrete, summarize decision‑critical metrics with targets that reflect clinical risk:

These values are illustrative but align with risk‑based expectations used in many submissions. Always defend targets with clinical reasoning and, where applicable, prior PMA or PER benchmarks.

Conclusion: Make RWE Work Like a Trial—Only Bigger, Broader, and Faster

RWE can accelerate diagnostic approvals and label expansions when it is planned like a trial, curated with audit‑ready provenance, and analyzed with methods that neutralize bias. For CDx especially, pair real‑world concordance and outcomes with tight process controls and a transparent narrative linking test behavior to treatment decisions. Combine this with early agency dialogue and you’ll turn routine practice data into compelling, review‑ready evidence that advances precision medicine at scale.