Certified Portuguese Medical Translation for an NHS Hospital Submission
The client’s problem Leonardo came to us at one in the morning. That detail matters, because people do not fill in translation forms at one in the morning…
Your device is ready for Great Britain. The technical file is built, the risk file is closed, and then someone in the review meeting asks whether the English manual is actually compliant, or just readable. At Medical Translations UK we prepare medical device manual translation for UKCA marking across GB submissions, and the question that catches manufacturers out is rarely about language quality. It is about evidence.
An Approved Body does not simply read your English instructions for use and decide they sound fine. It looks for a controlled process behind them: who translated the text, who checked it, against which source revision, and how you would prove that if asked two years later during surveillance. This guide sets out what the GB market expects from your translated manuals, and the records that keep them defensible.
Information supplied with a device placed on the GB market must be in English, covering the instructions for use, labelling and packaging text. UKCA marking does not accept “translated” as a tick box — your technical documentation should show a qualified translation process, revision-controlled files, terminology consistent with the labelling, and retained records linking each English version to the source it came from.
Yes. Devices placed on the GB market fall under the Medical Devices Regulations 2002, and the information supplied by the manufacturer must reach the user in English. That covers the instructions for use, the label, packaging text, any on-screen interface strings and safety information.
Two points regularly trip up non-GB manufacturers.
The first is territory. Great Britain and Northern Ireland are not the same regulatory market. Northern Ireland continues to follow EU rules under the Windsor Framework, using CE or UKNI marking, while UKCA applies to England, Scotland and Wales. Manufacturers building a single “UK” documentation pack sometimes discover late that they need two labelling routes.
The second is transitional acceptance of CE marked devices in GB. Those arrangements have shifted more than once and carry end dates set by the MHRA, so confirm the current position for your device class before assuming your existing CE pack carries you through. Our specialists see companies delay English documentation on the strength of an old briefing note, then face a compressed timeline when the date moves closer.
[Image: ukca-device-technical-documentation.jpg — Alt: “Instructions for use, labelling and packaging text prepared in English for a UKCA marked medical device.” Caption: Every item of information supplied with the device must reach the GB user in English.]
| Item | Why it matters for GB | Typical reviewer |
|---|---|---|
| Instructions for use (IFU) | Carries intended purpose, warnings and residual risk information | Approved Body, MHRA, end user |
| Device label and packaging text | Must be legible and complete at point of use | Approved Body, importer, distributor |
| Symbol explanations | Reduces text but must match recognised standards | Approved Body |
| Software and device user interface strings | Use errors trace directly to interface wording | Approved Body, usability assessor |
| Service and maintenance manuals | Supports safe servicing by GB engineers | Manufacturer, service network |
| Patient implant card and information leaflet | Required for applicable implantable devices | Clinician, patient |
| Field safety notices | Must reach GB users in English during a corrective action | MHRA, distributors |
| Declaration of conformity supporting documents | Referenced within the technical file | Approved Body, UK Responsible Person |
Scope changes by device class and by whether the device is professional or lay use, so map your own list against your classification rather than working from a generic set.
Translation sits inside your quality management system, not outside it. Under ISO 13485 it is an outsourced process, which means purchasing controls apply: a documented evaluation of the supplier, defined requirements passed to them, and records demonstrating the work was performed to those requirements. Auditors ask to see that file more often than manufacturers expect.
ISO 17100 matters because it defines what a compliant translation process contains. It sets competence requirements for the linguist and, importantly, requires revision by a second qualified person against the source text. A single translator working alone, however skilled, does not meet that standard. When our in-house specialists deliver device documentation, the reviser is a separate named individual and that is recorded.
The practical benefit is defensibility. If a use error is reported in GB and traced to a warning that reads differently in English, the questions that follow are about process control, not vocabulary.
Findings are rarely about elegant English. They concern consistency and traceability.
A component called a “connector” in the IFU and a “coupling” on the packaging looks like two parts to a GB nurse. Approved Bodies check terminology alignment across the whole information set, so a managed termbase applied to every deliverable prevents a whole category of findings.
Source languages differ in how strongly they phrase caution. A German or Japanese warning rendered into polite, general English can lose its instructional force. Risk-controlling text should carry the same weight it holds in your risk file, because that is what the reviewer compares it against.
Symbols reduce translated text, but only where they are used and explained in line with the harmonised standards your submission cites. Inventing a plain-English gloss for a standard symbol creates a mismatch between the manual and the labelling assessment.
Engineering changes move faster than documentation. A manual translated from revision 4 while the device ships against revision 6 is a live non-conformity, and it is the most common one we are asked to remediate.
If the file cannot name the translator, the reviser and the date, the process cannot be evidenced. Anonymous documentation fails the audit even when the language is correct.
1. Freeze the source before translation begins. Assign a document number and revision to the English-source or original-language master, and release it formally. Translating a working draft guarantees rework and breaks the audit trail before it starts.
2. Send the full information set together. IFU, label text, packaging copy and interface strings should be handled as one package so terminology is decided once. Splitting them across separate requests months apart is how a connector becomes a coupling.
3. Supply your termbase, risk file wording and any predicate manuals. Our medical device linguists work from your approved terminology rather than generic clinical vocabulary, which keeps the English aligned with what your submission already claims.
4. Require named revision as a deliverable, not a courtesy. Ask for the translator and reviser to be recorded against the job, with qualifications retained. That record belongs in your supplier file.
5. Record the source revision on every translated file. The English version should state which source document and revision it derives from, so any later engineering change flags exactly which deliverables need reissuing.
6. Retain the evidence for the documentation retention period applicable to your device. Post-market surveillance and vigilance questions can arrive years after launch, and the ability to produce the translation record quickly shortens every one of those conversations.
Before your submission goes out, confirm you have:
Yes. Self-declaration under UKCA changes the conformity assessment route, not the language obligation. Information supplied with the device must still reach the GB user in English.
Not as a finished deliverable. Unrevised machine output carries no competence record and no named reviser, which leaves the process unevidenced under ISO 13485 purchasing controls even where the English reads acceptably.
Not automatically. Your existing English EU file may be a strong starting point, but GB references, the UK Responsible Person details, symbol usage and any GB-specific labelling must be checked and updated rather than carried across unchanged.
No. Northern Ireland follows EU rules under the Windsor Framework, so its labelling and marking route differs from UKCA. Confirm your NI requirements separately before printing a single pack for both.
The manufacturer holds the obligation, but the UK Responsible Person is expected to hold and provide documentation to the MHRA on request. Both need access to the current English files.
No. Where an eIFU is permitted for your device and user group, the content still has to be in English, and users who request a paper copy must receive one. Confirm eligibility for your classification.
They must reach GB recipients in English and go out quickly, which is why an existing termbase and supplier arrangement matters. Building a translation route during an active corrective action costs time you rarely have.
It is typically raised as a non-conformity requiring correction and evidence of the corrective action, which can hold up certification. Where the device is already on the market, it may trigger a wider review of the information supplied.
Device submissions rely on process evidence rather than the personal certification used for civil documents. A signed statement can be issued, but the records auditors ask for are competence, revision and traceability.
Yes. Lay-user devices require readability appropriate to a non-clinical reader, while professional-use documentation can carry clinical register. The same source text often needs different English depending on the intended user.
Link the translation trigger to your change control process, so any revision affecting supplied information automatically raises a documentation task rather than being noticed at print stage.
The classification and conformity routes differ, but the expectation that information reaches GB users in English applies across both, including assay instructions and result interpretation text.
UKCA submissions rarely fail because someone wrote clumsy English. They fail because nobody can show which source revision the English came from, who checked it, or why the label and the manual describe the same part two different ways. Translation is a controlled process in your quality system, and treating it that way removes an entire class of findings before an assessor ever opens the file.
If you are scoping documentation for a GB launch and want to know exactly which items need English versions and what evidence to retain, send us your document list and our medical device specialists will map it against your classification. Request a compliance scope for your device documentation and we will set out the deliverables, records and revision controls in writing.
Our translation team handles certified translation requests for clients in the UK every day. This guide is built from the questions clients ask us most often.