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.

Understanding the Hierarchy of MedDRA Terms from LLT to SOC

Introduction to the MedDRA Hierarchical System

The Medical Dictionary for Regulatory Activities (MedDRA) is a standardized terminology used globally to code adverse events in clinical trials and post-marketing surveillance. One of its most powerful features is its hierarchical structure, which allows for flexible analysis of safety data. The hierarchy ranges from very specific patient-reported terms (Lowest Level Terms, LLTs) to broad categories used in regulatory summaries (System Organ Class, SOC).

This structure ensures that data can be reviewed at varying levels of detail. For example, a regulatory reviewer may focus on SOC-level summaries such as “Nervous system disorders,” while a safety physician may need PT-level data on “Convulsions” to understand case-level safety implications. Without this hierarchy, harmonized signal detection and cross-study comparisons would be impossible.

MedDRA’s hierarchy is applied across regulatory submissions, including FDA IND safety reports, EMA EudraVigilance submissions, and DSURs. Its standardized nature ensures global consistency in how adverse events are categorized and reported.

The Five Levels of MedDRA Terms

MedDRA’s structure is comprised of five interconnected levels. Each level rolls up into a broader category, enabling flexibility in data analysis.

1. Lowest Level Term (LLT): The most specific level, often the exact wording used by investigators. Example: “Heart attack.”
2. Preferred Term (PT): A distinct descriptor representing a single medical concept. Example: “Myocardial infarction.”
3. High Level Term (HLT): Groups of related PTs that share a common medical concept. Example: “Ischaemic coronary artery disorders.”
4. High Level Group Term (HLGT): Broader groups of related HLTs. Example: “Coronary artery disorders.”
5. System Organ Class (SOC): The highest level, grouping terms by organ system or etiology. Example: “Cardiac disorders.”

This structured roll-up allows sponsors and regulators to analyze adverse events at different levels of granularity. Investigators may use patient language (“chest pain”), but regulators require consistency across submissions, which MedDRA provides by coding these terms into PTs and SOCs.

Example of Hierarchical Mapping

Below is an illustrative example showing how terms map through the MedDRA hierarchy:

This example demonstrates how LLTs used by investigators are standardized into PTs and then progressively grouped into SOCs for high-level regulatory analysis.

Application of the Hierarchy in Clinical Trials

The MedDRA hierarchy is critical for both operational and regulatory purposes:

• Case-level analysis: Coders assign PTs to investigator terms for precise classification.
• Aggregate analysis: Regulators and safety teams review SOC-level data to detect system-wide toxicity patterns.
• Signal detection: Aggregated PTs under HLTs and HLGTs allow statistical analysis for safety signal identification.
• Regulatory submissions: IND safety reports, DSURs, and PSURs require tabulations at SOC and PT levels.

For example, in oncology trials, individual reports of “low platelets” coded as “Thrombocytopenia” (PT) roll up to the SOC “Blood and lymphatic system disorders,” enabling regulators to quickly assess hematologic toxicity across trials.

Challenges in Using the MedDRA Hierarchy

Despite its strengths, applying MedDRA’s hierarchy presents challenges:

• Ambiguity at LLT level: Investigator terms like “felt unwell” require careful coding to avoid misclassification.
• Overlapping SOCs: Certain PTs may link to multiple SOCs (primary and secondary linkages), complicating analysis.
• Version updates: Twice-yearly MedDRA updates may alter mappings, requiring database reconciliation.
• Consistency issues: Different coders may choose different LLTs for similar investigator terms.

These issues highlight the need for SOPs, coding conventions, and periodic coding reviews. Training coders on version updates and providing case-based examples reduces inconsistency and ensures compliance.

Regulatory Expectations and Audit Readiness

Regulatory agencies such as the FDA, EMA, and CDSCO expect sponsors to demonstrate traceability in their coding practices. During inspections, common findings include:

• Incorrect LLT or PT assignment for investigator terms.
• Failure to reconcile coding after MedDRA version updates.
• Inconsistent mapping of similar events across different studies.
• Lack of coding conventions documentation.

To avoid findings, sponsors must maintain coding guidelines, training logs, and reconciliation records. Regular audits and mock inspections can strengthen inspection readiness. Reference resources such as the EU Clinical Trials Register demonstrate regulatory emphasis on standardized coding practices.

Key Takeaways

The MedDRA hierarchy provides a structured approach to adverse event coding, ensuring accuracy, consistency, and global harmonization. Clinical teams must:

• Understand the five levels of MedDRA: LLT → PT → HLT → HLGT → SOC.
• Apply coding conventions consistently to avoid misclassification.
• Maintain updated databases aligned with new MedDRA versions.
• Document coding decisions for inspection readiness.
• Train coders and CRAs to navigate the hierarchy effectively.

By mastering the MedDRA hierarchy, sponsors and CROs can ensure high-quality safety data, meet regulatory expectations, and protect patients through accurate pharmacovigilance practices.