Medical Device Documentation Translation: How to Organise and Qualify It Inside Your Quality System
How should a medical device manufacturer manage translation of its documentation? Treat medical device documentation translation as a controlled process inside your quality system: qualify the supplier, approve terminology once, translate only what has changed and release every language together with the source. DEMA Solutions supports regulatory and labelling teams with an ISO 17100 certified process and in-house DTP.
Who this guide is for
This guide is written for the people who sign off translated device information and answer for it later. You may be a regulatory affairs manager preparing a submission and a list of target markets. You may work in quality assurance and need to decide what a translation supplier has to show before it goes on your approved supplier list. Or you may run technical documentation or labelling, which means you are the one who receives a revised IFU on Thursday and is asked when all the languages will be ready.
The same questions apply to manufacturers of in vitro diagnostic devices. The guide leaves aside the legal detail of what a label or IFU must contain and concentrates on how to organise the work, so that every language version is consistent, traceable and on time, at launch and at every change after it.
Why translation belongs inside the quality system
A translated label or IFU is not a courtesy copy of the source. For the user in Madrid or Warsaw it is the only version that exists, so its accuracy is part of the device’s safety and performance, and an error in it is a nonconformity like any other. If the Polish instructions give a cleaning temperature that the source never stated, the device on that market is shipped with wrong information, whatever the original says.
The MDR, Regulation (EU) 2017/745, and the IVDR, Regulation (EU) 2017/746, require the information supplied with a device to be in the official Union language or languages determined by each Member State where the device is made available to users or patients, and they attach language rules to other documents, such as field safety notices and the declaration of conformity. What each label and IFU has to contain, and how the national language choices work, is explained in our guide to EU MDR labeling requirements.
Once the translations are seen as part of the device, medical device documentation translation needs what any other process affecting the product needs: a qualified supplier, defined inputs, records, a link to change control and a clear release step.
What a device manufacturer actually translates
The volume rarely comes from a single document. It comes from a family of texts that describe the same device to different readers, at different moments, in different formats, and that all have to say the same thing.
Labels and packaging. Medical device packaging translation is short text under heavy constraints: fixed label areas, several languages on one carton, and a mix of content that must be translated, content that must never change, such as lot numbers, dates and UDI carriers, and content replaced by symbols. The work is closer to typesetting than to prose, and it usually runs through label templates or artwork files rather than word processors.
Instructions for use and eIFU. This is where most words sit. Indications, contraindications, warnings, preparation, cleaning and reprocessing, troubleshooting and technical data are read by surgeons, nurses, biomedical engineers or patients, depending on the device. Medical device manual translation for service and maintenance documentation adds another layer of readers. Where the rules permit electronic instructions, the language versions still have to exist and match the edition in circulation; eIFU changes the delivery channel, not the amount of translation.
Software and user interface strings. Device software, apps and analyser screens show menus, alarms and messages that must use exactly the terms of the IFU. These strings come as resource files with length limits and placeholders, and they are often translated by a different team on a different schedule. Our article on translating HMI and software user interfaces covers the technical side.
Patient-facing material. Implant cards and patient information for implantable devices, where applicable, and instructions for home use are read by people without clinical training. Correct terminology is not enough here; the text has to be understood at the first reading, which is why some manufacturers have patient texts rewritten in plain language before or during translation.
Field safety notices. These arrive without warning and with a short deadline. They have to be consistent across every market where the corrective action applies, and they reuse the wording of the IFU and labels, so they are the clearest test of whether your terminology and memory are in order before a crisis.
Training and sales material. Training decks, brochures, catalogues and websites follow looser rules, but claims about intended purpose and performance must still match the approved documentation. For devices that require one, the summary of safety and clinical performance also belongs in the set, and it is read by a wider public than the IFU.
These documents share a vocabulary and change together, which is why device translation cannot be organised file by file.
Qualifying a medical device documentation translation supplier under your QMS
ISO 13485, the quality management standard most device manufacturers work to, places supplier controls on the manufacturer. Its purchasing requirements ask you to evaluate, select and monitor suppliers according to their ability to provide what you need and according to the effect of their work on the product, and to keep records of that evaluation. A supplier that translates labels and instructions for use clearly affects the product, so it belongs in that process like a sterilisation contractor or a label printer does.
That has a useful consequence: a medical device translation vendor does not need its own ISO 13485 certificate to be qualified. The standard sets out how you, the manufacturer, control your suppliers. What you need from the translation supplier is evidence that its process is defined, carried out by qualified people and documented well enough for you to rely on it and to monitor it over time.
In practice, the evidence worth asking for falls into five areas. The first is a written description of the process: how a request is received, prepared, translated, revised, checked and delivered, and who is responsible at each step. A certification to ISO 17100, the international standard for translation services, gives you an external reference point for that description, because it requires defined translator competences and revision of every translation by a second qualified linguist.
The second area is people. Ask how translators and revisers are selected for medical content, which qualifications and subject experience they need, and whether translators work into their native language. The answer should describe criteria, not names.
The third is confidentiality. Device documentation often contains unreleased designs, clinical data and submission material. Ask how files are exchanged and stored, who has access, and what the supplier’s confidentiality commitments to its linguists look like, then put the terms in your agreement.
The fourth is records. For each project you should be able to see which source version was translated, which languages, who translated and revised, which glossary and memory were applied, and when the work was delivered. These records are what turn a translated file into something you can trace during an internal audit or when an authority asks how a warning was produced.
The fifth is corrections. Ask how a reported error is handled: who assesses it, how the corrected text is fed back into the memory and glossary so it does not return in the next update, and how the change is recorded. Our guide to assessing translation quality before you hire a supplier describes practical ways to test these points, including sample translations.
Once a supplier is approved, monitoring can stay light: review the correction log and delivery against agreed dates in your periodic supplier review.
Change control: translating updates without re-translating everything
Most translation work on a marketed device is not new text. It is a revised warning, a new indication, a reworded cleaning step or a software release that renames two menu items, and it should run through change control just as the source does.
Start with the source. A clean revised IFU forces the supplier to work out what changed, which adds time and risk. A change-marked source, or the change list from your change request, tells everyone involved exactly which sentences are in scope and lets reviewers concentrate on them.
A translation memory does the rest of the work. Because every approved sentence from earlier editions is stored with its translation, unchanged content is recognised and carried forward with the wording you already released, and only the new and modified sentences are translated and revised. Text that did not change in the source should not change in the translations either. The way a memory accumulates value across editions is described in our article on translation memory as a strategic asset.
The harder problem is alignment between documents. A change that touches the IFU often touches the label, the software and sometimes the training material, and each has its own owner and release path. Keep a simple cross-reference: for each change, which documents and which languages are affected, and which revision of each will be released. When the IFU moves to a new revision identifier, every language version should move with it, on the same date.
UDI-related updates are a good example of changes that look small but reach many files. A new device identifier or packaging configuration can mean new label artwork in every language, even when the translatable text barely changes. Treating these as label updates in their own right, with layout checks in each language, avoids surprises at the printer.
Finally, agree release timing in advance: whether all languages are released together or some markets may follow. A single release date for all affected languages is easier to defend and to audit.
Terminology and symbols
Consistent terminology is the cheapest safety measure in device documentation. A single approved glossary should cover the IFU, the labels, the software and the technical documentation, so that a component, an alarm or a procedure step has one name per language everywhere it appears. When the screen says one thing and the instructions another, the user hesitates, and hesitation during a procedure is exactly what the documentation is meant to prevent.
The glossary works best when your own experts approve it once: regulatory and clinical staff for indications and warnings, engineers for components and settings, and in-country reviewers for the terms users actually recognise. It should also record forbidden alternatives. Our guide to keeping terminology consistent across translators and suppliers explains how to build and maintain one.
Harmonised symbols help. Using the symbols in EN ISO 15223-1 reduces the amount of text on labels, which saves space and translation on small packaging. They do not remove the need for consistent terminology, though. The meaning of each symbol is usually explained in the instructions, warnings and handling conditions still need words, and the same terms appear again in the software and the IFU. Symbols reduce the volume; the glossary keeps what remains consistent.
Back translation and linguistic validation: when they add value
Back translation means translating the target text back into the source language, independently, so that someone who does not read the target language can compare meanings. Linguistic validation is a broader process, typically used for patient-reported questionnaires and similar instruments, in which translations are reconciled, back-translated and tested with people from the target population to check that they are understood as intended.
Both have a place in device documentation, but a limited one. They are most useful for patient-facing and usability-critical text, where the question is not only whether the translation is correct but whether a lay user will understand and act on it in the right way. They are also worth doing when a regulator, a notified body or a commercial partner explicitly asks for them, in which case the request itself defines the scope.
They are not a routine substitute for qualified revision. A back translation can look fine while the target text uses a term that users in that market do not recognise, and it can flag differences that are only stylistic. For most labels and IFU, a qualified translator, a second qualified reviser and an approved glossary give stronger assurance, with the extra steps reserved for texts where user understanding is the real risk.
Machine translation in regulated content
Machine translation is acceptable in device documentation only with full human post-editing and revision by qualified linguists. Inside that controlled process, with your approved glossary and memory steering the engine, it can speed up large, repetitive material such as service documentation.
The risks concentrate in exactly the places that matter most. Engines can drop a negation and turn a contraindication into an indication, soften a warning, swap units, move a decimal separator or reorder values in a table of settings, temperatures or concentrations. These errors read fluently. Warnings, contraindications and any text carrying numerical values that resemble dosages or settings deserve a full, line-by-line comparison against the source, whoever or whatever produced the first draft.
If you allow machine translation for some content types, write the rule down in your procedure: which documents, which level of post-editing and which revision step. Our overview of machine translation post-editing and where it stands today explains the levels of post-editing and where each one fits.
Planning around launches and submissions
Translation delays at launch almost never come from translation itself. They come from decisions taken late. The first is the language list. For each target market, record which languages the national rules require for labels, instructions and patient information, check the choice with your distributor or local partners and freeze it before translation starts. Adding a language after the label artwork is final is one of the most expensive changes you can make.
The second is the review cycle. Notified body review can lead to changes in the source documentation, and each round may reopen text that has already been translated. Where possible, translate after the source has passed the review steps most likely to change it, and plan a short update round for late findings rather than translating everything twice.
The third is layout. Labels, cartons and IFU leaflets need desktop publishing in every language, and text expansion is a real constraint on small labels. Build DTP lead time into the plan, including the check of every language proof before printing. Our article on how multilingual desktop publishing improves document translations shows what that work involves.
The real bottleneck, though, is late change to the source. A warning reworded two days before release must pass through translation, revision, layout and approval in every language, so an agreed source freeze date protects the launch more than any acceleration on the translation side.
Questions to ask before you choose a partner
When you compare medical device translation services, start by asking the supplier to walk you through a recent update for a regulated document: how the changed text was identified, how unchanged content was protected and how the languages were released together. Then ask what records they keep for each project and in what form you can receive them for your supplier file.
Next, ask how they select and keep translators and revisers for medical content, and how a correction you report is reflected in the memory and glossary so it does not return. Ask who owns the translation memory and the glossary, and in which formats they are delivered, so your approved wording stays available whatever happens to the relationship. Finally, ask how they handle labels and IFU layout, and whether that work is done in-house or passed to a third party. Our guide to choosing a technical translation company adds further questions for a structured comparison.
How DEMA Solutions works with medical device manufacturers
We support labelling, regulatory and documentation teams across the full set of device information, and our page on translation for labels, IFU and device documentation shows the document types we cover. Every project follows our ISO 17100 certified process: linguists with medical subject experience translate, and a second qualified linguist revises the work before it reaches you. Our workflow is documented, and each project leaves a record of what was translated, revised and delivered, and when, which you can use in your own supplier monitoring.
Your approved terminology lives in a controlled glossary, and your memories and glossaries are delivered to you in TMX and TBX on request. Our in-house DTP team lays out labels, cartons and IFU in the original files, so language versions come back ready for proof approval rather than as text to be placed by someone else. Confidentiality applies to every file and every linguist who works on it. Behind this are our teams in Italy, Serbia and Spain.
Day to day, you have one commercial contact, your sales manager, working closely with a dedicated project manager on your account. Requests can come by email, through a dedicated SharePoint space or through our client portal, where you describe each job, add notes on specific requirements, flag a field safety notice or other urgent request for priority delivery, and follow status and updated timelines. If you want to see the process before committing, you can submit test requests without commissioning a translation, and we offer training by video call or in person for your team.
Where TUBE fits
For device manufacturers whose labels and IFU are revised with every design change, new indication or market extension, TUBE is the solution that keeps each revision anchored to wording you have already approved. Your glossary and translation memory control machine translation, so a reworded warning or a new label variant starts from your terminology rather than from a generic engine. Every approved translation goes into a memory that belongs to you and that you can export at any time. And leverage reporting shows, for each update, how much of the text was reused and how much was new, which is useful evidence when you plan the next change.
Frequently asked questions
As a controlled process within the quality system. Qualify the translation supplier, approve one glossary for labels, IFU and software, send change-marked source files, reuse approved translations through a memory, release all affected languages with the source revision and keep records of each project.
Generally no. ISO 13485 places supplier controls on the device manufacturer, which evaluates, selects and monitors suppliers whose work affects the product under its own quality management system. A translation supplier can be qualified on evidence such as a documented process, translator and reviser qualifications, confidentiality arrangements and project records.
A description of the translation process, the criteria used to select translators and revisers, confidentiality terms, the records kept for each project and the procedure for handling and recording corrections. A certification to ISO 17100 provides an external reference for the process.
Send a change-marked source or a list of changes, and work with a translation memory that holds the approved translations of earlier editions. Unchanged sentences are reused as released, and only new or modified text is translated and revised.
Not as a general rule. Back translation and linguistic validation are useful for patient-facing and usability-critical texts, or when a regulator or partner asks for them. For most labels and IFU, qualified translation with revision by a second linguist and an approved glossary gives stronger assurance.
Only with full human post-editing and revision by qualified linguists. Warnings, contraindications and texts containing values such as settings or concentrations need careful comparison against the source, because machine errors in these places can read fluently.
No. Symbols from EN ISO 15223-1 reduce the text on labels, but warnings and handling conditions still need words, and the symbols are usually explained in the instructions, which must be translated consistently with the label.
Send one IFU or label set and your list of markets
The quickest way to see how this would fit your quality system is to try it on real material. Send us one IFU or label set and the list of target markets, along with any earlier translations or glossary you already have, and we will show you what can be reused, how we would handle terminology and layout, and which records you would receive for your supplier file.
How can we help?
Tell us what you need and we’ll get back to you with the solutions.