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.