Medical App Localization: Compliance Traps and Engineering Practices

Medical App Localization: Compliance Traps and Engineering Practices

Last year a digital therapeutics company came to us after their diabetes management app was flagged by German regulators. The issue wasn't the algorithm. It was the German version of an insulin dose reminder: mg/dL had been translated as mmol/L without converting the value. This is not an isolated case. Medical app localization without a compliance framework is a liability.

Why mobile app localization in healthcare is a high-risk operation

A mistranslation in a consumer app is a UX annoyance. In a medical app, it can constitute mislabeling of a medical device. Under EU MDR 2017/745, if an app is intended for diagnosis, prevention, or treatment of disease, it is a medical device. Its UI text, alerts, and instructions for use (IFU) are regulatory materials.

That means:

• Translation changes must go through change control, not hotfixed like marketing copy.
• Multilingual versions need version traceability synced with source code, aligning with IEC 62304 software configuration management.
• Clinical terminology must undergo clinical review, not be left to linguists alone.

We once saw a blood pressure logging app where the Japanese version swapped the labels for systolic and diastolic pressure. Linguistically correct. Clinically fatal.

Engineering the app translation workflow: from strings to controlled documents

Medical app localization does not start with "export to Excel." Our standard approach:

1. String asset audit

Classify text into three types:

Text type	Example	Handling strategy
Static UI	Buttons, menus	Translation memory + termbase
Dynamic content	User reports, notifications	Templated + placeholder validation
Regulatory text	IFU, contraindications	Controlled translation workflow with sign-off

Critical step: verify all variable placeholders (e.g., {value}, %s) are preserved and in correct order in the target. We run regex validation scripts before every delivery.

2. Termbase first

Medical terminology must be locked. For example, "adverse event" in Chinese is "不良事件", never "副作用" (side effect). A termbase should include:

• Source term
• Target term
• Definition source (e.g., ICH E2A)
• Forbidden translations

An incomplete termbase means garbage in, garbage out for translation memory.

3. Context screenshots

App translation without screenshots is blind translation. We require UI screenshots for every string, with character limits noted. German is typically 30% longer than English. Arabic right-to-left layout can break buttons.

4. Language quality assurance (LQA)

Follow ISO 17100 for translation, revision, and final verification. Medical projects add clinical review by bilingual staff with medical backgrounds to check dosages, units, and contraindications.

Managing multilingual versions: the drift trap

The most common failure in app multilingual projects is not translation quality—it's version drift.

The English version updates "maximum daily dose" from 4 to 3 times, but the French version doesn't. In an audit, that's a critical defect. Our approach:

• Manage strings as localization key-value pairs bound to the code repository.
• Run string consistency checks before each release, comparing key terms between source and target.
• Maintain a translation change log to meet MDR traceability requirements.

Real case: how IFU localization prevented a recall

An insulin pen companion app was preparing for the Brazilian market. The Portuguese IFU draft translated "prime the pen" as "preparar a caneta" (prepare the pen), which is ambiguous. Clinical review flagged that Brazilian diabetes education uses the fixed phrase "tirar o ar" (remove air). After correction, user testing showed error rates for the priming step dropped from 18% to 3%.

No translation standard captures that detail. Only local clinical experience does.

Your app localization checklist

Before submitting to app store review, confirm:

• All medically relevant strings are under change control
• Termbase covers dosages, units, anatomy, symptoms
• Variable placeholders match source exactly
• UI screenshots provided with character limits
• Clinical review completed and signed off
• Multilingual versions correspond to source code version
• Translation memory updated and archived

Medical app localization has no "close enough." One unit symbol, one swapped label, can trigger regulatory action. If your team is preparing a multilingual launch, contact the Linguist team for a tailored compliance localization plan.