A contraindication is a clinical situation, condition, or patient characteristic in which a medicine, biologic, or medical device should not be used because the risks clearly outweigh the benefits in that group. In labeling and regulatory documentation, contraindications are usually placed prominently in prescribing information, package inserts, summary-of-product-characteristics documents, and instructions for use to warn prescribers and patients against unsafe use.
Updated
Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.
Check source meaning → confirm the preferred term → record approved variants and references.
Translators encounter contraindications when localizing prescribing information, patient leaflets, and digital health content such as physician portals or e-labeling. Because this section often uses direct commands and prohibitions, the target language must preserve urgency and legal clarity without introducing softer language or conditions that the source text did not state.
A frequent error is rendering an absolute contraindication as a precaution or warning, which lowers the safety barrier and may allow use in a dangerous patient subgroup. Translators may also insert conditions such as 'unless advised by a doctor,' adding an exception that the approved label does not contain and shifting liability.
Chinese document application
Illustrative wording only. Confirm the rendering against the actual source and approved project terminology.
A contraindication, precaution and warning have different functions in an IFU. Retain the source category and do not weaken a prohibition into advice. Chinese punctuation and list structure should keep each condition attached to the action it restricts.
Inspect the Chinese list structure and the source prohibition together. A condition attached to one list item must not appear to restrict every item, or disappear when the layout turns a paragraph into bullets.
Send the complete IFU section and related label wording. Confirm approved patient-group terminology and request owner review of conflicting source categories.
Check intended use, warnings, document versions and approved terminology with the project team. Translation supports documentation; it does not establish product approval or regulatory acceptance.
Provide approved terms and previous translations with the source files. Agree how variants, ambiguous wording and revisions will be reviewed. Terminology maintenance and any termbase handback are confirmed in the project scope. See the 8-step AI + expert workflow.
Medical-device registration files and technical specifications, in volume.
Read the published project →Vaccine-production process documentation, SOPs, quality-control standards and microbiology-testing procedures.
Read the published project →Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.
Include the source and target languages, file types, intended use, deadline and any approved termbase. Agree handling before sending sensitive files. Acknowledged in 4 hours, quoted in 24.
Prepare an inquiry email →Life Science solutions →File handling →A glossary entry is not an official standard or evidence of regulatory acceptance. Confirm current requirements for your project separately.