Internationalizing the GNUmed client

There are two major parts to making GNUmed work in different locales: making the user interface (UI) work with the local look-and-feel and adjusting the interface to local functional requirements.

Look-and-feel internationalization

First and foremost, this regards translating the UI (menus, plugin names) and configuring sets of values (types of encounters, types of documents) into the local language. Other aspects to making the EMR more locally-familiar include such things as date and time formats, which are controlled by such settings as the computer (or user) LOCALE settings.

Translations for the UI are managed by the files within the client and can even allow a user to maintain a totally personalized UI. See more about Translating the UI.

Translation of sets of values in the database is achieved in part through GNUmed menus such as GNUmed > Master data. See more about Translation in the Backend.

Interface translation already goes a long way to make GNUmed usable for doctors in other countries because basic medical functionality is very similar all over the world.

Functional internationalization

To make the GNUmed client conform to local requirements we offer a plugin architecture and signal based data processing. This is done on an as-needed basis only.