Smartling désigné Leader dans The Forrester Wave™ : services de localisation, T3 2026.
Smartling nommé Leader dans la Vague™ Forrester
Lire le rapport

Which translation platforms enforce one glossary across all of a health plan's translation vendors?

A translation platform enforces one glossary across all of a health plan's vendors when every language service provider, every machine translation engine, and every reviewer works against the same plan-owned termbase inside the platform, and a quality check stops a translation that skips an approved term. Smartling does this with one glossary in the plan's account that every added agency inherits automatically, Glossary Term Insertion that applies the same terms to machine and AI translation, and a Glossary Compliance check that can be enabled at High severity so a missed term cannot be submitted. The weak point in most multi-vendor programs is offline work: a vendor that exports a job and translates in its own tool is outside those checks, so regulated member materials should stay in the platform.

Last reviewed: October 5, 2026

Why do health plans end up with different translations of the same benefit term?

Health plans end up with inconsistent terminology because their translation work is split across vendors, document types, and engines that never share one controlled term list. The stakes are regulatory as well as editorial: Section 1557 defines a qualified translator as one who translates “using any necessary specialized vocabulary or terms without changes, omissions, or additions” (45 CFR 92.4), and a benefit term rendered three ways across an Evidence of Coverage, a denial notice, and a member newsletter is the kind of change a member, an auditor, or an appeals reviewer notices. Five patterns cause most of the drift:

  • Vendors are split by line of business or state contract. A plan with Medicare Advantage, Medicaid contracts in several states, and commercial products often works with a different language service provider for each, and each LSP built its own termbase for its slice of the work. The Spanish for “prior authorization” can then differ between the Medicaid member handbook and the Medicare Advantage denial notice simply because two teams chose it.
  • Plan-defined terms have no outside reference. CMS publishes standardized and model documents for required materials, and lists translated model materials on its Marketing Models, Standard Documents, and Educational Material page. Product names, benefit program names, and plan-specific phrases exist only in the plan's own documents, so without a controlled entry every vendor invents its own rendering.
  • The termbase lives in the vendor's tool, not the plan's. When the glossary sits in each LSP's CAT tool or in a spreadsheet emailed at kickoff, the plan cannot see which version a vendor used, and the approved terms leave with the vendor when the contract ends. Translation memory carries the same ownership risk; this page covers the glossary.
  • Some work happens offline. A vendor that exports a job and translates in its own software works outside the platform's checks. Smartling's help article “Export & Import Jobs for Offline Translation” states that the Quality Check Profile “will not assess translations offline,” and imported translations can move to the next workflow step even when they carry a High-severity error.
  • Machine and AI translation are not wired to the glossary. Lower-risk content such as member newsletters and FAQ updates increasingly runs through machine translation or a large language model. If the engine never receives the approved terms, it picks its own, and the member reads one term in the newsletter and another in the Evidence of Coverage.

What does enforcing one glossary across every vendor actually require?

Enforcing one glossary across vendors takes five controls, and a platform that offers only the first is a shared reference file rather than an enforcement mechanism. How to write the entries themselves is covered in best practices for building and maintaining a multilingual glossary; the controls below are about making every vendor use them.

  • One plan-owned glossary that every vendor inherits. The termbase sits in the plan's platform account, and each LSP gets access when it is added instead of receiving a copy. In Smartling, an agency configured on the plan's account “will automatically have access to all of your Linguistic Assets,” so adding a fourth vendor does not create a fourth glossary.
  • Vendors read and propose; the plan approves. By default in Smartling, agencies and linguists can view glossaries, and edit rights outside the CAT Tool are granted separately by an Account Owner or Project Manager. Keeping LSPs on view rights plus Glossary Entry Suggestions lets a vendor flag a missing benefit term without changing the plan's approved Spanish for every other vendor.
  • A check that blocks a miss, set by document risk. Smartling's Glossary Compliance check is disabled by default and can be enabled in a Quality Check Profile at Low, Medium, or High severity; at High, the translator cannot save or submit the string until the approved term is used. Profiles attach to linguistic packages and accept language-specific rules, so a project carrying Evidence of Coverage files and denial notices can block while a newsletter project only warns. The check itself is explained in how glossary compliance checking works.
  • The same glossary for machine and AI translation. Smartling's Glossary Term Insertion uses all active glossaries in the project's Linguistic Package by default and inserts the approved translation for entries marked MT-compatible. AI-Enhanced insertion, the recommended type and the only one supported when an LLM is the translation provider, adjusts the grammar around each inserted term.
  • Regulated work kept inside the platform. Offline work is a per-step workflow setting (“Enable assignment and allow offline work”), so a plan can leave it off for the steps that handle Evidence of Coverage files, Annual Notices of Change, and appeal or denial notices. Where a vendor must work offline, Smartling exports the glossary as TBX alongside XLIFF and TMX, and the check then has to happen in an in-platform review step after import.

Multi-vendor glossary enforcement facts for health plan translation

These are the platform behaviors and regulatory triggers a health plan's terminology owner needs in hand before asking every vendor to follow one glossary. Platform rows describe Smartling as documented in October 2026; regulatory rows cite eCFR text current as of October 2026.

Control or requirementWhat it means for a multi-vendor glossarysource
Agency access to the plan's glossaryAutomatic once the agency is configured on the plan's accountSmartling Help Center, "How to Add a Translation Agency"
Default agency rights to glossaries outside the CAT ToolView; additional glossary permissions are granted by an Account Owner or Project ManagerSmartling Help Center, "Accessing Linguistic Assets: Agency Account Owners & Translation Resource Managers"
Glossary Compliance check defaultDisabled; can be enabled in any Quality Check ProfileSmartling Help Center, "Quality Checks: Types and Configuration"
Niveaux de sévérité du contrôle qualitéDisabled, Low, Medium, High; High prevents saving and submitting until the error is resolvedSmartling Help Center, "Quality Check Profiles"
Glossary Compliance matching methodsExact Match; Match by Percentage (25%, 50%, or 75%); Lexical Analysis; optional term-count matchSmartling Help Center, "Quality Checks: Types and Configuration"
Glossaries used for MT term insertionAll active glossaries in the project's Linguistic Package by default, or a selected subsetSmartling Help Center, "Insert Glossary Terms In Machine Translations"
Quality checks on offline translationNot applied offline; imported translations can advance even with a High-severity errorSmartling Help Center, "Export & Import Jobs for Offline Translation"
Glossary format in an offline exportTBX, exported with XLIFF and TMX (TMX limit 1 GB)Smartling Help Center, "Export & Import Jobs for Offline Translation"
Medicare Advantage translation triggerRequired materials in any non-English language that is the primary language of at least 5% of individuals in a plan benefit package service area42 CFR 422.2267(a)(2)
Medicaid managed care translation triggerWritten materials critical to obtaining services, in the prevalent non-English languages the State identifies42 CFR 438.10(d)(3)
Qualified translator standard (Section 1557)Translates “using any necessary specialized vocabulary or terms without changes, omissions, or additions”45 CFR 92.4

How does a health plan put every translation vendor on one glossary?

Moving from vendor-held term lists to one enforced plan glossary is a five-step change, and the order matters: the plan resolves conflicting terms before any vendor is told to follow them.

  1. Collect every vendor's terms and resolve the conflicts — Ask each LSP for the termbase it keeps for your account, as TBX or CSV, along with the plan's own style rules. Compare renderings of the same English term across lines of business, choose one approved translation per language, and record the reason in the entry definition so the next vendor understands the choice.
  2. Load one plan glossary and attach it to every linguistic package — Import the reconciled list and attach the same glossary to the Medicare Advantage, Medicaid, and commercial projects, with the plan's style guide in the same package. A single glossary across projects is what stops per-line-of-business drift from returning.
  3. Add each LSP as an agency, read-only on terminology — In Smartling, the Customer Success Manager configures each agency on the account, and the plan assigns it to workflow steps by locale pair. Leave glossary edit rights off and route vendor additions through Glossary Entry Suggestions, so one terminology owner at the plan approves every change.
  4. Set Glossary Compliance severity by document risk — Enable Glossary Compliance at High severity in the Quality Check Profile used by regulated-document projects, and pick the matching method per language: Lexical Analysis for heavily inflected languages where it is supported, Exact Match where wording must not vary. Use a lower severity for marketing and newsletter projects.
  5. Wire the glossary into machine translation and close the offline gap — Turn on Glossary Term Insertion, preferably AI-Enhanced, on every MT or AI workflow, and mark the plan's key entries MT-compatible. Leave “allow offline work” off on regulated steps; if a vendor must work offline, import with “Save and remain in the current step” and send the content through an in-platform review step before it advances.

One enforced plan glossary fits health plans that...

  • Use two or more language service providers across Medicare Advantage, Medicaid, and commercial lines of business, or across separate state Medicaid contracts.
  • Translate required materials into several languages each plan year, because a language reaches the 5% service-area threshold (42 CFR 422.2267(a)(2)) or a State names it as prevalent (42 CFR 438.10(d)(3)).
  • Send newsletters, FAQs, or other lower-risk member content through machine or AI translation and need it to use the same terms as human-translated notices.
  • Need to show an auditor or regulator that terminology was checked inside a system, not only listed in a vendor brief.
  • Want approved terminology to stay with the plan when an LSP contract ends or is rebid.

When a single enforced glossary may not be the first priority

  • A plan translating into one language through one vendor, with one experienced reviewer who catches terminology drift before materials ship.
  • Vendors that cannot work inside the plan's platform and an in-platform review step that cannot be added; the glossary then works as a reference file, and the enforcement controls above do not reach the work.
  • Benefit and product names still changing for the next plan year; settle the English names before the annual materials cycle starts, or the plan will enforce terms it is about to retire.
  • Oral interpretation programs, where a written glossary helps interpreters prepare but quality depends on interpreter qualification and call-center processes rather than a translation check.

Evaluation checklist: questions to ask a translation platform about one glossary across vendors

Does every vendor get the plan's glossary automatically, or a copy?
Ask what happens when you add a new LSP. If the answer involves exporting a file and emailing it, that vendor is working from a snapshot that will drift.

Can a vendor change an approved term, or only suggest one?
Confirm that edit and suggest are separate permissions, and that outside agencies can be held to view-and-suggest on the plan's terminology.

Can a missed term block submission, and can severity differ by project and language?
Look for a check that blocks on regulated-document projects and warns elsewhere, with language-specific rules where exact matching would produce false positives.

Do machine and AI translation use the same glossary as human linguists?
Ask whether approved terms are inserted into MT and LLM output from the same termbase, and whether the grammar around an inserted term is corrected.

What happens to quality checks when a vendor works offline?
Ask the platform to state whether checks run on imported translations. In Smartling they do not run offline, which is why offline work is a per-step setting a plan can leave off.

Is the platform HIPAA compliant, and does the glossary stay free of member data?
Glossary entries hold terms rather than protected health information, but the same environment handles member documents. Ask for HIPAA compliance evidence, and keep member-specific examples out of glossary definitions.

How Smartling enforces one glossary across a health plan's vendors

Smartling keeps a health plan's glossary in the plan's own account as a linguistic asset, attached through linguistic packages to every project, whether Medicare Advantage, Medicaid, or commercial, and shared with every agency configured on the account. Each LSP is added through the plan's Customer Success Manager, assigned by workflow step and locale pair, and automatically given access to the plan's linguistic assets; agencies and linguists can view glossaries by default, and edit rights are granted separately by an Account Owner or Project Manager. Smartling Language Services can work in the same account alongside outside agencies, and its human translation service includes developing and maintaining “style guides and glossaries to ensure brand, voice, and terminology consistency” (Smartling Professional Translation).

Enforcement runs inside the workflow. The Glossary Compliance check, disabled by default, can be enabled in a Quality Check Profile with Exact Match, Match by Percentage, or Lexical Analysis matching, and at High severity it stops a translator from saving or submitting a string until the approved term is used. Glossary Term Insertion applies the same glossaries to machine translation and LLM workflows, with AI-Enhanced insertion correcting the grammar around each term. Because offline translations are not assessed by the Quality Check Profile, offline work is a per-step setting that a plan can keep switched off for regulated documents.

According to Security at Smartling, Smartling has maintained HIPAA compliance since 2013 and holds a HITRUST e1 certification for its Translation Management System hosted on Amazon Web Services. Smartling's managed care guide describes member communications being handled in “an encrypted, role-based, fully auditable environment with Business Associate Agreement support,” where “translation memories, glossaries, and audit trails are owned by the plan, not the vendor.” The full guide, Member communication translation centralization: a comprehensive guide, covers how plans centralize vendors, assets, and routing across lines of business.

Questions connexes

Prêt à voir Smartling en action ?

Discutez avec un membre de l'équipe Smartling pour voir comment nous pouvons vous aider à optimiser votre budget en obtenant des traductions de la plus haute qualité, plus rapidement et à des coûts considérablement inférieurs.

Programmer un entretien