Streamlining EHR Integration through Common Data Models for RWE

Electronic Health Records (EHRs) provide a vast source of real-world data (RWD), but differences in formats and terminologies across systems create integration challenges. Common Data Models (CDMs) offer a solution by providing standardized data structures that enable consistent analysis across institutions, regions, and platforms.

This guide explores how pharmaceutical professionals and clinical trial stakeholders can use CDMs to harmonize EHR data, facilitating reliable real-world evidence (RWE) generation for regulatory and scientific purposes.

Why Common Data Models Are Essential:

Inconsistent EHR formats across healthcare systems hinder large-scale observational studies. CDMs solve this problem by:

• Defining standard tables and fields (e.g., patient demographics, diagnoses, drug exposures)
• Ensuring uniform terminologies (e.g., SNOMED CT, LOINC, RxNorm)
• Enabling cross-database analytics with common logic
• Supporting reproducible research through aligned metadata

Whether working on safety studies or comparative effectiveness research, CDMs improve data quality and integrity, enhancing GMP compliance when observational results are used to support regulatory filings.

Key Common Data Models Used in EHR Integration:

Here are the most widely adopted CDMs in the pharma and research community:

1. OMOP (Observational Medical Outcomes Partnership):
   • Developed by the Observational Health Data Sciences and Informatics (OHDSI) collaborative
   • Captures clinical data in a person-centric format
   • Supports standardized vocabularies and cohort definitions
2. Sentinel Common Data Model:
   • Created by the U.S. FDA’s Sentinel Initiative
   • Focused on post-marketing safety surveillance
   • Includes robust privacy protections and distributed analytics
3. PCORnet CDM:
   • Developed by the Patient-Centered Outcomes Research Institute
   • Optimized for patient-centered outcomes and engagement studies
4. HL7 FHIR (Fast Healthcare Interoperability Resources):
   • Not a CDM in the traditional sense, but a data exchange standard
   • Enables real-time EHR integration via APIs
   • Increasingly used in dynamic RWE platforms

Steps to Implement a Common Data Model for EHR Integration:

To adopt a CDM in your real-world evidence program, follow these steps:

1. Choose a CDM: Based on study goals, regulatory alignment, and partner ecosystem.
2. Extract Data: From source EHRs in both structured and unstructured formats.
3. Transform and Map: Clean and normalize data using extract-transform-load (ETL) pipelines, aligning with the CDM structure.
4. Standardize Terminologies: Use tools like Usagi for OMOP to map local codes to global standards.
5. Validate Data Quality: Perform checks on completeness, consistency, and referential integrity.
6. Deploy Analytics Tools: Utilize cohort builders, statistical engines, and visualization dashboards compatible with the CDM.

For long-term success, integrate CDM workflows into your Pharma SOP templates for reproducibility and compliance.

Regulatory Acceptance of CDM-Based Evidence:

Global regulatory bodies increasingly recognize CDM-aligned evidence in submissions. For example:

• The USFDA accepts Sentinel CDM results in drug safety monitoring.
• The EMA leverages OMOP-standardized data in DARWIN EU for RWE analysis.
• Health Canada encourages structured data submissions to improve review efficiency.

Maintaining traceability from original EHR sources to CDM tables is critical for regulatory audits. Align with data provenance principles to ensure integrity.

Common Challenges and Solutions in CDM Adoption:

• Challenge: Mapping diverse data sources with incompatible formats
• Solution: Use ETL automation tools like WhiteRabbit and RabbitInAHat (OMOP) for structured mapping
• Challenge: Clinical terminologies vary by institution or country
• Solution: Leverage SNOMED CT crosswalks and LOINC/RxNorm mappings
• Challenge: Governance and access across multi-site collaborations
• Solution: Employ federated data models or distributed queries with privacy controls

Build competency by including CDM mapping training in your Pharma Validation programs to improve internal capacity.

Case Example: OMOP CDM in Oncology RWE

In an oncology real-world evidence study, a pharmaceutical sponsor mapped EHR data from five hospitals to the OMOP CDM. They used standardized definitions to:

• Identify eligible lung cancer patients
• Track treatment regimens and outcomes
• Evaluate progression-free survival across treatment cohorts

This enabled fast data extraction and consistent outcome definitions, accelerating the generation of real-world insights aligned with StabilityStudies.in protocols.

Best Practices for Long-Term Sustainability:

• Document your ETL pipelines and update them regularly as source EHRs evolve
• Use open-source CDM tools to avoid vendor lock-in
• Join communities like OHDSI or PCORnet to stay updated on CDM advancements
• Align with pharma regulatory compliance for traceable and auditable CDM processes
• Incorporate metadata standards to improve data discoverability and reusability

CDM maturity models are emerging to guide institutions through phased adoption. Early wins in pilot projects can build momentum for wider rollouts.

Conclusion: Building RWE Infrastructure through CDMs

As the demand for high-quality real-world evidence grows, integrating EHRs using common data models becomes indispensable. CDMs provide the structure, standardization, and scalability needed to transform raw EHR data into regulatory-grade evidence.

Whether leveraging OMOP, Sentinel, PCORnet, or HL7 FHIR, success lies in methodical implementation, rigorous validation, and strategic alignment with regulatory and scientific goals. With the right approach, CDMs can unlock the full potential of EHRs for next-generation evidence generation in pharmaceuticals.

How Regulatory Bodies Accept EHR-Derived Data in Pharma Studies

Electronic Health Records (EHRs) are increasingly used as real-world data (RWD) sources for generating real-world evidence (RWE) in pharmaceutical research. However, not all EHR-derived data is considered fit-for-purpose by global regulatory agencies such as the EMA and the USFDA. To gain regulatory acceptance, EHR-based data must meet strict criteria for quality, traceability, reliability, and relevance.

This tutorial outlines how pharma professionals can ensure EHR-derived data complies with regulatory expectations, what documentation to prepare, and which standards to follow when planning submissions using RWE generated from electronic medical records.

Understanding Regulatory Expectations for EHR-Derived Data:

Agencies such as the FDA and EMA are open to the use of EHR data, provided the following criteria are met:

• Data Integrity: The source data must be complete, accurate, and unaltered.
• Traceability: Each data point must be traceable to its origin, including who entered it and when.
• Relevance: Data must be appropriate for the clinical question or regulatory decision.
• Transparency: Clear documentation of data provenance and transformation is required.
• Governance: Use of the EHR system must be under formal oversight with defined policies.

Regulatory bodies apply similar scrutiny to EHR-derived data as they do to data collected in randomized controlled trials (RCTs).

Step 1: Ensure EHR System Validity and Compliance

Only validated, regulated EHR systems should be used for data generation. Key checks include:

• 21 CFR Part 11 compliance for electronic records and signatures
• Audit trails that show who accessed or changed data
• System qualification and change control documentation
• Role-based access with permission logs

Systems that generate the data should undergo formal process validation and adhere to ALCOA+ principles (Attributable, Legible, Contemporaneous, Original, Accurate).

Step 2: Data Source Mapping and Documentation

Agencies expect thorough documentation of where data comes from. Your submission must include:

• List of all data fields used and their clinical significance
• Definitions of each variable (e.g., diagnosis codes, lab values)
• Data transformation or derivation logic applied
• Version control for datasets and extraction protocols

It’s also important to describe any limitations in data capture, such as missing values or inconsistent time intervals.

Step 3: Validate Data Quality and Consistency

Before submitting RWE derived from EHRs, conduct quality checks such as:

• Duplicate entry analysis
• Outlier detection (e.g., unrealistic blood pressure readings)
• Range and consistency checks
• Missing data imputation justifications

Agencies often require submission of the data cleaning steps, query logs, and issue resolution summaries. These are typically maintained under GMP documentation requirements.

Step 4: Clarify Patient Selection and Data Linkage Methodology

Patient population definitions must be precise and reproducible. Regulatory reviewers need to know:

• Inclusion and exclusion criteria for the dataset
• ICD/CPT/LOINC codes used for identifying conditions or procedures
• Data linkage rules if combining EHR with claims or registry data
• Patient privacy safeguards, such as de-identification SOPs

Be transparent if linkage required deterministic or probabilistic methods, and provide match accuracy rates.

Step 5: Align with Relevant Regulatory Frameworks

Each regulatory body provides guidance documents for RWD use:

• FDA: Framework for RWE program, 2018; Draft guidance on RWD use in submissions
• EMA: RWE Reflection Paper; Big Data Task Force Recommendations
• Health Canada: Guidance on RWD/RWE submissions
• CDSCO: Emerging interest in RWE for post-marketing studies in India

In all cases, align your submission to the specific regulatory definitions of fitness-for-purpose data.

Step 6: Use Standardized Data Models Where Possible

Adopt harmonized structures such as:

• OMOP CDM: Observational Medical Outcomes Partnership Common Data Model
• HL7 FHIR: Fast Healthcare Interoperability Resources
• Sentinel Data Model: Used by FDA for safety surveillance

These models improve traceability, transparency, and cross-system comparison. They are encouraged for studies submitted as RWE.

Step 7: Address Statistical and Methodological Rigor

Include a clear statistical analysis plan (SAP) that addresses:

• Confounding and bias mitigation strategies
• Propensity score matching or weighting techniques
• Sensitivity analyses for missing or ambiguous data
• Endpoint definitions using standardized clinical logic

Justify your choice of real-world comparators or external controls. Regulatory bodies evaluate RWE with the same rigor as RCTs in many cases.

Step 8: Submit RWE as Part of Regulatory Filing with Transparent Appendices

Whether used in a New Drug Application (NDA), Marketing Authorization Application (MAA), or post-marketing commitment, EHR-derived data must be submitted in a transparent, structured format:

• Include all data transformation protocols
• Provide audit logs and dataset lineage
• Append SAS or R scripts used for analysis
• Submit de-identified patient-level data as applicable

Consider publishing protocols and methods to boost reviewer confidence and transparency.

Conclusion: Charting a Path to Regulatory Acceptance

As regulators grow more open to EHR-derived RWE, pharmaceutical companies must meet heightened expectations for data quality, transparency, and methodological soundness. Follow the guidance outlined above to ensure your EHR-based study data is not just real-world, but real-useful for regulators.

Whether analyzing treatment persistence, adverse event patterns, or comparative effectiveness, EHR-derived RWE can accelerate access to therapies and post-market insights—provided it’s regulatory-grade.

For studies involving drug degradation patterns or treatment timelines, integrate datasets from StabilityStudies.in for enhanced outcome prediction in EHR-based research.