Leveraging Real‑World Evidence to Fulfill Post‑Approval Regulatory Commitments

Understanding the Role of RWE Post‑Approval

After a drug or biologic gains regulatory approval, its journey is far from over. Regulators often impose post‑approval commitments—studies designed to confirm long-term safety, effectiveness, and risk mitigation strategies in the real-world population. While randomized controlled trials (RCTs) have long been the gold standard, they can be expensive, time-consuming, and less reflective of real-world conditions.

Real‑World Evidence (RWE) offers a powerful complement to RCTs. Derived from Real‑World Data (RWD) such as electronic health records (EHRs), insurance claims, patient registries, and even digital health apps, RWE allows regulators and sponsors to monitor products in diverse, real-life settings. Increasingly, RWE is being used to satisfy post-approval requirements under frameworks from the FDA, EMA, PMDA, and Health Canada.

Types of Post‑Approval Commitments Supported by RWE

RWE can be used to fulfill several types of post‑marketing regulatory obligations, including:

• Post-Marketing Requirements (PMRs) mandated by the FDA for accelerated approvals or unresolved safety issues
• Post-Marketing Commitments (PMCs) agreed upon by sponsors to provide additional evidence after approval
• Risk Evaluation and Mitigation Strategies (REMS) with elements to assure safe use, requiring real-world monitoring
• Post-Authorization Safety Studies (PASS) and Post-Authorization Efficacy Studies (PAES) in the EU

These studies often require long-term observation across large patient populations, making RWE-based methodologies particularly attractive.

Regulatory Acceptance of RWE: A Global Overview

The FDA’s RWE Framework under the 21st Century Cures Act outlines scenarios where RWE can support regulatory decision-making, including fulfilling PMRs. The agency has released guidance on using EHRs and medical claims data, and the PDUFA VII commitments (2023–2027) further elevate RWE’s role.

In the European Union, EMA’s DARWIN EU platform is centralizing access to RWD for regulatory use. Japan’s PMDA and Health Canada are similarly piloting regulatory-grade RWE integration in post-market surveillance.

Examples of RWE Use in Post‑Approval Settings

Several landmark cases illustrate the feasibility and value of RWE in fulfilling regulatory obligations:

• Blincyto (blinatumomab): Accelerated FDA approval was followed by confirmatory safety and effectiveness assessments via real-world registry data for relapsed/refractory acute lymphoblastic leukemia.
• Covid-19 Vaccines: Post-market surveillance using EHR and claims data across multiple countries helped confirm safety in pregnancy, children, and patients with comorbidities.
• Oncology Observational Studies: Flatiron Health’s real-world datasets have supported post-approval evaluations of checkpoint inhibitors and CAR-T therapies.

Study Designs for RWE‑Based Commitments

Unlike RCTs, RWE studies typically use observational designs, such as:

• Retrospective Cohort Studies: Leverage historical patient data to assess long-term outcomes
• Prospective Registries: Track patients in real-time under routine clinical practice
• External Control Arms: Use RWD as a comparator group when an RCT arm is not feasible
• Pragmatic Clinical Trials: Blend trial structure with real-world care delivery models

These methods are particularly suited to rare diseases, pediatric populations, or patients excluded from trials—addressing diversity gaps in initial evidence packages.

Design Considerations and Methodological Challenges

To ensure RWE meets regulatory standards, sponsors must address several key challenges:

• Data Completeness and Accuracy: Missing or miscoded entries in EHRs and claims can distort outcomes.
• Selection Bias: Patients in real-world cohorts differ significantly from RCT participants.
• Confounding Variables: Lack of randomization means confounders must be controlled using statistical models.
• Endpoint Validity: Outcomes should align with pre-approved definitions and data availability.
• Regulatory Dialogue: Early interaction with agencies helps determine if RWE design meets acceptability thresholds.

Data Sources for RWE Generation

Common data types used to construct RWE studies include:

Best Practices for Sponsors Using RWE for Commitments

• Engage with the FDA/EMA via Type B/C meetings early to confirm study design acceptability
• Validate data sources through feasibility studies and pilot testing
• Use propensity score matching, regression adjustment, or instrumental variable methods for confounding control
• Implement a statistical analysis plan (SAP) and pre-specify outcomes
• Utilize eCTD Module 5 format to submit RWE study results

Case Study: RWE for Expanded Indication Approval

A respiratory drug approved for adults was considered for adolescent asthma treatment. Instead of initiating a full-scale trial, the sponsor aggregated RWE from multiple pediatric pulmonology centers across the U.S. and EU. Outcomes, including exacerbation frequency and steroid reduction, were compared to existing adult efficacy data. With additional literature bridging and population matching, EMA accepted the submission under a Type II variation supported primarily by RWE.

Future Outlook: Global Convergence on RWE Use

As agencies collaborate on data standards and evidence frameworks, we may see mutual recognition of RWE studies across regions. Initiatives like ICH E19 and CIOMS RWE guidelines aim to harmonize definitions, quality controls, and endpoint criteria.

Sponsors will benefit from investing in internal RWE infrastructure, including biostatistical expertise, data partnerships, and systems for RWE protocol governance.

Conclusion: RWE Is a Pillar of Post‑Approval Regulatory Strategy

Real‑World Evidence has emerged as a credible, regulator-endorsed strategy to fulfill post‑approval obligations. Whether used to support REMS, confirm safety profiles, or expand patient populations, RWE enables faster, more relevant, and often more cost-effective compliance.

As global regulatory bodies align, RWE will continue to reduce the time and burden of traditional trials while upholding safety and public health. For sponsors, the time to operationalize RWE as a formal component of post-approval strategy is now.

How to Standardize EHR Data for Research in Pharma

Electronic Health Records (EHRs) have revolutionized how patient data is collected, stored, and analyzed. For pharmaceutical professionals and clinical researchers, leveraging EHR data for real-world evidence (RWE) studies demands a robust standardization process. Without consistent structures, vocabularies, and formats, EHR data is often incomplete, fragmented, and unsuitable for regulatory-grade research.

This tutorial walks you through the practical steps of EHR data standardization, covering terminologies, models, mapping techniques, and quality control measures. By implementing these practices, pharma professionals can produce harmonized datasets that meet both research rigor and GMP compliance.

Why Standardization of EHR Data Matters:

Raw EHR data comes from diverse sources—hospital systems, outpatient clinics, specialty centers, and labs. Each source may use different formats, terminologies, and data entry practices. Standardization ensures:

• Interoperability across systems
• Accuracy and comparability of patient records
• Compliance with regulatory submissions (e.g., FDA, EMA)
• Reliable analysis for outcomes, safety, and utilization
• Faster integration with claims data or registries

As per CDSCO guidelines, structured and traceable data is a must for observational studies and post-marketing surveillance.

Step 1: Select a Common Data Model (CDM)

The first step in standardizing EHR data is choosing a suitable common data model. CDMs provide a universal structure that organizes medical records across settings. Popular models in pharma include:

• OMOP CDM: Used widely for observational and RWE studies; supports standard vocabularies.
• PCORnet CDM: Optimized for patient-centered outcomes research.
• i2b2/ACT: Often used for clinical cohort discovery.

For most pharma research applications, OMOP CDM is preferred due to its extensive use of controlled vocabularies and support from OHDSI (Observational Health Data Sciences and Informatics).

Step 2: Map EHR Data to Standard Vocabularies

Standard vocabularies ensure uniform interpretation of medical terms across institutions and systems. The key vocabularies include:

• SNOMED CT: Standard for clinical conditions and observations
• LOINC: Logical Observation Identifiers for lab tests and vitals
• RxNorm: Drug names and dosage forms
• ICD-10: Diagnosis coding for billing and analytics
• CPT/HCPCS: Procedure and service coding

Use mapping tools to align local terminologies with these standards. For example, map “high blood sugar” to SNOMED CT code 80394007 for “Hyperglycemia.”

Maintain documentation using Pharma SOP templates for mapping logs, version control, and quality checks.

Step 3: Normalize Field Formats and Units

Standardization also requires data field consistency. Normalize fields such as:

• Dates: Use ISO 8601 format (YYYY-MM-DD)
• Units: Convert lab results into standardized SI units
• Binary fields: Represent Yes/No as 1/0
• Sex: Use ‘M’ or ‘F’ or standard codes from HL7
• Vital signs: Specify measurement method (e.g., sitting BP vs ambulatory)

Normalize data types across tables (e.g., string, integer, boolean) to enable consistent queries and validation rules.

Step 4: Handle Missing or Ambiguous Data

Incomplete data is a frequent challenge in EHR research. Address this through:

• Imputation techniques (mean substitution, regression models)
• Logical inference (e.g., hospitalization dates from admission records)
• Flagging missing values for downstream sensitivity analysis
• Data source triangulation (e.g., match lab data with medication orders)

Document imputation methods in validation logs to ensure transparency in audits.

Step 5: Adopt Interoperability Standards

To ensure scalable and replicable integration across sites, use interoperability frameworks:

• HL7 FHIR: Fast Healthcare Interoperability Resources – supports API-based EHR access
• CDISC ODM: Clinical data exchange for trials and research
• X12/EDI: For linking insurance and claims data

HL7 FHIR, in particular, allows real-time access to normalized EHRs via endpoints—ideal for pharmacovigilance and post-market tracking.

Step 6: Quality Assurance of Standardized EHR Data

Ensure standardized data meets the following quality parameters:

1. Completeness: Are all required fields populated?
2. Accuracy: Are mappings and units verified?
3. Consistency: Are formats and types harmonized across records?
4. Traceability: Can source records be traced and reproduced?
5. Timeliness: Is the data up to date and refresh frequency defined?

Use automated data validation scripts and manual spot-checking. Include audits as part of pharma validation programs.

Use Case Example: RWE Study in Diabetes Patients

Suppose a pharma company wants to assess the effectiveness of a new diabetes drug in real-world patients using EHR data.

Steps taken:

1. Extract raw EHRs from three hospital systems
2. Normalize all lab results (HbA1c, glucose) into mg/dL
3. Map diagnosis codes to SNOMED CT and ICD-10 for diabetes and complications
4. Standardize drug prescriptions using RxNorm
5. Use OMOP CDM to align all fields
6. Validate data for completeness, duplicates, and logical errors
7. Link with claims data for hospitalization and cost tracking

The result: a research-ready dataset suitable for publication and submission to EMA.

Best Practices Summary:

• Select an industry-recognized CDM like OMOP
• Use controlled vocabularies for all medical terms
• Normalize units, data types, and field names
• Implement robust quality checks
• Maintain documentation and audit trails
• Train analysts on interoperability standards

Conclusion: Enabling RWE Through EHR Standardization

Without standardization, EHR data remains siloed and inconsistent. By applying the steps outlined here—adopting common data models, standard vocabularies, normalization protocols, and quality assurance—pharma professionals can convert disparate clinical records into powerful evidence generators.

Whether your goal is regulatory submission, safety signal detection, or comparative effectiveness research, harmonized EHR data forms the foundation of trustworthy and actionable insights. For advanced use cases like stability tracking or multi-source linkage, visit StabilityStudies.in.