Solutions
Medical documents are structured documents before they are text.
Tables of results, dosing information, reference lists, regulatory formatting — the structure is where the information lives. Translating the text and losing the structure loses the information.
What makes these documents hard
Four document-level problems, none of which are about vocabulary.
Tables carrying the data
A results table that breaks across a page or loses its header row is not a cosmetic problem. It is a table that no longer communicates.
Numbers and units
Dosages, measurements and reference values have to survive translation unchanged. A number that changed in processing is the most serious failure in this document class.
Regulatory formatting
Submission documents follow templates. Whether a translated document still satisfies the template is a document-structure question.
Scanned and mixed files
Older records and mixed collections are frequently scans, sometimes interleaved with digital pages in the same file.
The documents we get
The document types that come up most in this category.
Clinical and study documents
Protocols, reports, tables of results — heavily structured, heavily tabulated.
Regulatory submissions
Template-driven documents where the structure is part of the requirement.
Product and labelling documentation
Repetitive across markets, which is exactly where a glossary earns its keep.
Patient-facing material
Leaflets and forms, frequently supplied as PDFs or scans.
Terminology and consistency
Consistency is the requirement; you define it.
We do not supply medical glossaries and we do not provide medical advice. What we do is enforce the term list you provide — TXT, CSV or XLSX, up to 2000 terms — during translation.
Numbers and units are the case we treat most carefully. The pipeline's visual check compares the rendered output against the source, which is how a changed figure or a dropped decimal gets caught before delivery.
We are a document pipeline, not a regulatory affairs function. Validation, sign-off and regulatory acceptability are your reviewers' responsibilities.
How the work runs
Four steps, same pipeline for every industry.
- 01
You send one real document
The awkward one if you have it. It is evaluated on the same path your production work would take.
- 02
We run it end to end
Inspection, per-page routing, translation with your terminology applied, independent review, visual verification.
- 03
You judge the returned file
Layout, terminology, the pages that normally break. That is the evaluation.
- 04
Scope is agreed separately
Volume, language pairs, turnaround and integration. The sample tells you whether to have that conversation at all.
Questions
Are you certified for medical or regulatory work?
Ask us directly and we will tell you exactly where we stand rather than pointing at a badge. What we provide is the document pipeline; validation and sign-off are your reviewers' responsibility.
How are numbers and units protected?
The rendered output is compared against the source before delivery, which is how a changed figure or a dropped decimal is caught. It is the failure mode we treat most seriously in this document class.
Can you enforce our terminology?
Yes — your term list, up to 2000 terms, applied during translation rather than as a correction afterwards.
Do you handle scanned records?
Yes. Pages without a text layer go through optical recognition, and a file that mixes scanned and digital pages is handled page by page.
Do you provide medical translators?
No. We provide the pipeline that produces the translated document. Whether a qualified reviewer signs it off is your process decision.
Send us a document with a results table in it.
If the table survives intact, the rest of the document usually does too — and that is the part worth verifying.
- No signup, no self-service portal — you send a file, we run it.
- You get the finished document back, not a screenshot of one.
- If it is not good enough, you have lost nothing.