Concept fetching by FSN should be driven by the default locale- Registration App

Description

Across the board Bahmni relies a lot on fetching concepts by FSN (Fully Specified Name). When doing so it explicitly or implicitly does it for the current locale (so the user locale). In a multi-locale environment this will lead to issues when the FSN of a concept is not found in other locales than 'en'.

Example: concept "All Observation Templates".
For this concept to be fetchable in 'es' also, the Spanish FSN must be set to the same exact string than in English:

'en' FSN

'es' FSN

All Observation Templates

All Observation Templates

Suggested solution

Ensure that when concepts are fetched by FSN it is always done for the default locale. This will turn the default locale as the configuration locale.

The following are the cases on the registration app, where the concepts need to be fetched in default locale:

Dropdowns in

1. Additional patient info -> rationcard type, cluster
2. Other info -> education details,class, occupation

3.Death info
4.Height and Weight

The API associated with the scenarios is BahmniConceptSearchHandler

 

 

Status

Assignee

Swetha Bachugudem

Reporter

Swetha Bachugudem

Units

None

PercentDone

None

DueTime

None

Clients

None

External issue ID

None

UAT Assignee

None

Reviewer

None

Components

Sprint

Fix versions

Configure