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.

Comparing EMRs and Paper Charts for Retrospective Data Access and Consistency

Retrospective chart reviews are a cornerstone of real-world evidence (RWE) generation in pharma research. One key decision when planning such studies is whether to use Electronic Medical Records (EMRs) or traditional paper charts as the data source. Both formats present unique advantages and limitations, especially concerning data access, consistency, and abstraction methodology. This tutorial provides a structured approach to choosing and working with EMRs vs paper records in observational studies.

Understanding the Differences between EMRs and Paper Charts

Electronic Medical Records (EMRs) are digital versions of patient charts maintained in healthcare IT systems. Paper charts are physical files with handwritten or printed clinical documentation. The choice between them affects study planning, data quality, and compliance.

Pharma professionals must evaluate their retrospective study goals and site capabilities before choosing the data source. Proper documentation, such as pharma SOPs, should address both record types.

Advantages of Using EMRs in Chart Review Studies

EMRs are becoming the dominant data source due to several operational and research advantages:

• Efficient Access: Researchers can access records remotely or on-site with proper credentials.
• Structured Data: Common elements like vitals, lab results, and medications are stored in structured fields, enhancing consistency.
• Built-in Validation: EMR systems often have logic rules to reduce data entry errors.
• Better Traceability: EMRs maintain timestamps and user actions for auditability.
• Integration Capabilities: EMRs can integrate with registries and stability testing systems.

These benefits are particularly useful when extracting data for stability studies in pharmaceuticals.

Limitations of EMRs in Retrospective Research

Despite their advantages, EMRs also have limitations:

• Variability Across Sites: EMRs differ by vendor and configuration, complicating multi-site data harmonization.
• Data Overload: Large volumes of irrelevant data may obscure key findings.
• Unstructured Notes: Free-text fields require manual review or natural language processing (NLP).
• Restricted Access: Tight IT controls may delay data abstraction.
• Hidden PHI Risks: Even redacted data may contain trace identifiers.

These must be addressed in the validation protocol and computer system validation plans.

Working with Paper Charts: Pros and Cons

While paper records are declining, they remain prevalent in certain regions or small practices. They may be the only available source for older retrospective studies.

Advantages:

• Easy for small-volume reviews
• Accessible in rural or under-digitized settings
• No login or digital interface training needed

Disadvantages:

• High risk of illegibility and transcription errors
• Prone to loss or damage
• No electronic audit trails
• Manual data entry increases labor costs
• More difficult to ensure HIPAA compliance

Whenever paper charts are used, establish robust scanning, abstraction, and QA procedures aligned with GMP quality control principles.

Consistency Challenges Across Both Formats

Regardless of format, retrospective data consistency must be managed proactively:

• Source Heterogeneity: Different providers may chart using varying terminologies or templates.
• Missing Data: Common in both formats; needs predefined strategies.
• Temporal Discrepancies: Charting delays or misaligned timestamps may affect event sequencing.
• Record Gaps: Transitions between paper and EMRs often leave documentation gaps.

Define handling rules in your abstraction manual and ensure pharmaceutical compliance with real-world data standards.

Best Practices for Mixed-Source Chart Reviews

In many studies, researchers must work with both paper and EMR data. Here’s how to standardize access and consistency:

1. Train abstractors on both formats using mock records
2. Create dual abstraction templates covering EMR fields and paper equivalents
3. Use standardized coding systems like ICD-10 and MedDRA for diagnoses and events
4. Develop source verification guidelines for cross-referencing entries
5. Conduct inter-rater reliability checks across record types

Also include guidance on how to manage hybrid records that contain both scanned and digital content.

IRB and HIPAA Considerations Based on Record Type

EMRs and paper charts pose different regulatory risks. Address the following when submitting to an IRB or privacy board:

• EMR Access Logs: Provide credentials and system access details
• Paper Chart Handling: Define secure storage, transport, and redaction procedures
• Data Redaction: Specify PHI removal processes tailored to each format
• Waiver Justification: Clearly justify HIPAA waiver requests for both sources

Include these aspects in your submission to regulatory authorities such as USFDA.

Checklist for Data Access and Consistency:

1. Confirm record format type (EMR, paper, or hybrid)
2. Assess access feasibility and site policies
3. Create abstraction tools specific to each format
4. Train staff in format navigation and validation
5. Apply standard coding frameworks to normalize data
6. Log discrepancies and missing data during abstraction
7. Maintain SOPs for both electronic and paper workflows

Conclusion:

Choosing between EMRs and paper charts—or integrating both—can significantly impact the quality and consistency of data in retrospective chart reviews. Each format has distinct strengths and limitations. Pharma professionals should tailor their study design, SOPs, abstraction tools, and regulatory documentation based on the source format. With a proactive approach and appropriate tools, high-quality, consistent data can be extracted from both EMRs and paper records to support robust real-world evidence generation.