Excel Translation in Medical Compliance: Engineering Practices and Pitfalls

Why Medical Excel Translations Fail Audits

Last year, an IVD manufacturer received an observation during an FDA pre-approval inspection. The issue wasn't clinical data—it was an Excel device list submitted to reviewers. In one cell, "温度传感器" was translated as "temperature sensor," but elsewhere in the same file, it appeared as "thermal sensor." The reviewer questioned terminology control. This is not an isolated case. Excel file translation in the medical sector is rarely about language alone.

Hidden Traps in Spreadsheet Translation: Formulas, Formatting, and Data Validation

Most translation vendors handle XLSX files by extracting text, translating, and re-inserting. But medical spreadsheets often contain:

• Cross-sheet formulas (e.g., VLOOKUP referencing another workbook)
• Protected worksheets and locked cells
• Data validation dropdown lists (e.g., "Yes/No" requiring translation)
• Text strings in conditional formatting rules

Directly overwriting cells can break formulas and invalidate data validation. More insidious: some cell text is used as named ranges or chart titles, and links are lost after translation.

Engineering Checklist:

1. Use CAT tools with native XLSX support (e.g., Trados, memoQ) instead of converting to CSV first.
2. Lock formulas and referenced ranges before extraction, exposing only translatable text.
3. Build a separate termbase for data validation lists to ensure consistent option translation.
4. Run a formula audit script after re-insertion to check for #REF! errors.

Terminology Consistency: From Termbase to Cell-Level Validation

Terminology in medical spreadsheets must align with IFUs, labels, and risk management files. A common failure: in the same Excel file, "不良事件" is translated as "adverse event" in the header but "adverse incident" in data rows. This violates EU MDR 2017/745 Annex I, Section 23 on terminology consistency.

Our approach: before translation, extract key terms from the client's existing termbase and controlled vocabulary, import them into the CAT tool, and set enforced matching. After re-insertion, run a QA tool (e.g., Xbench) for terminology consistency checks, flagging all mismatched cells.

Data Integrity: Audit Trails and Version Control

21 CFR Part 11 requirements for electronic records apply to the translation process as well. If the translated Excel file is used for regulatory submission, an audit trail must be preserved: who changed which cell and when.

We recommend in the translation workflow:

• Retain the original file hash.
• Use a version-controlled translation memory.
• Deliver a change log documenting all text modifications.

Case Study: Translating a Clinical Trial Data Table

A CRO needed to translate a 3,000-row Excel subject data table into Chinese for an NMPA submission. The table included date formats, units (mg/dL), and free-text comments. We took these steps:

• Extracted the comment column as a separate sdlxliff file for translation, keeping other columns locked.
• Localized units (e.g., mg/dL unchanged, but "mg" to "毫克" with caution—clinical data often retains original units).
• Converted date formats from MM/DD/YYYY to YYYY-MM-DD to avoid ambiguity.
• After re-insertion, used a macro to compare numeric columns between original and translated files, ensuring no changes.

The final file passed sponsor QC with a terminology consistency score of 98.7%.

Tools and Process: Don't Rely on Machine Translation

Machine translation may work for short strings like "Yes," "No," or "N/A," but error rates are high for comments and complex descriptions. Medical spreadsheet translation must be handled by linguists with life sciences backgrounds and reviewed by terminology experts.

If your team is struggling with compliance in Excel file translation, let Linguist's engineering team perform a free file health check. No fee, no sales pitch.