How to Keep Medical Translation Terminology Consistent: A Terminology Management and QA Guide

Terminology inconsistencies often appear when medical content moves across documents, teams, and versions. The same drug may be referenced in clinical trial protocols, investigator brochures, pharmacovigilance materials, regulatory submissions, and product information. Drug names, active ingredients, clinical endpoints, diseases, and dosage information may therefore appear repeatedly across a project.

A practical terminology workflow starts before translation. Teams can identify reliable terminology sources, confirm project-specific terms, use approved translations during production, and run targeted QA checks before delivery. This reduces the amount of terminology cleanup required at the end of a project.

Where should medical terminology come from?

Different types of medical terms have different reference sources. The WHO International Nonproprietary Names (INN) system provides globally recognized names for active pharmaceutical substances. MedDRA provides standardized medical terminology for regulatory information related to human medical products. For European product information, EMA QRD templates and their language versions provide another relevant reference, while ICH guidelines define many concepts used in drug safety.

The appropriate source depends on the content. Active ingredients and generic drug names may be checked against WHO INN. Regulatory terminology for adverse events, symptoms, and diseases may require MedDRA. Drug-safety definitions may refer to the ICH E2 guidelines. Company-specific drug codes, targets, platform names, and internal product terminology should follow terminology already approved for the project.

When multiple sources use different wording, the project team should confirm the applicable standard and version before large-scale translation begins.

What should a medical termbase contain?

A two-column source-and-target glossary works for basic lookup, but it becomes harder to manage once terminology changes across projects and versions. Medical terminology often requires additional information about domain, abbreviation, source, approval status, and deprecated wording.

Useful fields may include Source Term, Approved Translation, Deprecated / Forbidden Term, Definition, Domain, Abbreviation, Source, Status, Version, and Note. A term with a high risk of ambiguity can include its approved translation, definition, applicable domain, and source. An outdated translation can remain in the termbase with a deprecated status so that QA checks can still detect it.

Not every general word requires a detailed terminology record. Drug names, regulatory terms, high-frequency specialist expressions, and easily confused concepts deserve more complete entries.

Why are Serious and Severe easy to confuse?

Serious and severe are a well-known example in drug-safety content. ICH E2A distinguishes the two concepts. Severe describes the intensity of an event, such as mild, moderate, or severe. Serious is determined according to criteria such as death, a life-threatening event, hospitalization, or persistent or significant disability.

An event can therefore be severe in intensity without meeting the criteria for a serious adverse event. A serious event may also occur without representing the highest level of symptom intensity. Treating both words simply as variants of “serious” in general English can introduce a conceptual error into the translation.

ICH E2A also distinguishes an adverse event (AE) from an adverse drug reaction (ADR). An AE may be an unfavorable sign, symptom, or disease that occurs after use of a medicinal product without requiring an established causal relationship. In the relevant clinical context, an ADR involves at least a reasonable possibility of a causal relationship between the medicinal product and the event.

Terms of this type can be flagged in advance as potentially confusing concepts. Their definitions, approved translations, and usage conditions can then be reviewed directly during translation and editing.

Where does terminology management fit into the workflow?

Before translation starts, teams can extract drug names, diseases, symptoms, adverse events, clinical endpoints, routes of administration, dosage forms, specifications, test parameters, abbreviations, and company-specific names. These terms can then be compared with existing termbases, approved historical documents, and required external sources.

Approved terminology should be available during translation rather than introduced only during final editing. After translation, QA can check terminology variants, outdated wording, abbreviations, and newly introduced specialist terms. Approved additions and changes can then be added back to the termbase for future projects.

The review should also cover titles, tables, figure captions, headers, footers, and copied content from previous document versions, where outdated terminology can remain unnoticed.

What should terminology QA check?

A terminology QA pass can detect cases where one source term has several translations, an approved term has been replaced with an unapproved variant, or a deprecated term has reappeared. It can also check abbreviation–full form pairs, potentially confused concepts such as serious and severe, and company-specific drug codes or product names.

Numbers, dosages, units, percentages, and decimal values fall under broader translation QA, but they deserve specific attention in medical documents. Linguistic and subject-matter review can focus on meaning, context, and language quality, while rule-based QA handles issues that can be checked systematically across a document or file set.

Managing medical terminology with LanTMS

As the number of projects and files grows, separate terminology spreadsheets become harder to search and maintain. LanTMS supports centralized management of translation projects, translation memories, termbases, and other language assets, allowing approved terminology to remain available for later projects.

A medical translation workflow can follow four practical stages: confirm terminology before translation, use approved terms during translation, run terminology QA after translation, and update the termbase with approved changes. Reusing confirmed terminology in later projects reduces repeated terminology decisions and limits variation between translators, files, and document versions.