Home/Documents/Medical Software Translation
Medical Software Translation Services
Mediwords translates and localizes medical software for device manufacturers, digital health companies and healthcare technology providers. From device interfaces and alarms to patient portals and clinical applications, our specialized translators work with your string files, preserve technical placeholders and review translated screens in context to support clear, consistent communication.
Get a quote- Strings in context
- Placeholders intact
- Native translators

Trusted by healthcare and life sciences organizations
What Medical Software Translation Involves
Medical software translation helps healthcare technology companies adapt user interfaces, clinical applications and software-generated content for different languages and markets. Our linguists work with menus, device screens, alarm messages, patient reports, notifications and help content, while preserving technical variables, terminology and interface constraints.
Software is not read like a document. Strings arrive in files without context, words like "Set" or "Clear" can mean several things, and the translation must fit a button designed for a short English word. A wrong word on a screen can lead to a wrong action, which is why medical software needs medical translators who also understand how software text works.
In Canada, some healthcare software is regulated as a medical device, depending on its intended medical purpose and functionality. Health Canada’s guidance on Software as a Medical Device (SaMD) explains how standalone medical software is defined and classified. Software that operates as part of a hardware medical device is assessed differently, while many administrative, telehealth and general wellness applications do not qualify as medical devices. Mediwords provides specialized linguistic localization for these different software environments.
Software We Translate
From a single device screen to a complete platform:
Device User Interfaces
Screens of infusion pumps, monitors, analyzers and imaging systems, with menus and settings.
Alarms and Error Messages
Alarm text, warnings and troubleshooting messages, where every word must be unambiguous.
Software as a Medical Device
Standalone software intended for regulated medical purposes, including certain diagnostic, monitoring and clinical decision-support applications, with terminology aligned across interfaces, reports and accompanying documentation.
Mobile Health Apps
Apps paired with devices, medication reminders and symptom trackers, from iOS and Android string files.
Patient Portals and Telehealth
Patient portals, appointment booking, secure messaging, virtual care interfaces and other healthcare applications, localized for clear communication and accessible navigation.
Medical website localizationGenerated Reports
Report templates, result labels and printouts generated by laboratory or clinical software.
Help and Release Notes
Online help, onboarding screens, release notes and user guides.
Notifications
Push notifications, emails and text messages sent by the software to patients and staff.
File Formats We Work With
| Source | What you send | What we deliver |
|---|---|---|
| Mobile apps | iOS .strings, Android .xml or JSON files | Translated files with keys and placeholders intact |
| Web applications and portals | JSON, XLIFF or CSV exports | Files in the same structure, ready to import |
| Device software | String tables in Excel, CSV or XLIFF | Translated tables with length checks |
| Help content | HTML, Word or CMS exports | Translated content in the same format |
| Screens for review | Screenshots or a test build | Comments and fixes after review in context |
We do not need access to your source code. We work from exports prepared by your development team and return files in the same structure.
Common Pitfalls in Software Localization
These are the problems we catch before your users do:
Placeholders and Variables
Variables such as {0}, %s and {patient_name} must be preserved without altering their syntax. We check their presence and placement in translated strings and flag any cases where grammar or word order requires special handling by the development team.
Length Limits
A French label is often longer than the English one. We respect character limits and propose short forms that remain clear. When a safe, understandable translation cannot fit the available space, we flag the limitation rather than introducing an ambiguous abbreviation.
Ambiguous Strings
A single word without context, such as "Set", is translated only after we know if it is a verb, a noun or a setting. We ask, or we check the screen.
Plurals and Gender
Messages like "1 alarm" and "3 alarms" need plural rules, and French adjectives change with the noun they describe.
Numbers, Units and Time
We apply appropriate locale-specific conventions for decimal separators, dates and time formats while preserving numerical values, measurement units and clinical meaning. Any unit conversion or change to displayed values requires explicit approval and technical validation by the client.
Joined Strings
Sentences built from several strings often break in translation. We flag them so your developers can fix the source.
Consistent with Your Labels and IFU
The words on the screen must match the words in the instructions for use, on the labels and in the training. If the manual tells a nurse to press "Pause" and the screen says "Suspend", the user hesitates at the wrong moment. We use one glossary across the software and the IFU translation, and we translate the screen captures used in the manual with the same terms as the live interface.
Software interface localization is one part of a broader medical device documentation project. Our medical device translation services cover instructions for use, technical manuals, regulatory documents and other product materials, while this service focuses on software strings, screen messages, interface terminology and localized application content. For the Canadian market, applicable language requirements should be assessed by the manufacturer’s regulatory or legal team.
Safe and Usable Translated Interfaces
On a medical device, the user interface is part of safety. A clinician must understand an alarm at a glance, and a patient must know which button confirms a dose. A translation that is accurate but long, abbreviated in an unusual way or inconsistent from one screen to the next makes the software harder to use.
Our translators choose short, standard terms that users already know, keep the same verb for the same action everywhere and avoid abbreviations unless the device space leaves no choice. When an abbreviation is unavoidable, we propose one that a French-speaking clinician would recognize and list it in the glossary for your team and your documentation.
Our linguistic reviews help identify unclear wording, inconsistent terminology and potential interface misunderstandings. Final usability validation, software testing, risk assessment and regulatory approval remain the responsibility of the manufacturer or software provider.
Patient-Facing Apps in Plain Language
Apps and portals used by patients need a different tone from device screens used by clinicians. A patient tracking blood glucose or booking a video visit reads on a small screen, sometimes with poor eyesight or limited health literacy. We write short sentences, everyday words and clear instructions, and keep medical terms only where they are needed.
Notifications deserve the same care: a reminder must be understood from the first words, before the rest of the message is cut off on the lock screen.
How We Localize Medical Software
- Preparation. We review the string files, character limits and screenshots, and agree on how to handle placeholders and untranslatable strings.
- Glossary. We align key terms with your labels, IFU and existing French material.
- Translation. A native medical translator translates the strings, with screenshots or notes for context.
- Revision. A second linguist checks every string, including placeholders, length and consistency.
- Check in context. We review the translated screens in a test build or screenshots and correct anything that is cut off or unclear.
- Updates. For each new release, we compare updated resource files with previously approved translations, identify new or changed strings and review unchanged strings where functionality or context has evolved. This helps maintain consistency while avoiding unnecessary retranslation.
For Digital Health Companies and Device Makers
Our software clients range from device manufacturers adding a French interface for the Canadian market to digital health companies launching an app or a portal for patients across Canada. For a patient-facing app, we also translate the store listing, the onboarding screens and the privacy notice, so the first French a user reads is as clear as the rest.
What to Send Us for a Quote
- String files: exports in their native format, with character limits if they exist
- Context: screenshots, a test build or a short description of each screen
- Related documents: IFU, labels or existing French terms
- Target languages: and the date of your release
- Update plan: how often you release new versions
With these, we send a fixed price and a delivery date within one business day.
Medical Software Translation FAQ
Which file formats do you translate?
We translate iOS .strings, Android .xml, JSON, XLIFF, CSV and Excel string tables, and return them in the same structure.
Do you need access to our source code?
No. We work from exports prepared by your developers and return translated files ready to import.
How do you handle placeholders and variables?
Placeholders stay untouched. Our translators and reviewers check that each one is present and correctly placed in the translated sentence.
Do you provide linguistic testing for medical software?
Yes. When you provide screenshots or access to a test build, we review localized screens for terminology consistency, truncated text, unclear messages and language-specific formatting issues. Functional testing, usability validation and regulatory approval remain with your development and quality teams.
Do you translate software that is regulated as a medical device?
Yes. We translate the interface, alarms, reports and help of software as a medical device, consistent with its labels and instructions for use.
Can you localize medical software across multiple releases?
We maintain approved terminology and translation resources across releases, translating new and modified content while reviewing existing strings when their context changes. This helps keep the interface consistent as your software evolves.
Can you translate our app store listing?
Yes. We translate the store description, screenshots text and release notes along with the app.
Do you translate software into languages other than French?
Yes. We localize software into more than 30 languages, including right-to-left languages such as Arabic and Persian.
Can you translate very short strings without context?
We translate them once we know how they are used. When the meaning is unclear, we ask your team or check the screen before translating.
Related Services
Get a Quote for Your Software
Send us your string files, a few screenshots and the languages you need. We reply within one business day with a fixed price and a delivery date. You can also write to us at info@mediwords.ca.