Inferensys

Glossary

Standardised MedDRA Query (SMQ)

A pre-defined grouping of MedDRA terms designed to assist in the identification and retrieval of potential safety cases related to a specific medical condition or syndrome during pharmacovigilance signal detection.
Developer working on RAG retrieval system, document chunks visible on screen, technical workspace with code editor.
PHARMACOVIGILANCE

What is Standardised MedDRA Query (SMQ)?

A pre-defined grouping of MedDRA terms designed to assist in the identification and retrieval of potential safety cases related to a specific medical condition or syndrome during pharmacovigilance signal detection.

A Standardised MedDRA Query (SMQ) is a validated, pre-coordinated set of MedDRA terms assembled to retrieve cases potentially related to a defined medical condition or safety topic. Developed by the ICH and maintained by the MSSO, SMQs address the challenge of identifying complex syndromes—like anaphylaxis or acute pancreatitis—that cannot be captured by a single preferred term, ensuring consistent case retrieval across databases.

SMQs function through a hierarchical algorithmic structure of broad and narrow search scopes. The narrow scope targets terms highly specific to the condition, maximizing precision, while the broad scope captures related signs, symptoms, and investigations to maximize sensitivity. This dual-scope design allows safety reviewers to balance signal detection power against the noise of false positives during aggregate reporting and disproportionality analysis.

ANATOMY OF A SAFETY QUERY

Core Characteristics of SMQs

Standardised MedDRA Queries are not simple keyword searches; they are meticulously curated, hierarchical groupings of MedDRA terms designed to retrieve potential safety cases with high sensitivity and specificity.

01

Hierarchical Term Structure

SMQs are constructed using a logical hierarchy to ensure comprehensive retrieval of adverse event reports, regardless of how specifically the event was coded.

  • Narrow Terms (Category A): Highly specific terms that definitively identify the condition of interest (e.g., 'Myocardial infarction').
  • Broad Terms (Category B): Less specific terms that may indicate the condition but require further review (e.g., 'Chest pain').
  • Algorithmic Logic: Cases are retrieved using Boolean logic (e.g., a narrow term OR a combination of broad terms).
02

Algorithmic Retrieval Logic

Unlike simple flat lists, SMQs apply algorithmic categories to balance search sensitivity against retrieval precision.

  • Category A (Narrow): Maximizes specificity; a single hit is often sufficient to identify a case.
  • Category B (Broad): Maximizes sensitivity; used to catch potential cases coded with vague or non-specific terminology.
  • Category C (Additional): Includes terms related to laboratory tests, investigations, or procedures that support the diagnosis but do not represent the condition itself.
03

Production and Maintenance

SMQs are developed and maintained by the CIOMS Working Group on SMQs and released biannually by the MSSO (Maintenance and Support Services Organization) in sync with the MedDRA dictionary.

  • Versioning: SMQs are updated to reflect new medical knowledge and changes in MedDRA terminology.
  • Testing: Each SMQ undergoes rigorous testing against legacy safety databases to validate its retrieval performance before release.
04

Design for Signal Detection

The primary purpose of an SMQ is to facilitate case retrieval for signal detection and aggregate reporting, not to replace medical assessment.

  • Standardized Case Series: SMQs allow safety scientists to pull a consistent, pre-defined cohort of cases across different products and databases.
  • Triage Tool: They serve as a high-sensitivity filter to reduce the manual workload of searching for complex syndromes like anaphylaxis or acute pancreatitis across millions of records.
05

Special SMQ Categories

Beyond standard medical conditions, specialized SMQs exist to address specific pharmacovigilance needs.

  • Anaphylactic Reaction (SMQ): A highly validated query combining narrow terms for confirmed anaphylaxis with broad terms for potential allergic manifestations.
  • COVID-19 (SMQ): A rapidly developed SMQ to track adverse events in the context of the pandemic.
  • Drug Abuse and Dependence (SMQ): Targets terms related to substance misuse, tolerance, and withdrawal syndromes.
06

Limitations and Caveats

While powerful, SMQs have inherent limitations that must be managed by the safety reviewer.

  • Coding Variability: The accuracy of retrieval is entirely dependent on the quality and granularity of the original verbatim term coding.
  • False Positives: Broad terms (Category B) can retrieve many irrelevant cases, requiring manual triage.
  • Not Diagnostic: An SMQ hit does not confirm the diagnosis; it only identifies a case that warrants clinical review.
STANDARDISED MEDDRA QUERIES

Frequently Asked Questions

Clarifying the design, application, and maintenance of pre-defined MedDRA term groupings used to retrieve potential safety cases during pharmacovigilance signal detection.

A Standardised MedDRA Query (SMQ) is a pre-defined, validated grouping of MedDRA terms designed to assist in the consistent identification and retrieval of potential Individual Case Safety Reports (ICSRs) related to a specific medical condition or syndrome. SMQs function as sophisticated database filters that operate across the MedDRA hierarchy. They include Preferred Terms (PTs) that describe the condition itself, along with associated signs, symptoms, and laboratory abnormalities. The query logic is structured into algorithmic categories—narrow terms for high specificity and broad terms for high sensitivity—allowing safety scientists to adjust the scope of their search. This standardized approach eliminates the variability inherent in ad-hoc term list creation, ensuring that two different organizations querying the same safety database for 'acute pancreatitis' will retrieve a comparable set of cases, which is critical for consistent global signal detection and aggregate reporting.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.