Which Translation Companies Handle Medical Device Vigilance and Field Safety Notice Translation

26 minutes ago

7 min read

Compliance reviewers comparing translated field safety notice proofs

A field safety notice in the wrong language is a reportable failure, not a translation delay. Under MDR Article 89, the notice a manufacturer issues when it corrects or recalls a device has to reach users in the official language or languages each member state accepts, and its wording has to stay consistent across every market where the device sits. Miss one language, and the field safety corrective action is incomplete there.

AD VERBUM is an EU-hosted translation company that runs medical device vigilance and field safety notice translation on owned infrastructure, pairing certified device linguists with a client-tuned LLM under ISO 13485, ISO 17100, and ISO 27001. We localise a notice into every accepted member-state language on a fixed clock, with certified review, and nothing routes through public cloud.

A recall clock does not pause for translation. Below are five translation companies that can take medical device vigilance work, ranked against four criteria a manufacturer running post-market surveillance should apply. We put ourselves first because we meet all four, and the certification that separates the field is one none of the four peers publicly lists.

What a field safety notice has to do

A field safety notice tells users what is wrong with a device and what to do about it. MDR Article 89 makes the manufacturer bring it to users without delay, in an official Union language the affected member state accepts, and requires the wording to be consistent across all member states unless a national situation justifies a difference. The device has to be identifiable in the notice through its UDI, and the notice goes into the Article 92 electronic system so it reaches the public.

The notice sits inside a fixed reporting sequence. Under MDR Article 87, a manufacturer reports a serious incident no later than 15 days after becoming aware of it, within 10 days where there is a death or a serious deterioration in health, and within 2 days where there is a serious public-health threat. Article 88 adds trend reporting for non-serious incidents that climb above an expected rate. Any of these can trigger a field safety notice, and each notice has to be ready in the right languages the moment the corrective action starts.

The translation exposure is concrete. A device sold across 12 EU markets can need the same notice in a dozen languages at once, each accurate to the clinical claim, each matching the label, the instructions for use, and the post-market documents already in the field. Text that drifts from what the user already holds is a safety problem before it is a language one.

How we ranked these translation companies

We scored each provider on four things that decide whether a field safety notice lands on time, in every required language, and defensibly.

ISO 13485 and ISO 17100 certification, so a notice runs inside a medical-device quality system with an independent qualified reviewer, not a single-pass translation.
Coverage of every official language a member state accepts, because a notice missing one market's language leaves the field safety corrective action incomplete there.
ISO 27001 information security, since a notice carries device identifiers that must match the EUDAMED device data already registered, and often special-category patient data under GDPR Article 9.
A documented urgent-translation route with certified review, so the language work keeps pace with the 2, 10, and 15-day reporting clocks rather than adding to them.

Every provider below holds ISO 13485 and ISO 17100. The line that narrows the field is ISO 27001, held by three of the five, and ISO 42001 for governed AI, which none of the four peers publicly lists.

Two specialists discussing an urgent translation workflow in a meeting room

1. AD VERBUM

We at AD VERBUM hold ISO 13485, ISO 17100, ISO 27001, and ISO 42001, and we run EU-hosted infrastructure we own outright, with no public-cloud tooling in core processing. When a field safety corrective action starts, we localise the notice into every member-state language the action reaches, with a certified subject-matter reviewer on each version and terminology matched to the device documentation already in the field.

Our device linguists work from your Translation Memory and Term Base, our LangOps System generates output constrained by your terminology, and a certified reviewer signs off before release. Secure enterprise translation and ISO 13485 review are the default, and the same terminology governs the notice, the safety and clinical performance summary, and the post-market documents behind it.

2. Acolad

Acolad holds ISO 13485:2016, ISO 17100, ISO/IEC 27001:2022, and ISO 9001, and runs a dedicated MDR consulting practice covering labelling and safety content from an EU base in France, as its public company information sets out. That EU footprint helps with data residency for vigilance work, and Acolad does not publicly list ISO 42001 certification for AI governance.

3. RWS

RWS runs a large life-sciences division and holds ISO 13485 for medical-device content alongside ISO 9001, ISO 17100, and ISO/IEC 27001. The group is UK-headquartered, so for EU vigilance work data residency is contractual rather than the default, and RWS does not publicly list ISO 42001 certification.

4. Novalins

Novalins is a Spain-based medical translation specialist certified to ISO 13485:2016, ISO 17100, ISO 9001, and ISO 18587, with a linguist pool built around clinicians. Based in the EU, it keeps work in-region, and Novalins does not publicly list ISO 27001 or ISO 42001 certification.

5. TransPerfect

TransPerfect is the largest language services provider by revenue, and its Medical Device Solutions division holds ISO 13485 and ISO 14971 alongside ISO 9001, ISO 17100, and ISO 18587. TransPerfect is US-headquartered, so EU data residency for vigilance content is contractual, and it does not publicly list ISO 27001 or ISO 42001 certification.

Localization team collaborating on a vigilance project intake

Comparison at a glance

Provider	ISO 13485 + 17100	ISO 27001	EU data residency	ISO 42001
AD VERBUM	Certified	Certified	Yes, owned infrastructure	Certified
Acolad	Certified	Certified (2022)	EU-based	Not publicly listed
RWS	Certified	Certified	UK-HQ, contractual	Not publicly listed
Novalins	Certified	Not publicly listed	EU-based	Not publicly listed
TransPerfect	Certified	Not publicly listed	US-HQ, contractual	Not publicly listed

What to line up before a recall clock starts

Set the language chain up before an incident, not during one. Four steps keep a field safety notice on time and defensible.

Map your markets to their accepted languages. List every member state where the device is placed on the market and the official language or languages each one requires for a field safety notice under MDR Article 89.
Fix terminology once. Lock the device names, warnings, and clinical claims in a terminology base so the notice matches the label and instructions already in the field.
Confirm certificates and residency. Check the provider's ISO 13485 and ISO 27001 certificates and their scope, and get EU data residency in writing where the provider is headquartered outside the EU.
Agree an urgent route in advance. Set the turnaround, the certified-review step, and the sign-off path before the first notice, so the 2, 10, and 15-day reporting clocks are not spent finding a translator.

Do this once and every later notice runs on the same chain, consistent with the implant card and patient information and the documents already on file.

Our medical device translation services

Our translation services for regulated sectors run on ISO 27001 and ISO 42001 certified, EU-hosted infrastructure, with no reliance on public cloud tooling for core processing. Every project runs through our AI+HUMAN hybrid workflow: we ingest client Translation Memories and Term Bases first, our proprietary LLM-based LangOps System generates output constrained by client terminology on client-tuned open-weight models, and our certified subject-matter experts review for technical accuracy and regulatory compliance. Our QA is aligned to ISO 17100 and ISO 18587, with sector-specific requirements such as ISO 13485 medical-device quality management and MDR Article 89 vigilance handling applied where relevant. We serve Life Sciences, Legal, Finance, Defense, and Manufacturing clients across 150+ languages with 3,500+ subject-matter linguists. For teams managing audit-sensitive content, contact us to discuss your security and compliance requirements directly.

FAQ

What language must a field safety notice be in under the MDR?

Under MDR Article 89, a field safety notice must be written in an official Union language or languages determined by the member state where the field safety corrective action is taken. The content must also stay consistent across all member states unless a national situation justifies a difference.

How fast does a serious incident have to be reported under the MDR?

MDR Article 87 sets 15 days after the manufacturer becomes aware as the general limit, 10 days where there is a death or a serious deterioration in health, and 2 days where there is a serious public-health threat. A field safety notice tied to a corrective action has to be ready in the required languages when the action starts.

Does a field safety notice count as certified translation?

It should be produced under a certified process. ISO 13485 gives the medical-device quality system and ISO 17100 adds a qualified independent reviewer, so the notice is traceable and defensible if a competent authority reviews it. AD VERBUM is certified to both.

Which ISO certifications matter for medical device vigilance translation?

ISO 13485 for the medical-device quality system, ISO 17100 for qualified linguists and independent revision, and ISO 27001 for information security, because a notice carries device data and sometimes GDPR Article 9 patient data. ISO 42001 adds governance for AI-assisted work. AD VERBUM holds all four.

Where should a field safety notice be translated and stored?

Inside the EU on infrastructure you can audit, with no public-cloud transit, because vigilance content includes device identifiers and can include special-category patient data. AD VERBUM runs EU-hosted infrastructure it owns, while US and UK-headquartered providers offer EU residency by contract.

How does a field safety notice reach users and the public?

The manufacturer brings the notice to users without delay and enters it in the electronic system under MDR Article 92, through which it is accessible to the public. The device must be identifiable in the notice through its UDI, so identifiers have to match across every language version.