Medical devices
One IFU, Two Markets: Spanish and Portuguese Cleared on the First Pass
A Minnesota manufacturer of Class II devices needed its IFU, labeling, and validation protocols in Mexican Spanish and Brazilian Portuguese. Both regulatory submissions went through without a translation-related objection.
Mexican Spanish and Brazilian Portuguese ran in parallel, each checked against its own market's labeling rules.
Warnings, contraindications, and reprocessing steps were translated back into English by independent linguists and compared line by line.
Our DTP team returned formatted IFU and labeling files with every ISO 15223-1 symbol left exactly where regulators expect it.
A Minnesota device maker looks south
The client designs and builds Class II medical devices from a facility in Minnesota, selling through distributors across the United States. After signing distribution agreements in Mexico and Brazil, the regulatory affairs team faced a documentation package it could not produce internally: the instructions for use, all product labeling, and two IQ/OQ validation protocols, about 30,000 words in total, needed in Mexican Spanish and Brazilian Portuguese.
The stakes were asymmetric in an uncomfortable way. A weak IFU reads badly to a patient or nurse and generates support calls. A wrong one delays market entry, because ANVISA in Brazil and the Mexican authority both review labeling as part of registration. The client had one launch window with its distributors and no appetite for a second submission round.
They came to us because medical device translation sits inside our core specialty, technical documentation with regulatory consequences, and because they wanted both languages handled by one accountable team rather than two vendors working from the same source in isolation.
The challenge: readable for a patient, exact for a regulator
An IFU serves two audiences at once. The person unpacking the device needs plain, unambiguous instructions. The reviewer at ANVISA needs wording that tracks the applicable RDC resolutions on device labeling, down to required statements and how risk information is presented. Text that satisfies one and fails the other fails, period.
Three constraints shaped the project beyond that tension:
- Brazilian regulatory conformity. ANVISA's RDC requirements for device labeling dictate specific content elements. The Portuguese had to align with the vocabulary used in those resolutions, without drifting into Portuguese from Portugal, which reads noticeably foreign to Brazilian users.
- Symbol control under ISO 15223-1. The labeling relied on standardized symbols for manufacturer, lot, sterility, and storage conditions. Symbols must never be translated, moved, or paired with improvised captions, and every accompanying text had to match the standard's sanctioned wording in each language.
- InDesign source files. The IFU and labels lived in multi-layer InDesign documents. Spanish and Portuguese run 15–25 percent longer than English, so the layout had to absorb expansion without shrinking type below the sizes the client's design controls allowed.
What we did
For Portuguese, we assigned Ana Beatriz Souza, a chemical engineering graduate of UFRJ with 15 years of technical translation into Brazilian Portuguese and long experience working documentation against Brazilian normative requirements. Her engineering background mattered on the IQ/OQ protocols, where installation and operational qualification steps have to read like the validation documents Brazilian engineers already use. The Spanish side went to a two-person medical team, translator and independent reviser, both native speakers working in Mexican Spanish.
The workflow added two safeguards on top of our standard translate-edit-proofread sequence. First, terminology sign-off happened at the front of the project rather than at the end. Ana sent the client's regulatory affairs team a short list of decision points in week one: required statements, symbol captions, the rendering of the intended-use claim. Second, we ran back-translation and validation on the safety-relevant sections: warnings, contraindications, and reprocessing instructions were translated back into English by linguists who had never seen the source, and the client's regulatory team compared the versions before release.
Back-translation is a comparison tool, no more. It does not certify a translation. What it does is expose shifts in meaning that no monolingual review can see, which is exactly what a regulatory affairs manager signing a submission wants on the record for the sections that carry patient risk.
Layout ran in parallel rather than as an afterthought. Our technical desktop publishing team worked directly in the client's InDesign files, managing text expansion, regenerating the tables of symbols, and producing final PDFs for both markets alongside the packaged source files. A final in-layout proofread caught line-break and hyphenation issues that only appear after typesetting.
Key numbers
| Metric | Detail |
|---|---|
| Volume | 30,000 words: IFU, product labeling, 2 IQ/OQ protocols |
| Languages | English to Mexican Spanish (es-MX) and Brazilian Portuguese (pt-BR) |
| Team | Ana Beatriz Souza (pt-BR) plus a two-person es-MX medical pair, with independent back-translators |
| Deliverables | Print-ready InDesign files and PDFs, back-translation reports, bilingual termbase, translation memory |
| Follow-on savings | 30 percent lower translation cost on the next product, through memory reuse |
The result
Both submissions cleared regulatory review on the first pass. Neither ANVISA nor the Mexican reviewer raised a translation-related objection, and the distributors launched inside the planned window. The back-translation reports gave the client documented evidence of translation control to file with the rest of its design records.
The quieter payoff came with the next product. When the client took the following device in the same family to both markets, the translation memory from this project already contained the approved warnings, reprocessing instructions, and labeling boilerplate. Reused segments were billed at match rates instead of full price, and the second product's translation cost came in 30 percent below the first. That is typical of how Brazilian Portuguese technical translation programs behave once a validated memory exists: the first project is the expensive one. If you have an IFU package heading for Latin America, request a quote and we will return an itemized breakdown within one business hour.
Questions about this project
Why run Mexico and Brazil as a single project?
The source content was identical, so both languages shared one kickoff, one symbol review, one query sheet, and one DTP pass. That kept the two versions structurally aligned and saved the client from coordinating two vendors who would each have asked the same questions separately.
What is back-translation and when do you recommend it?
An independent linguist translates the finished text back into English without seeing the original, and the two English versions are compared. Differences flag possible shifts in meaning. We recommend it for warnings, contraindications, and other safety-relevant IFU sections, and wherever a client wants documented translation control in the design history file.
Do you work directly in InDesign?
Yes. We translate from the IDML content of your InDesign files, manage the 15–25 percent text expansion typical of Spanish and Portuguese, keep ISO 15223-1 symbols untouched, and deliver packaged source files plus print-ready PDFs. A proofread happens in the final layout, after typesetting.
How did the second product cost 30 percent less?
The translation memory stored every approved segment from the first project. The next product in the family reused shared warnings, reprocessing instructions, and labeling boilerplate, so those segments were billed at reduced match rates rather than as new translation. The validated termbase also shortened the review cycle.