Medical and Scientific Translation Across Canada Contact us Français

Home/Industries/Translation Services for Digital Health and Telehealth Companies

Translation Services for Digital Health and Telehealth Companies

Digital health companies ship text every week: new screens, reminders, help articles, consent flows and privacy updates. Mediwords translates that text with native medical translators who understand both clinical language and software constraints, so patients and clinicians read your product in their language without broken variables, truncated buttons or medical terms that mean something else.

Get a quote
  • App strings
  • Patient portals
  • Privacy notices
Product manager reviewing translated screens of a telehealth app on a phone and a laptop

Trusted by healthcare and life sciences organizations

  • Dexcom logo, client of Mediwords
  • Canadian Cancer Society logo, client of Mediwords
  • Allianz logo, client of Mediwords
  • Sun Life logo, client of Mediwords
  • YMCA New Brunswick logo, client of Mediwords
  • Sinai Health logo, client of Mediwords

Translating a Health Product That Never Stops Changing

Health apps, telehealth platforms and patient portals combine clinical content with interface text: appointment reminders, help centres, onboarding screens, consent flows, privacy notices and app store listings. Mediwords translates these connected touchpoints for digital health teams, with terminology that remains consistent across the patient journey and successive software releases.

A printed leaflet is translated once. A health app is translated continuously. Each release adds strings, changes a label or rewrites an onboarding step, and the translated versions have to follow without delaying the release. The text is also read in fragments: a button, an error message, a reminder on a locked screen. Each fragment has to make sense on its own and fit the space your designers gave it.

Our work in this sector includes projects for WELL Health and Predictive Healthcare. We distinguish clinical terminology from interface labels, preserve technical placeholders and flag strings whose meaning depends on missing screen context.

Consistency matters as much as accuracy. When "appointment" is translated one way on the booking screen and another way in the reminder email, users wonder whether they are dealing with two different things. We keep one glossary for your product across releases and translators.

Who Reads Each Part of Your Product

The same product speaks to different readers, and the translation has to change register with them:

Part of the productReaderWhat the translation needs
Patient app screens and buttonsPatients of every age and literacy levelShort, plain words that fit the interface
Clinician dashboards and notes templatesPhysicians, nurses, pharmacistsPrecise clinical terms used in Canadian practice
Notifications, SMS and email remindersPatients, often on a lock screenThe key information in the first words, within length limits
Onboarding and consent to virtual careNew usersClear choices, nothing hidden in the wording
Help centre and FAQUsers with a problemSteps that match the translated interface exactly
Privacy notice and terms of useUsers, privacy officers, regulatorsLegal precision in plain language
App store listingPeople deciding whether to installNatural, search-friendly descriptions

Strings Are Not Sentences

Software text breaks in ways a document does not. Our translators handle the technical side as carefully as the medical one:

Placeholders and variables

We preserve variable names and token syntax while checking whether the target language requires a different word order. Potential issues with dynamic doses, dates or formatting are flagged for developer review.

Plurals and gender

Messages like "You have 1 new result" need different forms depending on the number, and some languages also change with gender. We use the plural and gender forms supported by your localization framework, and flag cases where the available string structure cannot express the target language correctly.

Length and context

French and many other languages often take more space than English. Screenshots, character limits and descriptions of each screen help us propose accurate wording. Final fit, accessibility and behaviour are tested in context by your product team.

Accessibility text is part of the localization scope too: screen-reader labels, field instructions, validation errors and accessible descriptions should remain meaningful in each language. We can translate the supplied strings, while implementation and accessibility testing remain with your design and engineering teams.

We work in the formats your developers export, such as JSON, XLIFF, strings and resource files, and return them with the same keys and structure. We preserve source keys, markup and protected variables during the linguistic workflow. Your development team remains responsible for importing the files and running functional and visual checks in the live application.

Canadian Rules That Shape Your Translated Product

Several rules affect which languages you need and how your legal text must read. Your legal and regulatory advisers decide what applies; these are the ones our clients mention most:

  • Quebec's Charter of the French language includes rules on the availability of software in French (section 52.1), alongside requirements that may apply to customer-facing documents and other communications. Whether a specific app, interface or contractual document is covered depends on its use and distribution; your legal team confirms the obligations for your product. Read the Charter.
  • Privacy notices: Federal and provincial privacy laws may apply depending on your organization and the information processed. For example, Quebec's private-sector privacy legislation includes requirements concerning confidentiality policies for technological collection of personal information. Mediwords translates approved privacy content; your privacy counsel determines the applicable legal requirements and approves the final wording.
  • Software as a medical device: some software functions may qualify as medical devices according to their intended medical purpose. Health Canada's guidance on software as a medical device explains the definition and classification of software as a medical device (SaMD). Manufacturers remain responsible for regulatory classification and for approving the applicable labelling and instructions.

When Your App Is a Medical Device, and When It Is Not

Many digital health products are wellness or administrative tools: booking, reminders, messaging, records access. Software intended to analyse clinical information, support diagnosis or recommend treatment may qualify as software as a medical device, depending on its intended use and Health Canada's criteria. When that applies, we translate approved instructions, warnings and alarms under document and terminology control; your manufacturer and regulatory team retain responsibility for device classification, risk management, verification and approval.

Our page on medical software translation covers device screens, alarms and regulated software text in detail. For your marketing site and patient-facing web pages, our medical website localization service covers web content, metadata and search keywords in each language.

Virtual Care in More Than One Language

Telehealth reaches patients who do not live near a clinic, and many of them are more comfortable in a language other than English. Appointment reminders, pre-visit questionnaires, consent to virtual care and after-visit instructions are the texts that most often decide whether a visit goes well.

We translate these texts between English and Canadian French and into more than 30 languages, including Punjabi, Mandarin, Arabic, Tagalog and Spanish. For sensitive clinical instructions, we preserve the clinician-approved content and flag ambiguity rather than rewriting the care advice. For French, our page on English to French medical translation explains why Canadian users expect Canadian vocabulary rather than European French.

Clinical Words Patients Read Differently

Digital products put clinical vocabulary in front of patients without a clinician there to explain it. A few words cause most of the confusion, in English and in translation:

Positive and negative

A negative result is good news for most tests, yet patients often read it as bad. We follow your clinical team's patient wording and keep it identical across screens, emails and help articles.

Chronic and acute

These terms describe duration, not severity, and literal translations can sound alarming. Patient-facing screens use the plain words your medical reviewers approved.

Normal range

A value outside the range is not always a problem. The translated message keeps the same caution as the source, without adding reassurance or worry.

We maintain an approved patient-facing glossary across releases. Our role is to preserve clinical meaning and the approved tone; the client's clinical team signs off on any change to health guidance, risk wording or interpretation of results.

Working With Your Release Cycle

A rhythm that keeps translated versions in step with English:

  1. Export. Your team sends the new or changed strings, with screenshots or screen names when available.
  2. Translation. A native medical translator translates the strings, keeping keys, placeholders and formatting.
  3. Revision. A second linguist checks meaning, terminology and consistency with the existing translated product.
  4. Questions. Anything ambiguous, such as a label whose context is unclear, is sent back as a written query rather than guessed.
  5. Return. We return files in the agreed format, with their keys and placeholders preserved, for import and testing by your development team. Price and delivery dates are agreed before each batch.

For recurring releases, we can use an approved glossary, translation memory and version references to keep changes consistent. Please provide the relevant source-string identifiers, screenshots and any approved clinical or legal copy so that questions can be resolved before the release is finalized.

Questions From Digital Health Companies

Do you translate app strings in JSON, XLIFF or strings files?

Yes. We work with JSON, XLIFF, .strings and other agreed localization files, preserving keys, placeholders and protected syntax. Your developers validate the imported files and their behaviour in the application.

Can you translate small batches for every release?

Yes. We handle recurring release batches using your approved terminology and previous translations. We agree on pricing, turnaround and priorities for each batch before work begins.

Do you translate privacy notices and terms of use?

Yes. We translate approved privacy notices, terms of use and consent flows with attention to clear language and consistent terminology. Your legal or privacy team approves the final text and confirms jurisdiction-specific requirements.

Does our app need to be in French for Quebec users?

Section 52.1 of Quebec's Charter of the French language addresses the availability of software in French, and other provisions may apply to public-facing communications and contracts. The requirements for your product depend on its circumstances; consult your legal advisers for an applicability assessment.

Can you translate regulated software text such as alarms and warnings?

Yes. We translate approved device screens, alarms, warnings and on-screen instructions with specialist linguistic revision and version control. Your regulatory and engineering teams remain responsible for verification, usability testing and final approval.

Which languages do telehealth companies usually need?

English and Canadian French are core combinations, alongside more than 30 languages including Punjabi, Mandarin, Cantonese, Arabic, Tagalog and Spanish. We select the target languages according to your users and markets.

Can you translate our app store listing?

Yes. We localize app store descriptions, feature summaries and release notes for your target market while preserving approved medical claims and respecting any supplied platform length limits.

What do you need to start a first project?

Send your string files or exports, screenshots or screen descriptions, target languages, existing glossary or approved copy, and release deadline. Share character limits and any regulatory or clinical review requirements where relevant.

Do you provide interpretation for telehealth visits?

No. Mediwords provides written translation only.

Get a Quote for Your Next Release

Send us your string files or screens with 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.