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.

Balancing Auto-coding and Manual Coding in MedDRA: Risks and Benefits

Introduction to Auto-coding and Manual Coding

Adverse event reporting in clinical trials depends heavily on MedDRA coding. Coders and pharmacovigilance staff transform investigator-reported verbatim terms into standardized Lowest Level Terms (LLTs) and Preferred Terms (PTs). Two primary approaches exist: auto-coding and manual coding. Both methods are widely used, and most sponsors employ a hybrid approach to balance efficiency and accuracy.

Auto-coding refers to the use of software algorithms that automatically map verbatim terms to MedDRA LLTs and PTs. This process improves speed and consistency but carries risks of misclassification. Manual coding, by contrast, requires trained coders to review verbatim terms and select the most accurate PT, ensuring clinical accuracy but requiring more time and resources.

Regulatory authorities, including the FDA, EMA, MHRA, and CDSCO, accept either method, provided coding is accurate, consistent, and traceable. Inspections often focus on whether sponsors have controls to minimize auto-coding errors and whether manual coding is performed with adequate SOPs and training.

Benefits of Auto-coding

Auto-coding offers several advantages:

• Speed: Automated mapping allows high-volume processing of adverse events, especially in late-phase or large-scale trials.
• Consistency: Ensures identical verbatim terms are mapped to the same PT, reducing variability between coders.
• Efficiency: Minimizes manual workload for straightforward terms, freeing safety teams for complex coding tasks.
• Scalability: Particularly useful in global pharmacovigilance databases handling thousands of SAE and AE reports daily.

For example, common terms such as “headache,” “nausea,” or “fever” can be reliably auto-coded to their respective PTs with little risk of error. In such scenarios, auto-coding significantly improves throughput without compromising accuracy.

Risks of Auto-coding

Despite its advantages, auto-coding presents risks:

• Misclassification: Verbatim terms that are ambiguous or unusual may be incorrectly coded.
• Lack of clinical context: Algorithms may select PTs that miss subtle nuances in the investigator’s description.
• False confidence: Users may rely too heavily on automated systems without appropriate review.
• Regulatory findings: Incorrect PT assignments discovered during inspections can be classified as major findings.

A common example is the investigator term “fainting.” An auto-coding algorithm may map this to “Loss of consciousness,” while the clinically correct PT should be “Syncope.” Without manual review, the coding would be inaccurate and potentially misleading in safety analyses.

Benefits of Manual Coding

Manual coding by trained professionals provides several advantages over automation:

• Clinical judgment: Coders apply medical knowledge to interpret ambiguous or complex terms.
• Accuracy: Reduces risk of misclassification by considering clinical context and study-specific nuances.
• Flexibility: Allows handling of rare events not typically recognized by auto-coding algorithms.
• Audit readiness: Demonstrates human oversight in coding processes, which regulators value during inspections.

For example, the term “liver swelling” might not have a straightforward auto-coded PT. A trained coder would correctly assign “Hepatomegaly,” ensuring data accuracy.

Limitations of Manual Coding

Manual coding, however, has its drawbacks:

• Time-consuming: Large datasets with thousands of AEs require significant manpower.
• Inter-coder variability: Different coders may select different PTs for the same term without clear conventions.
• Resource intensive: Requires continuous training and staffing.

For global trials, where thousands of SAE reports may be received monthly, manual-only coding can strain resources and delay reporting timelines.

Hybrid Approach: Best of Both Worlds

Most sponsors adopt a hybrid approach that combines the efficiency of auto-coding with the accuracy of manual coding:

• Auto-coding: Used for common, low-risk terms like “headache” or “nausea.”
• Manual coding: Applied to ambiguous, rare, or complex terms requiring clinical interpretation.
• Quality checks: Safety departments conduct routine audits to identify and correct auto-coding errors.

This balanced method ensures that large volumes of routine data are processed efficiently, while complex cases receive the clinical oversight they require. Many sponsors implement a “70/30 split,” where 70% of coding is auto-coded and 30% is manually reviewed.

Regulatory Expectations and Inspections

Regulators expect sponsors to demonstrate oversight in both auto-coding and manual coding processes. Common inspection findings include:

• Over-reliance on auto-coding without adequate review.
• Failure to document manual coding decisions.
• Lack of SOPs governing auto-coding thresholds and exceptions.
• Inconsistent coding across studies due to inter-coder variability.

To mitigate these risks, sponsors should maintain detailed SOPs, perform reconciliation checks, and train coders on both methods. Reference registries like the Japan Registry of Clinical Trials highlight the importance of coding accuracy in safety reporting worldwide.

Key Takeaways

The choice between auto-coding and manual coding in MedDRA is not binary. Clinical trial sponsors should:

• Leverage auto-coding for routine terms to improve speed and consistency.
• Apply manual coding for complex, ambiguous, or high-risk terms.
• Adopt hybrid models with built-in quality controls.
• Ensure SOPs and conventions are updated with each MedDRA release.
• Maintain inspection readiness by documenting coding workflows and training logs.

By balancing the benefits and risks of both methods, sponsors can ensure that safety data is coded efficiently, accurately, and in line with 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.