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.

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.