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.

Managing MedDRA Version Updates in Clinical Trials

Why MedDRA Versions Are Updated

The Medical Dictionary for Regulatory Activities (MedDRA) is updated twice a year—typically in March and September. These updates ensure that the dictionary evolves with medical science, incorporating new terms, restructuring hierarchies, and refining definitions. For sponsors, CROs, and regulators, version updates improve data accuracy, harmonize coding, and support signal detection across therapeutic areas.

Updates may include new Preferred Terms (PTs), modifications to System Organ Classes (SOCs), or reclassification of existing terms. For example, emerging conditions such as “COVID-19 pneumonia” were added in recent versions. Sponsors must adopt these updates in a timely manner to remain compliant with regulatory expectations. Agencies such as the FDA, EMA, and PMDA require that safety data submissions specify the MedDRA version used for coding.

Failure to manage version updates can result in inconsistent datasets, delayed submissions, and inspection findings. Thus, implementing structured processes for MedDRA updates is essential for regulatory compliance and pharmacovigilance.

Impact of Version Updates on Clinical Trials

Each MedDRA update can affect ongoing trials in several ways:

• New terms: Coders gain access to updated LLTs and PTs reflecting current medical knowledge.
• Retired terms: Certain LLTs may be deprecated, requiring recoding of existing events.
• Hierarchical shifts: PTs may be reassigned to different SOCs, changing how aggregate analyses are performed.
• Cross-study comparisons: Trials coded with different versions may produce inconsistent datasets unless reconciled.

For example, if “Myocardial infarction type 2” is added as a PT in a new version, coders must reassign prior cases coded under general “Myocardial infarction” PTs to ensure consistency in safety analyses.

Version changes may also impact DSURs, PSURs, and aggregate reports. Regulators often question whether sponsors have adequately managed version transitions when inconsistencies appear in safety datasets.

Case Example: MedDRA Version Transition in an Oncology Trial

Consider a Phase III oncology trial using MedDRA version 23.0. Midway through the trial, version 24.0 introduces new PTs for immune-related adverse events, including “Immune checkpoint inhibitor colitis.” The sponsor must:

1. Update the safety database to MedDRA v24.0.
2. Recode historical events from general terms like “Colitis” to the new PT where appropriate.
3. Train coders on the new version and updated coding conventions.
4. Document the reconciliation process in the Trial Master File (TMF).

This case illustrates how timely adoption of new versions ensures accurate pharmacovigilance and regulatory compliance, particularly in emerging therapeutic areas.

Regulatory Expectations on MedDRA Version Management

Regulatory agencies expect sponsors to demonstrate traceability and consistency in handling MedDRA updates. Common expectations include:

• Version documentation: Submissions must clearly state the MedDRA version used for coding.
• Transition management: Sponsors should document how and when version updates were implemented.
• Reconciliation: Safety datasets must be reconciled to avoid inconsistencies across versions.
• Training: Coders must be trained on new terms, structures, and conventions introduced in each update.
• Audit readiness: Regulators may review version transition logs during inspections.

Inspection findings often highlight failures in version management, such as continued use of outdated versions or lack of documentation on recoding decisions. For global compliance, sponsors should align coding practices across all regions, ensuring FDA, EMA, and CDSCO submissions use harmonized MedDRA versions.

Best Practices for Handling Version Updates

To effectively manage MedDRA updates, sponsors should adopt the following practices:

• Establish SOPs: Define clear procedures for adopting new MedDRA versions.
• Plan updates: Implement updates immediately after March and September releases.
• Reconcile datasets: Perform systematic recoding of historical cases impacted by new or retired terms.
• Train coders: Provide refresher training with examples of new terms and hierarchical changes.
• Audit processes: Maintain version control logs, reconciliation records, and coding decision documentation.

For instance, a sponsor may maintain a version reconciliation log that documents all PTs changed during an upgrade, along with rationale for recoding decisions. Such logs serve as valuable inspection artifacts.

Challenges in Managing Updates

Despite best practices, challenges remain:

• Resource burden: Updating databases and training coders requires time and staff.
• Cross-study consistency: Reconciling coding across multiple ongoing trials can be complex.
• Regulatory timelines: Version updates often coincide with critical submission deadlines.
• Automation risks: Auto-recoding features may misclassify terms without manual review.

These challenges highlight the importance of proactive planning, sponsor oversight, and hybrid manual/automated reconciliation processes.

External Resources and References

Coders and safety professionals should leverage external resources to stay aligned with regulatory expectations. The ISRCTN Registry often references MedDRA coding standards in trial protocols, demonstrating global alignment on terminology usage.

Key Takeaways

Handling MedDRA version updates is a critical pharmacovigilance function. Clinical teams must:

• Adopt new MedDRA versions promptly after release.
• Reconcile coding across trials to maintain consistency.
• Document transitions, rationale, and recoding decisions in audit-ready logs.
• Train coders on new terms and hierarchical changes.
• Maintain inspection readiness by aligning global submissions to the same version.

By managing MedDRA updates systematically, sponsors ensure accurate safety data, regulatory compliance, and reliable pharmacovigilance across global clinical development programs.

How to Code Ambiguous Verbiage in MedDRA for Clinical Trials

Introduction to Ambiguous Verbiage in Adverse Event Reporting

In clinical trials, adverse events (AEs) are initially reported by investigators in verbatim language, often reflecting patient statements or clinical notes. These terms are not always precise. Ambiguous expressions such as “feeling unwell,” “stomach upset,” or “heart problem” pose significant challenges during MedDRA coding. Unlike clear terms like “myocardial infarction” or “rash,” ambiguous terms require coder interpretation, which increases the risk of misclassification and regulatory non-compliance.

Regulators including the FDA, EMA, and CDSCO emphasize that accurate and consistent MedDRA coding is critical for pharmacovigilance and safety signal detection. Incorrect coding due to ambiguity can distort safety analyses and undermine the validity of DSURs, PSURs, and IND safety reports. To address this challenge, sponsors must implement SOPs, coding conventions, and training programs that guide coders in interpreting and coding ambiguous terms consistently.

Examples of Ambiguous Verbiage in Clinical Trials

Ambiguity often arises because investigators record patient experiences in lay language. Below are common examples and potential MedDRA interpretations:

These examples highlight the complexity of coding ambiguous terms. Without adequate conventions, coders may apply different PTs across trials, leading to inconsistent datasets.

Risks of Incorrect Coding Due to Ambiguity

Ambiguous coding errors can have serious consequences:

• Signal distortion: Misclassification of AEs can mask or exaggerate safety signals.
• Regulatory findings: Inspectors often flag inconsistencies in coding of ambiguous terms.
• Data fragmentation: Similar events coded differently across trials prevent accurate pooling of safety data.
• Audit deficiencies: Lack of documentation on coding decisions may be cited as a GCP non-compliance.

For instance, if “fainting” is coded as “Loss of consciousness” in one trial and “Syncope” in another, regulators may question the reliability of cross-study safety analyses. Consistency is therefore paramount in ambiguous coding cases.

Strategies for Handling Ambiguous Verbiage

Sponsors and CROs can manage ambiguity by applying structured strategies:

• Request clarification: Where possible, query the investigator for more detail before final coding.
• Use general PTs: When specifics are lacking, coders may assign broader PTs such as “Malaise.”
• Follow SOP conventions: Coding conventions should define how ambiguous terms are consistently coded.
• Flag for review: Ambiguous cases should undergo medical review by safety physicians.
• Document rationale: Coders should record the reasoning for selected PTs in audit trails.

For example, a sponsor SOP may state: “All reports of ‘feeling unwell’ should be coded as PT ‘Malaise’ unless additional clinical details are available.” Such conventions reduce variability and inspection risks.

Regulatory Expectations and Inspections

Regulators expect coders to demonstrate traceability in coding decisions for ambiguous terms. Common inspection findings include:

• Inconsistent PT selection across similar events.
• Failure to query investigators for clarification.
• Lack of documentation explaining coding rationale.
• Use of auto-coding without manual review of ambiguous terms.

To meet expectations, sponsors should establish coding conventions, maintain training records, and conduct routine audits. Inspection readiness requires evidence that ambiguous coding decisions were consistent, justified, and traceable. Public registries such as the NIHR Be Part of Research platform highlight the importance of standardized terminology for global safety data consistency.

Best Practices for Coders

Best practices for handling ambiguous terms include:

• Maintain detailed coding conventions with common ambiguous terms and assigned PTs.
• Provide refresher training to coders on how to handle vague or incomplete terms.
• Ensure coders escalate complex cases to medical safety officers.
• Review ambiguous terms in coding quality audits.
• Update conventions after each MedDRA version release.

These practices ensure that ambiguous terms are consistently coded and that datasets remain reliable across trials and submissions.

Key Takeaways

Coding ambiguous terms in MedDRA requires coders to balance accuracy, consistency, and regulatory compliance. To achieve this, clinical teams must:

• Recognize common sources of ambiguity in investigator-reported terms.
• Develop SOPs and conventions for standardizing ambiguous coding decisions.
• Document rationale and maintain audit trails for inspection readiness.
• Train coders and escalate complex cases to medical experts.
• Perform quality reviews to ensure consistency across trials.

By following structured strategies, sponsors and CROs can minimize the risks of misclassification, ensure reliable pharmacovigilance data, and meet global regulatory expectations.

How to Choose the Right Preferred Term (PT) in MedDRA Coding

Why Preferred Term Selection Matters

The Preferred Term (PT) is the cornerstone of MedDRA coding in clinical trials and pharmacovigilance. Each PT represents a unique medical concept that enables harmonized reporting of adverse events across studies and regions. The correct choice of PT ensures regulatory compliance, supports accurate signal detection, and allows for meaningful safety analysis. Conversely, misclassification at the PT level can lead to erroneous safety conclusions, missed signals, or regulatory findings during inspections.

For example, if an investigator records “fits,” coders must map this to the PT “Convulsion.” Selecting “Epilepsy” instead would be inappropriate because epilepsy implies a chronic condition, not an acute event. Regulators such as the FDA, EMA, and CDSCO expect sponsors to have robust processes and SOPs to ensure accuracy in PT selection.

Since PTs are used in aggregate safety reports such as DSURs, PSURs, and IND safety reports, the reliability of these submissions depends on consistent and accurate PT coding. Training coders and establishing coding conventions are therefore essential.

Process of Selecting a Preferred Term

Coders usually begin with the investigator-reported term, which is mapped to the Lowest Level Term (LLT). From there, MedDRA automatically links the LLT to a PT. The coder’s role is to ensure that the chosen PT truly reflects the intended meaning of the original investigator term.

The selection process typically involves:

1. Reviewing the verbatim term: Understand context and clinical meaning.
2. Identifying LLT matches: Search MedDRA for possible LLTs that fit.
3. Evaluating PT linkage: Ensure the LLT maps to the most accurate PT.
4. Applying coding conventions: Follow sponsor or CRO guidelines for standardization.
5. Quality check: Verify accuracy through peer review or safety database controls.

For example, the investigator term “stomach upset” could map to LLTs such as “Abdominal discomfort” or “Dyspepsia.” The coder must select the PT that best reflects the clinical description, likely “Dyspepsia.”

Examples of Correct PT Selection

Below is a table illustrating how PTs should be chosen for different investigator terms:

These examples show that careful PT selection maintains the clinical intent of the original term while ensuring regulatory-standard consistency.

Challenges in Choosing the Right PT

Despite clear rules, coders often face challenges in selecting PTs:

• Ambiguity: Investigator terms may be vague, such as “feeling unwell,” which lacks clinical specificity.
• Multiple options: Several LLTs may map to different PTs, requiring coder judgment.
• Updates in MedDRA: New PTs are introduced in biannual updates, requiring re-coding or reconciliation.
• Inter-coder variability: Different coders may select different PTs for the same verbatim term.
• System errors: Automated coding tools may misclassify terms without proper review.

For example, “fainting” could map to PTs such as “Syncope” or “Loss of consciousness.” Choosing the right PT depends on clinical context. Without clear conventions, inconsistencies may arise across studies.

Regulatory Expectations and Inspection Findings

Regulators expect traceability and consistency in PT selection. Common inspection findings include:

• Incorrect mapping of investigator terms to PTs.
• Lack of documentation for coding decisions.
• Failure to update PT assignments after MedDRA version upgrades.
• Inconsistent PT use across trials, leading to skewed safety analyses.

For example, an inspection may reveal that the same investigator term “blood clot” was coded as “Thrombosis” in one study and “Embolism” in another. Regulators view this as a major compliance gap. Sponsors are expected to have coding conventions and regular audits to prevent such inconsistencies.

Best Practices for PT Selection

To ensure accuracy in MedDRA coding, clinical teams should adopt these best practices:

• Develop detailed coding conventions with examples for common terms.
• Train coders and CRAs regularly on MedDRA updates and PT selection principles.
• Use hybrid auto/manual coding to balance efficiency with accuracy.
• Perform peer reviews and audits of coded terms to identify errors.
• Reconcile coding across studies to maintain consistency in aggregate reporting.

External resources such as the ClinicalTrials.gov database provide examples of standardized safety reporting, reinforcing the importance of accurate coding practices.

Key Takeaways

Choosing the right PT in MedDRA coding is critical for regulatory compliance, safety analysis, and inspection readiness. Clinical teams must:

• Understand the MedDRA hierarchy and its linkages from LLT to PT.
• Apply clear conventions to reduce ambiguity in coding.
• Ensure PT selection reflects the true clinical meaning of investigator terms.
• Document and audit coding decisions for consistency across trials.
• Stay updated with MedDRA version changes and retrain staff accordingly.

By applying these principles, sponsors and CROs can ensure that safety data is accurate, consistent, and aligned with global regulatory expectations.

Understanding MedDRA and Its Importance in Clinical Trials

Introduction to MedDRA

The Medical Dictionary for Regulatory Activities (MedDRA) is an internationally standardized medical terminology developed under the auspices of the International Council for Harmonisation (ICH). It is the global standard for coding adverse events, medical histories, indications, and procedures across clinical trials and post-marketing surveillance. Regulators such as the FDA, EMA, MHRA, PMDA, and CDSCO require the use of MedDRA for consistent reporting of adverse events.

MedDRA provides a common language that allows harmonized reporting of clinical and safety data across companies, regions, and regulatory submissions. This prevents misinterpretations that could arise if sponsors used different medical terminologies. For example, one sponsor might describe an event as “heart attack,” while another uses “myocardial infarction.” MedDRA coding ensures both are standardized under the same Preferred Term (PT) for regulatory analysis.

The dictionary is used throughout the product lifecycle: from early phase clinical trials to post-marketing pharmacovigilance. In safety reporting databases such as the FDA FAERS and the EMA EudraVigilance, MedDRA ensures that safety signals are consistently captured and analyzed across millions of case reports.

Why MedDRA Is Used in Clinical Trials

MedDRA is not just a vocabulary; it is a regulatory requirement and an analytical tool. Its use offers several key benefits:

• Regulatory compliance: All IND, NDA, BLA, and CTA submissions must use MedDRA coding for adverse events.
• Consistency: Ensures uniform representation of medical concepts across trials, preventing duplication or misclassification.
• Signal detection: Facilitates statistical analyses to identify potential safety issues across large datasets.
• Global harmonization: Enables cross-regional reporting under FDA, EMA, and WHO guidelines.
• Audit readiness: Provides clear documentation and coding traceability during GCP and pharmacovigilance inspections.

For example, in oncology trials, adverse events such as “low white blood cell count” are coded under the MedDRA PT “Neutropenia.” This standardization enables consistent analysis of hematological toxicity across multiple compounds and studies.

Structure of MedDRA and Its Application

MedDRA is hierarchical, consisting of five levels:

1. Lowest Level Terms (LLTs): Lay or specific terms entered by investigators (e.g., “heart attack”).
2. Preferred Terms (PTs): Standardized terms for analysis (e.g., “Myocardial infarction”).
3. High Level Terms (HLTs): Group of related PTs (e.g., “Ischemic coronary artery disorders”).
4. High Level Group Terms (HLGTs): Broader groupings (e.g., “Coronary artery disorders”).
5. System Organ Class (SOC): Highest level, grouping by organ system (e.g., “Cardiac disorders”).

By applying this structure, sponsors ensure that adverse events can be reviewed both in detail (PT-level) and broadly (SOC-level). Regulatory reviewers use SOC-level summaries to evaluate system-wide toxicities, while safety physicians use PT-level data for case-level assessments.

A sample MedDRA coding workflow might look like this:

This process demonstrates how MedDRA transforms site-reported terms into standardized codes for regulatory use.

Challenges and Limitations of MedDRA Use

While MedDRA brings enormous benefits, it is not without challenges:

• Ambiguous terms: Investigators may use vague language like “unwell,” which requires careful coding to avoid misclassification.
• Version updates: MedDRA is updated biannually (March and September). Sponsors must reconcile coding across versions, which can affect ongoing trials.
• Training needs: CRAs, coders, and safety teams must be trained regularly on MedDRA use and version changes.
• Auto-coding risks: Automated systems can misclassify terms if not reviewed by trained coders, especially for complex events.
• Consistency across teams: Large sponsors with multiple coding teams must maintain coding conventions to avoid discrepancies.

For example, if one coder selects the PT “Headache” for the term “Migraine” while another selects “Migraine,” analyses of central nervous system toxicity could be distorted. SOPs and coding guidelines are critical to mitigate such risks.

Regulatory Expectations and Inspections

Regulatory authorities expect sponsors to demonstrate traceability in MedDRA coding. During inspections, common findings include:

• Incorrect coding of investigator-reported terms.
• Lack of documentation explaining coding choices.
• Failure to update coding after MedDRA version upgrades.
• Inconsistent coding across related studies.

To prepare, sponsors should maintain coding conventions documents, perform regular coding reviews, and reconcile data after each MedDRA update. Training logs for CRAs and coders are often reviewed by inspectors as proof of competency.

Best Practices for MedDRA Implementation

To maximize the benefits of MedDRA and ensure regulatory compliance, clinical teams should adopt these best practices:

• Establish clear SOPs for coding workflows and version updates.
• Use hybrid coding: auto-coding for straightforward terms, manual coding for complex/ambiguous cases.
• Conduct regular coding consistency checks and audits.
• Train CRAs, coders, and pharmacovigilance staff on MedDRA fundamentals and updates.
• Reconcile coded data across studies and ensure alignment in DSURs and PSURs.

For example, a sponsor may implement quarterly coding review boards to evaluate difficult terms and ensure consistent PT selection across all trials.

External resources such as the WHO International Clinical Trials Registry provide references to safety reporting standards, reinforcing the need for harmonized MedDRA use worldwide.

Key Takeaways

MedDRA is the global standard for adverse event coding and is indispensable for regulatory compliance, data integrity, and safety signal detection. Clinical teams must:

• Understand the hierarchical structure of MedDRA (LLT → PT → HLT → HLGT → SOC).
• Apply consistent coding practices to avoid misclassification.
• Ensure timely updates with each new MedDRA version release.
• Train staff regularly to maintain competency in coding practices.
• Maintain audit-ready documentation and coding conventions.

By implementing robust MedDRA processes, sponsors and CROs ensure that safety data is reliable, regulators receive accurate submissions, and patient safety remains at the core of clinical research.