Problem

Depending on which part of the openIMIS community is translating things into another language version, there are currently different, diverging language silos. Web-page, manuals, facts sheets and so on have started to create their own glossary lists which are not harmonized. As a result, different terms are being used for the same things in each of the silos. On the other hand there are international standards set by e.g. FHIR or JLN.

Approach

Use of a central glossary in this wiki to manage terms and print-ready documentation pieces in the wiki. The first version was instantiated with glossary terms from the report in https://openimis.atlassian.net/wiki/spaces/OP/pages/807600219.

• English version: https://openimis.atlassian.net/wiki/spaces/KB/pages/808386618

• French test version: https://openimis.atlassian.net/wiki/spaces/FR/pages/821329993

This approach is oriented at the way wikipedia is managing different language version: There is one wiki page for each term which links to the corresponding wiki-page of the term in other language version. If done properly, dictionary tables and glossaries can be created automatically:

• for translations

• of definitions of terms

Furthermore, each wiki page can be used to elaborate each term in more detail, e.g. link different alias uses of the term, harmonise different representations in different standards (e.g. JLN, FHIR).

Way forward

1. Collect all relevant openIMIS resources e.g. dictionaries, definition lists etc:

2. Harmonise the terms in the English glossary:

3. Translate the English terms to the other language space, e.g French:

4. Update and correct document translations based on the openIMIS dictionary:

Ressources

• web page: www.openimis.org
  Texts are maintained in directly in the CMS under Drupal. There might be an initial starter version of the used texts which was used to define the first version of each page, but this is most likely not corresponding to the versions in the Drupal any more. As a result, the Drupal version is the leading version.

• user interfaces (go to the shared glossary of the web-front end project):
  The user-interfaces of the software are feeding from language resources, that are being maintained in a platform with a central glossary.

• key word list in starter kit:

• JLN Glossary of Health Insurance terms:

• FHIR Terminlogy: https://www.hl7.org/fhir/financial-module.html#fingloss

• WB Bible on Social Protection:

  • EN: https://socialprotection.org/discover/publications/sourcebook-foundations-social-protection-delivery-systems

  • FR: https://socialprotection.org/fr/discover/publications/sourcebook-foundations-social-protection-delivery-systems