# Term Mappings and Custom Vocabulary for Interpreters

> How OPI interpreters can use term mappings, custom vocabulary, and important words without overloading the call or trusting automation too much.

Author: Mirkamol
Published: April 24, 2026
Updated: September 7, 2026
Categories: Technology
Canonical page: https://useinterpreter.com/blog/term-mappings-custom-vocabulary-interpreters/
Custom vocabulary sounds like a small feature until you hear a name, medication, or case term get mangled three times in a row.

OPI calls depend on small words with large consequences: "Eliquis," "subrogation," "Medicaid," "arraignment," "aneurysm," "deductible." If a live transcript or speech tool keeps guessing the wrong term, the interpreter has to spend extra attention correcting the screen instead of listening.

Custom vocabulary features differ. Some guide speech recognition, some prefer a target-language equivalent, and some replace text after recognition. Check which behavior your tool actually implements.

For healthcare vocabulary discipline, the [NCIHC standards of practice](https://www.ncihc.org/standards-of-practice) are a useful guardrail.

> A custom term list is useful only when it matches the words your callers actually say.

## What a term mapping does

A translation term pair links a source term with a preferred equivalent. A recognition hint suggests a word the speech engine might hear. Those are related aids, not the same guarantee.

> [!TIP]
> Add terms after real misses, not after abstract study sessions. Your glossary should reflect your calls.


That can mean:

- A medication name and its correct spelling
- A provider name or facility name
- A legal term with an accepted equivalent
- An agency acronym
- A product name that speech recognition keeps misreading
- A phrase that should stay untranslated

In Interpreter, you can load Important Words and term pairs before a session. Other tools may call the same idea a glossary, vocabulary boost, custom dictionary, or forced replacement. Check the documentation: a glossary and a forced replacement can have different effects on the output.

You give the system a short list of terms that matter for this call.

## Keep the list short

Many interpreters overbuild the list. They add every word from a prep document, every possible medication, and every acronym they might hear. An unfocused list is harder for you to verify and test.

For a manageable practice list, start with:

- Names
- Uncommon medication or procedure terms
- Case-specific acronyms
- Brand names
- Terms with known mistranscriptions
- Words with high risk if confused

If you are interpreting a cardiology call, you do not need the whole cardiology textbook. You may need "metoprolol succinate," "atrial fibrillation," "echocardiogram," and the cardiologist's name.

Think of custom vocabulary as a call kit, not a dictionary.

## Use mappings for recognition, not decision-making

A term mapping can improve what appears on screen. It cannot decide what the speaker meant.

If a patient says something that sounds like "insulin," the tool may show "insulin" because you loaded it. That helps only if the speaker said insulin. If the audio was unclear, you still need to ask for repetition.

The interpreter stays responsible for the message. Treat the screen as a support, much like [Quick Lookup](/blog/quick-lookup-for-interpreters/) or notes. Use it to reduce friction, then apply your training.

Medical and legal calls make that responsibility sharper. Similar terms can point to different realities:

| Heard term | Possible confusion |
|---|---|
| ileum | ilium |
| hypertension | hypotension |
| appeal | repeal |
| premium | prepayment |
| discharge | discharge summary, discharge from care, discharge from debt |

Mappings can help the tool prefer the term you expect. They cannot remove the need to clarify.

## Build reusable sets by domain

You do not need to rebuild from scratch before every shift. Create small reusable sets:

**Medical intake:** primary care provider, date of birth, allergies, current medications, pharmacy, pain scale.

**Pharmacy:** refill, prior authorization, dosage, generic, brand name, contraindication, side effect.

**Insurance:** deductible, copay, coinsurance, claim number, member ID, appeal, network.

**Legal:** arraignment, affidavit, deposition, plea, continuance, probation, warrant.

**Utilities:** shutoff notice, account number, past due, payment arrangement, service address.

Each set should stay lean. You can add call-specific terms on top when the portal, patient, or client gives you clues.

For broader prep, use a more permanent glossary system. Our [interpreter glossary bank guide](/blog/interpreter-glossary-bank/) explains how to store terms across months of work without turning your live-call setup into clutter.

## Map both directions when the call is bilingual

OPI does not move in one direction. The provider may speak English. The patient may answer in Spanish, Arabic, Mandarin, or another language. Then the provider may quote the patient's words back.

If your tool supports it, add both directions:

- English source term to target-language equivalent
- Target-language term or spelling variant to English
- Common abbreviation to full term
- Brand and generic names as separate verified entries, without automatically replacing one with the other

Test both directions using invented sentences. Do not assume reversing a pair is always appropriate, or that a preferred equivalent preserves meaning in every context.

Do not invent equivalents. Use accepted professional terminology, your agency guidance, and your own verified glossary.

## Avoid patient-specific data

A custom vocabulary list can create a privacy problem if you fill it with names, dates of birth, claim numbers, addresses, or medical record numbers and then store it after the call.

Use the minimum. If you need a name during the call, remove it afterward unless your agency-approved tool handles session cleanup for you. Do not paste a full referral, chart note, or insurance letter into a vocabulary field unless the tool has approval for that data.

Healthcare interpreters should pair vocabulary tools with privacy habits. Start with [HIPAA for interpreters](/blog/hipaa-for-interpreters/) if your workflow includes patient information.

## Review what the tool got wrong

After a hard call, look at the terms the tool missed or distorted. Add the reusable ones to your glossary. Remove one-off details. If the same term keeps failing, create a mapping before the next related call.

Keep the review focused on recurring, non-sensitive terminology.

Term mappings work best when you treat them as preparation for the next likely mistake. Load the few words that would cost you the most attention if the system missed them. Then let the tool do its job quietly while you do yours.

Keep mappings that help in practice, remove misleading ones, and ask for clarification when the audio remains uncertain.

---

*Related reading:*
- [The Interpreter's Toolkit: What Belongs on Your Screen](/blog/interpreter-tools-guide/)
- [Quick Lookup for Interpreters](/blog/quick-lookup-for-interpreters/)
- [Building an Interpreter Glossary Bank](/blog/interpreter-glossary-bank/)
- [Medical Terminology for Interpreters](/blog/medical-terminology-for-interpreters/)