Life science localization — automated laboratory analyzer with a sample tray
Life Science · 生命科学

Medical device and life science translation.
Clear terminology. Traceable review.

IFU, 510(k) material, CE/MDR technical files, SOPs and clinical protocols — translated against the governing standard, with a documented and traceable process.

Start with your files

Connected files, from IFU to clinical records

Tell us what the documents are for, which source revision to use and who will read the translation.

Device information

IFU (Instructions For Use), labelling and packaging.

Submission and risk files

510(k) material, CE/MDR technical files and risk management files.

Clinical and quality records

Clinical protocols, SOPs and CAPA documentation.

IFU · LAYOUT SCHEMATIC

Document set alignment

ReferenceSourceTranslation
Device nameApproved nameSame reference
Section numberingSource structureMatched
RevisionConfirmed versionLinked record

Warnings, section hierarchy and approved terminology remain easy to cross-check.

Illustrative layout only. No customer content or product values are shown.

Why this is harder than it looks

01

The submitted wording is itself under review

In a regulatory submission the text is not a wrapper around the evidence — it is part of the evidence. Reviewers read what you filed. An ambiguous rendering of an indication, a contraindication or a performance claim becomes a question to answer, and questions cost review cycles.

02

Terms have to match the standard, not just be accurate

Regulated terminology is defined by the governing standard and by your own device labelling. A defensible synonym is still the wrong word if the standard and your label use another. Consistency with the source document set matters as much as linguistic quality.

03

Untraceable output is a compliance problem

A quality system requires a documented process with accountable steps. Text of unclear provenance — including unreviewed machine output — is difficult to defend during an audit, regardless of whether it happens to be correct.

Project context

What governs the work

EU MDR 2017/745

Member states determine the language(s) required for IFU and labelling in their market. Requirements are per-market, not EU-wide.

FDA submissions

Filed in English. Where source documentation, clinical data or QMS records were authored in another language, accurate English rendering is required.

ISO 13485 / ISO 9001:2015

A documented, auditable translation process with defined review steps.

How a life science project runs

01

Prepare the project

  • Client UploadFiles, reference material and any existing termbase
02

Translate and verify

  • AI TranslationDraft generation on a domain-tuned engine
  • Terminology MappingTerms locked against the project termbase
  • Expert ReviewDomain specialist validates accuracy and context
  • QALISA QA 3.1 audit against defined error categories
03

Deliver and retain

  • DeliveryFormat restored, delivered in the original layout
  • Knowledge Asset UpdateTerminology fed back — every project improves the next
Recommended service levelL3 — Angel PremiumRegulatory filings are expert-led and LISA QA 3.1 audited. This content is never delivered as reviewed machine output alone.

Selected work

Life ScienceFDA registration

US market entry for an IVD diagnostics firm

Challenge An in-vitro diagnostics company entering the US market needed its full FDA registration documentation translated to a standard that would withstand regulatory review.

Solution Expert-led translation by reviewers with biomedical background, following a documented and traceable process, accompanied by a written quality-assurance letter.

  • No language-related deficiency in the first review round
  • Written quality-assurance letter provided
  • Clinical-background reviewers throughout
Prepare the discussion

Bring the files. Make the open questions visible.

Medical device documentation for China

Start with the intended use, the document list and source revisions. Record approved Chinese product names and terminology, and list unresolved translation questions separately.

Use the China document preparation tool above to organize this information. For market-specific research, see medical device regulatory research for China →. Research and translation scopes are agreed separately; a document register does not establish regulatory compliance or approval. It is not an FDA or MDR submission template.

For a quote, include the source files, language direction, intended use and required date. Discuss your project →

“Documentation submitted to Europe for review is held to a very high standard. Angel recommended using English as the source language and having native-speaker translators handle it — the result met our expectations, and they were willing to take our experts’ feedback and revise patiently.”
Johnson & JohnsonLife Science

Life Science questions

FDA submissions are made in English. The translation requirement arises when your underlying technical documentation, clinical data, design history or quality records were authored in another language — those need accurate, defensible English rendering. Confirm the specifics of your pathway with your regulatory consultant; requirements differ by device class and submission type.
Under MDR 2017/745, instructions for use and labelling must be provided in the language(s) accepted by each member state where the device is placed on the market, and each member state determines that for its own territory. In practice this means planning for a set of languages defined by your target markets rather than a single EU version. Verify the current list for your markets with your notified body.
Projects are matched to reviewers with relevant domain background rather than distributed to whoever is available. For device documentation that means someone who can judge whether a clinical or technical term is used correctly in context — the judgement a general linguist cannot reliably make.
Send us your approved labelling, previous submissions or existing termbase at kickoff. Those terms are locked before review begins, so the translation aligns with what you have already filed instead of introducing a new vocabulary that a reviewer has to reconcile.
AI is used to generate the draft, never as the deliverable. Every regulatory document goes through domain expert review and a LISA QA 3.1 audit before delivery. The position is deliberate: AI handles speed, experts handle accuracy, and Angel handles accountability for what is delivered.
Under NDA covering everyone in the delivery chain, including reviewers. If your protocol requires specific handling, retention or destruction terms, raise it at kickoff so it is built into the project rather than retrofitted.

Send us a life science document

Acknowledged in 4 hours, quoted in 24. Discuss confidentiality before sharing sensitive files.