eduKateSG · Why Science?
Turn a clinician’s exact words into consistent medical data without losing the meaning that makes a safety signal worth investigating
Explore ICH M1 MedDRA through its five-level hierarchy, multiaxial links, careful term selection, version control, Standardised MedDRA Queries and transparent retrieval.
A headache, migraine and head discomfort may sound similar in casual conversation, yet safety analysis depends on preserving the idea that was actually reported. Shared terminology lets many organisations compare records while retaining enough specificity for medical review.
ICH describes MedDRA, the Medical Dictionary for Regulatory Activities, as a rich and highly specific standardised medical terminology developed to facilitate international sharing of regulatory information. It is used across registration, documentation and safety monitoring before and after a product is authorised.
Did you know? MedDRA has five linked levels, from very specific Lowest Level Terms through Preferred Terms, High Level Terms, High Level Group Terms and the broadest System Organ Classes. The hierarchy supports both faithful coding and broader retrieval.
For students, M1 turns vocabulary into data science. The useful habit is cheerful but exact: keep the reporter’s words, choose the closest supported concept, check the hierarchy and record the terminology version so another analyst can reproduce the result.
Chapter index
Chapters 1–9: MedDRA purpose, hierarchy, codes, versions and multilingual use
- 1. M1 gives regulatory science a shared medical language
- 2. The terminology supports a product across its life cycle
- 3. Five levels connect specific reports to broad medical groupings
- 4. Unique non-expressive codes stabilise identity
- 5. Code at the Lowest Level Term when the report supports it
- 6. Check the hierarchy above every selected term
- 7. Preserve every reported concept without inventing one
- 8. Current and non-current terms protect history differently
- 9. Multiaxiality supports more than one medical view
Chapters 10–17: term selection, multiaxial retrieval, SMQs, quality control and evidence receipts
- 10. The primary SOC helps prevent double counting
- 11. Grouping levels are designed for retrieval and presentation
- 12. Standardised MedDRA Queries begin safety investigations
- 13. An SMQ result is a search set rather than a diagnosis
- 14. Term selection and data retrieval are separate disciplines
- 15. Version control keeps counts reproducible
- 16. Quality review combines automation with medical judgement
- 17. A complete M1 receipt reconstructs language into evidence
CHAPTER 1 OF 17 · Understand the shared language
1. M1 gives regulatory science a shared medical language
MedDRA was launched in 1999 after ICH development in the late 1990s. A shared terminology helps sponsors and regulators exchange adverse events, indications, medical history, investigations and other medical concepts without relying on local synonyms alone.
A shared language becomes scientifically useful in m1 gives regulatory science a shared medical language when it preserves the source and exposes the grouping route. MedDRA was launched in 1999 after ICH development in the late 1990s. A shared terminology helps sponsors and regulators exchange adverse events, indications, medical history, investigations and other medical concepts without relying on local synonyms alone. Keep this guardrail beside the code: A standard term cannot add clinical detail that the reporter did not provide.
Try this
Make a term-selection card for m1 gives regulatory science a shared medical language. Trace m1 gives regulatory science a shared medical language from verbatim source wording through LLT, PT and the intended medical grouping. Keep the verbatim wording beside the code and hierarchy. Preserve this limit: A standard term cannot add clinical detail that the reporter did not provide.
A strong science note separates observation from interpretation. Trace m1 gives regulatory science a shared medical language from verbatim source wording through LLT, PT and the intended medical grouping. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Trace m1 gives regulatory science a shared medical language from verbatim source wording through LLT, PT and the intended medical grouping. Keep this boundary visible: A standard term cannot add clinical detail that the reporter did not provide.
CHAPTER 2 OF 17 · Understand the shared language
2. The terminology supports a product across its life cycle
Official ICH material describes use for registration, documentation and safety monitoring of medical products through pre-marketing and post-marketing activities. The same vocabulary can connect clinical trials, individual case reports, aggregate reviews and labels while each use keeps its own evidence rules.
For the terminology supports a product across its life cycle, a neat label is valuable only when its medical placement and version are visible. Official ICH material describes use for registration, documentation and safety monitoring of medical products through pre-marketing and post-marketing activities. The same vocabulary can connect clinical trials, individual case reports, aggregate reviews and labels while each use keeps its own evidence rules. Respect this boundary: A terminology version and coding convention are part of the result.
Try this
Run a retrieval rehearsal for the terminology supports a product across its life cycle. Challenge whether the terminology supports a product across its life cycle preserves specificity, chronology and the reporter’s meaning. Compare a specific and broader grouping, then explain any change in counts. Keep this boundary: A terminology version and coding convention are part of the result.
A strong science note separates observation from interpretation. Challenge whether the terminology supports a product across its life cycle preserves specificity, chronology and the reporter’s meaning. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Challenge whether the terminology supports a product across its life cycle preserves specificity, chronology and the reporter’s meaning. Keep this boundary visible: A terminology version and coding convention are part of the result.
CHAPTER 3 OF 17 · Understand the shared language
3. Five levels connect specific reports to broad medical groupings
The hierarchy runs from Lowest Level Term, or LLT, to Preferred Term, HLT, HLGT and System Organ Class. LLTs support coding of reported language; PTs represent single medical concepts; HLTs and HLGTs group concepts for retrieval; SOCs provide the broadest categories.
Imagine five levels connect specific reports to broad medical groupings as a ladder from a person’s words to a population-level pattern. The hierarchy runs from Lowest Level Term, or LLT, to Preferred Term, HLT, HLGT and System Organ Class. LLTs support coding of reported language; PTs represent single medical concepts; HLTs and HLGTs group concepts for retrieval; SOCs provide the broadest categories. Do not remove this rung: A retrieved case set is not by itself proof of a diagnosis or causal relationship.
Try this
Audit the vocabulary trail for five levels connect specific reports to broad medical groupings. Reconstruct five levels connect specific reports to broad medical groupings with the exact MedDRA release, code, hierarchy path and reviewer rule. Record the release, coding convention, reviewer and query so another analyst can repeat it. Respect this limit: A retrieved case set is not by itself proof of a diagnosis or causal relationship.
A strong science note separates observation from interpretation. Reconstruct five levels connect specific reports to broad medical groupings with the exact MedDRA release, code, hierarchy path and reviewer rule. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Reconstruct five levels connect specific reports to broad medical groupings with the exact MedDRA release, code, hierarchy path and reviewer rule. Keep this boundary visible: A retrieved case set is not by itself proof of a diagnosis or causal relationship.
CHAPTER 4 OF 17 · Understand the shared language
4. Unique non-expressive codes stabilise identity
Each MedDRA term has a unique numeric code. The code carries identity across supported languages and avoids treating translated wording as a different medical concept. A readable label remains important for people, while the code protects exchange between systems.
A shared language becomes scientifically useful in unique non-expressive codes stabilise identity when it preserves the source and exposes the grouping route. Each MedDRA term has a unique numeric code. The code carries identity across supported languages and avoids treating translated wording as a different medical concept. A readable label remains important for people, while the code protects exchange between systems. Keep this guardrail beside the code: Multiaxial retrieval requires an explicit counting rule.
Try this
Make a term-selection card for unique non-expressive codes stabilise identity. Re-run unique non-expressive codes stabilise identity after a version change and document every term or query difference. Keep the verbatim wording beside the code and hierarchy. Preserve this limit: Multiaxial retrieval requires an explicit counting rule.
A strong science note separates observation from interpretation. Re-run unique non-expressive codes stabilise identity after a version change and document every term or query difference. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Re-run unique non-expressive codes stabilise identity after a version change and document every term or query difference. Keep this boundary visible: Multiaxial retrieval requires an explicit counting rule.
CHAPTER 5 OF 17 · Code what was actually reported
5. Code at the Lowest Level Term when the report supports it
MedDRA term-selection guidance tells users to select the LLT that most accurately reflects the reported information. The coder should not diagnose, generalise or add detail that is absent from the source merely to reach a more familiar preferred term.
For code at the lowest level term when the report supports it, a neat label is valuable only when its medical placement and version are visible. MedDRA term-selection guidance tells users to select the LLT that most accurately reflects the reported information. The coder should not diagnose, generalise or add detail that is absent from the source merely to reach a more familiar preferred term. Respect this boundary: A standard term cannot add clinical detail that the reporter did not provide.
Try this
Run a retrieval rehearsal for code at the lowest level term when the report supports it. Trace code at the lowest level term when the report supports it from verbatim source wording through LLT, PT and the intended medical grouping. Compare a specific and broader grouping, then explain any change in counts. Keep this boundary: A standard term cannot add clinical detail that the reporter did not provide.
A strong science note separates observation from interpretation. Trace code at the lowest level term when the report supports it from verbatim source wording through LLT, PT and the intended medical grouping. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Trace code at the lowest level term when the report supports it from verbatim source wording through LLT, PT and the intended medical grouping. Keep this boundary visible: A standard term cannot add clinical detail that the reporter did not provide.
CHAPTER 6 OF 17 · Code what was actually reported
6. Check the hierarchy above every selected term
The official Points to Consider says to inspect the PT, HLT, HLGT and SOC placement above a candidate LLT. This catches a lexical match whose medical placement does not reflect the reporter’s meaning and makes the later grouping route visible.
Imagine check the hierarchy above every selected term as a ladder from a person’s words to a population-level pattern. The official Points to Consider says to inspect the PT, HLT, HLGT and SOC placement above a candidate LLT. This catches a lexical match whose medical placement does not reflect the reporter’s meaning and makes the later grouping route visible. Do not remove this rung: A terminology version and coding convention are part of the result.
Try this
Audit the vocabulary trail for check the hierarchy above every selected term. Challenge whether check the hierarchy above every selected term preserves specificity, chronology and the reporter’s meaning. Record the release, coding convention, reviewer and query so another analyst can repeat it. Respect this limit: A terminology version and coding convention are part of the result.
A strong science note separates observation from interpretation. Challenge whether check the hierarchy above every selected term preserves specificity, chronology and the reporter’s meaning. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Challenge whether check the hierarchy above every selected term preserves specificity, chronology and the reporter’s meaning. Keep this boundary visible: A terminology version and coding convention are part of the result.
CHAPTER 7 OF 17 · Code what was actually reported
7. Preserve every reported concept without inventing one
A narrative may contain a diagnosis, signs, tests and treatment. Term selection can require more than one concept when each is explicitly reported, but unnecessary multiple coding can create redundant counts. The coding convention should be documented and applied consistently.
A shared language becomes scientifically useful in preserve every reported concept without inventing one when it preserves the source and exposes the grouping route. A narrative may contain a diagnosis, signs, tests and treatment. Term selection can require more than one concept when each is explicitly reported, but unnecessary multiple coding can create redundant counts. The coding convention should be documented and applied consistently. Keep this guardrail beside the code: A retrieved case set is not by itself proof of a diagnosis or causal relationship.
Try this
Make a term-selection card for preserve every reported concept without inventing one. Reconstruct preserve every reported concept without inventing one with the exact MedDRA release, code, hierarchy path and reviewer rule. Keep the verbatim wording beside the code and hierarchy. Preserve this limit: A retrieved case set is not by itself proof of a diagnosis or causal relationship.
A strong science note separates observation from interpretation. Reconstruct preserve every reported concept without inventing one with the exact MedDRA release, code, hierarchy path and reviewer rule. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Reconstruct preserve every reported concept without inventing one with the exact MedDRA release, code, hierarchy path and reviewer rule. Keep this boundary visible: A retrieved case set is not by itself proof of a diagnosis or causal relationship.
CHAPTER 8 OF 17 · Code what was actually reported
8. Current and non-current terms protect history differently
MedDRA retains certain non-current LLTs so historical data remain accessible, but flags them as unsuitable for continued coding. New entries should use current terms, while migration and retrieval must keep older records traceable rather than silently rewriting their source history.
For current and non-current terms protect history differently, a neat label is valuable only when its medical placement and version are visible. MedDRA retains certain non-current LLTs so historical data remain accessible, but flags them as unsuitable for continued coding. New entries should use current terms, while migration and retrieval must keep older records traceable rather than silently rewriting their source history. Respect this boundary: Multiaxial retrieval requires an explicit counting rule.
Try this
Run a retrieval rehearsal for current and non-current terms protect history differently. Re-run current and non-current terms protect history differently after a version change and document every term or query difference. Compare a specific and broader grouping, then explain any change in counts. Keep this boundary: Multiaxial retrieval requires an explicit counting rule.
A strong science note separates observation from interpretation. Re-run current and non-current terms protect history differently after a version change and document every term or query difference. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Re-run current and non-current terms protect history differently after a version change and document every term or query difference. Keep this boundary visible: Multiaxial retrieval requires an explicit counting rule.
CHAPTER 9 OF 17 · Retrieve patterns without double counting
9. Multiaxiality supports more than one medical view
A Preferred Term may be linked to more than one SOC when different clinical classifications are useful. One SOC is designated primary for standard cumulative presentation, while secondary links help retrieval by another relevant route.
Imagine multiaxiality supports more than one medical view as a ladder from a person’s words to a population-level pattern. A Preferred Term may be linked to more than one SOC when different clinical classifications are useful. One SOC is designated primary for standard cumulative presentation, while secondary links help retrieval by another relevant route. Do not remove this rung: A standard term cannot add clinical detail that the reporter did not provide.
Try this
Audit the vocabulary trail for multiaxiality supports more than one medical view. Trace multiaxiality supports more than one medical view from verbatim source wording through LLT, PT and the intended medical grouping. Record the release, coding convention, reviewer and query so another analyst can repeat it. Respect this limit: A standard term cannot add clinical detail that the reporter did not provide.
A strong science note separates observation from interpretation. Trace multiaxiality supports more than one medical view from verbatim source wording through LLT, PT and the intended medical grouping. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Trace multiaxiality supports more than one medical view from verbatim source wording through LLT, PT and the intended medical grouping. Keep this boundary visible: A standard term cannot add clinical detail that the reporter did not provide.
CHAPTER 10 OF 17 · Retrieve patterns without double counting
10. The primary SOC helps prevent double counting
When data are presented across all SOCs, the primary allocation provides one standard place for a PT. Analysts can deliberately use secondary paths for a specific question, but must state the rule so one case or concept is not counted twice without explanation.
A shared language becomes scientifically useful in the primary soc helps prevent double counting when it preserves the source and exposes the grouping route. When data are presented across all SOCs, the primary allocation provides one standard place for a PT. Analysts can deliberately use secondary paths for a specific question, but must state the rule so one case or concept is not counted twice without explanation. Keep this guardrail beside the code: A terminology version and coding convention are part of the result.
Try this
Make a term-selection card for the primary soc helps prevent double counting. Challenge whether the primary soc helps prevent double counting preserves specificity, chronology and the reporter’s meaning. Keep the verbatim wording beside the code and hierarchy. Preserve this limit: A terminology version and coding convention are part of the result.
A strong science note separates observation from interpretation. Challenge whether the primary soc helps prevent double counting preserves specificity, chronology and the reporter’s meaning. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Challenge whether the primary soc helps prevent double counting preserves specificity, chronology and the reporter’s meaning. Keep this boundary visible: A terminology version and coding convention are part of the result.
CHAPTER 11 OF 17 · Retrieve patterns without double counting
11. Grouping levels are designed for retrieval and presentation
HLTs and HLGTs aggregate related PTs into broader medical categories. They help analysts move above individual preferred concepts, yet their breadth varies and they are not the ordinary level for coding an original report.
For grouping levels are designed for retrieval and presentation, a neat label is valuable only when its medical placement and version are visible. HLTs and HLGTs aggregate related PTs into broader medical categories. They help analysts move above individual preferred concepts, yet their breadth varies and they are not the ordinary level for coding an original report. Respect this boundary: A retrieved case set is not by itself proof of a diagnosis or causal relationship.
Try this
Run a retrieval rehearsal for grouping levels are designed for retrieval and presentation. Reconstruct grouping levels are designed for retrieval and presentation with the exact MedDRA release, code, hierarchy path and reviewer rule. Compare a specific and broader grouping, then explain any change in counts. Keep this boundary: A retrieved case set is not by itself proof of a diagnosis or causal relationship.
A strong science note separates observation from interpretation. Reconstruct grouping levels are designed for retrieval and presentation with the exact MedDRA release, code, hierarchy path and reviewer rule. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Reconstruct grouping levels are designed for retrieval and presentation with the exact MedDRA release, code, hierarchy path and reviewer rule. Keep this boundary visible: A retrieved case set is not by itself proof of a diagnosis or causal relationship.
CHAPTER 12 OF 17 · Retrieve patterns without double counting
12. Standardised MedDRA Queries begin safety investigations
Official MedDRA material defines SMQs as groupings of terms developed to facilitate retrieval of coded data as a first step in investigating safety issues. Some have narrow and broad scopes or algorithmic structures, and each remains version-specific.
Imagine standardised meddra queries begin safety investigations as a ladder from a person’s words to a population-level pattern. Official MedDRA material defines SMQs as groupings of terms developed to facilitate retrieval of coded data as a first step in investigating safety issues. Some have narrow and broad scopes or algorithmic structures, and each remains version-specific. Do not remove this rung: Multiaxial retrieval requires an explicit counting rule.
Try this
Audit the vocabulary trail for standardised meddra queries begin safety investigations. Re-run standardised meddra queries begin safety investigations after a version change and document every term or query difference. Record the release, coding convention, reviewer and query so another analyst can repeat it. Respect this limit: Multiaxial retrieval requires an explicit counting rule.
A strong science note separates observation from interpretation. Re-run standardised meddra queries begin safety investigations after a version change and document every term or query difference. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Re-run standardised meddra queries begin safety investigations after a version change and document every term or query difference. Keep this boundary visible: Multiaxial retrieval requires an explicit counting rule.
CHAPTER 13 OF 17 · Keep every conclusion reproducible
13. An SMQ result is a search set rather than a diagnosis
A retrieved case may need medical review, de-duplication, chronology and exposure assessment. SMQs do not cover every safety topic, and their content can change with successive releases, so a positive hit is evidence to inspect rather than proof of causation.
A shared language becomes scientifically useful in an smq result is a search set rather than a diagnosis when it preserves the source and exposes the grouping route. A retrieved case may need medical review, de-duplication, chronology and exposure assessment. SMQs do not cover every safety topic, and their content can change with successive releases, so a positive hit is evidence to inspect rather than proof of causation. Keep this guardrail beside the code: A standard term cannot add clinical detail that the reporter did not provide.
Try this
Make a term-selection card for an smq result is a search set rather than a diagnosis. Trace an smq result is a search set rather than a diagnosis from verbatim source wording through LLT, PT and the intended medical grouping. Keep the verbatim wording beside the code and hierarchy. Preserve this limit: A standard term cannot add clinical detail that the reporter did not provide.
A strong science note separates observation from interpretation. Trace an smq result is a search set rather than a diagnosis from verbatim source wording through LLT, PT and the intended medical grouping. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Trace an smq result is a search set rather than a diagnosis from verbatim source wording through LLT, PT and the intended medical grouping. Keep this boundary visible: A standard term cannot add clinical detail that the reporter did not provide.
CHAPTER 14 OF 17 · Keep every conclusion reproducible
14. Term selection and data retrieval are separate disciplines
The M1 Points to Consider programme maintains one document for MedDRA Term Selection and another for MedDRA Data Retrieval and Presentation. Separating input rules from analysis rules prevents the search strategy from quietly changing how source reports were coded.
For term selection and data retrieval are separate disciplines, a neat label is valuable only when its medical placement and version are visible. The M1 Points to Consider programme maintains one document for MedDRA Term Selection and another for MedDRA Data Retrieval and Presentation. Separating input rules from analysis rules prevents the search strategy from quietly changing how source reports were coded. Respect this boundary: A terminology version and coding convention are part of the result.
Try this
Run a retrieval rehearsal for term selection and data retrieval are separate disciplines. Challenge whether term selection and data retrieval are separate disciplines preserves specificity, chronology and the reporter’s meaning. Compare a specific and broader grouping, then explain any change in counts. Keep this boundary: A terminology version and coding convention are part of the result.
A strong science note separates observation from interpretation. Challenge whether term selection and data retrieval are separate disciplines preserves specificity, chronology and the reporter’s meaning. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Challenge whether term selection and data retrieval are separate disciplines preserves specificity, chronology and the reporter’s meaning. Keep this boundary visible: A terminology version and coding convention are part of the result.
CHAPTER 15 OF 17 · Keep every conclusion reproducible
15. Version control keeps counts reproducible
MedDRA evolves as medicine, products and reporting needs change. An analysis should record the release used for coding and retrieval, the date of any up-versioning, the SMQ version and the treatment of changed or non-current terms.
Imagine version control keeps counts reproducible as a ladder from a person’s words to a population-level pattern. MedDRA evolves as medicine, products and reporting needs change. An analysis should record the release used for coding and retrieval, the date of any up-versioning, the SMQ version and the treatment of changed or non-current terms. Do not remove this rung: A retrieved case set is not by itself proof of a diagnosis or causal relationship.
Try this
Audit the vocabulary trail for version control keeps counts reproducible. Reconstruct version control keeps counts reproducible with the exact MedDRA release, code, hierarchy path and reviewer rule. Record the release, coding convention, reviewer and query so another analyst can repeat it. Respect this limit: A retrieved case set is not by itself proof of a diagnosis or causal relationship.
A strong science note separates observation from interpretation. Reconstruct version control keeps counts reproducible with the exact MedDRA release, code, hierarchy path and reviewer rule. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Reconstruct version control keeps counts reproducible with the exact MedDRA release, code, hierarchy path and reviewer rule. Keep this boundary visible: A retrieved case set is not by itself proof of a diagnosis or causal relationship.
CHAPTER 16 OF 17 · Keep every conclusion reproducible
16. Quality review combines automation with medical judgement
Edit checks can find invalid codes, outdated versions, missing fields and inconsistent mappings. Medical review still asks whether selected concepts match the narrative and whether a retrieval strategy fits the safety question, population and clinical context.
A shared language becomes scientifically useful in quality review combines automation with medical judgement when it preserves the source and exposes the grouping route. Edit checks can find invalid codes, outdated versions, missing fields and inconsistent mappings. Medical review still asks whether selected concepts match the narrative and whether a retrieval strategy fits the safety question, population and clinical context. Keep this guardrail beside the code: Multiaxial retrieval requires an explicit counting rule.
Try this
Make a term-selection card for quality review combines automation with medical judgement. Re-run quality review combines automation with medical judgement after a version change and document every term or query difference. Keep the verbatim wording beside the code and hierarchy. Preserve this limit: Multiaxial retrieval requires an explicit counting rule.
A strong science note separates observation from interpretation. Re-run quality review combines automation with medical judgement after a version change and document every term or query difference. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Re-run quality review combines automation with medical judgement after a version change and document every term or query difference. Keep this boundary visible: Multiaxial retrieval requires an explicit counting rule.
CHAPTER 17 OF 17 · Keep every conclusion reproducible
17. A complete M1 receipt reconstructs language into evidence
The record includes source wording, language, selected LLT and code, hierarchy path, MedDRA release, coding convention, reviewer, query or SMQ version, primary and secondary SOC handling, case de-duplication, result, medical interpretation and uncertainty.
For a complete m1 receipt reconstructs language into evidence, a neat label is valuable only when its medical placement and version are visible. The record includes source wording, language, selected LLT and code, hierarchy path, MedDRA release, coding convention, reviewer, query or SMQ version, primary and secondary SOC handling, case de-duplication, result, medical interpretation and uncertainty. Respect this boundary: A standard term cannot add clinical detail that the reporter did not provide.
Try this
Run a retrieval rehearsal for a complete m1 receipt reconstructs language into evidence. Trace a complete m1 receipt reconstructs language into evidence from verbatim source wording through LLT, PT and the intended medical grouping. Compare a specific and broader grouping, then explain any change in counts. Keep this boundary: A standard term cannot add clinical detail that the reporter did not provide.
A strong science note separates observation from interpretation. Trace a complete m1 receipt reconstructs language into evidence from verbatim source wording through LLT, PT and the intended medical grouping. Record the source, version or date, population or device context, method, result and one uncertainty. If the official record does not show a field, write “not shown” instead of filling the gap from memory.
Evidence checkpoint
Trace a complete m1 receipt reconstructs language into evidence from verbatim source wording through LLT, PT and the intended medical grouping. Keep this boundary visible: A standard term cannot add clinical detail that the reporter did not provide.
M1 terminology evidence map
| Question | Evidence to capture | Boundary to retain |
|---|---|---|
| What was reported? | Verbatim wording and language | Do not infer an unreported diagnosis |
| How was it coded? | LLT, code, PT and hierarchy path | Check the medical placement |
| How was it retrieved? | PT list, grouping level or versioned SMQ | State primary and secondary paths |
| Can it be reproduced? | MedDRA release, convention, review and query | Preserve version history |
Science learning becomes useful when a student can show where a claim came from, why it applies and where it stops. Continue with the eduKate Science Learning Hub, compare choices in the Education Hub, and connect these habits to career pathways built from subject capabilities.
M1 makes medical vocabulary both human and computable. Its optimistic lesson is simple: careful words help people see the same safety pattern sooner, while visible versions and limits keep a convenient label from outrunning the evidence.
Primary sources and verification date
Source status checked 27 October 2026. FDA guidance describes the agency’s current thinking and does not replace applicable statutes, regulations or product-specific communication with FDA.
- ICH: MedDRA — Official purpose, history and regulatory use of MedDRA; checked 27 October 2026.
- MedDRA: Hierarchy — Official explanation of the five hierarchy levels.
- MedDRA: Standardised MedDRA Queries — Official description of SMQs as retrieval tools for safety investigation.
