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.

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.