How do you translate ISO 13485 medical-device quality records accurately when a wrong serial number, changed acceptance criterion or imprecise complaint status could affect a regulated device? This guide explains how to translate medical-device design controls, supplier records, manufacturing instructions, traceability logs, nonconformity reports, service records and post-market complaints across languages. It is written for technical translators, device manufacturers, auditors, regulatory teams and quality managers preparing documentation for international use.
If you are searching for how to translate an ISO 13485 quality manual, a medical-device design change request, a batch history record, a device complaint or an authorised technical label, begin with evidence rather than a bilingual word list. The translated record must describe the same device version, intended use, risk control, test method, decision status and responsible person as the approved source. A fluent statement that changes any of these can be worse than a clearly flagged translation question.
ISO 13485:2016 is the current published third edition of the international quality management system requirements standard for medical devices and regulatory purposes; ISO’s catalogue records a 2025 review confirmation. It describes a QMS framework, not a product authorisation or a guarantee of clinical safety. This independent article uses constructed examples and does not reproduce protected standard clauses. Local medical-device regulation, manufacturer-approved specifications and qualified professional review control real-world decisions.
What a correct medical-device translation must preserve
Treat a regulated technical record as a chain: one source version describes a defined device, a specified process or observation, a named decision maker and supporting evidence. Translators preserve that chain so the destination user can trace how the decision was reached. Do not manufacture a conclusion because it reads more elegantly than a cautious original. Do not treat a manufacturer’s controlled label as optional copywriting. Product identifiers, limitations, approvals and clinical safety-related language require particularly careful expert review.
The ISO management-system context helps organise a documentation workflow, but it cannot decide a jurisdiction’s medical-device registration status. Regulatory requirements, product claims and safety notices must be checked against the appropriate authorities and the manufacturer’s approved technical documentation. The scenarios below demonstrate translation choices rather than offering instructions to operate or treat patients with any actual device.
1. What an ISO 13485 quality management system is
A medical-device quality management system connects controlled procedures, responsibilities, product requirements, manufacturing, monitoring and documented evidence. It must not be translated as a promise that every product is approved in every destination market.
Working situation. A factory quality manual explains its procedures for manufacturing one category of devices. A distributor translation says the manual itself authorises the sale of every product globally.
Translation decision. Keep process conformity, product conformity and regulatory clearance as separate claims. Identify the entity and facility covered by the source document.
Reviewer test. Ask what actual evidence supports each public claim: quality-system certificate, product approval, test report or internal procedure. They are not interchangeable.
A useful way to review this record is to ask what a manufacturer, supplier, auditor or device user would do differently if the sentence were mistranslated. That action is the unit of meaning that must survive. Where the wording could support two operational interpretations, the authorised owner must resolve the ambiguity instead of leaving translation software to choose.
2. Regulatory requirements differ by market
A manufacturer’s documentation may address requirements from multiple jurisdictions. A word such as registration, listing, approval or clearance can have specific meanings that are not identical.
Working situation. A device registered in one country is described as ‘approved worldwide’ after a translator selects a familiar local term.
Translation decision. Keep the named market, authority, product identifier and status. Do not change a jurisdiction-specific procedural outcome into a universal sales permission.
Reviewer test. Have a regulatory affairs reviewer identify the actual competent authority and operative decision for every translated claim.
The documentary state matters. A proposal, approved instruction, measured test result, preliminary assessment and final release decision are not synonyms. Record which one the source describes. A fluent sentence that silently promotes a preliminary statement into final approval can alter the production and release chain.
3. Intended use and intended purpose
A device’s intended use influences classification, labelling, design validation and risk assessment. Translators cannot silently broaden what the manufacturer says a device is for.
Working situation. A monitoring accessory approved for one patient population is translated as suitable for all patients, removing a specified clinical limitation.
Translation decision. Preserve clinical indication, user group, use environment and manufacturer wording. Raise ambiguity with the authorised document owner.
Reviewer test. Ask whether a clinician reading only the translation would select the device for a use outside the documented scope.
Numbers and identifiers must remain stable through every format conversion. Review decimals, tolerances, temperatures, symbols, units, batch codes and part numbers as data, not decoration. When a software tool strips a leading zero or replaces a symbol, quality assurance should treat that as a potentially material content change.
4. Indications, contraindications and warnings
Instructions for use distinguish when a device is intended to help, when it should not be used and what risks require attention. The difference between a limitation and a warning may matter.
Working situation. A source warns against use in a defined condition; the target translation weakens it to a suggestion that additional care may sometimes be useful.
Translation decision. Maintain the warning’s conditional structure and level of obligation. Follow the manufacturer’s approved target-language labelling process.
Reviewer test. Have a qualified device specialist compare the decision a user would take from each version, not merely whether the terms look equivalent.
Test meaning using the actual workflow. A specialist who sees only the target-language record should identify the same device configuration, required process, acceptance condition and approving role. Back translation alone does not establish that an operator will select the correct part or perform the correct check.
5. Device model, variant and catalogue number
Product families may have similar names but different technical characteristics, sizes, sterilisation status or accessories. A translator should preserve identifiers rather than normalise them for style.
Working situation. A multilingual packing instruction drops the variant suffix from an implant kit code and matches the instruction to another model.
Translation decision. Lock product codes, configuration keys and approved names against the device master record. Avoid inventing translated part numbers.
Reviewer test. Try to locate the exact item from the translated record alone; it should resolve to a single approved configuration.
Responsible translation distinguishes the limits of evidence. A sample test, a design requirement, a quality-system certification and a regulatory authorisation may all appear in one document pack, but they answer different questions. Preserve attribution and scope so that the target reader knows exactly what the record proves and what remains unassessed.
6. Document control and revision status
Engineering documents pass through draft, review, approval, obsolescence and revision. Translating the correct words from an obsolete version can still make an unsafe document.
Working situation. A supplier translates revision B while production has moved to revision D. The content sounds correct but the dimensions and inspection sequence differ.
Translation decision. Record the source revision, effective date, approving owner and intended language variant. Flag superseded material visibly.
Reviewer test. Ask the production team to identify which revision is valid at the work station and how they would detect a withdrawn translation.
A useful way to review this record is to ask what a manufacturer, supplier, auditor or device user would do differently if the sentence were mistranslated. That action is the unit of meaning that must survive. Where the wording could support two operational interpretations, the authorised owner must resolve the ambiguity instead of leaving translation software to choose.
7. Design inputs and user needs
Design inputs express requirements derived from use, user needs and applicable obligations. They are not the same as brainstorming ideas or final test results.
Working situation. A requirement says a battery alarm must be audible under a specified condition. Its translation describes the alarm merely as a preferred feature.
Translation decision. Keep measurable requirements, conditions and acceptance thresholds. Preserve must/shall versus should/may as the authorised source uses them.
Reviewer test. Ask an engineer to derive the same design verification test from the translated statement as from the source.
The documentary state matters. A proposal, approved instruction, measured test result, preliminary assessment and final release decision are not synonyms. Record which one the source describes. A fluent sentence that silently promotes a preliminary statement into final approval can alter the production and release chain.
8. Design outputs and product specifications
Design outputs include specifications and other information necessary to realise the device. A translated design output must point to the same configuration and manufacturing constraints.
Working situation. A released drawing calls for a particular seal material; translation uses a broad material-family name that admits incompatible substitutes.
Translation decision. Preserve controlled material grades, dimensions, tolerances, reference drawings and acceptance methods.
Reviewer test. Ask the receiving supplier which material they would purchase and test whether it is exactly the material approved.
Numbers and identifiers must remain stable through every format conversion. Review decimals, tolerances, temperatures, symbols, units, batch codes and part numbers as data, not decoration. When a software tool strips a leading zero or replaces a symbol, quality assurance should treat that as a potentially material content change.
9. Design verification versus design validation
Verification checks whether specified requirements are met; validation addresses whether the resulting device meets intended use and user needs in relevant conditions. They are related but not synonymous.
Working situation. A design team verifies a component’s electrical tolerance. A report translation claims that clinical usability for the entire device has been validated.
Translation decision. Translate the specific question being answered, test setup and scope. Retain verification and validation as distinct record types.
Reviewer test. Ask which claim the evidence actually supports and whether the translated summary has expanded that claim.
Test meaning using the actual workflow. A specialist who sees only the target-language record should identify the same device configuration, required process, acceptance condition and approving role. Back translation alone does not establish that an operator will select the correct part or perform the correct check.
10. Design review and approval gates
A design review meeting can identify actions, raise concerns or recommend approval. It does not necessarily mean a change is formally authorised for production.
Working situation. A reviewer signs meeting minutes asking for more testing, but a translated cover note says the design change has been approved.
Translation decision. Preserve review outcomes, unresolved items and subsequent approval authority. Use separate labels for recommendation and release.
Reviewer test. Reconstruct the approval chain from the translated file and confirm that no unapproved decision appears complete.
Responsible translation distinguishes the limits of evidence. A sample test, a design requirement, a quality-system certification and a regulatory authorisation may all appear in one document pack, but they answer different questions. Preserve attribution and scope so that the target reader knows exactly what the record proves and what remains unassessed.
11. Design transfer and production readiness
Design transfer connects approved design specifications with manufacturing instructions, equipment, training and controls. Translation must preserve readiness conditions instead of implying transfer automatically succeeded.
Working situation. A pilot build shows a tooling issue. A multilingual handover says routine manufacturing may start because the design files were sent to the factory.
Translation decision. Distinguish document delivery, pilot assessment, process readiness, training and formal production authorisation.
Reviewer test. Ask the plant owner which signed record permits routine manufacturing and whether the target text identifies it.
A useful way to review this record is to ask what a manufacturer, supplier, auditor or device user would do differently if the sentence were mistranslated. That action is the unit of meaning that must survive. Where the wording could support two operational interpretations, the authorised owner must resolve the ambiguity instead of leaving translation software to choose.
12. Design changes and engineering change orders
A change may affect drawings, risk controls, suppliers, process settings, labelling or fielded devices. A translated change summary must not hide dependencies or substitute a proposal for a released revision.
Working situation. A proposed adhesive change is described as fully implemented before biocompatibility review and controlled tests have finished.
Translation decision. Keep reason, affected items, evaluation state, implementation date and approval status. Identify any related risk and regulatory review.
Reviewer test. Have cross-functional owners list which documents need updating from the translation and compare with the actual change-control impact analysis.
The documentary state matters. A proposal, approved instruction, measured test result, preliminary assessment and final release decision are not synonyms. Record which one the source describes. A fluent sentence that silently promotes a preliminary statement into final approval can alter the production and release chain.
13. Risk management and residual risk
Device risk work may identify hazards, hazardous situations, probability assumptions, severity and risk-control measures. The word ‘safe’ must not erase residual uncertainty.
Working situation. A report concludes that identified risk controls reduced a specific risk, but the translation states the device has zero risk.
Translation decision. Use proportionate terms that match the risk evaluation and evidence. Keep residual risks and user information in the correct sections.
Reviewer test. Ask a risk specialist what risk remains after the controls and whether the translated sentence leaves the same answer.
Numbers and identifiers must remain stable through every format conversion. Review decimals, tolerances, temperatures, symbols, units, batch codes and part numbers as data, not decoration. When a software tool strips a leading zero or replaces a symbol, quality assurance should treat that as a potentially material content change.
14. Software version and configuration
Device software can affect clinical function, cybersecurity and compatibility. A translated bug-fix notice should not promise a corrected behaviour in every deployed version.
Working situation. A repair bulletin applies to firmware 2.4.1, while the translated notice omits the version and tells all customers the defect is resolved.
Translation decision. Keep product, firmware, build and compatibility identifiers unchanged. Explain where the fix is available and whether installation is required.
Reviewer test. Test a sample device inventory against the target bulletin to confirm the affected population is selected correctly.
Test meaning using the actual workflow. A specialist who sees only the target-language record should identify the same device configuration, required process, acceptance condition and approving role. Back translation alone does not establish that an operator will select the correct part or perform the correct check.
15. Supplier qualification and audit outcomes
Supplier selection, approval, monitoring and corrective actions are not equivalent statuses. A passing questionnaire cannot automatically stand in for a qualified critical supplier.
Working situation. A packaging supplier submits a corrective-action plan after audit; translation lists the supplier as fully requalified without the required evidence.
Translation decision. Name the assessment method, approval state, scope and remaining restrictions. Avoid upgrading a plan to a completed finding.
Reviewer test. Compare the translated supplier list to the approved supplier register and follow-up evidence.
Responsible translation distinguishes the limits of evidence. A sample test, a design requirement, a quality-system certification and a regulatory authorisation may all appear in one document pack, but they answer different questions. Preserve attribution and scope so that the target reader knows exactly what the record proves and what remains unassessed.
16. Purchasing specifications and incoming acceptance
Purchase orders may reference specific grades, certificates, tests, drawings and handling requirements. Small terminological changes can lead to material substitution.
Working situation. A purchase specification calls for a sterilisation-compatible polymer grade; the translation only says ‘medical quality plastic’.
Translation decision. Retain exact grade, revision, acceptance standard and supplier documentation. Do not replace a controlled technical descriptor with marketing language.
Reviewer test. Ask purchasing and incoming inspection to identify the same material and verify the same properties from the translation.
A useful way to review this record is to ask what a manufacturer, supplier, auditor or device user would do differently if the sentence were mistranslated. That action is the unit of meaning that must survive. Where the wording could support two operational interpretations, the authorised owner must resolve the ambiguity instead of leaving translation software to choose.
17. Production work instructions and sequence
Controlled manufacturing instructions describe not just which operation occurs but also its order, conditions, tools and points requiring independent confirmation.
Working situation. A bonding procedure requires surface cleaning before adhesive application, but its target-language layout moves cleaning after assembly.
Translation decision. Maintain step order, prerequisites, safety notes and sign-off points. Test layout and numbering as well as translated prose.
Reviewer test. Observe a qualified operator walking through the target-language instruction in a controlled training environment.
The documentary state matters. A proposal, approved instruction, measured test result, preliminary assessment and final release decision are not synonyms. Record which one the source describes. A fluent sentence that silently promotes a preliminary statement into final approval can alter the production and release chain.
18. Process validation and process verification
Some manufacturing processes require validation where results cannot be fully verified by later inspection. Translators should not make a successful sample inspection sound like full process validation.
Working situation. An adhesive curing process has not completed its validation study. The target report calls three visual inspections a validated manufacturing process.
Translation decision. State the studied process parameters, report status, acceptance criteria and authorisation separately.
Reviewer test. Ask the process engineer which evidence demonstrates that the controlled process consistently achieves its intended result.
Numbers and identifiers must remain stable through every format conversion. Review decimals, tolerances, temperatures, symbols, units, batch codes and part numbers as data, not decoration. When a software tool strips a leading zero or replaces a symbol, quality assurance should treat that as a potentially material content change.
19. Sterilisation status and release criteria
Sterilised, sterile barrier intact, released for use and awaiting test results are different states. Translating one into another can create dangerous instructions.
Working situation. A batch has finished a sterilisation cycle but awaits approved release review. A translated dispatch record lists it as released and ready for patient use.
Translation decision. Retain validated process references, batch status and independent release requirements. Never imply sterility or release from a partial observation.
Reviewer test. Have the authorised release function confirm the exact evidence necessary to place the batch on the market.
Test meaning using the actual workflow. A specialist who sees only the target-language record should identify the same device configuration, required process, acceptance condition and approving role. Back translation alone does not establish that an operator will select the correct part or perform the correct check.
20. Cleanliness and contamination controls
Device cleanliness instructions can specify particulate, microbial or chemical controls depending on use. Generic adjectives such as ‘clean’ are insufficient to preserve a quantitative requirement.
Working situation. A medical tubing work instruction has a defined particulate check. The translation reduces the criterion to ‘looks clean to the operator’.
Translation decision. Translate the actual test method and acceptance limit with units and sampling conditions. Refer to the validated process.
Reviewer test. Ask inspection staff whether the translated requirement leads them to the same measured acceptance decision.
Responsible translation distinguishes the limits of evidence. A sample test, a design requirement, a quality-system certification and a regulatory authorisation may all appear in one document pack, but they answer different questions. Preserve attribution and scope so that the target reader knows exactly what the record proves and what remains unassessed.
21. Environmental and storage conditions
Temperature, humidity, light exposure and permitted transport excursions may change product properties. A translation should not localise numbers as though they were cosmetic.
Working situation. An adhesive component must be stored within a specified Celsius range; the target label changes the number while converting the unit incorrectly.
Translation decision. Verify values, units, allowable excursions and duration. Use a documented conversion only when necessary and keep the controlling specification.
Reviewer test. Calculate a sample storage event using the translated numbers to see whether a borderline shipment is accepted or rejected as intended.
A useful way to review this record is to ask what a manufacturer, supplier, auditor or device user would do differently if the sentence were mistranslated. That action is the unit of meaning that must survive. Where the wording could support two operational interpretations, the authorised owner must resolve the ambiguity instead of leaving translation software to choose.
22. Device history records and batch genealogy
Batch history documents connect materials, operators, equipment, checks, release decisions and dates. Translation should preserve unique identifiers and cross-references.
Working situation. A rework record identifies one lot, but a translated spreadsheet strips leading zeros and links the note to another production batch.
Translation decision. Lock lot, batch and serial identifiers as text where appropriate. Do not auto-format numbers or translate machine-readable codes.
Reviewer test. Trace a sample finished device backward to its components and release records using only the translated report.
The documentary state matters. A proposal, approved instruction, measured test result, preliminary assessment and final release decision are not synonyms. Record which one the source describes. A fluent sentence that silently promotes a preliminary statement into final approval can alter the production and release chain.
23. Traceability for implantable and high-risk devices
Traceability depth and record obligations can vary by product and jurisdiction. A translated record must not invent that every device has the same traceability requirements.
Working situation. A service distributor copies a generic device log into an implantable-device record and omits the patient linkage required by its approved workflow.
Translation decision. Follow the actual product classification, identifier system and authorised record structure. Preserve protected information handling.
Reviewer test. Have quality and regulatory specialists validate whether the translated fields support the required traceability operation.
Numbers and identifiers must remain stable through every format conversion. Review decimals, tolerances, temperatures, symbols, units, batch codes and part numbers as data, not decoration. When a software tool strips a leading zero or replaces a symbol, quality assurance should treat that as a potentially material content change.
24. Unique device identifiers and label codes
A UDI, production identifier and catalogue code have different functions. Translators should preserve scan data and ensure human-readable descriptions do not conflict with identifiers.
Working situation. An implant box has a correct machine-readable UDI but the translated adjacent label names another size variant.
Translation decision. Do not alter the code; compare its associated model, lot and date fields with approved master data and translations.
Reviewer test. Use a scanner test alongside visual label review. A correct barcode does not excuse a misleading human-readable description.
Test meaning using the actual workflow. A specialist who sees only the target-language record should identify the same device configuration, required process, acceptance condition and approving role. Back translation alone does not establish that an operator will select the correct part or perform the correct check.
25. Nonconformity and product disposition
Nonconforming material may be held, reworked, rejected or released under a controlled decision where permitted. A detected issue is not automatically resolved.
Working situation. An inspection report places a lot on hold pending evaluation. The translated warehouse system labels it accepted because a corrective action was opened.
Translation decision. Keep observation, segregation, disposition, approval and release as distinct states. Translate limits on use clearly.
Reviewer test. Ask a warehouse user whether the target text authorises shipment. If it does when the source prohibits it, stop release.
Responsible translation distinguishes the limits of evidence. A sample test, a design requirement, a quality-system certification and a regulatory authorisation may all appear in one document pack, but they answer different questions. Preserve attribution and scope so that the target reader knows exactly what the record proves and what remains unassessed.
26. Rework and repair boundaries
Rework to approved specification and repair that restores usability under specific arrangements can have different implications. A vague translation can conceal an unapproved deviation.
Working situation. An assembly is approved for a defined rework step; the target instruction permits any substitute repair method chosen by the technician.
Translation decision. Preserve the approved method, affected units, reinspection and required review. Escalate unfamiliar process terms rather than generalise them.
Reviewer test. Give the translation to a manufacturing engineer and ask which controlled work instruction they would execute.
A useful way to review this record is to ask what a manufacturer, supplier, auditor or device user would do differently if the sentence were mistranslated. That action is the unit of meaning that must survive. Where the wording could support two operational interpretations, the authorised owner must resolve the ambiguity instead of leaving translation software to choose.
27. Corrective and preventive action records
An investigation, containment step, proposed corrective action, verified implementation and effectiveness review are successive events, not synonyms.
Working situation. A recurring connector defect triggers a new CAPA. The translation reports the problem permanently solved when only temporary containment was completed.
Translation decision. Keep root-cause hypotheses, action owner, due date, verification and effectiveness evidence separate. Avoid unsupported claims of permanent elimination.
Reviewer test. Ask whether the translated timeline identifies the next evidence needed and the person authorised to close the action.
The documentary state matters. A proposal, approved instruction, measured test result, preliminary assessment and final release decision are not synonyms. Record which one the source describes. A fluent sentence that silently promotes a preliminary statement into final approval can alter the production and release chain.
28. Customer complaints and reportability
A customer complaint, confirmed device malfunction, adverse event allegation and regulatory-reportable event require different evaluations. Translators must not assign an official legal conclusion.
Working situation. A customer reports an intermittent alarm. The target intake form declares a proven injury and says the authority has been notified, neither of which is established.
Translation decision. Preserve reported words, allegation status, device identification, assessment stage and jurisdiction-specific reporting determination.
Reviewer test. Have complaint handling and vigilance specialists compare the target-language form with the actual investigation and reporting record.
Numbers and identifiers must remain stable through every format conversion. Review decimals, tolerances, temperatures, symbols, units, batch codes and part numbers as data, not decoration. When a software tool strips a leading zero or replaces a symbol, quality assurance should treat that as a potentially material content change.
29. Field safety notices and recalls
A corrective field action can affect defined models, lots, users and countries. Translation errors may exclude affected users or instruct unaffected users to act.
Working situation. A recall notice covers a particular batch range; the target version reverses the range endpoint and gives customers an inaccurate selection rule.
Translation decision. Control identifiers, action verbs, deadlines, response channels and validated user instructions. Use authorised local regulatory language.
Reviewer test. Run a sample inventory against the translated notice and check that affected and unaffected devices are classified correctly.
Test meaning using the actual workflow. A specialist who sees only the target-language record should identify the same device configuration, required process, acceptance condition and approving role. Back translation alone does not establish that an operator will select the correct part or perform the correct check.
30. Service records and calibration status
A serviced device may still require function checks, calibration verification or authorised return-to-use approval. Translation must not collapse maintenance into clearance.
Working situation. A hospital unit is repaired and awaiting a safety test. The translated repair sheet says ‘ready for clinical use’ after the mechanical fix alone.
Translation decision. Preserve equipment status, tests performed, outstanding checks and signatory authority. Match these against the service procedure.
Reviewer test. Ask the responsible technician which record allows release back to a clinical environment.
Responsible translation distinguishes the limits of evidence. A sample test, a design requirement, a quality-system certification and a regulatory authorisation may all appear in one document pack, but they answer different questions. Preserve attribution and scope so that the target reader knows exactly what the record proves and what remains unassessed.
31. Training and competency records
Training attendance does not always prove competence on a high-risk operation. A translated competency matrix should distinguish instruction, supervised practice and qualified authorisation.
Working situation. An employee signs into a sterilisation course but has not passed the practical assessment. The translation grants them independent operator status.
Translation decision. Keep training content, assessment method, restrictions, qualified assessor and expiry of authorisation as applicable.
Reviewer test. Have supervisors interpret the translated matrix and identify who may perform a task without supervision.
A useful way to review this record is to ask what a manufacturer, supplier, auditor or device user would do differently if the sentence were mistranslated. That action is the unit of meaning that must survive. Where the wording could support two operational interpretations, the authorised owner must resolve the ambiguity instead of leaving translation software to choose.
32. Distribution, transport and cold chain
Distribution documentation links storage and transit conditions with chain-of-custody and excursion decisions. Temperature alarms require assessment, not automatic acceptance or rejection by wording alone.
Working situation. A shipment has a temperature excursion pending manufacturer disposition. Translation calls it ‘stable’ and clears it for immediate distribution.
Translation decision. Preserve logger timestamps, temperature units, assessment status and disposition authority. Avoid reassuring adjectives not supported by review.
Reviewer test. Ask logistics and quality specialists to make the same hold-or-release decision from the translated report.
The documentary state matters. A proposal, approved instruction, measured test result, preliminary assessment and final release decision are not synonyms. Record which one the source describes. A fluent sentence that silently promotes a preliminary statement into final approval can alter the production and release chain.
33. Evidence from testing and statistical samples
Sample tests produce results within specified methods and assumptions. A translation must not imply that an observed sample proves every unit will perform identically.
Working situation. A strength test passes on the specified samples. A brochure translation promises that every manufactured device has been individually strength-tested.
Translation decision. Name sample size, method, acceptance criteria, population and testing date. Separate lot release from universal empirical claims.
Reviewer test. Have a statistician or quality engineer identify the actual inference the evidence supports.
Numbers and identifiers must remain stable through every format conversion. Review decimals, tolerances, temperatures, symbols, units, batch codes and part numbers as data, not decoration. When a software tool strips a leading zero or replaces a symbol, quality assurance should treat that as a potentially material content change.
34. Declaration of conformity and certificate scope
A declaration may be issued by a manufacturer under applicable rules, while independent certificates may cover a QMS or particular products. They are distinct forms of evidence.
Working situation. A company translates its supplier’s QMS certificate as a universal regulator’s approval of a medical implant.
Translation decision. Keep issuer, covered scope, dates and supporting scheme. Do not imply government approval solely from a quality certificate.
Reviewer test. Ask a target-market regulatory reviewer what the document actually authorises and whether the translation exaggerates it.
Test meaning using the actual workflow. A specialist who sees only the target-language record should identify the same device configuration, required process, acceptance condition and approving role. Back translation alone does not establish that an operator will select the correct part or perform the correct check.
35. Claims about biocompatibility and clinical performance
Device materials and designs may require different evaluations. Translators must not substitute a partial material test for a completed device-level clinical conclusion.
Working situation. A component passes an irritation test under specified conditions. Translation states the whole finished device has complete long-term clinical safety evidence.
Translation decision. Preserve test conditions, assessed endpoint, source report and remaining evaluations. Keep market claims inside the approved labelling package.
Reviewer test. Have the qualified reviewer compare the claim with the exact report, including negative findings and limitations.
Responsible translation distinguishes the limits of evidence. A sample test, a design requirement, a quality-system certification and a regulatory authorisation may all appear in one document pack, but they answer different questions. Preserve attribution and scope so that the target reader knows exactly what the record proves and what remains unassessed.
36. Translation in production software interfaces
Quality-critical software strings include alerts, status, units and confirmation buttons. Context and screen size can change how a translated instruction is understood.
Working situation. A device service application has ‘hold’ and ‘release’ controls, but the localisation uses one target word for both functions.
Translation decision. Test the translated interface in its actual state transitions; avoid approving isolated strings without screenshots or interaction context.
Reviewer test. Run a non-clinical simulated workflow and verify that every action matches the source intent before deployment.
A useful way to review this record is to ask what a manufacturer, supplier, auditor or device user would do differently if the sentence were mistranslated. That action is the unit of meaning that must survive. Where the wording could support two operational interpretations, the authorised owner must resolve the ambiguity instead of leaving translation software to choose.
37. Post-market trends and uncertain findings
Post-market surveillance may track early signals, complaints, trends and confirmed corrective actions. A signal is not automatically evidence of a defect or harmlessness.
Working situation. A trend analysis notes a possible rise in complaints. The translated report states that a product defect is conclusively established.
Translation decision. Preserve statistical uncertainty, observation periods, case definitions and investigation status. Avoid both alarmism and unwarranted reassurance.
Reviewer test. Ask a surveillance reviewer what remains hypothetical and what has actually been confirmed at the report date.
The documentary state matters. A proposal, approved instruction, measured test result, preliminary assessment and final release decision are not synonyms. Record which one the source describes. A fluent sentence that silently promotes a preliminary statement into final approval can alter the production and release chain.
Practical release workflow: from source document to controlled translation
Release stage 1: Select the controlled source
Record the device model, intended market, product status, language, document owner, revision and the exact file approved for translation. Resolve conflicts between older drawings, labelling files and manufacturing instructions before translating.
The purpose of this step is to produce a verifiable decision trail. A second reviewer should be able to identify the approved source, compare the target action with the manufacturer’s actual process and find the person authorised to resolve any open question.
Release stage 2: Identify decision-critical content
Highlight part numbers, serial ranges, warning statements, test limits, process settings, regulatory statuses and responsibility assignments. These require field-by-field review and often specialist sign-off.
The purpose of this step is to produce a verifiable decision trail. A second reviewer should be able to identify the approved source, compare the target action with the manufacturer’s actual process and find the person authorised to resolve any open question.
Release stage 3: Establish a terminology and style register
Define verification, validation, rework, repair, complaint, incident, CAPA, release, traceability and related specialised words with manufacturer-approved usage and context examples.
The purpose of this step is to produce a verifiable decision trail. A second reviewer should be able to identify the approved source, compare the target action with the manufacturer’s actual process and find the person authorised to resolve any open question.
Release stage 4: Preserve data and layout
Lock identifiers, decimal precision and regulated symbols. Rebuild tables so headers, units, rows and footnotes stay associated. Inspect page breaks and right-to-left rendering where relevant.
The purpose of this step is to produce a verifiable decision trail. A second reviewer should be able to identify the approved source, compare the target action with the manufacturer’s actual process and find the person authorised to resolve any open question.
Release stage 5: Involve qualified domain reviewers
Use engineering, quality, clinical and regulatory expertise according to content risk. The translator checks language; the authorised owner confirms what the device and documentation mean.
The purpose of this step is to produce a verifiable decision trail. A second reviewer should be able to identify the approved source, compare the target action with the manufacturer’s actual process and find the person authorised to resolve any open question.
Release stage 6: Test realistic readers and tasks
Use a controlled simulation: identify an affected lot, follow a non-clinical manufacturing or support record, or distinguish a complaint allegation from a confirmed finding. Stop if any decision differs from the approved source.
The purpose of this step is to produce a verifiable decision trail. A second reviewer should be able to identify the approved source, compare the target action with the manufacturer’s actual process and find the person authorised to resolve any open question.
Release stage 7: Approve and release the right version
Keep a traceable review record, approval signature, effective date and distribution list. Withdraw or clearly supersede older language versions when design changes require retranslation.
The purpose of this step is to produce a verifiable decision trail. A second reviewer should be able to identify the approved source, compare the target action with the manufacturer’s actual process and find the person authorised to resolve any open question.
Release stage 8: Monitor changes after publication
Connect new product revisions, field actions, supplier changes and regulatory decisions to the translation inventory. Update the exact affected sections instead of silently broadening claims.
The purpose of this step is to produce a verifiable decision trail. A second reviewer should be able to identify the approved source, compare the target action with the manufacturer’s actual process and find the person authorised to resolve any open question.
Worked example: a complaint, a hold and a design change are different records
Imagine a fictional manufacturer of a reusable patient-monitoring accessory. A distributor reports intermittent connector failures in units from a specified lot. The complaint team opens an investigation; quality management places remaining units from the lot on hold. An engineer proposes a material change, and laboratory testing begins on trial samples. The manufacturer has not yet confirmed the root cause, approved the change or authorised return of held stock to market.
If the translation says ‘connector defect confirmed and permanently repaired’, it makes at least three unsupported changes: a hypothesis becomes a finding, a design proposal becomes an implemented fix, and an uncompleted evaluation becomes a final outcome. The accurate record separates the distributor’s allegation, containment action, ongoing investigation, proposed change, test status and future authorisation. A reviewer should trace each to a dated record. This is the difference between a helpful specialist translation and a dangerous fictional assurance.
Frequently asked questions
Is ISO 13485:2016 still current?
Yes. ISO’s catalogue lists the 2016 third edition as published and notes its 2025 review confirmation. Verify official updates when beginning a regulated project.
Is ISO 13485 certification the same as approval of a medical device?
No. A quality management system certificate does not automatically establish product-specific regulatory authorisation or clinical suitability for every market.
Why are translation errors in device records significant?
They can alter model identification, required checks, warnings, release decisions, traceability and users’ understanding of product limitations.
What is the difference between verification and validation?
Verification addresses whether defined requirements are met. Validation addresses suitability for intended use under relevant conditions. The exact procedures and evidence depend on the device.
Can automatic translation be used for manufacturing instructions?
It may support a controlled draft, but consequential terms, technical data, layout and workflow must be reviewed and approved by qualified experts before actual use.
Should a translator change technical units to local conventions?
Only under an approved, verified conversion process that preserves the intended numerical requirement. Keep original identifiers and tolerances correctly linked.
How do I translate an unresolved complaint?
Retain the allegation, investigation status, evidence and decision owner. Do not convert an unverified observation into a confirmed defect or cleared safety finding.
Who approves safety-related labels?
The appropriate authorised manufacturer and relevant regulatory, quality or clinical specialists under the applicable controlled process.
Does this guide replace device instructions or regulatory rules?
No. It teaches safe documentation and language distinctions. Use the actual approved instructions, standards and applicable market requirements for real devices.
Primary reference and existing learning connections
Official source: ISO 13485:2016 — Medical devices, quality management systems, requirements for regulatory purposes (published March 2016; ISO catalogue confirmed following 2025 review; checked 3 November 2026). These examples and explanations are original educational material, not a translation of copyrighted standard clauses.
For the full meaning-transfer framework see the existing eduKate translation master. To develop controlled terminology and conceptual distinctions, consult the Vocabulary Learning Hub and How English Works: Translation and Meaning Across Languages. This specialist medical-device-record guide links into those established owners and does not compete with them.