Skip to content

Localization

CareFlow Kids and CareView Family are designed to support multiple languages.

The goal is to allow the applications to be used in different clinical environments while keeping medical data structured and language-independent.

Supported languages

The applications may provide user interface translations for multiple languages depending on the distribution version.

Examples may include:

  • English
  • French
  • Chinese
  • other languages as translations become available

The language used in the interface does not change the underlying medical data structure.

Language-independent clinical data

Clinical information stored inside .pemr bundles is designed to remain language-neutral whenever possible.

For example:

  • structured tokens
  • standardized coding systems
  • structured clinical fields

This approach ensures that:

  • the same .pemr bundle can be opened in different languages
  • reports can be generated in different languages if needed
  • data remains interoperable across environments.

Localization architecture

The applications use a localization-ready architecture.

This means:

  • user-visible text is separated from program logic
  • translations are stored in localization files
  • additional languages can be added without modifying core logic

This design allows the application to expand to new locales in the future.

Reports and language

Visit reports generated from the application reflect the current interface language used by the clinician.

However:

  • structured medical data stored in the bundle remains unchanged
  • the same bundle can be reopened later with another language setting.

Free text and mixed-language records

Some fields in the applications allow free text entry (for example clinical notes, comments, or addenda).

Free text is stored exactly as entered and is not automatically translated when the bundle is opened using another interface language.

As a result, if the same .pemr bundle is opened in applications configured with different locales, some sections may contain multiple languages.

For example:

  • clinician notes written in one language
  • parent notes written in another
  • reports generated in the interface language used at the time

In practice this situation should remain uncommon, because clinicians and families usually communicate using the same language during care interactions.

Nevertheless, the system preserves the original text exactly as written to avoid altering the clinical record.

Future localization improvements

Possible future improvements may include:

  • additional interface translations
  • localized medical report templates
  • region-specific clinical terminology
  • support for additional locale settings.