Understanding MedDRA and Its Importance in Clinical Trials

Introduction to MedDRA

The Medical Dictionary for Regulatory Activities (MedDRA) is a clinically validated, internationally recognized terminology used for the classification of adverse events (AEs) and medical information in clinical trials, post-marketing surveillance, and pharmacovigilance. Developed under the auspices of the International Council for Harmonisation (ICH), MedDRA provides a common language for reporting, analyzing, and sharing safety data across sponsors, regulatory agencies, and global stakeholders.

Before MedDRA, adverse event reporting was fragmented, with different countries and organizations using their own terminologies. This inconsistency led to data discrepancies and hindered global pharmacovigilance efforts. MedDRA was designed to standardize the reporting process, ensuring that the same medical concept is consistently captured and analyzed across studies and regulatory submissions. Today, it is used by regulators including the FDA, EMA, PMDA, and CDSCO, as well as the WHO Uppsala Monitoring Centre for global pharmacovigilance.

MedDRA is updated twice a year, typically in March and September, to incorporate new terms and reflect evolving medical knowledge. Its widespread adoption has made it an indispensable tool in drug development and safety monitoring worldwide.

Why MedDRA is Used in Clinical Research and Pharmacovigilance

MedDRA is essential because it allows for standardization, consistency, and accuracy in capturing adverse events. Its uses include:

• Regulatory submissions: Required for adverse event reporting in INDs, NDAs, BLAs, MAAs, and DSURs.
• Pharmacovigilance databases: Facilitates pooling and signal detection across multiple trials and post-marketing data.
• Cross-regional harmonization: Ensures consistency across FDA, EMA, and global regulatory systems.
• Data analysis: Enables statistical aggregation of terms across System Organ Classes (SOCs) for safety evaluations.
• Clarity in communication: Reduces ambiguity by mapping investigator verbatim terms to standardized terminology.

For example, an investigator might record “heart attack” as a verbatim term. MedDRA ensures that this is consistently mapped to the Preferred Term (PT) “Myocardial infarction” under SOC “Cardiac disorders.” This prevents discrepancies such as one coder entering “Cardiac arrest” while another selects “Coronary thrombosis.”

Without MedDRA, global clinical development would face major obstacles in consolidating safety data and meeting inspection requirements.

MedDRA in Global Regulatory Submissions

MedDRA is now a mandatory requirement in most regulatory submissions. For example:

• FDA: Requires MedDRA-coded data in IND safety reports and NDA submissions.
• EMA: Mandates MedDRA use in EudraVigilance reporting for EU-CTR compliance.
• PMDA (Japan): Uses MedDRA for post-marketing AE reporting.
• CDSCO (India): Aligns with MedDRA for SAE and pharmacovigilance submissions.

Public trial registries like the WHO International Clinical Trials Registry Platform emphasize standardized AE reporting, reinforcing MedDRA’s global significance. Its adoption enables cross-border regulatory collaboration, making it easier to detect emerging global safety issues.

Key Features of MedDRA

MedDRA offers several features that make it unique compared to older dictionaries:

• Hierarchical structure: Five levels from LLT (verbatim) to SOC (broadest category).
• Granularity: Contains over 80,000 terms, allowing precise coding.
• Multilingual availability: Supports coding in multiple languages for global trials.
• Clinical orientation: Designed by clinicians to reflect real-world medical practice.
• Flexibility: Allows aggregation for signal detection while retaining detail for case-level review.

These features make MedDRA not only a dictionary but also a powerful analytical tool for pharmacovigilance and regulatory science.

Case Study: MedDRA in an Oncology Trial

In a Phase III oncology trial, an investigator reported the following verbatim terms: “Low WBC,” “Neutrophil drop,” and “Leukocyte decreased.” Without MedDRA, these might be coded inconsistently. Using MedDRA, coders consistently map these to PT “Neutropenia” under SOC “Blood and lymphatic system disorders.”

This consistency ensures that safety analyses accurately capture the frequency of neutropenia across treatment arms, supporting regulatory decisions about the safety profile of the investigational drug.

Regulatory Expectations and Audit Readiness

Regulators often review MedDRA coding during inspections. Expectations include:

• Use of the latest MedDRA version at the time of reporting.
• Consistency of PT selection across trials and regions.
• Clear SOPs describing how ambiguous terms should be handled.
• Training records for coders and CRAs on MedDRA basics.
• Reconciliation logs for version upgrades and cross-database consistency.

Inspection findings often highlight coding inconsistencies, lack of training, or missing documentation. To prepare, sponsors should perform internal audits of MedDRA coding and maintain audit-ready trails of coding decisions.

Best Practices for Using MedDRA

To maximize the benefits of MedDRA, sponsors and CROs should adopt best practices:

• Implement detailed SOPs and conventions for coding decisions.
• Train coders and CRAs in MedDRA structure and updates.
• Reconcile data after each MedDRA version release.
• Perform routine audits to identify coding inconsistencies.
• Leverage hybrid auto/manual coding for efficiency and accuracy.

These measures ensure compliance with global expectations and improve the quality of safety data.

Key Takeaways

MedDRA is the global standard for adverse event reporting and pharmacovigilance. Clinical teams must:

• Understand MedDRA’s structure and purpose.
• Apply it consistently in safety databases and regulatory submissions.
• Maintain compliance through SOPs, training, and audits.
• Adapt promptly to new MedDRA versions released biannually.

By following these principles, sponsors ensure data accuracy, regulatory compliance, and reliable safety analyses in clinical trials and post-marketing surveillance.

Conducting and Facing MedDRA Coding Reviews During Audits

Why MedDRA Coding Reviews Are Critical in Audits

MedDRA (Medical Dictionary for Regulatory Activities) coding is a cornerstone of adverse event reporting in clinical trials. During regulatory inspections and internal audits, coding processes are carefully reviewed to ensure accuracy, traceability, and compliance. Regulators such as the FDA, EMA, MHRA, and CDSCO recognize that coding errors can distort safety signal detection, compromise pharmacovigilance, and lead to misleading regulatory submissions such as DSURs and PSURs.

Auditors typically review how investigator verbatim terms are transformed into Lowest Level Terms (LLTs) and Preferred Terms (PTs), and how these map through the MedDRA hierarchy to System Organ Classes (SOCs). They also examine coding conventions, reconciliation processes, training records, and audit trails. Weaknesses in coding practices are often cited as major findings during Good Clinical Practice (GCP) inspections.

Therefore, MedDRA coding reviews are not only technical checks but also assessments of an organization’s overall pharmacovigilance maturity and regulatory compliance framework.

Scope of MedDRA Coding Audits

Audits of MedDRA coding typically cover the following aspects:

• Accuracy: Whether verbatim terms are mapped to appropriate PTs.
• Consistency: Whether similar terms across studies are coded uniformly.
• Traceability: Whether coding decisions are documented and auditable.
• Version control: Whether coding aligns with the correct MedDRA version at the time.
• Training: Whether coders and CRAs received adequate MedDRA training.
• Reconciliation: Whether coding is reconciled across databases (CRFs, safety databases, TMF).

For example, an audit may review whether all cases of “fits” were consistently coded as “Convulsion” across multiple Phase II and III trials. Inconsistencies may suggest lack of coding conventions or inadequate coder training.

Common Audit Findings in MedDRA Coding

Across inspections and audits, recurring findings include:

• Incorrect PT selection due to ambiguous verbatim terms.
• Inconsistencies across coders or studies for the same term.
• Lack of documentation explaining coding choices.
• Failure to update coding after MedDRA version upgrades.
• Insufficient training of coders and CRAs in MedDRA basics.
• Delayed reconciliation between CRFs, safety databases, and narratives.

These issues highlight the importance of robust SOPs, coder training programs, and internal audits before regulatory inspections. Regulators frequently note that coding errors compromise pharmacovigilance reliability and may issue critical findings if systemic weaknesses are identified.

Case Study: Audit Review of Psychiatric Coding

In one Phase III antidepressant trial, auditors reviewed how suicidal ideation was coded. Investigators used terms like “patient talked about death” and “wants to die.” Coders inconsistently applied PTs—some used “Depression,” while others applied “Suicidal ideation.”

The audit team identified this inconsistency as a major finding because suicidality requires expedited reporting under global regulations. The sponsor was instructed to reconcile all prior data, retrain coders, and revise SOPs to explicitly define how suicidality terms should be coded. This case demonstrates how errors in psychiatric coding can escalate into regulatory risk.

Reconciliation During MedDRA Coding Audits

Auditors pay close attention to reconciliation of safety data across systems. For instance:

• CRF vs Safety Database: AE terms in CRFs must match those in the pharmacovigilance database.
• Narratives vs MedDRA Coding: Narrative descriptions must align with PT assignments.
• Version Updates: Recoding after MedDRA version changes must be documented.

Lack of reconciliation is often cited as a critical finding because it creates discrepancies in safety reporting to regulators. Sponsors must maintain detailed reconciliation logs and demonstrate periodic checks to auditors.

Regulatory Expectations During Inspections

Agencies expect sponsors to demonstrate that MedDRA coding processes are:

• Standardized: Clear SOPs define how coders handle ambiguous terms.
• Documented: Coding decisions include rationale in audit trails.
• Consistent: Coders across studies follow the same conventions.
• Version-aligned: Coding reflects the MedDRA version in use at the time of the event.
• Training-supported: Coders, CRAs, and safety staff maintain competency through training logs.

For example, the ANZCTR emphasizes harmonized AE reporting standards, which rely on consistent MedDRA coding practices. Inspectors expect sponsors to align with such international expectations.

Best Practices for Audit Readiness in MedDRA Coding

To prepare for audits and inspections, sponsors should implement:

• Comprehensive SOPs: Define coding rules, version updates, and reconciliation steps.
• Coder training: Conduct regular training and assessments for coders and CRAs.
• Internal audits: Perform mock audits focused on coding accuracy and traceability.
• Reconciliation logs: Maintain detailed logs comparing CRFs, narratives, and safety databases.
• Version management: Document how MedDRA updates were implemented.

These practices strengthen inspection readiness, minimize findings, and ensure that safety data is accurate and reliable across global submissions.

Key Takeaways

MedDRA coding reviews during audits are a critical part of pharmacovigilance oversight. Clinical teams must:

• Ensure accuracy, consistency, and traceability in MedDRA coding.
• Document coding conventions, training, and reconciliation processes.
• Conduct internal audits to detect and correct errors proactively.
• Prepare audit-ready evidence of version control and SOP compliance.

By adopting strong audit readiness practices, sponsors can demonstrate compliance, maintain regulatory trust, and ensure reliable pharmacovigilance across clinical development programs.