MEDICAL TRANSLATION INSTRUCTIONS v.

SCOPE

For this project you will have to translate strings related to medical content. They belong to
conversations between multiple speakers in a medical environment (for example, between a
doctor and a patient).

MEDICAL CONCEPTS AND TERMINOLOGY

Conversations will include medical terminology, which in some cases will require to be an
expert of the field. Therefore, translators will be divided into 2 groups:

- Group A: translators without medical experience

- Group B: translators with medical experience

Group A translators will have to skip any content they don’t feel comfortable with (because
it has technical terms, difficult medical concepts, it’s too complex, etc.). If you are in this
group, please make sure you translate only the strings where you are 100% sure that your
translation is correct, accurate, and uses proper medical terminology.

Group B translators will have to translate the strings that have been skipped by the Group A.
For some specific language combinations, you may also be asked by the PMs to judge
between 2 translations and indicate which one is better. If this is needed, you will be notified
and receive specific instructions by the PMs directly.

MACHINE TRANSLATION NOT ALLOWED

No Machine Translation is allowed in the translation. Human translation is always

required. It is strictly forbidden to use Google Machine Translation, Microsoft Machine or
any other MT engine translation. This requirement is essential as we are dealing with
sensitive content that cannot be shared under any circumstance with third parties.

MEANING AND ACCURACY

- Translations should be accurate. This means they have to fluently express the
meaning of the Source in the target language in a manner that a native speaker of the
target language would be likely to express such meaning.

- If a Source String’s meaning is ambiguous, the translation should be based upon the
most common meaning of the word or phrase in context.

1
PacteraEdge Confidential
 - Provide a translation of the source meaning rather than a “word by word” style
translation.

UNITS OF MEASUREMENT

- Don't convert units even if the target language uses different metric systems.

NUMBERS

- Numbers should be formatted so that they are natural and easy to read. Thousand
separators can be modified to fit the target language. For example, four-hundred
million dollars may be translated as "USD 400,000,000" or "4億ドル" depending on
the language.

GRAMMAR, PUNCTUATION AND CAPITALIZATION

- Please provide grammatically correct translations, including punctuation. If applicable

to the language, please include proper uppecase/lowercasing.
- If sentences are grammatically or syntactically wrong in source, fix them in the
translation.

SWEAR WORDS AND ADULT CONTENT

- If source contains swear words, violent/offensive language, adult content, etc. do not
omit them in the translation and look for the corresponding equivalents in the target
language. Original intent and tone should be maintained.
- If you don’t feel comfortable with the content and don’t want to translate it, skip the
hit.

QUERIES

If you have linguistic queries or doubts about the instructions, raise a ticket to our Query
Management System Global Query (C837-Isaac projects). If you do not have an account or
you cannot remember your username, reach out to Lu Zhang (lu.zhang32@pacteraedge.com).
If you don’t remember the password, you can reset it from the login page. If you have queries
about workflow, rates, payments, or want to report a technical bug (not related to linguistic
issues), reach out to the project managers by email: isaac_pm@pacteraedge.com. Do not
raise tickets in Global Query for non-linguistic topics.

2
PacteraEdge Confidential