Vocab. MEDDRA
The Medical Dictionary for Regulatory Activities (MedDRA) is a clinically validated international medical terminology thesaurus and adverse event classification dictionary used by regulatory authorities and the biopharmaceutical industry during the regulatory process, from pre-marketing (clinical research phase 0 to phase 3) to post-marketing activities (pharmacovigilance or clinical research phase 4), and for safety information data entry, retrieval, evaluation, and presentation. Products covered by the scope of MedDRA include pharmaceuticals, biologics, vaccines and drug-device combination products.
The source data is provided by:
- MedDRA Website that is supported by the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH).
-
MedDRA
Support Documentation:
-
What’s New MedDRA Version 27.1
-
Introductory Guide MedDRA Version 27.1
-
Introductory Guide for Standardised MedDRA Queries (SMQs) Version 27.1
-
Distribution File Format Version 27.1
-
- MedDRA Concept Description
- SNOMED CT MedDRA Simple Map Package
The procedures for transforming Concepts from the source to the OMOP Standard Vocabularies can be found on the OHDSI GitHub.
The MedDRA dictionary is organized with a five-level hierarchy. The highest or broadest level is System Organ Class (SOC), further divided into High-Level Group Terms (HLGT), High-Level Terms (HLT), Preferred Terms (PT) and finally into the most granular Lowest Level Terms (LLT).
Also, the MedDRA dictionary includes Standardised MedDRA Queries (SMQs). SMQs are groupings of terms that relate to a defined medical condition or area of interest.
MedDRA concepts have one distinct name per concept.
Concept codes are taken from the MedDRA codes (llt_code, pt_code, hlt_code, hlgt_code, soc_code from 1_low_level_term, 1_pref_term, 1_hlt_pref_term, 1_hltg_pref_term, 1_soc_term, respectively).
The majority of MedDRA concepts are in the “Condition” domain. Others domains: Measurement, Procedure and Observation.
The MedDRA concepts are composed from the following Concept Classes: SOC(System Organ Class - the highest level of MedDRA hierarchy), HLGT (High-Level Group Terms), HLT (High-Level Terms), PT (Preferred Terms), LLT (Lowest Level Terms)
MedDRA domain and concept classes were assigned pursuant to the following criteria:
| Source | Dependencies | Domain | Concept Class |
| MedDRA soc_term table | “soc_name” field value contains 'Investigations' | Measurement | SOC |
| soc_name field value contains IN ('Product issues', 'Social circumstances' ) | Observation | ||
| “soc_name” field value contains 'Surgical and medical procedures' | Procedure | ||
| “soc_name” field value contains 'disorders|Infections|Neoplasms|Injury, poisoning and procedural complications|Pregnancy, puerperium and perinatal conditions' | Condition | ||
| MedDRA hlgt_pref_term table |
“hlgt_name” field value contains 'Therapeutic and nontherapeutic effects
(excl toxicity)'
OR soc_name IN ( 'Product issues', 'Social circumstances') |
Observation | HLGT |
| “soc_name” field value contains 'disorders|Infections|Neoplasms|Injury, poisoning and procedural complications|Pregnancy, puerperium and perinatal conditions' | Condition | ||
| “soc_name” field value contains 'Surgical and medical procedures' | Procedure | ||
| “soc_name” field value contains 'Investigations' | Measurement | ||
| MedDRA hlt_pref_term table |
“hlt_name” field value contains 'exposures|Physical examination procedures
and organ system status'
OR “hlgt_name” field value contains 'Therapeutic and nontherapeutic effects (excl toxicity)' OR “soc_name” IN ('Product issues', 'Social circumstances') |
Observation | HLT |
|
“hlt_name” field value contains 'histopathology|imaging|procedure'
OR “soc_name” contains 'Surgical and medical procedures' |
Procedure | ||
|
“hlt_name” field value contains 'Gene mutations and other alterations NEC'
OR “soc_name” contains 'Investigations' |
'Measurement' | ||
| “soc_name” field value contains 'disorders|Infections|Neoplasms|Injury, poisoning and procedural complications|Pregnancy, puerperium and perinatal conditions' | Condition | ||
| MedDRA pref_term table |
“pt_name” field value contains 'monitoring|centesis|imaging|screen'
OR “hlt_name” contains 'histopathology|imaging|procedure' OR “soc_name” contains 'Surgical and medical procedures' |
Procedure | PT |
|
“hlt_name” field value contains 'exposures|Physical examination procedures
and organ system status'
OR “hlgt_name” contains 'Therapeutic and nontherapeutic effects (excl toxicity)' OR “soc_name” IN ('Product issues', 'Social circumstances' ) |
Observation | ||
|
“hlt_name” field value contains 'Gene mutations and other alterations NEC'
OR “soc_name” contains 'Investigations' |
Measurement | ||
| “soc_name” field contains 'disorders|Infections|Neoplasms|Injury, poisoning and procedural complications|Pregnancy, puerperium and perinatal conditions' | Condition | ||
| MedDRA low_level_term table | “soc_name” field value contains 'disorders|Infections|Neoplasms|Injury, poisoning and procedural complications|Pregnancy, puerperium and perinatal conditions' | Condition | LLT |
| “pt_name” field value contains:
'Monitoring|centesis|imaging|screen' OR “hlt_name” contains 'histopathology|imaging|procedure' OR “soc_name” contains 'Surgical and medical procedures' |
Procedure | ||
|
“hlt_name” field value contains 'exposures|Physical examination procedures
and organ system status'
OR “hlgt_name” contains 'Therapeutic and nontherapeutic effects (excl toxicity)' OR “soc_name” IN ('Product issues', 'Social circumstances') |
Observation | ||
|
“hlt_name” field value contains 'Gene mutations and other alterations NEC'
OR “soc_name” contains 'Investigations' |
Measurement |
Relationships are defined within MedDRA and between MedDRA and OMOP Standard Vocabularies (most commonly SNOMED).
A purpose of Internal MedDRA relationships is to build a MedDRA Hierarchy, which makes it easier to sort and browse the database for flexible data retrieval and for the clear presentation of data. The five-level structure of this terminology provides options for retrieving data by specific or broad groupings, according to the level of specificity required. The Lowest Level Term (LLT) level provides maximum specificity.
| Relationship (reverse relationship) | From | To |
| Is a | Descendant MedDRA Class | Ancestor MedDRA Class |
| Subsumes | Ancestor MedDRA Class | Descendant MedDRA Class |
| MedDRA contained in SMQ (MedDRA) (SMQ consists of MedDRA (MedDRA)) |
MedDRA | SMQ |
Most MedDRA concepts are Classifications or non-Standard concepts which means that they are mapped to the respective Standard concepts defined by the vocabulary team. Technically, they have single (1-to-1) or several (1-to-many) “Maps to” relationships in the concept_relationship_table. The purpose of External MedDRA relationships to SNOMED is to map them with Standard concepts (such as SNOMED) and use them for hierarchy construction and data analysis in OHDSI models.
Current external MedDRA relationships:
-
Maps to / Maps to value to OMOP standard vocabulary (most commonly SNOMED)
-
Is a / Subsumes between MedDRA and SNOMED / OMOP extension only
In case of complete semantic correspondence between the MedDRA and SNOMED concepts, the MedDRA concept is positioned above the SNOMED concept when constructing the hierarchy. In case of incomplete correspondence, various scenarios are possible, where the MedDRA concept in the hierarchy can be either higher (downhill mapping to SNOMED) or lower (uphill mapping to SNOMED) than the corresponding SNOMED concept. See the schema attached.
Most MedDRA concepts are Classifications or non-Standard concepts. That means they have to be mapped to the corresponding Standard Concepts using the CONCEPT_RELATIONSHIP table ("Maps to" and occasionally "Maps to value" records). Most of them are mapped to single SNOMED Concepts, generating one-to-one records in the CONCEPT_RELATIONSHIP table, but some of them create multiple records or have mappings to other domains.
When using MedDRA concepts to construct concept sets based on the MedDRA-SNOMED hierarchy, there might be cases where not all underlying child concepts from SNOMED are fully included. In such instances, it is recommended to conduct additional checks for the potential inclusion of additional SNOMED concepts when constructing the final concept set.
Using MedDRA concepts as classification is available for PT and LLT concepts with valid “Maps to” links (and ‘Is a / Subsumes’ links accordingly constructed on their basis). Other PT and LLT MedDRA concepts without corresponding “Maps to” links are considered non-standard (previously they were classification concepts).