MedDRA levels for data engineers
Synthetic data. Not submission-ready. Not a copy of official IG mapping tables. Licensed vocabularies are not republished here.
The problem
Safety and clinical datasets often need a coded adverse-event term, not just a verbatim string. MedDRA (Medical Dictionary for Regulatory Activities) is a licensed terminology used widely for that purpose. Data engineers get asked to “just join MedDRA” as if it were a public CSV. It is not, and the hierarchy is not a single column.
What official public material says
The official MedDRA hierarchy page describes five levels, from more specific to more general:
| Level | Official abbreviation | Role, in the official description’s terms |
|---|---|---|
| Lowest Level Term | LLT | The most specific level; official text says LLTs parallel how information is communicated and support assigning terms in a user database. |
| Preferred Term | PT | Official text: a distinct descriptor for a single medical concept. Each LLT is linked to only one PT. Each PT has at least one LLT. |
| High Level Term | HLT | Official text: related PTs grouped by anatomy, pathology, physiology, aetiology, or function. |
| High Level Group Term | HLGT | Official text: related HLTs grouped on similar principles. |
| System Organ Class | SOC | Official text: the most general grouping, including groupings by aetiology, manifestation site, or purpose. |
This site does not list MedDRA terms, codes, synonyms, or SOC contents. Those belong in a licensed MedDRA distribution. Version matters: analyses should record which MedDRA version was used, because the dictionary is updated over time (see official MedDRA sources for the current release process).
MedDRA also documents mapping activities and has published a download API announcement for licensed users. Use those official channels after you have a license.
A working (non-dictionary) example
In the synthetic AE extract, the source verbatim values are “mild headache after first dose” and “upset stomach”. An engineer’s pipeline should treat those as verbatim source text, store them unchanged, and only attach a coded term inside a system that has a licensed MedDRA file and a documented coding convention (who codes, when a query is raised, how version upgrades are handled).
There is no MedDRA code in this example on purpose.
The gotcha
Joining on a Preferred Term display string is unstable. Official structure is identifier- and version-based. A typo, a case change, or a version upgrade can break a string join.
Counting at the wrong level changes safety pictures: LLT is more specific than PT; rolling up to SOC is a different question than listing PTs. Official training, not a warehouse instinct, decides which level a report uses.
OMOP and MedDRA are not freely interchangeable. Some commercial or licensed vocabularies are excluded from a given tool because of licensing — if a platform documents that limitation, believe it, and use official MedDRA plus official OHDSI processes rather than scraping terms into a repo.
When not to use this
- Do not download, cache, or commit MedDRA files into a public site or git repo.
- Do not type remembered terms into a mapping table “to get unblocked.”
- Do not treat this hierarchy sketch as coding guidelines.
The five-level descriptions paraphrase the official public MedDRA hierarchy page linked below. No MedDRA terms or codes are included. No MedDRA file was downloaded or opened.