You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Avni has the ability to add subjects and encounters as form elements. However, the name of subjects/encounters is usually not sufficient to directly recognise them. We have several mechanisms in place to make this more specific.
On search results and subject select, we show the "Search Result Fields"
For encounter form fields, there is an "Encounter Identifier" field where we specify a format for a readable value of the encounter.
For one organisation, there is a hardcoding where we show the "Mobile Number" if the subject type is "Farmer"
This epic is to look at all these mechanisms and come up with a consistent way of configuring and displaying identifying values for these entities on forms (entry and view), search results across both android app and web app
The text was updated successfully, but these errors were encountered:
Avni has the ability to add subjects and encounters as form elements. However, the name of subjects/encounters is usually not sufficient to directly recognise them. We have several mechanisms in place to make this more specific.
This epic is to look at all these mechanisms and come up with a consistent way of configuring and displaying identifying values for these entities on forms (entry and view), search results across both android app and web app
The text was updated successfully, but these errors were encountered: