Skip to main content

How do I translate NexHealth for patients?

Use NexHealth's multilingual translation support to communicate with patients in their preferred language.

For use with NexHealth Forms, Communications, and Templates.

How patient preferred language gets set depends on your health record system.

Automatic (NexHealth reads it from your PMS)
NexHealth reads a patient's preferred language directly from your practice management system for: Dentrix, Eaglesoft, Open Dental, Dentrix Enterprise, and Orthotrac.

Manual (you set it in NexHealth)
For all other health record systems, NexHealth does not read preferred language from the PMS. You'll need to collect or set it one of two ways:

  • Add a Preferred language form field to any form so patients can select their language when they fill it out.

  • Go to the patient's profile and select Actions → Edit patient info to set their preferred language directly.

Once a patient's preferred language is set in NexHealth, they'll automatically receive communications in that language — as long as you've set up translations.

Bulk translate all templates, campaigns, and forms

Translate everything at once into one or more target languages.

1. Go to Settings → Translations.

Use the gear icon to open Settings, then click Translations in the left-hand sidebar.

2. Select + New translation.

Click + New translation at the top-right.

3. Select the desired language(s) to translate.

You can translate into multiple languages at once.

Use a list to checkmark which languages to translate into.

4. Re-translate as needed by selecting Edit for a language.

Select Edit next to a language to re-translate all your forms, campaigns, and templates in bulk — useful after you've updated many templates. Click Translate all. This will overwrite all existing translations for that language.

Translate individual templates

1. Go to Templates and select a specific template.

Select a Template to translate. You can also go directly to Reminders, Recalls, or Reviews from the left-hand sidebar.

2. Click Add translations.

Select Add translations from the upper right.

3. Select the desired language(s) to translate.

Any existing translations will be overridden.

4. Click Translate.

This will translate all steps in the template.

The translation will run in the background and may take some time. Refresh the page to view the translated content.

5. Review the messages.

Edit specific steps and select the translation from the top-left dropdown. Preview the message to confirm the translation looks right. Leave any Smart Commands intact.

Translate individual messages in templates, campaigns, or forms

Whether you're translating a form, a campaign, or an individual SMS or email within a template, the steps look the same. Patients whose preferred language matches a translation you've set up will automatically receive that communication in their language.

1. Start editing the communication you'd like to translate.

2. Click the + Language translations tab.

At the top of the editor, click + Language translations.

+Language translations is in the upper-left

3. Select a language and click + Translate.

Find the desired language and click + Translate.

+Translate is on the right side.

4. Preview, then Save.

Click Preview to review the translated content in context.

If you update your English content and want translations to reflect the change, click Remove the translation from the template editor, then follow steps 2–3 to re-translate.

FAQs

Can we add another language that's not listed?

That may be possible. Please let our team know.

How do I make changes to a translation?

  1. Click into the boxes on the right-hand side of the translation window to edit directly.

  2. To delete a translation, click Remove translation in the top right.

Why are there weird symbols in the translation?

Some forms use special formatting that appears as symbols in the translation table. When you Preview the form, these won't appear.

I don't have the patient's preferred language on file. How can I add it?

Did this answer your question?