Case Studies and Practical Examples of SAE Coding in MedDRA

Introduction to SAE Coding with MedDRA

Serious Adverse Events (SAEs) represent critical data points in clinical trials and pharmacovigilance. Regulatory authorities such as the FDA, EMA, and MHRA require accurate and consistent coding of SAEs using the Medical Dictionary for Regulatory Activities (MedDRA). Proper coding ensures that safety signals are identified, analyzed, and reported in compliance with global regulatory expectations.

While routine adverse events can often be coded through auto-coding tools, SAEs require additional diligence. Incorrect selection of Preferred Terms (PTs) can distort the seriousness, medical significance, and reporting timelines of the event. For this reason, regulators often scrutinize SAE coding during Good Clinical Practice (GCP) inspections and sponsor audits.

This article explores real-world case studies and examples of SAE coding, providing insights into common challenges, regulatory expectations, and best practices for maintaining accuracy and compliance.

Case Study 1: Myocardial Infarction in a Cardiology Trial

In a Phase III cardiology trial, an investigator reported “patient had a heart attack.” Coders must ensure this is mapped accurately through MedDRA’s hierarchy:

Coding as “Chest pain” would be incorrect and misleading. The accuracy of “Myocardial infarction” as PT is critical, as it determines expedited reporting timelines and influences safety signal detection for cardiovascular events.

Case Study 2: Psychiatric SAE with Suicidal Ideation

In an antidepressant trial, an investigator reported “patient said he wanted to die.” Coders faced the decision between “Depression” and “Suicidal ideation.”

The correct PT is “Suicidal ideation”. Coding as “Depression” would underestimate the risk and fail to trigger expedited reporting obligations (7-day reporting for life-threatening SAEs). This case highlights the importance of training coders to recognize suicidality and apply MedDRA PTs with precision.

Case Study 3: Ambiguous Gastrointestinal SAE

In an oncology trial, the verbatim term recorded was “severe stomach issues.” Potential coding options included:

• Dyspepsia
• Abdominal pain
• Gastrointestinal disorder

In this case, the sponsor’s SOP required querying investigators for clarification before assigning a PT. Once clarified as “Upper GI bleed,” the correct PT assigned was “Gastrointestinal hemorrhage.” This ensured accurate reporting and prevented data misinterpretation.

Case Study 4: Oncology SAE with Febrile Neutropenia

In a chemotherapy trial, the investigator recorded “fever with low WBC.” Coders needed to ensure proper alignment with MedDRA hierarchy:

Coding this as “Fever” or “Neutropenia” alone would miss the medical significance. The correct PT “Febrile neutropenia” accurately reflects the SAE, guiding both treatment urgency and regulatory reporting.

Case Study 5: Neurological SAE with Seizures

During a neurology study, the investigator wrote “patient had fits.” Coders had to avoid vague PTs like “Nervous system disorder” and instead select:

• LLT: Fits
• PT: Convulsion
• SOC: Nervous system disorders

This example illustrates why coders must understand cultural variations in reporting (e.g., “fits” in some regions versus “seizure” in others) and apply MedDRA appropriately.

Regulatory Expectations for SAE Coding

Regulators emphasize the importance of coding accuracy in SAE cases. Common inspection points include:

• Whether suicidality-related SAEs are consistently coded.
• Whether coders document rationale for ambiguous terms.
• Whether MedDRA version updates are applied to historical SAE data.
• Whether reconciliation between CRFs, narratives, and safety databases is documented.

The Health Canada Clinical Trials Database reinforces the expectation of harmonized SAE reporting standards, aligned with MedDRA coding practices.

Best Practices for SAE Coding

To strengthen SAE coding practices, sponsors should:

• Develop detailed SAE coding conventions, especially for psychiatric and oncology events.
• Train coders on recognizing ambiguous SAE verbatim terms.
• Audit SAE coding as part of pharmacovigilance quality oversight.
• Maintain reconciliation logs between CRFs, safety databases, and narratives.
• Document all coding decisions in audit-ready trails.

These practices ensure that SAE data are reliable, consistent, and defensible during audits and regulatory inspections.

Key Takeaways

SAE coding using MedDRA is one of the most scrutinized aspects of pharmacovigilance. Sponsors must:

• Apply accurate PTs to reflect medical significance.
• Document rationale for coding decisions.
• Ensure consistency across trials and versions.
• Prepare for inspections with robust SOPs and training records.

By integrating lessons from real-world case studies, clinical teams can ensure accurate SAE coding, meet regulatory expectations, and protect patient safety across global development programs.

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.