This page is part of the International Patient Access (v0.1.0: STU 1 Ballot 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

Internationalization Issues

Considerations for internationalization and localization

The International Patient Access specification provides a base underlying specification intended to be localized by individual countries to meet national laws, regulations and accepted practice.

It also provides for producers of generic patient-facing applications a basis on which to build, so that the application would be as compatible as possible with as many globally available implementations as possible.

This base version of the specification aims to provide general guidance rather than hard rules. The authors of the specification welcome feedback and suggestions on what should be required of implementations.

Language

This version of the specification makes no specific rules around language. However, further versions and other specifications building on top of this base specification are expected to impose constraints and recommendations on language.

Codeable concepts

To be usable for a wide range of internationally available applications, implementations SHOULD include codes from internationally supported code sets when they can. It is often not practical to store resources with textual descriptions in all possible languages, or even to populate this information on the fly. Rather, it is expected that applications rely on code systems and terminology servers to obtain human readable terms when required, for the language applicable. Therefore, implementers are encouraged to focus on providing extensive coverage of various code sets for codeable data, rather than focusing on support for an extensive number of languages for international apps and use cases.

Not all available data is always coded, and not all data can be coded with code systems. Also, for most patients their healthcare is most valuable in the language it is authored with. Therefore, applications SHALL be able to use the text representation of data elements when presenting data in a user interface when the coded data cannot be used.

Non-codeable concepts

There is also information that cannot be easily described with a code system, such as person names and addresses.

To be usable for a wide range of internationally available applications, implementations SHOULD expose the text element for this kind of data.